[Kubuntu Feisty] systemsettings crashes (11, SISGEGV)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kde-systemsettings (Ubuntu) |
Invalid
|
Undecided
|
Rich Johnson |
Bug Description
Since I upgraded from Edgy Eft to Feisty Fawn, systemsettings always crashes. The shell output just says that systemsettings is crashing. This is the backtrace:
(no debugging symbols found)
Using host libthread_db library "/lib/tls/
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1233127200 (LWP 19504)]
(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]
#6 0x0805bd7d in ?? ()
#7 0x08132898 in ?? ()
#8 0x00000000 in ?? ()
I am going to close this report for the time being as it cannot be reproduced nor is the crash log any good. If you can recreate this issue and get a better crash log, then I urge you to reopen this report. Thank you.