Page 1 of 3 123 LastLast
Results 1 to 10 of 23

Thread: KDE Telepathy acting like a key logger?

  1. #1

    Exclamation KDE Telepathy acting like a key logger?

    Looking at journalctl -f while using KDE Telepathy I see a new line appears on each key stroke in the chat window:

    Code:
    ..
    Nov 02 14:24:38 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: 536870961
    Nov 02 14:24:38 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: 536870962
    Nov 02 14:24:38 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: 536870963
    Nov 02 14:24:39 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: 536870966
    Nov 02 14:24:39 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: 75
    Nov 02 14:24:39 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: 74
    Nov 02 14:24:46 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: 50331680
    Nov 02 14:24:46 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: 50331664
    Nov 02 14:24:46 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: 84
    Nov 02 14:24:46 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: 69
    Nov 02 14:24:46 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: 83
    Nov 02 14:24:47 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: 84
    ...
    Also other messages appear in the log on chat window opening:

    Code:
    Nov 02 14:25:25 i7 org.freedesktop.Telepathy.Client.KTp.Proxy[2150]: ktp-proxy(5615) OTR::utils::getTrustLevel: Could not get trust level
    Nov 02 14:25:25 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: ** (process:5613): WARNING **: 1 dictionaries weren't free'd.
    Nov 02 14:26:03 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: ktp-text-ui(5635)/kdeui (kdelibs): Attempt to use QAction "language" with KXMLGUIFactory!
    Nov 02 14:26:03 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: ktp-text-ui(5635)/Telepathy-Qt tp-qt:0.9.5: Channel::groupLocalPendingContacts() used with no group interface
    Nov 02 14:26:04 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: tp-qt4-tpl DEBUG:  static Tpl::Utils* Tpl::Utils::instance()  :  Created Utils instance
    Nov 02 14:26:04 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: tp-qt4-tpl DEBUG:  TpAccount* Tpl::Utils::tpAccount(const AccountPtr&)  :  account= true
    Nov 02 14:26:04 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: tp-qt4-tpl DEBUG:  TpAccount* Tpl::Utils::tpAccount(const AccountPtr&)  :  objectPath= "/org/freedesktop/Telepathy/Account/gabble/jabber/studio_40anchev_2enet0"
    Nov 02 14:26:04 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: tp-qt4-tpl DEBUG:  TpAccountManager* Tpl::Utils::tpAccountManager()  :
    Nov 02 14:26:04 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: tp-qt4-tpl DEBUG:  TpAccount* Tpl::Utils::tpAccount(const AccountPtr&)  :  account= 0x1a4c160
    Nov 02 14:26:04 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: (process:5635): tp-glib-CRITICAL **: tp_asv_get_string: assertion 'asv != NULL' failed
    Nov 02 14:26:04 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: tp-qt4-tpl DEBUG:  TpAccount* Tpl::Utils::tpAccount(const AccountPtr&)  :  account= true
    Nov 02 14:26:04 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: tp-qt4-tpl DEBUG:  TpAccount* Tpl::Utils::tpAccount(const AccountPtr&)  :  objectPath= "/org/freedesktop/Telepathy/Account/gabble/jabber/studio_40anchev_2enet0"
    Nov 02 14:26:04 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: tp-qt4-tpl DEBUG:  TpAccountManager* Tpl::Utils::tpAccountManager()  :
    Nov 02 14:26:04 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: tp-qt4-tpl DEBUG:  TpAccount* Tpl::Utils::tpAccount(const AccountPtr&)  :  account= 0x1a4c160
    Nov 02 14:26:04 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: tp-qt4-tpl DEBUG:  TpAccount* Tpl::Utils::tpAccount(const AccountPtr&)  :  account= true
    Nov 02 14:26:04 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: tp-qt4-tpl DEBUG:  TpAccount* Tpl::Utils::tpAccount(const AccountPtr&)  :  objectPath= "/org/freedesktop/Telepathy/Account/gabble/jabber/studio_40anchev_2enet0"
    Nov 02 14:26:04 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: tp-qt4-tpl DEBUG:  TpAccountManager* Tpl::Utils::tpAccountManager()  :
    Nov 02 14:26:04 i7 org.freedesktop.Telepathy.Client.KTp.TextUi[2150]: tp-qt4-tpl DEBUG:  TpAccount* Tpl::Utils::tpAccount(const AccountPtr&)  :  account= 0x1a4c160
    Can this logging be turned off? I really don't want to have a key logger on my system.

    (i wonder if that should be reported as a privacy issue shomewhere)

  2. #2

    Default Re: KDE Telepathy acting like a key logger?

    [QUOTE=heyjoe;2734566Can this logging be turned off? I really don't want to have a key logger on my system.

    (i wonder if that should be reported as a privacy issue shomewhere)[/QUOTE]
    This is probably a known problem with kdelibs4 (too much debug output). It has been reported already, but I don't find the bug report at the moment...

    Actually it has been fixed upstream meanwhile, but we couldn't release the new version as update yet because it breaks the build of other KDE4 packages. And everybody was busy with finishing Leap (and handling a lot of bug reports after RC1)...

    But actually the output should not even go to the journal. Which display manager are you using? Try to switch to kdm.

    OTOH, I wouldn't be too worried about it, especially if you're the only user on this system. And other users should not be able to read *your* user's journal anyway.

  3. #3

    Default Re: KDE Telepathy acting like a key logger?

    Quote Originally Posted by wolfi323 View Post
    This is probably a known problem with kdelibs4 (too much debug output). It has been reported already, but I don't find the bug report at the moment...
    Quote Originally Posted by wolfi323 View Post

    Actually it has been fixed upstream meanwhile, but we couldn't release the new version as update yet because it breaks the build of other KDE4 packages. And everybody was busy with finishing Leap (and handling a lot of bug reports after RC1)...
    Actually I have reported it as a bug today and they told me in the comments to upgrade to 15.08. However I don't know how to upgrade as all my packages from the official repos are up to date, so I am waiting for them to say if I should upgrade to Plasma 5 for all that to work.

    But actually the output should not even go to the journal. Which display manager are you using?
    How do I check?

    Try to switch to kdm.
    How do I do that?

    OTOH, I wouldn't be too worried about it, especially if you're the only user on this system. And other users should not be able to read *your* user's journal anyway.
    Sure. But it doesn't hurt to do things correctly.

  4. #4

    Default Re: KDE Telepathy acting like a key logger?

    BTW pressing CTRL+Esc in KDE and searching for kdm showed me 3 root processes: one "X" and two "kdm".

  5. #5

    Default Re: KDE Telepathy acting like a key logger?

    Quote Originally Posted by heyjoe View Post
    Actually I have reported it as a bug today and they told me in the comments to upgrade to 15.08. However I don't know how to upgrade as all my packages from the official repos are up to date, so I am waiting for them to say if I should upgrade to Plasma 5 for all that to work.

    KDE Telepathy 15.08 doesn't have that problem, as it doesn't use kdelibs4 but rather KDE Frameworks5, yes.
    It is available for 13.2 in the KDE:Applications repo:
    https://en.opensuse.org/KDE_reposito...lications_only

    But if you want to use that, you should probably switch to Plasma5. KF5 applications should work the same in KDE4, but Plasmoids and systemsettings modules will not.

    Sure. But it doesn't hurt to do things correctly.
    Of course not.
    But this is a "bug" in kdelibs4 (actually a debug output statement has been forgotten to be removed) introduced in 4.14.9 and fixed in 4.14.10 (or something like that).

    As I wrote the kdelibs4 update causes other problems though, so we cannot just release it as-is for 13.2...
    This is fixed in Tumbleweed and Leap though, and 13.1 was not affected at all.

    Quote Originally Posted by heyjoe View Post
    BTW pressing CTRL+Esc in KDE and searching for kdm showed me 3 root processes: one "X" and two "kdm".
    Then you are using KDM apparently. Strange, debug output from applications should go to ~/.xsession-errors-:0 then.

  6. #6

    Default Re: KDE Telepathy acting like a key logger?

    Quote Originally Posted by wolfi323 View Post

    Strange, debug output from applications should go to ~/.xsession-errors-:0 then.
    Strange indeed. That file has size 0.

    So I guess I will have to jump to Plasma 5. Perhaps there are other bugs in KDE4 too and they will most probably be responded with "won't fix backwards".

    Thanks!

  7. #7

    Default Re: KDE Telepathy acting like a key logger?

    Quote Originally Posted by heyjoe View Post
    Strange indeed. That file has size 0.
    Hm, it's normal that .xsession-errors has file size 0, but .xsession-errors-:0 (or any other number, depending on which display your desktop is running) should be populated.

    So I guess I will have to jump to Plasma 5.
    Well, that's your decision.
    IIRC you did use Tumbleweed before and so should know how Plasma5 works.

    If you do want to switch, you should add the 3 repos KDE:Qt5, KDE:Frameworks5, and KDE:Applications. Then install "plasma5-session" (which will remove the KDE4 desktop), and then do a "zypper dup" (or "Switch packages..." in YaST) to all 3 of them.
    Afterwards you should have the latest Qt5, Plasma5, and all KDE Applications...

    You will have to select "Plasma 5" at the login screen too though, or else you'll probably end up in twm because KDE4 isn't found.

    Perhaps there are other bugs in KDE4 too and they will most probably be responded with "won't fix backwards".
    Yes there definitely are other bugs, but there are bugs in KF5/Plasma5 too.

    kdelibs4 is still actively maintained upstream though, it's just not always that easy to backport fixes to a released openSUSE version.
    And in previous weeks the priorities shifted more towards the next openSUSE release (Leap 42.1) that was imminent.

  8. #8

    Default Re: KDE Telepathy acting like a key logger?

    Quote Originally Posted by wolfi323 View Post
    Hm, it's normal that .xsession-errors has file size 0, but .xsession-errors-:0 (or any other number, depending on which display your desktop is running) should be populated.
    Quote Originally Posted by wolfi323 View Post
    Ah... sorry. Yes: .xsession-errors-:0 is definitely populated but it doesn't contain the string "telepathy" (case insensitive search).

    IIRC you did use Tumbleweed before and so should know how Plasma5 works.

    Wow, you remember (with so many people here)! That's amazing

    Thanks for explaining again about Plasma 5. We discussed that in the other thread. I really appreciate your help on this and I will upgrade now (fingers crossed lol).

    And in previous weeks the priorities shifted more towards the next openSUSE release (Leap 42.1) that was imminent.

    Sorry for the lame side question but can you say in short what Leap is? I have been reading the wiki and other sources found on Google but I am not sure if I am getting it. Is it aimed to replace the main version line of 13.1, 13.2... and continue it with 42.1 (instead of 13.3)? Or is it something between Tumbleweed and official, i.e. again something like a test ground. I read it is "the best of the two world" but I am not sure if that answers the simple question which (maybe) others ask too, i.e. "Is it for me?"

  9. #9

    Default Re: KDE Telepathy acting like a key logger?

    Quote Originally Posted by heyjoe View Post
    Sorry for the lame side question but can you say in short what Leap is?

    It is the next openSUSE version (i.e. the successor to 13.2), and will be officially released in two days.

    And the releases of Leap will be aligned to the releases of SLE (SUSE's commercial distribution), because it uses some packages from there.

    Is it aimed to replace the main version line of 13.1, 13.2... and continue it with 42.1 (instead of 13.3)?
    Yes and no.
    It does not really *replace* 13.1 and 13.2 yet, it's just the next version so to say.

    13.1 will still be supported for two months at least (and then by the Evergreen project as it seems), 13.2 is going to be supported until the next release (42.2) in a year plus two months.

    They just decided to change the versioning scheme and name because the development process went a bit different to earlier versions, i.e. some packages are being used from SLE (the commercial distribution), and are being maintained by SUSE (the commercial company) for the lifetime of Leap.

    Or is it something between Tumbleweed and official, i.e. again something like a test ground. I read it is "the best of the two world" but I am not sure if that answers the simple question which (maybe) others ask too, i.e. "Is it for me?"

    If it is for you, you have to decide for yourself.

    I already answered that above:
    It is "the best of the two worlds", because it contains some core packages from a commercial product (SLE, i.e. SUSE Linux Enterprise), but still a lot of packages from the "bleeding edge", i.e. Tumbleweed.
    And still it is tested automatically, like Tumbleweed is (and SLE even more).

    Btw, Tumbleweed isn't really supposed to be a "testing ground" any more either.
    It's a rolling distribution, that is actually supposed to be stable (as in working properly) all the time.
    But of course, things can happen, and not everything can be tested, especially on a rolling distribution that gets updated all the time...
    Last edited by wolfi323; 02-Nov-2015 at 15:05.

  10. #10

    Default Re: KDE Telepathy acting like a key logger?

    Thanks!

    So will we be able to update 13.2 to 42.1 in 2 days?

Page 1 of 3 123 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •