Menu
▾
▴
gtk2-perl-bugs — Bug reports and mail from bugzilla
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(3) |
Aug
(3) |
Sep
|
Oct
(1) |
Nov
(5) |
Dec
(6) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
(12) |
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
(15) |
Nov
(8) |
Dec
(4) |
| 2006 |
Jan
|
Feb
|
Mar
(11) |
Apr
(10) |
May
(105) |
Jun
(12) |
Jul
(42) |
Aug
(54) |
Sep
(15) |
Oct
(14) |
Nov
(27) |
Dec
(3) |
| 2007 |
Jan
(1) |
Feb
(6) |
Mar
(26) |
Apr
(11) |
May
(28) |
Jun
(5) |
Jul
(9) |
Aug
|
Sep
|
Oct
(4) |
Nov
(8) |
Dec
(7) |
| 2008 |
Jan
(4) |
Feb
(1) |
Mar
|
Apr
|
May
(6) |
Jun
(7) |
Jul
|
Aug
(16) |
Sep
(1) |
Oct
(4) |
Nov
(3) |
Dec
(1) |
| 2009 |
Jan
(37) |
Feb
(19) |
Mar
(32) |
Apr
(7) |
May
(2) |
Jun
(15) |
Jul
(8) |
Aug
(12) |
Sep
(2) |
Oct
(1) |
Nov
(6) |
Dec
(11) |
| 2010 |
Jan
(11) |
Feb
(5) |
Mar
(56) |
Apr
(75) |
May
(28) |
Jun
(10) |
Jul
(6) |
Aug
(1) |
Sep
(26) |
Oct
(23) |
Nov
(92) |
Dec
(41) |
| 2011 |
Jan
(6) |
Feb
(2) |
Mar
(2) |
Apr
(8) |
May
(20) |
Jun
(3) |
Jul
(1) |
Aug
(32) |
Sep
(6) |
Oct
(9) |
Nov
(3) |
Dec
(15) |
| 2012 |
Jan
(6) |
Feb
(13) |
Mar
|
Apr
(1) |
May
|
Jun
(2) |
Jul
(4) |
Aug
(7) |
Sep
|
Oct
(2) |
Nov
|
Dec
(4) |
| 2013 |
Jan
(9) |
Feb
(15) |
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
(9) |
Aug
|
Sep
(5) |
Oct
(4) |
Nov
(4) |
Dec
(11) |
| 2014 |
Jan
|
Feb
(3) |
Mar
(8) |
Apr
|
May
(4) |
Jun
(2) |
Jul
(2) |
Aug
(9) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
(2) |
Apr
(3) |
May
(7) |
Jun
(3) |
Jul
(5) |
Aug
(15) |
Sep
|
Oct
(1) |
Nov
|
Dec
(6) |
| 2016 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(6) |
Oct
(6) |
Nov
(7) |
Dec
(8) |
| 2017 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(8) |
| 2018 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
(10) |
Jun
|
Jul
|
Aug
(5) |
Sep
(4) |
Oct
(3) |
Nov
(3) |
Dec
(4) |
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(40) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-30 15:28:10
|
https://bugzilla.gnome.org/show_bug.cgi?id=620099 gnome-perl | Glib | unspecified Torsten Schoenfeld <kaffeetisch> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |614650 -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-30 15:24:49
|
https://bugzilla.gnome.org/show_bug.cgi?id=614650 gnome-perl | general | unspecified Torsten Schoenfeld <kaffeetisch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Ever Confirmed|0 |1 --- Comment #6 from Torsten Schoenfeld <kaf...@gm...> 2010-05-30 15:24:34 UTC --- OK, this turned out to be way more intricate than expected. Basically, the problem is, as I'm sure you know already, that the about_to_finish signal handler is called from a new thread. And we're not prepared to handle this. See bug 620099 for my current stab at this. If you want to test this, make sure you pass the callback reference by name, like this: $player->signal_connect(about_to_finish => "main::about_to_finish", $file2); Passing code references (i.e., \&about_to_finish) between threads is not supported (by us, but also by perl). -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-30 15:18:34
|
https://bugzilla.gnome.org/show_bug.cgi?id=620099 gnome-perl | Glib | unspecified --- Comment #5 from Torsten Schoenfeld <kaf...@gm...> 2010-05-30 15:18:21 UTC --- Created an attachment (id=162322) View: https://bugzilla.gnome.org/attachment.cgi?id=162322 Review: https://bugzilla.gnome.org/review?bug=620099&attachment=162322 Make the GObject ↔ SV association thread-safe Instead of associating to every GObject just one SV, use a hash table of perl interpreter → SV pairs so that we can store and hand out a thread-specific SV wrapper. Previously, when running in a new thread, we would still hand out the SV wrapper that was created in the main thread and which thus belongs to the main thread's interpreter. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-30 15:18:18
|
https://bugzilla.gnome.org/show_bug.cgi?id=620099 gnome-perl | Glib | unspecified --- Comment #4 from Torsten Schoenfeld <kaf...@gm...> 2010-05-30 15:18:06 UTC --- Created an attachment (id=162321) View: https://bugzilla.gnome.org/attachment.cgi?id=162321 Review: https://bugzilla.gnome.org/review?bug=620099&attachment=162321 Free interpreter clones when their threads exit -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-30 15:17:46
|
https://bugzilla.gnome.org/show_bug.cgi?id=620099 gnome-perl | Glib | unspecified --- Comment #3 from Torsten Schoenfeld <kaf...@gm...> 2010-05-30 15:17:36 UTC --- Created an attachment (id=162320) View: https://bugzilla.gnome.org/attachment.cgi?id=162320 Review: https://bugzilla.gnome.org/review?bug=620099&attachment=162320 Turn the macro GPERL_ENSURE_CONTEXT into a function Turn the macro GPERL_ENSURE_CONTEXT into the function gperl_ensure_context, and make it accept NULL as an argument to indicate that the master interpreter should be used. This allows us to make the _gperl_set_master_interp and _gperl_get_master_interp static. Also, make the thread-safety code conditional on !GPERL_DISABLE_THREADSAFE. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-30 15:17:38
|
https://bugzilla.gnome.org/show_bug.cgi?id=620099 gnome-perl | Glib | unspecified --- Comment #2 from Torsten Schoenfeld <kaf...@gm...> 2010-05-30 15:17:24 UTC --- Created an attachment (id=162318) View: https://bugzilla.gnome.org/attachment.cgi?id=162318 Review: https://bugzilla.gnome.org/review?bug=620099&attachment=162318 Clone the master perl interpreter if called from another thread Rename GPERL_SET_CONTEXT to GPERL_ENSURE_CONTEXT and make it clone the master interpreter if we find that the current thread doesn't have an interpreter associated with it. Previously, we would just install the master interpreter itself. And according to L<perlguts/"Should I do anything special if I call perl from multiple threads?">, this should be all there is to it. But apparently, this is not safe if we actually call into the interpreter concurrently. The discussion at <http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2005-12/msg00452.html> suggests that we need to create a clone. And when a thread already has an interpreter installed, don't replace it. We cannot use one thread's interpreter in another thread. To make this have an effect on closure invocation, change GPERL_CLOSURE_MARSHAL_INIT to use GPERL_ENSURE_CONTEXT instead of PERL_SET_CONTEXT. Also, add a few debug prints to the CLONE machinery in Glib::Object. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-30 15:17:13
|
https://bugzilla.gnome.org/show_bug.cgi?id=620099 gnome-perl | Glib | unspecified --- Comment #1 from Torsten Schoenfeld <kaf...@gm...> 2010-05-30 15:17:03 UTC --- Created an attachment (id=162317) View: https://bugzilla.gnome.org/attachment.cgi?id=162317 Review: https://bugzilla.gnome.org/review?bug=620099&attachment=162317 Fix a threading bug in dGPERL_CLOSURE_MARSHAL_ARGS Previously, dGPERL_CLOSURE_MARSHAL_ARGS used the dSP macro to declare the stack pointer. But dSP involves accessing the my_perl pointer which might be invalid if we've been called from a thread other than the main one. To avoid this, manually declare SV **sp first and let GPERL_CLOSURE_MARSHAL_INIT initialize it after it has set up my_perl via PERL_SET_CONTEXT. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-30 15:11:25
|
https://bugzilla.gnome.org/show_bug.cgi?id=620099 gnome-perl | Glib | unspecified Summary: Make it safe to call into Glib from foreign threads Classification: Bindings Product: gnome-perl Version: unspecified OS/Version: Linux Status: NEW Severity: normal Priority: Normal Component: Glib AssignedTo: gtk...@li... ReportedBy: kaf...@gm... QAContact: gtk...@li... GNOME target: --- GNOME version: --- Currently, when a foreign thread calls into Glib (e.g., invoking a signal handler or a callback), we use PERL_SET_CONTEXT to install a pointer to the main thread's perl interpreter into the current thread's local storage. A few bug reports and some experimentation suggest that this is not safe: one cannot use a single perl interpreter from multiple threads concurrently. I'll attach a set of patches that work towards fixing this by creating a clone of the master interpreter whenever we are called from a new foreign thread. In my limited testing, they seem to work fine. But they are not finished yet. For example, one of the changes is pthread-specific, and that might be problematic. But more importantly, I'm not convinced yet that we really want to take this approach, because creating clones is really expensive. Opinions appreciated. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-20 21:12:31
|
https://bugzilla.gnome.org/show_bug.cgi?id=619233 gnome-perl | Gtk2 | unspecified --- Comment #3 from Torsten Schoenfeld <kaf...@gm...> 2010-05-20 21:12:19 UTC --- Created an attachment (id=161593) --> (https://bugzilla.gnome.org/attachment.cgi?id=161593) Example III -- unfinished port of GtkHWrapBox -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-20 21:11:50
|
https://bugzilla.gnome.org/show_bug.cgi?id=619233 gnome-perl | Gtk2 | unspecified --- Comment #2 from Torsten Schoenfeld <kaf...@gm...> 2010-05-20 21:11:39 UTC --- Created an attachment (id=161592) --> (https://bugzilla.gnome.org/attachment.cgi?id=161592) Example II -- fairly boring -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-20 21:11:12
|
https://bugzilla.gnome.org/show_bug.cgi?id=619233 gnome-perl | Gtk2 | unspecified --- Comment #1 from Torsten Schoenfeld <kaf...@gm...> 2010-05-20 21:11:03 UTC --- Created an attachment (id=161591) --> (https://bugzilla.gnome.org/attachment.cgi?id=161591) Example I -- this one also relies on child properties -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-20 21:09:47
|
https://bugzilla.gnome.org/show_bug.cgi?id=619233 gnome-perl | Gtk2 | unspecified Summary: Make Gtk2::Container subclassable Classification: Bindings Product: gnome-perl Version: unspecified OS/Version: Linux Status: NEW Severity: enhancement Priority: Normal Component: Gtk2 AssignedTo: gtk...@li... ReportedBy: kaf...@gm... QAContact: gtk...@li... GNOME target: --- GNOME version: --- Created an attachment (id=161590) View: https://bugzilla.gnome.org/attachment.cgi?id=161590 Review: https://bugzilla.gnome.org/review?bug=619233&attachment=161590 Make Gtk2::Container subclassable Here's a pretty complete but rough attempt at making Gtk2::Container subclassable. It's been lying on my box for ages, but I haven't gotten around to completing it. It still needs documentation, tests and examples. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-20 19:47:03
|
https://bugzilla.gnome.org/show_bug.cgi?id=617980 gnome-perl | Gnome2::GConf | unspecified Dave Koberstein <davek> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #160479|0 |1 is obsolete| | --- Comment #1 from Dave Koberstein <da...@ko...> 2010-05-20 19:46:53 UTC --- Created an attachment (id=161584) View: https://bugzilla.gnome.org/attachment.cgi?id=161584 Review: https://bugzilla.gnome.org/review?bug=617980&attachment=161584 updated patch Updated patch checks for null before calling gconf_value_free() -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-17 22:15:51
|
https://bugzilla.gnome.org/show_bug.cgi?id=609932 gnome-perl | Gnome2::Rsvg | unspecified Torsten Schoenfeld <kaffeetisch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |kaf...@gm... Resolution| |FIXED --- Comment #3 from Torsten Schoenfeld <kaf...@gm...> 2010-05-17 22:15:42 UTC --- These methods (and a couple more) are now wrapped in the just-released 0.11. Unfortunately, I forgot about your patch and ended up writing nearly the exact same code. :-/ Anyway, thanks for the patch! -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-16 14:27:04
|
https://bugzilla.gnome.org/show_bug.cgi?id=614495 gnome-perl | Cairo | unspecified Torsten Schoenfeld <kaffeetisch> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #157617|none |committed status| | -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-16 14:26:54
|
https://bugzilla.gnome.org/show_bug.cgi?id=614495 gnome-perl | Cairo | unspecified Torsten Schoenfeld <kaffeetisch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #2 from Torsten Schoenfeld <kaf...@gm...> 2010-05-16 14:26:40 UTC --- A comment on the list and some more testing confirmed that you are indeed right, and that the manual is wrong. So committed your patch. Thanks. I also treated set_filter and get_filter similarly, for the same reasons. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-16 12:55:05
|
https://bugzilla.gnome.org/show_bug.cgi?id=615992 gnome-perl | Gtk2 | unspecified Torsten Schoenfeld <kaffeetisch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |NOTABUG --- Comment #2 from Torsten Schoenfeld <kaf...@gm...> 2010-05-16 12:54:52 UTC --- I can't reproduce the issue on my system now. Since the bug report is also very old and we haven't heard back from the reporter, I'm closing this as "not a bug". -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-16 12:40:15
|
https://bugzilla.gnome.org/show_bug.cgi?id=591070 gnome-perl | Glib | unspecified Torsten Schoenfeld <kaffeetisch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #3 from Torsten Schoenfeld <kaf...@gm...> 2010-05-16 12:23:25 UTC --- I've committed this last difference now. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-16 12:31:43
|
https://bugzilla.gnome.org/show_bug.cgi?id=608730 gnome-perl | Gtk2 | unspecified Torsten Schoenfeld <kaffeetisch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED --- Comment #1 from Torsten Schoenfeld <kaf...@gm...> 2010-05-16 12:31:25 UTC --- Looks great, thanks. Committed (after a minor whitespace modification). -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-16 12:31:43
|
https://bugzilla.gnome.org/show_bug.cgi?id=608730 gnome-perl | Gtk2 | unspecified Torsten Schoenfeld <kaffeetisch> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #152768|none |committed status| | -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-16 11:51:53
|
https://bugzilla.gnome.org/show_bug.cgi?id=616894 gnome-perl | Pango | unspecified Torsten Schoenfeld <kaffeetisch> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #159729|none |committed status| | -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-16 11:51:48
|
https://bugzilla.gnome.org/show_bug.cgi?id=616894 gnome-perl | Pango | unspecified Torsten Schoenfeld <kaffeetisch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #5 from Torsten Schoenfeld <kaf...@gm...> 2010-05-16 11:51:34 UTC --- I committed the second patch now. Attachment 159729 pushed as f59a97e - Don't leak Pango::Attribute objects -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-16 11:38:13
|
https://bugzilla.gnome.org/show_bug.cgi?id=613972 gnome-perl | Gtk2 | unspecified Torsten Schoenfeld <kaffeetisch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED --- Comment #6 from Torsten Schoenfeld <kaf...@gm...> 2010-05-16 11:38:01 UTC --- Alright, I committed a slightly modified variant of Kevin's patch. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-10 02:26:48
|
https://bugzilla.gnome.org/show_bug.cgi?id=613972 gnome-perl | Gtk2 | unspecified muppet <scott> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sc...@as... --- Comment #5 from muppet <sc...@as...> 2010-05-10 02:26:36 UTC --- Yes, we should. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
|
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2010-05-07 16:36:09
|
https://bugzilla.gnome.org/show_bug.cgi?id=617980 gnome-perl | Gnome2::GConf | unspecified André Klapper <a9016009> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |memory CC| |a90...@gm... -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
13 messages has been excluded from this view by a project administrator.
