This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1626098

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Wrong screen capturing and flickering when using gnome-screenshot or
  kazam on Dell XPS 13 9350

Status in linux package in Ubuntu:

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:      16.04
  version: Ubuntu 4.4.0-38.57-generic 4.4.19

    Installed: 3.18.0-1ubuntu2
    Candidate: 3.18.0-1ubuntu2
    Version table:
   *** 3.18.0-1ubuntu2 500
          500 xenial/main amd64 Packages
          100 /var/lib/dpkg/status

    Installed: 1.4.5-2
    Candidate: 1.4.5-2
    Version table:
   *** 1.4.5-2 500
          500 xenial/universe amd64 Packages
          500 xenial/universe i386 Packages
          100 /var/lib/dpkg/status

  When using the gnome-screenshot to capture screen, an irrelevant area of the 
screen is captured. It could be the login background or 'cached' screen area 
from windows that have been opened and closed a long time ago, instead of the 
real area captured with the cursor selector.

  This will might not be a gnome-screenshot at all, and more probably an
  intel hd graphics driver issue, since using any alternative packages
  for screenshoting or screencasting will end in same result.

  Another strange thing is that on cold boots, everything is working
  properly for a while, but after some time, and after screen locks, the
  capturing tools will again start to misbehave.

  Here are some screencasts captured with kazam, exposing a similar

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to