[Desktop-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

[Dave Chiluk]

As I have multiple profiles, I chose to simply delete all Cache
directories


$ find ~/.config/google-chrome \( -name "*Cache" \) | xargs -d '\n' -L 1 rm -rf

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

Title:
  After mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])

[Dave Chiluk]

Looking at mesa git staging/23.0 it looks like 78a75e0d2 and 4c986c58b
may also be required.

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

Title:
  Asynchronous wait on fence ... timed out
  (hint:intel_atomic_commit_ready [i915])

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Jammy:
  New
Status in mesa source package in Kinetic:
  New
Status in mesa source package in Lunar:
  New

Bug description:
  GUI hard lock during zoom session and gnome-terminal

  kern.log shows a mix of errors 
  __
  kernel: [ 3627.948545] Asynchronous wait on fence 
:00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready 
[i915])
  kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 
12:1:85db, in chrome [5521]
  kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped 
heartbeat on rcs0
  kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset 
due to GPU hang
  kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware 
i915/adlp_guc_70.1.1.bin version 70.1
  kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware 
i915/tgl_huc_7.9.3.bin version 7.9
  kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated
  kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled
  kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled
  ___

  I suspect this issue to be 
  upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755
  upstream commit: 
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217

  Reproducer: Although I don't have my own reproducer, the upstream mesa
  reproducer does trigger a hang on my machine.

  Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it
  loads, you will see pikachu. Press "S", he will go back.  My whole
  system freezes from this in Wayland, regardless of the browser.

  Kernel: 6.0.0-1008-oem
  Mesa: 22.2.5-0ubuntu0.1~22.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9
  Uname: Linux 6.0.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  8 21:40:19 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0b1a]
 Subsystem: Dell Device [1028:0b1a]
  InstallationDate: Installed on 2022-07-13 (211 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  MachineType: Dell Inc. Precision 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash 
mem_sleep_default=deep vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2022
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.1
  dmi.board.name: 03M8N5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A:
  dmi.product.family: Precision
  dmi.product.name: Precision 5570
  dmi.product.sku: 0B1A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])

[Dave Chiluk]

The above referenced commits are committed into mesa 23.0.0.   I see
references to backports of this onto stable, but I'm not familiar enough
with mesa as a project just yet.

** Also affects: mesa (Ubuntu Lunar)
   Importance: Undecided
 Assignee: Dave Chiluk (chiluk)
   Status: New

** Also affects: mesa (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: mesa (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Changed in: mesa (Ubuntu Jammy)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

** Changed in: mesa (Ubuntu Lunar)
 Assignee: Dave Chiluk (chiluk) => (unassigned)

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

Title:
  Asynchronous wait on fence ... timed out
  (hint:intel_atomic_commit_ready [i915])

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Jammy:
  New
Status in mesa source package in Kinetic:
  New
Status in mesa source package in Lunar:
  New

Bug description:
  GUI hard lock during zoom session and gnome-terminal

  kern.log shows a mix of errors 
  __
  kernel: [ 3627.948545] Asynchronous wait on fence 
:00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready 
[i915])
  kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 
12:1:85db, in chrome [5521]
  kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped 
heartbeat on rcs0
  kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset 
due to GPU hang
  kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware 
i915/adlp_guc_70.1.1.bin version 70.1
  kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware 
i915/tgl_huc_7.9.3.bin version 7.9
  kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated
  kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled
  kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled
  ___

  I suspect this issue to be 
  upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755
  upstream commit: 
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217

  Reproducer: Although I don't have my own reproducer, the upstream mesa
  reproducer does trigger a hang on my machine.

  Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it
  loads, you will see pikachu. Press "S", he will go back.  My whole
  system freezes from this in Wayland, regardless of the browser.

  Kernel: 6.0.0-1008-oem
  Mesa: 22.2.5-0ubuntu0.1~22.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9
  Uname: Linux 6.0.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  8 21:40:19 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0b1a]
 Subsystem: Dell Device [1028:0b1a]
  InstallationDate: Installed on 2022-07-13 (211 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  MachineType: Dell Inc. Precision 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash 
mem_sleep_default=deep vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2022
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.1
  dmi.board.name: 03M8N5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A:
  dmi.product.family: Precision
  dmi.product.name: Precision 5570
  dmi.product.sku: 0B1A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
  version.xserver-xorg-core: xserver-xor

[Desktop-packages] [Bug 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])

[Dave Chiluk]

** Tags added: indeed

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

Title:
  Asynchronous wait on fence ... timed out
  (hint:intel_atomic_commit_ready [i915])

Status in mesa package in Ubuntu:
  New

Bug description:
  GUI hard lock during zoom session and gnome-terminal

  kern.log shows a mix of errors 
  __
  kernel: [ 3627.948545] Asynchronous wait on fence 
:00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready 
[i915])
  kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 
12:1:85db, in chrome [5521]
  kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped 
heartbeat on rcs0
  kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset 
due to GPU hang
  kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware 
i915/adlp_guc_70.1.1.bin version 70.1
  kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware 
i915/tgl_huc_7.9.3.bin version 7.9
  kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated
  kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled
  kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled
  ___

  I suspect this issue to be 
  upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755
  upstream commit: 
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217

  Reproducer: Although I don't have my own reproducer, the upstream mesa
  reproducer does trigger a hang on my machine.

  Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it
  loads, you will see pikachu. Press "S", he will go back.  My whole
  system freezes from this in Wayland, regardless of the browser.

  Kernel: 6.0.0-1008-oem
  Mesa: 22.2.5-0ubuntu0.1~22.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9
  Uname: Linux 6.0.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  8 21:40:19 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0b1a]
 Subsystem: Dell Device [1028:0b1a]
  InstallationDate: Installed on 2022-07-13 (211 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  MachineType: Dell Inc. Precision 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash 
mem_sleep_default=deep vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2022
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.1
  dmi.board.name: 03M8N5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A:
  dmi.product.family: Precision
  dmi.product.name: Precision 5570
  dmi.product.sku: 0B1A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006669/+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 2006669] [NEW] Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])

[Dave Chiluk]

Public bug reported:

GUI hard lock during zoom session and gnome-terminal

kern.log shows a mix of errors 
__
kernel: [ 3627.948545] Asynchronous wait on fence 
:00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready 
[i915])
kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, 
in chrome [5521]
kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped 
heartbeat on rcs0
kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset due 
to GPU hang
kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware 
i915/adlp_guc_70.1.1.bin version 70.1
kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware 
i915/tgl_huc_7.9.3.bin version 7.9
kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated
kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled
kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled
___

I suspect this issue to be 
upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755
upstream commit: 
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217

Reproducer: Although I don't have my own reproducer, the upstream mesa
reproducer does trigger a hang on my machine.

Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it
loads, you will see pikachu. Press "S", he will go back.  My whole
system freezes from this in Wayland, regardless of the browser.

Kernel: 6.0.0-1008-oem
Mesa: 22.2.5-0ubuntu0.1~22.04.1

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9
Uname: Linux 6.0.0-1008-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb  8 21:40:19 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 
0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0b1a]
   Subsystem: Dell Device [1028:0b1a]
InstallationDate: Installed on 2022-07-13 (211 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
MachineType: Dell Inc. Precision 5570
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash 
mem_sleep_default=deep vt.handoff=7
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2022
dmi.bios.release: 1.9
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.1
dmi.board.name: 03M8N5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A:
dmi.product.family: Precision
dmi.product.name: Precision 5570
dmi.product.sku: 0B1A
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Assignee: Dave Chiluk (chiluk)
 Status: New


** Tags: amd64 apport-bug jammy ubuntu uec-images wayland-session

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

Title:
  Asynchronous wait on fence ... timed out
  (hint:intel_atomic_commit_ready [i915])

Status in mesa package in Ubuntu:
  New

Bug description:
  GUI hard lock during zoom session and gnome-terminal

  kern.log shows a mix of errors 
  __
  kernel: [ 3627.948545] Asynchronous wait on fence 
:00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready 
[i915])
  kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 
12:1:85db, in chrome [5521]
  kernel:

[Desktop-packages] [Bug 1211700] Re: [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) that saturate the GPU cause the Mir server to slow, freeze and stutter, displaying very f

[Dave Chiluk]

Closing this ticket where I can as there's no update for 5 years.  Plus
mir has been supplanted by wayland.

** Changed in: mesa (Ubuntu)
   Status: New => Won't Fix

** Changed in: mir (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: mir
   Status: Triaged => Fix Released

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

Title:
  [gallium] EGL clients using a gallium driver (radeon, nouveau,
  freedreno) that saturate the GPU cause the Mir server to slow, freeze
  and stutter, displaying very few frames

Status in Mir:
  Fix Released
Status in mesa package in Ubuntu:
  Won't Fix
Status in mir package in Ubuntu:
  Won't Fix

Bug description:
  GPU-heavy clients on Mesa gallium drivers (e.g. radeon, nouveau and
  freedreno) cause the Mir server to slow, sometimes to a halt. This is
  seen as a frozen screen, unable to move surfaces, or unable to switch
  VTs (for a while).

  For example:
     mir_demo_client_egltriangle -n
     mir_demo_client_eglplasma -n

  The -n flag (swapinterval = 0) seems to cause the client to overload
  the mir server to the point where it cannot render physical frames
  very often.

  $ es2_info
  EGL_VERSION = 1.4 (Gallium)
  EGL_VENDOR = Mesa Project
  EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base 
EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync 
EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer
  EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG
  GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel
  GL_RENDERER: Gallium 0.4 on AMD CEDAR
  ...
  $ es2_info
  EGL_VERSION = 1.4 (Gallium)
  EGL_VENDOR = Mesa Project
  EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base 
EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync 
EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer
  EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG
  GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel
  GL_RENDERER: Gallium 0.4 on NVA8
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1211700/+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 1968588] Re: Cannot create or add VPN in connection editor

[Dave Chiluk]

Workaround available here 
https://askubuntu.com/questions/1403896/cant-add-cisco-compatible-vpn-vpnc-on-network-manager-ubuntu-22-04/1404609#1404609

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

Title:
  Cannot create or add VPN in connection editor

Status in network-manager-applet package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed

Bug description:
  In 22.04 I am unable to create a new VPN in network manager and nm-
  connection-editor. After filing in the entire form the save button
  remains disabled!

  watching the terminal provides this error:
  Cannot save connection due to error: Invalid setting General: 
connection.interface-name: '': interface name must not be empty

  Seems like the form validator is not looking at the right field!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager-gnome 1.24.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 11 10:49:34 2022
  ExecutablePath: /usr/bin/nm-connection-editor
  InstallationDate: Installed on 2022-04-09 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE  FILENAME
   
   Wired connection 1  31e61843-ef5f-31e8-96a2-cf86d47e015c  ethernet  
1649688323  Mon 11 Apr 2022 10:45:23 AM EDT  yes  -999  
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s3  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/run/NetworkManager/system-connections/Wired connection 1.nmconnection
  nmcli-dev:
   DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTION  CON-UUID 
 CON-PATH   
   enp0s3  ethernet  connected  full  limited   
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
31e61843-ef5f-31e8-96a2-cf86d47e015c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1968588/+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 1968588] Re: Cannot create or add VPN in connection editor

[Dave Chiluk]

** Tags added: indeed

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

Title:
  Cannot create or add VPN in connection editor

Status in network-manager-applet package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed

Bug description:
  In 22.04 I am unable to create a new VPN in network manager and nm-
  connection-editor. After filing in the entire form the save button
  remains disabled!

  watching the terminal provides this error:
  Cannot save connection due to error: Invalid setting General: 
connection.interface-name: '': interface name must not be empty

  Seems like the form validator is not looking at the right field!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager-gnome 1.24.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 11 10:49:34 2022
  ExecutablePath: /usr/bin/nm-connection-editor
  InstallationDate: Installed on 2022-04-09 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE  FILENAME
   
   Wired connection 1  31e61843-ef5f-31e8-96a2-cf86d47e015c  ethernet  
1649688323  Mon 11 Apr 2022 10:45:23 AM EDT  yes  -999  
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s3  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/run/NetworkManager/system-connections/Wired connection 1.nmconnection
  nmcli-dev:
   DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTION  CON-UUID 
 CON-PATH   
   enp0s3  ethernet  connected  full  limited   
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
31e61843-ef5f-31e8-96a2-cf86d47e015c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1968588/+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 1922298] [NEW] Activities panel on wrong display

[Dave Chiluk]

Public bug reported:

The activities panel is showing up on the wrong display.  Selecting the
"primary display" as 3 in the display settings puts the top bar on
display 3 , but the activities bar on screen 2.  Screenshot attached

Similarly, selecting
primary display = 2 then activities bar ends up on 1
primary display = 1 then activities bar ends up on 3

I'm hoping this is just an off by one error somewhere.

I think gnome-shell is the correct package. Feel free to move to the
correct package

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-49-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  1 17:16:30 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-06-12 (293 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2021-04-01 17-05-08.png"
   
https://bugs.launchpad.net/bugs/1922298/+attachment/5483269/+files/Screenshot%20from%202021-04-01%2017-05-08.png

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

Title:
  Activities panel on wrong display

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The activities panel is showing up on the wrong display.  Selecting
  the "primary display" as 3 in the display settings puts the top bar on
  display 3 , but the activities bar on screen 2.  Screenshot attached

  Similarly, selecting
  primary display = 2 then activities bar ends up on 1
  primary display = 1 then activities bar ends up on 3

  I'm hoping this is just an off by one error somewhere.

  I think gnome-shell is the correct package. Feel free to move to the
  correct package

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  1 17:16:30 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-12 (293 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922298/+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 1890613] [NEW] Gnome unresponsive JS ERROR: TypeError: windowActor is null

[Dave Chiluk]

Public bug reported:

gnome-shell becomes unresponsive after about 1 day. I'm able to interact
with the window that had focus when the problem appears (in this case it
was Chrome), but I'm unable to select or otherwise interact with other
windows, the shell, dock, or indicators.

The logs are spammed with 
gnome-shell[2916]: JS ERROR: TypeError: windowActor is 
null#012_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28#012vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14

This looks similar to but different enough from 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774

I was using the i915 driver when this happened if that makes any
difference

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  6 09:08:32 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-06-12 (54 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal package-from-proposed

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

Title:
  Gnome unresponsive JS ERROR: TypeError: windowActor is null

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell becomes unresponsive after about 1 day. I'm able to
  interact with the window that had focus when the problem appears (in
  this case it was Chrome), but I'm unable to select or otherwise
  interact with other windows, the shell, dock, or indicators.

  The logs are spammed with 
  gnome-shell[2916]: JS ERROR: TypeError: windowActor is 
null#012_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28#012vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14

  This looks similar to but different enough from 
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774

  I was using the i915 driver when this happened if that makes any
  difference

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  6 09:08:32 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-12 (54 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890613/+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 1839589] Re: pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test]

[Dave Chiluk]

Hey thanks for the fix, I've been on vacation, and didn't have a chance
to look at this further.

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

Title:
  pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test]

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  pulseaudio fails to build from source on Eoan

  I was attempting to put together a patchset for LP#1839580, but it
  appears as if the packages are currently failing to build from source.
  Not sure how they built the first time around.

  Here's my ppa's buildlog, for a source package with my patch commented out of 
the series file.
  
https://launchpadlibrarian.net/436626918/buildlog_ubuntu-eoan-amd64.pulseaudio_1%3A12.2-2ubuntu4+lp1839580b2_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839589/+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 1839589] Re: pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test]

[Dave Chiluk]

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

Title:
  pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test]

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  pulseaudio fails to build from source on Eoan

  I was attempting to put together a patchset for LP#1839580, but it
  appears as if the packages are currently failing to build from source.
  Not sure how they built the first time around.

  Here's my ppa's buildlog, for a source package with my patch commented out of 
the series file.
  
https://launchpadlibrarian.net/436626918/buildlog_ubuntu-eoan-amd64.pulseaudio_1%3A12.2-2ubuntu4+lp1839580b2_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839589/+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 1839589] [NEW] pulseaudio FTBFS on eoan 12.2-2ubuntu4

[Dave Chiluk]

Public bug reported:

pulseaudio fails to build from source on Eoan

I was attempting to put together a patchset for LP#1839580, but it
appears as if the packages are currently failing to build from source.
Not sure how they built the first time around.

Here's my ppa's buildlog, for a source package with my patch commented out of 
the series file.
https://launchpadlibrarian.net/436626918/buildlog_ubuntu-eoan-amd64.pulseaudio_1%3A12.2-2ubuntu4+lp1839580b2_BUILDING.txt.gz

** 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/1839589

Title:
  pulseaudio FTBFS on eoan 12.2-2ubuntu4

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  pulseaudio fails to build from source on Eoan

  I was attempting to put together a patchset for LP#1839580, but it
  appears as if the packages are currently failing to build from source.
  Not sure how they built the first time around.

  Here's my ppa's buildlog, for a source package with my patch commented out of 
the series file.
  
https://launchpadlibrarian.net/436626918/buildlog_ubuntu-eoan-amd64.pulseaudio_1%3A12.2-2ubuntu4+lp1839580b2_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839589/+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 1839580] Re: LucidSound LS31 only outputs mono sound

[Dave Chiluk]

Upstream merge request.
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/143

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

Title:
  LucidSound LS31 only outputs mono sound

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  LucidSound LS31 only outputs mono sound.

  The usb vendor:prod = 2f12:0109.

  The fix is incoming.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839580/+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 1839580] [NEW] LucidSound LS31 only outputs mono sound

[Dave Chiluk]

Public bug reported:

LucidSound LS31 only outputs mono sound.

The usb vendor:prod = 2f12:0109.

The fix is incoming.

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Assignee: Dave Chiluk (chiluk)
 Status: In Progress

** 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/1839580

Title:
  LucidSound LS31 only outputs mono sound

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  LucidSound LS31 only outputs mono sound.

  The usb vendor:prod = 2f12:0109.

  The fix is incoming.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839580/+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 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[Dave Chiluk]

Enabling this plugin is the easiest way to work around this issue in bionic.
https://extensions.gnome.org/extension/1328/disable-workspace-switch-animation/

That being said what is the status of a real fix?

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  In Progress
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell source package in Eoan:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  [ Impact ]

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  [ Test case ]

  Open Android Emulator and switch workspace
  or
  Open Skype, start a test call and switch workspace

  GNOME-Shell should not crash

  [ Regression potential ]

  Very low, we remove windows from Javascript array when they're destroyed.
  A possible regression could be not switching to workspace when selecting a 
window that is in another one.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1812527/+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 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[Dave Chiluk]

** Tags added: indeed

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

Status in gjs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gjs source package in Bionic:
  Confirmed
Status in gnome-shell source package in Bionic:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

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

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

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Committed
Status in pulseaudio source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * User is only able to get mono audio from steelseries headsets
  because they provide both a stereo and mono output.  PA selects the
  mono output by default.

   * This should be backported to stable releases because this fix is 
 isolated to code that only applies to the affected headsets.  
 Additionally other gaming headsets may be more easily enabled by adding 
  ATTRS{idVendor}=="", ATTRS{idProduct}=="", 
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
 to /lib/udev/rules.d/90-pulseaudio.rules now.  Such as the Lucidsound 
 LS31 which I own.

   * The upload fixes the bug by conditionally setting a pulseaudio
  profile for the headset based on specific usb vendor and product ids
  in the udev rules.

  [Test Case]

   1. Acquire headset.
   2. Open sound settings, and click test speakers.
   3. Only option available will be mono sound

  [Regression Potential]

   * Risk of regressions should be mitigated to those who own the
  headset.  In which case it is likely that their headset is already not
  working.

  [Other Info]
   
   * All patches originate from upstream pulseaudio, and are documented as
 such including the shas.
   
   * I will be pursuing enabling other similar headsets in the coming weeks.
   * I plan to work with upstream pulseaudio to enable my own headset and to
 also make the headset templates backported here more generic.

  
   Original Description -

  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

I have tested bionic and cosmic myself, but I'd like to hear from a user
or two.  I have experienced the low-volume issue, but that appears to be
correctable by launching alsamixer.  All in all it's a better experience
than before imho.

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Committed
Status in pulseaudio source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * User is only able to get mono audio from steelseries headsets
  because they provide both a stereo and mono output.  PA selects the
  mono output by default.

   * This should be backported to stable releases because this fix is 
 isolated to code that only applies to the affected headsets.  
 Additionally other gaming headsets may be more easily enabled by adding 
  ATTRS{idVendor}=="", ATTRS{idProduct}=="", 
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
 to /lib/udev/rules.d/90-pulseaudio.rules now.  Such as the Lucidsound 
 LS31 which I own.

   * The upload fixes the bug by conditionally setting a pulseaudio
  profile for the headset based on specific usb vendor and product ids
  in the udev rules.

  [Test Case]

   1. Acquire headset.
   2. Open sound settings, and click test speakers.
   3. Only option available will be mono sound

  [Regression Potential]

   * Risk of regressions should be mitigated to those who own the
  headset.  In which case it is likely that their headset is already not
  working.

  [Other Info]
   
   * All patches originate from upstream pulseaudio, and are documented as
 such including the shas.
   
   * I will be pursuing enabling other similar headsets in the coming weeks.
   * I plan to work with upstream pulseaudio to enable my own headset and to
 also make the headset templates backported here more generic.

  
   Original Description -

  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

I uploaded these changes for bionic and cosmic.  Just waiting on sru
approval 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/1758736

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Cosmic:
  In Progress
Status in pulseaudio source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * User is only able to get mono audio from steelseries headsets
  because they provide both a stereo and mono output.  PA selects the
  mono output by default.

   * This should be backported to stable releases because this fix is 
 isolated to code that only applies to the affected headsets.  
 Additionally other gaming headsets may be more easily enabled by adding 
  ATTRS{idVendor}=="", ATTRS{idProduct}=="", 
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
 to /lib/udev/rules.d/90-pulseaudio.rules now.  Such as the Lucidsound 
 LS31 which I own.

   * The upload fixes the bug by conditionally setting a pulseaudio
  profile for the headset based on specific usb vendor and product ids
  in the udev rules.

  [Test Case]

   1. Acquire headset.
   2. Open sound settings, and click test speakers.
   3. Only option available will be mono sound

  [Regression Potential]

   * Risk of regressions should be mitigated to those who own the
  headset.  In which case it is likely that their headset is already not
  working.

  [Other Info]
   
   * All patches originate from upstream pulseaudio, and are documented as
 such including the shas.
   
   * I will be pursuing enabling other similar headsets in the coming weeks.
   * I plan to work with upstream pulseaudio to enable my own headset and to
 also make the headset templates backported here more generic.

  
   Original Description -

  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

I uploaded the changes to disco this morning.

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Cosmic:
  In Progress
Status in pulseaudio source package in Disco:
  In Progress

Bug description:
  [Impact]

   * User is only able to get mono audio from steelseries headsets
  because they provide both a stereo and mono output.  PA selects the
  mono output by default.

   * This should be backported to stable releases because this fix is 
 isolated to code that only applies to the affected headsets.  
 Additionally other gaming headsets may be more easily enabled by adding 
  ATTRS{idVendor}=="", ATTRS{idProduct}=="", 
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
 to /lib/udev/rules.d/90-pulseaudio.rules now.  Such as the Lucidsound 
 LS31 which I own.

   * The upload fixes the bug by conditionally setting a pulseaudio
  profile for the headset based on specific usb vendor and product ids
  in the udev rules.

  [Test Case]

   1. Acquire headset.
   2. Open sound settings, and click test speakers.
   3. Only option available will be mono sound

  [Regression Potential]

   * Risk of regressions should be mitigated to those who own the
  headset.  In which case it is likely that their headset is already not
  working.

  [Other Info]
   
   * All patches originate from upstream pulseaudio, and are documented as
 such including the shas.
   
   * I will be pursuing enabling other similar headsets in the coming weeks.
   * I plan to work with upstream pulseaudio to enable my own headset and to
 also make the headset templates backported here more generic.

  
   Original Description -

  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

** Description changed:

+ [Impact]
+ 
+  * User is only able to get mono audio from steelseries headsets because
+ they provide both a stereo and mono output.  PA selects the mono output
+ by default.
+ 
+  * This should be backported to stable releases because this fix is 
+isolated to code that only applies to the affected headsets.  
+Additionally other gaming headsets may be more easily enabled by adding 
+ ATTRS{idVendor}=="", ATTRS{idProduct}=="", 
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
+to /lib/udev/rules.d/90-pulseaudio.rules now.  Such as the Lucidsound 
+LS31 which I own.
+ 
+  * The upload fixes the bug by conditionally setting a pulseaudio
+ profile for the headset based on specific usb vendor and product ids in
+ the udev rules.
+ 
+ [Test Case]
+ 
+  1. Acquire headset.
+  2. Open sound settings, and click test speakers.
+  3. Only option available will be mono sound
+ 
+ [Regression Potential]
+ 
+  * Risk of regressions should be mitigated to those who own the headset.
+ In which case it is likely that their headset is already not working.
+ 
+ [Other Info]
+  
+  * All patches originate from upstream pulseaudio, and are documented as
+such including the shas.
+  
+  * I will be pursuing enabling other similar headsets in the coming weeks.
+  * I plan to work with upstream pulseaudio to enable my own headset and to
+also make the headset templates backported here more generic.
+ 
+ 
+  Original Description -
+ 
  There is not stereo playback only mono playback
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
-  /dev/snd/controlC1:  kaj1755 F pulseaudio
-  /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
-  /dev/snd/controlC0:  kaj1755 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
+  /dev/snd/controlC1:  kaj1755 F pulseaudio
+  /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
+  /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Cosmic:
  In Progress
Status in pulseaudio source package in Disco:
  In Progress

Bug description:
  [Impact]

   * User is only able to get mono audio from steelseries headsets
  because they provide both a stereo and mono output.  PA selects the
  mono output by default.

   * This should be backported to stable releases because this fix is 
 isolated to code that only applies to the affected headsets.  
 Additionally other gaming headsets may be more easily enabled by adding 
  ATTRS{idVendor}=="", ATTRS{idProduct}=="", 
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
 to /lib/udev/rules.d/90-pulseaudio.rules now.  Such as the Lucidsound 
 LS31 which I own.

   * The upload fixes the bug by conditionally setting a pulseaudio
  profile for the headset based on specific usb vendor and product ids
  in the udev rules.

  [Test Case]

   1. Acquire headset.
   2. Open sound settings, and click test 

[Desktop-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

I uploaded test packages for cosmic and disco to my ppa today.  If
someone with the headset could test either of those as well that would
be awesome.  I should be getting a headset here soon to test with.

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Cosmic:
  In Progress
Status in pulseaudio source package in Disco:
  In Progress

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

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

** Changed in: pulseaudio (Ubuntu Disco)
   Status: Confirmed => 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/1758736

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Cosmic:
  In Progress
Status in pulseaudio source package in Disco:
  In Progress

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

I'm pretty sure you need to adjust the "chat mix" knob on your headset
as the audio will now be playing through a separate audio device on the
headset.  Basically previously it was using the mono "chat"/mono output
on the headphones.  Now with the ppa it's primarily using the
"game"/stereo output.  AFAIU the knob adjusts the mix between the two
outputs on the headphones themselves.

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Cosmic:
  Confirmed
Status in pulseaudio source package in Disco:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

@Kaj Printz Madsen

I know you opened this a long time ago, but is there any chance you
could test the ppa for me?

Thanks.

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Cosmic:
  Confirmed
Status in pulseaudio source package in Disco:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

Looking at pulseaudio upstream, it looks like 12.2 has 
15386a710c1500f70085a6312fb4d84be4d254c9 and
c7fe78c9f73ded2c3428666722ec9c1af4b82812
  but not
83675b3745c64bd738400eae44eb4daa195ed88a
fe6a9a8f59932f29cc77eac2a7e2c6bd07c8c7d0
3454c19f3c277d5d0099f17e7ebf5d2005afa4b0

Bionic will needs all of the above sha's.

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Cosmic:
  Confirmed
Status in pulseaudio source package in Disco:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

Basically what I did was backport all the required Arctis stuff that
seemed to be required in order to get my lucid sound headphones working.

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Bionic:
  New
Status in pulseaudio source package in Cosmic:
  New
Status in pulseaudio source package in Disco:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

Can someone on this bug please test the packages from
https://launchpad.net/~chiluk/+archive/ubuntu/lp1758736
on Bionic?

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Bionic:
  New
Status in pulseaudio source package in Cosmic:
  New
Status in pulseaudio source package in Disco:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

[Dave Chiluk]

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

** Also affects: pulseaudio (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: pulseaudio (Ubuntu Disco)
   Importance: Low
 Assignee: Dave Chiluk (chiluk)
   Status: Confirmed

** Also affects: pulseaudio (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

** Changed in: pulseaudio (Ubuntu Cosmic)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

** Changed in: pulseaudio (Ubuntu Bionic)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Bionic:
  New
Status in pulseaudio source package in Cosmic:
  New
Status in pulseaudio source package in Disco:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1680438] Re: gnome-calculator comes up with totally wrong answer

[Dave Chiluk]

gnome has moved to gitlab.  Corresponding bug is now

https://gitlab.gnome.org/GNOME/gnome-calculator/issues/59

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

Title:
  gnome-calculator comes up with totally wrong answer

Status in GNOME Calculator:
  Expired
Status in gnome-calculator package in Ubuntu:
  Triaged

Bug description:
  Confirmed on:
   - Ubuntu 16.04.1: gnome-calculator version 1:3.18.3-0ubuntu1
   - Ubuntu 16.04.2: gnome-calculator version 1:3.18.3-0ubuntu1.16.04.1

  To reproduce the bug (have tried on multiple computers) do something
  along these lines in the gnome-calculator app:

   - Press 7 and Enter.  Screen should show 7 = 7, input field should show 7.
   - Press left arrow and type 12, then the right arrow and type +7.  Input 
field should show 127+7.
   - Press Enter.  Screen will show 127+7 = 91, input field will show 91.

  No scientific modes or anything; this is in normal mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calculator/+bug/1680438/+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 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

[Dave Chiluk]

** Tags added: indeed

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

Title:
  gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Hi all, 
  Originally I was reporting bug 1717170, about session crash after monitor 
disconnect/switch-off/input change on desktop PC and the bug was fixed 
according to bug tracker. But now, after gnome-shell and mutter update, the 
crash goes worse. Now it is not just session kick-out but complete crash. Same 
events can be used to reproduce the crash. This time also crash files was 
created.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 13:52:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-09-11 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f475acbac30 :   
movss  0x38(%rdi),%xmm0
   PC (0x7f475acbac30) ok
   source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_logical_monitor_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_wayland_get_geometry_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_sync_state () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1724557/+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 1719047] [NEW] Unable to resize window after snapped to half screen.

[Dave Chiluk]

Public bug reported:

Unable to resize window after snapped to half screen.  You can see the
arrow, tempting you to just try and resize the window at the edge, but
it's just toying with you.

More info https://bugzilla.gnome.org/show_bug.cgi?id=645153

This used to work in z+Unity ;(.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 22 19:15:17 2017
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'favorite-apps' b"['google-chrome-beta.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 
'gnome-control-center.desktop', 'keepassx.desktop', 
'chrome-knipolnnllmklapflnccelgolnpehhpl-Default.desktop', 
'terminator.desktop', 'org.gnome.Calculator.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.2'
 b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2016-04-25 (515 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-09-09 (13 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful regression-release wayland-session

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

Title:
  Unable to resize window after snapped to half screen.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Unable to resize window after snapped to half screen.  You can see the
  arrow, tempting you to just try and resize the window at the edge, but
  it's just toying with you.

  More info https://bugzilla.gnome.org/show_bug.cgi?id=645153

  This used to work in z+Unity ;(.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 19:15:17 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome-beta.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 
'gnome-control-center.desktop', 'keepassx.desktop', 
'chrome-knipolnnllmklapflnccelgolnpehhpl-Default.desktop', 
'terminator.desktop', 'org.gnome.Calculator.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.2'
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-04-25 (515 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-09 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1719047/+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 1690512] Re: shutdown/restart/suspend freezes laptop on intel graphics

[Dave Chiluk]

Please try the latest hwe stack by.  I'm using kabylake + the hwe stack
without issue at the moment.

sudo apt install --install-recommends linux-generic-hwe-16.04 xserver-
xorg-hwe-16.04

More info is available here.
https://wiki.ubuntu.com/Kernel/LTSEnablementStack

I'm also closing the intel-microcode track of this bug as at the moment
this does not appear to be hwe related.

Thank you,

** Changed in: intel-microcode (Ubuntu)
   Status: New => Invalid

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

Title:
  shutdown/restart/suspend freezes laptop on intel graphics

Status in intel-microcode package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  New

Bug description:
  I'm not sure where to report this under, so please bear with me.
  Reporting this bug using ubuntu-bug just crashes my system if im using
  intel graphics, I had to switch to nvidia graphics just to file this
  bug report so the automatically attached log files may not be a good
  representation of the problem.

  I've attached the syslog and kern.log files below.

  PROBLEM:

  When using intel graphics:

  Whenever I close the laptop lid or restart / shutdown using GUI or
  terminal commands, it goes into a black screen with a single "_" at
  the top left corner, and hangs. Only long-pressing (hard reset) the
  power button would shut down the computer.

  However, when I use sudo prime-select nvidia to switch over to nvidia,
  everything works fine.log

  I have tried many things, and all do not work. I have attached the
  logs for /var/log/syslog and /var/log/kern.log below.

  Attempts so far:

  1)Tried installing new intel drivers from Updated kernel to 4.8 now
  missing firmware warnings --> Did not work. Issue persists

  2) Tried upgrading kernel from 4.8 to 4.10.15 --> Did not work.
  Problem got worse. Instead of the normal login screen, it gives a
  terminal login screen and hangs.

  3) Tried the fix to nvidia-prime
  https://askubuntu.com/a/884506/547039, but both the poweron.sh and
  poweroff.sh script hangs my laptop instead.

  4) Tried sudo swapoff -a && systemctl poweroff as a workaround, no
  avail.

  5) Tried changing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force" Does not work
  either.

  Additional note:
  'sudo lshw -C display' on intel graphics outputs PCI(sysfs) then laptop 
freezes.

  LOG FILES:
  /var/log/syslog
  https://codeshare.io/5XOPwM

  /var/log/kern.log
  https://codeshare.io/aJp6nq

  specs:

  Intel 7700HQ, NVIDIA 1060GTX, kernel 4.8, Ubuntu 16.04

  Would really appreciate your help. Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset 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  381.22  Thu May  4 00:55:03 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 13 17:06:20 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-77-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-49-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-51-generic, x86_64: installed
   nvidia-381, 381.22, 4.8.0-51-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:65a1]
   NVIDIA Corporation Device [10de:1c20] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:65a1]
  InstallationDate: Installed on 2017-03-30 (43 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 0483:374b STMicroelectronics ST-LINK/V2.1 
(Nucleo-F103RB)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Aftershock P65xHP
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-51-generic 

[Desktop-packages] [Bug 1621776] Re: no hevc harware decode hevc whith 1060 - vdpau - 367.44 or 370.28

[Dave Chiluk]

This looks like an issue in the nvidia driver with decoding
HEVC_MAIN_10.

See
https://devtalk.nvidia.com/default/topic/918822/hevc-main-10-profile-decoding-using-vdpau-unsupported-on-gtx-950-361-28-/

https://devtalk.nvidia.com/default/topic/940228/linux/vdpau-expose-hevc-
main10-support-where-available-on-die/2

I haven't done much more looking into it than that.

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

Title:
  no hevc harware decode hevc whith 1060 - vdpau - 367.44 or 370.28

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

Bug description:
  Hi,

  I installed nvidia-367 last week. All was fine.
  Yesterday I have some update, may be because of release 370 and now, 
mpv/vdpau doesn't want to use the hardware decoding for hevc. 
  I tried with ffmpeg (-hwaccel vdpau) : the same. Whith "nvidia-smi dmon -i 
0", no doubt about that.

  I tried with the new nvidia-370 but no result for HW decoding HEVC for videos 
in main profile.
  Now, the problem is the same with 367.44 or 370.28.
  It was fine from the first install of 367 (and my new card) until 1/2 days 
ago.

  The hardware encoding with ffmpeg and hevc_nvenc works fine. I can
  encode with hw but not decode !!

  > Stream #0:0(eng): Video: hevc (Main 10), yuv420p(tv), 1920x1080 [SAR 1:1 
DAR 16:9], 23.98 fps, 23.98 tbr, 1k tbn, 23.98 tbc (default)
  MPV out:
  vd] Codec list:
  [vd] lavc:hevc - HEVC (High Efficiency Video Coding)
  [vd] Opening video decoder lavc:hevc
  [vd] Probing 'vdpau'...
  [vd] Trying hardware decoding.
  [vd] Selected video codec: HEVC (High Efficiency Video Coding) [lavc:hevc]
  [vd] Pixel formats supported by decoder: vaapi_vld vdpau yuv420p
  [vd] Codec profile: Main 10 (0x2)
  [vd] Pixel formats supported by decoder: vaapi_vld yuv420p
  [vd] Codec profile: Main 10 (0x2)
  [vd] Falling back to software decoding.
  [vd] Detected 4 logical cores.
  [vd] Requesting 5 threads for decoding.
  AO: [pulse] 48000Hz 5.1(side) 6ch float
  Using software decoding.

  
  Ubuntu 16.04 / 370.28 /  GeForce GTX 1060 3GB

  $ dpkg -l |egrep "vdpau|nvidia|cuda|mpv|linux-generic" |grep ii
  ii libcuda1-370 370.28-0ubuntu0~gpu16.04.1 amd64 NVIDIA CUDA runtime library
  ii libvdpau-dev:amd64 1.1.1-3ubuntu1 amd64 Video Decode and Presentation API 
for Unix (development files)
  ii libvdpau1:amd64 1.1.1-3ubuntu1 amd64 Video Decode and Presentation API for 
Unix (libraries)
  ii linux-generic 4.4.0.38.40 amd64 Complete Generic Linux kernel and headers
  ii mpv 2:0.19.0+git~xenial amd64 mplayer/mplayer2 based video player
  ii nvidia-370 370.28-0ubuntu0~gpu16.04.1 amd64 NVIDIA binary driver - version 
370.28
  ii nvidia-opencl-icd-370 370.28-0ubuntu0~gpu16.04.1 amd64 NVIDIA OpenCL ICD
  ii nvidia-prime 0.8.2 amd64 Tools to enable NVIDIA's Prime
  ii nvidia-settings 370.28-0ubuntu0~gpu16.04.1 amd64 Tool for configuring the 
NVIDIA graphics driver
  ii vdpauinfo 1.0-1 amd64 Video Decode and Presentation API for Unix 
(vdpauinfo utility)

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1621776/+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 1660388] Re: Window decorator corruption

[Dave Chiluk]

Uploading jpg a second time so it's obvious, and not missed in the maas
of auto-uploaded logs.

** Attachment added: "Awesome example of decorator corruption."
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1660388/+attachment/4810973/+files/corruption.jpg

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

Title:
  Window decorator corruption

Status in mesa package in Ubuntu:
  New
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  After switching back from another user or after lock screen I
  occasionally get corruption.  This usually takes a few weeks after a
  restart to reproduce.  Might be related to nvidia drivers or mesa, or
  compiz, or something else.  Experienced this before recent update to
  mesa 12.0.6, so I don't think this is a mesa regression.

  Decorations shown in jpg move with window, but are not selectable.

  Opening against unity, as the unity taskbar often shares similar
  corruption.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jan 30 10:54:45 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c03] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6163]
  InstallationDate: Installed on 2016-01-15 (380 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=029afe58-00c3-4872-9556-b3fd990c5cf1 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
scsi_mod.use_blk_mq=y dm_mod.use_blk_mq=y crashkernel=384M-:128M
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SIX7910J.86A.0594.2013.0806.2241
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DX79SI
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG28808-500
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSIX7910J.86A.0594.2013.0806.2241:bd08/06/2013:svn:pn:pvr:rvnIntelCorporation:rnDX79SI:rvrAAG28808-500:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Jan  9 00:41:06 2017
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1660388/+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 1660388] [NEW] Window decorator corruption

[Dave Chiluk]

Public bug reported:

After switching back from another user or after lock screen I
occasionally get corruption.  This usually takes a few weeks after a
restart to reproduce.  Might be related to nvidia drivers or mesa, or
compiz, or something else.  Experienced this before recent update to
mesa 12.0.6, so I don't think this is a mesa regression.

Decorations shown in jpg move with window, but are not selectable.

Opening against unity, as the unity taskbar often shares similar
corruption.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity 7.4.0+16.04.20160906-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Jan 30 10:54:45 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation Device [10de:1c03] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: eVga.com. Corp. Device [3842:6163]
InstallationDate: Installed on 2016-01-15 (380 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=029afe58-00c3-4872-9556-b3fd990c5cf1 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
scsi_mod.use_blk_mq=y dm_mod.use_blk_mq=y crashkernel=384M-:128M
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2013
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SIX7910J.86A.0594.2013.0806.2241
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DX79SI
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG28808-500
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrSIX7910J.86A.0594.2013.0806.2241:bd08/06/2013:svn:pn:pvr:rvnIntelCorporation:rnDX79SI:rvrAAG28808-500:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Jan  9 00:41:06 2017
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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

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

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


** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install 
third-party-packages ubuntu xenial

** Attachment added: "jpg of example decorator corruption"
   
https://bugs.launchpad.net/bugs/1660388/+attachment/4810946/+files/corruption.jpg

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

** Also affects: nvidia-graphics-drivers-367 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Window decorator corruption

Status in mesa package in Ubuntu:
  New
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  After switching back from another user or after lock screen I
  occasionally get corruption.  This usually takes a few weeks after a
  restart to reproduce.  Might be related to nvidia drivers or mesa, or
  compiz, or something else.  Experienced this before recent update to
  mesa 12.0.6, so I don't think this is a mesa regression.

  Decorations shown in jpg move with window, but are not selectable.

[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

[Dave Chiluk]

I spoke too soon still exists in Yakkety.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1589401] Re: cannot view wifi networks after re-enabling wifi

[Dave Chiluk]

With my recent update to Yakkety I no longer seem to be experiencing
this issue.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1631564] Re: Unity panel corruption on return from other user account

[Dave Chiluk]

Here's an example of corruption affecting windows outside of the unity
panel.

** Attachment added: "Screenshot from 2016-10-08 00-50-46.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1631564/+attachment/4757121/+files/Screenshot%20from%202016-10-08%2000-50-46.png

** Also affects: nvidia-graphics-drivers (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unity panel corruption on return from other user account

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

Bug description:
  My wife occasionally shares my computer.  After changing users, I've
  noticed that frequently the Unity panel becomes corrupted.  I'm not
  sure if this is nvidia drivers related or unity related, but I'll open
  against unity.

  I'm attaching a screen-cap of what I see when logging in after another
  user has been logged in.  Sometimes it also affects content of windows
  as well.

  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1625498 looks to
  be a similar but possibly different issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  Uname: Linux 4.8.0-040800rc8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.44  Wed Aug 17 22:24:07 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Sat Oct  8 00:18:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c02] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Device [196e:11d8]
  InstallationDate: Installed on 2016-01-15 (266 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-040800rc8-generic 
root=UUID=029afe58-00c3-4872-9556-b3fd990c5cf1 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
scsi_mod.use_blk_mq=y dm_mod.use_blk_mq=y crashkernel=384M-:128M
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SIX7910J.86A.0594.2013.0806.2241
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DX79SI
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG28808-500
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSIX7910J.86A.0594.2013.0806.2241:bd08/06/2013:svn:pn:pvr:rvnIntelCorporation:rnDX79SI:rvrAAG28808-500:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Oct  6 01:25:28 2016
  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.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1631564/+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 1576747] Re: Network manager applet unable to control wifi after suspend in 16.04

[Dave Chiluk]

** Summary changed:

- Network manager unable to control wifi after suspend in 16.04
+ Network manager applet unable to control wifi after suspend in 16.04

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

Title:
  Network manager applet unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> 

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

[Dave Chiluk]

Not a duplicate of 1585863, as 
$ sudo wpa_cli scan
does not recover nm-applet functionality.  There seem to be a number of similar 
but different issues related to wifi. 

** This bug is no longer a duplicate of bug 1585863
   WiFi malfunction after suspend & resume stress

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  

[Desktop-packages] [Bug 1592424] Re: Merge iputils from upstream

[Dave Chiluk]

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

This is a dupe of 1592425.  I'll blame the poor internet at the Athens
Sprint.

** Changed in: iputils (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

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

** This bug has been marked a duplicate of bug 1592425
   Merge iputils from upstream

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

Title:
  Merge iputils from upstream

Status in iputils package in Ubuntu:
  Fix Released

Bug description:
  Merge 3:20150815-2 from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1592424/+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 1592425] Re: Merge iputils from upstream

[Dave Chiluk]

** Changed in: iputils (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

Title:
  Merge iputils from upstream

Status in iputils package in Ubuntu:
  Fix Released

Bug description:
  Merge 3:20150815-2 from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1592425/+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 1592425] Re: Merge iputils from upstream

[Dave Chiluk]

Attached the above with suggested changes per slangasek's review.

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

Title:
  Merge iputils from upstream

Status in iputils package in Ubuntu:
  New

Bug description:
  Merge 3:20150815-2 from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1592425/+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 1592425] Re: Merge iputils from upstream

[Dave Chiluk]

* Merge from Debian unstable.  Remaining changes:
- Support cross-building
- Mark ping and ping6 setuid again as there's currently no good ways
  to have capabilities be kept in all our images. (LP: #1302192)


** Patch added: "iputils.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1592425/+attachment/4684082/+files/iputils.debdiff

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

Title:
  Merge iputils from upstream

Status in iputils package in Ubuntu:
  New

Bug description:
  Merge 3:20150815-2 from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1592425/+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 1592425] Re: Merge iputils from upstream

[Dave Chiluk]

** Patch removed: "iputils.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1592425/+attachment/4683577/+files/iputils.debdiff

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

Title:
  Merge iputils from upstream

Status in iputils package in Ubuntu:
  New

Bug description:
  Merge 3:20150815-2 from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1592425/+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 1592425] Re: Merge iputils from upstream

[Dave Chiluk]

Merge from Debian unstable.  Remaining changes:
- Support cross-building
- Removed "Mark ping and ping6 setuid again as there's currently 
  no good ways to have capabilities be kept in all our images.
  (LP: #1302192)" as this is no longer necessary.

Had to change Build-Depends: sgmlspl to sgmlspl:any, for crossbuilding.

** Patch added: "iputils.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1592425/+attachment/4683577/+files/iputils.debdiff

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

Title:
  Merge iputils from upstream

Status in iputils package in Ubuntu:
  New

Bug description:
  Merge 3:20150815-2 from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1592425/+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 1592425] [NEW] Merge iputils from upstream

[Dave Chiluk]

Public bug reported:

Merge 3:20150815-2 from upstream.

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

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

Title:
  Merge iputils from upstream

Status in iputils package in Ubuntu:
  New

Bug description:
  Merge 3:20150815-2 from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1592425/+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 1592424] [NEW] Merge iputils from upstream

[Dave Chiluk]

Public bug reported:

Merge 3:20150815-2 from upstream.

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

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

Title:
  Merge iputils from upstream

Status in iputils package in Ubuntu:
  New

Bug description:
  Merge 3:20150815-2 from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1592424/+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 1576747] Re: Network manager unable to control wifi after suspend in 16.04

[Dave Chiluk]

@monte

Alright thanks for the test. Can you please add --log-level=debug to 
/lib/systemd/system/NetworkManager.service at the end of the ExecStart= line.  
So it looks like this
ExecStart=/usr/sbin/NetworkManager --no-daemon --log-level=debug
Then
- restart your machine.
- suspend the machine.
- resume the machine.  Verifying that you hit the issue.
- Then upload your syslog as I did above.

Thank you,
Dave

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

[Dave Chiluk]

There is a firmware component for IMEI.  If I'm not mistaken the IMEI
firmware is what is responsible for vpro / AMT functionality.  According
to this FAQ https://software.intel.com/en-us/articles/intel-vpro-
technology-faq, it is capable of controlling a wireless card even while
in sleep states.  This could be putting the card in an unexpected state
while in suspend/sleep.

The update I installed was not simply a windows driver update, but
actually a firmware flash presumably for the formentioned vpro/amt
functionality.

That being said if your machines are not vpro/amt capable then that's
clearly not your issue, but until I hit that issue again it does seem to
be what resolved my issue.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] 

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

[Dave Chiluk]

So I don't seem to be able to reproduce this any more.  I did recently
boot windows on my laptop, and then ran updates.  I no longer seem to be
able to reproduce this issue.

One of the important updates was an update to the IMEI firmware on my
machine.  Can someone else on this bug please upgrade your IMEI firmware
*(which likely needs to be performed via windows), and then attempt to
reproduce this bug.  I'd like confirmation that the IMEI firmware update
did indeed resolve this issue.

Thanks

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   

[Desktop-packages] [Bug 1588944] Re: Incorrect 0% remaining battery detected forcing suspend

[Dave Chiluk]

In case anyone else hits this on their laptop and would like to disable
the auto-suspend, I installed dconf-editor, and changed critical-
battery-action to nothing.

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

Title:
  Incorrect 0% remaining battery detected forcing suspend

Status in indicator-power package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Invalid

Bug description:
  Ubuntu is detecting that my battery has depleted to low or 0% which
  results in the OS forcing suspend.  Normally this would be correct
  behavior, but in my case the battery has closer to 90% of remaining
  battery left.

  I have experienced this with 4.4.0-22 and 4.4.0-23, and am currently
  running 4.4.0-21 to see if it reproduces there as well.

  I do have -proposed enabled so it's a bit hard to determine if this is
  the kernel or something higher up the stack.

  This does seem to be mildly reproducible. 4.4.0-23 being the most
  problematic kernel so far.

  Of course this is a relatively new laptop so this could be a hardware
  issue as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chiluk 2462 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun  3 14:07:17 2016
  HibernationDevice: RESUME=UUID=4f4ea88e-642e-4be5-bdf0-bbc7f47f5628
  InstallationDate: Installed on 2016-04-25 (38 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 003: ID 04f2:b531 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FBCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=249f91bb-7789-41cc-9cc0-8ba25d7f55bb ro quiet splash pcie_aspm=force 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1588944/+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 1588944] Re: Incorrect 0% remaining battery detected forcing suspend

[Dave Chiluk]

Just to circle back around.  Due to the above upower output I really
started to suspect hardware.  I ended up checking the release iso, and
subsequently a certain Microsoft OS.  Both also saw the same issues.
Lenovo is over-nighting me a new battery.  Apparently the electronics in
the battery died fantastically.  Shame on me for suspecting our beloved
OS.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: upower (Ubuntu)
   Status: New => Invalid

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

** Changed in: upower (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

** Changed in: indicator-power (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

Title:
  Incorrect 0% remaining battery detected forcing suspend

Status in indicator-power package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Invalid

Bug description:
  Ubuntu is detecting that my battery has depleted to low or 0% which
  results in the OS forcing suspend.  Normally this would be correct
  behavior, but in my case the battery has closer to 90% of remaining
  battery left.

  I have experienced this with 4.4.0-22 and 4.4.0-23, and am currently
  running 4.4.0-21 to see if it reproduces there as well.

  I do have -proposed enabled so it's a bit hard to determine if this is
  the kernel or something higher up the stack.

  This does seem to be mildly reproducible. 4.4.0-23 being the most
  problematic kernel so far.

  Of course this is a relatively new laptop so this could be a hardware
  issue as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chiluk 2462 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun  3 14:07:17 2016
  HibernationDevice: RESUME=UUID=4f4ea88e-642e-4be5-bdf0-bbc7f47f5628
  InstallationDate: Installed on 2016-04-25 (38 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 003: ID 04f2:b531 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FBCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=249f91bb-7789-41cc-9cc0-8ba25d7f55bb ro quiet splash pcie_aspm=force 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1588944/+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 1588944] Re: Incorrect 0% remaining battery detected forcing suspend

[Dave Chiluk]

Here's a log of me pulling power, and plugging it back in.

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

** Attachment added: "upower.out"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588944/+attachment/4679103/+files/upower.out

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

Title:
  Incorrect 0% remaining battery detected forcing suspend

Status in indicator-power package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in upower package in Ubuntu:
  New

Bug description:
  Ubuntu is detecting that my battery has depleted to low or 0% which
  results in the OS forcing suspend.  Normally this would be correct
  behavior, but in my case the battery has closer to 90% of remaining
  battery left.

  I have experienced this with 4.4.0-22 and 4.4.0-23, and am currently
  running 4.4.0-21 to see if it reproduces there as well.

  I do have -proposed enabled so it's a bit hard to determine if this is
  the kernel or something higher up the stack.

  This does seem to be mildly reproducible. 4.4.0-23 being the most
  problematic kernel so far.

  Of course this is a relatively new laptop so this could be a hardware
  issue as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chiluk 2462 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun  3 14:07:17 2016
  HibernationDevice: RESUME=UUID=4f4ea88e-642e-4be5-bdf0-bbc7f47f5628
  InstallationDate: Installed on 2016-04-25 (38 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 003: ID 04f2:b531 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FBCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=249f91bb-7789-41cc-9cc0-8ba25d7f55bb ro quiet splash pcie_aspm=force 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1588944/+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 1576747] Re: Network manager unable to control wifi after suspend in 16.04

[Dave Chiluk]

@cyphermox

Here's the debug output we worked on today.  I removed most everything
from before I suspended the machine.  Everything remaining is either
from the suspend or the resume.

The output was achieved by adding --log-level=debug to
/lib/systemd/system/NetworkManager.service at the ExecStart= line, and
then restarting.

** Attachment added: "syslog debug output."
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576747/+attachment/4675543/+files/syslog

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 

[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress

[Dave Chiluk]

The above patches do not resolve this issue for my machine.  de-duping
1576747.

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

Title:
  WiFi malfunction after suspend & resume stress

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)   

 
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2

 
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=10 --s3-max-delay=10 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1585863/+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 1576747] Re: Network manager unable to control wifi after suspend in 16.04

[Dave Chiluk]

I went tested the patches for 1585863, but still saw the issue.

** This bug is no longer a duplicate of bug 1585863
   WiFi malfunction after suspend & resume stress

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> 

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

[Dave Chiluk]

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

This appears to be getting some progress via 1585863, so I'm marking it
as a dupe, even though this one is older.

** This bug has been marked a duplicate of bug 1585863
   WiFi malfunction after suspend & resume stress

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 

[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress

[Dave Chiluk]

This really should have been worked via one of the myriad of other older
open bugs related to this, like 1576747.  I'll start duping against this
bug.

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

Title:
  WiFi malfunction after suspend & resume stress

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)   

 
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2

 
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=10 --s3-max-delay=10 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1585863/+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 1576747] Re: Network manager unable to control wifi after suspend in 16.04

[Dave Chiluk]

I just tried 1.2.0-0ubuntu0.16.04.2, shutdown, started up, suspended
resumed, and still see this issue.

I'm sorry, I haven't had more time to debug this myself.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> 

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

[Dave Chiluk]

@aeaeaeaeaeae, virbr0 is owned/created by libvirt as the default network
for kvm.  This issue very likely unrelated.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  Apr 29 09:04:24 

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

[Dave Chiluk]

Well under further review.  Moving wifi zones does not seem to be
necessary, but sleeping for some extended time may be.

I can also confirm that killing and restarting nm-applet is another
less-hammerlike workaround.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

[Dave Chiluk]

So it looks as though I'm able to reproduce this by 
1. Connecting to wifi access point
2. Suspend
3. Move out of range, but in range of another saved access point.
4. Resume.

My computer automatically connected to the new access point, but does
not show any information to that effect.

I'm not sure if the new saved access point is required, but either way
you will no longer be able to manage wireless networks through the
applet.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

[Dave Chiluk]

It's possible.  I'll mark this as a dupe once we know more.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1691] manager: 

[Desktop-packages] [Bug 1576747] [NEW] Network manager unable to control wifi after suspend in 16.04

[Dave Chiluk]

Public bug reported:

After resume from suspend network manager no longer allows me to control
my wifi card, view available wireless networks, or select new ones.
Oddly enough, I'm still able to communicate on the network that I was
connected to prior to suspend.

Running
# sudo service network-manager restart
resolves the issue until the next suspend/resume.

I'll copy what I think is the relevant  portion of syslog below
__
Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: wake 
requested (sleeping: yes  enabled: yes)
Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
Apr 29 09:04:20 x1 laptop-mode: Laptop mode
Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
Apr 29 09:04:20 x1 laptop-mode: Laptop mode
Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: wpa_dbus_get_object_properties: 
failed to get object properties: (none) none
Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1691] manager: 
NetworkManager state is now CONNECTING
Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1698] device 
(wlp4s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1700] device 
(wlp4s0): Activation: (wifi) access point 'chiluks-5g 1' has security, but 
secrets are required.
Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1700] device 
(wlp4s0): state change: config -> need-auth (reason 'none') 

[Desktop-packages] [Bug 1303814] Re: unity-control-center crashed with SIGSEGV in gtk_list_store_reorder()

[Dave Chiluk]

I accidentally added a blank location followed by an actual location to
the "Time in other locations", choose locations dialog box.  I then
clicked sort by time.

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

Title:
  unity-control-center crashed with SIGSEGV in gtk_list_store_reorder()

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

Bug description:
  This issue uses to happen while switching windows using SUPER + W

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140404.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 15:39:00 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-03-31 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140330)
  ProcCmdline: unity-control-center datetime
  SegvAnalysis:
   Segfault happened at: 0x7f18d9d5c334 :   mov
%ebx,(%r14,%rax,4)
   PC (0x7f18d9d5c334) ok
   source "%ebx" ok
   destination "(%r14,%rax,4)" (0x1b15f5284) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   gtk_list_store_reorder () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from 
/usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libdatetime.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-control-center crashed with SIGSEGV in gtk_list_store_reorder()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu13
   deja-dup 30.0-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1303814/+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 1465706] Re: SRU: New upstream releases of nvidia for 14.04.3

[Dave Chiluk]

I should have said. I did however notice that this new driver does not
build against the OLDER kernels.

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

Title:
  SRU: New upstream releases of nvidia for 14.04.3

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-304-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Invalid
Status in nvidia-settings package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released
Status in nvidia-settings source package in Trusty:
  In Progress

Bug description:
  SRU Request:

  [Impact]
  The nvidia packages in Ubuntu 14.04 do not support the backported kernel from 
15.04.

  [Test Case]
  1) Enable the trusty-proposed repository, and install the 
linux-generic-lts-vivid

  2) Install one of the available nvidia packages or, if the nvidia
  driver is already installed, dist-upgrade after adding the -proposed
  repository.

  3) Restart and see if the system boots correctly. If unsure, please
  attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log

  [Regression Potential]
  Low, the packages come from either wily or vivid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1465706/+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 1465706] Re: SRU: New upstream releases of nvidia for 14.04.3

[Dave Chiluk]

After the recent update, I can confirm that bumblee broke for me as
well.  I had the same plymouth goes to black screen problem.

As a shot in the dark *(and me not trusting my installation), I removed
bbswitch and all nvidia related packages, and then installed nvidia-346.
The 3.13.0-62 kernel now boots fine with the new driver.

I did however notice that this new driver does not build against the
newer kernels.

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

Title:
  SRU: New upstream releases of nvidia for 14.04.3

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-304-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Invalid
Status in nvidia-settings package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released
Status in nvidia-settings source package in Trusty:
  In Progress

Bug description:
  SRU Request:

  [Impact]
  The nvidia packages in Ubuntu 14.04 do not support the backported kernel from 
15.04.

  [Test Case]
  1) Enable the trusty-proposed repository, and install the 
linux-generic-lts-vivid

  2) Install one of the available nvidia packages or, if the nvidia
  driver is already installed, dist-upgrade after adding the -proposed
  repository.

  3) Restart and see if the system boots correctly. If unsure, please
  attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log

  [Regression Potential]
  Low, the packages come from either wily or vivid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1465706/+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 1154431] Re: Unity doesn't start up

[Dave Chiluk]

This no longer looks to be an issue in 14.04+ so I'm going to close this
out as won't fix.

** Changed in: nvidia-graphics-drivers (Ubuntu)
   Status: Confirmed = Won't Fix

** Changed in: unity (Ubuntu)
   Status: Confirmed = Won't Fix

** Changed in: unity
   Status: Confirmed = Fix Released

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

Title:
  Unity doesn't start up

Status in Unity:
  Fix Released
Status in nvidia-graphics-drivers package in Ubuntu:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix

Bug description:
  I'm running stock 13.04. Previously I was affected by bug 982889. Now
  that X comes up, I don't see unity - no common toolbar on the top, no
  icons on the left side, no unity in the process list.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
  Uname: Linux 3.8.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.84  Wed Feb 27 04:58:49 
PST 2013
   GCC version:  gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-22ubuntu3)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Mar 13 10:34:40 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus: nvidia-304, 304.84, 3.8.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8400 GS] [10de:0422] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:c733]
  InstallationDate: Installed on 2013-02-01 (39 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64+mac (20130130)
  MachineType: Intel To be filled by O.E.M.
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-12-generic 
root=UUID=0084a9a5-74cd-47ba-afe6-a47d02d0b262 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: Intel
  dmi.board.version: To be filled by O.E.M.
  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.:bvr4.6.3:bd10/29/2009:svnIntel:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnIntel:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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: Intel
  version.compiz: compiz 1:0.9.9~daily13.03.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.4-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3
  xserver.bootTime: Wed Mar 13 10:17:21 2013
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.13.2-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1154431/+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 1436968] [NEW] Window at edge of desktop move workspaces when selected from different workspace

[Dave Chiluk]

Public bug reported:

Impact:
Window moves from edge of far right workspace to half on to far left workspace 

Test case:
1.  Move a window to the far right edge of the far right workspace.
2.  Change focus to the far left workspace.
3.  Select the window that was moved to the far right edge of the far right 
workspace using the launcher.
4.  The window moves roughly launcher width+15 pixels to the right, which 
makes it appear on the far left workspace.

Expected behavior.
Selecting the window causes the viewport to change to the correct workspace.

fyi, this is similar to bug 755842, but not the same.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.7
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 Mar 26 11:59:59 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1507]
InstallationDate: Installed on 2014-01-07 (442 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140106)
MachineType: ASUSTeK COMPUTER INC. UX32VD
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic.efi.signed 
root=UUID=292a06f6-464a-49e4-a244-2c2d668f33b7 ro quiet splash vt.handoff=7
SourcePackage: compiz
UpgradeStatus: No upgrade log present (probably fresh install)
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.name: UX32VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Mar 26 10:03:11 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4931 
 vendor CMN
xserver.version: 2:1.15.1-0ubuntu2.7

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


** Tags: amd64 apport-bug compiz-0.9 cts sts trusty ubuntu

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

Title:
  Window at edge of desktop move workspaces when selected from different
  workspace

Status in compiz package in Ubuntu:
  New

Bug description:
  Impact:
  Window moves from edge of far right workspace to half on to far left 
workspace 

  Test case:
  1.  Move a window to the far right edge of the far right workspace.
  2.  Change focus to the far left workspace.
  3.  Select the window that was moved to the far right edge of the far right 
workspace using the launcher.
  4.  The window moves roughly launcher width+15 pixels to the right, which 
makes it appear on the far left workspace.

  Expected behavior.
  Selecting the window causes the viewport to change to the correct workspace.

  fyi, this is similar to bug 755842, but not the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  

[Desktop-packages] [Bug 1240088] Re: add network (nm-applet) to login screen

[Dave Chiluk]

** Tags added: cts

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

Title:
  add network (nm-applet) to login screen

Status in “network-manager-applet” package in Ubuntu:
  Fix Released
Status in “unity-greeter” package in Ubuntu:
  Fix Released
Status in “network-manager-applet” source package in Precise:
  In Progress
Status in “unity-greeter” source package in Precise:
  In Progress

Bug description:
  [Impact] 
   * User has a hard time to login via network, (krb5) if nm-applet is not 
accessible via login screen. 

  [Test Case]
  1) make sure the system is configure to authenticate via krb5
  2) login with user A and disconnect from the network via nm-applet, logout
  3) Try to login with user B

   a. Actual Results:
  User B is not able to authenticate because the system is not connected to the 
network so we are not able to talk to the krb servers

   b. Expected Results:
  Users should be able to use network manager from within unity greater and 
reconnect to the network before attempting to login.

  
  [Regression Potential] 
   * n/a . The patch is a backport from upstream

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1240088/+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 861268] Re: text corruption in terminals (xterm, urxvt) and emacs

[Dave Chiluk]

** Changed in: compiz-core
 Assignee: Kip Warner (kip) = (unassigned)

** Changed in: compiz
 Assignee: Kip Warner (kip) = (unassigned)

** Changed in: compiz (Ubuntu)
 Assignee: Kip Warner (kip) = (unassigned)

** Changed in: nvidia-graphics-drivers (Ubuntu)
 Assignee: Kip Warner (kip) = (unassigned)

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

Title:
  text corruption in terminals (xterm, urxvt) and emacs

Status in Compiz:
  Confirmed
Status in Compiz Core:
  Confirmed
Status in “compiz” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers” package in Ubuntu:
  Confirmed

Bug description:
  Using tmux with urxvt results in frequent screen corruption.

  I am running tmux as tmux -2 to enable 256 colour mode and my
  .tmux.conf contains:

  set-option -g default-terminal screen-256color

  ... to enable 256 colours for apps running inside tmux. When
  corruption occurs, neither clearing the screen with clear or tput
  clear helps. What does seem to help is switching to another tmux
  window and back to the problematic one.

  This configuration used to work fine in natty.
  --- 
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  280.13  Wed Jul 27 16:55:43 PDT 
2011
   GCC version:  gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  DistUpgraded: Log time: 2011-09-25 10:58:52.659181
  DistroCodename: oneiric
  DistroRelease: Ubuntu 11.10
  DistroVariant: ubuntu
  GraphicsCard:
   nVidia Corporation GT218 [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo ThinkPad T410 [17aa:2142]
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  JockeyStatus:
   xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, 
Enabled, In use)
   xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Disabled, Not in use)
  MachineType: LENOVO 2516CTO
  NonfreeKernelModules: nvidia
  Package: unity 4.24.0-0ubuntu2b1
  PackageArchitecture: i386
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic-pae 
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro acpi_sleep=nonvs quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
  Tags:  oneiric running-unity ubuntu compiz-0.9 oneiric running-unity oneiric 
running-unity oneiric running-unity ubuntu compiz-0.9
  Uname: Linux 3.0.0-12-generic-pae i686
  UpgradeStatus: Upgraded to oneiric on 2011-09-25 (43 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET72WW (1.32 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu5
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

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

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

[Desktop-packages] [Bug 1307109] Re: Alcor Micro AU9540 keeps powering down when card is present

[Dave Chiluk]

** Changed in: pcsc-lite (Ubuntu)
 Assignee: Kip Warner (kip) = Dariusz Gadomski (dgadomski)

** Changed in: pcsc-lite (Ubuntu)
 Assignee: Dariusz Gadomski (dgadomski) = (unassigned)

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

Title:
  Alcor Micro AU9540 keeps powering down when card is present

Status in “pcsc-lite” package in Ubuntu:
  Confirmed

Bug description:
  I have smart card reader built-into this laptop, however, whenever I
  insert a card - it'll read it for a few seconds, then the USB
  connection to the reader gets powered down and thus the card
  disappears in the systems eyes.

  After a few seconds, it comes back and everything's happy.

  Then the cycle repeats again and again and again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-23-generic 3.13.0-23.45 [modified: 
boot/vmlinuz-3.13.0-23-generic]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jpds   3933 F pulseaudio
   /dev/snd/controlC0:  jpds   3933 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr  6 18:37:24 2014
  HibernationDevice: RESUME=UUID=05490d4c-6800-46a1-b5ba-8b32bdc57e89
  InstallationDate: Installed on 2014-04-06 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140406)
  MachineType: Hewlett-Packard HP EliteBook Folio 1040 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-23-generic N/A
   linux-backports-modules-3.13.0-23-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/09/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L83 Ver. 01.05
  dmi.board.name: 213E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.2A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL83Ver.01.05:bd02/09/2014:svnHewlett-Packard:pnHPEliteBookFolio1040G1:pvrA3009DD18303:rvnHewlett-Packard:rn213E:rvrKBCVersion24.2A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook Folio 1040 G1
  dmi.product.version: A3009DD18303
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1307109/+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 1311403] Re: Can't type password after resume.

[Dave Chiluk]

Same issue here.  This really should be a security concern.   Any one of
us could have been typing our password directly into irc if it was in
focus behind the lock screen.

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

Title:
  Can't type password after resume.

Status in Unity:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I couldn't type password after resume - no characters displayed this
  time.

  I had to Ctrl+alt+f2 and service lightdm restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Tue Apr 22 17:37:49 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-23 (150 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1311403/+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 269904] Re: Screen refresh problems with nvidia cards

[Dave Chiluk]

I sent James Jones a message on Linked-in directing him to this bug,
hopefully that helps.  The interwebs are a beautiful and often very
small place.

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

Title:
  Screen refresh problems with nvidia cards

Status in Compiz:
  In Progress
Status in “compiz” package in Ubuntu:
  Invalid
Status in “compiz-fusion-plugins-main” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-177” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers-180” package in Ubuntu:
  Invalid
Status in “compiz” source package in Intrepid:
  Fix Released
Status in “compiz-fusion-plugins-main” source package in Intrepid:
  Won't Fix
Status in “nvidia-graphics-drivers-177” source package in Intrepid:
  Won't Fix
Status in “nvidia-graphics-drivers-180” source package in Intrepid:
  Invalid
Status in “compiz-fusion-plugins-main” package in Debian:
  Fix Released

Bug description:
  == Proposed compiz-fusion-plugins-main patch ==
  See comment 234 by Anders Kaseorg and attached 
compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff.

  == Original report ==
  Binary package hint: compiz

  I'm using latest compiz on intrepid.

  Since jockey-gtk does not work on my box (I already filed a bug), I
  manually installed nvidia-glx-177 and added the driver → nvidia line
  to xorg.conf.

  Now I seem to be having some screen refresh problems when using
  compiz: parts of the screen are refreshed, but others aren't. That
  means nautilus doesn't show files or folders until I move the cursor
  over them, firefox doesn't show webpages properly until I scroll down,
  and so on.

  Please, tell me if there is any additional info I can provide to find
  out the cause.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/269904/+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 1183269] Re: new upstream release 9.1.3

[Dave Chiluk]

Yep 9.1.3-0ubuntu0.2 available from bug #1187500 resolves the issue .

Moved this bug to regression-proposed and verification-failed per the
SRUVerification page.

** Tags removed: verification-needed
** Tags added: regression-proposed verification-failed

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

Title:
  new upstream release 9.1.3

Status in “mesa” package in Ubuntu:
  Fix Released
Status in “mesa” source package in Raring:
  Fix Committed

Bug description:
  [Impact]
   * Improves support for richland by adding new pci ids.
   * Closest the following upstream bugs in 9.1.3:
  39251 - Second Life viewers from release 2.7.4.235167 to the last 
3.4.0.264911 crash on start.
  47478 - [wine] GLX_DONT_CARE does not work for GLX_DRAWABLE_TYPE or 
GLX_RENDER_TYPE
  56416 - [SNB bisected] SNB hang with rc6 and hiz on glxgears (and other 
GL apps) immediately after xinit.
  57436 - [GLSL1.40 IVB/HSW]Piglit 
spec/glsl-1.40/compiler_built-in-functions/inverse-mat2.frag fails61554 - 
[ivb] Mesa 9.1 performance regression on KWin's Lanczos shader
  61773 - abort is an incredibly not-smart way to handle IR validation
  62868 - solaris build broken with missing ffsll
  62999 - glXChooseFBConfig with GLX_DRAWABLE_TYPE, GLX_DONT_CARE fails
63078 - EGL X11 Regression: Maximum swap interval is 0 (worked with 9.0)
  63447 - [i965 Bisected]Ogles1conform/Ogles2conform/Ogles3conform cases 
segfault
  64662 - [SNB 9.1 Bisected]Ogles2conform 
GL2ExtensionTests/depth_texture_cube_map/depth_texture_cube_map.test fail
   * Closes the following upstream bugs in 9.1.2:
  44567 - [965gm] green artifacts when using GLSL in XBMC
  59238 - many new symbols in libxatracker after recent automake work
  59445 - [SNB/IVB/HSW Bisected]Oglc draw-buffers2(advanced.blending.none) 
segfault
  59495 - [i965 Bisected]Oglc fbblit(advanced.blitFb-3d-cube.mirror.both) 
fails
  60503 - [r300g] Unigine Heaven 3.0: all objects are black
  60510 - Firefox 18.0.2 Crash On Nvidia GeForce2
  61197 - [SNB Bisected] kwin_gles screen corruption
  61317 - [IVB] corrupt rendering with UBOs
  61395 - glEdgeFlag can't be set to false
  61947 - nullpointer dereference causes xorg-server segfault when nouveau 
DRI driver is loaded
  62357 - llvmpipe: Fragment Shader with return in main causes back output
  62434 - [bisected] 3284.073] (EE) AIGLX error: dlopen of 
/usr/lib/xorg/modules
  Debian #349437 - mesa - FTBFS: error: 'IEEE_ONE' undeclared
  Redhat #918661 - crash in routine Avogadro UI manipulation

  [Test Case]
   * Package is uploaded to saucy, a full piglit run will be done on i915, 
nouveau and ati.
   * Make sure that the unity dash blur is still fast on all cards.

  [Regression Potential]
   * Previous mesa had a patch reverted that caused unity's dash blur effect to 
be slow. Fixes have been pulled into 9.1.3 for this, and the revert no longer 
applies.
   * There's always the possibility for regressions like gpu lockups and 
rendering errors. Those should be watched.

  [Other Info]
   * Mesa has a MRE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1183269/+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 1187500] Re: [Saucy] Unity is slow on Intel graphics

[Dave Chiluk]

Tested, 9.1.3-0ubuntu0.2 fixes the regression introeduced by LP:
#1183269

Thanks.

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

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

Title:
  [Saucy] Unity is slow on Intel graphics

Status in “mesa” package in Ubuntu:
  Fix Released
Status in “mesa” source package in Raring:
  Fix Committed
Status in “mesa” source package in Saucy:
  Fix Released

Bug description:
  For the last few weeks, unity and/or compiz has been crazy slow on both my 
computers with Intel graphics, alt+tab can take 2-3 seconds to complete. The 
lag can be seen across the board with the dash as well.
  It worked fantastically well with previous versions, as well as at the 
beggining of the Saucy cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.9.0-3.8-generic 3.9.4
  Uname: Linux 3.9.0-3-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jun  4 14:17:39 2013
  DistUpgraded: 2013-05-15 16:20:35,929 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
  InstallationDate: Installed on 2012-07-31 (307 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-3-generic 
root=UUID=aac1b22f-87ee-4bc5-929b-1c9335912968 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to saucy on 2013-05-15 (19 days ago)
  dmi.bios.date: 02/17/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3202
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.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.:bvr3202:bd02/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPROGEN3:rvrRev1.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.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.45-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.7-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Fri May 31 19:02:46 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu10
  xserver.video_driver: intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1187500/+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 1183269] Re: new upstream release 9.1.3

[Dave Chiluk]

I think this should go to verification failed, as it introduced 1187500
which basically makes the dash and alt-tab unusable.

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

Title:
  new upstream release 9.1.3

Status in “mesa” package in Ubuntu:
  Fix Released
Status in “mesa” source package in Raring:
  Fix Committed

Bug description:
  [Impact]
   * Improves support for richland by adding new pci ids.
   * Closest the following upstream bugs in 9.1.3:
  39251 - Second Life viewers from release 2.7.4.235167 to the last 
3.4.0.264911 crash on start.
  47478 - [wine] GLX_DONT_CARE does not work for GLX_DRAWABLE_TYPE or 
GLX_RENDER_TYPE
  56416 - [SNB bisected] SNB hang with rc6 and hiz on glxgears (and other 
GL apps) immediately after xinit.
  57436 - [GLSL1.40 IVB/HSW]Piglit 
spec/glsl-1.40/compiler_built-in-functions/inverse-mat2.frag fails61554 - 
[ivb] Mesa 9.1 performance regression on KWin's Lanczos shader
  61773 - abort is an incredibly not-smart way to handle IR validation
  62868 - solaris build broken with missing ffsll
  62999 - glXChooseFBConfig with GLX_DRAWABLE_TYPE, GLX_DONT_CARE fails
63078 - EGL X11 Regression: Maximum swap interval is 0 (worked with 9.0)
  63447 - [i965 Bisected]Ogles1conform/Ogles2conform/Ogles3conform cases 
segfault
  64662 - [SNB 9.1 Bisected]Ogles2conform 
GL2ExtensionTests/depth_texture_cube_map/depth_texture_cube_map.test fail
   * Closes the following upstream bugs in 9.1.2:
  44567 - [965gm] green artifacts when using GLSL in XBMC
  59238 - many new symbols in libxatracker after recent automake work
  59445 - [SNB/IVB/HSW Bisected]Oglc draw-buffers2(advanced.blending.none) 
segfault
  59495 - [i965 Bisected]Oglc fbblit(advanced.blitFb-3d-cube.mirror.both) 
fails
  60503 - [r300g] Unigine Heaven 3.0: all objects are black
  60510 - Firefox 18.0.2 Crash On Nvidia GeForce2
  61197 - [SNB Bisected] kwin_gles screen corruption
  61317 - [IVB] corrupt rendering with UBOs
  61395 - glEdgeFlag can't be set to false
  61947 - nullpointer dereference causes xorg-server segfault when nouveau 
DRI driver is loaded
  62357 - llvmpipe: Fragment Shader with return in main causes back output
  62434 - [bisected] 3284.073] (EE) AIGLX error: dlopen of 
/usr/lib/xorg/modules
  Debian #349437 - mesa - FTBFS: error: 'IEEE_ONE' undeclared
  Redhat #918661 - crash in routine Avogadro UI manipulation

  [Test Case]
   * Package is uploaded to saucy, a full piglit run will be done on i915, 
nouveau and ati.
   * Make sure that the unity dash blur is still fast on all cards.

  [Regression Potential]
   * Previous mesa had a patch reverted that caused unity's dash blur effect to 
be slow. Fixes have been pulled into 9.1.3 for this, and the revert no longer 
applies.
   * There's always the possibility for regressions like gpu lockups and 
rendering errors. Those should be watched.

  [Other Info]
   * Mesa has a MRE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1183269/+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 1187500] Re: [Saucy] Unity is slow on Intel graphics

[Dave Chiluk]

** Tags added: raring

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

Title:
  [Saucy] Unity is slow on Intel graphics

Status in “mesa” package in Ubuntu:
  Fix Released
Status in “mesa” source package in Raring:
  In Progress
Status in “mesa” source package in Saucy:
  Fix Released

Bug description:
  For the last few weeks, unity and/or compiz has been crazy slow on both my 
computers with Intel graphics, alt+tab can take 2-3 seconds to complete. The 
lag can be seen across the board with the dash as well.
  It worked fantastically well with previous versions, as well as at the 
beggining of the Saucy cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.9.0-3.8-generic 3.9.4
  Uname: Linux 3.9.0-3-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jun  4 14:17:39 2013
  DistUpgraded: 2013-05-15 16:20:35,929 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
  InstallationDate: Installed on 2012-07-31 (307 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-3-generic 
root=UUID=aac1b22f-87ee-4bc5-929b-1c9335912968 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to saucy on 2013-05-15 (19 days ago)
  dmi.bios.date: 02/17/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3202
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.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.:bvr3202:bd02/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPROGEN3:rvrRev1.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.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.45-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.7-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Fri May 31 19:02:46 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu10
  xserver.video_driver: intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1187500/+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 1154431] Re: Unity doesn't start up

[Dave Chiluk]

** Tags added: unity

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

Title:
  Unity doesn't start up

Status in “nvidia-graphics-drivers” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I'm running stock 13.04. Previously I was affected by bug 982889. Now
  that X comes up, I don't see unity - no common toolbar on the top, no
  icons on the left side, no unity in the process list.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
  Uname: Linux 3.8.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.84  Wed Feb 27 04:58:49 
PST 2013
   GCC version:  gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-22ubuntu3)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Mar 13 10:34:40 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus: nvidia-304, 304.84, 3.8.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8400 GS] [10de:0422] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:c733]
  InstallationDate: Installed on 2013-02-01 (39 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64+mac (20130130)
  MachineType: Intel To be filled by O.E.M.
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-12-generic 
root=UUID=0084a9a5-74cd-47ba-afe6-a47d02d0b262 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: Intel
  dmi.board.version: To be filled by O.E.M.
  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.:bvr4.6.3:bd10/29/2009:svnIntel:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnIntel:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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: Intel
  version.compiz: compiz 1:0.9.9~daily13.03.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.4-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu3
  xserver.bootTime: Wed Mar 13 10:17:21 2013
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.13.2-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1154431/+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 993655] Re: Unity looses mouse click handler when using enabling USB headset

[Dave Chiluk]

A similar issue was resolved for a Creative Labs headset in
https://pad.lv/1007575 with kernel 3.5.0-24.37 which has been released.

If you are running a kernel later than that and this is still occurring
please say so in a comment.

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

Title:
  Unity looses mouse click handler when using enabling USB headset

Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  I have a Plantronics D100 headset.

  When I press the button on the headset to enable it, Unity looses its
  click handler, in that it can not click and drag windows.

  The cursor is visible and moves just fine. I can switch applications
  using Alt+Tab, and I can launch new applications using the keyboard.
  But I cannot close the existing window, or change focus to another
  window by using the mouse.

  The Headset microphone and speaker work just fine!

  Tested this on a laptop and desktop machine. Both running Ubuntu
  12.04.

  The headset I'm using is a Plantronics D100 unit.

  I have had this problem for the past month while on the 12.04 beta release. 
  --- 
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  NonfreeKernelModules: nvidia
  Package: unity 5.10.0-0ubuntu6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Tags:  precise
  Uname: Linux 3.2.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/993655/+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 993655] Re: Unity looses mouse click handler when using enabling USB headset

[Dave Chiluk]

Well apparently pad.lv doesn't like https.   Here's the direct link to
that other bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1007575

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

Title:
  Unity looses mouse click handler when using enabling USB headset

Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  I have a Plantronics D100 headset.

  When I press the button on the headset to enable it, Unity looses its
  click handler, in that it can not click and drag windows.

  The cursor is visible and moves just fine. I can switch applications
  using Alt+Tab, and I can launch new applications using the keyboard.
  But I cannot close the existing window, or change focus to another
  window by using the mouse.

  The Headset microphone and speaker work just fine!

  Tested this on a laptop and desktop machine. Both running Ubuntu
  12.04.

  The headset I'm using is a Plantronics D100 unit.

  I have had this problem for the past month while on the 12.04 beta release. 
  --- 
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  NonfreeKernelModules: nvidia
  Package: unity 5.10.0-0ubuntu6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Tags:  precise
  Uname: Linux 3.2.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/993655/+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 1154153] [NEW] Nvidia module crash: GPU has fallen off the bus.

[Dave Chiluk]

Public bug reported:

The last two mornings, the nvidia module has crashed during the middle
of the night (4 a.m.).  The displays are set to turn off and lock, but
the machine is not set up to go into suspend.

Here's an excerpt from the earliest error in kern.log.

kernel: [144532.511018] hda-intel: spurious response 0x1:0x0, last cmd=0x4f0700
kernel: [144532.511021] hda-intel: spurious response 0x40:0x0, last cmd=0x4f0700
kernel: [144532.511024] hda-intel: spurious response 0x0:0x0, last cmd=0x4f0700
kernel: [144532.777203] NVRM: GPU at :01:00.0 has fallen off the bus.
kernel: [144532.777214] NVRM: GPU at :01:00.0 has fallen off the bus.
kernel: [144582.521101] show_signal_msg: 51 callbacks suppressed
kernel: [144582.521108] Xorg[2151]: segfault at 617461481d ip 7fe6533bbd41 
sp 7fff94311438 error 4 in nvidia_drv.so[7fe652f47000+634000]
kernel: [144582.814351] init: lightdm main process (2129) terminated with 
status 1
kernel: [144597.810481] init: failsafe-x main process (28549) terminated with 
status 1
kernel: [144608.298745] BUG: soft lockup - CPU#1 stuck for 22s! [dconf 
worker:3334]
kernel: [144608.298883] Modules linked in: ip6table_filter ip6_tables 
ebtable_nat ebtables pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) 
ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state 
nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter 
ip_tables x_tables kvm_intel kvm bnep rfcomm parport_pc ppdev binfmt_misc nfsd 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev uvcvideo snd_usb_audio videodev 
snd_usbmidi_lib btusb v4l2_compat_ioctl32 hid_microsoft bluetooth bridge stp 
snd_hda_intel nvidia(P) snd_hda_codec snd_hwdep snd_pcm psmouse snd_seq_midi 
snd_rawmidi snd_seq_midi_event snd_seq snd_timer i7core_edac snd_seq_device 
dm_multipath edac_core serio_raw snd soundcore snd_page_alloc mac_hid lp 
parport nfs lockd fscache auth_rpcgss nfs_acl sunrpc usbhid hid r8169 
pata_jmicron
kernel: [144608.298925] CPU 1 
kernel: [144608.298926] Modules linked in: ip6table_filter ip6_tables 
ebtable_nat ebtables pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) 
ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state 
nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter 
ip_tables x_tables kvm_intel kvm bnep rfcomm parport_pc ppdev binfmt_misc nfsd 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev uvcvideo snd_usb_audio videodev 
snd_usbmidi_lib btusb v4l2_compat_ioctl32 hid_microsoft bluetooth bridge stp 
snd_hda_intel nvidia(P) snd_hda_codec snd_hwdep snd_pcm psmouse snd_seq_midi 
snd_rawmidi snd_seq_midi_event snd_seq snd_timer i7core_edac snd_seq_device 
dm_multipath edac_core serio_raw snd soundcore snd_page_alloc mac_hid lp 
parport nfs lockd fscache auth_rpcgss nfs_acl sunrpc usbhid hid r8169 
pata_jmicron
kernel: [144608.298956] 
kernel: [144608.298958] Pid: 3334, comm: dconf worker Tainted: P   O 
3.2.0-39-generic #62-Ubuntu BIOSTAR Group TP55/TP55
kernel: [144608.298961] RIP: 0010:[a02b54ed]  [a02b54ed] 
_nv012125rm+0x49/0x51 [nvidia]
kernel: [144608.299043] RSP: 0018:8807ed7e5828  EFLAGS: 0246
kernel: [144608.299044] RAX:  RBX: 8807ed7e57b8 RCX: 
000d
kernel: [144608.299045] RDX: 2000 RSI: 548d RDI: 
88080b57c034
kernel: [144608.299047] RBP: 8807fe03de80 R08: 00070004 R09: 
8807fe03dea8
kernel: [144608.299048] R10:  R11: 0001 R12: 
8103ec69
kernel: [144608.299049] R13: 8807ed7e5798 R14: 8103ec69 R15: 
8807ed7e5788
kernel: [144608.299051] FS:  7f084ad5b700() GS:88083fc4() 
knlGS:
kernel: [144608.299052] CS:  0010 DS:  ES:  CR0: 8005003b
kernel: [144608.299054] CR2: 12367832e4f0 CR3: 01c05000 CR4: 
06e0
kernel: [144608.299055] DR0:  DR1:  DR2: 

kernel: [144608.299057] DR3:  DR6: 0ff0 DR7: 
0400
kernel: [144608.299058] Process dconf worker (pid: 3334, threadinfo 
8807ed7e4000, task 8807fcc64500)
kernel: [144608.299059] Stack:
kernel: [144608.299081]   a02b4a6a 88080b57c008 
88080b57c008
kernel: [144608.299084]  00070004 a0584399 88080b57c008 
a05a09e4
kernel: [144608.299086]  88080b57c008 0045 88080b57c008 
00070004
kernel: [144608.299089] Call Trace:
kernel: [144608.299144]  [a02b4a6a] ? _nv011835rm+0xba/0x1c2 [nvidia]
kernel: [144608.299221]  [a0584399] ? _nv007992rm+0x26/0xb3 [nvidia]
kernel: [144608.299299]  [a05a09e4] ? _nv003210rm+0x48b3/0xaf83 
[nvidia]
kernel: [144608.299372]  [a0521450] ? _nv005265rm+0x116/0x1b9 [nvidia]
kernel: [144608.299446]  [a052163d] ? _nv005084rm+0x14a/0x1ed [nvidia]
kernel: [144608.299508]  

[Desktop-packages] [Bug 1154153] Re: Nvidia module crash: GPU has fallen off the bus.

[Dave Chiluk]

This has some interesting, and possibly related reading.
http://www.cyberciti.biz/faq/debian-ubuntu-rhel-fedora-linux-nvidia-
nvrm-gpu-fallen-off-bus/

The suggested solution is to turn on persistence for the nvidia card using
# /usr/bin/nvidia-smi -pm 1

This was never an issue with 3.2.0-38+310.14-0ubuntu0.1 *(the same
version I am currently running).


This also could be as simple as a real hardware issue.

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

Title:
  Nvidia module crash: GPU has fallen off the bus.

Status in “xorg” package in Ubuntu:
  New

Bug description:
  The last two mornings, the nvidia module has crashed during the middle
  of the night (4 a.m.).  The displays are set to turn off and lock, but
  the machine is not set up to go into suspend.

  Here's an excerpt from the earliest error in kern.log.

  kernel: [144532.511018] hda-intel: spurious response 0x1:0x0, last 
cmd=0x4f0700
  kernel: [144532.511021] hda-intel: spurious response 0x40:0x0, last 
cmd=0x4f0700
  kernel: [144532.511024] hda-intel: spurious response 0x0:0x0, last 
cmd=0x4f0700
  kernel: [144532.777203] NVRM: GPU at :01:00.0 has fallen off the bus.
  kernel: [144532.777214] NVRM: GPU at :01:00.0 has fallen off the bus.
  kernel: [144582.521101] show_signal_msg: 51 callbacks suppressed
  kernel: [144582.521108] Xorg[2151]: segfault at 617461481d ip 
7fe6533bbd41 sp 7fff94311438 error 4 in 
nvidia_drv.so[7fe652f47000+634000]
  kernel: [144582.814351] init: lightdm main process (2129) terminated with 
status 1
  kernel: [144597.810481] init: failsafe-x main process (28549) terminated with 
status 1
  kernel: [144608.298745] BUG: soft lockup - CPU#1 stuck for 22s! [dconf 
worker:3334]
  kernel: [144608.298883] Modules linked in: ip6table_filter ip6_tables 
ebtable_nat ebtables pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) 
ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state 
nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter 
ip_tables x_tables kvm_intel kvm bnep rfcomm parport_pc ppdev binfmt_misc nfsd 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev uvcvideo snd_usb_audio videodev 
snd_usbmidi_lib btusb v4l2_compat_ioctl32 hid_microsoft bluetooth bridge stp 
snd_hda_intel nvidia(P) snd_hda_codec snd_hwdep snd_pcm psmouse snd_seq_midi 
snd_rawmidi snd_seq_midi_event snd_seq snd_timer i7core_edac snd_seq_device 
dm_multipath edac_core serio_raw snd soundcore snd_page_alloc mac_hid lp 
parport nfs lockd fscache auth_rpcgss nfs_acl sunrpc usbhid hid r8169 
pata_jmicron
  kernel: [144608.298925] CPU 1 
  kernel: [144608.298926] Modules linked in: ip6table_filter ip6_tables 
ebtable_nat ebtables pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) 
ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state 
nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter 
ip_tables x_tables kvm_intel kvm bnep rfcomm parport_pc ppdev binfmt_misc nfsd 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev uvcvideo snd_usb_audio videodev 
snd_usbmidi_lib btusb v4l2_compat_ioctl32 hid_microsoft bluetooth bridge stp 
snd_hda_intel nvidia(P) snd_hda_codec snd_hwdep snd_pcm psmouse snd_seq_midi 
snd_rawmidi snd_seq_midi_event snd_seq snd_timer i7core_edac snd_seq_device 
dm_multipath edac_core serio_raw snd soundcore snd_page_alloc mac_hid lp 
parport nfs lockd fscache auth_rpcgss nfs_acl sunrpc usbhid hid r8169 
pata_jmicron
  kernel: [144608.298956] 
  kernel: [144608.298958] Pid: 3334, comm: dconf worker Tainted: P   O 
3.2.0-39-generic #62-Ubuntu BIOSTAR Group TP55/TP55
  kernel: [144608.298961] RIP: 0010:[a02b54ed]  [a02b54ed] 
_nv012125rm+0x49/0x51 [nvidia]
  kernel: [144608.299043] RSP: 0018:8807ed7e5828  EFLAGS: 0246
  kernel: [144608.299044] RAX:  RBX: 8807ed7e57b8 RCX: 
000d
  kernel: [144608.299045] RDX: 2000 RSI: 548d RDI: 
88080b57c034
  kernel: [144608.299047] RBP: 8807fe03de80 R08: 00070004 R09: 
8807fe03dea8
  kernel: [144608.299048] R10:  R11: 0001 R12: 
8103ec69
  kernel: [144608.299049] R13: 8807ed7e5798 R14: 8103ec69 R15: 
8807ed7e5788
  kernel: [144608.299051] FS:  7f084ad5b700() GS:88083fc4() 
knlGS:
  kernel: [144608.299052] CS:  0010 DS:  ES:  CR0: 8005003b
  kernel: [144608.299054] CR2: 12367832e4f0 CR3: 01c05000 CR4: 
06e0
  kernel: [144608.299055] DR0:  DR1:  DR2: 

  kernel: [144608.299057] DR3:  DR6: 0ff0 DR7: 
0400
  kernel: [144608.299058] Process dconf worker (pid: 3334, threadinfo 
8807ed7e4000, task 8807fcc64500)
  kernel: [144608.299059] Stack:
  

[Desktop-packages] [Bug 1080882] Re: Creative HS-950 USB headset causes X BUG, can't click outside window

[Dave Chiluk]

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

Christoph Keller, I need a favor.  I need you to verify this fix now in
the proposed kernel.  If it does not get verified this patch will be
removed.

The precise kernel is 3.2.0-38.59.
and in the quantal kernel is 3.5.0-24.37

Unfortunately since my headset has now died, I can not verify that the
latest kernel indeed solves the problem.  Can you update to 3.2.0-38 by
enabling the proposed repositories and verifying by adding a comment
both here and in http://pad.lv/1007575

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

Title:
  Creative HS-950 USB headset causes X BUG, can't click outside window

Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  Bug is similar to this one: https://bugs.launchpad.net/ubuntu/+source
  /xorg-server/+bug/1007575

  Pulseaudio usually crashes on login (if the headset is plugged) or
  when a sound is played. The only way to be able to click outside the
  active window is to unplug the headset.

  /var/log/Xorg.0.log:

  
  [34.792] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [34.792] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [34.792] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [34.792] (**) Creative Technology Creative USB Headset: always reports 
core events
  [34.792] (**) evdev: Creative Technology Creative USB Headset: Device: 
/dev/input/event6
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Vendor 
0x41e Product 0x400
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Found 8 
mouse buttons
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Found keys
  [34.792] (II) evdev: Creative Technology Creative USB Headset: Forcing 
relative x/y axes to exist.
  [34.792] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as mouse
  [34.792] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as keyboard
  [34.792] (**) evdev: Creative Technology Creative USB Headset: 
YAxisMapping: buttons 4 and 5
  [34.792] (**) evdev: Creative Technology Creative USB Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [34.792] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input14/event6
  [34.793] (II) XINPUT: Adding extended input device Creative Technology 
Creative USB Headset (type: KEYBOARD, id 11)
  [34.793] (**) Option xkb_rules evdev
  [34.793] (**) Option xkb_model pc105
  [34.793] (**) Option xkb_layout pt
  [35.200] (II) config/udev: removing device Creative Technology Creative 
USB Headset
  [35.204] (II) evdev: Creative Technology Creative USB Headset: Close
  [35.204] (II) UnloadModule: evdev
  [35.552] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [35.552] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [35.552] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [35.552] (**) Creative Technology Creative USB Headset: always reports 
core events
  [35.552] (**) evdev: Creative Technology Creative USB Headset: Device: 
/dev/input/event6
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Vendor 
0x41e Product 0x400
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Found 8 
mouse buttons
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Found keys
  [35.552] (II) evdev: Creative Technology Creative USB Headset: Forcing 
relative x/y axes to exist.
  [35.552] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as mouse
  [35.552] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as keyboard
  [35.552] (**) evdev: Creative Technology Creative USB Headset: 
YAxisMapping: buttons 4 and 5
  [35.552] (**) evdev: Creative Technology Creative USB Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [35.552] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input15/event6
  [35.552] (II) XINPUT: Adding extended input device Creative Technology 
Creative USB Headset (type: KEYBOARD, id 11)
  [35.552] (**) Option xkb_rules evdev
  [35.552] (**) Option xkb_model pc105
  [35.552] (**) Option xkb_layout pt
  [  2988.170] (II) config/udev: removing device Creative Technology Creative 
USB Headset
  [  2988.172] (II) evdev: Creative Technology Creative USB Headset: Close
  [  2988.172] (II) UnloadModule: evdev
  [  

[Desktop-packages] [Bug 1122177] [NEW] Citrix window minimizes after moving window with ALT+ mouse 1 move.

[Dave Chiluk]

Public bug reported:

Steps to reproduce.

1. Install Citrix Reciever
2. Open a demo cloud application like Word.  Available at 
http://demo.citrixcloud.net  after free login registration at 
http://citrixcloud.net/
3. Hold ALT + Left click on an application window.
4. Start moving mouse
5. Release Alt.
6. Release left click.
7. Stop moving mose.

Video of reproduce here.
http://people.canonical.com/~chiluk/citrix/Minimize.ogv

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-38.59-generic 3.2.37
Uname: Linux 3.2.0-38-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  310.14  Tue Oct  9 11:52:41 
PDT 2012
 GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
.tmp.unity.support.test.0:
 
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,grid,vpswitch,move,place,imgpng,regex,gnomecompat,snap,compiztoolbox,session,mousepoll,resize,unitymtgrabhandles,wall,animation,fade,workarounds,expo,ezoom,scale,unityshell]
CompositorRunning: compiz
Date: Mon Feb 11 09:54:02 2013
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
DkmsStatus:
 nvidia-experimental-310, 310.14, 3.2.0-37-generic, x86_64: installed
 nvidia-experimental-310, 310.14, 3.2.0-38-generic, x86_64: installed
 vboxhost, 4.2.6, 3.2.0-36-generic, x86_64: installed
 vboxhost, 4.2.6, 3.2.0-37-generic, x86_64: installed
 vboxhost, 4.2.6, 3.2.0-38-generic, x86_64: installed
ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed
GraphicsCard:
 NVIDIA Corporation Device [10de:1183] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Device [196e:1000]
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
JockeyStatus:
 xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release 
updates) (Proprietary, Disabled, Not in use)
 xorg:nvidia_experimental_304 - NVIDIA accelerated graphics driver 
(**experimental** beta) (Proprietary, Disabled, Not in use)
 xorg:nvidia_experimental_310 - NVIDIA accelerated graphics driver 
(**experimental** beta) (Proprietary, Enabled, In use)
MachineType: BIOSTAR Group TP55
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-38-generic 
root=UUID=fd58abb9-56f2-4094-8191-d931dea02669 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/02/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: None
dmi.board.name: TP55
dmi.board.vendor: BIOSTAR Group
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.chassis.version: 6.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd06/02/2010:svnBIOSTARGroup:pnTP55:pvr6.0:rvnBIOSTARGroup:rnTP55:rvr:cvnBIOSTARGroup:ct3:cvr6.0:
dmi.product.name: TP55
dmi.product.version: 6.0
dmi.sys.vendor: BIOSTAR Group
version.compiz: compiz 1:0.9.7.12-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.39-0ubuntu0.1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.3
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.11
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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


** Tags: amd64 apport-bug compiz-0.9 precise running-unity ubuntu

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

Title:
  Citrix window minimizes after moving window with ALT+ mouse 1 move.

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Steps to reproduce.

  1. Install Citrix Reciever
  2. Open a demo cloud application like Word.  Available at 
http://demo.citrixcloud.net  after free login registration at 
http://citrixcloud.net/
  3. Hold ALT + Left click on an application window.
  4. Start moving mouse
  5. Release Alt.
  6. Release left click.
  7. Stop moving mose.

  Video of reproduce here.
  http://people.canonical.com/~chiluk/citrix/Minimize.ogv

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 1122177] Re: Citrix window minimizes after moving window with ALT+ mouse 1 move.

[Dave Chiluk]

This also reproduces in gnome 2.

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

Title:
  Citrix window minimizes after moving window with ALT+ mouse 1 move.

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Steps to reproduce.

  1. Install Citrix Reciever
  2. Open a demo cloud application like Word.  Available at 
http://demo.citrixcloud.net  after free login registration at 
http://citrixcloud.net/
  3. Hold ALT + Left click on an application window.
  4. Start moving mouse
  5. Release Alt.
  6. Release left click.
  7. Stop moving mose.

  Video of reproduce here.
  http://people.canonical.com/~chiluk/citrix/Minimize.ogv

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-38.59-generic 3.2.37
  Uname: Linux 3.2.0-38-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  310.14  Tue Oct  9 11:52:41 
PDT 2012
   GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,grid,vpswitch,move,place,imgpng,regex,gnomecompat,snap,compiztoolbox,session,mousepoll,resize,unitymtgrabhandles,wall,animation,fade,workarounds,expo,ezoom,scale,unityshell]
  CompositorRunning: compiz
  Date: Mon Feb 11 09:54:02 2013
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-experimental-310, 310.14, 3.2.0-37-generic, x86_64: installed
   nvidia-experimental-310, 310.14, 3.2.0-38-generic, x86_64: installed
   vboxhost, 4.2.6, 3.2.0-36-generic, x86_64: installed
   vboxhost, 4.2.6, 3.2.0-37-generic, x86_64: installed
   vboxhost, 4.2.6, 3.2.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, even including gdb or git bisection work if 
needed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1183] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Device [196e:1000]
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  JockeyStatus:
   xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Disabled, Not in use)
   xorg:nvidia_experimental_304 - NVIDIA accelerated graphics driver 
(**experimental** beta) (Proprietary, Disabled, Not in use)
   xorg:nvidia_experimental_310 - NVIDIA accelerated graphics driver 
(**experimental** beta) (Proprietary, Enabled, In use)
  MachineType: BIOSTAR Group TP55
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-38-generic 
root=UUID=fd58abb9-56f2-4094-8191-d931dea02669 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: None
  dmi.board.name: TP55
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd06/02/2010:svnBIOSTARGroup:pnTP55:pvr6.0:rvnBIOSTARGroup:rnTP55:rvr:cvnBIOSTARGroup:ct3:cvr6.0:
  dmi.product.name: TP55
  dmi.product.version: 6.0
  dmi.sys.vendor: BIOSTAR Group
  version.compiz: compiz 1:0.9.7.12-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.39-0ubuntu0.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.11
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1122177/+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 1122177] Re: Citrix window minimizes after moving window with ALT+ mouse 1 move.

[Dave Chiluk]

** Description changed:

  Steps to reproduce.
  
  1. Install Citrix Reciever
  2. Open a demo cloud application like Word.  Available at 
http://demo.citrixcloud.net  after free login registration at 
http://citrixcloud.net/
  3. Hold ALT + Left click on an application window.
  4. Start moving mouse
  5. Release Alt.
  6. Release left click.
- 7. Stop moving mose.
+ 7. Stop moving mouse.
  
  Video of reproduce here.
  http://people.canonical.com/~chiluk/citrix/Minimize.ogv
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-38.59-generic 3.2.37
  Uname: Linux 3.2.0-38-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  310.14  Tue Oct  9 11:52:41 
PDT 2012
-  GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  310.14  Tue Oct  9 11:52:41 
PDT 2012
+  GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,grid,vpswitch,move,place,imgpng,regex,gnomecompat,snap,compiztoolbox,session,mousepoll,resize,unitymtgrabhandles,wall,animation,fade,workarounds,expo,ezoom,scale,unityshell]
  CompositorRunning: compiz
  Date: Mon Feb 11 09:54:02 2013
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
-  nvidia-experimental-310, 310.14, 3.2.0-37-generic, x86_64: installed
-  nvidia-experimental-310, 310.14, 3.2.0-38-generic, x86_64: installed
-  vboxhost, 4.2.6, 3.2.0-36-generic, x86_64: installed
-  vboxhost, 4.2.6, 3.2.0-37-generic, x86_64: installed
-  vboxhost, 4.2.6, 3.2.0-38-generic, x86_64: installed
+  nvidia-experimental-310, 310.14, 3.2.0-37-generic, x86_64: installed
+  nvidia-experimental-310, 310.14, 3.2.0-38-generic, x86_64: installed
+  vboxhost, 4.2.6, 3.2.0-36-generic, x86_64: installed
+  vboxhost, 4.2.6, 3.2.0-37-generic, x86_64: installed
+  vboxhost, 4.2.6, 3.2.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, even including gdb or git bisection work if 
needed
  GraphicsCard:
-  NVIDIA Corporation Device [10de:1183] (rev a1) (prog-if 00 [VGA controller])
-Subsystem: Device [196e:1000]
+  NVIDIA Corporation Device [10de:1183] (rev a1) (prog-if 00 [VGA controller])
+    Subsystem: Device [196e:1000]
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  JockeyStatus:
-  xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Disabled, Not in use)
-  xorg:nvidia_experimental_304 - NVIDIA accelerated graphics driver 
(**experimental** beta) (Proprietary, Disabled, Not in use)
-  xorg:nvidia_experimental_310 - NVIDIA accelerated graphics driver 
(**experimental** beta) (Proprietary, Enabled, In use)
+  xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Disabled, Not in use)
+  xorg:nvidia_experimental_304 - NVIDIA accelerated graphics driver 
(**experimental** beta) (Proprietary, Disabled, Not in use)
+  xorg:nvidia_experimental_310 - NVIDIA accelerated graphics driver 
(**experimental** beta) (Proprietary, Enabled, In use)
  MachineType: BIOSTAR Group TP55
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-38-generic 
root=UUID=fd58abb9-56f2-4094-8191-d931dea02669 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: None
  dmi.board.name: TP55
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd06/02/2010:svnBIOSTARGroup:pnTP55:pvr6.0:rvnBIOSTARGroup:rnTP55:rvr:cvnBIOSTARGroup:ct3:cvr6.0:
  dmi.product.name: TP55
  dmi.product.version: 6.0
  dmi.sys.vendor: BIOSTAR Group
  version.compiz: compiz 1:0.9.7.12-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.39-0ubuntu0.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.11
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  

[Desktop-packages] [Bug 1122177] Re: Citrix window minimizes after moving window with ALT+ mouse 1 move.

[Dave Chiluk]

I have also noticed what i will call the scared window effect.  Which I
feel is somehow related to whatever is going on in this bug.

Reproduce procedure
1-2 from above.
3. Hold ALT + Left click on an application window.
4. Start moving mouse
5. Release left click.
*** window minimizes like above *** 
6. Release alt.

7. Left click icon in unity bar.
8. Move mouse toward citrix window.
*** Citrix window re-minimizes *** (like it's scared of being used)

Video available here.
http://people.canonical.com/~chiluk/citrix/scaredwindow.ogv

I am not able to reproduce this exactly in gnome, but gnome does
occassionally give me a minimize/maximize/minimize sequence when running
through this test.

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

Title:
  Citrix window minimizes after moving window with ALT+ mouse 1 move.

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Steps to reproduce.

  1. Install Citrix Reciever
  2. Open a demo cloud application like Word.  Available at 
http://demo.citrixcloud.net  after free login registration at 
http://citrixcloud.net/
  3. Hold ALT + Left click on an application window.
  4. Start moving mouse
  5. Release Alt.
  6. Release left click.
  7. Stop moving mouse.

  Video of reproduce here.
  http://people.canonical.com/~chiluk/citrix/Minimize.ogv

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-38.59-generic 3.2.37
  Uname: Linux 3.2.0-38-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  310.14  Tue Oct  9 11:52:41 
PDT 2012
   GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,grid,vpswitch,move,place,imgpng,regex,gnomecompat,snap,compiztoolbox,session,mousepoll,resize,unitymtgrabhandles,wall,animation,fade,workarounds,expo,ezoom,scale,unityshell]
  CompositorRunning: compiz
  Date: Mon Feb 11 09:54:02 2013
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-experimental-310, 310.14, 3.2.0-37-generic, x86_64: installed
   nvidia-experimental-310, 310.14, 3.2.0-38-generic, x86_64: installed
   vboxhost, 4.2.6, 3.2.0-36-generic, x86_64: installed
   vboxhost, 4.2.6, 3.2.0-37-generic, x86_64: installed
   vboxhost, 4.2.6, 3.2.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, even including gdb or git bisection work if 
needed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1183] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: Device [196e:1000]
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  JockeyStatus:
   xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Disabled, Not in use)
   xorg:nvidia_experimental_304 - NVIDIA accelerated graphics driver 
(**experimental** beta) (Proprietary, Disabled, Not in use)
   xorg:nvidia_experimental_310 - NVIDIA accelerated graphics driver 
(**experimental** beta) (Proprietary, Enabled, In use)
  MachineType: BIOSTAR Group TP55
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-38-generic 
root=UUID=fd58abb9-56f2-4094-8191-d931dea02669 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: None
  dmi.board.name: TP55
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd06/02/2010:svnBIOSTARGroup:pnTP55:pvr6.0:rvnBIOSTARGroup:rnTP55:rvr:cvnBIOSTARGroup:ct3:cvr6.0:
  dmi.product.name: TP55
  dmi.product.version: 6.0
  dmi.sys.vendor: BIOSTAR Group
  version.compiz: compiz 1:0.9.7.12-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.39-0ubuntu0.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.11
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: 

[Desktop-packages] [Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window

[Dave Chiluk]

** Package changed: xorg-server (Ubuntu) = linux-meta (Ubuntu)

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

Title:
  SB Arena USB headset causes X BUG, can't click outside window

Status in “linux-meta” package in Ubuntu:
  In Progress
Status in “linux-meta” source package in Precise:
  In Progress
Status in “linux-meta” source package in Quantal:
  In Progress

Bug description:
  When I plug my SB Arena USB headset in, I can't click the mouse in any
  window besides the one with focus. The current window works ok, but
  any other doesn't register the click. Also, I get a BUG in the X logs.

  This on Precise, xserver-xorg-input-evdev  version 1:2.7.0-0ubuntu1

  /var/log/Xorg.0.log:
  on device insert:
  [252903.181] (II) config/udev: Adding input device Creative Technology SB 
Arena Headset (/dev/input/event9)
  [252903.181] (**) Creative Technology SB Arena Headset: Applying InputClass 
evdev keyboard catchall
  [252903.181] (II) Using input driver 'evdev' for 'Creative Technology SB 
Arena Headset'
  [252903.181] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
  [252903.181] (**) Creative Technology SB Arena Headset: always reports core 
events
  [252903.181] (**) evdev: Creative Technology SB Arena Headset: Device: 
/dev/input/event9
  [252903.181] (--) evdev: Creative Technology SB Arena Headset: Vendor 0x41e 
Product 0x403
  [252903.181] (--) evdev: Creative Technology SB Arena Headset: Found 8 mouse 
buttons
  [252903.181] (--) evdev: Creative Technology SB Arena Headset: Found keys
  [252903.181] (II) evdev: Creative Technology SB Arena Headset: Configuring as 
mouse
  [252903.181] (II) evdev: Creative Technology SB Arena Headset: Configuring as 
keyboard
  [252903.181] (**) evdev: Creative Technology SB Arena Headset: YAxisMapping: 
buttons 4 and 5
  [252903.181] (**) evdev: Creative Technology SB Arena Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [252903.181] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1a.1/usb4/4-1/4-1:1.3/input/input18/event9
  [252903.181] (II) XINPUT: Adding extended input device Creative Technology 
SB Arena Headset (type: KEYBOARD, id 15)
  [252903.181] (**) Option xkb_rules evdev
  [252903.181] (**) Option xkb_model pc105
  [252903.181] (**) Option xkb_layout us
  [252903.191] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes  
2)'
  BUG: ../../dix/getevents.c:850 in scale_to_desktop()
  [252903.191] 
  Backtrace:
  [252903.192] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f148e6f3866]
  [252903.192] 1: /usr/bin/X (0x7f148e56b000+0x621fe) [0x7f148e5cd1fe]
  [252903.192] 2: /usr/bin/X (0x7f148e56b000+0x62e6d) [0x7f148e5cde6d]
  [252903.192] 3: /usr/bin/X (GetPointerEvents+0xe2) [0x7f148e5cf202]
  [252903.192] 4: /usr/bin/X (QueuePointerEvents+0x1d) [0x7f148e5cf65d]
  [252903.192] 5: /usr/bin/X (xf86PostButtonEvent+0xdd) [0x7f148e60b5ed]
  [252903.192] 6: /usr/lib/xorg/modules/input/evdev_drv.so 
(0x7f1486989000+0x5f48) [0x7f148698ef48]
  [252903.192] 7: /usr/bin/X (0x7f148e56b000+0x8ae07) [0x7f148e5f5e07]
  [252903.192] 8: /usr/bin/X (0x7f148e56b000+0xb0d4a) [0x7f148e61bd4a]
  [252903.192] 9: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f148d891000+0xfcb0) 
[0x7f148d8a0cb0]
  [252903.192] 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) 
[0x7f148c7f0803]
  [252903.192] 11: /usr/bin/X (WaitForSomething+0x19b) [0x7f148e6f0c4b]
  [252903.192] 12: /usr/bin/X (0x7f148e56b000+0x4e4f2) [0x7f148e5b94f2]
  [252903.192] 13: /usr/bin/X (0x7f148e56b000+0x3d6aa) [0x7f148e5a86aa]
  [252903.192] 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) 
[0x7f148c72676d]
  [252903.192] 15: /usr/bin/X (0x7f148e56b000+0x3d99d) [0x7f148e5a899d]

  on removal:
  [252937.048] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes  
2)'
  BUG: ../../dix/getevents.c:850 in scale_to_desktop()
  [252937.048] 
  Backtrace:
  [252937.048] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f148e6f3866]
  [252937.048] 1: /usr/bin/X (0x7f148e56b000+0x621fe) [0x7f148e5cd1fe]
  [252937.048] 2: /usr/bin/X (0x7f148e56b000+0x62e6d) [0x7f148e5cde6d]
  [252937.048] 3: /usr/bin/X (GetPointerEvents+0xe2) [0x7f148e5cf202]
  [252937.048] 4: /usr/bin/X (QueuePointerEvents+0x1d) [0x7f148e5cf65d]
  [252937.048] 5: /usr/bin/X (xf86PostButtonEvent+0xdd) [0x7f148e60b5ed]
  [252937.048] 6: /usr/lib/xorg/modules/input/evdev_drv.so 
(0x7f1486989000+0x5f48) [0x7f148698ef48]
  [252937.048] 7: /usr/bin/X (0x7f148e56b000+0x8ae07) [0x7f148e5f5e07]
  [252937.048] 8: /usr/bin/X (0x7f148e56b000+0xb0d4a) [0x7f148e61bd4a]
  [252937.048] 9: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f148d891000+0xfcb0) 
[0x7f148d8a0cb0]
  [252937.048] 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) 
[0x7f148c7f0803]
  [252937.048] 11: /usr/bin/X (WaitForSomething+0x19b) [0x7f148e6f0c4b]
  [252937.049] 12: /usr/bin/X (0x7f148e56b000+0x4e4f2) [0x7f148e5b94f2]
  

[Desktop-packages] [Bug 1080882] Re: Creative HS-950 USB headset causes X BUG, can't click outside window

[Dave Chiluk]

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

** This bug has been marked a duplicate of bug 1007575
   SB Arena USB headset causes X BUG, can't click outside window

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

Title:
  Creative HS-950 USB headset causes X BUG, can't click outside window

Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  Bug is similar to this one: https://bugs.launchpad.net/ubuntu/+source
  /xorg-server/+bug/1007575

  Pulseaudio usually crashes on login (if the headset is plugged) or
  when a sound is played. The only way to be able to click outside the
  active window is to unplug the headset.

  /var/log/Xorg.0.log:

  
  [34.792] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [34.792] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [34.792] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [34.792] (**) Creative Technology Creative USB Headset: always reports 
core events
  [34.792] (**) evdev: Creative Technology Creative USB Headset: Device: 
/dev/input/event6
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Vendor 
0x41e Product 0x400
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Found 8 
mouse buttons
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Found keys
  [34.792] (II) evdev: Creative Technology Creative USB Headset: Forcing 
relative x/y axes to exist.
  [34.792] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as mouse
  [34.792] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as keyboard
  [34.792] (**) evdev: Creative Technology Creative USB Headset: 
YAxisMapping: buttons 4 and 5
  [34.792] (**) evdev: Creative Technology Creative USB Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [34.792] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input14/event6
  [34.793] (II) XINPUT: Adding extended input device Creative Technology 
Creative USB Headset (type: KEYBOARD, id 11)
  [34.793] (**) Option xkb_rules evdev
  [34.793] (**) Option xkb_model pc105
  [34.793] (**) Option xkb_layout pt
  [35.200] (II) config/udev: removing device Creative Technology Creative 
USB Headset
  [35.204] (II) evdev: Creative Technology Creative USB Headset: Close
  [35.204] (II) UnloadModule: evdev
  [35.552] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [35.552] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [35.552] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [35.552] (**) Creative Technology Creative USB Headset: always reports 
core events
  [35.552] (**) evdev: Creative Technology Creative USB Headset: Device: 
/dev/input/event6
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Vendor 
0x41e Product 0x400
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Found 8 
mouse buttons
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Found keys
  [35.552] (II) evdev: Creative Technology Creative USB Headset: Forcing 
relative x/y axes to exist.
  [35.552] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as mouse
  [35.552] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as keyboard
  [35.552] (**) evdev: Creative Technology Creative USB Headset: 
YAxisMapping: buttons 4 and 5
  [35.552] (**) evdev: Creative Technology Creative USB Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [35.552] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input15/event6
  [35.552] (II) XINPUT: Adding extended input device Creative Technology 
Creative USB Headset (type: KEYBOARD, id 11)
  [35.552] (**) Option xkb_rules evdev
  [35.552] (**) Option xkb_model pc105
  [35.552] (**) Option xkb_layout pt
  [  2988.170] (II) config/udev: removing device Creative Technology Creative 
USB Headset
  [  2988.172] (II) evdev: Creative Technology Creative USB Headset: Close
  [  2988.172] (II) UnloadModule: evdev
  [  2989.779] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [  2989.779] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [  2989.779] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [  2989.779] (**) Creative Technology Creative USB 

[Desktop-packages] [Bug 1080882] Re: Creative HS-950 USB headset causes X BUG, can't click outside window

[Dave Chiluk]

Fantastic, I'll push to the community maintainers, and hopefully it'll
get pulled in soon.

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

Title:
  Creative HS-950 USB headset causes X BUG, can't click outside window

Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  Bug is similar to this one: https://bugs.launchpad.net/ubuntu/+source
  /xorg-server/+bug/1007575

  Pulseaudio usually crashes on login (if the headset is plugged) or
  when a sound is played. The only way to be able to click outside the
  active window is to unplug the headset.

  /var/log/Xorg.0.log:

  
  [34.792] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [34.792] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [34.792] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [34.792] (**) Creative Technology Creative USB Headset: always reports 
core events
  [34.792] (**) evdev: Creative Technology Creative USB Headset: Device: 
/dev/input/event6
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Vendor 
0x41e Product 0x400
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Found 8 
mouse buttons
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Found keys
  [34.792] (II) evdev: Creative Technology Creative USB Headset: Forcing 
relative x/y axes to exist.
  [34.792] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as mouse
  [34.792] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as keyboard
  [34.792] (**) evdev: Creative Technology Creative USB Headset: 
YAxisMapping: buttons 4 and 5
  [34.792] (**) evdev: Creative Technology Creative USB Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [34.792] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input14/event6
  [34.793] (II) XINPUT: Adding extended input device Creative Technology 
Creative USB Headset (type: KEYBOARD, id 11)
  [34.793] (**) Option xkb_rules evdev
  [34.793] (**) Option xkb_model pc105
  [34.793] (**) Option xkb_layout pt
  [35.200] (II) config/udev: removing device Creative Technology Creative 
USB Headset
  [35.204] (II) evdev: Creative Technology Creative USB Headset: Close
  [35.204] (II) UnloadModule: evdev
  [35.552] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [35.552] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [35.552] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [35.552] (**) Creative Technology Creative USB Headset: always reports 
core events
  [35.552] (**) evdev: Creative Technology Creative USB Headset: Device: 
/dev/input/event6
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Vendor 
0x41e Product 0x400
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Found 8 
mouse buttons
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Found keys
  [35.552] (II) evdev: Creative Technology Creative USB Headset: Forcing 
relative x/y axes to exist.
  [35.552] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as mouse
  [35.552] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as keyboard
  [35.552] (**) evdev: Creative Technology Creative USB Headset: 
YAxisMapping: buttons 4 and 5
  [35.552] (**) evdev: Creative Technology Creative USB Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [35.552] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input15/event6
  [35.552] (II) XINPUT: Adding extended input device Creative Technology 
Creative USB Headset (type: KEYBOARD, id 11)
  [35.552] (**) Option xkb_rules evdev
  [35.552] (**) Option xkb_model pc105
  [35.552] (**) Option xkb_layout pt
  [  2988.170] (II) config/udev: removing device Creative Technology Creative 
USB Headset
  [  2988.172] (II) evdev: Creative Technology Creative USB Headset: Close
  [  2988.172] (II) UnloadModule: evdev
  [  2989.779] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [  2989.779] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [  2989.779] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [  2989.779] (**) Creative Technology Creative USB Headset: always reports 
core events
  [  2989.779] (**) evdev: Creative Technology Creative USB Headset: Device: 

[Desktop-packages] [Bug 1080882] Re: Creative HS-950 USB headset causes X BUG, can't click outside window

[Dave Chiluk]

Unplugging and replugging has been known to cause issue.  Additionally
holding volume up/down keys, also might cause issues.

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

Title:
  Creative HS-950 USB headset causes X BUG, can't click outside window

Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  Bug is similar to this one: https://bugs.launchpad.net/ubuntu/+source
  /xorg-server/+bug/1007575

  Pulseaudio usually crashes on login (if the headset is plugged) or
  when a sound is played. The only way to be able to click outside the
  active window is to unplug the headset.

  /var/log/Xorg.0.log:

  
  [34.792] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [34.792] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [34.792] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [34.792] (**) Creative Technology Creative USB Headset: always reports 
core events
  [34.792] (**) evdev: Creative Technology Creative USB Headset: Device: 
/dev/input/event6
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Vendor 
0x41e Product 0x400
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Found 8 
mouse buttons
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Found keys
  [34.792] (II) evdev: Creative Technology Creative USB Headset: Forcing 
relative x/y axes to exist.
  [34.792] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as mouse
  [34.792] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as keyboard
  [34.792] (**) evdev: Creative Technology Creative USB Headset: 
YAxisMapping: buttons 4 and 5
  [34.792] (**) evdev: Creative Technology Creative USB Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [34.792] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input14/event6
  [34.793] (II) XINPUT: Adding extended input device Creative Technology 
Creative USB Headset (type: KEYBOARD, id 11)
  [34.793] (**) Option xkb_rules evdev
  [34.793] (**) Option xkb_model pc105
  [34.793] (**) Option xkb_layout pt
  [35.200] (II) config/udev: removing device Creative Technology Creative 
USB Headset
  [35.204] (II) evdev: Creative Technology Creative USB Headset: Close
  [35.204] (II) UnloadModule: evdev
  [35.552] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [35.552] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [35.552] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [35.552] (**) Creative Technology Creative USB Headset: always reports 
core events
  [35.552] (**) evdev: Creative Technology Creative USB Headset: Device: 
/dev/input/event6
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Vendor 
0x41e Product 0x400
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Found 8 
mouse buttons
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Found keys
  [35.552] (II) evdev: Creative Technology Creative USB Headset: Forcing 
relative x/y axes to exist.
  [35.552] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as mouse
  [35.552] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as keyboard
  [35.552] (**) evdev: Creative Technology Creative USB Headset: 
YAxisMapping: buttons 4 and 5
  [35.552] (**) evdev: Creative Technology Creative USB Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [35.552] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input15/event6
  [35.552] (II) XINPUT: Adding extended input device Creative Technology 
Creative USB Headset (type: KEYBOARD, id 11)
  [35.552] (**) Option xkb_rules evdev
  [35.552] (**) Option xkb_model pc105
  [35.552] (**) Option xkb_layout pt
  [  2988.170] (II) config/udev: removing device Creative Technology Creative 
USB Headset
  [  2988.172] (II) evdev: Creative Technology Creative USB Headset: Close
  [  2988.172] (II) UnloadModule: evdev
  [  2989.779] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [  2989.779] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [  2989.779] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [  2989.779] (**) Creative Technology Creative USB Headset: always reports 
core events
  [  2989.779] (**) evdev: Creative Technology 

[Desktop-packages] [Bug 1080882] Re: Creative HS-950 USB headset causes X BUG, can't click outside window

[Dave Chiluk]

The test kernel is meant to specifically address the unable to click
outside window bug, but it may have the side benefit of fixing other
parts as well.

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

Title:
  Creative HS-950 USB headset causes X BUG, can't click outside window

Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  Bug is similar to this one: https://bugs.launchpad.net/ubuntu/+source
  /xorg-server/+bug/1007575

  Pulseaudio usually crashes on login (if the headset is plugged) or
  when a sound is played. The only way to be able to click outside the
  active window is to unplug the headset.

  /var/log/Xorg.0.log:

  
  [34.792] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [34.792] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [34.792] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [34.792] (**) Creative Technology Creative USB Headset: always reports 
core events
  [34.792] (**) evdev: Creative Technology Creative USB Headset: Device: 
/dev/input/event6
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Vendor 
0x41e Product 0x400
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Found 8 
mouse buttons
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Found keys
  [34.792] (II) evdev: Creative Technology Creative USB Headset: Forcing 
relative x/y axes to exist.
  [34.792] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as mouse
  [34.792] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as keyboard
  [34.792] (**) evdev: Creative Technology Creative USB Headset: 
YAxisMapping: buttons 4 and 5
  [34.792] (**) evdev: Creative Technology Creative USB Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [34.792] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input14/event6
  [34.793] (II) XINPUT: Adding extended input device Creative Technology 
Creative USB Headset (type: KEYBOARD, id 11)
  [34.793] (**) Option xkb_rules evdev
  [34.793] (**) Option xkb_model pc105
  [34.793] (**) Option xkb_layout pt
  [35.200] (II) config/udev: removing device Creative Technology Creative 
USB Headset
  [35.204] (II) evdev: Creative Technology Creative USB Headset: Close
  [35.204] (II) UnloadModule: evdev
  [35.552] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [35.552] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [35.552] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [35.552] (**) Creative Technology Creative USB Headset: always reports 
core events
  [35.552] (**) evdev: Creative Technology Creative USB Headset: Device: 
/dev/input/event6
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Vendor 
0x41e Product 0x400
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Found 8 
mouse buttons
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Found keys
  [35.552] (II) evdev: Creative Technology Creative USB Headset: Forcing 
relative x/y axes to exist.
  [35.552] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as mouse
  [35.552] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as keyboard
  [35.552] (**) evdev: Creative Technology Creative USB Headset: 
YAxisMapping: buttons 4 and 5
  [35.552] (**) evdev: Creative Technology Creative USB Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [35.552] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input15/event6
  [35.552] (II) XINPUT: Adding extended input device Creative Technology 
Creative USB Headset (type: KEYBOARD, id 11)
  [35.552] (**) Option xkb_rules evdev
  [35.552] (**) Option xkb_model pc105
  [35.552] (**) Option xkb_layout pt
  [  2988.170] (II) config/udev: removing device Creative Technology Creative 
USB Headset
  [  2988.172] (II) evdev: Creative Technology Creative USB Headset: Close
  [  2988.172] (II) UnloadModule: evdev
  [  2989.779] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [  2989.779] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [  2989.779] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [  2989.779] (**) Creative Technology Creative USB Headset: always reports 
core events
  [  2989.779] (**) 

[Desktop-packages] [Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window

[Dave Chiluk]

** Changed in: xorg-server (Ubuntu)
 Assignee: Chris J Arges (arges) = Dave Chiluk (chiluk)

** Changed in: xorg-server (Ubuntu Quantal)
 Assignee: Chris J Arges (arges) = Dave Chiluk (chiluk)

** Changed in: xorg-server (Ubuntu Precise)
 Assignee: Chris J Arges (arges) = Dave Chiluk (chiluk)

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

Title:
  SB Arena USB headset causes X BUG, can't click outside window

Status in “xorg-server” package in Ubuntu:
  In Progress
Status in “xorg-server” source package in Precise:
  In Progress
Status in “xorg-server” source package in Quantal:
  In Progress

Bug description:
  When I plug my SB Arena USB headset in, I can't click the mouse in any
  window besides the one with focus. The current window works ok, but
  any other doesn't register the click. Also, I get a BUG in the X logs.

  This on Precise, xserver-xorg-input-evdev  version 1:2.7.0-0ubuntu1

  /var/log/Xorg.0.log:
  on device insert:
  [252903.181] (II) config/udev: Adding input device Creative Technology SB 
Arena Headset (/dev/input/event9)
  [252903.181] (**) Creative Technology SB Arena Headset: Applying InputClass 
evdev keyboard catchall
  [252903.181] (II) Using input driver 'evdev' for 'Creative Technology SB 
Arena Headset'
  [252903.181] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
  [252903.181] (**) Creative Technology SB Arena Headset: always reports core 
events
  [252903.181] (**) evdev: Creative Technology SB Arena Headset: Device: 
/dev/input/event9
  [252903.181] (--) evdev: Creative Technology SB Arena Headset: Vendor 0x41e 
Product 0x403
  [252903.181] (--) evdev: Creative Technology SB Arena Headset: Found 8 mouse 
buttons
  [252903.181] (--) evdev: Creative Technology SB Arena Headset: Found keys
  [252903.181] (II) evdev: Creative Technology SB Arena Headset: Configuring as 
mouse
  [252903.181] (II) evdev: Creative Technology SB Arena Headset: Configuring as 
keyboard
  [252903.181] (**) evdev: Creative Technology SB Arena Headset: YAxisMapping: 
buttons 4 and 5
  [252903.181] (**) evdev: Creative Technology SB Arena Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [252903.181] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1a.1/usb4/4-1/4-1:1.3/input/input18/event9
  [252903.181] (II) XINPUT: Adding extended input device Creative Technology 
SB Arena Headset (type: KEYBOARD, id 15)
  [252903.181] (**) Option xkb_rules evdev
  [252903.181] (**) Option xkb_model pc105
  [252903.181] (**) Option xkb_layout us
  [252903.191] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes  
2)'
  BUG: ../../dix/getevents.c:850 in scale_to_desktop()
  [252903.191] 
  Backtrace:
  [252903.192] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f148e6f3866]
  [252903.192] 1: /usr/bin/X (0x7f148e56b000+0x621fe) [0x7f148e5cd1fe]
  [252903.192] 2: /usr/bin/X (0x7f148e56b000+0x62e6d) [0x7f148e5cde6d]
  [252903.192] 3: /usr/bin/X (GetPointerEvents+0xe2) [0x7f148e5cf202]
  [252903.192] 4: /usr/bin/X (QueuePointerEvents+0x1d) [0x7f148e5cf65d]
  [252903.192] 5: /usr/bin/X (xf86PostButtonEvent+0xdd) [0x7f148e60b5ed]
  [252903.192] 6: /usr/lib/xorg/modules/input/evdev_drv.so 
(0x7f1486989000+0x5f48) [0x7f148698ef48]
  [252903.192] 7: /usr/bin/X (0x7f148e56b000+0x8ae07) [0x7f148e5f5e07]
  [252903.192] 8: /usr/bin/X (0x7f148e56b000+0xb0d4a) [0x7f148e61bd4a]
  [252903.192] 9: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f148d891000+0xfcb0) 
[0x7f148d8a0cb0]
  [252903.192] 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) 
[0x7f148c7f0803]
  [252903.192] 11: /usr/bin/X (WaitForSomething+0x19b) [0x7f148e6f0c4b]
  [252903.192] 12: /usr/bin/X (0x7f148e56b000+0x4e4f2) [0x7f148e5b94f2]
  [252903.192] 13: /usr/bin/X (0x7f148e56b000+0x3d6aa) [0x7f148e5a86aa]
  [252903.192] 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) 
[0x7f148c72676d]
  [252903.192] 15: /usr/bin/X (0x7f148e56b000+0x3d99d) [0x7f148e5a899d]

  on removal:
  [252937.048] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes  
2)'
  BUG: ../../dix/getevents.c:850 in scale_to_desktop()
  [252937.048] 
  Backtrace:
  [252937.048] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f148e6f3866]
  [252937.048] 1: /usr/bin/X (0x7f148e56b000+0x621fe) [0x7f148e5cd1fe]
  [252937.048] 2: /usr/bin/X (0x7f148e56b000+0x62e6d) [0x7f148e5cde6d]
  [252937.048] 3: /usr/bin/X (GetPointerEvents+0xe2) [0x7f148e5cf202]
  [252937.048] 4: /usr/bin/X (QueuePointerEvents+0x1d) [0x7f148e5cf65d]
  [252937.048] 5: /usr/bin/X (xf86PostButtonEvent+0xdd) [0x7f148e60b5ed]
  [252937.048] 6: /usr/lib/xorg/modules/input/evdev_drv.so 
(0x7f1486989000+0x5f48) [0x7f148698ef48]
  [252937.048] 7: /usr/bin/X (0x7f148e56b000+0x8ae07) [0x7f148e5f5e07]
  [252937.048] 8: /usr/bin/X (0x7f148e56b000+0xb0d4a) [0x7f148e61bd4a]
  [252937.048] 9: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f148d891000+0xfcb0

[Desktop-packages] [Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window

[Dave Chiluk]

I bisected this issue down to being fixed by this commit.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=929578ab

I have uploaded kernels for precise and quantal here.
http://people.canonical.com/~chiluk/lp1007575/

Please verify with these kernels and report back.  Make sure you select
these kernels from grub when booting *(they may under the previous
kernels, or advanced options).

Also if you are running proprietary video card drivers make sure you
install the headers _all.deb and arch.deb files as well.

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

Title:
  SB Arena USB headset causes X BUG, can't click outside window

Status in “xorg-server” package in Ubuntu:
  In Progress
Status in “xorg-server” source package in Precise:
  In Progress
Status in “xorg-server” source package in Quantal:
  In Progress

Bug description:
  When I plug my SB Arena USB headset in, I can't click the mouse in any
  window besides the one with focus. The current window works ok, but
  any other doesn't register the click. Also, I get a BUG in the X logs.

  This on Precise, xserver-xorg-input-evdev  version 1:2.7.0-0ubuntu1

  /var/log/Xorg.0.log:
  on device insert:
  [252903.181] (II) config/udev: Adding input device Creative Technology SB 
Arena Headset (/dev/input/event9)
  [252903.181] (**) Creative Technology SB Arena Headset: Applying InputClass 
evdev keyboard catchall
  [252903.181] (II) Using input driver 'evdev' for 'Creative Technology SB 
Arena Headset'
  [252903.181] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
  [252903.181] (**) Creative Technology SB Arena Headset: always reports core 
events
  [252903.181] (**) evdev: Creative Technology SB Arena Headset: Device: 
/dev/input/event9
  [252903.181] (--) evdev: Creative Technology SB Arena Headset: Vendor 0x41e 
Product 0x403
  [252903.181] (--) evdev: Creative Technology SB Arena Headset: Found 8 mouse 
buttons
  [252903.181] (--) evdev: Creative Technology SB Arena Headset: Found keys
  [252903.181] (II) evdev: Creative Technology SB Arena Headset: Configuring as 
mouse
  [252903.181] (II) evdev: Creative Technology SB Arena Headset: Configuring as 
keyboard
  [252903.181] (**) evdev: Creative Technology SB Arena Headset: YAxisMapping: 
buttons 4 and 5
  [252903.181] (**) evdev: Creative Technology SB Arena Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [252903.181] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1a.1/usb4/4-1/4-1:1.3/input/input18/event9
  [252903.181] (II) XINPUT: Adding extended input device Creative Technology 
SB Arena Headset (type: KEYBOARD, id 15)
  [252903.181] (**) Option xkb_rules evdev
  [252903.181] (**) Option xkb_model pc105
  [252903.181] (**) Option xkb_layout us
  [252903.191] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes  
2)'
  BUG: ../../dix/getevents.c:850 in scale_to_desktop()
  [252903.191] 
  Backtrace:
  [252903.192] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f148e6f3866]
  [252903.192] 1: /usr/bin/X (0x7f148e56b000+0x621fe) [0x7f148e5cd1fe]
  [252903.192] 2: /usr/bin/X (0x7f148e56b000+0x62e6d) [0x7f148e5cde6d]
  [252903.192] 3: /usr/bin/X (GetPointerEvents+0xe2) [0x7f148e5cf202]
  [252903.192] 4: /usr/bin/X (QueuePointerEvents+0x1d) [0x7f148e5cf65d]
  [252903.192] 5: /usr/bin/X (xf86PostButtonEvent+0xdd) [0x7f148e60b5ed]
  [252903.192] 6: /usr/lib/xorg/modules/input/evdev_drv.so 
(0x7f1486989000+0x5f48) [0x7f148698ef48]
  [252903.192] 7: /usr/bin/X (0x7f148e56b000+0x8ae07) [0x7f148e5f5e07]
  [252903.192] 8: /usr/bin/X (0x7f148e56b000+0xb0d4a) [0x7f148e61bd4a]
  [252903.192] 9: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f148d891000+0xfcb0) 
[0x7f148d8a0cb0]
  [252903.192] 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) 
[0x7f148c7f0803]
  [252903.192] 11: /usr/bin/X (WaitForSomething+0x19b) [0x7f148e6f0c4b]
  [252903.192] 12: /usr/bin/X (0x7f148e56b000+0x4e4f2) [0x7f148e5b94f2]
  [252903.192] 13: /usr/bin/X (0x7f148e56b000+0x3d6aa) [0x7f148e5a86aa]
  [252903.192] 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) 
[0x7f148c72676d]
  [252903.192] 15: /usr/bin/X (0x7f148e56b000+0x3d99d) [0x7f148e5a899d]

  on removal:
  [252937.048] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes  
2)'
  BUG: ../../dix/getevents.c:850 in scale_to_desktop()
  [252937.048] 
  Backtrace:
  [252937.048] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f148e6f3866]
  [252937.048] 1: /usr/bin/X (0x7f148e56b000+0x621fe) [0x7f148e5cd1fe]
  [252937.048] 2: /usr/bin/X (0x7f148e56b000+0x62e6d) [0x7f148e5cde6d]
  [252937.048] 3: /usr/bin/X (GetPointerEvents+0xe2) [0x7f148e5cf202]
  [252937.048] 4: /usr/bin/X (QueuePointerEvents+0x1d) [0x7f148e5cf65d]
  [252937.048] 5: /usr/bin/X (xf86PostButtonEvent+0xdd) [0x7f148e60b5ed]
  [252937.048] 6: /usr/lib/xorg/modules/input/evdev_drv.so 
(0x7f1486989000+0x5f48) 

[Desktop-packages] [Bug 993655] Re: Unity looses mouse click handler when using enabling USB headset

[Dave Chiluk]

Please re-verify with the kernel mentioned here

https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1007575/comments/34

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) = Dave Chiluk (chiluk)

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

Title:
  Unity looses mouse click handler when using enabling USB headset

Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  I have a Plantronics D100 headset.

  When I press the button on the headset to enable it, Unity looses its
  click handler, in that it can not click and drag windows.

  The cursor is visible and moves just fine. I can switch applications
  using Alt+Tab, and I can launch new applications using the keyboard.
  But I cannot close the existing window, or change focus to another
  window by using the mouse.

  The Headset microphone and speaker work just fine!

  Tested this on a laptop and desktop machine. Both running Ubuntu
  12.04.

  The headset I'm using is a Plantronics D100 unit.

  I have had this problem for the past month while on the 12.04 beta release. 
  --- 
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  NonfreeKernelModules: nvidia
  Package: unity 5.10.0-0ubuntu6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Tags:  precise
  Uname: Linux 3.2.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/993655/+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 1080882] Re: Creative HS-950 USB headset causes X BUG, can't click outside window

[Dave Chiluk]

Please re-verify with this kernel mentioned here

https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1007575/comments/34


** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) = Dave Chiluk (chiluk)

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

Title:
  Creative HS-950 USB headset causes X BUG, can't click outside window

Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  Bug is similar to this one: https://bugs.launchpad.net/ubuntu/+source
  /xorg-server/+bug/1007575

  Pulseaudio usually crashes on login (if the headset is plugged) or
  when a sound is played. The only way to be able to click outside the
  active window is to unplug the headset.

  /var/log/Xorg.0.log:

  
  [34.792] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [34.792] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [34.792] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [34.792] (**) Creative Technology Creative USB Headset: always reports 
core events
  [34.792] (**) evdev: Creative Technology Creative USB Headset: Device: 
/dev/input/event6
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Vendor 
0x41e Product 0x400
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Found 8 
mouse buttons
  [34.792] (--) evdev: Creative Technology Creative USB Headset: Found keys
  [34.792] (II) evdev: Creative Technology Creative USB Headset: Forcing 
relative x/y axes to exist.
  [34.792] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as mouse
  [34.792] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as keyboard
  [34.792] (**) evdev: Creative Technology Creative USB Headset: 
YAxisMapping: buttons 4 and 5
  [34.792] (**) evdev: Creative Technology Creative USB Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [34.792] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input14/event6
  [34.793] (II) XINPUT: Adding extended input device Creative Technology 
Creative USB Headset (type: KEYBOARD, id 11)
  [34.793] (**) Option xkb_rules evdev
  [34.793] (**) Option xkb_model pc105
  [34.793] (**) Option xkb_layout pt
  [35.200] (II) config/udev: removing device Creative Technology Creative 
USB Headset
  [35.204] (II) evdev: Creative Technology Creative USB Headset: Close
  [35.204] (II) UnloadModule: evdev
  [35.552] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [35.552] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [35.552] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [35.552] (**) Creative Technology Creative USB Headset: always reports 
core events
  [35.552] (**) evdev: Creative Technology Creative USB Headset: Device: 
/dev/input/event6
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Vendor 
0x41e Product 0x400
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Found 8 
mouse buttons
  [35.552] (--) evdev: Creative Technology Creative USB Headset: Found keys
  [35.552] (II) evdev: Creative Technology Creative USB Headset: Forcing 
relative x/y axes to exist.
  [35.552] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as mouse
  [35.552] (II) evdev: Creative Technology Creative USB Headset: 
Configuring as keyboard
  [35.552] (**) evdev: Creative Technology Creative USB Headset: 
YAxisMapping: buttons 4 and 5
  [35.552] (**) evdev: Creative Technology Creative USB Headset: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [35.552] (**) Option config_info 
udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input15/event6
  [35.552] (II) XINPUT: Adding extended input device Creative Technology 
Creative USB Headset (type: KEYBOARD, id 11)
  [35.552] (**) Option xkb_rules evdev
  [35.552] (**) Option xkb_model pc105
  [35.552] (**) Option xkb_layout pt
  [  2988.170] (II) config/udev: removing device Creative Technology Creative 
USB Headset
  [  2988.172] (II) evdev: Creative Technology Creative USB Headset: Close
  [  2988.172] (II) UnloadModule: evdev
  [  2989.779] (II) config/udev: Adding input device Creative Technology 
Creative USB Headset (/dev/input/event6)
  [  2989.779] (**) Creative Technology Creative USB Headset: Applying 
InputClass evdev keyboard catchall
  [  2989.779] (II) Using input driver 'evdev' for 'Creative Technology 
Creative USB Headset'
  [  2989.779] (**) Creative Technology