[01:26] <elhoir> hello guys, coulñd you tell me what exactly are the linux-tools-* packages?
[01:26] <elhoir> what kind of tools?
[04:14] <bubbasaures> .
[04:53] <dns53> i'm trying to upgrade using do-release-upgrade -d and it is having problems calculating the upgrade, is there something i should try to debug it?
[07:56] <lordievader> Good morning.
[08:47] <elfy> morning
[08:54] <lordievader> Hey elfy, how are you this Saturday morning?
[08:57] <elfy> excellent thanks :)
[08:57] <elfy> you?
[08:57] <lordievader> Doing good here :), it's a nice day, sun in shining :)
[08:57] <elfy> wish it was here - it's not raining though :)
[09:36] <freddy__> clear
[10:32] <vitimiti> hi
[10:44] <BluesKaj> Howdy folks
[12:36] <rymate1234> hey I got a bug in the ubuntu 14.10 daily image http://images.rymate.co.uk/images/dsOYCo5.png
[12:37] <elfy> that's a screenshot of the system monitor
[12:42] <BluesKaj> rymate1234, best to describe your bug first
[12:42] <rymate1234> can you not see the black rectangles around the graphs
[12:43] <BluesKaj> not everyone uses your desktop so we can't see anything wrong
[12:47] <rymate1234> I get the same visual bug in a vm though http://images.rymate.co.uk/images/vv25zhX.png
[12:47] <rymate1234> so it can't just be "my pc"
[12:54] <BluesKaj> one has to expect the odd bug on a devel OS, altho it doesn't seem too serious you can file a bug if you wish
[13:10] <richardP> Hi all! I tried to boot into Ubuntu Next (Unity8) from USB, but the screen is not on the right postion: Screenshot: https://www.dropbox.com/s/f9l5uq90yqbms6y/IMG_20140927_150353.jpg?dl=0
[13:10] <richardP> Any idea?
[13:15] <lordievader> richardP: Wrong display setting?
[13:15] <richardP> but how can I change it?
[13:16] <richardP> I can't login, because I can't click to the skip intro button
[13:16] <lordievader> richardP: xrandr?
[13:16] <richardP> i'll try it, reboot
[13:18] <BluesKaj> was going to suggest f6
[13:21] <lordievader> f6? No modeset?
[13:24] <BluesKaj> options to boot with no acpi , nomodeset etc
[13:31] <kbroulik> is there at least a ppa that provides qt 5.3.2 for kubuntu utopic? I'm tired of having an outdated qt 5.3.0 version with all kinds of weird bugs that have been fixed months ago.
[13:34] <BluesKaj> kbroulik, so what makes you think a newer version will be bug free?
[13:34] <bipul> Hello, I am unable to intall Ubuntu14.10 on my Virtualbox.
[13:36] <elfy> bipul: unable to install at all - or get bug 1371651 ?
[13:40] <Daekdroom> BluesKaj, nomodeset wouldn't work with Mir.
[13:40] <BluesKaj> Daekdroom, well maybe the other options will
[13:41] <BluesKaj> Daekdroom, thought it was Xmir anyway
[13:42] <lordievader> Daekdroom: Why not? I thought nomodeset was a kernel thing?
[13:43] <bipul> elfy: Even i have also reported that issue.
[13:43] <Daekdroom> BluesKaj, XMir can only be used with Mir, as a means to make X-compiled apps work with Mir.
[13:43] <Daekdroom> lordievader, yes, but it's currently necessary for direct rendering, which is a pre-requisite for Mir.
[13:43] <BluesKaj> aamof lordievader I think it is, it bypasses the kernel module iirc
[13:44] <lordievader> Daekdroom: Ok, thanks.
[13:44] <elfy> bipul: bug number?
[13:45] <bipul> elfy: 1374754
[13:45] <BluesKaj> Daekdroom, then that's unfortunate, makes more difficult to boot with some gpus
[13:46] <BluesKaj> fortunately i don't use Unity
[13:46] <elfy> bipul: can't find it
[13:46] <elfy> bug 1374754
[13:46] <Daekdroom> BluesKaj, yes. Mir basically only works with opensource drivers that use KMS, right now. Closed-source ones will get support later (if at all, depending on whether Nvidia and AMD care)
[13:49] <bipul> elfy: yes
[13:49] <elfy> bipul: read it now - different issue
[13:50] <bipul> sorry i don't get you?
[13:50] <elfy> nvm - can't help you I'm afraid
[13:50] <BluesKaj> Daekdroom, maybe nvidia will help develop drivers for Mir, but support from amd/ati historically hasn't been as good so there may be problems with their gpus
[13:51] <elfy> tgm4883: you got a minute?
[13:51] <tgm4883> elfy: whats up?
[13:53] <elfy> PM'd you
[16:30] <Bluefoxicy> ugh
[16:30] <Bluefoxicy> Chromium needs a print option for media type, instead of hacking through the page with the developer tools and deleting all media=screen attributes and media=print tags
[17:00] <tux_> anyone use steam on 14.10 ?
[17:06] <jtaylor> <
[18:11] <ICantLinux> 14.10 updated yesterday (minor kernel update?) and now my display is no more. :(
[18:20] <BluesKaj> ICantLinux, which gpu?
[18:21] <ICantLinux> r9 280x. Was running mesa 10.3 from the x-staging ppa.
[18:21] <ICantLinux> (and xorg 1.16)
[18:23] <ObrienDave> intel graphics?
[18:29] <BluesKaj> amd gaming card, unfortunately, and support is tough to come by these days
[18:33] <ICantLinux> From what I can remember, grub and the kernel were updated. Don't remember the other updates. Strangely enough, glxinfo properly detects my GPU.
[19:00] <ICantLinux> Any way to revert Xorg to 1.15 (so I can attempt installing the proprietary drivers)?
[19:04] <lordievader> ICantLinux: Why do you need to revert Xorg for that?
[19:04] <ICantLinux> Catalyst beta doesn't support 1.16, unfortunately.
[19:06] <lordievader> Where did you read that? Usually they depend on version >=x
[19:07] <lordievader> Ah nvm, spotted it.
[19:07] <lordievader> I guess you are stuck with the open source driver on Utopic.
[19:38] <ICantLinux> Yup. Might have to try a kernel update. If the drivers still refuse to cooperate, it's back to 14.04.
[19:39] <Nothing_Much> ICantLinux: What happened?
[19:39] <Nothing_Much> Do you have specs?
[19:40] <lordievader> Nothing_Much: The AMD driver page specifies it. The beta driver only supports up to 3.13.
[19:41] <Nothing_Much> Then he needs to stick to the radeonsi driver
[19:41] <Nothing_Much> But specs would still be nice
[19:41] <Nothing_Much> APU or GPU, specifically
[19:41] <ICantLinux> Utopic updated yesterday. Installed kernel 3.16.0-18 along with some other minor updates. Can no longer boot to any display (monitor loses input after grub screen).
[19:41] <lordievader> Nothing_Much: That's what I said ;)
[19:42] <Nothing_Much> lordievader: Yes, but what is it? APU or GPU?
[19:42] <Nothing_Much> I have an APU and radeonSI runs perfectly fine
[19:42] <lordievader> 27-20:21 < ICantLinux> r9 280x. Was running mesa 10.3 from the x-staging ppa.
[19:42] <Nothing_Much> Oh okay
[19:42] <ICantLinux> Nothing_Much the latest beta supports >= 3.16. I currently have the radeon driver installed, but neither the default version or oibaf can fix the issue.
[19:43] <Nothing_Much> I think I missed the issue
[19:43] <Nothing_Much> What's up?
[19:43] <lordievader> ICantLinux: By the by, the package provided by Ubuntu doesn't work?
[19:44] <ICantLinux> Nope.
[19:44] <Nothing_Much> What package?
[19:44] <lordievader> The amd proprietary driver package.
[19:44] <Nothing_Much> Ah
[19:44] <ICantLinux> hmmm...
[19:44] <Nothing_Much> Yeah.. AMD just made an announcement that they want to know what's wrong with their driver
[19:45] <Nothing_Much> So they can fix it up and stuff
[19:45] <Nothing_Much> https://www.youtube.com/watch?v=zNHlIZ4F9Jc
[19:45] <ICantLinux> Default proprietary drivers don't support Utopic (no 3.16 kernel support) :(
[19:45] <Nothing_Much> Not even the updates-* one?
[19:45] <lordievader> That is somewhat strange at this point...
[19:45] <ICantLinux> Neither do IIRC.
[19:46] <Nothing_Much> Was there an xorg.conf in /etc/X11/?
[19:47] <ICantLinux> There's no xorg.conf. I've removed all the extraneous backups that the proprietary drivers generate as well.
[19:49] <ICantLinux_> Just tried resuming boot from safe mode. Everything works (albeit at a low resolution), but still can't boot normally.
[19:56] <Nothing_Much> ICantLinux: It's because you're not using the drive
[19:56] <Nothing_Much> r
[19:56] <Nothing_Much> It's using vesa I think, which is the basic video driver just to output the basic necessities
[19:56] <ICantLinux> How can I tell which driver I'm using?
[19:57] <lordievader> ICantLinux: lspci -k|grep -A2 VGA
[19:57] <ICantLinux> VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
[20:01] <ICantLinux> lordievader: X log contains no trace of radeon, but that could be because of safe booting.
[20:05] <lordievader> ICantLinux: Only one line of output? If so it is vesa.
[20:06] <ICantLinux> I'll try restarting and booting normally to get a better log. Might have to ssh though.
[20:14] <ICantLinux> lordievader: Even without quiet splash in kernel boot params, I get nothing. Not a thing. After grub screen, my monitor just loses input.
[20:14] <lordievader> ICantLinux: Try the nomodeset kernel parameter.
[20:15] <ICantLinux> Will do.
[20:19] <ICantLinux> lordievader: nomodeset appears to have made some sort of progress. I get an Ubuntu purple bar covering the first third of the screen, a black bar covering the second and miscellaneous noise along the last third.
[20:21] <lordievader> ICantLinux: This is still (trying) to use the AMD driver I suppose?
[20:22] <ICantLinux> Indeed. Still on the open source driver. Not sure if vesa is being used, however, as I can't even get to a shell.
[20:22] <lordievader> Err, with AMD I ment the closed-source one...
[20:23] <lordievader> ICantLinux: If you add 'text' as a kernel parameter do you get to a tty then?
[20:23] <ICantLinux> I don't think I CAN use fglrx. Will try.
[20:31] <ICantLinux> lordievader: Booting with text freezes after "Stopping userspace bootsplash"
[20:33] <lordievader> ICantLinux: Hmm, I guess you are out of luck. (In other words, I don't know how I can help you)
[20:34] <ICantLinux> I guess I'll just fiddle with grub until something (hopefully) works out. Thanks for your help :)
[20:45] <vitimiti> Hi
[21:52] <peepTV> apt-get remove bash
[21:53] <jtaylor> yeah, don't do that ..
[21:55] <peepTV> remote feature relly on bash
[21:59] <Daekdroom> ...?
[22:09] <peepTV> and cgi