[01:26] hello guys, coulñd you tell me what exactly are the linux-tools-* packages? [01:26] what kind of tools? === magic_ is now known as magic [04:14] . [04:53] 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] Good morning. [08:47] morning [08:54] Hey elfy, how are you this Saturday morning? [08:57] excellent thanks :) [08:57] you? [08:57] Doing good here :), it's a nice day, sun in shining :) [08:57] wish it was here - it's not raining though :) [09:36] clear [10:32] hi [10:44] Howdy folks [12:36] hey I got a bug in the ubuntu 14.10 daily image http://images.rymate.co.uk/images/dsOYCo5.png [12:37] that's a screenshot of the system monitor [12:42] rymate1234, best to describe your bug first [12:42] can you not see the black rectangles around the graphs [12:43] not everyone uses your desktop so we can't see anything wrong [12:47] I get the same visual bug in a vm though http://images.rymate.co.uk/images/vv25zhX.png [12:47] so it can't just be "my pc" [12:54] 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] 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] Any idea? [13:15] richardP: Wrong display setting? [13:15] but how can I change it? [13:16] I can't login, because I can't click to the skip intro button [13:16] richardP: xrandr? [13:16] i'll try it, reboot [13:18] was going to suggest f6 [13:21] f6? No modeset? [13:24] options to boot with no acpi , nomodeset etc [13:31] 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] kbroulik, so what makes you think a newer version will be bug free? [13:34] Hello, I am unable to intall Ubuntu14.10 on my Virtualbox. [13:36] bipul: unable to install at all - or get bug 1371651 ? [13:36] bug 1371651 in plymouth (Ubuntu) "Daily does not boot into graphical interface after installation" [Critical,Triaged] https://launchpad.net/bugs/1371651 [13:40] BluesKaj, nomodeset wouldn't work with Mir. [13:40] Daekdroom, well maybe the other options will [13:41] Daekdroom, thought it was Xmir anyway [13:42] Daekdroom: Why not? I thought nomodeset was a kernel thing? [13:43] elfy: Even i have also reported that issue. [13:43] BluesKaj, XMir can only be used with Mir, as a means to make X-compiled apps work with Mir. [13:43] lordievader, yes, but it's currently necessary for direct rendering, which is a pre-requisite for Mir. [13:43] aamof lordievader I think it is, it bypasses the kernel module iirc [13:44] Daekdroom: Ok, thanks. [13:44] bipul: bug number? [13:45] elfy: 1374754 [13:45] Daekdroom, then that's unfortunate, makes more difficult to boot with some gpus [13:46] fortunately i don't use Unity [13:46] bipul: can't find it [13:46] bug 1374754 [13:46] bug 1374754 in ubiquity (Ubuntu) "Unable to install Ubuntu14.10 on Virtualbox" [Undecided,New] https://launchpad.net/bugs/1374754 [13:46] 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] elfy: yes [13:49] bipul: read it now - different issue [13:50] sorry i don't get you? [13:50] nvm - can't help you I'm afraid [13:50] 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] tgm4883: you got a minute? [13:51] elfy: whats up? [13:53] PM'd you [16:30] ugh [16:30] 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] anyone use steam on 14.10 ? [17:06] < [18:11] 14.10 updated yesterday (minor kernel update?) and now my display is no more. :( [18:20] ICantLinux, which gpu? [18:21] r9 280x. Was running mesa 10.3 from the x-staging ppa. [18:21] (and xorg 1.16) [18:23] intel graphics? [18:29] amd gaming card, unfortunately, and support is tough to come by these days [18:33] From what I can remember, grub and the kernel were updated. Don't remember the other updates. Strangely enough, glxinfo properly detects my GPU. === krabador is now known as Guest65945 [19:00] Any way to revert Xorg to 1.15 (so I can attempt installing the proprietary drivers)? [19:04] ICantLinux: Why do you need to revert Xorg for that? [19:04] Catalyst beta doesn't support 1.16, unfortunately. [19:06] Where did you read that? Usually they depend on version >=x [19:07] Ah nvm, spotted it. [19:07] I guess you are stuck with the open source driver on Utopic. === cyphase is now known as Guest69235 [19:38] Yup. Might have to try a kernel update. If the drivers still refuse to cooperate, it's back to 14.04. [19:39] ICantLinux: What happened? [19:39] Do you have specs? [19:40] Nothing_Much: The AMD driver page specifies it. The beta driver only supports up to 3.13. [19:41] Then he needs to stick to the radeonsi driver [19:41] But specs would still be nice [19:41] APU or GPU, specifically [19:41] 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] Nothing_Much: That's what I said ;) [19:42] lordievader: Yes, but what is it? APU or GPU? [19:42] I have an APU and radeonSI runs perfectly fine [19:42] 27-20:21 < ICantLinux> r9 280x. Was running mesa 10.3 from the x-staging ppa. [19:42] Oh okay [19:42] 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] I think I missed the issue [19:43] What's up? [19:43] ICantLinux: By the by, the package provided by Ubuntu doesn't work? [19:44] Nope. [19:44] What package? [19:44] The amd proprietary driver package. [19:44] Ah [19:44] hmmm... [19:44] Yeah.. AMD just made an announcement that they want to know what's wrong with their driver [19:45] So they can fix it up and stuff [19:45] https://www.youtube.com/watch?v=zNHlIZ4F9Jc [19:45] Default proprietary drivers don't support Utopic (no 3.16 kernel support) :( [19:45] Not even the updates-* one? [19:45] That is somewhat strange at this point... [19:45] Neither do IIRC. [19:46] Was there an xorg.conf in /etc/X11/? [19:47] There's no xorg.conf. I've removed all the extraneous backups that the proprietary drivers generate as well. [19:49] Just tried resuming boot from safe mode. Everything works (albeit at a low resolution), but still can't boot normally. [19:56] ICantLinux: It's because you're not using the drive [19:56] r [19:56] It's using vesa I think, which is the basic video driver just to output the basic necessities [19:56] How can I tell which driver I'm using? [19:57] ICantLinux: lspci -k|grep -A2 VGA [19:57] VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [20:01] lordievader: X log contains no trace of radeon, but that could be because of safe booting. [20:05] ICantLinux: Only one line of output? If so it is vesa. [20:06] I'll try restarting and booting normally to get a better log. Might have to ssh though. [20:14] 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] ICantLinux: Try the nomodeset kernel parameter. [20:15] Will do. [20:19] 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] ICantLinux: This is still (trying) to use the AMD driver I suppose? [20:22] 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] Err, with AMD I ment the closed-source one... [20:23] ICantLinux: If you add 'text' as a kernel parameter do you get to a tty then? [20:23] I don't think I CAN use fglrx. Will try. [20:31] lordievader: Booting with text freezes after "Stopping userspace bootsplash" [20:33] ICantLinux: Hmm, I guess you are out of luck. (In other words, I don't know how I can help you) [20:34] I guess I'll just fiddle with grub until something (hopefully) works out. Thanks for your help :) === jje is now known as Guest50666 === trism_ is now known as trism === magic is now known as Guest57710 [20:45] Hi === tgm4883_ is now known as tgm4883 === jtaylor_ is now known as jtaylor === Guest69235 is now known as cyphase === cyphase is now known as Guest52545 === Guest50666 is now known as jje [21:52] apt-get remove bash [21:53] yeah, don't do that .. [21:55] remote feature relly on bash [21:59] ...? [22:09] and cgi === jje_ is now known as jje === jje is now known as Guest92539