[00:39] <Yasumoto> hey guys, I know the hug day pages stick to a pretty solid format, but do you think adding a link to https://wiki.ubuntu.com/Bugs/FindRightPackage would be helpful?
[00:42] <bdmurray> Yasumoto: yes, that would make a ton of sense ;)
[00:44] <emet> is there any specific process for joining the ubuntu bug team?
[00:45] <Yasumoto> bdmurray: cool
[00:45] <bdmurray> Yasumoto: Do you mind doing it?
[00:45] <emet> I applied but I am curious if I have to do anything else
[00:45] <bdmurray> emet: this team? https://wiki.ubuntu.com/UbuntuBugControl/
[00:46] <emet> there we go
[00:47] <Yasumoto> bdmurray: nope, adding it now
[00:47] <Yasumoto> I'm going to make it a section, just so it stands out
[00:48] <bdmurray> Sounds great
[00:48] <Yasumoto> I'm hoping to hold a mini bug jam at my school on Thursday, so it'll come in handy
[00:48] <bdmurray> Cool!  If you have any questions feel free to ask.
[00:50] <Yasumoto> will do, thanks bdmurray
[00:53] <emet> bdmurray, so bug control is like a more selective bugsquad?
[00:53] <bdmurray> emet: It is for more experienced members of bug squad yes
[02:31] <kgoetz> hm. i must have /parted. anyhow. wondering if its posable to email the -bugs list without subscribing - i tried a few nights ago, and it seems i got rejcted.
[03:16] <hggdh> kgoetz, which -bugs list?
[03:20] <kgoetz> hggdh: i can check exactly, iirc<EMAIL_ADDRESS>[03:20] <kgoetz><EMAIL_ADDRESS>[03:24] <hggdh> kgoetz, hold on. Let me check if it is moderated
[03:27] <kgoetz> thanks
[03:28] <hggdh> kgoetz, perhaps you wanted ubuntu-bugsquad instead? ubuntu-bugs is pretty much an output-from-launchpad mailing list
[03:29] <hggdh> or mail-in to a bug
[03:30] <hggdh> no, really, only output from LP... this is not a list to send to, at all
[03:32] <kgoetz> hggdh: hm. perhaps i autocompleted the wrong thing. i'll try -bugsquad instead thanks :)
[03:36] <hggdh> kgoetz, welcome
[03:44] <mrooney> is there a channel for the ubuntu.com website?
[03:45] <mrooney> I am wondering if http://www.ubuntu.com/products/whatisubuntu/804features/ intentionally doesn't reflect 8.04.1 changes (such as Firefox), or if it is a mistake
[03:46] <mrooney> sorry for off topic :]
[03:48] <greg-g> mrooney: there is the "ubuntu-website" project in LP where you can file bugs
[03:48] <greg-g> not sure about a website specific channel though
[03:49] <mrooney> greg-g: okay, thanks :)
[03:51] <mrooney> ahh, bug 262729
[06:58] <dholbach> good morning
[08:21] <Yasumoto> hey dholbach, I know you're super busy, but if you have some time, if you could check out https://code.edge.launchpad.net/~yasumoto7/five-a-day/icon_countdown (and maybe give some pointers :) that'd be a huge help
[08:26] <dholbach> Yasumoto: I'd suggest you talk to thekorn about it - he's the mastermind behind the applet
[08:27] <Yasumoto> dholbach: ah, good idea, thanks
[08:29] <Yasumoto> thekorn: ping :)
[08:30] <thekorn> hi dholbach and Yasumoto
[08:30] <thekorn> let me get this branch
[08:30] <Yasumoto> sweet
[08:31] <Yasumoto> thekorn: the icon changes fine when I call the update_icon() method with the About window
[08:31] <Yasumoto> but when it runs after a commit, it hangs and freezes
[08:32] <Yasumoto> I'm sure there's a way to debug it and figure out exactly what the issue is, but so far I haven't been able to gather any info
[08:32] <thekorn> righ, that's what I just found out ;)
[08:36] <thekorn> Yasumoto, I got an good idea on how you implemented it,
[08:36] <thekorn> I'm running iout of time right now,
[08:37] <Yasumoto> thekorn: cool, no worries
[08:37] <thekorn> but I will comment on the bugreport later today
[08:37] <Yasumoto> sweet, thanks
[08:37] <thekorn> but in general I think this is a good idea,
[08:37] <thekorn> thanks for your work so far,
[08:38] <Yasumoto> of course. the implementation may be a bit hokey, but it's a start
[09:05] <james_w> is there a project for Ubuntu documentation? bug 268435
[09:07] <dholbach> james_w:  https://bugs.launchpad.net/ubuntu-doc ?
[09:08] <james_w> dholbach: should have known, thanks :-)
[10:10] <james_w> my VMs are not available at the moment
[10:11] <james_w> does anyone have a test system that they could try something that may kill X and possibly prevent the user from logging in on?
[10:11] <james_w> bug 240231
[10:12] <james_w> well, they claim it hangs X, I'm just being paranoid about the other part
[10:22] <Ampelbein> james_w: if a virtual machine is sufficient i can test
[10:22] <james_w> Ampelbein: yeah, that's sufficient
[10:22] <james_w> Ampelbein: is the bug clear about what you have to do?
[10:22] <Ampelbein> looking
[10:23] <james_w> I just want it confirmed so I can forward it
[10:24] <Ampelbein> i'm not sure what "application with an unlock button" means. screensaver?
[10:26] <Hobbsee> usually
[10:26] <Ampelbein> ok, firing up a intrepid-vm
[10:27] <james_w> Ampelbein: no, something that uses policykit
[10:27] <james_w> Ampelbein: e.g. "time-admin"
[10:27] <Ampelbein> ok
[10:28] <Hobbsee> oh, that unlock
[10:32] <Ampelbein> ok, i did sudo passwd <user> -e and started time-admin. pressing unlock brings up the "authenticate"-window, i am able to enter the (current, but expired) password. ~20 sec later a window comes "Could not autenticate - An unexpected error has occured". Closing this results in time-admin hanging. But X continues to run and when using xkill on the non-responsive time-admin window, I can continue working as normal.
[10:34] <Ampelbein> oh, actually it's not time-admin hanging, but the "authenticate"-window (i assume thats policykit). Clicking close in time-admin closes time-admin.
[10:34] <Ampelbein> but the authenticate window has to be killed by xkill
[10:34] <Ampelbein> should i provide some screenshots?
[10:34] <james_w> interesting
[10:35] <james_w> so it's not as bad as the user says, but the policykit window still shouldn't hang
[10:35] <james_w> is this Intrepid?
[10:35] <Ampelbein> yes, intrepid.
[10:35] <Ampelbein> with yesterdays updates.
[10:35] <james_w> cool, thanks
[10:36] <Ampelbein> i'll look for version
[10:36] <james_w> could you update the bug with your findings?
[10:36] <Ampelbein> policykit:
[10:36] <Ampelbein>   Installed: 0.9-1ubuntu1
[10:36] <Ampelbein> ssure
[10:41] <Ampelbein> james_w: added comment, updated title and description
[10:41] <james_w> Ampelbein: great, thanks
[10:41] <james_w> I'll forward it shortly
[10:45] <Ampelbein> james_w: np. i'm adding some screenshots.
[12:26] <james_w> anyone on Intrepid running compiz?
[12:38] <Ampelbein> james_w: i can.
[12:38] <james_w> Ampelbein: great :-)
[12:38] <Ampelbein> how do you want me to mangle my system? ;-)
[12:39] <james_w> Ampelbein: can you open "users-admin" click "Unlock" and try moving the "Authorization" window, and the "users-admin" window?
[12:39] <Ampelbein> sec
[12:39] <james_w> I want to know if a bug has been fixed in Intrepid, or is just a difference in window managers
[12:39] <james_w> shouldn't break your system this time
[12:40] <Ampelbein> can move both
[12:41] <Ampelbein> but after some time (~30 sec) an error pops up, "Could not authenticate"
[12:42] <Ampelbein> (i did not enter my password in authenticate window, just moved both)
[12:43] <Ampelbein> weird. i have to restart users-admin to bring up unlock again.
[12:43] <Ampelbein> there seems to be a timeout
[12:44] <james_w> yeah
[12:44] <james_w> bug 201184
[12:44] <Ampelbein> so, when i press unlock for first time and wait for the error to appear (Could not authenticate, an unexpected error occured) i cannot use users-admin until i restart it
[12:44] <Ampelbein> even if i enter my password in authentication window.
[12:44] <james_w> you just confirmed bug 202269 is fixed though, thanks
[12:46] <Ampelbein> yeah.
[12:48] <Ampelbein> strange. now my openvpn session to my employer faded after this timeout and i'm unable to get it back working. hmpf. should be just a coincidence, right? because i see no reason why openvpn is connected to policykit.
[12:51] <Ampelbein> ok, works again. server has been restarted... weird coincidence.
[13:03] <tech2000> Hi anyone here running Intrepid Ibex in any other language than English? that can check this bug I just filed to gnome...
[13:03] <tech2000> http://bugzilla.gnome.org/show_bug.cgi?id=551640
[13:03] <seb128> tech2000: the bug described on launchpad and GNOME are not the same
[13:04] <seb128> tech2000: it's normal that it doesn't use the user directory because the admin tools are ran by the admin user
[13:04] <seb128> tech2000: the labels should be coherent though
[13:04] <tech2000> yes, they are..   just wanted to see so it's not just my system here..  :(
[13:04] <seb128> I don't get the issue on my system
[13:04] <james_w> bug 148534 isn't a polkit-gnome bug, I may have seen this reported elsewhere, has anyone else seen it?
[13:05] <seb128> in fact it does the same when using sudo right
[13:05] <tech2000> seb128: ok..
[13:15] <Ampelbein> james_w: bug 153706 ?
[13:16] <james_w> yeah, similar
[13:16] <james_w> have you ever seen a warning when shutting down by any method?
[13:17] <james_w> I wonder how low down this needs to/can be fixed
[13:17] <Ampelbein> since i'm the only user on my machine i don't have that problem.
[13:19] <james_w> me too
[14:55] <bddebian> Boo
[15:14] <atrus> i filed https://bugs.launchpad.net/bugs/259786 a while ago, but it was marked as 'invalid' before I could get the requested information. it's in there now, is there anything that needs to be done to get the status updated (since i can't apparently change it myself)
[15:29] <greg-g> atrus: if you are logged in you can change the status to New
[15:30] <atrus> oh, indeed i can. i think my problem was that i tried to change the status and add descriptive text simulatenously... didn't seem to work before anyways.
[15:32] <greg-g> ah, gotcha
[15:32] <greg-g> thanks for reporting the bug and providing the extra info
[15:33] <greg-g> just fyi: your bug was closed a bit prematurely, we usually wait 90 days after a request for information
[15:40] <atrus> thanks
[15:53] <mrooney> oh no, a five-a-day exception!
[16:17] <mrooney> dholbach: ping?
[16:17] <dholbach> mrooney: pong, but in a call right now - just ask and I or somebody else will answer in a bit
[16:21] <mrooney> dholbach: okay, I got the impression you had something to do with five-a-day, any ideas what http://dpaste.com/77212/ means? I am just doing something stupid?
[16:24] <dholbach> mrooney: argh, that's a definite bug
[16:24] <dholbach> mrooney: I'll take a look at it in an hour - should be easy to fix
[16:24] <dholbach> we have another fix pending
[16:24] <dholbach> one day I'll use unit tests...........
[16:25] <mrooney> dholbach: :)
[16:25] <dholbach> thanks mrooney
[16:25] <norsetto> dholbach: will fixing 5-a-day counts towards the 5-a-day :-) ?
[16:25] <dholbach> sure :-)
[16:25] <dholbach> bbl
[16:46] <dholbach> mrooney: uploaded, should be in PPA in a bit
[17:45] <Syntux> Would you guys consider bug # 229641 a bug or should we convert it to a question ?
[17:46] <bdmurray> bug 229641
[17:55] <bdmurray> Syntux: probably a bug and should be about cupsys
[17:56] <Syntux> bdmurray, but why not a question? I mean cupsys isn't responsible for getting all printers to work but getting them working if we have a driver
[17:58] <Syntux> and bug 251219 should be a wishlist?
[18:00] <bdmurray> Syntux: I see your point but don't think there is a practical benefit from converting it to a question since someone has responded in the bug report.
[18:01] <Syntux> ok
[18:03] <Konstigt> did I do it right when I closed bug  260174 with fix released?
[18:08] <bdmurray> Konstigt: yes, that looks good - thanks!
[20:29] <bdmurray> pedro_: I've been looking at some apport-crashes w/o a package and alot of them are gvfs crashes.  Do you know if this is working right?
[20:30] <bdmurray> The apport bit, not gvfs. ;)
[20:31] <Tindor> hi, does anyone know whether the bug that the new adept can't select many packages at once has been reported
[20:32] <sbeattie> bdmurray: hrm, I had a gvfs crash in the alpha 5 iso testing, but apport wouldn't submit it because there were newer packages available in the archive.
[20:34] <asomething> Tindor: not sure, you could take a look here: https://bugs.edge.launchpad.net/ubuntu/+source/adept
[20:35] <Tindor> asomething, thanks. I'm quite new to ubuntu and lauchpad and find it quite hard to navigate there
[20:51] <jdstrand> does python-launchpad-bugs have code in place to set Bug.authentication? (eg via ~/.p-l-b-rc or something)
[20:52] <bdmurray> jdstrand: ~/.python-launchpad-bugs.conf it looks like there is a cookies section
[20:56] <jdstrand> bdmurray: is that documented somewhere? more importantly (for me), can you paste the contents of yours somewhere?
[22:19] <mrooney> can someone confirm or deny that a version "0.11.6svn20080909-0ubuntu1" means it was pulled from SVN yesterday?
[22:20] <james_w> mrooney: that is correct I think
[22:20] <seb128> mrooney: the uploads history is easy to find on launchpad
[22:22] <seb128> mrooney: what is your issue exactly?
[22:23] <mrooney> seb128: well, you can probably tell me specifically since I was asking about rhythmbox (http://packages.ubuntu.com/intrepid/rhythmbox)
[22:24] <seb128> mrooney: ah your question was about the versionning and not about the version available
[22:24] <mrooney> seb128: http://bugzilla.gnome.org/show_bug.cgi?id=374078 apparently was fixed in r5751 of rhythmbox svn
[22:25] <mrooney> so I was trying to figure out how to tell if Intrepid has that patch
[22:25] <seb128> mrooney: right, that was fixed today, I'll do a new snapshot soon
[22:25] <seb128> mrooney: apt-get source rhythmbox; edit rhytmbox-*/ChangeLog
[22:25] <mrooney> seb128: today? 5751 is a long time ago, I think
[22:25] <Konstigt> how is it possible that bug 241139 is set to importance low? shouldn't it be critical?
[22:26] <seb128> mrooney: ah, they fixed a bug similar today, feel free to close this one then
[22:27] <mrooney> Konstigt: well it depends on how many people in impacts, among other things: https://wiki.ubuntu.com/Bugs/Importance
[22:27] <seb128> Konstigt: not everybody gets it, it's only samba, and changing to critical will not change the fact that the bug is an upstream one and the ubuntu team doesn't have anybody knowing gvfs good enough to work on that
[22:28] <mrooney> seb128: okay so, in general, svnXXXXXXX means it was synced from svn on that date though, right? so one can expect all fixes committed to svn before that?
[22:28] <danbhfive> Konstigt: I agree with seb128.  Its listed as an upstream bug
[22:30] <Konstigt> i would say a quite big percent of the ubuntu users use samba daily. maybe changing to critical doesn't help very much since it's an upstream bug but I think it would be more correct to have it as a critical. this is in my opinion an absolute blocker for intrepid.
[22:31] <seb128> mrooney: right
[22:32] <seb128> Konstigt: we might have intrepid next year then
[22:32] <seb128> Konstigt: trying to create a lock situation? ;-)
[22:32] <danbhfive> Konstigt: well, you should sell your case to the gnome devs, and get them to list it as critical.  I wouldn't worry.  I bet they'll fix it
[22:34] <danbhfive> Konstigt: actually, I looked again.  That bug does block intrepid
[22:34] <danbhfive> for gvfs, its listed as 8.10 milestone
[22:36] <eu_mesmo> hello
[22:37] <eu_mesmo> Is there a way to know whether it's being working on a bug?
[22:37] <eu_mesmo> I posted a bug some time ago and have no answers in the thread
[22:38] <danbhfive> eu_mesmo: I think its tough to get an answer unless someone confirms your bug
[22:38] <eu_mesmo> seems it has been accepted for the next ubuntu version, but not for the 8.04..
[22:38] <Ampelbein> eu_mesmo: due to the high amount of bugs filed this unfortunately happens
[22:38] <Ampelbein> eu_mesmo: can you give a bug number?
[22:38] <eu_mesmo> it has been confiremed for the next version..
[22:39] <eu_mesmo> yep: 251781
[22:39] <Ampelbein> bug #251781
[22:39] <eu_mesmo> yes, I started the bug, then Matthew confirmed for intrepid
[22:40] <eu_mesmo> but I have the bug in 8.04...
[22:40] <eu_mesmo> and know at least of one person that is having the same issue...
[22:44] <Ampelbein> eu_mesmo: since the problem is kernel-related one solution would be to upgrade your hardy to the latest intrepid-kernel, using the intrepid-repos just for that issue.
[22:45] <eu_mesmo> mmm, but is there a way to upgrade just the kernel and not the whole distro using the repos?
[22:46] <eu_mesmo> (in gentoo you can do that, thought that wasn't possible in debian distros...)
[22:46] <Ampelbein> eu_mesmo: sure, just install the kernel-image and remove the intrepid repos.
[22:46] <eu_mesmo> oh, interesting
[22:46] <eu_mesmo> and after doing so, won't it ask in any upgrade to downgrade the kernel?
[22:47] <danbhfive> eu_mesmo: heh, no
[22:47] <eu_mesmo> oh, ok
[22:47] <danbhfive> you have to do something called pinning if you want a downgrade to happen
[22:48] <danbhfive> regardless, the default is to never downgrade
[22:48] <eu_mesmo> ok, that's a good fix. I'll try that. Thank you very much for your help
[22:52] <eu_mesmo> goodbye and thanks again
[22:59] <dupondje> libgnomekbd-common got upgraded, and needs a newer version of libgnomekbd2
[22:59] <dupondje> but there isn't a new version of libgnomekbd2 yet ?
[23:00] <seb128> dupondje: no, the soname changed and the library is named libgnomekbd3 now
[23:01] <dupondje> gnome-applets etc needs libgnomekbd2 ...
[23:02] <seb128> dupondje: that's called a transition, wait for those to have build, libgnomekbd needed to build first, then the new library needed to be published then other applications can be rebuilt using the new library
[23:02] <dupondje> oh ok :)
[23:02] <seb128> dupondje: rebuild updates have been uploaded, try again after the next update in one hour
[23:03] <dupondje> i'll do :) thx
[23:04] <dupondje> https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/266956
[23:04] <dupondje> should be fixxed asap imo :x
[23:05] <james_w> seb128: is "Adjust date and time" from the context menu of the clock applet screwed for you as it is for me?
[23:05] <james_w> I can't set a time higher than "11:29:29"
[23:06] <dupondje> you can only ajust time in the morning ;)
[23:06] <seb128> james_w: yes
[23:06] <james_w> hmm, time-admin doesn't do much better it seems
[23:06] <james_w> is there a bug open?
[23:07] <jibel> james_w: yes there is one.
[23:07] <james_w> thanks
[23:07] <seb128> james_w: it has the same bug?
[23:08] <jibel> bug 267892
[23:08] <james_w> that's the badger
[23:08] <seb128> weird bug
[23:13] <dupondje> isn't 13:49:49 some int/long limit ?
[23:16] <dupondje> I can't even change anything in the time settings ... :p
[23:16] <dupondje> all gray'ed out
[23:25] <jibel> james_w: I've submitted a report upstream.
[23:25] <james_w> jibel: for which?
[23:26] <james_w> time-admin?
[23:26] <jibel> yes time-admin
[23:26] <james_w> thanks
[23:26] <james_w> I'm looking in to it
[23:26] <james_w> it may be an oobs issue
[23:30] <james_w> no the panel doesn't use oobs
[23:30] <james_w> it's either gtk, or a mistake with either the wrapping or the width I think
[23:40] <mrooney> hm, what might I do with bug 268752?
[23:44] <james_w> reassign it to the wallpapers package to start I would say
[23:44] <james_w> tell them it's being worked on and should be changed before release
[23:44] <bdmurray> james_w: probably ubuntu-artwork rather
[23:44] <james_w> ah, ok
[23:45] <bdmurray> or maybe not
[23:45] <bdmurray> ubuntu-wallpapers looks right