evolution crashed with SIGSEGV in g_type_check_instance_cast()

Bug #207746 reported by Marc Rabell
8
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: evolution

I wasn't doing anything special. It just crashed while idle.

It was open for about 2 days. Memory is OK, so don't know which could be the problem...

ProblemType: Crash
Architecture: i386
Date: Thu Mar 27 15:04:53 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/evolution
Package: evolution 2.22.0-0ubuntu2
PackageArchitecture: i386
ProcCmdline: evolution --sm-config-prefix /evolution-eib8xt/ --sm-client-id 117f000001000120654301000000058390003 --screen 0
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=ca_ES.UTF-8@valencia
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 g_type_check_instance_cast ()
 ?? () from /usr/lib/gtk-2.0/2.10.0/filesystems/libgio.so
 ?? ()
 ?? ()
 pthread_mutex_lock ()
Title: evolution crashed with SIGSEGV in g_type_check_instance_cast()
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video

Tags: apport-crash
Revision history for this message
Marc Rabell (m-rabell) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:volumes_drives_changed (volume_monitor=0x8aaab08, volume=0x8a7a2c0, user_data=0x82f2120)
IA__g_cclosure_marshal_VOID__OBJECT (closure=0x8e8d7e0, return_value=0x0, n_param_values=2,
IA__g_closure_invoke (closure=0x8e8d7e0, return_value=0x0, n_param_values=2,
signal_emit_unlocked_R (node=0x8da3f50, detail=0, instance=0x8aaab08, emission_return=0x0,
IA__g_signal_emit_valist (instance=0xb45091dc, signal_id=661, detail=0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in evolution:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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

Changed in evolution:
status: New → 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.