/srv/irclogs.ubuntu.com/2013/06/19/#ubuntu-desktop.txt

=== RAOF_ is now known as RAOF
=== 92AAAUIMO is now known as RAOF
pittiGood morning04:57
Tm_Tsv/aelyu sv05:01
pittiTm_T: I hope it was your cat and not your password :)05:19
Tm_Tpitti: heh, I managed to post something? I had two irssis running on top of each other, I simply tried to close this nicely but ended up killing the processes05:20
Tm_TI wonder how that whole mess even happened05:21
sil2100Morning! Damn, I overslept, went to sleep too late07:45
didrockssil2100: hey, how are you?07:45
didrocks(apart from this oversleeping ;))07:46
seb128good morning desktopers07:46
seb128hey didrocks, sil210007:46
didrockssalut seb128!07:46
sil2100didrocks: hi! After python-qt4 got finally published, I had to re-run indicators twice - since for the first time we had some failures on one machine07:46
sil2100didrocks: I wonder how it looks now07:46
didrockssil2100: but it didn't publish?07:46
didrockssil2100: from what I see, not really good07:47
didrockssil2100: I propose that we unblock that with a hangout if you don't mind07:47
didrocks(after your coffee)07:47
sil2100Well, yesterday it failed 4 tests on one machine, I re-run it but didn't see the results, hope it all looks ok - I also ran unity with whole-ppa enabled, but I'll look at the stacks in a moment and know what's up07:50
didrockssil2100: shouldn't we have this hangout? all the stacks tests fail and I prefer that we debug together07:51
didrocks(you can see in 2 minutes that all the stacks failed btw :p)07:51
sil2100Need VPN to work with a cherry on top pleaase07:54
sil2100:D07:54
didrocksheh, is it failing for you?07:54
didrocks(and can you please answer by yes or no on the hangout question? :p)07:54
sil2100Ok, ready07:58
sil2100Let's hang out07:58
sil2100didrocks: hm, why are those tests failing now I wonder? Yesterday at night they actually ran with the new python-qt08:00
sil2100didrocks: this is the first run I made: 10.97.0.1:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-2.2check/196/08:01
sil2100The second one was the same, but hm, strangly also the same number of failures08:01
sil2100And now suddenly the sip problem again08:02
didrockssil2100: https://plus.google.com/hangouts/_/2175b6828a78257a1bc2f4243a84d6bb5ad5c333 in case you didn't receive the notification :)08:02
Laneyg'morning08:03
seb128Laney, hey, how are you?08:04
Laneypretty good thanks08:04
Laneyyou08:05
Laney?08:05
mlankhorstmorning!08:05
mlankhorstLaney: I learned that I shouldn't try to overtake, or even try to tail, bikers who wear special glasses..08:06
Laneyspecial glasses?!?!?!?!08:06
seb128Laney, I'm good thanks, enjoying the not-so-warm-yet temperature of the morning08:06
Laneyhah, I remember now - today was supposed to be storm day08:06
mlankhorstbiker glasses or something, those that don't allow air to pass to the eyes08:07
Laneyoh yes08:07
mlankhorsthttp://www.bikester.nl/344505.html things like those08:07
Laneytoo fast? :P08:07
mlankhorstdefinitely!08:07
LaneyI should get some bike shorts08:10
sil2100didrocks: hmmm, it seems the Apps tests for ati are having some problems09:01
didrockssil2100: have you poked upstream? they should help fixing those :)09:01
sil2100didrocks: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/170/label=autopilot-ati/console09:01
sil2100Hard to say what's up, since it looks a bit hanged ;p09:02
sil2100It doesn't want to finish!09:02
didrocksjibel: hey, do you have time to have a look? ^ quite stuck on the webcreds part09:02
jibeldidrocks, sure, looking09:03
didrocksthanks09:03
sil2100jibel, didrocks: I saw some errors in the tests, i.e. in the autopilot parts, but still, it's hanged09:03
seb128Laney, hey, did you see andyrocks updated the patch for nautilus/trash segfault? in case you didn't start on it let it to me, I've another patch I want to include in the upload09:10
Laneyseb128: yeah I'm looking at it atm as it happens09:10
seb128Laney, k, please don't upload then, just commit to the vcs09:11
Laneyit does fix the crash but it's not /right/09:11
Laneyyou get a warning about the signal handler not existing09:11
seb128oh?09:11
Laneydon't know why09:11
jibeldidrocks, sil2100 autopilot process is running but is waiting on something (it's looping on [pid 13445] select(5, [4], [], [], {0, 500000}) = 0 (Timeout))09:12
jibeldidrocks, sil2100 there is the following message in dbus.log, I don't know if there is a relation:09:13
jibelstart: Job is already running: hud09:13
jibelFailed to activate service 'com.canonical.hud': timed out09:13
sil2100hmmm09:13
jibeldidrocks, sil2100 I cannot connect to the KVM to see what's happening on the screen, the java plugin is broken again09:14
darkxstseb128, if I get g-s-d 3.8 ready to run with g-c-c 3.6, can we get that onto the ubuntu-desktop ppa?09:14
darkxstalthough not real sure on the whole ibus situation, currently that is disabled in the gnome3 builds09:15
seb128darkxst, g-s-d 3.8 and g-c-c 3.6 ... sounds good, I will review it if you get it working, once step at the time is better09:16
sil2100jibel: hm, so what can we do now besides killing the job?09:17
sil2100That's the first time this is happening, maybe it's just a singular case?09:17
sil2100jibel: not sure if it makes sense to block all other test jobs09:17
jibelplugin fixed, wrong alternative09:18
darkxstseb128, ok, will do09:18
seb128darkxst, thanks09:18
didrockssil2100: just a note, don't touch the webcreds stack please :)09:18
sil2100didrocks: ACK ;)09:18
didrocksthx!09:18
jibelsil2100, didrocks so on the screen, everything is there (launcher, menus, ...) and responsive, just autopilot which is waiting for something09:20
jibelsil2100, it could be a broken tests waiting for an event that'll never happen? I saw something similar when autopilot was trying to reach an icon that was out of the screen on the launcher.09:22
jibelsil2100, I kill the webbrower_app test09:25
sil2100jibel: hm, it might be, since I saw some errors in the webbrowser tests when looking at the logs09:27
sil2100So something might have been broken, but it will be hard to see what - normally everything is handled by timeouts, so it should be impossible09:28
sil2100As we're using Eventually() for every waiting condition, which has a default 10 second timeout09:28
jibelsil2100, anyway, it was the last test and all 78 ran http://10.97.0.1:8080/view/cu2d/view/Autopilot%20Release%20Testing/job/autopilot-saucy-daily_release/170/testReport/09:28
sil2100But so many failed?09:29
jibelsil2100, 23 failed09:29
sil2100jibel: thanks! Let me check that and re-run later, thanks for the analysis ;)09:29
didrockssil2100: indicators passed! (one test failing, below the threshold)09:37
didrockshud*09:37
didrocksnow indicators?09:37
didrockssil2100: hud in manual publication apparently09:37
sil2100First I re-run Apps09:37
didrockslet's cross fingers :)09:38
sil2100In the meantime, let me publish HUD - it's safe to use with old unity (just tested)09:42
sil2100didrocks: http://10.97.0.1:8080/view/cu2d/view/Head/view/HUD/job/cu2d-hud-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_hud_13.10.1daily13.06.19-0ubuntu1.diff/*view*/ <- look ok, can I publish? ;)09:44
didrockssil2100: +1 :)09:46
seb128\o/09:47
Laneyseb128: ok, got a fix ...09:49
Laneylet me attach it upstream and push to bzr09:49
seb128Laney, great, thanks09:50
LaneyIt changes how it does the disconnection because I didn't understand why it was already disconnected :P09:50
* Laney prepares to get abused a bit09:50
seb128lol09:50
sil2100didrocks: can I publish the apps stack? As it's deping on webcreds09:51
sil2100(all tests passed \o/)09:52
sil2100I guess it's ok to publish ;)09:54
didrockssil2100: sure sure, I trust you, and you don't need me if there is no packaging change for an ack!09:58
didrockssil2100: so, indicators now?09:59
sil2100Yesss ;)10:00
Laneyseb128: ok pushed10:01
Laneyyay indicators10:01
seb128Laney, thanks10:01
didrocksLaney: tests didn't pass yet, don't declare victory :)10:06
didrocksseb128: the unity_gtk_modules tests never passed since we added it, can we have attente having a look?10:11
didrockssil2100: I think we should force the publication even if the tests are failing as it's the unity_gtk_modules ones, wdyt?10:11
didrockssil2100: as all the other tests seem good10:18
didrocksapart from those flacky unity gtk module ones10:18
didrocksright?10:18
sil2100Yep, and I upgraded and checked: new indicators don't seem to break old unity10:19
didrocksok :)10:19
sil2100didrocks: should I just run the publish job then?10:19
sil2100(without force)10:19
didrockssil2100: yeah, I guess then it will be in manual publication, but at least, we'll see why :)10:19
sil2100Lots and lots of packaging changes to browse through! Uh oh ;)10:19
didrockssil2100: I removed libical1 from the list FYI10:19
didrockssil2100: or maybe, let's wait for the next iso to clean that10:20
didrockssil2100: have you restarted the version? bamf changes still works with old unity?10:22
seb128didrocks, do you guys need extra testers? I can opt in the ppa if wanted10:22
didrocksseb128: if you can upgrade bamf without the rest, that would be helpful, please10:23
sil2100didrocks: I installed new bamf and ran a guest session10:23
seb128ok, from what ppa? ubuntu-unity/daily-build/ubuntu saucy?10:24
sil2100didrocks: and unity wasn't broken, launcher worked, pips appearing, switcher ok10:24
didrockssil2100: waow, that's awesome seeing the port! :)10:24
didrocksseb128: ubuntu-unity/daily-build saucy, yet10:24
sil2100didrocks: I'm checking the diffs now ;)10:24
didrocksyeah*10:24
didrockssil2100: doing the same as well to not loose time, but good practice for you :)10:24
* didrocks snifs seeing no trailing comma on gnome-screensaver10:25
didrocksjbicha!!! :p10:26
sil2100didrocks: hmmm, libusermetrics should export symbols in .symbols? Since it's C++ and the symbol names are mangled ;/10:28
didrockssil2100: yeah, it passed and built on all archs though. So it will be interesting to see with pete how it works now10:29
didrockssil2100: maybe the check is only run on the same arch now10:29
seb128didrocks, sil2100: new bamf works fine on saucy10:31
didrocks(thanks seb12810:31
seb128np10:31
sil2100didrocks: besides those small things the diffs look ok10:31
sil2100didrocks: how do you think, can I publish?10:31
sil2100s/how/what10:31
didrockssil2100: there is maybe an issue on http://10.97.0.1:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_libindicator_12.10.2daily13.06.19-0ubuntu1.diff10:31
didrocks-usr/share/libindicator/80indicator-debugging /usr/share/libindicator/10:32
didrocksin debian/libindicator-tools.install10:32
didrocksand +usr/share/libindicator/80indicator-debugging /usr/share/libindicator/10:32
didrocksin debian/libindicator3-tools.install10:32
didrockswithout any replaces: from libindicator3-tools against libindicator-tools10:32
didrockslet's see what files are shipped exactly by the current version10:32
didrocksand what files are shipped with the new version10:32
sil2100Now that you mention it, indeed10:32
didrocksok ./usr/share/libindicator/80indicator-debugging is a file10:35
seb128Laney, pitti, jasoncwarner_: btw I just uploaded a gtk update with a patch to fix the segfault after upgrades bug10:35
didrockssil2100: so missing Replaces :/10:35
sil2100Noooo~!10:35
didrocksted! this is clearly not your first package10:35
didrockssil2100: ok, let's see if we can rebuild just that package10:36
sil2100didrocks: without running the check job?10:36
Laneyseb128: good work, so it wasn't in nautilus10:36
didrockssil2100: or with, it doesn't take that long10:36
Laneyyou might want to reassign the bug then10:37
seb128Laney, no, it was gtk not refreshing is icon cache correctly when the one on disk was changing10:37
didrockssil2100: tip of trunk is rev 49810:37
didrocks+  * Automatic snapshot from revision 49810:37
didrocksok, no additional commit10:37
Laneyfair10:38
seb128Laney, good point ... done ;-)10:38
didrockssil2100: I'm tempted to directly push to trunk to speed up the process, the diff is here: http://paste.ubuntu.com/5780054/10:39
didrockssil2100: any opinion?10:39
didrocksurgh, one sec10:39
didrocksseb128: http://paste.ubuntu.com/5780058/10:39
didrockssil2100: ^10:39
sil2100Ah, ok, you mean the first one, yes?10:41
didrockssil2100: the second one10:41
seb128didrocks, http://bazaar.launchpad.net/~indicator-applet-developers/libindicator/trunk.13.10/revision/49810:41
didrockshum10:41
didrocksinteresting10:41
didrockssil2100: I haven't committed back :p10:41
seb128didrocks, NULL means "turn off" apparently10:41
sil2100;)10:41
didrocksseb128: ignore my diff :p10:42
seb128k10:42
didrockshttp://paste.ubuntu.com/5780066/10:42
didrockssil2100: seb128: this should be more within context ^ :p10:42
sil2100didrocks: yes, much better now ;)10:43
sil2100I prefer this version than the 3 ;p10:43
didrocksahah10:43
* didrocks pushes upstream10:43
didrockssil2100: so, rebuild only libindicator please10:44
sil2100o>10:44
didrocksthe test taking few minutes, we can afford them running10:44
didrockssil2100: all the other packaging changes are +1 for me, so then, we can force the publication10:44
sil2100didrocks: the check job still has the libical added, yes?10:45
sil2100Rebuilding!10:45
didrockssil2100: yep, after all, let's remove it once we get a new iso :10:45
didrocks:)10:45
seb128didrocks, yeah, looks fine to me10:51
didrocksgreat!10:51
* sil2100 still waiting for armhf of libindicators to start building11:07
sil2100;|11:07
didrockssil2100: well, we are waiting on the tests as well, right? as unity tests are running?11:08
didrockssil2100: are you sure it's not built? looking at the ppa, only amd64 is still building11:09
sil2100Aaah!11:09
sil2100hahah, sorry, misread amd64 for armhf11:09
sil2100;)11:09
didrocks:)11:09
didrocksETOOMANYA ;)11:09
=== MacSlow is now known as MacSlow|lunch
* ogra_ grins about didrocks and sil2100 .... and wonders what they will do once we have arm64 11:43
didrocksogra_: I'll buffer overflow my head I think :)11:47
ogra_haha11:47
sil2100didrocks: could you nominate to precise? https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1192216 ;)11:50
ubot2Ubuntu bug 1192216 in bamf (Ubuntu) "Bamf is not building in jenkins due to missing coverage xml and xunit formatted tests" [Undecided,New]11:50
sil2100I mean!11:50
sil2100To raring!11:50
sil2100;p11:50
didrockssil2100: is it something we should really backport? we don't have merger to precise11:50
didrocksah :)11:50
* sil2100 needs coffee11:50
didrocksok11:50
sil2100;(11:50
didrockssil2100: if it's fixed in saucy, please change the main status :)11:51
ogra_broken signon-ui deps made all image builds explode today (for all arches) ... is someone on that ?11:53
Laneyit was discussed at some length in #ubuntu-devel this morning11:56
Laneycomponent-mismatches don't get checked by proposed-migration11:56
ogra_yeah11:57
=== greyback is now known as greyback|lunch
=== bigon_ is now known as bigon
didrockssil2100: seb128: still same failures on unity_gtk_module tests FYI, but I guess good to publish the indicators stack12:23
seb128didrocks, k12:24
=== MacSlow|lunch is now known as MacSlow
attentesil2100, the tests didn't pass for you even after https://code.launchpad.net/~attente/unity-gtk-module/edit-undo-fix/+merge/169207?12:58
sil2100attente: hi! I'm not sure, since I remembered that one of your fixes fixed those tests, but then I saw that they were failing since at least a week now, so not sure hmm12:59
attentesil2100, i think it's the same problem looking at the recent jenkins logs; that edit-undo test is causing all the other ones to fail13:06
attenteif we merge this MP in, then maybe it'll be fixed13:08
seb128sil2100, didrocks: ^ just get that pending fix merged and enjoy working tests? :-)13:11
Sweetsharkseb128: https://launchpadlibrarian.net/142834255/libreoffice_1%3A4.1.0~beta2-0ubuntu1~ppa3_1%3A4.1.0~beta2~incompleteinternals1-0ubuntu1~ppa7.diff.gz <- the mother of all hacks13:14
seb128Sweetshark, does it work? ;-)13:15
sil2100Uh13:15
sil2100attente: approving!13:15
Sweetsharkseb128: locally yes, but if it holds on the ppa buildds: we will see -- still building ....13:16
attente:)13:16
Sweetsharkseb128: removing the object files before installing frees some 10GB for sure ...13:16
Sweetsharkseb128: we should have a hangout soonish to talk about how to set up a proper split build ...13:17
seb128Sweetshark, ok, I'm not sure I know enough about the topic to be useful in an hangout discussion .... maybe better to bounce some details/reading via email first?13:19
Sweetsharkseb128: yep. its not super urgent.13:20
=== greyback|lunch is now known as greyback
attenteseb128, i just did an upload of indicator-keyboard to the ppa, can you try it out? https://launchpad.net/~attente/+archive/indicator-keyboard13:30
seb128attente, sure13:31
seb128attente, why did you split the schemas in its own binary?13:32
attenteseb128, i wanted gnome-control-center to only depend on the schema and not the indicator13:33
seb128attente, the proper way is to put the key is gsettings-desktop-schemas13:36
attentenow that i think about it, i probably should've uploaded all the other ibus engines as well since some may be incompatible with 1.513:36
seb128in*13:36
seb128attente, if that's a key supposed to be shared by components13:36
seb128attente, that's where most of the schemas for most desktop settings are13:37
attenteseb128, ok, i'll move it over13:37
attentefunny thing is that was where i had it originally13:37
seb128attente, do you handle upgrades in some way? my test users had 4 layouts before I restarted my session with french as default and now it has only english14:01
=== om26er is now known as om26er|opt
=== om26er|opt is now known as om26er-otp
dobeydesrt, jbicha, or anyone really: do you know how i can get my Alt_L key to work properly in GNOME 3.x again? i can't find a setting to make it work right, and it's not working right in terminal, emacs, firefox, or lots of apps :(14:21
attenteseb128, it doesn't handle migrations of old layouts. i'll see if i can write a postinst script14:25
seb128attente, thanks, postinst is the wrong level though14:25
seb128attente, usually it's better to do it in the code, like a migration gsettings key and do the migration if it's unset14:26
seb128attente, the packaging system might not have access to user dirs if they are encrypted, or on nfs not mounted14:26
seb128attente, you can maybe have a look at how GNOME did the migration, I guess they handle it in some way14:26
attenteseb128, sure, thanks14:27
jbichadobey: works here, maybe you set Alt_L as a keyboard shortcut somewhere; do you still have the problem with a new clean user account?14:28
dobeyjbicha: i never set just Alt_L as a shortcut. it works fine under Unity. and ALt_L+drag, and Alt_L+tab work fine in gnome. :-/14:31
seb128jbicha, gnome-session 3.8 seems fine to me, if you want to upload14:31
seb128attente, good news is that your indicator and settings panel work great for me ;-)14:32
seb128attente, great work!14:32
seb128attente, I've just a problem with the icons used for the keymap ... how do you determine those?14:32
dobeyand i've looked through all the keybinding settings in dconf-editor to see if something obvious was screwing with it, but didn't see anything14:33
attenteseb128, the icons are in the ubuntu-mono package14:33
dobeyjbicha: oh, and Alt_L does the right thing, if i press Super+Alt_L+whatever, which is really weird14:33
=== tkamppeter_ is now known as tkamppeter
attenteseb128, we ended up throwing them all into there as svgs generated by the indicator source package14:34
attentebut what's the issue exactly?14:34
attente(i know there's at least one bug with the icon not switching properly when "new windows are set to use the default source")14:35
dobeyand Alt_R works as normal, but using it for everything is really annoying, especially with the extra long space bar on this keyboard14:35
seb128attente, http://ubuntuone.com/3cwRL3UgG6bP0VTsIfbJuf ... is that normal icons?14:41
seb128attente, sorry took me a bit to take a screenshot, there is a bug in saucy, if you undock your laptop it seems the screenshot try to snap content on screens that are off14:41
seb128attente, the coloring is buggy (maybe that's because I don't use the default theme) and french should be "Fr", not "FA"14:42
attenteseb128, ok. i have a good idea of what's happening there14:42
seb128attente, out of that problem things work great for me as a "multiple layout user"14:43
attente*phew*!14:43
seb128attente, I don't use ibus nor write any language that require it, so I can't really test ... but our g-s-d based indicator was only doing keyboard layouts so what we got there is already great and enough to replace it14:43
attenteseb128, ok, no problem, i'll fix up these issues so that we can push for more users testing14:46
seb128attente, I will try to unblock the ibus 1.5 situation meanwhile14:47
seb128that will be a first thing needed14:47
seb128attente, oh, other problem ... you will need to port unity-greeter, they have a custom keyboard indicator in there, which reads the old config key14:47
attenteseb128, unblock in what way?14:47
attenteseb128, ack14:48
seb128attente, we are still having ibus 1.4 as our default ibus version, I guess your indicator work only with 1.5?14:48
seb128attente, I will just kick in another discussion on the desktop list about ibus 1.5 and what are/were the blocker issues for upgrading to 1.514:48
attenteseb128, yeah, i mean, i guess we could try to get it working with 1.4, but no idea what kind of new issues that will cause14:49
seb128attente, don't bother about that, we will need to upgrade to 1.5 at some point ... one of the main blocker for me was that it didn't play nicely with our old GNOME keyboard stack, which was blocked on having an indicator14:51
seb128so with some luck we can just unblock that now14:51
seb128;-)14:51
attenteah, gotcha :)14:52
sil2100didrocks: in case you missed our talk with attante - the unity-gtk-module test failures should be fixed!14:57
didrockssil2100: I flyed over the discussion and I'm delighted :)14:57
sil2100didrocks: it seems attente made a fix branch that I probably even tested in the past (but probably forgot to approve), and it was waiting in ether14:57
seb128didrocks, the fix he submitted some time ago was waiting for somebody to review it :p14:57
sil2100So I should probably say 'oops my bad!'14:57
didrocksattente: you should konw, poke kindly, then yell :p14:57
didrocksknow*14:58
didrockssil2100: tsss :p14:58
didrockswell, great that's fixed :)14:58
didrockssad that unity-panel-service crashes and don't respawn in that case14:58
mhr3_seb128, ouch, my gedit is using 318mb of ram, it's been running for quite a while, but i was really loading anything huge there :/14:58
seb128mhr3_, was *not*, I guess?14:59
mhr3_seb128, right, sorry14:59
mhr3_seb128, and cups-browsed 330mb... damn15:00
mhr3_seb128, at least zeitgeist-fts isn't the biggest thing anymore :P15:00
didrocksmhr3_: tssss tsss tsss, don't try to find any excuse! you will still have the zeitgeist stamp to me! :)15:03
mhr3_didrocks, come on, it's clear now, zeitgeist is behaving like other services, so it's completely normal :P15:04
seb128bah, nm-applet/n-m got unhappy again and xchat-gnome nm integration disconnects when wifi disconnect15:05
seb128mhr3_, can I just blame your box? :-)15:05
didrocksmhr3_: tsssss :p15:05
seb128mhr3_, for the memory usage15:05
=== dednick is now known as dednick|lunch
mhr3_seb128, no :p15:06
attentedidrocks, duly noted ;)15:07
mhr3_seb128, but i'll forgive you the cups part, it's new code iirc15:07
seb128mhr3_, still mention it to tkamppeter15:07
seb128mhr3_, zeitgeist-fts is using 300m here if you want processes that eat memory :p15:08
mhr3_seb128, ah, you must lots of data, it's just 220mb here :)15:08
mhr3_hm, i loose words15:08
mhr3_think that's caused by the memory leaks15:09
seb128tkamppeter, hey, is there a known bug about "/usr/lib/cups/notifier/dbus dbus://" processes hanging around all day?15:09
seb128tkamppeter, I've a stack of those15:09
seb128mhr3_, ;-)15:09
mdeslaur_seb128: how does this work? https://code.launchpad.net/~dbusmenu-team/libdbusmenu/trunk.13.0415:18
mdeslaur_seb128: will something push that as an SRU if jenkins "released" it?15:18
mdeslaur_or is that inaccurate and I should upload it manually as an SRU?15:19
seb128mdeslaur_, see https://launchpad.net/ubuntu/raring/+queue?queue_state=115:19
seb128mdeslaur_, and cyphermox did the precise one, which is waiting there: http://launchpadlibrarian.net/142680700/libdbusmenu_0.6.2-0ubuntu0.2_source.changes15:20
mdeslaur_ok, slightly confused as I had just looked there and didn't see it in the queue15:20
seb128mdeslaur_, weird ...15:20
seb128mdeslaur_, they have a 2 steps process through a stagging ppa for SRUs, so maybe that created some delay15:20
seb128mdeslaur_, https://launchpad.net/~ubuntu-unity/+archive/sru-staging if you want to check diffs and stuff15:21
seb128hum, though the diff is with the previous daily in that case15:21
mdeslaur_seb128: awesome, thanks15:21
seb128so not very useful15:21
seb128but you get the content at least15:22
seb128mdeslaur_, yw15:22
=== om26er-otp is now known as om26er
=== dednick|lunch is now known as dednick
cyphermoxmdeslaur_: there's a jenkins button to push for that sru15:39
seb128cyphermox, seems like sil2100 pushed it for the stack in raring15:39
cyphermoxyeah15:39
=== davidcalle_ is now known as davidcalle
seb128Laney, btw there is a new glib out if you need a break from qml at some point ;-)16:39
Laneyso there is16:40
LaneyI'll look at it after I get this MPed16:41
seb128Laney, no hurry, I'm just mentioning it ;-)16:42
Laneyyeah but it seems like a good opportunity to do something different ...16:42
Laneyoh, looks like I'm patch piloting tomorrow anyway16:42
tkamppeterseb128, what's on with CUPS?16:43
seb128tkamppeter,16:44
seb128lp        1223  0.0  0.0   6484  1420 ?        S    17:57   0:00 /usr/lib/cups/notifier/dbus dbus://16:44
seb128lp        1224  0.0  0.0   6484  1424 ?        S    17:57   0:00 /usr/lib/cups/notifier/dbus dbus://16:44
seb128lp        1225  0.0  0.0   6484  1420 ?        S    17:57   0:00 /usr/lib/cups/notifier/dbus dbus://16:44
ubot2Launchpad bug 1223 in gcursor (Ubuntu) "gcursor: typo in description" [Medium,Fix released] https://launchpad.net/bugs/122316:44
seb128....16:44
ubot2Launchpad bug 1130 in xfwm4-themes (Ubuntu) "duplicate for #1224 unmet dependancy in xfwm4-themes" [Medium,Fix released] https://launchpad.net/bugs/113016:44
ubot2Launchpad bug 1225 in glom (Ubuntu) "Glom: missing dependency - PostgreSQL" [Low,Fix released] https://launchpad.net/bugs/122516:44
seb128ubot2, stupid bot16:45
ubot2Factoid 'stupid bot' not found16:45
seb128tkamppeter,16:45
seb128$ ps aux | grep "cups/notifier" | wc -l16:45
seb12810116:45
tkamppeterseb128, there was a bug report about this /usr/lib/cups/notifier/dbus dbus://, I think larsu has fixed such a thing some time ago.16:45
seb128well, it's back it seems16:45
seb128tkamppeter, https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/95919516:45
ubot2Ubuntu bug 959195 in indicator-printers (Ubuntu) "65 cups notifier processes running" [Undecided,Fix released]16:46
tkamppeterseb128, probably it needs refixing after every small change in the system.16:46
seb128tkamppeter, that's fixed after doing what was suggested in https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/959195/comments/916:50
ubot2Ubuntu bug 959195 in indicator-printers (Ubuntu) "65 cups notifier processes running" [Undecided,Fix released]16:50
seb128it was maybe a leftover config, I will watch for it16:50
seb128on that note, doing a break, bbiab16:50
tkamppeterseb128, the bug seems to be in indicator-printers and the fix was done in precise, by creating subscriptions with timeout so that if indicator-printers dies that the subscriptions it leaves behind go away within 15 minutes.16:50
* didrocks waves good evening17:04
Sweetsharkjust in case anyone pinged me around 1700UTC please redo, my session died.17:45
=== LordOfTime is now known as LordOfTime|EC2
=== dpm is now known as dpm-afk
=== mhr3__ is now known as mhr3
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!