Bug 864228

Summary: [abrt] teamgit-0.0.10-1.20120202.fc17: qMemEquals: Process /usr/bin/teamgit was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Alexander Osipenko <sipych>
Component: teamgitAssignee: Terje Røsten <terje.rosten>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: terje.rosten
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c0805951d6c73a494cc83a09f96a2727ea7f3105
Fixed In Version: teamgit-0.0.12-1.20130626.fc18 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-16 01:32:40 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: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: maps
none
File: dso_list
none
File: open_fds
none
File: var_log_messages none

Description Alexander Osipenko 2012-10-08 22:41:18 UTC 
Description of problem:
Try to start application

Version-Release number of selected component:
teamgit-0.0.10-1.20120202.fc17

Additional info:
libreport version: 2.0.14
abrt_version:   2.0.13
backtrace_rating: 4
cmdline:        teamgit
crash_function: qMemEquals
kernel:         3.5.5-2.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 qMemEquals at tools/qstring.cpp:315
: #2 MainWindowImpl::gotCommands at src/mainwindowimpl.cpp:210
: #3 MainWindowImpl::qt_static_metacall at build/moc_mainwindowimpl.cpp:235
: #4 QObject::event at kernel/qobject.cpp:1195
: #5 QWidget::event at kernel/qwidget.cpp:8830
: #6 QMainWindow::event at widgets/qmainwindow.cpp:1478
: #7 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:4551
: #8 QApplication::notify at kernel/qapplication.cpp:4412
: #9 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:915
: #10 sendEvent at kernel/qcoreapplication.h:231
Comment 1 Alexander Osipenko 2012-10-08 22:41:21 UTC 
Created attachment 623790 [details]
File: core_backtrace
Comment 2 Alexander Osipenko 2012-10-08 22:41:23 UTC 
Created attachment 623791 [details]
File: environ
Comment 3 Alexander Osipenko 2012-10-08 22:41:29 UTC 
Created attachment 623792 [details]
File: backtrace
Comment 4 Alexander Osipenko 2012-10-08 22:41:31 UTC 
Created attachment 623793 [details]
File: limits
Comment 5 Alexander Osipenko 2012-10-08 22:41:33 UTC 
Created attachment 623794 [details]
File: cgroup
Comment 6 Alexander Osipenko 2012-10-08 22:41:37 UTC 
Created attachment 623795 [details]
File: maps
Comment 7 Alexander Osipenko 2012-10-08 22:41:40 UTC 
Created attachment 623796 [details]
File: dso_list
Comment 8 Alexander Osipenko 2012-10-08 22:41:42 UTC 
Created attachment 623797 [details]
File: open_fds
Comment 9 Alexander Osipenko 2012-10-08 22:41:45 UTC 
Created attachment 623798 [details]
File: var_log_messages
Comment 10 Fedora End Of Life 2013-07-04 03:41:38 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.
Comment 11 Fedora Update System 2013-07-06 08:25:53 UTC 
teamgit-0.0.12-1.20130626.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/teamgit-0.0.12-1.20130626.fc18
Comment 12 Fedora Update System 2013-07-06 08:26:19 UTC 
teamgit-0.0.12-1.20130626.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/teamgit-0.0.12-1.20130626.fc19
Comment 13 Fedora Update System 2013-07-06 08:26:41 UTC 
teamgit-0.0.12-1.20130626.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/teamgit-0.0.12-1.20130626.fc17
Comment 14 Fedora Update System 2013-07-07 01:29:34 UTC 
Package teamgit-0.0.12-1.20130626.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing teamgit-0.0.12-1.20130626.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-12467/teamgit-0.0.12-1.20130626.fc18
then log in and leave karma (feedback).
Comment 15 Fedora Update System 2013-07-16 01:32:40 UTC 
teamgit-0.0.12-1.20130626.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 16 Fedora Update System 2013-07-16 01:34:49 UTC 
teamgit-0.0.12-1.20130626.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 17 Fedora Update System 2013-07-16 01:51:15 UTC 
teamgit-0.0.12-1.20130626.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.