[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: KDE phoning home



On Thu, 4 Sep 2025 18:41:31 +0500, Andrey Rakhmatullin wrote:

> On Thu, Sep 04, 2025 at 03:33:01PM +0200, Martin Steigerwald wrote:
>>Not using Systemd here, so cannot really comment on that. Grepping the
>>process list during a running Plasma session for "konqi" or "sentry"
>>does not reveal any processes.
>>
>>But it should be possible to disable or mask the service? It might be a
>>user session related service and disabling or masking it might need a
>>special syntax. With "systemctl status" you should be able to find out
>>the location of that service file. Would be interesting to see what
>>binary it launches ("Exec=") and what package it is from ("dpkg -S").
> 
> /usr/lib/systemd/user/drkonqi-sentry-postman.service, from drkonqi,
> executing /usr/lib/x86_64-linux-gnu/libexec/drkonqi-sentry-postman.
> https://planet.kde.org/harald-sitter-2024-09-04-plasma-crash-course-
drkonqi/#sentry

Thank you Andrey, this was very useful as was your link to
 ~/.cache/drkonqi/sentry-envelopes

I wasn't aware of the GUI of DrKonqi but I must have clicked on "Send a 
crash report" at some point not realising that this would send a report to 
the IP that was blocked by my firewall and not helped by the fact that 
this IP doesn't have any relevant whois information or a reverse DNS, so 
it looked rather like a bogus IP to me.

Now I understand the process better I have looked at the drkonqi log files 
with Kcrash and I have 2 entries which my firewall was preventing being 
sent to crash-reports.kde.org.

The first was from light-locker which was caused by Bug #1039957. As 
suggested in the bug report I have removed light-locker, so hopefully 
there will be no more occurrences.

The second one is from kleopatra for which I cannot find any relevant 
bugs. Interestingly this crash report seems to be generated on system 
shutdown, so will probably be difficult to find the cause.

To prevent the "Phoning home" firewall reports I have whitelisted 
77.235.60.43 and after sending the pending crash report no further 
connections have been noticed to that IP.

Thank you and Martin for your help with this. I now have a much better 
understanding of drkonqi and the implications of sending reports.

Regards

Rob Brewer


Reply to: