Bug 584455

Summary: [abrt] crash in thunar-vcs-plugin-0.1.2-2.fc12: Process /usr/libexec/tvp-svn-helper was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: 0g6m3wgpuuautai
Component: thunar-vcs-pluginAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: christoph.wickert, kevin, projects.rg, sacntct
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:081d7f5d6635cadc7d704bdba32b39ac1da55344
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-28 00:25:35 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
File: backtrace none

Description 0g6m3wgpuuautai 2010-04-21 15:33:49 UTC
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/tvp-svn-helper --log /home/bdhameli/workspace2/SIPRe
component: thunar-vcs-plugin
executable: /usr/libexec/tvp-svn-helper
kernel: 2.6.32.11-99.fc12.i686
package: thunar-vcs-plugin-0.1.2-2.fc12
rating: 4
reason: Process /usr/libexec/tvp-svn-helper was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

comment
-----
1. Use SubVersion Thunar Plug-in
2. Checkout new working copy
3. Right on directory -> SVN -> Log
4. Click on the first entry (and the only one for me) of revision list

How to reproduce
-----
1. Use SubVersion Thunar Plug-in
2. Checkout new working copy
3. Right on directory -> SVN -> Log
4. Click on the first entry (and the only one for me) of revision list

Comment 1 0g6m3wgpuuautai 2010-04-21 15:33:52 UTC
Created attachment 408112 [details]
File: backtrace

Comment 2 Christoph Wickert 2010-04-21 16:05:17 UTC
Thanks for your report. I have forwarded it upstream as
http://bugzilla.xfce.org/show_bug.cgi?id=6404

Comment 3 Raphael Groner 2010-05-13 13:04:18 UTC
(In reply to comment #1)
I had a quick look into the rpm source package. For me, it seems like to be an issue of the memory manager in GTK due to g_new_object fails.

I use gtk+2.20.

Comment 4 Christoph Wickert 2010-08-01 11:32:56 UTC
(In reply to comment #0)
> 3. Right on directory -> SVN -> Log
> 4. Click on the first entry (and the only one for me) of revision list

Can you give me the output of "svn log -v" for this entry please?

Comment 5 Bug Zapper 2010-11-03 16:38:24 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Christoph Wickert 2010-11-28 00:25:35 UTC
Further investigation will take place in the Xfce bug tracker, closing UPSTREAM.

Comment 7 Christoph Wickert 2011-07-16 12:51:35 UTC
*** Bug 722679 has been marked as a duplicate of this bug. ***