Version-Release number of selected component: tigervnc-1.2.80-0.9.20130307svn5060.fc18 Additional info: backtrace_rating: 4 cmdline: vncviewer jupiter:0 crash_function: Fl_X::set_cursor executable: /usr/bin/vncviewer kernel: 3.8.2-206.fc18.x86_64 uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 Fl_X::set_cursor at Fl_x.cxx:2668 #1 Fl_Window::cursor at fl_cursor.cxx:170 #2 Viewport::popupContextMenu at /usr/src/debug/tigervnc-1.2.80-20130307svn5060/vncviewer/Viewport.cxx:908 #3 Viewport::handle at /usr/src/debug/tigervnc-1.2.80-20130307svn5060/vncviewer/Viewport.cxx:441 #4 send at Fl.cxx:1104 #5 Fl::handle_ at Fl.cxx:1337 #6 DesktopWindow::fltkHandle at /usr/src/debug/tigervnc-1.2.80-20130307svn5060/vncviewer/DesktopWindow.cxx:434 #7 fl_handle at Fl_x.cxx:1833 #8 do_queued_events at Fl_x.cxx:201 #9 fl_wait at Fl_x.cxx:275
Created attachment 713900 [details] File: backtrace
Created attachment 713901 [details] File: cgroup
Created attachment 713902 [details] File: core_backtrace
Created attachment 713903 [details] File: dso_list
Created attachment 713904 [details] File: environ
Created attachment 713905 [details] File: limits
Created attachment 713906 [details] File: maps
Created attachment 713907 [details] File: open_fds
Created attachment 713908 [details] File: proc_pid_status
Created attachment 713909 [details] File: var_log_messages
I'm not sure if this is mentioned above, but this is dead easy to reproduce. Hit F8 to display the menu and then click in the vnc window (outside the menu). Boom. Instant crash. Happens all the time :)
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I haven't been able to reproduce this with: F-18: tigervnc-1.2.80-0.10.20130314svn5065.fc18 F-19: tigervnc-1.2.80-0.16.20130314svn5065.fc19 Perhaps it's fixed now?
Hopefully I am doing the right thing here. Abrt brought me here... dual monitors locally open full screen to a dual headed server when I close vnc (F8,end session) I get a crash 100% reproducible
(In reply to Jeremy Mordkoff from comment #15) > Hopefully I am doing the right thing here. Abrt brought me here... > > dual monitors locally > open full screen to a dual headed server > when I close vnc (F8,end session) I get a crash > > 100% reproducible more details that I'm pretty sure are not significant running across an SSH tunnel vnc server is running FC17 client is running FC20 monitor layout set using nvidia tools