GNOME Bugzilla – Bug 398056
crash in Epiphany Web Bookmarks: Reorganising bookmarks. ...
Last modified: 2007-01-18 16:49:47 UTC
Version: 2.16.1 What were you doing when the application crashed? Reorganising bookmarks. I had created and delete some categories, assigned many bookmarks to categories. This crash happened when I dragged the last 2 uncategorised bookmarks together to a category, they didn't seem to move, so I tried dragging them again and the crash happened. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 192684032 vsize: 0 resident: 192684032 share: 0 rss: 81330176 rss_rlim: 0 CPU usage: start_time: 1169121678 rtime: 0 utime: 25504 stime: 0 cutime:23890 cstime: 0 timeout: 1614 it_real_value: 0 frequency: 2 Backtrace was generated from '/usr/bin/epiphany' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1229130064 (LWP 25294)] [New Thread -1345479776 (LWP 31590)] [New Thread -1319556192 (LWP 30260)] [New Thread -1280693344 (LWP 25391)] [New Thread -1298666592 (LWP 25390)] [New Thread -1272300640 (LWP 25298)] [New Thread -1262371936 (LWP 25297)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 103283
Thread 1 (Thread -1229130064 (LWP 25294))
This is reproducible: 1. Create one or more categories 2. Create two or more uncategorised bookmarks 3. Open "Edit Bookmarks..." 4. Selected "Not Categorised" 5. Select all uncategorised bookmarks 6. Drag them to a category 7. *boom* Doesn't happen dragging multiple-selections in other situations, doesn't happen dragging the last uncategorised bookmark away on its own. Seems to be specifically when multiple bookmarks are categorised and there are no uncategorised ones left.
Thanks for the bug report. This particular bug has already been fixed in the current development relase, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 351814 ***