calibre 3.x.x crashes when clicking on preferences button in linux

[Stephane Boyer]

since Calibre 3.0 and still there in 3.1.1

Linux x64 kernel 4.11.x

as soon as you click on preferences, the interface freezes and you can only get out of caliber by doing a " killall calibre" in an xterm

had to revert to 2.85.1

bug only affects 3.x releases

Steph!

[Kovid Goyal (kovid)]

I cannot replicate this on any of my linux amchines. Usually when
calibre looks like it has frozen it is because the popup window (in this
case the preference window) is offscreen or behind the main window.
For instance, if you connected an external monitor in the past, Qt might
be positioning the window on that (now disconnected) external monitor.

THe easiest way to check if this is the problem is to do

mv ~/.config/calibre ~/.config/calibre-renamed

and start calibre and see if you can replicate the problem.

 status invalid

[Stephane Boyer (sboyer2)]

did this but nothing shows up

but calibre is running

output of " ps ax |grep -i calibre"

  4936 ? Ssl 0:00 /opt/calibre/bin/calibre --detach
  7152 pts/1 S+ 0:00 grep -i calibre

and now reversing your move command does not restore previous
functionnality, Calibre no-longer shows up on screen at all.

On 2017-06-24 11:34 PM, Kovid Goyal wrote:
> I cannot replicate this on any of my linux amchines. Usually when
> calibre looks like it has frozen it is because the popup window (in this
> case the preference window) is offscreen or behind the main window.
> For instance, if you connected an external monitor in the past, Qt might
> be positioning the window on that (now disconnected) external monitor.
>
> THe easiest way to check if this is the problem is to do
>
> mv ~/.config/calibre ~/.config/calibre-renamed
>
> and start calibre and see if you can replicate the problem.
>
> status invalid
>
> ** Changed in: calibre
> Status: New => Invalid
>

--
Stephane Boyer
twitter: @Sboyer2

[Stephane Boyer (sboyer2)]

and starting "calibre" from an xterm gives me this and freezes there.
and ONLY a "kill -9 PID" will stop it

QXcbConnection: XCB error: 2 (BadValue), sequence: 398, resource id: 0,
major code: 1 (CreateWindow), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 399, resource id:
117440516, major code: 2 (ChangeWindowAttributes), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 400, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 401, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 402, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 404, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 405, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 406, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 410, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 414, resource id:
117440516, major code: 2 (ChangeWindowAttributes), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 415, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 416, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 417, resource id:
117440516, major code: 20 (GetProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 421, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 422, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 425, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 428, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 430, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 447, resource id:
117440516, major code: 2 (ChangeWindowAttributes), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 448, resource id:
117440516, major code: 2 (ChangeWindowAttributes), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 449, resource id:
117440516, major code: 20 (GetProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 450, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 451, resource id:
117440516, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 452, resource id:
117440516, major code: 18 (ChangeProper...

[Stephane Boyer (sboyer2)]

and this is what i get in "ps ax"

after clicking on preferences (and ONLY preferences, none of the other
buttons are affected, (before i press prefs) edit metadata, convert
book, etc. works)

  8650 ? Ssl 0:10 /opt/calibre/bin/calibre --detach
  8689 ? S 0:00 /opt/calibre/bin/calibre-parallel
--pipe-worker from calibre.utils.ipc.pool import run_main, worker_main;
run_main(worker_main)

Steph!

On 2017-06-24 11:34 PM, Kovid Goyal wrote:
> I cannot replicate this on any of my linux amchines. Usually when
> calibre looks like it has frozen it is because the popup window (in this
> case the preference window) is offscreen or behind the main window.
> For instance, if you connected an external monitor in the past, Qt might
> be positioning the window on that (now disconnected) external monitor.
>
> THe easiest way to check if this is the problem is to do
>
> mv ~/.config/calibre ~/.config/calibre-renamed
>
> and start calibre and see if you can replicate the problem.
>
> status invalid
>
> ** Changed in: calibre
> Status: New => Invalid
>

--
Stephane Boyer
twitter: @Sboyer2

[Kovid Goyal (kovid)]

From that output it looks like Qt 5.6 which calibre 3 bundles does not like the X server on your machine. Not much I can do about it, I suggest staying with calibre 2.85.1 for the time being.