GNOME Bugzilla – Bug 170231
vino-preferences dialog unexpectedly crashes
Last modified: 2005-03-13 23:04:53 UTC
Distribution: Debian 3.1 Package: vino Severity: minor Version: GNOME2.10.0 2.10.x Gnome-Distributor: Ubuntu Synopsis: vino-preferences dialog unexpectedly crashes Bugzilla-Product: vino Bugzilla-Component: Preferences Dialog Bugzilla-Version: 2.10.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: The Remote Desktop applet (vino-preferences) crashes upon being dismissed (by clicking the close control in the top-right hand corner). Steps to reproduce the crash: 1. Enable Remote Desktop (in this case, settings were to prompt server user to allow a client to connect rather than using password) and dismisses dialog. 2. Connect to server from another Linux box (in this case, using Ethernet and the realvnc 4.0 vncviewer command-line tool) 3. Server operator allows connection. 4. Client operator dismisses vncviewer window. 5. Server operator loads Remote Desktop dialog, disables remote desktop then dismisses window. 6. Remote Desktop applet crashes. Expected Results: The applet should not crash. How often does this happen? Apparently, every time when following the above steps on this distribution. Additional Information: Observed on a fresh installation of the Ubuntu Hoary 5.04 preview release. 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 -1221614304 (LWP 7570)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 56818
Thread 1 (Thread -1221614304 (LWP 7570))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-13 15:43 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "vino". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
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. Looks like the stack trace in bug 168946, which has been marked as a duplicate of 166873. *** This bug has been marked as a duplicate of 166873 ***