|
Bugzilla – Full Text Bug Listing |
| Summary: | opensuse 10.3: kded crash during logout/restart/shutdown | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | ronald artos <ronartos> |
| Component: | KDE | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED NORESPONSE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P2 - High | CC: | jcea, kames, kees.bakker |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
.xsession-errors after the kded crash
debug file |
||
|
Description
ronald artos
2007-10-09 10:02:01 UTC
After each session, when logging out, or restart/shutdown. Kded always crash before going to login screen or continuing the shutdown process. Is there anything at the end of your ~/.xsession-errors? What is the output of running 'mount' ? mount display mounted partitions /dev/sda1 /boot /dev/sda3 / /dev/sda4 /home And during boot at STARTING DBUS.. nex line to it shows: User 'gdm' not exist ... By the way I'm using KDE opensuse 10.3 - note there is a checkbox below for resetting NEEDINFO - when several questions are asked, it is expected all of them will be answered, not just one of them - please install matching debuginfo packages for kdebase3,kdelibs3,qt3 and dbus-1 and provide the backtrace again Yes, I have the same problem. And it is a very critical problem by using freenx because the sessions will not ending. This bug identical to #304640. Interestingly the status of that one is RESOLVED, but the reality is that the bug is still present in openSUSE 10.3. Dirk Mueller suggests that it should be fixed in kdelibs3 3.5.7-72, but it is not. It seems to me that this bug does not show up for everyone otherwise it would have been noticed by Dirk. The question is what triggers the bug. Well, I guess I have to install the debug packages of kdebase3, kdelibs3, qt3 and dbus-1. Let's see how that goes. Later. I got a temporary fix for this problem:
1. Delete the profile of gnome's gdm in the /etc/dbus-1/system.d/Consolekit.conf
Look's like this:
<policy context="gdm">
<allow send_interface="org.freedesktop.ConsoleKit.Manager"/>
<allow send_interface="org.freedesktop.ConsoleKit.Seat"/>
<allow send_interface="org.freedesktop.ConsoleKit.Session"/>
<deny send_interface="org.freedesktop.ConsoleKit.Manager"
send_member="OpenSessionWithParameters"/>
<deny send_interface="org.freedesktop.ConsoleKit.Session"
send_member="Lock"/>
<deny send_interface="org.freedesktop.ConsoleKit.Session"
send_member="Unlock"/>
<deny send_destination="org.freedesktop.ConsoleKit"
send_interface="org.freedesktop.DBus.Properties" />
</policy>
2. Then roll back your gtk2 package from 2.12 to 2.10 which is available in GNOME:/Stable repos.
Well at least all those GTK2 and DBUS bugs are now gone by doing this. I've tested i several times and it works.
Hi, that don`t work on an 64bit System. Same Problem .. - This is not the same bug like #304640. - "Yes" is not an answer to my questions. Created attachment 178841 [details]
.xsession-errors after the kded crash
So Lubos is saying he needs the info. I can give my .xsession-errors (see attachment). (Should I check the checkbox if only half of the NEEDINFO is given?) Can anyone give me a hint as to how to make the backtrace? I've installed the debug packages of kdebase3, kdelibs3, qt3 and dbus-1, but still the KCrash windows is only visible for about one second and pressing the "Backtrace" tab doesn't help much. If I attach gdb to the kded process, then the crash does not happen. Neither does it happen if I do a "KDE_DEBUG=1 startkde" from a failsafe session. Is that bug not interesting enough ? I think this bug is a very high bug, because opensuse 10.3 can not realy work ... Can someone at least have a look at the .xsession-errors that I attached to this bug? And also, can someone give me a hint as to how to make a backtrace. Have a look at my previous comment where I explain what I already did. It's not a trivial RTFM issue. It is possible that the bug is in the RC2 already ? Bug 304640 https://bugzilla.novell.com/show_bug.cgi?id=304640 Comment #12: Your problem is unrelated to the reporter's problem (at least according to the information provided by the reporter) and we already have a patch for that, it'll be handled shortly. Setting back to NEEDINFO as information from original reporter is still needed. *** Bug 336627 has been marked as a duplicate of this bug. *** Stephan, perhaps you should get it touch with Lubos, because he doesn't agree (according to comment #16). And even if it is the same, we're somewhat in a deadlock, because Lubos wants more info, and I am unable to give the backtrace. After doing a bit of experimenting I get the impression that it is related to NFS mounts. There are two mounts on my system via NFS. If I remove those two, then I am not able to get the crashing KDED anymore. (Well, so far anyway.) Not hard evidence but still a strong suspicion. Can anyone else confirm this? Lubos, was that the reason you wanted to see the output of 'mount'? Yes I can confirm it. Simple mount with rw /server /home nfs rw Okay I found the error. Just remove /etc/init.d/dbus It works for me. Can anybody confirm that ? Sorry not remove. Change /etc/init.d/rc5.d/S01dbus to S199dbus Sorry ..... to S05dbus ok, but then the bug is still not fixed, right? Right. See comment #16 (or, alternatively, just ignore everything following comment #4). Created attachment 181508 [details]
debug file
Okay here is the debug file
I do it with
startx 2>&1 | tee startx.log
See comment #16 (and, everybody who's not the original reporter, go to bug #336627). Seems the original reporter disappeared and is not answering questions. |