kernel-packages team mailing list archive

[Ron O <ronouel@xxxxxxxxxxx>]

Thanks for the info- I thought the unpopulated list was a bug because 
the procedure you describe is not that self evident. I have never seen 
an unpopulated dropdown list that fills in after you type something into it.

Someone else classified this as medium priority, but it has a lot of 
people confused and in danger of being locked out of their systems. Now 
every time I do an update, I make sure there is no .failsafe file 
reintroduced before I shut down and my system runs fine.


On 12/03/2013 09:43 AM, Quinn Balazs wrote:
> To edit your original post, click the little yellow exclamation point
> above the bug description. To edit the package you have to type a
> package name into the "choose" field, and click the small magnifying
> glass to get a list of all possible packages that include that term.
>
> Generally this issue is caused by a combination of a kernel update and
> your graphics drivers. We'll file this against the "linux" package for
> the time being. Please run "apport-collect 1257085" which will gather a
> bunch of logs and post them attached to this report so that we can get a
> better idea of what's going on here.
>
>
> ** Package changed: ubuntu => linux (Ubuntu)
>
> ** Changed in: linux (Ubuntu)
>         Status: New => Incomplete
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1257058

Title:
  low graphics mode boot error

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 12.04 64 bit with Gnome fallback

  System starts with message the system is running in low graphics mode,
  the desktop does not come up, and the system is locked from all
  further entries.

  After one or more system restarts it boots normally. Problem discussed
  in http://askubuntu.com/questions/141606/how-to-fix-the-system-is-
  running-in-low-graphics-mode-error with several possible solutions.
  One that works is to sudo rm /etc/X11/xorg.conf - as long as this file
  is gone, there are no more boot errors. However this file keeps re-
  appearing and it seems to be re-introduced by the update linux-
  firmware_1.79.9_all.deb.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1257058/+subscriptions