[09:58] <czajkowski> aloha
[14:27] <KNRO> hello, I have an autobuild running via a recipe in launchpad, a package I'm making depends on another package that I have in my PPA, however, the build system can't see that, it only builds from MAIN. Is there a way to make it look for packages elsewhere?
[15:51] <dobey> KNRO: it does use packages that are built in the PPA. however, they must be in the PPA you're building in, and they must be fully published in that PPA.
[15:57] <djbobbydrake> anyone else having issues with launchpad?
[15:57] <djbobbydrake> ssh_exchange_identification: Connection closed by remote host
[15:57] <djbobbydrake> ssh_exchange_identification: Connection closed by remote host
[15:57] <djbobbydrake> bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist.
[15:59] <elmo> djbobbydrake: yeah, it's being DOSed, we're working on it
[15:59] <djbobbydrake> elmo: thx
[15:59] <elmo> djbobbydrake: should be back now
[16:00] <djbobbydrake> looks good now - thx!
[17:48] <kiw0r> [18:44] <kiw0r> hey there [18:44] <kiw0r> got a problem running my launchpad under ubuntu [18:47] <kiw0r> i want to compile a example c file to .elf file, the io.h and signal.h is missing. where can i find these?


[00:02] <NCommander> bryce, how can I get trace messages out of Xorg?
[00:06] <bryce> NCommander: strace the X binary.  However, stracing X rarely produces useful output
[00:06] <bryce> I usually end up using some combination of gdb and debugging print messages in key areas
[00:06] <NCommander> That will get the TRACE( )informatoion?
[00:07] <NCommander> Well, I'm not getting anything out of the fbdev driver
[00:07] <NCommander> I can't even tell if its probe function being run
[00:08] <bryce> gdb - breakpoints
[00:08]  * NCommander grabs his ddebs
[00:08] <bryce> debugging prints use X's internal debug/trace function calls (look around in whatever module you're working on for examples)
[00:09]  * NCommander nods
[00:09] <NCommander> Right, but how do I get those trace calls to actually print something, I'm not seeing anything with GDB
[00:10] <bryce> they should be printing to your Xorg.0.log; if not then presumably there's some option or flag that needs set
[00:11] <NCommander> Oh, thanks
[00:11]  * NCommander is an idiot, plain and simple
[00:11] <NCommander> At least I found my issue
[00:11] <bryce> heh
[00:12] <NCommander>         /* For now, just bail out for PROBE_DETECT. */
[00:12] <NCommander>         if (flags & PROBE_DETECT)
[00:12] <NCommander>                 return FALSE;
[00:12] <NCommander> -_-;
[00:12] <NCommander> Why didn't I see that earlier ...
[00:12] <bryce> btw fwiw exit error messages print to your /var/log/gdm/ files
[00:12] <bryce> (although sometimes I find it useful to shut down gdm and use startx, so the errors show up at the console)
[00:13] <NCommander> Debugging Xorg is a whole new ballgame
[00:14] <bryce> tell me about it
[00:18] <NCommander> bryce, want to wager a guess why probing is disabled by default on the fbdev driver?
[00:19] <bryce> unimplemented?
[00:22] <NCommander> Well,
[00:22] <NCommander> doesn't seem like it
[00:22] <NCommander> SCORE!
[00:22] <NCommander> I make Xorg segfault!
[00:25] <bryce> sometimes I also find it interesting to grab the git tree (cgit.freedesktop.org) and browse the changelog for the specific file... sometimes people include more details in their commit message why bits of code were added
[00:52] <NCommander> ah, handy
[00:52] <NCommander> I'll try that
[04:54] <pwnguin> (10:29:01 PM) Justin Dugger: can you bring up a terminal?
[04:54] <pwnguin> (10:29:06 PM) Dave: yes
[04:54] <pwnguin> (10:29:27 PM) Justin Dugger: ps aux | grep firefox
[04:54] <pwnguin> (10:30:13 PM) Dave: GOD DAMMIT
[04:54] <pwnguin> aww
[04:54] <pwnguin> crap
[04:54] <pwnguin> wrong paste buffer =(
[04:55] <pwnguin> jldugger@jldugger:/var/log $ ls -l XFree86.0.log
[04:55] <pwnguin> -rw-r--r-- 1 root root 42035 2005-05-08 01:15 XFree86.0.log
[05:11] <RAOF> Old school!
[05:13] <pwnguin> yea
[05:13] <pwnguin> i just upgrade, and upgrade
[05:13] <pwnguin> which apparently nobody does
[05:14] <pwnguin> because i get random bugs like "oh we switched to adm instead of admin"
[05:15] <pwnguin> meanwhile, my poor friend dave has been suffering in 8.04, where compiz seems to be crashing everything
[05:17] <pwnguin> wherein he has just admitted to adding things to xorg.conf to fix something
[07:30] <bryce> "It was slow, so I turned on some experimental options which sped it up.  Btw, it's crashing a lot, do you know what that might be?"
[08:04] <RAOF> Heh.
[09:40] <tseliot> seb128: I have rewritten my patch but I'm not sure as to whether it solves the problem since I can't reproduce the it: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/314406
[09:41] <tseliot> the patch is in my branch: https://code.edge.launchpad.net/~albertomilone/gnome-desktop/tseliot-fixes
[09:41] <seb128> tseliot: I'll give it a try thanks
[09:41] <seb128> tseliot: did you try to use an intrepid config?
[09:41] <tseliot> seb128: no, I didn't
[09:41] <seb128> that's what was making it crash
[09:41] <tseliot> do you have one
[09:42] <tseliot> ?
[09:42] <seb128> there is one on the bug no?
[09:42] <seb128> let me look
[09:42] <tseliot> ah, right, it wasn't attached but only copied and pasted
[09:42] <seb128> the xml is in the bug description
[09:42] <seb128> one of the dup has one too
[09:43] <tseliot> ok, let me try it
[09:52] <tseliot> seb128: when I log in an error dialog tells me that the settings cannot be applied and g-s-d doesn't segfault
[09:52] <seb128> ok good
[09:53] <tseliot> seb128: however I was able to reproduce another bug (with my own xml file) which creates an endless loop. I would like to fix this one too
[09:54] <seb128> the one you were discussing on the chan yesterday?
[09:54] <tseliot> yep
[09:55] <tseliot> I think that when the backlight is changed, the driver reprobes outputs, etc.
[09:55] <seb128> do you want to get that in the same upload? that's also a gnome-desktop change?
[09:55] <tseliot> yes, it's in gnome-desktop and it would be nice to have both patches in the same upload
[09:55] <seb128> ok, let me know when you want to get those sponsored
[09:56] <seb128> I'll not upload right now anyway due to the jaunty freeze
[09:56] <tseliot> seb128: also I didn't say that my patch fixes bug 314 as I wasn't sure that it could actually fix the bug. I'll correct the changelog too
[09:56] <tseliot> ok
[10:51] <tseliot> seb128: I can solve the other problem only if I stop both gnome-settings-daemon and gnome-power-manager on my laptop
[10:56]  * tseliot tries preventing g-s-d from listening to any kind of randr event
[11:01] <tseliot> no, it doesn't solve the problem
[12:35] <tseliot> seb128: I have found a workaround for the 2nd bug
[12:35] <tseliot> seb128: the reak problem should be in either X or in the Intel driver though
[12:35] <tseliot> s/reak/real
[12:36] <seb128> what is the workaround, wouldn't it better to fix the driver?
[12:37] <tseliot> seb128: if I prevent both g-s-d and gnome-power-manager from listening to RandR events I can't reproduce the problem
[12:38] <tseliot> yes, it would be better to fix the driver instead. I've never touched Intel code but I'll see what I can do
[12:38] <seb128> ok
[12:39] <tjaalton> is this the 'randr-probe bombing' bug, making the session slow?
[12:39] <tseliot> yep
[12:40] <tjaalton> AIUI it only happens with the updated libxrandr
[12:40] <tjaalton> but you already knew that?
[12:40] <tseliot> no, I didn't
[12:40] <tseliot> ok, I'll have a look at the diff then
[12:41] <tjaalton> bug 307306
[12:41]  * tseliot > lunch
[12:41] <tseliot> thanks
[14:14] <tseliot> seb128: I have fixed another issue in my patch so that it doesn't complain that the xml in .gnome2 is missing when no configuration file is available
[14:14] <seb128> tseliot: ah good
[14:14] <tseliot> seb128: I'll put it in my branch soon
[14:14] <seb128> cool
[14:16] <tseliot> seb128: another thing. Currently if some of the devices described in the xml are not connected you get an error message on login (every time) which says that your settings cannot be applied. Do we really want this?
[14:16] <seb128> I would say we don't no
[14:17] <tseliot> ok, in which case do you think we should show the error dialog?
[14:23] <tseliot> seb128: shall I simply ignore the error and prevent g-s-d from showing the dialog every time?
[14:25] <seb128> I think that makes sense
[14:26] <tseliot> ok
[15:15] <NCommander> bryce, w.r.t. to the machine id autoconfiguration mechanism discussed on the list, do you think there will be any issues getting that included in Ubuntu Xorg packages? (I'm working upstream git, but it probably will take some time/effort before the changes would flow from upstream into Ubuntu)
[15:49] <tjaalton> NCommander: sure
[15:50] <tjaalton> er, I mean it's possible to just add a patch for now
[15:50] <tjaalton> when it works
[15:55] <NCommander> tjaalton, well, I'm drafting an email to<EMAIL_ADDRESS>[15:55] <NCommander> tjaalton, is there an Ubuntu-X list I can Cc?
[15:56] <tjaalton> sure<EMAIL_ADDRESS>[15:57] <NCommander> tjaalton, thanks :-).
[15:57]  * NCommander adds this channel to his AJOIN list
[16:05] <NCommander> tjaalton, sent :-)
[16:08] <tseliot> seb128: I have updated my patch and the changelog in my branch: https://code.edge.launchpad.net/~albertomilone/gnome-desktop/tseliot-fixes
[16:08] <seb128> tseliot: ok, sponsoring will not be for today they are still working on the alpha but I'll give it a try later and let you know how it works for me
[16:08] <tseliot> seb128: ok, great
[16:08] <seb128> tseliot: could you add a comment to the bug to say that you have an updated version?
[16:08] <tseliot> sure
[16:10] <tseliot> done
[16:12] <seb128> thanks
[17:56] <NCommander> tseliot & bryce, I'd like feedback on my load mechanism once you get a few minutes.
[19:06] <superm1> bryce, i'm assuming intel 2.6 will be pulled in for jaunty, correct?  If so, i might try to formulate some patches that will get HDMI audio working without jumping to a whole knew alsa version
[19:07] <tjaalton> superm1: correct, once it builds against the kernel drm headers
[19:07] <superm1> oh that's still not sorted :(
[19:07] <tjaalton> nope
[19:08] <superm1> where's the disconnect right now?
[19:08] <tjaalton> it needs some compat stuff in the headers
[19:09] <superm1> so would it make more sense to ship this then in the X package where you guys can control it for most of the release and switch to the kernel one when you know it gets stable then, or is this more of a one off thing that shouldn't be happening very often?
[19:09] <tjaalton> well, shouldn't happen anymore after this :)
[19:11] <bryce> heya
[19:12] <bryce> tjaalton: what's the next step we should do for getting the kernel headers sorted?
[19:12] <tjaalton> bryce: filing a bug and assigning it to jbarnes (doing right now)
[19:14] <tjaalton> there, freedesktop bug 19591
[19:18] <bryce> tjaalton: are there any kernel-side changes to be done in ubuntu?
[19:18] <tjaalton> bryce: whatever comes from that bug
[19:18] <tjaalton> once it's applied upstream, it'll be pretty simple for them to pull
[19:19] <tjaalton> them = kernel-team
[19:19] <bryce> ok great
[19:19] <tjaalton> one fix was pulled in earlier, but it wasn't enough
[19:20] <bryce> so.. next question is xserver; how are we with that, anything I can help get sorted out?
[19:23] <tjaalton> I've merged it locally.. the only thing that probably should be added is the build-dep on linux-libc-dev, and adding it to xserver-xorg-dev deps
[19:23] <tjaalton> *the only thing missing until ok to upload, that is
[19:23] <tjaalton> I'll have time tomorrow :)
[19:23] <bryce> ok cool
[19:24] <bryce> perfect; we're in freeze still today anyway :-)
[19:24] <tjaalton> the drm header mess is holding mesa too
[19:25] <tjaalton> +back
[19:25] <bryce> erk, not fixed in the latest rc?
[19:26] <tjaalton> it doesn't build
[19:26] <bryce> what's the plan there?
[19:26] <tjaalton> the same fix as with -intel
[19:27] <tjaalton> the dri driver from mesa doesn't build
[19:27] <tjaalton> practically the same error too
[19:27] <bryce> ok, do we need a bug in on it too, or will someone (jesse?) address it when intel is addressed?
[19:27] <tjaalton> 'drm_i915_flip_t' undeclared
[19:27] <tjaalton> once the drm headers are fixed, the dri driver should build
[19:27] <tjaalton> so it's the same bug
[19:27] <bryce> ok
[19:27] <tjaalton> also mentioned there
[19:28] <tjaalton> (on the bug)
[20:42] <NCommander> bryce, how much do you know about regular autodetection? it *looks* like the FBDevProbe functions are called, so I'm now extremely confused
[20:43] <bryce> NCommander: I've tinkered with it only a bit, and more with the PCI stuff than the probe stuff
[20:43] <NCommander> Well, I'm just seeing if I'm loosing my mind about how AutoConf works
[20:43] <bryce> iow, at this point you may know more than me... but feel free to bounce ideas off me
[20:43] <NCommander> Well, it looks like the probe functions ARE called
[20:43] <NCommander> (i don't see where, the backtrace says its somewhere in xf86CallDriverProbe from InitOutput)
[20:45] <NCommander> Oh wait, this may be one of those **** I'm an idiot things :-)
[20:45] <bryce> hehe
[20:46] <NCommander> Its getting to the fbdev prober because its falling back on it
[20:46] <NCommander> (no other drivers are loading)
[20:46] <NCommander> WHich in turn calls its own probe functions.
[20:46]  * bryce nods
[20:46] <NCommander> Mystery solved
[20:46] <NCommander> Now if I can just figure out how to sanely get info out of FB devices :-)
[20:47] <bryce> sometimes the fallback logic feels like pinball ;-)
[20:47] <NCommander> This code base burns in all sorts of unclean ways
[20:47] <NCommander> Figuring out the build system was the first fun bit
[20:47] <NCommander> I always wondered why it was called the X strike force
[20:47] <NCommander> Now I know
[20:48] <bryce> heh
[20:57] <NCommander> Oh
[20:57] <NCommander> You are ****ing kidding
[20:57] <NCommander> the FB ID string can have nulls in place of spaces
[20:57] <NCommander> ARGHHHHHHHHHHHHHHHHHHHH
[20:57] <bryce> eww
[20:57] <bryce> that's crazy
[20:58] <NCommander> Ugh. it makes me want to scream, rant, rave, find the developer who designed this mechanism, and beat into them that NULLs shouldn't be used like this!
[20:59] <NCommander>        printf("  id          : \"" "%c%c%c%c" "%c%c%c%c" "%c%c%c%c" "%c%c%c%c" "\"\n",
[20:59] <NCommander>               fscreeninfo.id[0],  fscreeninfo.id[1],  fscreeninfo.id[2],  fscreeninfo.id[3],
[20:59] <NCommander>               fscreeninfo.id[4],  fscreeninfo.id[5],  fscreeninfo.id[6],  fscreeninfo.id[7],
[20:59] <NCommander>               fscreeninfo.id[8],  fscreeninfo.id[9],  fscreeninfo.id[10], fscreeninfo.id[11],
[20:59] <NCommander>               fscreeninfo.id[12], fscreeninfo.id[13], fscreeninfo.id[14], fscreeninfo.id[15] );
[20:59] <NCommander> oops
[20:59] <NCommander> http://paste.ubuntu.com/105322/
[20:59] <NCommander> That's what's required to print out the ID string
[20:59] <NCommander> MY EYES
[21:02] <bryce> oh the fun things you find in the dark corners of that which we call X.  ;-)
[21:02] <NCommander> That isn't X
[21:02] <NCommander> That's kernel madness
[21:03] <bryce> ahh, even darker corners
[21:10] <kees> er, wrong channel
[21:10] <kees> NCommander: http://paste.ubuntu.com/105325/
[22:17]  * NCommander doesn't quite get how xf86MatchDevice works ...


[00:02] <holmanb> Code_Bleu: happy to leave in the sysvinit files, thanks
[00:28] <Code_Bleu> holmanb: I'm walking and commenting via mobile, so hopefully it all makes sense on GH.  Can you resolve any you feel my answer was good enough? :)  Others I've mentioned I can test and/or make some changes...but it will prob be tomorrow.
[00:53] <holmanb> Code_Bleu: resolved the ones that look good, added more context
[15:01] <Code_Bleu> holmanb: all should be good to go in my PR now 😄
[17:32] <holmanb> Code_Bleu: nice :)
[17:32] <holmanb> Code_Bleu: I'll review this morning
[17:38] <holmanb> Code_Bleu: merged
[17:47] <meena> nice
[17:48] <meena> Code_Bleu:  as soon as we get https://github.com/canonical/cloud-init/pull/4654 merged, your usecase will be good to go
[17:48] -ubottu:#cloud-init- Pull 4654 in canonical/cloud-init "dmi: support OpenBSD native reading" [Open]
[17:49] <meena> ds-identify isn't very good at identifying disk resources on OpenBSD…. but, to be fair, cloudinit.util isn't very good at it either
[18:02] <Code_Bleu> holmanb: thanks!
[18:02] <Code_Bleu> meena: sounds good, thanks


[06:54] <Spass> suggestion - make Orage Globaltime display some major cities by default after fresh install, now it looks empty and its window is just tiny
[09:55] <bluesabre> knome: was actually wanting to move all of our branches to git this cycle
[09:55] <Unit193> \o/
[09:57] <bluesabre> https://wiki.xubuntu.org/devel/xubuntu-18.10
[09:58] <Unit193> >  Maintain packaging in vcs, ideally somewhere on launchpad.
[09:59] <bluesabre> (for simpler permission management)
[09:59] <Unit193> You want Vcs-bzr, right?
[10:00] <bluesabre> vcs-git in the end, unless lp's git repos don't work with ubuntu one
[10:00] <Unit193> I'm not sure what we've got that's not in vcs, besides sn-plug
[10:00] <Unit193> (I'm making a bad bzr joke.)
[10:00] <bluesabre> :D
[10:00] <bluesabre> 6AM, can't process jokes :)
[10:01] <Unit193> https://git.launchpad.net/~xubuntu-dev/+git/xfdashboard/
[10:01] <bluesabre> rad
[10:02] <bluesabre> guessing lp doesn't have a repo browser, so we could just list the git repos easily?
[10:03] <Unit193> https://code.launchpad.net/~xubuntu-dev/+git
[10:03] <bluesabre> awesome :D
[10:04] <bluesabre> so, that item is already complete
[10:04] <bluesabre> Unit193, you're pretty dependable
[10:04] <Unit193> Oh, sorry.
[10:04] <bluesabre> lol
[10:05] <bluesabre> does 18.10 have a name? I saw Simon Quigley mention "Cosmic"
[10:05] <Unit193> I have not responded to that one guy that emailed us, but was getting there.
[10:05] <Unit193> Cosmic CANIMAL, so half-named.
[10:06] <bluesabre> neat
[10:06] <Unit193> Could use 'devel' anyway. :>
[10:07] <bluesabre> I'll go around and update branches later if you haven't already beat me to it
[10:10] <bluesabre> Cosmic Capybara would be good, I think
[10:10] <Unit193> I liked other names..
[10:11] <Unit193> 'Chthonic Cthulhu' might have been my fav.
[11:43] <knome> bluesabre, yeah, i notied that
[11:43] <knome> +c
[11:43] <knome> bluesabre, now the question is if you want to handle the migration..
[16:44] <flocculant> Spass: why on earth would I want to remove some random cities from a plugin - just so I can then edit it to have sensible ones?
[16:46] <flocculant> knome: you around later this evning at all?
[16:57] <Spass> flocculant, yes I understand that my suggestion may sound ridiculous to you :) but I still think that having some "random" major cities (3-5) there is better than that - https://imgur.com/vkwqUPs
[16:59] <Spass> you're a power user so editing/removing those cities is a piece of cake, but new user who opens this application for the first time may just think "what the hell is that tiny thing?"
[16:59] <Spass> my opinion
[16:59] <flocculant> Spass: if we take that thinking one step further - shall we default to opening apps on the desktop so that notifications isn't empty?
[17:03] <flocculant> Spass: hang on - we don't actually have that in the panel - it's just installed
[17:04] <Spass> yes, it's a separate app in Accessories
[17:04] <flocculant> then I'm even more opposed to it :D
[17:05] <flocculant> at some point people need to try and work out what they have - nothing to do with being a power user/normal user
[17:11] <Spass> I don't agree, but I'm humble enough to understand, that my opinion doesn't matter here :) but hey, it's good to have some suggestions, right?
[17:11] <flocculant> of course you opinion matters - I just disagree :)
[17:12] <flocculant> if you want to - there's nothing stopping you adding it to the agenda for community meetings - as long as you show up to discuss it with people
[17:13] <flocculant> https://wiki.ubuntu.com/Xubuntu/Meetings
[17:13] <Spass> sure, I'll try to be here on the next meeting, is it scheduled already?
[17:13] <flocculant> nope - but you can add things to the agenda still
[17:16] <Spass> ok thanks
[17:16] <flocculant> no problem :)
[17:24] <Spass> I'm new to this so I don't want to mess something up, how to edit that wiki page? I'm logged in
[17:25] <flocculant> ummm
[17:26] <flocculant> not got time to look at that with yuou now - just add it - if it's not quite right someone will tidy it up
[17:52] <krytarik> LP bug 1768844.
[17:52] <krytarik> From #xubuntu earlier today.
[18:52] <flocculant> oh dear
[19:01] <tracker6> Buenas estoy probando el xubuntu 18.04lts y solo e encontrado un fallo que no tenía el 16.04lts  que es el brillo  de la  pantalla  que no responde  con el teclado ni sube  ni baja.  Aque es debido
[19:02] <krytarik> !es | tracker6
[23:05] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfce4-panel 4.13.3 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfce4-panel-4-13-3-released-tp50973.html (by Simon Steinbeiss)


[09:50] <teddy-dbear> Morning peoples, critters and everything else
[22:02] <InHisName> any humans or teddy bears checking in this evening ?
[23:46] <msalvatore> Hi.


[00:24] <penguin42> oh fascinating, it does work if I login in a private browser window
[18:26] <daftykins> penguin42: they're onto you ;) (Sainsbury's)
[18:38] <penguin42> must be the few kg of discount baking chocolate I bought
[18:38] <daftykins> hehe


[03:38] <arddhu> Hello all!
 Hi. My first post here. I'm new in lubuntu. I've installed it on my PC. I need some good music app which I can also use from my android phone
 Have you followed instructions on the screen (line above the sad face)?
 How you obtained office for install?
 Error message is telling to open a specific website and follow instructions listed there. Have you tried doing this?
[12:27] <Guest10517> kann ich mit leben
 was?
[12:28] <Guest10517> mit dem nicknamen
 Entschuldigung, ich kann nicht Sie wirklich verstehen.
[13:35] <stryker> kde is better
 @stryker [<stryker> kde is better], Than?
[13:38] <stryker> lxde/qt
 @stryker [<stryker> lxde/qt], kde has more years of development and more developers
[13:41] <stryker> ?
[13:41] <stryker> hello
 @stryker [<stryker> hello], do you have any questions about lubuntu?
[13:44] <Maik> @N0um3n0 already left
 Ok, thanks
[13:44] <akem> He really wanted to let us know his preferences.
[13:45] <Maik> they pop up always and everywhere, i'm used to it after 13+ years


[04:13] <lotuspsychje> good morning
[06:14] <ducasse> good morning
[09:10] <marcoagpinto> Heya
[20:26] <jeremy31> A few broken kernel updates on the Mint forums today, failure on installing linux-modules-extra
[20:26] <daftykins> o0
[20:53] <oerheks> jeremy31, must be unrelated to the 5.8 issues on ubuntu?
[20:55] <jeremy31> oerheks: Unrelated issues as Mint doesn't use any meta package for kernels
[21:09] <jeremy31> I wonder if there was some change that got some installs on linux-generic and removed  linux-generic-hwe-20.04  https://ubuntuforums.org/showthread.php?t=2456332&p=14013053#post14013053


[00:15] <Unit193> Hrm, not the one I was thinking.
[01:13] <canthus13> paultag: I just realized you look an awful lot like Patrick Cote...
[01:24] <dzho> maybe a little?
[01:29] <canthus13> from some angles.  (A very out-of-shape Patrick Cote...)
[01:47] <Unit193> Hah.
[10:38] <Zardoc54> Anyone online?
[10:38] <Unit193> Nope.
[10:38] <Zardoc54> :)
[10:38] <Zardoc54> Anyone here in the Dayton area?
[10:40] <Unit193> Couple close, but more towards Cincy.
[10:42] <Zardoc54> I am new to Ubuntu and looking for sources of help and info.
[10:44] <Unit193> You always have the typical places, forum, askubuntu, #ubuntu,etc.  Cool, what'd you switch from?
[10:44] <Zardoc54> WinXP
[10:46] <Unit193> Yeah, that ones getting to it's end of life, could be fun for sure.
[10:49] <Zardoc54> My only problem with Linux is you can't play Warcraft with it  :(
[12:20] <belkinsa> Unit193, where near Cincy?
[16:10] <Unit193> belkinsa: Well there was you and another person.
[16:13] <belkinsa> I think that person moved or is inactive now
[16:13] <Unit193> The group is inactive. :P
[16:16] <belkinsa> Yeah and it's sad
[16:42] <belkinsa> Though some day it will get active again.
[16:57] <Unit193> The whole idea is going away, so maybe not.
[16:58] <belkinsa> Do you know if it's happening in other LoCo's?
[16:58] <Unit193> Sure.
[16:58] <belkinsa> Do you know how they are dealing with it?
[17:46] <wrl_> I do have a question about filing a bug report for the upgrade attempt from 13.04 to 13.10 and can't seem to find anyone on more than a half dozen ubuntu forums to discuss that matter with.
[17:46] <belkinsa> https://help.ubuntu.com/community/ReportingBugs look at this and please ask in #ubuntu, they are the support folks.
[17:46] <jenni> [ ReportingBugs - Community Ubuntu Documentation ] - https://j.mp/1auIGbX
[17:49] <wrl_> ok