compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed.

Bug #1350523 reported by Carla Sella
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
frame
In Progress
Medium
Marco Trevisan (Treviño)
compiz (Ubuntu)
Won't Fix
Medium
Unassigned
Xenial
Invalid
Undecided
Unassigned
frame (Ubuntu)
Fix Released
Undecided
Unassigned
Xenial
Fix Released
Undecided
Unassigned

Bug Description

[Impact]

Unity might crash on systems with touch screen or multi-gesture supporting touchpads.

[Test case]

The crash is pretty random, it happens in some cases where unity is locked and after a suspension. Without having to touch any input.

[Regression Potential]

Regression potential: fix is very safe. We're just removing asserts in code, returning safe values and printing errors instead.

Not sure if the cause is running autopilot tests.

ProblemType: CrashDistroRelease: Ubuntu 14.10
Package: compiz-core 1:0.9.11+14.10.20140707-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
.tmp.unity.support.test.0:

.tmp.unity.support.test.1:

ApportVersion: 2.14.5-0ubuntu1
Architecture: amd64
AssertionMessage: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed.
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Jul 30 21:46:07 2014
DistUpgraded: 2014-05-04 22:52:42,676 DEBUG enabling apt cron job
DistroCodename: utopic
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: NVIDIA Corporation Device [10de:0491]
InstallationDate: Installed on 2014-02-13 (166 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211)
MachineType: System manufacturer System Product Name
ProcCmdline: compiz
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=5607f5b0-7033-4580-a503-1d178b40c2b5 ro quiet splash vt.handoff=7
Signal: 6SourcePackage: compiz
StacktraceTop:
 __assert_fail_base (fmt=0x7f25565248b0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f2539d8e36f "status == UFStatusSuccess", file=file@entry=0x7f2539d8e364 "device.cpp", line=line@entry=147, function=function@entry=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:92
 __GI___assert_fail (assertion=0x7f2539d8e36f "status == UFStatusSuccess", file=0x7f2539d8e364 "device.cpp", line=147, function=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:101
 frame_device_get_window_resolution_x () from /usr/lib/x86_64-linux-gnu/libframe.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6
Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed.
UpgradeStatus: Upgraded to utopic on 2014-05-04 (86 days ago)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers
dmi.bios.date: 09/13/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0803
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M2N
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.54-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Wed Jul 30 20:35:16 2014
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu8
xserver.video_driver: nouveau

Related branches

Revision history for this message
Carla Sella (carla-sella) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in compiz (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in compiz (Ubuntu):
status: New → Confirmed
Revision history for this message
Jonas G. Drange (jonas-drange) wrote :

Happened to me during a autopilot3-sandbox-run

Stephen M. Webb (bregma)
information type: Private → Public
Revision history for this message
Will Cooke (willcooke) wrote :

As part of the big bug clear up for 16.04 LTS I am marking this bug as Wont Fix.
These types of crasher are better handled by errors.ubutnu.com which can collate similar crash reports to help us identify persitent bugs rather than one-off crashes.
Sorry we are not able to help with this specific issue. If you are still experiencing this crash, please re-open the bug and add the tag "desktop-bugscrub-reopened". See https://wiki.ubuntu.com/BigDesktopBugScrub for more information.

Changed in compiz (Ubuntu):
status: Confirmed → Won't Fix
tags: added: desktop-bugscrub-autoclosed
Changed in frame:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
Chris J Arges (arges)
Changed in compiz (Ubuntu Xenial):
status: New → Invalid
Changed in frame (Ubuntu):
status: New → Fix Released
description: updated
Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

Hello Carla, or anyone else affected,

Accepted frame into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/frame/2.5.0daily13.06.05+16.04.20160809-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in frame (Ubuntu Xenial):
status: New → Fix Committed
tags: added: verification-needed
Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

This can't be easily verified, but there are no regressions or crashes.

So I'm marking it as verified.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package frame - 2.5.0daily13.06.05+16.04.20160809-0ubuntu1

---------------
frame (2.5.0daily13.06.05+16.04.20160809-0ubuntu1) xenial; urgency=medium

  * device: don't use asserts to get properties on failures, to avoid
    crashes (LP: #1350523)

 -- Marco Trevisan (Treviño) <mail@3v1n0.net> Tue, 09 Aug 2016 19:14:39 +0000

Changed in frame (Ubuntu Xenial):
status: Fix Committed → Fix Released
Revision history for this message
Chris J Arges (arges) wrote : Update Released

The verification of the Stable Release Update for frame has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.