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 360585 - crash in Evolution: While using a Search Fol...
crash in Evolution: While using a Search Fol...
Status: RESOLVED DUPLICATE of bug 359520
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-10-08 09:40 UTC by Jeremy Visser
Modified: 2006-10-10 23:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Jeremy Visser 2006-10-08 09:40:32 UTC 
What were you doing when the application crashed?
While using a Search Folder for a mailing list, with threaded messages and vertical layout enabled, Evolution 2.8 (Ubuntu Edgy) crashed and I was prompted to write this bug report.


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

Memory status: size: 90750976 vsize: 0 resident: 90750976 share: 0 rss: 25546752 rss_rlim: 0
CPU usage: start_time: 1160300347 rtime: 0 utime: 208 stime: 0 cutime:194 cstime: 0 timeout: 14 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 -1233385808 (LWP 7321)]
[New Thread -1283830880 (LWP 7328)]
[New Thread -1261474912 (LWP 7326)]
[New Thread -1252586592 (LWP 7325)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 75195







Comment 1


Elijah Newren





          2006-10-08 12:52:03 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.







Comment 2


Jeremy Visser





          2006-10-08 22:49:29 UTC
        



Ok, I'm very new to debugging stuff and C programming in general, so bear with me.

In gdb, typing "thread apply all bt" gave me this, which is very similar to the output before, so I'm not sure if I've done the right thing:





+
Trace
    75336






Thread 1
          (Thread -1233152336 (LWP 6863))


    

  • 
#0
em_folder_browser_new

    
                from
                /usr/lib/evolution/2.8/components/libevolution-mail.so

    

    • 

  • 
#1
e_filter_bar_get_type

    
                from
                /usr/lib/evolution/2.8/libefilterbar.so.0

    

    • 

  • 
#2
g_object_set_valist

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

    

    • 

  • 
#3
g_object_set

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

    

    • 

  • 
#4
em_folder_browser_new

    
                from
                /usr/lib/evolution/2.8/components/libevolution-mail.so

    

    • 

  • 
#5
em_folder_utils_copy_folder

    
                from
                /usr/lib/evolution/2.8/components/libevolution-mail.so

    

    • 

  • 
#6
mail_call_main

    
                from
                /usr/lib/evolution/2.8/components/libevolution-mail.so

    

    • 

  • 
#7
mail_call_main

    
                from
                /usr/lib/evolution/2.8/components/libevolution-mail.so

    

    • 

  • 
#8
g_io_channel_unix_get_fd

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

    

    • 

  • 
#9
g_main_context_dispatch

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

    

    • 

  • 
#10
g_main_context_check

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

    

    • 

  • 
#11
g_main_loop_run

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

    

    • 

  • 
#12
bonobo_main

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

    

    • 

  • 
#13
main

    • 








**********************************************

Before I typed "thread apply all bt", gdb gave me this, which ended in a segfault (Evolution, not gdb):

(evolution-2.8:6863): e-utils-WARNING **: Plugin 'Bogofilter junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0'
(no debugging symbols found)
(no debugging symbols found)
** (evolution-2.8:6863): DEBUG: mailto URL command: evolution %s
** (evolution-2.8:6863): DEBUG: mailto URL program: evolution
(no debugging symbols found)
[New Thread -1252398176 (LWP 6878)]
(no debugging symbols found)
[Thread -1252398176 (LWP 6878) exited]
[New Thread -1261286496 (LWP 6881)]
[New Thread -1252398176 (LWP 6882)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1283687520 (LWP 6884)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1233152336 (LWP 6863)]
0xb584bb77 in em_folder_browser_new ()
   from /usr/lib/evolution/2.8/components/libevolution-mail.so

**********************************************

Does that mean that I did not do some "debug" mode? Can you help me out here?

Anyway, thanks for responding so quickly!






Comment 3


Elijah Newren





          2006-10-09 00:17:35 UTC
        



Sweet, thanks for following up.  Lines like
  (no debugging symbols found)
and
  [New Thread -1252398176 (LWP 6878)]
when gdb is startup up are not useful, but the warning you copied might be.  The stack trace does indeed look like the one bug-buddy grabbed for you previously.  Can you installed debugging packages (for evolution, evolution-data-server, gtk2, libglib2, gnome-vfs2, and libgnomeui) from edgy and then get a new stack trace?  That ought to provide a lot more information.






Comment 4


Jeremy Visser





          2006-10-10 03:18:22 UTC
        



OK, the following looks a lot more helpful. It even mentions the names of some of my search folders:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1233275216 (LWP 9772)]
emfb_search_config_search (efb=0x8529830, rule=0x49, id=-1, 
    query=0x84103d0 "Advanced Search", data=0x841f000)
    at em-folder-browser.c:742
742     em-folder-browser.c: No such file or directory.
        in em-folder-browser.c
(gdb) thread apply all bt





+
Trace
    75541






Thread 1
          (Thread -1233275216 (LWP 9772))


    

  • 
#0
emfb_search_config_search

    
                at em-folder-browser.c
                  line
                  742

    

    • 

  • 
#1
set_property

    
                at e-filter-bar.c
                  line
                  722

    

    • 

  • 
#2
IA__g_object_set_valist

    
                at gobject.c
                  line
                  697

    

    • 

  • 
#3
IA__g_object_set

    
                at gobject.c
                  line
                  1207

    

    • 

  • 
#4
emfb_set_folder

    
                at em-folder-browser.c
                  line
                  1883

    

    • 

  • 
#5
emfv_got_folder

    
                at em-folder-view.c
                  line
                  691

    

    • 

  • 
#6
get_folder_got

    
                at mail-ops.c
                  line
                  1230

    

    • 

  • 
#7
mail_msgport_replied

    
                at mail-mt.c
                  line
                  461

    

    • 

  • 
#8
g_io_unix_dispatch

    • 

  • 
#9
IA__g_main_context_dispatch

    
                at gmain.c
                  line
                  2045

    

    • 

  • 
#10
g_main_context_iterate

    
                at gmain.c
                  line
                  2677

    

    • 

  • 
#11
IA__g_main_loop_run

    
                at gmain.c
                  line
                  2881

    

    • 

  • 
#12
bonobo_main

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

    

    • 

  • 
#13
main

    
                at main.c
                  line
                  615

    

    • 








P.S.: All this information is rather long. Would you rather me put it in a pastebin or would you rather archive it in Bugzilla?






Comment 5


Elijah Newren





          2006-10-10 03:23:16 UTC
        



Awesome, thanks for the extra information.  From thread 1 it looks like it's probably a duplicate of bug 359520 but I'll let an evolution maintainer verify.






Comment 6


Karsten Bräckelmann





          2006-10-10 18:27:53 UTC
        



Elijah, yes it is.

Thanks for all your efforts and the good stacktrace, Jeremy. :)


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






Comment 7


Jeremy Visser





          2006-10-10 23:29:10 UTC
        



Ah, good. I'm glad people know what the problem is.