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 469529 - crash in Evolution: Distribution: Mandriva L...
crash in Evolution: Distribution: Mandriva L...
Status: RESOLVED DUPLICATE of bug 364700
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-23 10:15 UTC by poligraphijus
Modified: 2007-09-24 18:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description poligraphijus 2007-08-23 10:15:30 UTC 
What were you doing when the application crashed?
Distribution: Mandriva Linux release 2007.1 (Official) for i586
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-13mdvlegacy #1 SMP Fri Mar 23 19:05:24 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Orange
Icon Theme: gnome

Memory status: size: 103514112 vsize: 103514112 resident: 28614656 share: 17379328 rss: 28614656 rss_rlim: 4294967295
CPU usage: start_time: 1187859586 rtime: 111 utime: 101 stime: 10 cutime:1 cstime: 3 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/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1237522720 (LWP 12111)]
[New Thread -1283634272 (LWP 12147)]
[New Thread -1275241568 (LWP 12146)]
[New Thread -1254372448 (LWP 12131)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 157325

Thread 1 (Thread -1237522720 (LWP 12111))

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


----------- .xsession-errors ---------------------
skipping package kernel-legacy-latest-2.6.17-14mdv.i586
skipping package kernel-source-latest-2.6.17-14mdv.i586
skipping package kernel-source-latest-2.6.17-13mdv.i586
skipping package kernel-source-stripped-latest-2.6.17-13mdv.i586
skipping package kernel-source-stripped-latest-2.6.17-14mdv.i586
skipping package kernel-xen0-latest-2.6.17-13mdv.i586
skipping package kernel-xen0-latest-2.6.17-14mdv.i586
skipping package kernel-xenU-latest-2.6.17-14mdv.i586
skipping package kernel-xenU-latest-2.6.17-13mdv.i586
unlocking urpmi database
getting lock on urpmi
getting exclusive lock on rpm
retrieving rpm files from medium "main_updates"...
warning: .dynamic section for "/usr/lib/libhal.so.1" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-24 18:53:56 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 ***