[15:10] <cnd> bregma, keep going
[15:10] <cnd> I can hear
[15:10] <cnd> but if I drop, I'm afraid the call will drop
[15:11] <dandrader> call quality is horrible
[15:11] <cnd> bregma, same here :(
[15:12] <cnd> hey!
[15:13] <cnd> tvoss, I fixed valgrind in precise
[15:13] <cnd> would that be picked up automatically?
[15:14] <cnd> there were 4 grail merges
[15:14] <cnd> sure
[15:14] <cnd> thanks all :)
[15:15] <cnd> I don't know :(
[15:15] <cnd> alright, I think that's a wrap
[15:15] <cnd> thanks for joining :)
[15:18] <bregma> cnd, as I mentioned, I think we need to relicense utouch-evemu, utouch-frame, and utouch-grail (or dual license) because they're now linked directly with utouch-geis
[15:18] <bregma> should I get a consult from Canonical legal first?
[15:18] <cnd> bregma, ok, that's what I couldn't understand on the call :)
[15:18] <cnd> send an email to olli
[15:18] <cnd> I doubt it would be an issue
[15:19] <cnd> but I don't know what the process is
[15:19] <bregma> when it comes to lawyers, everything could be an issue
[15:19] <bregma> I will pass the buck to Olli
[15:20] <Satoris> I would imagine that Google would not like to have Chromium become GPL licensed, either.
[15:40] <cnd> tvoss, will the qa instances pick up the next valgrind I uploaded to precise automatically?
[15:41] <tvoss> cnd, yeah valgrind is updated on each job execution
[15:42] <cnd> cool
[15:43] <tvoss> cnd, I installed a precompiled gtest in a snapshot of the build/test vm's
[15:43] <tvoss> as soon as everything is back online, we have test results again
[15:58] <tvoss> cnd, do you know if the evemu-testing framework is able to produce xml output?
[16:09] <bregma> tvoss, evemu uses the standard python unit testing framework
[16:09] <tvoss> bregma, thanks
[16:34] <cnd> bregma, alright, let's tackle this autofoo stuff
[16:35] <cnd> here's my current thinking
[16:35] <cnd> we can provide the sources for xorg-gtest in an xorg-gtest aclocal script as $XORG_GTEST_SOURCES
[16:36] <cnd> it would hold the locations of xorg-gtest-all.cpp and gtest-all.cc
[16:36] <cnd> we also define XORG_GTEST_CPPFLAGS, which would hold the -I flags for include locations
[16:37] <cnd> we can also define $XORG_GTEST_MAIN_SOURCES as xorg-gtest_main.cpp
[16:37] <cnd> and lastly XORG_GTEST_LIBS would be the list of libraries needed to link against (libX11)
[16:38] <cnd> the users of xorg-gtest would then call the aclocal macro, and all the sources, flags, and libs to their tests
[16:38] <cnd> oh right... now I remember why that's bad
[16:39] <cnd> bregma, if you use lots of warning flags, and even worse -Werror, then when you add the gtest sources to your target it will be built with those same flags
[16:39] <bregma> what's wrong with just providing a .pc file with appropriate --cflag and --libs, plus a special variable for the _main.cpp path?
[16:39] <bregma> gtest is a wholly separate concern
[16:40] <cnd> bregma, xorg-gtest should provide for gtest while gtest is broken, imo
[16:41] <bregma> the libgtest problem can also be solved with a simple .pc file with --cflags and --libs and a special variable for the .cpp path
[16:41] <cnd> bregma, we can't ship a .pc file that isn't from upstream
[16:41] <bregma> that .pc file could be bundled with xorg-gtest until it makes it upstream
[16:41] <bregma> as long as it has a different name
[16:41] <cnd> but the xorg-gtest .pc file won't know where the gtest sources are installed
[16:42] <cnd> I don't see any option other than providing an aclocal script
[16:42] <bregma> really, it's completely wrong to solve the libgtest problem through the xorg-gtest package, it should be either upstream or in a separate package
[16:42] <bregma> aclocal script, .pc file, it ends up as the same thing
[16:43] <cnd> aclocal script would be run at package configuration time, while .pc was already run and installed
[16:43] <bregma> yes, a strike against .pc files in the first place
[16:44] <cnd> while it's not ideal that gtest is broken, I don't see why we shouldn't provide a macro to find it too
[16:44] <bregma> the aclocal script I have in my proposed utouch-geis branch can be moved into xorg-gtest
[16:45] <cnd> bregma, I think the sticky point is really the automake inclusion
[16:46] <cnd> I don't see any way around telling people to copy either an automake file or a series of runes into their Makefile.am
[16:46] <bregma> you have a problem with telling people to include the appriate _CFLAGS variable into their .am files?
[16:46] <cnd> adding the sources to the test targets directly isn't a good solution
[16:46] <cnd> it's not the CFLAGS
[16:46] <cnd> it's the sources
[16:47] <bregma> a single source file with a configurable path
[16:47] <bregma> not unlike any other source file
[16:47] <cnd> bregma, you want different CPPFLAGS
[16:47] <cnd> you want to add -w to the end for external sources
[16:48] <cnd> of course, that's the only difference you want in the CPPFLAGS
[16:49] <bregma> we are using a third-party library that does not compile cleanly, and we rely on it?
[16:49] <cnd> it probably does against a specific version of gcc
[16:50] <cnd> but not against the one in precise
[16:50] <cnd> it would be nearly impossible to always compile cleanly against all compilers
[16:50] <cnd> especially when you have things like the big gcc 3 to 4 transition where warnings and errors got a lot more strict
[16:56] <cnd> bregma, the other issue is that the sources may be compiled with more pedantic warnings than what the gtest devs use
[16:56] <cnd> xorg specifies a lot of extra warnings by default
[16:57] <cnd> one example is a warning when you shadow a variable in an outer namespace
[17:04] <bregma> I can think of no way for an automake include snippet to resolve the problem, since using separate compile flags for some source requires building a convenience library and that means passing different flags to the convenience library for each target it gets linked to
[17:04] <bregma> the only reliable way is to have some kind of wackey target in the Makefile.am that gets reprocessed by config.status to massage various flags
[17:04] <cnd> bregma, the closest thing is to use AM_CPPFLAGS and tell the user to use AM_CPPFLAGS too
[17:05] <bregma> yes, force then into rigid lock-step, until everything breaks because they used per-target flags in a per-target way as documented, and they can;t figure out why theu get missing symbols in their link
[17:06] <bregma> that sounds kind of fragile
[17:06] <cnd> it's all a bit fragile
[17:07] <bregma> the least fragile way is to document how to build a gtest library in your project, and have the developers add those three lines where required
[17:07] <cnd> it sounds like the least fragile solution to me
[17:07] <cnd> that may be
[17:08] <cnd> bregma, as for your macro, why should we add a --with-gtest flag?
[17:08] <cnd> when would we have gtest, but not want to use it?
[17:09] <bregma> --with-gtest=PREFIX sets the prefix where to look for gtest (eg. /usr/local)
[17:09] <bregma> --without-gtest will give the default of $(prefix)
[17:10] <cnd> that doesn't make sense to me
[17:10] <bregma> I copied that logic from other macro files in /usr/share/aclocal
[17:10] <cnd> without-gtest should mean "compile without gtest"
[17:10] <bregma> the idea is if you specified --with-gtest=/usr/local/ it will pick up your local copy rather than the system-installed copy
[17:11] <cnd> yeah, but we have two separate variables for that
[17:11] <cnd> with-gtest-sources and with-gtest-includes
[17:12] <cnd> the sources installed by gtest don't include the headers, so with-gtest alone won't work
[17:13] <cnd> you'll always have to provide with-gtest and with-gtest-sources, or with-gtest and with-gtest-includes
[17:16] <bregma> um, perhaps you;re developing under a different OS than I am
[17:16] <cnd> ?
[17:17] <bregma> there is but a single gtest package available through the archives my system points to, and it installs the headers and sources
[17:17] <cnd> yes, but not to the same location
[17:17] <cnd> /usr/src/gtest/src/*.cc and /usr/include/gtest/*.h
[17:17] <cnd> --with-gtest=<prefix> won't work for both
[17:17] <bregma> right, $(prefix) == /usr
[17:18] <bregma> I have no problem with removing the --with-gtest, it's just a convention frequently used by autoconf macros but not all autoconf macros
[17:19] <cnd> I guess I was tripped up by: gtest_srcpath="$gtest_prefix/gtest/src"
[17:19] <cnd> it would need to be $gtest_prefix/src/gtest/src
[17:19] <cnd> but either way, I don't think it's worthwhile to have it
[17:19] <cnd> if I was running ./configure --help, I would be very confused
[17:20] <bregma> OK, consider it gone
[17:20] <cnd> bregma, why don't you use AC_CHECK_FILE for gtest-all.cc?
[17:21] <bregma> 'cos I forget it existed?
[17:21] <cnd> ok
[17:21] <bregma> test -f is a long-ingrained habit, AC_CHECK_FILE would be better
[17:22] <cnd> bregma, I'm thinking that the stuff in my proposed aclocal script is fine
[17:23] <cnd> http://cgit.freedesktop.org/~cndougla/xorg-gtest/tree/aclocal/xorg-gtest.m4?h=source
[17:23] <cnd> is there something that needs to change there?
[17:24] <cnd> inside _CHECK_GTEST in particular
[17:29] <bregma> other than that it should probably be a separate callable macro that can be pushed upstream, and should probably have optional ACTION-IF-FOUND and ACTION-IF-NOT-FOUND args, I have no criticisms
[17:31] <cnd> bregma, the _CHECK_GTEST is separate, and can be pushed upstream
[17:31] <cnd> I'll add ACTION-IF-FOUND to the macro
[17:35] <bregma> is _CHECK_GTEST not in the same .m4 file as CHECK_XORG_GTEST?
[17:36] <cnd> it is, are you saying it should be split into a separate file?
[17:37] <cnd> I worry that splitting it into a separate file would make it seem like a public macro
[17:37] <cnd> it's really just an implementation detail for xorg-gtest
[18:12] <cnd> bregma, here's what I've got: http://paste.ubuntu.com/891007/
[18:12] <cnd> is that alright with you?
[18:16] <bregma> did you test that last AS_IF with and withou an ACTON_IF_NOT_FOUND argument?
[18:17] <cnd> not yet
[18:17] <cnd> I will
[18:17] <cnd> but I wanted to get your thoughts first
[18:18] <bregma> ah, well, it's OK with me from a functional point of view
[18:20] <cnd> ok
[18:21] <cnd> I don't understand launchpad bug queries
[18:21] <cnd> they don't seem to do what you tell them to do
[18:22] <cnd> I'm finding lots of bugs that aren't found by the two queries I sent out last week
[18:23] <bregma> yes, there does seem to be some sort of dark magic involved
[19:42] <dandrader> cnd, in utouch-grail, I activate an atomic 3-touches Touch subscription and an atomic 3-touches Drag subscription. A 3-fingers drag is performed. What should happen?
[19:42] <cnd> dandrader, I think you should get both
[19:43] <cnd> because this is atomic handling, i.e. grail v1 handling, you would receive both gestures for the same touches
[19:43] <cnd> we really should have named this mode something other than atomic
[19:43] <cnd> maybe "compat" mode
[19:44] <dandrader> so that rule of having only one accepted gesture at a time doesn't hold, right?
[19:44] <cnd> it does, in the sense that only gestures for the same touch set are allowed
[19:45] <cnd> i.e. you can't have a one touch drag and a three touch drag at the same time
[19:45] <dandrader> so the rule is that the accepted gestures must take all existing touches
[19:45] <cnd> yeah
[19:46]  * cnd can't wait to move away from atomic mode...
[20:56] <dandrader> for a given recording made with evemu you're guaranteed to get the exact same number of grail slices independently of the machine where that recording is played? i.e., the update frequency will be the same, etc?
[21:01] <dandrader> cnd, ^
[21:01] <cnd> dandrader, should be
[21:01] <cnd> evemu playback is nondeterministic when it comes to timing though
[21:02] <cnd> it should be close, but the exact timestamp deltas between events will never be quite the same
[22:07] <cnd> bregma, I have fixed up the xorg-gtest stuff and confirmed it works with a rejiggered utouch-grail
[22:07] <cnd> it's mostly left the same as before, only now the macros has ACTION-IF-FOUND etc.
[22:08] <cnd> and the readme points out that manual automake rules is a valid way of handling things
[22:08] <cnd> do you want me to send it out for closer review again
[22:08] <cnd> or just push it so we can move on to fixing our tests?
[22:45] <bregma> cnd, if it works, I think it's been reviewd enough that you can just go ahead and push it
[22:52] <cnd> ok
[23:21] <cnd> if I were on the release team I would have real ultimate power
[23:22] <cnd> packages would quiver in my wake
[23:22] <cnd> oops, wrong channel :)
[23:23] <cnd> though to be clear, that was sarcastic :)
[23:25] <bregma> with power comes responibility
[23:25] <bregma> you couldn't drink during UDS, for example
[23:25] <cnd> oh man...


[06:23] <[Ch4m3l30n]> How can I tell which version/release of BlueZ is in the kernel I'm running?
[06:25] <[Ch4m3l30n]> I'm trying to pair my OUYA controller to my desktop PC so my wife and I can play Trine 2 together and it seems like the controller requires the "Auto-pairing (PIN lookup) support" introduced in BlueZ 5.5 released on May 14th 2013. Two subsequent releases within the last 7 days have further improved that controller support and fixed bugs.
[06:27] <mjg59> [Ch4m3l30n]: bluez is in userspace, not in the kernel
[06:28] <[Ch4m3l30n]> kernel modules = userspace?
[06:30] <mjg59> I'm not seeing any kernel modules in the bluez tarball
[06:32] <[Ch4m3l30n]> I wouldn't expect that you should... wouldn't they come from kernel.org?
[06:32] <[Ch4m3l30n]> http://www.bluez.org/about/ says "Currently BlueZ consists of many separate modules:
[06:32] <[Ch4m3l30n]> Bluetooth kernel subsystem core
[06:32] <[Ch4m3l30n]> L2CAP and SCO audio kernel layers"...
[06:33] <ohsix> bluez us entirely userspace, the radios have a socket interface
[06:35] <[Ch4m3l30n]> Let me ask my question a different way... the website http://www.bluez.org/ lists the latest releases as 5.x and the Ubuntu 13.04 package manager lists the latest available package for bluez as 4.101-0ubuntu8b1. Is that an indication that the bluez distributed in Ubuntu is incredibly old or what?
[06:35] <mjg59> It is
[06:37] <[Ch4m3l30n]> OK, I see that 4.101 was released about 1 year ago and the new 5.x versions are only 7 months old...
[06:39] <[Ch4m3l30n]> I will compile from the latest release source code. Thank you for your time and helping me understand the architecture to rectify my confusion. Cheers!
[06:40] <ohsix> theres a reason they're still using 4
[06:40] <ohsix> heh
[06:42] <ohsix> you will break your system, not in a way that can't be fixed,  but in a way not many people are willing to walk you through
[06:42] <[Ch4m3l30n]> ugh
[06:43] <[Ch4m3l30n]> It's so frustratingly paradoxical that Linux is so far ahead of the competition in many ways, yet also so far behind.
[06:45] <ohsix> big number changes imply a lot of change, takes time; most of the bluetooth work is use driven, and people are trying to get audio and stuff for phones/in vehicle entertainment work a bit better in the transition
[06:48] <[Ch4m3l30n]> Yes; I agree.


[02:08] <cheeko> i have ktorrent as my torrent clent whaen ever i put 2-3 torrents to gether to download only the first one starts to download the rest two of them sit idle
[02:09] <cheeko> is ther any other better torrent clent which downloads all torrents simultaneously
[04:45] <lockd> it would be nice if xubuntu and such were split into xubuntu-desktop and xubuntu-recommended
[04:46] <lockd> I keep updating xubuntu-desktop and it pulls in notify-osd
[06:06] <Balsaq> is this some kind of spam?
[06:58] <SandGorgon> anybody know where to pick up a nightly build of thunar from ? it apparently has the network path urls (e.g. smb://) supported using GIO
[08:22] <raquel> hi, I just switched from ubuntu to xubuntu by apt-getting all the xubuntu packages, but my memory footprint is still at 283MB, is this normal or do I need to uninstall some ubuntu programs/processes/etc to reduce the memory footprint?
[08:32] <raquel> !install
[08:32] <raquel> !vanilla
[09:24] <bsulzer> hi ev'rybody. how do i disable the 'feature' of moving a window to the next workspace by dragging them to the borders of the screen?
[09:30] <bsulzer> i have found out, that i've got another problem: i have a dual screen, but it seems, that the second screen is just another workspace. bug or feature?
[09:30] <TheSheep> depends on how you configured it, you can do it in many ways
[09:30] <TheSheep> !dualhead
[09:33] <bsulzer> TheSheep: thx a lot
[10:26] <bsulzer> hi, it's me again.
[10:27] <bsulzer> i'm looking for a list of commands to define my own keyboard shortcuts
[10:28] <bsulzer> for clarification: shortcut: SuperL + Right <command for moving window to next workspace> i'm looking for the <...>
[10:30] <bsulzer> !shortcuts
[10:31] <bsulzer> ubottu: doesn't work
[11:06] <Rahinsoo> hello all
[12:25] <Rahinsoo[Afk]> I've a problem with my Dell Latitude C400. When I update to xubuntu 9.10 : After booting the screens flickers and is shifted to the right about an inch wrapping around to the left side of the screen. The splash screen of the mouse looks good but as soon as the login screen loads is when the problem presents.I'm return to xubuntu 8.04 LTS because I don't display error.My graphic configuration Intel Corporation 82830.
[12:29] <Rahinsoo> somone for help?
[12:30] <Rahinsoo> *someone :)
[12:30] <psycho_oreos> have you actually tried clean install?
[12:32] <Rahinsoo> yes and I test the install to 9.10 directly on this computer but I had the same result...
[12:41] <Rahinsoo> I found this link : http://ubuntuforums.org/archive/inde...t-1307879.html. It is a solution?
[12:52] <Rahinsoo> no solution for my problem?
[12:53] <psycho_oreos> that link wouldn't work
[12:53] <psycho_oreos> and it sounds like xorg driver issue
[12:55] <djura-san> Rahinsoo, can you repeat the prob please?
[12:55] <Rahinsoo> I've a problem with my Dell Latitude C400. When I update to xubuntu 9.10 : After booting the screens flickers and is shifted to the right about an inch wrapping around to the left side of the screen. The splash screen of the mouse looks good but as soon as the login screen loads is when the problem presents.I'm return to xubuntu 8.04 LTS because I don't display error.My graphic configuration Intel Corporation 82830.
[12:56] <djura-san> that is common thing when you have no display drivers installed. Do yu have it installed?
[12:56] <Rahinsoo> I don't no
[12:56] <djura-san> hmm.
[12:57] <djura-san> wait 1s
[12:57] <psycho_oreos> I think since 8.10 the drivers are autodetected
[12:57] <Rahinsoo> I think that Driver Intel is auto on this version...
[12:58] <djura-san> is that so?
[12:58] <djura-san> then it sounds like xorg needs extra tuning...
[12:58]  * djura-san is not so familiar with that
[12:59] <djura-san> what baout your Xorg log?
[13:00] <djura-san> *about
[13:00] <psycho_oreos> these days xorg.conf is mostly blank, there is a way to manually work with it... by painfully extracting lines from xorg.0.log if they contain relevant video parameters and add them in
[13:02] <Rahinsoo> modify xorg.conf isn't the solution?
[13:03] <psycho_oreos> modifying is but you have to modify it correctly or it'll get ignored or spew out errors and leaving you in CLI
[13:04] <Rahinsoo> and install manual the driver?
[13:05] <psycho_oreos> Its hard for me to say because I don't have that chipset.. I must mention that Intel video chipsets can be annoying at times
[13:06] <psycho_oreos> I would personally try out various modes and various drivers.. if none of them gives you what you need, try vesa mode or even set vesa as failback
[13:09] <Rahinsoo> what is vesa and  various modes?
[13:10] <psycho_oreos> http://en.wikipedia.org/wiki/VESA
[13:11] <psycho_oreos> various modes as in the resolution and refresh rates.. or you can try and use the settings as specified from your current setup.. which means you'll need to examine the xorg.0.log from your current 8.10 setup
[13:13] <Rahinsoo> I must upgrade to 8.10...
[13:14] <psycho_oreos> err
[13:14] <psycho_oreos> I meant 8.04
[13:14] <psycho_oreos> misread
[13:15] <Rahinsoo> no problem^^
[13:20] <Rahinsoo> but I don't know to do try various modes and various driver...
[13:28] <ruba> hi
[14:58] <planktum_> ei all, someone told me to try this channel.. so here am i
[14:58] <planktum_> i need to regenerate the xfce4 applications menu
[15:00] <planktum_> is there a way to automatically regenerate the applications menu?
[15:00] <planktum_> or do i have the only and harsh route of doing it manually?
[15:06] <knome> planktum_, in karmic, there is no menu editor for xfce
[15:06] <knome> planktum_, because xfce 4.6 didn't have one, so yes, you'd have to go the manual way
[15:11] <planktum_> knome, thanks.. i wont expend the time on that.. to many new applis
[15:11] <planktum_> argg
[15:11] <planktum_> thanks for the answer
[15:13] <knome> planktum_, no problem! have fun
[15:13] <planktum_> same to you
[15:14] <planktum_> i go again for awesome wm true fun
[15:15] <knome> :)
[15:15] <planktum_> knome, one last question
[15:15] <knome> sure
[15:16] <planktum_> i cant seem to find a way to change my xfce4 lang (localization)
[15:16] <planktum_> have installed few more packages
[15:16] <planktum_> but, since the applications menu is not updated
[15:16] <planktum_> im unsure if there is a helper application to switch
[15:17] <planktum_> im under karmic
[15:18] <planktum_> i see nothing under System or Settings related to language
[15:18] <knome> planktum_, applications -> system -> language support
[15:18] <planktum_> the threads i find are for older xfce4 versions that seemed to have such thing
[15:18] <knome> should exist
[15:19] <planktum_> not in my install, that comes from a "multimedia" related distro
[15:19] <planktum_> any idea on how to add such thing?
[15:19] <knome> let me see
[15:19] <planktum_> i have got all related to lang support via synaptic
[15:20] <planktum_> but im clueless on how to invoque the application in question
[15:20] <knome> try "gnome-language-selector" from termianl
[15:20] <knome> *terminal
[15:20] <planktum_> yes
[15:20] <planktum_> , is not present
[15:20] <planktum_> i will try to install
[15:21] <knome> language-selector
[15:21] <knome> is the pkg
[15:21] <planktum_> uhmm there are many gnome-* thingg...
[15:22] <planktum_> oke
[15:22] <planktum_> getting it
[15:24] <planktum_> it got installed but seems is not in the PATH
[15:24] <planktum_> funny
[15:24] <planktum_> weird
[15:24] <planktum_> neither for the user or for root
[15:25] <knome> /usr/bin/gnome-language-selector
[15:26] <planktum_> ahh
[15:27] <planktum_> there you go!
[15:27] <planktum_> it is now installing some missing packages
[15:27] <planktum_> :)
[19:00] <Sememmon> Hm.. there a way to get xfce to run a script on logout? need to unmount my samba shares before NM decides to drop.
[19:15] <likemindead> There's definitely a way, Sememmon, but I don't know. Anything's possible in Linux. ;-)
[19:23] <Sememmon> -_-
[19:24] <pipedreambomb> hello, anyone there? sorry i'm an irc noob as well as a linux one :)
[19:25] <likemindead> What's up, pipedreambomb?
[19:26] <Besogon> likemindead, Where did you read that?
[19:27] <likemindead> Eh?
[19:28] <Besogon> Some imagine Pipe which can be burst by therorists... :D
[19:29] <likemindead> Sememmon, could you insert something here: http://wiki.xfce.org/tips#handle_acpi_event_for_power_button_show_xfce_logout_options ?
[19:29] <likemindead> In one of those Xfce shutdown files?
[19:31] <Sememmon> that looks to be just for handling acpi events with the power button
[19:32] <likemindead> Some of it, yeah, but what about the "/usr/local/sbin/xfce4-user-session-shutdown.sh" file?
[19:33] <Sememmon> that is being called by the acpi event.
[19:33] <likemindead> Surely what you're wanting has to be close to that.
[20:10]  * genii-around sips his coffee and pokes listlessly at genii_
[20:17] <Besogon> I think that there is no way to easy make local repositary
[20:17] <samile> Hey is there any way to auto login after suspend
[20:22] <_Techie_> samile, i would think so, however i cant think of anything other than a long excessive script which i dont know how to make
[20:23] <_Techie_> anyway, bbs | remaking my xbox HDD
[20:23] <samile> Thanks, I asked in #xfce and they said its a distro specific thing
[20:40] <likemindead> Lazy bot...
[21:52] <syrius> winblows
[21:56] <_Techie_> dont expect any support from me if thats your attitude
[23:56] <fander123> hi guys
[23:56] <vinnl> !hi | fander123
[23:57] <fander123> I have a problem, all the panels are deleted!!!! Even when I right-click the mouse nothing appears!
[23:57] <fander123> what's the problem?!
[23:59] <vinnl> !xfce4-panel
[23:59] <_Techie_> dang, i was gonna type out the fix
[23:59] <vinnl> fander123, see https://help.ubuntu.com/community/XubuntuPanels
[23:59] <vinnl> _Techie_, hehe, never understimate ubottu ;-)
[23:59] <_Techie_> i never do, however i forget what entries are valid


[00:05] <kdub> ugh, friday 4pm. slowest hour of the week
[00:05] <kdemarest> kdub: now it's time for you to get creative?
[00:06] <kdemarest> work on something fun, like http://www.dwavesys.com/en/products-services.html
[00:06] <kdub> if anything, its worse on this side of the country, cause i know 3/4 of it is out having fun already
[00:06] <kdemarest> ah, fun
[00:06] <kdub> that's sick
[00:06] <kdemarest> i just did some sprints in the living room
[00:06] <kdemarest> oh no, how do we heal it?
[00:06]  * kdemarest gives D*Wave CPR
[10:44] <kdemarest> some wolverines were let out by where i live.  i heard them while i was sitting under a tree outside at 2:30am
[10:44] <kdemarest> i am considering going back out, i think someone is after me.
[10:45] <kdemarest> going to go back out, i left a note just in case.
[11:32] <aaditya> O.O