[02:47] <RAOF> Bah.    Let me build mesa!
[04:15] <Sarvatt> RAOF: pfft use schroot
[04:15] <Sarvatt> it builds fine here
[04:16]  * Sarvatt totally blames his own lack of using mk-sbuild but oh well, it works
[07:15] <Sarvatt> soo, instead of blacklisting llvmpipe they will try to fix unity?
[07:16] <RAOF> Yup.
[07:16] <Sarvatt> https://bugs.launchpad.net/ubuntu/+source/nux/+bug/926859 noticed the responses when i was going through invalid 12.04 beta targetted bugs this morning
[07:16] <RAOF> It is apparently pretty much as easy as not abusing GL.
[07:17] <RAOF> ie: Actually calling GLXSwapBuffers, rather than trying to blit bits of the backbuffer on the frontbuffer.
[07:17] <RAOF> Jason apparently has that already done, and it works.
[07:18] <Sarvatt> works for kvm?
[07:18] <tjaalton> stgraber's comment is valid
[07:18] <tjaalton> indeed, it's killing kvm
[07:19] <RAOF> But that can be trivially worked around by selecting an Ubuntu2D session, right?
[07:19] <Sarvatt> kvm is the main consumer i would care about, thats problably higher than mgi/savage/etc consumers
[07:20] <tjaalton> RAOF: yeah, but needs manual intervention :)
[07:20] <RAOF> How slow is it in kvm?
[07:21]  * RAOF should give it a whirlygig.
[07:21] <Sarvatt> if its slow thats ok more worried about not working at all
[07:21] <tjaalton> it's using 50% cpu
[07:21] <tjaalton> not that nice on the host
[07:21] <Sarvatt> oh cool
[07:21] <tjaalton> hmm, should try it out on the t23 my parents have, but the usb image I have is probably too old..
[07:22] <Sarvatt> crap but working?
[07:22] <broder> is kvm enabling all the interesting SSE instructions and so forth within the guest?
[07:22]  * Sarvatt has 1gb free hdd space, cant even screw with kvm atm
[07:22] <broder> tjaalton: what happens if you pass, uh, -cpu host
[07:23] <tjaalton> broder: dunno, stgraber? :)
[07:23] <RAOF> tjaalton: I guess that depends on what the default experience should be; do we want people, by default, to have the full Unity experience in their virtualised environment at the cost of speed, or do we want people to opt-in to the full Unity for better default CPU usage.
[07:24] <Sarvatt> yeah if it works its totally another question, would be good to hear from people who care
[07:24] <Sarvatt> it wasnt working before
[07:24] <RAOF> Blacklisting llvmpipe would result in people being basically unable to test unity3d in kvm.
[07:24] <tjaalton> RAOF: true. and could be that a _fixed_ unity might not consume that much cpu when idling..
[07:26] <broder> bah. my precise iso is about 2 weeks old
[07:26] <Sarvatt> thats ok nithng changed besides desktop crap
[07:26] <Sarvatt> nothing changed in llvmpipe at least
[07:27] <broder> well, i'm having a hard time managing to start a terminal
[07:27] <RAOF> On unity/llvmpipe?
[07:27] <broder> yeah
[07:27] <RAOF> I'm not sure if Jason's fix is in the distro yet.
[07:27] <broder> i can't tell what's glitch and what's bad performance
[07:28] <RAOF> But everything should basically be working, barring damage events not necessarily resulting in the screen being updated :)
[07:28] <RAOF> Which is a pretty big caveat :)
[07:31] <Sarvatt> good point i have no clue either, living off in the driver world but the unity/compix fixes are important to that :)
[07:31] <broder> oh! right
[07:31] <broder> kvm still has the idiocy to make 128M of ram the default
[07:32] <broder> let's try this again, but this time actually give the VM enough RAM to do anything useful
[07:33] <broder> ok. kvm -cpu host -m 2048 -cdrom Downloads/my-old-precise.iso
[07:33] <broder> compiz seems to hover at about 20% CPU when i'm just running top in a gnome-terminal
[07:34] <broder> but it jumps to 50% or so if i show and then hide the dash
[07:34] <broder> actually, more like 80% if i do it a few times
[07:35] <broder> or just drag the gnome-terminal window around a bunch
[07:41] <RAOF> Yeah, don't show the dash.
[07:42] <RAOF> It'll try to render a gaussian blur of your whole screen.
[07:42] <RAOF> That's not fast on anything that's not massively parallel.
[07:42] <broder> does SSE4.2 not count?
[07:43] <broder> or whatever other fancy instructions i have in my nehalem
[07:44] <ricotz> RAOF, hello
[07:44] <broder> anyway, my gut is that if we'd be using llvmpipe, we should probably switch to unity-2d by default, but it'd be nice if it was still possible to run unity-3d under llvmpipe for the masochists
[07:44] <broder> i'm not totally sure how i would go about swinging that if i was going to try
[07:45] <broder> i guess move you could move llvmpipe back to libgl1-mesa-dri-experimental
[07:45] <ricotz> RAOF, are you planning another mesa upload soon? could you drop the hard-deps-generation of wayland before that?
[07:45] <RAOF> broder: You'd change the unity-greeter check to start unity2d by default when llvmpipe was present, but not override a manual unity3d selection ;)
[07:46] <RAOF> ricotz: I'm not planning on another mesa upload immediately; it's beta 1 freeze.  We can certainly do that in the next upload, though.
[07:47] <ricotz> RAOF, ok, while using wayland releases instead of snapshot it seems reasonable to drop this restriction from the package
[07:47] <RAOF> I agree.
[07:48] <tjaalton> yeah I overlooked that part
[07:48] <ricotz> it only creates issues currently
[07:48] <ricotz> tjaalton, hi :)
[07:49] <tjaalton> ricotz: hi, I did notice your ping yesterday, but replied directly to pitti
[07:49] <tjaalton> shouldn't be an issue anymore?
[07:50] <ricotz> tjaalton, alright, if you update wayland it will be again
[07:51] <tjaalton> ricotz: yeah, let's fix mesa first then
[07:51] <ricotz> tjaalton, ok
[07:53] <tjaalton> hmm, not sure what needs changing though
[07:53] <tjaalton> ah it's wayland
[07:53] <tjaalton>         dh_makeshlibs -V '$(PACKAGE) (= $(V))' -- -c4
[07:54] <ricotz> yes
[08:02] <RAOF> Dear autotools: seriously?!
[08:02] <tjaalton> so they say that 0.9 will be the point where no backwards-incompatible changes will be made anymore, but after 0.85 they still might
[08:06] <Sarvatt> tjaalton: oh with mesa 8.14? cool
[08:06] <Sarvatt> basically never, didnt expect any better :)
[08:07] <Sarvatt> intel guys, living in release+1 forever because who needs anything stable
[08:08] <tjaalton> Sarvatt: huh? speaking of wayland here. mesa build-depends on wayland, not the other way around :)
[08:09] <Sarvatt> tjaalton: who does wayland?
[08:09] <tjaalton> so maybe we need that hard dep until wayland 0.9 is released?
[08:09] <Sarvatt> dont mind me just complaining
[08:09] <tjaalton> heh
[08:09] <tjaalton> ok so we won't drop it ever, thanks for confirming ;)
[08:10] <Sarvatt> http://paste.ubuntu.com/855094/ according to ricotz though
[08:12] <Sarvatt> thats what we do in edgers then build wayland against it
[08:12] <Sarvatt> err build mesa against it
[08:13] <tjaalton> so build mesa every time wayland is updated?
[08:13] <Sarvatt> tjaalton: what the hell are you doing here btw?
[08:13] <tjaalton> writing nonsense as always :)
[08:13] <tjaalton> I might ask you the same!
[08:13] <Sarvatt> nah just one time and it doesnt have a hard dependency
[08:14] <tjaalton> so you don't care about api issues?
[08:14] <Sarvatt> if theres an api issue mesa gets updated to fix it
[08:14] <Sarvatt> it wouldnt be an issue in the distro
[08:14] <Sarvatt> with released versions of wayland and mesa
[08:15] <Sarvatt> its an issue with mesa master for at most a week at a time
[08:16] <Sarvatt> especially now that theres released versions, the hard dependecies were for when it was the same version but changing which shouldn't happen anymore
[08:16] <tjaalton> yeah well we have stable mesa now, so if wayland changes incompatibly and we update it without the hard dep
[08:18] <tjaalton> oh well
[08:18] <Sarvatt> and "stable" wayland that wont get touched against in 12.04, we can revisit problems in 12.10 :P
[08:19] <RAOF> When we're switching to wayland, amiright? :)
[08:19] <Sarvatt> lol
[08:19] <Sarvatt> ohyea i forgot
[08:21] <tjaalton> I'll drop it now so we won't forget
[08:22] <Sarvatt> it'll be fine if we dont touch it again this cycle but might come up again later, screwing up 100+ packages when we update mesa sucks
[08:23] <Sarvatt> all because of wayland nothing uses or cares about except mesa
[08:23] <tjaalton> yeah
[08:24] <tjaalton> i was surprised that it's so tiny
[08:24] <tjaalton> where's all the bloat?1!
[08:25] <Sarvatt> debian/patches/500_pointer_barrier_thresholds.diff duh
[08:26] <RAOF> ?
[08:27] <Sarvatt> joking, nowhere near as bad as the old 500 xi2 patch
[08:34] <RAOF> WE HAVE (mostly, ish) WORKING TESTS FOR 500_pointer_barrier_thresholds!  YAY!
[08:38] <Sarvatt> RAOF: cool, they test twinview too where the problems always are?
[08:39] <RAOF> Absolutely!
[08:39] <Sarvatt> really?!
[08:41] <RAOF> No, I'm lying.
[09:10] <tseliot> :)
[09:12] <Sarvatt> i'm just really surprised considering how much of a hack twinview is :)
[09:12] <Sarvatt> (and how much dx seems to use it)
[09:14] <Sarvatt> breaking twinview is like the ultimate no-go, i get guaranteed 10 pings the next morning every time someone does something i have no clue about
[09:14] <Sarvatt> unity-greeter broke with twinview, ok i obviously broke that
[09:15] <Sarvatt> or have any clue what happened
[09:16] <Sarvatt> yeah i'm bitter, oh well :)
[09:17] <jcristau> "switch to nouveau"
[09:17] <jcristau> or does that answer not work? :)
[09:17] <tjaalton> nouveau is seriously lacking on newer hw though :/
[09:18] <tjaalton> dualhead might work though
[09:18] <RAOF> Also, power management is a really nifty thing to have.
[09:23] <Sarvatt> lol power management? how's that nvd0 support coming for year old laptops? 3.5 kernel maybe?
[09:24] <Sarvatt> at least vesa works in 1.11 still, one benefit to not going to 1.12 in precise
[09:24] <tseliot> who needs power management anyway? It's nice to have something warm beside you in the winter ;)
[09:25] <jcristau> tseliot: people on the wrong side of the world
[09:25] <jcristau> (hi, RAOF)
[09:25] <jcristau> :)
[09:25] <tseliot> :D
[09:25] <RAOF> :P
[09:25] <Sarvatt> tseliot: whats the weather like where you are now? 22C here in winter, ugh!
[09:26] <RAOF> Sarvatt: Where are *you* that it's 22C?
[09:26] <tjaalton> +-0C here
[09:26] <Sarvatt> lol
[09:26] <jcristau> we had -10C a couple weeks ago
[09:26] <Sarvatt> RAOF: i'm in winter
[09:27] <tjaalton> been kinda wet the past few days, still lot of show
[09:27] <tjaalton> snow even
[09:27] <tseliot> Sarvatt: wow, that's warm. It's 11-14 °C during the day here
[09:27] <RAOF> It tops out at 22Cish *here*
[09:27] <Sarvatt> this is the first winter where i didn't see snow ever
[09:28] <Sarvatt> only time it snowed was when we were in budapest :)
[09:28] <tseliot> :)
[09:29] <Sarvatt> :)? you skipped out on budapest, bah! :)
[09:29] <Sarvatt> tseliot: are you going to be in orlando?
[09:30] <tseliot> yes, but at least I got hail twice here ;)
[09:30] <tjaalton> oakland?
[09:30] <tseliot> Sarvatt: do you mean Oakland?
[09:30] <Sarvatt> tseliot: wait, are you moving back to OEM/premium? i havent even asked ya yet
[09:30] <tseliot> Sarvatt: no, I'm not going anywhere
[09:30] <Sarvatt> tseliot: yeah totally, i keep calling oakland orlando, whats wrong with me
[09:31] <Sarvatt> really? ya like it in HWE?
[09:31] <tseliot> Sarvatt: wrong coast ;).  I'll do it again, just for you ;)
[09:33] <tjaalton> tseliot: :)
[09:34] <Sarvatt> tseliot: wait you were in dublin? i dont even remember, they had us segreated off to another floor from the desktop guys
[09:35] <Sarvatt> but we shoulda been near you because you were in OEM then
[09:35] <tseliot> Sarvatt: I spent quite some time in the Desktop team's room though
[09:35] <Sarvatt> lucky! you got crap done
[09:36] <tseliot> Sarvatt: yep :)
[09:39] <Sarvatt> i think tjaalton got the most done in hwe during that sprint because he was sitting at the boring table :)
[09:39] <tjaalton> hah
[09:40] <Sarvatt> updated -ati to work on llano
[09:40] <tjaalton> oh I did?
[09:40] <Sarvatt> yup, i remember asking you to do a git snapshot for that reason
[09:40] <Sarvatt> i was uh
[09:40] <Sarvatt> playing with minimodem
[09:40] <RAOF> cnd: Hey, would you be planning to factor out some of the xorg testing fun in utouch-geis and utouch-frame into xorg-gtest?  I'm thinking particularly of the pump event loop thingy, which I want want want right now.
[09:41] <RAOF> Because stupid async!
[09:41] <tjaalton> oh I committed some wayland upstream-ubuntu branch
[09:41] <Sarvatt> sending 2400 baud messages to other pcs in hopes it'd save me from having to press power thousands of times while state got shoved into the rtc
[09:42] <tseliot> :)
[09:42] <tjaalton> yeah I remember you playing with it.. funny stuff :)
[09:42] <Sarvatt> tjaalton: before that i spent 2 months pressing power
[09:43] <Sarvatt> i was really happy that things might be easier :)
[09:43] <tjaalton> hm no the funny part was manjos irc msg speech synthesizer
[09:43] <Sarvatt> lmao
[09:43] <tjaalton> minimodem was just cool
[09:43] <Sarvatt> i still screw with him now with the speech synthizer
[09:44] <Sarvatt> in #hwe say, I don't like vietnamese women.
[09:44] <tjaalton> rude :)
[09:45] <Sarvatt> his wife hears it, yeah :)
[09:45] <Sarvatt> he's rude, it's fun screwing with him
[09:46] <Sarvatt> tseliot: you're realling going to update wl?
[09:46] <Sarvatt> i wish we could just sync it from debian
[09:46] <Sarvatt> is dkms still not used in debian?
[09:46] <tseliot> Sarvatt: if it doesn't break apw's wireless, then yes
[09:47] <Sarvatt> tseliot: balls, it broke his wireless in october when you tried
[09:47] <tseliot> Sarvatt: I'm not sure, I haven't used debian since Etch...
[09:47] <Sarvatt> probably will break it
[09:47] <tseliot> (which I still have somewhere)
[09:47] <tseliot> yes, this is why I asked him to test it
[09:47] <Sarvatt> yea debian wl uses m-a
[09:47] <Sarvatt> screw that
[09:47] <tseliot> :/
[09:48] <Sarvatt> they keep it up to date really often though
[09:48] <apw> heh ... i have two machines now which can use wl, one now is supported by the main kernel
[09:49] <tseliot> so maybe they haven already broken his wireless in Debian ;)
[09:49] <apw> but this other one still needs it
[09:49] <Sarvatt> "supported" or supported?
[09:49] <tseliot> *have
[09:49] <jcristau> Sarvatt: dkms is used in debian
[09:49] <Sarvatt> is it?
[09:49] <Sarvatt> hmmmmmmmmmm
[09:49] <apw> Sarvatt, one i use for travel, is on the kernel driver
[09:49] <apw> and is very good
[09:49] <jcristau> dunno about wl though
[09:49] <jcristau> but in general, yeah
[09:50] <jcristau> i haven't used an oot driver since before dkms existed though :)
[09:50] <Sarvatt> brcmsmac spams my dmesg at least 1MB a day
[09:50] <apw> heh that doesn't supprise me :)
[09:52] <Sarvatt> -rw-r----- 1 syslog adm 9.1M Feb 24 04:50 /var/log/kern.log
[09:52] <Sarvatt> its all
[09:52] <Sarvatt> [29862.537191] ieee80211 phy0: START: tid 1 is not agg'able
[09:52] <Sarvatt> [29867.905498] ieee80211 phy0: brcms_c_dotxstatus: INTERMEDIATE but not AMPDU
[09:52] <Sarvatt> repeat
[09:53] <Sarvatt> means a lot, thanks broadcom
[09:53] <apw> there is indeed a lot of debug level crap emitted at too high a level, thats all the sort of thing that being in staging is meant to beat it out of them
[09:54] <Sarvatt> jcristau: hmm sounds like our brcmwl-kernel-source could be merged to debian to use dkms instead of m-a then
[09:55] <Sarvatt> m-a is the devil
[09:55] <jcristau> oot drivers are the devil ;)
[09:55] <Sarvatt> im fine with it but my wife isn't
[09:55] <jcristau> but, yeah.
[09:55] <Sarvatt> yeah thats true too :)
[09:56] <Sarvatt> automatically building with kernel updates instead of manually rebuilding though..
[09:57] <jcristau> ack
[09:57] <Sarvatt> theres a chunk of nics where it has to happen, brcmsmac doesn't cover some crap like macbooks
[10:00] <RAOF> Dear lord?  Macbooks with poorly supported hardwar?  Now there's a pleasant change of pace.
[10:01]  * apw enjoyed the juxtaposition of "crap" and "macs"
[10:01] <Sarvatt> cmacs!
[10:02] <Sarvatt> 4 people will know what i mean when i call them that next
[10:03] <Sarvatt> (yes i picked an arbitraty number)
[10:03] <Sarvatt> tseliot: brcm-wl from october works fine on my machine, where are you updating to?
[10:05]  * Sarvatt has been manually recompiling against each new kernel
[10:05] <apw> Sarvatt, i note that the phonetic spelling of that should be see-macs
[10:05] <Sarvatt> totally x related
[10:05] <tseliot> Sarvatt: <IP_ADDRESS>
[10:05] <tseliot> oh, where
[10:06] <Sarvatt> tseliot: so i had a problem with your same driver in dkms form that i was compiling manually 5 months ago
[10:07] <tseliot> Sarvatt: what problem?
[10:07] <Sarvatt> it didnt work
[10:07] <tseliot> oh
[10:07] <Sarvatt> i'll try the new one
[10:07] <tseliot> thanks
[10:08] <Sarvatt> they renamed the driver or something
[10:08] <Sarvatt> i thing that was the issue i had at the time
[10:08] <Sarvatt> think
[10:08] <Sarvatt> bah
[10:08] <Sarvatt> 5 am
[10:09] <tseliot> unfortunately I don't have a device to test the driver any more
[10:10] <Sarvatt> really? ok will absoltely test it, grabbing your source from chinstrap
[10:20] <tseliot> thanks
[10:20] <tseliot> my netbook died
[10:23] <Sarvatt> broadcom drivers kill it?
[10:27] <Lekensteyn> hi, any change that https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/931397 will be fixed before the beta?
[10:28] <jcristau> send a patch?
[10:32]  * Lekensteyn is downloading the daily image
[14:25] <Lekensteyn> bryceh: ping?
[14:42] <Lekensteyn> Any change that 1.11.5 is going to land in Precise?
[14:42] <cnd> RAOF, yeah, I plan on xorg-gtest being expanded over time
[14:43] <cnd> the tricky part is that utouch-evemu is under CLA
[14:43] <cnd> and some people don't like that
[14:43] <cnd> but maybe they won't notice :)
[14:43] <cnd> I was at the gtk hackfest, and they said they didn't mind it
[14:58] <stgraber> tjaalton: I updated bug 926859
[14:59] <stgraber> tjaalton: and I'll bring it up at the release meeting, will also be on the next techboard agenda if llvmpipe hasn't been blacklisted in unity-support-test by then...
[15:37] <Lekensteyn> Ubuntu' 1.11.4 != Xorg 1.11.4 right?
[16:41] <technoviking> RAOF: ping
[17:03] <tjaalton> stgraber: ok, good to know (didn't read the bug yet)
[17:04] <tjaalton> Lekensteyn: right, the input stack is from 1.12
[17:07] <Lekensteyn> tjaalton: is that <IP_ADDRESS>3?
[17:09] <Lekensteyn> I saw that the InputOption type has changed between 1.11.4 and <IP_ADDRESS>2
[17:09] <Lekensteyn> so, carelessly copying changes breaks things
[17:10] <Lekensteyn> it's not a key, value, next struct anymore
[17:12] <tjaalton> merged from master, more likely
[17:31] <bdmurray> RAOF: perhaps a hybrid-gfx tag, set by apport, would be useful?  I'm looking at bug 939283.
[18:27] <bryceh> Lekensteyn, yeah looks like you need cnd to look at that bug #931397
[18:28] <cnd> bryceh, yeah
[18:28] <cnd> I'm subscribed or assigned
[18:28] <cnd> I think it's a bug introduced by backporting
[18:28] <Lekensteyn> cnd: are you chase douglas?
[18:29] <cnd> Lekensteyn, yep
[18:29] <cnd> Lekensteyn, you can use "/whois cnd" in the future :)
[18:30] <Lekensteyn> true :)
[18:31] <Lekensteyn> Xorg -configure crashes as well
[18:31] <bryceh> cnd, from comment #2 wondering if it still needs the bits from that duplicateDevice call, which converts the pointer type?
[18:32] <Lekensteyn> when debugging I suggest to build with DEB_BUILD_OPTIONS=noopt or gdb will behave weird when setting some breakpoints
[18:33] <cnd> Lekensteyn, I usually use DEB_BUILD_OPTIONS="noopt nostrip noudev nocheck parallel=<n>"
[18:33] <bryceh> Lekensteyn, thanks for doing the extra gdb legwork btw, not many do, but it helps a lot.
[18:33] <cnd> yeah
[18:33] <cnd> +1 :)
[18:34] <Lekensteyn> your welcome, I've received some queries about it from users who have an nVidia Optimus laptop model
[18:34] <Lekensteyn> that needs to be fixed ;)
[18:35] <bdmurray> bryceh: bug 930004 and bug 930839 are both crashes in xcb during distribution upgrades.
[18:36] <bryceh> bdmurray, looking
[18:36] <bryceh> heh, like the description in the latter
[18:36] <bdmurray> yeah, that's a gem
[18:39] <bryceh> bdmurray, often xcb issues are races in threading behaviors, that can be quite challenging to sort out.  So if there's a set of steps to reproducing it, that'd likely help a good bit.
[18:43] <bdmurray> bryceh: is this helpful?
[18:43] <bdmurray> ERROR:root:NvidiaDetection returned a error: __init__() got an unexpected keyword argument 'datadir'
[18:43] <bdmurray> MarkUpgrade() called on a non-upgrable pkg: 'brasero'
[18:43] <bdmurray> ERROR:root:Upgrading 'brasero' failed
[18:43] <bdmurray> [xcb] Unknown sequence number while processing queue
[18:43] <bdmurray> [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[18:43] <bdmurray> [xcb] Aborting, sorry about that.
[18:43] <bdmurray> python: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
[18:43] <bryceh> bdmurray, yeah sounding like a client error
[18:44] <bdmurray> hrm
[18:44] <bryceh> looking in libx11
[18:45] <bryceh> "Most likely this is a multi-threaded client and XInitThreads has not been called" sounds relevant (and familiar...)
[18:49] <bryceh> bdmurray, wonder if it's a protocol mismatch between client app and server?
[18:50] <bdmurray> oh, like if libxcb updated and update-manager hadn't yet?
[18:51] <bryceh> something like that's what I'm wondering.
[18:52] <bryceh> as you probably already gathered, this fault is happening during the client polling of the X server, and it gets some response it didn't expect
[18:52] <bryceh> if we knew roughly how to trigger this bug, we could probably set up xtrace between the client and server to see  what the communication is between them
[18:54] <bryceh> here's the test that seems to be failing:
[18:54] <bryceh> XLIB_SEQUENCE_COMPARE(req->sequence, >=,
[18:54] <bryceh>                                        dpy->xcb->pending_requests->sequence)
[18:55] <bryceh> actually wait, it's not an unknown request but rather an unknown sequence number
[18:55] <bryceh> not sure what a sequence number is in this context
[18:56] <bryceh> so not that, but this:
[18:56] <bryceh> (XLIB_SEQUENCE_COMPARE(event_sequence, >,
[18:56] <bryceh>                                                   dpy->request)
[18:57] <bryceh> bdmurray, ok reading further... bunch of warning text regarding threading
[18:57] <bryceh> bdmurray, ok yeah so I'll paste the text into the bug report
[19:00] <bryceh> bdmurray, ok I'm finally remembering.  When we first switched to xcb, we had a huge spate of these types of bugs.  libxcb is more sensitive to how it's called in threading conditions, so the client code needs to be careful to make the calls properly
[19:01] <bryceh> bdmurray, so the assert that's being tripped is not a bug in X but rather is catching a bug in the client code
[19:01] <bryceh> at least, I think.
[19:02] <bryceh> I could be talking out of my ass.  That would hardly be new.
[19:06] <bryceh> bdmurray, ah, so bug 930004 looks like the threading issue I mentioned
[19:06] <bryceh> bug 930839 may be the mismatched client/server issue I mentioned previously.
[19:07] <bryceh> again though, kinda just guessing here.  Both appear to be client errors that XCB is catching (i.e. both are assertion fails), rather than actual segfaults in X
[19:16] <bryceh> bdmurray, #901675 is another similar bug in apport
[19:18] <bdmurray> okay, thanks
[19:18] <bryceh> another in g-s-d - 833694
[19:18] <bryceh> hmm
[19:19] <bryceh> bdmurray, ahh https://bugzilla.gnome.org/show_bug.cgi?id=657255#c8
[19:24] <bdmurray> um, where does that leave us?
[19:26] <bryceh> bdmurray, can you raise it with the upstream-manager folks to look into?
[19:26] <bryceh> bdmurray, it's not an X bug
[19:26] <bdmurray> upstream-manager?
[19:27] <bryceh> (I mean, aside from the fact that libxcb is sensitive to threading issues...)
[19:27] <bryceh> update-manager
[19:27] <bdmurray> ah okay
[19:38] <bdmurray> bryceh: but in bug 832513 they say it should be fixed in libglib2.0-0
[19:40] <bryceh> bdmurray, it's not the same bug, just different codebases making similar coding errors and hitting the same assertion
[19:41] <bryceh> bdmurray, it'd be like two C applications getting the same error message from gcc; it doesn't mean they have the same bug, nor that gcc is broken, just that they both happened to have the same kind of programming error.
[19:45] <bdmurray> bryceh: okay, thanks again for the help
[19:52] <bryceh> bdmurray, sure thing, let me know if you need more help


[02:26] <Stemp> Hi all, I have a problem with bug #123916. It affect Hardy and the problem is fixed in Debian.
[02:27] <Stemp> I built it in my PPA, but what should I do now ? requesting a Sync is only for Intrepid, right ?
[02:42] <mrooney> Stemp: right, what you want is one or both of 1) backport the updated package, 2) patch the current package to fix the bug
[02:44] <Stemp> As the actual package is a copy of an old Debian version, I guess it's better to ask for backport. So in fact there is nothing I have to do in launchpad bug ?
[02:46] <RAOF> Stemp: Verify that it's fixed in intrepid is nice.
[02:47] <Stemp> it is, the new version is in Intrepid
[02:49] <RAOF> Stemp: Right.  So, it'll only be fixed in Hardy with a SRU - Stable Release Update.  If you want that to happen, you need to ask nicely.
[02:49] <RAOF> And, by ask nicely, I mean: follow...
[02:49] <RAOF> !sru
[02:50] <Stemp> thanx RAOF
[03:02] <Stemp> Ok I did my 1-a-day :p Good night
[08:00] <dholbach> good morning
[08:02] <techno_freak> morning dholbach
[08:02] <dholbach> hi techno_freak
[11:33] <ma10> shouldn't incomplete bugs turn automatically invalid after a while? how long does it take?
[11:56] <persia> ma10: There's some debate about whether they should do so or not, but 60 days is the configured value.
[11:58] <ma10> persia: https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=date_last_updated&search=Search&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patc
[11:59] <ma10> there are bugs untouched since years!
[11:59] <ma10> This bug report was marked for expiration 243 days ago.
[11:59] <persia> ma10: RIght.  The automatic expiry appears to be off, yet the expiry clock is on.
[12:02] <ma10> persia: mhh.. would it be ok to set incomplete with the "old untouched" standard response all new (and maybe confirmed) bugs untouched for one year or so?
[12:03] <persia> ma10: I don't think the bugs become incomplete with age.  On the other hand, most of them could do with some triage.
[12:03] <Ampelbein> ma10: thats what i do with those.
[12:03] <persia> I suspect a lot of them are fixed.
[12:03] <ma10> i'm trying to think of some ways to reduce the clutter
[12:03] <persia> Ampelbein: How is that helpful to ensure the distribution is bug free?
[12:03] <persia> ma10: Triage the bugs?
[12:04] <ma10> yes.. 100% the submitter doesn't care anymore
[12:04] <Ampelbein> persia: if the issue is no longer there
[12:04] <persia> Ampelbein: If the issue is no longer there, the correct status is Fix Released, not Invalid.
[12:05] <Ampelbein> persia: not saying anything against it.
[12:05] <persia> ma10: Even if the submitter doesn't care, is it not worth checking to see if the bug is present, and either closing it, or ensuring it is complete?
[12:05] <Ampelbein> persia: thats what the "old untouched" response is for. if the submitter says its corrected with an update: Fix Released.
[12:06] <persia> Ampelbein: Ah.  In that case, I'm misunderstanding the terminology.  Please forgive the rant.
[12:06] <Ampelbein> persia: no problem. but according to https://wiki.ubuntu.com/Bugs/Responses#Bugs%20resolved%20after%20update%20or%20config%20change, the status should be set to invalid.
[12:06] <persia> Also, for many bugs with some information on how to reproduce, it's often easier to try to reproduce oneself than to ask the submitter.
[12:07] <persia> That URL crashes my browser, but from the title, I disagree.  If it was fixed by a config change, and we don't ship that by default, someone else will encounter the bug.
[12:07] <persia> If it was fixed by an update, it should be Fix Released.
[12:08] <Ampelbein> persia: i think the wiki has a point there. it could be anything that corrected the issue, including a hardware change, config change or the update.
[12:08] <Ampelbein> https://wiki.ubuntu.com/Bugs/Responses
[12:08] <persia> Indeed, but is it not worth trying to figure out what happened, and reporting it correctly?
[12:08] <Ampelbein> persia: depends on the severity.
[12:08] <persia> We mark a lot of bugs Invalid.  This has generated a fair amount of press that we don't care about bugs.
[12:09] <persia> I think we care about bugs, and it's worth spending a couple minutes to say "Yep, we fixed it, finally" so that the submitter feels like they should submit more bugs, and we can fix those as well.
[12:09] <Ampelbein> if its a minor bug that can't be reproduced in any of the new releases i don't see the point in trying to figure out why it happened in the first place.
[12:09] <ma10> the problem is that there are 21073 new unassigned bugs
[12:10] <ma10> do we have the manpower to do things "properly"?
[12:10] <persia> ma10: No.  The problem is that Ubuntu has bugs.  That is the thing that should be fixed.  Reducing the number of bugs doesn't mean anything at all.
[12:10] <persia> TO take an example, Microsoft's public bug tracker for Word doesn't have any bugs shown.  Does that mean there are no bugs in Word?
[12:11] <Ampelbein> you are right. but if we reduce the number of open bugs by checking which ones are still in the packages we could concentrate on the important things.
[12:12] <persia> Yes, but I'd also like to get more good bugs reported.  If someone has an issue, I'd like them to have a good experience reporting a bug.  I think it's worth a couple minutes to check the changelog for the affected package and verify it was fixed.
[12:12] <Ampelbein> and i think a response saying that the submitters bug has been fixed with a new release is better than no response at all.
[12:12] <persia> Generally there will be some mention of the fix.
[12:12] <persia> Precisely, and that encourages the submitter to upgrade, and report more bugs, and generally improves the quality of Ubuntu.
[12:13] <persia> I just think the appropriate bug status for "Fixed in a new release" is "Fix Released" and not "Invalid"
[12:14] <Ampelbein> so the first thing to do is check IF its still an issue. either by reproducing or by asking the submitter (status: incomplete). if its not an issue anymore we try to look in changelog. if mentioned there: status: fixreleased. if not mentioned: status invalid.
[12:14] <ma10> persia: i think the wiki says invalid for bugs whose cause was never understood
[12:14] <persia> Cool.  I was worried it was something else.  Thanks for the confirmation.  I'll try to turn off the rant button :)
[12:15] <Ampelbein> persia: sometimes its good to be ranted at. can bring oneself to think about it ;-)
[12:15] <persia> ma10: Yes, it does.  My main concern is the case of NEW Unconfirmed bugs of significant age, that we ought at least try to understand the cause.
[12:16] <persia> Ampelbein: That's a delightfully refreshing attitude :)
[12:18] <ma10> persia: ok policy received
[12:22] <ma10> but i still think it would be useful to have an automatic procedure that does something like: for old bugs, ask if it's still a problem, make incomplete, if someone replies turn back to new. And have a working auto expiry
[12:23] <persia> At the last UDS there was talk about having things go from incomplete to NEW when someone replied, but it needs more work, so we have to wait for the LP devs to do something.
[12:23] <ma10> yes i saw that on the mail from the lp team to motu where they asked to prioritize features
[12:24] <persia> My memory (which may be flawed) is that auto-expiry was turned off because the bugsquad only processes ~2500 bugs a week, and there's some backlog (it used to be a lot smaller), so using auto-expiry would expire some people's bugs just because someone was too busy to get back when the person answered.
[12:24] <ma10> but there was nothing about "auto respond to old bugs"
[12:25] <persia> You might propose it.  I believe the best way to do this is to file a bug against launchpad, but I may be mistaken.
[12:25] <ma10> (2500 bugs a week) that's not bad!
[12:26] <hggdh> ma10, indeed not bad -- but only if you have enough people to work on them!
[12:27] <ma10> ok, i'll think about filing a bug.. maybe someone already has
[12:28] <persia> ma10: Yep.  2500 bugs is actually a number to be celebrated, but it's hard to compete with the flow we get after some good press story, or a new release.
[12:29] <ma10> yeah i guess we could see it that way: more bugs more users more success :)
[12:29] <hggdh> ma10, auto-respond to old bugs does not really help any: if the bug was not been looked at before, it will probably not be looked at after an auto-query
[12:30] <ma10> hggdh: what i want to happen is that if the user does not respond the bug auto-expires
[12:30] <hggdh> and what if the user *does* respond, but nobody looks at it?
[12:31] <persia> That's why the expiry feature is less interesting until we can automatically turn off the clock when someone responds.
[12:31] <hggdh> I would personally find this very rude -- "are you still interested" -- "yes, I am" -- silence
[12:32] <ma10> turns automatically new and the cycles begins again.. the poor user is pinged over and over :) should not be too much of an annoymnet if it's once every 2 months
[12:32] <ma10> turns automatically new and the cycles begins again.. the poor user is pinged over and over :) should not be too much of an annoymnet if it's once every 2 months..
[12:32] <ma10> turns automatically new and the cycles begins again.. the poor user is pinged over and over :) should not be too much of an annoymnet if it's once every 2 months..
[12:32] <persia> Except it's a reminder every two months that one's bug is being ignored.
[12:32] <ma10> sorrry!!!! :(
[12:32] <persia> No, you've demonstrated the problem precisely :)
[12:32] <hggdh> it is not the frequency, but what persia jut said (darn, persia *again* preempted me ;-)
[12:32] <ma10> sorry for the multi-send
[12:33]  * persia leaves the next several responses to hggdh :)
[12:33]  * hggdh is too slow to compete
[12:37] <ma10> don't know i'm thinking.. i guess you're right anyway
[12:38] <ma10> i started this discussion because i'm beginning to mantain packages and the first thing i had to do was clean up a lot of old bugs before i could understand what i *really* had to fix
[12:47] <Ampelbein> ma10: another thing about automated expiry is that people would then think: why should i care about filing bugs, when i get an automated reply after X months to verify that i still have the issue.
[12:48] <Ampelbein> if the reply actually comes from a human being thats not so bad.
[12:48] <Ampelbein> because then the submitter sees that someone is taking care of the report.
[12:49] <Ampelbein> of course the next action after verification that the bug still exists should not be to set status new and leave it be ;-)
[12:49] <ma10> Ampelbein: that's true.. if you do it you subscribe and when he replies you have to care
[12:50] <ma10> lol :) this way you act no better than a bot
[12:54] <ma10> ok so what i learned is "care about the user, live with the clutter" :)
[12:54] <ma10> thanks
[12:55] <ma10> for the explanations!
[12:58] <persia> ma10: Thanks for cleaning up the clutter in the packages you examined to figure out what work needed to be done.
[13:04] <hggdh> ma10, still -- thank you for your proposal (even if not accepted): you are helping, and we we are all thankful for that.
[13:05] <hggdh> (and do not fell alone -- I have had some of my own ideas shot down, sometimes very fast ;-)
[13:06]  * Hobbsee loads her bubblegun, and points it in hggdh's general direction
[13:34]  * hggdh wonders if there is *any* kind of effective protection
[13:35] <hggdh> Hobbsee, ping
[13:36] <Hobbsee> hggdh: pong
[13:36] <hggdh> should I run for my life?
[13:36] <hggdh> :-)
[13:38] <bokey> wheres grendal?
[13:38] <bokey> :P
[13:54] <Hobbsee> heh
[13:54] <Hobbsee> not unless you fear a bubble attack...
[15:26] <Hew> Is there an easy way to know which dbgsym packages to install? Apport-retrace does a great job, but is there a single command or something that just targets a package and pulls the required packages?
[15:34] <afflux> Hew, no, apport-retrace looks at the ProcMaps field in the crash report, looks for the loaded libraries, searches for the packages they belong to, and pulls the dbgsym packages for them.
[15:35] <Hew> afflux: Ah ok, I assumed it just pulled all the dbgsym packages for the dependencies. Thanks for the info.
[15:38] <afflux> Hew: no problem. You still can find out which dbgsym packages you need by using some shell magic
[15:38] <afflux> Hew: like: cat /proc/9604/maps  | awk '{ print $6 }' | sort | grep -v '^$' | grep -v '^\[' | while read p; do dpkg -S $p; done | cut -d':' -f1 | sort -u
[15:38] <afflux> Hew: where cat /proc/9604/maps could be changed to point to the file containing the ProcMaps
[15:42] <Hew> afflux: I'm trying to triage bug 252174, which requires a valgrind log. Someone has (finally) produced one, but it's missing symbols. Is there something easy to tell the user? What info am I looking for in the valgrind.log?
[15:44] <afflux> Hew: are you running hardy?
[15:44] <afflux> oh wait, the report is for intrepid
[15:44] <afflux> never mind
[15:48] <Hew> afflux: Yes, this is an Intrepid bug. I was wondering how it's possible to look at a valgrind.log and work out which dbgsym packages it needs. Do I just look for all the "within /lib/libpthread-2.8.90.so" parts, and find which packages contain these files?
[15:49] <afflux> Hew: to make sure it will be complete, you look at the ProcMaps.txt file at the beginning of the report, and make sure that all libraries mentioned there have debug symbols.
[15:50] <Hew> afflux: ah of course, I should be able to work it out from there. Thanks again!
[15:50] <afflux> Hew: I'll have a list ready in a minute
[15:51] <Hew> afflux: wow thanks, even better than working it out myself! :P
[15:53] <afflux> Hew: you'll definetly need libc6-dbgsym libglib2.0-0-dbgsym and gvfs-dbgsym, maybe gvfs-backends-dbgsym and libgvfscommon0-dbgsym, unlikely are the ones for: libdbus-1-3, libgnome-keyring0, libpcre3 and libselinux1
[15:55] <Hew> afflux: Excellent, I'll post a comment and let the guy know!
[15:55] <afflux> thanks!
[17:17] <mcas> hello
[17:18] <Hew> mcas: hi
[17:18] <mcas> if there are bugs "please upgrade to newer version" or "please sync from debian"
[17:19] <mcas> are these bugs "wishlist"? i think they are but i want to ask bevor doing something wrong
[17:19] <Hew> mcas: Yes, they are wishlist.
[17:20] <mcas> ok :-)
[17:20] <mcas> thank you Hew
[17:21] <Hew> mcas: no worries, thank you for helping out :-)
[17:27] <persia> mcas: Hew: Please don't set the status of those bugs to "Wishlist".
[17:27] <persia> While it is often accurate, it's not always accurate (as sometimes we get a critical bugfix through a merge or a sync)
[17:27] <persia> Also, those are mostly filed by developers, and some of the developers complain about extra bugmail just for setting them wishlist.
[17:28] <persia> My understanding is that as the Launchpad API improves, the tool the developers use to file those bugs will automatically set them to the right Importance, but it doesn't do that yet.
[17:30] <Hew> persia: Sure thing. I know that wishlist isn't a blanket policy, but I was thinking the case here was probably a user asking for a new feature like most sync bugs. I suppose I should have asked for more detail.
[17:30] <Hew> mcas: Which bug are you working on?
[17:31] <Hew> mcas: or was it just a general question?
[17:31] <persia> Hew: Yeah, it gets confusing when users who aren't developers file what should be upgrade bugs and use the sync format.
[17:34] <xnevermore> Hey guys. I filed a bug (#255976) and provided a package for a new upstream version for sponsoring about three weeks ago, and have heard very little since. Is there any more I should do to get it noticed?
[17:34] <persia> bug #255976
[17:34] <Ampelbein> Hi! What about a bug like #74807, where the poster found a solution himself? What is the correct status to set the bug to? Personally I would say "Confirmed", have the documentation edited to represent the problem and then "Fix Released". What is the right way here?
[17:35] <Ampelbein> bug #74807
[17:35] <mcas> i need some help with bug 260244
[17:35] <persia> xnevermore: You've done everything you need.  The sponsor queue is a bit clogged right now.
[17:36] <mcas> i can confirm the problem with konqueror3 and don't have the problem with konqueror4
[17:36] <mcas> what should i do with this bug.
[17:36] <mcas> should i mark it as triaged?
[17:37] <persia> Ampelbein: I'd call that Triaged, as the solution is known for that hardware.  Mind you, it may not be trivial to integrate into the packaging because it may be that different hardware needs different settings, but that really needs a developer to investigate.
[17:37] <mcas> with a comment with my information?
[17:37] <xnevermore> persia: awesome. I just found it a bit strange. If I file a regular bug, I usually hear back from folks fairly soon, but when I release fixes, they seem to go unnoticed.
[17:37] <xnevermore> bug #257110 is another example
[17:38] <Ampelbein> persia: ok, then i would need someone of bug-control have set this. thanks for the info.
[17:38] <persia> xnevermore: Yeah, in the past we were better about pushing fixes, and less good about reviewing bugs.  We've tried to fix the reviewing bugs bit, but we're falling behind on the including fixes bit :(
[17:39] <xnevermore> lol
[17:39] <xnevermore> i see
[17:40] <asomething> xnevermore: I think a big part of that is that there are a lot of people triaging that aren't devs, so if you post a bug that needs more info people will ask you about it but when you have something that needs to be acted on it can take a little while longer for a response
[17:40] <persia> mcas: That's a tricky one.  You might ask in #kubuntu-testers if someone can reproduce with an earlier version, or maybe if they have any guidance on whether such bugs should be considered fixed.
[17:41] <xnevermore> persia: yeah, that makes sense.
[17:41] <mcas> persia: i tried it with a konqueror from kde4.0 not 4.1
[17:41] <persia> asomething: That's precisely it.  We seem to get about the same percentage of new people each cycle, but depending on which area is behind, that area gets more recruiting, so we're never quite perfectly balanced.
[17:42] <persia> mcas: Still, unless someone answers here, your choices are really to ask there, or find another bug for now.
[17:42] <mcas> ok
[17:42] <xnevermore> asomething: maybe the focus should be to motivate triagers and packagers to move up the later to become MOTU, etc.
[17:43] <persia> xnevermore: Last time we did that we ran out of triagers :)  It's all a matter of balance :)
[17:45] <xnevermore> persia: good point =P
[19:09] <jcastro> bdmurray: you do needs-packaging bugs as confirmed,wishlist right?
[19:12] <bdmurray> jcastro: correct, provided it isn't already packaged and minimal information about the software is provided
[19:12] <jcastro> https://bugs.edge.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=needs-packaging&field.tags_combinator=ANY&fiel
[19:12] <jcastro> might be a good 5-a-day target to clean these out then
[19:13] <greg-g> ugly link!
[19:13] <jcastro> sorry!
[19:13] <greg-g> heya
[19:13] <bdmurray> that's probably scriptable
[19:13] <jcastro> welcome back greg!
[19:13] <greg-g> jcastro: not quite, closer though, I'm in Minneapolis
[19:13] <jcastro> ah
[19:13] <jcastro> we need a bug jam. kubuntu-de is pulling away!
[19:14] <greg-g> getting there, next weekend, this weekend is the gf's sister's wedding
[19:14] <greg-g> jcastro: oh noes!
[19:14] <greg-g> we'll do one once some students are back in town, see if I can poster some geek hangouts
[19:18] <asomething> jcastro: if you do a hug day or something for those, one good thing to ask people to do is check if there is also a Debian ITP bug filed and link it, so as to not duplicate work
[19:19] <jcastro> asomething: good idea
[19:19] <greg-g> +1
[19:19] <bdmurray> asomething: I've written a script that looks for those
[19:19] <jcastro> hey ... you know how we link bugs to debian, etc ...
[19:19] <jcastro> I wonder if it would be useful if lp let you link to ITPs
[19:20] <bdmurray> jcastro: you can as though are filed in the debian bts about the wnpp pseudo-package
[19:20] <bdmurray> s/though/those/
[19:20] <jcastro> ahh
[19:20] <jcastro> now can you script /that/?
[19:20] <bdmurray> jcastro: yes, I wrote something that does that last weekend
[19:21] <jcastro> man, everytime I think of something you've already got a script
[19:21] <bdmurray> I'm still actively working on it but I've affected 76 needs-packaging bug reports so far
[19:22] <jcastro> hot
[19:23] <bdmurray> Yeah, I was / am really excited about it
[19:28] <greg-g> pretty soon bdmurray will write a script to come up with new script ideas
[19:28] <bdmurray> lol
[19:37] <greg-g> karma for code commits means that each time I commit to my 5-a-day branch I'm getting karma? :)
[19:37] <jcastro> extra motivation
[19:37] <jjesse> greg-g: don't know how that is working cause i've been commit to branches and haven't seen my karma go up yet
[19:37] <greg-g> jjesse: hmm
[19:37] <jjesse> doesn't even show in the karma summary section
[19:38] <jjesse> i see bugs, but no commits
[19:38] <greg-g> hmmm
[21:21] <bdmurray> james_w: still around?


[03:33] <scot3004> hi
[11:12] <chorgox> Good Morning everyone... I just upgrade to the new 12.10 after some problems the system settle, lol however I have a problem with the webcam is a logitech and is not working, anyone can point me to the right direction?
[11:12] <chorgox> thanks
[11:13] <chorgox> well is not that is not working , using chesse i can see video (somentimes) but youtube would stop working O.O
[11:21] <KnitGal> installed 12.10, not getting dock items or having access to system settings, etc, when in Unity.  but have access when I'm in Gnome.  how to fix this?
[11:21] <chorgox> ^--- I had that yesterday too, and automagically today is working
[11:22] <chorgox> was kind of like my Monitor was not detected or somenthing i guess
[11:23] <chorgox> but in you case maybe is the graphic card
[11:33] <duanedesign> chorgox: Cheese works but video in the browser does not?
[11:34] <duanedesign> have you installed 'ubuntu-restricted-extras'?
[11:35] <chorgox> is really weird if i have the CAM connected youtube would not work ,
[11:35] <chorgox> i only tried the cam in chesse , i think i did installed the extras (iill check again
[11:36] <duanedesign> cheese is the best app to check yourwebcam
[11:36] <duanedesign> IMHO :)
[11:38] <chorgox> yeah, i agree with you, cheese is my first stepo, after try with skype and so on, i guess is somenthingh with conflict between flash and the camera driver or similar, i can confirm that ubuntu-restricted-extras are already installed
[11:38] <duanedesign> hmm, interestring
[11:39] <chorgox> now i got youtube working and i plug my cam and chese does nothingh
[11:42] <chorgox> kind of it see the thingh in there but is not working (lsusb Bus 001 Device 010: ID 046d:08c2 Logitech, Inc. QuickCam PTZ)
[11:43] <chorgox> plug and and plug 3 times and now chesse sees my cam and show video .. really weird
[11:45] <duanedesign> that is strange.
[11:45] <chorgox> and youtube works. lol so is all really random
[11:47] <chorgox> i think i tried different configurations like start the pc with the cam umplaged start you tube after plug the cam and see what happens, and stuff and i can find a way to make everything work as i want
[11:48] <chorgox> is like "the cam would choose when and how" lol
[11:51] <duanedesign> chorgox: might check 'dmesg' to see if it has any clues
[11:54] <chorgox> ok never used that but i will try to learn about it, cheers,  Im trying to get skyp working and there is not MIC working ... I start to think that is more a audio conflict than anything else..
[11:59] <chorgox> woow lot of information i will restart to try to make sens of it brb cheers
[13:03] <KnitGal> how do i enablle web apps in 12.10?
[14:28] <holstein> KnitGal: you mean, how do you use a webapp?
[14:33] <KnitGal> yep
[14:35] <KnitGal> i'm not sure if it is working in 12.10 that i have installed and i can't figure out how to trigger it through Firfox or chromium.  i tried going to youtube.com but i didn't get anything like the screenshot i saw
[14:35] <holstein> KnitGal: i would just open it int he browser
[14:35] <holstein> KnitGal: what are you trying to accomplish? something like prism?
[14:36] <KnitGal> like, here:  http://www.omgubuntu.co.uk/2012/10/ubuntu-12-10-released
[14:36] <KnitGal> the YouTube screenshot
[14:36] <KnitGal> "Unity Web Apps"
[14:37] <holstein> KnitGal: im having issues on a public connection right now... give me a bit to look at that
[14:50] <holstein> KnitGal: you are using unity?
[14:50] <holstein> you dont have that icon?
[14:54] <duanedesign> KnitGal: have you added the preview ppa 'ppa:webapps/preview'
[14:57] <duanedesign> sudo add-apt-repository ppa:webapps/preview
[14:57] <duanedesign> sudo apt-get update && sudo apt-get install unity-webapps-preview
[14:57] <duanedesign> after running those commands, Log out and back in and web apps should be enabled
[14:58] <KnitGal> ah, thanks
[17:18] <Radaan> Anyone running ubuntu on a touchsmart tx2 here?
[17:19] <Radaan> or at least have experience with it?
[17:25] <wilee-nilee> Radaan, It might help to know that the channel works as your problem addressed in the form of a question. ;)
[17:32] <plague> Hi! Anyone could please provide link to turorial how to set up Apache2 virtual hosts under Ubuntu? Thanks in advance.
[17:36] <plague> :(
[17:46] <wilee-nilee> plague, Y0u might see if the #ubuntu-server can help. ;)


[00:29] <LaserJock> jcastro: ping
[00:58] <slangasek> LaserJock: yes, thanks
[01:06] <LaserJock> slangasek: done, thanks
[03:52] <lamont> do-release-upgrade -d  --mode=server
[03:52] <lamont> Checking for a new ubuntu release
[03:52] <lamont> No new release found
[03:53] <lamont> why does it hate me so?
[03:54] <wgrant> lamont: Which release?
[03:56] <lamont> ia64 with intrepid installed, pointed at a "reasonably current" mirror of the world
[03:56] <wgrant> Ah. ia64.
[03:56] <lamont> yeah.  ports
[03:57] <wgrant> It should still be using the same meta-release-development, though, I would think.
[03:58] <lamont> well, given that they're all forced by the local proxy to the same place, and that has the same file for all of them, yeah
[03:58] <lamont> so it claims jaunty
[03:58] <lamont> supported: 0 though
[03:58] <wgrant> That's fine.
[03:59] <lamont> http://paste.ubuntu.com/156288/
[04:00] <lamont> wtf.  how did I get an intrepid version of that file
[04:01] <lamont> wgrant: a well placed rm meta-release-development fixed it.
[04:02] <wgrant> lamont: Hmm.  I download the updater .tar.gz and look at DistUpgradeMain.py...
[04:15] <geofft> help=_("*DEPRECATED* this option will be ignore")
[04:26] <geofft> Is there a better way to see what extra stuff do-release-upgrade does beyond dist-upgrade, or should I continue to UTSL?
[05:50] <magcius> Guys! I got multiple message support working in notify-osd!
[06:16] <lifeless> StevenK: hoist a brew for me at the release party
[06:16] <StevenK> lifeless: You can't make it?
[06:16] <lifeless> StevenK: I'm booked already tonight and slug is friday
[06:16] <StevenK> Release party is Saturday
[06:16] <lifeless> oh
[06:16] <lifeless> thats right :)
[06:16] <lifeless> we'll see, I have some things happening saturday, but will try
[06:19] <chris062689> Is this the correct channel to go to if you need help package DEBs?
[06:21] <lifeless> no
[06:21] <chris062689> Which channel should I go to?
[06:21] <lifeless> #ubuntu-motu is a good place to learn about packaging
[07:22] <dholbach> good morning
[07:50] <tjaalton> how come the -security uploads are not shown on *-changes?
[08:12] <soren> tjaalton: For security reasons, of course.
[08:12] <soren> Hahah!
[08:13]  * soren crawls back under his rock
[08:16] <pitti> Good morning
[08:17]  * slangasek waves
[08:18] <mdke> happy release day :)
[08:18] <slangasek> indeed!
[08:21] <tjaalton> slangasek: would you like me to edit the relnotes wiki directly, or add the wacom entry as a comment to the bug?
[08:22] <slangasek> tjaalton: either is fine; the latter ensures we don't have to worry about getting in the way of each other's edits
[08:22] <tjaalton> slangasek: ok, I'll do that then
[08:39] <directhex> merry releasemas!
[08:43] <tjaalton> asac: firefox creating huge (4GB) sparse files on NFS sound familiar to you?-)
[09:06] <asac> tjaalton: not really ;)
[09:06] <asac> tjaalton: a sqlite db?
[09:07] <tjaalton> asac: formhistory.sqlite.. I was equally surprised
[09:07] <tjaalton> no idea how to reproduce, but some users have had that
[09:08] <liw> are sparse files problematic on nfs?
[09:08] <tjaalton> I'm not sure
[09:09] <tjaalton> might be an nfs boog
[09:10] <geofft> is this new with Jaunty or some new Firefox version?
[09:12] <tjaalton> geofft: no, with hardy
[09:13] <tjaalton> at least I believe it was
[09:17] <sabdfl> happy release day, all
[09:18] <ogra> sabdfl, to you too :)
[09:19] <ion_> Congrats
[09:23] <pitti> hey sabdfl, and to you!
[09:24] <directhex> it's a sabdfl!
[09:25] <sabdfl> life and kicking
[09:25] <sabdfl> err... liVe and kicking
[09:27] <davmor2> Congratulations Everybody and here's to the next release
[09:27] <tseliot> happy release :-)
[09:34]  * pitti goes to pre-review the ton of SRU
[09:35] <slangasek> pitti: yay :)
[09:39] <mdz> calc: that 56% is down from 63% for March
[09:39] <slangasek> wow, is that a percentage of new bugs or of all bugs?
[09:40] <ogra> we have bugs ?
[09:40] <directhex> debian-with-bugs!
[09:41] <directhex> pitti, i want an SRU for something. should i arrange for an 0ubuntu2 to be uploaded directly, or wait for karmic, sync -3 into karmic, and request that be used for the sru?
[09:42] <pitti> directhex: I'd advise to upload 0ubuntu1.1 as an SRU now
[09:42] <pitti> unless you really meant -3, and not ubuntu3
[09:42] <directhex> i meant -3
[09:42] <pitti> then 0ubuntu2 is okay
[09:43] <directhex> so "do it now" then
[09:43] <directhex> debdiff time!
[09:43] <pitti> yes, please prepare the bug for SRU, and upload to the queue
[09:44] <directhex> 1.0.1-0ubuntu1.1 is the correct versioning for an sru?
[09:44] <pitti> directhex: it's a valid one; it's not the only correct one
[09:44] <pitti> the main point is to avoid version clashes with karmic uploads
[09:46] <directhex> i'll requestsync it for karmic as soon as it opens
[09:49]  * tonyyarusso would like to briefly remind sabdfl, slangasek, and anyone else who may care that we are using #ubuntu-release-party again for Jaunty.  Remember to have fun today!
[09:51] <directhex> i still think thursday releases suffer from an inherent party-related flaw
[09:52] <cjwatson> Friday releases suffer from an inherent don't-release-and-then-disappear-for-the-weekend bug :-)
[09:52] <cjwatson> (oh, and they also tend to result in missing news cycles)
[09:54] <heno> and give less wiggle-room
[09:55] <directhex> releases full stop suffer from an inherent don't-release-then-get-drunk bug
[09:55] <directhex> solution: debian ;)
[09:55] <LaserJock> directhex: I don't know, if it took me that long to get a release out I'd want to get drunk for a long while
[09:56] <directhex> LaserJock, could always ban security teams from attending parties...
[09:58] <directhex> okay, i have a debdiff. now to do the SRU paperwork
[10:14] <directhex> hm. for an SRU i can't upload myself, do i hunt for a regular motu to upload it first, or go straight for a motu-sru person to take care of the lot?
[10:19] <pitti> directhex: oh, I thought you were motu
[10:19] <pitti> directhex: subscribe motu-sru for approval
[10:19] <pitti> directhex: AFAIR, motu-sru wants to ack universe SRUs before upload anyway
[10:21] <directhex> pitti, i'm just a lowly contributor. not even formally a member of any kind yet (though i now have a handy wiki page for people to leave me glowing testimonials)
[10:21] <directhex> pitti, i've subscribed motu-sru, and i'll poke cody-sommerville when he wakes (spoke with him yesterday about this bug)
[11:19] <Keybuk> gnargh!
[11:19] <Keybuk> setlocale() is not malloc()-safe
[11:20] <liw> hm?
[11:26] <wretched_dutchma> hello,
[11:26] <wretched_dutchma> can anyone tell me were I can suggest new programs for future ubuntu releases??
[11:27] <directhex> wretched_dutchma, https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[11:27] <wretched_dutchma> thank you :)
[11:52] <slangasek> superm1: how much lead-time do you need for http://mythbuntu.org/9.04/release to go live?
[11:55] <slangasek> TheMuso, luisbg: same question, regarding getting 9.04 on http://ubuntustudio.org/downloads
[12:05] <Ampelbein> pitti: hi, i noticed you assigned me to bug 351017 . does that mean that there is more work to be done on the package?
[12:06] <pitti> Ampelbein: no, I just want every release targetted bug to have an assignee
[12:06] <pitti> i. e. the one in charge for the bug
[12:06] <Ampelbein> ah, ok.
[12:12] <TheMuso> slangasek: sorry again since the website is not my area, I can't help.
[12:12]  * TheMuso is thinking though that he should change that for karmic.
[12:13] <TheMuso> i.e get web access since nobody ever appears to be around when these things need doing.
[12:13] <slangasek> TheMuso: fwiw, _MMA_ tells me he's more-or-less stepping down due to work committments, so I guess that would be a good idea :)
[12:13] <TheMuso> slangasek: Yeah I'm well aware of that.
[12:13] <TheMuso> Thing is I tend to do a fair chunk of stuff as it is, that the others don't want me to take any more on, however they sometimes don't pull their own weight.
[13:04] <madduck> at what time can we expect the release today?
[13:04] <jpds> madduck: When it's announced on ubuntu-announce.
[13:05] <madduck> oh how familiar that answer is :)
[13:06] <madduck> the reason i am asking is because i need to talk to one of your developers asap and would like to make sure I get the timing right
[13:08] <james_w> madduck: you need to talk to someone as soon as it's released, but not a moment before?
[13:09] <madduck> right
[13:09] <madduck> and i just wanted to get a bit of an idea when that would be
[13:10] <madduck> anyway, i'll just wait
[13:11]  * ogra points madduck to #ubuntu-release-party ...
[13:12] <ogra> will be announced there first
[13:12] <busfahrer> Where?
[13:12] <madduck> "Every time you ask if it's out yet, a unicorn loses it's horn." -- few, glad i asked the right question then. :)
[13:12] <ogra> lol
[13:12] <ogra> busfahrer,  #ubuntu-release-party
[13:12] <busfahrer> Thanks, already in there, hehe.
[13:13] <madduck> good luck all
[13:32] <lifeless> mvo:
[13:32] <lifeless> https://bugs.launchpad.net/bugs/288797 seems unfixed
[13:33] <mvo> lifeless: upgrade or fresh install?
[13:33] <slangasek> TheMuso, luisbg: now would be a good time to make http://mythbuntu.org/9.04/release available
[13:34] <slangasek> TheMuso, luisbg: er, I mean http://ubuntustudio.org/downloads of course
[13:36] <lifeless> mvo: read the comments
[13:36] <lifeless> mvo: ask for more info etc:)
[13:36] <mvo> lifeless: sorry, I thought you were hit by the bug too
[13:37] <slangasek> superm1: the sooner http://mythbuntu.org/9.04/release can be made available, the better
[13:39] <lifeless> mvo: I am subscribed forvarious reasons :)
[13:39] <slangasek> NCommander: do you have access to get http://xubuntu.org/news/9.04-release updated?  looks like I just missed mr_pouit, and Cody's not around AFAICS
[13:39] <lifeless> mvo: so I am seeing a stream of people still sayng they are hitting it
[13:40] <mvo> lifeless: they are hitting a different bug it seems (the fact that adding a new repository does not immediately update the index)
[13:40] <mvo> but I will respond in the bug
[13:40] <Ampelbein> pitti: i get a failed to built for powerpc for mjpegtools (351017), http://paste.ubuntu.com/156499/ . How can I get access to the config.log?
[13:47] <pitti> Ampelbein: you can't; you need to reproduce/debug it on a local machine
[13:48] <pitti> Ampelbein: perhaps because -mno-sse2 is applied on all architectures instead of just i386, and the switch doesn't exist on other arches?
[13:49] <pitti> Ampelbein: yeah, I think that's it
[13:49] <pitti> wrap it into something like
[13:49] <Ampelbein> pitti: that's what i suspect. but i don't have a powerpc-architecture here to test it. and since its the only change, yeah thats it. i broke another package
[13:49] <pitti> ifneq ($(findstring $(DEB_BUILD_ARCH), i386 lpia),)
[13:49] <pitti>  CFLAGS+=-fno-sse2
[13:49] <pitti> endif
[13:50] <pitti> (or whatever the flag/variable was)
[13:51] <c_korn> in how many hours will jaunty be released?
[13:51] <Ampelbein> pitti: will do that. is there a way to "simulate" another architecture with pbuilder? or perhaps with virtualbox?
[13:51] <ogra> c_korn, -> #ubuntu-release-party
[13:51] <pitti> Ampelbein: no, but you can change "i386" to "foobar" and verify that the flag isn't applied then
[13:52] <c_korn> ogra: thanks. I should have known that there is a channel for everything
[13:52] <Ampelbein> pitti: ah, yeah. cool. thanks for the help. (and sorry for breaking the package in the first try)
[13:52] <ogra> heh
[13:52] <pitti> Ampelbein: no prob
[13:54] <miki4242> pitti: hi, i'm the guy who mailed you about using v4l-dvb with dkms, sorry for long silence :-)
[13:54] <pitti> hi miki4242
[13:54] <miki4242> had too much work going on to reply earlier
[13:58] <miki4242> pitti: there were some problems regarding espeak: portaudio19 doesn't play nicely with pulseaudio. do you know what is going to happen to the release?
[13:58] <pitti> miki4242: you might want to talk to TheMuso about that
[13:59] <persia> Ampelbein, In extreme situations, it's possible to cat config.log during the build, but try other things first.
[13:59] <persia> (as in when it fails on a buildd, but isn't failing locally, etc.)
[13:59] <miki4242> pitti: ok thanks
[14:00] <kirkland> seb128: howdy
[14:00] <seb128> hi kirkland
[14:01] <kirkland> seb128: i just enabled jaunty-proposed, to help do some testing of those packages
[14:01] <kirkland> seb128: on dist-upgrade, i see:
[14:01] <kirkland> http://pastebin.ubuntu.com/156509/
[14:01] <kirkland> seb128: removing evolution, and such
[14:01] <kirkland> seb128: the last time i saw this, it took me about a day to resume my normal access to email :-)
[14:01] <seb128> kirkland: could you try to figure why?
[14:01] <kirkland> seb128: try to figure out why it wants to be removed?
[14:02] <seb128> oh
[14:02] <seb128> I know
[14:02] <kirkland> seb128: or why i lost a day fighting evolution?
[14:02] <seb128> kirkland: non !i386?
[14:02] <directhex> man, jaunty's been out for AGES! why's karmic taking so long to open? boo!!!!!! :<
[14:02] <seb128> kirkland: non i386 I mean
[14:02] <seb128> ?
[14:02] <kirkland> Linux t61p 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux
[14:02] <kirkland> seb128: ^
[14:02] <seb128> right
[14:02] <seb128> wait for the amd64 build to catch up for evolution-data-server
[14:02] <Ampelbein> persia: ok. i think pitti found the error and provided a fix, am now testing here and will reupload.
[14:02] <seb128> it built on i386 so -common is available but not the amd64 binaries
[14:02] <kirkland> seb128: aaaahhhh
[14:03] <seb128> yet another reason why I use an i386 install ;-)
[14:03] <kirkland> seb128: wow, that's a nasty little race in our build system
[14:03]  * pitti hugs slangasek, awesome work! congrats
[14:03] <kirkland> seb128: so last time, i must have dist-upgraded later in the day and it found a published build
[14:03] <persia> kirkland, It's worse when something FTBFS for only some architectures, because then it's more than a race condition.
[14:03] <kirkland> seb128: and then i was working again
[14:03] <seb128> kirkland: where it's really an issue is if the amd64 fails or take some days now
[14:04] <kirkland> persia: seb128: ack.  that sucks.
[14:04] <slangasek> pitti: you too :)
[14:04] <slangasek> congrats, all!
[14:04] <seb128> binaries are copied to -updates though
[14:04] <directhex> yay!
[14:04] <pitti> LOOK BEHIND! A THREE-ANTLERED JACKALOPE!
[14:04] <seb128> so we don't have the issue in updates
[14:04] <directhex> is my cake in the mail, then?
[14:04] <seb128> slangasek: congrats!
[14:04]  * kirkland hugs slangasek
[14:04] <persia> kirkland, The alternative is one copy of arch:all binaries for each arch, which is too painful to contemplate.
[14:04] <Keybuk> IS KARMIC OPEN YET?
[14:05] <seb128> well the bug there is also too strict depends between arch all and any binaries
[14:05] <persia> Keybuk, You win.
[14:05] <kirkland> Keybuk: oh, yeah, i'm installing it now :-)
[14:05] <seb128> and apt being stupid, you can tell that to mvo ;-)
[14:05] <ogra> Keybuk, on its way :)
[14:05] <directhex> pitti, i want to help you for giving me a moment to visualize monkey island's Lemonhead as a debian developer... "and the package says 'maintained by lemonhead'... just like one of mine!"
[14:05] <dholbach> asac: HAPPY BIRTHDAY! :-)
[14:05] <directhex> Keybuk, beat you to it
[14:05] <seb128> TOO MANY INFORMATIONS
[14:05] <directhex> Keybuk, [14:02] <directhex> man, jaunty's been out for AGES! why's karmic taking so long to open? boo!!!!!! :<
[14:05] <seb128> asac: happy birthday ;-)
[14:05] <persia> directhex, Except you didn't use ALL CAPS, so it doesn't count as a well-formed pony request.
[14:06] <pitti> asac: oh? happy (age++)!
[14:06] <directhex> persia, poot.
[14:06] <directhex> boo! asac gets jaunty for his birthday. i got a car accident!
[14:06] <ogra> asac, DUDE ! happy b-day !
[14:06] <mvo> seb128: its not sutpid, just a bit ... slow thinking
[14:06] <mvo> (ok, it is)
[14:06] <pitti> directhex: plusungood
[14:06] <seb128> mvo: ;-)
[14:06] <superm1> slangasek, should be live now
[14:06] <slangasek> superm1: great, thanks
[14:07] <seb128> mvo: I know, people should use "upgrade" and not "dist-upgrade" too
[14:07] <mvo> asac: HAPPY BDAY
[14:07] <ion_> (age++) = λx→age++x
[14:07] <directhex> ion_, nerd!
[14:07] <kirkland> seb128: i wonder if update-manager is any smarter about this than apt-get ...
[14:09] <seb128> kirkland: update-manager never remove an installed package so yes
[14:09] <seb128> kirkland: it would just wait for the amd64 build to be available
[14:09] <seb128> kirkland: and put the -common upgrade on hold
[14:12] <kirkland> seb128: cool, that's good to knoew
[14:12]  * cjwatson starts pushing karmic seeds
[14:12] <kirkland> seb128: i suppose that's why i saw the issue
[14:12] <seb128> right
[14:13] <kirkland> seb128: cheers, thanks for the help ;-)
[14:14] <cjwatson> NCommander,mr_pouit: please branch lp:~xubuntu-dev/ubuntu-seeds/xubuntu.jaunty to lp:~xubuntu-dev/ubuntu-seeds/xubuntu.karmic
[14:14] <seb128> kirkland: you're welcome, let me know if that's autofixed in one hour when the amd64 build is there
[14:16] <cjwatson> superm1: please branch lp:~mythbuntu/ubuntu-seeds/mythbuntu.jaunty to lp:~mythbuntu/ubuntu-seeds/mythbuntu.karmic
[14:16] <superm1> cjwatson, i thought i already did, will do if not
[14:17] <wgrant> I find it a little odd that the feature tour recommends that I use Microsoft Office formats.
[14:17] <cjwatson> I didn't look :)
[14:17] <cjwatson> superm1: oh, so you did. queue-jumper :)
[14:21] <directhex> wgrant, ?
[14:22] <wgrant> directhex: http://www.ubuntu.com/products/whatisubuntu/904features/web-browsing/, bottom right.
[14:22] <slangasek> mr_pouit: are you in a position to publish http://xubuntu.org/news/9.04-release, which still 404s?
[14:23] <cjwatson> james_w: please add karmic to the package importer
[14:23] <asac> thanks all ;)
[14:25] <directhex> wgrant, i think it means it in a "interop with windows weenies" kind of way
[14:25] <directhex> also, vista-- #randomly rebooted me mid-game as it decided to apply some updates i didn't ask it to
[14:26] <[reed]> so, I was surprised to see update-manager telling me fglrx isn't supported on 9.04 -- anybody know the bug # tracking that or when that may be resolved so I can actually upgrade?
[14:26] <directhex> [reed], ati dropped support for any cards older than $VERYNEW
[14:26] <mvo> [reed]: fglrx does not support r5xx cards anymore, just r6xx,r7xx
[14:27] <directhex> [reed], there's no fix. ever. unless ATI start doing what nvidia do, and have multiple fglrx releases at once which all support modern kernels & xservers
[14:27] <mvo> [reed]: there is a decent chance that the free driver works well for you, but it seems that its lacking in some areas (games), compiz should be fine
[14:27] <mvo> [reed]: best try that out with the livecd
[14:27] <slangasek> cody-somerville: hi, I can has http://xubuntu.org/news/9.04-release ?
[14:27] <cody-somerville> Yup. Bringing that online now
[14:27] <slangasek> thanks!
[14:27] <[reed]> so, I have an "ATI Mobility FireGL V5200" card
[14:27] <[reed]> I don't know what that maps to
[14:28] <[reed]> as far as rxxx goes
[14:28] <pitti> heh, www.ubuntu.com is basically dead
[14:29] <directhex> [reed], RV530
[14:29] <[reed]> guh
[14:29] <[reed]> that sucks
[14:30] <ogra> pitti, not for me
[14:30] <directhex> [reed], use the Free driver, or contact ATI, or stay using intrepid or older forever, or buy a new laptop. those are the options
[14:30] <mvo> [reed]: little we can do unfortuantely (other than to warn about it)
[14:30] <directhex> [reed], sorry, but that's what happens with proprietary stuff
[14:31] <[reed]> well, the only reason I use it is because I have an external monitor, and fglrx seems to be the only thing that can do dual monitors correctly
[14:31] <mr_pouit> NCommander: cody-somerville: can you create the branch? (I'm not on my machine right now)
[14:31] <cody-somerville> mr_pouit, branch for what?
[14:32] <persia> cody-somerville, karmic seeds.
[14:32] <ogra> likely karmic
[14:32] <cody-somerville> Sure
[14:32] <ogra> ah persia beats me
[14:32] <Ampelbein> pitti: attached modified debdiff to bug 351017, i tested locally with something arbitrary and the flag did not get applied. thanks.
[14:32]  * persia was using a very light stick
[14:32] <pitti> Ampelbein: can you upload yourself, or do you need a sponsor?
[14:33] <Ampelbein> pitti: i need a sponsor.
[14:35] <pitti> Ampelbein: uploaded, thanks! will process with the next batch
[14:58] <doko> lamont: would you like to have GCC-4.4 as the default for hppa and ia64?
[15:15] <calc> mdz: oh that is good news then :)
[15:29] <pitti> meh, launchpad.net is slow, or is that just me?
[15:29] <pitti> well, I guess it's the DC connection being maxed out
[15:30] <gnomefreak> pitti: its launchpad
[15:55] <ebroder> What's the best way to request a large-ish number of CDs for a student group I'm involved in to hand out to users? The last time we tried to order a batch of Intrepid CDs through shipit, we got 3
[15:57] <ScottK> ebroder: There's a "special request" link on the shipit page that gives you a chance to explain why you need more.  That's worked for me.
[15:57] <ebroder> Ok, I'll try that...as soon as shipit comes back up
[16:55] <cumulus007> Hi, a tour to introduce Ubuntu during installation was promised for Hardy, then it was delayed for Intrepid, and finally it would come in Jaunty
[16:56] <cumulus007> however, it's not there in jaunty
[16:56] <cumulus007> why is this?
[16:56] <persia> cumulus007, Maybe nobody wrote it yet?
[16:56] <ion_> You didn’t implement it yet. :-P
[17:00] <superm1> cumulus007, you mean the ubiquity slideshow spec?
[17:00] <cumulus007> yep
[17:01] <superm1> cumulus007, it's been discussed at the last two UDSes, and it will be discussed again at this one I believe
[17:01] <superm1> evand might know more on why it was delayed
[17:01] <cumulus007> Okay, I hope this will be implemented
[17:06] <evand> cumulus007: it's scheduled for Karmic.  We need to coordinate work between four teams, and that turns out to be quite difficult.
[17:06] <cumulus007> okay, that's a pity
[17:31] <azeem_> W2
[17:32] <azeem_> bah, sorry
[18:06] <Kano> hi, why is jaunty not default on packages.u?
[18:17] <weather15> Hello
[18:21] <soren> Kano: Probably an oversight. However, I suspect that at this very second, Intrepid is still what most people uses, so it's not that bad :)
[18:25] <ScottK> Kano: Because there isn't one magic "we released, so let's update every web tool everywhere that Ubuntu uses" button.
[18:26] <Kano> you could write it
[18:27] <soren> No, we couldn't.
[18:28] <persia> Kano, not trivially, because people write new web tools for Ubuntu every day.
[18:28] <Kano> packages is old
[18:28] <soren> Kano: And not run by Canonical.
[18:28] <soren> Kano: I'm not even sure the guy running it is an Ubuntu user.
[18:28] <Kano> haha
[18:29] <ScottK> Packages.ubuntu.com and packages.debian.org are the same codebase.
[18:29] <geser> soren: packages.u.c is hosted on sulfur.canonical.com now
[18:30] <soren> geser: still on Frank's behalf, though, isn't it?
[18:30] <soren> I mean.. We provide the hardware, but I thought he ran it.
[18:30] <soren> ICBW.
[18:30] <ScottK> AFAIK that's true.
[18:30] <geser> that I don't know
[18:31] <calc> is there a particular reason LP is falling over
[18:31] <calc> it seems about 50% failure rate for me currently
[18:31] <ScottK> calc: It's in the same data center as the primary mirrors.  It's release day.
[18:31]  * calc thought it was separate from the package distribution system
[18:31] <calc> ScottK: so overloaded it can't even get to its backend i suppose?
[18:32] <ScottK> Not sure where the bottleneck is, but clearly there is one.
[18:32] <calc> the page itself works but operations on it pop up the oops page
[18:32] <ScottK> This happens every release.
[18:32]  * calc thinks the LP server needs a dedicated connection to its database server
[18:33] <pitti> Keybuk: who's the MoM person nowadays? it needs to be flipped to Karmic, and all "updated merges" reset to "outstanding"
[18:33] <cjwatson> pitti: Keybuk said earlier he'd already poked MoM
[18:33] <pitti> ah, nice
[18:34] <cjwatson> he says he suspects archive.ubuntu.com hadn't quite pulsed out karmic yet
[18:34] <cjwatson> so it'll get round to it
[18:34] <cjwatson> calc: having trouble due to the load on shipit; they're aware, but it will probably also naturally subside
[18:38] <calc> cjwatson: ok
[18:48] <trunkz> Not entirely sure as to whether this is the correct channel, but I was reading up on the mailing lists, and it sems libspe2 should be in the repo's.. but it isnt.
[18:48] <trunkz> Its an important ps3 component of ubuntu.
[18:49] <ScottK> trunkz: For discussing getting new packages in, #ubuntu-motu is a better channel.
[18:50] <calc> trunkz: its not there for ps3? or just not there for other arches?
[18:50] <trunkz> calc, doesnt seem to be for powerpc or x86 (just ran it on my intel box)
[18:51] <trunkz> ScottK, will have a try there :)
[18:51] <calc> trunkz: https://launchpad.net/ubuntu/+source/libspe2/2.2.80-95-3.1ubuntu1
[18:51] <calc> trunkz: it shows like it is there
[18:51] <trunkz> I know.
[18:51] <pi_m> Hi, how can I disable the new notifications?
[18:51] <trunkz> But its not in the repo's
[18:51] <trunkz> I've compiled the source from launchpad
[18:51] <trunkz> but it seems apt-get & dpkg dont believe that its installed.. which is another problem :p
[18:52] <trunkz> Trying to do it via checkinstall now, hopefully the .deb will register itself.
[18:52] <calc> trunkz: this isn't it? http://ports.ubuntu.com/pool/main/libs/libspe2/libspe2-2_2.2.80-95-3.1ubuntu1_powerpc.deb
[18:53] <trunkz> that might be libspe2-2.. which it wont be
[18:53] <trunkz> i'll double check.
[18:53] <calc> trunkz: its built from the same libspe2 source
[18:53] <calc> trunkz: it looks like the sover changed
[18:54] <calc> trunkz: between 2.2.0 and 2.2.80 it changed name from libspe2 to libspe2-2
[18:54] <trunkz> .. ahh
[18:54] <calc> trunkz: at least from what i can see
[18:54] <trunkz> do they still have the 2.2.0 debs on there?
[18:55] <calc> trunkz: yea... look :)
[18:55] <calc> not in jaunty as it is old, but its in intrepid
[18:55] <trunkz> ya just saw itin intrepid
[18:55] <trunkz> thats going to fix a heck of alot of problems if it works.
[18:56] <calc> trunkz: what problems are you seeing? is it just a problem with your own code linking against the wrong library name?
[18:57] <trunkz> spe-medialib wont recognise libspe2 :)
[18:57] <calc> trunkz: spe-medialib is probably an old version then or not up to date with the spe2 libary
[18:57] <trunkz> All this.. just to get video working properly :)
[18:58] <calc> trunkz: so i take it spe-medialib isn't something that is in ubuntu?
[18:58] <trunkz> nope.
[18:58] <trunkz> It should be. but it isnt :)
[18:59] <calc> trunkz: so just modify its source to link the correct lib and/or just recompile it and it should work
[18:59] <trunkz> oh hello.. seems to play nice now.
[18:59] <calc> you might not have to modify anything depending on how it finds the spe library when building
[18:59] <calc> heh
[19:00] <pi_m> Or can you tell me where I can find this information (how can I disable the new notifications)?
[19:00] <trunkz> I'll probably submit a request for static builds of spe-medialib to be included in the repo :)
[19:04] <ScottK> trunkz: It'll get turned down.
[19:04] <trunkz> I'll bribe them with cookies.
[19:44] <pacejr> anyone have any speculation about the radeon driver stack in 9.10?
[19:47] <persia> pacejr, At this point, it's mostly an upstream thing: I doubt the decision would be taken as to what or how or any such until at least post UDS.
[19:48] <Kano> i hope the first new package for karmic will be vbox 2.2.x
[19:49] <pacejr> persia: yeah, i figured. 2.6.31 will likely be just too late for 9.10 anyways, right?
[19:50] <persia> I don't know.  Depends on when it releases, and what the kernel team decides at UDS.
[19:50] <pacejr> i seem to remember they've only switched to a kernel in the middle of ubuntu's release cycle once in the past few years
[19:50] <persia> No, the kernel switches in the cycle at least once *every* cycle.  It only switched late in the cycle once.
[19:51] <persia> The kernel team selects a version to target early in the cycle, and generally keeps to that choice.
[19:56] <LordKow> the version selection really does have a lot to do with each specific kernel release.
[19:56] <calc> as 2.6.30 isn't even released yet it is unlikely 2.6.31 will be in karmic
[19:56] <calc> 2.6.31 at the current kernel release rate would be out sometime after July (maybe August?)
[19:57] <LordKow> i would guess 2.6.30 in june. so.. late august.
[19:58] <pacejr> and i suppose the kernel team would be hesitant to patch the new radeon bits into 2.6.30?
[20:00] <calc> feature freeze is also late august so it will be interesting to see what they decide to go with :)
[20:09] <pacejr> at least fedora is guinea-pigging a lot of the new radeon stuff for us
[20:10] <Kano> but it was too late to fix intel onboard it seems for 9.04
[20:11] <Marfi> Passing word from #ubuntu...torrent link is being buggy
[20:12] <Marfi> back to work. Wonderful release!
[20:14] <jdong> Kano: I don't see a solution for that mess until probably closer to Karmic's release timeframe.
[20:14] <jdong> looks to me like upstream is the one in a state of flux.
[20:15] <Kano> updated intel drm maybe
[20:15] <magcius> I've got this annoying bug in my fork of notify-osd where the message box flashes for a minute before fading in. Anybody want to help?
[20:27] <ScottK> jdong: siretart was reporting significantly better performance with the current release.
[20:44] <NCommander> *sigh*
[20:44] <NCommander> That's fun
[20:47] <jdong> ScottK: performance isn't my issue; stability is my biggest concern currently
[20:48] <jdong> ScottK: EXA doesn't work anymore since Jaunty, UXA hardlocks every few hours and dies on resume
[20:48] <ScottK> jdong: I see.  For UXA, I agree.
[20:48] <LaserJock> jdong: talking about -intel
[20:48] <LaserJock> ?
[20:48] <ScottK> EXA works here, just is slow.
[20:48] <ScottK> LaserJock: Yea
[20:49] <LaserJock> yeah, I'm really buggered by it still
[20:49] <ScottK> EXA + Greedy works reasonably well here.
[20:49] <LaserJock> I have to turn off compositing or my GPU freezes within a few minutes
[20:49] <NCommander> pitti, is there any chance we can setup a SPARC retracer? (I'm currently actively debugging issues on SPARC< and it would be handy)
[20:49] <jdong> EXA for me deadlocks in some GEM call when Compiz tries to start.
[20:49] <jdong> it's a bug that I can produce in every modern-ish distro past Intrepid
[20:52] <ScottK> jdong: Which Intel do you have?
[20:52] <ScottK> jdong: Any chance you could give backports approval some love.  I'm sure it needs it.
[20:52] <jdong> ScottK: GMA950 in a old generation Macbook
[20:52] <ScottK> Ah.
[20:53] <jdong> and Backports is on my TODO list which is getting shoved to the weekend.... courses are really killing me right now
[20:56] <persia> NCommander, You can run apport-retrace locally.
[20:56] <NCommander> persia, link to documentation?
[20:57]  * NCommander suspects he needs the debug libraries installed :-/
[20:57] <persia> man apport-retrace
[20:58] <YokoZar> hmm the release notes page still refers to Ubuntu 9.04 beta (http://www.ubuntu.com/getubuntu/releasenotes/904overview)
[20:59] <persia> YokoZar, IF it's not already filed, file a bug against ubuntu-website.
[21:00] <cody-somerville> where did gtk-displayconfig go?
[21:03] <YokoZar> persia: done.  didn't realize we had a website project in launchpad, makes sense
[21:05] <magcius> Sorry... Ubuntu packaging n00b here... how do you use CDBS with automake?
[21:07] <persia> magcius, Better to ask in #ubutu-motu (and there's a couple files you can include, but how many to include depends on what you want to do).
[21:07] <ScottK> magcius: Packaging questions are better in #ubuntu-motu
[21:28] <siretart> jdong: ScottK's right. I'm currently running jaunty with 2.6.30-rc2 and intel 2.7.0 release (karmic ships 2.6.3) and EXA acceleration.
[21:30] <ScottK> kees: The last upload to the release pocket was your sepolgen upload.
[21:55] <NCommander> jdong, ping?
[22:39] <kees> ScottK: \o/  :)
[22:45] <joaopinto> my system hanged on a "Checkign initramfs for custom DSDT" after a crash, the only bug I found for the same message is bug 58386, but is rather old
[22:45] <joaopinto> any ideas ?
[22:46] <ScottK> joaopinto: File a new bug.
[22:46] <joaopinto> hum, shut it down for some more minutes and booted fine now
[22:46] <joaopinto> not sure i'll be able to reproduce
[22:46] <joaopinto> I have left my laptop for 10 minutes, and then found it shutdown, with the caps lock blinking
[22:48] <joaopinto> grr, now the wifi is also working
[22:49] <magcius> Would it make sense for Ubuntu to do the Select Best Server thing before a dist-upgrade?
[22:49] <magcius> I think that's a reasonable request.
[22:56] <alex-weej> anyone offer an explanation as to why "outline" is the default mode in compiz?
[22:56] <alex-weej> resizing used to be slow
[22:56] <alex-weej> but it isn't anymore
[22:56] <alex-weej> i can cook up a config patch debdiff if it's worth it
[23:12] <mrooney> pitti: around by any chance?


[03:35] <lotuspsychje> good morning
[03:48] <pavlushka> morning lotuspsychje
[03:48] <lotuspsychje> hey pavlushka
[03:51] <pavlushka> so lotuspsychje where can I make the request to avail networkmanager indicator as single/individual indicator to be added to the panel, in my case it is mate-panel?
[03:51] <lotuspsychje> network indicators are probably in a default group of the flavour
[03:52] <lotuspsychje> dont think they will allow them to be seperate
[03:54] <pavlushka> lotuspsychje: that would save some space on my 12.5 inch's display panel
[03:55] <oerheks> one could use conky ..
[03:55] <lotuspsychje> erm
[03:55] <lotuspsychje> save space from 1 lil indicator?
[03:56] <pavlushka> oerheks: yes but I can not also manage the network from there with a mouse click
[09:35] <rogerrogerroger> Hi all, got a strange problem after upgrading to Ubuntu 20.04 on my desktop, I can no longer mount an NFS share on my server... no config files have changed (double checked they weren't changed by the upgrade), desktop reports that the mount attempt times out, the server logs show that it successfully authenticates multiple times but no other messages in the logs... other desktop on Ubuntu 19.10 can still mount it no problem, any id
[09:35] <rogerrogerroger> eas?
[10:03] <myphs> hello everyone. so i installed 20.04 and wow! this thing feels pretty snappy. of course there were minor issues.
[10:03] <myphs> (1.) my password wasn't accepted the right way, because the keyboard layout changed mid-installation without any notice. so i reinstalled and chose a simple password.
[10:03] <myphs> (2.) using full disk encryption and copying 50GB of guild wars 2: the system/UI stopped several times for 1-2 seconds. nothing really was going on but kcryptd jumped up to ~6% per proc. so that might cause it?
[10:10] <myphs> and of course the moving icons when the dock is on the bottom doesn't work correctly, but that was already reported and there's a workaround :)
[10:56] <rogerrogerroger> aha, tried mounting with -v, it had stale file handles... running exportfs -f on the server sorted it
[17:24] <roody> hello, im running gimp2.10.18 on ubuntu 20.04. it looks like when i launch gimp, all the python plugins are failing to import gimpfu
[17:25] <roody> doesnt anyone know if pygimp was shipped or built with the new gimp version
[17:27] <lotuspsychje> roody: tell us how to reproduce this, maybe can see if its a bug
[17:28] <roody> sure, i just ran gimp --verbose.  im on 20.04.
[17:28] <roody> i think i pulled gimp from muon
[17:28] <roody> a few weeks back
[17:28] <roody> its definately not the snap
[17:28] <roody> package
[17:29] <roody> so that could be it
[17:29] <lotuspsychje> ok so what happens next?
[17:29] <lotuspsychje> !pm
[17:30] <lotuspsychje> you can tell it here roody
[17:30] <roody> OH ok
[17:31] <lotuspsychje> im running gimp in verbose now, what should i try now
[17:31] <roody> the error is on launch, i just did gimp --verbose. i was trying to figure out why i couldnt see the pyhon console
[17:31] <lotuspsychje> roody: you are on kubuntu i presume?
[17:31] <roody> yes
[17:32] <roody> im running the kde window manager
[17:33] <lotuspsychje> roody: what should i test now in gimp to reproduce that error?
[17:33] <myphs> i just run into another bug i guess: subtitles in software-center are just rectangles of the width of the glyph. everything else seems to be just normal. no idea how to reproduce
[17:33] <lotuspsychje> myphs: can you screenshot that please?
[17:34] <roody> sure
[17:34] <roody> i havent used irc in a while how do i send screenshot
[17:34] <lotuspsychje> roody: that message was not for you
[17:36] <lotuspsychje> roody: i dont see the errors you provide
[17:37] <lotuspsychje> roody: or did you try to import a plugin to get that error?
[17:38] <lotuspsychje> roody: reply here please
[17:38] <roody> i will try uninstall and reinstall
[17:39] <roody> because i wasnt writing any plugin
[17:39] <roody> it was failing to import gimpfu from the /usr/lib/gimp/2.0/plugin-uncrop.py
[17:39] <myphs> lotuspsychje: https://imgur.com/a/JeNOaf6
[17:40] <lotuspsychje> roody: where do i try that?
[17:41] <roody> gimp --verbose > launchlog.txt
[17:41] <roody> and just loooking through that file
[17:42] <lotuspsychje> roody: no, i mean did it fail to autoimport plugin in verbose mode, or did you add a plugin manual and get the error after?
[17:43] <roody> oh
[17:43] <lotuspsychje> myphs: wich language is your ubuntu?
[17:43] <roody> it failed to autoimport
[17:44] <lotuspsychje> ok tnx
[17:44] <myphs> lotuspsychje: english us
[17:45] <lotuspsychje> myphs: system up to date?
[17:46] <myphs> lotuspsychje: i just installed it a few hours ago and did an update and it worked perfectly fine aaaand as it seems there's another update ready
[17:46] <myphs> brb
[17:48] <lotuspsychje> roody: i dont even see that uncrop plugin and i dont get error neither
[17:50] <roody> then i think i know whats going on
[17:50] <luna-> Any Ubuntu Desktop and Ubuntu Women Meetings tonight?
[17:53] <roody> because i decided i was smart and installed gimp from muon which i dont think is the official version that ships with the ubuntu software tool
[17:53] <roody> lotus youve been a great help
[17:54] <roody> thanks
[17:54] <lotuspsychje> roody: you installed the snap version perhaps?
[17:54] <roody> im gonna do that now
[17:57] <myphs> lotuspsychje: ok, the update actually fixed it. i didn't expect another update so quickly after another. is noted
[17:57] <lotuspsychje> myphs: i wasnt able to reproduce the glitches in software, but i did have 77mb updates too
[17:57] <lotuspsychje> a lot of QT stuff
[17:59] <myphs> lotuspsychje: the issue must be somewhere in between then, i suppose. my update was around 15mb. well, hopefully it's gone
[18:00] <lotuspsychje> ok great, keep the spirit and the system up to date :p
[18:01] <myphs> haha, will do!
[18:10] <roody> well two for two lotus, i ended up running flatpak version and that works for me
[18:10] <roody> so im off
[18:10] <roody> everything loads correctly
[18:11] <myphs> and i totally forgot: when resizing a window, the window might glitch for a fraction of a second and then return to normality. still there after the update
[18:11] <lotuspsychje> ok, still interesting why that error comes
[18:11] <lotuspsychje> myphs: graphics card driver installed?
[18:13] <myphs> lotuspsychje: i clicked the 3rd party checkbox, if that does it? (Mesa Intel® HD Graphics 620 (KBL GT2))
[18:13] <roody> oh my error, i think its because there used to be a package called gimp-python a before 2.10
[18:13] <roody> and its no longer provided
[18:13] <roody> im not sure though
[18:13] <lotuspsychje> myphs: no, if its intel card alone, driver should get auto loaded
[18:13] <lotuspsychje> roody: but why do you get that error and i not
[18:14] <myphs> lotuspsychje: yes, i only have that intel integrated one
[18:14] <roody> hmm depends on which source you got your gimp from
[18:14] <lotuspsychje> roody: apt
[18:14] <lotuspsychje> !info gimp
[18:14] <lotuspsychje> is this the version you get the error on roody ?
[18:17] <roody> yea
[18:17] <roody> wait
[18:17] <roody> my download size is 4286
[18:18] <lotuspsychje> roody: apt policy gimp, from terminal
[18:19] <roody> Installed: (none)
[18:19] <roody>   Candidate: 2.10.18-1
[18:19] <roody>   Version table:
[18:19] <roody>      2.10.18-1 500
[18:19] <roody>         500 http://kr.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
[18:19] <lotuspsychje> yep
[18:19] <lotuspsychje> same
[18:19] <roody> i could re-install it
[18:19] <roody> to see
[18:19] <lotuspsychje> yes check plz
[18:21] <roody> by the way, im not sure if what im saying will work but myphs are you using bitmap fonts.  since you are resizing something
[18:21] <roody> this could cause the issue
[18:22] <myphs> roody: everything set to default here. and the window is irrelevant. i'm trying to grab some footage to share
[18:25] <roody> well, lotus it doesnt look like after the re-install i got any problems loading the python plugins.
[18:25] <roody> because guess what....
[18:25] <roody> no python modules in /usr/lib/gimp/2.0/plug-ins/
[18:25] <roody> on install
[18:26] <roody> makes sense now
[18:27] <roody> so since i need to use python-fu im just gonna use the flatpak version for now
[18:30] <myphs> we got him: https://imgur.com/a/B7GNJxS
[18:30] <myphs> what a beauty
[18:31] <lotuspsychje> wow
[18:31] <lotuspsychje> myphs: i would suspect that on ati/amd card
[18:32] <lotuspsychje> myphs: can you reproduce that somehow?
[18:32] <myphs> lotuspsychje: sorry, i am not in ownership of any of those
[18:33] <myphs> lotuspsychje: i can resize any window for a while and it happens once in a while, but i have no idea why
[18:34] <myphs> lotuspsychje: BUT! when i use more cpu cycles (when recording with obs for example) it happens less frequently
[18:34] <lotuspsychje> i got intel HD 620 graphics, lemme try that
[18:35] <myphs> any window. left and right seems to trigger it more often
[18:35] <lotuspsychje> hmmm cant make it scramble here
[18:35] <lotuspsychje> myphs: can you open a: journalctl -f and mess around after plz?
[18:37] <lotuspsychje> myphs: this is on xorg or wayland ?
[18:38] <myphs> lotuspsychje: sorry, i have no idea what you mean with journalctl and this is xorg
[18:38] <lotuspsychje> myphs: open a terminal and type: journalctl -f
[18:38] <myphs> lemme try with wayland
[18:39] <lotuspsychje> oh wait
[18:39] <lotuspsychje> you are right
[18:39] <lotuspsychje> i was able to do the same
[18:40] <myphs> yay
[18:41] <lotuspsychje> it scrambled with gnome monitor open on tab graphs and playing rezise very fast
[18:43] <lotuspsychje> myphs: do you know howto file a bug?
[18:44] <myphs> lotuspsychje: i don't know any canonical standards for bug reporting, but yeah
[18:45] <lotuspsychje> myphs: from a terminal: ubuntu-bug gnome-shell
[18:46] <lotuspsychje> myphs: then send the report and launchpad will jump open, add a title + description + your scrambled screenshot
[18:58] <lotuspsychje> myphs: you can make it scramble with other windows too? i seem only can with gnome monitor
[18:59] <myphs> lotuspsychje: yeah, firefox, terminal etc.
[19:00] <lotuspsychje> weird
[19:01] <lotuspsychje> myphs: lemme know the bug ID so i can affect it also
[19:02] <myphs> lotuspsychje: yeah, launchpad is a bit slow right now :/
[19:02] <lotuspsychje> tnx for bug #1872802
[19:02] <myphs> lotuspsychje: ah, here we go: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802
[19:04] <lotuspsychje> myphs: thank you for reporting this
[19:04] <lotuspsychje> myphs: i affected & commented
[19:05] <lotuspsychje> myphs: oh could you also add your graphics card in the description please?
[19:06] <myphs> lotuspsychje: it was a pleasure working with you and will do immediately
[19:07] <lotuspsychje> my pleasure myphs
[19:08] <lotuspsychje> nite ; )
[20:26] <lestac> Studding madagascar like fossa since already!


[14:10] <dimitern> allenap, gmb, jtv, rvba, hey guys, any of your around?
[14:10] <dimitern> you*
[14:10] <allenap> dimitern: otp, doing an interview right now, sorry.
[14:11] <dimitern> allenap, no worries, when you have 5m ping me please
[16:20] <dustmite> hi all, love the work that's been done on MAAS thus far....it is awesome
[16:24] <dustmite> where are the static IP assignments kept, in the postgres db?
[18:20] <blake_r> dustmite: yes help in the db
[18:21] <blake_r> dustmite: thanks
[18:31] <dustmite> thanks