We're not going to fix this issue for karmic or lucid since we don't
want to risk regressing anyone, but going forward the plan is to move
failsafe-x into a separate package called xdiagnose.
** Changed in: gdm-2.20 (Ubuntu)
Status: New = Won't Fix
** Changed in: gdm-2.20 (Ubuntu Karmic)
This bug still re-appears in lucid. The underlying problem seems to be
that /etc/init.d/failsafe-x.conf is in the wrong package. x11-common
should know nothing about gdm and yet here is a gdm referencing file, so
as soon as you stop using gdm 2.3, the system is broken. This file
should be in the
** Tags added: regression-update
** Tags removed: regression-updates
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.net/bugs/491483
Title:
Since failsafe-x was enabled in karmic it starts if
On
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
https://bugs.launchpad.net/bugs/491483
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs
I don't use gdm, and hit this bug. I was able to make the dialog go away by
moving these files out of /etc/init:
gdm.conf failsafe-x.conf plymouth* usplash.conf
I'm sure I didn't need to eliminate all of those, but just failsafe-x.conf
alone didn't do it so I cast a wider net.
--
Since
** Branch linked: lp:ubuntu/gdm
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
https://bugs.launchpad.net/bugs/491483
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm
** Branch linked: lp:ubuntu/karmic-updates/gdm
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
https://bugs.launchpad.net/bugs/491483
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Xubuntu 9.10 user with ONLY gdm xfce installed, and 6hrs of his life
he will never get back. Rant follows, solution at end:
Boy did this ruin and waste my entire day. I had to reboot to get ALSA
backports because the mic on my 3810T is broken with karmic, and
actually even with backports it's
This bug affects my multiseat system with Karmic. I am using just gdm
and due to the latest gdm doesn't support multiseat I had to downgrade
to gdm 2.20. When my X is starting, there are some error messages in the
xorg.log which do not affect any functionality as far as I can say
(II) config/hal:
Just one more comment, if this bug was fixed in latest gdm, to allow
people who use multiseat system to take advantages of this fix, it would
be nice if can be backported to gdm 2.20.
** Tags added: multiseat
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
Yes, there is a task open on this bug report for the gdm-2.20 package,
but it doesn't appear that anyone has taken responsibility yet for
fixing the bug there.
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
Just saying that comment #32 solves this problem for anyone using
gdm-2.20 also.
** Also affects: gdm-2.20 (Ubuntu)
Importance: Undecided
Status: New
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
Upgraded a Dell laptop Ubuntu 8.04 - 8.10 - 9.04 - 9.10. The last
upgrade introduced a problem: upon boot there is a popup (of which only
the top is visible, the rest is below the bottom edge of the screen)
telling me Ubuntu running in low-graphics mode. Upon ^C I get a
console prompt, and startx
I am aware of this; I know the details of this problem, having
discovered it independently in the days I spent figuring out why Ubuntu
failed to boot on my laptop into either X or single-user mode.
If kdm was used, then this bug also occurred in single-user mode because
the configuration check
I'd really like to purge my systems of this failsafe-x nonsense. Is
there documentation some where that explain how to disable the
ironically named program? When I was bit by this bug, I didn't have
access to another computer to search for a solution. I didn't have a
console to read the logs.
This bug was fixed in the package gdm - 2.28.1-0ubuntu2.1
---
gdm (2.28.1-0ubuntu2.1) karmic-proposed; urgency=low
* debian/gdm.upstart: Do not fail with exit status !=0 on startup
when disabled. LP: #491483
-- Philip Muskovac yo...@gmx.net Mon, 07 Dec 2009 16:30:05 +0100
Can someone tells to people like me that does not have gdm installed at
all, but only kdm, how they can have this bug fixed? We opened a new bug
but we ended up dupe of this.
However I do not see kdm here involved in the patching.
** Also affects: kdebase-workspace (Ubuntu)
Importance:
This bug also affected single-user mode. While it no longer occurs after
the fix, the script for failsafe-x should be disabled when booting with
kernel option single. It is otherwise extremely ironic that this so-
called failsafe-x has the potential to (and in fact did) cause the real
failsafe
Actually, can failsafe-x be set up to never run unless starting-dm has been
emitted? I see a
initctl emit starting-dm DM=kdm
and a similar line in gdm.conf. I don't know how upstart works, but presumably
one can configure it to only consider running if starting-dm has occurred. That
seems
If you don't have gdm installed, you don't have this bug. The
failsafe-X job is only ever run when gdm tries to run and fails.
I've reviewed the set of bugs marked as duplicates of this one, and un-
duped those that don't match - including bug #459639, which appears to
be the one under
This bug also affected single-user mode.
It affected only systems that had both kdm and gdm installed, with kdm
configured as the preferred DM. Users with only gdm installed were not
affected by this bug, with or without booting in single-user mode,
because the gdm job already exits '0' if it
** Changed in: gdm (Ubuntu Karmic)
Status: Fix Committed = Fix Released
** Changed in: gdm (Ubuntu Karmic)
Status: Fix Released = Fix Committed
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
I'm waiting for 3 weeks for a patch for my Laptop(Intel), my home
PC(NVIDIA) and my PC at work(NVIDIA). What a shame that such things
could happen. It cost me so much time. Is Karmic a beta? When will the
repositories be updatet?
--
Since failsafe-x was enabled in karmic it starts if gdm is
dm [2009-12-08 10:33 -]:
When will the repositories be updatet?
It will move to -updates when the package in -proposed got confirmed
to work.
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
I have activated 'proposed' in sources.list.
deb http://archive.ubuntu.com/ubuntu/ karmic-proposed restricted main
multiverse universe
But I can't see the 'gdm (2.29.1-0ubuntu3)'
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
Sorry, the package had a bad version number; I uploaded
2.28.1-0ubuntu2.1 to karmic-proposed now.
But I can't see the 'gdm (2.29.1-0ubuntu3)'
That's the version for lucid, not for karmic.
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics
This bug affects only KDM (Kubuntu) users, why is not mentioned in the
above list?
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
https://bugs.launchpad.net/bugs/491483
You received this bug notification because you are a member
s/only/also
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
https://bugs.launchpad.net/bugs/491483
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
Surprise, with the new GDM package I have a usable notebook again. It
seems, the patch does what it should. Thank you for all the help. But I
think, such a bug should be found before so many users get an unusable
system.
Thanks
DM
--
Since failsafe-x was enabled in karmic it starts if gdm is
** Tags added: verification-done
** Tags removed: verification-needed
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
https://bugs.launchpad.net/bugs/491483
You received this bug notification because you are a member of Ubuntu
I also have just tried out the proposed gdm fix and am all up and
running again. Thanks to all who have helped with this one. My
situation was Ubuntu install where I added kubuntu-desktop and chose
kdm, hence gdm and kdm co-resident. As laptop had intel graphics I got
as others with intel
I feel Steve Langasek's opinion makes sense (post #54). GDM should not
exit with non zero stauts when it is disabled. If it exits with 0 then
failsafe-x will not start and we won't have issue with KDM.
If GDM is disabled or loaded correctly the failsafe-x should not start.
I know I am mixing
** Changed in: gdm (Ubuntu)
Status: Invalid = Triaged
** Changed in: xorg (Ubuntu)
Status: Confirmed = Invalid
** Also affects: gdm (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: xorg (Ubuntu Karmic)
Importance: Undecided
Status: New
**
After analyzing the complete issue, I do not understand how this update
was released without realizing the various kinds of (kde, gdm, xdm etc)
users. :(
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
Debdiff for lucid with the fix from Steve. It works fine here.
** Attachment added: gdm_2.29.1-0ubuntu3.debdiff
http://launchpadlibrarian.net/36537002/gdm_2.29.1-0ubuntu3.debdiff
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode
Debdiff for karmic-proposed
** Attachment added: gdm_2.28.1-0ubuntu3.debdiff
http://launchpadlibrarian.net/36537015/gdm_2.28.1-0ubuntu3.debdiff
** Attachment removed: xorg_7.4+3ubuntu11.debdiff
http://launchpadlibrarian.net/36504330/xorg_7.4%2B3ubuntu11.debdiff
--
Since failsafe-x was
Although the proposed patch will fix this, it isn't the best approach.
The failsafeXServer script should be split off from gdm, made its own package,
and should be aware of all possible login managers.
The man page init(5) has a lovely example:
stop on stopping gdm or stopping kdm
What's
Hmmm, in fact I see that the various failsafe* files are part of the
x11-common package, not of
gdm. The simple fact that x11-common is laying files down in directory
/etc/gdm is a warning
flag (I'm mildly surprised that `lintian` doesn't complain about it).
--
Since failsafe-x was enabled in
@Bela: I completely agree with you that this isn't the best solution.
But we should at least upload the existing fix/workaround now to fix the
regression and then maybe open another bug about adding other DM support
to failsave-x in lucid.
--
Since failsafe-x was enabled in karmic it starts if
** Branch linked: lp:~ubuntu-desktop/gdm/ubuntu
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
https://bugs.launchpad.net/bugs/491483
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Accepted gdm into karmic-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: regression-updates
**
I had success with Philip's gdm patch! kdm[1064]: X server died during
startup and kdm[1064]: Failed to start X server. Starting failsafe X
server. are not to be found in the syslog.
PLEASE refactor this upstart sprawl. This was a very painful bug for
me. As an Intel IGP owner, I wasn't even
This bug was fixed in the package gdm - 2.29.1-0ubuntu3
---
gdm (2.29.1-0ubuntu3) lucid; urgency=low
* debian/gdm.upstart: Do not fail with exit status !=0 on startup
when disabled. LP: #491483
-- Philip Muskovac yo...@gmx.net Mon, 07 Dec 2009 19:33:05 +0100
** Changed in:
Please disregard the packages in my PPA and use the official proposed
packages. Martin Pitt beat me by a minute.
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
https://bugs.launchpad.net/bugs/491483
You received this bug
Hi ! (sorry for my bad english)
sorry I don't read all answer...
your problem is a same of that =
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/459639
?
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
No, you say in post #13 there that you do NOT have gdm installed, this
bug is about failsave-x launching while gdm is installed.
On 12/08/2009 12:03 AM, jajaX wrote:
Hi ! (sorry for my bad english)
sorry I don't read all answer...
your problem is a same of that =
Is the official update out? Or I need to wait for a while? I know I can
take it from proposed but still would prefer from the official updates.
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
@Philip Muskovac: What you mentioned in post #66, I would like to get
updates on the same. As I also agree with Bela as the failsafe-x should
be aware of all the DMs installed on the system. Could you please let
me/us know if some different bug is opened to resolve the same.
--
Since failsafe-x
Manish,
we need to test it from -proposed first and ensure that the update does
not cause regressions and fixes the problem. So any help with that and
feedback is appreciated. Thank you!
** Changed in: gdm (Ubuntu Karmic)
Importance: Undecided = High
--
Since failsafe-x was enabled in
49 matches
Mail list logo
