← Back to team overview

desktop-packages team mailing list archive

[Bug 1258220] Re: xbc_io.c:274:poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed

 

Mike, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. If this is reproducible on a supported release. 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: New => 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/1258220

Title:
  xbc_io.c:274:poll_for_event: Assertion
  `!xcb_xlib_threads_sequence_lost' failed

Status in remmina package in Ubuntu:
  Invalid

Bug description:
  I was using Firefox on anothe screen when reminna simply crashed.
  Brand new fully-patched OS install but using a copy of my
  /home/user/.remmina folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: remmina 1.0.0-4ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Dec  5 10:43:49 2013
  InstallationDate: Installed on 2013-12-05 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
  MarkForUpload: True
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

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