Black Screenshot

Reported by Gregor Santner on 2012-09-19
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
elementary OS
Undecided
Unassigned

Bug Description

Pictures created from the Screenshot-Application are only showing the mouse pointer.

Build: elementaryos-unstable-amd64.20120918

Only 3party-installed package: AMD Drivers 8.96.7

ProblemType: Bug
DistroRelease: elementary 0.2
Package: elementary-desktop 1.276-0~346~precise1 [origin: LP-PPA-elementary-os-daily]
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
Uname: Linux 3.2.0-30-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu13+elementary3~precise1
Architecture: amd64
CrashDB: elementary_meta
Date: Wed Sep 19 20:22:26 2012
InstallationMedia: elementary OS 0.2 "Luna" - Build amd64 LIVE Binary 20120918-01:30
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: elementary-meta
SuspiciousXErrors:

ThirdParty: True
UpgradeStatus: No upgrade log present (probably fresh install)

Gregor Santner (gregi94) wrote :
Gregor Santner (gregi94) on 2012-09-20
tags: added: precise
removed: preciser

This is a bug in fglrx, AMD's proprietary driver. Unfortunately, there's nothing we can do about this.

Changed in elementaryos:
status: New → Won't Fix

It failed to me with GIMP and the embedded screenshot utility, but in Ubuntu 12.04 it works like a charm...

Mattia Guidi (matguidi) wrote :

I respect the "won't fix" decision, but why is this bug not present in Ubuntu Precise Pangolin? This means a fix is actually possible.

Cody Garver (codygarver) wrote :

Ubuntu uses a different window manager.

Mattia Guidi (matguidi) wrote :

True, I see. Still, it's really frustrating. I would use the open-source drivers if they wouldn't cause my CPU to over-heat. Since with the Radeon drivers it's almost impossible to work, I have to use the proprietary ones - but cannot take any screenshots. Hope a fix will come out soon, either from AMD or from Radeon developers.

Mattia Guidi (matguidi) wrote :

Pardon my ignorance, but if it's the window manager, if this "bug" is present only in Gala (not in Compiz, not in Metacity), isn't it possible to fix Gala so to avoid this? To me it sounds like it's Gala that has something "peculiar" (in this respect) compared to other window managers. If the answer is that (by definition) open-source developer cannot adjust their code to make it work with proprietary drivers, then fine. But in practical terms the question exists.

Cody Garver (codygarver) wrote :

This bug is inherited from our relationship with GNOME's technologies. Gala is built on libmutter, as is GNOME Shell's window manager Mutter. libmutter is what has incompatibilities with the drivers, you'd have the same experiences if you were using GNOME Shell. Unfortunately, we can't do anything about it.

Paul Figueiredo (ghona76) wrote :

I realize that this is old, and has probably been solved by many others individually at this point. But I wanted to add this here so that others could maybe benefit if they experience the same issues.

The problem seems to be hardware acceleration not turned on by default. How I got it fixed:

1) After activating the driver, you will likely be met with a "driver is activated but not currently in use" error message.

2) open a terminal and type:

sudo apt-get install xvba-va-driver libva-glx1 libva-egl1 vainfo

followed by:

sudo vainfo

You should be met with a screen that looks like:

libva: VA-API version 0.32.0
Xlib: extension "XFree86-DRI" missing on display ":0".
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so
libva: va_openDriver() returns 0
vainfo: VA-API version: 0.32 (libva 1.0.15)
vainfo: Driver version: Splitted-Desktop Systems XvBA backend for VA-API - 0.7.8
vainfo: Supported profile and entrypoints
      VAProfileH264High : VAEntrypointVLD
      VAProfileVC1Advanced : VAEntrypointVLD

If you reboot your computer at this point, the error message in the driver dialogue should be gone.

3) Open your Catalyst Control Center as Administrator and enable Tear-free.

This got my screenshot working again with proprietary drivers. Maybe it will work for others.

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

Other bug subscribers