[00:01] <cxdvty> !ipod
[00:01] <ubottu> For information on how to sync and add tracks to your iPod, see the guide at https://help.ubuntu.com/community/IPodHowto - For the iPhone and the iPod Touch, see https://help.ubuntu.com/community/PortableDevices/iPhone - See !RockBox for information on liberating your iPod
[00:06] <cxdvty> k1l: Know what we should do? lol
[00:20] <k1l> i dont have apple hardware but people tell one should try itunes in wine.
[00:30] <cxdvty> it doesnt work for me
[00:31] <cxdvty> k1l: will jailbreaking services (such as redsn0w) work with wine?
[00:31] <k1l> i would not flash anything with wine
[00:33] <cxdvty> ok
[00:50] <k1l> now its plymouth-start.service failing on systemd, too
[00:56] <cxdvty> k1l: Wine won't run anything on my pc it always fails
[00:56] <cxdvty> !raring
[00:56] <ubottu> Ubuntu 13.04 (Raring Ringtail) was the 18th release of Ubuntu. Support ended on January 27, 2014. See !eol, !upgrade and http://ubottu.com/y/raring
[00:57] <cxdvty> k1l: you there?
[00:58] <k1l> ?
[00:58] <cxdvty> Wine wont run any windows programs at all it just crashes
[00:59] <k1l> i dont use wine nor do i use apple hardware or itunes. and i dont know if the wine guys will support wine running on a development ubuntu
[00:59] <cxdvty> imon 14.04 rn
[01:00] <k1l> then you are wrong in this channel with that issue. 14.04 is #ubuntu supportwise. but i would suggest to talk to the #winehq guys
[01:00] <k1l> !wine | cxdvty
[01:00] <ubottu> cxdvty: WINE is a compatibility layer for running Windows programs on GNU/Linux - More information: https://help.ubuntu.com/community/Wine - Search the !AppDB for application compatibility ratings - Join #winehq for application help - See !virtualizers for running Windows (or another OS) inside Ubuntu
[01:02] <cxdvty> k1l: is it hard to setup vmbox
[01:03] <k1l> no
[01:03] <cxdvty> I dont have a installation disc tho d:
[01:04] <cxdvty> Can i setup windows vmbox without it
[01:04] <k1l> no you need some installation media.
[01:05] <cxdvty> dang can i install it from online?
[01:08] <cxdvty> ??
[01:14] <cxdvty> k1l ^^
[01:15] <k1l> i dont know what windows offers today to install their OS. ##windows will know
[04:29] <rat> keithzg: I'm running a Acer C710 Chromebook. My hangs during boot may have been due to invalid entries in fstab which were created during install. Haven't rebooted to see if that's the case yet.
[04:29] <rat> Still haven't found an explanation for why I lost HIDs on Systemd boot
=== Malsasa_ is now known as Malsasa
=== Malsasa_ is now known as Malsasa
[08:59] <lordievader> Good morning.
[10:21] <Dulcin> Hi, I just installed the Ubuntu vivid daily, now when I maximize my terminator window it is dimming my screen, but only when I maximize it on my second monitor (dual monitor setup). Is this a new setting or a bug?
[10:22] <igalic> so yesterday i upgraded my system to 15.04, and now my cryptsetup is hosed (again). i have to manually encrypt my disks (plural) in initramfs, and even then it only works when booting through upstart. (which is kinda funny, cuz upstart was removed , only upstart-bin is left;)
[10:29] <igalic> Setting up libwayland-egl1-mesa:amd64 (10.5.0-0ubuntu1) ... ← i want to believe.
[10:34] <k1l_> Dulcin: that sounds like the "program is hanging" dimming. and not like a monitor dimming
[10:55] <Dulcin> k1l_, hmmm, it's strange because only terminator seems to do this, when I maximize. As soon as I right click for the mouse menu, it fades in again. Or when I resize the window, or move another window on top of it.
[10:56] <Dulcin> k1l_, Also when I maximize it on my other dual monitor, this behaviour is not replicated... so a bug then?
[10:56] <k1l_> well, does terminator log errors somewhere? or start terminator from another terminal and see if it errors there.
[10:56] <k1l_> i would call this a bug, yes
[10:57] <k1l_> maybe its just some theme or glib issue
[10:58] <Dulcin> It does give an error when I run it in another terminal, but I don't think it's related
[10:58] <Dulcin> k1l_, /usr/share/terminator/terminatorlib/window.py:63: Warning: The property GtkWindow:allow-shrink is deprecated and shouldn't be used anymore. It will be removed in a future version.
[10:58] <Dulcin>   self.set_property('allow-shrink', True)
[10:59] <Dulcin> Ok let's hope it will be fixed after the stable release
[11:00] <k1l_> well, if you file the bug report now the chances are way better it gets fixed for the release.
[11:00] <k1l_> !bug
[11:00] <ubottu> If you find a bug in Ubuntu or any of its derivatives, please file a bug using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs.
[11:00] <Dulcin> I'll do that
[12:36] <owlman> Hi all. Seeking some help with a fresh install of vivid-beta1 on new hardware
[12:37] <owlman> specifically a lenovo thinkpad Helix 2nd generation tablet with the ultrabook pro keyboard
[12:38] <owlman> Once sddm launches the keyboard dock stops working, and in tablet mode there is no virtual keyboard launched
[12:39] <owlman> grub recognises the keyboard dock, and launches a virtual keyboard in tablet mode
[12:40] <owlman> touchpad on keyboard dock and touchscreen both work
[12:43] <BluesKaj> Howdy all
[13:49] <igalic> really good to know that kernel 3.19 will fix my partner's networking issues, cuz, i upgraded my machine to test the upgrade in gernal, and her reaction was: i don't want that thing on my computer.
[13:50] <igalic> now my wifi card, which worked fine with 3.16 is breathtakingly slow and jittery it makes my eyes bleed.
[14:27] <mparillo> Is anybody having to re-connect to a WEP network with every re-boot? I opened https://bugs.kde.org/show_bug.cgi?id=344600 I am afraid they will claim it is *buntu-specific and point to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924 because 'Everything works on Debian Unstable' according to invalid https://bugs.kde.org/show_bug.cgi?id=340568
[14:27] <ubottu> KDE bug 344600 in applet "Network Manager Widget does not 'remember' to connect to previous WEP network" [Normal,Unconfirmed]
[14:27] <ubottu> Launchpad bug 1354924 in network-manager (Ubuntu) "Networkmanager does not autoconnect to wireless network" [Medium,Confirmed]
[14:27] <ubottu> KDE bug 340568 in applet "Plasma-nm doesn't reconnect automatically" [Minor,Resolved: invalid]
[14:43] <akiva-thinkpad> uhmmm, is this right: http://imgur.com/tgbHemW
[14:49] <k1l_> lol
[14:50] <k1l_> i dont use the softwarecenter, so i dont know. but it looks maybe a little too big to me :)
=== Toledo is now known as croberts
[17:21] <MoonUnit`> anyone had their screen go blank when updating today, got the kubuntu boot logo then 3 systemd services appeared then nothing, logged into another tty to check it finished updating then rebooted.
[17:27] <mparillo> MoonUnit`: Yes, I got a ton of TTY error messages relating to components of open-vm-tools-desktop I sent my VM an alt-ctrl-delete, forced my VM down, and Kubuntu Vivid came back.
[20:18] <keithzg> So any ideas why switching to systemd is caused root filesystems (at least mine, and apparently then some others') to initially mount read-only even thought the output of 'mount' claims rw?
[20:31] <keithzg> Guess I should pull down teh updates since yesterday and just see if that's fixed, heh.
[20:33] <elfy> I'm still pondering the non-usable state of our images
[20:36] <cxdvty> Hey all :D
[20:41] <BluesKaj> keithzg, I have 2 hdds on this pc and no trouble mounting or moving files between the two drives, running systemd on kubuntu 15.04
[20:46] <keithzg> BluesKaj: Definitely not saying it's universal, but at least myself and lordievader had our root filesystems now mounting as secretly read-only upon boot under systemd. He's using NFS, I'm using ext4 on a Chromebook, so not sure what the shared causal factor is.
[20:49] <keithzg> Damn, the latest round of updates fixed nothing.
[21:00] <keithzg> At least lightdm seems to load Plasma 5 sessions just fine now (haven't given sddm another shot yet)
=== Toledo is now known as croberts
[21:10] <lordievader> keithzg: Hmm, guess I'll update the other box soon.
[21:30] <keithzg> Hmm, just double checked and at least now upon boot / does indeed report that it's mounted ro