=== Jikan is now known as Jikai [04:35] How do I connect a Nexus 7 running Ubuntu to my Ubuntu computer via USB cable? [04:42] hey guys === jtechidna is now known as JontheEchidna [05:07] i love ctrl+page up/page down :) [05:11] anyone here? i need a hand with seahorse it is really annoying the crap out of me. I use auto login and seahorse asks for my password for some dumb reason. anyone else seeing this? [05:23] anything that accesses the gnome keyring'll require your PW to unlock it if you autologin [05:23] gnomefreak: ^ [05:23] that's been that way since a while now [05:23] *-gtk needs to be rebuilt i hope soon [05:24] TheLordOfTime: last release i was able to get it to stop but it seems i lost the choice or i wasnt looking in the right spot [05:24] gnomefreak: last release i gave up trying to get it to stop [05:24] it happens every new release for a while now, i say last 4 or so dev cycle [05:25] hell even the window controls cant be moved to right hand side any longer [05:26] i get this feeling im not going to be sleeping again. tonight will = day/night #3 i slept for like an hour or 2 in last 3 days [05:27] i guess i have a few bugs to report [05:42] now ii just need to figure out what the other bug was === yofel_ is now known as yofel [09:08] hey, is there a known issue with cifs mounts on raring with 3.8 kernel? always returns CIFS VFS: cifs_mount failed w/return code = -22 in kern.log [09:15] i can list the share fine with smbclient === Jikai is now known as Jikan [11:20] Hiyas all === LoganCloud is now known as Guest19155 [12:55] my cifs mount succeeded with -o guest,sec=ntlm without sec=ntlm it gave error -22 which isnt a sane error in this case Id say [12:56] mount.cifs says sec=ntlm Use NTLM password hashing (default) [12:59] can anyone file this? [13:07] hi all [14:46] https://wiki.ubuntu.com/UbuntuDeveloperWeek Day 3 starts in 14 minutes in #ubuntu-classrom [16:06] ...BBL [16:17] Considering the current stage of development, raring works surprisingly well for me [16:55] Anyone else here unable to load Steam? All of a sudden yesterday, Steam will not load for me... getting this beauty: /home/funnylookinhat/.local/share/Steam/steam.sh: line 403: 5980 Segmentation fault (core dumped) $STEAM_DEBUGGER "$STEAMROOT/$PLATFORM/$STEAMEXE" "$@" === STiK_W_ is now known as STiK_w === STiK_w is now known as STiK_W [19:13] Ok - X has crashed on me multiple times today... but I can't report it... every time I click through the apport screens to report the crash, it crashes again... usually when trying to determine the trace or include the display files [19:13] Any suggestions? I'd love to be able to supply a valid report. [19:19] heh... [19:35] FunnyLookinHat; did you try reporting it through the website? Maybe from a different system? And include the files later? === AlanChicken is now known as alanbell === alanbell is now known as AlanBell [19:40] MrChrisDruif, I wasn't sure which files to include, or what exactly to put in the report... I usually just let apport do it all for me. [19:40] =') [19:40] However - I believe it was an xorg-edgers issue - I've purged the PPA and issue has gone away :) [19:40] Seems legit... [19:40] The beauty of apport - for those of us who want to help but don't have the time to dive through log files... hahha [19:40] ;-) [20:31] FunnyLookinHat: note that you could use apport-cli to file a bug from a tty if you don't have X. Or you install openssh-server and file the bug by running apport-cli over ssh from another system [20:31] FunnyLookinHat: btw, you're not the only one without a functional Steam. I haven't yet debugged it though [20:32] yofel, The problem is that - in reporting the bug for X - it was crashing X again... losing my progress. Is there a way to look up a previous crash and report a bug for that via apport-cli ? [20:32] the crash information is stored in /var/crash/, so you can simply run apport-cli on the .crash file in there [20:32] yofel, it's a bad update - you can get around it with the following: ~$ STEAM_RUNTIME=0 steam [20:32] oh, yay, thanks :) [20:32] no problem :) [20:34] here's a related thread in case you want to bump it... :) http://steamcommunity.com/app/221410/discussions/0/864958435885593880/ [20:38] https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1102660 [20:38] Ubuntu bug 1102660 in xorg (Ubuntu) "Ubuntu Raring Hard Freezes with AMD Driver" [Undecided,New] [20:38] Can someone help me see if this is a bug with X or the kernel? [20:39] Help is appreciated. Thanks. By the way, you may need to look at the log files. === danbeck_ is now known as danbeck === emma_ is now known as emma === danage is now known as jumpin === emma is now known as em