Version-Release number of selected component: qemu-system-x86-1.6.1-2.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/qemu-system-x86_64 -machine accel=kvm -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile -daemonize crash_function: dl_new_hash executable: /usr/bin/qemu-system-x86_64 kernel: 3.12.5-302.fc20.i686 runlevel: N 5 type: CCpp uid: 107 Truncated backtrace: Thread no. 1 (9 frames) #0 dl_new_hash at dl-lookup.c:476 #1 _dl_lookup_symbol_x at dl-lookup.c:715 #2 elf_machine_rela at ../sysdeps/i386/dl-machine.h:502 #3 elf_dynamic_do_Rela at do-rel.h:137 #4 _dl_relocate_object at dl-reloc.c:294 #5 dl_main at rtld.c:2196 #6 _dl_sysdep_start at ../elf/dl-sysdep.c:249 #7 _dl_start_final at rtld.c:329 #8 _dl_start at rtld.c:555
Created attachment 841839 [details] File: backtrace
Created attachment 841840 [details] File: cgroup
Created attachment 841841 [details] File: core_backtrace
Created attachment 841842 [details] File: dso_list
Created attachment 841843 [details] File: environ
Created attachment 841844 [details] File: exploitable
Created attachment 841845 [details] File: limits
Created attachment 841846 [details] File: maps
Created attachment 841847 [details] File: open_fds
Created attachment 841848 [details] File: proc_pid_status
Created attachment 841849 [details] File: var_log_messages
Thanks for the report. There's only one hit on the retrace server so this isn't reproducible, and the backtrace is deep in the loader or something. And surprise surprise, a weird backtrace when the proprietary nvidia drivers are present on the system. I doubt this is qemu's fault, and likely has something to do with nvidia, so closing as CANTFIX