[Ubuntu-x-swat] [Bug 495253] Re: Failsafe mode uses Ubuntu specific branding unnecessarily

2010-08-05 Thread Twisted Lincoln, Inc.
I'm still getting this in Lucid. I don't have a screenshot this time, but the message looks basically identical. If this is to be filed as a "wishlist" item instead of a bug, I assume it likely won't be fixed any time soon. Would someone mind pointing me in the right direction as to where I mig

[Ubuntu-x-swat] [Bug 495253] Re: Failsafe mode uses Ubuntu specific branding unnecessarily

2009-12-11 Thread Twisted Lincoln, Inc.
Sadly, I can't seem to force the failsafe mode in 9.10 in order to post screenshots from it. I tried using the same xorg.conf file, but all I get is a quickly flickering console login prompt, no failsafe menu. I'm not sure if this is because I am running within VirtualBox or not. I don't have t

[Ubuntu-x-swat] [Bug 495253] Re: Failsafe mode uses Ubuntu specific branding unnecessarily

2009-12-11 Thread Twisted Lincoln, Inc.
This was taken from a fresh Ubuntu 9.04 install, having invoked the failsafe mode using the xorg.conf file previously attached. The exact same dialog occurs in Nexradix 1.16 (which is directly based on Ubuntu 9.04, and uses the same Xorg packages), indicating that the failsafe mode does not respec

[Ubuntu-x-swat] [Bug 495253] Re: Failsafe mode uses Ubuntu specific branding unnecessarily

2009-12-11 Thread Twisted Lincoln, Inc.
After hitting "ok" at the first dialog, this menu is presented. It also improperly uses "Ubuntu" rather than the distro name in question, or a distro-neutral statement. ** Attachment added: "Run Ubuntu in low-graphics mode for just one session." http://launchpadlibrarian.net/36702596/run%20ub

[Ubuntu-x-swat] [Bug 495253] Re: Failsafe mode uses Ubuntu specific branding unnecessarily

2009-12-11 Thread Twisted Lincoln, Inc.
Ok, I've attached the requested files after reproducing the issue on Ubuntu 9.04 using VirtualBox. I'll also attach the screenshots of the exact dialogs in question that have the unnecessary branding. -- Failsafe mode uses Ubuntu specific branding unnecessarily https://bugs.launchpad.net/bugs/49

[Ubuntu-x-swat] [Bug 495253] Re: Failsafe mode uses Ubuntu specific branding unnecessarily

2009-12-11 Thread Twisted Lincoln, Inc.
** Attachment added: "Custom /etc/X11/xorg.conf used to invoke failsafe mode in VirtualBox (since no nvidia driver is installed)" http://launchpadlibrarian.net/36702509/xorg.conf -- Failsafe mode uses Ubuntu specific branding unnecessarily https://bugs.launchpad.net/bugs/495253 You received

[Ubuntu-x-swat] [Bug 495253] Re: Failsafe mode uses Ubuntu specific branding unnecessarily

2009-12-11 Thread Twisted Lincoln, Inc.
** Attachment added: "/var/log/Xorg.0.log from Ubuntu 9.04 (jaunty) running in VirtualBox" http://launchpadlibrarian.net/36702494/Xorg.0.log -- Failsafe mode uses Ubuntu specific branding unnecessarily https://bugs.launchpad.net/bugs/495253 You received this bug notification because you are

[Ubuntu-x-swat] [Bug 495253] Re: Failsafe mode uses Ubuntu specific branding unnecessarily

2009-12-11 Thread Twisted Lincoln, Inc.
** Attachment added: "lspci -vvnn from Ubuntu 9.04 (Jaunty) running in VirtualBox" http://launchpadlibrarian.net/36702473/lspci.txt -- Failsafe mode uses Ubuntu specific branding unnecessarily https://bugs.launchpad.net/bugs/495253 You received this bug notification because you are a member

[Ubuntu-x-swat] [Bug 495253] Re: Failsafe mode uses Ubuntu specific branding unnecessarily

2009-12-11 Thread Twisted Lincoln, Inc.
"[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]" I'm not sure how any of those logs have any relevance to this issue. The concern isn't how failsafe mode comes to be started, but instead what is displayed once it is

[Ubuntu-x-swat] [Bug 495253] [NEW] Failsafe mode uses Ubuntu specific branding unnecessarily

2009-12-10 Thread Twisted Lincoln, Inc.
Public bug reported: Binary package hint: xorg The failsafe mode currenty greets the user with "Ubuntu is running in low graphics mode," and offers the user options on how to proceed. These dialogs all specifically reference "Ubuntu," rather than the distro name noted in /etc/lsb-release. This m