Re: No protocol specified, cannot open display error
On Sat, May 30, 2009 at 5:28 PM, Lorenzolory.fu...@infinito.it wrote: Well, googling no protocol specified cannot open display gave me a hint: are you trying to run gedit with root privilege, as in sudo gedit /etc/apt/sources.list (or /boot/grub/menu.lst or whatever)? If that's the case, you can: 1) try some of the solutions that google suggests 2) use kdesu/kdesudo, they are made specifically for the case where you need to use a program with a gui AND be root; in gnome they are called gtksu/gtksudo, but they do exactly the same thing Hope it helps... Hi, Thanks for the help! I don't try to run programs as root. This even happens as a regular user. That being said I must note that this problem hasn't happened in a while. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
No protocol specified, cannot open display error
Hi, After an certain amount of time applications no longer open on my Gnome desktop, When I try to run a program from an already opened terminal I get the following output: $ gedit No protocol specified cannot open display: When I log out and in the problem is solved. Is this a know bug in Lenny? Is there a workaround? Regards, Aniruddha -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: No protocol specified, cannot open display error
Aniruddha ha scritto: Hi, After an certain amount of time applications no longer open on my Gnome desktop, When I try to run a program from an already opened terminal I get the following output: $ gedit No protocol specified cannot open display: When I log out and in the problem is solved. Is this a know bug in Lenny? Is there a workaround? Regards, Aniruddha Never seen this on lenny, but given the error message - next time it doesn't work, can you post the value of your $DISPLAY? ifnewbie type ECHO $DISPLAY in your terminal /ifnewbie If it's not :0.0, that's most likely the problem (but I have no idea why logging out should solve the issue) good luck -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
