Hide Forgot
Description of problem: Version-Release number of selected component: virt-manager-1.4.0-4.fc26 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/python2 /usr/share/virt-manager/virt-manager crash_function: setcontext executable: /usr/bin/python2.7 global_pid: 7969 kernel: 4.9.0-0.rc6.git2.1.fc26.x86_64 pkg_fingerprint: 812A 6B4B 64DA B85D pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 0 (2 frames) #0 setcontext at ../sysdeps/unix/sysv/linux/x86_64/setcontext.S:55 #1 __start_context at ../sysdeps/unix/sysv/linux/x86_64/__start_context.S:39
Created attachment 1229364 [details] File: backtrace
Created attachment 1229365 [details] File: cgroup
Created attachment 1229366 [details] File: core_backtrace
Created attachment 1229367 [details] File: dso_list
Created attachment 1229368 [details] File: environ
Created attachment 1229369 [details] File: limits
Created attachment 1229370 [details] File: maps
Created attachment 1229371 [details] File: mountinfo
Created attachment 1229372 [details] File: namespaces
Created attachment 1229373 [details] File: open_fds
Created attachment 1229374 [details] File: proc_pid_status
Created attachment 1229375 [details] File: var_log_messages
This backtrace doesn't make much sense, and given that the report is marked TAINTED I'm guessing this is some kernel weirdness that we can't fix on an app side