abrt version: 1.1.13
Attached file: backtrace
reason: Process /usr/bin/vinagre was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce
1.server switched from 1920*1080 to 640*480. scaling was enabled.
Created attachment 461903 [details]
Please try installing this update of GTK-VNC and let me know if it still crashes when the server switches size. This update includes a fix that checks for the server sending out-of-bounds updates, and disconnects from the server cleanly instead of crashing
What VNC server are you connecting to though ? It could be that your server is buggy in sending VNC resizes.
It still crashes. Bug number for the submitted backtrace: 656068
the crash didn't happen at the first resolution change. The first
changes just killed the connection. Fifth change killed the client. It seems
that it is sensitive to the changes to lower resolution, not to higher.
*** Bug 656068 has been marked as a duplicate of this bug. ***
Can you capture me a trace with 'vinagre --gtk-vnc-debug' from time of initial connection to the VNC server, through the resizes, upto the point it crashes.
Then, do the same running
Created attachment 462335 [details]
output of 'vinagre --gtk-vnc-debug', vinagre crashed after resolution change
Created attachment 462340 [details]
output of 'valgrind vinagre'
output of several 'valgrind vinagre'. I was unable to provoke the crash by resolution changes through at lest 50 resolution changes during half an hour, running with valgrind.
These are the three key log messages at the end
The VNC server does a resize to 800x600 pixels:
(vinagre:21644): gvnc-DEBUG: vncconnection.c FramebufferUpdate type=-223 area (800x600) at location 0,0
And sends an initial framebuffer update for that new desktop
(vinagre:21644): gvnc-DEBUG: vncconnection.c FramebufferUpdate type=16 area (800x600) at location 0,0
But then bizarrely sends an update for a region that it way outside the framebuffer at offset 1166
(vinagre:21644): gvnc-DEBUG: vncconnection.c FramebufferUpdate type=16 area (19x19) at location 1166,695
So there are 2 bugs here
1. gtk-vnc is not doing a correct bounds check on framebuffer updates and thus scribbling over random memory when it gets that out of bounds update
2. vino is sending illegal framebuffer updates for regions outside the current framebuffer
I'm re-assigning this bug to gtk-vnc for resolution of the client side problem, and will clone against vino too.
gtk-vnc-0.4.2-2.fc14 has been submitted as an update for Fedora 14.
gtk-vnc-0.4.2-3.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update gtk-vnc'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/gtk-vnc-0.4.2-3.fc14
Sorry for using this as a chat board...
I tried installing this update from the updates-testing repo and I am used to do this. I notice from Bodhi that it should be there, however, I am not able to find the package. Yum only lists gtk-vnc 0.4.2-1 even with option --enablerepo=updates-testing. I vaguely remember that there should be some way to ensure that yum reads a fresh mirror of the repo?
gtk-vnc-0.4.2-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.