date:20201006

I should also note that Wayland sessions don't have this bug, and don't
have tearing either.

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

Title:
  Windows flicker when being resized with the mouse (Xorg sessions in
  groovy)

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker.  It only flickers when actively being
  resized, and when I stop dragging, it looks normal.  This behavior is
  does not occur on same pc in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Sep 22 10:21:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  MachineType: LENOVO 20FJS0AJ00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET26W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0AJ00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FJS0AJ00
  dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/gnome-shell/+bug/1896627/+subscriptions

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

[Desktop-packages] [Bug 1896627] Re: Windows flicker when being resized with the mouse (Xorg sessions in groovy)

Great, but keep in mind that's just a workaround. Using the 'intel'
driver is usually not recommended because it's getting old and buggy in
other ways. It is however your only option if you need 'TearFree'
enabled. See also
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=tearing

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

Title:
  Windows flicker when being resized with the mouse (Xorg sessions in
  groovy)

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker.  It only flickers when actively being
  resized, and when I stop dragging, it looks normal.  This behavior is
  does not occur on same pc in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Sep 22 10:21:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  MachineType: LENOVO 20FJS0AJ00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET26W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0AJ00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FJS0AJ00
  dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/gnome-shell/+bug/1896627/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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-10-06 Thread Piotr Tomaszewski

@Helmut Stult (helmut-stult), oh right. Did not see that post. Now
everything works like a charm. Even touchpad gestures works :) Thanks
guys, you are awesome!

-- 
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 Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  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

[Desktop-packages] [Bug 1896627] Re: Windows flicker when being resized with the mouse (Xorg sessions in groovy)

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

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

Title:
  Windows flicker when being resized with the mouse (Xorg sessions in
  groovy)

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker.  It only flickers when actively being
  resized, and when I stop dragging, it looks normal.  This behavior is
  does not occur on same pc in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Sep 22 10:21:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  MachineType: LENOVO 20FJS0AJ00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET26W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0AJ00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FJS0AJ00
  dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/gnome-shell/+bug/1896627/+subscriptions

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

[Desktop-packages] [Bug 1896627] Re: Windows flicker when being resized with the mouse (Xorg sessions in groovy)

2020-10-06 Thread fossfreedom

For 20.04 and 20.10 using the TearFree option has provided a workaround
solution for me.

Separately Sam (the issue reporter) has confirmed the same solution for
his intel graphics

https://askubuntu.com/questions/1066722/intel-screen-tearing-
ubuntu-18-04

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

Title:
  Windows flicker when being resized with the mouse (Xorg sessions in
  groovy)

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker.  It only flickers when actively being
  resized, and when I stop dragging, it looks normal.  This behavior is
  does not occur on same pc in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Sep 22 10:21:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  MachineType: LENOVO 20FJS0AJ00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET26W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0AJ00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FJS0AJ00
  dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/gnome-shell/+bug/1896627/+subscriptions

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

[Desktop-packages] [Bug 1898393] Re: Gnome Magnifier does track mouse cursor.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3237
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3237

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

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

** Changed in: gjs (Ubuntu)
   Status: New => Triaged

** Changed in: gjs (Ubuntu)
   Importance: Undecided => High

** Bug watch added: gitlab.gnome.org/GNOME/gjs/-/issues #353
   https://gitlab.gnome.org/GNOME/gjs/-/issues/353

** Also affects: gjs via
   https://gitlab.gnome.org/GNOME/gjs/-/issues/353
   Importance: Unknown
   Status: Unknown

** Summary changed:

- Gnome Magnifier does track mouse cursor.
+ Gnome 3.38 Magnifier does track mouse cursor.

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

Title:
  Gnome 3.38 Magnifier does track mouse cursor.

Status in gjs:
  Unknown
Status in GNOME Shell:
  Unknown
Status in gjs package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  The mouse tracking when using the Gnome shell magnifier doesn't work.
  Text cursor and focus cursor tracking works fine.

  To re-poroduce enable the magnification by pressing Super + Alt + 8.
  Move the mouse around and observe the magnified view remaining in one
  place. The magnified view should follow the mouse cursor.

  Tested on both X and Wayland. Using a virtual machine and Dell XPS
  9630.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  3 21:22:21 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.a11y.applications' b'screen-magnifier-enabled' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['update-manager']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2020-10-03 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-10-06 Thread Azizkhan

Is it able to build Ubuntu 5.8.13 kernel?
I mean from kernel.org

-- 
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 Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  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 Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  Prob

[Desktop-packages] [Bug 1657625] Re: pulseaudio crashed with SIGABRT in pa_hook_slot_free() from pa_dynarray_free() from pa_module_load() from pa_cli_command_load() from pa_cli_command_execute_line_st

** Tags removed: artful yakkety zesty
** Tags added: 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/1657625

Title:
  pulseaudio crashed with SIGABRT in pa_hook_slot_free() from
  pa_dynarray_free() from pa_module_load() from pa_cli_command_load()
  from pa_cli_command_execute_line_stateful()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/d769d435e3909253da5742ef109befab0758706e 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1879183] Re: Cheese does not show preferences/options/menus to non-GNOME Users

2020-10-06 Thread curtis martz

Ha, I know right? That would fit the pattern of decreased functionality
if the fix was just to disable the menu in Gnome too! saboteur style : )
Maybe they'll allow burning of blue ray data disks someday too? umm
er... sorry.

> On Oct 6, 2020, at 19:35, Brian Murray <1879...@bugs.launchpad.net> wrote:
> 
> I'd like to see this tested in an Ubuntu Gnome session to confirm that
> it does not regress there.
> 
> -- 
> You received this bug notification because you are subscribed to a
> duplicate bug report (1884461).
> https://bugs.launchpad.net/bugs/1879183
> 
> Title:
>  Cheese  does not show preferences/options/menus to non-GNOME Users
> 
> Status in cheese package in Ubuntu:
>  Fix Released
> Status in cheese source package in Focal:
>  Fix Committed
> Status in cheese package in Debian:
>  New
> 
> Bug description:
>  [Impact] 
>  Cheese no longer displays its menu button on non-GNOME desktop environments.
>  https://gitlab.gnome.org/GNOME/cheese/-/issues/62
> 
>  Xubuntu uses cheese as its default camera program. Advanced users can
>  still change these settings through dconf-editor, but this is neither
>  convenient nor intuitive.
> 
>  [Test Case]
> 
>  Use the cheese program in Xubuntu/xfce, Kubuntu/KDE or other non-GNOME
>  desktop environments. Notice missing menu in titlebar.
> 
>  [Regression Potential]
> 
>  The most likely regression would be if the patch disabled the menu in
>  GNOME. Testing has not shown this to be an issue.
> 
> 
>  [ORIGINAL REPORT]
>  Cheese has removed the GUI method of accessing preferences for non-GNOME 
> users.
>  
> https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d
> 
>  I'm not sure if upstream cheese devs care enough to fix it:
>  https://gitlab.gnome.org/GNOME/cheese/-/issues/62
>  https://gitlab.gnome.org/GNOME/cheese/-/issues/52
> 
>  Should Xubuntu default to a different camera program, such as
>  guvcview?
> 
>  (Partial?) WORKAROUND is to use dconf-editor:
>  dconf-editor /org/gnome/cheese
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1879183/+subscriptions


** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #52
   https://gitlab.gnome.org/GNOME/cheese/-/issues/52

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

Title:
  Cheese  does not show preferences/options/menus to non-GNOME Users

Status in cheese package in Ubuntu:
  Fix Released
Status in cheese source package in Focal:
  Fix Committed
Status in cheese package in Debian:
  New

Bug description:
  [Impact] 
  Cheese no longer displays its menu button on non-GNOME desktop environments.
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62

  Xubuntu uses cheese as its default camera program. Advanced users can
  still change these settings through dconf-editor, but this is neither
  convenient nor intuitive.

  [Test Case]

  Use the cheese program in Xubuntu/xfce, Kubuntu/KDE or other non-GNOME
  desktop environments. Notice missing menu in titlebar.

  [Regression Potential]

  The most likely regression would be if the patch disabled the menu in
  GNOME. Testing has not shown this to be an issue.

  
  [ORIGINAL REPORT]
  Cheese has removed the GUI method of accessing preferences for non-GNOME 
users.
  
https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d

  I'm not sure if upstream cheese devs care enough to fix it:
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62
  https://gitlab.gnome.org/GNOME/cheese/-/issues/52

  Should Xubuntu default to a different camera program, such as
  guvcview?

  (Partial?) WORKAROUND is to use dconf-editor:
  dconf-editor /org/gnome/cheese

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

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

[Desktop-packages] [Bug 1892087] Re: screenshot a select area does not work

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

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

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

Title:
  screenshot a select area does not work

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  Shift+Prt Scrn or invoke the screenshot app then select the `select the area 
to grab`. After area selected the save dialogue does not show up.
  screenshot a window or desktop works as normal.
  ubuntu 20.04

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

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

[Desktop-packages] [Bug 1887240] Re: screenshot no longer lets me copy before/without saving, nor choose where to save, if done via keyboard shortcut

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

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

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

Title:
  screenshot no longer lets me copy before/without saving, nor choose
  where to save, if done via keyboard shortcut

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded from 16.04 to 18.04, and unsuprsisingly, in 1 minute
  of use I have already found out a backwards idiotic design decision in
  Gnome that degrades usability (but I bet they did it thinking it was
  an improvement).

  I was used to using gnome-screenshot as follows:
  - I use either the shift+PrintScreen shortcut to grab a rectangle, or (less 
frequently) just the PrintScreen key to capture the whole screen
  - then the popup would show up where I could either copy the screenshot to 
the clipboard, to paste it into Gimp or Telegram, or any other application 
accepting image input (and often not save the screenshot at all); or choose a 
destination to save the screenshot to, which almost never was the default. 

  Now, after upgrading, I took (or wanted to take) a bunch of
  screenshots illustrating some of the pathetic bugs of the disastrous
  upgrade process, but to my surprise, even though I could hear the
  sound effect and see the visual effect of the screenshot being taken,
  no popup would show up. I thought gnome-screenshot was just broken and
  crashing like half of Ubuntu, and that none of the screenshot had been
  taken.

  Later it occurred to me to look at the default destination directory
  ~/Pictures, and it turned out all the screenshots are silently saved
  there.

  
  So now, if I take a screenshot using the keyboard shortcuts, I can neither:
  - copy the screenshot to the clipboard and omit saving it; nor:
  - choose to save it somewhere else other than the default.

  To do that, I have to launch the application manually. I have a
  launcher icon, but still I need two clicks to do what I would normally
  do with a single keyboard shortcut.

  
  I can unserstand that to some people, who just usually save their screenshots 
to the default location, this can be handy. But then it should be an option.

  I can't find a Settings menu or button or anything where I can change
  this behavior to restore the old one. Actually I can't even find a way
  to change the default save destination, which is additionally
  ridiculous.

  If such settings exist, they are undiscoverable.

  
  Additionally, even if this was just a change in default behavior (and hence 
configurable), the fact that the change happened silently is an additional 
serious issue. Given that the behavior changed, the first time I took a 
screenshot (via keyboard shortcut) with the new version, it should have shown a 
message saying "The screenshot was saved to /path/to/saved/screenshot [Don't 
show again]". That's how you change the behavior of things. You don't do it 
silently leaving me to wonder whether the screenshot was saved at all.

  Between the time I got the impressions screenshots were not working,
  and the time it occurred to me to look in the default directory and
  found out, I stopped taking screenshot.

  
  As usual, the Gnome team puts no thought whatsoever into what they do. They 
just keep making the software worse.

  I'm reporting this only to let you know, because as soon as I'm
  finished upgrading to the latest version just to give it a shot, I'm
  pretty sure I'll wipe out my hard disk and install OpenSUSE.

  
  I'm sick of Ubuntu. By the way, the reason I waited 4 years before upgrading, 
is mainly (1) because a single regression (which again is actually a design 
decision by Gnome, but also failure on the side of Ubuntu to patch it) that 
renders Nautilus (a basic component) completely unusable, which is 
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1164016. And to a 
lesser extent (2) the fact that EVERY SINGLE distribution upgrade until now had 
always led to bricking my computer (furtunately not this time, it's just the 
ugly unusable mess that Ubuntu 18.10 is). So I always postpone dist upgrades to 
when I have a few spare hours to waste fixing things and getting my computer 
back to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screenshot 3.25.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
  Uname: Linux 4.15.0-109-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 11 18:56:58 2020
  InstallationDate: Installed on 2013-10-11 (2464 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably

[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package

2020-10-06 Thread Cody Shepherd

My attempts to verify test case k) seem to indicate there is still a
problem somewhere.

I've verified

i) that grub-legacy-ec2 is no longer in the server seed [1]
iv) that the livecd.ubuntu-cpc.manifest contains grub-legacy-ec2 and 
ubuntu-server.

However,

ii) the rootfs manifest has not retained ubuntu-server
iii) cpc "secret sauce" hooks which purge grub-legacy-ec2 have not retained 
ubuntu-server.

The failure of ii) occurred in a livefs-build of the ubuntu-cpc project
in the xenial branch livecd-rootfs at version 2.408.61 (02ea8c93).

The failure of iii) occurred in a build of CPC "secret sauce" hooks
using the Ubuntu Old Fashioned tool [2] and the same branch/revision of
livecd-rootfs described above.

[1] 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/tree/server?h=xenial
[2] https://github.com/chrisglass/ubuntu-old-fashioned

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Invalid
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0

  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled

  j) Perform a release upgrade from the previous ubuntu release to the
  one being tested while having ubuntu-server NOT installed (or use a
  desktop install). At the end, motd-news should be disabled. Verify
  with:

  $ sudo /etc/update-motd.d/50-motd-news --force
  $ (no output)

  k) Test that supporting changes for xenial are in place:

    i) verify gru

[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)

** Summary changed:

- [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X 
display
+ Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X 
display)

** No longer affects: chromium-browser (Ubuntu)

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

Title:
  Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X
  display)

Status in Mutter:
  Unknown
Status in snapd:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run chromium installed via snap in Ubuntu 20.10 when
  running Ubuntu Wayland session. Unfortunately, chromium wouldn't
  start:

  > chromium 
  [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to 
open X display.

  I am able to run Firefox just fine (assuming that Firefox still runs
  on xwayland) and also Intellij snap works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 25 09:45:16 2020
  InstallationDate: Installed on 2016-09-05 (1480 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Snap: chromium 85.0.4183.121 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1898713] Re: Xorg crashes sometimes with Easystrokes

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

This appears to be a duplicate of bug 1733292 so please use that one
from now on.

Separately, I notice you seem to be using the *old* 'intel' graphics
driver (according to XorgLog.txt). If you can find the Xorg config file
(maybe in /usr/share/X11/xorg.conf.d) that is loading the 'intel'
graphics driver then I recommend removing that. The latest driver is
called 'modesetting' which should be used instead of 'intel'. And it
will be used automatically if you remove the config file that was
loading 'intel'.


** This bug has been marked a duplicate of bug 1733292
   Xorg crashed with SIGSEGV in point_on_screen from miPointerSetPosition from 
positionSprite from positionSprite from fill_pointer_events

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

Title:
  Xorg crashes sometimes with Easystrokes

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xorg crashes, session closes, all unsaved data is gone.

  What I did / Reproducing
  ===

  It happens when I use Easystrokes to emulate `Ctrl+F4` or
  `Ctrl+PageUp/Down`.

  So far it happened about 5 recognized times, 3 recorded within the
  last 3(?) month. twice during tab switching in incognito Firefox and
  once in VSCode.

  Reproducability
  
  I feel it's very consistent in crashing in Firefox incognito. But it's not 
purposely reproducible 100%.

  I would give more information, but the stacktrace of the crashdump
  does not tell much. I installed debug symbols for xorg, but they made
  no change viewing it.

  Here is the (obscured) stack trace:

  ```
  Reading symbols from /usr/lib/xorg/Xorg...
  Reading symbols from 
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
  [New LWP 100716]
  [New LWP 100705]
  [New LWP 100704]
  [New LWP 100707]
  [New LWP 100709]
  [New LWP 100708]
  [New LWP 100706]
  [New LWP 100711]
  [New LWP 100710]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  --Type  for more, q to quit, c to continue without paging--
  Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x55a0da61fe9c in miPointerSetPosition (
  pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
  screenx=screenx@entry=0x7f707b57d570, 
  screeny=screeny@entry=0x7f707b57d578, 
  nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
  at ../../../../mi/mipointer.c:610
  610   ../../../../mi/mipointer.c: No such file or directory.
  [Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
  (gdb) 
  (gdb) 
  (gdb) bt full
  #0  0x55a0da61fe9c in miPointerSetPosition
  (pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578, 
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at 
../../../../mi/mipointer.c:610
  pScreenPriv = 
  pScreen = 
  newScreen = 0x254
  x = 802
  y = 596
  switch_screen = 0
  should_constrain_barriers = 0
  i = 
  pPointer = 0x0
  #1  0x55a0da4ec840 in positionSprite
  (dev=dev@entry=0x55a0dc969400, mode=mode@entry=0, 
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580, 
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570, 
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at 
../../../../dix/getevents.c:961
  scr = 
  tmpx = 801.02961125081322
  tmpy = 595.47038874918678
  #2  0x55a0da4ecf4d in positionSprite
  (events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578, 
scre--Type  for more, q to quit, c to continue without paging--
  enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580, 
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at 
../../../../dix/getevents.c:952
  scr = 0x0
  num_events = 2
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #3  fill_pointer_events (events=0x7f708d903c20, 
  events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, 
type=, buttons=buttons@entry=0, ms=ms@entry=289728198, 
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at 
../../../../dix/get

[Desktop-packages] [Bug 1733292] Re: Xorg crashed with SIGSEGV in point_on_screen from miPointerSetPosition from positionSprite from positionSprite from fill_pointer_events

** Tags removed: disco
** Tags added: focal

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

Title:
  Xorg crashed with SIGSEGV in point_on_screen from miPointerSetPosition
  from positionSprite from positionSprite from fill_pointer_events

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  occasional screen locks up, the session ends, reverts to display
  manager (lightdm?), have to log in again.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Nov 20 09:11:46 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.0, 4.13.0-16-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [1028:05a4]
  InstallationDate: Installed on 2014-08-13 (1194 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810)
  MachineType: Dell Inc. OptiPlex 9020
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=e2d4a833-d4fd-4295-95a5-57c52551e6ba ro splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x56286fd4bad0:movswl 0x8(%rdi),%ecx
   PC (0x56286fd4bad0) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xorg-server
  StacktraceTop:
   ()
   miPointerSetPosition ()
   ()
   ()
   GetPointerEvents ()
  Title: Xorg crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 05/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A20
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA20:bd05/23/2017:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.88-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Sep 12 12:13:51 2017
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu6
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1898713] Re: Xorg crashes sometimes with Easystrokes

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Xorg crashes sometimes with Easystrokes

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xorg crashes, session closes, all unsaved data is gone.

  What I did / Reproducing
  ===

  It happens when I use Easystrokes to emulate `Ctrl+F4` or
  `Ctrl+PageUp/Down`.

  So far it happened about 5 recognized times, 3 recorded within the
  last 3(?) month. twice during tab switching in incognito Firefox and
  once in VSCode.

  Reproducability
  
  I feel it's very consistent in crashing in Firefox incognito. But it's not 
purposely reproducible 100%.

  I would give more information, but the stacktrace of the crashdump
  does not tell much. I installed debug symbols for xorg, but they made
  no change viewing it.

  Here is the (obscured) stack trace:

  ```
  Reading symbols from /usr/lib/xorg/Xorg...
  Reading symbols from 
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
  [New LWP 100716]
  [New LWP 100705]
  [New LWP 100704]
  [New LWP 100707]
  [New LWP 100709]
  [New LWP 100708]
  [New LWP 100706]
  [New LWP 100711]
  [New LWP 100710]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  --Type  for more, q to quit, c to continue without paging--
  Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x55a0da61fe9c in miPointerSetPosition (
  pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
  screenx=screenx@entry=0x7f707b57d570, 
  screeny=screeny@entry=0x7f707b57d578, 
  nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
  at ../../../../mi/mipointer.c:610
  610   ../../../../mi/mipointer.c: No such file or directory.
  [Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
  (gdb) 
  (gdb) 
  (gdb) bt full
  #0  0x55a0da61fe9c in miPointerSetPosition
  (pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578, 
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at 
../../../../mi/mipointer.c:610
  pScreenPriv = 
  pScreen = 
  newScreen = 0x254
  x = 802
  y = 596
  switch_screen = 0
  should_constrain_barriers = 0
  i = 
  pPointer = 0x0
  #1  0x55a0da4ec840 in positionSprite
  (dev=dev@entry=0x55a0dc969400, mode=mode@entry=0, 
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580, 
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570, 
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at 
../../../../dix/getevents.c:961
  scr = 
  tmpx = 801.02961125081322
  tmpy = 595.47038874918678
  #2  0x55a0da4ecf4d in positionSprite
  (events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578, 
scre--Type  for more, q to quit, c to continue without paging--
  enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580, 
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at 
../../../../dix/getevents.c:952
  scr = 0x0
  num_events = 2
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #3  fill_pointer_events (events=0x7f708d903c20, 
  events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, 
type=, buttons=buttons@entry=0, ms=ms@entry=289728198, 
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at 
../../../../dix/getevents.c:1434
  num_events = 2
  --Type  for more, q to quit, c to continue without paging--
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #4  0x55a0da4ee620 in GetPointerEvents
  (events=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, type=, type@entry=6, buttons=buttons@entry=0, flags=10, m

[Desktop-packages] [Bug 1898447] Re: HDMI sound output disappears after sleep

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

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

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  umayr  4915 F pulseaudio
   /dev/snd/pcmC0D3p:   umayr  4915 F...m pulseaudio
   /dev/snd/controlC1:  umayr  4915 F pulseaudio
   /dev/snd/controlC2:  umayr  4915 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-12 (267 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1898646] Re: Ubuntu 20.04 without sound with Via 1705 chipset

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

You don't need to do anything more, thanks.

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

Title:
  Ubuntu 20.04 without sound with Via 1705 chipset

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  working very well with ubuntu 18.04 during two years with the chipset Via 
1705,upgrade to ubuntu 20.04 sound do not work. Without sound, only appear 
ficticius in configuration without any device detected.
  We do all the steps indicated in the link 
https://help.ubuntu.com/community/SoundTroubleshootingProcedure but don't 
resolved.
  We like of Ubuntu 20.04, please need a solution. Thanks.

  Estimados, trabajamos muy bien con el Ubuntu 18.04 durante dos añoscon el 
chip Via 1705 sin problemas, com un sonido refinado em caja de sonido 
Harman/Kardon, lamentablemente al actualizar para Ubuntu 20,04 el sonido no se 
escucha, intentamos todos los pasos indicados en el link 
https://help.ubuntu.com/community/SoundTroubleshootingProcedure, pero no 
resolvio.
  Nos agradó el nuevo Ubuntu 20.04, por favor una solución para no desistir de 
este. Gracias.

  Bom, para que fique bem claro, este é um equipamento com o que
  trabalho em varias regiões, por isso se houver algum colegas que
  entenda um destes idiomas, agradeceria uma solução, trabalhamos
  durante dois anos com um chipset Via 1705 num Ubuntu 18.04, ao
  atualizar para a nova versão Ubuntu 20.04 nos deparamos em que o som
  não funciona, a placa não é detectada pelo painel GUI das
  configurações do Gnome, e pelo terminal o pulseaudio não funciona.
  Favor indicar uma solução pois o resto do sistema está estável e
  funcionando, não queremos desistir da atualização. Obrigado

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity935 F timidity
   /dev/snd/pcmC0D0p:   timidity935 F...m timidity
   /dev/snd/seq:timidity935 F timidity
   /dev/snd/timer:  timidity935 f timidity
  CasperMD5CheckResult: skip
  Date: Mon Oct  5 22:31:16 2020
  InstallationDate: Installed on 2018-10-27 (709 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to focal on 2020-10-03 (2 days ago)
  dmi.bios.date: 06/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81H3-M4
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/30/2014:svnECS:pnH81H3-M4:pvr1.0:rvnECS:rnH81H3-M4:rvr1.0:cvnECS:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H81H3-M4
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: ECS

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

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

[Desktop-packages] [Bug 1897224] Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display

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

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

Title:
  [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to
  open X display

Status in Mutter:
  Unknown
Status in snapd:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run chromium installed via snap in Ubuntu 20.10 when
  running Ubuntu Wayland session. Unfortunately, chromium wouldn't
  start:

  > chromium 
  [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to 
open X display.

  I am able to run Firefox just fine (assuming that Firefox still runs
  on xwayland) and also Intellij snap works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 25 09:45:16 2020
  InstallationDate: Installed on 2016-09-05 (1480 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Snap: chromium 85.0.4183.121 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1897224] Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display

2020-10-06 Thread James Henstridge

I've filed https://gitlab.gnome.org/GNOME/mutter/-/issues/1454 upstream
about this regression.

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

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

Title:
  [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to
  open X display

Status in Mutter:
  Unknown
Status in snapd:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run chromium installed via snap in Ubuntu 20.10 when
  running Ubuntu Wayland session. Unfortunately, chromium wouldn't
  start:

  > chromium 
  [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to 
open X display.

  I am able to run Firefox just fine (assuming that Firefox still runs
  on xwayland) and also Intellij snap works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 25 09:45:16 2020
  InstallationDate: Installed on 2016-09-05 (1480 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Snap: chromium 85.0.4183.121 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1892136] Re: reverse prime produces corrupted output on specific resolutions

It appears the Xorg developers already know about it. I don't know
enough about it myself to recommend Ubuntu jumps ahead of them on this.

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

Title:
  reverse prime produces corrupted output on specific resolutions

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  In Progress

Bug description:
  The issue has initially been discovered for resolution 1366x768 on a
  DisplayLink (evdi)-backed device, but applies also to UDL, as well as
  reverse prime setups (rendering on Intel, output through NVidia).

  The issue manifests with 1366x768 and several other resolutions only,
  due to the fact that the GPU seems to use 64-aligned framebuffer
  stride. This is "accidentally" fine with the most popular VGA
  resolutions (e.g. assuming 32bits/4bytes per pixel and FullHD, the
  stride would be 1920*4 -> 7680, which is divisible by 64 w/o a
  remainder, yet 1366*4=5464, 5464/64 = 85.375). The proposed fix is to
  update the stride with the GPU-provided value instead of the Xorg-
  calculated one at the stage of sharing the pixmap between GPUs. Doing
  that at earlier stage would probably require distinguishing between
  allocation of a FB and a generic pixmap, which is the same for Xorg.

  Issue for sure was seen on 18.04 and 19.04, probably still there for
  20.04.

  Upstream report:
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/889

  And posted (not yet integrated) fix:
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/496

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

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

[Desktop-packages] [Bug 1898068] Re: SRU the current 3.34.3 stable update

Groovy is already done. Just add a focal task when ready.

** Tags added: focal groovy

** Changed in: gnome-bluetooth (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  SRU the current 3.34.3 stable update

Status in gnome-bluetooth package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/blob/master/NEWS

  * Test case

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

  Check that evolution works correctly with different emails server and
  with online calendars

  * Regression potential

  The update has some changes around pairing and connecting devices,
  just make sure those functions work correctly

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

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

[Desktop-packages] [Bug 1897224] Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display

2020-10-06 Thread James Henstridge

Looking at the reasoning behind that change, Mutter introduced lazy
initialisation of Xwayland: binding the two sockets, and starting
Xwayland when someone connected to the abstract namespace socket.
Flatpak apps apparently can't speak to the abstract namespace socket, so
would hang forever when started since the connection to the non-abstract
/tmp/.X11-unix socket was never accepted.

Rather than fixing the initialisation logic to start Xwayland on connect
to either socket, they dropped the abstract namespace socket.  I'll talk
to the snapd folks about it, but this sounds like it should be dealt
with on the Mutter side.

** Changed in: mutter (Ubuntu)
   Status: Invalid => 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/1897224

Title:
  [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to
  open X display

Status in snapd:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run chromium installed via snap in Ubuntu 20.10 when
  running Ubuntu Wayland session. Unfortunately, chromium wouldn't
  start:

  > chromium 
  [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to 
open X display.

  I am able to run Firefox just fine (assuming that Firefox still runs
  on xwayland) and also Intellij snap works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 25 09:45:16 2020
  InstallationDate: Installed on 2016-09-05 (1480 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Snap: chromium 85.0.4183.121 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1897224] Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display

2020-10-06 Thread James Henstridge

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1424 is
definitely the culprit here.  Snaps depend on access to the abstract
namespace socket to function correctly.

Inside the sandboxes, snaps see a private /tmp that is under their
complete control.  So there is no /tmp/.X11-unix directory there.  They
can see the abstract namespace socket though, which the client libraries
will use automatically.

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

Title:
  [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to
  open X display

Status in snapd:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run chromium installed via snap in Ubuntu 20.10 when
  running Ubuntu Wayland session. Unfortunately, chromium wouldn't
  start:

  > chromium 
  [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to 
open X display.

  I am able to run Firefox just fine (assuming that Firefox still runs
  on xwayland) and also Intellij snap works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 25 09:45:16 2020
  InstallationDate: Installed on 2016-09-05 (1480 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Snap: chromium 85.0.4183.121 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1898620] Re: package libreoffice-draw 1:6.0.7-0ubuntu0.18.04.10 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2020-10-06 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libreoffice-draw 1:6.0.7-0ubuntu0.18.04.10 failed to
  install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error
  exit status 2

Status in libreoffice package in Ubuntu:
  New

Bug description:
  It is having some bug issues

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-draw 1:6.0.7-0ubuntu0.18.04.10
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Oct  6 00:31:06 2020
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2020-06-22 (104 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  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: libreoffice
  Title: package libreoffice-draw 1:6.0.7-0ubuntu0.18.04.10 failed to 
install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: Upgraded to focal on 2020-10-05 (0 days ago)

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

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

[Desktop-packages] [Bug 1898620] Re: package libreoffice-draw 1:6.0.7-0ubuntu0.18.04.10 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2020-10-06 Thread Seth Arnold

** Information type changed from Private Security to Public

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

Title:
  package libreoffice-draw 1:6.0.7-0ubuntu0.18.04.10 failed to
  install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error
  exit status 2

Status in libreoffice package in Ubuntu:
  New

Bug description:
  It is having some bug issues

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-draw 1:6.0.7-0ubuntu0.18.04.10
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Oct  6 00:31:06 2020
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2020-06-22 (104 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  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: libreoffice
  Title: package libreoffice-draw 1:6.0.7-0ubuntu0.18.04.10 failed to 
install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: Upgraded to focal on 2020-10-05 (0 days ago)

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

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

[Desktop-packages] [Bug 1896397] Update Released

The verification of the Stable Release Update for language-selector 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 language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1896397

Title:
  [UIFe] Tweak Arabic font

Status in language-selector package in Ubuntu:
  Fix Released
Status in language-selector source package in Focal:
  Fix Released

Bug description:
  [Impact]

  This is a follow-up of bug #1891733. After the new default font for
  Arabic had made it to focal, we got some additional feedback at
  . After further discussion,
  trial and error, and multiple changes in groovy it has landed in a
  consensus to make these adjustments:

  * Rename the .conf file from 69- to 56-

  * Drop binding="strong"

  * Drop the specification for monospace, and with that fall back
to DejaVu for Arabic monospace

  The significance of the changes, which motivates the proposed SRU, is
  made up of:

  1. Use DejaVu Sans Mono as default Arabic font for monospace
 instead of the previous non-mono font

  2. No longer conflicts with Kubuntu's custom font configuration

  [Test case]

  * Install the language-selector-{gnome,common} packages
from focal-proposed.

  * Open the Language Support tool and install Arabic.

  * Open a terminal window, run the below commands and confirm
that you get the same output:

$ LC_CTYPE=ar_EG.UTF-8 fc-match
NotoSansArabicUI-Regular.ttf: "Noto Sans Arabic UI" "Regular"
$ LC_CTYPE=ar_EG.UTF-8 fc-match monospace
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"

  [Regression risk]

  For some users this will change the default monospace font for
  rendering Arabic. That's the point. :)

  The change will only affect users with an Arabic locale. The risk that
  other users would be affected by the change is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1896397/+subscriptions

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

[Desktop-packages] [Bug 1896397] Re: [UIFe] Tweak Arabic font

This bug was fixed in the package language-selector - 0.204.2

---
language-selector (0.204.2) focal; urgency=medium

  * fontconfig/69-language-selector-ar.conf (LP: #1896397):
- Rename to 56-language-selector-ar.conf
- Drop binding="strong"
- Drop the specification for monospace, and with that fall back to
  DejaVu for Arabic monospace

 -- Gunnar Hjalmarsson   Sun, 27 Sep 2020 22:07:12
+0200

** Changed in: language-selector (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  [UIFe] Tweak Arabic font

Status in language-selector package in Ubuntu:
  Fix Released
Status in language-selector source package in Focal:
  Fix Released

Bug description:
  [Impact]

  This is a follow-up of bug #1891733. After the new default font for
  Arabic had made it to focal, we got some additional feedback at
  . After further discussion,
  trial and error, and multiple changes in groovy it has landed in a
  consensus to make these adjustments:

  * Rename the .conf file from 69- to 56-

  * Drop binding="strong"

  * Drop the specification for monospace, and with that fall back
to DejaVu for Arabic monospace

  The significance of the changes, which motivates the proposed SRU, is
  made up of:

  1. Use DejaVu Sans Mono as default Arabic font for monospace
 instead of the previous non-mono font

  2. No longer conflicts with Kubuntu's custom font configuration

  [Test case]

  * Install the language-selector-{gnome,common} packages
from focal-proposed.

  * Open the Language Support tool and install Arabic.

  * Open a terminal window, run the below commands and confirm
that you get the same output:

$ LC_CTYPE=ar_EG.UTF-8 fc-match
NotoSansArabicUI-Regular.ttf: "Noto Sans Arabic UI" "Regular"
$ LC_CTYPE=ar_EG.UTF-8 fc-match monospace
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"

  [Regression risk]

  For some users this will change the default monospace font for
  rendering Arabic. That's the point. :)

  The change will only affect users with an Arabic locale. The risk that
  other users would be affected by the change is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1896397/+subscriptions

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

[Desktop-packages] [Bug 1879183] Re: Cheese does not show preferences/options/menus to non-GNOME Users

I'd like to see this tested in an Ubuntu Gnome session to confirm that
it does not regress there.

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

Title:
  Cheese  does not show preferences/options/menus to non-GNOME Users

Status in cheese package in Ubuntu:
  Fix Released
Status in cheese source package in Focal:
  Fix Committed
Status in cheese package in Debian:
  New

Bug description:
  [Impact] 
  Cheese no longer displays its menu button on non-GNOME desktop environments.
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62

  Xubuntu uses cheese as its default camera program. Advanced users can
  still change these settings through dconf-editor, but this is neither
  convenient nor intuitive.

  [Test Case]

  Use the cheese program in Xubuntu/xfce, Kubuntu/KDE or other non-GNOME
  desktop environments. Notice missing menu in titlebar.

  [Regression Potential]

  The most likely regression would be if the patch disabled the menu in
  GNOME. Testing has not shown this to be an issue.

  
  [ORIGINAL REPORT]
  Cheese has removed the GUI method of accessing preferences for non-GNOME 
users.
  
https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d

  I'm not sure if upstream cheese devs care enough to fix it:
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62
  https://gitlab.gnome.org/GNOME/cheese/-/issues/52

  Should Xubuntu default to a different camera program, such as
  guvcview?

  (Partial?) WORKAROUND is to use dconf-editor:
  dconf-editor /org/gnome/cheese

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

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

[Desktop-packages] [Bug 357315] Re: "There was an error while getting the sharing information"

2020-10-06 Thread Jg-jguk

Still occurs every week. Often after a reboot.

Could it at least be possible to close this awful popup?

The [Close] button is broken.

** Attachment added: "There was an error getting the sharing information"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/357315/+attachment/5418581/+files/samba__Screenshot%20from%202020-10-06%2023-22-17.png

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

Title:
  "There was an error while getting the sharing information"

Status in nautilus-share package in Ubuntu:
  New

Bug description:
  Sometimes I get this message. "There was an error while getting the
  sharing information" bla bla bla something about samba.

  I cannot reproduce it because it sometimes occurs. Especially when I
  right click on a folder and see its properties.

  My version is Ubuntu 8.10 with all updates.

  I am new to Linux.

  Samba is not installed, not running.

  I am concerned somehow may be it can be a intrusion attempt or
  something like that?

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

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

[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

2020-10-06 Thread Emmett Keyser

FWIW this fixed the issue for me.

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

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

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

[Desktop-packages] [Bug 1870794] Re: Update for Unicode 13

2020-10-06 Thread Jeremy Bicha

The workflow does have a bit of an awkward consequence.

It means that bugs that affect a stable release but are fixed in a newer
release (or development series) are marked as Fix Released, unless
someone volunteers to fix the bug quickly.

I believe it's also harder for users to browse and find bugs like this
that affect them on the supported release they are running.

So I think your workflow works fine during the development cycle but I
don't know if it's ideal for stable releases.

Yes, I know y'all have had this workflow for years. I have been
uncomfortable with it for years too. 😉

Anyway, I'm not yet volunteering to do this SRU.

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

Title:
  Update for Unicode 13

Status in fonts-noto-color-emoji package in Ubuntu:
  Fix Released

Bug description:
  The current version is missing some emojis which are already available
  upstream. I didn't check them all but it seems they are v13 emojis.

  You can see the missing ones as tofu from here:
  https://unicode.org/emoji/charts/full-emoji-list.html

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: fonts-noto-color-emoji 0~20191119-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr  4 17:25:41 2020
  Dependencies:
   
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: fonts-noto-color-emoji
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1870794/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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-10-06 Thread Benjamin Rogoll

Hey Guys, didnt read everything, just for me the simplest version to fix
stuff on Manjaro is to download the 5.8.13-1 Kernel from the Manjaro
gitlab and install xf86-input-synaptics via pacman. I have not managed
to get it to work on Mint, but here it works flawlessly.

-- 
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 Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  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.

Re: [Desktop-packages] [Bug 1898646] Re: Ubuntu 20.04 without sound with Via 1705 chipset

2020-10-06 Thread Marcelo Smacom

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

Thanks for your contatct, gracias por seu contacto, obrigado pela resposta.
Reading with attention bug#1793640 and installing with apt-get install timidity
timidity-daemon, all the sound return with excelent funcionality.

How should I report correctly that the problem of this bug was fixed?
Como debo informar que el problema deste bug fué solucionado?
Sem querer incomodar mais ficamos ao seu dispor.

Marcelo Mattiello.
SMA Com. e Rep.de Informática Ltda.
Fone/Fax: 0xx47-3045-2590
Email: marc...@smacom.com.br
Celular: 0xx47-8402-5563
Skype: marcelo_smacom
www.smacom.com.br

Data: 05/10/2020
De: Daniel van Vugt <1898...@bugs.launchpad.net>
Para: Bug 1898646 <1898...@bugs.launchpad.net>
Assunto: [Bug 1898646] Re: Ubuntu 20.04 without sound with Via 1705 chipset ***
This bug is a duplicate of bug 1793640 ***
https://bugs.launchpad.net/bugs/1793640

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

** This bug has been marked a duplicate of bug 1793640
Pulseaudio fails to detect sound card, while timidity is installed

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1898646

Title:
Ubuntu 20.04 without sound with Via 1705 chipset

Status in pulseaudio package in Ubuntu:
New

Bug description:
working very well with ubuntu 18.04 during two years with the chipset
Via 1705,upgrade to ubuntu 20.04 sound do not work. Without sound, only appear
ficticius in configuration without any device detected.
We do all the steps indicated in the link
https://help.ubuntu.com/community/SoundTroubleshootingProcedure but don't
resolved.
We like of Ubuntu 20.04, please need a solution. Thanks.

Estimados, trabajamos muy bien con el Ubuntu 18.04 durante dos
añoscon el chip Via 1705 sin problemas, com un sonido refinado em caja
de sonido Harman/Kardon, lamentablemente al actualizar para Ubuntu 20,04 el
sonido no se escucha, intentamos todos los pasos indicados en el link
https://help.ubuntu.com/community/SoundTroubleshootingProcedure, pero no
resolvio.
Nos agradó el nuevo Ubuntu 20.04, por favor una solución
para no desistir de este. Gracias.

Bom, para que fique bem claro, este é um equipamento com o que
trabalho em varias regiões, por isso se houver algum colegas que
entenda um destes idiomas, agradeceria uma solução,
trabalhamos
durante dois anos com um chipset Via 1705 num Ubuntu 18.04, ao
atualizar para a nova versão Ubuntu 20.04 nos deparamos em que o
som
não funciona, a placa não é detectada pelo painel
GUI das
configurações do Gnome, e pelo terminal o pulseaudio
não funciona.
Favor indicar uma solução pois o resto do sistema
está estável e
funcionando, não queremos desistir da atualização.
Obrigado

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.7
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: timidity 935 F timidity
/dev/snd/pcmC0D0p: timidity 935 F...m timidity
/dev/snd/seq: timidity 935 F
timidity
/dev/snd/timer: timidity 935 f
timidity
CasperMD5CheckResult: skip
Date: Mon Oct 5 22:31:16 2020
InstallationDate: Installed on 2018-10-27 (709 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
ProcEnviron:
LANGUAGE=pt_BR:pt:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=pt_BR.UTF-8
SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to focal on 2020-10-03 (2 days ago)
dmi.bios.date: 06/30/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81H3-M4
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/30/2014:svnECS:pnH81H3-M4:pvr1.0:rvnECS:rnH81H3-M4:rvr1.0:cvnECS:ct3:cvr1.0:

dmi.produc

[Desktop-packages] [Bug 1898785] [NEW] [VivoBook 15_ASUS Laptop X542UF, Realtek ALC294, Speaker, Internal] No sound at all

2020-10-06 Thread yochay

Public bug reported:

As I tried to update my files, and install other addons from the terminal, 
nothing happened.. 
On my computer I have dual boot option and when Im using Windows it works fine. 
At ubuntu the speakers doesnt work at any application..

Thanks for you help :)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  yochay 1124 F pulseaudio
 /dev/snd/pcmC0D0p:   yochay 1124 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  6 23:36:02 2020
InstallationDate: Installed on 2020-09-23 (13 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  yochay 1124 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [VivoBook 15_ASUS Laptop X542UF, Realtek ALC294, Speaker, Internal] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X542UF.306
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X542UF
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.:bvrX542UF.306:bd05/22/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX542UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook 15_ASUS Laptop X542UF
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1898785

Title:
  [VivoBook 15_ASUS Laptop X542UF, Realtek ALC294, Speaker, Internal] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  As I tried to update my files, and install other addons from the terminal, 
nothing happened.. 
  On my computer I have dual boot option and when Im using Windows it works 
fine. At ubuntu the speakers doesnt work at any application..

  Thanks for you help :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yochay 1124 F pulseaudio
   /dev/snd/pcmC0D0p:   yochay 1124 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  6 23:36:02 2020
  InstallationDate: Installed on 2020-09-23 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yochay 1124 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [VivoBook 15_ASUS Laptop X542UF, Realtek ALC294, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X542UF.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X542UF
  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.:bvrX542UF.306:bd05/22/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX542UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook 15_ASUS Laptop X542UF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing

[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server

2020-10-06 Thread Jeff Lane

+1 Dann's suggestion works great when manually installing the packages
via apt.

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

Title:
  'ubuntu-drivers --gpgpu install' installs a lot of unnecessary
  packages, including a full desktop environment on Ubuntu Server

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  When I install the packaged nVidia drivers using --gpgpu, I expect
  that I am getting compute related GPGPU drivers.  Instead, I find that
  on a fresh Focal installation of Ubuntu Server, I also get a full
  desktop environment.

  This sets us up nicely for this bug:
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559

  because this pulls in gdm3 and a whole host of unnecessary desktop
  packages but does nothing to mitigate the gdm3 propensity to
  autosuspend, which makes the server become unresponsive when there is
  no user activity (even when it's running workloads on the GPGPU, the
  server can still autosuspend).

  Additionally, this adds a software stack that causes unnecessary CPU
  and memory usage on a machine that is meant to run headless and devote
  all resources to handling GPGPU compute activities.

  This is gpgpu mode
  
  Reading package lists... Done 
  
  Building dependency tree  
   
  Reading state information... Done 
  
  The following additional packages will be installed:  

apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils 
bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 
dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common 
enchant-2
evolution-data-server evolution-data-server-common fprintd gcr gdm3 
geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 
gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 
gir1.2-gnomebluetooth-1.0
gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 
gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 
gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 
gir1.2-upowerglib-1.0
gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center 
gnome-control-center-data gnome-control-center-faces gnome-desktop3-data 
gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts 
gnome-session-bin gnome-session-common
gnome-settings-daemon gnome-settings-daemon-common gnome-shell 
gnome-shell-common gnome-startup-applications gnome-user-docs 
gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 
iio-sensor-proxy im-config ippusbxd
language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 
libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 
libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 
libcolord-gtk1
libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 
libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 
libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 
libedataserverui-1.2-2
libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 
libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 
libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2
libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 
libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common 
libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 
libgssdp-1.2-0 libgtk2.0-0
libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common 
libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 
libgweather-common libharfbuzz-icu0 libhunspell-1.7-0 libhyphen0 libibus-1.0-5 
libical3 libice6
libieee1284-3 libimobiledevice6 libjavascriptcoregtk-4.0-18 libldb2 
libmediaart-2.0-0 libmozjs-68-0 libmutter-6-0 libnma0 libnotify4 libnss-mdns 
libnvidia-cfg1-435 libnvidia-common-435 libnvidia-compute-435 
libnvidia-decode-435
libnvidia-encode-435 libnvidia-fbc1-435 libnvidia-gl-435 libnvidia-ifr1-435 
libopenjp2-7 libpam-fprintd libpam-gnome-keyring libphonenumber7 libplist3 
libprotobuf17 libpulse-mainloop-glib0 libpulsedsp libpwquality-common 
libpwquality1
librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 
librygel-server-2.6-2 libsane libsane-common libsbc1 libsecret-1-0 
libsecret-common libsm6 libsmbclient libsnapd-glib1 libsoxr0 libspeexdsp1

[Desktop-packages] [Bug 1898447] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1898447/+attachment/5418510/+files/PulseList.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/1898447

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  umayr  4915 F pulseaudio
   /dev/snd/pcmC0D3p:   umayr  4915 F...m pulseaudio
   /dev/snd/controlC1:  umayr  4915 F pulseaudio
   /dev/snd/controlC2:  umayr  4915 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-12 (267 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1898447] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1898447/+attachment/5418509/+files/ProcEnviron.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/1898447

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  umayr  4915 F pulseaudio
   /dev/snd/pcmC0D3p:   umayr  4915 F...m pulseaudio
   /dev/snd/controlC1:  umayr  4915 F pulseaudio
   /dev/snd/controlC2:  umayr  4915 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-12 (267 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1898447] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1898447/+attachment/5418508/+files/ProcCpuinfoMinimal.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/1898447

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  umayr  4915 F pulseaudio
   /dev/snd/pcmC0D3p:   umayr  4915 F...m pulseaudio
   /dev/snd/controlC1:  umayr  4915 F pulseaudio
   /dev/snd/controlC2:  umayr  4915 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-12 (267 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1898447] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1898447/+attachment/5418506/+files/CurrentDmesg.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/1898447

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  umayr  4915 F pulseaudio
   /dev/snd/pcmC0D3p:   umayr  4915 F...m pulseaudio
   /dev/snd/controlC1:  umayr  4915 F pulseaudio
   /dev/snd/controlC2:  umayr  4915 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-12 (267 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1898447] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1898447/+attachment/5418507/+files/Dependencies.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/1898447

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  umayr  4915 F pulseaudio
   /dev/snd/pcmC0D3p:   umayr  4915 F...m pulseaudio
   /dev/snd/controlC1:  umayr  4915 F pulseaudio
   /dev/snd/controlC2:  umayr  4915 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-12 (267 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1898447] Re: HDMI sound output disappears after sleep

apport information

** Tags added: apport-collected

** Description changed:

  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME settings
  sound settings after waking the computer up from sleep. Running `pacmd
  list-cards` does show the HDMI sound output listed. I can bring the
  output back as a choice if I run `pulseaudio -k`, but I will lose the
  choice to select this output if I put the computer to sleep, leaving me
  only with the S/PDIF output from my motherboard.
  
  I didnt see this issue prior to what I suspect was an `apt upgrade`.
  
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3
  
  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.9
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  umayr  4915 F pulseaudio
+  /dev/snd/pcmC0D3p:   umayr  4915 F...m pulseaudio
+  /dev/snd/controlC1:  umayr  4915 F pulseaudio
+  /dev/snd/controlC2:  umayr  4915 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-01-12 (267 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: pulseaudio 1:13.99.1-1ubuntu3.6
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
+ Tags:  focal
+ Uname: Linux 5.4.0-48-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/06/2019
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F11
+ dmi.board.asset.tag: Default string
+ dmi.board.name: X570 AORUS MASTER
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: x.x
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.family: Default string
+ dmi.product.name: X570 AORUS MASTER
+ dmi.product.sku: Default string
+ dmi.product.version: -CF
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1898447/+attachment/5418505/+files/AlsaInfo.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/1898447

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMA

[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server

2020-10-06 Thread dann frazier

gdm3 is being pulled in via a "Recommends" chain. Disabling recommends will 
avoid it[*]. 
On my groovy system it reduced new packages installed from 452/291MB of 
archives to 56/165MB of archives. Seems like the right thing to do for at least 
--gpgpu installs - but maybe for all?

[*]
--- /usr/bin/ubuntu-drivers.orig2020-07-29 15:24:08.0 +
+++ /usr/bin/ubuntu-drivers 2020-10-06 19:18:53.208559657 +
@@ -155,7 +155,8 @@
 return
 
 ret = subprocess.call(['apt-get', 'install', '-o',
-'DPkg::options::=--force-confnew', '-y'] + to_install)
+   'DPkg::options::=--force-confnew', '-y',
+   '--no-install-recommends'] + to_install)
 
 oem_meta_to_install = fnmatch.filter(to_install, 'oem-*-meta')

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

Title:
  'ubuntu-drivers --gpgpu install' installs a lot of unnecessary
  packages, including a full desktop environment on Ubuntu Server

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  When I install the packaged nVidia drivers using --gpgpu, I expect
  that I am getting compute related GPGPU drivers.  Instead, I find that
  on a fresh Focal installation of Ubuntu Server, I also get a full
  desktop environment.

  This sets us up nicely for this bug:
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559

  because this pulls in gdm3 and a whole host of unnecessary desktop
  packages but does nothing to mitigate the gdm3 propensity to
  autosuspend, which makes the server become unresponsive when there is
  no user activity (even when it's running workloads on the GPGPU, the
  server can still autosuspend).

  Additionally, this adds a software stack that causes unnecessary CPU
  and memory usage on a machine that is meant to run headless and devote
  all resources to handling GPGPU compute activities.

  This is gpgpu mode
  
  Reading package lists... Done 
  
  Building dependency tree  
   
  Reading state information... Done 
  
  The following additional packages will be installed:  

apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils 
bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 
dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common 
enchant-2
evolution-data-server evolution-data-server-common fprintd gcr gdm3 
geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 
gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 
gir1.2-gnomebluetooth-1.0
gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 
gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 
gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 
gir1.2-upowerglib-1.0
gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center 
gnome-control-center-data gnome-control-center-faces gnome-desktop3-data 
gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts 
gnome-session-bin gnome-session-common
gnome-settings-daemon gnome-settings-daemon-common gnome-shell 
gnome-shell-common gnome-startup-applications gnome-user-docs 
gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 
iio-sensor-proxy im-config ippusbxd
language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 
libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 
libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 
libcolord-gtk1
libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 
libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 
libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 
libedataserverui-1.2-2
libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 
libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 
libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2
libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 
libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common 
libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 
libgssdp-1.2-0 libgtk2.0-0
libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common 
libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 
libgweather-common libharfbuzz-icu0 libhunspell-1.7-0 libhyphen0 l

[Desktop-packages] [Bug 495981] Re: NM disconnects Wi-Fi every 2 minutes but iwconfig+dhclient and wicd don't -- ath9k

2020-10-06 Thread Chris

I'm going to bump this, as the last report was years ago. I'm now
experiencing this issue on a Qualcomm Atheros AR938x device I've had for
years now. Same issue with constant disconnects as well as a new issue
that might involve iommu?

[  680.361521] ath9k :21:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x0010 address=0xfdee1544 flags=0x]
[  680.425700] ath9k :21:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x0010 address=0xfe720fc4 flags=0x]
[  680.425707] ath9k :21:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x0010 address=0xfe721000 flags=0x]
[  680.489520] ath9k :21:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x0010 address=0xff0d5a44 flags=0x]
[  680.650051] wlo1: authenticate with 10:c3:7b:ce:7e:ac
[  680.665173] wlo1: send auth to 10:c3:7b:ce:7e:ac (try 1/3)
[  680.666229] wlo1: authenticated
[  680.669072] wlo1: associate with 10:c3:7b:ce:7e:ac (try 1/3)
[  680.670356] wlo1: RX AssocResp from 10:c3:7b:ce:7e:ac (capab=0x11 status=0 
aid=4)
[  680.670494] wlo1: associated
[ 1014.692234] wlo1: authenticate with 10:c3:7b:ce:7e:ac
[ 1014.707630] wlo1: send auth to 10:c3:7b:ce:7e:ac (try 1/3)
[ 1014.708714] wlo1: authenticated
[ 1014.711340] wlo1: associate with 10:c3:7b:ce:7e:ac (try 1/3)
[ 1014.712644] wlo1: RX AssocResp from 10:c3:7b:ce:7e:ac (capab=0x11 status=0 
aid=4)
[ 1014.712784] wlo1: associated
[ 1295.496298] wlo1: authenticate with 10:c3:7b:ce:7e:ac
[ 1295.511421] wlo1: send auth to 10:c3:7b:ce:7e:ac (try 1/3)
[ 1295.512484] wlo1: authenticated
[ 1295.514554] wlo1: associate with 10:c3:7b:ce:7e:ac (try 1/3)
[ 1295.515851] wlo1: RX AssocResp from 10:c3:7b:ce:7e:ac (capab=0x11 status=0 
aid=4)

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

Title:
  NM disconnects Wi-Fi every 2 minutes but iwconfig+dhclient and wicd
  don't -- ath9k

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager

  I have Dell studio XPS 13 running:
  Description:  Ubuntu 9.10
  Release:  9.10

  with wifi card (lspci):
  06:00.0 Network controller: Atheros Communications Inc. AR928X Wireless 
Network Adapter (PCI-Express) (rev 01)

  that works (tries to) with ath9k module.

  It connects to my access point and works ok however, It disconnects every 2-3 
min saying (in dmesg):
  [  311.600306] wlan0: RX AssocResp from 00:1d:68:0c:97:63 (capab=0x411 
status=0 aid=2)
  and then automatically reconnects... I have tried different drivers and other 
things

  Interestingly when I right-clicked on network manger applet, select ¨disable 
networking¨ and then set up everything myself on console using iwconfig and 
dhclient. IT WORKS!!!
  no disconnections
  wpa_supplicant is still running in a background but not doing anything (my 
wifi has WEP encryption).

  I´ve seen some similar reports in Internet but they seem to think that
  it is a driver problem when to me it looks like a NetworkManager
  issue...

  Hope it helps

  drphd

  ProblemType: Bug
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sat Dec 12 19:42:18 2009
  DistroRelease: Ubuntu 9.10
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  IpRoute:
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.65
   172.16.77.0/24 dev vmnet1  proto kernel  scope link  src 172.16.77.1
   172.16.158.0/24 dev vmnet8  proto kernel  scope link  src 172.16.158.1
   default via 192.168.1.254 dev wlan0
  NonfreeKernelModules: nvidia
  Package: network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: network-manager
  Uname: Linux 2.6.31-16-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/495981/+subscriptions

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

[Desktop-packages] [Bug 1898771] [NEW] suspend does not lock screen Fresh Ubuntu Mate 20.04.1

2020-10-06 Thread Richard Silver

Public bug reported:

When suspending my freshly installed 20.04.1 system I noticed that on waking a 
password is not required. lightdm does not have locking enabled on suspend. A 
workaround I found from pszafer
 on archlinux blog. 

Quoted below:


create lockscreen.sh file somewhere in your home directory with:

#!/bin/sh
XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" dm-tool lock
- I've prefer just for sure creating dmlock.service file in home dir and create 
symlink to /etc/systemd/system.
File has to be in /etc/systemd/system/dmlock.service

[Unit]
Description=DM Lock before sleep
Before=sleep.target

[Service]
ExecStart=/home/user/dir/lockscreen.sh

[Install]
WantedBy=sleep.target
For your needs, you probably need hibernate.target.

Next run following commands:

systemctl daemon-reload
systemctl enable dmlock.service
Just for sure it is working you could run:

systemctl list-unit-files
systemctl start dmlock.service
Hope it helps you a little

** Affects: ubuntu-mate
 Importance: Undecided
 Status: New

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


** Tags: lightdm lock security suspend unlock

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

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

Title:
  suspend does not lock screen Fresh Ubuntu Mate 20.04.1

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  When suspending my freshly installed 20.04.1 system I noticed that on waking 
a password is not required. lightdm does not have locking enabled on suspend. A 
workaround I found from pszafer
   on archlinux blog. 

  Quoted below:

  
  create lockscreen.sh file somewhere in your home directory with:

  #!/bin/sh
  XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" dm-tool lock
  - I've prefer just for sure creating dmlock.service file in home dir and 
create symlink to /etc/systemd/system.
  File has to be in /etc/systemd/system/dmlock.service

  [Unit]
  Description=DM Lock before sleep
  Before=sleep.target

  [Service]
  ExecStart=/home/user/dir/lockscreen.sh

  [Install]
  WantedBy=sleep.target
  For your needs, you probably need hibernate.target.

  Next run following commands:

  systemctl daemon-reload
  systemctl enable dmlock.service
  Just for sure it is working you could run:

  systemctl list-unit-files
  systemctl start dmlock.service
  Hope it helps you a little

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

-- 
Mailing list: https://launchpad.net/~desktop-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] Update Released

The verification of the Stable Release Update for mutter 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1558886

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

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  Using Ubuntu 16.04 and 20.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

  

  [  Test case ]

  Run xinput and figure device IDs for your mouse.
  Run this evil script with 9 changed (be sure to change both) to your id:

for ((;;)) do xinput disable 9; echo Disabled; xinput enable 9; echo
  Enabled; done

  While the script runs, open some context menu in some program. It may require 
a few clicks due to evil script enabling/disabling mouse.
  This will sometimes crash GTK programs due to a mirror bug in GTK.

  GNOME Shell should not crash

  [ Regression potential ]

  Devices might be not be properly recognized when plugged and unplugged

  
  

  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 VMASignal: 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/mutter/+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 1896818] Update Released

The verification of the Stable Release Update for mutter 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896818

Title:
  Gnome-shell crash after turn display off in mutter
  3.36.6-ubuntu0.20.04.1 (NVIDIA)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  In Ubuntu 20.04.1 [focal-proposed]:

  [ Impact ]
  GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1.
  With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), 
all works fine.

  [ Test case ]
  Steps to reproduce the error:
  1) Lock screen;
  2) Turn off the display;
  3) Turn on the display;

  And the Gnome Shell crash and show us a blank screen with the message:
  "Oh no! Something has gone wrong."

  [ Regression potential ]
  This very fix was already handled as part of bug #1889090 and we had no 
regression report,.

  However, one possible is that the screen size is not set properly for
  the session, or that panning is enabled.

  [ Workaround ]
  Downgrade the libmutter package temporarily.

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.6-1ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
  Uname: Linux 5.4.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 23 15:57:17 2020
  InstallationDate: Installed on 2020-08-15 (38 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

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

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

[Desktop-packages] [Bug 1892440] Update Released

The verification of the Stable Release Update for mutter 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

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

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

[Desktop-packages] [Bug 1896332] Update Released

The verification of the Stable Release Update for mutter 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896332

Title:
  SRU 3.36.6

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

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.6

  [ 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 device management, desktop background
  image handling, screen-casting and night-switch.

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

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

[Desktop-packages] [Bug 1898769] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux-gnu/libnvidia-ml.so', which is also in package libnvidia-c

2020-10-06 Thread Deb Vorndran

Public bug reported:

Lenovo IdeaPad doesn't recognize my external hdmi monitor, says it's not
connected.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Oct  6 14:28:52 2020
ErrorMessage: trying to overwrite '/usr/lib/i386-linux-gnu/libnvidia-ml.so', 
which is also in package libnvidia-compute-450:i386 450.66-0ubuntu0.20.04.1
InstallationDate: Installed on 2020-02-23 (225 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 (not installed) failed to install/upgrade: trying to 
overwrite '/usr/lib/i386-linux-gnu/libnvidia-ml.so', which is also in package 
libnvidia-compute-450:i386 450.66-0ubuntu0.20.04.1
UpgradeStatus: Upgraded to focal on 2020-08-25 (41 days ago)

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


** Tags: amd64 apport-package focal

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/usr/lib/i386-linux-gnu/libnvidia-ml.so', which is also
  in package libnvidia-compute-450:i386 450.66-0ubuntu0.20.04.1

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

Bug description:
  Lenovo IdeaPad doesn't recognize my external hdmi monitor, says it's
  not connected.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Oct  6 14:28:52 2020
  ErrorMessage: trying to overwrite '/usr/lib/i386-linux-gnu/libnvidia-ml.so', 
which is also in package libnvidia-compute-450:i386 450.66-0ubuntu0.20.04.1
  InstallationDate: Installed on 2020-02-23 (225 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/usr/lib/i386-linux-gnu/libnvidia-ml.so', which is also in 
package libnvidia-compute-450:i386 450.66-0ubuntu0.20.04.1
  UpgradeStatus: Upgraded to focal on 2020-08-25 (41 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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()

This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2

---
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previous fixes, gbp has been a bad guy this time! (LP: #1896818)

mutter (3.36.6-1ubuntu0.20.04.1) focal; urgency=medium

  * Merge with debian, containing new stable release (LP: #1896332)
  * debian/patches:
- Refresh patches and drop applied ones
- Don't set the font-dpi on clutter-backend-x11 (LP: #1892440)
- Cherry-pick upstream night-switch fixes for 3.36 branch
- Cherry-pick upstream fixes for handling X11 devices removal
  (LP: #1558886)
  * xrandr-scaling: Don't update UI scale factor on xrandr-manager creation
(LP: #1892440)
  * debian/control: Revert pipewire version bumping
  * Remaining changes with debian:
- debian/control:
  + Update VCS flags to point to ubuntu salsa branch
- debian/gbp.conf: update branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr

mutter (3.36.6-1) unstable; urgency=medium

  * Team upload
  * New upstream release
  * Update symbols file
  * d/control.in, d/rules: Enable Pipewire on Debian (but not Ubuntu).
Now that we have Pipewire 0.3, we can enable screencasting and remote
desktop support again.

mutter (3.36.5-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Screencast fixes and improvements
- Fix glitches when subsurfaces extend outside the toplevel
- Improve background display in overview workspace switcher
- Fix wine copy & paste
- Plug memory leaks
  * Drop patches that were applied upstream

mutter (3.36.4-1) unstable; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop

 -- Marco Trevisan (Treviño)   Wed, 23 Sep 2020
22:03:53 +0200

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

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

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

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  Using Ubuntu 16.04 and 20.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

  

  [  Test case ]

  Run xinput and figure device IDs for your mouse.
  Run this evil script with 9 changed (be sure to change both) to your id:

for ((;;)) do xinput disable 9; echo Disabled; xinput enable 9; echo
  Enabled; done

  While the script runs, open some context menu in some program. It may require 
a few clicks due to evil script enabling/disabling mouse.
  This will sometimes crash GTK programs due to a mirror bug in GTK.

  GNOME Shell should not crash

  [ Regression potential ]

  Devices might be not be properly recognized when plugged and unplugged

  
  

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

  lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable
  google-chrome-stable:
    Install

[Desktop-packages] [Bug 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))

This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2

---
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previous fixes, gbp has been a bad guy this time! (LP: #1896818)

mutter (3.36.6-1ubuntu0.20.04.1) focal; urgency=medium

  * Merge with debian, containing new stable release (LP: #1896332)
  * debian/patches:
- Refresh patches and drop applied ones
- Don't set the font-dpi on clutter-backend-x11 (LP: #1892440)
- Cherry-pick upstream night-switch fixes for 3.36 branch
- Cherry-pick upstream fixes for handling X11 devices removal
  (LP: #1558886)
  * xrandr-scaling: Don't update UI scale factor on xrandr-manager creation
(LP: #1892440)
  * debian/control: Revert pipewire version bumping
  * Remaining changes with debian:
- debian/control:
  + Update VCS flags to point to ubuntu salsa branch
- debian/gbp.conf: update branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr

mutter (3.36.6-1) unstable; urgency=medium

  * Team upload
  * New upstream release
  * Update symbols file
  * d/control.in, d/rules: Enable Pipewire on Debian (but not Ubuntu).
Now that we have Pipewire 0.3, we can enable screencasting and remote
desktop support again.

mutter (3.36.5-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Screencast fixes and improvements
- Fix glitches when subsurfaces extend outside the toplevel
- Improve background display in overview workspace switcher
- Fix wine copy & paste
- Plug memory leaks
  * Drop patches that were applied upstream

mutter (3.36.4-1) unstable; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop

 -- Marco Trevisan (Treviño)   Wed, 23 Sep 2020
22:03:53 +0200

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

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

Title:
  gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion
  failed: (META_IS_STAGE_X11 (impl))

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  GNOME Shell crashes in meta_x11_get_stage_window.

  [ Test case ]

  Perform touch events via touchpad or touchscreen, eventually the shell
  will crash.

  Errors can be monitored at:
   https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  ---

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 22:08:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: 
gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gn

[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2

---
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previous fixes, gbp has been a bad guy this time! (LP: #1896818)

mutter (3.36.6-1ubuntu0.20.04.1) focal; urgency=medium

  * Merge with debian, containing new stable release (LP: #1896332)
  * debian/patches:
- Refresh patches and drop applied ones
- Don't set the font-dpi on clutter-backend-x11 (LP: #1892440)
- Cherry-pick upstream night-switch fixes for 3.36 branch
- Cherry-pick upstream fixes for handling X11 devices removal
  (LP: #1558886)
  * xrandr-scaling: Don't update UI scale factor on xrandr-manager creation
(LP: #1892440)
  * debian/control: Revert pipewire version bumping
  * Remaining changes with debian:
- debian/control:
  + Update VCS flags to point to ubuntu salsa branch
- debian/gbp.conf: update branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr

mutter (3.36.6-1) unstable; urgency=medium

  * Team upload
  * New upstream release
  * Update symbols file
  * d/control.in, d/rules: Enable Pipewire on Debian (but not Ubuntu).
Now that we have Pipewire 0.3, we can enable screencasting and remote
desktop support again.

mutter (3.36.5-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Screencast fixes and improvements
- Fix glitches when subsurfaces extend outside the toplevel
- Improve background display in overview workspace switcher
- Fix wine copy & paste
- Plug memory leaks
  * Drop patches that were applied upstream

mutter (3.36.4-1) unstable; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop

 -- Marco Trevisan (Treviño)   Wed, 23 Sep 2020
22:03:53 +0200

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

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubunt

[Desktop-packages] [Bug 1896332] Re: SRU 3.36.6

This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2

---
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previous fixes, gbp has been a bad guy this time! (LP: #1896818)

mutter (3.36.6-1ubuntu0.20.04.1) focal; urgency=medium

  * Merge with debian, containing new stable release (LP: #1896332)
  * debian/patches:
- Refresh patches and drop applied ones
- Don't set the font-dpi on clutter-backend-x11 (LP: #1892440)
- Cherry-pick upstream night-switch fixes for 3.36 branch
- Cherry-pick upstream fixes for handling X11 devices removal
  (LP: #1558886)
  * xrandr-scaling: Don't update UI scale factor on xrandr-manager creation
(LP: #1892440)
  * debian/control: Revert pipewire version bumping
  * Remaining changes with debian:
- debian/control:
  + Update VCS flags to point to ubuntu salsa branch
- debian/gbp.conf: update branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr

mutter (3.36.6-1) unstable; urgency=medium

  * Team upload
  * New upstream release
  * Update symbols file
  * d/control.in, d/rules: Enable Pipewire on Debian (but not Ubuntu).
Now that we have Pipewire 0.3, we can enable screencasting and remote
desktop support again.

mutter (3.36.5-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Screencast fixes and improvements
- Fix glitches when subsurfaces extend outside the toplevel
- Improve background display in overview workspace switcher
- Fix wine copy & paste
- Plug memory leaks
  * Drop patches that were applied upstream

mutter (3.36.4-1) unstable; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop

 -- Marco Trevisan (Treviño)   Wed, 23 Sep 2020
22:03:53 +0200

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

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

Title:
  SRU 3.36.6

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

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.6

  [ 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 device management, desktop background
  image handling, screen-casting and night-switch.

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

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

[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)

This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2

---
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previous fixes, gbp has been a bad guy this time! (LP: #1896818)

mutter (3.36.6-1ubuntu0.20.04.1) focal; urgency=medium

  * Merge with debian, containing new stable release (LP: #1896332)
  * debian/patches:
- Refresh patches and drop applied ones
- Don't set the font-dpi on clutter-backend-x11 (LP: #1892440)
- Cherry-pick upstream night-switch fixes for 3.36 branch
- Cherry-pick upstream fixes for handling X11 devices removal
  (LP: #1558886)
  * xrandr-scaling: Don't update UI scale factor on xrandr-manager creation
(LP: #1892440)
  * debian/control: Revert pipewire version bumping
  * Remaining changes with debian:
- debian/control:
  + Update VCS flags to point to ubuntu salsa branch
- debian/gbp.conf: update branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr

mutter (3.36.6-1) unstable; urgency=medium

  * Team upload
  * New upstream release
  * Update symbols file
  * d/control.in, d/rules: Enable Pipewire on Debian (but not Ubuntu).
Now that we have Pipewire 0.3, we can enable screencasting and remote
desktop support again.

mutter (3.36.5-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Screencast fixes and improvements
- Fix glitches when subsurfaces extend outside the toplevel
- Improve background display in overview workspace switcher
- Fix wine copy & paste
- Plug memory leaks
  * Drop patches that were applied upstream

mutter (3.36.4-1) unstable; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop

 -- Marco Trevisan (Treviño)   Wed, 23 Sep 2020
22:03:53 +0200

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

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

Title:
  Gnome-shell crash after turn display off in mutter
  3.36.6-ubuntu0.20.04.1 (NVIDIA)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  In Ubuntu 20.04.1 [focal-proposed]:

  [ Impact ]
  GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1.
  With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), 
all works fine.

  [ Test case ]
  Steps to reproduce the error:
  1) Lock screen;
  2) Turn off the display;
  3) Turn on the display;

  And the Gnome Shell crash and show us a blank screen with the message:
  "Oh no! Something has gone wrong."

  [ Regression potential ]
  This very fix was already handled as part of bug #1889090 and we had no 
regression report,.

  However, one possible is that the screen size is not set properly for
  the session, or that panning is enabled.

  [ Workaround ]
  Downgrade the libmutter package temporarily.

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.6-1ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
  Uname: Linux 5.4.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 23 15:57:17 2020
  InstallationDate: Installed on 2020-08-15 (38 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffil

[Desktop-packages] [Bug 1857947] Re: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_s

This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2

---
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previous fixes, gbp has been a bad guy this time! (LP: #1896818)

mutter (3.36.6-1ubuntu0.20.04.1) focal; urgency=medium

  * Merge with debian, containing new stable release (LP: #1896332)
  * debian/patches:
- Refresh patches and drop applied ones
- Don't set the font-dpi on clutter-backend-x11 (LP: #1892440)
- Cherry-pick upstream night-switch fixes for 3.36 branch
- Cherry-pick upstream fixes for handling X11 devices removal
  (LP: #1558886)
  * xrandr-scaling: Don't update UI scale factor on xrandr-manager creation
(LP: #1892440)
  * debian/control: Revert pipewire version bumping
  * Remaining changes with debian:
- debian/control:
  + Update VCS flags to point to ubuntu salsa branch
- debian/gbp.conf: update branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr

mutter (3.36.6-1) unstable; urgency=medium

  * Team upload
  * New upstream release
  * Update symbols file
  * d/control.in, d/rules: Enable Pipewire on Debian (but not Ubuntu).
Now that we have Pipewire 0.3, we can enable screencasting and remote
desktop support again.

mutter (3.36.5-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Screencast fixes and improvements
- Fix glitches when subsurfaces extend outside the toplevel
- Improve background display in overview workspace switcher
- Fix wine copy & paste
- Plug memory leaks
  * Drop patches that were applied upstream

mutter (3.36.4-1) unstable; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop

 -- Marco Trevisan (Treviño)   Wed, 23 Sep 2020
22:03:53 +0200

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

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

Title:
  gnome-shell crashed with SIGSEGV in get_top_visible_window_actor()
  from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack()
  from stack_tracker_sync_stack_later() from call_later_func()

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  GNOME Shell crashes

  [ Test case ]

  Four-finger gesture seems to trigger it, in any case it can be monitored via 
   - https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.1+git20191024-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 
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/mutter/+bug/1857947/+subscriptions

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

[Desktop-packages] [Bug 1887998] Re: Update to 3.36.4 and SRU it

This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2

---
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previous fixes, gbp has been a bad guy this time! (LP: #1896818)

mutter (3.36.6-1ubuntu0.20.04.1) focal; urgency=medium

  * Merge with debian, containing new stable release (LP: #1896332)
  * debian/patches:
- Refresh patches and drop applied ones
- Don't set the font-dpi on clutter-backend-x11 (LP: #1892440)
- Cherry-pick upstream night-switch fixes for 3.36 branch
- Cherry-pick upstream fixes for handling X11 devices removal
  (LP: #1558886)
  * xrandr-scaling: Don't update UI scale factor on xrandr-manager creation
(LP: #1892440)
  * debian/control: Revert pipewire version bumping
  * Remaining changes with debian:
- debian/control:
  + Update VCS flags to point to ubuntu salsa branch
- debian/gbp.conf: update branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr

mutter (3.36.6-1) unstable; urgency=medium

  * Team upload
  * New upstream release
  * Update symbols file
  * d/control.in, d/rules: Enable Pipewire on Debian (but not Ubuntu).
Now that we have Pipewire 0.3, we can enable screencasting and remote
desktop support again.

mutter (3.36.5-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Screencast fixes and improvements
- Fix glitches when subsurfaces extend outside the toplevel
- Improve background display in overview workspace switcher
- Fix wine copy & paste
- Plug memory leaks
  * Drop patches that were applied upstream

mutter (3.36.4-1) unstable; urgency=medium

  * New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
  * d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-100.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop

 -- Marco Trevisan (Treviño)   Wed, 23 Sep 2020
22:03:53 +0200

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

-- 
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:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

See #179 ;-)

-- 
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 Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  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 Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3

[Desktop-packages] [Bug 1880785] Re: Cannot enable 'Lock screen on suspend'

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

Title:
  Cannot enable 'Lock screen on suspend'

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I am trying to make my laptop lock the screen upon unsuspending. I
  have made sure that the setting is enabled in 'Settings > Privacy >
  Screen lock > Lock screen on suspend', but my laptop opens without a
  lock screen when I open it or press a key. This only started since
  upgrading to Ubuntu 20.04. Previously, I would have a locked screen
  and be prompted for a password upon unsuspending.

  $ gsettings get org.gnome.desktop.screensaver ubuntu-lock-on-suspend
  true

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.36.2-1ubuntu1~20.04.1
Candidate: 3.36.2-1ubuntu1~20.04.1
Version table:
   *** 3.36.2-1ubuntu1~20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.36.1-5ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  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: Tue May 26 21:28:39 2020
  DisplayManager: lightdm
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-07-16 (680 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-23 (33 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-10-06 Thread Piotr Tomaszewski

Won't build since there is no 0303-pinctrl-amd2.patch in repo.

-- 
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 Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  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 Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  Proble

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Use this PKGBUILD

** Attachment added: "PKGBUILD for 5.8.13"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5418466/+files/PKGBUILD

-- 
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 Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  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_Legi

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

@Piotr Tomaszewski (nfm886)

The patch is not included in the kernel, as other touchpads will no
longer work.

You can use the attached patch and build your own kernel. It works with
ELAN-Touchpad MSFT0001:00 04F3:3140


** Patch added: "Patch for Manjaro Kernel 5.8.13"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5418465/+files/0303-pinctrl-amd2.patch

-- 
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 Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  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:p

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-10-06 Thread Azizkhan

Can anyone provide debian packages for compiled kernel 5.8.13 with
patch?

-- 
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 Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  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 Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --

[Desktop-packages] [Bug 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

2020-10-06 Thread Decio Della Fortuna

Is there any news about it? Ubuntu 20.04.1, kernel 5.4.0-48, Nvidia CUDA
driver 455.23.05, ThinkPad P50, latest BIOS/firmware 1.62, with VGA
configured in discrete mode, integrated touchpad do not work.

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:36:18 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2019-04-26 (0 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:b596 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) 
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EQS0PQ00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash 
synaptic_intertouch=0 vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET83W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS0PQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS0PQ00
  dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/xserver-xorg-input-libinput/+bug/1826597/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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-10-06 Thread Piotr Tomaszewski

Hey @Helmut Stult (helmut-stult) 
I compiled kernel from there: https://gitlab.manjaro.org/packages/core/linux58
but unfortunately touchpad does not works. 

Linux Lenovo 5.8.13-4-MANJARO #1 SMP PREEMPT Tue Oct 6 19:05:24 CEST
2020 x86_64 GNU/Linux

↳ MSFT0001:00 04F3:3140 Touchpadid=17   [slave  pointer
(2)]

is something what i should do more to make it works?

-- 
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 Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  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:

[Desktop-packages] [Bug 1894593] Re: Fractional scaling switch doesn't work in Wayland sessions

2020-10-06 Thread Kai Mast

Thanks Daniel. I was not aware this switch isn't available upstream.

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

Title:
  Fractional scaling switch doesn't work in Wayland sessions

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

Bug description:
  Hitting the “fractional scaling” toggle in the “Screen Display” tab in
  gnome-control-centre page doesn't work - although the toggle changes
  to the “enabled” state there's no visible effect, and if I switch to a
  different page (or close g-c-c) and then switch back (or reopen g-c-c)
  then the toggle is back in the disabled state.

  Running from the command line, I see;
  (gnome-control-center:171131): display-cc-panel-WARNING **: 13:34:19.407: no 
sunset data, using 16.00

  (gnome-control-center:171131): display-cc-panel-WARNING **:
  13:34:19.407: no sunrise data, using 8.00

  (gnome-control-center:171131): display-cc-panel-CRITICAL **:
  13:34:21.972: file ../panels/display/cc-display-config.c: line 452
  (get_fractional_scaling_key): should not be reached

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.37.90-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0+bcachefs.git20200701.7e04f345-1-generic 
5.8.4
  Uname: Linux 5.8.0+bcachefs.git20200701.7e04f345-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  7 13:34:44 2020
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (76 days ago)

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

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

[Desktop-packages] [Bug 1898754] [NEW] Non-existent home directory entry in /etc/passwd

2020-10-06 Thread Patrick Goetz

Public bug reported:

This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two distros
I've checked.

This is likely a packaging error.  The cups-pk-helper user appears in
/etc/passwd as:

cups-pk-helper:x:111:118:user for cups-pk-helper service,,,:/home/cups-
pk-helper:/usr/sbin/nologin

Of course there is no directory /home/cups-pk-helper.  This appears
innocuous, but can cause problems for users that have, say autofs
mounted home directories.  To cite one example, the python virtual
environment anaconda trolls through /etc/passwd looking for environments
in /home/USER.  This triggers autofs to try and mount /home/cups-pk--
helper, which doesn't exist, causing the automounter to hang under
certain circumstances.  In, for example, Arch linux, this entry would
appear as the considerably more sensible

cups-pk-helper:x:111:118:user for cups-pk-helper
service,,,:/:/usr/sbin/nologin

While an edge case in the current compute environment, this is also a
very easy fix.  Don't reference non-existent directories. Many Ubuntu
packages make this packaging error when creating local users with non-
existent home directories; e.g. syslog.

** Affects: cups-pk-helper (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two distros
  I've checked.
  
  This is likely a packaging error.  The cups-pk-helper user appears in
  /etc/passwd as:
  
  cups-pk-helper:x:111:118:user for cups-pk-helper service,,,:/home/cups-
  pk-helper:/usr/sbin/nologin
  
  Of course there is no directory /home/cups-pk-helper.  This appears
  innocuous, but can cause problems for users that have, say autofs
  mounted home directories.  To cite one example, the python virtual
- environment anaconda trolls through /etc/passw looking for environments
+ environment anaconda trolls through /etc/passwd looking for environments
  in /home/USER.  This triggers autofs to try and mount /home/cups-pk--
- helper, which doesn't existing, causing the automounter to hang under
+ helper, which doesn't exist, causing the automounter to hang under
  certain circumstances.  In, for example, Arch linux, this entry would
  appear as the considerably more sensible
  
  cups-pk-helper:x:111:118:user for cups-pk-helper
  service,,,:/:/usr/sbin/nologin
  
  While an edge case in the current compute environment, this is also a
  very easy fix.  Don't reference non-existent directories. Many Ubuntu
  packages make this packaging error when creating local users with non-
  existent home directories; e.g. syslog.

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

Title:
  Non-existent home directory entry in /etc/passwd

Status in cups-pk-helper package in Ubuntu:
  New

Bug description:
  This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two
  distros I've checked.

  This is likely a packaging error.  The cups-pk-helper user appears in
  /etc/passwd as:

  cups-pk-helper:x:111:118:user for cups-pk-helper service,,,:/home
  /cups-pk-helper:/usr/sbin/nologin

  Of course there is no directory /home/cups-pk-helper.  This appears
  innocuous, but can cause problems for users that have, say autofs
  mounted home directories.  To cite one example, the python virtual
  environment anaconda trolls through /etc/passwd looking for
  environments in /home/USER.  This triggers autofs to try and mount
  /home/cups-pk--helper, which doesn't exist, causing the automounter to
  hang under certain circumstances.  In, for example, Arch linux, this
  entry would appear as the considerably more sensible

  cups-pk-helper:x:111:118:user for cups-pk-helper
  service,,,:/:/usr/sbin/nologin

  While an edge case in the current compute environment, this is also a
  very easy fix.  Don't reference non-existent directories. Many Ubuntu
  packages make this packaging error when creating local users with non-
  existent home directories; e.g. syslog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-pk-helper/+bug/1898754/+subscriptions

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

[Desktop-packages] [Bug 1897988] Re: GitKraken Flatpak doesn't display Icon in task switcher

2020-10-06 Thread Sai Vinoba

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

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

Title:
  GitKraken Flatpak doesn't display Icon in task switcher

Status in Ubuntu MATE:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Confirmed

Bug description:
  The GitKraken or any other flatpak doesn't display the icon on top of
  the window in the task switcher like other applications. I have
  attached a screenshot. It's the same for the bottom task bar too.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-48-generic 5.4.0-48.52
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  phillipsj   1317 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 20:33:37 2020
  InstallationDate: Installed on 2020-09-30 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 138a:0017 Validity Sensors, Inc. VFS 5011 fingerprint 
sensor
   Bus 001 Device 004: ID 04f2:b52c Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 002: ID 1199:9079 Sierra Wireless, Inc. Sierra Wireless 
EM7455 Qualcomm Snapdragon X7 LTE-A
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20F6006FUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=5a1e3d3b-2e79-426e-9641-1447dcd64341 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-48-generic N/A
   linux-backports-modules-5.4.0-48-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R02ET71W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F6006FUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:svnLENOVO:pn20F6006FUS:pvrThinkPadX260:rvnLENOVO:rn20F6006FUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X260
  dmi.product.name: 20F6006FUS
  dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260
  dmi.product.version: ThinkPad X260
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1898747] [NEW] [HP Pavilion Notebook, Nvidia GPU 80 HDMI/DP, Digital Out, HDMI] No sound at all on hdmi audio output

2020-10-06 Thread Lucas Arroyo Blanco

Public bug reported:

Recently I reinstalled ubuntu on my laptop and this time I found that
when I connect the laptop to the tv with the hdmi I manage to get the
video working but with no sound, it reproduces from the laptop speakers.

On pulseaudio volume control the digital stereo hdmi output appears as
unplugged and unavailable.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lucas  1634 F pulseaudio
 /dev/snd/controlC0:  lucas  1634 F pulseaudio
 /dev/snd/pcmC0D0c:   lucas  1634 F...m pulseaudio
 /dev/snd/pcmC0D0p:   lucas  1634 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  6 17:29:42 2020
InstallationDate: Installed on 2020-09-29 (7 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lucas  1634 F pulseaudio
 /dev/snd/controlC0:  lucas  1634 F pulseaudio
 /dev/snd/pcmC0D0c:   lucas  1634 F...m pulseaudio
 /dev/snd/pcmC0D0p:   lucas  1634 F...m pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [HP Pavilion Notebook, Nvidia GPU 80 HDMI/DP, Digital Out, HDMI] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 84F7
dmi.board.vendor: HP
dmi.board.version: 07.10
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.26:bd12/13/2019:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn84F7:rvr07.10:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Notebook
dmi.product.sku: 4AR14EA#ABE
dmi.sys.vendor: HP

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1898747

Title:
  [HP Pavilion Notebook, Nvidia GPU 80 HDMI/DP, Digital Out, HDMI] No
  sound at all on hdmi audio output

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Recently I reinstalled ubuntu on my laptop and this time I found that
  when I connect the laptop to the tv with the hdmi I manage to get the
  video working but with no sound, it reproduces from the laptop
  speakers.

  On pulseaudio volume control the digital stereo hdmi output appears as
  unplugged and unavailable.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lucas  1634 F pulseaudio
   /dev/snd/controlC0:  lucas  1634 F pulseaudio
   /dev/snd/pcmC0D0c:   lucas  1634 F...m pulseaudio
   /dev/snd/pcmC0D0p:   lucas  1634 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  6 17:29:42 2020
  InstallationDate: Installed on 2020-09-29 (7 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lucas  1634 F pulseaudio
   /dev/snd/controlC0:  lucas  1634 F pulseaudio
   /dev/snd/pcmC0D0c:   lucas  1634 F...m pulseaudio
   /dev/snd/pcmC0D0p:   lucas  1634 F...m pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [HP Pavilion Notebook, Nvidia GPU 80 HDMI/DP, Digital Out, HDMI] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.26
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 84F7
  dmi.board.vendor: HP
  dmi.board.version: 07.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.26:bd12/13/2019:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn84F7:rvr07.10:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5

[Desktop-packages] [Bug 1898745] [NEW] Login screen language reset after user ends session

2020-10-06 Thread veribaka

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
Focal Fossa 20.04.1

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in
3.36.3-0ubuntu0.20.04.1

3) What you expected to happen
When selecting a layout on login screen (en), the setting would persist.

4) What happened instead
The setting was reset to default (de)


Steps to reproduce:
1. Install device with Ubuntu Focal Fossa

2. Perform first login

3. Add German language support

4. Add German keyboard layout

5. Logout

6. Change keyboard layout to German (de)

7. Login

8. Logout

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


** Tags: focal

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

Title:
  Login screen language reset after user ends session

Status in gdm3 package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Focal Fossa 20.04.1

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in
  3.36.3-0ubuntu0.20.04.1

  3) What you expected to happen
  When selecting a layout on login screen (en), the setting would persist.

  4) What happened instead
  The setting was reset to default (de)

  
  Steps to reproduce:
  1. Install device with Ubuntu Focal Fossa

  2. Perform first login

  3. Add German language support

  4. Add German keyboard layout

  5. Logout

  6. Change keyboard layout to German (de)

  7. Login

  8. Logout

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

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

[Desktop-packages] [Bug 1872176] Re: [MS-7B38, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] fails after a while

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [MS-7B38, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] fails after a
  while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  When I'm using certain applications, mostly games, the sound starts
  breaking randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rohan  2393 F pulseaudio
   /dev/snd/pcmC0D7p:   rohan  2393 F...m pulseaudio
   /dev/snd/controlC1:  rohan  2393 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 14:17:58 2020
  InstallationDate: Installed on 2018-04-19 (722 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulseAudioLog:
   Apr 11 14:04:57 rohan-work dbus-daemon[884]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.32' (uid=126 pid=1920 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
   Apr 11 14:04:58 rohan-work dbus-daemon[884]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.37' (uid=126 pid=1920 comm="/usr/bin/pulseaudio --daemonize=no " 
label="unconfined")
   Apr 11 14:05:05 rohan-work systemd[1913]: pulseaudio.service: Succeeded.
   Apr 11 14:05:15 rohan-work systemd[1913]: pulseaudio.socket: Succeeded.
  Symptom_Type: Sound works for a while, then breaks
  Title: [MS-7B38, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] fails after a while
  UpgradeStatus: Upgraded to focal on 2020-04-02 (8 days ago)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.GR
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A320M PRO-VD PLUS (MS-7B38)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.GR:bd12/02/2019:svnMicro-StarInternationalCo.,Ltd:pnMS-7B38:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnA320MPRO-VDPLUS(MS-7B38):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B38
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd

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

-- 
Mailing list: https://launchpad.net/~desktop-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

@Coiby Xu (coiby)

#171 works for under Manjaro Linux and Kernel 5.8.13 too.

https://linux-hardware.org/?probe=7b7c4086f5

-- 
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 Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  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: Leno

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-10-06 Thread PD

@Azizkhan
check the patch file and your kernel file if the content for each line is 
consistent. If it is, you could copy patch file to kernel folder and run 
command "patch -p1 < patchfile"

@wangjun (biggerchina), @Coiby Xu (coiby)
Could you please summarize what you tested and did for patch? I am completely 
lost. :D

-- 
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 Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  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:rvrSDK0J407

[Desktop-packages] [Bug 1897962] Re: Out of Memory Error with Brother DCP-J7720W

Deleting the focal line for now, it can be fixed in that serie but to be
nominated it needs an assigned owner and it doesn't have one for nom

** No longer affects: sane-backends (Ubuntu Focal)

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

Title:
  Out of Memory Error with Brother DCP-J7720W

Status in sane-backends package in Ubuntu:
  Fix Released

Bug description:
  Installed XSane from the repository but when I scan the viewer screen is 
blank and if I try to save I get "Error during save: out of memory" 
  I believe that escl driver in 20.04 sane-backends is a problem and it is 
related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962539
  sane-backends 1.0.31 should be considered  for  focal-backports   and that if 
possible, escl driver could be individually SRU (Stable release update) in 
focal-updates.

  ppa:sane-project/sane-git  fixes the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1897962/+subscriptions

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

[Desktop-packages] [Bug 1892643] Re: [SRU] Update libgweather to 3.36.1

** Changed in: libgweather (Ubuntu Focal)
 Assignee: (unassigned) => Didier Roche (didrocks)

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

Title:
  [SRU] Update libgweather to 3.36.1

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Focal:
  New
Status in libgweather package in Debian:
  Unknown

Bug description:
  [Impact]

  libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36.

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  This version works around the unavailability of the NOAA weather
  services by using very short-term forecasts as current weather
  conditions.

  Sometimes the current weather is not available because the NOAA
  weather servers aren't working correctly. Version 3.36.1 fixes the
  unavailability of current temperature in some locations.

  
  [Test case]

  Make sure that gnome-weather is still working properly and the weather
  in gnome-shell is shown when gnome-weather is installed.

  
  [Regression potential]

  The regression potential is low since the changes in version 3.36.1
  are small.

  
  [Other]

  libgweather 3.36.1 has been successfully built as a no-change backport
  from Groovy to Focal in my PPA and runs fine:

  
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather&field.status_filter=published&field.series_filter=

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 23 19:05:21 2020
  InstallationDate: Installed on 2020-04-26 (119 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1880405] Re: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Tags removed: rls-ff-incoming

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

Title:
  High CPU and journal flooded with: JS ERROR: TypeError: null has no
  properties
  _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9

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

Bug description:
  O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I 
did face these problems. The sometimes I have to wait 10 seconds to see if a 
window reacts or not. It is hard to use. 
Installiert:   3.36.1-5ubuntu2
Installationskandidat: 3.36.2-1ubuntu1~20.04.1
Versionstabelle:
   3.36.2-1ubuntu1~20.04.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   *** 3.36.1-5ubuntu2 100
  100 /var/lib/dpkg/status
   3.36.1-5ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Sun May 24 15:43:34 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-05 (109 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago)

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

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

[Desktop-packages] [Bug 1870794] Re: Update for Unicode 13

untargetting for focal for now since there is no assignee, would still
be nice to SRU but desktop decided to not accepted as a active
nomination for now

** No longer affects: fonts-noto-color-emoji (Ubuntu Focal)

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

Title:
  Update for Unicode 13

Status in fonts-noto-color-emoji package in Ubuntu:
  Fix Released

Bug description:
  The current version is missing some emojis which are already available
  upstream. I didn't check them all but it seems they are v13 emojis.

  You can see the missing ones as tofu from here:
  https://unicode.org/emoji/charts/full-emoji-list.html

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: fonts-noto-color-emoji 0~20191119-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr  4 17:25:41 2020
  Dependencies:
   
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: fonts-noto-color-emoji
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1870794/+subscriptions

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

[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected

Daniel, could you add this one to your backlog?

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

** Also affects: plymouth (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Also affects: gdm3 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** No longer affects: mutter (Ubuntu)

** No longer affects: mutter (Ubuntu Focal)

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

Title:
  booting with splash hangs when external monitors are connected

Status in Plymouth:
  Unknown
Status in gdm3 package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Triaged
Status in gdm3 source package in Focal:
  New
Status in plymouth source package in Focal:
  New

Bug description:
  I think this is a problem with the splash boot loader. This problem is
  not reproduced if using nosplash.

  I have installed 20.04 to this laptop. Thinkpad T480, i7, intel
  graphics.

  Clean install of 20.04 beta, not an upgrade.
  When booting from the install, the greeter screen is never reached if 
external monitors are connected at startup.
  I get the spinning ubuntu logo, and nothing more. I can not change to virtual 
terminals. The fsck step does not commence.

  In recovery mood, I can log in.

  With no external monitors attached, it works.

  I am used to having such problems with Nvidia graphics is involved,
  but this is not the case on this laptop. It has been happily running
  18.04.

  External displays are recognised if they are connected after login.

  Also, when I edit /etc/default/grub so that it reads
  GRUB_CMDLINE_LINUX_DEFAULT=""
  (that is, splash disabled)
  it works fine with two external monitors attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 13:58:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2020-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 20L5S00F00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/myvg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5S00F00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5S00F00
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+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/plymouth/+bug/1872159/+subscriptions

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

[Desktop-packages] [Bug 1839380] Re: Nautilus freezes when restoring files and a copy already exists

This bug was fixed in the package nautilus - 1:3.38.1-1ubuntu1

---
nautilus (1:3.38.1-1ubuntu1) groovy; urgency=medium

  * New upstream version
- don't block to restore from trash (lp: #1839380)
  * debian/source_nautilus.py:
- updated the apport script to use the multiarch directory, install
  it in the nautilus binary that is arch any (lp: #1723822)
  * Resynchronizr on Debian:
- debian/control.in:
  + Build-Depend on libunity-dev
  + lower gnome-sushi Recommends to a Suggests
- debian/changelog, debian/nautilus.maintscript: set epoch number
  (which was added by error)
- debian/source_nautilus.py,
  debian/nautilus-data.install:
  + Apport hook to list versions of files in /usr/lib/nautilus and
reassign the crashes when they are not due to nautilus code directly
- debian/rules:
  + Build Unity support
- 0001-Respect-gtk-dialogs-use-header-for-all-dialogs.patch
  + Use a normal titlebar if the desktop environment wants it
- 04_suppress_umount_in_ltsp.patch:
  + Don't list unmount and eject actions on LTSP clients
- 12_unity_launcher_support.patch:
  + unity launcher integration (list bookmarks in the context menu,
display a bar on the icon during copies)
- 18_unity_icon_color.patch:
  + specify a background color for the unity launcher icon
- 19_unity_open_location_xid.patch:
  + Add a new dbus property to store the lists of opened locations
referenced by their parent nautilus window XID.
- 20_add_timestamp_to_operations.patch:
  + Add *WithTimestamp dbus methods for file operations that
might trigger a dialog, that should be presented with time.
- appstream-compulsory.patch:
  + Set nautilus as unremovable in GNOME Software
- nautilusgtkplacesview-show-error-if-volume-is-not-mo.patch:
  + show error if volume is not mounted, see LP #1764779
- ubuntu/shell-search-provider-implement-XUbuntuCancel-to-request-.patch:
  + implement XUbuntuCancel to request search cancellation
- ubuntu_backspace_behaviour.patch:
  + restore backspace behaviour to go back
- ubuntu_infobars_color.patch:
  + set infobar type to "other" rather than "question" to avoid blue
cluebars

 -- Sebastien Bacher   Mon, 05 Oct 2020 11:37:10
+0200

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

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

Title:
  Nautilus freezes when restoring files and a copy already exists

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  I have trashed the hidden file using nautilus to the trash bin, be it
  the hidden configuration file for XScreenSaver that is compiled from
  source, and it regenerated the hidden file in the same location that I
  have deleted the old copy in.

  I attempted to restore the file, but because the file with the same
  name is originated on the same location, Nautilus freezes. It should
  give me the "Replace file with newer version" dialog so I can decide
  if I want to replace the old file with the new one, or if I want to
  rename the trashed hidden file to another name. It shouldn't freeze.

  Here's the clearer example. Suppose that...

  1. I created a file named "test.txt" on "/home/eofla",
  2. I put it to the trash bin,
  3. I repeated Step 1, and
  4. I attempted to restore the same file that was on the trash.
  5. Nautilus freezes.

  Version of Ubuntu:

  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  Version of Nautilus:

  nautilus:
    Installed: 1:3.32.1-1ubuntu1
    Candidate: 1:3.32.1-1ubuntu1
    Version table:
   *** 1:3.32.1-1ubuntu1 500
  500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  Debug output with "G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus":

  Nautilus-Share-Message: 23:01:44.608: Called "net usershare info" but
  it failed: Failed to execute child process “net” (No such file or
  directory)

  Debug output using "gdb nautilus" with exported environment variables
  of G_DEBUG="all" NAUTILUS_DEBUG="All" (More useful, with stack trace):
  https://paste.ubuntu.com/p/ChpBrDsTtd/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.32.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  7 13:43:40 2019
  GsettingsChanges:

  InstallationDate: Installed on 2019-07-21 (16 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this b

[Desktop-packages] [Bug 1723822] Re: uncaught TypeError triggers ValueError

This bug was fixed in the package nautilus - 1:3.38.1-1ubuntu1

---
nautilus (1:3.38.1-1ubuntu1) groovy; urgency=medium

  * New upstream version
- don't block to restore from trash (lp: #1839380)
  * debian/source_nautilus.py:
- updated the apport script to use the multiarch directory, install
  it in the nautilus binary that is arch any (lp: #1723822)
  * Resynchronizr on Debian:
- debian/control.in:
  + Build-Depend on libunity-dev
  + lower gnome-sushi Recommends to a Suggests
- debian/changelog, debian/nautilus.maintscript: set epoch number
  (which was added by error)
- debian/source_nautilus.py,
  debian/nautilus-data.install:
  + Apport hook to list versions of files in /usr/lib/nautilus and
reassign the crashes when they are not due to nautilus code directly
- debian/rules:
  + Build Unity support
- 0001-Respect-gtk-dialogs-use-header-for-all-dialogs.patch
  + Use a normal titlebar if the desktop environment wants it
- 04_suppress_umount_in_ltsp.patch:
  + Don't list unmount and eject actions on LTSP clients
- 12_unity_launcher_support.patch:
  + unity launcher integration (list bookmarks in the context menu,
display a bar on the icon during copies)
- 18_unity_icon_color.patch:
  + specify a background color for the unity launcher icon
- 19_unity_open_location_xid.patch:
  + Add a new dbus property to store the lists of opened locations
referenced by their parent nautilus window XID.
- 20_add_timestamp_to_operations.patch:
  + Add *WithTimestamp dbus methods for file operations that
might trigger a dialog, that should be presented with time.
- appstream-compulsory.patch:
  + Set nautilus as unremovable in GNOME Software
- nautilusgtkplacesview-show-error-if-volume-is-not-mo.patch:
  + show error if volume is not mounted, see LP #1764779
- ubuntu/shell-search-provider-implement-XUbuntuCancel-to-request-.patch:
  + implement XUbuntuCancel to request search cancellation
- ubuntu_backspace_behaviour.patch:
  + restore backspace behaviour to go back
- ubuntu_infobars_color.patch:
  + set infobar type to "other" rather than "question" to avoid blue
cluebars

 -- Sebastien Bacher   Mon, 05 Oct 2020 11:37:10
+0200

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

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

Title:
  uncaught TypeError triggers ValueError

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  $ ubuntu-bug nautilus
  ERROR: hook /usr/share/apport/package-hooks/source_nautilus.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
  TypeError: add_info() takes 1 positional argument but 2 were given

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 203, in 
_run_hook
  symb['add_info'](report)
File "/usr/share/apport/package-hooks/source_nautilus.py", line 23, in 
add_info
  report["usr_lib_nautilus"] = package_versions(*sorted(plugin_packages))
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 785, in 
package_versions
  map(max, [map(len, t) for t in zip(*versions)])
  ValueError: not enough values to unpack (expected 2, got 0)
  This tool has been deprecated, use 'gio open' instead.
  See 'gio help open' for more info.

  $ Created new window in existing browser session.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashReports:
   640:121:119:20593327:2017-10-14 08:49:43.994080376 -0700:2017-10-14 
08:49:24.682136558 -0700:/var/crash/_usr_bin_gnome-shell.121.crash
   640:0:119:712257:2017-10-13 22:55:49.843941428 -0700:2017-10-13 
22:55:48.723911385 -0700:/var/crash/_usr_lib_udisks2_udisksd.0.crash
   640:1000:119:432238:2017-10-14 07:48:01.498643348 -0700:2017-10-14 
07:48:00.714643372 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.crash
   664:1000:119:0:2017-10-13 19:55:40.447393054 -0700:2017-10-13 
19:55:40.447393054 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.upload
   600:112:119:0:2017-10-13 19:55:42.247460153 -0700:2017-10-13 
19:55:42.247460153 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.uploaded
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 17:52:08 2017
  InstallationDate: Installed on 2017-10-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd

[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No sound at all

2020-10-06 Thread Bug Watch Updater

** Changed in: alsa-driver
   Status: Unknown => Fix Released

** Changed in: alsa-driver
   Importance: Unknown => Medium

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No sound at all

Status in ALSA driver:
  Fix Released
Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Desktop-packages] [Bug 1685754] Re: 'systemd --user' unduly forces umask=0022

2020-10-06 Thread Etienne URBAH

REGRESSION:  With systemd 246.6-1ubuntu1 from Ubuntu 20.10 Beta (Groovy
Gorilla), the issue had reappeared

** Tags added: groovy

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

Title:
  'systemd --user' unduly forces umask=0022

Status in gedit:
  Invalid
Status in gnome-session:
  Invalid
Status in GNOME Terminal:
  Confirmed
Status in Nautilus:
  Invalid
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Bionic:
  Invalid
Status in gnome-terminal source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  In order to set the default umask of my users to 027 or 007, I
  followed the instructions provided in 'man pam_umask' :

  In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
  'umask=007' (for myself).

  Then, MOST graphical applications systematically run with the correct
  umask.

  In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
  it systematically displays 0007.

  But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
  it systematically displays 0022.

  That is BAD, and is a security issue.

  
  Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
  UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
  if  [ "$UMASK" ];  then
umask  "${UMASK#$USER:*,umask=}"
  fi

  
  In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.

  Thank you in advance for a quick correction.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 24 08:36:58 2017
  InstallationDate: Installed on 2017-03-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1898541] Re: [FFe] Update to 3.38.0

2020-10-06 Thread Gunnar Hjalmarsson

Release team input on IRC:

https://irclogs.ubuntu.com/2020/10/06/%23ubuntu-desktop.html#t11:39

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

Title:
  [FFe] Update to 3.38.0

Status in gnome-software package in Ubuntu:
  New

Bug description:
  It would be good if we could ship gnome-software 3.38.0 with groovy.

  These are the 3.37.92 changes:

  Add sysprof support for profiling jobs
  Add webflow and basic auth support to flatpak plugin
  Coalesce refresh operations where possible
  Correctly mark layered rpm-ostree local packages as removable
  Fix flatpak bundle installation
  Handle invalid snap auth data
  Improve flatpak progress reporting for transactions
  Improve the heuristic for detecting old-style AppStream override files
  Many performance improvements in many areas of the code
  Only delete the firmware archive if we downloaded it to the cache
  Show a pulsing progress bar if progress is unknown
  Support loading appstream files from custom install prefix
  Use the runtime fwupd version for the user agent

  3.38.0 is a pure translation update.

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

-- 
Mailing list: https://launchpad.net/~desktop-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()

2020-10-06 Thread Treviño

Daniel,

Detailed ways to reproduce the crash are explained upstream at
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/823#note_866367

The crash was happening easily by using the above script, if it doesn't anymore 
than it's a verification.
I also verified this in my setup, but preferred to have some other reports.

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

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

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Using Ubuntu 16.04 and 20.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

  

  [  Test case ]

  Run xinput and figure device IDs for your mouse.
  Run this evil script with 9 changed (be sure to change both) to your id:

for ((;;)) do xinput disable 9; echo Disabled; xinput enable 9; echo
  Enabled; done

  While the script runs, open some context menu in some program. It may require 
a few clicks due to evil script enabling/disabling mouse.
  This will sometimes crash GTK programs due to a mirror bug in GTK.

  GNOME Shell should not crash

  [ Regression potential ]

  Devices might be not be properly recognized when plugged and unplugged

  
  

  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 VMASignal: 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/mutter/+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 1896577] Re: FFE: new upstream release 20.2 and migrate to llvm 11

2020-10-06 Thread Timo Aaltonen

This bug was fixed in the package mesa - 20.2.0-1

---
mesa (20.2.0-1) experimental; urgency=medium

  * New upstream release.
  * control: Add libclang-cpp11-dev to build-depends. (Closes: #954849)

 -- Timo Aaltonen   Tue, 29 Sep 2020 11:07:13 +0300

mesa (20.2.0~rc4-2) experimental; urgency=medium

  * Migrate to llvm/clang-11.
  * path_max.diff: Updated. (Closes: #969040)

 -- Timo Aaltonen   Thu, 17 Sep 2020 12:07:08 +0300

mesa (20.2.0~rc4-1) experimental; urgency=medium

  * New upstream prerelease.
  * rules: Move radv rule up to fix build on non-intel archs.

 -- Timo Aaltonen   Fri, 04 Sep 2020 19:32:58 +0300

mesa (20.2.0~rc2-1) experimental; urgency=medium

  * New upstream release candidate.
  * rules: Get rid of trailing commas in *_DRIVERS options.
  * control: Bump libglvnd build-dep.
  * Update mesa-common-dev.docs.

 -- Timo Aaltonen   Fri, 14 Aug 2020 18:30:42 +0300

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

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

Title:
  FFE: new upstream release 20.2 and migrate to llvm 11

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Mesa 20.2.0 was released on Sep 28th a month late, but we still want
  it in 20.10. It's been in debian experimental since rc1. The packaging
  in debian also migrates to use llvm 11.

  The risks involve graphical issues or even crashes when running more
  intense OpenGL/Vulkan apps like games. Running a desktop is a simple
  use-case and should work fine across the board. Upstream gitlab has a
  fairly extensive CI for various drivers, while Intel tests on their
  own CI. This means that any showstoppers should be shaken out already.

  We will be able to pull maybe two point-releases before groovy is
  frozen, and then push more as an SRU.

  I've tested 20.2.0 on Intel and AMD (RX 5700) and the latter too with
  some games, all good.

  packages for groovy are available on ppa:canonical-x/x-staging

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

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

[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

2020-10-06 Thread Emmett Keyser

A bug from more than 4 years ago is blocking this bug reported less than
2 months ago? Wow. Fascinating.

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

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

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

[Desktop-packages] [Bug 1898541] Re: [FFe] Update to 3.38.0

2020-10-06 Thread fossfreedom

On behalf of UB - no objections here +1.  Many thanks for doing this.
much appreciated.

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

Title:
  [FFe] Update to 3.38.0

Status in gnome-software package in Ubuntu:
  New

Bug description:
  It would be good if we could ship gnome-software 3.38.0 with groovy.

  These are the 3.37.92 changes:

  Add sysprof support for profiling jobs
  Add webflow and basic auth support to flatpak plugin
  Coalesce refresh operations where possible
  Correctly mark layered rpm-ostree local packages as removable
  Fix flatpak bundle installation
  Handle invalid snap auth data
  Improve flatpak progress reporting for transactions
  Improve the heuristic for detecting old-style AppStream override files
  Many performance improvements in many areas of the code
  Only delete the firmware archive if we downloaded it to the cache
  Show a pulsing progress bar if progress is unknown
  Support loading appstream files from custom install prefix
  Use the runtime fwupd version for the user agent

  3.38.0 is a pure translation update.

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

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

[Desktop-packages] [Bug 1898541] Re: [FFe] Update to 3.38.0

2020-10-06 Thread Gunnar Hjalmarsson

@David, @Sean: Since this package is seeded in Ubuntu Budgie and
Xubuntu, do you have any objections?

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

Title:
  [FFe] Update to 3.38.0

Status in gnome-software package in Ubuntu:
  New

Bug description:
  It would be good if we could ship gnome-software 3.38.0 with groovy.

  These are the 3.37.92 changes:

  Add sysprof support for profiling jobs
  Add webflow and basic auth support to flatpak plugin
  Coalesce refresh operations where possible
  Correctly mark layered rpm-ostree local packages as removable
  Fix flatpak bundle installation
  Handle invalid snap auth data
  Improve flatpak progress reporting for transactions
  Improve the heuristic for detecting old-style AppStream override files
  Many performance improvements in many areas of the code
  Only delete the firmware archive if we downloaded it to the cache
  Show a pulsing progress bar if progress is unknown
  Support loading appstream files from custom install prefix
  Use the runtime fwupd version for the user agent

  3.38.0 is a pure translation update.

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

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

[Desktop-packages] [Bug 1898713] Re: Xorg crashes sometimes with Easystrokes

** Attachment added: "text utf8"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418338/+files/LightdmDisplayLog.txt

** Attachment removed: "LightdmLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418321/+files/LightdmLog.txt

** Attachment removed: "XorgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418333/+files/XorgLog.txt

** Attachment removed: "XorgLogOld.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418334/+files/XorgLogOld.txt

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

Title:
  Xorg crashes sometimes with Easystrokes

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg crashes, session closes, all unsaved data is gone.

  What I did / Reproducing
  ===

  It happens when I use Easystrokes to emulate `Ctrl+F4` or
  `Ctrl+PageUp/Down`.

  So far it happened about 5 recognized times, 3 recorded within the
  last 3(?) month. twice during tab switching in incognito Firefox and
  once in VSCode.

  Reproducability
  
  I feel it's very consistent in crashing in Firefox incognito. But it's not 
purposely reproducible 100%.

  I would give more information, but the stacktrace of the crashdump
  does not tell much. I installed debug symbols for xorg, but they made
  no change viewing it.

  Here is the (obscured) stack trace:

  ```
  Reading symbols from /usr/lib/xorg/Xorg...
  Reading symbols from 
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
  [New LWP 100716]
  [New LWP 100705]
  [New LWP 100704]
  [New LWP 100707]
  [New LWP 100709]
  [New LWP 100708]
  [New LWP 100706]
  [New LWP 100711]
  [New LWP 100710]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  --Type  for more, q to quit, c to continue without paging--
  Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x55a0da61fe9c in miPointerSetPosition (
  pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
  screenx=screenx@entry=0x7f707b57d570, 
  screeny=screeny@entry=0x7f707b57d578, 
  nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
  at ../../../../mi/mipointer.c:610
  610   ../../../../mi/mipointer.c: No such file or directory.
  [Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
  (gdb) 
  (gdb) 
  (gdb) bt full
  #0  0x55a0da61fe9c in miPointerSetPosition
  (pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578, 
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at 
../../../../mi/mipointer.c:610
  pScreenPriv = 
  pScreen = 
  newScreen = 0x254
  x = 802
  y = 596
  switch_screen = 0
  should_constrain_barriers = 0
  i = 
  pPointer = 0x0
  #1  0x55a0da4ec840 in positionSprite
  (dev=dev@entry=0x55a0dc969400, mode=mode@entry=0, 
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580, 
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570, 
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at 
../../../../dix/getevents.c:961
  scr = 
  tmpx = 801.02961125081322
  tmpy = 595.47038874918678
  #2  0x55a0da4ecf4d in positionSprite
  (events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578, 
scre--Type  for more, q to quit, c to continue without paging--
  enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580, 
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at 
../../../../dix/getevents.c:952
  scr = 0x0
  num_events = 2
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #3  fill_pointer_events (events=0x7f708d903c20, 
  events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, 
type=, buttons=buttons@entry=0, ms=ms@entry=289728198, 
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at 
../../../../dix/getevents.c:1434
  num_events = 2
  --Type  for more, q to quit, c to continue without paging--
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678

[Desktop-packages] [Bug 1898713] Re: Xorg crashes sometimes with Easystrokes

** Attachment added: "text/plain; charset="utf-8""
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418340/+files/XorgLog.txt

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

Title:
  Xorg crashes sometimes with Easystrokes

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg crashes, session closes, all unsaved data is gone.

  What I did / Reproducing
  ===

  It happens when I use Easystrokes to emulate `Ctrl+F4` or
  `Ctrl+PageUp/Down`.

  So far it happened about 5 recognized times, 3 recorded within the
  last 3(?) month. twice during tab switching in incognito Firefox and
  once in VSCode.

  Reproducability
  
  I feel it's very consistent in crashing in Firefox incognito. But it's not 
purposely reproducible 100%.

  I would give more information, but the stacktrace of the crashdump
  does not tell much. I installed debug symbols for xorg, but they made
  no change viewing it.

  Here is the (obscured) stack trace:

  ```
  Reading symbols from /usr/lib/xorg/Xorg...
  Reading symbols from 
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
  [New LWP 100716]
  [New LWP 100705]
  [New LWP 100704]
  [New LWP 100707]
  [New LWP 100709]
  [New LWP 100708]
  [New LWP 100706]
  [New LWP 100711]
  [New LWP 100710]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  --Type  for more, q to quit, c to continue without paging--
  Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x55a0da61fe9c in miPointerSetPosition (
  pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
  screenx=screenx@entry=0x7f707b57d570, 
  screeny=screeny@entry=0x7f707b57d578, 
  nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
  at ../../../../mi/mipointer.c:610
  610   ../../../../mi/mipointer.c: No such file or directory.
  [Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
  (gdb) 
  (gdb) 
  (gdb) bt full
  #0  0x55a0da61fe9c in miPointerSetPosition
  (pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578, 
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at 
../../../../mi/mipointer.c:610
  pScreenPriv = 
  pScreen = 
  newScreen = 0x254
  x = 802
  y = 596
  switch_screen = 0
  should_constrain_barriers = 0
  i = 
  pPointer = 0x0
  #1  0x55a0da4ec840 in positionSprite
  (dev=dev@entry=0x55a0dc969400, mode=mode@entry=0, 
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580, 
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570, 
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at 
../../../../dix/getevents.c:961
  scr = 
  tmpx = 801.02961125081322
  tmpy = 595.47038874918678
  #2  0x55a0da4ecf4d in positionSprite
  (events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578, 
scre--Type  for more, q to quit, c to continue without paging--
  enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580, 
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at 
../../../../dix/getevents.c:952
  scr = 0x0
  num_events = 2
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #3  fill_pointer_events (events=0x7f708d903c20, 
  events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, 
type=, buttons=buttons@entry=0, ms=ms@entry=289728198, 
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at 
../../../../dix/getevents.c:1434
  num_events = 2
  --Type  for more, q to quit, c to continue without paging--
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #4  0x55a0da4ee620 in GetPointerEvents
  (events=0x7f708d903010, pDev=pD

[Desktop-packages] [Bug 1898713] Re: Xorg crashes sometimes with Easystrokes

** Attachment added: "text/plain; charset="utf-8""
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418339/+files/LightdmLog.txt

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

Title:
  Xorg crashes sometimes with Easystrokes

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg crashes, session closes, all unsaved data is gone.

  What I did / Reproducing
  ===

  It happens when I use Easystrokes to emulate `Ctrl+F4` or
  `Ctrl+PageUp/Down`.

  So far it happened about 5 recognized times, 3 recorded within the
  last 3(?) month. twice during tab switching in incognito Firefox and
  once in VSCode.

  Reproducability
  
  I feel it's very consistent in crashing in Firefox incognito. But it's not 
purposely reproducible 100%.

  I would give more information, but the stacktrace of the crashdump
  does not tell much. I installed debug symbols for xorg, but they made
  no change viewing it.

  Here is the (obscured) stack trace:

  ```
  Reading symbols from /usr/lib/xorg/Xorg...
  Reading symbols from 
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
  [New LWP 100716]
  [New LWP 100705]
  [New LWP 100704]
  [New LWP 100707]
  [New LWP 100709]
  [New LWP 100708]
  [New LWP 100706]
  [New LWP 100711]
  [New LWP 100710]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  --Type  for more, q to quit, c to continue without paging--
  Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x55a0da61fe9c in miPointerSetPosition (
  pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
  screenx=screenx@entry=0x7f707b57d570, 
  screeny=screeny@entry=0x7f707b57d578, 
  nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
  at ../../../../mi/mipointer.c:610
  610   ../../../../mi/mipointer.c: No such file or directory.
  [Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
  (gdb) 
  (gdb) 
  (gdb) bt full
  #0  0x55a0da61fe9c in miPointerSetPosition
  (pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578, 
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at 
../../../../mi/mipointer.c:610
  pScreenPriv = 
  pScreen = 
  newScreen = 0x254
  x = 802
  y = 596
  switch_screen = 0
  should_constrain_barriers = 0
  i = 
  pPointer = 0x0
  #1  0x55a0da4ec840 in positionSprite
  (dev=dev@entry=0x55a0dc969400, mode=mode@entry=0, 
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580, 
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570, 
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at 
../../../../dix/getevents.c:961
  scr = 
  tmpx = 801.02961125081322
  tmpy = 595.47038874918678
  #2  0x55a0da4ecf4d in positionSprite
  (events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578, 
scre--Type  for more, q to quit, c to continue without paging--
  enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580, 
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at 
../../../../dix/getevents.c:952
  scr = 0x0
  num_events = 2
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #3  fill_pointer_events (events=0x7f708d903c20, 
  events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, 
type=, buttons=buttons@entry=0, ms=ms@entry=289728198, 
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at 
../../../../dix/getevents.c:1434
  num_events = 2
  --Type  for more, q to quit, c to continue without paging--
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #4  0x55a0da4ee620 in GetPointerEvents
  (events=0x7f708d903010, pDev

[Desktop-packages] [Bug 1898713] [NEW] Xorg crashes sometimes with Easystrokes

Public bug reported:

Xorg crashes, session closes, all unsaved data is gone.

What I did / Reproducing
===

It happens when I use Easystrokes to emulate `Ctrl+F4` or
`Ctrl+PageUp/Down`.

So far it happened about 5 recognized times, 3 recorded within the last
3(?) month. twice during tab switching in incognito Firefox and once in
VSCode.

Reproducability

I feel it's very consistent in crashing in Firefox incognito. But it's not 
purposely reproducible 100%.

I would give more information, but the stacktrace of the crashdump does
not tell much. I installed debug symbols for xorg, but they made no
change viewing it.

Here is the (obscured) stack trace:

```
Reading symbols from /usr/lib/xorg/Xorg...
Reading symbols from 
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
[New LWP 100716]
[New LWP 100705]
[New LWP 100704]
[New LWP 100707]
[New LWP 100709]
[New LWP 100708]
[New LWP 100706]
[New LWP 100711]
[New LWP 100710]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
--Type  for more, q to quit, c to continue without paging--
Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x55a0da61fe9c in miPointerSetPosition (
pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
screenx=screenx@entry=0x7f707b57d570, 
screeny=screeny@entry=0x7f707b57d578, 
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
at ../../../../mi/mipointer.c:610
610 ../../../../mi/mipointer.c: No such file or directory.
[Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
(gdb) 
(gdb) 
(gdb) bt full
#0  0x55a0da61fe9c in miPointerSetPosition
(pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578, 
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at 
../../../../mi/mipointer.c:610
pScreenPriv = 
pScreen = 
newScreen = 0x254
x = 802
y = 596
switch_screen = 0
should_constrain_barriers = 0
i = 
pPointer = 0x0
#1  0x55a0da4ec840 in positionSprite
(dev=dev@entry=0x55a0dc969400, mode=mode@entry=0, 
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580, 
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570, 
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at 
../../../../dix/getevents.c:961
scr = 
tmpx = 801.02961125081322
tmpy = 595.47038874918678
#2  0x55a0da4ecf4d in positionSprite
(events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578, 
scre--Type  for more, q to quit, c to continue without paging--
enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580, 
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at 
../../../../dix/getevents.c:952
scr = 0x0
num_events = 2
event = 
raw = 0x7f708d903010
screenx = 801.02961125081322
screeny = 595.47038874918678
devx = 801.02961125081322
devy = 595.47038874918678
sx = 0
sy = 0
mask = 
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
scr = 
num_barrier_events = 0
#3  fill_pointer_events (events=0x7f708d903c20, 
events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, 
type=, buttons=buttons@entry=0, ms=ms@entry=289728198, 
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at 
../../../../dix/getevents.c:1434
num_events = 2
--Type  for more, q to quit, c to continue without paging--
event = 
raw = 0x7f708d903010
screenx = 801.02961125081322
screeny = 595.47038874918678
devx = 801.02961125081322
devy = 595.47038874918678
sx = 0
sy = 0
mask = 
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
scr = 
num_barrier_events = 0
#4  0x55a0da4ee620 in GetPointerEvents
(events=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, type=, type@entry=6, buttons=buttons@entry=0, flags=10, mask_in=)
at ../../../../dix/getevents.c:1691
ms = 289728198
num_events = 0
nev_tmp = 
mask = 
{last_bit = 1 '\001', has_unaccelerated = 1 '\001', mask = 
"\003\000--Type  for more, q to quit, c to continue without paging--
\000\000", valuators = {-1, -1.5, 0 }, unaccelerated = {-2, 
-3, 0 }}
scroll = 
{last_bit = -128 '\200', has_unaccelerated = 4 '\004', mask = 
"eݠU", valuators = {6.9229118033614265e-310, 6.9229013081954128e-310, 
6.922

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2020-10-06 Thread wangjun

@Azizkhan (injkgz)

read patch file ,find the right line,then manual patch ，do not use tool.

-- 
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 Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  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 Legion 5 15ARH05
  dmi.sys.

[Desktop-packages] [Bug 1892136] Re: reverse prime produces corrupted output on specific resolutions

2020-10-06 Thread Aleksander Miera

@vanvugt is there any chance this gets merged? Preferably on Xorg's end,
if you can give me a hint on whom to tag there it would be most
appreciated.

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

Title:
  reverse prime produces corrupted output on specific resolutions

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  In Progress

Bug description:
  The issue has initially been discovered for resolution 1366x768 on a
  DisplayLink (evdi)-backed device, but applies also to UDL, as well as
  reverse prime setups (rendering on Intel, output through NVidia).

  The issue manifests with 1366x768 and several other resolutions only,
  due to the fact that the GPU seems to use 64-aligned framebuffer
  stride. This is "accidentally" fine with the most popular VGA
  resolutions (e.g. assuming 32bits/4bytes per pixel and FullHD, the
  stride would be 1920*4 -> 7680, which is divisible by 64 w/o a
  remainder, yet 1366*4=5464, 5464/64 = 85.375). The proposed fix is to
  update the stride with the GPU-provided value instead of the Xorg-
  calculated one at the stage of sharing the pixmap between GPUs. Doing
  that at earlier stage would probably require distinguishing between
  allocation of a FB and a generic pixmap, which is the same for Xorg.

  Issue for sure was seen on 18.04 and 19.04, probably still there for
  20.04.

  Upstream report:
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/889

  And posted (not yet integrated) fix:
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/496

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

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

[Desktop-packages] [Bug 1897224] Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display

** Also affects: snapd
   Importance: Undecided
   Status: New

** Changed in: snapd
   Status: New => Confirmed

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

Title:
  [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to
  open X display

Status in snapd:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run chromium installed via snap in Ubuntu 20.10 when
  running Ubuntu Wayland session. Unfortunately, chromium wouldn't
  start:

  > chromium 
  [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to 
open X display.

  I am able to run Firefox just fine (assuming that Firefox still runs
  on xwayland) and also Intellij snap works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 25 09:45:16 2020
  InstallationDate: Installed on 2016-09-05 (1480 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Snap: chromium 85.0.4183.121 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1897224] Re: [snap] chromium wayland won't start in Ubuntu 20.10: Unable to open X display

Back on the subject of this bug, it may be related to changes in the fd
numbers of -listen and -displayfd passed to Xwayland in mutter 3.38. If
that's relevant at all then it's probably still a snapd issue.

** Changed in: mutter (Ubuntu)
   Status: In Progress => Invalid

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

** Summary changed:

- [snap] chromium wayland won't start in Ubuntu 20.10: Unable to open X display
+ [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X 
display

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

Title:
  [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to
  open X display

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run chromium installed via snap in Ubuntu 20.10 when
  running Ubuntu Wayland session. Unfortunately, chromium wouldn't
  start:

  > chromium 
  [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to 
open X display.

  I am able to run Firefox just fine (assuming that Firefox still runs
  on xwayland) and also Intellij snap works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 25 09:45:16 2020
  InstallationDate: Installed on 2016-09-05 (1480 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Snap: chromium 85.0.4183.121 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897224/+subscriptions

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

[Desktop-packages] [Bug 1751673] Re: nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

2020-10-06 Thread Cyrille37

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

Hi,

This bug continue, on Ubuntu 18.04.5 LTS + MATE 1.20.1.

In .xsession-errors :

(nm-applet:2221): Gtk-CRITICAL **: 12:09:29.609: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
(nm-applet:2221): Gtk-CRITICAL **: 12:09:29.609: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
(nm-applet:2221): Gtk-WARNING **: 12:09:29.611: Can't set a parent on widget 
which has a parent
(nm-applet:2221): Gtk-CRITICAL **: 12:09:29.614: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
(nm-applet:2221): Gtk-CRITICAL **: 12:09:29.614: gtk_widget_destroy: assertion 
'GTK_IS_WIDGET (widget)' failed
(nm-applet:2221): Gtk-WARNING **: 12:09:29.615: Can't set a parent on widget 
which has a parent

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

Title:
  nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET
  (widget)' failed

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  running 18.04 this message is spamming into syslog:
  > nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' 
failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.8.4-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Feb 26 01:16:49 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-09-28 (1611 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1 proto static metric 600 
   169.254.0.0/16 dev wlan1 scope link metric 1000 
   192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.34 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-01-12 (44 days ago)
  
modified.conffile..etc.polkit-1.localauthority.50-local.d.org.freedesktop.NetworkManager.pkla:
 [deleted]
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   wlan1  wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  k2l 
7df024b1-9b89-4f95-84c1-03188bb67f77  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   EC:88:92:02:17:7D  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  --  --   
 -- 
   eth1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1751673/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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-10-06 Thread Azizkhan

@wangjun
How did you compiled old patch with kernel 5.8.13?

-- 
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 Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  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 Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemTy

[Desktop-packages] [Bug 1897224] Re: [snap] chromium wayland won't start in Ubuntu 20.10: Unable to open X display