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 550140 - Can not add startup application to Startup Programs tab
Can not add startup application to Startup Programs tab
Status: RESOLVED DUPLICATE of bug 549727
Product: gnome-session
Classification: Core
Component: gnome-session
2.23.x
Other All
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-01 00:40 UTC by Dean Loros
Modified: 2008-09-01 12:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Dean Loros 2008-09-01 00:40:42 UTC 
Please describe the problem:
In 'Session Preferences', trying to add an additional startup application, the 'Add Startup Program' responds with 'The startup command cannot be empty' regardless of what is in any of the three input boxes. Even if selected via the 'Browse' button.

Steps to reproduce:
1. Add a new Startup Application
2. Fill in the fields 
3. Click "add"


Actual results:
Response is 'The startup command cannot be empty' even if all fields are filled.

Expected results:
New application added to startup list.

Does this happen every time?
Yes

Other information:
Please see https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/262875

This is happening with Ubuntu Intrepid testing, all current updates done as of this date.
Comment 1 Dean Loros 2008-09-01 00:50:57 UTC 
Also see: http://ubuntuforums.org/showthread.php?t=906701
Comment 2 Olivier Cortes 2008-09-01 07:51:43 UTC 
This bug is a duplicate of an already fixed bug (in SVN) : #549727.  But I can't find how to mark it. Perhaps I don't have enough permissions on this bugzilla.
Comment 3 William Jon McCann 2008-09-01 12:11:01 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 549727 ***