[00:09] <james_w> was there ever a process defined for what to do for bug reports about problems introduced by a package in -proposed?
[00:10] <james_w> for bug 293318
[00:12] <Hobbsee> yes
[00:12] <Hobbsee> !sru
[00:12] <greg-g> james_w: I assume that if the problem was not present before the -proposed package, it would be best to report that issue on the bug that is being fixed by that proposed package
[00:12] <greg-g> or read that
[00:12] <Hobbsee> james_w: point 6 on procedure there.
[00:13] <greg-g> ah, what Hobbsee said.
[00:13] <james_w> I believe that is if it makes it to -updates isn't it?
[00:13] <Hobbsee> took me a while to find out why i was getting random pings for SRU stuff...
[00:13] <Hobbsee> hmmm, don't think so?
[00:14] <james_w> the whole point of -proposed is testing, so I don't want to ring alarm bells
[00:14] <Hobbsee> either wya, i *do* suggest you wait a few hours, as i'd be the only person on that list around right now
[00:14] <james_w> there's no need to pretend the world is on fire if a user enables a testing repository and then hits a bug because of it
[00:15] <Hobbsee> that's true.  I think the idea is that definetly some people know about a regression, before it goes to -updates
[00:15] <Hobbsee> (safe than sorry principle, and such)
[00:15] <james_w> Hobbsee, Hobbsee, Hobbsee: regression, regression, regression!!! :-)
[00:16] <Hobbsee> james_w: well, finding people to reproduce it on amd64 might be a good idea first
[00:17] <james_w> yeah, I've alerted the person that did the upload, so we should be able to get a fix
[00:17] <Hobbsee> cool
[00:17] <Hobbsee> ooh, updates.  helps if i turn on -updates and -proposed and such.
[00:18] <james_w> I just remember a discussion about a proposed process for this, and so I wondered if it actually went anywhere
[00:18] <james_w> and we have the regression-* tags now, perhaps we should have a regression-proposed
[00:18] <james_w> but finding the SRU bug and dropping a note is the best thing to do I think
[00:19] <bdmurray> james_w: there is also proposed-pkg tag
[00:19] <Hobbsee> ahh
[00:19] <bdmurray> Yes, updating the SRU bug is the best idea.
[00:19] <Hobbsee> i'm not overly sure, tbh - i don't follow SRU'y stuff.
[00:19] <Hobbsee> btu that would be my guess, too
[00:19] <james_w> bdmurray: ah, would it make sense to align that with the regression-* tags, or at least ask sbeattie to track it?
[00:20] <bdmurray> well, proposed-pkg is really for apport-crash reports
[00:23] <bdmurray> see https://wiki.ubuntu.com/Testing/EnableProposed for more info about it
[00:25] <bdmurray> We could have people tag bug reports regression-proposed but really what should happen is commenting on the SRU bug because, and referencing a new bug report, because that is what is used for moving the package to -updates.
[00:25] <james_w> ah, ok
[00:25] <james_w> yeah
[00:25] <bdmurray> If somebody is running -proposed they should be able to find the SRU bug.
[00:26] <bdmurray> In theory at least. ;-)
[00:26] <sbeattie> heh.
[00:26] <Hobbsee> in theory.  THat actually requires thought.
[00:31] <bdmurray> sbeattie: maybe regression-proposed would be a good backup system though?
[00:33] <sbeattie> bdmurray: I'd be okay with that; should a) proposed-pkg remain separate and if so, should I track it as well?
[00:34] <james_w> you could write a but that adds links to the SRU bug adding links to any bugs that have regression-proposed attached
[00:34] <james_w> (sort of)
[00:35] <bdmurray> Hmm, there are 6 bugs tagged proposed-pkg already and the Bugs/Tags package has it being used more generally
[00:37] <bdmurray> I think using regression-proposed makes the most sense as it fits the scheme and moving / reviewing those six bugs isn't a big deal
[00:39] <james_w> does anyone have amd64 hardware to test this bug on for wgrant?
[00:39] <bdmurray> yeah
[00:47] <hggdh> james_w, what would you like me to test?
[00:47] <bdmurray> hggdh: bug 293318
[00:53] <hggdh> I am running it, I cannot see any increase of memory
[00:54] <greg-g> does it require a restart?
[00:58] <hggdh> let me try it
[01:01] <hggdh> restart is not needed, just a log-out/login
[01:02] <hggdh> james_w, I still do not see memory increases
[01:02] <hggdh> right now g-s-d is 264M virtual, 13k resident
[01:04] <hggdh> for the record, this is an AMD64 dual-core
[01:14] <lirel> hi, some time ago someone from in here reopened #287198 for me becuase the claimed duplicate could not be found, i'd like to reopen it again, because it was closed again without indicating the dublicate, is this okay to do, or will i be considered as spammer if i do this?
[01:15] <charlie-tca> Bug 287198
[01:16] <james_w> lirel: it's a duplicate
[01:16] <lirel> so where can i follow up the "original" one?
[01:17] <james_w> I'm looking
[01:26] <james_w> I can't find it right now, and GNOME's bugzilla isn't playing ball, sorry
[01:30] <lirel> sorry, i'm no native english speaker, i assume "not playing ball" means st like "is not working" :)  if this is the case i will have a look for this particular bug in gnome's bugzilla later and will reopen it if i don't find anything
[01:31] <james_w> lirel: please don't re-open it
[01:31] <james_w> lirel: if Pedro says it's a known bug, then it is, and having another bug open stating the same thing isn't really going to help anything
[01:32] <james_w> I know it sucks
[01:34] <lifeless> lirel: 'playing ball' == 'cooperating'
[01:37] <lirel> okay, i'm not catting binary files on an everyday basis ;)
[01:42] <lifeless> james_w: I would say having it open is reasonable while the presumed dup cannot be found
[01:43] <james_w> lifeless: perhaps, but if there is a dupe then this one will just be ignored, so there's little use to it
[01:43] <james_w> and I trust Pedro
[01:44] <lirel> james_w: that's what i wanted to hear, i just don't want to get this one "lost"
[01:44] <james_w> lirel: I bet we've all hit that bug :-)
[01:45] <lirel> yeah, but who filed it?
[01:45] <lifeless> james_w: and if there isn't a dup (because 'everyone knows the problem') then it isn't being tracked
[01:46] <lifeless> james_w: I don't see this as a trust issue; its simple housekeeping :- either there is a dup, or there isn't, and at the moment there is no record of the dup
[01:46] <james_w> ok, we disagree
[01:47] <james_w> now I must sleep
[01:48] <lirel> n8
[01:48] <lifeless> lirel: I would say, look thouroughly through gnome's bugzilla bug database
[01:48] <lifeless> lirel: if you can't find the issue there, file a new bug upstream
[01:53] <lirel> maybe i'll write an email to pedro before doing so
[01:54] <lirel> (filing a new one)
[01:58] <james_w> http://bugzilla.gnome.org/show_bug.cgi?id=127870
[02:00] <james_w> now, if only launchpad had a way to tell us if there are any bug watches of that bug
[02:00] <james_w> or at least a way that I knew about
[02:00] <nhandler> james_w: If there is a way, it isn't through the web interface. There might be a way using the API
[02:00] <lifeless> lirel: ^ james_w has found the bug
[02:01] <james_w> yeah, I don't feel like scripting that right now
[02:01] <lirel> ill post a comment about it
[02:01] <james_w> and the easy way is hampered by the fact that I don't know of a way to get the bugs for a source package yet
[02:01] <james_w> I've wanted it a few times though, so one day I'll write ti
[02:05] <lirel> damn: opened in 2003
[02:06] <lirel> nevermind, n8
[02:14] <saivann> bdmurray : Did you have time to test latest rhythmbox revision for bug 270777 ?
[04:52] <matthewi> Hi.  I've been reviewing some bugs and think https://bugs.edge.launchpad.net/ubuntu/+bug/293360 should probably be set to "Wishlist", so posting here as per the wiki
[04:53] <maco> matthewi: ill get it
[04:53] <matthewi> thx
[05:02] <matthewi> hash mismatch on an official mirror using apt?  Probably a support request and not a bug, right?
[06:15] <dholbach> good morning
[06:19] <thekorn> good morning dholbach
[06:19] <dholbach> hey thekorn
[08:06] <mr-russ> Hi all, I would like some launchpad bug management assistance.
[08:07] <mr-russ> bug #219274 appears to be marked private.  It's a duplicate of #134207.  Are all subscriber/reports of 219274 now attached to the 134207 bug?
[08:09] <mr-russ> If so, all reporters of duplicates can see my replies.  Also can you get any info about private bugs?  eg reporter and time reported?  As the other bugs are quite old and less likely to have active followup.
[08:12] <thekorn> mr-russ, let me check this bug
[08:12] <mr-russ> thanks.
[08:13] <Hobbsee> yes, they're subscribed.
[08:14] <Hobbsee>  Reported by  riventree (grendel-riventree: 13) on 2008-04-19  (Activity log)
[08:15] <thekorn> hmm, Hobbsee seems to be faster than me,
[08:15] <thekorn> anyway, removed private flag from bug 219274
[08:16] <mr-russ> now to prove my hunch that all these bugs are really #63141
[08:18] <mr-russ> thanks all for your fast response.  It's always a good experience visiting ubuntu-bugs.
[08:51] <mr-russ> next question :)   When I believe a bug belongs in another package, what's the best procedure?   The crash for the bugs mentioned earlier appears in PHP, but the root cause is a problem with PostgreSQL.  How should the classification be handled?
[08:51] <mr-russ> or libpq to be exact.
[08:58] <persia> mr-russ, Just adjust the package.  It ought be an option as if you were adjusting the status.
[09:05] <mr-russ> okay, I'm just concerned with the existing number of dups that it will get reported again.  I suppose I just monitor it and add new dups.
[09:07] <persia> Well, you could ave two tasks, one for the frontend, and one for the DB, so people can find it more easily.  Bit annoying to have to close the task manually, but might save on dup chasing.
[09:19] <seb128> persia: and that mail spam the people who are subscribed to the other task too
[09:21] <mr-russ> I think I just mailspamed people as I don't know how to bulk move duplicates to a new parent.
[09:22] <Hobbsee> mr-russ: there's no bulk moving of duplicates
[09:23] <Hobbsee> you have to move them all individually.
[09:23] <Hobbsee> so you probably did mailspam.  However,if you did it quick enough, launchpad tends to cache mails.
[09:23] <mr-russ> ah.
[09:25] <mr-russ> Is somebody willing to mark bug #63141 as triaged?  It's as good of a report as it's ever going to get :)
[09:27] <mr-russ> Can I subscribe to receive new bugs from just one package?
[09:28] <azimout> mr-russ: yes, you can
[09:29] <azimout> go to https://bugs.launchpad.net/ubuntu/+source/xyz (replace xyz with the package name)
[09:29] <azimout> and click on "subscribe to bug mail"
[09:29] <azimout> is this what you wanted?
[09:29] <mr-russ> does that send me all bug mail for that package?  or just new bug reports?
[09:30] <persia> Should send you all bug mail for the package.
[09:30] <mr-russ> Yeah, I was hoping for just new reports.  I suspect mail from 1 package is not huge though.
[09:31] <persia> Depends on the package, but if it's huge, you'd be able to guess before you subscribe :)
[09:31] <mr-russ> it's php,  I'm not willing to subscribe to the mozilla/firefox package.  The thought is scary!
[09:32] <persia> seb128, For this use case, don't they get it anyway because the bugs are being filed against the package that crashes, rather than the package with the bug?
[09:32] <seb128> persia: I don't know about this case and didn't follow the discussion, that's just a reminder that extra tasks means extra people mailed for every comment
[09:33] <persia> mr-russ, Thinking about it more: there's a valid case for two tasks : pg shouldn't crash, but php should trap that sanely.
[09:33] <persia> seb128, Yeah.  I agree that most of the time it's not a good idea.
[09:34] <mr-russ> It's hard because pg adds an SSL callback, and when curl closes SSL the pg callback is called, however since the library is unloaded, the callback segfaults.
[09:34] <mr-russ> so is it curl's fault, or php's fault for not trapping the problem with bad callbacks.  or maybe it's openssl's :)
[09:34] <mr-russ> I know the fix needs to come from postgresql.  but it's a hard bug.  It took me a full day to nail it down.
[09:41] <persia> mr-russ, I'm a big believer in defensive coding.  Library authors are all insane (a necessary prerequsite to being a library coder), so one needs to check to make sure that nothing goes wrong when one calls a library, or allows a library to call a callback.
[09:42] <persia> fixing postgressql to not crash is a good thing.  Fixing php to not crash when postgressql crashes is possibly also wise.
[09:46] <mr-russ> and fixing curl when openssl calls a callback :)
[09:46] <mr-russ> or fixing openssl to ensure the callback is still valid,  I'm not even sure how you do that.  but a problem for another day.
[09:49] <persia> Indeed.  Lots of bugs to fix there :)
[09:55] <mr-russ> what is the difference between:  postgresql, postgresql-8.1, postgresql-8.2 packages?  all bugs that are in all versions would go in postgresql and version specific bugs in the version label?
[09:58] <persia> No, those are different packages, I think the old ones are either from earlier releases, or for people who need backward compatibility.
[09:59] <mr-russ> the bug affects all version, do I add all those packages to the affected packages for the bug?
[09:59] <mr-russ> sorry for all the questions, it's not simple to understand all this stuff.
[10:00] <persia> No.  Only add the current package.  The old ones are unlikely to be fixed.
[10:50] <azimout> reminder: it's bug day today!
[11:04] <unenough> bug? restart doesn't really work. computer reboots and gets stuck just before loading grub
[11:07] <azimout> unenough: what do you mean "stuck"? i may be a problem with your grub menu file...
[11:07] <unenough> no, it works when i shutdown
[11:08] <unenough> only when i reboot, that is, power doesn't shutdown completely, does this occur
[11:09] <unenough> and only when i reboot from linux. rebooting from windows works
[11:23] <azimout> unenough: ok, and what do you mean stuck? what do you see? error messages?
[11:23] <mvo> unenough: what kind of machine is that? what chipset/cpu?
[11:24] <unenough> i see nothing. blank text screen with blinking cursor
[11:25] <unenough> Toshiba Satellite A215
[11:25] <unenough> (laptop)
[11:33] <azimout> unenough: file a bug report under grub, and paste the link here
[11:45] <unenough> mvo, I'm pretty sure the bug has nothing to do with grub
[11:46] <unenough> the problem is how the linux kernel performs a reboot on this machine
[11:53] <mvo> unenough: right, I have a system that can not reboot, I need to halt it and then power it on again, now I always thought that this is simply a HW problem, this is why I asked for the machine specs
[12:07] <nhandler> Are there any bug control admins here?
[12:12] <james_w> nhandler: I believe pedro_ is
[12:13] <nhandler> pedro_: Could you renew my Bug Control membership?
[12:13] <pedro_> yes i'm here, nhandler can i help you with something?
[12:13] <pedro_> nhandler: sure, give me a few mins
[12:13] <nhandler> Thanks pedro_
[12:17] <pedro_> nhandler: done, thanks you!
[12:18] <nhandler> Thanks again pedro_!
[12:21] <Hobbsee> hmmm.  are any hardy systems actually running cron, if they've enabled & disabled the root account?
[12:41] <shirish> hi all, I just changed some stuff at https://wiki.ubuntu.com/DebuggingProgramCrash
[12:41] <shirish> I wanna know
[12:41] <shirish> a. On which of the bug lists should I report this change?
[12:42] <Hobbsee> ubuntu-bugs@
[12:42] <shirish> b. There is some information missing in the web-page , gpg --recv-key 428D7C01 but no keyserver given, what to do in such a case
[12:42] <shirish> Hobbsee: thank you
[12:43] <Hobbsee> shirish: by using the default?
[12:43] <Hobbsee> shirish: would help if you learned to spell 'feisty', too, before you put it into the documentation.
[12:45] <shirish> Hobbsee: would look if I did some mistake in the spellings
[12:45] <shirish> Hobbsee: I tried the default given there
[12:46] <Hobbsee> Most  keyservers synchronize with each other, so there is gener‐
[12:46] <Hobbsee>               ally no need to send keys to more than one server. The keyserver
[12:46] <Hobbsee>               hkp://subkeys.pgp.net  uses  round robin DNS to give a different
[12:46] <Hobbsee>               keyserver each time you use it.
[12:46] <shirish> gpg --recv-key 428D7C01
[12:46] <shirish> gpg: no keyserver known (use option --keyserver)
[12:46] <Hobbsee> so, you could either specify the default (which would be pointless), or you can increase the load one one of the servers (which doesn't make sense to do)
[12:46] <Hobbsee> sarah@neptune:~% gpg --recv-key 428D7C01                                11:46PM
[12:47] <Hobbsee> gpg: requesting key 428D7C01 from hkp server subkeys.pgp.net
[12:47] <Hobbsee> gpg: key 428D7C01: "Ubuntu Debug Symbol Archive Automatic Signing Key <ubuntu-archive@lists.ubuntu.com>" not changed
[12:47] <Hobbsee> gpg: Total number processed: 1
[12:47] <Hobbsee> gpg:              unchanged: 1
[12:47] <Hobbsee> works for me.
[12:47] <shirish> Hobbsee: does that have an issue with dhcp or something?
[12:47] <Hobbsee> no?
[12:48] <shirish> why did you put the time 11:46 PM, does one need to give time as well?
[12:48] <Hobbsee> no, it's just part of my .zsh.
[12:49] <shirish> Hobbsee: ah ok, its saying gpg: keyserver receive failed: bad URI
[12:50] <Hobbsee> doesn't look to be a commonly found issue - no one's reported it
[12:50] <shirish> Hobbsee: please lemme know what can I do to resolve it?
[12:51] <Hobbsee> hmmm.  Some people have.
[12:51] <Hobbsee> on the forums.
[12:52] <Hobbsee> hmm, not only on the forums.  Just no one's filed a bug.
[12:52] <Hobbsee> shirish: am I really your personal google searcher?
[12:52] <Hobbsee> shirish: or are you just lazy?
[12:52] <shirish> Hobbsee: no, just lemme know which package should I file this against, gpg or something else?
[12:52] <Hobbsee> gnupg, i expect.
[12:53] <shirish> Hobbsee: thank you for your help.
[12:53]  * Hobbsee mutters about people who still don't fix their wiki errors.
[12:55]  * Hobbsee edits it
[14:40] <bddebian> Boo
[16:21] <hggdh> seb128 ping
[16:21] <seb128> hggdh: hi
[16:22] <hggdh> hi seb128 I am building a PPA for E-D-S for bug 205999
[16:22] <seb128> ah good
[16:22] <hggdh> Milan has proposed a patch, and it is asking for tests on it
[16:22] <hggdh> this will be (right now) for Intrepid
[16:22] <seb128> right, I read your comment on the bug
[16:23] <seb128> do you think that's worth a sru?
[16:23] <hggdh> oh, OK
[16:23] <hggdh> I think it might -- this has a good impact
[16:23] <hggdh> (usability)
[16:24] <seb128> ok, should be easy to find a sponsor for the update
[16:31] <hggdh> seb128, I will prepare a debdiff for Hardy
[16:32] <seb128> hggdh: thanks
[16:37] <hggdh> OK, question for anyone familiar with PPA & etc: my build failed with "gawk: command not found" for Evolution-data-server
[16:37] <hggdh> I expected gawk would be part of the base systems
[16:38] <ivoks> me too :)
[16:38] <ivoks> but it isn't
[16:38] <ivoks> package should build depend on gawk
[16:38] <hggdh> so I have to add a depends for gawk...
[16:39] <hggdh> thanks. Still weird -- this is a debdiff from e-d-s... how did it build originally then?
[16:39] <seb128> hggdh: the intrepid source should build fine in an intrepid environment that's weird
[16:39] <seb128> are you sure that's the issue?
[16:39] <seb128> do you have the build log url?
[16:40] <hggdh> seb128, yes -- http://launchpadlibrarian.net/19342549/buildlog_ubuntu-intrepid-amd64.evolution-data-server_2.24.1-0ubuntu1ppa3_FAILEDTOBUILD.txt.gz
[16:41] <seb128> it did that on all archs?
[16:41] <hggdh> I will check the others now
[16:42] <hggdh> also failed the same on lpia and i386
[16:42] <seb128> hggdh: what is your ppa page?
[16:43] <hggdh> https://launchpad.net/~hggdh2/+archive
[16:43] <seb128> hggdh: gawk is not installed in other builds either bug that doesn't break the build
[16:44] <seb128> did you run autotools or something?
[16:44] <hggdh> no -- I got your latest source, and just added the patch + debuild -S
[16:44] <seb128> $ debdiff evolution-data-server_2.24.1-0ubuntu1.dsc evolution-data-server_2.24.1-0ubuntu1ppa3.dsc | diffstat
[16:44] <seb128>  Makefile                                      | 3007 +++++++++++++++++++
[16:44] <seb128>  config.log                                    | 4047 ++++++++++++++++++++++++++
[16:44] <seb128>  config.status                                 | 1669 ++++++++++
[16:44] <seb128>  debian/patches/70_bug524377.patch             |   86
[16:44] <seb128>  evolution-data-server-2.24.1/debian/changelog |   22
[16:45] <seb128>  libdb/Makefile                                |  660 ++++
[16:45] <seb128>  6 files changed, 9491 insertions(+)
[16:45] <seb128> no you didn't
[16:45] <seb128> you got autotools running
[16:45] <hggdh> I certainly did not ask for it
[16:45] <seb128> clean the other changes and try again
[16:45] <hggdh> k
[16:45] <hggdh> ah
[16:45] <seb128> you didn't edit any makefile* or ran autogen.sh?
[16:46] <hggdh> nope -- but I did debuild binary before generating the ppa
[16:46] <hggdh> maybe a cruft
[16:46] <hggdh> left by the binary build
[16:46] <seb128> sometime the autotools are automatically called
[16:46] <hggdh> yes
[16:47] <seb128> but usually that's when a autotools file timestamp changed
[16:47] <hggdh> I will save the ./debian, and reinstall the orig.tar
[16:47] <seb128> ie if you editing one for some reason
[16:47] <seb128> right
[16:47] <seb128> untar the tar.gz and copy the debian directory
[16:47] <hggdh> yup
[16:47] <hggdh> I really expected a debuild -S to clean up
[16:49] <bdmurray> saivann: the -proposed version of rhythmbox is working for me now
[16:57] <hggdh> oh, oh, the pains caused by ignorance... ;-)
[16:58] <seb128> hggdh: what do you mean by clean up there? debuild does make clean but there is no cleanup to do to updated makefiles
[16:58] <seb128> hggdh: the only clean you could do is to run autogen to update the makefile rather which is what you don't want usually
[16:59] <hggdh> yes, I had just realised it... again I forgot a basic rule: *always* start with clean sources
[16:59] <hggdh> last time it was with coreutils
[16:59] <bdmurray> saivann: I did notice the file I copied over had no id3 tag though.  Does that happen to you too?
[17:22] <jegHegy> paging Alberto Milone
[18:23] <bdmurray> ogasawara: does bug 193970 only affect iwl3945 and iwl4965?  Is there another bug for other drivers?
[18:24] <ogasawara> bdmurray: I believe that is the only bug, is there another driver reporting this issue?
[18:24] <bdmurray> I'm looking at bug 292280 where they mention iwlagn
[18:25] <ogasawara> bdmurray: I'd assume that'd be a dup of 193970
[18:27] <ogasawara> bdmurray: I'm going to go ahead and mark it as a dup, unless you want to
[18:28] <bdmurray> ogasawara: feel free just mark it off the hug day list! ;-)
[18:28] <ogasawara> bdmurray: ok
[18:28] <bdmurray> perhaps updating the title of 193970 would be good too
[19:12] <bdmurray> Anybody know where the technical overview for intrepid is now?
[19:13] <bdmurray> I found it
[19:13] <silentz> hey
[19:13] <silentz> i got some bugs :(
[19:14] <bdmurray> Have you found out if they are reported in Launchpad?
[19:14] <silentz> himm i dont think so
[19:14] <silentz> it is about the pidgin and
[19:14] <silentz> the gedit
[19:15] <silentz> the pidgin if the compiz runnig it stuck :(
[19:15] <silentz> and every thing deleted :S
[19:17] <snap-l> silentz: I'm running into an (unreported) issue re: Pidgin and memory leaks
[19:17] <silentz> thats good notice that i have 2.5.2
[19:17] <snap-l> Run the command "top" in a window and press "m" to sort by memory usage.
[19:17] <silentz> the 2nd thing with the gedit
[19:17] <silentz> when i open any file small of big
[19:18] <silentz> it start sooo slow
[19:18] <silentz> then it work good
[19:18] <snap-l> Check your memory usage for pidgin. I think that's the crux of your issue.
[19:19] <silentz> i have a very good PC
[19:19] <silentz> with good specification
[19:19] <silentz> i dont think it is a memory problem
[19:19] <silentz> i have used 8.04
[19:20] <silentz> with no problem in gedit
[19:20] <silentz> but pidgin from the existence of 2.5.0 untill 2.5.2
[19:20] <WelshDragon> If i want to make a suggestion...Do i just report a bug and then change the importance to Wishlist?
[19:21] <bdmurray> WelshDragon: it depends on the scope of the suggestion
[19:21] <bdmurray> WelshDragon: What do you have in mind?
[19:22] <silentz> himmm
[19:22] <silentz> not really
[19:22] <WelshDragon> bdmurray, A very simple suggestion. gdebi-gtk doesn't give users an option to uninstall the package if it's already installed. It only has a reinstall option.
[19:22] <silentz> i like ubuntu but some time really dont like these small bugs :(
[19:24] <bdmurray> WelshDragon: I'm not sure that falls with-in the applications scope, but that is something you could submit in Launchpad.
[19:25] <WelshDragon> bdmurray, Submit it as a bug report though?
[19:25] <silentz> man i'm tooo lazy to make a report with my bad english :D
[19:26] <bdmurray> WelshDragon: yes
[19:26] <WelshDragon> bdmurray, OK. Thank you :)
[19:26] <chrisccoulson> WelshDragon - i agree with bdmurray about your idea perhaps being outside of the scope for gdebi-gtk
[19:27] <chrisccoulson> i think it would be counterintuitive to have to double click on a .deb package in order to uninstall it
[19:27] <chrisccoulson> that's what synaptic is for;)
[19:27] <bdmurray> The package description also says 'Simple too to install deb files'
[19:28] <chrisccoulson> gdebi-gtk is there purely as a tool to facilitate the easy installation of deb files you've downloaded, to allow you to just double click on a package
[19:28] <chrisccoulson> i don't really think it should have any other features tbh
[19:31] <silentz>  i have a suggestion :D
[19:31] <silentz> why dont we make a shortcut
[19:31] <silentz> in the Right click list
[19:31] <silentz> the said uninstall
[19:32] <silentz> without making a new package dedicated for uninstalling :D
[19:32] <silentz> like in linux mint
[19:33] <silentz> ??
[19:34] <WelshDragon> chrisccoulson, It may seem counterintuitive, but when you double click an exe in Windows, It gives you an option to repair or uninstall? In terms of trying to make ubuntu more user friendly, surely it'd be a plus for gdebi to include an uninstall button aswell.
[19:34] <silentz> yea i know
[19:35] <silentz> but the user like that should keep
[19:35] <silentz> the .deb :S
[19:35] <silentz> but making a shortcut for the user to right click on the programme then uninstall it would be better
[19:35] <silentz> Right ?
[19:36] <silentz> and it is oky to make both the button and my idea also :)
[19:36] <chrisccoulson> perhaps an option in the context menu if you right-clicked on a deb. but the problem is then that the file manager has to check whether that application is already installed before populating the context menu
[19:38] <silentz> yea it is a good point but we can solve if with ....
[19:38] <silentz> >>> hard to explain :S
[19:38] <silentz> making the debian file check himself
[19:39] <silentz> in where it is installed only
[19:39] <silentz> if so the button if enabled
[19:39] <WelshDragon> >< Already been suggested *bonk*
[19:39] <silentz> if not button is disables
[19:39] <silentz> Right ?
[19:41] <chrisccoulson> i dunno. you could try suggesting it on Launchpad if you like, but I don't think we need to clutter up the right-click context menu anymore than it alreadt is. it becomes less useful and harder to use if we start sticking extra options in it
[19:41] <azimout1> come on guys, today is bug day. quit wasting time about whether gdebi should uninstall packages and solve some bugs! :-P
[19:41] <silentz> himmm
[19:41] <silentz> yea Right man
[19:42] <silentz> i think i'm disturbing you
[19:42] <silentz> i'm really newbie in linux world >> just one year
[19:42] <silentz> c ya soon : - D
[19:43] <azimout1> e.g. i have no clue where to start with this one: https://bugs.launchpad.net/ubuntu/+bug/293061
[19:48] <chrisccoulson> azimout1 - i can't reproduce bug 293061
[19:48] <chrisccoulson> maybe it's locale related?
[19:48] <chrisccoulson> could you get the reporter to try running firefox with a different locale and see if it goes away?
[19:48] <homy> I can't reproduce either. english locale.
[19:48] <chrisccoulson> something like "LC_ALL=en_US.UTF-8 firefox"
[19:49] <azimout1> i know, i can't reproduce it either
[19:49] <azimout1> but he has the problem also in eclipse
[19:49] <chrisccoulson> i'd defo get the reporter to try a different locale. or you could try his locale perhaps? i would do it now but i have to go and eat and i don't have the time to install the necessary packages
[19:50] <chrisccoulson> yeah, the eclipse/FF problems might be related
[19:50] <azimout1> ok, i will, thanx
[19:59] <jdstrand> ogasawara: hi! are you aware of any IO issues with 2.6.27, maybe or maybe not related to LVM?
[19:59] <jdstrand> ogasawara: after upgrading to intrepid I seem to have all kinds of IO contention
[19:59] <ogasawara> jdstrand: not that I'm aware of but I'm still going through some newer bug reports
[19:59] <jdstrand> (esp during builds or using VMs)
[20:00] <jdstrand> ogasawara: I'll file one if I can get anything more specific than 'it feels a lot slower'
[20:00] <ogasawara> jdstrand: although I do recall something from kees, just a sec
[20:00] <ogasawara> jdstrand: but he mentioned it was eventually resolved with an update
[20:00] <jdstrand> ogasawara: we've both been complaing to each other...
[20:01] <ogasawara> jdstrand: bug 262843
[20:02] <pyraz> hello all, I was wondering if anyone could point me to the best place to get started with helping with bugs
[20:02] <pyraz> is triaging the best place to start?
[20:03] <ogasawara> jdstrand: bug 291683
[20:04] <jdstrand> ogasawara: ok. I'll dig into those in a bit. thanks!
[20:04] <pedro_> pyraz: do you want to start with some easy tasks? probably triaging the bugs without a package is the easier way to start with this
[20:04] <pedro_> pyraz: today we have a hug day about that look at https://wiki.ubuntu.com/UbuntuBugDay/20081104
[20:08] <pyraz> yes, easier sounds better, i'm checking out that site now
[20:08] <pyraz> thanks
[20:08] <saivann> bdmurray : -proposed version works for your now?? Did you try to transfer the same music files than the last time it failed?
[20:09] <bdmurray> saivann: yes, the same file as indicated in the bug
[20:09] <saivann> bdmurray : I'm trying to see if ID3 tags are removed during transfer..
[20:16] <saivann> bdmurray : I just tried with a fresh install, rhythmbox failed to transfer, I updated to intrepid-proposed, rhythmbox successfully transfered and the copied MP3 file still have all ID3 tags
[20:16] <saivann> Artist, Album, etc.
[20:19] <bdmurray> saivann: hmmm, I'll remove rhythmbox and try again
[20:20] <saivann> bdmurray : Strangely, someone else reported that the version in -proposed didn't work, exactly like you..
[20:21] <bdmurray> saivann: It wouldn't be device specific would it?
[20:23] <saivann> bdmurray : I also thought about this.. The changes that the upstream developer included is definitively not device-specific, but perhaps that libmtp has some device specific bugs.. I don't know
[20:58] <bdmurray> saivann: still no tags and the files copied have a strange extension too
[20:59] <weboide> Hi, i was trying to reproduce bug I can reproduce this bug in 8.10.
[20:59] <weboide> *BUT* the properties for this error dialog box is _NET_WM_STATE_SKIP_TASKBAR which should mean that it should not appear in the alt-tab windows list.
[20:59] <weboide> argh nevermind the last line...
[20:59] <saivann> bdmurray : Yes I also have a weird filename, that seems to be normal here. But I have all ID3 tags. Are-you transfering MP3 or other audio file types?
[20:59] <bdmurray> saivann: mp3
[20:59] <weboide> ... in https://bugs.launchpad.net/ubuntu/+bug/189294 and in fact I don't know if that's a normal behaviour
[21:01] <saivann> bdmurray : I tried many files on two computers, one AMD64 and one i386 and I never get error or missing ID3 tags, always with -proposed release, so I really don't know why you have this behavior. Any outputs in the terminal if you run rhythmbox on it?
[21:07] <charlie-tca> weboide: I can not get the error to come up with an empty drive. I would think the error
[21:07] <charlie-tca> should not block Alt+tab switching
[21:07] <weboide> charlie-tca: I think what he means is:
[21:08] <bdmurray> saivann: nothing, I could try on another system
[21:08] <weboide> charlie-tca: when you have an error dialog, the dialog doesn't show up in the alt-tab windows list
[21:09] <weboide> charlie-tca: so the dialog falls into the background and the only way to get it back to front is to minimize every other windows
[21:09] <weboide> I reproduced it in 8.10
[21:10] <weboide> charlie-tca: but i need confirmation about if that's a normal behaviour or not
[21:10] <weboide> charlie-tca: the window has a SKIP TASKBAR property
[21:10] <charlie-tca> I don't know why the window couldn't be brought back! I think it is valid
[21:11] <charlie-tca> unless that is so that the error window never grabs focus
[21:12] <charlie-tca> I just don't know, I guess. Sorry
[21:12] <saivann> bdmurray : BTW, do you have all updates installed?
[21:12] <weboide> charlie-tca: well I thought that this is kind of a lot of work to bring back that error window, so I think ill confirm it.
[21:12] <bdmurray> saivann: last I checked - about 5 hours ago
[21:13] <charlie-tca> agreed
[21:13] <weboide> charlie-tca: I expected that error to show up in the alt-tab
[21:13] <charlie-tca> That's my thought too! How else can you get rid of it?
[21:14] <bdmurray> saivann: and its just rhythmbox from -proposed correct?
[21:14] <weboide> charlie-tca: I think the expected behaviour is when you alt-tab to the application that raised the error, the error should show up also. (isn't this feature working already?) does it mean nautilus has a weird way to raise error windows? hmm..
[21:15] <saivann> bdmurray : Yes, with version number that ends with 4.1
[21:16] <azimout1> question: Bug #292990 should be assigned to pdvd (the user purchased the software on canonical shop) but launchpad gives me "Package pdvd not published in Ubuntu"
[21:17] <azimout1> Bug #292990
[21:33] <bdmurray> saivann: the id3 tags exist on my desktop I wonder if a specific package is required...
[21:34] <saivann> bdmurray : ID3 tags are correctly transfered on your other computer?
[21:35] <bdmurray> saivann: that's correct and 'dpkg -l | grep id3' is different for both systems
[21:35] <saivann> bdmurray : Oh, weird :P Are both of your computers freshly installed, or some packages might have been uninstalled?
[21:36] <bdmurray> saivann: neither are freshly installed.
[21:39] <saivann> bdmurray : Ok, in my case it was always fresh installs of intrepid final release, and it worked correctly so I guess that something's missing
[21:40] <saivann> bdmurray : Perhaps gstreamer0.10-plugins-good or libid3tag0 ?
[22:13] <bdmurray> saivann: it seems some files on my mtp player aren't tagged at all
[22:13] <Susana> hello, ctrl+alt+f# hardly ever works for me at first time (i have to press twice) which package should that be reported against?
[22:16] <saivann> bdmurray : That would explain some things :) Perhaps that you can try with gnomad2 to see if you get the same result
[22:16] <chrisccoulson> Susana - good question. i saw someone else report a similar issue a little while ago, but i can't remember which package they assigned it too
[22:16] <saivann> Susana : I also reproduce this bug sometime?
[22:17] <charlie-tca> Will this help? https://wiki.ubuntu.com/DebuggingProcedures#Hardware
[22:17] <saivann> Susana : If you find the appropriate bug report, let me know :)
[22:18] <chrisccoulson> i think i saw a bug describing a similar problem reported against consolekit a little while ago, although i don't think that is the correct package. james_w - do you know if this was the case? if so, can you remember what happened to it?
[22:20] <ogasawara> thekorn: I have a random plb question.  I know it's possible to add new tasks to a bug using something like Bug.NewTask("project", "bzr-fs")
[22:20] <chrisccoulson> i've answered my own question. Susana - it's bug 271962
[22:21] <ogasawara> thekorn: is it possible to add release nominations the same way?
[22:22] <Susana> chrisccoulson: thanks
[22:22] <bdmurray> saivann: its the same with gnomad2.  I'd guess it didn't write the tags when I first transferred them to the device
[22:24] <thekorn> ogasawara, hi, no support for nominations is not implemented
[22:24] <saivann> bdmurray : I still wonder why dieterv still reports that it doesn't work, he seems to have the same issue then you when you tried for the first time
[22:25] <thekorn> ogasawara, there is a open bug 172802
[22:25] <bdmurray> thekorn: you mean approving nominations but can you target a bug to a release?
[22:26] <thekorn> bdmurray, honestly, I#m not sure, I just checked the branch attached to this bug,
[22:27] <thekorn> there is only parsing of nominatiions implemented,
[22:28] <thekorn> but no way of changing things,
[22:28] <thekorn> unfortunatly this did not get any work recently
[22:30] <thekorn> hmm on the other hand I thought I did some more work, maybe I forgot to push some revisions,
[22:32] <ogasawara> thekorn:  I'd definitely be interested in having both the ability to add a nomination and then approve it.  let me know if there's anything I can do to help.
[22:36] <thekorn> ogasawara, ok, will try to work on it in the next few days
[23:06] <james_w> chrisccoulson: you are right about Susana's bug, and I think it's still against consolekit, but I never figured out whether that was the right place
[23:07] <azimout1> is there some page that lists past bugdays?
[23:07] <chrisccoulson> thanks james_w. yeah, i'm not sure if it is the right place either
[23:07] <chrisccoulson> i can actually reproduce the bug sometimes
[23:07] <james_w> they pointed to a bug report that described the right symptoms, but I couldn't see that the fix for that had regressed
[23:07] <james_w> I can reproduce it as well
[23:08] <chrisccoulson> azimout1 - i'm not sure if there is an easy way to find past bugdays, but all the URLs are of the format https://wiki.ubuntu.com/UbuntuBugDay/yyyymmdd
[23:09] <james_w> chrisccoulson: did I see you discussing the bug that you triaged just before release that was deferred to be an SRU?
[23:09] <james_w> was it the evolution one I mean?
[23:09] <azimout1> i'm guessing dholback might know, but his not in the channel
[23:10] <bdmurray> azimout1: https://wiki.ubuntu.com/UbuntuBugDay/Planning
[23:10] <chrisccoulson> james_w - i mentioned it on #ubuntu-motu because RAOF had come across the problem - it's the one for evolution-sharp
[23:11] <james_w> chrisccoulson: cool, if you need a hand getting that done feel free to ping me
[23:11] <james_w> Susana: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/271962 is the one we were talking about for your bug
[23:12] <chrisccoulson> thanks james_w - i think someone beat me to it though
[23:13] <chrisccoulson> on the VT switching problem - i just noticed something and i'm not sure how relevant it is. my girlfriend is logged in on VT7, and I'm on VT9. I tried to switch to VT1 from my own session, and I ended up at my girlfriends locked screen on VT7 instead, so it didn't just return to my own session
[23:21] <james_w> chrisccoulson: interesting, will you note that in the report?
[23:21] <chrisccoulson> yeah, i can do that
[23:21] <james_w> chrisccoulson: did she log in first?
[23:21] <james_w> I assume from the VT assignments
[23:21] <chrisccoulson> she did log in first
[23:21] <james_w> good catch
[23:22] <james_w> it does sound the original fix has regressed somehow
[23:26] <azimout1> chrisccoulson: i found the way to find all past bugdays!
[23:26] <azimout1> just did a search in wiki.ubuntu.com :-)
[23:34] <bdmurray> azimout1: did my url not help?
[23:36] <azimout1> bdmurray: sorry, i had missed your response. yes, it's what i was looking for. thank you