[Touch-packages] [Bug 1928566] [NEW] Triangular window rendering artifacts on xubuntu 20.04.1

2021-05-15 Thread Aleksandr
Public bug reported:

Window and content rendering artifacts in some applications. The
artifacts look like triangles. Sometimes small, sometimes half the size
of a window.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: XFCE
Date: Sun May 16 09:30:39 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1043:15bd]
InstallationDate: Installed on 2021-05-11 (4 days ago)
InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 008: ID 04ca:3005 Lite-On Technology Corp. Atheros Bluetooth
 Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
 Bus 001 Device 002: ID 0bda:5603 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X200MA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=58e5ff6d-3ae6-4dc0-b103-280ed09a8720 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/19/2019
dmi.bios.release: 5.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X200MA.601
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X200MA
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.:bvrX200MA.601:bd04/19/2019:br5.6:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X200MA
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

** Attachment added: "Window and content rendering artifacts in some 
applications. The artifacts look like triangles. Sometimes small, sometimes 
half the size of a window."
   
https://bugs.launchpad.net/bugs/1928566/+attachment/5497881/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0_2021-05-16_08-41-42.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1928566

Title:
  Triangular window rendering artifacts on xubuntu 20.04.1

Status in xorg package in Ubuntu:
  New

Bug description:
  Window and content rendering artifacts in some applications. The
  artifacts look like triangles. Sometimes small, sometimes half the
  size of a window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun May 16 09:30:39 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1043:15bd]
  InstallationDate: Installed on 2021-05-11 (4 days ago)
  InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 008: ID 04ca:3005 Lite-On Technology Corp. Atheros Bluetooth
   Bus 001 Device 003: ID 05e3:0608 Genesys 

[Touch-packages] [Bug 1441460] Re: [xubuntu] Failing to sleep after inactivity - power manager error?

2021-05-15 Thread Launchpad Bug Tracker
[Expired for powermgmt-base (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: powermgmt-base (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu.
https://bugs.launchpad.net/bugs/1441460

Title:
  [xubuntu] Failing to sleep after inactivity - power manager error?

Status in powermgmt-base package in Ubuntu:
  Expired
Status in xfce4-power-manager package in Ubuntu:
  Invalid

Bug description:
  Newly installed XUbuntu 14.10 on 2 different machines but both
  experience the same problem.

  Problem:

  Failing to sleep after inactivity and a "xfce4 power manager error"

  When setting the machine in xfce4-power-manager to suspend after e.g.
  15 minutes the machine will fail to suspend.

  This is the message that meets me when I login after a failed suspend:

  Power Manager Error  
  GDBus.Error:org.freedesktop.DBus.Error.NoReply:
  Did not receive a reply. Possible causes include: the
  remote application did not send a reply, the message
  bus security policy blocked the reply, the reply
  timeout expired, or the network connection was 
  broken.

  http://s27.postimg.org/l24boyvqp/Screenshot_2015_04_05_15_20_38.png

  I can suspend from the logout dialog box.

  The following command suspends the system just fine:
  $ dbus-send --system --print-reply --dest="org.freedesktop.UPower" 
/org/freedesktop/UPower org.freedesktop.UPower.Suspend

  $ xfce4-power-manager --dump
  ---
  Xfce power manager version 1.4.1
  With policykit support
  With network manager support
  ---
  Can suspend: True
  Can hibernate: False
  Authorized to suspend: True
  Authorized to hibernate: False
  Authorized to shutdown: True
  Has battery: False
  Has brightness panel: True
  Has power button: True
  Has hibernate button: True
  Has sleep button: True
  Has LID: False

  So I guess It's some kind of  auth or policykit issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1441460/+subscriptions

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


[Touch-packages] [Bug 1928564] [NEW] systemctl reboot hangs the machine under hirsute 21.04

2021-05-15 Thread Robert Dinse
Public bug reported:

If you type "systemctl reboot" instead of rebooting the machine hangs
hard, nothing except a hard power cycle seems to get it's attention.
This is true of both physical hardware and virtual machines, it was NOT
a problem under groovy.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: systemd 247.3-3ubuntu3
Uname: Linux 5.12.4 x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Sat May 15 19:12:59 2021
InstallationDate: Installed on 2020-08-10 (278 days ago)
InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 
root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7
SourcePackage: systemd
SystemdFailedUnits:
 Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: 
Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
 Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago)
dmi.bios.date: 06/04/2020
dmi.bios.release: 16.2
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1602
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z390-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: ASUS_MB_CNL
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1928564

Title:
  systemctl reboot hangs the machine under hirsute 21.04

Status in systemd package in Ubuntu:
  New

Bug description:
  If you type "systemctl reboot" instead of rebooting the machine hangs
  hard, nothing except a hard power cycle seems to get it's attention.
  This is true of both physical hardware and virtual machines, it was
  NOT a problem under groovy.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu3
  Uname: Linux 5.12.4 x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Sat May 15 19:12:59 2021
  InstallationDate: Installed on 2020-08-10 (278 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 
root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago)
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 16.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1602
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z390-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04

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

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


[Touch-packages] [Bug 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04

2021-05-15 Thread Robert Dinse
This resulted in a several hour outage and a 44 mile round trip drive
that should not have been necessary.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1928564

Title:
  systemctl reboot hangs the machine under hirsute 21.04

Status in systemd package in Ubuntu:
  New

Bug description:
  If you type "systemctl reboot" instead of rebooting the machine hangs
  hard, nothing except a hard power cycle seems to get it's attention.
  This is true of both physical hardware and virtual machines, it was
  NOT a problem under groovy.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu3
  Uname: Linux 5.12.4 x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Sat May 15 19:12:59 2021
  InstallationDate: Installed on 2020-08-10 (278 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 
root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago)
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 16.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1602
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z390-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04

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

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


[Touch-packages] [Bug 1928534] Re: [82DG, Realtek ALC287, Speaker, Internal] No sound at all

2021-05-15 Thread Hui Wang
Please run:

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x08
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x4ab7

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

Title:
  [82DG, Realtek ALC287, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  PC:Lenovo YOGA 14C Intel EVO   CPU:i5-1135G7

  sound card:
  cat /proc/asound/cards
   0 [sofhdadsp  ]: sof-hda-dsp - sof-hda-dsp
LENOVO-82DG-Yoga14cITL2021-LNVNB161216

  others info:
  inxi -SMA
  System:Host: rick Kernel: 5.8.0-53-generic x86_64 bits: 64 Desktop: Gnome 
3.36.7 
 Distro: Ubuntu 20.04.2 LTS (Focal Fossa) 
  Machine:   Type: Convertible System: LENOVO product: 82DG v: Yoga 14cITL 2021 
 serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0L77769 WIN serial: 
 
 UEFI: LENOVO v: F5CN34WW date: 08/25/2020 
  Audio: Device-1: Intel driver: sof-audio-pci 
 Sound Server: ALSA v: k5.8.0-53-generic 

  This laptop was Windows10 before I install Ubuntu-OS,since I installed
  Ubuntu-OS,there is no sound in SPEAKER anymore, but it still works
  when I'm using headphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rick  25469 F pulseaudio
   /dev/snd/pcmC0D0p:   rick  25469 F...m pulseaudio
   /dev/snd/pcmC0D6c:   rick  25469 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 15 15:51:48 2021
  InstallationDate: Installed on 2021-05-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82DG, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2020
  dmi.bios.release: 1.34
  dmi.bios.vendor: LENOVO
  dmi.bios.version: F5CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 14cITL 2021
  dmi.ec.firmware.release: 1.34
  dmi.modalias: 
dmi:bvnLENOVO:bvrF5CN34WW:bd08/25/2020:br1.34:efr1.34:svnLENOVO:pn82DG:pvrYoga14cITL2021:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct31:cvrYoga14cITL2021:
  dmi.product.family: Yoga 14cITL 2021
  dmi.product.name: 82DG
  dmi.product.sku: LENOVO_MT_82DG_BU_idea_FM_Yoga 14cITL 2021
  dmi.product.version: Yoga 14cITL 2021
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2021-05-15 Thread Hui Wang
I checked the log, looks there is no problem on the speakers.

The bass speaker and main speaker work together, if you play some sound
from the speaker, the sound will be played by bass speaker and main
speaker together.

How do you expect the bass speaker to work?

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2021-05-15 Thread Launchpad Bug Tracker
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 Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1926165

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1926316] Re: lxappearance crashes on launch

2021-05-15 Thread Boris Gjenero
This also fixes the Lxdm greeter crash I reported at
https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1922443. I installed
the pre-release builds from
https://launchpad.net/ubuntu/+source/glib2.0/2.68.1-1~ubuntu21.04.1/+build/21536716
and confirm that the bug is fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1926316

Title:
  lxappearance crashes on launch

Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  Backtrace of the segmentation fault

  Program received signal SIGSEGV, Segmentation fault.
  0x7790c79d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  (gdb) bt
  #0  0x7790c79d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #1  0x7790ccc1 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x7790cf41 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x7790d079 in g_key_file_load_from_file () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x55407072 in load_icon_themes_from_dir ()
  #5  0x554073dd in icon_theme_init ()
  #6  0x55404c92 in main ()

  Strace shows that the programs borks while trying to load the icon
  theme "/usr/share/icons/gnome/index.theme".

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lxappearance 0.6.3-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Config_System_openbox: Error: [Errno 2] No such file or directory: 
'/etc/xdg/lxsession/openbox/desktop.conf'
  CurrentDesktop: lxde
  Date: Tue Apr 27 21:47:03 2021
  Icons_Default: No icons theme configured by default
  InstallationDate: Installed on 2021-01-12 (105 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: lxappearance
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926316/+subscriptions

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


[Touch-packages] [Bug 1902898] Re: power-button action inconsistent between user session and greeter

2021-05-15 Thread dann frazier
Verified - I do now get the prompt! Thanks laney & didrocks!

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1902898

Title:
  power-button action inconsistent between user session and greeter

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Focal:
  Fix Committed
Status in ubuntu-settings source package in Hirsute:
  Fix Released

Bug description:
  [Impact] 
  When a user is logged in to the Ubuntu desktop, a power button event will 
cause the user to be prompted to choose if they'd like to proceed with a 
shutdown. However, if the system is sitting at a greeter screen, a power button 
event will instead attempt a suspend w/o prompting. This is due to a different 
set of defaults for the greeter and the user.
  This is a fix for this, aligning all power actions between the greeter 
behaviour and the user session one on the user session.

  [Test Plan] 
  1. Install new package and reboot
  2. On the greeter screen (gdm), press the physical power button of your 
machine.
  3. You should be now prompted about what to do, like shutdown. You can 
dismiss it.
  4. Clicking on the physical suspend button should suspend the machine 
immediatly.

  [Where problems could occur]
  We change the scope of when we applied those settings: we were only applying 
them to the GNOME session ran by the user, and it will now be applied as 
default to the GNOME session ran by gdm.
  Impacts is thus limited to the greeter screen.

  
  Diff is available on this commit: 
https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu-settings/commit/?h=focal=ca2f9aa9b03862ff044b64d7ef9506ca87e3dd89

  --
  Original report content:

  For a logged-in desktop user, they
  see:

  $ gsettings get org.gnome.settings-daemon.plugins.power
  power-button-action 'interactive'

  But the gdm user sees:
  $ sudo machinectl shell gdm@ /bin/bash
  Connected to the local host. Press ^] three times within 1s to exit session.
  gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power 
power-button-action
  'suspend'

  Changing the gdm user's setting to "interactive" using gsettings
  causes the greeter to begin prompting, consistent with the logged in
  user experience.

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

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


[Touch-packages] [Bug 1731581] Re: Context menus do not appear for Gtk text areas upon right-click

2021-05-15 Thread PJSingh5000
The issue has since been fixed and is not present in gtk3, version 3.24.

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1731581

Title:
  Context menus do not appear for Gtk text areas upon right-click

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  When right-clicking on Gtk text areas (such as an editable text area
  or a text entry field), a context menu does not appear.  The pop-up
  context menu typically lists options such as copy, paste, etc.

  EXAMPLES

  Examples of applications that are impacted include:
  1. Gedit Text Area
  2. Nautlus (editable address bar)
  3. Google Chrome URL bar
  4. GtkHash (text entry fields)

  Interestingly the text areas of some other applications do show pop-up 
context menu when right-clicked:
  1. Libre Office Writer
  2. Web pages in Google Chrome that require text entry (such as this web page)

  RECREATING ISSUE

  I do not have a consistent way to recreate this issue (yet). When I
  first log in, the right-click context menus work fine.  After some
  time of usage, the right-click context menus no longer appear.  If I
  use the computer long enough (over an hour) without rebooting, this
  issue always appears.

  This issue seems to only affect widgets that require text entry.
  However, there is one exception I have noticed: the tabs in Google
  Chrome stop showing pop-up context menus at the same time as this
  issues manifests itself for the rest of gnome-shell applications with
  text areas.

  
  OTHER CONTEXT MENUS

  Context menus for other widgets do appear upon right-click, as
  expected, and work fine.  For example, the context menu for window
  title bars appear when right-clicking on them.  The context menu for
  folders and files in Nautilus also appear when right-clicking on them.

  
  SYSTEM INFORMATION

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.1-0ubuntu5
Candidate: 3.26.1-0ubuntu5
Version table:
   *** 3.26.1-0ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 10 18:39:00 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['caffe...@patapon.info', 
'coverflowalt...@palatis.blogspot.com', 'print...@linux-man.org', 
'refresh-w...@kgshank.net', 'ubuntu-appindicat...@ubuntu.com', 
'ubuntu-d...@ubuntu.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'cariboubloc...@git.keringar.xyz', 'gpa...@gnome-shell-extensions.gnome.org']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-11-08 (2 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.11.07 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected

2021-05-15 Thread PJSingh5000
@Egmont,

You mean it will always be like this going forward?

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - -

Is this the feature you are referring to?...

f. New active mark and face feature: when enabled, it will highlight the text
   inserted by a bracketed paste (the `active region') and the text found by
   incremental and non-incremental history searches. This is tied to bracketed
   paste and can be disabled by turning off bracketed paste.

..or, is it this one?...

h. Bracketed paste mode is enabled by default.

If so, it looks like this "feature" can be disabled. How?

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - -

I find there is an inconsistency with this new approach:
If you've just pasted text, then highlight the text, the text looks 
unhighlighted.
This is visually confusing.

Perhaps this is an unintended consequence that needs remediation?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1926256

Title:
  Pasted text in the terminal is always highlighted and selected

Status in bash package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in mate-terminal package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 21.04 installed
  2. Launch terminal
  3a. Execute some command, select this command to copy it, then paste command
  3b. Paste some command from clipboard to terminal

  Expected result:
  * pasted command is not highlighted and is not selected

  Actual result:
  * pasted command is selected and highlighted

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mate-terminal 1.24.1-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Apr 27 09:43:56 2021
  InstallationDate: Installed on 2021-04-23 (3 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1928534] Re: [82DG, Realtek ALC287, Speaker, Internal] No sound at all

2021-05-15 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  [82DG, Realtek ALC287, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  PC:Lenovo YOGA 14C Intel EVO   CPU:i5-1135G7

  sound card:
  cat /proc/asound/cards
   0 [sofhdadsp  ]: sof-hda-dsp - sof-hda-dsp
LENOVO-82DG-Yoga14cITL2021-LNVNB161216

  others info:
  inxi -SMA
  System:Host: rick Kernel: 5.8.0-53-generic x86_64 bits: 64 Desktop: Gnome 
3.36.7 
 Distro: Ubuntu 20.04.2 LTS (Focal Fossa) 
  Machine:   Type: Convertible System: LENOVO product: 82DG v: Yoga 14cITL 2021 
 serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0L77769 WIN serial: 
 
 UEFI: LENOVO v: F5CN34WW date: 08/25/2020 
  Audio: Device-1: Intel driver: sof-audio-pci 
 Sound Server: ALSA v: k5.8.0-53-generic 

  This laptop was Windows10 before I install Ubuntu-OS,since I installed
  Ubuntu-OS,there is no sound in SPEAKER anymore, but it still works
  when I'm using headphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rick  25469 F pulseaudio
   /dev/snd/pcmC0D0p:   rick  25469 F...m pulseaudio
   /dev/snd/pcmC0D6c:   rick  25469 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 15 15:51:48 2021
  InstallationDate: Installed on 2021-05-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82DG, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2020
  dmi.bios.release: 1.34
  dmi.bios.vendor: LENOVO
  dmi.bios.version: F5CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 14cITL 2021
  dmi.ec.firmware.release: 1.34
  dmi.modalias: 
dmi:bvnLENOVO:bvrF5CN34WW:bd08/25/2020:br1.34:efr1.34:svnLENOVO:pn82DG:pvrYoga14cITL2021:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct31:cvrYoga14cITL2021:
  dmi.product.family: Yoga 14cITL 2021
  dmi.product.name: 82DG
  dmi.product.sku: LENOVO_MT_82DG_BU_idea_FM_Yoga 14cITL 2021
  dmi.product.version: Yoga 14cITL 2021
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1928534] [NEW] [82DG, Realtek ALC287, Speaker, Internal] No sound at all

2021-05-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

PC:Lenovo YOGA 14C Intel EVO   CPU:i5-1135G7

sound card:
cat /proc/asound/cards
 0 [sofhdadsp  ]: sof-hda-dsp - sof-hda-dsp
  LENOVO-82DG-Yoga14cITL2021-LNVNB161216

others info:
inxi -SMA
System:Host: rick Kernel: 5.8.0-53-generic x86_64 bits: 64 Desktop: Gnome 
3.36.7 
   Distro: Ubuntu 20.04.2 LTS (Focal Fossa) 
Machine:   Type: Convertible System: LENOVO product: 82DG v: Yoga 14cITL 2021 
   serial:  
   Mobo: LENOVO model: LNVNB161216 v: SDK0L77769 WIN serial: 
 
   UEFI: LENOVO v: F5CN34WW date: 08/25/2020 
Audio: Device-1: Intel driver: sof-audio-pci 
   Sound Server: ALSA v: k5.8.0-53-generic 

This laptop was Windows10 before I install Ubuntu-OS,since I installed
Ubuntu-OS,there is no sound in SPEAKER anymore, but it still works when
I'm using headphone.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rick  25469 F pulseaudio
 /dev/snd/pcmC0D0p:   rick  25469 F...m pulseaudio
 /dev/snd/pcmC0D6c:   rick  25469 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May 15 15:51:48 2021
InstallationDate: Installed on 2021-05-12 (2 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
Symptom_Card: sof-hda-dsp - sof-hda-dsp
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [82DG, Realtek ALC287, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/25/2020
dmi.bios.release: 1.34
dmi.bios.vendor: LENOVO
dmi.bios.version: F5CN34WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0L77769 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Yoga 14cITL 2021
dmi.ec.firmware.release: 1.34
dmi.modalias: 
dmi:bvnLENOVO:bvrF5CN34WW:bd08/25/2020:br1.34:efr1.34:svnLENOVO:pn82DG:pvrYoga14cITL2021:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct31:cvrYoga14cITL2021:
dmi.product.family: Yoga 14cITL 2021
dmi.product.name: 82DG
dmi.product.sku: LENOVO_MT_82DG_BU_idea_FM_Yoga 14cITL 2021
dmi.product.version: Yoga 14cITL 2021
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal
-- 
[82DG, Realtek ALC287, Speaker, Internal] No sound at all
https://bugs.launchpad.net/bugs/1928534
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver in Ubuntu.

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


[Touch-packages] [Bug 1928540] [NEW] After upgrading Ubuntu 18LTS to 20LTS: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script

2021-05-15 Thread Oliver Kohll
Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.4
ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
Uname: Linux 4.15.0-55-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat May 15 12:08:24 2021
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2014-11-26 (2362 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2021-05-15 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1928540

Title:
  After upgrading Ubuntu 18LTS to 20LTS: package initramfs-tools
  0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools
  package post-installation script subprocess returned error exit status
  1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.4
  ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat May 15 12:08:24 2021
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-11-26 (2362 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2021-05-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1928540/+subscriptions

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


[Touch-packages] [Bug 1928540] Re: After upgrading Ubuntu 18LTS to 20LTS: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script s

2021-05-15 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1928540

Title:
  After upgrading Ubuntu 18LTS to 20LTS: package initramfs-tools
  0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools
  package post-installation script subprocess returned error exit status
  1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.4
  ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat May 15 12:08:24 2021
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-11-26 (2362 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2021-05-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1928540/+subscriptions

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


[Touch-packages] [Bug 1268210] Re: unity-scopes-runner: Typo in package description: "scoped"

2021-05-15 Thread Hans Joachim Desserud
And now also updated in the package descripts project
https://translations.launchpad.net/ddtp-ubuntu/hirsute/+pots/ddtp-
ubuntu-universe/fr/122882/+translate

** Changed in: ddtp-ubuntu
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1268210

Title:
  unity-scopes-runner: Typo in package description: "scoped"

Status in Package Descriptions for Ubuntu:
  Fix Released
Status in libunity:
  Fix Committed
Status in libunity package in Ubuntu:
  Fix Released

Bug description:
  Package: unity-scopes-runner
  Version: 7.1.3+14.04.20131106-0ubuntu1

  Hello,

  The package description contains a small typo, I think:
   The scope runner is a handy tool for wrapping on a desktop the various
   scoped installed on the system.
  Should be:
   The scope runner is a handy tool for wrapping on a desktop the various
   scopes installed on the system.

  in the string #16945
  
https://translations.launchpad.net/ddtp-ubuntu/trusty/+pots/ddtp-ubuntu-main/fr/16945

  Regards,
  Pascal

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

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