Bug 583783 - [abrt] crash in bzr-2.0.5-1.fc12: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in bzr-2.0.5-1.fc12: Process /usr/bin/python was killed by signa...
Keywords:
Status: CLOSED DUPLICATE of bug 583951
Alias: None
Product: Fedora
Classification: Fedora
Component: qbzr
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Toshio Ernie Kuratomi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9018135e340bfbac684360fddc1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-19 17:49 UTC by greg
Modified: 2010-05-10 05:09 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-05-10 05:09:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (29.22 KB, text/plain)
2010-04-19 17:49 UTC, greg
no flags Details

Description greg 2010-04-19 17:49:45 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/bzr qmerge --ui-mode
component: bzr
executable: /usr/bin/python
kernel: 2.6.32.11-99.fc12.x86_64
package: bzr-2.0.5-1.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 greg 2010-04-19 17:49:48 UTC
Created attachment 407648 [details]
File: backtrace

Comment 2 Toshio Ernie Kuratomi 2010-04-19 19:53:32 UTC
Is this reproducible?  Do I need to set anythings in the UI?  Is the bzr branch this is being done in available publically?  I jsut tried bzr qmerge --ui-mode on my F12 box in one of my own trees and did not get a seg fault but I didn't have anything to merge at the time.

Comment 3 David Alan Hjelle 2010-04-23 15:49:56 UTC

How to reproduce
-----
1. Attempt to run bzr qdiff on a file that does not exist.
2.
3.


Comment
-----
Attempt to run bzr qdiff on a file that does not exist. I made a typo...

Comment 4 Toshio Ernie Kuratomi 2010-04-23 21:58:00 UTC
Still not able to reproduce:

$ bzr qdiff asdlkahdkjadiue
bzr: ERROR: Path(s) are not versioned: asdlkahdkjadiue
$ rpm -q bzr qbzr
bzr-2.0.5-1.fc12.x86_64
qbzr-0.18.5-1.fc12.noarch

Comment 5 Toshio Ernie Kuratomi 2010-04-23 22:12:10 UTC
Also, since these seem to be involved in the crash:

PyQt4-4.7.3-1.fc12.x86_64
qt-4.6.2-14.fc12.x86_64

Are your versions of these packages the same?

Comment 6 Toshio Ernie Kuratomi 2010-04-25 16:13:32 UTC
setting needinfo -- someone who can reproduce this crash, I need to know the output of:

rpm -q bzr qbzr PyQt4 qt


* A reliable reproducer
* If you have multiple machines, whether you can reproduce on multiple machines.

I suspect that PyQt4 may be causing these crashes and upgrading to the latest f12 version will fix it.

Comment 7 greg 2010-04-26 10:08:26 UTC
rpm -q bzr qbzr PyQt4 qt
---->
bzr-2.0.5-1.fc12.x86_64
package qbzr is not installed
PyQt4-4.7.2-2.fc12.x86_64
qt-4.6.2-8.fc12.x86_64


I try to stay up to date so I'm not sure it was the version at that time. Also note I always use the excellent bzr explorer

thanks for your support

Comment 8 Toshio Ernie Kuratomi 2010-04-26 15:28:19 UTC
(In reply to comment #7)
> rpm -q bzr qbzr PyQt4 qt
> ---->
> bzr-2.0.5-1.fc12.x86_64
> package qbzr is not installed

Note: I've packaged qbzr so it would be helpful to install that in place of your local copy so we're all using the same versions of things::
  su -c yum install qbzr

> PyQt4-4.7.2-2.fc12.x86_64
> qt-4.6.2-8.fc12.x86_64
> 
> 
> I try to stay up to date so I'm not sure it was the version at that time. Also
> note I always use the excellent bzr explorer
> 
This looks like a PyQt/Sip bug as reported here:
  https://bugzilla.redhat.com/show_bug.cgi?id=583951

If you can update these packages and it stops crashing I'll feel confident in closing this as a duplicate:
  su -c 'yum --enablerepo=updates-testing update sip PyQt4'

(That should get you: sip-4.10.2-1.fc12, PyQt4-4.7.3-1.fc12)

Comment 9 Toshio Ernie Kuratomi 2010-05-10 05:09:40 UTC
Okay, closing as fixed by the sip/PyQt4 update.  Feel free to reopen this bug or create a new one if this continues.

*** This bug has been marked as a duplicate of bug 583951 ***


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