desktop-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

exquest, thank you for reporting this bug to Ubuntu. Mavericks reached EOL on April 10, 2012.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this an issue on a supported release? If so, please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

Now reproduce the crash, then 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'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
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.

Please do not attach your crash report manually to this report and
reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Changed in: remmina (Ubuntu)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/683249

Title:
  cant connect to rdp or vnc via ssh tunnel in version 8.0

Status in remmina package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: remmina

  I've been using Remmina for a while to remote into various computers.
  Up to this point it's worked great but this past weekend I upgraded my
  laptop to Ubuntu 10.10 which comes with Remmina 0.8.0.

  When I try to connect to a remote RDP server via a ssh tunnel I get a
  message that says "Unable to connect to RDP server 127.0.0.1" even
  though I specified the server:port as I'm supposed to.  Using the
  exact same settings I'm able to connect on my Ubuntu 10.04 desktop
  with Remmina 0.7.4.


  the output of 'apt-cache policy remmina'
  remmina:
    Installed: 0.8.0-1
    Candidate: 0.8.0-1
    Version table:
   *** 0.8.0-1 0
          500 http://mirrors.ecvps.com/ubuntu/ maverick/universe i386 Packages
          100 /var/lib/dpkg/status

  
  If I can provide any further information let me know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/683249/+subscriptions