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 547666 - crash in Epiphany Web Browser: Ctrl-+
crash in Epiphany Web Browser: Ctrl-+
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-13 20:13 UTC by neil.hemingway
Modified: 2008-08-13 22:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description neil.hemingway 2008-08-13 20:13:23 UTC
Version: 2.22.3

What were you doing when the application crashed?
Ctrl-+


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

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: Industrial

Memory status: size: 214695936 vsize: 214695936 resident: 85385216 share: 25014272 rss: 85385216 rss_rlim: 4294967295
CPU usage: start_time: 1218572025 rtime: 229675 utime: 216039 stime: 13636 cutime:1 cstime: 2 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 0xb6b2e920 (LWP 16900)]
[New Thread 0xb07d3b90 (LWP 29970)]
[New Thread 0xb37d9b90 (LWP 29902)]
[New Thread 0xb1fd6b90 (LWP 28730)]
[New Thread 0xb2fd8b90 (LWP 28729)]
[New Thread 0xb27d7b90 (LWP 16912)]
[New Thread 0xb40a9b90 (LWP 16909)]
[New Thread 0xb50abb90 (LWP 16908)]
[New Thread 0xb48aab90 (LWP 16907)]
[New Thread 0xb5ab6b90 (LWP 16902)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()


----------- .xsession-errors (733658 sec old) ---------------------
[35;01mwarning: Device not found[0m
[31;01merror: Unable to communicate with device (code=12): hp:/par/HP_LaserJet_6L?device=/dev/parport0[0m
[35;01mwarning: Device not found[0m
[31;01merror: Unable to communicate with device (code=12): hp:/par/HP_LaserJet_6L?device=/dev/parport0[0m
[35;01mwarning: Device not found[0m
[31;01merror: Unable to communicate with device (code=12): hp:/par/HP_LaserJet_6L?device=/dev/parport0[0m
[35;01mwarning: Device not found[0m
[31;01merror: Unable to communicate with device (code=12): hp:/par/HP_LaserJet_6L?device=/dev/parport0[0m
[35;01mwarning: Device not found[0m
[31;01merror: Unable to communicate with device (code=12): hp:/par/HP_LaserJet_6L?device=/dev/parport0[0m
[35;01mwarning: Device not found[0m
[31;01merror: Unable to communicate with device (code=12): hp:/par/HP_LaserJet_6L?device=/dev/parport0[0m
[35;01mwarning: Device not found[0m
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Reinout van Schouwen 2008-08-13 22:28:51 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 ***