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 763680 - Totem:ERROR:totem-grilo.c:700:browse_cb: code should not be reached
Totem:ERROR:totem-grilo.c:700:browse_cb: code should not be reached
Status: RESOLVED DUPLICATE of bug 730028
Product: totem
Classification: Core
Component: general
3.19.x
Other Linux
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-03-15 13:00 UTC by Olivier Fourdan
Modified: 2016-03-15 13:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Olivier Fourdan 2016-03-15 13:00:11 UTC 
Description:

Trying to run totem from curent git raises the following error:

  Totem:ERROR:totem-grilo.c:700:browse_cb: code should not be reached
  Aborted (core dumped)

How reproducible:

100% reproducible in both X11 and Wayland

Step to reproduce:

1. Run totem

Actual result:

Totem:ERROR:totem-grilo.c:700:browse_cb: code should not be reached
Aborted (core dumped)

Expected result:

No crash

Additional data:

The totem window appears for a short time.

(gdb) bt

+ Trace 236084

  • #0 raise
    from /lib64/libc.so.6
  • #1 abort
    from /lib64/libc.so.6
  • #2 g_assertion_message
    at gtestutils.c line 2429
  • #3 g_assertion_message_expr
    at gtestutils.c line 2452
  • #4 browse_cb
    at totem-grilo.c line 700
  • #5 queue_process
    at grl-source.c line 2095
  • #6 g_main_dispatch
    at gmain.c line 3154
  • #7 g_main_context_dispatch
    at gmain.c line 3769
  • #8 g_main_context_iterate
    at gmain.c line 3840
  • #9 g_main_context_iteration
    at gmain.c line 3901
  • #10 g_application_run
    at gapplication.c line 2381
  • #11 main
    at totem.c line 83 






Comment 1


Bastien Nocera





          2016-03-15 13:06:09 UTC
        



Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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






Comment 2


Olivier Fourdan





          2016-03-15 13:17:33 UTC
        



Indeed https://bugzilla.gnome.org/show_bug.cgi?id=730028#c12 fixed the problem:

tracker-control -r
tracker-control -s