[Desktop-packages] [Bug 1986468] Re: right click on icon does not always show bookmarks
Seems Nautilus in 24.04 still has the same behavior : no bookmarks shown when right clicking its icon in dash unless nautilus is already running. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1986468 Title: right click on icon does not always show bookmarks Status in nautilus package in Ubuntu: New Bug description: Hi, Ubuntu 22.04 here. A right click on Nautilus icon ( in the dock ) does not always show the list of bookmarks ( automatic and manually added ). Nautilus has to be already launched and running in order to show that list. This list of « shortcuts » was ago always accessible on right click - in Unity. It's a very convenient list of shortcuts, non-intrusive, calm on the eyes, and fast. On Xorg I may be able to launch Nautilus as a minimized window, using xdotools or wmctrl or devilspie. On Wayland I don't know how to do that : starting Nautilus as a minimized window with my session might be a workaround for that missing list. But ideally an option for Nautilus to start minimized sounds cleaner ( but options like -%u or --start-minimized are not offered by Nautilus afaik ). For references : ⋅ https://forum.ubuntu-fr.org/viewtopic.php?id=2073543 ⋅ https://forum.ubuntu-fr.org/viewtopic.php?id=2072493 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1986468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028819] Re: File-Roller should depend on 7zip package instead of abandoned p7zip-full since version 43
The p7zip dependency was Debian-only so there is nothing at all to fix on the Ubuntu side. Therefore, I am closing this bug. ** Changed in: file-roller (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/2028819 Title: File-Roller should depend on 7zip package instead of abandoned p7zip- full since version 43 Status in file-roller package in Ubuntu: Fix Released Status in file-roller package in Debian: Fix Released Bug description: File-Roller switched from p7zip to official 7zip utility since version 43.alpha , see https://gitlab.gnome.org/GNOME/file-roller/-/commit/b798bbd96d3777c20026f1dc2d3e15ecb5bc853d and https://gitlab.gnome.org/GNOME/file-roller/-/commit/a4359d11e05023605c4270c67ad703bc8a71f8fd but File-Roller Ubuntu/Debian package version 43-1 still depends on abandoned by upstream p7zip-full, while it should depend on 7zip package instead of p7zip-full or maybe better to have "Depends: 7zip | p7zip-full" ? There are lots of bugs in p7zip, for example some large zip files cannot be extract on 16.02 but can on 9.20, see https://sourceforge.net/p/p7zip/discussion/383044/ and http://bugs.debian.org/src:p7zip also https://bugs.launchpad.net/ubuntu/+source/p7zip It seems Debian developers planing to replace p7zip-full with official 7zip package, see https://bugs.debian.org/991428 Also there is a related note in NEWS file: - Distros will want to adjust the `data/packages.match` file. Some archive managers in Ubuntu/Debian already depends on official 7zip package instead of p7zip, see arqiver for example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2028819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Ubuntu 24.04 installed today. Firefox autonomous archive downloaded from https://www.mozilla.org/fr/firefox/all/#product-desktop-release And « ooops… » in any tab, terminal says : [Parent 5931, IPC I/O Parent] WARNING: process 6020 exited on signal 11: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265 [Parent 5931, IPC I/O Parent] WARNING: process 6026 exited on signal 11: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265 [Parent 5931, IPC I/O Parent] WARNING: process 6036 exited on signal 11: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265 [Parent 5931, IPC I/O Parent] WARNING: process 6084 exited on signal 11: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265 [Parent 5931, IPC I/O Parent] WARNING: process 6099 exited on signal 11: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265 [Parent 5931, IPC I/O Parent] WARNING: process 6110 exited on signal 11: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265 [Parent 5931, IPC I/O Parent] WARNING: process 6119 exited on signal 11: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265 [Parent 5931, IPC I/O Parent] WARNING: process 6128 exited on signal 11: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265 [Parent 5931, IPC I/O Parent] WARNING: process 6143 exited on signal 11: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265 [Parent 5931, IPC I/O Parent] WARNING: process 6147 exited on signal 11: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265 [Parent 5931, IPC I/O Parent] WARNING: process 6150 exited on signal 11: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:265 …firefox as a snap looks to run fine but I have many bwrap processes that use 100% cpu to the point of over-heating. Is it related ? See picture of monitor → https://i.ibb.co/BZCfNjJ/2404-bwrap.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Invalid Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Invalid Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Incomplete Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Confirmed Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Invalid Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Released Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiph
[Desktop-packages] [Bug 2059281] Re: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd
I have uploaded c2esp 27-11ubuntu4 now. In the code of c2esp I have found some logging statements which cast pointer addresses to long int. Probably this works only on 64-bit and not on 32-bit and so caused the crashes in the autopkgtest. I could not test whether it is really the fix, I am simply giving it a try. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to c2esp in Ubuntu. https://bugs.launchpad.net/bugs/2059281 Title: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd Status in c2esp package in Ubuntu: In Progress Status in cups package in Ubuntu: Fix Released Bug description: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059281] Re: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd
Problem seems to be rather the broken cups.pc file from Debian in the cups package, which is fixed in 2.4.7-1.2ubuntu2, as after this cups release the tests of said packages have passed. ** Package changed: libcupsfilters (Ubuntu) => cups (Ubuntu) ** Changed in: cups (Ubuntu) Status: Triaged => Fix Released ** Also affects: c2esp (Ubuntu) Importance: Undecided Status: New ** Changed in: c2esp (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to c2esp in Ubuntu. https://bugs.launchpad.net/bugs/2059281 Title: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd Status in c2esp package in Ubuntu: In Progress Status in cups package in Ubuntu: Fix Released Bug description: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2052820] Re: RDP Remote Desktop :[ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1
Is this issue still relevant to you and do you have non-ascii chars in your rdp password? see: https://askubuntu.com/a/1462215 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2052820 Title: RDP Remote Desktop :[ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 Status in gnome-remote-desktop package in Ubuntu: New Bug description: Subject: [GNOME Remote Desktop] Error with File Descriptor Check Leading to Connection Closure Dear Ubuntu Community, I am reaching out to report an issue encountered with the `gnome- remote-desktop` service on my system. I have been experiencing connection stability issues, and upon inspecting the service's logs, I found repeated errors related to file descriptor checks and connection closures. **System Information:** - **OS**: Ubuntu 20.04 LTS - **GNOME Remote Desktop Version**: (please insert your version here) - **System Architecture**: (please insert your architecture here, e.g., x86_64) **Issue Description:** The `gnome-remote-desktop` service consistently logs errors indicating an inability to check file descriptors, leading to the closure of remote desktop connections. These errors occur during the negotiation of security protocols and seem to prevent successful remote desktop sessions. **Relevant Log Excerpts:** 2月 09 23:46:10 taichu-System gnome-remote-desktop-daemon[489774]: [23:46:10:236] [489774:535692] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 2月 09 23:46:10 taichu-System gnome-remote-de[489774]: Unable to check file descriptor, closing connection 2月 09 23:46:10 taichu-System gnome-remote-desktop-daemon[489774]: [23:46:10:808] [489774:535727] [ERROR][com.freerdp.core.peer] - peer_recv_callback: CONNECTION_STATE_INITIAL - rdp_server_accept_n> 2月 09 23:46:10 taichu-System gnome-remote-de[489774]: Unable to check file descriptor, closing connection **Steps to Reproduce:** 1. Start `gnome-remote-desktop` service. 2. Attempt to establish a remote desktop connection from a client. 3. Observe the connection instability and check the service's logs for errors. **Expected Behavior:** The `gnome-remote-desktop` service should handle file descriptors correctly and maintain stable remote desktop connections without prematurely closing them. **Actual Behavior:** The service logs errors related to file descriptor checks and terminates remote desktop connections. **Attempts to Resolve:** - Restarted the `gnome-remote-desktop` service. - Checked for updates to the `gnome-remote-desktop` package. I have not found a workaround for this issue and am seeking assistance from the community to identify a fix or obtain a patch. Thank you for your attention to this matter. I am looking forward to any suggestions or guidance on resolving this issue. Best regards, Chinese User (from the Ubuntu Community) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-remote-desktop 42.9-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity Date: Fri Feb 9 23:52:15 2024 InstallationDate: Installed on 2023-12-03 (68 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-remote-desktop UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2052820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043517] Re: gnome-shell on non-active VT busy-loops through libwayland-server.so (sometimes)
** Changed in: xorg-server
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/2043517
Title:
gnome-shell on non-active VT busy-loops through libwayland-server.so
(sometimes)
Status in X.Org X server:
Fix Released
Status in mutter package in Ubuntu:
New
Status in xwayland package in Ubuntu:
New
Bug description:
I run several gnome sessions at once - different users on different
Virtual Terminals.
Sometimes, gnome-shell for a non-active VT starts using 100% CPU. Or,
actually 99% CPU because it's doing IPC as well. And the
corresponding XWayland uses 40% CPU.
FWIW, sending SIGSTOP to either gnome-shell or XWayland stops the
other one from busy-looping as well.
If I switch back to the affected VT, it appears to function fine, but
it is still using 100% + 40% CPU.
Version numbers:
Ubuntu 22.04.3 LTS
gnome-shell 42.9-0ubuntu2
xwayland 2:22.1.1-1ubuntu0.7
$ ps -aux | grep 'alan .*gnome-shell$'
alan9248 26.1 3.4 5492888 269136 ? Rsl 19:54 30:26
/usr/bin/gnome-shell
$ sudo strace -p 9248 2>&1|head
strace: Process 9248 attached
epoll_wait(37, [{events=EPOLLIN, data={u32=403234816, u64=139797293752320}}],
32, 0) = 1
recvmsg(21, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\1\0\0\0\0\0\f\0\3\0\0\0", iov_len=752}, {iov_base="",
iov_len=3344}], msg_iovlen=2, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC},
MSG_DONTWAIT|MSG_CMSG_CLOEXEC) = 12
write(4, "\1\0\0\0\0\0\0\0", 8) = 8
sendmsg(21, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\3\0\0\0\0\0\f\0[\2\0\0\1\0\0\0\1\0\f\0\3\0\0\0",
iov_len=24}], msg_iovlen=1, msg_controllen=0, msg_flags=0},
MSG_DONTWAIT|MSG_NOSIGNAL) = 24
poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLIN},
{fd=19, events=POLLIN}, {fd=20, events=POLLIN}, {fd=23, events=POLLIN}, {fd=24,
events=POLLIN}, {fd=25, events=POLLIN}, {fd=34, events=POLLIN}, {fd=36,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=54, events=POLLIN}, {fd=63,
events=POLLIN}, {fd=66, events=POLLIN}], 14, 79809702) = 2 ([{fd=4,
revents=POLLIN}, {fd=37, revents=POLLIN}])
read(4, "\2\0\0\0\0\0\0\0", 16) = 8
write(4, "\1\0\0\0\0\0\0\0", 8) = 8
epoll_wait(37, [{events=EPOLLIN, data={u32=403234816, u64=139797293752320}}],
32, 0) = 1
The recvmsg() call is here:
#0 __libc_recvmsg (fd=21, msg=0x7fff1de64a50, flags=1073741888) at
../sysdeps/unix/sysv/linux/recvmsg.c:35
#1 0x7f2531ea5ad6 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#2 0x7f2531ea4eea in wl_event_loop_dispatch () at
/lib/x86_64-linux-gnu/libwayland-server.so.0
#3 0x7f2531d2b45b in wayland_event_source_dispatch (base=, callback=, data=)
at ../src/wayland/meta-wayland.c:110
#4 0x7f2532b42d3b in g_main_dispatch (context=0x55c0046cc8f0) at
../../../glib/gmain.c:3419
#5 g_main_context_dispatch (context=0x55c0046cc8f0) at
../../../glib/gmain.c:4137
#6 0x7f2532b98258 in g_main_context_iterate.constprop.0
(context=0x55c0046cc8f0, block=block@entry=1, dispatch=dispatch@entry=1,
self=) at ../../../glib/gmain.c:4213
#7 0x7f2532b422b3 in g_main_loop_run (loop=0x55c00698ae30) at
../../../glib/gmain.c:4413
#8 0x7f2531cd0b79 in meta_context_run_main_loop
(context=context@entry=0x55c0046c70c0, error=error@entry=0x7fff1de64f08)
at ../src/core/meta-context.c:437
#9 0x55c003cf4f12 in main (argc=, argv=)
at ../src/main.c:650
The sendmsg() call is here:
Thread 1 "gnome-shell" hit Breakpoint 1, __libc_sendmsg (fd=21,
msg=0x7fff1de64c50, flags=16448) at ../sysdeps/unix/sysv/linux/sendmsg.c:26
26../sysdeps/unix/sysv/linux/sendmsg.c: No such file or directory.
(gdb) where
#0 __libc_sendmsg (fd=21, msg=0x7fff1de64c50, flags=16448) at
../sysdeps/unix/sysv/linux/sendmsg.c:26
#1 0x7f2531ea1c9d in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#2 0x7f2531ea565e in wl_display_flush_clients () at
/lib/x86_64-linux-gnu/libwayland-server.so.0
#3 0x7f2531d2b437 in wayland_event_source_prepare
(base=base@entry=0x55c004a374d0, timeout=timeout@entry=0x7fff1de64dc4)
at ../src/wayland/meta-wayland.c:97
#4 0x7f2532b428e7 in g_main_context_prepare (context=0x55c0046cc8f0,
priority=0x7fff1de64e50) at ../../../glib/gmain.c:3739
#5 0x7f2532b98123 in g_main_context_iterate.constprop.0
(context=0x55c0046cc8f0, block=block@entry=1, dispatch=dispatch@entry=1,
self=) at ../../../glib/gmain.c:4193
#6 0x7f2532b422b3 in g_main_loop_run (loop=0x55c00698ae30) at
../../../glib/gmain.c:4413
#7 0x7f2531cd0b79 in meta_context_run_main_loop
(context=context@entry=0x55c0046c70c0, error=error@entry=0x7fff1de64f08)
at ../src/core/meta-context.c:437
#8 0x55c003cf4f12 in main (argc=, argv=)
at ../src/main.c:650
To manage notification
[Desktop-packages] [Bug 2028819] Re: File-Roller should depend on 7zip package instead of abandoned p7zip-full since version 43
** Changed in: file-roller (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/2028819 Title: File-Roller should depend on 7zip package instead of abandoned p7zip- full since version 43 Status in file-roller package in Ubuntu: New Status in file-roller package in Debian: Fix Released Bug description: File-Roller switched from p7zip to official 7zip utility since version 43.alpha , see https://gitlab.gnome.org/GNOME/file-roller/-/commit/b798bbd96d3777c20026f1dc2d3e15ecb5bc853d and https://gitlab.gnome.org/GNOME/file-roller/-/commit/a4359d11e05023605c4270c67ad703bc8a71f8fd but File-Roller Ubuntu/Debian package version 43-1 still depends on abandoned by upstream p7zip-full, while it should depend on 7zip package instead of p7zip-full or maybe better to have "Depends: 7zip | p7zip-full" ? There are lots of bugs in p7zip, for example some large zip files cannot be extract on 16.02 but can on 9.20, see https://sourceforge.net/p/p7zip/discussion/383044/ and http://bugs.debian.org/src:p7zip also https://bugs.launchpad.net/ubuntu/+source/p7zip It seems Debian developers planing to replace p7zip-full with official 7zip package, see https://bugs.debian.org/991428 Also there is a related note in NEWS file: - Distros will want to adjust the `data/packages.match` file. Some archive managers in Ubuntu/Debian already depends on official 7zip package instead of p7zip, see arqiver for example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2028819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059726] [NEW] GNOME Snapshot doesn't show webcam image
Public bug reported:
I'm getting errors when I try to use GNOME Snapshot on Ubuntu Noble:
➜ snapshot
2024-03-28T19:30:02.289308Z INFO snapshot::application::imp: Snapshot
(org.gnome.Snapshot)
2024-03-28T19:30:02.289323Z INFO snapshot::application::imp: Version: 45.2
2024-03-28T19:30:02.289327Z INFO snapshot::application::imp: Datadir:
/usr/share/snapshot
libEGL warning: egl: failed to create dri2 screen
2024-03-28T19:30:02.675094Z ERROR aperture::viewfinder: Could not start
camerabin: Element failed to change its state
2024-03-28T19:30:02.679375Z ERROR aperture::viewfinder: Could not start
camerabin: Element failed to change its state
2024-03-28T19:30:02.680012Z ERROR aperture::viewfinder: Bus Error from
Some("/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir")
stream error: error output enum formats: Invalid argument
Some("../src/gst/gstpipewiresrc.c(689): on_state_changed ():
/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir")
2024-03-28T19:30:02.680031Z ERROR aperture::viewfinder: Bus Error from
Some("/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir")
Internal data stream error.
Some("../libs/gst/base/gstbasesrc.c(3175): gst_base_src_loop ():
/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir:\nstreaming
stopped, reason not-negotiated (-4)")
2024-03-28T19:30:02.680074Z ERROR aperture::viewfinder: Bus Error from
Some("/GstCameraBin:camerabin0/GstFileSink:videobin-filesink")
Could not open file "cap_%d" for writing.
Some("../plugins/elements/gstfilesink.c(507): gst_file_sink_open_file ():
/GstCameraBin:camerabin0/GstFileSink:videobin-filesink:\nsystem error:
Permission denied")
2024-03-28T19:30:02.680081Z ERROR aperture::viewfinder: Bus Error from
Some("/GstCameraBin:camerabin0/GstFileSink:videobin-filesink")
GStreamer error: state change failed and some element failed to post a proper
error message with the reason for the failure.
Some("../libs/gst/base/gstbasesink.c(5906): gst_base_sink_change_state ():
/GstCameraBin:camerabin0/GstFileSink:videobin-filesink:\nFailed to start")
2024-03-28T19:30:02.680318Z ERROR aperture::viewfinder: Bus Error from
Some("/GstCameraBin:camerabin0/GstFileSink:videobin-filesink")
Could not open file "cap_%d" for writing.
Some("../plugins/elements/gstfilesink.c(507): gst_file_sink_open_file ():
/GstCameraBin:camerabin0/GstFileSink:videobin-filesink:\nsystem error:
Permission denied")
2024-03-28T19:30:02.680325Z ERROR aperture::viewfinder: Bus Error from
Some("/GstCameraBin:camerabin0/GstFileSink:videobin-filesink")
GStreamer error: state change failed and some element failed to post a proper
error message with the reason for the failure.
Some("../libs/gst/base/gstbasesink.c(5906): gst_base_sink_change_state ():
/GstCameraBin:camerabin0/GstFileSink:videobin-filesink:\nFailed to start")
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-snapshot 45.2+vendored-0ubuntu1
Uname: Linux 6.8.2-x64v4-xanmod1 x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 28 16:31:40 2024
InstallationDate: Installed on 2021-11-26 (853 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: gnome-snapshot
UpgradeStatus: Upgraded to noble on 2024-02-23 (34 days ago)
** Affects: gnome-snapshot (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble third-party-packages wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-snapshot in Ubuntu.
https://bugs.launchpad.net/bugs/2059726
Title:
GNOME Snapshot doesn't show webcam image
Status in gnome-snapshot package in Ubuntu:
New
Bug description:
I'm getting errors when I try to use GNOME Snapshot on Ubuntu Noble:
➜ snapshot
2024-03-28T19:30:02.289308Z INFO snapshot::application::imp: Snapshot
(org.gnome.Snapshot)
2024-03-28T19:30:02.289323Z INFO snapshot::application::imp: Version: 45.2
2024-03-28T19:30:02.289327Z INFO snapshot::application::imp: Datadir:
/usr/share/snapshot
libEGL warning: egl: failed to create dri2 screen
2024-03-28T19:30:02.675094Z ERROR aperture::viewfinder: Could not start
camerabin: Element failed to change its state
2024-03-28T19:30:02.679375Z ERROR aperture::viewfinder: Could not start
camerabin: Element failed to change its state
2024-03-28T19:30:02.680012Z ERROR aperture::viewfinder: Bus Error
[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
Turns out after a fresh reboot the memory usage isn't much different
after I close all apps and VmData for gnome shell is only about 400MB.
So, perhaps this isn't the smoking gun I thought it was.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
Status in GNOME Shell:
Confirmed
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Bionic:
Fix Released
Bug description:
Upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
---
gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
almost 2 GiB.
user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
/usr/bin/gnome-shell
strace output is voluminous; here is a representative sample:
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\231\n\10\0\n\0
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
open("/proc/self/stat", O_RDONLY) = 36
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
fcntl(36, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
read(36, "", 3072) = 0
close(36) = 0
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) =
1 ([{fd=4, revents=POLLIN}])
read(4, "\1\0\0\0\0\0\0\0", 16) = 8
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, {msg_name(0)=NULL,
msg_iov(1)=[{"[\2\327&h\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, even
[Desktop-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade
Please refer to https://lists.ubuntu.com/archives/ubuntu- devel/2024-March/042954.html for more information about the current state of upgrades. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade
Temporary bypass: wget http://mirrors.kernel.org/ubuntu/pool/main/n/network-manager/network-manager_1.45.90-1ubuntu1_amd64.deb dpkg --force-all -i network-manager_1.45.90-1ubuntu1_amd64.deb dpkg output on my system: Preparing to unpack network-manager_1.45.90-1ubuntu1_amd64.deb ... Unpacking network-manager (1.45.90-1ubuntu1) over (1.45.90-1ubuntu1) ... dpkg: network-manager: dependency problems, but configuring anyway as you requested: network-manager depends on libnm0 (= 1.45.90-1ubuntu1); however: Version of libnm0:amd64 on system is 1.45.90-1ubuntu3. Setting up network-manager (1.45.90-1ubuntu1) ... ... After that everything works fine. Did the same with network-manager-openvpn and network-manager-openvpn- gnome to bring back VPN, also works. Btw, after full-upgrade I have a ton (114) of "not gonna be installed" packages in apt output because some libs are missing from repos, seems something went wrong when uploading new packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade
After the extensive upgrades of today no network. As per this bug report, network-manager seems to be gone. In my case this is a 24.04 Ubuntu Desktop QEMU/KVM VM running on my main Debian server host. In my case the command was "sudo apt dist-upgrade" ** Attachment added: "dpkg listing" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+attachment/5760309/+files/dpkg-network-manager.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018539] Re: File selector extremely slow
Same here... It's been months and it makes my desktop nearly unusable after a day or so... And I need to reboot to fix. It gets slower and slower with each use of the file selector. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2018539 Title: File selector extremely slow Status in nautilus package in Ubuntu: Confirmed Bug description: When you try to upload/download a file in an application (e.g. Firefox, Signal, etc) the file selector that opens is extremely slow to appear, search and change directory. Often times, if I try to search for a file in it, I have to wait 10 or more second before the letters I typed appear, and most of the time the last letter I pressed when typing, will appear before the rest of what I wrote, meaning I have to wait for my query to be deleted before I re-type it again. This has only just started since upgrading to Ubuntu 23.04. I noticed that Nautilus has been faster in general since the update, but in the file selector specifically, it's become unusable. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:39:48 2023 InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade
Yeah, I guess making a full-upgrade instead of upgrade was a bad idea :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058930] Re: Missing in i386 Packages index
Apparently this was linked to the extra `setup-commands` issue that made us loose the `proposed` pocket, and got "fixed" by updating the database with the `no-proposed` tag. TL;DR: fixed, and we didn't loose any cowboy specific to that issue, everything is fine. ** Changed in: libvpx (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop 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: Fix Released 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade
Guess it uninstalls network-manager to install new version but new version can't be installed because it depends on libnetplan1 which is missing from repos. https://packages.ubuntu.com/noble/network-manager currently shows [depends on] libnetplan1 (>= 0.106) Package not available You can't simply install previous version 1.45.90-1ubuntu1, which still shows in `apt show network-manager`, because its dependency libnm0 of the same version is already missing from repos. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058930] Re: Missing in i386 Packages index
** Tags removed: rls-nn-incoming -- You received this bug notification because you are a member of Desktop 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: Fix Released 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
I did the modification : [Unit] Description=Sound Service # We require pulseaudio.socket to be active before starting the daemon, because # while it is possible to use the service without the socket, it is not clear # why it would be desirable. # # A user installing pulseaudio and doing `systemctl --user start pulseaudio` # will not get the socket started, which might be confusing and problematic if # the server is to be restarted later on, as the client autospawn feature # might kick in. Also, a start of the socket unit will fail, adding to the # confusion. # # After=pulseaudio.socket is not needed, as it is already implicit in the # socket-service relationship, see systemd.socket(5). Requires=pulseaudio.socket ConditionUser=!root [Service] ExecStart=/usr/bin/pulseaudio - --daemonize=no --log-target=file:/home/$USER/pulse.txt LockPersonality=yes MemoryDenyWriteExecute=yes NoNewPrivileges=yes Restart=on-failure RestrictNamespaces=yes SystemCallArchitectures=native SystemCallFilter=@system-service # Note that notify will only work if --daemonize=no Type=notify UMask=0077 Slice=session.slice [Install] Also=pulseaudio.socket WantedBy=default.target However, after rebooting the system, I couldn't locate the pulse.txt file in my home directory (/home/$USER/) or by searching it, and have confirmed that hidden files are visible. On a positive note, I noticed that I can now choose the headphone microphone from the input device list without the need to delete and re-setup the headphone from the Bluetooth settings. Thanks for the help. On Thu, Mar 28, 2024 at 12:27 PM Hui Wang <2051...@bugs.launchpad.net> wrote: > The content in the pulseaudio.log (#9) is not helpful. > > > Could you edit /usr/lib/systemd/user/pulseaudio.service: > change the line "ExecStart=/usr/bin/pulseaudio --daemonize=no > --log-target=journal" to "ExecStart=/usr/bin/pulseaudio - > --daemonize=no --log-target=file:/home/$user/pulse.txt" > > reboot > > connect your bt headset and try to change profile from A2DP to HSP/HFP, > then upload the pulse.txt. > > -- > 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...
[Desktop-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
Thanks @vanvugt, this was helpful. I'm running ubuntu 23.10. It's been
about a week since I rebooted and I noticed swap usage was quite high.
I've got 32GB of RAM and am a developer with a bunch of stuff open at
once. Decided to investigate. Closed everything, but left just gnome
running and a terminal. Did a swapoff -a to clear swap and dropped
caches to get it as close to just what was allocated as possible. It
still showed 14GB of memory used with 5GB in cache. That seems high.
So, ran this to take a look at VmData for gnome-shell:
cat /proc/$(pgrep -f /usr/bin/gnome-shell)/status | grep VmData
That reveals:
VmData:1231000 kB
That seems a bit excessive.
Full disclosure. I do use extensions. It's too bare-bones without them.
I miss being able to Alt-F2 -> R and reboot gnome, but it appears to not
be possible now with Wayland.
> It's important to remember that RSS increases is no indication of a leak - it
> will rise and fall according to how busy the machine is and not how much new
> memory the process has allocated. Please ignore all RSS values as they are
> going to be unpredictable and misleading.
>
> As for VSZ, that's kind of related to potential leaks. The problem with VSZ
> is that it's a measure of the address space mappings size and is also not a
> measure of regular memory allocated by the process. Although you can use
> changes in VSZ to detect leaks and bloat, address space used by VSZ is not an
> indication of the memory requirements of the process.
>
> Probably a better field to monitor for actual leaks is VmData which you can
> find in:
> /proc/PID/status
>
> VmData is a more realistic indication of memory allocated by the process.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
Status in GNOME Shell:
Confirmed
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Bionic:
Fix Released
Bug description:
Upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
---
gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
almost 2 GiB.
user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
/usr/bin/gnome-shell
strace output is voluminous; here is a representative sample:
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\231\n\10\0\n\0
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource te
[Desktop-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037509] Re: Gnome/Ubuntu desktop wayland
Thanks for the bug report. Please attach screenshots, photos or a video of the problem so we can better understand the issue. ** Package changed: ubuntu-meta (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2037509 Title: Gnome/Ubuntu desktop wayland Status in Ubuntu: Incomplete Bug description: Good day, I hasten to inform you about a problem that has not left your distribution for several releases in a row. When the Wayland secant is launched, some window elements for control are not active. In particular, the open new tab/settings expand/collapse buttons in browsers and ower applications do not work. Snap and Deb are equally susceptible to this problem. The solution is to login to X11 and immediately log out and log into Wayland again. In the current builds of the Minotaur, the problem appeared quite recently, with the release of the public beta; in the builds for developers, this problem did not occur. I will be very upset if this problem goes into release. Please correct it if possible. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:14:33 2023 InstallationDate: Installed on 2023-06-21 (98 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230620) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2037509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059651] [NEW] network-manager gets uninstalled on apt full-upgrade
Public bug reported: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. ** Affects: network-manager (Ubuntu) Importance: High Status: New ** Affects: ubuntu-meta (Ubuntu) Importance: High Status: New ** Tags: noble ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade Status in network-manager package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2057773] Re: After the latest kernel update if you toggle wifi on and off the system crashes
** Summary changed: - After the latest Kernal update if you toggle wifi on and off the system crashes + After the latest kernel update if you toggle wifi on and off the system crashes ** Description changed: - I got a kernal update today and updated it. + I got a kernel update today and updated it. So after i updated it and toggled wifi on and off the system soft locked it is nonfunctional but the mouse still works. It even can't do a sudo reboot or reboot at all. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 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 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 13 15:23:23 2024 InstallationDate: Installed on 2024-01-22 (51 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) IpRoute: - default via 192.168.0.1 dev wlp2s0 proto dhcp src 192.168.2.37 metric 600 - 169.254.0.0/16 dev wlp2s0 scope link metric 1000 - 192.168.0.0/22 dev wlp2s0 proto kernel scope link src 192.168.2.37 metric 600 + default via 192.168.0.1 dev wlp2s0 proto dhcp src 192.168.2.37 metric 600 + 169.254.0.0/16 dev wlp2s0 scope link metric 1000 + 192.168.0.0/22 dev wlp2s0 proto kernel scope link src 192.168.2.37 metric 600 ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.44.2 connected started full enabled enabled enabled missing enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.44.2 connected started full enabled enabled enabled missing enabled -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2057773 Title: After the latest kernel update if you toggle wifi on and off the system crashes Status in network-manager package in Ubuntu: New Bug description: I got a kernel update today and updated it. So after i updated it and toggled wifi on and off the system soft locked it is nonfunctional but the mouse still works. It even can't do a sudo reboot or reboot at all. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 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 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 13 15:23:23 2024 InstallationDate: Installed on 2024-01-22 (51 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp src 192.168.2.37 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/22 dev wlp2s0 proto kernel scope link src 192.168.2.37 metric 600 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057773/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record
Is this issue solved till now? Also are these solutions applicable for Ubuntu 20.04.6 LTS or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2055148] Re: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan
https://github.com/canonical/netplan/pull/447 ** Changed in: netplan Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop 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: Fix Committed 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059418] [NEW] Bluetooth earbuds not being 'set up' on new machine
Public bug reported: The problem concerns earbuds 0B:20:24:A3:E7:56 T60 that worked perfectly under completely patched Ubuntu 22.04 on my old machine but now refuse to be setup on a new box running completely patched Ubuntu 22.04 . Other old bluetooth gadgets attached without issue. The end result at the very bottom of this page indicates ‘requestor exited before bonding was completed’ . root@bill:~# bluetoothctl --version bluetoothctl: 5.64 root@bill:~# hciconfig -a hci0: Type: Primary Bus: USB BD Address: BC:C7:46:9D:25:98 ACL MTU: 1021:8 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:11627 acl:0 sco:0 events:466 errors:0 TX bytes:78563 acl:0 sco:0 commands:422 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'bill' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: (0xc) Revision: 0x40d LMP Version: (0xc) Subversion: 0x7225 Manufacturer: Realtek Semiconductor Corporation (93) root@bill:~# bluetoothctl Agent registered [CHG] Controller BC:C7:46:9D:25:98 Pairable: yes [bluetooth]# show Controller BC:C7:46:9D:25:98 (public) Name: bill Alias: bill Class: 0x007c0104 Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control (110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Audio Sink (110b--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer (1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0540 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x0a (10) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded [bluetooth]# devices Device 74:45:CE:BA:24:65 WH-CH710N At this point I started the earbuds (T60) having a problem getting set up. [CHG] Controller BC:C7:46:9D:25:98 Discoverable: yes [CHG] Controller BC:C7:46:9D:25:98 Discovering: yes [NEW] Device 34:95:04:4B:07:3C 34-95-04-4B-07-3C [CHG] Device 34:95:04:4B:07:3C RSSI: -86 [NEW] Device 0B:20:24:A3:E7:56 T60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -52 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: no [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -64 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: no [CHG] Device 0B:20:24:A3:E7:56 RSSI: -50 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -50 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -80 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -46 [bluetooth]# info 0B:20:24:A3:E7:56 Device 0B:20:24:A3:E7:56 (public) Name: T60 Alias: T60 Class: 0x00240404 Icon: audio-headset Paired: no Trusted: no Blocked: no Connected: no LegacyPairing: no ManufacturerData Key: 0x7262 Manufact
[Desktop-packages] [Bug 2058687] Re: [SRU] libreoffice 7.6.6 for mantic
Packaging changes are staged at https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/log/?h=wip/mantic-7.6 ** Description changed: [Impact] * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release - * Version 7.6.5 is currently released in mantic. For a list of fixed bugs compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 (that's a total of ? bugs): + * Version 7.6.5 is currently released in mantic. For a list of fixed bugs compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 (that's a total of 39 bugs): https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs - https://wiki.documentfoundation.org/Releases/7.6.6/RC2#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.6/RC3#List_of_fixed_bugs 7.6.6 RC3 is identical to the 7.6.6 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1898/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15869507/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240323_001335_50e00@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240324_215819_0b108@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240322_202324_f628d@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240322_145135_f3904@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240322_140411_ca6c5@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] - * A minor release with a total of ? bug fixes always carries the + * A minor release with a total of 39 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2058687 Title: [SRU] libreoffice 7.6.6 for mantic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Mantic: In Progress Bug description: [Impact] * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release * Version 7.6.5 is currently released in mantic. For a list of fixed bugs compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 (that's a total of 39 bugs): https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.6/RC3#List_of_fixed_bugs 7.6.6 RC3 is identical to the 7.6.6 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A r
[Desktop-packages] [Bug 2057842] Re: FFe: [MIR] freedp2 -> freerdp3 in main
This bug was fixed in the package gnome-remote-desktop - 46~rc-0ubuntu2
---
gnome-remote-desktop (46~rc-0ubuntu2) noble; urgency=medium
* No-change rebuild for mutter ABI changes on armhf.
-- Matthias Klose Mon, 25 Mar 2024 19:27:18 +0100
** Changed in: gnome-remote-desktop (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2057842
Title:
FFe: [MIR] freedp2 -> freerdp3 in main
Status in freerdp3 package in Ubuntu:
Fix Released
Status in gnome-remote-desktop package in Ubuntu:
Fix Released
Status in remmina package in Ubuntu:
Fix Released
Bug description:
Feature Freeze Exception Request
--
There are only 2 packages in Ubuntu main that use freerdp2: remmina and
gnome-remote-desktop. It is requested to switch both to freerdp3. Therefore
only one version of freerdp will be in main. freerdp2 will be demoted to
universe since many universe packages use it and are not prepared to switch to
freerdp3.
This also requests updating gnome-control-center to fully enable the
features of gnome-remote-desktop 46.
Impact
--
A headline feature of GNOME 46 is support as a Remote Desktop server without
requiring someone to already be logged in locally ("headless" mode). This
feature requires gnome-remote-desktop 46. gnome-remote-desktop 46 requires
freerdp3.
Impact if this does not happen
--
- We would need to patch gnome-control-center to use the older Remote Desktop
panel (or at least hide the new tab for Remote Login)
- We would need to keep using gnome-remote-desktop 45 instead of 46. The
gnome-remote-desktop upstream maintainers would be unhappy with this decision.
gnome-remote-desktop 45 was tested against Mutter 45. Changes in Mutter 46 may
require changes in gnome-remote-desktop for things to work well although a
simple test showed that basic remote desktop seems to work ok with the
mismatch. (See comment #1 from upstream developer.)
Why this did not land sooner
---
It required the packaging of a new source package freerdp3. And we had to do
this sooner than Debian. Sorry too many things to do before Feature Freeze and
this did not make it.
Affected Packages
-
- gnome-remote-desktop 45 -> 46
- gnome-control-center (to update the Remote Desktop settings page)
- remmina 1.4.34 -> 1.4.35 and swap build-depends. Remmina 1.4.34 did not
work with freerdp 3.3 in my testing
- gnome-connections (build-dependency swap): Not required by other changes
and not in Main but makes sense to switch it also
Affected Flavors
Only Ubuntu Desktop and Edubuntu ships gdm3, gnome-control-center,
gnome-remote-desktop. (Cinnamon 23.04 and daily 23.10 also ships
gnome-control-center but this appears to be a bug since they ship
cinnamon-control-center and is likely already fixed in noble-proposed)
Remmina is included in Ubuntu Desktop, Cinnamon, Kylin, and Unity.
gnome-connections has no reverse dependencies or recommends.
Upstream Changes
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/46.rc/NEWS
https://gitlab.com/Remmina/Remmina/-/blob/rel/v1.4.35/CHANGELOG.md
gnome-control-center 46~beta was already in Ubuntu 24.04 LTS before Feature
Freeze. It will be updated to 46.0. The relevant part here is whether we use
the 46~beta version of the Remote Desktop page or the 46.0 version.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.rc/NEWS
Build Logs
--
I have backported GNOME Shell 46 RC and GTK4 4.13 to the Ubuntu Desktop PPA.
The PPA currently has noble-proposed disabled so that it is easily possible to
try this set of packages without dealing with the incomplete 32-bit time
transition in noble-proposed. In addition, the PPA has the affected packages
from this FFe.
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+packages
Testing Done
---
1. From Ubuntu 23.10 client using Remmina, I was successfully able to connect
to Ubuntu 24.04 LTS host using GNOME Shell 46 RC and GNOME Remote Desktop 46
RC. Remote control worked.
2. From Ubuntu 24.04 LTS client with Remmina 1.4.35 built with
freerdp3, I was able to connect to Ubuntu 23.10 host. Remote control
worked.
3. From Ubuntu 24.04 LTS client with GNOME Connections 46 RC built
with freerdp3, I was able to connect to Ubuntu 23.10 host. Remote
control worked.
4. I added a new Remote Login test case to
https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop and
verified that remote login worked. Notably, enabling this changes the
port for the older service, now called "Desktop Sharing" to 3390.
Since 3389 is the default port, users would then need to manually
specific port 3390 for Desktop Sharing in their
[Desktop-packages] [Bug 2059412] [NEW] SyntaxWarning: invalid escape sequence '\.'
Public bug reported:
Installing software-properties gives
--->
/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197:
SyntaxWarning: invalid escape sequence '\.'
elif
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
uri) == None:
<---
Marked as "wishlist" importance because Python still passes that to
re.match as '\.' instead of '.', so the behavior is correct, as can be
confirmed with
--->
% python3 -c 'print("\.")'
:1: SyntaxWarning: invalid escape sequence '\.'
\.
<---
** Affects: software-properties (Ubuntu)
Importance: Wishlist
Assignee: Nathan Teodosio (nteodosio)
Status: Triaged
** Description changed:
Installing software-properties gives
--->
/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197:
SyntaxWarning: invalid escape sequence '\.'
- elif
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
uri) == None:
+ elif
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
uri) == None:
<---
+
+ Marked as "wishlist" importance because Python still passes that to
+ re.match as '\.' instead of '.', so the behavior is correct, as can be
+ confirmed with
+
+ --->
+ % python3 -c 'print("\.")'
+ :1: SyntaxWarning: invalid escape sequence '\.'
+ \.
+ <---
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/2059412
Title:
SyntaxWarning: invalid escape sequence '\.'
Status in software-properties package in Ubuntu:
Triaged
Bug description:
Installing software-properties gives
--->
/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197:
SyntaxWarning: invalid escape sequence '\.'
elif
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
uri) == None:
<---
Marked as "wishlist" importance because Python still passes that to
re.match as '\.' instead of '.', so the behavior is correct, as can be
confirmed with
--->
% python3 -c 'print("\.")'
:1: SyntaxWarning: invalid escape sequence '\.'
\.
<---
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2059412/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
The content in the pulseaudio.log (#9) is not helpful. Could you edit /usr/lib/systemd/user/pulseaudio.service: change the line "ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal" to "ExecStart=/usr/bin/pulseaudio - --daemonize=no --log-target=file:/home/$user/pulse.txt" reboot connect your bt headset and try to change profile from A2DP to HSP/HFP, then upload the pulse.txt. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. 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 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.27.1:bd10/03/2023:br1.27:svnDellInc.:pnVostro3400:pvr:rvnDellInc.:rn0GGCMJ:rvrA02:cvnDellInc.:ct10:cvr:sku0A23: dmi.product.family: Vostro dmi.product.name: Vostro 3400 dmi.product.sku: 0A23 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-01-28T08:52:28.427855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 2058847] Re: budgie-wm crashes immediately when mutter-common has been upgraded to version 46.0
** Also affects: magpie (Ubuntu) Importance: Undecided Status: New ** No longer affects: budgie-desktop (Ubuntu) ** Changed in: magpie (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2058847 Title: budgie-wm crashes immediately when mutter-common has been upgraded to version 46.0 Status in magpie package in Ubuntu: Triaged Status in mutter package in Ubuntu: New Bug description: mutter-common 46.0 packages remove the org.gnome.mutter.x11 gconf schema. This causes budgie-wm to crash immediately on login. Downgrading to 45.3 fixes everything. $ apt policy mutter-common mutter-common: Installed: 45.3-1ubuntu1 Candidate: 46.0-1ubuntu1 Version table: 46.0-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main i386 Packages *** 45.3-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu noble/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu noble/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: budgie-core 10.9.1-3ubuntu1 Uname: Linux 6.8.1-060801-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Sun Mar 24 16:00:24 2024 InstallationDate: Installed on 2022-03-19 (736 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: budgie-desktop UpgradeStatus: Upgraded to noble on 2023-11-03 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magpie/+bug/2058847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047256] Re: Ubuntu 24.04 Some image thumbnails no longer displayed
The fix was in the apparmor package and not nautilus and that is included in your updates list indeed, the fixed version finally migrated out of the proposed pocket ** Changed in: nautilus (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2047256 Title: Ubuntu 24.04 Some image thumbnails no longer displayed Status in nautilus package in Ubuntu: Fix Released Bug description: After recent updates on my Ubuntu Noble 24.04 nautilus does not show thumbnails of PDF and other image files. On a different partition same PC Ubuntu Noble 24.04 not recently updated image thumbnails are correctly displayed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 22 16:15:59 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(879, 943)' InstallationDate: Installed on 2023-12-10 (12 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.1-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 nautilus-image-converter 0.4.0-2 nautilus-share0.7.5-0.3 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2047256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047256] Re: Ubuntu 24.04 Some image thumbnails no longer displayed
Nautilus not changed but problem disappeared after last updates Start-Date: 2024-03-28 07:54:04 Commandline: apt upgrade Requested-By: corrado (1000) Upgrade: dpkg:amd64 (1.22.4ubuntu5, 1.22.6ubuntu5), libpam-runtime:amd64 (1.5.2-9.1ubuntu3, 1.5.3-5ubuntu3), python3-distupgrade:amd64 (1:24.04.7, 1:24.04.9), tcl:amd64 (8.6.13, 8.6.14), ubuntu-release-upgrader-gtk:amd64 (1:24.04.7, 1:24.04.9), apparmor:amd64 (4.0.0~alpha4-0ubuntu1, 4.0.0-beta3-0ubuntu2), python3-typing-extensions:amd64 (4.9.0-1, 4.10.0-1), libtiff6:amd64 (4.5.1+git230720-3ubuntu1, 4.5.1+git230720-4ubuntu1), software-properties-common:amd64 (0.99.42, 0.99.44), libtcl8.6:amd64 (8.6.13+dfsg-2, 8.6.14+dfsg-1), libapparmor1:amd64 (4.0.0~alpha4-0ubuntu1, 4.0.0-beta3-0ubuntu2), python3-software-properties:amd64 (0.99.42, 0.99.44), libxml2:amd64 (2.9.14+dfsg-1.3ubuntu1, 2.9.14+dfsg-1.3ubuntu2), python3-pkg-resources:amd64 (68.1.2-2, 68.1.2-2ubuntu1), libpam-modules:amd64 (1.5.2-9.1ubuntu3, 1.5.3-5ubuntu3), python3-cairo:amd64 (1.25.1-2, 1.25.1-2build1), python3-click:amd64 (8.1.6-1, 8.1.6-2), libcap-ng0:amd64 (0.8.4-2, 0.8.4-2build1), dmsetup:amd64 (2:1.02.185-3ubuntu1, 2:1.02.185-3ubuntu2), software-properties-gtk:amd64 (0.99.42, 0.99.44), tcl8.6:amd64 (8.6.13+dfsg-2, 8.6.14+dfsg-1), snapd:amd64 (2.60.4+23.10, 2.61.3+24.04), libpam-modules-bin:amd64 (1.5.2-9.1ubuntu3, 1.5.3-5ubuntu3), python3-yaml:amd64 (6.0.1-2, 6.0.1-2build1), python3-brotli:amd64 (1.1.0-2, 1.1.0-2build1), libpam0g:amd64 (1.5.2-9.1ubuntu3, 1.5.3-5ubuntu3), libbrotli1:amd64 (1.1.0-2, 1.1.0-2build1), ubuntu-release-upgrader-core:amd64 (1:24.04.7, 1:24.04.9), libdevmapper1.02.1:amd64 (2:1.02.185-3ubuntu1, 2:1.02.185-3ubuntu2) End-Date: 2024-03-28 07:54:33 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2047256 Title: Ubuntu 24.04 Some image thumbnails no longer displayed Status in nautilus package in Ubuntu: Fix Committed Bug description: After recent updates on my Ubuntu Noble 24.04 nautilus does not show thumbnails of PDF and other image files. On a different partition same PC Ubuntu Noble 24.04 not recently updated image thumbnails are correctly displayed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 22 16:15:59 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(879, 943)' InstallationDate: Installed on 2023-12-10 (12 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.1-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 nautilus-image-converter 0.4.0-2 nautilus-share0.7.5-0.3 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2047256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916301] Re: I can't play live videos on YouTube (problem with live transmission) - Ubuntu 18.04.5
To troubleshoot the issue with playing live YouTube videos on Firefox in
Ubuntu, follow these steps:
Firstly, ensure that your Firefox browser is up to date by updating it
to the latest version available. You can do this through the browser's
settings or by using the package manager in Ubuntu.
Next, temporarily disable any browser extensions or add-ons you have
installed in Firefox. Sometimes, these extensions can interfere with
video playback.
Clear the cache in Firefox to remove any potentially corrupted or
outdated data that might be causing playback issues. This can be done
through the browser's settings under Privacy & Security.
Check if Media Source Extensions (MSE) are enabled in Firefox settings.
MSE is necessary for HTML5 video playback. You can access these settings
by typing "about:config" in the address bar and ensuring that
"media.mediasource.enabled" is set to true.
Install multimedia codecs on your system if they are missing. Use the
command sudo apt install ubuntu-restricted-extras to install the
necessary codecs for multimedia playback.
Disable hardware acceleration in Firefox settings to see if it resolves
the issue. Sometimes, hardware acceleration can cause compatibility
issues with certain videos.
If the problem persists, try playing the live videos in a different
browser like Google Chrome to see if the issue is specific to Firefox.
Check your system's audio settings to ensure that they are configured
correctly and that audio devices are properly recognized.
Make sure your system is up to date by running sudo apt update followed
by sudo apt upgrade to update all system packages.
If none of the above steps work, consider reinstalling Firefox. Use the
commands sudo apt purge firefox followed by sudo apt install firefox to
remove and reinstall Firefox on your system.
By following these steps by https://luadist.org/youtubers-life-2/, you
can systematically troubleshoot and potentially resolve the issue with
playing live YouTube videos on Firefox in Ubuntu.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1916301
Title:
I can't play live videos on YouTube (problem with live transmission) -
Ubuntu 18.04.5
Status in firefox package in Ubuntu:
Invalid
Bug description:
Dear Launchpad Team,
I can't play live videos from Youtube. I have problem only with live
transmission. Normal videos works fine. I noticed that I also have
this same problem on Focal (now I checked this on Bionic - Ubuntu
18.04.5). On Lubuntu 18.04.5 on other machine I don't have this
problem. I can play on Lubuntu all Youtube videos. What is a problem?
Do you know? I think that by default Ubuntu have not necessary package
to play live videos on Youtube. Have I right or this is a bug? On
Answers section on launchpad anyone can't tell me if it is a bug so
this is why I report this bug now. If it is not a bug I am very sorry
and you can delete this report now.
Example I have problem with this video:
https://www.youtube.com/watch?v=21X5lGlDOfg
I used debugger by youtube and this is output of this:
"debug_error": {
"errorCode": "html5.unsupportedlive",
"errorMessage": "Ten format wideo nie jest obsługiwany.",
"Nx": "HTML5_NO_AVAILABLE_FORMATS_FALLBACK",
"cj": "","
If it is a bug can you fix it?
UPDATE: Today I updated my firefox to the newest version 86.0. This
bug still exists.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916301/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991545] Re: Domain groups not accepted as 'AdminIdentities'
After revisiting this, I found the issue was on my side. Our LDAP wasn't returning the members list for groups when queried so polkit wasn't able to authorise those users. I fixed this in our sssd.conf using the 'ignore_group_members = false' option. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1991545 Title: Domain groups not accepted as 'AdminIdentities' Status in policykit-1 package in Ubuntu: New Bug description: Domain groups cannot be configured as 'AdminIdentities' under /etc/polkit-1/localauthority.conf.d EXAMPLE CONFIG # /etc/polkit-1/localauthority.conf.d/90-test.conf [Configuration] AdminIdentities=unix-group:sysapp With the above config, 'sysapp' is a group in LDAP. SSSD is configured on the machine to allow domain users to log in. Sudo rules have been configured for the 'sysapp' group and work correctly. However, any action that creates a polkit/GUI prompt for authentication does not allow users in the 'sysapp' group to authenticate. Instead, it only accepts auth from the root user. If I change the config to use a local group, instead of a domain group, everything works as expected. Similarly if I specify a domain USER instead of a domain group, everything works as expected. The problem seems to only be with domain/LDAP groups. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: policykit-1 0.105-33 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 3 15:20:36 2022 InstallationDate: Installed on 2022-07-15 (80 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: policykit-1 UpgradeStatus: Upgraded to jammy on 2022-08-02 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1991545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059401] [NEW] No sound from Jabra 510 speaker after upgrade to 23.10
Public bug reported:
My Jabra 510 speaker used to work in older releases of Ubuntu but, since
upgrade to 23.10 and switch to pipewire, only the microphone works. If
I select the speaker output in settings or directly in Zoom I hear
nothing.
I found an upstream issue here:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1984. Some
users report that pipewire master fixes the issue.
I tried creating a file /etc/pipewire/pipewire.conf and adding the
configuration from that ticket:
context.properties = {
default.clock.quantum = 2048
default.clock.min-quantum = 1024
default.clock.max-quantum = 4096
}
The Jabra speaker then started working in Zoom but the Ubuntu settings app
showed no devices at all. I'm guessing that the quantum setting worked around
the bug but creating the file overrode some other config that Ubuntu is relying
on. It's not clear how to configure pipewire on ubuntu, upstream seems to use
a different file layout.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: pipewire 0.3.79-2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 28 09:23:03 2024
InstallationDate: Installed on 2018-12-11 (1934 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: pipewire
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: pipewire
Importance: Unknown
Status: Unknown
** Affects: pipewire (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #1984
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1984
** Also affects: pipewire via
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1984
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pipewire in Ubuntu.
https://bugs.launchpad.net/bugs/2059401
Title:
No sound from Jabra 510 speaker after upgrade to 23.10
Status in PipeWire:
Unknown
Status in pipewire package in Ubuntu:
New
Bug description:
My Jabra 510 speaker used to work in older releases of Ubuntu but,
since upgrade to 23.10 and switch to pipewire, only the microphone
works. If I select the speaker output in settings or directly in Zoom
I hear nothing.
I found an upstream issue here:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1984. Some
users report that pipewire master fixes the issue.
I tried creating a file /etc/pipewire/pipewire.conf and adding the
configuration from that ticket:
context.properties = {
default.clock.quantum = 2048
default.clock.min-quantum = 1024
default.clock.max-quantum = 4096
}
The Jabra speaker then started working in Zoom but the Ubuntu settings app
showed no devices at all. I'm guessing that the quantum setting worked around
the bug but creating the file overrode some other config that Ubuntu is relying
on. It's not clear how to configure pipewire on ubuntu, upstream seems to use
a different file layout.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: pipewire 0.3.79-2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 28 09:23:03 2024
InstallationDate: Installed on 2018-12-11 (1934 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
SourcePackage: pipewire
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/pipewire/+bug/2059401/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2032992] Re: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript
The fix is in Snapd beta and should be in stable in the next month or so. ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Released ** Changed in: firefox (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2032992 Title: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript Status in Mozilla Firefox: Fix Released Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1) Install chromium snap snap install chromium 2) Install openjdk-21 documentation sudo apt install openjdk-21-doc 3) Browse API documentation chromium /usr/share/doc/openjdk-21-doc/api/index.html The search bar is inactive and dev console contains: jquery-3.6.1.min.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND $ls -l /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js lrwxrwxrwx 1 root root 43 Mar 17 13:31 /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js -> ../../../../javascript/jquery/jquery.min.js cat /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js prints the file contents Downloaded version of chrome opens documentation with active search bar and no javascript errors /tmp/chrome/chrome /usr/share/doc/openjdk-21-doc/api/index.html Expected results: Chromium snap should be able to follow symlink into /usr/share/javascript and correctly load OpenJDK API documentation. Note: this probably should be a specific exclusion for Debian-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/2032992/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2050884] Re: Ubuntu Metrics server is not accepting reports
https://salsa.debian.org/gnome-team/gnome-initial- setup/-/merge_requests/23 ** Changed in: gnome-initial-setup (Ubuntu) Status: Triaged => In Progress ** Changed in: gnome-initial-setup (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2050884 Title: Ubuntu Metrics server is not accepting reports Status in gnome-initial-setup package in Ubuntu: In Progress Status in ubuntu-report package in Ubuntu: Triaged Bug description: gnome-initial-setup now prompts to send a report immediately, and when it does, it fails, I'll attach a screenshot in the comments. Even when I clicked "Don't send to ubuntu" or however it's phrased, I still encountered the error message pop up in the comments. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-initial-setup 46~alpha-2ubuntu1 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 CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 10:38:31 2024 InstallationDate: Installed on 2024-01-23 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2050884/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 966390] Re: PPTP in NetworkManager dont load ip_gre MPPE required kernel module.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager-pptp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/966390 Title: PPTP in NetworkManager dont load ip_gre MPPE required kernel module. Status in network-manager-pptp package in Ubuntu: Confirmed Bug description: When attempt to start a VPN with MPPE, it dont complete the process. Log before loading ip_gre: Mar 27 13:40:42 scrat NetworkManager[1398]: Starting VPN service 'pptp'... Mar 27 13:40:42 scrat NetworkManager[1398]: VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 4210 Mar 27 13:40:42 scrat NetworkManager[1398]: VPN service 'pptp' appeared; activating connections Mar 27 13:40:42 scrat NetworkManager[1398]: VPN plugin state changed: starting (3) Mar 27 13:40:42 scrat NetworkManager[1398]: VPN connection 'Comjota::Versa' (Connect) reply received. Mar 27 13:40:42 scrat pppd[4214]: Plugin /usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded. Mar 27 13:40:42 scrat pppd[4214]: pppd 2.4.5 started by root, uid 0 Mar 27 13:40:42 scrat pppd[4214]: Using interface ppp0 Mar 27 13:40:42 scrat pppd[4214]: Connect: ppp0 <--> /dev/pts/2 Mar 27 13:40:42 scrat pptp[4217]: nm-pptp-service-4210 log[main:pptp.c:314]: The synchronous pptp option is NOT activated Mar 27 13:40:42 scrat NetworkManager[1398]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Mar 27 13:40:42 scrat NetworkManager[1398]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Mar 27 13:40:42 scrat pptp[4232]: nm-pptp-service-4210 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request' Mar 27 13:40:42 scrat pptp[4232]: nm-pptp-service-4210 log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply Mar 27 13:40:42 scrat pptp[4232]: nm-pptp-service-4210 log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established. Mar 27 13:40:43 scrat pptp[4232]: nm-pptp-service-4210 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request' Mar 27 13:40:43 scrat pptp[4232]: nm-pptp-service-4210 log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply. Mar 27 13:40:43 scrat pptp[4232]: nm-pptp-service-4210 log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 768). Mar 27 13:40:46 scrat pppd[4214]: CHAP authentication succeeded Mar 27 13:40:46 scrat kernel: [ 629.733299] PPP MPPE Compression module registered Mar 27 13:40:49 scrat pppd[4214]: LCP terminated by peer (MPPE disabled) Mar 27 13:40:50 scrat pptp[4232]: nm-pptp-service-4210 log[pptp_read_some:pptp_ctrl.c:544]: read returned zero, peer has closed Mar 27 13:40:50 scrat pptp[4232]: nm-pptp-service-4210 log[callmgr_main:pptp_callmgr.c:258]: Closing connection (shutdown) Mar 27 13:40:50 scrat pptp[4232]: nm-pptp-service-4210 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 'Call-Clear-Request' Mar 27 13:40:50 scrat pptp[4232]: nm-pptp-service-4210 log[pptp_read_some:pptp_ctrl.c:544]: read returned zero, peer has closed Mar 27 13:40:50 scrat pptp[4232]: nm-pptp-service-4210 log[call_callback:pptp_callmgr.c:79]: Closing connection (call state) Mar 27 13:40:50 scrat pppd[4214]: Modem hangup Mar 27 13:40:50 scrat pppd[4214]: Connection terminated. Mar 27 13:40:50 scrat avahi-daemon[1361]: Withdrawing workstation service for ppp0. Mar 27 13:40:50 scrat NetworkManager[1398]: VPN plugin failed: 1 Mar 27 13:40:50 scrat NetworkManager[1398]:SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Mar 27 13:40:50 scrat pppd[4214]: Exit. After loading ip_gre: Mar 27 13:52:09 scrat NetworkManager[1398]: Starting VPN service 'pptp'... Mar 27 13:52:09 scrat NetworkManager[1398]: VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 5890 Mar 27 13:52:09 scrat NetworkManager[1398]: VPN service 'pptp' appeared; activating connections Mar 27 13:52:09 scrat NetworkManager[1398]: VPN plugin state changed: init (1) Mar 27 13:52:09 scrat NetworkManager[1398]: VPN plugin state changed: starting (3) Mar 27 13:52:09 scrat NetworkManager[1398]: VPN connection 'Comjota::Versa' (Connect) reply received. Mar 27 13:52:09 scrat pppd[5894]: Plugin /usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded. Mar 27 13:52:09 scrat pppd[5894]: pppd 2.4.5 started by root, uid 0 Mar 27 13:52:09 scrat pppd[5894]: Using interface ppp0 Mar 27 13:52:09 scrat pppd[5894]: Connect: ppp0 <--> /dev/pts/3 Mar 27 13:52:09 scrat pptp[5899]: nm-pptp-service-5890 log[main:pptp.c:314]: The synchronous pptp option is NOT activated Mar 27 13:52:09 scrat Netwo
[Desktop-packages] [Bug 2057842] Re: FFe: [MIR] freedp2 -> freerdp3 in main
This bug was fixed in the package remmina - 1.4.35+dfsg-0ubuntu2
---
remmina (1.4.35+dfsg-0ubuntu2) noble; urgency=medium
* No-change rebuild against libcups2t64
-- Michael Hudson-Doyle Wed, 20 Mar 2024
13:56:31 +1300
** Changed in: remmina (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2057842
Title:
FFe: [MIR] freedp2 -> freerdp3 in main
Status in freerdp3 package in Ubuntu:
Fix Released
Status in gnome-remote-desktop package in Ubuntu:
Fix Committed
Status in remmina package in Ubuntu:
Fix Released
Bug description:
Feature Freeze Exception Request
--
There are only 2 packages in Ubuntu main that use freerdp2: remmina and
gnome-remote-desktop. It is requested to switch both to freerdp3. Therefore
only one version of freerdp will be in main. freerdp2 will be demoted to
universe since many universe packages use it and are not prepared to switch to
freerdp3.
This also requests updating gnome-control-center to fully enable the
features of gnome-remote-desktop 46.
Impact
--
A headline feature of GNOME 46 is support as a Remote Desktop server without
requiring someone to already be logged in locally ("headless" mode). This
feature requires gnome-remote-desktop 46. gnome-remote-desktop 46 requires
freerdp3.
Impact if this does not happen
--
- We would need to patch gnome-control-center to use the older Remote Desktop
panel (or at least hide the new tab for Remote Login)
- We would need to keep using gnome-remote-desktop 45 instead of 46. The
gnome-remote-desktop upstream maintainers would be unhappy with this decision.
gnome-remote-desktop 45 was tested against Mutter 45. Changes in Mutter 46 may
require changes in gnome-remote-desktop for things to work well although a
simple test showed that basic remote desktop seems to work ok with the
mismatch. (See comment #1 from upstream developer.)
Why this did not land sooner
---
It required the packaging of a new source package freerdp3. And we had to do
this sooner than Debian. Sorry too many things to do before Feature Freeze and
this did not make it.
Affected Packages
-
- gnome-remote-desktop 45 -> 46
- gnome-control-center (to update the Remote Desktop settings page)
- remmina 1.4.34 -> 1.4.35 and swap build-depends. Remmina 1.4.34 did not
work with freerdp 3.3 in my testing
- gnome-connections (build-dependency swap): Not required by other changes
and not in Main but makes sense to switch it also
Affected Flavors
Only Ubuntu Desktop and Edubuntu ships gdm3, gnome-control-center,
gnome-remote-desktop. (Cinnamon 23.04 and daily 23.10 also ships
gnome-control-center but this appears to be a bug since they ship
cinnamon-control-center and is likely already fixed in noble-proposed)
Remmina is included in Ubuntu Desktop, Cinnamon, Kylin, and Unity.
gnome-connections has no reverse dependencies or recommends.
Upstream Changes
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/46.rc/NEWS
https://gitlab.com/Remmina/Remmina/-/blob/rel/v1.4.35/CHANGELOG.md
gnome-control-center 46~beta was already in Ubuntu 24.04 LTS before Feature
Freeze. It will be updated to 46.0. The relevant part here is whether we use
the 46~beta version of the Remote Desktop page or the 46.0 version.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.rc/NEWS
Build Logs
--
I have backported GNOME Shell 46 RC and GTK4 4.13 to the Ubuntu Desktop PPA.
The PPA currently has noble-proposed disabled so that it is easily possible to
try this set of packages without dealing with the incomplete 32-bit time
transition in noble-proposed. In addition, the PPA has the affected packages
from this FFe.
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+packages
Testing Done
---
1. From Ubuntu 23.10 client using Remmina, I was successfully able to connect
to Ubuntu 24.04 LTS host using GNOME Shell 46 RC and GNOME Remote Desktop 46
RC. Remote control worked.
2. From Ubuntu 24.04 LTS client with Remmina 1.4.35 built with
freerdp3, I was able to connect to Ubuntu 23.10 host. Remote control
worked.
3. From Ubuntu 24.04 LTS client with GNOME Connections 46 RC built
with freerdp3, I was able to connect to Ubuntu 23.10 host. Remote
control worked.
4. I added a new Remote Login test case to
https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop and
verified that remote login worked. Notably, enabling this changes the
port for the older service, now called "Desktop Sharing" to 3390.
Since 3389 is the default port, users would then need to manually
specific port 3390 for Desktop Sharing in their remote connection app
(Remmina
[Desktop-packages] [Bug 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x
This bug was fixed in the package netplan.io - 1.0-1
---
netplan.io (1.0-1) unstable; urgency=medium
* New upstream release 1.0:
- state/status: add support for identifying bridge/bond/vrf members !420
- Netplan status --diff !440
- Netplan state diff !386
- allow COMMON_LINK_HANDLERS for VRFs (LP: #2031421, Closes: #1049432) !401
- netplan: add support for WPA3-Enterprise (LP: #2029876) !402
- wifi: support WPA2 and WPA3 Personal simultaneously !404
- auth: add support for LEAP and EAP-PWD (LP: #2038811) !415
- wifi: allow to have a psk and an eap password simultaneously !416
- Migrate CriticalConnection to KeepConfiguration (LP: #1896799) !424
- apply: bring "lo" back up if it's managed by NM (LP: # 2034595) !408
- Post 0.107 cleanup & dropping API/ABI compat !400
- ABI: Refactoring for libnetplan.so.1 !434
- Add additional bridge port settings !410
- SR-IOV improvements (VF-LAG support) !439
Documentation:
- Add spelling checking to the CI !417
- doc: libnetplan API reference, using Doxygen and Sphinx.breathe !423
- doc: Update 'Netplan everywhere' for 23.10 !418
- added mii-monitor-interval !411
- Adopt Docs Starter Pack !429
- Fix howto docs !430
- docs: add a topic about security !433
- Document and restructure libnetplan's public API symbols !438
- Lang. & formatting fixes in API docs. !441
- Update examples.md !442
Bug fixes:
- GitHub CI fixes !405
- util: don't return a placeholder netdef in the iterator !406
- tunnels/validation: do not error out if "local" is not defined !407
- cli/sriov: remove unused code !435
- wireguard: ignore empty endpoints (LP: #2038811) !414
- parse: improve the parsing of access-points (LP: #1809994) !413
- tests: Add autopkgtest for LP: #1959570 !419
- Fix permissions on folder '/run/NetworkManager/' !422
- parse-nm/wg: append the correct prefix to IPv6 (LP: #2046158) !428
- disable StartLimitBurst in the ovs-cleanup service (LP: #2047827) !431
- ctests: stop including C files in the test files !432
- workflow/coverity: install missing dependencies !436
- state_diff: fix filtering of host scoped routes !426
- sriov: don't generate duplicate entries in the rebind.service file !437
- check if ovsdb-server.service is active before displaying warning !421
- parser: accept the special MAC address options (LP: #2045096) !427
- CI: fix NetworkManager autopkgtest not using deb822 !443
- tests: Be less strict about systemctl daemon-reload (LP: #2048388)
- Netplan status --diff refactoring !444
* d/netplan-generator.install: Fix PLACEHOLDER location
* d/netplan-generator.lintian-overrides: Clean up unused override
* d/source/options: Ignore .envrc (direnv)
* d/control: pkg-config -> pkgconf
* d/rules: Make use of -Dpython.bytecompile=-1
* d/control: Update short description
* d/control,d/libnetplan1.symbols: Prepare for libnetplan1 SOVER bump
* d/control: Add iproute2 build-dep (for running tests)
* d/rules: Drop removal of legacy symlink (integrated in meson)
* d/t/control: execute netplan diff test cases
* d/patches: Drop patches, applied upstream
* d/t/control: Mark new 'diff' autopkgtest as flaky
-- Lukas Märdian Thu, 29 Feb 2024 11:51:50 +0100
** Changed in: netplan.io (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2048388
Title:
Test suite often fails with "systemd units changed without reload" on
s390x
Status in Netplan:
Invalid
Status in netplan.io package in Ubuntu:
Fix Released
Status in wpa package in Ubuntu:
New
Bug description:
The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
often fails with
AssertionError: systemd units changed without reload
Looking at the history of autopkgtest runs, it looks like that the
error does not always occur during execution of a specific test. I've
seen occurrences of this error during the following test-cases:
test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL
Example [1]:
781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
781s --
781s Traceback (most recent call last):
781s File
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line
189, in test_dhcp6
781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
781s File
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in
generate_and_settle
781s self.fail('systemd units changed without reload')
781s AssertionError: systemd units changed without reload
[
[Desktop-packages] [Bug 2045096] Re: Error in network definition: Invalid MAC address 'random'
This bug was fixed in the package netplan.io - 1.0-1 --- netplan.io (1.0-1) unstable; urgency=medium * New upstream release 1.0: - state/status: add support for identifying bridge/bond/vrf members !420 - Netplan status --diff !440 - Netplan state diff !386 - allow COMMON_LINK_HANDLERS for VRFs (LP: #2031421, Closes: #1049432) !401 - netplan: add support for WPA3-Enterprise (LP: #2029876) !402 - wifi: support WPA2 and WPA3 Personal simultaneously !404 - auth: add support for LEAP and EAP-PWD (LP: #2038811) !415 - wifi: allow to have a psk and an eap password simultaneously !416 - Migrate CriticalConnection to KeepConfiguration (LP: #1896799) !424 - apply: bring "lo" back up if it's managed by NM (LP: # 2034595) !408 - Post 0.107 cleanup & dropping API/ABI compat !400 - ABI: Refactoring for libnetplan.so.1 !434 - Add additional bridge port settings !410 - SR-IOV improvements (VF-LAG support) !439 Documentation: - Add spelling checking to the CI !417 - doc: libnetplan API reference, using Doxygen and Sphinx.breathe !423 - doc: Update 'Netplan everywhere' for 23.10 !418 - added mii-monitor-interval !411 - Adopt Docs Starter Pack !429 - Fix howto docs !430 - docs: add a topic about security !433 - Document and restructure libnetplan's public API symbols !438 - Lang. & formatting fixes in API docs. !441 - Update examples.md !442 Bug fixes: - GitHub CI fixes !405 - util: don't return a placeholder netdef in the iterator !406 - tunnels/validation: do not error out if "local" is not defined !407 - cli/sriov: remove unused code !435 - wireguard: ignore empty endpoints (LP: #2038811) !414 - parse: improve the parsing of access-points (LP: #1809994) !413 - tests: Add autopkgtest for LP: #1959570 !419 - Fix permissions on folder '/run/NetworkManager/' !422 - parse-nm/wg: append the correct prefix to IPv6 (LP: #2046158) !428 - disable StartLimitBurst in the ovs-cleanup service (LP: #2047827) !431 - ctests: stop including C files in the test files !432 - workflow/coverity: install missing dependencies !436 - state_diff: fix filtering of host scoped routes !426 - sriov: don't generate duplicate entries in the rebind.service file !437 - check if ovsdb-server.service is active before displaying warning !421 - parser: accept the special MAC address options (LP: #2045096) !427 - CI: fix NetworkManager autopkgtest not using deb822 !443 - tests: Be less strict about systemctl daemon-reload (LP: #2048388) - Netplan status --diff refactoring !444 * d/netplan-generator.install: Fix PLACEHOLDER location * d/netplan-generator.lintian-overrides: Clean up unused override * d/source/options: Ignore .envrc (direnv) * d/control: pkg-config -> pkgconf * d/rules: Make use of -Dpython.bytecompile=-1 * d/control: Update short description * d/control,d/libnetplan1.symbols: Prepare for libnetplan1 SOVER bump * d/control: Add iproute2 build-dep (for running tests) * d/rules: Drop removal of legacy symlink (integrated in meson) * d/t/control: execute netplan diff test cases * d/patches: Drop patches, applied upstream * d/t/control: Mark new 'diff' autopkgtest as flaky -- Lukas Märdian Thu, 29 Feb 2024 11:51:50 +0100 ** Changed in: netplan.io (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2045096 Title: Error in network definition: Invalid MAC address 'random' Status in Netplan: Fix Committed Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: New Bug description: netplan dose not understand the 'random' key word in 'Cloned MAC address' set by networkmanager. ``` /etc/netplan/90-NM-X.yaml:9:19: Error in network definition: Invalid MAC address 'random', must be XX:XX:XX:XX:XX:XX or XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX macaddress: "random" ^ ``` netplan Version 0.107-5ubuntu2 network-manager Version 1.44.2-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2045096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2029480] Re: SyntaxWarnings with Python3.12
This bug was fixed in the package hplip - 3.23.12+dfsg0-0ubuntu4 --- hplip (3.23.12+dfsg0-0ubuntu4) noble; urgency=medium * Fix FTBFS on armhf due to implicit functions -- Simon Chopin Fri, 22 Mar 2024 15:40:13 +0100 ** Changed in: hplip (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2029480 Title: SyntaxWarnings with Python3.12 Status in HPLIP: Confirmed Status in hplip package in Ubuntu: Fix Released Bug description: Fedora 39 uses Python 3.12 by default, which generates many SyntaxWarnings when running hplip scripts. Most warnings are due regular expressions in strings, so making them raw fixes the issue. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/2029480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054869] Re: Lot of SyntaxWarning messages during install
*** This bug is a duplicate of bug 2029480 ***
https://bugs.launchpad.net/bugs/2029480
This bug was fixed in the package hplip - 3.23.12+dfsg0-0ubuntu4
---
hplip (3.23.12+dfsg0-0ubuntu4) noble; urgency=medium
* Fix FTBFS on armhf due to implicit functions
-- Simon Chopin Fri, 22 Mar 2024 15:40:13 +0100
** Changed in: hplip (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/2054869
Title:
Lot of SyntaxWarning messages during install
Status in HPLIP:
Confirmed
Status in hplip package in Ubuntu:
Fix Released
Bug description:
Ubuntu 24.04 lot of SyntaxWarning messages during install
running python rtupdate hooks for python3.12...
/usr/share/hplip/base/LedmWifi.py:34: SyntaxWarning: invalid escape sequence
'\d'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/device.py:49: SyntaxWarning: invalid escape sequence
'\d'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/g.py:304: SyntaxWarning: invalid escape sequence '\|'
spinner = "\|/-\|/-"
/usr/share/hplip/base/g.py:354: SyntaxWarning: invalid escape sequence '\d'
m = re.search('python(\d(\.\d){0,2})', ext_path)#get the python
version where the .so file is found
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape
sequence '\#'
re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape
sequence '\/'
re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape
sequence '\*'
re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/base/logger.py:439: SyntaxWarning: invalid escape sequence
'\<'
elem_start = re.findall("(\<\W{0,1}\w+) ?", line)[0]
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: hplip 3.22.10+dfsg0-2ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 24 10:31:07 2024
InstallationDate: Installed on 2024-02-20 (4 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240220)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: Gigabyte Technology Co., Ltd. H510M H
Papersize: a4
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.6.0-14-generic
root=UUID=46acaa02-3641-4fce-877b-03fb0f9525e5 ro quiet splash vt.handoff=7
SourcePackage: hplip
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F14
dmi.board.asset.tag: Default string
dmi.board.name: H510M H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF14:bd03/25/2022:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnH510MH:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH510MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: H510 MB
dmi.product.name: H510M H
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/2054869/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8
This bug was fixed in the package privoxy - 3.0.34-3ubuntu1 --- privoxy (3.0.34-3ubuntu1) noble; urgency=medium * debian/apparmor/usr.sbin.privoxy: attempt on fixing the denial on containers (LP: #2058866). -- Łukasz 'sil2100' Zemczak Tue, 26 Mar 2024 17:16:43 +0100 ** Changed in: privoxy (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2058866 Title: proposed-migration for cups-browsed 2.0.0-0ubuntu8 Status in apparmor package in Ubuntu: Invalid Status in cups-browsed package in Ubuntu: Fix Released Status in privoxy package in Ubuntu: Fix Released 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049061] Re: adsysctl update with a domain user fails if KRB5CCNAME is not set
This bug was fixed in the package adsys - 0.14.1
---
adsys (0.14.1) noble; urgency=medium
* Pin Go toolchain to 1.22.1 to fix the following security vulnerabilities:
- GO-2024-2598
- GO-2024-2599
* Update apport hook to include journal errors and package logs
* CI and quality of life changes not impacting package functionality:
- Enable end-to-end tests in GitHub Actions
- Remove stale AD resources on test finish
- Add developer documentation for running end-to-end tests
- Collect and upload end-to-end test logs on failure
- Report test coverage in Cobertura XML format
- Silence gosec warnings using nolint and remove deprecated ifshort linter
- Use an environment variable to update golden files
- Bump github actions to latest:
- azure/login
- softprops/action-gh-release
* Update dependencies to latest:
- github.com/charmbracelet/lipgloss
- github.com/golangci/golangci-lint
- github.com/golang/protobuf
- github.com/stretchr/testify
- golang.org/x/crypto
- golang.org/x/net
- google.golang.org/grpc
- google.golang.org/protobuf
adsys (0.14.0) noble; urgency=medium
* Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061)
- This functionality is opt-in and activated if the detect_cached_ticket
setting is set to true
- If the AD backend (e.g. sssd) doesn't export the KRB5CCNAME variable,
adsys
will now determine the path to the default ticket cache and use it during
authentication (when adsys is executed through the PAM module) and runs of
adsysctl update for the current user.
* Allow sssd backend to work without ad_domain being set (LP: #2054445)
* Upgrade to Go 1.22
* CI and quality of life changes not impacting package functionality:
- Pass token explicitly to Codecov action
- Fix require outside of main goroutine
- Mark function arguments as unused where applicable
Thanks to Edu Gómez Escandell
- End to end test VM template creation updates
- Bump github actions to latest:
- codecov/codecov-action
- peter-evans/create-pull-request
* Update dependencies to latest:
- github.com/charmbracelet/bubbles
- github.com/golangci/golangci-lint
- golang.org/x/crypto
- golang.org/x/net
- google.golang.org/grpc
-- Gabriel Nagy Thu, 21 Mar 2024 12:27:01
+0200
** Changed in: adsys (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2049061
Title:
adsysctl update with a domain user fails if KRB5CCNAME is not set
Status in adsys package in Ubuntu:
Fix Released
Bug description:
In an environment where /etc/krb5.conf sets "default_ccache_name =
FILE:/tmp/krb5cc_%{uid}" and you don't have the KRB5CCNAME variable
set, running "adsysctl update" with a AD domain user will fail.
If you either export the variable with the path to the kerberos ticket
OR run the command "adsysctl update
" it works.
The adsysctl command should fallback to the default location when
KRB5CCNAME is not defined or have a mechanism to query klist and find
the Kerberos tickets location.
Given that adsys can't find Kerberos tickets when `klist` does. It
seems like a feature parity issue, granted, an edge case.
Here is an example of a reproducer:
https://pastebin.ubuntu.com/p/FjyTWQChjM/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: adsys 0.9.2~22.04.2
ProcVersionSignature: Ubuntu 6.2.0-1014.14~22.04.1-aws 6.2.16
Uname: Linux 6.2.0-1014-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: aws
CloudName: aws
CloudPlatform: ec2
CloudRegion: us-west-2
CloudSubPlatform: metadata (http://169.254.169.254)
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 11 11:39:06 2024
Ec2AMI: ami-00094f7041bb1b79d
Ec2AMIManifest: (unknown)
Ec2Architecture: x86_64
Ec2AvailabilityZone: us-west-2b
Ec2Imageid: ami-00094f7041bb1b79d
Ec2InstanceType: t3.large
Ec2Instancetype: t3.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Ec2Region: us-west-2
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
sssd 2.6.3-1ubuntu3.2
python3-samba 2:4.15.13+dfsg-0ubuntu1.5
SourcePackage: adsys
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.polkit-1.localauthority.conf.d.99-adsys-privilege-enforcement.conf:
[deleted]
modified.conffile..etc.sudoers.d.99-adsys-privilege-enforcement: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2049061/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Pos
[Desktop-packages] [Bug 2054445] Re: Regresion in sssd backend configuration
This bug was fixed in the package adsys - 0.14.1 --- adsys (0.14.1) noble; urgency=medium * Pin Go toolchain to 1.22.1 to fix the following security vulnerabilities: - GO-2024-2598 - GO-2024-2599 * Update apport hook to include journal errors and package logs * CI and quality of life changes not impacting package functionality: - Enable end-to-end tests in GitHub Actions - Remove stale AD resources on test finish - Add developer documentation for running end-to-end tests - Collect and upload end-to-end test logs on failure - Report test coverage in Cobertura XML format - Silence gosec warnings using nolint and remove deprecated ifshort linter - Use an environment variable to update golden files - Bump github actions to latest: - azure/login - softprops/action-gh-release * Update dependencies to latest: - github.com/charmbracelet/lipgloss - github.com/golangci/golangci-lint - github.com/golang/protobuf - github.com/stretchr/testify - golang.org/x/crypto - golang.org/x/net - google.golang.org/grpc - google.golang.org/protobuf adsys (0.14.0) noble; urgency=medium * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) - This functionality is opt-in and activated if the detect_cached_ticket setting is set to true - If the AD backend (e.g. sssd) doesn't export the KRB5CCNAME variable, adsys will now determine the path to the default ticket cache and use it during authentication (when adsys is executed through the PAM module) and runs of adsysctl update for the current user. * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Upgrade to Go 1.22 * CI and quality of life changes not impacting package functionality: - Pass token explicitly to Codecov action - Fix require outside of main goroutine - Mark function arguments as unused where applicable Thanks to Edu Gómez Escandell - End to end test VM template creation updates - Bump github actions to latest: - codecov/codecov-action - peter-evans/create-pull-request * Update dependencies to latest: - github.com/charmbracelet/bubbles - github.com/golangci/golangci-lint - golang.org/x/crypto - golang.org/x/net - google.golang.org/grpc -- Gabriel Nagy Thu, 21 Mar 2024 12:27:01 +0200 ** Changed in: adsys (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2054445 Title: Regresion in sssd backend configuration Status in adsys package in Ubuntu: Fix Released Bug description: This is a regression from when we added support for multiple AD backends (see https://github.com/ubuntu/adsys/pull/467) Previously adsys would use the first domain from `sssd.conf` and potentially override it if `ad_domain` is explicitly set for the domain, see: https://github.com/ubuntu/adsys/blob/32a830f2a8204cc8b896094bad512ed619fbf6b7/internal/adsysservice/adsysservice.go#L279-L280 The current implementation raises an error if we are not able to find an `ad_domain` setting in the domain section, even if we already have a domain (`sssdDomain`): https://github.com/ubuntu/adsys/blob/c68d2cc999d25b1cb408a9e31775a76d2af4c8c7/internal/ad/backends/sss/sss.go#L62-L65 Ideally we should set `domain` to `sssdDomain` if we cannot find a value for `ad_domain`, which will mimic the behavior previous to the refactor. While by default joining a domain with `realm join` will set the appropriate configuration values in `sssd.conf` so this doesn't happen, this is a regression we should aim to fix. ### Steps to reproduce it 1. Join an AD domain with sssd (e.g. using `realm join`) 2. Install the latest version of adsys, run `adsysctl update -m -vv`, everything should work 3. Comment out the `ad_domain` line from `/etc/sssd/sssd.conf` 4. `adsysctl update -m -vv` now fails, and the adsysd service does not start anymore 5. (Optional) To confirm the functionality prior to the regression, re-attempt the steps above on Ubuntu 22.04 using the adsys version currently in the archive (0.9.2) -- adsys is able to correctly determine the domain even without the `ad_domain` setting. GitHub issue: https://github.com/ubuntu/adsys/issues/910 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2054445/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
This bug was fixed in the package plymouth - 24.004.60-1ubuntu6 --- plymouth (24.004.60-1ubuntu6) noble; urgency=medium * Cherry-pick upstream fixes for consistent default scale selection that matches what Mutter chooses on the login screen (LP: #2054769) * plymouth.hook: Stop automatically re-installing DRM kernel modules in initrd. initramfs-tools already does this for us in hooks/framebuffer and should be the authority for which drivers to include. * Install a /usr/share/initramfs-tools/conf-hooks.d/plymouth with FRAMEBUFFER=y to make it clear to initramfs-tools that we always want framebuffer support when Plymouth is installed. (LP: #1970069) -- Daniel van Vugt Thu, 21 Mar 2024 14:46:56 +0100 ** Changed in: plymouth (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054769] Re: Boot animation and login screen use different display scales
This bug was fixed in the package plymouth - 24.004.60-1ubuntu6 --- plymouth (24.004.60-1ubuntu6) noble; urgency=medium * Cherry-pick upstream fixes for consistent default scale selection that matches what Mutter chooses on the login screen (LP: #2054769) * plymouth.hook: Stop automatically re-installing DRM kernel modules in initrd. initramfs-tools already does this for us in hooks/framebuffer and should be the authority for which drivers to include. * Install a /usr/share/initramfs-tools/conf-hooks.d/plymouth with FRAMEBUFFER=y to make it clear to initramfs-tools that we always want framebuffer support when Plymouth is installed. (LP: #1970069) -- Daniel van Vugt Thu, 21 Mar 2024 14:46:56 +0100 ** Changed in: plymouth (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054769 Title: Boot animation and login screen use different display scales Status in Plymouth: New Status in mutter package in Ubuntu: Won't Fix Status in plymouth package in Ubuntu: Fix Released Bug description: Boot animation and login screen use different display scales, on some (not many) machines. For example on a Microsoft Surface Laptop 4, Plymouth seems to use scale 2 for the boot screen while GNOME selects scale 1 for the login screen. This means the Ubuntu logo shrinks. I've tried a few laptops and so far it's only the Surface Laptop 4 that has the problem: 13.5" 2256x1504, 201 PPI To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/2054769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2057710] Re: Accountsservice FTBFS on noble
This bug was fixed in the package accountsservice - 23.13.9-2ubuntu4 --- accountsservice (23.13.9-2ubuntu4) noble; urgency=medium * debian/patches/0001-tests-s-assertEquals-assertEqual.patch: Add patch to fix FTBFS with unittest from Python 3.12. (LP: #2057710) -- David Mohammed Tue, 12 Mar 2024 21:51:36 + ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2057710 Title: Accountsservice FTBFS on noble Status in accountsservice package in Ubuntu: Fix Released Bug description: package version 23.13.9-2ubuntu FTBFS on all architectures. This is because of an invalid test This has been resolved upstream - see the attached debdiff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2057710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054851] Re: [radeon] gnome-shell and Xorg both crash with SIGSEGV in radeon_bo_reference()
This bug was fixed in the package mesa - 24.0.3-1ubuntu3 --- mesa (24.0.3-1ubuntu3) noble; urgency=medium * Unwind remaining bootstrap changes. -- Steve Langasek Fri, 22 Mar 2024 18:31:49 + ** Changed in: mesa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2054851 Title: [radeon] gnome-shell and Xorg both crash with SIGSEGV in radeon_bo_reference() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa package in Debian: Fix Released Bug description: Idont know ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Feb 23 10:38:05 2024 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-10-01 (146 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CO.UTF-8 LANGUAGE=es_CO:es PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.3-1ubuntu1 Signal: 11 SignalName: SIGSEGV SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2054851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2057704] Re: jackd2 FTBFS due to waflib incompatible with Python 3.12
This bug was fixed in the package jackd2 - 1.9.21~dfsg-3ubuntu1 --- jackd2 (1.9.21~dfsg-3ubuntu1) noble; urgency=medium * d/p/1002-Update-to-waf-2.0.26.patch: apply an upstream patch to fix Python 3.12 compatibility issues with the waf build system. (LP: #2057704). -- Zixing Liu Tue, 12 Mar 2024 14:45:25 -0600 ** Changed in: jackd2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/2057704 Title: jackd2 FTBFS due to waflib incompatible with Python 3.12 Status in jackd2 package in Ubuntu: Fix Released Bug description: jackd2 is now unbuildable after Python 3.12 due to a very outdated WAF build system inside. The upstream has already fixed the issue in a recent commit, we need to introduce this as a patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2057704/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
This bug was fixed in the package policykit-1 - 124-1ubuntu1 --- policykit-1 (124-1ubuntu1) noble; urgency=medium * polkitd.postinst: call systemd-sysusers with SYSTEMD_NSS_DYNAMIC_BYPASS=1 This works around an upgrade bug in systemd where nss-systemd cannot establish a varlink connection with io.systemd.DynamicUser, hence causing the polkitd user/group creation to fail. (LP: #2054716) -- Nick Rosbrook Wed, 13 Mar 2024 14:15:18 -0400 ** Changed in: policykit-1 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054716 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Bug description: I was working on recreating bug 2054319 and did so by modifying my /etc/apt/sources.list file from jammy to noble and installing polkit and all its dependencies. bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic linux-headers-6.5.0-14-generic linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic linux-modules-extra-6.2.0-36-generic linux-modules-extra-6.5.0-14-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 libzstd1 locales systemd systemd-dev systemd-oomd systemd-resolved systemd-sysv systemd-timesyncd udev Suggested packages: glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container systemd-homed systemd-userdbd systemd-boot libqrencode4 libtss2-rc0 Recommended packages: libnss-nis libnss-nisplus The following NEW packages will be installed: libduktape207 libsystemd-shared systemd-dev systemd-resolved The following packages will be upgraded: gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 libzstd1 locales pkexec policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev 26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded. Need to get 34.9 MB of archives. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Feb 22 08:46:48 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-11-02 (112 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058604] Re: Framework 16 disable touchpad when typing doesn't work
This bug was fixed in the package libinput - 1.25.0-1ubuntu1 --- libinput (1.25.0-1ubuntu1) noble; urgency=medium * Backport a patch from upstream to fix disable touchpad when typing on Framework 16 (LP: #2058604) -- Mario Limonciello Tue, 26 Mar 2024 13:55:28 -0500 ** Changed in: libinput (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2058604 Title: Framework 16 disable touchpad when typing doesn't work Status in libinput package in Ubuntu: Fix Released Bug description: Due to the "input deck" the Framework 16 has a "USB" internal keyboard. This throws off heuristics for detection of keyboards to turn off when you select disable touchpad when typing. This is fixed in upstream libinput with the following change: https://gitlab.freedesktop.org/libinput/libinput/-/commit/566857bd98131009699c9ab6efc7af37afd43fd0 As that's not yet part of a release yet and it's a trivial change, could it be cherry picked for Ubuntu to give a better experience to Framework 16 users? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2058604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059157] Re: proposed-migration for cups 2.4.7-1.2ubuntu1
This bug was fixed in the package cups - 2.4.7-1.2ubuntu2 --- cups (2.4.7-1.2ubuntu2) noble; urgency=low * Remove Debian's own (broken) cups.pc file, CUPS has it upstreanm from 2.4.6 on (LP: #2059157). -- Till Kamppeter Tue, 26 Mar 2024 23:17:19 +0100 ** Changed in: cups (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2059157 Title: proposed-migration for cups 2.4.7-1.2ubuntu1 Status in c2esp package in Ubuntu: New Status in cups package in Ubuntu: Fix Released Bug description: multiple cups-related packages are having test failures on armhf after time_t transition. https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9 I am suspecting a common cups-based issue. cups-browsed already has a separate bug open at https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947315] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_pa
Similar crashes in GNOME 45 and 46 are being tracked in https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7339 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7339 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7339 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1947315 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from st_theme_node_transition_get_paint_box() Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/9e0eb2f488ad83e41a8977709955a661857ba95e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1947315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947315] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_pa
Although zero crashes (of the same stack trace) in releases after Jammy suggests this should stay closed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1947315 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from st_theme_node_transition_get_paint_box() Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/9e0eb2f488ad83e41a8977709955a661857ba95e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1947315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947315] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_pa
There are still hundreds of these crash reports even in 42.9, even this week. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1947315 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from st_theme_node_transition_get_paint_box() Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/9e0eb2f488ad83e41a8977709955a661857ba95e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1947315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
I thought it was worth mentioning that sound does work via the headphone jack on Ubuntu 23.10 and that when using the speaker, audio levels are still detected in system settings. This makes me think all codecs etc are working but that it's a simple toggle somewhere to get the speaker to work rather than it requiring driver updates etc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. 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.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
