vinagre segfault when connecting via Connect dialog

Bug #772429 reported by Paul Hardwick
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
vinagre (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: vinagre

Description: Ubuntu 11.04
Release: 11.04
vinagre:
  Installed: 2.30.3-1ubuntu2
  Candidate: 2.30.3-1ubuntu2
  Version table:
 *** 2.30.3-1ubuntu2 0
        500 http://gb.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

Scenario 1:
launched vinagre from command line
Click "connect" button, select VNC, click "Find", select IPV4 or IPV6 connection to Ubuntu 10.10 remote desktop.
Expected connection achieved and password dialog.
What happened: Segfault
[ 8042.137556] vinagre[2656]: segfault at 96 ip b6e7cfcc sp bfef5db0 error 4 in libgobject-2.0.so.0.2800.6[b6e4a000+45000]

Scenario 2:
launched vinagre from command line
Click "connect" button, select VNC, type in IPV4 address of Ubuntu 10.10 remote desktop.
Expected connection achieved and password dialog and then view of desktop.
What happened: Remote desktop appears, able to move remote windows for a few seconds before session locks up. Need to close connection and Vinagre before reconnection possible.

Revision history for this message
Peter Neyeloff (wxneypar) wrote :

Hi I think this is the same bug as mine, 778600

Have you found any solution?
Cheers,

Revision history for this message
Sebastien Bacher (seb128) wrote :

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.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

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.

Changed in vinagre (Ubuntu):
importance: Undecided → Low
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.