FS#67690 - [qt5-base] [calibre] Crashes immediately after clicking "Edit Metadata"

Attached to Project: Community Packages
Opened by Dason Kurkiewicz (dasonk) - Sunday, 23 August 2020, 15:26 GMT
Last edited by Antonio Rojas (arojas) - Friday, 04 September 2020, 13:28 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Antonio Rojas (arojas)
Eli Schwartz (eschwartz)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The program crashes when I click on "Edit Metadata". If I install Calibre using their binary and instructions on their site I don't have this issue so my assumption is a missing dependency or mismatched version of something.

Additional info:
* package version(s): 4.23.0-1

Steps to reproduce:

Open Calibre -> Click on "Edit Metadata"
This task depends upon

Closed by  Antonio Rojas (arojas)
Friday, 04 September 2020, 13:28 GMT
Reason for closing:  Fixed
Additional comments about closing:  calibre 4.23.0-2
Comment by Doug Newgard (Scimmia) - Sunday, 23 August 2020, 15:45 GMT
Works fine for me. Logs?
Comment by Eli Schwartz (eschwartz) - Sunday, 23 August 2020, 18:04 GMT
I get this issue too, which I bisected to https://github.com/kovidgoyal/calibre/commit/9b3c57062b847548d0b8effdaae8d8cbba69dffc

The previous commit works fine, this commit crashes.
Comment by Eli Schwartz (eschwartz) - Monday, 24 August 2020, 04:48 GMT
Update: I can get it to work if I `unset DBUS_SESSION_BUS_ADDRESS XDG_RUNTIME_DIR` before running calibre.

Not really sure what's going on here. This is incredibly weird.

What DE or WM do you use? (FWIW I use Cinnamon.) Can you get it to work if you unset these variables?
Comment by Dason Kurkiewicz (dasonk) - Monday, 24 August 2020, 16:12 GMT
I run gnome. Unsetting those variables did allow me to get into the edit metadata without crashing.

Comment by Eli Schwartz (eschwartz) - Tuesday, 25 August 2020, 01:05 GMT
Have you ever launched a Gnome assistive technology before? e.g. the Virtual Keyboard. Is one currently running?
Comment by Dason Kurkiewicz (dasonk) - Tuesday, 25 August 2020, 01:14 GMT
I didn't think I had but I just checked and the "Screen Reader" accessibility option was turned on. I'll verify that with that option turned on Calibre crashes when I click the Edit Metadata but when I turn it off it does *not* crash. Interesting.
Comment by Eli Schwartz (eschwartz) - Tuesday, 25 August 2020, 01:29 GMT
If you turn them on once, they might just... linger in the background, forever.

I do not understand how this innocent little LineEdit results in a Qt crash... It's possible the upstream developer might have some idea, I mentioned it at https://bugs.launchpad.net/calibre/+bug/1892646
Comment by Eli Schwartz (eschwartz) - Tuesday, 25 August 2020, 04:42 GMT
I asked about this on Freenode IRC in the #qt channel, ended up building debug symbols and reporting a backtrace here: https://bugreports.qt.io/browse/QTBUG-86232
Comment by Eli Schwartz (eschwartz) - Friday, 28 August 2020, 21:27 GMT
Upstream workaround: https://github.com/kovidgoyal/calibre/commit/35f770955e07c4b39c5d694bc070d820ad4996d7

I backported it into the current package.
Comment by Antonio Rojas (arojas) - Friday, 04 September 2020, 08:35 GMT
Can we close this?
Comment by Dason Kurkiewicz (dasonk) - Friday, 04 September 2020, 12:46 GMT
Absolutely. Everything is working great now. Thanks!
Comment by Eli Schwartz (eschwartz) - Friday, 04 September 2020, 13:05 GMT
Well, Qt is still broken, but since we don't have any programs triggering the bug that's not a big deal. AFAICT the bug I opened is not on the verge of getting fixed, so there is nothing to backport either...

There is nothing actionable to do here and calibre is successfully worked around, so sure, let's close it.

Loading...