[00:32] <furkan> does anybody here have a copy of a 16.04 Alpha 1 ISO image? any flavour would do...
[00:41] <ChibaPet> furkan: http://cdimage.ubuntu.com/daily-live/current/ http://cdimage.ubuntu.com/ubuntu-server/daily/current/
[00:42] <furkan> ChibaPet: thanks but i was looking for a copy of the initial alpha 1 release, not the current daily build
[00:43] <furkan> there's a regression that i'm trying to narrow down
[00:43] <ChibaPet> furkan: The changes between then and now would constitute bug fixes.
[00:43] <ChibaPet> ah, gotcha
[00:43] <furkan> and it's proving too painful to work backwards and downgrade individual packages
[00:43] <ChibaPet> Alright, bug fixes and regressions then. :P
[00:43] <furkan> my volume keys stop working after suspend/resume
[00:43] <furkan> :(
[00:44] <ChibaPet> Oh, that's odd.
[00:44] <ChibaPet> USB keyboard, out of curiosity?
[00:45] <furkan> yeah, USB
[00:45] <ChibaPet> Unplugging and replugging ought to help.
[00:45] <furkan> just tried it right now, doesn't seem to have had an effect
[00:45] <ChibaPet> USB keyboards with multimedia keys present a distinct UHID for the multimedia keys. I haven't seen sleep mess that up, but as a temporary workaround, it shoul reinitialize and reattach if you re-plug.
[00:45] <ChibaPet> hrm
[00:46] <ChibaPet> The other thing to look at is xev output.
[00:46] <furkan> that's another thing i was playing with a while back
[00:46] <ChibaPet> I don't use Unity here, so I just catch the keystrokes in my window manager to process, but ... I'll try to remember to check xev on my wife's Unity once it's done updating.
[00:47] <furkan> it doesn't give any output for the volume keys when i just run xev
[00:47] <ChibaPet> hrm
[00:47] <furkan> but there was another tool too let me check what it was...
[00:47] <ChibaPet> I get this, not that it particularly helps you: https://bpaste.net/show/eb59011f0382
[00:47] <ChibaPet> as an example
[00:48] <furkan> yeah that's what i get too when it's working normally
[00:48] <furkan> but there's this other tool, evtest
[00:48] <ChibaPet> Anything in dmesg noting a detach?
[00:48] <ChibaPet> Oh, I'm not familiar with that. Will have to learn about it.
[00:48] <furkan> right now i'm not getting any output in either of them
[00:49] <furkan> but if i remember correctly, i have to be running both of them simultaneously to get any output for the volume keys... it's strange
[00:49] <furkan> and no nothing like that in dmesg
[00:49] <ChibaPet> How about in /var/log/Xorg.0.log?
[00:50] <furkan> no "detach" in there either
[00:50] <ChibaPet> Anything about evdev that looks relevant, though?
[00:51] <furkan> hmmm
[00:51] <furkan> there's quite a bit in here about evdev, trying to read through it
[00:53] <furkan> this seems to be the only error, and it looks like it happened after the suspend/resume: [    48.425] (EE) evdev: Microsoft Microsoft® 2.4GHz Transceiver v9.0: Unable to open evdev device "/dev/input/event6".
[00:53] <furkan> dunno if that's relevant
[00:54] <ChibaPet> That seems like a BlueTooth device or something.
[00:54] <furkan> just a Microsoft nano-receiver
[00:54] <furkan> it's an MS wireless keyboard
[00:54] <ChibaPet> Here's someone futzing with multimedia keys - maybe something in there will spark an idea: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/44169
[00:55] <ChibaPet> Wait, it's a wireless keyboard?
[00:55] <furkan> yeah wireless keyboard + mouse combo
[00:55] <ChibaPet> That's... almost certainly your multimedia device then.
[00:55] <ChibaPet> Thought you said it was USB. Anyway...
[00:55] <furkan> oh, yeah it's USB but it's a USB wireless receiver
[00:55] <ChibaPet> I'd bet that event6 is where the multimedia uhid is attaching.
[00:55] <furkan> not built-in bluetooth or anything
[00:56] <ChibaPet> kk, I've seen those
[00:56] <furkan> hmm
[00:56] <ChibaPet> So, when you try detaching/reattaching, are you just toggling the keyboard, or pulling the USB thing? Just be interesting to see if that matters.
[00:56] <ChibaPet> I'd assume pulling the USB adapter would give you a full reset, but we're touching on stuff where I'm insufficiently familiar to catch subtleties.
[00:57] <furkan> i pulled the USB receiver out and plugged it back in
[00:58] <furkan> interesting bug report
[00:58] <furkan> pretty old though, from back in 2006-2008
[00:58] <ChibaPet> Hrm. I heard this odd flopping noise, and it was my two year old unloading a bookcase onto the floop, book by book.
[00:58] <furkan> in my case it was working fine with Ubuntu 15.10, and stopped after the upgrade to 16.04
[00:58] <ChibaPet> floor
[00:59] <furkan> haha
[00:59] <ChibaPet> Yeah, not saying it's the same. Just stuff to look at.
[00:59] <furkan> but yeah that looks interesting
[01:00] <ChibaPet> The closest I got to digging into evdev was when I was trying to get my USB keyboard to work under FreeBSD, which just presents the raw uhid. It was the frist time I understood that the silly keyboard presents multiple devices to the system.
[01:00] <furkan> so it looks like in /dev/input i don't have an event6
[01:00] <furkan> i should try rebooting and see if it comes back
[01:02] <ChibaPet> That seems extreme.
[01:02] <ChibaPet> udev ought to be creating things like that as devices that need them are plugged in.
[01:02] <ChibaPet> ALSO... It might get a name other than event6 on re-insertion.
[01:02] <ChibaPet> I'd watch dmesg and watch the contents of /dev as you pull the plug and re-insert.
[01:03] <ChibaPet> Alright, I need to clean up books and finish working on my wife's machine. I'll be back later. Sorry I don't have any more direct help.
[01:03] <furkan> i just tried unplugging and plugging back in
[01:03] <furkan> again
[01:03] <furkan> and same error
[01:03] <ChibaPet> Anything interesting?
[01:03] <ChibaPet> hrm
[01:03] <furkan> [  4111.568] (EE) evdev: Microsoft Microsoft® 2.4GHz Transceiver v9.0: Unable to open evdev device "/dev/input/event6".
[01:03] <furkan> [  4111.568] (EE) PreInit returned 2 for "Microsoft Microsoft® 2.4GHz Transceiver v9.0"
[01:04] <furkan> but hey that's progress at least.. i hadn't noticed that before
[01:04] <furkan> thanks for the help :)
[01:04] <ChibaPet> Mm, and it's almost certainly directly related.
[01:04] <ChibaPet> sure - please tell us what you find, as I'd be interested in knowing what it was
[01:04] <furkan> will do, if there is any progress :)
[02:07] <drhalan1> hey. is there anything I have to do for resolvconf to read stuff in /etc/network/interfaces?
[02:07] <drhalan1> is xenial even still using resolvconf?
[02:10] <drhalan1> anyways my problem: putting an entry in /etc/resolv.conf works. putting the same thing in /etc/network/interfaces doesn't
[02:10] <drhalan1> (even after a reboot)
[02:20] <ChibaPet> drhalan1: You put resolvconf lines into interface descriptions.
[02:20] <drhalan1> i put °dns-nameservers° instead of °namerserver"
[02:20] <ChibaPet> Correct.
[02:20] <ChibaPet> And dns-search.
[02:24] <drhalan1> doh dns-search fixed it
[02:24] <drhalan1> thanks ChibaPet
[02:24] <ChibaPet> cool
[02:24] <ChibaPet> sure thing
[02:53] <Fudge> you can use two hostnames with search in resolv.conf i have my isp and my local network to resolve local hostnames from my gateway
[02:54] <ChibaPet> I think you can go up to six, maybe more.
[02:54] <ChibaPet> There's a cap that's smaller than what I could really use, but, eh.
[03:23] <drhalan1> ChibaPet: maybe you can help me with this issue too? http://pastebin.com/1damUL2M
[03:24] <drhalan1> not sure why i need to call ifup before resolvconf works...
[03:28] <drhalan1> i guess it is due to manual...but resolvconf should still setup dns...
[10:05] <lordievader> Good morning.
[10:13] <Fudge> hi cobber
[10:13] <Fudge> still having dhclient probs, but my buddy with exact same setup isnt, so what have i ddone differently
[10:15] <lordievader> Fudge: Tcpdump it, do you get replies on your dhcp requests?
[10:17] <Fudge> listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
[10:17] <lordievader> No need to paste the entire output here ;)
[10:18] <Fudge> if i run dhclient eth0 manually i get an ip, but when i leave it to expire in 700seconds or what ever the lease time is, i dont get a new one
[10:19] <lordievader> Tcpdump it and watch the logs when that happens.
[10:19] <Fudge> ok
[10:21] <Fudge> bound to 203.206.58.81 -- renewal in 6355 seconds.
[10:21] <lordievader> Time for coffee ;)
[10:24] <Fudge> lol
[10:24] <Fudge> ill prob be in bed then damn
[10:24] <lordievader> Not if you drink your coffee :P
[10:24]  * lordievader slides Fudge a fresh cup of coffee
[10:24] <Fudge> i ran out, i could brew some though
[10:28] <Fudge> cheers
[11:16] <Fudge>   ok using his rules too
[11:24] <lordievader> ?
[11:25] <Fudge> iptables
[11:49]  * lordievader is confused
[11:49] <lordievader> What does iptables have to do with this?
[13:16] <BluesKaj> Hey folks
[14:48] <mayhem> will mir+unity8 be shipped with 16.04?
[14:48] <lotuspsychje> !info unity8-desktop-session-mir | mayhem
[14:49] <mayhem> yeah, I was going through it..
[14:49] <k1l> mayhem: they are already in 15.10.
[14:50] <mayhem> sorry, what I meant is that is there a separate version planned for 16.04 (with mir+unity8)
[14:52] <k1l> mayhem: no
[14:54] <mayhem> :k1l thanks for the confirmation
[16:13] <nicomachus> I decided to take the beta plunge on my HTPC finally. I tried to upgrade with do-release-upgrade -d, but it's unable to authenticate module-init-tools and aborts the process.
[16:24] <lotuspsychje> nicomachus: from wily?
[16:24] <nicomachus> Yea.
[16:25] <lotuspsychje> nicomachus: fresh install instead, i had kernel issues from wily to xenial upgrade
[16:25] <nicomachus> I guess there's a way to create a file to allow unauthed, but I'm not sure that's a good idea.
[16:26] <lotuspsychje> nicomachus: i ended up with 4.2 kernel where i should have higher on xenial
[16:26] <lotuspsychje> nicomachus: mixxed things up
[16:26] <lotuspsychje> nicomachus: fresh all working like a charm now
[16:27]  * nicomachus sighs
[16:27] <nicomachus> okkkkkk
[16:27] <nicomachus> guess I need to backup and do that then.
[16:31] <lotuspsychje> nicomachus: youl be happy with a fresh one mate :p
[16:31] <nicomachus> Probably.
[16:34] <nicomachus> thank god for gigabit upload speeds to google drive.
[16:51] <lotuspsychje> :p
[20:04] <alkisg> Hi guys, `do-release-upgrade -d` on mate 15.10 doesn't give me 16.04
[20:04] <alkisg> Does that only work for vanilla ubuntu? Should I sed through sources.list instead?
[23:51] <ChibaPet> drhalan1: I just saw your paste from last night. The bit I don't get is how eth0 had an address before the ifup. That it did suggests that the system didn't start from a totally clean state.
[23:51] <ChibaPet> I'd guess from what I see that you added the resolvconf lines after eth0 was already up.