[05:48] hi folks, I was trying to see what setup my touchpad has, when I was confronted by this error message: http://wstaw.org/m/2012/10/08/plasma-desktopTN2364.png [05:49] I don't know if I should file a bug, and if so what info to include in the bug report [05:49] but something is clearly askew [06:09] valorie: file a bug against kde [06:12] heh [06:13] def. a KDE bug yes, but i guess I'll have to ask in the devel chan where in KDE the problem is [06:13] thanks, tjaalton [06:19] whatever has the capplet [06:20] valorie: synaptiks [06:21] ok [06:21] seems like a discovery problem [06:21] because the touchpad is working [06:22] but the "error message" is clearly insane [06:41] morning [06:42] interesting error indeed :-) [06:43] :-) [07:42] mvo: can you look at https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1062503 ? [07:42] Launchpad bug 1062503 in apt (Ubuntu) "apt fails to install libglapi-mesa-lts-quantal correctly on switching x stacks" [Undecided,New] [08:02] https://bugs.launchpad.net/ubuntu/+source/xorg-server?field.status:list=NEW&field.status:list=INCOMPLETE_WITH_RESPONSE&field.status:list=CONFIRMED&field.status:list=TRIAGED&field.status:list=INPROGRESS&field.status_upstream=pending_bugwatch&field.status_upstream=hide_upstream&field.status_upstream=resolved_upstream&field.status_upstream-empty-marker=1&field.upstream_target=xorg-server&field.tag=quantal+-kubuntu+-xubuntu+-ppc+- [08:02] omit&field.tags_combinator=ALL [08:03] odd we have a sudden influx of xserver crashes involving __mpn_lshift() since the last few days [08:07] yeah I noticed the same [08:09] probably all dupes, but didn't look into them at all [08:10] mlankhorst: I will look at it once I'm finished my current task ,thanks for the pointer [08:11] yay ty :) [08:19] bryceh: yeah weird bunch though, can't make sense of it, seems to be nouveau [08:20] not because of the patch you pushed?-) [08:21] not a chance, it changes 1 constant to another [08:22] seems more like a continuation of some other problem [08:27] and since it's run during atexit, whatever caused it to crash already happened.. [08:28] [ 23980.340] (II) NOUVEAU(0): NVEnterVT is called. [08:28] [ 23980.414] (EE) NOUVEAU(0): failed to set mode: Device or resource busy [08:28] Fatal server error: [08:28] [ 23980.414] failed to create screen resources [08:31] besides, the other one is radeon [08:31] https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1061515 [08:31] Launchpad bug 1061515 in xorg-server (Ubuntu) "Xorg crashed with SIGABRT in __mpn_lshift()" [Medium,New] [08:35] listp=0xffffffffffffffff [08:36] ^ do they all have that in common? [08:36] didn't check, wouldn't surprise me [08:36] #11 0x00007f3c74c3c02c in ErrorF (f=0xb42

) at ../../os/log.c:817 [08:37] seems exit is messed up at least [08:37] 0xb42 out of bounds sounds suspcious too [08:37] yeah it's probably overwritten [08:38] at least 3 follow this pattern. [08:38] and here I was hoping we wouldn't have a random memory corruption right before release :\ [08:39] http://pastebin.com/02gPy0AY is what valgrind came up with [08:40] one during xf86OutputSetEDID too, but that one is probably less harmful [08:40] intriguing [08:42] probably the same as on intel, mouse gets freed after devices are, so it tries to clean up device backing which wouldn't work.. [09:02] although in this case it seems to be a refcount bug [09:22] the edid one is probably harmless, but a real simple fix [09:34] tjaalton: could you upload xorg-server real quick? I doubt the cursor problem will be fixed today but the other issue should be fixed [09:36] mlankhorst: alright [09:39] no compat output sounds like a bug? [09:39] jcristau: presumably it happens before compat_output is initialized [09:41] because it happens during edid probing [09:41] hmm [09:41] ok.. [09:54] the real annoying parts are the cursor problems though [09:59] oh fun, found another one [10:00] hmm, might pull other fixes too [10:01] the xserver stable branches seem to have died somehow [10:02] tjaalton: yeah hitting some fun :/ [10:05] http://paste.ubuntu.com/1267192/ for the acpi valgrind bug? [10:05] for valgrind backtrace justifying it: http://paste.ubuntu.com/1267193/ [10:08] but I need to do slightly more justification, hold on with uploading for now [10:24] tjaalton: ok so the trigger for that one is killing acpid before Xorg-server is closed [10:30] hrm [10:30] why not just rip the acpi code from the server then, it's not used for anything aiui [10:32] except acpi events for video probably? [10:35] intel handles XF86_APM_CAPABILITY_CHANGED at least.. [10:36] if it wasn't for being the last day before final freeze, I would agree that we should nuke it [10:36] that might be replaced by drm hotplug events nowadays [10:36] maybe... [10:38] riight, maybe not nuke it now :) [10:41] tjaalton: ok I'm tempted to leave it for now, see if someone reviews it and if not have it in before release since it's a real crasher [10:45] pushed [15:23] mlankhorst: sorry for the slow reply, I commented in the bug, would be great to get the output of the debug comment i put there [15:24] ok [15:29] mvo: seems to not even consider unpacking amd64 version [15:31] added log :-) === bjsnider_ is now known as bjsnider === soren_ is now known as soren [22:33] After removing unity from my 12.04 install, X fails to display anything. It starts without any fail messages in ~/.xsession-errors and runs but doesn't display anything at all [22:36] ps ax shows X running at least but X log seems to show it exiting at the end here for no apparent reason http://pastebin.com/96zrSt4J [22:37] I tried killing X and all dm's then using startx but it exhibits the same problem [22:37] * soreau about to try with different user [22:41] soreau: vesa? [22:42] not even fb0? [22:50] soreau, check the lightdm logs [22:50] nope, not even a new user works [22:51] the screen seems to change modes but just shows illuminated black [22:51] mlankhorst: vesa is what the default is choosing [22:51] This is a really old intel gpu, I think i810 or something [22:52] yeah I noticed :/ [22:52] has always worked fine until I decided to uninstall all the unity stuff instead of chmod -x [22:52] So I'm guessing somewhere in it's xinit sequence it tries to load some unity stuff and things go south from there [22:53] jeez i810? why? [22:53] It's just an old box I use as a server really [22:53] some people like pain [22:53] heh, ok... just keep it away from the rest of us ;-) [22:54] I guess I could try starting X manually without startx, let's see [22:55] nope, same thing [22:55] i can't even begin to remember how this is supposed to work to start with.. [22:55] * soreau reinstalls unity stuff as a last ditch effort [22:56] nope, still broke [22:57] I guess it's time to reinstall. Is 12.10 out yet? [22:58] !isitout [22:58] Quantal? Nope, it's not out. Wait some 6 months... [22:58] haha [22:58] heh [22:58] !forget isitout [23:00] * soreau begins preparations with a backup [23:00] hell, it's been a good run though. Had 10.04 installed until lts-upgrading to 12.04 and of course things began to fall apart after that [23:01] so haven't reinstalled on this machine for at least a couple years now [23:03] well that's good though, userspace modesetting finally dying off :p [23:05] I'm using xubuntu this time though, this unity curse is getting ridiculous and out of hand [23:06] well i810 is probably below system requirements for ubuntu anywa [23:07] You should be able to start X without unity running, though. [23:07] RAOF: X refuses to display anything. Even with startx or X :0 [23:07] tried with a new user, still nothing [23:08] Refuses to display anything, or cleanly shuts down immediately? [23:08] RAOF: https://wiki.ubuntu.com/MaartenLankhorst/DeveloperApplication ? [23:08] RAOF: ps ax show it's running but X log tells a different story http://pastebin.com/96zrSt4J [23:08] mlankhorst: Thanks for the ping :) [23:09] That looks like X cleanly shutdown after its last client died, which is what our X-starting tools tend to do. [23:10] well the X process never returned apparently [23:11] RAOF: and this log was taken from a 'normal' boot without doing anything extra [23:11] the power glitched this morning and when I rebooted it, I noticed it had reinstalled unity stuff. Then I removed everything unity and now it's broken [23:12] (since the next reboot after removing unity) [23:12] Does "everything unity" include unity-greeter? [23:12] night [23:12] If I try starting an X client from ssh, it seems to work but still the display will not output anything [23:12] Because removing that'll break lightdm, because that's the greeter that we use ;) [23:13] RAOF: Looks like it [23:14] Try installing unity-greeter; I suspect that might get lightdm displaying something, since it'll have something to display. [23:14] I heard the bongos but no display output [23:15] It's as if X is working fine but there's no output to the display [23:16] Hm, fun. [23:54] mesa 9 is out