=== rbs-tito_ is now known as rbs-tito [03:31] should i close bug 234015? as it seems to be a specific faulty hardware issue [03:31] Launchpad bug 234015 in pybluez "blueproximity is unable to find bluetooth devices" [Undecided,New] https://launchpad.net/bugs/234015 === asac_ is now known as asac === jacob is now known as jacob[vacation] [08:33] mp [08:33] oops === dodger_ is now known as Hurtz [09:09] hello [10:27] can someone help me out on bug 229477 ? [10:27] Launchpad bug 229477 in hal "most of the laptopkeys don't work " [Undecided,In progress] https://launchpad.net/bugs/229477 [10:27] I don't know what part is responsible for keeping track of the status of the CD/DVD-drive, lshal -m didn't show anything here [10:28] what should I ask him for? === _neversfelde is now known as neversfelde [10:48] qense: that may happen if some process is accessing the cdrom [10:49] qense: my first question would be: is there a cd in the drive? [10:49] aargh! of course [10:49] I forgot that [10:49] qense: and if there is a cd in the drive, lsof | grep cdrom may tell what is keeping the drive busy [10:50] and where there isn't? Isn't the closure and opening of CD/DVD drives monitored by the hardware itself? [10:51] qense: I tried the lshal -m trick, but that didn't say anything for me either [10:51] so I guess the hardware may handle the key directly indeed [10:52] ok, thx [12:04] Hey hows the global bug hunt going? [12:32] Hey, would the following qualify as a "wishlist"? https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/238303 [12:32] Launchpad bug 238303 in pm-utils "Please merge pm-utils 1.1.2.2-1 from Debian unstable main" [Undecided,New] [12:37] I wouldn' touch it [12:37] I think it's a workflow bug [12:37] since the universe sponsors are subscribed to it [12:38] main sponsors * [12:38] there were some pretty heavy discussions about workflow bugs lately and some people got angry [12:38] this kind of bugs are used to keep track of things the people who maintain the packages have to do [12:40] oops, I forgot to ping ciaramooney ;) [12:40] now I've did [12:40] done! [12:40] Lol. Thanks. [12:41] ;) [12:47] qense: I have a question. When a bug is triaged as "incomplete" launchpad says something like "If nothing happens in 60 days then it will be close" or something. Does this mean that the bug eventually gets taken off the tracker or at least "closed" [12:47] ? [12:48] they planned to mark the bug as invalid after 60 days [12:48] but if I'm right they disabled it and now stops couting down at 59 days to go [12:49] so it remains on the tracker, and has to be closed manually at some point? [12:49] yes [12:49] but there's some discussion about that [12:49] some people say a bug should never be markes as invalid unless it's not a bug or doesn't happen(anymore) [12:50] others say that inactive bugs take valuable space in search lists and make things harders/longer for people [12:50] the triage guide advices to close a bug after there hasn't been a response for more than a month after the last comment [16:54] morning [16:57] hello [17:04] hello! [17:36] maybe a compromise should be reached along the lines of "dont mark expired bugs invalid, but do hide them from default searches === bureflux is now known as afflux [19:49] oh thats annoying [19:49] gnome bugzilla marks dups invalid and LP doesn't migrate to the dup [19:50] oh thats interesting [19:50] the dup also has a partner on LP [19:51] if one was to trust upstream bug trackers, one could automatically suggest dups in LP === ember_ is now known as ember [21:14] hi all~ how should 'X needs packaging' bugs be dealt with? [21:14] https://bugs.launchpad.net/ubuntu/+bug/238170 [21:14] Launchpad bug 238170 in ubuntu "Please sync farsight2 0.0.2-1 (universe) from Debian experimental." [Undecided,New] [21:35] Awsoonn: that is a workflow report so unless you really know what you are doing you probably shouldn't touch it [21:37] I want to learn what to do if possible [21:38] well, what I mean is, they are for developers themselves [21:38] see https://lists.ubuntu.com/archives/ubuntu-bugsquad/2008-May/000851.html [21:38] basically triagers should avoid them as the devs are using them to track their own progress and not report a bug persay [21:42] I would recommend installing greasemonkey (if it isn't already) and Brian's script in that email, which puts in big text at the top "This is a workflow bug" so triagers know to leave them alone [21:43] alright [21:43] thank you [21:44] Awsoonn: no problem :) does it make sense? [21:44] it took me a fair amount of reading to (I think) wrap my head around them [21:44] totaly [21:44] okay, great, thanks for helping out [21:45] if you are looking for bugs to triage, do you know about #ubuntu-bugs-announce? [21:45] it announces bugs as they come in with packages and importance and status, etc, so you can scan that for interesting bugs you think you can help with, it is a useful resource [21:46] nope, I'll keep that in mind [21:46] I have a question, would firefox maximizing so huge that the title bar goes underneath the top panel be considered a bug? [21:47] its not in fullscreen mode...but acts like it is, i have to PUT it in fullscreen, then resize it to get it back from doing this. [21:48] alan_m, I would say yes [21:48] its...quite annoying. [21:49] it does it on a regular install with no addons to firefox [21:49] It has happened to me as well, I feel your pain [21:49] i know if i remove firefox package and install it back it gives a quick fix...but..then it goes back to old habits :/ [21:53] Awsoonn, even a clean profile doing it to you? [21:54] mrooney: thanks for the linkage for that greasemonkey script [21:56] alan_m: it doesn't happen often to me [21:57] its nuts :/ [21:57] alan_m: it never happens to me but ive got plenty of extensions installed from other teams and trusty old foxclocks [21:58] yeah [22:02] Old_Soldier: no problem! [22:02] thank bdmurray really! [22:03] im pretty new to bug triage ive been more involved in the forum teams and lately ubuntu docs but bug squad and bugcontrol is definitley complimentary to my other activities :) [22:40] problems with an upgrade go to what package? [22:43] Awsoonn: sometimes "problems with upgrade" are actually questions. I always start off with making sure they dont have a transient archive server connection issue [22:43] * Old_Soldier deals with that daily on the forums [22:44] just my 2 cents :) [22:45] * alan_m takes your 2 cents and runs hehe j/k [22:45] https://bugs.launchpad.net/ubuntu/+bug/238035 [22:45] Launchpad bug 238035 in synaptic "after upgrade computer acts like a client" [Undecided,New] [22:46] * alan_m is confused by that description, heh, gonna read on [22:46] thats...weird [22:46] i'd reply and get more information. its kind of confusing and really isnt very helpful [22:47] alan_m: indeed [22:47] yeah, im doing that now Old_Soldier [22:47] lol but i guess i think too much like a forum rat [22:49] https://bugs.launchpad.net/ubuntu/+bug/238035 [22:49] Launchpad bug 238035 in synaptic "after upgrade computer acts like a client" [Undecided,New] [22:50] I cant do anything but add that comment to it....way more info needed. [23:19] hi [23:19] !hi [23:19] Hi! Welcome to #ubuntu-bugs! [23:20] hello mohbana [23:20] is there a bug file against ubuntu not adjusting the font settings? i.e., selecting no subpixel rendering has no effect [23:20] !google [23:20] google is the helpers' friend; many newer users dont have the google-fu yet; For GNU/Linux: http://google.com/linux [23:21] thats how I find out the fast way if a bug exists or no [23:21] t [23:33] could someone tell me? [23:40] Hi, I'm about to report a bug on launchpad. I can't find a bug report for the specific problem. I read it's better to submit it through apport but it's not program crash, should I use the apport-cli version to submit? [23:48] windmill: good question, I have never used apport to submit a bug by hand, I don't know if that is proper or not [23:51] windmill: If it's a GTK program you can click on "help->report a problem" [23:52] dsas, I can't dot [23:53] sorry, I was trying to say I can't do that because of the nature of the bug [23:53] it displays a dialogue that I can't close, so technically the app (nautilus) is still running