[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 138582] The application KPowersave (kpowersave) crashed and
From:       vendion Gear <vendion () hotmail ! com>
Date:       2006-12-18 15:43:46
Message-ID: 20061218154346.1169.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=138582         




------- Additional Comments From vendion hotmail com  2006-12-18 16:43 -------
I still get this bug in SUSE linux 10.2, everything listed in the Crash handler is \
below.

General:
Short description
The application KPowersave (kpowersave) crashed and caused the signal 11 (SIGSEGV)

What is this?
An application mostly receives the SIGSEGV signal due to a bug in the application.  \
The application was asked to save its documents.

What can i do?
You might want to send a bug report for this application.  Check if it is listed on \
http://bugs.kde.org, otherwise mail the author.  Please include as much information \
as possible, maybe the original documents.  If you have a way to reproduce the error, \
include this also.

Backtrace
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 -1231169024 (LWP 6844)]
(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  0xb674e197 in dbus_threads_init () from /usr/lib/libdbus-1.so.3
#10 0xb673b622 in dbus_connection_send_with_reply ()
   from /usr/lib/libdbus-1.so.3
#11 0xb673b8ea in dbus_connection_send_with_reply_and_block ()
   from /usr/lib/libdbus-1.so.3
#12 0xb7f47163 in libhal_device_property_exists () from /usr/lib/libhal.so.1
#13 0xb67b95a0 in dbusHAL::halGetPropertyString ()
   from /opt/kde3/lib/libkdeinit_kpowersave.so
#14 0xb67c54dc in HardwareInfo::checkPowermanagement ()
   from /opt/kde3/lib/libkdeinit_kpowersave.so
#15 0xb67c8d90 in HardwareInfo::HardwareInfo ()
   from /opt/kde3/lib/libkdeinit_kpowersave.so
#16 0xb67da95f in kpowersave::kpowersave ()
   from /opt/kde3/lib/libkdeinit_kpowersave.so
#17 0xb67ddc9b in kdemain () from /opt/kde3/lib/libkdeinit_kpowersave.so
#18 0xb7f51764 in kdeinitmain () from /opt/kde3/lib/kde3/kpowersave.so
#19 0x0804e33f in QGList::~QGList ()
#20 0x00000002 in ?? ()
#21 0x0805c520 in ?? ()
#22 0x00000001 in ?? ()
#23 0x00000000 in ?? ()


Other
Yes i can reproduce this error, it happens everytime i start up my laptop, or go into \
the command line and try to start up kpowersave.

Also i don't know if this is the same as what mike reported, but i'm just listing \
this so this bug can be reopened.


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic