GNOME Bugzilla – Bug 300627
vino server don't start or crash immediatly
Last modified: 2005-04-15 01:06:47 UTC
Distribution: Debian 3.1 Package: vino Severity: normal Version: GNOME2.6.1 unspecified Gnome-Distributor: Debian Synopsis: vino server don't start or crash immediatly Bugzilla-Product: vino Bugzilla-Component: Server Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.1) Description: Description of the crash: The setup in preferences is regular, but the vnc server probably crash immediatly, because i can't see the process, i can't see the tcp port open (via netstat or snort), i can't connect from other pc. When i reopen the vino-preferences setup form, the system show me a msg asking if i want restat the vino application. Steps to reproduce the crash: 1. enable remote desktop sharing from vino-preferences 2. try to connect from other pc (this step fail) 3. reopening vino-preferences a msg appear that ask if you want restart vino. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/vino-preferences' (no debugging symbols found) Using host libthread_db library "/lib/tls/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 -1222015136 (LWP 20267)] (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) 0xb766c4ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 58177
Thread 1 (Thread -1222015136 (LWP 20267))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-14 11:52 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "vino". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was daniele.bocci+bugbuddy@isti.cnr.it. 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 300188, which has been marked as a duplicate of 166873. *** This bug has been marked as a duplicate of 166873 ***