[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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1038055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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. Maybe there should be plymouth --wait quit instead of plymouth quit in /etc/init/plymouth-stop.conf? I tried to find how exactly plymouth quit is handled (especially if the plymouth daemon really releases drm before that command returns) but I never got to the answer. You can try to change the X patch in #31 to spin also on EACCESS (bad solution imho) or plymouth should be fixed to really release drm when told to quit. And I also had this problem in Fedora, someone else reported it at https://bugzilla.redhat.com/show_bug.cgi?id=855677 I reenabled plymouth-splash and will play a little with it again, but it happens randomly in maybe 1/10 reboots so it's not easy to hit. ** Bug watch added: Red Hat Bugzilla #855677 https://bugzilla.redhat.com/show_bug.cgi?id=855677 -- 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 before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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) column widths change dynamically on alt-tab, lags on large folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1066395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850960 Title: iscsid tries to reconnect existing session at startup, failing to do so and hanging the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/850960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 fails with EACCESS Apr 21 02:25:36 kujoniq kernel: [3.134782] [drm:drm_ioctl], pid=1207, cmd=0xc0106407, nr=0x07, dev 0xe200, auth=1 Apr 21 02:25:36 kujoniq kernel: [3.134784] [drm:drm_ioctl], ret = fff3 Apr 21 02:25:36 kujoniq kernel: [3.134790] [drm:drm_ioctl], pid=1207, cmd=0xc0106407, nr=0x07, dev 0xe200, auth=1 Apr 21 02:25:36 kujoniq kernel: [3.134792] [drm:drm_ioctl], ret = fff3 So it's not really a drm problem. Xorg tries to start too soon while plymouth-splash is still doing stuff with drm. After i disabled plymouth-splash i never reproduced this again. -- 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: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 fails to start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/927684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 2. plymouth calls drm_dropmaster_ioctl before X starts And another thing is the Xorg.log timestamps can't really be trusted. -- 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: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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: BOOT_IMAGE=/vmlinuz-3.2.0-24-generic root=/dev/mapper/ssd-ubuntu--precise ro quiet drm.debug=1 Apr 21 02:25:35 kujoniq kernel: [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-3.2.0-24-generic root=/dev/mapper/ssd-ubuntu--precise ro quiet drm.debug=1 Apr 21 02:25:35 kujoniq kernel: [2.487567] [drm] Initialized drm 1.1.0 20060810 Apr 21 02:25:35 kujoniq kernel: [2.497942] [drm:drm_pci_init], Apr 21 02:25:35 kujoniq kernel: [2.497952] [drm:drm_get_pci_dev], Apr 21 02:25:35 kujoniq kernel: [2.497977] [drm:drm_get_minor], Apr 21 02:25:35 kujoniq kernel: [2.498099] [drm:drm_get_minor], new minor assigned 64 Apr 21 02:25:35 kujoniq kernel: [2.498101] [drm:drm_get_minor], Apr 21 02:25:35 kujoniq kernel: [2.498161] [drm:drm_get_minor], new minor assigned 0 Apr 21 02:25:35 kujoniq kernel: [2.552305] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). Apr 21 02:25:35 kujoniq kernel: [2.552306] [drm] Driver supports precise vblank timestamp query. Apr 21 02:25:35 kujoniq kernel: [2.552830] [drm:drm_sysfs_connector_add], adding VGA-1 to sysfs Apr 21 02:25:35 kujoniq kernel: [2.552960] [drm:drm_sysfs_hotplug_event], generating hotplug event Apr 21 02:25:35 kujoniq kernel: [2.567174] [drm:drm_sysfs_connector_add], adding HDMI-A-1 to sysfs Apr 21 02:25:35 kujoniq kernel: [2.567194] [drm:drm_sysfs_hotplug_event], generating hotplug event Apr 21 02:25:35 kujoniq kernel: [2.567201] [drm:drm_sysfs_connector_add], adding DP-1 to sysfs Apr 21 02:25:35 kujoniq kernel: [2.567235] [drm:drm_sysfs_hotplug_event], generating hotplug event Apr 21 02:25:35 kujoniq kernel: [2.676194] [drm:drm_irq_install], irq=51 Apr 21 02:25:35 kujoniq kernel: [2.783104] fbcon: inteldrmfb (fb0) is primary device Apr 21 02:25:35 kujoniq kernel: [2.783492] [drm:drm_vblank_get], enabling vblank on crtc 0, ret: -22 Apr 21 02:25:36 kujoniq kernel: [2.951148] [drm:drm_calc_timestamping_constants], crtc 3: hwmode: htotal 2080, vtotal 1235, vdisplay 1200 Apr 21 02:25:36 kujoniq kernel: [2.951151] [drm:drm_calc_timestamping_constants], crtc 3: clock 154000 kHz framedur 16679910 linedur 13506, pixeldur 6 Apr 21 02:25:36 kujoniq kernel: [2.957757] fb0: inteldrmfb frame buffer device Apr 21 02:25:36 kujoniq kernel: [2.957757] drm: registered panic notifier Apr 21 02:25:36 kujoniq kernel: [2.957806] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 Apr 21 02:25:36 kujoniq kernel: [2.997507] [drm:drm_stub_open], Apr 21 02:25:36 kujoniq kernel: [2.997510] [drm:drm_open_helper], pid = 286, minor = 0 Apr 21 02:25:36 kujoniq kernel: [2.997514] [drm:drm_setup], Apr 21 02:25:36 kujoniq kernel: [2.997517] [drm:drm_ioctl], pid=286, cmd=0xc0406400, nr=0x00, dev 0xe200, auth=1 Apr 21 02:25:36 kujoniq kernel: [2.997520] [drm:drm_ioctl], pid=286, cmd=0xc0406400, nr=0x00, dev 0xe200, auth=1 Apr 21 02:25:36 kujoniq kernel: [2.997523] [drm:drm_release], open_count = 1 Apr 21 02:25:36 kujoniq kernel: [2.997525] [drm:drm_release], pid = 286, device = 0xe200, open_count = 1 Apr 21 02:25:36 kujoniq kernel: [2.997528] [drm:drm_lastclose], Apr 21 02:25:36 kujoniq kernel: [2.997541] [drm:drm_lastclose], driver lastclose completed Apr 21 02:25:36 kujoniq kernel: [2.997542] [drm:drm_lastclose], lastclose completed Apr 21 02:25:36 kujoniq kernel: [2.997546] [drm:drm_stub_open], Apr 21 02:25:36 kujoniq kernel: [2.997548] [drm:drm_open_helper], pid = 286, minor = 0 Apr 21 02:25:36 kujoniq kernel: [2.997549] [drm:drm_setup], Apr 21 02:25:36 kujoniq kernel: [2.997551] [drm:drm_ioctl], pid=286, cmd=0xc0406400, nr=0x00, dev 0xe200, auth=1 Apr 21 02:25:36 kujoniq kernel: [2.997553] [drm:drm_ioctl], pid=286, cmd=0xc0406400, nr=0x00, dev 0xe200, auth=1 Apr 21 02:25:36 kujoniq kernel: [2.997556] [drm:drm_release], open_count = 1 Apr 21 02:25:36 kujoniq kernel: [2.997557] [drm:drm_release], pid = 286, device = 0xe200, open_count = 1 Apr 21 02:25:36 kujoniq kernel: [2.997559] [drm:drm_lastclose], Apr 21 02:25:36 kujoniq kernel: [2.997566] [drm:drm_lastclose], driver lastclose completed Apr 21 02:25:36 kujoniq kernel: [2.997568] [drm:drm_lastclose], lastclose completed Apr 21 02:25:36 kujoniq kernel: [2.997571] [drm:drm_stub_open], Apr 21 02:25:36 kujoniq kernel: [2.997572] [drm:drm_open_helper], pid = 286, minor = 0 Apr 21 02:25:36 kujoniq kernel: [2.997574] [drm:drm_setup], Apr 21 02:25:36 kujoniq kernel: [2.997576] [drm:drm_ioctl], pid=286, cmd=0xc0406400, nr=0x00, dev 0xe200, auth=1 Apr 21 02:25:36 kujoniq kernel: [2.997578] [drm:drm_ioctl],
[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] [drm:drm_stub_open], Apr 21 02:28:24 kujoniq kernel: [2.826854] [drm:drm_open_helper], pid = 1317, minor = 0 Apr 21 02:28:24 kujoniq kernel: [2.826857] [drm:drm_setup], Apr 21 02:28:24 kujoniq kernel: [2.826865] [drm:drm_ioctl], pid=1317, cmd=0xc0406400, nr=0x00, dev 0xe200, auth=1 Apr 21 02:28:24 kujoniq kernel: [2.826869] [drm:drm_ioctl], pid=1317, cmd=0xc0406400, nr=0x00, dev 0xe200, auth=1 Apr 21 02:28:24 kujoniq kernel: [2.826873] [drm:drm_release], open_count = 1 Apr 21 02:28:24 kujoniq kernel: [2.826875] [drm:drm_release], pid = 1317, device = 0xe200, open_count = 1 Apr 21 02:28:24 kujoniq kernel: [2.826878] [drm:drm_lastclose], Apr 21 02:28:24 kujoniq kernel: [2.826890] [drm:drm_lastclose], driver lastclose completed Apr 21 02:28:24 kujoniq kernel: [2.826892] [drm:drm_lastclose], lastclose completed Apr 21 02:28:24 kujoniq kernel: [2.826905] [drm:drm_stub_open], Apr 21 02:28:24 kujoniq kernel: [2.826906] [drm:drm_open_helper], pid = 1317, minor = 0 Apr 21 02:28:24 kujoniq kernel: [2.826908] [drm:drm_setup], Apr 21 02:28:24 kujoniq kernel: [2.826917] [drm:drm_ioctl], pid=1317, cmd=0xc0106407, nr=0x07, dev 0xe200, auth=1 Apr 21 02:28:24 kujoniq kernel: [2.826919] APW: drm_setversion called Apr 21 02:28:24 kujoniq kernel: [2.826921] APW: drm_setversion returned 0 Apr 21 02:28:24 kujoniq kernel: [2.826922] [drm:drm_ioctl], pid=1317, cmd=0xc0106401, nr=0x01, dev 0xe200, auth=1 Apr 21 02:28:24 kujoniq kernel: [2.826924] [drm:drm_ioctl], pid=1317, cmd=0xc0106401, nr=0x01, dev 0xe200, auth=1 Apr 21 02:28:24 kujoniq kernel: [2.826934] [drm:drm_ioctl], pid=1317, cmd=0xc0106407, nr=0x07, dev 0xe200, auth=1 Apr 21 02:28:24 kujoniq kernel: [2.826935] APW: drm_setversion called Apr 21 02:28:24 kujoniq kernel: [2.826937] APW: drm_setversion returned 0 Apr 21 02:28:24 kujoniq kernel: [2.826939] [drm:drm_ioctl], pid=1317, cmd=0xc0106446, nr=0x46, dev 0xe200, auth=1 Apr 21 02:28:24 kujoniq kernel: [2.826989] [drm:drm_ioctl], pid=1317, cmd=0x80106463, nr=0x63, dev 0xe200, auth=1 -- 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: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Mon Apr 16 10:35:28 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7750] Advanced Micro Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:21fa] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) MachineType: MSI MS-7750 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/ssd-ubuntu--precise ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z68A-G43 (G3) (MS-7750) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd08/25/2011:svnMSI:pnMS-7750:pvr1.0:rvnMSI:rnZ68A-G43(G3)(MS-7750):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7750 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.7.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 precise ubuntu -- 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 boot on core i5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/982889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 boot on core i5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/982889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 or something -- 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: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 trying to start faster than drm driver is ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3080494/+files/udev.txt-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 Title: X trying to start faster than drm driver is ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Title: X trying to start faster than drm driver is ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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. 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: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 try again. -- 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: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu. https://bugs.launchpad.net/bugs/933680 Title: Menu windows are being left on the screen as empty 'boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/933680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
