** Tags added: gdm kdm nvidia slim
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at start
https://bugs.launchpad.net/bugs/491483
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I have to report that this bug does also affect other login-managers (well, one
at least: Slim).
And I am using a Nvidia 9500gt video card - not an ATI. So it does not seem to
have much to do with the video card actually.
I had the same problem: After an update with the automated update-manager
If you have both kdm and gdm installed, you have upstart configurations
for both of them:
/etc/init/gdm.conf:
(..)
script
[ ! -f /etc/X11/default-display-manager -o $(cat
/etc/X11/default-display-manager 2/dev/null) = /usr/sbin/gdm ]
(..)
/etc/init/kdm.conf:
(..)
script
[ ! -f
Anyone with 2.6.31-16 installed? And is this problem resolved with it? I
am worried that should we install it or not.
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at start
https://bugs.launchpad.net/bugs/491483
You received this bug notification because
Update: I have updated with 2.6.31-16 by selecting the required
packages. Things are working fine. I still have the 7 packages
downgraded (mentioned above) waiting to be updated. I hope it works for
everyone else.
--
after recent update which included xorg, xserver etc causes low-graphics mode
** Changed in: slim
Status: New = Invalid
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server
Status: Confirmed = Invalid
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at start
Thank you, Urs, for your patch, which works perfectly. Now, can we get
this patch into karmic-updates as soon as possible?
** Changed in: gdm (Ubuntu)
Status: New = Invalid
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at start
This bug affects me and I don't even use KDE, but do use the KDM login manager
over GDM because I like it.
A user called doctordruidphd on the Ubuntu forums has given a workaround that I
have tested to work on several systems I have that are affected.
cd /etc/init
sudo mv failsafe-x.conf
Ok, a comment how I understand this issue:
failsave-x only supports use cases where gdm is not DISABLED. Setups where gdm
is used or isn't installed aren't affected. So...
although I understand that the patch described above works, I get the feeling
this is fixed at the wrong place.
First of
I think another big question is one I try to suggest an answer to, but
am not 100% positive. Why is it tripping into bulletproof X to begin
with? Surely, Bulletproof or failsafe X should be fixed, but it
shouldn't be loading in the first place in this case. As to fixing a
broken X, I'm still used
@Selenia:
what happens:
k/ubuntu boots
upstart finds gdm.conf and tries to start gdm
upstart finds kdm.conf and tries to start kdm
upstart finds failsave-x.conf and tries to start failsave-x
gdm finds out that it's not the chosen WM and fails with exit status 1
kdm finds out that it's the chosen
Seems gdm and kdm have the required sanity checks to not start when not
chosen, but failsafe-x always assumes gdm is chosen, by what you are
saying. It could probably be patched in upstart but likely should really
be fixed in failsafe-x, if this is what is indeed happening. Maybe I'll
break it
@Selenia: Have you looked at the patch provided by Urs Fleisch? It is a
real fix, not a workaround, since it does not break failsafe-x when
using GDM.
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at start
https://bugs.launchpad.net/bugs/491483
You
@Michael (and Urs):
Why don't we just add the check to the failsave-x upstart script? That
seems to be a better way to fix this IMHO, since that's the place where
the bug is.
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at start
So the fix that I'm using, post #30, works because KDM starts faster
because it doesn't have to test drivers?
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at start
https://bugs.launchpad.net/bugs/491483
You received this bug notification because you are
And the Failsave-X scripts are part of the xorg package and not xorg-
server.
** Package changed: xorg-server (Ubuntu) = xorg (Ubuntu)
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at start
https://bugs.launchpad.net/bugs/491483
You received this bug
Here's a debdiff for karmic-proposed that makes the failsave-x upstart task
abort if gdm isn't enabled.
Can you guys test it by editing your /etc/init/failsave-x.conf to look like
this:
start on stopped gdm EXIT_STATUS=[!0]
stop on runlevel [06]
script
[ ! -f
Adding the check to the upstart script seems to be a good idea. I've
created a patch for that. Ideally, the check whether GDM is default
display manager should be in the start on condition, but I don't know
how to do that.
** Attachment added: Patch of the upstart script failsafe-x
Ah, we had t he same idea. :-)
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at start
https://bugs.launchpad.net/bugs/491483
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I too suffered from this issue after the xorg updates in question. My
Toshiba Satellite M45-S265 laptop uses an Intel 915GM graphics card. I
also stopped experiencing this issue when switching to GDM. I reverted
back to the older xorg package versions as mentioned above, which got
rid of the
cd /etc/init
sudo mv failsafe-x.conf failsafe-x.conf-disable
cd /etc/init.d
sudo mv failsafe-x failsafe-x-disable
works for me -- ive been told that this is an issue related to kdm trying to
start before video drivers are loaded: all credit for this workaround goes to
doctordruidphd on
Me too with this issue after xorg update. Here on a ATI Radeon Xpress 1100.
Reverting to older packages resolved the problem. I try again and download the
new packages and the same problem. Using GDM no problem to login. Now I use the
following command proposed at the forum,
Doctordruid's workaround works for me also. I upgraded the packages I
had previously downgraded regarding xorg, etc and performed the steps in
doctordruid's workaround. I rebooted and was able to use kdm with no
problem.
--
after recent update which included xorg, xserver etc causes
Nice! Lots of workarounds for this. Can we get the package updated itself with
possible bugs removed from Ubuntu?
Anyone can help so that this bug reach to them and they can take action for it?
We would love a bug free ubuntu, don't we?
--
after recent update which included xorg, xserver etc
It's a big free kubuntu that I'm after. Ubuntu users are living free
and easy.
It's interesting that this post suggests a timing issue with KDM.
http://ubuntuforums.org/showpost.php?p=8420206postcount=10
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at
This bug looks like a dupe of bug #481514
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at start
https://bugs.launchpad.net/bugs/491483
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Can anyone else confirm that removing package xserver-xorg-video-vesa or
turning off splash fixes this? If not then my bug is different and I
shall file another report.
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at start
setting nosplash nomodeset as kernel arguments did work for me
I've xserver-xorg-video-vesa 1:2.2.1-1
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at start
https://bugs.launchpad.net/bugs/491483
You received this bug notification because you are a
I got KDM back up with x11-common=1:7.4+3ubuntu10. Details below.
Eli, I think it's related to this.
I have an Intel IGP. I managed to get the failsafe X11 up and running
by changing the value for Driver from vesa to intel in the newly
created /etc/X11/xorg.conf.failsafe. I believe that
** Summary changed:
- afte recent update which included xorg, xserver etc causes low-graphics mode
error at start
+ after recent update which included xorg, xserver etc causes low-graphics mode
error at start
--
after recent update which included xorg, xserver etc causes low-graphics mode
I found the following workarounds:
During grub boot (or in /boot/grub/menu.lst) edit the kernel options to include
nosplash nomodeset
There is still an error during X startup but now the Exit to console login
works (consoles are no longer all black).
Also after exiting to the console, sometime
** Description changed:
Binary package hint: xorg
Using Ubuntu/Kubuntu 9.10 on Toshiba Laptop with ATI radeon HD 3650
Today morning I did updated the system with updates available.
Following is the recent log entry in the Software update module in KDE.
Installed: ureadahead,
Same problem here. Kubuntu 9.10, KDE 4.3.4, Nvidia card, nouveau driver.
The x11-common downgrade to 1:7.4+3ubuntu7 did work for me too as a temporary
workaround.
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at start
I'm not sure if this the same bug I'm seeing, but it sounds similar.
Using a Thinkpad T42p with ATI M10 NT/FireGL Mobility T2 chipset.
If I have xserver-xorg-video-vesa installed and splash set in kernel
command line arguments then I will get the Ubuntu is running in low-
graphics mode error
34 matches
Mail list logo
