Bug 227793

Summary: ksystemlog starting as root causing problems
Product: [Applications] KSystemLog Reporter: m.wege
Component: generalAssignee: Nicolas Ternisien <nicolas.ternisien>
Status: REPORTED ---    
Severity: normal CC: gavsiu, guillaume.frognier, mail, mjwany48, smowtenshi
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=414971
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description m.wege 2010-02-20 11:42:52 UTC 
Version:           unknown (using 4.4.00 (KDE 4.4.0), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.31-20-generic

Ksystemlog ist starting as a root process. This seems to cause some problems. First it does not use the users settings for fonts, font size and so on. Secondly it crashes the crash manager appearing also starts as root, which means it does not have my settings for bugs.kde.org and then also creates a new kwallet for the root user.
Isn't it possibile to run KSystemlog as a normal user and request root right with the new Kauthframe-work when needed?
Comment 1 Christoph Feck 2010-10-12 02:42:49 UTC 
NB, did you report those crashes?
Comment 2 Christoph Feck 2015-10-19 22:35:00 UTC 
*** Bug 354106 has been marked as a duplicate of this bug. ***
Comment 3 mjwany48 2022-05-23 19:39:13 UTC 
For some reason I can't pass kdesu authentication when opening ksystemlog, even though the password is correct (I do have su user configured). 

(Interestingly however, if I launch ksystemlog from terminal as my default user (administrator account, not su and without using sudo) , it launches without prompting any password and with all tabs/logs working.  If I launch it as another user which isn't administrator, ksystemlog launches but some tabs (ex. Authentication log) cannot be opened and a message saying the user has not enough privileges is shown.)
Comment 4 Guillaume Frognier 2023-08-30 13:39:26 UTC 
I confirm this.
Comment 5 gavsiu 2023-09-16 20:06:28 UTC 
Will this be fixed in Plasma 6?