[02:43] <Unit193> "To restart X, type 'sudo /etc/init.d/lightdm' on an ubuntu system."  Really now, no restart?  No `service` command?  Lower case ubuntu? :P
[02:44] <Unit193> IdleOne: Howdy, can you put the word 'restart' somewhere in the !xorg factoid?  Changing it to service lightdm restart may be better as well.
[02:44] <rww> !xorg
[02:44] <rww> !-xorg
[02:44] <Unit193> s/ubuntu/Ubuntu/ would be nice, but not required.
[02:44] <rww> lol so many problems
[02:44] <basketball> rww,  i got unbanned
[02:44] <Unit193> Err, not the sed argument.
[02:45] <rww> does Saucy use kdm? trusty Kubuntu doesn't
[02:45] <Unit193> Everything uses lightdm.
[02:45] <rww> basketball: good good
[02:47] <rww> !no, xorg is <reply> X.Org is an implementation of the X Windows System, and is the part of your system that's responsible for graphical output. To restart it on an Ubuntu system, type 'sudo service lightdm restart'. To fix screen resolution or other X.Org problems: https://wiki.ubuntu.com/X/Config/Resolution . See also !xorgconf
[02:47] <rww> !xorg
[02:47] <rww> !xorgconf
[02:49] <rww> !no, xorgconf is <reply> The /etc/X11/xorg.conf file is deprecated, but sometimes may still be needed to pass values to specific drivers. See `man xorg.conf` for file structure and syntax. | Generic xorg.conf generation: http://ubottu.com/y/xorgconf | ATI proprietary driver specific: http://ubottu.com/y/atiamd | Nvidia proprietary driver specific: http://ubottu.com/y/nvidia
[02:49] <rww> !xorgconf
[02:53] <Unit193> Nice.
[03:23] <basketball> anyone know if the dropbox servers are down
[03:24] <holstein> basketball: thats offtopic here
[03:24] <Unit193> !support | basketball
[03:24] <holstein> http://www.downforeveryoneorjustme.com/ is what i use
[06:48] <MooDoo> hello all
[06:56] <Tm_T> hai
[06:57] <jussi> Morning Tm_T
[06:58] <Tm_T> I apparently keep falling off of freenode
[06:58] <Tm_T> from
[06:58] <Tm_T> bah, more coffee
[06:59] <MooDoo> coffee o/
[08:52] <AlanBell> bkerensa: fixed, thanks!
[09:06] <MooDoo> morning AlanBell
[19:42] <mhall119> can someone mute Otak in #ubuntu-uds-plenary?
[19:42] <mhall119> or kick/ban him
[19:43] <rww> mhall119: everyone with ubuntu/member/* cloaks has ops in there, including you
[19:43] <mhall119> yeah, but I don't know the commands
[19:43]  * mhall119 has the power, but not the knowledge 
[19:43] <MooDoo> slash kick username i think :)
[19:43] <rww> mhall119: /msg chanserv op #ubuntu-uds-plenary and I'll deal with it
[19:44] <rww> erm, stick an rww on the end of that
[19:44] <rww> oh, k1l just joined, they should be able to deal with it
[19:45] <MooDoo> :)
[19:45] <k1l> mhall119: i made a mute on it. should be quiet now.
[19:45] <rww> mhall119: for future reference: /msg chanserv op #channelname nickhere will op that nick in that channel assuming you have op access. after that, if you op yourself, /ban nickhere should do something useful
[19:45] <mhall119> thanks rww
[19:46] <mhall119> fortunately I need that so rarely that I always forget it
[19:46] <rww> good position to be in
[19:48] <k1l> seems like mhall119 is in the right channels :)
[19:48] <Fuchs> /ban nickhere does something completely up to the client, and whether it is useful or not is debatable at best. I'd recommend to either let an operator handle it who knows what is best, or read it up at http://freenode.net/using_the_network.shtml, or if both don't work  (e.g. urgency), at least use something less destructive than a ban
[19:49] <rww> Fuchs: I checked mhall119's client first. it woud have done *!*user@*.domain.net unless he changed defaults :3
[19:49] <Fuchs> rww: still you recommend it in a public channel, hence also other people might follow that advice, with clients such as something with libpurple, or even more worrysome stuff
[19:49] <rww> good point
[19:50] <Unit193> Ouch, libpurple..
[19:50] <ClumsyFairyQueen> eww Pidgin
[19:50]  * ClumsyFairyQueen hides
[19:50] <Fuchs> I didn't intend to start a client war, just wanting to mention that  /ban  is _completely_ up to the client, and some might mess up badly
[19:51] <rww> i still see people with that moreirc pidgin plugin that leaks subsequent commands in /part messages frequently
[19:51] <rww> you'd think someone would have fixed that by now :\
[19:51] <Fuchs> if chanservs quiet is available: that might not be _the_ best solution and I'd still recommend letting someone who knows this stuff handle it, but at least it is predictable and easy to revert, so that would be the slightly less insane option :)
[19:51] <rww> .oO(maybe i should make a bot to detect and message about it)
[19:52] <rww> Fuchs: which CS flag gives /cs quiet? +o?
[19:52] <Fuchs> .oO(maybe not, because IRC bots doing $something on triggers are a bad idea in most cases)
[19:52] <Fuchs> rww: r
[19:52] <rww> Fuchs: thx
[19:52] <Fuchs> you're welcome
[19:53] <rww> Fuchs: well, one PM in response to a /part message and subsequent CTCP VERSION would be less horrendous than usual for bots, but yeah
[19:53] <rww> i'm also too lazy to actually code it so *shrug*
[19:53] <Fuchs> and thus laziness saves the world again :)
[19:54] <MooDoo> don't be lazy delegate ;)
[19:54] <chu> I like to call it structured procrastination.
[19:57] <rww> random reminder that the next Ubuntu IRC Council meeting is almost exactly a week from today, so if anyone has anything they want on the agenda, go put it on there: https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda
[19:59] <chu> "... and keep it out of there!"
[20:00] <Fuchs> I'd vote for that, idoru is shite. But so is, in my opinion, every other (useless) floodbot, ask niko, he knows my opinion (and demonstration)
[20:01] <Fuchs> hm, I guess that wasn't an appropriate word for in here, sorry for that
[20:26] <MooDoo> Fuchs: !language ;)
[20:27] <MooDoo> sorry couldn't resist :D