desktop-packages team mailing list archive

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

Bastien Durel, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. 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/988843

Title:
  remmina/rdp window turns blue or crashes gnome-shell

Status in remmina package in Ubuntu:
  Invalid

Bug description:
  When using precise remmina to access to a windows remote computer, the whole window (including decorations, see screenshot) turns blue.
  This is triggered by hitting the "resize window" button

  This often (but not each time) crashes the shell, wich cannot be re-
  launched (even with --replace), complaining about a composer started
  on the screen

  when crashing, remmina prints this message in the terminal:
  (remmina:4484): Gtk-WARNING **: drawing failure for widget `GtkDrawingArea': invalid matrix (not invertible)

  this message is printed in the .xsession-errors:
  Avertissement du gestionnaire de fenêtres : Log level 16: The program 'gnome-shell' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadAlloc (insufficient resources for operation)'.
    (Details: serial 66933 error_code 11 request_code 12 minor_code 0)
    (Note to programmers: normally, X errors are reported asynchronously;
     that is, you will receive the error a while after causing it.
     To debug your program, run it with the GDK_SYNCHRONIZE environment
     variable to change this behavior. You can then get a meaningful
     backtrace from your debugger if you break on the gdk_x_error() function.)

  I may send the whole .xsession-errors file if needed

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