patch from CVS to fix crash triggered when closing ekiga by example

Bug #76301 reported by Sebastien Bacher
22
Affects Status Importance Assigned to Milestone
gnome-vfs2 (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs
Edgy
Fix Released
Medium
Sebastien Bacher

Bug Description

Upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=359655

Ekiga crashes sometime when closed. The bug has around 300 duplicates for now and upstream would be glad if we can backport the patch to edgy (they send several mails about that already). The patch is part of the feisty gnome-vfs version and an user stated upstream that it fixes the bug for him (that's a race condition and is not easy to trigger to make sure that's the case)

Upstream commit for that bug:
http://cvs.gnome.org/viewcvs/gnome-vfs/libgnomevfs/gnome-vfs-module-callback.c?r1=1.10&r2=1.11

Comment for the commit:

"2006-11-07 Alexander Larsson <email address hidden>

 * libgnomevfs/gnome-vfs-module-callback.c (stack_table_destroy):
 Protect against reordering of atexit handlers and thread exit
 handlers. Don't know if this is possible, but could be the cause
 of bug #359655."

Revision history for this message
Sebastien Bacher (seb128) wrote :

That has been fixed to feisty already

Changed in gnome-vfs2:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

changelog:

 gnome-vfs2 (2.16.1-0ubuntu6) edgy-proposed; urgency=low
 .
   * debian/patches/91_from_cvs_protect_against_handlers_reordering.patch:
     - patch from CVS, "Protect against reordering of atexit handlers and
       thread exit handlers", can be triggered when closing ekiga by example
       (Ubuntu: #76301)

Revision history for this message
Sebastien Bacher (seb128) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in gnome-vfs2:
assignee: nobody → seb128
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

http://librarian.launchpad.net/5444040/gnomevfs.debdiff approved for upload to edgy-proposed.

Revision history for this message
Sebastien Bacher (seb128) wrote :

uploaded to edgy-proposed

Revision history for this message
Sebastien Bacher (seb128) wrote :

the upstream bug has over 400 duplicates and upstream is pretty unhappy about Ubuntu because of it, could anybody approve that edgy-proposed upload?

Revision history for this message
Matt Zimmerman (mdz) wrote :

The minimum aging period has elapsed; the package can be migrated to edgy-updates once testing has been completed per StableReleaseUpdates.

Why is upstream unhappy with Ubuntu? This bug does not seem Ubuntu-specific.

Revision history for this message
Yannick Defais (sevmek) wrote :

Hello Matt Zimmerman,

Maybe because Ubuntu is mainstream...

Really, can't you do something to at least reduce the amount of reports? It is just growing and growing right now.

Regards,
Yannick

Revision history for this message
Matt Zimmerman (mdz) wrote : Re: [Bug 76301] Re: patch from CVS to fix crash triggered when closing ekiga by example

On Sun, Jan 07, 2007 at 02:25:11AM -0000, Yannick Defais wrote:
> Hello Matt Zimmerman,
>
> Maybe because Ubuntu is mainstream...
>
> Really, can't you do something to at least reduce the amount of reports?
> It is just growing and growing right now.

I don't know of anything we can do to control how many people report this
bug to GNOME, no.

What we can do is prepare, test and release a fix for Ubuntu, which is what
we are doing.

What we cannot do is release an untested fix.

The fix is in edgy-proposed and thereby publicly available for testing.
Confirmation of both the fix and of a lack of functional regressions is
welcome here.

--
 - mdz

Revision history for this message
Jan Schampera (jan-schampera) wrote :

> I don't know of anything we can do to control how many people report this
> bug to GNOME, no.
Unfortunately nothing, of course.

> What we can do is prepare, test and release a fix for Ubuntu, which is what
> we are doing.
In the weeks after the fix was done, it didn't look like Ubuntu would use it. Nearly all the bugreports came from Edgy users (I estimate about 95%). That's why we shaked our heads after a while.
As of now, the flood time seems to be over, I only get 2-3 DUPs per day for it.
Of course it isn't/wasn't an Ubuntu bug, but Edgy seems to be the only distribution that either
- used that buggy GNOME-VFS implementation or reported
OR
- reported bugs at all

Hence the confusion on our side about the progress here.

I hope that explains our point of view, at least a little bit.

Regards,
Jan

Revision history for this message
Sebastien Bacher (seb128) wrote :

Matt, "The minimum aging period has elapsed", that would be true if somebody accepted the upload to edgy-proposed which is apparently not the case, the upload is waiting on moderation for weeks now.

The bug is not Ubuntu specific, the version shipped with edgy has that bug though, we didn't update to the new gnomevfs version, Ubuntu has many users and bug-buddy which is used by default make easy for bugzilla to get flooded, the combinaisons of those facts makes that most of dups come from edgy.

The frustration comes from the fact that the proposed update is still waiting for moderation after some weeks and they keep getting duplicates for that problem meanwhile

Revision history for this message
Tollef Fog Heen (tfheen) wrote :

Accepted into edgy-proposed

Changed in gnome-vfs2:
status: Confirmed → Fix Committed
Revision history for this message
Simon Law (sfllaw) wrote :

Regression tested and it looks fine. Please upload to edgy-updates immediately.

Thanks.

Revision history for this message
Sebastien Bacher (seb128) wrote :

update uploaded now

Revision history for this message
Martin Pitt (pitti) wrote :

Upload accepted into edgy-updates.

Changed in gnome-vfs2:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.