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 741637 - crash in gom_repository_automatic_migrator
crash in gom_repository_automatic_migrator
Status: RESOLVED DUPLICATE of bug 748196
Product: grilo
Classification: Other
Component: plugins
0.2.x
Other NetBSD
: Normal normal
: ---
Assigned To: grilo-maint
grilo-maint
Depends on:
Blocks:
 
 
Reported: 2014-12-17 10:39 UTC by Patrick Welche
Modified: 2015-04-27 11:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Patrick Welche 2014-12-17 10:39:07 UTC 
Starting totem 3.14.1 without a filename dumps core with:

(gdb) bt

+ Trace 234427

  • #0 g_type_class_ref
    from /usr/pkg/lib/libgobject-2.0.so.0
  • #1 gom_repository_automatic_migrator
    at ./gom/gom-repository.c line 357
  • #2 gom_repository_migrate_cb
    at ./gom/gom-repository.c line 184
  • #3 gom_adapter_worker
    at ./gom/gom-adapter.c line 111
  • #4 g_thread_proxy
    from /usr/pkg/lib/libglib-2.0.so.0
  • #5 ??
    from /usr/lib/libpthread.so.1
  • #6 ??
    from /usr/lib/libc.so.12
  • #7 ??
  • #8 ??
  • #1 gom_repository_automatic_migrator
    at ./gom/gom-repository.c line 357 

I have only just built and installed gom 0.2.1 as an indirect dependency for totem, so why "migrator". Migrate from an earlier (non-existent) version?

What should I look for?
Comment 1 Bastien Nocera 2014-12-17 15:48:33 UTC 
Which version of grilo-plugins and gom?
Comment 2 Patrick Welche 2014-12-17 16:31:04 UTC 
I mentioned gom 0.2.1 above. grilo-plugins is 0.2.13.
Comment 3 Bastien Nocera 2014-12-18 07:57:44 UTC 
I have no idea which grilo plugin is crashing on your machine, but I cannot reproduce.
Comment 4 Patrick Welche 2015-01-07 21:14:15 UTC 
But maybe you could give me a hint on where to look?
Is there a way of listing plugins as they are loaded?
How did you make the connection between a function called gom_repository_migrate_cb() and grilo plugins?
Comment 5 Patrick Welche 2015-01-07 23:45:18 UTC 
Maybe this gives a clue?

$ totem
(totem:10132): Grilo-DEBUG: [registry] grl-registry.c:254: $GRL_PLUGIN_RANKS is not set, using default ranks.
(totem:10132): Grilo-DEBUG: [shoutcast] grl-shoutcast.c:136: shoutcast_plugin_init
Grilo-INFO: [shoutcast] grl-shoutcast.c:143: Configuration not provided! Plugin not loaded
(totem:10132): Grilo-DEBUG: [registry] grl-registry.c:368: Failed to initialize plugin from /usr/pkg/lib/grilo-0.2/libgrlshoutcast.so. Check if plugin is well configured
(totem:10132): Grilo-DEBUG: [bookmarks] grl-bookmarks.c:132: grl_bookmarks_plugin_init
(totem:10132): Grilo-DEBUG: [bookmarks] grl-bookmarks.c:174: grl_bookmarks_source_new
(totem:10132): Grilo-DEBUG: [bookmarks] grl-bookmarks.c:236: Opening database connection...
(totem:10132): Grilo-DEBUG: [registry] grl-registry.c:829: New source available: 'grl-bookmarks'
(totem:10132): Grilo-DEBUG: [registry] grl-registry.c:239: Source rank 'grl-bookmarks' : 0
(totem:10132): Grilo-DEBUG: [source] grl-source.c:3697: requested fast keys
(totem:10132): Grilo-DEBUG: [source] grl-source.c:1026: operation_set_ongoing (1)
(totem:10132): Grilo-DEBUG: [source] grl-source.c:4483: grl_source_notify_change_start
(totem:10132): Grilo-DEBUG: [registry] grl-registry.c:380: Loaded plugin 'grl-bookmarks' from '/usr/pkg/lib/grilo-0.2/libgrlbookmarks.so'
[1]   Segmentation fault (core dumped) totem
Comment 6 Patrick Welche 2015-01-07 23:58:08 UTC 
Yes, it is a clue: compiling grilo-plugins --disable-bookmarks prevents the crash.
Comment 7 Bastien Nocera 2015-04-27 11:16:40 UTC 
I'm going to take a guess and say that this was bug 748196 in gom. Please reopen if you can still see the problem with the newer version of gom.

*** This bug has been marked as a duplicate of bug 748196 ***