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