[Desktop-packages] [Bug 2056500] Re: missing words in /usr/share/dict/words

[Luke Schierer]

it looks like I needed to install wamerican-insane then run  sudo
select-default-wordlist

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

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

Title:
  missing words in /usr/share/dict/words

Status in scowl package in Ubuntu:
  Invalid

Bug description:
  ```
  luke@opus91:~$ dpkg -S /usr/share/dict/words 
  wamerican: /usr/share/dict/words
  luke@opus91:~$ 

  luke@opus91:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  Codename:   jammy
  luke@opus91:~$ 
  ```


  ```grep tuck /usr/share/dict/words ``` shows that the following words 
(minimally) are missing:
  ```
  tuckahoe
  tuckahoe
  tuckshops
  untuck
  untucked
  untucks
  untucking
  tuckerization
  tuckedly
  stuckism
  ```

  all of which show up on https://www.thefreedictionary.com/words-
  containing-tuck and some of which are used in the NY Times spelling
  bee game.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wamerican 2020.12.07-2
  ProcVersionSignature: Ubuntu 6.2.0-1017.17~22.04.1-aws 6.2.16
  Uname: Linux 6.2.0-1017-aws x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: aws
  CloudName: aws
  CloudPlatform: ec2
  CloudRegion: us-east-1
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Thu Mar  7 22:21:42 2024
  Ec2AMI: ami-0c7217cdde317cfec
  Ec2AMIManifest: (unknown)
  Ec2Architecture: x86_64
  Ec2AvailabilityZone: us-east-1a
  Ec2Imageid: ami-0c7217cdde317cfec
  Ec2InstanceType: t3.medium
  Ec2Instancetype: t3.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Ec2Region: us-east-1
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: scowl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/scowl/+bug/2056500/+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 2056500] [NEW] missing words in /usr/share/dict/words

[Luke Schierer]

Public bug reported:

```
luke@opus91:~$ dpkg -S /usr/share/dict/words 
wamerican: /usr/share/dict/words
luke@opus91:~$ 

luke@opus91:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.3 LTS
Release:22.04
Codename:   jammy
luke@opus91:~$ 
```


```grep tuck /usr/share/dict/words ``` shows that the following words 
(minimally) are missing:
```
tuckahoe
tuckahoe
tuckshops
untuck
untucked
untucks
untucking
tuckerization
tuckedly
stuckism
```

all of which show up on https://www.thefreedictionary.com/words-
containing-tuck and some of which are used in the NY Times spelling bee
game.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: wamerican 2020.12.07-2
ProcVersionSignature: Ubuntu 6.2.0-1017.17~22.04.1-aws 6.2.16
Uname: Linux 6.2.0-1017-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: aws
CloudName: aws
CloudPlatform: ec2
CloudRegion: us-east-1
CloudSubPlatform: metadata (http://169.254.169.254)
Date: Thu Mar  7 22:21:42 2024
Ec2AMI: ami-0c7217cdde317cfec
Ec2AMIManifest: (unknown)
Ec2Architecture: x86_64
Ec2AvailabilityZone: us-east-1a
Ec2Imageid: ami-0c7217cdde317cfec
Ec2InstanceType: t3.medium
Ec2Instancetype: t3.medium
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Ec2Region: us-east-1
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: scowl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ec2-images jammy

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

Title:
  missing words in /usr/share/dict/words

Status in scowl package in Ubuntu:
  New

Bug description:
  ```
  luke@opus91:~$ dpkg -S /usr/share/dict/words 
  wamerican: /usr/share/dict/words
  luke@opus91:~$ 

  luke@opus91:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  Codename:   jammy
  luke@opus91:~$ 
  ```


  ```grep tuck /usr/share/dict/words ``` shows that the following words 
(minimally) are missing:
  ```
  tuckahoe
  tuckahoe
  tuckshops
  untuck
  untucked
  untucks
  untucking
  tuckerization
  tuckedly
  stuckism
  ```

  all of which show up on https://www.thefreedictionary.com/words-
  containing-tuck and some of which are used in the NY Times spelling
  bee game.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wamerican 2020.12.07-2
  ProcVersionSignature: Ubuntu 6.2.0-1017.17~22.04.1-aws 6.2.16
  Uname: Linux 6.2.0-1017-aws x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: aws
  CloudName: aws
  CloudPlatform: ec2
  CloudRegion: us-east-1
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Thu Mar  7 22:21:42 2024
  Ec2AMI: ami-0c7217cdde317cfec
  Ec2AMIManifest: (unknown)
  Ec2Architecture: x86_64
  Ec2AvailabilityZone: us-east-1a
  Ec2Imageid: ami-0c7217cdde317cfec
  Ec2InstanceType: t3.medium
  Ec2Instancetype: t3.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Ec2Region: us-east-1
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: scowl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/scowl/+bug/2056500/+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 2004552] Re: Sound doesn't work on ASUS X670E-E motherboard.

[Luke Ashe-Browne]

affects me too. 
DistroRelease: Ubuntu 22.10
Base Board Information
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG STRIX X670E-F GAMING WIFI
Version: Rev 1.xx

I suppose any x670E-...  range of boards, perhaps eve the hero will all
have this issue.

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

Title:
  Sound doesn't work on ASUS X670E-E motherboard.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  None of the outputs work for my digital optical output on my ASUS ROG
  STRIX X670E-E GAMING WIFI motherboard since updating the
  ALC4080/ALC4082 firmware.

  The issue is resolved in the upstream package of alsa-ucm-conf
  (https://github.com/alsa-project/alsa-ucm-conf). When I applied the
  newer configs sound started working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  2 06:08:15 2023
  InstallationDate: Installed on 2023-01-08 (24 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X670E-E GAMING WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/04/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2004552/+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 2022897] Re: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 failed to install/upgrade: podproces nowy pakiet chromium-browser skrypt pre-installation zwrócił kod błęd

[Luke Skywalker]

Hey!
Thanks for response! Issue occured probably because during upgrading i have 
lost an internet connection for a longer while. But now, after updating & 
upgrading, everything is ok.
Sorry for bothering with minor issues, but I'm newbie to Linux :)
May the force be with us all.

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

Title:
  package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 failed to
  install/upgrade: podproces nowy pakiet chromium-browser skrypt pre-
  installation zwrócił kod błędu 1

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  during : sudo apt upgrade i receive: Errors occured during proceeding: 
/var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jun  5 09:26:42 2023
  Dependencies:
   
  ErrorMessage: podproces nowy pakiet chromium-browser skrypt pre-installation 
zwrócił kod błędu 1
  InstallationDate: Installed on 2023-06-05 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: chromium-browser
  Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 failed to 
install/upgrade: podproces nowy pakiet chromium-browser skrypt pre-installation 
zwrócił kod błędu 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2022897/+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 2022897] [NEW] package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 failed to install/upgrade: podproces nowy pakiet chromium-browser skrypt pre-installation zwrócił kod bł

[Luke Skywalker]

Public bug reported:

during : sudo apt upgrade i receive: Errors occured during proceeding: 
/var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Jun  5 09:26:42 2023
Dependencies:
 
ErrorMessage: podproces nowy pakiet chromium-browser skrypt pre-installation 
zwrócił kod błędu 1
InstallationDate: Installed on 2023-06-05 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: chromium-browser
Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 failed to 
install/upgrade: podproces nowy pakiet chromium-browser skrypt pre-installation 
zwrócił kod błędu 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 failed to
  install/upgrade: podproces nowy pakiet chromium-browser skrypt pre-
  installation zwrócił kod błędu 1

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  during : sudo apt upgrade i receive: Errors occured during proceeding: 
/var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jun  5 09:26:42 2023
  Dependencies:
   
  ErrorMessage: podproces nowy pakiet chromium-browser skrypt pre-installation 
zwrócił kod błędu 1
  InstallationDate: Installed on 2023-06-05 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: chromium-browser
  Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.3 failed to 
install/upgrade: podproces nowy pakiet chromium-browser skrypt pre-installation 
zwrócił kod błędu 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2022897/+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 2020078] Re: firefox-snap causes system-wide freeze

[Luke Goshen]

I executed the command you provided, and it returns "No additional
information collected". I'll remember to run these commands next time
when I report a bug.

Is there anything else I can do?

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

Title:
  firefox-snap causes system-wide freeze

Status in firefox package in Ubuntu:
  New

Bug description:
  May 18 10:03:02 jonsmith kernel: [  290.566068] ACPI Error: Aborting method 
\_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566228] ACPI Error: Aborting method 
\EV5 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566389] ACPI Error: Aborting method 
\SMEE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566550] ACPI Error: Aborting method 
\SMIE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566708] ACPI Error: Aborting method 
\NEVT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566899] ACPI Error: Aborting method 
\_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.694431] ACPI BIOS Error (bug): Could 
not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND 
(20220331/psargs-330)
  May 18 10:03:02 jonsmith kernel: [  290.694455] 
  May 18 10:03:02 jonsmith kernel: [  290.694458] No Local Variables are 
initialized for Method [BRT6]
  May 18 10:03:02 jonsmith kernel: [  290.694460] 
  May 18 10:03:02 jonsmith kernel: [  290.694463] Initialized Arguments for 
Method [BRT6]:  (2 arguments defined for method invocation)
  May 18 10:03:02 jonsmith kernel: [  290.694465]   Arg0:   409b1dbf 
   Integer 0001
  May 18 10:03:02 jonsmith kernel: [  290.694477]   Arg1:   ad7ffa02 
   Integer 
  May 18 10:03:02 jonsmith kernel: [  290.694486] 
  May 18 10:03:02 jonsmith kernel: [  290.694490] ACPI Error: Aborting method 
\_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.694650] ACPI Error: Aborting method 
\EV5 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.694810] ACPI Error: Aborting method 
\SMEE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.695006] ACPI Error: Aborting method 
\SMIE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.695174] ACPI Error: Aborting method 
\NEVT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.695348] ACPI Error: Aborting method 
\_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
  May 18 10:03:03 jonsmith kernel: [  291.373091] audit: type=1107 
audit(1684384383.334:60): pid=1089 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" peer_pid= 
peer_label="unconfined"
  May 18 10:03:03 jonsmith kernel: [  291.373091]  exe="/usr/bin/dbus-daemon" 
sauid=102 hostname=? addr=? terminal=?'
  May 18 10:03:03 jonsmith kernel: [  291.373813] audit: type=1107 
audit(1684384383.334:61): pid=1089 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" 
mask="send" name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" 
peer_pid= peer_label="unconfined"
  May 18 10:03:03 jonsmith kernel: [  291.373813]  exe="/usr/bin/dbus-daemon" 
sauid=102 hostname=? addr=? terminal=?'
  May 18 10:03:03 jonsmith kernel: [  291.377907] audit: type=1107 
audit(1684384383.338:62): pid=1089 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" peer_pid= 
peer_label="unconfined"
  May 18 10:03:03 jonsmith kernel: [  291.377907]  exe="/usr/bin/dbus-daemon" 
sauid=102 hostname=? addr=? terminal=?'
  May 18 10:03:03 jonsmith kernel: [  291.378569] audit: type=1107 
audit(1684384383.338:63): pid=1089 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  

[Desktop-packages] [Bug 2020078] Re: firefox-snap causes system-wide freeze

[Luke Goshen]

I have Ubuntu 22.04 installed on my system with 16GB RAM and 1TB disk
space.

Running a large number of resource-heavy apps/processes does (and
should, logically) cause system freezes/hangups, after which the system
must be rebooted.

But when running Firefox, no matter how low the resource consumption
from other background apps, the system freezes with a high probability,
sometimes with as low as 3 open tabs. If browser cache is a problem, I
tend to browse in Private Mode most often, yet that does not stop a
system crash.

I have kept track of CPU consumption in the System Monitor, and my
system has crashed several times without there having been more than 20%
RAM usage. Firefox also doesn't have any crash reports from these
instances. I have tried several fixes suggested by Mozilla (turning off
hardware acceleration etc) but none have resulted in any improvements in
my situation. I remember running 4-5 windows each with at least 5 tabs
without ever encountering a crash. Please help me fix this issue.

Please find the last few lines from the system log above. I forced
shutdown after the last line using the power button because of a system
freeze.

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

Title:
  firefox-snap causes system-wide freeze

Status in firefox package in Ubuntu:
  New

Bug description:
  May 18 10:03:02 jonsmith kernel: [  290.566068] ACPI Error: Aborting method 
\_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566228] ACPI Error: Aborting method 
\EV5 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566389] ACPI Error: Aborting method 
\SMEE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566550] ACPI Error: Aborting method 
\SMIE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566708] ACPI Error: Aborting method 
\NEVT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.566899] ACPI Error: Aborting method 
\_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.694431] ACPI BIOS Error (bug): Could 
not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND 
(20220331/psargs-330)
  May 18 10:03:02 jonsmith kernel: [  290.694455] 
  May 18 10:03:02 jonsmith kernel: [  290.694458] No Local Variables are 
initialized for Method [BRT6]
  May 18 10:03:02 jonsmith kernel: [  290.694460] 
  May 18 10:03:02 jonsmith kernel: [  290.694463] Initialized Arguments for 
Method [BRT6]:  (2 arguments defined for method invocation)
  May 18 10:03:02 jonsmith kernel: [  290.694465]   Arg0:   409b1dbf 
   Integer 0001
  May 18 10:03:02 jonsmith kernel: [  290.694477]   Arg1:   ad7ffa02 
   Integer 
  May 18 10:03:02 jonsmith kernel: [  290.694486] 
  May 18 10:03:02 jonsmith kernel: [  290.694490] ACPI Error: Aborting method 
\_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.694650] ACPI Error: Aborting method 
\EV5 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.694810] ACPI Error: Aborting method 
\SMEE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.695006] ACPI Error: Aborting method 
\SMIE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.695174] ACPI Error: Aborting method 
\NEVT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
  May 18 10:03:02 jonsmith kernel: [  290.695348] ACPI Error: Aborting method 
\_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
  May 18 10:03:03 jonsmith kernel: [  291.373091] audit: type=1107 
audit(1684384383.334:60): pid=1089 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" peer_pid= 
peer_label="unconfined"
  May 18 10:03:03 jonsmith kernel: [  291.373091]  exe="/usr/bin/dbus-daemon" 
sauid=102 hostname=? addr=? terminal=?'
  May 18 10:03:03 jonsmith kernel: [  291.373813] audit: type=1107 
audit(1684384383.334:61): pid=1089 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" 
mask="send" name=":1.9" pid=2650 

[Desktop-packages] [Bug 2020078] [NEW] firefox-snap causes system-wide freeze

[Luke Goshen]

Public bug reported:

May 18 10:03:02 jonsmith kernel: [  290.566068] ACPI Error: Aborting method 
\_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
May 18 10:03:02 jonsmith kernel: [  290.566228] ACPI Error: Aborting method 
\EV5 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
May 18 10:03:02 jonsmith kernel: [  290.566389] ACPI Error: Aborting method 
\SMEE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
May 18 10:03:02 jonsmith kernel: [  290.566550] ACPI Error: Aborting method 
\SMIE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
May 18 10:03:02 jonsmith kernel: [  290.566708] ACPI Error: Aborting method 
\NEVT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
May 18 10:03:02 jonsmith kernel: [  290.566899] ACPI Error: Aborting method 
\_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
May 18 10:03:02 jonsmith kernel: [  290.694431] ACPI BIOS Error (bug): Could 
not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND 
(20220331/psargs-330)
May 18 10:03:02 jonsmith kernel: [  290.694455] 
May 18 10:03:02 jonsmith kernel: [  290.694458] No Local Variables are 
initialized for Method [BRT6]
May 18 10:03:02 jonsmith kernel: [  290.694460] 
May 18 10:03:02 jonsmith kernel: [  290.694463] Initialized Arguments for 
Method [BRT6]:  (2 arguments defined for method invocation)
May 18 10:03:02 jonsmith kernel: [  290.694465]   Arg0:   409b1dbf 
   Integer 0001
May 18 10:03:02 jonsmith kernel: [  290.694477]   Arg1:   ad7ffa02 
   Integer 
May 18 10:03:02 jonsmith kernel: [  290.694486] 
May 18 10:03:02 jonsmith kernel: [  290.694490] ACPI Error: Aborting method 
\_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
May 18 10:03:02 jonsmith kernel: [  290.694650] ACPI Error: Aborting method 
\EV5 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
May 18 10:03:02 jonsmith kernel: [  290.694810] ACPI Error: Aborting method 
\SMEE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
May 18 10:03:02 jonsmith kernel: [  290.695006] ACPI Error: Aborting method 
\SMIE due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
May 18 10:03:02 jonsmith kernel: [  290.695174] ACPI Error: Aborting method 
\NEVT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
May 18 10:03:02 jonsmith kernel: [  290.695348] ACPI Error: Aborting method 
\_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) 
(20220331/psparse-529)
May 18 10:03:03 jonsmith kernel: [  291.373091] audit: type=1107 
audit(1684384383.334:60): pid=1089 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" peer_pid= 
peer_label="unconfined"
May 18 10:03:03 jonsmith kernel: [  291.373091]  exe="/usr/bin/dbus-daemon" 
sauid=102 hostname=? addr=? terminal=?'
May 18 10:03:03 jonsmith kernel: [  291.373813] audit: type=1107 
audit(1684384383.334:61): pid=1089 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" 
mask="send" name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" 
peer_pid= peer_label="unconfined"
May 18 10:03:03 jonsmith kernel: [  291.373813]  exe="/usr/bin/dbus-daemon" 
sauid=102 hostname=? addr=? terminal=?'
May 18 10:03:03 jonsmith kernel: [  291.377907] audit: type=1107 
audit(1684384383.338:62): pid=1089 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" peer_pid= 
peer_label="unconfined"
May 18 10:03:03 jonsmith kernel: [  291.377907]  exe="/usr/bin/dbus-daemon" 
sauid=102 hostname=? addr=? terminal=?'
May 18 10:03:03 jonsmith kernel: [  291.378569] audit: type=1107 
audit(1684384383.338:63): pid=1089 uid=102 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/PolicyKit1/Authority" 
interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" 
mask="send" name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" 
peer_pid= peer_label="unconfined"
May 18 10:03:03 jonsmith kernel: [  291.378569]  exe="/usr/bin/dbus-daemon" 
sauid=102 hostname=? addr=? terminal=?'
May 18 10:03:04 jonsmith kernel: [  292.511267] audit: type=1400 
audit(1684384384.470:64): apparmor="DENIED" operation="open" 

[Desktop-packages] [Bug 2004554] Re: Dock shows wrong indicator dots (eventually) when "Include applications from the current workspace only" is enabled

[Luke Henderson]

For me, the bug (assuming it's the same one) manifests itself as an
incorrectly placed dot on a primary workspace. After I have used the
"Show Applications" menu to move a "favorite" app to another workspace,
I click back to the primary workspace. Even though the app is not on
this primary workspace, the indicator dot remains. Toggling between the
two workspaces resolves the issue and the dot goes away while I'm
looking at the primary workspace.

I have these extensions enabled:
d...@rastersoft.com
ubuntu-appindicat...@ubuntu.com
ubuntu-d...@ubuntu.com

Note that this problem does not exist for apps that are on the other
side of the separator, along with the recycle bin. I have firefox,
files, and terminal pinned using "favorite". This would explain why the
initial comment mentions "files" as it's probably pinned.

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

Title:
  Dock shows wrong indicator dots (eventually) when "Include
  applications from the current workspace only" is enabled

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged

Bug description:
  While switching workspace, the option : include applications from
  current workspace only is opted. The files founder does not switch
  properly. If opened in one workspace, and switched to another
  workspace. Then the dot ( that shoes finder is open) does not go away.
  And many more please check.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  2 16:47:24 2023
  DistUpgraded: 2023-01-27 15:07:45,014 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] CoffeeLake-H GT2 [UHD 
Graphics 630] [1462:12aa]
   NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f15] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU106M [GeForce RTX 
2060 Mobile] [1462:12aa]
  InstallationDate: Installed on 2021-05-11 (631 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Micro-Star International Co., Ltd. GF65 Thin 9SEXR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=f2aafeb8-65f1-4f53-a7f4-a8bac75a5fbd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2023-01-27 (6 days ago)
  dmi.bios.date: 10/21/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16W1IMS.10C
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16W1
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16W1IMS.10C:bd10/21/2021:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnGF65Thin9SEXR:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16W1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku16W1.1:
  dmi.product.family: GF
  dmi.product.name: GF65 Thin 9SEXR
  dmi.product.sku: 16W1.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  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/gnome-shell-extension-ubuntu-dock/+bug/2004554/+subscriptions


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

[Desktop-packages] [Bug 2012199] [NEW] nautilus crashes during search or bulk filename editing

[Luke Goshen]

Public bug reported:

EVERY search or bulk file renaming action causes nautilus to crash
immediately. All searches cause nautilus to crash immediately. No search
ever comes through. Simple typing in the search bar, or as much as
clicking on it causes nautilus to crash.

Once multiple files are selected and Fn+F2 (Rename) action is selected,
nautilus crashes even without allowing the rename dialog box to appear.
Note that single file renaming still works.

The crashed window gives the option to wait, but waiting never solves
the problem, and I am always forced to restart nautilus after force-
quitting.

What is causing this problem? If this issue is not widespread enough to
receive a bugfix, could the developers guide me with this. I find doing
a fresh install risky because of lack of enough storage for a complete
PC backup.

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

** Package changed: grub-installer (Ubuntu) => nautilus (Ubuntu)

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

Title:
  nautilus crashes during search or bulk filename editing

Status in nautilus package in Ubuntu:
  New

Bug description:
  EVERY search or bulk file renaming action causes nautilus to crash
  immediately. All searches cause nautilus to crash immediately. No
  search ever comes through. Simple typing in the search bar, or as much
  as clicking on it causes nautilus to crash.

  Once multiple files are selected and Fn+F2 (Rename) action is
  selected, nautilus crashes even without allowing the rename dialog box
  to appear. Note that single file renaming still works.

  The crashed window gives the option to wait, but waiting never solves
  the problem, and I am always forced to restart nautilus after force-
  quitting.

  What is causing this problem? If this issue is not widespread enough
  to receive a bugfix, could the developers guide me with this. I find
  doing a fresh install risky because of lack of enough storage for a
  complete PC backup.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2012199/+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 1981665] Re: window size changes after unlocking locked screen

[Luke Goshen]

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

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

** No longer affects: ubuntu

** Description changed:

  My display has dock enabled without auto-hide.
  
  When I lock the screens with multiple windows open (usually including
  Firefox, Nautilus and Evince), and then unlock it a few moments later,
  one of these windows is oversized and fullscreen (covering the whole
  screen from beneath the dock).
+ 
+ This issue also occurs at times without any lock-unlock event, when
+ there are 3 and more active windows.

** Summary changed:

- window size changes after unlocking locked screen
+ window size changes without specific triggers

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

Title:
  window size changes without specific triggers

Status in evince package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  My display has dock enabled without auto-hide.

  When I lock the screens with multiple windows open (usually including
  Firefox, Nautilus and Evince), and then unlock it a few moments later,
  one of these windows is oversized and fullscreen (covering the whole
  screen from beneath the dock).

  This issue also occurs at times without any lock-unlock event, when
  there are 3 and more active windows.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1981665/+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 1913977] Re: Bad sound quality (no bass) on Thinkpad T490s

[Luke Larsen]

I am having the same issue on my Thinkpad T490. Very tinny/high treble
audio with no bass.

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

Title:
  Bad sound quality (no bass) on Thinkpad T490s

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound works on with 20.04 on the Thinkpad T490s, but sound quality is
  noticeably worse than on Windows. It looks like the same bug here:
  https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hmahmood   1360 F pulseaudio
   /dev/snd/pcmC0D0p:   hmahmood   1360 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 31 19:14:57 2021
  InstallationDate: Installed on 2021-01-30 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [20NYS83800, Realtek ALC257, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2020
  dmi.bios.release: 1.70
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET92W (1.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NYS83800
  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.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2JET92W(1.70):bd08/31/2020:br1.70:efr1.20:svnLENOVO:pn20NYS83800:pvrThinkPadT490s:rvnLENOVO:rn20NYS83800:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T490s
  dmi.product.name: 20NYS83800
  dmi.product.sku: LENOVO_MT_20NY_BU_Think_FM_ThinkPad T490s
  dmi.product.version: ThinkPad T490s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1913977/+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 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

[Luke Faraone]

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1849346/+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 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

[Luke Faraone]

Unless the snap move was intended to provide isolation from Kerberos,
setting to medium because this breaks many enterprise usecases for
Firefox.

** Changed in: firefox (Ubuntu)
   Importance: Undecided => Medium

** Changed in: firefox (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1849346/+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 1481835]

[Luke]

Why is this listed as a "papercut"?  From Regina's analysis in Comment
48, the developer is going to have to be very careful to not break
things worse than they fix. For a student developer new the codebase,
this sounds like a standalone project  itself.

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

Title:
  [UPSTREAM] Unable to group raster image(s) with drawing object(s)

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:
 1. Create new document in LibreOffice Writer
 2. put rester images into document and put on images some drawing objects 
(arrows, other shapes), text. 
 3. try to group images with drawing objects.

  Expected behaviour:
 User can select and group image(s) with drawing object(s)

  Actual behaviour:
 User can not select and group image(s) with drawing object(s)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice 1:3.5.7-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-61.100~precise1-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  Date: Wed Aug  5 18:59:59 2015
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1481835/+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 1917183] Re: Font spacing and rendering is wrong in Firefox 86

[Luke Horwell]

It may not be just limited to Firefox, I can confirm the WebKit
inspector window has rendering issues too. Ubuntu MATE Welcome is an
example.

$ ubuntu-mate-welcome --inspect

(Note that I was running from its source code, I have not checked the
snap)

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

Title:
  Font spacing and rendering is wrong in Firefox 86

Status in Ubuntu MATE:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu MATE 21.04 Font spacing is incorrect.

  Including screen shots of pages.

  This front spacing issue is occurring whilst filing this bug report on
  Launchpad.

  Expected outcome:
  Font's space and render properly in Firefox

  Actual outcome:
  Font space and render is incorrect.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: firefox 86.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  franksmcb   2695 F pulseaudio
  BuildID: 20210222142601
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: MATE
  Date: Sat Feb 27 16:50:33 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:348
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntumate.js
   prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2019-12-13 (442 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20191213)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.154 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:348
  Profile0PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntumate.js
   prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=77.0/20200528194502 (Out of date)
   Profile0 - LastVersion=86.0/20210222142601 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to hirsute on 2020-06-02 (270 days ago)
  dmi.bios.date: 08/07/2019
  dmi.bios.release: 2.82
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETC2WW (2.82 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2347GBU
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2347GBU:pvrThinkPadT430:rvnLENOVO:rn2347GBU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2347GBU
  dmi.product.sku: LENOVO_MT_2347
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1917183/+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 1846423] Re: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION

[Luke Gopher]

I Confirm that bug on Ubuntu Focal with release
:1:78.5.1+build1-0ubuntu0.20.04.1

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

Title:
  Lightning: Cannot dismiss reminders. Got a VALUE parameter with an
  illegal type for property: VALUE=DURATION

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Cannot dismiss reminders for a recurrence with exceptions. Calendar entries 
like this are generated:
  BEGIN:VALARM
  ACTION:DISPLAY
  DESCRIPTION:My recurrence
  TRIGGER;VALUE=DURATION:-PT120M
  X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Got a VALUE parame
   ter with an illegal type for property: VALUE=DURATION
  END:VALARM

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xul-ext-lightning 1:60.8.0+build1-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2004 F pulseaudio
   /dev/snd/controlC0:  vectro 2004 F pulseaudio
  BuildID: 20190705212852
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Wed Oct  2 17:50:39 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.14 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=60.8.0/20190705212852 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.sku: T4M40UT#ABA
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1846423/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Luke Renaud]

>From what I can gather this is not a function of the headset or
Bluetooth device, but it's a function of firmware differences in the
host side Bluetooth adapters.

For example, I have a Sony WH-1000MX3.

I have a USB dongle adapter that does not work in the HSP/HFP mode. When
selecting the mode the active profile throws various errors then returns
to the "off" PulseAudio/ALSA profile.

lsusb on the CSR USB dongle.
```
Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle 
(HCI mode)
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass  224 Wireless
  bDeviceSubClass 1 Radio Frequency
  bDeviceProtocol 1 Bluetooth
  bMaxPacketSize064
  idVendor   0x0a12 Cambridge Silicon Radio, Ltd
  idProduct  0x0001 Bluetooth Dongle (HCI mode)
  bcdDevice   88.91
  iManufacturer   0 
  iProduct2 
  iSerial 0 
  bNumConfigurations  1
```

I also have an Intel Bluetooth/WiFi 802.11ac card (Bluetooth is on the
USB bus), that does support the HSP/HFP mode, abet with noticeably
reduced audio quality. I think there is a separate bug in launchpad
tracking the audio quality issues of that mode though.

header for `lsusb -v` on the Intel card.
```
Bus 001 Device 005: ID 8087:07dc Intel Corp. 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass  224 Wireless
  bDeviceSubClass 1 Radio Frequency
  bDeviceProtocol 1 Bluetooth
  bMaxPacketSize064
  idVendor   0x8087 Intel Corp.
  idProduct  0x07dc 
  bcdDevice0.01
  iManufacturer   0 
  iProduct0 
  iSerial 0 
  bNumConfigurations  1
```

lspci on the intel card
```
04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260
Flags: bus master, fast devsel, latency 0, IRQ 96
Memory at f760 (64-bit, non-prefetchable) [size=8K]
Capabilities: 
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
```

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1852679] Re: CLI to copy to clipboard does not work

[Luke Midworth]

I'm using Cinnamon and the same thing happens - CLI `gnome-screenshot
--area --clipboard` fails to capture to the clipboard. Instead, it gives
the following errors:

```
** Message: 17:49:49.673: Unable to select area using GNOME Shell's builtin 
screenshot interface, resorting to fallback X11.
** Message: 17:49:58.422: Unable to use GNOME Shell's builtin screenshot 
interface, resorting to fallback X11.
```

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

Title:
  CLI to copy to clipboard does not work

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded today to 19.10.  I have a keyboard shortcut setup to run 
gnome-screenshot --area -c to allow me to do quick screen grabs.  I can confirm 
that if I use the screenshot dialog I can copy to the clipboard with that but 
using the CLI version of the same function does not work. 
  It looks like it functions normal but when you go to paste the screenshot 
that you just took, nothing happens. 

  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  apt-cache policy gnome-screenshot
  gnome-screenshot:
Installed: 3.33.90-1ubuntu1
Candidate: 3.33.90-1ubuntu1
Version table:
   *** 3.33.90-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1852679/+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 1876467] Re: Network Manager Applet Icon error on VPN Connection

[Luke Horwell]

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

** This bug has been marked a duplicate of bug 1875066
   Missing NM-icon for established vpn-connections

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

Title:
  Network Manager Applet Icon error on VPN Connection

Status in Ubuntu MATE:
  New
Status in network-manager-applet package in Ubuntu:
  Invalid

Bug description:
  The Network icon in the top panel doesn't change to the icon with a
  lock when a Palo Alto VPN Network is conected.

  In ubuntu Mate 16 and 18 the default behavior was to change the icon
  adding a small size lock.

  In Ubuntu Mate 20, in Traditional Desktop, seems something is missing.
  When connecting to the VPN, icon changes to a black screen with a
  forbidden icon (see attachment).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1876467/+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 1874047] Re: 20.04 - Software Boutique - No Filter drop-down placement

[Luke Horwell]

** Changed in: ubuntu-mate
   Status: Confirmed => Invalid

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

Title:
  20.04 - Software Boutique - No Filter drop-down placement

Status in Ubuntu MATE:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released

Bug description:
  Open the Software Boutique and click on 'Sound and Video' and then
  click on the drop-down curently set to 'No Filter'.

  Expected result:  menu of options opens immediately below.

  Actual result:  menu for filters appears way off to the right, and
  below, outside of the application window.

  Problem reported originally by lqlarry here - https://ubuntu-
  mate.community/t/software-boutique-filter-menu/21546

  I have confirmed that it affects more than 1 person.

  Ubuntu-MATE RC1 installed and updated from daily since start of Alpha
  test (clean install at that time).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1874047/+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 1874047] Re: 20.04 - Software Boutique - No Filter drop-down placement

[Luke Horwell]

Yep, I came across the same reports this morning before checking here. I
can confirm from yesterday that GNOME Web (epiphany-browser) also
demonstrates the misplacement. Here's a test page:

https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select

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

Title:
  20.04 - Software Boutique - No Filter drop-down placement

Status in Ubuntu MATE:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  In Progress

Bug description:
  Open the Software Boutique and click on 'Sound and Video' and then
  click on the drop-down curently set to 'No Filter'.

  Expected result:  menu of options opens immediately below.

  Actual result:  menu for filters appears way off to the right, and
  below, outside of the application window.

  Problem reported originally by lqlarry here - https://ubuntu-
  mate.community/t/software-boutique-filter-menu/21546

  I have confirmed that it affects more than 1 person.

  Ubuntu-MATE RC1 installed and updated from daily since start of Alpha
  test (clean install at that time).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1874047/+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 1874047] Re: 20.04 - Software Boutique - No Filter drop-down placement

[Luke Horwell]

This is a regression introduced in gir1.2-webkit2 2.28.1, which Ubuntu
updated on 16th April 2020 for security updates. This was working fine
in 2.28.0.

This affects other applications that use WebKit2.

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

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

Title:
  20.04 - Software Boutique - No Filter drop-down placement

Status in Ubuntu MATE:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  Open the Software Boutique and click on 'Sound and Video' and then
  click on the drop-down curently set to 'No Filter'.

  Expected result:  menu of options opens immediately below.

  Actual result:  menu for filters appears way off to the right, and
  below, outside of the application window.

  Problem reported originally by lqlarry here - https://ubuntu-
  mate.community/t/software-boutique-filter-menu/21546

  I have confirmed that it affects more than 1 person.

  Ubuntu-MATE RC1 installed and updated from daily since start of Alpha
  test (clean install at that time).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1874047/+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 1867943] [NEW] Nautilus “Open Other Application” problem

[Luke Thallmayer]

Public bug reported:

When using Nautilus and I right click on an image file I get a drop down
menu, the first two items are “Open With *Default application*” and
“Open With Other Application”.

I use Mirage as my default application for image files.

On one account when I right click on an image file and choose “Open With
Other Application”, Mirage is the preselected application not “Image
Viewer” which is my usual second choice.

On another account Mirage isn’t preselected, “Image Viewer” is. This is
the expected behavior.

I used the "Properties"->"Open With" to select “Image Viewer” and set it
as the default. But that didn't work, it went back to Mirage as the
default.

I tried setting other programs as the default the same way and none
stuck, it always returned to Mirage.

I went to Settings->Details->Default Applications and changed the
“Photos” from Mirage to “Image Viewer”. That worked and when right
clicking and selecting “Other Application” Mirage is preselected. As
expected.

When I changed Settings->Details->Default Applications->“Photos” back to
Mirage the problem returned. Mirage is the default and the preselected
“Other Application”.

“Right click on an image file and select : 'Open With Other Application' Then 
right click on the application that you do not want to be on that menu. Click 
on 'Forget association'”. Worked on other programs but not on Mirage.
 
Description:Ubuntu 18.04 LTS (beaver-osha X84)
Release:18.04
Nautilus 1:3.26.4-0~ubuntu18.04.5 (from Software center)

I expected Image Viewer to be the preselected Other Application.
I got Mirage as the default application and the preselected “Other Application”

I expected Mirage to be removed from the list when I clicked on “Forget 
association”
What I got was Mirage would not go gently into the night

I expected Mirage to accept not being the default application when using 
"Properties"->"Open With" to chose another application as the default.
What I got was Mirage remaining the default.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.4-0~ubuntu18.04.5
ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18
Uname: Linux 4.15.0-1073-oem x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 18 11:21:53 2020
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osha+X84
InstallationDate: Installed on 2019-11-28 (111 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug bionic

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

Title:
  Nautilus “Open Other Application” problem

Status in nautilus package in Ubuntu:
  New

Bug description:
  When using Nautilus and I right click on an image file I get a drop
  down menu, the first two items are “Open With *Default application*”
  and “Open With Other Application”.

  I use Mirage as my default application for image files.

  On one account when I right click on an image file and choose “Open
  With Other Application”, Mirage is the preselected application not
  “Image Viewer” which is my usual second choice.

  On another account Mirage isn’t preselected, “Image Viewer” is. This
  is the expected behavior.

  I used the "Properties"->"Open With" to select “Image Viewer” and set
  it as the default. But that didn't work, it went back to Mirage as the
  default.

  I tried setting other programs as the default the same way and none
  stuck, it always returned to Mirage.

  I went to Settings->Details->Default Applications and changed the
  “Photos” from Mirage to “Image Viewer”. That worked and when right
  clicking and selecting “Other Application” Mirage is preselected. As
  expected.

  When I changed Settings->Details->Default Applications->“Photos” back
  to Mirage the problem returned. Mirage is the default and the
  preselected “Other Application”.

  “Right click on an image file and select : 'Open With Other Application' Then 
right click on the application that you do not want to be on that menu. Click 
on 'Forget association'”. Worked on other programs but not on Mirage.
   
  Description:  Ubuntu 18.04 LTS (beaver-osha X84)
  Release:  18.04
  Nautilus 1:3.26.4-0~ubuntu18.04.5 (from Software center)

  I expected Image Viewer to be the preselected Other Application.
  I got Mirage as the default application and the preselected “Other 
Application”

  I expected 

[Desktop-packages] [Bug 1862281] Re: Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse

[Luke Barone-Adesi]

The problem does not show up on "Ubuntu on Wayland" (as judged by 20
minutes of moving the mouse while running the stress-ng script in the
first post).

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

Title:
  Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  If I run a thermal transition test script (30 seconds stress-ng, 30
  seconds sleep, in a loop) and move a local USB mouse, Kubuntu reliably
  crashes, usually in the first couple of runs and almost 100% of the
  time by run 6.

  This appears to be hardware-linked, but not due to a specific piece of
  bad hardware: I have swapped literally every piece of hardware in the
  system.

  It shows up (while running the script at the end):
  - On both an MSI B450 Gaming plus max and MSI MPG X570 Gaming plus mainboard.
  - On both an AMD Ryzen 5 3600 and 3600X CPU.
  - With one or two sticks of RAM. I've tested both sticks individually, in 
more than one mainboard slot.
  - Regardless of whether the mainboard is in/attached to a case.
  - Regardless of whether there is an m.2 SSD installed or I'm running off a 
live Kubuntu 19.10 USB stick with no hard disk attached.
  - Regardless of which of two mice I use (an old Logitech one, or a GTX 133 
Gaming mouse).
  - Regardless of whether I'm using a Corsair VS650 or Corsair AX850 PSU.
  - Regardless of whether I'm using an AMD RX 5700 XT or using an Nvidia 
Gigabyte GeForce RTX 2700 Super (with open source drivers in both cases).
  - Regardless of whether I'm using KDE or XFCE.
  - Regardless of whether I'm using the default KDE DM or switch to GDM3 and 
set WaylandEnable=false.
  - Regardless of whether I use the default 5.3.0-29-generic kernel or 
5.4.17-050417-generic.
  - Regardless of whether I go directly into the graphical environment or start 
in runlevel 3 and then manually run startx.
  - Regardless of whether it's on the rising or falling edge of the 
stress-script's temperature changes.
  - Regardless of bios version on the X570 mainboard (the one it shipped with, 
or the newest one released in January 2020).
  - Regardless of whether XMP is on or off in the bios.
  - Regardless of whether I use the default or set global c-state to "control = 
disabled" in the bios.
  - Regardless of whether I add processor.max_cstate=5 idle=halt in grub.
  - Regardless of whether or not speakers are plugged in.
  - Regardless of whether I'm using a USB port that is directly on the 
motherboard or is on the front of the case.
  - Regardless of which monitor it is attached to.

  It doesn't show up:
  - On an old i7-4771 machine I have, also running Kubuntu 19.10, while running 
the test script.
  - When I use a mouse remotely with ssh -Y [ip of the machine I am reporting 
this from] xeyes, while running the test script.
  - When I do non-mouse USB input, ie via a USB keyboard or USB wifi dongle, 
including under saturated network load, while running the test script.
  - During stress tests of the GPU, CPU, etc. Tools like memtest, mprime, 
Unigine Superposition, repeated kernel compiles, etc run stably overnight.
  - When the system is entirely idle aside from mouse movement.
  - When I start in runlevel 3 and run the same test script, using the mouse 
with gpm.
  - Running the same test script without mouse movement: this was stable 
overnight, then crashed within a couple of minutes of moving the mouse.

  It shows up with load other than the stress-ng+sleep script too, but
  much less reliably - I'm writing this bug report on the relevant
  machine, with firefox open. Crashes occur at least once a week under
  these conditions, but not frequently.

  Crashes occur with sensor-reported CPU temperatures of 32 to 41
  degrees Celsius. Nothing is overheating, and the system is stable at
  much higher temperatures under sustained stress tests.

  The symptoms of the crash: the display stops updating and the system
  does not respond to any further input, including via the network or
  magic sysrq key. There is nothing related to it in syslog or
  journalctl, including when I'm running journalctl -f at the time of
  the crash.

  The test script:
  #!/bin/bash
  for x in {1..1}
  do
  echo "Run $x at `date`"
  stress-ng --cpu 12 --cpu-method all --verify -t 30s --metrics-brief
  sleep 30
  done

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  Uname: Linux 5.4.17-050417-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Feb  7 00:02:22 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA 

[Desktop-packages] [Bug 1862281] Re: Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse

[Luke Barone-Adesi]

I've installed weston, run telinit 3, and from the terminal run weston-
launch. 20 minutes of moving the mouse later, this appears to be stable
(just as gpm in a console after booting into runlevel 3 is).

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

Title:
  Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  If I run a thermal transition test script (30 seconds stress-ng, 30
  seconds sleep, in a loop) and move a local USB mouse, Kubuntu reliably
  crashes, usually in the first couple of runs and almost 100% of the
  time by run 6.

  This appears to be hardware-linked, but not due to a specific piece of
  bad hardware: I have swapped literally every piece of hardware in the
  system.

  It shows up (while running the script at the end):
  - On both an MSI B450 Gaming plus max and MSI MPG X570 Gaming plus mainboard.
  - On both an AMD Ryzen 5 3600 and 3600X CPU.
  - With one or two sticks of RAM. I've tested both sticks individually, in 
more than one mainboard slot.
  - Regardless of whether the mainboard is in/attached to a case.
  - Regardless of whether there is an m.2 SSD installed or I'm running off a 
live Kubuntu 19.10 USB stick with no hard disk attached.
  - Regardless of which of two mice I use (an old Logitech one, or a GTX 133 
Gaming mouse).
  - Regardless of whether I'm using a Corsair VS650 or Corsair AX850 PSU.
  - Regardless of whether I'm using an AMD RX 5700 XT or using an Nvidia 
Gigabyte GeForce RTX 2700 Super (with open source drivers in both cases).
  - Regardless of whether I'm using KDE or XFCE.
  - Regardless of whether I'm using the default KDE DM or switch to GDM3 and 
set WaylandEnable=false.
  - Regardless of whether I use the default 5.3.0-29-generic kernel or 
5.4.17-050417-generic.
  - Regardless of whether I go directly into the graphical environment or start 
in runlevel 3 and then manually run startx.
  - Regardless of whether it's on the rising or falling edge of the 
stress-script's temperature changes.
  - Regardless of bios version on the X570 mainboard (the one it shipped with, 
or the newest one released in January 2020).
  - Regardless of whether XMP is on or off in the bios.
  - Regardless of whether I use the default or set global c-state to "control = 
disabled" in the bios.
  - Regardless of whether I add processor.max_cstate=5 idle=halt in grub.
  - Regardless of whether or not speakers are plugged in.
  - Regardless of whether I'm using a USB port that is directly on the 
motherboard or is on the front of the case.
  - Regardless of which monitor it is attached to.

  It doesn't show up:
  - On an old i7-4771 machine I have, also running Kubuntu 19.10, while running 
the test script.
  - When I use a mouse remotely with ssh -Y [ip of the machine I am reporting 
this from] xeyes, while running the test script.
  - When I do non-mouse USB input, ie via a USB keyboard or USB wifi dongle, 
including under saturated network load, while running the test script.
  - During stress tests of the GPU, CPU, etc. Tools like memtest, mprime, 
Unigine Superposition, repeated kernel compiles, etc run stably overnight.
  - When the system is entirely idle aside from mouse movement.
  - When I start in runlevel 3 and run the same test script, using the mouse 
with gpm.
  - Running the same test script without mouse movement: this was stable 
overnight, then crashed within a couple of minutes of moving the mouse.

  It shows up with load other than the stress-ng+sleep script too, but
  much less reliably - I'm writing this bug report on the relevant
  machine, with firefox open. Crashes occur at least once a week under
  these conditions, but not frequently.

  Crashes occur with sensor-reported CPU temperatures of 32 to 41
  degrees Celsius. Nothing is overheating, and the system is stable at
  much higher temperatures under sustained stress tests.

  The symptoms of the crash: the display stops updating and the system
  does not respond to any further input, including via the network or
  magic sysrq key. There is nothing related to it in syslog or
  journalctl, including when I'm running journalctl -f at the time of
  the crash.

  The test script:
  #!/bin/bash
  for x in {1..1}
  do
  echo "Run $x at `date`"
  stress-ng --cpu 12 --cpu-method all --verify -t 30s --metrics-brief
  sleep 30
  done

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  Uname: Linux 5.4.17-050417-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Feb  7 00:02:22 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  

[Desktop-packages] [Bug 1843201] Re: Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome

[Luke Faraone]

Thanks for looking into this, and the pointer.

I guess, another option would be to not request shortcut inhibition,
unless I'm misunderstanding its value? Unless there's a worry that some
other application will be able to steal your password this way — it
doesn't seem obviously warranted to me.

For example, `ssh-askpass-fullscreen` does not generate this prompt. It
isn't clear to me that the fullscreen-ness of this implementation
materially changes the risk profile, so either shortcut inhibition isn't
useful, or I should file a bug against `ssh-askpass-fullscreen` to
either request this privilege or document the gap.

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

Title:
  Unity in Wayland prompts for keyboard focus on each run of ssh-
  askpass-gnome

Status in gnome-desktop package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  New

Bug description:
  When using a Wayland-based Unity session on Ubuntu 19.04:

  1. Have ssh-askpass-gnome as your askpass program.
  2. ssh-add -c 
  3. `ssh` to a host

  Each time, before the ssh-askpass prompt is shown, Unity shows this
  dialog:

  +-+
  | |
  | ssh-askpass wants to inhibit shortcuts  |
  | |
  | You can restore Shortcuts by pressing   |
  | Super+Escape.   |
  | |
  |_|
  |   Deny | Allow  |
  +-+

  This is mildly distracting, and it means that you need to hit ,
  answer, , instead of just answer .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ssh-askpass-gnome 1:7.9p1-10
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  8 15:04:25 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1
  InstallationDate: Installed on 2019-08-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1843201/+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 1733002] Re: Google Online Account Two Factor with hardware key fails immediately

[Luke Faraone]

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Triaged

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

Title:
  Google Online Account Two Factor with hardware key fails immediately

Status in gnome-online-accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  The hardware key authentication two factor fails immediately with a
  web based retry dialogue when connecting a Google account to the
  online accounts in settings using a hardware key second factor.

  Steps to reproduce:
  1. Set Google Account to default to a hardware security key like a Yubikey or 
other FIDO standard key after having two factor authentication enabled on your 
Google Account.
  2. Open Online accounts
  3. Add a Google Account
  4. Enter google email address
  5. Enter google password
  6. (this is the login flow of two factor, if default is the hardware key the 
error should appear).

  Work around:
  Choose use another method to authenticate: enter the authentication code and 
you will proceed.

  Expectations were:
  The ability to use the hardware key to authenticate as the second factor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 17 16:01:11 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Luke Meissner]

Until the fix gets pushed to bionic and cosmic, you should able to get
stereo playback using the headphone jack adapter for the headsets that
should be included with them. Cable's a bit short, but it works.

-- 
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 1745666] Re: gsd-housekeeping leaks file descriptors

[Luke Horstman]

I'm not sure if this is related or if this helps troubleshoot, but my
system will randomly go unresponsive and needs to be hard rebooted. May
or may not be related to this bug.

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

Title:
  gsd-housekeeping leaks file descriptors

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Apparently a process called gsd-housekeeping is periodically invoked
  on my Ubuntu 17.10 system. It traverses my /var/tmp for some reason.
  Looks like it is leaking file descriptors while doing so.

  My syslogs are full of error messages like the following:

  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h: Error 
opening directory 
'/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h': Too many 
open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h': Too many 
open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h: Error opening directory 
'/var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h': Too many open files

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt policy gnome-settings-daemon
  gnome-settings-daemon:
Installed: 3.26.2-0ubuntu0.1
Candidate: 3.26.2-0ubuntu0.1
Version table:
   *** 3.26.2-0ubuntu0.1 500
  500 http://se.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-0ubuntu5 500
  500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+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 1745666] Re: gsd-housekeeping leaks file descriptors

[Luke Horstman]

Same issue here. Ubuntu 18.04 Kernel4.15.0-42-generic Dec 06 2018

Failed to enumerate children of /tmp/systemd-private-
42045536c330493292b9e62a860928e4-fwupd.service-GNaXSl: Error opening
directory '/tmp/systemd-private-42045536c330493292b9e62a860928e4-fwupd
.service-GNaXSl': Permission denied

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

Title:
  gsd-housekeeping leaks file descriptors

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Apparently a process called gsd-housekeeping is periodically invoked
  on my Ubuntu 17.10 system. It traverses my /var/tmp for some reason.
  Looks like it is leaking file descriptors while doing so.

  My syslogs are full of error messages like the following:

  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h: Error 
opening directory 
'/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h': Too many 
open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h': Too many 
open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h: Error opening directory 
'/var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h': Too many open files

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt policy gnome-settings-daemon
  gnome-settings-daemon:
Installed: 3.26.2-0ubuntu0.1
Candidate: 3.26.2-0ubuntu0.1
Version table:
   *** 3.26.2-0ubuntu0.1 500
  500 http://se.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-0ubuntu5 500
  500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+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 1750197] Re: App grid animation causes heavy CPU spikes and dropped frames in Wayland & Xorg

[Luke B.]

Not to be nagging, but I can't help but enjoy this upstream fix as it
was implemented in other distros like Fedora. Is there an ETA for
Ubuntu's implementation?

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

Title:
  App grid animation causes heavy CPU spikes and dropped frames in
  Wayland & Xorg

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Upstream Issues:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/349
  https://gitlab.gnome.org/GNOME/mutter/issues/233

  Ubuntu Release: 17.10 and 18.04
  gnome-shell version: 3.28.2
  System Theme: CommuniTheme

  Opening the Applications Overview (App Grid) displays a very janky
  animation, and my CPU will spike to nearly 90% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall higher impact on resource usage.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1750197/+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 823155]

[Luke]

Verified in Version: 6.0.6.2
Build ID: 1:6.0.6-0ubuntu0.18.04.1
and
Version: 6.2.0.0.alpha0+
Build ID: b9234b43ed259a10cf9077032af0f79740f01d8b
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 

The bugdoc attachment 51048 does not play a sound in the slideshow nor
when I edit the custom animation->Options->Preview Sound

If I create a new slideshow, insert shape, and add a custom animation
with a sound. The sound does play in the Options->Preview Sound. If I
preview the animation or start the slideshow, the sound does not play.

Created Bug 120569 to handle Comment 31, sound resource not found which
affect both Linux and Windows machines, preventing even the Sound
Preview from working.

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

Title:
  [Upstream] Impress Custom Animation Sound Effect not audible in Slide
  Show

Status in LibreOffice:
  Confirmed
Status in OpenOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Triaged
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  1)  lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  2) apt-cache policy libreoffice-impress
  libreoffice-impress:
    Installed: 1:3.5.2-2ubuntu1
    Candidate: 1:3.5.2-2ubuntu1
    Version table:
   *** 1:3.5.2-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in a new Impress document via the
  Terminal:

  loimpress --nologo

  New Impress file -> click the rectangle containing "Click to add text"
  -> Under Tasks Custom Animation -> button Add... -> Entrance tab
  highlight Random Effects -> OK button -> right of Property ... button
  -> Effect tab -> change Sound dropdown apert -> OK button -> Slide
  Show and it plays the apert sound.

  4) What happens instead is no sound is played during the slide show.

  Original Reporter Comments: I am using Ubuntu 11.04 Natty. I have
  tested this in Ubuntu 10.10 with OpenOffice.org presentation
  (Impress), same problem too. All in all I have tried this on 3
  different computers. 2 on 11.04 and 1 on 10.10

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libreoffice 1:3.3.2-1ubuntu5
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic i686
  Architecture: i386
  Date: Tue Aug  9 16:59:45 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/823155/+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 1801264] [NEW] Wifi drops out 1-30 minutes after boot on Ubuntu 18.10

[Luke Anscombe]

Public bug reported:

I will boot, Wifi connects fine, and then the wifi drops out and no
connection can be made until a restart. When I try to reconnect it
"Connection Failed: Activation of network connection failed".  The Wifi
works fine on phone and on Fedora 29.

Network Manager 1.12.4

Expected:

Wifi stays connected

Happened:

Wifi drops out after 1-30 minutes.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: network-manager 1.12.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov  2 13:38:42 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-11-02 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
IpRoute:
 default via 192.168.42.129 dev enp0s20f0u2 proto dhcp metric 100 
 169.254.0.0/16 dev enp0s20f0u2 scope link metric 1000 
 192.168.42.0/24 dev enp0s20f0u2 proto kernel scope link src 192.168.42.66 
metric 100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 enp0s20f0u2  ethernet  connected/org/freedesktop/NetworkManager/Devices/3  
Wired connection 1  a79e5d9a-26c0-34c5-a20d-5a371d0eafd6  
/org/freedesktop/NetworkManager/ActiveConnection/9 
 wlp1s0   wifi  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
 lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.12.4   connected  started  full  enabled enabled  
disabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic wayland-session

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

Title:
  Wifi drops out 1-30 minutes after boot on Ubuntu 18.10

Status in network-manager package in Ubuntu:
  New

Bug description:
  I will boot, Wifi connects fine, and then the wifi drops out and no
  connection can be made until a restart. When I try to reconnect it
  "Connection Failed: Activation of network connection failed".  The
  Wifi works fine on phone and on Fedora 29.

  Network Manager 1.12.4

  Expected:

  Wifi stays connected

  Happened:

  Wifi drops out after 1-30 minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 13:38:42 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-02 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IpRoute:
   default via 192.168.42.129 dev enp0s20f0u2 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s20f0u2 scope link metric 1000 
   192.168.42.0/24 dev enp0s20f0u2 proto kernel scope link src 192.168.42.66 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION  CON-UUID  CON-PATH
   
   enp0s20f0u2  ethernet  connected
/org/freedesktop/NetworkManager/Devices/3  Wired connection 1  
a79e5d9a-26c0-34c5-a20d-5a371d0eafd6  
/org/freedesktop/NetworkManager/ActiveConnection/9 
   wlp1s0   wifi  unavailable  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  

[Desktop-packages] [Bug 1799851] Re: Software Boutique window suddenly shows Welcome window and looses all the apps I queued to install

[Luke Horwell]

Robert, please note Martin marked the bug report invalid for "gnome-
software" which is correct as GNOME Software is the wrong package.
"ubuntu-mate-welcome" is the one at fault.

Also note that the "Gtk-Message error" (and poor code quality) you
described for ubuntu-bug is just a GTK warning for the developer of that
application, it is not an error.

---

This bug report does not contain any valuable details of the crash to
address what happened. Software Boutique does not retain the queue
across sessions, and there is no stacktrace nor can it be reproduced for
further inspection.

Please elaborate on this:

> I was selecting apps to install in the Software Boutique, then
suddenly the Boutique Window displayed the welcome window and lost all
the apps I queued for installation.

What are the steps to reproduce the same crash you experienced?

** Changed in: ubuntu-mate-welcome (Ubuntu)
   Status: New => Incomplete

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

Title:
  Software Boutique window suddenly shows Welcome window and looses all
  the apps I queued to install

Status in gnome-software package in Ubuntu:
  Invalid
Status in ubuntu-mate-welcome package in Ubuntu:
  Incomplete

Bug description:
  I was selecting apps to install in the Software Boutique, then
  suddenly the Boutique Window displayed the welcome window and lost all
  the apps I queued for installation.

  Ubuntu 18.04.1 LTS (just reinstalled when Ubuntu MATE 18.10 went into total 
meltdown).
  AMD 64-bit prosessor

  Menu->Administration->Software Boutique

  I had actually hoped to install the same software I had installed when
  I first installed 18.04.

  All work lost.

  The code quality is definitely going down hill fast. (even ubuntu-bug -w gets 
an error message
  robert@A88XM-A:~/Desktop$ ubuntu-bug -w
  Gtk-Message: 20:41:01.726: GtkDialog mapped without a transient parent. This 
is discouraged.).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python3.6-minimal 3.6.6-1~18.04
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Wed Oct 24 20:41:06 2018
  ExecutablePath: /usr/bin/python3.6
  InstallationDate: Installed on 2018-10-25 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  SourcePackage: python3.6
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799851/+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 1750197] Re: App grid animation causes heavy CPU spikes and dropped frames in Wayland & Xorg

[Luke B.]

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

** This bug has been marked a duplicate of bug 1799609
   App Grid "Spring" Animation Increases CPU Usage and Drops Frames

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

Title:
  App grid animation causes heavy CPU spikes and dropped frames in
  Wayland & Xorg

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Upstream Issues:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/349
  https://gitlab.gnome.org/GNOME/mutter/issues/233

  Ubuntu Release: 17.10 and 18.04
  gnome-shell version: 3.28.2
  System Theme: CommuniTheme

  Opening the Applications Overview (App Grid) displays a very janky
  animation, and my CPU will spike to nearly 90% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall higher impact on resource usage.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1750197/+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 1799609] [NEW] App Grid "Spring" Animation Increases CPU Usage and Drops Frames

[Luke B.]

Public bug reported:

[This is a new report to reflect latest information, considering
previous issue report was submitted two cycles ago]

Opening the Applications Overview (App Grid) displays a janky animation.
Seemingly worse depending on number of application icons being
displayed, this issue will also instantly cause 2 CPU spikes. Differing
hardware configurations will see more/less pronounced results; however,
it is present to some extent on nearly every machine. It will happen
regardless of using the default XOrg or Wayland. This bug is worse on
lower-powered machines, with a 2014 Celeron CPU taking a 65-70% hit with
no other applications open.

Work is being done upstream to squash this very complex bug.
https://gitlab.gnome.org/GNOME/gnome-shell/issues/349
https://gitlab.gnome.org/GNOME/mutter/issues/233
https://gitlab.gnome.org/GNOME/mutter/issues/232

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 23 19:20:44 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2018-10-23 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug cosmic

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

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

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

** Description changed:

  [This is a new report to reflect latest information, considering
  previous issue report was submitted two cycles ago]
  
  Opening the Applications Overview (App Grid) displays a janky animation.
  Seemingly worse depending on number of application icons being
  displayed, this issue will also instantly cause 2 CPU spikes. Differing
  hardware configurations will see more/less pronounced results; however,
  it is present to some extent on nearly every machine. It will happen
  regardless of using the default XOrg or Wayland. This bug is worse on
  lower-powered machines, with a 2014 Celeron CPU taking a 65-70% hit with
  no other applications open.
  
  Work is being done upstream to squash this very complex bug.
+ https://gitlab.gnome.org/GNOME/gnome-shell/issues/349
+ https://gitlab.gnome.org/GNOME/mutter/issues/233
+ https://gitlab.gnome.org/GNOME/mutter/issues/232
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 23 19:20:44 2018
  DisplayManager: gdm3
  GsettingsChanges:
-  b'org.gnome.shell' b'command-history' redacted by apport
-  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
-  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.shell' b'command-history' redacted by apport
+  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-10-23 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  App Grid "Spring" Animation Increases CPU Usage and Drops Frames

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  [This is a new report to reflect latest information, considering
  previous issue report was submitted two cycles ago]

  Opening the Applications Overview (App Grid) displays a janky
  animation. Seemingly worse depending on number of application icons
  being displayed, this issue will also instantly cause 2 CPU spikes.
  Differing hardware configurations will see more/less pronounced
  results; however, it is present to some extent 

[Desktop-packages] [Bug 1485955]

[Luke]

With all the interest and dupes this would make a good 100 paper cuts
project.

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

Title:
  [upstream] EDITING: Background Color button from Table toolbar should
  change cell background instead of paragraph background

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
 1. Launch LibreOffice Writer
 2. Insert table to the new document (Table -> Insert -> Table)
 3. Write some multirow text in table cells
 4. Try to change cell background:
4.1. place cursor on desired cell
4.2. select color from palette from "Background Color" drop-down 
(located on Table toolbar).
4.3. click "Background Color" button on Table toolbar.

  Expected results:
 background color of TABLE CELL (where cursor was) is changed to desired 
color.

  Actual results:
 background color of TEXT PARAGRAPH (where cursor was) is changed to 
desired color.

  Workaround:
 There is slow non-intuitive background - select whole cell, select color 
from palette from "Background Color" drop-down (located on Table toolbar), 
click "Background Color" button on Table toolbar.

  Affected versions:
 LibreOffice 3.5.7.2  Build ID: 350m1(Build:2) = pre-installed Ubuntu 
12.04.5 LTS version;
 LibreOffice 4.2.7.2  Build ID: 420m0(Build:2) = pre-installed Ubuntu 
14.04.2 LTS version;
 LibreOffice 4.4.2.2  Build ID: 40m0(Build:2) = pre-installed Ubuntu 15.04 
version.

  
  Comment:
 I can't believe how this bug is possible. It is inherited from OO.org (I 
saw it on OO.org 3.2 in Ubuntu 10.04.4 LTS too).
 Microsoft Word 2003 and 2007 of course have normal behaviour with cell 
background.
 I attached pdf document with screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice 1:3.5.7-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-61.100~precise1-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  Date: Tue Aug 18 11:45:50 2015
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1485955/+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 1787863] Re: gnome-control-center occasionally fails to launch after multiple tries

[Luke B.]

Research leads me to believe this should be an upstream bug.

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

Title:
  gnome-control-center occasionally fails to launch after multiple tries

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

Bug description:
  Release: Ubuntu 18.04.1 LTS
  Package Version: 1:3.28.2-0ubuntu0.18.04.1
  Expected Behavior: Program should always launch upon request.
  Problematic Behavior: Attempting to launch this program causes the shell to 
display the loading indicator for an unusual amount of time, only to never 
display the program.

  Description: Upon launching this program through a terminal emulator,
  it never opens and never displays any output. Passing the verbose (-v)
  option with the program has the same result. When I launch it through
  the GUI, the shell displays the spinning circle (loading indicator)
  for an absurd amount of time. The program still does not open. This is
  a fresh install, so I restarted my computer. When launched again, the
  program opened and operated normally. However, upon closing the
  program and opening it again, it does not open up. Task management
  tools only show the process for a brief 3-5 seconds after requesting
  it to open and then it disappears. To my knowledge, this bug does not
  affect any other programs.

  Workaround:
  Entering the command
   killall gnome-control-center
  allows it to open again upon next launches.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Aug 19 18:17:37 2018
  InstallationDate: Installed on 2018-08-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1787863/+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 1787863] [NEW] gnome-control-center occasionally fails to launch after multiple tries

[Luke B.]

Public bug reported:

Release: Ubuntu 18.04.1 LTS
Package Version: 1:3.28.2-0ubuntu0.18.04.1
Expected Behavior: Program should always launch upon request.
Problematic Behavior: Attempting to launch this program causes the shell to 
display the loading indicator for an unusual amount of time, only to never 
display the program.

Description: Upon launching this program through a terminal emulator, it
never opens and never displays any output. Passing the verbose (-v)
option with the program has the same result. When I launch it through
the GUI, the shell displays the spinning circle (loading indicator) for
an absurd amount of time. The program still does not open. This is a
fresh install, so I restarted my computer. When launched again, the
program opened and operated normally. However, upon closing the program
and opening it again, it does not open up. Task management tools only
show the process for a brief 3-5 seconds after requesting it to open and
then it disappears. To my knowledge, this bug does not affect any other
programs.

Workaround:
Entering the command
 killall gnome-control-center
allows it to open again upon next launches.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Sun Aug 19 18:17:37 2018
InstallationDate: Installed on 2018-08-19 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  gnome-control-center occasionally fails to launch after multiple tries

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

Bug description:
  Release: Ubuntu 18.04.1 LTS
  Package Version: 1:3.28.2-0ubuntu0.18.04.1
  Expected Behavior: Program should always launch upon request.
  Problematic Behavior: Attempting to launch this program causes the shell to 
display the loading indicator for an unusual amount of time, only to never 
display the program.

  Description: Upon launching this program through a terminal emulator,
  it never opens and never displays any output. Passing the verbose (-v)
  option with the program has the same result. When I launch it through
  the GUI, the shell displays the spinning circle (loading indicator)
  for an absurd amount of time. The program still does not open. This is
  a fresh install, so I restarted my computer. When launched again, the
  program opened and operated normally. However, upon closing the
  program and opening it again, it does not open up. Task management
  tools only show the process for a brief 3-5 seconds after requesting
  it to open and then it disappears. To my knowledge, this bug does not
  affect any other programs.

  Workaround:
  Entering the command
   killall gnome-control-center
  allows it to open again upon next launches.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Aug 19 18:17:37 2018
  InstallationDate: Installed on 2018-08-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1787863/+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 1750197] Re: App drawer animation causes heavy CPU spikes in Wayland & Xorg

[Luke B.]

The upstream bugs related to this issue (found up top) have been
updated, as work is being done upstream.

** Description changed:

- https://gitlab.gnome.org/GNOME/gnome-shell/issues/55
+ Upstream Issues: 
+ https://gitlab.gnome.org/GNOME/mutter/issues/232
+ https://gitlab.gnome.org/GNOME/mutter/issues/233
  
  Ubuntu Release: 17.10 and 18.04
- gnome-shell version: 3.26.2
- System Theme: CommuniTheme Beta
+ gnome-shell version: 3.28.2
+ System Theme: CommuniTheme
  
- Upon navigating through various areas of the system, GUI animations are
- very stuttery. This heavily affects the CPU usage of my device. For
- instance, opening the shell app drawer displays a very janky animation,
- and my CPU will spike to nearly 85% for each open/close. This happens
- regardless of using XOrg or Wayland; however Wayland appears to have an
- overall lower impact on resource usage. The CPU in this laptop isn't the
- greatest (being a 2014 Celeron), but this is noticeably more sluggish
- compared to previous releases like 16.04 and 16.10.
+ Opening the Applications Overview (App Grid) displays a very janky
+ animation, and my CPU will spike to nearly 90% for each open/close. This
+ happens regardless of using XOrg or Wayland; however Wayland appears to
+ have an overall higher impact on resource usage.
  
  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.
  
  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.
  
  ProblemType: Bug
- DistroRelease: Ubuntu 17.10
- Package: gnome-shell 3.26.2-0ubuntu0.1
+ DistroRelease: Ubuntu 18.04
+ Package: gnome-shell 3.28.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- App drawer animation causes heavy CPU spikes in Wayland & Xorg
+ App grid animation causes heavy CPU spikes and dropped frames in Wayland & 
Xorg

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

Title:
  App grid animation causes heavy CPU spikes and dropped frames in
  Wayland & Xorg

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Upstream Issues: 
  https://gitlab.gnome.org/GNOME/mutter/issues/232
  https://gitlab.gnome.org/GNOME/mutter/issues/233

  Ubuntu Release: 17.10 and 18.04
  gnome-shell version: 3.28.2
  System Theme: CommuniTheme

  Opening the Applications Overview (App Grid) displays a very janky
  animation, and my CPU will spike to nearly 90% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall higher impact on resource usage.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1750197/+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 1750197] Re: App drawer animation causes heavy CPU spikes in Wayland & Xorg

[Luke B.]

I very much appreciate the work you have done upstream. I have been
trying to follow along, but I cannot contribute to this particular issue
due to my skillset. Are the upstream changes going to be seen in 18.10
or the existing 18.04 when finalized?

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

Title:
  App drawer animation causes heavy CPU spikes in Wayland & Xorg

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/55

  Ubuntu Release: 17.10 and 18.04
  gnome-shell version: 3.26.2
  System Theme: CommuniTheme Beta

  Upon navigating through various areas of the system, GUI animations
  are very stuttery. This heavily affects the CPU usage of my device.
  For instance, opening the shell app drawer displays a very janky
  animation, and my CPU will spike to nearly 85% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall lower impact on resource usage. The CPU in
  this laptop isn't the greatest (being a 2014 Celeron), but this is
  noticeably more sluggish compared to previous releases like 16.04 and
  16.10.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1750197/+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 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

So I built a kernel from the Upstream LTS (4.17.3) and tried to apply
the patch, which failed. So I removed it and tried a clean build and was
able to get Xenial to boot up with this kernel. I then decided to
install Bionic and install this kernel on my laptop however, I noticed
that when I downloaded the latest version (as of July 2, 2018) the
laptop display worked. I checked and I am running Bionic with the
4.15.0-24 kernel. I then installed the NVIDIA proprietary drivers and
low and behold the laptop is working. (I had to modify my grub to
include nouveau.modeset=0 since after logging in the display would hang,
but after passing the kernel parameter everything worked out of the
box.)

This is quite amazing! I'm going to check out the ChangeLog to see what
patches you have running on this.

For the most part, things are working normally. I did notice if I try to
go to the TTY1 or TTY2, I get the GNOME login Screen on TTY1 and my
normal desktop on TTY2, but TTY3-6 are standard terminals. The
brightness control keys still do not work, but the touchpad works so far
from initial testing (Haven't tried the 5 finger test on it yet, but 4
fingers works) and the hibernate issue when the lid closes seems to be
fixed since I was able to resume when I opened the laptop and pressed
space bar to turn it back on.

I will continue to test, but we may have a winner winner chicken dinner
for this bug.

Thanks!!

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not login to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1761261/+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 1433774] Re: When double clicking an executable bash script in file manager, it opens in gedit rather than executing

[Luke]

This is a horrible UX issue that will only trip up new users and should
be addressed. Sane defaults, please!

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

Title:
  When double clicking an executable bash script in file manager, it
  opens in gedit rather than executing

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Download https://www.torproject.org/dist/torbrowser/4.0.4/tor-browser-
  linux64-4.0.4_en-US.tar.xz and extract it to a folder.

  Navigate to that folder in the GNOME file manager.

  Double click "start-tor-browser".

  Expected result: The script executes and launches the browser.

  Actual result: The script opens in gedit. Even when right clicking it,
  "Run" is not listed as an option anywhere. It's not even an option
  under "Open With... -> Other Application". The only way to run it is
  from a terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.7
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 18 16:00:48 2015
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-03-06 (12 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1433774/+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 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

Trackpad and Graphics work with the spth-pincntrl-fix.diff patch on the
4.17 kernel, however, the wifi card does not work, and if you close the
lid or it goes to hibernate, the system becomes unresponsive.

I removed this kernel and am working again on the 4.15.0-20 kernel with
the patch.

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not login to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1761261/+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 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

[1] https://wiki.ubuntu.com/KernelTeam/GitKernelBuild

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not login to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1761261/+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 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

I tried testing with the latest RC build of the 4.17 kernel from kernel.org 
(Torvald's GIT) and built the kernel following the instructions here [1].
After installing the kernel and headers, it looks like it regressed and the 
display did not work (backlight) and I could not switch terminals. I was able 
to reboot my laptop and switch the the previous kernel. My next test will be 
with the patches and see what happens.

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not login to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1761261/+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 1767098] [NEW] Tonga PRO [Radeon R9 285/380] HDMI output always "disconnected"

[Luke Carrier]

Public bug reported:

On a fresh installation of Ubuntu 18.04, both DVI outputs on the back of
the card function as expected but it is not possible to enable the HDMI
output.

I can reliably reproduce the issue under both X and Wayland.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 26 11:22:57 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Tonga PRO [Radeon R9 
285/380] [1462:2015]
InstallationDate: Installed on 2018-04-26 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V
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.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1767098

Title:
  Tonga PRO [Radeon R9 285/380] HDMI output always "disconnected"

Status in xorg package in Ubuntu:
  New

Bug description:
  On a fresh installation of Ubuntu 18.04, both DVI outputs on the back
  of the card function as expected but it is not possible to enable the
  HDMI output.

  I can reliably reproduce the issue under both X and Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 26 11:22:57 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Tonga PRO [Radeon R9 
285/380] [1462:2015]
  InstallationDate: Installed on 2018-04-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V
  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 

[Desktop-packages] [Bug 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

So I patched the 4.15.0-15-generic kernel from kernel.ubuntu.com with
the supplied patch and then intstalled the kernel on my 16.04 xenail
laptop and everything works as it should. The display came up, the touch
pad is responsive and working normally. I have enclosed my dumps of
lswh, lspci, lsmod and my cmdline output.

How I installed this:
I build a bionic container on my laptop:
lxc launch ubuntu-daily:bionic kernel
lxc file push spth-pinctrl-fix.diff kernel/root/
lxc exec kernel bash
apt update && apt upgrade -y
apt build-dep linux-image-`uname -r`
apt install fakeroot
git clone git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
cd ubuntu-bionic
cp ../spth-pinctrl-fix.diff .
patch -p1 < spth-pintctrl-fix.diff
fakeroot debian/rules clean
fakeroot debian/rules binary-headers binary-generic binary-perarch

After the build and the output of the deb files:
exit
mkdir ~/kernel-test
cd ~/kernel-test
lxc file pull kernel/root/linux-image-4.15.0-15-generic_4.15.0-15.16_amd64.deb .
lxc file pull 
kernel/root/linux-image-extra-4.15.0-15-generic_4.15.0-15.16_amd64.deb .
lxc file pull kernel/root/linux-headers-4.15.0-15_4.15.0-15.16_all.deb . 
lxc file pull 
kernel/root/linux-headers-4.15.0-15-generic_4.15.0-15.16_amd64.deb .

Also, the linux-headers-4.15.0-15 deb depends on libssl1.1, which is
default in Bionic, but not in Xenial, so I had to download that deb file
from here: https://packages.ubuntu.com/bionic/libssl1.1

And then I just used dpkg -i to install the files and reboot the laptop
and it started up properly.

While the laptop display works and the touchpad is responsive and works
properly. there are still issues with the FN+F7/F8 brightness controls,
and the other FN options that should work out of the box, but at least
the display works with the 4.15.0-15 kernel


** Attachment added: "logs.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1761261/+attachment/5125965/+files/logs.tar.gz

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not login to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1761261/+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 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

It could be a backlight issue. I tried with the latest daily-build
(April 16, 2018) and I boot up with the nouveau.modeset=0 kernel param
and it shows the splash screen, and then I hear the login sound, and if
I turn off the lights in my office and look closely, I can see the
display, but it looks like the backlight for the screen is not lit. I
tried adjusting the brightness using the FN+F7/F8 (Which adjust
brightness) and they don't work (They don't work on any other
distribution/Release as well. Only things that work are volume control
and Projector options).

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not login to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1761261/+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 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

I have noticed the same thing. I am running on 16.04 with the HWE 17.10 kernel 
and monitor works.
I installed the bionic 4.14.0-17 kernel and I was able to still use the laptop 
display. I tried the latest Bionic kernel (4.15.0-13) and it does not work.
During testing on another bug (LP:1738263) I tested Artful with the Bionic 
kernel 4.15.0-10 and everything appeared to be working normally with the 
exception that DKMS failed to build the NVIDIA modules due to not being 
compatible with the the header files. However, when you install anything newer, 
the display fails to stay on past the GRUB menu.

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not login to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1761261/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Luke Williams]

I have an Asus ROG GL703VD and have a similar issue. The display shows the ROG 
display, then flashes purple for a second (Grub menu splash before the Ubuntu 
splash logo, which doesn't display on the laptop, but does on the HDMI display) 
then goes blank and never comes online. Even pressing CTRL+ALT+F1-6 does not 
switch between virtual terminals on the laptop display, it does shift on the 
mirrored HDMI display. The only way to get a display is to hook up a monitor to 
the HDMI port and then logging in and setting the display to mirror mode. In 
fact, this is the only way to install Bionic on the device as even booting the 
install media with nouveau blacklisted doesn't work. In previous releases, 
running nouveau.modeset=0 would bring up the display properly and then you 
could install, but with Bionic, this is does not work. Also, installing the 
Bionic kernel in Xenial or Artful creates the same condition for those 
releases.  
I have looked at the logs and settings everywhere, and from what I can tell 
everything appears to be loading properly. Gnome sees both displays when 
connected, but the laptop display remains black.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not login to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1761261/+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 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

** Description changed:

  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able to
  finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
- the account to autologin otherwise I could not loging to the laptop. I
+ the account to autologin otherwise I could not login to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
- installed the nvidia-390 drivers from ppa:graphic-drivers/ppa which
+ installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
  installed, but still no local display.
  
  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.
  
  lspci shows the graphics card and NVIDIA card, and lsmod does show that
  before NVIDIA drivers install, it is using nouveau, asus_wmi, and i915
  for graphcis, and once NVIDIA drivers are install, lsmod only shows i915
  and asus_wmi for graphics while nvidia is used for gpu and 3D, but still
  no display on the laptop.
  
  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.
  
  Please let me know if you need any other information.
  
  Thanks,
  Luke

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not login to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1761261/+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 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

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

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not loging to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphic-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1761261/+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 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

** Attachment added: "lshw.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1761261/+attachment/5101640/+files/lshw.txt

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

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

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not loging to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphic-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1761261/+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 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

** Attachment added: "lsmod_nvidia.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1761261/+attachment/5101641/+files/lsmod_nvidia.txt

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

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

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not loging to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphic-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1761261/+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 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1761261/+attachment/5101642/+files/lspci.txt

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

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

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not loging to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphic-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1761261/+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 1761261] [NEW] nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

Public bug reported:

Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
using 3D) and the installer does not display. I have tried
nouveau.modeset=0 and nomodeset boot options to no avail. I was able to
finally install Bionic by hooking up the laptop to a projector, but
after a reboot, the laptop display still did not work and I had to set
the account to autologin otherwise I could not loging to the laptop. I
then install openssh-server so that I could ssh into the laptop and I
installed the nvidia-390 drivers from ppa:graphic-drivers/ppa which
installed, but still no local display.

In Artful, I could install with the nouveau.modeset=0 and then
installing the proprietary NVIDIA drivers and everything (except
touchpad, LP: 1738263) worked.

lspci shows the graphics card and NVIDIA card, and lsmod does show that
before NVIDIA drivers install, it is using nouveau, asus_wmi, and i915
for graphcis, and once NVIDIA drivers are install, lsmod only shows i915
and asus_wmi for graphics while nvidia is used for gpu and 3D, but still
no display on the laptop.

lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
lspci.txt shows the detected hardware
lshw.txt shows the hardware in the laptop.

Please let me know if you need any other information.

Thanks,
Luke

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: asus display gl703vd nouveau nvidia

** Attachment added: "lsmod_prenvidia.txt"
   
https://bugs.launchpad.net/bugs/1761261/+attachment/5101639/+files/lsmod_prenvidia.txt

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

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

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not loging to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphic-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1761261/+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 1760341] [NEW] Intermittent freeze in display output, XPS 9530 with nouveau

[Luke Carrier]

Public bug reported:

Display output intermittently pauses for approximately a second, causing
the system to appear "stuttery". During freezes mouse input doesn't seem
to be registered and keyboard input is repeated, as though keys are
being held down.

Watching the journal via `journalctl -f`, the following message appears
each time the problem occurs:

Mar 31 20:16:18 luke-ultrabook kernel: nouveau :02:00.0: bus: MMIO write of 
0002 FAULT at 4188ac [ IBUS ]
Mar 31 20:16:27 luke-ultrabook kernel: nouveau :02:00.0: bus: MMIO write of 
0002 FAULT at 4188ac [ IBUS ]

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Mar 31 20:11:01 2018
DistUpgraded: 2018-03-31 16:47:43,480 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05fe]
   Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fe]
InstallationDate: Installed on 2018-01-29 (61 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: Dell Inc. XPS 15 9530
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=58327001-b3e0-4118-a0e6-03e8221a44f2 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to bionic on 2018-03-31 (0 days ago)
dmi.bios.date: 07/30/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: XPS 15 9530
dmi.board.vendor: Dell Inc.
dmi.board.version: A09
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: XPS 15 9530
dmi.product.version: A09
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic false-gpu-hang freeze regression reproducible 
ubuntu wayland-session

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

Title:
  Intermittent freeze in display output, XPS 9530 with nouveau

Status in xorg package in Ubuntu:
  New

Bug description:
  Display output intermittently pauses for approximately a second,
  causing the system to appear "stuttery". During freezes mouse input
  doesn't seem to be registered and keyboard input is repeated, as
  though keys are being held down.

  Watching the journal via `journalctl -f`, the following message
  appears each time the problem occurs:

  Mar 31 20:16:18 luke-ultrabook kernel: nouveau :02:00.0: bus: MMIO write 
of 0002 FAULT at 4188ac [ IBUS ]
  Mar 31 20:16:27 luke-ultrabook kernel: nouveau :02:00.0: bus: MMIO write 
of 0002 FAULT at 4188ac [ IBUS ]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Mar 31 20:11:01 2018
  DistUpgraded: 2018-03-31 16:47:43,480 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05fe]
 Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fe]
  InstallationDate: Installed on 2018-01-29 (61 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - 

[Desktop-packages] [Bug 8949] Re: Opening a deleted 'recent document' results in a new file.

[Luke B.]

I can confirm this issue no longer affects Ubuntu 18.04, as recently
viewed items are removed upon deletion.

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

Title:
  Opening a deleted 'recent document' results in a new file.

Status in GNOME Panel:
  Invalid
Status in GTK+:
  Won't Fix
Status in One Hundred Papercuts:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  http://bugzilla.gnome.org/show_bug.cgi?id=143385

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-panel/+bug/8949/+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 1750197] Re: Activities overview causes heavy CPU spikes in Wayland & Xorg

[Luke B.]

What I did was profile gnome-shell using sysprof, and I found that file
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.5502.0 uses 25.06% of CPU
time by itself. My guess is that it's called/utilized very frequently.
Attached is part of the output that should explain what I'm stating.

Let me know if any more information is necessary.

** Attachment added: "My sysprof findings"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1750197/+attachment/5081778/+files/ProfileOutput_LukeB.txt

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

Title:
  Activities overview causes heavy CPU spikes in Wayland & Xorg

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Release: 17.10 and 18.04
  gnome-shell version: 3.26.2
  System Theme: CommuniTheme Beta

  Upon navigating through various areas of the system, GUI animations
  are very stuttery. This heavily affects the CPU usage of my device.
  For instance, opening the shell app drawer displays a very janky
  animation, and my CPU will spike to nearly 85% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall lower impact on resource usage. The CPU in
  this laptop isn't the greatest (being a 2014 Celeron), but this is
  noticeably more sluggish compared to previous releases like 16.04 and
  16.10.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1750197/+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 1750197] Re: Activities overview causes heavy CPU spikes in Wayland & Xorg

[Luke B.]

Forgive me, but what method did you use to profile the resource usage of
gnome-shell? I would like to see if the root cause you discovered
matches what affects my system.

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

Title:
  Activities overview causes heavy CPU spikes in Wayland & Xorg

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Release: 17.10 and 18.04
  gnome-shell version: 3.26.2
  System Theme: CommuniTheme Beta

  Upon navigating through various areas of the system, GUI animations
  are very stuttery. This heavily affects the CPU usage of my device.
  For instance, opening the shell app drawer displays a very janky
  animation, and my CPU will spike to nearly 85% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall lower impact on resource usage. The CPU in
  this laptop isn't the greatest (being a 2014 Celeron), but this is
  noticeably more sluggish compared to previous releases like 16.04 and
  16.10.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1750197/+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 1750197] Re: Activities overview causes heavy CPU spikes in Wayland & Xorg

[Luke B.]

Just to clarify, the app drawer has this problem as well.

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

Title:
  Activities overview causes heavy CPU spikes in Wayland & Xorg

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Release: 17.10 and 18.04
  gnome-shell version: 3.26.2
  System Theme: CommuniTheme Beta

  Upon navigating through various areas of the system, GUI animations
  are very stuttery. This heavily affects the CPU usage of my device.
  For instance, opening the shell app drawer displays a very janky
  animation, and my CPU will spike to nearly 85% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall lower impact on resource usage. The CPU in
  this laptop isn't the greatest (being a 2014 Celeron), but this is
  noticeably more sluggish compared to previous releases like 16.04 and
  16.10.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1750197/+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 1750197] Re: App Drawer Animation Causes Heavy CPU Spikes in Wayland & XOrg

[Luke B.]

** Description changed:

- Ubuntu Release: 17.10
+ Ubuntu Release: 17.10 and 18.04
  gnome-shell version: 3.26.2
  System Theme: CommuniTheme Beta
  
  Upon navigating through various areas of the system, GUI animations are
  very stuttery. This heavily affects the CPU usage of my device. For
  instance, opening the shell app drawer displays a very janky animation,
  and my CPU will spike to nearly 85% for each open/close. This happens
  regardless of using XOrg or Wayland; however Wayland appears to have an
  overall lower impact on resource usage. The CPU in this laptop isn't the
  greatest (being a 2014 Celeron), but this is noticeably more sluggish
  compared to previous releases like 16.04 and 16.10.
  
  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.
  
  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  App Drawer Animation Causes Heavy CPU Spikes in Wayland & XOrg

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Release: 17.10 and 18.04
  gnome-shell version: 3.26.2
  System Theme: CommuniTheme Beta

  Upon navigating through various areas of the system, GUI animations
  are very stuttery. This heavily affects the CPU usage of my device.
  For instance, opening the shell app drawer displays a very janky
  animation, and my CPU will spike to nearly 85% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall lower impact on resource usage. The CPU in
  this laptop isn't the greatest (being a 2014 Celeron), but this is
  noticeably more sluggish compared to previous releases like 16.04 and
  16.10.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1750197/+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 1750197] Re: App Drawer Animation Causes Heavy CPU Spikes in Wayland & XOrg

[Luke B.]

Yes, it does. When changing the screen brightness in 17.10, the slider
wiggles around rapidly during a slight delay before the brightness
actually adjusts.

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

Title:
  App Drawer Animation Causes Heavy CPU Spikes in Wayland & XOrg

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Release: 17.10
  gnome-shell version: 3.26.2
  System Theme: CommuniTheme Beta

  Upon navigating through various areas of the system, GUI animations
  are very stuttery. This heavily affects the CPU usage of my device.
  For instance, opening the shell app drawer displays a very janky
  animation, and my CPU will spike to nearly 85% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall lower impact on resource usage. The CPU in
  this laptop isn't the greatest (being a 2014 Celeron), but this is
  noticeably more sluggish compared to previous releases like 16.04 and
  16.10.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1750197/+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 1750197] Re: App Drawer Animation Causes Heavy CPU Spikes in Wayland & XOrg

[Luke B.]

Upon further investigation, I can confirm that this issue only affects
the App Drawer. Minimizing and Maximizing windows, and etc are all
buttery smooth.

** Summary changed:

- GUI Animations Cause Heavy CPU Spikes in Wayland & XOrg
+ App Drawer Animation Causes Heavy CPU Spikes in Wayland & XOrg

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

Title:
  App Drawer Animation Causes Heavy CPU Spikes in Wayland & XOrg

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Release: 17.10
  gnome-shell version: 3.26.2
  System Theme: CommuniTheme Beta

  Upon navigating through various areas of the system, GUI animations
  are very stuttery. This heavily affects the CPU usage of my device.
  For instance, opening the shell app drawer displays a very janky
  animation, and my CPU will spike to nearly 85% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall lower impact on resource usage. The CPU in
  this laptop isn't the greatest (being a 2014 Celeron), but this is
  noticeably more sluggish compared to previous releases like 16.04 and
  16.10.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1750197/+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 1750197] [NEW] GUI Animations Cause Heavy CPU Spikes in Wayland & XOrg

[Luke B.]

Public bug reported:

Ubuntu Release: 17.10
gnome-shell version: 3.26.2
System Theme: CommuniTheme Beta

Upon navigating through various areas of the system, GUI animations are
very stuttery. This heavily affects the CPU usage of my device. For
instance, opening the shell app drawer displays a very janky animation,
and my CPU will spike to nearly 85% for each open/close. This happens
regardless of using XOrg or Wayland; however Wayland appears to have an
overall lower impact on resource usage. The CPU in this laptop isn't the
greatest (being a 2014 Celeron), but this is noticeably more sluggish
compared to previous releases like 16.04 and 16.10.

This same issue is still existent, but somewhat less noticeable on my
other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
after opening/closing the app drawer.

Please do not hesitate to follow up with requests for more info, as I
will be happy to help.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Sat Feb 17 19:13:00 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2018-02-17 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful 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/1750197

Title:
  GUI Animations Cause Heavy CPU Spikes in Wayland & XOrg

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Release: 17.10
  gnome-shell version: 3.26.2
  System Theme: CommuniTheme Beta

  Upon navigating through various areas of the system, GUI animations
  are very stuttery. This heavily affects the CPU usage of my device.
  For instance, opening the shell app drawer displays a very janky
  animation, and my CPU will spike to nearly 85% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall lower impact on resource usage. The CPU in
  this laptop isn't the greatest (being a 2014 Celeron), but this is
  noticeably more sluggish compared to previous releases like 16.04 and
  16.10.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1750197/+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 1745539] [NEW] package libsane1 1.0.27-1~experimental3ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

[Luke Brumfield]

Public bug reported:

Description:Ubuntu Bionic Beaver (development branch)
Release:18.04

libsane1:
  Installed: 1.0.27-1~experimental3ubuntu1
  Candidate: 1.0.27-1~experimental3ubuntu1
  Version table:
 *** 1.0.27-1~experimental3ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

Broken after running apt-get update, no other programs appear to be
affected

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libsane1 1.0.27-1~experimental3ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
Date: Thu Jan 25 23:17:52 2018
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2018-01-06 (20 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180101)
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.19.0.4ubuntu1
 apt  1.6~alpha5
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental3ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package libsane1 1.0.27-1~experimental3ubuntu1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  libsane1:
Installed: 1.0.27-1~experimental3ubuntu1
Candidate: 1.0.27-1~experimental3ubuntu1
Version table:
   *** 1.0.27-1~experimental3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Broken after running apt-get update, no other programs appear to be
  affected

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Thu Jan 25 23:17:52 2018
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-06 (20 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180101)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental3ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1745539/+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 1740484] Re: video corruption with amd RX560 and 2k display

[Luke McKee]

ll be right
at the top of the dmesg. Details on my motherboard etc are in the
original post. Yo

[0.00] efi: EFI v2.60 by American Megatrends
[0.00] efi:  ACPI 2.0=0xd48df000  ACPI=0xd48df000  SMBIOS=0xdb92f000  
SMBIOS 3.0=0xdb92e000  ESRT=0xd815b998 
[0.00] random: fast init done
[0.00] SMBIOS 3.0.0 present.
[0.00] DMI: System manufacturer System Product Name/PRIME B350M-A, BIOS 
3401 12/04/2017

Finding exactly what is required to replicate this at your end will be
useful.

Just search amdgpu in the ubuntu bug ticket to see other users who are
suffering.

https://bugs.launchpad.net/ubuntu?field.searchtext=amdgpu=Search%3Alist=NEW%3Alist=INCOMPLETE_WITH_RESPONSE%3Alist=INCOMPLETE_WITHOUT_RESPONSE%3Alist=CONFIRMED%3Alist=TRIAGED%3Alist=INPROGRESS%3Alist=FIXCOMMITTED=_reporter=_dupes=on_patch=_no_package
=

Cheers,

Luke


Среда, 24 января 2018, 16:10 +07:00 от MSI OCSS <msih...@msi.com>:

Ticket:
MSI/AMI EFI-ACPI firmware & MSI GPU SBIOS/ATOMBIOS break AMD Power Play in 
Stable linux - request new firmware builds for me (and others)

Content:
Hi, Sir,
As you know, there are two install file in the AMD  lLinux driver package, 
'amdgpu-pro-install' and 'amdgpu-install', 'amdgpu-pro-install' is for Radeon 
Pro GPU which is for use in workstations, and amdgpu-intall is for all other 
product.
And we are endeavoring to reproduce the fan issue with Linux, although we 
had tried it with Ubuntu, but the fan work fine without any settings.
For gather more information, as you said before, did the issue fix while 
amdgpu.dc=1 enabled? Thanks.


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

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

Title:
  video corruption with amd RX560 and 2k display

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a new PC. Freshly installed ubuntu 17.10

  I get a lot of video corruption on my 2k display. It usually shows up
  as bands of the background image or gnome-shell status bar flickering
  across the display at different vertical positions. Everything works
  fine if I select 'Gnome under X.Org' from the login screen instead of
  wayland.

  GNOME 3.26.2, Linux 4.13, Radeon RX560 using amdgpu, Lenovo l24q-10
  monitor running at 2k (2560x1440@ 59.95Hz).

  There is a Fedora Bug with same info:
  https://bugzilla.redhat.com/show_bug.cgi?id=1417778 with a video
  showing the problem in there.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 29 11:06:18 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: Sapphire Technology Limited Baffin [Radeon RX 560] [1da2:e348]
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=2452d0da-14e9-4f88-9660-5a86aee79ff4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3401
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3401:bd12/04/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xse

[Desktop-packages] [Bug 1733158] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

[Luke]

Public bug reported:

Method
~~
1.) Follow instructions on https://wiki.winehq.org/Ubuntu to install WINE 
STAGING
2.) Error occurred installing.
3.) Use the following command: sudo apt-get install -f


Expected Results

Wine to install correctly without any hassle


Actual Results
~~
Error when installing + being asked to submit a bug report

Please see attached file for terminal output

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.4
Architecture: amd64
Date: Sun Nov 19 18:48:44 2017
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-uc5f8z/141-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2017-11-09 (9 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

** Attachment added: "Terminal Output"
   
https://bugs.launchpad.net/bugs/1733158/+attachment/5011199/+files/Terminal%20Output%20for%20Ubuntu%20Error

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Method
  ~~
  1.) Follow instructions on https://wiki.winehq.org/Ubuntu to install WINE 
STAGING
  2.) Error occurred installing.
  3.) Use the following command: sudo apt-get install -f

  
  Expected Results
  
  Wine to install correctly without any hassle

  
  Actual Results
  ~~
  Error when installing + being asked to submit a bug report

  Please see attached file for terminal output

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  Date: Sun Nov 19 18:48:44 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-uc5f8z/141-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-11-09 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1733158/+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 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Luke Faraone]

** Description changed:

- I've found an issue on some of our Xenial office machines, causing
- NetworkManager to drop its IP address lease in some cases when it
- shouldn't. I'm not sure if the actual bug is in NetworkManager or
- perhaps dbus or dhclient, but I'll do my best to help to figure out
- where it is.
+ SRU REQUEST:
+ 
+ Debdiff (nm-dhcp-helper.debdiff) attached.
+ 
+ Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This bug
+ was fixed upstream in 1.4.
+ 
+ [Impact]
+ 
+  * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP
+    lease renewal due to a DBus race condition.
+ 
+  * Upstream NetworkManager 1.4 fixes the race condition by changing
+    nm-dhcp-helper's DBus notification from signal "Event" to method
+    "Notify".
+ 
+  * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix 
to NM 1.2. This SRU request applies that backported patch to Xenial's
+    NM 1.2.x.
+ 
+ [Test Case]
+ 
+  * Not reliably reproducible. Out of hundreds of machines, only a
+    dozen or so fail to notify NetworkManager of a DHCP lease
+    renewal about 30-50% of the time. (i.e. It's always the same
+    handful of machines that fail.)
+ 
+  * All such machines with the patched packages have been fine for weeks,
+    over many dozens of lease renewals.
+ 
+ [Regression Potential]
+ 
+ * The patch changes both nm-dhcp-helper and NetworkManager itself. As
+ soon as the new packages are unpacked, the new nm-dhcp-helper will be
+ used on DHCP lease renewals, with the new Notify mechanism. Since the
+ running, old NetworkManager is still expecting Event notifications, the
+ patched nm-dhcp-helper has fallback capability to Event.
+ 
+ * Once NetworkManager is restarted and is running the patched version,
+ it will have the new Notify support.
+ 
+ [Other Info]
+ 
+  * Upstream bug w/ patch:
+ https://bugzilla.gnome.org/show_bug.cgi?id=784636
+ 
+  * RHEL bug with links to the 1.4 commits from which the patch was
+    derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276
+ 
+  * NOTE:  The final comment on the upstream GNOME bug claims that the
+ fix is incomplete.  However, it is possible that the running
+ NetworkManager was not restarted (see Regression Potential notes above),
+ which is why nm-dhcp-helper is falling back to Event.  The remainder of
+ the log messages in that final comment are from a custom wrapper the
+ submitter was running around nm-dhcp-helper.  I have deployed the exact
+ same patch (without said wrapper) to real-world systems and tested
+ extensively, and see nothing but successful DHCP lease renewal
+ notifications using D-Bus Notify, not D-Bus Event.
+ 
+ 
+ 
+ I've found an issue on some of our Xenial office machines, causing 
NetworkManager to drop its IP address lease in some cases when it shouldn't. 
I'm not sure if the actual bug is in NetworkManager or perhaps dbus or 
dhclient, but I'll do my best to help to figure out where it is.
  
  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.
  
  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').
  
  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager
  reports a new lease with lease time 7200.
  
  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound
  
  After this, dhclient is supposed to keep the lease fresh, which it does.
  E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this
  DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds.
  
  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 

[Desktop-packages] [Bug 1711180] [NEW] Ubuntu 17.10 Artful Ardvark shows Black Window, requires "Force Quit"

[Luke Smith]

Public bug reported:

Installed it fine, but Artful Aardvark Ubuntu 17.10 show just a black
window. Freezes there, and eventually I am prompted to "Wait" or "Force
Quit".  If I don't force quit it stays black all day.

Here are my results:

LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID: Ubuntu
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10
Codename:   artful

name:  chromium
summary:   "Chromium web browser, open-source version of Chrome"
publisher: osomon
contact:   olivier.til...@canonical.com
description: |
  An open-source browser project that aims to build a safer, faster, and more
  stable way for all Internet users to experience the web.
commands:
  - chromium
notes: 
  private: false
  confinement: strict
  devmode: false
  jailmode:false
  trymode: false
  enabled: true
  broken:  false
tracking:  candidate
installed: 60.0.3112.101 (5) 151MB 
refreshed: 2017-08-15 10:17:57 -0400 EDT
channels:
  stable:  –   
  candidate:   60.0.3112.101 (5) 151MB -
  beta:61.0.3163.39  (1) 151MB -
  edge:↑   
---
name:  core
summary:   "snapd runtime environment"
publisher: canonical
contact:   snappy-canonical-storeacco...@canonical.com
description: |
  The core runtime environment for snapd
type:  core
notes: 
  private: false
  confinement: strict
  devmode: false
  jailmode:false
  trymode: false
  enabled: true
  broken:  false
tracking:  stable
installed: 16-2.26.14 (2462) 84MB 
refreshed: 2017-07-20 08:45:34 -0400 EDT
channels:  
  stable:  16-2.26.14   (2462) 84MB -
  candidate:   16-2.27  (2601) 85MB -
  beta:16-2.27.2(2677) 85MB -
  edge:16-2.27.1+git322.46fa975 (2671) 86MB -

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: snap

** Tags added: snap

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

Title:
  Ubuntu 17.10 Artful Ardvark shows Black Window, requires "Force Quit"

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Installed it fine, but Artful Aardvark Ubuntu 17.10 show just a black
  window. Freezes there, and eventually I am prompted to "Wait" or
  "Force Quit".  If I don't force quit it stays black all day.

  Here are my results:

  LSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Codename: artful

  name:  chromium
  summary:   "Chromium web browser, open-source version of Chrome"
  publisher: osomon
  contact:   olivier.til...@canonical.com
  description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
  commands:
- chromium
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  candidate
  installed: 60.0.3112.101 (5) 151MB 
  refreshed: 2017-08-15 10:17:57 -0400 EDT
  channels:
stable:  –   
candidate:   60.0.3112.101 (5) 151MB -
beta:61.0.3163.39  (1) 151MB -
edge:↑   
  ---
  name:  core
  summary:   "snapd runtime environment"
  publisher: canonical
  contact:   snappy-canonical-storeacco...@canonical.com
  description: |
The core runtime environment for snapd
  type:  core
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  stable
  installed: 16-2.26.14 (2462) 84MB 
  refreshed: 2017-07-20 08:45:34 -0400 EDT
  channels:  
stable:  16-2.26.14   (2462) 84MB -
candidate:   16-2.27  (2601) 85MB -
beta:16-2.27.2(2677) 85MB -
edge:16-2.27.1+git322.46fa975 (2671) 86MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1711180/+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 555212] Re: package flashplugin-nonfree 10.0.1.218 really9.0.262.0ubuntu1 failed to install/upgrade: Package is in a very bad inconsistent state - you should reinstall it befor

[Luke Robbie]

** This bug is no longer a duplicate of bug 429841
   broken packaging: package flashplugin-nonfree failed to install/upgrade: 
(breaks upgrade)

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

Title:
  package flashplugin-nonfree 10.0.1.218 really9.0.262.0ubuntu1 failed
  to install/upgrade: Package is in a very bad inconsistent state - you
  should  reinstall it before attempting a removal.

Status in flashplugin-nonfree package in Ubuntu:
  New

Bug description:
  Binary package hint: flashplugin-nonfree

  Problem started while upgrading from 8.04.1 to 9.10.  Original version
  of  flashplugin-nonfree had an issue & all attempts to correct failed.
  Unable to even re-install with Synaptic.  Need a clean copy for
  install, I think.  Need your help.  I'm primarily a hardware tech.

  ProblemType: Package
  AptOrdering:
   flashplugin-nonfree: Remove
   flashplugin-installer: Install
   flashplugin-nonfree: Install
   flashplugin-installer: Configure
   flashplugin-nonfree: Configure
  Architecture: amd64
  Date: Mon Apr  5 01:20:21 2010
  DistroRelease: Ubuntu 9.10
  ErrorMessage: Package is in a very bad inconsistent state - you should  
reinstall it before attempting a removal.
  LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  Package: flashplugin-nonfree 10.0.1.218+really9.0.262.0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
  SourcePackage: flashplugin-nonfree
  Title: package flashplugin-nonfree 10.0.1.218+really9.0.262.0ubuntu1 failed 
to install/upgrade: Package is in a very bad inconsistent state - you should  
reinstall it before attempting a removal.
  Uname: Linux 2.6.31-20-generic x86_64
  XsessionErrors:
   (nautilus:5956): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table 
still has 2 elements at quit time (keys above)
   (nautilus:5956): Eel-WARNING **: "nautilus-directory.c: directories" hash 
table still has 2 elements at quit time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/555212/+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 1670933] Re: Accessibility partly broken due to X root window being kept from login session.

[Luke Yelavich]

** Project changed: lightdm => lightdm-gtk-greeter

** Changed in: lightdm-gtk-greeter
 Assignee: (unassigned) => Luke Yelavich (themuso)

** Also affects: unity-greeter (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity-greeter (Ubuntu)
 Assignee: (unassigned) => Luke Yelavich (themuso)

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

Title:
  Accessibility partly broken due to X root window being kept from login
  session.

Status in LightDM GTK+ Greeter:
  New
Status in unity-greeter package in Ubuntu:
  New

Bug description:
   affects lightdm

  Lightdm version 1.21.5, in 17.04. Some components of the Unity and
  Mate desktops are currently not accessible when logging in using
  lightdm. So far I've tested and reproduced this problem with both
  unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I
  mentioned in the title, i.e the X root window is kept around.

  At-spi gets loaded in the greeter for use with Orca. At-spi ads a
  property atom, AT_SPI_BUS, to the root X window to allow software to
  be able to find the accessibility bus. If my understanding is correct,
  this root window is kept around for the user login session. What then
  happens is software either using Qt or Gtk loads its accessibility
  support code, which in turn looks for the AT_SPI_BUS property.
  Normally on session load, this property is not present, at which point
  the support code then connects to org.a11y.bus, which in turn via
  systemd loads the at-spi bus launcher and registry to respond to the
  bus activation/request. At-spi adds the AT_SPI_BUS property to the X
  root window at load.

  However the AT_SPI_BUS property is hanging around from the greeter
  session, which is confusing software. At-spi only then gets loaded
  from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome
  session binaries, but this happens after unity-panel-service and mate-
  panel are loaded. As such they are inaccessible for the session, or
  until the user kills them and they get reloaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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 1697717] [NEW] Don't default to storing podcasts in ~

[Luke picciau]

Public bug reported:

I added some podcasts to rhythmbox and found they were being stored in
my home directory and not in a directory like ~/podcasts. This quickly
makes a mess of my home directory.

I found this bug
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/62400 which has
been marked as resolved a long time ago but I am still having this issue
on a new install with the default settings for rhythmbox.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: rhythmbox 3.3-1ubuntu7
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jun 14 00:34:50 2017
InstallationDate: Installed on 2017-05-13 (31 days ago)
InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Don't default to storing podcasts in ~

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  I added some podcasts to rhythmbox and found they were being stored in
  my home directory and not in a directory like ~/podcasts. This quickly
  makes a mess of my home directory.

  I found this bug
  https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/62400 which
  has been marked as resolved a long time ago but I am still having this
  issue on a new install with the default settings for rhythmbox.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rhythmbox 3.3-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun 14 00:34:50 2017
  InstallationDate: Installed on 2017-05-13 (31 days ago)
  InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1697717/+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 1691420] Re: package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in pack

[Luke picciau]

Looks like this could have been caused by installing KDE and then gnome

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

Title:
  package account-plugin-google (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/share/accounts/providers/google.provider', which is also in
  package kaccounts-providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  Not quite sure what triggered this bug

  Description:Ubuntu 16.04.2 LTS
  Release:16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat May 13 22:35:12 2017
  DuplicateSignature:
   package:account-plugin-google:(not installed)
   Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2017-05-13 (4 days ago)
  InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: account-plugins
  Title: package account-plugin-google (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1691420/+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 1691420] [NEW] package account-plugin-google (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in pa

[Luke picciau]

Public bug reported:

Not quite sure what triggered this bug

Description:Ubuntu 16.04.2 LTS
Release:16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: account-plugin-google (not installed)
ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sat May 13 22:35:12 2017
DuplicateSignature:
 package:account-plugin-google:(not installed)
 Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
  trying to overwrite '/usr/share/accounts/providers/google.provider', which is 
also in package kaccounts-providers 4:15.12.3-0ubuntu1
ErrorMessage: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
InstallationDate: Installed on 2017-05-13 (4 days ago)
InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: account-plugins
Title: package account-plugin-google (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/accounts/providers/google.provider', which is 
also in package kaccounts-providers 4:15.12.3-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict xenial

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

Title:
  package account-plugin-google (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/share/accounts/providers/google.provider', which is also in
  package kaccounts-providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  Not quite sure what triggered this bug

  Description:Ubuntu 16.04.2 LTS
  Release:16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat May 13 22:35:12 2017
  DuplicateSignature:
   package:account-plugin-google:(not installed)
   Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2017-05-13 (4 days ago)
  InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: account-plugins
  Title: package account-plugin-google (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/providers/google.provider', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1691420/+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 1689167] Re: seahorse hangs with ykcs11 module loaded

[Luke Faraone]

Appears to be a conflict between opensc and ykcs11 -- both are buggy :(

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

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

Title:
  seahorse hangs with ykcs11 module loaded

Status in seahorse package in Ubuntu:
  Invalid

Bug description:
  With a YubiKey IV Nano inserted with PIV enabled, starting Seahorse
  with ykcs11 installed and added to the user's p11-kit config, Seahorse
  hangs.

  Contents of ~/.config/pkcs11/modules/ykcs11.module:

  module: /usr/lib/x86_64-linux-gnu/libykcs11.so

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: seahorse 3.20.0-3.1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun May  7 11:24:13 2017
  ExecutablePath: /usr/bin/seahorse
  InstallationDate: Installed on 2017-04-09 (27 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: seahorse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1689167/+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 1689167] [NEW] seahorse hangs with ykcs11 module loaded

[Luke Faraone]

Public bug reported:

With a YubiKey IV Nano inserted with PIV enabled, starting Seahorse with
ykcs11 installed and added to the user's p11-kit config, Seahorse hangs.

Contents of ~/.config/pkcs11/modules/ykcs11.module:

module: /usr/lib/x86_64-linux-gnu/libykcs11.so

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: seahorse 3.20.0-3.1
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Sun May  7 11:24:13 2017
ExecutablePath: /usr/bin/seahorse
InstallationDate: Installed on 2017-04-09 (27 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: seahorse
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

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

Title:
  seahorse hangs with ykcs11 module loaded

Status in seahorse package in Ubuntu:
  New

Bug description:
  With a YubiKey IV Nano inserted with PIV enabled, starting Seahorse
  with ykcs11 installed and added to the user's p11-kit config, Seahorse
  hangs.

  Contents of ~/.config/pkcs11/modules/ykcs11.module:

  module: /usr/lib/x86_64-linux-gnu/libykcs11.so

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: seahorse 3.20.0-3.1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun May  7 11:24:13 2017
  ExecutablePath: /usr/bin/seahorse
  InstallationDate: Installed on 2017-04-09 (27 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: seahorse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1689167/+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 1532544] Re: Window becomes unresponsive and sound stops when skipping to next track

[Luke picciau]

I haven't had this issue in a long time. Maybe it has been fixed?

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

Title:
  Window becomes unresponsive and sound stops when skipping to next
  track

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  When skipping to the next track rhythmbox will sometimes become
  unresponsive and rapidly send the error

  (rhythmbox:4897): GStreamer-CRITICAL **: gst_poll_write_control:
  assertion 'set != NULL' failed

  (rhythmbox:4897): GStreamer-WARNING **: gstsystemclock: write control
  failed in wakeup_async, trying again: 11:Resource temporarily
  unavailable

  
  to ~/.cache/upstart/indicator-sound.log which takes up most of the CPU and 
quickly fills all hard drive space.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: rhythmbox 3.2.1-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 10 23:04:18 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-26 (168 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to wily on 2015-10-23 (79 days ago)

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

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

Re: [Desktop-packages] [Bug 1684324] [NEW] [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all

[Luke Yelavich]

Try moving your pulseaudio config out of the way. Log out of your
desktop session, switch to a text virtual terminal by pressing control +
alt + f1, logging in there, and moving the pulseaudio config like so:

mv .config/pulse .config/pulse.old

Log out of the text terminal, switch back to the GUI login by pressing
Alt + F7, and then log in as normal, and see how things go.

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

Title:
  [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Upgraded to 17.04 from 16.10 today. Sound worked ok in previous
  versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim1857 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Wed Apr 19 19:36:52 2017
  InstallationDate: Installed on 2015-03-28 (753 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim1857 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (0 days ago)
  dmi.bios.vendor: Dell Inc.
  dmi.board.vendor: Dell Inc.

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

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

Re: [Desktop-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

[Luke Yelavich]

Hui, do you know which patch in the pulseaudio package is responsible
for this revert? A quick glance and I cannot find it.

Luke

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

Re: [Desktop-packages] [Bug 1676232] [NEW] No HDMI 5.1 profile listed for card, only 7.1

[Luke Yelavich]

Could you please get a log from PulseAudio, as outlined here:
https://wiki.ubuntu.com/PulseAudio/Log? Thanks.

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

Title:
  No HDMI 5.1 profile listed for card, only 7.1

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have researched and requested help on Launchpad two times and not had any 
responses what do to next. There is no HDMI 5.1 profile available There is 7.1 
HDMI and it functions perfectly (sans missing channels on a 5.1 audio system). 
Please see below how the profile isn't detected and made available? Please 
direct me to a proper way to fix this. On a fresh install Ubuntu 16.04.2 LTS
  Release:  16.04

  
  Thanks.

  ___1 card(s) available.
  index: 0
name: 
driver: 
owner module: 6
properties:
alsa.card = "0"
alsa.card_name = "HDA Intel"
alsa.long_card_name = "HDA Intel at 0xdf40 irq 33"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "293e"
device.product.name = "82801I (ICH9 Family) HD Audio Controller"
device.form_factor = "internal"
device.string = "0"
device.description = "Built-in Audio"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
input:analog-stereo: Analog Stereo Input (priority 60, 
available: unknown)
output:analog-stereo: Analog Stereo Output (priority 6000, 
available: unknown)
output:analog-stereo+input:analog-stereo: Analog Stereo Duplex 
(priority 6060, available: unknown)
output:iec958-stereo: Digital Stereo (IEC958) Output (priority 
5500, available: unknown)
output:iec958-stereo+input:analog-stereo: Digital Stereo 
(IEC958) Output + Analog Stereo Input (priority 5560, available: unknown)
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 
5400, available: unknown)
output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) 
Output + Analog Stereo Input (priority 5460, available: unknown)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(priority 300, available: unknown)
output:hdmi-surround71+input:analog-stereo: Digital Surround 
7.1 (HDMI) Output + Analog Stereo Input (priority 360, available: unknown)
off: Off (priority 0, available: unknown)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D3p:   fhess  5316 F...m pulseaudio
   /dev/snd/controlC0:  fhess  5316 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Mar 26 19:03:55 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [HP Pavilion dv7 Notebook PC, Nvidia MCP77/78 HDMI, Digital Out, HDMI] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30F4
  dmi.board.vendor: Compal
  dmi.board.version: 99.75
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd10/01/2008:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.13:rvnCompal:rn30F4:rvr99.75:cvnCompal:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-03-26T01:09:33.814682

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

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

Re: [Desktop-packages] [Bug 1667328] Re: Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?) apps

[Luke Yelavich]

Ok, I see pavucontrol changing the volume, and I see the control center
connecting, but I don't see anything about it not being able to change
the microphone volume, same with Chromium. Are you able to change the
microphone volume with the sound indicator?

One thing you could try, is to move your pulseaudio configuration out of
the way temporarily to see if that resolves things. The best time to do
this is when not logged into a graphical session, and do the move in a
console. You want to move ~/.config/pulse out of the way. Once done, try
the control center, and chromium again. No need to test pavucontrol, we
know that its 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/1667328

Title:
  Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?)
  apps

Status in gstreamer package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a Lenovo Thinkpad X1 Carbon (2nd gen, 2014?) running Ubuntu
  Yakkety (16.10). Kernel is the most current one: 4.8.0-39-generic
  #42-Ubuntu

  In the last days the microphone stopped working when I am on the
  Google Hangouts video conference in the Chromium browser. I checked
  the sound settings of the System Settings and on the "input" tab the
  slider for the microphone volume is grayed out and cannot be moved
  away from the zero position. The microphone level monitor bar does not
  move when talking or touching the microphone.

  Then I found the following on the internet

  http://askubuntu.com/questions/508221/sound-input-device-microphone-
  not-working

  and tried to solve the problem following the hints:

  - Reboot does not solve the problem.

  - I could not do any tests with gstreamer-properties as it seems to
  have been removed from gstreamer (what is the successor?).

  - pavucontrol (Pulse Audio Sound Control) shows on its "Input Devices"
  Tab that the microphone of the laptop is OK and that the kernel works
  with it. The Level monitor bar is moving according to environment
  noise and touching of the microphone.

  - "sudo alsa force-reload" does not solve the problem.

  - "sudo apt-get remove --purge alsa-base pulseaudio; sudo apt-get
  install alsa-base pulseaudio ubuntu-desktop" and reboot afterwards
  does not solve the problem.

  - audacity is recording through the microphone correctly.

  - Adding "options snd-hda-intel position_fix=1" to /etc/modprobe.d
  /alsa-base.conf and rebooting does not solve the problem.

  I hope that is a known problem. Please tell me if you need further 
information.
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  till   2897 F pulseaudio
   /dev/snd/controlC1:  till   2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2015-04-30 (686 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: pulseaudio 1:9.0-2ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Tags: yakkety third-party-packages
  Uname: Linux 4.8.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET40WW (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A8X50300
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET40WW(1.17):bd09/02/2014:svnLENOVO:pn20A8X50300:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8X50300:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20A8X50300
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer/+bug/1667328/+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 1627534] Re: Keeps resetting homepage to start.ubuntu-mate.org

[Luke Horwell]

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

It's a duplicate of https://bugs.launchpad.net/ubuntu/+source/ubuntu-
mate-settings/+bug/1605887

The configuration that causes Firefox to set the default home page
resides in the "ubuntu-mate-default-settings" package. You can install
the MATE Desktop on its own, but Ubuntu MATE desktop packages will
require this package too.

** This bug has been marked a duplicate of bug 1605887
   Ubuntu MATE Start page are overriding users' preferences.

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

Title:
  Keeps resetting homepage to start.ubuntu-mate.org

Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-mate-settings package in Ubuntu:
  Confirmed

Bug description:
  Since the Xenial -> Yakkety beta upgrade, firefox resets its homepage
  to https://start.ubuntu-mate.org/ upon each start.

  I use the default Unity 7 desktop, no Mate whatsoever. (I might have
  started up Mate once or twice for a very short period, way before even
  upgrading to Xenial.)

  Happened both with firefox-49 package as shipped by Xenial, as well as
  firefox-48 that's currently in Yakkety beta (I purged and then
  reinstalled the package to get the one matching the distro, rather
  than the latest).

  No startup wrapper script or something like that should mess with my
  preferred homepage, let alone set it to something that is about a
  different desktop than the one I'm using.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 48.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  egmont 2339 F pulseaudio
  BuildID: 20160728202151
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun Sep 25 21:34:07 2016
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-05-30 (1579 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.11  metric 
600
  MostRecentCrashID: bp-02582fc4-8633-4d4a-86cb-814af2140429
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntumate.js
   prefs.js
  Profiles: Profile0 (Default) - LastVersion=48.0/20160728202151 (In use)
  RelatedPackageVersions:
   google-talkplugin 5.41.0.0-1
   icedtea-8-plugin  1.6.2-3ubuntu1
   gnome-shell   3.20.3-1ubuntu2
   rhythmbox-mozilla 3.4.1-1ubuntu1
   browser-plugin-evince 3.22.0-0ubuntu1
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  SubmittedCrashIDs: bp-02582fc4-8633-4d4a-86cb-814af2140429
  UpgradeStatus: Upgraded to yakkety on 2016-09-23 (2 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 03QB
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 300E4Z/300E5Z/300E7Z
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr03QB:bd12/14/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4Z/300E5Z/300E7Z:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300E4Z/300E5Z/300E7Z:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 300E4Z/300E5Z/300E7Z
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

Re: [Desktop-packages] [Bug 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

[Luke Yelavich]

Could you also get a log from PulseAudio as per
https://wiki.ubuntu.com/PulseAudio/Log. 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/1673942

Title:
  pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.

  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.

  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.

  The pulseaudio log collects initial messages, but nothing else is
  echoed to the log - which could be anything from 3-20 minutes
  [typically].

  I'm more than happy to assist in getting whatever logs are required,
  but nothing I've seen documented seems to help.

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

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

Re: [Desktop-packages] [Bug 1673942] Re: pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

[Luke Yelavich]

Please run apport-collect 1673942 in a terminal so we can get some more
information about your hardware.

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

Title:
  pulseaudio suddenly stops. No dmesg entries. Nothing in the syslog

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this only happens when sound is through the PCI sound card. When i
  connect speakers to the motherboard output (I lose the 5.1 component),
  pulseaudio never dies.

  I have switched and replaced the sound card to no effect but I never
  really thought that was the issue.

  There seems to be no evidence of the failure unless I run it from the
  command line with -, when eventually I see a 'killed' message.

  The pulseaudio log collects initial messages, but nothing else is
  echoed to the log - which could be anything from 3-20 minutes
  [typically].

  I'm more than happy to assist in getting whatever logs are required,
  but nothing I've seen documented seems to help.

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

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

Re: [Desktop-packages] [Bug 1667328] Re: Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?) apps

[Luke Yelavich]

Are any of those logs taken from when you are trying to use the
microphone or when you try and adjust the settings for it in control-
center?

If not, try getting a log when trying to use both pavucontrol and unity-
control-center to change microphone settings, since you did indicate
that pavucontrol was at least showing something.

Could you also run apport-collect 1667328 so I can get some info about
your actual hardware?

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

Title:
  Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?)
  apps

Status in gstreamer package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a Lenovo Thinkpad X1 Carbon (2nd gen, 2014?) running Ubuntu
  Yakkety (16.10). Kernel is the most current one: 4.8.0-39-generic
  #42-Ubuntu

  In the last days the microphone stopped working when I am on the
  Google Hangouts video conference in the Chromium browser. I checked
  the sound settings of the System Settings and on the "input" tab the
  slider for the microphone volume is grayed out and cannot be moved
  away from the zero position. The microphone level monitor bar does not
  move when talking or touching the microphone.

  Then I found the following on the internet

  http://askubuntu.com/questions/508221/sound-input-device-microphone-
  not-working

  and tried to solve the problem following the hints:

  - Reboot does not solve the problem.

  - I could not do any tests with gstreamer-properties as it seems to
  have been removed from gstreamer (what is the successor?).

  - pavucontrol (Pulse Audio Sound Control) shows on its "Input Devices"
  Tab that the microphone of the laptop is OK and that the kernel works
  with it. The Level monitor bar is moving according to environment
  noise and touching of the microphone.

  - "sudo alsa force-reload" does not solve the problem.

  - "sudo apt-get remove --purge alsa-base pulseaudio; sudo apt-get
  install alsa-base pulseaudio ubuntu-desktop" and reboot afterwards
  does not solve the problem.

  - audacity is recording through the microphone correctly.

  - Adding "options snd-hda-intel position_fix=1" to /etc/modprobe.d
  /alsa-base.conf and rebooting does not solve the problem.

  I hope that is a known problem. Please tell me if you need further
  information.

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

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

Re: [Desktop-packages] [Bug 1671556] [NEW] [bytcr-rt5640 - bytcr-rt5640, playback] Pulseaudio fails to detect card

[Luke Yelavich]

Could you plesae get a log from PulseAudio as outlined here:
https://wiki.ubuntu.com/PulseAudio/Log.

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

Title:
  [bytcr-rt5640 - bytcr-rt5640, playback] Pulseaudio fails to detect
  card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a quantum byte Intel® Atom™ CPU Z3735F @ 1.33GHz × 4 Intel® Bay
  Trail 64-bit

  the audio shows as dummy input

  
  OS is ubuntu 16.10

  I followed the help file and this is the screen text (below)

  any help or direction would be appreciated


  
  steve@elmoviii:~$ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: bytcrrt5640 [bytcr-rt5640], device 0: Baytrail Audio (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: bytcrrt5640 [bytcr-rt5640], device 1: Deep-Buffer Audio (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  steve@elmoviii:~$ sudo lspci
  [sudo] password for steve: 
  00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
SoC Transaction Register (rev 0f)
  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Graphics & Display (rev 0f)
  00:03.0 Multimedia controller: Intel Corporation Atom Processor Z36xxx/Z37xxx 
Series Camera ISP (rev 0f)
  00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, 
Celeron N2000 Series USB xHCI (rev 0f)
  00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx 
Series Trusted Execution Engine (rev 0f)
  00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Power Control Unit (rev 0f)
  steve@elmoviii:~$ sudo lspci -v
  00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
SoC Transaction Register (rev 0f)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC 
Transaction Register
Flags: bus master, fast devsel, latency 0
Kernel driver in use: iosf_mbi_pci

  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Graphics & Display (rev 0f) (prog-if 00 [VGA controller])
DeviceName:  Onboard IGD
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display
Flags: bus master, fast devsel, latency 0, IRQ 262
Memory at 9040 (32-bit, non-prefetchable) [size=4M]
Memory at 8000 (32-bit, prefetchable) [size=256M]
I/O ports at 1000 [size=8]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [d0] Power Management version 2
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [b0] Vendor Specific Information: Len=07 
Kernel driver in use: i915
Kernel modules: i915

  00:03.0 Multimedia controller: Intel Corporation Atom Processor Z36xxx/Z37xxx 
Series Camera ISP (rev 0f)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Camera 
ISP
Flags: bus master, fast devsel, latency 0
Memory at 9000 (32-bit, non-prefetchable) [size=4M]
Capabilities: [80] Power Management version 2
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-

  00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, 
Celeron N2000 Series USB xHCI (rev 0f) (prog-if 30 [XHCI])
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron 
N2000 Series USB xHCI
Flags: bus master, medium devsel, latency 0, IRQ 261
Memory at 90c0 (64-bit, non-prefetchable) [size=64K]
Capabilities: [70] Power Management version 2
Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
Kernel driver in use: xhci_hcd

  00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx 
Series Trusted Execution Engine (rev 0f)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Trusted Execution Engine
Flags: bus master, fast devsel, latency 0, IRQ 263
Memory at 90b0 (32-bit, non-prefetchable) [size=1M]
Memory at 90a0 (32-bit, non-prefetchable) [size=1M]
Capabilities: [80] Power Management version 3
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit-
Kernel driver in use: mei_txe
Kernel modules: mei_txe

  00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Power Control Unit (rev 0f)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power 
Control Unit
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0c 
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: 

[Desktop-packages] [Bug 1670022] [NEW] Pulseaudio volume master breaks after plugging in headphones

[Luke Schlather]

Public bug reported:

The only way I've found to restore it is by rebooting. I can control the
volume with amixer, and pavucontrol's per-application sliders work fine,
but the master in pavucontrol doesn't work. (So naturally the volume
keys don't work either.)

** Affects: xubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: alsa-utils (Ubuntu) => xubuntu-meta (Ubuntu)

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

Title:
  Pulseaudio volume master breaks after plugging in headphones

Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  The only way I've found to restore it is by rebooting. I can control
  the volume with amixer, and pavucontrol's per-application sliders work
  fine, but the master in pavucontrol doesn't work. (So naturally the
  volume keys don't work either.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1670022/+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 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()

[Luke Yelavich]

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

** Also affects: pulseaudio via
   https://bugs.freedesktop.org/show_bug.cgi?id=65520
   Importance: Unknown
   Status: Unknown

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

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

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

Re: [Desktop-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

[Luke Yelavich]

affects ubuntu/pulseaudio
 status invalid

Ok, closing for now. Feel free to re-open if this crops up again.


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

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

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.

  Got an other crash, and that time 'sound' is fully lost (pulseaudio
  not reloaded). Wonder if lp:1662860 can be concerned.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

Re: [Desktop-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

[Luke Yelavich]

After making the changes you made, are you still getting crashes?

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

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.

  Got an other crash, and that time 'sound' is fully lost (pulseaudio
  not reloaded). Wonder if lp:1662860 can be concerned.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

Re: [Desktop-packages] [Bug 1662147] Re: Cannot stop pulseaudio

[Luke Yelavich]

Do you have pulseaudio-module-jack installed? I believe that includes a
module that will talk to jack and have pulse move out of the way, and
reroute itself through jack.

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

Title:
  Cannot stop pulseaudio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I need to kill pulseaudio as I'm using Jackd instead. I don't want to
  delete it as I may need it back again.

  So far the only workaround I found was to delete /usr/bin/pulseaudio
  (or move it out of the way).

  
  norru@GBWWSRUNUBWS02:~$ pulseaudio -k
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru29938  8557  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru29940 29938  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru29941 29940  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30111 29396  0 11:27 pts/000:00:00 grep --color=auto pulse
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru29938  8557  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru29940 29938  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru29941 29940  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30230 29396  0 11:27 pts/000:00:00 grep --color=auto pulse
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru29938  8557  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru29940 29938  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru29941 29940  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30250 28914  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30252 28942  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30297 29396  0 11:27 pts/000:00:00 grep --color=auto pulse
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru29941 1  1 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30469 29396  0 11:27 pts/000:00:00 grep --color=auto pulse
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru29941 1  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30486 29396  0 11:27 pts/000:00:00 grep --color=auto pulse
  norru@GBWWSRUNUBWS02:~$ pulseaudio -k
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru30489 29396  0 11:27 pts/000:00:00 grep --color=auto pulse
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru30493 1  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru30506 29396  0 11:27 pts/000:00:00 grep --color=auto pulse
  norru@GBWWSRUNUBWS02:~$ ubuntu-bug pulseaudio

  norru@GBWWSRUNUBWS02:~$ sudo service pulseaudio stop
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru30493 1  0 11:27 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog

  norru@GBWWSRUNUBWS02:~$ kill 30493
  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru32318 1  1 11:32 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog

  
  norru@GBWWSRUNUBWS02:~$ kill -9 32318

  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru32361  8557  0 11:34 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru32363 32361  0 11:34 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru32364 32363  1 11:34 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog

  norru@GBWWSRUNUBWS02:~$ ps -ef | grep pulse
  norru32364 1  1 11:34 ?00:00:00 /usr/bin/pulseaudio --start 
--log-target=syslog
  norru32381 29396  0 11:34 pts/000:00:00 grep --color=auto pulse

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  norru 30493 F pulseaudio
   /dev/snd/controlC0:  norru 30493 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Feb  6 11:28:49 2017
  InstallationDate: Installed on 2015-06-10 (606 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (97 days ago)
  dmi.bios.date: 10/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4502
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  

Re: [Desktop-packages] [Bug 1658528] Re: Sound not working anymore

[Luke Yelavich]

Ok, do you have a 16.04 image handy? You may want to consider
downloading 16.04, and testing with that. If that works, then maybe its
worth considering an upgrade.

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

Title:
  Sound not working anymore

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Didn't do anything strange but the sound just stopped working for my
  headphones. Just like that.

  I have multiple soundcards. The one affected is CA0132 which is the
  built-in card of the motherboard. The other card isn't affected
  (CA0106) and is working fine with external speakers. I also tried with
  a plug and play usb soundcard (USB PnP Sound Device). also not
  affected and is working (as expected I guess).

  Tried restarting. Tried playing around with alsamixer and pavucontrol.
  Tried checking for updates and updating to latest. ...Didn't try doing
  a back-flip tho hehe XD

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf]
  ProcVersionSignature: Ubuntu 3.13.0-107.154-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-107-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 22 23:30:29 2017
  InstallationDate: Installed on 2015-02-19 (703 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: G1.Sniper Z87
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd11/21/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperZ87:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperZ87:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: G1.Sniper Z87
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

Re: [Desktop-packages] [Bug 1658528] Re: Sound not working anymore

[Luke Yelavich]

What if you unplug and re-plug? If that doesn't work, then its likely
something may have happened to your hardware. Do you have other outputs
you could test?

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

Title:
  Sound not working anymore

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Didn't do anything strange but the sound just stopped working for my
  headphones. Just like that.

  I have multiple soundcards. The one affected is CA0132 which is the
  built-in card of the motherboard. The other card isn't affected
  (CA0106) and is working fine with external speakers. I also tried with
  a plug and play usb soundcard (USB PnP Sound Device). also not
  affected and is working (as expected I guess).

  Tried restarting. Tried playing around with alsamixer and pavucontrol.
  Tried checking for updates and updating to latest. ...Didn't try doing
  a back-flip tho hehe XD

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf]
  ProcVersionSignature: Ubuntu 3.13.0-107.154-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-107-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 22 23:30:29 2017
  InstallationDate: Installed on 2015-02-19 (703 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: G1.Sniper Z87
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd11/21/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperZ87:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperZ87:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: G1.Sniper Z87
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

Re: [Desktop-packages] [Bug 1658528] [NEW] Sound not working anymore

[Luke Yelavich]

Had you updated your system that you can remember prior to this problem
occurring? If you were to boot 14.04 live media, does the problem exist
there? If you have Windows or another distro installed, does the problem
occur there?

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

Title:
  Sound not working anymore

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Didn't do anything strange but the sound just stopped working for my
  headphones. Just like that.

  I have multiple soundcards. The one affected is CA0132 which is the
  built-in card of the motherboard. The other card isn't affected
  (CA0106) and is working fine with external speakers. I also tried with
  a plug and play usb soundcard (USB PnP Sound Device). also not
  affected and is working (as expected I guess).

  Tried restarting. Tried playing around with alsamixer and pavucontrol.
  Tried checking for updates and updating to latest. ...Didn't try doing
  a back-flip tho hehe XD

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf]
  ProcVersionSignature: Ubuntu 3.13.0-107.154-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-107-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 22 23:30:29 2017
  InstallationDate: Installed on 2015-02-19 (703 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: G1.Sniper Z87
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd11/21/2014:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperZ87:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperZ87:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: G1.Sniper Z87
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

Re: [Desktop-packages] [Bug 1656832] Re: orca key, e. g. insert + space, is not responding

[Luke Yelavich]

Urm... no. Are you able to create a new user account and try and start
Orca there? If so, what happens?

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

Title:
  orca key, e. g. insert + space, is not responding

Status in gnome-orca package in Ubuntu:
  New

Bug description:
  After activating the orca screenreader with alt-super-s keys the speech 
output initiates.
  But the orca desktop key, i. e. insert, combined with a command, e. g. space, 
is not working.
  Expected result: orca settings window opens.
  Actual result: nothing happens.

  I checked the received keycodes: both keys are responding correctly.
  Affected package and binary:
  gnome-orca: /usr/bin/orca

  Affected distribution:
  ubuntu 16.04 LTS

  Thanks a lot!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-orca 3.18.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 16 15:04:21 2017
  InstallationDate: Installed on 2013-10-18 (1186 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: gnome-orca
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (267 days ago)

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

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

Re: [Desktop-packages] [Bug 1656832] [NEW] orca key, e. g. insert + space, is not responding

[Luke Yelavich]

Do other Orca keyboard keystrokes work? Where were you when starting
Orca? What happens if once you have started orca, you log out and back
in again? Do things work then as expected?

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

Title:
  orca key, e. g. insert + space, is not responding

Status in gnome-orca package in Ubuntu:
  New

Bug description:
  After activating the orca screenreader with alt-super-s keys the speech 
output initiates.
  But the orca desktop key, i. e. insert, combined with a command, e. g. space, 
is not working.
  Expected result: orca settings window opens.
  Actual result: nothing happens.

  I checked the received keycodes: both keys are responding correctly.
  Affected package and binary:
  gnome-orca: /usr/bin/orca

  Affected distribution:
  ubuntu 16.04 LTS

  Thanks a lot!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-orca 3.18.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 16 15:04:21 2017
  InstallationDate: Installed on 2013-10-18 (1186 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: gnome-orca
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (267 days ago)

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