GNOME Bugzilla – Bug 551329
crash in Document Viewer: opening a pdf in iceweas...
Last modified: 2008-09-20 17:39:40 UTC
Version: 2.22.2 What were you doing when the application crashed? opening a pdf in iceweasel Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Tenebrific Icon Theme: HighContrast Memory status: size: 310439936 vsize: 310439936 resident: 37318656 share: 14004224 rss: 37318656 rss_rlim: 18446744073709551615 CPU usage: start_time: 1220863469 rtime: 232 utime: 142 stime: 90 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7fb199d09780 (LWP 4066)] [New Thread 0x40fde950 (LWP 4067)] 0x00007fb192e61d96 in poll () from /lib/libc.so.6
+ Trace 206478
Thread 2 (Thread 0x40fde950 (LWP 4067))
----------- .xsession-errors (7 sec old) --------------------- Unable to create /home/shegeek/.dbus/session-bus SESSION_MANAGER=local/xmaspresent:/tmp/.ICE-unix/3756 ** Message: another SSH agent is running at: /tmp/ssh-ohlYIr3756/agent.3756 ** (gnome-settings-daemon:3815): WARNING **: Error in setting vertical scroll ** (gnome-settings-daemon:3815): WARNING **: Error in setting horizontal scroll xrdb: "*Label.background" on line 220 overrides entry on line 150 xrdb: "*Text.background" on line 226 overrides entry on line 191 xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 ** (gnome-panel:3832): CRITICAL **: panel_applet_frame_change_background: assertion `PANEL_IS_WIDGET (GTK_WIDGET (frame)->parent)' failed Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 542574 ***