Vino closes and restart automatically when "Preferences" option is open
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vino (Ubuntu) |
Fix Released
|
Medium
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: vino
I'm testing using Ubuntu karmic 9.10. The package with the bug is vino 2.26.2-1ubuntu1.
I want to get into preferences but when i'm there vino closes and restart automatically. Then I can't access again anymore from a remote computer. Killing vino-server and restarting it doesn't work, I have to reboot Ubuntu in order to fix it.
GPU: i945
Driver: xserver-
It doesn't happen in Jaunty.
ProblemType: Bug
Architecture: i386
Date: Fri Jul 17 09:54:09 2009
DistroRelease: Ubuntu 9.10
Package: vino 2.26.2-1ubuntu1
ProcEnviron:
LANG=es_AR.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: vino
Uname: Linux 2.6.31-3-generic i686
description: | updated |
description: | updated |
summary: |
- Vino crashes and restart automatically when "Preferences" option is open + Vino closes and restart automatically when "Preferences" option is open |
Changed in vino (Ubuntu): | |
status: | Invalid → New |
Changed in vino (Ubuntu): | |
status: | New → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.
If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.
If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/ apport/ apport- qt --crash- file=/var/ crash/_ my_crash_ report. crash in a terminal - where _my_crash_ report. crash is the crash you would like to report.
I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.