Bug 1853664 - Cinnamon disconnection inadequate
Summary: Cinnamon disconnection inadequate
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 32
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1357426
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-03 13:45 UTC by xzj8b3
Modified: 2021-05-25 17:11 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-05-25 17:11:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description xzj8b3 2020-07-03 13:45:20 UTC
If you have installed Cinnamon in addition to Gnome shell when you end your Linux desktop session mint the user is not properly disconnected and going back to Gnome Shell seems to give problems to some extensions, for example:

https://extensions.gnome.org/extension/1230/gmail-message-tray/

which seems to be no longer able to detect messages until a reboot with subsequent Gnome -Shell...This is because Cinnamon doesn't seem to correctly disconnect the user if you switch from one desktop to the other!!!

Comment 1 leigh scott 2020-07-03 14:39:31 UTC
It isn't cinnamon's job to kill user processes, logind should do it.

Comment 2 xzj8b3 2020-07-05 13:19:35 UTC
Well I've reported what's happening, report it... I think it's useless to reopen another report!!!

Comment 3 Zbigniew Jędrzejewski-Szmek 2020-07-06 20:02:27 UTC
We would really love to. KillUserProcesses=yes is the setting that does this. Unfortunately, people
are against setting this this way. KillUserProcesses=yes would solve many issues like this
(e.g. with pulseaudio remaining after a crash and similar). See #1357426.

Comment 4 xzj8b3 2020-07-07 15:16:35 UTC
Yes of course but if the problem occurs during reboot one does not access the shell in time

You will be able to access and terminate it once you are aware of the problem, but I think that for it and new users some verification is necessary so that the problem does not recur because many often use secondary desktops!

Comment 5 Fedora Program Management 2021-04-29 16:48:41 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Ben Cotton 2021-05-25 17:11:14 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.