Description of problem: Crashed on installing rhythmbox Version-Release number of selected component: gnome-software-3.10.0-1.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: gnome-software crash_function: gtk_widget_get_accessible executable: /usr/bin/gnome-software kernel: 3.11.1-300.fc20.x86_64 runlevel: unknown type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (8 frames) #0 gtk_widget_get_accessible at gtkwidget.c:12689 #1 app_state_changed at gs-app-tile.c:68 #7 g_object_notify_by_spec_internal at gobject.c:1141 #8 g_object_notify at gobject.c:1183 #9 gs_app_set_state at gs-app.c:317 #10 gs_plugin_loader_thread_func at gs-plugin-loader.c:1616 #11 g_thread_proxy at gthread.c:798 #13 clone at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
Created attachment 804564 [details] File: backtrace
Created attachment 804565 [details] File: cgroup
Created attachment 804567 [details] File: core_backtrace
Created attachment 804570 [details] File: dso_list
Created attachment 804572 [details] File: environ
Created attachment 804575 [details] File: exploitable
Created attachment 804577 [details] File: limits
Created attachment 804580 [details] File: maps
Created attachment 804582 [details] File: open_fds
Created attachment 804584 [details] File: proc_pid_status
Problem happens when you try and install an application in the new Gnome 'Software' application. To reproduce: 1) Find a package 2) Press install reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: gnome-software crash_function: gtk_widget_get_accessible executable: /usr/bin/gnome-software kernel: 3.11.2-301.fc20.x86_64 package: gnome-software-3.10.0-1.fc20 reason: Process /usr/bin/gnome-software was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
Also happens when using "Remove" for a package marked as "installed".
I'm pretty sure this should be fixed in 3.10.3, can you please verify? http://koji.fedoraproject.org/koji/buildinfo?buildID=474286 -- thanks.
After pressing the install button gnome-software crashed. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: gnome-software crash_function: gtk_widget_get_accessible executable: /usr/bin/gnome-software kernel: 3.11.8-300.fc20.x86_64 package: gnome-software-3.10.3-1.fc20 reason: Process /usr/bin/gnome-software was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
Switched to tab Installing while some items were finished some not started and some currently installed. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: gnome-software crash_function: gtk_widget_get_accessible executable: /usr/bin/gnome-software kernel: 3.11.6-301.fc20.x86_64 package: gnome-software-3.10.3-1.fc20 reason: Process /usr/bin/gnome-software was killed by signal 11 (SIGSEGV) runlevel: unknown type: CCpp uid: 1000
Just happened to me. Tried to install Manview. Gnome-software crashed and threw up this bug-error. rpm -q gnome-software gnome-software-3.10.4-1.fc20.x86_64
(In reply to Richard Hughes from comment #13) > I'm pretty sure this should be fixed in 3.10.3, can you please verify? > http://koji.fedoraproject.org/koji/buildinfo?buildID=474286 -- thanks. Richard, I hit this in F20 final (gnome-software 3.10.4-1.fc20)
This has happened to me multiple times when trying to install software through Gnome Software in F20 final. This seems to occur after I install another piece of software, then begin browsing through the available software before the install is finished, however it is intermittent. I do not know if this is the only condition in which this occurs.
Agree with Eli -- it happened when installing several packages and browsing for other packages. When I waited for one to finish before searching for other packages, this error did not occur.
same as Eki and Aija.
Just installing beediff from gnome-software-3.10.4-1.fc20 reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: gnome-software crash_function: gtk_widget_get_accessible executable: /usr/bin/gnome-software kernel: 3.11.10-301.fc20.x86_64 package: gnome-software-3.10.4-1.fc20 reason: Process /usr/bin/gnome-software was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: On a Gnome desktop: yum install @xfce yum install switchdesk-gui after reboot i've got this error reporter: libreport-2.1.11 backtrace_rating: 3 cmdline: gnome-software crash_function: gtk_widget_get_accessible executable: /usr/bin/gnome-software kernel: 3.12.6-300.fc20.x86_64 package: gnome-software-3.10.4-1.fc20 reason: gnome-software killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
libreport 2.2.0 sent me here gnome-software-3.10.4-2.fc20 kernel-3.13.6-200.fc20.x86_64 kernel: gnome-software[1711]: segfault at e2f6fd74 ip 00000032feee3fc3 sp 00007fffc04f25d0 error 4 in libgtk-3.so.0.1000.6[32fec00000+509000] [User Logs]: Mar 20 22:39:09 f20v.localdomain gnome-session[689]: (gnome-software:1492): Gs-WARNING **: failed to get updates: no results to show Mar 20 22:45:43 f20v.localdomain gnome-session[689]: (gnome-software:1711): Gs-WARNING **: failed to get updates: no results to show Mar 20 22:47:21 f20v.localdomain gnome-session[689]: (gnome-software:1711): Gtk-CRITICAL **: gtk_widget_get_accessible: assertion 'GTK_IS_WIDGET (widget)' failed Mar 20 22:47:21 f20v.localdomain gnome-session[689]: (gnome-software:1711): Gtk-CRITICAL **: gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed
Created attachment 877119 [details] core_backtrace, c23
Created attachment 877120 [details] coredump.xz
Another user experienced a similar problem: I don't remember the cause of the problem becuase it was a while ago and im only reporting the errors now. reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: gnome-software crash_function: gtk_widget_get_accessible executable: /usr/bin/gnome-software kernel: 3.11.10-301.fc20.x86_64 package: gnome-software-3.10.4-1.fc20 reason: Process /usr/bin/gnome-software was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
Estaba intentando instalar software desde la aplicacion y se cierra, solo me envia la ventana informe de errores automaticos y lo hace de manera automatica no me da tiempo para mas. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: gnome-software crash_function: gtk_widget_get_accessible executable: /usr/bin/gnome-software kernel: 3.11.10-301.fc20.x86_64 package: gnome-software-3.10.4-1.fc20 reason: Process /usr/bin/gnome-software was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: i suspect resident virus in cache memory.... reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gnome-software crash_function: gtk_widget_get_accessible executable: /usr/bin/gnome-software kernel: 3.14.4-200.fc20.x86_64 package: gnome-software-3.10.4-2.fc20 reason: gnome-software killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I was trying to remove software. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gnome-software crash_function: gtk_widget_get_accessible executable: /usr/bin/gnome-software kernel: 3.14.9-200.fc20.x86_64 package: gnome-software-3.10.4-2.fc20 reason: gnome-software killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Pues en realidad no tengo idea de como suceden la mayor parte de los problemas, inclusive aveces o muy seguido nisiquiera tengo abiertos los programas y ocurren muchos de los avisos de probelmas de errores reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gnome-software crash_function: gtk_widget_get_accessible executable: /usr/bin/gnome-software kernel: 3.14.9-200.fc20.x86_64 package: gnome-software-3.10.4-2.fc20 reason: gnome-software killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.