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 463464 - crash in Evolution: Aprendo in menù modifica...
crash in Evolution: Aprendo in menù modifica...
Status: RESOLVED DUPLICATE of bug 426496
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-04 17:53 UTC by ruggeroferrari
Modified: 2007-08-17 08:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description ruggeroferrari 2007-08-04 17:53:10 UTC 
What were you doing when the application crashed?
Aprendo in menù modifica la voce "preference" 


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.3 2007-04-12 (SUSE)
BugBuddy Version: 2.18.1

System: Linux 2.6.18.8-0.5-default #1 SMP Fri Jun 22 12:17:53 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70199902
Selinux: No
Accessibility: Enabled
GTK+ Theme: Synchronicity
Icon Theme: Tango

Memory status: size: 632758272 vsize: 632758272 resident: 27070464 share: 23973888 rss: 51044352 rss_rlim: 838630400
CPU usage: start_time: 1186234404 rtime: 778 utime: 718 stime: 60 cutime:31 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47422751092048 (LWP 14901)]
[New Thread 1141147968 (LWP 14921)]
[New Thread 1132755264 (LWP 14920)]
[New Thread 1124362560 (LWP 14919)]
[New Thread 1115969856 (LWP 14918)]
[New Thread 1107577152 (LWP 14917)]
[New Thread 1099184448 (LWP 14916)]
[New Thread 1098918208 (LWP 14915)]
[New Thread 1082132800 (LWP 14914)]
[New Thread 1090525504 (LWP 14909)]
0x00002b21752cbc5f in waitpid () from /lib64/libpthread.so.0

+ Trace 152804

Thread 1 (Thread 47422751092048 (LWP 14901))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 html_cluev_type_init
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #5 html_cluev_type_init
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #6 html_object_calc_size
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #7 html_engine_calc_size
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #8 html_engine_redraw_selection
    from /usr/lib64/libgtkhtml-3.14.so.19
  • #9 g_main_context_dispatch
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #10 g_main_context_iterate
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #12 bonobo_main
    from /opt/gnome/lib64/libbonobo-2.so.0
  • #13 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors ---------------------
QClipboard: Unknown SelectionClear event received.
QDate::setYMD: Invalid date 0000-00-00
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x22061e4
(evolution-2.10:14901): Gtk-CRITICAL **: gtk_file_system_unix_get_parent: assertion `g_path_is_absolute (filename)' failed
(evolution-2.10:14901): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
--------------------------------------------------
Comment 1 André Klapper 2007-08-17 08:35:08 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 426496 ***