On 10/01/2010 06:38 PM, Martin Pitt wrote:
> Jamie Krug [2010-09-23 18:47 -]:
>
>> Based on my previous comment (#79), I'm curious whether you think this
>> bug is still relevant or whether I should be opening a new bug (I'm
>> guessing the latter).
>>
> Yes, it indeed sounds as if you
Jamie Krug [2010-09-23 18:47 -]:
> Based on my previous comment (#79), I'm curious whether you think this
> bug is still relevant or whether I should be opening a new bug (I'm
> guessing the latter).
Yes, it indeed sounds as if you have an unrelated problem then.
Thanks!
--
gdm/kdm starting
Adding kdebase-workspace task for kdm.
** Also affects: kdebase-workspace (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- gdm starting too early for DRM modules to load, no video
+ gdm/kdm starting too early for DRM modules to load, no video
** Changed in: kdebase-wor
Unfortunately it is not that well-defined. This is mainly a race
condition between loading DRM modules (such as nvidia) and gdm starting
up. So this should mainly be tested by people who are affected by this
bug, i. e. they do not get X start up, or with only the framebuffer
driver (meaning no 3D a
Shouldn't SRUs have a well-defined test case?
--
gdm starting too early for DRM modules to load, no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
** Branch linked: lp:ubuntu/lucid-proposed/gdm
--
gdm starting too early for DRM modules to load, no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Accepted gdm into lucid-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!
** Changed in: gdm (Ubuntu Lucid)
Sta
Martin,
Based on my previous comment (#79), I'm curious whether you think this
bug is still relevant or whether I should be opening a new bug (I'm
guessing the latter). I've further confirmed the battery power
relationship by working for a few hours with AC power plugged in and now
crash, then lat
I have some new clues on my crashes! First, Martin's changes to my
gdm.conf as mentioned in comment #67 did not fix all for me, as I just
had a few more crashes. What I noticed (and had a hunch this morning
too), is that I believe I've primarily (if not always) had crashes occur
while on battery po
@John
> Do you remember if you are typing anything when they happen? Anything
> else you can remember about the circumstances? You mentioned above a
> resume, is that always or usually involved?
I'm fairly certain I was *not* typing anything, but usually had just
clicked something (e.g., a link).
Seth:
> Include
>
> ps -ef | grep X
> gdmtty="$(ps --no-heading -o tty -p $(pgrep X))"
> stty -F "/dev/$gdmtty"
> ps -f -t "$gdmtty"
I rebooted, switched to tty1 and I'm attaching the output from the
above. Thanks.
** Attachment added: "out_20100922-1156.tgz"
https://bugs.launchpad.net/ubunt
Martin:
> by looking at "glxinfo" or just the X server look it should
> be possible to detect this situation right after boot.
Sorry, I'm not entirely sure what to look for, but I've attached the
output from a glxinfo command just after boot/login.
** Attachment added: "glxinfo.out"
https://b
@Jamie
I think the fact that you haven't been getting VT1 starts confirms that
the /etc/init/gdm.conf fix is effective.
Those logs look like the ones you posted in comment #69 and comment #98
of bug #625239. You are running on a good virtual terminal rather than
VT1 or VT2 and you get just the he
On 09/22/2010 04:10 PM, Jamie Krug wrote:
> Martin:
>
>> Crashes which happen during the running GNOME/KDE session are
>> unrelated to this.
>>
> Interesting. After sharing extensive results in bug #625239, it seemed
> quite clear that my issue related to the correct bug and that #625239
>
Jamie,
well, it could be that you actually only get a crash later on, when
gdm starts X.org on the framebuffer driver, and nvidia (or fglrx,
etc.) only gets loaded later on. So it would crash when you try to
start a 3D application, etc.
However, by looking at "glxinfo" or just the X server look i
Martin:
> Crashes which happen during the running GNOME/KDE session are
> unrelated to this.
Interesting. After sharing extensive results in bug #625239, it seemed
quite clear that my issue related to the correct bug and that #625239
was a duplicate of this one (and has been marked as such). Am I
Jamie Krug [2010-09-22 13:31 -]:
> The crashes don't always occur right after reboot.
Any effect which is related to the gdm.conf start condition _is_
related to boot. I. e. if gdm starts too early, then you will not get
a graphical environment at all, or a very poor one (no acceleration,
etc
Martin,
As you suggested, I've changed to this in my gdm.conf:
start on (filesystem
and started dbus
and stopped udevtrigger)
I will run with this for normal use and report back in a few days, or
whenever a crash might occur (hopefully none!). I can also do 20 reboots
in a ro
Seth [2010-09-22 8:00 -]:
> On Lucid or on Maverick?
Doesn't matter really.
--
gdm starting too early for DRM modules to load, no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
On 09/22/2010 08:45 AM, Martin Pitt wrote:
> Yes, changing gdm.conf is all that the proposed SRU will do as well.
>
> Can you please change this to
>
> start on (filesystem
> and started dbus
> and stopped udevtrigger)
>
> and run with that for a few days? Perhaps also do 20 reb
Yes, changing gdm.conf is all that the proposed SRU will do as well.
Can you please change this to
start on (filesystem
and started dbus
and stopped udevtrigger)
and run with that for a few days? Perhaps also do 20 reboots in a row if
you can? Does that make a difference?
--
As I mentioned in my previous comment, I had another GDM crash right
after a reboot. The logs for this one are attached here. Please let me
know if there's anything else I can provide. Thanks.
** Attachment added: "logs_20100921-2053.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/6
The patch from comment #64 does not entirely fix this issue for me on
Lucid, although it has certainly improved things. I looked at the patch
and changed my /etc/init/gdm.conf file accordingly (hopefully that's all
I was supposed to do?). My gdm.conf is included with the archive
attached to this co
SRU patch: http://bazaar.launchpad.net/~ubuntu-
desktop/gdm/lucid/revision/251
(Cherrypicked from packaging trunk)
--
gdm starting too early for DRM modules to load, no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Bugs, which
Lucid SRU uploaded. This needs review/ack from another SRU team member
now.
--
gdm starting too early for DRM modules to load, no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
** Branch linked: lp:~ubuntu-desktop/gdm/lucid
--
gdm starting too early for DRM modules to load, no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
** Summary changed:
- Dell Studio XPS 13 no video
+ gdm starting too early for DRM modules to load, no video
--
gdm starting too early for DRM modules to load, no video
https://bugs.launchpad.net/bugs/615549
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
27 matches
Mail list logo
