[Ubuntu-x-swat] [Bug 1656620] Re: Discoloration in some XFCE icons and window borders

2017-01-24 Thread Bug Watch Updater
** Changed in: mesa
   Status: Unknown => Confirmed

** Changed in: mesa
   Importance: Unknown => Medium

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

Title:
  Discoloration in some XFCE icons and window borders

To manage notifications about this bug go to:
https://bugs.launchpad.net/llvm/+bug/1656620/+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 1643789] Re: Backport packages for 16.04.2 lts-hwe stack

2017-01-24 Thread Steve Langasek
Hello Timo, or anyone else affected,

Accepted libdrm into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.70-1~ubuntu16.04.1 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 on 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: libdrm (Ubuntu Xenial)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed

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

Title:
  Backport packages for 16.04.2 lts-hwe stack

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1643789/+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 1646537] Re: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100%

2017-01-24 Thread AceLan Kao
** Changed in: linux (Ubuntu Vivid)
   Status: In Progress => Won't Fix

-- 
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/1646537

Title:
  Backlight sometimes fails to resume from suspend & screen brightness
  sometimes will not dim below 100%

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646537/+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 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-24 Thread Daniel van Vugt
Fortunately that's already the case. An app in Unity8 is always asking
Unity8 to ask USC to turn the screen off. Unity8 already has the option
of rejecting it, in theory.

-- 
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/1521403

Title:
  Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent
  (./src/platforms/mirserver/screen.cpp:406)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1521403/+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 1659140] [NEW] x crashes when I log in and back out of a tty (console, cntrl-alt-F2 thing, whatever)

2017-01-24 Thread My name
Public bug reported:

Observed behavior:

When I get an alternate tty, or whatever it's called, with cntrl-alt-FN,
where N is any digit, 2-6, inclusive; log in as the same user on the
console; do stuff; and then log out with "exit":

I'm suddenly back in tty1 and X has crashed. There is no x on any
console. I can start it again with startx.

Expected behavior:

As it does in 14.04, I should just get a login prompt and stay in the
same console. X running in tty1 should be unaffected, like x in tty7
would be unaffected in Trusty.


This is 64 bit Xenial with a minimalist Openbox environment, built from the 
mini.iso. I start X with "startx".

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

-- 
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/1659140

Title:
  x crashes when I log in and back out of a tty (console, cntrl-alt-F2
  thing, whatever)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1659140/+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 1646574] Re: Mouse cursor invisible or does not move

2017-01-24 Thread Brad Figg
** Package changed: xserver-xorg-video-nouveau (Ubuntu) => linux
(Ubuntu)

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

Title:
  Mouse cursor invisible or does not move

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646574/+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 1646574] Re: Mouse cursor invisible or does not move

2017-01-24 Thread David Jordan
This bug affects a number of different systems with Nvidia 10 Series
(Pascal) GPUs.  When using Nouveau, the cursor is drawn in the top left
corner of the screen and appears to be stuck there despite the user
being able to move around and click anywhere.

While it's possible to work around this bug by installing the
proprietary Nvidia driver, this bug is a huge hassle when installing
from the standard iso.  (Also when the proprietary driver breaks or is
removed for some reason)

The Nouveau developers report that this is fixed in Kernel 4.10 and pointed to 
this commit as solving the issue:
https://github.com/skeggsb/nouveau/commit/b94985176af536ab752a63baecdee263ffcce63f
With the two preceding commits being needed as well:
https://github.com/skeggsb/nouveau/commit/0d874f550816a6d7038658c3ec78c992e40c132f
https://github.com/skeggsb/nouveau/commit/88a1b714678ad1f5bda441052383e70a9d52f100

Still need to test these commits, but they look promising.

With 16.04.2 bringing in the 4.8 kernel, which is affected by this bug,
it would be nice to have these cherry picked to make sure the ISO works
with modern NVIDIA GPUs.

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

Title:
  Mouse cursor invisible or does not move

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1646574/+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


Re: [Ubuntu-x-swat] [Bug 1653259] Re: Ubuntu 16.10 Full screen freeze appears to be a continuation of bug 1561795

2017-01-24 Thread Jan Greeff
Thanks Matthias. The problem appears to have been sorted out by the 
developers because a fresh install of Ubuntu 16.04 solved the problem 
for me.

On 24/01/2017 22:17, Matthias Laumer wrote:
> Just found a workaround...
>
> I have installed ccsm and added the specific window-classes to
> "Gerneral" -> "Composite" -> "Undirect match" like: "& !(class=google-
> chrome)"
>
> I had a simular problem with Virtual-Box in Full-Screen Mode ...
> therefor I have added  "& class=VirtualBox" as well... now it is
> working.
>

-- 
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/1653259

Title:
  Ubuntu 16.10 Full screen freeze appears to be a continuation of bug
  1561795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1653259/+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 1653259] Re: Ubuntu 16.10 Full screen freeze appears to be a continuation of bug 1561795

2017-01-24 Thread Matthias Laumer
Just found a workaround...

I have installed ccsm and added the specific window-classes to
"Gerneral" -> "Composite" -> "Undirect match" like: "& !(class=google-
chrome)"

I had a simular problem with Virtual-Box in Full-Screen Mode ...
therefor I have added  "& class=VirtualBox" as well... now it is
working.

-- 
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/1653259

Title:
  Ubuntu 16.10 Full screen freeze appears to be a continuation of bug
  1561795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1653259/+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 1656315] Re: nividia driver 304 not loading under Trusty

2017-01-24 Thread Galen Thurber
Some system update has cleared this glitch.
I also did a purge of nvidia & reboots before attempting an install of 304.134 
via "Additional Drivers" software update option.

Start-Date: 2017-01-20  17:52:19
Commandline: aptdaemon role='role-commit-packages' sender=':1.116'
Upgrade: libcuda1-304:amd64 (304.132-0ubuntu0.14.04.2, 
304.134-0ubuntu0.14.04.1), nvidia-304:amd64 (304.132-0ubuntu0.14.04.2, 
304.134-0ubuntu0.14.04.1), libseccomp2:amd64 (2.1.0+dfsg-1, 
2.1.1-1ubuntu1~trusty3), nvidia-opencl-icd-304:amd64 (304.132-0ubuntu0.14.04.2, 
304.134-0ubuntu0.14.04.1)
End-Date: 2017-01-20  17:53:23

Start-Date: 2017-01-21  15:01:42
Commandline: /usr/sbin/synaptic
Install: xserver-xorg-video-nouveau-lts-xenial-dbg:amd64 
(1.0.12-1build2~trusty1)
Remove: lives:amd64 (2.2.0~ds0-1), ...
Purge: libcuda1-304:amd64 (304.134-0ubuntu0.14.04.1), nvidia-settings:amd64 
(331.20-0ubuntu8), nvidia-304:amd64 (304.134-0ubuntu0.14.04.1), 
nvidia-opencl-icd-304:amd64 (304.134-0ubuntu0.14.04.1), libvdpau1:amd64 
(0.7-1ubuntu0.1)
End-Date: 2017-01-21  15:02:09

** Changed in: xorg (Ubuntu)
   Status: New => Fix Released

-- 
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/1656315

Title:
  nividia driver 304 not loading under Trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1656315/+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 1653259] Re: Ubuntu 16.10 Full screen freeze appears to be a continuation of bug 1561795

2017-01-24 Thread Matthias Laumer
I have the same situation here with a Ubuntu 16.04 running on a Kaby-
Lake CPU. Fullscreen in Google-Chrome or in the editor "Atom" crashes
Unity. Cant minimize the fullscreen-window again, cant click anything.
Only possible way is rebooting.

-- 
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/1653259

Title:
  Ubuntu 16.10 Full screen freeze appears to be a continuation of bug
  1561795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1653259/+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 1659089] [NEW] Ubuntu acting up when working with Virtualbox and other programs

2017-01-24 Thread Barry Parker
Public bug reported:

Bug report has been added.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.101  Thu Dec  1 15:52:31 
PST 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
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
Date: Tue Jan 24 11:27:19 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-59-generic, x86_64: installed
 nvidia-340, 340.101, 4.4.0-59-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-59-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Apple Inc. G84M [GeForce 8600M GT] [106b:00a3]
InstallationDate: Installed on 2017-01-19 (5 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Apple Inc. MacBookPro4,1
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=a7dc4c24-c475-4254-a40b-2452715de03b ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/27/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP41.88Z.00C1.B03.0802271651
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F42C89C8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42C89C8
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP41.88Z.00C1.B03.0802271651:bd02/27/08:svnAppleInc.:pnMacBookPro4,1:pvr1.0:rvnAppleInc.:rnMac-F42C89C8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C89C8:
dmi.product.name: MacBookPro4,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple 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.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
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: Tue Jan 24 11:14:50 2017
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
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/1659089

Title:
  Ubuntu acting up when working with Virtualbox and other programs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1659089/+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 1639180] Re: no login possible after update to nvidia 304.132

2017-01-24 Thread Brian Murray
Setting to Fix Released then.

bdmurray@flash:~$ apt-cache policy nvidia-304
nvidia-304:
  Installed: 304.134-0ubuntu0.16.04.1
  Candidate: 304.134-0ubuntu0.16.04.1
  Version table:
 *** 304.134-0ubuntu0.16.04.1 500
500 http://192.168.10.7/ubuntu xenial-security/restricted amd64 Packages
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu xenial/main 
amd64 Packages
100 /var/lib/dpkg/status
 304.131-0ubuntu3 500
500 http://192.168.10.7/ubuntu xenial/restricted amd64 Packages


** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639180

Title:
  no login possible after update to nvidia 304.132

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1580123] Re: xrandr --scale (again) confines mouse to native solution

2017-01-24 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Unknown => Incomplete

** Changed in: xorg-server
   Importance: Unknown => High

-- 
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/1580123

Title:
  xrandr --scale (again) confines mouse to native solution

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1580123/+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 1658962] [NEW] Xorg freezes

2017-01-24 Thread Viktor Penkov
Public bug reported:

Suddenly, Xorg crashes when browsing the web.

Searching through the dmesg and syslog, dmesg has the following:


[  249.927216] [ cut here ]
[  249.927260] WARNING: CPU: 3 PID: 2332 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_uncore.c:619 
hsw_unclaimed_reg_debug+0x69/0x90 [i915]()
[  249.927262] Unclaimed register detected before writing to register 0x223a0
[  249.927264] Modules linked in: ctr ccm bnep binfmt_misc intel_rapl arc4 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek 
snd_hda_codec_generic kvm uvcvideo snd_hda_codec_hdmi
irqbypass snd_hda_intel iwlmvm videobuf2_vmalloc snd_hda_codec mac80211 
snd_hda_core videobuf2_memops videobuf2_v4l2 snd_hwdep videobuf2_core serio_raw 
v4l2_common intel_pch_thermal snd_pcm btusb videodev btrtl joydev media 
input_leds iwlwifi btbcm snd_seq_midi btintel rtsx_pci_ms snd_seq_midi_event 
bluetooth thinkpad_acpi snd_rawmidi nvram cfg80211 snd_seq lpc_ich 
snd_seq_device memstick snd_timer mei_me snd mei shpchp soundcore mac_hid 
parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg 
dm_crypt hid_generic usbhid hid crct10dif_pclmul crc32_pclmul rtsx_pci_sdmmc 
i915 aesni_intel aes_x86_64
[  249.927318]  lrw gf128mul glue_helper ablk_helper psmouse cryptd 
i2c_algo_bit drm_kms_helper ahci syscopyarea libahci sysfillrect sysimgblt 
rtsx_pci e1000e fb_sys_fops drm ptp pps_core wmi video
fjes
[  249.927333] CPU: 3 PID: 2332 Comm: chromium-browse Not tainted 
4.4.42-040442-generic #201701120631
[  249.927335] Hardware name: LENOVO 20BV003SBM/20BV003SBM, BIOS JBET54WW (1.19 
) 11/06/2015
[  249.927337]  0086 1b064ea6 88023dcc3cd8 
813d8ff3
[  249.927340]  88023dcc3d20 c0321358 88023dcc3d10 
810800f2
[  249.927343]  88022f73 000223a0 000223a0 
88022f730080
[  249.927346] Call Trace:
[  249.927348][] dump_stack+0x63/0x90
[  249.927359]  [] warn_slowpath_common+0x82/0xc0
[  249.927361]  [] warn_slowpath_fmt+0x5c/0x80
[  249.927384]  [] hsw_unclaimed_reg_debug+0x69/0x90 [i915]
[  249.927406]  [] gen8_write32+0x5b/0x1d0 [i915]
[  249.927425]  [] intel_lrc_irq_handler+0x1bc/0x240 [i915]
[  249.927441]  [] gen8_gt_irq_handler+0x217/0x240 [i915]
[  249.927456]  [] gen8_irq_handler+0xa1/0x740 [i915]
[  249.927461]  [] handle_irq_event_percpu+0x8d/0x1d0
[  249.927463]  [] handle_irq_event+0x3e/0x60
[  249.927466]  [] handle_edge_irq+0x80/0x150
[  249.927469]  [] handle_irq+0x1d/0x30
[  249.927472]  [] do_IRQ+0x4b/0xd0
[  249.927475]  [] common_interrupt+0x82/0x82
[  249.927476]  
[  249.927478] ---[ end trace 27bb76d8ad7cb53b ]---


A hard reboot was needed to get back to normal.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.4.42-040442-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: i3
Date: Tue Jan 24 12:25:24 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:5034]
InstallationDate: Installed on 2016-01-06 (383 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
MachineType: LENOVO 20BV003SBM
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.42-040442-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/06/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET54WW (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BV003SBM
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BV003SBM:pvrThinkPadT450:rvnLENOVO:rn20BV003SBM:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BV003SBM
dmi.product.version: ThinkPad T450
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
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: 

[Ubuntu-x-swat] [Bug 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-24 Thread MichaƂ Sawicz
There definitely are usecases for applications requesting display power
changes, but yes they need to be filtered/mangled by the shell, and only
applied when the requesting app, and session, are in focus.

Whether that should be a privileged operation, I'm not sure. As long as
the user can easily escape it (Alt+Tab, power button etc.), I don't
think we need to protect this.

-- 
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/1521403

Title:
  Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent
  (./src/platforms/mirserver/screen.cpp:406)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1521403/+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 1639051] Re: gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2

2017-01-24 Thread jani
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639051

Title:
  gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2,
  304.132-0ubuntu0.14.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1639051/+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