[00:00] <secretlondon> horrible things to debug, I have with my laptop, which i think may actually be thermal
[00:00] <LimCore> RAOF: that should fix that nvidia bug? or is it needed to have installed true non-SMP kernel and drivers
[00:00] <RAOF> LimCore: That should fix it; it only appears when two CPUs are running.
[00:01] <RAOF> LimCore: Ok, more than one CPU :)
[00:01]  * LimCore stops shopping for quad core then
[00:01] <LimCore> MAIN CPU, TURN OFF
[00:03]  * LimCore  echo 0 > /sys/devices/system/cpu/cpu1/online
[00:04]  * secretlondon has found yet _another_ problem with rhythmbox's cd ripping
[00:04] <LimCore> secretlondon: QA of linux software often makes me sad
[00:05] <secretlondon> well it's not thinking about uses in this case.
[00:05] <LimCore> secretlondon: about hardware lockups on laptop - do you have then corrupted FS because of that?
[00:05] <LimCore> I used to use reiser, and after some hw problems my FS got horribly mangled
[00:05] <secretlondon> LimCore: no thankfully it's okay, nothing obviously broken so far
[00:06] <LimCore> now I use ext3
[00:06]  * secretlondon adds that CD to the "I can't rip because rhythmbox is brain damaged" pile
[00:07] <RAOF> secretlondon: Really?  Tried Banshee (from the beta PPA)?  It's cool, and I hooked up the error-detection/correction code in it :)
[00:07] <secretlondon> ROAF: thanks, I'll have a look
[00:08] <secretlondon> ROAF: rhythmbox won't rip multiple artist CDs, it puts them all in different folders :(
[00:08] <secretlondon> ROAF: and there is no way of stopping it
[00:09] <RAOF> Ah, right.  I'm not sure whether banshee does that correctly yet, either.  But there's certainly been discussion of the VA problem.
[00:09] <secretlondon> and I used to use kaudioextractor under gnome but that seems borked for some reason
[00:10] <LimCore> how to debug hard lockups?
[00:10] <LimCore> plugin some funky cpu debugger or something?
[00:10] <LimCore> would be so nice to start second CPU and restart mobo without loosing memory content to debug it.
[00:10] <secretlondon> there's some reference to sshing into a dead box
[00:10] <secretlondon> not tried it though
[00:11] <LimCore> or a hardware solution to dump memory into partion
[00:11] <LimCore> * into something, i.e. firewire or eth or serial
[00:11] <RAOF> LimCore: One of the fundamental problems with that is 'how do you know the kernel's discio subsystem isn't broken'.
[00:12] <RAOF> IE: It _thinks_ it's writing to the right spot on disc, but it's actually scrobbling all over your partition table.
[00:12] <LimCore> dump to serial
[00:12] <RAOF> Yeah; better.
[00:12] <LimCore> it should be in hardware I guess
[00:13] <LimCore> like, a chip that cuts off the CPU on watchdog alarm,  and then just read entire memory to serial
[00:13] <RAOF> There's netconsole or somesuch thing, and a bunch of other kernel logging things; but they're patches against mainline AFAIK.
[00:13] <LimCore> Im thinking lower level. if entire cpu is totally dead
[00:14] <LimCore> like adapter for ram chip
[00:15] <LimCore> you put ram into it,  and it into mobo.  normally it simply acts like 2 cm "cable/extender".  but press a button and then it disconnects from mainboard, and reads all memrory into a wire using buildin chip (using mobo only to take power)
[00:15] <RAOF> That'd be pretty sweet.
[00:19] <LimCore> memory actually survives 10 - 120 seconds after power off
[00:19] <LimCore> from what I read
[00:20] <LimCore> so actually, just moving stick into other box really fast should do it (with bios/etc that do NOT zero it out on bootup)
[00:23] <LimCore> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/180507
[00:23] <LimCore> stupid nvidia bug, I'm on to you.
[00:33] <RAOF> LimCore: Even longer if you quickly cool it to -50C with compressed air :)
[00:36] <LimCore> or simply use liquid nitrogen, its just like 10 usd
[00:36] <LimCore> actually... that might work!
[00:53] <ffm> bdmurray: ping
[00:55] <bdmurray> ffm: hi
[00:56] <ffm> bdmurray: Have you had time to look at my bugcontrol app yet?
[00:58] <bdmurray> ffm: No, but I could do that right now.
[01:01] <ffm> bdmurray: That'd be great, thanks.
[01:01] <ffm> (not to be a bother...)
[01:18] <secretlondon> RAOF: doesn't look like banshee can rip multiple artist CDs either
[01:18] <RAOF> Gah.  Sorry for leading you down a rabbit hole.
[01:18] <RAOF> I thought that had been fixed; clearly that's still TODO :(
[01:19] <lifeless> I use grip
[01:19] <secretlondon> nah that's fine, I'm sick of rhythmbox
[01:19] <lifeless> set it up once, and love it forever
[01:19] <lifeless> multi artist cd's work beautifully
[01:19] <secretlondon> kaudiocreator does/did i think, but I can't get working under gnome currently
[01:19] <secretlondon> lifeless: thanks, i'll have a look
[01:19] <bdmurray> hi lifeless
[01:19] <lifeless> hi bdmurray
[01:26]  * greg-g seconds lifeless 
[01:26]  * secretlondon is downloading it now!
[01:27] <greg-g> :)
[01:27] <greg-g> horrible settings interface, but, luckily you only need to do that once
[01:28] <secretlondon> greg-g well I know _exactly_ how I want my music drive laid out
[01:28] <secretlondon> I've been re-ripping my CDs and keep running into rhythmbox breakage
[01:35] <sectech> Is there anything special when it comes to translation bugs?
[01:35] <greg-g> yeah, rhythmbox has never been a solution for me for anything besides listening to online radio
[01:35] <sectech> A reporter just posted a bug about a spelling mistaken in synaptic... I confirmed as I was able to reproduce it
[01:35] <sectech> bug 228441
[01:37] <bdmurray> I'll fix it but in the future tagging them as string-fix and bitesize would be helpfl
[01:38] <sectech> bdmurray, do we have documentation on what to do in translation problems? Or should I add that to my own personal instructions?
[01:38] <bdmurray> that's english though right?
[01:38] <sectech> yep... US English
[01:42] <sectech> k... so for translations add the tags string-fix and bitesize
[01:42] <bdmurray> not for translations, most of the dialogs are written in English and then translated to other languages
[01:43] <sectech> Okay so just US English
[01:43] <sectech> ?
[01:43] <sectech> Man I could make my own wiki with the documentation I'm making lol
[01:43] <bdmurray> bitesize is for bugs that are easy to fix
[01:43] <bdmurray> string-fix is for dialog changes
[01:44] <sectech> Okay
[01:44] <sectech> thanks bdmurray
[01:44] <bdmurray> However wrt this bug add/remove is not synaptic
[01:45] <sectech> oh... my mistake for not catching that.... sorry....
[01:46] <bdmurray> well, I'm confused about where the misspelling is
[01:46] <sectech> Did you see the guys screen snap?
[01:47] <sectech> basically a space is missing I believe... brb I'll recreate it
[01:47] <secretlondo> no space between is and already
[01:47] <bdmurray> right, I meant which package
[01:47] <secretlondo> synaptic itself
[01:47] <bdmurray> the reporter mentions synaptic but there is no salready string there
[01:48] <secretlondo> it could be apt
[01:48] <secretlondo> dialog box "unable to get an exclusive lock"
[01:48] <secretlondo> i'll transcribe it and add it to the bug
[01:48] <sectech> ps -aux shows synaptic...
[01:49] <sectech> heh I wonder how that spelling mistake was missed during testing
[01:50] <bdmurray> I've got to run for dinner but will check it out later.
[01:50] <secretlondo> sectech actually people regularly overlook those sort of errors, we read it as it should be.
[01:50] <sectech> Is there a wiki for appropriate tags?
[01:50] <sectech> for bug reports...
[01:51] <bdmurray> https://wiki.ubuntu.com/Bugs/Tags
[01:51] <sectech> awesome!
[01:51] <secretlondo> it does look like add/remove programs
[01:51] <secretlondo> i'm not sure what that actually is
[01:55]  * greg-g assumes bdmurray has most of the bug documentation wiki page names/addresses memorized
[01:57] <secretlondon> argh - grip hasn't installed vorbis tools
[01:58] <greg-g> probably a suggested but not dependent package
[01:58] <sectech> Okay here is a good example of a bug where I have no idea what to mark it as...  bug #228438
[01:59] <sectech> A statement with a reply....
[01:59] <sectech> and not a bug
[01:59] <secretlondon> well invalid or fix released. Often we use fixed released for available in devel version
[02:00] <sectech> Okay so in this case fix released would be okay?
[02:00] <greg-g> yeah, it looks like scott just forgot to set the status
[02:00] <secretlondon> I think fix released will wind him up
[02:01] <secretlondon> so invalid, as he specifically asked for a backport
[02:01] <sectech> Okay... invalid it is
[02:03] <sectech> Some of these are easy to deal with... bug #228429 specifically asked for a wishlist.... although I am not sure if there might be an explanation that could be given...
[02:03] <sectech> I didn't touch that one at all yet
[02:04] <secretlondon> we see two packages providing the same file as a bug
[02:04] <secretlondon> but I've set that to wishlist anyway
[02:05] <greg-g> could ask them to file a bug report against the problem package(s)
[02:05] <sectech> greg-g, that might be helpful....
[02:06] <sectech> because I don't think what he is reporting is that common
[02:06] <sectech> AFAIK
[02:06] <secretlondon> when you get it it's very annoying
[02:06] <secretlondon> but it'll be reported against the package that won't install
[02:06] <sectech> I'll make the request
[02:07]  * secretlondon is ripping her first cd with grip
[02:07] <secretlondon> I've confirmed the bug that grip should depend on vorbis tools, as it can't rip without it
[02:07] <secretlondon> but i'm not sure what the rules are for depends/recommends
[02:23] <sectech> pedro_,  I noticed you closed one of the bugs that I requested a backtrace on... bug #228376... Should I be asking for a new apport bug like you did where a backtrace is needed?
[02:24] <pedro_> sectech: yes, that's likely a dup though
[02:25] <pedro_> but yeah ask for an apport rather
[02:25] <greg-g> does all of the hardwork for them
[02:26] <sectech> Hmm okay.... I don't see it in the standard responsive wiki though... I'll add it to my own little instruction manual lol
[02:26] <greg-g> sectech: https://wiki.ubuntu.com/Bugs/Responses#head-20ebac8207b4398d32f955193ac904e3c4228dea
[02:26] <pedro_> there's one there
[02:26] <pedro_> exactly
[02:26] <greg-g> :)
[02:27] <sectech> ..... lol.... okay I think that's a hint to call it a day for this lol...
[02:27] <sectech> It was right in front of me
[02:28] <greg-g> there are a lot of responses on that page, easy to miss some (I do when I even know it is there somewhere)
[02:28] <sectech> It's very helpful though...
[02:29] <pedro_> bdmurray: this user is doing spam on some bugs https://bugs.edge.launchpad.net/~balaji-ramasubramanian
[02:29] <pedro_> selling computers
[02:30] <pedro_> an ps3 mm man i'd love to have a ps3
[02:30] <pedro_> anyways, is there something we can do about?
[02:30] <secretlondon> I want an eee myself
[02:30] <sectech> pedro_, we have a PS3...  The new grand theft auto is awesome :)
[02:30] <pedro_> niice
[02:30] <greg-g> pedro_: looks like it might be unintentional
[02:31] <greg-g> pedro_: the spam that is
[02:31] <pedro_> greg-g: on 3 bugs?
[02:31] <secretlondon> I think it needs manual intervention from a launchpad admin, I think they are on #launchpad
[02:31] <greg-g> there are all 3 bugs he has been actively involved with
[02:31] <greg-g> like a spam program got a hold of his contacts list
[02:31] <greg-g> s/there are/they are
[02:32] <secretlondon> it's email spam certainly
[02:32] <mcisbackuk> Does anyone have any idea on bug #228491
[02:32] <pedro_> ok will send him an email just in case
[02:33] <greg-g> pedro_: you can probably safely remove the comments or whatever, just maybe wait on deactivating his account
[02:33] <secretlondon> yeah he has contributed things other than spam
[02:33] <mcisbackuk> It's my bug in case anyone's wondering, I really need help setting this up, I've tried other rooms, but I assumed since you guys practically write these things....
[02:33] <pedro_> yeah, will contact him maybe he's not aware of the issue
[02:33] <secretlondon> and there are some windows spam viruses going around
[02:34] <secretlondon> mcisbackuk, I think that's the kernel, which should be the same
[02:34] <secretlondon> which driver do you get instead? (and it's all the same machine, right?)
[02:34] <mcisbackuk> secretlondon: I haven't had a problem before, I was using Ubuntu Hardy, not 2 hours ago, it was perfectly fine...
[02:35] <mcisbackuk> ermmmm.....fglrx but its not configured in the xorg.conf file, and since I don't know how to rewrite it to work I'm here for help, and to say its a bug
[02:36] <secretlondon> mcisbackuk, https://wiki.ubuntu.com/X/Debugging
[02:36] <secretlondon> xorg.conf is now really minimal and doesn't help much
[02:36] <secretlondon> I'll add a comment to the bug
[02:37] <mcisbackuk> Yeah I just looked at xorg.conf....pretty blank...
[02:38] <secretlondon> mcisbackuk, I've just asked for 3 bits of info on the bug
[02:38] <mcisbackuk> OK, I'll try to provide them
[02:41] <mcisbackuk> secretlondon: Updated and all attached
[02:41] <secretlondon> ty
[02:43] <RAOF> mcisbackuk: That Xorg.0.log looks like everything's working fine.
[02:44] <secretlondon> yeah it has RADEON in it
[02:44] <RAOF> It's using the open source drivers, which provide 3D etc.  If you have the fglrx drivers installed as well that may cause problems, but it looks fine from here.
[02:44] <mcisbackuk> RAOF: I thought so, its just really strange the CU usgae is constantly at 100% or close to, and Second Life doesn't draw properly, its using the CPU instead of the card...
[02:44] <RAOF> mcisbackuk: I'm going to guess that you've got
[02:44] <secretlondon> mcisbackuk, cpu usage at 100% could be all sorts of things
[02:44] <RAOF> the xserver-xgl package installed, right?
[02:44] <secretlondon> and that'll be an SL option somewhere
[02:44] <mcisbackuk> hang on...
[02:46] <mcisbackuk> xserver-xgl not installed, and SL worked perfectly fine default settings etc etc in Ubuntu 2 1/2 hours ago....this Xubuntu is a fresh install
[02:46] <secretlondon> mcisbackuk, check your SL preferences
[02:46] <RAOF> Ok, so it's probably not my fault then.  Good.
[02:47] <mcisbackuk> RAOF: Don't understand, is that one of yours then? lool
[02:47] <secretlondon> you prob do want the closed source driver though, if youare running 3d games
[02:47] <RAOF> Other things to check would include: what is it that's using up 100% cpu - the system monitor, htop, or top will be useful there.
[02:47] <RAOF> secretlondon: Does the closed driver even support the 9200 still?
[02:47] <RAOF> secretlondon: I know the latest fglrx dropped support for quite a lot of cards.
[02:48] <secretlondon> RAOF: no idea, I don't speak 'radeon' tbh
[02:49] <mcisbackuk> RAOF: I did run top, and 99% usage was for SL, and ummm fglrx I assumed was still supporting the 9200, like I say it was fine in Ubuntu, or was that a different one I was using?
[02:49] <RAOF> mcisbackuk: Nope; fglrx only officially supports down to the 9500.
[02:49] <secretlondon> you are running fglrx as well?
[02:49] <RAOF> At least according to the text of the xorg-driver-fglrx package.
[02:49] <mcisbackuk> secretlondon: I'm not that well up on driver configs, how do I find out?
[02:50] <secretlondon> mcisbackuk, it wasn't in the log file i asked for
[02:50] <secretlondon> but you saw it in top?
[02:50] <mcisbackuk> secretlondon: The 99% usage for SecondLife in top yes
[02:50] <secretlondon> mcisbackuk, I would expect SL to be a resource hog
[02:51] <RAOF> mcisbackuk: 99% usage for SL seems perfectly normal to me; that's what you expect an OpenGL game to use.
[02:51] <secretlondon> running windowed may be better, and lower the graphics settings
[02:51] <RAOF> (Using 'game' in its loosest possible sense :P)
[02:51] <greg-g> heh
[02:51] <mcisbackuk> secretlondon: True but the card/OpenGL had proper problems 3D drawing it....again Ubuntu (more resources) no problem....
[02:51] <mcisbackuk> lol
[02:52] <secretlondon> mcisbackuk, I think SL brings in bits of gnome
[02:52] <RAOF> mcisbackuk: So your actual bug is that SL shows corrupted graphics on Xubuntu, yes?
[02:52] <sectech> lol....someone posted a bug report because there pogo games arn't working anymore.
[02:52] <sectech> hah
[02:53] <secretlondon> pogo games?
[02:53] <mcisbackuk> RAOF: Basically, yes. But I do believe its a driver problem of some sort, or X......since it was fine in Ubuntu.....makes sense to me anyway lol
[02:53] <RAOF> mcisbackuk: Oh, it may well be a driver problem; rendering issues often are.
[02:53] <sectech> secretlondon, It's an online game site... basically java driven...
[02:53] <secretlondon> sectech so an issue with our java support?
[02:53] <mcisbackuk> RAOF: Oh and it runs like real crap.......I know it lags sometimes but it was unreal, 4-5 fps if I was lucky.
[02:54] <secretlondon> I had horrible problems on my geforce 4 MX, just a blank screen in SL
[02:54] <maccam94> vpnc doesn't have ssl support compiled in. i'm trying to build it from source (with ubuntu's patches), right now i've got the upstream vpnc source and the diff file for ubuntu's build. how do i patch the original source?
[02:54] <sectech> secretlondon,  Yes it's a Java issue, I have no doubt about that at all... I just found it amusing that someone actually named pogo in a bug report
[02:54] <secretlondon> sectech we ask them to, when it's a website thing
[02:54] <mcisbackuk> God even I'm not that bad.................(he says)
[02:55]  * secretlondon points at all the horrible flash + firefox bugs
[02:55] <RAOF> mcisbackuk: So; everything looks good from what you've posted so far.  Can you run 'glxinfo'?  Does it say 'direct rendering: yes'?
[02:55] <mcisbackuk> what the hell..............>>>
[02:55] <mcisbackuk> The program 'glxinfo' is currently not installed.  You can install it by typing:
[02:55] <mcisbackuk> sudo apt-get install mesa-utils
[02:55] <mcisbackuk> bash: glxinfo: command not found
[02:56] <mcisbackuk> Methinks I'll install it
[02:57] <mcisbackuk> directrendering = no
[02:57] <mcisbackuk> pastebin it??
[02:57] <RAOF> Yup.
[02:57] <maccam94> mcisbackuk: sudo apt-get install ubuntu-desktop
[02:57] <maccam94> assuming you're using plain ubuntu
[02:57] <mcisbackuk> ubuntu-desktop?
[02:57] <secretlondon> maccam94, he's running Xubuntu
[02:57] <maccam94> oh
[02:57] <maccam94> xubuntu-desktop then
[02:57] <mcisbackuk> lol
[02:57] <RAOF> Oh, actually; can you do the same thing, but with a verbose debug variable set.
[02:57] <sectech> Night folks...
[02:57] <secretlondon> night sectech
[02:57] <maccam94> 'nite sectech
[02:58] <RAOF> WTF? I've got direct rendering?  Why is this picking up nouveau?
[02:58] <mcisbackuk> http://pastebin.com/m719ee95d
[02:58] <secretlondon> RAOF: my hardy install had VESA :(
[02:58] <mcisbackuk> was that for me RAOF? verbose thing?
[02:59] <secretlondon> segfault at the end
[02:59] <RAOF> mcisbackuk: Could you run "LIBGL_DEBUG=verbose glxinfo" and pastebin that?
[02:59] <mcisbackuk> sure
[02:59] <RAOF> Heh; that probably means you've got fglrx installed somewhere.
[02:59] <RAOF> Proprietary drivers have an annoying habit of hijacking libGL which causes all other drivers to lose the ability to do 3d.
[03:00] <mcisbackuk> http://pastebin.com/ma9a0a6b
[03:00] <mcisbackuk> OK, well if thats the case....it was default install btw
[03:01] <secretlondon> #
[03:01] <secretlondon> libGL: OpenDriver: trying /usr/lib/dri/r200_dri.so
[03:01] <secretlondon> #
[03:01] <secretlondon> libGL error: dlopen /usr/lib/dri/r200_dri.so failed (/usr/lib/dri/r200_dri.so: undefined symbol: _glapi_Dispatch)
[03:01] <secretlondon> #
[03:01] <secretlondon> libGL error: unable to load driver: r200_dri.so
[03:02] <RAOF> So, there's the problem.
[03:02] <mcisbackuk> Means nothing to me, being honest.
[03:03] <secretlondon> mcisbackuk, don't worry. just picking out the nasties from the log
[03:03] <RAOF> mcisbackuk: Do you have a /usr/lib/libGL.so.1 file?
[03:03] <mcisbackuk> 1 sec..
[03:04] <RAOF> That _should_ be equivalent to having libgl1-mesa-glx installed.
[03:04] <mcisbackuk> I have a "file" yes
[03:06] <mcisbackuk> libgl1-mesa-glx IS installed, yes
[03:06] <RAOF> Hm.  Do you have a nice, high bandwith connection?  If so, I'd suggest reinstalling the mesa 3D stack with "sudo aptitude reinstall ~nmesa"
[03:06] <mcisbackuk> RAOF: I do yeah
[03:06] <RAOF> That'll reinstall every package that has 'mesa' in the name.
[03:07] <mcisbackuk> RAOF: And that will sort me out?
[03:07] <RAOF> mcisbackuk: Hopefully, yes.
[03:07] <RAOF> Basically, it might, and it shouldn't take very long with a high-bandwidth connection, so it's worth trying.
[03:08] <mcisbackuk> OK, ermmm......is this still a bug then, I mean will you need me again for more input on launchpad?
[03:08] <mcisbackuk> Obviously if I can I will help
[03:08] <RAOF> If this works, then it's probably not a bug, at least not an obvious one.
[03:09] <mcisbackuk> OK so that last bit it tilde n mesa right? ~nmesa
[03:09] <RAOF> Yeah, the ~n bit is 'match by name' to aptitude.
[03:09] <mcisbackuk> ahhh ok :)
[03:10] <mcisbackuk> **** how much does it wanna download! lol
[03:10] <mcisbackuk> .....he says.....its done
[03:10] <RAOF> Quite a bit; that's your whole 3D stack right there :)
[03:10] <mcisbackuk> restart X?
[03:10] <RAOF> You shouldn't have to.
[03:10] <RAOF> Do the glxinfo fandango again.
[03:11] <mcisbackuk> same...directrendering=no and seg fault at end
[03:11] <RAOF> Ok.  So something weird is happening.
[03:12] <mcisbackuk> You want another verbose paste?
[03:12] <RAOF> Does 'grep glapi_Dispatch /usr/lib/libGL.so.1' return any output?
[03:12] <mcisbackuk> Nope
[03:13] <RAOF> Can you post the output of "ls -lah /usr/lib/libGL*" ?
[03:13] <RAOF> That'll probably want to be pastebinned.
[03:13] <mcisbackuk> lol will do :0
[03:13] <mcisbackuk> :)
[03:14]  * RAOF is confused.  _His_ libGL has that symbol.
[03:14] <mcisbackuk> http://pastebin.com/m37c744cf
[03:14] <mcisbackuk> so=symbol then (am learning)
[03:15] <RAOF> so = shared object (what windows calls a DLL).
[03:15] <RAOF> The symbol is the name of the function in that shared object.
[03:15] <mcisbackuk> shared library thing....yup i get ya
[03:16] <mcisbackuk> Lets be clear though.....I hate indo$e with a passion lol linux for 2 years so far ;0
[03:16] <mcisbackuk> :)
[03:17] <RAOF> Can you pastebin the output of libgl1-mesa-glx?
[03:17] <mcisbackuk> 1 se
[03:17] <mcisbackuk> c
[03:19] <mcisbackuk> bash: libgl1-mesa-glx: command not found
[03:20] <mcisbackuk> only 1 line didnt see the point of paste binning it
[03:20] <RAOF> Ahem.  Whoops :)
[03:20] <RAOF> ...the output of apt-cache policy libgl1-mesa-glx :)
[03:20] <mcisbackuk> lol :)
[03:21] <mcisbackuk> http://pastebin.com/m45a4dd58 there you go
[03:22] <RAOF> mcisbackuk: And "grep glapi_Dispatch /usr/lib/libGL.so.1.2" _really_ gives no output?  It doesn't say "Binary file <foo> matches"?
[03:23] <mcisbackuk> Nope nothing at all, just the next # prompt
[03:24] <RAOF> Something's seriously broken, then.
[03:24] <mcisbackuk> Well would it be easier if I tell you exactly what I've done since install?
[03:24] <RAOF> I have the same package version installed, and my version has that symbol.
[03:24] <RAOF> mcisbackuk: Maybe.  Go for it.
[03:26] <secretlondon> I'm actually getting a similar response on my box
[03:26] <mcisbackuk> Fresh format/install dual boot with XP, installed OOo, Software Sources, checked all uypdate repositories, including backports and proposed, updated, didn't work before or after updates, downloaded/installed Second Life, created symlink Launcher on desktop.....nothing out of the ordinary
[03:26] <mcisbackuk> Thank god I'm not going mad lol
[03:26] <secretlondon> apt-cache says installed, grep no such file, libgl- command not found
[03:27] <secretlondon> I'm running nvidia
[03:27] <RAOF> secretlondon: Oh, that's fine.  You don't have mesa's libGL anyway.
[03:27] <mcisbackuk> Not just an ATI problem then?
[03:27] <secretlondon> RAOF: ok phew!
[03:28] <RAOF> secretlondon: Because, as I mentioned, the proprietary drivers _replace_ libGL to make life harder for everyone.
[03:28] <secretlondon> RAOF: thanks!
[03:28]  * secretlondon always learns loads on this channel
[03:28] <RAOF> Technically it's not to make life harder for everyone, it's because they don't want to use mesa's infrastructure.
[03:29] <RAOF> mcisbackuk: Do you have nvidia-glx installed?  Or xorg-driver-fglrx?
[03:29] <mcisbackuk> Checking...
[03:30] <RAOF> (Or nvidia-glx-legacy, -new, -envy, etc)
[03:30] <mcisbackuk> nvidia...nothing (i'm not that silly lol), xorg-driver-fglrx yes
[03:31] <RAOF> mcisbackuk: Right.  Uninstall xorg-driver-fglrx, and everything will work.
[03:31] <RAOF> I thought you didn't have taht installed :(
[03:31] <mcisbackuk> I didn't saay I had...... :S
[03:32] <mcisbackuk> fglrx-control to be removed as well, thats ok is it?
[03:32] <secretlondon> yeah
[03:33] <mcisbackuk> Done, X restart or will it be ok?
[03:33] <RAOF> You shouldn't need to restart X.
[03:33] <RAOF> Just run glxinfo again :)
[03:33] <mcisbackuk> OK
[03:33] <mcisbackuk> Yup, DX rendering = yes, no segfault
[03:34] <RAOF> Ding!  Everything will work smoothly now.
[03:34] <secretlondon> YAY
[03:34] <mcisbackuk> Isn't this still a problem for people with same card....I mean it was the default installation......
[03:34] <secretlondon> you def didn't install fglrx?
[03:34] <mcisbackuk> But thank you....very much appreciated :)
[03:34] <mcisbackuk> Nope 100%
[03:34] <mcisbackuk> Wouldn't even know why I'd bother lol
[03:35] <mcisbackuk> I _would_ format down and test that but I've got a few bits on here
[03:36] <RAOF> If fglrx is getting installed by default, that would be a bug.  But are you _sure_ you did'nt install fglrx?  Did you install fglrx-control?
[03:36] <mcisbackuk> No, didn't install either as far as I'm aware
[03:36] <mcisbackuk> Is there any log to check that?
[03:37] <RAOF> There's /var/log/dpkg.log, but that would require fairly careful reading.
[03:37] <RAOF> It's possible that these packages got pulled in by you accidentally while you were installing something else.
[03:38] <mcisbackuk> Surely should be able to do a mask search...I'm not worried about looking through it
[03:38] <mcisbackuk> Yeah, I guess it is possible, I am human
[03:38] <mcisbackuk> Oh hang on....
[03:39] <mcisbackuk> In the standard Add/Remove I DID install that ATI Catalyst Control Centre thing.....assuming I could easily control gamma, brightness etc as in Windows, hadn't seen it before on *buntu, could _that_ have a dependency for it?
[03:40] <RAOF> mcisbackuk: Yes.
[03:40] <mcisbackuk> Damn I must look so thick right now lol
[03:41] <RAOF> That's the fglrx-control package :)
[03:42] <mcisbackuk> Surely I'm not the only one whose done this though....but ermmm would it be possible to make a suggestion? Maybe have a warning type thing in the description in the debian/control file saying _do not install if you're stupid like me and have a Radeon 9500 or under_
[03:43] <RAOF> Hm.  Maybe.
[03:43] <mcisbackuk> Don't put my name on the stuid bit though :) lol
[03:46] <RAOF> So, tecnically, you need to be using the fglrx driver before that package will do anything at all.  And it will install the fglrx package automatically, but not set it up, so just installing that package will a) Not work, and b) break your 3d.
[03:46] <mcisbackuk> I'll be honest - people seeing "Control panel for the ATI graphics accelerators Control panel for the ATI Radeon and FireGL graphics accelerators." might probably assume the same, maybe add an extra bit saying do not install if you do not have at least radeon 9500, or possibly get the installer to do a glxinfo and look to see if direct rendering is already on and if so deny the installer the ability to install it, wit
[03:46] <RAOF> This is sub-optimal.
[03:46] <mcisbackuk> I see what you mean
[03:46] <mcisbackuk> Basically it tells it to use a driver that isn't there, hence the break?
[03:47] <RAOF> Well, no.  It installs the fglrx driver, which breaks all other 3d on the system.
[03:47] <mcisbackuk> Ahh right
[03:47] <RAOF> IE: when fglrx is installed, only the fglrx driver can do 3d.
[03:47] <mcisbackuk> Kind of an override?
[03:47] <RAOF> (People not-infrequently break their 3d by installing nvidia-glx, too)
[03:48] <RAOF> mcisbackuk: Exactly.  It replaces libGL (which is what your problem was) with a version that only works with fglrx.
[03:48] <mcisbackuk> Ahhhhhhhhh....makes sense now
[03:48] <mcisbackuk> :)
[03:48] <RAOF> The nvidia driver does exactly the same thing.
[03:48] <RAOF> So _installing_ either of them will break your 3d.  (This has the corollory that you can't have 3d with an nvidia card and any other card at the same time).
[03:49] <mcisbackuk> fglrx is only for the beefier cards then I take it?
[03:49] <mcisbackuk> Hmm...
[03:50] <mcisbackuk> Shall I mark bug #228491 invalid then?
[03:50] <RAOF> mcisbackuk: Yeah.  I'll see what I can do about making fglrx-control less inticing :)
[03:50] <RAOF> fglrx will drive > 9500, and is the only 3d driver for > X850.
[03:51] <mcisbackuk> Brilliant! Thanks so much for the help...and teaching! Very much appreciated - hopefully I should be OK now bug-wise :) Thanks again
[03:52] <mcisbackuk> Goodnight all, I can sleep now!!
[03:54]  * secretlondon has been tempted to log in to sl for the first time in years
[03:54] <secretlondon> lol
[03:55] <secretlondon> I better close xchat really
[04:00] <techno_freak> :0
[05:43] <maccam94> for some reason ff3b5 is taking up 550mb of ram, with not a lot of stuff open...
[06:12] <mrooney> maccam94: quite strange, mine takes up less than a hundred at startup and scales quite reasonably
[06:13] <maccam94> yeah i've seen it stay in the 100-150 range most of the time
[06:14] <maccam94> i've only got 18 tabs open, no flash :-\
[06:34] <CarlFK> update broke my wifi: Atheros Communications Inc. AR242x 802.11abg
[06:34] <CarlFK> yay for the previous kernel: 2.6.24-12-generic
[09:54] <qense> hello
[10:01] <james_w> hi qense
[12:11] <askand> Hi, ﻿When I have firefox open and start rhythmbox and try to play a song it doesnt work. If I close firefox, play, and opens firefox after that it works..that is because of flash and pulseaudio I guess? Is there a bugreport about that?
[13:17] <kahrytan> How does X server get a list of available modes for a monitor?
[13:18] <kahrytan> And dont say EDID cuz that isnt true.
[13:18] <james_w> kahrytan: #ubuntu-x might have more people able to answer your question
[13:19] <kahrytan> there is far to many channels
[13:19] <kahrytan> Im still trying to figure out decent workaround for my bug
[13:20] <kahrytan> How does Screen Resolutions applet get it's mode list ?
[13:21] <james_w> asks the X server I presume
[13:21] <kahrytan> cuz it obviously gets it wrong
[13:21] <kahrytan> and detects my monitor incorrectly
[13:22] <afflux> morning
[13:22] <james_w> hi afflux
[13:22] <afflux> hi james_w
[14:44] <bddebian> Boo
[14:50] <ogra> bee
[15:03] <sectech> Hey could someone take a look at bug #226928 and provide me with some feedback...
[15:04] <sectech> I know the wireless button doesn't work in the same way as it does in windows,  but I think they intended it to be that wya
[15:04] <sectech> err way
[15:16] <sectech> Actually it's a dup never mind
[15:55] <ruiboon> Hi! When a bug has a Backtrace and Vlagrind logs attached, is it still considered as incomplete or confirmed?
[15:55] <ruiboon> though i cannot reproduce the steps
[15:55] <ruiboon> and yes. the steps to reproduce the bug has been given by the submitter
[15:56] <jeromeg> ruiboon: is the backtrace ok ?
[15:56] <jeromeg> or is it full of "??" ?
[15:56] <ruiboon> there are some "??"
[15:57] <ruiboon> jeromeg: does ?? means that the dbgsym has not been installed?
[15:58] <jeromeg> yes
[15:58] <jeromeg> could you give me a link to the bug ?
[15:58] <ruiboon> https://bugs.launchpad.net/ubuntu/+source/roxterm/+bug/227685
[16:00] <jeromeg> ruiboon: the backtrace is useless
[16:01] <jeromeg> all debugging symbols are missing
[16:01] <jeromeg> ruiboon: same thing for the valgrind log
[16:02] <ruiboon> hmm.. then do i still ask the submitter to install the relevant dbgsym or make it as other status?
[16:03] <jeromeg> move the bug as incomplete
[16:03] <jeromeg> oh it is already ;)
[16:03] <ruiboon> given that the submitter has should have installed the correct dbgsym as mentioned in one of the post
[16:03] <jeromeg> just ask to ask the debugging symbols and to reprovide a backtrace and a valgrind log
[16:03] <jeromeg> ruiboon: ;)
[16:04] <jeromeg> ruiboon: you could also tell him not to send tarballs
[16:04] <jeromeg> just the plain text files
[16:04] <ruiboon> noted that
[16:04] <ruiboon> guess that plain text files are easier to work with
[16:04] <jeromeg> yep
[16:05] <jeromeg> it's a pain to download the tarball and then to open the files
[16:05] <jeromeg> and copressing text files won't save much space
[16:08] <ruiboon> jeromeg: there is also another question that i would like to ask re another bug.
[16:08] <jeromeg> go on
[16:08] <ruiboon> jeromeg: this time round, the bug is reproduceable on my end
[16:08] <jeromeg> link ?
[16:09] <ruiboon> https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/227747
[16:09] <ruiboon> did a backtrace, and the ?? seems to belong to flashplugin-nonfree.
[16:10] <ruiboon> others dbgsym are install. just could not find one for the flashplugin
[16:10] <ruiboon> does the backtrace suggest that the fault lies within flashplugin or firefox?
[16:11] <jeromeg> ruiboon: the mozilla team has a very particular procedure to triage bug
[16:11] <maccam94> ff3b5 is currently using 70% of my 1GB of ram... WTH
[16:11] <jeromeg> ruiboon: you should read https://wiki.ubuntu.com/MozillaTeam/Bugs and https://wiki.ubuntu.com/MozillaTeam/Bugs/Procedures
[16:13] <ruiboon> jeromeg: reading them now.....
[16:13] <jeromeg> great
[16:14] <ruiboon> jeromeg: ".. when you have a testcase ...  but since you might not be really sure if a bug is complete now ... you tagg it mt-confirm and keep it in incomplete state..."
[16:14] <ruiboon> jeromeg: so that means i leave it at incomplete stage and tag is as mt-confirm?
[16:14] <jeromeg> ruiboon: yep
[16:15] <ruiboon> jeromeg: ok. Thanks for helping me to understand even more abt the debugging procedure!
[16:15] <jeromeg> ruiboon: you can go to #ubuntu-mozillateam to ask them about more details
[16:16] <jeromeg> ruiboon: np
[16:16] <ruiboon> ruiboon: thanks for the reference
[17:11] <ruiboon> when the backtrace does not give relevant information, i.e. "??" exists, even though <package>-dbgsym is installed, how should we proceed from here?
[17:12] <ruiboon> currently leaving it at incomplete
[17:17] <james_w> ruiboon: can you give the bug number please?
[17:18] <ruiboon> james_w: LP: #227685
[17:18] <james_w> bug 227685
[17:18] <james_w> thanks ubottu
[17:19] <ruiboon> oo. didn't realise that it should be typed like that
[17:21] <ruiboon> james_w: installed roxterm-dbgsym and did the backtrace. "??" still present. http://paste.ubuntu.com/11138/
[17:22] <james_w> ruiboon: the valgrind log looks ok
[17:22] <james_w> ruiboon: sometimes it's just impossible to get anything useful out of gdb, for instance corrupted stacks.
[17:23] <james_w> "Access not within mapped region at address 0x0"
[17:23] <james_w> it's passing NULL to dbus or something I expect.
[17:24] <ruiboon> james_w: that could be one possibility.
[17:25] <ruiboon> james_w: should i tag it as confirmed now? given that the valgrind log is ok
[17:25] <james_w> ruiboon: have you reproduced it?
[17:25] <emgent> heya
[17:26] <emgent> bdmurray: hi :)
[17:26] <ruiboon> james_w: could not reproduced it on a fresh installation of the package
[17:26] <ruiboon> james_w: and following the submitter testcase
[17:27] <emgent> mdz: cool dance with fabbione :)
[17:27] <emgent> http://www.youtube.com/watch?v=DQ113000uQg hehehhe
[17:27] <emgent> bdmurray: ping
[17:28] <bdmurray> emgent: I've a meeting shortly, what is up?
[17:32] <james_w> ruiboon: is roxterm single instance?
[17:32] <emgent> bdmurray: can you review my expire day in bugcontrol team?
[17:32] <ruiboon> james_w: single instance as in...?
[17:33] <emgent> (when you have time and if it`s possible) :)
[17:33] <james_w> ruiboon: run "roxterm" and then open another terminal and run "roxterm -d /usr"
[17:33] <james_w> ruiboon: so, please go ahead and set it to confirmed.
[17:34] <james_w> ruiboon: it's doing something silly when there is already another instance.
[17:34] <ruiboon> james_w: Segmentation fault on the second one
[17:34] <ruiboon> james_w: got it. Thanks!
[17:34] <james_w> no problem
[19:54] <sectech> That's odd... a bug has been marked as a duplicate, yet I get an access error when trying to reference that bug
[19:55] <sectech> bug #228014... I can't see it's duplicate
[19:55] <sectech> .... well there is my answer...
[20:02] <bdmurray> sectech: I've unprivatized that bug
[20:03] <sectech> Thank you...
[20:04] <greg-g> dang privatization of bugs, always causing more problems than its worth

[20:04] <bdmurray> hi greg-g
[20:05] <greg-g> heya bdmurray
[20:06] <sectech> It still says I don't have permission to access that page
[20:06] <greg-g> sectech: just to be safe, go to the link that ubottu just provided, that still doesn't work?
[20:07] <bdmurray> bug 228014
[20:07] <greg-g> eh?
[20:07] <sectech> 228014 I can access
[20:07] <sectech> bug #228385 is the one I want
[20:08] <sectech> bug 228385
[20:08] <sectech> whoops.. lag
[20:08] <greg-g> ahhh
[20:08] <bdmurray> okay fixed
[20:08] <sectech> Can the reporter set the privacy of his/her own bug?
[20:09] <bdmurray> sectech: yes, but this is an apport crash which by default is private
[20:09] <sectech> ahh... possible sensitive information.... I understand
[20:09] <greg-g> so they would have to notice that it is private and then open it up, yeah
[20:10] <greg-g> or, a bugcontrol team member can open it up/check it for sensitive info if you ask (like you did)
[20:10] <bdmurray> The quantity of private bug reports should be close to 0
[20:10] <greg-g> surprising that the bug had 22 dups yet was still private
[20:11] <greg-g> although, do private bugs show up in the "your bug looks a lot like these..." page in LP?
[20:11]  * greg-g wouldn't know how to test that without creating some fake bugs
[20:12] <secretlondon> aport does auto duping
[20:13] <sectech> The bug I am triaging is 228492... I don't have enough information to mark it as a dup though.
[20:13] <sectech> I mistakenly marked it as confirmed then saw it has little to no information to go with it even after my request...
[20:13] <greg-g> sectech: yeah, I mean some people actually don't add their new apport bug when they see that it has already been reported, instead they just subscribe
[20:13] <greg-g> erm, that was supposed to be to secretlondon
[20:14] <greg-g> secretlondon: so, I was thinking that the reason it has such high number of dups is because the master didn't show up in the list of "are you sure your bug isn't any of these?"
[20:15] <sectech> I'm taking on the approach that I would rather try and re-create it myself first before asking for backtraces... If I can recreate it I would sooner just do it myself
[20:15] <secretlondon> greg_g if it's an apport crash then people generally submit them (which I think is correct) and apport dupes them when it retraces
[20:16] <greg-g> right, but I know sometimes I don't submit known dups through apport and just subscribe instead
[20:16] <secretlondon> I'd rather have more apport data than less, and foo crashes could be caused by multiple things
[20:16] <greg-g> right
[20:16]  * greg-g agrees
[20:16] <secretlondon> only the retrace will tell us if it's the same
[20:16] <greg-g> I should know better than to assume the bug reporters are looking deeply into whether their bug is a dup or not like we do :)
[20:17] <secretlondon> for apport I _always_ submit myself, as I want to see the retrace
[20:18] <secretlondon> but it looks like most of those dupes are done by apport
[20:18] <greg-g> yeah
[20:18] <secretlondon> which is cool
[20:19] <secretlondon> and there's a lot of them :(
[20:23]  * greg-g goes to the pub for "Friday Beer"
[20:24] <secretlondon> :)
[20:35] <bdmurray> sectech: that seems to be a dup of bug 227717
[20:37] <sectech> bdmurray, It might be...  Do you think there is enough info provided by the original reporter?
[20:38] <bdmurray> I was referring to bug 228385
[20:39] <sectech> I wasn't able to look at the original bug though to verify it against before.... Yes this one does
[20:40] <sectech> Do you want to mark it, or do you want me to?
[20:40] <bdmurray> We don't have enough information to verify that bug 228492 is a dup but I'd put money on it.
[20:40] <sectech> oooh... a betting man :P
[20:41] <sectech> It probably is...
[20:42] <Mactaylor> why is there a bug about JFS failing to boot with grub?
[20:42] <sectech> bug #?
[20:43] <Mactaylor> 1 sec
[20:44] <Mactaylor> https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/14010
[20:44] <Mactaylor> it boots for me
[20:45] <sectech> Mactaylor,  That bug was in relation to a alpha or beta iso
[20:46] <sectech> not the final release.
[20:46] <Mactaylor> ok
[20:46] <sectech> I'll add a note to the bug asking if the bug still happens on the final release
[20:47] <bdmurray> That was weird
[20:47] <sectech> Maybe he thought that the people in #ubuntu-bugs were the ones doing the bug reports :P
[20:48] <bdmurray> sectech: I think the bug is in a fine state as it is
[20:48] <sectech> I wasn't going to change it... I just added a note.
[20:50] <sectech> Pedro was involved with that one...  I won't change the status of bugs if other team members are involved without asking...
[20:50] <bdmurray> that's a different pedro
[20:51] <sectech> Okay well still lol.... plus the bug was created in 2005
[20:51] <sectech> brb supper.
[21:23] <sectech> back
[21:23] <sectech> A little KFC for a Friday evening.... nice
[21:37] <sectech> Can someone verify bug #228781
[22:05] <rio> https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/228154 -- anybody knows how to fix this? :(
[22:07] <bdmurray> Maybe look in /usr/share/hal/fdi/information/10freedesktop/10-camera-ptp.fdi
[22:08] <rio> what to look? :P
[22:10] <bdmurray> sorry try /usr/share/hal/fdi/preprobe/10osvendor/20-libgphoto2.fdi
[22:14] <rio> bdmurray: i think the file is fine
[22:14] <bdmurray> Is your camera in there?
[22:14] <rio> there a matching vendor and product id saying      <merge key="camera.access_method" type="string">ptp</merge>
[22:14] <rio> <merge key="camera.libgphoto2.name" type="string">Canon Digital IXUS 30 (PTP mode)</merge>
[22:15] <rio> but this one doesnt show up in f-spot/gthumb
[22:15] <rio> only the normale mode ones do
[22:17] <rio> http://rafb.net/p/dqMjSK64.html
[22:17] <rio> bdmurray: thats whats matching my camera
[22:18] <rio> should i try to comment the normal mode?
[22:18] <rio> maybe it fetches the first matching or sth like this?
[22:21] <rio> even if the normal mode is commented, it shows up
[22:25] <bdmurray> rio: I'm not quite certain how this it works in this case
[22:26] <rio> maybe i need to copy it to /etc/hal/fdi/preprobe or sth?
[22:26] <bdmurray> no, it is fine where it is
[22:28] <rio> is this cached anywhere?
[22:30] <bdmurray> How did you comment it out?
[22:32] <mrooney> bdmurray: did my reply to the bugcontrol list come through on whatever moderation test you are attempting? I notice it didn't make it to the list
[22:32] <mrooney> oh and, hello! :)
[22:32] <rio> bdmurray: i tried <!-- .. -->
[22:32] <rio> but now i even removed it
[22:35] <bdmurray> there seems to be a command line interface to gphoto2
[22:36] <bdmurray> gphoto2 --list-cameras shows normal mode as experimental
[22:36] <rio> ill install gphoto2
[22:36] <rio> yes its good to be experimental because it doesnt even work
[22:36] <rio> thats why i need ptp :)
[22:38] <rio> $ gphoto2 --auto-detect
[22:38] <rio> Modell                         Port
[22:38] <rio> ----------------------------------------------------------
[22:38] <rio> Canon Digital IXUS 30 (normal mode) usb:
[22:38] <rio> Canon Digital IXUS 30 (normal mode) usb:004,008
[22:40] <james_w> rio: did you unplug your camera after changing the file?
[22:41] <rio> im switching it off and an
[22:41] <rio> on
[22:42] <rio> gphoto2 -l --camera "Canon Digital IXUS 30 (PTP mode)"
[22:42] <rio> that works
[22:42] <rio> so the PTP-driver is fine
[22:42] <rio> but why isnt it used?
[22:53] <bdmurray> rio: I'm not certain but documenting what you've found in the bug report would be helpful
[22:53] <rio> ill do
[23:01] <rio> okay, updated the report
[23:01] <rio> bdmurray: thanks so fae
[23:02] <rio> far
[23:16] <rio> i think i found the wrongdoer