[00:09] was there ever a process defined for what to do for bug reports about problems introduced by a package in -proposed? [00:10] for bug 293318 [00:10] Launchpad bug 293318 in gnome-settings-daemon "gnome-settings-daemon leaks memory" [Undecided,New] https://launchpad.net/bugs/293318 [00:12] yes [00:12] !sru [00:12] Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates [00:12] 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] or read that [00:12] james_w: point 6 on procedure there. [00:13] ah, what Hobbsee said. === asac_ is now known as asac [00:13] I believe that is if it makes it to -updates isn't it? [00:13] took me a while to find out why i was getting random pings for SRU stuff... [00:13] hmmm, don't think so? [00:14] the whole point of -proposed is testing, so I don't want to ring alarm bells [00:14] 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] 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] that's true. I think the idea is that definetly some people know about a regression, before it goes to -updates [00:15] (safe than sorry principle, and such) [00:15] Hobbsee, Hobbsee, Hobbsee: regression, regression, regression!!! :-) [00:16] james_w: well, finding people to reproduce it on amd64 might be a good idea first [00:17] yeah, I've alerted the person that did the upload, so we should be able to get a fix [00:17] cool [00:17] ooh, updates. helps if i turn on -updates and -proposed and such. [00:18] I just remember a discussion about a proposed process for this, and so I wondered if it actually went anywhere [00:18] and we have the regression-* tags now, perhaps we should have a regression-proposed [00:18] but finding the SRU bug and dropping a note is the best thing to do I think [00:19] james_w: there is also proposed-pkg tag [00:19] ahh [00:19] Yes, updating the SRU bug is the best idea. [00:19] i'm not overly sure, tbh - i don't follow SRU'y stuff. [00:19] btu that would be my guess, too [00:19] bdmurray: ah, would it make sense to align that with the regression-* tags, or at least ask sbeattie to track it? [00:20] well, proposed-pkg is really for apport-crash reports [00:23] see https://wiki.ubuntu.com/Testing/EnableProposed for more info about it [00:25] 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] ah, ok [00:25] yeah [00:25] If somebody is running -proposed they should be able to find the SRU bug. [00:26] In theory at least. ;-) [00:26] heh. [00:26] in theory. THat actually requires thought. [00:31] sbeattie: maybe regression-proposed would be a good backup system though? [00:33] bdmurray: I'd be okay with that; should a) proposed-pkg remain separate and if so, should I track it as well? [00:34] you could write a but that adds links to the SRU bug adding links to any bugs that have regression-proposed attached [00:34] (sort of) [00:35] Hmm, there are 6 bugs tagged proposed-pkg already and the Bugs/Tags package has it being used more generally [00:37] 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] does anyone have amd64 hardware to test this bug on for wgrant? [00:39] yeah [00:47] james_w, what would you like me to test? [00:47] hggdh: bug 293318 [00:48] Launchpad bug 293318 in gnome-settings-daemon "gnome-settings-daemon leaks memory" [High,In progress] https://launchpad.net/bugs/293318 [00:53] I am running it, I cannot see any increase of memory [00:54] does it require a restart? [00:58] let me try it [01:01] restart is not needed, just a log-out/login [01:02] james_w, I still do not see memory increases [01:02] right now g-s-d is 264M virtual, 13k resident [01:04] for the record, this is an AMD64 dual-core [01:14] 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] Bug 287198 [01:15] Launchpad bug 287198 in vte "[hardy] doing cat on binary files breaks gnome-terminals charset" [Undecided,Invalid] https://launchpad.net/bugs/287198 [01:16] lirel: it's a duplicate [01:16] so where can i follow up the "original" one? [01:17] I'm looking === bdmurray changed the topic of #ubuntu-bugs to: Hug Day! https://wiki.ubuntu.com/UbuntuBugDay/20081104 | Ubuntu BugSquad | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | If you have been triaging bugs for a while, please apply to https://launchpad.net/~ubuntu-bugcontrol/ | Want to report a bug? Read https://help.ubuntu.com/community/ReportingBugs | User support (not related to triage) is in #ubuntu [01:26] I can't find it right now, and GNOME's bugzilla isn't playing ball, sorry [01:30] 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] lirel: please don't re-open it [01:31] 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] I know it sucks [01:34] lirel: 'playing ball' == 'cooperating' [01:37] okay, i'm not catting binary files on an everyday basis ;) [01:42] james_w: I would say having it open is reasonable while the presumed dup cannot be found [01:43] lifeless: perhaps, but if there is a dupe then this one will just be ignored, so there's little use to it [01:43] and I trust Pedro [01:44] james_w: that's what i wanted to hear, i just don't want to get this one "lost" [01:44] lirel: I bet we've all hit that bug :-) [01:45] yeah, but who filed it? [01:45] james_w: and if there isn't a dup (because 'everyone knows the problem') then it isn't being tracked [01:46] 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] ok, we disagree [01:47] now I must sleep [01:48] n8 [01:48] lirel: I would say, look thouroughly through gnome's bugzilla bug database [01:48] lirel: if you can't find the issue there, file a new bug upstream [01:53] maybe i'll write an email to pedro before doing so [01:54] (filing a new one) [01:58] http://bugzilla.gnome.org/show_bug.cgi?id=127870 [01:58] Gnome bug 127870 in VteTerminal "terminal garbled and needs 'reset' after cat'ing file" [Normal,Reopened] [02:00] now, if only launchpad had a way to tell us if there are any bug watches of that bug [02:00] or at least a way that I knew about [02:00] james_w: If there is a way, it isn't through the web interface. There might be a way using the API [02:00] lirel: ^ james_w has found the bug [02:01] yeah, I don't feel like scripting that right now [02:01] ill post a comment about it [02:01] 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] I've wanted it a few times though, so one day I'll write ti [02:05] damn: opened in 2003 [02:06] nevermind, n8 === rgreening_ is now known as rgreening [02:14] bdmurray : Did you have time to test latest rhythmbox revision for bug 270777 ? [02:14] Launchpad bug 270777 in rhythmbox "[SRU] unable to copy music from an MTP device" [Low,Fix committed] https://launchpad.net/bugs/270777 === rgreening_ is now known as rgreening === boomer is now known as Guest20284 [04:52] 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:52] Launchpad bug 293360 in ubuntu "[needs-packaging] Project Looking Glass" [Undecided,New] [04:53] matthewi: ill get it [04:53] thx [05:02] hash mismatch on an official mirror using apt? Probably a support request and not a bug, right? [06:15] good morning [06:19] good morning dholbach [06:19] hey thekorn === LucidFox is now known as LucidFox_TDK === thekorn_ is now known as thekorn [08:06] Hi all, I would like some launchpad bug management assistance. [08:07] 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:07] Bug 219274 on http://launchpad.net/bugs/219274 is private [08:09] 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] mr-russ, let me check this bug [08:12] thanks. [08:13] yes, they're subscribed. [08:14] Reported by riventree (grendel-riventree: 13) on 2008-04-19 (Activity log) [08:15] hmm, Hobbsee seems to be faster than me, [08:15] anyway, removed private flag from bug 219274 [08:15] Launchpad bug 219274 in php5 "php5 crashed with SIGSEGV in CRYPTO_lock() (dup-of: 147207)" [Undecided,New] https://launchpad.net/bugs/219274 [08:15] Launchpad bug 147207 in php5 "gutsy php5 crashed with SIGSEGV in CRYPTO_lock()" [Medium,New] https://launchpad.net/bugs/147207 [08:16] now to prove my hunch that all these bugs are really #63141 [08:18] thanks all for your fast response. It's always a good experience visiting ubuntu-bugs. [08:51] 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] or libpq to be exact. [08:58] mr-russ, Just adjust the package. It ought be an option as if you were adjusting the status. === LucidFox_TDK is now known as LucidFox [09:05] 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] 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] persia: and that mail spam the people who are subscribed to the other task too [09:21] I think I just mailspamed people as I don't know how to bulk move duplicates to a new parent. [09:22] mr-russ: there's no bulk moving of duplicates [09:23] you have to move them all individually. [09:23] so you probably did mailspam. However,if you did it quick enough, launchpad tends to cache mails. [09:23] ah. [09:25] Is somebody willing to mark bug #63141 as triaged? It's as good of a report as it's ever going to get :) [09:25] Launchpad bug 63141 in php5 "PHP (cli) exits with a segfault if pg_connect() called." [Low,Confirmed] https://launchpad.net/bugs/63141 [09:27] Can I subscribe to receive new bugs from just one package? [09:28] mr-russ: yes, you can [09:29] go to https://bugs.launchpad.net/ubuntu/+source/xyz (replace xyz with the package name) [09:29] and click on "subscribe to bug mail" [09:29] is this what you wanted? [09:29] does that send me all bug mail for that package? or just new bug reports? [09:30] Should send you all bug mail for the package. [09:30] Yeah, I was hoping for just new reports. I suspect mail from 1 package is not huge though. [09:31] Depends on the package, but if it's huge, you'd be able to guess before you subscribe :) [09:31] it's php, I'm not willing to subscribe to the mozilla/firefox package. The thought is scary! [09:32] 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] 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] 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] seb128, Yeah. I agree that most of the time it's not a good idea. [09:34] 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] 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] 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] 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] fixing postgressql to not crash is a good thing. Fixing php to not crash when postgressql crashes is possibly also wise. [09:46] and fixing curl when openssl calls a callback :) [09:46] 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] Indeed. Lots of bugs to fix there :) [09:55] 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] No, those are different packages, I think the old ones are either from earlier releases, or for people who need backward compatibility. [09:59] the bug affects all version, do I add all those packages to the affected packages for the bug? [09:59] sorry for all the questions, it's not simple to understand all this stuff. [10:00] No. Only add the current package. The old ones are unlikely to be fixed. === slacker_1l is now known as slacker_nl [10:50] reminder: it's bug day today! [11:04] bug? restart doesn't really work. computer reboots and gets stuck just before loading grub [11:07] unenough: what do you mean "stuck"? i may be a problem with your grub menu file... [11:07] no, it works when i shutdown [11:08] only when i reboot, that is, power doesn't shutdown completely, does this occur [11:09] and only when i reboot from linux. rebooting from windows works [11:23] unenough: ok, and what do you mean stuck? what do you see? error messages? [11:23] unenough: what kind of machine is that? what chipset/cpu? [11:24] i see nothing. blank text screen with blinking cursor [11:25] Toshiba Satellite A215 [11:25] (laptop) [11:33] unenough: file a bug report under grub, and paste the link here [11:45] mvo, I'm pretty sure the bug has nothing to do with grub [11:46] the problem is how the linux kernel performs a reboot on this machine [11:53] 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] Are there any bug control admins here? [12:12] nhandler: I believe pedro_ is [12:13] pedro_: Could you renew my Bug Control membership? [12:13] yes i'm here, nhandler can i help you with something? [12:13] nhandler: sure, give me a few mins [12:13] Thanks pedro_ [12:17] nhandler: done, thanks you! [12:18] Thanks again pedro_! === maio_ is now known as ma10 [12:21] hmmm. are any hardy systems actually running cron, if they've enabled & disabled the root account? [12:41] hi all, I just changed some stuff at https://wiki.ubuntu.com/DebuggingProgramCrash [12:41] I wanna know [12:41] a. On which of the bug lists should I report this change? [12:42] ubuntu-bugs@ [12:42] 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] Hobbsee: thank you [12:43] shirish: by using the default? [12:43] shirish: would help if you learned to spell 'feisty', too, before you put it into the documentation. [12:45] Hobbsee: would look if I did some mistake in the spellings [12:45] Hobbsee: I tried the default given there [12:46] Most keyservers synchronize with each other, so there is gener‐ [12:46] ally no need to send keys to more than one server. The keyserver [12:46] hkp://subkeys.pgp.net uses round robin DNS to give a different [12:46] keyserver each time you use it. [12:46] gpg --recv-key 428D7C01 [12:46] gpg: no keyserver known (use option --keyserver) [12:46] 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] sarah@neptune:~% gpg --recv-key 428D7C01 11:46PM [12:47] gpg: requesting key 428D7C01 from hkp server subkeys.pgp.net [12:47] gpg: key 428D7C01: "Ubuntu Debug Symbol Archive Automatic Signing Key " not changed [12:47] gpg: Total number processed: 1 [12:47] gpg: unchanged: 1 [12:47] works for me. [12:47] Hobbsee: does that have an issue with dhcp or something? [12:47] no? [12:48] why did you put the time 11:46 PM, does one need to give time as well? [12:48] no, it's just part of my .zsh. [12:49] Hobbsee: ah ok, its saying gpg: keyserver receive failed: bad URI [12:50] doesn't look to be a commonly found issue - no one's reported it [12:50] Hobbsee: please lemme know what can I do to resolve it? [12:51] hmmm. Some people have. [12:51] on the forums. [12:52] hmm, not only on the forums. Just no one's filed a bug. [12:52] shirish: am I really your personal google searcher? [12:52] shirish: or are you just lazy? [12:52] Hobbsee: no, just lemme know which package should I file this against, gpg or something else? [12:52] gnupg, i expect. [12:53] 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 === murdok_ is now known as murdok [14:40] Boo === tad is now known as rrittenhouse === dholbach_ is now known as dholbach [16:21] seb128 ping [16:21] hggdh: hi [16:22] hi seb128 I am building a PPA for E-D-S for bug 205999 [16:22] Launchpad bug 205999 in evolution "Attachments names using "ç" are not correctly sent by Evolution (ATT.dat)" [Unknown,Confirmed] https://launchpad.net/bugs/205999 [16:22] ah good [16:22] Milan has proposed a patch, and it is asking for tests on it [16:22] this will be (right now) for Intrepid [16:22] right, I read your comment on the bug [16:23] do you think that's worth a sru? [16:23] oh, OK [16:23] I think it might -- this has a good impact [16:23] (usability) [16:24] ok, should be easy to find a sponsor for the update [16:31] seb128, I will prepare a debdiff for Hardy [16:32] hggdh: thanks [16:37] OK, question for anyone familiar with PPA & etc: my build failed with "gawk: command not found" for Evolution-data-server [16:37] I expected gawk would be part of the base systems [16:38] me too :) [16:38] but it isn't [16:38] package should build depend on gawk [16:38] so I have to add a depends for gawk... [16:39] thanks. Still weird -- this is a debdiff from e-d-s... how did it build originally then? [16:39] hggdh: the intrepid source should build fine in an intrepid environment that's weird [16:39] are you sure that's the issue? [16:39] do you have the build log url? [16:40] seb128, yes -- http://launchpadlibrarian.net/19342549/buildlog_ubuntu-intrepid-amd64.evolution-data-server_2.24.1-0ubuntu1ppa3_FAILEDTOBUILD.txt.gz [16:41] it did that on all archs? [16:41] I will check the others now [16:42] also failed the same on lpia and i386 [16:42] hggdh: what is your ppa page? [16:43] https://launchpad.net/~hggdh2/+archive [16:43] hggdh: gawk is not installed in other builds either bug that doesn't break the build [16:44] did you run autotools or something? [16:44] no -- I got your latest source, and just added the patch + debuild -S [16:44] $ debdiff evolution-data-server_2.24.1-0ubuntu1.dsc evolution-data-server_2.24.1-0ubuntu1ppa3.dsc | diffstat [16:44] Makefile | 3007 +++++++++++++++++++ [16:44] config.log | 4047 ++++++++++++++++++++++++++ [16:44] config.status | 1669 ++++++++++ [16:44] debian/patches/70_bug524377.patch | 86 [16:44] evolution-data-server-2.24.1/debian/changelog | 22 [16:45] libdb/Makefile | 660 ++++ [16:45] 6 files changed, 9491 insertions(+) [16:45] no you didn't [16:45] you got autotools running [16:45] I certainly did not ask for it [16:45] clean the other changes and try again [16:45] k [16:45] ah [16:45] you didn't edit any makefile* or ran autogen.sh? [16:46] nope -- but I did debuild binary before generating the ppa [16:46] maybe a cruft [16:46] left by the binary build [16:46] sometime the autotools are automatically called [16:46] yes [16:47] but usually that's when a autotools file timestamp changed [16:47] I will save the ./debian, and reinstall the orig.tar [16:47] ie if you editing one for some reason [16:47] right [16:47] untar the tar.gz and copy the debian directory [16:47] yup [16:47] I really expected a debuild -S to clean up [16:49] saivann: the -proposed version of rhythmbox is working for me now [16:57] oh, oh, the pains caused by ignorance... ;-) [16:58] 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] 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] yes, I had just realised it... again I forgot a basic rule: *always* start with clean sources [16:59] last time it was with coreutils [16:59] saivann: I did notice the file I copied over had no id3 tag though. Does that happen to you too? [17:22] paging Alberto Milone === macd_ is now known as macd [18:23] ogasawara: does bug 193970 only affect iwl3945 and iwl4965? Is there another bug for other drivers? [18:23] Launchpad bug 193970 in ubuntu-release-notes "iwl3945 | iwl4965: Wireless can't be activated after disabling kill switch" [Undecided,Fix released] https://launchpad.net/bugs/193970 [18:24] bdmurray: I believe that is the only bug, is there another driver reporting this issue? [18:24] I'm looking at bug 292280 where they mention iwlagn [18:24] Launchpad bug 292280 in ubuntu "rfkill switch doesn't work properly" [Undecided,New] https://launchpad.net/bugs/292280 [18:25] bdmurray: I'd assume that'd be a dup of 193970 === Guest81984 is now known as WelshDragon [18:27] bdmurray: I'm going to go ahead and mark it as a dup, unless you want to [18:28] ogasawara: feel free just mark it off the hug day list! ;-) [18:28] bdmurray: ok [18:28] perhaps updating the title of 193970 would be good too === LimCore_ is now known as LimCore [19:12] Anybody know where the technical overview for intrepid is now? [19:13] I found it [19:13] hey [19:13] i got some bugs :( [19:14] Have you found out if they are reported in Launchpad? [19:14] himm i dont think so [19:14] it is about the pidgin and [19:14] the gedit [19:15] the pidgin if the compiz runnig it stuck :( [19:15] and every thing deleted :S [19:17] silentz: I'm running into an (unreported) issue re: Pidgin and memory leaks [19:17] thats good notice that i have 2.5.2 [19:17] Run the command "top" in a window and press "m" to sort by memory usage. [19:17] the 2nd thing with the gedit [19:17] when i open any file small of big [19:18] it start sooo slow [19:18] then it work good [19:18] Check your memory usage for pidgin. I think that's the crux of your issue. [19:19] i have a very good PC [19:19] with good specification [19:19] i dont think it is a memory problem [19:19] i have used 8.04 [19:20] with no problem in gedit [19:20] but pidgin from the existence of 2.5.0 untill 2.5.2 [19:20] If i want to make a suggestion...Do i just report a bug and then change the importance to Wishlist? [19:21] WelshDragon: it depends on the scope of the suggestion [19:21] WelshDragon: What do you have in mind? [19:22] himmm [19:22] not really [19:22] 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] i like ubuntu but some time really dont like these small bugs :( [19:24] WelshDragon: I'm not sure that falls with-in the applications scope, but that is something you could submit in Launchpad. [19:25] bdmurray, Submit it as a bug report though? [19:25] man i'm tooo lazy to make a report with my bad english :D [19:26] WelshDragon: yes [19:26] bdmurray, OK. Thank you :) [19:26] WelshDragon - i agree with bdmurray about your idea perhaps being outside of the scope for gdebi-gtk [19:27] i think it would be counterintuitive to have to double click on a .deb package in order to uninstall it [19:27] that's what synaptic is for;) [19:27] The package description also says 'Simple too to install deb files' [19:28] 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] i don't really think it should have any other features tbh [19:31] i have a suggestion :D [19:31] why dont we make a shortcut [19:31] in the Right click list [19:31] the said uninstall [19:32] without making a new package dedicated for uninstalling :D [19:32] like in linux mint [19:33] ?? [19:34] 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] yea i know [19:35] but the user like that should keep [19:35] the .deb :S [19:35] but making a shortcut for the user to right click on the programme then uninstall it would be better [19:35] Right ? [19:36] and it is oky to make both the button and my idea also :) [19:36] 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] yea it is a good point but we can solve if with .... [19:38] >>> hard to explain :S [19:38] making the debian file check himself [19:39] in where it is installed only [19:39] if so the button if enabled [19:39] >< Already been suggested *bonk* [19:39] if not button is disables [19:39] Right ? [19:41] 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] come on guys, today is bug day. quit wasting time about whether gdebi should uninstall packages and solve some bugs! :-P [19:41] himmm [19:41] yea Right man [19:42] i think i'm disturbing you [19:42] i'm really newbie in linux world >> just one year [19:42] c ya soon : - D [19:43] e.g. i have no clue where to start with this one: https://bugs.launchpad.net/ubuntu/+bug/293061 [19:44] Launchpad bug 293061 in ubuntu "The input text field of firefox is too wide/long" [Undecided,New] [19:48] azimout1 - i can't reproduce bug 293061 [19:48] Launchpad bug 293061 in ubuntu "The input text field of firefox is too wide/long" [Undecided,New] https://launchpad.net/bugs/293061 [19:48] maybe it's locale related? [19:48] could you get the reporter to try running firefox with a different locale and see if it goes away? [19:48] I can't reproduce either. english locale. [19:48] something like "LC_ALL=en_US.UTF-8 firefox" [19:49] i know, i can't reproduce it either [19:49] but he has the problem also in eclipse [19:49] 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] yeah, the eclipse/FF problems might be related [19:50] ok, i will, thanx === gaspode is now known as gaspode_ === gaspode_ is now known as gaspode__ === gaspode__ is now known as gaspode [19:59] ogasawara: hi! are you aware of any IO issues with 2.6.27, maybe or maybe not related to LVM? [19:59] ogasawara: after upgrading to intrepid I seem to have all kinds of IO contention [19:59] jdstrand: not that I'm aware of but I'm still going through some newer bug reports [19:59] (esp during builds or using VMs) [20:00] ogasawara: I'll file one if I can get anything more specific than 'it feels a lot slower' [20:00] jdstrand: although I do recall something from kees, just a sec [20:00] jdstrand: but he mentioned it was eventually resolved with an update [20:00] ogasawara: we've both been complaing to each other... [20:01]