How do I reset GNOME to the defaults?

Clash Royale CLAN TAG#URR8PPP up vote
102
down vote
favorite
I was playing around with some settings, and now I need to reset GNOME to it's defaults - how do I do that?
gnome configuration
add a comment |Â
up vote
102
down vote
favorite
I was playing around with some settings, and now I need to reset GNOME to it's defaults - how do I do that?
gnome configuration
add a comment |Â
up vote
102
down vote
favorite
up vote
102
down vote
favorite
I was playing around with some settings, and now I need to reset GNOME to it's defaults - how do I do that?
gnome configuration
I was playing around with some settings, and now I need to reset GNOME to it's defaults - how do I do that?
gnome configuration
edited Nov 29 '11 at 14:02
asked Aug 8 '11 at 15:46
jrgâ¦
38.3k49146235
38.3k49146235
add a comment |Â
add a comment |Â
9 Answers
9
active
oldest
votes
up vote
126
down vote
accepted
For Unity-related configuration resetting, take a look here.
For Ubuntu 17.10 and higher, you can reset all the settings using dconf.
This command will delete your configuration files. Once it's run there is no going back!
Still with me?
GNOME2
Run the following in the terminal or Alt+F2:
rm -rf .gnome .gnome2 .gconf .gconfd .metacity
That will do is remove all the GNOME2 configuration settings. Log out, and log back in. You'll be back to a stock desktop.
You can backup before playing around with your settings in the future:
mkdir ./.old-gnome-config && mv ./.gnome* ./.old-gnome-config && mv .gconf* ./.old-gnome-config && mv ./.metacity ./.old-gnome-config
GNOME3
If your config isn't worth saving run the following:
rm -rf .gnome .gnome2 .gconf .gconfd .metacity .cache .dbus .dmrc .mission-control .thumbnails ~/.config/dconf/user ~.compiz*
To back up and reset GNOME3:
mkdir ./.old-gnome-config/ && mv ./.gnome* ./.old-gnome-config/ && mv .gconf* ./.old-gnome-config/ && mv ./.metacity ./.old-gnome-config/ && mv ./.cache ./.old-gnome-config/ && mv ./.dbus ./.old-gnome-config/ && mv ./.dmrc ./.old-gnome-config/ && mv ./.mission-control ./.old-gnome-config/ && mv ./.thumbnails ./.old-gnome-config/ && mv ~/.config/dconf/* ./.old-gnome-config/
10
more concise and precise to use a for loop for the backup step, e.g.for f in .gnome .gnome2 .gconf .gconfd .metacity; do mv $f $f.bak; doneormkdir -p ~/.backup-gnome-config/ && for f in .gnome .gnome2 .gconf .gconfd .metacity; do mv $f ~/.backup-gnome-config/; done
â hobs
Aug 13 '12 at 1:38
Shorten that last bit tomkdir ./.old-gnome-config/ && mv ./.gnome* .gconf* ./.metacity ./.cache ./.dbus ./.dmrc ./.mission-control ./.thumbnails ~/.config/dconf/* ./.old-gnome-config/
â smac89
Dec 22 '16 at 19:08
add a comment |Â
up vote
18
down vote
Fore me those directories were not sufficient - I had to delete ~/.config/dconf/user as well.
This helped for me in those two cases:
- gnome-panel config broken
(tried to specify location "left" for one gnome panel, it immediately crashed and could not be started afterwards) - GTK Theme and GTK Icons broken
(nevertheless the selection via e. g.gnome-tweak-tool, it remained in ugly Windows-style grey look and icons were standard gnome - I have no clue how this was provoked, it appeared suddenly after login)
This corresponds to the Gnome 3 Fallback Mode I use on Linux Mint 12 Lisa (Oneiric based). But the GTK problem persisted in all other login modes as well (MATE, Gnome 3 Standard)!
I am unsure now to which mechanism the ~/.config/dconf/user file corresponds, as I found out that in Linux Mint only _mateconf-editor_ is installed by default but outfitted with the title and icon of gconf-editor from Natty!
After installing gconf-editor additionally, this one is titled identically but has a different (new) icon. But don't rely on this icon stories, because this will rely on the icon theme which is Mint-X-Dark for me.
Theory says that dconf is the successor for gconf, but I found no information regarding the GUIs.
1
Yes, I had the same problem and needed to remove ~/.config/dconf aswell
â wim
Jan 4 '12 at 23:25
+1 for the info, but it'd be even better if you rewrite to incorporate your edits
â djeikyb
Jan 5 '12 at 22:23
This helped with the missing Lock Screen menu option (which is probably down to yet another corrupt dconf config)
â prusswan
Nov 30 '12 at 4:59
1
Saved my life! Spent the last two hours unable to load my Ubuntu desktop, but deleting ~/.config/dconf/user did the trick
â leopld
Jan 9 '15 at 14:52
This is weird, i have to delete this file after every reboot to avoid login loop.
â Ondra à ½ià ¾ka
May 4 at 16:33
 |Â
show 2 more comments
up vote
14
down vote
For 17.10+
There isn't a great solution but this may do the job or most of it.
dconf reset -f /org/gnome/
Then log out/in
That command's path could be shortened if needing a more extensive reset, i.e. to just /org/ or even / but I'd go with above first.
Worst case one could also just go this in a terminal, I think it's a bit overkill as it will set all dconf (gsettings) back to defaults
mv .config/dconf/user .config/dconf/user.bak && sudo reboot
add a comment |Â
up vote
11
down vote
If you want to reset your GNOME specific settings to default as if you had never logged in try
rm -rf .gnome .gnome2 .gconf .gconfd .metacity
add a comment |Â
up vote
4
down vote
Logout, switch to command line (Alt+ctrl+F1), login, do:rm -rf .gnome .gnome2 .gconf .gconfd .metacity, switch to X (Alt+ctrl+F7).
Just like they described it here:
http://www.linuxjournal.com/content/resetting-gnomes-settings-ubuntu
add a comment |Â
up vote
3
down vote
You can use the mv command.
The syntax is:
mv source1 source2 source3 ... sourceN destination
So in your case:
mv .gnome .gnome2 .gconf .gconfd .metacity .cache
.dbus .dmrc .mission-control .thumbnails .config/dconf/user
.compiz* ./.old-gnome-config/
The last one is the destination.
Explanation: This is moving the old configuration to backup destination ./.old-gnome-config/ it needs to be run in the home directory. Afterwards ubuntu restores the default configuration.
â mondjunge
Oct 21 '13 at 10:22
add a comment |Â
up vote
2
down vote
Resetting Gnome Extensions
If you need to remove your Gnome Extensions (I ran into this problem when trying out Ubuntu 17.10 on an upgraded system) run:
rm -rf ~/.local/share/gnome-shell/extensions
Keep in mind that this will wipe all of your extensions.
To remove an individual extension, you can navigate to ~/.local/share/gnome-shell/extensions and look for the extension's folder, then delete it.
If you'd like to backup
To backup, run:
cp ~/.local/share/gnome-shell/extensions ~/.local/share/gnome-shell/extensions-bkup
now my extensions don't load. any fix for that? I've installed the again from the site but either all don't work or just some works
â Tosho
Dec 25 '17 at 2:44
@Tosho a couple of things: 1. Did you check to see that the extensions you installed are compatible with your Gnome Shell version? 2. Have you restarted Gnome Shell or logged out + logged back in?
â RolandiXorâ¦
Dec 25 '17 at 17:05
I've re-installed Ubuntu Gnome 17.04 keeping my using my old /home partition. Now after some cleaning, re-installs and deleting, now most of them seems to work just fine. Only few extensions got ERROR after Updating from extensions.gnome.org or they crash randomly and restart doesn't fix anything. I'll leave it like it is for now. Thanks
â Tosho
Dec 26 '17 at 18:09
add a comment |Â
up vote
0
down vote
I did :
cd $HOME
cd .config
rm -R *
sudo reboot
And I've found my desktop like the first day I create my user account, but all my software params are the same (firefox, thunderbird, filezilla...)
This helped me. Thank YOUUU!!
â thednp
Sep 8 '15 at 17:54
Its help me.. Thanks @P-J Marquet
â Amitabha Biswas
Mar 30 '16 at 10:59
This resets EVERYTHING that uses ~/.config to store configuration data. NOT recommended.
â RolandiXorâ¦
Dec 20 '17 at 0:15
add a comment |Â
up vote
-1
down vote
Reinstalling gnome-tweak-tool resolved this issue and after reboot the GNOME 3 come up again. Actually gnome-tweak-tool was installed but the system detects it as a uninstalled one.
5
Are you saying that reinstallinggnome-tweak-toolactually resets GNOME settings to their defaults? Or just that it can fix some problems that might motivate someone to want to reset them?
â Eliah Kagan
Oct 7 '12 at 12:15
Issue is Gnome settings reset. Reinstalling 'gnome-tweak-tool' does not reset Gnome settings.
â Pasi Suominen
Apr 5 at 14:49
add a comment |Â
9 Answers
9
active
oldest
votes
9 Answers
9
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
126
down vote
accepted
For Unity-related configuration resetting, take a look here.
For Ubuntu 17.10 and higher, you can reset all the settings using dconf.
This command will delete your configuration files. Once it's run there is no going back!
Still with me?
GNOME2
Run the following in the terminal or Alt+F2:
rm -rf .gnome .gnome2 .gconf .gconfd .metacity
That will do is remove all the GNOME2 configuration settings. Log out, and log back in. You'll be back to a stock desktop.
You can backup before playing around with your settings in the future:
mkdir ./.old-gnome-config && mv ./.gnome* ./.old-gnome-config && mv .gconf* ./.old-gnome-config && mv ./.metacity ./.old-gnome-config
GNOME3
If your config isn't worth saving run the following:
rm -rf .gnome .gnome2 .gconf .gconfd .metacity .cache .dbus .dmrc .mission-control .thumbnails ~/.config/dconf/user ~.compiz*
To back up and reset GNOME3:
mkdir ./.old-gnome-config/ && mv ./.gnome* ./.old-gnome-config/ && mv .gconf* ./.old-gnome-config/ && mv ./.metacity ./.old-gnome-config/ && mv ./.cache ./.old-gnome-config/ && mv ./.dbus ./.old-gnome-config/ && mv ./.dmrc ./.old-gnome-config/ && mv ./.mission-control ./.old-gnome-config/ && mv ./.thumbnails ./.old-gnome-config/ && mv ~/.config/dconf/* ./.old-gnome-config/
10
more concise and precise to use a for loop for the backup step, e.g.for f in .gnome .gnome2 .gconf .gconfd .metacity; do mv $f $f.bak; doneormkdir -p ~/.backup-gnome-config/ && for f in .gnome .gnome2 .gconf .gconfd .metacity; do mv $f ~/.backup-gnome-config/; done
â hobs
Aug 13 '12 at 1:38
Shorten that last bit tomkdir ./.old-gnome-config/ && mv ./.gnome* .gconf* ./.metacity ./.cache ./.dbus ./.dmrc ./.mission-control ./.thumbnails ~/.config/dconf/* ./.old-gnome-config/
â smac89
Dec 22 '16 at 19:08
add a comment |Â
up vote
126
down vote
accepted
For Unity-related configuration resetting, take a look here.
For Ubuntu 17.10 and higher, you can reset all the settings using dconf.
This command will delete your configuration files. Once it's run there is no going back!
Still with me?
GNOME2
Run the following in the terminal or Alt+F2:
rm -rf .gnome .gnome2 .gconf .gconfd .metacity
That will do is remove all the GNOME2 configuration settings. Log out, and log back in. You'll be back to a stock desktop.
You can backup before playing around with your settings in the future:
mkdir ./.old-gnome-config && mv ./.gnome* ./.old-gnome-config && mv .gconf* ./.old-gnome-config && mv ./.metacity ./.old-gnome-config
GNOME3
If your config isn't worth saving run the following:
rm -rf .gnome .gnome2 .gconf .gconfd .metacity .cache .dbus .dmrc .mission-control .thumbnails ~/.config/dconf/user ~.compiz*
To back up and reset GNOME3:
mkdir ./.old-gnome-config/ && mv ./.gnome* ./.old-gnome-config/ && mv .gconf* ./.old-gnome-config/ && mv ./.metacity ./.old-gnome-config/ && mv ./.cache ./.old-gnome-config/ && mv ./.dbus ./.old-gnome-config/ && mv ./.dmrc ./.old-gnome-config/ && mv ./.mission-control ./.old-gnome-config/ && mv ./.thumbnails ./.old-gnome-config/ && mv ~/.config/dconf/* ./.old-gnome-config/
10
more concise and precise to use a for loop for the backup step, e.g.for f in .gnome .gnome2 .gconf .gconfd .metacity; do mv $f $f.bak; doneormkdir -p ~/.backup-gnome-config/ && for f in .gnome .gnome2 .gconf .gconfd .metacity; do mv $f ~/.backup-gnome-config/; done
â hobs
Aug 13 '12 at 1:38
Shorten that last bit tomkdir ./.old-gnome-config/ && mv ./.gnome* .gconf* ./.metacity ./.cache ./.dbus ./.dmrc ./.mission-control ./.thumbnails ~/.config/dconf/* ./.old-gnome-config/
â smac89
Dec 22 '16 at 19:08
add a comment |Â
up vote
126
down vote
accepted
up vote
126
down vote
accepted
For Unity-related configuration resetting, take a look here.
For Ubuntu 17.10 and higher, you can reset all the settings using dconf.
This command will delete your configuration files. Once it's run there is no going back!
Still with me?
GNOME2
Run the following in the terminal or Alt+F2:
rm -rf .gnome .gnome2 .gconf .gconfd .metacity
That will do is remove all the GNOME2 configuration settings. Log out, and log back in. You'll be back to a stock desktop.
You can backup before playing around with your settings in the future:
mkdir ./.old-gnome-config && mv ./.gnome* ./.old-gnome-config && mv .gconf* ./.old-gnome-config && mv ./.metacity ./.old-gnome-config
GNOME3
If your config isn't worth saving run the following:
rm -rf .gnome .gnome2 .gconf .gconfd .metacity .cache .dbus .dmrc .mission-control .thumbnails ~/.config/dconf/user ~.compiz*
To back up and reset GNOME3:
mkdir ./.old-gnome-config/ && mv ./.gnome* ./.old-gnome-config/ && mv .gconf* ./.old-gnome-config/ && mv ./.metacity ./.old-gnome-config/ && mv ./.cache ./.old-gnome-config/ && mv ./.dbus ./.old-gnome-config/ && mv ./.dmrc ./.old-gnome-config/ && mv ./.mission-control ./.old-gnome-config/ && mv ./.thumbnails ./.old-gnome-config/ && mv ~/.config/dconf/* ./.old-gnome-config/
For Unity-related configuration resetting, take a look here.
For Ubuntu 17.10 and higher, you can reset all the settings using dconf.
This command will delete your configuration files. Once it's run there is no going back!
Still with me?
GNOME2
Run the following in the terminal or Alt+F2:
rm -rf .gnome .gnome2 .gconf .gconfd .metacity
That will do is remove all the GNOME2 configuration settings. Log out, and log back in. You'll be back to a stock desktop.
You can backup before playing around with your settings in the future:
mkdir ./.old-gnome-config && mv ./.gnome* ./.old-gnome-config && mv .gconf* ./.old-gnome-config && mv ./.metacity ./.old-gnome-config
GNOME3
If your config isn't worth saving run the following:
rm -rf .gnome .gnome2 .gconf .gconfd .metacity .cache .dbus .dmrc .mission-control .thumbnails ~/.config/dconf/user ~.compiz*
To back up and reset GNOME3:
mkdir ./.old-gnome-config/ && mv ./.gnome* ./.old-gnome-config/ && mv .gconf* ./.old-gnome-config/ && mv ./.metacity ./.old-gnome-config/ && mv ./.cache ./.old-gnome-config/ && mv ./.dbus ./.old-gnome-config/ && mv ./.dmrc ./.old-gnome-config/ && mv ./.mission-control ./.old-gnome-config/ && mv ./.thumbnails ./.old-gnome-config/ && mv ~/.config/dconf/* ./.old-gnome-config/
edited Oct 4 '17 at 20:48
Galgalesh
4,87112352
4,87112352
answered Aug 8 '11 at 15:51
jrgâ¦
38.3k49146235
38.3k49146235
10
more concise and precise to use a for loop for the backup step, e.g.for f in .gnome .gnome2 .gconf .gconfd .metacity; do mv $f $f.bak; doneormkdir -p ~/.backup-gnome-config/ && for f in .gnome .gnome2 .gconf .gconfd .metacity; do mv $f ~/.backup-gnome-config/; done
â hobs
Aug 13 '12 at 1:38
Shorten that last bit tomkdir ./.old-gnome-config/ && mv ./.gnome* .gconf* ./.metacity ./.cache ./.dbus ./.dmrc ./.mission-control ./.thumbnails ~/.config/dconf/* ./.old-gnome-config/
â smac89
Dec 22 '16 at 19:08
add a comment |Â
10
more concise and precise to use a for loop for the backup step, e.g.for f in .gnome .gnome2 .gconf .gconfd .metacity; do mv $f $f.bak; doneormkdir -p ~/.backup-gnome-config/ && for f in .gnome .gnome2 .gconf .gconfd .metacity; do mv $f ~/.backup-gnome-config/; done
â hobs
Aug 13 '12 at 1:38
Shorten that last bit tomkdir ./.old-gnome-config/ && mv ./.gnome* .gconf* ./.metacity ./.cache ./.dbus ./.dmrc ./.mission-control ./.thumbnails ~/.config/dconf/* ./.old-gnome-config/
â smac89
Dec 22 '16 at 19:08
10
10
more concise and precise to use a for loop for the backup step, e.g.
for f in .gnome .gnome2 .gconf .gconfd .metacity; do mv $f $f.bak; done or mkdir -p ~/.backup-gnome-config/ && for f in .gnome .gnome2 .gconf .gconfd .metacity; do mv $f ~/.backup-gnome-config/; doneâ hobs
Aug 13 '12 at 1:38
more concise and precise to use a for loop for the backup step, e.g.
for f in .gnome .gnome2 .gconf .gconfd .metacity; do mv $f $f.bak; done or mkdir -p ~/.backup-gnome-config/ && for f in .gnome .gnome2 .gconf .gconfd .metacity; do mv $f ~/.backup-gnome-config/; doneâ hobs
Aug 13 '12 at 1:38
Shorten that last bit to
mkdir ./.old-gnome-config/ && mv ./.gnome* .gconf* ./.metacity ./.cache ./.dbus ./.dmrc ./.mission-control ./.thumbnails ~/.config/dconf/* ./.old-gnome-config/â smac89
Dec 22 '16 at 19:08
Shorten that last bit to
mkdir ./.old-gnome-config/ && mv ./.gnome* .gconf* ./.metacity ./.cache ./.dbus ./.dmrc ./.mission-control ./.thumbnails ~/.config/dconf/* ./.old-gnome-config/â smac89
Dec 22 '16 at 19:08
add a comment |Â
up vote
18
down vote
Fore me those directories were not sufficient - I had to delete ~/.config/dconf/user as well.
This helped for me in those two cases:
- gnome-panel config broken
(tried to specify location "left" for one gnome panel, it immediately crashed and could not be started afterwards) - GTK Theme and GTK Icons broken
(nevertheless the selection via e. g.gnome-tweak-tool, it remained in ugly Windows-style grey look and icons were standard gnome - I have no clue how this was provoked, it appeared suddenly after login)
This corresponds to the Gnome 3 Fallback Mode I use on Linux Mint 12 Lisa (Oneiric based). But the GTK problem persisted in all other login modes as well (MATE, Gnome 3 Standard)!
I am unsure now to which mechanism the ~/.config/dconf/user file corresponds, as I found out that in Linux Mint only _mateconf-editor_ is installed by default but outfitted with the title and icon of gconf-editor from Natty!
After installing gconf-editor additionally, this one is titled identically but has a different (new) icon. But don't rely on this icon stories, because this will rely on the icon theme which is Mint-X-Dark for me.
Theory says that dconf is the successor for gconf, but I found no information regarding the GUIs.
1
Yes, I had the same problem and needed to remove ~/.config/dconf aswell
â wim
Jan 4 '12 at 23:25
+1 for the info, but it'd be even better if you rewrite to incorporate your edits
â djeikyb
Jan 5 '12 at 22:23
This helped with the missing Lock Screen menu option (which is probably down to yet another corrupt dconf config)
â prusswan
Nov 30 '12 at 4:59
1
Saved my life! Spent the last two hours unable to load my Ubuntu desktop, but deleting ~/.config/dconf/user did the trick
â leopld
Jan 9 '15 at 14:52
This is weird, i have to delete this file after every reboot to avoid login loop.
â Ondra à ½ià ¾ka
May 4 at 16:33
 |Â
show 2 more comments
up vote
18
down vote
Fore me those directories were not sufficient - I had to delete ~/.config/dconf/user as well.
This helped for me in those two cases:
- gnome-panel config broken
(tried to specify location "left" for one gnome panel, it immediately crashed and could not be started afterwards) - GTK Theme and GTK Icons broken
(nevertheless the selection via e. g.gnome-tweak-tool, it remained in ugly Windows-style grey look and icons were standard gnome - I have no clue how this was provoked, it appeared suddenly after login)
This corresponds to the Gnome 3 Fallback Mode I use on Linux Mint 12 Lisa (Oneiric based). But the GTK problem persisted in all other login modes as well (MATE, Gnome 3 Standard)!
I am unsure now to which mechanism the ~/.config/dconf/user file corresponds, as I found out that in Linux Mint only _mateconf-editor_ is installed by default but outfitted with the title and icon of gconf-editor from Natty!
After installing gconf-editor additionally, this one is titled identically but has a different (new) icon. But don't rely on this icon stories, because this will rely on the icon theme which is Mint-X-Dark for me.
Theory says that dconf is the successor for gconf, but I found no information regarding the GUIs.
1
Yes, I had the same problem and needed to remove ~/.config/dconf aswell
â wim
Jan 4 '12 at 23:25
+1 for the info, but it'd be even better if you rewrite to incorporate your edits
â djeikyb
Jan 5 '12 at 22:23
This helped with the missing Lock Screen menu option (which is probably down to yet another corrupt dconf config)
â prusswan
Nov 30 '12 at 4:59
1
Saved my life! Spent the last two hours unable to load my Ubuntu desktop, but deleting ~/.config/dconf/user did the trick
â leopld
Jan 9 '15 at 14:52
This is weird, i have to delete this file after every reboot to avoid login loop.
â Ondra à ½ià ¾ka
May 4 at 16:33
 |Â
show 2 more comments
up vote
18
down vote
up vote
18
down vote
Fore me those directories were not sufficient - I had to delete ~/.config/dconf/user as well.
This helped for me in those two cases:
- gnome-panel config broken
(tried to specify location "left" for one gnome panel, it immediately crashed and could not be started afterwards) - GTK Theme and GTK Icons broken
(nevertheless the selection via e. g.gnome-tweak-tool, it remained in ugly Windows-style grey look and icons were standard gnome - I have no clue how this was provoked, it appeared suddenly after login)
This corresponds to the Gnome 3 Fallback Mode I use on Linux Mint 12 Lisa (Oneiric based). But the GTK problem persisted in all other login modes as well (MATE, Gnome 3 Standard)!
I am unsure now to which mechanism the ~/.config/dconf/user file corresponds, as I found out that in Linux Mint only _mateconf-editor_ is installed by default but outfitted with the title and icon of gconf-editor from Natty!
After installing gconf-editor additionally, this one is titled identically but has a different (new) icon. But don't rely on this icon stories, because this will rely on the icon theme which is Mint-X-Dark for me.
Theory says that dconf is the successor for gconf, but I found no information regarding the GUIs.
Fore me those directories were not sufficient - I had to delete ~/.config/dconf/user as well.
This helped for me in those two cases:
- gnome-panel config broken
(tried to specify location "left" for one gnome panel, it immediately crashed and could not be started afterwards) - GTK Theme and GTK Icons broken
(nevertheless the selection via e. g.gnome-tweak-tool, it remained in ugly Windows-style grey look and icons were standard gnome - I have no clue how this was provoked, it appeared suddenly after login)
This corresponds to the Gnome 3 Fallback Mode I use on Linux Mint 12 Lisa (Oneiric based). But the GTK problem persisted in all other login modes as well (MATE, Gnome 3 Standard)!
I am unsure now to which mechanism the ~/.config/dconf/user file corresponds, as I found out that in Linux Mint only _mateconf-editor_ is installed by default but outfitted with the title and icon of gconf-editor from Natty!
After installing gconf-editor additionally, this one is titled identically but has a different (new) icon. But don't rely on this icon stories, because this will rely on the icon theme which is Mint-X-Dark for me.
Theory says that dconf is the successor for gconf, but I found no information regarding the GUIs.
edited May 5 at 7:06
d a i s y
3,05672242
3,05672242
answered Jan 4 '12 at 23:14
Nicolas
487519
487519
1
Yes, I had the same problem and needed to remove ~/.config/dconf aswell
â wim
Jan 4 '12 at 23:25
+1 for the info, but it'd be even better if you rewrite to incorporate your edits
â djeikyb
Jan 5 '12 at 22:23
This helped with the missing Lock Screen menu option (which is probably down to yet another corrupt dconf config)
â prusswan
Nov 30 '12 at 4:59
1
Saved my life! Spent the last two hours unable to load my Ubuntu desktop, but deleting ~/.config/dconf/user did the trick
â leopld
Jan 9 '15 at 14:52
This is weird, i have to delete this file after every reboot to avoid login loop.
â Ondra à ½ià ¾ka
May 4 at 16:33
 |Â
show 2 more comments
1
Yes, I had the same problem and needed to remove ~/.config/dconf aswell
â wim
Jan 4 '12 at 23:25
+1 for the info, but it'd be even better if you rewrite to incorporate your edits
â djeikyb
Jan 5 '12 at 22:23
This helped with the missing Lock Screen menu option (which is probably down to yet another corrupt dconf config)
â prusswan
Nov 30 '12 at 4:59
1
Saved my life! Spent the last two hours unable to load my Ubuntu desktop, but deleting ~/.config/dconf/user did the trick
â leopld
Jan 9 '15 at 14:52
This is weird, i have to delete this file after every reboot to avoid login loop.
â Ondra à ½ià ¾ka
May 4 at 16:33
1
1
Yes, I had the same problem and needed to remove ~/.config/dconf aswell
â wim
Jan 4 '12 at 23:25
Yes, I had the same problem and needed to remove ~/.config/dconf aswell
â wim
Jan 4 '12 at 23:25
+1 for the info, but it'd be even better if you rewrite to incorporate your edits
â djeikyb
Jan 5 '12 at 22:23
+1 for the info, but it'd be even better if you rewrite to incorporate your edits
â djeikyb
Jan 5 '12 at 22:23
This helped with the missing Lock Screen menu option (which is probably down to yet another corrupt dconf config)
â prusswan
Nov 30 '12 at 4:59
This helped with the missing Lock Screen menu option (which is probably down to yet another corrupt dconf config)
â prusswan
Nov 30 '12 at 4:59
1
1
Saved my life! Spent the last two hours unable to load my Ubuntu desktop, but deleting ~/.config/dconf/user did the trick
â leopld
Jan 9 '15 at 14:52
Saved my life! Spent the last two hours unable to load my Ubuntu desktop, but deleting ~/.config/dconf/user did the trick
â leopld
Jan 9 '15 at 14:52
This is weird, i have to delete this file after every reboot to avoid login loop.
â Ondra à ½ià ¾ka
May 4 at 16:33
This is weird, i have to delete this file after every reboot to avoid login loop.
â Ondra à ½ià ¾ka
May 4 at 16:33
 |Â
show 2 more comments
up vote
14
down vote
For 17.10+
There isn't a great solution but this may do the job or most of it.
dconf reset -f /org/gnome/
Then log out/in
That command's path could be shortened if needing a more extensive reset, i.e. to just /org/ or even / but I'd go with above first.
Worst case one could also just go this in a terminal, I think it's a bit overkill as it will set all dconf (gsettings) back to defaults
mv .config/dconf/user .config/dconf/user.bak && sudo reboot
add a comment |Â
up vote
14
down vote
For 17.10+
There isn't a great solution but this may do the job or most of it.
dconf reset -f /org/gnome/
Then log out/in
That command's path could be shortened if needing a more extensive reset, i.e. to just /org/ or even / but I'd go with above first.
Worst case one could also just go this in a terminal, I think it's a bit overkill as it will set all dconf (gsettings) back to defaults
mv .config/dconf/user .config/dconf/user.bak && sudo reboot
add a comment |Â
up vote
14
down vote
up vote
14
down vote
For 17.10+
There isn't a great solution but this may do the job or most of it.
dconf reset -f /org/gnome/
Then log out/in
That command's path could be shortened if needing a more extensive reset, i.e. to just /org/ or even / but I'd go with above first.
Worst case one could also just go this in a terminal, I think it's a bit overkill as it will set all dconf (gsettings) back to defaults
mv .config/dconf/user .config/dconf/user.bak && sudo reboot
For 17.10+
There isn't a great solution but this may do the job or most of it.
dconf reset -f /org/gnome/
Then log out/in
That command's path could be shortened if needing a more extensive reset, i.e. to just /org/ or even / but I'd go with above first.
Worst case one could also just go this in a terminal, I think it's a bit overkill as it will set all dconf (gsettings) back to defaults
mv .config/dconf/user .config/dconf/user.bak && sudo reboot
edited Dec 20 '17 at 3:08
muru
1
1
answered Sep 27 '17 at 16:20
doug
13.6k13451
13.6k13451
add a comment |Â
add a comment |Â
up vote
11
down vote
If you want to reset your GNOME specific settings to default as if you had never logged in try
rm -rf .gnome .gnome2 .gconf .gconfd .metacity
add a comment |Â
up vote
11
down vote
If you want to reset your GNOME specific settings to default as if you had never logged in try
rm -rf .gnome .gnome2 .gconf .gconfd .metacity
add a comment |Â
up vote
11
down vote
up vote
11
down vote
If you want to reset your GNOME specific settings to default as if you had never logged in try
rm -rf .gnome .gnome2 .gconf .gconfd .metacity
If you want to reset your GNOME specific settings to default as if you had never logged in try
rm -rf .gnome .gnome2 .gconf .gconfd .metacity
answered Aug 8 '11 at 15:53
Christopher Stansbury
7241421
7241421
add a comment |Â
add a comment |Â
up vote
4
down vote
Logout, switch to command line (Alt+ctrl+F1), login, do:rm -rf .gnome .gnome2 .gconf .gconfd .metacity, switch to X (Alt+ctrl+F7).
Just like they described it here:
http://www.linuxjournal.com/content/resetting-gnomes-settings-ubuntu
add a comment |Â
up vote
4
down vote
Logout, switch to command line (Alt+ctrl+F1), login, do:rm -rf .gnome .gnome2 .gconf .gconfd .metacity, switch to X (Alt+ctrl+F7).
Just like they described it here:
http://www.linuxjournal.com/content/resetting-gnomes-settings-ubuntu
add a comment |Â
up vote
4
down vote
up vote
4
down vote
Logout, switch to command line (Alt+ctrl+F1), login, do:rm -rf .gnome .gnome2 .gconf .gconfd .metacity, switch to X (Alt+ctrl+F7).
Just like they described it here:
http://www.linuxjournal.com/content/resetting-gnomes-settings-ubuntu
Logout, switch to command line (Alt+ctrl+F1), login, do:rm -rf .gnome .gnome2 .gconf .gconfd .metacity, switch to X (Alt+ctrl+F7).
Just like they described it here:
http://www.linuxjournal.com/content/resetting-gnomes-settings-ubuntu
edited Aug 8 '11 at 16:05
answered Aug 8 '11 at 15:52
Krzysztof Hasià Âski
347110
347110
add a comment |Â
add a comment |Â
up vote
3
down vote
You can use the mv command.
The syntax is:
mv source1 source2 source3 ... sourceN destination
So in your case:
mv .gnome .gnome2 .gconf .gconfd .metacity .cache
.dbus .dmrc .mission-control .thumbnails .config/dconf/user
.compiz* ./.old-gnome-config/
The last one is the destination.
Explanation: This is moving the old configuration to backup destination ./.old-gnome-config/ it needs to be run in the home directory. Afterwards ubuntu restores the default configuration.
â mondjunge
Oct 21 '13 at 10:22
add a comment |Â
up vote
3
down vote
You can use the mv command.
The syntax is:
mv source1 source2 source3 ... sourceN destination
So in your case:
mv .gnome .gnome2 .gconf .gconfd .metacity .cache
.dbus .dmrc .mission-control .thumbnails .config/dconf/user
.compiz* ./.old-gnome-config/
The last one is the destination.
Explanation: This is moving the old configuration to backup destination ./.old-gnome-config/ it needs to be run in the home directory. Afterwards ubuntu restores the default configuration.
â mondjunge
Oct 21 '13 at 10:22
add a comment |Â
up vote
3
down vote
up vote
3
down vote
You can use the mv command.
The syntax is:
mv source1 source2 source3 ... sourceN destination
So in your case:
mv .gnome .gnome2 .gconf .gconfd .metacity .cache
.dbus .dmrc .mission-control .thumbnails .config/dconf/user
.compiz* ./.old-gnome-config/
The last one is the destination.
You can use the mv command.
The syntax is:
mv source1 source2 source3 ... sourceN destination
So in your case:
mv .gnome .gnome2 .gconf .gconfd .metacity .cache
.dbus .dmrc .mission-control .thumbnails .config/dconf/user
.compiz* ./.old-gnome-config/
The last one is the destination.
edited Mar 30 '14 at 12:29
answered Oct 20 '13 at 17:11
maxadamo
1304
1304
Explanation: This is moving the old configuration to backup destination ./.old-gnome-config/ it needs to be run in the home directory. Afterwards ubuntu restores the default configuration.
â mondjunge
Oct 21 '13 at 10:22
add a comment |Â
Explanation: This is moving the old configuration to backup destination ./.old-gnome-config/ it needs to be run in the home directory. Afterwards ubuntu restores the default configuration.
â mondjunge
Oct 21 '13 at 10:22
Explanation: This is moving the old configuration to backup destination ./.old-gnome-config/ it needs to be run in the home directory. Afterwards ubuntu restores the default configuration.
â mondjunge
Oct 21 '13 at 10:22
Explanation: This is moving the old configuration to backup destination ./.old-gnome-config/ it needs to be run in the home directory. Afterwards ubuntu restores the default configuration.
â mondjunge
Oct 21 '13 at 10:22
add a comment |Â
up vote
2
down vote
Resetting Gnome Extensions
If you need to remove your Gnome Extensions (I ran into this problem when trying out Ubuntu 17.10 on an upgraded system) run:
rm -rf ~/.local/share/gnome-shell/extensions
Keep in mind that this will wipe all of your extensions.
To remove an individual extension, you can navigate to ~/.local/share/gnome-shell/extensions and look for the extension's folder, then delete it.
If you'd like to backup
To backup, run:
cp ~/.local/share/gnome-shell/extensions ~/.local/share/gnome-shell/extensions-bkup
now my extensions don't load. any fix for that? I've installed the again from the site but either all don't work or just some works
â Tosho
Dec 25 '17 at 2:44
@Tosho a couple of things: 1. Did you check to see that the extensions you installed are compatible with your Gnome Shell version? 2. Have you restarted Gnome Shell or logged out + logged back in?
â RolandiXorâ¦
Dec 25 '17 at 17:05
I've re-installed Ubuntu Gnome 17.04 keeping my using my old /home partition. Now after some cleaning, re-installs and deleting, now most of them seems to work just fine. Only few extensions got ERROR after Updating from extensions.gnome.org or they crash randomly and restart doesn't fix anything. I'll leave it like it is for now. Thanks
â Tosho
Dec 26 '17 at 18:09
add a comment |Â
up vote
2
down vote
Resetting Gnome Extensions
If you need to remove your Gnome Extensions (I ran into this problem when trying out Ubuntu 17.10 on an upgraded system) run:
rm -rf ~/.local/share/gnome-shell/extensions
Keep in mind that this will wipe all of your extensions.
To remove an individual extension, you can navigate to ~/.local/share/gnome-shell/extensions and look for the extension's folder, then delete it.
If you'd like to backup
To backup, run:
cp ~/.local/share/gnome-shell/extensions ~/.local/share/gnome-shell/extensions-bkup
now my extensions don't load. any fix for that? I've installed the again from the site but either all don't work or just some works
â Tosho
Dec 25 '17 at 2:44
@Tosho a couple of things: 1. Did you check to see that the extensions you installed are compatible with your Gnome Shell version? 2. Have you restarted Gnome Shell or logged out + logged back in?
â RolandiXorâ¦
Dec 25 '17 at 17:05
I've re-installed Ubuntu Gnome 17.04 keeping my using my old /home partition. Now after some cleaning, re-installs and deleting, now most of them seems to work just fine. Only few extensions got ERROR after Updating from extensions.gnome.org or they crash randomly and restart doesn't fix anything. I'll leave it like it is for now. Thanks
â Tosho
Dec 26 '17 at 18:09
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Resetting Gnome Extensions
If you need to remove your Gnome Extensions (I ran into this problem when trying out Ubuntu 17.10 on an upgraded system) run:
rm -rf ~/.local/share/gnome-shell/extensions
Keep in mind that this will wipe all of your extensions.
To remove an individual extension, you can navigate to ~/.local/share/gnome-shell/extensions and look for the extension's folder, then delete it.
If you'd like to backup
To backup, run:
cp ~/.local/share/gnome-shell/extensions ~/.local/share/gnome-shell/extensions-bkup
Resetting Gnome Extensions
If you need to remove your Gnome Extensions (I ran into this problem when trying out Ubuntu 17.10 on an upgraded system) run:
rm -rf ~/.local/share/gnome-shell/extensions
Keep in mind that this will wipe all of your extensions.
To remove an individual extension, you can navigate to ~/.local/share/gnome-shell/extensions and look for the extension's folder, then delete it.
If you'd like to backup
To backup, run:
cp ~/.local/share/gnome-shell/extensions ~/.local/share/gnome-shell/extensions-bkup
edited Dec 20 '17 at 3:07
muru
1
1
answered Dec 20 '17 at 0:13
RolandiXorâ¦
44.5k25139228
44.5k25139228
now my extensions don't load. any fix for that? I've installed the again from the site but either all don't work or just some works
â Tosho
Dec 25 '17 at 2:44
@Tosho a couple of things: 1. Did you check to see that the extensions you installed are compatible with your Gnome Shell version? 2. Have you restarted Gnome Shell or logged out + logged back in?
â RolandiXorâ¦
Dec 25 '17 at 17:05
I've re-installed Ubuntu Gnome 17.04 keeping my using my old /home partition. Now after some cleaning, re-installs and deleting, now most of them seems to work just fine. Only few extensions got ERROR after Updating from extensions.gnome.org or they crash randomly and restart doesn't fix anything. I'll leave it like it is for now. Thanks
â Tosho
Dec 26 '17 at 18:09
add a comment |Â
now my extensions don't load. any fix for that? I've installed the again from the site but either all don't work or just some works
â Tosho
Dec 25 '17 at 2:44
@Tosho a couple of things: 1. Did you check to see that the extensions you installed are compatible with your Gnome Shell version? 2. Have you restarted Gnome Shell or logged out + logged back in?
â RolandiXorâ¦
Dec 25 '17 at 17:05
I've re-installed Ubuntu Gnome 17.04 keeping my using my old /home partition. Now after some cleaning, re-installs and deleting, now most of them seems to work just fine. Only few extensions got ERROR after Updating from extensions.gnome.org or they crash randomly and restart doesn't fix anything. I'll leave it like it is for now. Thanks
â Tosho
Dec 26 '17 at 18:09
now my extensions don't load. any fix for that? I've installed the again from the site but either all don't work or just some works
â Tosho
Dec 25 '17 at 2:44
now my extensions don't load. any fix for that? I've installed the again from the site but either all don't work or just some works
â Tosho
Dec 25 '17 at 2:44
@Tosho a couple of things: 1. Did you check to see that the extensions you installed are compatible with your Gnome Shell version? 2. Have you restarted Gnome Shell or logged out + logged back in?
â RolandiXorâ¦
Dec 25 '17 at 17:05
@Tosho a couple of things: 1. Did you check to see that the extensions you installed are compatible with your Gnome Shell version? 2. Have you restarted Gnome Shell or logged out + logged back in?
â RolandiXorâ¦
Dec 25 '17 at 17:05
I've re-installed Ubuntu Gnome 17.04 keeping my using my old /home partition. Now after some cleaning, re-installs and deleting, now most of them seems to work just fine. Only few extensions got ERROR after Updating from extensions.gnome.org or they crash randomly and restart doesn't fix anything. I'll leave it like it is for now. Thanks
â Tosho
Dec 26 '17 at 18:09
I've re-installed Ubuntu Gnome 17.04 keeping my using my old /home partition. Now after some cleaning, re-installs and deleting, now most of them seems to work just fine. Only few extensions got ERROR after Updating from extensions.gnome.org or they crash randomly and restart doesn't fix anything. I'll leave it like it is for now. Thanks
â Tosho
Dec 26 '17 at 18:09
add a comment |Â
up vote
0
down vote
I did :
cd $HOME
cd .config
rm -R *
sudo reboot
And I've found my desktop like the first day I create my user account, but all my software params are the same (firefox, thunderbird, filezilla...)
This helped me. Thank YOUUU!!
â thednp
Sep 8 '15 at 17:54
Its help me.. Thanks @P-J Marquet
â Amitabha Biswas
Mar 30 '16 at 10:59
This resets EVERYTHING that uses ~/.config to store configuration data. NOT recommended.
â RolandiXorâ¦
Dec 20 '17 at 0:15
add a comment |Â
up vote
0
down vote
I did :
cd $HOME
cd .config
rm -R *
sudo reboot
And I've found my desktop like the first day I create my user account, but all my software params are the same (firefox, thunderbird, filezilla...)
This helped me. Thank YOUUU!!
â thednp
Sep 8 '15 at 17:54
Its help me.. Thanks @P-J Marquet
â Amitabha Biswas
Mar 30 '16 at 10:59
This resets EVERYTHING that uses ~/.config to store configuration data. NOT recommended.
â RolandiXorâ¦
Dec 20 '17 at 0:15
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I did :
cd $HOME
cd .config
rm -R *
sudo reboot
And I've found my desktop like the first day I create my user account, but all my software params are the same (firefox, thunderbird, filezilla...)
I did :
cd $HOME
cd .config
rm -R *
sudo reboot
And I've found my desktop like the first day I create my user account, but all my software params are the same (firefox, thunderbird, filezilla...)
edited Jul 28 '15 at 0:30
amc
4,47862746
4,47862746
answered Jul 27 '15 at 19:46
P-J Marquet
91
91
This helped me. Thank YOUUU!!
â thednp
Sep 8 '15 at 17:54
Its help me.. Thanks @P-J Marquet
â Amitabha Biswas
Mar 30 '16 at 10:59
This resets EVERYTHING that uses ~/.config to store configuration data. NOT recommended.
â RolandiXorâ¦
Dec 20 '17 at 0:15
add a comment |Â
This helped me. Thank YOUUU!!
â thednp
Sep 8 '15 at 17:54
Its help me.. Thanks @P-J Marquet
â Amitabha Biswas
Mar 30 '16 at 10:59
This resets EVERYTHING that uses ~/.config to store configuration data. NOT recommended.
â RolandiXorâ¦
Dec 20 '17 at 0:15
This helped me. Thank YOUUU!!
â thednp
Sep 8 '15 at 17:54
This helped me. Thank YOUUU!!
â thednp
Sep 8 '15 at 17:54
Its help me.. Thanks @P-J Marquet
â Amitabha Biswas
Mar 30 '16 at 10:59
Its help me.. Thanks @P-J Marquet
â Amitabha Biswas
Mar 30 '16 at 10:59
This resets EVERYTHING that uses ~/.config to store configuration data. NOT recommended.
â RolandiXorâ¦
Dec 20 '17 at 0:15
This resets EVERYTHING that uses ~/.config to store configuration data. NOT recommended.
â RolandiXorâ¦
Dec 20 '17 at 0:15
add a comment |Â
up vote
-1
down vote
Reinstalling gnome-tweak-tool resolved this issue and after reboot the GNOME 3 come up again. Actually gnome-tweak-tool was installed but the system detects it as a uninstalled one.
5
Are you saying that reinstallinggnome-tweak-toolactually resets GNOME settings to their defaults? Or just that it can fix some problems that might motivate someone to want to reset them?
â Eliah Kagan
Oct 7 '12 at 12:15
Issue is Gnome settings reset. Reinstalling 'gnome-tweak-tool' does not reset Gnome settings.
â Pasi Suominen
Apr 5 at 14:49
add a comment |Â
up vote
-1
down vote
Reinstalling gnome-tweak-tool resolved this issue and after reboot the GNOME 3 come up again. Actually gnome-tweak-tool was installed but the system detects it as a uninstalled one.
5
Are you saying that reinstallinggnome-tweak-toolactually resets GNOME settings to their defaults? Or just that it can fix some problems that might motivate someone to want to reset them?
â Eliah Kagan
Oct 7 '12 at 12:15
Issue is Gnome settings reset. Reinstalling 'gnome-tweak-tool' does not reset Gnome settings.
â Pasi Suominen
Apr 5 at 14:49
add a comment |Â
up vote
-1
down vote
up vote
-1
down vote
Reinstalling gnome-tweak-tool resolved this issue and after reboot the GNOME 3 come up again. Actually gnome-tweak-tool was installed but the system detects it as a uninstalled one.
Reinstalling gnome-tweak-tool resolved this issue and after reboot the GNOME 3 come up again. Actually gnome-tweak-tool was installed but the system detects it as a uninstalled one.
edited Oct 7 '12 at 12:13
Eliah Kagan
79.4k20221359
79.4k20221359
answered Sep 21 '12 at 16:21
askkur
9
9
5
Are you saying that reinstallinggnome-tweak-toolactually resets GNOME settings to their defaults? Or just that it can fix some problems that might motivate someone to want to reset them?
â Eliah Kagan
Oct 7 '12 at 12:15
Issue is Gnome settings reset. Reinstalling 'gnome-tweak-tool' does not reset Gnome settings.
â Pasi Suominen
Apr 5 at 14:49
add a comment |Â
5
Are you saying that reinstallinggnome-tweak-toolactually resets GNOME settings to their defaults? Or just that it can fix some problems that might motivate someone to want to reset them?
â Eliah Kagan
Oct 7 '12 at 12:15
Issue is Gnome settings reset. Reinstalling 'gnome-tweak-tool' does not reset Gnome settings.
â Pasi Suominen
Apr 5 at 14:49
5
5
Are you saying that reinstalling
gnome-tweak-tool actually resets GNOME settings to their defaults? Or just that it can fix some problems that might motivate someone to want to reset them?â Eliah Kagan
Oct 7 '12 at 12:15
Are you saying that reinstalling
gnome-tweak-tool actually resets GNOME settings to their defaults? Or just that it can fix some problems that might motivate someone to want to reset them?â Eliah Kagan
Oct 7 '12 at 12:15
Issue is Gnome settings reset. Reinstalling 'gnome-tweak-tool' does not reset Gnome settings.
â Pasi Suominen
Apr 5 at 14:49
Issue is Gnome settings reset. Reinstalling 'gnome-tweak-tool' does not reset Gnome settings.
â Pasi Suominen
Apr 5 at 14:49
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f56313%2fhow-do-i-reset-gnome-to-the-defaults%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password