Bug#504239: grub-choose-default: fails with message No protocol specified
On Sun, Nov 2, 2008 at 9:24 AM, Kjell Braden [EMAIL PROTECTED] wrote: This looks like your shell's environment is not allowed to connect to your display (ie. $DISPLAY and $XAUTHORITY are not set correctly). How exactly did you run grub-choose-default? The canonical way to do this would be starting via su-to-root -c grub-choose-default or similar (sudo, kdesudo, gksu), which would preserve most of the environment. I can no longer reproduce this behavior. The window appears when I try it now. I see no reason to keep the issue open. I have invoked it (both before and now) by using su in konsole to get to root and then issue the command. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#504239: grub-choose-default: fails with message No protocol specified
On Sun, Nov 2, 2008 at 9:24 AM, Kjell Braden [EMAIL PROTECTED] wrote: This looks like your shell's environment is not allowed to connect to your display (ie. $DISPLAY and $XAUTHORITY are not set correctly). How exactly did you run grub-choose-default? The canonical way to do this would be starting via su-to-root -c grub-choose-default or similar (sudo, kdesudo, gksu), which would preserve most of the environment. I can no longer reproduce this behavior. The window appears when I try it now. I see no reason to keep the issue open. I have invoked it (both before and now) by using su in konsole to get to root and then issue the command. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#504239: grub-choose-default: fails with message No protocol specified
John Marter schrieb: Package: grub-choose-default Version: 0.2-6 Severity: normal When I run grub-choose-default as root I get the following output instead of a menu # grub-choose-default Using /boot/grub/menu.lst and /boot/grub/default Getting entries Getting default Creating window, might take a second No protocol specified Traceback (most recent call last): File /usr/sbin/grub-choose-default, line 325, in module tk_root = Tk() File /usr/lib/python2.5/lib-tk/Tkinter.py, line 1650, in __init__ self.tk = _tkinter.create(screenName, baseName, className, interactive, wantobjects, useTk, sync, use) _tkinter.TclError: couldn't connect to display :0 This looks like your shell's environment is not allowed to connect to your display (ie. $DISPLAY and $XAUTHORITY are not set correctly). How exactly did you run grub-choose-default? The canonical way to do this would be starting via su-to-root -c grub-choose-default or similar (sudo, kdesudo, gksu), which would preserve most of the environment. signature.asc Description: OpenPGP digital signature
Bug#504239: grub-choose-default: fails with message No protocol specified
Package: grub-choose-default Version: 0.2-6 Severity: normal When I run grub-choose-default as root I get the following output instead of a menu # grub-choose-default Using /boot/grub/menu.lst and /boot/grub/default Getting entries Getting default Creating window, might take a second No protocol specified Traceback (most recent call last): File /usr/sbin/grub-choose-default, line 325, in module tk_root = Tk() File /usr/lib/python2.5/lib-tk/Tkinter.py, line 1650, in __init__ self.tk = _tkinter.create(screenName, baseName, className, interactive, wantobjects, useTk, sync, use) _tkinter.TclError: couldn't connect to display :0 -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages grub-choose-default depends on: ii grub-pc [grub] 1.96+20080724-10 GRand Unified Bootloader, version ii menu2.1.40 generates programs menu for all me ii python 2.5.2-2 An interactive high-level object-o ii python-tk 2.5.2-1 Tkinter - Writing Tk applications grub-choose-default recommends no packages. grub-choose-default suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
