Bug 143312 - Application KPowersave (kpowersave) crashed and caused the signal 11 (SIGSEGV)
Summary: Application KPowersave (kpowersave) crashed and caused the signal 11 (SIGSEGV)
Status: RESOLVED NOT A BUG
Alias: None
Product: docs.kde.org
Classification: Websites
Component: Missing Content (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Documentation Editorial Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-21 20:01 UTC by Steve Stuthridge
Modified: 2007-03-21 22:50 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 Steve Stuthridge 2007-03-21 20:01:06 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    SuSE RPMs
OS:                Linux

Running SUSE v10.2

Crash handler appears everytime PC boots

Backtrace text is pasted in below.

Thanks for any help!


Yours faithfully,
Steve Stuthridge


*********************************************************
System configuration startup check disabled.

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231587104 (LWP 3915)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#9  0xb670e159 in libhal_device_property_exists () from /usr/lib/libhal.so.1
#10 0xb675d5a0 in dbusHAL::halGetPropertyString ()
   from /opt/kde3/lib/libkdeinit_kpowersave.so
#11 0xb67694dc in HardwareInfo::checkPowermanagement ()
   from /opt/kde3/lib/libkdeinit_kpowersave.so
#12 0xb676cd90 in HardwareInfo::HardwareInfo ()
   from /opt/kde3/lib/libkdeinit_kpowersave.so
#13 0xb677e95f in kpowersave::kpowersave ()
   from /opt/kde3/lib/libkdeinit_kpowersave.so
#14 0xb6781c9b in kdemain () from /opt/kde3/lib/libkdeinit_kpowersave.so
#15 0xb7ee2764 in kdeinitmain () from /opt/kde3/lib/kde3/kpowersave.so
#16 0x0804e33f in QGList::~QGList ()
#17 0x00000001 in ?? ()
#18 0x0807c8b8 in ?? ()
#19 0x00000001 in ?? ()
#20 0x00000000 in ?? ()
******************************************************
Comment 1 Philip Rodrigues 2007-03-21 21:18:28 UTC
Thanks for reporting this problem. Unfortunately, kpowersave bugs aren't tracked at this site, but you could try reporting the problem to the kpowersave developers.
Comment 2 Steve Stuthridge 2007-03-21 22:50:27 UTC
Philip Rodrigues wrote:
[bugs.kde.org quoted mail]

Thanks for the quick reply, much appreciated
Steve