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 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
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
Created attachment 96913
Fix session saving / KApplication changes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support session restoration
To manage
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
Created attachment 96914
Fix session saving / KMainWindow changes
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support session restoration
To
..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
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
KDE5/Qt5 does not support session restoration
To manage
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
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
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
Bugs, which is subscribed to Ubuntu.
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
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
Bugs, which is subscribed to Ubuntu.
(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
I have essentially the same problem when building a biarch gcc (my goal is to
compile i386 and amd64 on i386). I had a look into /usr/x86_64-linux-gnu/lib,
lib32, and lib64:
-lib32 contains 32-bit libraries
-lib64 contains 64-bit libraries
-lib contains 64-bit libraries as well, they seem to be
Note: So it looks more like a problem elsewhere in the cross build
toolchain than in gcc...
--
Error building powerpc64 cross compiler: 64 bit libc not found linking libgcc
https://bugs.launchpad.net/bugs/280681
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The situation is even more complicated: Apparently I had a screwed up
install of some cross packages. After reinstalling them lib is a symlink
to lib64... whatever. libc.so and libpthread.so in lib and consequently
lib64 are still linker scripts.
--
Error building powerpc64 cross compiler: 64
The linker is supposed to treat any input files that are not valid object files
as linker scripts. So either it fails to do that (its output looks like it) or,
much more likely, this *is* a simple case of looking into the wrong directory.
Even if the scripts were executed they'd point to the
Public bug reported:
Binary package hint: linux-image-2.6.17-11-generic
I have an nforce2 chipset. The system hangs during major disk activity like
updatedb running, i.e. the mouse cursor jumps and windows take seconds to
redraw sometimes.
On some message board it was suggested to disable the
22 matches
Mail list logo
