gnome-flashback crashed with SIGABRT() in g_assertion_message()

Bug #1639616 reported by Thomas Mayer on 2016-11-06
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-flashback (Ubuntu)
Undecided
Unassigned

Bug Description

I get this error from time to time. To this day, I could not figure out which action leads to the problem. I just get notified about the error (see screen shot) but besides that I do not notice any negative effects. My system still runs smoothly even if the error appears.

The error appears in the middle of a session most of the time. In rare cases it appears directly after suspend/resume. I believe it does not appear after a clean boot, but I'm not so sure about that. I have the impression that there might be a side effect of suspend/resume which makes this error more likely to happen.

I have continouosly let ubuntu's error reporting proceed, but so far nothing has improved for months.

I also found some issues via launchpad which are somehow similar, but either classified as duplicates or closed because of missing feedback. However, this particular error still happens on up-to-date ubuntu 16.04.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-flashback 3.18.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Nov 6 20:05:02 2016
InstallationDate: Installed on 2014-11-29 (708 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-flashback
UpgradeStatus: Upgraded to xenial on 2016-06-15 (144 days ago)

Thomas Mayer (thomas303) wrote :
Dmitry Shachnev (mitya57) wrote :

This bug would be more informative, if you enabled proper crash reporting as described on https://wiki.ubuntu.com/Apport#Ubuntu_12.04_and_later.

Anyway, on errors.ubuntu.com there are two popular entries that may match your bug. Both are related to the monitor manager. I am attaching stack traces for both of them.

Dmitry Shachnev (mitya57) wrote :
Dmitry Shachnev (mitya57) wrote :

I should also add that both these crashes happen on 16.04 only, not on 16.10.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers