Intel poulsbo drivers. Unfortunately, also only "sudo kdm start" works.
Any recomended upstart commands just crap out - "sudo service kdm start" or
"start kdm", even though recommended by "sudo /etc/init.d/kdm start" don't work.
--
gdm sometimes fails to start after new upstart merge
https://bug
i'm using nvidia restricted too, the same problem, i have to do ctrl-
alt-f7 to start.
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434361
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in u
My problem seems to be related to: #437067
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434361
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
deskto
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/32480896/dmesg.log
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434361
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ub
still a problem in 2.6.31.11 kernel. I'm using nvidia restricted
drivers.
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434361
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
d
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/32480894/Xorg.0.log
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434361
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in
This also affects KDM,
Boot process will stand in VT1 unless manually starting "sudo kdm start"
** Attachment added: "kdm.log"
http://launchpadlibrarian.net/32480893/kdm.log
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434361
You received this bug n
Mike, I do have a NVidia video card, but please note that I did also try
booting without restricted NVidia drivers, using only the community nv-driver
and the problem did not go away. So I do not think it is a dkms issue.
But reinstalling all kernel packages did fix it for me. Also the warnings a
Here I can't reproduce it anymore.
I know for sure that this bug is usplash related.
I found that workaround few days ago, I just boot the system without 'splash'
argument, and all works just fine.
Now usplash is loaded from initrd, so maybe a kernel update fixed that.
--
gdm sometimes fails to
Problem is back after second reboot.
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434361
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
Wonder if it is a issue with dkms, since people on the forums who had
this problem were all using NVidia video drivers.
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434361
You received this bug notification because you are a member of Ubuntu
Desktop Bugs
Re-installing kernel packages fixed it for me also.
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434361
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing li
@Maxim: Are you still experiencing this bug with the latest updates
installed?
** Changed in: gdm (Ubuntu)
Status: New => Incomplete
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434361
You received this bug notification because you are a member
** Changed in: gdm (Ubuntu)
Status: Confirmed => New
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434361
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs ma
Today I reinstalled all my latest kernel packages (2.6.31-10).
I did this just to make sure it wasn't broken somehow.
You see, everytime x started, I did get a crash report informing of a serious
kernel issue and suggesting a restart.
After that my Karmic started to behave like it should:
booting:
** Changed in: gdm (Ubuntu)
Status: New => Confirmed
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434361
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs ma
My Karmic Ubuntu 64-bit system seems to be affected by this one too.
For me this happens on every boot. It started on 22 September after the updates.
Before that I could always enter xsplash.
Now my Karmic never enters xsplash. Instead after the grub I always get
usplash, with a new look as from t
I have very interesting results.
I found out that in fact, gdm doesn't 'fail to start' in fact it starts just
fine.
What happens is that somebody switches console to VT1.
Then if I switch back to VT7, gdm starts its work, and in few seconds I see
login windows.
--
gdm sometimes fails to start
Yea
Everytime my system boots, I am peresented with console, then I have to log in,
and restart gdm from there
Tommorow I try to see how I could help with that.
Meanwhile this is 90% reproducible
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434
On 09/22/2009 01:31 PM, Sebastien Bacher wrote:
> Robbie, why did you remove the ubuntu-boot tag there? The issue seems a
> upstart boot race one...
>
We're using that tag to track must-fix Beta boot peformance/experience bugs
right now, and while I consider this important...I don't consider must-
On Tue, 2009-09-22 at 11:27 +, Sebastien Bacher wrote:
> Scott, any idea if that's an upstart or gdm issue and how to debug
> those?
>
I don't know how to debug gdm.
First would be to find out why gdm doesn't start, e.g. gdm's logs or X's
logs, and thus find out what it's missing.
Scott
--
Robbie, why did you remove the ubuntu-boot tag there? The issue seems a
upstart boot race one...
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434361
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed t
** Tags removed: ubuntu-boot
--
gdm sometimes fails to start after new upstart merge
https://bugs.launchpad.net/bugs/434361
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.u
Scott, any idea if that's an upstart or gdm issue and how to debug
those?
** Changed in: gdm (Ubuntu)
Importance: Undecided => Medium
** Changed in: gdm (Ubuntu)
Assignee: (unassigned) => Scott James Remnant (scott)
--
gdm sometimes fails to start after new upstart merge
https://bugs.la
24 matches
Mail list logo
