[Touch-packages] [Bug 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect
Just want to update this bug - I have not found a fix for this. Instead
I've been relying on the Logitech universal receiver which is working
great in my experience.
--
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/2040657
Title:
bluez does not detect Logitech Pebble M350, no option to connect
Status in bluez package in Ubuntu:
New
Bug description:
I lost the proprietary USB dongle and decided I wanted to try
bluetooth with this particular mouse. I am able to connect with
bluetooth on Windows 11, but the device doesn't even show up in
`bluetoothctl scan on`.
This is seen on Jammy with bluez 5.64-0ubuntu1
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-03-06 (242 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: zfs
Package: bluez 5.68-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Tags: mantic wayland-session
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild
sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.58
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET75W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDUS
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: D0:AB:D5:BB:40:FD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2059049] [NEW] adduser allows no password when PAM's pwquality is restrictively set
Public bug reported: If pam_pwqaulity is restrictively set a user can still be created by adduser without a password. e.g., ``` eslerm@mino:~$ cat /etc/pam.d/common-password |grep pwquality password requisite pam_pwquality.so retry=3 minlen=8 maxrepeat=3 ucredit=-1 lcredit=-1 dcredit=-1 ocredit=-1 difok=3 gecoscheck=1 reject_username enforce_for_root eslerm@mino:~$ sudo adduser bar info: Adding user `bar' ... info: Selecting UID/GID from range 1000 to 5 ... info: Adding new group `bar' (1002) ... info: Adding new user `bar' (1002) with group `bar (1002)' ... info: Creating home directory `/home/bar' ... info: Copying files from `/etc/skel' ... New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits passwd: Have exhausted maximum number of retries for service passwd: password unchanged Try again? [y/N] N Changing the user information for bar Enter the new value, or press ENTER for the default Full Name []: Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] info: Adding new user `bar' to supplemental / extra groups `users' ... info: Adding user `bar' to group `users' ... eslerm@mino:~$ sudo cat /etc/shadow|grep bar bar:!:19802:0:9:7::: ``` This was raised as an issue to the Security team. Foundations suggested to file a bug. This is possibly only a feature request. If this behavior is unexpected by the maintainers, it is likely a security issue. I am leaning towards this being a feature request and not marking the bug for Public/Private Security. ** Affects: adduser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2059049 Title: adduser allows no password when PAM's pwquality is restrictively set Status in adduser package in Ubuntu: New Bug description: If pam_pwqaulity is restrictively set a user can still be created by adduser without a password. e.g., ``` eslerm@mino:~$ cat /etc/pam.d/common-password |grep pwquality password requisite pam_pwquality.so retry=3 minlen=8 maxrepeat=3 ucredit=-1 lcredit=-1 dcredit=-1 ocredit=-1 difok=3 gecoscheck=1 reject_username enforce_for_root eslerm@mino:~$ sudo adduser bar info: Adding user `bar' ... info: Selecting UID/GID from range 1000 to 5 ... info: Adding new group `bar' (1002) ... info: Adding new user `bar' (1002) with group `bar (1002)' ... info: Creating home directory `/home/bar' ... info: Copying files from `/etc/skel' ... New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits passwd: Have exhausted maximum number of retries for service passwd: password unchanged Try again? [y/N] N Changing the user information for bar Enter the new value, or press ENTER for the default Full Name []: Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] info: Adding new user `bar' to supplemental / extra groups `users' ... info: Adding user `bar' to group `users' ... eslerm@mino:~$ sudo cat /etc/shadow|grep bar bar:!:19802:0:9:7::: ``` This was raised as an issue to the Security team. Foundations suggested to file a bug. This is possibly only a feature request. If this behavior is unexpected by the maintainers, it is likely a security issue. I am leaning towards this being a feature request and not marking the bug for Public/Private Security. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2059049/+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 2059048] [NEW] adduser allows no password when PAM's pwquality is restrictively set
Public bug reported: If pam_pwqaulity is restrictively set a user can still be created by adduser without a password. e.g., ``` eslerm@mino:~$ cat /etc/pam.d/common-password |grep pwquality password requisite pam_pwquality.so retry=3 minlen=8 maxrepeat=3 ucredit=-1 lcredit=-1 dcredit=-1 ocredit=-1 difok=3 gecoscheck=1 reject_username enforce_for_root eslerm@mino:~$ sudo adduser bar info: Adding user `bar' ... info: Selecting UID/GID from range 1000 to 5 ... info: Adding new group `bar' (1002) ... info: Adding new user `bar' (1002) with group `bar (1002)' ... info: Creating home directory `/home/bar' ... info: Copying files from `/etc/skel' ... New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits passwd: Have exhausted maximum number of retries for service passwd: password unchanged Try again? [y/N] N Changing the user information for bar Enter the new value, or press ENTER for the default Full Name []: Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] info: Adding new user `bar' to supplemental / extra groups `users' ... info: Adding user `bar' to group `users' ... eslerm@mino:~$ sudo cat /etc/shadow|grep bar bar:!:19802:0:9:7::: ``` This was raised as an issue to the Security team. Foundations suggested to file a bug. This is possibly only a feature request. If this behavior is unexpected by the maintainers, it is likely a security issue. I am leaning towards this being a feature request and not marking the bug for Public/Private Security. ** Affects: adduser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2059048 Title: adduser allows no password when PAM's pwquality is restrictively set Status in adduser package in Ubuntu: New Bug description: If pam_pwqaulity is restrictively set a user can still be created by adduser without a password. e.g., ``` eslerm@mino:~$ cat /etc/pam.d/common-password |grep pwquality password requisite pam_pwquality.so retry=3 minlen=8 maxrepeat=3 ucredit=-1 lcredit=-1 dcredit=-1 ocredit=-1 difok=3 gecoscheck=1 reject_username enforce_for_root eslerm@mino:~$ sudo adduser bar info: Adding user `bar' ... info: Selecting UID/GID from range 1000 to 5 ... info: Adding new group `bar' (1002) ... info: Adding new user `bar' (1002) with group `bar (1002)' ... info: Creating home directory `/home/bar' ... info: Copying files from `/etc/skel' ... New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits New password: BAD PASSWORD: The password contains less than 1 digits passwd: Have exhausted maximum number of retries for service passwd: password unchanged Try again? [y/N] N Changing the user information for bar Enter the new value, or press ENTER for the default Full Name []: Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] info: Adding new user `bar' to supplemental / extra groups `users' ... info: Adding user `bar' to group `users' ... eslerm@mino:~$ sudo cat /etc/shadow|grep bar bar:!:19802:0:9:7::: ``` This was raised as an issue to the Security team. Foundations suggested to file a bug. This is possibly only a feature request. If this behavior is unexpected by the maintainers, it is likely a security issue. I am leaning towards this being a feature request and not marking the bug for Public/Private Security. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2059048/+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 2059033] Re: Xorg crashes with SIGABRT
** Changed in: mesa Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2059033 Title: Xorg crashes with SIGABRT Status in Mesa: New Status in mesa package in Ubuntu: New Bug description: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x560c5cc756a0 in OsAbort () at ../../../../os/utils.c:1352 #6 0x560c5cc7aea9 in AbortServer () at ../../../../os/log.c:879 #7 0x560c5cc7be9a in FatalError (f=f@entry=0x560c5ccadc10 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1017 #8 0x560c5cc72abd in OsSigHandler (unused=, sip=0x713ae7b0, signo=6) at ../../../../os/osinit.c:156 #9 OsSigHandler (signo=6, sip=0x713ae7b0, unused=) at ../../../../os/osinit.c:110 #10 #11 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #12 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #13 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #14 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #15 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #16 0x7f72fc49d86d in _iris_batch_flush (batch=0x560c5e916118, file=, line=) at ../src/gallium/drivers/iris/iris_batch.c:1116 #17 0x7f72fd1da6ff in iris_fence_flush (ctx=0x560c5e915be0, out_fence=0x0, flags=) at ../src/gallium/drivers/iris/iris_fence.c:267 #18 0x7f72fc55f127 in st_flush (flags=0, fence=0x0, st=0x560c5e93bbc0) at ../src/mesa/state_tracker/st_cb_flush.c:60 #19 st_glFlush (ctx=, gallium_flush_flags=0) at ../src/mesa/state_tracker/st_cb_flush.c:94 #20 0x7f72fe56b604 in _glamor_block_handler (screen=0x560c5e8655a0, timeout=0x713af054) at ../../../../glamor/glamor.c:285 #21 0x7f72fe5a6157 in msBlockHandler (pScreen=0x560c5e8655a0, timeout=0x713af054) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:701 #22 0x560c5cb01095 in BlockHandler (pTimeout=pTimeout@entry=0x713af054) at ../../../../dix/dixutils.c:394 #23 0x560c5cc6c0c9 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:201 #24 0x560c5cafc3e7 in Dispatch () at ../../../../dix/dispatch.c:492 #25 0x560c5cb006b4 in dix_main (argc=11, argv=0x713af268, envp=) at ../../../../dix/main.c:272 #26 0x7f72fec29d90 in __libc_start_call_main (main=main@entry=0x560c5cae95d0 , argc=argc@entry=11, argv=argv@entry=0x713af268) at ../sysdeps/nptl/libc_start_call_main.h:58 #27 0x7f72fec29e40 in __libc_start_main_impl (main=0x560c5cae95d0 , argc=11, argv=0x713af268, init=, fini=, rtld_fini=, stack_end=0x713af258) at ../csu/libc-start.c:392 #28 0x560c5cae9605 in _start () This post describes a similar issue: https://gitlab.freedesktop.org/drm/intel/-/issues/4858 I tried using a workaround from the above link, to set GPU to max frequency using command "intel_gpu_frequency -m", this seemed to reduce the rate of occurrence from once per day to once every 3 days, but this is not a permanent solution. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2059033/+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 2057836] Re: gst-python1.0 fails to build: test failures
same test failures with pygobject 3.48.1-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/2057836 Title: gst-python1.0 fails to build: test failures Status in pygobject: New Status in gst-python1.0 package in Ubuntu: Triaged Status in pygobject package in Ubuntu: Triaged Status in gst-python1.0 package in Debian: Confirmed Bug description: gst-python1.0 fails to build because of test failures. https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1 https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1 I have reported the issue to the upstream developers https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353 To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/2057836/+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 2059033] Re: Xorg crashes with SIGABRT
** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #4858 https://gitlab.freedesktop.org/drm/intel/-/issues/4858 ** Also affects: mesa via https://gitlab.freedesktop.org/drm/intel/-/issues/4858 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2059033 Title: Xorg crashes with SIGABRT Status in Mesa: Unknown Status in mesa package in Ubuntu: New Bug description: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x560c5cc756a0 in OsAbort () at ../../../../os/utils.c:1352 #6 0x560c5cc7aea9 in AbortServer () at ../../../../os/log.c:879 #7 0x560c5cc7be9a in FatalError (f=f@entry=0x560c5ccadc10 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1017 #8 0x560c5cc72abd in OsSigHandler (unused=, sip=0x713ae7b0, signo=6) at ../../../../os/osinit.c:156 #9 OsSigHandler (signo=6, sip=0x713ae7b0, unused=) at ../../../../os/osinit.c:110 #10 #11 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #12 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #13 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #14 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #15 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #16 0x7f72fc49d86d in _iris_batch_flush (batch=0x560c5e916118, file=, line=) at ../src/gallium/drivers/iris/iris_batch.c:1116 #17 0x7f72fd1da6ff in iris_fence_flush (ctx=0x560c5e915be0, out_fence=0x0, flags=) at ../src/gallium/drivers/iris/iris_fence.c:267 #18 0x7f72fc55f127 in st_flush (flags=0, fence=0x0, st=0x560c5e93bbc0) at ../src/mesa/state_tracker/st_cb_flush.c:60 #19 st_glFlush (ctx=, gallium_flush_flags=0) at ../src/mesa/state_tracker/st_cb_flush.c:94 #20 0x7f72fe56b604 in _glamor_block_handler (screen=0x560c5e8655a0, timeout=0x713af054) at ../../../../glamor/glamor.c:285 #21 0x7f72fe5a6157 in msBlockHandler (pScreen=0x560c5e8655a0, timeout=0x713af054) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:701 #22 0x560c5cb01095 in BlockHandler (pTimeout=pTimeout@entry=0x713af054) at ../../../../dix/dixutils.c:394 #23 0x560c5cc6c0c9 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:201 #24 0x560c5cafc3e7 in Dispatch () at ../../../../dix/dispatch.c:492 #25 0x560c5cb006b4 in dix_main (argc=11, argv=0x713af268, envp=) at ../../../../dix/main.c:272 #26 0x7f72fec29d90 in __libc_start_call_main (main=main@entry=0x560c5cae95d0 , argc=argc@entry=11, argv=argv@entry=0x713af268) at ../sysdeps/nptl/libc_start_call_main.h:58 #27 0x7f72fec29e40 in __libc_start_main_impl (main=0x560c5cae95d0 , argc=11, argv=0x713af268, init=, fini=, rtld_fini=, stack_end=0x713af258) at ../csu/libc-start.c:392 #28 0x560c5cae9605 in _start () This post describes a similar issue: https://gitlab.freedesktop.org/drm/intel/-/issues/4858 I tried using a workaround from the above link, to set GPU to max frequency using command "intel_gpu_frequency -m", this seemed to reduce the rate of occurrence from once per day to once every 3 days, but this is not a permanent solution. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2059033/+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 2058691] Re: No sound card detected on the Dell xps 16 2024 (9640)
I think sof-mtl-rt711-4ch.tplg and sof-mtl-rt711.tplg aren't the same thing. I'm guessing the former is for devices with four audio channels? I'm on arch with a sof-mtl-rt711-4ch.tplg and another file beginning with "sof-mtl-rt711", but no "sof-mtl-rt711.tplg". Renaming either of them to sof-mtl-rt711 produces the same error. Also, googling "sof-mtl- rt711" reveals an internal Intel document mentioning the existence of this file, so I'd imagine Intel hasn't released the file yet. -- 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/2058691 Title: No sound card detected on the Dell xps 16 2024 (9640) Status in alsa-driver package in Ubuntu: New Bug description: The sound card is not detected on the Dell XPS 16 2024 (9640). A Cirrus Logic CS42L43 card is used which apparently got support in Linux 6.6 https://www.google.com/url?sa=t=web=j=89978449=https://www.phoronix.com/forums/forum/software/general- linux-open-source/1408193-linux-6-6-lands-support-for-the-cirrus- logic-cs42l43-audio-codec=2ahUKEwiukq-ZroaFAxUWhf0HHe- jCngQFnoECA8QAQ=AOvVaw3VW5hROJFzdJPUaIX-3igC https://www.reddit.com/r/DellXPS/comments/1ax1i4t/support_for_xps_16_9640_documentation/ No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 21 23:00:06 2024 InstallationDate: Installed on 2024-03-19 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240319) MachineType: Dell Inc. XPS 16 9640 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2024 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 0YFT36 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd01/15/2024:br1.1:efr1.2:svnDellInc.:pnXPS169640:pvr:rvnDellInc.:rn0YFT36:rvrA00:cvnDellInc.:ct10:cvr:sku0C62: dmi.product.family: XPS dmi.product.name: XPS 16 9640 dmi.product.sku: 0C62 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2058691/+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 2059033] [NEW] Xorg crashes with SIGABRT
Public bug reported: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x560c5cc756a0 in OsAbort () at ../../../../os/utils.c:1352 #6 0x560c5cc7aea9 in AbortServer () at ../../../../os/log.c:879 #7 0x560c5cc7be9a in FatalError (f=f@entry=0x560c5ccadc10 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1017 #8 0x560c5cc72abd in OsSigHandler (unused=, sip=0x713ae7b0, signo=6) at ../../../../os/osinit.c:156 #9 OsSigHandler (signo=6, sip=0x713ae7b0, unused=) at ../../../../os/osinit.c:110 #10 #11 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #12 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #13 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #14 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #15 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #16 0x7f72fc49d86d in _iris_batch_flush (batch=0x560c5e916118, file=, line=) at ../src/gallium/drivers/iris/iris_batch.c:1116 #17 0x7f72fd1da6ff in iris_fence_flush (ctx=0x560c5e915be0, out_fence=0x0, flags=) at ../src/gallium/drivers/iris/iris_fence.c:267 #18 0x7f72fc55f127 in st_flush (flags=0, fence=0x0, st=0x560c5e93bbc0) at ../src/mesa/state_tracker/st_cb_flush.c:60 #19 st_glFlush (ctx=, gallium_flush_flags=0) at ../src/mesa/state_tracker/st_cb_flush.c:94 #20 0x7f72fe56b604 in _glamor_block_handler (screen=0x560c5e8655a0, timeout=0x713af054) at ../../../../glamor/glamor.c:285 #21 0x7f72fe5a6157 in msBlockHandler (pScreen=0x560c5e8655a0, timeout=0x713af054) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:701 #22 0x560c5cb01095 in BlockHandler (pTimeout=pTimeout@entry=0x713af054) at ../../../../dix/dixutils.c:394 #23 0x560c5cc6c0c9 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:201 #24 0x560c5cafc3e7 in Dispatch () at ../../../../dix/dispatch.c:492 #25 0x560c5cb006b4 in dix_main (argc=11, argv=0x713af268, envp=) at ../../../../dix/main.c:272 #26 0x7f72fec29d90 in __libc_start_call_main (main=main@entry=0x560c5cae95d0 , argc=argc@entry=11, argv=argv@entry=0x713af268) at ../sysdeps/nptl/libc_start_call_main.h:58 #27 0x7f72fec29e40 in __libc_start_main_impl (main=0x560c5cae95d0 , argc=11, argv=0x713af268, init=, fini=, rtld_fini=, stack_end=0x713af258) at ../csu/libc-start.c:392 #28 0x560c5cae9605 in _start () This post describes a similar issue: https://gitlab.freedesktop.org/drm/intel/-/issues/4858 I tried using a workaround from the above link, to set GPU to max frequency using command "intel_gpu_frequency -m", this seemed to reduce the rate of occurrence from once per day to once every 3 days, but this is not a permanent solution. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2059033 Title: Xorg crashes with SIGABRT Status in mesa package in Ubuntu: New Bug description: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at
[Touch-packages] [Bug 2057836] Re: gst-python1.0 fails to build: test failures
Debian added a b-d on pygobject >= 3.48.1, which we don't have -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/2057836 Title: gst-python1.0 fails to build: test failures Status in pygobject: New Status in gst-python1.0 package in Ubuntu: Triaged Status in pygobject package in Ubuntu: Triaged Status in gst-python1.0 package in Debian: Confirmed Bug description: gst-python1.0 fails to build because of test failures. https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1 https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1 I have reported the issue to the upstream developers https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353 To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/2057836/+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 2053228] Re: software-properties-gtk does not start
Version from proposed works fine, thanks.
corrado@corrado-n7-nn-0306:~$ apt policy software-properties-gtk
software-properties-gtk:
Installed: 0.99.44
Candidate: 0.99.44
Version table:
*** 0.99.44 100
100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
100 http://archive.ubuntu.com/ubuntu noble-proposed/main i386 Packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Fix Committed
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
Following up, `Acquire::Retries=0` seems to be avoiding the bug in prod,
which strengthens my suspicion that it's related to retries.
As for the actual bug, when apt is hanging, I notice that the work queue
has items in it, but they have not been delegated to a worker. There is
a condition that is supposed to "unstuck" the queue here[1], but for
some reason `GetFetchAfter` is returning a zeroed time_point which
avoids that condition[2].
The way we're setting `FetchAfter` looks OK to me[3] though I'm not
familiar with std::chrono. Maybe there's some other place where we're
partially copying the item or instantiating a new item and failing to
copy the `FetchAfter` value.
A bandaid patch is attached. I'm not sure if there's any downside in
calling `Cycle` there. A real bugfix IMO would address the zeroed
`FetchAfter` value described above, or potentially refactor so that work
items are immediately delegated instead of having to rely on calling
`Cycle` at the right time. I am missing a lot of context so that maybe
that's not possible.
[1] https://salsa.debian.org/apt-
team/apt/-/blob/db797312548f6e7d6d1d1faa9f1e48c1e521d290/apt-
pkg/acquire.cc#L738-740
[2] https://salsa.debian.org/apt-
team/apt/-/blob/db797312548f6e7d6d1d1faa9f1e48c1e521d290/apt-
pkg/acquire.cc#L733-736
[3] https://salsa.debian.org/apt-
team/apt/-/blob/db797312548f6e7d6d1d1faa9f1e48c1e521d290/apt-
pkg/acquire-worker.cc#L651-655
** Attachment added: "patch"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+attachment/5759339/+files/patch
--
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/2003851
Title:
occasional hanging 'apt-get update' from daily cronjob since Jammy
22.04
Status in apt package in Ubuntu:
Confirmed
Bug description:
Hi!
Yesterday I spotted several machines of ours where a period `apt-get
update` was stalled. The `http` children were hanging in `WaitFd`
(waiting for parent instructions/queue). The parent was looping in
`AcquireUpdate` every 500ms.
We have a cronjob that runs every few hours which calls `apt-get update` and
does some post-processing. We noticed that several of them had stalled at some
point in time. Killing the parent (apt-get) got it unstuck, removing the locks.
Example:
```
# apt-get update
Reading package lists... Done
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 154026
(apt-get)
N: Be aware that removing the lock file is not a solution and may break your
system.
E: Unable to lock directory /var/lib/apt/lists/
```
Task listing:
```
root 153929 \_ /usr/sbin/CRON -f -P
root 153942 \_ /bin/sh -c [ -x /etc/zabbix/scripts/dpkg.updates ]
&& /etc/zabbix/scripts/dpkg.updates --cron
root 153943 \_ /bin/sh /etc/zabbix/scripts/dpkg.updates --cron
root 154026 \_ apt-get update
_apt 154029 \_ /usr/lib/apt/methods/http
_apt 154030 \_ /usr/lib/apt/methods/http
_apt 154031 \_ /usr/lib/apt/methods/http
_apt 154033 \_ /usr/lib/apt/methods/gpgv
```
Open (TCP) sockets. All have 1 item in the Recv-Q (probably a FIN or RST?):
```
# netstat -apn | grep -E '154026|154029|154030|154031|154033'
tcp 1 0 10.x.x.x:60868 217.x.x.x:80 CLOSE_WAIT 154030/http
tcp 1 0 10.x.x.x:40756 178.x.x.x:80 CLOSE_WAIT 154029/http
tcp 1 0 10.x.x.x:56818 185.x.x.x:80 CLOSE_WAIT 154031/http
```
All children (including gpgv) were waiting using pselect6(1, [0], NULL, NULL,
NULL, NULL).
The parent (apt-get) was waiting using pselect6(10, [5 6 7 9], [],
NULL, {tv_sec=0, tv_nsec=5}, NULL).
The http sockets in the children were at fd=3.
Parent lsof:
```
# lsof -p 154026 +E
...
apt-get 154026 root4uW REG8,10 262281
/var/lib/apt/lists/lock
apt-get 154026 root5r FIFO 0,13 0t0 4015176 pipe 154029,http,1w
apt-get 154026 root6r FIFO 0,13 0t0 4012448 pipe 154030,http,1w
apt-get 154026 root7r FIFO 0,13 0t0 4015192 pipe 154031,http,1w
apt-get 154026 root8w FIFO 0,13 0t0 4015177 pipe 154029,http,0r
apt-get 154026 root9r FIFO 0,13 0t0 4015233 pipe 154033,gpgv,1w
apt-get 154026 root 10w FIFO 0,13 0t0 4012449 pipe 154030,http,0r
apt-get 154026 root 12w FIFO 0,13 0t0 4015193 pipe 154031,http,0r
apt-get 154026 root 14w FIFO 0,13 0t0 4015234 pipe 154033,gpgv,0r
http 154029 _apt0r FIFO 0,13 0t0 4015177 pipe
154026,apt-get,8w
http 154029 _apt1w FIFO 0,13 0t0 4015176 pipe
154026,apt-get,5r
http 154030 _apt0r FIFO 0,13 0t0 4012449 pipe
154026,apt-get,10w
http 154030 _apt1w FIFO 0,13 0t0 4012448 pipe
[Touch-packages] [Bug 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8
Sponsored! ** Changed in: cups-browsed (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2058866 Title: proposed-migration for cups-browsed 2.0.0-0ubuntu8 Status in apparmor package in Ubuntu: New Status in cups-browsed package in Ubuntu: Fix Committed Bug description: cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via an autopkgtest), early enough that LD_DEBUG=all gives no output. A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable ran, so 8 was uploaded to try to fix this. But the executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups- browsed and segfaults when invoked as /usr/sbin/cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8
I'll take care of the sponsoring. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2058866 Title: proposed-migration for cups-browsed 2.0.0-0ubuntu8 Status in apparmor package in Ubuntu: New Status in cups-browsed package in Ubuntu: New Bug description: cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via an autopkgtest), early enough that LD_DEBUG=all gives no output. A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable ran, so 8 was uploaded to try to fix this. But the executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups- browsed and segfaults when invoked as /usr/sbin/cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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 2058800] Re: [needs-packaging] Add systemd-bsod
This is already done in noble. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- 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/2058800 Title: [needs-packaging] Add systemd-bsod Status in systemd package in Ubuntu: Fix Released Bug description: One of the components of systemd 255 and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2058800/+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
Re: [Touch-packages] [Bug 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
Hello Hui Wang, yeah unfortunately i think it's a hardware issue since i tried windows and fedora but same thing. For the bluetooth headphone (Redmi buds 4 active) in windows and fedora works fine, in ubuntu even if I set output a configuration to HSP/HFP instead of A2DP mic doesn't work, the only way to get it work is to remove the device from bluetooth settings and set it up again. I recorded a short video for the issue : https://youtu.be/cZaSqgFJ-Gw On Sat, Mar 23, 2024 at 1:20 AM Hui Wang <2051...@bugs.launchpad.net> wrote: > Please upload a complete dmesg with the kernel you updated on 19/03/2024 > (dummy output). > > And could you also test the latest upstream mainline kernel or ubuntu > 24.04 (just put the iso to usb flash drive, boot from it and try ubuntu > 24.04, no need to install). > > https://kernel.ubuntu.com/mainline/v6.8/ > > > And also, it looks like a hardware issue to me. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2051570 > > Title: > [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] > Underruns, dropouts or crackling sound > > Status in alsa-driver package in Ubuntu: > New > > Bug description: > Since the last three weeks' updates, I have encountered several > challenges with the audio functionality on my system. Primarily, upon > starting my laptop, the audio often fails to work, displaying "Dummy > Output." To resolve this, I find myself needing to restart the laptop > two or three times before the audio becomes functional. > > Even when the audio is working, I've noticed a recurring issue where, > after playing video or audio for approximately 2-3 minutes, the sound > starts crackling and buzzing. The intensity of these distortions > gradually increases, resembling the static interference on a radio > station with a weak signal. This issue persists even when using 3.5mm > headphones, requiring the use of a USB headset or Bluetooth headphones > to enjoy distortion-free audio. > > Furthermore, I have observed that, regardless of the Ubuntu version > (ranging from 22.04 to 22.04.3), I face difficulties changing the > microphone output settings when an external audio peripheral, such as > a USB headset, 3.5mm headphones, or Bluetooth headphones, is > connected. The OS appears to exclusively utilize the microphone from > the connected peripheral, making it impossible to switch to the > laptop's built-in microphone. > > For your reference, here are the specifications of my laptop and the > Ubuntu version I am currently using: > > Laptop: Dell Vostro 3400 > CPU: 11th Gen Intel i5-1135G7 > GPU: Intel TigerLake-LP GT2 Iris Xe > Memory: 2490MiB / 19720MiB > Resolution: 1920x1080 > OS: Ubuntu 22.04.3 LTS x86_64 > Kernel: 6.5.0-14-generic > DE: GNOME 42.9 > Shell: bash 5.1.16 > Sound Card: Card: HDA Intel PCH, Chip: Cirrus Logic CS8409/CS42L42 > > **UPDATE 12/02/2024 Noticed that every time my laptop fan starts > spinning the crackling sound appears, after fan stops the crackling sound > disappear. > **UPDATE 19/03/2024 I did a software update to the linux kernel > 6.5.0-26, now i get a dummy output in sound even if i restart the system > many times, and if i use my Bluetooth headphone i can't use the mic, > neither the mic of the laptop or of the headphone (there is no option is > the settings to choose from) it's all blank. > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu7 > ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 > Uname: Linux 6.5.0-15-generic x86_64 > ApportVersion: 2.20.11-0ubuntu82.5 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: galxy-a10 1437 F pulseaudio > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Mon Jan 29 17:50:44 2024 > InstallationDate: Installed on 2024-01-16 (13 days ago) > InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 > (20230807.2) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH > successful > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_Jack: Speaker, Internal > Symptom_PulseAudioLog: جانفي 29 17:49:49 galxya10-VR > whoopsie-upload-all[712]: > INFO:root:/var/crash/_usr_bin_pulseaudio.1000.crash already marked for > upload, skipping > Symptom_PulsePlaybackTest: PulseAudio playback test successful > Symptom_Type: Underruns, dropouts, or "crackling" sound > Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] > Underruns, dropouts or crackling sound > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/03/2023 > dmi.bios.release: 1.27 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.27.1 > dmi.board.name: 0GGCMJ >
[Touch-packages] [Bug 2058930] Re: Missing in i386 Packages index
Actually, this seems to be an issue of the source package not being pulled from -proposed, as I can install the binaries just fine in a LXD container: root@nn:~# dpkg --add-architecture i386 root@nn:~# apt update [...] root@nn:~# apt install libvpx9:i386 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libnsl-dev libtirpc-dev Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-14-base:i386 libc-bin libc-dev-bin libc-devtools libc6 libc6:i386 libc6-dev libgcc-s1:i386 libidn2-0:i386 libunistring5:i386 locales Suggested packages: glibc-doc glibc-doc:i386 locales:i386 libnss-nis:i386 libnss-nisplus:i386 The following NEW packages will be installed: gcc-14-base:i386 libc6:i386 libgcc-s1:i386 libidn2-0:i386 libunistring5:i386 libvpx9:i386 The following packages will be upgraded: libc-bin libc-dev-bin libc-devtools libc6 libc6-dev locales 6 upgraded, 6 newly installed, 0 to remove and 7 not upgraded. Need to get 15.3 MB of archives. After this operation, 18.6 MB of additional disk space will be used. Do you want to continue? [Y/n] [...] Get:12 http://archive.ubuntu.com/ubuntu noble-proposed/main i386 libvpx9 i386 1.14.0-1ubuntu1 [1129 kB] 0 root@nn:~# apt-get source libvpx Reading package lists... Done NOTICE: 'libvpx' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/multimedia-team/libvpx.git Please use: git clone https://salsa.debian.org/multimedia-team/libvpx.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 4332 kB of source archives. Get:1 http://archive.ubuntu.com/ubuntu noble/main libvpx 1.13.1-2ubuntu1 (dsc) [2366 B] Get:2 http://archive.ubuntu.com/ubuntu noble/main libvpx 1.13.1-2ubuntu1 (tar) [4316 kB] Get:3 http://archive.ubuntu.com/ubuntu noble/main libvpx 1.13.1-2ubuntu1 (diff) [13.6 kB] Fetched 4332 kB in 1s (8427 kB/s) dpkg-source: info: extracting libvpx in libvpx-1.13.1 dpkg-source: info: unpacking libvpx_1.13.1.orig.tar.xz dpkg-source: info: unpacking libvpx_1.13.1-2ubuntu1.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying 0001-Relax-ABI-check.patch dpkg-source: info: applying 0002-Do-not-undefine-_FORTIFY_SOURCE.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/2058930 Title: Missing in i386 Packages index Status in libvpx package in Ubuntu: New Bug description: The new version of libvpx 1.14 seems not to be published to http://ftpmaster.internal on i386 only. This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having any effect on i386: https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/2058930/+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 2058930] Re: Missing in i386 Packages index
** Description changed: - The new version of libvpx 1.14 seems to be missing in - http://archive.ubuntu.com/ubuntu/dists/noble- - proposed/main/binary-i386/Packages.xz, while it's still available in - http://archive.ubuntu.com/ubuntu/dists/noble- - proposed/main/binary-i386/Packages.gz. - - Grep for "Source: libvpx". + The new version of libvpx 1.14 seems not to be published to + http://ftpmaster.internal on i386 only. This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having any effect on i386: https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/2058930 Title: Missing in i386 Packages index Status in libvpx package in Ubuntu: New Bug description: The new version of libvpx 1.14 seems not to be published to http://ftpmaster.internal on i386 only. This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having any effect on i386: https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/2058930/+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 2058930] [NEW] Missing in i386 Packages index
Public bug reported: The new version of libvpx 1.14 seems not to be published to http://ftpmaster.internal on i386 only. This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having any effect on i386: https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386 ** Affects: libvpx (Ubuntu) Importance: Undecided Status: New ** Tags: rls-nn-incoming update-excuse ** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/2058930 Title: Missing in i386 Packages index Status in libvpx package in Ubuntu: New Bug description: The new version of libvpx 1.14 seems not to be published to http://ftpmaster.internal on i386 only. This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having any effect on i386: https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/2058930/+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 2055148] Re: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan
** Tags added: fr-7190 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2055148 Title: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan Status in Netplan: Triaged Status in netplan.io package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: From: https://discourse.ubuntu.com/t/blog-netplan-developer- diaries/35932/11 Hi all, NetworkManager connections with an explicit DoT (DNS over TLS) configuration are not supported with Netplan, but NetworkManager does feed back the DoT DNS info with server address and Server Name Indication (SNI) in the form server_address#SNI, e.g. 1.2.3.4#dns.myhome.com as nameserver addresses to Netplan. As a result, subsequent Netplan config applications fail because DNS servers don’t have the expected dotted decimal (IPv4) or colon’ed hex (IPv6) form. ``` nmcli> describe ipv4.dns === [dns] === [NM property description] Array of IP addresses of DNS servers. For DoT (DNS over TLS), the SNI server name can be specified by appending "#example.com" to the IP address of the DNS server. This currently only has effect when using systemd-resolved. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2055148/+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 2058743] Re: systemd local DNS tests failing with timeout
** Attachment added: "Output of networkd-test.py" https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+attachment/5759255/+files/networkd-test.log -- 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/2058743 Title: systemd local DNS tests failing with timeout Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Investigations done in 22.04/Jammy but may be affecting other series, too. The dnsmasq package recently was updated from 2.86-1.1ubuntu0.5 to 2.90-0ubuntu0.22.04.1. This seems to have brought back the same issue reported in bug #1957086. Sounds like both have interaction issues. To reproduce: $ pull-lp-source systemd jammy # Install test deps $ sudo apt install systemd udev libpam-systemd libnss-systemd acl locales evemu-tools python3 pkg-config cryptsetup-bin systemd-sysv policykit-1 dnsmasq-base $ cd systemd-249.11/test/ $ sudo ./networkd-test.py == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/home/ubuntu/systemd-249.11/test/./networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 421, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 526, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 252.167s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+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 2058743] Re: systemd local DNS tests failing with timeout
** Attachment added: "Journal of systemd while running the test" https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+attachment/5759257/+files/systemd.log -- 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/2058743 Title: systemd local DNS tests failing with timeout Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Investigations done in 22.04/Jammy but may be affecting other series, too. The dnsmasq package recently was updated from 2.86-1.1ubuntu0.5 to 2.90-0ubuntu0.22.04.1. This seems to have brought back the same issue reported in bug #1957086. Sounds like both have interaction issues. To reproduce: $ pull-lp-source systemd jammy # Install test deps $ sudo apt install systemd udev libpam-systemd libnss-systemd acl locales evemu-tools python3 pkg-config cryptsetup-bin systemd-sysv policykit-1 dnsmasq-base $ cd systemd-249.11/test/ $ sudo ./networkd-test.py == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/home/ubuntu/systemd-249.11/test/./networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 421, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 526, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 252.167s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+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 2058743] Re: systemd local DNS tests failing with timeout
** Attachment added: "Log of the DNS resolving dnsmasq while running the test" https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+attachment/5759256/+files/dnsmasq-vpn.log -- 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/2058743 Title: systemd local DNS tests failing with timeout Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Investigations done in 22.04/Jammy but may be affecting other series, too. The dnsmasq package recently was updated from 2.86-1.1ubuntu0.5 to 2.90-0ubuntu0.22.04.1. This seems to have brought back the same issue reported in bug #1957086. Sounds like both have interaction issues. To reproduce: $ pull-lp-source systemd jammy # Install test deps $ sudo apt install systemd udev libpam-systemd libnss-systemd acl locales evemu-tools python3 pkg-config cryptsetup-bin systemd-sysv policykit-1 dnsmasq-base $ cd systemd-249.11/test/ $ sudo ./networkd-test.py == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/home/ubuntu/systemd-249.11/test/./networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 421, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 526, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 252.167s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+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 2058743] Re: systemd local DNS tests failing with timeout
Could you please provide journalctl debug logs from systemd-resolved, so we can get more details of what's going on? e.g. put this into the systemd-resolved override.conf [Service] Environment=SYSTEMD_LOG_LEVEL=debug $ sudo systemctl edit systemd-resolved $ sudo systemctl restart systemd-resolved And maybe also provide dnsmasq logs. ** Tags added: rls-jj-incoming -- 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/2058743 Title: systemd local DNS tests failing with timeout Status in dnsmasq package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Investigations done in 22.04/Jammy but may be affecting other series, too. The dnsmasq package recently was updated from 2.86-1.1ubuntu0.5 to 2.90-0ubuntu0.22.04.1. This seems to have brought back the same issue reported in bug #1957086. Sounds like both have interaction issues. To reproduce: $ pull-lp-source systemd jammy # Install test deps $ sudo apt install systemd udev libpam-systemd libnss-systemd acl locales evemu-tools python3 pkg-config cryptsetup-bin systemd-sysv policykit-1 dnsmasq-base $ cd systemd-249.11/test/ $ sudo ./networkd-test.py == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/home/ubuntu/systemd-249.11/test/./networkd-test.py", line 678, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 421, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 526, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 252.167s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+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 2058876] Re: display freeze
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.
Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2058876
Title:
display freeze
Status in Ubuntu:
Incomplete
Bug description:
The display keeps freezing. Sometime mouse keeps freezing. Sometime
after a sleep, when the laptop wake ups, the display not working or it
remain blank. again I have to restart it. It is very annoying as your
workspace i.e. all the opened apps got deleted. Again you have to
restart. It hampers the work. I am using NVIDIA driver 535 (tested)
display driver, which is recommended. I have gtx 1650 graphics. Ryzen
5 4000 series processor.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-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 535.161.07 Sat Feb 17
22:55:48 UTC 2024
GCC version:
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: Mon Mar 25 09:29:55 2024
DistUpgraded: 2024-01-13 13:01:05,362 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: I don't know
GraphicsCard:
NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] TU117M [1025:1447]
Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c7) (prog-if
00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Renoir [1025:1455]
InstallationDate: Installed on 2023-08-30 (208 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_IN
LANGUAGE=en_IN:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=33f81450-d6fa-4803-aba2-9ddca9a4a12a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2024-01-13 (72 days ago)
dmi.bios.date: 02/04/2021
dmi.bios.release: 1.4
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Stonic_RNS
dmi.board.vendor: RO
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.04
dmi.ec.firmware.release: 1.2
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.04:bd02/04/2021:br1.4:efr1.2:svnAcer:pnNitroAN515-44:pvrV1.04:rvnRO:rnStonic_RNS:rvrV1.04:cvnAcer:ct10:cvrV1.04:sku:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN515-44
dmi.product.sku:
dmi.product.version: V1.04
dmi.sys.vendor: Acer
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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
[Touch-packages] [Bug 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8
The attachment "apparmor-add-execmap.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2058866 Title: proposed-migration for cups-browsed 2.0.0-0ubuntu8 Status in apparmor package in Ubuntu: New Status in cups-browsed package in Ubuntu: New Bug description: cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via an autopkgtest), early enough that LD_DEBUG=all gives no output. A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable ran, so 8 was uploaded to try to fix this. But the executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups- browsed and segfaults when invoked as /usr/sbin/cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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 2058876] Re: display freeze
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2058876
Title:
display freeze
Status in xorg package in Ubuntu:
New
Bug description:
The display keeps freezing. Sometime mouse keeps freezing. Sometime
after a sleep, when the laptop wake ups, the display not working or it
remain blank. again I have to restart it. It is very annoying as your
workspace i.e. all the opened apps got deleted. Again you have to
restart. It hampers the work. I am using NVIDIA driver 535 (tested)
display driver, which is recommended. I have gtx 1650 graphics. Ryzen
5 4000 series processor.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-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 535.161.07 Sat Feb 17
22:55:48 UTC 2024
GCC version:
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: Mon Mar 25 09:29:55 2024
DistUpgraded: 2024-01-13 13:01:05,362 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: I don't know
GraphicsCard:
NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] TU117M [1025:1447]
Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c7) (prog-if
00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Renoir [1025:1455]
InstallationDate: Installed on 2023-08-30 (208 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_IN
LANGUAGE=en_IN:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=33f81450-d6fa-4803-aba2-9ddca9a4a12a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2024-01-13 (72 days ago)
dmi.bios.date: 02/04/2021
dmi.bios.release: 1.4
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Stonic_RNS
dmi.board.vendor: RO
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.04
dmi.ec.firmware.release: 1.2
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.04:bd02/04/2021:br1.4:efr1.2:svnAcer:pnNitroAN515-44:pvrV1.04:rvnRO:rnStonic_RNS:rvrV1.04:cvnAcer:ct10:cvrV1.04:sku:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN515-44
dmi.product.sku:
dmi.product.version: V1.04
dmi.sys.vendor: Acer
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/xorg/+bug/2058876/+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 2058876] [NEW] display freeze
You have been subscribed to a public bug:
The display keeps freezing. Sometime mouse keeps freezing. Sometime
after a sleep, when the laptop wake ups, the display not working or it
remain blank. again I have to restart it. It is very annoying as your
workspace i.e. all the opened apps got deleted. Again you have to
restart. It hampers the work. I am using NVIDIA driver 535 (tested)
display driver, which is recommended. I have gtx 1650 graphics. Ryzen 5
4000 series processor.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-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 535.161.07 Sat Feb 17
22:55:48 UTC 2024
GCC version:
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: Mon Mar 25 09:29:55 2024
DistUpgraded: 2024-01-13 13:01:05,362 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: I don't know
GraphicsCard:
NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] TU117M [1025:1447]
Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c7) (prog-if 00
[VGA controller])
Subsystem: Acer Incorporated [ALI] Renoir [1025:1455]
InstallationDate: Installed on 2023-08-30 (208 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_IN
LANGUAGE=en_IN:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=33f81450-d6fa-4803-aba2-9ddca9a4a12a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2024-01-13 (72 days ago)
dmi.bios.date: 02/04/2021
dmi.bios.release: 1.4
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Stonic_RNS
dmi.board.vendor: RO
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.04
dmi.ec.firmware.release: 1.2
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.04:bd02/04/2021:br1.4:efr1.2:svnAcer:pnNitroAN515-44:pvrV1.04:rvnRO:rnStonic_RNS:rvrV1.04:cvnAcer:ct10:cvrV1.04:sku:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN515-44
dmi.product.sku:
dmi.product.version: V1.04
dmi.sys.vendor: Acer
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug freeze mantic ubuntu
--
display freeze
https://bugs.launchpad.net/bugs/2058876
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to xorg in Ubuntu.
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058838] Re: Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg crash + Crash -- 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/2058838 Title: Crash Status in Ubuntu: Incomplete Bug description: When switching KVM my X session crashes. Syslog gets cleared as well for some reason. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-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 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 23:58:33 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GA102GL [RTX A5000] [10de:2231] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA102GL [RTX A5000] [10de:147e] InstallationDate: Installed on 2022-04-07 (717 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) MachineType: ASUS System 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.8.0-11-generic root=UUID=c56061b9-1478-4914-a919-96eb077fff48 ro quiet splash nvidia-drm.modeset=1 initcall_blacklist=acpi_cpufreq_init amd_pstate=active amd_pstate.shared_mem=1 acpi_enforce_resources=lax vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2023 dmi.bios.release: 18.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1807 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1807:bd09/26/2023:br18.7:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.init.d.apport: 2024-02-22T08:20:00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 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/+bug/2058838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
