Bug 456816

Summary: kazehakase segfauls with kazehakase-ruby on ruby side
Product: [Fedora] Fedora Reporter: Mamoru TASAKA <mtasaka>
Component: ruby-gnome2Assignee: Allisson Azevedo <allisson>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: tagoh
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 0.17.0-3.fc10 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-18 04:13:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
gdb log when segv happens none

Description Mamoru TASAKA 2008-07-27 17:37:58 UTC
Description of problem:
kazehakase (maintained by me) causes segv on start with kazehakase-ruby
also installed.
gdb shows that segv is happening on ruby side.

Version-Release number of selected component (if applicable):
ruby-1.8.6.230-5.fc10.i386
kazehakase-ruby-0.5.4-7.svn3506_trunk.fc10.i386
libcanberra-gtk2-0.4-1.fc10.i386

How reproducible:
100%

Steps to Reproduce:
1. install kazehakase, kazehakase-ruby
2. type "$ kazehakase"
3.
  
Actual results:
kazehakase segfaults

Additional info:
Strangely enough, when I download libcanberra-gtk2 to 0.3-2.fc10, segfault
never happens...

Comment 1 Mamoru TASAKA 2008-07-27 17:37:59 UTC
Created attachment 312736 [details]
gdb log when segv happens

Comment 2 Akira TAGOH 2008-07-28 12:15:16 UTC
That looks like a GC bug or related to GC in anywhere, including the extension
if kazehakase-ruby has anything.

Comment 3 Mamoru TASAKA 2008-08-23 14:17:17 UTC
Once closing as I don't see this issue with ruby-1.8.6.287-1.fc10.
If the issue occurs again, I will reopen this bug or resubmit another one.

Thank you.

Comment 4 Mamoru TASAKA 2008-09-09 06:18:05 UTC
Sorry, however if I remove ~/.kazehakase this bug can always be reproduced
with 1.8.6.287-1.fc10. gdb backtrace is still the same as my comment 1.

Reopening...

Comment 5 Mamoru TASAKA 2008-09-18 02:19:50 UTC
Kazehakase upstream and also ruby-gnome2 upstream confirmed that this is
a bug in Ruby/Glib.
http://ruby-gnome2.svn.sourceforge.net/viewvc/ruby-gnome2/ruby-gnome2/trunk/glib/ChangeLog?r1=3303&r2=3312

Reassigning to ruby-gnome2.

Comment 6 Mamoru TASAKA 2008-09-18 04:13:56 UTC
Fixed in ruby-gnome2-0.17.0-3.fc10.

To Allisson:
Would you sync F-8/9 branches to devel?

Comment 7 Allisson Azevedo 2008-09-18 11:13:46 UTC
Hi Mamoru,

I think it's a good ideia, you can sync the branches?

Comment 8 Mamoru TASAKA 2008-09-18 11:43:51 UTC
(In reply to comment #7)
> Hi Mamoru,
> 
> I think it's a good ideia, you can sync the branches?

Okay, then I will do later.

Comment 9 Fedora Update System 2008-09-18 14:09:49 UTC
ruby-gnome2-0.17.0-1.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/ruby-gnome2-0.17.0-1.fc9

Comment 10 Fedora Update System 2008-09-18 14:12:19 UTC
ruby-gnome2-0.17.0-1..fc8 has been submitted as an update for Fedora 8.
http://admin.fedoraproject.org/updates/ruby-gnome2-0.17.0-1..fc8

Comment 11 Fedora Update System 2008-09-25 00:04:49 UTC
ruby-gnome2-0.17.0-1.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2008-09-25 00:22:21 UTC
ruby-gnome2-0.17.0-1.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.