Just installed F22 using fedup from F21. See the Users list for a couple of general comments. Regarding KDE:
1) The Plasma session restore bug is still present.
2) SDDM is still broken (no gnome-key support) so I use KDM. Luckily it still works on F22.
3) I get a crash report on each login from kf5-kactivities. I have no use for Activies in Plasma but the package can't be removed because of Plasma dependencies.
poc
Patrick O'Callaghan wrote:
Just installed F22 using fedup from F21. See the Users list for a couple of general comments. Regarding KDE:
- The Plasma session restore bug is still present.
Progress is happening, looks like we finally have a set of patches (4 so far) that successfully saves session.
Work is continuing to get that saved session to restore properly.
-- Rex
On Tue, 2015-05-26 at 18:40 -0500, Rex Dieter wrote:
Patrick O'Callaghan wrote:
Just installed F22 using fedup from F21. See the Users list for a couple of general comments. Regarding KDE:
- The Plasma session restore bug is still present.
Progress is happening, looks like we finally have a set of patches (4 so far) that successfully saves session.
Work is continuing to get that saved session to restore properly.
Thanks Rex. Can't happen too soon.
poc
On 05/27/15 18:32, Patrick O'Callaghan wrote:
On Tue, 2015-05-26 at 18:40 -0500, Rex Dieter wrote:
Patrick O'Callaghan wrote:
Just installed F22 using fedup from F21. See the Users list for a couple of general comments. Regarding KDE:
- The Plasma session restore bug is still present.
Progress is happening, looks like we finally have a set of patches (4 so far) that successfully saves session.
Work is continuing to get that saved session to restore properly.
Thanks Rex. Can't happen too soon.
Yes, thanks Rex....
Wonder when the patches will hit updates-testing. :-) :-)
On 05/26/2015 06:40 PM, Rex Dieter wrote:
Patrick O'Callaghan wrote:
Just installed F22 using fedup from F21. See the Users list for a couple of general comments. Regarding KDE:
- The Plasma session restore bug is still present.
Progress is happening, looks like we finally have a set of patches (4 so far) that successfully saves session.
Work is continuing to get that saved session to restore properly.
This is great news. I'm curious about the code and would like to have a look at it. Where can I find it?
Glenn Holmer wrote:
On 05/26/2015 06:40 PM, Rex Dieter wrote:
Patrick O'Callaghan wrote:
Just installed F22 using fedup from F21. See the Users list for a couple of general comments. Regarding KDE:
- The Plasma session restore bug is still present.
Progress is happening, looks like we finally have a set of patches (4 so far) that successfully saves session.
Work is continuing to get that saved session to restore properly.
This is great news. I'm curious about the code and would like to have a look at it. Where can I find it?
There's pieces of the equation all over, patches we're carrying so far:
kf5-kconfig https://git.reviewboard.kde.org/r/123705/ ----------- http://pkgs.fedoraproject.org/cgit/kf5-kconfig.git/tree/0001-Add-KConfigGui-... http://pkgs.fedoraproject.org/cgit/kf5-kconfig.git/tree/0003-fix-missing-exp...
kf5-kxmlgui: https://git.reviewboard.kde.org/r/123706 ----------- http://pkgs.fedoraproject.org/cgit/kf5-kxmlgui.git/tree/0001-Add-session-man...
The kf5 ones are in f22 stable updates already, the ones below are not... yet
kwin: https://git.reviewboard.kde.org/r/123580 http://pkgs.fedoraproject.org/cgit/kwin.git/tree/kwin-session_management_rev...
qt5-qtbase: https://bugreports.qt.io/browse/QTBUG-45484 ----------- http://pkgs.fedoraproject.org/cgit/qt5-qtbase.git/tree/qtbase-opensource-src...
qt5-qtbase: https://bugreports.qt.io/browse/QTBUG-46310 ----------- http://pkgs.fedoraproject.org/cgit/qt5-qtbase.git/tree/0002-xcb-set-SM_CLIEN...
On 05/26/2015 06:40 PM, Rex Dieter wrote:
Patrick O'Callaghan wrote:
- The Plasma session restore bug is still present.
Progress is happening, looks like we finally have a set of patches (4 so far) that successfully saves session.
Work is continuing to get that saved session to restore properly.
This works for me now! Since I use specific desktops for different purposes (e.g. email on desktop 7), I am overjoyed to see it working again. This was my single biggest problem with Plasma 5.
Can anybody else verify? I tried it on three machines.
On Sun, 2015-07-05 at 11:48 -0500, Glenn Holmer wrote:
On 05/26/2015 06:40 PM, Rex Dieter wrote:
Patrick O'Callaghan wrote:
- The Plasma session restore bug is still present.
Progress is happening, looks like we finally have a set of patches (4 so far) that successfully saves session.
Work is continuing to get that saved session to restore properly.
This works for me now! Since I use specific desktops for different purposes (e.g. email on desktop 7), I am overjoyed to see it working again. This was my single biggest problem with Plasma 5.
Can anybody else verify? I tried it on three machines.
As I said in another thread, it appears to work for KDE apps. Firefox runs but seems to have a bug. No news on Chrome, which flat out doesn't work.
poc
On 07/06/15 04:48, Patrick O'Callaghan wrote:
As I said in another thread, it appears to work for KDE apps. Firefox runs but seems to have a bug. No news on Chrome, which flat out doesn't work.
I don't know what you mean by "flat out doesn't work", but I have Chrome working just fine on several systems that were installed from scratch and 2 systems that were upgraded via fedup.
Even in KDE4 I always made sure I quite Chrome before logout since it was a roll of the dice for it to restore the tabs I had open/pinned.
On Mon, 2015-07-06 at 05:02 +0800, Ed Greshko wrote:
On 07/06/15 04:48, Patrick O'Callaghan wrote:
As I said in another thread, it appears to work for KDE apps. Firefox runs but seems to have a bug. No news on Chrome, which flat out doesn't work.
I don't know what you mean by "flat out doesn't work", but I have Chrome working just fine on several systems that were installed from scratch and 2 systems that were upgraded via fedup.
I mean that when I log out and in again, Chrome does not restart. If I restart it manually, it restores all the tabs and windows I've defined in my manually saved session (just not on the correct desktops). Actually that's not completely true. There is one tab that is always restored even though I've saved the session without it. No idea what's going on there, though it could be a Chrome bug.
Even in KDE4 I always made sure I quite Chrome before logout since it was a roll of the dice for it to restore the tabs I had open/pinned.
I never had to do that. IIRC Chrome would always restore just as I left it.
poc
On 07/06/15 05:15, Patrick O'Callaghan wrote:
On Mon, 2015-07-06 at 05:02 +0800, Ed Greshko wrote:
On 07/06/15 04:48, Patrick O'Callaghan wrote:
As I said in another thread, it appears to work for KDE apps. Firefox runs but seems to have a bug. No news on Chrome, which flat out doesn't work.
I don't know what you mean by "flat out doesn't work", but I have Chrome working just fine on several systems that were installed from scratch and 2 systems that were upgraded via fedup.
I mean that when I log out and in again, Chrome does not restart. If I restart it manually, it restores all the tabs and windows I've defined in my manually saved session (just not on the correct desktops). Actually that's not completely true. There is one tab that is always restored even though I've saved the session without it. No idea what's going on there, though it could be a Chrome bug.
After you logout, either login as a different user or ssh into the system and check to see if any Chrome processes remain running.
FWIW, I think most of the problem with Chrome and restarts are probably Chrome issues...which is why I manually shut it down and start it up.
Even in KDE4 I always made sure I quite Chrome before logout since it was a roll of the dice for it to restore the tabs I had open/pinned.
I never had to do that. IIRC Chrome would always restore just as I left it.
Yes, YMMV. I've had no such luck as I've said.
On Mon, 2015-07-06 at 05:23 +0800, Ed Greshko wrote:
I mean that when I log out and in again, Chrome does not restart.
If I
restart it manually, it restores all the tabs and windows I've
defined
in my manually saved session (just not on the correct desktops). Actually that's not completely true. There is one tab that is
always
restored even though I've saved the session without it. No idea
what's
going on there, though it could be a Chrome bug.
After you logout, either login as a different user or ssh into the system and check to see if any Chrome processes remain running.
Tried that. There are no Chrome processes left. Also, I nearly always end the session by rebooting because of updates (this is a home machine that is always logged in). What mystifies me is that it refuses to forget this one tab, even though I've saved the session with the tab closed. If I could figure out where Chrome saves its state I might be able to fix that. There is a file called .config/google-chrome/Local\ State but it doesn't look like they want you to edit it.
FWIW, I think most of the problem with Chrome and restarts are probably Chrome issues...which is why I manually shut it down and start it up.
Even in KDE4 I always made sure I quite Chrome before logout since
it
was a roll of the dice for it to restore the tabs I had
open/pinned.
I never had to do that. IIRC Chrome would always restore just as I
left
it.
Yes, YMMV. I've had no such luck as I've said.
Well, go figure.
poc
On Sun, 2015-07-05 at 23:40 +0200, Markus Slopianka wrote:
On Sunday 05 July 2015 21:48:01 Patrick O'Callaghan wrote:
No news on Chrome, which flat out doesn't work.
Chrome is not part of Fedora. Please direct complaints about Chrome at Google.
AFAIK apps are meant to save and restore state via the session manager in a standard way. If Chrome also fails on other DEs then I agree it's a Chrome issue. If not, then not necessarily.
poc
On 07/06/15 07:31, Patrick O'Callaghan wrote:
On Sun, 2015-07-05 at 23:40 +0200, Markus Slopianka wrote:
On Sunday 05 July 2015 21:48:01 Patrick O'Callaghan wrote:
No news on Chrome, which flat out doesn't work.
Chrome is not part of Fedora. Please direct complaints about Chrome at Google.
AFAIK apps are meant to save and restore state via the session manager in a standard way. If Chrome also fails on other DEs then I agree it's a Chrome issue. If not, then not necessarily.
Does that mean we'll now be waiting on your report as to how it performs in other DEs? :-) :-)
On Mon, 2015-07-06 at 07:35 +0800, Ed Greshko wrote:
On 07/06/15 07:31, Patrick O'Callaghan wrote:
On Sun, 2015-07-05 at 23:40 +0200, Markus Slopianka wrote:
On Sunday 05 July 2015 21:48:01 Patrick O'Callaghan wrote:
No news on Chrome, which flat out doesn't work.
Chrome is not part of Fedora. Please direct complaints about Chrome at Google.
AFAIK apps are meant to save and restore state via the session manager in a standard way. If Chrome also fails on other DEs then I agree it's a Chrome issue. If not, then not necessarily.
Does that mean we'll now be waiting on your report as to how it performs in other DEs? :-) :-)
It'll be a long wait. I did try it in Gnome but I'm unable to figure out how Gnome is supposed to be configured to save and restore sessions. Apparently there's something called gnome-session-properties but I can't find it anywhere, including with 'dnf search'.
poc
-
Ed Greshko -
Germano Massullo -
Glenn Holmer -
Markus Slopianka -
Patrick O'Callaghan -
Rex Dieter