[00:02] <mrooney> james_w: well now I have been unable to resist giving ubuntu-wallpapers a hug. I see you Confirmed bug 198563, but I can't figure out where they are called "Simple Ubuntu"
[00:03] <james_w> I remember confirming it, let me look
[00:04] <james_w> yeah, still present
[00:04] <james_w> in the tooltips of the preview images
[00:04] <james_w> in "Preferences->Appearance"
[00:05] <mrooney> hmm, I don't notice that on Hardy, Elephant says "Elephant" but the Heron and the Heron-less both say "Ubuntu"
[00:05] <james_w> I can't see where it's set in the package though
[00:06] <mrooney> james_w: are you testing on Intrepid and noticing something different from me?
[00:06] <james_w> I'm on Intrepid
[00:06] <mrooney> oh okay, so to clarify the bug isn't that two things have the same name, but that Elephant is improperly named, right?
[00:07] <james_w> and have "Ubuntu" for plain brown, and "Simple Ubuntu" for the heron and elephant
[00:07] <james_w> I think they are all misnamed
[00:07] <mrooney> I would think the plain brown and heron should be swapped
[00:07] <mrooney> yeah haha
[00:11] <mrooney> james_w: still looking for it in the package? or gave up?
[00:11] <james_w> I was looking at something else for a minute
[00:11] <james_w> I had pretty much given up
[00:11] <mrooney> can I apt-get source for Intrepid on Hardy?
[00:11] <james_w> know of a way to extract metadata from .png files?
[00:11] <james_w> mrooney: yeah, add an Intrepid deb-src line
[00:11] <bdmurray> strings!
[00:12] <james_w> not so good on .png apparently :-)
[00:13] <james_w> mrooney: apt-get source will always pull from Intrepid then. You can override with e.g. "apt-get source ubuntu-wallpapers/hardy" I believe
[00:16] <mrooney> james_w: something like "deb-src http://archive.ubuntu.com/ubuntu/ intrepid main restricted" ?
[00:17] <james_w> I think that's right
[00:18] <bdmurray> mrooney: that's correct
[00:18] <bdmurray> james_w: actually I think pkgname/release is broken
[00:19] <bdmurray> however you can do pkgname=versionnumber
[00:25] <mrooney> james_w: it's right in ubuntu-wallpapers.xml.in :]
[00:25] <mrooney> I think anyway, it mirrors what I see in Hardy, though it should have pulled the intrepid version I would expect...
[00:26] <james_w> it's not what's in my /usr/share/gnome-background-properties/ubuntu-wallpapers.xml though
[00:26] <james_w> I have Ubuntu/Ubuntu/Elephant there
[00:26] <mrooney> yeah that is what my xml.in looks like here
[00:27] <mrooney> did I not grab the Intrepid source maybe?
[00:28] <james_w> yeah, it's just not what I see in the tooltips
[00:32] <mrooney> oh, they match up on Hardy for me, hrmph
[00:32] <mrooney> if my Intrepid install wasn't so sketchy I'd just try it :)
[01:17] <emet> sometimes people submit nonsensical or hard to understand bug reports, is there any way to handle these?
[01:19] <hggdh> emet, try to understand and, of course, ask for clarification ;-)
[01:20] <hggdh> what is the bug?
[01:22] <emet> bug 268758
[01:22] <emet> I fixed the spelling in the subject
[01:22] <emet> that's okay right?
[01:23] <Hobbsee> take them out the back of the parking lot and enlighten them....
[01:23] <Hobbsee> ahem!
[01:24] <Hobbsee> emet: do we distribute vmware-workstation?
[01:24] <emet> I don't think so
[01:25] <emet> I really doubt that's what it crashed though
[01:26] <Hobbsee> hmmm
[01:26] <Hobbsee> the retracer might come up with something.
[01:28] <mrooney> hm, bug 268784 is interesting
[01:30] <Hobbsee> interesting...
[01:30] <Hobbsee> Fetched 33.9MB in 54s (621kB/s)
[01:30] <Hobbsee> Extracting templates from packages: 100%
[01:30] <Hobbsee> E: Sub-process /usr/bin/dpkg returned an error code (2)
[01:30] <Hobbsee> yet trying it again works fine.
[01:55] <kees> sbeattie: have you been involved in the hardy kernel SRUing?  I'm trying to figure out how close the -proposed kernel is to getting published.
[01:56] <sbeattie> kees: not really, I tested one item.
[01:57] <kees> sbeattie: okay, I'll go ask the kernel folks
[02:00] <bcurtiswx> Bug Control: Bug 268795 needs to be marked wishlist
[02:01] <bcurtiswx> thank you
[02:04] <mrooney> bcurtiswx: okay, looks reasonable, done!
[02:05] <bcurtiswx> mrooney: ty :-)
[02:08] <bcurtiswx> mrooney, i grew up in greece.  just read you go to RIT.
[02:11] <mrooney> bcurtiswx: oh neat! indeed
[02:11] <mrooney> where are you now?
[02:13] <bcurtiswx> mrooney, i graduated from SUNY Oswego, now im a Computational Science Grad student at george mason uni in VA
[02:19] <mrooney> bcurtiswx: oh that sounds exciting. using your education to help out ubuntu as well, apparently?
[02:21] <bcurtiswx> that is correct.  Goal is to become an ubuntu member
[02:22] <mrooney> nice, good luck!
[02:27] <bcurtiswx> thank you!
[02:28] <hggdh> hum. bug 268784 is actually a good idea, at least on the first part
[02:29] <hggdh> so is bug 268791, by the same reporter
[02:30] <hggdh> I crossed by the reporter on bug 120527, BTW
[02:31] <mrooney> hggdh: yeah, they are more meta bugs like, how bugs should be filed, I wonder what we should do with them
[02:31] <bcurtiswx> i've wondered the same thing
[02:32] <hggdh> so do I, so do I... perhaps a good idea is to circulate them to the bugsquad/bug-control lists
[02:32] <bcurtiswx> whats the bugsquad list, i've been meaning to subscribe
[02:32] <hggdh> part is under our (theoretical) umbrella, part is LP
[02:33] <hggdh> these are the mailing lists we use to discuss bug work
[02:33] <bcurtiswx> sorry, i meant whats the website to subscribe
[02:33] <bcurtiswx> :-X its late and my brain has stopped on my
[02:33] <hggdh> https://lists.ubuntu.com/
[02:33] <bcurtiswx> me*
[02:33] <hggdh> bcurtiswx, ^^
[02:34] <bcurtiswx> thank you hggdh :)
[02:34] <hggdh> welcome
[02:35] <hggdh> BTW -- if any of you deal with mathematics, Sage is a cool system
[02:35] <mrooney> hmm bug 268800 confuses me as kmenuedit doesn't seem to be a package in Intrepid
[02:35] <mrooney> can anyone enlighten me?
[02:36] <Hobbsee> mrooney: it's part of kdebase / libs / one of them.
[02:36] <Hobbsee> or, used to be, anyway.
[02:37] <hggdh> seems to be there, per dpkg -S
[02:37] <hggdh> kdebase-workspace-bin
[02:38] <mrooney> Hobbsee: hmm...searching for it on packages.ubuntu.com only shows up to Hardy
[02:38] <Hobbsee> ah yes, the kde4-based names changed.
[02:38] <Hobbsee> mrooney: it changed names, as did lot of kde's stuff, with the 3-->4 transition.
[02:38] <hggdh> which made me rather confused...
[02:39] <Hobbsee> hggdh: tell me about it...i didn't help package it for a very good reason ;)
[02:41] <mrooney> hggdh: ah, are you saying the new name is kdebase-workspace-bin?
[02:41] <mrooney> of kmenuedit
[02:42] <hggdh> mrooney, correct for kde4
[02:49] <mrooney> it seems like the packages list should inform me of that
[02:51] <bcurtiswx> is rmadison a really useful tool?
[02:51] <hggdh> what we should do is build is a database with all of that, and give it a web interface, so you could search similar to apt-cache search (and really get results)
[02:51] <hggdh> bcurtiswx, if you are looking for a package, and you know the correct name of the package, yes
[02:52] <hggdh> OTH, if you do *not* know the package name, it is worth nothing
[02:53] <bcurtiswx> haha, i figured that out
[02:53] <bcurtiswx> if only they'd build in a wild card selection
[02:53] <bcurtiswx> like virtualbox* for example
[02:55] <hggdh> mrooney, 'whereis kmenuedit', followed by 'dpkg -S' on the result
[02:56] <Hobbsee> bcurtiswx: YES!
[02:56] <Hobbsee> (as for rmadison being useful
[02:56] <Hobbsee> )
[02:57] <persia> mrooney: Alternately, you can shortcut it for an executable with `dpkg -S $(which kmenuedit)` (not that kmenuedit is necessarily an executable, but it is sometimes faster than going through possibly many whereis entries
[02:58] <hggdh> yes, much simpler. Even better cuz 'which' will work on the current path, while 'whereis' has a hardcoded path (if I remember correctly)
[03:00] <persia> hggdh: whereis is hardcoded, but it also searches for things that aren't binaries, which can be useful in some cases.
[03:01] <mrooney> hi persia! medium-time no see!
[03:01] <persia> locate is even more powerful: assuming it's been installed overnight, it can find anything anywhere by name (and doesn't take anything like the time required for the newer indexers that care about things like file content or file type)
[03:02] <persia> mrooney: Hi.  I've been busy, but had a bit of time now, and thought I'd comment :)
[03:06] <mrooney> oh I didn't mean to imply you were gone, just that I haven't seen you, I guess we've both been busy :)
[03:06] <hggdh> persia, wasn't locate taken out of standard installs?
[03:08] <Hobbsee> hggdh: slocate changed to mlocate, on desktops, and got deleted on servers, iirc?
[03:08] <persia> hggdh: Plus, mlocate is easy for triagers to install, and is a handy tool.
[03:09]  * persia uses locate all the time when which isn't enough to track down the right package for a bug
[03:10] <persia> I also find `grep -r $(name) /usr/share/applications/` to be useful when a submitter reports the name of the menu item, but that doesn't happen to match a package name.
[03:10] <mrooney> I only have used locate to find files on my computer
[03:11] <persia> That finds out which .desktop file defines the menu entry, and one can then use dpkg -S to find the package responsible.
[03:11] <persia> mrooney: If you know the command line, which is usually a bit faster, as it only has to search the current $PATH, rather than the filesystem contents index.
[03:11] <persia> (mind you, both are typically fast enough not to really notice)
[03:13] <hggdh> Hobsee, yes, this sounds, on my meager memory, more like it... thanks
[06:32] <Hew> Hey guys. My ubuntu-bugcontrol subscription is due to expire in seven days. Can someone renew this for me?
[06:36] <persia> Hew: You need to catch one of bdmurray, heno, pedro, jorge, or ogasawara.  I'd recommend trying on the other side of the day, as this tends to be a time that none of them are about (although there are exceptional days)
[06:38] <Hew> persia: No worries, I'll ask again later tonight :-)
[07:09] <dholbach> good morning
[07:11] <maco> dholbach: hola
[07:11] <dholbach> hiya mac
[07:11] <dholbach> maco!
[07:16] <Hew> Could someone look at bug #261685? The E100 supports ogg vorbis and flac, but when I transfer these files using rhythmbox, it turns them all into mp3. Is this the same bug, or a new one?
[07:24] <maco> dholbach: hew was asking for his bug control subscription to be renewed about a half hour ago, by the way
[07:24] <dholbach> maco: I'm not an admin of the team
[07:24] <dholbach> and as far as I know you can renew it yourself, can't you?
[07:24] <maco> oh sorry
[07:24] <maco> *shrug* i'm not on the team
[07:24] <dholbach> ... yet
[07:27] <Hew> I need to have the subscription renewed by an admin of the team. I'll ask again a bit later :-)
[07:31]  * maco thought dholbach was in the list persia mentioned
[07:33] <ogasawara> Hew: what's your launchpad id?
[07:33] <Hew> ogasawara: hew
[07:35] <ogasawara> Hew: ok, it should be renewed
[07:36] <ogasawara> Hew: I think you'll get an email in a sec
[07:36] <Hew> ogasawara: yep, it has been. Thanks a lot :-)
[11:04] <LimCore> recent kmail asks me each time for my passphrase to openpgp... this is really bad... known problem?  Also, kmail seems to be riddled with other openpgp bugs I found... still :/
[11:04] <LimCore> https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/268925
[11:14] <persia> LimCore: likely an issue with your GPG agent, rather than with kmail: there've been a few reports of problems with agents in intrepid.
[11:15] <LimCore> Im using 8.04
[13:26] <Pres-Gas> https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/252174
[13:27] <Pres-Gas> Why is there soooooo many duplicates on this?  I am getting mail bombed.
[13:28] <Hew> Pres-Gas: It affects a lot of people. Unsubscribe if you don't want to receive mail about it.
[13:28] <Pres-Gas> One of the mailings is has a subject line regarding ati catalyst video driver
[13:29] <Pres-Gas> I am fine with getting it if the subject line of all of them stayed the same...I was afraid something was amiss.
[13:30] <Hew> Pres-Gas: Sebastien regularly cleans up all the dupes. If it's marked as a duplicate, then it's safe to say it's the same issue.
[13:32] <Hew> Pres-Gas: If you are referring to bug 258720, just look at the bug description and the stacktrace. It's pretty clear it's the same issue.
[14:06] <mrooney> Hmm, what interesting definition of a day 5-a-day has. Does anyone know the day cutoffs in GMT?
[14:52] <abby87> sleep event is there in acpi right? or acpi-support?
[15:03] <bddebian> Boo
[15:03] <jjesse> don't cry i didn't mean to scare you :)
[15:05] <bddebian> :)
[15:47] <jwendell> hi, pedro_
[15:48] <pedro_> hey jwendell, how's going?
[15:48] <pedro_> jwendell: going to latinoware?
[15:48] <jwendell> pedro_, yep, and about you?
[15:48] <pedro_> i think so yep, just waiting for izabel to confirm some dates
[15:49] <jwendell> pedro_, the forum is from oct-30 until 01-nov
[15:52] <jwendell> pedro_, why a crash should have a valgrind log when it already has a good backtrace?
[15:52] <pedro_> jwendell: right, but in the email izabel sent us she said that we could arrive there the 28/29 so i'm asking here the right dates for that in order to ask for a couple of days at the job
[15:53] <pedro_> jwendell: well for example if the crash is related to a memory allocation it should have a valgrind log to see what's causing that issue
[15:54] <pedro_> valgrind helps better there, gdb doesn't really show anything
[15:54] <jwendell> pedro_, you just closed a bug even without ask upstream...
[15:54] <pedro_> jwendell: number?
[15:54] <jwendell> https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/257371
[15:55] <pedro_> jwendell: well that's correct i did closed that because we indeed need a valgrind log as Seb asked you
[15:56] <pedro_> jwendell: you can take the bug upstream if you want to but they probably are going to ask you for the same info
[15:56] <jwendell> pedro_, ok, my doubt is: Why asking for a valgrind log even if you're not sure the cause of the problem
[15:57] <jwendell> it makes the life of bug reporters too much difficult
[15:57] <pedro_> jwendell: so what can we do ? just close them?
[15:57] <jwendell> pedro_, forward it upstream and let developers decide if they want valgrind log
[15:58] <pedro_> if you can reproduce it that's ok if it happens again and you likely know how to reproduce it please get a valgrind log
[15:58] <pedro_> jwendell: alright , you're welcome to do so ;-)
[15:58] <pedro_> but as said they are probably going to ask for the same info
[15:59] <seb128> what is the discussion about?
[15:59] <pedro_> seb128: bug 257371
[15:59] <pedro_> jwendell:  is asking why we ask for valgrind logs on memory corruption bugs
[16:00] <seb128> because stacktraces are not revelant usually when there is a corruption
[16:00] <pedro_> he thinks that upstream should decide if they want it or not and we should forward them anyways
[16:00] <pedro_> seb128: that's what i said
[16:00] <pedro_> s/it/if
[16:00] <seb128> no
[16:00] <seb128> that's a question of whether we want to throw everything at upstream or send them quality bugs
[16:01] <seb128> we decided to try having some quality there
[16:01] <jwendell> the question is:
[16:01] <seb128> jwendell: but nothing prevent you to forward your bugs on bugzilla yourself if you want though
[16:01] <jwendell> in order to get a good backtrace it's enough to install some -dbg packages
[16:01] <jwendell> this is easy to people
[16:02] <jwendell> but a valgrind log is not so easy, so, most bugs will be closed as invalid
[16:02] <seb128> only corruption ones
[16:03] <jwendell> seb128, how do you know if a bug is corruption memory or not? do you look through logs and backtraces?
[16:03] <seb128> jwendell: yes, crashes in g_slice are corruptions
[16:04] <seb128> usually that's something trying to use an incorrect pointed or something has been freed already
[16:04] <seb128> s/pointed/pointer
[16:04] <jwendell> as a developer I already got some bugs like that, and, for me, a backtrace was enough
[16:05] <jwendell> I was able to identify the bug with a decent bt
[16:05] <seb128> jwendell: so tell me where the bug is from this e-d-s stacktrace
[16:05] <jwendell> that's not the point of my question
[16:05] <jwendell> I'd like to improve the file of bug reporters
[16:06] <jwendell> s/file/life/
[16:06] <seb128> upstream doesn't look at most of the crashes anyway
[16:06] <jwendell> hehe
[16:06] <seb128> so I prefer to send good ones
[16:06] <jwendell> true in this case (evo)
[16:06] <seb128> rather than some which are known to not be really useful but could be used to do detective work anyway
[16:07] <seb128> valgrind is not that hard to use
[16:07] <seb128> you just have one command to run usually
[16:07] <seb128> it's a bit different for session services
[16:08] <jwendell> back to my crash, it's unreproducible, I didn't even remember what I was doing...
[16:08] <seb128> but it gives useful clue on where the variable is freed where the stacktrace usually doesn't
[16:08] <seb128> right, upstream has thousand of suchs bugs
[16:08] <seb128> I don't judge use to send "that happened once, there is no other details and no valgrind log" bugs, they just pile in bugzilla for nothing
[16:08] <seb128> s/use/useful
[16:09] <jwendell> ok, I see the point
[16:10] <seb128> as said you are feel to contribute and forward those bugs, that's an opensource project
[16:10] <seb128> but I'm not wanting to do that
[16:10] <seb128> s/feel/free
[16:11] <jwendell> seb128, I know, I was question about Ubuntu triage
[16:11] <jwendell> seb128, I understand now
[16:11] <seb128> good ;-)
[16:12] <seb128> jwendell: btw you didn't reply yesterday, what do you need in the new gdm version? (curious about it)
[16:13] <jwendell> seb128, I just want to try it, to have a strong opinion about it, because people are going to ask me about new Ubuntu with old GDM at our local events
[16:14] <seb128> jwendell: I'll try to upload the new version to a ppa tomorrow
[16:14] <jwendell> seb128, it will need consolekit 0.3
[16:15] <seb128> jwendell: why? I tried the current svn yesterday and it runs on my intrepid
[16:15] <jwendell> seb128, mccann told me
[16:15] <seb128> they are just making sure distros will not use it ;-)
[16:15] <jwendell> haha
[16:33] <stiV> kees you just marked the bug i reported https://bugs.launchpad.net/ubuntu/+source/apt/+bug/269014 as a duplicate ... but i don't think it is. https://bugs.launchpad.net/ubuntu/+source/apt/+bug/243630 describes an error where the CONTENT of the gzipped files gets signed instead of the file itself - the checksum is right there.
[16:33] <stiV> but at the moment ALL the sha256 checksums of gzipped files are exactly the same
[16:33] <stiV> i think this is a different problem ...
[16:34] <kees> stiV: oh?  let me go read more closely, sorry about that!  I thought it was a feisty vs hardy thing.  one sec
[16:35] <kees> stiV: yikes.  yeah.
[16:38] <stiV> ﻿i don't know who else is using sha256, but reprepro is. i don't know what to relate this bug to ... it's not a bug of apt itself, just of the signing process i guess
[16:38] <stiV> signing == checksum calculation
[16:49] <kees> stiV: thanks for the heads-up on that -- the archive admins are looking into it right now.
[16:50] <kees> stiV: btw, the bug is in "Soyuz" the tool that does the archive creations.  (The bug has been updated to reflect that.)
[16:52] <stiV> thanks for the info!
[17:02] <bdmurray> ogasawara: do you have an intrepid testing comment I could copy?
[17:04] <ogasawara> bdmurray: you mean you didn't get the 9123491234 call for testing emails? :)  Just a sec I think I have a condensed version
[17:04] <bdmurray> ogasawara: I deleted them all!
[17:04] <ogasawara> hehe
[17:11] <ogasawara> bdmurray: the test bug should have the long version (typo included).  or you can use something probably like http://pastebin.osuosl.org/22068
[17:12] <bdmurray> ogasawara: okay, thanks
[18:10] <bdmurray> ogasawara: can you lend any insight into bug 225258?
[18:16] <ogasawara> bdmurray: I haven't tried to build the kernel docs in a while
[18:17] <bdmurray> ogasawara: okay, the bug would be related to the doc not the doc making tool though right?
[18:18] <ogasawara> bdmurray: I believe so
[18:21] <hwilde> [69486.326312] BUG: soft lockup - CPU#0 stuck for 11s! [wpa_supplicant:4379]
[18:21] <hwilde> what info would you like to submit this as a bug
[18:22] <ogasawara> hwilde: what kernel are you using?  I've seen a few bugs with similar errors being fixed with 2.6.27
[18:22] <hwilde> 2.6.24-19-generic :(
[18:23] <ogasawara> hwilde: ah.  so how reproducible is it?
[18:23] <hwilde> it's only two months old but I buess i'm out of date
[18:23] <hwilde> it's not reproducible like on demand
[18:23] <hwilde> but it happens over and over and over
[18:23] <ogasawara> hwilde:  it would be best if you could try the 2.6.27 if possible
[18:24] <hwilde> I guess I will start building a new image :/
[18:24] <hwilde> do you have bug #s
[18:24] <ogasawara> hwilde: not off the top of my head, but just a sec and let my try to search
[18:25] <hwilde> I found plenty of cpu lockups, but not specifically referencing wpa_supplicant
[18:27] <james_w> ogasawara: hey hey, what's the tag you are using for .27 regressions?
[18:27] <ogasawara> james_w: regression-2.6.27
[18:27] <james_w> thanks
[18:27] <ogasawara> james_w: feel free to ping me with the bug id too
[18:28] <ogasawara> hwilde: bug 256433 - but not exactly the same as what you may be seeing
[18:29] <hwilde> nah my khubd is happy
[18:29] <hwilde> already been there done that
[18:30] <james_w> ogasawara: bug 262853 (it's not directly in linux)
[18:33] <ogasawara> james_w: ok thanks
[18:38] <hwilde> ogasawara, so, I can't just upgrade this machine bc it's remote and behind a customer firewall...
[18:39] <hwilde> is there some way I can push all the required packages to it ?
[18:40] <ogasawara> hwilde:  you'll probably have to copy the .deb file over then
[18:41] <james_w> ogasawara: upstream don't have a bug tracker, but it's reported a couple of times on their mailing list, no response yet
[18:42] <ogasawara> james_w: thanks, yah that's one where the kernel's not like to change so the ov51x-jpeg-source will need to be updated
[18:42] <james_w> ogasawara: sure, it happened for Hardy as well
[18:43] <ogasawara> james_w: but it is good for us to note what's breaking due to the 2.6.27 shift
[19:01] <CarlF1> http://dpaste.com/77517/  whacked formatting on line 38 - is that a bug, and what package?
[19:06] <bdmurray> CarlF1: looks like apport
[19:35] <CarlF1> bdmurray: thanks
[22:37] <dupondje> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/269170
[23:42] <bdmurray> hggdh: hi!
[23:42] <hggdh> bdmurray, hi
[23:58] <hggdh> so... how was the hug day? Or is?
[23:59] <bdmurray> hggdh: fine, not much activity in the channel but some on the wiki page
[23:59] <hggdh> cool. Just got back from the day's work (still to go out & have dinner)