After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 468594 - It is too easy to remove an startup application.
It is too easy to remove an startup application.
Status: RESOLVED OBSOLETE
Product: gnome-session
Classification: Core
Component: gnome-session-properties
git master
Other Linux
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
: 550894 557432 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-08-20 17:19 UTC by Pedro Villavicencio
Modified: 2014-03-05 11:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Attachments
add revert button (4.45 KB, patch)
2007-09-29 03:31 UTC, Jared Moore
rejected Details | Review

Description Pedro Villavicencio 2007-08-20 17:19:18 UTC
This bug has been filled here:

https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/133706

"Binary package hint: gnome-session

All is in the title ... and it is impossible to recover easily.

I think that a confirmation window can correct this problem."
Comment 1 Jared Moore 2007-09-28 08:57:00 UTC
Another solution would be to have a "Revert" button (similar to the one in Alacarte). That also allows you to quickly go back to the defaults if you totally stuffed something up (e.g. changed the name/command/comment of one of the defaults, or added an app that you don't like, or added something that breaks the session, etc).

Comment 2 Jared Moore 2007-09-29 03:31:09 UTC
Created attachment 96357 [details] [review]
add revert button

This patch adds a revert button. Pressing this button will ask for confirmation, and then delete all files in |~/.config/autostart| and then refresh the GUI.

If necessary, it could be changed to only delete .desktop files, or perhaps only delete files in the list, etc. but I thought I might keep it simple to start off with. :)
Comment 3 Vincent Untz 2007-09-30 06:35:32 UTC
I don't think "revert" should mean deleting all files in ~/.config/autostart. This would be confusing in most cases, since you usually have files there that might be useful (eg, right now, I have at least 3 or 4 files for programs I added myself).
Comment 4 Jared Moore 2007-09-30 06:55:49 UTC
I think there might be a misunderstanding here. :) 

With the revert button I'm thinking along the lines of "Arghh, I've stuffed everything up, just get me back to default and then I can try to fix it". If you have added programs yourself, then clearly you know _how_ to add those programs, so if you do press revert then it's fairly easy to get back to where you were.

On the other hand, if you're a beginner and started messing around and removed something crucial (like gnome-volume-manager or update-notifier, etc), then it takes quite a bit of effort to figure out how to fix that. In this case, pressing revert is a much easier way of guaranteeing that all your terrible mistakes have been undone. :)

So it's meant to be "revert all changes, ever", not "revert all changes that I just made". 
Comment 5 Vincent Untz 2007-09-30 07:14:22 UTC
So it should be called "Revert to defaults" :-)

This bug is more about the other "Revert", IMHO, and this other "Revert" is probably more important since that's what you usually might want to do.

(and really, we should make it so that people disable a startup program instead of removing it when they don't want it to start - I've the feeling that people might prefer removing them, which creates this issue)
Comment 6 Jared Moore 2007-09-30 07:28:44 UTC
Yes, the confirmation dialog box says "Revert startup programs to original settings?"

When you say 'other revert', do you mean 'revert all changes that I just made'? If so, I don't think that's very useful - if you delete something important without knowing what it was, you probably would not notice until the next time you tried to log in, which would be too late (since you would have closed the window).

Agreed on the disabling :)

Comment 7 Jared Moore 2008-07-04 14:11:28 UTC
Patch is obsolete due to new session-properties codebase.

Anybody have new opinions on my proposed solution? I might be able to cook up a new patch if anyone's interested. :)
Comment 8 Owen Taylor 2008-08-26 17:58:41 UTC
IMO, the first fix is just to make it impossible to remove a system specified startup program ... disabling them is sufficient. If a user added a startup program themselves, they probably can figure out how to add it back. 

I also agree with the original reporter that a confirmation dialog on "Remove" is a good idea, it is a destructive operation.

Various schemes for "Revert" or "Undo" for dialogs have discussed by the UI guys but I don't think anything has been officially blessed. Going off and inventing something and spending a lot of time implementing it seems like unnecesary adventurism for a rather obscure dialog.

Comment 9 William Jon McCann 2008-08-26 18:17:59 UTC
Yeah, I've been bitten by this too.  Owen's recommendations sound good to me.
Comment 10 Ray Strode [halfline] 2008-08-29 21:43:15 UTC
is this bug 333670 rearing its ugly head again?
Comment 11 Owen Taylor 2008-08-30 16:23:52 UTC
Not really ... deleting the system specified startup items works fine:  it writes out a file in the user's dir with hidden=true ... you just don't want to do it.
Comment 12 Lucas Rocha 2009-01-08 10:35:40 UTC
*** Bug 550894 has been marked as a duplicate of this bug. ***
Comment 13 Lucas Rocha 2009-01-09 01:08:49 UTC
*** Bug 557432 has been marked as a duplicate of this bug. ***
Comment 14 Matthias Clasen 2014-03-05 11:39:04 UTC
gnome-session-properties is no longer included in gnome-session.