tracker-applet crashed with SIGSEGV in g_closure_invoke()

Bug #269280 reported by Vivian Stewart
166
This bug affects 8 people
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Invalid
Medium
Unassigned
Declined for Intrepid by Sebastien Bacher

Bug Description

Binary package hint: tracker

I right clicked on the tracker icon in system tray and selected preferences then changed the "automatically pause all indexing if ..." to "automatically pause indexing if ..."

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/tracker-applet
NonfreeKernelModules: nvidia
Package: tracker-search-tool 0.6.6-1ubuntu4
ProcAttrCurrent: unconfined
ProcCmdline: tracker-applet
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: tracker
StacktraceTop:
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: tracker-applet crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.26-1-rt x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

Tags: apport-crash
Revision history for this message
Vivian Stewart (vivichrist) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:signal_emit_unlocked_R (node=0x27569e0, detail=0, instance=0x229d430, emission_return=0x0,
IA__g_signal_emit_valist (instance=0x229d430, signal_id=<value optimized out>, detail=0,
IA__g_signal_emit (instance=0x7f76afab0f80, signal_id=0, detail=35976352)
gtk_real_button_released (button=0x7f76afab0f80)
IA__g_closure_invoke (closure=0x2757a30, return_value=0x0, n_param_values=1,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in tracker:
importance: Undecided → Medium
Revision history for this message
kseise (kevin-seise) wrote :

I got this one too, although I didn't actually change the pause preferences, just looked at them. Again, AMD64 with update Alpha 6 of 8.10

Revision history for this message
kseise (kevin-seise) wrote :

Still getting this with all updates. Tracker is not indexing all of my files either.

Revision history for this message
Ludovic Claude (ludovicc) wrote :

Same as kseise, I have upgraded Ubuntu to Intrepid beta today

Revision history for this message
Jim Braux-Zin (j-brauxzin) wrote :

Same problem on Intrepid beta. Didn't make any change in the preferences.

Revision history for this message
Matthew McGowan (mmcg069) wrote :

I see this problem too. Ubuntu Ibex x86_64. Tracker in general doesn't seem to be working to well in Ibex for me.

Revision history for this message
Nigel Stolting (nigel-stolting) wrote :

This seems reproducible in the Intrepid beta, whenever the indexing preferences are changed.

Revision history for this message
Alex Lopez (alfitovdkiv) wrote :

I can confirm on beta too. When closing preferences it crashes.

Revision history for this message
Mario Italo (marioitalo) wrote :

Same problem here. Intrepid Ibex Final amd64.

Revision history for this message
Christian Roessner (christian-roessner-net) wrote :

Can confirm on jaunty - last updated on 2009-01-25. Just looking at prefs. Doing nothing except clicking on close.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try on current jaunty?

Revision history for this message
Shane Fagan (shanepatrickfagan) wrote :

Still effects jaunty all updates installed. 03/04/09

Revision history for this message
Matthew McGowan (mmcg069) wrote :

I still see this. I change some settings and after a short while tracker-applet disappears from the panel

Revision history for this message
Haiko von Holten (hholten) wrote :

I observe this bug too on Intrepid. Tracker-Applet preferences dialog results in a "segmentation fault" when hitting the close-button. The entire applet crashes.

Revision history for this message
Haiko von Holten (hholten) wrote :

I can't confirm it on a current (unused/clean) Jaunty!

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thanks Haiko. I'll mark this as fixed. Tracker has changed quite signifcantly in Jaunty so it's quite likely that this crash occurs in obsolete code anyway.

Changed in tracker (Ubuntu):
status: New → Fix Released
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Actually, re-opening as there is an earlier comment saying this still exists on Jaunty.

shane - are you sure it's the same crash? Could you get a backtrace?

Changed in tracker (Ubuntu):
status: Fix Released → Incomplete
Revision history for this message
José Ernesto Dávila Pantoja (josernestodavila) wrote :

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in tracker (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.