[00:00] <ArtArfon> ScottK: Perhaps you should say this to the people destroying gnu/mc.
[00:00] <ScottK> ArtArfon: I've no idea what you're talking about, but I'm reasonably confident it's not closely related to Ubuntu development (which is the topic of this channel).
[00:02] <ArtArfon> ScottK: If you dont know anything, then why adress me at all ?
[00:04] <ScottK> ArtArfon: Unless you have something to say relevant to Ubuntu development, please don't say anything at all (if a certain class of people have body odor problems doesn't qualify).
[00:04] <ArtArfon> ScottK: I note youre dressed for the occation :P
[03:43] <kees> pitti: I'm curious what you think of apport upstream commit 1792 -- I was trying to find a way to handle key clobbering without doing a "raise"
[04:07] <Hobbsee> hmmm. how would i track down why my mouse is bouncing across the screen, rather than moving fluidly after rebotin gteh second time to maverick?
[04:09] <Hobbsee> google is not being helpful
[04:11] <cody-somerville> Hobbsee, wireless mouse?
[04:11] <Hobbsee> cody-somerville: yes, and the keyborad seems tob e gting some elters in th ewrong sequence, or dropping them
[04:11] <Hobbsee> i keep getin gwrong password, and the irc is speaking or itself
[04:12] <cody-somerville> Hobbsee, anything useful in dmesg?
[04:12] <Hobbsee> cody-somerville: nothing obvious to me, but i'm not fluid in it.  i'l pastebin
[04:14] <Hobbsee> cody-somerville: http://www.pastebin.ca/1957945
[04:15] <Hobbsee> i upgraded last night, rebooted, and all was fine, keyboard wroked, etc, installed the enwer virtualbox and wine from their ppas, booted this morning, and sudenly there's major mice and keyboard problems
[04:17] <Hobbsee> Bus 006 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser  <-- and i'm fairly sur ethat's notmy mouse, eiter
[04:20] <cody-somerville> Hobbsee, is it logitech at least? lol
[04:20] <Hobbsee> cody-somerville: yeah, mx30
[04:20] <Hobbsee> * mk300
[04:21] <cody-somerville> Hobbsee, This might be a stupid question but have you tried unplugging and then plugging it back in?
[04:22] <Hobbsee> cody-somerville: have now, no dice
[04:23] <cody-somerville> Hobbsee, does it still register it as LX710 Cordless Desktop Laser?
[04:23] <Hobbsee> cody-somerville: yes
[04:25] <cody-somerville> Hobbsee, lines 749 - 770 look relevant
[04:27] <Hobbsee> good ponit
[04:30] <Hobbsee> cody-somerville: the windows solution worked.  go figure
[04:30] <cody-somerville> The windows solution? whats that?
[04:31] <ebroder> Keep rebooting until the problem goes away?
[04:31] <Hobbsee> that's the one
[04:31] <Hobbsee> "if in doubt, reboot"
[04:32] <Hobbsee> doesn't seem to be a common problem - i couldn't find any other references to it with maverick
[04:32] <cody-somerville> ah, yea I figured that would probably fix it
[04:33] <Hobbsee> and it still detects wrong, incidently
[04:34] <ebroder> That seems like it's likely to be the device mis-identifying to make it easier for Logitech to put the drivers together, but what do I know
[04:34] <Hobbsee> probably
[04:35] <cody-somerville> Hobbsee, It looks like it was probably caused by your nvidia driver hanging on an interrupt
[04:35] <Hobbsee> cody-somerville: i see.  which i assume means i should'nt file a bug
[04:36] <Hobbsee> (and my typing fails now are actualyl me, not the keyboard.  i think)
[04:39] <cody-somerville> Hobbsee, If it happens often you could rewrite your DSDT so that at least the graphics driver didn't screw up USB. Just download and decompile the DSDT, locate the USB devices, and change the permitted interrupt lines, recompile and put in your initramfs.
[04:39] <Hobbsee> cody-somerville: noted
[05:02] <nigelb> Hobbsee: I've seen the keyboard thing with lucid, but I thought that was my hardware being finiky
[05:02] <nigelb> some of the keys would not work on a boot making logging in a pain because the password just wouldn't work
[05:03] <Hobbsee> nigelb: ouch, tha tsucks
[05:03] <nigelb> Hobbsee: yeah.  I just wait it out and it starts working :)
[05:04] <nigelb> (or the windows solution: thou shall reboot until it works)
[05:04] <Hobbsee> hehe
[05:04] <nigelb> hrm, if this is something kernel I should log a bug, but the problem goes away by the time I log in :/
[05:06] <cody-somerville> nigelb, It happens every time you boot?
[05:06] <nigelb> cody-somerville: nope, once in a while
[05:10] <nigelb> cody-somerville: ah, mine's nvidia too.  sigh.
[05:10] <nigelb> I'm hitting the same problem as Hobbsee perhaps.
[05:11] <Hobbsee> nigelb: that was happening all the way into x
[05:11] <Hobbsee> nigelb: so i'm guessing not
[05:11] <nigelb> Hobbsee: 'all the way in x' means?
[05:12] <Hobbsee> nigelb: as in, happens in gdm, happens after everything is loaded.  happened until i shut the machine down again
[05:12] <nigelb> Hobbsee: similar here.
[05:12] <nigelb> my password doesn't have all characters
[05:12] <nigelb> somtimes I can get it, but some keys are still not working.
[05:14] <cody-somerville> I wouldn't be so quick to assume the problem is the same.
[05:14] <cody-somerville> lots of things could cause the symptoms you're describing.
[05:15] <nigelb> hrm, what logs would be the best to get too the bottom of this?
[05:15] <nigelb> if I can get in and get logs maybe I can try something.
[05:17] <cody-somerville> nigelb, I recommend that if you decide to do that then you use ubuntu-bug - it'll collect the logs for you automatically.
[05:18] <nigelb> okay, ubuntu-bug linux next time.  I just hope those keys woork
[05:18] <nigelb> :D
[06:29] <wgrant> maco: Is gally meant to have an explicit 0: epoch? That's a little strange.
[06:30] <maco> wgrant: i got so used to seeing kde packages that start with 4: that i forgot they were optional
[06:30] <wgrant> Haha.
[06:31] <wgrant> See, KDE does bad things to your mind.
[08:34] <pitti> kees: looks fine; if you could add an appropriate stanza to NEWS, too?
[09:26]  * Claudinux help
[13:16] <DocMAX> hi, when compiling programs, they get very big
[13:16] <DocMAX> static dropbear for example
[13:16] <DocMAX> is 900k
[13:17] <DocMAX> pre compiled are only 150k
[13:17] <DocMAX> any ideas?
[18:10] <kees> pitti: thanks, done.
[18:12] <pitti> kees: cheers
[18:57] <LLStarks> hi
[20:09] <prodigy> lol
[20:09] <shadeslayer> wth was that
[20:41] <LLStarks> pitti, you there?
[23:45] <penguin42> bug 657489 may be a nasty one to look out for
[23:46] <penguin42> really none obvious to find and breaks a grub update
[23:46] <DocMAX> hi, whats "stripe" in compiling terms?
[23:48] <penguin42> more context?
[23:49] <DocMAX> i think i read something about a stripe flag
[23:49] <DocMAX> it should make the binary much smaller
[23:49] <penguin42> ah!
[23:49] <penguin42> strip
[23:50] <DocMAX> ah strip! =)
[23:50] <DocMAX> where do i set this flag, and was does strip actually do?
[23:51] <penguin42> DocMAX: It removes symbols from object files - makes it really really hard to debug and if you select some options cause linking problems; but mostly just about debugging
[23:51] <DocMAX> where do i set this flag?
[23:51] <DocMAX> make CFLAGS="-strip" ?
[23:52] <penguin42> I'd normally just use the strip command on the binary; I think Debian package builds tend to do it automatically in the packages
[23:52] <DocMAX> want to compile samba
[23:52] <DocMAX> so i do a "strip smbd" ?
[23:53] <DocMAX> on the binary?
[23:53] <penguin42> yeh - why are you doing that?
[23:53] <DocMAX> smbd is about 10 MB!
[23:54] <wgrant> Why are you building it yourself?
[23:54] <DocMAX> i found other pre-compiled binarys with only 2 MB, i dont know how they do it