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 545826 - crash in Epiphany Web Bookmarks: ctrl +
crash in Epiphany Web Bookmarks: 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-01 09:41 UTC by penguinfou
Modified: 2008-08-01 13:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description penguinfou 2008-08-01 09:41:12 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: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 157470720 vsize: 157470720 resident: 50475008 share: 27062272 rss: 50475008 rss_rlim: 4294967295
CPU usage: start_time: 1217583588 rtime: 666 utime: 601 stime: 65 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 0xb6bd8720 (LWP 3134)]
[New Thread 0xb1957b90 (LWP 3144)]
[New Thread 0xb0955b90 (LWP 3143)]
[New Thread 0xb1156b90 (LWP 3142)]
[New Thread 0xb220ab90 (LWP 3140)]
[New Thread 0xb320cb90 (LWP 3139)]
[New Thread 0xb2a0bb90 (LWP 3138)]
[New Thread 0xb5b5bb90 (LWP 3135)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

----------- .xsession-errors (42 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-01 13:49:27 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 ***