Bug 666137 - [abrt] grsync-1.1.1-1.fc13: g_key_file_is_group_name: Process /usr/bin/grsync was killed by signal 11 (SIGSEGV)
Summary: [abrt] grsync-1.1.1-1.fc13: g_key_file_is_group_name: Process /usr/bin/grsync...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: grsync
Version: 13
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5aaacec63ca8af6f11fabc9be05...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-29 06:17 UTC by nomnex
Modified: 2011-06-27 12:50 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 12:50:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (13.94 KB, text/plain)
2010-12-29 06:17 UTC, nomnex
no flags Details

Description nomnex 2010-12-29 06:17:48 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/grsync -i
comment: Lost everything: .grsync profiles are gone?!? only grsync.ini file left in the hidden dir .grsync in /home. Nice! Thank you LXDE...
component: grsync
crash_function: g_key_file_is_group_name
executable: /usr/bin/grsync
kernel: 2.6.34.7-66.fc13.i686
package: grsync-1.1.1-1.fc13
rating: 4
reason: Process /usr/bin/grsync was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1293603148
uid: 500

How to reproduce
-----
1. Open grsync
2. selected a source dir and a dest dir
3. crashed

Comment 1 nomnex 2010-12-29 06:17:51 UTC
Created attachment 471033 [details]
File: backtrace

Comment 2 nomnex 2010-12-29 06:54:57 UTC
Package: grsync-1.1.1-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. I suffere a previous Grsync crash on LXDE
2. I have de-install/re-install grsync because of an error msg : The session you specified on the command line doesn't exists
3. still not working

Comment 3 nomnex 2010-12-29 08:05:59 UTC
Package: grsync-1.1.1-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. I suffere a previous Grsync crash on LXDE
2. I have de-install/re-install grsync because of an error msg : The session you specified on the command line doesn't exists
3. still not working

Comment 4 Bug Zapper 2011-05-30 12:21:31 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 5 Bug Zapper 2011-06-27 12:50:08 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.