Failsafe mode uses Ubuntu specific branding unnecessarily

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 if it has reached you inappropriately; please just reply to this message indicating so.]

"[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.

Nonetheless, I've attempted to comply... however intentionally invoking the failsafe mode is rather difficult, especially on Karmic... I will reinstall Jaunty, and try to post a screenshot with the exact dialogs in question, if that will help.

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.

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 respect the distro name listed in /etc/lsb-release.

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.

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 time right now to do a fresh install on a real machine, but if needed, I can do so if someone can give me a better way to force the failsafe mode to come up.

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!

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 be a mistake. If so then the status may be adjusted accordingly and additional documentation may be required.

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.

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 might go about changing this manually to the distro-neutral statement I mentioned in the report? I'd be willing to compile from source and fork the package if need be.

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 instead of apt.log for determining last major upgrade.
  * failsafe-X fixes:
    + Fix broken reconfigure option in failsafe-X scripts. Drop command to
      call Xorg -configure. In addition to not working in this case, when
      it does work it generates a xorg.conf that would never work.
      (LP: #565490)
  * xdiagnose applet fixes:
    + Fix crash with KeyError in run(): 'quiet' by checking key existance
      before deleting.
      (LP: #946836)
    + Fix non-closable error listings window, by converting main window from
      a Dialog to a Window.
      (LP: #941882)
    + Fix ^C in terminal to terminate the program.
    + Fix strings to not refer directly to Ubuntu, so can be more easily
      used in derivatives.
      (LP: #495253)
    + Fix crash about /etc/default/grub being unwritable. Check file
      existance on startup and exit if it isn't present.
      (LP: #946309)
    + Fix test failure in config_update removing a non-existant key.
      Check for it before removal.
 -- Bryce Harrington <email address hidden> Wed, 14 Mar 2012 13:14:31 -0700