[00:43] <sfn> I have Installed Kubuntu14.10 and mysql-workbench. query runs but results are not displayed in the result window
[02:57] <novato_kde> Hi!, i am a novice in linux, i have a kubuntu 12.04 but some days ago the kde log manager crash, and after put the pswd and hit enter
[02:58] <novato_kde> the pc don log in and says a fatal error ocurred, check kdm logfiles, any advice
[03:04] <novato_kde> Help...!
[03:33] <LogicalDash> The mixer applet in my systray seems to have no effect on actual sound levels at all, and doesn't show the same levels as KMix does. KMix can adjust volume correctly though. What might cause this?
[04:19] <crdpink> LogicalDash: tried selecting the master channel in kmix? If it's a widget try removing then adding again. (I have to do both these things with a sound widget I use)
[04:20] <LogicalDash> crdpink: master channel did it, thanks
[04:20] <crdpink> sweet
[06:13] <max> hi all
[06:13] <max> ololo
[06:13] <Guest28682> piu piu
[07:58] <CHR0N0S> Hello, can somebody please help me to resolve shutdown problem on fresh install of Kubuntu 14.04? I have tried all kinds of solutions without any success!
[07:58] <hateball> CHR0N0S: What does "shutdown problem" mean more specifically
[07:59] <CHR0N0S> hateball: I mean that when I try to shutdown my machine it starts the procedure but hangs before powering off!
[08:02] <lordievader> CHR0N0S/hateball: Interesting to note is that the problem ain't there when he shutsoff from a tty.
[08:02] <CHR0N0S> hateball: When I goto shutdown the only way to get it to power off is to start the shutdown procedure and wait until it hangs then press and hold the power button.
[08:04] <CHR0N0S> lordievader: I have tried this also when booted from a live disc and it does exactly the same thing!
[08:04] <hateball> Does it happen if you shut down from lightdm, before logging in?
[08:05] <CHR0N0S> lordievader: I tried it using a different machine from the same live disc and it shut down and powered off normally.
[08:06] <CHR0N0S> hateball: Not sure what you mean am still a newbie when it comes to linux!
[08:06] <hateball> CHR0N0S: I mean on the login window, before you reach the desktop
[08:06] <CHR0N0S> hateball: haven't tried that yet!
[08:07] <CHR0N0S> hateball: I can log out and try if you like?
[08:13] <hateball> CHR0N0S: Well it's one thing to try, just to see if it's something KDE related that hangs or if it's pure hardware
[08:13] <CHR0N0S> hateball: I can always try also do you need my system specs?
[08:14] <hateball> CHR0N0S: not now no :)
[08:14] <CHR0N0S> hateball:  ok will log out and try as you suggested!
[08:14] <CHR0N0S> b.b.i.a.b.
[08:24] <CHR0N0S> hateball: I'm a little embarassed, I forgot to mention that when I installed I configured Kubuntu to autologin, the only way I can reach the screen you mentioned is do a log out after having already logged in to system!
[08:25] <hateball> CHR0N0S: Yes well that shouldnt matter in this case
[08:26] <lordievader> Unless the KDE session starts something nasty that doesn't want to die on shutdown...
[08:26] <hateball> Yes
[08:26] <CHR0N0S> hateball: I tried what you suggested from there after I left and still the same results!1
[08:26] <hateball> Alright, hmmm
[08:26] <valorie> you can choose to start each session "clean" or resume the previous session
[08:27] <valorie> in systemsettings
[08:27] <lordievader> valorie: That should've went to #kde ;)
[08:28] <hateball> CHR0N0S: Oh, does a reboot have the same behavior, or is it only when you Shut down?
[08:28] <CHR0N0S> hateball: only shutdown misbehaves reboot does ok!1
[08:28] <lordievader> CHR0N0S: Ah, in all cases?
[08:29] <CHR0N0S> lordievader: everytime I've tried it!
[08:29] <lordievader> CHR0N0S: Ok, great.
[08:30] <CHR0N0S> lordievader: I'm beginning to get a sneaky suspicion this is machine related not O.S.?
[08:31] <lordievader> CHR0N0S: Try shutting down from a tty after stopping lightdm. If it still has the problem then I'm starting to agree ;)
[08:32] <CHR0N0S> lordievader: please can you tell me how to do that again as I didn't take notes the first time we tried it?
[08:33] <CHR0N0S> lordievader: oh wait I did take notes too I just had to find them....:D
[08:34] <CHR0N0S> okay here goes nothing, B.B.I.A.B.
[08:44] <CHR0N0S> ok going to try this from my laptop so leave desktop free to work on and still be here online!
[08:44] <CHR0N0S> lordievader: I must have done something wrong because instead of shutting down it did rebbot!
[08:45] <CHR0N0S> reboot, even
[08:48] <lordievader> CHR0N0S: What was the last command you issued?
[08:48] <CHR0N0S> lordievader: sudo shutdown now -h -r
[08:49] <CHR0N0S> lordievader: just tried again and omitted the -r option and it hangs as usual.
[08:52] <CHR0N0S> lordievader: don't think it has anything to do with the current issue but when I try to use this or any other method to shut down with it seems as if the system cooling fans speed up or get louder than normal?
[08:52] <hateball> CHR0N0S: Do you have any "weird" peripherals plugged in, or what sort of system is this?
[08:53] <hateball> Since it seems the kernel chokes trying to halt, perhaps it doesnt like something in your hardware config
[08:54] <lordievader> Chaser: Use "sudo poweroff" to poweroff.
[08:54] <CHR0N0S> hateball: desktop and only peripherals I have plugged in are a webcam and an external usb hard drive
[08:54] <CHR0N0S> hateball: oh and my wireless mouse
[08:55] <CHR0N0S> lordievader: from where do I issue that command from terminal or tty1?
[08:55] <hateball> CHR0N0S: You could try removing the external HDD unless you need it at all times
[08:55] <hateball> It could be it fails to unmount it or something
[08:56] <lordievader> CHR0N0S: Yes, after your stopped lightdm.
[08:56] <CHR0N0S> hateball: I use it quite often as it is my main storage where I keep files that I may need?
[08:56] <hateball> CHR0N0S: Yes well, you don't have the OS installed to it I assume
[08:56] <hateball> CHR0N0S: It's just to rule things out :)
[08:57] <CHR0N0S> lordievader: I'm not quite certain how to stop this lightdm didn't write that part down I guess?
[08:57] <CHR0N0S> hateball: ok will try that and see what happens
[08:58] <CHR0N0S> waiting for reboot now
[08:58] <lordievader> CHR0N0S: sudo service lightdm stop
[09:01] <CHR0N0S> lordievader: from terminal or tty1?
[09:02] <lordievader> CHR0N0S: tty
[09:03] <lordievader> CHR0N0S: It turns off your gui ;)
[09:04] <CHR0N0S> lordievader: o.i.c...
[09:07] <CHR0N0S> still hanging at usual point...:(
[09:08] <lordievader> CHR0N0S: Now I'm starting to agree that the problem may lie else where.
[09:09] <CHR0N0S> lordievader: hateball: now on the screen it says Kubuntu 14.04 ....[   407.431608] reboot: Power downal   15, shutting down...
[09:10] <CHR0N0S> but just sitting there doing nothing
[09:10] <lordievader> CHR0N0S: Would it be an acpi problem?
[09:11] <lordievader> CHR0N0S: https://wiki.ubuntu.com/DebuggingACPI
[09:11] <CHR0N0S> oh and b.t.w. I did disconnect the external drive as hateball suggested!
[09:11] <CHR0N0S> lordievader: not sure?
[09:12] <CHR0N0S> lordievader: hateball: really appreciate all the help you guys are giving me.
[09:13] <CHR0N0S> lordievader: will goto website on desktop as soon as it finishes rebooting.
[09:15] <CHR0N0S> on the website now will read and get back to you!
[09:23] <CHR0N0S> lordievader: hateball: here is a pastie I did of dmidecode pastebin.com/CpH1Jf93
[09:25] <CHR0N0S> figuring this out is going to be a real pain in the arse...:D
[09:26] <CHR0N0S> I need a cigarette...
[09:26] <hateball> that paste is awful
[09:26] <hateball> :|
[09:26] <CHR0N0S> sorry?
[09:26] <hateball> Well, it's horrible to read :)
[09:27] <hateball> no linebreaks etc
[09:27] <lordievader> CHR0N0S: Please install pastebinit, and run your command again appending "|pastebinit".
[09:28] <CHR0N0S> lordievader: okay? how to do that?
[09:28] <hateball> CHR0N0S: You could try booting with the acpi=off option
[09:28] <hateball> CHR0N0S: "sudo apt-get install pastebinit && sudo dmidecode|pastebinit"
[09:28] <lordievader> ^ that ;)
[09:30] <CHR0N0S> lordievader: hateball: does this need to be on the machine I am working on or on my laptop that I am using to talk to you on?
[09:30] <hateball> CHR0N0S: on the machine where you  have the issue
[09:31] <CHR0N0S> hateball: ok thanks
[09:31] <hateball> I would try editing grub when you boot and append "acpi=off" to the bootline tho
[09:32] <CHR0N0S> hateball: one more question on that subject do I need to do both commands at once or one at a time?
[09:34] <CHR0N0S> hateball: what does it mean http://paste.ubuntu.com/7968833/?
[09:37] <hateball> CHR0N0S: it just lists all the hardware, the motherboard being most interesting. googling DG33BU gives some stuff
[09:37] <hateball> CHR0N0S: googling suggests others have issues with acpi on it, so that's why you could try booting with acpi=off
[09:38] <CHR0N0S> hateball: o.i.c. I figured it out I know the motherboard has reached end of life as far as tech support from Intel goes...
[09:38] <CHR0N0S> hateball: can you please tell me how to do this ?
[09:40] <hateball> CHR0N0S: Editing grub on boot is quite easy, you hold down shift when you boot and you get to the grub menu. then press 'e' to edit the entry used to boot, "linux-something-or-other" and put acpi=off at the end of the bootline
[09:40] <hateball> CHR0N0S: you said the same thing happens on liveboot right? you can press F6 when you boot and choose acpi=off there right away, if you dont feel comfortable with editing the above
[09:41] <CHR0N0S> hateball: yes quite correct I did say that earlier, you are right!
[09:42] <CHR0N0S> hateball: is the pastebin thing a one time thing or can I use it anytime if so how?
[09:43] <hateball> CHR0N0S: you can use it any time, just do "$command|pastebinit" and it will create a new one
[09:43] <hateball> for instance "echo HELLO WORLD|pastebinit"
[09:45] <CHR0N0S> hateball: kewl thanks!
[09:52] <CHR0N0S> hateball: how would I do paste of existing document from system?
[09:55] <hateball> CHR0N0S: what sort of document?
[09:55] <hateball> if it's a plain textfile you could just "cat file.txt|pastebinit"
[09:56] <CHR0N0S> hateball:  I saved a copy of system specs in kate to the hard drive for future refferences
[10:00] <CHR0N0S> hateball: not working, got errors when I tried to do it, don't think it actually has an extension such as .txt, just a filename...
[10:01] <hateball> CHR0N0S: just cat the file then
[10:01] <hateball> !tab
[10:03] <CHR0N0S> hateball: in terminal it keeps telling me No such file or directory...?
[10:05] <CHR0N0S> anyways back to issue at hand gooing to try the reboot thing and use F6 method...
[10:07] <CHR0N0S> here's paste of full system specs in case you're wondering...paste.ubuntu.com/7969057
[10:10] <CHR0N0S> hateball: F6 thing didn't work....?
[10:11] <CHR0N0S> hateball: I mean it booted straight into O.S. no pass go no collect $200.00 dollars....:(
[10:12] <CHR0N0S> hateball: OH wait I forgot a step...:S
[10:17] <CHR0N0S> hateball: nevermind neither way works cannot access that screen no matter what...
[10:17] <CHR0N0S> hateball: is there someother way I might do the editing?
[10:29] <hateball> CHR0N0S: F6 works on the liveboot, not when installed
[10:29] <hateball> CHR0N0S: see holding shift ^
[10:30] <CHR0N0S> hateball: yes I figured out the holding shift part after I tried the F6 method first....
[10:31] <CHR0N0S> hateball: neither method works it will not let me access the grub menu, it just boots straight into the O.S.
[10:33] <CHR0N0S> hateball: In my system bios I have an ACPI Suspend State with the options of S1 State or S3 State but as I have already changed them back and forth and tried to do normal shutdown without any luck I don't know if it pertains to the problem at hand?
[10:33] <hateball> CHR0N0S: well what we want to do is disable ACPI entirely
[10:34] <hateball> and editing grub on boot is a nice way, since it's not permanent
[10:34] <hateball> CHR0N0S: anyhow, do you have the liveboot handy? you may as well just try that (F6)
[10:34] <CHR0N0S> hateball: trying the reboot holding shift key again now...
[10:36] <CHR0N0S> holding shift while rebooting does nothing the machine just ignores the key and continues to boot normally...
[10:36] <CHR0N0S> wait a minute
[10:36] <CHR0N0S> finally
[10:36] <CHR0N0S> at grub menu now
[10:36] <CHR0N0S> already pressed e
[10:37] <hateball> you should have a line starting with linux
[10:37] <hateball> probably ends with "quiet splash"
[10:37] <hateball> so at the end of that, type "acpi=off" without the ""
[10:38] <hateball> then press.... b, is it? to continue boot
[10:40] <CHR0N0S> hateball: linux   /boot/vmlinuz-3.13.0-32-generic root=UUID=79bd802b-4da5-4165-9ab8-67f8897c3bec ro quite splash $vt_handoff
[10:40] <hateball> CHR0N0S: yes, just append acpi=off at the end of that line
[10:42] <CHR0N0S> hateball: waiting
[10:42] <hateball> CHR0N0S: for what? :p
[10:43] <CHR0N0S> hateball: funny! waiting for machine to reboot now...:P
[10:44] <CHR0N0S> arghhhhhhhh
[10:45] <CHR0N0S> anybody got a nerve tablet I think I need one now.............
[10:45] <hateball> CHR0N0S: Why would the machine reboot?
[10:46] <hateball> The whole point was to add acpi=off, then continue booting as usual, and try a shutdown
[10:46] <CHR0N0S> hateball: did and done no luck
[10:46] <hateball> blah
[10:47] <CHR0N0S> stubborn honery machine..........
[10:48] <hateball> CHR0N0S: is it running the latest bios
[10:49] <CHR0N0S> hateball: as far as I know it is running the most recent one that Intel offered for the motherboard...
[10:50] <hateball> very well, then I am running out of ideas
[10:50] <lordievader> CHR0N0S: Are you running Trusty (14.04)?
[10:51] <CHR0N0S> lordievader: please tell me how to find out?
[10:51] <lordievader> CHR0N0S: lsb_release -a |pastebinti
[10:51] <lordievader> CHR0N0S: lsb_release -a |pastebinit
[10:53] <CHR0N0S> lordievader: http://paste.ubuntu.com/7969379
[10:54] <lordievader> CHR0N0S: Jup you are running Trusty. I'm interested to see if Precise has the issue too. Could you perhaps download a Precise live-cd and see if the problem is there too?
[10:54] <BluesKaj> 'Morning folks
[10:54] <lordievader> CHR0N0S: A live session should suffice.
[10:55] <CHR0N0S> hateball: lordievader: when I did the pastie in terminal it showed also the message...No LSB modules are available.
[10:55] <hateball> yes thats alright
[10:55] <CHR0N0S> morning BluesKaj
[10:56] <hateball> all googling I do suggests it's an acpi issue
[10:56] <BluesKaj> Hi CHR0N0S
[10:56] <hateball> CHR0N0S: could you boot again, appending acpi=off, then run "cat /proc/cmdline|pastebinit" just to make sure you were actually booting that
[10:56] <CHR0N0S> BluesKaj: Yes I'm back in here bugging the good folks of the realm again!
[10:57] <hateball> CHR0N0S: you can run "cat /proc/cmdline" now just to see what it does :p
[10:57] <CHR0N0S> hateball: I've tried doing the reboot thing holding shift but it's being very stubborn
[10:58] <hateball> sometimes it is, doesnt help that the grub timeout is set to 0 by default
[10:59] <CHR0N0S> lordievader: hateball: http://paste.ubuntu.com/7969414
[11:00] <BluesKaj> CHR0N0S, holding left shift right after the uefi/bios page?
[11:00] <lordievader> CHR0N0S: Are you sure you entered the kernel parameter correctly?
[11:01] <CHR0N0S> BluesKaj: tried doing it with both, now doing left
[11:01] <CHR0N0S> lordievader: pretty darn sure but not 100%
[11:02] <CHR0N0S> about ready to throw the darned thing out to rubbish pile...
[11:03] <hateball> From experience that tends to not solve the problem ;)
[11:03] <CHR0N0S> hateball: no doubt but might save the last nerve I been hanging onto for the past 20 or so years....
[11:05] <hateball> CHR0N0S: just to be clear, you press e to edit, then append acpi=off to the line starting with linux, then press ctrl-x (or F10)
[11:05] <hateball> no enter presses or any such
[11:06] <hateball> we can edit this in a permanent way from inside the OS, but it's not so nice if it breaks things entirel
[11:06] <CHR0N0S> hateball: just pressed e to edit then edited then ctrl-x to exit
[11:06] <BluesKaj> CHR0N0S, just to catch up here, are you on 12.04 LTS live-media?
[11:06] <CHR0N0S> BluesKaj: No!1
[11:07] <CHR0N0S> BluesKaj: at least not on the machine that is having the problem anyways....
[11:07] <BluesKaj> ok
[11:07] <hateball> CHR0N0S: well, could you just try booting on the livemedia and pressing F6 there?
[11:07] <hateball> it allows for easier adding of those options
[11:08] <CHR0N0S> hehe
[11:08] <CHR0N0S> in the middle of trying that now
[11:10] <CHR0N0S> ok what do I do now got a menu popped up with those options?
[11:10] <hateball> yes, press enter on the option
[11:11] <hateball> it should add to the bootline
[11:12] <CHR0N0S> which option do I choose there are several, noapic, acpi=off, edd=on, nodmraid, nomodeset, and Free software only...?
[11:12] <hateball> just go with acpi=off for now
[11:13]  * BluesKaj wonders if nomodeset is still effective
[11:14] <CHR0N0S> hateball: it's not adding anything as far as I can tell?
[11:15] <hateball> it's supposed to get a checkmark next to it iirc
[11:15] <hateball> dunno if I have some boot media here...
[11:16] <CHR0N0S> hateball: when I manually added it, and pressed enter the machine started doing Memtest86+
[11:22] <CHR0N0S> hateball: when I press enter on that option it places an x by the option but I can't seem to get it to do anything else from there?
[11:24] <CHR0N0S> hateball: there is also an additional option that is here now that wasn't present the first time, it's nolapic...
[11:29] <BluesKaj> CHR0N0S, is there an OS on the machine that won't boot ...I'm not clear on your situation, or are you still trying to install?
[11:29] <hateball> BluesKaj: machine wont shutdown, works otherwise
[11:29] <hateball> so trying to rule out ACPI
[11:29] <BluesKaj> aha
[11:29] <hateball> CHR0N0S: you can press F6 to get the menu, then ESC, and add the options yourself, then press ENTER to boot
[11:31] <BluesKaj> I had the same problem and was shutting down from the VT/TTY , then after an upgrade the problem disappeared, but that was on 14.10
[11:32] <CHR0N0S> BluesKaj: I have fresh install of Kubuntu 14.04 x86
[11:34] <CHR0N0S> hateball: http://paste.ubuntu.com/7969617
[11:34] <BluesKaj> x86 , so 32bit, must be an older pc
[11:35] <CHR0N0S> actually it's a core2quad but hate running a 64-bit os with only 4GB system RAM
[11:35] <hateball> CHR0N0S: yes, boot with that, then check with "cat /proc/cmdline" that it actually booted it
[11:35] <hateball> If you have >2GB there's no reason to not run x64
[11:36] <BluesKaj> CHR0N0S, at lot of apps run better with 64 bit nowadays
[11:37] <BluesKaj> the 32 bit problem is mostly solved by now , altho there area few games still haning on to 32bit
[11:37] <CHR0N0S> hateball: BluesKaj: well actually there is a reason besides that, I play Diablo 3 and getting bit to run on any version of linux is a feat in itself but I have read that there are particuliar issues with running it under a 64-bit linux...
[11:38] <hateball> mhm, I don't see why that should matter, you'll still be running 32-bit wine
[11:38] <hateball> anyhow. it doesnt matter for your shutdown issues
[11:38] <BluesKaj> yup
[11:38] <CHR0N0S> yup
[11:39] <CHR0N0S> did boot with that and it is there that's the pastie I sent last to show you what it vsaid
[11:39] <hateball> ah!
[11:39] <hateball> CHR0N0S: so, does shutting down work?
[11:39] <CHR0N0S> lmao don't know haven't tried it yet been busy typing in here...:P
[11:40] <hateball> multitasking ;p
[11:40] <hateball> I'm at work, been writing emails and doing remote support while typing here ;D
[11:41] <CHR0N0S> hateball: Not for me, there's no such thing, got a one tracked mind and it's been derailed for years...lol
[11:43] <CHR0N0S> hateball: wished I could do pastie from the point it's now at...bunch of BS on screen last thing says something like *Stopping  early crypto disks...
[11:43] <hateball> CHR0N0S: are you booting from CD or USB?
[11:43] <hateball> sometimes it halts waiting for an enter press iirc
[11:43] <hateball> without stating so
[11:43] <CHR0N0S> actually booting from bootable flash drive
[11:44] <CHR0N0S> tried enter no satisfaction still
[11:44] <hateball> well, boo
[11:45] <CHR0N0S> have to do an updraft treatment be back shortly
[11:45] <BluesKaj> I still think you should be running a 64bit OS, and there's no reason not to run 32 bit on a 64 bit install
[11:46] <hateball> CHR0N0S: We could try adding the options to your permanent install, it *shouldnt* break anything
[11:46] <CHR0N0S> see above^
[11:52] <CHR0N0S> hateball: okay back now, sorry but holding a nebulizer to your mouth and typing at the same timme are very difficult to do.
[11:54] <hateball> CHR0N0S: I don't know what that is, but could you boot into your disk install now?
[11:55] <CHR0N0S> hateball: sorry it's part of my updraft machine that I use to take breathing treatments with, I have severe asthma and emphysema...
[11:57] <CHR0N0S> hateball: I've rebooted from the hard disk drive now!
[11:57] <hateball> CHR0N0S: Very well, run "sudo kate /etc/default/grub" and find the line GRUB_CMDLINE_LINUX_DEFAULT=
[11:58] <hateball> it probably has "quiet splash" right now
[11:58] <hateball> so you add acpi=off in there as well, then save the file
[11:58] <hateball> after that, you run "sudo update-grub" and it will generate a new config
[11:58] <hateball> Then... reboot, and see how things work
[11:59] <CHR0N0S> hateball:  strange but in terminal I got all kinds of error messages but it opened kate anyways?
[12:00] <hateball> yes, dont worry about those
[12:00] <hateball> I suppose the proper way is "kdesudo kate"
[12:03] <CHR0N0S> hateball: at present the line states GRUB_CMDLINE_DEFAULT="quite splash" do you want me to add "acpi=off" at the end or edit line to include "acpi=off" as such "quite splash acpi=off"?
[12:04] <hateball> CHR0N0S: the latter
[12:04] <hateball> so it's all between the same ""
[12:06] <CHR0N0S> hateball: not so slow as all that I figured out what you meant from you saying the latter!
[12:07] <hateball> best to make sure :)
[12:08] <CHR0N0S> hateball: have to let it restart to make changes become effective then will try to do shutdown correct?
[12:08] <hateball> CHR0N0S: Yep
[12:08] <hateball> CHR0N0S: and be sure to check with "cat /proc/cmdline" that it booted with acpi=off this time
[12:09] <CHR0N0S> hateball: panel bar going nuts after reboot?
[12:10] <hateball> CHR0N0S: that... shouldnt happen
[12:11] <CHR0N0S> hateball: clock is all screwwy the time and date are all mixed together?
[12:11] <hateball> :|
[12:11] <hateball> I don't see how turning off acpi should make weird stuff happen
[12:11] <hateball> gotta reboot myself, brb
[12:12] <CHR0N0S> ???
[12:12] <CHR0N0S> okay
[12:14] <hateball> CHR0N0S: acpi=off is a kernel option, it shouldnt do anything to KDE
[12:14] <CHR0N0S> hateball: http://paste.ubuntu.com/7969913
[12:15] <hateball> CHR0N0S: Did you try shutting down yet?
[12:15] <CHR0N0S> hateball: just now still hanging in usual spot!
[12:16] <hateball> ugh :(
[12:16] <hateball> CHR0N0S: well, then I guess you can revert the changes to grub
[12:16] <hateball> See if that makes the clock not "screwy" also
[12:18] <CHR0N0S> hateball: I'm beginning to think it isn't meant for me to run Kubuntu or any other x86 linux on this machine, I had the same issue under LM17x86 also...
[12:20] <CHR0N0S> hateball: last two lines on screen before it hangs are *All processes ended within 1 seconds ...   [ok] nm-dispatcher.action: Disconnected from the system bus, exiting.
[12:22] <hateball> CHR0N0S: you could always try a 64-bit liveboot
[12:23] <CHR0N0S> yesterday while trying to resolve same issue due to a message on the screen when it hangs, I removed modemmanager, that of course had no effect either.
[12:23] <CHR0N0S> can I make with startup disc creator from inside a 32-bit os?
[12:25] <CHR0N0S> that was really when I noticed strange issue with clock and panel bar...
[12:25] <hateball> CHR0N0S: yes that should be possible
[12:26] <CHR0N0S> hateball: I'll reboot and try but will have to hook back up my external drive as that is where I have the .iso for it saved...
[12:26] <BluesKaj> CHR0N0S, don't try the regular shutdown gui , just drop to a vt/tty,  ctl+alt+f1-f6 then login and after the pw, sudo powerdown, or sudo halt at the prompt
[12:27] <hateball> well all of that works, but he wants to do it in gui
[12:27] <CHR0N0S> BluesKaj: I've been doing the shutdown gui
[12:28] <BluesKaj> well, as aworkaround until you canfind the solution, which seems to be hardware related IMO
[12:29] <CHR0N0S> hateball: and no even when I do the vt/tty it will still hang unless I give the -r option...
[12:29] <hateball> CHR0N0S: ah, right
[12:29] <hateball> well, as long as you have an x64 iso I'd try that one
[12:30] <CHR0N0S> hateball: but that will only cause it to do reboot...
[12:30] <hateball> seeing as the issue is the same live or not, it should be quite fast to try
[12:30] <hateball> really you shouldnt be using 32-bit anyhow ;p
[12:31] <CHR0N0S> going to be afk for a bit have to hook back up external drive and do iso
[12:33] <CHR0N0S> not quite so fast to try in this case...:P
[12:33] <hateball> CHR0N0S: also as for diablo3, seems to be not much of a problem according to http://appdb.winehq.org/objectManager.php?sClass=version&iId=25953
[12:36] <CHR0N0S> hateball:lmao  when you're a newbie such as myself to linux all is a problem you have to stop and think about one fact I grew up using microshaft winblows...
[12:37] <hateball> oh well
[12:38] <CHR0N0S> hateball: well hellsbells now startup disc creator not wanting to run....:(
[12:39] <CHR0N0S> hateball: not had this problem before
[12:39] <hateball> CHR0N0S: is it spitting out any errors?
[12:40] <CHR0N0S> hateball: big long ones!
[12:40] <CHR0N0S> and they are in a pop up window I can't cut and paste from either
[12:41] <hateball> CHR0N0S: if you run this in a terminal "/usr/bin/python3 /usr/bin/usb-creator-kde" what happens?
[12:41] <CHR0N0S> hateball: hang on will try
[12:42] <CHR0N0S> hateball: short answer it says Not a directory...
[12:43] <CHR0N0S> hateball: should I have did sudo first?
[12:43] <hateball> CHR0N0S: nope
[12:44] <hateball> I wonder if any permissions got screwed when we ran "sudo kate" earlier...
[12:44] <CHR0N0S> hateball: unsure
[12:44] <hateball> CHR0N0S: Alright, in a terminal, can you run "find ./ -user root"
[12:45] <hateball> It should list any files in your homedirectory owned by root
[12:45] <CHR0N0S> haven't reverted any changes done to system either yet!
[12:45] <lordievader> CHR0N0S: You say you didn't have it before, to what where you refering?
[12:45] <hateball> that should be ~/ and not ./, just to make sure...
[12:46] <lordievader> Ah, the startup disc creator not running, nvm...
[12:46] <CHR0N0S> hateball: typed find./-user root reply bash: find./-user: No such file or directory
[12:47] <hateball> CHR0N0S: you're missing spaces
[12:47] <CHR0N0S> hateball: ?oh
[12:48] <CHR0N0S> hateball: maybe because eyeballs keep trying to shut, no spring chicken here anymore lol
[12:48] <hateball> :)
[12:49] <CHR0N0S> hateball: should be typed find ./-user root?
[12:50] <hateball> CHR0N0S: still missing a space between ./ and -user
[12:50] <CHR0N0S> OKAY!
[12:51] <CHR0N0S> hateball: ./ .kde/share/apps/RecentDocuments/grub.desktop
[12:51] <hateball> CHR0N0S: hopefully it doesnt return anything when it's done
[12:51] <CHR0N0S> ooooooooooop's
[12:52] <CHR0N0S> hateball: see above^ was what it returned
[12:53] <CHR0N0S> going after another glass of tea brb!
[12:53] <hateball> CHR0N0S: just to be sure, do "find ~/ -user root" instead
[12:57] <CHR0N0S> hateball: /home/rodney/ .kde/share/apps/RecentDocuments/grub.desktop
[12:57] <hateball> CHR0N0S: alright, if you do "ls -ld ~/" does that say "rodney rodney" or is there something about root in there?
[12:57] <CHR0N0S> as best as I can see that's what it says
[12:58] <CHR0N0S> ls-ld ~/ ?
[12:58] <hateball> CHR0N0S: space between ls -ld
[13:00] <CHR0N0S> hateball: drwxr -xr -x 22 rodney rodney 4096 Aug 6 07:33 /home/rodney/
[13:02] <hateball> CHR0N0S: alright, that looks good
[13:02] <CHR0N0S> hateball: can you believe I've been a computer tech for over 20 yrs now but always used microshaft winblows...
[13:02] <hateball> :)
[13:03] <CHR0N0S> hateball: I feel like a complete newborn idiot
[13:03] <hateball> CHR0N0S: anyhow, you could run "kdesudo kate /etc/default/grub" and revert those changes
[13:03] <hateball> remember to run "sudo update-grub" aftwards
[13:04] <hateball> Since nothing in your ~/ seems to have weird permissions I dunno why stuff dont work proper
[13:04] <CHR0N0S> hateball: you are referring to the acpi=off thingy?
[13:06] <hateball> CHR0N0S: yes
[13:06] <CHR0N0S> hateball: still getting those wierd errors in terminal...
[13:06] <CHR0N0S> hateball: changes done
[13:07] <CHR0N0S> should I by any chance reinstall modemmanager?
[13:08] <hateball> CHR0N0S: if you mean something like "IBusInputContext::createInputContext: no connection to ibus-daemon" thats nothing to worry about
[13:09] <hateball> CHR0N0S: does running "kdesudo /usr/bin/usb-creator-kde" work?
[13:10] <CHR0N0S> hateball: to tell you for sure I'd have to rerun previous commands to give exact output but that was only one amongst many such errors
[13:15] <CHR0N0S> hateball: couldn't create image from ""   Could not resolve property : linearGradient5167   Bus::open Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon
[13:15] <hateball> CHR0N0S: does the app start at all?
[13:15] <CHR0N0S> hateball: no
[13:15] <hateball> :|
[13:16] <CHR0N0S> hateball: oh wait :S
[13:16] <CHR0N0S> hateball: app started after I put in password...
[13:16] <hateball> well then
[13:17] <hateball> go forth and create a 64-bit usb stick
[13:18] <CHR0N0S> it's saying the device needs to be formatted for use?
[13:19] <CHR0N0S> hateball: now same error as before and I hope you will not want me to type it all in as it is rather a long beastie...
[13:19] <hateball> the USB stick will need to reformatted yes
[13:19] <hateball> I'm not really sure but something seems proper messed up on that machine
[13:19] <CHR0N0S> I tried the erase function in startup disc creator but that's when I get the error
[13:20] <hateball> I don't suppose you have access to another machine to make a bootable USB on?
[13:21] <CHR0N0S> this machine but it's booted from a live disc now as it has Winblows 7 installed on the hard drive and no IRC client installed under Winblows...:(
[13:22] <CHR0N0S> hateball: gonna try something brb
[13:23] <hateball> CHR0N0S: well, quassel runs on windows as well. and you can follow these instructions https://help.ubuntu.com/community/BurningIsoHowto
[13:28] <CHR0N0S> might as well go find it to download for winblows be right back
[13:28] <Naphatul> how can i make kate open a new window when i open a new text file?
[13:30] <CHR0N0S> hateball: in case I don't make it back soon enough or you decide to leave, really my thanks to you and the others for all the help, yoou've been more than kind and I truly appreciate it!
[13:30] <hateball> CHR0N0S: Well I'm leaving work soon but I'm usually around... good luck :)
[13:31] <CHR0N0S> hateball: thanks again
[13:34] <hateball> Naphatul: do you open files by clicking on them in a gui?
[13:35] <Naphatul> hateball: usually via dolphin
[13:36] <hateball> Naphatul: "kate -n" will start a new session every time, so you could rightclick a textfile and edit properties...
[13:36] <hateball> then "options for filetype" (?) not on english locale so
[13:37] <hateball> it should list the apps available to open, kate should be on top if it is default I guess. you can edit that and change the  command to include -n
[13:39] <Naphatul> hateball: it's currently "kate -b " what does the -b do should i replace it or just add -n?
[13:40] <hateball> Naphatul: just add -n
[13:41] <Naphatul> hateball: apparently i don't have access to write to ~/.kde/something
[13:42] <hateball> hmmm
[13:42] <hateball> well there are various ways to do this, not sure which one is the "best"
[13:44] <hateball> Naphatul: What I would do, and what is probably unsupported and gets overwritten on upgrades etc, is "kdesudo kate /usr/share/applications/kde4/kate.desktop"
[13:44] <hateball> Naphatul: at the bottom you have a line Exec=
[13:44] <hateball> add the -n, save file, and it should behave as expected after that
[13:45] <Naphatul> hateball: apparently the file dialog is attempting to change /home/user/apllications/kde4/kate.desktop
[13:45] <Naphatul> which doesn't exist
[13:45] <Naphatul> as opposed to the /usr/share version
[13:45] <Naphatul> bug?
[13:45] <Guest19882> can i do a do a text interface install of kubuntu
[13:46] <Guest19882> like for if i want certain nonstandard features
[13:46] <hateball> !minimal
[13:47] <shadeslayer> Guest19882: you'll have to go through the minimal cd route
[13:47] <Guest19882> it is ubuntu with no desktop environment?
[13:56] <BadBIOS> hey
[14:09] <David1965> EyeR you there my friend
[14:31] <BadBIOS> :bprompt heyyy
[14:34] <BluesKaj> BadBIOS, if you have a question, just ask ... look in nicklist to find other users
[14:57] <me> hello
[14:58] <Guest79191> I am using rekong. I tried to load a dumnet using writer, but writer got stock. Works fine alone. Is there some incompatibility between writer and rekonq
[15:00] <Guest79191> using version 12 kubuntu on livecd
[15:46] <hrtuuop> hello
[15:47] <hrtuuop> have a problem with kbuildsycoca4
[15:49] <hrtuuop> I have about 1200 .desktop files in my applications folder, and KBuildSycoca::createEntry: tries to parse them, but won't finish nor stop..
[16:36] <zaggynl> heya, I'm trying to use the nvidia prop drivers but I seem to stay on nouveau, any tips?
[16:36] <zaggynl> glxinfo | grep -i vendor says: OpenGL vendor string: nouveau
[16:38] <zaggynl> additional driver dialog shows: http://i.imgur.com/QNrGE7X.png
[17:40] <EvilRoey> HI ALL
[17:40] <EvilRoey> question... in Firefox, how can I get a count of open tabs?
[17:40] <TaZeR> hey mick
[17:40] <TaZeR> on your fingers would be fastest
[17:40] <EvilRoey> hey though I'm not Irish I resent that epiphet
[17:41] <TaZeR> theres an addon called tab something that tells you how many are open as one of its features
[17:41] <EvilRoey> ah okay
[17:41] <EvilRoey> I mean the Session Manager plugin tells you how many open tabs, but only for saved sessions
[17:42] <EvilRoey> ah
[17:42] <EvilRoey> from #firefox: EvilRoey: extensions, https://addons.mozilla.org/en-US/firefox/addon/tab-counter/
[18:13] <jubo2> Hiya and thanks for the awesome Window Maker and the awesome Debian GNU/Linux derivative OS
[18:13] <jubo2> I'm on 14.04
[18:13] <jubo2> I
[18:14] <jubo2> I've run 'sudo aptitude update' and 'sudo aptitude upgrade'.. should I do something before running 'sudo aptitude dist-upgrade' ?
[18:14] <lordievader> jubo2: Nope, you can run it without worries.
[18:14] <lordievader> Do look at what it wants to do.
[18:15] <jubo2> 'k
[18:16] <jubo2> last time I run 'dist-upgrade' on any machine I broke a functional Debian6 so a little spooked
[18:16] <lordievader> jubo2: That's why you should also look at what it is going to do ;)
[18:16] <sithlord48> jubo2:  you should not use aptitude with kubuntu. use apt instead
[18:16] <jubo2> well it was still able to boot in single user mode and I could scp over all my relevant files
[18:17] <jubo2> which I didn't need coz I had made backups
[18:17] <sithlord48> iirc aptitude has a poor dependicy resolver that can cause issues with kubunt
[18:17] <jubo2> aptitude has been good for me
[18:18] <jubo2> last time I installed the AMP part of LAMP it was done in a minute or two
[18:18] <sithlord48> jubo2:  do u have broken packages? or just lamp issues?
[18:18] <jubo2> sithlord48: no. everything is fine with the system I'm upgrading
[18:19] <sithlord48> jubo2: distro upgrade?
[18:20] <jubo2> I've the exported personal web identity key and a .tar.gz of the XML dump of the only site in the MySQL of this Kubuntu14.04 running inside of virtualbox
[18:20] <jubo2> there is nothing of value on the system besides those two things that are in the backup servers
[18:21] <sithlord48> ok was gonna say if upgrading to newer version you should use "do-release-upgrade"
[18:21] <jubo2> I'm set..
[18:21] <jubo2> sithlord48: wait.. what?
[18:21] <sithlord48> if you are going from lets say 13.10 to 14.04 using the command do-release-upgrade will do it for your.
[18:21] <jubo2> I've heard said that I should run 'sudo apt dist-upgrade' ?
[18:21] <jubo2> 'tis not correct ?
[18:22] <sithlord48> do-release-upgrade will change your release version . dist-upgrade will install upgrades that require the install of previously not installed packages.
[18:22] <jubo2> huh.. what?
[18:23] <sithlord48> your on 14.04 yes?
[18:23] <jubo2> 'k .. I get message that 'sudo apt do-release-upgrade' is what I want to enter in the shell ?
[18:23] <yofel> dist-upgrade is named "dist"-upgrade because debian uses it like that. In ubuntu we use do-release-upgrade for upgrades to a new ubuntu release
[18:23] <sithlord48> no sudo do-release-upgrade
[18:24] <jubo2> hmm..
[18:24] <sithlord48> -d if going for a devel version (but since 14.04.1 is out you will upgrade to that
[18:24] <jubo2> I do that.
[18:24] <yofel> technically dist-upgrade does the same as upgrade but allows removing packages (which is why it should be used with care)
[18:24] <jubo2> It says "no new rlease found"
[18:25] <jubo2> how do I check for my system version ?
[18:25] <sithlord48> cause your on 14.04 your on the newest release
[18:25] <jubo2> that happened with 'sudo aptitude upgrade' ??
[18:25] <sithlord48> we really don't use aptitiude in kubuntu
[18:26] <sithlord48> to upgrade your packages use sudo apt update then sudo apt upgrade
[18:26] <jubo2> sithlord48: I did that
[18:26] <jubo2> but with aptitude
[18:26] <jubo2> I'm used to aptitude
[18:26] <sithlord48> ok are all your packages not updated?
[18:27] <jubo2> I come from Commiemist GNU/Linux Camp
[18:27] <yofel> aptitude works perfectly fine in most cases, we just recommend apt-get. Just make sure to double-check what 'aptitude full-upgrade' or 'apt-get dist-upgrade' want to do if you use them
[18:28] <yofel> jubo2: 'lsb_release -r' will tell you the release you're running
[18:28] <jubo2> yofel: tnx
[18:29] <yofel> and 14.04 is the lastest, so do-release-upgrade won't find anything newer by default
[18:29] <jubo2> yofel: I'm not undestanding... I thought 14.04 and 14.04.1 are different versions
[18:29] <sithlord48> 14.04.1 is updated iso for 14.04
[18:29] <sithlord48> just contains all the updates since release so you don't need to dl and install as many
[18:29] <jubo2> i c
[18:30] <yofel> right
[18:30] <jubo2> then I'm up-to-date and no errors were reported in update nor upgrade :D :D
[18:30] <sithlord48> then your good :D
[18:31] <sithlord48> for updating i have been using apt upgrade (not apt-get 0) works nicly seams to pull extra depencies when needed so i would suggest using it when possible for your updates.
[18:32] <sithlord48> aptitude will work but just watch what it wants to do . i remember it trashing kubuntu systems . idk if it still has issues or not cause i don't use it
[18:37] <sithlord48> woo hoo i can finally access KFN again..
[18:41] <bprompt> *cough*
[19:05] <colamann_> hello, everyone! does anyone have recommendations on how to save an apparently completely broken kubuntu after a botched upgrade from 13.x to 14.04? the system now hangs very early during the startup process. right now i'm considering a clean install, but if anyone has a better idea, i'm all ears
[19:08] <rberg> colamann: are you able to see anything on the screen that may indicate what the problem is?
[19:09] <rberg> if not I would try setting grub to use gfxmode=text and remove splash and quiet from the kernel commandline in grub
[19:10] <colamann> i get past grub (i can choose between all the remaining installed kernel versions as well as recovery mode) but the problems seems the same with each one of them
[19:12] <colamann> i might add that i got an error message during upgrade (did the gui upgrade - maybe i shouldn't have) telling me that some error occurred that may have left my os non-working. the message wasn't any more specific, though
[19:14] <colamann> there is some output before the system hangs, nothing that seems like an error message to me. i didn't think to write the output down
[19:19] <rberg> I guess I would boot up a cd/usb and chroot into the broken install and run update-grub and grub-install /dev/sd$whatever
[19:20] <colamann> ok, so you think it's a grub problem even though i get a bit past grub??
[19:22] <BluesKaj> colamann, describe "a bit past grub"., what shows?
[19:22] <rberg> the only time I ever noticed a message like "may have left my os non-working." has been grub..  also do 'update-initramfs -u -k all'
[19:23] <rberg> I am leaning toward the initramfs.. but thats just a feeling
[19:27] <colamann> thanks, i'll try that first thing tomorrow (don't have the broken box here right now)
[20:07] <deitarion> Is Ark under 14.04 supposed to not be listed as a handler for RAR archives? If that's a bug, could someone use `dpkg -S` to figure out which package I forgot to pull into my Lubuntu while trying to replace file-roller?
[20:08] <deitarion> ...OK, this HAS to be a bug. It's also experiencing the same issue with Zip files.
[20:14] <bprompt> deitarion:      dunno... but I gather you can always set the MIME of those to ark.. under File associatioons
[20:16] <deitarion> bprompt: That's not all. I also need to figure out why Ark asks me to pick the filetype from an empty list when I double-click a .tar.gz file.
[20:17] <bprompt> hmm
[20:17] <deitarion> Given how many bugs I've had to squash or work around, I'd have stayed on Lubuntu 12.04 if I didn't need a newer glibc for things like dolphin-emu 4.x and GOG.com offerings like Don't Starve.
[20:18] <bprompt> well
[20:18] <deitarion> Well, a newer GCC for dolphin-emu.
[20:18] <bprompt> you can always just compile your own glibc I'd think
[20:20] <deitarion> bprompt: Given how much work I've already put into it, probably better to stay the course and build solutions that won't inevitably break anyway. (eg. Replacing my current "downgrade Geeqie to the Precise packages" solution with a potentially more robust compile-from-source one, finding GTK+ 2.x replacements for everything that switched to those irritating GTK 3.x Open/Save dialogs, etc.)
[20:20] <bprompt> heeheh
[20:21] <bprompt> gtk 3.x themes are css-based  btw, as opposed to gtk 2.x
[20:21] <bprompt> so... they'd be more customizable I'd think... but usually is just code
[20:22] <deitarion> bprompt: While I'm sure it'd be possible to substitute acceptably colorful icons, I doubt the CSS would be powerful enough to rip out the Places/Devices/Bookmarks categorization and go back to a compact list without so many entries I'll never use.
[20:23] <deitarion> Unlike the new Timeline and Search sections in Dolphin, GTK+ file dialogs gray out the Remove options for the new additions.
[20:24] <deitarion> ...and god only knows how much other stuff will break or misbehave if I start removing lines from xdg-user-dirs.dirs and then set it immutable in an attempt to force the GTK+ 3.x dialogs to not show Places that have no use in my filing system.
[20:25] <deitarion> (Luckily, so far, I've only tripped over the GTK+ 3.x dialogs in File Roller and Audacious Media Player and I'm already planning to replace the latter with QMMP to restore the ability to play via an external MIDI device or to automatically flush dead entries from the playlist.)
[20:29] <bprompt> ahem..    one may note qmmp is far smaller than audacious =)   more or less same compact GUI, is also skinnable =)
[20:29]  * bprompt uses qmmp
[20:30] <deitarion> *nod* That's why I'm looking into switching. The Qt UI is almost identical, it's got an MPRIS plugin, which should be enough for me to tie on all my custom UI, and the handful of chiptune formats it doesn't support yet are on the TODO list.
[20:31] <deitarion> Heck, given how much custom UI I've got, it's more that I want a chiptune-compatible alternative to GStreamer with a ready-made playlist editor than anything else.
[20:32] <deitarion> bprompt: Oh, given that I tested it successfully with QMMP's MPRIS plugin, you may find this little utility interesting --> https://github.com/ssokolow/lap
[20:33] <deitarion> It's basically a terminal swiss-army playlist builder.
[20:37] <bprompt> hmm
[20:38] <deitarion> It grew a bit organically, so the commands do behave a little inconsistently (eg. some defaulting to XDG_MUSIC_DIR and some not) but, now that I've almost finished recovering from having my root partition eat itself, I'll get back to cleaning up the innards soon.
[20:40] <deitarion> Anyway, that script, the OSD plugin, some xbindkeys bindings, and the Audacious Jump to File dialog are 99% of how I interact with my media player so I think you can see why the filetype support is the main thing I care about in Audacious and QMMP.
[22:17] <sirellyn> So I just reinstalled this laptop w kubuntu.  Wireless was working before, but not now.
[22:17] <sirellyn> I can see the wireless hotspots too.  I just can't connect or ping them.
[22:19] <sirellyn> I can't even ping my router over wireless.