[00:03] <djsmith> I've got a patch to fix (what I consider) a bug in /etc/dhcp3/dhclient-exit-hooks.d/ntp. What's the best channel for submitting/reviewing the patch?
[00:06] <trinikrono> djsmith: i would have to guess #ubuntu-motu
[00:08] <djsmith> trinikrono: Thanks. Headed there now.
[01:03] <persia> Just a reminder, it's Patch Day. Anyone with some time to review patches and help get them in the right places is encouraged to stop by #ubuntu-reviews and help out.
[01:12] <trinikrono> hi guys,i am trying to get rid of old bugs i have one bug 359298 he said it is working so i put it as fix released, is that ok?
[01:12] <ubot4> Launchpad bug 359298 in ubuntu "compose single-quote c give ç not c acute (heat: 4)" [Undecided,Fix released] https://launchpad.net/bugs/359298
[01:14] <bbordwell> Is there someone here that knows alot about dbus?
[01:44] <svz90> Hello; I would it be possible to me to ask a question here regarding triaging?
[01:45] <bbordwell> svz90, yes this is the appropriate channel for that
[01:45] <svz90> Great. I have two bugs that are clearly duplicates of each other, but they were reported against different packages (one in xscreensave and one in gnome-screensaver)
[01:46] <svz90> I wanted to ask, should I just set one as primary, and add the other package to the first?
[01:47] <bbordwell> svz90, can you post links?
[01:47] <svz90> Certainly. Bug 1: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/555343
[01:47] <ubot4> Launchpad bug 555343 in gnome-screensaver (Ubuntu) "Screensaver obscures password box (affects: 1) (heat: 6)" [Undecided,New]
[01:47] <svz90> And the other:
[01:47] <svz90> https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/569993
[01:47] <ubot4> Launchpad bug 569993 in xscreensaver (Ubuntu) "[fglrx] GL screensaver obscures window to enter password when lock is enabled (affects: 2) (heat: 6)" [Undecided,Confirmed]
[01:49] <bbordwell> svz90, I could be wrong but I bet that gnome-screensaver calls upon xscreensaver to do its job. So the bug is realy only in xscreensaver. But I do not know the code so I am not sure
[01:49] <persia> It doesn't.
[01:50] <bbordwell> persia, thanks. So do you think they are just entirely seperate bugs or what?
[01:50] <persia> More concretely, these are valid separate bugs.
[01:51] <bbordwell> svz90, ^^
[01:51] <persia> I think so.  That said, it may be that the screensaver *contents* have the bug, rather than the screensaver programs.
[01:51] <svz90> Even if they have the exact same problem (only on the gl screensavers)?
[01:51] <persia> It would be interesting to know *which* screensavers demonstrate the issue (or if it's all of them)
[01:52] <bbordwell> svz90, sometimes the same symptom has more than one bug, sometimes the same bug has more than one symptom :)
[01:52] <persia> svz90: Well, that's the tricky bit.  It might be that the bug is in screensaver-gl ot xscreensaver-gl-extra or rss-glx
[01:53]  * bbordwell still looking for someone that knows alot about dbus
[01:53] <persia> So it's interesting to know *which* screensavers.  If the same screensaver has the same issue regardless of the screensaver display program, than the bug is probably with the screensaver, rather than with the screensaver display program, in which these may be duplicates (but are not currently against the right package)
[01:54] <svz90> persia: should I then request more information on the gnome bug - that one doesn't specify which experience the problem,
[01:55] <persia> That seems a sensible place to start, yes.
[01:55] <persia> The other good way to work the issue is to try to replicate yourself with each screensaver display program, and each screensaver, and build a list of cases where it is an issue.
[01:56] <bbordwell> I belive this bug is ready to be marked as triaged, could a member of BC please do so? https://bugs.launchpad.net/pidgin/+bug/574933
[01:56] <ubot4> Launchpad bug 574933 in pidgin (Ubuntu) (and 1 other project) "Tapping on the libnotify box several times causes a segmentation fault (affects: 2) (heat: 6)" [Undecided,Confirmed]
[01:58] <svz90> persia: alright. I'll ask for more info, and will check if the problem occurs when using xscreensaver instead of gnome-screensaver. If it appears to be a gl screensaver issue, does it get filed separately, or against xscreensaver?
[01:59] <svz90> there doesn't appear to be a separate package for xscreensaver-gl in launchpad.
[02:00] <persia> It seems to be produced by the xscreensaver source package.
[02:01] <persia> You can always check with `apt-cache show ${PACKAGE} | grep Source`.  If that returns nothing, the source is the same as the binary name.  If it returns something, then that's the source that produces that binary.
[02:02] <persia> The key is to determine if the bug is in the screensaver *data* or the screensaver *display program*, as that helps determine if it's one or two bugs.
[02:02] <persia> If it's in the *data*, you also want to check the rss-glx data to see if that also has the bug.
[02:05] <svz90> Will do. Thanks for the help persia, bbordwell
[02:05] <persia> Good luck, and thanks for helping out with triage.
[02:46] <trinikrono> hey guys i was wondering what to do with a bug like this, change to question? bug 361442
[02:46] <ubot4> Launchpad bug 361442 in ubuntu "Request for Repository Change 'korea' (affects: 1) (heat: 5)" [Undecided,New] https://launchpad.net/bugs/361442
[02:55] <persia> trinikrono: I thought there used to be a special project for that sort of thing, but I can't find a reference now.  Try asking in #ubuntu-mirrors (but be prepared for a long delay: folks there aren't so active some times of day)
[02:58] <trinikrono> well i put it out there
[02:58] <trinikrono> but i was wondering what to do with the bug report itself, if to make into a question or what
[03:00] <persia> I think it just needs to get set to a different project, or something.
[03:00] <persia> And the mirror admins then can either act on it or not.
[03:01] <persia> But we also use bugs for requests like this that require certain sorts of administrative action.
[03:04] <trinikrono> well i asked in ubuntu mirrors and subscribed to the bug
[03:04] <persia> That's abour all you can do now.  When someone (finally) gets back to you in #ubuntu-mirrors, or one of the mirror admins digs at the bug, you'll know you were successful.
[03:04] <persia> Pick another bug and let that one stew for a bit.
[03:05] <trinikrono> did you see the one i did earlier
[03:06] <trinikrono> i just wanted someone to check it for me bug 359298. i set it to fix released
[03:06] <ubot4> Launchpad bug 359298 in ubuntu "compose single-quote c give ç not c acute (heat: 4)" [Undecided,Fix released] https://launchpad.net/bugs/359298
[03:06]  * persia looks
[03:09] <persia> I'm not convinced the bug is fixed, but as the only person who ever reported it doesn't use GNOME anymore, and it works for them, the status is probably fine.
[03:12] <trinikrono> :D well that works for me
[03:13] <trinikrono> i am starting with the old bugs, then i will try the hard ones lol
[03:15] <persia> Not a bad strategy :)
[03:20] <trinikrono> bug 363474, should this be a question or a feature request?
[03:20] <ubot4> Launchpad bug 363474 in ubuntu "9.04 server install doesn't provide "static IP" or "DHCP with static IP" options" [Undecided,New] https://launchpad.net/bugs/363474
=== malev_ is now known as malev
[03:28] <persia> trinikrono: I'd call that a question, yeah.  it's easy enough to configure it either by preseeding *or* by selecting "Go Back" after doing networking, and selecting "Configure Networking" manually.
[03:30] <persia> My experience is further that if the DHCP temporary setup address passes a nameserver and default domain and the server name matches something on the nameserver, the static IP is automatically set based on the nameserver lookup.
[03:34] <trinikrono> okie well i hit the convert to question response,
[03:34] <trinikrono> and i am going to sleep. night all
[05:07] <persia> Just a reminder, it's Patch Day. Anyone with some time to review patches and help get them in the right places is encouraged to stop by #ubuntu-reviews and help out.
=== 18VAAT7XR is now known as malev
[06:06] <bbordwell> Is there anyone here that is very familiar with Dbus?
[06:07] <persia> It's usually better to just ask the question.  If someone is, they'll answer.  If nobody is, you'll get the same response as if you ask what you've asked :)
[06:08] <bbordwell> Okay, I have these two bugs that I think both come down to the same Dbus bug, but I do not know enough about it to know for sure of to file a useful report.
[06:08] <bbordwell> https://bugs.launchpad.net/ubuntu/+source/evolution-indicator/+bug/566877
[06:08] <ubot4> Launchpad bug 566877 in evolution-indicator (Ubuntu) (and 1 other project) "Disabling and Enabling "Evolution Indicator" plugin closes evolution (affects: 2) (heat: 12)" [Low,Triaged]
[06:09] <bbordwell> https://bugs.launchpad.net/ubuntu/+source/pidgin-libnotify/+bug/574933
[06:09] <ubot4> Launchpad bug 574933 in pidgin-libnotify (Ubuntu) (and 2 other projects) "Tapping on the libnotify box several times causes a segmentation fault (affects: 2) (heat: 6)" [Undecided,Confirmed]
[06:09] <bbordwell> In two separate apps that use plugins that use dbus, disabling the plugin and then enabling it crashes the program.
[06:11] <bbordwell> So if anyone can help me decide to file a dbus bug or not, and also help me make the report useful I would appreciate it.
[06:14] <bbordwell> On a seperate issue, I think this bug: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/543892 should be marked as having an importance of medium. It was marked as low by my suggestion by a member of BC but the extent of the problem was larger than I originaly thought
[06:14] <ubot4> Launchpad bug 543892 in brasero (Ubuntu Lucid) (and 2 other projects) "Brasero Fails to open using the -p argument (affects: 6) (dups: 1) (heat: 34)" [Low,Triaged]
[06:16] <ddecator> ah, brasero...
[06:16] <ddecator> so trying to burn a playlist seemingly won't work for many users?
[06:16] <persia> I think upsteam is on 543892, and it doesn't matter what we set the importance to anymore.
[06:17] <bbordwell> persia, No one upstream has looked at the bug since we nailed it down as a brasero bug and not a rhythmbox bug, about 3 weeks ago
[06:18] <persia> Ah, OK.  Moving to Medium.  Please upstream the brasero task.
[06:19] <bbordwell> persia, the linked upstream bug got reassinged to brasero, but the bug watcher seems not to have picked it up
[06:20] <bbordwell> ah i got it
[06:23] <bbordwell> ddecator, yep if you tell rhytmbox to burn a playlist it creates a brasero project, then sends 'brasero --project=<projectname>' which does absolutely nothing
[06:24] <bbordwell> I have found 3 seperate problems that this bug causes, as shown in the description
[06:24] <cshong_> Hello! I hope someone can make some changes to bug #569994 at https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/569994 . Other people reported that the bug affect gnome-settings-daemon. But, I tested on Kubuntu and confirmed that the bug affect Kubuntu also.
[06:24] <ubot4> cshong_: Bug 569994 on http://launchpad.net/bugs/569994 is private
[06:24] <ubot4> Launchpad bug 569994 in gnome-settings-daemon (Ubuntu) (and 1 other project) "eject hotkey fails to eject cd on gnome lucid (affects: 2) (heat: 14)" [Low,Triaged]
[06:27] <cshong_> The bug 569994 also affect Kubuntu, so is it really related to gnome-settings-daemon?
[06:27] <ubot4> Launchpad bug 569994 in gnome-settings-daemon (Ubuntu) (and 1 other project) "eject hotkey fails to eject cd on gnome lucid (affects: 2) (heat: 14)" [Low,Triaged] https://launchpad.net/bugs/569994
[06:29] <bbordwell> !info gnome-settings-daemon
[06:29] <ubot4> bbordwell: gnome-settings-daemon (source: gnome-settings-daemon): daemon handling the GNOME session settings. In component main, is extra. Version 2.30.0-0ubuntu6 (lucid), package size 280 kB, installed size 4088 kB
[06:35] <cshong_> The 569994 bug also affect Kubuntu.
[06:44] <persia> cshong_: I strongly suspect they are different bugs, as i don't believe that it's shared infrastructure that provides that eject.  I may be mistaken though.
[07:05] <ddecator> i'm guessing that a bug being fixed in a trunk build of software available via PPA isn't enough to mark it as fix committed?
[07:08] <persia> Not unless you're talking about the upstream task and the PPA is the PPA used by upstream for their testing :)
[07:09] <ddecator> had a feeling, haha. there is a bug in ff 3.6.x that is fixed in 3.7, upstream said not to bother reporting upstream since they won't backport it, so not sure the best way to mark the bug
[07:13] <ddecator> maybe just won't fix?
[07:23] <aburch> ddecator: Keep the report open until 3.7 is in Ubuntu, then mark as Fix Released.  Also a comment that it is fixed upstream in 3.7 would be nice.
[07:24] <ddecator> aburch: sure. i'm talking to a few others upstream to see how they want to handle it
[07:24] <ddecator> aburch: but that seems like the best option at this point
[07:24] <bbordwell> ddecator, To modify that a little, wait till 3.7 is out, then use this canned response: https://wiki.ubuntu.com/Bugs/Responses#Fixed%20in%20Development%20release%20while%20still%20existing%20in%20a%20previous%20release
[07:25] <bbordwell> as another idea
[07:25] <ddecator> bbordwell: well if 3.7 becomes the default in maverick, then that's an option
[08:23] <ddecator> hm, finally found an upstream report that fits. since it's fix released, is it even worth marking as "Also affects" or should i just point the user to the report?
[08:25] <jpds> Is it fixed in Ubuntu?
[08:26] <ddecator> jpds: it's not released in Ubuntu yet (the fix is in Firefox 3.7, and upsteam doesn't plan to backport it)
[08:26] <BUGabundo_remote> I may be sick, but I'm unbreakable. \w/
[08:26] <ddecator> hey BUGabundo_remote, hope you feel better
[08:26] <BUGabundo_remote> still no +1 :(
[08:26] <BUGabundo_remote> thanks ddecator
[08:27] <jpds> ddecator: Then I, personally, would file an Ubuntu task and link it to track it's progress in Ubuntu.
[08:27] <BUGabundo_remote> two Francesinhas and 20 min karting aint mixing :|
[08:29] <ddecator> jpds: as in add it as an "Also affects project" even though it will just say Fix Released?
[08:29] <jpds> ddecator: It's not fixed release in Ubuntu, it's confirmed.
[08:30] <ddecator> jpds: right, but the upstream report will say fix released on the report
[08:30] <jpds> Yep.
[08:30] <ddecator> alright, i'll just add it
[08:30] <jpds> [That's how I personally track fixes between projects FWIW].
[08:39] <ddecator> jpds: so when you track fixes this way, do you generally mark the ubuntu report as triaged?
[08:39] <jpds> ddecator: Yes.
[08:39] <ddecator> jpds: fair enough, thanks =)
[10:21]  * BUGabundo_remote lets try eating an apple and see if my stomach does throw it out again, like it did with last night dinner 
[10:22]  * vish tickles BUGabundo_remote 's stomach ;p
[10:23] <vish> om26er: could you try and test https://bugs.launchpad.net/bugs/35876 ?
[10:23] <ubot4> Launchpad bug 35876 in update-manager (Ubuntu) (and 4 other projects) "'Downloading package information' and 'building dependency tree' progress dialogs request focus too often (affects: 12) (dups: 9) (heat: 192)" [Low,Incomplete]
[10:23] <vish> om26er: test it with metacity [no visual effects] , this bug was actually fixed a long time ago
[10:24] <om26er> vish, ok, on it
[10:28] <om26er> vish, no does not exist with metacity
[10:28] <vish> om26er: could you comment that on the bug , I can close it
[10:30] <om26er> reproducable with compiz though.. commenting
[10:31] <vish> om26er: yeah compiz is present, thats another bug
[10:31] <vish> s/thats/there is
[10:42]  * BUGabundo_remote vomits on vish hands
[10:42] <BUGabundo_remote> oopss sorry about that
[10:42] <vish> BUGabundo_remote: ;p missed me
[11:08] <MrKanister> Hi there. Can someone please renew my Ubuntu Bug Control membership? Thanks in advance.
=== yofel_ is now known as yofel
[13:47] <eredien> Hi, I upgraded to Lucid Lynx a few days ago and am having trouble finding which package my error is in since the error comes before the boot splash screen, which was the only boot error listed in the finding package section on the wiki
[14:03] <BUGabundo_remote> eredien: maybe plymouth ?
[14:20] <hyperair> Just a reminder, it's Patch Day. Anyone with some time to review patches and help get them in the right places is encouraged to stop by #ubuntu-reviews and help out.
=== jorge_ is now known as jcastro
=== mcas is now known as marcus_irssi
[16:35] <nigelbabu> Just a reminder, it's Patch Day. Anyone with some time to review patches and help get them in the right places is encouraged to stop by  #ubuntu-reviews and help out.
[16:35] <nigelbabu> We only have about 108 bugs more to be reviewed, help us make it ZERO!
=== yofel_ is now known as yofel
=== andreas__ is now known as anoteng
[18:07] <Laibsch> I'd like to bring bug 574192 a bit forward.  I wonder if that is a bug in gnome-ppp, one of the dialing libs (if there is such a thing) or in the kernel.  I kind of thing it may be the latter.  What module would it be, then?  I guess in case it's a kernel bug, it would be good to report it upstream.
[18:07] <ubot4> Launchpad bug 574192 in gnome-ppp (Ubuntu) "Japanese E-mobile D26HW (carrier customized Huawei UMTS modem) fails to connect with gnome-ppp (regression from karmic) (affects: 1) (heat: 10)" [Undecided,New] https://launchpad.net/bugs/574192
[18:07] <Laibsch> the modem seems to be detected alright.  it doesn't seem to be able to make any kind of connection, though in lucid whereas that was possible in karmic
[18:08] <connor6892> Hi, I've just confirmed my first bug, could someone a little more experienced please check everything's okay and it's headed for the right place?
[18:43] <Damascene> hi,
[18:43] <Damascene> is this a known bug: DBus error org.gtk.Private.RemoteVolumeMonitor.Failed: An operation is already pending
[18:44] <Damascene> it happens every time I connect a flash memory or external hard disk
[18:47] <mrand> Damascene: I turned up http://ubuntuforums.org/showthread.php?t=1175638, as well as a number of launchpad tickets, when I googled that error.
[18:48] <Damascene> thanks :]
[18:48] <Damascene> that was old report
[19:11] <stefg> Hi, i have a problem/regression in lucid (x64). In araound 20% of boot attempts lucid will fail because it can't mount a lvm volume, seems to me like a timing problem. This happens during initrd, so i don't have anything in the logs or dmesg. It seems to me as a variation of https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/527666. I'd really like to file a *useful* bug report, but...
[19:11] <stefg> ...since there's nothing in the logs I'm looking for advice how to track the problem further down.
[19:11] <ubot4> Launchpad bug 527666 in mountall (Ubuntu Lucid) (and 1 other project) "mountall blocks on timeout waiting for a partition, rather than supplying prompt and picking it up later (affects: 34) (dups: 2)" [High,Fix released]
[19:12] <stefg> How do i do debugging during execution of the initrd filesystem ?
[19:28] <bdmurray> can anybody recreate bug 274179?  I'm not having any luck
[19:28] <ubot4> Launchpad bug 274179 in system-config-printer (Ubuntu) "Review Firewall message when trying to set up network printer (affects: 3) (dups: 2) (heat: 34)" [Low,New] https://launchpad.net/bugs/274179
=== radoe_ is now known as radoe
[21:18] <StevePearson> Hi, I am using lucid and am strugling to work out how to report a bug I have discovered... Any advice would be welcomed!
[21:20] <StevePearson> Anyone?
[21:21] <Aquina> Aehm... what kinda bug?
[21:22] <StevePearson> It's the volume control. When you use dual x screens, and mute. The icon is only updated on one screen and not both
[21:22] <StevePearson> nothing major
[21:22] <Aquina> I don't know whether this is actually a bug.
[21:23] <StevePearson> oh, ok
[21:23] <StevePearson> you mean maybe by design?
[21:23] <Aquina> maybe but I'm one of the Xubuntu girls. Better you ask someone else in here. :-)
[21:24] <Aquina> I'm just hanging around here to get the latest news.
[21:24] <StevePearson> Ok, I'll ask again later. Many Thanks anyway!
[21:24] <maco> itd be a bug
[21:25] <maco> the icon should update regardless of whether its the one that was used to do the volume change
[21:25] <maco> StevePearson: ^
[21:25] <StevePearson> Ok, I followed the wiki instructions on posting a bug, but was stumped. Do you know what I need to do to post it? I want to contribute if I can
[21:28] <StevePearson> ??
[21:31] <astraljava> StevePearson: It would help to know what you did, and where you left off.
[21:33] <StevePearson> It's very simple to reproduce. I am using 10.04 (64bit), two Nvidia cards with the Binary driver (Sorry!). I can either mute by clicking the sound icon and selting mute, or by pressing the mute key on my keyboard.
[21:34] <StevePearson> Both methods produce the same result.
[21:34] <astraljava> StevePearson: I mean filing the bug. What did you try, and what left you stumped?
[21:34] <StevePearson> The icon only relects the mute action on the x screen I did it on
[21:34] <StevePearson> OOPS
[21:34] <StevePearson> doh
[21:35] <StevePearson> I logged into launchpad, selected 'Report a bug'
[21:35] <StevePearson> This took me back to the wiki page
=== BUGabundo is now known as BUGabundo_Chuck
[21:36] <StevePearson> which suggests I report it via launchpad
[21:36] <StevePearson> I am in a loop
[21:36] <StevePearson> https://help.ubuntu.com/community/ReportingBugs
[21:36] <mrand> StevePearson: it is suggesting that you use "ubuntu-bug <package-name>"
[21:37] <mrand> Someone else will have to suggest the package name though...  or maybe an internet search on launchpad OR ubuntu volume control would turn it up.
[21:38] <StevePearson> Yes, I read this. But I couldn't determine the package name
[21:38] <StevePearson> ok
[21:38] <StevePearson> Thats helpful!
[21:38] <StevePearson> Many Thanks
[21:40] <StevePearson> Thanks, I found it. Very simple... Right click on the sound Icon > About > Url to Launchpad page for that package!
[21:41] <StevePearson> Now I feel a bit daft!
[21:56] <mrand> StevePearson: no worries.  Thanks for helping!
[22:21] <trinikrono> hey all :D
=== BUGabundo_Chuck is now known as BUGabundo_House
=== BUGabundo_House is now known as BUGabundo_DrHous
=== BUGabundo_DrHous is now known as BUGabundoDrHouse
=== BUGabundoDrHouse is now known as BUGabundo_HIMYM
[23:11] <nigelbabu> Just a reminder, it's Patch Day. Anyone with some time to review patches and help get them in the right places is encouraged to stop by   #ubuntu-reviews and help out.
[23:12] <nigelbabu> We're down to around 91 bugs from 185 bugs that we started with!
[23:16] <Aquina> When ISO testing is over for me I'll start triaging. Patch stuff is still a way to go for me...
[23:25] <nigelbabu> Its not *that* hard, similar to triage most of the time
=== BUGabundo_HIMYM is now known as BUGabundo_NCISLA
[23:27] <Aquina> I will get involved in this wuite soon. :-)
[23:29] <Aquina> Does patching require you to actually bugfix or *simply* apply patches make diffs and thelike? I studied CS but I'm not the best coder in the world... :]
[23:32] <nigelbabu> most its testing patches that others have written