Description of problem: I just had a bug report when I started my comp. Version-Release number of selected component: qgis-1.8.0-6.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: qgis crash_function: data kernel: 3.6.8-2.fc17.i686 truncated backtrace: :Thread no. 1 (10 frames) : #0 data at ../../src/corelib/tools/qscopedpointer.h:135 : #1 qGetPtrHelper<QScopedPointer<QObjectData> > at ../../src/corelib/global/qglobal.h:2455 : #2 d_func at itemviews/qtreewidget.h:370 : #3 QTreeWidget::setItemHidden at itemviews/qtreewidget.cpp:3105 : #4 setHidden at /usr/include/QtGui/qtreewidget.h:403 : #5 QgsLegend::mouseReleaseEvent at /usr/src/debug/qgis-1.8.0/src/app/legend/qgslegend.cpp:561 : #6 QWidget::event at kernel/qwidget.cpp:8371 : #7 QFrame::event at widgets/qframe.cpp:557 : #8 QAbstractScrollArea::viewportEvent at widgets/qabstractscrollarea.cpp:1043 : #9 QAbstractItemView::viewportEvent at itemviews/qabstractitemview.cpp:1644
Created attachment 656074 [details] File: core_backtrace
Created attachment 656075 [details] File: environ
Created attachment 656077 [details] File: backtrace
Created attachment 656078 [details] File: limits
Created attachment 656079 [details] File: cgroup
Created attachment 656080 [details] File: smolt_data
Created attachment 656081 [details] File: executable
Created attachment 656082 [details] File: maps
Created attachment 656083 [details] File: dso_list
Created attachment 656084 [details] File: proc_pid_status
Created attachment 656085 [details] File: open_fds
Created attachment 656086 [details] File: var_log_messages
"Comp"?
(In reply to comment #13) > "Comp"? Sorry, "computer". But I have many errors when I use Qgis. This is not the only bug report I had when using it.
So what seems to be happening is that the QgsLegend::mouseReleaseEvent at qgis-1.8.0/src/app/legend/qgslegend.cpp:561 is trying to set a tree view item to hidden which has already been destroyed. (We don't know where it got destroyed, we'd need a log from Valgrind for that.) Now whether the QgsLegend::mouseReleaseEvent is faulty (missing some checks, and possibly some other code setting a pointer to 0 when deleting the object so that QgsLegend::mouseReleaseEvent can check for a non-null pointer) or whether QgsLegend::mouseReleaseEvent is itself getting triggered on a destroyed object (which would mean the code destroying it is faulty and should be using deleteLater rather than delete), I'm not sure. In any case, I'm fairly sure the bug is somewhere in QGIS (not in Qt).
May I ask you to file a bug upstream? http://hub.qgis.org/projects/quantum-gis/issues Please be so kind and post the link afterwards.
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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.