[09:05] <brendand> got a bug i need to raise about the volume change notification not working properly, anyone have any ideas which package it should go to?
[09:08] <brendand> is there such a package as indicator-sound?
[09:19] <brendand> anyone can confirm this bug in Oneiric? https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/805857
[09:19] <ubot4> Launchpad bug 805857 in indicator-sound (Ubuntu) "Volume slider in sound applet cannot be dragged easily (affects: 1) (heat: 6)" [Undecided,New]
[09:42] <brendand> jibel - that bug is quite annoying, can it be set to high at least? it's a regression from natty
[09:42] <brendand> if you can confirm it that is
[09:43] <brendand> actually it probably fits more as a medium
[09:43] <brendand> strictly speaking
[09:43] <brendand> but it's annoying me a lot :)
[10:11] <jibel> brendand, it's already reported. Let me find the dup
[10:12] <brendand> we should really have a smarter duplicate matching algorithm
[10:19] <jibel> brendand, bug 804009
[10:19] <ubot4> Launchpad bug 804009 in indicator-sound (Ubuntu Oneiric) (and 1 other project) "clicking on the volume slider closes the SoundMenu (affects: 1) (heat: 8)" [High,Confirmed] https://launchpad.net/bugs/804009
[10:21] <jibel> brendand, bug 805822 is also a known issue in Natty
[10:21] <ubot4> Launchpad bug 805822 in ubiquity (Ubuntu) "manual partitioning in ubiquity doesn't allow individual changing of mount targets any more (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/805822
[10:21] <jibel> its in the release notes iirc
[10:26] <brendand> any sign of A2 yet?
[10:29] <jibel> brendand, we need to validate a fix for lighdm first. but you can smoketest the latest daily builds.
[10:31] <jibel> brendand, desktop images are on the tracker
[10:32] <brendand> \o/
[10:38] <htorque> hey everyone! how can i append an .apport file to an existing bug? couldn't figure that one out from man apport-cli
[10:39] <brendand> 'apport-collect BUGNUMBER'
[10:42] <htorque> can't do that, that's sending too much private data :-(
[10:43] <htorque> i wrote the report to a file and cleaned that, should i just attach it?
[10:43] <brendand> htorque - bug number?
[10:44] <htorque> bug 805808 again
[10:44] <ubot4> Launchpad bug 805808 in network-manager (Ubuntu) "NM slow to connect through WPA2 on boot and after resuming from standby [Intel Centrino Ultimate-N 5300 & 6300] (affects: 1) (heat: 10)" [Undecided,Incomplete] https://launchpad.net/bugs/805808
[10:44] <brendand> just making sure :)
[12:18] <hggdh> htorque: as a rule of thumb, we disregard .apport attachments
[12:20] <htorque> hggdh: k, but why doesn't apport-cli let me add it then? i can't do '-u <bug> -c <file>'.
[12:22] <hggdh> htorque: use 'apport-collect' to add data (i.e., attachments) to an existing bug
[12:26] <pedro_> hello hggdh!
[12:37] <hggdh> pedro_: good morning, sir (and jibel as well)
[12:38] <jibel> Good morning hggdh and pedro_
[12:38] <pedro_> good morning jibel!
[12:38] <pedro_> or noon/afternoon
[12:38] <hggdh> hum. It rhymes
[12:41] <hggdh> pedro_: I guess 'good morningnoon' covers morning, noon, and afternoon
[12:41] <pedro_> hahahaha
[12:41] <pedro_> hggdh, now we just need a word that also covers night for the Australian folks :-P
[12:42] <jibel> does good mornoong suites any diurnal period too ?
[12:42] <hggdh> even better! It is more, ah, soundfull (or soundfool?)
[12:44] <hggdh> ** bug-controllers **: we have two pending membership requrest in the queue. How about looking at them?
[12:44]  * hggdh goes do the needful, and all that
[12:45] <hggdh> jibel: do we already have a candidate?
[12:45] <jibel> anyone can confirm bug 805923, it's a mouse attack against lightdm
[12:45] <ubot4> Launchpad bug 805923 in lightdm (Ubuntu) "lightdm-example-gtk-greeter crashed with SIGABRT in raise() (affects: 1) (heat: 10)" [Medium,New] https://launchpad.net/bugs/805923
[12:46] <jibel> hggdh, yes we do.
[12:47] <hggdh> jibel: I will try 805923, I have to rebbot anyway
[12:47] <hggdh> brb
[12:54] <hggdh> where are my workspaces? And what happened to Unity?
[12:54] <hggdh> and is there a meaning to life, after all?
[12:55] <yofel> sure, 42
[12:55] <hggdh> heh. I *knew* ;-)
[12:55]  * penguin42 nods
[12:56] <hggdh> Can some one explain to me, in few, short, and simple sentences, what happened to Unity?
[12:56] <seb128> "nothing"?
[12:56] <seb128> works for me at least
[12:56] <hggdh> LOL
[12:56] <penguin42> broken for me on OO
[12:56] <pedro_> works ok for me too
[12:56] <seb128> jibel, don't hammer too much on the greater it's an hello world one
[12:56] <seb128> jibel, it will be replaced by the unity one when robert_ancell write it in the next weeks
[12:56]  * penguin42 has a recurring segfault in unity-panel-services
[12:56] <ikt> ohh
[12:57] <seb128> jibel, not sure it's worth opening bugs about it
[12:57] <ikt> is alpha 2 out?
[12:57] <seb128> ikt, no, testing is just starting
[12:57] <hggdh> it does work for me. I lost two workspaces, gained an 'Activity' tab in the top, and all my shortcuts are gone
[12:57] <seb128> ikt, it's scheduled for thursday
[12:57] <ikt> ah ok
[12:57] <seb128> hggdh, seems like you are using gnome-shell
[12:57] <hggdh> bloody hell.
[12:57] <jibel> seb128, if a double-click is hammering what is real hammering .
[12:58] <seb128> jibel, lol
[12:58] <hggdh> I tried so hard not to even get there...
[12:58] <seb128> jibel, double click is fine, I was telling you in case you planned to hammer and open 25 bugs
[12:58] <hggdh> seb128: so there is a bug lurking here somewhere, will find it
[12:58] <seb128> jibel, like you did for gnome-control-center to the poor rodrigo ;-)
[12:58] <jibel> seb128, that was not my intention :-)
[12:58] <seb128> ok, great, ignore me then
[12:59] <seb128> jibel, thanks for the great testing btw ;-)
[12:59] <hggdh> seb128: it *was* his intention, pedro_ and I can testify
[12:59] <seb128> now we need to get pedro to send those bugs to GNOME
[12:59] <jibel> pedro_, btw there are some g-c-c bugs to upstream.
[12:59] <pedro_> oh yes he said 'i'm going to open thousand of reports just so they get assigned to rodrigo'
[12:59] <pedro_> i heard that
[12:59] <seb128> never trust the frenchs...
[13:00] <seb128> pedro_, you stop kicking in my door btw!
[13:00] <pedro_> !!
[13:00] <pedro_> ahahahaha!
[13:00]  * pedro_ hugs seb128
[13:00] <pedro_> that was funny :-P
[13:00]  * seb128 hugs pedro_
[13:00] <seb128> we just need to hide next time or I'm sure you guys will take your revenge
[13:01] <seb128> ;-)
[13:01] <pedro_> sleep with one eye open :-P
[13:01] <hggdh> heh. Nice start of day today -- I already feel happier (and I know it will pass, sigh)
[13:02]  * hggdh goes in 'recherche de la unity perdue
[16:37] <kamusin> am trying to get a full backtrace from a gwibber issue but I can't find which dbg package is missing,  actual backtrace at http://pastebin.ubuntu.com/638478/
[16:37] <kamusin> any help is well received and appreciated
[16:39] <hggdh> kamusin: would it generate an apport report if it failed on normal usage? If so, you can use apport-retrace to grab the dbgsyms
[16:40] <kamusin> actually it does, but it's still incomplete , don't know why
[16:40] <deuxpi> gwibber is written in Python, so it does have backtraces, but it doesn't need debug symbol packages
[16:43] <Ampelbein> deuxpi: if the crash is in gwibber itself, yes. if the crash is in a library called from gwibber, you still need debugging symbols.
[16:44] <hggdh> kamusin: you can also use 'apt-file' -- ápt-file search /usr/lib/python2.7/dist-packages/appindicator/_appindicator.so
[16:45] <kamusin> I did hggdh, I have installed python-appindicator-dbgsym but is still incomplete
[16:45] <kamusin> libappindicator1-dbgsym, libappindicator3-1-dbgsym and nothing happens.. still incomplete
[16:45] <hggdh> try installing libappindicator1dbgsym
[16:46] <hggdh> libappindicator1-dbgsym
[16:46] <hggdh> darn!
[16:46] <kamusin> yep, weeird...
[16:47] <kamusin> by the way, am running Oneiric
[16:47] <hggdh> kamusin: are all the libraries up-to-date?
[16:47] <kamusin> hggdh, all is up to date
[16:47]  * hggdh grumbles a bit about debug libraries
[16:48] <kamusin> :(
[16:50] <hggdh> and the python debug libraries as well, are they installed? It looks -- apart from frame 5 -- that these are calls from within Python
[16:51] <kamusin> ok I will check them as the last resort
[16:54] <kamusin> nope, nothing changed... oh god..
[16:57] <jibel> hm, nice bug with dbus menu, when there are 2 windows with the same menu, dbusmenu sends the command to both not only the active window. interesting
[17:03] <kamusin> jibel, heh
[17:03] <kamusin> ok time for lunch (brb)
[18:41] <Elbrus> if a bug makes the package uninstallable, what should the severity be? high? (bug 805677)
[18:41] <ubot4> Launchpad bug 805677 in lazarus (Ubuntu) "Oneiric: please rebuild lazarus, it depends on an old fpc version (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/805677
[18:41]  * Elbrus is wondering if he should rephrase the bug summary of his own bug
[18:42] <charlie-tca> Depends on the package, according to https://wiki.ubuntu.com/Bugs/Importance
[18:43]  * Elbrus is looking into that page
[18:46] <Elbrus> I would go for: A bug that has a severe impact on a non-core application.
[18:46] <Elbrus> so can somebody set the bug to medium for me please?
[18:47] <charlie-tca> done
[18:48] <Elbrus> charlie-tca: thanks
[18:48] <charlie-tca> no problem
[18:53] <Ampelbein> charlie-tca, Elbrus: I disagree. If the package has wrong dependencies it can't be installed at all, which (to me) is "Has a severe impact on a small portion of Ubuntu users", ergo -> High.
[18:54] <Ampelbein> Additionally, in this case unrelated packages fail to build from source and FTBFS bugs are of High Importance.
[18:59] <charlie-tca> developers would know that better than myself. I would expect them to raise it when needed
[19:00] <Elbrus> hmm, my package (winff) FTBFS indeed
[19:00] <charlie-tca> Where would I find FTBFS bugs are HIGH? It is not in https://wiki.ubuntu.com/Bugs/Importance
[19:00] <Elbrus> and lazarus (and fpc) doesn't have much caretakers in ubuntu.. (I am one of them)
[19:01] <Elbrus> as my package depends on it
[19:01] <micahg> Elbrus: if it won't affect the images, I'll take care of it tomorrow when I'm piloting
[19:02] <Elbrus> alpha image you mean?
[19:02] <micahg> Elbrus: right, we're frozen until thursday for those
[19:02] <Elbrus> right, I don't think my package or lazarus are on the image (if that is what you are talking about)
[19:03] <charlie-tca> Ampelbein: Where would I find FTBFS bugs are HIGH? It is not in https://wiki.ubuntu.com/Bugs/Importance
[19:04] <Ampelbein> charlie-tca: I guess it's not mentioned explicitly, but if you look at recent FTBFS bugs filed they are all classified as "High".
[19:04] <charlie-tca> I don't think I ever saw that anyone as justification to set any importantance.
[19:06] <Elbrus> charlie-tca: well, Debian considers them grave: http://www.debian.org/Bugs/Developer#severities
[19:06] <Elbrus> which is pretty high ;)
[19:06] <charlie-tca> Elbrus: I will agree with that. I think Debian grave == Ubuntu critical
[19:07] <micahg> hmm, I would think Debian grave = high
[19:07] <Ampelbein> charlie-tca: In Debian, they are RC-Critical, meaning a package gets removed from the release. In Ubuntu we generally don't remove packages from releases because they fail to build.
[19:07] <Elbrus> I think Debian critical == Ubuntu critical
[19:08] <charlie-tca> I thought grave was higher than critical in Debian?
[19:08] <Elbrus> nope
[19:08] <Elbrus> see my link
[19:08] <charlie-tca> Then I am wrong.
[19:10] <Elbrus> Amplebein: actually, the bug in question here doesn't FTBFS, it causes other packages to
[19:10] <Elbrus> so how does this dependecy walk through?
[19:11] <Elbrus> s/dependecy/dependency
[19:11] <Ampelbein> Elbrus: See https://launchpadlibrarian.net/74230317/buildlog_ubuntu-oneiric-amd64.winff_1.3.2-4_FAILEDTOBUILD.txt.gz
[19:11] <Elbrus> well, I put that in the report myself...
[19:12] <Elbrus> I mean, how does the severity of one bug depend on the severity of an other bug that it causes
[19:13]  * Elbrus hasn't reported the FTBFS for winff yet, but has it on his radar
[19:13] <Ampelbein> Elbrus: If a bug is self-contained so that it only affects it's own package I consider it less serious than a bug making other packages fail.
[19:14] <Elbrus> I agree
[19:14] <Elbrus> but I can't remember that I saw this in Ubuntu's wiki's or similar
[19:18] <Elbrus> related question, should the FTBFS of winff be "Also affects project" or should it really be an other bug. It should be blocked by this one, but I don't know how to achieve that in launchpad
[19:20] <Ampelbein> Elbrus: sadly, launchpad doesn't support "Blocked" bugs like bts does :-(
[19:20] <Elbrus> shame
[19:20] <Ampelbein> Elbrus: Just use 'Also affects distribution', choose Ubuntu and the correct sourcepackage
[19:21] <Elbrus> Ampelbein: that is what I assumed
[23:11] <valorin> Anyone around who can help get Bug #755842 noticed by the right people? It's a serious usability bug imho and it would be great to get it fixed before Oneiric.
[23:11] <ubot4> Launchpad bug 755842 in unity (Ubuntu) (and 1 other project) "Non-maximized windows which sit on the border of a workspace move when called (affects: 25) (dups: 4) (heat: 98)" [Undecided,Confirmed] https://launchpad.net/bugs/755842
[23:27] <penguin42> well I guess it needs an importance setting - I suggest a 'Medium' ('A usability issue that does not limit the functionality of a core application' or possibly 'A bug that has a moderate impact on a core application') ?
[23:34] <pedro_> which bug are you folks talking?
[23:34] <pedro_> hello again btw
[23:34] <penguin42> bug 755842
[23:34] <ubot4> Launchpad bug 755842 in unity (Ubuntu) (and 1 other project) "Non-maximized windows which sit on the border of a workspace move when called (affects: 25) (dups: 4) (heat: 98)" [Undecided,Confirmed] https://launchpad.net/bugs/755842
[23:37] <pedro_> that seems fine, yes, i've changed it to triaged/medium
[23:41] <penguin42> Thanks
[23:44] <valorin> pedro_, Thank you.
[23:45] <pedro_> you're welcome