date:20210928

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

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

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

Title:
  Qualcomm Atheros QCA6174

Status in Ubuntu MATE:
  Expired
Status in linux package in Ubuntu:
  Expired
Status in network-manager package in Ubuntu:
  Expired

Bug description:
  On Ubuntu Mate 20 (and also Linux Mint 20)
  Ping over lan wireless result:  icmp_seq=1 Destination Host Unreachable
  Network card Wireless Qualcomm Atheros QCA6174

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1888042/+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 1888042] Re: Qualcomm Atheros QCA6174

[Expired for Ubuntu MATE because there has been no activity for 60
days.]

** Changed in: ubuntu-mate
   Status: Incomplete => Expired

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

Title:
  Qualcomm Atheros QCA6174

Status in Ubuntu MATE:
  Expired
Status in linux package in Ubuntu:
  Expired
Status in network-manager package in Ubuntu:
  Expired

Bug description:
  On Ubuntu Mate 20 (and also Linux Mint 20)
  Ping over lan wireless result:  icmp_seq=1 Destination Host Unreachable
  Network card Wireless Qualcomm Atheros QCA6174

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1888042/+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 1888042] Re: Qualcomm Atheros QCA6174

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

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Qualcomm Atheros QCA6174

Status in Ubuntu MATE:
  Expired
Status in linux package in Ubuntu:
  Expired
Status in network-manager package in Ubuntu:
  Expired

Bug description:
  On Ubuntu Mate 20 (and also Linux Mint 20)
  Ping over lan wireless result:  icmp_seq=1 Destination Host Unreachable
  Network card Wireless Qualcomm Atheros QCA6174

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1888042/+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 1888125] Re: refreshing cache stuck in ubuntu mate 20.04

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

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  refreshing cache stuck in ubuntu mate 20.04

Status in Ubuntu MATE:
  Incomplete
Status in software-properties package in Ubuntu:
  Expired

Bug description:
  i have a very annoying bug which is refreshing cache is just not
  closing only if i rebooted the system!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1888125/+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 1017428] Re: avahi-demon is not disabled when on unicast '.local' domain

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

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

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

Title:
  avahi-demon is not disabled when on unicast '.local' domain

Status in avahi package in Ubuntu:
  Expired

Bug description:
  Version : Linux Mint 13 Mate 64bits

  The avahi daemon messes with .local name resolution. There are scripts
  in mint to automatically disable the avahi-daemon when a .local domain
  is detected. They don't work anymore.

  /etc/resolvconf/update-libc.d/avahi-daemon : executes another script if it 
exists : 
  /usr/lib/avahi/avahi-daemon-check-dns.sh : supposed to detect .local domains 
and disable avahi-daemon accordingly. 

  avahi-daemon-check-dns.sh returns : 
  grep: /etc/resolv.conf: No such file or directory

  resolv.conf was removed, which is why this script works no more.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1017428/+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 1406687] Re: Missing icon for mouse battery power

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

** Changed in: indicator-power (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Missing icon for mouse battery power

Status in indicator-power package in Ubuntu:
  Expired

Bug description:
  I am using Ubuntu MATE 14.04.

   have a Logitech wireless mouse. The battery icon for the mouse is
  missing in the panel. It shows up as a white rectangle with a red
  circle.

  I have attached screenshots.

  Admittedly, this might not be a MATE buA as this bug report shows:

  https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1144504

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1406687/+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 1555331] Re: crash in g_slist_remove_all from gtk_rc_clear_realized_style

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

** Changed in: gtk+2.0 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  crash in g_slist_remove_all from gtk_rc_clear_realized_style

Status in gtk+2.0 package in Ubuntu:
  Expired
Status in mate-panel package in Ubuntu:
  Won't Fix

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

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: mate-panel 1.12.2-1
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Mar  9 22:49:55 2016
  ExecutablePath: /usr/bin/mate-panel
  InstallationDate: Installed on 2016-02-25 (12 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  ProcCmdline: mate-panel
  SegvAnalysis:
   Segfault happened at: 0x7f4fa6439b1c :cmp
%rbp,(%rdi)
   PC (0x7f4fa6439b1c) ok
   source "%rbp" ok
   destination "(%rdi)" (0x160016) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-panel
  StacktraceTop:
   g_slist_remove_all () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_rc_reset_styles () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  Title: mate-panel crashed with SIGSEGV in g_slist_remove_all()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1555331/+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 1591704] Re: bluetoothd crashed with SIGSEGV in GIIO_wsetb()

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

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

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

Title:
  bluetoothd crashed with SIGSEGV in __GI__IO_wsetb()

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Bluetooth crashinfo displayed shortly after login. This happens
  repeatedly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-powerpc-smp 4.4.8
  Uname: Linux 4.4.0-22-powerpc-smp ppc
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  Date: Sat Jun 11 11:26:29 2016
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2015-09-16 (269 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha powerpc 
(20150827)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 05ac:0215 Apple, Inc. Internal Keyboard/Trackpad (ISO)
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/lib/bluetooth/bluetoothd
  ProcEnviron:
   LANG=de_AT.UTF-8
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
  ProcKernelCmdLine: root=UUID=e7580396-741d-4923-8a8a-50db1b938df3 ro 
rootflags=subvol=@ quiet splash
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   __GI__IO_wsetb (f=f@entry=0x204b7ca0 <_IO_stdout_>, b=b@entry=0x0, 
eb=eb@entry=0x0, a=a@entry=0) at wgenops.c:105
   _IO_unbuffer_all () at genops.c:918
   _IO_cleanup () at genops.c:960
   __run_exit_handlers (status=0, listp=, 
run_list_atexit=run_list_atexit@entry=true) at exit.c:95
   __GI_exit (status=) at exit.c:104
  Title: bluetoothd crashed with SIGSEGV in __GI__IO_wsetb()
  UpgradeStatus: Upgraded to xenial on 2016-05-08 (35 days ago)
  UserGroups:
   
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:14:51:95:FF:B4  ACL MTU: 384:8  SCO MTU: 64:8
UP RUNNING 
RX bytes:534 acl:0 sco:0 events:27 errors:0
TX bytes:612 acl:0 sco:0 commands:26 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1591704/+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 1944606] Re: [EDIFIER X3 R, recording] Microphone is not detected as an audio input

2021-09-28 Thread Hui Wang

If so, usually it is the issue on bluetooth host controller side. Either
the kernel's driver issue or the bluetooth firmware's issue.

Please upload the log of '$usb-devices'.

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

Title:
  [EDIFIER X3 R, recording] Microphone is not detected as an audio input

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Device doesn't appear in the input options inside gnome sound
  controls. It appears in pavucontrol, but there is no port associated
  to it, and no sound is captured.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amanda 2204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity
  Date: Wed Sep 22 14:46:42 2021
  InstallationDate: Installed on 2021-09-09 (13 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: EDIFIER X3 R
  Symptom_Type: None of the above
  Title: [EDIFIER X3 R, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0TMFFT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd03/30/2021:br1.4:svnDellInc.:pnVostro5402:pvr:sku0A03:rvnDellInc.:rn0TMFFT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5402
  dmi.product.sku: 0A03
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1944606/+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 1945367] Re: Xorg crash with Nvidia drivers after installation

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Xorg crash with Nvidia drivers after installation

Status in Ubuntu:
  Incomplete

Bug description:
  i open a second bug report because i have already freeze problem after the 
installation of nvidia drivers and reboot.
  Freeze become generally when i am using firefox and visioning a video with 
youtube.
  I specify that since the last bug report, i re install ubuntu with official 
.iso without other package non official.
  To create the report, i have to connect to the PC from another one with ssh.
  When i use ubuntu-bug, it is not possible to join nvidia-bug-report because 
the application dont give me the hand to finish the report.
  When i try to execute nvidia-bug-report, i have the same thing.

  To use the PC, i have to use nouveau drivers and intel Xe GPU with
  poor performances ...

  Thanks for help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.63.01  Tue Aug  3 
20:44:16 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  Date: Tue Sep 28 21:13:05 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2090]
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Intel Corporation Device [8086:2090]
  InstallationDate: Installed on 2021-09-26 (1 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Intel(R) Client Systems NUC11PHi7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=24658b6f-3e37-4376-bc2e-2207e961c9c8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PHTGL579.0063.2021.0707.1057
  dmi.board.name: NUC11PHBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M26151-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 12.19
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPHTGL579.0063.2021.0707.1057:bd07/07/2021:br5.19:efr12.19:svnIntel(R)ClientSystems:pnNUC11PHi7:pvrM26149-403:skuSWNUC11PHKi7C00:rvnIntelCorporation:rnNUC11PHBi7:rvrM26151-402:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: PH
  dmi.product.name: NUC11PHi7
  dmi.product.sku: SWNUC11PHKi7C00
  dmi.product.version: M26149-403
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2

[Touch-packages] [Bug 1945376] Re: [Asus ZenBook Flip UX363EA] Touchpad stops working after closing the laptop

** Summary changed:

- Touch pad stopped working
+ [Asus ZenBook Flip UX363EA] Touchpad stops working after closing the laptop

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

Title:
  [Asus ZenBook Flip UX363EA] Touchpad stops working after closing the
  laptop

Status in linux package in Ubuntu:
  New

Bug description:
  The touchpad on my Asus ZenBook flip always stops working after I
  close the laptop! I have to restart the computer to make working
  again.

  Appreciate your support.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-36.40-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Sep 29 08:55:00 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Iris Xe Graphics [1043:1362]
  InstallationDate: Installed on 2021-03-14 (198 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945376/+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 1930188] Re: Acer Aspire 5 sound driver issues

2021-09-28 Thread Hui Wang

** Also affects: pulseaudio (Ubuntu Impish)
   Importance: Medium
   Status: Fix Released

** Also affects: linux (Ubuntu Impish)
   Importance: Medium
   Status: Fix Released

** Also affects: alsa-ucm-conf (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

Title:
  Acer Aspire 5 sound driver issues

Status in alsa-ucm-conf package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  New
Status in linux source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  New
Status in linux source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  In Progress
Status in alsa-ucm-conf source package in Impish:
  New
Status in linux source package in Impish:
  Fix Released
Status in pulseaudio source package in Impish:
  Fix Released

Bug description:
  SRU Justification for alsa-ucm-conf:

  [Impact]
  On the machines with the sof audio driver, users could adjust the input
  volume from UI, but this only adjusts the "Capture Volume",  the "Mic
  Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture
  Volume" to max, the recorded volume is still very low.

  [Fix]
  Backport a upstream patch, the patch adds the "Mic Boost" into the
  ucm

  [Test]
  plug a headset, make sure the headset-mic is the active input device,
  adjust the input volume to %20, open a terminal and run alsamixer,
  check the "Capture Volume" and "Mic Boost" value, then adjust the
  input volume to 80%, check those values and we could see both values
  are changed.

  [Where problems could occur]
  This patch could make the parse of input volume control fail, then
  the input volume can't be changed anymore when users adjust the
  volume from UI. But this possibility is very low, I tested this patch
  on many lenovo and dell machines with sof audio driver, all worked
  well.

  

  SRU Justification for pulseaudio:

  [Impact]
  On the machines with the sof audio driver, after booting up, the
  active output device is speaker by default, we adjust the output
  volume to 100%, then we plug a headphone, and adjust the output
  volume from 100% to 20%, now in theory, the speaker's volume is
  100%, the headphone's volume is 20%. We plugout the headphone,
  the active output device becomes speaker and we expect the volume
  changes to 100%, but the output volume for speaker is 20%.

  [Fix]
  Backport a upstream patch, this patch is already in the pulseaudio-15.0,
  so impish already has this fix. Only hirsute and focal need to backport
  this patch.

  [Test]
  adjust speaker's volume to 80%, then plug headphone and adjust headphone's
  volume to 20%, unplug the headphone, the speaker's volume becomes to 80%,
  plug the headphone, the headphone's volume becomes to 20%.

  [Where problems could occur]
  The patch writes the output volume to hardware immediately when switching
  output device on the machines with sof audio driver, this could introduce
  pop noise when changing the output device, but this possibility is very
  low, I tested the patch on many lenovo and dell machines with sof audio 
driver,
  all worked as expected and have no pop noise when switching output device.

  

  The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels
  with stable update already, but it is not merged to ubuntu 5.4.0
  kernel yet, so I sent this SRU for the focal kernel.

  [Impact]
  Users plug headphone and Mic to the audio jacks, but the system
  can't detect them, and couldn't output sound through headphone and
  record sound through Mic.

  [Fix]
  Backport a upstream patch, this will set the Mic to auto-detection
  mode and set the headphone to left location.

  [Test]
  Plug a headset to the headset audio jack, both headphone and mic
  could be detected. And output the sound to headphone, could hear
  the sound, record the sound through Mic, the sound could be recorded.

  [Where problems could occur]
  The patch is specific to Acer Aspire 5 machine, if it could introduce
  regression, it will make the audio like internal mic and internal spk
  stop working. But this possibility is very low.

  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset

[Touch-packages] [Bug 1945376] Re: Touch pad stopped working

2021-09-28 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Touch pad stopped working

Status in xorg package in Ubuntu:
  New

Bug description:
  The touchpad on my Asus ZenBook flip always stops working after I
  close the laptop! I have to restart the computer to make working
  again.

  Appreciate your support.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-36.40-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Sep 29 08:55:00 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Iris Xe Graphics [1043:1362]
  InstallationDate: Installed on 2021-03-14 (198 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1945376/+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 1930188] Re: Acer Aspire 5 sound driver issues

2021-09-28 Thread Mathew Hodson

** Also affects: alsa-ucm-conf (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu Focal)

** No longer affects: linux (Ubuntu Hirsute)

** No longer affects: linux (Ubuntu Impish)

** No longer affects: pulseaudio (Ubuntu Focal)

** No longer affects: pulseaudio (Ubuntu Hirsute)

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

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: alsa-ucm-conf (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Also affects: linux (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: alsa-ucm-conf (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Focal)
   Status: New => Fix Released

** Changed in: linux (Ubuntu Hirsute)
   Status: New => Fix Released

** Changed in: pulseaudio (Ubuntu Focal)
   Status: New => In Progress

** Changed in: pulseaudio (Ubuntu Hirsute)
   Status: New => In Progress

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

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

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

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

Title:
  Acer Aspire 5 sound driver issues

Status in alsa-ucm-conf package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  New
Status in linux source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  New
Status in linux source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  In Progress

Bug description:
  SRU Justification for alsa-ucm-conf:

  [Impact]
  On the machines with the sof audio driver, users could adjust the input
  volume from UI, but this only adjusts the "Capture Volume",  the "Mic
  Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture
  Volume" to max, the recorded volume is still very low.

  [Fix]
  Backport a upstream patch, the patch adds the "Mic Boost" into the
  ucm

  [Test]
  plug a headset, make sure the headset-mic is the active input device,
  adjust the input volume to %20, open a terminal and run alsamixer,
  check the "Capture Volume" and "Mic Boost" value, then adjust the
  input volume to 80%, check those values and we could see both values
  are changed.

  [Where problems could occur]
  This patch could make the parse of input volume control fail, then
  the input volume can't be changed anymore when users adjust the
  volume from UI. But this possibility is very low, I tested this patch
  on many lenovo and dell machines with sof audio driver, all worked
  well.

  

  SRU Justification for pulseaudio:

  [Impact]
  On the machines with the sof audio driver, after booting up, the
  active output device is speaker by default, we adjust the output
  volume to 100%, then we plug a headphone, and adjust the output
  volume from 100% to 20%, now in theory, the speaker's volume is
  100%, the headphone's volume is 20%. We plugout the headphone,
  the active output device becomes speaker and we expect the volume
  changes to 100%, but the output volume for speaker is 20%.

  [Fix]
  Backport a upstream patch, this patch is already in the pulseaudio-15.0,
  so impish already has this fix. Only hirsute and focal need to backport
  this patch.

  [Test]
  adjust speaker's volume to 80%, then plug headphone and adjust headphone's
  volume to 20%, unplug the headphone, the speaker's volume becomes to 80%,
  plug the headphone, the headphone's volume becomes to 20%.

  [Where problems could occur]
  The patch writes the output volume to hardware immediately when switching
  output device on the machines with sof audio driver, this could introduce
  pop noise when changing the output device, but this possibility is very
  low, I tested the patch on many lenovo and dell machines with sof audio 
driver,
  all worked as expected and have no pop noise when switching output device.

  

  The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels
  with stable update already, but it is not merged to ubuntu 5.4.0
  kernel

[Touch-packages] [Bug 1945376] [NEW] Touch pad stopped working

You have been subscribed to a public bug:

The touchpad on my Asus ZenBook flip always stops working after I close
the laptop! I have to restart the computer to make working again.

Appreciate your support.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-36.40-generic 5.11.22
Uname: Linux 5.11.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu65.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed Sep 29 08:55:00 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Iris Xe Graphics [1043:1362]
InstallationDate: Installed on 2021-03-14 (198 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/20/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UX363EA.306
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX363EA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
dmi.product.family: ZenBook Flip
dmi.product.name: ZenBook UX363EA_UX371EA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute third-party-packages ubuntu wayland-session
-- 
Touch pad stopped working
https://bugs.launchpad.net/bugs/1945376
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1943984] Re: No archive files for static compilation are included in the -dev package

2021-09-28 Thread Mathew Hodson

** Also affects: graphite2 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994757
   Importance: Unknown
   Status: Unknown

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

Title:
  No archive files for static compilation are included in the -dev
  package

Status in graphite2 package in Ubuntu:
  New
Status in graphite2 package in Debian:
  Unknown

Bug description:
  There is no libgraphite2.a file, so it is not possible to compile
  statically against this library. See attached patch to solve this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+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 990982] Re: [Multiarch] libfreetype6-dev:i386 dependencies issue

2021-09-28 Thread Anders Bandicoot

6 years later, I'm encountering the same issue in Ubuntu 18.04.

sudo apt install libfreetype6-dev:i386
[...]
The following packages have unmet dependencies:
 libfreetype6-dev:i386 : Depends: libc6-dev:i386 but it is not going to be 
installed or
  libc-dev:i386
 Depends: zlib1g-dev:i386 but it is not going to be 
installed or
  libz-dev:i386
 Depends: libpng-dev:i386 but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.

And then, for the linux-libc-dev:i386 dependency:

sudo apt install linux-libc-dev:i386
[...]
The following packages will be REMOVED:
  build-essential g++ g++-7 gcc-7-multilib gcc-multilib libc6-dev libc6-dev-i386
  libc6-dev-x32 libfreetype6-dev libpng-dev libstdc++-7-dev linux-libc-dev 
zlib1g-dev
The following NEW packages will be installed:
  linux-libc-dev:i386

I echo kenorb's sentiment: is there a workaround to install the 32-bit
FreeType libraries?

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

Title:
  [Multiarch] libfreetype6-dev:i386 dependencies issue

Status in freetype package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released

Bug description:
  I'm on
  alex@leon:~$ uname -a
  Linux leon 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux

  It's a fresh 12.04 install from a mini 30MB iso dd'ed to a USB flash drive.
  So it's clean and up-to-date.

  I have libfreetype6 and libfreetype6-dev installed.
  To compile wine from source (32 and 64 bit version), I need both 32 and 64 
bit development packages of several libraries.

  For gcc, I had to install gcc-multilib instead of gcc:i386 (gcc and gcc:i386 
seem to be incompatible).
  But there is no freetype6-multilib package hence my bug report.

  I think the following console output will tell you more things than
  long sentences :

  alex@leon:~$ sudo apt-get install libfreetype6-dev:i386
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
libexpat1-dev
  Use 'apt-get autoremove' to remove them.
  The following extra packages will be installed:
libc6-dev:i386 linux-libc-dev:i386 zlib1g-dev:i386
  Suggested packages:
glibc-doc:i386 manpages-dev:i386
  Recommended packages:
gcc:i386 c-compiler:i386
  The following packages will be REMOVED:
build-essential dkms g++ gcc gcc-multilib libfontconfig1-dev
libfreetype6-dev virtualbox-dkms
  The following NEW packages will be installed:
libc6-dev:i386 libfreetype6-dev:i386 linux-libc-dev:i386 zlib1g-dev:i386
  0 upgraded, 4 newly installed, 8 to remove and 0 not upgraded.
  Need to get 6,832 kB of archives.
  After this operation, 17.2 MB of additional disk space will be used.
  Do you want to continue [Y/n]? ^C

  I'm sure you understand removing build-essential and gcc is not really
  something I want to do.

  Hopefully, wine provides a configure switch (--without-freetype) to
  workaround the issue.

  If you need more details, just let me know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/990982/+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 1943312] Re: dependency problems of version 3.4.2-1ubuntu3

2021-09-28 Thread Steve Langasek

*This* bug was never present in the release pocket.  It was resolved
before libffi left -proposed.

As a user, you should not be installing updates from the -proposed
pocket of the development release.

You should file a new bug report for the issue you're experiencing.

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

Title:
  dependency problems of version 3.4.2-1ubuntu3

Status in libffi package in Ubuntu:
  Fix Released

Bug description:
  Have both libffi8ubuntu1:amd64 and libffi8ubuntu1:i386 installed
  previously. Got these after upgrading to 3.4.2-1ubuntu3

  dpkg: dependency problems prevent configuration of libffi8:amd64:
   libffi8:i386 (3.4.2-1ubuntu3) breaks libffi8ubuntu1 and is unpacked but not 
configured.
libffi8:amd64 (3.4.2-1ubuntu3) provides libffi8ubuntu1.

  dpkg: error processing package libffi8:amd64 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libffi8:i386:
   libffi8:amd64 (3.4.2-1ubuntu3) breaks libffi8ubuntu1 and is unpacked but not 
configured.
libffi8:i386 (3.4.2-1ubuntu3) provides libffi8ubuntu1.

  dpkg: error processing package libffi8:i386 (--configure):
   dependency problems - leaving unconfigured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943312/+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 1934199] Re: Switch from Livepatch service to UA client

2021-09-28 Thread Robert Ancell

I had a WIP branch done as part of the ESM work. That's now been
rescheduled to April 2022, and the Livepatch migration will be done as
part of that.

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

Title:
  Switch from Livepatch service to UA client

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Hirsute:
  Won't Fix
Status in software-properties source package in Impish:
  Won't Fix

Bug description:
  software-properties currently uses a HTTP over Unix domain socket
  service from the livepatch snap to get the status and enable/disable
  it. This service is being deprecated with the 'ua' command line tool
  now providing this functionality. software-properties also installed
  the snap to gain access to this service. This is no longer required as
  the 'ua' tool does this.

  (*) The Livepatch service is a HTTP over Unix domain service running
  on livepatchd.sock inside the livepatch snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+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 1943312] Re: dependency problems of version 3.4.2-1ubuntu3

2021-09-28 Thread Diego Romero

hey, can I upgrade or not? Last time I updated, I broke my system and
had to reinstall, and now someone has already tested if you can upgrade
without breaking the system? This bug has been affecting me for a long
time and it's been bothering me .. No matter that I change the update
settings to update normal (not under development) partial updates keep
appearing, has any developer been able to fix this problem? And if you
did, what sequence of commands should we use to fix these broken
updates?

** Attachment added: "Captura de tela de 2021-09-28 17-51-24.png"
   
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943312/+attachment/5528790/+files/Captura%20de%20tela%20de%202021-09-28%2017-51-24.png

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

Title:
  dependency problems of version 3.4.2-1ubuntu3

Status in libffi package in Ubuntu:
  Fix Released

Bug description:
  Have both libffi8ubuntu1:amd64 and libffi8ubuntu1:i386 installed
  previously. Got these after upgrading to 3.4.2-1ubuntu3

  dpkg: dependency problems prevent configuration of libffi8:amd64:
   libffi8:i386 (3.4.2-1ubuntu3) breaks libffi8ubuntu1 and is unpacked but not 
configured.
libffi8:amd64 (3.4.2-1ubuntu3) provides libffi8ubuntu1.

  dpkg: error processing package libffi8:amd64 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libffi8:i386:
   libffi8:amd64 (3.4.2-1ubuntu3) breaks libffi8ubuntu1 and is unpacked but not 
configured.
libffi8:i386 (3.4.2-1ubuntu3) provides libffi8ubuntu1.

  dpkg: error processing package libffi8:i386 (--configure):
   dependency problems - leaving unconfigured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943312/+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 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

2021-09-28 Thread Seth Arnold

Worked for me on my daily workstation:

⏚ [sarnold:~/trees] 100 $ sudo apt install -tfocal-proposed libpam0g 
libpam-runtime libpam-modules-bin libpam-modules
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Recommended packages:
  update-motd
The following packages will be upgraded:
  libpam-modules libpam-modules-bin libpam-runtime libpam0g
4 upgraded, 0 newly installed, 0 to remove and 50 not upgraded.
Need to get 394 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://192.168.0.27/ubuntu focal-proposed/main amd64 libpam0g amd64 
1.3.1-5ubuntu4.3 [55.4 kB]
Get:2 http://192.168.0.27/ubuntu focal-proposed/main amd64 libpam-modules-bin 
amd64 1.3.1-5ubuntu4.3 [41.2 kB]
Get:3 http://192.168.0.27/ubuntu focal-proposed/main amd64 libpam-modules amd64 
1.3.1-5ubuntu4.3 [260 kB]
Get:4 http://192.168.0.27/ubuntu focal-proposed/main amd64 libpam-runtime all 
1.3.1-5ubuntu4.3 [37.3 kB]
Fetched 394 kB in 0s (10.6 MB/s)  
Preconfiguring packages ...
(Reading database ... 233861 files and directories currently installed.)
Preparing to unpack .../libpam0g_1.3.1-5ubuntu4.3_amd64.deb ...
Unpacking libpam0g:amd64 (1.3.1-5ubuntu4.3) over (1.3.1-5ubuntu4.2) ...
Setting up libpam0g:amd64 (1.3.1-5ubuntu4.3) ...
(Reading database ... 233861 files and directories currently installed.)
Preparing to unpack .../libpam-modules-bin_1.3.1-5ubuntu4.3_amd64.deb ...
Unpacking libpam-modules-bin (1.3.1-5ubuntu4.3) over (1.3.1-5ubuntu4.2) ...
Setting up libpam-modules-bin (1.3.1-5ubuntu4.3) ...
(Reading database ... 233861 files and directories currently installed.)
Preparing to unpack .../libpam-modules_1.3.1-5ubuntu4.3_amd64.deb ...
Unpacking libpam-modules:amd64 (1.3.1-5ubuntu4.3) over (1.3.1-5ubuntu4.2) ...
Setting up libpam-modules:amd64 (1.3.1-5ubuntu4.3) ...
(Reading database ... 233861 files and directories currently installed.)
Preparing to unpack .../libpam-runtime_1.3.1-5ubuntu4.3_all.deb ...
Unpacking libpam-runtime (1.3.1-5ubuntu4.3) over (1.3.1-5ubuntu4.2) ...
Setting up libpam-runtime (1.3.1-5ubuntu4.3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.31-0ubuntu9.2) ...
⏚ [sarnold:~/trees] 7s $ sudo -k ; sudo ls 
[sudo] password for sarnold: 
...

recent journal entries:
Sep 28 20:24:43 millbarge sudo[540916]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
Sep 28 20:24:45 millbarge sudo[540916]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory

and journal entries from an authentication performed after installing
the update:

Sep 28 20:27:14 millbarge audit[548532]: SYSCALL arch=c03e syscall=59 
success=yes exit=0 a0=55bfed873130 a1=55bfed6fa4f0 a2=55bfed8b1910 a3=8 items=2 
ppid=19448 pid=548532 auid=1000 uid=1000 gid=1000 euid=0 suid=0 fsuid=0 
egid=1000 sgid=1000 fsgid=1000 tty=pts2 ses=4 comm="sudo" exe="/usr/bin/sudo" 
key="execpriv"
Sep 28 20:27:14 millbarge audit: EXECVE argc=2 a0="sudo" a1="-k"
Sep 28 20:27:14 millbarge audit: CWD cwd="/home/sarnold/trees"
Sep 28 20:27:14 millbarge audit: PATH item=0 name="/usr/bin/sudo" inode=814680 
dev=00:1c mode=0104755 ouid=0 ogid=0 rdev=00:00 nametype=NORMAL cap_fp=0 
cap_fi=0 cap_fe=0 cap_fver=0 cap_frootid=0
Sep 28 20:27:14 millbarge audit: PATH item=1 name="/lib64/ld-linux-x86-64.so.2" 
inode=452898 dev=00:1c mode=0100755 ouid=0 ogid=0 rdev=00:00 nametype=NORMAL 
cap_fp=0 cap_fi=0 cap_fe=0 cap_fver=0 cap_frootid=0
Sep 28 20:27:14 millbarge audit: PROCTITLE proctitle=7375646F002D6B
Sep 28 20:27:14 millbarge audit[548533]: SYSCALL arch=c03e syscall=59 
success=yes exit=0 a0=55bfed6ddf40 a1=55bfed727b00 a2=55bfed8b1910 a3=8 items=2 
ppid=19448 pid=548533 auid=1000 uid=1000 gid=1000 euid=0 suid=0 fsuid=0 
egid=1000 sgid=1000 fsgid=1000 tty=pts2 ses=4 comm="sudo" exe="/usr/bin/sudo" 
key="execpriv"
Sep 28 20:27:14 millbarge audit: EXECVE argc=2 a0="sudo" a1="ls"
Sep 28 20:27:14 millbarge audit: CWD cwd="/home/sarnold/trees"
Sep 28 20:27:14 millbarge audit: PATH item=0 name="/usr/bin/sudo" inode=814680 
dev=00:1c mode=0104755 ouid=0 ogid=0 rdev=00:00 nametype=NORMAL cap_fp=0 
cap_fi=0 cap_fe=0 cap_fver=0 cap_frootid=0
Sep 28 20:27:14 millbarge audit: PATH item=1 name="/lib64/ld-linux-x86-64.so.2" 
inode=452898 dev=00:1c mode=0100755 ouid=0 ogid=0 rdev=00:00 nametype=NORMAL 
cap_fp=0 cap_fi=0 cap_fe=0 cap_fver=0 cap_frootid=0
Sep 28 20:27:14 millbarge audit: PROCTITLE proctitle=7375646F006C73
Sep 28 20:27:17 millbarge audit[548533]: USER_AUTH pid=548533 uid=1000 
auid=1000 ses=4 msg='op=PAM:authentication grantors=pam_permit,pam_cap 
acct="sarnold" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 
res=success'
Sep 28 20:27:17 millbarge audit[548533]: USER_ACCT pid=548533 uid=1000 
auid=1000 ses=4 msg='op=PAM:accounting grantors=pam_permit acct="sarnold" 
exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Sep 28 20:27:17 millbarge sudo[548533]:  sarnold

[Touch-packages] [Bug 1945367] [NEW] Xorg crash with Nvidia drivers after installation

2021-09-28 Thread j l h

Public bug reported:

i open a second bug report because i have already freeze problem after the 
installation of nvidia drivers and reboot.
Freeze become generally when i am using firefox and visioning a video with 
youtube.
I specify that since the last bug report, i re install ubuntu with official 
.iso without other package non official.
To create the report, i have to connect to the PC from another one with ssh.
When i use ubuntu-bug, it is not possible to join nvidia-bug-report because the 
application dont give me the hand to finish the report.
When i try to execute nvidia-bug-report, i have the same thing.

To use the PC, i have to use nouveau drivers and intel Xe GPU with poor
performances ...

Thanks for help.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.63.01  Tue Aug  3 20:44:16 
UTC 2021
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
Date: Tue Sep 28 21:13:05 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed
 virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
 virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:2090]
 NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Intel Corporation Device [8086:2090]
InstallationDate: Installed on 2021-09-26 (1 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: Intel(R) Client Systems NUC11PHi7
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=24658b6f-3e37-4376-bc2e-2207e961c9c8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/07/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: PHTGL579.0063.2021.0707.1057
dmi.board.name: NUC11PHBi7
dmi.board.vendor: Intel Corporation
dmi.board.version: M26151-402
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 12.19
dmi.modalias: 
dmi:bvnIntelCorp.:bvrPHTGL579.0063.2021.0707.1057:bd07/07/2021:br5.19:efr12.19:svnIntel(R)ClientSystems:pnNUC11PHi7:pvrM26149-403:skuSWNUC11PHKi7C00:rvnIntelCorporation:rnNUC11PHBi7:rvrM26151-402:cvnIntelCorporation:ct35:cvr2.0:
dmi.product.family: PH
dmi.product.name: NUC11PHi7
dmi.product.sku: SWNUC11PHKi7C00
dmi.product.version: M26149-403
dmi.sys.vendor: Intel(R) Client Systems
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~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 crash focal ubuntu

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

Title:
  Xorg crash with Nvidia drivers after installation

Status in xorg package in Ubuntu:
  New

Bug description:
  i open a second bug report because i have already freeze problem after the 
installation of nvidia drivers and reboot.
  Freeze become generally when i am using firefox and visioning a video with 
youtube.
  I specify that since the last bug report, i re install ubuntu with official 
.iso without other package non official.
  To create the report, i have to connect to the PC from another one with ssh.
  When i use

[Touch-packages] [Bug 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

2021-09-28 Thread Simon Déziel

It works:

# witness the original bug while running `sudo -i` in another session:
sdeziel@xeon:~$ tail -f /var/log/auth.log | grep pam
Sep 28 16:56:52 xeon sudo: pam_unix(sudo:auth): Couldn't open /etc/securetty: 
No such file or directory
Sep 28 16:56:53 xeon sudo: pam_unix(sudo:session): session opened for user root 
by (uid=0)

# install from -proposed:
root@xeon:~# apt-get install libpam0g libpam-runtime libpam-modules-bin 
libpam-modules
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Suggested packages:
   libpam-doc (1.3.1-5ubuntu4.3)
Recommended packages:
   update-motd (3.6-0ubuntu6.1)
The following packages will be upgraded:
   libpam-modules (1.3.1-5ubuntu4.2 => 1.3.1-5ubuntu4.3)
   libpam-modules-bin (1.3.1-5ubuntu4.2 => 1.3.1-5ubuntu4.3)
   libpam-runtime (1.3.1-5ubuntu4.2 => 1.3.1-5ubuntu4.3)
   libpam0g (1.3.1-5ubuntu4.2 => 1.3.1-5ubuntu4.3)
4 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 394 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 libpam0g 
amd64 1.3.1-5ubuntu4.3 [55.4 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
libpam-modules-bin amd64 1.3.1-5ubuntu4.3 [41.2 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
libpam-modules amd64 1.3.1-5ubuntu4.3 [260 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
libpam-runtime all 1.3.1-5ubuntu4.3 [37.3 kB]
Fetched 394 kB in 1s (477 kB/s)  
Preconfiguring packages ...
(Reading database ... 53805 files and directories currently installed.)
Preparing to unpack .../libpam0g_1.3.1-5ubuntu4.3_amd64.deb ...
Unpacking libpam0g:amd64 (1.3.1-5ubuntu4.3) over (1.3.1-5ubuntu4.2) ...
Setting up libpam0g:amd64 (1.3.1-5ubuntu4.3) ...
(Reading database ... 53805 files and directories currently installed.)
Preparing to unpack .../libpam-modules-bin_1.3.1-5ubuntu4.3_amd64.deb ...
Unpacking libpam-modules-bin (1.3.1-5ubuntu4.3) over (1.3.1-5ubuntu4.2) ...
Setting up libpam-modules-bin (1.3.1-5ubuntu4.3) ...
(Reading database ... 53805 files and directories currently installed.)
Preparing to unpack .../libpam-modules_1.3.1-5ubuntu4.3_amd64.deb ...
Unpacking libpam-modules:amd64 (1.3.1-5ubuntu4.3) over (1.3.1-5ubuntu4.2) ...
Setting up libpam-modules:amd64 (1.3.1-5ubuntu4.3) ...
(Reading database ... 53805 files and directories currently installed.)
Preparing to unpack .../libpam-runtime_1.3.1-5ubuntu4.3_all.deb ...
Unpacking libpam-runtime (1.3.1-5ubuntu4.3) over (1.3.1-5ubuntu4.2) ...
Setting up libpam-runtime (1.3.1-5ubuntu4.3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.31-0ubuntu9.3) ...
...

# confirm the fix by opening another session with `sudo -i`:
sdeziel@xeon:~$ tail -f /var/log/auth.log | grep pam
Sep 28 18:28:51 xeon sudo: pam_unix(sudo:session): session opened for user root 
by (uid=0)

** 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 pam in Ubuntu.
https://bugs.launchpad.net/bugs/1860826

Title:
  pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
  directory

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Focal:
  Fix Committed
Status in pam source package in Groovy:
  Won't Fix
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]
  Removal of the /etc/securetty file from the system results in useless log 
messages whenever pam_unix is invoked, which for some systems is quite a lot of 
logging. /etc/securetty is not coming back, and this is not an error.

  [Test Plan]
  1. Run 'sudo -s'.  Confirm that 'journalctl | grep sudo.*securetty' returns a 
line 'sudo[...]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such 
file or directory'.
  2. Install libpam-modules update from -proposed.
  3. Confirm that 'grep nullok_secure' /etc/pam.d/common-auth returns no lines.
  4. Run 'sudo -k'.
  5. Run 'sudo -s' again.
  6. Confirm that sudo succeeds and gives you a root shell.
  7. Confirm that 'journalctl | grep sudo.*securetty' does not show any new 
lines.

  [Where problems could occur]
  PAM is a sensitive package because it's used in all authentication operations 
on the system.  A bug here could render a user unable to log in to their system.

  Risks are mitigated by:
  - including a patch that treats the obsolete 'nullok_secure' as an alias for 
'nullok' to ensure any user-edited configurations continue to work rather than 
throwing errors about unknown options
  - editing the system-managed /etc/pam.d/common-auth config to use 'nullok' 
instead of 'nullok_secure' for future compatibility.

  Because we are editing the system config, this could also cause issues
  on future upgrades with

Re: [Touch-packages] [Bug 1944606] Re: [EDIFIER X3 R, recording] Microphone is not detected as an audio input

2021-09-28 Thread Amanda Arenales

I tried it, but it didn't work. It goes back to A2DP by itself

Em seg., 27 de set. de 2021 às 23:30, Hui Wang <1944...@bugs.launchpad.net>
escreveu:

> If so, please select hsp/hfp from configuration, the A2DP only has
> output.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1944606
>
> Title:
>   [EDIFIER X3 R, recording] Microphone is not detected as an audio input
>
> Status in alsa-driver package in Ubuntu:
>   New
>
> Bug description:
>   Device doesn't appear in the input options inside gnome sound
>   controls. It appears in pavucontrol, but there is no port associated
>   to it, and no sound is captured.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
>   Uname: Linux 5.11.0-34-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.20
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  amanda 2204 F pulseaudio
>   CasperMD5CheckResult: skip
>   CurrentDesktop: Unity
>   Date: Wed Sep 22 14:46:42 2021
>   InstallationDate: Installed on 2021-09-09 (13 days ago)
>   InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
> (20210819)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_Card: EDIFIER X3 R
>   Symptom_Type: None of the above
>   Title: [EDIFIER X3 R, recording] Recording problem
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 03/30/2021
>   dmi.bios.release: 1.4
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.4.1
>   dmi.board.name: 0TMFFT
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.4.1:bd03/30/2021:br1.4:svnDellInc.:pnVostro5402:pvr:sku0A03:rvnDellInc.:rn0TMFFT:rvrA00:cvnDellInc.:ct10:cvr:
>   dmi.product.family: Vostro
>   dmi.product.name: Vostro 5402
>   dmi.product.sku: 0A03
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1944606/+subscriptions
>
>

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

Title:
  [EDIFIER X3 R, recording] Microphone is not detected as an audio input

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Device doesn't appear in the input options inside gnome sound
  controls. It appears in pavucontrol, but there is no port associated
  to it, and no sound is captured.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amanda 2204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity
  Date: Wed Sep 22 14:46:42 2021
  InstallationDate: Installed on 2021-09-09 (13 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: EDIFIER X3 R
  Symptom_Type: None of the above
  Title: [EDIFIER X3 R, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0TMFFT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd03/30/2021:br1.4:svnDellInc.:pnVostro5402:pvr:sku0A03:rvnDellInc.:rn0TMFFT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5402
  dmi.product.sku: 0A03
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1944606/+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 1945235] Re: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from transport_put() from hfp_rfcomm_handle()

2021-09-28 Thread Igor V. Kovalenko

This could be a problem in pulseaudio native backend, provoked by
numerous reconnections between bluez and headset.

If verbose log from pulseaudio daemon can be collected for this crash, I
think it is worth to file an issue in pulseaudio tracker here
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/ with
verbose log attached.

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

Title:
  pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from
  transport_put() from hfp_rfcomm_handle()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3f255341dbcb4f57cf88d6fc2bed25ae18a760fe

  ---

  have headphones bluetooth
  bluetooth connect and disconnect if i turn off sound

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  duncan20876 F pulseaudio
   /dev/snd/controlC0:  duncan20876 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Mon Sep 27 21:06:47 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-13 (14 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_bluetooth_transport_put () at 
/usr/lib/pulse-15.0+dfsg1/modules/libbluez5-util.so
   () at /usr/lib/pulse-15.0+dfsg1/modules/libbluez5-util.so
   pa_mainloop_dispatch () at /lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_iterate () at /lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_run () at /lib/x86_64-linux-gnu/libpulse.so.0
  Title: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/21/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1945235/+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 1923845] Re: Please compress packages with zstd by default

** Merge proposal linked:
   
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/python-debian/+git/python-debian/+merge/407413

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz=1=1
  https://codesearch.debian.net/search?q=control.tar.xz=1=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
  apt - seems fixed already
  ceph- not affected in Ubuntu's version
  circlator   - not affected, just test data
  cowdancer   - not affected, just documentation
  eccodes - skip, just orig-data.tar.xz
  eckit   - skip, just

[Touch-packages] [Bug 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

2021-09-28 Thread Brian Murray

Hello Seth, or anyone else affected,

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

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

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

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

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

** Changed in: pam (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
  directory

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Focal:
  Fix Committed
Status in pam source package in Groovy:
  Won't Fix
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]
  Removal of the /etc/securetty file from the system results in useless log 
messages whenever pam_unix is invoked, which for some systems is quite a lot of 
logging. /etc/securetty is not coming back, and this is not an error.

  [Test Plan]
  1. Run 'sudo -s'.  Confirm that 'journalctl | grep sudo.*securetty' returns a 
line 'sudo[...]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such 
file or directory'.
  2. Install libpam-modules update from -proposed.
  3. Confirm that 'grep nullok_secure' /etc/pam.d/common-auth returns no lines.
  4. Run 'sudo -k'.
  5. Run 'sudo -s' again.
  6. Confirm that sudo succeeds and gives you a root shell.
  7. Confirm that 'journalctl | grep sudo.*securetty' does not show any new 
lines.

  [Where problems could occur]
  PAM is a sensitive package because it's used in all authentication operations 
on the system.  A bug here could render a user unable to log in to their system.

  Risks are mitigated by:
  - including a patch that treats the obsolete 'nullok_secure' as an alias for 
'nullok' to ensure any user-edited configurations continue to work rather than 
throwing errors about unknown options
  - editing the system-managed /etc/pam.d/common-auth config to use 'nullok' 
instead of 'nullok_secure' for future compatibility.

  Because we are editing the system config, this could also cause issues
  on future upgrades with undesirable prompts to the user.  However, the
  maintainer scripts are not meant to prompt on changes to the pam-
  config, and this code has been in Debian for a while with no reports
  of problems.

  
  [Original description]
  Hello, after upgrading to focal I found the following in my journalctl output:

  Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory

  The login package stopped packaging this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
  and now forcibly removes the file:
  https://paste.ubuntu.com/p/myh9cGWrHD/

  However, the pam package's pam_unix.so module has not yet been adapted to 
ignore this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Fri Jan 24 23:35:33 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pam
  UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

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


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

[Touch-packages] [Bug 1945205] Re: [FFe] Add zstd support

2021-09-28 Thread Steve Langasek

>From my perspective, this is a bugfix, not a new feature, since it's
required to maintain compatibility with current .deb packages as shipped
in the corresponding Ubuntu release.

** Changed in: python-debian (Ubuntu)
   Status: New => Confirmed

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

Title:
   [FFe] Add zstd support

Status in python-debian package in Ubuntu:
  Confirmed

Bug description:
  [Feature Freeze Exception]

  Now that dpkg-deb defaults to compressing with zstd, python-debian can
  no longer decompress the compressed data into the binary package
  archive [1].

  The proposed change, created as an MP at [2], introduces zstd support
  to python-debian 0.1.39 by adding a dependency to zstd to the package
  and by extending the python-debian xz support for python < 3.3, where
  xz was still not supported by tarfile, to also support the zstd
  compression.

  It is also important to note that, for python-debian 0.1.40, the
  relevant (here patched) code was re-worked (python < 3.3 support was
  dropped) and this proposed patch, along with the relevant proposed
  unit test, will need to be re-written. This re-writing effort is
  already an ongoing work proposed upstream in [3].

  Once [3] is merged, this patch can be dropped and python-debian can be
  sync'd from upstream again. If there is a need to merge python-debian
  before [3] is accepted and released upstream, the next version of
  python-debian will need to drop the proposed patch and apply [3]
  instead, for the reasons listed above.

  While python-debian is not completely broken without this FFe patch,
  some of its features will not work properly on Ubuntu packages now
  they are compressed with zstd. For instance, any packages or scripts
  that try to use python-debian for extracting data from deb packages
  will no longer work. Namely, dh-cmake FTBFS when trying to decompress
  a deb package during its unit test run step [4].

  A PPA with the proposed fix is available at [5], along with the build
  logs.

  I ran the dep8 test suite locally with the following results:

autopkgtest [20:04:02]:  summary
python3-debian PASS

  I am also attaching the logs for installation, removal and upgrades of
  the patched package.

  [1] https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1923845
  [2] 
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/python-debian/+git/python-debian/+merge/407413
  [3] 
https://salsa.debian.org/python-debian-team/python-debian/-/merge_requests/65
  [4] 
https://launchpadlibrarian.net/552708462/buildlog_ubuntu-impish-amd64.dh-cmake_0.6.1_BUILDING.txt.gz
  [5] 
https://launchpad.net/~athos-ribeiro/+archive/ubuntu/lp-1923845-python-debian/+packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1945205/+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 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt

2021-09-28 Thread Martin Pitt

> I am in contact with Christian now, and hope to sort this out soon.

Sorry -- I meant Christian Kellner, bolt's upstream, not you :-)

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

Title:
  umockdev 0.16.3-1 breaks autopkgtest of bolt

Status in bolt package in Ubuntu:
  In Progress
Status in umockdev package in Ubuntu:
  Invalid
Status in umockdev package in Debian:
  Unknown

Bug description:
  The test of bolt fails with the new version due to a crash:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz

  ...
Trace/breakpoint trap (core dumped)

  The bolt test really uses umockdev, d/t/control has gir1.2-umockdev-1.0 and
  python3-dbusmock and the new version causes this.

  Retrying autopkgtest locally with no, all and just umockdev from proposed
  and it seems reproducible.
   - impish-release - works
   - impish-all-proposed - crashes
   - impish-release + umockdev+libc6 from proposed - crashes

  Repro:
  $ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power

  FYI:
  Downgrading to umockdev 0.16.2-1 in the same environment does not
  eliminate the issue. So it might happen at the bolt test-build time.

  Debian has the same issue in:
  https://ci.debian.net/data/autopkgtest/testing/amd64/b/bolt/15587717/log.gz

  The new mockdev fails to create /sys/bus which is requested by the test.
  From there the error path is what crashes, but the root cause is why we enter
  the error-path in the first place.

  One should be aware, this fail is "normal" if the environment is not mocked.
  Even in the good case the different calls with/without umockdev lead to
  exactly the same crash.
  # good
  $ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
  # same crash as the new version has with umockdev-wrapper
  $ gdb /usr/libexec/installed-tests/bolt/test-power

  This is based on ldpreload.
  $ cat /usr/bin/umockdev-wrapper
  #!/bin/sh
  # Wrapper program to preload the libumockdev library, so that test programs 
can
  # set $UMOCKDEV_DIR for redirecting sysfs and other queries to a test bed.
  exec env LD_PRELOAD=libumockdev-preload.so.0:$LD_PRELOAD "$@"

  Gut feeling: it seems the mocking no more happens, and due to that
  it runs into the non-mocked crash

  Debugging with that:
  $ pull-lp-source bolt
  $ cd bolt-0.9.1/tests
  $ gdb /usr/libexec/installed-tests/bolt/test-power
  (gdb) set environment LD_PRELOAD libumockdev-preload.so.0
  (gdb) b mock_sysfs_init
  (gdb) run

  With that we can see that while the crash is somewhere inside g_warning the
  reason is in the g_mkdir failing with the new umockdev.

  
  Good-case

  Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
  165   {
  (gdb) n
  171 ms->bed = umockdev_testbed_new ();
  (gdb) 
  [New Thread 0x76e65640 (LWP 11444)]
  # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
  # DEBUG: umockdev.vala:104: Created udev test bed /tmp/umockdev.RQBNA1
  172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
  (gdb) 
  [New Thread 0x76664640 (LWP 11445)]
  175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
  (gdb) 
  180 sys = umockdev_testbed_get_sys_dir (ms->bed);
  (gdb) 
  182 bus = g_build_filename (sys, "bus", NULL);
  (gdb) p sys
  $1 = 0x555b99a0 "/tmp/umockdev.RQBNA1/sys"
  (gdb) n
  183 r = g_mkdir (bus, 0744);
  (gdb) p bus
  $2 = 0x555be330 "/tmp/umockdev.RQBNA1/sys/bus"
  (gdb) n
  185 if (r < 0)
  (gdb) p r
  $3 = 0
  (gdb) n
  188 cls = g_build_filename (sys, "class", NULL);

  Bad-Case

  Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
  165   {
  (gdb) n
  171 ms->bed = umockdev_testbed_new ();
  (gdb) 
  [New Thread 0x76e65640 (LWP 17082)]
  # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
  # DEBUG: umockdev.vala:110: Created udev test bed /tmp/umockdev.TK2VA1
  172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
  (gdb) 
  [New Thread 0x76664640 (LWP 17083)]
  175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
  (gdb) 
  180 sys = umockdev_testbed_get_sys_dir (ms->bed);
  (gdb) 
  182 bus = g_build_filename (sys, "bus", NULL);
  (gdb) p sys
  $1 = 0x555a98b0 "/tmp/umockdev.TK2VA1/sys"
  (gdb) n
  183 r = g_mkdir (bus, 0744);
  (gdb) p bus
  $2 = 0x555be560 "/tmp/umockdev.TK2VA1/sys/bus"
  (gdb) n
  185 if (r < 0)
  (gdb) p r
  $3 = -1
  (gdb) n
  186   g_warning ("could not create %s", bus);
  (gdb) n

  ** (/usr/libexec/installed-tests/bolt/test-power:17078): WARNING **:
  15:11:06.614: could not create /tmp/umockdev.TK2VA1/sys/bus

  Thread 1 "test-power" received signal SIGTRAP, Trace/breakpoint trap.

[Touch-packages] [Bug 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt

2021-09-28 Thread Martin Pitt

Christian, as I write above I believe this really needs to be fixed in
bolt's tests. The umockdev change was a bug fix which bolt's tests
(incorrectly) worked around. So I hope you don't mind that I flipped the
affected package around? I am in contact with Christian now, and hope to
sort this out soon.

** Changed in: bolt (Ubuntu)
   Status: Invalid => In Progress

** Changed in: umockdev (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  umockdev 0.16.3-1 breaks autopkgtest of bolt

Status in bolt package in Ubuntu:
  In Progress
Status in umockdev package in Ubuntu:
  Invalid
Status in umockdev package in Debian:
  Unknown

Bug description:
  The test of bolt fails with the new version due to a crash:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz

  ...
Trace/breakpoint trap (core dumped)

  The bolt test really uses umockdev, d/t/control has gir1.2-umockdev-1.0 and
  python3-dbusmock and the new version causes this.

  Retrying autopkgtest locally with no, all and just umockdev from proposed
  and it seems reproducible.
   - impish-release - works
   - impish-all-proposed - crashes
   - impish-release + umockdev+libc6 from proposed - crashes

  Repro:
  $ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power

  FYI:
  Downgrading to umockdev 0.16.2-1 in the same environment does not
  eliminate the issue. So it might happen at the bolt test-build time.

  Debian has the same issue in:
  https://ci.debian.net/data/autopkgtest/testing/amd64/b/bolt/15587717/log.gz

  The new mockdev fails to create /sys/bus which is requested by the test.
  From there the error path is what crashes, but the root cause is why we enter
  the error-path in the first place.

  One should be aware, this fail is "normal" if the environment is not mocked.
  Even in the good case the different calls with/without umockdev lead to
  exactly the same crash.
  # good
  $ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
  # same crash as the new version has with umockdev-wrapper
  $ gdb /usr/libexec/installed-tests/bolt/test-power

  This is based on ldpreload.
  $ cat /usr/bin/umockdev-wrapper
  #!/bin/sh
  # Wrapper program to preload the libumockdev library, so that test programs 
can
  # set $UMOCKDEV_DIR for redirecting sysfs and other queries to a test bed.
  exec env LD_PRELOAD=libumockdev-preload.so.0:$LD_PRELOAD "$@"

  Gut feeling: it seems the mocking no more happens, and due to that
  it runs into the non-mocked crash

  Debugging with that:
  $ pull-lp-source bolt
  $ cd bolt-0.9.1/tests
  $ gdb /usr/libexec/installed-tests/bolt/test-power
  (gdb) set environment LD_PRELOAD libumockdev-preload.so.0
  (gdb) b mock_sysfs_init
  (gdb) run

  With that we can see that while the crash is somewhere inside g_warning the
  reason is in the g_mkdir failing with the new umockdev.

  
  Good-case

  Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
  165   {
  (gdb) n
  171 ms->bed = umockdev_testbed_new ();
  (gdb) 
  [New Thread 0x76e65640 (LWP 11444)]
  # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
  # DEBUG: umockdev.vala:104: Created udev test bed /tmp/umockdev.RQBNA1
  172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
  (gdb) 
  [New Thread 0x76664640 (LWP 11445)]
  175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
  (gdb) 
  180 sys = umockdev_testbed_get_sys_dir (ms->bed);
  (gdb) 
  182 bus = g_build_filename (sys, "bus", NULL);
  (gdb) p sys
  $1 = 0x555b99a0 "/tmp/umockdev.RQBNA1/sys"
  (gdb) n
  183 r = g_mkdir (bus, 0744);
  (gdb) p bus
  $2 = 0x555be330 "/tmp/umockdev.RQBNA1/sys/bus"
  (gdb) n
  185 if (r < 0)
  (gdb) p r
  $3 = 0
  (gdb) n
  188 cls = g_build_filename (sys, "class", NULL);

  Bad-Case

  Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
  165   {
  (gdb) n
  171 ms->bed = umockdev_testbed_new ();
  (gdb) 
  [New Thread 0x76e65640 (LWP 17082)]
  # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
  # DEBUG: umockdev.vala:110: Created udev test bed /tmp/umockdev.TK2VA1
  172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
  (gdb) 
  [New Thread 0x76664640 (LWP 17083)]
  175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
  (gdb) 
  180 sys = umockdev_testbed_get_sys_dir (ms->bed);
  (gdb) 
  182 bus = g_build_filename (sys, "bus", NULL);
  (gdb) p sys
  $1 = 0x555a98b0 "/tmp/umockdev.TK2VA1/sys"
  (gdb) n
  183 r = g_mkdir (bus, 0744);
  (gdb) p bus
  $2 = 0x555be560 "/tmp/umockdev.TK2VA1/sys/bus"
  (gdb) n
  185 if (r < 0)

[Touch-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Fix Released

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

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

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  Fix Released

Bug description:
  SRU Justification for alsa-ucm-conf:

  [Impact]
  On the machines with the sof audio driver, users could adjust the input
  volume from UI, but this only adjusts the "Capture Volume",  the "Mic
  Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture
  Volume" to max, the recorded volume is still very low.

  [Fix]
  Backport a upstream patch, the patch adds the "Mic Boost" into the
  ucm

  [Test]
  plug a headset, make sure the headset-mic is the active input device,
  adjust the input volume to %20, open a terminal and run alsamixer,
  check the "Capture Volume" and "Mic Boost" value, then adjust the
  input volume to 80%, check those values and we could see both values
  are changed.

  [Where problems could occur]
  This patch could make the parse of input volume control fail, then
  the input volume can't be changed anymore when users adjust the
  volume from UI. But this possibility is very low, I tested this patch
  on many lenovo and dell machines with sof audio driver, all worked
  well.

  

  SRU Justification for pulseaudio:

  [Impact]
  On the machines with the sof audio driver, after booting up, the
  active output device is speaker by default, we adjust the output
  volume to 100%, then we plug a headphone, and adjust the output
  volume from 100% to 20%, now in theory, the speaker's volume is
  100%, the headphone's volume is 20%. We plugout the headphone,
  the active output device becomes speaker and we expect the volume
  changes to 100%, but the output volume for speaker is 20%.

  [Fix]
  Backport a upstream patch, this patch is already in the pulseaudio-15.0,
  so impish already has this fix. Only hirsute and focal need to backport
  this patch.

  [Test]
  adjust speaker's volume to 80%, then plug headphone and adjust headphone's
  volume to 20%, unplug the headphone, the speaker's volume becomes to 80%,
  plug the headphone, the headphone's volume becomes to 20%.

  [Where problems could occur]
  The patch writes the output volume to hardware immediately when switching
  output device on the machines with sof audio driver, this could introduce
  pop noise when changing the output device, but this possibility is very
  low, I tested the patch on many lenovo and dell machines with sof audio 
driver,
  all worked as expected and have no pop noise when switching output device.

  

  The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels
  with stable update already, but it is not merged to ubuntu 5.4.0
  kernel yet, so I sent this SRU for the focal kernel.

  [Impact]
  Users plug headphone and Mic to the audio jacks, but the system
  can't detect them, and couldn't output sound through headphone and
  record sound through Mic.

  [Fix]
  Backport a upstream patch, this will set the Mic to auto-detection
  mode and set the headphone to left location.

  [Test]
  Plug a headset to the headset audio jack, both headphone and mic
  could be detected. And output the sound to headphone, could hear
  the sound, record the sound through Mic, the sound could be recorded.

  [Where problems could occur]
  The patch is specific to Acer Aspire 5 machine, if it could introduce
  regression, it will make the audio like internal mic and internal spk
  stop working. But this possibility is very low.

  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect

[Touch-packages] [Bug 1934199] Re: Switch from Livepatch service to UA client

** Changed in: software-properties (Ubuntu Hirsute)
   Status: New => Won't Fix

** Changed in: software-properties (Ubuntu Bionic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: software-properties (Ubuntu Xenial)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Switch from Livepatch service to UA client

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Hirsute:
  Won't Fix
Status in software-properties source package in Impish:
  Won't Fix

Bug description:
  software-properties currently uses a HTTP over Unix domain socket
  service from the livepatch snap to get the status and enable/disable
  it. This service is being deprecated with the 'ua' command line tool
  now providing this functionality. software-properties also installed
  the snap to gain access to this service. This is no longer required as
  the 'ua' tool does this.

  (*) The Livepatch service is a HTTP over Unix domain service running
  on livepatchd.sock inside the livepatch snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+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 1945225] Re: udev produces unpredictable net names when PCI device is a bridge

** Merge proposal linked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/409304

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

Title:
  udev produces unpredictable net names when PCI device is a bridge

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  udev can produce unpredictable network interface names by default when 
multiple devices map to the same slot due to an intermediate bridge. On an 
Nvidia DGX2 system, I see the following when booting a system with udev 
245.4-4ubuntu3.13:

  ubuntu@akis:~$ ls /sys/class/net
  enp134s0f0  enp6s0  ens103  ens107  eth3  eth9
  enp134s0f1  ens102  ens106  eth1eth7  lo

  For each ens* device, there is a sibling eth* device that maps to the
  same slot because both devices are behind the same bridge.

  Unpredictable names present well known problems, but I'll describe a
  specific issue I'm having. We currently do automated network testing
  that MAAS deploys a system and then configures 2 specific NICs on the
  system. While MAAS does take care to always restore the names used
  during commissioning (eth3 will always be the same NIC on every
  deploy), these names can change each time the system is commissioned.
  So today we need to go in and edit the NIC names manually in MAAS any
  time the system is re-commissioned.

  [Test Case]
  Boot with kernel option net.naming-scheme=v247; verify that all network 
interfaces receive predictable names.

  [Fix]
  This issue was addressed upstream by adding a new v247 naming scheme that 
detects this scenario and disables usage of slot-based names for these devices. 
Obviously changing the default naming scheme in a released LTS series could 
break users. However, we could introduce the v247 scheme in a focal SRU, and 
keep the default scheme of v245 (via -Ddefault-net-naming-scheme=v245). Users 
impacted by this could then opt-in to the v247 scheme by passing 
net.naming-scheme=v247 or net.naming-scheme=latest on the kernel command line. 
I could add this to DGX2 systems via a kernel_opts MAAS tag to always get 
predictable names during commissioning.

  [Regression Risk]
  This would change the behavior of any users who select 
net.naming-scheme=latest, since the latest will now be v247 and not v245. I'm 
not sure why an existing Ubuntu user would be doing that though - AFAICT, 
Ubuntu currently always defaults to the latest scheme.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1945225/+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 1934199] Re: Switch from Livepatch service to UA client

2021-09-28 Thread Ken VanDine

@robert-ancell:  IIRC you had some code for this already?  Or am I
misremembering it?

** Changed in: software-properties (Ubuntu Focal)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Switch from Livepatch service to UA client

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Hirsute:
  New
Status in software-properties source package in Impish:
  Won't Fix

Bug description:
  software-properties currently uses a HTTP over Unix domain socket
  service from the livepatch snap to get the status and enable/disable
  it. This service is being deprecated with the 'ua' command line tool
  now providing this functionality. software-properties also installed
  the snap to gain access to this service. This is no longer required as
  the 'ua' tool does this.

  (*) The Livepatch service is a HTTP over Unix domain service running
  on livepatchd.sock inside the livepatch snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+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 1934199] Re: Switch from Livepatch service to UA client

it's not going to be ready for impish

** Changed in: software-properties (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  Switch from Livepatch service to UA client

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Hirsute:
  New
Status in software-properties source package in Impish:
  Won't Fix

Bug description:
  software-properties currently uses a HTTP over Unix domain socket
  service from the livepatch snap to get the status and enable/disable
  it. This service is being deprecated with the 'ua' command line tool
  now providing this functionality. software-properties also installed
  the snap to gain access to this service. This is no longer required as
  the 'ua' tool does this.

  (*) The Livepatch service is a HTTP over Unix domain service running
  on livepatchd.sock inside the livepatch snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+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 1931958] Re: 0~git20200629+e7aa92a-8 is FTFBS

** Changed in: libcamera (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  0~git20200629+e7aa92a-8 is FTFBS

Status in gstreamer1.0 package in Ubuntu:
  New
Status in libcamera package in Ubuntu:
  New

Bug description:
  Fails to build due to gstreamer using deprecated g_memdup:

  /usr/include/gstreamer-1.0/gst/base/gstbytereader.h: In function ‘guint8* 
gst_byte_reader_dup_data_unchecked(GstByteReader*, guint)’:
  /usr/include/gstreamer-1.0/gst/base/gstbytereader.h:365:41: error: ‘void* 
g_memdup(gconstpointer, guint)’ is deprecated: Use 'g_memdup2' instead 
[-Werror=deprecated-declarations]
365 |   return (guint8 *) g_memdup (data, size);
| ^
  In file included from /usr/include/glib-2.0/glib.h:82,
   from /usr/include/gstreamer-1.0/gst/gst.h:27,
   from ../src/gstreamer/gstlibcamerasrc.h:12,
   from ../src/gstreamer/gstlibcamerasrc.cpp:34:
  /usr/include/glib-2.0/glib/gstrfuncs.h:257:23: note: declared here
257 | gpointer  g_memdup (gconstpointer mem,

  Fixed in gstreamer upstream:
  
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/b16e96dd878e0c5e7baeb8fad62ca43de1f66982

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1931958/+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 1933828] Re: NTP servers from DHCP are not propagated to timesyncd

The bug is assigned and targetted to focal, it's import for the LTS but
we don't believe it should be a release issue for impish

** Tags removed: rls-ii-incoming
** Tags added: rls-ii-notfixing

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

Title:
  NTP servers from DHCP are not propagated to timesyncd

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Focal:
  New

Bug description:
  Network manager gets NTP servers from DHCP but do not update timesyncd to use 
it which keeps using ntp.ubuntu.com.
   
  This is a problem on private networks which do not have access to public 
internet. On this type of network the configuration of timesyncd must be 
updated manually instead of inheriting the conf from the dhcp servers.

  This can be integrated with a NM dispatcher script such as below:

  etc/NetworkManager/dispatcher.d/10-update-timesyncd for example:

  ==8<=8<=8<=8<=8<==
  #! /usr/bin/bash

  [ -n "$CONNECTION_UUID" ] || exit

  INTERFACE=$1
  ACTION=$2

  case $ACTION in
  up | dhcp4-change | dhcp6-change)
  [ -n "$DHCP4_NTP_SERVERS" ] || exit
  mkdir -p /etc/systemd/timesyncd.conf.d/
  cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  [Time]
  NTP=$DHCP4_NTP_SERVERS
  RootDistanceMaxSec=15
  EOF
  systemctl restart systemd-timesyncd
 ;;
  down)
  rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  systemctl restart systemd-timesyncd
  ;;
  esac
  ==8<=8<=8<=8<=8<==

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 28 14:08:52 2021
  InstallationDate: Installed on 2020-05-31 (393 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  RebootRequiredPkgs:
   linux-image-5.11.0-20-generic
   linux-base
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933828/+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 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt

Since Debian is also affected I filed it there as well:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995248

** Bug watch added: Debian Bug tracker #995248
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995248

** Also affects: umockdev (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995248
   Importance: Unknown
   Status: Unknown

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

Title:
  umockdev 0.16.3-1 breaks autopkgtest of bolt

Status in bolt package in Ubuntu:
  Invalid
Status in umockdev package in Ubuntu:
  In Progress
Status in umockdev package in Debian:
  Unknown

Bug description:
  The test of bolt fails with the new version due to a crash:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz

  ...
Trace/breakpoint trap (core dumped)

  The bolt test really uses umockdev, d/t/control has gir1.2-umockdev-1.0 and
  python3-dbusmock and the new version causes this.

  Retrying autopkgtest locally with no, all and just umockdev from proposed
  and it seems reproducible.
   - impish-release - works
   - impish-all-proposed - crashes
   - impish-release + umockdev+libc6 from proposed - crashes

  Repro:
  $ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power

  FYI:
  Downgrading to umockdev 0.16.2-1 in the same environment does not
  eliminate the issue. So it might happen at the bolt test-build time.

  Debian has the same issue in:
  https://ci.debian.net/data/autopkgtest/testing/amd64/b/bolt/15587717/log.gz

  The new mockdev fails to create /sys/bus which is requested by the test.
  From there the error path is what crashes, but the root cause is why we enter
  the error-path in the first place.

  One should be aware, this fail is "normal" if the environment is not mocked.
  Even in the good case the different calls with/without umockdev lead to
  exactly the same crash.
  # good
  $ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
  # same crash as the new version has with umockdev-wrapper
  $ gdb /usr/libexec/installed-tests/bolt/test-power

  This is based on ldpreload.
  $ cat /usr/bin/umockdev-wrapper
  #!/bin/sh
  # Wrapper program to preload the libumockdev library, so that test programs 
can
  # set $UMOCKDEV_DIR for redirecting sysfs and other queries to a test bed.
  exec env LD_PRELOAD=libumockdev-preload.so.0:$LD_PRELOAD "$@"

  Gut feeling: it seems the mocking no more happens, and due to that
  it runs into the non-mocked crash

  Debugging with that:
  $ pull-lp-source bolt
  $ cd bolt-0.9.1/tests
  $ gdb /usr/libexec/installed-tests/bolt/test-power
  (gdb) set environment LD_PRELOAD libumockdev-preload.so.0
  (gdb) b mock_sysfs_init
  (gdb) run

  With that we can see that while the crash is somewhere inside g_warning the
  reason is in the g_mkdir failing with the new umockdev.

  
  Good-case

  Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
  165   {
  (gdb) n
  171 ms->bed = umockdev_testbed_new ();
  (gdb) 
  [New Thread 0x76e65640 (LWP 11444)]
  # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
  # DEBUG: umockdev.vala:104: Created udev test bed /tmp/umockdev.RQBNA1
  172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
  (gdb) 
  [New Thread 0x76664640 (LWP 11445)]
  175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
  (gdb) 
  180 sys = umockdev_testbed_get_sys_dir (ms->bed);
  (gdb) 
  182 bus = g_build_filename (sys, "bus", NULL);
  (gdb) p sys
  $1 = 0x555b99a0 "/tmp/umockdev.RQBNA1/sys"
  (gdb) n
  183 r = g_mkdir (bus, 0744);
  (gdb) p bus
  $2 = 0x555be330 "/tmp/umockdev.RQBNA1/sys/bus"
  (gdb) n
  185 if (r < 0)
  (gdb) p r
  $3 = 0
  (gdb) n
  188 cls = g_build_filename (sys, "class", NULL);

  Bad-Case

  Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
  165   {
  (gdb) n
  171 ms->bed = umockdev_testbed_new ();
  (gdb) 
  [New Thread 0x76e65640 (LWP 17082)]
  # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
  # DEBUG: umockdev.vala:110: Created udev test bed /tmp/umockdev.TK2VA1
  172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
  (gdb) 
  [New Thread 0x76664640 (LWP 17083)]
  175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
  (gdb) 
  180 sys = umockdev_testbed_get_sys_dir (ms->bed);
  (gdb) 
  182 bus = g_build_filename (sys, "bus", NULL);
  (gdb) p sys
  $1 = 0x555a98b0 "/tmp/umockdev.TK2VA1/sys"
  (gdb) n
  183 r = g_mkdir (bus, 0744);
  (gdb) p bus
  $2 = 0x555be560 "/tmp/umockdev.TK2VA1/sys/bus"
  (gdb) n
  185 if (r < 0)
  (gdb) p r
  $3 = -1
  (gdb) n
  186   g_warning ("could not create %s",

[Touch-packages] [Bug 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt

** Changed in: bolt (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  umockdev 0.16.3-1 breaks autopkgtest of bolt

Status in bolt package in Ubuntu:
  Invalid
Status in umockdev package in Ubuntu:
  In Progress

Bug description:
  The test of bolt fails with the new version due to a crash:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz

  ...
Trace/breakpoint trap (core dumped)

  The bolt test really uses umockdev, d/t/control has gir1.2-umockdev-1.0 and
  python3-dbusmock and the new version causes this.

  Retrying autopkgtest locally with no, all and just umockdev from proposed
  and it seems reproducible.
   - impish-release - works
   - impish-all-proposed - crashes
   - impish-release + umockdev+libc6 from proposed - crashes

  Repro:
  $ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power

  FYI:
  Downgrading to umockdev 0.16.2-1 in the same environment does not
  eliminate the issue. So it might happen at the bolt test-build time.

  Debian has the same issue in:
  https://ci.debian.net/data/autopkgtest/testing/amd64/b/bolt/15587717/log.gz

  The new mockdev fails to create /sys/bus which is requested by the test.
  From there the error path is what crashes, but the root cause is why we enter
  the error-path in the first place.

  One should be aware, this fail is "normal" if the environment is not mocked.
  Even in the good case the different calls with/without umockdev lead to
  exactly the same crash.
  # good
  $ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
  # same crash as the new version has with umockdev-wrapper
  $ gdb /usr/libexec/installed-tests/bolt/test-power

  This is based on ldpreload.
  $ cat /usr/bin/umockdev-wrapper
  #!/bin/sh
  # Wrapper program to preload the libumockdev library, so that test programs 
can
  # set $UMOCKDEV_DIR for redirecting sysfs and other queries to a test bed.
  exec env LD_PRELOAD=libumockdev-preload.so.0:$LD_PRELOAD "$@"

  Gut feeling: it seems the mocking no more happens, and due to that
  it runs into the non-mocked crash

  Debugging with that:
  $ pull-lp-source bolt
  $ cd bolt-0.9.1/tests
  $ gdb /usr/libexec/installed-tests/bolt/test-power
  (gdb) set environment LD_PRELOAD libumockdev-preload.so.0
  (gdb) b mock_sysfs_init
  (gdb) run

  With that we can see that while the crash is somewhere inside g_warning the
  reason is in the g_mkdir failing with the new umockdev.

  
  Good-case

  Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
  165   {
  (gdb) n
  171 ms->bed = umockdev_testbed_new ();
  (gdb) 
  [New Thread 0x76e65640 (LWP 11444)]
  # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
  # DEBUG: umockdev.vala:104: Created udev test bed /tmp/umockdev.RQBNA1
  172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
  (gdb) 
  [New Thread 0x76664640 (LWP 11445)]
  175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
  (gdb) 
  180 sys = umockdev_testbed_get_sys_dir (ms->bed);
  (gdb) 
  182 bus = g_build_filename (sys, "bus", NULL);
  (gdb) p sys
  $1 = 0x555b99a0 "/tmp/umockdev.RQBNA1/sys"
  (gdb) n
  183 r = g_mkdir (bus, 0744);
  (gdb) p bus
  $2 = 0x555be330 "/tmp/umockdev.RQBNA1/sys/bus"
  (gdb) n
  185 if (r < 0)
  (gdb) p r
  $3 = 0
  (gdb) n
  188 cls = g_build_filename (sys, "class", NULL);

  Bad-Case

  Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
  165   {
  (gdb) n
  171 ms->bed = umockdev_testbed_new ();
  (gdb) 
  [New Thread 0x76e65640 (LWP 17082)]
  # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
  # DEBUG: umockdev.vala:110: Created udev test bed /tmp/umockdev.TK2VA1
  172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
  (gdb) 
  [New Thread 0x76664640 (LWP 17083)]
  175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
  (gdb) 
  180 sys = umockdev_testbed_get_sys_dir (ms->bed);
  (gdb) 
  182 bus = g_build_filename (sys, "bus", NULL);
  (gdb) p sys
  $1 = 0x555a98b0 "/tmp/umockdev.TK2VA1/sys"
  (gdb) n
  183 r = g_mkdir (bus, 0744);
  (gdb) p bus
  $2 = 0x555be560 "/tmp/umockdev.TK2VA1/sys/bus"
  (gdb) n
  185 if (r < 0)
  (gdb) p r
  $3 = -1
  (gdb) n
  186   g_warning ("could not create %s", bus);
  (gdb) n

  ** (/usr/libexec/installed-tests/bolt/test-power:17078): WARNING **:
  15:11:06.614: could not create /tmp/umockdev.TK2VA1/sys/bus

  Thread 1 "test-power" received signal SIGTRAP, Trace/breakpoint trap.

  
  I'll tag this update-excuse and FYI-subscribe Martin who has done the Debian 
upload and the Ubuntu sync of this on

[Touch-packages] [Bug 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt

Looking at the changelog this looks suspicious:
  - Immediately create "bus" and "class" directories in /sys to fix udev   
enumerator (thanks David Lechner)

That change is at
  
https://github.com/martinpitt/umockdev/commit/5e829601434610ef510bda12571291509a3a51d2

And that explains it, the bolt test code wants to create
/tmp/umockdev.RQBNA1/sys/bus and it already exists.

Offending code in bolt tests is at:
https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/tests/mock-sysfs.c#L183

Checking that theory in the debugger confirms that - breaking just prior
to the failing mkdir.

Good-case
183   r = g_mkdir (bus, 0744);
(gdb) p bus
$4 = 0x555be330 "/tmp/umockdev.P7PGA1/sys/bus"
(gdb) shell find /tmp/umockdev.P7PGA1/
/tmp/umockdev.P7PGA1/
/tmp/umockdev.P7PGA1/sys
/tmp/umockdev.P7PGA1/ioctl
/tmp/umockdev.P7PGA1/ioctl/_default

Bad-case
183   r = g_mkdir (bus, 0744);
(gdb) p bus
$4 = 0x555be560 "/tmp/umockdev.7MRGA1/sys/bus"
gdb) shell find /tmp/umockdev.7MRGA1/
/tmp/umockdev.7MRGA1/
/tmp/umockdev.7MRGA1/sys
/tmp/umockdev.7MRGA1/sys/bus
/tmp/umockdev.7MRGA1/sys/class
/tmp/umockdev.7MRGA1/ioctl
/tmp/umockdev.7MRGA1/ioctl/_default

So we either need to stop umockdev from doing that (but that will break
whatever it fixed to introduce this) OR we need to teach bolt tests to
be ok, if the directory already exists.

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

Title:
  umockdev 0.16.3-1 breaks autopkgtest of bolt

Status in bolt package in Ubuntu:
  Invalid
Status in umockdev package in Ubuntu:
  In Progress

Bug description:
  The test of bolt fails with the new version due to a crash:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz

  ...
Trace/breakpoint trap (core dumped)

  The bolt test really uses umockdev, d/t/control has gir1.2-umockdev-1.0 and
  python3-dbusmock and the new version causes this.

  Retrying autopkgtest locally with no, all and just umockdev from proposed
  and it seems reproducible.
   - impish-release - works
   - impish-all-proposed - crashes
   - impish-release + umockdev+libc6 from proposed - crashes

  Repro:
  $ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power

  FYI:
  Downgrading to umockdev 0.16.2-1 in the same environment does not
  eliminate the issue. So it might happen at the bolt test-build time.

  Debian has the same issue in:
  https://ci.debian.net/data/autopkgtest/testing/amd64/b/bolt/15587717/log.gz

  The new mockdev fails to create /sys/bus which is requested by the test.
  From there the error path is what crashes, but the root cause is why we enter
  the error-path in the first place.

  One should be aware, this fail is "normal" if the environment is not mocked.
  Even in the good case the different calls with/without umockdev lead to
  exactly the same crash.
  # good
  $ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
  # same crash as the new version has with umockdev-wrapper
  $ gdb /usr/libexec/installed-tests/bolt/test-power

  This is based on ldpreload.
  $ cat /usr/bin/umockdev-wrapper
  #!/bin/sh
  # Wrapper program to preload the libumockdev library, so that test programs 
can
  # set $UMOCKDEV_DIR for redirecting sysfs and other queries to a test bed.
  exec env LD_PRELOAD=libumockdev-preload.so.0:$LD_PRELOAD "$@"

  Gut feeling: it seems the mocking no more happens, and due to that
  it runs into the non-mocked crash

  Debugging with that:
  $ pull-lp-source bolt
  $ cd bolt-0.9.1/tests
  $ gdb /usr/libexec/installed-tests/bolt/test-power
  (gdb) set environment LD_PRELOAD libumockdev-preload.so.0
  (gdb) b mock_sysfs_init
  (gdb) run

  With that we can see that while the crash is somewhere inside g_warning the
  reason is in the g_mkdir failing with the new umockdev.

  
  Good-case

  Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
  165   {
  (gdb) n
  171 ms->bed = umockdev_testbed_new ();
  (gdb) 
  [New Thread 0x76e65640 (LWP 11444)]
  # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
  # DEBUG: umockdev.vala:104: Created udev test bed /tmp/umockdev.RQBNA1
  172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
  (gdb) 
  [New Thread 0x76664640 (LWP 11445)]
  175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
  (gdb) 
  180 sys = umockdev_testbed_get_sys_dir (ms->bed);
  (gdb) 
  182 bus = g_build_filename (sys, "bus", NULL);
  (gdb) p sys
  $1 = 0x555b99a0 "/tmp/umockdev.RQBNA1/sys"
  (gdb) n
  183 r = g_mkdir (bus, 0744);
  (gdb) p bus
  $2 = 0x555be330 "/tmp/umockdev.RQBNA1/sys/bus"
  (gdb) n
  185 if (r < 0)
  (gdb) p r
  $3 = 0
  (gdb) n
  188 cls = g_build_filename (sys, "class", NULL);

  Bad-Case

  Breakpoint 1, mock_sysfs_init

[Touch-packages] [Bug 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt

2021-09-28 Thread Martin Pitt

Thanks Christian -- Indeed I noticed that, and set
https://gitlab.freedesktop.org/bolt/bolt/-/merge_requests/246 the day
after to fix this. Unfortunately I didn't get a reaction yet, and
Christian also didn't respond on IRC yet. I'll do some more prodding.

** Changed in: bolt (Ubuntu)
   Status: New => In Progress

** Changed in: bolt (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

** Changed in: umockdev (Ubuntu)
   Status: New => In Progress

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

Title:
  umockdev 0.16.3-1 breaks autopkgtest of bolt

Status in bolt package in Ubuntu:
  Invalid
Status in umockdev package in Ubuntu:
  In Progress

Bug description:
  The test of bolt fails with the new version due to a crash:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz

  ...
Trace/breakpoint trap (core dumped)

  The bolt test really uses umockdev, d/t/control has gir1.2-umockdev-1.0 and
  python3-dbusmock and the new version causes this.

  Retrying autopkgtest locally with no, all and just umockdev from proposed
  and it seems reproducible.
   - impish-release - works
   - impish-all-proposed - crashes
   - impish-release + umockdev+libc6 from proposed - crashes

  Repro:
  $ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power

  FYI:
  Downgrading to umockdev 0.16.2-1 in the same environment does not
  eliminate the issue. So it might happen at the bolt test-build time.

  Debian has the same issue in:
  https://ci.debian.net/data/autopkgtest/testing/amd64/b/bolt/15587717/log.gz

  The new mockdev fails to create /sys/bus which is requested by the test.
  From there the error path is what crashes, but the root cause is why we enter
  the error-path in the first place.

  One should be aware, this fail is "normal" if the environment is not mocked.
  Even in the good case the different calls with/without umockdev lead to
  exactly the same crash.
  # good
  $ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
  # same crash as the new version has with umockdev-wrapper
  $ gdb /usr/libexec/installed-tests/bolt/test-power

  This is based on ldpreload.
  $ cat /usr/bin/umockdev-wrapper
  #!/bin/sh
  # Wrapper program to preload the libumockdev library, so that test programs 
can
  # set $UMOCKDEV_DIR for redirecting sysfs and other queries to a test bed.
  exec env LD_PRELOAD=libumockdev-preload.so.0:$LD_PRELOAD "$@"

  Gut feeling: it seems the mocking no more happens, and due to that
  it runs into the non-mocked crash

  Debugging with that:
  $ pull-lp-source bolt
  $ cd bolt-0.9.1/tests
  $ gdb /usr/libexec/installed-tests/bolt/test-power
  (gdb) set environment LD_PRELOAD libumockdev-preload.so.0
  (gdb) b mock_sysfs_init
  (gdb) run

  With that we can see that while the crash is somewhere inside g_warning the
  reason is in the g_mkdir failing with the new umockdev.

  
  Good-case

  Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
  165   {
  (gdb) n
  171 ms->bed = umockdev_testbed_new ();
  (gdb) 
  [New Thread 0x76e65640 (LWP 11444)]
  # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
  # DEBUG: umockdev.vala:104: Created udev test bed /tmp/umockdev.RQBNA1
  172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
  (gdb) 
  [New Thread 0x76664640 (LWP 11445)]
  175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
  (gdb) 
  180 sys = umockdev_testbed_get_sys_dir (ms->bed);
  (gdb) 
  182 bus = g_build_filename (sys, "bus", NULL);
  (gdb) p sys
  $1 = 0x555b99a0 "/tmp/umockdev.RQBNA1/sys"
  (gdb) n
  183 r = g_mkdir (bus, 0744);
  (gdb) p bus
  $2 = 0x555be330 "/tmp/umockdev.RQBNA1/sys/bus"
  (gdb) n
  185 if (r < 0)
  (gdb) p r
  $3 = 0
  (gdb) n
  188 cls = g_build_filename (sys, "class", NULL);

  Bad-Case

  Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
  165   {
  (gdb) n
  171 ms->bed = umockdev_testbed_new ();
  (gdb) 
  [New Thread 0x76e65640 (LWP 17082)]
  # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
  # DEBUG: umockdev.vala:110: Created udev test bed /tmp/umockdev.TK2VA1
  172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
  (gdb) 
  [New Thread 0x76664640 (LWP 17083)]
  175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
  (gdb) 
  180 sys = umockdev_testbed_get_sys_dir (ms->bed);
  (gdb) 
  182 bus = g_build_filename (sys, "bus", NULL);
  (gdb) p sys
  $1 = 0x555a98b0 "/tmp/umockdev.TK2VA1/sys"
  (gdb) n
  183 r = g_mkdir (bus, 0744);
  (gdb) p bus
  $2 = 0x555be560 "/tmp/umockdev.TK2VA1/sys/bus"
  (gdb) n
  185 if (r < 0)
  (gdb) p r
  $3 = -1

[Touch-packages] [Bug 1945321] [NEW] umockdev 0.16.3-1 breaks autopkgtest of bolt

Public bug reported:

The test of bolt fails with the new version due to a crash:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz

...
  Trace/breakpoint trap (core dumped)

The bolt test really uses umockdev, d/t/control has gir1.2-umockdev-1.0 and
python3-dbusmock and the new version causes this.

Retrying autopkgtest locally with no, all and just umockdev from proposed
and it seems reproducible.
 - impish-release - works
 - impish-all-proposed - crashes
 - impish-release + umockdev+libc6 from proposed - crashes

Repro:
$ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power

FYI:
Downgrading to umockdev 0.16.2-1 in the same environment does not
eliminate the issue. So it might happen at the bolt test-build time.

Debian has the same issue in:
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bolt/15587717/log.gz

The new mockdev fails to create /sys/bus which is requested by the test.
>From there the error path is what crashes, but the root cause is why we enter
the error-path in the first place.

One should be aware, this fail is "normal" if the environment is not mocked.
Even in the good case the different calls with/without umockdev lead to
exactly the same crash.
# good
$ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
# same crash as the new version has with umockdev-wrapper
$ gdb /usr/libexec/installed-tests/bolt/test-power

This is based on ldpreload.
$ cat /usr/bin/umockdev-wrapper
#!/bin/sh
# Wrapper program to preload the libumockdev library, so that test programs can
# set $UMOCKDEV_DIR for redirecting sysfs and other queries to a test bed.
exec env LD_PRELOAD=libumockdev-preload.so.0:$LD_PRELOAD "$@"

Gut feeling: it seems the mocking no more happens, and due to that
it runs into the non-mocked crash

Debugging with that:
$ pull-lp-source bolt
$ cd bolt-0.9.1/tests
$ gdb /usr/libexec/installed-tests/bolt/test-power
(gdb) set environment LD_PRELOAD libumockdev-preload.so.0
(gdb) b mock_sysfs_init
(gdb) run

With that we can see that while the crash is somewhere inside g_warning the
reason is in the g_mkdir failing with the new umockdev.


Good-case

Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
165 {
(gdb) n
171   ms->bed = umockdev_testbed_new ();
(gdb) 
[New Thread 0x76e65640 (LWP 11444)]
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
# DEBUG: umockdev.vala:104: Created udev test bed /tmp/umockdev.RQBNA1
172   ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
(gdb) 
[New Thread 0x76664640 (LWP 11445)]
175   ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
(gdb) 
180   sys = umockdev_testbed_get_sys_dir (ms->bed);
(gdb) 
182   bus = g_build_filename (sys, "bus", NULL);
(gdb) p sys
$1 = 0x555b99a0 "/tmp/umockdev.RQBNA1/sys"
(gdb) n
183   r = g_mkdir (bus, 0744);
(gdb) p bus
$2 = 0x555be330 "/tmp/umockdev.RQBNA1/sys/bus"
(gdb) n
185   if (r < 0)
(gdb) p r
$3 = 0
(gdb) n
188   cls = g_build_filename (sys, "class", NULL);

Bad-Case

Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
165 {
(gdb) n
171   ms->bed = umockdev_testbed_new ();
(gdb) 
[New Thread 0x76e65640 (LWP 17082)]
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used 
after threads are created
# DEBUG: umockdev.vala:110: Created udev test bed /tmp/umockdev.TK2VA1
172   ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
(gdb) 
[New Thread 0x76664640 (LWP 17083)]
175   ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
(gdb) 
180   sys = umockdev_testbed_get_sys_dir (ms->bed);
(gdb) 
182   bus = g_build_filename (sys, "bus", NULL);
(gdb) p sys
$1 = 0x555a98b0 "/tmp/umockdev.TK2VA1/sys"
(gdb) n
183   r = g_mkdir (bus, 0744);
(gdb) p bus
$2 = 0x555be560 "/tmp/umockdev.TK2VA1/sys/bus"
(gdb) n
185   if (r < 0)
(gdb) p r
$3 = -1
(gdb) n
186 g_warning ("could not create %s", bus);
(gdb) n

** (/usr/libexec/installed-tests/bolt/test-power:17078): WARNING **:
15:11:06.614: could not create /tmp/umockdev.TK2VA1/sys/bus

Thread 1 "test-power" received signal SIGTRAP, Trace/breakpoint trap.


I'll tag this update-excuse and FYI-subscribe Martin who has done the Debian 
upload and the Ubuntu sync of this on 16th Sept (post FF).

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

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


** Tags: update-excuse

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

** Summary changed:

- 0.16.3-1 breaks autopkgtest of bolt
+ umockdev 0.16.3-1 breaks autopkgtest of bolt

** Tags added: update-excuse

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-09-28 Thread Thomas Bechtold

** Changed in: livecd-rootfs (Ubuntu Hirsute)
 Assignee: (unassigned) => Thomas Bechtold (toabctl)

** Changed in: livecd-rootfs (Ubuntu Focal)
 Assignee: (unassigned) => Thomas Bechtold (toabctl)

** Changed in: livecd-rootfs (Ubuntu Bionic)
 Assignee: (unassigned) => Thomas Bechtold (toabctl)

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

Title:
  magic-proxy broke with iptables 1.8.7-1ubuntu2

Status in launchpad-buildd:
  Invalid
Status in iptables package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in iptables source package in Bionic:
  Invalid
Status in livecd-rootfs source package in Bionic:
  New
Status in lxd source package in Bionic:
  Invalid
Status in iptables source package in Focal:
  Invalid
Status in livecd-rootfs source package in Focal:
  New
Status in lxd source package in Focal:
  Invalid
Status in iptables source package in Hirsute:
  Invalid
Status in livecd-rootfs source package in Hirsute:
  New
Status in lxd source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  The fixes for this bug (including the fixes for LP:#1944906) need to be 
backported to hirsute, focal and bionic) to be able to re-enable  the 
"repo-snapshot-stamp" feature for image builds. That feature is important to 
get consistent image builds (means the same set of packages included in the 
different images) when doing multiple builds (eg. for AWS, Azure and GCE).

  [Test Plan]
  - build a livecd-rootfs image with the changes for every series in a PPA
  - Do build an image with the livecd-rootfs from the PPA and enable the 
repo-snapshot-stamp feature
  - Check that the build did not fail or hang

  [Where problems could occur]
  The codepath that will be changed is only executed in livecd-rootfs if the 
repo-snapshot-stamp feature is enabled. And that feature is currently broken so 
it shouldn't be enabled anywhere.

  [Original description]

  when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic
  proxy stopped working in livecd-rootfs.

  It does very simple thing:

  iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner
  daemon -j REDIRECT --to 8080

  inside hirsute lxd container, with quite high privileges, in a bionic
  VM, running 4.15 kernel.

  With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound
  connectivity the very first http networking command after the above
  call would just hang indefinitely.

  However, if one does this instead:

  iptables -vv -t nat -S
  iptables-legacy -vv -t nat -S
  iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon 
-j REDIRECT --to 8080

  somehow magically everything starts to work fine.

  weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-09-28 Thread Brian Murray

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

** Also affects: livecd-rootfs (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: iptables (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: livecd-rootfs (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: lxd (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: iptables (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: livecd-rootfs (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: lxd (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

Title:
  magic-proxy broke with iptables 1.8.7-1ubuntu2

Status in launchpad-buildd:
  Invalid
Status in iptables package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in iptables source package in Bionic:
  Invalid
Status in livecd-rootfs source package in Bionic:
  New
Status in lxd source package in Bionic:
  Invalid
Status in iptables source package in Focal:
  Invalid
Status in livecd-rootfs source package in Focal:
  New
Status in lxd source package in Focal:
  Invalid
Status in iptables source package in Hirsute:
  Invalid
Status in livecd-rootfs source package in Hirsute:
  New
Status in lxd source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  The fixes for this bug (including the fixes for LP:#1944906) need to be 
backported to hirsute, focal and bionic) to be able to re-enable  the 
"repo-snapshot-stamp" feature for image builds. That feature is important to 
get consistent image builds (means the same set of packages included in the 
different images) when doing multiple builds (eg. for AWS, Azure and GCE).

  [Test Plan]
  - build a livecd-rootfs image with the changes for every series in a PPA
  - Do build an image with the livecd-rootfs from the PPA and enable the 
repo-snapshot-stamp feature
  - Check that the build did not fail or hang

  [Where problems could occur]
  The codepath that will be changed is only executed in livecd-rootfs if the 
repo-snapshot-stamp feature is enabled. And that feature is currently broken so 
it shouldn't be enabled anywhere.

  [Original description]

  when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic
  proxy stopped working in livecd-rootfs.

  It does very simple thing:

  iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner
  daemon -j REDIRECT --to 8080

  inside hirsute lxd container, with quite high privileges, in a bionic
  VM, running 4.15 kernel.

  With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound
  connectivity the very first http networking command after the above
  call would just hang indefinitely.

  However, if one does this instead:

  iptables -vv -t nat -S
  iptables-legacy -vv -t nat -S
  iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon 
-j REDIRECT --to 8080

  somehow magically everything starts to work fine.

  weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1916931] Re: omshell returns inconsistent results or segfaults

2021-09-28 Thread Andrea

I confirm the bug on our environment with Ubuntu 20.04 and isc-dhcp-server 
4.4.1. 
Omshell randomly goes on segfault:
[Tue Sep 28 11:05:22 2021] omshell[4604]: segfault at 0 ip 55623cdd06dc sp 
7ffd5a2c7c78 error 4 in omshell[55623cd97000+45000]

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

Title:
  omshell returns inconsistent results or segfaults

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  I have just built a Ubuntu 20.04 server and installed isc-dhcp-server
  4.4.1 on it and I am seeing inconsistent returns from omshell. 
  Initially omshell returns data as expected, but when I exit and re-enter 
  omshell connections fail.

  Here is the initial, working, session:

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect
  obj: 
  > new failover-state
  obj: failover-state
  > set name = "dhcp-failover"
  obj: failover-state
  name = "dhcp-failover"
  > open
  obj: failover-state
  name = "dhcp-failover"
  partner-address = c0:9d:e9:76:e9:55:00:00
  partner-port = 00:00:02:07
  local-address = 10:9d:e9:76:e9:55:00:00
  local-port = 00:00:02:07
  max-outstanding-updates = 00:00:00:0a
  mclt = 00:00:01:2c
  load-balance-max-secs = 00:00:00:03
  load-balance-hba =
  
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
  partner-state = 00:00:00:02
  local-state = 00:00:00:02
  partner-stos = 60:36:d0:68
  local-stos = 60:36:8b:3b
  hierarchy = 00:00:00:01
  last-packet-sent = 00:00:00:00
  last-timestamp-received = 00:00:00:00
  skew = 00:00:00:00
  max-response-delay = 00:00:00:3c
  cur-unacked-updates = 00:00:00:00

  Here is what I see when the connect fails.  Well, just hangs really.

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect

  And then I hit ctrl-c to break out and tried again:

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect
  Segmentation fault (core dumped)

  Note, the peer to this server is still running Ubuntu 18.04 with
  isc-dhcp-server 4.3.5.  Running the exact same commands on the peer
  works reliably.  (They are using the same python script to drive
  omshell.)  The DHCP server on the new system appears to be working 
  just fine as reported by omshell on the peer and systemctl.

  I was curious if the problem could be with the mis-matched versions
  of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system
  and get the same results.

  I also tried using a python script with the pypureomapi module to
  try and determine if the problem was in omshell or the server.  I 
  got very similar results when I attempted to get information about
  the failover state of the server.  Interestingly interrogating
  the server about host information seems to work just fine.

  This is a critical bug since I don't see how to fail over a DHCP
  that is running the isc-dhcp-server on 20.04 without being able
  to issue omapi commands.

  I am attaching apport output to this bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-09-28 Thread Thomas Bechtold

** Description changed:

- [Why SRU?]
+ [Impact]
  The fixes for this bug (including the fixes for LP:#1944906) need to be 
backported to hirsute, focal and bionic) to be able to re-enable  the 
"repo-snapshot-stamp" feature for image builds. That feature is important to 
get consistent image builds (means the same set of packages included in the 
different images) when doing multiple builds (eg. for AWS, Azure and GCE).
  
  [Test Plan]
  - build a livecd-rootfs image with the changes for every series in a PPA
  - Do build an image with the livecd-rootfs from the PPA and enable the 
repo-snapshot-stamp feature
  - Check that the build did not fail or hang
  
  [Where problems could occur]
  The codepath that will be changed is only executed in livecd-rootfs if the 
repo-snapshot-stamp feature is enabled. And that feature is currently broken so 
it shouldn't be enabled anywhere.
- 
  
  [Original description]
  
  when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic
  proxy stopped working in livecd-rootfs.
  
  It does very simple thing:
  
  iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner
  daemon -j REDIRECT --to 8080
  
  inside hirsute lxd container, with quite high privileges, in a bionic
  VM, running 4.15 kernel.
  
  With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound
  connectivity the very first http networking command after the above call
  would just hang indefinitely.
  
  However, if one does this instead:
  
  iptables -vv -t nat -S
  iptables-legacy -vv -t nat -S
  iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon 
-j REDIRECT --to 8080
  
  somehow magically everything starts to work fine.
  
  weird.

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

Title:
  magic-proxy broke with iptables 1.8.7-1ubuntu2

Status in launchpad-buildd:
  Invalid
Status in iptables package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid

Bug description:
  [Impact]
  The fixes for this bug (including the fixes for LP:#1944906) need to be 
backported to hirsute, focal and bionic) to be able to re-enable  the 
"repo-snapshot-stamp" feature for image builds. That feature is important to 
get consistent image builds (means the same set of packages included in the 
different images) when doing multiple builds (eg. for AWS, Azure and GCE).

  [Test Plan]
  - build a livecd-rootfs image with the changes for every series in a PPA
  - Do build an image with the livecd-rootfs from the PPA and enable the 
repo-snapshot-stamp feature
  - Check that the build did not fail or hang

  [Where problems could occur]
  The codepath that will be changed is only executed in livecd-rootfs if the 
repo-snapshot-stamp feature is enabled. And that feature is currently broken so 
it shouldn't be enabled anywhere.

  [Original description]

  when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic
  proxy stopped working in livecd-rootfs.

  It does very simple thing:

  iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner
  daemon -j REDIRECT --to 8080

  inside hirsute lxd container, with quite high privileges, in a bionic
  VM, running 4.15 kernel.

  With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound
  connectivity the very first http networking command after the above
  call would just hang indefinitely.

  However, if one does this instead:

  iptables -vv -t nat -S
  iptables-legacy -vv -t nat -S
  iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon 
-j REDIRECT --to 8080

  somehow magically everything starts to work fine.

  weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-09-28 Thread Thomas Bechtold

** Description changed:

+ [Why SRU?]
+ The fixes for this bug (including the fixes for LP:#1944906) need to be 
backported to hirsute, focal and bionic) to be able to re-enable  the 
"repo-snapshot-stamp" feature for image builds. That feature is important to 
get consistent image builds (means the same set of packages included in the 
different images) when doing multiple builds (eg. for AWS, Azure and GCE).
+ 
+ [Test Plan]
+ - build a livecd-rootfs image with the changes for every series in a PPA
+ - Do build an image with the livecd-rootfs from the PPA and enable the 
repo-snapshot-stamp feature
+ - Check that the build did not fail or hang
+ 
+ [Where problems could occur]
+ The codepath that will be changed is only executed in livecd-rootfs if the 
repo-snapshot-stamp feature is enabled. And that feature is currently broken so 
it shouldn't be enabled anywhere.
+ 
+ 
+ [Original description]
+ 
  when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic
  proxy stopped working in livecd-rootfs.
  
  It does very simple thing:
  
  iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner
  daemon -j REDIRECT --to 8080
  
  inside hirsute lxd container, with quite high privileges, in a bionic
  VM, running 4.15 kernel.
  
  With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound
  connectivity the very first http networking command after the above call
  would just hang indefinitely.
  
  However, if one does this instead:
  
  iptables -vv -t nat -S
  iptables-legacy -vv -t nat -S
  iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon 
-j REDIRECT --to 8080
  
  somehow magically everything starts to work fine.
  
  weird.

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

Title:
  magic-proxy broke with iptables 1.8.7-1ubuntu2

Status in launchpad-buildd:
  Invalid
Status in iptables package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid

Bug description:
  [Why SRU?]
  The fixes for this bug (including the fixes for LP:#1944906) need to be 
backported to hirsute, focal and bionic) to be able to re-enable  the 
"repo-snapshot-stamp" feature for image builds. That feature is important to 
get consistent image builds (means the same set of packages included in the 
different images) when doing multiple builds (eg. for AWS, Azure and GCE).

  [Test Plan]
  - build a livecd-rootfs image with the changes for every series in a PPA
  - Do build an image with the livecd-rootfs from the PPA and enable the 
repo-snapshot-stamp feature
  - Check that the build did not fail or hang

  [Where problems could occur]
  The codepath that will be changed is only executed in livecd-rootfs if the 
repo-snapshot-stamp feature is enabled. And that feature is currently broken so 
it shouldn't be enabled anywhere.

  
  [Original description]

  when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic
  proxy stopped working in livecd-rootfs.

  It does very simple thing:

  iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner
  daemon -j REDIRECT --to 8080

  inside hirsute lxd container, with quite high privileges, in a bionic
  VM, running 4.15 kernel.

  With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound
  connectivity the very first http networking command after the above
  call would just hang indefinitely.

  However, if one does this instead:

  iptables -vv -t nat -S
  iptables-legacy -vv -t nat -S
  iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon 
-j REDIRECT --to 8080

  somehow magically everything starts to work fine.

  weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1945309] Re: Screen flickering on Ubuntu 20.04 - HP Spectre X360 with Intel Skylake GT2 [HD Graphics 520]

Thanks for the bug report. Please edit /etc/default/grub and change:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0"

and then run:

  sudo update-grub

and reboot.

Does that fix the problem?

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Screen flickering on Ubuntu 20.04 - HP Spectre X360 with Intel Skylake
  GT2 [HD Graphics 520]

Status in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 20.04.3 LTS on my HP Spectre X360 with Intel Skylake
  GT2 [HD Graphics 520] and I am having flickering graphics.

  The problem sometimes happens showing grey flickering boxes 5-6 times
  in a minute, and sometimes it does not happen for 2-3 minutes.
  Overall, it annoys me quite a lot.

  I have tried decreasing the refresh rate from 60Hz to lower options,
  but that didn't work. Updating the drivers or purging Intel graphics
  didn't work either. I also tried a couple of stuff I saw online
  regarding /etc/X11/xorg.conf.d/.

  I do not have this issue on Windows, therefore it must be Ubuntu-
  related.

  When I set nomodeset on GRUB and update it, flickering disappears, but
  at the cost of my brightness adjuster and Night Light.

  As for package I have:

  apt-cache policy pkgname
  N: Unable to locate package pkgname

  dpkg -l |grep xserver-xorg-core
  ii xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 amd64 Xorg X server - core 
server

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 28 11:55:47 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:804e]
  InstallationDate: Installed on 2021-09-22 (5 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic 
root=UUID=c68313b0-c9ba-4714-abc0-dff5762a92b2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
  Identifier  "Intel Graphics"
  Driver  "intel"
  Option  "TearFree""true"
   EndSection
  dmi.bios.date: 12/27/2019
  dmi.bios.release: 15.54
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.54
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 804E
  dmi.board.vendor: HP
  dmi.board.version: 33.24
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 33.24
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.54:bd12/27/2019:br15.54:efr33.24:svnHP:pnHPSpectrex360Convertible:pvr:skuN7H72EA#AB8:rvnHP:rn804E:rvr33.24:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible
  dmi.product.sku: N7H72EA#AB8
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-1028
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1945309/+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 1945309] [NEW] Screen flickering on Ubuntu 20.04 - HP Spectre X360 with Intel Skylake GT2 [HD Graphics 520]

2021-09-28 Thread Uyfar Us

Public bug reported:

I am using Ubuntu 20.04.3 LTS on my HP Spectre X360 with Intel Skylake
GT2 [HD Graphics 520] and I am having flickering graphics.

The problem sometimes happens showing grey flickering boxes 5-6 times in
a minute, and sometimes it does not happen for 2-3 minutes. Overall, it
annoys me quite a lot.

I have tried decreasing the refresh rate from 60Hz to lower options, but
that didn't work. Updating the drivers or purging Intel graphics didn't
work either. I also tried a couple of stuff I saw online regarding
/etc/X11/xorg.conf.d/.

I do not have this issue on Windows, therefore it must be Ubuntu-
related.

When I set nomodeset on GRUB and update it, flickering disappears, but
at the cost of my brightness adjuster and Night Light.

As for package I have:

apt-cache policy pkgname
N: Unable to locate package pkgname

dpkg -l |grep xserver-xorg-core
ii xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 amd64 Xorg X server - core 
server

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 28 11:55:47 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:804e]
InstallationDate: Installed on 2021-09-22 (5 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: HP HP Spectre x360 Convertible
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic 
root=UUID=c68313b0-c9ba-4714-abc0-dff5762a92b2 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf:
 Section "Device"
Identifier  "Intel Graphics"
Driver  "intel"
Option  "TearFree""true"
 EndSection
dmi.bios.date: 12/27/2019
dmi.bios.release: 15.54
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.54
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 804E
dmi.board.vendor: HP
dmi.board.version: 33.24
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 33.24
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.54:bd12/27/2019:br15.54:efr33.24:svnHP:pnHPSpectrex360Convertible:pvr:skuN7H72EA#AB8:rvnHP:rn804E:rvr33.24:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
dmi.product.name: HP Spectre x360 Convertible
dmi.product.sku: N7H72EA#AB8
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-1028
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~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: ubuntu
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug focal third-party-packages ubuntu

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

Title:
  Screen flickering on Ubuntu 20.04 - HP Spectre X360 with Intel Skylake
  GT2 [HD Graphics 520]

Status in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 20.04.3 LTS on my HP Spectre X360 with Intel Skylake
  GT2 [HD Graphics 520] and I am having flickering graphics.

  The problem sometimes happens showing grey flickering boxes 5-6 times
  in a minute, and sometimes it does not happen for 2-3 minutes.
  Overall, it annoys me quite a lot.

  I have tried decreasing the refresh rate from 60Hz to lower options,
  but that didn't work. Updating the drivers or purging Intel graphics
  didn't work either. I also tried a couple of stuff I saw online
  regarding /etc/X11/xorg.conf.d/.

  I do not have this issue on Windows, therefore it must be Ubuntu-
  related.

  When I set nomodeset on GRUB and update it, flickering disappears, but
  at the cost of my brightness adjuster and Night Light.

  As for package I have:

  apt-cache policy pkgname
  N: Unable to locate package pkgname

  dpkg -l |grep xserver-xorg-core
  ii xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 amd64 Xorg X server - core 
server

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu

[Touch-packages] [Bug 1945302] Re: Screen flickering on Ubuntu 20.04 - HP Spectre X360 with Intel Skylake GT2 [HD Graphics 520]

Thanks for the bug report.

You seem to be using the 'oibaf' PPA which is unsupported and often
causes bugs like this. Please remove it using 'ppa-purge', reboot, and
then open new bugs for any issues you still have.


** Package changed: xorg (Ubuntu) => ubuntu

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

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

Title:
  Screen flickering on Ubuntu 20.04 - HP Spectre X360 with Intel Skylake
  GT2 [HD Graphics 520]

Status in Ubuntu:
  Invalid

Bug description:

  I am using Ubuntu 20.04.3 LTS on my HP Spectre X360 with Intel Skylake
  GT2 [HD Graphics 520] and I am having flickering graphics.

  The problem sometimes happens showing grey flickering boxes 5-6 times
  in a minute, and sometimes it does not happen for 2-3 minutes.
  Overall, it annoys me quite a lot.

  I have tried decreasing the refresh rate from 60Hz to lower options,
  but that didn't work. Updating the drivers or purging Intel graphics
  didn't work either. I also tried a couple of stuff I saw online
  regarding /etc/X11/xorg.conf.d/.

  I do not have this issue on Windows, therefore it must be Ubuntu-
  related.

  When I set nomodeset on GRUB and update it, flickering disappears, but
  at the cost of my brightness adjuster and Night Light.

  As for package I have:

  apt-cache policy pkgname
  N: Unable to locate package pkgname

  dpkg -l |grep xserver-xorg-core 
  ii  xserver-xorg-core  2:1.20.11-1ubuntu1~20.04.2 
   amd64Xorg X server - core server

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 28 10:43:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:804e]
  InstallationDate: Installed on 2021-09-22 (5 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic 
root=UUID=c68313b0-c9ba-4714-abc0-dff5762a92b2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
  Identifier  "Intel Graphics"
  Driver  "intel"
  Option  "TearFree""true"
   EndSection
  dmi.bios.date: 12/27/2019
  dmi.bios.release: 15.54
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.54
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 804E
  dmi.board.vendor: HP
  dmi.board.version: 33.24
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 33.24
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.54:bd12/27/2019:br15.54:efr33.24:svnHP:pnHPSpectrex360Convertible:pvr:skuN7H72EA#AB8:rvnHP:rn804E:rvr33.24:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible
  dmi.product.sku: N7H72EA#AB8
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107+git2109250500.122ff0~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.3~git2109270600.0e3fcc~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.3~git2109270600.0e3fcc~oibaf~f
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1945302/+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 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2021-09-28 Thread Timo Aaltonen

huh, focal-updates has a much newer mesa which has that commit..

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

Title:
  Crash in libegl-mesa0 due to out of bound array access

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
  on Mesa master branch with change:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
  .This bug is to request to include this change in Mesa upgrades in
  bionic.

  Please let me know if this change needs to be back ported to other
  branch so that libegl-mesa0 upgrade in Bionic could pick this change.

  lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+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 1945302] [NEW] Screen flickering on Ubuntu 20.04 - HP Spectre X360 with Intel Skylake GT2 [HD Graphics 520]

2021-09-28 Thread Uyfar Us

Public bug reported:


I am using Ubuntu 20.04.3 LTS on my HP Spectre X360 with Intel Skylake
GT2 [HD Graphics 520] and I am having flickering graphics.

The problem sometimes happens showing grey flickering boxes 5-6 times in
a minute, and sometimes it does not happen for 2-3 minutes. Overall, it
annoys me quite a lot.

I have tried decreasing the refresh rate from 60Hz to lower options, but
that didn't work. Updating the drivers or purging Intel graphics didn't
work either. I also tried a couple of stuff I saw online regarding
/etc/X11/xorg.conf.d/.

I do not have this issue on Windows, therefore it must be Ubuntu-
related.

When I set nomodeset on GRUB and update it, flickering disappears, but
at the cost of my brightness adjuster and Night Light.

As for package I have:

apt-cache policy pkgname
N: Unable to locate package pkgname

dpkg -l |grep xserver-xorg-core 
ii  xserver-xorg-core  2:1.20.11-1ubuntu1~20.04.2   
 amd64Xorg X server - core server

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 28 10:43:48 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:804e]
InstallationDate: Installed on 2021-09-22 (5 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: HP HP Spectre x360 Convertible
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic 
root=UUID=c68313b0-c9ba-4714-abc0-dff5762a92b2 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf:
 Section "Device"
Identifier  "Intel Graphics"
Driver  "intel"
Option  "TearFree""true"
 EndSection
dmi.bios.date: 12/27/2019
dmi.bios.release: 15.54
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.54
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 804E
dmi.board.vendor: HP
dmi.board.version: 33.24
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 33.24
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.54:bd12/27/2019:br15.54:efr33.24:svnHP:pnHPSpectrex360Convertible:pvr:skuN7H72EA#AB8:rvnHP:rn804E:rvr33.24:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
dmi.product.name: HP Spectre x360 Convertible
dmi.product.sku: N7H72EA#AB8
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107+git2109250500.122ff0~oibaf~f
version.libgl1-mesa-dri: libgl1-mesa-dri 21.3~git2109270600.0e3fcc~oibaf~f
version.libgl1-mesa-glx: libgl1-mesa-glx 21.3~git2109270600.0e3fcc~oibaf~f
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~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 third-party-packages ubuntu

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

Title:
  Screen flickering on Ubuntu 20.04 - HP Spectre X360 with Intel Skylake
  GT2 [HD Graphics 520]

Status in xorg package in Ubuntu:
  New

Bug description:

  I am using Ubuntu 20.04.3 LTS on my HP Spectre X360 with Intel Skylake
  GT2 [HD Graphics 520] and I am having flickering graphics.

  The problem sometimes happens showing grey flickering boxes 5-6 times
  in a minute, and sometimes it does not happen for 2-3 minutes.
  Overall, it annoys me quite a lot.

  I have tried decreasing the refresh rate from 60Hz to lower options,
  but that didn't work. Updating the drivers or purging Intel graphics
  didn't work either. I also tried a couple of stuff I saw online
  regarding /etc/X11/xorg.conf.d/.

  I do not have this issue on Windows, therefore it must be Ubuntu-
  related.

  When I set nomodeset on GRUB and update it, flickering disappears, but
  at the cost of my brightness adjuster and Night Light.

  As for package I have:

  apt-cache policy pkgname
  N: Unable to locate package pkgname

  dpkg -l |grep xserver-xorg-core 
  ii  xserver-xorg-core  2:1.20.11-1ubuntu1~20.04.2 
   amd64Xorg X

[Touch-packages] [Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models

2021-09-28 Thread Lukas Märdian

** Changed in: systemd (Ubuntu Impish)
   Status: Fix Released => Won't Fix

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

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  Won't Fix
Status in systemd package in Ubuntu:
  Won't Fix
Status in systemd source package in Focal:
  Won't Fix
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and 
kernel 5.13, or kernel with this patch backported:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1938259/+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 1776499] Re: Crash in libegl-mesa0 due to out of bound array access

2021-09-28 Thread Penny Chiu

This issue is still happened using focal-update.

I checked below changelog for libegl-mesa0 package:

- https://packages.ubuntu.com/focal/libegl-mesa0
- https://packages.ubuntu.com/focal-updates/libegl-mesa0

And found the change is only existed in focal, but not in focal-update:

mesa (18.1.1-1ubuntu1) cosmic; urgency=medium

  * Merge from Debian.
  * glvnd-fix-a-segfault-in-eglgetprocaddess.diff: Backport a commit to
fix a segfault. (LP: #1776499)

 -- Timo Aaltonen   Wed, 13 Jun 2018 12:10:21 +0300

Timo, can we also have this fix landed in focal-update?

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

Title:
  Crash in libegl-mesa0 due to out of bound array access

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  Crash in libegl-mesa0 due to out of bound array access. Crash is fixed
  on Mesa master branch with change:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d
  .This bug is to request to include this change in Mesa upgrades in
  bionic.

  Please let me know if this change needs to be back ported to other
  branch so that libegl-mesa0 upgrade in Bionic could pick this change.

  lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  apt-cache policy libegl-mesa0
  libegl-mesa0:
Installed: 18.0.0~rc5-1ubuntu1
Candidate: 18.0.0~rc5-1ubuntu1
Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+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 1945235] Re: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from transport_put() from hfp_rfcomm_handle()

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

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

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

Title:
  pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from
  transport_put() from hfp_rfcomm_handle()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3f255341dbcb4f57cf88d6fc2bed25ae18a760fe

  ---

  have headphones bluetooth
  bluetooth connect and disconnect if i turn off sound

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  duncan20876 F pulseaudio
   /dev/snd/controlC0:  duncan20876 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Mon Sep 27 21:06:47 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-13 (14 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_bluetooth_transport_put () at 
/usr/lib/pulse-15.0+dfsg1/modules/libbluez5-util.so
   () at /usr/lib/pulse-15.0+dfsg1/modules/libbluez5-util.so
   pa_mainloop_dispatch () at /lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_iterate () at /lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_run () at /lib/x86_64-linux-gnu/libpulse.so.0
  Title: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/21/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1945235/+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 1945235] Re: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from transport_put() from hfp_rfcomm_handle()

Tracking in
https://errors.ubuntu.com/problem/3f255341dbcb4f57cf88d6fc2bed25ae18a760fe

** Summary changed:

- pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put()
+ pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from 
transport_put() from hfp_rfcomm_handle()

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1945235/+attachment/5528499/+files/CoreDump.gz

** Information type changed from Private to Public

** Description changed:

+ https://errors.ubuntu.com/problem/3f255341dbcb4f57cf88d6fc2bed25ae18a760fe
+ 
+ ---
+ 
  have headphones bluetooth
  bluetooth connect and disconnect if i turn off sound
  
  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  duncan20876 F pulseaudio
-  /dev/snd/controlC0:  duncan20876 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  duncan20876 F pulseaudio
+  /dev/snd/controlC0:  duncan20876 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Mon Sep 27 21:06:47 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-13 (14 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  ProcEnviron:
-  LANG=fr_FR.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
-  pa_bluetooth_transport_put () at 
/usr/lib/pulse-15.0+dfsg1/modules/libbluez5-util.so
-  () at /usr/lib/pulse-15.0+dfsg1/modules/libbluez5-util.so
-  pa_mainloop_dispatch () at /lib/x86_64-linux-gnu/libpulse.so.0
-  pa_mainloop_iterate () at /lib/x86_64-linux-gnu/libpulse.so.0
-  pa_mainloop_run () at /lib/x86_64-linux-gnu/libpulse.so.0
+  pa_bluetooth_transport_put () at 
/usr/lib/pulse-15.0+dfsg1/modules/libbluez5-util.so
+  () at /usr/lib/pulse-15.0+dfsg1/modules/libbluez5-util.so
+  pa_mainloop_dispatch () at /lib/x86_64-linux-gnu/libpulse.so.0
+  pa_mainloop_iterate () at /lib/x86_64-linux-gnu/libpulse.so.0
+  pa_mainloop_run () at /lib/x86_64-linux-gnu/libpulse.so.0
  Title: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/21/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  separator:

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

Title:
  pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from
  transport_put() from hfp_rfcomm_handle()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3f255341dbcb4f57cf88d6fc2bed25ae18a760fe

  ---

  have headphones bluetooth
  bluetooth connect and disconnect if i turn off sound

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  duncan20876 F pulseaudio
   /dev/snd/controlC0:  duncan20876 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Mon Sep 27 21:06:47 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-13 (14 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=

[Touch-packages] [Bug 1945290] [NEW] /usr/bin/pulseaudio:6:pa_bluetooth_transport_put:transport_put:hfp_rfcomm_handle:rfcomm_io_callback:dispatch_pollfds

2021-09-28 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

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

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


** Tags: impish

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

Title:
  
/usr/bin/pulseaudio:6:pa_bluetooth_transport_put:transport_put:hfp_rfcomm_handle:rfcomm_io_callback:dispatch_pollfds

Status in pulseaudio package in Ubuntu:
  New

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:15.0+dfsg1-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/3f255341dbcb4f57cf88d6fc2bed25ae18a760fe 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1945290/+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 1945290] Re: /usr/bin/pulseaudio:6:pa_bluetooth_transport_put:transport_put:hfp_rfcomm_handle:rfcomm_io_callback:dispatch_pollfds

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

** This bug has been marked a duplicate of bug 1945235
   pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from 
transport_put() from hfp_rfcomm_handle()

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

Title:
  
/usr/bin/pulseaudio:6:pa_bluetooth_transport_put:transport_put:hfp_rfcomm_handle:rfcomm_io_callback:dispatch_pollfds

Status in pulseaudio package in Ubuntu:
  New

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:15.0+dfsg1-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/3f255341dbcb4f57cf88d6fc2bed25ae18a760fe 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1945290/+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 1945121] Re: Ubuntu auto-suspends when I unplug my laptop after not having used it for a few minutes.

Tracking upstream in https://gitlab.gnome.org/GNOME/gnome-settings-
daemon/-/issues/134 although I found it by
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/563 which
better matches this bug.

** Package changed: xorg (Ubuntu) => gnome-settings-daemon (Ubuntu)

** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #134
   https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/134

** Also affects: gnome-settings-daemon via
   https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/134
   Importance: Unknown
   Status: Unknown

** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #563
   https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/563

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

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

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

Title:
  Ubuntu auto-suspends when I unplug my laptop after not having used it
  for a few minutes.

Status in GNOME Settings Daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 20.04.3 LTS

  I have my power settings so that Ubuntu will never auto-suspend if
  plugged in, but will do so after 20 minutes if on battery power.

  If I leave it plugged in but untouched for 20 minutes, and then unplug
  it (to move it to another room when I come back to it), then it
  suspends on the way there.

  It would seem more intuitive that unplugging/plugging in would be
  considered interaction, and would reset the delay. The expected
  behavior, in that case, would be that it gets unplugged, stays on, and
  then suspends after 20 minutes if there is no further interaction.

  I know any official fix would probably take a while, if one is even
  considered. Is there any workaround?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.91.03  Fri Jul  2 
06:04:10 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 26 14:35:33 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.91.03, 5.11.0-34-generic, x86_64: installed
   nvidia, 460.91.03, 5.11.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Mobile) [1043:18fe]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti Mobile] 
[1043:18fe]
  InstallationDate: Installed on 2021-02-21 (216 days ago)
  InstallationMedia: Ubuntu 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 003: ID 13d3:5666 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 005: ID 1b1c:1b5c Corsair CORSAIR NIGHTSWORD RGB Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. TUF GAMING FX504GE_FX80GE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic 
root=UUID=94577a37-4156-ac57-02e9-af5914abc257 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX504GE.320
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX504GE
  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.ec.firmware.release: 1.16
  dmi.modalias:

[Touch-packages] [Bug 1945116] Re: gnome-shell crashed with SIGSEGV in old_intel_region_release() from old_intel_miptree_release() from intel_free_texture_image_buffer()

This appears to be in the same family as bug 1943406. But rather than
being driver-specific it looks like mutter is trying to delete an
invalid texture, which will crash differently for each driver.

** Summary changed:

- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in old_intel_region_release() from 
old_intel_miptree_release() from intel_free_texture_image_buffer()

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

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

** Summary changed:

- gnome-shell crashed with SIGSEGV in old_intel_region_release() from 
old_intel_miptree_release() from intel_free_texture_image_buffer()
+ [i915] gnome-shell crashed with SIGSEGV in old_intel_region_release() from 
old_intel_miptree_release() from intel_free_texture_image_buffer()

** Information type changed from Private to Public

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

Title:
  [i915] gnome-shell crashed with SIGSEGV in old_intel_region_release()
  from old_intel_miptree_release() from
  intel_free_texture_image_buffer()

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell crashed with SIGSEGV. on login to unity session this error
  report was generated.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu6
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Sep 26 21:35:14 2021
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1630503878
  InstallationDate: Installed on 2021-09-26 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210924)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/anubhav
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i915_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i915_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i915_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i915_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945116/+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 1945288] [NEW] Search domains missing from resolv.conf stub

2021-09-28 Thread Peter Ludikovsky

Public bug reported:

System is Mint 20.2, with the relevant packages taken from Ubuntu Focal.

This is the output of `systemd-resolv --status vpn0`:
Link 7 (vpn0)
  Current Scopes: DNS
DefaultRoute setting: yes
   LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
  DNSSEC setting: no
DNSSEC supported: no
  Current DNS Server: 10.0.0.53
 DNS Servers: 10.0.0.53
  DNS Domain: example.com
  example.com.rpz
  privatelink.blob.core.windows.net
  node.prd.lan.example.com
  node.stg.lan.example.com
  node.dev.lan.example.com

However that last domain is missing from `/etc/resolv.conf` (symlink to 
`/run/systemd/resolve/stub-resolv.conf`), instead there is a line
# Too many search domains configured, remaining ones ignored.

According to resolv.conf(5) since glibc 2.26 the number of search
domains should be unlimited, and installed is 2.31-0ubuntu9.3

VPN is PaloAlto GlobalProtect through the OpenConnect plugin on
NetworkManager.

Exact same setup and behaviour for a colleague using Pop!_OS 20.04

--
systemd:
  Installed: 245.4-4ubuntu3.13
  Candidate: 245.4-4ubuntu3.13
  Version table:
 *** 245.4-4ubuntu3.13 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
100 /var/lib/dpkg/status
 245.4-4ubuntu3.11 500
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 245.4-4ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

libc-bin:
  Installed: 2.31-0ubuntu9.3
  Candidate: 2.31-0ubuntu9.3
  Version table:
 *** 2.31-0ubuntu9.3 100
100 /var/lib/dpkg/status
 2.31-0ubuntu9.2 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
 2.31-0ubuntu9 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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


** Tags: focal

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

Title:
  Search domains missing from resolv.conf stub

Status in systemd package in Ubuntu:
  New

Bug description:
  System is Mint 20.2, with the relevant packages taken from Ubuntu
  Focal.

  This is the output of `systemd-resolv --status vpn0`:
  Link 7 (vpn0)
Current Scopes: DNS
  DefaultRoute setting: yes
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
Current DNS Server: 10.0.0.53
   DNS Servers: 10.0.0.53
DNS Domain: example.com
example.com.rpz
privatelink.blob.core.windows.net
node.prd.lan.example.com
node.stg.lan.example.com
node.dev.lan.example.com

  However that last domain is missing from `/etc/resolv.conf` (symlink to 
`/run/systemd/resolve/stub-resolv.conf`), instead there is a line
  # Too many search domains configured, remaining ones ignored.

  According to resolv.conf(5) since glibc 2.26 the number of search
  domains should be unlimited, and installed is 2.31-0ubuntu9.3

  VPN is PaloAlto GlobalProtect through the OpenConnect plugin on
  NetworkManager.

  Exact same setup and behaviour for a colleague using Pop!_OS 20.04

  --
  systemd:
Installed: 245.4-4ubuntu3.13
Candidate: 245.4-4ubuntu3.13
Version table:
   *** 245.4-4ubuntu3.13 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   245.4-4ubuntu3.11 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  libc-bin:
Installed: 2.31-0ubuntu9.3
Candidate: 2.31-0ubuntu9.3
Version table:
   *** 2.31-0ubuntu9.3 100
  100 /var/lib/dpkg/status
   2.31-0ubuntu9.2 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
   2.31-0ubuntu9 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1945288/+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 1926084] Re: [hirsute] [Intel AX200 Bluetooth] Bluetooth speakers reconnect randomly

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

Yes I was thinking that but didn't have any evidence of it yet. Let's
group this with bug 1933771 for now.

** This bug has been marked a duplicate of bug 1933771
   Bluetooth headset random disconnects AX200

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

Title:
  [hirsute] [Intel AX200 Bluetooth] Bluetooth speakers reconnect
  randomly

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth speakers reconnect randomly.
  The onlt workaround that seems to work is to remove speakers from paired 
devies, restart buetooth service and connect them once again. Once these stepss 
are performed connection become stable until reboot or hibernation.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluez 5.56-0ubuntu4
  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
  CurrentDesktop: GNOME
  Date: Sun Apr 25 17:22:11 2021
  InstallationDate: Installed on 2021-04-13 (12 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera
   Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth
   Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard 
and Mouse Combo
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO F0FA0066UA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-18 (6 days ago)
  dmi.bios.date: 03/31/2021
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O4VKT32A
  dmi.board.asset.tag: INVALID
  dmi.board.name: 371F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN 3424143288435
  dmi.chassis.type: 13
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1:
  dmi.product.family: IdeaCentre AIO 5 27IMB05
  dmi.product.name: F0FA0066UA
  dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05
  dmi.product.version: IdeaCentre AIO 5 27IMB05
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 44:AF:28:F7:A9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:2239397 acl:225 sco:0 events:318945 errors:0
TX bytes:207283666 acl:315238 sco:0 commands:3564 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926084/+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 1926145] Re: bluetooth disconnects and reconnects on 21.04

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

** This bug is no longer a duplicate of bug 1926084
   [hirsute] [Intel AX200 Bluetooth] Bluetooth speakers reconnect randomly
** This bug has been marked a duplicate of bug 1933771
   Bluetooth headset random disconnects AX200

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

Title:
  bluetooth disconnects and reconnects on 21.04

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth speaker disconnects randomly and reconnects again. Problem
  occurred after upgrade to Ubuntu 21.04 ( -d ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926145/+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 1945010] Re: [vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from mm_buffer_destroy() from pb_destroy()

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

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

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

Title:
  [vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from
  mm_buffer_destroy() from pb_destroy()

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

Bug description:
  https://errors.ubuntu.com/problem/d20095c0f9516f2d25a5e5b9194fdb87eec5ba8b

  ---

  gnome-shell crashed with SIGSEGV

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu6
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 25 01:54:33 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945010/+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 1945010] Re: [vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from mm_buffer_destroy() from pb_destroy()

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

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

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

Title:
  [vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from
  mm_buffer_destroy() from pb_destroy()

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

Bug description:
  https://errors.ubuntu.com/problem/d20095c0f9516f2d25a5e5b9194fdb87eec5ba8b

  ---

  gnome-shell crashed with SIGSEGV

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu6
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 25 01:54:33 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945010/+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 1945010] Re: [vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from mm_buffer_destroy() from pb_destroy()

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

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

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

Title:
  [vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from
  mm_buffer_destroy() from pb_destroy()

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

Bug description:
  https://errors.ubuntu.com/problem/d20095c0f9516f2d25a5e5b9194fdb87eec5ba8b

  ---

  gnome-shell crashed with SIGSEGV

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu6
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 25 01:54:33 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945010/+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 1945010] Re: gnome-shell crashed with SIGSEGV

Tracking in
https://errors.ubuntu.com/problem/d20095c0f9516f2d25a5e5b9194fdb87eec5ba8b

** Tags added: vmware vmwgfx

** Summary changed:

- gnome-shell crashed with SIGSEGV
+ [vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from 
mm_buffer_destroy() from pb_destroy()

** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)

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

** Information type changed from Private to Public

** Description changed:

+ https://errors.ubuntu.com/problem/d20095c0f9516f2d25a5e5b9194fdb87eec5ba8b
+ 
+ ---
+ 
  gnome-shell crashed with SIGSEGV
  
  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu6
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 25 01:54:33 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
-  ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
-  ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
-  ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
-  ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
+  ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
+  ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
+  ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
+  ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
+  ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  separator:

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

Title:
  [vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from
  mm_buffer_destroy() from pb_destroy()

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

Bug description:
  https://errors.ubuntu.com/problem/d20095c0f9516f2d25a5e5b9194fdb87eec5ba8b

  ---

  gnome-shell crashed with SIGSEGV

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu6
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 25 01:54:33 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945010/+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 1926084] Re: [hirsute] [Intel AX200 Bluetooth] Bluetooth speakers reconnect randomly

2021-09-28 Thread Maxim Petrov

Most likely cause of this problem is this bug in linux-firmware

https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771

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

Title:
  [hirsute] [Intel AX200 Bluetooth] Bluetooth speakers reconnect
  randomly

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth speakers reconnect randomly.
  The onlt workaround that seems to work is to remove speakers from paired 
devies, restart buetooth service and connect them once again. Once these stepss 
are performed connection become stable until reboot or hibernation.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluez 5.56-0ubuntu4
  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
  CurrentDesktop: GNOME
  Date: Sun Apr 25 17:22:11 2021
  InstallationDate: Installed on 2021-04-13 (12 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera
   Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth
   Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard 
and Mouse Combo
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO F0FA0066UA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-18 (6 days ago)
  dmi.bios.date: 03/31/2021
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O4VKT32A
  dmi.board.asset.tag: INVALID
  dmi.board.name: 371F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN 3424143288435
  dmi.chassis.type: 13
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1:
  dmi.product.family: IdeaCentre AIO 5 27IMB05
  dmi.product.name: F0FA0066UA
  dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05
  dmi.product.version: IdeaCentre AIO 5 27IMB05
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 44:AF:28:F7:A9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:2239397 acl:225 sco:0 events:318945 errors:0
TX bytes:207283666 acl:315238 sco:0 commands:3564 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926084/+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 1944951] Re: KDE delayed display update / konsole artifacts

** Summary changed:

- delayed display update / konsole artifacts
+ KDE delayed display update / konsole artifacts

** Package changed: xorg (Ubuntu) => kwin (Ubuntu)

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

Title:
  KDE delayed display update / konsole artifacts

Status in kwin package in Ubuntu:
  Confirmed

Bug description:
  Since one of the recent Impish updates, konsole shows artifacts and
  reacts slowly.  In fact, it looks like screen updates are pipelined on
  pixel-group granularity somehow, and the pipeline isn't drained
  completely: When more text goes to the terminal (e.g., I type
  something), existing artifacts vanish, but new ones (in the new text)
  appear.

  Unfortunately, I don't see any of the previous konsole .deb releases
  (e.g. 4:21.08.1-1 or 4:21.08.0-1) on the Ubuntu mirrors, so I cannot
  go back and simply check whether the newest konsole updates are the
  culprit.  I'm actually not sure whether konsole is responsible at all,
  I originally intended to file against xorg; however, I see those
  artifacts in neither xterm nor gnome-terminal.

  Find attached a screenshot (taken with an external camera; these
  artifacts cannot be recorded using a screenshot tool such as
  imagemagick's "import") where I ran "ls" in /tmp, and cleared the
  terminal with ^L afterwards.  The screen is still littered with
  remains of the "ls" output.  It took a few tries to get artifacts this
  pronounced, though; usually they only concern small parts of the
  terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Sep 24 08:09:18 2021
  DistUpgraded: 2021-08-08 15:09:23,066 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 530 [17aa:5050]
 Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:5050]
  InstallationDate: Installed on 2016-11-26 (1762 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: LENOVO 20FXS05500
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-16-generic 
root=/dev/mapper/vgubuntu-root ro kopt=root=/dev/mapper/vgubuntu-root 
resume=/dev/mapper/vgubuntu-swap nouveau.runpm=0 mitigations=off 
i915.i915_enable_fbc=0
  SourcePackage: xorg
  UpgradeStatus: Upgraded to impish on 2021-08-08 (46 days ago)
  dmi.bios.date: 10/24/2019
  dmi.bios.release: 2.30
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET90W (2.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS05500
  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.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET90W(2.30):bd10/24/2019:br2.30:efr1.5:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:skuLENOVO_MT_20FX_BU_Think_FM_ThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FXS05500
  dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.1-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1944951/+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 1451032] Re: keyscript option in crypttab not implemented

2021-09-28 Thread TJ

This really should not be marked Invalid since it represents a very real
regression on recommended and documented functionality that many
installs using LUKS rely upon. Workarounds of varying security quality
abound as a result instead of a single, well designed and integrated
solution.

Indeed, in December 2020 Lennart Poettering created a simple patch for
this by extending the cryptsetup code to read an AF_SOCKET [1] and
recommended linking that with a system-service that sets
StandardOutput=socket [2][3] where the key data can be read from.

[1] hasn't been merged into systemd as yet but with some additional push
upstream that could likely happen.

[1]
https://github.com/poettering/systemd/commit/e2c2f868b28f1445e061bf7eb475b0c49efe3ac2

[2] https://github.com/systemd/systemd/pull/3007#issuecomment-710212323

[3] https://github.com/systemd/systemd/pull/3007#issuecomment-713860129

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

Title:
keyscript option in crypttab not implemented

Status in systemd package in Ubuntu:
Invalid
Status in systemd package in Debian:
Fix Released

Bug description:
The setup for unlocking an encrypted volume during boot using (only) a
keyfile (on a detachable USB drive) usually calls for a keyscript to
be specified as one of the encrypted volume's options. But with
systemd, such encrypted volumes can only be unlocked during boot by
typing in a passphrase.

Steps to reproduce:
1. Have a LUKS encrypted volume.
2. Have said volume specified in /etc/crypttab, with keyscript= option
pointing to your script for outputting the unlocking key.
3. Boot.

What I expect to happen:
To have the volume unlocked by the script at boot time without manual
intervention.

What happens instead:
Plymouth shows a prompt to enter a valid passphrase for the volume.

Workarounds:
Apparently the options for unlocking encrypted drives, including keyscript,
can also be specified at the kernel command-line, without crypttab, and
according to yaantc at Hacker News [1] this can be used to work around the
issue. I haven't personally tried this.

* [1] https://news.ycombinator.com/item?id=8477913

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat May 2 15:39:07 2015
InstallationDate: Installed on 2014-10-18 (196 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
MachineType: ASUSTeK COMPUTER INC. UX32A
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed
root=UUID=2185885c-b860-49a8-973f-fa3b52d3eecf ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2015-04-23 (8 days ago)
dmi.bios.date: 01/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32A.214
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32A
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.:bvrUX32A.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX32A
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/systemd/+bug/1451032/+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 1451032] Re: keyscript option in crypttab not implemented

2021-09-28 Thread TJ

Update: Lennart's AF_SOCKET solution was added to systemd v248 in:

commit e2c2f868b28f1445e061bf7eb475b0c49efe3ac2
Author: Lennart Poettering 
Date:   Wed Nov 4 17:24:53 2020 +0100

cryptsetup: port cryptsetup's main key file logic over to 
read_full_file_full()

Previously, we'd load the file with libcryptsetup's calls. Let's do that
in our own, so that we can make use of READ_FULL_FILE_CONNECT_SOCKET,
i.e. read in keys via AF_UNIX sockets, so that people can plug key
providers into our logic.

This provides functionality similar to Debian's keyscript= crypttab
option (see → #3007), as it allows key scripts to be run as socket
activated services, that have stdout connected to the activated socket.
In contrast to traditional keyscript= support this logic runs stuff out
of process however, which is beneficial, since it allows sandboxing and
similar.

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

Title:
  keyscript option in crypttab not implemented

Status in systemd package in Ubuntu:
  Invalid
Status in systemd package in Debian:
  Fix Released

Bug description:
  The setup for unlocking an encrypted volume during boot using (only) a
  keyfile (on a detachable USB drive) usually calls for a keyscript to
  be specified as one of the encrypted volume's options. But with
  systemd, such encrypted volumes can only be unlocked during boot by
  typing in a passphrase.

  Steps to reproduce:
  1. Have a LUKS encrypted volume.
  2. Have said volume specified in /etc/crypttab, with keyscript= option 
pointing to your script for outputting the unlocking key.
  3. Boot.

  What I expect to happen:
  To have the volume unlocked by the script at boot time without manual 
intervention.

  What happens instead:
  Plymouth shows a prompt to enter a valid passphrase for the volume.

  Workarounds:
  Apparently the options for unlocking encrypted drives, including keyscript, 
can also be specified at the kernel command-line, without crypttab, and 
according to yaantc at Hacker News [1] this can be used to work around the 
issue. I haven't personally tried this.

  * [1] https://news.ycombinator.com/item?id=8477913

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  2 15:39:07 2015
  InstallationDate: Installed on 2014-10-18 (196 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed 
root=UUID=2185885c-b860-49a8-973f-fa3b52d3eecf ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (8 days ago)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  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.:bvrUX32A.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  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/systemd/+bug/1451032/+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 1943813] Re: Problem with bluetooth keyboard: not usable

If it works in Ubuntu 20.04.3 as you say, and only fails in MATE, then
we probably shouldn't assign this to the common package where it's
working already.

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

** Summary changed:

- Problem with bluetooth keyboard: not usable
+ Problem with bluetooth keyboard: not usable in MATE

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

Title:
  Problem with bluetooth keyboard: not usable in MATE

Status in Ubuntu MATE:
  New
Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I have a bluetooth keyboard that I use regularly with other devices. The 
keyboard is Jelly Comb Case with Italian Keyboard for Samsung Galaxy Tab S6 
Lite 10.4 ", Removable Backlit Keyboard in 7 Colors, Italian QWERTY for Sam If 
I try to use it with Ubuntu it only works with the LIVE version. When I install 
Ubuntu it stops working, after updates.
  I have tried with various Ubuntu Mate and also the impish version of Ubuntu 
Mate but, using the same notebook, the computer cannot use it (LIVE yes, 
installed no).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1943813/+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 1926084] Re: [hirsute] [Intel AX200 Bluetooth] Bluetooth speakers reconnect randomly