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