[07:07] <patrick__> I am new to development, and I am trying to boot up Ubuntu with testdrive for the first time. When I do, Ubuntu starts to boot, but then prints out the error message "BUG soft lockup..." Has anyone seen this before?
[11:24] <test___> Hi
[12:25] <coz_> hey guys, noticed , on t his dual monitor set up, the cursor edge resistance between  the two monitors... is there a way to reduce its effectiveness?
[12:29] <coz_> I mean, when moving a window from one monitor to the other, the cursor gets "stuck" at the bezel edge of the mon itors,, grid kicks in, and it takes a good "swing" to actually get that window to the other monitor by passing the grid animation.
[12:29] <coz_> actrually sometimes a real good  "slam"  to get it past  :)
[12:31] <coz_> ah never mind,, I thiank I got it
[13:09] <BluesKaj> Hiyas all
[13:19] <shaneo1> hi guys, did an update the other day in 13.04, now I am unable to login, the nvidia splash screen flashs up 3 times but I can not get to lightdm, I entered recovery mode and remove nvidia, now I can get access only to tty 1, but when I try to restart lightdm, it returns to the blank screen with a flashing _ in the top left, noueuv display drivers not working either, any advise?  kernal is 3.5.0, although it mentions when I do an up
[13:20] <shaneo1> if the nvidia drivers are in stalled and the blinking _ displays I can not ctrl-alt-f1 to tty
[13:55] <shaneo1> can anyone assist with my login issue
[14:06] <BluesKaj> shaneo1, try nomodeset in the grubline right after "quiet splash , highlight the ubuntu kernel in grub then use 'e' key edit
[14:12] <shaneo1> ok  I will try that thanks
[14:15] <shaneo1> no thats a no go, last line stays  *starting              [OK]  and thats it
[14:15] <shaneo1> is there a log file I can look at to see what is breaking
[14:21] <penguin42> shaneo1: if you can get to a ctrl-alt-f1 console there are a few
[14:21] <shaneo1> yes I am there now
[14:21] <penguin42>  /var/log/lightdm is a good place to look
[14:21] <shaneo1> ok
[14:21] <penguin42> also dmesg
[14:22] <shaneo1> lightdm is empty
[14:22] <penguin42> completely?
[14:23] <shaneo1> yes
[14:23] <penguin42> hmm curious
[14:24] <shaneo1> last entry on dmesg is IPv6: ADDRCONF(NETDEV_UP: wlan0: Link is not ready
[14:25] <shaneo1> im not using IPv6, using IPv4
[14:25] <penguin42> don't worry about that, last message isn't necessarily important
[14:25] <shaneo1> ok I needed to add lightdm.log
[14:26] <shaneo1> failed to start greeter
[14:26] <penguin42> note, it's not /var/log/lightdm.log, it's /var/log/lightdm that's a directory
[14:26] <shaneo1> stopping display
[14:26] <shaneo1> yes I get that :-)
[14:26] <shaneo1> X server stopped
[14:26] <penguin42> ok, what about x-0.log in there?
[14:27] <shaneo1> removing x server auroity /var/run/lightdm/root/:0
[14:27] <shaneo1> exiting with return value 1
[14:27] <penguin42> not last line; can you pastebin the file
[14:27] <shaneo1> not sure how I can from tty
[14:27] <penguin42> pastebinit
[14:29] <shaneo1> just installing it now
[14:29] <shaneo1> ok lightdm.log is http://paste.ubuntu.com/1604617/
[14:31] <shaneo1> x-0.log is http://paste.ubuntu.com/1604621/
[14:32] <penguin42>  var/log/lightdm/x-0-greeter.log   do you have that one?
[14:32] <penguin42> hmm, the error setting MTRR doesn't look good
[14:33] <shaneo1> greeter is http://paste.ubuntu.com/1604626/
[14:33] <shaneo1> no i noticed that error ;-/
[14:33] <shaneo1> I removed nvidia drivers so that I could tty
[14:33] <penguin42> oh, the greeter symbol error looks the more important
[14:34] <shaneo1> ok
[14:34] <penguin42> shaneo1: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1110645
[14:35] <shaneo1> thanks I will take a look
[14:36] <shaneo1> i did notice wayland as part of the update before this issue happened
[14:37] <shaneo1> thanks penguin42, I will do what the bug suggests and get back
[14:39] <BluesKaj> I had a similar issue , that's why I suggested nomodeset , which gave me access to the desktop with startx , but no lightdm greeter
[14:40] <shaneo1> i have tried startx
[14:41] <shaneo1> even installed gdm
[14:42] <penguin42> right, but in this case it's not an X failure, it's the greeter
[14:42] <shaneo1> no didn't seem to work for me, I just tried startx again and got the MTRR error show up
[14:43] <penguin42> ok, is the greeter error still there though?
[14:43] <shaneo1> yes
[14:44] <shaneo1> i think I removed Xauthority ok, not sure how to downgrade the wayland lib though
[14:44] <penguin42> shaneo1: Have you got the ppa installed that bug talks about?
[14:45] <shaneo1> no i don't think so, I just have what raring changed
[14:45] <shaneo1> when I upgraded
[14:45] <penguin42> hmm
[14:45] <penguin42> shaneo1: I'd delete the log file that moans about the bug, stop lightdm  and start it again and see if it comes back
[14:46] <shaneo1> ok
[14:46] <shaneo1> it comes back
[14:48] <penguin42> not sure then, you could try changing greeter
[14:53] <shaneo1> I will see if gdm works for me
[14:53] <shaneo1> i have tried it before, thanks for your help, i have registered myself against this bug
[14:54] <penguin42> it might get as far as letting you login and then fail at a guess
[14:55] <shaneo1> yes it fails back at tty wuth the MTRR argument 22
[14:56] <BluesKaj> wayland ..wth is wayland doing in the mix ?
[14:56] <penguin42> now that one is an nvidia/kernel ism
[14:56] <penguin42> BluesKaj: I think from that bug that the unity stuff is linked against it (presumably _can_ use it) but one of the libraries disagrees
[15:02] <shaneo1> I have no idea what wayland is doing
[15:03] <shaneo1> but i remember seeing it in the updates i did the other day, when it was all working, i assumed Canonical was moving over sometime soon
[15:03] <BluesKaj> perhaps if wayland developement was more complete , we wouldn't have all these X problems
[15:03] <shaneo1> As I have removed the nvidia drivers, i assume it cant see the default noveau drivers
[15:03] <shaneo1> I agree
[15:04] <shaneo1> I have wayland running as a service after doing ps -ef | grep wayland
[15:04] <penguin42> BluesKaj: Well I assume it will take a long time to stabilise it as well
[15:05] <BluesKaj> shaneo1,  check if xserver-xorg-video-nouveau is installed
[15:06] <shaneo1> how should I do that, I don't think I removed it
[15:06] <shaneo1> but i may have done to get nvidia drivers working
[15:06] <BluesKaj> just tryt to install it at the tty
[15:06] <shaneo1> ok
[15:07] <shaneo1> simplist things are best
[15:07] <shaneo1> already the new version
[15:08] <shaneo1> wants me to remove python-xkit and screen-resolution-extra though
[15:08] <shaneo1> im gonna try reinstalling nvidia-current and then reboot with nomodeset
[15:09] <shaneo1> not tried that one yet
[15:11] <BluesKaj> shaneo1, don't use nomodeset after installing nvidia-current ..we won't know what's breaking or we'll have to dsearch the logs , try nomodeset the install nvidia current if you can get to a desktop
[15:12] <BluesKaj> then install nvidia-current
[15:12] <shaneo1> im not able to get to tty with nvidia drivers installed
[15:13] <shaneo1> or desktop
[15:13] <shaneo1> blankscreen with flashing _ top left
[15:13] <BluesKaj> well, then just try nomodeset first ...you need to have tty available
[15:13] <penguin42> shaneo1: I'd suggest dropping back a kernel version, the mtrr stuff is a 3 way fight between bios, kernel and graphics stuff
[15:14] <shaneo1> ok
[15:14] <shaneo1> i see that from the on screen disco I just had lol
[15:15] <shaneo1> started in recovery mode now, to remove nvidia drivers
[15:16] <BluesKaj> the nouveau driver seems to work ok if you just want a working desktop for now
[15:16] <shaneo1> yes that will be fine, if I can get that working
[15:18] <shaneo1> I might just do a fresh install as this is a mash up of 12.10 and 13.04
[15:20] <shaneo1> thanks for your time guys
[15:54] <elhoir> hello all
[15:54] <elhoir> i have a problem at screen resolution with nouveau driver
[15:54] <elhoir> i cant use 1280x1024 - screen goes off
[15:55] <elhoir> it was working in ubuntu 12.10
[15:59] <penguin42> but what res is working for you?
[16:03] <elhoir> 124x768
[16:03] <elhoir> its the res im using now
[16:04] <elhoir> 1024x768 sorry
[16:04] <penguin42> can you pastebin your /var/log/Xorg.0.log ?
[16:05] <elhoir> sure
[16:06] <elhoir> http://pastebin.com/0TRnwPiQ
[16:06] <elhoir> here it is
[16:09] <elhoir> any idea?
[16:09] <penguin42> hmm
[16:09] <penguin42> that sees the 1280x1024 just fine
[16:10] <penguin42> elhoir: can you pastebin the output of xrandr please
[16:11] <elhoir> penguin42, http://pastebin.com/SrQqzb6M
[16:12] <penguin42> hmm, well that says it can see it as well
[16:12] <penguin42> ah, but your error is the screen goes off - not that it doesn't work
[16:12] <penguin42> ah ok, hmm
[16:12] <elhoir> goes in power save mode
[16:12] <elhoir> so, stand-by
[16:12] <elhoir> dunno why
[16:13] <elhoir> and i cant restore it but pressing power button and rebooting
[16:13] <elhoir> and when i reboot, screen is at 1024x768 again
[16:14] <penguin42> hmm
[16:15] <penguin42> elhoir: from a command line you could try   xrandr --output VGA-1 --mode 1280x1024     I suspect that will do the same thing, but it would be good to know?
[16:16] <elhoir> if i dont answer in a short period of time, and i disconnect from IRC, you know the reason :)
[16:16] <shaneo1> BlueKaj: I had disabled nouveau in /etc/modprobe.d/blacklist.conf I now have a different error, still have the silly lightdm error http://paste.ubuntu.com/1604913/ but now the x-0.log has changed http://paste.ubuntu.com/1604916/
[16:20] <elhoir> penguin42, imhere
[16:20] <elhoir> you saw :)
[16:21] <elhoir> screen in stand-by mode again
[16:21] <elhoir> i had to reboot
[16:21] <penguin42> yeh
[16:21] <shaneo1> with nomodeset I get the MTRR  invalid argument (22) again after typing startx in tty1
[16:21] <elhoir> the thing is, login scren is at 1280x1024 i think
[16:21] <penguin42> elhoir: I don't suppose you have another machine on your network do you that you can remotely logonto this one from?
[16:21] <elhoir> and it changes to 1024x768 when logged in
[16:21] <elhoir> penguin42, yes i have - a laptop
[16:22] <elhoir> i can login via SSH
[16:22] <penguin42> elhoir: So what I'd do is remotely login via ssh, then change to 1280x1024 and see if the machine is really still running and it's just the display that's dead
[16:22] <penguin42> elhoir: You should be able to kill X off and restart it, but before you do see if there is anything in /var/log/Xorg.0.log or the kernel logs
[16:22] <elhoir> penguin42, machine is up, i can confirm it
[16:23] <elhoir> penguin42, i can power off machine using power off button, so machine is up :)
[16:24] <penguin42> elhoir: OK, so see if you can see if there are any log information there
[16:24] <penguin42> elhoir: you might be able to do a    export DISPLAY=:0.0  and use xrandr to switch back to 1024x768
[16:25] <elhoir> penguin42, why is login screen at 1280x1024 and iot changes when logged int ? :(
[16:25] <elhoir> logged in*
[16:25] <penguin42> haha don't know
[16:26] <penguin42> elhoir: You could look at /var/log/lightdm there are X logs in there from where lightdm starts X
[16:27] <BluesKaj> shaneo1, my solution was drastic though ,  since 13.04 wouldn't install properly from the live dvd, I installed 12.10 and did a net upgrade to 13.04 ..it was my only way around the problem
[16:28] <shaneo1> yes trying to use the livecd install for 13.04 is a bit hit and miss when installing ;-/
[16:29] <elhoir> penguin42, http://pastebin.com/6zuWKgkY
[16:30] <penguin42> elhoir: Yeh there should be an x-0.log in ther as well?
[16:30] <elhoir> yeah im on it
[16:30] <elhoir> penguin42, http://pastebin.com/wr1mHNxx
[16:31] <elhoir> "resize called 1024 768" :(
[16:31] <elhoir> where??
[16:31] <penguin42> elhoir: Yeh that confuses me more
[16:31] <elhoir> i have no Xorg.conf
[16:31] <penguin42> you shouldn't need one
[16:32] <elhoir> yeah, i mean, that could be the problem, but it isnt
[16:32] <elhoir> res might be hardcoded in there, but i havent that file
[16:32] <penguin42> yeh I'm out of ideas
[16:33] <shaneo1> god I hate display driver issues lol
[16:33] <penguin42> haha yeh
[16:33] <elhoir> filling a bug report maybe?
[16:33] <penguin42> elhoir: Yep
[16:33] <elhoir> im on it
[16:37] <elhoir> penguin42, done https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1114431
[16:38] <elhoir> penguin42, but i dont know if the bug is related to nouveau... i think nope....
[16:38] <elhoir> ubottu, hey you are fast :)
[16:38] <elhoir> ouch
[16:39] <penguin42> elhoir: hehe, it's probably nouveau
[16:40] <penguin42> elhoir: I mean it knows the display can do 1280x1024, it's offering to switch it, and then dieing; you could try giving it a modeline and see if that works
[16:42] <elhoir> penguin42, sorry i dont understand  "giving it a modeline"
[16:42] <elhoir> im not english , im spanish :)
[16:42] <penguin42> elhoir: A modeline is an explicit definition of all the parameters for the monitor/frequencies etc
[16:42] <elhoir> and how can i do that
[16:42] <elhoir> ?
[16:42] <penguin42> it's rather tricky
[16:43] <penguin42> elhoir: if you look in the man page for xrandr there is an example for doing (see the example that uses --newmode)
[16:45] <elhoir> xrandr --newmode "1024x768" 63.50  1024 1072 1176 1328  768  771
[16:45] <elhoir>               775 798 -hsync +vsync
[16:45] <elhoir> this one?
[16:46] <elhoir> bff.. .i dunno what values do i have to put in there ....
[16:46] <penguin42> yeh, as I say it's rather tricky
[16:46] <penguin42> elhoir: So the other thing you could do is if you still have your 12.10 install is to compare the stuff in it's /var/log/Xorg.0.log against the raring and see what changed
[16:48] <elhoir> no i have no 12.10 install
[16:48] <elhoir> i upgraded both desktop and laptop
[16:48] <elhoir> :P
[16:49] <penguin42> nod
[16:49] <penguin42> elhoir: The other thing is that xrandr seems tobe offering both 60hz and 75hz for the monitor; not sure which one it's using but it might be worth trying to figure out how to do the other
[16:50] <elhoir> its using 75Hz according to monitor menu
[16:50] <elhoir> in 1024x768
[16:52] <penguin42> right but the xrandr output shows it's giving a choice of two for the 1280x1024 mode
[16:52] <elhoir> ahm
[16:52] <elhoir> i cant answer to that....
[16:55] <penguin42> elhoir: You see the + next to the 60 I think that means it prefers the 60Hz but there is a faster available
[16:55] <elhoir> aha
[16:58] <elhoir> in the "screen" applet insinde gnome, 1024x768 is 4:3 while 1280x1024 is 5:4
[16:58] <elhoir> it doesnt matter, itsnt it?
[16:59] <penguin42> shouldn't
[17:02] <elhoir> ok
[17:19] <elhoir> so... what can i do? :(
[17:20] <penguin42> elhoir: Try booting off a 12.10/12.04 live image and capture an xorg.0.log ?
[17:21] <elhoir> ok i will, and i will attach output to the bug report
[18:07] <BluesKaj> shaneo1_, how goes the kernel install ?
[18:08] <shaneo1_> I have manually installed the kernel, have 3.0.8-4-generic now, but still have the same login issue... damn
[18:08] <shaneo1_> lol
[18:08] <shaneo1_> a lot of blood sweat and tears
[18:09] <shaneo1_> but i must be getting somewhere as I can no longer install nvidia-current, says it depends on nvidia-304
[18:09] <shaneo1_> so im guessing something is locking up the x.org
[18:12] <BluesKaj> oh , dump the xorg if it's interfering m, then run nvidia-xconfig after you get a successful nvidia driver install
[18:13] <BluesKaj> ytou shouldn't need an xorg file with nouveau , it's actaully better not to have one
[18:14] <BluesKaj> which nvidia card , shaneo1_ ?
[18:14] <shaneo1_> GEFORCE 9800M GT
[18:15] <shaneo1_> you suggesting I manually download it from Nvidia site?
[18:16] <BluesKaj> no
[18:17] <shaneo1_> ok
[18:17] <BluesKaj> but that card gives you more driver options
[18:17] <BluesKaj> in the kernel
[18:17] <shaneo1_> ok
[18:18] <shaneo1_> not delved in there. To me its like a black box lol
[18:19] <BluesKaj> I'm running an entry level 8400gs and it runs great on thenew 310.32 , on the 3.8.0.4 kernel , but that comes later
[18:20] <shaneo1_> I have had mine running great too on the 310, I even updated to the 313??
[18:20] <bjsnider> what login issue?
[18:21] <shaneo1_> still the same symbol lookup error for libgdk-3.so.0 and the undefined symbol: wl_resistry_interface
[18:23] <shaneo1_> ok lightdm is running, but nothing displays
[18:24] <shaneo1_> after I did a sudo service lightdm restart
[18:54] <STiK> Damn... Ubuntu runs better in VM than it does natively on my laptop.
[18:55] <elhoir> STiK, and what is more damn strangeous, alpha versions, runs for me better than final releases :PPPP
[18:55] <STiK> I've noticed that as well lol
[18:58] <ironhalik> elhoir: same here
[18:58] <ironhalik> on 13.04, my x220 power consumption oscilates around 9-10W most of the time
[18:59]  * elhoir has a GT 220 too
[18:59] <ironhalik> I bet my laptop it will be around 13-15 after release
[18:59] <ironhalik> ThinkPad x220 ;>
[18:59] <elhoir> i have a problem with resolution, but nothing hard
[18:59] <elhoir> ironhalik, ouch sorry :)
[19:00] <ironhalik> guys running arch achieve 7W idle
[19:01] <ironhalik> but they don't have Unity :>
[19:02] <elhoir> sometimes i think about using Debian instead of Ubuntu, but Debian has pretty old stuff in it :(
[19:02] <STiK> I've grown to kinda like Unity.
[19:03] <ironhalik> I fell in love with Unity, around 11.10
[19:03] <ironhalik> except some quirks
[19:05] <elhoir> i didnt until 12.04 iirc
[19:05] <elhoir> but at job i couldnt ebable it
[19:06] <elhoir> dunno why, probably the integrated nvidia card
[19:06] <elhoir> it was a 7100
[19:06] <elhoir> nvidia nforce 630i/7100 IIRC
[19:06] <STiK> My laptop has the stupid hybrid graphics.
[19:07] <ironhalik> STiK: bublebee not working for you?
[19:07] <elhoir> STiK, afaik Intel integrated GPUs works very well in Linux
[19:07] <elhoir> due to good open drivers
[19:07] <STiK> I had it working well with 12.10 but not 13.04 yet
[19:08] <STiK> But since this seems to work much better in VM I may just do that :)
[19:23] <STiK> That was odd.. Had to copy version.h over for tools to install.
[19:30] <SonikkuAmerica2> I'm liking the vamped Unity dash and the new pinwheel logo. What else has been implemented so far? (I have the upgrade)
[19:35] <ironhalik> anyone noticed eclipse hanging on "Loading Workspace"?
[19:40] <ironhalik> ok, removed the config files
[19:43] <penguin42> perfectly normal behaviour for eclipse....
[19:43] <ironhalik> is there any way to integrate eclipse menu bar into unity?
[19:44] <ironhalik> at least a relatively bug free way
[22:23] <Guest48290> When I try to run Raring on testdrive, I get an error message saying "BUG: soft lockup..." Has anyone seen this before?