https://bugs.kde.org/show_bug.cgi?id=514571

            Bug ID: 514571
           Summary: Clean shutdown of Chrome on logout/shutdown - buggy
                    under Wayland
    Classification: Plasma
           Product: plasmashell
      Version First 6.5.4
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Startup process
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: 1.0

SUMMARY

There are numerous bugs both here and elsewhere that report how KDE and Google
Chrome do not behave nicely on logout. Particularly how on future sessions,
Chrome opens with no memory of previously opened tabs. Most of these suggest a
logout script (installed under KDE autostart) to kill Chrome prior to logout. I
had applied such a solution and found that while not perfect, it achieved what
was required. Since transitioning to Wayland, this script no longer functions,
and I am unable to guarantee a clean logout that will allow me to resume in
future sessions. Given how ubiquitous Chrome is, how long this issue has
existed, and the recent push to move to Wayland, this is becoming a bigger
issue

SCRIPT

I have the following script code set to run on logout:

#!/bin/bash

killall -INT chrome
sleep 2

OBSERVED RESULT UNDER X11

This is not a perfect solution, the script will kill all running instances of
Chrome, then wait two seconds to allow Chrome to write currently open tabs to
disk.

In a future plasma session, when I launch Chrome, it will report that Chrome
crashed and ask me if I wish to restore all previously open windows/tabs. If I
select yes, it will re-open all tabs I had from the previous session.

This is not perfect, I would prefer Chrome to just open without asking me, but
I can live with that "issue"

OBSERVED RESULT UNDER WAYLAND

Observed outcomes are random, I see one of three situations occurring with
roughly equal probability when I start Chrome in a future plasma wayland
session

a) The same as above, Chrome reported it crashed and asks me if I wish to
restore previously opened windows/tabs. I select yes and all is OK

b) Chrome reports that it crashed and asks me if I wish to restore previously
opened windows/tabs. I select yes and some of my previously opened windows/tabs
are restored, others are not. Furthermore, the remaining windows/tabs are NOT
in the Chrome history when trying to open previously closed tabs

c) Chrome reports no issues and starts with no windows/tabs open.  None of the
tabs from the previous sessions are saved in the history and cannot be
recovered/reopened from anywhere

These three occur with equal probability, issuing a manual "killall -9 chrome"
on the command line prior to logging out always works as per (a) above

WHAT I'VE TRIED

I've tried increasing the wait time in the sleep command to five seconds, this
has not changed the probability of any of the three outcomes occurring.

I've tried inserting a "kdialog" command after the sleep command to stop the
logout/shutdown process until I click "ok" on the dialog box, this has not
changed the probability of any of the three outcomes occurring 

EXPECTED RESULT

Behaviour of logout scripts under wayland only should not be this random.

Furthermore, this issue has been a bug for a long time. Is it not possible,
particularly given how common Chrome use is, to put a fix into KDE such that
Chrome is shutdown cleanly before logout, such that restarting in a future
session will automatically open all previously opened windows/tabs

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Linux 6.12.58
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to