[01:59] <Aki-Thinkpad> is there an image for 14.10 available yet?
[01:59] <rww> no
[01:59] <Aki-Thinkpad> might as well start testing
[01:59] <Aki-Thinkpad> rww, shucks
[02:00] <Aki-Thinkpad> I figure this one is going to be a real unstable one :)
[04:55] <tozen> hi all! is this channel for ubuntu dev branchs testers?
[08:10] <Fudge> rww:  ppl could upgrade though right?
[08:10] <Fudge> through sources.list
[08:18] <rww> Fudge: yep
[09:40] <antoronson05> Hello
[09:41] <antoronson05> I have a problem with my Ubuntu 14.04 Os
[09:41] <antoronson05> Please help me to downgrade it to Ubuntu 13.10
[09:57] <elfy> antoronson05: we're already dealing with 14.10 in here now - best place to go would be #ubuntu
[09:58] <elfy> though as far as I know downgrading is going to be installing 13.10 over 14.04
[10:15] <BluesKaj> 'Morning folks
[13:23] <lordievader> Good afternoon.
[13:30] <penguin42> greetings
[13:30] <BluesKaj> running 14.10 Kubuntu here, and the neworking is not auto loading on both eth0 and wifi. Have to run dhclient to connect on both.
[13:31] <penguin42> BluesKaj: You broken the unicorn already?
[13:31] <BluesKaj> penguin42, yup:)
[13:33] <BluesKaj> networking's merely an annoyance at this point, the dhclient command does work tho
[13:34] <BluesKaj> just doesn't autoconnect at boot
[13:34] <BluesKaj> or login, I haven't checked the logs
[13:36] <BluesKaj> it shows connected to the modem/router in the panel, but not to the internet. I can ssh into the other pcs on the lan before running dhclient
[13:38] <penguin42> missing the default route?
[13:38] <BluesKaj> seems so
[13:38] <penguin42>   ip route    should show you
[13:39] <BluesKaj> ok let me reboot and i'll check
[13:41] <junka> hi, is there a release schedule for utopic yet?
[13:41] <lordievader> junka: See topic.
[13:42] <junka> thanks lordievader
[13:59] <BluesKaj> default via 192.168.2.1 dev wlan0  proto static
[13:59] <BluesKaj> 192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.12  metric 9
[13:59] <penguin42> hmm, well it's got the default route - can it ping the 192.168.2.1 ?
[14:01] <BluesKaj> hmm,  ping: icmp open socket: Operation not permitted
[14:02] <lordievader> Firewall being a pita?
[14:02] <penguin42> BluesKaj: Try that as root?
[14:03] <BluesKaj> it pings ok as root
[14:03] <penguin42> it's a bit mean not to let you ping as a normal user
[14:03] <penguin42> ok, so can you ping an external host by ip?
[14:06] <BluesKaj> yeah have to sudo ping google.com to get a response, otherwise i get the icmp open socket: Operation not permitted
[14:06] <penguin42> sounds like broken perms on the ping binary?
[14:07] <penguin42> can you do non-ping external connections?
[14:07] <penguin42> something like wget http://www.google.com ?
[14:08] <BluesKaj> wget http://www.google.com works
[14:08] <BluesKaj> without sudo
[14:08] <penguin42> ok - so external connectivity is all working great - what makes you think it was broken without dhcpc ?
[14:09] <Bluefoxicy> So
[14:09] <Bluefoxicy> libpam-tmpdir in 14.10 right?  :)
[14:10]  * penguin42 doesn't know yet - just doing my utopic upgrade on a vm :-)
[14:10] <BluesKaj> it showed the machine was connected to the internet at login altho it wasn't really connected until dhclient was invoked
[14:10] <penguin42> but if you do that ping and that wget before the dhclient did they work?
[14:10] <BluesKaj> was connected to the lan tho
[14:11] <BluesKaj> no
[14:11] <BluesKaj> let me try this on my desktop pc
[14:13] <penguin42> BluesKaj: OK but what does the route look like prior to the dhclient  ?
[14:14] <BluesKaj> just got a notice on the desktop reboot about the dhcp server crashing
[14:15] <penguin42> server?
[14:15] <lordievader> Are you running your own dhcp server?
[14:16] <BluesKaj> no, using net
[14:16] <BluesKaj> NM
[14:19] <BluesKaj> penguin42, wget http://www.google.com unable to resolve host address
[14:20] <penguin42> ok, does the ping work?
[14:20] <BluesKaj> ip route gives the same operation not permitted
[14:20] <penguin42> huh, ok as root
[14:21] <BluesKaj> no
[14:21] <penguin42> so, as root what happens?
[14:22] <BluesKaj> same , unable to reslve
[14:22] <BluesKaj> resolve
[14:22] <penguin42> by IP
[14:23] <BluesKaj> the NM icon in the panel shows eth0 is connected tho
[14:24] <penguin42> what happens if you ping by ip as root
[14:25] <BluesKaj> sudo ping 4.4.4.4 sending bytes of data but no response
[14:25] <penguin42> use 8.8.8.8
[14:25] <BluesKaj> ok
[14:26] <BluesKaj> that works
[14:26] <penguin42> ok, good, so your connectivity is there - just your domain resolution is broken
[14:27] <penguin42> you said your dhcpserver crashed - are you sure it wasn't dnsmasq?
[14:28] <BluesKaj> yes I'm sure it said dhcp server
[14:28] <penguin42> curious
[14:28] <penguin42> ok, well you can see what your /etc/resolv.conf says
[14:29] <penguin42> 8.8.8.8 is always a good one to remember, it's owned by google and is just a good ping target
[14:30] <penguin42> (and DNS server)
[14:34] <BluesKaj> resolv.conf is empty , probly still written to by /etc/resolvconf/resolv.conf.d/base
[14:34] <BluesKaj> checking /etc/resolvconf/resolv.conf.d/base
[14:35] <penguin42> empty?
[14:35] <penguin42> I don't think it should be empty
[14:35] <penguin42> resolvconf is supposed to set that up
[14:39] <penguin42> BluesKaj: Check that you have the resolvconf package installed
[14:45] <BluesKaj> penguin42, yeah , newest version
[14:46]  * penguin42 wonders what runs resolvconf
[14:47] <BluesKaj> in my case it's probly NM
[14:49] <penguin42> BluesKaj: My freshly updated vm to utopic can ping as non-root
[14:49] <penguin42> BluesKaj: (unity this vm)
[14:53] <BluesKaj> penguin42, I can ping as root , but not as user
[14:53] <BluesKaj> without running dhclient
[14:54] <penguin42> if you run dhclient it changes that?
[14:54] <penguin42> are you sure? I can understand that dhclient would fix up the resolv.conf but I can't see how it can fix the rootiness
[14:55] <BluesKaj> yes I'm sure
[14:57] <BluesKaj> also have to run dhclient as root
[14:58] <BluesKaj> which seems normal
[15:01] <penguin42> ok, that's very weird
[15:05] <BluesKaj> when I run dhclient as user = RTNETLINK answers operation not permitted
[15:05] <penguin42> yeh, I expect to need to run dhclient as root, what surprises me is it influences ping's behaviour with an ip
[15:07] <BluesKaj> penguin42, I've seen this before with other users, but i don't recall the fix...perhaps NM needs some tweaking by the devs for 14.10
[15:07] <penguin42> my 14.10 unity is working ok
[15:08] <BluesKaj> unity probly uses a different NM setup
[15:09] <penguin42> but I've seen ping require root in two situations   1) Where it doesn't have perms to run at all (screw up in filesystem) and hence I wouldn't expect dhcpcd to fix it,  or  2) If the address looks likea broadcast address - but that's also not the case in your situation, so I don't know what's going on
[15:10] <BluesKaj> I'd run from the interfaces and resolvconf files but setting it up for wifi and vpn is rather complex so I let NM and openvpn NM take care of the settings
[15:10] <penguin42> yeh, I've never figured out wifi manually
[15:13] <BluesKaj> might be a bug in dhcp/NM setting for 14.10
[15:14] <BluesKaj> not auto loading the dhcp server
[15:14] <penguin42> yeh what's confusing for me is I can't see how if dhcp/nm screw up they would produce the failure you're seeing
[15:14] <penguin42> well, I can see most of the failure - just not the ping permission error change
[15:15] <BluesKaj> odd tho because dropbox updates fine at login
[15:46] <BluesKaj> penguin42, dnsmasq was using 50% of the cpu and it nothing happened after I killed it
[15:48] <BluesKaj> on both machines
[15:48] <Na3iL> You need to edit /etc/NetworkManager/NetworkManager.conf file → gksudo gedit /etc/NetworkManager/NetworkManager.conf
[15:49] <Na3iL> then add a # to the line dns=dnsmasq
[15:49] <Na3iL> so it will be #dns=dnsmasq
[15:49] <Na3iL> and restart it by typing sudo restart network-manager
[15:54] <penguin42> BluesKaj: Interesting, dns naming has broken in my unity vm - ping by IP still works
[15:54] <penguin42> BluesKaj: And yes, dnsmasq is eating cpu
[15:55] <BluesKaj> Na3iL, thanks for the tip .. restarting NM now
[15:55] <Na3iL> you welcome :)
[15:56] <penguin42> BluesKaj: So it's not just KDE
[15:57] <penguin42> for me dnsmasq appears to be stuck doing socket operations on a pipe
[16:00] <penguin42> hmm, still ff28 in +1
[16:03] <BluesKaj> ok dnsmasq commented out, no longereating cpu for no reason
[16:03] <penguin42> have you reported that bk - since I've just hit the same thing (although for me ping never gives a perm error)
[16:14] <BluesKaj> ok penguin42 , connection to internet problem solved...seems dnsmasq was the culprit as you suspected earlier
[16:15] <BluesKaj> thanks to Na3iL :)
[16:15] <penguin42> BluesKaj: Yeh I just hit the same problem on Gnome - although ping was OK - did you report it?
[16:16] <Na3iL> you welcome BluesKaj  :)
[16:18] <BluesKaj> not yet, it's kind of early days, don't you think ? especially if dnsmasq is causing it, some users who use manual networking setups use dnsmasq in their networking files
[16:18] <BluesKaj> penguin42,^
[16:18] <penguin42> BluesKaj: dnsmasq is broken -> bug
[16:18] <BluesKaj> they'll soon discover it
[16:18] <Na3iL> dnsmasq is broken on what version of ubuntu ?
[16:19] <Na3iL> 14.04 ?
[16:19] <BluesKaj> 14.10
[16:19] <BluesKaj> we're bleeding edgers here :)
[16:20] <Na3iL> u can report it on launchpad
[16:57]  * penguin42 reports it
[16:59] <Na3iL> cool :)
[17:02] <penguin42> bug 1313393
[17:02] <penguin42> BluesKaj: Can you please confirm that one
[17:03] <BluesKaj> ok penguin42 , confirmed
[17:03] <BluesKaj> bug 1313392
[17:04] <BluesKaj> looks like some overlap there :)
[17:07] <BluesKaj> penguin42, confirm bug 1313392
[17:12] <BluesKaj> BBL ...it's a nice day . yardwork awaits
[19:13] <penguin42> http://imagebin.org/307853  ok - that really shouldn't happen
[19:14] <penguin42> I can't find a way to type into the command box, but still