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 546715 - crash in Epiphany Web Bookmarks: again a "ctrl +" crash
crash in Epiphany Web Bookmarks: again a "ctrl +" crash
Status: RESOLVED DUPLICATE of bug 546713
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-07 05:10 UTC by epiphany-ftw
Modified: 2008-08-07 08:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description epiphany-ftw 2008-08-07 05:10:47 UTC
Version: 2.22.3

What were you doing when the application crashed?
again a "ctrl +" crash


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

System: Linux 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Simple
Icon Theme: gnome

Memory status: size: 116969472 vsize: 116969472 resident: 37961728 share: 21700608 rss: 37961728 rss_rlim: 4294967295
CPU usage: start_time: 1218085800 rtime: 519 utime: 466 stime: 53 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 0xb6c0e920 (LWP 12110)]
[New Thread 0xb3857b90 (LWP 12120)]
[New Thread 0xb2855b90 (LWP 12119)]
[New Thread 0xb3056b90 (LWP 12118)]
[New Thread 0xb4127b90 (LWP 12116)]
[New Thread 0xb5129b90 (LWP 12115)]
[New Thread 0xb4928b90 (LWP 12114)]
[New Thread 0xb5acbb90 (LWP 12111)]
(no debugging symbols found)
0xb7fce424 in __kernel_vsyscall ()


----------- .xsession-errors (1128568 sec old) ---------------------
[driAllocateTexture:636] unable to allocate texture
[driAllocateTexture:636] unable to allocate texture
[driAllocateTexture:636] unable to allocate texture
[driAllocateTexture:636] unable to allocate texture
[driAllocateTexture:636] unable to allocate texture
[driAllocateTexture:636] unable to allocate texture
[driAllocateTexture:636] unable to allocate texture
[driAllocateTexture:636] unable to allocate texture
[driAllocateTexture:636] unable to allocate texture
[driAllocateTexture:636] unable to allocate texture
[driAllocateTexture:636] unable to allocate texture
[driAllocateTexture:636] unable to allocate texture
[driAllocateTexture:636] unable to allocate texture
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Reinout van Schouwen 2008-08-07 08:21:21 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 546713 ***