| Unit193 | * Move laptop-detect from /usr/sbin to /usr/bin - Wed, 08 Mar 2017 00:59:54 +0100 | 00:37 |
|---|---|---|
| Unit193 | Debian #894481 | 01:03 |
| ubottu | Debian bug 894481 in numlockx "numlockx: `laptop-detect` has moved from /usr/sbin to /usr/bin" [Normal,Open] http://bugs.debian.org/894481 | 01:03 |
| Unit193 | https://packages.qa.debian.org/g/gtk-theme-config/news/20180331T035526Z.html | 04:00 |
| -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: tumbler 0.2.1 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-tumbler-0-2-1-released-tp50878.html (by Ali Abdallah-4) | 07:55 | |
| -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: tumbler 0.1.33 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-tumbler-0-1-33-released-tp50879.html (by Ali Abdallah-4) | 08:22 | |
| flocculant | if I didn't know that our iso was suffering from this bluetooth issue - I would just assume that I can't install xubuntu and would go looking for something that worked :( | 09:27 |
| flocculant | willem: thanks :) | 09:36 |
| willem | flocculant, ?? I don't think I complained about bluetooth lately; but then again I'm old and may have forgotten I did... | 10:52 |
| willem | hmm, i did: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349, but that was quite some time back | 11:34 |
| ubottu | Launchpad bug 1490349 in bluez (Ubuntu) "15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted" [High,Invalid] | 11:34 |
| flocculant | willem: we have one at the moment that leads to a 75s timeout in I assume anything with no bluetooth | 11:43 |
| willem | I read about that one | 11:47 |
| willem | I think I did report the slow boot after first install | 11:47 |
| flocculant | willem: also - the thanks were for the reply to the testing soon e-mail ;) | 12:08 |
| willem | ah, right! I didn't realize that. | 12:09 |
| flocculant | I only just did when I read you again :p | 12:09 |
| willem | All I saw was your line about bluetooth and thanking me | 12:09 |
| willem | I hope my e-mail helps, though. | 12:11 |
| flocculant | yep - always useful to get comments like that from 'normal' testers :) | 12:15 |
| willem | Never been called normal before | 12:16 |
| flocculant | :D | 12:16 |
| willem | makes a change I guess ;-) | 12:16 |
| flocculant | I've not talked to you for quite long enough to tar you with the 'crazy people who test things' brush yet lol | 12:17 |
| flocculant | if you're still putting up with us mid- Cantankerous Cicada cycle - I'll call you crazy :) | 12:18 |
| willem | I'll try to live up to your expectations, then | 12:24 |
| flocculant | :) | 12:28 |
| ali1234 | funnily enough i read that bug yesterday | 12:42 |
| ali1234 | apparently it is not a bug | 12:43 |
| ali1234 | flocculant: i wish to complain | 13:34 |
| ali1234 | the iso tracker tests ask me to verify that "The slideshow is entirely in your language" | 13:34 |
| ali1234 | but the xubuntu slideshow has that slide with "hello" written in all different languages | 13:35 |
| ali1234 | therefore i have to fail it :) | 13:35 |
| willem | ali1234, :-) I was tempted to do the same first time I came across that slide ;-) | 13:39 |
| TJ- | Anyone know of a better channel to catch hold of devs that understand the light-locker<>lightdm interactions ? | 13:56 |
| bluesabre | TJ-: #lightdm would probably be best. The maintainer of light-locker comes and goes at #xfce-dev | 15:03 |
| TJ- | thanks. | 15:03 |
| TJ- | I'm sticking in some gs_debug() now to try to trace the lid-closed suspend/resume path | 15:04 |
| TJ- | Looks like the lid-closed>suspend>resume>blank-user-session-vt is a timing issue; with a few debug options and light-locker --debug >/tmp/log I cannot reproduce it | 16:14 |
| TJ- | Getting more interesting. Even without --debug enabled, my local build of light-locker (with embedded gs_debug() statements) will not fail, but the system's version will. So I've got 3 possible diffs: 1) my 5 gs_debug() statements 2) my binary isn't stripped 3) pssobitl different build options | 16:41 |
| TJ- | And just found another data-point that is a workaround. When the blank user VT is present, connecting charger (PM not set to suspend when lid-closed on AC) and then closing and re-opening lid, the VT is active and visible again | 16:43 |
| ali1234 | good news: tumblerd's exif orientation code is not broken, it's my images :) | 19:30 |
| ali1234 | and also imagemagick is partly to blame | 19:31 |
| === GridCube_ is now known as GridCube | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!