Description of problem: launching ViTables and trying to open the .hg file of interest. Version-Release number of selected component: ViTables-2.1-3.fc17 Additional info: libreport version: 2.0.14 abrt_version: 2.0.13 cmdline: /usr/bin/python /usr/bin/vitables kernel: 3.5.4-2.fc17.x86_64 backtrace: :vtapp.py:750:nodeOpen:TypeError: arguments did not match any overloaded call: : QMessageBox.information(QWidget, QString, QString, QMessageBox.StandardButtons buttons=QMessageBox.Ok, QMessageBox.StandardButton defaultButton=QMessageBox.NoButton): argument 1 has unexpected type 'VTApp' : QMessageBox.information(QWidget, QString, QString, int, int button1=0, int button2=0): argument 1 has unexpected type 'VTApp' : QMessageBox.information(QWidget, QString, QString, QString, QString button1Text=QString(), QString button2Text=QString(), int defaultButtonNumber=0, int escapeButtonNumber=-1): argument 1 has unexpected type 'VTApp' : :Traceback (most recent call last): : File "/usr/lib/python2.7/site-packages/vitables/h5db/dbsTreeView.py", line 279, in mouseDoubleClickEvent : self.activateNode(current) : File "/usr/lib/python2.7/site-packages/vitables/h5db/dbsTreeView.py", line 146, in activateNode : self.vtapp.nodeOpen(index) : File "/usr/lib/python2.7/site-packages/vitables/vtapp.py", line 750, in nodeOpen : 'Text of the Unimplemented node dialog')) :TypeError: arguments did not match any overloaded call: : QMessageBox.information(QWidget, QString, QString, QMessageBox.StandardButtons buttons=QMessageBox.Ok, QMessageBox.StandardButton defaultButton=QMessageBox.NoButton): argument 1 has unexpected type 'VTApp' : QMessageBox.information(QWidget, QString, QString, int, int button1=0, int button2=0): argument 1 has unexpected type 'VTApp' : QMessageBox.information(QWidget, QString, QString, QString, QString button1Text=QString(), QString button2Text=QString(), int defaultButtonNumber=0, int escapeButtonNumber=-1): argument 1 has unexpected type 'VTApp' : :Local variables in innermost frame: :current: <PyQt4.QtCore.QModelIndex object at 0x2f7f7c0> :index: <PyQt4.QtCore.QModelIndex object at 0x2f7f7c0> :self: <vitables.vtapp.VTApp object at 0x2cd0950> :leaf: /group1/table1 (UnImplemented(2,)) '' : NOTE: <The UnImplemented object represents a PyTables unimplemented : dataset present in the '/home/l.orifici/projs/eolo_0.8/tables/core/Installazione/5/4.h5' HDF5 file. If you want to see this : kind of HDF5 dataset implemented in PyTables, please contact the : developers.> : :dbs_tree_leaf: <vitables.h5db.leafNode.LeafNode object at 0x2e53550>
Created attachment 622974 [details] File: core_backtrace
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.