https://bugs.kde.org/show_bug.cgi?id=374538
--- Comment #37 from imagina...@mailbox.org --- (In reply to Nate Graham from comment #36) > That can't possibly be the offending commit as it is a UI bugfix for an > unrelated piece of code (the language KCM) which has no way of touching the > logout/shutdown/reboot process. Almost thought so. The problem is to find a truly reliable trigger for this thing. The best that I could find was to load many programs (a defined set of) and then log out. But in some cases that may not have been enough to provoke the hang. So it may be that one or the other of the "goods" was a false negative which would then invalidate the final result. The "bads" were clearly bads - that's for sure. What's also puzzling for me is that some logouts happen really fast while others take really long but in the end succeed (hence the 2 minutes wait). When I'm sure I have a definitely trusty trigger I might repeat the bisect. -- You are receiving this mail because: You are watching all bug changes.