GNOME Bugzilla – Bug 302975
vino preferences dialog chrashing
Last modified: 2005-05-05 01:43:16 UTC
Distribution: Debian 3.1 Package: vino Severity: normal Version: GNOME2.10.0 unspecified Gnome-Distributor: Ubuntu Synopsis: vino preferences dialog chrashing Bugzilla-Product: vino Bugzilla-Component: Preferences Dialog Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: I enabled remote desktop access. Someone used. After quiting the remote access I closed the dialog with the close button and the vino preferences application crashed. Steps to reproduce the crash: 1. Enable remote access, keep preferences dialog open 2. Had remote access and terminated it normally 3. Close preferences dialog will result in crash Expected Results: Dialog terminates without crash. How often does this happen? Once. Tried it only once. Additional Information: No. Debugging Information: Backtrace was generated from '/usr/bin/vino-preferences' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208060640 (LWP 17563)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 59147
Thread 1 (Thread -1208060640 (LWP 17563))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-04 11:14 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. Matches the stack trace in bug 172037, which has been marked as a duplicate of 166873. *** This bug has been marked as a duplicate of 166873 ***