| === timvishet is now known as timvisher | ||
| === john is now known as johnasassdwsgre | ||
| === zz_XeBlackWater is now known as XeBlackWater | ||
| === Punna is now known as Pwnna | ||
| xubuntu33w | HI there, I was most impressed with X14.04, the install, the GUI, great work, Thanks. But, I am sorry to say, apart from the great GUI, I tried for two days to get X14.04 to share drives on Win Net... Hopeless... | 04:57 |
|---|---|---|
| * xangua sees no question or details | 04:58 | |
| xubuntu33w | Oh, sorry, mu bad, ranting I guess... | 04:59 |
| xubuntu33w | I for the life of me like X, how does one get a stable connection onto a Win network ? | 05:00 |
| xubuntu33w | Tried Samba.... How do premission work in that ? | 05:00 |
| johnasassdwsgre | xubuntu33w, have you tried system-config-samba ? | 05:01 |
| xubuntu33w | Yes followed the web link that did that, Sorry DOS man, and Linux is a bit of a mistry to me.... | 05:02 |
| xubuntu33w | Had a connection for awhile, until restart.. | 05:02 |
| xubuntu33w | Only with the "Home" folders, but, was triying to share USB HDD over network ? | 05:03 |
| xubuntu33w | Like it, great stuff, clean, easy to follow, but network shares... ?? Impossible... Anyway moving back to win7 (rubbish).. But thanks.. | 05:04 |
| === XeBlackWater is now known as zz_XeBlackWater | ||
| === zz_XeBlackWater is now known as XeBlackWater | ||
| quazimodo | yo | 09:41 |
| quazimodo | there anyway to make xubuntu wake up from suspend via usb wireless mouse click? | 09:42 |
| quazimodo | via a menu or something, I don't want to hard wire a particular mouse/keyboard device which seems to be what the guides are showing | 09:43 |
| deshipu | quazimodo: in bios settings of your computer | 09:45 |
| quazimodo | deshipu: oh? | 09:46 |
| quazimodo | i thought it was somewhere else :P | 09:47 |
| shanti | bonjour | 09:53 |
| shanti | quelqun pour un petit conseil ? | 09:54 |
| cfhowlett | !fr | shanti | 09:55 |
| ubottu | shanti: Nous sommes desoles mais ce canal est en anglais uniquement. Si vous avez besoin d'aide ou voulez discuter en français, veuillez taper /join #ubuntu-fr ou /join #ubuntu-qc. Merci. | 09:55 |
| deshipu | I'm always fascinated by different levels of courtesy in those messages in different languages. | 09:56 |
| deshipu | sorry for ot | 09:56 |
| === XeBlackWater is now known as zz_XeBlackWater | ||
| === zz_XeBlackWater is now known as XeBlackWater | ||
| Megabyte | Hello, guys | 11:10 |
| === XeBlackWater is now known as zz_XeBlackWater | ||
| === zz_XeBlackWater is now known as XeBlackWater | ||
| xubuntu3i8 | anyone one ? | 15:34 |
| xubuntu3i8 | on* | 15:34 |
| GridCube | lol, less than a minute | 15:35 |
| El_Presidente | hi is sync to vblank in the compositor also possible on the second screen? because it works flawlessly on my primary monitor but my secondary monitor still shows tearing | 15:51 |
| === XeBlackWater is now known as zz_XeBlackWater | ||
| sleezio | hello, can someone recommend a system log viewer for xubuntu? i installed the ksystemlog from software center, but it isn't showing up in the menu | 19:30 |
| === benonsoftware is now known as \b | ||
| === \b is now known as benonsoftware | ||
| === bazhang_ is now known as bazhang | ||
| === zz_XeBlackWater is now known as XeBlackWater | ||
| cajuntechie | Hey everyone, for some reason, I can't lock the screen in a 14.04 session. Is this likely an X problem or something else? I'd like to know which log to look at so I don't bug the mailing list with a bunch of useless crap. | 22:55 |
| ochosi | cajuntechie: how are you trying to lock the screen? did you upgrade to 14.04 or do a clean install? | 23:02 |
| cajuntechie | ochosi: I'm clicking on the menu button then selecting the lock icon. Shortcut doesn't work either. This was a totally clean install. | 23:03 |
| ochosi | ok, strange | 23:03 |
| ochosi | could you open a terminal and run "light-locker-command -l"? | 23:04 |
| cajuntechie | Let me try that | 23:16 |
| cajuntechie | Hmm, it says light locker is not running | 23:17 |
| ochosi | that is weird, did you disable it maybe? | 23:17 |
| ochosi | you could open light locker settings from the settings manager | 23:17 |
| cajuntechie | Hmm, maybe. Let me go look. That actually does sound familiar. I think I might have | 23:18 |
| cajuntechie | Yep, it was off. Thanks! | 23:18 |
| ochosi | ;) | 23:19 |
| cajuntechie | Actually I;m wrong. It still isn't working | 23:19 |
| ochosi | you might have to restart your session after enabling it (although you shouldn't have to) | 23:20 |
| ochosi | but you can start by opening another terminal | 23:20 |
| ochosi | and trying the command i gave you before again | 23:20 |
| cajuntechie | Hmm, I'm still getting the 'light locker is not running'. So I should try to log out andn back in? | 23:21 |
| ochosi | yeah you can try that | 23:21 |
| ochosi | if that doesn't help, come back here and we can look further | 23:21 |
| cajuntechie | OK thanks. Let me try that | 23:22 |
| cajuntechie | Hmm that didn't work. Which log file should I look in? I assume this is an X.org thing? | 23:24 |
| ochosi | nope, not an xorg thing | 23:24 |
| cajuntechie | Oh | 23:24 |
| cajuntechie | lol | 23:24 |
| ochosi | first, let's check whether light-locker starts up | 23:24 |
| ochosi | open another terminal and run "light-locker" | 23:24 |
| cajuntechie | I assume I should sudo this? | 23:24 |
| ochosi | nope | 23:24 |
| ochosi | otherwise i'd have mentioned it ;) | 23:25 |
| cajuntechie | Ahh I've seen this error before. It seems dbus is having problems. I'm getting a failure to connect to socket | 23:25 |
| ochosi | could you pastebin the error? | 23:25 |
| cajuntechie | Sure one sec | 23:25 |
| ochosi | ty | 23:25 |
| cajuntechie | http://pastebin.com/u4Aeqea8 | 23:26 |
| ochosi | oh right, that is just a warning | 23:30 |
| ochosi | ignore that | 23:30 |
| ochosi | is it still running? | 23:30 |
| ochosi | i mean, is the terminal still open etc? | 23:30 |
| cajuntechie | Yes | 23:30 |
| ochosi | ok, open a second terminal and try the "light-locker-command -l" again | 23:30 |
| cajuntechie | That worked | 23:31 |
| cajuntechie | It logged me out fine | 23:31 |
| ochosi | ok, good | 23:31 |
| ochosi | that's a start :) | 23:31 |
| cajuntechie | Whoohoo! lol | 23:31 |
| ochosi | so light-locker is generally working, just not autostarting for some reason | 23:31 |
| ochosi | not sure why though | 23:31 |
| ochosi | but anyway | 23:32 |
| ochosi | you can kill the running instance with ctrl+c | 23:32 |
| cajuntechie | Done | 23:32 |
| ochosi | then run "ls .config/autostart" | 23:32 |
| ochosi | is there a file named "light-locker.desktop"? | 23:32 |
| cajuntechie | Yes, there is | 23:33 |
| ochosi | ok, then run "mousepad .config/autostart/light-locker.desktop" | 23:33 |
| cajuntechie | OK I'm there now | 23:33 |
| ochosi | what does the exec line say? | 23:33 |
| ochosi | (you can paste it in here directly, since it's just one line) | 23:34 |
| cajuntechie | It's empty. | 23:34 |
| ochosi | that's bad | 23:34 |
| cajuntechie | Ok | 23:34 |
| ochosi | ok, close mousepad again, then open light locker settings again | 23:34 |
| ochosi | disable and re-enable light-locker again there | 23:34 |
| ochosi | then open the desktop file again with mousepad and look whether the exec line is still empty | 23:34 |
| cajuntechie | Ok done. | 23:35 |
| cajuntechie | Ahh now it has stuff in it | 23:35 |
| ochosi | ok, better | 23:35 |
| ochosi | then try lock again | 23:35 |
| cajuntechie | Worked like a charm. | 23:35 |
| ochosi | ok | 23:36 |
| ochosi | cool :) | 23:36 |
| ochosi | should be fixed now | 23:36 |
| cajuntechie | Thank you so much for your help! I know it's not a major problem but it's bugged the heck out of me for weeks. | 23:36 |
| ochosi | not sure why it didn't work the first time | 23:36 |
| ochosi | no problem :) | 23:36 |
| cajuntechie | So if this happens again, all I should have to do is do this again. | 23:37 |
| ochosi | yeah, you can also check the running processes to see whether light-locker is running | 23:37 |
| ochosi | e.g. with "ps -A | grep light-locker" from the terminal | 23:37 |
| cajuntechie | I hadn't even thought about that. I guess I didn't remember that light-locker was the lock app for lightdm | 23:37 |
| ochosi | should've called it lightdm-locker :] | 23:37 |
| cajuntechie | lol I probably still wouldn't have remembered lol | 23:38 |
| ochosi | hehe | 23:38 |
| ochosi | sure | 23:38 |
| cajuntechie | Anyway,. thank you again. I'm happy to have my lock back! | 23:38 |
| ochosi | btw, if you ever feel like helping the community by doing some testing, that is always welcome! (ofc any other sort of help is also appreciated ;)) | 23:38 |
| ochosi | our team is quite small, so contributions are more than welcome | 23:39 |
| cajuntechie | I'm actually thinking about doing that. Maybe some dev eventually but definitely testing and doc. | 23:39 |
| ochosi | cool! | 23:39 |
| ochosi | right now we're only about 7-10 people, and we all have lives | 23:40 |
| cajuntechie | Yeah, that's a small team with a lot of work! | 23:40 |
| ochosi | indeed | 23:40 |
| cajuntechie | I'm going to look at getting involved then :-) | 23:40 |
| ochosi | nice, always feel free to ping me if you need help/orientation | 23:41 |
| cajuntechie | No problem and thank you again for your help | 23:42 |
| cajuntechie | I assume testing in a VM is allowed? I don't have to blow away my install? | 23:42 |
| ochosi | absolutely! | 23:42 |
| ochosi | VM testing is totally fine | 23:43 |
| cajuntechie | Great. | 23:43 |
| ochosi | although sometimes we enounter vm specific bugs | 23:43 |
| ochosi | but yeah, gotta live with that | 23:43 |
| cajuntechie | Yeah, I can imagine. But I'm sure somebody will recognize that pretty quick if I don't | 23:44 |
| ochosi | yeah, at least somebody can always check with a real install | 23:44 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!