=== duflu_ is now known as duflu
pittiGood morning03:53
pittirobru: I am now03:53
robrupitti, haha. i can't remember why I wanted to talk to you04:00
pittirobru: ah, if only we had a way to relay messages to absent people :)04:01
robrupitti, one day we will! I'm sure of it!04:02
robrupitti, 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:03
pittirobru: network-manager, some discussions about python-dbusmock, langpack maintenance, jhbuild maintenance, some systemd bug fixing, fatrace enhancements04:05
robrupitti, hmmmmmm, not ringing any bells. I'll try to email you next time I think of it ;-)04:06
pittirobru: or just ask your question on IRC; I read backscroll04:06
robrupitti, good point ;-)04:06
=== tkamppeter_ is now known as tkamppeter
jibelgood morning06:51
didrockssalut jibel!06:55
jibelsalut didrocks !06:58
seb128hey desktopers07:21
didrockssalut seb12807:21
seb128lut didrocks07:21
didrockshey Laney!08:03
Laneyguten morgen didrocks! wie gehts?08:03
darkxstpitti, have you had a chance to look into the retracer yet/08:05
pittiah no, we even disabled LP crashes for raring now08:05
didrocksLaney: Es geht mir gut, and und Sie?08:05
pittibonjour didrocks et seb12808:05
didrockssalut pitti!08:05
Laneysehr gut, danke08:05
darkxstpitti, we are still getting them08:06
darkxstand have a rather large list of unusable crash reports08:06
seb128Laney, pitti: good morning!08:11
=== mvo__ is now known as mvo
* pitti hugs mvo08:11
seb128mvo \o/08:12
didrockshey mvo!08:12
mvoseb128, pitti: good morning!08:12
mvohey didrocks08:12
mvowoah, what a nice hello I get :)08:12
seb128mvo, good to see you are still hanging around, we miss you here ;-)08:13
* mvo hugs seb12808:14
pittimvo: want us to spoil your welcome with some ridiculously hard apt bugs? :-)08:14
mvoI knew it!08:14
mvowhich one?08:15
* seb128 hugs mvo back08:15
mvo(of the many)08:15
* pitti ponders08:15
* mvo runs away screaming08:15
pittimvo: oh, oh! how about this terribly inconsistent --auto-remove vs. autoremove?08:15
pittithat'll keep you busy blueprinting, testing, and implementing for 3 months!08:15
* pitti hugs mvo, j/k of course08:16
mvolike that you can spell it with or without the "--" :P08:16
* mvo thinks we should remove options if we can08:16
seb128mvo, is there an official way to ask "when was the last update done"?09:04
seb128mvo, like an api in aptd or something? or that's basically "check the timestamp of some apt file"?09:05
mvoseb128: as in successful apt-get update run or apt-get {dist-,}upgrade09:05
seb128mvo, last time upgrades have been applied, so the later09:05
mvoseb128: currently its the timestamp, a api would be good I suppose09:05
mvoseb128: /var/log/apt/history.log is probably the best bet09:06
seb128mvo, danke09:06
seb128mvo, I'm trying to figure what we need to build https://wiki.ubuntu.com/AboutThisDevice#Phone09:07
seb128mvo, though what "update" means will likely change on device where we will deploy base images rather than package09:07
seb128mvo, but I'm looking at how we get those infos nowadays just for documentation purpose09:07
mvoseb128: I would say use the history file, that is the best way right now09:09
seb128mvo, thanks09:09
darkxstseb128, is there a bug/blueprint somewhere tracking what needs to be done to land 3.8 components?09:31
seb128no, but we should probably do that09:31
seb128I will file one09:32
darkxstseb128, ok, seem like a good idea09:32
didrocksTheMuso: 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:34
didrocksTheMuso: heard about it?09:35
seb128didrocks, can you mention it n #ubuntu-devel? I think diwic made the patch?09:35
didrocksyeah, it did09:35
seb128he's not on -desktop09:36
didrocksseb128: let's move the discussion there, then, thanks!09:37
seb128didrocks, thank you for pointing it ;-)09:37
seb128didrocks, got feedback from the french forum? ;-)09:37
ricotzdidrocks, hey, i am complaining too then ;)09:37
didrocksseb128: exactly, and quite an important one, so not just one isolated case…09:37
seb128ricotz, do you get the issue?09:37
ricotzseb128, yes09:38
seb128ricotz, good, you can help diwic to debug then maybe? ;-)09:38
ricotzi already reverted the upgrade since it would drain my battery ;)09:38
xclaesseseb128, 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
seb128xclaesse, that was supposed to be fixed in recent compiz updates, when did you restart your session last?09:45
xclaesse11:45:49 up 2 days uptime09:45
xclaesse2 days, 15:55 even09:46
seb128compiz (1:0.9.9~daily13.04.10-0ubuntu1) raring; urgency=low09:46
seb128  [ Steve Langasek ]09:46
seb128  * Adding/Removing an external monitor causes open windows to move to09:46
seb128    another workspace (LP: #763148)09:46
ubot2Launchpad 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/76314809:46
xclaesseok, I'll restart and let you know if it happens again then.09:47
=== alan_g is now known as alan_g|tea
=== alan_g|tea is now known as alan_g
=== ara_ is now known as ara
* Laney installs a logind-using lightdm11:22
* Laney reboots without remembering to actually install it *ahem*11:24
=== alan_g is now known as alan_g|lunch
pittiLaney: nice!12:10
Laneynot so - it crashes :P12:10
pittiLaney: so you can now shutdown from the login screen?12:10
Laneyin theory though12:11
Laneyyou should be able to do all of that12:11
pittiI also saw a patch on the bug that should provide logind based user switching12:11
Laneyyeah, and robert landed shutdown/reboot in trunk12:11
pittigreat, so it sounds things will come together nicely12:11
pittiI currently plan to do the switch on the sprint12:12
pittiwhen we have Robert, you, stgraber, slangasek, and me together to deal with any remaining fallout12:12
Laneyyay, should be exciting12:13
LaneyI'll hopefully stop it crashing today ...12:13
stgraberconsidering it'll be the first week of the S cycle, I doubt we'll break too many machines ;)12:13
=== mvo_ is now known as mvo
=== olli__ is now known as olli
ritz_cyphermox ping13:01
=== alan_g|lunch is now known as alan_g
psivaaseb128: didrocks: Just reported bug 1170338 that's impacting VM installations with today's images and with updated packages.13:05
ubot2Launchpad 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/117033813:05
didrockspsivaa: hey, instead of attaching the crash, can you report the bug with apport-bug -c <crash file>?13:07
didrockspsivaa: so that we can get a retraced stacktrace13:07
didrockspsivaa: FYI, there is a new version of compiz/unity now13:07
didrockspsivaa: so upgrading to those and restarting the session would be great :)13:07
psivaadidrocks: as i said in the bug, this bug was reported after updating with the latest packages13:08
didrockspsivaa: you meant 20130418 desktop image13:08
psivaadidrocks: yes, i installed that image, then did a dist-upgrade and reported the bug after that13:09
didrocksok, what version of unity is it? (all packages were not acked at the same time)13:09
psivaadidrocks: ^13:10
didrocksLaney: waiting for your nux branch btw :p13:11
didrockspsivaa: ok, and nux?13:11
didrocksI think it should be the latest as well13:11
didrockspsivaa: 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:12
psivaadidrocks: 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 bit13:13
didrockspsivaa: you don't have any other .crash file in /var/crash/ ?13:13
didrockspsivaa: also, if you see that, try starting a terminal and type "unity"13:13
didrockspsivaa: to ensure you see the same, that would be useful info :)13:14
psivaadidrocks: there is no crash file in /var/crash13:14
psivaa*no other crash files other than that is attached to the bug, but that crash occurred before updating the system13:15
didrockspsivaa: and the indicator processes are running?13:15
didrockspsivaa: as well as unity-panel-service?13:15
Laneydidrocks: https://code.launchpad.net/~laney/nux/remove-unneeded-changelog-entry/+merge/15959013:15
Laneymaybe it should have been against lp:nux/raring? But I don't see that in the config and the branches have the same commits anyway13:15
didrocksLaney: approved :)13:16
didrocksLaney: no, they didn't diverge yet13:16
Laneyno, looks not13:16
Laneywill it get pushed to both then?13:16
psivaadidrocks: unable to locate unity-panel-service ??13:16
psivaaand unable to locate nux13:17
didrockspsivaa: what do you mean by "locate"13:17
seb128those are not commands/not in the standard path13:17
didrocksLaney: no idea, I hope that the guy who will diverge will make sure that branches are synchronized first :)13:18
psivaadidrocks: sorry when i run apt-cache policy nux i get 'unable to locate package nux'13:18
didrocksthere is no nux package13:18
didrocksis the package name13:18
didrockspsivaa: and I'm asking if the process unity-panel-service and the indicators one are running (on your system)13:19
psivaadidrocks: ahh sorry,  4.0.1daily13.04.17~13.04-0ubuntu1 is the installed version13:21
didrocksok, at least, latest on everything :)13:21
seb128didrocks, psivaa: yep, confirmed13:33
seb128the libgl1-mesa-dri update breaks unity (segfault) in virtualbox13:34
seb128tjaalton, ^13:34
seb128bryce, ^13:34
psivaaseb128: thanks :)13:35
=== vrruiz_ is now known as rvr
didrocksmlankhorst: so, in the future, do you mind ensuring that mesa is not breaking unity in a vm? :)13:46
seb128psivaa, 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 issue13:50
seb128psivaa, that's in the raring queue and should get it when an archive admin reviews it13:50
mlankhorstdidrocks: the breakage was specifically due to a rebase of a size reduction hack for mesa, I'm more curious why it wasn't hit before13:54
tjaaltonhuh, it was tested on kvm, but not virtualbox13:55
mlankhorsttjaalton: it only happens on i386 llvmpipe or nouveau13:55
mlankhorstand even for nouveau only < nvc013:55
psivaaseb128: yes, it's working now with that deb installation on kvm, thanks13:55
seb128psivaa, yw13:55
tjaaltonok so it was probably on amd64 then13:55
seb128tjaalton, it happens in Xephyr with software rendering forced as well13:56
seb128so not specific to virtualbox13:56
mlankhorststill i386 specific..13:56
seb128but my point was that we should test on i386 and amd6413:57
seb128especially for an upload the day before hard freeze :p13:57
seb128that ffe has been coming for a while13:57
seb128it's a been disconcerting that nobody tested on i386 vm during that time13:58
tjaaltonyes, shame on us :)14:01
dobeytedg: is indicator-datetime still your baby?14:02
seb128tjaalton, 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
tedgdobey, No, not really.  It's the indicator team's.14:02
tedgdobey, I think that charles touched it last.14:02
seb128dobey, charles has been looking at it most recently14:02
dobeyah ok14:03
tjaaltonseb128: we'll just upload it earlier and not wait for upstream indefinitely14:03
tjaaltonthat was the original mistake14:03
tjaaltonwould've caught this issue a month earlier14:03
tjaaltonor two14:03
seb128but you would have broken unity performances  on some intel cards...14:03
tjaaltonwell, the current version just reverts the commit which caused that.. dunno why it didn't occur to me earlier to do that14:04
mlankhorstidle hope that upstream would fix it..14:05
tjaaltonturns out to be kinda hard I guess. such is life when you're after a few fps on some games :)14:05
dobeycharles: bug #1170366 for you :)14:16
ubot2Launchpad bug 1170366 in indicator-datetime (Ubuntu) "Broken handling of All-Day events" [Undecided,New] https://launchpad.net/bugs/117036614:16
=== Sweetsha1k is now known as Sweetshark
Laneypitti: Phew - I got it to stop crashing and show me a greeter14:30
Laneyshutdown/reboot don't seem to work just yet though - will work on that next14:30
Laneyalso, do you think we should be opening a CK session if logind is running or not?14:30
Laneybrb, lunch14:31
pittiLaney: if you care about running that on raring, then it may make sense, yes14:32
pittiLaney: we won't need that any more in squishy14:32
kenvandinehehe... squishy14:40
kenvandinepitti, i think you should get to name at least one release :)14:40
pittiwell, it gets high time to announce the new name..14:45
=== alan_g is now known as alan_g|tea
davmor2kenvandine: next time P comes around I think we have Powerhungry Pitti :)14:45
davmor2I mean by then Ubuntu will be using so little power someone needs to use it :)14:48
pittiI'm practicing my pushups! :-)14:49
davmor2pitti: :)14:50
=== m_conley_away is now known as m_conley
davmor2pitti: is squid the animal to your squishy?14:51
pittithat has a certain ring to it14:53
pitti"adapts to all your needs and forms"14:53
xclaesseseb128, windows changing of workspace happened again14:55
davmor2pitti: tentacles in many pies14:55
seb128xclaesse, try asking slangasek/smspillaz on #ubuntu-unity14:55
xclaesseseb128, laptop was docked with external monitor, then I suspend it, undock while suspended, then wakeup without external monitors => firefox got moved to first workspace14:56
xclaessebut it seems thta other windows stayed on their workspace14:56
seb128where was it before? on a position that still exist?14:56
seb128if it was on the screen that got removed it's normal that it gets moved on somewhere visible14:56
xclaesseyep, I configured compiz to have 8 workspaces horizontally14:57
xclaessewhen I have external monitor, the laptop monitor is disabled14:57
xclaesseso I never use dual screen14:57
=== alan_g|tea is now known as alan_g
Dark_lightwho's the mesa maintaner that's working on mesa for 13.08 ?15:50
mitya57Dark_light: 13.08?15:51
mitya57Dark_light: I believe mesa is maintained by #ubuntu-x team15:51
Dark_lighthumm ok I've been told to look for him here I'll try there, thanks!15:54
jbichaseb128: hey I missed the gnome 3.8 conversation yesterday16:02
seb128jbicha, hey16:02
jbichaI think the stuff in the GNOME3 PPA for raring should be fairly safe to land in S next month16:02
seb128jbicha, is that the gnome3 or the staging ppa?16:03
jbichathere's a few bugs with GTK 3.8, Software Center, and Nautilus desktop handling but those shouldn't be too bad16:03
jbichajust the regular gnome3 PPA16:03
jbichastaging is for stuff that needs more work16:03
jbichathat would give us a split 3.6/3.8 foundation but it's worked pretty well so far16:04
jbichapersonally I usually run Raring+gnome3 PPA but without the staging PPA16:05
seb128jbicha, it would help if those had vcs-es and merge requests16:05
seb128jbicha, 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 raring16:05
seb128jbicha, I just fixed the system proxy stuff tuesday we would have released with that broken otherwise16:05
jbichamerge requests against what?16:06
seb128the official packaging vcs-es16:07
seb128like a nautilus-3-8 packaging vcs than we could bzr merge on lp:~ubuntu-desktop/nautilus/ubuntu16:07
seb128rather than having to try to figure out what changed and copy stuff overs by hand16:07
jbichayeah we could do bzr branches16:08
seb128it would make easier to see the history of the work that happened on the vcs16:08
seb128some people tend to not properly list their changes in the changelog there ;-)16:09
seb128(ricotz to not list anyone :p)16:09
jbicharicotz has been doing better with that for the gnome3 ppas for several weeks now16:09
seb128good to read16:09
seb128like 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 version16:10
seb128it means that either the change is not included in the ppa at all, or it got commented out, it got updated16:10
seb128but I can't get that information easily atm :/16:10
seb128jbicha, well, in any case agreed, 90% of the ppa should be fine16:11
seb128the most problematic one will be nautilus16:11
seb128(and g-s-d/g-c-c but they are not in that ppa yet)16:11
seb128what about gtk and software-center?16:11
jbichayes 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-0ubuntu516:13
jbichawe 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:13
seb128the rebasing would be easier with a packaging vcs ;-)16:14
seb128it would just be to merge the new revision from the ubuntu serie16:14
jbichathe merging gets complicated when patches get rebased so I'm not sure it would be smooth16:14
seb128anyway, I told earlier to darkxst that I would register a blueprint for GNOME 3.816:14
seb128and start listing known issues for the updates16:15
jbichathere's bug 1163886 that we haven't figured out yet, someone mentioned yesterday that it worked if they ran usc with sudo16:15
ubot2Launchpad 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/116388616:15
seb128do you know of any component that will need lot of work16:15
seb128out of nautilus/g-c-c/g-s-d?16:15
jbichag-c-c needs Canonical expertise to figure out how to get external panels working again16:16
jbichapower management is broken but 2/3 of the problem will be solved by logind16:17
seb128going to be a lot of fun rebasing patches we had for e.g adding unity launcher controls to the display capplet I guess16:17
jbichathere's quite a few other patches that need to be rebased (they're listed in d/changelog)16:17
seb128I'm a bit concerned about stuff moving to gnome-shell as well16:17
seb128like https://bugzilla.gnome.org/show_bug.cgi?id=69120216:18
ubot2Gnome bug 691202 in power "power: Drop explicit screen locking on suspend" [Normal,Resolved: fixed]16:18
seb128or media keys handling16:18
darkxstseb128, does unit use the OSD's?16:18
seb128we have notify-osd16:18
seb128if you are speaking about libnotify notification service16:18
darkxstok so you don't use the ones that were removed from g-s-d16:19
seb128you mean?16:19
seb128the service is what displays the messages on screen16:19
seb128e.g the rendering16:19
jbichag-s-d did some extra media keys refactoring for 3.7.92 so the ppa is still on 3.7.9116:19
seb128you mean the popups for media keys/volume/screen etc ?16:20
seb128we sort of use g-s-d16:20
seb128we patch the g-s-d code to send synchronous notifications to notify-osd16:20
darkxstI probably should go to bed, (like 2hrs ago)16:33
darkxstseb128, just cc me on the blueprint whenever you make it16:36
* didrocks waves good evening17:02
=== alan_g is now known as alan_g|life
tedgHey 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:39
attentetedg, sorry, i don't understand what you mean by manifest20:42
attenteis it the .indicator file?20:43
tedgattente, yes20:43
attenteit's generated from data/Makefile.am20:43
tedgAh, I see.  Thanks!20:44
desrtmterry, larsu: just about to leave montréal.  flight is a bit (20mins) late21:30
desrti'll text when i land21:31
mterrydesrt, k21:31
TheMusodidrocks: No, your comment is the first I've heard about it.21:58
TheMusodidrocks: Ah, seems David has fixed it.22:01
=== m_conley is now known as m_conley_away
=== hggdh_ is now known as hggdh

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