[01:28] <Cheesehead> Bug 784557: Looking for a second opinion
[01:28] <ubot4`> Launchpad bug 784557 in ubuntu "Searching for some proprietary software yields no results in software centre / application lens (affects: 1) (heat: 442)" [Undecided,Invalid] https://launchpad.net/bugs/784557
[01:28] <Cheesehead> I marked that bug Invalid in Brainstorm becasue it seemed like a good Wishlist or Low bug
[01:29] <Cheesehead> Looking for opinions - shouls it be Low, Wishlist, or Brainstorm?
[01:29] <Cheesehead> (dratted spelling)
[01:34] <Cheesehead> Again, I'm the one who Invalidated it in Brainstorm, not Launchpad. Somebody else did that.
[01:34] <Cheesehead> So the poor user is stuck bureaucratic limbo.
[01:50] <Cheesehead> Anyone?
[01:55] <hggdh> Cheesehead: agreed, and I reopened the bug
[01:55] <Cheesehead> Thanks for the look.
[01:56] <hggdh> Cheesehead: welcome, and thank you for looking at it
[01:57] <Cheesehead> Back to Brainstorm.....
[04:01] <CarlFK> how do I bug /etc/profile?  http://dpaste.com/548153/ blocks starting at 4 and 32 both run all the scripts in /etc/profile.d so they all get run twice
[04:06] <braiam> CarlFK: «dpkg -S /etc/profile»
[04:07] <braiam> CarlFK: it gives you al package related to the file
[04:07] <CarlFK> dpkg-query: no path found matching pattern /etc/profile.
[04:09] <CarlFK> how about: bash-completion, base-files: /etc/profile.d
[04:11] <CarlFK> http://packages.ubuntu.com/oneiric/amd64/base-files/filelist  there it is.
[04:12] <CarlFK> er, no.  there is /usr/share/base-files/profile
[04:12] <CarlFK> but it is the same file
[04:12] <CarlFK> so has the same problem, so it wins the bug.
[04:12] <micahg> CarlFK: base-files sounds right
[05:25] <cwillu_segfault> who wants to look at a crashing compiz in gdb with source?
[05:25] <cwillu_segfault> (segfault in regexec)
[05:51] <cwillu_segfault> who should get subscribed and/or poked with a compiz bug if there's now a backtrace with sourcelines attached, and no devs have commented yet?
[05:51] <cwillu_segfault> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/706918
[05:51] <ubot4`> Launchpad bug 706918 in fedora (and 2 other projects) "compiz crashed with SIGSEGV in RegexExp::evaluate() (affects: 13) (heat: 68)" [Undecided,Invalid]
[05:52] <cwillu_segfault> (it's in ubuntu too :p)
[06:00] <braiam> cwillu_segfault: I guest that it should be forwarded to the upstream
[06:00] <cwillu> sorry, could you repeat that?
[06:00] <braiam> cwillu: I guest that it should be forwarded to the upstream
[06:00] <cwillu> ah, thanks
[14:19] <robrt`> Hi bugs team
[14:19] <robrt`> Just wondering, if I come across any bugs that are either outdated / can't be reproduced anymore / are fixed by now, is there anything I could do to help clean up?
[14:19] <robrt`> E.g. https://bugs.launchpad.net/ubuntu/+source/rhythmbox-ubuntuone-music-store/+bug/532543 has been fixed ages ago
[14:19] <ubot4`> Launchpad bug 532543 in rhythmbox-ubuntuone-music-store (Ubuntu) "Cancelling paypal doesn't return to store (affects: 1) (heat: 7)" [Undecided,In progress]
[14:21] <arand> Normally you'd close (-> invali if you o no know the version/patch it was fixed in) the with a "We think it's fixed by now, if not, please feel free to reopen" I think there should be a teamplate for that..
[14:22] <robrt`> Yeah, but I'm not a Squad member :-)
[14:23] <arand> I think you can do this without being one..
[14:25] <robrt`> Ah, you're right. Thanks.
[14:29] <jibel> robrt`, it's a good practice to add an extract of the changelog, or point to the comment of an upstream bugtracker or mailing list discussion when closing an issue as 'fix released'
[14:30] <robrt`> will keep that in mind, thanks.
[15:06] <jibel> robrt`, thanks for helping with bugs :)
[15:06] <robrt`> Just getting my feet wet; it's all new and alien so far :-)
[18:36] <serfus> hey folks, can someone help me a sec with bzr related?
[18:37] <serfus> i'm trying to commit, but nothing happens... i feel pretty stupid... i guess i should do something but not sure what
[18:39] <hggdh> serfus: give us details, maybe wse can help (or direct you to a better channel)
[18:39] <serfus> i have fixed a small bug
[18:40] <serfus> what i did now is 'bzr commit --fixes=lp:789567'
[18:40] <serfus> which brought me to VIM
[18:40] <serfus> (i think so)
[18:40] <serfus> now i'm stuck
[18:40] <serfus> first time i'm doing this so....
[18:40] <serfus> :)
[18:41] <hggdh> serfus: all commits must have a commit message (explanation of what has changed, why)
[18:41] <serfus> --- This line and the following will be ignored --------------
[18:41] <serfus> modified:
[18:41] <serfus>   sessioninstaller/core.py
[18:41] <serfus> then many blank lines
[18:42] <hggdh> serfus: you can run like this: bzr commit --fixes=lp:123456 -m "sessioninstaller/core.py: changed yadda yadda to cater for blahblah"
[18:42] <hggdh> serfus: or, if you did not pass a -m, an editor will be opened; you then add in you comments there, and save (Esc ZZ)
[18:43] <serfus> hggdh, oh i think i understand!
[18:43] <serfus> give me a sec
[18:44] <serfus> just where do i add those comments?
[18:44] <hggdh> on the editor, *before* the line '--- This line and the following... ---'
[18:45] <hggdh> and then save it -- bzr will do the rest (throwing away the '... This line ...", and adding your comments to the change
[18:46] <hggdh> on doubts, there is always 'bzr commit --help' to _try_ to clean things out
[18:46] <serfus> ya this is what i should have look for
[18:46] <serfus> many thanks hggdh
[18:46] <serfus> !
[18:46] <serfus> i'll try to proceed from here
[18:46] <hggdh> serfus: you are most welcome
[18:55] <micahg> serfus: if this is for an archive upload, you can use debcommit if you make a proper changelog entry, it will automatically use the changelog entry as the commit message and do the bug linking for you
[19:00] <serfus> micahg, hum not sure if it's a archive upload
[19:01] <serfus> sounds a bit to complected for me :)
[19:01] <micahg> serfus: well, anything where you're adding a changelog entry
[19:01] <serfus> anyway, i got it already
[22:03] <Wipster> good evening all, in launchpad I have found numerous bugs reports which all come from the same problem as mine does, should I compile the list of duplicates into mine and add mine to the others? Does it help if they are all linked up?
[22:19] <braiam> Wipster: review them, search for the most complete, and mark the other ones as dupes
[22:20] <charlie-tca> if they are not kernel or xorg bugs only
[22:20] <charlie-tca> please don't dup kernel bugs
[22:24] <braiam> Wipster: don't dup kernel bugs ;)
[22:30] <Wipster> braiam, ok thanks so not xorg stuff too? The issue is with xserver
[22:31] <charlie-tca> Unless your hardware is an exact match, it is not a duplicate
[22:31] <braiam> Wipster: give some bug numbers
[22:31] <charlie-tca> and yes, almost is not exact
[22:35] <Wipster> #774978 is the best description and most full, has a lot of dupes.
[22:36] <braiam> bug 776978
[22:36] <ubot4`> Launchpad bug 776978 in xorg-server (Ubuntu) "everything on screen is garbled apart from the top bar (2 monitors, different resolutions, unity, natty) (affects: 10) (heat: 58)" [Undecided,New] https://launchpad.net/bugs/776978
[22:37] <Wipster> umm bug 774978 :)
[22:37] <ubot4`> Launchpad bug 774978 in xserver-xorg-input-synaptics (Ubuntu) "xserver crashes in RecordAReply when XRecord is enabled in syndaemon (affects: 80) (dups: 19) (heat: 366)" [High,Triaged] https://launchpad.net/bugs/774978