[00:22] <alesan> hi, is Kubuntu using pulseaudio ???
[00:34] <gannondorf> Saluton kubuntu!
[07:21] <lordievader> Good morning.
[08:13] <soee> good morning
[08:31] <decepary> hey.
[08:34] <decepary> what's up?
[08:56] <MJ2363> hi every1
[08:56] <MJ2363> how can I purge all gnome packages in order to install kde-desktop?
[08:57] <valorie> you need not purge anything to install the kde-desktop, if you don't want to
[08:57] <MJ2363> yes I know...
[08:57] <hateball> !purekde
[08:57] <MJ2363> but I would like to remove gnome for space puroposes
[08:57] <valorie> ok
[08:58] <hateball> note the versions ^
[08:58] <MJ2363> are those for 13.10?
[08:58] <MJ2363> I think thery are a bit outdated :(
[09:13] <skramer_> Hi all. I have a rather stupid question today: How can I force apps that I ran by 'kdesudo ...' to have same look as if I ran them as normal user?
[09:15] <hateball> skramer_: You could set the desktop theme for root I suppose
[09:16] <hateball> assuming they are qt applications
[09:16] <skramer_> Ok. So I should do 'kdesudo systemsttings' and then select same them for window decoration, etc.?
[09:17] <skramer_> Gtk apps will look bit different, anyway. But that´s no problem :)
[09:17] <valorie> skramer_: it's rather dangerous to run stuff as root
[09:21] <skramer_> valorie: I´m quite aware that no program should not be run as root normally. Still, sometimes I need to edit some file  in /etc. So 'kdesudo kate  file' should make me able editing the file, but I want to have kate looking same as if I ran it as my normal user...
[09:21] <valorie> ok, as long as you are aware
[09:21] <skramer_> :)
[11:52] <serj> re
[12:44] <taduro__> sup guys
[12:44] <taduro__> when I log in with my user
[12:44] <taduro__> the screen goes black
[12:44] <taduro__> any ideas? :(
[12:46] <monkeyjuice> what you using taduro__ 13.**?
[12:48] <monkeyjuice> taduro__:  did it work?, what made it stop working?, did you upgrade?, ect
[12:48] <taduro__> 13.10 monkeyjuice
[12:49] <taduro__> monkeyjuice: nothing, I was in class, I switched off my computer
[12:49] <taduro__> and when I arrived at home..
[12:49] <taduro__> surprise
[12:56] <monkeyjuice> been looking for help online taduro__ there are a few bugs it seems , hoping someone else will jump in and help you with this..
[12:57] <taduro__> ok thank you very much monkeyjuice
[13:04] <Linusnewb> hi all
[13:06] <Linusnewb> how do I stop networkmanager or restart it? service network-manager stop does it not
[13:08] <Linusnewb> /etc/init.d/networking stop Error: calling a sysvinit script.... blablabla
[13:15] <Linusnewb> no one any idea?
[13:18] <taduro__> Linusnewb: no, sorry :/
[13:23] <Linusnewb> taduro__ I think I have a plasma-nm tool in 13.10 kubuntu but what applet it is using I don't now gnome utils or kde something in xorg or whatever
[13:24] <alvin> Linusnewb: service networking restart (name changed)
[13:26] <Linusnewb> is there any way to look what is the new name on console
[13:30] <maruf> hayy all how are you....?
[13:34] <BluesKaj> Hi all
[14:19] <Taduro> If I do $ startx > log.txt ← That will save what startx says? because I can log with other accounts (rigth now I'm using that other account) but with my account, when I try to log in, it shows up the kdm(?) splash screen like "loading" but woah, the screen goes entirely black. I tried with another tty, login in with my account and then startx, but it does the same, when it arrives to the "plasma loading screen", the screen goes black
[15:08] <Whiskey`Wonka> yay muon is again forgetting how to work
[15:35] <Bundestrojaner> hello
[15:37] <apachelogger> Taduro: sudo apt-get install kubuntu-desktop ... as for the logs you can find the regular log at ~/.cache/upstart/startkde.log
[15:37] <Taduro> apachelogger: hello! But I'm right now using plasma with another user
[15:37] <Taduro> You want me to install kubuntu-desktop with my normal account?
[15:37] <Bundestrojaner> when i start KGPG, it shows the Name in the bar at the bottom of the screen, for a few seconds, than it dissapears. The program never starts. When i start it from console, i get twice "QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave."
[15:37] <apachelogger> Taduro: sudo apt-get purge kubuntu-settings-active
[15:38] <apachelogger> Bundestrojaner: are you sure it's not simply hiding in the systray?
[15:41] <Bundestrojaner> apachelogger: you're right, thx! I didn't know it stays in tray. and the error message in Konsole confirmed me...
[15:43] <apachelogger> Bundestrojaner: FWIW, I think it should open the window when started manually regardless of whether it is in the tray alraedy; you may want to file a bug at bugs.kde.org
[15:44] <Taduro> apachelogger: can you explain it again, please?
[15:46] <apachelogger> oh wait, that makes even less sense
[15:46] <apachelogger> Taduro: best get that startkde.log
[15:46] <apachelogger> something must be incorrectly configured such that  your plasma-desktop doesn't come up
[15:47] <lordievader> Good afternoon.
[15:56] <Taduro> apachelogger: I sent you the paste
[16:04] <AshishL> i was planning on installing Kubuntu for development on windows using Virtual Machine ... i visited a link . Can anyone tell me if it is appropriate ? http://www.artiss.co.uk/2009/01/running-kubuntu-under-virtualbox
[16:16] <Taduro> apachelogger: there are more logs?
[16:17] <BluesKaj> lordievader, I burned the daily image to dvd yesterday , is that new enough to contain the latest kernel.?
[16:19] <lordievader> BluesKaj: Does the live-env work? uname -a to check.
[16:20] <BluesKaj> lordievader, 3.12.0-5-generic
[16:21] <BluesKaj> used the live dvd to install in vmware
[16:21] <lordievader> BluesKaj: That is a quite recent kernel.
[16:22] <lordievader> BluesKaj: Is also what run on this updated install of Trusty.
[16:22] <lordievader> BluesKaj: But the live env works?
[16:22] <lordievader> The graphics I mean?
[16:22] <apachelogger> Taduro: unregistered nicks cannot query me :P
[16:22] <Taduro> oh
[16:23] <Taduro> apachelogger: http://paste.ubuntu.com/6525345/
[16:25] <apachelogger> hm
[16:26] <apachelogger> Taduro: mv ~/.kde/share/config/ksmserver ~
[16:26] <apachelogger> then try to log in
[16:27] <Taduro> apachelogger: I ahve to leave, I'll come here in a moment!
[16:28] <BluesKaj> lordievader, no live dvd diesn't work by itself , but works fine in vmwareplayer
[16:28] <Whiskey`Wonka> anyone know what to do about muon? "this operation could not continue proper wauthorization was not provided"
[16:30] <Whiskey`Wonka> polkit is isntalled, im not using a remote session. im guessing its a dbus issue?
[16:31] <lordievader> BluesKaj: Ahh, so it really is the hardware.. You cannot get into a tty on the actual machine (not a vm)?
[16:31] <apachelogger> really hard to say
[16:31] <apachelogger> Whiskey`Wonka: tried a restart?
[16:31] <Whiskey`Wonka> apachelogger: i know a restart will fix it but this isnt friggen windows
[16:31] <Whiskey`Wonka> id a solution not a bandaid
[16:31] <Whiskey`Wonka> like*
[16:32] <apachelogger> well
[16:32] <apachelogger> oh actually
[16:32] <apachelogger> Whiskey`Wonka: is qaptworker running?
[16:32] <BluesKaj> lordievader, no tty available
[16:32] <Whiskey`Wonka> ill look
[16:33] <Whiskey`Wonka> oot     18018  0.0  0.0 254884  7208 ?        Sl   06:50   0:00 /usr/bin/qaptworker2
[16:34] <apachelogger> Whiskey`Wonka: cd ~; sudo gdb -p `pidof qaptworker2`  .... once you get a prompt type ... set logging on ... and after that ... thread apply all bt ... and after that .... set logging off ... and after that quit
[16:35] <BluesKaj> lordievader, I also tried 13.10, same result
[16:35] <apachelogger> Whiskey`Wonka: after that you should find a file called gdb.txt in your home, please paste the content
[16:35] <apachelogger> Whiskey`Wonka: and then you can run `sudo killall qaptworker2` and see if that makes muon work again
[16:36] <Whiskey`Wonka> Inferior 1 [process 18018] will be detached.
[16:36] <Whiskey`Wonka> that ok?
[16:36] <apachelogger> yeah
[16:37] <Whiskey`Wonka> mmm, must have done something wrong, no gdb.txt
[16:37] <apachelogger> Whiskey`Wonka: can you paste the output of the terminal session?
[16:39] <Whiskey`Wonka> http://pastebin.com/tfGXGMCE
[16:39] <Whiskey`Wonka> should i still restart qaptworker2?
[16:39] <apachelogger> you forgot set logging on xD
[16:39] <apachelogger> Whiskey`Wonka: yeah
[16:40] <Whiskey`Wonka> i sware i typed it lol
[16:40] <apachelogger> only logging off
[16:40] <apachelogger> anyway, the backtrace is not useful
[16:40] <Whiskey`Wonka> =(
[16:40] <Whiskey`Wonka> worth a try
[16:41] <apachelogger> well, if it fixes the issue it's still only a workaround but I have the strong feeling that qaptworker2 gets stuck and consequently the authentication fails
[16:41] <apachelogger> however it's nigh impossible to find out why it gets stuck
[16:42] <Whiskey`Wonka> thats fun
[16:43] <Whiskey`Wonka> damn this thing is running like crap now
[16:43] <Whiskey`Wonka> and its still not asking for perms
[16:43] <apachelogger> Whiskey`Wonka: killall polkit-kde-authentication-agent-1
[16:44] <apachelogger> start it again via `/usr/lib/kde4/libexec/polkit-kde-authentication-agent-1`
[16:44] <apachelogger> does that help?
[16:44] <Whiskey`Wonka> ah! there is no polkit-kde-authentication-agent-1 running
[16:44] <Whiskey`Wonka> only polkit listed is root       944  0.0  0.0 272308  4280 ?        Sl   Dec03   0:01 /usr/lib/policykit-1/polkitd --no-debug
[16:45] <apachelogger> that would explain it then
[16:45] <apachelogger> curious that it would explode
[16:45] <apachelogger> or maybe it was not started
[16:45] <Whiskey`Wonka> not sure why it wouldnt start, it handles the wallet too doesnt it?
[16:46] <Whiskey`Wonka> or i should ask, what handled kde wallet and the new wifi manager keys ?
[16:46] <apachelogger> wallet is independent of polkit
[16:46] <apachelogger> polkit expands permissions beyond the user settings
[16:47] <apachelogger> the wallet is user specific though
[16:47] <Whiskey`Wonka> http://pastebin.com/b4PTm8NF
[16:47] <apachelogger> unamed app is funny xD
[16:47] <apachelogger> Whiskey`Wonka: does it work now?
[16:48] <Taduro> apachelogger: I'm back, do you know how to get the message from the konsole in english? for the errore message I'm getting..
[16:48] <Whiskey`Wonka> ill try but it looks like /usr/lib/kde4/libexec/polkit-kde-authentication-agent-1 did not run
[16:48] <apachelogger> Taduro: LANG=C before the command you want to have in english
[16:48] <apachelogger> e.g. LANG=C kde4-config --help
[16:49] <Taduro> apachelogger: awesome
[16:49] <Taduro> apachelogger: mv: cannot stat '/home/soul/.kde/share/config/ksmserver': No such file or directory
[16:49] <apachelogger> ohm
[16:50] <Whiskey`Wonka> Still no password dialog for muon updater (and likely not for muon)
[16:50] <Whiskey`Wonka> holy crap its 9 already =\
[16:50] <apachelogger> Taduro: ls -l ~/.kde/share/config |grep "^d"
[16:50] <Whiskey`Wonka> and still -5 outside, screw working
[16:51] <apachelogger> ^^
[16:52] <Taduro> apachelogger: http://paste.ubuntu.com/6525589/
[16:52] <Whiskey`Wonka> lucky for me its a light load today and I can wait till later
[16:52] <apachelogger> Whiskey`Wonka: maybe try `dbus-monitor` and in another terminal `dbus-monitor --system` and then try to get authorization
[16:52] <apachelogger> however I find it unlikely that this will yield any information
[16:52] <apachelogger> Taduro: mv ~/.kde/share/config/session ~
[16:53] <apachelogger> then try to login
[16:53] <Whiskey`Wonka> dbus-monitor Failed to open connection to session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[16:53] <Whiskey`Wonka> that was su, should i run as my user?
[16:53] <apachelogger> yeah, your user
[16:54] <Whiskey`Wonka> LOTS of info but no idea what it all means
[16:55] <Whiskey`Wonka> signal sender=:1.152 -> dest=(null destination) serial=48 path=/org/kubuntu/qaptworker/transaction2450b95d1c294f2a9853667382533c94; interface=org.kubuntu.qaptworker2.transaction; member=propertyChanged
[16:55] <apachelogger> ah, yeah, restart them, and try to do as little as possible between starting the application and trying to get authorization, then immediately after the error ctrl-c the monitors again
[16:55] <apachelogger> and paste all the output
[16:56] <Whiskey`Wonka> oh boy
[16:56] <Whiskey`Wonka> that mens shuttign down lots of apps, mmm
[16:56] <apachelogger> Whiskey`Wonka: nah
[16:56] <apachelogger> Whiskey`Wonka: just don't go into them
[16:56] <apachelogger> they shouldn't create much output while idle
[16:57] <apachelogger> but as soon as you switch into an application a wall of spew appears :P
[16:58] <Whiskey`Wonka> hmmm
[16:58] <Whiskey`Wonka> ok so should i have muon updater running already? cause launching it spews
[16:59] <Taduro> apachelogger: I have to reboot? because i get the same
[16:59] <Whiskey`Wonka> but i only get 1 shot at trying for the password, after it, it doesnt give the error, it just doesnt do anything
[16:59] <apachelogger> Taduro: new log please
[17:00] <apachelogger> (I am just guessing here :P)
[17:00] <apachelogger> Taduro: oh, actually ... run `echo "DisableAll=false" >> ~/.kde/share/config/kdebugrc` and try to log in again
[17:01] <apachelogger> that should create a more verbose log
[17:01] <apachelogger> Whiskey`Wonka: oh, so you get a password dialog?
[17:01] <Whiskey`Wonka> no
[17:01] <apachelogger> Whiskey`Wonka: update can be running already
[17:01] <Whiskey`Wonka> when i press 'install updates' it churns for a sec thn goes directly to the error
[17:01] <apachelogger> authorization is requested on-demand
[17:02] <Whiskey`Wonka> ok
[17:02] <Whiskey`Wonka> and once i do THAT, it doesnt error till i restart updater
[17:03] <apachelogger> Whiskey`Wonka: huh
[17:03] <apachelogger> Whiskey`Wonka: if you start updater, then the monitors, and then try to install the updates it doesn't error at all?
[17:03] <Whiskey`Wonka> yes
[17:03] <Taduro> apachelogger: http://paste.ubuntu.com/6525638/
[17:07] <Whiskey`Wonka> http://pastebin.com/6QYV2Jct
[17:08] <Whiskey`Wonka> http://pastebin.com/Mr0HKzyg
[17:08] <apachelogger> Taduro: all those errors from psi do not make me very confident
[17:08] <Whiskey`Wonka> thats dbus-monitor and --system respectivly
[17:08] <apachelogger> Taduro: have you manually put psi and quassel on autostart?
[17:08] <Taduro> hmmm, manually I don't remember but they start automatically always, apachelogger .
[17:09] <apachelogger> Taduro: check ~/.config/autostart ~/.kde/share/autostart
[17:09] <apachelogger> Taduro: if there's stuff in there move it out and try a log in again
[17:10] <Taduro> ok apachelogger
[17:11] <apachelogger> Whiskey`Wonka: yeah, no viable information
[17:11] <Whiskey`Wonka> seams to be the story of the day
[17:13] <apachelogger> it's just really bad stuff to debug as the entire process so utterly opaque it makes you wanna cry
[17:14] <Whiskey`Wonka> yes it is
[17:14] <Taduro> apachelogger: I think I have to reboot because now I get the same I thing? http://paste.ubuntu.com/6525683/
[17:14] <Whiskey`Wonka> i do networking tech support over the phone, its highly anoying
[17:14] <apachelogger> ehm
[17:15] <apachelogger> Taduro: you did all that stuff in the user with the broken plasma, right?
[17:15] <Whiskey`Wonka> im infectious!
[17:15] <apachelogger> xD
[17:15] <Whiskey`Wonka> ill hold of rebooting for a while if you have any ideas
[17:16] <Taduro> apachelogger: yes, at my home (my user is Soul but I don't use the same nick because is taken)
[17:16] <Whiskey`Wonka> its up to 4F, yay
[17:16] <apachelogger> Taduro: then that log is impossible to happen
[17:17] <Taduro> but I didn't rebooted
[17:17] <Taduro> I'm doing it in the..
[17:17] <apachelogger> you don't need to
[17:17] <Taduro> tty6
[17:17] <apachelogger> the session folder you moved prevents a previous session containing psi/quassel to be started again and if you moved all files out the autostart folders psi/quassel also should not be automatically started
[17:17] <apachelogger> makes no sense
[17:18] <apachelogger> Taduro: grep -r psi ~/.kde
[17:19] <Taduro> oooooooooo my goooood what iss thiiiiiiis
[17:19] <Taduro> lol
[17:19] <Taduro> haha
[17:19] <apachelogger> lol?
[17:19] <apachelogger> Whiskey`Wonka: so... you could try to find someone in #kde-devel who knows a thing or two about polkit to help you debug this, but short of that I'd simply reboot
[17:20] <apachelogger> it certainly would help a bunch if we could find a way to trigger the issue reliably, but so far that wasn't the case :S
[17:21] <Taduro> apachelogger: http://paste.ubuntu.com/6525708/
[17:21] <Taduro> I think the problem is not with psi :S
[17:21] <apachelogger> :O
[17:22] <apachelogger> Taduro: if you get the black screen and hit alt-f2 does an input field appear?
[17:22] <apachelogger> although that would be odd
[17:22] <Taduro> no
[17:22] <Taduro> because
[17:22] <Taduro> I can't log in
[17:22] <Taduro> the black screen appears when kde is starting
[17:22] <apachelogger> right
[17:22] <Taduro> do you know when the HDD image appears?
[17:22] <apachelogger> but you don't get thrown back to the logion screen, right?
[17:22] <Taduro> nope
[17:23] <Taduro> it's like
[17:23] <apachelogger> ok, so try hitting alt-f2 on that black screen :P
[17:24] <Taduro> apachelogger: bnitg
[17:24] <Taduro> bnothung
[17:24] <Taduro> nothing*
[17:24] <apachelogger> brrr
[17:24] <apachelogger> Taduro: mv ~/.kde/share/config/plasma* ~
[17:28] <Linusnewb> i haven't anything find about a renamed service as networking or networkmanager :(
[17:28] <apachelogger> ?
[17:38] <Denc> hello, i run into problems with transsmison and in my case transsmision wont download torrents, have anyone any idea what can i do wrong?
[17:40] <hackndoes> Hi guys
[17:41] <Guest80451> how do I prevent nouveau from loading? I added a blacklist file with 'blacklist nouveau' and 'options nouveau modset=0' but it doesn't help
[17:42] <Guest80451> for some reason it's still loaded
[17:43] <Guest80451> Guest80451 is me
[17:44] <Guest80451> do I also need to un install the nouveau driver from the system?
[17:44] <Guest80451> I wan't to install the official nvidia driver from nvidia site
[17:49] <dougl> hackndoes_, nvidia?
[17:49] <Taduro> apachelogger: I rebooted and nothing, it has no sense.... I'll try to do a backup and then reinstall..
[17:50] <dougl> hackndoes_, I don't think you need to go to all that trouble... do the existing drivers work? do you have  a gui?
[17:51] <hackndoes_> dougl: yes nvidia
[17:52] <hackndoes_> dougl: I don't like the nouveau
[17:52] <hackndoes_> it's too slow
[17:53] <apachelogger> Taduro: reinstall sounds like too much... something in your users $HOME is creating the issue
[17:53] <dougl> hackndoes_, but you have a gui?
[17:53] <apachelogger> Taduro: you could try mv .kde kde (i.e. resetting your kde settings)
[17:53] <hackndoes_> dougl: now I do yes
[17:54] <hackndoes_> dougl: but with nouveau
[17:54] <apachelogger> Taduro: if that does not help it already reduces the amount of places where the bad boy could be hiding... if it does work then you just need to move .kde/share/config/ files around until login starts working
[17:54] <Taduro> apachelogger: that sounds nice
[17:55] <dougl> hackndoes_, go on the k menu button and when search for "jockey-kde" and run that and it will install the drivers you want.
[17:56] <hackndoes_> noe I want the official nvidia. many users say that the offical nvidia drivers work much better for them
[17:57] <dougl> hackndoes_, apparently there is a bug where the additional drivers application wrongly reports the nvidi... jockey-kde will install the official nvidia drivers
[17:57] <hackndoes_> dougl: what?
[17:58] <dougl> someone correct me if I am wrong "jockey-kde will install the official nvidia drivers"
[17:58] <hackndoes_> dougl: I can't find a jockey-kde application in kde menu
[17:59] <hackndoes_> dougl: is jocky-kde and the additional drivers the same?
[17:59] <hackndoes_> when I ran jocky-kde it laumched the additional drivers application
[18:00] <dougl> hackndoes_, I was saying after you use the jockey-kde (additional drivers) the nvidia official drivers will be installed and used but the application "jockey-kde" that I told you to "SEARCH" for will find additional drivers and when you run that the second time it will say the official drivers are installed but not in use...
[18:01] <dougl> that is a bug... you know nvidia drivers are being used because when you boot and kde starts you briefly see the official nvidia splash screen.
[18:01] <hackndoes_> dougl:  but the official nvidia driver is a more advanced version
[18:01] <hackndoes_> so I can't disable the nouveau from loading?
[18:01] <dougl> sure - I use them too. and installed them as per the instruction I just gave you.
[18:02] <hackndoes_> so you didn't install the NVIDIA.run file from the official site?
[18:04] <dougl> no, I used jockey-kde which finds additional drivers app and that plays nicer with kubuntu... honest I did it 4 times since oct 28...
[18:04] <dougl> I have a video of my machine booting and shutting down - wanna see it?
[18:05] <dougl> should be able to make out the nvidia splash... poor quality but I wanted to catch grub and plymouth splash screens too.
[18:05] <hackndoes_> dougl: I know what the nvidia spalsh look like.
[18:05] <Taduro> apachelogger: Please, don't forget me If i keep with this issue haha
[18:06] <hackndoes_> just wanted to install the official latest from the site, people say that it works much better for them
[18:06] <dougl> lol - I knew you would... my point is that proves nvidia drivers are loaded and being used
[18:06] <hackndoes_> so I wanted to try
[18:06] <hackndoes_> ohhhhhhhhhhhhh :)
[18:06] <hackndoes_> well I will install from repo now. you say it will load nvidia? so in lsmod | grep nvidia I will see it?
[18:06] <dougl> jockey-kde will download the latest stable
[18:07] <dougl> yes
[18:07] <dougl> lsmod
[18:07] <hackndoes_> dougl: well I am restarting wish me luck
[18:07] <Taduro> apachelogger: it worked!!!!!1 marry me!!
[18:08] <dougl> true love !!! right on!
[18:09] <dougl> linux love
[18:09] <apachelogger> Taduro: groovy
[18:10] <dougl> So... does jockey-kde get the latest drivers or am I mistaken?
[18:11] <18WAE89NC> dougl: I think you are mistaken
[18:12] <18WAE89NC> I think it just brings the version it manages for each distro (304 is always there and another newer one which you choose if you want
[18:12] <dougl> 319 I tho
[18:12] <dougl> t
[18:12] <18WAE89NC> dougl: currently it's 319.60
[18:12] <dougl> sec checking mine
[18:13] <18WAE89NC> dougl: anyway it didn't succeed, after install I still have the nouveau loaded!!!! it drives me crazy it used to work perfactly
[18:13] <dougl> 18WAE89NC, sec...
[18:13] <18WAE89NC> dougl: it's me hackndoes
[18:14] <dougl> 18WAE89NC, figered... but yes what I described to you I did on mine and version 319.32 was installed
[18:15] <dougl> and that is what you want right 319.32?
[18:15] <18WAE89NC> dougl: you have two 319 versions the 32 and the 60
[18:15] <dougl> sec I will check
[18:15] <18WAE89NC> I want 331 which is on the site but I would sattle for the 60 or 32 but that doesn't work as well
[18:15] <18WAE89NC> for some reason it doens't get loaded.
[18:15] <18WAE89NC> should I uninstall the nouveau?
[18:16] <dougl> 18WAE89NC, still checking - what video card do you have?
[18:16] <18WAE89NC> it's a lapto it's the nvidia nvs-4200 or something like that
[18:16] <18WAE89NC> lemme check exactly
[18:17] <18WAE89NC> dougl: GF119M NVS 4200M
[18:17] <18WAE89NC> but it used to work before. now it just keeps the nouveau there
[18:17] <dougl> and no jockey-kde only installed 319.32 on my end
[18:18] <18WAE89NC> dougl: well what am I to do? should I remove the nouveau?
[18:18] <dougl> no you should not have to un install the nouveau drivers jockey-kde will config the nvidia drivers to load...
[18:19] <18WAE89NC> well it doesn't
[18:19] <dougl> when you ran the additional drivers did it ask you for a password and everything?
[18:19] <18WAE89NC> yes
[18:19] <18WAE89NC> and finished successfully and required restart so I restarted.
[18:20] <18WAE89NC> something doens't let it boot with the nvidia driver
[18:20] <18WAE89NC> it used to work before
[18:20] <dougl> what doe additional drivers say now?
[18:25] <18WAE89NC> dougl: it says it's activated but not currently in use
[18:25] <dougl> 18WAE89NC, when you run "nvidia-settings" from a command line in a window do you get the propietary nvidia config app window
[18:25] <dougl> 18WAE89NC, but did you see the nvidia splash or verify - is saying it is not activated is a bug
[18:26] <18WAE89NC> I don't see it and in lsmod I see the nouveau
[18:26] <dougl> nvidia-settings is where you can see it say what driver is being used... please run nvidia-settings
[18:26] <18WAE89NC> the propriatary nvidia config opens but it thrown an error on open and opens a very limitted window
[18:27] <18WAE89NC> it says this, You do not appear to be using the NVIDIA X driver.  Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server.
[18:27] <dougl> ok... back in additional drivers select 319 drivers and select activate
[18:27] <18WAE89NC> dougl: but it's activated
[18:28] <18WAE89NC> it's green and activated, just saying it's not currently in use
[18:29] <dougl> yeah - mine says that and when I asked about it they said it was a bug and to ignore it.
[18:30] <Bundestrojaner> is it possible to install 2 versions of a programm parallel on Kubuntu?
[18:31] <dougl> Bundestrojaner, easy answer no... if you compile your own yes
[18:32] <dougl> 18WAE89NC, I don't understand... does that notebook have 2 video cards...?
[18:32] <Bundestrojaner> and is it possible to ignoring dependencies?
[18:32] <Bundestrojaner> ignore
[18:32] <dougl> Bundestrojaner, investigate force option
[18:33] <Bundestrojaner> thx
[18:33] <18WAE89NC> yes
[18:33] <18WAE89NC> it has intel and nvidia
[18:33] <dougl> Bundestrojaner, if you do what I suggest there is a good chance you will break your system
[18:34] <dougl> the intel is messing things up
[18:35] <dougl> I knew it... I had one like that a few years back acer-asus I dunno/rememmber and I think I disabled the intel in the bios and never looked b ack
[18:36] <dougl> 18WAE89NC, can you bios disable the intel?
[18:38] <Bundestrojaner> dougl: i want to install a wine 1.5 which includes usb-acces.
[18:38] <Bundestrojaner> But i get the stupid error: "Depends on: wine, but can't be installed
[18:39] <Bundestrojaner> (translated from german, maybe not exactly)
[18:39] <dougl> !ge
[18:40] <18WAE89NC> dougl: well it's optimus and it's disabled
[18:40] <18WAE89NC> dougl: only the nvidia is active in bios
[18:40] <dougl> 18WAE89NC,  lets do jockey-kde again and see what happens.
[18:41] <18WAE89NC> dougl: what am i supposed to do with it?
[18:41] <18WAE89NC> dougl: switch to another driver?
[18:42] <dougl> sure...
[18:42] <18WAE89NC> OK I will try another one
[18:42] <dougl> any nvidia driver should work... that is not an exceptionally new card
[18:43] <dougl> acer or asus notebook?
[18:43] <18WAE89NC> it used to work before
[18:43] <18WAE89NC> dell latitude
[18:43] <dougl> hmm
[18:43] <18WAE89NC> I am trying to reboot now. will return with results....
[18:45] <dougl> :)
[18:52] <dougl> Crap 18WAE89NC is not coming back... I hope I did not get him to nuke his box
[18:53]  * genii makes more coffee
[18:53]  * dougl just refilled
[18:54] <linuxer1995> test
[18:54] <dougl> pass test
[20:50] <Walzmyn> when I boot up, my login screen in on my second monitor (which is not always on) How can I force it to the primary monitor?
[20:51] <Walzmyn> Or make it clone on both monitors at the least.
[22:09] <arthurfiggis> Walzmyn: not very helpful i know, but i've been trying to figure out the same thing :) i have a monitor hooked up via dvi and a tv hooked up via hdmi...every linux distro i've tried defaults to the hdmi tv, which is rather inconvenient :( if i can figure it out on my own i'll mention the solution here, but if anyone else knows... ^^