[Bug 1038055] Re: graphics fail to initialise correctly, in kvm with cirrus graphics (after LUKS install)

This bug is back with 13.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1038055 Title: graphics fail to initialise correctly, in kvm with cirrus graphics (after LUKS install) To manage

[Bug 982889] Re: X trying to start before plymouth has finished using the drm driver

I don't think the patch from #31 will fix this because X is really getting EACCESS (0xfff3) not EAGAIN as can be seen in #22 I also think this is probably an issue in plymouth because plymouth is told to quit and release drm before X starts but it somehow does not allways do this in time.

[Bug 1066395] Re: Nautilus (list view) column widths change dynamically on alt-tab, lags on large folders

Simple left-click on the window title, or even losing window focus is enough to trigger this column resizing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066395 Title: Nautilus (list view)

[Bug 850960] Re: iscsid tries to reconnect existing session at startup, failing to do so and hanging the system

*** This bug is a duplicate of bug 677333 *** https://bugs.launchpad.net/bugs/677333 ** This bug has been marked a duplicate of bug 677333 open-iscsi: reconnecting to targets fails with kernel 2.6.32 due to sysfs changes (open-iscsi pkg version out of date with kernel) -- You received

[Bug 982889] Re: X trying to start faster than drm driver is ready

Yes, dmesg output when X fails to start with that kernel is in comment #18 #19 is when it starts fine But when X failed to start it never even got to your debug code cause it failed in drm_ioctl with EACCESS as can be seen from drm debug output. This is where it tries to call drm_set_version and

[Bug 927684] Re: X windows occasionally fails to start up

Try disabling plymouth-splash sudo mv /etc/init/plymouth-splash.conf /etc/init/plymouth- splash.conf.disabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/927684 Title: X windows occasionally

[Bug 982889] Re: X trying to start faster than drm driver is ready

After disabling plymouth-splash I can't reproduce this anymore. It's a race between plymouth and xorg. Plymouth holds DRM master (drm_setmaster_ioctl) while xorg tries to start (drm_setversion) and fails with EACCESS because it needs DRM_MASTER for that. It works fine if 1. plymouth never starts

[Bug 982889] Re: X trying to start faster than drm driver is ready

So I tried a few things with drm.debug=1 kernel param When I reproduce the problem, something (plymouth?) does drm stuff before xorg, and xorg then gets EACCESS error from drm_setversion ioctl (nr=0x07) and dmesg looks like this Apr 21 02:25:35 kujoniq kernel: [0.00] Command line:

[Bug 982889] Re: X trying to start faster than drm driver is ready

Everything starts fine if nothing touches drm before X or it somehow finishes correctly before X tries to start i guess ... Apr 21 02:28:24 kujoniq kernel: [2.802193] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 Apr 21 02:28:24 kujoniq kernel: [2.826851]

[Bug 982889] Re: X trying to start faster than drm driver is ready

Maybe related to #927684 #899725 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start faster than drm driver is ready To manage notifications about this bug go to:

[Bug 982889] [NEW] xorg fails to start after boot on core i5

Public bug reported: X server fails to start the first time after boot, it works fine when I start it again. Looks like a race condition with intel drm initialization, i guess X tries to start faster than drm driver is initialized so it fails. ProblemType: Bug DistroRelease: Ubuntu 12.04

[Bug 982889] Re: xorg fails to start after boot on core i5

** Attachment added: Xorg.0.log https://bugs.launchpad.net/bugs/982889/+attachment/3076065/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: xorg fails to start after

[Bug 982889] Re: X trying to start faster than drm driver is ready

Putting sleep 1 in /etc/init/lightdm.conf was enough. When i look at dmesg it says [2.263168] [drm] Initialized drm 1.1.0 20060810 [2.766592] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 so i guess xorg tries to use it at [ 2.497] in some partially initialized state

[Bug 982889] Re: X trying to start faster than drm driver is ready

** Attachment added: lshw.txt https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3080437/+files/lshw.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X

[Bug 982889] Re: X trying to start faster than drm driver is ready

udev log and corresponding dmesg and xorg log In this case it got to a state when lightdm/X thought it was doing fine, but i got black screen with blinking cursor + mouse pointer ** Attachment added: udev.txt-2012-04-17

[Bug 982889] Re: X trying to start faster than drm driver is ready

** Attachment added: dmesg-2012-04-17 https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3080497/+files/dmesg-2012-04-17 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982889

[Bug 982889] Re: X trying to start faster than drm driver is ready

** Attachment added: Xorg.0.log-2012-04-17 https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3080498/+files/Xorg.0.log-2012-04-17 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 982889] Re: X trying to start faster than drm driver is ready

I looked at the code and it seems it fails somewhere in kernel drm_setversion ioctl after being called from libdrm drmSetInterfaceVersion. I guess it's because drm driver load didn't finish yet. And there are no usefull return values in the code involved so there's no way to know libdrm should

[Bug 933680] Re: Menu windows are being left on the screen as empty 'boxes

*** This bug is a duplicate of bug 933615 *** https://bugs.launchpad.net/bugs/933615 ** This bug has been marked a duplicate of bug 933615 menu shadows not clearing when menus close -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to