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 463289 - crash in Evolution: Sending/Receiving Mail
crash in Evolution: Sending/Receiving Mail
Status: RESOLVED DUPLICATE of bug 364700
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-03 23:41 UTC by kary.plain
Modified: 2007-09-24 20:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description kary.plain 2007-08-03 23:41:12 UTC
What were you doing when the application crashed?
Sending/Receiving 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: Mist
Icon Theme: Mist

Memory status: size: 132820992 vsize: 132820992 resident: 25624576 share: 16232448 rss: 25624576 rss_rlim: 4294967295
CPU usage: start_time: 1186184443 rtime: 77 utime: 69 stime: 8 cutime:3 cstime: 1 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 -1237575968 (LWP 8451)]
[New Thread -1308628064 (LWP 8498)]
[New Thread -1300235360 (LWP 8497)]
[New Thread -1270850656 (LWP 8475)]
[New Thread -1261917280 (LWP 8474)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1237575968 (LWP 8451))

  • #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 ---------------------
** (evolution:8212): DEBUG: mailto URL program: evolution
getting exclusive lock on urpmi
unlocking urpmi database
medium "main_updates" is up-to-date
medium "contrib_updates" is up-to-date
getting exclusive lock on urpmi
unlocking urpmi database
medium "main_updates" is up-to-date
    ftp://mirrors.usc.edu/pub/linux/distributions/mandrakelinux/official/2007.1/i586/media/contrib/updates/media_info/hdlist.cz
        0% of 5131k completed, ETA = 1:08:49, speed = 1272                     
        10% of 5131k completed, ETA = 0:00:17, speed = 642k                    
        26% of 5131k completed, ETA = 0:
Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:8451): DEBUG: mailto URL command: evolution %s
** (evolution:8451): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 Pascal Terjan 2007-08-08 22:15:18 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 and reopen this bug or report a new one. Thanks in advance!
Comment 2 Tobias Mueller 2007-09-24 20:07:16 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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