first time after restart evolution crached. Second start was OK

Bug #102198 reported by bAmbAm
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

first time after restart system evolution crached. Second start was OK

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Apr 3 04:49:07 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/evolution-2.10
Package: evolution 2.10.0-0ubuntu2
PackageArchitecture: i386
ProcCmdline: evolution --component=mail
ProcCwd: /home/bambam
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 g_main_context_check () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Uname: Linux bambam-desktop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: likely-dup
Revision history for this message
bAmbAm (bambam-venom-project) wrote :
Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:g_main_context_iterate (context=0x8092088, block=1, dispatch=1, self=0x8067268) at gmain.c:2674
IA__g_main_loop_run (loop=0x80c35b8) at gmain.c:2881
bonobo_main () at bonobo-main.c:311
main (argc=2, argv=0xbff629e4) at main.c:611

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Daniel Holbach (dholbach) wrote :

I've seen that or a similar backtrace before. Marking 'likely-dup'.

Changed in evolution:
status: Unconfirmed → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you still get the issue on gutsy?

Changed in evolution:
status: Confirmed → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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!.

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