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 623981 - tracker-extract crashed with SIGSEGV in strtol()
tracker-extract crashed with SIGSEGV in strtol()
Status: RESOLVED INCOMPLETE
Product: tracker
Classification: Core
Component: General
0.8.x
Other Linux
: Normal critical
: ---
Assigned To: tracker-general
Jamie McCracken
Depends on:
Blocks:
 
 
Reported: 2010-07-09 19:29 UTC by Pedro Villavicencio
Modified: 2010-08-26 04:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pedro Villavicencio 2010-07-09 19:29:45 UTC
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/tracker/+bug/603527

"It crashes on start up after about 5secs after seeing the desktop load"

".

Thread 1 (process 1839)

  • #0 *__GI_____strtol_l_internal
    at strtol_l.c line 298
  • #1 *__GI_strtol
    at strtol.c line 110
  • #2 extract_mp3
  • #3 get_file_metadata
  • #4 tracker_extract_get_metadata
  • #5 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #6 _dbus_object_tree_dispatch_and_unlock
    at dbus-object-tree.c line 856
  • #7 dbus_connection_dispatch
    at dbus-connection.c line 4485
  • #8 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #9 g_main_context_dispatch
    at /build/buildd/glib2.0-2.25.10/glib/gmain.c line 2044
  • #10 g_main_context_iterate
    at /build/buildd/glib2.0-2.25.10/glib/gmain.c line 2675
  • #11 g_main_loop_run
    at /build/buildd/glib2.0-2.25.10/glib/gmain.c line 2883
  • #12 main
    at tracker-main.c line 468

Comment 1 Aleksander Morgado 2010-07-14 14:52:56 UTC
Would it be possible to get this MP3 file which triggers the issue? Email is fine.

"/media/Data 2 (Large)_/Shared/Music/Music/Compilations/101 Running Songs/80 Can't Stop Moving.mp3"
Comment 2 Akhil Laddha 2010-08-26 04:52:45 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!