[09:57] <ochosi> brainwash: the screen-blanking happens only on the lock-event and was specifically added to provide screensaver-like functionality. we'll see whether we can do a dpms-off call instead of the blanking, that'd leave the monitor switched off (as happens during the VT switch), resulting in "lock > blank > dpms off" instead of the current "lock > blank > dpms off > blank"
[10:27] <ochosi> pleia2, knome: we could work around the slow submission page in the wiki by moving the "accepted submissions" to a separate page, what do you think?
[10:27] <knome> ochosi, if you think that's needed
[10:27] <ochosi> (accepted submissions being those that 1) don't violate our guidelines and 2) have all the necessary information, incl. license)
[10:27] <ochosi> not sure, it's just a pain to use atm
[10:28] <knome> the worst thing is seeing which attachments are not linked
[10:28] <knome> (that's relatively quick from the wiki's side)
[10:28] <knome> otherwise i don't see a problem
[10:28] <knome> (except that maybe we would like to organize the photos differently when we are deciding about them)
[10:35] <ochosi> ok, let's wait whether submissions stop flowing in
[10:36] <knome> if they don't, well, then it's probably not too awful to submit stuff to the wiki :)
[10:43] <ochosi> yeah, but it also gets increasingly annoying to check the new submissions with a bad connection like mine...
[10:43] <knome> well the "problem" is not actually in the wiki
[10:44] <knome> it's because people upload 5MB images, then the wikimarkup jus stretches them to 250px wide images
[10:44] <knome> if you want to help making the submissions page faster, we should simply tell people to upload a 250px wide preview-image
[10:44] <knome> (and possibly the original file, but not link that; or, upload the original file to another wikipage or service)
[10:53] <slickymaster> good morning all
[10:53] <knome> morning slickymaster 
[10:53] <ochosi> morning slickymaster 
[10:54] <ochosi> knome: not sure, sounds quite elaborate
[10:54] <slickymaster> ochosi, knome, morning
[10:55] <slickymaster> knome: not sure if we did saw this http://irclogs.ubuntu.com/2013/11/15/%23xubuntu-devel.html#t14:53
[10:55] <slickymaster> if you ^ª^
[10:56] <knome> i did
[10:56] <slickymaster> elfy, did you by any chance tried to install today's daily build? I got this https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1252205
[10:56] <slickymaster> knome, any ideas?
[10:59] <knome> slickymaster, sounds like a possible ubiquity problem
[10:59] <knome> eg. not a xubuntu-specific one
[10:59] <slickymaster> knome: yeah, that I know, but I was asking regarding https://bugs.launchpad.net/ubuntu/+source/xubuntu-docs/+bug/1251332,
[11:00] <knome> aha :)
[11:00] <knome> umm,
[11:00] <slickymaster> knome: :)
[11:00] <knome> ask balloons what he thinks
[11:01] <slickymaster> okie dokie, I'll do it
[11:01] <knome> ta
[11:01] <knome> i'll follow up if needed
[11:02] <slickymaster> knome: I'll report you any away
[13:02] <knome> bbl
[14:06] <brainwash> will the xfce packages get updated/synced soon in trusty?
[14:07] <brainwash> the 4.12 PPA does not offer packages for trusty yet
[14:30] <ochosi> hi micahg_mobile :)
[14:32] <micahg_mobile> Hi, i hope my crazy work schedule is done for the time being so i can get back to Xubuntu 
[14:40] <brainwash> ochosi: so the blanking change does reduce the amount of flicker/screen backlight weirdness on your system?
[14:41] <ochosi> micahg_mobile: that sounds nice!
[14:41] <ochosi> brainwash: yeah, well it's as i described before > blank > dpms off > blank
[14:42] <ochosi> it's hard to imagine that a single X call would slow down the switching to the greeter noticeably
[14:43] <brainwash> dpms off ?
[14:43] <ochosi> dpms is the power-management of the screen
[14:43] <ochosi> means, not just blank, but switched off
[14:44] <brainwash> I know that
[14:44] <brainwash> but why?
[14:44] <ochosi> the dpms off happens during the VT switch
[14:44] <ochosi> it's out of our hands
[14:44] <brainwash> oh
[14:45] <ochosi> ok, so explaining again: screensaver-timeout > blank screen (3s or so) > dpms off (VT switch 1sec) > blank screen (until the user touches mouse or keyboard)
[14:48] <brainwash> so the screen should be blank after screen lock?
[14:48] <ochosi> yeah
[14:48] <ochosi> as with xscreensaver
[14:48] <brainwash> o.o
[14:48] <ochosi> or any screensaver
[14:49] <brainwash> not here, I lock the screen manually and the greeter is visible
[14:49] <ochosi> are you using the latest revision of the greeter?
[14:49] <ochosi> or the daily PPA
[14:50] <brainwash> Installed: 1.6.1+146+97~ubuntu13.10.1
[14:51] <ochosi> should work with that one
[14:51] <ochosi> (i'm still on 1.6.1+145, but the last commit was for the language menu)
[14:52] <ochosi> and you lcok with "light-locker-command -l"?
[14:52] <brainwash> yes
[14:52] <ochosi> what version of light-locker?
[14:52] <brainwash> Installed: 1.0.0+2111+4~ubuntu13.10.1
[14:53] <ochosi> ok, you're testing on saucy though, not trusty right?
[14:53] <ochosi> cause so far i've only tested saucy
[14:53] <brainwash> saucy
[14:53] <ochosi> strange strange
[14:53] <ochosi> should work
[14:53] <brainwash> it's the intel based system
[14:53] <ochosi> no wonder you didn't notice an improvement then...
[14:54] <ochosi> well the code isn't very graphic card specific
[14:54] <ochosi> it's a general X call
[14:54] <ochosi> or xlib to be exact
[14:54] <brainwash> so it most likely blanks the screen and unblanks it immediately 
[14:55] <ochosi> what does "xset q" tell you about the screen saver?
[14:56] <brainwash> http://lpaste.net/95860
[14:56] <ochosi> (oh, and i assume you don't use any weird lightdm-version, right?)
[14:56] <ochosi> could you try this:
[14:57] <ochosi> xset s 600
[14:57] <ochosi> and then lock the screen
[14:58] <ochosi> i guess if blanking is completely disabled forcing the screensaver might not work
[14:59] <brainwash> negative, the strange thing is that locking the screen blocks keyboard shortcuts in vt7
[14:59] <brainwash> when I return back
[14:59] <brainwash> might be related
[15:00] <ochosi> yeah, that seems fishy
[15:00] <ochosi> but i wouldn't know what it's related to tbh
[15:01] <brainwash> I'll test it on my trusty test system too, not sure if the screen blanks on this system or not
[15:01] <brainwash> most likely it does not either
[15:02] <brainwash> the pc is currently in use :/
[15:02] <ochosi> did you check again after doing xset s 600 with xset q to see whether blanking is now enabled?
[15:02] <brainwash> yes, no change
[15:02] <ochosi> that's weird
[15:02] <ochosi> then obviously the whole test didn't do anything
[15:02] <brainwash> we need 1-2 more testers :)
[15:03] <ochosi> as long as blanking is disabled, i wouldn't expect it to work
[15:03] <ochosi> well we simply need to switch on blanking for you
[15:03] <ochosi> then it should work
[15:05] <brainwash> xset s 2 blanks the screen after 2 sec
[15:06] <ochosi> ok
[15:06] <ochosi> then light-locker should automatically take you to the lock-screen
[15:06] <ochosi> unless you edited the desktop file or the update didn't change it for some reason
[15:06] <brainwash> I mean it blanks the current x session after 2 sec, not the new one created by light-locker
[15:07] <brainwash> I'm still a bit confused, maybe I'll understand the problem after doing some more testing
[15:08] <ochosi> and xset q tells you that the blanking-value is changed too?
[15:08] <brainwash> timeout:  600    cycle:  0
[15:09] <brainwash> but this does not affect vt8, right?
[15:10] <ochosi> ah, hm, that's probably true
[15:10] <ochosi> i guess we have to find out how to set this value so that it gets remembered
[15:10] <ochosi> for all x sessions
[15:10] <ochosi> probably with sudo, but i'm not sure
[15:11] <brainwash> via lightdm maybe?
[15:12] <ochosi> no, lightdm respects the global default values for X afaik
[15:12] <brainwash> yes, I mean an interface to change them via lightdm
[15:15] <ochosi> ah, hm, not sure
[15:15] <ochosi> anyway, i'll have to investigate this later or tomorrow
[15:16] <ochosi> my first instinct would be to run xset with sudo and then restart and see whether the values stuck
[15:16] <ochosi> (normal xset isn't remembered)
[15:16] <ochosi> if you have a custom xorg.conf, check that for configuration
[15:34] <brainwash> ochosi: same for my trusty/AMD system, the screen unblanks immediately and reveals the greeter
[15:35] <slickymaster> knome: ping
[16:46] <slickymaster> bbl
[16:51] <brainwash> ochosi: ok, found the culprit
[16:51] <brainwash> ochosi: the issue is related to bug 1251431
[16:53] <brainwash> the background gets set twice, and the screen is forced to blank twice also, maybe there is something wrong a hint or flag
[16:54] <brainwash> setting the background another time might also reset the state
[16:56] <brainwash> (calling the root surface function)
[20:41] <ochosi> brainwash: tbh i don't think that's related
[20:42] <ochosi> bbl
[20:43] <brainwash> ochosi: works for me
[20:43] <brainwash> if only the background specified in the conf file gets displayed or the user one
[20:45] <brainwash> but calling the root surface function twice unblanks the screen
[20:49] <brainwash> ochosi: btw can you triage the linked lp report please?
[21:06] <knome> lderan, or, we should rather discuss that here :)
[21:06] <lderan> sounds good to me
[21:07] <knome> lderan, aha, so basically: the vote results are shown newest-first in the wiki output
[21:07] <knome> would make more sense if they were chronological top-down
[21:07] <lderan> sounds easy enough to do
[21:07] <knome> yep
[21:07] <knome> just a small thing i didn't notice until we had loads of votes in the last meeting :)
[21:08] <lderan> :P
[21:08] <knome> https://wiki.ubuntu.com/Xubuntu/Meetings/Archive/Minutes/2013-11-14 for a real life example
[21:10] <lderan> okay, just need to reverse the items. shall do so now
[21:11] <lderan> shall also make a commit and poke the alan some more with the new changes
[21:12] <knome> :)
[21:12] <knome> ta
[21:13] <lderan> no problemo