IMO this isn't a Qt bug, I commented on Jira. I suspect another app isn't implementing the protocol directly, but if we really want to protect ourselves then we should probably ditch the entire session management code from Qt 4 (it's gone in Qt 5, too :)
Simon Original Message From: Matthew Woehlke Sent: Thursday, April 30, 2015 16:49 To: development@qt-project.org Cc: releas...@qt-project.org Subject: Re: [Development] Qt 4.8.7 release candidate available On 2015-04-30 09:17, Salovaara Akseli wrote: > If blocker issues for Qt 4.8.7 release (i.e. new regression) are found please > report those to bugreports.qt.io and raise issue also (with bug id) on > releasing mailing list. Is there no hope for getting https://bugreports.qt.io/browse/QTBUG-38599 fixed? This is a really nasty bug that cripples all (newly launched) Qt applications when it happens. It's listed as P1 and has been reproduced, but I don't know enough about the bowels of QSessionManager to suggest a solution. KDE4 is likely to be around for a while yet (e.g. LTS distros) and it would be good if this can be fixed. -- Matthew _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
