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 544064 - crash in Evolution Mail and Calendar: I close Evolution
crash in Evolution Mail and Calendar: I close Evolution
Status: RESOLVED DUPLICATE of bug 541872
Product: evolution-rss
Classification: Other
Component: general
0.0.1
Other All
: High critical
: ---
Assigned To: evolution-rss-maint
evolution-rss-maint
Depends on:
Blocks:
 
 
Reported: 2008-07-21 22:02 UTC by Joaquin Martinez Gadea
Modified: 2008-08-01 01:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Joaquin Martinez Gadea 2008-07-21 22:02:31 UTC 
What were you doing when the application crashed?
I close Evolution


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

System: Linux 2.6.25-2-vserver-amd64 #1 SMP Mon Jul 14 11:35:37 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Mist

Memory status: size: 568172544 vsize: 568172544 resident: 54202368 share: 29474816 rss: 54202368 rss_rlim: 18446744073709551615
CPU usage: start_time: 1216677611 rtime: 266 utime: 252 stime: 14 cutime:2 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 0x7f7d7be9e7a0 (LWP 6651)]
[New Thread 0x40a32950 (LWP 6732)]
0x00007f7d77741edf in waitpid () from /lib/libpthread.so.0

+ Trace 203436

Thread 1 (Thread 0x7f7d7be9e7a0 (LWP 6651))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.3/glib/gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.3/glib/gspawn.c line 682
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 216
  • #5 <signal handler called>
  • #6 ??
  • #7 AppendAndRemoveThread
    at ../../dist/include/xpcom/nsAutoPtr.h line 972
  • #8 PL_DHashTableEnumerate
  • #9 nsThreadManager::Shutdown
    at ../../dist/include/xpcom/nsBaseHashtable.h line 221
  • #10 NS_ShutdownXPCOM_P
    at nsXPComInit.cpp line 774
  • #11 XRE_TermEmbedding
    at nsEmbedFunctions.cpp line 160
  • #12 EmbedPrivate::PopStartup
    at EmbedPrivate.cpp line 565
  • #13 gecko_shutdown
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-evolution-rss.so
  • #14 exit
    from /lib/libc.so.6
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 _start
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (9 sec old) ---------------------
QObject::disconnect: Unexpected null parameter
QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * )
Advertencia del gestor de ventanas: WM_TRANSIENT_FOR inválido para la ventana 0x65 especificada para 0x1400b71 ().
ICE default IO error handler doing an exit(), pid = 6017, errno = 11
ICE default IO error handler doing an exit(), pid = 6060, errno = 11
Advertencia del gestor de ventanas: WM_TRANSIENT_FOR inválido para la ventana 0x65 especificada para 0x1402246 ().
closing
Advertencia del gestor de ventanas: WM_TRANSIENT_FOR inválido para la ventana 0x65 especificada para 0x300000d (scribus).
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:6651): DEBUG: mailto URL command: evolution %s
** (evolution:6651): DEBUG: mailto URL program: evolution
calendar-gui-Message: Check if default client matches (1216161158.29681.7@debian 1216161158.29681.10@debian)
RSS Plugin enabled (evolution 2.22, evolution-rss 0.1.0)
RSS: cleaning all remaining sessions ...done
--------------------------------------------------
Comment 1 Akhil Laddha 2008-07-22 04:21:31 UTC 
could be related to bug 541872
Comment 2 Bharath Acharya 2008-08-01 01:07:36 UTC 
This is a dup of bug 541872

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