[00:02] <bluesabre> brainwash: done
[00:02] <bluesabre> Unit193: question when you're around
[00:05] <bluesabre> brainwash: since this one came up again today, does it fix the issue for all keyboard shortcuts, or does it only apply to the one? https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1292290
[00:15] <Unit193> bluesabre: Not quite here, but still.
[00:15] <bluesabre> :)
[00:15] <bluesabre> know a lot about rm_conffile?
[00:17] <Unit193> A little, man dpkg-maintscript-helper
[00:17] <Unit193> http://manpages.ubuntu.com/dpkg-maintscript-helper 
[00:18] <bluesabre> aha
[00:18] <bluesabre> that answers my question
[00:19] <bluesabre> thanks Unit193!
[00:19] <Unit193> Hah, well glad I could help.
[00:20] <brainwash> bluesabre: the updated keyboard shortcuts file from vivid fixes the maximize action in utopic and the maximize action + workspace actions in trusty
[00:20] <brainwash> -> everything should be fixed then
[00:20] <brainwash> (in xubuntu at least)
[00:21] <bluesabre> alrighty, thanks brainwash
[00:30] <brainwash> should we pick the patch for bug 1314829 ?
[00:31] <brainwash> it seems to me that there won't be a new ristretto version any time soon
[00:32] <bluesabre> sure, seems reasonable.  low priority, so poke me about it if its not done in a few days
[00:33] <brainwash> maybe let debian do the job
[00:34] <brainwash> but you are right, it's a low priority task
[01:50] <bluesabre> brainwash: uploaded xubuntu-default-settings for trusty... waiting for approval now.  
[02:21] <bluesabre> Unit193: did we have an ITP for xfdashboard or soundmenu at any point?
[02:40] <Unit193> bluesabre: Nope.
[02:40] <Unit193> I can give you a list of xfce4* ones though, and skippy-xd had one, but that's it.
[03:10] <Unit193> bluesabre: Not really sure how to do this either.  It'd make more sense to push xfdash 2.x stable series to Debian, but in Xubuntu we use and it makes sense to use 3.x series.
[07:59] <ochosi> bluesabre, brainwash: well, some ristretto patches have been merged recently, so might as well do a drive-by git-snapshot instead of integrating the single patch (then we also get other patches and translations). as soon as we get release-rights, there'll be a 0.6.4 though
[08:06] <ochosi> pleia2, elfy: nice work on the stickers article!
[08:07] <elfy> morning ochosi 
[08:08] <elfy> not actually seen it yet
[08:11] <ochosi> oh :)
[08:11] <ochosi> well i presumed you were involved there
[08:11] <elfy> I was here and there :)
[08:39] <elfy> ochosi bluesabre - did you see the comment from jjfrv8 re "black screen bug when I set to lock on suspend" 
[08:39] <elfy> I see the same here with the new xfpm too
[08:42] <ochosi> i did see some of the comments of jjfrv8 
[08:42] <ochosi> anyway, i'm not entirely sure what sort of permission/polkit? issue he's having there
[08:43] <ochosi> but that black screen bug might be resolved when resetting xfpm's settings
[08:43] <ochosi> at least that's where i would start
[08:43] <ochosi> plus, the light-locker.desktop file in your ~/.config/autostart should be reset not to pass any parameters
[08:44] <elfy> I don't have a file in there
[08:44] <ochosi> when did you install vivid?
[08:44] <elfy> 3 weeks ago perhaps
[08:44] <ochosi> oh
[08:44] <Unit193> On the daily or just uploaded?  Shouldn't be much difference I wouldn't think.
[08:45] <ochosi> hmm, might be that the autostart file is in a system folder still
[08:45] <ochosi> or it got cleaned out in case you removed light-locker-settings
[08:45] <elfy> probably :)
[08:45] <elfy> I'll check it out later from a clean one
[08:45] <ochosi> either way, maybe a good idea to just do a "apt-get install light-locker --reinstall" to be sure
[08:45] <ochosi> ok, that's also an option :)
[08:46] <elfy> :)
[08:46] <elfy> time for that later today or tomorrow
[08:46] <elfy> and I'll try and get a call out to test it this weekend
[08:47] <ochosi> cool
[08:47] <ochosi> i'll be away over the weekend btw, will only return in a week
[08:47] <elfy> ok 
[08:48] <ochosi> might be around at some points though, but mostly for reading up, likely won't have much time to get things done
[08:48] <elfy> :)
[08:48] <ochosi> was following up on our xdg-utils merge today though, so hopefully it'll be merged in the afternoon
[08:48] <ochosi> then the bug where parole (and others) reset your screensaver time will finally be a thing of the past
[08:49] <elfy> \o/
[08:49] <elfy> that one just confused me completely :)
[08:49] <ochosi> brainwash: in case that xdg-utils MR gets merged today, could you prep the SRU for it? i'll be gone for a week after today
[09:57] <ochosi> knome: hmm, that -dev wallpaper...
[09:57] <knome> hmm hmm
[09:57]  * knome ponders if it gets ready by ochosi pondering
[09:57] <knome> i can probably look at it later today, but i'll have to leave to meet a client in about an hour, so no can do now
[09:58] <ochosi> sure, just felt like poking you about it again
[09:58] <knome> yep, i know it's late
[09:58] <ochosi> as i mentioned earlier, i'll be more or less gone for a week
[09:58] <ochosi> so i wanted to poke around before taking off
[09:58] <knome> starting from what again? :)
[09:58] <ochosi> tonight
[09:58] <knome> aha
[09:59] <knome> well bluesabre is around, we can organize a surprise for you
[09:59] <knome> (but don't hold your breath)
[10:00] <ochosi> weeee
[10:02] <ochosi> knome: any opinion on doing another highlight-color for 15.04?
[10:02] <ochosi> something teal maybe
[10:03] <knome> personally, i think we've messed up with people's systems enough already
[10:03] <knome> but otoh, if we did that every cycle...
[10:03] <knome> i guess i don't have a strong opinion, i'll revert back to the default anyway
[10:04] <ochosi> yeah, same here
[10:05] <knome> to try to think it objectively..
[10:05] <knome> we have playfully shown that customizing is easy... what would the another custom color be for?
[10:05] <ochosi> the idea was that the highlight color could be a small reference to the release name/animal
[10:05] <ochosi> but yeah, that could be a problem
[10:06] <ochosi> many animals are brown
[10:06] <knome> if it's about being distinct from cycle to cycle, then that might be a good argument
[10:06] <knome> brown, yeah, and even if we had the most exoticly colored animals, we'd run out of colors "soon"
[10:06] <knome> or end up redoing similar things
[10:07] <ochosi> yeah
[10:07] <ochosi> that is the downside of it
[10:09] <knome> and i don't knwo if it's worth the maintaining burden
[10:09] <knome> which is not much by itself, but it happens surely every cycle, and thought has to be put into it...
[10:10] <ochosi> yeah
[10:10] <ochosi> true that
[10:10] <ochosi> and it potentially makes the wallpaper creation more work
[10:11] <ochosi> because you might get a weird color of reference
[10:11] <knome> heh
[10:11] <ochosi> although that could also be an advantage
[10:11] <knome> well if it's done before the wallpaper creating has begun, it's not more work
[10:11] <knome> but it might be limiting creativity
[10:11] <ochosi> not getting stuck and redoing wallpapers in the same style / color-palette
[10:11] <ochosi> yeah, well up to you
[10:11] <knome> yeah well, we can change the wallpaper palette anyway
[10:11] <ochosi> we can also do it the other way round
[10:12] <knome> i don't think that should be the deciding factor
[10:12] <knome> sure, but then we essentially lose the relation to the animal color :)
[10:12] <ochosi> we could sync the highlight color with the wallpaper palette
[10:12] <ochosi> yeah, i know, it's just a different idea i just had ;)
[10:12] <knome> heh
[11:10] <brainwash> ochosi: will anyone do the packaging for trusty xdg-utils?
[11:11] <brainwash> what about the recent security patch for xdg-utils? both patches could be bundled
[11:19] <brainwash> bluesabre: should I subscribe the sru team to the keybind report?
[11:20] <brainwash> I did not yesterday, because the package was not uploaded yet
[11:25] <bluesabre> brainwash: I just added them and set the status to "In Progress"
[11:25] <brainwash> bluesabre: thanks :)
[11:31] <bluesabre> for the record, vivid might not be a good testing ground for light-locker... I disabled light-locker completely, shut my lid, opened it back up and my whole laptop was frozen...
[11:31] <bluesabre> screen on, time standing still
[11:32] <brainwash> uhm.. meh
[11:32] <brainwash> the kernel could be the cause
[11:36] <bluesabre> yeah, who knows. If I install the nvidia drivers, I can't get a graphical login and the greeter will run at 96% cpu
[11:36] <bluesabre> hopefully that's another driver issue, I don't want to have to fix that
[11:37] <bluesabre> s/driver/kernel
[11:40] <brainwash> you greeter? my xorg runs at 100% while the graphical user session is active
[11:40] <brainwash> your
[11:40] <brainwash> open source radeon driver
[11:43] <bluesabre> no graphical login, drop to VT1, login, view processes, the lightdm-gtk-greeter binary running at 96%, but only with the nvidia proprietary
[11:43] <bluesabre> should probably check what its doing with nouveau as well... I'll get to that later today
[11:43] <brainwash> the greeter package in vivid seems to be rather outdated
[11:44] <brainwash> or do you run master anyway?
[11:44] <bluesabre> no updates since then.  Running whats in vivid.  We'll be releasing 1.10/2.0 sometime very soon
[11:46] <brainwash> new upload will fix some issues
[11:47] <brainwash> like bug 1410770
[11:48] <bluesabre> ah cool, hadn't kept up with that one
[11:48] <bluesabre> still catching up to everything I missed
[11:58] <brainwash> bluesabre: do you have a trusty system available for testing?
[11:59] <bluesabre> to what extent?  I have a trusty server I can vnc into
[11:59] <brainwash> just to test random xubuntu stuff
[11:59] <brainwash> like bug 1365965
[12:00] <brainwash> to make sure that it does not cause anything strange
[12:01] <brainwash> so that we can finally push this upload to -updates
[12:02] <brainwash> I did not notice anything strange, and we use 4.11.8 in utopic + vivid
[12:03] <brainwash> the icon position reset might not be fully fixed, but it does not seem to be worse than in 4.11.6
[12:04] <bluesabre> we just need to get that fixed, release 4.11.9, and then SRU that in for good measure
[12:04] <brainwash> should I close the report then?
[12:04] <bluesabre> or comment saying that its not worse than before and the other fixes warrant an upload, and mark it verification-done
[12:05] <bluesabre> your call
[12:05] <bluesabre> gotta run to work
[12:05] <brainwash> ok
[12:05] <brainwash> cya
[13:52] <jjfrv8> ochosi, after several reboots and changes to xfpm settings, I am no longer getting the notifications I posted last night
[13:52] <jjfrv8> however, the machine still won't suspend if I have "lock on suspend" enabled. It does suspend and wake up fine without locking.
[13:52] <jjfrv8> now when I wait > 1 minute to try to come out of the black screen/non-suspend mode, I get: http://en.zimagez.com/zimage/xfpmbug04.php
[13:52] <jjfrv8> and my network connection is broken, I can't log out, restart, etc.
[13:52] <jjfrv8> this morning, I reinstalled light-locker like you suggested and tried things again.  Same symptoms.
[13:53] <jjfrv8> I can try a clean install on other hardware tonight.
[14:01] <jjfrv8> no snow day today, gotta go to work :(, bblte
[14:15] <ochosi> jjfrv8: as bluesabre pointed out today, unfortunately vivid doesnt seem to be the most stable testing ground wrt suspend. even without xfpm or light-locker we're getting troubles with suspending, so it could also be related to the kernel or graphics drivers
[14:16] <ochosi> i would suggest to hang in there and as soon as things have stablized a bit more (which they'll hopefully do), we can get to more testing...
[14:46] <ochosi> brainwash: good news, xdg-utils just got sponsored
[14:47] <ochosi> has that security patch you're referring to been already packaged for xdg-utils in ubuntu?
[15:20] <ochosi> haha, nice fail on the release-ml. "alpha 1 released"
[15:26] <brainwash> ochosi: I don't know what ubuntu is doing with that security patch, or if they even know about it
[15:26] <brainwash> they should know, because debian patched it some days ago
[15:26] <ochosi> from what i see xdg-utils isn't too well maintained
[15:27] <elfy> ochosi: don't laugh too much - I put me down for doing the community side of it for beta 1
[15:27] <ochosi> so i guess if you want it, you'd have to do something about it
[15:27] <elfy> and if I'm missing I out you as second :D
[15:27] <ochosi> elfy: that's very nice of you
[15:27] <elfy> s/out/put
[15:27] <ochosi> oh, that's not very nice of you
[15:27] <elfy> heh
[15:27] <ochosi> i'll remember to be offline around b1 then ;)
[15:28] <elfy> well it was kind of - better had as wxl did this one - and riddell did the last - there'd be no-one to do the next ... 
[15:28] <ochosi> i'd say the bar is not too high for you though, considering that a2 was just announced as a1 ;)
[15:29] <ochosi> anyway, time to grab a coffe
[15:29] <ochosi> e
[15:29] <elfy> heh
[15:30] <brainwash> ochosi: can't find anything in launchpad regarding https://www.debian.org/security/2015/dsa-3131
[15:31] <ochosi> well it's 4 days old, and as i said, xdg-utils isn't very actively maintained
[15:31] <ochosi> which is illustrated by the fact that i have two consecutive patches in it
[15:31] <brainwash> but there is a ubuntu security team
[15:31] <ochosi> with half a year diff
[15:32] <ochosi> well, feel free to bring it up with them
[15:32] <brainwash> if we have to inform the team about this stuff, then something is wrong
[15:50] <ochosi> brainwash: why? they're people too
[15:51] <brainwash> people who read the debian security announcements
[15:51] <brainwash> anyway, I filed a report
[16:18] <brainwash> ochosi: ubuntu is not affected, because xdg-utils is old and does not even include the commit which introduces the vulnerability 
[16:18] <ochosi> haha, nice
[16:19] <ochosi> either way, if you have time to prep the SRU for xdg-utils, that'd be great
[16:19] <brainwash> will anyone do the packaging for the timeout patch?
[16:19] <ochosi> packaging?
[16:20] <brainwash> drop the obsolete upstream patch, include the timeout one, create a package
[16:20] <ochosi> well, it has been sponsored/uploaded
[16:20] <ochosi> so yeah, obviously it has been packaged
[16:21] <brainwash> the SRU team will do it for trusty/utopic?
[16:21] <ochosi> yes, that's the idea
[16:21] <ochosi> cause we don't have upload rights for xdg-utils anyhow
[16:21] <brainwash> ok, I'll do the sru then
[16:22] <ochosi> thanks a bunch
[16:22] <ochosi> i gotta go in the next 20mins
[16:22] <brainwash> but first I'll test the vivid package, so it won't be today
[16:22] <ochosi> then i'll be back next week
[16:22] <ochosi> yeah, that's ok
[16:22] <brainwash> ok :)
[16:22] <ochosi> my absence is one reason why i wanted to ask you to look into it
[16:22] <ochosi> just so that things keep moving forward
[16:23] <ochosi> also, you know the bug/patch, so you can formulate the sru
[16:23] <ochosi> so yeah, thanks!
[16:24] <knome> brainwash, if you need help with the SRU (in the case you get stuck), you can ask bluesabre or me
[16:26] <brainwash> that should not be the problem, I was just afraid that I would have to prepare the packages for trusty/utopic too
[16:26] <brainwash> which is a bit messy
[17:41] <brainwash> ochosi: bad news, xdg-screensaver is broken in vivid
[17:41] <brainwash> not my part, but the DE detection
[17:47] <brainwash> somehow caused by dropping the obsolete upstream patch
[20:31] <elfy> evening ali1234 
[20:32] <elfy> so I did run audio bug collect from a live-session, then changed it afterwards to point at indicator-sound instead of alsa
[20:33] <ali1234> looks good
[20:34] <elfy> good 
[20:34] <elfy> referred to the other bug - so I guess anything that the old one included they can find
[20:34] <elfy> not much else I can do :)
[20:34] <ali1234> you could post the crash report for indicator-sound as well
[20:35] <elfy> didn't appear to do that this time - or I confused it by running ubuntu-bug almost immediately 
[20:35] <elfy> but it is easily reproduced :)
[20:35] <ali1234> it's still there in /var/crash
[20:36] <ali1234> i can see the whoopsie errors in your dmesg
[20:36] <elfy> that dmesg is from livesession 
[20:37] <elfy> as I said easily reproduced - just boot the livesession
[20:38] <ali1234> let's see if there's anything on e.u.c.
[20:41] <ali1234> there is a trick you can do to make apport send reports to launchpad instead of e.u.c.
[20:41] <ali1234> can you tell me approximates the last time you submitted a report?
[20:41] <elfy> which is?
[20:41] <elfy> umm
[20:42] <elfy> it was either sometime between 7 and 9:30 am or sometime after 4 pm today 
[20:44] <ali1234> 64 bit?
[20:45] <ali1234>          FLAGRANT SYSTEM ERROR        Computer over.        Virus = Very Yes.     
[20:46] <ali1234> there are no reports for those time periods :(
[20:46] <ali1234> and now the site is down
[20:47] <elfy> was definitely today and I was out between 9:30 and 4 
[20:48] <ali1234> http://askubuntu.com/questions/150476/how-do-i-submit-a-full-bug-report-with-crash-dump-and-steps-to-reproduce
[20:48] <elfy> LP says 4 hours ago actually 
[20:48] <ali1234> if apport is refusing to send the report to the right place
[20:48] <ali1234> no, i don't mean bug report on launchpad
[20:48] <ali1234> i mean when was the last time you sent as automatic error report (which takes no user input other than clicking "send")
[20:49] <elfy> oh - I bet I forgot to do that to this install 
[20:52] <elfy> I did ... 
[20:58] <elfy> ok - done that and also unignored the crash
[21:04] <elfy> ali1234: so I did those things, restarted the indicator, got the pop-up, which is now reporting it to launchpad 
[21:05] <elfy> shall I actually do that - again 
[21:12] <elfy> well I did - currently it's set to private for some reason but bug 1413747
[21:37] <brainwash> ali1234: I was using your xfwm4 zooming feature and noticed that there is a 1px line at the bottom which is not zoomed
[21:39] <brainwash> 1680x1050, but the zooming area is only 1680x1049
[21:41] <ali1234> that is impossible
[21:41] <ali1234> unless you mean it is just a black line
[21:41] <ali1234> even then, still impossible
[21:42] <ali1234> zooming only modifies the transformation parameters
[21:43] <brainwash> interesting, no the it's the actual screen content
[21:43] <brainwash> -the
[21:43] <ali1234> it doesn't touch the source and destination regions at all
[21:43] <ali1234> it zooms the entire composited buffer
[21:43] <ali1234> drawing part of it unzoomed would require two drawing operations and there is only one
[21:44] <ali1234> it could be not redrawing that part of the screen i suppose
[21:44] <ali1234> just leaving the old contents
[21:44] <ali1234> but i think even that is impossible
[21:45] <brainwash> restarted the session and it's still reproducible
[21:46] <ali1234> i can't reproduce it (obviously)
[21:46] <brainwash> I placed a text editor with some text at the bottom to easy spot this strange glitch
[21:47] <ali1234> what happens if you use a video player?
[21:49] <brainwash> it does not update the 1px line while zooming
[21:50] <ali1234> hmm
[21:51] <brainwash> driver related?
[21:52] <ali1234> probably not
[21:52] <ali1234> well, maybe
[21:52] <ali1234> basically i have no idea
[21:56] <brainwash> it's easy to test, so maybe someone else could try and test it
[21:59] <brainwash> I don't know if it worked properly at some point, because I've accidentally triggered zooming and noticed it instantly, because there was some text at the bottom
[22:29] <brainwash> ali1234: works fine with the open source driver
[22:54] <brainwash> interesting.. I lock the screen of my session in VT7 via light-locker. now, the unlock screen aka gtk greeter also spawns in VT7
[22:56] <brainwash> bluesabre: ^ ?
[22:57] <brainwash> if I unlock and lock again, then things will be broken
[22:57] <bluesabre> that's a new one
[22:58] <brainwash> did they break lightdm? :)
[22:59] <brainwash> so you can spawn the greeter in the same VT?
[23:01] <brainwash> currently it's a bug and should not happen, but it seems to work somehow, well temporary
[23:09] <brainwash> ali1234: bug 1413784 any idea?
[23:23] <ali1234> graphical corruption is very common with intel chipsets
[23:26] <brainwash> yes, especially with the "new" accel method SNA
[23:26] <brainwash> fixed upstream https://bugs.freedesktop.org/show_bug.cgi?id=80033
[23:27] <brainwash> reporter is using 14.04
[23:46] <bluesabre> brainwash: lightdm tends to break alot during development cycle... usually test-mode is gone until after last beta