[Bug 2065579] [NEW] [UBUNTU 22.04] OS guest boot issues on 9p filesystem

You have been subscribed to a public bug:

=== Reported by <d.herrendoerfer@de.ibm.com> - 2024-05-13 03:53:01 ===

---Problem Description---
OS guest boot issues on 9p filesystem due to unix domain sockets open failure

Contact Information = d.herrendoerfer@de.ibm.com

Machine Type = 3931-7G4

---uname output---
5.15.0-92-generic #102-Ubuntu SMP Wed Jan 10 09:35:24 UTC 2024 s390x s390x s390x GNU/Linux

---Steps to Reproduce---
#!/bin/bash

# Cleanup target dir
[ -d ./target ] && rm -rf target
mkdir target

# Add configuration updates
mkdir -p ./target/etc/initramfs-tools/
echo 9p >> ./target/etc/initramfs-tools/modules
echo 9pnet_virtio >> ./target/etc/initramfs-tools/modules

# Add the test script
cat > ./target/test_init << EOF
#!/bin/bash

echo "Test for unix domain sockets"

nc -Ul /socket &
sleep 1
echo "Sockets work" | nc -UN /socket || echo "Sockets fail"

echo o > /proc/sysrq-trigger
sleep 999
EOF
chmod 700 ./target/test_init

# Create an Ubuntu 23.10 around it
echo "Creating Ubuntu target OS"
debootstrap --variant=minbase\
--include=udev,kmod,initramfs-tools,systemd,netcat-openbsd,linux-image-generic \
--exclude=man,bash-completion \
mantic ./target > /dev/null || exit 1

# Run the test in 9p forwarded filesystem
echo "Running OS in qemu"
qemu-system-s390x \
-m 8192 \
-smp 4 \
-nodefaults -nographic -no-reboot -no-user-config \
-kernel ./target/boot/vmlinuz \
-initrd ./target/boot/initrd.img \
-append 'root=fsRoot rw rootfstype=9p rootflags=trans=virtio,version=9p2000.L,msize=512000,cache=mmap,posixacl console=ttysclp0 init=/test_init quiet' \
-fsdev local,security_model=passthrough,multidevs=remap,id=fsdev-fsRoot,path=./target \
-device virtio-9p-pci,id=fsRoot,fsdev=fsdev-fsRoot,mount_tag=fsRoot \
-device virtio-serial-ccw -device sclpconsole,chardev=console \
-chardev stdio,id=console,signal=off


---Debugger---
A debugger is not configured

Userspace rpm: qemu-(current).deb

Userspace tool common name: qemu

Userspace tool obtained from project website: na

The userspace tool has the following bit modes: both

*Additional Instructions for d.herrendoerfer@de.ibm.com:
-Attach ltrace and strace of userspace application.

** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New


** Tags: architecture-s39064 bugnameltc-206380 severity-critical targetmilestone-inin---
--
[UBUNTU 22.04] OS guest boot issues on 9p filesystem
https://bugs.launchpad.net/bugs/2065579
You received this bug notification because you are subscribed to linux in Ubuntu.

[Bug 2065514] Re: WARNING: CPU: 5 PID: 485 at drivers/gpu/drm/i915/display/intel_bios.c:2655 print_ddi_port+0x3cc/0x460 [i915]

[ 7.153977] ------------[ cut here ]------------
[ 7.153979] i915 0000:00:02.0: Port A asks to use VBT vswing/preemph tables
[ 7.153996] WARNING: CPU: 5 PID: 485 at drivers/gpu/drm/i915/display/intel_bios.c:2655 print_ddi_port+0x3cc/0x460 [i915]
[ 7.154253] Modules linked in: snd_intel_sdw_acpi snd_hda_codec snd_hda_core i915(+) mac80211 snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event libarc4 irqbypass crct10dif_pclmul snd_rawmidi polyval_clmulni uvcvideo polyval_generic ghash_clmulni_intel sha256_ssse3 videobuf2_vmalloc sha1_ssse3 snd_seq uvc aesni_intel videobuf2_memops btusb videobuf2_v4l2 processor_thermal_device_pci drm_buddy crypto_simd btrtl snd_seq_device ttm processor_thermal_device iwlwifi cmdlinepart cryptd processor_thermal_wt_hint btintel snd_timer videodev mei_hdcp mei_pxp drm_display_helper spi_nor processor_thermal_rfim btbcm rtsx_usb_ms btmtk rapl processor_thermal_rapl intel_rapl_msr mtd mei_me cec intel_rapl_common memstick bluetooth videobuf2_common i2c_i801 snd intel_cstate cfg80211 wmi_bmof mc mei rc_core i2c_smbus spi_intel_pci processor_thermal_wt_req ecdh_generic processor_thermal_power_floor spi_intel soundcore i2c_algo_bit ecc processor_thermal_mbox igen6_edac int3403_thermal int340x_thermal_zone intel_pmc_core intel_vsec
[ 7.154340] pmt_telemetry int3400_thermal acpi_pad acpi_thermal_rel pmt_class acpi_tad joydev input_leds serio_raw mac_hid msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 rtsx_usb_sdmmc usbhid rtsx_usb hid_multitouch hid_generic nvme ucsi_acpi typec_ucsi crc32_pclmul intel_lpss_pci nvme_core intel_lpss xhci_pci nvme_auth idma64 i2c_hid_acpi typec xhci_pci_renesas i2c_hid hid video wmi pinctrl_tigerlake
[ 7.154387] CPU: 5 PID: 485 Comm: (udev-worker) Tainted: G U 6.8.0-31-generic #31-Ubuntu
[ 7.154392] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 750XED/NP750XED-KC2IN, BIOS P14CFG.040.231120.HQ 11/20/2023
[ 7.154395] RIP: 0010:print_ddi_port+0x3cc/0x460 [i915]
[ 7.154817] Code: fc ff ff 49 8b 7e 08 48 8b 5f 50 48 85 db 74 21 e8 b9 d0 5a ee 44 89 f9 48 89 da 48 c7 c7 18 aa 6c c1 48 89 c6 e8 94 40 b2 ed <0f> 0b e9 94 fe ff ff 48 8b 1f eb da 8b 7d c4 4c 89 55 d0 31 f6 45
[ 7.154822] RSP: 0018:ffffa365460577b8 EFLAGS: 00010246
[ 7.154828] RAX: 0000000000000000 RBX: ffff96f5c257b3b0 RCX: 0000000000000000
[ 7.154831] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 7.154834] RBP: ffffa36546057808 R08: 0000000000000000 R09: 0000000000000000
[ 7.154836] R10: 0000000000000000 R11: 0000000000000000 R12: ffff96f5c3cc8000
[ 7.154839] R13: 0000000000000001 R14: ffff96f5c3cc8000 R15: 0000000000000041
[ 7.154842] FS: 00007b3dc621e8c0(0000) GS:ffff96f960280000(0000) knlGS:0000000000000000
[ 7.154846] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 7.154850] CR2: 0000761ecdfda6c0 CR3: 0000000114dba000 CR4: 0000000000f50ef0
[ 7.154853] PKRU: 55555554
[ 7.154855] Call Trace:
[ 7.154858] <TASK>
[ 7.154862] ? show_regs+0x6d/0x80
[ 7.154870] ? __warn+0x89/0x160
[ 7.154878] ? print_ddi_port+0x3cc/0x460 [i915]
[ 7.155273] ? report_bug+0x17e/0x1b0
[ 7.155280] ? handle_bug+0x51/0xa0
[ 7.155284] ? exc_invalid_op+0x18/0x80
[ 7.155288] ? asm_exc_invalid_op+0x1b/0x20
[ 7.155294] ? print_ddi_port+0x3cc/0x460 [i915]
[ 7.155687] ? print_ddi_port+0x3cc/0x460 [i915]
[ 7.156076] parse_ddi_ports+0x18f/0x230 [i915]
[ 7.156468] intel_bios_init+0x26b/0x380 [i915]
[ 7.156849] intel_display_driver_probe_noirq+0x3b/0x240 [i915]
[ 7.157183] i915_driver_probe+0x2fc/0x5f0 [i915]
[ 7.157344] ? drm_privacy_screen_get+0x16d/0x190
[ 7.157348] ? acpi_dev_found+0x64/0x80
[ 7.157353] i915_pci_probe+0xd0/0x170 [i915]
[ 7.157516] local_pci_probe+0x44/0xb0
[ 7.157521] pci_call_probe+0x55/0x1a0
[ 7.157523] pci_device_probe+0x84/0x120
[ 7.157526] really_probe+0x1c4/0x410
[ 7.157529] __driver_probe_device+0x8c/0x180
[ 7.157532] driver_probe_device+0x24/0xd0
[ 7.157534] __driver_attach+0x10b/0x210
[ 7.157536] ? __pfx___driver_attach+0x10/0x10
[ 7.157539] bus_for_each_dev+0x8a/0xf0
[ 7.157542] driver_attach+0x1e/0x30
[ 7.157544] bus_add_driver+0x156/0x260
[ 7.157546] driver_register+0x5e/0x130
[ 7.157549] __pci_register_driver+0x5e/0x70
[ 7.157552] i915_pci_register_driver+0x23/0x30 [i915]
[ 7.157710] i915_init+0x34/0x120 [i915]
[ 7.157866] ? __pfx_i915_init+0x10/0x10 [i915]
[ 7.158017] do_one_initcall+0x5b/0x340
[ 7.158022] do_init_module+0xc0/0x2c0
[ 7.158026] load_module+0xba1/0xcf0
[ 7.158029] init_module_from_file+0x96/0x100
[ 7.158031] ? init_module_from_file+0x96/0x100
[ 7.158033] idempotent_init_module+0x11c/0x2b0
[ 7.158036] __x64_sys_finit_module+0x64/0xd0
[ 7.158038] x64_sys_call+0x1d6e/0x25c0
[ 7.158040] do_syscall_64+0x7f/0x180
[ 7.158043] ? do_syscall_64+0x8c/0x180
[ 7.158045] ? do_syscall_64+0x8c/0x180
[ 7.158047] ? irqentry_exit+0x43/0x50
[ 7.158051] entry_SYSCALL_64_after_hwframe+0x73/0x7b
[ 7.158055] RIP: 0033:0x7b3dc612725d
[ 7.158070] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 8b bb 0d 00 f7 d8 64 89 01 48
[ 7.158072] RSP: 002b:00007ffc2454f0e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[ 7.158075] RAX: ffffffffffffffda RBX: 00005fa2b4a2ec20 RCX: 00007b3dc612725d
[ 7.158076] RDX: 0000000000000004 RSI: 00005fa2b4a30cd0 RDI: 0000000000000033
[ 7.158078] RBP: 00007ffc2454f1a0 R08: 0000000000000040 R09: 00007ffc2454f130
[ 7.158079] R10: 00007b3dc6203b20 R11: 0000000000000246 R12: 00005fa2b4a30cd0
[ 7.158080] R13: 0000000000020000 R14: 00005fa2b4a07610 R15: 00005fa2b4a2eed0
[ 7.158082] </TASK>
[ 7.158083] ---[ end trace 0000000000000000 ]---

** Summary changed:

- i don't know what type of bugs these are
+ WARNING: CPU: 5 PID: 485 at drivers/gpu/drm/i915/display/intel_bios.c:2655 print_ddi_port+0x3cc/0x460 [i915]

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

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2065514

Title:
WARNING: CPU: 5 PID: 485 at
drivers/gpu/drm/i915/display/intel_bios.c:2655
print_ddi_port+0x3cc/0x460 [i915]

Status in linux package in Ubuntu:
Triaged

Bug description:
but what i can is my ubuntu is not working properly on samsumg galaxy
book2

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-31-generic 6.8.0-31.31
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: mohammad-ummer 1911 F.... pipewire
/dev/snd/controlC0: mohammad-ummer 1911 F.... pipewire
mohammad-ummer 1915 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun May 12 11:13:47 2024
InstallationDate: Installed on 2024-05-12 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 750XED
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=4019ea6f-a9c2-4c11-a0be-4f2dcb802b76 ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.8.0-31-generic N/A
linux-backports-modules-6.8.0-31-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2023
dmi.bios.release: 5.25
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P14CFG.040.231120.HQ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP750XED-KC2IN
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SAMSUNG_SW_REVISION_12345+0.0.0000
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP14CFG.040.231120.HQ:bd11/20/2023:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn750XED:pvrP14CFG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP750XED-KC2IN:rvrSAMSUNG_SW_REVISION_12345+0.0.0000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-ADLP-PCFG:
dmi.product.family: Galaxy Book2
dmi.product.name: 750XED
dmi.product.sku: SCAI-A5A5-A5A5-ADLP-PCFG
dmi.product.version: P14CFG
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

[Bug 2065456] Re: segfault when importing *.tif as book cover

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

** No longer affects: linux (Ubuntu)

** Also affects: calibre (Ubuntu Oracular)
Importance: Undecided
Status: New

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2065456

Title:
segfault when importing *.tif as book cover

Status in calibre package in Ubuntu:
New
Status in calibre source package in Oracular:
New

Bug description:
Calibre 7.10:

Traceback (most recent call last):
File "calibre/gui2/ui.py", line 147, in __init__
File "calibre/gui2/ui.py", line 165, in init_iaction
File "calibre/customize/__init__.py", line 659, in load_actual_plugin
File "importlib/__init__.py", line 126, in import_module
File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
File "<frozen importlib._bootstrap>", line 1147, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
File "calibre/customize/zipplugin.py", line 205, in exec_module
File "calibre_plugins.similar_stories.action", line 12, in <module>
from PyQt4.Qt import QMenu, QToolButton, QApplication, Qt, QMessageBox, QUrl
ModuleNotFoundError: No module named 'PyQt4'
qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
Segmentation fault

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

[Bug 2056800] Re: Bluetooth adapter not working ATS2851

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

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

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2056800

Title:
Bluetooth adapter not working ATS2851

Status in linux package in Ubuntu:
Expired
Status in linux-firmware package in Ubuntu:
Won't Fix

Bug description:
Hi, I purchased this adapter: https://www.amazon.co.uk/Maxuni-
Bluetooth-Computer-Receiver-Keyboard/dp/B0BQ3964FP

It doesn't currently work on Linux due to a firmware bug.

The fixes are documented on the web:

https://www.linuxcompatible.org/story/xanmod-linux-kernel-618-released/
"Bluetooth: Fix issue with Actions Semi ATS2851 based devices"

https://github.com/xanmod/linux/commit/00f4b7c036814009e54ae2841c188fe064717ddf


This is what it shows up as:
Bus 001 Device 012: ID 10d7:b012 Actions general adapter

My kernel version is 6.5.0-25-generic

Anyone know how this is fixed? Im running Ubuntu 23.10

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

[Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

with ubuntu 24.04 and kernel 6.8 sound on cs35l41 fixed on um3402 AMD
Ryzen

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1981433

Title:
[Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in Linux Firmware:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed

Bug description:
Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
similar models with Realtek ALC294.

No solution works. Audio is not muted, tried adding snd-hda arguments
- no dice.

This has been reported numerous times, when will a fix finally be
rolled out?!

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-41-generic 5.15.0-41.44
ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: martin 1730 F.... pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 12 13:57:05 2022
InstallationDate: Installed on 2022-07-12 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-41-generic N/A
linux-backports-modules-5.15.0-41-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/15/2022
dmi.bios.release: 5.25
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UX3402ZA.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX3402ZA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.5
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
dmi.product.family: Zenbook
dmi.product.name: Zenbook UX3402ZA_UX3402ZA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/1981433/+subscriptions

[Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

** Tags added: kern-10892

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1981433

Title:
[Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in Linux Firmware:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed

Bug description:
Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
similar models with Realtek ALC294.

No solution works. Audio is not muted, tried adding snd-hda arguments
- no dice.

This has been reported numerous times, when will a fix finally be
rolled out?!

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-41-generic 5.15.0-41.44
ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: martin 1730 F.... pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 12 13:57:05 2022
InstallationDate: Installed on 2022-07-12 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-41-generic N/A
linux-backports-modules-5.15.0-41-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/15/2022
dmi.bios.release: 5.25
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UX3402ZA.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX3402ZA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.5
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
dmi.product.family: Zenbook
dmi.product.name: Zenbook UX3402ZA_UX3402ZA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/1981433/+subscriptions

Re: [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

Thanks a lot! It will be great if you could explain what to do with this
information, as I am not expert enough to understand it by itself. I did
try to understand using web search, but not sure about it at all, so
thanks again.

On 08/05/24 16:08, Charles Keepax wrote:
> Support should be added to the kernel as of:
>
> b257187bcff4 ("ALSA: hda: cs35l41: Support additional ASUS Zenbook 2022
> Models")
>
> And firmware as of:
>
> 771968c68191 ("linux-firmware: Add firmware for Cirrus CS35L41 on ASUS
> Laptops")
>

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1981433

Title:
[Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in Linux Firmware:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed

Bug description:
Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
similar models with Realtek ALC294.

No solution works. Audio is not muted, tried adding snd-hda arguments
- no dice.

This has been reported numerous times, when will a fix finally be
rolled out?!

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-41-generic 5.15.0-41.44
ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: martin 1730 F.... pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 12 13:57:05 2022
InstallationDate: Installed on 2022-07-12 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-41-generic N/A
linux-backports-modules-5.15.0-41-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/15/2022
dmi.bios.release: 5.25
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UX3402ZA.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX3402ZA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.5
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
dmi.product.family: Zenbook
dmi.product.name: Zenbook UX3402ZA_UX3402ZA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/1981433/+subscriptions

[Bug 2038288] Re: Failed to start thermald.service

dptfxtract works for me.

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2038288

Title:
Failed to start thermald.service

Status in linux package in Ubuntu:
Confirmed
Status in thermald package in Ubuntu:
Triaged

Bug description:
Get lot of thermald errors logged with that Mate session on Mantic

dbus-broker-launch[775]: Invalid group-name in /usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
systemd[1]: Starting thermald.service - Thermal Daemon Service...
thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
thermald[892]: *** stack smashing detected ***: terminated
systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
systemd[1]: thermald.service: Failed with result 'signal'.
systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
systemd[1]: Stopped thermald.service - Thermal Daemon Service.
systemd[1]: Starting thermald.service - Thermal Daemon Service...
thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
thermald[982]: *** stack smashing detected ***: terminated
systemd[1]: Started thermald.service - Thermal Daemon Service.
thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
systemd[1]: thermald.service: Failed with result 'signal'.
systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
systemd[1]: Stopped thermald.service - Thermal Daemon Service.
systemd[1]: Starting thermald.service - Thermal Daemon Service...
thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
thermald[1049]: *** stack smashing detected ***: terminated
systemd[1]: Started thermald.service - Thermal Daemon Service.
systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
systemd[1]: thermald.service: Failed with result 'core-dump'.
systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
systemd[1]: Stopped thermald.service - Thermal Daemon Service.
systemd[1]: Starting thermald.service - Thermal Daemon Service...
systemd[1]: Started thermald.service - Thermal Daemon Service.
thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
thermald[1117]: *** stack smashing detected ***: terminated
systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
systemd[1]: thermald.service: Failed with result 'core-dump'.
systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
systemd[1]: Stopped thermald.service - Thermal Daemon Service.
systemd[1]: Starting thermald.service - Thermal Daemon Service...
systemd[1]: Started thermald.service - Thermal Daemon Service.
thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
thermald[1180]: *** stack smashing detected ***: terminated
systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
systemd[1]: thermald.service: Failed with result 'core-dump'.
systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
systemd[1]: Stopped thermald.service - Thermal Daemon Service.
systemd[1]: thermald.service: Start request repeated too quickly.
systemd[1]: thermald.service: Failed with result 'core-dump'.
systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
DistroRelease: Ubuntu 23.10
Package: thermald 2.5.4-2
PackageArchitecture: amd64
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Tags: mantic
Uname: Linux 6.5.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
modified.conffile..etc.init.thermald.conf: [deleted]

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

[Bug 2064873] Re: crash when trying an AppImage

Yes, it seems to be an AppArmor issue - modifying the kernel options
(/proc/cmdline => BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic
root=UUID=... ro resume=UUID=... log_buf_len=2M apparmor=0) the
applications start normally.

Ho could this be done to *all* AppImage applications?

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2064873

Title:
crash when trying an AppImage

Status in linux package in Ubuntu:
Incomplete

Bug description:
Trying to run an AppImage (such as ungoogled-
chromium_124.0.6367.91-1.AppImage from https://ungoogled-
software.github.io/ungoogled-chromium-binaries/) will crash, with the
following error message:

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[16771:16771:0505/192239.800083:FATAL:zygote_host_impl_linux.cc(126)] No usable sandbox! Update your kernel or see https://chromium.9oo91esource.qjz9zk/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
Trace/breakpoint trap (core dumped)
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Some searches on Internet
(https://stackoverflow.com/questions/67138645/error-the-suid-sandbox-
helper-binary-was-found-but-is-not-configured-correctly) tell that one
should use kernel.unprivileged_userns_clone=1 however on kernel
6.8.0-31-generic there is no such parameter.

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

[Bug 2056461] Re: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown

** Description changed:

+ [Impact]
+
+ It seems that kernel 6.8 introduced a regression in the 9pfs related to
+ caching and netfslib, that can cause some user-space apps to read
+ content from files that is not up-to-date (when they are used in a
+ producer/consumer fashion).
+
+ It seems that the offending commit is this one:
+
+ 80105ed2fd27 ("9p: Use netfslib read/write_iter")
+
+ Reverting the commit seems to fix the problem. However the actual bug
+ might be in netfslib or how netfslib is used in the 9p context.
+
+ The regression has been reported upstream and we are still investigating
+ (https://lore.kernel.org/lkml/Zj0ErxVBE3DYT2Ea@gpd/).
+
+ In the meantime it probably makes sense to temporarily revert the commit
+ as a SAUCE patch. Then we will drop the SAUCE patch once we'll have a
+ proper fix upstream.
+
+ [Test case]
+
+ The following test should complete correctly without any timeout:
+
+   pull-lp-source -d hello
+   autopkgtest-buildvm-ubuntu-cloud -r noble
+   autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img
+
+
+ [Fix]
+
+ Revert the following commit (until we have a proper fix upstream):
+
+ 80105ed2fd27 ("9p: Use netfslib read/write_iter")
+
+ [Regression potential]
+
+ We may experience other regressions related to 9pfs with this change,
+ however it's quite unlikely to happen since we are reverting a commit,
+ restoring the previous behavior.
+
+ [Original bug report]
+
autopkgtest-virt-qemu sometimes hangs when running tests on noble
images. Originally reported by schopin, who also provided a reproducer:

- pull-lp-source -d hello
- autopkgtest-buildvm-ubuntu-cloud -r noble
- autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img
+   pull-lp-source -d hello
+   autopkgtest-buildvm-ubuntu-cloud -r noble
+   autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img

I've been able to reproduce it with debugging enabled:

- autopkgtest -ddd -U hello_2.10-3.dsc -- qemu --debug --show-boot
+   autopkgtest -ddd -U hello_2.10-3.dsc -- qemu --debug --show-boot
/path/to/image

It can get stuck during different stages, but AFAICT always during
"copydown" operations, log excerpts follow. It may be a coincidence, but
this started happening around the time linux-image-6.8.0-11-generic
(6.8.0-11.11) migrated to noble. The testbeds I used booted 6.6 but then
rebooted into that 6.8 kernel after being upgraded by autopkgtest.

-- logs --

Removing autopkgtest-satdep (0) ...
[...]
autopkgtest-virt-qemu: DBG: executing copydown /tmp/autopkgtest.output.g8v75e8g/tests-tree/ /t/
autopkgtest-virt-qemu: DBG: ['cmdls', "(['tar', '--directory', '/tmp/autopkgtest.output.g8v75e]
autopkgtest-virt-qemu: DBG: ['srcstdin', "<_io.BufferedReader name='/dev/null'>", 'deststdout']
autopkgtest-virt-qemu: DBG: +< tar --directory /tmp/autopkgtest.output.g8v75e8g/tests-tree/ --
autopkgtest-virt-qemu: DBG: +> /tmp/autopkgtest-qemu.ztmr6f5k/runcmd sh -ec if ! test -d /tmp-
autopkgtest-virt-qemu: DBG: +>?

-- or --

autopkgtest: DBG: sending command to testbed: copydown /tmp/autopkgtest.output.c9utq3bx/tests-tree/ /tmp/autopkgtest.H8NDfW/build.DLR/src/
autopkgtest-virt-qemu: DBG: executing copydown /tmp/autopkgtest.output.c9utq3bx/tests-tree/ /tmp/autopkgtest.H8NDfW/build.DLR/src/
autopkgtest-virt-qemu: DBG: ['cmdls', "(['tar', '--directory', '/tmp/autopkgtest.output.c9utq3bx/tests-tree/', '--warning=none', '-c', '.', '-f', '-'], ['/tmp/autopkgtest-qemu.qtkcgg5l/runcm]
autopkgtest-virt-qemu: DBG: ['srcstdin', "<_io.BufferedReader name='/dev/null'>", 'deststdout', "<_io.BufferedReader name='/dev/null'>", 'devnull_read', <_io.BufferedReader name='/dev/null'>]
autopkgtest-virt-qemu: DBG: +< tar --directory /tmp/autopkgtest.output.c9utq3bx/tests-tree/ --warning=none -c . -f -
autopkgtest-virt-qemu: DBG: +> /tmp/autopkgtest-qemu.qtkcgg5l/runcmd sh -ec if ! test -d /tmp/autopkgtest.H8NDfW/build.DLR/src/; then mkdir -- /tmp/autopkgtest.H8NDfW/build.DLR/src/; fi; cd-
autopkgtest-virt-qemu: DBG: +>?

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2056461

Title:
autopkgtest-virt-qemu on noble images sometimes hangs doing copydown

Status in autopkgtest package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
In Progress

Bug description:
[Impact]

It seems that kernel 6.8 introduced a regression in the 9pfs related
to caching and netfslib, that can cause some user-space apps to read
content from files that is not up-to-date (when they are used in a
producer/consumer fashion).

It seems that the offending commit is this one:

80105ed2fd27 ("9p: Use netfslib read/write_iter")

Reverting the commit seems to fix the problem. However the actual bug
might be in netfslib or how netfslib is used in the 9p context.

The regression has been reported upstream and we are still
investigating (https://lore.kernel.org/lkml/Zj0ErxVBE3DYT2Ea@gpd/).

In the meantime it probably makes sense to temporarily revert the
commit as a SAUCE patch. Then we will drop the SAUCE patch once we'll
have a proper fix upstream.

[Test case]

The following test should complete correctly without any timeout:

  pull-lp-source -d hello
  autopkgtest-buildvm-ubuntu-cloud -r noble
  autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img


[Fix]

Revert the following commit (until we have a proper fix upstream):

80105ed2fd27 ("9p: Use netfslib read/write_iter")

[Regression potential]

We may experience other regressions related to 9pfs with this change,
however it's quite unlikely to happen since we are reverting a commit,
restoring the previous behavior.

[Original bug report]

autopkgtest-virt-qemu sometimes hangs when running tests on noble
images. Originally reported by schopin, who also provided a
reproducer:

  pull-lp-source -d hello
  autopkgtest-buildvm-ubuntu-cloud -r noble
  autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img

I've been able to reproduce it with debugging enabled:

  autopkgtest -ddd -U hello_2.10-3.dsc -- qemu --debug --show-boot
/path/to/image

It can get stuck during different stages, but AFAICT always during
"copydown" operations, log excerpts follow. It may be a coincidence,
but this started happening around the time linux-
image-6.8.0-11-generic (6.8.0-11.11) migrated to noble. The testbeds I
used booted 6.6 but then rebooted into that 6.8 kernel after being
upgraded by autopkgtest.

-- logs --

Removing autopkgtest-satdep (0) ...
[...]
autopkgtest-virt-qemu: DBG: executing copydown /tmp/autopkgtest.output.g8v75e8g/tests-tree/ /t/
autopkgtest-virt-qemu: DBG: ['cmdls', "(['tar', '--directory', '/tmp/autopkgtest.output.g8v75e]
autopkgtest-virt-qemu: DBG: ['srcstdin', "<_io.BufferedReader name='/dev/null'>", 'deststdout']
autopkgtest-virt-qemu: DBG: +< tar --directory /tmp/autopkgtest.output.g8v75e8g/tests-tree/ --
autopkgtest-virt-qemu: DBG: +> /tmp/autopkgtest-qemu.ztmr6f5k/runcmd sh -ec if ! test -d /tmp-
autopkgtest-virt-qemu: DBG: +>?

-- or --

autopkgtest: DBG: sending command to testbed: copydown /tmp/autopkgtest.output.c9utq3bx/tests-tree/ /tmp/autopkgtest.H8NDfW/build.DLR/src/
autopkgtest-virt-qemu: DBG: executing copydown /tmp/autopkgtest.output.c9utq3bx/tests-tree/ /tmp/autopkgtest.H8NDfW/build.DLR/src/
autopkgtest-virt-qemu: DBG: ['cmdls', "(['tar', '--directory', '/tmp/autopkgtest.output.c9utq3bx/tests-tree/', '--warning=none', '-c', '.', '-f', '-'], ['/tmp/autopkgtest-qemu.qtkcgg5l/runcm]
autopkgtest-virt-qemu: DBG: ['srcstdin', "<_io.BufferedReader name='/dev/null'>", 'deststdout', "<_io.BufferedReader name='/dev/null'>", 'devnull_read', <_io.BufferedReader name='/dev/null'>]
autopkgtest-virt-qemu: DBG: +< tar --directory /tmp/autopkgtest.output.c9utq3bx/tests-tree/ --warning=none -c . -f -
autopkgtest-virt-qemu: DBG: +> /tmp/autopkgtest-qemu.qtkcgg5l/runcmd sh -ec if ! test -d /tmp/autopkgtest.H8NDfW/build.DLR/src/; then mkdir -- /tmp/autopkgtest.H8NDfW/build.DLR/src/; fi; cd-
autopkgtest-virt-qemu: DBG: +>?

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

[Bug 2065514] [NEW] i don't know what type of bugs these are

Public bug reported:

but what i can is my ubuntu is not working properly on samsumg galaxy
book2

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-31-generic 6.8.0-31.31
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: mohammad-ummer 1911 F.... pipewire
/dev/snd/controlC0: mohammad-ummer 1911 F.... pipewire
mohammad-ummer 1915 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun May 12 11:13:47 2024
InstallationDate: Installed on 2024-05-12 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 750XED
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=4019ea6f-a9c2-4c11-a0be-4f2dcb802b76 ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.8.0-31-generic N/A
linux-backports-modules-6.8.0-31-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2023
dmi.bios.release: 5.25
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P14CFG.040.231120.HQ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP750XED-KC2IN
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SAMSUNG_SW_REVISION_12345+0.0.0000
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP14CFG.040.231120.HQ:bd11/20/2023:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn750XED:pvrP14CFG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP750XED-KC2IN:rvrSAMSUNG_SW_REVISION_12345+0.0.0000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-ADLP-PCFG:
dmi.product.family: Galaxy Book2
dmi.product.name: 750XED
dmi.product.sku: SCAI-A5A5-A5A5-ADLP-PCFG
dmi.product.version: P14CFG
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug noble wayland-session

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2065514

Title:
i don't know what type of bugs these are

Status in linux package in Ubuntu:
New

Bug description:
but what i can is my ubuntu is not working properly on samsumg galaxy
book2

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-31-generic 6.8.0-31.31
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: mohammad-ummer 1911 F.... pipewire
/dev/snd/controlC0: mohammad-ummer 1911 F.... pipewire
mohammad-ummer 1915 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun May 12 11:13:47 2024
InstallationDate: Installed on 2024-05-12 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 750XED
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=4019ea6f-a9c2-4c11-a0be-4f2dcb802b76 ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.8.0-31-generic N/A
linux-backports-modules-6.8.0-31-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2023
dmi.bios.release: 5.25
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P14CFG.040.231120.HQ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP750XED-KC2IN
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SAMSUNG_SW_REVISION_12345+0.0.0000
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP14CFG.040.231120.HQ:bd11/20/2023:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn750XED:pvrP14CFG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP750XED-KC2IN:rvrSAMSUNG_SW_REVISION_12345+0.0.0000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-ADLP-PCFG:
dmi.product.family: Galaxy Book2
dmi.product.name: 750XED
dmi.product.sku: SCAI-A5A5-A5A5-ADLP-PCFG
dmi.product.version: P14CFG
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

[Bug 2057467] Re: my external monitor screen keeps going blank intermittently

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

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

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2057467

Title:
my external monitor screen keeps going blank intermittently

Status in linux package in Ubuntu:
Expired

Bug description:
I have connected a samsung exnternal monitor to my laptop via VGA cable.
But the screen frequently goes blank, I have tried updating the graphics drivers but of no use. Please help.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
Uname: Linux 6.5.0-25-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: Tue Mar 12 13:10:05 2024
DistUpgraded: 2024-02-05 14:12:41,366 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: nvidia/470.239.06, 6.5.0-25-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller])
Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c]
InstallationDate: Installed on 2022-11-10 (488 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
MonitorsUser.xml: <rate>59.96</rate>
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-25-generic root=UUID=d786cdef-a41c-4f13-8357-af62bee963a6 ro i915.enable_dc=0 intel_idle.max_cstate=2
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2024-02-05 (36 days ago)
dmi.bios.date: 10/20/2014
dmi.bios.release: 0.29
dmi.bios.vendor: LENOVO
dmi.bios.version: 9ACN29WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lancer 5A2
dmi.board.vendor: LENOVO
dmi.board.version: NANANANANO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G50-70
dmi.ec.firmware.release: 0.29
dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:br0.29:efr0.29:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:skuLENOVO_MT_20351_BU_idea_FM_LenovoG50-70:
dmi.product.family: IDEAPAD
dmi.product.name: 20351
dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70
dmi.product.version: Lenovo G50-70
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.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
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/linux/+bug/2057467/+subscriptions

[Bug 2064873] Re: crash when trying an AppImage

Yes, unprivileged_userns_clone exists:

# cat /proc/sys/kernel/unprivileged_userns_clone
1

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2064873

Title:
crash when trying an AppImage

Status in linux package in Ubuntu:
Incomplete

Bug description:
Trying to run an AppImage (such as ungoogled-
chromium_124.0.6367.91-1.AppImage from https://ungoogled-
software.github.io/ungoogled-chromium-binaries/) will crash, with the
following error message:

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[16771:16771:0505/192239.800083:FATAL:zygote_host_impl_linux.cc(126)] No usable sandbox! Update your kernel or see https://chromium.9oo91esource.qjz9zk/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
Trace/breakpoint trap (core dumped)
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Some searches on Internet
(https://stackoverflow.com/questions/67138645/error-the-suid-sandbox-
helper-binary-was-found-but-is-not-configured-correctly) tell that one
should use kernel.unprivileged_userns_clone=1 however on kernel
6.8.0-31-generic there is no such parameter.

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