Linux Issue

peterkent · 10-13-2014, 09:18 AM

Using Linux Mint 13 Maya (Ubuntu Precise)

On attempting to run Calibre 2.0 or later, I get:

$ calibre
Traceback (most recent call last):
File "site-packages/calibre/gui2/splash.py", line 56, in run
File "site-packages/calibre/gui2/splash.py", line 87, in _show_message
File "site-packages/calibre/gui2/splash.py", line 84, in send
File "site-packages/calibre/utils/ipc/__init__.py", line 19, in eintr_retry_call
IOError: [Errno 32] Broken pipe
libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
Segmentation fault

Any ideas? I've reverted to Calibre 1.48

gbm · 10-13-2014, 09:47 AM

Quote:

Originally Posted by peterkent

Using Linux Mint 13 Maya (Ubuntu Precise)

On attempting to run Calibre 2.0 or later, I get:

$ calibre
Traceback (most recent call last):
File "site-packages/calibre/gui2/splash.py", line 56, in run
File "site-packages/calibre/gui2/splash.py", line 87, in _show_message
File "site-packages/calibre/gui2/splash.py", line 84, in send
File "site-packages/calibre/utils/ipc/__init__.py", line 19, in eintr_retry_call
IOError: [Errno 32] Broken pipe
libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
Segmentation fault

Any ideas? I've reverted to Calibre 1.48

Open a terminal and post the results of:

Code:

cat /proc/cpuinfo

bernie

peterkent · 10-13-2014, 10:03 AM

$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
stepping : 6
microcode : 0x60c
cpu MHz : 1998.000
cache size : 6144 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm dts tpr_shadow vnmi flexpriority
bogomips : 5984.76
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
stepping : 6
microcode : 0x60c
cpu MHz : 1998.000
cache size : 6144 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm dts tpr_shadow vnmi flexpriority
bogomips : 5984.97
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

PeterT · 10-13-2014, 10:06 AM

What calibre version? There was an issue with 2.0, supposedly fixed in 2.1. See https://bugs.launchpad.net/calibre/+bug/1360200 and/or Calibre 2.0 crashes at startup under Linux Mint 17

peterkent · 10-13-2014, 10:21 AM

Same error with 2.1 and the latest version.

gbm · 10-13-2014, 10:28 AM

Do you have another python program running? If so then stop it.
Download and reinstall calibre 2.5 using the manual install.

Code:

sudo rm -rf /opt/calibre/* && sudo tar xvf /path/to/downloaded/calibre-tarball.txz -C /opt/calibre

Best option is to upgrade to Mint 17.

bernie

peterkent · 10-13-2014, 10:40 AM

Precisely the same error installing 2.5 manually.

I'm reluctant to upgrade Mint without some confidence that it's going to fix the problem.

gbm · 10-13-2014, 10:46 AM

Quote:

Originally Posted by peterkent

Precisely the same error installing 2.5 manually.

I'm reluctant to upgrade Mint without some confidence that it's going to fix the problem.

I am running Mint 17 Mate and Cinnamon calibre works good on both systems.

Make a live usb stick of Mint 17, install calibre using the live usb to test.

bernie

DiapDealer · 10-13-2014, 11:35 AM

It could be the calibre splash logo that's doing it. I had a similar issue with the calibre 2.0 betas on a virtual Mint 15 (Xfce) installation before. The installation would go OK, but it wouldn't run.

Find the gui.json file in calibre's config directory (probably ~/.config/calibre) and look for:

Code:

"show_splash_screen": true,

and change it to:

Code:

"show_splash_screen": false,

Worth a shot anyway.

I have no issues at all with calibre 2.x on Mint 16/Cinnamon, for what it's worth.

peterkent · 10-13-2014, 12:06 PM

For some reason the line
"show_splash_screen": true,
wasn't present.

So I added
"show_splash_screen": false,

This made a subtle difference in that the only errors now are

libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
Segmentation fault

Still refusing to run

thechach · 10-13-2014, 12:10 PM

Something along these lines perhaps? Sounds identical.

https://bugs.launchpad.net/calibre/+bug/1365764

gbm · 10-13-2014, 12:26 PM

Quote:

Originally Posted by peterkent

For some reason the line
"show_splash_screen": true,
wasn't present.

So I added
"show_splash_screen": false,

This made a subtle difference in that the only errors now are

libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
Segmentation fault

Still refusing to run

Rename your home/.config/calibre folder and then let calibre start up like it is a fresh install.

bernie

DiapDealer · 10-13-2014, 12:42 PM

Quote:

Originally Posted by gbm

Rename your home/.config/calibre folder and then let calibre start up like it is a fresh install.

bernie

And before you close down calibre after the successful configure, use the GUI to disable the splash screen (Preferences->Look and Feel->Main interface) in case you didn't get it correctly disabled in the gui.json file.

Then again ... it may be something else entirely.

kovidgoyal · 10-13-2014, 09:15 PM

A segfault means qt 5 does not like something on your system. You can get more info by getting a backtrace from the core file, or running under gdb, but generally speaking, you're better off just stick with 1.48 (which uses Qt 4) until you are ready to upgrade your system.

peterkent · 10-14-2014, 03:24 AM

Quote:

just stick with 1.48 (which uses Qt 4) until you are ready to upgrade your system.

Thanks for the advice. I think I'll do that and stick with 1.48 for a little while longer.

10-13-2014, 09:18 AM	#1
peterkent Junior Member Posts: 9 Karma: 10 Join Date: Oct 2014 Device: Kindle paperwhite	Linux Issue Using Linux Mint 13 Maya (Ubuntu Precise) On attempting to run Calibre 2.0 or later, I get: $ calibre Traceback (most recent call last): File "site-packages/calibre/gui2/splash.py", line 56, in run File "site-packages/calibre/gui2/splash.py", line 87, in _show_message File "site-packages/calibre/gui2/splash.py", line 84, in send File "site-packages/calibre/utils/ipc/__init__.py", line 19, in eintr_retry_call IOError: [Errno 32] Broken pipe libpng warning: iCCP: Not recognizing known sRGB profile that has been edited Segmentation fault Any ideas? I've reverted to Calibre 1.48

10-13-2014, 10:28 AM	#6
gbm Wizard Posts: 2,215 Karma: 8888888 Join Date: Jun 2010 Device: Kobo Clara HD,Hisence Sero 7 Pro RIP, Nook STR, jetbook lite	Do you have another python program running? If so then stop it. Download and reinstall calibre 2.5 using the manual install. Code: sudo rm -rf /opt/calibre/* && sudo tar xvf /path/to/downloaded/calibre-tarball.txz -C /opt/calibre Best option is to upgrade to Mint 17. bernie

10-13-2014, 11:35 AM	#9
DiapDealer Grand Sorcerer Posts: 28,882 Karma: 207000000 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	It could be the calibre splash logo that's doing it. I had a similar issue with the calibre 2.0 betas on a virtual Mint 15 (Xfce) installation before. The installation would go OK, but it wouldn't run. Find the gui.json file in calibre's config directory (probably ~/.config/calibre) and look for: Code: "show_splash_screen": true, and change it to: Code: "show_splash_screen": false, Worth a shot anyway. I have no issues at all with calibre 2.x on Mint 16/Cinnamon, for what it's worth.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[CC] - Linux wireless connection issue	Lofwyr23	Devices	8	09-09-2013 12:04 PM
Linux update issue	kojak666	Calibre	1	12-25-2011 10:58 PM
0.6.9 Linux Install Issue	notsure	Calibre	8	08-28-2009 05:12 PM
0.6.10 Linux install issue	jquest	Calibre	5	08-28-2009 10:58 AM
Calibre 0.6.4 Linux Install Issue	notsure	Calibre	4	08-03-2009 06:47 PM

10-13-2014, 10:03 AM	#3
peterkent Junior Member Posts: 9 Karma: 10 Join Date: Oct 2014 Device: Kindle paperwhite	$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz stepping : 6 microcode : 0x60c cpu MHz : 1998.000 cache size : 6144 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm dts tpr_shadow vnmi flexpriority bogomips : 5984.76 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz stepping : 6 microcode : 0x60c cpu MHz : 1998.000 cache size : 6144 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm dts tpr_shadow vnmi flexpriority bogomips : 5984.97 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management:

10-13-2014, 10:06 AM	#4
PeterT Grand Sorcerer Posts: 13,693 Karma: 79983758 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	What calibre version? There was an issue with 2.0, supposedly fixed in 2.1. See https://bugs.launchpad.net/calibre/+bug/1360200 and/or Calibre 2.0 crashes at startup under Linux Mint 17

10-13-2014, 10:21 AM	#5
peterkent Junior Member Posts: 9 Karma: 10 Join Date: Oct 2014 Device: Kindle paperwhite	Same error with 2.1 and the latest version.

10-13-2014, 10:40 AM	#7
peterkent Junior Member Posts: 9 Karma: 10 Join Date: Oct 2014 Device: Kindle paperwhite	Precisely the same error installing 2.5 manually. I'm reluctant to upgrade Mint without some confidence that it's going to fix the problem.

10-13-2014, 12:06 PM	#10
peterkent Junior Member Posts: 9 Karma: 10 Join Date: Oct 2014 Device: Kindle paperwhite	For some reason the line "show_splash_screen": true, wasn't present. So I added "show_splash_screen": false, This made a subtle difference in that the only errors now are libpng warning: iCCP: Not recognizing known sRGB profile that has been edited Segmentation fault Still refusing to run

10-13-2014, 12:10 PM	#11
thechach Junior Member Posts: 3 Karma: 10 Join Date: Aug 2014 Device: Nook HD+	Something along these lines perhaps? Sounds identical. https://bugs.launchpad.net/calibre/+bug/1365764

10-13-2014, 09:15 PM	#14
kovidgoyal creator of calibre Posts: 45,604 Karma: 28548974 Join Date: Oct 2006 Location: Mumbai, India Device: Various	A segfault means qt 5 does not like something on your system. You can get more info by getting a backtrace from the core file, or running under gdb, but generally speaking, you're better off just stick with 1.48 (which uses Qt 4) until you are ready to upgrade your system.

Advert

Advert