date:20200717

[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  WL: compositor bug: The compositor tried to use an object from one
  client in a 'wl_pointer.enter' for a different client (resulting in
  Gnome terminal crashing)

Status in gnome-terminal package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired
Status in wayland package in Ubuntu:
  Expired

Bug description:
  Since upgrading to 20.04 and switching to Wayland, Gnome terminal
  occasionally crashes. I interpret the corresponding logs to mean that
  it's actually Wayland that fails to do something in the background,
  which then takes down Gnome terminal:

  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client 
communication (pid 11639)
  touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events 
from display: Katkennut putki
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Main process exited, code=exited, status=1/FAILURE
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Failed with result 'exit-code'.

  I have yet to nail down the precise circumstances, as this has (so
  far) been somewhat rare, having occurred perhaps once or twice a week.

  Since the log mentions pointer, I should perhaps mention that I've set
  `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome
  terminal also exhibits other misbehaviour wrt. to this, occasionally
  refusing to get focus, or alternatively losing the focus, despite
  mouse cursor being over the terminal window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.8-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  Uname: Linux 5.4.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 15:22:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed
   xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2016-10-13 (1302 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic 
root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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: System manufacturer
  version.compiz: compiz N/A

[Desktop-packages] [Bug 1878956] Re: Shutdown continues even after cancelled by application

[Expired for gnome-session (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-session (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Shutdown continues even after cancelled by application

Status in gnome-session package in Ubuntu:
  Expired

Bug description:
  1. Open a text editor of any kind and edit any document.  Do not save
  2. Initiate a shutdown from the GUI menu
  3. The application will prompt you save because it's being closed.  Select 
"cancel" to abort the save and close.  The file won't be saved and the 
application will not close.
  4. After a few seconds, the computer will immediately shut down, losing your 
document changes.

  This means that when a shutdown is initiated, there's nothing the user
  can do to abort the shutdown.

  What should have happened is that Ubuntu should have noticed that the
  shutdown was cancelled.  That's how Windows and Mac works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1878956/+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 1878911] Re: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

[Expired for tex-common (Ubuntu) because there has been no activity for
60 days.]

** Changed in: tex-common (Ubuntu)
   Status: Incomplete => Expired

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

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

Status in tex-common package in Ubuntu:
  Expired

Bug description:
  warning that package tex-common 6.13 could not be installed on update
  to 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: tex-common 6.13
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 15 16:39:31 2020
  ErrorMessage: installed tex-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2019-07-18 (302 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: tex-common
  Title: package tex-common 6.13 failed to install/upgrade: installed 
tex-common package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to focal on 2020-05-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1878911/+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 1878782] Re: Bluetooth is on but scanned devices are not showing.

[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth is on but scanned devices are not showing.

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Bluetooth in spite of being switched on, shows the same image as when
  it is off in the paired devices menu. I cannot access my paired
  devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dashtrox   1582 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 15 13:48:16 2020
  InstallationDate: Installed on 2020-05-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 1TCN27WW(V2.08)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr1TCN27WW(V2.08):bd07/06/2018:svnLENOVO:pn80UD:pvrLenovoideapad110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15ISK:
  dmi.product.family: ideapad 110-15ISK
  dmi.product.name: 80UD
  dmi.product.sku: LENOVO_MT_80UD_BU_idea_FM_ideapad 110-15ISK
  dmi.product.version: Lenovo ideapad 110-15ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878782/+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 1866540] Re: X server freezed

[Expired for xserver-xorg-video-nouveau (Ubuntu) because there has been
no activity for 60 days.]

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

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

Title:
  X server freezed

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

Bug description:
  As I was playing with bzflag, the Xserver freezed. Keyboard and mouse didn't 
work anymore, only ALT-SYS-R S I U B to boot.
  It's the first time I've got this bug.


  Mar  8 11:22:40 Ordinateur-David kernel: [ 3809.838604] nouveau :05:00.0: 
bzflag[11340]: Unknown handle 0x00cb
  Mar  8 11:22:40 Ordinateur-David kernel: [ 3809.838608] nouveau :05:00.0: 
bzflag[11340]: validate_init
  Mar  8 11:22:40 Ordinateur-David kernel: [ 3809.838609] nouveau :05:00.0: 
bzflag[11340]: validate: -2

  $ lsb_release -rd
  Description:  Linux Mint 19.3 Tricia
  Release:  19.3

  
  $ apt-cache policy xserver-xorg-video-nouveau
  xserver-xorg-video-nouveau:
Installé : 1:1.0.15-2
Candidat : 1:1.0.15-2
   Table de version :
   *** 1:1.0.15-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: tricia
  DistroRelease: Linux Mint 19.3
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK107GL [Quadro K2000] [10de:0ffe] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GK107GL [Quadro K2000] [103c:094c]
  LightdmDisplayLog: -2
  MachineType: Hewlett-Packard HP Z420 Workstation
  Package: xserver-xorg-video-nouveau 1:1.0.15-2 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=16ff2b10-8f36-42a7-93bd-4c84973fe52a ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Tags: tricia third-party-packages ubuntu
  Uname: Linux 5.3.0-51-generic x86_64
  UnreportableReason: Ce paquet n'est pas officiellement pris en charge par 
Linux. Veuillez désinstaller tout paquet tiers et réessayer.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/29/2019
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.96
  dmi.board.asset.tag: VANTYGHEM
  dmi.board.name: 1589
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.asset.tag: VANTYGHEM
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53335X G=D
  dmi.product.name: HP Z420 Workstation
  dmi.product.sku: WM445ET#ABF
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1866540/+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 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)

[Expired for wayland (Ubuntu) because there has been no activity for 60
days.]

** Changed in: wayland (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  WL: compositor bug: The compositor tried to use an object from one
  client in a 'wl_pointer.enter' for a different client (resulting in
  Gnome terminal crashing)

Status in gnome-terminal package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired
Status in wayland package in Ubuntu:
  Expired

Bug description:
  Since upgrading to 20.04 and switching to Wayland, Gnome terminal
  occasionally crashes. I interpret the corresponding logs to mean that
  it's actually Wayland that fails to do something in the background,
  which then takes down Gnome terminal:

  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client 
communication (pid 11639)
  touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events 
from display: Katkennut putki
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Main process exited, code=exited, status=1/FAILURE
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Failed with result 'exit-code'.

  I have yet to nail down the precise circumstances, as this has (so
  far) been somewhat rare, having occurred perhaps once or twice a week.

  Since the log mentions pointer, I should perhaps mention that I've set
  `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome
  terminal also exhibits other misbehaviour wrt. to this, occasionally
  refusing to get focus, or alternatively losing the focus, despite
  mouse cursor being over the terminal window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.8-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  Uname: Linux 5.4.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 15:22:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed
   xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2016-10-13 (1302 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic 
root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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: System manufacturer
  version.compiz: compiz N/A

[Desktop-packages] [Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)

[Expired for gnome-terminal (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  WL: compositor bug: The compositor tried to use an object from one
  client in a 'wl_pointer.enter' for a different client (resulting in
  Gnome terminal crashing)

Status in gnome-terminal package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired
Status in wayland package in Ubuntu:
  Expired

Bug description:
  Since upgrading to 20.04 and switching to Wayland, Gnome terminal
  occasionally crashes. I interpret the corresponding logs to mean that
  it's actually Wayland that fails to do something in the background,
  which then takes down Gnome terminal:

  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client 
communication (pid 11639)
  touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events 
from display: Katkennut putki
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Main process exited, code=exited, status=1/FAILURE
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Failed with result 'exit-code'.

  I have yet to nail down the precise circumstances, as this has (so
  far) been somewhat rare, having occurred perhaps once or twice a week.

  Since the log mentions pointer, I should perhaps mention that I've set
  `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome
  terminal also exhibits other misbehaviour wrt. to this, occasionally
  refusing to get focus, or alternatively losing the focus, despite
  mouse cursor being over the terminal window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.8-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  Uname: Linux 5.4.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 15:22:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed
   xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2016-10-13 (1302 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic 
root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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: System manufacturer
  version.compiz: compiz N/A

[Desktop-packages] [Bug 1878988] Re: stuttering or dropped frames in Gnome

[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  stuttering or dropped frames in Gnome

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

Bug description:
  experiencing frame "stutter" or regular dropped frames in gnome.
  Occurs with intel integrated graphics, AMD gpu with open source
  drivers, and nvidia gpu with proprietary drivers. This does not occur
  in KDE. I do not believe this occurring before upgrading from 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri May 15 16:20:41 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-06 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  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/1878988/+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 1879117] Re: desktop icon get pixel error

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  desktop icon get pixel error

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  temporarily fixed by changing tweak options

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 10:15:21 2020
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  InstallationDate: Installed on 2018-11-20 (543 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-04 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879117/+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 1879016] Re: Crash with "Object .Gjs_AppIndicatorIconActor__1 ..." loss of Riot AppIndicator icon

[Expired for gnome-shell-extension-appindicator (Ubuntu) because there
has been no activity for 60 days.]

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Crash with "Object .Gjs_AppIndicatorIconActor__1 ..." loss of Riot
  AppIndicator icon

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Expired

Bug description:
  Sporadically, I see loss of the Riot-Desktop (https://github.com
  /vector-im/riot-web/ care of https://packages.riot.im/debian/) app
  indicator icon. This appears to be associated with the following log
  lines from `journalctl /usr/bin/gnome-shell`

  ```
  May 16 10:54:22 cube gnome-shell[1688]: Object .Gjs_AppIndicatorIconActor__1 
(0x55ec9dec3a00), has been already finalized. Impossible to set any property to 
it.
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: == Stack trace for 
context 0x55ec9bc28340 ==
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #0 0x7ffd2838cb50 b   
resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7fbf1c1b5de0 @ 87)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #1 0x55ec9c0c0d10 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/indicatorStatusIcon.js:93
 (0x7fbed86c9340 @ 58)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #2 0x7ffd2838deb0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #3 0x7ffd2838df70 b   
self-hosted:916 (0x7fbf1c1f12b8 @ 367)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #4 0x7ffd2838e060 b   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7fbf1c1d2230 @ 386)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #5 0x55ec9c0c0c88 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:190
 (0x7fbed86b6f78 @ 22)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #6 0x7ffd2838f3c0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #7 0x55ec9c0c0be0 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:219
 (0x7fbed86b65e8 @ 225)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #8 0x7ffd28390720 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #9 0x55ec9c0c0b68 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/extension.js:61
 (0x7fbed8688780 @ 37)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #10 0x55ec9c0c0aa8 i   
resource:///org/gnome/shell/ui/extensionSystem.js:83 (0x7fbf086592b8 @ 441)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #11 0x55ec9c0c0a28 i   
resource:///org/gnome/shell/ui/extensionSystem.js:354 (0x7fbf08659d58 @ 13)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #12 0x7ffd28391490 b   
self-hosted:251 (0x7fbf1c1c4ab0 @ 223)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #13 0x55ec9c0c09a8 i   
resource:///org/gnome/shell/ui/extensionSystem.js:353 (0x7fbf08659cd0 @ 64)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #14 0x55ec9c0c0928 i   
resource:///org/gnome/shell/ui/extensionSystem.js:371 (0x7fbf08659de0 @ 87)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #15 0x7ffd28392990 b   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7fbf1c1d2230 @ 386)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #16 0x7ffd28393130 b   
resource:///org/gnome/shell/ui/sessionMode.js:205 (0x7fbf083704d8 @ 254)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #17 0x7ffd28394520 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #18 0x55ec9c0c07e8 i   
resource:///org/gnome/shell/ui/sessionMode.js:167 (0x7fbf083702b8 @ 40)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #19 0x7ffd28395880 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
  May 16 10:54:22 cube gnome-shell[1688]: Object .Gjs_AppIndicatorIconActor__1 
(0x55ec9d075050), has been already finalized. Impossible to set any property to 
it.
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #20 0x55ec9c0c0740 i   
resource:///org/gnome/shell/ui/screenShield.js:1282 (0x7fbf08353a28 @ 188)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #21 0x7ffd28396be0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #22 0x55ec9c0c0690 i   
resource:///org/gnome/shell/ui/screenShield.js:1331 (0x7fbf08353ab0 @ 391)
  May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #23 0x7ffd28397f40 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71)
  May 16 10:54:22 cube

[Desktop-packages] [Bug 1878988] Re: stuttering or dropped frames in Gnome

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  stuttering or dropped frames in Gnome

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

Bug description:
  experiencing frame "stutter" or regular dropped frames in gnome.
  Occurs with intel integrated graphics, AMD gpu with open source
  drivers, and nvidia gpu with proprietary drivers. This does not occur
  in KDE. I do not believe this occurring before upgrading from 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri May 15 16:20:41 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-06 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  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/1878988/+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 1879076] Re: [nvidia] Xorg freeze

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [nvidia] Xorg freeze

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  When in both Firefox and Opera hardware acceleration is on and browser
  is running it will trigger freeze with X.OrgX driver on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 12:17:35 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 1600M] [10de:040d] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G84GLM [Quadro FX 1600M] [1028:019b]
  InstallationDate: Installed on 2020-04-08 (38 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Precision M6300
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=57f985ce-6982-47e4-8428-74d41764c9ce ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0JM680
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd06/05/2013:svnDellInc.:pnPrecisionM6300:pvr:rvnDellInc.:rn0JM680:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M6300
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879076/+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 1879113] Re: package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

[Expired for pygobject (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pygobject (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in pygobject package in Ubuntu:
  Expired

Bug description:
  Installing ra1nstorm virtual Mac

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-gi-cairo 3.26.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun May 17 13:06:06 2020
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2020-05-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.3
  SourcePackage: pygobject
  Title: package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1879113/+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 1879039] Re: [prl_vid] Xorg crash

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [prl_vid] Xorg crash

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  After Firefox crushes couldnt open any browser, no Firefox nor
  Chromium and I had to restart the OS. Ubuntu 19.10 is a guest OS on
  Parallels 15

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_vid prl_tg
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Sat May 16 12:17:36 2020
  DistUpgraded: 2020-05-09 07:53:36,319 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   parallels-tools, 15.1.4.47270, 4.15.0-100-generic, x86_64: installed
   parallels-tools, 15.1.4.47270, 5.3.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Parallels, Inc. Accelerated Virtual Video Adapter [1ab8:4005] (prog-if 00 
[VGA controller])
 Subsystem: Parallels, Inc. Accelerated Virtual Video Adapter [1ab8:0400]
  InstallationDate: Installed on 2018-08-10 (644 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Parallels Software International Inc. Parallels Virtual Platform
  MonitorsUser.xml: Virtual1unknownunknownunknown144090059.988003001yes
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=b214da3c-eaae-4adf-bfcc-c64b050618e8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2020-05-09 (7 days ago)
  dmi.bios.date: 04/13/2020
  dmi.bios.vendor: Parallels Software International Inc.
  dmi.bios.version: 15.1.4 (47270)
  dmi.board.name: Parallels Virtual Platform
  dmi.board.vendor: Parallels Software International Inc.
  dmi.board.version: None
  dmi.chassis.type: 9
  dmi.chassis.vendor: Parallels Software International Inc.
  dmi.modalias: 
dmi:bvnParallelsSoftwareInternationalInc.:bvr15.1.4(47270):bd04/13/2020:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct9:cvr:
  dmi.product.family: Parallels VM
  dmi.product.name: Parallels Virtual Platform
  dmi.product.sku: Undefined
  dmi.product.version: None
  dmi.sys.vendor: Parallels Software International Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879039/+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 1887610] Autopkgtest regression report (pulseaudio/1:13.99.1-1ubuntu3.5)

2020-07-17 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted pulseaudio (1:13.99.1-1ubuntu3.5) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

openjdk-8/8u252-b09-1ubuntu1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#pulseaudio

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 1884850] Re: Xorg server uses unacceptably large amounts of memory (and keep growing)

2020-07-17 Thread Wirawan Purwanto

Please ignore #6. I clicked "Post" too soon. I will complete it and re-
post.

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

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

Title:
  Xorg server uses unacceptably large amounts of memory (and keep
  growing)

Status in libreoffice package in Ubuntu:
  New
Status in marco package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Description: Xorg server uses unacceptably large amounts of memory
  (and keep growing)

  Ever since I upgraded to Ubuntu 20.04 (with fresh install) on my
  laptop (Lenovo T450s, Intel Core i5-5200U, Intel HD5500 graphics), I
  have been troubled by the way Xorg process uses memory.

  Here is an example of memory usage of Xorg as a function of time. I
  rebooted the laptop on June 17:

  Xorg-usage-20200617a.txt:root1224  1.9  0.8 948408 98848 tty7 
Rsl+ 10:38   0:05  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200617b.txt:root1224  2.2  0.8 978264 105180 tty7
Ssl+ 10:38   0:22  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200618a.txt:root1224  0.3  1.3 1143064 162584 tty7   
Ssl+ Jun17   3:15  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200619a.txt:root1224  0.3  2.9 1432232 360700 tty7   
Ssl+ Jun17  12:30  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200619b.txt:root1224  0.3  2.7 1313120 338656 tty7   
Ssl+ Jun17  12:39  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200623a.txt:root1224  0.3  6.0 1944364 738596 tty7   
Ssl+ Jun17  31:55  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

  The filename indicates the date the "ps fuxa" command was run.
  Contrast this against the memory usage of another Xorg process run for XPRA:

  Xorg-usage-20200617b.txt:wirawan 4452  2.4  2.0 1106920 244984 ?  
Ssl  10:46   0:12  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200618a.txt:wirawan 4452  0.2  2.0 1108572 246616 ?  
Ssl  Jun17   2:25  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200619a.txt:wirawan 4452  0.2  2.0 1112460 249516 ?  
Ssl  Jun17   8:34  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200619b.txt:wirawan 4452  0.2  2.0 1112964 250020 ?  
Ssl  Jun17   8:40  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200623a.txt:wirawan 4452  0.1  2.0 1113092 250544 ?  
Ssl  Jun17  11:22  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100

  My desktop usage pattern:

  * MATE desktop
  * 4-desktop setting (standard default MATE when shipped)
  * GNUCASH
  * about 3 windows of terminal (each about 5-10 tabs)
  * XPRA running Firefox web browser (to isolate web browser pixmap memory 
usage, if that was the culprit)
  * LibreOffice (several windows open at any time)
  * using "redshift" to change the desktop color to red at night

  I have never seen this before using Ubuntu 20.04 on this machine.
  Before, when I was running Debian 8, I could run this machine for months 
literally without Xorg memory bloating rapidly like this (but then I was using 
xfce instead of MATE).
  I viewed the output of xrestop, the pixmap memory

[Desktop-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu8

---
pulseaudio (1:13.99.1-1ubuntu8) groovy; urgency=medium

  * d/p/0033-alsa-make-the-unsuspend-more-robust.patch:
- resolve cases where there is no available audio entry in sound
  settings after suspending in 'Performance mode' (LP: #1887610)

 -- Hui Wang   Wed, 15 Jul 2020 15:29:05 +0800

** Changed in: pulseaudio (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 1884850] Re: Xorg server uses unacceptably large amounts of memory (and keep growing)

2020-07-17 Thread Wirawan Purwanto

Hi Daniel, responding to your comment:

In my years of using Linux desktop (in particular, XFCE), I have never
experienced memory explosion caused by Xorg server like what I described
in this bug report. Please allow me to be a bit candid here. It seems
like the newer versions of desktop software (which could mean one or
more of these: Xorg, firefox, Libre Office, XFCE and/or MATE, ...) leads
to significant bloat in memory usage. This is to the point that a very
capable laptop (with >= 8 GB of RAM) would perform poorly because of
memory thrashing today even when our usage pattern is not changed over
the years (at least I feel so). I'll back this up below.

I still have a desktop computer running Debian 8 and XFCE. Here are some
stats on that running system:

* up time = 31

*

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

Title:
  Xorg server uses unacceptably large amounts of memory (and keep
  growing)

Status in marco package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Description: Xorg server uses unacceptably large amounts of memory
  (and keep growing)

  Ever since I upgraded to Ubuntu 20.04 (with fresh install) on my
  laptop (Lenovo T450s, Intel Core i5-5200U, Intel HD5500 graphics), I
  have been troubled by the way Xorg process uses memory.

  Here is an example of memory usage of Xorg as a function of time. I
  rebooted the laptop on June 17:

  Xorg-usage-20200617a.txt:root1224  1.9  0.8 948408 98848 tty7 
Rsl+ 10:38   0:05  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200617b.txt:root1224  2.2  0.8 978264 105180 tty7
Ssl+ 10:38   0:22  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200618a.txt:root1224  0.3  1.3 1143064 162584 tty7   
Ssl+ Jun17   3:15  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200619a.txt:root1224  0.3  2.9 1432232 360700 tty7   
Ssl+ Jun17  12:30  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200619b.txt:root1224  0.3  2.7 1313120 338656 tty7   
Ssl+ Jun17  12:39  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200623a.txt:root1224  0.3  6.0 1944364 738596 tty7   
Ssl+ Jun17  31:55  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

  The filename indicates the date the "ps fuxa" command was run.
  Contrast this against the memory usage of another Xorg process run for XPRA:

  Xorg-usage-20200617b.txt:wirawan 4452  2.4  2.0 1106920 244984 ?  
Ssl  10:46   0:12  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200618a.txt:wirawan 4452  0.2  2.0 1108572 246616 ?  
Ssl  Jun17   2:25  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200619a.txt:wirawan 4452  0.2  2.0 1112460 249516 ?  
Ssl  Jun17   8:34  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200619b.txt:wirawan 4452  0.2  2.0 1112964 250020 ?  
Ssl  Jun17   8:40  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200623a.txt:wirawan 4452  0.1  2.0 1113092 250544 ?  
Ssl  Jun17  11:22  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100

  My desktop usage pattern:

  * MATE desktop
  * 4-desktop setting (standard default MATE when shipped)
  * GNUCASH

[Desktop-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

2020-07-17 Thread Hui Wang

@Jpodjarny,

And please also upload the dmesg. BTW, how did you update, only update
the pulseaudio or upgrade many packages? And what is the pulseaudio
version now (checking it by running dpkg -s pulseaudio | grep Version).

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

2020-07-17 Thread Hui Wang

@Jpodjarny,

Could you please run pa-info > audio-log.txt, then upload the audio-
log.txt?

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 1886672] Re: Multiple screen display issues

2020-07-17 Thread David Rasch

I have the 3.36.3 package installed
ii  gnome-shell3.36.3-1ubuntu1~20.04.2 amd64graphical shell for the 
GNOME desktop

I'm experiencing a crash upon resume from sleep, something with either
gnome-shell or screensaver crashes. After suspend, I can see my screen
(without much of the window decorations or layouts) before it eventually
restarts things and then I can unlock my screen normally.

I have a dell xps 13 9380,

ERROR: apport (pid 693953) Thu Jul 16 20:11:08 2020: this executable already 
crashed 2 times, ignoring
ERROR: apport (pid 694509) Thu Jul 16 20:28:01 2020: called for pid 693961, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 694509) Thu Jul 16 20:28:01 2020: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pid 694509) Thu Jul 16 20:28:01 2020: debug: session gdbus call: 
(true,)

ERROR: apport (pid 694509) Thu Jul 16 20:28:01 2020: this executable already 
crashed 2 times, ignoring
ERROR: apport (pid 699014) Thu Jul 16 23:00:33 2020: called for pid 694516, 
signal 6, core limit 0, dump mode 1
ERROR: apport (pid 699014) Thu Jul 16 23:00:33 2020: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pid 699014) Thu Jul 16 23:00:33 2020: debug: session gdbus call: 
(true,)

ERROR: apport (pid 699014) Thu Jul 16 23:00:33 2020: this executable already 
crashed 2 times, ignoring
ERROR: apport (pid 779097) Fri Jul 17 17:10:53 2020: called for pid 699036, 
signal 6, core limit 0, dump mode 1
ERROR: apport (pid 779097) Fri Jul 17 17:10:53 2020: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pid 779097) Fri Jul 17 17:10:53 2020: debug: session gdbus call: 
(true,)

ERROR: apport (pid 779097) Fri Jul 17 17:10:53 2020: this executable
already crashed 2 times, ignoring


** Attachment added: "logs and pci"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886672/+attachment/5393634/+files/details.zip

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

Title:
  Multiple screen display issues

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  New bug for me. Issue was fine till last week. I think this may be
  related to the following as it started happening shortly thereafter.

  I have XPS13 with second monitor, all working fine till I lock screen
  or suspend. Then my second monitor will not 'resume'. I.e. stays off.

  This behaviour started after (or shortly after) playing a wine game
  using Lutris to launch. Shutting game down and almost immediately
  hitting suspend on the laptop. Was rushing out.

  It's a wild shot in the dark but I think something got messed up / not
  saved correctly in this process.

  To get it working I need to unplug monitor (using USB-C > HDMI) >
  suspend > plug in monitor > resume and sometimes still need to open
  display settings before it 'kicks in'. Damn annoying. Hope someone can
  help :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Jul  7 16:44:52 2020
  DistUpgraded: 2020-05-15 15:17:42,708 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:082a]
  InstallationDate: Installed on 2019-01-29 (525 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-05-15 (53 days ago)
  dmi.bios.date: 11/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.13.0
  dmi.board.name: 0PVG6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PVG6D:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.product.sku: 082A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx

[Desktop-packages] [Bug 1886345] Re: Display gets corrupted and text gets replaced by odd characters

2020-07-17 Thread Druid

** Attachment added: "journalctl -b0 > journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886345/+attachment/5393633/+files/journal.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/1886345

Title:
  Display gets corrupted and text gets replaced by odd characters

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This is a fresh install of 2020.04.
  Issue is that the display routinely gets corrupted and flickers with blocks 
of previously open windows. 
  If left without a restart, the system menu text will get replaced by odd 
characters and system dialog boxes will not display, buttons for the dialog 
boxes will briefly appear with no text when cursor is over them.
  Very occasionally, the system will stop responding to the mouse and keyboard 
after clicking an icon on the dash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  5 15:24:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-03 (63 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886345/+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 1886345] Re: Display gets corrupted and text gets replaced by odd characters

2020-07-17 Thread Druid

** Attachment added: "lspci -k > lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886345/+attachment/5393632/+files/lspcik.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/1886345

Title:
  Display gets corrupted and text gets replaced by odd characters

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This is a fresh install of 2020.04.
  Issue is that the display routinely gets corrupted and flickers with blocks 
of previously open windows. 
  If left without a restart, the system menu text will get replaced by odd 
characters and system dialog boxes will not display, buttons for the dialog 
boxes will briefly appear with no text when cursor is over them.
  Very occasionally, the system will stop responding to the mouse and keyboard 
after clicking an icon on the dash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  5 15:24:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-03 (63 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886345/+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 1887296] Re: Moving popup windows drags the application's main window behind it

2020-07-17 Thread teo1978

> We do not consider Gnome's defaults in this area unreasonable.

That no longer surprises me.

Ubuntu apparently has stopped fighting the idiotic decisions taken by
Gnome upstream.

You are no longer patching the type-ahead-triggers-search madness, you
refused to restore the "open with" submenu, you have embraced the
reversed sorting icons, and the list goes on.

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

Title:
  Moving popup windows drags the application's main window behind it

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Sometimes programs open a "popup" or a "secondary", "child" window, I
  don't know what the word is.

  For example, in Chrome, if I right-click on an image in a web page and
  choose "Save As", this will open a new file browser window that allows
  me to browse for a directory to save the image to.

  Until Ubuntu 16.04, I could move that child window around by dragging
  it by its title bar, and that would not move around the parent window
  behind it.

  Now, it does. That is, the "parent" window greyes out, and moving the
  "child" window (i.e. the popup) on the foreground causes the parent
  window in the background to move as if they were glued together.

  In the above example, if I drag around the "Save As" window, the
  Chrome window behind it moves too. Even worse, if the parent window is
  maximized, it will "oppose resistance" to the dragging of the popup
  window, and if I drag far enough, the parent window will unmaximize
  and unblock the movement of both windows.

  It's pure madness.

  
  I can't imagine a scenario where this is the unavoidable consequence of some 
improvement. It looks like it is by design.

  Why?

  What were you thinking? Why do you ACTIVELY work to degrade usability
  and make the users' life miserable??

  
  Here's a very real-life example:

  As mentioned above, I right-click on something in the browser (like an
  image or a video) and do Save As. When the file browser window opens,
  it covers the content of the web page from which I was saving the
  content. Maybe I want to move the child window in order to reveal the
  web page that I was visiting in the first place, because the context
  (which I haven't memorized in full in my brain just yet) helps me
  choose a file name for the very file I'm saving.

  
  Another example: I am browsing some folder in Nautilus. I right-click on a 
file or folder inside it, and open Properties. That opens in a popup. Now I 
want to have another look at the name of the file I selected (of which I'm now 
seeing the properties), and those around it, because I'm wondering if I chose 
the wrong file, or for whatever other reason. I can't do taht without closing 
the Properties window.

  The everyday examples are countless.

  
  This is idiotic. Seriously, what are you doing?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 18:11:28 2020
  DistUpgraded: 2020-07-12 15:56:23,368 INFO cache.commit()
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.108: added
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (2465 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag

[Desktop-packages] [Bug 1781597] Re: [SRU] WoWLAN settings are not supported

2020-07-17 Thread Simon Quigley

** Tags removed: verification-done-cosmic
** Tags added: rls-bb-incoming

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

Title:
  [SRU] WoWLAN settings are not supported

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Triaged
Status in network-manager source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  WoWLAN lets us wake up the system by sending wake packets over the
  wifi connection. This is something requested by some OEM projects, for
  bionic server images.

  NM 1.12 supports configuring this feature, so this can be achieved by
  backporting that support to 1.10 (bionic version). These are the MPs
  for cosmic and bionic:

  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468
  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465

  [Test Case]

  First, the wifi card must support WoWLAN. This can be checked by
  running

  $ iw phy

  and searching for "WoWLAN support:" in the output. If it is supported,
  with the patch applied a connection configured with wowlan can be
  created with:

  $ sudo nmcli d wifi connect  password 
  $ sudo nmcli c modify  802-11-wireless.wake-on-wlan 8
  $ sudo nmcli c down 
  $ sudo nmcli c up 

  We can check with 'iw' that WoWLAN is active for the connection:

  $ iw phy phy0 wowlan show
  WoWLAN is enabled:
   * wake up on magic packet

  In this case we have configured the connection to wake up the system
  when a 'magic' packet is received. We can then suspend the system with

  $ sudo systemctl suspend

  And we should be able to wake the system from another device with the
  command

  $ sudo etherwake -i  

  [Regression Potential]

  Although the patch is not especially small, it is a backport of
  changes that have been merged upstream, with very little modifications
  to make it compile in 1.10. It is also a rather isolated feature that
  should not conflict with existing ones. The feature will be activated
  only if configured from the command line, so the risk of regressions
  should be small. Note also that the patch will be removed as soon as
  Ubuntu moves to NM 1.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+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 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working

2020-07-17 Thread Marcelo Pires

Yes! Google Chrome.

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

Title:
  [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When you start playing some audio, the sound disappears.

  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
Subsystem: ASUSTeK Computer Inc. M5A78L LE
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  
  uname -a
  Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  alsa-info

  
  !!
  !!ALSA Information Script v 0.4.65
  !!

  !!Script ran on: Fri Jun 19 13:38:12 UTC 2020

  
  !!Linux Distribution
  !!--

  Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu
  20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu
  20.04 LTS" HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies
  /privacy-policy" UBUNTU_CODENAME=focal

  
  !!DMI Information
  !!---

  Manufacturer:  System manufacturer
  Product Name:  System Product Name
  Product Version:   System Version
  Firmware Version:  1201   
  Board Vendor:  ASUSTeK Computer INC.
  Board Name:M5A78L-M LX/BR

  
  !!ACPI Device Status Information
  !!---

  /sys/bus/acpi/devices/ATK0110:00/status15
  /sys/bus/acpi/devices/PNP0103:00/status15
  /sys/bus/acpi/devices/PNP0400:00/status15
  /sys/bus/acpi/devices/PNP0501:00/status15
  /sys/bus/acpi/devices/PNP0C0C:00/status11
  /sys/bus/acpi/devices/PNP0C0F:00/status9
  /sys/bus/acpi/devices/PNP0C0F:01/status9
  /sys/bus/acpi/devices/PNP0C0F:02/status9
  /sys/bus/acpi/devices/PNP0C0F:03/status9
  /sys/bus/acpi/devices/PNP0C0F:04/status9
  /sys/bus/acpi/devices/PNP0C0F:05/status9
  /sys/bus/acpi/devices/PNP0C0F:06/status9
  /sys/bus/acpi/devices/PNP0C0F:07/status9
  /sys/bus/acpi/devices/device:20/status 15
  /sys/bus/acpi/devices/device:21/status 15

  
  !!Kernel Information
  !!--

  Kernel release:5.4.0-37-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes

  
  !!ALSA Version
  !!

  Driver version: k5.4.0-37-generic
  Library version:1.2.3
  Utilities version:  1.2.2

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xfe9f4000 irq 16

  
  !!PCI Soundcards installed in the system
  !!--

  00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 
Azalia (Intel HDA) [1002:4383]
Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445]

  
  !!Modprobe options (Sound related)
  !!

  snd_pcsp: index=-2
  snd_usb_audio: index=-2
  snd_atiixp_modem: index=-2
  snd_intel8x0m: index=-2
  snd_via82xx_modem: index=-2
  snd_atiixp_modem: index=-2
  snd_intel8x0m: index=-2
  snd_via82xx_modem: index=-2
  snd_usb_audio: index=-2
  snd_usb_caiaq: index=-2
  snd_usb_ua101: index=-2
  snd_usb_us122l: index=-2
  snd_usb_usx2y: index=-2
  snd_cmipci: mpu_port=0x330 fm_port=0x388
  snd_pcsp: index=-2
  snd_usb_audio: index=-2
  snd_hda_intel: model=auto
  snd_hda_intel: dmic detect=0

  
  !!Loaded sound module options
  !!---

  !!Module: snd_hda_intel
align_buffer_size : -1
bdl_pos_adj : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
beep_mode : 
N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N
dmic_detect : Y
enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
enable_msi : -1
id : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
index : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
jackpoll_ms : 
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0

[Desktop-packages] [Bug 1880570] Re: Dock - running applications are not/delayed updated

2020-07-17 Thread Adam Barton

I've had this bug constantly since I updated to 20.04. Installing gnome-
shell-extension-ubuntu-dock/ 67ubuntu20.04.5 did NOT fix the issue.

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

Title:
  Dock - running applications are not/delayed updated

Status in Dash to dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  The running applications, displayed in the dock are sometimes not
  updated, or only updated with a long delay (after 20-30 seconds).
  However restarting with `alt`+`F2` -> "r" -> `enter`, fixes the
  problem temporarily, just to come back shortly after. At first I
  thought it was something caused by my update to 20.04, but it even
  happens with a fresh install (dock location is at the bottom). I think
  there are multiple ways to trigger this behavior, but what worked
  reliably so far is to close the last running application, so that the
  dock is completely empty (no favorite applications in the dock - only
  the "Show applications" button on the dock). So far this triggered the
  bug every time, but I'm quite sure there were also other ways to get
  into this "dock no longer/delayed updating" state with other means.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 16:36:18 2020
  InstallationDate: Installed on 2020-05-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1880570/+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 1886592] Re: Add support for VMware Horizon SSO to gnome-shell

Is this something we need to get backported to focal?

As I don't think could be included in upstream's gnome-3-36 branch, so
we'll have to carry the patch

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

Title:
  Add support for VMware Horizon SSO to gnome-shell

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Bionic:
  In Progress
Status in gnome-shell source package in Eoan:
  Won't Fix
Status in gnome-shell source package in Focal:
  In Progress
Status in gnome-shell source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  VMware Horizon is a VDI product that runs atop of VMware's normal
  virtualisation stack, and it supports SSO authentication for login.

  In the past, the VMware Horizon agent has been pretty buggy, and
  requires SSO patches to be present to function, otherwise it breaks
  and causes entire outages for anyone trying to use the VDI.

  To solve this, VMware had been custom compiling their own libgnome-
  shell.so libraries with their SSO patches, which are based on oVirt's
  SSO implementation. When you install VMware Horizon agent to the
  instance, it overwrites Ubuntu's libgnome-shell.so with their custom
  compiled one.

  VMware don't keep their custom compiled libgnome-shell.so library up
  to date, so bugs that have already been fixed still live on in their
  library. Also, when Ubuntu updates our gnome-shell packages, it
  overwrites the custom libgnome-shell.so library, which then causes the
  Horizon agent to break, and causes outages for anyone using the VDI,
  which have to be solved by manually copying the custom library back.

  This situation is untenable for VMware Horizon users, so I have asked
  VMware to upstream their SSO patches. After a long painful process,
  they have landed in gnome-shell master.

  This SRU will significantly improve the quality of life for VMware
  Horizon users, and will remove the need for VMware to distribute
  custom libraries.

  [Testcase]

  You need an instance that runs on VMware Horizon, and the Horizon
  agent needs to be installed and running. Ideally, SSO authentication
  should be enabled to test all features, but it is not necessary to
  partially test.

  Test packages are available in this ppa:
  https://launchpad.net/~mruffell/+archive/ubuntu/sf247978-test

  If you install the test package in a VMware Horizon VDI, the instance
  should come up cleanly after reboot and function properly, especially
  with SSO login.

  The instance should be able to function without custom libgnome-
  shell.so libraries provided by VMware.

  
  [Regression Potential]

  The code refactors the oVirt SSO implementation into a more
  generalised interface, which other virtualisation platforms can use.
  oVirt has been transitioned to this interface as part of the
  refactoring, which means that any if the new oVirt SSO implementation
  is broken, it could break users running in oVirt.

  VMware's patches also use the new generalised interface, which is much
  simpler than before, and it has been tested internally by VMware.
  There was a very long review process with upstream GNOME, which ironed
  out all of their concerns.

  I have been reviewing the code along the way, and I am confident that
  it will not cause any regressions. If a regression did occur, then it
  would break SSO functionality only.

  [Other Information]

  Upstream Issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1983
  Upstream merge-request: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/915

  Commits:

  commit 809f820cd4a4eebb120ab5dde3f1985d35bcb540 
  Author: yun341 <5933...@qq.com>
  Date: Sat, 4 Jan 2020 00:31:15 +0800
  Subject: gdm: Refactor oVirt to a generic CredentialManager interface
  Link: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/809f820cd4a4eebb120ab5dde3f1985d35bcb540

  commit 4ea0fca4fc09ffd6e0b6994ee1354f07f7d5d2b5
  Author: yun341 <5933...@qq.com>
  Date: Thu, 2 Jul 2020 06:54:55 +0800
  Subject: gdm: Introduce vmware credential manager for pre-authenticated logins
  Link: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/4ea0fca4fc09ffd6e0b6994ee1354f07f7d5d2b5

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1886592/+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 1887478] Re: missing symlinks for login and logout files used by gnome

2020-07-17 Thread Yousuf 'Jay' Philips

Debian is upstream to Ubuntu. Here is a MR at freedesktop.org.
https://gitlab.freedesktop.org/xdg/xdg-sound-theme/-/merge_requests/1

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

Title:
  missing symlinks for login and logout files used by gnome

Status in sound-theme-freedesktop package in Ubuntu:
  Triaged

Bug description:
  Merge request submitted upstream in Debian to fix the issue.
  https://salsa.debian.org/gnome-team/sound-theme-freedesktop/-/merge_requests/1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1887478/+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 304393] Re: rpcbind grabs ports used by other daemons such as cupsd

2020-07-17 Thread Dan Streetman

** Tags added: sts

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

Title:
  rpcbind grabs ports used by other daemons such as cupsd

Status in cups package in Ubuntu:
  Invalid
Status in rpcbind package in Ubuntu:
  Fix Released
Status in rpcbind source package in Xenial:
  In Progress
Status in rpcbind source package in Bionic:
  In Progress
Status in rpcbind package in Debian:
  Fix Released
Status in Fedora:
  Confirmed

Bug description:
  [impact]

  rpcbind binds to a 'random' reserved port at startup, which can
  conflict with the reserved port number for other applications that
  actually 'own' the reserved port number. One example is cups, which
  uses the reserved port 631.

  This prevents the actual 'owner' of the reserved port from starting,
  since it can't bind to its reserved port.

  Additionally, this can raise alarms from security monitoring software
  that does not expect programs to be listening on random reserved
  ports.

  [test case]

  start rpcbind and check which ports it is listening on, e.g.:

  $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc
  udp0  0 0.0.0.0:614 0.0.0.0:* 
  4678/rpcbind

  each time rpcbind is restarted, it will be listening to a different
  'random' port.

  [regression potential]

  this adds a way to disable rpcbind from listening to the 'random'
  port. any regression would likely prevent rpcbind from starting, or
  may cause problems with the interaction between rpcinfo and rpcbind,
  as rpcinfo may use the random reserved port in some cases, as detailed
  in the Debian bug.

  [scope]

  This is needed only for Bionic and earlier.

  In Focal and later, and in Debian, rpcbind defaults to not opening the
  random reserved port.  The admin can use the -r parameter to cause
  rpcbind to restore the old behavior of opening the random reserved
  port.

  [other info]

  Note that the -r parameter is a Debian addition, and the upstream
  rpcbind has disabled the random port functionality at build time;
  there is no runtime parameter to allow the admin to choose the
  behavior.

  Also, as discussed in the Debian bug, disabling this rpcbind 'feature'
  is known to cause problems for the rpcinfo program, which is why
  Debian introduced the -r parameter. So, when this -r parameter is
  backported to Bionic and earlier, we must retain the default behavior
  for those releases, which is for rpcbind to open the random reserved
  port.

  Thus, the patch for this will first backport the upstream patch that adds 
functionality to be able to disable the 'remote calls' function, and also 
backports the debian patch to change that from a compile-time to run-time 
option. Then, another patch is added, which changes the default back to the 
behavior of x/b, which is for remote calls to be enabled by default,
  and also adds a check for the existence of an environment variable 
"RPCBIND_RMTCALLS_DEFAULT_DISABLED" which, if defined (to anything), will 
change the default to disabled.

  This allows 1) retaining the existing default behavior of rpcbind in x
  and b, while also 2) providing a mechanism to change that default for
  anyone who does *not* want remote calls to be enabled, and 3) allowing
  the mechanism to change the default to remain in place after an
  upgrade to Focal. Using the environment variable, instead of changing
  or adding the cmdline parameter, allows anyone using the variable to
  disable the remote calls default to upgrade to Focal without breaking
  rpcbind. After the upgrade to Focal, the environment variable (defined
  in /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be
  ignored without any change needed to the rpcbind package in Focal or
  later.

  [original description]

  As this backports that functionality, it

  Binary package hint: cups

  cups 1.3.9-2ubuntu4
  From /var/log/cups/error_log:
  cups: unable to bind socket for address 127.0.0.1:631 - Address already in 
use.

  Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd
  when started.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+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 1764156] Re: Make all gnome-session-properties AppStream strings translatable

2020-07-17 Thread Gunnar Hjalmarsson

Thanks for your report!

What happened was that the AppStream metadata generator started to pull
info from existing .desktop files for packages without explicit metainfo
files. The gnome-startup-applications binary package is one of a myriad
of such packages.

https://appstream.ubuntu.com/focal/main/issues/gnome-startup-
applications.html

Since gnome-session-properties.desktop does not include a Description
field, and as explained at the linked page, AppStream pulls that info
from the package description, which is not translated.

So adding an AppStream metainfo file might help. However, the gnome-
session source package is in main, and I'm not sure if the AppStream
metadata generator has the ability to get translations from the
/usr/share/locale-langpack directory. When looking at update manager,
for instance, there is a gettext-data-not-found warning which indicates
otherwise.

https://appstream.ubuntu.com/focal/main/issues/update-manager.html

** Changed in: gnome-session (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Make all gnome-session-properties AppStream strings translatable

Status in Ubuntu Translations:
  New
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  The AppStream metadata were recently added for "Startup Applications"
  (gnome-session-properties) in Ubuntu 18.04; it would be nice if "The
  Startup Applications Preferences app allows configuring applications
  to run automatically when logging in to your desktop. This app
  complies with the FreeDesktop.org Desktop Application Autostart
  Specification so it will work even if your chosen desktop is not
  GNOME." string was translatable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1764156/+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 1558886] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()

Even though the trace is quite different, I'm confident that this is due
to the same root cause of lp:1846403 and
https://gitlab.gnome.org/GNOME/mutter/-/issues/1345

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1345
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1345

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1345
   Importance: Unknown
   Status: Unknown

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

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

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 16.04 LTS Beta release. Was using gnome-shell and using
  Chrome web browser when computer became unresponsive to any commands
  or mouse clicks. About 3-4 minutes later a crash report popped up on
  my screen. I clicked report and now I am reporting this as a new bug
  as I have never had this happen before on previous versions of Ubuntu.
  I was attempting to copy and save an image from Google Chrome when
  this happened.

  
  Similar crash still happening, as per 
https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa

  
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable
  google-chrome-stable:
    Installed: 49.0.2623.75-1
    Candidate: 49.0.2623.75-1
    Version table:
   *** 49.0.2623.75-1 100
  100 /var/lib/dpkg/status

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 17 22:20:56 2016
  DisplayManager: lightdm
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-24 (22 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f634ba78320:mov0xe0(%rdi),%rax
   PC (0x7f634ba78320) ok
   source "0xe0(%rdi)" (0x00e0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   clutter_x11_handle_event () from 
/usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/libmutter.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (14 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

** Tags added: focal

** Description changed:

  Using Ubuntu 16.04 LTS Beta release. Was using gnome-shell and using
  Chrome web browser when computer became unresponsive to any commands or
  mouse clicks. About 3-4 minutes later a crash report popped up on my
  screen. I clicked report and now I am reporting this as a new bug as I
  have never had this happen before on previous versions of Ubuntu. I was
  attempting to copy and save an image from Google Chrome when this
  happened.
  
+ 
+ Similar crash still happening, as per 
https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa
+ 
+ 
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04
  
  lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable
  google-chrome-stable:
-   Installed: 49.0.2623.75-1
-   Candidate: 49.0.2623.75-1
-   Version table:
-  *** 49.0.2623.75-1 100
- 100 /var/lib/dpkg/status
+   Installed: 49.0.2623.75-1
+   Candidate: 49.0.2623.75-1
+   Version table:
+  *** 49.0.2623.75-1 100
+ 100 /var/lib/dpkg/status
  
- ProblemType: Crash
- DistroRelease: Ubuntu 16.04
+ ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 17 22:20:56 2016
  DisplayManager: lightdm
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-24 (22 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
-  LANGUAGE=en_US
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x7f634ba78320:mov0xe0(%rdi),%rax
-  PC (0x7f634ba78320) ok
-  source "0xe0(%rdi)" (0x00e0) not located in a known VMA region (needed 
readable region)!
-  destination "%rax" ok
+  Segfault happened at: 0x7f634ba78320:mov0xe0(%rdi),%rax
+  PC (0x7f634ba78320) ok
+  source "0xe0(%rdi)" (0x00e0) not located in a known VMA region (needed 
readable region)!
+  destination "%rax" ok
  SegvReason: reading NULL VMA
- Signal: 11
- SourcePackage: gnome-shell
+ Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
-  ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
-  clutter_x11_handle_event () from 
/usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
-  ?? () from /usr/lib/libmutter.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
+  clutter_x11_handle_event () from 
/usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
+  ?? () from /usr/lib/libmutter.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (14 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 16.04 LTS Beta release. Was using gnome-shell and using
  Chrome web browser when computer became unresponsive to any commands
  or mouse clicks. About 3-4 minutes later a crash report popped up on
  my screen. I clicked report and now I am reporting this as a new bug
  as I have never had this happen before on previous versions of Ubuntu.
  I was attempting to copy and save an image from Google Chrome when
  this happened.

  
  Similar crash still happening, as per 
https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa

  
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable
  google-chrome-stable:
    Installed: 49.0.2623.75-1
    Candidate: 49.0.2623.75-1
    Version table:
   *** 49.0.2623.75-1 100
  100 /var/lib/dpkg/status

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 17 22:20:56 2016
  DisplayManager: lightdm
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-24 (22 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)

[Desktop-packages] [Bug 1558886] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()

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

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

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

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

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 16.04 LTS Beta release. Was using gnome-shell and using
  Chrome web browser when computer became unresponsive to any commands
  or mouse clicks. About 3-4 minutes later a crash report popped up on
  my screen. I clicked report and now I am reporting this as a new bug
  as I have never had this happen before on previous versions of Ubuntu.
  I was attempting to copy and save an image from Google Chrome when
  this happened.

  
  Similar crash still happening, as per 
https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa

  
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable
  google-chrome-stable:
    Installed: 49.0.2623.75-1
    Candidate: 49.0.2623.75-1
    Version table:
   *** 49.0.2623.75-1 100
  100 /var/lib/dpkg/status

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 17 22:20:56 2016
  DisplayManager: lightdm
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-24 (22 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f634ba78320:mov0xe0(%rdi),%rax
   PC (0x7f634ba78320) ok
   source "0xe0(%rdi)" (0x00e0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   clutter_x11_handle_event () from 
/usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/libmutter.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (14 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1558886/+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 1888005] [NEW] /usr/bin/gnome-shell:11:_clutter_input_device_reset_scroll_info:meta_seat_x11_translate_event:meta_clutter_backend_x11_translate_event:meta_x11_handle_event:hand

2020-07-17 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.36.3-1ubuntu1~20.04.2, the problem page at 
https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: focal groovy

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

Title:
  /usr/bin/gnome-
  
shell:11:_clutter_input_device_reset_scroll_info:meta_seat_x11_translate_event:meta_clutter_backend_x11_translate_event:meta_x11_handle_event:handle_host_xevent

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.36.3-1ubuntu1~20.04.2, the problem page at 
https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888005/+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 1857340] Re: Setting "IPv6 Method" to "Disable" does not disable IPv6

2020-07-17 Thread Bug Watch Updater

** Changed in: gnome-control-center
   Status: New => Fix Released

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

Title:
  Setting "IPv6 Method" to "Disable" does not disable IPv6

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Setting "IPv6 Method" to "Disable" does not disable IPv6

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 23 06:50:59 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-11-21 (31 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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-control-center/+bug/1857340/+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 1888005] Re: /usr/bin/gnome-shell:11:_clutter_input_device_reset_scroll_info:meta_seat_x11_translate_event:meta_clutter_backend_x11_translate_event:meta_x11_handle_event:handle

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

** This bug has been marked a duplicate of bug 1558886
   gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()

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

Title:
  /usr/bin/gnome-
  
shell:11:_clutter_input_device_reset_scroll_info:meta_seat_x11_translate_event:meta_clutter_backend_x11_translate_event:meta_x11_handle_event:handle_host_xevent

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.36.3-1ubuntu1~20.04.2, the problem page at 
https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888005/+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 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

2020-07-17 Thread Jpodjarny

I lost my sound after update:
orge2@jorge-Mate-20-4:~$ pactl --version
pactl 13.99.1
Compilado con libpulse 13.99.0
Linked con libpulse 13.99.0
jorge2@jorge-Mate-20-4:~$ pactl list short sinks
0   auto_null   module-null-sink.c  s16le 2ch 44100Hz   
SUSPENDED
jorge2@jorge-Mate-20-4:~$ lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)

jorge2@jorge-Mate-20-4:~$ pacmd dump
### Configuration dump generated at Fri Jul 17 14:53:48 2020

### Configuration dump generated at Fri Jul 17 15:24:44 2020

load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore
load-module module-augment-properties
load-module module-switch-on-port-available
load-module module-switch-on-connect
load-module module-udev-detect
load-module module-alsa-card device_id="0" name="pci-_00_1b.0" 
card_name="alsa_card.pci-_00_1b.0" namereg_fail=false tsched=yes 
fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes 
avoid_resampling=no card_properties="module-udev-detect.discovered=1"
load-module module-native-protocol-unix
load-module module-default-device-restore
load-module module-always-sink
load-module module-null-sink sink_name=auto_null 
sink_properties='device.description="Salida Ficticia"'
load-module module-intended-roles
load-module module-suspend-on-idle
load-module module-console-kit
load-module module-systemd-login
load-module module-position-event-sounds
load-module module-role-cork
load-module module-snap-policy
load-module module-filter-heuristics
load-module module-filter-apply
load-module module-x11-publish display=:0 xauthority=/home/jorge2/.Xauthority
load-module module-x11-cork-request display=:0 
xauthority=/home/jorge2/.Xauthority
load-module module-x11-xsmp display=:0 xauthority=/home/jorge2/.Xauthority 
session_manager=local/jorge-Mate-20-4:@/tmp/.ICE-unix/1812,unix/jorge-Mate-20-4:/tmp/.ICE-unix/1812
load-module module-cli-protocol-unix

set-sink-volume auto_null 0x101b3
set-sink-mute auto_null no
suspend-sink auto_null yes

set-source-volume auto_null.monitor 0x1
set-source-mute auto_null.monitor no
suspend-source auto_null.monitor yes

set-card-profile alsa_card.pci-_00_1b.0 off

set-default-sink auto_null
set-default-source auto_null.monitor

### EOF
jorge2@jorge-Mate-20-4:~$

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 304393] Re: rpcbind grabs ports used by other daemons such as cupsd

2020-07-17 Thread Dan Streetman

** Description changed:

  [impact]
  
  rpcbind binds to a 'random' reserved port at startup, which can conflict
  with the reserved port number for other applications that actually 'own'
  the reserved port number. One example is cups, which uses the reserved
  port 631.
  
  This prevents the actual 'owner' of the reserved port from starting,
  since it can't bind to its reserved port.
  
  Additionally, this can raise alarms from security monitoring software
  that does not expect programs to be listening on random reserved ports.
  
  [test case]
  
  start rpcbind and check which ports it is listening on, e.g.:
  
  $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc
- udp0  0 0.0.0.0:614 0.0.0.0:* 
  4678/rpcbind
+ udp0  0 0.0.0.0:614 0.0.0.0:* 
  4678/rpcbind
  
  each time rpcbind is restarted, it will be listening to a different
  'random' port.
  
  [regression potential]
  
- this adds a method to disable rpcbind from listening to the 'random'
- port. any regression would likely prevent rpcbind from starting, or may
- cause problems with the interaction between rpcinfo and rpcbind, as
- rpcinfo may use the random reserved port in some cases, as detailed in
- the Debian bug.
+ this adds a way to disable rpcbind from listening to the 'random' port.
+ any regression would likely prevent rpcbind from starting, or may cause
+ problems with the interaction between rpcinfo and rpcbind, as rpcinfo
+ may use the random reserved port in some cases, as detailed in the
+ Debian bug.
  
  [scope]
  
  This is needed only for Bionic and earlier.
  
  In Focal and later, and in Debian, rpcbind defaults to not opening the
  random reserved port.  The admin can use the -r parameter to cause
  rpcbind to restore the old behavior of opening the random reserved port.
  
  [other info]
  
  Note that the -r parameter is a Debian addition, and the upstream
  rpcbind has disabled the random port functionality at build time; there
  is no runtime parameter to allow the admin to choose the behavior.
  
  Also, as discussed in the Debian bug, disabling this rpcbind 'feature'
  is known to cause problems for the rpcinfo program, which is why Debian
  introduced the -r parameter. So, when this -r parameter is backported to
  Bionic and earlier, we must retain the default behavior for those
  releases, which is for rpcbind to open the random reserved port.
  
- TBD: specific method to disable rmtcalls in backport
+ Thus, the patch for this will first backport the upstream patch that adds 
functionality to be able to disable the 'remote calls' function, and also 
backports the debian patch to change that from a compile-time to run-time 
option. Then, another patch is added, which changes the default back to the 
behavior of x/b, which is for remote calls to be enabled by default,
+ and also adds a check for the existence of an environment variable 
"RPCBIND_RMTCALLS_DEFAULT_DISABLED" which, if defined (to anything), will 
change the default to disabled.
  
+ This allows 1) retaining the existing default behavior of rpcbind in x
+ and b, while also 2) providing a mechanism to change that default for
+ anyone who does *not* want remote calls to be enabled, and 3) allowing
+ the mechanism to change the default to remain in place after an upgrade
+ to Focal. Using the environment variable, instead of changing or adding
+ the cmdline parameter, allows anyone using the variable to disable the
+ remote calls default to upgrade to Focal without breaking rpcbind. After
+ the upgrade to Focal, the environment variable (defined in
+ /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored
+ without any change needed to the rpcbind package in Focal or later.
  
  [original description]
  
  As this backports that functionality, it
  
  Binary package hint: cups
  
  cups 1.3.9-2ubuntu4
  From /var/log/cups/error_log:
  cups: unable to bind socket for address 127.0.0.1:631 - Address already in 
use.
  
  Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when
  started.

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

Title:
  rpcbind grabs ports used by other daemons such as cupsd

Status in cups package in Ubuntu:
  Invalid
Status in rpcbind package in Ubuntu:
  Fix Released
Status in rpcbind source package in Xenial:
  In Progress
Status in rpcbind source package in Bionic:
  In Progress
Status in rpcbind package in Debian:
  Fix Released
Status in Fedora:
  Confirmed

Bug description:
  [impact]

  rpcbind binds to a 'random' reserved port at startup, which can
  conflict with the reserved port number for other applications that
  actually 'own' the reserved port number. One example is cups, which
  uses the reserved port 631.

  This prevents the actual 'owner' of the reserved

[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system

2020-07-17 Thread Bob Briscoe

Att'd: nautilus extensions installed. The only one I'm aware of having
explicitly installed is nautilus-image-converter (and of course
nautilus-dbgsym).

** Attachment added: "nautilus extensions installed re. bug #1887315"

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+attachment/5393608/+files/20200717-ra-nautilus-extensions.txt

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

Title:
Nautilus crashes while over-typing search term on remote smb file
system

Status in nautilus package in Ubuntu:
Incomplete

Bug description:
==Impact==

nautilus crashes while typing the term to search a remote directory
within an NT file system over the smb protocol. The problem may affect
other remote file systems or protocols, but I have only tested these.

Repeatable.

==How to repeat==

1. Open Nautilus
2. In the sidebar, click Other Locations
3. Type smb://example/share into the 'Connect to server' field or select an
existing share URI
4. Click Connect
5. Optionally, when the contents of the share appears, select any depth of
sub-directories.
6. Click the search icon and type a search string
7. Once the search results have returned, without closing the search box,
select the previous search term and over-type another search term.

Nautilus crashes.

Typically, prior to the window disappearing the graphics freezes
within the search field showing both the previous and the current
search terms on top of each other.

Often it is necessary to kill the nautilus process and/or reboot the
smb daemon on the remote machine before being able to use the smb
share again.

Before typing a second search term, if instead of over-typing, you
delete the selection either i) with the key; or ii) clicking
the (x) to clear the field; or iii) clicking the search icon twice to
remove and reinstate the search field; it is possible to search for a
second term without crashing.

It is possible that the crash depends on how fast the search term is
typed, because nautilus starts searching as you type. I have tried to
paste a search term over an existing term, which usually seems to work
without crashing. On the other hand, I have had nautilus crash when
typing a search term after having explicitly cleared the search field,
but before nautilus has displayed the full contents of the directory
again (about 150 files).

I have not had nautilus crash when over-typing the search field for a
local file system, whether ntfs or ext3.

==Related bugs==

Bug #1795028 seems to be identical, and claims to have been fixed in
package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to
be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains
more precisely how to reproduce the crash.

==Crash Reports==

A typical crash report from my system is here:
https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 12 21:03:59 2020
InstallationDate: Installed on 2020-06-03 (38 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+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 1887998] [NEW] Update to 3.36.4 and SRU it

Public bug reported:

[ Impact ]

That's the current GNOME stable update, including some fixes and translation 
updates
https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.4

[ Test case ]

The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

GNOME Shell and its components should continue working

[ Regression potential ]

There have been fixes in X11 screencasting and touch-interaction, so
ensure there are no problems with those.

** Affects: mutter (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

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

Title:
  Update to 3.36.4 and SRU it

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.4

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  [ Regression potential ]

  There have been fixes in X11 screencasting and touch-interaction, so
  ensure there are no problems with those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/+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 1760849] Re: Login screen appears on only one monitor and it's not the one I want

2020-07-17 Thread Paul White

** Tags added: focal

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

Title:
  Login screen appears on only one monitor and it's not the one I want

Status in gdm:
  Unknown
Status in gdm3 package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Upstream bugs:
  https://gitlab.gnome.org/GNOME/gdm/issues/168
  https://gitlab.gnome.org/GNOME/gdm/issues/183
  https://gitlab.gnome.org/GNOME/gdm/issues/195
  https://gitlab.gnome.org/GNOME/gdm/issues/319
  https://gitlab.gnome.org/GNOME/gdm/issues/372

  The Ubuntu login screen is tiled on all displays, not mirrored, making
  it nearly impossible to login when using an external monitor if the
  laptop screen is not visible.

  There appears to be no available control to alter the display settings
  of the login screen. Prior to bionic, the controls followed the mouse
  onto different displays so you could login by giving the mouse a swipe
  to the right to get the controls to appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 22:13:53 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1760849/+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 1672931] Re: [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of native GTK/Qt (and so menus don't appear in the titlebar)

2020-07-17 Thread Christopher Townsend

** Changed in: libertine/devel
   Status: In Progress => Triaged

** Changed in: libertine/devel
 Assignee: Christopher Townsend (townsend) => (unassigned)

** Changed in: libertine/devel
Milestone: 1.8 => None

** Changed in: libertine/trunk
Milestone: 1.8 => None

** Changed in: ubuntu-app-launch (Ubuntu)
   Status: In Progress => Triaged

** Changed in: ubuntu-app-launch (Ubuntu)
 Assignee: Christopher Townsend (townsend) => (unassigned)

** Changed in: xorg-server (Ubuntu)
   Status: In Progress => Triaged

** Changed in: xorg-server (Ubuntu)
 Assignee: Christopher Townsend (townsend) => (unassigned)

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

Title:
  [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of
  native GTK/Qt (and so menus don't appear in the titlebar)

Status in Canonical System Image:
  Confirmed
Status in Libertine:
  Triaged
Status in Libertine devel series:
  Triaged
Status in Libertine trunk series:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in libertine package in Ubuntu:
  Triaged
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Qt & GTK apps on Unity8 are defaulting to Xmir instead of native
  GTK/Qt on Mir.

  I noticed a slight change in appearance and performance, but also:

  dan  25410  0.1  0.2 423316 38996 ?Sl   11:14   0:00 Xmir 
-rootless -displayfd 3 -mir org.gnome.Calculator
  dan  25456  1.8  0.5 606084 91736 ?Sl   11:14   0:03 Xmir 
-rootless -displayfd 3 -mir org.gnome.Nautilus
  dan  25611  1.7  0.2 345312 35520 ?Sl   11:18   0:00 Xmir 
-rootless -displayfd 3 -mir webbrowser-app_webbrowser-app_10

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672931/+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 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working

2020-07-17 Thread Marcelo Pires

In addition, After closing all applications and trying, the sound works
again.

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

Title:
  [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When you start playing some audio, the sound disappears.

  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
Subsystem: ASUSTeK Computer Inc. M5A78L LE
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  
  uname -a
  Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  alsa-info

  
  !!
  !!ALSA Information Script v 0.4.65
  !!

  !!Script ran on: Fri Jun 19 13:38:12 UTC 2020

  
  !!Linux Distribution
  !!--

  Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu
  20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu
  20.04 LTS" HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies
  /privacy-policy" UBUNTU_CODENAME=focal

  
  !!DMI Information
  !!---

  Manufacturer:  System manufacturer
  Product Name:  System Product Name
  Product Version:   System Version
  Firmware Version:  1201   
  Board Vendor:  ASUSTeK Computer INC.
  Board Name:M5A78L-M LX/BR

  
  !!ACPI Device Status Information
  !!---

  /sys/bus/acpi/devices/ATK0110:00/status15
  /sys/bus/acpi/devices/PNP0103:00/status15
  /sys/bus/acpi/devices/PNP0400:00/status15
  /sys/bus/acpi/devices/PNP0501:00/status15
  /sys/bus/acpi/devices/PNP0C0C:00/status11
  /sys/bus/acpi/devices/PNP0C0F:00/status9
  /sys/bus/acpi/devices/PNP0C0F:01/status9
  /sys/bus/acpi/devices/PNP0C0F:02/status9
  /sys/bus/acpi/devices/PNP0C0F:03/status9
  /sys/bus/acpi/devices/PNP0C0F:04/status9
  /sys/bus/acpi/devices/PNP0C0F:05/status9
  /sys/bus/acpi/devices/PNP0C0F:06/status9
  /sys/bus/acpi/devices/PNP0C0F:07/status9
  /sys/bus/acpi/devices/device:20/status 15
  /sys/bus/acpi/devices/device:21/status 15

  
  !!Kernel Information
  !!--

  Kernel release:5.4.0-37-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes

  
  !!ALSA Version
  !!

  Driver version: k5.4.0-37-generic
  Library version:1.2.3
  Utilities version:  1.2.2

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xfe9f4000 irq 16

  
  !!PCI Soundcards installed in the system
  !!--

  00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 
Azalia (Intel HDA) [1002:4383]
Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445]

  
  !!Modprobe options (Sound related)
  !!

  snd_pcsp: index=-2
  snd_usb_audio: index=-2
  snd_atiixp_modem: index=-2
  snd_intel8x0m: index=-2
  snd_via82xx_modem: index=-2
  snd_atiixp_modem: index=-2
  snd_intel8x0m: index=-2
  snd_via82xx_modem: index=-2
  snd_usb_audio: index=-2
  snd_usb_caiaq: index=-2
  snd_usb_ua101: index=-2
  snd_usb_us122l: index=-2
  snd_usb_usx2y: index=-2
  snd_cmipci: mpu_port=0x330 fm_port=0x388
  snd_pcsp: index=-2
  snd_usb_audio: index=-2
  snd_hda_intel: model=auto
  snd_hda_intel: dmic detect=0

  
  !!Loaded sound module options
  !!---

  !!Module: snd_hda_intel
align_buffer_size : -1
bdl_pos_adj : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
beep_mode : 
N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N
dmic_detect : Y
enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
enable_msi : -1
id : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
index : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
jackpoll_ms :

[Desktop-packages] [Bug 1760849] Re: Login screen appears on only one monitor and it's not the one I want

2020-07-17 Thread Ponnuvel Palaniyappan

This still happens on Ubuntu 20.04 (Focal), too. In my case, I have one
external monitor which is mirrored. But the login screen appears only on
the laptop's screen but not on the external monitor's display.

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

Title:
  Login screen appears on only one monitor and it's not the one I want

Status in gdm:
  Unknown
Status in gdm3 package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Upstream bugs:
  https://gitlab.gnome.org/GNOME/gdm/issues/168
  https://gitlab.gnome.org/GNOME/gdm/issues/183
  https://gitlab.gnome.org/GNOME/gdm/issues/195
  https://gitlab.gnome.org/GNOME/gdm/issues/319
  https://gitlab.gnome.org/GNOME/gdm/issues/372

  The Ubuntu login screen is tiled on all displays, not mirrored, making
  it nearly impossible to login when using an external monitor if the
  laptop screen is not visible.

  There appears to be no available control to alter the display settings
  of the login screen. Prior to bionic, the controls followed the mouse
  onto different displays so you could login by giving the mouse a swipe
  to the right to get the controls to appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 22:13:53 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1760849/+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 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working

2020-07-17 Thread Marcelo Pires

Hello,

I opened YouTube, using chrome, and there is no sound. I tried firefox,
and I was also unsuccessful! The speakers are making little pops!

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

Title:
  [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When you start playing some audio, the sound disappears.

  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
Subsystem: ASUSTeK Computer Inc. M5A78L LE
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  
  uname -a
  Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  alsa-info

  
  !!
  !!ALSA Information Script v 0.4.65
  !!

  !!Script ran on: Fri Jun 19 13:38:12 UTC 2020

  
  !!Linux Distribution
  !!--

  Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu
  20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu
  20.04 LTS" HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies
  /privacy-policy" UBUNTU_CODENAME=focal

  
  !!DMI Information
  !!---

  Manufacturer:  System manufacturer
  Product Name:  System Product Name
  Product Version:   System Version
  Firmware Version:  1201   
  Board Vendor:  ASUSTeK Computer INC.
  Board Name:M5A78L-M LX/BR

  
  !!ACPI Device Status Information
  !!---

  /sys/bus/acpi/devices/ATK0110:00/status15
  /sys/bus/acpi/devices/PNP0103:00/status15
  /sys/bus/acpi/devices/PNP0400:00/status15
  /sys/bus/acpi/devices/PNP0501:00/status15
  /sys/bus/acpi/devices/PNP0C0C:00/status11
  /sys/bus/acpi/devices/PNP0C0F:00/status9
  /sys/bus/acpi/devices/PNP0C0F:01/status9
  /sys/bus/acpi/devices/PNP0C0F:02/status9
  /sys/bus/acpi/devices/PNP0C0F:03/status9
  /sys/bus/acpi/devices/PNP0C0F:04/status9
  /sys/bus/acpi/devices/PNP0C0F:05/status9
  /sys/bus/acpi/devices/PNP0C0F:06/status9
  /sys/bus/acpi/devices/PNP0C0F:07/status9
  /sys/bus/acpi/devices/device:20/status 15
  /sys/bus/acpi/devices/device:21/status 15

  
  !!Kernel Information
  !!--

  Kernel release:5.4.0-37-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes

  
  !!ALSA Version
  !!

  Driver version: k5.4.0-37-generic
  Library version:1.2.3
  Utilities version:  1.2.2

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xfe9f4000 irq 16

  
  !!PCI Soundcards installed in the system
  !!--

  00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 
Azalia (Intel HDA) [1002:4383]
Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445]

  
  !!Modprobe options (Sound related)
  !!

  snd_pcsp: index=-2
  snd_usb_audio: index=-2
  snd_atiixp_modem: index=-2
  snd_intel8x0m: index=-2
  snd_via82xx_modem: index=-2
  snd_atiixp_modem: index=-2
  snd_intel8x0m: index=-2
  snd_via82xx_modem: index=-2
  snd_usb_audio: index=-2
  snd_usb_caiaq: index=-2
  snd_usb_ua101: index=-2
  snd_usb_us122l: index=-2
  snd_usb_usx2y: index=-2
  snd_cmipci: mpu_port=0x330 fm_port=0x388
  snd_pcsp: index=-2
  snd_usb_audio: index=-2
  snd_hda_intel: model=auto
  snd_hda_intel: dmic detect=0

  
  !!Loaded sound module options
  !!---

  !!Module: snd_hda_intel
align_buffer_size : -1
bdl_pos_adj : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
beep_mode : 
N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N
dmic_detect : Y
enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
enable_msi : -1
id : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
index :

[Desktop-packages] [Bug 1887824] Re: License wrong in software list

2020-07-17 Thread Didi Kohen

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

seems it has been fixed today

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

Title:
  License wrong in software list

Status in snap-store-desktop:
  New
Status in gucharmap package in Ubuntu:
  New

Bug description:
  In the package page in the Ubuntu software center, this appears as 
proprietary, it should be GPLv3
  Checked on version 1:13.0.1-1 on 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store-desktop/+bug/1887824/+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 1883924] Re: Ubuntu.exe will not be detected properly if other LTS version is installed

2020-07-17 Thread Patrick Wu

I have tested 2.3.6-0ubuntu2~20.04.0 on ubuntu.exe with ubuntu 20.04,
18.04 and 16.04 installed alongside (ubuntu2004.exe, ubuntu1804.exe,
ubuntu1604.exe). As the screenshot shown, the problem of wrong basename
is now solved.

** Attachment added: "Annotation 2020-07-18 003041.png"
   
https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883924/+attachment/5393594/+files/Annotation%202020-07-18%20003041.png

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

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

Title:
  Ubuntu.exe will not be detected properly if other LTS version is
  installed

Status in wslu package in Ubuntu:
  Fix Released
Status in wslu source package in Xenial:
  New
Status in wslu source package in Bionic:
  New
Status in wslu source package in Focal:
  Fix Committed
Status in wslu source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This affects all wslu tools on all releases when using from the Ubuntu
  app from Microsoft Store. When other LTS version of app is installed
  from Microsoft Store, baseexec generated by wslu on Ubuntu app will
  not be using ubuntu.exe but other LTS release apps (such as
  ubuntu1804.exe)

  [Test Case]

   * Install Ubuntu and Ubuntu 18.04 LTS from Microsoft Store.
   * run any wslu tools (like wslfetch --help)
   * Verify that ~/.config/wslu/baseexec contains the path to ubuntu.exe

  [Regression Potential]

  This patch will try to regenerate  ~/.config/wslu/baseexec when trying
  to execute any wslu commands (like wslfetch). Potential regressions
  would be a result of  ~/.config/wslu/baseexec not regenerated
  properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883924/+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 1764156] Re: Make all gnome-session-properties AppStream strings translatable

2020-07-17 Thread AsciiWolf

** Tags added: focal

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

Title:
  Make all gnome-session-properties AppStream strings translatable

Status in Ubuntu Translations:
  New
Status in gnome-session package in Ubuntu:
  New

Bug description:
  The AppStream metadata were recently added for "Startup Applications"
  (gnome-session-properties) in Ubuntu 18.04; it would be nice if "The
  Startup Applications Preferences app allows configuring applications
  to run automatically when logging in to your desktop. This app
  complies with the FreeDesktop.org Desktop Application Autostart
  Specification so it will work even if your chosen desktop is not
  GNOME." string was translatable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1764156/+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 1887263] Re: nautilus freezes possibly in connection w/ samba share mounted/unmounted

Closing then but feel free to reopen so we can investigate more if it
happens again

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

Title:
  nautilus freezes possibly in connection w/ samba share
  mounted/unmounted

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  test steps:
  - mouunt samba share w/:
  smb://host/share
  - open local disc w/ personal folder
  - scroll directory e. g. w/ show hidden files enabled in order to get a long 
list

  expected result:
  directory scrolls up and down

  actual result:
  scrolling freezes for some seconds before scrolling completes:
  - no directory selection appears until after freeze is over
  - only selection possible is the mounted samba share, which returns to the 
top level directory of the share

  leder@home-ryzen-desktop:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  leder@home-ryzen-desktop:~$ apt-cache policy nautilus
  nautilus:
Installiert:   1:3.36.3-0ubuntu1
Installationskandidat: 1:3.36.3-0ubuntu1
Versionstabelle:
   *** 1:3.36.3-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.36.1.1-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  Uname: Linux 5.6.19-050619-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 04:32:18 2020
  InstallationDate: Installed on 2020-06-22 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887263/+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 1881909] Re: Screen tearing with Nvidia Optimus

2020-07-17 Thread Bradley Pearce

This issue effected me also, and I fixed it by following these steps:

http://ubuntuhandbook.org/index.php/2018/07/fix-screen-tearing-
ubuntu-18-04-optimus-laptops/

Does this help for you?

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

Title:
  Screen tearing with Nvidia Optimus

Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  I have screen tearing when using nvidia card with 390 driver, affect
  browsers such as firefox and chromium also desktop since I have screen
  tearing when moving window around.

  I have no such problem when using using 18.04.4 and nvidia card with
  390 driver. Intel graphic have no such problem weather in 18.04 or
  20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  3 21:18:49 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
   NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652]
  InstallationDate: Installed on 2020-06-01 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK Computer Inc. K43SD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=8f02391a-a313-4598-b702-db7eccd55312 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K43SD.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K43SD
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK43SD.208:bd08/10/2012:svnASUSTeKComputerInc.:pnK43SD:pvr1.0:rvnASUSTeKComputerInc.:rnK43SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K43SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1881909/+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 1881909] Re: Screen tearing with Nvidia Optimus

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

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Screen tearing with Nvidia Optimus

Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  I have screen tearing when using nvidia card with 390 driver, affect
  browsers such as firefox and chromium also desktop since I have screen
  tearing when moving window around.

  I have no such problem when using using 18.04.4 and nvidia card with
  390 driver. Intel graphic have no such problem weather in 18.04 or
  20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  3 21:18:49 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
   NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652]
  InstallationDate: Installed on 2020-06-01 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK Computer Inc. K43SD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=8f02391a-a313-4598-b702-db7eccd55312 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K43SD.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K43SD
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK43SD.208:bd08/10/2012:svnASUSTeKComputerInc.:pnK43SD:pvr1.0:rvnASUSTeKComputerInc.:rnK43SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K43SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1881909/+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 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system

Thanks, the backtrace indicates it's hitting and issue in libffi which
usually indicates use of bindings ... do you have any nautilus extension
installed? it's usually sign the issue is due to one of those (or due to
nautilus-python)

What's the output of 
$ dpkg -l | grep nautilus ?

> I would like to give review comments on the DebuggingProgramCrash
instructions. I had to guess what was meant on a number of points.
Where's the appropriate place to post a review?

Writing a post on https://discourse.ubuntu.com/ would be a nice starting
point

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

Title:
  Nautilus crashes while over-typing search term on remote smb file
  system

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  ==Impact==

  nautilus crashes while typing the term to search a remote directory
  within an NT file system over the smb protocol. The problem may affect
  other remote file systems or protocols, but I have only tested these.

  Repeatable.

  ==How to repeat==

  1. Open Nautilus
  2. In the sidebar, click Other Locations
  3. Type smb://example/share into the 'Connect to server' field or select an 
existing share URI
  4. Click Connect
  5. Optionally, when the contents of the share appears, select any depth of 
sub-directories.
  6. Click the search icon and type a search string
  7. Once the search results have returned, without closing the search box, 
select the previous search term and over-type another search term.

  Nautilus crashes.

  Typically, prior to the window disappearing the graphics freezes
  within the search field showing both the previous and the current
  search terms on top of each other.

  Often it is necessary to kill the nautilus process and/or reboot the
  smb daemon on the remote machine before being able to use the smb
  share again.

  Before typing a second search term, if instead of over-typing, you
  delete the selection either i) with the  key; or ii) clicking
  the (x) to clear the field; or iii) clicking the search icon twice to
  remove and reinstate the search field; it is possible to search for a
  second term without crashing.

  It is possible that the crash depends on how fast the search term is
  typed, because nautilus starts searching as you type. I have tried to
  paste a search term over an existing term, which usually seems to work
  without crashing. On the other hand, I have had nautilus crash when
  typing a search term after having explicitly cleared the search field,
  but before nautilus has displayed the full contents of the directory
  again (about 150 files).

  I have not had nautilus crash when over-typing the search field for a
  local file system, whether ntfs or ext3.

  ==Related bugs==

  Bug #1795028 seems to be identical, and claims to have been fixed in
  package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to
  be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains
  more precisely how to reproduce the crash.

  ==Crash Reports==

  A typical crash report from my system is here:
  https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 21:03:59 2020
  InstallationDate: Installed on 2020-06-03 (38 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+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 1881909] Re: Screen tearing with Nvidia Optimus

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

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

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

Title:
  Screen tearing with Nvidia Optimus

Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  I have screen tearing when using nvidia card with 390 driver, affect
  browsers such as firefox and chromium also desktop since I have screen
  tearing when moving window around.

  I have no such problem when using using 18.04.4 and nvidia card with
  390 driver. Intel graphic have no such problem weather in 18.04 or
  20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  3 21:18:49 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
   NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652]
  InstallationDate: Installed on 2020-06-01 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK Computer Inc. K43SD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=8f02391a-a313-4598-b702-db7eccd55312 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K43SD.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K43SD
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK43SD.208:bd08/10/2012:svnASUSTeKComputerInc.:pnK43SD:pvr1.0:rvnASUSTeKComputerInc.:rnK43SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K43SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1881909/+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 1887263] Re: nautilus freezes possibly in connection w/ samba share mounted/unmounted

2020-07-17 Thread leder

Could not reproduce. Thank you for your attention, Sebastien!

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

Title:
  nautilus freezes possibly in connection w/ samba share
  mounted/unmounted

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  test steps:
  - mouunt samba share w/:
  smb://host/share
  - open local disc w/ personal folder
  - scroll directory e. g. w/ show hidden files enabled in order to get a long 
list

  expected result:
  directory scrolls up and down

  actual result:
  scrolling freezes for some seconds before scrolling completes:
  - no directory selection appears until after freeze is over
  - only selection possible is the mounted samba share, which returns to the 
top level directory of the share

  leder@home-ryzen-desktop:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  leder@home-ryzen-desktop:~$ apt-cache policy nautilus
  nautilus:
Installiert:   1:3.36.3-0ubuntu1
Installationskandidat: 1:3.36.3-0ubuntu1
Versionstabelle:
   *** 1:3.36.3-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.36.1.1-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  Uname: Linux 5.6.19-050619-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 04:32:18 2020
  InstallationDate: Installed on 2020-06-22 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887263/+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 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system

2020-07-17 Thread Bob Briscoe

gdb output attached.

When overtyping the search field in nautilus within gdb, it didn't crash
in the same way: the nautilus window hung (whereas without gdb nautilus
crashed). So I did -C in gdb as instructed. But then I got [Wait /
Force Quit] over the nautilus window and gdb had become unresponsive,
with the nautilus process as a defunct child.

So, I killed gdb, ran it again, and this time, once I had got nautilus
in its hung state, I completed the gdb output without using -C.

PS. I would like to give review comments on the DebuggingProgramCrash
instructions. I had to guess what was meant on a number of points. Where's the
appropriate place to post a review?

** Attachment added: "gdb output for nautilus bug #1887315"

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+attachment/5393586/+files/gdb-nautilus.txt

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

Title:
Nautilus crashes while over-typing search term on remote smb file
system

Status in nautilus package in Ubuntu:
Incomplete

Bug description:
==Impact==

Repeatable.

==How to repeat==

Nautilus crashes.

Typically, prior to the window disappearing the graphics freezes
within the search field showing both the previous and the current
search terms on top of each other.

Often it is necessary to kill the nautilus process and/or reboot the
smb daemon on the remote machine before being able to use the smb
share again.

I have not had nautilus crash when over-typing the search field for a
local file system, whether ntfs or ext3.

==Related bugs==

==Crash Reports==

A typical crash report from my system is here:
https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1

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

[Desktop-packages] [Bug 1887891] Re: dav/davs behind proxy doesn't work

2020-07-17 Thread Jean-Christophe

It's done :

https://gitlab.gnome.org/GNOME/gvfs/-/issues/495

** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #495
   https://gitlab.gnome.org/GNOME/gvfs/-/issues/495

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

Title:
  dav/davs behind proxy doesn't work

Status in gvfs package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 20.04 behind manual proxy.
  When I want to connect on a server with webdav, I have a message : "Erreur 
HTTP : Erreur de résolution de cloud.rochodc.com : Nom ou service inconnu" -> 
DNS Error Name ou service not known

  I can connect to a webdav server on my private network.

  I can connect to cloud.rochodc.com with Firefox and the proxy I use for the 
system.
  I can connect to cloud.rochodc.com with Ubuntu 18.04 with the same proxy and 
nautilus.

  Online account with parameters doesen't work at all.

  JC

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Fri Jul 17 08:22:05 2020
  InstallationDate: Installed on 2020-07-09 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1887891/+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 1887977] [NEW] Bluetooth headset is not reconnecting automatically if disconnected in between

2020-07-17 Thread Srikanth

Public bug reported:

Some times Bluetooth headset is not reconnecting automatically if
disconnected in between. I need to remove the bluetooth headset and
again pair it, then it is connecting.

1. Ubuntu Version - 20.04
2. Software version - bluez Installed: 5.53-0ubuntu3
3. Expected result : Every time when I restart the laptop or resume it the 
headset should connect automatically
4. Some times when I restart the laptop or resume the laptop, then eventhough 
headset is switched on bluetooth connection is not established. Instead if I 
remove the the headset from bluetooth list and again newly pair it with laptop 
then headset it connected. Verified the bluetooth head set by connecting it to 
mobile phone and other os like windows/mac os and it seems there is no issue 
with headset.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 17 19:58:10 2020
InstallationDate: Installed on 2020-05-04 (73 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD Webcam
 Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Nitro AN515-52
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=a609dea6-45d9-4ed8-8a46-ba56dae5a117 ro quiet splash
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2018
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.19
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Freed_CFS
dmi.board.vendor: CFL
dmi.board.version: V1.19
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.19
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.19:bd07/13/2018:svnAcer:pnNitroAN515-52:pvrV1.19:rvnCFL:rnFreed_CFS:rvrV1.19:cvnAcer:ct10:cvrV1.19:
dmi.product.family: Acer Nitro 5
dmi.product.name: Nitro AN515-52
dmi.product.sku: 
dmi.product.version: V1.19
dmi.sys.vendor: Acer
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 18:56:80:A6:CA:8D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:16973 acl:0 sco:0 events:2752 errors:0
TX bytes:678011 acl:0 sco:0 commands:2750 errors:0

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


** Tags: amd64 apport-bug focal

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

Title:
  Bluetooth headset is not reconnecting automatically if disconnected in
  between

Status in bluez package in Ubuntu:
  New

Bug description:
  Some times Bluetooth headset is not reconnecting automatically if
  disconnected in between. I need to remove the bluetooth headset and
  again pair it, then it is connecting.

  1. Ubuntu Version - 20.04
  2. Software version - bluez Installed: 5.53-0ubuntu3
  3. Expected result : Every time when I restart the laptop or resume it the 
headset should connect automatically
  4. Some times when I restart the laptop or resume the laptop, then eventhough 
headset is switched on bluetooth connection is not established. Instead if I 
remove the the headset from bluetooth list and again newly pair it with laptop 
then headset it connected. Verified the bluetooth head set by connecting it to 
mobile phone and other os like windows/mac os and it seems there is no issue 
with headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 17 19:58:10 2020
  InstallationDate: Installed on 2020-05-04 (73 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD Webcam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Nitro AN515-52
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=a609dea6-45d9-4ed8-8a46-ba56dae5a117 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: Insyde Corp.

[Desktop-packages] [Bug 1887976] [NEW] package libxt6 1:1.1.5-1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libxt6/changelog.Debian.gz' partilhado, que é diferente de outras inst

2020-07-17 Thread DALTON NUNES OLIVEIRA

Public bug reported:

error

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: libxt6 1:1.1.5-1
ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18
Uname: Linux 5.3.0-62-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.9
AptOrdering:
 libxt6:i386: Install
 NULL: ConfigurePending
Architecture: amd64
CompositorRunning: None
Date: Fri Jul 17 11:30:18 2020
DistUpgraded: 2020-07-09 12:07:43,389 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho 
“./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8))
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: nvidia, 450.57, 5.3.0-62-generic, x86_64: installed
DpkgTerminalLog:
 A preparar para desempacotar .../libxt6_1%3a1.1.5-1_i386.deb ...
 A descompactar libxt6:i386 (1:1.1.5-1) sobre (1:1.1.5-1) ...
 dpkg: erro ao processar o arquivo 
/var/cache/apt/archives/libxt6_1%3a1.1.5-1_i386.deb (--unpack):
  a tentar sobreescrever '/usr/share/doc/libxt6/changelog.Debian.gz' 
partilhado, que é diferente de outras instâncias do pacote libxt6:i386
ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libxt6/changelog.Debian.gz' partilhado, que é diferente de 
outras instâncias do pacote libxt6:i386
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1331]
 NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:1332]
InstallationDate: Installed on 2020-07-09 (7 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing
 Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 001 Device 004: ID 8087:0029 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Nitro AN515-54
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=a01360a5-1be4-42d8-acb6-d4a957e1c1c0 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4ubuntu0.1
SourcePackage: libxt
Title: package libxt6 1:1.1.5-1 failed to install/upgrade: a tentar 
sobreescrever '/usr/share/doc/libxt6/changelog.Debian.gz' partilhado, que é 
diferente de outras instâncias do pacote libxt6:i386
UpgradeStatus: Upgraded to eoan on 2020-07-09 (7 days ago)
dmi.bios.date: 05/11/2020
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.30
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Octavia_CFS
dmi.board.vendor: CFL
dmi.board.version: V1.30
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.30
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.30:bd05/11/2020:svnAcer:pnNitroAN515-54:pvrV1.30:rvnCFL:rnOctavia_CFS:rvrV1.30:cvnAcer:ct10:cvrV1.30:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN515-54
dmi.product.sku: 
dmi.product.version: V1.30
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-package eoan ubuntu

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

Title:
  package libxt6 1:1.1.5-1 failed to install/upgrade: a tentar
  sobreescrever '/usr/share/doc/libxt6/changelog.Debian.gz' partilhado,
  que é diferente de outras instâncias do pacote libxt6:i386

Status in libxt package in Ubuntu:
  New

Bug description:
  error

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: libxt6 1:1.1.5-1
  ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.9
  AptOrdering:
   libxt6:i386: Install
   NULL: ConfigurePending
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Jul 17 11:30:18 2020
  DistUpgraded: 2020-07-09 12:07:43,389 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho 
“./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:

[Desktop-packages] [Bug 1887970] [NEW] Core dump

2020-07-17 Thread Spr Base

Public bug reported:

latest snap on Ubuntu LTS
ver : 84.0.4147.89  
https://bugs.chromium.org/p/chromium/issues/detail?id=1106509#c2

Can you add debug symbols for libs? I'd be happy to provide a backtrace.

note, I am running with GPU disabled!

There are various SIGTRAP, SIGSEGV core dumps I can easily reproduce

Run this 50  times

chromium-browser --no-sandbox --incognito --virtual-time-budget=5000
--disable-gpu --headless --print-to-pdf=a.pdf http://www.chimpazee.jp >>
log.log 2>&1

other sites easy to reproduce if you run it 50 times

Sri-Langka.com
newdress.it
cwalkerart.net


What went wrong?
Failed to open /dev/null
[0716/091926.883693:WARNING:gpu_process_host.cc(1233)] The GPU process has 
crashed 1 time(s)
[0716/091926.889564:WARNING:gpu_process_host.cc(1233)] The GPU process has 
crashed 2 time(s)
[0716/091926.893577:WARNING:gpu_process_host.cc(1233)] The GPU process has 
crashed 3 time(s)
[0716/091926.894491:WARNING:gpu_process_host.cc(1233)] The GPU process has 
crashed 4 time(s)
[0716/091926.908258:WARNING:gpu_process_host.cc(1233)] The GPU process has 
crashed 5 time(s)
[0716/091926.910687:WARNING:gpu_process_host.cc(1233)] The GPU process has 
crashed 6 time(s)
[0716/091926.910721:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process 
isn't usable. Goodbye.
Trace/breakpoint trap



other core dumps from this release

Chrome_IOThread_S5_1594714909.core
Chrome_IOThread_S5_1594716342.core
Chrome_IOThread_S5_1594716369.core
Chrome_IOThread_S5_1594716698.core
Chrome_IOThread_S5_1594719025.core
Chrome_IOThread_S5_1594719158.core
Chrome_IOThread_S5_1594719721.core
Chrome_IOThread_S5_1594720056.core
Chrome_IOThread_S5_1594720555.core
Chrome_IOThread_S5_1594720727.core
Chrome_IOThread_S5_1594723143.core
Chrome_IOThread_S5_1594723555.core
Chrome_IOThread_S5_1594724765.core
Chrome_IOThread_S5_1594726735.core
chrome_S5_1594713852.core
chrome_S5_1594714094.core
chrome_S5_1594715092.core
chrome_S5_1594715446.core
chrome_S5_1594716376.core
chrome_S5_1594717583.core
chrome_S5_1594718113.core
chrome_S5_1594719128.core
chrome_S5_1594719384.core
chrome_S5_1594721440.core
chrome_S5_1594721535.core
chrome_S5_1594722795.core
chrome_S5_1594722978.core
chrome_S5_1594723249.core
chrome_S5_1594724206.core
chrome_S5_1594724258.core
chrome_S5_1594724538.core
chrome_S5_1594724988.core
chrome_S5_1594725002.core
chrome_S5_1594726378.core
chrome_S6_1594713950.core
chrome_S6_1594714908.core
chrome_S6_1594716342.core
chrome_S6_1594716368.core
chrome_S6_1594716697.core
chrome_S6_1594717712.core
chrome_S6_1594719024.core
chrome_S6_1594719157.core
chrome_S6_1594719720.core
chrome_S6_1594720055.core
chrome_S6_1594720554.core
chrome_S6_1594720726.core
chrome_S6_1594720810.core
chrome_S6_1594721013.core
chrome_S6_1594722356.core
chrome_S6_1594723142.core
chrome_S6_1594723554.core
chrome_S6_1594724764.core
chrome_S6_1594726734.core
ThreadPoolForeg_S5_1594714202.core
ThreadPoolForeg_S5_1594714760.core
ThreadPoolForeg_S5_1594717626.core
ThreadPoolForeg_S5_1594720170.core
ThreadPoolForeg_S5_1594721977.core
ThreadPoolForeg_S5_1594724067.core
ThreadPoolForeg_S5_1594726574.core
ThreadPoolServi_S5_1594714496.core
ThreadPoolServi_S5_1594718153.core
ThreadPoolServi_S5_1594718433.core
ThreadPoolServi_S5_1594718656.core
ThreadPoolServi_S5_1594721429.core
ThreadPoolServi_S5_1594721635.core
ThreadPoolServi_S5_1594721840.core
ThreadPoolServi_S5_1594723905.core
ThreadPoolServi_S5_1594726588.core
ThreadPoolServi_S5_1594726621.core

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

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

Title:
  Core dump

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  latest snap on Ubuntu LTS
  ver : 84.0.4147.89  
  https://bugs.chromium.org/p/chromium/issues/detail?id=1106509#c2

  Can you add debug symbols for libs? I'd be happy to provide a
  backtrace.

  note, I am running with GPU disabled!

  There are various SIGTRAP, SIGSEGV core dumps I can easily reproduce

  Run this 50  times

  chromium-browser --no-sandbox --incognito --virtual-time-budget=5000
  --disable-gpu --headless --print-to-pdf=a.pdf http://www.chimpazee.jp
  >> log.log 2>&1

  other sites easy to reproduce if you run it 50 times

  Sri-Langka.com
  newdress.it
  cwalkerart.net


  What went wrong?
  Failed to open /dev/null
  [0716/091926.883693:WARNING:gpu_process_host.cc(1233)] The GPU process has 
crashed 1 time(s)
  [0716/091926.889564:WARNING:gpu_process_host.cc(1233)] The GPU process has 
crashed 2 time(s)
  [0716/091926.893577:WARNING:gpu_process_host.cc(1233)] The GPU process has 
crashed 3 time(s)
  [0716/091926.894491:WARNING:gpu_process_host.cc(1233)] The GPU process has 
crashed 4 time(s)
  [0716/091926.908258:WARNING:gpu_process_host.cc(1233)] The GPU process has 
crashed 5 time(s)
  [0716/091926.910687:WARNING:gpu_process_host.cc(1233)]

[Desktop-packages] [Bug 1887968] [NEW] Pairing with bluetooth mice fails

2020-07-17 Thread Julian

Public bug reported:

I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems to
use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.

I've been unsuccessful to pair with 2 different bluetooth mice. However
bluetooth seems to work with other devices. I'm under the impression
that this problem only happens with Bluetooth LE devices.

Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:

[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled

A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.

Running btmon while trying to pair with the device gives me the
following:

Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64) 
  0.998188
= Note: Bluetooth subsystem version 2.22
  0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)   
   [hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C 
   [hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation) 
   [hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14   
 {0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
 {0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8 
  {0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8 
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
  Type: Passive (0x00)
  Interval: 60.000 msec (0x0060)
  Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4 
> #2 [hci0] 8.284618
  LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6 
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4 
> #4 [hci0] 8.289616
  LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52   
> #5 [hci0] 8.343614
  LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
  Event type: 0x0013
Props: 0x0013
  Connectable
  Scannable
  Use legacy advertising PDUs
Data status: Complete
  Legacy PDU Type: ADV_IND (0x0013)
  Address type: Random (0x01)
  Address: E5:5B:67:2A:09:76 (Static)
  Primary PHY: LE 1M
  Secondary PHY: No packets
  SID: no ADI field (0xff)
  TX power: 127 dBm
  RSSI: -20 dBm (0xec)
  Periodic advertising invteral: 0.00 msec (0x)
  Direct address type: Public (0x00)
  Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
  Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a  .Raz
65 72 20 41 74 68 65 72 69 73er Atheris  
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6 
#6 [hci0] 8.343656
Extended scan: Disabled (0x00)
Filter duplicates: Disabled (0x00)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4 
> #7 [hci0] 8.345617
  LE Set

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-
from-source/commit/?id=ff07991f41f89a21355b6e1c77a4db4393321d47
hopefully fixes it

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1887966] [NEW] firefox is freezing

2020-07-17 Thread Ljubiša Dukić

Public bug reported:

firefox is freezing while openning new page or scrolling

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 78.0.2+build2-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ljubisa 982 F pulseaudio
 /dev/snd/controlC0:  ljubisa 982 F pulseaudio
BuildID: 20200708170202
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 17 15:52:34 2020
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:730
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2020-06-17 (30 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
 default via 192.168.8.1 dev wlp3s5 proto dhcp metric 600 
 169.254.0.0/16 dev wlp3s5 scope link metric 1000 
 192.168.8.0/24 dev wlp3s5 proto kernel scope link src 192.168.8.100 metric 600
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=sr_RS
 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:730
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=78.0.2/20200708170202 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V8.4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A68HM-E33 V2 (MS-7721)
dmi.board.vendor: MSI
dmi.board.version: 9.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 9.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.4:bd08/10/2016:svnMSI:pnMS-7721:pvr9.0:rvnMSI:rnA68HM-E33V2(MS-7721):rvr9.0:cvnMSI:ct3:cvr9.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7721
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 9.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug focal

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

Title:
  firefox is freezing

Status in firefox package in Ubuntu:
  New

Bug description:
  firefox is freezing while openning new page or scrolling

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 78.0.2+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ljubisa 982 F pulseaudio
   /dev/snd/controlC0:  ljubisa 982 F pulseaudio
  BuildID: 20200708170202
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 17 15:52:34 2020
  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:730
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-06-17 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.8.1 dev wlp3s5 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s5 scope link metric 1000 
   192.168.8.0/24 dev wlp3s5 proto kernel scope link src 192.168.8.100 metric 
600
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sr_RS
   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 ','

[Desktop-packages] [Bug 1887804] Re: chromium-browser does not follow XDG base directory specification

Oh and I didn't confirm my own bug, that was done by the janitor because
someone else felt that this affects them, I just restored the previous
status.

** Also affects: chromium-browser
   Importance: Undecided
   Status: New

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

Title:
  chromium-browser does not follow XDG base directory specification

Status in Chromium Browser:
  New
Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Currently Chromium does not follow the XDG base directory
  specification which means that the cache and configuration folder
  aren't properly used.

  This causes the issue that it's nearly impossible to properly migrate
  or back up Chromium configuration (between computers) and it makes for
  example mounting cache as tmpfs or wiping it very very difficult.

  I felt those both immensely when trying to migrate my home folder,
  gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder]
  (and ~/snap itself is also not XDG base directory specification
  compliant, shame!).

  There's also the issue that the previous configuration that is located
  properly, isn't migrated by the migrational package.

  In order to fix this bug, it would require making the snap package
  follow the XDG base directory specification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1887804/+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 1887804] Re: chromium-browser does not follow XDG base directory specification

Upstream bug report that would resolve a half of this issue:
https://bugs.chromium.org/p/chromium/issues/detail?id=1106754

Just to summarize what's left broken by this specific Ubuntu package:

  * Config and cache are not in the folders defined by the base
directory specification

  * Current `common`/configuration folder is incomplete - can't be
backed up and restored

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

Title:
  chromium-browser does not follow XDG base directory specification

Status in Chromium Browser:
  New
Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Currently Chromium does not follow the XDG base directory
  specification which means that the cache and configuration folder
  aren't properly used.

  This causes the issue that it's nearly impossible to properly migrate
  or back up Chromium configuration (between computers) and it makes for
  example mounting cache as tmpfs or wiping it very very difficult.

  I felt those both immensely when trying to migrate my home folder,
  gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder]
  (and ~/snap itself is also not XDG base directory specification
  compliant, shame!).

  There's also the issue that the previous configuration that is located
  properly, isn't migrated by the migrational package.

  In order to fix this bug, it would require making the snap package
  follow the XDG base directory specification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1887804/+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 1887804] Re: chromium-browser does not follow XDG base directory specification

I also have to repeat that currently, copying over the folder contents
you mentioned did NOT result in a working instance of Chromium. All of
my extensions broke, databases failed to open, the common folder is just
incomplete and needs attention. Please do try it yourself.

That absolutely 100% NOT a duplicate of the general snap lunacy.

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

Title:
  chromium-browser does not follow XDG base directory specification

Status in Chromium Browser:
  New
Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Currently Chromium does not follow the XDG base directory
  specification which means that the cache and configuration folder
  aren't properly used.

  This causes the issue that it's nearly impossible to properly migrate
  or back up Chromium configuration (between computers) and it makes for
  example mounting cache as tmpfs or wiping it very very difficult.

  I felt those both immensely when trying to migrate my home folder,
  gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder]
  (and ~/snap itself is also not XDG base directory specification
  compliant, shame!).

  There's also the issue that the previous configuration that is located
  properly, isn't migrated by the migrational package.

  In order to fix this bug, it would require making the snap package
  follow the XDG base directory specification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1887804/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-07-17 Thread Alex

I had a 2080ti that died so I was running a 1070 until the RMA came, and
the updated PPA worked perfectly with no issues. Swapped in the new
2080ti yesterday and have had a pretty significant performance hit since
then, choppy movement and animations, feels like the whole desktop is
running at 30fps or less. Same driver and other hardware.

Nvidia driver 440.100

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

Title:
  [nvidia] Screen scaling 125% gives 200%

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

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1887804] Re: chromium-browser does not follow XDG base directory specification

> You're right, it does contain cache data. That would be an upstream
bug, can you please file it at
https://bugs.chromium.org/p/chromium/issues/entry ?

I will

>  I just found bug #1575053 which looks very similar to your issue, so
I'm going to mark it as duplicate, and I encourage you to read all the
comments to understand the rationale.

They're not duplicates because that one is about moving ~/snap, this one
is making the package actually XDG base directory specification
compliant. If Snap does not offer basic mount features, then this is
also a bug in snapd.

** This bug is no longer a duplicate of bug 1575053
   Please move the "$HOME/snap" directory to a less obtrusive location

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

Title:
  chromium-browser does not follow XDG base directory specification

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Currently Chromium does not follow the XDG base directory
  specification which means that the cache and configuration folder
  aren't properly used.

  This causes the issue that it's nearly impossible to properly migrate
  or back up Chromium configuration (between computers) and it makes for
  example mounting cache as tmpfs or wiping it very very difficult.

  I felt those both immensely when trying to migrate my home folder,
  gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder]
  (and ~/snap itself is also not XDG base directory specification
  compliant, shame!).

  There's also the issue that the previous configuration that is located
  properly, isn't migrated by the migrational package.

  In order to fix this bug, it would require making the snap package
  follow the XDG base directory specification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887804/+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 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

2020-07-17 Thread Shengyao Xue

** Changed in: oem-priority
   Status: New => In Progress

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

2020-07-17 Thread Liz Fong-Jones

`stage-packages libdrm-intel1` still fails despite skipping the build
steps. Needs a selector to skip it on !amd64/i386.

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1887793] Re: [snap] chromium unable to launch

>From memory I gathered this set of command from this bug report:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365

Maybe it's related ?

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

Title:
  [snap] chromium unable to launch

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Updated the chromium snap yesterday, latest/stable (1229). Today from
  a fresh boot, it won't launch.

  ```
  mattias@cerebus:~$ chromium
  Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module"
  Trace/breakpoint trap (core dumped)
  ```

  Using snap revert it goes back to latest/stable (1213), and works
  perfectly.

  Refreshing back to 1229 reproduces the issue.

  OS: Ubuntu 20.04 LTS x86_64 
  Kernel: 5.4.0-40-generic 
  Uptime: 1 hour, 43 mins 
  Packages: 2233 (dpkg), 86 (snap) 
  Shell: bash 5.0.16 
  Resolution: 2560x1440, 2560x1440 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i7-4770K (8) @ 3.900GHz 
  GPU: NVIDIA GeForce GTX 970 
  Memory: 8251MiB / 15945MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1887793] Re: [snap] chromium unable to launch

>From memory I gathered this set of command from this 
 #1864365

Maybe it's related ?

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

Title:
  [snap] chromium unable to launch

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Updated the chromium snap yesterday, latest/stable (1229). Today from
  a fresh boot, it won't launch.

  ```
  mattias@cerebus:~$ chromium
  Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module"
  Trace/breakpoint trap (core dumped)
  ```

  Using snap revert it goes back to latest/stable (1213), and works
  perfectly.

  Refreshing back to 1229 reproduces the issue.

  OS: Ubuntu 20.04 LTS x86_64 
  Kernel: 5.4.0-40-generic 
  Uptime: 1 hour, 43 mins 
  Packages: 2233 (dpkg), 86 (snap) 
  Shell: bash 5.0.16 
  Resolution: 2560x1440, 2560x1440 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i7-4770K (8) @ 3.900GHz 
  GPU: NVIDIA GeForce GTX 970 
  Memory: 8251MiB / 15945MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system

Did you try to follow https://wiki.ubuntu.com/Debug%20Symbol%20Packages
(which is referenced from the other pages).

You can also directly find the packages from the build referenced there
https://launchpad.net/ubuntu/+source/nautilus/1:3.36.3-0ubuntu1/+build/19437394

You can e.g download
https://launchpad.net/ubuntu/+source/nautilus/1:3.36.3-0ubuntu1/+build/19437394/+files
/nautilus-dbgsym_3.36.3-0ubuntu1_amd64.ddeb and install it using dpkg -i
locally

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

Title:
  Nautilus crashes while over-typing search term on remote smb file
  system

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  ==Impact==

  nautilus crashes while typing the term to search a remote directory
  within an NT file system over the smb protocol. The problem may affect
  other remote file systems or protocols, but I have only tested these.

  Repeatable.

  ==How to repeat==

  1. Open Nautilus
  2. In the sidebar, click Other Locations
  3. Type smb://example/share into the 'Connect to server' field or select an 
existing share URI
  4. Click Connect
  5. Optionally, when the contents of the share appears, select any depth of 
sub-directories.
  6. Click the search icon and type a search string
  7. Once the search results have returned, without closing the search box, 
select the previous search term and over-type another search term.

  Nautilus crashes.

  Typically, prior to the window disappearing the graphics freezes
  within the search field showing both the previous and the current
  search terms on top of each other.

  Often it is necessary to kill the nautilus process and/or reboot the
  smb daemon on the remote machine before being able to use the smb
  share again.

  Before typing a second search term, if instead of over-typing, you
  delete the selection either i) with the  key; or ii) clicking
  the (x) to clear the field; or iii) clicking the search icon twice to
  remove and reinstate the search field; it is possible to search for a
  second term without crashing.

  It is possible that the crash depends on how fast the search term is
  typed, because nautilus starts searching as you type. I have tried to
  paste a search term over an existing term, which usually seems to work
  without crashing. On the other hand, I have had nautilus crash when
  typing a search term after having explicitly cleared the search field,
  but before nautilus has displayed the full contents of the directory
  again (about 150 files).

  I have not had nautilus crash when over-typing the search field for a
  local file system, whether ntfs or ext3.

  ==Related bugs==

  Bug #1795028 seems to be identical, and claims to have been fixed in
  package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to
  be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains
  more precisely how to reproduce the crash.

  ==Crash Reports==

  A typical crash report from my system is here:
  https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 21:03:59 2020
  InstallationDate: Installed on 2020-06-03 (38 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+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 1887861] Re: Gnome Lock screen shows old screen before lock screen

2020-07-17 Thread Marc Deslauriers

** Information type changed from Private Security to Public Security

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

Title:
  Gnome Lock screen shows old screen before lock screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a laptop with led backlight.

  When the locking the screen and then hitting return key the old screen(screen 
before lock) is displayed for a short period then the lock screen is displayed. 
I assume this is because if I
  had an older style backlight the delay would be happing while the backlight 
is warning up.
  Since this is an led backlight there is no warm up (delay) between turning on 
the screen backlight
  and the display showing.

  This is a also a security problem because any person walking up to the lock 
laptop can see what
  was on the screen before locking without a password.

  If need I can record the whole thing with my smart phone to show the
  security issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset zunicode zavl icp zcommon znvpair 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 16 17:02:59 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-30 (108 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1887861/+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 1424201] Re: Web browsers lacking hardware-accelerated video decoding

2020-07-17 Thread Michel-Ekimia

** Description changed:

- The chromium team has done a great job to totally disable hardware
- decoding on Linux.
+ This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux
+ browsers.
  
- Even ignoring the GPU blacklist does not enable GPU decoding.
+ In 2015 I opened this bug , no easy solution was available and battery
+ drained when playing video in browser was crazy.
  
- How ever the patch is quite simple and it's already working using this
- PPA ( using libVA ) :
+ In july 2020, things are getting better :
  
- https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev
+ - Chromium :
  
- the corresponding patch is here :
+ A patch is used on most distro packages. Ubuntu now will integrate this
+ patch on Snap chromium stable soon , more info here
+ https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497
  
- http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium-
- browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff
  
- that would be great if we could have this patch indefault Ubuntu
- chromium build, this situation is really sad right now, google use linux
- to make chromeOS so chromebook are really good at playing videos but
- GNU/Linux chromium is slow at doing it.
+ - Firefox :
+ 
+ Firefox team has done a great job and now Va-api decoding in Wayland is
+ possible and X11 is possible in nightly !
+ 
+ Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727
+ 
+ We shall close this bug when both browsers will have Va-api decoding
+ available in Stable.

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

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux
  browsers.

  In 2015 I opened this bug , no easy solution was available and battery
  drained when playing video in browser was crazy.

  In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. Ubuntu now will integrate
  this patch on Snap chromium stable soon , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497


  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  We shall close this bug when both browsers will have Va-api decoding
  available in Stable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1877536] Re: BlueZ 5.54 release

This bug was fixed in the package bluez - 5.54-0ubuntu1

---
bluez (5.54-0ubuntu1) groovy; urgency=medium

  * New upstream release 5.54 (LP: #1877536)
- Fix issue with HOGP to accept data only from bonded devices.
- Fix issue with A2DP sessions being connected at the same time.
- Fix issue with class UUID matches before connecting profile.
- Add support for handling MTU auto-tuning option for AVDTP.
- Add support for new policy for Just-Works repairing.
- Add support for Enhanced ATT bearer (EATT).
  * Dropped CVE-2020-0556-[1-4].patch as release 5.54 onward is not affected.
  * Dropped (already unused) CVE-2017-1000250.patch as release 5.47 onward
is not affected.

 -- Daniel van Vugt   Fri, 08 May 2020
16:28:03 +0800

** Changed in: bluez (Ubuntu)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000250

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0556

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

Title:
  BlueZ 5.54 release

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.54 to groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1877536/+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 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system

2020-07-17 Thread Bob Briscoe

I'm following the instructions to upload a backtrace. I've disable apport, but 
I've floundered on step 1 of Generating the backtrace.
"1. Please ensure you have packages with debug symbols installed. You can 
do this by following the instructions at DebuggingProgramCrash."

Can you give more specific instructions for this case? I can't find a
nautilus package with debug symbols installed.

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

Title:
  Nautilus crashes while over-typing search term on remote smb file
  system

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  ==Impact==

  nautilus crashes while typing the term to search a remote directory
  within an NT file system over the smb protocol. The problem may affect
  other remote file systems or protocols, but I have only tested these.

  Repeatable.

  ==How to repeat==

  1. Open Nautilus
  2. In the sidebar, click Other Locations
  3. Type smb://example/share into the 'Connect to server' field or select an 
existing share URI
  4. Click Connect
  5. Optionally, when the contents of the share appears, select any depth of 
sub-directories.
  6. Click the search icon and type a search string
  7. Once the search results have returned, without closing the search box, 
select the previous search term and over-type another search term.

  Nautilus crashes.

  Typically, prior to the window disappearing the graphics freezes
  within the search field showing both the previous and the current
  search terms on top of each other.

  Often it is necessary to kill the nautilus process and/or reboot the
  smb daemon on the remote machine before being able to use the smb
  share again.

  Before typing a second search term, if instead of over-typing, you
  delete the selection either i) with the  key; or ii) clicking
  the (x) to clear the field; or iii) clicking the search icon twice to
  remove and reinstate the search field; it is possible to search for a
  second term without crashing.

  It is possible that the crash depends on how fast the search term is
  typed, because nautilus starts searching as you type. I have tried to
  paste a search term over an existing term, which usually seems to work
  without crashing. On the other hand, I have had nautilus crash when
  typing a search term after having explicitly cleared the search field,
  but before nautilus has displayed the full contents of the directory
  again (about 150 files).

  I have not had nautilus crash when over-typing the search field for a
  local file system, whether ntfs or ext3.

  ==Related bugs==

  Bug #1795028 seems to be identical, and claims to have been fixed in
  package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to
  be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains
  more precisely how to reproduce the crash.

  ==Crash Reports==

  A typical crash report from my system is here:
  https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 21:03:59 2020
  InstallationDate: Installed on 2020-06-03 (38 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+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 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

2020-07-17 Thread Łukasz Zemczak

Hello Hui, or anyone else affected,

Accepted pulseaudio into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.5 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-focal

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-07-17 Thread Nicolas Rogues

done today

got an error from vger.kernel.org (policy analysis reported: your
address is not liked source for email) but not from other recipients, so
if any of the other affected users has an approved email address with
this server, I will be glad to provide the initial email for forwarding

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo

[Desktop-packages] [Bug 1887793] Re: [snap] chromium unable to launch

2020-07-17 Thread Mattias Wernér

@procsynth

I just tried a reboot and you're quite right, everything seems fine
again.

Kudos to whoever fixed that particular gnarly bug.

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

Title:
  [snap] chromium unable to launch

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Updated the chromium snap yesterday, latest/stable (1229). Today from
  a fresh boot, it won't launch.

  ```
  mattias@cerebus:~$ chromium
  Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module"
  Trace/breakpoint trap (core dumped)
  ```

  Using snap revert it goes back to latest/stable (1213), and works
  perfectly.

  Refreshing back to 1229 reproduces the issue.

  OS: Ubuntu 20.04 LTS x86_64 
  Kernel: 5.4.0-40-generic 
  Uptime: 1 hour, 43 mins 
  Packages: 2233 (dpkg), 86 (snap) 
  Shell: bash 5.0.16 
  Resolution: 2560x1440, 2560x1440 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i7-4770K (8) @ 3.900GHz 
  GPU: NVIDIA GeForce GTX 970 
  Memory: 8251MiB / 15945MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

Tentative fix to enable building on !amd64: https://git.launchpad.net
/~chromium-team/chromium-browser/+git/snap-from-
source/commit/?id=d8f8bf958810e0b48a1dd9e480fbe2def7e8f9f1

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1882161] Update Released

2020-07-17 Thread Łukasz Zemczak

The verification of the Stable Release Update for pulseaudio has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * On the Dell machines with multi function audio jack, the
     headphone/headset can't output sound automatically, which is different
     from ubuntu 18.04. The headphone/headset should be able to  output
     sound automatically after plugging in the audio jack.

  [Test Case]

   * On Tiger Lake platform
     Reproduce step:
     1. plug headphone/headset
     2. open g-c-c sound to check

     Expect result: The output device should switch to headphone or headset,
    since headphone's priority is higher in ucm2 config.
     Actual result: The output device is still internal speaker.

  [Regression Potential]

   * The change insert the ucm device by its priority, the potential
 regression is low, since if the change is not working properly, the 
 side effect is that the order of ucm devices are wrong, and it won't 
 switch to the correct output device as expect, but user can still
 config it manually.

  [Other]

   * This bug originates from an OEM private bug #1875597, then ubuntu users
     reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329
     and the 1st issue of #1881659 have the same root cause as #1875597

   * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and
     Headset MIC, and the pulseaudio parse the input device Headset MIC
     first then Mic2, finally the audio jack is set to Mic2 mode, this make
     the audio jack can't output sound anymore. To fix it, let the audio
     jack set to Headset MIC mode by default (Headset MIC has higher
     priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the
     device event to module-switch-on-port-available by the order of
     priority in the umc2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882161/+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 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.4

---
pulseaudio (1:13.99.1-1ubuntu3.4) focal; urgency=medium

  * d/p/0032-alsa-mixer-store-the-ucm_device-with-the-order-of-th.patch
- switch the port on ucm devices based on the priority (LP: #1882161)

 -- Hui Wang   Fri, 05 Jun 2020 09:52:22 +0800

** Changed in: pulseaudio (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * On the Dell machines with multi function audio jack, the
     headphone/headset can't output sound automatically, which is different
     from ubuntu 18.04. The headphone/headset should be able to  output
     sound automatically after plugging in the audio jack.

  [Test Case]

   * On Tiger Lake platform
     Reproduce step:
     1. plug headphone/headset
     2. open g-c-c sound to check

     Expect result: The output device should switch to headphone or headset,
    since headphone's priority is higher in ucm2 config.
     Actual result: The output device is still internal speaker.

  [Regression Potential]

   * The change insert the ucm device by its priority, the potential
 regression is low, since if the change is not working properly, the 
 side effect is that the order of ucm devices are wrong, and it won't 
 switch to the correct output device as expect, but user can still
 config it manually.

  [Other]

   * This bug originates from an OEM private bug #1875597, then ubuntu users
     reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329
     and the 1st issue of #1881659 have the same root cause as #1875597

   * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and
     Headset MIC, and the pulseaudio parse the input device Headset MIC
     first then Mic2, finally the audio jack is set to Mic2 mode, this make
     the audio jack can't output sound anymore. To fix it, let the audio
     jack set to Headset MIC mode by default (Headset MIC has higher
     priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the
     device event to module-switch-on-port-available by the order of
     priority in the umc2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882161/+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 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

2020-07-17 Thread Łukasz Zemczak

Hello! Seeing that this is priority for the OEM team, I'll conditionally
release this early - and on a Friday (oh no!). The problem with this is
that we'd have to make sure that if this does regress anything, there is
someone to react quickly during the weekend. I'll be available, but I'd
appreciate if someone from the OEM team could also keep eyes out for any
news of regression. Please give me a poke if anything like that happens.

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

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * On the Dell machines with multi function audio jack, the
     headphone/headset can't output sound automatically, which is different
     from ubuntu 18.04. The headphone/headset should be able to  output
     sound automatically after plugging in the audio jack.

  [Test Case]

   * On Tiger Lake platform
     Reproduce step:
     1. plug headphone/headset
     2. open g-c-c sound to check

     Expect result: The output device should switch to headphone or headset,
    since headphone's priority is higher in ucm2 config.
     Actual result: The output device is still internal speaker.

  [Regression Potential]

   * The change insert the ucm device by its priority, the potential
 regression is low, since if the change is not working properly, the 
 side effect is that the order of ucm devices are wrong, and it won't 
 switch to the correct output device as expect, but user can still
 config it manually.

  [Other]

   * This bug originates from an OEM private bug #1875597, then ubuntu users
     reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329
     and the 1st issue of #1881659 have the same root cause as #1875597

   * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and
     Headset MIC, and the pulseaudio parse the input device Headset MIC
     first then Mic2, finally the audio jack is set to Mic2 mode, this make
     the audio jack can't output sound anymore. To fix it, let the audio
     jack set to Headset MIC mode by default (Headset MIC has higher
     priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the
     device event to module-switch-on-port-available by the order of
     priority in the umc2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882161/+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 1887793] Re: [snap] chromium unable to launch

@mlw I my last test the fix survived a reboot though it did not few
months ago.

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

Title:
  [snap] chromium unable to launch

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Updated the chromium snap yesterday, latest/stable (1229). Today from
  a fresh boot, it won't launch.

  ```
  mattias@cerebus:~$ chromium
  Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module"
  Trace/breakpoint trap (core dumped)
  ```

  Using snap revert it goes back to latest/stable (1213), and works
  perfectly.

  Refreshing back to 1229 reproduces the issue.

  OS: Ubuntu 20.04 LTS x86_64 
  Kernel: 5.4.0-40-generic 
  Uptime: 1 hour, 43 mins 
  Packages: 2233 (dpkg), 86 (snap) 
  Shell: bash 5.0.16 
  Resolution: 2560x1440, 2560x1440 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i7-4770K (8) @ 3.900GHz 
  GPU: NVIDIA GeForce GTX 970 
  Memory: 8251MiB / 15945MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1887793] Re: [snap] chromium unable to launch

@mlw I my last test the fix survived a reboot though I did not few
months ago.

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

Title:
  [snap] chromium unable to launch

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Updated the chromium snap yesterday, latest/stable (1229). Today from
  a fresh boot, it won't launch.

  ```
  mattias@cerebus:~$ chromium
  Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module"
  Trace/breakpoint trap (core dumped)
  ```

  Using snap revert it goes back to latest/stable (1213), and works
  perfectly.

  Refreshing back to 1229 reproduces the issue.

  OS: Ubuntu 20.04 LTS x86_64 
  Kernel: 5.4.0-40-generic 
  Uptime: 1 hour, 43 mins 
  Packages: 2233 (dpkg), 86 (snap) 
  Shell: bash 5.0.16 
  Resolution: 2560x1440, 2560x1440 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i7-4770K (8) @ 3.900GHz 
  GPU: NVIDIA GeForce GTX 970 
  Memory: 8251MiB / 15945MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1881923] Re: No icons in file picker

Can you please share the output of the following command?

snap changes --abs-time chromium

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

Title:
  No icons in file picker

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I installed chromium via snap on Ubuntu 20.04. When the file picker is
  opend (for example to upload some files) all icons are missing. Files
  and folders have no icon (see attached screenshot).

  Ubuntu 20.04 LTS
  Chromium Version 83.0.4103.61 (Official Build) snap (64-bit)

  Maybe it is a problem with the apparmor-profile?

  [27780.715573] audit: type=1400 audit(1591194917.741:3258): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/etc/fstab" pid=5553 
comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [27780.737385] audit: type=1400 audit(1591194917.761:3259): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/mount/utab" 
pid=5553 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [27781.003139] audit: type=1400 audit(1591194918.029:3260): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/mount/utab" 
pid=5553 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [27781.012869] audit: type=1107 audit(1591194918.037:3261): pid=1073 uid=100 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/hostname1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.285" pid=5553 label="snap.chromium.chromium" peer_pid=156208 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=100 hostname=? addr=? 
terminal=?'
  [27784.173782] audit: type=1400 audit(1591194921.197:3262): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/mount/utab" 
pid=5553 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1881923/+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 1887824] Re: License wrong in software list

2020-07-17 Thread Kai Kasurinen

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

** Also affects: snap-store-desktop
   Importance: Undecided
   Status: New

** This bug has been marked a duplicate of bug 1878924
   snap-store says an app is proprietary while it's free

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

Title:
  License wrong in software list

Status in snap-store-desktop:
  New
Status in gucharmap package in Ubuntu:
  New

Bug description:
  In the package page in the Ubuntu software center, this appears as 
proprietary, it should be GPLv3
  Checked on version 1:13.0.1-1 on 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store-desktop/+bug/1887824/+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 1887793] Re: [snap] chromium unable to launch

2020-07-17 Thread Mattias Wernér

Workaround is effective. From what I recall the effects are only
temporary though.

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

Title:
  [snap] chromium unable to launch

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Updated the chromium snap yesterday, latest/stable (1229). Today from
  a fresh boot, it won't launch.

  ```
  mattias@cerebus:~$ chromium
  Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module"
  Trace/breakpoint trap (core dumped)
  ```

  Using snap revert it goes back to latest/stable (1213), and works
  perfectly.

  Refreshing back to 1229 reproduces the issue.

  OS: Ubuntu 20.04 LTS x86_64 
  Kernel: 5.4.0-40-generic 
  Uptime: 1 hour, 43 mins 
  Packages: 2233 (dpkg), 86 (snap) 
  Shell: bash 5.0.16 
  Resolution: 2560x1440, 2560x1440 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i7-4770K (8) @ 3.900GHz 
  GPU: NVIDIA GeForce GTX 970 
  Memory: 8251MiB / 15945MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1887804] Re: chromium-browser does not follow XDG base directory specification

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

Please do not confirm your own bugs.

> Change the folder it's confined to.

As I explained earlier it's a security feature implemented by snapd, the
chromium snap doesn't get to choose where its data is stored. I just
found bug #1575053 which looks very similar to your issue, so I'm going
to mark it as duplicate, and I encourage you to read all the comments to
understand the rationale.


> No, not really. The profile folder contains gigabytes of cache files.

You're right, it does contain cache data. That would be an upstream bug,
can you please file it at
https://bugs.chromium.org/p/chromium/issues/entry ?

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

** This bug has been marked a duplicate of bug 1575053
   Please move the "$HOME/snap" directory to a less obtrusive location

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

Title:
  chromium-browser does not follow XDG base directory specification

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Currently Chromium does not follow the XDG base directory
  specification which means that the cache and configuration folder
  aren't properly used.

  This causes the issue that it's nearly impossible to properly migrate
  or back up Chromium configuration (between computers) and it makes for
  example mounting cache as tmpfs or wiping it very very difficult.

  I felt those both immensely when trying to migrate my home folder,
  gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder]
  (and ~/snap itself is also not XDG base directory specification
  compliant, shame!).

  There's also the issue that the previous configuration that is located
  properly, isn't migrated by the migrational package.

  In order to fix this bug, it would require making the snap package
  follow the XDG base directory specification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887804/+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 1887793] Re: [snap] chromium unable to launch

Thanks Mattias. Could you also try the suggested workaround at
https://forum.snapcraft.io/t/chromium-snap-kernel-has-no-file-
descriptor-comparison-support-operation-not-permitted/18921/2 and let us
know whether this "fixes" the problem for you too?

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

Title:
  [snap] chromium unable to launch

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Updated the chromium snap yesterday, latest/stable (1229). Today from
  a fresh boot, it won't launch.

  ```
  mattias@cerebus:~$ chromium
  Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module"
  Trace/breakpoint trap (core dumped)
  ```

  Using snap revert it goes back to latest/stable (1213), and works
  perfectly.

  Refreshing back to 1229 reproduces the issue.

  OS: Ubuntu 20.04 LTS x86_64 
  Kernel: 5.4.0-40-generic 
  Uptime: 1 hour, 43 mins 
  Packages: 2233 (dpkg), 86 (snap) 
  Shell: bash 5.0.16 
  Resolution: 2560x1440, 2560x1440 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i7-4770K (8) @ 3.900GHz 
  GPU: NVIDIA GeForce GTX 970 
  Memory: 8251MiB / 15945MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1887824] Re: License wrong in software list

Thank you for your bug report, could you take a screenshot showing the
issue?

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

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

Title:
  License wrong in software list

Status in gucharmap package in Ubuntu:
  New

Bug description:
  In the package page in the Ubuntu software center, this appears as 
proprietary, it should be GPLv3
  Checked on version 1:13.0.1-1 on 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1887824/+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 1768074] Re: Mouseover does not show folder names reliably

thanks

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

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

Title:
  Mouseover does not show folder names reliably

Status in baobab:
  Confirmed
Status in baobab package in Ubuntu:
  Triaged

Bug description:
  When holding my cursor still over a folder in the visualization (in
  either mode) I expect the name and size of the folder to appear in a
  floating box, as well as the names the folders contained in it.

  In my brand new install of Ubuntu 18.04, however, this does not happen most 
of the time. When holding my cursor over a folder, it «lights up» as usual, but 
after a second or two, it gets darker again, and nothing appears.
  However, it sometimes does work for certain folders. Based on a small amount 
of testing, those folders seem to be close to 8 or 9 o'clock when using the pie 
chart mode, and mostly only folders at the bottom of the hierarchy. I can then 
move the cursor within the visualization and see the names of all the folders 
as usual. But if the cursor is outside any folder for some small amount of 
time, I have to «activate» it again by holding the cursor over a working folder 
again.

  The behavior is quite strange and unpredictable, and I have no idea
  what is causing it or what to do about it. But I thought I would
  report it here as it makes it very difficult for me to use this
  application. I am happy to answer any questions.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: baobab 3.28.0-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 17:43:39 2018
  InstallationDate: Installed on 2018-04-27 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: baobab
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/baobab/+bug/1768074/+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 1887478] Re: missing symlinks for login and logout files used by gnome

Thanks for the details, the url in the description is a Debian change,
not an upstream one though, but let's see if it gets reviewed there

** Changed in: sound-theme-freedesktop (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  missing symlinks for login and logout files used by gnome

Status in sound-theme-freedesktop package in Ubuntu:
  Triaged

Bug description:
  Merge request submitted upstream in Debian to fix the issue.
  https://salsa.debian.org/gnome-team/sound-theme-freedesktop/-/merge_requests/1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1887478/+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 1887263] Re: nautilus freezes possibly in connection w/ samba share mounted/unmounted

Could you try to follow the steps on 
https://wiki.ubuntu.com/Backtrace#Already_running_programs? you might also have 
a better chance to get a someone helping with the issue upstream
https://gitlab.gnome.org/GNOME/nautilus/-/issues

** Changed in: nautilus (Ubuntu)
   Status: In Progress => Incomplete

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

Title:
  nautilus freezes possibly in connection w/ samba share
  mounted/unmounted

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  test steps:
  - mouunt samba share w/:
  smb://host/share
  - open local disc w/ personal folder
  - scroll directory e. g. w/ show hidden files enabled in order to get a long 
list

  expected result:
  directory scrolls up and down

  actual result:
  scrolling freezes for some seconds before scrolling completes:
  - no directory selection appears until after freeze is over
  - only selection possible is the mounted samba share, which returns to the 
top level directory of the share

  leder@home-ryzen-desktop:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  leder@home-ryzen-desktop:~$ apt-cache policy nautilus
  nautilus:
Installiert:   1:3.36.3-0ubuntu1
Installationskandidat: 1:3.36.3-0ubuntu1
Versionstabelle:
   *** 1:3.36.3-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.36.1.1-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  Uname: Linux 5.6.19-050619-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 04:32:18 2020
  InstallationDate: Installed on 2020-06-22 (19 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887263/+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 1887843] Re: Dismissing notifications in the notification window changes position of do-not-disturb button

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

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

Title:
  Dismissing notifications in the notification window changes position
  of do-not-disturb button

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  When new notifications appear in the notification window of Ubuntu
  20.04 it is possible to dismiss them by clicking the 'clear all'
  button or by dismissing individual notifications. When messages are
  dismissed, it results in a (downward) change in position of the 'do
  not disturb' toggle button. The expected behavior would be that the
  position of the button is not affected by addition/removal of
  notifications. Reporting in gnome shell, but it is also possible this
  is a theme styling issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 16 14:06:17 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-06 (10 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1887843/+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 1887793] Re: [snap] chromium unable to launch

2020-07-17 Thread Mattias Wernér

log attached

** Attachment added: "chromium_log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+attachment/5393468/+files/chromium_log.txt

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

Title:
  [snap] chromium unable to launch

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Updated the chromium snap yesterday, latest/stable (1229). Today from
  a fresh boot, it won't launch.

  ```
  mattias@cerebus:~$ chromium
  Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module"
  Trace/breakpoint trap (core dumped)
  ```

  Using snap revert it goes back to latest/stable (1213), and works
  perfectly.

  Refreshing back to 1229 reproduces the issue.

  OS: Ubuntu 20.04 LTS x86_64 
  Kernel: 5.4.0-40-generic 
  Uptime: 1 hour, 43 mins 
  Packages: 2233 (dpkg), 86 (snap) 
  Shell: bash 5.0.16 
  Resolution: 2560x1440, 2560x1440 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i7-4770K (8) @ 3.900GHz 
  GPU: NVIDIA GeForce GTX 970 
  Memory: 8251MiB / 15945MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1887816] Re: Right click "open with" opens directly without asking for a program

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

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

Title:
  Right click "open with" opens directly without asking for a program

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  I copied .txt files to my desktop folder (from NTFS external disk) and tried 
to open them but they were with right 777 (rwxrwxrwx) so press Enter (etc.) try 
to execute and not open the file with an editing program.
  Then I rote a bug report (#1887514), understood my problem and changed the 
rights of the files.

  But there is still a problem.

  When I was trying to identify the problem, I tried "open with" on the
  right click menu. It worked (a window is opened and ask witch program
  I want to use). And after reporting bug 1887514 (that wasn't a bug)
  the option "open with" didn't opened anymore the window to choose a
  program. It opens directly as if I've selected "open".

  It do the same to every new files I add to the desktop, and I already
  have rebooted my computer (it was some days ago).

  I am not sure if the package I've selected is the right one for this
  problem, I don't know a lot about how Ubuntu is structured (and I
  don't know where I can find precise information).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-desktop-icons 20.04.0-2~ubuntu20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 16 16:20:32 2020
  InstallationDate: Installed on 2020-07-12 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1887816/+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 1887891] Re: dav/davs behind proxy doesn't work