Bug 73003 - When starting Konqueror filemanager as root from a normal user login, de kdedaemon crashes
Summary: When starting Konqueror filemanager as root from a normal user login, de kded...
Status: RESOLVED NOT A BUG
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kded (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: George Staikos
URL:
Keywords:
: 73098 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-01-20 03:17 UTC by jsvrp.gw
Modified: 2004-01-28 01:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

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

Using KDE 3.2R1

How to reproduce:

- Start the Konqueror filemanager as root, from the system menu
- The system will ask for the root password, give that and press OK
- After a while the Konqueror filemanager will launch, but at the same time DRKonqi pops-up with a report that the KDE Daemon crashed. This results in the following backtrace:

[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 ()

The Filemanager can be used without problems, system as whole not affected on first sight.

Cheers,

Jeroen
Comment 1 jsvrp.gw 2004-01-20 03:40:30 UTC
It seems really root-user related. I've logged in as root in KDE 3.2RC1 and DrKonqi appears with the same crash report, righ away, even during the display of ths splash-screen.

I've deleted .kde fron the root-user, but still the same problems. I don't know a way to change the summary of this bug, but it should read now:

When starting KDE as root de kdedaemon crashes 
Comment 2 George Staikos 2004-01-20 10:26:36 UTC
Where did this thinkpad module come from?
Comment 3 George Staikos 2004-01-20 10:28:59 UTC
Thinkpad module bug, not kmilo bug.
  Contact the author of that module or remove it.
Comment 4 jsvrp.gw 2004-01-20 18:23:49 UTC
This on is onot resolved.
Comment 5 jsvrp.gw 2004-01-20 18:26:49 UTC
This is nit a thinkpad bug, if you refer to the IBM thinkpad. I'm working on a intel coppermine 1ghz.

Cheers,


Jeroen
Comment 6 George Staikos 2004-01-20 21:20:21 UTC
Look at the backtrace below that you provided.  It is loading kmilo_thinkpad.  You clearly installed this because it is not part of KDE.  That is what is crashing.  Remove it and then if it still crashes (elsewhere), please provide the new backtrace.

#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&) () 
Comment 7 jsvrp.gw 2004-01-21 00:32:15 UTC
Thanks for your replies.

Sorry, but this seems to be part of kdeutils3-3.1.95:

# rpm -qf /opt/kde3/lib/kde3/kmilo_thinkpad.la
kdeutils3-3.1.95-0
# rpm -qf /opt/kde3/lib/kde3/kmilo_thinkpad.so
kdeutils3-3.1.95-0
# rpm -qf /opt/kde3/share/services/kmilo/kmilo_thinkpad.desktop
kdeutils3-3.1.95-0

Maybe you can transfer this bug to kdeutils then.

Cheers,

Jeroen
Comment 8 jsvrp.gw 2004-01-21 00:41:42 UTC
I moved the .so and .la files to _filename and the problems are gone. So that is great. On the other hand, the lib is still part of kdeutils and kdeutils is an important set of utils, so this bug still counts. I wish I could move it to kdeutils, but as a normal bugreporter I can't do that.

Cheers,

Jeroen
Comment 9 George Staikos 2004-01-21 01:04:46 UTC
Let me state again, that is -not- part of KDE.  I don't know where you got it from.

$  find | grep thinkpad
./klaptopdaemon/thinkpad_common.h
$
Comment 10 jsvrp.gw 2004-01-21 02:29:09 UTC
I find this very strange. You are first refering to  kmilo_thinkpad.so and later to thinkpad_common.h. thinkpad_common.h is not part of my system and kmilo_thinkpad.so is part of kde3utils and that is part of kde. Never mind, I will make a new bug report in kde3utils.

Cheers,

Jeroen
Comment 11 George Staikos 2004-01-21 02:32:21 UTC
Subject: Re:  When starting Konqueror filemanager as root from a normal user login, de kdedaemon crashes

On Tuesday 20 January 2004 20:29, jsvrp.gw@myrealbox.com wrote:
> ------- Additional Comments From jsvrp.gw@myrealbox.com  2004-01-21 02:29
> ------- I find this very strange. You are first refering to 
> kmilo_thinkpad.so and later to thinkpad_common.h. thinkpad_common.h is not
> part of my system and kmilo_thinkpad.so is part of kde3utils and that is
> part of kde. Never mind, I will make a new bug report in kde3utils.

  What I just proved was that the -only- thing in kdeutils is 
thinkpad_common.h.  There is -no- kmilo_thinkpad module in KDE!  You clearly 
got it from somewhere else, perhaps your distro adds it.  You must contact 
whomever you got it from.  There is nothing we can do about it, sorry.

Comment 12 George Staikos 2004-01-21 03:02:52 UTC
*** Bug 73098 has been marked as a duplicate of this bug. ***
Comment 13 Jonathan Riddell 2004-01-28 01:17:04 UTC
This problem in my KMilo Thinkpad plugin has already been fixed.  

I didn't expect packagers to pick it up so soon.