|
Bugzilla – Full Text Bug Listing |
| Summary: | sig 11 from KDED after every logout / shutdown / reboot | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Fred van Zwieten <fvzwieten> |
| Component: | KDE | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | jcea, wstephenson |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | 64bit | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
xsession-errors
kdedbacktrace |
||
|
Description
Fred van Zwieten
2007-08-25 06:53:17 UTC
That should be "investigate" :-) Can you please in a failsafe session call "export KDE_DEBUG=1" then start KDE session with "startkde" and end it. Does the error happen again? Is some error printed/backtrace in .xsesion-error? Did as you instructed. The error doesn't happen then. No file .xsession-error has been made. Install gdb and the debuginfo package for kdelibs3. From a different X session, attach gdb to the crashing kded process (without KDE_DEBUG=1), use gdb -p `pidof kded`. Then logout and switch to the gdb, type bt and paste the resulting backtrace here. Created attachment 161068 [details]
xsession-errors
Created attachment 161640 [details]
kdedbacktrace
It seems to be something to do with knetworkmanger.There will be no kded-crash if knetworkmanger is closed before shutdown.
I can confirm this bug still exists on a fresh 10.3 beta 3 install fixed for RC1 hopefully. if you try KDE:KDE3 or home:dirkmueller's kdelibs3 to doublecheck and can confirm that its fixed then that would be great! Can't check now. I forgot to take my laptop power cable home from work, and it's out of juice :-(. Maybe tomorrow. I synced with factory and it's fixed. Thanks. |