[04:26] <jasoncwarner_> hey bryceh or RAOF, around?
[04:38] <RAOF> jasoncwarner_: Yup, what's up?
[04:38] <jasoncwarner_> hey RAOF remember that mouse reverse scrolling bug?
[04:38] <jasoncwarner_> (apple mighty mouse thing)?
[04:39] <RAOF> With the horizontal scrolling?
[04:39] <jasoncwarner_> it's back...wondering if my custom config is messing up the upstream fix
[04:39] <jasoncwarner_> yeah
[05:10] <pitti> Good morning
[05:52] <bryceh> jason__, tried removing your custom config?
[06:10] <rickspencer3> pitti, what's the word on the street about beta2?
[06:11] <rickspencer3> (also, I was woken up by a bird very early this morning, I kinda blame you guys for this)
[06:11] <pitti> rickspencer3: it's out :) haven't heard about catastrophes yet
[06:11] <rickspencer3> "no catastrophes" is as good as it gets sometimes ;)
[06:11] <pitti> rickspencer3: pah -- I've been for about two weeks now, by a bird that sounds like an alarm clock
[06:13] <rickspencer3> pitti, I'm actually reading good things about beta2 on reddit
[06:13] <rickspencer3> comments are quite positive about both robustness and Unity
[06:13] <pitti> nothing on heise.de yet
[06:14] <rickspencer3> pitti, no archive probs?
[06:14] <rickspencer3> I thought we were supposed to have a crush of uploads and a mess to untangle today
[06:14] <rickspencer3> ;)
[06:15] <pitti> rickspencer3: if you want some, we'll need to reupload LibO
[06:15] <pitti> rickspencer3: our -proposed builds failed :/
[06:15] <pitti> because of that LP bug again
[06:15] <pitti> so we need to build in precise directly
[06:15] <rickspencer3> *sigh*
[06:15] <pitti> rickspencer3: but it's in trunk now, should be rolled out next week
[06:15] <pitti> from then on we'll be able to use -proposed all the time
[06:15] <rickspencer3> pitti, can Sweetshark just fix LO once and for all next cycle
[06:16] <rickspencer3> ?
[06:16] <pitti> rickspencer3: not Sweetshark's fault this time
[06:16] <rickspencer3> pitti, oh, I thoguht it was never his fault
[06:16] <rickspencer3> I thought the problem was it has a monolythic build structure
[06:16] <pitti> it's just the 4 h on amd64 vs. 20 h on armhf difference
[06:16] <rickspencer3> monolithic
[06:16] <rickspencer3> I was not taking Sweetshark'
[06:17] <rickspencer3> s name in vain !
[06:17] <rickspencer3> I remember we had discussed years ago refactoring it into a more modular build structure, so we could rebuild only parts that changed, etc...
[06:18] <pitti> right, but upstream went the opposite direction
[06:18] <pitti> they merged all their per-project git trees into one
[06:19] <robert_ancell> pitti, are you planning on updating pygobject and libgnomekbd?
[06:19] <didrocks> good morning
[06:20] <pitti> robert_ancell: yes, I wanted to sync it after the freeze (pygobject)
[06:20] <pitti> robert_ancell: and I'm happy to look into libgnomekbd, too; I hope we can just sync as well, I might need to make some fixes to Debian
[06:20] <pitti> bonjour didrocks
[06:21] <rickspencer3> hey didrocks
[06:21] <didrocks> guten morgen pitti, how are you?
[06:21] <robert_ancell> pitti, I had a quick look and there's more than trivial changes.  I think you had your name on it somewhere so I thought I'd leave it to you if you are most familair
[06:21] <didrocks> bonjour rickspencer3 ;)
[06:21] <rickspencer3> didrocks, I'm reading nice things about unity this morning
[06:21] <didrocks> rickspencer3: nice blog post!
[06:21] <rickspencer3> good evening robert_ancell, btw
[06:21] <didrocks> rickspencer3: ah?
[06:21] <rickspencer3> :)
[06:21] <robert_ancell> rickspencer3, hey
[06:21] <didrocks> (nice btw ;))
[06:22] <rickspencer3> didrocks, I think the combination of all around quality on the desktop, and feature completion in Unity has come together very noticably for beta2
[06:22] <rickspencer3> didrocks, what does the French community think?
[06:23] <didrocks> rickspencer3: they really love precise. Quite bored by the stability (they like when things broke in the unstable forum) even ;) So really, there is the feeling that the Quality really raised compared to the feedback 6 months ago
[06:24] <didrocks> rickspencer3: they are still some concerns about some features/design, but the overall impression on Unity is really positive
[06:24] <pitti> now we just need to fix that effing HUD to not come up all the time again
[06:24] <pitti> but yes, by and large it's really good
[06:24] <rickspencer3> pitti, I;m starting to agree with you about HUD invocation
[06:24] <didrocks> pitti: you still have that in 3D? I know it's an issue on 2D
[06:24] <didrocks> but not sure in 3D
[06:24] <rickspencer3> this does not happen to me, but I read about it
[06:24] <RAOF> I've not been noticing accidentally bringing up the HUD.
[06:24] <pitti> didrocks: it was fixed in 5.6, then re-broken in 5.8
[06:25] <didrocks> rickspencer3: it's an executive decision about the shortcut, we tried to make design coming back on this decision one month ago when all the issues arised
[06:25] <pitti> at least it's configurable in 3D
[06:25] <didrocks> pitti: do you have a test case?
[06:25] <pitti> but we really need to make it configurable in 2D, too
[06:25] <didrocks> pitti: there is really no step by step reproducer in 3D for accidental reveal since 5.6
[06:26] <rickspencer3> didrocks, by executive decision, do you mean it's was sabdfl decided?
[06:26] <didrocks> rickspencer3: indeed
[06:26] <pitti> I'll try to come up with one; it's erratic, but happens all the time here
[06:26] <robert_ancell> rickspencer3, that's how I read that :)
[06:26] <didrocks> pitti: please do ;)
[06:26] <rickspencer3> so is the bug simply that 2d needs to work like 3d?
[06:26] <didrocks> pitti: I'm using alt heavily in weechat, that didn't happen to me since 5.6
[06:26]  * rickspencer3 should use 2d more
[06:27] <rickspencer3> I actually used the hud in gimp yesterday, it is very useful there
[06:27] <didrocks> rickspencer3: well, not "simple" though, as the hack is in compiz and related to the fact that unity and compiz are in the same process
[06:27] <didrocks> so can't do that in 2d as metacity and unity-2d are 2 processes
[06:27] <rickspencer3> didrocks, but from a user perspective, it should work the same?
[06:28] <didrocks> rickspencer3: right, from a user perspective, apart from pitti's case who seem to still have a bad test case
[06:28] <didrocks> (in 3D)
[06:28] <didrocks> just telling that fixing this in compiz took approximately a full week (maybe a little bit more)
[06:28] <didrocks> so not trivial at all
[06:29] <didrocks> will talk again with the 2D guys today
[06:29] <didrocks> to know where we are standing at
[06:29] <rickspencer3> didrocks, is there a specific bug report on this?
[06:30] <didrocks> rickspencer3: there were quite a lot in 3D, but they are all fixed in 5.6 (that's why I would love to hear from additional wrong cases)
[06:31] <didrocks> rickspencer3: for 2d, there is bug #923410 and bug #947613
[06:31] <ubot2> Launchpad bug 923410 in unity-2d "HUD - closing a window with <Alt>+<F4> opens the hud" [Undecided,Confirmed] https://launchpad.net/bugs/923410
[06:31] <ubot2> Launchpad bug 947613 in unity-2d "Alt key summoning HUD needs to be configurable" [High,Confirmed] https://launchpad.net/bugs/947613
[06:31] <rickspencer3> thanks didrocks
[06:31] <didrocks> yw :)
[06:31] <didrocks> (the first one was used for tracking in 3D btw)
[06:35] <tkamppeter> pitti, hi
[06:35] <pitti> hey tkamppeter
[06:36] <tkamppeter> pitti, can you upload cups and cups-filters to Debian and Ubuntu, now where beta freeze is over?
[06:36] <micahg> tkamppeter: you hear any reports of HP desktop printing being broke in precise?
[06:37] <pitti> tkamppeter: can do, yes
[06:42] <tkamppeter> micahg, today there came in a bug that Ghostscript falls into an infinite loop, do you mean this (bug 968785)? If not, tell me the bug number.
[06:42] <ubot2> Launchpad bug 968785 in ghostscript "ghostscript runs for indefinitely long period of time when called by foomatic-rip" [Undecided,New] https://launchpad.net/bugs/968785
[06:43] <pitti> tkamppeter: the poppler 0.18 patch fails to unapply, will need to fix this first
[06:43] <micahg> tkamppeter: no, I think it has to do with not uploading the firmware, once I did that manually, I was able to print
[06:53] <RAOF> didrocks: Thinking of keyboard shortcuts, have you seen bug #968914 (tapping <super><left> leaves the launcher and keyboard shortcuts overlay up until you press <super> again)?
[06:53] <ubot2> Launchpad bug 968914 in unity "Tapping <Super><left> leaves launcher and “keyboard shortcuts” open" [Undecided,New] https://launchpad.net/bugs/968914
[06:53] <pitti> tkamppeter: all done
[06:54] <didrocks> RAOF: yeah, this one is known and fixed in trunk
[06:54] <didrocks> RAOF: we will have on Monday a compiz version with this fix and another without my workaround for upgrade users ;)
[06:55] <RAOF> *Without*?
[06:55] <RAOF> You mean, users' settings won't get reset? :)
[06:57] <didrocks> RAOF: right, and we will have a proper fix :)
[06:57] <didrocks> (and no more python process starting at boot time)
[06:57] <didrocks> (and then and happier pitti)
[06:57] <didrocks> (sun will shine, we will enjoy a beer all together…)
[06:57] <pitti> didrocks: unity-lens-video and unity-scope-video-remot ?
[06:58] <RAOF> Bunnies will frolick in the dells
[06:58] <didrocks> pitti: they are not started at login :)
[06:58] <didrocks> RAOF: exactly! :)
[07:49] <tkamppeter> pitti, thanks.
[08:00] <seb128> hey
[08:02] <pitti> bonjour seb128, ca va?
[08:02] <pitti> seb128: congrats for breaking the 300 mark!
[08:02] <seb128> pitti, hey, wie geht's?
[08:02] <seb128> I'm good thanks
[08:02] <seb128> got it? waouh! ;-)
[08:04] <pitti> seb128: so, nobody got any counts from the proposed copies
[08:04] <seb128> pitti, which are least prevented didrocks to go too high in scoring :p
[08:05] <didrocks> that's not fair!
[08:05] <didrocks> :)
[08:05] <pitti> you win either way :)
[08:07] <didrocks> yeah, but it can be so much more classy :)
[08:10] <dpm> good morning desktop people!
[08:11] <pitti> hey dpm, wie gehts?
[08:11] <dpm> morgen pitti, gut, danke! Und selbst?
[08:12] <seb128> hey dpm
[08:12] <dpm> morning seb128
[08:13] <seb128> pitti, go pitti go! if I count well with this morning uploads you need one small extra bug to get to 300 ;-)
[08:13] <pitti> seb128: I have one udisks fix committed in Debian
[08:13] <pitti> seb128: and debugging the race you had yesterday :)
[08:13] <seb128> \o/
[08:13] <pitti> seb128: oh, did you count the cups stuff?
[08:13] <seb128> pitti, yes
[08:13] <pitti> seb128: most of these are already fixed
[08:13] <seb128> oh ok
[08:13] <pitti> seb128: Till did -0bzrN uploads
[08:13] <pitti> these just have one for me
[08:14] <seb128> ok, so a few extra ones still
[08:14] <pitti> anyway, getting to 300 should be no problem
[08:14] <seb128> pitti, let me know if you need extra debug output on your udisks race
[08:14]  * pitti ^5s seb128, we really made precise measurably better
[08:14] <dpm> hi mvo, I know Synaptic might be a low priority package, but if you've got the chance, do you think it'd be possible to do an upload including translations only, to fix bug 889351 - it seems lots of translations done in LP are not shipped in the package
[08:14] <ubot2> Launchpad bug 889351 in synaptic "Synaptic does not ship all available translations" [Undecided,Confirmed] https://launchpad.net/bugs/889351
[08:14]  * seb128 hugs pitti
[08:17] <micahg> dpm: that should be fixed in precise
[08:19] <dpm> cool thanks micahg, if it is, would you mind updating the bug status?
[08:22] <micahg> dpm: hmm, nope, no en_* translations
[08:26] <pitti> Sweetshark: guten Morgen
[08:26] <pitti> Sweetshark: sorry to tell you that all the recent builds failed due to bug 930217
[08:26] <ubot2> Launchpad bug 930217 in launchpad "Make proposed pocket useful for staging uploads" [Low,Fix committed] https://launchpad.net/bugs/930217
[08:27] <pitti> Sweetshark: that fix will be rolled out next week, but could you please prepare a no-change upload to precise today, so that it can build over the weekend?
[08:27] <pitti> Sweetshark: (we unfroze precise, so we can't use -proposed any more)
[08:39] <mvo> dpm: oh, sure
[08:45] <seb128> pitti, do you have any opinion on taking that change for precise?
[08:45] <seb128> http://cgit.freedesktop.org/accountsservice/commit/?id=1fd8d981d134257e1d18ef356f5aa08a6f2d7f28
[08:45] <seb128> http://cgit.freedesktop.org/accountsservice/commit/?id=552a0c856a6e3a7c2e6450ab80e79f4204062281
[08:46] <pitti> seb128: doesn't quite match Debian/ubuntu, though
[08:46] <pitti> most system users have /bin/false as shell
[08:46] <seb128> pitti, there is an extra commit to add /bin/false
[08:46] <pitti> and many have /bin/sh actually
[08:47] <pitti> the static uids
[08:47] <pitti> libuuid:x:100:101::/var/lib/libuuid:/bin/sh
[08:47] <pitti> some dynamic system users seem to get it wrong, too
[08:47] <seb128> hum ok, seems a bit risky
[08:47] <pitti> sshd:x:114:65534::/var/run/sshd:/usr/sbin/nologin
[08:47] <pitti> and we have nologin in a different path
[08:47] <seb128> pitti, the context is https://bugzilla.gnome.org/show_bug.cgi?id=671484
[08:47] <Sweetshark> pitti: well, "no-change" still means a version-bump right?
[08:47] <ubot2> Gnome bug 671484 in User Accounts "segfault in um_user_set_icon_file() (when uid < UID_MIN?)" [Critical,Resolved: notgnome]
[08:47] <pitti> Sweetshark: right
[08:47] <Sweetshark> pitti: k, will do
[08:48] <pitti> Sweetshark: thanks, and sorry for the mess; I wasn't aware that it would trash builds as well
[08:48] <seb128> pitti, i.e the user account dialog has issues with users having an uid < UID_MIN, but I guess it's not a frequent case
[08:48] <seb128> pitti, thanks, you convinced me it's less risky to stay with what we have :p
[08:48] <pitti> seb128: right, real users should stay with >= 500, and with Debian's default config >= 1000
[08:49] <pitti> if you use something else, then the GUI tools won't show these
[08:49] <seb128> pitti, well there is a bit of a bug somewhere but I guess we should fix it from the g-c-c side
[08:50] <seb128> pitti, that segfaults has 5 duplicates in launchpad so it happens to some people
[08:50] <pitti> right
[08:51] <seb128> pitti, I will look at making g-c-c robust to those rather, playing catchup on what is a valid shell or not seems risky for this cycle
[08:51] <seb128> pitti, thanks
[08:51] <seb128> doh, 425 updates today
[08:52] <pitti> seb128: yes, and as long as sys users have /bin/sh, it won't help us much
[08:52] <seb128> updating to beta2 to post beta2 feels like distupgrading from oneiric to precise :p
[08:52] <pitti> seb128: I think this upstream commit doesn't really improve matters; there's a reason LSB prescribes UID ranges
[08:52] <pitti> seb128: heh, indeed; and to not small degree your fault :)
[08:52] <seb128> lol
[08:52] <pitti> gnome 3.4 love
[08:52] <seb128> indeed
[08:52] <pitti> but that staging in proposed worked really well
[08:53] <seb128> pitti, I'm pondering trying to argue with upstream over the uid stuff
[08:53] <pitti> not a second of archive breakage, and we could use the builders during freeze
[08:53] <seb128> pitti, indeed!
[08:53]  * pitti looks forward to next week, when Colin's fix will get rolled out
[08:53] <dpm> awesome, thanks mvo. I've added a comment on the bug that the i18n branch needs to be merged before the upload. Also, I've just updated the Catalan translation, but it won't make it until tomorrow's daily export to the branch. Are you planning to do the upload before tomorrow, and if so, may I send you the PO file (or a merge proposal), if it's not too much extra work?
[08:55] <didrocks> pitti: +1 on proposed, I buy definitively it :)
[08:55] <pitti> I just got three HUDs in a row from pressing ctrl+alt+something
[08:55] <pitti> but not reliably
[08:55] <didrocks> pitti: ctrl + alt + which key?
[08:56] <didrocks> pitti: not a key handled by compiz?
[08:56] <pitti> cursor mostly
[08:56] <didrocks> (like no switching ws)
[08:56] <pitti> e. g. ws switch
[08:56] <didrocks> hum
[08:56] <didrocks> I'm always using that :/
[08:56] <pitti> I also got it all the time yesterday when grabbing/ungrabbing keyboard/mouse in kvm
[08:56] <didrocks> didn't get the HUD once since 5.6 :/
[08:57] <didrocks> even now, trying very hard to just type ctrl + alt + left and release in one shot
[08:57] <seb128> yeah, I didn't get it either for like 2 weeks
[08:57] <didrocks> my ws switches
[08:57] <didrocks> but didn't see the hUD
[08:57] <didrocks> HUD*
[08:57] <pitti> yes, if I hammer on them and want to get it, it doesn't appear
[08:57] <pitti> Heisenbug
[08:57] <didrocks> :)
[08:58] <mvo> dpm: I can put the upload on my agenda for monday
[08:59] <dpm> mvo, that would be great, thanks!
[09:00] <mvo> dpm: I put it on my todo
[09:00] <dpm> cool :)
[09:11] <didrocks> seb128: do you know on which version of glib bug #926208 was supposed to be fixed?
[09:11] <ubot2> Launchpad bug 926208 in bamf "bamfdaemon crashed with SIGABRT in g_assertion_message()" [Critical,Fix released] https://launchpad.net/bugs/926208
[09:11] <seb128> didrocks, 2.31.22-0ubuntu1
[09:12]  * didrocks sees that the latest dup is old
[09:12] <didrocks> looking for new crashers in bamf
[09:13] <didrocks> ok, last one was on 2012-03-15
[09:14] <didrocks> so I guess the commenter just got a something else and thought it's the same
[09:16] <seb128> didrocks, or he didn't restart his session for a week and still have the old glib in process or is using an outdated mirror
[09:17] <didrocks> seb128: right, at least, with the crash, he will get a new loaded one :)
[09:26] <tkamppeter> pitti, can you have a look at bug 968890. Ther CUPS seems not to start because the Dialog utility for Debconf does not find the correct terminal size.
[09:26] <ubot2> Launchpad bug 968890 in cups "package cups 1.5.2-8bzr2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1" [Undecided,New] https://launchpad.net/bugs/968890
[09:40] <pitti> tkamppeter: hm, no immediate idea; perhaps the upgrade is ran in a very small terminal?
[09:44] <tkamppeter> pitti, should then be some protection against that done, for example apt-get or dpkg aborting with an error right in the beginning? Or should the Readline version of the Debconf interface be checked so that it actually works?
[09:45] <pitti> debconf could perhaps fallback to a different backend then
[09:45] <pitti> tkamppeter: either way, feel free to reassign to debconf; there's nothing cups specific there
[09:47] <tkamppeter> pitti, thanks, will do.
[09:50] <xclaesse> ahah, I can tell beta2 got released, number of user of the MSN app in GOA jumped from 300 daily to over 400 in one day
[09:55] <tkamppeter> pitti, done.
[09:55] <pitti> didrocks: hm, I get it half of the time when using alt+left/right to switch between channels in weechat, but also if I just do that in a terminal (when it has no particular effect)
[09:56] <didrocks> pitti: oh, maybe you do press an arrows before alt?
[09:57] <pitti> didrocks: I'm pretty sure I don't; but I press arrow very quickly after alt
[09:57] <pitti> didrocks: in all the cases when the HUD popped up, the alt+arrow actually did change teh channel
[09:57] <pitti> when I press alt, wait a bit, press arrow, it works
[09:57] <didrocks> maybe my machine is too slow, but I tried to ping very quickly
[09:57] <pitti> but when I press alt and then arrow very quickly (as I usually do), I get it
[09:58] <pitti> I can now reproduce it 100% of the time
[09:59] <didrocks> seb128: can you try on your machine? ^
[09:59] <pitti> $ xev | grep -A2 ^KeyPress
[09:59] <pitti> KeyPress event, serial 36, synthetic NO, window 0x3800001,
[09:59] <pitti>     root 0xbe, subw 0x0, time 17590219, (112,69), root:(113,867),
[09:59] <pitti>     state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
[09:59] <pitti> --
[09:59] <pitti> KeyPress event, serial 36, synthetic NO, window 0x3800001,
[09:59] <pitti>     root 0xbe, subw 0x0, time 17590299, (112,69), root:(113,867),
[09:59] <pitti>     state 0x8, keycode 113 (keysym 0xff51, Left), same_screen YES,
[09:59] <pitti> didrocks: ^ this proves that I get the correct order
[09:59] <pitti> and I get the HUD
[10:00] <seb128> I can confirm yes
[10:00] <pitti> didrocks: I better stick that into a bug report, I guess?
[10:00] <didrocks> pitti: yes please
[10:00] <didrocks> pitti: I can add it to the priority list
[10:00] <pitti> it doesn't matter which window (or none at all) is focussed
[10:01]  * didrocks definitively doesn't reproduce, even if I fly over the keyboard
[10:02] <JamesTait> didrocks: ping
[10:03] <tkamppeter> pitti, for all these "CUPS does start on upgrade" bugs I would appreciate if you add a section to https://wiki.ubuntu.com/DebuggingPrintingProblems with instructions to investigate the bug and your debug version of the Upstart script for download. Then I can start as with all the other bugs "follow the instructions of section "XXX" on https://wiki.ubuntu.com/DebuggingPrintingProblems".
[10:03] <didrocks> hey JamesTait ;)
[10:03] <didrocks> JamesTait: so, you crash, you can reproduce, nice!
[10:03] <didrocks> JamesTait: can you run please oneconf-query --hosts --direct?
[10:03] <JamesTait> didrocks: For the public record: https://pastebin.canonical.com/63438/
[10:04] <didrocks> (you can use the ubuntu pastebin for it ;))
[10:07] <didrocks> JamesTait: in case you didn't notice ^
[10:07] <JamesTait> didrocks: Good point. ;) http://pastebin.ubuntu.com/906981/
[10:07] <pitti> didrocks: added everythign I know about it to bug 969039
[10:07] <ubot2> Launchpad bug 969039 in unity "HUD appears when pressing Alt+Cursor key" [Undecided,New] https://launchpad.net/bugs/969039
[10:07] <pitti> seb128: ^ if you can reproduce
[10:08] <seb128> pitti, ok, will comment on it
[10:08] <seb128> though I think the only way is to move the hud out of alt, that's being discussed on unity-design
[10:08] <seb128> like I can't reproduce those bugs in "normal" use, you need to be brutal in timing
[10:09] <seb128> I'm not sure they will ever manager to get it good enough for those
[10:10] <pitti> didrocks: oh, https://bugs.launchpad.net/ubuntu/+source/unity/+bug/969039/comments/2
[10:10] <ubot2> Launchpad bug 969039 in unity "HUD appears when pressing Alt+Cursor key" [Undecided,New]
[10:10] <pitti> didrocks: that might explain why you cannot reproduce
[10:11] <didrocks> JamesTait: ok, so you should have a ~/.cache/oneconf directory as well
[10:11] <didrocks> JamesTait: can you please tar it and send it to me? :)
[10:11] <didrocks> (there is no credential in it, just your package list)
[10:11] <didrocks> pitti: oh maybe, would be interesting to play with this settings
[10:12] <didrocks> pitti: it's either that, either my computer is too slow to pick the timing issue with this resolution
[10:12] <didrocks> the only way to show it for me is to press an arrow before alt
[10:12] <didrocks> not in the common case, whatever brutal I am
[10:13] <JamesTait> didrocks: Sure, gimme 2 secs.
[10:13] <didrocks> still weird that any of those settings can impact on your machine
[10:14] <pitti> didrocks: hm, I'm not particularly trying hard to be fast; it's my normal keyboard speed, that's how I get it all the time
[10:14] <pitti> didrocks: but it indeed seems to be due to my settings, I don't get it in a guest session
[10:15] <seb128> pitti, it's still quite brutal compared to what "normal" users do ;-)
[10:15] <didrocks> seb128: are you infering pitti is brutal? :)
[10:15] <pitti> *shrug* my wife doesn't type any slower than I do
[10:15] <seb128> well we probably all use keybindings enough to be snappy on them
[10:15] <seb128> well typing is different from keybindings
[10:15] <pitti> but yes, compared to my mother I do
[10:16] <pitti> but if you use keybindings often enough, they get so deeply into your muscle memory that you are just bound to get very fast with them
[10:16] <seb128> right
[10:16] <pitti> I use alt+cursor and ctrl+alt+cursor hundreds of times every day
[10:16] <JamesTait> didrocks: On its way. :)
[10:16] <seb128> well as said before I think it's pretty much impossible to fix
[10:16] <didrocks> JamesTait: no worry ;)
[10:16] <seb128> they should move hud away from the alt key
[10:17] <pitti> seb128: well, this particular issue should be absolutely fixable, even more so because it doesn't happen in a fresh profile
[10:17] <pitti> there clearly is another X key event between the alt press and release
[10:17] <pitti> but independently of that, I agree to not overloading alt
[10:17] <seb128> pitti, it feels like they are playing wack a mole on alt tapping for a month
[10:17] <pitti> ctrl+space or so seems quite fine
[10:17] <seb128> indeed
[10:18] <pitti> and 3d is at least configurable
[10:18] <pitti> 2d sucks because it's hardwired
[10:18] <seb128> I'm puzzled that it doesn't happen in a fresh profile
[10:19] <pitti> seb128, didrocks: argh, hang on -- just noticed that my guest session is 2d
[10:19] <seb128> but yeah, confirmed, doesn't happen in a guest session, weird
[10:20] <didrocks> ah
[10:20] <didrocks> pitti: support for changing the key will be added to 2D btw
[10:20] <didrocks> (I just discussed it on #ubuntu-unity)
[10:21] <pitti> but I now ran a 3D guest session, and still unreproducible
[10:21] <pitti> gnargh
[10:21] <pitti> didrocks: are all compiz settings in gconf?
[10:21] <pitti> didrocks: i. e. if I were to try unity --reset again, and it goes away, could I restore them by saving my gconf tree? (for debugging this)
[10:21] <pitti> or do we have some ~/.config/compiz whatever stuff?
[10:22] <didrocks> pitti: all compiz settings are in gconf, yeah, but some unity are in gsettings
[10:22] <pitti> ok, I'll try to bisect this
[10:22] <didrocks> and for those I wanted to be shared between 2D and 3D, they put it into gconf to avoid sharing it
[10:22]  * didrocks sighs
[10:23] <pitti> I'll see how to make it reproducible from a fresh profile, and what triggers it
[10:23] <didrocks> thanks pitti!
[10:23] <pitti> this annoys me enough to warrant spending some time on it
[10:24] <pitti> finishing up that apport upload first, though
[10:24] <didrocks> yeah, especially I wasn't aware about that one
[10:26] <didrocks> JamesTait: ah, I think I know what happened and how you ended up in that situation :)
[10:26] <didrocks> JamesTait: at least, the crash makes perfect sense to me now :)
[10:26] <JamesTait> didrocks: That's good. :)
[10:26] <didrocks> JamesTait: I know how to unstuck you, but I would appreciate you keep the broken state to confirm the fix
[10:26] <didrocks> (in addition to my incoming test case ;))
[10:27] <JamesTait> didrocks: Not a problem. :)
[10:27] <didrocks> JamesTait: ok, will work on it ASAP (when the world will be a little bit quieter ;))
[10:28] <didrocks> JamesTait: thanks again for the debugging info :)
[10:28] <JamesTait> didrocks: You're welcome. Ping me if you need anything else!
[10:28] <didrocks> will do!
[10:29] <seb128> pitti, random bet but reading your config and looking at mine, it could happen when putting some wm action binded with an alt combinaison
[10:30] <seb128> pitti, I use alt-& to go to ws1
[10:30] <seb128> pitti, well you put alt-b
[10:30] <pitti> ah, so I'll try to bind alt+b in the guest session and see whether it happens then
[10:30] <seb128> well->where
[10:32] <pitti> hm, that's not it alone, unless it depends on restarting unity
[10:32] <pitti> hm, why does the guest session default to 2D..
[10:36] <didrocks> pitti: it happens in the past due to apparmor preventing reading /etc/compizconfig/profile
[10:36] <didrocks> happened*
[10:36] <pitti> user-session=ubuntu-2d
[10:36] <pitti> sorry, my fault; leftover from some ubuntu-defaults-builder experiments
[10:37] <popey> bug 969044
[10:37] <ubot2> Launchpad bug 969044 in ubiquity ""try ubuntu" button launches unity 3d when orca is running" [Undecided,New] https://launchpad.net/bugs/969044
[10:37] <popey> if we have orca loaded, we shouldn't be logging people with a11y requirements in to unity, but unity 2d?
[10:38] <popey> (on the CD)
[10:38] <pitti> I'm not very up to date on that TBH; we used to in the past, but it appears 3D got a lot more accessible
[10:38] <pitti> so is that still necessary then?
[10:39] <pitti> then again, users of orca won't have much to enjoy from 3D anyway
[10:39] <popey> 3d is not accessible
[10:39] <popey> AIUI 2D is the focus for a11y work, so we "recommend" people with a11y requirements use 2d
[10:44] <didrocks> popey: if you select the accessibility session at startup (before even ubiquity)
[10:44] <didrocks> popey: it doesn't start 2D?
[10:44] <popey> apparently not, Alan Bell (who filed the bug) told me this in the pub so i asked him to check it today and file a bug
[10:44] <didrocks> pitti: as popey told, 3d had no work on accessibility this cycle
[10:44] <popey> hence bug 959044
[10:44] <popey> er
[10:44] <popey> 969044
[10:45] <pitti> didrocks: just to confirm, launcher staying with the shortcut numbers selected when I press super+something is the one that's already fixed in trunk, right?
[10:45] <didrocks> popey: the bug isn't clear enough
[10:45] <didrocks> popey: it doesn't say if orca was starting after ubiquity was showing its first page
[10:46] <popey> I'll test and confirm
[10:46] <pitti> didrocks: (or alternatively, the help staying around indefinitely)
[10:46] <didrocks> popey: or if the accessibility was turned even before ubiquity starts (like if you press enter at the very beginning in the boot and choose a11y)
[10:46] <didrocks> popey: thanks
[10:46] <didrocks> pitti: right
[10:47] <didrocks> pitti: there will be soon a compiz version available in the ppa (I think today won't again be the OneConf day :()
[11:30] <popey> didrocks / pitti updated bug 969044 - it does indeed start Unity 3d, not 2d when you enable the accessibility screen reader, which does seem like a regression
[11:30] <ubot2> Launchpad bug 969044 in ubiquity ""try ubuntu" button launches unity 3d when orca is running" [Undecided,Confirmed] https://launchpad.net/bugs/969044
[11:30] <popey> ubuntu 11.10 worked.
[11:30] <popey> (worked as in, started 2d)
[11:32] <didrocks> popey: I worked on that at the time, but it should really be assigned/talked to TheMuso
[11:32] <didrocks> popey: thanks for the feedback :)
[11:33] <didrocks> pitti: maybe something to track on your list? ^ not sure if the settings I did in the natty/oneiric time has been reverted
[11:34] <pitti> didrocks: sure, tagged; is that actually in ubiquity, or does that need some magic to adjust the default session?
[11:34] <didrocks> pitti: not ubiquity, it's in casper
[11:34] <popey> thanks
[11:35] <pitti> didrocks: ah, I'll have a look then
[11:35] <ritz> seb128, heya, if I understand correctly, we have lp:gtk upstream tree. and lp:~ubuntu-desktop/gtk/ubuntugtk3 with the basic patches/diff to build from this upstream tree for precise . Is this correct ?
[11:35] <pitti> didrocks: i. e. casper should check if orca is enabled, and adjust the default session to 2d?
[11:35] <didrocks> pitti: I can maybe have a look, not sure today though
[11:35] <didrocks> pitti: exactly
[11:35] <didrocks> let me dig to my changes
[11:35] <seb128> ritz, correct
[11:35] <pitti> didrocks: thanks, I'll figure it out
[11:35] <pitti> didrocks: just wanted to confirm how it should work
[11:36]  * pitti toddles off for lunch, bbl
[11:36] <ritz> seb128, sweet, thanks :)
[11:36] <seb128> yw
[11:37] <didrocks> pitti: IIRC, I used at the time the gdm-set-default-session that I rewrote as lightm-set-defaults (you have a session switch) in Oneiric
[11:42] <popey> hmm, if I press super + left arrow, my window sticks to the left edge of the screen, and then the popup shortcuts keys thing appears and stays on screen even after i let go of super.. anyone else reproduce this?
[11:42] <popey> I have to press super again to make it go away
[11:43] <seb128> popey, -> #ubuntu-unity for unity issues
[11:43] <popey> ah sorry
[11:43] <seb128> no worry
[11:43] <seb128> but upstreams are not on #ubuntu-desktop ;-)
[11:43] <popey> haha
[11:43] <popey> riiiiiight ☺
[12:29] <pitti> seb128, popey: that's already fixed upstreamn
[12:29] <pitti> I get that as well, it's what I asked didrocks about a few hours ago
[12:29] <seb128> pitti, ok
[12:29] <didrocks> pitti: btw, a compiz is building in the ppa:unity-team/staging
[12:30] <didrocks> the workaround-less compiz fixing this issue as well ^
[12:31] <didrocks> (and it indeed fixed it for me)
[12:32] <seb128> didrocks, is there an abi change?
[12:32] <didrocks> seb128: not this time
[12:33] <didrocks> so we can even party ;)
[12:35] <seb128> didrocks, good, maybe put it on in the desktop ppa as well?
[12:35] <seb128> didrocks, for those who want to try the stable compiz without jumping on staging unity
[12:36] <desrt> rawr
[12:36] <smspillaz> rwar >
[12:36] <smspillaz> ?
[12:36] <desrt> smspillaz: hey.  you're back!
[12:36] <didrocks> seb128: why not :)
[12:37] <smspillaz> desrt: been back for two weeks now
[12:37] <desrt> haven't seen you around much
[12:37] <desrt> probably been too busy working ;)
[12:37] <Sweetshark> pitti: building source package
[12:39] <Sweetshark> pitti: arrgh, should that be -v1:3.5.1-1ubuntu2 or ubuntu3 when ubuntu3 was a failed build in proposed?
[12:40] <desrt> seb128: so that issue you hit yesterday was a bug in the hud algorithm
[12:40] <desrt> seb128: we didn't notice it before because it was covered by another bug
[12:41] <pitti> Sweetshark: doesn't matter much; but use -v1:3.5.1-1ubuntu1 to be truly correct
[12:41] <pitti> Sweetshark: i. e. the current version in precise
[12:41] <Sweetshark> pitti: k
[12:42] <seb128> desrt, the dropping the pre scoring to 1 screwing the results?
[12:42] <seb128> desrt, hey btw
[12:42] <desrt> seb128: ya
[12:42] <desrt> seb128: i have a new algorithm mostly-done now
[12:44] <desrt> the old one was too hard to make sense of :p
[12:44] <seb128> desrt, not sure if I ;-) or :-( that
[12:45] <desrt> i think it's mostly a good thing
[12:45] <desrt> i'm going to spend the morning writing tests
[12:49] <xclaesse> is gnome-online-accounts 3.4.0 build with --enable-facebook ?
[12:52] <xclaesse> seems it is noto
[12:52] <xclaesse> FYI, fedora activated it
[12:52] <xclaesse> I think ubuntu should too
[12:58] <jpds> xclaesse: Sounds like a wishlist bug.
[13:05] <seb128> xclaesse, didn't kenvandine has reservations about this? especially that you said that GNOME was checking on legal for it?
[13:05] <Sweetshark> pitti: new package is on chinstrap
[13:05] <seb128> xclaesse, in any case we don't use gnome online account in Ubuntu by default so it's not going to make a real difference
[13:07] <desrt> seb128: initial testing shows the new algorithm to be somewhere between 4 and 10 times faster
[13:08] <desrt> ie: query that used to take ~20ms on my box is now taking ~3ms
[13:09] <xclaesse> seb128, yes GNOME is "checking" legal... waiting 3months for a lawyer to flip a coin to say yes or no with a probability of 50% to be wrong anyway.
[13:09] <pitti> Sweetshark: and now it's in precise, too; thanks!
[13:09] <jpds> xclaesse: Better safe than sorry.
[13:10] <Sweetshark> pitti: awesome, thanks
[13:10] <xclaesse> jpds, no need of a lawyer to be sure that if facebook wants to find a flaw they always can. terms are written for that
[13:11] <seb128> desrt, without any functionality drop?
[13:12] <desrt> seb128: currently i lost the highlighting again
[13:12] <desrt> seb128: will bring it back soon :)
[13:12] <desrt> that's not on the 'critical path' in any case, so bringing it back won't add anything
[13:13] <desrt> about functionality losses: adjusted pre-drop penalty is gone (and i think i convinced myself it never worked properly in the first place)
[13:14] <desrt> as we discussed yesterday it was probably better to get rid of that anyway
[13:15] <desrt> so now top 3 results for "pre" in firefox are "print PREview" "restore PREvious session" and "PREferences"
[13:15] <desrt> ie: matches at starts of words are now greatly emphasised
[13:19] <desrt> it seems to improve the ability to type "f s p a" to mean "file > save page as"
[13:19] <desrt> which is kinda nice
[13:24] <seb128> desrt, can you style typo something? i.e do you still have a distance based calculation?
[13:24] <seb128> desrt, i.e prefre matchs preferences?
[13:24] <desrt> seb128: yes.  the core algorithm is basically the same
[13:25] <desrt> if i removed that capability, i'd like to think i could have done more than 10x improvement :)
[13:25] <pitti> seb128: I'm about to upload glib now; any objections, or do you still have stuff?
[13:25] <pitti> seb128: I merged with Debian, to also get the multiarch bug fix
[13:26] <pitti> seb128: nice to see that all our remaining delta is only for 12.04 stuff :)
[13:26] <seb128> pitti, nice! no, the only stuff I had to my list was the multiarch fix that debian added, if you merged we will get it
[13:26] <seb128> pitti, thanks for working on that ;-)
[13:26] <pitti> great
[13:27] <pitti> seb128: sorry, you already worked on that?
[13:27] <seb128> pitti, oh, remaining delta, make sure you don't do the postinst one again
[13:27] <pitti> hrw mentioned it a few hours ago, and I didn't see you respond
[13:27] <seb128> pitti, no, it was on my "tagged emails to look at before precise", ie. my queue
[13:27] <pitti> seb128: "the postinst one"?
[13:28] <seb128> pitti, I didn't start don't worry, I just had that noted as "needs to be fixed by somebody for precise"
[13:28] <seb128> pitti, so good that you got to it ;-)
[13:28] <pitti> seb128: I kept the libzeitgeist-io conflicts and the /etc/etc/bash_completion.d/ removal
[13:28] <seb128> pitti, wait
[13:28] <pitti> (i. e. the -bin maintscript and postinst)
[13:29] <seb128> pitti,
[13:29] <seb128> --- glib2.0-2.31.4.tested/debian/libglib2.0-0.postrm.in	2011-12-13 22:15:40.000000000 +0000
[13:29] <seb128> +++ glib2.0-2.31.6/debian/libglib2.0-0.postrm.in	2012-01-03 17:28:37.000000000 +0000
[13:29] <seb128> @@ -14,7 +14,7 @@
[13:29] <seb128>      rmdir -p --ignore-fail-on-non-empty /usr/lib/gio/modules
[13:29] <seb128>  fi
[13:29] <seb128>
[13:29] <seb128> -if [ -d /usr/share/glib-2.0/schemas ]; then
[13:29] <seb128> +if [ "$1" = purge ] && [ -d /usr/share/glib-2.0/schemas ]; then
[13:29] <seb128>
[13:29] <seb128> pitti, please make sure you don't drop that diff
[13:29] <seb128> pitti, you dropped it once before in the previous merge and it breaks the world ;-)
[13:29]  * pitti looks for the corresponding bug, to commit it to Debian
[13:30] <seb128> pitti, not sure there is a bug, it's just "if you delete the mmap on upgrade you get no schemas installed and all applications aborting during that timeframe"
[13:30] <pitti> ah, right
[13:30] <seb128> pitti, it's something which leaded to quite some gsettings abort bugs
[13:30] <seb128> pitti, the mmap update is safe, no need to delete it, the update will replace it
[13:33] <pitti>   * debian/libglib2.0-0.postrm.in: Only remove the compiled schemas on purge,
[13:33] <pitti>     not during upgrades. Otherwise we loose the cache if there is no other
[13:33] <pitti>     package during the upgrade that installs a schema and thus calls our
[13:33] <pitti>     trigger to rebuild it.
[13:33] <pitti> seb128: ^ does that sound about right?
[13:33] <pitti> (for the Debian commit)
[13:34] <seb128> pitti, I'm not sure about the second part the Otherwise...
[13:35] <seb128> pitti, but for sure "Otherwise we have no schemas available during the time the postrm from $olversion is run and the postinst of $newversion is run which leads to softwares to abort on missing schemas"
[13:35] <pitti> ah, right
[13:36] <dobey> anyone seen anything like bug #969209 ?
[13:36] <ubot2> Launchpad bug 969209 in gtk+3.0 "Missing expander arrows in some tree views" [Undecided,Confirmed] https://launchpad.net/bugs/969209
[13:36] <seb128> dobey, yeah, should be fixed with http://fpaste.org/oHnp/
[13:37] <pitti> seb128: cheers
[13:37] <seb128> dobey, ups, that expired
[13:37] <seb128> pitti, yw, thanks for getting it in Debian ;-) I mentioned it to mbiebl some weeks ago but he said he would ask Josselin and never commented back
[13:37] <seb128> dobey, https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/963243
[13:37] <ubot2> Launchpad bug 963243 in gtk+3.0 "Cannot display passwords in keyrings (dup-of: 963862)" [Low,Confirmed]
[13:37] <ubot2> Launchpad bug 963862 in gtk+3.0 "The keyring "login" doesn't display any keys or saved passwords." [High,In progress]
[13:38] <dobey> seb128: ah is that uploaded yet?
[13:39] <seb128> dobey, http://pastebin.ubuntu.com/907217/
[13:39] <seb128> dobey, if you want the diff
[13:39] <seb128> dobey, no, I was sort of waiting for Company to commit it to git upstream, but it's on my list for today
[13:40] <dobey> ok, i'll wait then.
[13:40] <dobey> thanks
[13:40] <seb128> dobey, Company doesn't seem to be around, I just wanted to check with him before uploading
[13:40] <seb128> dobey, yw
[13:40] <seb128> dobey, I closed your bug as dup btw ;-)
[13:41] <dobey> sure. if evolution is still weird after that fix goes in, i'll file a new bug against evo for that part
[13:41] <seb128> dobey, thanks, I confirmed it fixes the seahorse case
[13:42] <dobey> right, evo is behaving a bit differently, so i'm not sure if it's the same bug, but it's close enough for a mention :)
[13:42] <seb128> dobey, do you get your expander if you change theme?
[13:43] <dobey> not in evolution
[13:43] <seb128> dobey, that's enough to trigger a refresh and fix it in seahorse
[13:43] <seb128> ok, so maybe different bugs indeed
[13:43] <dobey> yep. will see after this fix lands :)
[13:52] <pitti> seb128: I tried for a while to synthesize the crash in bug 899757
[13:52] <ubot2> Launchpad bug 899757 in udisks "udisks-daemon assertion error: HACK: Wanting to register object at path `%s' but there is already an object there." [Medium,Incomplete] https://launchpad.net/bugs/899757
[13:52] <pitti> seb128: do you remember what you did exactly when it crashed? plugging in the device and it bounced a few times?
[13:53] <pitti> seb128: your log has dozens of adds and remove, I wonder if these were from 20 tries, or a single plugin which bounces like hell
[13:53] <seb128> pitti, I played with the ipod connector contacts to make it mount unmount in serie
[13:53]  * pitti curses at udisks log to not have timestamps
[13:53] <seb128> pitti, i.e just stress test to triger the bug
[13:54] <pitti> seb128: ah, so plugin, pull out, plugin, pull out in rapid succession?
[13:54] <davmor2> seb128: just checking before I try did you resolve the music player issue from yesterday?
[13:54] <seb128> pitti, the first time I got it I was plugging and unplugging the ipod and a sd card to debug gsd
[13:54] <pitti> davmor2: yes, sohuld be fixed in current precise
[13:54] <seb128> davmor2, yes
[13:54] <seb128> pitti, right, the log is from a purelly stresscase non normal use to get the log
[13:54] <seb128> pitti, so yes, unplug,plug several time by seconds
[13:55] <pitti> seb128: thanks
[13:55] <seb128> yw
[13:55] <davmor2> seb128, pitti: Yay works here :)
[13:56] <bcurtiswx> banshee as my default music player, using the music lens, searching 'adele' and clicking on her '21' album should in theory bring me to the ubuntu music store on banshee, correct?
[13:56] <vibhavp> yeah
[13:57] <vibhavp> If adele is present on the Ubuntu One Music Store
[13:57] <pitti> I'm pretty sure it is, I bought that album a few weeks ago from 7digital
[13:57] <bcurtiswx> i verified beforehand that adele and album 21 are in fact in htere
[13:57] <bcurtiswx> there*
[13:57] <bcurtiswx> so I got to the point where banshee was loaded, but there's no music store showing up in banshee
[13:58] <pitti> seb128: hm, I inserted and pulled my poor USB stick about 50 times, with varying timings, and didn't get it; bah
[13:58] <pitti> bcurtiswx: yes, there is no UbuntuOne music store for banshee any more
[13:59] <bcurtiswx> pitti, OK, then IMO rhythmbox should open in that use case, correct?
[13:59] <chrisccoulson> w00t, goodbye ugly flicker in firefox history menu
[13:59] <pitti> bcurtiswx: yes, I guess so
[14:01] <pitti> bcurtiswx: if it's any consolation, if I try it here I just get {"error": "bad or missing url"} in RB
[14:01] <pitti> dobey: ^
[14:01] <pitti> i. e. when I just click on "ubuntu one" in RB
[14:02] <seb128> pitti, well playing with the connector is higher timing that plugin and unpluging, I can play with the contact directly
[14:02] <seb128> pitti, I might have got the first one when jungling with the 2 devices
[14:02] <pitti> seb128: ah, you keep the power on, but not the data lines?
[14:03] <pitti> seb128: I so blame Apple for this bug !!!111!!!one
[14:03] <seb128> pitti, I don't know, I play with the dock contacts, what happens with the flacky connections...
[14:03] <dobey> eh?
[14:03] <dobey> bcurtiswx: there is no u1 music store in banshee on precise
[14:03] <bcurtiswx> pitti, dobey: also if that lens is used and an album is clicked on and the user doesn't have rhythmbox-ubuntuone installed it should request the user to install it (if it's not supposed to be installed by default)
[14:03] <dobey> bcurtiswx: it is installed by default
[14:04] <dobey> or it is supposed to be
[14:04] <bcurtiswx> dobey, OK. So is there a way to inform the user that they can't check out albums if it's not installed (like i had it occur) ?
[14:05] <kenvandine> hey bcurtiswx
[14:05] <dobey> i don't think so
[14:05] <bcurtiswx> kenvandine, hey :)
[14:05] <dobey> bcurtiswx: i guess whatever provides the store scope needs to Depends on it
[14:06] <bcurtiswx> dobey, whatever works best for the time you all have left :)
[14:07] <pitti> does the U1 ms in RB work for anyone in current precise?
[14:08] <bcurtiswx> pitti, i just installd rhythmbox-ubuntuone and upon rhythmbox restart and clicking the store it worked fine with no errors
[14:08] <dobey> pitti: i don't have any problems
[14:09] <bcurtiswx> use case: closing rhythmbox and clicking on adele's 21 album from the music lens I get: "Error while getting credentials:
[14:09] <bcurtiswx> The '/org/freedesktop/secrets/collection/login/24' object does not exist"
[14:09] <dobey> ah crap
[14:09] <dobey> that *is* a bug, which i thought was fixed, but alas :(
[14:10] <dobey> bcurtiswx: what veresions of rhythmbox-ubuntuone and libubuntuoneui-3.0-1?
[14:11] <bcurtiswx> both 2.99.91-0ubuntu1
[14:11] <dobey> sigh
[14:11] <dobey> bcurtiswx: can you file a bug please?
[14:12] <bcurtiswx> dobey, yes with the error from above?
[14:12] <dobey> yes
[14:12] <bcurtiswx> dobey, would you like me to assign it to you?
[14:12] <dobey> sure
[14:12] <bcurtiswx> OK,  brb
[14:12] <dobey> unless you want to fix it :)
[14:13] <bcurtiswx> dobey, file against rhythmbox?
[14:13] <dobey> also, a bug about the lens being odd when rhythmbox-ubuntuone isn't installed
[14:13] <dobey> bcurtiswx: libubuntuone for that object does not exist error
[14:14] <bcurtiswx> and the lens for rhythmbox-ubuntuone?
[14:16] <dobey> unity-scope-musicstores
[14:17] <bcurtiswx> dobey, thx
[14:18] <didrocks> and a new request bug #969235
[14:18] <ubot2> Launchpad bug 969235 in unity "Keyboard shortcuts - Update some window management shortcuts to use "Ctrl + Super" instead of just "Super" " [Undecided,Confirmed] https://launchpad.net/bugs/969235
[14:19] <didrocks> pitti: not sure if you need a FFe for this one ^ at least, we should ping the documentation team
[14:19] <pitti> didrocks: yeah, and translations, too
[14:20] <didrocks> right
[14:20] <didrocks> I asked design to do the paperwork, quite tired to achieve it :)
[14:20] <didrocks> and that push to more and more changes
[14:20] <didrocks> so let's wait for them doing it
[14:21] <seb128> didrocks, with the same rational maybe they can come with ctrl-alt tapping for the hud ;-)
[14:22] <didrocks> seb128: ahah, from what I heard… no for now :(
[14:22] <didrocks> but maybe the change to ask for it? ;)
[14:23] <didrocks> at least, now we have bug #969256
[14:23] <ubot2> Launchpad bug 969256 in unity "Keyboard shortcuts - The HUD keyboard shortcut should be configurable" [Undecided,Confirmed] https://launchpad.net/bugs/969256
[14:23] <didrocks> the translation team has been warned
[14:23] <didrocks> I need some compiz work though to expose the key in ccsm
[14:23] <didrocks> oupss, I meant, in g-c-c
[14:23] <didrocks> and unity-2d needs now to read gconf keys
[14:23] <didrocks> which was removed from it IIRC
[14:24] <rickspencer3> didrocks, someone told me that if you change the HUD from using the ALT key, it breaks ALT for other things in Unity, is this the case?
[14:24] <seb128> desrt, I wonder if bug #968898 is a side effect of your patch
[14:24] <ubot2> Launchpad bug 968898 in gnome-settings-daemon "background picture not cached" [Undecided,Confirmed] https://launchpad.net/bugs/968898
[14:24] <didrocks> rickspencer3: was the case pre-5.8
[14:24] <rickspencer3> didrocks, I like the sound of that!
[14:24] <desrt> seb128: yes.  it is.
[14:24] <desrt> seb128: directly caused by my changes, in fact
[14:24] <didrocks> rickspencer3: heh, how to end better the week, isn't it? :)
[14:25] <desrt> seb128: so you have a choice to make, really...
[14:25] <chrisccoulson> kenvandine, oh, i didn't touch my toes ;)
[14:25] <desrt> do you want to make copies of local files or not?
[14:25] <chrisccoulson> i did do this though: http://bazaar.launchpad.net/~extension-hackers/globalmenu-extension/trunk/revision/314
[14:25] <rickspencer3> didrocks, well, it was as tough week, but the feedback I am reading about the beta is quite nice
[14:25] <kenvandine> chrisccoulson hehe :)
[14:25] <desrt> if you don't make copies and someone erases the original then you get this bug
[14:25] <desrt> if you do make copies, you cause the UI to be ugly and cause lightdm to break
[14:25] <kenvandine> chrisccoulson, your awesome dbusmenu speedup was in yesterday's upload!
[14:25] <chrisccoulson> excellent :)
[14:26] <desrt> GG CC
[14:26] <seb128> desrt, I'm still trying to understand the practical issue in that bug
[14:26] <bcurtiswx> dobey, bug #969262
[14:26] <ubot2> Launchpad bug 969262 in libubuntuone "Error while getting credentials: The '/org/freedesktop/secrets/collection/login/24' object does not exist" [Undecided,New] https://launchpad.net/bugs/969262
[14:26] <seb128> desrt, in practice I would say "don't delete an image you use"
[14:26] <desrt> seb128: so would i
[14:26] <desrt> seb128: but people expect that they can do that because the old behaviour is that a copy was made
[14:26] <seb128> desrt, I will comment on the bug thanks
[14:26] <bcurtiswx> i tried 'ubuntu-bug libubuntuone' but it said package did not exist what was I doing wrong there?
[14:27] <dobey> bcurtiswx: ubuntu-bug only accepts binary packages as package names it seems
[14:27] <dobey> bcurtiswx: so would have been libubuntuone-3.0-1
[14:27] <bcurtiswx> dobey, OK. I'll keep that in mind. Thx :) onto the second bug
[14:29] <mdeslaur> seb128: I don't believe a typical user can associate their wallpaper with a particular file. Maybe it should get copied, but to a public location?
[14:29] <mdeslaur> meh
[14:30] <seb128> mdeslaur, what do you mean "can't associate with a particular file"?
[14:30] <seb128> mdeslaur, if you click on a file and select "set as wallpaper" you probably know on what file you clicked?
[14:30] <seb128> mdeslaur, give users some credit ;-)
[14:30] <mdeslaur> seb128: saying "this file should be my wallpaper". But then later being able to realize that the file you're deleting is the one you've set as your wallpaper
[14:30] <dobey> doesn't gnome make a copy in ~/.local/share/?
[14:31] <mdeslaur> seb128: it's a file management association typically understood by power users
[14:31] <seb128> dobey, no, it used to copy to .cache by desrt changed that because it breaks stuff, the path of the image is weird in the capplet for example
[14:32] <seb128> mdeslaur, well same as if you delete your a lettre you wrote in word and try to open it later... I mean if you delete stuff you are using too bad for you
[14:32] <chrisccoulson> kenvandine, that change i've just done should also speed up the HUD for firefox too, as the menu structure no longer changes unnecessarily :)
[14:32] <dobey> oh, i guess they broke the xml awesomeness for gnome 3.0
[14:32] <dobey> so it only reads xml now
[14:36] <bcurtiswx> dobey, bug #969271
[14:36] <ubot2> Launchpad bug 969271 in unity-lens-music "Clicking an album should bring up only rhythmbox and make sure that rhythmbox-ubuntuone is installed" [Undecided,New] https://launchpad.net/bugs/969271
[14:37] <dobey> didrocks: ^^ want an easy bug for your kill count?
[14:39] <dobey> didrocks: need to make unity-scope-musicstores Depends on rhythmbox-ubuntuone
[14:40] <didrocks> dobey: hum, but it still has the banshee logic as well
[14:40] <didrocks> isn't it?
[14:40] <dobey> didrocks: no. well there's no u1 store in banshee in precise
[14:41] <didrocks> dobey: ok in this case
[14:42] <bcurtiswx> I can't reproduce having banshee as default and the lens opening banshee, so <shrugs> ignroe that part of it for now
[14:44] <dobey> bcurtiswx: i suspect that probably happens in 11.10 as well, if you remove the u1 extension
[14:44] <bcurtiswx> hmm, lemme try removing the extension and see if banshee loads
[14:45] <bcurtiswx> dobey, yes banshee loads in that case
[14:45] <dobey> bcurtiswx: also, what cpu, and how much RAM does your computer have? and how many songs are in your regular music library, and how many songs are in your u1ms library?
[14:47] <bcurtiswx> want me to add that to the lens bug ?
[14:49] <bcurtiswx> dobey, AMD Turion X2, 4GB RAM
[14:49] <dobey> no. asking in reference to your other bug
[14:49] <dobey> it's a race condition
[14:50] <dobey> i thought i fixed it, but apparently only made it harder to hit
[14:52] <pitti> seb128: hm, do you still have time to try something with the ipod? I can't make head or tail of it; your udisks debug log is clearly missing a remove event, and I wonder where that's (not) coming from
[14:53] <seb128> pitti, sure
[14:54] <bcurtiswx> dobey, 559 regular songs and 2 albums in my u1ms (30 songs)
[14:54] <pitti> seb128: so in short, I need an udisks output again, plus a parallel run of udevadm monitor -e --udev 2>&1 | tee /tmp/udev.log
[14:54] <pitti> seb128: and at the end, a stack trace of that udisks crash
[14:54] <pitti> seb128: (doesn't need to be particularly symbolic, if I can see the rough path it crashes in, that's enough)
[14:54] <pitti> seb128: so udisks-dbgsym and libglib2.0-dbg ought to suffice
[14:55] <dobey> bcurtiswx: ok, thanks
[14:55] <pitti> seb128: beacuse the stack trace from the original reporter doesn't look like it's matching your udisks debug log
[14:55] <bcurtiswx> dobey, yw. Off to a seminar, bbl :)
[14:56] <pitti> seb128: I get the crash if I disable a particular piece of code in udisks, which is meant to prevent that very thing
[14:58] <seb128> pitti, http://pastebin.ubuntu.com/907325/
[14:58] <seb128> pitti, that's the stracktrace from yesterday
[14:58] <seb128> pitti, from the .crash
[14:58] <seb128> pitti, will try to get the logs now
[14:59] <pitti> seb128: corresponding to https://launchpadlibrarian.net/98880792/udisks.log ?
[14:59] <pitti> seb128: cheers
[14:59] <seb128> pitti, yes
[14:59] <pitti> ok, that matches pretty well then after all
[15:00] <dobey> thanks didrocks
[15:01] <didrocks> dobey: yw, thanks for the head's up :)
[15:03] <seb128> pitti, http://people.canonical.com/~seb128/udev.log
[15:03] <seb128> pitti, http://people.canonical.com/~seb128/udisks.log
[15:04] <pitti> seb128: splendid, thanks!
[15:04] <seb128> pitti, yw
[15:06] <seb128> pitti, http://pastebin.ubuntu.com/907337/
[15:06] <seb128> pitti, that's the corresponding stacktrace
[15:06]  * pitti hugs seb18
[15:06]  * pitti hugs seb128, too
[15:06] <pitti> and any other seb!
[15:06]  * seb128 hugs pitti back ;-)
[15:15] <seb128> pitti, https://launchpadlibrarian.net/99017695/fix-lp899858.patch ... +1 0 -1?
[15:16] <pitti> seb128: LGTM, if it works :)
[15:16] <seb128> pitti, seems to work for the oem guys, I don't feel adventurous on a friday evening to upload but I will give it a try on monday and upload if that works there
[15:16] <seb128> here
[15:25] <mterry> tremolux, filing all sorts of USC bugs for ya
[15:30] <pitti> seb128: that udev.log was tremendously helpful indeed
[15:30] <seb128> pitti, oh great, what weird is happening?
[15:30] <pitti> UDEV  [26112.087644] change   /sdb (block)
[15:31] <pitti> DEVNAME=/dev/sdb
[15:31] <pitti> DEVPATH=/sdb
[15:31] <pitti> this is utter bogus
[15:31] <seb128> pitti, seems weird indeed
[15:31] <pitti> device paths shoudl be something like
[15:31] <seb128> pitti, udev bog then?
[15:31] <pitti> UDEV  [26101.941079] change   /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/host25/target25:0:0/25:0:0:0/block/sdb (block)
[15:31] <pitti> kernel bug, yes (udev is just the messenger)
[15:31] <pitti> that looks like an event from the in-kernel media polling
[15:32] <pitti> seb128: can you please check something while the ipod is plugged in?
[15:32] <seb128> pitti, sure
[15:32] <pitti> ps aux|grep udisks.*polling
[15:32] <seb128> $ ps aux|grep udisks.*polling
[15:32] <seb128> root     25904  0.0  0.0   6552   728 ?        S    17:04   0:00 udisks-daemon: polling /dev/sdb /dev/sr0
[15:32] <seb128> pitti, ^
[15:33] <pitti> oha
[15:33] <pitti> seb128: are you running udev 175-0ubuntu8 ?
[15:33] <seb128> ii  udev                                         175-0ubuntu6                                   rule-based device node and kernel event manager
[15:33] <pitti> aah
[15:34] <pitti> seb128: would you be able to update udev, pull out the ipod, plug it in again, and check that ps aux|grep again?
[15:34] <seb128> pitti, do I need to restart udev,the box?
[15:34] <pitti> seb128: udev restarts itself, no reboot necessary
[15:34] <pitti> you just need to disconnect and reconnect the device
[15:34] <seb128> root     25904  0.0  0.0   6552   728 ?        S    17:04   0:00 udisks-daemon: polling /dev/sr0
[15:34] <pitti> the wonderful world of hotplugging
[15:34] <seb128> pitti, ^
[15:35] <pitti> hm, why the heck is it still polling the CD
[15:35] <pitti> but that's a separate bug
[15:35] <pitti> seb128: do you still get the crash now?
[15:36] <seb128> (udisks-daemon:5424): udisks-daemon-ERROR **: **** HACK: Wanting to register object at path `/org/freedesktop/UDisks/devices/sdb' but there is already an object there. This is an internal error in the daemon. Aborting.
[15:36] <seb128> pitti, yes
[15:36] <pitti> seb128: thanks; any chance you could get me an udev log for this?
[15:36] <pitti> I want to compare the bogus change event
[15:37] <pitti> in any case, I have a slightly better idea now what happens
[15:38] <seb128> pitti, http://people.canonical.com/~seb128/udevbis.log
[15:38] <pitti> seb128: oh, as for polling sr0, I bet/hope that will be gone after a reboot (you didn't dis/reconnect the CD drive)
[15:38] <seb128> pitti, in fact I don't have to tweak the cable so much, just doing normal plug,unplug with some seconds between leads to that
[15:38] <pitti> UDEV  [28238.049733] change   /sdb (block)
[15:38] <pitti> ok, same thing
[15:39] <seb128> pitti, but the ipod has a few seconds or "connecting" with the logo spinning on screen
[15:39] <pitti> seb128: thanks!
[15:39] <seb128> so I'm not sure how those devices work
[15:39] <seb128> pitti, yw
[15:40] <pitti> seb128: so you don't need to be particularly fast, right?
[15:41] <seb128> pitti, no, not crazy fast
[15:41] <pitti> in fact, it shoudln't even happen when you do it "crazy fast"
[15:41] <seb128> pitti, like plug it, wait a second, unplug, wait a second, plug
[15:41] <pitti> as the polling is only done every two seconds
[15:41] <seb128> do that a few times
[15:41] <pitti> right, until the polling kicks in
[15:57] <tremolux> mterry: rock on!! thanks MT  :D
[15:58] <pitti> seb128: ah, you run i386, right?
[15:58] <pitti> seb128: if I toss you a small udisks patch, could you build a package?
[15:58] <seb128> pitti, yes, i386, sure
[15:59] <pitti> seb128: http://people.canonical.com/~pitti/tmp/udisks.debug.patch
[15:59] <pitti> seb128: I bet I know what this will show, but I'd rather confirm
[15:59] <pitti> seb128: I just need the udisks log this time, no crash report or udev log
[16:01] <seb128> pitti, building
[16:04] <seb128> pitti, http://pastebin.ubuntu.com/907438/
[16:04] <seb128> pitti, tail of the log
[16:05] <pitti> **** UPDATING /sys/sdb
[16:05] <pitti> **** registering /org/freedesktop/UDisks/devices/sdb
[16:05] <pitti> hah
[16:06] <pitti> seb128: merci beaucoup; I can't reproduce it yet, but now at least I know exactly what happens and what goes wrong
[16:07] <pitti> I can fix it, but I really want to find a way to synthesize it to add it to the tests, so that udisks2 etc. won't have the same problem all over again
[16:07] <seb128> pitti, yw
[16:07] <seb128> pitti, what happens?
[16:07] <seb128> just curious
[16:07] <davmor2> pitti, seb128: in seahorse you can't get to your keyring is this know,  I'm guessing so but thought I'd check
[16:08] <pitti> seb128: there are devices which don't tell us when their media changes, such as CD-ROM or SD card drives
[16:08] <seb128> davmor2, it's fixed with today's gtk and you can, just expand the line with the keyboard
[16:08] <pitti> seb128: either udisks or the kernel continuously needs to poll them, by and large by open()ing the device with O_NONBLOCK
[16:08] <pitti> this will trigger a media change event
[16:09] <pitti> seb128: it looks like this polling kicks in shortly after the device gets removed, and as the kernel doesn't happen a real device for sdb any more (and no parent for it), it just creates an /sdb fake thingy
[16:09] <pitti> that's the area I don't know well any more
[16:09] <pitti> seb128: anyway, udisks misinterprets that as "oh, it's a change event, I don't know about this device so treat it as "added"
[16:09] <pitti> seb128: and then when the real device comes back, it tries to add it again
[16:10] <G__81> hi seb128
[16:10] <seb128> G__81, hi
[16:10] <seb128> pitti, ok
[16:10] <G__81> seb128: remember we spoke on the other day about Ubuntu-Development. I was interested and have installed Ubuntu too
[16:10] <seb128> pitti, thanks for the explanation
[16:11] <seb128> G__81, yes
[16:11] <davmor2> seb128: Thanks I figured it would of been know and almost certainly fixed :)  you guys rock
[16:11] <seb128> yw
[16:11] <G__81> seb128: i have a doubt about this sponsorship. I fix a bug and for me to commit, you sponsor me is it?
[16:12] <seb128> G__81, right, you fix a bug and do a merge proposal on launchpad or file a bug with a patch and subscribe ubuntu-sponsors
[16:12] <seb128> we review those regularly
[16:13] <G__81> seb128: oh ok so once i get sponsored what happens for the subsequent bugs, i fix a bug and then submit the same for review and once review is done, i commit it is it since i am already sponsored ?
[16:13] <G__81> is that how it is?
[16:13] <seb128> what do you mean? it works the same way that contributing to upstream project
[16:13] <seb128> somebody needs to commit,upload for you
[16:13] <seb128> until you did enough work to be granted direct access
[16:13] <seb128> then you can do it yourself without sponsoring
[16:14] <G__81> oh for every bug you sponsor is it?
[16:14] <pitti> anyway, need to run now
[16:14] <pitti> good night everyone, have a nice weekend!
[16:14] <G__81> the upstream projects that i am part of, i do git format-patch and send out the patch and the maintainer applies it. Is it the same here ?
[16:15] <seb128> same here, it has been a buggy week ;-)
[16:15] <seb128> pitti, 'night, good w.e, see you monday
[16:15] <pitti> seb128: s/buggy/busy/?
[16:15] <pitti> (buggy as well for sure, though)
[16:15] <seb128> pitti, yeah, busy making ubuntu less buggy :p
[16:15] <seb128> ;-)
[16:16] <seb128> G__81, same principle out of the fact that we don't use git so it's not git format-patch, it's usually standard gnu diff, debdiff or merge request on launchpad
[16:17] <G__81> oh ok seb128 thanks so can you point me to some easy stuff to start off with ?
[16:17] <G__81> some upstream package ?
[16:17] <G__81> something easy to start off with
[16:18] <seb128> G__81, not off hand, pick a package,component you are interested in, look at the bug list and figure something you would like to work on,fix maybe,
[16:19] <G__81> hmmm ok will do that thanks seb128
[16:19] <seb128> yw!
[16:20] <G__81> can you give me the link in LP so that i can see the list of packages ?
[16:20] <nessita> hello everyone! quick question: I have the launcher set to auto-hide, and very often happens that the launcher appears and never goes "back" again. Any idea if this is reported already? is there a workaround?
[16:32] <didrocks> nessita: are you using 2d or 3d?
[16:32] <didrocks> hey ;)
[16:33] <nessita> hola didrocks! 2d
[16:33] <didrocks> seb128: so, the quick hack for g-c-c will be a longer hack FYI
[16:33] <nessita> didrocks: I've tried everything I could think of
[16:33] <didrocks> nessita: there are some autothide issues in it
[16:33] <didrocks> nessita: I suggest pinging upstream on #ubuntu-unity
[16:33] <nessita> didrocks: thanks, will do
[16:33] <didrocks> yw :)
[16:34] <didrocks> seb128: alt tapping is not supported by g-c-c shortcut, it even doesn't show it if you set a key to only "<Alt>"
[16:34] <didrocks> seb128: so I guess fun times on Monday :)
[16:38] <BigWhale> Any Gtk/Gdk experts around here? I was told at #gtk+ that gdk_window_add_filter() was skipped from introspection
[16:39] <BigWhale> anyone know why and if this can be enabled in the (near) future? :)
[16:42] <dobey> that's a question for #gtk+
[16:42] <BigWhale> dobey, yeah... they don't know
[16:42] <BigWhale> presently
[16:42] <dobey> they don't know why their own api isn't being introspected by their own introspection device?
[16:43] <BigWhale> yes... well those that are currently present :)
[16:44] <dobey>  * gdk_window_add_filter: (skip)
[16:44] <dobey> perhaps that is why it is skipped :)
[16:44] <dobey> the docs in the code say to skip it
[16:46] <BigWhale> err, yes. I was told that. but they don't know why. :)
[16:46] <BigWhale> why the skip mark
[16:48] <BigWhale> I'll subscribe to a bunch of mailing lists ..
[16:48] <BigWhale> :>
[17:00] <dobey> BigWhale: then dig through git to see who made that change, and ask that person why it's like that :)
[17:00] <dobey> BigWhale: or patch it out and see what breaks
[17:02] <didrocks> ok, time for week-end here!
[17:02] <didrocks> have a good evening everyone :)
[17:07] <BigWhale> dobey, I probably will do something like that. Just not right now. :/
[17:30] <raffa50> hello
[17:30] <dobey> hi
[17:30] <raffa50> how can i insert a new mime type?
[17:30] <raffa50> example: i made an application  (that you can install whit a .deb) that makes a .slyproj file, but the user should open it whit double click
[17:30] <raffa50> (whit double click on .slyproj my application should open)
[17:31] <dobey> by following the xdg shared mime info, and xdg desktop file specifications
[17:34] <JanC> http://standards.freedesktop.org/desktop-entry-spec/latest/ & http://standards.freedesktop.org/shared-mime-info-spec/latest/
[17:35] <raffa50> my .deb package can't add the mime type (for other users tath download my app)
[17:35] <raffa50> ?
[17:38] <JanC> raffa50: it can, just read those specs (as dobey says, you'll need both)
[17:38] <dobey> raffa50: there are data files your application has to install
[17:39] <dobey> raffa50: you might want to look at the source trees of other projects that use the same build system as you do, and which do what you want, for some better examples of how to do it
[17:40] <raffa50> i'm programming in gambas
[17:40] <raffa50> (don't laught at me)
[17:40] <raffa50> gambas = visual basic
[17:43] <JanC> we might not like to use it ourselves, but everybody can use what they like/prefer, so nobody will be laughed at
[17:44] <JanC> raffa50: you might want to look at other applications written in gambas
[17:44] <raffa50> no example i searched
[17:45] <dobey> raffa50: what tool is used to build/install the application?
[17:45] <dobey> what application is it?
[17:45] <raffa50> gambas
[17:46] <raffa50> gambas build it's packages
[17:46] <raffa50> and generate a .gambas file for my app
[17:46] <JanC> raffa50: gambas makes .deb packages?
[17:46] <raffa50> in my case
[17:46] <raffa50> yes
[17:47] <raffa50> you said JanC
[17:47] <JanC> raffa50: maybe ask the gambas developers then, and if they don't support this yet, file a bug
[17:47] <raffa50> i asked on italian forum
[17:47] <raffa50> ...
[17:47] <raffa50> maybe on english
[17:48] <JanC> it only needs to copy a couple of files into some locations during install, so it should be easy to add that
[17:49] <JanC> and the gambas developers can ask for help if they are not sure about how to do this correctly
[17:53] <raffa50> i can't understand that guided that you gave to me
[17:53] <raffa50> x.x
[17:55] <JanC> raffa50: I'm sure you could given enough time, but the easiest way is to have the gambas developers implement this, and then it will work for all gambas programs...
[17:59] <bcurtiswx> away
[17:59] <bcurtiswx> sorry missing / :P
[18:00] <raffa50> i thought i could make it whit .deb pakcage
[18:04] <raffa50> no english forum
[18:04] <raffa50> x.x
[18:04] <dobey> is anyone else having weird color issues with flash on youtube?
[18:05] <mdeslaur> dobey:  bug #967091 and bug #967182
[18:05] <ubot2> Launchpad bug 967091 in adobe-flashplugin "Wrong tint with Nvidia after upgrading to 11.2" [Undecided,Confirmed] https://launchpad.net/bugs/967091
[18:05] <ubot2> Launchpad bug 967182 in adobe-flashplugin "Flash plugin <IP_ADDRESS> and libvdpau1 together cause breakage in firefox and chromium in Precise and Oneiric for nvidia users" [Undecided,Confirmed] https://launchpad.net/bugs/967182
[18:05] <mdeslaur> dobey: flash and nvidia don't like each other anymore
[18:05] <dobey> ah
[18:05] <dobey> it's weird
[18:06] <dobey> vimeo is fine
[18:06] <dobey> but youtube is messed up
[18:10] <Sweetshark> pitti: I nearly died of the 'failed to build' mails for 3.5.1-1ubuntu3 ....
[18:11] <dobey> hmm :-/
[18:15] <JanC> raffa50: you could try the mailing list
[18:15] <JanC> ("Gambas Users" mailing list)
[18:18] <maxb> Can anyone tell me where GNOME stores the metadata for its Recycle Bin?
[18:18] <maxb> I have an "untitled folder" that is stuck there, and doesn't go away when I empty it
[18:18] <maxb> I want to track down where this info might be being stored
[18:21] <JanC> maxb: ~/.local/share/Trash/
[18:22] <JanC> or in case of external disks, let me check
[18:22] <maxb> There isn't anything in ~/.local/share/Trash except empty {info,files,expunged} directories
[18:22] <maxb> I'm not aware of having any external disks attached
[18:23] <maxb> AHA
[18:23] <JanC> http://standards.freedesktop.org/trash-spec/trashspec-latest.html might be useful
[18:23] <maxb> What about a network share
[18:23] <JanC> that's external too indeed
[18:24] <maxb> Hah, right, there is a .Trash-1000 folder in a cifs share I have mounted :-)
[18:24] <maxb> And I don't have permissions as my user to modify it
[18:24] <maxb> Problem solved :-)
[18:25] <JanC> http://standards.freedesktop.org/ --> is a good place to find cross-desktop (GNOME, KDE, XFCE, etc.) specs
[18:36] <raffa50> Torvalds help me!
[19:00] <mvo> seb128: hi, silly question - isn't this http://paste.ubuntu.com/907697/ supposed to show a label under bar ? I don't seem to see one :/
[19:00] <mvo> seb128: ohhhhh, Gtk.Label.new() again :/
[19:01]  * mvo scratches head


[02:52] <ScottK> opencv on arm64 now causes an ICE, which is a regression.  What's the best way to deal with that to get it to migrate?
[02:53] <infinity> ScottK: disabling precompiled headers, probably.
[02:54] <ScottK> Fun.  55 MB tarball.
[02:56] <ScottK> At 42 kB/s
[02:56] <ScottK> Double fun.
[02:59] <ScottK> infinity: Would it be reasonable to override pykde being blocked on the apport jenkins failure?  The gtk front end failed too, so I'm pretty sure it's not pykde's fault.
[03:11] <ScottK> infinity: Does your recommendation change if I say the upstream code in question is unchanged, so it's likely a gcc regression?
[03:12] <infinity> ScottK: No, we know it's a GCC issue, but we've already disabled PCH in a few packages to move on for now.
[03:12] <ScottK> Ok.
[03:13] <ScottK> Got an example I can use to try and figure out how to do that?
[03:13] <infinity> https://patches.ubuntu.com/w/wxwidgets3.0/wxwidgets3.0_3.0.1-1ubuntu1.patch
[03:13] <infinity> Assuming you're lucky enough to have a configure switch for it.
[03:14] <ScottK> It's CMake, but it looks like I do.
[03:14] <ScottK> Thanks.
[03:15] <ScottK> ENABLE_PRECOMPILED_HEADERS
[03:15] <infinity> Kay.  So something more like this: http://launchpadlibrarian.net/177701306/sandboxgamemaker_2.7.1%2Bdfsg-2build2_2.7.1%2Bdfsg-2ubuntu1.diff.gz
[03:15] <ScottK> Thanks.
[03:17] <ScottK> That may be a tomorrow thing.  Suddenly I'm tired.
[06:50] <mlankhorst> can someone accept llvm-toolchain-3.4 in utopic?
[06:50] <mlankhorst> seems that llvm-3.4-tools is NEW
[06:51] <infinity> mlankhorst: It's also FTBFS on all !x86, so I was in no rush to accept.
[06:51] <mlankhorst> ah
[06:51]  * mlankhorst looks
[06:51] <infinity> mlankhorst: Due to this, I believe:
[06:51] <infinity>   * Ship the compiler-rt static libraries in libclang-3.4-dev
[06:52] <infinity> mlankhorst: But I didn't have the time to investigate how to unbreak it.
[07:00] <mlankhorst> fun part is that it's not supposed to happen afaict
[07:00] <mlankhorst> # Create this fake directory to make the install libclang-common-dev happy
[07:00] <mlankhorst> # under the unsupported archs of compiler-rt
[07:04] <mlankhorst> except libclang-3.4-dev takes a different source directory, weird stuff :/
[07:12] <mlankhorst> infinity: https://mblankhorst.nl/etc/llvm-toolchain-3.4_3.4.2-3ubuntu2.debdiff ?
[07:13] <infinity> mlankhorst: Maybe? :P
[07:13] <infinity> mlankhorst: Give it a test-run on porter-powerpc, perhaps.
[07:14] <mlankhorst> ok
[07:22] <infinity> ^-- That was pre-reviewed by cjwatson, I didn't just pull a fast one.
[08:19] <mlankhorst> infinity: yeah that llvm-toolchain-3.4 debdiff fixes the FTBFS on ppc
[08:33] <infinity> mlankhorst: Uploading.
[09:05] <michagogo> Question: does getting an SRU in before a point release change anything?
[09:05] <michagogo> (For a universe package, that is)
[09:06] <michagogo> In other words, would there be any specific value in bug 1314616 getting in before 12.04.5, or does it not matter?
[09:06] <cjwatson> Doesn't much matter for things that aren't on images.
[09:08] <michagogo> (Btw, do people regularly look at the list of things waiting to be sponsored?)
[09:08] <michagogo> s/e /e that can sponsor/
[09:25] <mlankhorst> there ya go :-)
[09:45] <xnox> Laney: will desktop-next be doing an alpha-1?
[09:45] <Laney> xnox: no
[09:45] <xnox> ogra_: ubuntu-touch for alpha-1?! =)
[09:45] <ogra_> huh ?
[09:45] <Laney> we'd have replied to the thread if so
[09:46] <xnox> ok.
[09:46] <ogra_> xnox, lol, surely not :)
[10:01] <mlankhorst> now we just need armhf :-)
[11:25] <infinity> Wow, britney, seriously?
[11:26] <infinity> cjwatson: Fun misfeature.  Since glibc was new source, britney totally didn't care that its binaries were out of date on some arches and migrated it prematurely.  Whee.
[11:47] <mlankhorst> oops
[12:36] <cjwatson> infinity: I guess that meant nothing was uninstallable in the interim
[12:37] <infinity> cjwatson: True, was just a surprise that it didn't actually care about the binaries being out of date, since it deals with things as source package units.
[12:39] <mlankhorst> yay llvm-toolchain-3.4 built
[13:02] <jamespage> arges, any chance you could accept the neutron and cinder updates from jdstrand into trusty-proposed?
[13:02] <jamespage> coreycb, ^^
[13:20] <cjwatson> final: glibc/arm64
[13:20] <cjwatson> so hopefully that's sorted out
[13:22] <infinity> cjwatson: Yeah, my email implied as much.
[13:22] <cjwatson> Email where?
[13:23] <infinity> cjwatson: The duplicate ACCEPTED mail.
[13:23] <cjwatson> Oh right
[13:42] <arges> jamespage: I can (and was planning on) reviewing them today
[13:43] <jamespage> arges, thankyou!
[13:43] <arges> jamespage: was nova already taken care off (...looks)
[13:43] <jamespage> arges, no - that's still in the queue as well
[13:43] <arges> jamespage: ok yup its on my todo list today
[13:43] <jamespage> arges, ++excellent
[13:57] <cjwatson> That livecd-rootfs upload should sort out */trusty/amd64 livefs builds.  Then it's just Edubuntu to sort out.
[14:02]  * stgraber looks
[14:06] <cjwatson> Thanks
[14:06] <stgraber> cjwatson: accepted. You were missing the usual SRU paperwork, but I guess the testcase is "just rebuild ubuntu gnome" so that's fine.
[14:06] <cjwatson> Er, sorry, yeah.  I plan to switch trusty to PROPOSED=1 and see if it works
[14:07] <cjwatson> Pretty much any vaguely normal flavour exhibits it
[14:08] <cjwatson> I've actually tested it already using the new build-against-PPA facility
[14:09] <arges> Hi. looking at the nova upload in trusty. A security update went in at ubuntu1.2, but the debdiff for ubuntu1.3 includes the changelog entry for the security update as well. Should I reject and request this be done against ubuntu1.2?
[14:09] <arges> In addition to some other changelog mangling; not sure why that happened either.
[14:12] <infinity> arges: I'm not sure I understand the question.  The debdiff contains 1.2 and 1.3 because LP is brain damaged, not because the uploader did anything wrong.
[14:13] <infinity> arges: (It's a debdiff between proposed and proposed)
[14:14] <infinity> arges: The changelog weirdness after that is a bit odd, I'll give you that.  Especially the part where it introduces a spelling error that wasn't there before. ;)
[14:14] <arges> infinity: ok and in that case -proposed is in -updates, so I thought we'd get a debdiff between -updates and what the uploader is requesting
[14:14] <infinity> arges: Yeah, LP's not that smart.  If you want the debdiff from updates, you'll get to do it yourself.
[14:15] <arges> infinity: ok. and second... looking at cinder. I noticed the debdiff is against whats in -proposed; and the current -proposed never got accepted into updates. in that case shoudl we request a debdiff against whats in -update?
[14:15] <infinity> arges: How do you propose to request this?
[14:16] <infinity> arges: If you just mean you want someone to manually do it, you can just as easily do that yourself.  *shrug*
[14:16] <arges>  infinity i can do it. I just want to make sure the upload is oK
[14:17] <arges> infinity: so again, I can attribute this to LP oddness?
[14:17] <infinity> arges: I think it's obvious what's going on in that cinder update, though.
[14:17] <cjwatson> You can always attribute wrong debdiff to LP oddness.  It's always fine to download it yourself and debdiff manually against what rmadison reports for the suites you care about.
[14:17] <infinity> arges: The previous upload was already accepted, and this just adds the security update 1-liner and the changelog bits.
[14:18] <cjwatson> I mean completely wrong base for debdiff, of course.
[14:18] <arges> infinity: yup yup. I'm just making sure I don't mess something up
[14:18] <infinity> To be fair, the cinder debdiff isn't against the wrong base.
[14:20] <infinity> arges: If I were being a pedant, I'd punt the nova one for the weird history mangling, but probably only because the change in attribution and the introduction of a new typo really irk me. :P
[14:21] <infinity> Oh, actually, it also breaks the changelog format.
[14:21] <arges> that's not good
[14:21] <infinity>      exception when starting instances with libvirt LXC or XEN. (LP: #1297962)
[14:21] <infinity>
[14:22] <infinity> - -- Chuck Short<EMAIL_ADDRESS>Tue, 20 May 2014 12:04:39 -0400
[14:22] <infinity> -
[14:22] <infinity> ubot93: Not helpful.
[14:22] <infinity>  nova (1:2014.1-0ubuntu1) trusty; urgency=medium
[14:22] <infinity> arges: So, yeah, make chuck fix his mess there, IMO.
[14:23] <arges> jamespage: zul ^^^ I'm going to reject nova because of changelog mangling. want to check it over before I do so?
[14:23] <infinity> arges: But probably worth reviewing the rest of the upload first, and keeping a copy around, so you can enumerate all the bad, and debdiff old.dsc new.dsc when he reuploads to only see what was fixed instead of re-reviewing the whole thing.
[14:23] <zul> arges:  go ahead ill fix it up and re-upload it
[14:23] <arges> infinity: yup I have it local
[14:24] <infinity> zul: I assume you can spot all the bad in http://launchpadlibrarian.net/177877395/nova_1%3A2014.1-0ubuntu1.1_1%3A2014.1.1-0ubuntu1.3.diff.gz and don't need it pointed out? :)
[14:24] <infinity> zul: (In the changelog, that is)
[14:24] <zul> infinity:  yeah
[14:24]  * infinity needs to start stapling "debdiff before you upload" notes to everyone's foreheads.
[14:31] <mlankhorst> but an upload generates the debdiff for you ;-)
[14:44] <arges> infinity: so I re-constructed the cinder upload in trusty. the changelog jumps from 2014.1-0ubuntu1 to 2014.1.1-0ubuntu2. which skips 2014.1-0ubuntu1.1 (in -updates)
[14:45] <infinity> arges: Yeah, I made that out from the debdiff.
[14:45] <infinity> arges: The way it's done looks fine to me.
[14:46] <arges> infinity: ok. I didn't know if it was necessary to have another changelog entry for 2014.1-0ubuntu1.1
[14:46] <infinity> arges: Well, linear history is nice, but I get the impression that Jamie did 1.1 and 2 at the same time, and just did 2 as an addendum to 1, so it sort of makes sense to me.
[14:47] <arges> infinity: yup, I can see that
[14:47]  * arges goes and looks at teh rest of the diff : )
[14:47] <infinity> arges: His 1-liner and weird changelog would be fine with me, anyway.  The rest of it might be scary. ;)
[14:48] <infinity> (But openstack has an MRE, so as long as the diff doesn't look obviously broken, you're good)
[14:48] <arges> well i already reviewed it last week anyway, so mostly it is a glance to ensure changelog matches the features in the usptream changelog / formatting wierdness / etc
[14:51] <arges> also is bug 1185019 supposed to be private/emargoed still?
[14:51] <arges> embargoed
[14:52] <infinity> arges: I would hope not, since it's fixe released all over the place.
[14:52] <arges> infinity: pinging jamie about it
[14:53] <infinity> I can un-private it.
[14:53] <infinity> Done.
[14:53] <arges> infinity: hold on
[14:53] <infinity> Hrm?
[15:40] <arges> zul: ok, so the nova upload is against 2014.1-0ubuntu1.1 while 2014-1-0ubuntu1.2 is in proposed. I tried to reconstruct this using 1.1 and that patch didn't apply; also I notcied that d/p/libvirt-Handle-unsupported-host-capabilities.patch seemed to be dropped.
[15:42] <zul> arges:  crap can you reject it one more time
[15:42] <arges> : )
[16:24] <ScottK> ksudoku has suddenly started FTBFS on armhf and I don't think it will get fixed for alpha1.  It's blocking a stack of other packages from transitioning via libkdegames.  I'd like to either force it or do a binary removal on the one arch.  It's got no rdepends.  Thoughts?
[16:26] <cjwatson> It does have one rdepends: kdegames
[16:26] <cjwatson> That seems a little tricky as you'd have to remove meta-kde/armhf
[16:26] <ScottK> Oh.  Right.
[16:27] <ScottK> I can fix that not to depend on it for armhf.
[16:27] <ScottK> Easy enough.
[16:27] <cjwatson> Right, I think if you do that temporarily it's fine to remove the no-longer-buildable binary
[16:27] <ScottK> OK.  Thanks.
[16:35] <ScottK> OK, that takes care of that one.
[17:22] <ScottK> That worked.  The stack of packages around libkdegames migrated.
[17:22] <cjwatson> Cool
[17:24] <ScottK> Analitza built so that'll resolve two more depwaits on armhf.  I think kalzlium is good now too (waiting to see), so we're getting there.
[18:18] <ScottK> So, it looks like between libav, cups, and gnutls the chances of something like a KDE release making it to the release pocket are nil.
[18:18] <ScottK> Is anyone actively working on these?
[18:21] <xnox> yes
[18:39] <LocutusOfBorg1> xnox, do you have any timeline for libav? or do you need help? I cannot upload, but since the transition is already done in debian I hope the changes should be minimal
[18:40] <LocutusOfBorg1> libavg should just need a sourceful upload in debian and a sync :)
[18:49] <ScottK> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt looks rather scary for libav.
[18:55] <xnox> LocutusOfBorg1: what do you mean "just a sourceful upload for libavg" it fails to build from source with libav10, no?
[18:57] <LocutusOfBorg1> xnox, you are the maintainer right? did you miss this? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739664#34
[19:01] <xnox> LocutusOfBorg1: yeah, i  did miss that.
[19:02] <LocutusOfBorg1> wonderful to hear, I was afraid about some showstopper for the new release :)
[19:09] <xnox> LocutusOfBorg1: that upstream release does not compile against libav10
[19:13] <xnox> trying harder
[19:19] <LocutusOfBorg1> :( sorry for that
[19:59] <rtg> can someone just reject Precise openipmi 2.0.18-0.1ubuntu1 ?
[20:00] <rtg> I think I messed it up
[20:06] <stgraber> sure, always happy to reject stuff :)
[20:06] <rtg> well, maybe not. config.guess and config.sub get generated during 'clean' which is the bulk of the diff
[20:07] <rtg> perhaps I'll just come back to this tomorrow. EOD for me.
[20:08] <stgraber> you may be able to trick it into not doing that so you only get the initscript diff but if you can't that's no big deal either, we're used to that kind of automagic spam
[20:08] <rtg> stgraber, ok, if it looks good then please accept it.
[20:55] <ScottK> I think all the Kubuntu stuff that will make it to the release pocket for Alpha 1 without some form of violence on the archive is there.
[20:55] <ScottK> shadeslayer: ^^^
[20:55] <stgraber> as I said in the e-mail this morning, I've got all the participating flavours already disabled in cron, so when you are ready, just trigger a build
[20:55] <stgraber> I'll setup the block shortly too
[20:56] <ScottK> Please ping here when you've set the block.  I may as well wait for that.
[21:08] <stgraber> ScottK: done
[21:23] <ScottK> stgraber: Thanks.
[21:33] <ScottK> And then I managed to request the rebuild, so I think we're off and running.
[21:38] <shadeslayer> ScottK: thx for getting everything in, it was a bank holiday here today
[21:53] <ScottK> stgraber: We should probably have the upgrade milestone for Alpha 1 too.
[22:01] <stgraber> ScottK: ah yeah, I'll add some of those
[22:22] <ScottK> stgraber: Thanks.
[23:13] <wxl> someone correct me if i'm wrong but the difference between amd64 and amd64+mac is that amd64 is uefi and amd64+mac is not, correct?
[23:15] <wxl> i.e. as long as they didn't use uefi, a person with amd64 hardware could test amd64+mac?
[23:16] <infinity> wxl: It's even more subtle than that.  amd64+mac is for booting CDs (but not USB sticks) on a specific generation of broken/weird Macs.
[23:16] <wxl> infinity: my understanding is that there were some amd64 machines that suffered the same fate
[23:16] <infinity> wxl: As for who can successfully boot it without breaking their non-Macs, I'm not entirely sure.
[23:16] <wxl> infinity: do i also gather from your statement that on usb it works with amd64 and intel macs without problem? :)
[23:17] <infinity> wxl: Yeah, if you don't use shiny spinny media, the regular amd64 image should work fine, even on the goofy Macs in question.
[23:18] <wxl> infinity: oh now that's funny.


[08:16] <GeekFreak> Hello
[08:18] <Noskcaj> hey GeekFreak
[08:18] <GeekFreak> how are you Noskcaj
[08:18] <Noskcaj> pretty good. you?


[01:36] <Shentino> I think the perfect VCS would be git's branching and merging logic combined with bzr's flexibility and ability to handle directories as first class objects


[00:04] <astroo-> 'Twisted light' carries 2.5 terabits of data per second
[00:04] <astroo-> http://www.bbc.co.uk/news/science-environment-18551284
[02:59] <astroo-> ciao pessoal
[20:55] <astroo-> ola pessoal


[00:39] <xubuntu22w> hello i am trying to figure out how to add folders to the wallpaper selector is their a way to enable subfolders or something?
[04:03] <SirSlippers> HoWdY!!  XUBUNTU 16.04 - How do I change Screen Display from 640X480 to 1280X1024 ???
[04:05] <SirSlippers> AFK a minute ... BRB
[04:22] <SirSlippers> OK back ...   XUBUNTU 16.04 - How do I change Screen Display from 640X480 to 1280X1024 ???
[04:23] <SirSlippers> Would I be better advised to DUMP 16.4 and go with a version that isn't so new?
[04:49] <akis> hi all. i installed 16.04 (clean installation) on 3 machines. 2 of them have 4gb ram and celeron cpu and the 3rd has only 2gb but a core duo cpu. I see that 16.04 needs more ram than 14.04 did to run the same applications. On my 3rd machine (this with 2gb ram only) many times (when many tabs on browser are open or flash is running) exceeds the whole ram (set vm.swappiness=1 instead the default 60) and start swappiness. Doea any one else realize
[04:49] <akis>  that 16.04 need more ram than 14.04 did?
[05:01] <SirSlippers> OK .. this is weird!  I rebooted XUbuntu 16.04 and I got a nice 1280 X 1024 screen.  Then I shut it down and got the old 640X480 screen ... hmmm ... anyone know how to PERMANAENT LY change this please!
[05:02] <SirSlippers> I remember on some readings about VGA=771 was helping get the black screen to be readable ...
[05:02] <SirSlippers> I don't know where to type that in though
[05:09] <SirSlippers> WoW!!  I've been waiting an hour for help ... hmmm ...
[05:13] <cspack> SirSlippers: that setting is in /etc/default/grub
[05:14] <SirSlippers> cspack: > that's nice ... how do I get there?  Where do I type that in?  NEWB ALERT!
[05:15] <SirSlippers> and is VGA=771  for 640 X 480?  What is the setting for 1024X768 or 1280 X 1024?
[05:15] <SirSlippers> there is TONS of people having problems with this inability to adjust the screen settings ...
[05:20] <cspack> SirSlippers: those codes are kind of old, you can just type the resolution you want /etc/default/grub. For example: GRUB_GFXMODE=1024x746
[05:21] <SirSlippers> ok .. great!  umm .. WHERE do I "Just Type The Resolution you want"  ??
[05:23] <cspack> SirSlippers: I told you the file name "/etc/default/grub". Best bet is to look for a grub2 tutorial if you're not familiar with it.
[05:25] <SirSlippers> the tutorials are written by people showing of how much they know and NOT really trying to explain clearly to someone just starting what to do!!
[05:26] <SirSlippers> there are SO MANY STEPS that are missed in those ... (sigh)  maybe I better stay with WinDoZe ...
[05:28] <SirSlippers> cspack:  thankx anyways ... but you were of little assistance ... I came HERE for help ... I already TRIED the tutorials that you spoke of ... geeze ...
[10:10] <ax562> good morning/good afternoon/good evening
[11:47] <ax562> does anyone use deluge in here?
[11:48] <Reklan> not me sorry
[11:58] <bazhang> ax562, used it, prefer transmission
[11:59] <bazhang> rtorrent if you want the cli
[13:12] <g4b1t> hello everyone just a quick question. Is it safe to upgrade my xubuntu 14.04.1 to 16.04 at this point?
[13:20] <ax562> 16.04 is great g4blt
[13:20] <ax562> go for it
[13:22] <g4b1t> ax562,  ok thanks !
[13:24] <ax562> np
[15:48] <chuckmcm> ok so is there a way to get a window back or set non-mirror mode on the displays from xrandr?
[15:50] <chuckmcm> well logging out and in again works
[15:50] <chuckmcm> sigh
[21:47] <chuckmcm> really annoying have to reset my screen placement every time my screen blanks.
[22:26] <hmir> Hey guys. I have xubuntu 14.10. I've have heard that upgrading 14.10 to 16.04 is a huge hassle, and that I may have to upgrade first to 15.04 and then from 15.04 to 16.04. Is this accurage?
[22:26] <hmir> I would prefer a clean insstall, but the cdrom drive on my laptop is faulty, and the laptop BIOS is old, does not support booting from USB.
[22:27] <hmir> So, I would prefer to upgrade the release from within the OS.
[22:27] <hmir> Any advice/recommendation?
[22:33] <choki> hello
[22:33] <choki> is there already a fix for suspend bug where you dont have a mouse pointer visible?
[23:01] <hanshenrik> Wow shit
[23:01] <choki> hanshenrik: wow
[23:02] <hanshenrik> When booting from CD running running a in-ram system, it should NOT try to hibernate when closing the laptop screen
[23:02] <choki> it doesnt
[23:02] <hanshenrik> But yeah it seems like it tried to do that - and froze(/crashed?) In the process
[23:04] <hanshenrik> Oh nvm, seems it woke up again now :o
[23:05] <choki> hanshenrik: i lik xubuntu :3
[23:05] <hanshenrik> Me2. I especially prefer it over Unity
[23:06] <hanshenrik> Is Ubuntu still using that in 16.04?
[23:06] <choki> yes :D
[23:06] <choki> hanshenrik: but sadly xub 16.04 has a bad bug with suspend on laptops
[23:33] <kgb> o/ sup pplz!..:) hey, guys, eye HATE asking for help (bc, we should be able 2 figure it out, heh. :)); BUT, having had upgraded from Ubuntu 15.10 to Ubuntu 16.04 LTS I do NOT have *functional* Perl, even though everything seems to be installed!.. What's going on, for example, is that I can't load HexChat (XChat2) Plugins which require Perl; in fact, it's not there - it's not getting loaded - I don't understand it? o.0 http://i.imgur.com/62d0TVJ.png
[23:33] <kgb> ... Python is there, no problem; Perl - gone? :-0
[23:35] <kgb> ^^ Everything, ofc., had been working *fine* prior to the upgrade (which, btw., I found out - the hard way, LOL - should never be run, heh; in the time it took to upgrade, I could've re-installed the system, like, 10 times, lolz. :))
[23:43] <kgb> ok, let me rephrase - as I need help here, pls!! :)) is there a way to get a list of Perl files necessary to function - so that I can paste it here - and then ask WTH is going on?? :DD
[23:49] <kgb> #IgnoreKGBDayIsHere yay! \o/