Bug 554610 – crash in Evolution Mail and Calendar: Anlage eines neuen Kalen...

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 554610 - crash in Evolution Mail and Calendar: Anlage eines neuen Kalen...


Summary:	crash in Evolution Mail and Calendar: Anlage eines neuen Kalen...


Status:	RESOLVED DUPLICATE of bug 548396

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.22.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-10-01 20:13 UTC by bodmenke3
Modified:	2008-10-03 04:25 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description bodmenke3 2008-10-01 20:13:18 UTC

What were you doing when the application crashed?
Anlage eines neuen Kalenders


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-486 #1 Fri Jul 18 17:03:35 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Mist

Memory status: size: 105103360 vsize: 105103360 resident: 44584960 share: 21725184 rss: 44584960 rss_rlim: 4294967295
CPU usage: start_time: 1222891793 rtime: 821 utime: 768 stime: 53 cutime:4 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

[Thread debugging using libthread_db enabled]
[New Thread 0xb6661b80 (LWP 8256)]
[New Thread 0xb4422b90 (LWP 8387)]
[New Thread 0xb5c2eb90 (LWP 8357)]
[New Thread 0xb3c21b90 (LWP 8335)]
[New Thread 0xb4c23b90 (LWP 8287)]
0xb7f5e430 in __kernel_vsyscall ()

+ Trace 207621

Thread 1 (Thread 0xb6661b80 (LWP 8256))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /tmp/buildd/glib2.0-2.16.5/glib/gspawn.c line 374
#3 IA__g_spawn_command_line_sync
at /tmp/buildd/glib2.0-2.16.5/glib/gspawn.c line 682
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 segv_redirect
at main.c line 519
#7 <signal handler called>
#8 connection_listen_cb
at e-component-listener.c line 48
#9 ??
from /usr/lib/libORBit-2.so.0
#10 ??
#11 ??
#12 ??
from /usr/lib/libORBit-2.so.0
#13 ??
from /usr/lib/libORBit-2.so.0
#14 ??
#15 ??
#16 ??
#17 ??
from /usr/lib/libORBit-2.so.0
#18 ??
#19 ??
#20 ??
#21 ??
from /usr/lib/libORBit-2.so.0
#22 ??
#23 ??
#24 ??
from /usr/lib/libORBit-2.so.0
#25 ??
from /usr/lib/libglib-2.0.so.0
#26 ??
#27 ??
#28 ??
#29 g_idle_dispatch
at /tmp/buildd/glib2.0-2.16.5/glib/gmain.c line 4090
#0 __kernel_vsyscall



----------- .xsession-errors (23 sec old) ---------------------
QComboBox::insertItem: (unnamed) Index 5 out of range
QComboBox::insertItem: (unnamed) Index 5 out of range
QComboBox::insertItem: (unnamed) Index 5 out of range
QComboBox::insertItem: (unnamed) Index 5 out of range
QComboBox::insertItem: (unnamed) Index 5 out of range
DCOP aborting call from 'anonymous-7901' to 'knotify'
KCrash: Application 'knotify' crashing...
Fenstermanager-Warnung:Ungültiges WM_TRANSIENT_FOR-Fenster 0x66 festgelegt für 0x2c0000b (KNotify - ).
QObject::disconnect: Unexpected null parameter
QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * )
evolution-shell-Message: Killing old version of evolution-data-server...
evolution-shell-Message: Killing old version of evolution-data-server...
evolution-shell-Message: Killing old version of evolution-data-server...
calendar-gui-Message: Check if default client matches (1193412436.11172.8@Bodo1 1193412436.11172.8@Bodo1)
calendar-gui-Message: Check if default client matches (1195206520.13187.5@Bodo1 1222891944.8256.0@Bodo1)
--------------------------------------------------

Comment 1 Akhil Laddha 2008-10-03 04:25:10 UTC

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.

*** This bug has been marked as a duplicate of 548396 ***