[00:00] marjo: ok try booting with vga=315 added to grub [00:01] if that works, update your bios to fix it [00:01] Sarvatt: add vga=315 to the kernel command line? [00:01] * Sarvatt nods [00:02] Sarvatt: no such luck; drum heard, blank screen [00:02] Sarvatt: still want dmesg? [00:03] marjo: what does dmesg | grep "vesafb: mode" say when booting with that vga=315? [00:04] 800x600? [00:04] Sarvatt: returns nothing [00:05] * Sarvatt scratches head [00:09] apw: la la la? :) [00:51] Sarvatt, any thoughts on bug #692677? [00:51] Launchpad bug 692677 in nvidia-settings (Ubuntu) (and 1 other project) "Desktop login to unity leads to hang and compiz crash when X Server Display Confirmation is clicked on (affects: 1) (heat: 8)" [High,Triaged] https://launchpad.net/bugs/692677 [00:52] nvidia-setting's glx calls through unity behave differently than when booted with classic desktop [01:26] for something that's "trivial to fix" that is a large patch [01:41] Hm. So, I can't reproduce *that* crash, but nvidia-settings is all manner of messed up here. [01:42] Which is odd, because it was working perfectly last night. [01:43] SIGFPE! Woot! [02:15] RAOF, hrm [02:16] Just updating to the most current stuff & seeing if I can reproduce. [03:36] Sarvatt, RAOF: Example output from new apport hook - https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/693667 [03:36] Launchpad bug 693667 in xorg (Ubuntu) "Yet another apport test (affects: 1) (heat: 6)" [Undecided,New] [03:37] You know about the APPORT_STAGING env variable, yes? [03:37] Also, that nvidia-settings thing is weird. [03:38] oh, hadn't seen mention of APPORT_STAGING before [03:39] anyway, I mostly test apport locally anyway [03:40] Is DistUpgraded the last time the machine was upgraded from one release to another, or the last time dist-upgrade was run (that's a stupid terminology confusion :() [03:42] what does an apt-get dist-upgrade do exactly? [03:43] Upgrade + install new packages if appropriate. [03:43] upgrade to a new distro? [03:43] “upgrade” is just “install newer versions of what I've got installed, but don't install any new packages” [03:44] well, if it's not upgrading to a new distro then i don't see why it's called "dist-upgrade". sounds like it should do what update-manager -d does [03:44] RAOF, specifically it is top -n 1 from /var/log/dist-upgrade/apt.log [03:44] It does, dosen't it :) [03:45] RAOF, which isn't precisely what I'm after so I might change it [03:45] Hm. SIGFPE in nvidia_drv for all! [03:46] basically what I want is a mechanical way to indicate whether the user's system was upgraded from a prior release, or was a fresh install to natty (possibly with some updates) [03:46] Yeah. That's a fine goal. [03:46] my working theory is that the existence of any content in /var/log/dist-upgrade/apt.log would indicate an upgraded machine [03:47] but I'm open to better solutions [03:47] for now though, being called to dinner... bbl [03:50] Hm. Working theory - switching to display server configuration *sometimes* causes nvidia-settings to resize its window to nonsensical values; from here, maximising will crash the server with an FPE in nvidia_drv, or gtk-window-decorator will BadAlloc first. [03:51] maybe dist-upgrade is one of those things that makes more sense in debian, where there's only a new distro every thousand years or so, than it does in ubuntu, where you can't throw a rock without hitting a new distro [05:16] Well, it really does look like 06_thingamy.patch is to blame. [05:35] RAOF, oh? [05:36] bjsnider, yeah the upgrade vs. dist-upgrade thing has always seemed weird. [05:59] bryceh: Well, I rebuilt nvidia-settings without it and it doesn't seem to trigger the same madness. [06:37] hmm, well sounds like the patch needs more work before we can be shipping it === yofel_ is now known as yofel [20:49] any chance to run fan speed control with old NVIDIA 8500GT