ubuntu-x-swat team mailing list archive
-
ubuntu-x-swat team
-
Mailing list archive
-
Message #30427
[Bug 457443] Re: X fails in virtualbox post jaunty->karmic upgrade
So the cause is pretty clear:
(II) LoadModule: "vboxvideo"
(WW) Warning, couldn't open module vboxvideo
(II) UnloadModule: "vboxvideo"
(EE) Failed to load module "vboxvideo" (module does not exist, 0)
(EE) No drivers available.
In earlier times, gdm/X.org used to have a fallback mechanism to VESA.
Perhaps it should just entirely ignore xorg.conf if it is faulty? Bryce,
do you think the latter option would be suitable, also for upstream?
** Changed in: xorg (Ubuntu)
Importance: Undecided => Medium
** Changed in: xorg (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) => Bryce (bryce)
** Changed in: xorg (Ubuntu)
Status: Confirmed => Triaged
** Changed in: xorg (Ubuntu)
Assignee: Bryce (bryce) => Bryce Harrington (bryceharrington)
** Summary changed:
- X fails in virtualbox post jaunty->karmic upgrade
+ No "safe" fallback on broken xorg.conf
** Summary changed:
- No "safe" fallback on broken xorg.conf
+ No "safe" fallback on broken xorg.conf or missing driver
--
No "safe" fallback on broken xorg.conf or missing driver
https://bugs.launchpad.net/bugs/457443
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
Follow ups
References