abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: vinagre component: vinagre crash_function: vnc_framebuffer_get_width executable: /usr/bin/vinagre kernel: 2.6.35.6-48.fc14.x86_64 package: vinagre-2.31.4-1.fc14 rating: 4 reason: Process /usr/bin/vinagre was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1290635457 uid: 500 How to reproduce ----- 1. Using SSH to map a local port to the remote port, also using a different port from standard (i.e. not 22) 2. Then make VNC connection to server 3. Occasionally crashes when attempting connection - but not always (intermittant)
Created attachment 462787 [details] File: backtrace
Package: vinagre-2.31.4-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. logg in 2. 3.
Package: vinagre-2.31.4-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open vinagre (remote desktop viewer) 2. Connect to another linux box (Centos) 3. Connect to a third (Windows XP box - UltraVNC) Step 3 crashes vinagre pretty regularly. Also, when I only connect to Centos box, the interface works fine, but then slowly degrades in performance until I have to restart vinagre. This also did not happen before the latest update. Comment ----- This used to work before the latest update...
Package: vinagre-2.31.4-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Start vinagre 2. Open and close bookmarks in quick succession 3. Boom
The first two reported crashes are bug 650104 which is in gtk-vnc. Comment 4 is reporting a completely different problem, likely bug 654350 *** This bug has been marked as a duplicate of bug 650104 ***