=== tjaalton_ is now known as tjaalton [09:37] * bryce spams launchpad [09:50] noted :) [10:30] bryce: Shouldn't you be asking people to try with Intrepid? [10:30] bryce: Development ISOs aren't likely to be very good right now. [10:33] and no x related updates there either [10:34] but maybe it'll take 1-2 months for the people to test, so then there'll be some alpha available .) [10:34] :) [10:43] Heh. [10:55] Ohhhh. [10:55] Damn tablets. [10:56] Damn users, too. [10:56] It seems that the Synaptics stuff to gnome-settings-daemon [10:56] Bah. [10:57] it seems that the Synaptics stuff in gnome-settings-daemon causes a DevicePresenceNotify storm when there's a bad Wacom device entry. [10:58] Probably because it initially tries to set the properties on startup, so tries to open the device, which causes X to look for it again, which causes it to send a DevicePresenceNotify, because the device didn't previously exist because /dev/input/wacom doesn't exist. [10:58] Meanwhile the device has already disappeared again, so the device open attempt brings it back. [10:59] Also filling Xorg.0.log very, very quickly. [11:04] hehe [11:18] At least I can reproduce it now. === seb128_ is now known as seb128 [11:44] jcristau: I'm trying to compile a small program which uses xcb but I'm getting an error. Any ideas? http://pastebin.com/d42d7a6ea [11:51] tseliot: libxcb-randr is a separate lib with a separate .pc [11:51] xcb-randr, unsurprisingly enough. [11:52] wgrant: ah, right [11:53] gcc -Wall xrandr-xcb.c -o xrandr-xcb `pkg-config --cflags --libs xcb-renderutil xcb-randr xcb-aux` did it [11:53] Excellent. [11:53] * wgrant also seems to have solved that g-s-d bug. [11:54] \o/ [11:54] DeviceEnabled vs. DeviceAdded isn't well documented, except in the server code. [12:16] tseliot: Is Envy still meant to be used on Intrepid? [12:17] wgrant: envyng-core and envyng-qt [12:18] tseliot: OK, so that would be a yes. Thanks. [12:18] yes [17:09] bryce: are you auto-spamming bugs now? I hardly think I need to provide lspci info for https://bugs.launchpad.net/ubuntu/+source/xfonts-utils/+bug/274266 a bug in a manpage [17:09] Launchpad bug 274266 in xfonts-utils "update-fonts-dir(8) manpage needs updating" [Low,Incomplete] [17:28] sbeattie: care to write a patch for the manpage? [17:35] sbeattie: yes I'm auto-spamming [22:51] hi [22:52] Hi rzr. [22:53] is ~tormodvolden here sometimes ? [22:54] I've not seen him speaking, but he might lurk. [22:54] under which nickname ? [22:58] I have no clue. [22:58] rzr: ^^ [22:59] thx anyway [23:00] rzr: 'tormod' [23:01] oki makes sense [23:12] heya [23:17] Hi bryce_. You had a lot of fun spamming, I see [23:21] wgrant: I did [23:21] so far managed to get a few dozen confirmations of bugs fixed too [23:22] well, fixed or hw no longer available [23:22] And I finally got something more useful than "me too" out of people experiencing that damn g-s-d issue. It's like users are deliberately blocking it. [23:22] Right, I closed a couple this morning as well. [23:22] And in 60 days you can close lots more! [23:22] yep [23:22] I didn't keep a precise count, but there were over 400 New bugs moved to Incomplete [23:22] Oh, nice. [23:23] I just noticed my bugs/x folder rapidly approaching my bugs folder in number of messages. [23:27] wgrant: let me run this next idea past you [23:28] what do you think of this. the next launchpad spam idea I have is to automatically move New bugs with Xorg.0.log + lspci, or Xorg.0.log + backtrace -> Confirmed [23:28] bryce_: I think a tag might be better for that. [23:30] I could tag them as well, but the point is to get them out of New state. [23:30] Hmm, good point. [23:31] I guess moving to Confirmed automatically and Triaged manually would be a reasonable workaround. [23:31] So that would work. [23:32] * bryce_ nods [23:34] ok, switching to my other wireless ap. brb [23:34] For fixing a regression in -proposed, do I attach the debdiff to the original or regression bug? [23:48] 10:34:11 < wgrant> For fixing a regression in -proposed, do I attach the debdiff to the original or regression bug? [23:49] the regression bug [23:49] Great, thanks. [23:49] well, either is probably fine [23:50] I'd do the regression bug though. easier to track. Cross reference them for the release manager's convenience. [23:50] Yep.