** No longer affects: qt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support session restoration
Status in KDE Base
** Changed in: plasma-workspace (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: Timo Jyrinki (timo-jyrinki) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
*** Bug 363876 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support
*** Bug 366673 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support
(In reply to Leslie Zhai from comment #61)
> Yup also worked for ArchLinux now ;-)
I use Antergos (Arch based distro) and I observed next problem. I mean
that konsole is not restored in such case. One day I shut down system
(calling proper option in K menu) and when next day I login konsole is
** Bug watch added: KDE Bug Tracking System #362671
https://bugs.kde.org/show_bug.cgi?id=362671
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
(In reply to Storm Engineer from comment #58)
> (In reply to Thomas Lübking from comment #57)
> > Firefox or cairo-dock were certainly not targetted or affected by the
> > related patches.
>
> I did some more testing, and indeed Qt apps (or at least most of them) seem
> to get restored properly
Yup also worked for ArchLinux now ;-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support session restoration
Status in
** Bug watch added: freedesktop.org Bugzilla #70593
https://bugs.freedesktop.org/show_bug.cgi?id=70593
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
Just upgraded to 5.6.0, it is NOT fixed, but quite to the contrary,
session restore is now even more broken than before.
Until now Firefox and Cairo-Dock were restored, but not anymore.
Please reopen!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
(In reply to Storm Engineer from comment #58)
> The following do NOT get restored:
> - Firefox
https://forum.kde.org/viewtopic.php?f=111=131515
> Isn't Chrome using Qt tho?
No. And as mentioned, Qt (vlc) still *is* broken itr.
It by this patch just got the *option* to not act brokenly.
Every
Sorry, forgot details:
Arch Linux 64 bit
qt5 5.6.0
plasma 5.6.0
plasma-framework 5.20.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
(In reply to Thomas Lübking from comment #57)
> Firefox or cairo-dock were certainly not targetted or affected by the
> related patches.
I did some more testing, and indeed Qt apps (or at least most of them) seem to
get restored properly now. The following get restored:
- Dolphin
-
Firefox or cairo-dock were certainly not targetted or affected by the
related patches.
This only affects Qt applications directly, so if that indeed triggered
something, either the session crashes on logout or the mentioned
applications used some timer based self-quitting (and are thus no more
Just wanted to say thank you.
I've got ~10 articles open in okular at a given time,
and since it has no session management of its own
this fix was most appreciated.
Wish I could beam you a beer.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
*** Bug 357641 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support
** Changed in: kdebase-workspace
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not
*** Bug 349432 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support
Git commit 58e49487aece3de19aae90bbb9b80cd5aab94d04 by Andreas Hartmetz.
Committed on 19/02/2016 at 18:55.
Pushed by ahartmetz into branch 'master'.
Fix session management for KApplication based applications.
- Call QGuiApplication::setFallbackSessionManagementEnabled(false)
to prevent
Git commit f7cbcc77722256db084d3b0ab6ce76173e959f0e by Andreas Hartmetz.
Committed on 19/02/2016 at 18:49.
Pushed by ahartmetz into branch 'master'.
Fix session management broken since KF5 / Qt5.
Requires Qt 5.6 branch not more than a few days old, or >= 5.6.0
when it is released.
Parts of the
Git commit a08befeac43647e222f48dfd7bed067be81573c4 by Andreas Hartmetz.
Committed on 19/02/2016 at 19:08.
Pushed by ahartmetz into branch 'master'.
KNotes: fix session save / restore.
Requires Qt >= 5.6.0 or recent 5.6 branch.
M +3-0knotes/src/apps/knotesapp.cpp
*** Bug 355707 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support
*** Bug 357942 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support
*** Bug 343518 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support
..and frankly, I don't feel like gold-plating the solution to this mess.
It's not going to be pretty either way, nobody cares too much except
when their stuff breaks (ours did), and there are many people to
convince to effect really big changes. There is bigger fish to fry.
--
You received this
Created attachment 96914
Fix session saving / KMainWindow changes
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support
Please file a review request (attaching the frameworks group), the bug is
assigned to Seli and I'm not sure anybody but us reads it.
I can already say that it lacks a QT_VERSION test.
About the Qt side, one might want to consider using a Qt::ApplicationAttribute
instead?
Created attachment 96913
Fix session saving / KApplication changes
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support
So, looking into the Qt sources a bit more it seems that
a) Session management is FUBAR in Qt5 and actually was likewise FU in Qt4 -
adding the proposed flag will only restore the completely FU condition of Qt4,
ie. allow clients (KDE) to workaround the brokeness ...
b) this actually *only*
Well, "shrug, I don't care then" - Qt seems to be dropping desktop
support anyway, so it probably doesn't really matter.
For principal reasins I'd however object " proven to be not broken by being
around for over 10 years":
It wasn't "broken" because one major client class (KDE) simply replaced
These patches mostly fix session saving (and therefore restoring),
together with the necessary Qt patch. Applications not using
KApplication or KMainWindow will need to call
QSessionManager::setAutoCloseWindowsEnabled(false) themselves. There a
some processes like that in your average KDE session
Guys, I just wanted to say a big thanks for looking into this :). Being
the original reporter of related bug #341930, session management in
*very* important for me.
While your technical discussion is way far above my technical abilities,
if there is anything I can do, like testing patches, please
I don't think that either dynamic properties or changing behavior that has been
pretty much proven to be not broken by being around for over 10 years with no
complaints will fly upstream, and I don't think they are a very good idea
myself.
For Qt5, an application attribute might be a good idea.
Those patches are just what I currently have, they are just intended to show
the important logic changes. I wasn't really planning to even submit them for
review because unfortunately I seem to be the expert on session management.
It seems pretty clear that applications either largely expect
I'm actually aware of the problem with session management since last
summer, now I've upgraded my stuff to have more KF5-based applications
and suprisingly found it still just doesn't work. So I've dived deeper
into it this time, reading all the discussion here and last part of bug
#341930, both
Fun fact (though you likely already know) - KApplication::commitData(.)
*did* send a fake close event to everything but KMainWindow ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
(In reply to Alexey Chernov from comment #30)
> The same way commercial customers or applications would be affected with API
> changes.
How an ABI styable API extension could affect anyone is frankly beyond
me - I doubt it will help to resolve the problem but there's really no
problem with it.
(In reply to Thomas Lübking from comment #26)
> (In reply to Alexey Chernov from comment #25)
>
> > According to what?
> According to "This is not fixed in years and each and every session
> management code was ported as "#if 0""
> If there was some relevant interest, it would be fixed long time,
(In reply to Andreas Hartmetz from comment #27)
> We can, however, implement a workaround in KDE (and then fix our stuff when
> something breaks):
> [...]
> Now which repository should that go in? It would be ugly to copy and paste
> the necessary code around - it should be roughly ten lines.
(In reply to Thomas Lübking from comment #22)
> > 5. I completely don't like the proposed way to preserve the compatibility
> > with (4) and make
> > the use case of broken session management client implementation legal and
> > default, but
> > also try to allow proper-written apps to still
You can't just send fake close events to clients that don't expect that.
That... technique... is a KDE specialty. KDE applications are written to
deal with it. In the general case, though, it is legitimate to start
destroying internal data structures in a close event, and it is
legitimate not to
We cannot change Qt in a way that breaks existing applications. Qt5 has
not exactly just been released, and commercial customers value stability
very much. Some of them even pay for Qt licenses, which is good for all
Qt users, so really, we should not make things worse for them.
--
You received
(In reply to Andreas Hartmetz from comment #29)
> We cannot change Qt in a way that breaks existing applications. Qt5 has not
> exactly just been released, and commercial customers value stability very
> much. Some of them even pay for Qt licenses, which is good for all Qt users,
> so really, we
How exactly did you try the kwrite crashing workaround? Just by sending a
zombie closeEvent?
Do you still have a backtrace?
(Let's say it's legit for a leaf widget to assume that the close event
it doesn't ignore() will cause a close with all implications on future
user interaction, data
(In reply to Alexey Chernov from comment #23)
> Comments like this clearly don't help
Seriously, you asked for breaking clients because that's what you'd "like" to
do - what did you expect to hear? That's simply not an acceptable stance.
> Never mentioned minor update or particular version.
(In reply to Alexey Chernov from comment #25)
> According to what?
According to "This is not fixed in years and each and every session management
code was ported as "#if 0""
If there was some relevant interest, it would be fixed long time, since it's
really not that hard.
> > Loosing your data
For a KMainWindow solution, one should not require a nasty global
eventfilter on the application - handling KMainWindow::closeEvent()
should be sufficient, but there might be an additional pitfall on modal
windows (ie. if there's already a save dialog, we might have to
forcefully activate that to
> 5. I completely don't like the proposed way to preserve the compatibility
> with (4) and make
> the use case of broken session management client implementation legal and
> default, but
> also try to allow proper-written apps to still survive somehow, adding some
> strange
> workarounds to
(In reply to Thomas Lübking from comment #24)
> (In reply to Alexey Chernov from comment #23)
>
> > Comments like this clearly don't help
> Seriously, you asked for breaking clients because that's what you'd "like"
> to do - what did you expect to hear? That's simply not an acceptable stance.
No
Yes indeed, it doesn't work because ignoring close events cancels
logout. Damn.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
** Changed in: qtbase-opensource-src (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does
(In reply to Andreas Hartmetz from comment #18)
> How should that be done, sending close events and expecting applications to
> save their state in response, but not close windows or the application?
QCloseEvent ce;
QApplication::sendEvent(window, );
You only want to emit the event, the widget
** Changed in: kdebase-workspace
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not
reported ;-) https://bugreports.qt.io/browse/QTBUG-49939
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support session
(In reply to Thomas Lübking from comment #13)
> Andreas, the Qt patch kills the ability to cancel the logout process (when
> the process or user prevents closing a window), I'm not sure it will be
> accepted and if, you probably will have caused a feature breakage. See
> comment #8. Instead of
In reply to comment 7: Yes, that looks like a working monkey patch :)
I'm trying to get this https://codereview.qt-project.org/#/c/142232/ merged to
fix the bug properly. I'm also looking at a preliminary fix in ksmserver, but
I'm not sure if I understand sub-session support, and on a related
The typical fail will be the "there are 5 tabs open, close/cancel"
dialogs.
Afaiu this was added because of some MS Windows behavior and even if
not, one has to assume that clients simply rely on window "save your
work first!" protection to be in place and not somewhen been killed by
the SM (what
How should that be done, sending close events and expecting applications to
save their state in response, but not close windows or the application? It
would mean that applications are session management aware but don't use the
session management API and implement a very crude version of session
Yes, my concern is that status quo for several/many applications is that
they do no connect to saveStateRequest() or commitDataRequest() and
*only* perform interaction on window close events (since this is the
regular case *during* the session)
Stripping this mechanism will cause a behavioral
Note: sub-session support in the session manager is basically support
for activities. Session restore of activities has never worked well
enough to be useful for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The session manager getting an OK means asking the client and at this
point the client can cancel the shutdown, or save its state and wait to
get killed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src
Hi Andreas,
Thanks for your patch! I do not have Qt developer's account, so I could not +1
for your great job.
Hope Qt5.x will integrate your patch to fix the restore session relative issue.
About ksmserver session management improvement, as you said make it
robust
Andreas, the Qt patch kills the ability to cancel the logout process
(when the process or user prevents closing a window), I'm not sure it
will be accepted and if, you probably will have caused a feature
breakage. See comment #8. Instead of actually closing, the system likely
wants to ask whether
** Changed in: kdebase-workspace
Status: Unknown => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support
Launchpad has imported 9 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=354724.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Bug watch added: KDE Bug Tracking System #354724
https://bugs.kde.org/show_bug.cgi?id=354724
** Changed in: kdebase-workspace
Importance: Low => Unknown
** Changed in: kdebase-workspace
Status: Fix Released => Unknown
** Changed in: kdebase-workspace
Remote watch: KDE Bug
This bug is marked as "RESOLVED FIXED" whereas with plasma 5.4.3 and Qt
5.4.2 in Kubuntu 15.10 no application is restarted on login.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
KWin is not responsible for restarting applications.
This bug was *only* about not restoring window manager attributes (position,
virtual desktop, etc.) on session restorage.
There're fundamental bugs in Qt5 that prevent (both, correct and entire)
restoring of Qt5 applications, see
*
Here is a very helpful comment from Thomas Lübking from kde-bugs
#341930:
KWin is not responsible for restarting applications.
This bug was *only* about not restoring window manager attributes (position,
virtual desktop, etc.) on session restorage.
There're fundamental bugs in Qt5 that prevent
Let's wait for the latter patch to be approved and merged, and I can
then cherry-pick it later.
The former patch is already part of the Qt 5.5.1 packages that will land
soon to xenial.
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)
--
72 matches
Mail list logo
