[Ubuntu-x-swat] [Bug 1652282] [NEW] Wayland default policy prohibits root applications

2017-04-24 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have found that after switching from Xorg to Wayland on Ubuntu GNOME
16.10 with GNOME 3.22 that GParted does not run when I try to run it as
root. That is when I click the icon and enter my password nothing
happens. I have found that when running what is run when the icon is
clicked that the output in Terminal is (gparted-pkexec):

Created symlink /run/systemd/system/-.mount → /dev/null.
Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
Created symlink /run/systemd/system/boot.mount → /dev/null.
Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
Created symlink /run/systemd/system/tmp.mount → /dev/null.
No protocol specified

(gpartedbin:16832): Gtk-WARNING **: cannot open display: :0
Removed /run/systemd/system/-.mount.
Removed /run/systemd/system/boot-efi.mount.
Removed /run/systemd/system/boot.mount.
Removed /run/systemd/system/run-user-1000.mount.
Removed /run/systemd/system/run-user-120.mount.
Removed /run/systemd/system/tmp.mount.

So I am now unable to launch and use GParted as root which is really the
only way I can run it in order to make changes.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gparted 0.25.0-1
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Dec 23 11:13:13 2016
InstallationDate: Installed on 2016-05-15 (221 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: gparted
UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago)

** Affects: gparted
 Importance: High
 Status: Confirmed

** Affects: ubuntu-gnome
 Importance: High
 Status: Triaged

** Affects: wayland (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: amd64 apport-bug wayland wayland-session
-- 
Wayland default policy prohibits root applications
https://bugs.launchpad.net/bugs/1652282
You received this bug notification because you are a member of Ubuntu-X, which 
is subscribed to wayland in Ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1685811] Re: Acceleration lost after upgrading from 16.10 to 17.04

2017-04-24 Thread Timo Aaltonen
install xdiagnose and run 'apport-collect 1685811'

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1685811

Title:
  Acceleration lost after upgrading from 16.10 to 17.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1685811/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1660072] Re: Missing depends on xkb-data-i18n

2017-04-24 Thread Gunnar Hjalmarsson
xkb-data should not depend on it, since the xkeyboard-config
translations are provided via language packs on Ubuntu.

With that said, I agree that it's a bit odd that nothing depends on xkb-
data-i18n. This is how the existence of xkb-data-i18n is explained in
the changelog:

"control, rules, xkb-data-i18n.install, xkb-data.install:
Split out xkb-data-i18n to be used by console-setup."

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1660072

Title:
  Missing depends on xkb-data-i18n

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1660072/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1685774] Re: Turkish keyboard issues

2017-04-24 Thread Bug Watch Updater
** Changed in: xkeyboard-config
   Status: Unknown => Fix Released

** Changed in: xkeyboard-config
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1685774

Title:
  Turkish keyboard issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1685774/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1685774] Re: Turkish keyboard issues

2017-04-24 Thread Gunnar Hjalmarsson
As regards the Turkish currency symbol, it was changed in xkb-data 2.20
as a fix of .
However, Ubuntu 17.04 is shipped with version 2.19 of the xkb-data
package, so this will be fixed when 2.20 reaches Ubuntu (in 17.10 or
18.04).

As regards the other things you list, it looks to me as if you basically
would like to see a complete rewrite of the Turkish keyboard layout.

On 2017-04-24 13:18, Cem wrote:
> * For the letter ã, Alt Gr + Ü key should be pressed then a key
> should be pressed.

Currently ++Ü followed by A results in ā.

> * For the letter õ, Alt Gr + Ü key should be pressed then o key
> should be pressed.

Currently ++Ü followed by O results in ō.

> * For the character ~, Alt Gr + Ü should be pressed then space key
> should be pressed.

Currently +Ü results in ~ (without space).

> * For the letter æ, Alt Gr + A should be pressed

Currently the æ symbol is not present with the Turkish layout AFAICT.

Stopping there...

To propose an update of the Turkish keyboard layout, I have to ask you
to file an upstream bug.

https://bugs.freedesktop.org/enter_bug.cgi?product=xkeyboard-
config;component=General

** Bug watch added: freedesktop.org Bugzilla #99187
   https://bugs.freedesktop.org/show_bug.cgi?id=99187

** Package changed: langpack-locales (Ubuntu) => xkeyboard-config
(Ubuntu)

** Changed in: xkeyboard-config (Ubuntu)
   Importance: Undecided => Medium

** Changed in: xkeyboard-config (Ubuntu)
   Status: New => Confirmed

** Also affects: xkeyboard-config via
   https://bugs.freedesktop.org/show_bug.cgi?id=99187
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1685774

Title:
  Turkish keyboard issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1685774/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1685774] [NEW] Turkish keyboard issues

2017-04-24 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

There are still some problems with Turkish keyboard in 17.04:

* The currency is updated as ₺ at 17.04 but there is no way to type it by 
keyboard. By the standard, it should be Alt Gr + T key to type ₺:
https://thumb1.shutterstock.com/display_pic_with_logo/3175712/591962180/stock-photo-word-no-meaning-hayir-in-turkish-written-on-a-keyboard-in-a-row-with-red-keys-591962180.jpg



Some keys' behaviors are different from Windows, so for those, it can be
considered as any update or not, but for any case, I am also reporting:

http://wiki.laptop.org/images/thumb/6/64/TR-MP-Qv1.png/800px-TR-MP-
Qv1.png

* For the letter ã, Alt Gr + Ü key should be pressed then a key should be 
pressed.
* For the letter õ, Alt Gr + Ü key should be pressed then o key should be 
pressed.
* For the character ~, Alt Gr + Ü should be pressed then space key should be 
pressed.
* For the letter æ, Alt Gr + A should be pressed 
* For the letter â, Shift + 3 then a should be pressed.
* For the letter û, Shift + 3 then u should be pressed.
* For the letter ô, Shift + 3 then o should be pressed.
* For the letter î, Shift + 3 then ı or i should be pressed.
* For the letter ê, Shift + 3 then e should be pressed.
* For the character ^, Shift + 3 then space should be presssed.
* For the letter é, Alt Gr + ş then e should be pressed.
* For the letter á, Alt Gr + ş then a should be pressed.
* For the letter ú, Alt Gr + ş then u should be pressed.
* For the letter ó, Alt Gr + ş then o should be pressed.
* For the letter í, Alt Gr + ş then ı or i should be pressed.
* For the character ´, Alt Gr + ş then space should be pressed.
* For the letter ò, Alt Gr + , then o should be pressed.
* For the letter ù, Alt Gr + , then u should be pressed.
* For the letter à, Alt Gr + , then a should be pressed.
* For the character `, Alt Gr + , then space should be pressed.

** Affects: xkeyboard-config (Ubuntu)
 Importance: Medium
 Status: Confirmed

-- 
Turkish keyboard issues
https://bugs.launchpad.net/bugs/1685774
You received this bug notification because you are a member of Ubuntu-X, which 
is subscribed to xkeyboard-config in Ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1685811] [NEW] Acceleration lost after upgrading from 16.10 to 17.04

2017-04-24 Thread Hadmut Danisch
Public bug reported:

Hi,

on my ASRock Beebox N3150, 
00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 21)


the graphics became significantly slower after upgrading from 16.10 to 17.04. 
Swapping windows or desktops does not really happen instantly anymore and 
became a process with sometimes visible progress. It looks as if the hardware 
acceleration was lost during update. 


regards

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xserver-xorg-core 2:1.19.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Apr 24 16:23:56 2017
InstallationDate: Installed on 2016-04-22 (367 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
SourcePackage: xorg-server
UpgradeStatus: Upgraded to zesty on 2017-04-18 (5 days ago)

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1685811

Title:
  Acceleration lost after upgrading from 16.10 to 17.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1685811/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1647600] Re: Xvfb fails with new mesa, results in ubiquity FTBFS

2017-04-24 Thread LocutusOfBorg
I did a sync and rebased the above patch, would be nice to recheck it on
artful

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libepoxy in Ubuntu.
https://bugs.launchpad.net/bugs/1647600

Title:
  Xvfb fails with new mesa, results in ubiquity FTBFS

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1586539] Re: Major screen flickering in Chromium and Google Chrome

2017-04-24 Thread Timo Aaltonen
That's a kernel change which is included in v4.10.

Closing as fixed, on 16.04 the hwe-16.04 kernel will be updated to it
before 16.04.3, and before that happens you can use the -edge kernel
which is on v4.10 already.

** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu)

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

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1586539

Title:
  Major screen flickering in Chromium and Google Chrome

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1586539/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1685775] [NEW] Can't use VGA

2017-04-24 Thread GNACADJA
Public bug reported:

Hi,

when i connect an external screen, throught VGA , my laptop (DELL
Latitude E6410 ) doesn't detect it.

typing  xrandr -q  in terminal give me :

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1280 x 800, current 1280 x 800, maximum 1280 x 800
default connected primary 1280x800+0+0 0mm x 0mm
   1280x800  76.00* 

thanks for your help

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.9.0-040900-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Apr 24 12:07:49 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 i915-4.6.3-4.4.0, 1, 4.4.0-71-generic, x86_64: installed
 i915-4.6.3-4.4.0, 1, 4.4.0-72-generic, x86_64: installed
 virtualbox, 5.0.36, 4.4.0-72-generic, x86_64: installed
 virtualbox, 5.0.36, 4.9.0-040900-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Latitude E6410 [1028:040a]
InstallationDate: Installed on 2016-06-26 (302 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. Latitude E6410
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-040900-generic 
root=/dev/mapper/ubuntu--vg-root ro nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf:
 Section "Device"
 Identifier "My device"
 Driver "intel"
 EndSection
dmi.bios.date: 08/10/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.asset.tag: 111737
dmi.board.name: 0667CC
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.asset.tag: 111737
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd08/10/2010:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0667CC:rvrA03:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6410
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Apr 24 11:31:32 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 No devices detected.
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1685775

Title:
  Can't use VGA

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1685772] [NEW] to high cpu frequenz

2017-04-24 Thread Bock
Public bug reported:

Hallo, the cpu  running is always  to high (35%-45%).
The compiz Prozess need always power.
I need help to configure Ubuntu right.
Ähmm, i can German.

Hear u scudelin

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Apr 24 12:58:04 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 3Dfx Interactive, Inc. Voodoo 4 / Voodoo 5 [121a:0009] (rev 01) (prog-if 00 
[VGA controller])
   Subsystem: 3Dfx Interactive, Inc. Voodoo5 PCI 5500 [121a:0003]
InstallationDate: Installed on 2017-03-22 (32 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle 
(HCI mode)
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: MSI MS-7250
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=d9822317-7575-424c-9308-78678355dc5c ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2007
dmi.bios.vendor: MS-7250
dmi.bios.version: V1.8
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7250
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnMS-7250:bvrV1.8:bd07/31/2007:svnMSI:pnMS-7250:pvr1.0:rvnMSI:rnMS-7250:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7250
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Apr 24 12:39:03 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImExPS/2 Generic Explorer Mouse MOUSE, id 9
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1685772

Title:
  to high cpu frequenz

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp