[00:11] RAOF, any ideas for bug #726179 ? [00:11] Launchpad bug 726179 in xserver-xorg-video-intel (Ubuntu) "stuttery adobe flash chromium video playback (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/726179 [00:20] bryce_: Um. Nothing obvious. [00:25] RAOF: I finally figured out what was crashing my x server....it is the virt-manager...it is when I switching between an open virtual machine window and going back to the desktop. I opened bug #719036 Is there anything else I could try? [00:25] Launchpad bug 719036 in fglrx-installer (Ubuntu) "[fglrx] ATI FirePro 2450 512MB PCI-e x16 Graphics Video Card crashed X every 24-48 hours (affects: 1) (heat: 254)" [Undecided,New] https://launchpad.net/bugs/719036 [00:26] RAOF, I'm not even sure what procedure to use for analyzing flash video playback problems. Is this likely to not be an X issue? Maybe there's a more appropriate package this should be filed against? [00:27] bryce_: It's probably better to file against the flash player? [00:28] ok [00:32] huh weird, we're getting a notable spate of "-fglrx doesn't install" bugs today [00:34] oh maybe someone's just triaging them over [01:13] RAOF, ok another "interesting" bug I'm nfi'd on - bug 721881 [01:13] Launchpad bug 721881 in xserver-xorg-video-intel (Ubuntu) "compiz crashed with SIGSEGV in intel_region_data() (affects: 1) (heat: 10)" [Medium,New] https://launchpad.net/bugs/721881 [01:14] seems to be unity crashing in some mesa code [01:18] Yeah, that's definitely mesa code. [01:19] Ah, sweet mipmapping fun. [01:22] do you have a 7.10.1 package in a ppa somewhere? maybe having them test on that would be next action for this bug? [01:23] I don't have 7.10.1 anywhere yet. That wouldn't be a bad idea, but I don't think there's anything new in the i915 mipmapping code there. === Azelphur is now known as zz_Azelphur === zz_Azelphur is now known as Azelphur [06:58] hrm, after resume some parts of the screen are "dead", no input goes through [07:24] running compiz --replace restored sanity [07:39] RAOF: actually, I also have a personal git-tree on git.d.o, wonder if I could delegate write access to it.. [07:39] for xf86-input-wacom that is [07:39] and whee, first patch accepted upstream (oneliner reported on lp) [08:20] RAOF, hello [08:21] ara: Howdie! [08:21] What's up? :) [08:21] RAOF, good, thanks! yourself? [08:21] A bit tired. I've just been running around, doing push-ups, etc for an hour or so. [08:22] hehehe [08:22] But I have a coffee, and a patch to make unity less hateful on multi-head systems! [08:22] great, people will be happy :) [08:22] RAOF, cr3 told me that you mentioned a bug in Lucid that prevent installations for desktops without a monitor attached to them, do you remember the bug number? [08:24] I'll hunt it down. [08:25] It was fixed in 1.9. [08:25] Hah! There it is. Bug #337889 [08:25] Launchpad bug 337889 in xorg-server (Ubuntu) "[needs 1.9] X server should fallback to vesa when a monitor isn't connected (heat: 4)" [Wishlist,Fix released] https://launchpad.net/bugs/337889 [08:27] That didn't get fixed by falling back to vesa, by the way, but kms drivers will start X without a monitor attached because they can resize the framebuffer when a monitor *does* get plugged in. [08:27] ara: ^^^^ [08:28] RAOF, thanks! [08:29] RAOF, do you think this will arrive as SRU to lucid at some point? [08:30] Probably not. [08:30] I could look to see how intricate it would be to backport if it's really important. [08:31] RAOF, well, right now, for our testing environment, it is a bit critical, as we have a bunch of desktops and only one monitor. But, oh, well, let's hope to get a KVM :) [08:32] RAOF, thanks for pointing me to the right bug [08:32] And you need to start X on them? [08:33] Hm. I guess so. [08:52] Hi all [08:53] Does anyone have an idea on how I could debug bug 726496 (or provide some more useful info so someone else more knowledgeable can debug it)? [08:53] Launchpad bug 726496 in compiz (Ubuntu) "Cannot use Unity or Classic desktop with effects after the latest nvidia+xorg update (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/726496 [08:57] dpm: well, fwiw classic with effects works here. is the whole screen frozen, or can you draw on the desktop on some part of the screen? [08:59] hi tjaalton, the whole screen is frozen, as far as I can tell. The mouse pointer works. If I switch to a tty and then I switch back to the previous graphic screen, then the screen is black and the mouse pointer still works. Works, as in it moves, but clicking/hovering has no effect [09:00] dpm: ok, so its broken [09:01] yeah, the only workaround I've found is to switch to a tty, kill compiz and start metacity [09:01] could be a bug in the nvidia driver then. works fine on my gf8600gt [09:01] tseliot might have ideas when he shows up [09:02] where did you upgrade from? [09:02] ok, thanks tjaalton, I'll ask him [09:02] what do you mean, where I upgraded from? [09:02] you said there it used to work [09:03] was it natty or.. [09:03] Oh, I see , I was already in natty, and the xorg+nvida had been held back for a while. As soon as there was a new nvidia driver in main a few days ago, I upgraded [09:03] ok, so it's probably the driver then [09:04] I've had a problem with compiz that it marks part of the screen "dead", where no input goes through [09:04] after resume [09:04] so do you think I shoud add a bug task for 'nvidia-current'? [09:04] yeah [09:05] ok, let me do that. In the meantime, do you think it might be worth going back to the previous xorg+nvidia versions? Are there instructions somewhere to do something like that? [09:06] oh I'm probably seeing bug 723014 [09:06] Launchpad bug 723014 in unity (Ubuntu Natty) (and 4 other projects) "New window tracking system breaks in the case where windows try to restack relative to destroyed windows that were never mapped (affects: 1) (heat: 503)" [Undecided,Confirmed] https://launchpad.net/bugs/723014 [09:07] dpm: that's an invasive change.. it's only possible if you have the old packages around [09:07] aiui [09:08] tjaalton, if it's only a matter of getting the old packages, I can see if they're still in the cache or I can get them from LP [09:08] you'd need nvidia-current, xserver-xorg-core, xserver-xorg-input-evdev (and -synaptics it seems) [09:08] at least those [09:10] ok, I'll give that a go, thanks tjaalton! [09:12] (but after work :) [11:59] hi tseliot, how are you? [11:59] if you've got some minutes, could you give me a hand debugging bug 726496? [11:59] Launchpad bug 726496 in nvidia-graphics-drivers (Ubuntu) (and 1 other project) "Cannot use Unity or Classic desktop with effects after the latest nvidia+xorg update (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/726496 [11:59] hola dpm, fine thanks, you? [12:00] * tseliot has a look [12:00] fine as well, better than my laptop :) [12:01] hehe [12:03] dpm: what does this command say? update-alternatives --display gl_conf [12:05] tseliot, http://paste.ubuntu.com/574939/ [12:06] dpm: it looks fine. What driver/xorg were you using before the upgrade? [12:08] I was using nvidia as well, let me check if I can find out the versions [12:11] tseliot, I think I must have been using 260.19.29-0ubuntu1 [12:11] (nvidia) [12:12] ok, with the old xserver, I guess [12:13] yeah [12:15] dpm: ok, I'll try to reproduce the problem here and then I'll talk to nvidia about it [12:16] sounds great, thanks a lot tseliot! [12:55] dpm: oh, and please attach your nvidia-bug-report.log to the bug report. You can generate it in your home directory by running the nvidia-bug-report.sh script with root privileges [13:53] dpm_: oh, and please attach your nvidia-bug-report.log to the bug report. You can generate it in your home directory by running the nvidia-bug-report.sh script with root privileges [13:57] tseliot, ok, thanks for the heads up, done. [13:57] thanks === dpm_ is now known as dpm [14:14] cnd: Are you around yet? [14:14] lag, yep [14:14] cnd: Great, I have a query [14:14] been a while since I've chatted with you :) [14:14] cnd: I know, UDS I believe [14:14] I've fallen into the world of Linaro [14:14] so long ago :) [14:15] It's a dark place :) [14:15] heh [14:15] I'm currently working on ST-Ericsson's new u8500 [14:15] I have a Ubuntu desktop which is visible on the touchscreen [14:16] When I run evtest, I can see that my presses are being processed, but nothing happens to the desktop [14:16] Is there a missing link I should be aware of/can test in some way [14:17] 20Mpix camera, oh please.. :P [14:17] on u8500 [14:17] tjaalton: Camera is broken :( [14:17] lag: by design it seems :) [14:17] tjaalton: Proprietary [14:17] tjaalton: Where were you looking to see that? [14:18] 20MPix crammed on such a small area means problems anyway [14:18] http://www.stericsson.com/platforms/U8500.jsp [14:19] Ah cool [14:19] lag: https://wiki.ubuntu.com/Multitouch/Testing/uTouchEvEmu#Debugging [14:19] if you can get me the device.prop and a sample device.record files [14:19] then I can figure out what's wrong [14:19] tjaalton: http://www.linaro.org/snowball-announcement/ [14:20] cnd: That's great - then you can teach me how to debug it myself :) [14:20] ahh, I can do that right now if you want [14:20] when you run evtest [14:21] you should see ABS_{X,Y} events [14:21] and I believe you should see BTN_TOUCH go from 0 to 1 when you are actively touching [14:21] cnd: I see: Event: time 1299161597.022652, type 3 (Absolute), code 54 (?), value 591 [14:21] I believe that is all you need for basic single touch touchscreen support [14:21] ahh! you're getting multitouch! [14:21] I am - cool [14:22] * lag 3 finger swipes the board [14:22] Rebooted ;) [14:22] I'll tell you something else ... when I touch the screen, screensaver is still activated [14:22] lag, ok, MT is complicated [14:22] And in the console evtest is still seeing presses [14:23] I don't think I have enough time to run through it all here :) [14:23] I just want it to work? [14:23] if you can get me the evemu files [14:23] When I press Firefox, I want it to open [14:23] I can virtually recreate your device on my machine here [14:23] and figure out what's going on [14:23] That's neat [14:24] yep [14:24] No idea how to install it though [14:24] Where's the ARM *.deb? [14:24] https://wiki.ubuntu.com/Multitouch/Testing/uTouchEvEmu#Debugging [14:24] it's in ubuntu [14:24] just follow the instructions [14:24] cnd: Saw that, but I don't have networking on the device [14:25] oh [14:25] then download it to a usb drive? [14:25] I can put it onto an SDCard - looking for the *.deb now [14:26] cnd: Wooooooo: http://ports.ubuntu.com/pool/main/u/utouch-evemu/ [14:26] lag, isn't this an armel board? [14:26] Yeah [14:26] in which case you can find it at launchpad.net/ubuntu/+source/utouch-evemu [14:26] Is the one at http://ports.ubuntu.com/pool/main/u/utouch-evemu/ incorrect? [14:27] I dunno [14:27] I don't know anything about ports [14:27] :) [14:27] it could be the exact same file for all I know [14:34] cnd: Hopefully there isn't a loooooooong list of dependencies [14:34] lag, I'd be surprised if there was any list of deps, tbh [14:34] it's c, and it operates directly on kernel ioctls and fds [14:35] dpkg: error processing utouch-evemu-tools (--install): [14:35] dependency problems - leaving unconfigured [14:35] lag, you'll need it's lib package [14:35] libutouch-evemu1 [14:35] but that's it [14:35] cnd: Yep, installing that now [14:35] as long as you have libc too :) [14:35] Lots of SD card (which is also used for rootfs) swapping [14:36] heh [14:37] Do I have to do: evemu-device device.prop [14:37] lag, nope [14:37] that's for me to do to debug [14:37] Just the two files yeah? [14:37] yeah [14:37] k [14:37] En route [14:43] cnd: Which repo are those tools in? I'm trying to install them on my desktop [14:43] cnd: Or are they just in your PPA? [14:43] lag, they're in ubuntu [14:44] ubuntu main [14:44] natty [14:44] Oh, not Maverick? [14:44] no [14:44] Ah [14:49] cnd: How's my input situation looking? :s [14:50] lag, I got your files, but it's gonna be a bit for me to get back to you [14:50] one of our team members is leaving tomorrow [14:50] and a bunch of tasks are being doled out [14:50] cnd: NP, I'll move onto something else [14:50] cnd: Thanks [15:15] hi [15:15] is it possible to run GDM inside Xephyr? [15:32] hi [15:33] compiz is crashing like hell on my radeon5450 with ati drivers (natty) [15:33] seb128 suggested to ask here [15:34] I reported bug 728495 about it, will expand it with some new data [15:34] Launchpad bug 728495 in compiz (Ubuntu) "hangs machine on alt-tab or going to screen corner (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/728495 [15:41] other question: I run evolution, it gives me 'add account' wizard and if I cover 'forward' button with mouse all text from window disapears. on second step all is gone too but if I switch to other window then checkbox with 'restore evolution from the backup file' re-appears. [15:50] re [15:53] hrw: which version of libgl1-mesa-dri do you have? [15:53] installed [15:55] probably the latest, just want to make sure [15:55] good question [15:56] *** 7.11.0+git20110203.7535f93e-0ubuntu0sarvatt 0 [15:56] will recheck with default ubuntu one [15:56] it's newer [15:56] the one from natty [15:56] though the edgers one should have the fixes I'm looking at... [15:57] this one is old edgers [15:57] 7.10.1~git20110215.cc1636b6-0ubuntu2 is what I have [15:58] hrw: yeah ppa-purge xorg-edgers, natty should be better off. that edgers one is not using r600g either [15:58] oh :) [15:59] that might explain it then [15:59] I thought that I dropped all from edgers when 6.14 got released [16:00] might want to add edgers to your sources, do an apt-get update (but dont upgrade) and ppa-purge xorg-edgers to make sure it cleans it all [16:00] Sarvatt: 17:00 hrw@home:~$ dpkg -l|grep sarv|wc -l [16:00] 0 [16:01] ok, restrted x11, lets press alt-tab 8 times [16:01] works [16:02] glad it was something easy :) [16:02] yes [16:02] yep :) [16:03] lets now test evo problem [16:03] still exists ;( [16:14] http://marcin.juszkiewicz.com.pl/download/screenshots/evo/ - can someone take a look and comment? [16:21] ok, I need to get rid of compiz [16:21] if I maximize evolution window then it does not accept any input === mdeslaur_ is now known as mdeslaur [17:08] heh, so the diff between winischofers sis driver and the 0.9.1 from xorg is 1.5MB [17:08] and winischofers driver was the basis for SiS's 771/671 work [17:08] actually, the basis was the premium version [17:09] the diff between it and the one from SiS is manageable [17:14] "manageable" meaning less than 1MB, but the SiS version has removed shadowfb and added xvmc === jussi01_ is now known as jussi === yofel_ is now known as yofel === apachelogger_ is now known as apachelogger === jcristau_ is now known as jcristau === popey_ is now known as popey [20:39] ok, color me confused.. this is happening just from updating the kernel to 2.6.38-rc7 from 2.6.38-rc6, even got him to double check its still fine with the old kernel - http://launchpadlibrarian.net/65546346/ThreadStacktrace.txt [20:54] * Sarvatt shakes fist at https://bugs.launchpad.net/ubuntu/+source/nux/+bug/728672 [20:54] Launchpad bug 728672 in nux (Ubuntu) "compiz crashed with SIGSEGV in intel_miptree_image_copy() (affects: 1) (dups: 1) (heat: 18)" [Medium,New] [22:27] bryce_: heads up we're going to get a ton of bugs if 2.6.38-rc7 (2.6.38-6) gets uploaded to natty soon, looks like unity and mutter are busted on it [22:28] (on intel 965+, sorry) [22:29] uh oh [22:29] Sarvatt, ref? [22:29] Eep. On what hardware? Everything, or just intel (or just *some* intel)? [22:29] Aah. So, basically, on all intel. [22:29] Check. [22:29] apw, ^^^ [22:29] Sarvatt: Does the kernel team know about this? It sounds like something they might be interested in :) [22:29] #intel-gfx and the bug I just linked [22:29] looks like fedora is getting a bunch of bugs on it now that they updated too, i've been banging my head trying to figure out whats going on [22:30] https://bugs.launchpad.net/ubuntu/+source/nux/+bug/728672 [22:30] Launchpad bug 728672 in nux (Ubuntu) "compiz crashed with SIGSEGV in intel_miptree_image_copy() (affects: 1) (dups: 1) (heat: 18)" [Medium,New] [22:30] Yay mipmaps! Why are they always the things that are broken? [22:30] https://bugzilla.redhat.com/show_bug.cgi?id=681285 [22:30] bugzilla.redhat.com bug 681285 in mesa "i965: crash in brw_wm_surface_state.c::prepare_wm_surfaces() where intelObj->mt == NULL" [Unspecified,New] [22:31] I asked the guy who reported the nux bug to try reverting c2e0eb167070a6e9dcb49c84c13c79a30d672431, only thing I can see remotely related [23:02] Sarvatt: I presume that bug also happens on mesa 7.10.1? I've updated it in pkg-xorg git now, if you're interested. [23:34] not sure, was afk while waiting for him to test a revert, looks like c2e0eb167070a6e9dcb49c84c13c79a30d672431 (drm/i915: fix corruptions on i8xx due to relaxed fencing) is whats breaking userspace in 2.6.38-rc7 because its fine reverted.. [23:35] and \o/ thanks for updating it there! [23:35] It obviously needs more testing before releasing on an unsuspecting populace, but it's there :)