Gnome shell extensions disabled at every startup

Bug #1236749 reported by David Da Silva on 2013-10-08
754
This bug affects 167 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
Low
Unassigned
gnome-shell (Ubuntu)
Low
Unassigned
upstart (Ubuntu)
Low
Unassigned

Bug Description

Since gnome-shell 3.10, my extensions are disabled by default at every boot.
I need to launch Tweak Tool to enable theme by hand every time.

Both pre-installed extensions ( AlternateTab) and user-installed ones (top-icons)

Step to reproduce :
Enable an extension in Tweak Tool ( Alternate Tab for example)
reboot computer,
open Tweak Tool : Alternate tab is disabled.

Running on Ubuntu 13.10
GNOME Shell 3.10.0.1
gnome-tweak-tool 3.10..0-0ubuntu1-saucy1

C.Robinson (panacier) wrote :

I would like to confirm this as a bug as I have experienced the same problem on every version of gnome-shell 3.10 I have tried on ubuntu-GNOME, with anywhere from one to all three ( staging/testing/next) ppa enabled.

Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Daniel Cannon (webbed) wrote :

I can confirm this also using Ubuntu Suacy and the Gnome 3 staging/next ppas.

Have tested toggling the extensions through the Gnome Tweak Tool and the Gnome Extensions website.

This only happens on a full reboot, if you log out and back in as your user the extensions will remain enabled.

Linuxsusefan (linuxsusefan) wrote :

I can confirm same problem here.

My system: Ubuntu-GNOME 13.10 (32bit in vmwareplayer) - PPAs: gnome3 → staging & next,

My system is currently. Various extensions have been tested, always with the same result, after a "reboot" all extensions are disabled.

Jose Manuel Perdomo (joz3) wrote :

I have the same error (ubuntu 13.10 RC upgrade from 13.04 x64), I found a temporary solution (http://askubuntu.com/questions/352875/how-can-i-enable-all-installed-gnome-shell-extensions), but hopefully soon find a definitive solution ...

Sergio Souza (i-sergio-m) wrote :

I confirm the problem. Using the extensions installed via apt or using extensions get of extensions.gnome.org the problem happens.

My system: Ubuntu Gnome 13.10 64 bit (3.11.0-12-generic #19-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux), PPA Gnome 3 Team Staging and Next.

Nury Farelo (nuryfv) wrote :

I have the same problem, Ubuntu 13.10 Gnome 3.10.

Gorgonilla (lviggiani) wrote :

Same problem here. Everithing has been working fine until today when I started having the issue.

Dale C. Miller (zoelavie) wrote :

I have the same issue - Gnome 3.10.1, Ubuntu 13.10, using staging and next ppa's.

mimbel (y-fathi) wrote :

I have the same issue dualboot ubuntu 13.10/ ubuntu Gnome 13.10 and shared partition home

C.Robinson (panacier) wrote :

I hope this will help in resolving this issue - at lease for some. There are three possible login entries in the session menu accessible via cog to the left of the login button. Set option to "system default" instead of "gnome or classic" , extensions should now stay enabled after reboot. This has worked for me on two recent installs, including one I did earlier on today on which I am currentlly making this post. Good luck......

Gorgonilla (lviggiani) wrote :

@C,Robinson: your suggestion worked for me, thanks!

mimbel (y-fathi) wrote :

D'nt work with me

bhatta (bhattacharya-abhishek) wrote :

Same issue with Ubuntu Gnome 13.10, Gnome 3.10 here. Have to try out C.Robinson(panacier)' solution and see what happens.

Marking it as affecting me.
Also, Gnome Tweak Tool crashes randomly on startup, already reported !

bhatta (bhattacharya-abhishek) wrote :

@C.Robinson, so far your workaround works fine for me ! Thanks for the tip !

Ozgur Kucuktekin (ozgurktekin) wrote :

I have the same problem, Ubuntu 13.10 Gnome 3.10.

gutigen (gutigen) wrote :

Same issue in Ubuntu Gnome 13.10 with Gnome 3.10, C.Robinson workaround doesn't solve it.

ANOOP (anooparssss) wrote :

I also have the same problem , using ubuntu 13.10 64 bit(using staging and next ppa's)
selecting "system default" in gdm doesn't do anything.it just freezes .

sined (sinedooo) wrote :

I have the same problem, Ubuntu 13.10 + Gnome Shell 3.10(using staging and next ppa's).

Jarosław Guza (jarekj83-4) wrote :

i have got the same problem
Ubuntu 13.10, Gnome-Shell 3.10, after reboot all extensions are off

Same issue, Ubuntu 13.10 + Gnome 3.10 (32 bits) and staging and next ppa's. And I have never installed top-icons...

Rick Opper (brainstormtrooper) wrote :

OK.... I had the same problem (in OpenSUSE after updating to 13.1 w/ gnome 3.10), but I found what caused it for me and it may be the same for others.

I had non-existent extensions set as activated in dconf. This was because openSUSE used to ship with Alternate-status-menu (for Suspend, etc...) installed by default. It stayed in dconf and contaminated it.

Here's what to do:

1) in dconf - clear the enabled extensions key (or gsettings set org.gnome.shell enabled-extensions '[]')

MAKE SURE THE ENABLED EXTENSIONS ARE ACTUALLY INSTALLED

2) log out and back in (to clean up)
3)in tweak tool, re-enable the extensions.

They should stay enabled now - have for me ;-)

Hope this helps.

gutigen (gutigen) wrote :

@Rick Opper:

Doesn't solve the issue :/

Robinson workaround (comment 12) solved my problem.
Ubuntu Gnome 13.10
Gnome Shell 3.10.1

Nazar Mokrynskyi (nazar-pc) wrote :

Workaround doesn't work
Ubuntu 13.10
Gnome-shell 3.10.1

Please, fix this, I'm tired to re-enable all extensions after reboot and screen locking.

Weird, that they become disabled sometimes, not always. But I didn't found pattern of this behavior.

Grzegorz G. (grzesiek1e5) wrote :

I have this problem too, but not at every startup. It only happens sometimes. Also gnome-tweak-tool often crashes (similar to comment #15 ) and sometimes screen locking behaves weird (see attachment) - I can take a screenshot and it lands in my Images folder, but I can't alt-tab, or anything like this. I have to ctrl+alt+F6, login and run

DISPLAY=:0 gnome-shell --replace

, but sometimes even this doesn't work. Some data:

Ubuntu 13.10

$ gnome-shell --version
GNOME Shell 3.8.4

$ gsettings get org.gnome.shell enabled-extensions
['<email address hidden>', '<email address hidden>', 'Applications_Overview_Tooltip@Tornado', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', 'nvidiatemp@baco', '<email address hidden>', '<email address hidden>', '<email address hidden>', 'Windows_Overview_Tooltips@Tornado', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>']

BTW Windows Overview Tooltips isn't shown on https://extensions.gnome.org/local/ . I'll disable it and try other workarounds mentioned here.

Loric (loric-brevet) wrote :

I have the same problem too. Hope it will be fixed soon.

By the way until that I implemented a solution script in python.

[https://github.com/loric-/enableGnomeExtensions.py][1]

  [1]: https://github.com/loric-/enableGnomeExtensions.py

Grzegorz G. (grzesiek1e5) wrote :

(My original comment was #27 )
Disabling only Windows Overview Tooltips didn't seem to work, but disabling appindicatorsupport extension too seems to help.

jnns (jnns) wrote :

Could anyone of the devs chime in and tell whether there's additional info needed to fix this issue? It's becoming a nuisance although it's only a minor issue and probably easy to fix.

Blaster (holst-niels) wrote :

Also affected by this. Clean install of Gnome-Ubuntu and shell upgraded to 3.10.

My other identical machine running a clean install of Ubuntu 13.10, added Gnome Shell 3.8 and then upgraded to Shell 3.10 is not affected by this.

Any help would be appreciated.

Blaster (holst-niels) wrote :

Edit: It's definitely GDM-related.

I fixed it by installing a KDE desktop, logging into that once, logging into Gnome again, and rebooting.
Confirmed by rebooting 10 times, and extensions are now persistent.

Somebody with inside knowledge about GDM file permissions should probably be assigned this damn bug.

Noah Stewart (noah13013) wrote :

Solution #12 didn't work for me at all.

I didn't understand #23. I didn't feel like deciphering the answer since the following response claims it didn't work.

Similar to #31, I have another PC of different specs that never has this problem.

Solution #28 for the win! Nice solution.

Gregor Giesen (grgi) wrote :

I found the following odd behaviour: If I do the reboot after (!) logging out (e.g. from the GDM menu), then my extensions will be still activated afterwards. This is a somehow cumbersome workaround and sometimes I forget to do this extra step.
It looks like a direct reboot does not do a clean shutdown of the GNOME session.

granjerox (granjerox) wrote :

Same Problem here:
           - Ubuntu Gnome 3.10
           - Enabled ppas:
                      gnome3-team-gnome3-staging-saucy
                      gnome3-team-gnome3-saucy
                      gnome3-team-gnome3-next-saucy
           - Versions:
                      gnome-shell 3.10.2.1-0ubuntu1~saucy1
                      gdm 3.10.0.1-0ubuntu1~saucy4

- Workarround #12 did the trick, extensions remained enabled after gdm restart.

I want also to point that session logout didn't work until changing gdm to "system default".

pst007x (turone) wrote :

Sam issue here:

Ubuntu 13.10 64-bit
GeForce GTX 580M/PCIe/SSE2
Intel® Core™ i7-2860QM CPU @ 2.50GHz × 8

I find that the issue is definitely intermittent, and what is strange logging out and back in brings the extensions back.

Perhaps it has something to do with timings, or a loading sequence?

Is there a way I can force Gnome to load extensions using a script?

pst007x (turone) wrote :

Additional:

Try disabling all of your extensions and booting up with one enabled at a time. I found that an Extension called TASKBAR, which was set to create a second bar at the bottom of the screen caused all extensions to intermittently not start on boot up.

Perhaps some of the issues here could be to do with the way Gnome is handling some extensions, causing them to crash?

Tim (darkxst) on 2014-02-05
Changed in ubuntu-gnome:
milestone: none → trusty
status: New → Confirmed
Tim (darkxst) wrote :

The general reason that gnome-shell will disable all extensions, is when a buggy extension crashes gnome-shell. This is done as a fail-safe, to ensure you are able to restart gnome-shell.

Please can those affected try the following:
- disable all extensions
- enable only one of the official extensions from gnome-shell-extensions package
- try to reproduce the issue, if it happens attach ~/.cache/upstart/gnome-session.log to this bug
- if the above works, re-enable all your extensions, reproduce issue then attach above log

Changed in gnome-shell (Ubuntu):
importance: Undecided → Low
Changed in ubuntu-gnome:
importance: Undecided → Low
Pietrek B. (ptrbrzozowski) wrote :

I did what tim wrote in #38 and still no go. I disabled each extension except for "Places status Indicator", logged out, logged back in - it was fine. Rebooted the system - the extension was removed. Attaching gnome-session.log.

Running 13.10 with gnome3 and gnome-staging PPAs.

Pietrek B. (ptrbrzozowski) wrote :

I also notied that this is what I get after a reboot : gsettings get org.gnome.shell enabled-extensions
@as [] - that's from terminal of course.

Blaster (holst-niels) wrote :

Same as Pietrek B #39

gnome-session[3692]: WARNING: App 'gnome-shell.desktop' exited with code 1
gnome-session[3692]: WARNING: App 'gnome-shell.desktop' respawning too quickly
gnome-session[3692]: WARNING: Could not get session class: No such file or directory
gnome-session[3692]: CRITICAL: We failed, but the fail whale is dead. Sorry....

Was also running 13.10 with gnome3 and gnome-staging PPAs. Now I'm back to my stable Gnome Shell 3.8.4

I really don't think this is caused by a buggy extension as Tim states in #38.

My bet is on GDM and/or some weird timing issue.

Evian De la Torre (jael-1308) wrote :

Testing

extensions on:

Top Icons, Task bar, Coverflow Alt-tab, Drop Down terminal, frippery move clock, places status indicator, and others

In Ubuntu 13.10, Gnome 3.10.1

the solution is in comment # 12

Pietrek B. (ptrbrzozowski) wrote :

Workaround in #12 doesn't work for me. X server respawns right after I type my password and press enter if I choose "System default" as my session in GDM.

Jason Stoops (stoopsj) wrote :

Workaround in #12 fixed this issue for me. UbuntuGnome 13.10, Gnome 3.10.1.

Llyo (innerdust) wrote :

Use this trick :

Set all the extensions you want to be on. Then run:
gsettings get org.gnome.shell enabled-extensions

This should come up with something like
[wilf@whm ~]$ gsettings get org.gnome.shell enabled-extensions
['<email address hidden>', '<email address hidden>', '<email address hidden>']

Copy the output, and then run gnome-session-properties

Press add, and then enter the output of gsettings get org.gnome.shell enabled-extensions "['use... ...blogspot.com']" - PUT THE DOUBLE QUOTES IN, OTHERWISE THIS WILL NOT WORK (If not sure, test the command in the terminal first - if no feedback is give, it worked).

Workaround in #12 did'nt work for me...When I login to system settings I can just see my desktop wallpaper. Mouse pointer is invisible though it works. As I can see icon selected as I move the mouse around. Launcher is too gone.Only GNOME helps

Blaster (holst-niels) wrote :

#46: Are you running LightDM or GDM?

thrantir (thrantir) wrote :

#12 workaround works for me

Piotr Cichocki (ciiichy) wrote :

I have got the same problem.
Install Ubuntu Gnome (http://ubuntugnome.org/) solved this problem.

jnns (jnns) wrote :

GNOME Shell 3.11.92 exhibits this problem as well.
I installed 3.11.92-0ubuntu1~trusty2 from http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/.

Tim (darkxst) on 2014-04-11
Changed in ubuntu-gnome:
milestone: trusty → trusty.1

I can confirm it still fails on Ubuntu GNOME 14.04 and that workarounds #12 and #34 worked for me.

Ubuntu 14.04, GDM and gnome 3.12.1 from the gnome-staging PPA.

Also confirming that the workaround from comment #12 resolves this for me. I have selected the System Default session from the gear beside the Login button in GDM.

Dickson Owuor (dickytea2007) wrote :

Ubuntu 14.04, GDM and gnome 3.12.2 from the gnome-staging PPA.

Also confirming this issue but the workaround from comment #12 resolves this for me too.

Sergey Zolotarev (szx) wrote :

How do you make GNOME the System Default session in GDM? It just shows a blank gray screen for me...

DeadVirus (amfcosta13) wrote :

For me, the System Default also only shows a grey screen. I had unity installed before, that's probably because of it.

Filipe Sizilio (filipesizilio) wrote :

Confirming this issue but the workaround from comment #12 resolves this for me too.

DeadVirus (amfcosta13) wrote :

For those who won't get a desktop environment when selecting the "System Default", try the following on a terminal and reboot: gsettings set org.gnome.desktop.session session-name 'gnome'

After that, selecting System Default works and solves this bug.

Eslam (eslam-husseiny) wrote :

Confirming this issue too.
Ubuntu version : 14.04.1 LTS
gnome-shell version : 3.12.2

And the workaound of comment #12 works fine for me :)

Thanks

WindWalker (elwindwalker) wrote :

Confirm this issue.
Fixed with comment #12.

MeduZa (meduzapat) wrote :

Confirm this issue.
Fixed with comment #12.

Stephen Brightwood (brightws) wrote :

Running Ubuntu 14.10 and Gnome 3.14 from Gnome3 PPA. This is still a persistent error and has effected me for about a year now. previously I used the workaround where the extensions were loaded at startup using gsettings - but this is now not available in the latest release so it has stopped working for me. The "default logging" has no effect and clearing out the extensions folders before re-enabling a small subset doesn't work either.
This is the result of gsettings enabled-extensions:

['<email address hidden>', '<email address hidden>', '<email address hidden>', 'transparentwindows@ellen', '<email address hidden>', '<email address hidden>']

This is after I have specifically removed transparent window and gradio in dconf.

It seems that there are multiple places where these settings are stored and they are probably conflicting.

Its really annoying that this error is effecting so many people and is persistent for over a year at this stage. Its enough to drive you towards KDE. Can we get this sorted before it destroys the credibility of the Gnome project.

peter mutch (peter2mutch) wrote :

Combining #57 and #12 worked for me, after a mere 3 hours of fiddling.

I had tried manually editing the pages for xsessions, gdm, gnome-session, xinit, startx, etc with no success. This is the only workaround that worked for me.

Ubuntu 14.04 with Gnome 3.12

dale f (manzanitalaceration) wrote :

Combining #57 and #12 did NOT work for me UbuntuGnome 14.04 with Gnome 3.12

dale f (manzanitalaceration) wrote :

On subsequent reboots the fix of combining #57 and #12 DID work for me (UbuntuGnome 14.04 with Gnome 3.12). So reboot a couple of times...but the problem was always sporadic. I will report back here if the problem reappears.

Georg Peters (georgpeters) wrote :

Combining #57 and #12 did work - ubuntu Gnome 14.10 with gnome 3.12.2

doylep (doylep) wrote :

I experienced this problem on Ubuntu 14.10 with Gnome 3.12.2 when I upgraded from the Ubuntu packaged version of gnome to the gnome3-team version. Two other issues arose as well: gnome-terminal its lost profile settings and crashed when I tried to edit them, and the gdm login screen did not display any usernames. Maybe the dconf settings have become inconsistent across the two sources of gnome packages.

Comment #23 (resetting dconf) solved my problem.

On 26/10/14 13:56, Patton Doyle wrote:
> Two other issues arose as well: gnome-terminal its lost profile
> settings and crashed when I tried to edit them, and the gdm login screen
> did not display any usernames. Maybe the dconf settings have become
> inconsistent across the two sources of gnome packages.
>
Please file other issues under new bugs.

Tim (darkxst) wrote :

Bug 1385572, tracks the underlying issue that is causing extensions to get disabled

Launchpad Janitor (janitor) wrote :

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

Changed in upstart (Ubuntu):
status: New → Confirmed
molecule-eye (niburu1) wrote :

You can prevent resetting of enabled-extensions by logging out first before shutting down (and then e.g. shutting down from the login screen). This workaround came about by reading Bug 1385572.

demius (anonymoususertj) wrote :

#12 worked for me (running ubuntu-gnome 14.04 with gnome 3.12)

Matthew Harrison (mpharrison) wrote :

I had this with 14.10 (Unity edition with Gnome 3.14 from ppa:gnome3-team/gnome3-staging installed)

Fix from Comment #57 worked, except I used Dconf Editor to set the value.

Spyros (pipis-nm) wrote :

I tried Comments #12 and #57 but they didnt work . Can we add this extensions to startup applications ? Unfortunately i cant use startup on tweak tool because it doesnt work (i think it must be broken).

Ubuntu 14.10
Gnome 3.14

Spyros (pipis-nm) wrote :

Finally Comment #12 worked fine for me !

tags: added: trusty
tags: added: utopic
Changed in upstart (Ubuntu):
importance: Undecided → Low
matyas (albertmatyi) wrote :

Thank you @Rick ! Comment #12 worked like a charm on gnome 3.14

Important part:
gsettings set org.gnome.shell enabled-extensions '[]'

Only had to restart shell via: Alt+F2 / r / Enter

tags: added: vivid

Comment #12 works for me.

Ubuntu 14.10
Gnome-shell 3.14.3

The problem with this bug is that it doesn't exhibit itself consistently or predictably.

On my previous laptop's Ubuntu GNOME 14.10 setup, reboots worked fine until some point (a month after installing?), at which point this behavior started happening... but only on a clean reboot. If I killed power to my laptop by force instead, extensions would stay. (This probably further confirms the hypothesis in bug 1385572.) The previous laptop was a Dell Precision M6400 with a Core 2 Duo CPU and Quadro FX 2700M graphics. I forget if I tried nVidia drivers or not.

So far, I have not seen this happen with clean reboots on my current laptop. It is a Lenovo G60-45 with the following combined CPU/GPU: "AMD A6-6310 APU with AMD Radeon R4 Graphics". I mainly use the AMD drivers due to freezing issues with mesa; I forget if this happened with mesa as well or not. This is still with Ubuntu GNOME 14.10.

Rafal (rjtskolasinski) wrote :

I confirm the issue.

Solution #12 works for me.

Tim (darkxst) wrote :

I uploaded a gnome-session update that hopefully fixes this to ppa:darkxst/ppa. Please test, if it works, will get the fix into trusty and utopic.

Brian Visel (eode) wrote :

I'm using gnome staging (3.14), so the PPA doesn't help with me personally, but thank you for your work! I hope it solves the issue for others.

In the meantime, since the issue is caused by the faulty reboot/shutdown without closing out the session completely, I did this:

* Install Suspend Button extension, and configure it to replace the reboot option with suspend (keeps me from accidentally rebooting)
* When I need to reboot/shutdown, I log out instead, then reboot/shutdown from GDM/Login Screen

Tim (darkxst) on 2015-03-11
Changed in ubuntu-gnome:
milestone: trusty.1 → trusty.3
Tim (darkxst) wrote :

Brian the vivid package from that ppa should most likely work on 14.10 with gnome-staging enabled, if you want to test it

Hello David, or anyone else affected,

Accepted gnome-session into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-session/3.9.90-0ubuntu16.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-needed
Brian Murray (brian-murray) wrote :

Hello David, or anyone else affected,

Accepted gnome-session into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-session/3.9.90-0ubuntu12.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

just change the session to system default and the problem goes away! it worked for me

rolly (aureliano-cabiddu) wrote :

I confirm, comment #12 works for me too.

Ubuntu 14.04.2
Gnome-shell 3.12.2

P.S.: it needs to reboot two times to working.

madivak (madivak) wrote :

#12 works for me... Ubuntu 14.04 LTS , gnome-shell 3.10

Andreas Ritter (eddie8) wrote :

Ubuntu 15.10, default gnome.
Also affected sometimes: The last month, only about once a week, for now since a few days on every startup.

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

Other bug subscribers