[01:14] <furkan> so it seems that the problem with my multimedia keys might be related to udev or X
[01:14] <furkan> after suspend/resume, this is what i see in my X log:
[01:14] <furkan> [  4111.568] (EE) evdev: Microsoft Microsoft® 2.4GHz Transceiver v9.0: Unable to open evdev device "/dev/input/event6".
[01:14] <furkan> [  4111.568] (EE) PreInit returned 2 for "Microsoft Microsoft® 2.4GHz Transceiver v9.0"
[01:14] <furkan> same error if i unplug the USB receiver and plug it back in
[01:15] <furkan> any ideas on how i can find the culprit? it was working fine with Ubuntu 15.10
[02:11] <RAOF_> furkan: “PreInit returned 2” looks like a pretty good lead...
[02:14] <RAOF> Survey suggests that this is BadValue...
[02:15] <RAOF> furkan: Oh, right. That's caused by “unable to open evdev device”
[02:16] <RAOF> furkan: Is that *all* the log?
[02:16] <furkan> RAOF: no i can share the whole thing, but that was the error
[02:17] <RAOF> Errors are often caused by warnings earlier :)
[02:17] <RAOF> Pastebin the whole log and I'll have a quick look at it.
[02:17] <furkan> ok just 1 sec then because i'll have to do another suspend/resume, since i restarted
[02:18] <RAOF> Oh, so it works fine at startup?
[02:18] <furkan> yeah
[02:20]  * RAOF guesses that this is going to be logind integration fallout
[02:25] <furkan> ok got the log, pastebining it now
[02:26] <furkan> RAOF: here it is http://pastebin.com/XNFwSp5S
[02:28] <furkan> that's a fresh boot followed by a suspend/resume
[02:29] <RAOF> “[    12.122] (EE) systemd-logind: failed to get session: PID 1038 does not belong to any known session” is quite interesting.
[02:29] <RAOF> What strange thing are you doing? :)
[02:29] <furkan> i have no idea lol..
[02:29] <furkan> all i did was reboot, log in
[02:29] <furkan> test the volume buttons to make sure they were working
[02:29] <furkan> and then suspend/resume
[02:30] <furkan> and then of course test them again to verify that they're no longer working
[02:30] <RAOF> Yeah, that's preeety odd.
[02:30] <furkan> so i'm checking pid 1038
[02:30] <furkan> root      1038 11.8  0.7 660072 131116 tty7    Ssl+ 21:23   0:48 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[02:30] <RAOF> It's almost certainly Xorg
[02:31] <furkan> yeah
[02:31] <RAOF> :)
[02:31] <RAOF> It happily re-adds *most* of your wireless devices, just not the piece that's the multimedia keys.
[02:31] <RAOF> ???
[02:31] <furkan> yeah
[02:31] <furkan> it's a keyboard + mouse combo
[02:31] <furkan> MS Sculpt Ergonomic
[02:32] <furkan> mouse works fine, and keyboard also works fine apart from the volume keys
[02:32] <RAOF> It's not clear what's going wrong here; it might even be a kernel issue.
[02:32] <furkan> i tried booting into an older kernel though, and it still persists
[02:32] <furkan> not sure if the errors are the same
[02:32] <RAOF> Good thinking; probably not that then.
[02:33] <furkan> i also tried downgrading systemd/udev but dealing with the dependencies was hell
[02:33] <RAOF> File a bug against xserver-xorg-input-evdev. If you want to do a little light debugging, the relevant code is in src/evdev.c:EvdevOpenDevice
[02:33] <furkan> interesting, thanks for the tip
[02:33] <furkan> should i file it on launchpad? or upstream?
[02:34] <RAOF> Launchpad
[02:34] <furkan> alright will do, thanks :)
[02:34] <RAOF> If you've tried with xf86-input-evdev from trunk, you can also file upstream :)
[02:34] <RAOF> But certainly Launchpad.
[02:35] <furkan> i guess before i do that i'll also boot from a live ISO
[02:35] <furkan> just to make sure that my configuration isn't somehow broken
[02:55] <RAOF> Not a bad idea.
[05:37] <tjaalton> furkan: does that device exist after resume? and test if it works with evtest
[05:37] <tjaalton> from a vt
[05:37] <furkan> tjaalton: no the device disappears after resume
[05:38] <tjaalton> x doesn't do that
[05:39] <tjaalton> reattaching doesn't help
[05:40] <furkan> sorry i don't understand, you mean if the device disappears the problem lies somewhere else?
[05:40] <tjaalton> yes
[05:40] <furkan> oh ok i see
[05:40] <furkan> so udev or something?
[05:41] <tjaalton> oh and the other one was a question
[05:41] <furkan> and i tried evtest in a VT
[05:41] <furkan> hold on let me copy it
[05:42] <furkan> it shows something like ^[[25@
[05:42] <furkan> (that's from memory since i can't copy/paste from a VT)
[05:42] <furkan> let me just write it on some paper to make sure
[05:44] <furkan> yeah it's ^[[25~, ^[[26~, and ^[[[D, for mute, vol-, and vol+
[05:46] <furkan> but it doesn't show the event time and stuff
[05:46] <furkan> like it does for all the other keys
[05:47] <furkan> oh and no, reattaching the USB receiver doesn't help
[05:58] <tjaalton> so the event device is there after suspend?
[05:59] <furkan> no the device is gone
[05:59] <furkan> and with evtest, when i make keystrokes i get output like this for all the keys other than the volume ones:
[05:59] <furkan> Event: time 1456725562.966902, -------------- SYN_REPORT ------------
[05:59] <furkan> Event: time 1456725563.022896, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7002c
[05:59] <furkan> Event: time 1456725563.022896, type 1 (EV_KEY), code 57 (KEY_SPACE), value 0
[06:00] <furkan> but for mute/vol-/vol+ i get nothing like that, just ^[[25~, ^[[26~, and ^[[[D
[06:00] <furkan> so it seems the keyboard sends something, but no event is registered?
[06:00] <tjaalton> but how can you run evtest if the device is gone?
[06:01] <furkan> i think the keyboard shows up as more than 1 device
[06:01] <furkan> even in evtest it's listed twice
[06:01] <tjaalton> sure, but then you can't test the one that is gone right?
[06:03] <furkan> oh right, yeah, i was testing the remaining ones
[06:03] <furkan> so i'm looking in /dev/input/by-path
[06:03] <furkan> there's 3 symlinks, pci-***-event-kbd
[06:03] <furkan> *** = some long number
[06:04] <furkan> symlinked to ../event2, ../event4, and ../event6
[06:04] <furkan> and the event4 symlink is broken, of course, since it's no longer there
[06:05] <furkan> so should i file a bug against udev, then?
[06:09] <tjaalton> what kernel used to work?
[06:09] <tjaalton> 4.2 from 15.10?
[06:10] <furkan> yeah 4.2
[06:10] <furkan> but even if i boot up w/ 4.2 it doesn't seem to fix it
[06:11] <tjaalton> the exact same 4.2?
[06:11] <furkan> yeah i tried going even further back to 3.19, from 15.04
[06:11] <furkan> i didn't purge my 15.04 + 15.10 kernels
[06:11] <tjaalton> so then maybe udev rhen
[06:11] <tjaalton> -then
[06:12] <furkan> i tried downgrading udev to test, but so many dependencies
[06:12] <tjaalton> having issues of my own right now, limited to just my phone atm :P
[06:12] <furkan> oh sorry, i hate typing on my phone lol
[06:14] <tjaalton> some local network snag
[06:15] <furkan> i may try to see if i can downgrade udev later, but i'll have to manually download a whole bunch of packages (systemd, xorg, and some other misc packages)
[06:15] <furkan> last time i tried i did 15 packages but there were still more that were broken
[06:16] <furkan> downloaded them all individually from launchpad
[06:21] <tjaalton> maybe ask pitti when he's around
[16:06] <ricotz> tjaalton, hi, regarding your nvme issues, was this fixed and are the current daily iso working for you?
[16:38] <tjaalton> ricotz: i'm not sure, haven't tried images since
[17:01] <ricotz> tjaalton, ok
[17:05] <tjaalton> but i upgraded a machine to xenial which needs it and it boots up fine
[17:12] <ricotz> tjaalton, used trusty and upgraded to 4.5rc6 due missing hardware support, and this triggers the missing nvme problem, so initramfs in trusty still needs fixing 
[17:13] <tjaalton> oh yes
[17:13] <tjaalton> there is a bug too, somewhere
[17:15] <ricotz> tjaalton, the xenial images simply hang on boot (black screen), and going a bit further with nomodeset
[17:16] <ricotz> with i7-6560U
[17:16] <ricotz> (trusty-daily boots and works)
[17:22] <tjaalton> hmm ok, i can test tomorrow
[17:23] <tjaalton> which kernel does it have?
[17:25] <tjaalton> assuming 4.4.0-8 so no i915_bpo yet
[17:26] <ricotz> tjaalton, I guess not
[17:27] <ricotz> https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/log/?h=master-next
[17:28] <tjaalton> yeah it's there, -9 should happen today
[17:28] <tjaalton> oh, tagged already