[00:00] <micahg> Mathuin: anyone can contribute a patch to fix bugs in Ubuntu
[00:01] <Mathuin> Well, sure, anyone could contribute a patch to FreeBSD.  The fact that it took eighteen months for my two-line patch to be committed is one of the primary reasons I switched to Ubuntu.
[00:01] <Mathuin> I got tired of having to patch my kernel every time I ran "cd /usr/src && sudo make update".
[00:05] <Mathuin> https://code.launchpad.net/~doctormo/screenlets/options-rework/+merge/3935 -- oh dear.
[00:15] <greg-g> Mathuin: that seems like that ended well, no? (well, a year ago)
[00:16] <Mathuin> greg-g: crash and burn, with a bit of dead-cat bounce as the "new project" is pretty much dead as well.
[00:16] <Mathuin> To the point where I became the #2 recent contributor when I submitted a bug report asking if the project was alive. :-)
[00:20] <greg-g> well, yeah, I mean, it may be dead, but at least it didn't turn into a huge flame war
[00:20] <Mathuin> greg-g:  I learned from another bug in the UA database that the owner's looking to give it up.  I just sent in an offer to take it over.
[02:29] <bcurtiswx> Mathuin: join #empathy on irc.gimp.net or #telepathy here on freenode
[08:10] <hsm> If I see a bug in Ubuntu, what's the best channel to record it?
[08:14] <lifeless> $ ubuntu-bug packagename
[08:16] <hsm> lifeless: allright, can you help me with this? I see a wrongly displayed taskbar in ubuntu 10.04. What should I do to report this?
[08:22] <hsm> lifeless: ?
[08:35] <sense> hsm: Have you searched at Launchpad for the problem, to see if it isn't already reported?
[08:35] <kermiac> hsm: when you say "taskbar", are you referring to the top gnome panel? This is just a guess, but it might be bug 439448
[08:35] <ubot2> Launchpad bug 439448 in gnome-panel (Ubuntu Maverick) (and 5 other projects) "visual corruption affecting several panel applets (affects: 316) (dups: 80) (heat: 1751)" [Medium,Triaged] https://launchpad.net/bugs/439448
[08:36] <hsm> sense: yeah.. well i searched on taskbar and background
[08:36] <sense> hsm: kermiac's bug might be yours
[08:38] <hsm> kermiac: sorry, is missed your remark, i'm referring to the bottom bar (containing activie applications), but as I just found out it is for both bars..
[08:38] <hsm> kermiac: I will have a look into the bug you mentioned
[08:39] <hsm> kermiac: & sense: it's not the bug I mean.. What I am experiencing is that the background gradient of the taskbars keeps repeating itself when I scale the height of the bars.
[08:40] <sense> hsm: That is a theme-related issue, I suppose.
[08:40] <sense> hsm: It is how panel-backgrounds work.
[08:41] <sense> hsm: Although you could consider reporting a bug because different behaviour may be desired.
[08:41] <sense> Maybe there is already one.
[08:41] <kermiac> hsm: it might be easier if you could upload a screenshot of the issue, as sense said - it may be related to your theme. Does it happen when using the default theme?
[08:42] <hsm> sense: okay.. maybe these can be improved by scaling the background..
[08:42] <hsm> kermiac: where shall I upload this? In the bugreport?
[08:43] <kermiac> hsm | !screenshots
[08:43] <kermiac> !screenshots
[08:43] <ubot2> Screenshots can be made with the [PrtScr] button. Want to show us a screenshot of your problem? Upload an image to http://tinyurl.com/imagebin and post a link to it.
[08:44] <sense> hsm: But if you're trying to add screenshots to a bug report, please attach them there indeed. The pastebin is useful if you want to ask something here.
[08:49] <hsm> kermiac: http://imagebin.org/108056
[08:50] <hsm> sense: & kermiac: where shall I report this bug? launchpad bugs redirects me to another page..
[08:51] <sense> hsm: Have you read that page?
[08:51] <sense> hsm: I think that this bug has been reported before.
[08:53] <hsm> sense: I guess ..
[08:54] <sense> Let me search for it.
[08:56] <kermiac> sense: it *might* be bug 532309  see the screenshot in comment #34
[08:56] <ubot2> Launchpad bug 532309 in light-themes (Ubuntu) "Light-themes: panel-background isn't scaling (affects: 45) (dups: 8) (heat: 282)" [Low,Confirmed] https://launchpad.net/bugs/532309
[08:56] <sense> ah, there it is
[08:57] <sense> hsm: Your bug is probably bug #532309.
[09:00] <hsm> thanks sense! thats it! Will read it.. thanks so much
[09:01] <sense> hsm: You're welcome, and thank kermiac, because he did most of the work! :)
[09:06] <hsm> kermiac: THANKS kermiac! My problem is solved!
[09:06] <kermiac> hsm: no probs mate
[09:34] <sense> new tag: 'nautilus-desktop-icons'
[09:34] <vish> sense: :s
[09:34] <sense> For everything related to the icons that Nautilus puts on your desktop.
[09:35] <sense> vish: Why the :S?
[09:35] <vish> sense: how many bugs are there related to those icons?
[09:35] <vish> latest fad seems to be adding more tags :D
[09:35] <sense> It is really helpful to keep track of the different issues related to the desktop!
[09:36] <sense> Sebastien is seeing quite some of them, at least, and I've seen a few as well.
[09:37] <sense> The desktop probably needs a usability overhaul, but meanwhile we can categorise bugs to make it easier for the interested folks to find the issues.
[09:37] <vish> there are ~10 bugs , iirc
[09:37] <JoshuaL> People using icons on their desktop is a bug ;-)
[09:38] <vish> sense: well , if you are tagging them for personal interest seems good , but dont see the point in making it official
[09:44] <vish> sense: mainly more because , there have been already tagged upstream and aday is looking into them , and we aernt going to be doing much usability work separate from upstream :)
[09:44] <sense> ok
[09:44] <sense> Didn't know about that
[09:44] <sense> .
[12:12] <BrunoAlves> Hey! I couldn't find any mention on bugtracker.... but it's about plymouth... plymouth uses a file called boot-duration in /var/lib/plymouth to determine the duration of boot, and to properly draw the progress bar... but here this file is always an empty file... can anyone confirm this?
[12:17] <BrunoAlves> anyone?
[12:26] <BrunoAlves> I'm not seeing any messages... am I transmitting messages here?
[12:27] <devildante> We are here, just that we are all busy :(
[12:28] <BrunoAlves> thanks... and sorry
[12:29] <BrunoAlves> well... if anyone could please confirm if theirs /var/lib/plymouth/boot-duration is an empty file.....
[12:36] <mythos> BrunoAlves, -rw-r--r-- 1 root root 0 2010-07-27 20:37 /var/lib/plymouth/boot-duration
[12:38] <vish> bcurtiswx: :D
[12:39] <vish> bcurtiswx: we were on the same bug ;)
[12:39] <BrunoAlves> thanks!
[12:39] <bcurtiswx> vish: ah ha, and i'm talking to you in -desktop
[12:45] <gnomefreak> BrunoAlves: i dont have that file at all
[12:46] <gnomefreak> gnomefreak@Development:/var/lib/plymouth$ ls
[12:46] <gnomefreak> gnomefreak@Development:/var/lib/plymouth
[12:47] <yofel_> 2621812 0 -rw-r--r-- 1 root root 0 2010-07-17 21:30 /var/lib/plymouth/boot-duration
[12:47] <devildante> gnomefreak: weird, I have this (empty) file too
[12:47] <yofel> 0 byte file
[12:47] <devildante> -rw-r--r-- 1 root root 0 2010-08-04 10:44 /var/lib/plymouth/boot-duration
[12:47] <gnomefreak> are you 2 on maverick or lucid?
[12:47] <devildante> maverick
[12:47] <yofel> gnomefreak: maverick upgraded from lucid
[12:48] <devildante> me too upgraded from lucid :)
[12:48] <gnomefreak> maybe its because i cant get plymouth to show up at all
[12:48] <yofel> well, the file isn't part of any package, so it was created by plymouth at some point
[13:12] <stanley_robertso> hi vish
[13:18] <vish> stanley_robertso: hey
[13:19] <gnomefreak> i have to reboot but can someone try to confirm bug 598514 while im gone?
[13:19] <ubot2> Launchpad bug 598514 in gnome-screensaver (Ubuntu) (and 1 other project) "F-spot no longer works (affects: 1) (heat: 6)" [Undecided,Fix released] https://launchpad.net/bugs/598514
[13:20] <gnomefreak> ok be back in a few
[13:21] <devildante> @everyone: shouldn't this be "Invalid" for gnome-screensaver?
[13:22] <yofel> bdmurray: filed the merge request https://code.edge.launchpad.net/~yofel/canonical-qa-tracking/gm-response-pa/+merge/31694
[13:25] <stanley_robertso> vish,   wassup.. how is it going ?
[13:26] <yofel> devildante: probably, but I wouldn't change it as closed is closed
[13:26] <devildante> yofel: okay, thx
[13:36] <gnomefreak> vish: was it you that gets/got the passprase dialog when using auto login?
[13:37] <vish> gnomefreak: yup
[13:37] <gnomefreak> s/passprase/passphase
[13:37] <gnomefreak> vish: can you please confirm bug 611001
[13:37] <ubot2> Launchpad bug 611001 in gdm (Ubuntu) "Password prompt shows when automatically login (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/611001
[13:37]  * gnomefreak going through my bugs
[13:38] <seb128> gnomefreak, it's not a bug
[13:39] <vish> seb128: this is even when not using any stored password.
[13:39] <gnomefreak> seb128: ? its a feature?
[13:39] <vish> seb128: it just asks for keyring unlock always
[13:39] <seb128> something might be using a password
[13:39] <seb128> calendar, wireless
[13:39] <seb128> im
[13:40] <devildante> there is some discussion on ayatana mailing list about this
[13:40] <vish> seb128: for me its on a VM , not using anything in it  , its just for testing i have that there
[13:40] <vish> no im/wireless
[13:41] <seb128> vish, I will have to test an a3 install
[13:41] <seb128> but g-k didn't change since lucid
[13:41] <seb128> so I doubt it
[13:41] <gnomefreak> me neither. nothing should need to use that AFAIK
[13:41] <seb128> could be ubuntuone or something trying to use a password
[13:41] <seb128> gnomefreak, "that" being the keyring?
[13:41] <vish> yeah , U1 might be that!
[13:41] <seb128> we have tons of softwares using the keyring
[13:42] <seb128> it's really not a gdm bug in any case
[13:43] <gnomefreak> i disabled ubuntu1 from loading, but i still have ssh keyring loading at startup
[13:43] <gnomefreak> maybe that is why? seb128 yes that == keyring
[13:44] <seb128> dunno
[13:44] <seb128> in any case it's not a gdm bug
[13:44] <seb128> gdm has nothing to do with password after login
[13:44] <seb128> you probably just have a software running trying to use the keyring
[13:45] <gnomefreak> well ill disable ssh keyring on load and when i reboot i will find out
[13:47] <gnomefreak> seb128: can you please update the bug
[13:49] <gnomefreak> i guess it could be the gsettings data conversion
[13:49] <seb128> gnomefreak, I doubt it
[13:50] <seb128> why would that need a password?
[13:50] <gnomefreak> ok hmm
[13:50] <gnomefreak> seb128: not sure
[13:51] <gnomefreak> than the only other thing that is in startup menu is ssh . PA wouldnt need it and Nm gnome sound
[13:53] <gnomefreak> well i will reboot and see what happens with ssh disabled
[14:05] <gnomefreak> chrisccoulson: and seb128  thanks for updating bug. it seems it is ssh that caused it
[14:06] <seb128> weird
[14:06] <seb128> the ssh agent should not be used until you ssh somewhere
[14:06] <seb128> or do you have a ssh remote folder or something?
[14:11] <gnomefreak> seb128: i havent needed my ssh key in a while. i did accently changed a setting and im working on change remember currently running apps in the startup apps under option unless it only saves it when the box is checked
[14:12] <gnomefreak> i changed my passphrase under keys and encryptions
[14:12] <gnomefreak> back to needing one
[14:13] <gnomefreak> i will keep playing with it
[14:22] <yofel> vish: updated the no-package response on the wiki page with the one brian set for the gm scrpts (https://code.edge.launchpad.net/~yofel/canonical-qa-tracking/gm-response-pa/+merge/31694) does that sound good?
[14:27] <vish> yofel: looks good to me :)
[14:27] <yofel> actually that was the original merge
[14:27] <yofel> vish: https://wiki.ubuntu.com/Bugs/Responses#Bugs%20without%20a%20package
[14:35] <vish> yofel: oops! got distracted!  yeah , i was wondering why "ubuntu-bug" was removed from the wiki
[14:36] <vish> yofel: we could use: "When reporting bugs in the future please use 'ubuntu-bug' and the name of the package affected "
[14:36] <vish> yofel: no need to mention apport
[14:37] <gnomefreak> if you add the apport-collect
[14:37] <vish> gnomefreak: "reporting" ;)
[14:37] <gnomefreak> ah
[14:37] <vish> yofel: but the reason i didnt add it was because i dint know why it was removed
[14:37] <yofel> I'm just trying to find out..
[14:39] <yofel> actually, ubuntu-bug was never mentioned it seems
[14:40] <yofel> like here a rev from last year https://wiki.ubuntu.com/Bugs/Responses?action=recall&rev=265#Bugs%20without%20a%20package
[14:40] <vish> yofel: use the direct link to : https://help.ubuntu.com/community/ReportingBugs ,the wiki link is just a refresh page
[14:41] <gnomefreak> should i file the nvidia+kernel bug aganst linux or nvidia-current
[14:43] <yofel> vish: done for the wiki page
[14:45] <gnomefreak> yofel: the second link?
[14:45] <vish> yofel: also , "use apport by using 'ubuntu-bug'" > "use 'ubuntu-bug'"  ?
[14:46] <vish> my system is totally borked :(
[14:46] <yofel> IMHO it wouldn't be bad for people to know that they're using apport if we're already not using apport-bug
[14:47] <yofel> gnomefreak: second link?
[14:47] <vish> had a harddrive check failure , accepted to auto-correct and several things seem to have gotten reverted! :/
[14:47] <gnomefreak> the ReportingBugs link?
[14:48] <yofel> gnomefreak: I changed the 2nd one https://wiki.ubuntu.com/Bugs/Responses#Bugs%20without%20a%20package
[14:48] <vish> yofel: not sure why we need to mention that we use apport.. it would just confuse, that would be a response used for everyone, not just for those running a dev release
[14:48] <gnomefreak> yofel: thanks
[14:49] <vish> yofel: anyway , a second pair of eyes would be good too :)
[14:49] <gnomefreak> i also have buttonlacethong (not sure if that is current spelling or not
[14:49] <gnomefreak> damn
[14:49] <vish> gnomefreak: whaaaaaT1
[14:50] <vish> lol!
[14:50] <gnomefreak> i was talking to someone else.
[14:50] <gnomefreak> we are joking around on aim
[14:50] <yofel> ^^
[14:50] <Pici> riiight
[14:50] <vish> gnomefreak: yeah , right , you were only joking ;p
[14:50] <gnomefreak> :)
[14:51] <gnomefreak> apport is slow atm like really slow
[14:54] <gnomefreak> still going. that is about 5 minutes so far
[15:04] <vish> devildante: http://imgur.com/2NOVK nice work!
[15:05] <devildante> thx, vish :)
[15:05] <greg-g> vish: that is live in maverick?
[15:05] <greg-g> devildante: ^
[15:05] <vish> greg-g: not yet :)
[15:05] <greg-g> ahh
[15:05] <vish> thats his branch
[15:05] <greg-g> looks awesome though
[15:05] <greg-g> devildante++
[15:06] <devildante> still a little slow though, but mvo said he would take care of it :)
[15:06] <greg-g> awesome
[15:06] <vish> devildante: mpt is reviewing it as we speak :) !
[15:06] <devildante> oh oh oh great :p
[15:06] <vish> devildante: if you finish that fast , we can merge it for Maverick :)
[15:07] <devildante> yay!
[15:07] <devildante> It's already finished (for me)
[15:08] <devildante> because my pathetic python/pygtk skills mean I can't fix the slowness
[15:08] <devildante> So I think I'll just wait mpt's verdict :p
[16:44] <cjae> wow a bugs channel
[16:44] <cjae> : )
[16:45]  * cjae hopes there is someone nice enough to report a bug
[16:47] <devildante_> cjae: no, you have to do everything by yourself, muhaha :p
[16:47] <charlie-tca> cjae: this channel is for discussion of the bug reports filed. To see the actual bugs filed, there is #ubuntu-bugs-announce
[16:47] <cjae> No I just suck at reporting them since I never know the real underlying problem :P
[16:48] <devildante_> cjae: what's your problem?
[16:48] <cjae> one sec trying to ge t some detail
[16:51] <cjae> http://kde-look.org/content/show.php/Palmscan+?content=126482 ok I think maybe this is causing part of  it, it is my theme for kdm
[16:52] <cjae> might also be the shitty properitary ati driver but I think it was doing it with the opensource one as well
[16:54] <cjae> when I login the computer sometimes freezes on the kde splash screen and I mean freeze hard like no tty sometimes
[16:55] <cjae> like hard reset is the only way and sometimes it just works upon reboot
[16:55] <devildante_> cjae: does it occur when using the default kdm theme?
[16:55] <cjae> could that theme cause that kind of problem?
[16:56] <devildante_> cjae: idk, it could be
[16:56] <devildante_> cjae: it's preferable to use default settings
[16:57] <devildante_> cjae: can you test?
[16:57] <cjae> I think it did with it too but this is my first time with a ati system really, so I cant really judge the comparison with nvidia
[16:59] <cjae> but when I login with the default stuff the is sort of graphic tearing at the  top of the screen that seems to fixed by using a non-default theme in the ....
[16:59] <cjae> workspace theme
[16:59] <cjae> sorry trying hard to use right terminalogy
[17:00] <devildante_> cjae: can you precise when it does happen? (everytime, every 2 reboots...)
[17:01] <cjae> also the ati opensource driver really misdetects my tv via hdmi (my monitor is hooked up via dvi)
[17:01] <cjae> devildante_: every two, its very weird
[17:02] <cjae> brb 1
[17:04] <cjae> ok
[17:06] <cjae> so I think the theme - might - be the login thing but doesnt explain the tearing sometimes, the tearing is sort of like that bad tearing in kde 4.1 and such
[17:08] <cjae> I spoke about the ati opensource in #radeon but they told me it was tvs fault, hdmi overscan that couldnt be turned off or something, checked all menu, nothing, used properitary, worked fine
[17:10] <cjae> also when I FIrst installed 10.04 I had I nvidia card and the nouveau driver had vertical hold issue to tv too but that was via svideo, never got time to report that either
[17:11] <cjae> other than those things 10.04 has been pretty sweet
[17:14] <cjae> devildante_: what do you mean test?
[17:15] <cjae> like change the theme back and forth
[17:15] <devildante_> I meant test it with the default kdm theme
[17:17] <cjae> sure but I am lame at reporting because either I dont have enough info in the report or I get lame things back, like "have you tried upgrading" or this will not be passed on to devs
[17:18] <cjae> or too little time
[17:18] <cjae> :(
[17:19] <cjae> brb will test theme
[17:30] <cjae> ok so it wont do it now with either theme on and a bunch of apps open and restore session on/off in kde
[17:30] <cjae> but it really does happen
[17:31] <cjae> gf tried restarting system three times last night and nothing all hung on kdm then when I got home I restarted she watched and it just went
[17:32] <cjae> she is proficent enough to know to like she didnt press recovery mode or anything, it really hung after burning a bluray disc data failed
[17:33] <cjae> as well
[17:35] <cjae> oh which brings me to k3b is broken for bluray as well, sent a bug report for that as well, that report went well though, got am email from sabastian saying it had been fixed
[17:35] <cjae> think it was him anyway
[17:36] <cjae> think the k3b is still broken in 10.04 had to use nero linux
[17:36] <cjae> :(
[17:38] <cjae> also these are never upgraded systems either as a fresh install when distro changes
[17:39] <cjae> always as a *
[17:40]  * cjae loves the advancement on the opensource video drivers though
[17:42] <cjae> anyway have seriously cut into time much needed for other things, if anyone can make use of this then great, if not, then sorry plugging up channel :)
[17:43] <cjae> all ati issues where on 64 bit too
[20:32] <vish> who assigns bugs to the Ubuntu Desktop team?
[20:34] <vish> can anyone assign?
[20:35] <seb128> we stopped assigning bugs to that team
[20:35] <yofel> er, wasn't that their previous way of tracking thins?
[20:35] <yofel> ah
[20:35] <seb128> it was useful to list bugs on any components tracked by the team
[20:35] <seb128> but we have better way to do that nowadays
[20:36] <vish> seb128: yeah , thought so , was wondering if it had changed , thanks
[20:36] <yofel> you might want to fix https://wiki.ubuntu.com/DesktopTeam/Bugs then, it says 'Our bugs have the assignee desktop-bugs ' under 'Links'
[20:36] <seb128> right
[20:37] <vish> yofel:  nah , Bug 613198 got assigned to the team itself! so was confused
[20:37] <ubot2> Launchpad bug 613198 in indicator-sound (Ubuntu) "indicator-sound requests an invalid libido version (affects: 1) (heat: 6)" [Medium,New] https://launchpad.net/bugs/613198
[20:38] <yofel> ah
[20:59] <hggdh> wow!
[21:03] <vish> hggdh: ??? finally ,someone told you the bugsquad secret? :)
[21:04]  * vish hides
[21:05]  * vish pretty sure hggdh is gonna kick a few of our asses :D
[21:05]  * hggdh looks for vish, but cannot find him
[21:05] <vish> hggdh: when i our ro_bot coming back?
[21:06] <vish> is*
[21:09] <hggdh> bug 1
[21:09] <ubot2> Launchpad bug 1 in tilix (and 18 other projects) "Microsoft has a majority market share (affects: 509) (heat: 2644)" [High,New] https://launchpad.net/bugs/1
[21:10] <hggdh> vish: this one ^?
[21:10] <vish> now , i'm confused :D
[21:10] <vish> hggdh: i was asking about pedro_  :)
[21:12] <hggdh> vish: oh. Sorry, difficult to see the difference between them two
[21:12] <vish> true!
[21:12] <hggdh> I think he is in next week, had two conferences to go
[21:12] <vish> cool..
[22:24] <BUGabundo> evening
[22:27] <bcurtiswx> Hola
[23:38] <km0r3> I need to forward bug 613622 to project's bug tracker on SourceForge. I've opened a new bug and copypasted the information; is this the only way for forwarding bugs to SF?
[23:38] <ubot2> Launchpad bug 613622 in qtpfsgui (Ubuntu) "qtpfsgui crash (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/613622
[23:50] <micahg> km0r3: yeah, you can link the bug if there's an upstream project in LP
[23:52] <km0r3> micahg: ah, too bad :/
[23:52] <km0r3> micahg: well, thank you for th answer
[23:53] <micahg> km0r3: no, you have to do what you did first, but you can then link it in LP
[23:53] <micahg> km0r3: where's the SF bug?
[23:55] <km0r3> micahg: ok, I did that
[23:55] <km0r3> micahg: http://sourceforge.net/tracker/?func=detail&aid=3039712&group_id=183831&atid=906820
[23:56] <micahg> km0r3: yep, you did it, now I can mark our bug triaged
[23:56] <ubot2> km0r3: Error: <Bugtracker.plugin.Sourceforge instance at 0xb6b2d0c> bug 3039712 not found
[23:56] <km0r3> WTF?
[23:56] <micahg> km0r3: that's pretty useless both for upstream and us actually
[23:56] <micahg> they'll need a backtrace at a minimum
[23:56] <micahg> as would we
[23:57] <km0r3> micahg: so, we should mark it incomplete and request more information?
[23:58] <micahg> km0r3: yes, there should be a response requesting a backtrace
[23:59] <km0r3> micahg: so what's the attachment of the bug? http://launchpadlibrarian.net/53064364/_usr_bin_qtpfsgui.1000.crash