After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 650974 - Removing a source when searching is ongoing leads to crash
Removing a source when searching is ongoing leads to crash
Status: RESOLVED OBSOLETE
Product: grilo
Classification: Other
Component: core
git master
Other Linux
: Normal critical
: ---
Assigned To: grilo-maint
grilo-maint
Depends on:
Blocks:
 
 
Reported: 2011-05-24 14:36 UTC by Juan A. Suarez Romero
Modified: 2018-09-24 09:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Juan A. Suarez Romero 2011-05-24 14:36:10 UTC 
Steps to reproduce it:

* Perform a search in an UPnP source supporting searching
* While searching is in progress, stop (or kill) the UPnP server

Current behaviour is a crash :)

Expected behaviour is not a crash indeed, but also user should be notified that there are no more elements from the source, and maybe the reason (SOURCE_REMOVED error?)
Comment 1 Murray Cumming 2012-11-14 09:58:58 UTC 
Maybe this is a candidate for a test case, to be run during "make check", so that when it is fixed it remains fixed.
Comment 2 Juan A. Suarez Romero 2012-11-16 15:39:16 UTC 
Indeed
Comment 3 gnome.vrb 2014-07-15 18:20:44 UTC 
Juan, can you paste a trace of the crash ?
Comment 4 Bastien Nocera 2014-08-15 12:50:27 UTC 
This was at a time when we had the old gupnp based plugin, marking as NEEDINFO.
Comment 5 GNOME Infrastructure Team 2018-09-24 09:17:38 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/grilo/issues/19.