Evolution crashes when selecting type of server

Bug #194941 reported by setlord on 2008-02-24
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: evolution

I'm using Hardy Alpha 4, fresh install. When I'm in the second step of the assistant for new account, I mean, when I'm selecting type of server I'm using, the application crashes.

ProblemType: Crash
Architecture: i386
Date: Sat Feb 23 22:57:48 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: cdrom
Package: evolution 2.21.91-0ubuntu1
PackageArchitecture: i386
ProcCmdline: evolution --component=mail
ProcCwd: /home/aquiroz
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 g_type_check_instance_is_a ()
 g_file_get_path () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/gtk-2.0/2.10.0/filesystems/libgio.so
 ?? ()
 ?? ()
Title: evolution crashed with SIGSEGV in g_type_check_instance_is_a()
Uname: Linux bagheera 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev scanner tape vboxusers video

setlord (quiroz-alonso) wrote :

StacktraceTop:IA__g_type_check_instance_is_a (type_instance=0x8191a50, iface_type=137029136)
IA__g_file_get_path (file=0x8191a50) at /build/buildd/glib2.0-2.15.5/gio/gfile.c:396
get_icon_string (icon=0x83ef660) at gtkfilesystemgio.c:789
IA__gtk_file_system_volume_get_icon_name (file_system=0xb510acc8, volume=0x8134b28,
IA__gtk_file_system_volume_render_icon (file_system=0xb510acc8, volume=0x8134b28,

Changed in evolution:
importance: Undecided → Medium
Pedro Villavicencio (pedro) wrote :

Is this reproducible with latest package?

Changed in evolution:
status: New → Incomplete
Pedro Villavicencio (pedro) 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 evolution:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers