![]() # | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service Could you show me what your command zypper lr -d shows please? You seem to have different repos. I wanted to wait to see whether a python update makes calibre usable again. Interesting, farcusnz, now 3 days after your reply I still have only version 20200909 and Zypper dup says nothing to do, You had already version 20200910. I presume that is related to the first line “Fatal Python error: PyEval_SaveThread: NULL tstate” but I don’t understand what it means and even less how it can be fixed. Here twice I opened (each time a different) book and then it crashed. I opened calibre in the command line and got the following: calibreįatal Python error: PyEval_SaveThread: NULL tstateĬurrent thread 0x00007f7a6a424740 (most recent call first):įile "/usr/lib64/calibre/calibre/gui2/webengine.py", line 126 in _dispatch_messagesįile "/usr/lib64/calibre/calibre/gui2/viewer/main.py", line 239 in mainįile "/usr/lib64/calibre/calibre/gui_launch.py", line 80 in ebook_viewerįile "/usr/lib64/calibre/calibre/utils/ipc/worker.py", line 208 in mainįile "/usr/bin/calibre-parallel", line 20 in Ĭurrent thread 0x00007fc1017d9740 (most recent call first): ![]() Or to be more accurate the books opened for less than a second and then disappeared. ![]() Although everything looked OK when I opened calibre I couldn’t open any books. ![]() Today I updated tumbleweed to version 20200906. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |