[00:01] <bluesabre> ali1234: I don't suppose you know of min/max mouse acceleration options with xorg? Can't seem to find any docs on it. Related to https://bugzilla.xfce.org/show_bug.cgi?id=12622
[03:41] <ali1234> i don't know but the acceleration slider in mouse settings seems to have no effect for me
[09:53] <bluesabre> ali1234: that's seemingly related to libinput
[10:06] <brainwash> bluesabre: having it built with libinput support in some ppa would help to test it
[11:22] <TJ-> This week I discovered a security vulnerability in the screen-lock/hide desktop functionality. When there are multiple X screens the lock only operates on :0.0. Contents of other X screens remain visible. This reminded me of the same bug I reported in 2013 (!) in KDE which has still not been fixed. Where best to report this against? Presumably upstream but not sure which project/package. ( Bug #1264821
[11:22] <TJ-> )
[11:40] <bluesabre> TJ-: light-locker would be the project I believe, https://github.com/the-cavalry/light-locker would be the upstream
[11:42] <ochosi> (fairly dormant upstream, tbh)
[11:44] <TJ-> hmmm, it looks like it should just be dropped! combined with the other LL bug where lid-induced suspend results in 'dead' tty on resume!
[11:45] <TJ-> It really annoys me, devs working on core display technology don't test on multiple X screens - which is a very common scenario in enterprises especially.
[11:55] <TJ-> I'll look at it in more depth next week
[11:56] <bluesabre> I've considered in the past porting gnome-screensaver to xfce
[11:56] <bluesabre> works well as a lock screen, and switch user works
[11:57] <bluesabre> not tried with multiple X screens, but likely has better support than light-locker
[11:57] <bluesabre> even though ll was originally based on it
[12:06] <ochosi> you can simply go to one of the first revisions when i was still contributing a bit more
[12:06] <ochosi> that's basically gnome-screensaver without gnome depends
[12:06] <ochosi> (and that was my original idea)
[12:08] <bluesabre> neat
[12:08] <ochosi> it was usable and working
[18:26] <brainwash> bluesabre: I'm curious about this one also https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/xfce4-settings&id=a1a6ca07f0577a62b8e6679ee023eea774502d8e
[18:27] <brainwash> this was linked in a launchpad report
[18:28] <brainwash> what would not building with upower support break?
[18:32] <brainwash> xubuntu users often mention the workaround to edit /etc/UPower/UPower.conf, and do IgnoreLid=false ==> IgnoreLid=true
[18:32] <brainwash> as workaround for that black screen thing
[18:38] <bluesabre> brainwash: I don't know the answer to that. As far as I know, some laptops report to Upower one value, while others do the reverse
[18:38] <bluesabre> ochosi may know more
[18:39] <brainwash> the archlinux people do not seem to have any major problems with their builds
[18:40] <brainwash> at least they did not revert that linked commit
[18:41] <brainwash> I'd think that systemd can handle those events
[18:41] <brainwash> lid close/open
[18:41] <TJ-> interesting; that's the bug I originally reported. Not revisited it since, I just manually suspend before closing the lid
[18:42] <brainwash> you mean bug 1431149 ?
[18:42] <TJ-> Bug #1759950
[18:43] <brainwash> still open
[18:43] <brainwash> upstream I mean
[18:44] <TJ-> light-locker upstream is basically abandonware so far as I could tell
[18:44] <brainwash> it does look like it
[18:45] <TJ-> I did a lot of source-code diving/debugging and narrowed it down some, but never got to looking at upower. If I can find some time this week I'll investigate that lead and report back in my bug report
[18:45] <brainwash> I recall that getting rid of VT switching was on the roadmap
[18:45] <brainwash> sadly, no progress
[18:47] <TJ-> what I found was that in the LidClose event case, the number of Close events didn't match the number of Open events after resume, which seemed to leave the X server state as DPMS off or something. My memory is quite sketchy without re-reading my notes
[18:47] <brainwash> is that with xubuntu only?
[18:48] <TJ-> yes
[18:48] <TJ-> I also noticed it seems to be timing related, in that for me at least, faster CPUs seemed to suffer it more than slower ones. Not sure if that was just co-incidence though - I didn't do rigorous tests of that!
[18:49] <brainwash> maybe building -settings without upower could somehow help
[18:50] <brainwash> I assume that would mean that upower is not pulled in anymore
[18:50] <brainwash> wait. the power-manager needs it still, or?
[18:51] <brainwash> this really requires a proper investigation =S
[18:54] <TJ-> looking at the source, it provides a dbus service for x-p-m 
[19:01] <brainwash> ah
[19:02] <brainwash> does x-p-m really need that service?
[19:02] <brainwash> I assume that it can fall back to systemd
[19:03] <TJ-> I've just spotted a bug in upower, reporting the battery state as 208% of design capacity
[19:03] <brainwash> that's called 'supercharged'
[19:05] <TJ-> note line 45 vs line 5: http://paste.ubuntu.com/p/bphCcjmFbd/
[19:12] <Spass> on 18.10 I have problems with whoopsie - https://ibb.co/jYT0ue
[19:14] <Spass> I think it's when I want to report that "once a day" bug with cups-browsed
[19:20] <Unit193> < bluesabre> works well as a lock screen, and switch user works   I think you just described xscreensaver? :P
[19:20] <bluesabre> Unit193: didn't you share that xscreensaver sometimes doesn't show for folks now :D
[19:22] <Unit193> Oooh dang, you do read me. :3  And yeah, login screen tends to flash for a second then goes away, but esc out of it and move mouse again to bring it up.
[19:22] <Unit193> And only Xfce folks! :P
[19:23] <knome> Unit193's new motto: "Use GNOME, people!"
[19:23] <bluesabre> my new motto: Use knome, people!"
[19:23] <knome> uhhh
[19:23] <bluesabre> :D
[19:23] <Unit193> Pretty sure that'd be the last thing I'd say.
[19:23] <bluesabre> :D
[19:23] <knome> i'm sure you didn't intend it to be interpreted as i did..
[19:24] <bluesabre> probably not
[19:24] <knome> (:
[19:55] <Unit193> Besides, there's Xfce people here, that might be an Xfce specific problem, maybe one of them can fix it! :D
[20:02] <bluesabre> :D