Bug 760235 - Can not start calibre, PyQt4 module fails-to-load/segfault
Summary: Can not start calibre, PyQt4 module fails-to-load/segfault
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: PyQt4
Version: 16
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-05 16:57 UTC by biAji
Modified: 2013-02-14 02:16 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-14 02:16:39 UTC
Type: ---


Attachments (Terms of Use)

Description biAji 2011-12-05 16:57:45 UTC
Description of problem:
Everytime try to start calibre count an "Segment Fault" error

Version-Release number of selected component (if applicable):
calibre-0.8.25-1.fc16.i686

How reproducible:
Just start it

Steps to Reproduce:
1. open a terminal 
2. type  calibre
3. boom~~
  
Actual results:


Expected results:


Additional info:

I try using python -m pdb to trace the error . It maybe releate to PyQt4 module.
Because when execute the import function as the line 7 below, it's produce the error:


> /usr/lib/calibre/calibre/gui2/__init__.py(1)<module>()
-> __license__   = 'GPL v3'
(Pdb) l
  1 B->	__license__   = 'GPL v3'
  2  	__copyright__ = '2008, Kovid Goyal <kovid at kovidgoyal.net>'
  3  	""" The GUI """
  4  	import os, sys, Queue, threading
  5  	from threading import RLock
  6  	from urllib import unquote
  7  	from PyQt4.Qt import (QVariant, QFileInfo, QObject, SIGNAL, QBuffer, Qt,

Comment 1 Kevin Fenzi 2011-12-05 21:44:14 UTC
output of: 

rpm -q PyQt4

and

rpm -V PyQt4 

please?

Comment 2 biAji 2011-12-06 14:36:32 UTC
 rpm -q PyQt4
PyQt4-4.8.6-1.fc16.i686


rpm -V PyQt4 

no output at all~  It seemed my package is ok.

Comment 3 Kevin Fenzi 2011-12-09 22:50:21 UTC
Can you run: 

calibre-debug -g

and attach the output? 
Also, can you create a new user, login as them and run calibre. Does it work there? 
(That will tell us if it's a system wide issue or a per user setting issue).

Comment 4 biAji 2012-01-17 14:02:08 UTC
It seemed the error changed since I update to  calibre-0.8.33-2.fc16.i686:

$  calibre-debug -g
Segmentation fault

$ calibre-debug   
Traceback (most recent call last):
  File "/usr/bin/calibre-debug", line 19, in <module>
    sys.exit(main())
  File "/usr/lib/calibre/calibre/debug.py", line 242, in main
    ipython()
  File "/usr/lib/calibre/calibre/__init__.py", line 763, in ipython
    from IPython.Shell import IPShellEmbed
ImportError: No module named Shell

==================


I create a new user as you request, but still got the same error.

Comment 5 biAji 2012-01-17 14:10:16 UTC
OK, I'm wrong, it seemed still there:

> /usr/lib/calibre/calibre/gui2/__init__.py(7)<module>()
-> from PyQt4.Qt import (QVariant, QFileInfo, QObject, SIGNAL, QBuffer, Qt,
(Pdb) l
  2  	__copyright__ = '2008, Kovid Goyal <kovid at kovidgoyal.net>'
  3  	""" The GUI """
  4  	import os, sys, Queue, threading
  5  	from threading import RLock
  6  	from urllib import unquote
  7 B->	from PyQt4.Qt import (QVariant, QFileInfo, QObject, SIGNAL, QBuffer, Qt,
  8  	                    QByteArray, QTranslator, QCoreApplication, QThread,
  9  	                    QEvent, QTimer, pyqtSignal, QDateTime, QDesktopServices,
 10  	                    QFileDialog, QFileIconProvider, QSettings,
 11  	                    QIcon, QApplication, QDialog, QUrl, QFont)
 12  	
(Pdb)

Comment 6 Rex Dieter 2012-01-17 17:53:59 UTC
this combination works for me:

$ rpm -q calibre qt sip PyQt4
calibre-0.8.33-2.fc16.x86_64
qt-4.8.0-7.fc16.x86_64
qt-4.8.0-7.fc16.i686
sip-4.13-1.fc16.x86_64
PyQt4-4.8.6-1.fc16.x86_64

can you verify the versions of all these on your system too?

Comment 7 Rex Dieter 2012-01-17 17:58:23 UTC
minimal test case, try:

python -c 'from PyQt4.Qt import *'

does that give error too?

Comment 8 biAji 2012-01-18 14:08:48 UTC
Thanks for your quick reply!

$rpm -q calibre qt sip PyQt4
calibre-0.8.33-2.fc16.i686
qt-4.8.0-5.fc16.i686
sip-4.13-1.fc16.i686
PyQt4-4.8.6-1.fc16.i686
================================

$ python -c 'from PyQt4.Qt import *'
Segmentation fault


ok, it seemed just exist in x86 build of fedora 16~

Comment 9 Rex Dieter 2012-01-18 14:29:19 UTC
OK, definitely, PyQt4 specific, reassigning.

Comment 10 Fedora End Of Life 2013-01-17 00:15:38 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 11 Fedora End Of Life 2013-02-14 02:16:51 UTC
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.


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