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 368719 - crash in Evolution: Deleting Primary Only Ac...
crash in Evolution: Deleting Primary Only Ac...
Status: RESOLVED DUPLICATE of bug 348315
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-11-01 05:44 UTC by crh15
Modified: 2006-11-04 19:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description crh15 2006-11-01 05:44:30 UTC 
What were you doing when the application crashed?
Deleting Primary Only Account (IMAP)


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 212709376 vsize: 0 resident: 212709376 share: 0 rss: 52510720 rss_rlim: 0
CPU usage: start_time: 1162355237 rtime: 0 utime: 4579 stime: 0 cutime:4345 cstime: 0 timeout: 234 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232521552 (LWP 8504)]
[New Thread -1390871648 (LWP 12108)]
[New Thread -1336247392 (LWP 8525)]
[New Thread -1337984096 (LWP 8519)]
[New Thread -1327166560 (LWP 8518)]
[New Thread -1286534240 (LWP 8515)]
[New Thread -1277744224 (LWP 8512)]
[New Thread -1269351520 (LWP 8508)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 81311







Comment 1


Karsten Bräckelmann





          2006-11-01 22:16:35 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


crh15





          2006-11-01 22:59:54 UTC
        



This help?

--Chris


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 199249920 vsize: 0 resident: 199249920 share: 0 rss: 41287680 rss_rlim: 0
CPU usage: start_time: 1162421537 rtime: 0 utime: 1157 stime: 0 cutime:1076 cstime: 0 timeout: 81 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233365328 (LWP 7210)]
[New Thread -1371604064 (LWP 7268)]
[New Thread -1346159712 (LWP 7238)]
[New Thread -1337271392 (LWP 7231)]
[New Thread -1328481376 (LWP 7230)]
[New Thread -1287611488 (LWP 7227)]
[New Thread -1278825568 (LWP 7222)]
[New Thread -1270432864 (LWP 7220)]
0xffffe410 in __kernel_vsyscall ()




+
Trace
    81651






Thread 1
          (Thread -1233365328 (LWP 7210))


    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
waitpid

    
                from
                /lib/tls/i686/cmov/libc.so.6

    

    • 

  • 
#2
gnome_gtk_module_info_get

    
                from
                /usr/lib/libgnomeui-2.so.0

    

    • 

  • 
#3
segv_redirect

    
                at main.c
                  line
                  426

    

    • 

  • 
#4
<signal handler called>

    • 

  • 
#5
camel_folder_summary_content_info_free

    
                from
                /usr/lib/libcamel-provider-1.2.so.8

    

    • 

  • 
#6
camel_message_info_free

    
                from
                /usr/lib/libcamel-provider-1.2.so.8

    

    • 

  • 
#7
camel_vee_store_new

    
                from
                /usr/lib/libcamel-provider-1.2.so.8

    

    • 

  • 
#8
camel_message_info_free

    
                from
                /usr/lib/libcamel-provider-1.2.so.8

    

    • 

  • 
#9
camel_folder_summary_clear

    
                from
                /usr/lib/libcamel-provider-1.2.so.8

    

    • 

  • 
#10
camel_folder_summary_new

    
                from
                /usr/lib/libcamel-provider-1.2.so.8

    

    • 

  • 
#11
camel_object_unref

    
                from
                /usr/lib/libcamel-1.2.so.8

    

    • 

  • 
#12
camel_folder_construct

    
                from
                /usr/lib/libcamel-provider-1.2.so.8

    

    • 

  • 
#13
camel_object_unref

    
                from
                /usr/lib/libcamel-1.2.so.8

    

    • 

  • 
#14
sync_folder_free

    
                at mail-ops.c
                  line
                  1480

    

    • 

  • 
#15
mail_msg_free

    
                at mail-mt.c
                  line
                  193

    

    • 

  • 
#16
mail_msgport_replied

    
                at mail-mt.c
                  line
                  463

    

    • 

  • 
#17
g_io_channel_unix_get_fd

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#18
g_main_context_dispatch

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#19
g_main_context_check

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#20
g_main_loop_run

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#21
bonobo_main

    
                from
                /usr/lib/libbonobo-2.so.0

    

    • 

  • 
#22
main

    
                at main.c
                  line
                  615

    

    • 

  • 
#0
__kernel_vsyscall

    • 













Comment 3


Karsten Bräckelmann





          2006-11-04 19:20:57 UTC
        



Yes, this helps, thanks Chris! :)


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