=== gunner_genii is now known as genii === maxb_ is now known as maxb [10:34] Just reported a bug that when you lock your screen, xorg crashes [10:34] Through the "crashed" dialog === wall0 is now known as wallzero [12:26] are there any mayor bugs that i should wait for before upgrading to the dev release? [12:42] dns53: If you have XMir installed, disable it since its dual monitor support is still finicky [13:49] Hiya folks [14:03] Howdy BluesKaj [14:06] Hey Nothing_Much [14:07] BluesKaj: If you work for Canonical or know how to program for XMir, will XMir be a top priority for the 15.04-16.04 cycle? [14:13] Nothing_Much, i don't work for Canonical and i don't use Unity or Gnome, I'm a KDE guy. Sorry I have no idea about XMir, just hear rumours [14:13] Oh no problem [14:14] Nothing_Much: i see you mentioning xmir quite a lot. you know we don't ship it by default? [14:14] Wasn't xmir a transition thing? [14:14] yeah [14:15] popey: I know! I'm just overly enthusiastic of dumping xorg [14:15] So most of the attention will be put in Mir rather than Xmir, I suppose. [14:16] Nothing_Much: might want to reset those expectations! ☻ [14:17] I can wait another year, you guys are doing a pretty good job, honestly, I can almost play TF2 at framerates over 30 now with XMir [14:17] The problem though is that the screen freezes, flickers, then goes back to the game [14:17] Everything works as normal until another 30 seconds passes [14:18] Hmm.. [14:31] Nothing_Much, gpu? [15:03] BluesKaj: Radeon APU [15:11] hmm, shouldn't be having any graphics problems unless the driver isn't quite up to the task ..not real familiar with APUs and their available linux drivers [15:13] lordievader, not really. XMir, being a transition thing, is actually necessary for Mir to be useful for most users. [15:15] Most users won't care for reasons that legacy/older software won't work, they simply want them to work, so XMir will be a thing for awhile. [15:16] Daekdroom: Allright, I know nothing of mir/xmir. Thanks for the update :) [16:48] I have got a weird problem... apt stopped updating neon5 - and I can't figure out why. [16:49] The ppa is still there, it just doesn't show any updates - though I know my installed version is /way/ out of date. [16:49] high-rez: apt-cache policy neon5 #into a pastebin please [16:51] http://pastebin.com/seuL1CET [16:52] you see, its already the latest ppa version [16:53] high-rez: You'll have to go with Utopic+Kubuntu-next if you want the latest. (5.0.2 will allmost hit) [16:54] Huh, you're right I was just looking at the Packages here - for some reason I thought i updated on my other PC. [16:54] lordievader: Ahh, is the PPA for trusty no longer being actively worked? [16:55] high-rez: That I do not know, I do know sgclark is hard at work for the Utopic one. [16:55] I see [16:55] Welp, there yah go. I've always been a fan of unicorns anyways, I guess. [16:56] They've never done wrong by me. Except my little pony. [16:57] Thanks folks. [16:57] high-rez: You are already is #ubuntu+1 ;) [16:59] :) [21:01] Hello! Does anyone know which version of gthumb this? I don't understand the naming. is it 3.3.1 or 3.2.8? http://packages.ubuntu.com/utopic/gnome/gthumb [21:04] haha with a name like that I don't blame you [21:04] grueinthedark: https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1290691 [21:04] Launchpad bug 1290691 in gThumb "gThumb 3.3.1 incompatible with Unity and other non-Gnome environments" [Medium,New] [21:05] grueinthedark: It looks like it's 3.2.8 because having upgraded to 3.3.1 they found it broke on anything non-gnome [21:05] grueinthedark: but then they needed a way to force people who had upgraded to 3.3.1 to downgrade again, hence it's still the 3.3.1 package name [21:06] ... [21:07] Thanks for the information. [23:01] I just upgraded to Ubuntu 14.10 but I'm having some troubles with the network manager & dnsmasq.d [23:02] nslookup & dig resolve *.local (as defined in /etc/NetworkManager/dnsmasq.d/dotlocal) just fine [23:02] But when I use another tool such as wget or ping the domain can't be resolved [23:02] Does anyone know if this is a known issue? [23:03] hmm that's odd if dig works [23:03] http://paste.ubuntu.com/8391353/ [23:04] ping is working here on .local; 14.10 kubuntu [23:04] ok [23:05] if you look at /etc/nsswitch.conf what does your hosts line look like? [23:05] files mdns4_minimal [NOTFOUND=return] dns [23:05] hmm [23:05] I have: hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 [23:07] You're on the right track [23:07] setting dns as the first entry fixed it [23:07] If I take over the exact line you pasted it doesn't work [23:07] hmm [23:11] Setting dns just before mdns4_minimal works, just after it doesn't [23:14] leon@polly:~$ dpkg -l |grep mdns | awk '{print $2}' [23:14] libnss-mdns:amd64 [23:14] So I guess that's good [23:21] I found this bug that looks like the issue I'm having: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/80900 [23:21] Launchpad bug 80900 in avahi (Ubuntu) "Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks" [Medium,Triaged] [23:21] For now I'll just change the order in nsswitch.conf [23:22] penguin42: thanks for pointing me in the right direction! [23:23] no problem [23:23] that's an ancient ancient ancient bug though