desktop-packages team mailing list archive

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

Daniel Richard G., 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/717578

Title:
  remmina assert failure: *** glibc detected *** remmina: realloc():
  invalid pointer: 0x000000000270b320 ***

Status in remmina package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: remmina

  I had just wrapped up an RDP session to a remote Windows system (by
  invoking a remote reboot), switched to another virtual desktop while
  that was in progress, and then BAM! Apport dialog.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: remmina 0.8.0-1
  Uname: Linux 2.6.37-020637-generic x86_64
  Architecture: amd64
  AssertionMessage: *** glibc detected *** remmina: realloc(): invalid pointer: 0x000000000270b320 ***
  Date: Sat Feb 12 00:46:59 2011
  ExecutablePath: /usr/bin/remmina
  ProcCmdline: remmina
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: remmina
  StacktraceTop:
   raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
   abort () at abort.c:92
   __libc_message (do_abort=<value optimized out>, fmt=<value optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
   malloc_printerr (action=3, str=0x7fa0747d4f8b "realloc(): invalid pointer", ptr=<value optimized out>) at malloc.c:6283
   __libc_realloc (oldmem=0x0, bytes=16) at malloc.c:3778
  Title: remmina assert failure: *** glibc detected *** remmina: realloc(): invalid pointer: 0x000000000270b320 ***
  UserGroups: adm audio cdrom dialout floppy plugdev video

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