[Bug 775117] Re: Thunar hangs on first launch of each session
I had the same experience as @gridcube (comment 15) on Xubuntu 11.10/Oneiric; very slow first open of Thunar, with multiple instances popping open. Last test, I tried to open my ~/Downloads folder in Thunar (via Kupfer); while nothing was happening, I tried opening my home folder in thunar from Terminal; shortly after *three* Thunar windows opened (one for Home and *two* for ~/Downloads). Joshua O'Leary's workaround (comment 13) of changing AutoMount to false in /usr/share/gvfs/mounts/network.mount seems to fix this hang for me. Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/775117 Title: Thunar hangs on first launch of each session To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/775117/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625670] Re: Not all desktop items are themed
@dualityim: FWIW, your workaround in comment #28 works well for me as well (Maverick 64-bit). Thanks. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. https://bugs.launchpad.net/bugs/625670 Title: Not all desktop items are themed -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625670] Re: Not all desktop items are themed
I can confirm this as well: top panel always looks awful after a reboot; generally takes numerous logout/login cycles to get clean theme; fast system w/nVidia, i7 and SSD: Maverick/10.10 64-bit System76 Serval Pro (SER-P6) laptop Core i7-840QM Processor ( 45nm, 8MB L3 Cache, 1.86GHz ) 8 GB - DDR3 1333 MHz Nvidia GeForce GTX 285M Graphics with 1GB GDDR3 Video Memory 160 GB Intel X25-M Solid State Drive I'm attaching screen shots of both the good and bad look of my top panel. I'm using the default Maverick Ambiance theme. FWIW, the following workaround was posted at http://ubuntuforums.org/showpost.php?p=9969103postcount=6 sudo mkdir /usr/share/gdm/nostart sudo mv /usr/share/gdm/autostart/LoginWindow/gnome-settings-daemon.desktop /usr/share/gdm/nostart/ # logout/login ** Attachment added: Screen shots of good/bad themed top panel. https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/625670/+attachment/1749876/+files/theme-screenshots.tar.gz -- Not all desktop items are themed https://bugs.launchpad.net/bugs/625670 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 615549] Re: gdm/kdm starting too early for DRM modules to load, no video
Martin, Seth: Thanks for the confirmation. FWIW, I've narrowed my newfound nasty crashes down to the Chrome browser, with nVidia drivers installed, but only when on battery power! If I disable nVidia drivers, or simply keep AC power connected to my laptop, everything is fine; but with battery power and nVidia, Chrome crashes hard almost instantly, every time--including a fresh install of Lucid/10.04 64-bit. Nothing else seems to cause a crash. As long as I stick with Firefox when on battery power, I've never seen a crash while working (with plenty of other apps, for extended periods). Ah well, haven't found a report yet, but will open a bug soon if I have to. -- gdm/kdm 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 Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 615549] Re: gdm starting too early for DRM modules to load, no video
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 later booting up on battery power and seeing crashes come fairly quickly and repeatedly. I've been searching around for other bugs that match, but no luck. Thanks again. -- 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 Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 615549] Re: gdm starting too early for DRM modules to load, no video
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 row, but I'm not sure this will show me much. The crashes don't always occur right after reboot. Is there something more to this? Thanks. -- 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 Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 615549] Re: gdm starting too early for DRM modules to load, no video
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 really dealing with a completely different bug still? If so, any tips would be incredibly appreciated. This has been a long frustrating road (i.e., nice new loaded System76 Serval laptop w/Ubuntu 10.04, which is barely usable). Thanks in advance! -- 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 Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 615549] Re: gdm starting too early for DRM modules to load, no video
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://bugs.launchpad.net/ubuntu/+source/gdm/+bug/615549/+attachment/1623265/+files/glxinfo.out -- 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 Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 615549] Re: gdm starting too early for DRM modules to load, no video
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/ubuntu/+source/gdm/+bug/615549/+attachment/1623267/+files/out_20100922-1156.tgz -- 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 Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 615549] Re: gdm starting too early for DRM modules to load, no video
@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). I doubt the resume was involved, because last night I rebooted right after a crash and saw another crash shortly thereafter--unless it's possible that some sort of residual issue was related. If you think you were only having the VT1 (VT2) problem before you first reported the problem perhaps it would be worthwhile to check the changes you were trying out around comment #69 to see if they were all reversed. You were making changes to the grub configuration, if I recall. Yes, I'm positive that I've reversed any and all changes. I've triple- checked. I may attempt a clean install soon anyway, just to be absolutely certain. Since we now know that your problem was related to the start of the proprietary NVIDIA driver and since the new problem looks like a crash in the same driver, you might be able to get relief from both by trying to switch to a different driver. I'm no longer using an nvidia card with my lucid system, but if I remember correctly I think you might check either the System-Admin-Hardware Drivers to change drivers, or perhaps you can switch drivers just by turning off all special effects in the Appearance preference. The new driver name then would be reflected in your xorg.0.log files. I'm not sure I follow you here. I have tried the alternate nVidia driver (version 173) and the recommended one, but had issues with both. When I disable nVidia drivers I have no problem, but then I get a very boring desktop experience ;-) Thanks again. -- 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 Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 615549] Re: gdm starting too early for DRM modules to load, no video
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 power. This would explain the fact that I'm sometimes perfectly stable all day at the office (with AC power plugged in to my laptop) while other times it's just crash after crash. I've also noticed that the crashes seem to occur very soon after login. The last 4-5 crashes have also all occurred just as I was opening Chrome browser. I've also found a hint of this being battery/power related, as I found mentions of gnome-power-manager in a GDM log just after crash. I've attached various output and X/GDM logs. Here are a few lines from my :0-greeter.log.1 log, which has the gnome-power-manager warnings: (gnome-power-manager:1852): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.1/gobject/gsignal.c:2273: signal `proxy- status' is invalid for instance `0x773250' ** (gnome-power-manager:1852): WARNING **: Either HAL or DBUS are not working! ** (gnome-power-manager:1852): WARNING **: proxy failed ** (gnome-power-manager:1852): WARNING **: failed to get Computer root object ** (gnome-power-manager:1852): WARNING **: proxy NULL!! Martin, you'd mentioned that the crash could be delayed from boot if something using 3D opens--could this be what's happening with Chrome? Then again, if my bug is related to power management, is this a separate bug or related? Thanks again to all for any help! ** Attachment added: out_20100922-1626.tar.gz https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/615549/+attachment/1624344/+files/out_20100922-1626.tar.gz -- 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 Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 615549] Re: gdm starting too early for DRM modules to load, no video
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 comment. I went nearly two full days with this patch and no GDM crash, including a few reboots, suspends and hibernates... until tonight :( The lovely GDM crash appeared again, shortly after resuming from a suspend. I've also included relevant log files around the time of this GDM crash. After the crash, I shut down, then booted again, and promptly had another GDM crash almost immediately. I've logged in again and have been safe for 10-15 minutes here on tty8 now. I'll add a separate attachment for logs for this second crash. ** Attachment added: logs_20100921-2050.tar.gz https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/615549/+attachment/1620683/+files/logs_20100921-2050.tar.gz -- 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 Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 615549] Re: gdm starting too early for DRM modules to load, no video
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/615549/+attachment/1620684/+files/logs_20100921-2053.tar.gz -- 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 Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
Forgive me if I'm missing something, but based on comments from Martin and Steve, and Seth's thorough testing reported in comment #159, my understanding is that I should simply wait for the bug #615549 fix to be back-ported to Lucid. Is this correct? Should I be updating bug #615549 for Lucid in some way, or will this bug continue as a way to get that back-port? I don't want to step on toes of developers or other who know better, but I didn't want to sit here doing nothing if I could help move this along :) Thanks. -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
Steve Langasek wrote in #150: Thanks. Could you now provide the same files when *not* booting with this workaround? Yes, the attached archive contains two sets of logs, both without vga=799 or any other workaround in place. One has quiet splash appended to the boot line, which landed X on tty2 (as expected, and would likely crash eventually). The other has plymouth:debug appended to the boot line, which landed X on tty7 (and is generally more stable, rarely crashing--another near workaround). I've included udev, /proc/fb and any relevant X/gdm logs. HTH! One curious thing I notice in the plymouth log is that none of the renderers load: [./plugin.c] open_device:could not open '/dev/fb0': No such file or directory Can you confirm that when booting this way, you get a text-only plymouth splash screen? Yes, with vga=799 I see a text-only splash. ** Attachment added: bug-625239-logs.tar.gz https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/625239/+attachment/1588876/+files/bug-625239-logs.tar.gz -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
Steve, Please show the contents of a plymouth:debug log, and /proc/fb, when booting with vga=799 (and without grub_gfxmode set). Attaching /var/log/udev, /var/log/plymouth-debug.log and /proc/fb after boot with no GRUB_GFXMODE set and: GRUB_CMDLINE_LINUX_DEFAULT=vga=799 plymouth:debug GRUB_CMDLINE_LINUX= Keep in mind that the above generally behaves as a workaround for me. I did boot with X on VT7 this time. Jamie, is the udev log file attached to comment 89 from a boot with or without the vga=799 workaround, and with or without an X crash on startup? I believe the log attached to 89 was without the vga=799, but I can't be absolutely certain, sorry. Instead, I probably had the plymouth:debug in there, which also turned out to be a workaround. When I had vga=799 in there, I don't believe I ever had a crash. ** Attachment added: vga-799-plymouth-debug-no-grub_gfxmode.tar.gz https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/625239/+attachment/1583158/+files/vga-799-plymouth-debug-no-grub_gfxmode.tar.gz -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
Steve, Seth, Jamie, can one of you also show the output of 'grep fb /var/log/kern.log' on a system showing this problem? Attached, after boot with standard configuration (no workarounds or related custom config at all). ** Attachment added: kern.log-grep-fb.out https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/625239/+attachment/1583163/+files/kern.log-grep-fb.out -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
Steve, I meant to confirm that the boot that produced the output file attached to comment #127 did indeed land me with X on vt2, and I did crash, as expected, after a few minutes, when pressing enter in Terminal. -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
Steve, You might also be able to confirm this is the problem by commenting out the graphics-device-added fb0 part of the start condition. Okay, testing with standard disto version of /etc/default/grub and the following in my /etc/init/gdm.conf: start on (filesystem and started dbus and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1 or stopped udevtrigger)) stop on runlevel [016] Boot seemed to be fairly quick and I did NOT notice the flicker I used to see after the splash screen. It was a pretty smooth transition to the GDM login screen, and I'm on tty7. I've also been working for 40 minutes now without a crash, which seems promising. Are there any logs you'd like me to report with this configuration/boot? -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
Seth, So let me get this straight, you just removed the graphics-device-added fb0 PRIMARY_DEVICE_FOR_DISPLAY=1 disjunction? Yes, that is exactly what I did, and nothing else. -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
Steve, Seth, The graphics-device-added fb0 PRIMARY_DEVICE_FOR_DISPLAY=1 removal tweak is not a guaranteed workaround after all. I just booted up again and crashed within a minute of use. I was just waiting for a Chrome tab to open--no keyboard activity this time. -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
I seem to have discovered a slightly new style of crashes, which I believe have only occurred when I have a modified /etc/init/gdm.conf file. Yesterday and today I've witnessed this new crash behavior with both: * Seth's /etc/init/gdm.conf workaround from https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/532047/comments/91 * Steve's suggested test that I note in comment #130 (which didn't crash immediately, but did upon a second boot) These are the characteristics of my new crash experience: * Boots with X on tty7 and seems fine for a while. * Crashes without keyboard cause (sometimes using mouse/click, one time doing nothing but waiting for IntelliJ IDEA to open). * Crash to login screen, then X on tty8. * After crash and relogin to tty8, usually another crash very quickly (again, not related to keyboard activity), which then moves X to tty9. * After a crash, I'm unable to switch to any other tty--all show completely blank screen. My original issue, which I can reproduce any time by simply keeping the original /etc/init/gdm.conf and /etc/default/grub in place, was unique to the above in the following ways: * First boot always to tty1 or tty2 (usually tty2). * Always crashed within an hour of working, when pressing Enter. * Always on tty8 after second login, and never crashed again until a reboot. * Both before and after a crash, I was still able to switch to other ttys with no problem. The one workaround that seems to always work, to the best of my knowledge, is when I only add vga=799 to the linux boot line, and change nothing else. I'm pretty sure I went days without a crash with Seth's gdm.conf tweak, so it was odd when it suddenly started crashing like crazy yesterday. -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
Seth, May I suggest _not_ tweaking your gdm.conf in that particular way then? Yes :) I did so only as a workaround, but obviously that was not stable. I also just discovered that the same crashes can now occur even with a untouched gdm.conf. Possibly a different bug, sure, but I hope not!?! Perhaps you did not notice, but I have posted a fix that works for me. It is a patch against gdm and the package is available from https://launchpad.net/~bugs-sehe/+archive/gdm625239 I had not noticed you mention a fix, but not realize it was made available in your PPA. Thank you very much for the detailed instructions --that's what I needed. BTW, I just disabled my nVidia drivers, so I could at least post an update without crashing, and I noticed that my boot was notably MUCH faster. I'll be curious to see if I notice the same with your fix. Off to apply your patch. Thanks! -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
Seth, thanks for the additional workaround. I've applied your patch from ppa:bugs-sehe/gdm625239 and all has been well for about an hour. My boot time seemed a little slow again, after re-enabling my nVidia drivers, but I can live with that if I have a stable X session! I will report back if I see another crash, but so far your fix appears to be successful for me as well. Thanks. -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
Seth, I just installed bootchart, rebooted and had 2 quick crashes (with your patch installed). I only see black screen when switching tty, so unable to check out logs so far. I'll report back soon. -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
Seth, With just a couple bootcharts, it appears I take 4 seconds longer to boot with nVidia drivers enabled. Also, despite having an extremely fast machine, your boots were about 400% faster than mine! I've attached the two, in case they're of any interest. Is there any reason installing bootchart would reintroduce this bug, or does this just mean that your fix simply doesn't work for me? I could remove bootchart and see... Thanks. ** Attachment added: bootcharts.tar.gz https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/625239/+attachment/1585924/+files/bootcharts.tar.gz -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
