** Branch linked: lp:ubuntu/xdiagnose
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/495253
Title:
Failsafe mode uses Ubuntu specific branding unnecessarily
To manage notifications about this bug
This bug was fixed in the package xdiagnose - 2.2
---
xdiagnose (2.2) precise; urgency=low
* apport hook fixes:
+ Fix tagging of compiz bugs. Only include the tag if we can extract
a valid number from the compiz --version string.
(LP: #927343)
+ Use main.log
** Changed in: xdiagnose (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/495253
Title:
Failsafe mode uses Ubuntu specific branding unnecessarily
To
** Package changed: xorg (Ubuntu) = xdiagnose (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/495253
Title:
Failsafe mode uses Ubuntu specific branding unnecessarily
To manage notifications
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
** Changed in: xorg (Ubuntu)
Importance: Undecided = Wishlist
--
Failsafe mode uses Ubuntu specific branding unnecessarily
https://bugs.launchpad.net/bugs/495253
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Hi twistedlincoln,
Please attach the output of `lspci -vvnn` and `dmesg`, and attach your
/var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this
issue. If you're using a custom /etc/X11/xorg.conf please attach that as well.
[This is an automated message. Apologies
[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.
** 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
** 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 a
** 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
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
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.
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
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
Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Thanks for taking the time to make Ubuntu better!
** Changed in: xorg (Ubuntu)
Thank you for taking the time to report this bug and helping to make
Ubuntu better!
I am going to mark this as confirmed because you attached the
appropriate screenshot documenting the non-generic language of the
failsafe process. I am only a volunteer and I am new to triaging so my
actions may
17 matches
Mail list logo
