FS#57992 - [cura] segfault on startup

Attached to Project: Community Packages
Opened by Gonçalo Pereira (G-Pereira) - Tuesday, 27 March 2018, 14:34 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 04 April 2018, 22:23 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jelle van der Waa (jelly)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Since the change of the version code it throws a SEGFAULT when starting the app.
This is because the app is confusing configs folders between this two:
~/.config/cura/3.2/cura.cfg
~/.config/cura/master/cura.cfg

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
simply start the app
This task depends upon

Closed by  Antonio Rojas (arojas)
Wednesday, 04 April 2018, 22:23 GMT
Reason for closing:  Fixed
Additional comments about closing:  python-pyqt5 5.10.1-2
Comment by Gonçalo Pereira (G-Pereira) - Tuesday, 27 March 2018, 14:34 GMT
version is 3.2.1-2
Comment by Doug Newgard (Scimmia) - Tuesday, 27 March 2018, 14:44 GMT
Is this different than your other ticket,  FS#57558 ?

Not much we can do about configs in your home dir.
Comment by Gonçalo Pereira (G-Pereira) - Tuesday, 27 March 2018, 14:53 GMT
Yes you can, on a clean install it does not work because it generate the folder 3.2 and then expects everything else to be on master folder.
Comment by Eli Schwartz (eschwartz) - Tuesday, 27 March 2018, 14:54 GMT
> If you want you can change the ownership of the package to me, I would like to mantain it :)

If you're suggesting you'd like to apply as a Trusted User, this is not really how you go about doing that.
Comment by Gonçalo Pereira (G-Pereira) - Tuesday, 27 March 2018, 14:58 GMT
Yes that is correct sorry :)
Comment by Gonçalo Pereira (G-Pereira) - Tuesday, 27 March 2018, 15:02 GMT
About solving the problem, you've set cura version on the cmake command but the makefile is changing it back to master on this line:
set(CURA_VERSION "master" CACHE STRING "Version name of Cura")
Comment by Gonçalo Pereira (G-Pereira) - Wednesday, 28 March 2018, 22:12 GMT
[(140157118235968)-MainThread] UM.Qt.Bindings.Theme.load [172]: Loading theme file: /usr/share/cura/resources/themes/cura-light/theme.json
2018-03-28 23:13:49,326 - DEBUG - [(140157118235968)-MainThread] UM.Qt.Bindings.Theme.load [240]: Loaded theme /usr/share/cura/resources/themes/cura-light
2018-03-28 23:13:49,388 - DEBUG - [(140157118235968)-MainThread] LocalContainerProvider.LocalContainerProvider.loadContainer [50]: Loading container fdmprinter
Fatal Python error: Segmentation fault

Thread 0x00007f787de58700 (most recent call first):
File "/usr/lib/python3.6/site-packages/UM/Backend/Backend.py", line 155 in _storeStderrToLogThread
File "/usr/lib/python3.6/threading.py", line 864 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap

Thread 0x00007f787e659700 (most recent call first):
File "/usr/lib/python3.6/site-packages/UM/Backend/Backend.py", line 147 in _storeOutputToLogThread
File "/usr/lib/python3.6/threading.py", line 864 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap

Thread 0x00007f787f794700 (most recent call first):
File "/usr/lib/cura/plugins/USBPrinting/USBPrinterOutputDeviceManager.py", line 86 in _updateThread
File "/usr/lib/python3.6/threading.py", line 864 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap

Thread 0x00007f78a0bb4700 (most recent call first):
File "/usr/lib/cura/plugins/RemovableDriveOutputDevice/RemovableDrivePlugin.py", line 61 in _updateThread
File "/usr/lib/python3.6/threading.py", line 864 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap

Thread 0x00007f78a17fa700 (most recent call first):
File "/usr/lib/python3.6/threading.py", line 295 in wait
File "/usr/lib/python3.6/threading.py", line 426 in acquire
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 86 in _nextJob
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 116 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap

Thread 0x00007f78a1ffb700 (most recent call first):
File "/usr/lib/python3.6/threading.py", line 295 in wait
File "/usr/lib/python3.6/threading.py", line 426 in acquire
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 86 in _nextJob
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 116 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap

Thread 0x00007f78a27fc700 (most recent call first):
File "/usr/lib/python3.6/threading.py", line 295 in wait
File "/usr/lib/python3.6/threading.py", line 426 in acquire
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 86 in _nextJob
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 116 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap

Thread 0x00007f78a2ffd700 (most recent call first):
File "/usr/lib/python3.6/threading.py", line 295 in wait
File "/usr/lib/python3.6/threading.py", line 426 in acquire
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 86 in _nextJob
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 116 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap

Thread 0x00007f78a37fe700 (most recent call first):
File "/usr/lib/python3.6/threading.py", line 295 in wait
File "/usr/lib/python3.6/threading.py", line 426 in acquire
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 86 in _nextJob
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 116 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap

Thread 0x00007f78a3fff700 (most recent call first):
File "/usr/lib/python3.6/threading.py", line 295 in wait
File "/usr/lib/python3.6/threading.py", line 426 in acquire
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 86 in _nextJob
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 116 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap

Thread 0x00007f78a8e8a700 (most recent call first):
File "/usr/lib/python3.6/threading.py", line 295 in wait
File "/usr/lib/python3.6/threading.py", line 426 in acquire
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 86 in _nextJob
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 116 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap

Thread 0x00007f78a968b700 (most recent call first):
File "/usr/lib/python3.6/threading.py", line 295 in wait
File "/usr/lib/python3.6/threading.py", line 426 in acquire
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 86 in _nextJob
File "/usr/lib/python3.6/site-packages/UM/JobQueue.py", line 116 in run
File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap

Current thread 0x00007f78df3ec540 (most recent call first):
File "/usr/lib/python3.6/site-packages/UM/Qt/QtApplication.py", line 236 in initializeEngine
File "/usr/lib/python3.6/site-packages/cura/CuraApplication.py", line 730 in run
File "/usr/bin/cura", line 141 in <module>
[1] 9762 segmentation fault (core dumped) cura
Comment by Jelle van der Waa (jelly) - Thursday, 29 March 2018, 06:57 GMT
Please don't paste such long backtraces, and again the problem is *somewhere* in Qt, I don't see any relation with setting the version.
Comment by Gonçalo Pereira (G-Pereira) - Thursday, 29 March 2018, 08:59 GMT
Yes I also thought of that, can you lower the version of the qt dependency? I am on a clean install so the problem certainly it's not only happening to me.
Comment by Thomas B (xythobuz) - Saturday, 31 March 2018, 00:11 GMT
Can confirm, I'm also on a very fresh Arch installation, installed this Cura packet without changing or creating any configs, and it's segfaulting on launch just as described here.

So, yes, this problem is definitely not only happening to G-Pereira :)
Comment by Jelle van der Waa (jelly) - Saturday, 31 March 2018, 18:25 GMT
Yes, it is known that it's broken, there is no need to report that......
Comment by Gerrit Großkopf (gerrit) - Saturday, 31 March 2018, 18:42 GMT
i wish i could just subcribe to changes without a comment but on this occasion, thank you for your hard work, Jelle van der Waa :) have a good day
Comment by Jelle van der Waa (jelly) - Sunday, 01 April 2018, 16:16 GMT
Further investigation, shows it's likely that the loading of cura's QML file triggers the segfault.

In /usr/lib/python3.6/site-packages/UM/Qt/QtApplication.py, it segfaults on:

self._engine = QQmlApplicationEngine()
self._engine.load(self._main_qml) # self._main_qml=/usr/share/cura/resources/qml/Cura.qml

File is owned by uranium.
   backtrace.txt (2.8 KiB)
Comment by Jelle van der Waa (jelly) - Sunday, 01 April 2018, 20:06 GMT
Btw, found the faulty commit in PyQt and send an e-mail about it upstream. Hopefully they can figure it out soon.

The code to revert is http://pkgbuild.com/~jelle/0001-Revert-register-type-magic.patch

Loading...