Bug 759074
Summary: | [abrt] xournal-0.4.5-15.fc16: handle_error: Process /usr/bin/xournal was killed by signal 5 (SIGTRAP) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mohamed AMAZIRH <m.amazirh> | ||||||||||
Component: | gtk2 | Assignee: | Matthias Clasen <mclasen> | ||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 16 | CC: | bargem, bp2626, buhrt, christophe.ribet, dylan.semler, mclasen, mkasik, nathanael, privat, ricflopes, rvinyard | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | i686 | ||||||||||||
OS: | Unspecified | ||||||||||||
URL: | https://sourceforge.net/tracker/index.php?func=detail&aid=3067270&group_id=163434&atid=827733 | ||||||||||||
Whiteboard: | abrt_hash:78624435ff0d8ce2ffc9fea41988f56a626ed0fd | ||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2013-02-14 01:58:04 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
Mohamed AMAZIRH
2011-12-01 11:28:13 UTC
Created attachment 539091 [details]
File: dso_list
Created attachment 539092 [details]
File: maps
Created attachment 539093 [details]
File: smolt_data
Created attachment 539094 [details]
File: backtrace
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Hello Mohamed. Is the issue reproducible? If You know how to reproduce it, then please attach the reproduction scenario. Anyway ... this seems to be a gdk related issue and the SIGTRAP was very probably raised by some assert. Upstream seems to have a similar bug report with the same error message: https://sourceforge.net/tracker/index.php?func=detail&aid=3067270&group_id=163434&atid=827733 ... and they seem to have a patch in the CVS. This is going to be introduced in the next version. Please, let me know if the issue is still present. Best regards, Jaromir. Hello Jaromir. Sorry it took me a long time to respond. >Is the issue reproducible? If You know how to reproduce it, then please attach >the reproduction scenario. The crash happens randomly, and only once in a while, so it's hard to come up with a reproduction scenario . But every time it happens, it's always when I'm trying to switch away from or back to Xournal (I don't have to click on the canvas like in the upstream bug). >... and they seem to have a patch in the CVS. >This is going to be introduced in the next version. >Please, let me know if the issue is still present. Ok. Thank you for your help. Backtrace analysis of bugs across components suggests the actual bug is in component gtk2 or libX11 instead of component xournal, reassigning to gtk2. Bugs which were found to be similar to this bug: gnome-color-manager: bug #659928 pgadmin3: bug #798789 seamonkey: bug #645145, bug #689149 ucview: bug #684978 This comment is automatically generated. *** Bug 798789 has been marked as a duplicate of this bug. *** *** Bug 714130 has been marked as a duplicate of this bug. *** nomachine guest 64 bits with server freenx 32 bits try to use xfce4 panel on guest backtrace_rating: 4 Package: Terminal-0.4.8-4.fc18 OS Release: Fedora release 18 (Spherical Cow) Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. |