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 486675 - crash in Email: Internet Connection lost...
crash in Email: Internet Connection lost...
Status: RESOLVED DUPLICATE of bug 364700
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-14 20:21 UTC by vlad76
Modified: 2007-10-22 22:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description vlad76 2007-10-14 20:21:43 UTC
What were you doing when the application crashed?
Internet Connection lost when Evolution send/receives emails


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 136937472 vsize: 136937472 resident: 25694208 share: 18112512 rss: 25694208 rss_rlim: 4294967295
CPU usage: start_time: 1192393030 rtime: 134 utime: 119 stime: 15 cutime:1 cstime: 2 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208875296 (LWP 3002)]
[New Thread -1273373808 (LWP 3073)]
[New Thread -1262883952 (LWP 3072)]
[New Thread -1252000880 (LWP 3071)]
[New Thread -1219740784 (LWP 3037)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208875296 (LWP 3002))

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


----------- .xsession-errors ---------------------
GTK Panel of SCIM 1.4.5
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.5
Impossibile aprire il file .desktop «/usr/share/applications/openoffice.org-1.9-writer.desktop» per l'icona di avvio: No such file or directory
Impossibile aprire il file .desktop «/usr/share/applications/openoffice.org-1.9-impress.desktop» per l'icona di avvio: No such file or directory
Impossibile aprire il file .desktop «/usr/share/applications/openoffice.org-1.9-calc.desktop» per l'icona di avvio: No such file or directory
CalDAV Eplugin starting up ...
** (evolution:3002): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3002): DEBUG: mailto URL program: evolution
(evolution:3002): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3002): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3002): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 Akhil Laddha 2007-10-16 05:34:08 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful
in determining the cause of the crash. Could you please install some debugging
packages [1] and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the "details", now
containing way more information. Please copy that stacktrace and paste it as a
comment here.  Thanks!


[1] debugging packages for evolution, evolution-data-server and gtkhtml,
    plus debugging packages for some basic GNOME libs. More details can
    be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Comment 2 Tobias Mueller 2007-10-22 22:21:18 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 ***