search

olivierkes / manuskript

A open-source tool for writers
http://www.theologeek.ch/manuskript
GNU General Public License v3.0
1.78k stars 236 forks source link

Segmentation fault on Ubuntu 16.04 #574

Open zsoca8711 opened 5 years ago

zsoca8711 commented 5 years ago

Hi guys,

I tried manuskript and i love it. I was exploring the features and started having crashes after a few minutes.

I attempted to work out which feature was it and my impression is that it has to do something with plots and opening the Story line view.

I've tried with running the app from command line so i get some errors, but i'm not sure if this helps. Hope it does.

Any questions, let me know.

[/tmp] python3 /usr/bin/manuskript Debug: Web rendering engine used: QWebView Running manuskript version 0.9.0. Note: No translator found or loaded from system locale for locale en_US. Loading: /home/janoszsolt/pCloudDrive/0000_Konyviras/Proba1/proba1.msk Detected file format version: 1. Zip: True. Project /home/janoszsolt/pCloudDrive/0000_Konyviras/Proba1/proba1.msk loaded. QXcbConnection: XCB error: 5 (BadAtom), sequence: 616, resource id: 0, major code: 19 (DeleteProperty), minor code: 0 Fatal Python error: Segmentation fault

Current thread 0x00007f6b61ed6700 (most recent call first): File "/usr/share/manuskript/manuskript/main.py", line 145 in launch File "/usr/share/manuskript/manuskript/main.py", line 158 in run File "/usr/bin/manuskript", line 30 in Segmentation fault (core dumped)

gedakc commented 5 years ago

Did you have concurrent manuskript sessions open on the same project?

Because "CloudDrive" is mentioned in the log, I assume you have the project synchronized with other devices, and perhaps edit the project from multiple devices.

This is okay as long as only one device has the project open at any one time. Otherwise changes on one device will cause issues with other concurrently open devices, and lead to corruption of smart revision tracking. See issue #315.

If you have not used concurrent manuskript sessions, then something else may be going one. We have had a similar issue reported by ArchLinux users. See issue #450.

zsoca8711 commented 5 years ago

I didn't have the project open from an other device.

450 is not really helping :(

gedakc commented 5 years ago

If you create a new project does the crash occur?

What are the exact steps that reproduce the crash?

worstje commented 5 years ago

Some basic searches seem to indicate this bug is thrown by the platform abstraction layer of Qt. Another project introduced a very similar error while messing graphical code. Pixmaps, maybe? I don't really know the classes in question, but the general gist of the patch that is said to fix the problem in that project changed the way objection destruction was handled, among which was an added deleteLater() call. Maybe we have some graphical code that can benefit from such treatment to avoid this problem?

@zsoca8711 It would be useful to know more about the system you are running on for when someone wants to try to reproduce it or spot parallels with other bug reports.

What distribution? What version of Qt? What version of Python?

zsoca8711 commented 5 years ago

Hi @worstje

Sorry for the late response.

Python 3.5.2

[~] lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial

[~] pip3 list | grep -i qt qtconsole 4.4.2

@gedakc I have opened a new project. Seems okay in the last 10 minutes, which is a record since it started crashing :)

zsoca8711 commented 5 years ago

@gedakc I talked to soon, as soon as i accidentally clicked onto the white area below the editor, the app froze and then crashed. Since then, i tried to restart and got a new crash in ~10 seconds.

DarkRedman commented 5 years ago

I've a similar issue that happened after I changed the style from Fusion to another but in anycase it seems there is an issue with Qt5 because the icons don't load, last time I was not on Manjaro but Antergos and it worked perfectly with loading the icons. Now I selected "Plastique" and restart it does this core dump all the time, seems some style does crash and others don't.


qt5ct: using qt5ct plugin
Running manuskript version 0.9.0.
Found translation in settings: manuskript_fr.qm
Loaded translation from settings: manuskript_fr.qm.
qt5ct: D-Bus global menu: no
Loading: <private file>
Detected file format version: 1. Zip: True.
Le projet <private file> a été chargé.
Fatal Python error: Segmentation fault

Current thread 0x00007ff4b7398680 (most recent call first):
  File "/opt/manuskript/bin/../manuskript/ui/views/treeDelegates.py", line 41 in paint
  File "/opt/manuskript/bin/../manuskript/main.py", line 145 in launch
  File "/opt/manuskript/bin/../manuskript/main.py", line 158 in run
  File "/usr/bin/manuskript", line 13 in <module>
Erreur de segmentation (core dumped)```
worstje commented 5 years ago

@DarkRedman Thank you for the report.

Unfortunately this seems to be a Qt bug related to the specific theme you are using. The code of yours is crashing on:

# Background
style.drawPrimitive(style.PE_PanelItemViewItem, opt, painter)

For future reference, it would be useful if you listed what operating system you are using, and which theme exhibits the behaviour.

As it is, it is not a bug I am able to reproduce... but the code does not provide me any clues on the best way to work around it without impacting the rest of our users, either. The call in question is a quite basic one when it comes to drawing things interface elements, and it is used in several places in the manuskript codebase.

On your end, you could try commenting out that line (put a # in front of it) and see if it alleviates your crash... but I worry your outline might look a bit messed up as a result. Perhaps you can give it a shot and let us know how that works out? 😄

Kussh commented 4 years ago

I had the same error

Running manuskript version 0.11.0.
Preferred translation: ['en-GB'] (based on available ui languages)
Loaded translation: manuskript_en_GB.qm
Fontconfig warning: FcPattern object weight does not accept value [40 210)
Fatal Python error: Segmentation fault

Current thread 0x00007f5fae36a740 (most recent call first):
  File "/snap/manuskript/239/bin/../manuskript/ui/welcome.py", line 422 in populateTemplates
  File "/snap/manuskript/239/bin/../manuskript/ui/welcome.py", line 45 in __init__
  File "/snap/manuskript/239/bin/../manuskript/ui/mainWindow.py", line 32 in setupUi
  File "/snap/manuskript/239/bin/../manuskript/mainWindow.py", line 58 in __init__
  File "/snap/manuskript/239/bin/../manuskript/main.py", line 156 in prepare
  File "/snap/manuskript/239/bin/../manuskript/main.py", line 231 in run
  File "/snap/manuskript/239/bin/manuskript", line 13 in <module>
Segmentation fault (core dumped)

In my case, I'm using Manjaro 20.0 I installed the package from the Snap store. Apparently it's missing some dependencies. The error might be related to that? Anyway, I solved it by manually pulling the package from here and that solved my problem. Take this with two grains of salt as I'm inexperienced.

worstje commented 4 years ago

@Kussh That's not the same problem as what the other two had. I think you intended to comment in issue #763 instead?