GNOME extensions deactivated after lock unlock

Bug #1697229 reported by Francewhoa
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
gnome-session
New
Unknown
gnome-session (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Summary:
Lock then unlock GNOME session result in all GNOME extensions to be deactivated. Intermittent bug.

Steps to reproduce:
1. Install fresh Debian 8.8 Jessie

2. Using https://extensions.gnome.org install and activate all the following extensions:
https://extensions.gnome.org/extension/310/alt-tab-workspace/
<email address hidden> (version 10.0)

https://extensions.gnome.org/extension/484/workspace-grid/
<email address hidden> (version 18.0)

https://extensions.gnome.org/extension/495/topicons/
<email address hidden>@gmail.com (version 29.0)

https://extensions.gnome.org/extension/672/disable-screen-shield/
<email address hidden> (version 7.0)

https://extensions.gnome.org/extension/425/project-hamster-extension/
<email address hidden> (version 26.0)

https://extensions.gnome.org/extension/1082/cpufreq/
cpufreq@konkor (version 12.0)

3. Lock GNOME session

4. Unlock GNOME session. Notice that all extensions are now deactivated :( Expected result is that they should remaining activated per their configuration.

5. Using "Tweak Tool"/"gnome-tweak-tool" re-activate all those extensions. Restart GNOME by pressing "ALT-F2" keys, type "r", press "Enter" key. The extensions are now working.

6. Lock GNOME session again

7. Unlock GNOME session again. Issue is reproduced again. All extensions are deactivated. This bug is intermittent though. It depends on various factors, including but not limited:
• Which extensions are activated
• Your personal configuration with "gnome-tweak-tool" and "gnome-session" packages

8. This issue can also be reproduce with rebooting, instead of lock and unlock the session. Same steps to reproduce as above. But simply reboot.

Using
• Base system: Debian 8.8 Jessie, 64-bit
• Gnome: 3.14.1
• gnome-tweak-tool: 3.14.2-2
• gnome-session: 3.14.0-2
• gnome-session-bin: 3.14.0-2
• gnome-session-common: 3.14.0-2
• Kernel: 4.9.0-0.bpo.3-amd64 #1 SMP Debian 4.9.25-1~bpo8+1 (2017-05-19) x86_64 GNU/Linux

Notes:
This bug was fixed in the package gnome-session - 3.9.90-0ubuntu16.1 with that ticket comment #15 at https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1385572/comments/15
So that ticket #1385572 is closed. But somehow this bug is back and reported by others in tickets #1236749 and #1385572. Maybe a regression? Maybe a zombie-bug, LOL ;) Anyhow I'm reopening this bug with this new ticket #1697229.

I would be happy to contribute testing

Here is another related ticket which includes some temporary fixes, such as:
# 12 at https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1236749/comments/12
# 57 at https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1236749/comments/57

Francewhoa (francewhoa)
tags: added: amd64 jessie
description: updated
Francewhoa (francewhoa)
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Francewhoa (francewhoa) wrote :

After I created that ticket #1697229 I realized that this launchpad seems to be for Ubuntu. Since gnome-session is primarily maintain by bugs.debian.org it seems more appropriate to create this ticket with bugs.debian.org?
I created a ticket at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864592

Feel really free to use either ticket or both

Changed in gnome-session:
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-session (Ubuntu):
status: New → Confirmed
Revision history for this message
Dmitriy Geels (dmig) wrote :

Started experiencing this bug after Ubuntu update 18.04->18.10.

Revision history for this message
Nick Clay (nickdclay) wrote :

I've experienced possibly this bug intermittently since moving to Manjaro Gnome with Gnome 3.30.2. In my case it's not all the extensions that are reset, but two that I've set different to default: Places status indicator and Topicons plus. Furthermore, rebooting usually puts it right; it's the locking and unlocking that deactivates those extensions on my system.

Revision history for this message
tellapu (tellapu) wrote :

In Ubuntu 19.10 it still happens to me, after I logout and login again (I use Ubuntu Desktop not the Gnome desktop). Thanks for working on this.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.