[00:06] <racarr> ricmm: Got screen blanking working, an early version (needs some cleanup before proposable) is at lp:~robertcarr/mir/test-android-screen-blanking
[00:06] <racarr> you can see how it works in examples/demo-shell/window_manager.cpp
[00:06] <racarr> can test (hasnt been tested on gnex) by running mir demo server shell and using any hardware button
[00:06] <racarr> which will turn the display on and off
[00:14] <RAOF> racarr: Hey, is there a way to get libmirclient to dump a bunch of debug info via an environment variable?
[00:31] <racarr> RAOF: I think there is MIR_CLIENT_RPC_REPORT=log
[00:36] <RAOF> racarr: Ta.
[00:37] <RAOF> That might have less of a timing impact than gdb breakpoints, which is what I'm currently using.
[00:55] <ricmm> racarr: nice, any chance it can be proposed today?
[00:59] <tvoss> RAOF, http://unity.ubuntu.com/mir/component_reports.html
[01:01] <RAOF> tvoss: Ah, thanks.
[01:26] <rsalveti> kdub: that's fine, mind just opening a bug against libhybris?
[01:26] <rsalveti> will take care of it tomorrow morning
[01:30] <duflu> RAOF: Do you have sufficient hardware to prove bug 1216472 is indeed intel-specific?
[01:32] <RAOF> duflu: I think I have a counterexample in my radeon system, to which I've managed to attach my partially broken second LCD.
[01:32] <duflu> RAOF: "Counter" as in radeon with two outputs works fine?
[01:33] <RAOF> No, as in radeon with two outputs suffers a similar problem.
[01:33] <duflu> Ugh
[01:33] <duflu> RAOF: I've been trying to avoid a simple and ugly workaround (if damage for any output is empty give it one pixel's worth)
[01:33] <RAOF> Although that's somewhat masked by what appears to be “mir with fails to send buffers to radeon with two monitors”
[01:36] <RAOF> A bug which is apparently timing related, as when I dump logs and attach gdb it no longer appears.
[01:38] <duflu> RAOF: Without bypass? :)
[01:38] <RAOF> duflu: Works, but exhibits the frame ordering issue.
[01:39] <duflu> RAOF: Is it possible the breaking-up of the root window is similarly incompatible with multiple DDXen?
[01:40] <RAOF> Possibly?
[01:43] <RAOF> Hm.
[01:43] <RAOF> Not a huge fan of the bug where closing a window will sometimes kill X.
[01:50] <duflu> Doesn't Unity8 solve that? (no way to close apps) ;)
[01:55] <RAOF> Bah. Stupid lttng.
[01:55]  * RAOF lunches
[03:34] <jrr> yay heisenbug
[04:50] <alf|xmir-devel> RAOF: duflu: Could some of our problems be caused by xmir creating a mir surface for each output, which for "clone" mode end up at the same area in our virtual space (e.g. both have top-left at 0,0)?
[04:50] <RAOF> alf|xmir-devel: That's possible (and I'm pretty sure there's at least one damage-tracking bug in there), but this occurs with non-overlapping outputs, too.
[05:03] <alf|xmir-devel> RAOF: btw, thanks to Marteen's investigation, we believe that the egl image problems for nested mir are caused by having different dri2 screens for egl and gbm. At least for the nested mir case (i.e. optionally), we need to pass the used gbm_device to platform mir and initialize the egl dri2 using the gbm dri2 setup (liked platform_drm does). Do you see any possible blockers with this approach?
[05:33] <RAOF> robert_ancell: DEB_BUILD_OPTIONS="notest" bzr bd -- -us -uc
[05:33] <RAOF> robert_ancell: DEB_BUILD_OPTIONS="notest parallel=9 nostrip noopt" bzr bd -- -us -uc
[05:39] <duflu> alf|xmir-devel: I can't yet imagine how it would cause functional problems, but sounds like bug 1216748
[05:57] <RAOF> alf|xmir-devel: You mean that the nested server's EGL needs to use the same drm fd as the nested server's mir platorm?
[06:27] <alf|xmir-devel> RAOF: no, it must use the same dri2 screen/implementation as the gbm_device the nested server is using, so that it can share resources proprely (e.g. like the bo image).
[06:29] <RAOF> alf|xmir-devel: Can we do that?
[06:33] <alf|xmir-devel> RAOF: platform_drm seems to be doing exactly that, so it seems possible... although we won't know for sure until we try.
[06:50] <duflu> RAOF: This looks related to out of order frames... The DDX is accessing the MirBufferPackage after free(); bug 1224296
[06:50] <RAOF> Thanks for the pointer.
[06:50] <RAOF> (Bam, ching!)
[06:53] <duflu> RAOF: Does X build with symbols by default? I did not expect "??"
[06:53] <RAOF> You'd need to install xserver-xorg-core-dbg
[06:53] <RAOF> And the corresponding intel -dbg, too.
[07:09] <hikiko> duflu, are you still getting the crash with the drm permission message? in a fresh installation I got it once and then I upgraded and since then I've restarted lightdm more than 20 times and I dont get it
[07:09] <duflu> hikiko: Yeah occasionally. As many people do. Seems to be the most popular Mir bug :(
[07:11] <hikiko> ouf :/ what might happened and I cant reproduce it anymore :S unity compositor + mir are running for sure and I was getting it until 1 hr ago when I upgraded :S :S
[07:12] <duflu> RAOF: OK, got full debug symbols. Now doesn't look related to frame order... bug 1224296
[07:12] <duflu> Also bug 1221616
[07:14] <RAOF> duflu: Aha. Thanks.
[07:29] <duflu> As it happens, both bugs now look like things ickle was very vaguely referring to a while ago, but failed to explain or pinpoint
[07:39]  * RAOF fixes it, and goes to see if it magically fixes everything
[07:46] <RAOF> Oh, right.
[07:46] <duflu> RAOF: I expect it will *only* make mode setting more stable... ?
[07:46] <RAOF> Yes, that's a bit silly
[07:47] <mlankhorst> or is it?
[08:14] <RAOF> mlankhorst: Me DestroyPixmap()ing a Pixmap that I didn't allocate *is* a bit silly, yes :)
[08:16] <mlankhorst> depends, were you allowed to do so?
[08:19] <RAOF> ...maybe.
[09:19] <robert_ancell> bye all, see you in Boston
[09:24] <alan_g> alf|xmir-devel: Update pushed to https://code.launchpad.net/~alan-griffiths/mir/combine-nested-gbm-and-android/+merge/185054
[09:26] <alf|xmir-devel> alan_g: thanks, I will check in a bit, my experiments have broken XMir currently :)
[09:27] <alan_g> alf|xmir-devel: I expect you to learn from your experiments. ;)
[09:43] <mpt> Is it possible to open a surface without specifying what size it is? (If not, there's no point remembering the size of a surface to restore it next time, like we would for position.)
[09:43] <smspillaz> mpt: you need to specify the size
[09:43] <mpt> ta
[09:44] <smspillaz> mpt: also nonzero positions aren't supported (yet) iirc
[09:44] <mpt> smspillaz, okay, so Mir has complete control of (absolute) position, while the app has complete control of size.
[09:45] <mpt> (Unless it requests a size larger than any display, I guess.)
[09:46] <smspillaz> mpt: it technically has complete control of both
[09:46] <smspillaz> (mir)
[09:46] <mpt> yeah, hence the brackets :-)
[09:46] <smspillaz> part of the reason for using server side buffer allocation was so that we could limit the memory usage of applications
[09:47] <smspillaz> so its theoretically possible that you could be denied certain sizes
[09:47] <smspillaz> however, I don't know any good reasons other than memory pressure as to why that would be done in practise
[09:48] <duflu> smspillaz: I'm /told/ much because that's the way Android does it ... (?)
[09:49] <duflu> mpt: Clients (apps) have no control over position. Although there is a hint for what monitor to appear on (used by XMir)
[09:50]  * duflu migrates to the laptop
[09:50] <mpt> smspillaz, if you close a document that was open on a Cinema Display, then reopen it when the only display is a tiny ThinkPad, Mir shouldn't let it open at its previous size.
[09:52] <smspillaz> mpt: it doesn't matter, the application makes the request for the buffer size
[09:53] <smspillaz> the point I was trying to make is that you may (as an application) request a size of M x N
[09:53] <smspillaz> but if you're under memory pressure then you might get something smaller
[09:53] <smspillaz> I wouldn't imagine there'd be any policy implemented on the display server side to prevent applications from creating big windows otherwise
[09:54] <smspillaz> generally as a display server you should probably just respect what the client wants unless it creates a security or performance problem
[09:54] <mpt> smspillaz, I'm writing up the policy right now ... I guess it's window manager level rather than display server level, though.
[09:55] <smspillaz> *shrug* I'm not involved with mir's development so I don't care that much
[09:55] <mpt> Thanks for the answers. :-)
[09:55] <smspillaz> though I will say that trying to have the window manager control application sizes is a bad idea for multiple reasons
[09:56] <smspillaz> mostly because the edge cases end up in the window manager and not the individual applications
[09:57] <mpt> smspillaz, what I have currently is that the only case, where the window manager will force a smaller size, is where there is no display available large enough to show it at the requested size
[09:58] <smspillaz> makes sense
[09:58] <smspillaz> mpt: it might be worth discussing that with the developers directly though :)
[09:59] <mpt> For sure, I only asked the channel in general because tvoss wasn't here. :-)
[10:01] <alan_g> mpt: The general answer is that the Mir library provides hooks for the shell to intercept and tailor the requests. And it is the shell that sets the strategy.
[10:06] <mpt> ta
[10:20] <mpt> tvoss_, have you given any thought to how toolkits will place tooltips close to the screen edge, when they don't know how close the window is to the screen edge?
[10:20] <mpt> how close the parent surface is, I mean
[10:21] <tvoss_> mpt, not yet, but the idea I have in mind is like: apps provide an anchor point in surface relative coordinates, and unity decides where to put the surface depending on closeness to the edge
[10:23] <mpt> tvoss_, makes sense.
[10:24] <tvoss_> mpt, cool
[14:27] <hikiko> question: in /etc/init.d/ there's a lightdm script that should print some messages, where are these messages printed? I cant see them at syslog + I inserted some echo "foo" >> /tmp/foo but there's no /tmp/foo when I restart lightdm... I didnt find any relevant info in the upstart documentation so far any idea?
[14:29] <alf|xmir-devel> hikiko: /var/log/lightdm/*
[14:30] <hikiko> no alf|xmir-devel
[14:30] <hikiko> I dont want to get the lightdm log
[14:30] <hikiko> I want to get the output of the script that starts the lightdm
[14:30] <hikiko> in /etc/init.d
[14:30] <hikiko> to see if a signal is send twice
[15:40] <kgunn> kdub: ping
[15:40] <kdub> kgunn, pong
[15:40] <kgunn> kdub: hey...gotta request...can you flash the pending image http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/pending/
[15:40] <kgunn> this contains mir, but not on by default
[15:41] <kdub> okay, will try
[15:41] <kgunn> to turn on....just modify the /etc/environment file...for QT_QPA_PLATFORM=ubuntumirclient
[15:41] <kgunn> then, rename/delete SF
[15:41] <kgunn> on nexus4
[15:41] <kgunn> and see what you see :)
[15:42] <kgunn> team in lexington is claiming its flickering very very bad...but want to know what you see
[15:42] <kgunn> kdub: greyback says he does not see this flicker on galaxynexus
[15:42] <kgunn> kdub: guys in lexington said they saw it on nexus4
[15:43] <kgunn> racarr: ^ ...in case you're awake & on :)
[15:44] <kgunn> kdub: racarr ... i am trying here....but fear messing something up...(first time i did this...it was stuck at google splash)
[15:47] <kgunn> on my second attempt
[15:48] <greyback> kgunn: I'm having same problem actually. It's like upstart isn't starting hte user session any more. Did mterry's stuff change that?
[16:03] <kgunn> greyback: hmm...so i'm using pending, adb pull etc/environment, modify to QT_QPA_PLATFORM=ubuntumirclient, then adb push, then adb remount, rm /etc/bin/surfaceflinger, reboot
[16:03] <kgunn> i get stuck at splash every time
[16:04] <greyback> kgunn: perfect. I'm getting the same. unity8 isn't being started
[16:05] <greyback> kgunn: if you adb in, can run it manually with "GRID_UNIT_PX=18 QT_QPA_PLATFORM=ubuntumirserver unity8"
[16:05] <greyback> but the lenses and indicators are not running either
[16:06] <greyback> so it's kinda blank
[16:06] <kgunn> greyback: couldn't decipher mterry's response...so is it related ?
[16:06] <kgunn> do we need to go whine to asac to get that last piece in?
[16:06] <greyback> kgunn: I don't think so. But something has changed, and I've no idea what
[16:07] <kgunn> greyback: did you ever get past the splash (....thot you said you saw flicker at some point)
[16:07] <greyback> kgunn: well I need someone who understand the upstart situation to help out
[16:07] <kgunn> greyback: oh duh...you manually launched
[16:07] <greyback> kgunn: I ran it manually with that command. And can launch and switch apps when
[16:07] <greyback> s/when/then/
[16:08] <kdub> i get 'Library unity-mir not found/loaded "
[16:10] <kgunn> kdub: what the what? ^ greyback
[16:11] <greyback> kgunn: aha, that was fixed in trunk. As workaround, please install "libunity-mir-dev"
[16:11] <greyback> kdub: ^^
[16:11] <dandrader> where mir log goes by default?
[16:11] <kdub> /tmp/
[16:12] <dandrader> ok, thanks
[16:14] <kdub> dandrader, --glog-log-dir can change the directory
[16:14] <kdub> greyback, how do you normally compile unity8 for the phone?
[16:15] <kdub> i've been trying in an armhf chroot on and off, never seem to have much luck with that method
[16:15] <dandrader> kdub, does logging work as usual even when you run those examples like mir_demo_standalone_input_filter?
[16:15] <greyback> kdub: on the device itself. I've also not got chroot working
[16:16] <kdub> dandrader, i think it should, haven't tried with that specific example though
[16:16] <greyback> kdub: this is closest I've got: https://wiki.ubuntu.com/SimpleSbuild
[16:16] <greyback> but I'm stuck on older kernel without aufs (don't ask), and I need to compile it myself. Never got around to it
[16:18] <kdub> greyback, thanks, i guess i'll try on the phone
[16:19] <kdub> greyback, now i get "ASSERT: "!isEmpty()" in file /usr/include/qt5/QtCore/qlist.h, line 288
[16:19] <kdub> "
[16:20] <greyback> kdub: no idea how you got that. Please apt-get update everything, then check QT_QPA_PLATFORM=ubuntumirclient in your env
[16:21] <alan_g> kdub: re problem I'm seeing with multiwin under nested. If I increase the alpha (to, say, 0xe0) then it works - does that suggest anything to you?
[16:22] <kdub> alan_g, that the alpha is being mis-set somewhere
[16:23] <kdub> alan_g, it could just be that the alpha in the example has to be turned to opaque
[16:24] <alan_g> kdub: I do get show through - so it isn't just treating as opaque
[16:28] <kdub> greyback, still getting that isEmpty() error after the upgrade :/
[16:30] <kdub> alan_g, perhaps the example is picking the wrong pixel format?
[16:31] <kdub> greyback, maybe there's a ppa i haven't installed?
[16:31] <greyback> kdub: what device are you using? No ppa is necessary
[16:32] <kdub> mako
[16:32] <alan_g> kdub: It looks right. (And why the different behavior in nested - it ought to be nested code that causes problems).
[16:33] <kdub> alan_g, perhaps the incorrect egl configuration is chosen
[16:34] <kdub> let me check...
[18:30] <kgunn> kdub: new image...http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/pending/
[18:30] <kgunn> greyback: ^
[18:30] <kgunn> racarr: ^
[18:31] <kdub> kgunn, is it important to test the image? i was just going to see if i can compile it myself to see the flicker
[18:31] <greyback> kgunn: yay
[18:31] <kgunn> kdub: nah...keep compiling
[18:32] <kgunn> i was just pointing it out....it only _might_ be interesting
[18:32] <kgunn> it could also be a mess
[18:32] <greyback> I'll downloading it now, will let oyu know
[18:32]  * greyback decided not to bother about correct English any more
[18:33] <kgunn> dude...aren't you irish ??....you're worse than american :)
[18:33] <kdub> me fail english? that's unpossible!
[18:34] <kgunn> only american's allowed to butcher english....and not speak any other languages to boot :)
[18:41] <racarr> *clinks red white and blue power rings with kgunn and kdub*
[18:41] <racarr> America!
[18:43] <kgunn> racarr: ....its wonder twins power activate
[18:43] <racarr> lol
[18:44] <racarr> ill test the image
[18:46] <kgunn> racarr: http://www.youtube.com/watch?v=ktUx57i63e0
[18:46] <kgunn> explains alot about my inner workings ^
[18:50] <kgunn> ...oh... racarr i just got it... note america.... 'merica!
[18:51] <greyback> oh for the love of all that's holy
[18:52] <kgunn> hmmm...im still stuck at splash (w.o command line)
[18:52] <greyback> me too :(
[18:52] <greyback> kdub: and now I get your failure too
[18:53] <kgunn> hmmm...it complains on command line for me
[18:53] <kgunn> seg fault
[18:55] <greyback> and has weird backtrace. http://pastebin.ubuntu.com/6098316/
[18:55] <greyback> wtf is happening?!
[18:57] <racarr> How to use bzr
[18:57] <racarr> I can't merge trunk int o dpms-support-api without it...removing all of dpms
[18:57] <kdub> racarr, that's happened to me before, shortcoming of bzr
[18:58] <kdub> i usually just make a patchfile and apply on top :)
[18:59] <racarr> :( yeah
[18:59] <racarr> or you can do reverts
[18:59] <kdub> well, might be a shortcoming of bzr, or a shortcoming of my knowledge of how to use bzr
[19:00] <greyback> kdub: try "export QT_SELECT=qt5" and then try shell
[19:01] <greyback> no actually, no good either
[19:04]  * greyback needs to EOD
[19:06] <kdub> mmk
[19:16] <kgunn> kdub: gonna step out for a very late lunch (read as errands)
[19:16] <kgunn> let me know how your build effort concludes
[20:21] <racarr> Lunch
[21:21] <kgunn> kdub: curious how your build is going ?...went ?
[21:24] <kdub> kgunn, still going :) arm compiles
[21:25] <kdub> tinkering with the mali604 in the meantime
[21:26] <kgunn> ooo you must be native compiling
[21:26] <kdub> yeah, i had some issues with a qemu/chroot compile (which greyback said he had too)
[21:49] <kdub> kgunn, i still get that isEmpty() error from qlist.h with the version i compiled
[21:58] <kgunn> :-/
[22:44] <kdub> the mali driver is a bit weird... but got just got a client frame to render!
[23:51] <kgunn> kdub: \o/


[00:24] <psusi> cjwatson, well I'm trying to attach what I think is the final draft of that patch to the bug report but firefox is being fubar and won't select the right file.... going to see if an update and reboot fixes it...
[00:52] <siddhartha> hello,sorry about the noob-ness.. i have a question: i was running a karmic installation.. i somehow managed to change change my release type to eeebuntu after adding some package repos.  Recently i added lucid repos. Is there any way to change the distribution release type ? lsb_release -a tells me im still running eeebuntu.
[00:54] <siddhartha> hello,sorry about the noob-ness.. i have a question: i was running a karmic installation.. i somehow managed to change change my release type to eeebuntu after adding some package repos.  Recently i added lucid repos. Is there any way to change the distribution release type ? lsb_release -a tells me im still running eeebuntu.
[00:55] <arand> siddhartha: -> #ubuntu or #ubuntu+1
[00:56] <Sarvatt> slangasek: I'm guessing its the vga=795 (aka 1280x1024x24bpp) boot option they are passing to a vga16fb.. :D
[00:58] <siddhartha> leave #ubuntu-devel
[02:14] <slangasek> Sarvatt: nope, the fact that they're *using* VGA16 is proof that the vga= option had no effect (which probably means they're using grub2)
[02:16] <slangasek> Sarvatt: if vga= had worked, /proc/fb would show vesafb as fb0 instead of vga16fb
[03:13] <nixternal> slangasek: any pointers on creating a custom plymouth theme? the one I created yesterday will not work with the new plymouth, it always falls back to the ubuntu one
[03:13] <slangasek> nixternal: are you using update-alternatives?
[03:13] <nixternal> yes
[03:13] <nixternal> update-alternatives --config default.plymouth
[03:14] <slangasek> er - you're not doing that in the maintainer scripts, are you?
[03:14] <nixternal> no no, I am doing this locally
[03:14] <slangasek> ok
[03:14] <nixternal> not in packaging at all
[03:15] <slangasek> well, the only fallback path is between default.plymouth and text.plymouth
[03:15] <slangasek> does /etc/alternatives/default.plymouth point where you expect?
[03:15] <nixternal> yup
[03:15] <slangasek> can you post the theme somewhere?
[03:15] <slangasek> sounds like the theme is simply failing to load
[03:15] <nixternal> oh, no it doesn't
[03:15] <nixternal> there is the problem
[03:15] <slangasek> ok :)
[03:15] <nixternal> hrmm
[03:15] <nemo> Did you guys drop libcaca from libSDL?
[03:16] <nemo> (Karmic/Lucid)
[03:18] <nixternal> hrmm
[03:18] <nixternal> still falls back to ubuntu dangit
[03:19] <nixternal> I am guessing we can't use the fade-in example with anything other than ubuntu now slangasek?
[03:20] <slangasek> ScottK: so there's one flaw in the proposed methodology on foundations-lucid-supportable-binaries: we know whether the source package FTBFS at the beginning of the cycle, but we don't know whether there were binaries *of that version* in the archive at the time without doing a lot of LP parsing; so if the package was FTBFS /at the time it was uploaded/, but has subsequently built, we have no good way to distinguish those binaries that we
[03:21] <slangasek> ... successfully built *afterwards* from those that were built *earlier*.
[03:21] <slangasek> nixternal: what do you mean?
[03:21] <slangasek> the fade-in theme isn't Ubuntu-specific; it doesn't even include an Ubuntu logo
[03:22] <nixternal> but it uses the ubuntu logo no matter what
[03:22] <nixternal> wth...I just did the xubuntu-logo theme, and on shutdown it worked, but on startup it went back to the ubuntu logo again
[03:22] <slangasek> did you forget to rebuild an initramfs?
[03:23] <nixternal> shush :p
[03:26] <nixternal> slangasek: ok, got it working, however the fade-in theme is locked to the ubuntu logo...i have another fade-in theme from fedora that was the stars and it worked yesterday
[03:28] <slangasek> ScottK: so - if we remove all the binaries that are built from source <= the version that failed in the rebuild test, we risk nuking some that do actually build successfully now, and only FTBFS then because of a bug in a different package
[03:29] <slangasek> ScottK: I can't say how many packages will be affected by this - if I could say, I wouldn't have to worry in the first place :) - but the number of source packages showing up in my report is much lower than the number in Lucas's latest rebuild
[03:29] <slangasek> ScottK: so I'm inclined to propose them all for removal anyway
[03:30] <slangasek> nixternal: ah yes, I can confirm this in the source - the logo path has to be compiled into the splash plugins, and points at /lib/plymouth/ubuntu-logo.png
[03:30] <slangasek> nixternal: so if you want to use one of the other splash plugins with a different logo, you'll need to dpkg-divert /lib/plymouth/ubuntu-logo.png
[03:32] <slangasek> nixternal: note that if you do a dpkg diversion of this file in a package, you will need to also Conflict: with any other theme packages that want to divert the same file
[03:32] <slangasek> (maybe this should have also been an alternative, hmm)
[03:37] <nixternal> slangasek: yeah, I don't feel like doing a divert, so I will go with something else in the mean time
[03:42] <slangasek> nixternal: oh, and if this is for packaging, the only base theme that integrates with mountall is the ubuntu-logo theme; so I don't advise basing off any of the others if you're planning to ship this by default for a flavor release
[03:43] <nixternal> right, that is what I am basing the kubuntu one off of now
[03:45] <superm1> slangasek, is there going to be an alternative for just replacing the logo in the ubuntu-logo theme?  it seems kind of silly to reproduce all the logic in the script in individual themes and have to keep up with syncing it all the time then
[03:50] <slangasek> superm1: if you're only replacing the logo and want to leave the colors and fonts the same, dpkg-divert on the logo would do the job; but an alternative may be the better way to go for scalability, so I'd suggest filing a bug on plymouth about this and I'll talk to Keybuk on Monday
[03:51] <superm1> oh yeah, i forgot that the default background for ubuntu-logo isn't black, so some folks might not want that
[03:52] <superm1> i'll file a bug though still
[04:15] <slangasek> superm1: hum, see my follow-up
[04:16] <slangasek> superm1: perhaps that unblocks you for what you're trying to do
[04:17] <superm1> slangasek, yeah that should help a lot, thanks!
[04:28] <ScottK> slangasek: What about doing on the list at the start of the cycle and still out of date?
[04:29] <ScottK> I think that gets us to the same place.
[04:29] <slangasek> ScottK: that misses packages that are up-to-date because they built prior to lucid and haven't been uploaded since
[04:29] <slangasek> ScottK: so do we want the false-positives, or the false-negatives?
[04:29] <ScottK> Right.
[04:31] <ScottK> slangasek: On the list at the start of the cycle and (still out of date or version == the version on the list)?
[04:32] <slangasek> that runs into the same false positives as before
[04:33] <slangasek> it doesn't tell us if it was on the list at the start of the cycle because of a bug in the package, or a bug in its build-deps
[04:33] <ScottK> slangasek: We don't care why, just that we can't build it.
[04:34] <slangasek> it doesn't tell us we /can't/ build it, it tells us we /couldn't/ build it then
[04:34] <ScottK> OK.  One more try.
[04:35] <slangasek> I'm ok to say "yes, we may be removing packages that build fine now in the rare case that they built before, failed to build in November, and are buildable again today"
[04:35] <slangasek> I just want to be clear that this is what we're saying
[04:36] <ScottK> Check that list against the latest rebuild list.
[04:37] <slangasek> ah, that works
[04:37] <ScottK> If it isn't on that list, then it's OK.  If it's not out of date, ignore it, if it's out of date, give it a retry.
[04:37] <ScottK> Does that work?
[04:38] <slangasek> yep (hmm, which of us is lagged? :)
[04:39] <psusi> well that was messed up... had to delete my firefox profile to get it to stop inserting the wrong file in the upload dialog on lp... it kept putting in the one above the one I clicked.... in the process I noticed two other things really fubar... the first was ctrl-alt-F1 no longer switches to a tty, and the second is when I logged in a guest session, it got access denied trying to ls /home despite the fact that /home is world readable
[04:39] <psusi> were either of those last two intentional?  and if so, how the hell was the second one done? ;)
[04:40] <slangasek> the guest session is done with apparmor
[04:40] <slangasek> ctrl-alt-f1 is not intentional
[04:40] <psusi> plymouth bug?
[04:41] <slangasek> no
[04:41] <slangasek> not unless you're running an old version of plymouth
[04:41] <psusi> just upgraded
[04:42] <ScottK> slangasek: I was lagged.  My wifi router was bought when we had one wifi device in the house.  I think we have about 10 now.  Every now and then it has a conniption.
[04:43] <ScottK> Also we have 4 7 year olds over for a slumber party tonight, so every now and then, I have to go restore order.
[04:43] <psusi> grrr.... well I guess that explains it... still very frustrating getting access denied on something world readable, heh...
[04:55] <slangasek> ScottK: right - cross-referencing with http://udd.debian.org/cgi-bin/ubuntu_ftbfs.cgi removes 103 source packages from the cull list, leaving 125
[04:56] <ScottK> I'm suprised it's not more.  That's good news I guess.
[04:56] <ScottK> Of the 103 are any currently out of date and needing to be tried again?
[04:56] <ScottK> If there are, shoot me a list and I'll take care of them.
[05:00] <slangasek> hmm, let me see
[05:07] <slangasek> ScottK: libpoe-component-client-dns-perl is the only one
[05:07] <ScottK> OK.  I'll have a look
[05:07] <ScottK> Thanks.
[05:08] <ScottK> Retried, we'll see.
[05:16] <ScottK> slangasek: Odd.  The retry on that failed.
[05:16]  * ScottK throws up his hands and says "Perl, meh!"
[05:16] <slangasek> is it possible that it failed to be included in lucas's latest rebuild run at all?
[05:17] <slangasek> (the page I'm pulling from only shows me confirmed failures, it doesn't confirm the names of the packages that succeeded)
[05:17] <ScottK> Perhaps.
[05:17] <ScottK> Maybe lucas will read the scrollback and check.
[05:17] <slangasek> lucas: ^^ :)
[05:19] <slangasek> "t/06_hosts.t" - looks suspiciously like a test suite whose success depends on the buildd environment's network config
[05:20] <ScottK> Wouldn't suprise me.  Since it's arch all it never hits a buildd in Debian.
[05:28] <genii> I'm affected by bug 545585  , 2 days ago the bug report says "This bug was fixed in the package linux - 2.6.32-18.27"   Is there a timeline when -18 will be in the repositories?
[05:29] <crimsun> genii: it's already in the repo.
[05:30] <genii> crimsun: Weird. dist-upgrade reports nothing available (I'm still on -17 but using -16 for stability due to this bug)
[05:31] <crimsun> genii: your mirror probably hasn't synced yet
[05:33] <genii> Strange. apt-cache search shows it but dist-upgrade reports no kernel updates.
[05:34]  * genii manually installs
[05:37] <wgrant> It looks like the new linux-meta isn't out yet.
[05:37] <wgrant> That's required to pull in the new ABI.
[07:28] <diwic> How do I easiest make a debug build of a package?
[07:29] <wgrant> diwic: There are pre-built debug symbols for all packages in the archive. See ddebs.ubuntu.com
[07:30] <diwic> wgrant, yes, I've tried that, but when I try to debug the line just jumps up and down, I guess I need to build with -O0 to avoid that
[07:31] <diwic> i e when I press "next" in ddd/gdb the next line is often not the expected one
[07:32] <diwic> I guess, due to aggressive inlining and other optimizations
[09:01] <lucas> slangasek: yes, tests hanged, so I had to kill it manually => did not fail, but did not succeed.
[09:01] <slangasek> lucas: could you give me a list of those?
[09:04] <lucas> slangasek: on http://people.ubuntuwire.org/~lucas/ubuntu-nbs/, there are files with the full results on i386 and amd64
[09:13] <slangasek> lucas: so the 'Unknown's in http://people.ubuntuwire.org/~lucas/ubuntu-nbs/res.lucid.{i386,amd64} are what I'm looking for?
[10:40] <pecisk> kenvandine, ping? :)
[11:01] <geser> slangasek: removals in Debian are still imported into lucid, right? or are removal bugs needed?
[11:03] <gnomefreak> were the daily alt. ISo's moved?
[11:03] <gnomefreak> http://cdimage.ubuntu.com/daily/current/ doesnt have them
[11:07] <lifeless> gnomefreak: releases.ubuntu.com
[11:09] <gnomefreak> lifeless: those are daily builds? why wasnt desktop image moved
[11:09] <gnomefreak> http://cdimage.ubuntu.com/daily-live/current/ has daily desktop
[11:11] <gnomefreak> releases.ubuntu is the latest released ISO (beta1)
[11:12] <sabdfl> slangasek: what's the protocol to request a sync from Debian now, for schroedinger?
[11:29] <lifeless> sabdfl: well, its a new upstream, so requestsync --lp -d unstable -e schroedinger
[11:29] <lifeless> unless 1.0.8->1.0.9 is bugfix only from upstream, in which case drop the -e
[11:36] <mattn> hi
[11:36] <mattn> i'm trying to build a package that adds a new entry to /etc/services
[11:36] <mattn> is there a debian-way to do this?
[11:38] <pecisk> mattn, why would you do that?
[11:39] <mattn> to see the service when doing netstat -l for my package ;)
[11:39] <mattn> or should one not add local services at all?
[11:39] <lifeless> submit a patch to netbase
[11:40] <aburch> Actually, ask IANA (see the header of /etc/services)
[11:41] <lifeless> aburch: actually, I think you need to see the header :)
[11:41] <Laney> I'm getting this aptitude core reasonably reliably now
[11:41] <lifeless> "or are needed by a Debian package" is in that header.
[11:41] <lifeless> mattn: you could see the nmap package, a comment in services suggests that nmap might add more, in some fashion.
[11:42] <mattn> good idea - thanks
[11:43] <mattn> looks like it delivers some own service file
[11:45] <cjwatson> lifeless: (gnomefreak has left, but FYI) daily builds are never on releases.u.c - if they're missing from cdimage, it's because the build failed (probably several times in succession)
[11:46] <cjwatson> geser: you need to file removal bugs - semi-automatic removal processing stops at DIF
[12:46] <lifeless> cjwatson: oh, ok
[12:47] <lifeless> cjwatson: thanks
[14:10] <WoAnerges> hi guys!
[14:10] <WoAnerges> have VAIO with "ATI mobility radeon HD 4570" and Intel Core2 DUO T6600 @ 2.2GHz.
[14:10] <WoAnerges> can't install ubuntu 10.04 normally. problems with video appearance.
[14:10] <WoAnerges> need help.
[14:11] <WoAnerges> i know - the image in attachment - it looks like video card owerheat, but it's not an owerheat of vc processor. i am sure about that, because i had a vc that was damaged by owerheating. this is not that case. i think there's a compability problem with laptop hardware. dear development team,,, you must fix it :S
[14:11] <WoAnerges> don't leave me without ubuntu. (=
[14:11] <WoAnerges> http://ubuntuforums.org/attachment.php?attachmentid=151676&d=1269750326
[14:12] <azeem> WoAnerges: please ask in #ubuntu
[14:12] <WoAnerges> they sent me here
[14:12] <WoAnerges> :(
[14:12] <WoAnerges> i feel like in a hospital!!!
[15:45] <lucas> slangasek: yes
[16:39] <BenHoltz> hey everyone i need some help with my ubuntu instalation.  I have upgraded to the 10.04 version and I'm having problems with grub loading.  Can someone point me in the right direction to re-configuring grub?
[16:40] <BenHoltz> i just  read the topic, i will take this to #ubuntu
[18:13] <slangasek> geser: I think a removal bug is a good idea
[18:33] <ari-tczew> can we add a patchsystem in SRU?
[18:50] <blistov> oi. Lucid Beta, up to date as of this minute, host disk is a single 7500RPM SATA2 disk which moves ~90MBps, ext3/ext4 fs, libvirt/kvm linux guests get ~20MBps max, and windows guests get <4MBps max, using any emulation mode (ide/scsi/usb, and virtio for linux)
[18:51] <blistov> If I put the guest image on dev/shm, I get about 20MBps in Windows guests and about 250MBps in Linux guests.
[18:51] <blistov> Any idea's?  Haven't found any bug report yet.
[18:52] <sladen> blistov: file one please
[19:09] <blistov> sladen, do you think this should be filed under kvm or libvirt?  Same response from qemu.
[19:10] <cnd_mini> I'm working to clean up the linux-firmware-nonfree package, and I've come across the lintian tag stating that there's no valid copyright statement in debian/copyright
[19:10] <cnd_mini> I'm not sure who the copyright should be assigned to
[19:11] <cnd_mini> it's a native package with no upstream, and it's just a bunch of non-distributable firmware files
[19:20] <sladen> blistov: you can attach the same bug to both
[19:21] <sladen> blistov: eg. created it again qemu, then click "also affects distribution (Ubuntu)" and add kvm/etc
[20:27] <cjwatson> ari-tczew: please don't - just work with whatever's in place right now
[20:28] <cjwatson> cnd_mini: there doesn't have to be a single answer - you're supposed to list all the copyright statements and licences and which parts of the package they apply to
[20:54] <psusi> cjwatson, you get a chance to look at my last revision of the parted patch?
[21:02] <jono> can anyone tell me where the purple ubuntu wallpaper lives on an ubuntu system
[21:03] <zyga> jono: I think it's called warty-final
[21:03] <zyga> just dpkg -S warty
[21:04] <zyga> it should find it
[21:04] <zyga> it's in /usr/share/backgrounds AFAIR
[21:06]  * psusi kicks debugfs... says there are extra inode fields there, but won't show what they are or let you manipulate them
[21:11] <rlameiro> what is the name of the propietary drivers installer?
[21:12] <crimsun_> jockey?
[21:12] <rlameiro> ok
[21:14] <rlameiro> ok jockey gives me this error SystemError: installArchives() failed
[21:14] <rlameiro> trying to install a broadcom driver
[21:14] <rlameiro> does anyone here come into this?
[21:16] <zyga> rlameiro: did you run it from command line?
[21:16] <rlameiro> yes
[21:16] <rlameiro> zyga, it doesnt output nothing
[21:16] <rlameiro> does it have a verbose option?
[21:17] <rlameiro> no it doesnt have verbose option
[21:17] <rlameiro> it just output a error message saying
[21:18] <rlameiro> SystemError: installArchives() failed
[21:18] <zyga> hmm, if it's written in python (SystemError hints that)
[21:19] <zyga> it probably has a log file somewhere, can you check the source code of what it does?
[21:20] <rlameiro> try to look at it
[21:23] <cjwatson> psusi: I haven't been at my laptop all day, sorry
[21:23] <zyga> rlameiro: me?
[21:24] <rlameiro> zyga, no, me :D
[21:24] <rlameiro> I didnt find anything
[21:24] <psusi> cjwatson, ahh, ok... well I'm satisfied with those parted changes and have gone back to working on e2defrag... hope you get them in for beta 2
[21:25] <cjwatson> psusi: I certainly intend to!  I want to get those bugs closed
[21:25] <zyga> rlameiro: did you run jockey-gtk or jockey-text?
[21:25] <cjwatson> psusi: it's on my list for Monday
[21:25] <rlameiro> gtk version
[21:26] <rlameiro> zyga running the text version now
[21:26] <zyga> rlameiro: I'm checking the source now, please run the text version
[21:26] <rlameiro> it outputs nothing
[21:26] <rlameiro> just says searchinf for available drivers and then quits
[21:28] <zyga> rlameiro: I ran jockey-gtk via strace to check if it opens any files but it seems not to
[21:28] <zyga> so chances for log files are none
[21:28] <rlameiro> in text mode i made this
[21:28] <rlameiro>  sudo jockey-text -e kmod:wl
[21:28] <rlameiro> and the result was exactly the same
[21:29] <rlameiro> i think there are some bugs already
[21:29] <rlameiro> but this on beta1,
[21:29] <rlameiro> i am running ubuntustudio, could it be for that?
[21:30] <zyga> rlameiro: I think that some part of jockey is catching exceptions and not showing the backtrace
[21:30] <zyga> rlameiro: I don't know
[21:30] <rlameiro> zyga, maybe jockey is calling some lib or other script ...
[21:31] <rlameiro> do i have a way to know that?
[21:31] <zyga> rlameiro: most likely apt stuff
[21:31] <rlameiro> without having to read all the code :D
[21:31] <zyga> rlameiro: yes, check what it imports
[21:31] <zyga> no
[21:31] <zyga> :-)
[21:31] <zyga> just see the imports
[21:31] <rlameiro> lol
[21:31] <zyga> and imports of imports that don't look like standard python stuff or gtk stuff that cannot possibly install software
[21:33] <rlameiro> well it imports a lot of dbus stuff
[21:33] <rlameiro> and oslib...
[21:34] <zyga> rlameiro: I think the actuall stuff is somewhere inside jokey's libraries
[21:35] <rlameiro> zyga, well
[21:35] <rlameiro> i will ty to reboot now and see how it goes
[21:35] <rlameiro> cya
[21:39] <rlameiro> zyga, it works now
[21:39] <zyga> rlameiro: I checked oslib, it imports apt module
[21:39] <rlameiro> It seams that the problem might be related with the indexing of the apt list or something...
[21:40] <rlameiro> this is straight from install
[21:40] <rlameiro> it shouldn't happen
[21:40] <rlameiro> fort the firstcommers this can be very scary :D
[21:45] <zyga> rlameiro: you should file a bug about that though
[21:45] <zyga> rlameiro: include the output from jockey
[21:45] <zyga> if anything the error handling code should be more user friendly
[21:46] <rlameiro> zyga, what is the handling code?
[21:46] <zyga> well the details are not important unless you want to fix this and dig deeper
[21:46] <zyga> but the part that broke was this:
[21:46] <zyga> the UI was bad
[21:46] <zyga> something was not working
[21:47] <zyga> but the UI didn't tell you anything about which part is broken
[21:47] <rlameiro> yeap
[21:47] <zyga> didn't include any logs or any other reference for tracking this for power users
[21:47] <rlameiro> but the text version had the same problem also
[21:47] <zyga> did you run apt-get update or similar before rebooting?
[21:47] <zyga> rlameiro: yes, both versions didn't handle that error condition very well
[21:47] <rlameiro> no
[21:47] <rlameiro> ok
[21:47] <zyga> rlameiro: so it was fixed by magic, that's not good
[21:47] <zyga> I was hoping you can still reproduce it
[21:48] <rlameiro> ok i will file that bug
[21:48] <rlameiro> so i will file that on jockey bugs
[21:48] <rlameiro> is there some tool to give info of my sistem, so devs can now?
[21:49] <rlameiro> zyga, for reproducing it i will need to do a fresh install again :D
[21:49] <zyga> since jockey itself didn't crash nothing can help us directly
[21:49] <zyga> I think it's best to include the actual output
[21:49] <rlameiro> ok
[21:49] <rlameiro> maybe i go and ask about it on ubuntu-bugs
[21:49] <zyga> (and the commands you launched)
[21:49] <zyga> as well as the fact that reboot fixed the problem
[21:50] <rlameiro> ok
[22:20] <rlameiro> zyga
[22:20] <rlameiro> !bug #550503
[22:20] <rlameiro> you can go ther if you want
[22:20] <rlameiro> i did mentioned you
[22:20] <rlameiro> :d
[22:42]  * psusi is deeper into the innards of the ext4 fs than any human ever should be...
[22:46] <dottedmag> psusi: So Theodore Ts'o is not a human? Is he a superhuman officially now? :)
[22:46] <psusi> hehehe.... if I could have him over my shoulder working on this ancient code of his I would ;)
[22:47] <psusi> this stuff was written when dinosaurs ruled the earth...
[22:47] <psusi> and now I'm going over the new headers trying to figure out what has changed and update it to use the new features... like extents
[22:50] <psusi> didn't ted used to hang out in here?  not seen him lately
[23:31] <arand> Daviey: If not already aware (sorry if), plymouth-theme has now switched over to be provided by lubuntu-plymouth-theme instead of mythbuntu-default-settings, also Bug #550237 exists.
[23:34] <Daviey> arand: I don't think it's a bug with mythbuntu tbh
[23:34] <superm1> arand, i think the recommends of plymouth need to be fixed to recommend "plymouth-theme-ubuntu-text | plymouth-themes" instead.
[23:34] <Daviey> lubuntu-plymouth-theme is alphabetically before myth*, which is why you are now seeing lubuntu*
[23:35] <superm1> Yup
[23:36] <arand> Yea, it's in the recommends  pulled in by plymouth that the issue lies, I assume
[23:36] <slangasek> hmm, fixoring plymouth then
[23:36] <arand> Wouldn't recommending plymouth-theme-ubuntu-logo have a place as well?
[23:37] <slangasek> arand: metapackages will already pull in -ubuntu-logo by default, and it's an open question whether we want that on server; we only need to recommend one default, so -text should be it
[23:38] <arand> Ah, ok
[23:40]  * slangasek uploads the fix
[23:40] <arand> So I can set a confirmed for the plymouth task then at least, to get some communication out to the bug-lookers?
[23:40] <slangasek> if you do it fast :)
[23:40] <psusi> hrm.... odd.... /etc/mke2fs.conf says in the defaults section to use 256 byte inodes, but does not set the extra_isize flag... I don't think you're supposed to do that... if it isn't 128 bytes that flag should be set....
[23:41] <slangasek> arand: please also advise them to manually remove lubuntu-plymouth-theme / mythbuntu-default-settings
[23:41] <arand> slangasek: Done, so the updated package won't solve things automatically for people who alreadty installed it?
[23:42] <slangasek> arand: nope, an update won't cause these theme packages to be kicked out
[23:45] <Daviey> the joy of running beta :)
[23:46] <superm1> slangasek, as it stands today, plymouth-theme-ubuntu-logo appears to be a dependency of ubuntu-standard.  should that perhaps be moved to the desktop and netbook seeds respectively so that server doesn't pull in the logo'd themes too?
[23:46] <Daviey> superm1: I think the logo'd theme is "as designed" :(
[23:47] <slangasek> superm1: as I said, it's "an open question" :)
[23:47] <Daviey> i'm meaning to see how that works with serial console.
[23:47] <arand> slangasek: Are those reasonable instructions: http://pastebin.ubuntu.com/404764/ ?
[23:47]  * Daviey will sulk and throw his toys if serial console is busted. :)
[23:49] <slangasek> arand: sure
[23:49] <slangasek> superm1: bug #548954


[00:13] <Q-FUNK> http://lists.x.org/mailman/listinfo/xorg-driver-geode
[00:14] <Q-FUNK> new list just to group -amd resources and have a more open discussion than the AMD mailing lists allow
[00:14] <Q-FUNK> related to this
[00:14] <Q-FUNK> http://www.x.org/wiki/AMDGeodeDriver
[01:09] <bryce> Q-FUNK: nice
[01:09] <bryce> Q-FUNK: is there a way to unsub from the info-linux list then?
[01:10] <bryce> or will we be automatically unsubscribed?
[01:33] <Q-FUNK> check the message source.  you can unsubscribe following X-headers in the message
[01:38] <bryce> actually no you can't - it references http://ldcmail.amd.com as the mailman server, but this doesn't appear to be accessible (maybe it's an internal amd.com machine?)
[02:05] <Q-FUNK> jordan could unsubscribe you
[02:53] <ubotu> New bug: #176029 in x11-xserver-utils (main) "Please sync x11-xserver-utils (7.3+2) from Debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/176029
[05:57] <tjaalton> sweet, a new xserver snapshot.. I'll merge it later today
[06:50] <ubotu> New bug: #176061 in xorg (main) "System do not respond properly after rotate the screen" [Undecided,New] https://launchpad.net/bugs/176061
[10:56] <ubotu> New bug: #176099 in x11-xserver-utils (main) "Please sync x11-xserver-utils 7.3+2  (main) from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/176099
[13:00] <ubotu> New bug: #156065 in xorg (main) "gdm login crashes" [Medium,New] https://launchpad.net/bugs/156065
[13:48] <ubotu> New bug: #156212 in xorg (main) "Changing screensaver crashes X" [Medium,Confirmed] https://launchpad.net/bugs/156212
[17:45] <ubotu> New bug: #159747 in totem (main) "video playback failure with ubuntu 7.10 (dup-of: 146455)" [Undecided,Invalid] https://launchpad.net/bugs/159747
[19:11] <Q-FUNK> could radeonhd be moved to main starting with hardy?
[19:12] <Q-FUNK> for all I know, http://www.verkkokauppa.com/popups/prodinfo.php?id=24558 might be supported by it, but since it doesn't come on the CD, I could not test it at the computer store.
[19:12] <Q-FUNK> in gutsy, it's in universe
[19:14] <bryce> that's probably a good idea
[19:16] <Q-FUNK> btw, that hardware even failed to launch with fbdev and vesa, when purposely configured manually on the gutsy CD
[19:17] <bryce> I can't read that page ;-)
[19:17] <Q-FUNK> aye, but the specs should remain clear :)
[19:17] <bryce> näytönohjain ?
[19:17] <Q-FUNK> X kept on reporting "screen found, but none with usable mode" or something similar
[19:18] <Q-FUNK> näytönohjain = display driver ~ graphic card
[19:18] <Q-FUNK> so yes, that ATI card :)
[19:18] <bryce> you should talk with tormod about what's actually supported; he's had his finger closest to the pulse of ati stuff lately
[19:19] <Q-FUNK> oh, ok
[19:19] <Q-FUNK> good to know
[19:19] <bryce> I'm mostly focusing on intel stuff at present
[19:19] <Q-FUNK> mind you, pretty weird that not even vesa or fbdev work.
[19:19] <Q-FUNK> ok
[19:19] <bryce> yes that does sound strange
[19:19] <bryce> however it's not been unknown for ati to fail vesa
[19:20] <bryce> I thought most of the known issues were squared away, but...
[19:20] <bryce> maybe you've got a HW X curse?
[19:20] <bryce> ;-)
[19:20] <Q-FUNK> :D
[19:54] <tjaalton> oh goody, new monitor & mb & cpu etc arrived
[19:57] <tjaalton> the xserver I uploaded failed to build on most archs
[20:03] <bryce> erf
[20:15] <ubotu> New bug: #176186 in xorg-server (main) "[gutsy] 'Lock screen' +gnome-screensaver + XMMS OpenGL visualizer causes Xorg to crash" [Undecided,New] https://launchpad.net/bugs/176186
[20:19] <tjaalton> ../../../../../hw/xfree86/os-support/linux/lnx_apm.c:43: error: expected specifier-qualifier-list before 'apm_event_t'
[20:19] <tjaalton> etc
[20:20] <tjaalton> only sparc finished :)
[20:20] <bryce> heh
[20:20] <bryce> man, I'm having a heck of a time rebuilding my pbuilder root on hardy
[20:20] <tjaalton> I couldn't create one, that's why I didn't test build it :/
[20:21] <bryce> uff
[20:22] <tjaalton> ok, offline for a while until the machine is up and running again
[20:22] <tjaalton> ->
[20:45] <ubotu> New bug: #176193 in xkeyboard-config (main) "missing key description in xkb "us" keyboard" [Undecided,New] https://launchpad.net/bugs/176193
[21:57] <tjaalton> bugger, my old radeon is capable of 1920x1200 via dvi after all :)