Description of problem:
I install some programms just.
Version-Release number of selected component:
cmdline: /usr/bin/gnome-software --gapplication-service
runlevel: N 5
Thread no. 1 (10 frames)
#0 g_type_check_instance at gtype.c:4134
#1 g_signal_handlers_disconnect_matched at gsignal.c:2858
#2 gs_app_row_destroy at gs-app-row.c:366
#7 gtk_widget_dispose at gtkwidget.c:11962
#9 gtk_container_remove at gtkcontainer.c:1737
#10 gtk_list_box_forall_internal at gtklistbox.c:2360
#11 gs_shell_installed_load at gs-shell-installed.c:237
#12 gs_shell_installed_reload at gs-shell-installed.c:261
#13 gs_shell_updates_changed_cb at gs-shell.c:505
#14 _g_closure_invoke_va at gclosure.c:831
Created attachment 1004002 [details]
Created attachment 1004003 [details]
Created attachment 1004004 [details]
Created attachment 1004006 [details]
Created attachment 1004008 [details]
Created attachment 1004010 [details]
Created attachment 1004012 [details]
Created attachment 1004014 [details]
Created attachment 1004016 [details]
Created attachment 1004017 [details]
Looks like a GsApp ref / unref mismatch somewhere. Do you have a way to reproduce this, by any chance?
I'm so sorrty but I can't tell precisely about this bug because I have some other bugs now. If i reproduce this that need i to do then?
If you find a way to reproduce it, please let me know what steps you did to get it to crash and I'll see if I can figure out the cause then.
gnome-software-3.18.0-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-88c71c30c0
gnome-software-3.18.0-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update gnome-software'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-88c71c30c0
gnome-software-3.18.0-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.