Ubuntu
xorg package

bulletproof-x hiding real problems

Bug #148122 reported by Hervé Cauwelier
2
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Binary package hint: displayconfig-gtk

(I chose the package I know but this is related to the failsafe X feature.)

I just modified my X configuration, restarted, and saw displayconfig-gtk instead of GDM.

I switched back to console, stopped GDM, cleaned up the xorg.conf, restarted GDM... still displayconfig-gtk appearing.

I was a bit upset because I reverted all my changes and I thought I restored a functional version.

I then remembered looking at the Xorg.0.log would be a good idea... I figured out it was moved to Xorg.0.log.old.

I read there that there was a simple syntax error in my file, a "EndSction" without the "e".

Here is my report: displayconfig-gtk (or the failsafe X) is hiding the error message we had before.
I would prefer some dialog window open up above displayconfig-gtk to report *why* the user see this screen.
I would then have fixed the error at once.

Please report some dialog like :

"The graphical interface failed to start because of the following error:

XXX (the errors from X log)

Please check the configuration and validate to continue."

Related branches

lp:ubuntu/lucid/xorg
Revision history for this message
Bryce Harrington (bryce) wrote :

Good idea to implement for Hardy.

For Gutsy, we'll switch the bulletproof-x display to :10, which should be a safe change even at this late date, and should allow experienced users the ability to go to the failed X screen and read the original message.

Changed in displayconfig-gtk:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Hervé Cauwelier (hcauwelier-deactivatedaccount) wrote :

Thank you for considering my thoughts.

This is a nice compromise given the little time left... But then can your insert at the bottom of the screen (or dc-gtk's window) a message like "You can see the error message by typing Alt+F7. Switch back to this screen by typing Alt+F10" ?

Thanks again.

Revision history for this message
Sebastian Heinlein (glatzor) wrote :

You won't see the log files on the 7th terminal. Furthermore the fail safe x server won't run on the 10th terminal. The :10 is just another identifier for the fail safe x server, so it won't touch the Xorg.0.log. Advanced error location methods should be part of the documentation and not of the default user interface.

Revision history for this message
Bryce Harrington (bryce) wrote :

With the new failsafe-X dialogs, I've included some code to make it print the error messages right on the initial dialog, if any errors are present.

Also, there is now an option in the new failsafeX code to display and/or save the Xorg.0.log file if the user wishes to investigate more deeply.

Changed in xorg:
status: Triaged → Fix Released
status: Fix Released → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xorg - 1:7.4~2ubuntu4

---------------
xorg (1:7.4~2ubuntu4) intrepid; urgency=low

  * local/Failsafe/failsafeXServer:
    - 'discover' is no longer used, so disable the pci-id based detection
      of alternate fallback driver. (LP: #272086)
    - Add detection of ppc hardware and prefer 'fbdev' instead of 'vesa'
      in this case (LP: #155685)
    - Send log to Xorg.failsafe.log when in failsafe mode (LP: #179164)
  * local/Failsafe/failsafeDexconf:
    - Re-sync with dexconf; use input-hotplug for devices. (LP: #227818)
  * local/Failsafe/failsafeXinit:
    - Display the X errors on initial dialog. (LP: #148122)
    - Specify /etc/X11/xorg.conf exactly, rather than $xorg_conf, which
      actually points to xorg.conf.failsafe
  * local/dexconf:
    - Remove duplicate line if generating an xorg.conf for KVM sessions
    - Note that some settings can't be set in xorg.conf any longer
      (LP: #263124)

 -- Bryce Harrington <email address hidden> Fri, 19 Sep 2008 21:08:52 -0700

Changed in xorg:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.