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 168722 - Issue launching from Gnome Sessions Startup
Issue launching from Gnome Sessions Startup
Status: RESOLVED INCOMPLETE
Product: firestarter
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Tomas Junnonen
Tomas Junnonen
Depends on:
Blocks: 338159
 
 
Reported: 2005-02-28 03:52 UTC by Pablo Pérez Benítez
Modified: 2011-01-27 05:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description Pablo Pérez Benítez 2005-02-28 03:52:13 UTC 
Version details: 1.0.3

I couldn't get Firestarter being launched (minimized) by Gnome Sessions after
following the instructions in the online manual.

Gnome's Current Sessions lists Firestarter as launching state or with a life
preserver state icon (which I don't know the meaning here).

sudo firestarter --start-hidden does work (only?) from the gnome-terminal.

To enable Firestarter to be launched with sudo I added to the /etc/sudoers this:
 myuser ALL=NOPASSWD: /usr/sbin/firestarter
In the online manual the former path is mistyped(?) as /usr/bin/firestarter

I am using Firestarter 1.0.3 in Debian Sid and Gnome 2.8.1
Comment 1 Lonnie Best 2007-05-08 04:06:18 UTC 
There seems to be a bug in /etc/sudoers. I've written an article that describes a work around:
http://www.howtoadvice.com/AutoFirestarter/

Ultimately, we should lobby for Firestarter's development team to abstract our desired behavior (of launching the Firestarter status icon upon login) to a check box in its preferences menu.

Lonnie Lee Best
Comment 2 Fabio Durán Verdugo 2010-12-13 02:53:11 UTC 
This bug was reported against a version which is not supported any more. Developers are no longer working on this version so there will not be any bug fixes for it.
Can you please check again if the issue you reported here still happens in a recent version of GNOME and update this report by adding a comment and adjusting the 'Version' field?

Again thank you for reporting this and sorry that it could not be fixed for the version you originally used here.

Without feedback this report will be closed as INCOMPLETE after 6 weeks.