http://blog.gmane.org/gmane.comp.gnome.bugsquad hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2381 <pre> Dear Andre, I have sent another email just a few seconds ago to you about the tabs bug 675417 and want to know if it has been re-inserted into the properties section so I can use it in the latest version of nautilus. Sorry for using this arena to contact you but it was available. Thank you for your time Philip, San Antonio, TX </pre> Philip 2012-05-11T15:38:36 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2379 <pre>CC'ing gnome-bugsquad FYI. andre </pre> Andre Klapper 2012-04-21T23:23:30 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2378 <pre>Hi everybody, it's time again for a quarterly GNOME report to let community and companies know what has been going on between January and March 2012. Please update your section for Q1/2012 here: https://live.gnome.org/GnomeMarketing/QuarterlyReports/2012/Q1 The list of potential teams and writers: * Board and Executive Director - Karen Sandler * Bugsquad - Andre Klapper * Membership and Elections Committee - Tobias Mueller * GNOME User Groups - ??? * Accessibility Team - Alejandro Piñeiro Iglesias, Joanmarie Diggs * Outreach Program for Women - Marina Zhurakhinskaya * Localization - Petr Kovar * Documentation - ??? * Web - Andreas Nilsson, Vinicius Depizzol * Google Summer of Code 2012 - ??? * Marketing - ??? * Sysadmin - ??? * Design - ??? * Conference planning: GUADEC, GNOME.asia? - ??? If you do not have time, please consider delegating the task! There are some sections that do not have writers yet - please fill your name in on the wiki if you could write a summary. It really does not have to be long! I also assume that every writer welcomes help and input (that's why I also send this to corresponding mailing lists). We would like to finish the Q1 report before by May 11, 2012. Thanks for your help, andre </pre> Andre Klapper 2012-04-16T14:21:19 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2374 <pre>Hi Andre, Andre Klapper schreef op 19.03.2012 09:51: I haven't followed development closely as of late, but I'll take my chances to bring up the issue that in 3.3.90 on Mageia Cauldron, I cannot add my Google account which uses two-step authentication. This bug has been filed against Empathy but as far as I can tell it's valid for all kind of Google accounts: https://bugzilla.gnome.org/show_bug.cgi?id=647007. I asked about it on IRC and Owen replied that he had seen workiong two-step authentication demonstrated by dzeuthen at some point. IMHO, this is a pretty serious issue. </pre> Reinout van Schouwen 2012-03-19T10:19:01 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2373 <pre>GNOME 3.4.0 will be released in one week. Later today is HARD CODE FREEZE (but you can always ask the release-team for exceptions). This is a list of potential release blockers plus some "should-fix" tickets. This list is not necessarily complete. Feedback, updates, help from packagers, developers, maintainers, contributors, etc. is welcome. Please do speak up if some important bugs are not listed here. andre ====================================== AT-SPI =================== Orca commands are sometimes passed through to the application https://bugzilla.gnome.org/show_bug.cgi?id=671976 =================== CHEESE =================== All buttons disabled. Can not take photo or video. https://bugzilla.gnome.org/show_bug.cgi?id=671357 =================== CLUTTER-GTK =================== floating toolbar not working (in Empathy) https://bugzilla.gnome.org/show_bug.cgi?id=670874 =================== EPIPHANY =================== There are still references to the "GNOME web browser" on translations https://bugzilla.gnome.org/show_bug.cgi?id=671424 Would require string freeze breaks. =================== GDM =================== [PATCH] add automatic multi seat support https://bugzilla.gnome.org/show_bug.cgi?id=655380 =================== GNOME-CONTROL-CENTER =================== Trying to add a new language: crash while typing in the search field before the language list is completely populated https://bugzilla.gnome.org/show_bug.cgi?id=671693 Good stacktrace available. =================== GNOME-SESSION =================== fail whale extension list looks bad https://bugzilla.gnome.org/show_bug.cgi?id=671693 Needs more information and testing. [PATCH] Need signal matching Setenv dbus method so apps in initialization phase can update their env too https://bugzilla.gnome.org/show_bug.cgi?id=662528 Five patches available awaiting review for two months now gnome-session no longer starts desktop files under /usr/share/gdm/autostart/LoginWindow https://bugzilla.gnome.org/show_bug.cgi?id=663721 Inline patch that needs more work available =================== GNOME-SHELL =================== Be able to ask for IM account password https://bugzilla.gnome.org/show_bug.cgi?id=658961 Patch reviewed and needs updating; would require okay from gnome-i18n&lt; at &gt; Extension loading is broken in 3.3.90 https://bugzilla.gnome.org/show_bug.cgi?id=670477 Confirmed by another user [PATCH] networkAgent: Fix external-ui dialogs https://bugzilla.gnome.org/show_bug.cgi?id=671556 Patch needs another review and commit [PATCH] Orca doesn't present ""Overview"" name when this is focused https://bugzilla.gnome.org/show_bug.cgi?id=671378 Patch adds two new strings, needs okay from gnome-i18n&lt; at &gt; restart by typing ""r"" in the gnome-shell run-dialog 2x in one minute brings up the ""oops"" window https://bugzilla.gnome.org/show_bug.cgi?id=648384 [NEEDINFO] Gnome 3.0 and 3.2 crashing when disabling wireless https://bugzilla.gnome.org/show_bug.cgi?id=668388 Stuck as no news have been provided. Might unmark this soon. ====================================== </pre> Andre Klapper 2012-03-19T08:51:56 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2371 <pre>GNOME 3.4.0 will be released in two weeks. This is a list of potential release blockers plus some "should-fix" tickets according to yesterday's release team meeting. This list is not necessarily complete. Feedback, updates, help from packagers, developers, maintainers, contributors, etc. is welcome. Please do speak up if some important bugs are not listed here. andre ====================================== CHEESE =================== All buttons disabled. Can not take photo or video. https://bugzilla.gnome.org/show_bug.cgi?id=671357 =================== GDM =================== [PATCH] Port to GSettings https://bugzilla.gnome.org/show_bug.cgi?id=635375 [PATCH] add automatic multi seat support https://bugzilla.gnome.org/show_bug.cgi?id=655380 =================== GNOME-SESSION =================== fail whale extension list looks bad https://bugzilla.gnome.org/show_bug.cgi?id=671693 Needs more information and testing. [PATCH] Need signal matching Setenv dbus method so apps in initialization phase can update their env too https://bugzilla.gnome.org/show_bug.cgi?id=662528 Five patches available awaiting review for two months now gnome-session no longer starts desktop files under /usr/share/gdm/autostart/LoginWindow https://bugzilla.gnome.org/show_bug.cgi?id=663721 Inline patch that needs more work available fail whale triggers too easily https://bugzilla.gnome.org/show_bug.cgi?id=671694 =================== GNOME-SHELL =================== Be able to ask for IM account password https://bugzilla.gnome.org/show_bug.cgi?id=658961 Patch reviewed and needs updating; would require okay from gnome-i18n&lt; at &gt; Extension loading is broken in 3.3.90 https://bugzilla.gnome.org/show_bug.cgi?id=670477 Confirmed by another user [PATCH] Expose ATK_STATE_EXPANDABLE and ATK_STATE_EXPANDED as appropriate for Alt+Tab switcher https://bugzilla.gnome.org/show_bug.cgi?id=670719 [PATCH] Orca doesn't present ""Overview"" name when this is focused https://bugzilla.gnome.org/show_bug.cgi?id=671378 Patch adds two new strings, needs okay from gnome-i18n&lt; at &gt; [PATCH] Orca doesn't present the proper role for items on the top panel https://bugzilla.gnome.org/show_bug.cgi?id=667432 Two patches that need review [PATCH] Orca doesn't present anything when run dialog is launched https://bugzilla.gnome.org/show_bug.cgi?id=670308 Second patch needs a review, depends on bug 667432 [PATCH] Orca doesn't present Categories on the Applications view correctly https://bugzilla.gnome.org/show_bug.cgi?id=670327 Both patches have been reviewed, probably just needs a commit? [PATCH] Orca doesn't present some elements at user menu https://bugzilla.gnome.org/show_bug.cgi?id=671404 [PATCH] Required a way to add accessible states to a generic container https://bugzilla.gnome.org/show_bug.cgi?id=668366 Two patches that need review [PATCH] Notifications need ROLE_NOTIFICATION so that ATs can identify and present them https://bugzilla.gnome.org/show_bug.cgi?id=648645 Simple and tested two-liner patch needs review and commit (dynamic) workspace count stored in dconf https://bugzilla.gnome.org/show_bug.cgi?id=671568 Last open ticket of the "Stuff writing to dconf on first login" collection Gnome 3.0 and 3.2 crashing when disabling wireless https://bugzilla.gnome.org/show_bug.cgi?id=668388 Patch was rejected; no news since then restart by typing ""r"" in the gnome-shell run-dialog 2x in one minute brings up the ""oops"" window https://bugzilla.gnome.org/show_bug.cgi?id=648384 Integration of keyboard indicator with input methods https://bugzilla.gnome.org/show_bug.cgi?id=641531 Patch awaiting review. Quite complex and new strings so maybe postpone to 3.6? =================== GTK+ =================== gnome-panel crashes with multiple screens https://bugzilla.gnome.org/show_bug.cgi?id=662023 Good stacktrace available; Comment 28 has info how to reproduce GtkStyle background color regression https://bugzilla.gnome.org/show_bug.cgi?id=671437 Seen by two people; visible in Evolution. =================== LIBGWEATHER =================== [PATCH] Port to GSettings https://bugzilla.gnome.org/show_bug.cgi?id=646854 =================== MUTTER =================== [PATCH] Access on unreffed pointer https://bugzilla.gnome.org/show_bug.cgi?id=671601 Patch reviewed already, just needs to go in. ====================================== </pre> Andre Klapper 2012-03-09T11:50:36 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2370 <pre> Thanks for you advice, I'll repost on gnome-love! See you, </pre> Fabrice DELENTE 2012-03-08T10:27:26 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2369 <pre>Hello Fabrice :) On 07.03.2012 19:00, Fabrice DELENTE wrote: I have the feeling that gnome-love is more appropriate for your issue. Check out http://live.gnome.org/GnomeLove And I have no idea about your issue, sorry. Cheers, Tobi _______________________________________________ gnome-bugsquad mailing list gnome-bugsquad&lt; at &gt;gnome.org http://mail.gnome.org/mailman/listinfo/gnome-bugsquad </pre> Tobias Mueller 2012-03-08T10:21:04 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2368 <pre>Hello. I don't think it's a bug, I think I just misinstalled it but I didn't find any relevant forum or mailing list, sorry for the noise. I compiled and installed gnome-bluetooth on a slackware 13.37 machine that doesn't use gnome. When I start bluetooth-manager, it keeps searching forever for devices, even though I can see them and connect to them with blueman (but blueman seems unsupported now...), bot as a user or as root. I think there is a misconfiguration somewhere, how can I find it? Does bluetooth-manager rely on modification in policy files? Thanks. </pre> Fabrice DELENTE 2012-03-07T18:00:05 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2367 <pre> This is, in theory, a useful thing. If the bug affects the docs, give it the keyword and don't close it until the docs are updated. I think I've also proposed in the past just not closing bugs and instead moving them to the docs component, as well as some sort of special "NEEDSDOC" status/resolution. The problem with any of these mechanisms is that, unless developers use them religiously, we still have to chase down changes, so the partial list we get from bugzilla isn't that much help. -- Shaun </pre> Shaun McCance 2012-02-10T21:31:44 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2366 <pre> Makes sense. I've fixed the defaults of the affected Bugzilla products and for all open tickets (which was exactly one). The problem is how to identify them... Might need quite some manual reviewing when I'm bored at the Docs Hackfest. :P The keyword description says "This bug (or something in it) needs documenting." Querying for reports that got the "documentation" keyword *added*: * in the last 90 days[1]: 2 * in the last 365 days: 5 * in the last 730 days: 16 * in the last 1825 days: 28 =&gt; Usage seems to not be very widespread anyway. Removing the keyword (used by 1816 tickets in total) might be too noisy, but we could update the keyword description and give better instructions (file a ticket in the Docs component for user docs issues, or something similar, no idea about devel-docs though). andre [1] https://bugzilla.gnome.org/buglist.cgi?chfieldto=Now;query_format=advanced;chfield=keywords;chfieldfrom=-90d;chfieldvalue=documentation </pre> Andre Klapper 2012-02-10T21:17:37 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2363 <pre>Ladies and Gentlemen, a quick look at some basic GNOME Bugzilla activity in 2011. Created by using https://bugzilla.gnome.org/page.cgi?id=weekly-bug-summary.html&amp;days=365&amp;products=0&amp;reporters=15&amp;hunters=15&amp;patchers=15&amp;reviewers=15 Overall statistics: 2011 2010 2009 Open reports at the end(*): 44003 42828 40527 Opened in that year: 28287 32232 39403 Closed in that year: 27552 30534 40280 (*): Excludes reports marked as enhancements The following people closed more than 600 bugs in 2011: 3098 Akhil Laddha 1473 Fabio Durán Verdugo 1084 Matthias Clasen 920 Bastien Nocera 820 André Klapper 792 Cosimo Cecchi 781 Milan Crha The following people reported more than 200 bugs in 2011: 292 William Jon McCann 291 Matthias Clasen 291 Guillaume Desmottes 287 Cosimo Cecchi 278 Akhil Laddha 248 Bastien Nocera 219 Vincent Untz 210 Pedro Villavicencio 200 Joanmarie Diggs The following people contributed more than 200 patches in 2011: 449 Guillaume Desmottes 401 Jasper St. Pierre 389 Milan Crha 370 Matthias Clasen 333 Dan Winship 321 Florian Müllner 316 Vincent Penquerc'h 300 Colin Walters 250 Cosimo Cecchi 212 Giovanni Campagna The following people reviewed more than 250 patches in 2011: 686 Dan Winship 662 Owen Taylor 611 Sebastian Dröge 587 Colin Walters 579 Matthias Clasen 420 Bastien Nocera 392 Guillaume Desmottes 383 Florian Müllner 319 Jasper St. Pierre Enjoy 2012!, andre </pre> Andre Klapper 2012-01-02T12:06:39 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2362 <pre> That line should have been: Note that this de-facto blocks ANY automatic reports by bug-buddy andre </pre> Andre Klapper 2011-12-13T11:06:28 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2361 <pre>As GNOME 3.2.2 was released on November 17th I have bumped the minimally required GNOME version for bug reports submitted to GNOME Bugzilla via bug-buddy from 2.32.0 to 3.0.0. Note that de facto blocks ANY automatic reports bug bug-buddy, as a version 3 of bug-buddy does not exist as most distros have downstream reporting tools nowadays. Reports filed in the last 60 days including the string "BugBuddy Version: 2": 103 https://bugzilla.gnome.org/buglist.cgi?chfieldto=Now;query_format=advanced;chfield=[Bug%20creation];chfieldfrom=-60d;longdesc=BugBuddy%20Version%3A%202;longdesc_type=substring Reports filed in the last 60 days including the string "Gnome Release: 2": 103 https://bugzilla.gnome.org/buglist.cgi?chfieldto=Now;query_format=advanced;chfield=[Bug%20creation];chfieldfrom=-60d;longdesc=Gnome%20Release%3A%202;longdesc_type=substring Reports filed in the last 60 days including the string "BugBuddy Version: 3": 0 https://bugzilla.gnome.org/buglist.cgi?chfieldto=Now;query_format=advanced;chfield=[Bug%20creation];chfieldfrom=-60d;longdesc=BugBuddy%20Version%3A%202;longdesc_type=substring andre </pre> Andre Klapper 2011-12-13T11:03:25 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2360 <pre>[Please edit the recipients list if your answer is specific to your mailing list to avoid unneeded cross-posting.] The second and last bunch of Google Code-In tasks will be published on December 16th. Afterwards no tasks can be added anymore, so if you have an idea take a look at https://live.gnome.org/GoogleCodeIn and add it NOW! For basic info about Google Code-In see my previous announcement email: https://mail.gnome.org/archives/desktop-devel-list/2011-October/msg00175.html http://blogs.gnome.org/aklapper/2011/12/09/google-code-in-2011-second-and-last-round-coming/ lists some of the achievements of the last weeks. Thanks, andre </pre> Andre Klapper 2011-12-09T13:30:15 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2359 <pre>I've answered this already on IRC, still pasting it here for the records. Note that for those that I did not comment on I totally agree. On Wed, 2011-11-30 at 03:27 +0000, kbenjamin Coplon wrote: can you elaborate? did you retest it? yes, perfect. please go ahead and close it, mentioning that comment 4 in the other report, and asking the reporter to leave a comment if it's still an issue in a recent version of brasero I'd add a comment explaining that we **assume** as per comment 2 that it's an ubuntu-specific issue. so NOTGNOME is fine, but also ask if it's still an issue in recent versions, just to be sure. if you tested that this still doesn't exist in 3.2, all your proposed changes sound good. I'd keep "OS = Linux" though, it's not really important here. I'd also reset the old Target Milestone to --- Looks good! Thanks! andre </pre> Andre Klapper 2011-11-30T17:10:07 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2358 <pre>https://bugzilla.gnome.org/show_bug.cgi?id=505995 obsolete https://bugzilla.gnome.org/show_bug.cgi?id=514106 fixed_in_stable (see it's duplicate https://bugzilla.gnome.org/show_bug.cgi?id=554071#c4) https://bugzilla.gnome.org/show_bug.cgi?id=578180 not_gnome (looks like a Ubuntu patch also version 2.26.0) https://bugzilla.gnome.org/show_bug.cgi?id=348316 "new" version 3.2x GNOME version "unversioned enhancement" os "all" importance "normal ,enhancement" https://bugzilla.gnome.org/show_bug.cgi?id=389476 "new" https://bugzilla.gnome.org/show_bug.cgi?id=438850 "new" UE version unspecified os all https://bugzilla.gnome.org/show_bug.cgi?id=584893 "new" version unspecified https://bugzilla.gnome.org/show_bug.cgi?id=438852 "new" os all milestone na GNOME ver UE what do you think so far? </pre> kbenjamin Coplon 2011-11-30T03:27:05 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2357 <pre> Hi, I've handed out permissions to you (and added you to my bugmail watchlist). Please make sure that you have read the triage guide. In short: 1) Use common sense. 2) If unsure, ask first before changing some fields. https://bugzilla.gnome.org/browse.cgi?product=brasero might be a good place to start. In case that you are unsure please just add a comment to the bug report, but do not change any fields - or ask in the #bugs IRC channel on irc.gimp.org (and be patient as not everybody is always in front of a computer). Your primary contacts are kittykat and andre. Enjoy!, andre </pre> Andre Klapper 2011-11-29T21:02:11 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2356 <pre>i ask because of http://www.google-melange.com/gci/task/view/google/gci2011/7137205 thanks </pre> kbenjamin Coplon 2011-11-29T20:50:45 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2355 <pre>Thank you, thats a lot of valuable information to think about and understand. E.g., I completely missed the Bugmaster's role, somehow implicitly confused that with a developer role. Two quick clarifications/answers below. &gt; For me, yes! Though thorough analysis needs to be done. Sometimes the &gt; data might indicate one thing, while practically something else happens. Exactly, to add to your point, our goals are roughly threefold: At the technical level, the hope is to simplify some queries that are not so easily generated via Bugzilla reports: time trends, intervals between states, particular trajectories (e.g., *-resolved-unconfirmed-resolved-*). From the more practical perspective, to come up with summary measures that accurately reflect concerns of various teams (maintainer, bugsquad, user). From a theoretical perspective to learn from (and, hopefully, to help with) the distributed decision making process that takes place in this large and complex organization with a variety of roles/stakeholders. &gt; Ideally it should be built into Pe2. How does Pe2 gather its data btw? Depends on the project. For the prototype and historic analysis scraping Bugzilla/Jira/Trac seems sufficient, for a live look at the current state of the project thats not going to work, would need some update subscription mechanism. For GNOME it is based on the existing extracts: http://academic.patrick.wagstrom.net/research/gnome http://msr.uwaterloo.ca/msr2009/challenge/msrchallengedata.html http://passion-lab.org/download Also:http://mail.gnome.org/archives/academia-list/2010-October/thread.html#00002 Audris On 11/21/2011 05:08 AM, Olav Vitters wrote: Missed </pre> Audris Mockus 2011-11-21T15:51:42 http://permalink.gmane.org/gmane.comp.gnome.bugsquad/2354 <pre>First impressions. On Sun, Nov 20, 2011 at 06:37:46PM -0500, Audris Mockus wrote: Seems quite interesting. However, due note that there are multiple teams involved with Bugzilla: 1) bugmasters very small group of administrators 2) bugsquad loosely connected group of people who triage bugs 3) maintainers/developers 4) users The entire triage process is decided by bugsquad themselves. I've cc'ed gnome-bugsquad as I think they'll be interested in this email as well. That is a public mailing list btw. I will need to look into that a bit more, need more time for that. For me, yes! Though thorough analysis needs to be done. Sometimes the data might indicate one thing, while practically something else happens. Ideally it should be built into Pe2. How does Pe2 gather its data btw? I'd like to see: - how often are bugs closed as incomplete - buggyness of GNOME in general over time - pareto chart of top crashing products - all duplicate crashers should be detected automatically - crashers should not be filed at bugzilla, instead they should be on some separate server which only task is to handle the crashers - separate server should forward to bugzilla - pareto chart of products where no action seems to be taken (indicating need to ask maintainer, or lack of maintainer) - anything that indicates sudden trend break, be it positive or negative e.g.: suddenly there are way more bugs fixed for a product than usual, or opposite There are some problems with bug-buddy: - the retrace server is broken, so the change of version 2.19 is broken - we should let the retracing be done by the distribution There are plans to change the crash handling significantly. See: https://live.gnome.org/Design/Apps/Oops https://live.gnome.org/GnomeOS/Design/Whiteboards/ProblemReporting The designers+maintainers want to provide a well integrated problem reporting infrastructure. GNOME is becoming more and more integrated with the OS. OS problems affect the perception people have of GNOME. E.g. if suspend doesn't work, GNOME will be seen as bad. We (GNOME) should work to ensure such lower level problems can be detected, reported and fixed. This relies on two things: - bugsquad to triage the bugs and - maintainers to fix the bug Would also be nice to see it in a control chart. Though think the data is not stable. E.g. new GNOME means new crashers (I assume). Same for when a new distribution is released. Ideally I'd like to see the number of crashers per amount of hours spend in the software. But that is impossible to gather at the moment. See for instance: https://crash-stats.mozilla.com/products/Firefox That has crashers per 100 users, also quite interesting. </pre> Olav Vitters 2011-11-21T10:08:05 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.gnome.bugsquad