Comment 8 for bug 30291

I am also having this problem where the firestarter GUI frontend is not able to start while using sudo. I am running the most recently updated version of Dapper.

If I have no entries for firestarter in my /etc/sudoers file, then I can run "sudo firestarter" and the application starts after asking for my password.

If I have either one of the following entries in my /etc/sudoers file, the application gives me an error when running "sudo firestarter":
%admin ALL=(root)NOPASSWD:/usr/sbin/firestarter
%admin ALL= NOPASSWD: /usr/sbin/firestarter

This is the error I recieve:
    (firestarter:8362): Gtk-WARNING **: cannot open display:

The output of "echo $DISPLAY" is:
    :0.0

The output of "sudo firestarter --display :0.0" is:
    Xlib: connection to ":0.0" refused by server
    Xlib: No protocol specified

    (firestarter:9174): Gtk-WARNING **: cannot open display: :0.0

I had no problems with having Firestarter automatically startup (using the above method) while using Breezy. I get the above errors using an exact replica of my older /etc/sudoers file from my Breezy install. If there is any other information needed to replicate the problem then let me know.