[Desktop-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Taihsiang Ho]

Test the same hardware as comment #15. This time I use proposed stack. I
could not reproduce the issue.

More information for reference (including the package information):

ubuntu@201507-18697:~$ DISPLAY=:0 glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
308 frames in 5.0 seconds = 61.559 FPS
299 frames in 5.0 seconds = 59.612 FPS
299 frames in 5.0 seconds = 59.598 FPS

ubuntu@201507-18697:~$ DISPLAY=:0 DRI_PRIME=1 glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
325 frames in 5.0 seconds = 64.859 FPS
300 frames in 5.0 seconds = 59.990 FPS
300 frames in 5.0 seconds = 59.792 FPS
297 frames in 5.0 seconds = 59.214 FPS
298 frames in 5.0 seconds = 59.584 FPS
301 frames in 5.0 seconds = 60.008 FPS
301 frames in 5.0 seconds = 60.000 FPS

ubuntu@201507-18697:~$ uname -a
Linux 201507-18697 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@201507-18697:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful
ubuntu@201507-18697:~$

ubuntu@201507-18697:~$ dpkg -l libdrm-common libdrm2 libcapnp-0.5.3 
libdrm-amdgpu1 libwayland-egl1-mesa libwayland-client0 libwayland-server0  
libegl1-mesa libgbm1 libmircore1   libmircommon7 libmirprotobuf3  libmirclient9 
libllvm5.0 libgl1-mesa-dri
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version 
ArchitectureDescription
+++-=-===-===-===
ii  libcapnp-0.5.3:amd64  0.5.3-2ubuntu2  
amd64   Cap'n Proto C++ library
ii  libdrm-amdgpu1:amd64  2.4.83-1
amd64   Userspace interface to amdgpu-specific kernel DRM 
services -- runtime
ii  libdrm-common 2.4.83-1
all Userspace interface to kernel DRM services -- 
common files
ii  libdrm2:amd64 2.4.83-1
amd64   Userspace interface to kernel DRM services -- 
runtime
ii  libegl1-mesa:amd6417.2.4-0ubuntu1~17.10.2 
amd64   free implementation of the EGL API -- runtime
ii  libgbm1:amd64 17.2.4-0ubuntu1~17.10.2 
amd64   generic buffer management API -- runtime
ii  libgl1-mesa-dri:amd64 17.2.4-0ubuntu1~17.10.2 
amd64   free implementation of the OpenGL API -- DRI modules
ii  libllvm5.0:amd64  1:5.0-3 
amd64   Modular compiler and toolchain technologies, 
runtime library
ii  libmirclient9:amd64   0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - client library
ii  libmircommon7:amd64   0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - shared library
ii  libmircore1:amd64 0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - shared library
ii  libmirprotobuf3:amd64 0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - RPC definitions
ii  libwayland-client0:amd64  1.14.0-1
amd64   wayland compositor infrastructure - client library
ii  libwayland-egl1-mesa:amd6417.2.4-0ubuntu1~17.10.2 
amd64   implementation of the Wayland EGL platform -- 
runtime
ii  libwayland-server0:amd64  1.14.0-1
amd64   wayland compositor infrastructure - server library


ubuntu@201507-18697:~$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM 
Registers [8086:1904] (rev 08)
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 520 
[8086:1916] (rev 07)
00:04.0 Signal processing controller [1180]: Intel Corporation Skylake 
Processor Thermal Subsystem [8086:1903] (rev 08)
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller [8086:9d2f] (rev 20)
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP 
Thermal subsystem [8086:9d31] (rev 20)
00:16.0 Communication controller [0780]: Intel Corporation Sunris

[Desktop-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[ethan.hsieh]

** Tags added: verification-done-xenial

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Taihsiang Ho]

Hi, I can't reproduce this issue with a fresh installed Artful on the I+A 
system[1] with gfx
  - Intel Corporation HD Graphics 520 [8086:1916] (rev 07)
  - Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / 
M340/M360 / M440/M445] [1002:6900] (rev 81)


I might need more information to reproduce and make sure this issue on Artful 
as well.

---


[1] Test machine -  CID 201507-18697 - Dell Latitude E5570

[2] More information for reference (including package information)


ubuntu@201507-18697:~$ DISPLAY=:0 glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
359 frames in 5.0 seconds = 71.667 FPS
300 frames in 5.0 seconds = 59.997 FPS
301 frames in 5.0 seconds = 60.002 FPS
300 frames in 5.0 seconds = 59.996 FPS
300 frames in 5.0 seconds = 60.000 FPS
301 frames in 5.0 seconds = 60.002 FPS
300 frames in 5.0 seconds = 59.996 FPS

ubuntu@201507-18697:~$ DISPLAY=:0 DRI_PRIME=1 glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
302 frames in 5.0 seconds = 60.321 FPS
301 frames in 5.0 seconds = 59.996 FPS
301 frames in 5.0 seconds = 60.005 FPS
301 frames in 5.0 seconds = 59.989 FPS
301 frames in 5.0 seconds = 60.008 FPS

ubuntu@201507-18697:~$ uname -a
Linux 201507-18697 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

ubuntu@201507-18697:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful
ubuntu@201507-18697:~$ apt-cache policy libdrm-amdgpu1
libdrm-amdgpu1:
  Installed: 2.4.83-1
  Candidate: 2.4.83-1
  Version table:
 *** 2.4.83-1 500
500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status


ubuntu@201507-18697:~$ apt-cache policy libgl1-mesa-dri
libgl1-mesa-dri:
  Installed: 17.2.2-0ubuntu1
  Candidate: 17.2.2-0ubuntu1
  Version table:
 *** 17.2.2-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

ubuntu@201507-18697:~$ dpkg -l libdrm-common libdrm2 libcapnp-0.5.3 
libdrm-amdgpu1 libwayland-egl1-mesa libwayland-client0 libwayland-server0  
libegl1-mesa libgbm1 libmircore1   libmircommon7 libmirprotobuf3  libmirclient9 
libllvm5.0 libgl1-mesa-dri
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version 
ArchitectureDescription
+++-=-===-===-===
ii  libcapnp-0.5.3:amd64  0.5.3-2ubuntu2  
amd64   Cap'n Proto C++ library
ii  libdrm-amdgpu1:amd64  2.4.83-1
amd64   Userspace interface to amdgpu-specific kernel DRM 
services -- runtime
ii  libdrm-common 2.4.83-1
all Userspace interface to kernel DRM services -- 
common files
ii  libdrm2:amd64 2.4.83-1
amd64   Userspace interface to kernel DRM services -- 
runtime
ii  libegl1-mesa:amd6417.2.2-0ubuntu1 
amd64   free implementation of the EGL API -- runtime
ii  libgbm1:amd64 17.2.2-0ubuntu1 
amd64   generic buffer management API -- runtime
ii  libgl1-mesa-dri:amd64 17.2.2-0ubuntu1 
amd64   free implementation of the OpenGL API -- DRI modules
ii  libllvm5.0:amd64  1:5.0-3 
amd64   Modular compiler and toolchain technologies, 
runtime library
ii  libmirclient9:amd64   0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - client library
ii  libmircommon7:amd64   0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - shared library
ii  libmircore1:amd64 0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - shared library
ii  libmirprotobuf3:amd64 0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - RPC definitions
ii  libwayland-client0:amd64  1.14.0-1

[Desktop-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[ethan.hsieh]

@Timo

Here is the test result of mesa (xenial-proposed)

A. Test Result:
1. DRI_PRIME=1 glxgear: Pass
2. DRI_PRIME=1 glxgear -fulscreen: Pass
3. glxgear: Pass
4. glxgear -fulscreen: Pass
5. Unigine_Heaven-4.0.run (5mins): Pass
6. Unigine_Heaven-4.0.run (Fullscreen, 5mins): Pass
7. DRI_PRIME=1 Unigine_Heaven-4.0.run (5mins): Pass
8. DRI_PRIME=1 Unigine_Heaven-4.0.run (Fullscreen, 5mins): Pass

B. Test Environment:
1. Ubuntu: Xenial 16.04
2. Graphic Card:
 b. Intel [8086:5917] (rev 07) + AMD [1002:6900] (rev ff)
3.Installed package:
 a. Online Update
 b. Enable xenial-proposed and then upgrade mesa
libglapi-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb
libgl1-mesa-dri_17.2.4-0ubuntu1~16.04.3~1_amd64.deb
libxatracker2_17.2.4-0ubuntu1~16.04.3~1_amd64.deb
libwayland-egl1-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb
libgl1-mesa-glx_17.2.4-0ubuntu1~16.04.3~1_amd64.deb
libgbm1_17.2.4-0ubuntu1~16.04.3~1_amd64.deb
libegl1-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb

** Tags removed: verification-needed-xenial

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1663157] Re: Guest session processes are not confined in 16.10 and newer releases

[Tyler Hicks]

@rbalint can you please open a new bug to track re-enabling the guest
session with proper confinement rather than piggy back on this bug?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1663157

Title:
  Guest session processes are not confined in 16.10 and newer releases

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Yakkety:
  Fix Released
Status in lightdm source package in Zesty:
  Fix Released
Status in lightdm source package in Artful:
  Fix Released

Bug description:
  Processes launched under a lightdm guest session are not confined by
  the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu
  16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The
  processes are unconfined.

  The simple test case is to log into a guest session, launch a terminal
  with ctrl-alt-t, and run the following command:

   $ cat /proc/self/attr/current

  Expected output, as seen in Ubuntu 16.04 LTS, is:

   /usr/lib/lightdm/lightdm-guest-session (enforce)

  Running the command inside of an Ubuntu 16.10 and newer guest session
  results in:

   unconfined

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1663157/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1741245] Re: gnome-shell freezes and crashes upon usb drive insertion

[alperyilmaz]

*** This bug is a duplicate of bug 1720768 ***
https://bugs.launchpad.net/bugs/1720768

Uh oh! Then, is there anything I can do, to pinpoint the actual problem?

Is there any package/tool which I can run before inserting USB and
collect information during freeze and restart of gnome-shell?

Running strace or similar tool for gnome-shell pid would do any help?

I'm afraid the crash reports for gnome-shell are huge and might contain
noise originating from other bugs/problems. I thought; the info, trace,
calls during the event only might help locate the problem may be..

Thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1741245

Title:
  gnome-shell freezes and crashes upon usb drive insertion

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  1) Release
  Ubuntu 17.10

  2)Package version
  gnome-shell 3.26.2-0ubuntu0.1

  3) What is expected

  After inserting, external HD drive, USB flash drive or phone (to
  charge) the computer should not freeze and crash

  4) What happens instead
  Almost all the time, when I insert an external drive gnome-shell freezes for 
a while and then restarts. I check the `dmesg` output and couldn't find the 
cause of this problem. And, not sure where to start and what to diagnose or 
test. 
  Also, unfortunately I don't have a script or method to reproducible this 
error elsewhere. I'm willing to participate if any developer wants to do tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741245/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked

[clickwir]

Quick comment, before today I've never seen this happen on this PC. Now
it's happened 4 times in the past couple hours.

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

Title:
  Screen blank, audio choppy, system locked

Status in xorg package in Ubuntu:
  New

Bug description:
  While watching a YouTube video, screen went blank. Audio cut out,
  after a few seconds the audio started playing normally for a few more
  seconds then kept repeating the last half a second of audio for a few
  more seconds. Then it stopped and nothing responded.

  It did this a few times over the course of an hour. Had to power off
  the PC to get a reboot. Last time it did this I ssh'd from another PC
  to get dmesg and syslog info as it happened. Attaching those captures.

  clickwir@mach:~$ uname -a
  Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  clickwir@mach:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.10
  Release:17.10
  Codename:   artful

  
   dmesg 

  [   10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up 
link
  [   10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
  [   10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000
  [   10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000
  [   10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   10.730200] r8169 :02:00.0 eth0: link down
  [   10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   16.875586] FS-Cache: Loaded
  [   16.896010] FS-Cache: Netfs 'nfs' registered for caching
  [   16.914353] NFS: Registering the id_resolver key type
  [   16.914364] Key type id_resolver registered
  [   16.914364] Key type id_legacy registered
  [   17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team
  [   17.513074] Ebtables v2.0 registered
  [   17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   17.863232] bridge: filtering via arp/ip/ip6tables is no longer available 
by default. Update your scripts to load br_netfilter if you need this.
  [   17.864899] virbr0: port 1(virbr0-nic) entered blocking state
  [   17.864903] virbr0: port 1(virbr0-nic) entered disabled state
  [   17.864995] device virbr0-nic entered promiscuous mode
  [   17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
  [   18.038385] virbr0: port 1(virbr0-nic) entered blocking state
  [   18.038388] virbr0: port 1(virbr0-nic) entered listening state
  [   18.095412] virbr0: port 1(virbr0-nic) entered disabled state
  [   89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   92.062606] show_signal_msg: 27 callbacks suppressed
  [   92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 
7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000]
  [   95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed

  ### abnormal begins here ###

  [ 1429.496584] sched: RT throttling activated
  [ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 
'tsc' as unstable because the skew is too large:
  [ 1429.706305] clocksource:   'hpet' wd_now: c4741f2e 
wd_last: c3bcdb60 mask: 
  [ 1429.706306] clocksource:   'tsc' cs_now: 4acf553cc2d 
cs_last: 4ac71a54967 mask: 
  [ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog
  [ 1434.739539] nfs: server 10.1.0.4 not responding, still trying
  [ 1437.469449] nfs: server 10.1.0.4 OK
  [ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
  [ 1439.143498] sched_clock: Marking unstable (1439092126811, 
50992985)<-(1439477690212, -334199655)
  [ 1440.403916] clocksource: Switched to clocksource hpet
  [ 1443.553969] hrtimer: interrupt took 629117003 ns
  [ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to 
run: 209.684 msecs
  [ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 44.646 msecs
  [ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering 
kernel.perf_event_max_sample_rate to 500
  [ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 61.329 msecs
  [ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering 
kernel.perf_event_max_sample_rate to 250
  [ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 172.103 msecs
  [ 1463.284345] perf: interrupt took too long (1344829 > 599262), lowering 
kernel.perf_event_max_sample_rate to 250
  [ 1465.175694] INFO: NMI handler (

[Desktop-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked

[clickwir]

I used "ubuntu-bug" to gather this info. I see it set
"ExtraDebuggingInterest: I just need to know a workaround" but that's
not what I selected when it asked. I chose the option that was something
like "Yes, but not if too technical".

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

Title:
  Screen blank, audio choppy, system locked

Status in xorg package in Ubuntu:
  New

Bug description:
  While watching a YouTube video, screen went blank. Audio cut out,
  after a few seconds the audio started playing normally for a few more
  seconds then kept repeating the last half a second of audio for a few
  more seconds. Then it stopped and nothing responded.

  It did this a few times over the course of an hour. Had to power off
  the PC to get a reboot. Last time it did this I ssh'd from another PC
  to get dmesg and syslog info as it happened. Attaching those captures.

  clickwir@mach:~$ uname -a
  Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  clickwir@mach:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.10
  Release:17.10
  Codename:   artful

  
   dmesg 

  [   10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up 
link
  [   10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
  [   10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000
  [   10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000
  [   10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   10.730200] r8169 :02:00.0 eth0: link down
  [   10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   16.875586] FS-Cache: Loaded
  [   16.896010] FS-Cache: Netfs 'nfs' registered for caching
  [   16.914353] NFS: Registering the id_resolver key type
  [   16.914364] Key type id_resolver registered
  [   16.914364] Key type id_legacy registered
  [   17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team
  [   17.513074] Ebtables v2.0 registered
  [   17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   17.863232] bridge: filtering via arp/ip/ip6tables is no longer available 
by default. Update your scripts to load br_netfilter if you need this.
  [   17.864899] virbr0: port 1(virbr0-nic) entered blocking state
  [   17.864903] virbr0: port 1(virbr0-nic) entered disabled state
  [   17.864995] device virbr0-nic entered promiscuous mode
  [   17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
  [   18.038385] virbr0: port 1(virbr0-nic) entered blocking state
  [   18.038388] virbr0: port 1(virbr0-nic) entered listening state
  [   18.095412] virbr0: port 1(virbr0-nic) entered disabled state
  [   89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   92.062606] show_signal_msg: 27 callbacks suppressed
  [   92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 
7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000]
  [   95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed

  ### abnormal begins here ###

  [ 1429.496584] sched: RT throttling activated
  [ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 
'tsc' as unstable because the skew is too large:
  [ 1429.706305] clocksource:   'hpet' wd_now: c4741f2e 
wd_last: c3bcdb60 mask: 
  [ 1429.706306] clocksource:   'tsc' cs_now: 4acf553cc2d 
cs_last: 4ac71a54967 mask: 
  [ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog
  [ 1434.739539] nfs: server 10.1.0.4 not responding, still trying
  [ 1437.469449] nfs: server 10.1.0.4 OK
  [ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
  [ 1439.143498] sched_clock: Marking unstable (1439092126811, 
50992985)<-(1439477690212, -334199655)
  [ 1440.403916] clocksource: Switched to clocksource hpet
  [ 1443.553969] hrtimer: interrupt took 629117003 ns
  [ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to 
run: 209.684 msecs
  [ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 44.646 msecs
  [ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering 
kernel.perf_event_max_sample_rate to 500
  [ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 61.329 msecs
  [ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering 
kernel.perf_event_max_sample_rate to 250
  [ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 172.103 msecs
  [ 1463.284345] perf: interrupt took t

[Desktop-packages] [Bug 1742867] [NEW] Screen blank, audio choppy, system locked

[clickwir]

Public bug reported:

While watching a YouTube video, screen went blank. Audio cut out, after
a few seconds the audio started playing normally for a few more seconds
then kept repeating the last half a second of audio for a few more
seconds. Then it stopped and nothing responded.

It did this a few times over the course of an hour. Had to power off the
PC to get a reboot. Last time it did this I ssh'd from another PC to get
dmesg and syslog info as it happened. Attaching those captures.

clickwir@mach:~$ uname -a
Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

clickwir@mach:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful


 dmesg 

[   10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up link
[   10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[   10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000
[   10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000
[   10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   10.730200] r8169 :02:00.0 eth0: link down
[   10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[   12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[   16.875586] FS-Cache: Loaded
[   16.896010] FS-Cache: Netfs 'nfs' registered for caching
[   16.914353] NFS: Registering the id_resolver key type
[   16.914364] Key type id_resolver registered
[   16.914364] Key type id_legacy registered
[   17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   17.513074] Ebtables v2.0 registered
[   17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed
[   17.863232] bridge: filtering via arp/ip/ip6tables is no longer available by 
default. Update your scripts to load br_netfilter if you need this.
[   17.864899] virbr0: port 1(virbr0-nic) entered blocking state
[   17.864903] virbr0: port 1(virbr0-nic) entered disabled state
[   17.864995] device virbr0-nic entered promiscuous mode
[   17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[   18.038385] virbr0: port 1(virbr0-nic) entered blocking state
[   18.038388] virbr0: port 1(virbr0-nic) entered listening state
[   18.095412] virbr0: port 1(virbr0-nic) entered disabled state
[   89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed
[   92.062606] show_signal_msg: 27 callbacks suppressed
[   92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 
7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000]
[   95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed

### abnormal begins here ###

[ 1429.496584] sched: RT throttling activated
[ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 
'tsc' as unstable because the skew is too large:
[ 1429.706305] clocksource:   'hpet' wd_now: c4741f2e 
wd_last: c3bcdb60 mask: 
[ 1429.706306] clocksource:   'tsc' cs_now: 4acf553cc2d 
cs_last: 4ac71a54967 mask: 
[ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog
[ 1434.739539] nfs: server 10.1.0.4 not responding, still trying
[ 1437.469449] nfs: server 10.1.0.4 OK
[ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
[ 1439.143498] sched_clock: Marking unstable (1439092126811, 
50992985)<-(1439477690212, -334199655)
[ 1440.403916] clocksource: Switched to clocksource hpet
[ 1443.553969] hrtimer: interrupt took 629117003 ns
[ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to 
run: 209.684 msecs
[ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
44.646 msecs
[ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering 
kernel.perf_event_max_sample_rate to 500
[ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
61.329 msecs
[ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
172.103 msecs
[ 1463.284345] perf: interrupt took too long (1344829 > 599262), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1465.175694] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
209.709 msecs
[ 1479.788229] perf: interrupt took too long (1849954 > 1681036), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1481.889284] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
209.761 msecs
[ 1481.889284] perf: interrupt took too long (3252104 > 2312442), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1491.745472] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
401.897 msecs
[ 1491.745472] perf: i

[Desktop-packages] [Bug 1742865] [NEW] Fn Keys do not work, nvidia card not found

[marc]

Public bug reported:

Browsed and tried solutions over the past 2 years, nothing worked...

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98
Uname: Linux 4.4.0-108-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
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: Fri Jan 12 06:43:48 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake Integrated Graphics [17aa:3828]
   Subsystem: Lenovo GM108M [GeForce 940M] [17aa:3829]
InstallationDate: Installed on 2016-07-07 (553 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f3:208d Elan Microelectronics Corp. 
 Bus 001 Device 003: ID 174f:14e6 Syntek 
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80R6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic.efi.signed 
root=UUID=8fa7aafa-77cc-4651-b87f-4565439e7577 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/28/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: D3CN27WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo Yoga 500-15ISK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 500-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrD3CN27WW:bd10/28/2015:svnLENOVO:pn80R6:pvrLenovoYoga500-15ISK:rvnLENOVO:rnLenovoYoga500-15ISK:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYoga500-15ISK:
dmi.product.name: 80R6
dmi.product.version: Lenovo Yoga 500-15ISK
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.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
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: Fri Jan 12 06:14:57 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   14162 
 vendor SDC
xserver.version: 2:1.18.4-0ubuntu0.7

** 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 Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1742865

Title:
  Fn Keys do not work, nvidia card not found

Status in xorg package in Ubuntu:
  New

Bug description:
  Browsed and tried solutions over the past 2 years, nothing worked...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98
  Uname: Linux 4.4.0-108-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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: Fri Jan 12 06:43:48 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:3828]
 Subsystem: Lenovo GM108M [GeForce 940M] [17aa:3829]
  InstallationDate: Installed on 2016-07-07 (553 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:208d Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 174f:14e6 Syntek 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Lin

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Daniel van Vugt]

It's ready :)

https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu4

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1718824

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Artful:
  New

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742750] Re: [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file

[Daniel van Vugt]

pulseaudio (1:11.1-1ubuntu4) bionic; urgency=high

  * 0030-load-module-switch-on-connect.patch: Correct typo in default.pa
causing pulseaudio startup failure. (LP: #1742750, LP: #1732629)
  * Refresh patches to apply more cleanly:
- 0802-alsa-mixer-Add-support-for-usb-audio-in-the-Dell-doc.patch
- 0803-build-sys-add-the-Dell-dock-TB16-configuration.patch

 -- Daniel van Vugt   Fri, 12 Jan 2018
10:23:11 +0800

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1742750

Title:
  [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to
  invalid /etc/pulse/default.pa file

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
  connect.patch, which changes line 38 of /etc/pulse/default.pa to read
  ".endif### Load audio drivers statically".  It appears that there are
  a couple of line feeds missing here, and having the comment on the
  same line as the endif causes pulseaudio not to start.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1732629] Re: Selecting USB Amp/Dac audio output in gnome sound does nothing

[Daniel van Vugt]

Users of 18.04 can now test:

https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu4

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1732629

Title:
  Selecting USB Amp/Dac audio output in gnome sound does nothing

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Running Ubuntu 17.10, when I plug an external USB Amp/Dac it is
  correctly recognized and I can play audio through it via aplay, but
  when I select it as my output sink from gnome sound, nothing happens:
  apps still output sound via the speakers.

  In order to fix it I have to restart pulseaudio.
  I've also found online that modifying /etc/pulse/default.pa, moving 
module-switch-on-connect.so loading before module-udev-detect.so, permanently 
fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   sergio 1374 F...m pulseaudio
   /dev/snd/controlC1:  sergio 1374 F pulseaudio
   /dev/snd/controlC0:  sergio 1374 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 09:03:19 2017
  InstallationDate: Installed on 2017-10-24 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.4
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-11-15T18:42:36.359190

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Phil Norisez]

I got it to work, and it fixes my problem with the launcher resulting in
an unknown file error on /usr/bin/compiz.

Go to Software & Updates via command line
ubuntu-software &
and selecting it from a list of apt applications.

Use Developer Options to enable xenial-proposed.

Then run command line:
sudo apt-get install libgl1-mesa-dri/xenial-proposed

This installed it for me.

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742856] [NEW] Silently stops receiving mail (agent not ready)

[Roman Odaisky]

Public bug reported:

Every couple weeks, some of my accounts silently stop receiving email as
though I’m not being sent any. I think this happens with my GMail
accounts and not with my own IMAP server, but I’m not sure. When I go to
akonadiconsole, the affected agent has nothing where other agents have
“Ready”. If I restart the agent, mail starts being received.

This is unfortunately yet another Akonadi Does Not Work problem. Please
fix.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: akonadi-server 4:17.04.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Jan 12 05:53:12 2018
InstallationDate: Installed on 2015-12-17 (756 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: akonadi
UpgradeStatus: Upgraded to artful on 2017-10-16 (87 days ago)

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


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1742856

Title:
  Silently stops receiving mail (agent not ready)

Status in akonadi package in Ubuntu:
  New

Bug description:
  Every couple weeks, some of my accounts silently stop receiving email
  as though I’m not being sent any. I think this happens with my GMail
  accounts and not with my own IMAP server, but I’m not sure. When I go
  to akonadiconsole, the affected agent has nothing where other agents
  have “Ready”. If I restart the agent, mail starts being received.

  This is unfortunately yet another Akonadi Does Not Work problem.
  Please fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: akonadi-server 4:17.04.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jan 12 05:53:12 2018
  InstallationDate: Installed on 2015-12-17 (756 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: akonadi
  UpgradeStatus: Upgraded to artful on 2017-10-16 (87 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Incomplete => Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/934291

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Unknown
Status in cups package in Ubuntu:
  Invalid
Status in cups-pk-helper package in Ubuntu:
  In Progress
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742852] [NEW] [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

[gabriel]

Public bug reported:

After a windows update I lost all the sound on my ubuntu machine. It's the 
second time that this happends.
My sound is unmuted and at a loud level and nothing is comming out of my 
speakers.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
  gbergeron   3656 F alsamixer
CurrentDesktop: Unity
Date: Thu Jan 11 22:21:23 2018
InstallationDate: Installed on 2017-11-29 (43 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   gbergeron   2408 F...m pulseaudio
 /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
  gbergeron   3656 F alsamixer
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX430UAR.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX430UAR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX430UAR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1742852

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After a windows update I lost all the sound on my ubuntu machine. It's the 
second time that this happends.
  My sound is unmuted and at a loud level and nothing is comming out of my 
speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Jan 11 22:21:23 2018
  InstallationDate: Installed on 2017-11-29 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   gbergeron   2408 F...m pulseaudio
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UAR.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742769] Re: Pulse Audio Won't Run After BionicBeaver Update

[Daniel van Vugt]

*** This bug is a duplicate of bug 1742750 ***
https://bugs.launchpad.net/bugs/1742750

This one is a duplicate so effectively closed already.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1742769

Title:
  Pulse Audio Won't Run After BionicBeaver Update

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  As per the bug report, I've noticed that Pulse Audio is segfaulting.
  Happened after the large update to Bionic Beaver this morning
  (Thursday Jan 11/18).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
  Uname: Linux 4.14.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Thu Jan 11 13:32:21 2018
  InstallationDate: Installed on 2017-12-20 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1742769] Re: Pulse Audio Won't Run After BionicBeaver Update

[Stephen Allen]

*** This bug is a duplicate of bug 1742750 ***
https://bugs.launchpad.net/bugs/1742750

OK Thanks for this - Did not see that one prior to filing. Should I close
mine or has that already been done?

On Thu, Jan 11, 2018 at 9:20 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> *** This bug is a duplicate of bug 1742750 ***
> https://bugs.launchpad.net/bugs/1742750
>
> Duplicate of bug 1742750, thanks.
>
> ** This bug has been marked a duplicate of bug 1742750
>Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/
> default.pa file
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1742769
>
> Title:
>   Pulse Audio Won't Run After BionicBeaver Update
>
> Status in pulseaudio package in Ubuntu:
>   New
>
> Bug description:
>   As per the bug report, I've noticed that Pulse Audio is segfaulting.
>   Happened after the large update to Bionic Beaver this morning
>   (Thursday Jan 11/18).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: pulseaudio 1:11.1-1ubuntu3
>   ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
>   Uname: Linux 4.14.0-16-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu6
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp',
> '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c',
> '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p',
> '/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p',
> '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p',
> '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1',
> '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
>   CurrentDesktop: GNOME
>   Date: Thu Jan 11 13:32:21 2018
>   InstallationDate: Installed on 2017-12-20 (21 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   SourcePackage: pulseaudio
>   Symptom: audio
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/12/2012
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 1401
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: M5A97 LE R2.0
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: Rev 1.xx
>   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:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
>   dmi.product.family: To be filled by O.E.M.
>   dmi.product.name: To be filled by O.E.M.
>   dmi.product.version: To be filled by O.E.M.
>   dmi.sys.vendor: To be filled by O.E.M.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742769/+subscriptions
>


-- 

This email is printed from 100% recycled electrons.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1742769

Title:
  Pulse Audio Won't Run After BionicBeaver Update

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  As per the bug report, I've noticed that Pulse Audio is segfaulting.
  Happened after the large update to Bionic Beaver this morning
  (Thursday Jan 11/18).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
  Uname: Linux 4.14.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Thu Jan 11 13:32:21 2018
  InstallationDate: Installed on 2017-12-20 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK 

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Hui Wang]

@Daniel,

Got it, waiting for 1:11.1-1ubuntu4 is ready. Then will do the test.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1718824

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Artful:
  New

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1717246] Re: nvidia-* kernel module failed to build (error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .unload = nv_drm_unload, )

[Daniel van Vugt]

** This bug is no longer a duplicate of bug 1741671
   nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to 
build [nv-linux.h:199:2: error: #error "This driver requires the ability to 
change memory types!"]

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

Title:
  nvidia-* kernel module failed to build (error: initialization from
  incompatible pointer type [-Werror=incompatible-pointer-types] .unload
  = nv_drm_unload,)

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  nvidia-340:
Installiert:   340.102-0ubuntu0.16.04.2
Installationskandidat: 340.102-0ubuntu0.16.04.2
Versionstabelle:
   *** 340.102-0ubuntu0.16.04.2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/restricted 
amd64 Packages
  100 /var/lib/dpkg/status
   340.102-0ubuntu0.16.04.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/restricted 
amd64 Packages
   340.96-0ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/restricted amd64 
Packages

  
  expected to be able to build kernel module with Kernel(-image & -headers) 
4.11.0-14-generic.
  just got an error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.102-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DKMSKernelVersion: 4.11.0-14-generic
  Date: Thu Sep 14 14:04:50 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-32-generic, x86_64: installed
   bbswitch, 0.8, 4.10.0-33-generic, x86_64: installed
   nvidia-340, 340.102: added
  DuplicateSignature: 
dkms:nvidia-340:340.102-0ubuntu0.16.04.2:/var/lib/dkms/nvidia-340/340.102/build/nv-drm.c:124:15:
 error: initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]
  GraphicsCard:
   NVIDIA Corporation C79 [GeForce 9400M G] [10de:0866] (rev b1) (prog-if 00 
[VGA controller])
 Subsystem: Acer Incorporated [ALI] C79 [GeForce 9400M G] [1025:0160]
  InstallationDate: Installed on 2017-08-16 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Acer Aspire 5737Z
  PackageVersion: 340.102-0ubuntu0.16.04.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=c62a2411-5d52-4b5b-ab0b-be0119fe97e1 ro priority=low quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.05
  dmi.board.name: KALA0
  dmi.board.vendor: Acer
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd02/13/2009:svnAcer:pnAspire5737Z:pvrV1.05:rvnAcer:rnKALA0:rvrN/A:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5737Z
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Sep 14 10:06:20 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.19.3-1ubuntu1~16.04.2

To manage notifications about this bug go

[Desktop-packages] [Bug 1742837] Re: nvidia-304 304.135-0ubuntu0.16.04.1: nvidia-304 kernel module failed to build (error: initialization from incompatible pointer type [-Werror=incompatible-pointer-t

[Daniel van Vugt]

*** This bug is a duplicate of bug 1717246 ***
https://bugs.launchpad.net/bugs/1717246

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1717246, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- nvidia-304 304.135-0ubuntu0.16.04.1: nvidia-304 kernel module failed to build
+ nvidia-304 304.135-0ubuntu0.16.04.1: nvidia-304 kernel module failed to build 
(error: initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]  .unload = nv_drm_unload,)

** This bug has been marked a duplicate of bug 1717246
   nvidia-* kernel module failed to build (error: initialization from 
incompatible pointer type [-Werror=incompatible-pointer-types] .unload = 
nv_drm_unload,)

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

Title:
  nvidia-304 304.135-0ubuntu0.16.04.1: nvidia-304 kernel module failed
  to build (error: initialization from incompatible pointer type
  [-Werror=incompatible-pointer-types]  .unload = nv_drm_unload,)

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  New

Bug description:
  problems with starup

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-304 304.135-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.135  Tue Jan 17 15:26:26 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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
  DKMSKernelVersion: 4.13.0-26-generic
  Date: Thu Jan 11 11:25:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304, 304.135, 4.10.0-42-generic, x86_64: installed
   nvidia-304, 304.135, 4.4.0-109-generic, x86_64: installed
  DuplicateSignature: 
dkms:nvidia-304:304.135-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-304/304.135/build/nv-drm.c:80:15:
 error: initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: XFX Pine Group Inc. G86 [GeForce 8500 GT] [1682:230b]
  InstallationDate: Installed on 2017-11-01 (71 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ECS H61H2-CM
  PackageVersion: 304.135-0ubuntu0.16.04.1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=eb749f2f-d622-4f9d-bd2d-9e81f86f52e1 ro recovery nomodeset
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: nvidia-graphics-drivers-304
  Title: nvidia-304 304.135-0ubuntu0.16.04.1: nvidia-304 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/28/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.name: H61H2-CM
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/28/2013:svnECS:pnH61H2-CM:pvr:rvnECS:rnH61H2-CM:rvr1.0:cvnECS:ct3:cvr:
  dmi.product.name: H61H2-CM
  dmi.sys.vendor: ECS
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Jan 11 20:59:51 2018
  xserver.configfile: default
  xse

[Desktop-packages] [Bug 1742750] Re: [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file

[Daniel van Vugt]

** Tags added: bionic regression-proposed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1742750

Title:
  [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to
  invalid /etc/pulse/default.pa file

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
  connect.patch, which changes line 38 of /etc/pulse/default.pa to read
  ".endif### Load audio drivers statically".  It appears that there are
  a couple of line feeds missing here, and having the comment on the
  same line as the endif causes pulseaudio not to start.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Leo Pilachowski]

It appears that the mirror I contact to still has not synced.  How do I
use "archive.ubuntu.com" ?

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742750] Re: Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file

[Daniel van Vugt]

Fix for bionic.

** Patch added: "pulseaudio_11.1-1ubuntu4.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742750/+attachment/5035556/+files/pulseaudio_11.1-1ubuntu4.debdiff

** Summary changed:

- Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid 
/etc/pulse/default.pa file
+ [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid 
/etc/pulse/default.pa file

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1742750

Title:
  [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to
  invalid /etc/pulse/default.pa file

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
  connect.patch, which changes line 38 of /etc/pulse/default.pa to read
  ".endif### Load audio drivers statically".  It appears that there are
  a couple of line feeds missing here, and having the comment on the
  same line as the endif causes pulseaudio not to start.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1724068] Re: Ralink Bluetooth is not recognized on Ubuntu 17.10

[Launchpad Bug Tracker]

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1724068

Title:
  Ralink Bluetooth is not recognized on Ubuntu 17.10

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Hello, hello, I have a problem with my ASUS k550DP and my integrated 
Bluetooth Ralink device, with Ubuntu 17.10
  the rfkill list all command does not show me the Bluetooth device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724068/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1724068] Re: Ralink Bluetooth is not recognized on Ubuntu 17.10

[Carlos Renê]

Me too Hp Pavilion x360:  Bluetooth [0d11]: Ralink corp. RT3290
Bluetooth [1814:3298] do not have a drive to install!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1724068

Title:
  Ralink Bluetooth is not recognized on Ubuntu 17.10

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Hello, hello, I have a problem with my ASUS k550DP and my integrated 
Bluetooth Ralink device, with Ubuntu 17.10
  the rfkill list all command does not show me the Bluetooth device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724068/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742769] Re: Pulse Audio Won't Run After BionicBeaver Update

[Daniel van Vugt]

*** This bug is a duplicate of bug 1742750 ***
https://bugs.launchpad.net/bugs/1742750

Duplicate of bug 1742750, thanks.

** This bug has been marked a duplicate of bug 1742750
   Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid 
/etc/pulse/default.pa file

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1742769

Title:
  Pulse Audio Won't Run After BionicBeaver Update

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  As per the bug report, I've noticed that Pulse Audio is segfaulting.
  Happened after the large update to Bionic Beaver this morning
  (Thursday Jan 11/18).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
  Uname: Linux 4.14.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Thu Jan 11 13:32:21 2018
  InstallationDate: Installed on 2017-12-20 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Daniel van Vugt]

And verification failed. See bug 1742750 now.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1718824

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Artful:
  New

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742750] Re: Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file

[Daniel van Vugt]

Thanks for that. I recall fixing that typo already but somehow that fix
got lost.

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Critical

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: pulseaudio (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1742750

Title:
  Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid
  /etc/pulse/default.pa file

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
  connect.patch, which changes line 38 of /etc/pulse/default.pa to read
  ".endif### Load audio drivers statically".  It appears that there are
  a couple of line feeds missing here, and having the comment on the
  same line as the endif causes pulseaudio not to start.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742449] Re: nvidia-340.104 dkms fails to build against 4.13.0-26

[Daniel van Vugt]

*** This bug is a duplicate of bug 1741671 ***
https://bugs.launchpad.net/bugs/1741671

OK, your build is actually failing here:

In file included from /var/lib/dkms/nvidia-340/340.102/build/nv.c:13:0:
/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h: At top level:
/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:199:2: error: #error "This 
driver requires the ability to change memory types!"
 #error "This driver requires the ability to change memory types!"
  ^
scripts/Makefile.build:308: recipe for target 
'/var/lib/dkms/nvidia-340/340.102/build/nv.o' failed
make[2]: *** [/var/lib/dkms/nvidia-340/340.102/build/nv.o] Error 1

So this is a duplicate of bug 1741671. Please add comments to that one.

** This bug has been marked a duplicate of bug 1741671
   nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to 
build [nv-linux.h:199:2: error: #error "This driver requires the ability to 
change memory types!"]

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

Title:
  nvidia-340.104 dkms fails to build against 4.13.0-26

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Laptops like my Thinkpad W510 cannot use newer drivers than nvidia-340
  because support for their old GPU was dropped in newer revisions.

  Meltdown/Spectre is upon us and I got 4.13.0-26 today, but
  nvidia-340's dkms driver will not build, for the common reason most
  nvidia drivers won't build against the new kernels. Looking at
  nvidia's official announcement I did not see a plan or release date
  for updates to nvidia-340, yet.

  Since my laptop is my own, I'm running with the pre-KPTI 4.10.0-42 for
  now, but figured I should report this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1742449/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1741245] Re: gnome-shell freezes and crashes upon usb drive insertion

[Daniel van Vugt]

*** This bug is a duplicate of bug 1720768 ***
https://bugs.launchpad.net/bugs/1720768

That new link is a different crash - bug 1714989 :)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1741245

Title:
  gnome-shell freezes and crashes upon usb drive insertion

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  1) Release
  Ubuntu 17.10

  2)Package version
  gnome-shell 3.26.2-0ubuntu0.1

  3) What is expected

  After inserting, external HD drive, USB flash drive or phone (to
  charge) the computer should not freeze and crash

  4) What happens instead
  Almost all the time, when I insert an external drive gnome-shell freezes for 
a while and then restarts. I check the `dmesg` output and couldn't find the 
cause of this problem. And, not sure where to start and what to diagnose or 
test. 
  Also, unfortunately I don't have a script or method to reproducible this 
error elsewhere. I'm willing to participate if any developer wants to do tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741245/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1739931] Re: Separator lines in shell popup menus are too faint to see

[Daniel van Vugt]

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Confirmed

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1739931

Title:
  Separator lines in shell popup menus are too faint to see

Status in Ubuntu theme:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  when I click on the dock icons, some of the lines in the popup menus
  are blank and some of them appear to be incorrect. see top left of
  attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 23 22:24:40 2017
  InstallationDate: Installed on 2016-08-18 (492 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1739931/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()

[Daniel van Vugt]

OK, if that's the fix then we'll get it in mutter 3.26.3. Now looking
forward to that one even more.

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_read_events() from ospoll_wait()

Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid
Status in mutter package in Fedora:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/c27f5c4fef272640ec1027318712f0434c7c8857

  ---

  no idea how to reproduce

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Nov 13 13:55:16 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-15-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1507]
  InstallationDate: Installed on 2013-09-03 (1531 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? ()
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1732629] Re: Selecting USB Amp/Dac audio output in gnome sound does nothing

[Daniel van Vugt]

It has to be fixed in 18.04 first. And after that it may get backported
to 17.10 only if people can confirm the fix is helping them. I would
love to get feedback from more users on that -- it seemed to not make
any difference for me when I tried it.

Bionic users will have the fix soon at least:
https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu3

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1732629

Title:
  Selecting USB Amp/Dac audio output in gnome sound does nothing

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Running Ubuntu 17.10, when I plug an external USB Amp/Dac it is
  correctly recognized and I can play audio through it via aplay, but
  when I select it as my output sink from gnome sound, nothing happens:
  apps still output sound via the speakers.

  In order to fix it I have to restart pulseaudio.
  I've also found online that modifying /etc/pulse/default.pa, moving 
module-switch-on-connect.so loading before module-udev-detect.so, permanently 
fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   sergio 1374 F...m pulseaudio
   /dev/snd/controlC1:  sergio 1374 F pulseaudio
   /dev/snd/controlC0:  sergio 1374 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 09:03:19 2017
  InstallationDate: Installed on 2017-10-24 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.4
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-11-15T18:42:36.359190

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742837] Re: nvidia-304 304.135-0ubuntu0.16.04.1: nvidia-304 kernel module failed to build

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  nvidia-304 304.135-0ubuntu0.16.04.1: nvidia-304 kernel module failed
  to build

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  New

Bug description:
  problems with starup

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-304 304.135-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.135  Tue Jan 17 15:26:26 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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
  DKMSKernelVersion: 4.13.0-26-generic
  Date: Thu Jan 11 11:25:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304, 304.135, 4.10.0-42-generic, x86_64: installed
   nvidia-304, 304.135, 4.4.0-109-generic, x86_64: installed
  DuplicateSignature: 
dkms:nvidia-304:304.135-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-304/304.135/build/nv-drm.c:80:15:
 error: initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: XFX Pine Group Inc. G86 [GeForce 8500 GT] [1682:230b]
  InstallationDate: Installed on 2017-11-01 (71 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ECS H61H2-CM
  PackageVersion: 304.135-0ubuntu0.16.04.1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=eb749f2f-d622-4f9d-bd2d-9e81f86f52e1 ro recovery nomodeset
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: nvidia-graphics-drivers-304
  Title: nvidia-304 304.135-0ubuntu0.16.04.1: nvidia-304 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/28/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.name: H61H2-CM
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/28/2013:svnECS:pnH61H2-CM:pvr:rvnECS:rnH61H2-CM:rvr1.0:cvnECS:ct3:cvr:
  dmi.product.name: H61H2-CM
  dmi.sys.vendor: ECS
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Jan 11 20:59:51 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB USB Keyboard KEYBOARD, id 8
   inputUSB USB Keyboard KEYBOARD, id 9
   inputUSB Wheel Mouse  MOUSE, id 10
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1742837/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Status: Fix Released => Triaged

** Changed in: oem-priority
 Assignee: (unassigned) => ethan.hsieh (ethan.hsieh)

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727716] Re: 17.10 sticky keys doesn t work

[Daniel van Vugt]

^^^
The above fix is scheduled for release upstream in the next preview release of 
gnome-shell 3.27 (3.27.2?). It doesn't appear to be backported to 3.26 but that 
would appear unlikely (I am guessing) due to the large number of patches 
involved.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1727716

Title:
  17.10 sticky keys doesn t work

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  hi

  I upgraded my system to 17.10 but now sticky keys doesn t work altough
  I reopen it in typing asist.

  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1727716/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742837] [NEW] nvidia-304 304.135-0ubuntu0.16.04.1: nvidia-304 kernel module failed to build

[darwin padilla]

Public bug reported:

problems with starup

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-304 304.135-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.135  Tue Jan 17 15:26:26 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
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
DKMSKernelVersion: 4.13.0-26-generic
Date: Thu Jan 11 11:25:31 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 nvidia-304, 304.135, 4.10.0-42-generic, x86_64: installed
 nvidia-304, 304.135, 4.4.0-109-generic, x86_64: installed
DuplicateSignature: 
dkms:nvidia-304:304.135-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-304/304.135/build/nv-drm.c:80:15:
 error: initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]
GraphicsCard:
 NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: XFX Pine Group Inc. G86 [GeForce 8500 GT] [1682:230b]
InstallationDate: Installed on 2017-11-01 (71 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: ECS H61H2-CM
PackageVersion: 304.135-0ubuntu0.16.04.1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=eb749f2f-d622-4f9d-bd2d-9e81f86f52e1 ro recovery nomodeset
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: nvidia-graphics-drivers-304
Title: nvidia-304 304.135-0ubuntu0.16.04.1: nvidia-304 kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/28/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.name: H61H2-CM
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/28/2013:svnECS:pnH61H2-CM:pvr:rvnECS:rnH61H2-CM:rvr1.0:cvnECS:ct3:cvr:
dmi.product.name: H61H2-CM
dmi.sys.vendor: ECS
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Jan 11 20:59:51 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB USB Keyboard KEYBOARD, id 8
 inputUSB USB Keyboard KEYBOARD, id 9
 inputUSB Wheel Mouse  MOUSE, id 10
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu1~16.04.4

** Affects: nvidia-graphics-drivers-304 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  nvidia-304 304.135-0ubuntu0.16.04.1: nvidia-304 kernel module failed
  to build

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  New

Bug description:
  problems with starup

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-304 304.135-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.135  Tue Jan 17 15:26:26 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/activ

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Daniel van Vugt]

Thanks Timo.

Hui: It's now in bionic-proposed. Can you test it with the Dell dock?

https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu3

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1718824

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Artful:
  New

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage

[bj mccormick]

Actually, disregard that last comment. I never rebooted after updating
snap using the ppa. I didn't think it was needed, but after a reboot
this morning and running the updated software fresh I have not had a
recurrence of the bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1723362

Title:
  gnome-software spams error messages to journald and causes 100% CPU
  usage

Status in GNOME Software:
  Unknown
Status in gnome-software package in Ubuntu:
  Invalid
Status in snapd-glib package in Ubuntu:
  In Progress

Bug description:
  gnome-software spams this message to journald:

  Okt 13 11:00:19 zenbook gnome-software[3582]: g_byte_array_remove_range: 
assertion 'index_ + length <= array->len' failed
  Okt 13 11:00:19 zenbook gnome-software[3582]: Ignoring unexpected response

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 10:58:38 2017
  InstallationDate: Installed on 2016-10-25 (352 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.1-0ubuntu1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to artful on 2017-10-04 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1723362/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory t

[emmanuel okeke]

Started having the same issues today after updating to the 
linux-image-4.13.0-26-generic.
Had to remove the binary driver, and switch to the X.Org version temporarily.

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

Title:
  nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed
  to build [nv-linux.h:199:2: error: #error "This driver requires the
  ability to change memory types!"]

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  not compiling after installation of linux-image-4.13.0-21-generic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.102-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-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.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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
  DKMSKernelVersion: 4.13.0-21-generic
  Date: Sat Jan  6 18:36:58 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DuplicateSignature: 
dkms:nvidia-340:340.102-0ubuntu0.16.04.2:/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:199:2:
 error: #error "This driver requires the ability to change memory types!"
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2016-04-26 (619 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  PackageVersion: 340.102-0ubuntu0.16.04.2
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039E202413102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039E202413102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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: Sat Jan  6 18:17:29 2018
  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.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1741671/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()

[Bug Watch Updater]

** Changed in: mutter (Fedora)
   Status: Unknown => Fix Committed

** Changed in: mutter (Fedora)
   Importance: Unknown => Undecided

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_read_events() from ospoll_wait()

Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid
Status in mutter package in Fedora:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/c27f5c4fef272640ec1027318712f0434c7c8857

  ---

  no idea how to reproduce

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Nov 13 13:55:16 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-15-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1507]
  InstallationDate: Installed on 2013-09-03 (1531 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? ()
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1728588] Re: Xwayland crashed with wl_registry@2: error 0: invalid global wl_output (36) after kernel: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22

[Timo Aaltonen]

*** This bug is a duplicate of bug 1731911 ***
https://bugs.launchpad.net/bugs/1731911

** This bug has been marked a duplicate of bug 1731911
   Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from 
FatalError() from xwl_read_events() from ospoll_wait()

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

Title:
  Xwayland crashed with wl_registry@2: error 0: invalid global wl_output
  (36) after kernel:  [drm:intel_mst_disable_dp [i915]] *ERROR* failed
  to update payload -22

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I turned off my screen for a few hours then turned it on again and my
  session was no longer there and i had to login again.

  The following lines from syslog at the time that i turned on the
  screen again look suspicious. My hypothesis is that the error from the
  Intel kernel driver caused the "Fatal server error" "wl_registry@2:
  error 0: invalid global wl_output (36)" in gnome-shell. Since the
  screen is actually still operational (after all, the computer didn't
  crash, only that session, and i was immediately shown the login screen
  and able to login again), what should have happened is that gnome-
  shell should have gracefully dealt with whatever happened without a
  fatal error.

  This is the first time this has happened, and it did not used to
  happen before my upgrade to Artful a few days ago.

  Oct 30 05:46:16 bshanks-SP4 kernel: [358036.641989] [drm:intel_mst_disable_dp 
[i915]] *ERROR* failed to update payload -22
  Oct 30 05:46:16 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is 
replacing existing [0x5563dd13c
  c40 Gjs_ShowAppsIcon.dash-item-container] connect method
  ...
  (a bunch of similar warnings about addSignalMethods)
  ...
  Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE)
  Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: Fatal server error:
  Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE) 
wl_registry@2: error 0: invalid global wl_output (36)
  Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 30 06:01:36 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-04-06 (572 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-26 (4 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Timo Aaltonen]

you need to ppa-purge all extra ppa's, and then try again

or just run 'sudo apt update && apt upgrade' after enabling -proposed,
that should work on top of my ppa (but not padoka's, since it has 17.3)

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()

[Launchpad Bug Tracker]

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

** Changed in: mutter (Ubuntu)
   Status: New => Confirmed

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_read_events() from ospoll_wait()

Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid
Status in mutter package in Fedora:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/c27f5c4fef272640ec1027318712f0434c7c8857

  ---

  no idea how to reproduce

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Nov 13 13:55:16 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-15-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1507]
  InstallationDate: Installed on 2013-09-03 (1531 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? ()
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742816] [NEW] compiz crashing

[Borislav]

Public bug reported:

Compiz is crashing dash
WIN Key not working
Dash not working
No panel
launcher disappears
sidebar disappears
alt tab not working

Any ideas for a solution?
I'll use lubuntu for workaround so i can use my system properly its fresh 
installed because of the but and thought that i F up  something and i pre 
installed ubuntu 16.04LTS but after some update i've got same problem.
I'm sorry for my bad English

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jan 12 01:04:08 2018
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:

InstallationDate: Installed on 2018-01-10 (1 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages xenial

** Description changed:

- Compiz is crashing dash 
- WIN Key not working 
- Dash not working 
- No panel 
- launcher disappears 
- sidebar disappears 
+ Compiz is crashing dash
+ WIN Key not working
+ Dash not working
+ No panel
+ launcher disappears
+ sidebar disappears
  alt tab not working
  
  Any ideas for a solution?
- I'll use lubuntu for workaround so i can use my system properly its fresh 
installed because of the but and thought that i F up  something and i pre 
installed ubuntu 16.04LTS but after some update i've got same problem
+ I'll use lubuntu for workaround so i can use my system properly its fresh 
installed because of the but and thought that i F up  something and i pre 
installed ubuntu 16.04LTS but after some update i've got same problem.
+ I'm sorry for my bad English
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 12 01:04:08 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
-  
+ 
  InstallationDate: Installed on 2018-01-10 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1742816

Title:
  compiz crashing

Status in nautilus package in Ubuntu:
  New

Bug description:
  Compiz is crashing dash
  WIN Key not working
  Dash not working
  No panel
  launcher disappears
  sidebar disappears
  alt tab not working

  Any ideas for a solution?
  I'll use lubuntu for workaround so i can use my system properly its fresh 
installed because of the but and thought that i F up  something and i pre 
installed ubuntu 16.04LTS but after some update i've got same problem.
  I'm sorry for my bad English

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 12 01:04:08 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:

  InstallationDate: Installed on 2018-01-10 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[MeanJim]

I'm affected by this bug as well.  I tried the -proposed package, but
I'm getting the same error as Emmanuel Grumbach pasted above.

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[Leo Pilachowski]

*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594

Thanks.  I saw that and that the comment on the "fix" was entered 8
minutes after my post above. But, I see there may be dependency problems
installing that fix.

LP

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

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  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: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1741447/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.

[Desktop-packages] [Bug 1742733] Re: Display Bug

[Timo Aaltonen]

*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594

** This bug has been marked a duplicate of bug 1735594
   [regression] compiz crashes after Mesa upgrade

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

Title:
  Display Bug

Status in xorg package in Ubuntu:
  New

Bug description:
  When I attempt to use the launcher it will disappear as well as
  everything else on the screen. It comes back after a few seconds, but
  I am unable to use the dash search at all. If I mouse over the icon
  for the search it immediately makes all windows, icons and launcher
  disappear. I am unable to power off my computer as well. When I click
  shut down it does the same thing as trying to click the search option.
  It never did this until the recent most recent updates.

  Ubuntu 16.04.3 LTS
  Panasonic Toughbook CF-52 Laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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: Thu Jan 11 11:09:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile 4 Series 
Chipset Integrated Graphics Controller [10f7:8338]
 Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile 4 Series 
Chipset Integrated Graphics Controller [10f7:8338]
  InstallationDate: Installed on 2017-12-03 (38 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Matsushita Electric Industrial Co.,Ltd. CF-52GCMBXAM
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-26-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.50L16
  dmi.board.name: CF52-2L
  dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.board.version: 1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.50L16:bd08/11/2008:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-52GCMBXAM:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF52-2L:rvr1:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
  dmi.product.family: CF52-2L
  dmi.product.name: CF-52GCMBXAM
  dmi.product.version: 002
  dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Jan 11 07:56:31 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()

[Timo Aaltonen]

the fedora bug says it's a bug in mutter, fixed by

https://git.gnome.org/browse/mutter/commit/?h=gnome-3-26&id=cde5454622d99320a66f2fd352df132a4bfdab4b

** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Invalid

** Bug watch added: Red Hat Bugzilla #1500325
   https://bugzilla.redhat.com/show_bug.cgi?id=1500325

** Changed in: xorg-server (Fedora)
   Importance: Undecided => Unknown

** Changed in: xorg-server (Fedora)
   Status: Confirmed => Unknown

** Changed in: xorg-server (Fedora)
 Remote watch: Red Hat Bugzilla #1511681 => Red Hat Bugzilla #1500325

** Package changed: xorg-server (Fedora) => mutter (Fedora)

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_read_events() from ospoll_wait()

Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Invalid
Status in mutter package in Fedora:
  Unknown

Bug description:
  https://errors.ubuntu.com/problem/c27f5c4fef272640ec1027318712f0434c7c8857

  ---

  no idea how to reproduce

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Nov 13 13:55:16 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-15-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1507]
  InstallationDate: Installed on 2013-09-03 (1531 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? ()
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742739] Re: Xwayland crashes after unlocking screen

[Timo Aaltonen]

*** This bug is a duplicate of bug 1731911 ***
https://bugs.launchpad.net/bugs/1731911

** This bug has been marked a duplicate of bug 1731911
   Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from 
FatalError() from xwl_read_events() from ospoll_wait()

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

Title:
  Xwayland crashes after unlocking screen

Status in xorg-server package in Ubuntu:
  New

Bug description:
  When I unlock the screen from screensaver sometimes, but not always,
  Xwayland coredumps.

  $ gdb /usr/bin/Xwayland ~/core
  GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1
  Copyright (C) 2017 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /usr/bin/Xwayland...(no debugging symbols found)...done.
  [New LWP 6786]
  [New LWP 6787]
  [New LWP 6790]
  [New LWP 6788]
  [New LWP 6789]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/bin/Xwayland :0 -rootless -terminate -core 
-listen 4 -listen 5 -displayfd'.
  Program terminated with signal SIGABRT, Aborted.
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
  51../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
  [Current thread is 1 (Thread 0x7f9140a68a80 (LWP 6786))]
  (gdb) bt full
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
  set = {__val = {171515904, 0, 0, 0, 0, 140261709342601, 
94745322873264, 67108868, 140261785854288, 0, 94745365252208, 94745321417623, 
  0, 94745348741304, 94745366391120, 94745365252128}}
  pid = 
  tid = 
  #1  0x7f913db03f5d in __GI_abort () at abort.c:90
  save_stage = 2
  act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0}, 
sa_mask = {__val = {94745348741304, 94745366391120, 
94745365252128, 140720405293760, 140720405293764, 12884901928, 
94745363065648, 0, 7425099061155604736, 0, 94745363176736, 11, 
67108868, 140261785854288, 7425099061155604736, 0}}, sa_flags = 
-1655605696, sa_restorer = 0x7ffc05c52cb0}
  sigs = {__val = {32, 0 }}
  #2  0x562b9d50913a in OsAbort ()
  No symbol table info available.
  #3  0x562b9d50ec53 in ?? ()
  No symbol table info available.
  #4  0x562b9d50fa75 in FatalError ()
  No symbol table info available.
  #5  0x562b9d39543f in ?? ()
  No symbol table info available.
  #6  0x562b9d506cb1 in ?? ()
  No symbol table info available.
  #7  0x562b9d4ffcbb in WaitForSomething ()
  No symbol table info available.
  #8  0x562b9d4cb9f3 in ?? ()
  No symbol table info available.
  #9  0x562b9d4cfc90 in ?? ()
  No symbol table info available.
  #10 0x7f913daec1c1 in __libc_start_main (main=0x562b9d394a60, argc=11, 
argv=0x7ffc05c53be8, init=, fini=, 
  rtld_fini=, stack_end=0x7ffc05c53bd8) at 
../csu/libc-start.c:308
  result = 
  unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 8252881868666068147, 
94745321359984, 140720405298144, 0, 0, 2388897359761923251, 
  2449221155427998899}, mask_was_saved = 0}}, priv = {pad = 
{0x0, 0x0, 0x7ffc05c53c48, 0x7f9140abc150}, data = {prev = 0x0, 
cleanup = 0x0, canceltype = 96812104}}}
  not_first_call = 
  #11 0x562b9d394a9a in _start ()
  No symbol table info available.

  Any idea what is going on here?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,imgjpeg,decor,mousepoll,move,compiztoolbox,regex,place,commands,imgpng,grid,gnomecompat,dbus,resize,screenshot,animation,session,fade,cube,workarounds,rotate,scale,unitymtgrabhandles,expo,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Jan 11 17:02:07 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  Gra

[Desktop-packages] [Bug 1742801] [NEW] [HDA-Intel - HDA NVidia, playback] No sound at all

[Salam]

Public bug reported:

the device is well connected and I am hearing the noise of the speakers
they do when they are connected but if open a youtube or a site to learn
a language that uses the sound ,there is no sound at all,even when I
open the system setting and make a test of the sound all it seems
function well but no sound

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  theseer9   2534 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jan 11 22:45:44 2018
InstallationDate: Installed on 2018-01-05 (6 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: Built-in Audio - HDA NVidia
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  theseer9   2534 F pulseaudio
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA NVidia, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: PBCBR00.P27
dmi.board.vendor: Packard Bell BV
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Packard Bell BV
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrPBCBR00.P27:bd11/20/2008:svnPackardBellBV:pnIMEDIAA3507SP:pvrPTU080Y005:rvnPackardBellBV:rn:rvr1.0:cvnPackardBellBV:ct3:cvr1.0:
dmi.product.name: IMEDIA A3507 SP
dmi.product.version: PTU080Y005
dmi.sys.vendor: Packard Bell BV

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1742801

Title:
  [HDA-Intel - HDA NVidia, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  the device is well connected and I am hearing the noise of the
  speakers they do when they are connected but if open a youtube or a
  site to learn a language that uses the sound ,there is no sound at
  all,even when I open the system setting and make a test of the sound
  all it seems function well but no sound

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  theseer9   2534 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 11 22:45:44 2018
  InstallationDate: Installed on 2018-01-05 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: Built-in Audio - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  theseer9   2534 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA NVidia, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: PBCBR00.P27
  dmi.board.vendor: Packard Bell BV
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Packard Bell BV
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrPBCBR00.P27:bd11/20/2008:svnPackardBellBV:pnIMEDIAA3507SP:pvrPTU080Y005:rvnPackardBellBV:rn:rvr1.0:cvnPackardBellBV:ct3:cvr1.0:
  dmi.product.name: IMEDIA A3507 SP
  dmi.product.version: PTU080Y005
  dmi.sys.vendor: Packard Bell BV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742801/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1729728] Re: window picker is broken in 3.26

[Brian Murray]

Hello Eugene, or anyone else affected,

Accepted gnome-applets into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
applets/3.26.0-1ubuntu0.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-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

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

** Changed in: gnome-applets (Ubuntu Artful)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-artful

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-applets in Ubuntu.
https://bugs.launchpad.net/bugs/1729728

Title:
  window picker is broken in 3.26

Status in gnome-applets package in Ubuntu:
  Fix Released
Status in gnome-applets source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  One of the applets shipped in gnome-applets package is broken. It crashes on 
startup because of missing GSettings schema file.

  [Test Case]
  * Log into GNOME Flashback session.
  * Try to add the “Window picker” applet to the panel.

  Expected result: panel does not crash, applet is added.

  [Proposed Fix]
  The proposed fix just makes the gsettings schema installed:

  https://git.gnome.org/browse/gnome-applets/commit/?id=6aedbc3a6af54190

  [Regression Potential]
  None, as the fix just adds a missing file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1729728/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Emmanuel Grumbach]

$ sudo apt-get install libgl1-mesa-dri/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '17.2.4-0ubuntu1~16.04.3' (Ubuntu:16.04/xenial-proposed 
[amd64]) for 'libgl1-mesa-dri'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 indicator-bluetooth : Depends: unity-control-center but it is not going to be 
installed or
gnome-control-center but it is not going to be 
installed or
ubuntu-system-settings but it is not going to 
be installed
   Depends: gnome-bluetooth but it is not going to be 
installed or
ubuntu-system-settings but it is not going to 
be installed
 liboxideqt-qmlplugin : Depends: libqt5quick5 (>= 5.0.2) but it is not going to 
be installed or
 libqt5quick5-gles (>= 5.0.2) but it is not 
going to be installed
 liboxideqtcore0 : Depends: libqt5gui5 (>= 5.4.0) but it is not going to be 
installed or
libqt5gui5-gles (>= 5.4.0) but it is not going to 
be installed
 liboxideqtquick0 : Depends: libqt5gui5 (>= 5.0.2) but it is not going to be 
installed or
 libqt5gui5-gles (>= 5.0.2) but it is not going to 
be installed
Depends: libqt5quick5 (>= 5.2.0) but it is not going to be 
installed or
 libqt5quick5-gles (>= 5.2.0) but it is not going 
to be installed
 libqmenumodel0 : Depends: libqt5gui5 (>= 5.0.2) but it is not going to be 
installed or
   libqt5gui5-gles (>= 5.0.2) but it is not going to be 
installed
 libqt5multimedia5 : Depends: libqt5gui5 (>= 5.2.0) but it is not going to be 
installed or
  libqt5gui5-gles (>= 5.2.0) but it is not going to 
be installed
 libqt5multimediaquick-p5 : Depends: libqt5gui5 (>= 5.0.2) but it is not going 
to be installed or
 libqt5gui5-gles (>= 5.0.2) but it is not 
going to be installed
Depends: libqt5quick5 (>= 5.4.0) but it is not 
going to be installed or
 libqt5quick5-gles (>= 5.4.0) but it is not 
going to be installed
 libqt5widgets5 : Depends: libqt5gui5 (>= 5.5.0) but it is not going to be 
installed or
   libqt5gui5-gles (>= 5.5.0) but it is not going to be 
installed
 libubuntugestures5 : Depends: libqt5gui5 (>= 5.0.2) but it is not going to be 
installed or
   libqt5gui5-gles (>= 5.0.2) but it is not going 
to be installed
  Depends: libqt5quick5 (>= 5.0.2) but it is not going to 
be installed or
   libqt5quick5-gles (>= 5.0.2) but it is not going 
to be installed
 libubuntutoolkit5 : Depends: libqt5gui5 (>= 5.0.2) but it is not going to be 
installed or
  libqt5gui5-gles (>= 5.0.2) but it is not going to 
be installed
 qml-module-io-thp-pyotherside : Depends: libqt5gui5 (>= 5.0.2) but it is not 
going to be installed or
  libqt5gui5-gles (>= 5.0.2) but it is 
not going to be installed
 Depends: libqt5quick5 (>= 5.0.2) but it is not 
going to be installed or
  libqt5quick5-gles (>= 5.0.2) but it 
is not going to be installed
 qml-module-qtquick-layouts : Depends: libqt5gui5 (>= 5.5.0) but it is not 
going to be installed or
   libqt5gui5-gles (>= 5.5.0) but it is not 
going to be installed
  Depends: libqt5quick5 (>= 5.2.0) but it is not 
going to be installed or
   libqt5quick5-gles (>= 5.2.0) but it is 
not going to be installed
 qml-module-qtquick-window2 : Depends: libqt5quick5 (>= 5.0.2) but it is not 
going to be installed or
   libqt5quick5-gles (>= 5.0.2) but it is 
not going to be installed
 qml-module-ubuntu-layouts : Depends: libqt5quick5 (>= 5.0.2) but it is not 
going to be installed or
  libqt5quick5-gles (>= 5.0.2) but it is 
not going to be installed
 qml-module-ubuntu-performancemetrics : Depends: libqt5gui5 (>= 5.0.2) but it 
is not going to be installed or
 libqt5gui5-gles (>= 5.0.2) but 
it is not going to be installed
Depends: libqt5quick5 (>= 5.0.2) but it 
is not going to be installed or
 libqt5quick5-gles (>= 5.0.2) 
but it is no

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Timo Aaltonen]

your mirror hasn't been synced yet, use archive.ubuntu.com in the
meantime

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Emmanuel Grumbach]

$ sudo apt-get install libgl1-mesa-dri/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Release 'xenial-proposed' for 'libgl1-mesa-dri' was not found

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Timo Aaltonen]

"mesa" is the source package, try "sudo apt install libgl1-mesa-dri"...
that should pull everything

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1741348] Re: gnome-flashback/gnome-panel: bottom right workspace selector will not accept preference change to more than 1 workspace

[Alberts Muktupāvels]

sudo apt-get install compizconfig-settings-manager

Above will install settings manager if it is not already installed. Then
open application, click on `General Options` and select `Desktop Size`
tab.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1741348

Title:
  gnome-flashback/gnome-panel: bottom right workspace selector will not
  accept preference change to more than 1 workspace

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  xwininfo: Window id: 0x2200016 "Bottom Expanded Edge Panel"

    Absolute upper-left X:  0
    Absolute upper-left Y:  1416
    Relative upper-left X:  0
    Relative upper-left Y:  0
    Width: 2560
    Height: 24
    Depth: 32
    Visual: 0x82
    Visual Class: TrueColor
    Border width: 0
    Class: InputOutput
    Colormap: 0x222 (not installed)
    Bit Gravity State: NorthWestGravity
    Window Gravity State: NorthWestGravity
    Backing Store State: NotUseful
    Save Under State: no
    Map State: IsViewable
    Override Redirect State: no
    Corners:  +0+1416  -0+1416  -0-0  +0-0
    -geometry 2560x24+0-0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-panel 1:3.24.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Jan  4 15:32:50 2018
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.gnome-panel.layout' b'object-id-list' b"['menu-bar', 
'show-destkop', 'window-list', 'workspace-switcher', 'launcher', 'launcher-0', 
'launcher-1', 'launcher-2', 'launcher-3', 'launcher-4', 'launcher-5', 
'launcher-7', 'launcher-8', 'launcher-10', 'launcher-12', 'launcher-13', 
'launcher-6', 'launcher-9', 'launcher-14', 'notification-area', 
'indicator-applet-complete', 'launcher-11']"
   b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['top-panel', 
'bottom-panel']"

  InstallationDate: Installed on 2017-01-05 (364 days ago)
  InstallationMedia: It
  SourcePackage: gnome-panel
  UpgradeStatus: Upgraded to artful on 2017-10-22 (74 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1741348/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742449] Re: nvidia-340.104 dkms fails to build against 4.13.0-26

[trzalica]

I've also tested kernel 4.4.111 and it also works with nvidia-340 and in
the article which I attached in the previous comment it says that 4.4,
4.9 and 4.14 are all updated with security patches... Have I missed
something?

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

Title:
  nvidia-340.104 dkms fails to build against 4.13.0-26

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Laptops like my Thinkpad W510 cannot use newer drivers than nvidia-340
  because support for their old GPU was dropped in newer revisions.

  Meltdown/Spectre is upon us and I got 4.13.0-26 today, but
  nvidia-340's dkms driver will not build, for the common reason most
  nvidia drivers won't build against the new kernels. Looking at
  nvidia's official announcement I did not see a plan or release date
  for updates to nvidia-340, yet.

  Since my laptop is my own, I'm running with the pre-KPTI 4.10.0-42 for
  now, but figured I should report this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1742449/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory t

[Richard Collins]

going back to 4.10 works. Otherwise, everything appears as normal except
I can't login to any of my user accounts (local machine, ubuntu
usernames). Logging in appears to work, and then I'm back to the login
screen again.

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

Title:
  nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed
  to build [nv-linux.h:199:2: error: #error "This driver requires the
  ability to change memory types!"]

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  not compiling after installation of linux-image-4.13.0-21-generic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.102-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-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.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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
  DKMSKernelVersion: 4.13.0-21-generic
  Date: Sat Jan  6 18:36:58 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DuplicateSignature: 
dkms:nvidia-340:340.102-0ubuntu0.16.04.2:/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:199:2:
 error: #error "This driver requires the ability to change memory types!"
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2016-04-26 (619 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  PackageVersion: 340.102-0ubuntu0.16.04.2
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039E202413102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039E202413102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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: Sat Jan  6 18:17:29 2018
  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.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1741671/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1741348] Re: gnome-flashback/gnome-panel: bottom right workspace selector will not accept preference change to more than 1 workspace

[Stephen Crowley]

where would one find that?


On 01/11/2018 12:13 PM, Alberts Muktupāvels wrote:
> This is known bug, you have to use CompizConfig Settings Manager to
> change that.
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1741348

Title:
  gnome-flashback/gnome-panel: bottom right workspace selector will not
  accept preference change to more than 1 workspace

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  xwininfo: Window id: 0x2200016 "Bottom Expanded Edge Panel"

    Absolute upper-left X:  0
    Absolute upper-left Y:  1416
    Relative upper-left X:  0
    Relative upper-left Y:  0
    Width: 2560
    Height: 24
    Depth: 32
    Visual: 0x82
    Visual Class: TrueColor
    Border width: 0
    Class: InputOutput
    Colormap: 0x222 (not installed)
    Bit Gravity State: NorthWestGravity
    Window Gravity State: NorthWestGravity
    Backing Store State: NotUseful
    Save Under State: no
    Map State: IsViewable
    Override Redirect State: no
    Corners:  +0+1416  -0+1416  -0-0  +0-0
    -geometry 2560x24+0-0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-panel 1:3.24.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Jan  4 15:32:50 2018
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.gnome-panel.layout' b'object-id-list' b"['menu-bar', 
'show-destkop', 'window-list', 'workspace-switcher', 'launcher', 'launcher-0', 
'launcher-1', 'launcher-2', 'launcher-3', 'launcher-4', 'launcher-5', 
'launcher-7', 'launcher-8', 'launcher-10', 'launcher-12', 'launcher-13', 
'launcher-6', 'launcher-9', 'launcher-14', 'notification-area', 
'indicator-applet-complete', 'launcher-11']"
   b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['top-panel', 
'bottom-panel']"

  InstallationDate: Installed on 2017-01-05 (364 days ago)
  InstallationMedia: It
  SourcePackage: gnome-panel
  UpgradeStatus: Upgraded to artful on 2017-10-22 (74 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1741348/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory t

[Richard Collins]

nVidia GeForce GTX 750Ti
Ubuntu 16.04 LTS Desktop amd64

Before Restart:
uname -a: Linux Dell-Precision-3620 4.10.0-42-generic #46~16.04.1-Ubuntu SMP 
Mon Dec 4 15:57:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed
  to build [nv-linux.h:199:2: error: #error "This driver requires the
  ability to change memory types!"]

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  not compiling after installation of linux-image-4.13.0-21-generic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.102-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-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.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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
  DKMSKernelVersion: 4.13.0-21-generic
  Date: Sat Jan  6 18:36:58 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DuplicateSignature: 
dkms:nvidia-340:340.102-0ubuntu0.16.04.2:/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:199:2:
 error: #error "This driver requires the ability to change memory types!"
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2016-04-26 (619 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  PackageVersion: 340.102-0ubuntu0.16.04.2
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039E202413102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039E202413102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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: Sat Jan  6 18:17:29 2018
  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.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1741671/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742791] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1742791

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  System initiated bug report, after automatic upgrade from 14.04 to
  16.04 reported problems.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Jan 11 20:15:07 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-07-01 (2386 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-01-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1742791/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742791] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Merciman]

Public bug reported:

System initiated bug report, after automatic upgrade from 14.04 to 16.04
reported problems.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Thu Jan 11 20:15:07 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2011-07-01 (2386 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2018-01-11 (0 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1742791

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  System initiated bug report, after automatic upgrade from 14.04 to
  16.04 reported problems.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Jan 11 20:15:07 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-07-01 (2386 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-01-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1742791/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742449] Re: nvidia-340.104 dkms fails to build against 4.13.0-26

[trzalica]

Yes they are, take a look at this article:
http://news.softpedia.com/news/linux-kernels-4-14-13-4-9-76-and-4-4-111
-bring-more-security-fixes-update-now-519321.shtml

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

Title:
  nvidia-340.104 dkms fails to build against 4.13.0-26

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Laptops like my Thinkpad W510 cannot use newer drivers than nvidia-340
  because support for their old GPU was dropped in newer revisions.

  Meltdown/Spectre is upon us and I got 4.13.0-26 today, but
  nvidia-340's dkms driver will not build, for the common reason most
  nvidia drivers won't build against the new kernels. Looking at
  nvidia's official announcement I did not see a plan or release date
  for updates to nvidia-340, yet.

  Since my laptop is my own, I'm running with the pre-KPTI 4.10.0-42 for
  now, but figured I should report this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1742449/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742713] Re: Move mesa-vulkan-drivers from Univers to Main and install by default in Ubuntu 18.04

[Hans Joachim Desserud]

*** This bug is a duplicate of bug 1742714 ***
https://bugs.launchpad.net/bugs/1742714

** This bug has been marked a duplicate of bug 1742714
   Move mesa-vulkan-drivers from Univers to Main and install by default in 
Ubuntu 18.04

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

Title:
  Move mesa-vulkan-drivers from Univers to Main and install by default
  in Ubuntu 18.04

Status in mesa package in Ubuntu:
  New

Bug description:
  A Vulkan related bug was filed at
  https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in
  a related note, having mesa-vulkan-drivers moved from Universe to Main
  and installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten
  mature and since the OpenGL drivers are installed, it will very
  complimentary.

  Having this available will aid game developers and users who load up a
  Vulkan application and get errors. They may not know to enable
  Universe in their Software Manager and to manually install mesa-
  vulkan-drivers for their video card. They may just load up that Vulkan
  application, find out it doesn't work, and then give up on it. We
  cannot have that for future adoption of the API.

  Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV
  are implementing experimental support for Vulkan. For Ubuntu being a
  leader for the desktop and a base for GNU/Linux gaming, shouldn't it
  be painless for Ubuntu 18.04? Especially since it is a long term
  release for 5 years.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Emmanuel Grumbach]

I am sorry, but I can't find how to install that package.

I did:

$ sudo apt-get update 
Hit:1 http://il.archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://il.archive.ubuntu.com/ubuntu xenial-updates InRelease  

Hit:3 http://il.archive.ubuntu.com/ubuntu xenial-backports InRelease

Hit:4 http://il.archive.ubuntu.com/ubuntu xenial-proposed InRelease 
  
Hit:5 http://security.ubuntu.com/ubuntu xenial-security InRelease   
  
Ign:6 http://linux.dropbox.com/ubuntu xenial InRelease  
 
Ign:7 http://linux.dropbox.com/ubuntu wily InRelease
Hit:8 http://linux.dropbox.com/ubuntu xenial Release
Hit:9 http://linux.dropbox.com/ubuntu wily Release 
Reading package lists... Done  


So clearly, -proposed is there.

And then:
$ sudo apt-get install mesa/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Unable to locate package mesa


What package exactly should I be looking for?

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[Timo Aaltonen]

*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594

forget about those ppa's and follow the main bug, a fix has been
uploaded to xenial-proposed already

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

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  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: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1741447/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packag

[Desktop-packages] [Bug 1742714] Re: Move mesa-vulkan-drivers from Univers to Main and install by default in Ubuntu 18.04

[Launchpad Bug Tracker]

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

** Changed in: mesa (Ubuntu)
   Status: New => Confirmed

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

Title:
  Move mesa-vulkan-drivers from Univers to Main and install by default
  in Ubuntu 18.04

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  A Vulkan related bug was filed at
  https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in
  a related note, having mesa-vulkan-drivers moved from Universe to Main
  and installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten
  mature and since the OpenGL drivers are installed, it will very
  complimentary.

  Having this available will aid game developers and users who load up a
  Vulkan application and get errors. They may not know to enable
  Universe in their Software Manager and to manually install mesa-
  vulkan-drivers for their video card. They may just load up that Vulkan
  application, find out it doesn't work, and then give up on it. We
  cannot have that for future adoption of the API.

  Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV
  are implementing experimental support for Vulkan. For Ubuntu being a
  leader for the desktop and a base for GNU/Linux gaming, shouldn't it
  be painless for Ubuntu 18.04? Especially since it is a long term
  release for 5 years.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Description changed:

  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or kernel
  graphics driver bug. The unvisible 3/4 part of the screen seems to be
  fully operational. I may open an application window in it and drag it to
  the visible 1/4 part of the screen. Besides the screen display issue the
  system seems to run properly. I was able to report this bug while
- running the 4.13.0-26-generic kernel.
+ running the 4.13.0-26-generic kernel. The laptop is Samsung N130.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel. The laptop is
  Samsung N130.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Attachment added: "xfce.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+attachment/5035300/+files/xfce.jpg

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Attachment added: "console.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+attachment/5035301/+files/console.jpg

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Attachment added: "dmesg_linux_4.10.0-42-generic.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+attachment/5035302/+files/dmesg_linux_4.10.0-42-generic.txt

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Attachment added: "dmesg_linux_4.13.0-26-generic.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+attachment/5035303/+files/dmesg_linux_4.13.0-26-generic.txt

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Attachment added: "lspci-vvv.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+attachment/5035306/+files/lspci-vvv.txt

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Attachment added: "lshw.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+attachment/5035304/+files/lshw.txt

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Attachment added: "lsmod.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+attachment/5035305/+files/lsmod.txt

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1456016] Re: Xorg nouveau graphics driver freezes or crashes

[Diogo Gomes]

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  Xorg nouveau graphics driver freezes or crashes

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  I'm not saying xorg is the culprit, I think problem is graphics related thus 
it happens when I choose Nouveau graphics driver instead of proprietary Nvidia.
  My GPU is an integrated one and uses shared RAM, this bug is more frequent 
when hardware settings are "AUTODETECT FRAME BUFFER SIZE=enabled" otherwise 
when it's set to "FIXED=256MB" it isn't that frequent.
  The steps to reproduce this bug are not pretty clear, this crash happens at 
least once a day, appearently when there's too much memory in use.
  I used to use "Nvidia proprietary driver" with Ubuntu 14.10 with less 
problems but some crashes correctly managed by system without closing any 
application but with Ubuntu 15.04 this crashes make all applications get 
closed, that's why I decided to change to Nouveau but it gets so slow. I'm 
really considering rollback to Ubuntu 14.10 which caused less problems.
  When Systems freezes both keyboard and mouse get irresponsive too. I've 
collected some data through SSH which are attached:
   "Xorg.0.freezetime.log" is "/var/log/Xorg.0.log" at Freeze moment.
   "kikedmesg.txt" is "dmsg.txt" at Freeze moment.
  Please contact me with directions to help in solving this issue.
  Some Info:
  1)Ubuntu 15.04 64 bits
  2)xserver-xorg-video-nouveau version 1:1.0.11-1ubuntu2build1

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.17.2-0ubuntu1
  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: Sun May 17 20:08:57 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053b] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:82b3]
  InstallationDate: Installed on 2015-05-02 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=73fab811-79d9-488b-9316-7e0df86fbc90 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xserver-xorg-video-nouveau
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0709
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-VM HDMI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.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.:bvr0709:bd12/05/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-VMHDMI:rvrRevx.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.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Sun May 17 19:17:29 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   in

[Desktop-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~16.04.3 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

** Changed in: mesa (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Tags removed: verification-done-xenial
** Tags added: verification-needed-xenial

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Łukasz Zemczak]

Hello Falk, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~16.04.3 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

** Changed in: mesa (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742756] Re: 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Description changed:

  After upgrading to kernel 4.13.0-26-generic 3/4 of screen is unreadable.
- It is both in xorg/xfce and terminal after pressing ctrl+alt+F1.
- Everything works perfect when I reboot my laptop with older
- 4.10.0-42-generic kernel. It may be also a kernel graphics driver bug
- rather than xorg bug. Now I'm wiritng this description on a 1/4 part of
- the screen that looks ok. Besides the screen display issue the system
- seems to run ok.
+ It is both in xorg/xfce and conole (ctrl+alt+F1). Everything works
+ perfect when I reboot my laptop with older 4.10.0-42-generic kernel. I'm
+ not sure whether it is Xorg bug or kernel graphics driver bug. The
+ unvisible 3/4 part of the screen seems to be fully operational. I may
+ open an application window in it and drag it to the visible 1/4 part of
+ the screen. Besides the screen display issue the system seems to run
+ properly.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  After upgrading to kernel 4.13.0-26-generic 3/4 of screen is unreadable.
- It is both in xorg/xfce and conole (ctrl+alt+F1). Everything works
+ It is both in xorg/xfce and console (ctrl+alt+F1). Everything works
  perfect when I reboot my laptop with older 4.10.0-42-generic kernel. I'm
  not sure whether it is Xorg bug or kernel graphics driver bug. The
  unvisible 3/4 part of the screen seems to be fully operational. I may
  open an application window in it and drag it to the visible 1/4 part of
  the screen. Besides the screen display issue the system seems to run
  properly.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  After upgrading to kernel 4.13.0-26-generic 3/4 of screen is unreadable.
  It is both in xorg/xfce and console (ctrl+alt+F1). Everything works
  perfect when I reboot my laptop with older 4.10.0-42-generic kernel. I'm
  not sure whether it is Xorg bug or kernel graphics driver bug. The
  unvisible 3/4 part of the screen seems to be fully operational. I may
  open an application window in it and drag it to the visible 1/4 part of
  the screen. Besides the screen display issue the system seems to run
- properly.
+ properly. I was able to report this bug while running the
+ 4.13.0-26-generic kernel.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- 3/4 of XFCE and console screen is unreadable
+ [Xubuntu] 3/4 of XFCE and console screen is unreadable

** Description changed:

- After upgrading to kernel 4.13.0-26-generic 3/4 of screen is unreadable.
- It is both in xorg/xfce and console (ctrl+alt+F1). Everything works
- perfect when I reboot my laptop with older 4.10.0-42-generic kernel. I'm
- not sure whether it is Xorg bug or kernel graphics driver bug. The
- unvisible 3/4 part of the screen seems to be fully operational. I may
- open an application window in it and drag it to the visible 1/4 part of
- the screen. Besides the screen display issue the system seems to run
- properly. I was able to report this bug while running the
- 4.13.0-26-generic kernel.
+ After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
+ unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
+ Everything works perfect when I reboot my laptop with older
+ 4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or kernel
+ graphics driver bug. The unvisible 3/4 part of the screen seems to be
+ fully operational. I may open an application window in it and drag it to
+ the visible 1/4 part of the sc

[Desktop-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[Leo Pilachowski]

*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594

There appear to be two ppa locations to get the fix for 16.04 i386:

ppa: paulo-miguel-dias / pkppa

ppa:tjaalton/ppa

Please tell us again how to get and try out the possible fix.  I am
experienced but new to Ubuntu but need to get a older system up and
running asap on 16.04.

Leo

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

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  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: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/17

[Desktop-packages] [Bug 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory t

[Diogo Gomes]

This is really bad for one of my computers.

The open source drivers crash the system since a few years ago and after
this update I can't use the proprietary drivers there.

Boot with old kernel image from GRUB menu do not seems a workaround
because after the Meltdown and Spectre we can't stand with an outdated
kernel.

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

Title:
  nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed
  to build [nv-linux.h:199:2: error: #error "This driver requires the
  ability to change memory types!"]

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  not compiling after installation of linux-image-4.13.0-21-generic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.102-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-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.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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
  DKMSKernelVersion: 4.13.0-21-generic
  Date: Sat Jan  6 18:36:58 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DuplicateSignature: 
dkms:nvidia-340:340.102-0ubuntu0.16.04.2:/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:199:2:
 error: #error "This driver requires the ability to change memory types!"
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2016-04-26 (619 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  PackageVersion: 340.102-0ubuntu0.16.04.2
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039E202413102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039E202413102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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: Sat Jan  6 18:17:29 2018
  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.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1741671/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742769] [NEW] Pulse Audio Won't Run After BionicBeaver Update

[Stephen Allen]

Public bug reported:

As per the bug report, I've noticed that Pulse Audio is segfaulting.
Happened after the large update to Bionic Beaver this morning (Thursday
Jan 11/18).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu3
ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
Uname: Linux 4.14.0-16-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: GNOME
Date: Thu Jan 11 13:32:21 2018
InstallationDate: Installed on 2017-12-20 (21 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 LE R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
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:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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


** Tags: amd64 bionic package-from-proposed pulseaudio sound wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1742769

Title:
  Pulse Audio Won't Run After BionicBeaver Update

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  As per the bug report, I've noticed that Pulse Audio is segfaulting.
  Happened after the large update to Bionic Beaver this morning
  (Thursday Jan 11/18).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
  Uname: Linux 4.14.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Thu Jan 11 13:32:21 2018
  InstallationDate: Installed on 2017-12-20 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1385292] Re: can't rename files in nautilus

[Dennis Baudys]

The problem still exists here (e.g. using nemo and trying to rename
files does not work in any way). I'm living with this very annoying bug
since years. Frustrating.

DistroRelease: Linux Mint 17.3 Rosa
Uname: Linux 4.4.0-109-generic #132~14.04.1-Ubuntu SMP
NonfreeKernelModules: nvidia
Architecture: amd64
CurrentDesktop: Cinnamon

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1385292

Title:
  can't rename files in nautilus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Triaged

Bug description:
  sometimes can't rename files with F2 button. It is higlight changing,
  but nothing gonna happen, it is not responding

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 24 17:48:33 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-10-24 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1385292/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1738651] Re: top right panel in Gnome Metacity Freezes a few minutes after login

[Alberts Muktupāvels]

Might be problem with indicator-applet. Does journalctl have errors
and/or warnings related to indicator-applet when it freezes?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1738651

Title:
  top right panel in Gnome Metacity Freezes a few minutes after login

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  Hello,

  I've reinstalled Ubuntu 17.10, and the top right panel in Gnome
  Metacity fails to respond after a minute or so.

  The left click doesn't work, but the right click does work (although
  it doesn't fix anything, it only says "About" which is useless).  The
  upper left "Applications" and "Places" still works.

  I should also add that the time freezes as well.

  -Dave

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1738651/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1741348] Re: gnome-flashback/gnome-panel: bottom right workspace selector will not accept preference change to more than 1 workspace

[Alberts Muktupāvels]

This is known bug, you have to use CompizConfig Settings Manager to
change that.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1741348

Title:
  gnome-flashback/gnome-panel: bottom right workspace selector will not
  accept preference change to more than 1 workspace

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  xwininfo: Window id: 0x2200016 "Bottom Expanded Edge Panel"

    Absolute upper-left X:  0
    Absolute upper-left Y:  1416
    Relative upper-left X:  0
    Relative upper-left Y:  0
    Width: 2560
    Height: 24
    Depth: 32
    Visual: 0x82
    Visual Class: TrueColor
    Border width: 0
    Class: InputOutput
    Colormap: 0x222 (not installed)
    Bit Gravity State: NorthWestGravity
    Window Gravity State: NorthWestGravity
    Backing Store State: NotUseful
    Save Under State: no
    Map State: IsViewable
    Override Redirect State: no
    Corners:  +0+1416  -0+1416  -0-0  +0-0
    -geometry 2560x24+0-0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-panel 1:3.24.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Jan  4 15:32:50 2018
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.gnome-panel.layout' b'object-id-list' b"['menu-bar', 
'show-destkop', 'window-list', 'workspace-switcher', 'launcher', 'launcher-0', 
'launcher-1', 'launcher-2', 'launcher-3', 'launcher-4', 'launcher-5', 
'launcher-7', 'launcher-8', 'launcher-10', 'launcher-12', 'launcher-13', 
'launcher-6', 'launcher-9', 'launcher-14', 'notification-area', 
'indicator-applet-complete', 'launcher-11']"
   b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['top-panel', 
'bottom-panel']"

  InstallationDate: Installed on 2017-01-05 (364 days ago)
  InstallationMedia: It
  SourcePackage: gnome-panel
  UpgradeStatus: Upgraded to artful on 2017-10-22 (74 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1741348/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Łukasz Zemczak]

Hello Lawrence, or anyone else affected,

Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.2 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-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

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

** Tags removed: verification-done verification-done-artful
** Tags added: verification-needed verification-needed-artful

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727390] Re: New bugfix release 17.2.4

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.2 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-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

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

** Tags removed: verification-done-artful
** Tags added: verification-needed verification-needed-artful

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

Title:
  New bugfix release 17.2.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.2:

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

  The EGL code has improved handling of the new wl_dmabuf codepath.

  SWR no longer crashes when checking environment variables.

  Other gallium drivers have also seen updates - freedreno, nouveau and
  radeonsi. The gallivm module, used by llvmpipe et al. has gained little
  endian PPC64 fixes.

  The VA and VDPAU state-trackers have seems improvements handling
  interlaced videos.

  We're using python3 compatible constructs which gives us SCons 3.0
  support."

  "Mesa 17.2.4 is now available.

  In this release we have:

  In Mesa Core we have included a change to prevent KOTOR from breaking
  when in combination with the ATI fragment shader extension. 
  Additionally, NIR has also received a correction.

  Mesa's state tracker has gotten a patch to avoid leaks in certain
  situations like when resizing a window.

  Intel drivers have received several fixes.  The compiler has gotten a
  couple, while anv also received one.  i965 got a patch to avoid VA-
  API, Beignet and other contexts in the system to break when in
  combination with previous versions of Mesa 17.2.x.

  AMD's compiler has received a couple of fixes while radv has also
  received another couple, including one to avoid a hang due to an
  overflow on huge textures.

  Broadcom's vc4 has corrected a problem when compiling with Android's
  clang.

  clover has also seen fixed a problem compiling after a specific clang
  revision.

  Vulkan's WSI has gotten plugged a memory leak for X11."

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  [Regression potential]

  These releases are tested against compliance, bugfix releases in
  particular have minimal risk of regressing anything major at least.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.2 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-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

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

** Changed in: mesa (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Triaged
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Łukasz Zemczak]

Hello Falk, or anyone else affected,

Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.2 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-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

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

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: mesa (Ubuntu Artful)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742758] [NEW] package install-info 6.4.90.dfsg.1-1build1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 255

[Ivan Goncalves Silverio]

Public bug reported:

Fail in install eclipse process

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: install-info 6.4.90.dfsg.1-1build1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Thu Jan 11 15:58:43 2018
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 255
InstallationDate: Installed on 2017-09-14 (118 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: texinfo
Title: package install-info 6.4.90.dfsg.1-1build1 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 255
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texinfo in Ubuntu.
https://bugs.launchpad.net/bugs/1742758

Title:
  package install-info 6.4.90.dfsg.1-1build1 failed to install/upgrade:
  sub-processo script post-installation instalado retornou estado de
  saída de erro 255

Status in texinfo package in Ubuntu:
  New

Bug description:
  Fail in install eclipse process

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: install-info 6.4.90.dfsg.1-1build1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Jan 11 15:58:43 2018
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 255
  InstallationDate: Installed on 2017-09-14 (118 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: texinfo
  Title: package install-info 6.4.90.dfsg.1-1build1 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 255
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1741902] Re: Drag and drop state may be freezed by rogue application

[Alberts Muktupāvels]

Well, I don't know how drag & drop works so I can not say that it is bug
in X server. I would start by reporting / re-assigning this bug to
nautilus especially if it is only app that causes this problem.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1741902

Title:
  Drag and drop state may be freezed by rogue application

Status in metacity package in Ubuntu:
  New

Bug description:
  I had some issues with nautlilus in the past time, that of cause need
  to be resolved by the nautlilus devs, but it turns out that IO freezes
  (eg. dropped sftp connections) may freeze nautlilus while drag and
  drop operations, and hence freeze metacity in some kind, as d&d seems
  to lock some control to the participating applications.

  What I do:

  Drag a file from nautilus.

  What happens:

  Nautilus blocks for some reason, eg. dropped sftp connection. The
  mouse pointer stays in dragging state after releasing the mouse
  button. No drop action is executed. Windows can still be bought to
  front by clicking them, but never gain focus and no application
  (besides nautlilus I guess, which is stalled) receives clicks or
  keystrokes. If at some point nautilus crashes in turn, the system
  usability is fully restored. If not, a restart by hard shutdown is
  needed to regain control.

  What should happen:

  If an application fails to commence it's drag and drop interaction,
  the action should be canceled on metacity's behalf. Otherwise any
  rogue application can stop user interaction down to moving the pointer
  around, requiring hard reboot.

  Security considerations:

  Low. The freezed state seems to block screen locking, and may reveal
  an unprotected desktop if the rogue application releases control at
  some point, eg. by crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: metacity 1:3.18.7-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-105.128-generic 4.4.98
  Uname: Linux 4.4.0-105-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Jan  8 14:52:41 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-23 (503 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: metacity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742756] [NEW] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

Public bug reported:

After upgrading to kernel 4.13.0-26-generic 3/4 of screen is unreadable.
It is both in xorg/xfce and terminal after pressing ctrl+alt+F1.
Everything works perfect when I reboot my laptop with older
4.10.0-42-generic kernel. It may be also a kernel graphics driver bug
rather than xorg bug. Now I'm wiritng this description on a 1/4 part of
the screen that looks ok. Besides the screen display issue the system
seems to run ok.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
CurrentDesktop: XFCE
Date: Thu Jan 11 18:29:04 2018
InstallationDate: Installed on 2017-12-18 (24 days ago)
InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug corruption i386 xenial

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

Title:
  3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic 3/4 of screen is
  unreadable. It is both in xorg/xfce and terminal after pressing
  ctrl+alt+F1. Everything works perfect when I reboot my laptop with
  older 4.10.0-42-generic kernel. It may be also a kernel graphics
  driver bug rather than xorg bug. Now I'm wiritng this description on a
  1/4 part of the screen that looks ok. Besides the screen display issue
  the system seems to run ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1648107] Re: $XAUTHORITY should move into $XDG_RUNTIME_DIR

[Markus Kuhn]

While we are at it, we could probably also set

  ICEAUTHORITY=$XDG_RUNTIME_DIR/ICEauthority

in a similar fashion, as this is the equivalent cookie facility for X11
client-client communication.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1648107

Title:
  $XAUTHORITY should move into $XDG_RUNTIME_DIR

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Historically, the X authority file was placed into $HOME/.Xauthority
  such that X11 clients on remote servers could access it in
  environments in which $HOME is located on a network file system.

  Today, this practice has become an anachronism that causes far more
  problems than it solves:

  a) Remote X11 clients are typically started today via "ssh -X", which
  emulates its own X11 server port $DISPLAY and therefore always creates
  its own X authority file entry on the remote server. Therefore, there
  is no longer any practical benefit from having the X authority file
  located in $HOME.

  b) If $HOME is on a network file system that implements "root squash",
  then commands such as "sudo xterm" or "sudo wireshark" won't work to
  start an X client with root privileges, as root is not able to read
  ~/.Xauthority via NFS. :-(

  c) If $HOME is on a network file system with Kerberos authentication,
  then users can easily get locked out by their screensavers once the
  Kerberos ticket expires. This is because some screen lockers (e.g.,
  gnome-screensaver) invoke a separate utility (e.g., /usr/lib/gnome-
  screensaver/gnome-screensaver-dialog) in order to ask the user of a
  locked screen for their password. Such a tool needs to access
  $XAUTHORITY right before it can display the password prompt, which
  will fail if the user's Kerberos ticket has expired (e.g. because a
  machine was suspended for 24 hours and therefore the ticket was not
  refreshed automatically on time). Without the ability to ask for a
  password, the screensaver then cannot call pam_krb5 to renew the
  user's Kerberos ticket, and the user remains locked out in a deadlock
  situation. :-(

  Both b) and c) are regular reasons for support requests in
  educational/corporate Linux environments with $HOME on Kerberized NFS.

  The solution is simple. Instead of $HOME/.Xauthority, just use in
  future $XDG_RUNTIME_DIR/xauthority as the location of the X authority
  file. (In case $XDG_RUNTIME_DIR/ does not exist, /tmp/xauthority-$USER
  might be a suitable fallback option.)

  According to https://standards.freedesktop.org/basedir-spec/basedir-
  spec-latest.html the $XDG_RUNTIME_DIR has all the right properties for
  holding the X authority file: it is always located in a local tmpfs
  filesystem, guaranteed to be accessible only to the current user, and
  will be wiped when the user has closed all sessions.

  On modern Linux systems, pam_systemd usually creates
  XDG_RUNTIME_DIR=/run/user/$UID, and wipes it in the end.

  (Note that according to https://standards.freedesktop.org/basedir-spec
  /basedir-spec-latest.html you should set the "sticky bit" on any files
  created in $XDG_RUNTIME_DIR whose timestamp is not updated regularly.)

  Feature request: please provide an option for LightDM to do the
  equivalent of

export XAUTHORITY=$XDG_RUNTIME_DIR/xauthority
chmod +t $XAUTHORITY

  and encourage Linux distribution maintainers to set this option by
  default, such that ~/.Xauthority is no longer used.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1740033] Re: [Realtek ALC1220, Green Line Out, Rear] Background noise or low volume on left speaker only

[Joao]

** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1740033

Title:
  [Realtek ALC1220, Green Line Out, Rear] Background noise or low volume
  on left speaker only

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  I've upgraded my computer to a new one with a Realtek ALC1220 from an
  ASUS crosshair VI hero and on my ubuntu 17.10 my 5.1 surround left
  audio is busted, I've configured the system audio to 5.1 and tested
  all speakers one by one and the only one that isn't working correctly
  is the left speaker, it emits the testing sound but is disturbed and
  very low, I've checked alsaconf and everything is alright there.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  biohazard   1481 F pulseaudio
   /dev/snd/controlC1:  biohazard   1481 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Dec 25 15:39:30 2017
  InstallationDate: Installed on 2017-12-25 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: High background noise, or volume is too low
  Title: [System Product Name, Realtek ALC1220, Green Line Out, Rear] 
Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3008
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3008:bd11/29/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1740033/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1735216] Re: Wacom UI highly insufficient

[Launchpad Bug Tracker]

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1735216

Title:
  Wacom  UI highly insufficient

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  I've been asked to post a bug (feature request?) here
  (https://askubuntu.com/questions/980892/xsetwacom-wont-find-wacom-
  tablet-under-17-10-but-did-with-17-04-multiple-cur) on the following
  grounds:

   The UI offered in Wayland for controlling a graphics tablet (such as my 
Wacom Bamboo Touch on a Thinkpad T450s under Ubuntu 17.10) is nowhere near a 
replacement for xsetwacom's functionality:
  This tablet has both touch and a stylus.  Wayland seems to know that.

   (1) a UI is never a replacement for a CLI. I  have scripts which
  controlled the tablet under X11, e.g. to turn touch on and off. Now I
  cannot use Wayland because even if the UI was fixed, my scripts won't
  work.

   (2) Wayland UI does not offer option to turn touch off

   (3) Wayland UI does not offer option to rotate the pad

   (4) Mapping the tablet (touch) to a single monitor does not work (it
  still spans both my monitors)

   (5) Mapping the tablet (touch) to absolute coordinates does not work
  (it is still relative)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 29 11:31:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1735216/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742750] [NEW] Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file

[Michael Marley]

Public bug reported:

Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-connect.patch,
which changes line 38 of /etc/pulse/default.pa to read ".endif### Load
audio drivers statically".  It appears that there are a couple of line
feeds missing here, and having the comment on the same line as the endif
causes pulseaudio not to start.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1742750

Title:
  Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid
  /etc/pulse/default.pa file

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
  connect.patch, which changes line 38 of /etc/pulse/default.pa to read
  ".endif### Load audio drivers statically".  It appears that there are
  a couple of line feeds missing here, and having the comment on the
  same line as the endif causes pulseaudio not to start.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742746] [NEW] Update flash plugin to 28.0.0.137

[Bruce Guenter]

Public bug reported:

Adobe has released security updates for Adobe Flash Player for Windows,
Macintosh, Linux and Chrome OS. These updates address an important out-
of-bounds read vulnerability that could lead to information exposure.

This affects version 28.0.0.126, which is the current package in all
Ubuntu releases.

References:
https://helpx.adobe.com/security/products/flash-player/apsb18-01.html
https://forums.adobe.com/thread/2435528

** Affects: flashplugin-nonfree (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to flashplugin-nonfree in Ubuntu.
https://bugs.launchpad.net/bugs/1742746

Title:
  Update flash plugin to 28.0.0.137

Status in flashplugin-nonfree package in Ubuntu:
  New

Bug description:
  Adobe has released security updates for Adobe Flash Player for
  Windows, Macintosh, Linux and Chrome OS. These updates address an
  important out-of-bounds read vulnerability that could lead to
  information exposure.

  This affects version 28.0.0.126, which is the current package in all
  Ubuntu releases.

  References:
  https://helpx.adobe.com/security/products/flash-player/apsb18-01.html
  https://forums.adobe.com/thread/2435528

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1742746/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp