[00:40] <pedahzur> That was fun. Upgraded to KDE 4.13. Log in. Notes pops up, says it wants to migrate my notes. I say go for it.  But now notes says I have no notes. Grr.
[00:40] <pedahzur> Also, how does one restart kdm these days? There is no /etc/init.d/kdm file any more.
[00:43] <pedahzur> Thankfully I still have ~/.kde/share/apps/knotes/notes.ics  But it would be nice if the migration had actually worked.
[00:44] <Chaser> pedahzur: isn't it lightdm ?
[00:44] <pedahzur> Chaser: Maybe? There is not /etc/init.d/lightdm either.
[00:44] <pedahzur> *no
[00:47] <rvdv> I have done a new installation of Kubuntu and here there is a /etc/init.d/lightdm
[00:47] <Chaser> me too, have lighttd init file. Standard kubuntu 14.04.
[00:48] <rvdv> lightdm and lightdm-kde-greeter are both installed
[00:55] <pedahzur> Sorry, this is 12.04.
[01:17] <TheFakeazneD525> pedahzur: sudo restart kdm
[04:51] <silv3r_m00n> hi there
[04:52] <silv3r_m00n> i am unable to change the font size for gtk apps, from systemsettings > appearance settings > GTK, any idea how to fix this ?
[05:57] <silv3r_m00n> on kubuntuforums, where is the option to reset password ?
[06:40] <lordievader> Good morning.
[06:41] <Luke_T> hey could anyone help with a pretty big problem i'm having?
[06:42] <valorie> Luke_T: what problem?
[06:43] <Luke_T> I've been trying to uninstall kubuntu but i can't get it to work at all. I initially installed it with pendrivelinux and since i did that, I haven't been able to use pendrivelinux again for a different operating system
[06:43] <Luke_T> i'm trying to put OSX back on
[06:44] <Luke_T> oh yeah I should probably mentiion its a macbook
[06:46] <lordievader> Luke-T: Shouldn't the OSX installer take care of that?
[06:47] <valorie> uninstall?
[06:48] <valorie> You can just wipe that part of the disk
[06:48] <Luke_T> sorry for being a noob but how would i do that?
[06:49] <valorie> I don't know anything about installing OSx, sorry
[06:50] <Luke_T> i mean how would i wipe it? everything i've tried hasnt worked so far
[06:50] <lordievader> Open a partition editor and remove the kubuntu partitions.
[06:50] <valorie> on your 'pendrivelinux' you could put a disk repair ISO
[06:50] <lordievader> Also people don't like it when you crosspost.
[06:51] <valorie> or if it's just one or two partitions, rather than the whole disk, what lordievader said
[06:51] <valorie> !partition
[06:51] <Luke_T> thanks for the help i'll try that, also sorry for cross posting it was just annoying me :P
[07:16] <F-3000> Heya there! I got this fancy problem, that I got boot sector (MBR) on wrong place. It should be on internal HD (sda), but it went to USB-stick (sdb) during install - a and b were opposite than normally and I forgot that in one point. Kubuntu itself works good, it just doesnt boot if that USB-stick isnt in place. Could someone hint me about how to move/reinstall only the MBR? Using GRUB, as default on Kubuntu (14.04). I installed thru mini
[07:17] <F-3000> Suprisingly a lot multilive-USB gives headaches. :D
[07:20] <valorie> F-3000: this happens suprisingly often
[07:20] <valorie> !grub
[07:20] <valorie> you'll want grub2
[07:21] <valorie> and the restoregrub has good stuff too
[07:32] <lordievader> F-3000: Just install grub to sda again.
[08:02] <F-3000> valorie and lordievader: thanks. Mere sudo grub-install /dev/sda did the trick. :) Now I need to figure out how to restore grub for the multiliveusb. :P
[08:03] <lordievader> F-3000: Boot into it and run "sudo update-grub2"?
[08:03] <valorie> multi-liveUSBs are sort of unreliable, IMO
[08:04] <F-3000> valorie: It has worked quite well for me. Only problem is, that I cant access the start-menus of the ISOs.
[08:07] <F-3000> valorie: And I have to keep in mind that sda and sdb might swap, so that I don't have to go thru this again. :P
[08:09] <F-3000> valorie: Well, maybe one "problem" is, that I cannot choose guided partitioning, as mostly innerHD is not available as an option, only the multiliveusb, which I find extremely odd.
[08:10] <valorie> I found the multiUSB to be useful to show off various ISOs
[08:10] <valorie> but not reliable for installing
[08:11] <F-3000> How it's unreliable for installing?
[08:11] <valorie> that's been my experience
[08:11] <F-3000> What difficulties you've faced?
[08:13] <F-3000> valorie: Just out of curiosity. Maybe I can learn something.
[08:14] <valorie> the same as you -- misplaced grub
[08:16] <F-3000> valorie: Heh, usually grub goes into proper place. This time, a & b were swapped, and I forgot to change sda to sdb when minimal-install asked for grub location.
[08:16] <valorie> OK
[08:33] <nick87720z> hello. I just got kde 4.13 from kubuntu backport ppa. Made full reboot just for kdm restart (was a bit lazy to do it manually). Now akonadi doesn't work: http://paste.ubuntu.com/7378246/
[08:46] <F-3000> Some hints how to start figuring out why wlan isn't working? I've installed restricted drivers that Kubuntu suggested (thru Driver Manager), yet still nothing. Wlan cannot be enabled thru network manager.
[08:47] <lordievader> F-3000: Is the correct driver loaded? (lspci -k|grep Network)
[08:49] <F-3000> lordievader: Will check, once system has booted. Thought of booting with acpi=off option, but forgot to add it (removed splash and quiet).
[08:51] <lordievader> F-3000: It's better to leave acpi on, especially on a laptop.
[08:52] <F-3000> lordievader: It works oddly. Not as snappy as much slower desktop, cannot shutdown/reboot (have to do 5sec powerbutton down to shut down after "will now halt").
[08:58] <F-3000> lordievader: Not sure if correct driver is in use. "Kernel driver in use: wl"
[08:59] <lordievader> Broadcom device? Should be right, does it show up in iwconfig?
[08:59] <F-3000> lordievader: Ay, broadcom, BCM4311.
[09:00] <F-3000> lordievader: iwconfig shows "no wireless extensions." on both eth0 and lo.
[09:01] <lordievader> Hmm, yesterday was someone with the same chip and problem.
[09:02] <lordievader> You may try the opensource driver.
[09:05] <F-3000> lordievader: From Driver Manager, right?
[09:05] <lordievader> https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx
[09:08] <F-3000> lordievader: Alright, thanks. I'll fool around with that page's info. :)
[09:09] <F-3000> lordievader: Driver Manager anyways shows only driver options for NVIDIA. I've selected recommended already. Luckily there was howto available how to do it thru terminal, as nouveau crashed if tried to actually do something.
[09:33] <F-3000> lordievader: Tried acpi=off, looks like it was a bad idea with actual installed system. With liveusb it worked better.
[09:54] <BluesKaj> Howdy folks
[10:15] <F-3000> BluesKaj: Hey there. :)
[10:15] <BluesKaj> hi F-3000
[10:17] <F-3000> BluesKaj: Got Kubuntu running good, booting working properly, wlan connects. Now I only need to figure out how to fix laptop's unwillingness to shut down. :P
[10:17] <F-3000> *shutdown properly
[10:18] <F-3000> BluesKaj: Eh, it did just that. Disabling wl driver had such effect? Is that possible??
[10:19] <BluesKaj> wierd
[10:22] <BluesKaj> if it won't shit down run , init 0
[10:22] <F-3000> Doh! How to make driver b43 (for broadcom) to start automatically? Currently it requires doing modprobe.
[10:23] <F-3000> BluesKaj: I hope it wont shit down. :D
[10:23] <BluesKaj> hehe
[10:26] <F-3000> Oh, I need to remove "blacklist b43" from /etc/modprobe.d/blacklist-bcm43.conf ?
[10:26] <BluesKaj> yeah, makes sense
[10:27] <F-3000> This is odd. After blacklisting wl, laptop definitely seems to work better.
[10:28] <F-3000> No more background distortion behind dialog when selecting "Leave", instead just black.
[10:29] <F-3000> Laptop actually shuts down, instead of freezing after showing "system going to halt" (or something alike, cant remember exact anymore?)
[10:31] <F-3000> After I installed firmware-b43-installer and rebooted, something got tainted during boot. Cant remember anymore what it was, didnt fully understand what happened. Doesnt happen anymore.
[10:32] <BluesKaj> keep up with the updates and upgrades and all should be well
[10:33] <shadeslayer> F-3000: fwiw try linux-firmware-nonfree
[10:33] <shadeslayer> that might work
[10:33] <F-3000> shadeslayer: Driver Manager suggested that, I installed it.
[10:33] <doctorpepper_> can anyome tell me which package contains plasmoidviewer
[10:33] <shadeslayer> F-3000: and it worked?
[10:34] <F-3000> shadeslayer: I didn't see any difference, nor I know why it was suggested, to be honest.
[10:34] <fulton> Anyone had a problem upgrading from 12.04.4 to 14.04 where at some point KDM would restart and drop into a shell?
[10:35] <shadeslayer> F-3000: Broadcom usually has many issues :/
[10:35] <shadeslayer> sometimes it works, many times it doesn't
[10:36] <F-3000> shadeslayer: This one works good with b43.
[10:36] <shadeslayer> ok
[10:36] <BluesKaj> fulton, lightdm is now the default for 14.04
[10:37] <BluesKaj> F-3000, could be dnsmasq bug ..I had it earlier , alt+F2 , kdesudo kate /etc/NetworkManager/NetworkManager.conf , comment the line dns=dnsmasq, with a # in front
[10:37] <F-3000> BluesKaj: What's that?
[10:38] <F-3000> BluesKaj: I know dns, but masq... I think I've read about it, but cant remember.
[10:38] <fulton> that was *during* the upgrade, not after; didn't return to desktop so I don't know what happened to the upgrade procedure
[10:38] <BluesKaj> dns may be buggy
[10:38] <BluesKaj> masq rather
[10:38] <BluesKaj> !dnsmasq
[10:39] <BluesKaj> !info dnsmasq
[10:40] <BluesKaj> fulton, has the install fifnshed successfully ?
[10:40] <BluesKaj> finished*
[10:41] <fulton> don't know, it dropped me back into the shell; there was a dpkg running and a python <defunct>
[10:41] <fulton> can I trigger something from the command line?
[10:42] <F-3000> BluesKaj: Funny thing. Not utterly useless, I'd suppose.
[10:42] <fulton> or just reboot?
[10:43] <BluesKaj> fulton, if you're in a shell try installing lightdm
[10:44] <BluesKaj> F-3000, I have the bcm 4313 chip  and had a similar problem with wifi
[10:48] <F-3000> BluesKaj: My only problem currently is, that b43 doesnt start without manual modprobe.
[10:49] <BluesKaj> F-3000,  try running sudo dhclient wlan0 instead of modprobe
[10:50] <F-3000> BluesKaj: Response: Cannot find device "wlan0"
[10:51] <F-3000> BluesKaj: There's no blacklist rule for b43, yet it still doesn't get loaded at startup.
[10:51] <BluesKaj> F-3000, run iwlist scan and look for wlanX
[10:52] <BluesKaj> X being a different number than 0
[10:52] <F-3000> wlan0 exists after modprobe b43
[10:52] <BluesKaj> ok
[10:56] <F-3000> Any suggestions how to get b43 loading at startup?
[10:57] <F-3000> Do I need to make a script to do modprobe? :P
[10:59] <BluesKaj> F-3000, have you seen this, http://askubuntu.com/questions/305079/how-do-i-get-the-right-wireless-modules-to-load-at-startup-for-a-bcm4322
[11:02] <F-3000> BluesKaj: Now I have. If b43 is supposed to be in /etc/modules, that's the reason why it wasnt working.
[11:03] <BluesKaj> did that tut help then ?
[11:03] <F-3000> BluesKaj: Testing it right now.
[11:05] <F-3000> BluesKaj: It e
[11:06] <F-3000> BluesKaj: It helped with starting the driver, although now wlan didnt autoconnect.
[11:06] <F-3000> BluesKaj: And I noticed that Network Manager's menu goes below bottom panel.
[11:07] <BluesKaj> F-3000, http://linuxg.net/how-to-fix-broadcom-bcm4311-wireless-driver-on-ubuntu-and-linux-mint/
[11:08] <BluesKaj> scroll down to "To make it work automatically,"
[11:08] <F-3000> BluesKaj: wlan autoconnected when I did manual modprobe.
[11:09] <F-3000> BluesKaj: But I'll take a look at the page. :)
[11:09] <BluesKaj> autoconnected is not the correct choice of words there, you shouldn't have to modprobe to autoconnect
[11:12] <F-3000> BluesKaj: I know that modprobe shouldnt be needed for wifi autoconnection. I find it odd that autoconnection didnt occur. Maybe it's because secrets are local (user), and wlan was started before user had logged in, it failed?
[11:12] <F-3000> BluesKaj: I'll reboot and confirm that autoconnect fails, then I'll see what happens when I change connection settings to allow any user to connect with them.
[11:14] <F-3000> BluesKaj: Now it worked. :D This is both hilarious and frustrating. :P
[11:15] <BluesKaj> so it was user permissions
[11:15] <F-3000> BluesKaj: I didnt get that far.
[11:15] <F-3000> BluesKaj: I didn't change anything, just rebooted.
[11:15] <BluesKaj> ok
[11:15] <F-3000> BluesKaj: Now I'm doing yet another reboot without any changes.
[11:17] <F-3000> BluesKaj: Again, it worked. I dont know what made it fail at the first time.
[11:18] <BluesKaj> if you ran those commands in the tut then the autoconnect is turned on at startuo
[11:19] <F-3000> BluesKaj: I'll try delayed login now (not logging in asap).
[11:19] <F-3000> BluesKaj: I didn't run any of the commands from tut.
[11:19] <F-3000> I added b43 to modules with nano.
[11:19] <BluesKaj> ok, basiclly the same effect
[11:20] <F-3000> Ay.
[11:20] <F-3000> BluesKaj: Delay had no effect, still connection. At least its tested that autoconnecting works now, hah.
[11:21] <F-3000> BluesKaj: Should I remove default driver, though?
[11:21] <BluesKaj> F-3000, if it works now , don't "fix" it
[11:22] <F-3000> BluesKaj: Alright. :D I thought same. ;)
[11:22] <BluesKaj> the default driver wasn't loading afaik
[11:23] <BluesKaj> you just needed it to add it to /etc/modules
[11:23] <BluesKaj> err needed to
[11:26] <F-3000> BluesKaj: If wl was default, it's off thru blacklist.
[11:28] <F-3000> BluesKaj: And yes, got b43 to work by adding it to /etc/modules. Funny that [...]-installer didn't do something already.
[11:28] <BluesKaj> bcm wifi can be troublesome , but most bcm probs are solvable IME
[11:57] <F-3000> BluesKaj: Alright, I think the laptop's running good for now. Huge thanks for your assistance! :)
[12:40] <risetkt> hello
[12:40] <risetkt> 0.0
[12:40] <risetkt> 0.0
[12:40] <risetkt>  any body here?
[12:40] <risetkt> anybody here?
[12:40] <risetkt> 0.0
[12:40] <BluesKaj> risetkt, yes
[12:41] <risetkt> 0.0 wow
[12:41] <risetkt> i want to report a bug
[12:41] <wolf__> here
[12:41] <BluesKaj> !bug
[12:41] <risetkt> ok  thanks
[12:42] <BluesKaj> just make sure it's not already reported risetkt
[12:43] <BluesKaj> you can confirm on launchpad that it affects you too if the bug has already been filed
[12:44] <BluesKaj> risetkt, don't pm pls, we can discuss in here
[12:44] <risetkt> oh sorry..
[12:45] <risetkt> but how can i search bugs? like if i want to search bugs on chrome browser , what should i do?
[12:47] <risetkt> ahh...0.0
[12:49] <BluesKaj> rethus, open dolphin help, then bug report, then choose the app from the dropdown
[12:50] <BluesKaj> risetkt,^
[12:50] <risetkt> ok thanks
[13:24] <nick87720z> hey again, i just got response on #kde about one eventually appearing problem with akonadi database
[13:24] <nick87720z> [02.05.14 19:17:21] <rdieter> nick87720z: some post akonadi-1.13.1 upstream commits try to fix that, either poke your packagers to include that, or wait for akonadi-1.13.2 release
[13:25] <nick87720z> [02.05.14 19:20:08] <rdieter> nick87720z: see https://bugs.kde.org/show_bug.cgi?id=331867
[13:26] <nick87720z> This is exactly what i have after upgrade to kde 4.13 from backport ppa
[15:28] <Meepers> Hi.
[15:28] <Meepers> Anyone here?
[15:29] <Meepers> I just installed Kubuntu on a Asus G750
[15:29] <Meepers> Dual booting with Windows 8.1
[15:29] <Meepers> And Kubuntu detects my wireless chipset.
[15:29] <Meepers> But when I load it and click apply...
[15:29] <Meepers> Nothing happens.
[15:30] <Meepers> The driver manager keeps nagging me about the driver.
[15:30] <Meepers> But when I try to load the driver...
[15:30] <Meepers> It just reloads and keeps nagging me.
[15:30] <Meepers> Any help?
[15:34] <BluesKaj> Meepers, which wifi chip ?
[15:36] <BluesKaj> Meepers, sudo lshw -C network
[15:52] <dougiel> is it called the system tray where the clock sits? why is it sometimes the icons in my 'system tray' are white and sometimes they are coloured?
[15:54] <dougiel> white with a glowing effect if I remember right
[16:06] <BluesKaj> bbl
[16:11] <meepers> Where is everyone?
[16:14] <meepers> Hi?
[16:14] <meepers> Can anyone help me?
[16:19] <meepers> Where is everyone?
[16:21] <rvdv> meepers: Just ask
[16:29] <meepers> I installed Kubuntu on my Asus G750
[16:29] <meepers> ...And in the LiveUSB is detected our Broadcom 802.11ac wireless chip.
[16:29] <meepers> And everything was going well.
[16:29] <meepers> But after installing, the driver manager detects the chip.
[16:30] <meepers> But when I try to load it, it doesn't.
[16:30] <meepers> The manager just reloads and nags me to load the driver again.
[16:36] <meepers> Why is the driver manager doing that?
[16:36] <meepers> And how do I get the driver loaded?
[18:15] <M0rgenstern> Hello
[18:17] <M0rgenstern> Could someone help me please with kubuntu's cryptsetup? I installed kubuntu and now it won't let me in
[18:38] <meeperkins> HI
[18:38] <meeperkins> Is anyone available to talk
[18:38] <meeperkins> ?
[19:17] <Whiskey`Wonka> yay more cpu fan issues
[19:18] <Whiskey`Wonka> was working fine in 13.10. did the upgrade to 14 and stopped working
[19:19] <Whiskey`Wonka> checking, acpi/ibm/fan said it was disabled, i did somethings and now it sas enabled but it still speed:0
[19:19] <Whiskey`Wonka> why is there no trivial way to just say "fan run at RPM ABC"
[19:50] <designs> hello everyone
[19:50] <designs> is anyone aviable to help me with something?
[19:57] <pmd`> designs: just ask and wait, if anyone can help, they will.
[21:49] <Etriaph> I'm having a strange issue with Rekonq in the past couple of days.  Flash videos (YouTube) are displaying the skin on people as a pale blue.  Color correction issue maybe?
[22:34] <zenx> wow kubuntu 14.04 is so awesome
[22:41] <valorie> zenx: I'm finding it smooth as silk
[22:41] <valorie> what are you liking?
[22:43] <zenx> first of all the development tools like kdiff, kate, kdevelop(heard good things about it)
[22:43] <zenx> but the polish is incredible, no program crashes so far
[22:43] <zenx> graphics are top
[22:44] <zenx> very smooth indeed
[22:44] <zenx> next gen desktop :D
[22:47] <valorie> I'm happy to hear that
[22:47] <valorie> usually we only hear the growls here!
[22:47] <valorie> nice to hear compliments as well
[22:51] <zenx> maybe kde users are more demanding :P
[22:52] <zenx> the last place I worked almost everyone bye the time I left had converted to kde
[22:55] <valorie> well, people come into IRC because they have problems
[22:55]  * valorie just lives here
[23:05] <zenx> that or quassel has kubuntu in the autojoin list
[23:56] <Whiskey1> valorie: well, kubuntu isnt do bad. a few issues, like my FAN not working. would love to fix that. else its decent nad all my gear runs it.
[23:58] <valorie> not sure about the fan, Whiskey1 -- have you filed a bug?
[23:58]  * valorie goes off to dinner
[23:59] <Whiskey1> valorie: oh its 'not a bug' acording to everyone else