Version: 2.14.3

What were you doing when the application crashed?
trying to figure out why synaptic won't load


Distribution: Debian lenny/sid
Gnome Release: 2.18.2 2007-05-28 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.18-4-486 #1 Mon Mar 26 16:39:10 UTC 2007 i586
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 105508864 vsize: 105508864 resident: 42995712 share: 23339008 rss: 42995712 rss_rlim: 4294967295
CPU usage: start_time: 1184011945 rtime: 173411 utime: 153951 stime: 19460 cutime:5 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/epiphany'

(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 -1241769760 (LWP 6602)]
(no debugging symbols found)
0xb6f50b11 in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 146847

----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
LoadPlugin: failed to initialize shared library /usr/lib/totem/libtotem-complex-plugin.so [/usr/lib/totem/libtotem-complex-plugin.so: undefined symbol: _ZN13nsTArray_base9sEmptyHdrE]
Window manager warning: last_user_time (3079025712) is greater than comparison timestamp (2904320496).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x2c00091 (Synaptic) appears to be one of the offending windows with a timestamp of 3079025712.  Working around...

(time-admin:9993): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Window manager warning: last_user_time (3079742512) is greater than comparison timestamp (2904351801).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x2c00003 (Time and D) appears to be one of the offending windows with a timestamp of 3079742512.  Working around...
Failed to read a valid object file image from memory.
--------------------------------------------------