| Summary: | ending KDE session takes long time | ||
|---|---|---|---|
| Product: | [Unmaintained] ksmserver | Reporter: | ndeb |
| Component: | general | Assignee: | Lubos Lunak <l.lunak> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | kde |
| Priority: | NOR | ||
| Version First Reported In: | 2.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
ndeb
2007-11-20 21:48:53 UTC
I cannot reproduce and I'm not aware of any changes that could lead to that. Maybe you have hostname resolution broken or something else that might lead to blocking? My machine does not have a host name. "uname -n' prints "localhost'. I have always had this setting with kde-3.5.6 as well (where there was no such delay in closing KDE session). BTW, I have seen this long delay in session closing on multiple distributions (mandriva-2008.0, opensuse-10.3) using kde-3.5.7+. I've never heard of such problem and I have no idea what it could be, sorry. Guessing from "SmsDie timeout" in your log, bug #99137 and similar are unrelated. This bugreport should have nothing to do with sound (can you check, disabling logout sound, disabling sound entirely or similar?), the application for an unknown reason don't respond to ksmserver. To comment 6, as mentioned in the original report, arts is always disabled. Also, I am not logging out but simply closing the KDE/X session. I have noticed this large delay during closing KDE session on multiple OS'es (mandriva 2008., fedora 8 and opensuse 10.3). To sum up, the following are applicable in my case: 1) System run-level is 3 which means no display manager (kdm/gdm/zdm etc.) is running. 2) Arts is disabled. 3) KDE session is launched by running "startx" command. 4) The long delay appears when KDE/X session is closed down (there is no actual logout or shutdown involved) via the usual "logout" option in KDE menu. kde-3.5.9 has the same problem. *** This bug has been marked as a duplicate of bug 189004 *** |