[00:32] does anybody here have a copy of a 16.04 Alpha 1 ISO image? any flavour would do... [00:41] furkan: http://cdimage.ubuntu.com/daily-live/current/ http://cdimage.ubuntu.com/ubuntu-server/daily/current/ [00:42] ChibaPet: thanks but i was looking for a copy of the initial alpha 1 release, not the current daily build [00:43] there's a regression that i'm trying to narrow down [00:43] furkan: The changes between then and now would constitute bug fixes. [00:43] ah, gotcha [00:43] and it's proving too painful to work backwards and downgrade individual packages [00:43] Alright, bug fixes and regressions then. :P [00:43] my volume keys stop working after suspend/resume [00:43] :( [00:44] Oh, that's odd. [00:44] USB keyboard, out of curiosity? [00:45] yeah, USB [00:45] Unplugging and replugging ought to help. [00:45] just tried it right now, doesn't seem to have had an effect [00:45] 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] hrm [00:46] The other thing to look at is xev output. [00:46] that's another thing i was playing with a while back [00:46] 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] it doesn't give any output for the volume keys when i just run xev [00:47] hrm [00:47] but there was another tool too let me check what it was... [00:47] I get this, not that it particularly helps you: https://bpaste.net/show/eb59011f0382 [00:47] as an example [00:48] yeah that's what i get too when it's working normally [00:48] but there's this other tool, evtest [00:48] Anything in dmesg noting a detach? [00:48] Oh, I'm not familiar with that. Will have to learn about it. [00:48] right now i'm not getting any output in either of them [00:49] 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] and no nothing like that in dmesg [00:49] How about in /var/log/Xorg.0.log? [00:50] no "detach" in there either [00:50] Anything about evdev that looks relevant, though? [00:51] hmmm [00:51] there's quite a bit in here about evdev, trying to read through it [00:53] 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] dunno if that's relevant [00:54] That seems like a BlueTooth device or something. [00:54] just a Microsoft nano-receiver [00:54] it's an MS wireless keyboard [00:54] 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:54] Launchpad bug 44169 in X.Org X server "no multimedia keys when using evdev with mouse" [Medium,Won't fix] [00:55] Wait, it's a wireless keyboard? [00:55] yeah wireless keyboard + mouse combo [00:55] That's... almost certainly your multimedia device then. [00:55] Thought you said it was USB. Anyway... [00:55] oh, yeah it's USB but it's a USB wireless receiver [00:55] I'd bet that event6 is where the multimedia uhid is attaching. [00:55] not built-in bluetooth or anything [00:56] kk, I've seen those [00:56] hmm [00:56] 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] 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] i pulled the USB receiver out and plugged it back in [00:58] interesting bug report [00:58] pretty old though, from back in 2006-2008 [00:58] 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] in my case it was working fine with Ubuntu 15.10, and stopped after the upgrade to 16.04 [00:58] floor [00:59] haha [00:59] Yeah, not saying it's the same. Just stuff to look at. [00:59] but yeah that looks interesting [01:00] 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] so it looks like in /dev/input i don't have an event6 [01:00] i should try rebooting and see if it comes back [01:02] That seems extreme. [01:02] udev ought to be creating things like that as devices that need them are plugged in. [01:02] ALSO... It might get a name other than event6 on re-insertion. [01:02] I'd watch dmesg and watch the contents of /dev as you pull the plug and re-insert. [01:03] 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] i just tried unplugging and plugging back in [01:03] again [01:03] and same error [01:03] Anything interesting? [01:03] hrm [01:03] [ 4111.568] (EE) evdev: Microsoft Microsoft® 2.4GHz Transceiver v9.0: Unable to open evdev device "/dev/input/event6". [01:03] [ 4111.568] (EE) PreInit returned 2 for "Microsoft Microsoft® 2.4GHz Transceiver v9.0" [01:04] but hey that's progress at least.. i hadn't noticed that before [01:04] thanks for the help :) [01:04] Mm, and it's almost certainly directly related. [01:04] sure - please tell us what you find, as I'd be interested in knowing what it was [01:04] will do, if there is any progress :) [02:07] hey. is there anything I have to do for resolvconf to read stuff in /etc/network/interfaces? [02:07] is xenial even still using resolvconf? [02:10] anyways my problem: putting an entry in /etc/resolv.conf works. putting the same thing in /etc/network/interfaces doesn't [02:10] (even after a reboot) [02:20] drhalan1: You put resolvconf lines into interface descriptions. [02:20] i put °dns-nameservers° instead of °namerserver" [02:20] Correct. [02:20] And dns-search. [02:24] doh dns-search fixed it [02:24] thanks ChibaPet [02:24] cool [02:24] sure thing === Ian is now known as Ian_Corne [02:53] 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] I think you can go up to six, maybe more. [02:54] There's a cap that's smaller than what I could really use, but, eh. [03:23] ChibaPet: maybe you can help me with this issue too? http://pastebin.com/1damUL2M [03:24] not sure why i need to call ifup before resolvconf works... [03:28] i guess it is due to manual...but resolvconf should still setup dns... [10:05] Good morning. [10:13] hi cobber [10:13] still having dhclient probs, but my buddy with exact same setup isnt, so what have i ddone differently [10:15] Fudge: Tcpdump it, do you get replies on your dhcp requests? [10:17] listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes [10:17] No need to paste the entire output here ;) [10:18] 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] Tcpdump it and watch the logs when that happens. [10:19] ok [10:21] bound to 203.206.58.81 -- renewal in 6355 seconds. [10:21] Time for coffee ;) [10:24] lol [10:24] ill prob be in bed then damn [10:24] Not if you drink your coffee :P [10:24] * lordievader slides Fudge a fresh cup of coffee [10:24] i ran out, i could brew some though [10:28] cheers [11:16] ok using his rules too [11:24] ? [11:25] iptables [11:49] * lordievader is confused [11:49] What does iptables have to do with this? === yofel_ is now known as yofel [13:16] Hey folks === yofel_ is now known as yofel [14:48] will mir+unity8 be shipped with 16.04? [14:48] !info unity8-desktop-session-mir | mayhem [14:48] mayhem: unity8-desktop-session-mir (source: unity8-desktop-session): Unity8 desktop session for Mir. In component universe, is optional. Version 1.0.12+15.10.20150609-0ubuntu1 (xenial), package size 4 kB, installed size 54 kB [14:49] yeah, I was going through it.. [14:49] mayhem: they are already in 15.10. [14:50] sorry, what I meant is that is there a separate version planned for 16.04 (with mir+unity8) [14:52] mayhem: no [14:54] :k1l thanks for the confirmation [16:13] 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] nicomachus: from wily? [16:24] Yea. [16:25] nicomachus: fresh install instead, i had kernel issues from wily to xenial upgrade [16:25] 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] nicomachus: i ended up with 4.2 kernel where i should have higher on xenial [16:26] nicomachus: mixxed things up [16:26] nicomachus: fresh all working like a charm now [16:27] * nicomachus sighs [16:27] okkkkkk [16:27] guess I need to backup and do that then. [16:31] nicomachus: youl be happy with a fresh one mate :p [16:31] Probably. [16:34] thank god for gigabit upload speeds to google drive. [16:51] :p [20:04] Hi guys, `do-release-upgrade -d` on mate 15.10 doesn't give me 16.04 [20:04] Does that only work for vanilla ubuntu? Should I sed through sources.list instead? === Ian__ is now known as Ian_Corne [23:51] 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] I'd guess from what I see that you added the resolvconf lines after eth0 was already up.