Gil Cara [2009-12-19 1:23 -]:
> W: Some index files failed to download, they have been ignored, or old ones
> used instead.
> Is this a bug, Because i can't upgrade my obuntu. What shal i do?
Just try again a bit later, you might just have hit a bad time on your
mirror.
--
upstart job keep
W: A error occurred during the signature verification. The repository is
not updated and the previous index files will be used.GPG error:
http://ph.archive.ubuntu.com hardy-updates Release: The following
signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive
Automatic Signing Key
W: Fail
Argyle: first of all it may help if you read the thread, as I have
described the solution further up!;)
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm
I still have this problem. Is it supposed to be fixed? What do I do?
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mai
Bug #475259 can't be exposed on a system whose X server is working, no;
and I don't think that bug should block the -updates migration - but I
was intimately involved in preparing the SRU, so I was giving you all
the information I had in order to let you make your own judgement call
here.
--
upst
I'm not sure what to do with the xorg proposed update now. Bug 475259
wasn't introduced by the xorg/gdm changes, but I don't understand how it
can suddenly be exposed on a system which previously had a correct
xorg.conf/drivers.
Some insight as to whether this should block the -updates migration
w
This bug was fixed in the package gdm - 2.28.1-0ubuntu2
---
gdm (2.28.1-0ubuntu2) karmic-proposed; urgency=low
* Don't respawn gdm on failure; this lets us capture X failures instead and
trigger the bulletproof X handler here. LP: #441638.
* re-export any XORGCONFIG value pas
It would be great to see this pushed out, this issue is making it
difficult for users to troubleshoot underlying X issues...
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Tags added: iso-testing
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
http
firebird wrote:
>I have now completely emptied /etc/X11/xorg.conf and voila, it works!
This fixed it for me.
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
That bug appears to be a problem with failsafe X not working correctly
on the user's system, but there's no information there about why gdm is
failing in the first place. I think this needs to be triaged further
before concluding that we shouldn't proceed with this SRU (OTOH, we also
shouldn't pub
bug #476874 is an user stating the upgrade broke things
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
deskt
A latter bug was found in getting the failsafe session up, since dexconf
no longer generates xorg.conf's, it also can't be used to generate the
failsafe mode's xorg.conf. I've uploaded a change which just generates
a standard xorg.conf (this is pretty much all dexconf was doing last
release anyway
** Tags added: verification-done
** Tags removed: verification-needed
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mail
Yep, the blinking is fixed for me on a fresh install of Karmic server (I
wanted RAID6 support at install) with ubuntu-desktop installed. The gdm
package gets my OK for moving to updates. 'cause, you know, I know you
were waiting for /my/ OK, right? =)
--
upstart job keeps restarting a dying gdm
Hi guys!
I guess what Bryce Harrington required from me is then obsolete?
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs
In my case the nvidia kernel module was not built correctly built (it
was resolved a day later) causing this problem.
It is simple to reproduce just create a bad xorg.conf, this can be done
by making a spelling mistake, having the wrong driver ie the nvidia
driver marked in the xorg.conf when the
** Changed in: gdm (Ubuntu Karmic)
Assignee: Martin Pitt (pitti) => Steve Langasek (vorlon)
** Changed in: gdm (Ubuntu)
Assignee: Martin Pitt (pitti) => Steve Langasek (vorlon)
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this bug noti
** Branch linked: lp:~ubuntu-desktop/gdm/ubuntu
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@
> I realized by connecting to the machine via ssh that actually everything is
> running, ie. GDM, X, Pulse, whatever you just don't get to see anything which
> is due to a completely out of range resolution of horizontal 268kHz, vertical
> 281Hz.
> I have now completely emptied /etc/X11/xorg.con
** Changed in: gdm (Ubuntu)
Milestone: karmic-updates => None
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing
Ladies and gentlemen here comes the solution:
I realized by connecting to the machine via ssh that actually everything is
running, ie. GDM, X, Pulse, whatever you just don't get to see anything which
is due to a completely out of range resolution of horizontal 268kHz, vertical
281Hz.
I have now
Ok guys, here's the deal:
Not only GDM is not starting but also TTY1-TTY7 are being terminated, and that
before GDM is attempted to be started.
Of course GDM cannot start if there is no TTY available.
Further this problem occurs only with kernel 2.6.31-14
kernel 2.6.28-15 boots perfectly!
Btw. t
** Changed in: gdm (Ubuntu Karmic)
Status: Triaged => In Progress
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs m
And yes, dropping 'respawn' from the job is enough to stop the job from
being respawned by upstart.
I think the only justification for setting respawn is that, even though
it's not the upstart default, it's a sensible default policy for
services. So if it's not working for any reason, by all mean
On Tue, Oct 27, 2009 at 10:12:24PM -, dns_server wrote:
> gdm is not starting x we have xsplash now.
Incorrect. gdm is still the service that starts X, xsplash is launched from
there.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer
gdm is not starting x we have xsplash now.
does xsplash have the same logic that gdm did and dump back to a failsafe.
it seems that xsplash is crashing and upstart is respawning it as it crashes.
--
upstart job keeps restarting a dying gdm
https://bugs.launchpad.net/bugs/441638
You received this
Scott, is there a particular reason why you made the gdm upstart job
respawning? It already has its own logic to respawn on a crashing X
server (or if an X session terminates normally). If gdm itself is
crashing, then restarting it over and over does not make much sense
either.
Any objections in m
28 matches
Mail list logo
