[03:53] <pitti> Good morning
[03:53] <pitti> robru: I am now
[04:00] <robru> pitti, haha. i can't remember why I wanted to talk to you
[04:01] <pitti> robru: ah, if only we had a way to relay messages to absent people :)
[04:02] <robru> pitti, one day we will! I'm sure of it!
[04:03] <robru> pitti, I must have seen your name associated with some random project or other that I had a passing interest in. have you worked on any notable side-projects in the last day or two?
[04:05] <pitti> robru: network-manager, some discussions about python-dbusmock, langpack maintenance, jhbuild maintenance, some systemd bug fixing, fatrace enhancements
[04:06] <robru> pitti, hmmmmmm, not ringing any bells. I'll try to email you next time I think of it ;-)
[04:06] <pitti> robru: or just ask your question on IRC; I read backscroll
[04:06] <robru> pitti, good point ;-)
[06:51] <jibel> good morning
[06:55] <didrocks> salut jibel!
[06:58] <jibel> salut didrocks !
[07:21] <seb128> hey desktopers
[07:21] <didrocks> salut seb128
[07:21] <seb128> lut didrocks
[08:02] <Laney> heya
[08:03] <didrocks> hey Laney!
[08:03] <Laney> guten morgen didrocks! wie gehts?
[08:05] <darkxst> pitti, have you had a chance to look into the retracer yet/
[08:05] <pitti> ah no, we even disabled LP crashes for raring now
[08:05] <didrocks> Laney: Es geht mir gut, and und Sie?
[08:05] <didrocks> -and
[08:05] <pitti> bonjour didrocks et seb128
[08:05] <didrocks> salut pitti!
[08:05] <Laney> sehr gut, danke
[08:06] <darkxst> pitti, we are still getting them
[08:06] <darkxst> and have a rather large list of unusable crash reports
[08:11] <seb128> Laney, pitti: good morning!
[08:11]  * pitti hugs mvo
[08:12] <seb128> mvo \o/
[08:12] <didrocks> hey mvo!
[08:12] <mvo> seb128, pitti: good morning!
[08:12] <mvo> hey didrocks
[08:12] <mvo> woah, what a nice hello I get :)
[08:13] <seb128> mvo, good to see you are still hanging around, we miss you here ;-)
[08:14]  * mvo hugs seb128
[08:14] <pitti> mvo: want us to spoil your welcome with some ridiculously hard apt bugs? :-)
[08:14] <mvo> I knew it!
[08:15] <mvo> which one?
[08:15]  * seb128 hugs mvo back
[08:15] <mvo> (of the many)
[08:15]  * pitti ponders
[08:15] <mvo> ;)
[08:15]  * mvo runs away screaming
[08:15] <pitti> mvo: oh, oh! how about this terribly inconsistent --auto-remove vs. autoremove?
[08:15] <pitti> that'll keep you busy blueprinting, testing, and implementing for 3 months!
[08:16]  * pitti hugs mvo, j/k of course
[08:16] <mvo> like that you can spell it with or without the "--" :P
[08:16]  * mvo thinks we should remove options if we can
[09:04] <seb128> mvo, is there an official way to ask "when was the last update done"?
[09:05] <seb128> mvo, like an api in aptd or something? or that's basically "check the timestamp of some apt file"?
[09:05] <mvo> seb128: as in successful apt-get update run or apt-get {dist-,}upgrade
[09:05] <seb128> mvo, last time upgrades have been applied, so the later
[09:05] <mvo> seb128: currently its the timestamp, a api would be good I suppose
[09:06] <mvo> seb128: /var/log/apt/history.log is probably the best bet
[09:06] <seb128> mvo, danke
[09:06] <mvo> yw
[09:07] <seb128> mvo, I'm trying to figure what we need to build https://wiki.ubuntu.com/AboutThisDevice#Phone
[09:07] <seb128> mvo, though what "update" means will likely change on device where we will deploy base images rather than package
[09:07] <seb128> mvo, but I'm looking at how we get those infos nowadays just for documentation purpose
[09:09] <mvo> seb128: I would say use the history file, that is the best way right now
[09:09] <seb128> mvo, thanks
[09:31] <darkxst> seb128, is there a bug/blueprint somewhere tracking what needs to be done to land 3.8 components?
[09:31] <seb128> no, but we should probably do that
[09:32] <seb128> I will file one
[09:32] <darkxst> seb128, ok, seem like a good idea
[09:32] <seb128> right
[09:34] <didrocks> TheMuso: hey, quite a few people are complaining since latest pulseaudio update that it's taking a big chunk of their CPU. I wonder if the inotify patch doesn't go crazy if /run/ isn't present or anything…
[09:35] <didrocks> TheMuso: heard about it?
[09:35] <seb128> didrocks, can you mention it n #ubuntu-devel? I think diwic made the patch?
[09:35] <didrocks> yeah, it did
[09:35] <didrocks> he*
[09:36] <seb128> he's not on -desktop
[09:37] <didrocks> seb128: let's move the discussion there, then, thanks!
[09:37] <seb128> didrocks, thank you for pointing it ;-)
[09:37] <seb128> didrocks, got feedback from the french forum? ;-)
[09:37] <ricotz> didrocks, hey, i am complaining too then ;)
[09:37] <didrocks> seb128: exactly, and quite an important one, so not just one isolated case…
[09:37] <seb128> ricotz, do you get the issue?
[09:38] <ricotz> seb128, yes
[09:38] <seb128> ricotz, good, you can help diwic to debug then maybe? ;-)
[09:38] <ricotz> i already reverted the upgrade since it would drain my battery ;)
[09:45] <xclaesse> seb128, is it known that after suspend/resume or external monitor connect/disconnect (not sure what triggers it exactly) sometimes the windows are moved to different workspaces?
[09:45] <seb128> xclaesse, that was supposed to be fixed in recent compiz updates, when did you restart your session last?
[09:45] <xclaesse> 11:45:49 up 2 days uptime
[09:46] <xclaesse> 2 days, 15:55 even
[09:46] <seb128> xclaesse,
[09:46] <seb128> compiz (1:0.9.9~daily13.04.10-0ubuntu1) raring; urgency=low
[09:46] <seb128>   [ Steve Langasek ]
[09:46] <seb128>   * Adding/Removing an external monitor causes open windows to move to
[09:46] <seb128>     another workspace (LP: #763148)
[09:46] <ubot2> Launchpad bug 763148 in Compiz Core "Adding/Removing an external monitor causes open windows to move to another workspace" [Medium,In progress] https://launchpad.net/bugs/763148
[09:47] <xclaesse> ok, I'll restart and let you know if it happens again then.
[09:47] <xclaesse> thanks
[09:48] <seb128> thanks
[11:22]  * Laney installs a logind-using lightdm
[11:24]  * Laney reboots without remembering to actually install it *ahem*
[12:10] <pitti> Laney: nice!
[12:10] <Laney> not so - it crashes :P
[12:10] <pitti> Laney: so you can now shutdown from the login screen?
[12:11] <Laney> in theory though
[12:11] <Laney> you should be able to do all of that
[12:11] <pitti> I also saw a patch on the bug that should provide logind based user switching
[12:11] <Laney> yeah, and robert landed shutdown/reboot in trunk
[12:11] <pitti> great, so it sounds things will come together nicely
[12:12] <pitti> I currently plan to do the switch on the sprint
[12:12] <pitti> when we have Robert, you, stgraber, slangasek, and me together to deal with any remaining fallout
[12:13] <Laney> yay, should be exciting
[12:13] <Laney> I'll hopefully stop it crashing today ...
[12:13] <stgraber> considering it'll be the first week of the S cycle, I doubt we'll break too many machines ;)
[13:01] <ritz_> cyphermox ping
[13:05] <psivaa> seb128: didrocks: Just reported bug 1170338 that's impacting VM installations with today's images and with updated packages.
[13:05] <ubot2> Launchpad bug 1170338 in compiz (Ubuntu) "Launcher and systems indicator icons do not appear on VMs with raring desktop installations" [Undecided,New] https://launchpad.net/bugs/1170338
[13:07] <didrocks> psivaa: hey, instead of attaching the crash, can you report the bug with apport-bug -c <crash file>?
[13:07] <didrocks> psivaa: so that we can get a retraced stacktrace
[13:07] <didrocks> psivaa: FYI, there is a new version of compiz/unity now
[13:07] <didrocks> psivaa: so upgrading to those and restarting the session would be great :)
[13:08] <psivaa> didrocks: as i said in the bug, this bug was reported after updating with the latest packages
[13:08] <didrocks> psivaa: you meant 20130418 desktop image
[13:09] <psivaa> didrocks: yes, i installed that image, then did a dist-upgrade and reported the bug after that
[13:09] <didrocks> ok, what version of unity is it? (all packages were not acked at the same time)
[13:10] <psivaa> 13.04.18~13.04-oubuntu1
[13:10] <psivaa> didrocks: ^
[13:11] <didrocks> Laney: waiting for your nux branch btw :p
[13:11] <didrocks> psivaa: ok, and nux?
[13:11] <didrocks> I think it should be the latest as well
[13:12] <didrocks> interesting
[13:12] <didrocks> psivaa: I don't have any vm off hand, I'll try with tomorrow's image, weird you see that on vm and not on hw…
[13:13] <psivaa> didrocks: yes, i tried it with hw and it did not occur, also i only tried with i386 as of now, will try with amd64 in a bit
[13:13] <didrocks> psivaa: you don't have any other .crash file in /var/crash/ ?
[13:13] <didrocks> psivaa: also, if you see that, try starting a terminal and type "unity"
[13:14] <didrocks> psivaa: to ensure you see the same, that would be useful info :)
[13:14] <psivaa> didrocks: there is no crash file in /var/crash
[13:15] <didrocks> interesting…
[13:15] <psivaa> *no other crash files other than that is attached to the bug, but that crash occurred before updating the system
[13:15] <didrocks> psivaa: and the indicator processes are running?
[13:15] <didrocks> psivaa: as well as unity-panel-service?
[13:15] <Laney> didrocks: https://code.launchpad.net/~laney/nux/remove-unneeded-changelog-entry/+merge/159590
[13:15] <Laney> maybe it should have been against lp:nux/raring? But I don't see that in the config and the branches have the same commits anyway
[13:16] <didrocks> Laney: approved :)
[13:16] <didrocks> Laney: no, they didn't diverge yet
[13:16] <Laney> cheers
[13:16] <didrocks> AFAIK
[13:16] <Laney> no, looks not
[13:16] <Laney> will it get pushed to both then?
[13:16] <psivaa> didrocks: unable to locate unity-panel-service ??
[13:17] <psivaa> and unable to locate nux
[13:17] <didrocks> ?
[13:17] <didrocks> psivaa: what do you mean by "locate"
[13:17] <seb128> those are not commands/not in the standard path
[13:18] <didrocks> Laney: no idea, I hope that the guy who will diverge will make sure that branches are synchronized first :)
[13:18] <Laney> heh
[13:18] <psivaa> didrocks: sorry when i run apt-cache policy nux i get 'unable to locate package nux'
[13:18] <didrocks> there is no nux package
[13:18] <didrocks> libnux-4.0-0
[13:18] <didrocks> is the package name
[13:19] <didrocks> psivaa: and I'm asking if the process unity-panel-service and the indicators one are running (on your system)
[13:21] <psivaa> didrocks: ahh sorry,  4.0.1daily13.04.17~13.04-0ubuntu1 is the installed version
[13:21] <didrocks> ok, at least, latest on everything :)
[13:33] <seb128> didrocks, psivaa: yep, confirmed
[13:34] <seb128> the libgl1-mesa-dri update breaks unity (segfault) in virtualbox
[13:34] <seb128> tjaalton, ^
[13:34] <seb128> bryce, ^
[13:35] <psivaa> seb128: thanks :)
[13:46] <didrocks> mlankhorst: so, in the future, do you mind ensuring that mesa is not breaking unity in a vm? :)
[13:50] <seb128> psivaa, you can install https://launchpad.net/~mlankhorst/+archive/ppa/+files/libgl1-mesa-dri_9.1.1-0ubuntu3%7Eppa1_i386.deb if you need a working vm, that fixes the issue
[13:50] <seb128> psivaa, that's in the raring queue and should get it when an archive admin reviews it
[13:54] <mlankhorst> didrocks: the breakage was specifically due to a rebase of a size reduction hack for mesa, I'm more curious why it wasn't hit before
[13:55] <tjaalton> huh, it was tested on kvm, but not virtualbox
[13:55] <mlankhorst> tjaalton: it only happens on i386 llvmpipe or nouveau
[13:55] <mlankhorst> and even for nouveau only < nvc0
[13:55] <psivaa> seb128: yes, it's working now with that deb installation on kvm, thanks
[13:55] <seb128> psivaa, yw
[13:55] <tjaalton> ok so it was probably on amd64 then
[13:56] <seb128> tjaalton, it happens in Xephyr with software rendering forced as well
[13:56] <seb128> so not specific to virtualbox
[13:56] <mlankhorst> still i386 specific..
[13:57] <seb128> right
[13:57] <seb128> but my point was that we should test on i386 and amd64
[13:57] <seb128> especially for an upload the day before hard freeze :p
[13:57] <seb128> that ffe has been coming for a while
[13:58] <seb128> it's a been disconcerting that nobody tested on i386 vm during that time
[14:01] <tjaalton> yes, shame on us :)
[14:02] <dobey> tedg: is indicator-datetime still your baby?
[14:02] <seb128> tjaalton, sorry, I'm not wanting to point finger, just to make sure next time we do test on those target so we don't run into a breakage again ;-)
[14:02] <tedg> dobey, No, not really.  It's the indicator team's.
[14:02] <tedg> dobey, I think that charles touched it last.
[14:02] <seb128> dobey, charles has been looking at it most recently
[14:03] <dobey> ah ok
[14:03] <tjaalton> seb128: we'll just upload it earlier and not wait for upstream indefinitely
[14:03] <tjaalton> that was the original mistake
[14:03] <tjaalton> would've caught this issue a month earlier
[14:03] <tjaalton> or two
[14:03] <seb128> but you would have broken unity performances  on some intel cards...
[14:04] <tjaalton> well, the current version just reverts the commit which caused that.. dunno why it didn't occur to me earlier to do that
[14:05] <mlankhorst> idle hope that upstream would fix it..
[14:05] <tjaalton> turns out to be kinda hard I guess. such is life when you're after a few fps on some games :)
[14:16] <dobey> charles: bug #1170366 for you :)
[14:16] <ubot2> Launchpad bug 1170366 in indicator-datetime (Ubuntu) "Broken handling of All-Day events" [Undecided,New] https://launchpad.net/bugs/1170366
[14:30] <Laney> pitti: Phew - I got it to stop crashing and show me a greeter
[14:30] <Laney> shutdown/reboot don't seem to work just yet though - will work on that next
[14:30] <Laney> also, do you think we should be opening a CK session if logind is running or not?
[14:31] <Laney> brb, lunch
[14:32] <pitti> Laney: if you care about running that on raring, then it may make sense, yes
[14:32] <pitti> Laney: we won't need that any more in squishy
[14:40] <kenvandine> hehe... squishy
[14:40] <kenvandine> pitti, i think you should get to name at least one release :)
[14:45] <pitti> well, it gets high time to announce the new name..
[14:45] <davmor2> kenvandine: next time P comes around I think we have Powerhungry Pitti :)
[14:48] <davmor2> I mean by then Ubuntu will be using so little power someone needs to use it :)
[14:49] <pitti> lol
[14:49] <pitti> I'm practicing my pushups! :-)
[14:49] <kenvandine> hehe
[14:50] <davmor2> pitti: :)
[14:51] <davmor2> pitti: is squid the animal to your squishy?
[14:53] <pitti> that has a certain ring to it
[14:53] <pitti> "adapts to all your needs and forms"
[14:55] <xclaesse> seb128, windows changing of workspace happened again
[14:55] <davmor2> pitti: tentacles in many pies
[14:55] <seb128> xclaesse, try asking slangasek/smspillaz on #ubuntu-unity
[14:56] <xclaesse> seb128, laptop was docked with external monitor, then I suspend it, undock while suspended, then wakeup without external monitors => firefox got moved to first workspace
[14:56] <xclaesse> but it seems thta other windows stayed on their workspace
[14:56] <seb128> where was it before? on a position that still exist?
[14:56] <seb128> if it was on the screen that got removed it's normal that it gets moved on somewhere visible
[14:57] <xclaesse> yep, I configured compiz to have 8 workspaces horizontally
[14:57] <xclaesse> when I have external monitor, the laptop monitor is disabled
[14:57] <xclaesse> so I never use dual screen
[15:50] <Dark_light> who's the mesa maintaner that's working on mesa for 13.08 ?
[15:51] <mitya57> Dark_light: 13.08?
[15:51] <mitya57> Dark_light: I believe mesa is maintained by #ubuntu-x team
[15:54] <Dark_light> humm ok I've been told to look for him here I'll try there, thanks!
[16:02] <jbicha> seb128: hey I missed the gnome 3.8 conversation yesterday
[16:02] <seb128> jbicha, hey
[16:02] <jbicha> I think the stuff in the GNOME3 PPA for raring should be fairly safe to land in S next month
[16:03] <seb128> jbicha, is that the gnome3 or the staging ppa?
[16:03] <jbicha> there's a few bugs with GTK 3.8, Software Center, and Nautilus desktop handling but those shouldn't be too bad
[16:03] <jbicha> just the regular gnome3 PPA
[16:03] <jbicha> staging is for stuff that needs more work
[16:04] <jbicha> that would give us a split 3.6/3.8 foundation but it's worked pretty well so far
[16:05] <jbicha> personally I usually run Raring+gnome3 PPA but without the staging PPA
[16:05] <seb128> jbicha, it would help if those had vcs-es and merge requests
[16:05] <seb128> jbicha, I don't want to repeat what happened this cycle, we regressed on gnome-control-center and nautilus and then everybody moved to work on the ppa and let the regressions in raring
[16:05] <seb128> jbicha, I just fixed the system proxy stuff tuesday we would have released with that broken otherwise
[16:06] <jbicha> merge requests against what?
[16:07] <seb128> the official packaging vcs-es
[16:07] <seb128> like a nautilus-3-8 packaging vcs than we could bzr merge on lp:~ubuntu-desktop/nautilus/ubuntu
[16:07] <seb128> rather than having to try to figure out what changed and copy stuff overs by hand
[16:08] <jbicha> yeah we could do bzr branches
[16:08] <seb128> it would make easier to see the history of the work that happened on the vcs
[16:09] <seb128> some people tend to not properly list their changes in the changelog there ;-)
[16:09] <seb128> (ricotz to not list anyone :p)
[16:09] <jbicha> ricotz has been doing better with that for the gnome3 ppas for several weeks now
[16:09] <seb128> good to read
[16:10] <seb128> like the nautilus 3.8 changelog doesn't mention the patch to restore the "create document" submenu that you said would not work in the new version
[16:10] <seb128> it means that either the change is not included in the ppa at all, or it got commented out, it got updated
[16:10] <seb128> but I can't get that information easily atm :/
[16:11] <seb128> jbicha, well, in any case agreed, 90% of the ppa should be fine
[16:11] <seb128> the most problematic one will be nautilus
[16:11] <seb128> (and g-s-d/g-c-c but they are not in that ppa yet)
[16:11] <seb128> what about gtk and software-center?
[16:13] <jbicha> yes nautilus needs more work, if you would look at the debian/changelog you'd see that the last version in common is 1:3.6.3-0ubuntu5
[16:13] <jbicha> we have to continually rebase against current Ubuntu and we hadn't done that recently for nautilus (but I did do it for gnome-control-center this week)
[16:14] <seb128> right
[16:14] <seb128> the rebasing would be easier with a packaging vcs ;-)
[16:14] <seb128> it would just be to merge the new revision from the ubuntu serie
[16:14] <jbicha> the merging gets complicated when patches get rebased so I'm not sure it would be smooth
[16:14] <seb128> anyway, I told earlier to darkxst that I would register a blueprint for GNOME 3.8
[16:15] <seb128> and start listing known issues for the updates
[16:15] <jbicha> there's bug 1163886 that we haven't figured out yet, someone mentioned yesterday that it worked if they ran usc with sudo
[16:15] <ubot2> Launchpad bug 1163886 in software-center (Ubuntu) "software-center crashed with signal 5 with the GNOME3 PPA on 13.04" [Medium,Confirmed] https://launchpad.net/bugs/1163886
[16:15] <seb128> do you know of any component that will need lot of work
[16:15] <seb128> out of nautilus/g-c-c/g-s-d?
[16:16] <jbicha> g-c-c needs Canonical expertise to figure out how to get external panels working again
[16:16] <seb128> yeah
[16:17] <jbicha> power management is broken but 2/3 of the problem will be solved by logind
[16:17] <seb128> going to be a lot of fun rebasing patches we had for e.g adding unity launcher controls to the display capplet I guess
[16:17] <jbicha> there's quite a few other patches that need to be rebased (they're listed in d/changelog)
[16:17] <seb128> right
[16:17] <seb128> I'm a bit concerned about stuff moving to gnome-shell as well
[16:18] <seb128> like https://bugzilla.gnome.org/show_bug.cgi?id=691202
[16:18] <ubot2> Gnome bug 691202 in power "power: Drop explicit screen locking on suspend" [Normal,Resolved: fixed]
[16:18] <seb128> or media keys handling
[16:18] <darkxst> seb128, does unit use the OSD's?
[16:18] <seb128> "OSD"?
[16:18] <seb128> we have notify-osd
[16:18] <seb128> if you are speaking about libnotify notification service
[16:19] <darkxst> ok so you don't use the ones that were removed from g-s-d
[16:19] <seb128> you mean?
[16:19] <seb128> the service is what displays the messages on screen
[16:19] <seb128> e.g the rendering
[16:19] <seb128> oh
[16:19] <jbicha> g-s-d did some extra media keys refactoring for 3.7.92 so the ppa is still on 3.7.91
[16:19] <darkxst> yes
[16:20] <seb128> you mean the popups for media keys/volume/screen etc ?
[16:20] <darkxst> yes
[16:20] <seb128> we sort of use g-s-d
[16:20] <seb128> we patch the g-s-d code to send synchronous notifications to notify-osd
[16:22] <darkxst> ok
[16:33] <darkxst> I probably should go to bed, (like 2hrs ago)
[16:36] <darkxst> seb128, just cc me on the blueprint whenever you make it
[17:02]  * didrocks waves good evening
[20:39] <tedg> Hey attente, larsu was saying that indicator-keyboard has the manifest for indicator-ng in it.  But I can't find it.  Can you give me a pointer?
[20:42] <attente> tedg, sorry, i don't understand what you mean by manifest
[20:43] <attente> is it the .indicator file?
[20:43] <tedg> attente, yes
[20:43] <attente> it's generated from data/Makefile.am
[20:44] <tedg> Ah, I see.  Thanks!
[21:30] <desrt> mterry, larsu: just about to leave montréal.  flight is a bit (20mins) late
[21:31] <desrt> i'll text when i land
[21:31] <mterry> desrt, k
[21:58] <TheMuso> didrocks: No, your comment is the first I've heard about it.
[22:01] <TheMuso> didrocks: Ah, seems David has fixed it.