GNOME Bugzilla – Bug 463456
crash in Tasks: I was configuring an LDA...
Last modified: 2007-08-10 18:53:10 UTC
Version: 2.10 What were you doing when the application crashed? I was configuring an LDAP server. I had just deleted an incorrect search base from the text box and pressed OK. Then it crashed and the bug buddy interface was displayed. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 127389696 vsize: 127389696 resident: 47558656 share: 32993280 rss: 47558656 rss_rlim: 4294967295 CPU usage: start_time: 1186246236 rtime: 1524 utime: 1425 stime: 99 cutime:0 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 -1209092384 (LWP 21834)] [New Thread -1230652528 (LWP 21867)] [New Thread -1241142384 (LWP 21866)] [New Thread -1219748976 (LWP 21853)] (no debugging symbols found) 0x00d27402 in __kernel_vsyscall ()
+ Trace 152798
Thread 1 (Thread -1209092384 (LWP 21834))
----------- .xsession-errors (114 sec old) --------------------- new dimensions = (48,48) we need to scale up scale = 1 index:0 new dimensions = (48,48) initial setting of an image. no scaling scale = 1 new dimensions = (48,48) we need to scale up scale = 1 : Old width = 150.000000, New width = 404.000000 : Old width = 404.000000, New width = 453.000000 : Old width = 453.000000, New width = 510.000000 (evolution:21834): e-utils-WARNING **: calling e_icon_factory_get_icon_filename with unknown icon_size value (48) --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 444924 ***