Bug 73098 - When starting KDE as a root user, there is a crash of the kdedaemon because of kmilo_thinkpad.so
Summary: When starting KDE as a root user, there is a crash of the kdedaemon because o...
Status: RESOLVED DUPLICATE of bug 73003
Alias: None
Product: klaptopdaemon
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Paul Campbell
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-21 02:45 UTC by jsvrp.gw
Modified: 2004-01-21 03:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jsvrp.gw 2004-01-21 02:45:55 UTC
Version:            (using KDE KDE 3.2.0)
Installed from:    SuSE RPMs
OS:          Linux

This is a recreation of bug #73003.

I've logged in as root in KDE 3.2RC1 and DrKonqi appears with a crash report, right away during the display of the splash-screen.
 
I've deleted .kde from the root-user, but still the same problems.

The problem also appears when starting Konqueror as a filemanager as root in a normal-user-session.

I moved /opt/kde3/lib/kde3/kmilo_thinkpad.la and /opt/kde3/lib/kde3/kmilo_thinkpad.so  to _filename and the problems are gone.

This is the backtrace (when starting konqueror as root):

[New Thread 16384 (LWP 10452)] 
 0x412a0a86 in waitpid () from /lib/i686/libpthread.so.0 
 #0 0x412a0a86 in waitpid () from /lib/i686/libpthread.so.0 
 #1 0x407bac1a in KCrash::defaultCrashHandler(int) () 
 from /opt/kde/lib/libkdecore.so.4 
 #2 0x4129f96c in __pthread_sighandler () from /lib/i686/libpthread.so.0 
 #3 <signal handler called> 
 #4 0x4160e6ce in KMilo::KMiloD::displayText(QString const&) () 
 from /opt/kde3/lib/kde3/kded_kmilod.so 
 #5 0x41787236 in ThinkPadMonitor::retrieveVolume() () 
 from /opt/kde3/lib/kde3/kmilo_thinkpad.so 
 #6 0x41785f4f in ThinkPadMonitor::init() () 
 from /opt/kde3/lib/kde3/kmilo_thinkpad.so 
 #7 0x4160df6a in KMilo::KMiloD::KMiloD(QCString const&) () 
 from /opt/kde3/lib/kde3/kded_kmilod.so 
 #8 0x4160d844 in create_kmilod () from /opt/kde3/lib/kde3/kded_kmilod.so 
 #9 0x4154e3e2 in Kded::loadModule(KService const*, bool) () 
 from /opt/kde/lib/libkdeinit_kded.so 
 #10 0x4154ddc6 in Kded::initModules() () from /opt/kde/lib/libkdeinit_kded.so 
 #11 0x41550b14 in kdemain () from /opt/kde/lib/libkdeinit_kded.so 
 #12 0x4001a894 in kdeinitmain () from /opt/kde3/lib/kde3/kded.so 
 #13 0x0804dbc9 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) () 
 #14 0x080502ac in main ()
Comment 1 jsvrp.gw 2004-01-21 02:47:55 UTC
Please note that after the crash KDE behaviour seems NOT affected.
Comment 2 George Staikos 2004-01-21 03:02:49 UTC
As I said, this is something -external- to KDE.  You should contact whoever made your packages and ask them what's wrong.

*** This bug has been marked as a duplicate of 73003 ***