Bug 337667 - autostart sequence fails to finish with offending program, prevents logout/shutdown/reboot
Summary: autostart sequence fails to finish with offending program, prevents logout/sh...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kdeinit (show other bugs)
Version: 4.11.5
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-21 14:17 UTC by Felipe Sateler
Modified: 2018-11-12 16:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Script that hangs autostart (794 bytes, text/x-python)
2014-07-21 14:17 UTC, Felipe Sateler
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Felipe Sateler 2014-07-21 14:17:44 UTC
Created attachment 87858 [details]
Script that hangs autostart

This was originally filed as debian bug 753610[1], and comments posted on bugs #327543 and #328571. Repeating the information I provided since this bug appears to be different from those already reported.

The first comment I posted here was:

-- First message

I cannot logout, reboot or shut down the computer from the "Leave" menu. The confirmation pop-up never appears.

I have discovered that ksmserver does not respond to the org.kde.KSMServerInterface.logout dbus method.

Also, KDE does not appear to be starting the programs configured to autostart on login (not sure  if related, but since both are session related...).

I have been unable to find any logs that might be related. xsession-errors does not say anything, nor does the X log or the systemd journal.

I'm using systemd 208. PolicyKit issues are not likely, because I can issue systemctl poweroff as my own user just fine.

I did test with a test user, and I can logout with that user. This suggests that I have some sort of misconfiguration that confuses kde.

-- End First message

And then further investigation revealed that:

-- Second Message

It seems that the problem for me is autostarting a certain type of application.

I have configured for autostart 3 applications: pasystray, arbtt and a custom python script. As long as I don't activate my custom python script, all seems to be well.

My custom script is very short. All it does is define a function, and hook it up to the org.freedesktop.ScreenSaver.ActiveChanged signal.

Given the information on this bug [#327543], I tried both glib and QT mainloops. Both hanged the autostart sequence, and prevented the exit dialogs from appearing.

Disabling the offending application seems to unbreak kde, even without QT_NO_GLIB.

-- End Second Message


If more information is required, or more testing needed, please do not hesitate to request it.

Please find attached the script that hangs the autostart sequence.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753610
Comment 1 Andrew Crouthamel 2018-11-12 02:55:34 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Felipe Sateler 2018-11-12 13:55:18 UTC
Hi,

I'm no longer using KDE, so I'm afraid I cannot verify if this bug is still present. 

Please close this bug.

Saludos
Comment 3 Andrew Crouthamel 2018-11-12 16:18:24 UTC
Thanks for the update!