UbuntuIRC / 2008 /07 /23 /#ubuntu-bugs.txt
niansa
Initial commit
4aa5fce
=== nhandler is now known as nhandler_AFK
=== mcasadevall_ is now known as NCommander
[06:09] <Hew> bug #224366 is a dupe but I can't find the original bug. It's that issue where an app can't access the sound device because it's in use by pulseaudio. eg, flash videos don't play while rhythmbox does. Surely it's a big bug somewhere; can anyone find it?
[06:09] <ubottu> Launchpad bug 224366 in quodlibet "Quod libet and flashplugin-nonfree conflict over sound" [Undecided,New] https://launchpad.net/bugs/224366
[06:12] <Rocket2DMn> Hew, i think youre right, but i dont think its with flashplugin-nonfree specifically
[06:12] <Hew> yea I think it was pulseaudio
[06:12] <Hew> I know Wine gets blocked too
[06:13] <Hew> ah, I think this is it: bug #183917
[06:13] <ubottu> Launchpad bug 183917 in libflashsupport "Sound stops working in Firefox once other applications (Pidgin, Rhythmbox) have played sound" [Low,Confirmed] https://launchpad.net/bugs/183917
[06:14] <Hew> sorting reports by number of duplicates really helps :-)
=== fdd is now known as mem
=== mem is now known as core0
=== core0 is now known as fdd
[07:57] <NCommander> Why is grabbing the Session causing mod_python to crash
=== seb128_ is now known as seb128
[13:54] <philsf> how can I set status of a bug per release?
[13:55] <philsf> I "nominated" the bug for hardy and intrepido, but can't find where to set the status for each
[13:55] <philsf> https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/128074
[13:55] <ubottu> Launchpad bug 128074 in poppler "strange font behaviour - connected letters" [Low,Fix committed]
[13:56] <philsf> Bug #128074 is "Fix Released" for Intrepid, and "New" for Hardy.
[13:56] <ubottu> Launchpad bug 128074 in poppler "strange font behaviour - connected letters" [Low,Fix committed] https://launchpad.net/bugs/128074
[14:00] <james_w> philsf: you can only do that once it has been approved
[14:00] <james_w> nominating means that it shows up on a list for consideration, from which it will be either accepted or declined. If it is accepted then you can change the status in each release.
[14:01] <philsf> oh.. you sound as if I shouldn't have done it..
[14:01] <philsf> sorry for that
[14:02] * philsf feels like a kid that dropped something
[14:02] <seb128> philsf: I doubt it'll be accepted, that's not a trivial change and the comments indicate it's not perfect, not something for stable updates
[14:03] <james_w> philsf: I didn't mean that, sorry if I gave that impression.
[14:04] <philsf> seb128: I see. I still think it's important that this is fixed, especially in an LTS release. the LTS should be the one used in academic workplaces, but this is really a stopper for newbies.
[14:04] <seb128> philsf: well if there is a solid patch available I'm not against it but so far nobody suggested one
[14:05] <philsf> of course one could use one of the plethora other choices for pdf readers, but in gnome, they are all slower than evince
[14:05] <philsf> seb128: I see. thanks for your comments, though. can I revert the improper nomination?
[14:06] <seb128> not sure, I've the privileges to accept or refuse those so I don't know what interface the people who don't get
[14:06] <philsf> james_w: no worries. I should have read.... something... before messing with bug statuses
[14:06] <seb128> but just wait for somebody to accept or reject it that's no issue
[14:06] <philsf> maybe this should be accepted, and turned hardy state to invalid?
[14:08] <philsf> I just posted the informative last post to upstream, so they see the new screenshot, and know about the still wrong "fi" string problem. maybe if there's a fix, someone can backport the patch to poppler 0.6.4
[14:08] <philsf> k, thanks sebastian
[14:09] <pereza> Hi. that is a problem for new peple when working with bugs. Sometime I say to myself if it is ok to change thing in the bug report
[14:09] <seb128> philsf: did you try in intrepid using 0.8? does it work correctly on this version?
[14:10] <philsf> seb128 I can't install intrepid right now, and have no time to learn about VMs, sorry
[14:10] <philsf> not that I wouldnt like it
[14:10] <seb128> maybe you can download a liveCD and give it a try?
[14:10] <seb128> no need to install
[14:10] <philsf> seb128: how could I forget that...
[14:11] <seb128> philsf: see, there is always a solution ;-)
[14:12] <philsf> pereza: yeah, maybe lp could have some help links or ballons
[14:12] <philsf> new alpha tomorrow? I'll do it then
[14:14] <pereza> question here, bug 224589, do we need to know which version of ubuntu he/she is running?
[14:14] <ubottu> Launchpad bug 224589 in apt "apt-get --only-source does not work" [Undecided,New] https://launchpad.net/bugs/224589
[14:19] <pereza> philsf, any ideas?
[14:27] <philsf> pereza: can you reproduce it?
[14:30] <philsf> pereza: I always assume bug reporters are using the latest release at the time of the posting. people who are lazy enough to upgrade, aren't exactly the most common bug reporters
[14:30] <philsf> nevertheless if you(someone) can reproduce it in hardy, that's what counts
[14:41] <pereza> philsf, thanks for the info
[15:21] <Jazzva> jcastro, ping
[15:22] * persia generally encourages contentful pings, even when only one person can be any help at all.
[15:23] <jcastro> Jazzva: yo!
[15:23] <Jazzva> ok :)
[15:24] <Jazzva> jcastro, could you please prolong my membership in ubuntu-bugcontrol. I received notification that it's about to expire
[15:24] <Jazzva> persia, thanks for the advice...
[15:24] <jcastro> Jazzva: one moment
[15:25] <Jazzva> jcastro, ok
[15:25] <jcastro> hmm, I have no idea how to do that
[15:26] <persia> Jazzva: Can you not extend it yourself?
[15:26] <jcastro> I don't see anywhere in the UI on how to manage membership length in a team
[15:26] <Jazzva> persia, I'm not sure I can...
[15:27] <jcastro> I think when it expires it sends you a mail to extend?
[15:27] * persia looks at the new UI, having done this before
[15:27] <Jazzva> persia, nope... I think administrator only can do that.
[15:27] <Jazzva> *only administrator
[15:28] <Jazzva> jcastro, https://edge.launchpad.net/~ubuntu-bugcontrol/+members , there should be a pen icon on the right of every row. My name is Saša Bodiroža, so you can search with that
[15:28] <persia> Jazzva: What do you get when you visit the team page in LP? I think you should get a menu item to renew.
[15:28] <jcastro> ah, I see it, thanks
[15:29] <persia> jcastro: As an admin, if you show all members (/+members) you can edit specific members.
[15:29] <james_w> jcastro: hi, could you extend mine while you are at it please?
[15:29] <Jazzva> pereza, I can't find that option.
[15:29] <jcastro> yep, found it, you're all set Jazzva
[15:29] <Jazzva> ups, persia
[15:29] <james_w> hi persia
[15:29] <persia> james_w: Hi
[15:29] <Jazzva> jcastro, thanks :)
[15:29] <jcastro> james_w: all set
[15:29] <james_w> great, thanks.
[15:56] <jonpackard> I'm trying to run a backtrace using gdb for a problem in Tomboy.. I'm getting an error about /usr/bin/tomboy not being an executable.. could anybody please help me with this please? See http://pastebin.com/f64be32fd for full output. Thanks!
[15:59] <persia> jonpackard: tomboy is a bash script. You might find more information there about how to get a trace.
[16:00] <persia> That said, you may do just as well to turn on apport and report it that way (see https:/wiki.ubuntu.com/Testing/EnableProposed for instructions on activating apport
[16:01] <jonpackard> persia: thanks! I'm actually confirming bug 250502 and wanted to include a backtrace for more info
[16:01] <ubottu> Launchpad bug 250502 in tomboy "Tomboy crashes when creating a new notebook" [Undecided,Incomplete] https://launchpad.net/bugs/250502
[16:03] <persia> jonpackard: If you can discover a good generic way to do it, it might be good to add some information on how to debug Mono apps. As much as I like backtraces, I'm not sure how to get a good one for those.
[16:10] <seb128> the current handling of mono crashes is not good
[16:10] <seb128> getting a gdb stacktrace of the mono interpreter is usually not that useful
[16:11] <seb128> would be nice if somebody could write special handling for mono crash, similar to what is done for python crashes
[16:12] <seb128> also GNOME crashing is likely either a gnome-session or xorg bug
[16:13] <NCommander> seb128, well, right now, a big mono fix for a lot of the random segfaults went in
[16:13] <NCommander> (it was caused by some "genius" commenting out an entire block of code; I rewrote the patch to do it right, and it went upstream"
[16:13] <seb128> ah, good to know
[16:15] <NCommander> yeah
[16:15] <NCommander> I want to backport to Hardy
[16:15] <NCommander> But I haven't been able to find or write a test case that proves its affected beside having the same braindead code fix
[16:15] <jonpackard> Thanks for the help. Which package provides Mono? I want to include that when I confirm the bug about Tomboy.
[16:16] <NCommander> jonpackard, mono provides mono ;-)
[16:16] <NCommander> postscript is an ASCII format, right?
[16:17] <jonpackard> jon@bjh34kj54b:~$ apt-cache policy mono
[16:17] <jonpackard> mono:
[16:17] <jonpackard> Installed: (none)
[16:17] <jonpackard> Candidate: (none)
[16:17] <jonpackard> Version table:
[16:17] <jonpackard> =(
[16:18] <seb128> jonpackard: mono-jit
[16:18] <persia> postscript may be unicode, but is usually also ASCII
[16:18] <persia> (or rather UTF8)
[16:19] <jonpackard> seb128: Thanks! That did the trick. :)
[16:23] <NCommander> the wiki running slow >.<;
[16:23] <NCommander> I finished the inital report though
[16:23] <seb128> yeah, the wiki is always slow apparently
[16:24] <NCommander> seb128,
[16:24] <NCommander> er
[16:25] <NCommander> bah
[16:25] <NCommander> https://wiki.ubuntu.com/MainInclusionReportlibspecrte
[16:25] <seb128> NCommander: you typoed the title ;-)
[16:25] <NCommander> Not a great way to start this off
[16:26] <NCommander> There won't be an easy way to rename a page?
[16:26] <seb128> NCommander: there is
[16:26] <NCommander> I don't see alink
[16:26] <seb128> the other actions combo has it
[16:36] <bdmurray> ogasawara: I've found a new kernel bug w/o a package should it just go straight to linux?
[16:36] <bdmurray> ogasawara: or should a 2.6.22 task be opened?
[16:48] <bdmurray> ogasawara: did you see my question?
[16:49] <ogasawara> bdmurray: I didn't, what was it?
[16:50] <bdmurray> I saw a gutsy kernel bug w/o a package and wasn't sure if it should go straight to 2.6.22 or linux
[16:50] <ogasawara> bdmurray: I'd push it to linux and ask for testing against hardy
[16:51] <bdmurray> well, I've lost the bug now but okay ;)
[17:56] <bdmurray> thekorn: your greasemonkey script is really neat
[18:17] <bdmurray> mvo: have you seen that tomorrow is a hug day for apt?
[18:18] <mvo> bdmurray: no, that is nice, I look forward to it
[18:24] <bdmurray> mvo: could you look at bug 228127?
[18:24] <ubottu> Launchpad bug 228127 in synaptic "phrasing in download dialog is incorrect" [Low,In progress] https://launchpad.net/bugs/228127
[18:25] <mvo> bdmurray: sure
[18:26] <bdmurray> mvo: its already for fixing! ;)
[18:27] <mvo> bdmurray: thanks, commited to my main branch
[18:31] <bdmurray> mvo: great, thank you!
[18:33] <mvo> bdmurray: thank you! it will be part of the next regular upload
[18:33] <bdmurray> mvo: bug 209049 too
[18:34] <ubottu> Launchpad bug 209049 in unattended-upgrades "Spelling Mistake in 50unattended-upgrades" [Wishlist,Fix committed] https://launchpad.net/bugs/209049
[18:36] <mvo> bdmurray: done
=== mdz_ is now known as mdz
[18:54] <mouz> I forwarded a bug upstream, but now i'm not sure how to link to the remote bug. I'm confused by the existence of tasks already and also I'm not sure what is a 'project' and what is a 'distribution' in this context. Would like some help :) bug 239926 Thanks.
[18:54] <ubottu> Launchpad bug 239926 in firefox-3.0 "middle button to open a new tab" [Wishlist,Incomplete] https://launchpad.net/bugs/239926
[18:54] <persia> mouz: To where did you forward it?
[18:55] <mouz> persia: bugzilla.mozilla.org
[18:55] <persia> URL?
[18:55] <mouz> https://bugzilla.mozilla.org/show_bug.cgi?id=447646
[18:56] <ubottu> Mozilla bug 447646 in History "middle button and hold on history to open new tab" [Enhancement,Unconfirmed]
[18:56] <bdmurray> mouz: https://wiki.ubuntu.com/Bugs/Watches
[18:56] <persia> mouz: OK. You'll notice that the bug has two tasks: one for Ubuntu, and one for Upstream.
[18:56] <persia> If you click the little arrow to the left of the Upstream task (the top one), it will provide an entry box for you to put that URL.
[18:57] <mouz> persia: yes (bdmurray i will read it later thanks)
[18:57] <mouz> yes
[18:58] <mouz> persia can i trust that small icon left of the first row is saying 'this is an upstream task'?
[18:59] <persia> mouz: Not quite. The distribution tasks are of the form "package (distribution)". The project tasks are of the form "project name". Ideally, each project is upstream, although there are a couple exceptions remaining to be cleaned up.
[19:01] <mouz> persia: persia: ok. so just past the URL after 'URL:'?
[19:01] <mouz> s/past/paste/
[19:02] <persia> mouz: I believe that should work. You might also have to adjust the radio button.
[19:02] <persia> Check the status of the main page and make sure there is a link under "Assigned" to verify.
[19:02] <mouz> persia: yes. thanks. it looks right now.
[19:04] <mouz> still i do not really understand what is a project, what is a distribution...
[19:05] <persia> mouz: A project is a collection of code creating one or more associated applications that work in a variety of environments.
[19:05] <persia> Examples include ardour, open office, mozilla, tkgate, etc.
[19:05] <persia> A distribution is a collection of projects and glue to build a complete operating environment for a computer.
[19:06] <persia> When tracking bugs, we distinguish between the status in Ubuntu (the distribution) and the status upstream (the project) as something may be fixed in one place first, and someone may need to manually migrate the fix into the other.
[19:09] <mouz> persia: What would be a reason to ever add a distrotask for another distribution then Ubuntu (if there is any)?
[19:11] <persia> mouz: Well, it might be that Ubuntu wants to track something in an upstream distribution (e.g. Debian), or a downstream distribution (e.g. Baltix) wants to track Ubuntu.
[19:12] <persia> Remember, while LP is often used for Ubuntu, it is also used for other projects and distributions.
[19:14] <mouz> Ok I understand now. Thanks persia. bdmurray thanks a lot for the link, I will read it now.
[19:26] <thekorn> bdmurray, I'm glad you like the gm script,
[19:27] <thekorn> my next plan is to add some black/whitelist to this script
[19:27] <thekorn> but than it should be complete
[19:28] <bdmurray> cool, well let me know and I'll merge it. If you could update the README too that would be outstanding
[19:29] <thekorn> yes will do so in the next days
=== mcas_away is now known as mcas
[20:16] <sectech> Has anyone heard of any bugs trying to run intrepid on vbox?
[20:21] <bahadunn> sectech: by vbox do you mean virtualbox?
[20:22] <sectech> yup
[20:22] <sectech> I tried alpha-2 and the nightly... I get a kernel panic each time
[20:35] <jonpackard> sectech: see bug 246067
[20:35] <ubottu> Launchpad bug 246067 in linux "Kernel panic during boot after upgrading to kernel 2.6.26.3-generic" [High,Confirmed] https://launchpad.net/bugs/246067
[20:36] <jonpackard> 2.6.26-2 and earlier seem to work most of the time
[20:37] <sectech> Kinda hard to triage when you can't install the distro lol
[20:38] <sectech> jonpackard, Thanks.... I'll tinker around with it a bit later
[20:51] <jonpackard> sectech: DO you have a VT-x or AMD-V capable processor? I've heard that enabling that function in virtualbox sometimes allows a successful boot on the latest Intrepid kernel
[20:56] <sectech> jonpackard, I tried with that option on.... It crawls.
=== geser_ is now known as geser
[21:21] <jonpackard> sectech: weird.. isn't that supposed to improve the virtualization performance and compatibility?
[21:25] <bdmurray> nellery: hey there
[21:25] <nellery> bdmurray, hi
[21:26] <bdmurray> Have you seen this debian-bug-search script I wrote? I think it'd be handy for the bug day
[21:27] <nellery> bdmurray, I believe I saw it on planet
[21:27] <nellery> I'll take a look at it
[21:28] <bdmurray> cool, I thought it might deserve a blip on the targetted bug list
[21:28] <bdmurray> Oh, by the way I usually sort the New bugs by highest number first
[21:28] <bdmurray> So the "fresh" ones are at the top
[21:29] <nellery> bdmurray, woops, I think I forgot to put the dash in -nr
[21:29] <nellery> I probably did --sort:nr
[21:29] <nellery> I'll change that
[21:31] <bdmurray> nellery: cool, thanks!
[21:34] <nellery> no problem
[21:38] <greg-g> ooo, new LP coming out?
=== mcas is now known as mcas_away
[21:51] <jthan_> I just joined Launchpad and the Ubuntu BugSquad, I haven't really gotten into any programming yet but I'm interested in it. How much would I need to know before I begin with a mentor?
[21:54] <Iulian> jthan_: First of all you don't need to know any programming language to work with bugs but if you know it will help you.
[21:54] <jthan_> lulian: what is required then?
[21:55] <jthan_> lulian: I would LIKE to get into programming though, but anywhere is a start.
[21:55] <Iulian> jthan_: Well, just read our wiki page (see the topic). If you have any more questions, feel free to ask here.
[21:55] <Iulian> jthan_: This channel is for Ubuntu bugs only.
[21:57] <Iulian> bdmurray: ping
[21:58] <bdmurray> Iulian: pong
[21:59] <Iulian> bdmurray: Hi there. My membership for bug control team is about to expire in a few days. Could you please renew it?
[22:02] <_gunni_> Is there a possiblity to push a bug? There is a bug, assigned, confirmed, and patch is inside the launpad entries (Just one line of code), but isnt fixed for some time.
[22:05] <Iulian> _gunni_: Which bug?
[22:07] <_gunni_> https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/204624
[22:07] <ubottu> Launchpad bug 204624 in linux-restricted-modules-2.6.24 "CAPI not working correctly on Ubuntu hardy (8.04)" [Undecided,Confirmed]
[22:13] <_gunni_> Iulian: Patch is in this post, just to make it easier: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/204624/comments/11
[22:13] <ubottu> Launchpad bug 204624 in linux-restricted-modules-2.6.24 "CAPI not working correctly on Ubuntu hardy (8.04)" [Undecided,Confirmed]
[22:14] <bdmurray> Iulian: you are all set
[22:32] <bdmurray> ogasawara: any ideas about 21481?
[22:33] <ogasawara> bdmurray: whoa, 2.6.12
[22:33] <bdmurray> eh, I think it has been hijacked
[22:35] <bdmurray> starting around comment 16
=== NicNack is now known as NickNak
[23:54] * calc hugs the people who wrote the greasemonkey scripts, they rock! :)
[23:56] <bdmurray> ;)
[23:57] * greg-g needs to remember to update those soon, he's must be broken, because everyone has 0 karma :)
[23:57] <bdmurray> Yeah, I fixed that last week
[23:57] <bdmurray> You might as well wait until after the next roll out though as I suspect some stuff will break again
[23:57] <greg-g> yeah, figured
[23:58] <greg-g> i haven't been doing a ton of triaging lately anyways
[23:59] <sbeattie> bdmurray: did you push your mutt scripts to bzr somewhere?
[23:59] <bdmurray> not yet
[23:59] <bdmurray> sbeattie: is there one in particular you are intereseted in?