Description of problem: 1. open texstudio 2. open tex document 3. press F5 (compile and view) 4. texstudio crashes Pressing F6 (compile) works. The system on which this bug occurs, has a NVIDIA GTX 470 with nouveau driver installed. Version-Release number of selected component: texstudio-2.12.6-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: texstudio crash_function: SimulatedCPU::push(char*) executable: /usr/bin/texstudio journald_cursor: s=4337b5da427a49f6af8d547860fb67b0;i=baa;b=79087030ea97447eb5766de3c08a3800;m=200b91e47;t=561316696e7c9;x=9786996482c2aab2 kernel: 4.14.8-200.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (2 frames) #0 SimulatedCPU::push(char*) at ../debughelper.cpp:54 #1 SimulatedCPU::call(char*) at ../debughelper.cpp:1122
Created attachment 1372388 [details] File: backtrace
Created attachment 1372389 [details] File: cgroup
Created attachment 1372390 [details] File: core_backtrace
Created attachment 1372391 [details] File: cpuinfo
Created attachment 1372392 [details] File: dso_list
Created attachment 1372393 [details] File: environ
Created attachment 1372394 [details] File: exploitable
Created attachment 1372395 [details] File: limits
Created attachment 1372396 [details] File: maps
Created attachment 1372397 [details] File: open_fds
Created attachment 1372398 [details] File: proc_pid_status
Created attachment 1372399 [details] File: var_log_messages
texstudio-2.12.8-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-48f51ab8eb
texstudio-2.12.8-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-48f51ab8eb
texstudio-2.12.8-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.