[Touch-packages] [Bug 2041496] Re: btmgmt --index broken in Mantic

[Juerg Haefliger]

This has landed in upstream bluez now:
https://github.com/bluez/bluez/commit/303925b28110469ad002ac19ce0eb9c84d6aceb2

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

Title:
  btmgmt --index broken in Mantic

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  On Mantic:

  $ btmgmt --index 1 info
  Unable to open 1: No such file or directory (2)
  Index list with 1 item
  hci0: Primary controller
   addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c
   supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy 
configuration static-addr phy-configuration
   current settings: powered ssp br/edr le secure-conn
   name rpi-5b-rev1d0-f88b
   short name
  hci0: Configuration options
   supported options: public-address
   missing options:

  Note the error 'Unable to open...' above.

  The machine has only a single hci so index 1 is invalid. The correct
  result should be:

  $ btmgmt --index 1 info
  Reading hci1 info failed with status 0x11 (Invalid Index)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2041496/+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 2038453] Update Released

[Chris Halse Rogers]

The verification of the Stable Release Update for apt has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] apt snapshot integration backport

Status in Ubuntu Pro:
  Triaged
Status in Ubuntu Pro 18.04 series:
  Triaged
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Won't Fix
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Jammy:
  Fix Released
Status in apt source package in Lunar:
  Won't Fix
Status in apt source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  The snapshot service provides users access to older states of the archive 
with ease of use, and enables a consistent user experience across all supported 
releases, as otherwise users would have to rewrite their sources.list to make 
use of snapshots and set up pinning; hence partners requested the feature be 
SRUed to older releases as well.

  [Test plan]
  The complete regression test suite in autopkgtests includes an automatic test 
case for this and the known limitations that have been fixed. Aside from that, 
it is also worthwhile to do an end-to-end test:

  Configure snapshot=yes for Ubuntu sources in your sources.list and

  1. run apt update - it should not use snapshot
  2. run apt update --snapshot 20231001T00Z, it should download the snapshot
  3. run apt policy --snapshot 20231001T00Z hello, it should show hello in 
the snapshot
  4. run apt install --snapshot 20231001T00Z hello, it should install hello 
from the snapshot
  5. Run apt update; observe snapshot not being downloaded
  6. Observe snapshots are gone from /var/lib/apt/lists again

  [Where problems could occur]
  The integration has been purposefully limited in how it works to reduce the 
impact it has on the APT code; hence it was possible to cherry-pick this into 
22.04, 20.04, and even 18.04, with only a minor editorial change. This 
significantly limits the risk.

  This feature is only enabled for sources with snapshot=yes (.list) or
  Snapshot: yes (.sources) or other truthy values apt recognizes. Most
  users will not have such entries as they did not have an APT
  supporting it.

  This combined should ensure that users do not experience any
  regressions. However the feature may be lacking in some ways that we
  may want to address in follow up SRUs; it has not been used in the
  wild a lot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-pro/+bug/2038453/+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 2038453] Re: [SRU] apt snapshot integration backport

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 2.4.11

---
apt (2.4.11) jammy; urgency=medium

  * Backport archive snapshot integration as of 2.7.3 (LP: #2038453)

 -- Julian Andres Klode   Fri, 06 Oct 2023 10:53:53
+0200

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

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

Title:
  [SRU] apt snapshot integration backport

Status in Ubuntu Pro:
  Triaged
Status in Ubuntu Pro 18.04 series:
  Triaged
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Won't Fix
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Jammy:
  Fix Released
Status in apt source package in Lunar:
  Won't Fix
Status in apt source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  The snapshot service provides users access to older states of the archive 
with ease of use, and enables a consistent user experience across all supported 
releases, as otherwise users would have to rewrite their sources.list to make 
use of snapshots and set up pinning; hence partners requested the feature be 
SRUed to older releases as well.

  [Test plan]
  The complete regression test suite in autopkgtests includes an automatic test 
case for this and the known limitations that have been fixed. Aside from that, 
it is also worthwhile to do an end-to-end test:

  Configure snapshot=yes for Ubuntu sources in your sources.list and

  1. run apt update - it should not use snapshot
  2. run apt update --snapshot 20231001T00Z, it should download the snapshot
  3. run apt policy --snapshot 20231001T00Z hello, it should show hello in 
the snapshot
  4. run apt install --snapshot 20231001T00Z hello, it should install hello 
from the snapshot
  5. Run apt update; observe snapshot not being downloaded
  6. Observe snapshots are gone from /var/lib/apt/lists again

  [Where problems could occur]
  The integration has been purposefully limited in how it works to reduce the 
impact it has on the APT code; hence it was possible to cherry-pick this into 
22.04, 20.04, and even 18.04, with only a minor editorial change. This 
significantly limits the risk.

  This feature is only enabled for sources with snapshot=yes (.list) or
  Snapshot: yes (.sources) or other truthy values apt recognizes. Most
  users will not have such entries as they did not have an APT
  supporting it.

  This combined should ensure that users do not experience any
  regressions. However the feature may be lacking in some ways that we
  may want to address in follow up SRUs; it has not been used in the
  wild a lot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-pro/+bug/2038453/+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 2038453] Re: [SRU] apt snapshot integration backport

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 2.0.10

---
apt (2.0.10) focal; urgency=medium

  * Backport archive snapshot integration as of 2.7.3 (LP: #2038453)

 -- Julian Andres Klode   Fri, 06 Oct 2023 11:42:30
+0200

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

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

Title:
  [SRU] apt snapshot integration backport

Status in Ubuntu Pro:
  Triaged
Status in Ubuntu Pro 18.04 series:
  Triaged
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Won't Fix
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Jammy:
  Fix Released
Status in apt source package in Lunar:
  Won't Fix
Status in apt source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  The snapshot service provides users access to older states of the archive 
with ease of use, and enables a consistent user experience across all supported 
releases, as otherwise users would have to rewrite their sources.list to make 
use of snapshots and set up pinning; hence partners requested the feature be 
SRUed to older releases as well.

  [Test plan]
  The complete regression test suite in autopkgtests includes an automatic test 
case for this and the known limitations that have been fixed. Aside from that, 
it is also worthwhile to do an end-to-end test:

  Configure snapshot=yes for Ubuntu sources in your sources.list and

  1. run apt update - it should not use snapshot
  2. run apt update --snapshot 20231001T00Z, it should download the snapshot
  3. run apt policy --snapshot 20231001T00Z hello, it should show hello in 
the snapshot
  4. run apt install --snapshot 20231001T00Z hello, it should install hello 
from the snapshot
  5. Run apt update; observe snapshot not being downloaded
  6. Observe snapshots are gone from /var/lib/apt/lists again

  [Where problems could occur]
  The integration has been purposefully limited in how it works to reduce the 
impact it has on the APT code; hence it was possible to cherry-pick this into 
22.04, 20.04, and even 18.04, with only a minor editorial change. This 
significantly limits the risk.

  This feature is only enabled for sources with snapshot=yes (.list) or
  Snapshot: yes (.sources) or other truthy values apt recognizes. Most
  users will not have such entries as they did not have an APT
  supporting it.

  This combined should ensure that users do not experience any
  regressions. However the feature may be lacking in some ways that we
  may want to address in follow up SRUs; it has not been used in the
  wild a lot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-pro/+bug/2038453/+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 2033639] Re: debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error

[Bug Watch Updater]

** Changed in: debug-me (Debian)
   Status: New => Fix Released

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

Title:
  debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error

Status in binutils package in Ubuntu:
  New
Status in debug-me package in Ubuntu:
  Triaged
Status in debug-me package in Debian:
  Fix Released

Bug description:
  debug-me 1.20221231-1 fails to build from source on ppc64el due to
  internal ld.gold error (binutils 2.41-4ubuntu1):

  ```
  Linking dist/build/debug-me/debug-me ...
  /usr/bin/ld.gold: internal error in set_xindex, at ../../gold/object.h:1050
  collect2: error: ld returned 1 exit status
  `powerpc64le-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1)
  ```

  Full log: https://launchpadlibrarian.net/684538812/buildlog_ubuntu-
  mantic-ppc64el.debug-me_1.20221231-1_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2033639/+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 2043529] [NEW] HDMI port issues after ubuntu 23 upgrade

[Michael Forehnd]

Public bug reported:

Hdmi port will not recognize external display after lunar lobster
install. This issue was verified by upgrading my desktop to lunar
lobster that had 22.10 previously installed. The desktop has 3 monitors
working before the upgrade. After the upgrade only one monitor will
work. I have attempted to trouble shoot the issue but am leaning towards
a bug at this point. The thunderbolt works for displaying however I am
unable to get the hdmi to recognize any connection. The port is working
and was verified by windows that is dual booted on this laptop.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15
Uname: Linux 6.2.0-27-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  545.29.02  Thu Oct 26 21:21:38 
UTC 2023
 GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~23.04)
ApportVersion: 2.26.1-0ubuntu2.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 14 18:29:03 2023
DistUpgraded: Fresh install
DistroCodename: lunar
DistroVariant: ubuntu
DkmsStatus:
 evdi/1.14.1, 6.2.0-27-generic, x86_64: installed
 nvidia/545.29.02, 6.2.0-27-generic, x86_64: installed
 rtl8812AU/#MODULE_VERSION#: added
 virtualbox/7.0.6, 6.2.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 
[VGA controller])
   Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:087d]
   Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d]
InstallationDate: Installed on 2023-02-21 (266 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
 Bus 001 Device 002: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter
 Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5530
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/zsh
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic 
root=UUID=47692d38-dda2-45e4-b8f9-eb478775c1fe ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/13/2023
dmi.bios.release: 1.31
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.31.0
dmi.board.name: 0CDJF9
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd03/13/2023:br1.31:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0CDJF9:rvrA01:cvnDellInc.:ct10:cvr:sku087D:
dmi.product.family: Precision
dmi.product.name: Precision 5530
dmi.product.sku: 087D
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.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-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug lunar ubuntu wayland-session

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

Title:
  HDMI port issues after ubuntu 23 upgrade

Status in xorg package in Ubuntu:
  New

Bug description:
  Hdmi port will not recognize external display after lunar lobster
  install. This issue was verified by upgrading my desktop to lunar
  lobster that had 22.10 previously installed. The desktop has 3
  monitors working before the upgrade. After the upgrade only one
  monitor will work. I have attempted to trouble shoot the issue but am
  leaning towards a bug at this point. The thunderbolt works for
  displaying however I am unable to get the hdmi to recognize any
  

[Touch-packages] [Bug 2043524] [NEW] audio disappeared after upgrade to Ubuntu 23.10

[Mark Bixler]

Public bug reported:

I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except
there is no audio output on streaming functions. The external bluetooth
speaker is connected and detected. It is charged and responds to
testing. Just no sound when playing videos or podcasts.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  owner   975 F wireplumber
 /dev/snd/seq:owner   971 F pipewire
CasperMD5CheckResult: fail
CurrentDesktop: KDE
Date: Tue Nov 14 17:50:17 2023
InstallationDate: Installed on 2023-04-15 (213 days ago)
InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago)
dmi.bios.date: 07/04/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V3.0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-P31/W8 (MS-7788)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7788
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug mantic

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

Title:
  audio disappeared after upgrade to Ubuntu 23.10

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except
  there is no audio output on streaming functions. The external
  bluetooth speaker is connected and detected. It is charged and
  responds to testing. Just no sound when playing videos or podcasts.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owner   975 F wireplumber
   /dev/snd/seq:owner   971 F pipewire
  CasperMD5CheckResult: fail
  CurrentDesktop: KDE
  Date: Tue Nov 14 17:50:17 2023
  InstallationDate: Installed on 2023-04-15 (213 days ago)
  InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago)
  dmi.bios.date: 07/04/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P31/W8 (MS-7788)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7788
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+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 1250109] Re: Please use dpkg-triggers for update-grub when installing or removing kernel packages

[Ubuntu Foundations Team Bug Bot]

The attachment "use-triggers.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

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

Title:
  Please use dpkg-triggers for update-grub when installing or removing
  kernel packages

Status in grub2 package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in grub2 package in Debian:
  Won't Fix

Bug description:
  Currently the kernel package runs update-grub every time one is
  installed or removed.  This results in it being run a dozen times
  during a dist-upgrade, and this is rather time consuming and annoying.
  Please use a dpkg trigger to cause update-grub to be run only once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1250109/+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 1250109] Re: Please use dpkg-triggers for update-grub when installing or removing kernel packages

[Julian Andres Klode]

update-initramfs -c call by kernel postinst hook is not covered, but we
need to make sure the initramfs is there at kernel configuration point
because we need it to be there when updating boot loaders.

e.g. if we triggered both in that case, update-grub could run before
update-initramfs.

if we included an initramfs-tools hook to run update-grub, update-grub
could be run twice but update-initramfs only once.

I propose we keep this bug for grub2 change to match upstream, but it
may be worth revisiting how we can merge update-initramfs -c and update-
initramfs -u calls when updating kernels and other packages touching
initramfs in one session.

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

Title:
  Please use dpkg-triggers for update-grub when installing or removing
  kernel packages

Status in grub2 package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in grub2 package in Debian:
  Won't Fix

Bug description:
  Currently the kernel package runs update-grub every time one is
  installed or removed.  This results in it being run a dozen times
  during a dist-upgrade, and this is rather time consuming and annoying.
  Please use a dpkg trigger to cause update-grub to be run only once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1250109/+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 1250109] Re: Please use dpkg-triggers for update-grub when installing or removing kernel packages

[Julian Andres Klode]

Draft fix for update-grub: https://salsa.debian.org/grub-
team/grub/-/merge_requests/46

Still need to take care of grub-install at some point, haven't figured
out the best approach there yet.

** Changed in: grub2 (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

** Changed in: grub2 (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Please use dpkg-triggers for update-grub when installing or removing
  kernel packages

Status in grub2 package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in grub2 package in Debian:
  Won't Fix

Bug description:
  Currently the kernel package runs update-grub every time one is
  installed or removed.  This results in it being run a dozen times
  during a dist-upgrade, and this is rather time consuming and annoying.
  Please use a dpkg trigger to cause update-grub to be run only once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1250109/+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 589496] Re: bash --rcfile does not behave as documented

[Dan Bungert]

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

Merging with LP: #1097467, as documentation fixes are happening there to
reflect long-standing upstream desired behavior.

** This bug has been marked a duplicate of bug 1097467
   bash does not fulfill --rcfile option properly

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

Title:
  bash --rcfile does not behave as documented

Status in bash package in Ubuntu:
  Confirmed
Status in bash package in Debian:
  New

Bug description:
  Binary package hint: bash

  the bash manpage says this about --rcfile

  --rcfile file
  Execute commands from file instead of the system  wide  initial‐
  ization file /etc/bash.bashrc and the standard personal initial‐
  ization file ~/.bashrc if the shell is interactive (see  INVOCA‐
  TION below).

  under INVOCATION it says

  When  an  interactive  shell that is not a login shell is started, bash
  reads and executes commands from  /etc/bash.bashrc  and  ~/.bashrc,  if
  these  files  exist.  This may be inhibited by using the --norc option.
  The --rcfile file option will force bash to read and  execute  commands
  from file instead of /etc/bash.bashrc and ~/.bashrc.

  but when i execute
  $ bash --rcfile somercfilewhichreallydoesexistandisreadableandall
  it will still read /etc/bash/bashrc (can be verified by adding --verbose)

  using lucid with bash 4.1-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/589496/+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 1904048] Re: ı have amd64 cpu but . updater want installed intel microcode firmware

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

The initramfs contains all possible needed firmware and kernel modules.
This allows moving the system disk into a different computer (e.g. from
an AMD system to an Intel system).

The intel microcode is ignored on AMD systems and the amd microcode is
ignored on Intel systems. These extra files have no noticeable
performance impact.

Can you give more details why your laptop is very slow?

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  ı have amd64 cpu but . updater want installed intel microcode firmware

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  software updater wants install some and ı want see whats new

  intel-microcode changelog:
  installed: 3.20200609.0ubuntu0.18.04.1
  new: 3.20201110.0ubuntu0.18.04.2 

  when ı see 5 minutes a go , ı said Aao!!? when ,?

  and yes, my laptop is very slow , why , maybe this ?

  
  Ubuntu 18.04.5 LTS
  AMD® C-60 apu with radeon(tm) hd graphics × 2
  3,5 GiB Ram

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1904048/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Dan Bungert]

Uploaded

** Changed in: bash (Ubuntu)
 Assignee: (unassigned) => Dan Bungert (dbungert)

** Changed in: bash (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  New
Status in bash package in Ubuntu:
  Fix Committed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

    --rcfile file
    Execute commands from file instead of the system wide 
initialization file /etc/bash.bashrc and the standard personal initial‐
    ization file ~/.bashrc if the shell is interactive (see 
INVOCATION below).

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 1250109] Re: Please use dpkg-triggers for update-grub when installing or removing kernel packages

[Julian Andres Klode]

@Andy I'm unassigning you and changing the bug status as the initramfs
part has been resolved, update-initramfs does

if [ -n "$DPKG_MAINTSCRIPT_PACKAGE" ] && [ $# = 1 ] && [ "$1" = -u ]; then
if dpkg-trigger --no-await update-initramfs; then   
 
echo "update-initramfs: deferring update (trigger activated)"   
 
exit 0  
fi  
 
fi  
 

We can patch grub  to do the same

** Changed in: initramfs-tools (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

** Changed in: initramfs-tools (Ubuntu)
 Assignee: Andy Whitcroft (apw) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Andy Whitcroft (apw) => (unassigned)

** Changed in: grub2 (Ubuntu)
 Assignee: Andy Whitcroft (apw) => (unassigned)

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

Title:
  Please use dpkg-triggers for update-grub when installing or removing
  kernel packages

Status in grub2 package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in grub2 package in Debian:
  Won't Fix

Bug description:
  Currently the kernel package runs update-grub every time one is
  installed or removed.  This results in it being run a dozen times
  during a dist-upgrade, and this is rather time consuming and annoying.
  Please use a dpkg trigger to cause update-grub to be run only once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1250109/+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 1920933] Re: live desktop system booted with ip=dhcp has the right lease, hostname not set at all

[Benjamin Drung]

initramfs-tools >= 0.142ubuntu5 (in mantic) has the qemu-net autopkgtest
that covers this use case and it checks that the hostname is set
correctly.

Does your initramfs comes without /etc/hostname?

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

Title:
  live desktop system booted with ip=dhcp has the right lease, hostname
  not set at all

Status in initramfs-tools package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Here the cmdline:

  vmlinuz initrd=initrd rootfstype=nfs netboot=nfs
  nfsroot=162.38.151.26:/exports/focal-desktop boot=casper ip=dhcp
  fsck.mode=skip automatic-ubiquity
  url=http://162.38.151.26/preseed/fds/focal-efi.seed

  File /run/systemd/netif/leases/2:

  # This is private data. Do not parse.
  ADDRESS=162.38.80.32
  NETMASK=255.255.248.0
  ROUTER=162.38.80.1
  SERVER_ADDRESS=162.38.87.254
  NEXT_SERVER=162.38.151.26
  T1=7200
  T2=12600
  LIFETIME=14400
  DNS=162.38.151.23 162.38.151.24
  NTP=193.51.157.3
  DOMAINNAME=fdsetu.infra.domain.fr
  DOMAIN_SEARCH_LIST=infra.domain.fr fdsetu.infra.domain.fr
  HOSTNAME=focal-uefi
  CLIENTID=0152540071e1f2

  But the hostname is still the default one "ubuntu"

  $ hostnamectl
   Static hostname: ubuntu
 Icon name: computer-vm
   Chassis: vm
Machine ID: cbb8d889829d4e2594ab55a53749e7e9
   Boot ID: c93c8cc26fa040f6b010077e676bf7ec
Virtualization: kvm
  Operating System: Ubuntu 20.04.2 LTS
Kernel: Linux 5.8.0-43-generic
  Architecture: x86-64

  It should be "focal-uefi".
  I had the same issue with ubuntu server autoinstall

  See https://bugs.launchpad.net/subiquity/+bug/1905932

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.4
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperVersion: 1.445.1
  Date: Tue Mar 23 15:30:42 2021
  LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: vmlinuz initrd=initrd rootfstype=nfs netboot=nfs 
nfsroot=162.38.151.26:/exports/focal-desktop boot=casper ip=dhcp fsck.mode=skip 
automatic-ubiquity url=http://162.38.151.26/preseed/fds/focal-efi.seed
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.1
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-3.1
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1920933/+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 1941649] Re: switch to zstd by default breaks booting focal LTS kernel

[Benjamin Drung]

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  switch to zstd by default breaks booting focal LTS kernel

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  While trying to track down a behavior difference between focal and
  impish, I installed focal's kernel in an impish userspace and
  attempted to boot it. The boot failed, unable to find root. While GRUB
  reported that it had loaded the initramfs, no initramfs messages were
  emitted during boot. I tracked this down to initramfs-tools having
  switched to use zstd compression by default. zstd decompression does
  not appear to be supported by the LTS 5.4 kernel - it appears to have
  been added upstream in v5.9. I imagine this is likely to cause
  problems with partial-upgrade scenarios.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1941649/+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 1954320] Re: Add privacy screen modules to the initrd

[Benjamin Drung]

We can just use similar code in initramfs-tools now that we use dracut-
install from dracut.

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Add privacy screen modules to the initrd

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Jammy:
  Confirmed

Bug description:
  Starting with kernel 5.17 the kernel supports the builtin privacy
  screens built into the LCD panel of some new laptop models.

  This means that the drm drivers will now return -EPROBE_DEFER from
  their probe() method on models with a builtin privacy screen when the
  privacy screen provider driver has not been loaded yet.

  To avoid any regressions Ubuntu should modify its initrd generation
  tool to include privacy screen provider drivers in the initrd (at
  least on systems with a privacy screen), before 5.17 kernels start
  showing up in the Ubuntu repos.

  If this change is not made, then users using a graphical bootsplash
  (plymouth) will get an extra boot-delay of up to 8 seconds
  (DeviceTimeout in plymouthd.defaults) before plymouth will show and
  when using disk-encryption where the LUKS password is requested from
  the initrd, the system may fallback to text-mode after these 8
  seconds.

  I've written a patch with the necessary changes for dracut, which
  might be useful as an example for how to deal with this, see:
  https://github.com/dracutdevs/dracut/pull/1666

  ATM the only kms driver using privacy screens is the i915 driver and
  the only provider is the thinkpad_acpi driver. But both are likely to
  change (and change soon!), so the detection really should be made
  dynamic as has been done in the dracut patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1954320/+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 1958052] Re: Update-initramfs still shows missing drivers even if i already added drivers.

[Benjamin Drung]

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

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

** This bug has been marked a duplicate of bug 1943906
   warning about missing firmware is mostly just noise

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

Title:
  Update-initramfs still shows missing drivers even if i already added
  drivers.

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Update-initramfs still shows missing drivers even if i already added drivers.
  Bug #1958038 made about finding how to make automatic driver install. So i 
got driver, wifi working, but still update-initramfs thinks im missing some 
drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.13
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 04:34:51 2022
  InstallationDate: Installed on 2022-01-15 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958052/+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 1907310] Re: initramfs-tools ignores the FRAMEBUFFER option _again_

[Benjamin Drung]

I checked on Ubuntu 23.10: cryptsetup-initramfs sets FRAMEBUFFER=y in
/usr/share/initramfs-tools/conf-hooks.d/cryptsetup

So cryptsetup-initramfs enforces including the framebuffer modules.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  initramfs-tools ignores the FRAMEBUFFER option _again_

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  see lp:1561643 for the previous 3-year discussion having resulted in a
  (temporary) fix.

  Currently, running Ubuntu 21.04 Hirsute, I noticed +60MB growth in initrd 
files again.
  Doing lsinitramfs on these images, I found that they are happily stuffed with 
i915 and amdgpu modules, as well as with netronome nic firmwares which of 
course everyone surely needs, making initrd of 73 MB.
  That's with MODULES=dep and FRAMEBUFFER=n in 
/etc/initramfs-tools/initramfs.conf

  this does not happen with Ubuntu 20.04, with same options in initramfs.conf. 
  On my Focal system, initrd images have size of 12MB, with largest components 
being .so libraries and lvm executable.

  So, I would conclude that initramfs-tools reintroduced this
  misbehavior after 20.04 release but in some different way. Now trying
  to compare /usr/share/initramfs-tools content between 20.04 and 21.04.
  Probably the title of this bug will need to be changed. As I am not
  allowed to reopen lp:1561643 , I am creating a new bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1907310/+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 1943906] Re: warning about missing firmware is mostly just noise

[Benjamin Drung]

initramfs-tools 0.142ubuntu11 in mantic uses dracut-install for
installing the kernel modules (see bug #2031185) and those warning are
gone now.

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Fix Released

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

Title:
  warning about missing firmware is mostly just noise

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  Every time an LTS release gets a new backport kernel, we see reports
  from concerned users when they see something like this:

  W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for 
module i915

  and since we don't do full backports of linux-firmware this is just
  noise for the users. Could there be a way to warn only during the
  development phase? That way the missing firmware would more likely get
  added for the primary kernel prior to release, but not warn when using
  a newer backport/mainline kernel.

  (in this case the guc firmware would be pointless to add to l-f, since
  while they would be loaded, the feature they add is not enabled by
  default)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: initramfs-tools 0.140ubuntu6
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 17 08:47:46 2021
  InstallationDate: Installed on 2018-02-06 (1318 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180206)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to impish on 2020-09-02 (379 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1943906/+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 1946475] Re: USB support in intram broken for raspberry 4 after udpate

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Do you still have the problem or did you upgrade to Ubuntu 20.04 or
22.04?

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  USB support in intram broken for raspberry 4 after udpate

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have a Raspberry PI 4 running Ubuntu 18.04.

  Recently I apt-get upgrade'd it which resulted in new kernel and
  ramdisk.

  My initramdisk now does not recognize USB devices.

  I can see the modules are there (usb-storage uas), and I can load
  them, but no devices come up, in particular USB storage.

  I have looked at the recent commits to this package, and I wonder if
  the following commit may have had something to do, as it is recent and
  deals with device firmware and resuming devices..

  https://git.launchpad.net/ubuntu/+source/initramfs-
  tools/commit/?id=3faf13b2b7217c05a20d649b10920f828b3c83c3

  I really don't understand what is the process until USB devices are
  instantiated as /dev/disk/... so I am a bit lost in finding out
  exactly what is not working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1946475/+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 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)

[Benjamin Drung]

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Microsoft Surface Laptop 4 keyboard not available during early boot
  (can't enter disk unlock password)

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With 22.04 LTS, fully updated, freshly built initrd's for both 5.15
  (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge)
  kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model
  1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is
  not available during early boot, such as for entering a full disk
  encryption passphrase. Just pressing enter at said prompt has no
  effect. Connecting an external keyboard via USB and typing the
  passphrase from there works around it.

  The keyboard works fine on the fully booted system.

  Secure boot is disabled on this system.

  
  --

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 13 00:53:34 2023
  Dependencies:
   adduser 3.118ubuntu5
   apt 2.4.8
   apt-utils 2.4.8
   busybox-initramfs 1:1.30.1-7ubuntu3
   ca-certificates 20211016ubuntu0.22.04.1
   coreutils 8.32-4.1ubuntu1
   cpio 2.13+dfsg-7
   debconf 1.5.79ubuntu1
   debconf-i18n 1.5.79ubuntu1
   dmsetup 2:1.02.175-2.1ubuntu4
   dpkg 1.21.1ubuntu2.1
   gcc-12-base 12.1.0-2ubuntu1~22.04
   gettext-base 0.21-4ubuntu4
   gpgv 2.2.27-3ubuntu2.1
   grub-common 2.06-2ubuntu7.1
   grub-gfxpayload-lists 0.7
   grub-pc 2.06-2ubuntu7.1
   grub-pc-bin 2.06-2ubuntu7.1
   grub2-common 2.06-2ubuntu7.1
   init-system-helpers 1.62
   initramfs-tools 0.140ubuntu13.1
   initramfs-tools-bin 0.140ubuntu13.1
   initramfs-tools-core 0.140ubuntu13.1
   klibc-utils 2.0.10-4
   kmod 29-1ubuntu1
   libacl1 2.3.1-1
   libapt-pkg6.0 2.4.8
   libattr1 1:2.5.1-1build1
   libaudit-common 1:3.0.7-1build1
   libaudit1 1:3.0.7-1build1
   libblkid1 2.37.2-4ubuntu3
   libbrotli1 1.0.9-2build6
   libbz2-1.0 1.0.8-5build1
   libc6 2.35-0ubuntu3.1
   libcap-ng0 0.7.9-2.2build3
   libcap2 1:2.44-1build3
   libcom-err2 1.46.5-2ubuntu1.1
   libcrypt1 1:4.4.27-1
   libdb5.3 5.3.28+dfsg1-0.8ubuntu3
   libdevmapper1.02.1 2:1.02.175-2.1ubuntu4
   libefiboot1 37-6ubuntu2
   libefivar1 37-6ubuntu2
   libffi8 3.4.2-4
   libfreetype6 2.11.1+dfsg-1ubuntu0.1
   libfuse3-3 3.10.5-1build1
   libgcc-s1 12.1.0-2ubuntu1~22.04
   libgcrypt20 1.9.4-3ubuntu3
   libgmp10 2:6.2.1+dfsg-3ubuntu1
   libgnutls30 3.7.3-4ubuntu1.1
   libgpg-error0 1.43-3
   libgssapi-krb5-2 1.19.2-2ubuntu0.1
   libhogweed6 3.7.3-1build2
   libidn2-0 2.3.2-2build1
   libk5crypto3 1.19.2-2ubuntu0.1
   libkeyutils1 1.6.1-2ubuntu3
   libklibc 2.0.10-4
   libkmod2 29-1ubuntu1
   libkrb5-3 1.19.2-2ubuntu0.1
   libkrb5support0 1.19.2-2ubuntu0.1
   liblocale-gettext-perl 1.07-4build3
   liblz4-1 1.9.3-2build2
   liblzma5 5.2.5-2ubuntu1
   libmount1 2.37.2-4ubuntu3
   libnettle8 3.7.3-1build2
   libnsl2 1.3.0-2build2
   libp11-kit0 0.24.0-6build1
   libpam-modules 1.4.0-11ubuntu2.3
   libpam-modules-bin 1.4.0-11ubuntu2.3
   libpam0g 1.4.0-11ubuntu2.3
   libpcre2-8-0 10.39-3ubuntu0.1
   libpng16-16 1.6.37-3build5
   libseccomp2 2.5.3-2ubuntu2
   libselinux1 3.3-1build2
   libsemanage-common 3.3-1build2
   libsemanage2 3.3-1build2
   libsepol2 3.3-1build1
   libsmartcols1 2.37.2-4ubuntu3
   libssl3 3.0.2-0ubuntu1.8
   libstdc++6 12.1.0-2ubuntu1~22.04
   libsystemd0 249.11-0ubuntu3.6
   libtasn1-6 4.18.0-4build1
   libtext-charwidth-perl 0.04-10build3
   libtext-iconv-perl 1.7-7build3
   libtext-wrapi18n-perl 0.06-9
   libtinfo6 6.3-2
   libtirpc-common 1.3.2-2ubuntu0.1
   libtirpc3 1.3.2-2ubuntu0.1
   libudev1 249.11-0ubuntu3.6
   libunistring2 1.0-1
   libuuid1 2.37.2-4ubuntu3
   libxxhash0 0.8.1-1
   libzstd1 1.4.8+dfsg-3build1
   linux-base 4.5ubuntu9
   linux-modules-5.19.0-28-generic 5.19.0-28.29~22.04.1
   logsave 1.46.5-2ubuntu1.1
   lsb-base 11.1.0ubuntu4
   mount 2.37.2-4ubuntu3
   openssl 3.0.2-0ubuntu1.8
   os-prober 1.79ubuntu2
   passwd 1:4.8.1-2ubuntu2.1
   perl-base 5.34.0-3ubuntu1.1
   sensible-utils 0.0.17
   systemd-hwe-hwdb 249.11.2
   tar 1.34+dfsg-1build3
   ubuntu-keyring 2021.03.26
   ucf 3.0043
   udev 249.11-0ubuntu3.6
   util-linux 2.37.2-4ubuntu3
   uuid-runtime 2.37.2-4ubuntu3
   zlib1g 1:1.2.11.dfsg-2ubuntu9.2
   zstd 1.4.8+dfsg-3build1
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-02-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Package: linux-image-5.19.0-28-generic 5.19.0-28.29~22.04.1
  PackageArchitecture: amd64
  ProcCpuinfoMinimal:
   processor: 7
   vendor_id: GenuineIntel
   cpu family   : 6
   model: 140
 

[Touch-packages] [Bug 2038512] Re: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image

[Benjamin Drung]

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Fix Committed

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [Mediatek] mt8195-demo: please help to include these MediaTek drivers
  in initrd.img in CD/DVD release image

Status in initramfs-tools package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  Peripheral probe failure for MediaTek boards 'mt8195-demo' and 
'genio-1200-evk'.

  [Ubuntu Version]
  Jammy

  [initramfs-tools]
  0.140ubuntu13.4

  [Kernel version]
  5.15 -> 6.2
  (Generate initrd.img-6.2.0 on 5.15 kernel.)

  [Fix]
  I've used 'dracut' to examing the driver dependencies for boards 
'mt8195-demo' and 'genio-1200-evk'.
  It is able to buot into console and use USB port3.
  Hope these drivers could help to run installer with USB disk in next daily 
build.

  Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if
  just simply add driver lists in '/etc/modules',
  '/etc/modprobe.d/mediatek.conf' or '/etc/modules-
  load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems
  this tool will include more common framework drivers into initrd.img.

  [MediaTek relate drivers]
  file: mediatek-drivers-for-mt8195-demo-bringup.txt
  (Not listed in probing sequence)

  i2c-mt65xx
  spi-mt65xx
  reset-ti-syscon
  mt6397
  rtc-mt6397
  mtk-pmic-wrap
  mt6315-regulator
  spmi-mtk-pmif
  mtk_scp_ipi
  mediatek-drm
  mtk-vcodec-dec
  mtk-vcodec-enc
  mtk_jpeg
  mtk-vcodec-common
  mtk-jpeg-enc-hw
  mtk-vpu
  mtk-jpeg-dec-hw
  mtk-cmdq-helper
  mtk-cmdq-helper
  mtk-cmdq-mailbox
  mtk-mdp3
  phy-mtk-mipi-dsi-drv
  btmtk
  leds-mt6360
  tcpci_mt6360
  mt6360_charger
  mt6360-regulator
  mt6360-core
  mt6359-regulator
  mt6360-adc
  snd-soc-mt8195-afe
  snd-soc-mtk-common
  snd-soc-dmic
  dwmac-mediatek
  stmmac-platform
  stmmac
  mtk-rng
  mtk_scp
  mtk_rpmsg
  pwm-mediatek
  pwm-mtk-disp
  nvmem_mtk-efuse
  mtk-sd
  cqhci
  phy-mtk-tphy
  mtu3
  xhci-mtk-hcd
  phy-mtk-pcie
  pcie-mediatek-gen3

  [lsmod log]
  file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt

  [Other info]
  effected kernel (6.2-latest)
  ubuntu kernel for lunar, and Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+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 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs

[Benjamin Drung]

intel_lpss_pci is also needed for the Surface Laptop 4 (see bug
#2007050).

** Changed in: initramfs-tools (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1)
  due to missing kernel modules in initramfs

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Mantic:
  New

Bug description:
  I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root
  partition, which I decrypt via passphrase during boot, at the "Please
  unlock disk nvme0n1p4_crypt" prompt.

  Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10
  "Mantic", the built-in keyboard doesn't work for entering the
  passphrase.

  Quickest workaround: plug in a USB keyboard for entering the
  passphrase.

  Workaround: add the following modules to "/etc/initramfs-
  tools/modules":

  spi_pxa2xx_platform
  intel_lpss_pci

  ... then "sudo update-initramfs -u".

  I found that both kernel modules were required to get the keyboard
  recognised in initramfs.

  I did a bit of digging into what changed for 23.10. It could
  potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do
  not install ARM/RISCV specific modules on other architectures".

  I had a look into how dracut handles it. Turns out that they
  specifically include "spi_pxa2xx_platform" after reporting a similar
  bug report in Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=2166209

  I don't know how (if?) they handle the 2nd module, "intel_lpss_pci".

  Anyway, I don't need an immediate fix since the workaround works for
  me. Just posting this for further investigation, and for any other
  MacBook Pro users in the same situation. Thanks for working on Ubuntu,
  I think you're all amazing!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+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 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)

[Benjamin Drung]

Forwarded adding surface_aggregator_registry to dracut:
https://github.com/dracutdevs/dracut/pull/2558

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

Title:
  Microsoft Surface Laptop 4 keyboard not available during early boot
  (can't enter disk unlock password)

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With 22.04 LTS, fully updated, freshly built initrd's for both 5.15
  (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge)
  kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model
  1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is
  not available during early boot, such as for entering a full disk
  encryption passphrase. Just pressing enter at said prompt has no
  effect. Connecting an external keyboard via USB and typing the
  passphrase from there works around it.

  The keyboard works fine on the fully booted system.

  Secure boot is disabled on this system.

  
  --

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 13 00:53:34 2023
  Dependencies:
   adduser 3.118ubuntu5
   apt 2.4.8
   apt-utils 2.4.8
   busybox-initramfs 1:1.30.1-7ubuntu3
   ca-certificates 20211016ubuntu0.22.04.1
   coreutils 8.32-4.1ubuntu1
   cpio 2.13+dfsg-7
   debconf 1.5.79ubuntu1
   debconf-i18n 1.5.79ubuntu1
   dmsetup 2:1.02.175-2.1ubuntu4
   dpkg 1.21.1ubuntu2.1
   gcc-12-base 12.1.0-2ubuntu1~22.04
   gettext-base 0.21-4ubuntu4
   gpgv 2.2.27-3ubuntu2.1
   grub-common 2.06-2ubuntu7.1
   grub-gfxpayload-lists 0.7
   grub-pc 2.06-2ubuntu7.1
   grub-pc-bin 2.06-2ubuntu7.1
   grub2-common 2.06-2ubuntu7.1
   init-system-helpers 1.62
   initramfs-tools 0.140ubuntu13.1
   initramfs-tools-bin 0.140ubuntu13.1
   initramfs-tools-core 0.140ubuntu13.1
   klibc-utils 2.0.10-4
   kmod 29-1ubuntu1
   libacl1 2.3.1-1
   libapt-pkg6.0 2.4.8
   libattr1 1:2.5.1-1build1
   libaudit-common 1:3.0.7-1build1
   libaudit1 1:3.0.7-1build1
   libblkid1 2.37.2-4ubuntu3
   libbrotli1 1.0.9-2build6
   libbz2-1.0 1.0.8-5build1
   libc6 2.35-0ubuntu3.1
   libcap-ng0 0.7.9-2.2build3
   libcap2 1:2.44-1build3
   libcom-err2 1.46.5-2ubuntu1.1
   libcrypt1 1:4.4.27-1
   libdb5.3 5.3.28+dfsg1-0.8ubuntu3
   libdevmapper1.02.1 2:1.02.175-2.1ubuntu4
   libefiboot1 37-6ubuntu2
   libefivar1 37-6ubuntu2
   libffi8 3.4.2-4
   libfreetype6 2.11.1+dfsg-1ubuntu0.1
   libfuse3-3 3.10.5-1build1
   libgcc-s1 12.1.0-2ubuntu1~22.04
   libgcrypt20 1.9.4-3ubuntu3
   libgmp10 2:6.2.1+dfsg-3ubuntu1
   libgnutls30 3.7.3-4ubuntu1.1
   libgpg-error0 1.43-3
   libgssapi-krb5-2 1.19.2-2ubuntu0.1
   libhogweed6 3.7.3-1build2
   libidn2-0 2.3.2-2build1
   libk5crypto3 1.19.2-2ubuntu0.1
   libkeyutils1 1.6.1-2ubuntu3
   libklibc 2.0.10-4
   libkmod2 29-1ubuntu1
   libkrb5-3 1.19.2-2ubuntu0.1
   libkrb5support0 1.19.2-2ubuntu0.1
   liblocale-gettext-perl 1.07-4build3
   liblz4-1 1.9.3-2build2
   liblzma5 5.2.5-2ubuntu1
   libmount1 2.37.2-4ubuntu3
   libnettle8 3.7.3-1build2
   libnsl2 1.3.0-2build2
   libp11-kit0 0.24.0-6build1
   libpam-modules 1.4.0-11ubuntu2.3
   libpam-modules-bin 1.4.0-11ubuntu2.3
   libpam0g 1.4.0-11ubuntu2.3
   libpcre2-8-0 10.39-3ubuntu0.1
   libpng16-16 1.6.37-3build5
   libseccomp2 2.5.3-2ubuntu2
   libselinux1 3.3-1build2
   libsemanage-common 3.3-1build2
   libsemanage2 3.3-1build2
   libsepol2 3.3-1build1
   libsmartcols1 2.37.2-4ubuntu3
   libssl3 3.0.2-0ubuntu1.8
   libstdc++6 12.1.0-2ubuntu1~22.04
   libsystemd0 249.11-0ubuntu3.6
   libtasn1-6 4.18.0-4build1
   libtext-charwidth-perl 0.04-10build3
   libtext-iconv-perl 1.7-7build3
   libtext-wrapi18n-perl 0.06-9
   libtinfo6 6.3-2
   libtirpc-common 1.3.2-2ubuntu0.1
   libtirpc3 1.3.2-2ubuntu0.1
   libudev1 249.11-0ubuntu3.6
   libunistring2 1.0-1
   libuuid1 2.37.2-4ubuntu3
   libxxhash0 0.8.1-1
   libzstd1 1.4.8+dfsg-3build1
   linux-base 4.5ubuntu9
   linux-modules-5.19.0-28-generic 5.19.0-28.29~22.04.1
   logsave 1.46.5-2ubuntu1.1
   lsb-base 11.1.0ubuntu4
   mount 2.37.2-4ubuntu3
   openssl 3.0.2-0ubuntu1.8
   os-prober 1.79ubuntu2
   passwd 1:4.8.1-2ubuntu2.1
   perl-base 5.34.0-3ubuntu1.1
   sensible-utils 0.0.17
   systemd-hwe-hwdb 249.11.2
   tar 1.34+dfsg-1build3
   ubuntu-keyring 2021.03.26
   ucf 3.0043
   udev 249.11-0ubuntu3.6
   util-linux 2.37.2-4ubuntu3
   uuid-runtime 2.37.2-4ubuntu3
   zlib1g 1:1.2.11.dfsg-2ubuntu9.2
   zstd 1.4.8+dfsg-3build1
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-02-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Package: linux-image-5.19.0-28-generic 5.19.0-28.29~22.04.1
  PackageArchitecture: amd64
  ProcCpuinfoMinimal:
   processor: 7
   vendor_id: GenuineIntel
   cpu family   : 6
   model  

[Touch-packages] [Bug 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)

[Benjamin Drung]

I checked the included modules on Ubuntu 23.10 (linux 6.5.0-10-generic)
and following modules are included:

8250_dw
pinctrl_tigerlake (pinctrl-tigerlake.ko)
surface_aggregator
surface_hid
surface_hid_core

Following modules are not included, but will be included by the fix for
bug #2042710:

intel_lpss
intel_lpss_pci

Following module needs to be included (also dracut is affected):

surface_aggregator_registry

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

Title:
  Microsoft Surface Laptop 4 keyboard not available during early boot
  (can't enter disk unlock password)

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With 22.04 LTS, fully updated, freshly built initrd's for both 5.15
  (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge)
  kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model
  1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is
  not available during early boot, such as for entering a full disk
  encryption passphrase. Just pressing enter at said prompt has no
  effect. Connecting an external keyboard via USB and typing the
  passphrase from there works around it.

  The keyboard works fine on the fully booted system.

  Secure boot is disabled on this system.

  
  --

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 13 00:53:34 2023
  Dependencies:
   adduser 3.118ubuntu5
   apt 2.4.8
   apt-utils 2.4.8
   busybox-initramfs 1:1.30.1-7ubuntu3
   ca-certificates 20211016ubuntu0.22.04.1
   coreutils 8.32-4.1ubuntu1
   cpio 2.13+dfsg-7
   debconf 1.5.79ubuntu1
   debconf-i18n 1.5.79ubuntu1
   dmsetup 2:1.02.175-2.1ubuntu4
   dpkg 1.21.1ubuntu2.1
   gcc-12-base 12.1.0-2ubuntu1~22.04
   gettext-base 0.21-4ubuntu4
   gpgv 2.2.27-3ubuntu2.1
   grub-common 2.06-2ubuntu7.1
   grub-gfxpayload-lists 0.7
   grub-pc 2.06-2ubuntu7.1
   grub-pc-bin 2.06-2ubuntu7.1
   grub2-common 2.06-2ubuntu7.1
   init-system-helpers 1.62
   initramfs-tools 0.140ubuntu13.1
   initramfs-tools-bin 0.140ubuntu13.1
   initramfs-tools-core 0.140ubuntu13.1
   klibc-utils 2.0.10-4
   kmod 29-1ubuntu1
   libacl1 2.3.1-1
   libapt-pkg6.0 2.4.8
   libattr1 1:2.5.1-1build1
   libaudit-common 1:3.0.7-1build1
   libaudit1 1:3.0.7-1build1
   libblkid1 2.37.2-4ubuntu3
   libbrotli1 1.0.9-2build6
   libbz2-1.0 1.0.8-5build1
   libc6 2.35-0ubuntu3.1
   libcap-ng0 0.7.9-2.2build3
   libcap2 1:2.44-1build3
   libcom-err2 1.46.5-2ubuntu1.1
   libcrypt1 1:4.4.27-1
   libdb5.3 5.3.28+dfsg1-0.8ubuntu3
   libdevmapper1.02.1 2:1.02.175-2.1ubuntu4
   libefiboot1 37-6ubuntu2
   libefivar1 37-6ubuntu2
   libffi8 3.4.2-4
   libfreetype6 2.11.1+dfsg-1ubuntu0.1
   libfuse3-3 3.10.5-1build1
   libgcc-s1 12.1.0-2ubuntu1~22.04
   libgcrypt20 1.9.4-3ubuntu3
   libgmp10 2:6.2.1+dfsg-3ubuntu1
   libgnutls30 3.7.3-4ubuntu1.1
   libgpg-error0 1.43-3
   libgssapi-krb5-2 1.19.2-2ubuntu0.1
   libhogweed6 3.7.3-1build2
   libidn2-0 2.3.2-2build1
   libk5crypto3 1.19.2-2ubuntu0.1
   libkeyutils1 1.6.1-2ubuntu3
   libklibc 2.0.10-4
   libkmod2 29-1ubuntu1
   libkrb5-3 1.19.2-2ubuntu0.1
   libkrb5support0 1.19.2-2ubuntu0.1
   liblocale-gettext-perl 1.07-4build3
   liblz4-1 1.9.3-2build2
   liblzma5 5.2.5-2ubuntu1
   libmount1 2.37.2-4ubuntu3
   libnettle8 3.7.3-1build2
   libnsl2 1.3.0-2build2
   libp11-kit0 0.24.0-6build1
   libpam-modules 1.4.0-11ubuntu2.3
   libpam-modules-bin 1.4.0-11ubuntu2.3
   libpam0g 1.4.0-11ubuntu2.3
   libpcre2-8-0 10.39-3ubuntu0.1
   libpng16-16 1.6.37-3build5
   libseccomp2 2.5.3-2ubuntu2
   libselinux1 3.3-1build2
   libsemanage-common 3.3-1build2
   libsemanage2 3.3-1build2
   libsepol2 3.3-1build1
   libsmartcols1 2.37.2-4ubuntu3
   libssl3 3.0.2-0ubuntu1.8
   libstdc++6 12.1.0-2ubuntu1~22.04
   libsystemd0 249.11-0ubuntu3.6
   libtasn1-6 4.18.0-4build1
   libtext-charwidth-perl 0.04-10build3
   libtext-iconv-perl 1.7-7build3
   libtext-wrapi18n-perl 0.06-9
   libtinfo6 6.3-2
   libtirpc-common 1.3.2-2ubuntu0.1
   libtirpc3 1.3.2-2ubuntu0.1
   libudev1 249.11-0ubuntu3.6
   libunistring2 1.0-1
   libuuid1 2.37.2-4ubuntu3
   libxxhash0 0.8.1-1
   libzstd1 1.4.8+dfsg-3build1
   linux-base 4.5ubuntu9
   linux-modules-5.19.0-28-generic 5.19.0-28.29~22.04.1
   logsave 1.46.5-2ubuntu1.1
   lsb-base 11.1.0ubuntu4
   mount 2.37.2-4ubuntu3
   openssl 3.0.2-0ubuntu1.8
   os-prober 1.79ubuntu2
   passwd 1:4.8.1-2ubuntu2.1
   perl-base 5.34.0-3ubuntu1.1
   sensible-utils 0.0.17
   systemd-hwe-hwdb 249.11.2
   tar 1.34+dfsg-1build3
   ubuntu-keyring 2021.03.26
   ucf 3.0043
   udev 249.11-0ubuntu3.6
   util-linux 2.37.2-4ubuntu3
   uuid-runtime 2.37.2-4ubuntu3
   zlib1g 1:1.2.11.dfsg-2ubuntu9.2
   zstd 1.4.8+dfsg-3build1
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed 

[Touch-packages] [Bug 1097467] Re: bash does not fulfill --rcfile option properly

[Dave Jones]

Doh, I always forget something...

** Patch added: "1097467-2.debdiff"
   
https://bugs.launchpad.net/gnubash/+bug/1097467/+attachment/5719318/+files/1097467-2.debdiff

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  New
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

    --rcfile file
    Execute commands from file instead of the system wide 
initialization file /etc/bash.bashrc and the standard personal initial‐
    ization file ~/.bashrc if the shell is interactive (see 
INVOCATION below).

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 2043442] Re: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

[Gunnar Hjalmarsson]

Thanks for your report.

I see Plasma and Wayland, which reminds me of
 and .

* Have you applied the IBus Wayland virtual keyboard?

* If you have, can you please run this command:

  im-config -n none

  and reboot, and then let us know if that improves things.

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

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

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

Title:
  /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  Apport captured a system freeze [crash] which required a hard reboot.
  However I could not confirm that the report was successfully uploaded.

  The /var/log/apport.log entry is as follows.
  
  ERROR: apport (pid 17772) 2023-11-13 17:17:02,197: this executable already 
crashed 2 times, ignoring
  INFO: apport (pid 27019) 2023-11-13 21:07:39,820: called for pid 17786, 
signal 11, core limit 0, dump mode 1
  INFO: apport (pid 27019) 2023-11-13 21:07:39,821: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
  ERROR: apport (pid 27019) 2023-11-13 21:07:40,821: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  INFO: apport (pid 27019) 2023-11-13 21:07:42,687: wrote report 
/var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
  INFO: apport (pid 29410) 2023-11-13 21:38:11,084: called for pid 27746, 
signal 11, core limit 0, dump mode 1
  INFO: apport (pid 29410) 2023-11-13 21:38:11,085: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
  ERROR: apport (pid 29410) 2023-11-13 21:38:12,085: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  Note:The last line may explain why I could not verify the file
  upload when I performed the following proceedure per:
  https://help.ubuntu.com/community/ReportingBugs

  ---
  luigi@l-g905:~$ ubuntu-bug /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash

  luigi@l-g905:~$ sudo cat /var/lib/whoopsie/whoopsie-id
  
7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80

  
https://errors.ubuntu.com/user/7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80:
 No such file or directory
  -

  
  This upload fialure seemed confirmed when in: 
https://answers.launchpad.net/ubuntu/+questions?
  a search found no Questions matching "ibus-ui-gtk3" for Ubuntu
  "ibus-ui-gtk3" is not mentioned in the release notes bugs section.

  In
  https://errors.ubuntu.com/?release=Ubuntu%2023.10=day
  text Searches for _usr_libexec_ibus-ui-gtk3 and the "Whoopsie-id" above both 
returned "phrase not found"

  I reproduced the executable failure using Terminal with these results
  --
  ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

  Returns:
  ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

  (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
  assertion '(offset + len) <= string_length' failed

  (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
  assertion '(offset + len) <= string_length' failed

  ** (ibus-ui-gtk3:9353): ERROR **: 23:11:04.236: No input_method global

  Trace/breakpoint trap (core dumped)
  -

  I am attaching the _usr_libexec_ibus-ui-gtk3.1000.crash file
  /var/crash/ _ust_libexec_ibus-ui-gtk3.1000.crash (3.1 MiB - 1144 lines
  - modified on 11/13/23 9:07 PM - US-ASCII)

  Platform Information 
  Operating System: Ubuntu Studio 23.10
  KDE Plasma Version:   5.27.8
  KDE Frameworks Version:   5.110.0
  Qt Version:   5.15.10
  Kernel Version:   6.5.0-10-lowlatency (64-bit)
  Graphics Platform:Wayland
  Processors:   24 × AMD Ryzen 9 7900X 12-Core Processor
  Memory:   31.0 GiB of RAM
  Graphics Processor:   NV172
  Manufacturer: MicroElectronics
  Product Name: G905
  System Version:   1.0

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


-- 
Mailing list: https://launchpad.net/~touch-packages

[Touch-packages] [Bug 2038512] Re: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image

[Benjamin Drung]

Forwarded adding System Power Management Interface (SPMI) modules to
dracut: https://github.com/dracutdevs/dracut/pull/2557

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

Title:
  [Mediatek] mt8195-demo: please help to include these MediaTek drivers
  in initrd.img in CD/DVD release image

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  [Impact]
  Peripheral probe failure for MediaTek boards 'mt8195-demo' and 
'genio-1200-evk'.

  [Ubuntu Version]
  Jammy

  [initramfs-tools]
  0.140ubuntu13.4

  [Kernel version]
  5.15 -> 6.2
  (Generate initrd.img-6.2.0 on 5.15 kernel.)

  [Fix]
  I've used 'dracut' to examing the driver dependencies for boards 
'mt8195-demo' and 'genio-1200-evk'.
  It is able to buot into console and use USB port3.
  Hope these drivers could help to run installer with USB disk in next daily 
build.

  Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if
  just simply add driver lists in '/etc/modules',
  '/etc/modprobe.d/mediatek.conf' or '/etc/modules-
  load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems
  this tool will include more common framework drivers into initrd.img.

  [MediaTek relate drivers]
  file: mediatek-drivers-for-mt8195-demo-bringup.txt
  (Not listed in probing sequence)

  i2c-mt65xx
  spi-mt65xx
  reset-ti-syscon
  mt6397
  rtc-mt6397
  mtk-pmic-wrap
  mt6315-regulator
  spmi-mtk-pmif
  mtk_scp_ipi
  mediatek-drm
  mtk-vcodec-dec
  mtk-vcodec-enc
  mtk_jpeg
  mtk-vcodec-common
  mtk-jpeg-enc-hw
  mtk-vpu
  mtk-jpeg-dec-hw
  mtk-cmdq-helper
  mtk-cmdq-helper
  mtk-cmdq-mailbox
  mtk-mdp3
  phy-mtk-mipi-dsi-drv
  btmtk
  leds-mt6360
  tcpci_mt6360
  mt6360_charger
  mt6360-regulator
  mt6360-core
  mt6359-regulator
  mt6360-adc
  snd-soc-mt8195-afe
  snd-soc-mtk-common
  snd-soc-dmic
  dwmac-mediatek
  stmmac-platform
  stmmac
  mtk-rng
  mtk_scp
  mtk_rpmsg
  pwm-mediatek
  pwm-mtk-disp
  nvmem_mtk-efuse
  mtk-sd
  cqhci
  phy-mtk-tphy
  mtu3
  xhci-mtk-hcd
  phy-mtk-pcie
  pcie-mediatek-gen3

  [lsmod log]
  file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt

  [Other info]
  effected kernel (6.2-latest)
  ubuntu kernel for lunar, and Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+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 2038512] Re: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image

[Benjamin Drung]

linux-modules-extra-6.5.0-10-generic ships four System Power Management
Interface (SPMI) modules on arm64:

drivers/spmi/hisi-spmi-controller.ko.zst
drivers/spmi/spmi-mtk-pmif.ko.zst
drivers/spmi/spmi-pmic-arb.ko.zst
drivers/spmi/spmi.ko.zst

See https://packages.ubuntu.com/mantic-updates/arm64/linux-modules-
extra-6.5.0-10-generic/filelist

Including those should not consume too much space.

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

Title:
  [Mediatek] mt8195-demo: please help to include these MediaTek drivers
  in initrd.img in CD/DVD release image

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  [Impact]
  Peripheral probe failure for MediaTek boards 'mt8195-demo' and 
'genio-1200-evk'.

  [Ubuntu Version]
  Jammy

  [initramfs-tools]
  0.140ubuntu13.4

  [Kernel version]
  5.15 -> 6.2
  (Generate initrd.img-6.2.0 on 5.15 kernel.)

  [Fix]
  I've used 'dracut' to examing the driver dependencies for boards 
'mt8195-demo' and 'genio-1200-evk'.
  It is able to buot into console and use USB port3.
  Hope these drivers could help to run installer with USB disk in next daily 
build.

  Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if
  just simply add driver lists in '/etc/modules',
  '/etc/modprobe.d/mediatek.conf' or '/etc/modules-
  load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems
  this tool will include more common framework drivers into initrd.img.

  [MediaTek relate drivers]
  file: mediatek-drivers-for-mt8195-demo-bringup.txt
  (Not listed in probing sequence)

  i2c-mt65xx
  spi-mt65xx
  reset-ti-syscon
  mt6397
  rtc-mt6397
  mtk-pmic-wrap
  mt6315-regulator
  spmi-mtk-pmif
  mtk_scp_ipi
  mediatek-drm
  mtk-vcodec-dec
  mtk-vcodec-enc
  mtk_jpeg
  mtk-vcodec-common
  mtk-jpeg-enc-hw
  mtk-vpu
  mtk-jpeg-dec-hw
  mtk-cmdq-helper
  mtk-cmdq-helper
  mtk-cmdq-mailbox
  mtk-mdp3
  phy-mtk-mipi-dsi-drv
  btmtk
  leds-mt6360
  tcpci_mt6360
  mt6360_charger
  mt6360-regulator
  mt6360-core
  mt6359-regulator
  mt6360-adc
  snd-soc-mt8195-afe
  snd-soc-mtk-common
  snd-soc-dmic
  dwmac-mediatek
  stmmac-platform
  stmmac
  mtk-rng
  mtk_scp
  mtk_rpmsg
  pwm-mediatek
  pwm-mtk-disp
  nvmem_mtk-efuse
  mtk-sd
  cqhci
  phy-mtk-tphy
  mtu3
  xhci-mtk-hcd
  phy-mtk-pcie
  pcie-mediatek-gen3

  [lsmod log]
  file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt

  [Other info]
  effected kernel (6.2-latest)
  ubuntu kernel for lunar, and Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Paride Legovini]

Actually, it would be nice if the new patch had some dep-3 headers (see
[1], `quilt --dep3` and maybe dep3changelog). In particular I think we
miss bug references an a description of the patch. Do you think you
could add the relevant ones? Thanks!

[1] https://dep-team.pages.debian.net/deps/dep3/

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  New
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

    --rcfile file
    Execute commands from file instead of the system wide 
initialization file /etc/bash.bashrc and the standard personal initial‐
    ization file ~/.bashrc if the shell is interactive (see 
INVOCATION below).

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 2043492] Re: Installed 23.10 on Huawei 16s. Speakers don't work. When I plug in headphones, the speakers work. the operating system seems to have the two switched. Also, on googl

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  Installed 23.10 on Huawei 16s.  Speakers don't work.  When I plug in
  headphones, the speakers work.  the operating system seems to have the
  two switched.  Also, on google meets, it cannot find a sound device.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No further information.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  noe2350 F pipewire
noe2357 F wireplumber
   /dev/snd/seq:noe2350 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 16:42:30 2023
  InstallationDate: Installed on 2023-11-01 (13 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.23
  dmi.board.asset.tag: N/A
  dmi.board.name: CREF-XX-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1010
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1010
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.23:bd11/08/2022:br1.23:efr1.23:svnHUAWEI:pnCREF-XX:pvrM1010:rvnHUAWEI:rnCREF-XX-PCB:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
  dmi.product.family: MateBook
  dmi.product.name: CREF-XX
  dmi.product.sku: C100
  dmi.product.version: M1010
  dmi.sys.vendor: HUAWEI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2043492/+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 2043215] Re: Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in Xorg.

[Peter Freeth]

Same problem. Under Xorg, the Wacom tablet can move the pointer but as
soon as I tap to click, the system locks up. Pressing alt tab a few
times restores movement to the pointer. The Wacom is therefore unusable
under Xorg. Sadly, in GIMP it's also unusable under Wayland as the
pointers are invisible.

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

Title:
  Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in
  Xorg.

Status in xorg package in Ubuntu:
  New

Bug description:
  There is more information on this issue: 
https://github.com/xournalpp/xournalpp/issues/5303
  and the other bug report that is linked there.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 10 07:17:22 2023
  DistUpgraded: 2023-11-06 20:32:35,715 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Fujitsu Limited. HD Graphics 5500 [10cf:1898]
  InstallationDate: Installed on 2021-05-25 (899 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=ce1b5a3a-3fee-4143-a385-d16e7d44c53a ro i8042.notimeout i8042.nomux 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to mantic on 2023-11-07 (3 days ago)
  dmi.bios.date: 12/21/2015
  dmi.bios.release: 1.15
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.15
  dmi.board.name: FJNB288
  dmi.board.vendor: FUJITSU
  dmi.board.version: D2
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.15:bd12/21/2015:br1.15:svnFUJITSU:pnLIFEBOOKT935:pvr:rvnFUJITSU:rnFJNB288:rvrD2:cvnFUJITSU:ct10:cvr:sku:
  dmi.product.name: LIFEBOOK T935
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2043215/+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 2043442] Re: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

[Paul White]

** Tags added: mantic

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

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

Title:
  /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

Status in ibus package in Ubuntu:
  New

Bug description:
  Apport captured a system freeze [crash] which required a hard reboot.
  However I could not confirm that the report was successfully uploaded.

  The /var/log/apport.log entry is as follows.
  
  ERROR: apport (pid 17772) 2023-11-13 17:17:02,197: this executable already 
crashed 2 times, ignoring
  INFO: apport (pid 27019) 2023-11-13 21:07:39,820: called for pid 17786, 
signal 11, core limit 0, dump mode 1
  INFO: apport (pid 27019) 2023-11-13 21:07:39,821: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
  ERROR: apport (pid 27019) 2023-11-13 21:07:40,821: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  INFO: apport (pid 27019) 2023-11-13 21:07:42,687: wrote report 
/var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
  INFO: apport (pid 29410) 2023-11-13 21:38:11,084: called for pid 27746, 
signal 11, core limit 0, dump mode 1
  INFO: apport (pid 29410) 2023-11-13 21:38:11,085: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
  ERROR: apport (pid 29410) 2023-11-13 21:38:12,085: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  Note:The last line may explain why I could not verify the file
  upload when I performed the following proceedure per:
  https://help.ubuntu.com/community/ReportingBugs

  ---
  luigi@l-g905:~$ ubuntu-bug /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash

  luigi@l-g905:~$ sudo cat /var/lib/whoopsie/whoopsie-id
  
7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80

  
https://errors.ubuntu.com/user/7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80:
 No such file or directory
  -

  
  This upload fialure seemed confirmed when in: 
https://answers.launchpad.net/ubuntu/+questions?
  a search found no Questions matching "ibus-ui-gtk3" for Ubuntu
  "ibus-ui-gtk3" is not mentioned in the release notes bugs section.

  In
  https://errors.ubuntu.com/?release=Ubuntu%2023.10=day
  text Searches for _usr_libexec_ibus-ui-gtk3 and the "Whoopsie-id" above both 
returned "phrase not found"

  I reproduced the executable failure using Terminal with these results
  --
  ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

  Returns:
  ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

  (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
  assertion '(offset + len) <= string_length' failed

  (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
  assertion '(offset + len) <= string_length' failed

  ** (ibus-ui-gtk3:9353): ERROR **: 23:11:04.236: No input_method global

  Trace/breakpoint trap (core dumped)
  -

  I am attaching the _usr_libexec_ibus-ui-gtk3.1000.crash file
  /var/crash/ _ust_libexec_ibus-ui-gtk3.1000.crash (3.1 MiB - 1144 lines
  - modified on 11/13/23 9:07 PM - US-ASCII)

  Platform Information 
  Operating System: Ubuntu Studio 23.10
  KDE Plasma Version:   5.27.8
  KDE Frameworks Version:   5.110.0
  Qt Version:   5.15.10
  Kernel Version:   6.5.0-10-lowlatency (64-bit)
  Graphics Platform:Wayland
  Processors:   24 × AMD Ryzen 9 7900X 12-Core Processor
  Memory:   31.0 GiB of RAM
  Graphics Processor:   NV172
  Manufacturer: MicroElectronics
  Product Name: G905
  System Version:   1.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2043442/+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 2043492] [NEW] Installed 23.10 on Huawei 16s. Speakers don't work. When I plug in headphones, the speakers work. the operating system seems to have the two switched. Also, on goo

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

No further information.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  noe2350 F pipewire
  noe2357 F wireplumber
 /dev/snd/seq:noe2350 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 14 16:42:30 2023
InstallationDate: Installed on 2023-11-01 (13 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2022
dmi.bios.release: 1.23
dmi.bios.vendor: HUAWEI
dmi.bios.version: 1.23
dmi.board.asset.tag: N/A
dmi.board.name: CREF-XX-PCB
dmi.board.vendor: HUAWEI
dmi.board.version: M1010
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1010
dmi.ec.firmware.release: 1.23
dmi.modalias: 
dmi:bvnHUAWEI:bvr1.23:bd11/08/2022:br1.23:efr1.23:svnHUAWEI:pnCREF-XX:pvrM1010:rvnHUAWEI:rnCREF-XX-PCB:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
dmi.product.family: MateBook
dmi.product.name: CREF-XX
dmi.product.sku: C100
dmi.product.version: M1010
dmi.sys.vendor: HUAWEI

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


** Tags: amd64 apport-bug mantic wayland-session
-- 
Installed 23.10 on Huawei 16s.  Speakers don't work.  When I plug in 
headphones, the speakers work.  the operating system seems to have the two 
switched.  Also, on google meets, it cannot find a sound device.
https://bugs.launchpad.net/bugs/2043492
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver in Ubuntu.

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

[Touch-packages] [Bug 2043442] [NEW] /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Apport captured a system freeze [crash] which required a hard reboot.
However I could not confirm that the report was successfully uploaded.

The /var/log/apport.log entry is as follows.

ERROR: apport (pid 17772) 2023-11-13 17:17:02,197: this executable already 
crashed 2 times, ignoring
INFO: apport (pid 27019) 2023-11-13 21:07:39,820: called for pid 17786, signal 
11, core limit 0, dump mode 1
INFO: apport (pid 27019) 2023-11-13 21:07:39,821: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
ERROR: apport (pid 27019) 2023-11-13 21:07:40,821: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

INFO: apport (pid 27019) 2023-11-13 21:07:42,687: wrote report 
/var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
INFO: apport (pid 29410) 2023-11-13 21:38:11,084: called for pid 27746, signal 
11, core limit 0, dump mode 1
INFO: apport (pid 29410) 2023-11-13 21:38:11,085: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
ERROR: apport (pid 29410) 2023-11-13 21:38:12,085: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

Note:The last line may explain why I could not verify the file
upload when I performed the following proceedure per:
https://help.ubuntu.com/community/ReportingBugs

---
luigi@l-g905:~$ ubuntu-bug /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash

luigi@l-g905:~$ sudo cat /var/lib/whoopsie/whoopsie-id
7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80

https://errors.ubuntu.com/user/7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80:
 No such file or directory
-


This upload fialure seemed confirmed when in: 
https://answers.launchpad.net/ubuntu/+questions?
a search found no Questions matching "ibus-ui-gtk3" for Ubuntu
"ibus-ui-gtk3" is not mentioned in the release notes bugs section.

In
https://errors.ubuntu.com/?release=Ubuntu%2023.10=day
text Searches for _usr_libexec_ibus-ui-gtk3 and the "Whoopsie-id" above both 
returned "phrase not found"

I reproduced the executable failure using Terminal with these results
--
~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

Returns:
~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

(ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
assertion '(offset + len) <= string_length' failed

(ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
assertion '(offset + len) <= string_length' failed

** (ibus-ui-gtk3:9353): ERROR **: 23:11:04.236: No input_method global

Trace/breakpoint trap (core dumped)
-

I am attaching the _usr_libexec_ibus-ui-gtk3.1000.crash file /var/crash/
_ust_libexec_ibus-ui-gtk3.1000.crash (3.1 MiB - 1144 lines - modified on
11/13/23 9:07 PM - US-ASCII)

Platform Information 
Operating System: Ubuntu Studio 23.10
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.0-10-lowlatency (64-bit)
Graphics Platform:  Wayland
Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor
Memory: 31.0 GiB of RAM
Graphics Processor: NV172
Manufacturer:   MicroElectronics
Product Name:   G905
System Version: 1.0

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


** Tags: apport bot-comment crash failure halt mantic system upload
-- 
/usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes
https://bugs.launchpad.net/bugs/2043442
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ibus 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 1097467] Re: bash does not fulfill --rcfile option properly

[Paride Legovini]

Thanks for digging into this issue and updating the relevant Debian bug,
refreshing the debdiff. This LGTM, tested locally, the manpage renders
fine. I am going to sponsor this.

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  New
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

    --rcfile file
    Execute commands from file instead of the system wide 
initialization file /etc/bash.bashrc and the standard personal initial‐
    ization file ~/.bashrc if the shell is interactive (see 
INVOCATION below).

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-settings - 23.10.6

---
ubuntu-settings (23.10.6) noble; urgency=medium

  * Remove ubuntu-raspi-settings{,-desktop,-server} packages; these are now
produced by the ubuntu-raspi-settings package (LP: #2039104)

 -- Dave Jones   Mon, 06 Nov 2023 09:21:35
+

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Fix Released

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Mantic:
  New

Bug description:
  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs

[Benjamin Drung]

Forwarded adding intel_lpss_pci to dracut:
https://github.com/dracutdevs/dracut/pull/2556

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

Title:
  Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1)
  due to missing kernel modules in initramfs

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools source package in Mantic:
  New

Bug description:
  I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root
  partition, which I decrypt via passphrase during boot, at the "Please
  unlock disk nvme0n1p4_crypt" prompt.

  Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10
  "Mantic", the built-in keyboard doesn't work for entering the
  passphrase.

  Quickest workaround: plug in a USB keyboard for entering the
  passphrase.

  Workaround: add the following modules to "/etc/initramfs-
  tools/modules":

  spi_pxa2xx_platform
  intel_lpss_pci

  ... then "sudo update-initramfs -u".

  I found that both kernel modules were required to get the keyboard
  recognised in initramfs.

  I did a bit of digging into what changed for 23.10. It could
  potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do
  not install ARM/RISCV specific modules on other architectures".

  I had a look into how dracut handles it. Turns out that they
  specifically include "spi_pxa2xx_platform" after reporting a similar
  bug report in Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=2166209

  I don't know how (if?) they handle the 2nd module, "intel_lpss_pci".

  Anyway, I don't need an immediate fix since the workaround works for
  me. Just posting this for further investigation, and for any other
  MacBook Pro users in the same situation. Thanks for working on Ubuntu,
  I think you're all amazing!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+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 2015562] Re: Segfault in dnsmasq when using certain static domain entries + DoH (bugfix possibly exists upstream)

[Miriam España Acebal]

The DEP-8 tests will be more suitable to be submitted to the development
version, so I'll split them from here.

While working on a more specific test for this instead of the ones
submitted for review, Sergio discovered that the error wasn't  enough
reproducible with the following

netflix-nov6.conf:
# Null  response on these domains
server=/netflix.com/#
address=/netflix.com/::
server=/netflix.net/#
address=/netflix.net/::
server=/nflxext.com/#
address=/nflxext.com/::

It needs another double line of server/address: with that, we always get
the segmentation fault.

The bad news are that the proposed patch doesn't mitigate the error...
so it would need another change introduced in upper versions. Looking
for that change now.

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

Title:
  Segfault in dnsmasq when using certain static domain entries + DoH
  (bugfix possibly exists upstream)

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  In Progress

Bug description:
  Hi folks,

  I've been using dnsmasq for my home DNS needs, which includes
  returning null entries for certain domain queries. The specific case
  in which I found this segfault was returning null  records for
  Netflix (to ensure Netflix does not try to use my IPv6 tunnel to
  egress traffic through).

  I've been using very simple configuration snippet to achieve this,
  this is attached as netflix-nov6.conf (the full file contains more
  entries).

  Ever since I've upgraded from Ubuntu 20.04 to 22.04, dnsmasq kept
  segfaulting at random occasions. I also attempted do an apt
  update&, but there are no newer versions of this package
  available.

  Further research into this issue showed that a surefire way to trigger
  this segfault was to go to a website blocked via this method (for
  testing purposes, a dig query works quite well). The segfault can be
  reproduced reliably, and always occurs after one or a few queries
  towards the "blocked" domain entries.

  I found a commit in the upstream dnsmasq git repo which seems to fix this 
issue, the fix made it into 2.87:
  
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=de372d6914ae20a1f9997815f258efbf3b14c39b

  Would it be possible to backport this into the version used in the
  current LTS Ubuntu release? Thanks!

  --

  $ lsb_release -d
  Description:  Ubuntu 22.04.2 LTS
  $ apt-cache policy dnsmasq
  dnsmasq:
    Installed: 2.86-1.1ubuntu0.2
    Candidate: 2.86-1.1ubuntu0.2
    Version table:
   *** 2.86-1.1ubuntu0.2 500
  500 http://de.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   2.86-1.1ubuntu0.1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy-security/universe amd64 
Packages
   2.86-1.1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages

  --

  Excerpt from the dnsmasq logs, with debugging enabled, after I loaded 
fast.com:
  Apr 07 13:47:41 budgie systemd[1]: Started dnsmasq - A lightweight DHCP and 
caching DNS server.
  Apr 07 13:47:42 budgie dnsmasq[109976]: query[type=65] 
fast.dradis.netflix.com from 192.168.10.82
  Apr 07 13:47:42 budgie dnsmasq[109976]: config error is REFUSED (EDE: network 
error)
  Apr 07 13:47:43 budgie dnsmasq[109976]: query[type=65] 
ichnaea-web.netflix.com from 192.168.10.82
  Apr 07 13:47:43 budgie systemd[1]: dnsmasq.service: Main process exited, 
code=dumped, status=11/SEGV
  Apr 07 13:47:43 budgie systemd[1]: dnsmasq.service: Failed with result 
'core-dump'.

  Core dump is also attached.

  Reproduction steps:
  - 1. Install dnsmasq on Ubuntu 22.04 (or any Ubuntu release using dnsmasq 
2.86)
  - 1.5. Configure one or multiple DNS servers for dnsmasq
  - 2. Copy netflix-nov6.conf into /etc/dnsmasq.d/
  - 3. Restart/reload dnsmasq
  - 3.5 Verify that dnsmasq resolves domains correctly:

  root@budgie:~# dig +short -tA ubuntu.com @127.0.0.1
  185.125.190.21
  185.125.190.20
  185.125.190.29
  root@budgie:~# dig +short -t ubuntu.com @127.0.0.1
  2620:2d:4000:1::28
  2620:2d:4000:1::26
  2620:2d:4000:1::27

  - 4. Perform a type65 / HTTPS recordtype query for netflix.com towards
  the dnsmasq server once or twice:

  root@budgie:~# dig +short -tTYPE65 netflix.com @127.0.0.1
  root@budgie:~# dig +short -tTYPE65 netflix.com @127.0.0.1
  ;; communications error to 127.0.0.1#53: timed out
  ;; communications error to 127.0.0.1#53: connection refused
  ;; communications error to 127.0.0.1#53: connection refused
  ;; no servers could be reached

  - 5. Check logs to verify segfault:

  Apr 07 14:03:28 budgie systemd[1]: Started dnsmasq - A lightweight DHCP and 
caching DNS server.
  Apr 07 14:03:32 budgie dnsmasq[111585]: query[type=65] netflix.com from 
127.0.0.1
  Apr 07 14:03:32 budgie dnsmasq[111585]: config error is REFUSED 

[Touch-packages] [Bug 1516025] Re: Realtek ALC3661 Alienware14 / Soundoutput / Jack

[kakarot23]

Investing basics lay the foundation for individuals seeking to navigate
the world of financial markets and wealth accumulation. At its core,
investing involves deploying capital with the expectation of generating
returns over time. https://thefinancialappetite.net/category/getting-
started/investing-basics/

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

Title:
  Realtek ALC3661 Alienware14 / Soundoutput / Jack

Status in ALSA driver:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When watching the following video (but also audio from other programs) with 
the volume at 100%, the audio loudness is lower in comparison to the same audio 
being played at 100% in Windows 10:
  https://www.youtube.com/watch?v=YQHsXMglC9A

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imran  1619 F pulseaudio
   /dev/snd/controlC1:  imran  1619 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov 13 18:08:07 2015
  HibernationDevice: RESUME=UUID=2401d43e-85ec-4c88-81c1-c597086504a1
  InstallationDate: Installed on 2015-11-07 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Alienware Alienware 14
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=a534221a-37cb-4092-8ce2-934940eede6d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A09
  dmi.board.name: 07MJ2Y
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09:
  dmi.product.name: Alienware 14
  dmi.product.version: A09
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1516025/+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 2043255] Re: Wayland user session terminates when screen is disabled on inactivity

[Timo Aaltonen]

** Package changed: wayland (Ubuntu) => mutter (Ubuntu)

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

Title:
  Wayland user session terminates when screen is disabled on inactivity

Status in mutter package in Ubuntu:
  New

Bug description:
  Reproducibly, the user is logged out the moment the screen gets
  disabled due to inactivity. Can be worked around by disabling the
  "screen disabling on inactivity" feature in the system settings.

  Issue started after upgrade from 23.04 to 23.10. Wayland is used.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 11 09:21:02 2023
  DistUpgraded: 2023-11-03 18:23:57,803 DEBUG icon theme changed, re-reading
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Lucienne [17aa:5097]
  InstallationDate: Installed on 2021-08-27 (806 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=86fa7801-2441-4de0-bdff-28c460a157ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (8 days ago)
  dmi.bios.date: 05/17/2021
  dmi.bios.release: 1.6
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1OET27W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20YHS00A00
  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.6
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1OET27W(1.06):bd05/17/2021:br1.6:efr1.6:svnLENOVO:pn20YHS00A00:pvrThinkPadE15Gen3:rvnLENOVO:rn20YHS00A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20YH_BU_Think_FM_ThinkPadE15Gen3:
  dmi.product.family: ThinkPad E15 Gen 3
  dmi.product.name: 20YHS00A00
  dmi.product.sku: LENOVO_MT_20YH_BU_Think_FM_ThinkPad E15 Gen 3
  dmi.product.version: ThinkPad E15 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043255/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Bug Watch Updater]

** Changed in: gnubash
   Status: Unknown => New

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  New
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

    --rcfile file
    Execute commands from file instead of the system wide 
initialization file /etc/bash.bashrc and the standard personal initial‐
    ization file ~/.bashrc if the shell is interactive (see 
INVOCATION below).

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Dave Jones]

** Patch added: "1097467-1.debdiff"
   
https://bugs.launchpad.net/gnubash/+bug/1097467/+attachment/5719274/+files/1097467-1.debdiff

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  Unknown
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

    --rcfile file
    Execute commands from file instead of the system wide 
initialization file /etc/bash.bashrc and the standard personal initial‐
    ization file ~/.bashrc if the shell is interactive (see 
INVOCATION below).

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 1097467] Re: bash does not fulfill --rcfile option properly

[Dave Jones]

It appears this has come up before, and was discussed upstream. [1] and
[2] cover discussion of whether --rcfile should ignore the system-wide
bashrc (SYS_BASHRC hereafter), with the conclusion from upstream that it
should not. [3] is an attempt by someone to fix this upstream by
modifying bash's behaviour, which is rejected by the upstream
developers. [4] and [5] are the upstream Debian bugs (which I'll link
this bug to).

At any rate, upstream bash devs have made their position quite clear:
the Debian-patched documentation is wrong, and the behaviour of bash is
as expected. So, the solution to this bug is to fix the documentation.
I'll propose an updated patch here and see if we can't put this decade-
old bug to bed!

I'll also try and rebase the noble patch upstream for Debian (there's
already a patch there, but it's predictably ancient).

[1]: https://lists.gnu.org/archive/html/bug-bash/2018-01/msg3.html

[2]: https://lists.gnu.org/archive/html/bug-bash/2009-05/msg00031.html

[3]: https://savannah.gnu.org/support/index.php?107950

[4]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516152

[5]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343673

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

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

** Also affects: gnubash via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516152
   Importance: Unknown
   Status: Unknown

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  Unknown
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

    --rcfile file
    Execute commands from file instead of the system wide 
initialization file /etc/bash.bashrc and the standard personal initial‐
    ization file ~/.bashrc if the shell is interactive (see 
INVOCATION below).

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs

[Terence Tan]

Thanks Benjamin for making the fix.

I'm happy if this targets Noble; I'm not overly familiar with the SRU
process.

Unsure how much of a real-world impact this bug has; it's users of
Ubuntu non-LTS, with a MacBook Pro of a certain year range, using
cryptsetup which I don't think is the default (?)

Speaking for myself, I did the manual edits to /etc/initramfs-
tools/modules and my system works now, so I'm happy to mark this bug as
resolved.

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

Title:
  Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1)
  due to missing kernel modules in initramfs

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools source package in Mantic:
  New

Bug description:
  I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root
  partition, which I decrypt via passphrase during boot, at the "Please
  unlock disk nvme0n1p4_crypt" prompt.

  Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10
  "Mantic", the built-in keyboard doesn't work for entering the
  passphrase.

  Quickest workaround: plug in a USB keyboard for entering the
  passphrase.

  Workaround: add the following modules to "/etc/initramfs-
  tools/modules":

  spi_pxa2xx_platform
  intel_lpss_pci

  ... then "sudo update-initramfs -u".

  I found that both kernel modules were required to get the keyboard
  recognised in initramfs.

  I did a bit of digging into what changed for 23.10. It could
  potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do
  not install ARM/RISCV specific modules on other architectures".

  I had a look into how dracut handles it. Turns out that they
  specifically include "spi_pxa2xx_platform" after reporting a similar
  bug report in Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=2166209

  I don't know how (if?) they handle the 2nd module, "intel_lpss_pci".

  Anyway, I don't need an immediate fix since the workaround works for
  me. Just posting this for further investigation, and for any other
  MacBook Pro users in the same situation. Thanks for working on Ubuntu,
  I think you're all amazing!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+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 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs

[Benjamin Drung]

I stripped the timestamp (sed -s 's/\[[0-9. ]*\] //') and sorted the
entries of the two dmesg outputs, but I did not find new entries in the
diff.

lspci shows that following devices are using the intel_lpss_pci kernel
module:

00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO I2C Controller #0 (rev 21)
00:15.2 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO I2C Controller #2 (rev 21)
00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO UART Controller #0 (rev 21)
00:1e.3 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO SPI Controller #1 (rev 21)

and I found this in the dmesg log:

input: Apple SPI Keyboard as /devices/pci:00/:00:1e.3/pxa2xx-
spi.3/spi_master/spi2/spi-APP000D:00/input/input4

which shows that the keyboard is connected via SPI on 00:1e.3.

That explains it. I will upload a fixed initramfs-tools to noble and
file a bug against dracut to include intel_lpss_pci. Thanks for your
investigation and help. Do you want to help on getting the SRU (see
https://wiki.ubuntu.com/StableReleaseUpdates) into mantic?

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

Title:
  Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1)
  due to missing kernel modules in initramfs

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools source package in Mantic:
  New

Bug description:
  I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root
  partition, which I decrypt via passphrase during boot, at the "Please
  unlock disk nvme0n1p4_crypt" prompt.

  Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10
  "Mantic", the built-in keyboard doesn't work for entering the
  passphrase.

  Quickest workaround: plug in a USB keyboard for entering the
  passphrase.

  Workaround: add the following modules to "/etc/initramfs-
  tools/modules":

  spi_pxa2xx_platform
  intel_lpss_pci

  ... then "sudo update-initramfs -u".

  I found that both kernel modules were required to get the keyboard
  recognised in initramfs.

  I did a bit of digging into what changed for 23.10. It could
  potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do
  not install ARM/RISCV specific modules on other architectures".

  I had a look into how dracut handles it. Turns out that they
  specifically include "spi_pxa2xx_platform" after reporting a similar
  bug report in Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=2166209

  I don't know how (if?) they handle the 2nd module, "intel_lpss_pci".

  Anyway, I don't need an immediate fix since the workaround works for
  me. Just posting this for further investigation, and for any other
  MacBook Pro users in the same situation. Thanks for working on Ubuntu,
  I think you're all amazing!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+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 2043114] Re: sshd segmentation fault on 20.04.6 (focal)

[Ivaylo Markov]

Yes, seems pretty consistent. I just tried it again before I write out
the reproduction steps, and it took maybe a couple of minutes.

The configuration is basically just:

sed -i.bak 's/#LogLevel INFO/LogLevel DEBUG/g' /etc/ssh/sshd_config
systemctl restart sshd

As for making enough connections to cause the issue, I use something
along the lines of:

parallel -j 99 -N0 "ssh root@example 'mount; sleep 1; cat /proc/cpuinfo;
free -h;  dd if=/dev/zero of=/dev/null bs=1 count=8192; mount -av; sleep
$(($RANDOM % 5)); lshw'"  ::: {1..5000}

It is essentially running random commands to simulate some sort of
activity on the machine. The amount of parallel connections (`-j 99`)
might need to be adjusted - too little connections won't trigger the
bug, too many can cause an OOM situation.

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

Title:
  sshd segmentation fault on 20.04.6 (focal)

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  We have a physical server running Ubuntu 20.04.6 LTS (amd64) and 
openssh-server 1:8.2p1-4ubuntu0.9. Sometimes sshd crashes with a segmentation 
fault on remote login with key authentication:
  [193107.651745] sshd[1229630]: segfault at 5557eba6a008 ip 7f2326a2ca53 
sp 7ffcba40c510 error 4 in libc-2.31.so[7f23269b8000+178000]

  We’ve changed only the following values in the stock sshd_config file:

  LogLevel DEBUG
  PasswordAuthentication no
  MaxStartups 100:30:100

  The server is used for automated software testing, and sometimes our test 
suite might make a large amount of SSH connections in a short period of time, 
which seems to be correlated with the crashes. But at the same time, I have to 
note that the connection count was not near the MaxStartups limit, and we’ve 
had crashes before adding that setting.
  Since the backtrace shows the debug logging function in the stack, we’re 
currently experimenting with using `LogLevel INFO` to try and isolate the issue.

  I am attaching the backtrace. I could provide the full dump file,
  although I am hesitant due to the possibility of private keys or other
  sensitive information leaking.

  # apt-cache policy openssh-server
  openssh-server:
Installed: 1:8.2p1-4ubuntu0.9
Candidate: 1:8.2p1-4ubuntu0.9
Version table:
   *** 1:8.2p1-4ubuntu0.9 500
  500 http://mirrors.storpool.com/ubuntu/archive focal-updates/main 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:8.2p1-4 500
  500 http://mirrors.storpool.com/ubuntu/archive focal/main amd64 
Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Package: openssh-server 1:8.2p1-4ubuntu0.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-128.144-generic 5.4.210
  Tags:  focal
  Uname: Linux 5.4.0-128-generic x86_64
  UpgradeStatus: Upgraded to focal on 2021-01-13 (1030 days ago)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2043114/+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