Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1167016
Summary: | ark-4.14.3-1 : crash on exit | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rex Dieter <rdieter> | ||||
Component: | ark | Assignee: | Than Ngo <than> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 21 | CC: | arjunak234, awilliam, jreznik, kevin, ltinkl, massi.ergosum, rdieter, rnovacek, than | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | AcceptedFreezeException | ||||||
Fixed In Version: | ark-4.14.3-2.fc21 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-11-25 03:05:41 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1043131 | ||||||
Attachments: |
|
Description
Rex Dieter
2014-11-22 16:47:22 UTC
ark-4.14.3-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/FEDORA-2014-15442/ark-4.14.3-2.fc21 Proposed as a Freeze Exception for 21-final by Fedora user rdieter using the blocker tracking app because: Ark application as shipped on fedora live spin crashes on exit. Would like to ship non-crashing default applications. Discussed at 2014-11-24 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2014-11-24/f21-blocker-review.2014-11-24-17.01.log.txt . Accepted as a freeze exception issue - obviously good to fix crasher bugs in apps on the live image. ark-4.14.3-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 1167752 has been marked as a duplicate of this bug. *** I can still reproduce this in ark-4.14.3-2. #6 0x00007f80948672a0 in KXMLGUIFactory::removeClient(KXMLGUIClient*) (this=0x0, client=client@entry=0x2003448) at /usr/src/debug/kdelibs-4.14.3/kdeui/xmlgui/kxmlguifactory.cpp:419 #7 0x00007f807a9549d4 in Ark::Part::~Part() (this=0x20033b0, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /usr/src/debug/ark-4.14.3/part/part.cpp:141 #8 0x00007f807a954a59 in Ark::Part::~Part() (this=0x20033b0, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /usr/src/debug/ark-4.14.3/part/part.cpp:146 #9 0x00007f8095b4c479 in KParts::Part::slotWidgetDestroyed() (this=0x20033b0) at /usr/src/debug/kdelibs-4.14.3/kparts/part.cpp:353 #10 0x00007f809281cf8c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x2003220, m=m@entry=0x7f8092b65240 <QObject::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff9cd35340) at kernel/qobject.cpp:3567 #11 0x00007f809281d9ff in QObject::destroyed(QObject*) (this=this@entry=0x2003220, _t1=_t1@entry=0x2003220) at .moc/release-shared/moc_qobject.cpp:148 #12 0x00007f8092821b97 in QObject::~QObject() (this=0x2003220, __in_chrg=<optimized out>) at kernel/qobject.cpp:871 #13 0x00007f8093a3aaa7 in QWidget::~QWidget() (this=0x2003220, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1554 Created attachment 962920 [details]
Click on the "test.docx" file and then close ark to crash it.
Please open a new, preferably upstream, bug report... the crash you're experiencing is similar, but different. (I think this is precisely why we chose to carry a different KXMLGUIFactory patch, the one upstream chose to use may fail in this case) Should we revert the upstream patch and apply our previous one instead? |