From kirrus at kirrus.co.uk Tue May 1 19:45:57 2007 From: kirrus at kirrus.co.uk (Kirrus) Date: Tue, 01 May 2007 20:45:57 +0100 Subject: GUI to bughelper? In-Reply-To: References: Message-ID: <1178048757.8406.4.camel@asus.lan> Hello, I'm a newbie to this list, so first hello :) Secondly, I took a look at bughelper. Is anyone working on a GUI for it, or can I have a crack at it. I'm pretty much a newbie at programming as well, but I'd like to try. I'd probably use Gambas, heard great things about it. Anyone object: is there already a GUI in the works / out there? Regards, Johnathon -------------- next part -------------- An HTML attachment was scrubbed... URL: From norsetto at alice.it Wed May 2 12:27:39 2007 From: norsetto at alice.it (Cesare Tirabassi) Date: Wed, 02 May 2007 14:27:39 +0200 Subject: Debugging sound problems Message-ID: <1178108859.5864.12.camel@desktop> Dear all, I've stumbled upon this script: http://www.linux-sound.info/alsa/scripts/alsa-info.sh I feel this might be very handy when debugging sound problems. The user can easily download and launch the script and the script will automatically collect all relevant information and send the results to pastebin. I have added a couple of lines about this to the sound debugging guide: https://help.ubuntu.com/community/DebuggingSoundProblems I hope you will find this tool useful. Happy debugging! From quail.linux at gmail.com Wed May 2 23:47:20 2007 From: quail.linux at gmail.com (Dale) Date: Thu, 3 May 2007 09:17:20 +0930 Subject: Debugging sound problems In-Reply-To: <1178108859.5864.12.camel@desktop> References: <1178108859.5864.12.camel@desktop> Message-ID: <9b3004970705021647v4563a58cp39afed8b2b9d24ae@mail.gmail.com> Hi, I have tested the script and all i get is errors. :~/Desktop$ sh alsa-info.sh alsa-info.sh: 151: [[: not found ALSA Information Script v 0.4.20 ---------------------------- alsa-info.sh: 157: [[: not found alsa-info.sh: 172: [[: not found alsa-info.sh: 262: [[: not found alsa-info.sh: 351: [[: not found alsa-info.sh: 380: Syntax error: Bad substitution I have tried running it under root aswell and get the same errors Regards Dale On 5/2/07, Cesare Tirabassi wrote: > Dear all, > > I've stumbled upon this script: > > http://www.linux-sound.info/alsa/scripts/alsa-info.sh > > I feel this might be very handy when debugging sound problems. The user > can easily download and launch the script and the script will > automatically collect all relevant information and send the results to > pastebin. > > I have added a couple of lines about this to the sound debugging guide: > > https://help.ubuntu.com/community/DebuggingSoundProblems > > I hope you will find this tool useful. > > Happy debugging! > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -- [WWW] http://southernvaleslug.org/ [IRC] #southern-vales.lug on irc.freenode.net "The significant problems we face cannot be solved at the same level of thinking we were at when we created them" Albert Einstein From towsonu2003 at gmail.com Thu May 3 15:41:30 2007 From: towsonu2003 at gmail.com (t u) Date: Thu, 03 May 2007 11:41:30 -0400 Subject: ubuntu membership / community In-Reply-To: <85CC9FBE4A3BB243A79038DD6F5AE723030B3A72@mmug1.sbec.int> References: <85CC9FBE4A3BB243A79038DD6F5AE723030B3A72@mmug1.sbec.int> Message-ID: <463A02AA.1040902@gmail.com> Hi, First of all, welcome :) You might want to check this web page regarding participation in Ubuntu: http://www.ubuntu.com/community/participate The first thing that came to my mind when you mentioned that you test Ubuntu on Dell machines was these two web pages: https://wiki.ubuntu.com/HardwareSupportMachinesLaptopsDell https://wiki.ubuntu.com/HardwareSupportMachinesDesktopsDell I'm sure others will give much better advice on a starting point, but maybe you could help with those two compatibility databases? Or maybe check out the bugs that are occuring in Dell systems? The bug system is located at https://launchpad.net/ubuntu/+bugs . I'm CC'ing the bugsquad in case they know more about this. If you're interested in anything else, you can just jump in and enjoy :) Great to see you here :) t u Sharp, Michael wrote: > I am very interested in helping in the effort of being a member of > ubuntu project. I have tested ubuntu on several systems here at my > company for which are all Dells. Since we are a Dell shop I have the > ability to load ubuntu on all different sorts of systems. This would be > a GREAT help to the community of ubuntu. As you can tell I very > interested in being a member to support and troubleshot varies issue > around ubuntu as wells hardware problems. My back round stems around > I.T, so if you fill that I can help with this let me know. I am not a > programmer but I do a lot of R & D around Linux for which I have gotten > a lot of my friends to switch too. Again I believe I would be a GREAT > asset to the community of ubuntu. Thank you for time. > > > > Regards, > > Michael Sharp > From konghao at bsw.net.cn Tue May 8 08:50:24 2007 From: konghao at bsw.net.cn (konghao) Date: Tue, 8 May 2007 16:50:24 +0800 Subject: All Side Testing Report of Ubuntu from BSTQC Message-ID: Hi, there Thanks for reading this email. After the hard work of guys in our company BSTQC(Beijing Software Testing & QA Center), we release our new all-sided testing report for Ubuntu-6.10 which we finished several days before. In our testing report, we've listed: 19 S2-bug(very serious), 108 S3-bug(middle serious), 106 S4-bug(normal), 33 S5-bug-for-suggestions(suggestions). Totally 266 bugs. Even the new Ubuntu 7.04 has been released, this report would be very valuable for all developers and users. Actually, there are many bugs are related to parent/upstream applications because we took default complete installation of Ubuntu-6.10 CD as test target, I think if someone have interest about them, they can have a look or just ignore. If you didn't find the version record of these applications, they are the default version in Ubuntu-6.10 CD. You can download it from BSTQC ftp server. Anyone has problems with downloading the testing report please contact me by sending email to konghao at bsw.net.cn. If some one could provide downloading server outside of China and put this testing report on your server, it would be great appreciated! FTP address: 210.76.123.18 username: ostl password: ostl_ubuntu The subdirectory of newest testing report is "ubuntu 6.10", please check them. Since the human resource issue and the the limitation of internet-access, it's regrettable that these guys can not register bug one by one in launchpad. The all-side testing of newest Ubuntu 7.04 are ongoing, we will release the testing report as soon as possible. Thanks! & Best regards! Hao Kong - BSTQC ---------------------------------------------- National Application Software Testing Labs Beijing Software Testing & QA Center Add:Building 3A,Zhongguancun Software Park, Shangdi,Haidian District,Beijing,China 100094 TEL:(+86)-010-82825511-726 Fax:(+86)-010-82826408 Email:konghao at bsw.net.cn ----------------------------------------------- From daniel.holbach at ubuntu.com Tue May 8 12:11:53 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Tue, 08 May 2007 14:11:53 +0200 Subject: bughelper idea: buglog In-Reply-To: <462D334E.9070807@ubuntu.com> References: <462D334E.9070807@ubuntu.com> Message-ID: <1178626313.9182.15.camel@lovegood> Hello everybody, I'm CCing the BugSquad on this topic as this might change and improve our triage workflow soon. Please give us input on the idea below. We had a session about it here at UDS and I did some initial hacking on it at https://code.launchpad.net/~bughelper-dev/buglog/main At the moment we envision this as a Firefox plugin, which would open a pop-up after you changed a bug and asked you to * add a comment about what you did * put your reply into the categories "everything's ok with the bug now", "it'd be nice if somebody checked what I did" or "I had no clue what to do with the bug". Am Dienstag, den 24.04.2007, 00:29 +0200 schrieb Henrik Nilsen Omma: > I've been mulling over for a while a new feature of bughelper that would > help each person structure their bug triaging better and learn from others. > > Developers and experienced triagers generally know how to deal with any > given bug. They either know package well enough to be able to move the > bug on to its next stage They may know how it should be fixed and assign > it to themselves or someone else, they recognise that it needs more > info, that it belongs to a different package, that it should be moved > upstream, etc. Failing all that they will know who else on the team > would know better and ask. A developer will very rarely look at a bug > and just say 'I dunno, I give up' and walk away. > > Novice bug triagers, myself included, do this often. And frequently it > is the right thing to do. There are certain bugs that I simply don't > know where to start working on. It may have all the right log files > attached and thus not need any more information. I can recognise some > characteristic traits in ubiquity log files, but other times I simply > don't know what to make of it. The best use of my time in that case is > probably to skip it (or spend half a day reading code and programming > text books for that one bug). By putting it aside I can move on to other > bugs where I can be more useful and leave this one to someone more > experienced. But, I would like to note that fact down somewhere, and > adding an 'I don't know' (followed by several 'me too don't know', just > creates noise). > > When I was doing bulk triage of ubiquity I would make a list of the > mysterious bugs, group them to the best of my ability and send them off > in a batch by email to Colin. I would make special note of bugs that > looked like a new issue that he should know about or that were > noteworthy in some other way. It would be good to have a standard way of > doing this without everyone emailing or pinging the core developers > every day. > > I suggest an approach to this in this spec: > https://wiki.ubuntu.com/BugHelper/BugLog At the moment we're trying to gather use cases and ideas for this. So please don't be shy and add your thoughts on this thread. Sky's the limit. Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: From pochu at ubuntu.com Tue May 15 18:51:31 2007 From: pochu at ubuntu.com (Emilio Pozuelo Monfort) Date: Tue, 15 May 2007 20:51:31 +0200 Subject: StableReleaseUpdates: liferea 1.2.10c-0ubuntu1.1 available for testing in feisty-proposed In-Reply-To: <200705111814.07290.ubuntu@kitterman.com> References: <1178139407.6360.9.camel@FUN.ncat.edu> <200705111814.07290.ubuntu@kitterman.com> Message-ID: <464A0133.7060405@ubuntu.com> Hello, A testing version of liferea has landed in dapper-proposed. To test, please add: deb http://archive.ubuntu.com/ubuntu/ feisty-proposed main to your sources.list(5). Then, update and upgrade (or install) liferea. Please provide feedback to Bug #103688: https://bugs.launchpad.net/ubuntu/feisty/+source/liferea/+bug/103688 Thanks, Emilio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From pochu at ubuntu.com Tue May 15 21:47:43 2007 From: pochu at ubuntu.com (Emilio Pozuelo Monfort) Date: Tue, 15 May 2007 23:47:43 +0200 Subject: StableReleaseUpdates: liferea 1.2.10c-0ubuntu1.1 available for testing in feisty-proposed In-Reply-To: <464A1DA2.9080903@gmail.com> References: <1178139407.6360.9.camel@FUN.ncat.edu> <200705111814.07290.ubuntu@kitterman.com> <464A0133.7060405@ubuntu.com> <464A1DA2.9080903@gmail.com> Message-ID: <464A2A7F.8070609@ubuntu.com> t u wrote: > Emilio Pozuelo Monfort wrote: >> Hello, >> >> A testing version of liferea has landed in dapper-proposed. To test, >> please add: >> >> deb http://archive.ubuntu.com/ubuntu/ feisty-proposed main > [...] > > Hi, > > Is this for Feisty or Dapper? Your email says "dapper-proposed" but the > sources.list line says "feisty-proposed". Sorry, was a mistake :) It's for feisty-proposed. > Thanks :) Cheers Emilio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From pochu at ubuntu.com Fri May 18 17:32:24 2007 From: pochu at ubuntu.com (Emilio Pozuelo Monfort) Date: Fri, 18 May 2007 19:32:24 +0200 Subject: StableReleaseUpdates: liferea 1.2.10c-0ubuntu1.1 available for testing in feisty-proposed Message-ID: <464DE328.2010705@ubuntu.com> (Resending, the .debs are now on the repository). Hello, A testing version of liferea has landed in feisty-proposed. To test, please add: deb http://archive.ubuntu.com/ubuntu/ feisty-proposed main to your sources.list(5). Then, update and upgrade (or install) liferea. Please provide feedback to Bug #103688: https://bugs.launchpad.net/ubuntu/feisty/+source/liferea/+bug/103688 Thanks, Emilio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 190 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From brian at ubuntu.com Thu May 24 04:15:04 2007 From: brian at ubuntu.com (Brian Murray) Date: Wed, 23 May 2007 21:15:04 -0700 Subject: Bug Tagging Message-ID: <20070524041504.GF6814@murraytwins.com> I've recently started using some new bug tags[1] as an alternative way to identify and find bugs. For example, I created a 'metabug' tag for bugs that have a high likely-hood of duplication. An example of a metabug is 53923 "tifm: Texas Instruments Card reader not working" where some specific Ti Multimedia Cards aren't reading cards. This bug is currently in progress but we do have 20 duplicates of it, and more could come in as the hardware is prevalent. The idea of a 'metabug' tag appeals to my workflow as I look a lot of different packages and this becomes an easy reference sheet for common bugs. It could also be useful for new triagers and those coming back from a break. Please have a look at the list of current 'metabugs'[2] and tag more if you see them. In an effort to make openoffice.org bugs make them more approachable, I have started use tags such as 'ooo-calc' to identify which specific application the bug appears in. Finally, there is the 'commercial' tag to identify bugs in packages like Opera that don't yet exist in Launchpad. As I understand it these packages may appear in Launchpad so I'd like us to be able to find those bugs again and assign them to the right package. Please take a moment to look at the list of tags currently in use, add any tags you think would be useful, and subscribe to the wiki page. [1] https://wiki.ubuntu.com/BugSquad/Tags [2] https://launchpad.net/ubuntu/+bugs?field.tag=metabug Thanks, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From freddymartinez9 at ubuntu.com Thu May 24 04:29:09 2007 From: freddymartinez9 at ubuntu.com (Freddy Martinez) Date: Wed, 23 May 2007 23:29:09 -0500 Subject: Bug Tagging In-Reply-To: <20070524041504.GF6814@murraytwins.com> References: <20070524041504.GF6814@murraytwins.com> Message-ID: [snip] > In an effort to make openoffice.org bugs make them more approachable, > I have started use tags such as 'ooo-calc' to identify which specific > application the bug appears in. Would it also be beneficial to add Mozilla Team's bug tags,[1]. The only problem I see is bug triagers who are unfamiliar with MT's practices attempting to use these tags. What do you all think? [snip] [1] https://wiki.ubuntu.com/MozillaTeam/Bugs/Tags -- Best, Freddy Martinez Ubuntu. Linux for human beings. www.chi.ubuntu-us.org From brian at ubuntu.com Thu May 24 15:26:55 2007 From: brian at ubuntu.com (Brian Murray) Date: Thu, 24 May 2007 08:26:55 -0700 Subject: Bug Tagging In-Reply-To: References: <20070524041504.GF6814@murraytwins.com> Message-ID: <20070524152655.GG6814@murraytwins.com> On Wed, May 23, 2007 at 11:29:09PM -0500, Freddy Martinez wrote: > [snip] > >In an effort to make openoffice.org bugs make them more approachable, > >I have started use tags such as 'ooo-calc' to identify which specific > >application the bug appears in. > Would it also be beneficial to add Mozilla Team's bug tags,[1]. The > only problem I see is bug triagers who are unfamiliar with MT's > practices attempting to use these tags. What do you all think? > [snip] > [1] https://wiki.ubuntu.com/MozillaTeam/Bugs/Tags Personally, I think these tags are more process specific where as the tags we currently have listed on the BugSquad/Tags page are a description of the bug. Perhaps just putting links to team's tagging pages would be the best idea. -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From hmontoliu at gmail.com Thu May 24 14:05:16 2007 From: hmontoliu at gmail.com (Hilario J. Montoliu) Date: Thu, 24 May 2007 16:05:16 +0200 Subject: Bug Tagging In-Reply-To: References: <20070524041504.GF6814@murraytwins.com> Message-ID: <1180015516.6443.5.camel@paleo.chiti.org> El mié, 23-05-2007 a las 23:29 -0500, Freddy Martinez escribió: > [snip] > > In an effort to make openoffice.org bugs make them more approachable, > > I have started use tags such as 'ooo-calc' to identify which specific > > application the bug appears in. > Would it also be beneficial to add Mozilla Team's bug tags,[1]. The > only problem I see is bug triagers who are unfamiliar with MT's > practices attempting to use these tags. What do you all think? > [snip] > [1] https://wiki.ubuntu.com/MozillaTeam/Bugs/Tags In addition to Freddy's post, IMHO this link [1] might be more descriptive about how do we (the Mozilla Team [2]) use the MT's tags. [1] https://wiki.ubuntu.com/MozillaTeam/Bugs/States [2] https://launchpad.net/~mozillateam -- Hilario J. Montoliu -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Esta parte del mensaje está firmada digitalmente URL: From brian at ubuntu.com Thu May 24 17:49:44 2007 From: brian at ubuntu.com (Brian Murray) Date: Thu, 24 May 2007 10:49:44 -0700 Subject: Bug Tagging In-Reply-To: <714626160705240954j5190a7cas8dcee01596825469@mail.gmail.com> Message-ID: <20070524174944.GH6814@murraytwins.com> On Thu, May 24, 2007 at 12:54:06PM -0400, Yuriy Kozlov wrote: > >In an effort to make openoffice.org bugs make them more approachable, > >I have started use tags such as 'ooo-calc' to identify which specific > >application the bug appears in. Finally, there is the 'commercial' tag > >to identify bugs in packages like Opera that don't yet exist in > >Launchpad. As I understand it these packages may appear in Launchpad so > >I'd like us to be able to find those bugs again and assign them to the > >right package. > > > >Please take a moment to look at the list of tags currently in use, add > >any tags you think would be useful, and subscribe to the wiki page. > > > >[1] https://wiki.ubuntu.com/BugSquad/Tags > >[2] https://launchpad.net/ubuntu/+bugs?field.tag=metabug > > > > Would it be useful to start doing something like this for kdebase and > for guidance? If you mean to tag kdebase bugs based on their component i.e. a kicker bug tagged as 'kdebase-kicker' I think this is a great idea. Looking at the approximately 500 kdebase bugs it is hard to know where to start and I think this will help a lot. -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From brian at ubuntu.com Sat May 26 05:13:55 2007 From: brian at ubuntu.com (Brian Murray) Date: Fri, 25 May 2007 22:13:55 -0700 Subject: Ubuntu Hug Day: 30 May 2007 Message-ID: <20070526051355.GE6814@murraytwins.com> I'm happy to announce our next Hug Day on Wednesday, May 30th. This Hug Day we are going to do a couple of things differently. The event will be held in #ubuntu-devel this time. Additionally, a wiki page has been created with tables of bugs in specific categories to work on. Notice there is a column for you to add your name after meeting the goal for a bug! https://wiki.ubuntu.com/UbuntuBugDay/20070530 This list will be finalized shortly before 0001 UTC on the 30th to ensure that all the bugs on it still need attention. Our goal is to deal with all of the bugs on that list. So on 30 May 2007, in all timezones, we'll be meeting in #ubuntu-devel on irc.freenode.net for another Ubuntu Hug Day. https://wiki.ubuntu.com/UbuntuBugDay While you are welcome to apply to join the Ubuntu QA team anytime, Hug Day is a great day to join! https://wiki.ubuntu.com/UbuntuQA If you're interested in helping, please stop by. And feel free to ask bdmurray, dholbach and the rest of the team for ways to help out. Hope to see you there and your name on the list of bug huggers! -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From eternal1 at eternal1.com.ar Sun May 27 06:44:24 2007 From: eternal1 at eternal1.com.ar (Diego Vazquez) Date: Sun, 27 May 2007 06:44:24 -0000 Subject: [Bug 117114] [apport] beryl-settings crashed with ImportError in () References: <20070527064424.16508.93246.malonedeb@potassium.ubuntu.com> Message-ID: <20070527064424.16508.93246.malonedeb@potassium.ubuntu.com> Public bug reported: Binary package hint: beryl-settings [apport] beryl-settings crashed with ImportError in () ProblemType: Crash Architecture: amd64 Date: Sun May 27 03:36:37 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/beryl-settings InterpreterPath: /usr/bin/python2.5 Package: beryl-settings 0.2.1-0ubuntu1 PackageArchitecture: all ProcCmdline: python /usr/bin/beryl-settings ProcCwd: /home/eternal1 ProcEnviron: PATH=/home/eternal1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=es_ES.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/beryl-settings'] SourcePackage: beryl-settings Traceback: Traceback (most recent call last): File "/usr/bin/beryl-settings", line 22, in import berylsettings ImportError: No module named berylsettings Uname: Linux node02 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 GNU/Linux ** Affects: beryl-settings (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] beryl-settings crashed with ImportError in () https://bugs.launchpad.net/bugs/117114 You received this bug notification because you are a member of Ubuntu BugSquad, which is a bug contact for beryl-settings in ubuntu. From eternal1 at eternal1.com.ar Sun May 27 06:44:24 2007 From: eternal1 at eternal1.com.ar (Diego Vazquez) Date: Sun, 27 May 2007 06:44:24 -0000 Subject: [Bug 117114] Re: [apport] beryl-settings crashed with ImportError in () References: <20070527064424.16508.93246.malonedeb@potassium.ubuntu.com> Message-ID: <20070527064424.16508.80327.malone@potassium.ubuntu.com> ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7846849/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7846850/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7846851/ProcStatus.txt -- [apport] beryl-settings crashed with ImportError in () https://bugs.launchpad.net/bugs/117114 You received this bug notification because you are a member of Ubuntu BugSquad, which is a bug contact for beryl-settings in ubuntu. From jerome.guelfucci at gmail.com Sun May 27 07:06:12 2007 From: jerome.guelfucci at gmail.com (=?utf-8?b?SsOpcsO0bWUgR3VlbGZ1Y2Np?=) Date: Sun, 27 May 2007 07:06:12 -0000 Subject: [Bug 117114] Re: [apport] beryl-settings crashed with ImportError in () References: <20070527064424.16508.93246.malonedeb@potassium.ubuntu.com> Message-ID: <20070527070612.31670.43809.malone@gangotri.ubuntu.com> *** This bug is a duplicate of bug 107275 *** https://bugs.launchpad.net/bugs/107275 Thank you for your bug report, this particular bug has already been reported by other users. Feel free to report any other bug you find. ** This bug has been marked a duplicate of bug 107275 [apport] beryl-settings crashed with ImportError in () -- [apport] beryl-settings crashed with ImportError in () https://bugs.launchpad.net/bugs/117114 You received this bug notification because you are a member of Ubuntu BugSquad, which is a bug contact for beryl-settings in ubuntu. From jerome.guelfucci at gmail.com Sun May 27 07:06:18 2007 From: jerome.guelfucci at gmail.com (=?utf-8?b?SsOpcsO0bWUgR3VlbGZ1Y2Np?=) Date: Sun, 27 May 2007 07:06:18 -0000 Subject: [Bug 117112] Re: [apport] beryl-settings crashed with ImportError in () References: <20070527063219.31670.68528.malonedeb@gangotri.ubuntu.com> Message-ID: <20070527070618.12421.84973.malone@gandwana.ubuntu.com> *** This bug is a duplicate of bug 107275 *** https://bugs.launchpad.net/bugs/107275 Thank you for your bug report, this particular bug has already been reported by other users. Feel free to report any other bug you find. ** This bug has been marked a duplicate of bug 107275 [apport] beryl-settings crashed with ImportError in () -- [apport] beryl-settings crashed with ImportError in () https://bugs.launchpad.net/bugs/117112 You received this bug notification because you are a member of Ubuntu BugSquad, which is a bug contact for beryl-settings in ubuntu. From jerome.guelfucci at gmail.com Sun May 27 07:06:25 2007 From: jerome.guelfucci at gmail.com (=?utf-8?b?SsOpcsO0bWUgR3VlbGZ1Y2Np?=) Date: Sun, 27 May 2007 07:06:25 -0000 Subject: [Bug 117110] Re: [apport] beryl-settings crashed with ImportError in () References: <20070527062728.16508.62377.malonedeb@potassium.ubuntu.com> Message-ID: <20070527070626.16508.12500.malone@potassium.ubuntu.com> *** This bug is a duplicate of bug 107275 *** https://bugs.launchpad.net/bugs/107275 Thank you for your bug report, this particular bug has already been reported by other users. Feel free to report any other bug you find. ** This bug has been marked a duplicate of bug 107275 [apport] beryl-settings crashed with ImportError in () -- [apport] beryl-settings crashed with ImportError in () https://bugs.launchpad.net/bugs/117110 You received this bug notification because you are a member of Ubuntu BugSquad, which is a bug contact for beryl-settings in ubuntu. From daniel.holbach at ubuntu.com Tue May 29 09:58:27 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Tue, 29 May 2007 11:58:27 +0200 Subject: Bug Contacts Message-ID: <1180432707.6337.2.camel@bert> Hello everybody, somebody in ~bugsquad made the team a Bug Contact of beryl-settings. Please don't do that. The BugSquad is not meant to triage bugs of specific packages, but to be a lose group that tries to clean up Malone, fix bugs and think of clever ways to organise the bug workflow. Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From daniel.holbach at ubuntu.com Tue May 29 14:21:31 2007 From: daniel.holbach at ubuntu.com (Daniel Holbach) Date: Tue, 29 May 2007 16:21:31 +0200 Subject: Universe HUG Day Message-ID: <1180448491.5853.16.camel@bert> Hello everybody, we're having a Universe HUG Day again! How it's different from a normal HUG Day? * Together we will look at Universe and Multiverse bugs * We will work on bugs linked from http://wiki.ubuntu.com/MOTU/Bugs * We will try to identify bugs that are suited for new contributors. Using the new Launchpad Mentoring feature, tagging bugs as 'bitesize' and/or 'packaging' will help with that too. MOTU Mentors will use these bugs to give new contributors a chance to get acquainted with Ubuntu Development tools. Join us in #ubuntu-bugs on June 2nd, all timezones, all the time. Have a nice day, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: