=== prth is now known as prth|away
[06:33] <mgedmin> ah the pain that is a kernel update when your / has insufficient free space
[07:44] <Noskcaj> darkxst, Is there anything i can do to speed up the gtk3 transition?
[07:45] <Noskcaj> and is it the only thing we're waiting for to and upower?
[07:45] <darkxst> they are the two most important
[07:45] <Noskcaj> *to land
[07:46] <darkxst> for gtk3 it will be a lot of patching Ubuntu themes etc, code fixes
[07:47] <Noskcaj> ok
[07:47] <darkxst> it would be good to start a thread on -desktop list about it, we are often left out of the loop when it comes to GTK transition.
[07:48] <darkxst> Otherwise pushing through the upower transition as soon as possible would be most useful
[07:48] <Noskcaj> Actually, do we need gtk3 first for upower?
[07:48] <darkxst> no
[07:48] <darkxst> upower was 3.12 stuff
[07:49] <Noskcaj> I'll prep my PPA so it can be copied straight to ubuntu
[07:49] <darkxst> so is BlueZ5
[07:49] <Noskcaj> bluez looks like more of a mess to actually package though
[07:49] <darkxst> (I would actually be curious to hear what debian did about that transition)
[07:50] <darkxst> if they removed old packages for it, we can probably do the same in vivid, but not sure if it happens via auto-sync
[07:50] <darkxst> there is so much stale cruft in the archives, that holds up these already painful transitions
[07:54] <darkxst> Noskcaj, It would also be good to fill out the packaging blueprint with more details about what is blocking what etc, I've been meaning to but havent yet
[07:57] <berglh> darkxst: I've been going through some tough life stuff at the moment, kind of in the middle of packing my lfe up and moving back to Brisbane, when I have landed and setteled I should have some more time!
[07:59] <darkxst> berglh, no problem, whenever you are ready! and all the best with the move back
[08:00] <darkxst> things will be pretty quite until gtk+ 3.14 lands anyway
[08:01] <darkxst> hopefully that will be in 3-4weeks, but that is complete guess
[08:07] <darkxst> Noskcaj, also maybe you can email -devel list and find out what/if any plans there are for ubuntu to implement DEP-11 (for gnome-software)
[08:08] <Noskcaj> ok
[08:08] <Noskcaj> I'll just ask in irc first in case someone there knows
[08:09] <darkxst> sure
[08:27] <filipposironi> hey everyone, sorry to bother but I just finished configuring a new Ubuntu GNOME installation with encrypted LVM and I found out a few issues. Basically, the system doesn
[08:29] <filipposironi> basically, the system doesn't reliably boot, the first time I switch the power on grub doesn't show any choice and the boot doesn't proceed, after a power cycle grub shows up and I'm asked for my passphrase
[08:29] <filipposironi> I also have an issue with the shutdown, which may not end at all requiring me to power off my system the hard way
[08:29] <filipposironi> have anyone encountered these issues before?
[08:36] <mgedmin> I only tested encrypted LVM once in KVM
[08:37] <darkxst> there were some possible issues with LVM in VM's but havent heard of much on real hardware
[08:37] <mgedmin> the grub boot menu shows up when the system failed to boot successfully the last time
[08:37] <mgedmin> normally it's hidden, unless you press the right key at the right time in the boot process
[08:41] <mgedmin> as for failures to shut down
[08:42] <mgedmin> I'm experiencing some due to virtualbox
[08:42] <mgedmin> http://pad.lv/1373860
[08:42] <ubot5> Launchpad bug 1373860 in virtualbox (Ubuntu) "/etc/rc6.d/K20virtualbox hangs on reboot if a VM is running" [Undecided,New]
[08:43] <mgedmin> filipposironi, if a system fails to shut down cleanly, I suggest you use the "magic sysrq" to shut it down semi-cleanly
[08:44] <mgedmin> press alt-sysrq (same key as printscreen, usually), then while holding those two keys down press S, wait a second or two until your hard disk LED goes off, then U, then B (to reboot) or O (to poweroff)
[08:44] <mgedmin> this will prevent potential disk corruption due to unwritten data in the OS disk cache
[08:45] <mgedmin> back to encrypted boot issues: you may want to browse https://bugs.launchpad.net/ubuntu/+source/cryptsetup and https://bugs.launchpad.net/ubuntu/+source/plymouth
[08:45] <mgedmin> those two components are responsible for presenting a password prompt during boot
[08:45] <mgedmin> (they're supposed to collaborate)
[08:46] <filipposironi> mgedmin, thanks for the suggestion, I'll try at the next reboot . On the grub side, if at the second boot (reboot) grub shows up it means during the first it doesn't ask for my passphrase :S I don't know if the issue is within grub or the system itself then
[08:47] <mgedmin> what happens?
[08:47] <mgedmin> does it show any text on the screen?
[08:47] <mgedmin> does it hang on boot and you hit ctrl-alt-del?
[08:47] <mgedmin> does it fail then restart by itself?
[08:47] <mgedmin> do any keys work?
[08:47] <filipposironi> nope, it just shows a gray-ish screen
[08:48] <filipposironi> no logos or whatsoever
[08:50] <filipposironi> ctrl-alt-del works
[08:50] <filipposironi> other keys don't
[08:50] <mgedmin> what have you tried?
[08:50] <mgedmin> useful keys to try: esc, alt-left (repeatedly)
[08:52] <filipposironi> a maybe useful note, the boot issue is consistent while the shutdown issue sadly is not, which makes it even more complex to analyze
[08:53] <filipposironi> apparently, both esc and lalt do nothing interesting
[09:02] <mgedmin> a picture of the gray-ish screen might be useful (or not)
[09:02] <mgedmin> the background used for the splash screen in ubuntu-gnome is sort of gray-oish
[09:02] <mgedmin> but it has a noticeable texture
[09:02] <filipposironi> it's the very same gray
[09:03] <filipposironi> anyway, I disabled all the graphical things both in the system boot and in grub and the boot became reliable
[09:03] <filipposironi> :S
[09:06] <mgedmin> what's your graphics hardware?
[09:20] <filipposironi> it's an aspeed gpu
[09:21] <filipposironi> Aspeed AST2300 to be precise
[09:22] <mgedmin> whoa, never heard of those before
[09:25] <filipposironi> it's integrated into a server motherboard
[09:25] <filipposironi> http://www.asus.com/Commercial_Servers_Workstations/P9DC4L/specifications/
[09:33] <darkxst> filipposironi, not heard of those either, but if the drivers aren't great you will have problems
[09:33] <darkxst> thats the main thing keeping linux DE's off Arm hardware as well
[09:35] <mgedmin> afaiu this thing has no 3d acceleration and uses xserver-xorg-video-modesetting
[09:36] <darkxst> that will be horrid, it should fall back to software rendering, but that is far from ideal
[09:39] <filipposironi> I know, this was an headless machine once but it know became my workstation, I'm still waiting for my new GPU to get shipped
[09:40] <filipposironi> I hope everything will start working better with my NVIDIA GTX 750 Ti
[09:40] <mgedmin> maybe
[09:40] <mgedmin> nvidia is not known for linux-friendliness
[09:41] <darkxst> mgedmin, nvidia is not know for open-source friendly
[09:41] <mgedmin> for gaming nvidia closed-source drivers probably provide best performance and feature support
[09:41] <mgedmin> for a regular desktop I'd be happiest with intel graphics
[09:41] <darkxst> their linux drivers are first-class and 750Ti runs rock solid here
[09:45] <filipposironi> Intel doesn't build PCI/PCIe graphics card as far as I know and my CPU doesn't come with an integrated GPU
[09:46] <filipposironi> I was going for NVIDIA since I'll have a multidisplay setup and I found out that NVIDIA works better in this setting than AMD (which may be a little friendlier with respect to FOSS)
[09:49] <mgedmin> so does it boot into gnome successfully now?
[09:49] <mgedmin> how fast or slow does the desktop feel?
[09:50] <filipposironi> anyway, thanks everyone for the kindness
[09:51] <filipposironi> yeah, it boots without issues and I couldn't see the shutdown issue anymore
[09:51] <darkxst> filipposironi, 750Ti with NVIDIA propriety drivers works great with my 3 monitors here
[09:51] <filipposironi> the desktop is really bad since the GPU doesn't go beyond 1024x768 and I've a 1280x1024 LCD attached
[09:52] <mgedmin> ouch ouch ouch
[09:52] <filipposironi> but as of now, I'm using my laptop to access the machine via SSH while I'm waiting for the new graphic card and the multidisplay setup to be completed
[09:53] <darkxst> filipposironi, I run 2x1280x1024 and a full HD TV panel on 750
[09:54] <darkxst> the only thing that won't work is plymouth graphical boot screen, so you don't get the nice GNOME logo at boot
[09:54] <filipposironi> I bought two 24" 1920x1080 displays, which I plan on connecting via DVI
[09:55] <darkxst> that will work as well
[09:55] <filipposironi> so, if the graphical boot doesn't work for you it means I'll have to disabled it too, and type the passphrase as I'm doing now
[09:56] <filipposironi> without any fancy graphic
[09:56] <darkxst> it uses text mode automatically
[09:56] <darkxst> once NVIDIA release their wayland drivers, graphical plymouth should work fine
[09:57] <DASPRiD> darkxst, oh, gnome shell finally supports more than 2 monitors?
[09:57] <darkxst> DASPRiD, it always has!
[09:57] <DASPRiD> i remember in being quite brken some versions ago
[09:57] <darkxst> some drivers have issues with it though
[09:57] <darkxst> I've been running 3 since about 3.4
[10:00] <filipposironi> darkxst, so I can uncomment the quite splash option in my /etc/default/grub and grub/kernel should be able to figure out everything
[10:01] <DASPRiD> darkxst, that is, on a single-head card, right?
[10:02] <darkxst> filipposironi, yes,
[10:03] <darkxst> DASPRiD, maybe not all the way back then, but for the most part yes
[11:12] <LinDol> hi all
[14:34] <mgedmin> there's a memory leak in 14.10 + staging ppa
[14:35] <mgedmin> this was the 3rd time my laptop died a swappy death
[17:42] <octoquad> darkxst, yes both flgrx and flgrx-updates are 2:14.201-0ubuntu2. Just updated from flgrx to fglrx-updates to see if anything would change but it still wants to remove all fglrx packages :(
[18:58] <celeRon_> greetings
[19:01] <celeRon_> Looking to replace windows 8 with Ubuntu Gnome, however, I'm a little puzzled because the UEFI thing isn't allowing me to install
[19:02] <celeRon_> the only work around it is to disable secure boot, which isn't all that great because I use it to protect my system in general, when leaving it unattended.
=== ccarella is now known as ccar_away
[21:14] <darkxst> octoquad, can you try boot a live CD and try there, just to rule out any local issues on your system
[21:14] <darkxst> if it was really that broken I would expect to have seen dozens of reports by now
[21:58] <octoquad> sure