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 436939 - crash in Evolution: Retreiving mail
crash in Evolution: Retreiving mail
Status: RESOLVED DUPLICATE of bug 373699
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 440886 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-05-08 16:45 UTC by JTorelli3
Modified: 2007-06-11 11:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description JTorelli3 2007-05-08 16:45:32 UTC
What were you doing when the application crashed?
Retreiving mail


Distribution: Mandriva Linux release 2007.1 (Official) for i586
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-13mdv #1 SMP Fri Mar 23 19:03:31 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Amaranth

Memory status: size: 185167872 vsize: 185167872 resident: 23842816 share: 16871424 rss: 23842816 rss_rlim: 4294967295
CPU usage: start_time: 1178642724 rtime: 193 utime: 165 stime: 28 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1237489952 (LWP 5966)]
[New Thread -1371845728 (LWP 5979)]
[New Thread -1363453024 (LWP 5978)]
[New Thread -1354658912 (LWP 5977)]
[New Thread -1293313120 (LWP 5973)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1237489952 (LWP 5966))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #5 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #7 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #8 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (6 sec old) ---------------------
evolution-alarm-notify-Message:  Wed May  9 00:00:00 2007
evolution-alarm-notify-Message:  Tue May  8 12:45:07 2007
Debug: Loading Beagle.Util.Conf+IndexingConfig from indexing.xml
Debug: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml
Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml
(gnome-panel:5729): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 24
SIOCETHTOOL: Operation not permitted
SIOCETHTOOL: Operation not permitted
/home/john/.MdkOnline/mdkonline should be set to TRUE: please use --force or -f option to launch applet at /usr/bin/mdkapplet line 242.
CalDAV Eplugin starting up ...
** (evolution:5966): DEBUG: mailto URL command: evolution %s
** (evolution:5966): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 palfrey 2007-05-09 11:17:04 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!
Comment 2 Susana 2007-05-24 11:34:46 UTC
*** Bug 440886 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2007-06-11 11:55:40 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 373699 ***