[05:02] <sambagirl> i think future releases should have the option of xfce or mate managers
[05:43] <sambagirl> how do you turn off the dock at the bottom?
[13:18] <manifolder> Hello
[13:55] <simply_shenaniga> manifolder


[12:00] <justaquickquesti> hey guys
[12:01] <justaquickquesti> I'm having some issues installing eclipse
[12:16] <justaquickquesti> gcj forces its way in
[12:16] <justaquickquesti> it doesn't matter if I already have java 5/6/openjdk


[16:56] <jono> mhall119, hey
[16:56] <jono> weird, I created http://uds.ubuntu.com/getinvolved/ but I don
[16:57] <jono> weird, I created http://uds.ubuntu.com/getinvolved/ but I don's see anything
[16:59] <mhall119> jono: what template did you use?
[16:59] <jono> mhall119, I just created a page
[16:59] <mhall119> jono: try "Default" instead of "Default Template"
[16:59] <jono> where do I select a template?
[17:00] <jono> I don't see a place to select a template
[17:02] <mhall119> jono: on the right-side, under the "Page Attributes" section
[17:02] <mhall119> below Parent
[17:02] <jono> aha!
[17:03] <jono> mhall119, fixed
[17:03] <jono> thanks!
[17:03] <mhall119> jono: FYI, dates have been updated on all the uds.u.c pages I found dates on, and the new summit is registered in summit.u.c, so we can announce whenever you're ready
[17:04] <jono> thanks mhall119
[17:04] <jono> mhall119, what is the markup for the numbered steps?
[17:11] <mhall119> jono: I don't know if it's available on uds.u.c
[17:11] <jono> mhall119, ok, np
[17:11] <mhall119> the CSS is part of the developer.u.c theme
[17:12] <mhall119> jono: the sprint is also registered in LP: https://launchpad.net/sprints/uds-1311
[17:12] <jono> thanks mhall119
[17:17] <mhall119> ok, lunch time, bbl
[17:45] <jono> mhall119, I created http://uds.ubuntu.com/getinvolved/propose-a-session/
[17:45] <jono> working on the join page now
[18:18] <jono> mhall119, ok, see http://uds.ubuntu.com/getinvolved/
[18:18] <jono> can you add Get Involved as as top level nav, and the child pages as sub-nav?
[18:20] <mhall119> jono: I'll have to edit the theme branch to add it
[18:20] <mhall119> but yes
[18:21] <mhall119> ugh, jono the sub-nav code in the theme is hard-coded to a page that doesn't exist anymore, so it'll take a bit of fixing up to
[18:21] <mhall119> get subnav working properly
[18:26] <jono> mhall119, ahhh
[18:26] <jono> lets just get the main top level nav added first
[18:27] <mhall119> ok, still going to require a theme edit and deployment though
[18:38] <jcastro> man I just had a sad thought
[18:38] <jcastro> this is the first release we don't get shirts for, just by being at a real UDS
[18:42] <mhall119> jcastro: you just now had that sad thought?  I realized it during uds-1305
[18:59] <jcastro> <-- lunch
[19:26] <mhall119> jono: ok, theme changes made and deployed
[19:26] <jono> thanks mhall119
[19:27] <jono> I am announcing now
[19:27] <mhall119> \o/
[19:33] <jono> mhall119, hey
[19:33] <jono> I am fixing my app name
[19:33] <jono> and I need to upload a new version
[19:33] <jono> it isnt clear to me how I upload a newer version
[19:33] <pleia2> jcastro: yeah, I just bought one from the shop
[19:34] <pleia2> must maintain continuity in my tshirt collection
[19:34] <jono> mhall119, oh got it
[19:35] <jcastro> pleia2: yeah
[19:36] <jcastro> the only one I hate is that horrible one we had in spain
[19:36] <jcastro> the white one with the splashy weird thing
[19:38] <nigelb> Afternoon :)
[19:39] <pleia2> nigelb: sleep well?
[19:39] <jono> mhall119, on http://<IP_ADDRESS>/publish/apps/get-started/ there isnt actually a link to where you upload a new app
[19:39] <nigelb> I got 10 hours of sleep! It was glorious :)
[19:39] <pleia2> :)
[19:39] <nigelb> No more jetlag and the fever definitely seems to have gone.
[19:40] <nigelb> I can see what the hype about this office is about. The view from here is lovely!
[19:41] <pleia2> yay
[19:41] <pleia2> see epic steakhouse across the street?
[19:42] <nigelb> No, I haven't yet.
[19:42] <pleia2> ah ok
[19:42] <nigelb> I'm being a geek and sitting inside and coding :D
[19:42] <pleia2> nice view there too, and tastey :d
[19:42] <pleia2> hehe
[19:43] <pleia2> see, this is why every day I want to go outside and play
[19:48] <mhall119> jono: hmmm, I thought the link on step #1 used to redirect to a page that would allow it...
[19:49] <jono> mhall119, doesnt look like it
[19:49] <mhall119> ah, it should link to just /dev/ not /dev/account/
[19:49] <jono> well step 1 is set up an acct
[19:49] <jono> so maybe a later step links to the page?
[19:50] <jose> jono: ping
[19:50] <jono> hey jose
[19:50] <mhall119> jono: try it now
[19:50] <mhall119> jono: we linked to /dev/ in the current production site
[19:50] <mhall119> for the old store anyway
[19:51] <mhall119> which should take you to the signup form if you don't have an account already
[19:51] <jose> jono: hey, people were asking about your Q&A yesterday, if you could provide a short explanation on your blog it'd be great
[19:51] <jono> mhall119, well, I recommend you keep the first link to the acct page
[19:52] <jono> but then add the link to /dev/ on step 4
[19:52] <mhall119> ok
[19:52] <jono> jose, yeah, will do - things have been a bit hectic recently
[19:52] <jose> thanks! :)
[19:53] <mhall119> jono: refresh and look at step #4 now
[19:56] <jono> mhall119, perfect!
[19:57] <jono> mhall119, can you add the UDS Hallway Track?
[19:57] <jono> ahh it is there
[19:57] <jono> you are fast :-)
[19:58] <jcastro> jono: how's your afternoon? we should sync
[20:00] <jono> jcastro, I am slammed today, tomorrow is fine though
[20:00] <jono> does that work?
[20:01] <jcastro> nod
[20:09] <pleia2> jono: can you send to community-announce as well?
[20:09] <jono> pleia2, sure, which email address?
[20:09] <pleia2><EMAIL_ADDRESS>[20:10] <pleia2> I'll toss up on fridge
[20:10] <jono> sent pleia2
[20:10] <jono> thanks!
[20:10] <jono> pleia2, actually
[20:10] <jono> hold on
[20:10] <jono> I will write a more dedicated post for the fridge
[20:11] <jono> that better explains how to propose sessions
[20:11] <pleia2> ok :)
[20:15] <jono> pleia2, http://pastebin.ubuntu.com/6189701/
[20:15] <jono> thanks!
[20:16] <pleia2> cool, on it
[20:17] <jono> thanks pleia2
[20:19] <pleia2> http://fridge.ubuntu.com/2013/10/03/next-online-ubuntu-developer-summit-19-21-nov-2013/
[20:19] <pleia2> there we go
[20:21] <mhall119> jono: pleia2: http://www.reddit.com/r/Ubuntu/comments/1noeoj/next_ubuntu_developer_summit_uds_dates_announced/
[20:22] <jono> awesome, thanks pleia2 mhall119
[20:23] <jono> mhall119, can you do me a favor?
[20:24] <jono> mhall119, create a sub-page on uds.ubuntu.com/about called Track Leads and list each track and include mugshots, names, and contact details for each of the track leads
[20:25] <mhall119> jono: the tracks page on summit.u.c isn't enough?
[20:26] <jono> mhall119, I dont see mugshots and contact details
[20:26] <jono> mhall119, I recommend we only use summit for the scheduling
[20:26] <jono> and uds.u.c for metadata about the event
[20:28] <mhall119> ok
[20:28] <jono> mhall119, who are the current list of track leads?
[20:28] <jono> I want to make sure I don'
[20:28] <jono> I want to make sure I don't miss some people
[20:28] <mhall119> jono: I'm assuming same track leads as last time
[20:28] <jono> mhall119, yup
[20:28] <mhall119> jono: I haven't added them to summit yet
[20:28] <mhall119> who for design?
[20:28] <jono> mhall119, waiting to hear back from them
[20:29] <mhall119> ok
[20:34] <mhall119> jono: smoser will be at an event that week, is that correct?
[20:40] <jono> mhall119, npo
[20:40] <jono> that was the week before
[20:46] <mhall119> ok


[16:27] <vaganyik> leave
[19:47] <vaganyik> leave
[21:37] <lmat> I installed vino, but there is no vino-preferences. What should I do? I restarted hoping to invoke the deep magic, but it did not work.
[21:37] <lmat> I'm trying to follow, for instance, https://medium.com/@aldo_mx/simplest-way-to-configure-vnc-server-in-xubuntu-16-04-lts-and-newer-6c0b3ae21fe5
[21:43] <lmat> find / -name vino-preferences -print 2>/dev/null; returns nothing.
[21:53] <brainwash> lmat: "Apparently the functionality of vino-preferences was merged into gnome-control-center for 18.04."


[09:16] <lordievader> Good morning.
[09:17] <OerHeks> hey lordievader :-)\
[09:17] <lordievader> Hey OerHeks, how are you?
[09:18] <ducasse> morning, all!
[09:19] <lordievader> Hey ducasse
[09:19] <ducasse> all is well?
[09:20] <OerHeks> fine thank you, long time no see lordievader
[09:20] <OerHeks> hi ducasse
[09:20] <lordievader> Here it is :) how are you ducasse
[09:20] <lordievader> OerHeks: Great. Indeed, long time ;)
[09:20] <ducasse> couldn't be better :)
[13:16] <ducasse> this "ubuntu on windows" thing is not something that is supported in #ubuntu, is it?
[13:54] <OerHeks> !ubuwin
[13:54] <OerHeks> ducasse, ^^  glad we don't have to
[14:02]  * ducasse breathes a sigh of relief
[14:03] <ducasse> i seriously wanted to tell that guy to f**k off, but i'd probably been banned.
[14:06] <OerHeks> there is other dude, that runs ubuntu on top of win10 ..
[14:06] <OerHeks> not official i guess
[14:07] <OerHeks> http://linux.softpedia.com/blog/you-can-now-run-ubuntu-linux-with-the-unity-desktop-on-top-of-windows-10-506159.shtml
[14:07] <ducasse> omg.
[14:08]  * ducasse buries his head in is hands and cries quietly.
[14:08] <OerHeks> wait ..
[14:08] <OerHeks> this one makes me bark .. https://community.skype.com/t5/Linux/Exciting-news-for-Linux-users/td-p/4430988
[14:12] <ducasse> i really couldn't care less about skype for linux, imo we should promote open options...
[14:16] <ducasse> but, "exciting news" - they really are full of themselves :)
[16:14] <DJones> If they update the desktop app for skype, then all well and good to them, not something I use anyway, but would consider if it was regularly updated
[21:25] <ark-knight> is it possible to download a cd that automatically installs ubuntu?
[21:25] <daftykins> that sounds a lot like a support question which belongs in #ubuntu
[21:26] <daftykins> and no


[00:00] <acheronuk> right. going to say goodnight I think
[00:00] <acheronuk> trying not to burn candle at both ends this week
[00:00] <acheronuk> I bet I'm back at 2am when I can't sleep or something now I've said that!
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #799: SUCCESS in 7 min 1 sec: http://kci.pangea.pub/job/mgmt_merger/799/
[00:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-sdk build #107: STILL FAILING in 11 min: http://kci.pangea.pub/job/zesty_unstable_plasma-sdk/107/
[00:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevplatform build #150: STILL FAILING in 21 min: http://kci.pangea.pub/job/xenial_unstable_kdevplatform/150/
[00:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevplatform build #142: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_kdevplatform/142/
[00:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #52: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_kproperty/52/
[00:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdb build #41: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kdb/41/
[00:44] <tsimonq2> acheronuk, clivejo: OMG HAHAHAHAHAHAHAHAHAHA so remember that ark test we tried to fix? https://youtu.be/zhJQSpy3Luc?t=22m30s take a look :P
[00:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_k3b build #33: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/yakkety_unstable_k3b/33/
[00:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #236: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/236/
[00:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #200: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/200/
[00:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #52: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/xenial_unstable_kdb/52/
[00:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #298: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/xenial_unstable_cantor/298/
[00:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #310: STILL FAILING in 38 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/310/
[00:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-cli-tools build #275: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_kde-cli-tools/275/
[00:57] <sintre> ahh yummy roast beef
[00:58] <sintre> all done wxl around
[01:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #89: STILL UNSTABLE in 52 min: http://kci.pangea.pub/job/zesty_unstable_kopete/89/
[01:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdiagram build #53: STILL UNSTABLE in 52 min: http://kci.pangea.pub/job/yakkety_unstable_kdiagram/53/
[01:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #97: FAILURE in 16 min: http://kci.pangea.pub/job/zesty_unstable_kstars/97/
[01:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #366: FAILURE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kstars/366/
[01:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kproperty build #57: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/zesty_unstable_kproperty/57/
[01:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdb build #49: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/zesty_unstable_kdb/49/
[01:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #93: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/93/
[01:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #47: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/xenial_unstable_trojita/47/
[01:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #110: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/zesty_unstable_marble/110/
[01:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #104: STILL UNSTABLE in 41 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/104/
[01:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #66: STILL UNSTABLE in 1 hr 17 min: http://kci.pangea.pub/job/yakkety_unstable_krita/66/
[01:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdb build #42: STILL FAILING in 34 min: http://kci.pangea.pub/job/yakkety_unstable_kdb/42/
[01:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevplatform build #151: STILL FAILING in 35 min: http://kci.pangea.pub/job/xenial_unstable_kdevplatform/151/
[01:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevplatform build #143: STILL FAILING in 36 min: http://kci.pangea.pub/job/yakkety_unstable_kdevplatform/143/
[01:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #232: FAILURE in 42 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/232/
[02:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #178: STILL UNSTABLE in 55 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/178/
[02:10] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okular build #120: STILL UNSTABLE in 55 min: http://kci.pangea.pub/job/zesty_unstable_okular/120/
[02:10] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #78: STILL UNSTABLE in 55 min: http://kci.pangea.pub/job/zesty_unstable_kdiagram/78/
[02:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #80: STILL UNSTABLE in 55 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/80/
[02:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #367: STILL FAILING in 28 min: http://kci.pangea.pub/job/xenial_unstable_kstars/367/
[02:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #233: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/233/
[02:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #98: STILL FAILING in 31 min: http://kci.pangea.pub/job/zesty_unstable_kstars/98/
[02:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #329: STILL FAILING in 22 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/329/
[02:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_spectacle build #89: STILL UNSTABLE in 46 min: http://kci.pangea.pub/job/zesty_unstable_spectacle/89/
[02:24] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #90: STILL UNSTABLE in 46 min: http://kci.pangea.pub/job/zesty_unstable_cantor/90/
[02:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #282: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/282/
[02:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #209: STILL UNSTABLE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_okular/209/
[02:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalzium build #116: STILL UNSTABLE in 57 min: http://kci.pangea.pub/job/yakkety_unstable_kalzium/116/
[02:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #156: STILL UNSTABLE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/156/
[02:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #186: STILL UNSTABLE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/186/
[02:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #207: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/207/
[02:24] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpimtextedit build #98: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_kpimtextedit/98/
[02:29] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-sdk build #108: STILL FAILING in 1 hr 14 min: http://kci.pangea.pub/job/zesty_unstable_plasma-sdk/108/
[02:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #330: STILL FAILING in 8 min 34 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/330/
[02:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #311: STILL FAILING in 57 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/311/
[02:50] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_korganizer build #75: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/zesty_unstable_korganizer/75/
[02:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #68: STILL UNSTABLE in 1 hr 49 min: http://kci.pangea.pub/job/xenial_unstable_krita/68/
[02:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-cli-tools build #216: STILL UNSTABLE in 1 hr 23 min: http://kci.pangea.pub/job/yakkety_unstable_kde-cli-tools/216/
[03:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #211: STILL FAILING in 1 hr 2 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/211/
[03:03] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevplatform build #108: STILL FAILING in 28 min: http://kci.pangea.pub/job/zesty_unstable_kdevplatform/108/
[03:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kexi build #61: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/yakkety_unstable_kexi/61/
[03:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #91: STILL UNSTABLE in 1 hr 49 min: http://kci.pangea.pub/job/zesty_unstable_krita/91/
[03:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #161: FIXED in 43 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/161/
[03:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #171: STILL FAILING in 39 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/171/
[03:21] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevplatform build #109: STILL FAILING in 12 min: http://kci.pangea.pub/job/zesty_unstable_kdevplatform/109/
[03:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_korganizer build #62: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_korganizer/62/
[03:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #212: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/212/
[04:13] <wxl> sintre: yo yo yo
[04:13] <sintre> welcome back
[04:13] <sintre> off in utube land had to shut down system
[04:13] <sintre> rdy to start again
[04:14] <wxl> so log into that tab
[04:14] <sintre> got a ubuntu account rolling
[04:14] <sintre> got restart sry drained batt to 20% i don't wanna try it hehe
[04:14] <sintre> botting now
[04:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #80: STILL UNSTABLE in 2 hr 5 min: http://kci.pangea.pub/job/xenial_unstable_calligra/80/
[04:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #172: STILL FAILING in 57 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/172/
[04:20] <sintretester2> god i have to make easier passowrds lol
[04:20] <sintretester2> ok let start from scratch
[04:20] <sintretester2> console open
 Connected to the Internet?
[04:21] <sintretester2> yep on the machie ow
[04:21] <sintretester2> now bla
 Take ubiquity to the point of failure
[04:22] <sintretester2> commands
 Um open the installer
[04:23] <sintretester2> or are is that slang for the installer
 Ubiquity is the name of the installer
[04:24] <sintretester2> its do i slow as a snail thing once i selecrt to move on t disk like before
[04:24] <sintretester2> k there again same result what commadnd we need
 Do `ubuntu-bug ubiquity` and go through all the prompts until you get that login tab in the browser
[04:25] <sintretester2> link to pic pos place again i'll show you
[04:26] <sintretester2> same apport screen
[04:26] <sintretester2> as before came up
 Just go all the way through it until you get your login tab
[04:28] <sintretester2> in what bug descrition
[04:28] <sintretester2> wants sry
[04:28] <sintretester2> what should would titleit
 So describe it
[04:29] <sintretester2> help me ut here lol
 Ubiquity doesn't offer auto-resize option work GPT partition table containing Windows and Ubuntu installs
 s/work/on/
[04:31] <sintretester2> ok not it wants athed files
[04:32] <sintretester2> so what rea out should we do orshould i use screens
[04:32] <sintretester2> attached files bla
 I have no clue what you're saying
[04:32] <sintretester2> srry me and chicklet keyboard doesn't get along wwll
 Type slower
[04:33] <sintretester2> httpp if you can for screens i'll show you
 http://imgur.com
[04:35] <sintretester2> http://imgur.com/a/kJYzp
 You just need to fill in further information
 A good bug report should have:
 1. Steps to reproduce
 2. Expected results
 3. Actual results
[04:37] <sintretester2> let me get o ther system for a bi on this
[04:38] <sintretester2> bit bla
[04:38] <sintretester2> snd i'll text myself
[04:41] <sintre> Problem is as best i can follow with kubuntu 16.04.2   :installer will not see and auto- adjust partion or give the option to do so
[04:41] <sintre> it a start lol workin on it atm
 You're kind of thinking about it wrong
 Tell you what. Just copy the title into further info for now
[04:42] <sintre> ok
 You can edit later from the other machine
[04:44] <sintre> done for now
[04:44] <sintre> so hope you can see it show up had to use other machine to sumbit
 Give me a link
[04:44] <sintre> god that damn laptop is birght when on dsc power lol
 Or you can say bug number here
[04:45] <sintretester2> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1664440
[04:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_korganizer build #66: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/yakkety_unstable_korganizer/66/
 There you go
 Congrats on your first bug. I'll take it from here
[04:46] <sintretester2> thx i think the logd are same
[04:47] <sintretester2> same system same stik
 Sounds good
 Bbl
[04:47] <sintretester2> so logs should beidentical even if we did them again
[04:48] <sintre> ahh cool i see it did serve up some adition read outs
[04:53] <sintre> well not cool if you gota try to make sense of it all
[04:53] <sintre> damn bigger read outs than i thought lol
 You should get an update that I edited the description. That's how a bug report should be written
[05:02] <sintre> i gotta start somehwere :)
[05:02] <sintre> i wonder how much fire i'll take lol
[05:02] <sintre> but i don't mind that
[05:03] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdbusaddons build #101: STILL UNSTABLE in 8 min 50 sec: http://kci.pangea.pub/job/zesty_unstable_kdbusaddons/101/
[05:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #191: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/191/
[05:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemviews build #95: STILL UNSTABLE in 9 min 50 sec: http://kci.pangea.pub/job/zesty_unstable_kitemviews/95/
[05:07] <sintre> thx wxl  your right that description would give people wosmething to work with
[05:07] <sintre> thx for a lesson
 No problem
 So now you know go file some more bugs XD
 Read here for more instructions through:
 !bugs
 Ugh do that. Ubottu won't listen to me while on telegram
[05:09] <sintre> can anybody just "edit" a persons bug report or some tier of bug tracking moderators
 I think anyone can but I don't remember
 I have the highest level of control
[05:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwidgetsaddons build #104: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_kwidgetsaddons/104/
[05:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kjobwidgets build #246: STILL UNSTABLE in 7 min 7 sec: http://kci.pangea.pub/job/yakkety_unstable_kjobwidgets/246/
[05:28] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwallet build #90: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kwallet/90/
[05:28] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kjobwidgets build #95: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kjobwidgets/95/
[05:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdbusaddons build #263: STILL UNSTABLE in 7 min 53 sec: http://kci.pangea.pub/job/yakkety_unstable_kdbusaddons/263/
[05:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kguiaddons build #188: STILL UNSTABLE in 8 min 52 sec: http://kci.pangea.pub/job/yakkety_unstable_kguiaddons/188/
[05:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcompletion build #171: STILL UNSTABLE in 8 min 52 sec: http://kci.pangea.pub/job/yakkety_unstable_kcompletion/171/
[05:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcodecs build #260: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kcodecs/260/
[05:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcoreaddons build #199: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kcoreaddons/199/
[05:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwidgetsaddons build #265: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kwidgetsaddons/265/
[05:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ki18n build #259: STILL UNSTABLE in 8 min 48 sec: http://kci.pangea.pub/job/yakkety_unstable_ki18n/259/
[05:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kguiaddons build #372: FAILURE in 4 min 9 sec: http://kci.pangea.pub/job/xenial_unstable_kguiaddons/372/
[05:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdbusaddons build #399: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_kdbusaddons/399/
[05:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ki18n build #394: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_ki18n/394/
[05:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcodecs build #376: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_kcodecs/376/
[05:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfig build #409: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_kconfig/409/
[05:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwidgetsaddons build #388: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_kwidgetsaddons/388/
[05:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kconfigwidgets build #226: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_kconfigwidgets/226/
[05:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemviews build #366: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_kitemviews/366/
[06:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kguiaddons build #373: NOW UNSTABLE in 9 min 36 sec: http://kci.pangea.pub/job/xenial_unstable_kguiaddons/373/
[06:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #367: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/367/
[06:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #389: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/389/
[07:52] <santa_> good morning everyone
[07:55] <sintre> ok i just found wierdest crap ever
[07:55] <sintre> posting in offtop lol
[08:45] <acheronuk> Morning :)
[08:45] <sintre> hi there
[08:45] <sintre> well almost sleep time for me lol
[08:46] <sintre> well success kinda , i logined in and https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1664440
[08:46] <sintre> xxl did all the typing lol
[08:46] <sintre> but its out there with full info now
[08:47] <sintre> i mean wxl
[08:47] <sintre> so now i guess we wait
[10:35] <acheronuk> santa_:  https://launchpad.net/ubuntu/+source/gdk-pixbuf/2.36.5-0ubuntu1
[10:37] <acheronuk> amd64 not building for that, so no binary-indep packages produced, so kdeplasma-addons build-dep chain for -proposed for non amd64 build is borked?
[10:38] <santa_> oh, maybe
[10:38] <acheronuk> apt-get install scim-dev libscim-dev libscim8v5 libgtk2.0-dev libgtk2.0-0 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common
[10:39] <santa_> great, so now I have 2 problems in my table and not just one XD
[10:39] <acheronuk> The following packages have unmet dependencies:
[10:39] <acheronuk>  libgdk-pixbuf2.0-0 : Depends: libgdk-pixbuf2.0-common (= 2.36.5-0ubuntu1) but 2.36.4-1 is to be installed
[10:39] <santa_> thank you very much for pointing that out
[10:39] <acheronuk> following the build deps one by one
[10:39] <acheronuk> santa_: np. it just seemed very odd, so I checked!
[10:39] <santa_> regarding the other problem
[10:40] <santa_> http://gpul.grupos.udc.es/buildstatus_ubuntu-exp2/ubuntu-exp2_status_plasma.html
[10:40] <santa_> I still have no clue why that files are gone in my build server
[10:41] <santa_> (hence the rebuild in the ppa)
[10:42] <santa_> just waanted to test if something changed in zesty which might be triggering that
[10:42] <santa_> s/waanted/wanted/
[10:44] <acheronuk> appstream files going missing? no, I had the same thing with plasma-workspace (I think), and try as I might I could not work out why they vanished. Identical thing happened in KCI to the same package at the same time.
[10:51] <acheronuk> seems some has poke the rebuild button on gdk-pixbuf, so fingers crossed
[10:51] <acheronuk> spoke too soon. amd64 still failed
[11:00] <acheronuk> santa_: lovely. plasma-desktop also has a scim-dev build dep :/
[11:03] <santa_> well, let's hope someone will fix it because I'm busy with other things
[11:39] <BluesKaj> Hi all
 Morning
 SHOOT URGHHHH
 My shell is down, no IRC for me
 (Photo, 800x600) https://irc-attachments.kde.org/W1mY0Av7/file_1976.jpg
 In case you want to learn Spanish, Simom
 @tsimonq2, not missing much
[21:09] <ahoneybun> acheronuk: about babe qt player
[21:09] <ahoneybun> I don't think we have a kf5 version of knotifications
[21:14] <acheronuk> knotifications is part of frameworks now, so Kf5 by definition
[21:14] <ahoneybun> mm
[21:15] <ahoneybun> Project ERROR: Unknown module(s) in QT: KNotifications
[21:17] <acheronuk> you need to have [ taglib - knotification lib - qt 5.8 libs ]installed in order to compile this app from source
[21:17] <ahoneybun> I have no idea the package names for Ubuntu though
[21:17] <ahoneybun> I can't find anything from kf5 knotifications in p.u.com
[21:17] <acheronuk> well, we don't have Qt 5.8 to start with
[21:17] <ahoneybun> mm
[21:17] <ahoneybun> right
[21:17] <ahoneybun> guess I'll have to wait for someone to snap it
[21:24] <acheronuk> maybe a standalone Qt install of 5.8 from qt.io would work. not tried stuff with that for ages though
[22:11] <acheronuk> santa_: what is happening with frameworks?
[22:12] <santa_> acheronuk: nothing actually, I think we are ready to upload both frameworks and plasma. I mean if anything with kdeplasma-addons we could allways fix it later
[22:13] <santa_> today I have been struggling with getting plasma 5.9 working on my virtualbox, but if you tested that at least plasma starts I think we are good to go
[22:14] <santa_> and I think you did it, didn't you?
[22:14] <acheronuk> back in 2 secs
[22:16] <acheronuk> santa_: yes, I am running plasma 5.9.1 from staging on this PC. seems
[22:16] <acheronuk> *seems fine
[22:16] <acheronuk> santa_: typically, 5.9.2 is out today
[22:16] <santa_> so you have my green light
[22:17] <santa_> well we can upload so we start to see autopkgtests/migration issues
[22:18] <santa_> and at the same time we could stage 5.9.2
[22:18] <acheronuk> yep, can do
[22:18] <santa_> do we need freeze exeption for 5.9.2 being a bugfix release?
[22:18] <acheronuk> nope
[22:18] <santa_> * exception
[22:19] <santa_> allright, so I vote for uploading asap
[22:19] <acheronuk> santa_: as long as there are no no 'features'
[22:20] <sintre> well bug me and wxl worked on last two days have one comment as of yet
[22:21] <sintre> sowaiting around probally not good lol
[22:21] <sintre> seems might tke very long time to get help lol
[22:21] <sintre> but hey got atleast one comment
[22:21] <sintre> :)
 Feature Freeze is NOT in effect yet...
[22:22] <santa_> yes but it's coming soon
 Soon meaning a few days
[22:25] <sintre> this alot more ability to modify software for the iso?
[22:26] <valorie> Feature Freeze the 16th, according to the sched
[22:26] <valorie> and our beta 1 freeze is the 23rd
[22:27] <sintre> 9 days out then
[22:28] <sintre> atleast on offical release dates that is
[22:28] <sintre> i assume somebody has it in there hands by now
[22:32] <valorie> we're not ready for beta 1 yet, if that's what you mean
[22:33] <sintre> yea , just wanted to know if somebody has it in thier hands yet and if any probs is all
[22:33] <sintre> are you in idia yet :)
[22:33] <sintre> india
[22:34] <valorie> oh, I don't fly until the 7th of March
[22:34] <valorie> gosh, I need all the days between now and then to prepare
[22:35] <sintre> ohh thought you were leaving yesterday lol sry , you mentioned it
[22:35] <sintre> not dates though my bad
[22:35] <sintre> remember to pack your own peanuts
[22:35] <sintre> long haul travel is a nightmare
[22:36] <sintre> this is getting anooying , somebody out there has to have a gtp partion with a duel win10 install out there
[22:36] <sintre> just so it can get confirmed
[22:37] <sintre> thats probally gotta happen before any attention is gonna go to it
[22:43] <acheronuk> santa_: right. sorry. got sidetracked. I shall just do that upload my end then? or have you stuff built, and git tags signed etc?
[22:43] <sintre> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1664440
[22:43] <sintre> lol wrong chanl sry
[22:47] <santa_> acheronuk: you can go ahead running do-all gbp-archive, let me know if you need any assistance
[22:48] <santa_> once done I would just double check that the thing was properly pushed and taged in git
[23:14] -kubuntu-ci:#kubuntu-devel- Starting build #26 for job mgmt_pause_integration (previous build: ABORTED)
[23:21] <acheronuk> tsimonq2: your shell back?
[23:22] <tsimonq2> acheronuk: yep
[23:30] <acheronuk> santa_: FW and plasma uploaded
[23:32] <santa_> acheronuk: thank you very much, I'm going to update my clones
[23:33] <valorie> \o/
[23:34] <valorie> how close are we to being up-to-date on Apps?
[23:34] <valorie> besides PIM
[23:36] <acheronuk> valorie: will get to them once FW and plasma get built and migrated as they can
[23:36] <acheronuk> valorie: language pack update needs to be looked 1st I think though
[23:37] <acheronuk> *looked at
[23:41] <santa_> acheronuk: everything seems in place
[23:41] <acheronuk> santa_: good :)
[23:41] <santa_> acheronuk: regarding plasma probably I will want to poke you a bit tomorror to catch up with your work
[23:42] <santa_> I had more than enough of kubuntu today
[23:43] <acheronuk> santa_: ok. should be around parts of the afternoon and evening tomorrow, or not far away
[23:45] <santa_> thank you


[01:25] <chrisccoulson> Laney - this pidgin update is a PITA ;)
[01:25] <chrisccoulson> i've got it to build now, and it even connects successfully to yahoo
[01:26] <chrisccoulson> but then it crashes immediately
[01:26] <chrisccoulson> oh well!
[02:14] <TheMuso> .c
[07:14] <didrocks> >qzqy
[08:06] <didrocks> (^ for the record, this is a /away in qwerty on an azerty keyboard ;))
[08:47] <pitti> Good morning
[08:48] <chrisccoulson> good morning pitti
[08:55] <chrisccoulson> pitti - i made some progress on the pidgin SRU last night
[08:55] <chrisccoulson> it builds fine, and connects to yahoo now
[08:55] <chrisccoulson> but then it crashes :(
[08:55] <chrisccoulson> so, still some more work for me to do on that ;)
[08:58] <pitti> chrisccoulson: great to hear!
[08:58] <chrisccoulson> yeah, it's getting there:)
[08:58] <pitti> chrisccoulson: did you just backport the entire yahoo stack? (might be easier)
[08:59] <chrisccoulson> pitti - i didn't do that. i managed to get the existing patch to apply with a bit of re-factoring
[09:00] <chrisccoulson> but it currently adds 2 new members to an existing public struct in libpurple, which we probably want to avoid for a SRU
[09:00] <chrisccoulson> so theres still a bit for me to do on that
[09:00] <pitti> chrisccoulson: that doesn't sound like an API break, though?
[09:00] <pitti> ABI, I mean
[09:01] <chrisccoulson> i can leave it as it is if you're ok with it
[09:01] <seb128> hey chrisccoulson pitti
[09:01] <pitti> chrisccoulson: I think here it is safer to backport the entire stack than trying to mix old and new code; but I haven't really looked into it
[09:02] <seb128> pitti, the netbook reinstall worked just fine there
[09:02] <seb128> out of the fact that the mini 10 wireless doesn't seem to work
[09:02] <chrisccoulson> pitti  - yeah, i'm not sure. my only concern is that we break other protocols that use this functionality in libpurple
[09:02] <chrisccoulson> hey seb128
[09:02] <seb128> it wasn't working on jaunty either
[09:02] <seb128> but it's working on the unr image
[09:02] <seb128> which is weird
[09:04] <pitti> hey seb128
[09:08] <seb128> hey rickspencer3
[09:08] <rickspencer3> hi seb128
[09:08] <rickspencer3> seb128, what's the word on the street?
[09:08] <seb128> all good as far as I can see there
[09:09] <seb128> I reinstalled my mini 10 using an usb key without whipping install and it worked great
[09:09] <rickspencer3> great!
[09:10] <seb128> and my bugsmail box was not flooded today
[09:10] <seb128> ie I already did read the backlog from the night
[09:10] <pitti> hey rickspencer3
[09:10] <seb128> good start of day there
[09:10]  * seb128 in good mood today ;-)
[09:10] <pitti> euca still has a major installer bug, and there seems some trouble with i386+PAE, but otherwise good
[09:12] <rickspencer3> pitti, bug #s?
[09:12] <pitti> rickspencer3: bug 458904
[09:13]  * rickspencer3 is setting next to mdz ;)
[09:13] <pitti> rickspencer3: the other is just being discussed between cjwatson and ara in #u-release
[09:13] <rickspencer3> hi mdz
[09:15] <rickspencer3> thanks pitti
[09:23] <mdz> pitti, the installer bug is not so major in my opinion, given the relative maturity of the feature. we decided last night to release note it since there is a workaround (manual configuration)
[09:58] <proppy> hi
[09:58] <proppy> kenvandine: could you remind me the EmpathyChatWindow bug #?
[10:26] <pitti> seb128: btw, it seems the brasero upload got rejected? could you re-do that as SRU, please?
[10:27] <seb128> pitti, the upgrade was from robert_ancell and the upload from themuso I think I will let them deal with that
[10:27] <pitti> ok
[10:27] <seb128> pitti, I will ping robert_ancell to tell him to do a sru
[10:27] <seb128> pitti, thanks for following up there though
[10:34] <seb128> pitti, new ubiquity, means respin of all images?
[10:34] <pitti> seb128: only i386, not all the other arches
[10:34] <seb128> pitti, new ubiquity, means respin of all images?
[10:34] <seb128> ups
[10:34] <pitti> seb128: that's why we uploaded to karmic-updates
[10:34] <seb128> should really stop to scrolling up with focus going somewhere else
[10:34] <pitti> so that we can re-spin i386 only
[10:34] <seb128> thanks touchapd
[10:34] <pitti> heh
[10:35] <seb128> pitti, ok
[10:35] <pitti> unfortunate, but unavoidable :-(
[10:35] <seb128> alright, I'm just asking because I didn't reinstall my laptop yet
[10:35] <seb128> I will do that once the respin is there
[10:36] <seb128> so far I reinstall my netbook and desktop worked great
[10:36] <pitti> great, thanks
[10:36] <seb128> reinstalled rather
[10:36] <pitti> oh, your zoo has three computers now?
[10:36] <seb128> it's faster to reinstall than to do rc to karmic upgrades
[10:36] <seb128> yes, a desktop, a laptop and a netbook
[10:36] <seb128> I don't use the desktop much nowadays though
[10:37] <seb128> rather the laptop on the dock
[10:37] <seb128> but the box is still there
[10:42] <TheMuso> seb128: Already told him./
[10:42] <mvo> seb128: could you still do a upgrade for me please? even if it takes long :) ?
[10:42] <seb128> TheMuso, thanks
[10:42] <mvo> seb128: just to report problems
[10:42] <TheMuso> seb128: slangasek asked me to SRU it, and I passed it onto Robert.
[10:42] <seb128> mvo, which one?
[10:43] <mvo> seb128: I don't mind, one that you use and that is not upgraded yet
[10:43] <seb128> mvo, in fact I did upgrade my laptop yesterday which worked
[10:44] <seb128> I was still planning to reinstall because I've the feeling things get slower over years
[10:44] <seb128> or it's just karmic boot time which went down
[10:44] <seb128> I remember feeling my laptop being quite fast to boot when I got it
[10:44] <seb128> it seems to take ages now
[10:44] <mvo> seb128: ok, thats fine, I was only interessted in hearing about upgrade issues :)
[10:45] <seb128> mvo, no issue from my side but I don't install tons of crazy things
[10:45] <seb128> ie I've pretty much a standard install, those are well tested ;-)
[10:45]  * mvo nods
[10:48] <seb128> grub to gdm is over a minute on bootcharts there
[10:48] <seb128> it's almost 2 minutes from start to desktop loaded
[10:49] <seb128> it takes almost 15 seconds for xorg to start on the bootchart
[10:49] <seb128> I'm wondering what is going on
[10:49] <seb128> bbl, doing some boot charting and testing
[11:01]  * Ng wonders why seahorse-agent isn't running
[11:01] <Ng> I'm getting proper SSH key behaviour from something, but not for GPG keys (fresh karmic install on sunday)
[11:04] <didrocks> Ng: You have to install seahorse-plugins
[11:04] <Ng> didrocks: yeah I'm wondering if I installed that after I last booted
[11:04] <didrocks> it's no more part of default installation
[11:04] <didrocks> hey pedro_
[11:04] <pedro_> salut didrocks
[11:05] <Ng> hah, well given that I've not actually rebooted this install since the first day I used it, I guess that's what it is
[11:05] <Ng> sorry ;)
[11:05] <didrocks> Ng: yeah, the session is launched in /etc/xdg/autostart IIRC (I didn't checked)
[11:05] <didrocks> so, just loggin off and on should do the trick
[11:06] <Ng> didrocks: I think that's seahorse-daemon, seahorse-agent is from Xsession.d
[11:06] <Ng> I'll log out in a bit and check :)
[11:10] <huats> morning !
[11:21] <pitti> bonjour huats!
[11:21] <pitti> seb128: new i386 iso ETA < 1 hour, FYI
[11:25] <seb128> pitti, ok thanks, let's get lunch now then
[11:45] <seb128> pitti, do you know if there is any driver difference between unr and standard ubuntu?
[11:45] <pitti> seb128: shouldn't be; it's the same kernel, unless you are using the lpia one?
[11:45] <seb128> no I'm not
[11:46] <seb128> the wireless on my mini 10 is working only on unr though for some reason
[11:52] <chrisccoulson> hmmm, it seems that users keep thinking that the sporadic placement of icons in the places and system menu is a bug
[11:54] <seb128> chrisccoulson, right, that and the 2 slots notify-osd logic
[11:54] <seb128> I think those are 2 design errors
[11:55] <chrisccoulson> seb128 - i've not really followed the discussion about the notify-osd logic
[11:55] <seb128> but seems the design team seems to break at least one thing by cycle before considering changing back next cycle under user reaction
[11:55] <chrisccoulson> i agree with the concept of no icons, but the places menu does look broken at the moment, and users think so too :(
[11:55] <chrisccoulson> it would look better with no icons at all
[11:56] <seb128> users keep filling bugs about bubbles not being in the corner
[11:56] <seb128> the bug is quite popular
[11:56] <seb128> they did set up a ppa with a notify-osd with 1 slot too
[11:56] <seb128> which is quite popular too
[11:56] <chrisccoulson> i quite like the new notify-osd design :)
[11:56] <seb128> the 2 slots?
[11:57] <seb128> I hate it
[11:57] <chrisccoulson> really?
[11:57] <seb128> bubbles keep going over my firefox tabs
[11:57] <chrisccoulson> i don't have to lift my head up as far to read notifications ;)
[11:57] <chrisccoulson> oh, ok. i didn't notice that, but then i never have windows maximized
[11:57] <chrisccoulson> that's probably why it hasn't annoyed me yet ;)
[11:57] <seb128> I've most of the things I use take one workspace
[11:58] <seb128> email client on one workspace
[11:58] <seb128> IRC client on one another
[11:58] <seb128> web browser on one another
[11:58] <Ng> seb128++, for workspace layout sanity, and correctness about the silly bubble position ;)
[11:58] <chrisccoulson1> i tend to use e-mail on one workspace, but everything else on another
[11:58] <chrisccoulson1> i should make better use of my screen real-estate really ;)
[11:58] <seb128> admittedly bubble are transparent on mouse overt but when you switch tabs using keyboard it still goes in the way
[11:59] <chrisccoulson1> yeah, that would be annoying
[11:59] <chrisccoulson1> i see everyones point now ;)
[12:00] <chrisccoulson1> i definately hate the places menu though!
[12:00] <seb128> also most users don't use synchronous notifications often
[12:00] <seb128> so they don't why bubbles are shifted
[12:00] <seb128> same here
[12:00] <seb128> especially that the 2 other menus have icons
[12:00] <seb128> so it really looks weird and buggy
[12:01] <Ng> seb128: non-laptop people could conceivably never use sync notifications
[12:01] <Ng> if you don't have volume keys or brightness keys, your bubbles always look wrong ;)
[12:01] <seb128> Ng, right, many keyboard have volume keys though
[12:01] <Ng> sure
[12:01] <chrisccoulson1> seb128 - yeah, i agree. everyone i've shown it to seems to feel the same too.
[12:02] <seb128> chrisccoulson1, any idea about https://bugzilla.gnome.org/show_bug.cgi?id=599209 btw?
[12:02] <mvo> those are probably not "target users" - that is the argument I usually when when trying to argue issues like that
[12:03] <seb128> mvo, +get?
[12:03] <mvo> seb128: yes
[12:03]  * mvo was sure he typed thet get
[12:03] <chrisccoulson1> seb128 - i've not noticed that one yet. i can take a look at it though
[12:03] <mvo> the cat ate it!
[12:03] <seb128> mvo, what users are not the target? the ones not cleaver enough to not understand the 2 slot logic? ;-)
[12:03] <seb128> clever
[12:03] <mvo> exactly
[12:04] <seb128> I just find it looks weird
[12:04] <seb128> and keep going over my tabs, I liked it better when it went over the search entry
[12:04] <chrisccoulson1> seb128 - i've assigned the LP bug to me. i'll take a look when i next get the chance
[12:04] <seb128> chrisccoulson1, thanks
[12:04] <seb128> chrisccoulson1, upstream suggested it might be due to an ubuntu change
[12:05] <seb128> but g-s-d upstream is a bit too inclined to blame bugs on  ubuntu changes sometime
[12:05] <chrisccoulson1> it seems that every upstream is like that recently ;)
[12:05] <seb128> we might be doing too many change
[12:06] <seb128> oh, I just download a fedora 12 beta iso
[12:06] <seb128> let me try in kvm if it has the issue
[12:06] <seb128> downloaded rather
[12:06]  * seb128 boots kvm
[12:06] <chrisccoulson1> yeah, we definately carry too many patches on some packages
[12:06] <seb128> urg, their boot screen is really weir
[12:06] <seb128> weird
[12:07] <chrisccoulson1> i just get the plymouth fallback with fedora
[12:07] <seb128> they have a white, light blue, blue bar
[12:07] <chrisccoulson1> that's what i see
[12:07] <seb128> and the color move
[12:07] <seb128> it's not nice looking
[12:07] <mvo> the dark?
[12:07] <mvo> its also difficult to read - gray on black in a small font...
[12:07] <chrisccoulson1> seb128 - you need real graphics hardware for plymouth to work properly
[12:08] <chrisccoulson1> i don't even think it would work properly with my NVIDIA card :(
[12:09] <seb128> hum, login doesn't work
[12:09] <seb128> and their language selection is suboptimal too
[12:09] <seb128> brb
[12:13] <seb128> ok, automatic login keeps spinning but doesn't log in
[12:13] <seb128> and you have to select the language and keyboard on the gdm screen and guess the layout variant to use etc
[12:14] <seb128> I like the ubuntu way better ;-)
[12:14] <seb128> any lunch time
[12:14] <seb128> bbl
[12:14] <chrisccoulson1> i've not tried it for a little while
[12:26] <chrisccoulson1> seb128 - the locate pointer issue is an upstream problem. g-s-d will immediately turn the option off again if it fails to spawn gsd-locate-pointer, and this fails because the path is hard-coded as /usr/libexec/gsd-locate-pointer in gsd-mouse-manager.c
[12:27] <chrisccoulson1> (at least that is the case with the 2.28.0 source i have here at work)
[12:27] <chrisccoulson1> anyway lunch time for me too
[12:27] <chrisccoulson1> bbl
[12:48] <seb128> lool, there?
[12:49] <seb128> lool, do you know why unr and stock ubuntu would behave different on wireless?
[12:49] <seb128> using a dell mini 10 config
[13:04] <chrisccoulson> hey seb128 - did you see my earlier comment about the locate_pointer issue before i went for lunch?
[13:04] <seb128> chrisccoulson, yes, good catch thanks
[13:04] <seb128> chrisccoulson, I reassigned the upstream bug
[13:05] <chrisccoulson> thanks, i still can't do that
[13:05] <Laney> chrisccoulson: how goes pidgin?
[13:05] <Laney> pain in the bum isn't it? :)
[13:05] <chrisccoulson> Laney - i'll carry on working on it this evening, but it currently connects successfully to Yahoo and then crashes ;)
[13:06] <seb128> chrisccoulson, did you ask for bug triage rights?
[13:06] <kklimonda> bad yahoo ;)
[13:06] <seb128> pedro_, ^ what is required for chrisccoulson to be able to reassign bugs on gnome.bugzilla.org?
[13:07] <seb128> pedro_, he's doing good work for a while so it should get those ;-)
[13:07] <lool> seb128: No I do not know; they are supposed to be really close in terms of seeds
[13:07] <lool> seb128: If you know which specific package should be present, I can check
[13:07] <seb128> lool, ok, thanks anyway
[13:07] <seb128> lool, no, but I will have a look
[13:08] <lool> The only differences between ubuntu.karmic and unr.karmic live and ship-live seeds are purely langpacks
[13:08] <lool> (Just checked again)
[13:09] <seb128> lool, I didn't try karmic unr yet
[13:09] <lool> Ok
[13:09] <seb128> lool, it's working out of the box on jaunty unr
[13:09] <seb128> but not on jaunty or karmic ubuntu
[13:09] <lool> seb128: jaunty's UNR had weird seeds though
[13:09] <lool> seb128: But it might be that we regressed UNR by syncing things with ubuntu as a reference
[13:09] <pedro_> seb128, I'm already asking for the permissions there
[13:10] <pedro_> chrisccoulson, what's your account on gnome bugzilla?
[13:10] <seb128> pedro_, thanks
[13:10] <lool> seb128: Would be interesting to know which package it is by booting jaunty unr
[13:10] <seb128> pitti, you have bugzilla bug triaging rights?
[13:10] <lool> seb128: Is this on dell mini?
[13:10] <seb128> lool, mini 10
[13:10] <chrisccoulson> pedro_ - my account is<EMAIL_ADDRESS>[13:11] <pedro_> chrisccoulson, thanks
[13:11] <seb128> lool, mini 10v rather
[13:11] <chrisccoulson> pedro_ - thank you too:)
[13:11] <seb128> lool, it was shipped with hardy which worked out of the box and jaunty unr too
[13:13] <lool> seb128: I heard broadcom-wireless needs to be manually installed
[13:14] <lool> seb128: Apparently, it's a complex issue with jockey and APT repos
[13:14] <seb128> lool, hum ok, still it's working on jaunty unr so it should be doable ;-)
[13:14] <lool> seb128: I understand that we would like jockey to try to install it from the ship-live seed (packages in the pool on the images) only, but jockey would have to use lower level calls to APT to achieve this
[13:16] <pedro_> chrisccoulson, you're all set!
[13:16] <seb128> pedro_, good work ;-)
[13:16] <chrisccoulson> pedro_ - thanks!
[13:16] <pedro_> seb128, chrisccoulson my pleasure ;-)
[13:16]  * pedro_ goes back to iso testing
[13:17] <lool> seb128: Eh but I cant check how it worked in jaunty   :)
[13:17] <lool> seb128: I looked it up and couldn't find the broadcom thing in the manifest
[13:17] <seb128> lool, let me try, I still have the unr iso there and an usb key
[13:24] <lool> seb128: Thanks; if it's for your wifi, then we need to check which package ships the driver
[13:24] <lool> seb128: Here, "file /sys/class/net/wlan0/device/driver/module" says /sys/class/net/wlan0/device/driver/module: symbolic link to `../../../../module/iwlagn'
[13:24] <lool> and dpkg -S iwlagn.ko shows where it's from
[13:26] <seb128> lool, ok, key being written I will tell you that in a few minutes
[13:37] <pitti> seb128: how do I tell?
[13:37] <pitti> seb128: I have "status bug reporter" and can assign/close/etc.
[13:37] <seb128> pitti, can you reopen bugs there?
[13:37] <pitti> seb128: yes, I think I can
[13:37] <seb128> ok
[13:37] <seb128> so you just lack git commit
[13:37] <pitti> I did several times AFAIR
[13:37] <pitti> seb128: btw, new i386 desktops up
[13:38] <seb128> ok
[13:41] <seb128> lool, is the jaunty unr manifest online somewhere?
[13:46] <didrocks> jcastro: thanks ;)
[13:47] <seb128> didrocks, what did he do this time? ;-)
[13:48] <lool> seb128: Yes
[13:48] <didrocks> seb128: it was related to UDS room twinning :-)
[13:48] <lool> seb128: http://releases.ubuntu.com/jaunty/
[13:48] <seb128> didrocks, ok
[13:56] <kenvandine> hey rickspencer3
[13:56] <rickspencer3> hi kenvandine
[13:56] <rickspencer3> I just had lunch with a couple of calabora guys
[13:57] <chrisccoulson> seb128 - what do you think about bug 462253? i'm not too sure it's a gvfs issue. i've seen Nautilus fail to show folder contents before when stat() fails on one of the files, and that seems to be what is happening there
[13:57] <chrisccoulson> ?????????? ? ?          ?                 ?                ? VIDEO_TS.BUP
[13:57] <chrisccoulson> i suppose that stat() shouldn't fail in the first place though
[13:58] <seb128> chrisccoulson, I'm not sure to understand the issue yet
[13:58] <seb128> did the submitter reply to my comment?
[13:58]  * seb128 opens the bug now
[13:59] <chrisccoulson> seb128 - he just added a comment there
[13:59] <seb128> right
[13:59] <seb128> ls also has a permission denied issue
[13:59] <seb128> why do you think it's not a gvfs issue?
[13:59] <seb128> gvfs-ls has the same bug
[13:59] <seb128> gvfs-ls has the same bug
[13:59] <seb128> ups
[13:59] <seb128> see previous comment
[13:59] <seb128> see previous comment
[14:00]  * seb128 kicks touchpad
[14:01] <chrisccoulson> he's only posted the output of "ls -l" in the mount directory so far
[14:01] <seb128> no
[14:02] <chrisccoulson> oh yeah, i missed the earlier comment ;)
[14:02] <seb128> chrisccoulson, see 2 comments before the current one
[14:03] <seb128> chrisccoulson, if gvfs-ls has the same I guess it's gvfs or gio at fault there
[14:03] <seb128> chrisccoulson, but I could be wrong, I need to look at the code
[14:03] <chrisccoulson> the permission denied error is just a consequence of this: "?????????? ? ?          ?                 ?                ? VIDEO_TS.BUP", and that is normally because stat() fails on that file (so there is no information about the file)
[14:03] <chrisccoulson> that's normally a lower level issue i think
[14:03] <seb128> it's a bit weird
[14:03] <seb128> right
[14:04] <seb128> corruption?
[14:04] <chrisccoulson> quite possibly
[14:04] <seb128> I'm not sure how a stat can be failing there...
[14:04] <chrisccoulson> perhaps he could run "ls -l" through strace?
[14:04] <seb128> chrisccoulson, can you ask for details on the bug if you know what to ask there?
[14:04] <chrisccoulson> just to see if it is that which fails
[14:04] <seb128> thanks ;-)
[14:04] <chrisccoulson> can do:)
[14:05] <seb128> cool!
[14:16] <seb128> tedg, hey
[14:17] <tedg> Good morning seb128
[14:17] <seb128> tedg, thanks for looking at the crasher, sorry I was not clear when I suggested it was due to the indicator, I meant the dynamic menu changes for fusa detection indeed
[14:18] <seb128> I don't think it's important for a sru but would be nice to fix in lucid!
[14:18] <tedg> seb128: I can't come up with a simple fix.  It's probably the one of the menu items is getting deallocated before being show.  No clue how that could happen.
[14:18] <seb128> can you work on the change you suggested for lucid?
[14:18] <tedg> seb128: Yup.
[14:18] <seb128> thanks
[14:42] <dobey> seb128, pitti, james_w: oh i almost forgot... care to give me some endorsement on https://wiki.ubuntu.com/RodneyDawes/DeveloperApplication ? :)
[14:43] <hggdh> seb128: bug 359658 is ready for SRU to Jaunty
[15:05] <seb128> lool, do you know if there is a way to see what driver is being used for eth<n>?
[15:06] <lool> seb128: 14:24 < lool> seb128: Thanks; if it's for your wifi, then we need to check  which package ships the driver
[15:06] <lool> 14:24 < lool> seb128: Here, "file /sys/class/net/wlan0/device/driver/module"  says /sys/class/net/wlan0/device/driver/module: symbolic link to  `../../../../module/iwlagn'
[15:06] <lool> seb128: replace wlan0 with eth0 and look at the end of the output
[15:07] <pitti> dobey: will do; what do you apply for? upload rights for the ubuntuone-* packages?
[15:08] <dobey> pitti: universe-contributor, and then will apply for ~ubuntu-desktop after I am accepted for universe-contributor, as you suggested
[15:08] <seb128> lool, it's "wl"
[15:08] <seb128> works on jaunty unr, not on karmic unr
[15:09] <pitti> dobey: I didn't sponsor too many packages from you yet, so I can't vouch for general motu/~u-desktop yet (not sure how many other packages you touched); you could also start with getting single package upload rights (which requires much less packaging experience)
[15:09] <pitti> dobey: the sum of my, james_w, seb128's and other sponsors experience might be enough, of course; not sure how many other folks sponsor your uploads
[15:10] <dobey> was mostly seb128 and james_w
[15:10] <pitti> dobey: so, I'll add my blurb there soon
[15:10] <dobey> and i think scottk sponsored a backport request
[15:10] <dobey> pitti: thanks
[15:13] <seb128> dobey, I can't really vouch for you either, I've not sponsored complicated changes from you
[15:13] <seb128> those I did upload were mainly new version updates
[15:13] <seb128> not new packages or binary splits or transitions
[15:14] <james_w> agreed, but I'm happy to speak about the value of your contributions, which is what universe-contributor is about
[15:15] <pitti> ^ *nod*
[15:15] <seb128> +1
[15:15] <pitti> package uploader is also fine from my POV
[15:15] <seb128> asac, around today?
[15:15] <dobey> i don't know, i'm just going on what you guys suggested :)
[15:16] <asac> seb128: yes ... just around the corner ;)
[15:16] <seb128> asac, do you know if bcm4315 cards are supposed to work out of the box in ubuntu?
[15:17] <seb128> asac, my mini 10v wireless works only in jaunty unr
[15:17] <seb128> karmic unr or jaunty or karmic ubuntu doesn't see eth1
[15:17] <asac> seb128: well. usually yes, but its a proprietary driver and as such is flaky
[15:17] <asac> seb128: do you have "wl" driver loaded?
[15:17] <seb128> on jaunty unr yes
[15:17] <asac> i think that driver moved somewhere else ...
[15:17] <superm1> use jockey to enable it on karmic
[15:17] <asac> afaik its supposed to get detected by jockey
[15:18] <seb128> it's not listed in jockey
[15:18] <superm1> make sure your apt cache is up to date first
[15:18] <asac> but a few weeks ago there was an issue, but i didnt follow what came out of it after i connected the user with pitti
[15:18] <superm1> and then it should be offered in jockey
[15:18] <seb128> apt-cache search doesn't list bcmwl-kernel-source
[15:18] <seb128> how do I update my cache without internet?
[15:18] <superm1> you don't.  Keybuk_ was talking about this last week in #ubuntu-devel
[15:19] <seb128> which means karmic is useless on my mini 10v, great
[15:19] <asac> hmm. odd. i thought that we put that in restricted and as that the driver pieces are on CD
[15:19] <asac> isnt that the case?
[15:19] <dobey> seb128: boot the jaunty kernel under karmic?
[15:19] <superm1> the driver is on the CD, so you can install it from the CD still
[15:19] <asac> superm1: why doesnt jockey do that?`
[15:19] <asac> isnt that the idea?
[15:20] <asac> or just a bug that is known?
[15:20] <pitti> asac: no, we can't fit the entire tool chain on CDs
[15:20] <pitti> seb128: connect it to ethernet, apt-get update, and use jockey
[15:20] <superm1> pitti, actually yes everything needed to install bcmwl is on the CD http://cdimages.ubuntu.com/daily-live/current/karmic-desktop-i386.list
[15:20] <asac> oh
[15:20] <asac> right
[15:20] <pitti> superm1: oh, I see; right, we discussed that a while ago
[15:20] <Keybuk_> everything needed is on the CD
[15:21] <pitti> the CD isn't added as a repository
[15:21] <Keybuk_> *but* you have to do it by hand using dpkg
[15:21] <superm1> and it's properly offered when you boot in live mode.  the problem is the cd not being a valid repository post install
[15:21] <superm1> yes^
[15:21] <Keybuk_> pitti: and even if it was, the on-the-net repos fail to update, so apt refuses to work anyway
[15:21] <seb128> do we have an open bug about that?
[15:22] <pitti> I'm sure we have plenty
[15:22] <seb128> I'm not sure to get the issue
[15:22] <seb128> why could it work in jaunty unr but not in ubuntu?
[15:22] <Keybuk_> no idea
[15:22] <pitti> but it's not really trivial to solve
[15:22] <Keybuk_> jaunty unr was probably "special"
[15:22] <pitti> seb128: because in jaunty we still had l-r-m
[15:22] <superm1> it was shipped in linux-restricted-modules in jaunty
[15:22] <pitti> whic shipped wl
[15:22] <pitti> but l-r-m is gone
[15:22] <superm1> so everyone "had it" by default then
[15:23] <seb128> why did we drop it? that seems useful to have there
[15:23] <Keybuk> because it was evil
[15:23] <pitti> kernel team decided to drop l-r-m entirely, not just wl
[15:23] <Keybuk> it's been replaced by dkms
[15:24] <seb128> it has been replacing by something which doesn't work ;-)
[15:24] <pitti> seb128: do you see the b43 driver in jockey? (for downloading the firmware)
[15:24] <pitti> seb128: it does work
[15:24] <seb128> no, jockey is empty
[15:24] <superm1> b43 doesn't work with 4315 anyway
[15:24] <pitti> seb128: it's not the fault of dkms, it's a matter of having the package available/installed or not
[15:25] <pitti> superm1: ok, then jockey wouldn't show it
[15:25] <Keybuk> seb128: you mean like pidgin was replaced by empathy?
[15:25] <davmor2> sta is working here now both in live and installed
[15:25] <pitti> seb128: if only we would know someone at dell who could pester the broadcom guys to do proper drivers :)
[15:25] <seb128> pitti, ;-)
[15:26] <seb128> still not fun that jaunty was working on the mini 10v and karmic is not
[15:26] <pitti> intel wifi FTW
[15:26] <superm1> pitti, are you going to move jockey to apt daemon during lucid?  that should likely allow providing feedback more easily, and possibly enabling the CD repository on demand
[15:26] <pitti> superm1: trunk uses packagekit
[15:26] <Keybuk> pitti: if only we knew someone at dell who we could pester to stop building hardware which relies on non-free drivers
[15:27] <pitti> superm1: but it's not really an issue of aptdaemon vs. python-apt
[15:27] <superm1> haha
[15:27] <seb128> Keybuk, let's not troll empathy vs pidgin, empathy is supposed to do the same work ;-)
[15:27] <pitti> superm1: we could jump through some hoops to have jockey temporarily use the CD repository, install from that, drop it again, and ignore the http sources
[15:27] <pitti> and build a lot of new UI around it to cope
[15:28] <superm1> pitti, can you set up a session at UDS to try to discuss solutions to this type of problem then in case there are some better ideas?
[15:28] <Keybuk> seb128: so is dkms
[15:28] <lool> seb128: dpkg -S wl.ko?
[15:28] <seb128> superm1, how do I install bcmwl?
[15:29] <seb128> lool, it's in the volatile directory and not shipped by any deb according to dpkg
[15:29] <seb128> lool, but it was in l-r-m apparently
[15:29] <superm1> seb128, on karmic, just add the cdrom/usb stick in software-properties-gtk and you should be able to use apt-get to do it
[15:29] <seb128> superm1, thanks
[15:30] <Keybuk> if that fails
[15:30] <Keybuk> dpkg -i /media/blah-blah/pool/*/*/*.deb ;-)
[15:32] <seb128> it seems suboptimal to have the deb there and not installed
[15:32] <seb128> can't we just auto install those?
[15:34] <pitti> well, we don't want to install the nvidia/fglrx/wl drivers everywhere
[15:34] <pitti> superm1: I suppose you'll install it by default on the pre-installed boxes you sell?
[15:40] <lool> seb128: It seems that lrm was replaced by DKMS based individual debs so you probably hit this jockey/APT issue due to lrm being replaced by individual packages
[15:40] <lool> seb128: Sorry   :-/
[15:40] <lool> seb128: We need to fix this jockey/apt interaction
[15:40] <seb128> lool, yes, what we were just discussing
[15:40] <seb128> I don't get why jockey doesn't list it after install though
[15:40] <seb128> the list is empty
[15:41] <seb128> do you know if there is a bug about that?
[15:42] <james_w> pitti: apport gets turned off at release? In what way is it turned off?
[15:42] <lool> seb128: Dunno
[15:42] <lool> seb128: Scott seems to know about these gotchas with mini 10v
[15:42] <pitti> james_w: it did; /etc/default/apport says enabled=0 now
[15:43] <james_w> pitti: and what effect does that have?
[15:43] <james_w> I'm wondering if that will have effectively turned off kerneloops as well
[15:43] <pitti> james_w: segfaults and python crashes don't cause .crash files to be written any more
[15:43] <pitti> james_w: I'm not sure actually
[15:43] <pitti> james_w: but do we even install that by default? I don't have it here, and it's a fresh install from yesterday evening
[15:43] <Keybuk> seb128: no, because that would be AGAINST THE LAW
[15:44] <james_w> pitti: we should
[15:44] <james_w> kerneloops-daemon at least
[15:44] <pitti> james_w: oops, I do have that, yes
[15:44] <james_w> which causes .crash files to be written
[15:44] <james_w> should we have disabled that as well?
[15:44] <pitti> kernoops  1503  0.0  0.0  20064   264 ?        Ss   Oct27   0:02 /usr/sbin/kerneloops
[15:44] <pitti> meh
[15:44] <lool> Mé?
[15:44] <pitti> james_w: well, not sure about the kerneloops.org submission, but I think we should disable that, too
[15:45] <seb128> Keybuk, I should talk to those who recommended the mini 10v as a netbook working out of the box on ubuntu ;-)
[15:45] <james_w> pitti: ok, I'll prepare an SRU to disable kerneloops from starting?
[15:46] <pitti> james_w: it might provoke some "ubuntu talks home" concern, so that might be better indeed
[15:46] <pitti> james_w: it doesn't seem to have a default file unfortunately
[15:47] <james_w> hmm, yeah
[15:47] <james_w> it only talks home if they accept
[15:47] <superm1> pitti, for karmic i've actually got a method that runs jockey post install to evaluate what's necessary
[15:48] <superm1> pitti, but basically if it's determined that something can use the driver, it will get loaded
[15:50] <superm1> so maybe the right solution is to roll this into a ubiquity plugin for lucid?
[15:50] <lool> What's starting up language-selector on login?
[15:53] <mvo> language-selector is started?
[15:53] <mvo> not just a notification about that?
[15:54] <pitti> james_w: ah, right; so the "talk home" is not a big deal, it's just having it in the first place then?
[15:54] <james_w> yeah
[15:54] <james_w> just the same issues we don't run apport in stable releases I guess
[15:54] <james_w> and the fact that it is still a bit sucky and so will give you lots of duplicate reports and things
[16:02] <seb128> pitti, is jockey hanging for 1 minute after clicking active normal?
[16:03] <seb128> it did open a "download and install" dialog now but the bar doesn't move
[16:03] <pitti> not really, it should give you a progress dialog
[16:03] <pitti> but apt is very poor with giving progress
[16:03] <seb128> it's all pretty slow for something which is on a local usb stick
[16:03] <pitti> so if building/installing takes a while, it will appear stuck
[16:03] <seb128> it's like 2 minutes now
[16:03] <seb128> oh, it builds, ok
[16:03] <seb128> ssd drive = no noise
[16:03] <pitti> hm, I tested the wl stuff some days ago, and it hung for 10 seconds or so
[16:03] <seb128> so it seems to do nothing
[16:04] <pitti> but not more
[16:04] <seb128> it's a good 3 minutes now
[16:04] <seb128> I did enable the b43 option
[16:04] <mvo> pitti: what exactly is the problem with apt? is it the dpkg database reading that takes so long?
[16:05] <pitti> mvo: no, progress information through package install; it's like 0 - 40% - 100%
[16:05] <pitti> seb128: ah, it's not STA?
[16:05] <seb128> well it's listing both
[16:05] <pitti> seb128: I thought b43 wouldn't even be displayed?
[16:05] <seb128> I decided to active the first one first to try
[16:05] <mvo> yeah, for a single package that is correct, thats the best we get from dpkg
[16:05] <pitti> seb128: for b43 it downloads and installs b43-fwcutter, and that then downloads the firmware
[16:06] <seb128> over 5 minutes now
[16:06] <mvo> but a single package should usually much faster than 1-2 minutes?
[16:06] <superm1> b43 loads on 4315, but will just display something in dmesg about how it can't do anything
[16:06] <seb128> I'm wondering if it's still working
[16:08] <pitti> seb128: do you have a running apt/dpkg process?
[16:08] <pitti> and a b43-fwcutter one?
[16:08] <seb128> pitti, .xsessions-error has a raise BackendCrashError
[16:09] <seb128> let me look
[16:09] <seb128> pitti, no
[16:09] <pitti> hm, then it crashed
[16:09] <pitti> seb128: do you have an exception in /var/log/jockey.log ?
[16:10] <seb128> no
[16:10] <seb128> DEBUG: Installing package: b43-fwcutter
[16:10] <seb128> and nothing after that one
[16:14] <seb128> pitti, https://bugs.edge.launchpad.net/ubuntu/+source/jockey/+bug/413624
[16:14] <seb128> pitti, http://launchpadlibrarian.net/30315756/Traceback.txt
[16:14] <seb128> I get the same stacktrace in .xsession-errors
[16:15] <pitti> seb128: hm, unfortunately that's an useless stack trace
[16:15] <seb128> ok
[16:15] <seb128> do you need anything before I close jockey and try to install sta?
[16:16]  * pitti comments on the bug
[16:17] <pitti> seb128: no, the frontend is pretty independent, you can close it
[16:18] <seb128> ok thanks
[16:18] <pitti> added debug instructions
[16:24] <seb128> pitti, the backend side is flooding very quickly with "result coult not be parsed"
[16:29] <pitti> oh, I wonder where that comes from
[16:30] <seb128> it's looping on that and never stops
[16:41] <seb128> hum, another case where empathy fails to connect to msn but pidgin works correctly
[16:43] <chrisccoulson> heh, i've just had an old colleague e-mail me, and commenting that karmic is looking nice:)
[16:45] <seb128> chrisccoulson, good ;-)
[17:13] <seb128> pitti, want me to try something else before I wipe this install?
[17:13] <seb128> pitti, I get the bug every time but I'm going to put unr
[17:14] <pitti> seb128: do you see anything helpful in the log which would show what prints those "result could not be parsed" messages?
[17:14] <seb128> no
[17:14] <seb128> the line before is Installing...
[17:14] <pitti> seb128: go ahead; with the same hardware and network the bug should occur under UNR, too
[17:14] <seb128> then it loops on that one
[17:15] <seb128> I've no clue about jockey and what it tries to parse though
[17:17] <Laney> omg
[17:17] <Laney> can I disable U1 notifications?
[17:21] <seb128> pitti, the "result could not be parsed" is a string in apt_pkg.so
[17:21] <seb128> pitti, the "result could not be parsed" is a string in apt_pkg.so, not sure it's coming from there though...
[17:21] <chrisccoulson> pitti - do you think bug 457123 is SRU-able?
[17:21] <pitti> it uses python-apt
[17:21] <pitti> seb128: ^
[17:22] <seb128> pitti, note that this box has no internet so has not been able to do an apt-get update
[17:22] <pitti> ah
[17:22] <seb128> ie the apt indexes might not be in a right state
[17:22] <pitti> seb128: you will need internet to download the firmware
[17:22] <seb128> I just added the usb key as a cdrom to use jockey
[17:22] <seb128> hum
[17:23] <seb128> it's a chicken egg issue ;-)
[17:23] <seb128> I need internet to download the firwmware to get internet
[17:23] <seb128> ok, you win, I'm using wired internet to get that one
[17:27] <pitti> ethernet for the win :)
[17:28] <pitti> and bad drivers FTL
[17:36] <mvo> seb128: hm, that message seems to come from a media change events, I suspect that jockey does not implement media change?
[17:36] <pitti> mvo: it doesn't
[17:36] <pitti> mvo: it's a noninteractive d-bus backend
[17:36] <mvo> ok, that explains it (also the message is really not helpful
[17:37] <mvo> so it seems the deb is on the cd but that prevents it from becoming installed
[17:38] <mvo> lucid material
[17:38] <seb128> pitti, mvo: confirmed it works after disabling the cdrom source
[17:39] <mvo> hm, thinking about it, if it could just return False to media change events it should fallback to http
[17:39] <seb128> cdrom being wrong wording in the apt source config dialog since that's an usb key
[17:39] <seb128> software-source I mean
[17:39]  * mvo will add code to python-apt that assumes that
[17:40] <seb128> great the box crashed after the driver install
[17:40] <seb128> mvo, pitti: you guys want a bug about the apt-cdrom thingy?
[17:41] <pitti> seb128: please
[17:41] <mvo> seb128: if you can still reproduce it, can I send you a test patch?
[17:41] <seb128> pitti, where? python-apt? jockey
[17:41] <pitti> seb128: both probably
[17:41] <pitti> (two tasks)
[17:41] <seb128> mvo, it easy to trigger yes
[17:41] <seb128> install karmic on a mini 10v
[17:42] <seb128> enable the usb key as cdrom source
[17:42] <seb128> and try to enable the wireless network in jockey
[17:42] <seb128> ie I can test it for you
[17:45] <mvo> seb128: could you please try this patch?
[17:45] <mvo> http://paste.ubuntu.com/303708/
[17:47] <mvo> seb128: just to see if it helps, the real fix needs to go into python-apt
[17:49] <seb128> mvo, trying
[17:49] <seb128> mvo, pitti: bug #462771
[17:50] <pitti> seb128: merci
[17:52] <pitti> mvo: hm, does p-apt magically callback the invoker of a function?
[17:53] <pitti> mvo: your patch merely adds a new method to the OSLib class, but doesn't use it anywhere?
[17:53] <mvo> pitti: its a callback that the progress code calls
[17:54] <mvo> pitti: the bug is in python-apts default implementaiton, but this was the quiest way for a test-run
[17:54] <seb128> mvo, sorry it's going to take another 5 minutes, the box crashed again
[17:54] <seb128> it doesn't like those drivers installs
[18:01] <seb128> pitti, is there a cache dir in jockey?
[18:01] <seb128> it seems to find the driver without internet since I downloaded it
[18:01] <seb128> cleaning the apt cache is not enough
[18:01] <pitti> seb128: /var/cache/jockey/ caches which drivers it already presented to you through notifications, but not much else
[18:02] <seb128> pitti, or, no downloaded firmware?
[18:02] <seb128> or driver
[18:02] <seb128> or whatever it got online
[18:02] <pitti> seb128: firmware> /lib/firmware/b43
[18:02] <pitti> and b43-fwcutter / bcmwl-kernel-source packages
[18:02] <pitti> those all belogn to the driver packages, though
[18:02] <pitti> seb128: if you delete /lib/firmware/b43, then it should appear disabled again
[18:03] <seb128> it's disabled
[18:03] <seb128> but when I enable it again it seems to manage to do that without having to download
[18:04] <seb128> ok, will be faster to just redo a test install
[18:04] <seb128> mvo, I will ping you back about the change after dinner
[18:05] <seb128> will make me test the current i386 iso too
[18:05] <mvo> seb128: have you removed /var/cache/apt/archives/* ?
[18:06] <seb128> mvo, I did sudo apt-get clean
[18:06] <seb128> which should be equivalent no?
[18:06] <mvo> hm, that should be sufficient
[18:06] <pitti> seb128: are you trying b43 or wl?
[18:06] <seb128> pitti, both
[18:06] <seb128> anyway new install running
[18:06] <seb128> it's an usb2 key and a ssd disk
[18:06] <seb128> it's going to be quick
[18:06] <pitti> seb128: the latter is bcmwl-kernel-source (purge), the former is /lib/firmware/b43/ and b43-fwcutter
[18:06] <mvo> seb128: ok, I will have to leave sonish for today, but if you could let me know I will prepare a sru for python-apt with a more sane default
[18:07] <seb128> mvo, ok, no hurry anyway, I will let you know tomorrow morning
[18:07] <mvo> thanks
[18:07] <seb128> pitti, I did dpkg -r bcmwl-kernel-source
[18:07] <seb128> maybe I should have purged rather
[18:07] <seb128> anyway, reinstalling now
[18:07] <pitti> seb128: ah, no, you need to remove it from the apt cache, too
[18:07] <pitti> seb128: /var/cache/apt/archives/bcmwl-kernel-source*.deb
[18:07] <seb128> did that too
[18:07] <seb128> sudo apt-get clean
[18:07] <pitti> or apt-get clean
[18:08] <pitti> then it needs to redownload the .deb
[18:23] <tgpraveen> what does SRU mean?
[18:23] <tgpraveen> !SRU
[18:24] <tgpraveen> forund it!
[18:35] <tgpraveen> seb128: will https://bugs.launchpad.net/ubuntu/+source/enchant/+bug/446230 be getting an SRU? should I file for that separately?
[18:35] <seb128> tgpraveen, no and no
[18:36] <tgpraveen> ok
[18:37] <seb128> mvo, the change doesn't seem to make a difference
[19:15] <chrisccoulson> vuntz - i'm just trying to investigate why my screensaver doesn't come on sometimes, and i've just noticed that if an application registers an inhibitor with gnome-session, but then crashes before releasing it, the inhibitor object remains (preventing the screensaver activating automatically again for the remainder of the session)
[19:15] <chrisccoulson> this could be more robust couldn't it?
[19:27] <chrisccoulson> hmmmm, i see it's meant to remove the inhibitors already, but that doesn't seem to be working :-/
[19:34] <vuntz> chrisccoulson: hrm, that's bad, indeed
[19:34] <chrisccoulson> yeah, i'm just trying to work out whats going on
[19:37] <tjaalton> should karmic have g-v-m installed?
[19:37] <chrisccoulson> tjaalton - no it shouldn't
[19:37] <chrisccoulson> g-v-m should disappear from the archive
[19:37] <tjaalton> chrisccoulson: nice
[19:38] <tjaalton> a bit late to fix now, but maybe it should be cleaned from the system on dist-upgrade
[19:39] <chrisccoulson> the only release with it installed by default currently is hardy. so it should probably be cleaned on hardy -> lucid upgrades
[19:39] <tjaalton> hmmh, too bad it has been on my system for way too long then ;)
[19:40] <tjaalton> I was wondering why I always got a gvm popup asking what to do with media containing pictures
[19:40] <tjaalton> the settings didn't persist
[19:40] <tjaalton> so it's just that gvm was running
[19:41] <tjaalton> I wonder what else is running that shouldn't :)
[19:45] <chrisccoulson> vuntz - this is wierd. i've just ran gnome-session through GDB, and set a break on inhibitor_has_bus_name. when i kill totem, i see this function called for every inhibitor, but when i inspect inhibitor->priv->bus_name, every inhibitor has the same bus name (and it's wrong)
[19:45] <chrisccoulson> which is why they don't get removed
[19:47] <chrisccoulson> ah
[19:47] <chrisccoulson> totem still proxies requests through gnome-screensaver, and the bus name is the bus name of gnome-screensaver
[19:47] <chrisccoulson> that's why it doesn't work
[19:47] <chrisccoulson> gggargh
[19:48] <chrisccoulson> totem needs to use the new interface :(
[19:48] <tjaalton> nautilus Breaks: gnome-volume-manager (<< 2.24), but the version in the archive is later, so no wonder it's not cleaned away
[19:48] <tjaalton> gvm that is
[19:48] <chrisccoulson> i'm not sure the Breaks is there for cleaning on upgrade. i don't know if breaks is appropriate for that really
[19:49] <tjaalton> well, it provides the same functionality
[19:49] <tjaalton> resulting in bad user experience
[19:49] <tjaalton> maybe conflicts then
[19:49] <chrisccoulson> yeah, it does. i was hoping to get it removed from the arhive this cycle, but ended up running out of time
[19:50] <chrisccoulson> **yeah, it does provide a bad use experience
[19:50] <tjaalton> maybe the conflict could be added as an update?
[19:50] <seb128> re
[19:50] <chrisccoulson> hello seb128
[19:50] <seb128> chrisccoulson, hey, what totem issue do you investigate?
[19:50] <seb128> tjaalton, what is the issue?
[19:51] <chrisccoulson> seb128 - session inhibiting ;)
[19:51] <seb128> what sort of issue does it lead to?
[19:51] <tjaalton> seb128: g-v-m should be cleaned on upgrade
[19:51] <chrisccoulson> inhibitors are leaked if totem crashes, or exits without removing them first. which means that the screensaver doesn't automatically lock the screen for the rest of the session once this has happened
[19:52] <tjaalton> seb128: so nautilus should conflict with it
[19:52] <seb128> tjaalton, the change was before hardy not likely to be a real issue now
[19:53] <tjaalton> unless you've been dist-upgrading from a release to another, like me
[19:53] <seb128> tjaalton, especially that update-manager will clean it on upgrade
[19:53] <seb128> tjaalton, you didn't use update-manager?
[19:53] <tjaalton> hasn't done it here
[19:53] <tjaalton> I've used it, but always upgraded to alpha2/3 or so
[19:53] <seb128> DistUpgrade/demoted.cfg.hardy:gnome-volume-manager
[19:54] <seb128> it might have been added later in the cycle than that
[19:54] <tjaalton> ok, good
[19:54] <seb128> we don't do dist-upgrade tweaks to earlier usually
[19:54] <seb128> to -> so
[19:54] <seb128> or too early
[19:54] <seb128> anyway it should not be an issue for many users
[19:55] <seb128> it was 1.5 year ago and the dist-upgrade will clean it
[19:55] <tjaalton> hope so :)=
[19:56] <tjaalton> maybe the cleanup app and update-manager should share such configs
[19:57] <seb128> it's not listed in computer-janitor?
[19:57] <tjaalton> let me install it again and test..
[19:58] <tjaalton> nope
[19:58] <seb128> ok, that's probably a bug then
[19:59] <tjaalton> ok, I'll file it
[20:17] <mvo> seb128: hey - do you get the same message with the patch as before? or a different one/no message but the same behavior ?
[20:18] <seb128> mvo, same message
[20:18] <seb128> but I might have edited the wrong file I'm not sure what is correct with the python modern world
[20:19] <mvo> seb128: hm, maybe or I did a typo or something - it should be in /usr/lib/python2.6/dist-package should have the symlink
[20:19] <mvo> seb128: could you add a "print "hello" or something into the mediaChange()
[20:19] <mvo> just to see if its called at all?
[20:19] <seb128> ok
[20:20] <mvo> or open("/tmp/seb","w").write("hello")
[20:20] <mvo> to be sure its not eaten by some redirection
[20:20] <seb128> gpm is on crack after install in karmic
[20:20] <seb128> 11 hours of battery remaining, right
[20:21] <kenvandine> seb128, i want your batter :)
[20:22] <kenvandine> battery
[20:22] <seb128> it's going to be quite expensive but I'm wanting to sell it for a good price ... ;-)
[20:23] <tgpraveen> !info empathy
[20:23] <seb128> tgpraveen, ?
[20:24] <seb128> mvo, seems to not be called
[20:24] <tgpraveen> seb128: sorry wrong channel
[20:27] <mvo> seb128: meh, my mistake I think, give me a sec
[20:28] <mvo> seb128: please try http://paste.ubuntu.com/303822/
[20:28] <mvo> seb128: no need to unpatch the previous one, should do no harm
[20:28] <mvo> (but also no good)
[20:30] <seb128> mvo, that one works
[20:32] <mvo> seb128: cool, now it fetches from the net?
[20:32] <seb128> mvo, it tries to fetch from the key which is not there
[20:32] <seb128> I'm going to try with the key in a few minutes when it's available
[20:32] <seb128> using it on another box right now
[20:33] <seb128> ie it displays "failed to fetch cdrom:...."
[20:33] <seb128> with a file not found error
[20:34] <seb128> mvo, did I already told you that you rock today? ;-)
[20:34]  * seb128 hugs mvo
[20:34] <mvo> seb128: no, but I'm happy to hear that :)
[20:35] <mvo> just to confirm, you get a file-not-found and then it gets it from the http source?
[20:35] <seb128> no, just the not found but I don't have http sources
[20:36] <seb128> I'm trying to enable the wireless driver to get online
[20:36] <seb128> so I never apt-get updated it
[20:36] <mvo> aha, ok
[20:36] <mvo> thanks for the super-quick test!
[20:36] <seb128> you're welcome
[20:44] <seb128> mvo, it seems to file to fetch the file from the usb key still
[20:44] <seb128> but at least it doesn't hang
[20:47] <mvo> yeah, well - in order for that the mediaChange() method needs to get actually implemented
[20:47] <mvo> and not just return "FAIL" :)
[20:48] <seb128> ok so it's all good
[20:48] <mvo> yeah, that was the scope of the fix for today
[20:48] <seb128> do you want me to try on wired internet too?
[20:48] <seb128> should cd be used before http in such cases?
[20:48] <mvo> if its no hassle
[20:48] <mvo> yes
[20:48] <mvo> but apt usually adds the CD to the top of the sources.list
[20:56] <seb128> mvo, ok, works
[20:56] <seb128> mvo, I used wired ethernet to apt-get update
[20:56] <seb128> tried without your change it hanged and printed the lines
[20:56] <seb128> with your change it download over http as expected
[21:07] <mvo> seb128: thanks
[21:07] <seb128> mvo, thank you for looking at the issue ;-)
[21:10] <mvo> seb128: do you think its sru worthy?
[21:10] <seb128> mvo, no
[21:11] <seb128> or depends of the number of duplicate bugs on jockey
[21:11]  * mvo nods
[21:11] <seb128> I'm not sure how many users enable cdrom sources
[21:11] <seb128> but I would tend to say not many
[21:14] <mvo> ok
[21:16] <bigon> will somebody make a package for empathy <IP_ADDRESS> ?
[21:16]  * Laney is annoyed by how many notifications U1 is showing
[21:16] <Laney> bigon: what's new there?
[21:16] <seb128> bigon, already done and uploaded a sru candidate
[21:16] <seb128> as sru candidate
[21:17] <bigon> seb128: ok great
[21:18] <seb128> bigon, you can look to open bugs btw to see if somebody work on updates, we need to have bugs to track sru updates
[21:53] <pitti> seb128: out of interest, how long does an ubiquity run take on your netbook? (usb->ssd)
[21:53] <seb128> pitti, I didn't measure but less than 10 minutes I think
[21:53] <seb128> some 6 to 8 minutes
[21:53] <pitti> wow
[21:54] <seb128> I got a high speed usb key recently that's nice
[21:54] <seb128> like copying a cd iso to the key is some 1 minute
[21:55] <seb128> hey robert_ancell
[21:55] <robert_ancell> seb128, hey
[21:55] <seb128> robert_ancell, how are you?
[21:55] <seb128> been busy doing iso testing?
[21:56] <seb128> how is karmic looking in your opinion?
[21:56] <robert_ancell> seb128, is it out already?
[21:56] <seb128> no
[21:56] <seb128> tomorrow
[21:56] <pitti> hey robert_ancell
[21:56] <robert_ancell> pitti, hey
[21:56] <seb128> but current isos should be the karmic set
[21:56]  * pitti knocks on wood
[21:56] <robert_ancell> seb128, I've just been running my up-to-date install.  Nothing is broken that I use or have tried to use
[21:57] <robert_ancell> I'll set up a VM today
[21:57] <pitti> robert_ancell: do you have hardware VM support?
[21:57] <seb128> robert_ancell, I've assigned some bugs to you, let me know if you already have too much to do though
[21:57] <robert_ancell> pitti, no, just a standard old laptop
[21:57] <seb128> robert_ancell, do you want to do the totem 2.28.2 update as a sru too btw?
[21:58] <robert_ancell> seb128, np
[21:58] <seb128> robert_ancell, I expect that we will spend the next week mainly looking at karmic feedback and doing some srus
[21:59] <seb128> then start on merges with debian for lucid and some updates
[21:59] <robert_ancell> seb128, sure.  I was doing some triaging yesterday.  There are so many vague "my hardware doesn't work" bugs
[21:59] <seb128> then prepare uds
[21:59] <seb128> robert_ancell, right, I do read all desktop bugs, takes me like 2 hours a day
[21:59] <seb128> I want a "I don't care about this issue" button
[22:00] <seb128> just to put all those noise bugs out of the way
[22:00] <robert_ancell> seb128, yes - there's a class of bugs that basically can't be fixed or would take so much time to fix they'd be obsolete by the time you found the problem
[22:01] <seb128> I just go by numbers, we can't spent a day one a weird local issue
[22:01]  * TheMuso waves.
[22:01] <robert_ancell> TheMuso, hi
[22:01] <seb128> hey TheMuso
[22:01] <seb128> robert_ancell, karmic looks good from feedback in any case
[22:02] <seb128> the most frequent complain is youtube videos playing not working in totem I think
[22:02] <seb128> with gdm lack of options
[22:02] <seb128> also some inhibitor issues chrisccoulson seems to be looking at now
[22:02] <robert_ancell> seb128, oh they love to bitch about gdm... there's nothing you can say to quieten the masses
[22:10] <pitti> bryce__: http://www2.bryceharrington.org:8080/files/images/dutch-pirate.jpg -> this is awesome
[22:11] <bryce__> pitti, :-)
[23:05] <robert_ancell> pitti, what makes you think the seahorse-plugin may be related to icons?
[23:06] <pitti> robert_ancell: the third-last or so stack frame
[23:06] <pitti> (from the bottom of the file)
[23:07] <robert_ancell> pitti, ah, haven't seen a trace like this
[23:15] <pitti> good night everyone
[23:19] <DGMurdockIII> whats that tool that in ubuntu that run a system test then send the info back to the ubuntu dev
[23:21] <chrisccoulson> checkbox?
[23:21] <chrisccoulson> 'night pitti
[23:24] <DGMurdockIII> used to be somthing else