[00:02] <quantibiliy> need the developers channel for xubuntu or , perhaps here. dual screen issues? seems to rotate and wonder if its cycling through the "work spaces's' and some how is messing with the the dual screen, cause i fix it, then it messes up, so i just cycle through (top, left, down, right) then after soem time i get tired of it, so i leave it be unless i need to mess with it... haven't messsed with it lately but today i boote
[00:02] <quantibiliy> d up to a configuration that worked flawless...  so i wonder if its haveing it set on work spaces currently assinged to the screen.
[00:16] <rexonis> Really enjoying the quality of 16.04.
[00:17] <rexonis> The codebase feels tighter. The desktop feels more polished.
[00:27] <Headzup> And the amazon advertising is deactivated by default!
[01:11] <Fritigern> I early-adopted 16.04 yesterday (a year long habit) and now when running apt-get update, I recieve warnings/errors about weak algorythms. Here's one of them:  http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: Signature by key <KEY HIDDEN> uses weak digest algorithm (SHA1)
[01:11] <Fritigern> My question is now: is there anything I can do about it, or is this something that the repo maintainers should fix?
[01:12] <dax> Fritigern: it's something that the repository maintainers should fix
[01:13] <Fritigern> Poop. So until they fix it, I (and many others) will be stuck with this warning, or is it an error?
[02:38] <Xpistos> Hey All. Does 16.04 support touchscreens?
[02:38] <Xpistos> I have a Lenovo Twist that I am dying to get my touchscreen working.
[04:16] <lotuspsychje> !unity
[04:18] <dax> !notunity
[04:18] <lotuspsychje> dax: would it be a good idea to add ubuntu mate to !flavors?
[04:18] <ChibaPet> Wouldn't a better suggestion be installing "ubuntu-gnome-desktop" ? Or is it just gnome-desktop? Looking.
[04:19] <ChibaPet> !info ubuntu-gnome-desktop
[04:19] <dax> lotuspsychje: yeah, !flavors needs a major update
[04:19] <lotuspsychje> dax: edubuntu also might die :p
[04:20] <dax> *nod*
[07:34] <agronholm> I would like to report several bugs in xenial final beta installation, what do I do?
[07:34] <agronholm> I already logged in to launchpad but I can't figure out how to report a new bug
[09:14] <Fudge> agronholm:  first make sure all updates are installed
[09:15] <Fudge> apport is one way, ubuntu-bug is another, see this page mate https://help.ubuntu.com/community/ReportingBugs
[09:22] <agronholm> Fudge: how do I do that when it won't install in the first place?
[09:22] <agronholm> I'm in the process of writing a report on the appropriate forum
[09:22] <agronholm> basically, grub crashed, among other bugs
[09:31] <agronholm> I'm trying to reproduce the problem in virtualbox but I got a UEFI warning dialog with two buttons, neither of which does anything when clicked
[09:31] <agronholm> the installer is so thoroughly and hilariously broken I don't know to laugh or cry
[09:42] <Fudge> oh there were soem bugs in the beta release i saw
[09:42] <Fudge> can you google xenial beta release notes and take a look, there were a couple of bugs tha tpop up when it is installed in a particular way
[09:42] <agronholm> I did
[09:42] <agronholm> nothing about the problems I saw
[09:43] <agronholm> the only "known bugs" were related to the partitioning phase
[09:43] <agronholm> and I didn't hit them
[09:43] <Fudge> ah, if its just grub you could chroot to /target and fix it yourself if you know how
[09:44] <Fudge> sounds like youre having a hard time
[09:44] <agronholm> I don't know how, and I shouldn't have to
[09:44] <agronholm> I repeated the install process with 15.10 right after and it worked flawlessly
[09:45] <agronholm> I'm just not sure where to report these problems so Canonical employees can see them and fix the problems
[09:45] <Fudge> you might have to wait until release, it is beta afterall
[09:46] <agronholm> I thought the entire point of having a beta was that problems would get discovered by users like me and reported to Canonical
[09:46] <agronholm> if they don't accept user feedback, why release a beta in the first place?
[09:47] <Fudge> like you I am just a user too, i dont know if you can use ubuntu-bug from the live image or not, you could try against ubiquity like ubuntu-bug ubiquity if I recall correctly
[09:47] <agronholm> what's ubiquity?
[09:48] <Fudge> that is the name of the installer
[09:48] <agronholm> okay
[09:49] <agronholm> this is where I got stuck with virtualbox: http://imgur.com/tQQvqZP
[09:49] <agronholm> neither button does anything when clicked
[09:50] <Fudge> which screen is it, sorry but I can not see so pics or screenshots don't help
[09:51] <agronholm> ah :(
[09:51] <lordievader> Good morning.
[09:51] <agronholm> it's the screen where you choose your location
[09:51] <agronholm> there's a modal dialog on top of that
[09:51] <agronholm> titled "Force UEFI installation?"
[09:51] <Fudge> I usually manually partition, choose the partition, format ext4 mount point /. install grub to the desk, which for me is sda. then next next fill out user info then wait.
[09:52] <Fudge> hi lordievader
[09:52] <agronholm> Fudge: I tried the same (though with btrfs instead of ext4)
[09:52] <lordievader> Hey Fudge, how are you?
[09:52] <Fudge> agronholm:  what method of install are you choosing, to entire disk. I do recall problems in the past with UEFI if installing manually
[09:52] <Fudge> going good mate, have a nice longneck of Bavairia here next to me
[09:53] <Fudge> did you see the screenoshot agronholm  just posted lordievader , ideas?
[09:53] <agronholm> Fudge: are you asking me if I chose the topmost option (automatic) when prompted?
[09:54] <agronholm> instead of partitioning manually?
[09:54] <Fudge> yep
[09:54] <agronholm> no I did not -- I chose to partition manually
[09:54] <agronholm> otherwise I would not get a btrfs root disk
[09:54] <lordievader> I suppose you don't have another install on your vb box?
[09:55] <agronholm> lordievader: what do you mean?
[09:55] <lordievader> The uefi warning says there may be another install using the bios system, is this true?
[09:56] <agronholm> no it's not
[09:56] <agronholm> this was a freshly partitioned drive
[09:56] <agronholm> I had to create the partition table in the partitioner section of the installer
[09:57] <agronholm> so how it determined that I had another OS installed is a mystery
[09:57] <lordievader> They I'd ignore the warning.
[09:58] <agronholm> lordievader: I wish I could but neither button does anything when pushed
[09:58] <lordievader> Hehe, well that is helpfull...
[09:58] <agronholm> it's the same thing when I tried to install on bare metal -- grub crashed and I was told that after closing this dialog an error report would be sent
[09:58] <agronholm> but the close button did nothing
[09:58] <lordievader> I suppose you could boot it into bios mode. But how to force vb into that I do not know.
[09:59] <agronholm> I specifically booted with EFI support to reproduce the problems I had on bare metal
[09:59] <agronholm> I have no real intention of installing this on VB
[10:00] <lordievader> Ah...
[10:01] <agronholm> I wasn't expecting the installer to fail so hard in UEFI mode
[10:03] <Fudge> UEFI sux
[10:03] <flocculant> agronholm: just to be clear here - you're trying to do this to reproduce a bug on hardware so you can report it?
[10:03] <agronholm> flocculant: I believe that is what I just said
[10:04] <agronholm> the keyboard layout selector is broken too, even without UEFI
[10:04] <agronholm> worked flawlessly with 15.10
[10:04] <flocculant> agronholm: and when you tried to install on hardware it didn't crash and then fall back to the livesession desktop?
[10:04] <agronholm> flocculant: it did crash
[10:04] <agronholm> flocculant: when installing grub
[10:05] <flocculant> right - but did it leave you at the desktop?
[10:05] <flocculant> because it should - then you can report bugs with ubuntu-bug
[10:05] <agronholm> not sure what you mean by that -- it didn't drop me to console if that's what you mean
[10:06] <flocculant> no - just the livesession desktop
[10:06] <agronholm> no
[10:06] <agronholm> I just got an error message saying that when I close this dialog it will send the error report
[10:06] <flocculant> right - and then it didn't
[10:06] <agronholm> but then I couldn't close the dialog because the "close" button didn't do anything
[10:07] <agronholm> the button would respond normally, but nothing would happen when pressing it
[10:07] <flocculant> I assume you checked the iso
[10:07] <agronholm> I can do that
[10:07] <flocculant> I would - hit any key - check for defects
[10:08] <agronholm> no errors found
[10:08] <flocculant> then start it - but use the try option rather than install so you're at a desktop
[10:08] <agronholm> also: http://imgur.com/PKmfHYG
[10:08] <flocculant> then when it crashes - open a terminal and ubuntu-bug ubiquity
[10:08] <flocculant> yea - I'd not do that
[10:08] <agronholm> this is how the installer looks on my laptop
[10:09] <flocculant> yea that looks right
[10:09] <agronholm> the "Jatka" (Continue) button causes the cursor to turn to a rolling ball and it takes several minutes there
[10:09] <agronholm> flocculant: looks right to you that the window content creeps halfway onto the title bar and the desktop is far larger than the screen?
[10:10] <flocculant> oh right - no that doesn't look right :)
[10:10] <agronholm> look at the upper right corner -- the clock and other icons are not there because the desktop is larger
[10:10] <agronholm> most dialogs are displayed off screen which is why I initially thought the installer had frozen
[10:11] <flocculant> agronholm: mmm
[10:11] <agronholm> so the question is: who do I report these multiple bugs to?
[10:11] <agronholm> the display bug and the broken keyboard layout selector
[10:11] <agronholm> and the broken grub install
[10:12] <Fudge> it all falls under ubiquity
[10:12] <flocculant> I'd report to ubiquity
[10:12] <agronholm> alright, I'll go to launchpad
[10:12] <flocculant> agronholm: what language are you using there?
[10:12] <agronholm> Finnish
[10:13] <Fudge> if the installer is still stalling, t open a terminal, control alt t. type sudo pkill -9 ubiquity  then if ubuntu-but doesnt launch, do it manually by typing ubuntu-bug ubiquity
[10:13] <flocculant> agronholm: might be bug 1549529 fopr language
[10:13] <agronholm> flocculant: perhaps
[10:14] <agronholm> but I would've assumed that I get to select another keyboard layout
[10:14] <flocculant> agronholm: and you tried to set that before the installer started?
[10:16] <agronholm> flocculant: I would have to try to boot the ubuntu ISO in legacy BIOS mode for that
[10:16] <agronholm> trying now in virtualbox
[10:18] <agronholm> yes, the keyboard layout selection looks correct if I install the right layout before starting the installer
[10:18] <agronholm> so I'm definitely hitting #1549529
[10:19] <flocculant> ok - so that's one out of the way - easy one though :)
[10:20] <agronholm> what's this casper package?
[10:28] <flocculant> that's what runs the live system afaik
[10:31] <lordievader> Wasn't casper the one responsible for setting up the live session? (Setting up the user, making sure it has what it needs, etc)
[10:32] <flocculant> lordievader: afaik yea
[10:34] <agronholm> does 16.04 use mir instead of X?
[10:34] <agronholm> in the installer
[10:34] <agronholm> that would explain why it looks so bad on a high DPI display
[10:34] <flocculant> agronholm: no
[10:35] <agronholm> then I am at a loss as to what causes the display problems
[10:35] <agronholm> it doesn't happen on 15.10
[10:35] <flocculant> agronholm: no idea I'm afraid
[10:36] <agronholm> I should boot in the "Try Ubuntu" mode on bare metal and see if it happens there too (it probably will)
[11:27] <nrosvall> is the fix for black corners round CSD windows coming to 16.04 before final release?
[11:33] <flocculant> nrosvall: supposedly - bug 1516403
[11:37] <nrosvall> Yes I noticed that too. Thanks.
[11:43] <lotuspsychje> nrosvall: you can add 'im affected' and tell your story to the bug?
[11:44] <agronholm> I'm not sure what to file a bug against (wrt the display bugs with high DPI displays)
[11:47] <lotuspsychje> agronholm: can you explain the full story? whats going on?
[11:47] <agronholm> lotuspsychje: short version: http://imgur.com/PKmfHYG
[11:48] <agronholm> the longer version you can read if you scroll back a bit
[11:49] <flocculant> nrosvall: I saw your comment yesterday, you *might* be better asking in -desktop tomorrow when there are people about who're actually working on this
[11:50] <lotuspsychje> agronholm: just joined, cant scroll back...you want install 3rd party software?
[11:50] <agronholm> lotuspsychje: you don't see anything wrong with the display in that photo?
[11:51] <lotuspsychje> agronholm: it keeps loading for next?
[11:51] <agronholm> lotuspsychje: no.
[11:52] <agronholm> lotuspsychje: do you not see that the window content is overlapped with the title bar?
[11:52] <agronholm> or that the clock and the usual symbols are missing from the upper right part of the screen?
[11:52] <lotuspsychje> right
[11:52] <agronholm> the desktop that was created is much larger than the display
[11:52] <lotuspsychje> bbl sorry
[11:52] <agronholm> which also causes any dialogs to appear off screen
[12:02] <nrosvall> flocculant, sure. I'll ask tomorrow :)
[13:16] <ika_> Hello. I just installed 16.04 on a PC with a Nvidia Fermi card and the latest prop. driver (361.x). It's an analog monitor (dsub only) and the screen is offset to the right (4:3 resolutions are displayed correcly, but those are streched and LCD panels look terrible in non-native resolution). Is there any way to fix this?
[13:16] <ika_> i.imgur.com/otx9uFh
[13:16] <ika_> https://i.imgur.com/otx9uFh
[13:23] <ChibaPet> ika_: does xrandr show the monitor as supporting the mode(s) you want?
[13:24] <ChibaPet> If not, something I've done with recalcitrant hardware in the past is to force in the correct mode.
[13:26] <BluesKaj> Hi folks
[13:26] <ika_> ChibaPet : http://pastebin.com/XLG2C4vL
[13:26] <ChibaPet> ika_: I hate pastebin - any chance you could use bpaste.net ?
[13:26] <ika_> I would have 1680x1050 as native res
[13:26] <ika_> sure
[13:26] <ika_> https://bpaste.net/show/4ee17e211fe2
[13:28] <ika_> I wonder, would it help if I would manually make a Modeline entry xorg.conf ?
[13:28] <ika_> in xorg*
[13:29] <ChibaPet> You can do that, but an easier and quicker test to see if it'll do what you want... oh, it's offering. Wait. It's showing 1680x1050 as the mode in use. What am I missing?
[13:29] <ChibaPet> Hm, I also wonder if there's a cap to modes a VGA cable will actually support.
[13:30] <ika_> vga cables support way much more (1600x1200 is the recommended tho), but never had problem with previous ubuntu builds
[13:30] <ika_> yes it's just offset so I can'T see half of the screen
[13:30] <ika_> well 40% of it
[13:31] <ChibaPet> Ah. That seems like it'd be a monitor setting. They usually let you control image offset from the monitor controls.
[13:31] <ChibaPet> Although that's easily the most dramatic offset I can remember seeing.
[13:31] <ika_> not that much I can get back about 10% with the monitor OSD
[13:33] <ika_> well, I had to try asking it here. Thanks for your time:)
[13:33] <ChibaPet> man xrandr
[13:33] <ChibaPet> there are some options that might help, but I've not found the silver bullet yet
[13:33] <ChibaPet> reading it now
[13:34] <ChibaPet> maybe --transform
[13:34] <ChibaPet> Maybe something with --pos...
[13:35] <ChibaPet> FWIW, if you find a way to do it with xrandr, there will be an xorg conf equivalent.
[13:35] <ChibaPet> ...or you can be lazy like me and invoke xrandr on login.
[13:38] <ika_> Thank you. I'm also looking into it now. I just wanted to save time, thought maybe it's a known issue.
[13:39] <ChibaPet> It's not one I've heard of before. Sorry!
[13:52] <ikonia> !info irssi
[14:26] <tracker3> Hi there
[14:27] <tracker3> Ubuntu is deleting xorg.conf at every boot. Is it me or what?
[14:29] <ika_> ChibaPet : There is a beta driver (which even adds Vulcan support). I installed that one and it fixed the issue. ( https://bpaste.net/show/2ec4073a9ded )
[14:30] <ika_> could not make it work with the previous ones, no matter what I tried
[14:30] <ika_> Just in case anyone might run into the same issue:)
[15:05] <nicomachus> ika_: thanks for not being this guy: https://imgur.com/lUmiWl3
[15:21] <lotuspsychje> agronholm: did you upgrade or clean install 16.04?
[15:22] <agronholm> lotuspsychje: see my writeup here: http://ubuntuforums.org/showthread.php?t=2318658&p=13461877#post13461877
[15:22] <lotuspsychje> kk
[15:25] <lotuspsychje> agronholm: did you installed the btrfs way on 15.10 also?
[15:25] <agronholm> lotuspsychje: yes
[15:26] <agronholm> working perfectly
[15:26] <lotuspsychje> agronholm: so on 16.04 less luck with that?
[15:26] <agronholm> indeed
[15:26] <lotuspsychje> agronholm: i think you should add a bug for all this
[15:26] <agronholm> on what package?
[15:26] <lotuspsychje> agronholm: hmmm not sure
[15:26] <agronholm> which package is responsible for the display bugs?
[15:27] <lotuspsychje> !bug
[15:27] <lotuspsychje> agronholm: we need to findout wich package is the cause
[15:27] <lotuspsychje> agronholm: still trying to puzzle your issue out :p
[15:27] <agronholm> lotuspsychje: thank you for the effort
[15:27] <lotuspsychje> agronholm: at wich point are you stuck really?
[15:28] <agronholm> it was the point at which grub install crashed
[15:28] <agronholm> I didn't want to spend more time on it as I had more important things to do
[15:28] <agronholm> I guess I could try that with virtualbox
[15:28] <lotuspsychje> yeah
[15:29] <lotuspsychje> i hear they trying to make btrfs support better so, maybe on final
[15:29] <agronholm> is this really about btrfs though?
[15:30] <lotuspsychje> not sure, still marked as experimental though
[15:30] <agronholm> raid5/6 is experimental, the rest of btrfs is stable
[15:30] <lotuspsychje> agronholm: but if you say it worked on wily
[15:30] <agronholm> yes
[15:30] <lotuspsychje> np
[15:31] <lotuspsychje> agronholm: could you check if this is similar? https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1548134
[15:33] <lotuspsychje> agronholm: the last reply on this bug, looks interesting..leaving space fro grub?
[15:33] <agronholm> lotuspsychje: that caught my attention too
[15:33] <agronholm> I didn't have to do that with 15.10
[15:33] <agronholm> but with virtualbox the partitioner insisted on it
[15:33] <lotuspsychje> weird
[15:34] <lotuspsychje> agronholm: this guy bugs it to package grub-installer
[15:34] <agronholm> the problem is, I don't want to wipe my system again to test
[15:34] <agronholm> with virtualbox I can play around but it's not the same
[15:34] <lotuspsychje> agronholm: true
[15:35] <lotuspsychje> agronholm: but as xenial still in development, i would suggest new bug to get attention on this
[15:36] <agronholm> alright
[15:36] <lotuspsychje> agronholm: https://help.ubuntu.com/community/btrfs
[15:37] <lotuspsychje> agronholm: this also mentions: When installing Ubuntu in one large btrfs-Partition without an extra boot-partition, take care to keep about 1 Mib space free at the beginning of the disk. This is possible using the partition manager in the Ubuntu installer. When there is not this space, the installer fails at the end when trying to install Grub!
[15:37] <lotuspsychje> im not the btfrs expert, but this might be the reason why grub cant install perhaps?
[15:38] <agronholm> lotuspsychje: that would make sense, I just wonder if this is a new requirement
[15:38] <agronholm> hm
[15:39] <lotuspsychje> agronholm: the wiki is edited in 2013, so think not
[15:39] <agronholm> https://bpaste.net/show/287ac1f4700e
[15:39] <agronholm> this is my current partition table
[15:40] <lotuspsychje> agronholm: well i didnt do btfrs before, so i cant really tell sorry
[15:41] <agronholm> it's ok
[15:41] <lotuspsychje> agronholm: do a few tests maybe to make sure its not a bug
[15:41] <agronholm> I'm in the process of installing 16.04 on vbox in a similar manner
[15:41] <lotuspsychje> ok
[15:43] <lotuspsychje> agronholm: found another bug: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1534922
[15:43] <tracker3> Hi there. Is it me or xubuntu 16.04 deletes xorg.conf at every boot
[15:44] <lotuspsychje> tracker3: clean installed or upgraded?
[15:44] <tracker3> upgraded
[15:44] <lotuspsychje> tracker3: from wich?
[15:44] <tracker3> 15.10
[15:44] <agronholm> lotuspsychje: this might indeed be relevant
[15:44] <lotuspsychje> tracker3: what graphics card?
[15:44] <lotuspsychje> agronholm: yeah i think so too
[15:44] <tracker3> Hybrid of Intel hd 3000 \ AMD Radeon HD 6550m
[15:44] <lotuspsychje> tracker3: radeon or amdgpu?
[15:44] <agronholm> lotuspsychje: that display bug will likely be the biggest PITA though
[15:44] <tracker3> radeon
[15:45] <agronholm> I couldn't reproduce it in virtualbox
[15:45] <lotuspsychje> tracker3: well i would suggest a clean install 16.04 test first before we start a bug
[15:45] <agronholm> so I'm assuming it's a thing with high DPI displays
[15:45] <tracker3> Im going to add chattr that xorg.conf cannot be deleted and catch the process which is deleting it
[15:45] <lotuspsychje> agronholm: 4K screen?
[15:45] <agronholm> 3K but yeah
[15:45] <lotuspsychje> kk
[15:46] <lotuspsychje> tracker3: 16.04 is still in development, so can you help test clean install, see if your radeon loads better that way?
[15:46] <tracker3> lotuspsychje, If i save /home while reinstalling ubuntu 16.04 will it count as a "clean install"?
[15:46] <lotuspsychje> tracker3: yes
[15:47] <tracker3> cya later then
[15:47] <lotuspsychje> tracker3: tnx
[15:48] <lotuspsychje> agronholm: btrfs 16.04 grub google search gives alot of those same bugs so it seems
[15:48] <agronholm> lotuspsychje: ok so remember that partition table I pasted a while back?
[15:48] <lotuspsychje> yes
[15:48] <agronholm> it showed the first partition starting at sector 2048
[15:49] <agronholm> sector size being 512 bytes
[15:49] <agronholm> 2048 * 512 bytes makes exactly 1 megabyte
[15:49] <agronholm> so that's the "embed area" in which the grub install couldn't fit
[15:50] <lotuspsychje> ah
[15:50] <agronholm> strangely, it fit there just fine when I installed it in virtualbox the same way
[15:50] <agronholm> gonna try it in EFI mode now
[15:51] <lotuspsychje> agronholm: ok good luck mate
[15:51] <agronholm> thanks :)
[16:02] <agronholm> lotuspsychje: I was able to reproduce the grub install failure in EFI mode
[16:02] <agronholm> on virtualbox
[16:03] <lotuspsychje> oh
[16:03] <agronholm> as well as the "close button not working" problem
[16:03] <lotuspsychje> agronholm: any idea how to solve?
[16:03] <agronholm> other than booting in legacy mode?
[16:04] <agronholm> I'm not even sure what's wrong
[16:04] <agronholm> it just said it couldn't install grub
[16:04] <lotuspsychje> weird man
[16:06] <penguin42> hmm someone I know I hit that the other day
[16:07] <lotuspsychje> penguin42: did you see what solved?
[16:07] <penguin42> I think in the end he attacked the disc with gparted to delete the partitioning - fdisks wouldn't get it back to get rid of that 2048
[16:07] <penguin42> I'd guessed it used to be GPT partitioned
[16:08] <lotuspsychje> agronholm: ^
[16:09] <agronholm> lotuspsychje: doesn't seem relevant to my case
[16:09] <lotuspsychje> ok
[16:10] <agronholm> strange thing...if I use the English language for the installer, I get the correct keyboard layout (Finnish) selected by default
[16:11] <agronholm> but if I choose Finnish as the installer language, it gives me US English only :P
[16:11] <agronholm> the keyboard detection on the other hand gives me a Latvian layout (wtf?)
[16:12] <lotuspsychje> agronholm: is this the daily or beta2 you tseting?
[16:12] <lotuspsychje> testing
[16:12] <agronholm> beta2
[16:12] <lotuspsychje> agronholm: maybe you can also test this on a daily iso
[16:13] <agronholm> maybe...but I'm thinking beta2 is so fresh that a daily build is unlikely to contain any major fixes at this point
[16:13] <lotuspsychje> well im on daily, and running like a rocket on my desktop
[16:13] <lotuspsychje> agronholm: just trying to widen your options :p
[16:13] <agronholm> did you boot via EFI or BIOS?
[16:14] <lotuspsychje> agronholm: bios, its an old amd3200+
[16:14] <agronholm> mhm
[16:14] <lotuspsychje> but not btfrs here
[16:14] <agronholm> then you're unlikely to hit the problems I'm seeing
[16:14] <lotuspsychje> no
[16:15] <lotuspsychje> im on ssd and ext4
[16:18] <agronholm> lotuspsychje: http://imgur.com/4u0NENr
[16:19] <agronholm> it looks like the grub package failed to install
[16:19] <agronholm> so it wasn't even about grub-install not working
[16:20] <lotuspsychje> i see
[16:20] <agronholm> I wonder where I could get more information
[16:20] <lotuspsychje> lemme lok that up
[16:21] <agronholm> looks like I'm not the first one to see this: http://askubuntu.com/questions/260297/12-04-2-failed-to-install-grub-efi-to-target
[16:21] <ika_> bye
[16:21] <lotuspsychje> agronholm: are you singleboot or dualbooting?
[16:22] <agronholm> lotuspsychje: this is a fresh virtualbox instance with no other drives or operating systems attached
[16:22] <lotuspsychje> agronholm: but are you dualbooting physically?
[16:22] <agronholm> no
[16:23] <agronholm> not sure what it has to do with this
[16:23] <lotuspsychje> agronholm: disabled fastboot and secureboot from bios?
[16:23] <agronholm> from virtualbox settings you mean?
[16:24] <lotuspsychje> agronholm: no in your physical machine
[16:24] <lotuspsychje> agronholm: check this: http://askubuntu.com/questions/485008/ubuntu-14-04-install-grub-efi-amd64-signed-failed-to-install-into-target
[16:24] <lotuspsychje> same error you having
[16:24] <BluesKaj> UEFI is such a pita, I just used the legacy mode to install kubuntu after wiping W8.1 of the drive when i received my laptop and changed the partition table to dos, no more grub install problems
[16:24] <BluesKaj> of=off
[16:25] <agronholm> BluesKaj: fair enough
[16:25] <agronholm> I guess legacy boot would solve this problem...but the display being way off is still a major issue
[16:26] <BluesKaj> agronholm, especially if you have no intention of installing Windows 8 or above
[16:26] <agronholm> yeah
[16:28] <lotuspsychje> agronholm: maybe virtualbox glitches on your grafix card
[16:28] <agronholm> lotuspsychje: you misunderstand
[16:28] <lotuspsychje> agronholm: or did the window overlay happen on physical too?
[16:28] <agronholm> the display glitches happened on bare metal but not virtualbox
[16:29] <lotuspsychje> kk
[16:29] <lotuspsychje> agronholm: what card is that?
[16:29] <agronholm> this is an integrated Intel (i195 I think), though I have an embedded nvidia 940 too
[16:30] <lotuspsychje> optimus?
[16:30] <agronholm> yeah
[16:30] <lotuspsychje> there might be our bottleneck
[16:30] <agronholm> I haven't gotten to use it as it requires kernel 4.6 :)
[16:30] <agronholm> lotuspsychje: bottleneck?
[16:30] <lotuspsychje> optimus cards always need nvidia-prime
[16:30] <lotuspsychje> and the right driver combo
[16:30] <agronholm> I would assume it uses the intel as it has on all previous ubuntus
[16:31] <agronholm> any way to check?
[16:31] <lotuspsychje> agronholm: sudo lshw -C video
[16:31] <agronholm> I will try
[16:31] <lotuspsychje> agronholm: also check additional drivers section wich driver loaded for nvidia
[16:32] <lotuspsychje> some optimus cards dont like latest driver
[16:32] <agronholm> well I hadn't gotten that far with 16.04 and 15.10 just uses the intel device
[16:32] <lotuspsychje> so maybe an nvidia-353-updates + nvidia-prime might do the trick>?
[16:32] <lotuspsychje> 352
[16:33] <lotuspsychje> agronholm: or a nomodeset install at first, then install the drivers after install
[16:34] <lotuspsychje> !nomodeset
[16:34] <agronholm> lotuspsychje: I think the installer should just work out of the box but I'll see if those options make any difference
[16:34] <lotuspsychje> ok, but as you have weird grafix issues, might be worth the test
[16:41] <BluesKaj> yeah, the optimus hybrid gpus are always a problem, but think nvidia-prime is installed by default and forget bumblebee since it's utterly useless on the newer ubuntu OSs
[16:42] <CrackerJack> nikolov@ubuntu-ivan:~$ inxi -F
[16:42] <CrackerJack> System:    Host: ubuntu-ivan Kernel: 4.6.0-040600rc1-generic x86_64 (64 bit)
[16:42] <CrackerJack>            Desktop: Unity 7.4.0  Distro: Ubuntu 16.04 xenial
[16:42] <CrackerJack> :)
[16:42] <BluesKaj> CrackerJack, ??
[16:43] <CrackerJack> just use new kernel
[16:43] <CrackerJack> not you problem
[16:43] <BluesKaj> bleeding edge for sure
[16:44] <CrackerJack> use free driver
[16:44] <CrackerJack> my is old radeon
[16:49] <iray> dropping to say that i really am loving ubuntu16.04 lts beta2
[16:49] <iray> well done!
[16:49] <agronholm> I'm surprised to see that in the "Try Ubuntu" mode I'm not seeing the graphical issues
[16:50] <agronholm> but as I expected it's using the Intel controller, not the nvidia one
[16:52] <iray> ive never had good results (with respect to multiple monitors connected to docking stations; on hp elitebook series) when using nvida drivers
[16:53] <iray> *nvidia drivers for ubuntu
[16:53] <agronholm> you mean the proprietary ones or nouveau?
[16:53] <iray> noether.
[16:53] <iray> *niether..
[16:53] <iray> though, it all works well for the case
[16:54] <iray> where i am using the default video drivers
[16:54] <iray> (non 3d accelerated drivers)
[16:54] <agronholm> in the "install ubuntu" mode I get those glitches
[16:54] <agronholm> I just snapped a photo of the setup screen
[16:55] <agronholm> is there any way to verify which driver is being used in this mode?
[16:55] <agronholm> I have no clue how to get a console here
[16:57] <tracker3> ctrl+alt+t
[16:58] <tracker3> and glxinfo | grep OpenGL
[16:58] <tracker3> will seal the deal
[16:58] <agronholm> well having opengl with nvidia 940 is impossible with kernels < 4.6
[16:59] <agronholm> ctrl+alt+t does nothing btw
[17:01] <agronholm> nomodeset had an interesting result
[17:01] <lotuspsychje> aha
[17:02] <agronholm> my laptop screen went dark but both external monitors were set to a non-optimal display mode
[17:02] <agronholm> the glitches are gone though
[17:02] <lotuspsychje> agronholm: yeah install the drivers later
[17:02] <lotuspsychje> agronholm: also cable internet + updates enabled during setup
[17:05] <agronholm> well, thanks for your assistance
[17:05] <agronholm> that's enough experimentation for today
[17:05] <lotuspsychje> agronholm: hope it gets solved mate
[17:05] <lotuspsychje> :p
[17:05] <agronholm> yeah
[17:06] <agronholm> but at least there's an easy workaround for the glitches: run ubiquity through the "try ubuntu" mode
[17:06] <lotuspsychje> :p
[17:07] <iray> i think the new kernel is doing wonders for how ubuntu is addressing my cores.;
[17:08] <iray> i used to freeze on 14.04  constantly when intellij would index source
[17:08] <lotuspsychje> :p
[17:08] <lotuspsychje> iray: nice to hear
[17:08] <iray> now, its churning through it like butter
[17:08] <iray> i VERY happy about it
[17:08] <iray> *i am
[17:08] <lotuspsychje> same here
[17:09] <lotuspsychje> 8sec boot, 3sec halt on my ssd
[17:09] <iray> yeah.. similar here.
[17:09] <iray> flying...
[17:09] <lotuspsychje> and thats on an old amd 3200+ with 2gig ram lol
[17:10] <agronholm> iray: interesting, I'm still having those issues with 15.10
[17:10] <agronholm> mouse cursor freezes with high CPU or disk usage
[17:10] <agronholm> not sure which
[17:10] <iray> 16.04 cleared it up.. its gotta be the new linux kernel
[17:11] <lotuspsychje> !info linux-image-generic
[17:11] <iray> $ uname -a
[17:11] <iray> Linux blackhole9 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:08:31 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[17:11] <lotuspsychje> yep
[17:18] <pcn> Hi everyone!  What's the status of ubuntu with prime/hybrid graphics?
[17:19] <pcn> Specifically with nvidia
[17:21] <agronholm> pcn: what card do you have
[17:22] <agronholm> (nvidia)
[17:23] <pcn> lshw says NVIDIA Corporation GM107M [GeForce GTX 960M] (rev ff)
[17:24] <pcn> sorry, lspci (any typos probably a result of my copying by hand excuse me for that)
[17:24] <agronholm> pcn: nouveau requires kernel 4.6 for accelerated graphics
[17:24] <agronholm> and even then the performance is poor
[17:25] <agronholm> http://www.phoronix.com/scan.php?page=article&item=gtx-900-nouveau&num=1
[17:26] <agronholm> my early attempts to make the binary driver work on my optimus laptop failed miserably so I've refrained from any further attempts
[17:26] <agronholm> wayland/mir have the potential to provide proper support
[17:26] <agronholm> with X it's impossible
[17:27] <pcn> How does unaccelereated nouveau compare to the intel driver, though?
[17:27] <pcn> maybe less-accellerated is a better term, but you get my drift
[17:27] <grhthy> hi guys
[17:27] <agronholm> pcn: that'd be no acceleration at all on kernel < 4.6
[17:27] <agronholm> and no, I haven't tried if it even works at all
[17:28] <agronholm> last I remember nouveau didn't even recognize my 940M
[17:28] <grhthy> is the removal of FGLRX driver a problem for someone having an amd gpu?
[17:28] <grhthy> I'm afraid of overheat
[18:07] <ryan_turner> I'm having an issue where my Dell XPS 13 9350 with 16.04 isn't suspending properly. If I go to suspend and then turn it back on, I end up at the bios Dell splash, and then once I get a user session running it has me report an error. how do I troubleshoot this more on my own?
[18:10] <pcn> ryan_turner: my 9550 is the same.  I'm very interested too.
[19:18] <BluesKaj> ryan_turner, I use sudo pm-suspend, works fine in the terminal
[19:19] <BluesKaj> pcn,^
[19:19] <ryan_turner> Will try that now.
[19:20] <ryan_turner> Yep that worked brilliantly! Now how do I do that in place of the normal suspend that happens when I close the top or use the menu?
[19:23] <BluesKaj> it's 16.04 , I just use the terminal until the problem is fixed
[19:23] <ryan_turner> Didnt realize it was a known issue
[19:23] <ryan_turner> OK, thank you!
[19:24] <ryan_turner> Any issue/ticket open that I can +1?
[19:24] <BluesKaj> well , it's known to us :-)
[19:25] <BluesKaj> I'm on kde so your power app will be different
[19:26] <BluesKaj> or may be
[21:26] <tracker4> Hi there
[21:27] <tracker4> In 15.10 my usb4g dongle detected automatically, and did well after upgrade to 16.04 beta2, but after clean reinstall of 16.04 - my usb4g dongle is not detected by system
[21:50] <tracker4> fixed by myself
[23:23] <tracker4> Hi there
[23:24] <tracker4> is it me or xubuntu 16.04 really moves my xorg.conf at every boot?