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 548957 - crash in Epiphany Web Browser: pressed the Larger butto...
crash in Epiphany Web Browser: pressed the Larger butto...
Status: RESOLVED DUPLICATE of bug 525357
Product: epiphany
Classification: Core
Component: [obsolete] BugBuddyBugs
2.22.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-22 07:39 UTC by sasch
Modified: 2008-08-23 13:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description sasch 2008-08-22 07:39:43 UTC
Version: 2.22.3

What were you doing when the application crashed?
pressed the Larger button to enlarge the font on the page.		


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-486 #1 Fri Aug 8 18:05:01 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 167968768 vsize: 167968768 resident: 54022144 share: 22978560 rss: 54022144 rss_rlim: 4294967295
CPU usage: start_time: 1219390657 rtime: 356 utime: 334 stime: 22 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b2a700 (LWP 8003)]
[New Thread 0xb1cefb90 (LWP 8014)]
[New Thread 0xb24f9b90 (LWP 8012)]
[New Thread 0xb2cfab90 (LWP 8011)]
[New Thread 0xb3dcbb90 (LWP 8009)]
[New Thread 0xb4dcdb90 (LWP 8008)]
[New Thread 0xb45ccb90 (LWP 8007)]
[New Thread 0xb5b16b90 (LWP 8004)]
(no debugging symbols found)
0xb7f0d430 in __kernel_vsyscall ()


----------- .xsession-errors (12 sec old) ---------------------
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
--------------------------------------------------
Comment 1 Reinout van Schouwen 2008-08-23 13:32:22 UTC
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 525357 ***