[Desktop-packages] [Bug 1969140] Re: Window minimize animation flickers and appears in the wrong place
The bug is still present in Ubuntu 24.04 final release. -- 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/1969140 Title: Window minimize animation flickers and appears in the wrong place Status in Dash to dock: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: Graphical glitches appears while minimizing or maximizing apps in x11 session randomly, screencast below ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1969140/+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 2061977] [NEW] t64 migration: libgtk-3-0t64 has unmet dependencies, blocks >200 packages
Public bug reported: lsb_release -rd No LSB modules are available. Description:Ubuntu Noble Numbat (development branch) Release:24.04 This unresolved dependency seems to be the main t64 migration blocker for the last weeks. I've manually thinned out the dependencies that "apt upgrade" can't solve but the libgtk-3-0t64/libreoffice-core unresolvable dependencies remain as main blocker. This has not changes for at least 2 weeks now. root@kyle:/# apt install vim-tiny Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgtk-3-0t64 : Depends: libcups2 (>= 2.3~b6) Recommends: libgtk-3-bin libreoffice-core : Depends: libcups2t64 (>= 1.7.0) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. root@kyle:/# There are no held packages. root@kyle:/# apt update; apt upgrade Hit:1 http://dl.google.com/linux/earth/deb stable InRelease Hit:2 http://security.ubuntu.com/ubuntu mantic-security InRelease Hit:3 http://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease Hit:4 https://download.tinkerforge.com/apt/ubuntu noble InRelease Hit:5 https://repo.steampowered.com/steam stable InRelease Hit:6 https://updates.signal.org/desktop/apt xenial InRelease Hit:7 https://updates.signal.org/desktop/apt artful InRelease Hit:8 https://mkvtoolnix.download/ubuntu mantic InRelease Hit:9 http://ppa.launchpad.net/yubico/stable/ubuntu kinetic InRelease Hit:10 http://security.ubuntu.com/ubuntu noble-security InRelease Hit:11 https://ppa.launchpadcontent.net/ubuntuhandbook1/handbrake/ubuntu mantic InRelease Hit:12 https://dl.google.com/linux/chrome/deb stable InRelease Hit:13 https://packages.microsoft.com/repos/ms-teams stable InRelease Hit:14 https://ppa.launchpadcontent.net/yubico/stable/ubuntu noble InRelease Hit:15 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/jammy pgadmin4 InRelease Hit:16 http://apt.postgresql.org/pub/repos/apt mantic-pgdg InRelease Hit:17 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/mantic pgadmin4 InRelease Hit:18 http://ppa.launchpad.net/yubico/stable/ubuntu mantic InRelease Hit:19 http://apt.postgresql.org/pub/repos/apt noble-pgdg InRelease Hit:20 http://ppa.launchpad.net/yubico/stable/ubuntu noble InRelease Hit:21 http://archive.ubuntu.com/ubuntu mantic InRelease Hit:22 http://archive.ubuntu.com/ubuntu mantic-updates InRelease Hit:23 http://archive.ubuntu.com/ubuntu mantic-backports InRelease Hit:24 http://archive.ubuntu.com/ubuntu noble InRelease Hit:25 http://archive.ubuntu.com/ubuntu noble-updates InRelease Hit:26 http://archive.ubuntu.com/ubuntu noble-backports InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 210 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: alsa-utils atril coreutils evince gimp gir1.2-gst-plugins-base-1.0 gir1.2-javascriptcoregtk-4.1 gir1.2-webkit2-4.1 gstreamer1.0-gl gstreamer1.0-gtk3 gstreamer1.0-libav gstreamer1.0-plugins-bad gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-pulseaudio gstreamer1.0-vaapi gstreamer1.0-x hexchat hexchat-common hexchat-plugins hexchat-python3 hplip hplip-data hplip-gui imagemagick-6.q16 libatk-wrapper-java-jni libblockdev-nvme3 libfcgi-perl libfido2-1 libfluidsynth3 libglusterfs0 libgssapi-krb5-2 libgssapi-krb5-2:i386 libgstreamer-gl1.0-0 libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libhpmud0 libimage-magick-q16-perl
[Desktop-packages] [Bug 2061364] [NEW] Remote login black screen
Public bug reported: on 24.04 when RDP from a windows client it logs on but most of the gui dosnt load. There is some options for like poweroff /on but the have zero effect. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-remote-desktop 46.0-2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 08:21:06 2024 InstallationDate: Installed on 2024-04-14 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-remote-desktop UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- 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/2061364 Title: Remote login black screen Status in gnome-remote-desktop package in Ubuntu: New Bug description: on 24.04 when RDP from a windows client it logs on but most of the gui dosnt load. There is some options for like poweroff /on but the have zero effect. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-remote-desktop 46.0-2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 08:21:06 2024 InstallationDate: Installed on 2024-04-14 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= 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/2061364/+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 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
Same issue after upgrading from 23.10 on a Lenovo Legion 5 15ARH7H -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble Status in gnome-keyring package in Ubuntu: Triaged Bug description: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+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 1969140] Re: Window minimize animation flickers and appears in the wrong place
Unfortunately the bug is still present in Ubuntu 24.04 beta. Could it be solved, before the final version is 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/1969140 Title: Window minimize animation flickers and appears in the wrong place Status in Dash to dock: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: Graphical glitches appears while minimizing or maximizing apps in x11 session randomly, screencast below ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1969140/+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 2059861] Re: recovery test not possible
Hmm, that's odd. That means... maybe there's a problem decrypting some of your metadata, but you do have an unencrypted version of that metadata in duplicity cache folders...? But if you can restore stuff, that likely means you can decrypt the latest actual data... If you run "DEJA_DUP_DEBUG=1 deja-dup" and reproduce the issue, do you see any interesting output? ** Changed in: deja-dup (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/2059861 Title: recovery test not possible Status in deja-dup package in Ubuntu: Incomplete Bug description: When I'm asked for the password to encrypt, and I type the password and click Next, it briefly loads and the Enter password box appears again. However, the password is correct, because I can restore a backup. Only the test doesn't work. lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 apt-cache policy deja-dup deja-dup: Installiert: 42.9-1ubuntu3 Installationskandidat: 42.9-1ubuntu3 Versionstabelle: *** 42.9-1ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.9-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: deja-dup 42.9-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 31 15:07:23 2024 InstallationDate: Installed on 2023-06-09 (296 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/2059861/+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 2059033] Re: Xorg crashes with SIGABRT
Tried kernel parameter i915.enable_dc=0 as suggested by https://wiki.archlinux.org/title/intel_graphics#Crash.2Ffreeze_on_low_power_Intel_CPUs; still crashes -- 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/2059033 Title: Xorg crashes with SIGABRT Status in Mesa: New Status in mesa package in Ubuntu: New Bug description: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x560c5cc756a0 in OsAbort () at ../../../../os/utils.c:1352 #6 0x560c5cc7aea9 in AbortServer () at ../../../../os/log.c:879 #7 0x560c5cc7be9a in FatalError (f=f@entry=0x560c5ccadc10 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1017 #8 0x560c5cc72abd in OsSigHandler (unused=, sip=0x713ae7b0, signo=6) at ../../../../os/osinit.c:156 #9 OsSigHandler (signo=6, sip=0x713ae7b0, unused=) at ../../../../os/osinit.c:110 #10 #11 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #12 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #13 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #14 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #15 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #16 0x7f72fc49d86d in _iris_batch_flush (batch=0x560c5e916118, file=, line=) at ../src/gallium/drivers/iris/iris_batch.c:1116 #17 0x7f72fd1da6ff in iris_fence_flush (ctx=0x560c5e915be0, out_fence=0x0, flags=) at ../src/gallium/drivers/iris/iris_fence.c:267 #18 0x7f72fc55f127 in st_flush (flags=0, fence=0x0, st=0x560c5e93bbc0) at ../src/mesa/state_tracker/st_cb_flush.c:60 #19 st_glFlush (ctx=, gallium_flush_flags=0) at ../src/mesa/state_tracker/st_cb_flush.c:94 #20 0x7f72fe56b604 in _glamor_block_handler (screen=0x560c5e8655a0, timeout=0x713af054) at ../../../../glamor/glamor.c:285 #21 0x7f72fe5a6157 in msBlockHandler (pScreen=0x560c5e8655a0, timeout=0x713af054) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:701 #22 0x560c5cb01095 in BlockHandler (pTimeout=pTimeout@entry=0x713af054) at ../../../../dix/dixutils.c:394 #23 0x560c5cc6c0c9 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:201 #24 0x560c5cafc3e7 in Dispatch () at ../../../../dix/dispatch.c:492 #25 0x560c5cb006b4 in dix_main (argc=11, argv=0x713af268, envp=) at ../../../../dix/main.c:272 #26 0x7f72fec29d90 in __libc_start_call_main (main=main@entry=0x560c5cae95d0 , argc=argc@entry=11, argv=argv@entry=0x713af268) at ../sysdeps/nptl/libc_start_call_main.h:58 #27 0x7f72fec29e40 in __libc_start_main_impl (main=0x560c5cae95d0 , argc=11, argv=0x713af268, init=, fini=, rtld_fini=, stack_end=0x713af258) at ../csu/libc-start.c:392 #28 0x560c5cae9605 in _start () This post describes a similar issue: https://gitlab.freedesktop.org/drm/intel/-/issues/4858 I tried using a workaround from the above link, to set GPU to max frequency using command "intel_gpu_frequency -m", this seemed to reduce the rate of occurrence from once per day to once every 3 days, but this is not a permanent solution. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2059033/+subscriptions -- Mailing list: https://launchpad.net/~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 2059033] [NEW] Xorg crashes with SIGABRT
Public bug reported: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x560c5cc756a0 in OsAbort () at ../../../../os/utils.c:1352 #6 0x560c5cc7aea9 in AbortServer () at ../../../../os/log.c:879 #7 0x560c5cc7be9a in FatalError (f=f@entry=0x560c5ccadc10 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1017 #8 0x560c5cc72abd in OsSigHandler (unused=, sip=0x713ae7b0, signo=6) at ../../../../os/osinit.c:156 #9 OsSigHandler (signo=6, sip=0x713ae7b0, unused=) at ../../../../os/osinit.c:110 #10 #11 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #12 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #13 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #14 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #15 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #16 0x7f72fc49d86d in _iris_batch_flush (batch=0x560c5e916118, file=, line=) at ../src/gallium/drivers/iris/iris_batch.c:1116 #17 0x7f72fd1da6ff in iris_fence_flush (ctx=0x560c5e915be0, out_fence=0x0, flags=) at ../src/gallium/drivers/iris/iris_fence.c:267 #18 0x7f72fc55f127 in st_flush (flags=0, fence=0x0, st=0x560c5e93bbc0) at ../src/mesa/state_tracker/st_cb_flush.c:60 #19 st_glFlush (ctx=, gallium_flush_flags=0) at ../src/mesa/state_tracker/st_cb_flush.c:94 #20 0x7f72fe56b604 in _glamor_block_handler (screen=0x560c5e8655a0, timeout=0x713af054) at ../../../../glamor/glamor.c:285 #21 0x7f72fe5a6157 in msBlockHandler (pScreen=0x560c5e8655a0, timeout=0x713af054) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:701 #22 0x560c5cb01095 in BlockHandler (pTimeout=pTimeout@entry=0x713af054) at ../../../../dix/dixutils.c:394 #23 0x560c5cc6c0c9 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:201 #24 0x560c5cafc3e7 in Dispatch () at ../../../../dix/dispatch.c:492 #25 0x560c5cb006b4 in dix_main (argc=11, argv=0x713af268, envp=) at ../../../../dix/main.c:272 #26 0x7f72fec29d90 in __libc_start_call_main (main=main@entry=0x560c5cae95d0 , argc=argc@entry=11, argv=argv@entry=0x713af268) at ../sysdeps/nptl/libc_start_call_main.h:58 #27 0x7f72fec29e40 in __libc_start_main_impl (main=0x560c5cae95d0 , argc=11, argv=0x713af268, init=, fini=, rtld_fini=, stack_end=0x713af258) at ../csu/libc-start.c:392 #28 0x560c5cae9605 in _start () This post describes a similar issue: https://gitlab.freedesktop.org/drm/intel/-/issues/4858 I tried using a workaround from the above link, to set GPU to max frequency using command "intel_gpu_frequency -m", this seemed to reduce the rate of occurrence from once per day to once every 3 days, but this is not a permanent solution. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2059033 Title: Xorg crashes with SIGABRT Status in mesa package in Ubuntu: New Bug description: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at
[Desktop-packages] [Bug 2056434] Re: Thunderbird profile not migrated to snap
@Sebastien: Your new push fixed the issue. After the new snap was installed, I started Thunderbird and it immediately imported the original profile and started to download the emails from all IMAP accounts. The locally cached mail folders didn't get copied. So far things seem to be working but I didn't have time yet for closer test beyond deleting a few emails. What was notable was to see that thunderbird spit out a number of errors on vcf cards while downloading the emails. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2056434 Title: Thunderbird profile not migrated to snap Status in thunderbird package in Ubuntu: Fix Released Bug description: Today's update installed the thunderbird snap and removed the thunderbird binary but it did not migrate my thunderbird profile. Now I don't have access to any old mails anymore. Looking at ~/.thunderbird: $ cat profiles.ini [Profile1] Name=default IsRelative=1 Path=ao6t0qef.default Default=1 [InstallFDC34C9F024745EB] Default=ji04wv64.default-release Locked=1 [Profile0] Name=default-release IsRelative=1 Path=ji04wv64.default-release [General] StartWithLastProfile=1 Version=2 ji04wv64.default-release is the folder that should have been migrated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056434/+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 2056434] Re: Thunderbird profile not migrated to snap
@Heinrich: Exactly ONE. The snapped profile manager doesn't see the profile in the proper place ~/.thunderbird Snap is causing nothing but trouble. DEB had been working fine since its inception. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2056434 Title: Thunderbird profile not migrated to snap Status in thunderbird package in Ubuntu: In Progress Bug description: Today's update installed the thunderbird snap and removed the thunderbird binary but it did not migrate my thunderbird profile. Now I don't have access to any old mails anymore. Looking at ~/.thunderbird: $ cat profiles.ini [Profile1] Name=default IsRelative=1 Path=ao6t0qef.default Default=1 [InstallFDC34C9F024745EB] Default=ji04wv64.default-release Locked=1 [Profile0] Name=default-release IsRelative=1 Path=ji04wv64.default-release [General] StartWithLastProfile=1 Version=2 ji04wv64.default-release is the folder that should have been migrated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056434/+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 2056668] Re: Thunderbird Snap migration loses user profile
*** This bug is a duplicate of bug 2056434 ***
https://bugs.launchpad.net/bugs/2056434
@Patrik Lunquist Unfortunately this solution doesn't work for me.
As already shown in my previous post.
In the screenshot attached there you can see the "messenger window"
that opens up when starting thunderbird after moving the .thunderbird
directory.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2056668
Title:
Thunderbird Snap migration loses user profile
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
TL;DR: Snap implementation is FUBAR, how do I get back to a non-SNAP
version?
I consider this bug to be Grave since it not only affects thunderbid,
but also a huge number of depending other services, bug-reporting
amongst it.
Thunderbird Snap migration loses user profile
With the migration from normal deb to snap all and any settings, addons,
accounts, etc got lost.
This is a big no-no.
Architecture: amd64
Version: 1:115.8.1+build1+snap2
No LSB modules are available.
Description: Ubuntu Noble Numbat (development branch)
Release: 24.04
root@kyle:/opt/DATA/media/incoming/tmp# apt-cache policy thunderbird
thunderbird:
Installed: 1:115.8.1+build1+snap2
Candidate: 1:115.8.1+build1+snap2
Version table:
*** 1:115.8.1+build1+snap2 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
1:115.8.1+build1-0ubuntu0.23.10.1 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64
Packages
1:115.3.1+build1-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
neuffer@kyle:~$ ls -la ~/.thunderbird/
total 28
drwx-- 5 neuffer neuffer 4096 Okt 7 2019 .
drwxr-x--- 26 neuffer neuffer 4096 Mär 10 11:09 ..
drwx-- 17 neuffer neuffer 4096 Mär 5 17:50 8ru3o2xn.default
drwx-- 4 neuffer neuffer 4096 Mär 5 15:58 'Crash Reports'
-rw-rw-r-- 1 neuffer neuffer 45 Okt 7 2019 installs.ini
drwx-- 2 neuffer neuffer 4096 Apr 2 2019 'Pending Pings'
-rw-rw-r-- 1 neuffer neuffer 166 Okt 7 2019 profiles.ini
neuffer@kyle:~$
neuffer@kyle:~$ thunderbird --ProfileManager
_IceTransSocketINETConnect() no usable address for kyle:44955
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[Parent 27516, Main Thread] WARNING: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 'glib
warning', file
/build/thunderbird/parts/thunderbird/build/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird:27516): IBUS-WARNING **: 11:14:30.844: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
console.error: (new UnknownError("IndexedDB:
thunderbird/url-classifier-skip-urls getLastModified() IndexedDB: The
operation failed for reasons unrelated to the database itself and not covered
by any other error code.", "resource://services-settings/IDBHelpers.jsm", 18))
_IceTransSocketINETConnect() no usable address for kyle:44955
[ImapModuleLoader] Using nsImapService.cpp
[Parent 27516, Main Thread] WARNING: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 'glib
warning', file
/build/thunderbird/parts/thunderbird/build/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird:27516): IBUS-WARNING **: 11:15:38.811: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0
unprotected)"
console.error: ({})
JavaScript error: chrome://messenger/content/aboutMessage.js, line 119:
NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057
(NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.addProgressListener]
console.error: (new TypeError("NetworkError: Network request failed",
Re: [Desktop-packages] [Bug 2056434] Re: Thunderbird profile not migrated to snap
On 3/11/24 17:13, Patrik Lundquist wrote: > Close Thunderbird. > > Remove the new, empty profile. > rm -r ~/snap/thunderbird/common/.thunderbird > > > mv ~/.thunderbird ~/snap/thunderbird/common/ > That was my very first test. Unfortunately it does NOT work for me as described before and shown in the screenshot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2056434 Title: Thunderbird profile not migrated to snap Status in thunderbird package in Ubuntu: Confirmed Bug description: Today's update installed the thunderbird snap and removed the thunderbird binary but it did not migrate my thunderbird profile. Now I don't have access to any old mails anymore. Looking at ~/.thunderbird: $ cat profiles.ini [Profile1] Name=default IsRelative=1 Path=ao6t0qef.default Default=1 [InstallFDC34C9F024745EB] Default=ji04wv64.default-release Locked=1 [Profile0] Name=default-release IsRelative=1 Path=ji04wv64.default-release [General] StartWithLastProfile=1 Version=2 ji04wv64.default-release is the folder that should have been migrated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056434/+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 2056668] Re: Thunderbird Snap migration loses user profile
*** This bug is a duplicate of bug 2056434 ***
https://bugs.launchpad.net/bugs/2056434
On 3/11/24 10:30, Skia wrote:
> Here is how I worked around this:
> * close thunderbird, make sure it's not running in the background
> * `rsync -raxPHAX ~/.thunderbird/ ~/snap/thunderbird/common/.thunderbird/`
> * edit `~/snap/thunderbird/common/.thunderbird/profiles.ini` to make sure the
> only profile listed here is the one with the data (the biggest folder in
> `~/snap/thunderbird/common/.thunderbird/`)
> * run thunderbird
>
> So far, everything seems to be in order, including contacts, calendars
> on multiple accounts, sieve filter and message redirect plugins.
>
Unfortunately this has not worked for me.
Before I had also tried moving the whole ~/.thunderbird folder to
~/snap/thunderbird/common/ (which does essentially the same thing as
your rsync)
I just get the error message that you can see in the attached
screenshot.
When I move back the empty profile I get what you'd expect: An empty
profile with no settings etc.
** Attachment added: "Thunderbird_SNAP_FUBAR_2024-03-11_13-16-23.png"
https://bugs.launchpad.net/bugs/2056668/+attachment/5754808/+files/Thunderbird_SNAP_FUBAR_2024-03-11_13-16-23.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2056668
Title:
Thunderbird Snap migration loses user profile
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
TL;DR: Snap implementation is FUBAR, how do I get back to a non-SNAP
version?
I consider this bug to be Grave since it not only affects thunderbid,
but also a huge number of depending other services, bug-reporting
amongst it.
Thunderbird Snap migration loses user profile
With the migration from normal deb to snap all and any settings, addons,
accounts, etc got lost.
This is a big no-no.
Architecture: amd64
Version: 1:115.8.1+build1+snap2
No LSB modules are available.
Description: Ubuntu Noble Numbat (development branch)
Release: 24.04
root@kyle:/opt/DATA/media/incoming/tmp# apt-cache policy thunderbird
thunderbird:
Installed: 1:115.8.1+build1+snap2
Candidate: 1:115.8.1+build1+snap2
Version table:
*** 1:115.8.1+build1+snap2 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
1:115.8.1+build1-0ubuntu0.23.10.1 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64
Packages
1:115.3.1+build1-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
neuffer@kyle:~$ ls -la ~/.thunderbird/
total 28
drwx-- 5 neuffer neuffer 4096 Okt 7 2019 .
drwxr-x--- 26 neuffer neuffer 4096 Mär 10 11:09 ..
drwx-- 17 neuffer neuffer 4096 Mär 5 17:50 8ru3o2xn.default
drwx-- 4 neuffer neuffer 4096 Mär 5 15:58 'Crash Reports'
-rw-rw-r-- 1 neuffer neuffer 45 Okt 7 2019 installs.ini
drwx-- 2 neuffer neuffer 4096 Apr 2 2019 'Pending Pings'
-rw-rw-r-- 1 neuffer neuffer 166 Okt 7 2019 profiles.ini
neuffer@kyle:~$
neuffer@kyle:~$ thunderbird --ProfileManager
_IceTransSocketINETConnect() no usable address for kyle:44955
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[Parent 27516, Main Thread] WARNING: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 'glib
warning', file
/build/thunderbird/parts/thunderbird/build/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird:27516): IBUS-WARNING **: 11:14:30.844: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
console.error: (new UnknownError("IndexedDB:
thunderbird/url-classifier-skip-urls getLastModified() IndexedDB: The
operation failed for reasons unrelated to the database itself and not covered
by any other error code.", "resource://services-settings/IDBHelpers.jsm", 18))
_IceTransSocketINETConnect() no usable address for kyle:44955
[ImapModuleLoader] Using nsImapService.cpp
[Parent 27516, Main Thread] WARNING: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 'glib
warning', file
[Desktop-packages] [Bug 2056668] [NEW] Thunderbird Snap migration loses user profile
Public bug reported:
TL;DR: Snap implementation is FUBAR, how do I get back to a non-SNAP
version?
I consider this bug to be Grave since it not only affects thunderbid,
but also a huge number of depending other services, bug-reporting
amongst it.
Thunderbird Snap migration loses user profile
With the migration from normal deb to snap all and any settings, addons,
accounts, etc got lost.
This is a big no-no.
Architecture: amd64
Version: 1:115.8.1+build1+snap2
No LSB modules are available.
Description:Ubuntu Noble Numbat (development branch)
Release:24.04
root@kyle:/opt/DATA/media/incoming/tmp# apt-cache policy thunderbird
thunderbird:
Installed: 1:115.8.1+build1+snap2
Candidate: 1:115.8.1+build1+snap2
Version table:
*** 1:115.8.1+build1+snap2 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
1:115.8.1+build1-0ubuntu0.23.10.1 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64
Packages
1:115.3.1+build1-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
neuffer@kyle:~$ ls -la ~/.thunderbird/
total 28
drwx-- 5 neuffer neuffer 4096 Okt 7 2019 .
drwxr-x--- 26 neuffer neuffer 4096 Mär 10 11:09 ..
drwx-- 17 neuffer neuffer 4096 Mär 5 17:50 8ru3o2xn.default
drwx-- 4 neuffer neuffer 4096 Mär 5 15:58 'Crash Reports'
-rw-rw-r-- 1 neuffer neuffer 45 Okt 7 2019 installs.ini
drwx-- 2 neuffer neuffer 4096 Apr 2 2019 'Pending Pings'
-rw-rw-r-- 1 neuffer neuffer 166 Okt 7 2019 profiles.ini
neuffer@kyle:~$
neuffer@kyle:~$ thunderbird --ProfileManager
_IceTransSocketINETConnect() no usable address for kyle:44955
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[Parent 27516, Main Thread] WARNING: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 'glib
warning', file
/build/thunderbird/parts/thunderbird/build/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird:27516): IBUS-WARNING **: 11:14:30.844: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
console.error: (new UnknownError("IndexedDB:
thunderbird/url-classifier-skip-urls getLastModified() IndexedDB: The
operation failed for reasons unrelated to the database itself and not covered
by any other error code.", "resource://services-settings/IDBHelpers.jsm", 18))
_IceTransSocketINETConnect() no usable address for kyle:44955
[ImapModuleLoader] Using nsImapService.cpp
[Parent 27516, Main Thread] WARNING: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 'glib
warning', file
/build/thunderbird/parts/thunderbird/build/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird:27516): IBUS-WARNING **: 11:15:38.811: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0
unprotected)"
console.error: ({})
JavaScript error: chrome://messenger/content/aboutMessage.js, line 119:
NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057
(NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.addProgressListener]
console.error: (new TypeError("NetworkError: Network request failed",
"resource://services-settings/Utils.sys.mjs", 229))
** Affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
** Tags: grave release-critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2056668
Title:
Thunderbird Snap migration loses user profile
Status in thunderbird package in Ubuntu:
New
Bug description:
TL;DR: Snap implementation is FUBAR, how do I get back to a non-SNAP
version?
I consider this bug to be Grave since it not only affects thunderbid,
but also a huge number of depending other services, bug-reporting
amongst it.
Thunderbird Snap migration loses user profile
With the
[Desktop-packages] [Bug 2048697] Re: Saving backup server credentials
OK that is an interesting data point about the password != NULL failure... But that error is probably coming from the gvfsd-sftp binary, not the deja-dup binary. As another data point, if you use a newer version - like from snap or flatpak installs, does that change anything? I don't remember fixing anything around that, but you never know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/2048697 Title: Saving backup server credentials Status in deja-dup package in Ubuntu: New Bug description: If I want to run a backup, I have to enter the username and password for the target backup server over and over again. Even if I set the checkbox Remember password. System: Description: Ubuntu 22.04.3 LTS Release: 22.04 deja-dup: Installiert: 42.9-1ubuntu3 Installationskandidat: 42.9-1ubuntu3 Versionstabelle: *** 42.9-1ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.9-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: deja-dup 42.9-1ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 22:34:52 2024 InstallationDate: Installed on 2023-06-09 (213 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/2048697/+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 2028698] Re: desktop freezes when copying file to android phone
Files with a quotation mark (") in the filename also seem to trigger it.
I haven't exhaustively tested to determine if there are other characters
that also trigger it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/2028698
Title:
desktop freezes when copying file to android phone
Status in gvfs package in Ubuntu:
Confirmed
Bug description:
If you try to copy a file named a:b.m4b using the nautilus file
manager to a USB-connected Android phone in MTP mode, the desktop will
freeze until you disconnect the USB cable. Then you'll get an error
from nautilus:
"Fehler beim Kopieren von »a:b.m4b«.
Beim Kopieren der Datei nach mtp://Google_Pixel_7_291...
mer%Speicher/Audiobooks ist ein Fehler aufgetreten
libmtp-Fehler: Could not send object."
This happens when the file to be copied contains the colon symbol :
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gvfs-backends 1.48.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
Uname: Linux 5.19.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 25 21:46:45 2023
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85
InstallationDate: Installed on 2021-08-20 (704 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/zsh
SourcePackage: gvfs
UpgradeStatus: Upgraded to jammy on 2022-09-10 (318 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2028698/+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 2049660] [NEW] screen artifacts especially when changing workspaces
Public bug reported: Installed fresh, artifacts started after update. Happens when interacting gnome; menus, changing workspaces, etc. Attached screencast ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 17:55:34 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8c21] InstallationDate: Installed on 2024-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: HP HP Pavilion Plus Laptop 14-ey0xxx ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7trxt5@/vmlinuz-6.5.0-14-generic root=ZFS=rpool/ROOT/ubuntu_7trxt5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2023 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8C21 dmi.board.vendor: HP dmi.board.version: 87.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.27 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd08/10/2023:br15.2:efr87.27:svnHP:pnHPPavilionPlusLaptop14-ey0xxx:pvrType1ProductConfigId:rvnHP:rn8C21:rvr87.27:cvnHP:ct10:cvrChassisVersion:sku8Y7M1EA#ABH: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Plus Laptop 14-ey0xxx dmi.product.sku: 8Y7M1EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption jammy ubuntu wayland-session ** Attachment added: "screencast of changing workspaces to cause artificats" https://bugs.launchpad.net/bugs/2049660/+attachment/5740202/+files/Screencast%20from%2017-01-24%2018%3A11%3A51.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2049660 Title: screen artifacts especially when changing workspaces Status in xorg package in Ubuntu: New Bug description: Installed fresh, artifacts started after update. Happens when interacting gnome; menus, changing workspaces, etc. Attached screencast ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 17:55:34 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8c21] InstallationDate: Installed on 2024-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: HP HP Pavilion Plus Laptop 14-ey0xxx ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7trxt5@/vmlinuz-6.5.0-14-generic root=ZFS=rpool/ROOT/ubuntu_7trxt5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2023 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8C21 dmi.board.vendor: HP dmi.board.version: 87.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release:
[Desktop-packages] [Bug 2048697] Re: Saving backup server credentials
Hmm… that means we aren’t able to store passwords in your desktop secrets / passwords store. It looks like you’re using gnome, so that’s very unexpected (there are known issues with KDE). If you connect to these servers using the basic Files (nautilus) app, do the passwords get saved? ** Changed in: deja-dup (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/2048697 Title: Saving backup server credentials Status in deja-dup package in Ubuntu: Incomplete Bug description: If I want to run a backup, I have to enter the username and password for the target backup server over and over again. Even if I set the checkbox Remember password. System: Description: Ubuntu 22.04.3 LTS Release: 22.04 deja-dup: Installiert: 42.9-1ubuntu3 Installationskandidat: 42.9-1ubuntu3 Versionstabelle: *** 42.9-1ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.9-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: deja-dup 42.9-1ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 22:34:52 2024 InstallationDate: Installed on 2023-06-09 (213 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/2048697/+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 2045644] [NEW] IO error when playing sound
Public bug reported: When using pipewire, sound doesn't play through HDMI. In KDE Audio settings, choosing the HDMI output and playing test sound fails with IO Error. Playing to the internal speaker works. If I use Pulseaudio instead, sound plays normally. The controller is Alder Lake PCH-P High Definition Audio Controller. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pipewire 0.3.79-2 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Dec 5 09:51:36 2023 InstallationDate: Installed on 2023-03-24 (256 days ago) InstallationMedia: Kubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: pipewire UpgradeStatus: Upgraded to mantic on 2023-04-24 (225 days ago) ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2045644 Title: IO error when playing sound Status in pipewire package in Ubuntu: New Bug description: When using pipewire, sound doesn't play through HDMI. In KDE Audio settings, choosing the HDMI output and playing test sound fails with IO Error. Playing to the internal speaker works. If I use Pulseaudio instead, sound plays normally. The controller is Alder Lake PCH-P High Definition Audio Controller. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pipewire 0.3.79-2 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Dec 5 09:51:36 2023 InstallationDate: Installed on 2023-03-24 (256 days ago) InstallationMedia: Kubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: pipewire UpgradeStatus: Upgraded to mantic on 2023-04-24 (225 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2045644/+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 2043529] [NEW] HDMI port issues after ubuntu 23 upgrade
Public bug reported: Hdmi port will not recognize external display after lunar lobster install. This issue was verified by upgrading my desktop to lunar lobster that had 22.10 previously installed. The desktop has 3 monitors working before the upgrade. After the upgrade only one monitor will work. I have attempted to trouble shoot the issue but am leaning towards a bug at this point. The thunderbolt works for displaying however I am unable to get the hdmi to recognize any connection. The port is working and was verified by windows that is dual booted on this laptop. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 545.29.02 Thu Oct 26 21:21:38 UTC 2023 GCC version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~23.04) ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 18:29:03 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: evdi/1.14.1, 6.2.0-27-generic, x86_64: installed nvidia/545.29.02, 6.2.0-27-generic, x86_64: installed rtl8812AU/#MODULE_VERSION#: added virtualbox/7.0.6, 6.2.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2023-02-21 (266 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5530 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=47692d38-dda2-45e4-b8f9-eb478775c1fe ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2023 dmi.bios.release: 1.31 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.31.0 dmi.board.name: 0CDJF9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.31.0:bd03/13/2023:br1.31:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0CDJF9:rvrA01:cvnDellInc.:ct10:cvr:sku087D: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2043529 Title: HDMI port issues after ubuntu 23 upgrade Status in xorg package in Ubuntu: New Bug description: Hdmi port will not recognize external display after lunar lobster install. This issue was verified by upgrading my desktop to lunar lobster that had 22.10 previously installed. The desktop has 3 monitors working before the upgrade. After the upgrade only one monitor will work. I have attempted to trouble shoot the issue but am leaning towards a bug at this point. The thunderbolt works for displaying however I am unable to get the hdmi to recognize any connection.
[Desktop-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
I still have the HP 840 G1, currently on 22.04. I’ll keep an eye on the black screen issue and will report back as soon as it happens again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 Status in xorg package in Ubuntu: Incomplete Bug description: Once every couple hours, the internal laptop display goes black for a few seconds. This was reproducible: + With the laptop connected to a port replicator and the external display connected into the port replicator DP port via DP-DVI adapter. The external display remains on during this time. + With the laptop not connected into a port replicator but connected to an external display. The external display remains on during this time. + With the laptop not connected to either a port replicator or an external display. The hard disk was originally installed with Ubuntu MATE 14.10 in a HP EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and finally moved to the EliteBook 840 G1. The problem started immediately after the drive move. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 8 00:53:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (1002 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2014-12-09 (1158 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Tags: xenial ubuntu Uname: Linux 4.4.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: CNU407CM0V dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
How did you get the FCC Unlock to enable the modem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1981190/+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 2036817]
(In reply to Eric from comment #28) > LibreOffice 7.6.2.1 on opensuse Tumbleweed. This just crashed when i closed > it. It's a simple spreadsheet I am attaching, but the crash happens randomly > at close, not every time. Didn't crash for me in a quick test, but that doesn't necessarily say much as you say it's random. In any case, unless this is known to be related to the issue originally described here, I think this should be handled in a separate bug report, ideally with some more details on what might help to trigger it. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: df79eedf6989ab4c2913a23a7e72079bd719168b CPU threads: 12; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded -- 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/2036817 Title: soffice.bin crashed with SIGSEGV in com::sun::star::uno::Reference::operator->() Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: Occurred when exiting Calc/ ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 13:44:57 2023 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2023-09-17 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2) ProcAttrCurrent: libreoffice-soffice (complain) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi PC (0x7f4aee4abf8e) ok source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: ?? () from /usr/lib/libreoffice/program/libmergedlo.so comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned int, com::sun::star::uno::Reference const&) () from /usr/lib/libreoffice/program/libmergedlo.so comphelper::OAccessibleContextWrapper::disposing() () from /usr/lib/libreoffice/program/libmergedlo.so cppu::WeakComponentImplHelperBase::dispose() () from /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3 cppu::WeakComponentImplHelperBase::release() () from /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3 Title: soffice.bin crashed with SIGSEGV in comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/2036817/+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 2034986] Re: some text became unreadable during a distribution upgrade
Just now upgrading ubuntu-mate 23.04 to 23.10 and encountered the corrupt text issues. Screenshot attached. ** Attachment added: "corruption.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2034986/+attachment/5710737/+files/corruption.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/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Committed Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade
Am in the process of an Ubuntu-Mate 23.04 to 23.10 upgrade and have the corrupted text issue. -- 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/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Committed Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+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 2039486] [NEW] Xwayland 23.2.0 glitches when connecting to vnc based systems
Public bug reported: Ubuntu 23.10 is affected by the following issue: Xwayland 23.2.0 glitches when connecting to vnc based systems https://gitlab.freedesktop.org/xorg/xserver/-/issues/1575 see also: https://bbs.archlinux.org/viewtopic.php?id=288243 see also: https://github.com/TigerVNC/tigervnc/issues/1663 Possible fix: Update Xwayland Ubuntu package to version 23.2.1 ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New -- 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/2039486 Title: Xwayland 23.2.0 glitches when connecting to vnc based systems Status in xwayland package in Ubuntu: New Bug description: Ubuntu 23.10 is affected by the following issue: Xwayland 23.2.0 glitches when connecting to vnc based systems https://gitlab.freedesktop.org/xorg/xserver/-/issues/1575 see also: https://bbs.archlinux.org/viewtopic.php?id=288243 see also: https://github.com/TigerVNC/tigervnc/issues/1663 Possible fix: Update Xwayland Ubuntu package to version 23.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2039486/+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 2033571] Re: Thunderbug hangs on trying to retrieve new email list
I finally gave in and reinstalled Ubuntu. The problem has gone away. I couldn't stand using Evolution anymore ...mcf On 6/10/23 00:37, Sebastien Bacher wrote: > Thank you for your bug report, could you provide some details on the type of > server? Could you also check if the new 115 update fixes it? > Also do you have any error printed out in the journal? > > ** Changed in: thunderbird (Ubuntu) > Importance: Undecided => Low > > ** Changed in: thunderbird (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2033571 Title: Thunderbug hangs on trying to retrieve new email list Status in thunderbird package in Ubuntu: Incomplete Bug description: Connects to server Checks server capabilities Never comes back. inbox tab shows activity forever. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:102.13.0+build1-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mcf1530 F pulseaudio /dev/snd/controlC0: mcf1530 F pulseaudio BuildID: 20230704155023 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Aug 31 12:36:00 2023 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2023-06-03 (88 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.181 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 MostRecentCrashID: bp-0b813420-2716-4e1f-8e16-189a30230720 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 Profile0PrefSources: prefs.js Profile0Prefs: accessibility.typeaheadfind.flashBar: 0 (prefs.js) extensions.lastAppVersion: "102.13.0" (prefs.js) network.trr.blocklist_cleanup_done: true (prefs.js) places.database.lastMaintenance: 1693361930 (prefs.js) privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js) Profile0Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 Profile2PrefSources: prefs.js Profile2Prefs: extensions.lastAppVersion: "115.2.0" (prefs.js) places.database.lastMaintenance: 1693433736 (prefs.js) privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js) Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile2 - LastVersion=115.2.0/20230828145448 (Out of date) Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=102.13.0/20230704155023 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-0b813420-2716-4e1f-8e16-189a30230720 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2021 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.asset.tag: not specified dmi.board.name: 04D48M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.2.0 dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/02/2021:br5.3:svnDellInc.:pnInspiron153515:pvr1.2.0:rvnDellInc.:rn04D48M:rvrA00:cvnDellInc.:ct10:cvr1.2.0:sku0AB4: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3515 dmi.product.sku: 0AB4 dmi.product.version: 1.2.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
Re: [Desktop-packages] [Bug 2033571] Re: Thunderbug hangs on trying to retrieve new email list
I have no idea of the type of email server. It is hosted by hostgo.com. I am trying to receive emails via imap. I am running 115 now (upgraded yestarday). It still won't download current messages. I did find that library libotr wasn't installed (console message) so I installed it. Still no luck. The console shows the following: services.settings: Failed to load last_modified.json: TypeError: NetworkError when attempting to fetch resource. Utils.sys.mjs:322 WebGL context was lost. 2 Troubleshoot.sys.mjs:710:17 I have 3 3 machines running ubuntu 22.04. The others run thunderbird fine. It is just this one that has troubles. Evolution runs OK (it's just not as good an email client). ...Michael Flower On Thu, 2023-10-05 at 13:37 +, Sebastien Bacher wrote: > Thank you for your bug report, could you provide some details on the > type of server? Could you also check if the new 115 update fixes it? > Also do you have any error printed out in the journal? > > ** Changed in: thunderbird (Ubuntu) > Importance: Undecided => Low > > ** Changed in: thunderbird (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2033571 Title: Thunderbug hangs on trying to retrieve new email list Status in thunderbird package in Ubuntu: Incomplete Bug description: Connects to server Checks server capabilities Never comes back. inbox tab shows activity forever. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:102.13.0+build1-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mcf1530 F pulseaudio /dev/snd/controlC0: mcf1530 F pulseaudio BuildID: 20230704155023 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Aug 31 12:36:00 2023 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2023-06-03 (88 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.181 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 MostRecentCrashID: bp-0b813420-2716-4e1f-8e16-189a30230720 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 Profile0PrefSources: prefs.js Profile0Prefs: accessibility.typeaheadfind.flashBar: 0 (prefs.js) extensions.lastAppVersion: "102.13.0" (prefs.js) network.trr.blocklist_cleanup_done: true (prefs.js) places.database.lastMaintenance: 1693361930 (prefs.js) privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js) Profile0Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 Profile2PrefSources: prefs.js Profile2Prefs: extensions.lastAppVersion: "115.2.0" (prefs.js) places.database.lastMaintenance: 1693433736 (prefs.js) privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js) Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile2 - LastVersion=115.2.0/20230828145448 (Out of date) Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=102.13.0/20230704155023 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-0b813420-2716-4e1f-8e16-189a30230720 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.da
[Desktop-packages] [Bug 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04
This is fixed in the 23.10 dailies. I'm not sure it's really practical to fix this for the next 22.04 point release, unfortunately. ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Fix Released ** Changed in: subiquity Status: Triaged => Fix Released -- 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/1974483 Title: autoinstall ssh:install-server:false is misleading in 22.04 Status in subiquity: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Jammy: Confirmed Bug description: With 22.04, openssh-server is baked into the image curtin copies to the target. The ssh:install-server key no longer controls whether openssh-server gets installed. It should be easy enough to have the bit of code that installs openssh-server when the key is true also remove it when the key is false. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1974483/+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 1574586] Re: Not able to rate/review snaps
** Project changed: snappy => snapd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1574586 Title: Not able to rate/review snaps Status in Ratings and Reviews server: New Status in snapd: Confirmed Status in gnome-software package in Ubuntu: Triaged Bug description: Snaps are not able to be rated/reviewed. To manage notifications about this bug go to: https://bugs.launchpad.net/rnr-server/+bug/1574586/+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 1593407] Re: Guest session cannot run snaps
** Project changed: snappy => snapd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1593407 Title: Guest session cannot run snaps Status in Light Display Manager: Confirmed Status in snapd: Confirmed Status in Ubuntu MATE: Confirmed Status in Desktop: New Status in firefox package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in firefox source package in Xenial: Confirmed Status in lightdm source package in Xenial: Confirmed Status in snapd source package in Xenial: Confirmed Bug description: I'm using Ubuntu 16.04. The guest session cannot execute snaps, because of a permission error. The LightDM's guest session AppArmor profile is not allowing access to /snap and other needed files and folders. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1593407/+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 1598667] Re: No snapd API for account registration / password reset
** Project changed: snappy => snapd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1598667 Title: No snapd API for account registration / password reset Status in snapd: Triaged Status in gnome-software package in Ubuntu: Triaged Bug description: There is no mechanism for registering an account using snapd or resetting your password. This is currently done by knowing the appropriate URLs to visit (https://login.ubuntu.com/+forgot_password etc). To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1598667/+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 1555567] Re: [snaps] License information from the store not available
** Project changed: snappy => snapd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/167 Title: [snaps] License information from the store not available Status in snapd: Confirmed Status in snapd-glib: Confirmed Status in Software Center Agent: New Status in gnome-software package in Ubuntu: Fix Released Bug description: While the store (and its API) has a field to specify the app's license, it seems to be ignored somewhere on its way to the client. As an example, ubuntu-calculator-app.ubuntucoredev has GPL3 set as its license in the store, yet in GNOME Software it is tagged as "non-free" when listed in a search. Clicking on the package details in GNOME Software, the license type is shown as "Unknown". To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/167/+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 1643910] Re: BAMF_DESKTOP_FILE_HINT not set in correct place for unity7
** Project changed: snappy => snapd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1643910 Title: BAMF_DESKTOP_FILE_HINT not set in correct place for unity7 Status in snapd: Triaged Status in bamf package in Ubuntu: Fix Released Bug description: Occasionally when I pin items to the Unity7 launcher, the BAMF code (as I'm told) incorrectly matches to /snap/app/revision/ This is a security issue because the Exec= line points to /snap/app/revision/... which bypasses snap run (/snap/bin/...) and therefore snap-confine. I'm told by Marcus (aka, 3v1n0 aka Trevinho) that this is because BAMF_DESKTOP_FILE_HINT is not exported by snap env and instead only injected in the desktop file that is created in /var/lib/snapd/desktop/applications upon snap install. This means that the wrong Exec= (ie, where it points to the binary) may occur in two places: 1. when launching /snap/bin/... from the command line 2. when something in /var/lib/snapd/desktop/applications/*.desktop doesn't match properly In both cases, the initial launch is fine, but pinning the icon to the launcher results in the wrong entry in the Exec= line and launching from this pinned launcher entry after is unconfined. You can check by doing: 1. launch application from the dash 2. run sudo aa-status and see if it is launched under confinement 3. pin the icon that is in the launcher 4. close the application, then launch from the pinned icon 5. run sudo aa-status and see if it is launched under confinement This doesn't happen all the time. For example, vlc seems to work fine both from the command line and from launching via a pinned launcher entry. chrome-test on the other hand doesn't seem to work with either. Related https://github.com/snapcore/snapd/pull/1580 -- puts BAMF_DESKTOP_FILE_HINT in the desktop file instead of in the environment, but Marco requested that this change (https://github.com/snapcore/snapd/pull/1580#issuecomment-234546220). https://trello.com/c/xP1hN3BF/152-improve-desktop-file-support-by- adding-a-new-bamf-desktop-file-hint-environment-hint also discussed this issue, but the card is archived and therefore it won't be worked on. I'm having trouble finding a simple reproducer (other than chrome- test) but am told by Marco that the BAMF matching will always work if BAMF_DESKTOP_FILE_HINT in the process' environment always points to the desktop file in /var/lib/snapd/desktop/applications. I will continue to look for a simple reproducer. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1643910/+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 2035016] Re: one of 3 monitors "frozen" when a window moves there
I have experienced this (or something very like this) a few times on my t14 amd gen 3, which does not have dual GPUs. I only updated to libmutter 45 this morning though. -- 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/2035016 Title: one of 3 monitors "frozen" when a window moves there Status in mutter package in Ubuntu: Incomplete Bug description: When I move a window to one of my 3 monitors (not the main display), the monitor freezes. That means that moving the mouse there doesn't work and the picture is frozen on that monitor (including the mouse pointer which is visible there). The journal has those logs: Sep 10 07:21:49 clown-t14 gnome-shell[5640]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Sep 10 07:21:49 clown-t14 systemd[5341]: Started vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 launched by kgx process 7379. Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object .Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d5260 b resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9 55b07789d9f0 i resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10 7ffe4d1dc560 b resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11 55b07789d968 i resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12 55b07789d8d8 i resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789d9f0 i
[Desktop-packages] [Bug 2033571] Re: Thunderbug hangs on trying to retrieve new email list
Problem started after software update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2033571 Title: Thunderbug hangs on trying to retrieve new email list Status in thunderbird package in Ubuntu: New Bug description: Connects to server Checks server capabilities Never comes back. inbox tab shows activity forever. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:102.13.0+build1-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mcf1530 F pulseaudio /dev/snd/controlC0: mcf1530 F pulseaudio BuildID: 20230704155023 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Aug 31 12:36:00 2023 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2023-06-03 (88 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.181 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 MostRecentCrashID: bp-0b813420-2716-4e1f-8e16-189a30230720 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 Profile0PrefSources: prefs.js Profile0Prefs: accessibility.typeaheadfind.flashBar: 0 (prefs.js) extensions.lastAppVersion: "102.13.0" (prefs.js) network.trr.blocklist_cleanup_done: true (prefs.js) places.database.lastMaintenance: 1693361930 (prefs.js) privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js) Profile0Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 Profile2PrefSources: prefs.js Profile2Prefs: extensions.lastAppVersion: "115.2.0" (prefs.js) places.database.lastMaintenance: 1693433736 (prefs.js) privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js) Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile2 - LastVersion=115.2.0/20230828145448 (Out of date) Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=102.13.0/20230704155023 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-0b813420-2716-4e1f-8e16-189a30230720 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2021 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.asset.tag: not specified dmi.board.name: 04D48M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.2.0 dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/02/2021:br5.3:svnDellInc.:pnInspiron153515:pvr1.2.0:rvnDellInc.:rn04D48M:rvrA00:cvnDellInc.:ct10:cvr1.2.0:sku0AB4: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3515 dmi.product.sku: 0AB4 dmi.product.version: 1.2.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2033571/+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 2033571] Re: Thunderbug hangs on trying to retrieve new email list
Using imap!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2033571 Title: Thunderbug hangs on trying to retrieve new email list Status in thunderbird package in Ubuntu: New Bug description: Connects to server Checks server capabilities Never comes back. inbox tab shows activity forever. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:102.13.0+build1-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mcf1530 F pulseaudio /dev/snd/controlC0: mcf1530 F pulseaudio BuildID: 20230704155023 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Aug 31 12:36:00 2023 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2023-06-03 (88 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.181 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 MostRecentCrashID: bp-0b813420-2716-4e1f-8e16-189a30230720 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 Profile0PrefSources: prefs.js Profile0Prefs: accessibility.typeaheadfind.flashBar: 0 (prefs.js) extensions.lastAppVersion: "102.13.0" (prefs.js) network.trr.blocklist_cleanup_done: true (prefs.js) places.database.lastMaintenance: 1693361930 (prefs.js) privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js) Profile0Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 Profile2PrefSources: prefs.js Profile2Prefs: extensions.lastAppVersion: "115.2.0" (prefs.js) places.database.lastMaintenance: 1693433736 (prefs.js) privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js) Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile2 - LastVersion=115.2.0/20230828145448 (Out of date) Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=102.13.0/20230704155023 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-0b813420-2716-4e1f-8e16-189a30230720 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2021 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.asset.tag: not specified dmi.board.name: 04D48M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.2.0 dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/02/2021:br5.3:svnDellInc.:pnInspiron153515:pvr1.2.0:rvnDellInc.:rn04D48M:rvrA00:cvnDellInc.:ct10:cvr1.2.0:sku0AB4: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3515 dmi.product.sku: 0AB4 dmi.product.version: 1.2.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2033571/+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 2033571] [NEW] Thunderbug hangs on trying to retrieve new email list
Public bug reported: Connects to server Checks server capabilities Never comes back. inbox tab shows activity forever. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:102.13.0+build1-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mcf1530 F pulseaudio /dev/snd/controlC0: mcf1530 F pulseaudio BuildID: 20230704155023 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Aug 31 12:36:00 2023 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2023-06-03 (88 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.181 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 MostRecentCrashID: bp-0b813420-2716-4e1f-8e16-189a30230720 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 Profile0PrefSources: prefs.js Profile0Prefs: accessibility.typeaheadfind.flashBar: 0 (prefs.js) extensions.lastAppVersion: "102.13.0" (prefs.js) network.trr.blocklist_cleanup_done: true (prefs.js) places.database.lastMaintenance: 1693361930 (prefs.js) privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js) Profile0Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 Profile2PrefSources: prefs.js Profile2Prefs: extensions.lastAppVersion: "115.2.0" (prefs.js) places.database.lastMaintenance: 1693433736 (prefs.js) privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js) Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile2 - LastVersion=115.2.0/20230828145448 (Out of date) Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=102.13.0/20230704155023 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-0b813420-2716-4e1f-8e16-189a30230720 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2021 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.asset.tag: not specified dmi.board.name: 04D48M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.2.0 dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/02/2021:br5.3:svnDellInc.:pnInspiron153515:pvr1.2.0:rvnDellInc.:rn04D48M:rvrA00:cvnDellInc.:ct10:cvr1.2.0:sku0AB4: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3515 dmi.product.sku: 0AB4 dmi.product.version: 1.2.0 dmi.sys.vendor: Dell Inc. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2033571 Title: Thunderbug hangs on trying to retrieve new email list Status in thunderbird package in Ubuntu: New Bug description: Connects to server Checks server capabilities Never comes back. inbox tab shows activity forever. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:102.13.0+build1-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mcf1530 F pulseaudio /dev/snd/controlC0: mcf1530 F pulseaudio BuildID: 20230704155023 CasperMD5CheckResult: pass Channel:
[Desktop-packages] [Bug 1951685] Re: Chromium flatpak reliably crashes xdg-desktop-portal
Hi, the problem occurs again with Flatpak 1.14.4: UngoogledChromium refuses to load any content after a short period of time. Installed browser version: com.github.Eloston.UngoogledChromium 114.0.5735.106 OS: Ubuntu 20.04.6 LTS (Focal Fossa) Desktop: Gnome 3.36.9 Best regards Michael -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1951685 Title: Chromium flatpak reliably crashes xdg-desktop-portal Status in xdg-desktop-portal package in Ubuntu: New Bug description: For a while now I am facing the issue that Chromium installed via Flatpak after a minute or so stops working with a puzzling error ERR_NO_SUPPORTED_PROXIES. I guess this is due to the Proxy feature of the desktop portal because now I noticed that the portal is actually crashing shortly after I started Chromium and/or started browsing. According to the stack trace this happens in get_one_app_state so I think this bug was fixed in version 1.7.0 with this patch: https://github.com/flatpak/xdg-desktop- portal/commit/a0b641f1230016e8ed9a291c70d4dd226429dda4 Could that fix please be backported to 1.6.0/focal? PID: 15467 (xdg-desktop-por) UID: 1000 (xxx) GID: 1000 (xxx) Signal: 11 (SEGV) Timestamp: Sat 2021-11-20 16:55:00 CET (4min 23s ago) Command Line: /usr/libexec/xdg-desktop-portal Executable: /usr/libexec/xdg-desktop-portal Control Group: /user.slice/user-1000.slice/user@1000.service/xdg-desktop-portal.service Unit: user@1000.service User Unit: xdg-desktop-portal.service Slice: user-1000.slice Owner UID: 1000 (xxx) Boot ID: 1841d625a5354885a778e18a20b48103 Machine ID: 30e0f491ec7847428bc900251dc271af Hostname: xxx Storage: /var/lib/systemd/coredump/core.xdg-desktop-por.1000.1841d625a5354885a778e18a20b48103.15467.1637423700.lz4 Message: Process 15467 (xdg-desktop-por) of user 1000 dumped core. Stack trace of thread 15505: #0 0x7f5990c485f4 g_str_hash (libglib-2.0.so.0 + 0x405f4) #1 0x7f5990c4773c g_hash_table_lookup (libglib-2.0.so.0 + 0x3f73c) #2 0x5646137cf282 get_one_app_state (xdg-desktop-portal + 0x30282) #3 0x5646137cf778 background_monitor (xdg-desktop-portal + 0x30778) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5 0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f5990b15293 __clone (libc.so.6 + 0x122293) Stack trace of thread 15470: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a4a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7f5990c5a4f1 n/a (libglib-2.0.so.0 + 0x524f1) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5 0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f5990b15293 __clone (libc.so.6 + 0x122293) Stack trace of thread 15475: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a4a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7f598e5f099d n/a (libdconfsettings.so + 0xa99d) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5 0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f5990b15293 __clone (libc.so.6 + 0x122293) Stack trace of thread 15467: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a6f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3) #3 0x5646137bb7e8 main (xdg-desktop-portal + 0x1c7e8) #4 0x7f5990a1a0b3 __libc_start_main (libc.so.6 + 0x270b3) #5 0x5646137bb94e _start (xdg-desktop-portal + 0x1c94e) Stack trace of thread 15471: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a6f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3) #3 0x7f5990eaff8a n/a (libgio-2.0.so.0 + 0x11ef8a) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5
[Desktop-packages] [Bug 1981351] Re: libreoffice crash, undefined symbol: hb_graphite2_face_get_gr_face
Reconfigure HarfBuzz src with `./configure --with-graphite2` (and make install) to fix the error. -- 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/1981351 Title: libreoffice crash, undefined symbol: hb_graphite2_face_get_gr_face Status in libreoffice package in Ubuntu: Invalid Bug description: Libreoffice doesn't open or work launching from terminal errors out with following error: /usr/lib/libreoffice/program/soffice.bin: symbol lookup error: /usr/lib/libreoffice/program/libmergedlo.so: undefined symbol: hb_graphite2_face_get_gr_face A quick google search gave solution to remove /usr/local/lib/x86_64-linux-gnu/libharfbuzz.so.0, which works although temporarily the package "libharfbuzz0b" reinstalls this lib and it causes same error again Also the package libharfbuzz0b is used by other packages so cant be removed from apt directly, leading to no permanent solution to this problem Info about the libreoffice and libharfbuzz0b packages - ``` apt list libreoffice -a Listing... Done libreoffice/jammy-updates,now 1:7.3.4-0ubuntu0.22.04.1 amd64 [installed] libreoffice/jammy 1:7.3.2-0ubuntu2 amd64 ``` ``` apt list libharfbuzz0b -a Listing... Done libharfbuzz0b/jammy,now 2.7.4-1ubuntu3 amd64 [installed,automatic] libharfbuzz0b/jammy 2.7.4-1ubuntu3 i386 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice 1:7.3.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 11 23:31:01 2022 InstallationDate: Installed on 2020-08-06 (704 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to jammy on 2022-04-24 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1981351/+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 2018401] Re: Backport neon27 to 0.32.5 in Ubuntu 22.04, 0.32.2 has bugs
** Summary changed: - Backport neon27 to 0.32.5 in Ubunto 22.04, 0.32.2 has bugs + Backport neon27 to 0.32.5 in Ubuntu 22.04, 0.32.2 has bugs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to neon27 in Ubuntu. https://bugs.launchpad.net/bugs/2018401 Title: Backport neon27 to 0.32.5 in Ubuntu 22.04, 0.32.2 has bugs Status in neon27 package in Ubuntu: New Bug description: Due to a bug in neon27 it is not possible to mount WebDAV folders with davfs. See https://github.com/notroj/neon/issues/78 and https://github.com/notroj/neon/issues/88 This is solved in 0.32.5 as available in newer Ubuntu versions. Please provide a backport to upgrade neon27 to 0.32.5 in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2018401/+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 2021499] [NEW] package firefox 113.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Public bug reported: This happened when i was upgrading to Ubuntu 22.04 on my VMWARE. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 113.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1596 F pulseaudio BuildID: 20230522134052 CasperMD5CheckResult: unknown Channel: Unavailable Date: Mon May 29 14:41:22 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2023-05-29 (0 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) IpRoute: default via 192.168.80.2 dev ens33 proto dhcp metric 100 169.254.0.0/16 dev ens33 scope link metric 1000 192.168.80.0/24 dev ens33 proto kernel scope link src 192.168.80.129 metric 100 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, 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.9 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 113.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-05-29 (0 days ago) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2021499 Title: package firefox 113.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: This happened when i was upgrading to Ubuntu 22.04 on my VMWARE. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 113.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1596 F pulseaudio BuildID: 20230522134052 CasperMD5CheckResult: unknown Channel: Unavailable Date: Mon May 29 14:41:22 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2023-05-29 (0 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) IpRoute: default via 192.168.80.2 dev ens33 proto dhcp metric 100 169.254.0.0/16 dev ens33 scope link metric 1000 192.168.80.0/24 dev ens33 proto kernel scope link src 192.168.80.129 metric 100 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, 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.9 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 113.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-05-29 (0 days ago) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dm
[Desktop-packages] [Bug 2020593] Re: after computer crash LibreOffice recovered open files, but only a small fraction of them
The screenshot I attached was blank. I didn't check it beforehand, but Screenshot did not capture output on my terminal. I think you have what you need in the ProcCpuinfo files. If not let me know. -- 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/2020593 Title: after computer crash LibreOffice recovered open files, but only a small fraction of them Status in libreoffice package in Ubuntu: New Bug description: My system crashes frequently, but each time when I open LibreOffice it lists all previously open files and recovers them. This time it listed the files, appeared to recover them, but after I clicked Finish I had only six out of a couple dozen files. All my untitled files are gone, nowhere to be found. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-148.165-generic 5.4.231 Uname: Linux 5.4.0-148-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 23 13:32:08 2023 InstallationDate: Installed on 2019-10-21 (1310 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2022-12-26 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2020593/+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 2020593] [NEW] after computer crash LibreOffice recovered open files, but only a small fraction of them
Public bug reported: My system crashes frequently, but each time when I open LibreOffice it lists all previously open files and recovers them. This time it listed the files, appeared to recover them, but after I clicked Finish I had only six out of a couple dozen files. All my untitled files are gone, nowhere to be found. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-148.165-generic 5.4.231 Uname: Linux 5.4.0-148-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 23 13:32:08 2023 InstallationDate: Installed on 2019-10-21 (1310 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2022-12-26 (147 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2023-05-23 13-29-35.png" https://bugs.launchpad.net/bugs/2020593/+attachment/5675060/+files/Screenshot%20from%202023-05-23%2013-29-35.png -- 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/2020593 Title: after computer crash LibreOffice recovered open files, but only a small fraction of them Status in libreoffice package in Ubuntu: New Bug description: My system crashes frequently, but each time when I open LibreOffice it lists all previously open files and recovers them. This time it listed the files, appeared to recover them, but after I clicked Finish I had only six out of a couple dozen files. All my untitled files are gone, nowhere to be found. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-148.165-generic 5.4.231 Uname: Linux 5.4.0-148-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 23 13:32:08 2023 InstallationDate: Installed on 2019-10-21 (1310 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2022-12-26 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2020593/+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 2018985] [NEW] package ubuntu-minimal 1.501 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
Public bug reported: after restart same crash ProblemType: Package DistroRelease: Ubuntu 23.04 Package: ubuntu-minimal 1.501 ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue May 9 11:25:37 2023 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert ImageMediaBuild: 20221018.1 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: ubuntu-meta Title: package ubuntu-minimal 1.501 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 arm64-image lunar raspi-image -- 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/2018985 Title: package ubuntu-minimal 1.501 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert Status in ubuntu-meta package in Ubuntu: New Bug description: after restart same crash ProblemType: Package DistroRelease: Ubuntu 23.04 Package: ubuntu-minimal 1.501 ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue May 9 11:25:37 2023 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert ImageMediaBuild: 20221018.1 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: ubuntu-meta Title: package ubuntu-minimal 1.501 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2018985/+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 2018661] [NEW] package libxxf86vm1 1:1.1.4-1build3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: Attempting to install steam ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libxxf86vm1 1:1.1.4-1build3 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None Date: Sat May 6 16:04:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:122d] InstallationDate: Installed on 2023-02-14 (81 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. X750JA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=/dev/mapper/vgubuntu-root ro recovery nomodeset dis_ucode_ldr Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.6 SourcePackage: libxxf86vm Title: package libxxf86vm1 1:1.1.4-1build3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X750JB.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X750JA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX750JB.208:bd08/14/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnX750JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X750JA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: libxxf86vm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxxf86vm in Ubuntu. https://bugs.launchpad.net/bugs/2018661 Title: package libxxf86vm1 1:1.1.4-1build3 failed to install/upgrade: dpkg- deb --fsys-tarfile subprocess returned error exit status 2 Status in libxxf86vm package in Ubuntu: New Bug description: Attempting to install steam ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libxxf86vm1 1:1.1.4-1build3 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None Date: Sat May 6 16:04:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:122d] InstallationDate: Installed on 2023-02-14 (81 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. X750JA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=/dev/mapper/vgubuntu-root ro recovery nomodeset dis_ucode_ldr Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.6 SourcePackage: libxxf86vm Title: package libxxf86vm1 1:1.1.4-1build3 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X750JB.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X750JA
[Desktop-packages] [Bug 2018401] [NEW] Backport neon27 to 0.32.5 in Ubunto 22.04, 0.32.2 has bugs
Public bug reported: Due to a bug in neon27 it is not possible to mount WebDAV folders with davfs. See https://github.com/notroj/neon/issues/78 and https://github.com/notroj/neon/issues/88 This is solved in 0.32.5 as available in newer Ubuntu versions. Please provide a backport to upgrade neon27 to 0.32.5 in Ubuntu 22.04 ** Affects: neon27 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to neon27 in Ubuntu. https://bugs.launchpad.net/bugs/2018401 Title: Backport neon27 to 0.32.5 in Ubunto 22.04, 0.32.2 has bugs Status in neon27 package in Ubuntu: New Bug description: Due to a bug in neon27 it is not possible to mount WebDAV folders with davfs. See https://github.com/notroj/neon/issues/78 and https://github.com/notroj/neon/issues/88 This is solved in 0.32.5 as available in newer Ubuntu versions. Please provide a backport to upgrade neon27 to 0.32.5 in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2018401/+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 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
This is still an issue with 22.04.2 LTS. If both dock auto-hide and 200% scaling are enabled, search results can not be clicked. Changing either setting allows clicking. Installed gnome-shell-extension-ubuntu-dock version is 72~ubuntu5.22.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in Dash to dock: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Confirmed Bug description: The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1979096/+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 2015134] [NEW] libdmapsharing with 3.0 API is incompatible with libsoup3
Public bug reported: The version of the libdmapsharing API found in the libdmapsharing packages shipped by Ubuntu is obsolete, and the versions of libdmapsharing that provide it are incompatible with libsoup3. Since more applications are requiring libsoup3, and libsoup3 cannot exist with libsoup2 in the same process, Ubuntu should move to libdmapsharing-3.9.12+ in its upcoming release. Libdmapsharing-3.9.12+ makes use of libsoup3. The packages that use libdmapsharing include Rhythmbox and grilo-plugins, and both recently moved to libsoup3: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1996 https://gitlab.gnome.org/GNOME/grilo-plugins/-/commit/ae34da2264eab49eceaeeb0d1510b952a65ae030 The 3.9 series of libdmapsharing is available at: https://www.flyn.org/projects/libdmapsharing/ ** Affects: libdmapsharing (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libdmapsharing in Ubuntu. https://bugs.launchpad.net/bugs/2015134 Title: libdmapsharing with 3.0 API is incompatible with libsoup3 Status in libdmapsharing package in Ubuntu: New Bug description: The version of the libdmapsharing API found in the libdmapsharing packages shipped by Ubuntu is obsolete, and the versions of libdmapsharing that provide it are incompatible with libsoup3. Since more applications are requiring libsoup3, and libsoup3 cannot exist with libsoup2 in the same process, Ubuntu should move to libdmapsharing-3.9.12+ in its upcoming release. Libdmapsharing-3.9.12+ makes use of libsoup3. The packages that use libdmapsharing include Rhythmbox and grilo-plugins, and both recently moved to libsoup3: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1996 https://gitlab.gnome.org/GNOME/grilo-plugins/-/commit/ae34da2264eab49eceaeeb0d1510b952a65ae030 The 3.9 series of libdmapsharing is available at: https://www.flyn.org/projects/libdmapsharing/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdmapsharing/+bug/2015134/+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 2009071] [NEW] [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all
Public bug reported: New install of Ubuntu 22.04 has no audio. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1793 F pulseaudio /dev/snd/controlC1: mblack 1793 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Thu Mar 2 13:21:20 2023 InstallationDate: Installed on 2023-03-02 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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: mblack 1793 F pulseaudio /dev/snd/controlC1: mblack 1793 F pulseaudio mblack 8091 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Razer dmi.bios.version: 1.07 dmi.board.name: SO690 dmi.board.vendor: Razer dmi.board.version: 4 dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnRazer:bvr1.07:bd01/27/2023:br1.7:efr1.3:svnRazer:pnBlade16-RZ09-0483:pvr9.04:rvnRazer:rnSO690:rvr4:cvnRazer:ct10:cvr:skuRZ09-0483SEJ3: dmi.product.family: 1A583006 Razer Blade dmi.product.name: Blade 16 - RZ09-0483 dmi.product.sku: RZ09-0483SEJ3 dmi.product.version: 9.04 dmi.sys.vendor: Razer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2009071 Title: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: New install of Ubuntu 22.04 has no audio. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1793 F pulseaudio /dev/snd/controlC1: mblack 1793 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Thu Mar 2 13:21:20 2023 InstallationDate: Installed on 2023-03-02 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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: mblack 1793 F pulseaudio /dev/snd/controlC1: mblack 1793 F pulseaudio mblack 8091 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Razer dmi.bios.version: 1.07 dmi.board.name: SO690 dmi.board.vendor: Razer dmi.board.version: 4 dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnRazer:bvr1.07:bd01/27/2023:br1.7:efr1.3:svnRazer:pnBlade16-RZ09-0483:pvr9.04:rvnRazer:rnSO690:rvr4:cvnRazer:ct10:cvr:skuRZ09-0483SEJ3: dmi.product.family: 1A583006 Razer Blade dmi.product.name: Blade 16 - RZ09-0483 dmi.product.sku: RZ09-0483SEJ3 dmi.product.version: 9.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2009071/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1930769] Re: When enabled, Firefox AppArmor profile prevents U2F devices from working
Hi Don Rico!
This is actually fixed for me on 22.04
22.04 moved Firefox into snap, and snap has a whitelist of permitted U2F
tokens:
https://github.com/snapcore/snapd/blob/2.58.3/interfaces/builtin/u2f_devices.go#L43
That's a list of USB VID and PID, which you can find for your device
using the lsusb command. If your U2F device isn't on that list, you can
raise an MR like https://github.com/snapcore/snapd/pull/10642 to get it
enabled.
Some might debate the wisdom of the OS vendor maintaining a list of
blessed devices - but it is what it is.
--
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/1930769
Title:
When enabled, Firefox AppArmor profile prevents U2F devices from
working
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Summary:
If you enable the apparmor profile that comes in Ubuntu's Firefox
package, it prevents USB U2F tokens from being used.
To reproduce:
1. Obtain a USB FIDO/U2F token - such as a Yubikey; and a clean
install of Ubuntu 20.04 with Firefox installed, but the AppArmor
profile for firefox disabled (As is the default).
2. Confirm the correct function of your U2F token - such as at
https://demo.yubico.com/webauthn-technical
3. Enable the AppArmor profile with the following command, then
restart firefox.
sudo aa-enforce /etc/apparmor.d/usr.bin.firefox
4. Repeat your test of your U2F token. You will find Firefox is unable
to access your U2F token. Any accounts you need U2F to log into are
now inaccessible.
5. Disabling the apparmor profile and restarting firefox will make U2F
work again.
To work around:
Edit /etc/apparmor.d/usr.bin.firefox and replace these lines:
# Doesn't seem to be required, but noisy. Maybe allow 'r' for 'b*' if
needed.
# Possibly move to an abstraction if anything else needs it.
deny /run/udev/data/** r,
Instead allowing access to udev data, and to hidraw devices:
/run/udev/data/** r,
/dev/hidraw[0-9] rw,
I haven't checked the security implications of this change; some might
feel it grants overly broad access. Chromium, which in 20.04 is
delivered as a snap, includes udev rules (70-snap.chromium.rules)
which I suspect grant access in a device-id-whitelisted way.
This is me resubmitting #1930768 this time with all the info attached.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 88.0.1+build1-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mtandy 1757 F pulseaudio
/dev/snd/controlC1: mtandy 1757 F pulseaudio
BuildID: 20210504152106
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 3 23:34:55 2021
ForcedLayersAccel: False
IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2021-05-31 (3 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
IpRoute:
default via 192.168.0.1 dev enp3s0 proto dhcp metric 100
169.254.0.0/16 dev enp3s0 scope link metric 1000
192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.2 metric 100
MostRecentCrashID: bp-4122b123-9c74-4baf-b817-c8a771171216
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:352
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=88.0.1/20210504152106 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2202
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-K
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2202:bd07/11/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-K:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
mtime.conffile..etc.apparmor.d.usr.bin.firefox: 2021-06-03T23:25:44.143815
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930769/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to :
[Desktop-packages] [Bug 2006754] Re: hdmi audio not working after suspend to ram
So, just to try something, I installed kernel 6.2rc8 from Ubuntu kernel PPA. And... Problem fixed!! -- 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/2006754 Title: hdmi audio not working after suspend to ram Status in alsa-driver package in Ubuntu: New Bug description: Hello I installed a new Kubuntu 22.10 system on a Beelink GTR6 (AMD Ryzen 9 6900HX). Everything is running fine. Except that after a wakeup from a suspend to RAM, there is no more Audio coming through the loudspeakers in my HDMI monitor, although every widget, audio control etc still say that audio is playing. I have not yet found any way to reactivate the audio, except of a complete reboot of the system. I am not sure, how to debug this. I have tried very many recommendations from the net (to restart pipewire, wireplumber, disconnect the HDMI device, open amixer, ...), but none worked. Thanks Michael --- Betriebssystem: Kubuntu 22.10 KDE-Plasma-Version: 5.25.5 KDE-Frameworks-Version: 5.98.0 Qt-Version: 5.15.6 Kernel-Version: 5.19.0-31-generic (64-bit) Grafik-Plattform: X11 Prozessoren: 16 × AMD Ryzen 9 6900HX with Radeon Graphics Speicher: 28.2 GiB Arbeitsspeicher Grafikprozessor: REMBRANDT Hersteller: AZW Produktname: GTR Systemversion: V02 Affected package: No idea, maybe pipewire, wireplumber, but probably a kernel driver Expected result: HDMI audio should work after wakeup from a suspend- to-ram Some output from pw-cli ls: ``` id 0, type PipeWire:Interface:Core/3 object.serial = "0" core.name = "pipewire-0" id 1, type PipeWire:Interface:Module/3 object.serial = "1" module.name = "libpipewire-module-rt" id 2, type PipeWire:Interface:Module/3 object.serial = "2" module.name = "libpipewire-module-protocol-native" id 3, type PipeWire:Interface:Module/3 object.serial = "3" module.name = "libpipewire-module-profiler" id 4, type PipeWire:Interface:Profiler/3 object.serial = "4" id 5, type PipeWire:Interface:Module/3 object.serial = "5" module.name = "libpipewire-module-metadata" id 6, type PipeWire:Interface:Factory/3 object.serial = "6" module.id = "5" factory.name = "metadata" factory.type.name = "PipeWire:Interface:Metadata" factory.type.version = "3" id 7, type PipeWire:Interface:Module/3 object.serial = "7" module.name = "libpipewire-module-spa-device-factory" id 8, type PipeWire:Interface:Factory/3 object.serial = "8" module.id = "7" factory.name = "spa-device-factory" factory.type.name = "PipeWire:Interface:Device" factory.type.version = "3" id 9, type PipeWire:Interface:Module/3 object.serial = "9" module.name = "libpipewire-module-spa-node-factory" id 10, type PipeWire:Interface:Factory/3 object.serial = "10" module.id = "9" factory.name = "spa-node-factory" factory.type.name = "PipeWire:Interface:Node" factory.type.version = "3" id 11, type PipeWire:Interface:Module/3 object.serial = "11" module.name = "libpipewire-module-client-node" id 12, type PipeWire:Interface:Factory/3 object.serial = "12" module.id = "11" factory.name = "client-node" factory.type.name = "PipeWire:Interface:ClientNode" factory.type.version = "4" id 13, type PipeWire:Interface:Module/3 object.serial = "13" module.name = "libpipewire-module-client-device" id 14, type PipeWire:Interface:Factory/3 object.serial = "14" module.id = "13" factory.name = "client-device" factory.type.name = "Spa:Pointer:Interface:Device" factory.type.version = "0" id 15, type PipeWire:Interface:Module/3 object.serial = "15" module.name = "libpipewire-module-portal" id 16, type
[Desktop-packages] [Bug 2007004] Re: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected
2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 - Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx - Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 - Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 - Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx + Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by + local choice (Reason: 3=DEAUTH_LEAVING) + Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx + with macid 0 left + Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 + Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 + Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx + Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 + Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 + Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> - Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 - Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 - Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx - Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx - Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) - Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated - Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) - Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) - Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx joined with macid 0 - Feb 11 20:47:19 ithaca kernel: [ 3449.943789] wlo1: associated - Feb 11 20:47:19 ithaca kernel: [ 3449.995269] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready + Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 + Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 + Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx + Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx + Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) + Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated + Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de:5d:xx:xx:xx:xx (try 1/3) + Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2) + Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx joined with macid 0 + Feb 11 20:47:19 ithaca kernel: [ 3449.943789] wlo1: associated + Feb 11 20:47:19 ithaca kernel: [ 3449.995269] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready Nothing logged in dmesg After reconnecting WiFi, everything works OK again. - - I assume bluez is the correct package - please let me know if otherwise, - of if there is any other info I can provide. - - Thanks, - - Michael ** Summary changed: - Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected + rtw88_8821ce: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2007004 Title: rtw88_8821ce: Bluetooth Mouse go
[Desktop-packages] [Bug 2007004] [NEW] Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected
if otherwise, of if there is any other info I can provide. Thanks, Michael ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2007004 Title: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected Status in bluez package in Ubuntu: New Bug description: Ubuntu 22.04.01 / ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse. Fully updated via apt. Everything worked OK until sometime around early January 2023 (it may have started earlier, but I only noticed it the first time I moved to a location without WiFi). Since then, everything works OK as long as I am connected to WiFi. The moment I disconnect from a WiFi network, or disable WiFi altogether, the mouse begins to rapidly disconnect/connect in a loop about 3-4 times a second. If I boot up somewhere where I have no WiFi signal, same thing happens. If I boot with an older 22.04.01 live USB - no problem If I boot with a recent 22.10 live USB - same problem root@ithaca:~ # uname -a Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux root@ithaca:~ # inxi -EMN Machine: Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA v: 1.0 serial: Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX UEFI: American Megatrends v: E410MA.302 date: 09/11/2020 Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1 Output of running bluetoothctl while this happens: root@ithaca:/var/log # bluetoothctl Agent registered (At this point I disconnect WiFI. Mouse starts acting up immediately, responding erratically, then about 10 seconds elapse, then the below messages start) [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no (This goes on and on about 3 times a second until I reconnect Wifi using the touchpad) [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX Connected: no [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes [MX Anywhere 2S]# [MX Anywhere 2S]# kern.log messages while this happens: < I disconnect from Wifi> Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from de:5d:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta de:5d:xx:xx:xx:xx with macid 0 left Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87 Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88 Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90 Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91 Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx < I reconnect to Wifi> Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93 Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94 Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 2S] on 20:4e:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with de:5d:xx:xx:xx:xx Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to de:5d:xx:xx:xx:xx (try 1/3) Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with de
[Desktop-packages] [Bug 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER
It's 2023 now, and I just ran across this problem. What is the solution? I searched on Google and found people having variations of this or similar problems since 2018. That FIVE years. The newest discussion I found on Google (and don't find anymore) explained that this is an issue with the Kernel and some cgroups. When upgrading the release to 22.10 and installing proposed kernels didn't help, I was about to uninstall Ubuntu that I just used to replace the outdated Macos on my kids computers. I told them Linux is faster, just as beautiful and there are no issues with random stuff not working. By replacing APT packages with snaps you are forcing your users to use snaps. I have no quarrels with snap. Go ahead and replace Debian with it. But at least make them work for Gods sake. If you don't care for human users and want to get big in cloud enterprise, that's fine too, just tell us that we're no longer relevant as users. I choose ubuntu exactly because I did not want to be bothered by having to fix my kids computers. I choose ubuntu for my work environment because it worked so far. I'm using Linux since it was first published. I have no sensibility that creating home directories in a place other than /home is a problem that will lead to basic programs such as browsers not working anymore. When I see an error message "Permission denied", I expect to see a filesystem object with permissions denying access, not a directory to which that very user actually has full access. This is the output of `mount`: ``` sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=3874748k,nr_inodes=968687,mode=755,inode64) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=787660k,mode=755,inode64) /dev/mapper/ubuntu--vg-ubuntu--lv on / type ext4 (rw,relatime) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64) cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=19470) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime) ramfs on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700) /var/lib/snapd/snaps/bare_5.snap on /snap/bare/5 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide) /var/lib/snapd/snaps/chromium_2295.snap on /snap/chromium/2295 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide) /var/lib/snapd/snaps/core20_1587.snap on /snap/core20/1587 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide) /var/lib/snapd/snaps/core20_1778.snap on /snap/core20/1778 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide) /var/lib/snapd/snaps/cups_872.snap on /snap/cups/872 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide) /var/lib/snapd/snaps/firefox_2277.snap on /snap/firefox/2277 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide) /var/lib/snapd/snaps/gnome-3-38-2004_119.snap on /snap/gnome-3-38-2004/119 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide) /var/lib/snapd/snaps/gtk-common-themes_1535.snap on /snap/gtk-common-themes/1535 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide) /var/lib/snapd/snaps/lxd_24322.snap on /snap/lxd/24322 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide) /var/lib/snapd/snaps/lxd_23541.snap on /snap/lxd/23541 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide) /var/lib/snapd/snaps/snap-store_638.snap on /snap/snap-store/638 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide) /var/lib/snapd/snaps/snapd_17950.snap on /snap/snapd/17950 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide,x-gvfs-hide) /var/lib/snapd/snaps/snapd-desktop-integration_49.snap on /snap/snapd-desktop-integration/49 type squashfs
[Desktop-packages] [Bug 2002102] [NEW] gnome-shell has continouus high cpu utilization of nearly 20 %
Public bug reported: excerpt from top: 4625 michael 20 0 5077584 256364 114324 S 18,3 3,2 10:32.37 gnome-shell 1500 root 20 0 1139948 121488 72424 S 10,6 1,5 7:22.24 Xorg 4858 michael 20 0 405756 44672 32928 S 3,3 0,6 2:14.81 plank 6861 michael 20 0 898372 61712 44712 S 3,0 0,8 0:10.26 gnome-terminal- 5207 michael 31 11 12,5g 565140 204924 S 2,3 7,0 15:48.61 firefox 14261 michael 31 11 2471436 134648 92944 S 2,0 1,7 0:06.48 Isolated Web Co 10389 root 20 0 0 0 0 I 1,3 0,0 0:28.22 kworker/1:3-events 14 root 20 0 0 0 0 I 0,3 0,0 0:05.85 rcu_sched 22 root 20 0 0 0 0 S 0,3 0,0 0:14.96 ksoftirqd/1 131 root 0 -20 0 0 0 D 0,3 0,0 0:03.14 kworker/u9:0+i915_flip 177 root 0 -20 0 0 0 I 0,3 0,0 0:01.17 kworker/2:1H-events_highpri 250 root 20 0 0 0 0 I 0,3 0,0 0:10.68 kworker/0:2-events 4902 michael 31 11 1827896 50784 17048 S 0,3 0,6 0:19.78 syncthing 5504 michael 31 11 2486188 141052 91908 S 0,3 1,8 0:31.26 Isolated Web Co 6788 michael 20 0 1471320 76164 57676 S 0,3 0,9 0:26.51 wfica 7142 michael 20 0 15768 3296 R 0,3 0,1 0:14.54 top 7150 michael 20 0 3948680 384776 194316 S 0,3 4,8 0:26.26 thunderbird ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 6 11:32:40 2023 DisplayManager: lightdm EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-19 (2696 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha amd64 (20150729) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-08-26 (132 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2002102 Title: gnome-shell has continouus high cpu utilization of nearly 20 % Status in gnome-shell package in Ubuntu: New Bug description: excerpt from top: 4625 michael 20 0 5077584 256364 114324 S 18,3 3,2 10:32.37 gnome-shell 1500 root 20 0 1139948 121488 72424 S 10,6 1,5 7:22.24 Xorg 4858 michael 20 0 405756 44672 32928 S 3,3 0,6 2:14.81 plank 6861 michael 20 0 898372 61712 44712 S 3,0 0,8 0:10.26 gnome-terminal- 5207 michael 31 11 12,5g 565140 204924 S 2,3 7,0 15:48.61 firefox 14261 michael 31 11 2471436 134648 92944 S 2,0 1,7 0:06.48 Isolated Web Co 10389 root 20 0 0 0 0 I 1,3 0,0 0:28.22 kworker/1:3-events 14 root 20 0 0 0 0 I 0,3 0,0 0:05.85 rcu_sched 22 root 20 0 0 0 0 S 0,3 0,0 0:14.96 ksoftirqd/1 131 root 0 -20 0 0
[Desktop-packages] [Bug 1966418]
Is this still a problem? -- 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/1966418 Title: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) Status in Gnome DevHelp: Invalid Status in Mesa: Fix Released Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in webkit2gtk package in Ubuntu: Invalid Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+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 1995073] Re: Ubuntu 22.10 deja-dup throws exception when login
The packaging suggests (but does not recommend) python3-pydrive. Which means it isn't installed by default when you install deja-dup. (Which I believe is done so that python3-pydrive doesn't have to be promoted to main.) But the packaging does also set it up so that Deja Dup *should* have offered to install python3-pydrive when you tried to back up and it wasn't installed... So that looks like the bug here. Wonder why it didn't. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1995073 Title: Ubuntu 22.10 deja-dup throws exception when login Status in deja-dup package in Ubuntu: New Bug description: Can't login and restore from GDrive. See attached picture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1995073/+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 1995073] Re: Ubuntu 22.10 deja-dup throws exception when login
If you install python3-pydrive does that error go away? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1995073 Title: Ubuntu 22.10 deja-dup throws exception when login Status in deja-dup package in Ubuntu: New Bug description: Can't login and restore from GDrive. See attached picture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1995073/+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 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland
Hi, In order to meet our customer's schedule expectation, would you please upload this solution to -proposed before Oct. 29, 2022? Thanks for your support. -- 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/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: Fix Committed Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Confirmed Status in gnome-shell source package in Kinetic: Fix Released Bug description: [Impact] Users using desktop PC is not able to switch monitor mode between mirrored and joined mode using Super-P or keyboard shortcut. This SRU fixes the issue. [Test Plan] 1. Use a desktop PC and start GNOME 3 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again Expected: Display Switcher popup should appear Actual: Display Switcher does not popup [Where problems could occur] Although this change is minimal, the impact should be only on switching display mode using the shortcut. [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
Hi Daniel, In order to meet customer's TTM expectation, would you please upload the solution to Jammy -proposed no later than Oct. 29, 2022? Thanks for your great support. -- 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/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Status in mutter source package in Kinetic: Fix Released Bug description: [ Impact ] On dual-GPU systems, gnome-shell may crash in gbm_surface_release_buffer() during display config changes, like when rearranging monitor positions. [ Test Plan ] 1. Find a dual GPU system where both use open source drivers (like Intel + AMD). 2. Ideally also attach one monitor to each GPU. 3. Open Settings and repeatedly change the monitor layout pressing Apply each time. Expect: System does not crash. [ Where problems could occur ] Anywhere to do with screen updates since the entire triple buffering patch has been updated. [ Other Info ] The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 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/mutter/+bug/1969422/+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 1993008] Re: ftbfs: E: fontconfig: alien-tag fc-cache-used-in-maintainer-script
lintian errors do not count as a build failure. You could file this as a bug in Debian if you like -- we'll pick up the fix from there in due course. ** Changed in: fontconfig (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1993008 Title: ftbfs: E: fontconfig: alien-tag fc-cache-used-in-maintainer-script Status in fontconfig package in Ubuntu: Invalid Bug description: When trying to build from source using debuild -us -uc -b the result errors out with Now running lintian fontconfig_2.13.1-4.4ubuntu1_amd64.changes ... E: fontconfig: alien-tag fc-cache-used-in-maintainer-script [usr/share/lintian/overrides/fontconfig:1] W: libfontconfig-doc: bad-whatis-entry [usr/share/man/man3/FcPatternIterNext.3.gz] from: https://www.mit.edu/afs.new/sipb/project/debathena/lintian/www/tags/fc-cache-used-in-maintainer-script.html "This script apparently runs fc-cache. Updating of the fontconfig cache files is now handled automatically by triggers, so running fc-cache from maintainer scripts is no longer necessary." ubuntu: kinetic kudu libfontconfig1-dev: Installed: 2.13.1-4.4ubuntu1 Candidate: 2.13.1-4.4ubuntu1 Version table: *** 2.13.1-4.4ubuntu1 500 500 http://ubuntu.hysing.is/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libfontconfig-dev 2.13.1-4.4ubuntu1 Uname: Linux 6.0.1-gnulibre x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Oct 14 21:07:42 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fontconfig UpgradeStatus: Upgraded to kinetic on 2022-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1993008/+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 1689381] Re: FTBFS cp: cannot stat 'doc/fontconfig-user.html'
fontconfig 2.13.1-4.4ubuntu1 built successfully for me in a kinetic sbuild so I think this can be closed. ** Changed in: fontconfig (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1689381 Title: FTBFS cp: cannot stat 'doc/fontconfig-user.html' Status in fontconfig package in Ubuntu: Fix Released Bug description: while attempting to build with debuild: debuild -us -uc -b ... Adding cdbs dependencies to debian/libfontconfig1-dbg.substvars dh_installdirs -plibfontconfig1-dbg \ dh_installdocs -pfontconfig ./README ./NEWS ./AUTHORS cp: cannot stat 'doc/fontconfig-user.html': No such file or directory dh_installdocs: cp --reflink=auto -a doc/fontconfig-user.html debian/fontconfig/usr/share/doc/fontconfig returned exit code 1 /usr/share/cdbs/1/rules/debhelper.mk:235: recipe for target 'binary-install/fontconfig' failed make: *** [binary-install/fontconfig] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 debuild: fatal error at line 1116: dpkg-buildpackage -rfakeroot -us -uc -b failed z@aisha:~/fontconfig/fontconfig-2.11.94/debian$ ubuntu: 17.10 artful libfontconfig1-dev: 2.11.94-0ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libfontconfig1-dev (not installed) ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Mon May 8 19:23:10 2017 InstallationDate: Installed on 2016-05-07 (366 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fontconfig UpgradeStatus: Upgraded to artful on 2017-05-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1689381/+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 1992688] Re: firefox deb not installed
This just needs to be backported to Jammy now? -- 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/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in firefox source package in Jammy: New Status in ubuntu-meta source package in Jammy: Triaged Bug description: Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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 1990312] Re: Can't change desktop language in Ubuntu 22.04
Set the package to "ubuntu-meta" containing "ubuntu-desktop" ** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- 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/1990312 Title: Can't change desktop language in Ubuntu 22.04 Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I initially installed Ubuntu 22.04 with the English language. Now, I'd like to use the Ubuntu desktop in the German language. I believe I've done everything needed. I rebooted of course. The login screen is now in German, but my user desktop is still in English, except the calendar showing the date. See the attached screenshot. Here is the output of the "locale" command: LANG=de_DE.UTF-8 LANGUAGE=en LC_CTYPE=en_US.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=en_US.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= Am I the only one having this issue? Thanks in advance Michael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990312/+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 1988499] [NEW] Snap prevents repartitioning Azure resource disk
Public bug reported: In an Azure VM, the resource disk (a.k.a. “local” or “temp” disk) has a single partition created by the Azure infrastructure. Linux cloud-init creates an ext4 file system in that partition and arranges for it to be mounted on /mnt. In Ubuntu 20.04 and Ubuntu 22.04 images in the Azure Marketplace, snap then creates a bind mount of /mnt for its internal purposes. Some customers want to use the Azure resource disk for purposes other than a file system mounted on /mnt. If they unmount the disk, and use a partition editor to remove or change the partition structure, the closing ioctl to re-read the partition table fails because the Linux kernel still has a reference to the disk. The command “blockdev --rereadpt” also fails. After debugging this problem, it turns out that the umount of /mnt only partially succeeds, and that’s why the ioctl thinks the disk is still in use. From what’s visible in the file system, the umount has succeeded. And “lsblk” shows that /dev/sdb1 (assuming the resource disk is /dev/sdb) as not mounted anywhere. But this message: [ 51.885870] EXT4-fs (sdb1): unmounting filesystem. is *not* output in dmesg because internally the Linux kernel still has a reference to the mount that it is waiting (forever) to go away. The problem is that snap has a reference to the mount, which was created by “snap-confine” doing the bind mount. This behavior of snap is specifically for the /mnt mount point (and maybe “/” for the root file system?): * If I bugger things up a bit so that cloud-init doesn’t force the resource disk mount point to be /mnt, and change it to be /mnt2, then Ubuntu boots normally, and mounts the resource disk on /mnt2. At that point, I can umount /mnt2, and the umount is done 100%, including the “unmounting filesystem” message in dmesg. The ioctl problem in fdisk or parted goes away commensurately. * If I remove “snap” entirely from my Ubuntu 20.04 installation, the problem also goes away. * The problem does not occur on RHEL 8.5 or CentOS 8.5, which don’t have snap in the first place. What’s the right way to solve this problem? Unfortunately, I’m not knowledgeable about snap or what snap-confine is trying to do. * Why is snap tracking /mnt? Is there a way to tell snap not to track /mnt? * Or is there some design flaw in snap that causes the mount on /mnt to not work normally? Longer run, we’re looking at enhancing cloud-init with an option to not mount the resource disk at all, which should avoid the problem. But still, there should be a way for the mount of the resource disk on /mnt to work normally. ** Affects: ubuntu Importance: Undecided Status: New ** Package changed: gnome-bluetooth (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1988499 Title: Snap prevents repartitioning Azure resource disk Status in Ubuntu: New Bug description: In an Azure VM, the resource disk (a.k.a. “local” or “temp” disk) has a single partition created by the Azure infrastructure. Linux cloud- init creates an ext4 file system in that partition and arranges for it to be mounted on /mnt. In Ubuntu 20.04 and Ubuntu 22.04 images in the Azure Marketplace, snap then creates a bind mount of /mnt for its internal purposes. Some customers want to use the Azure resource disk for purposes other than a file system mounted on /mnt. If they unmount the disk, and use a partition editor to remove or change the partition structure, the closing ioctl to re-read the partition table fails because the Linux kernel still has a reference to the disk. The command “blockdev --rereadpt” also fails. After debugging this problem, it turns out that the umount of /mnt only partially succeeds, and that’s why the ioctl thinks the disk is still in use. From what’s visible in the file system, the umount has succeeded. And “lsblk” shows that /dev/sdb1 (assuming the resource disk is /dev/sdb) as not mounted anywhere. But this message: [ 51.885870] EXT4-fs (sdb1): unmounting filesystem. is *not* output in dmesg because internally the Linux kernel still has a reference to the mount that it is waiting (forever) to go away. The problem is that snap has a reference to the mount, which was created by “snap-confine” doing the bind mount. This behavior of snap is specifically for the /mnt mount point (and maybe “/” for the root file system?): * If I bugger things up a bit so that cloud-init doesn’t force the resource disk mount point to be /mnt, and change it to be /mnt2, then Ubuntu boots normally, and mounts the resource disk on /mnt2. At that point, I can umount /mnt2, and the umount is done 100%, including the “unmounting filesystem” message in dmesg. The ioctl problem in fdisk or parted goes away commensurately. * If I remove “snap” entirely from my
[Desktop-packages] [Bug 1980934] Re: Backup fail with unknown error
** Changed in: deja-dup (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1980934 Title: Backup fail with unknown error Status in deja-dup package in Ubuntu: Fix Released Bug description: I removed the cache and start a backup in console like DEJA_DUP_DEBUG=1 deja-dup and got during verification the Unknown Error with following final outputs DUPLICITY: DEBUG 1 DUPLICITY: . Found manifest volume 845 DUPLICITY: INFO 1 DUPLICITY: . Found 845 volumes in manifest DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' DUPLICITY: DEBUG 1 DUPLICITY: . Removing still remembered temporary file /tmp/duplicity-7zeqbwou-tempdir/mkstemp-oc2otu7o-1 DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' I than checked the cache which still contains all files including the lockfile ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 7 10:55:01 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-12-07 (942 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to focal on 2020-10-04 (640 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1980934/+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 1988313] [NEW] xcalc button colours muddled
Public bug reported: The xcalc app has muddled button colours when in the default TI mode. In particular, the digits 7, 8 and 9 are a different colour to the digits 1 to 6. This was fixed upstream by a corrected Xresources file in https://gitlab.freedesktop.org/xorg/app/xcalc/-/commit/19eb8cefe1c3f7b5018e51d3dd5cc4bf691a553d I believe that kinetic is okay, being based on xcalc 1.1.1 which has this patch. But 22.04LTS and 20.04LTS are both affected. The impact is only cosmetic, but it would still look better if it were fixed! Bug in x11-apps 7.7+8build2 (and previous versions for several years) ** Affects: x11-apps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-apps in Ubuntu. https://bugs.launchpad.net/bugs/1988313 Title: xcalc button colours muddled Status in x11-apps package in Ubuntu: New Bug description: The xcalc app has muddled button colours when in the default TI mode. In particular, the digits 7, 8 and 9 are a different colour to the digits 1 to 6. This was fixed upstream by a corrected Xresources file in https://gitlab.freedesktop.org/xorg/app/xcalc/-/commit/19eb8cefe1c3f7b5018e51d3dd5cc4bf691a553d I believe that kinetic is okay, being based on xcalc 1.1.1 which has this patch. But 22.04LTS and 20.04LTS are both affected. The impact is only cosmetic, but it would still look better if it were fixed! Bug in x11-apps 7.7+8build2 (and previous versions for several years) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/1988313/+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 1872124] Re: Please integrate ubuntu-drivers --gpgpu into Ubuntu Server
The version of subiquity in 22.04.1 supports this now. ** Changed in: subiquity Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1872124 Title: Please integrate ubuntu-drivers --gpgpu into Ubuntu Server Status in cloud-init: Incomplete Status in MAAS: Incomplete Status in subiquity: Fix Released Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Could subiquity provide an option in the UI to install and execute ubuntu-drivers-common on the target? The use case I'm interested in is an "on-rails" installation of Nvidia drivers for servers being installed for deep learning workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1872124/+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 1983381] Re: Enable the restic backend
https://gitlab.gnome.org/World/deja-dup/-/blob/main/PACKAGING.md has some advice for packagers around enabling restic support. (Though note that it references the new `-Dpackagekit=enabled` flag which only exists in 44.x. Just ignore that for 43.x. PackageKit is automatically used as long as it exists at build time in 43.x) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1983381 Title: Enable the restic backend Status in deja-dup package in Ubuntu: New Bug description: https://discourse.gnome.org/t/call-for-testing-deja-dup-43-alpha/7602 Even though it's flagged as experimental, there is a lot of excitement around it, and it's still opt-in. It looks like it requires rclone, which is not in main, but the same trick used for pydrive can be used, and then it can be installed at run-time if the user selects restic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1983381/+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 1952533] Re: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while
I have the same problem. It started late in 2021, I think. I have no damn clue what's going on. Sound often works when booting from "off". It often breaks if I put my laptop to sleep and wake it. It may break at other times? When the sound stops, it stops sound on the whole machine. I have a USB-A to 3.5" headphone adapter and I thought I could use that because it is separate hardware, but, no, that doesn't work either. I've tried blacklisting the snd_hda_codec_realtek module, but it still happens. I've tried installing the original OS (Ubuntu 18.04 from Dell) and it still happens. Maybe I zapped the audio card with static electricity and it stopped working? But why would that affect the USB-A dongle? Maybe there was a firmware update from Dell that changed its behavior? I'm stupified. But I need audio. I love Linux, but I'm thinking of abandoning Linux and going to MacOS, because I need working audio! -- 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/1952533 Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sometimes if I run `pulseaudio -k` a few times, sound returns. Sometimes if I run `sudo alsa force-reload`, sound returns. Sometimes if I shutdown and start the laptop, sound returns. This first occurred a few months ago when I was running 20.04, and I upgraded to 21.10 in the hope it would fix the issue. It did not - sound continues to be intermittent. I use the Brave browser, not firefox. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sheehan3636 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 27 20:21:47 2021 InstallationDate: Installed on 2021-10-15 (43 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Nov 27 19:00:54 xps systemd[1436]: pulseaudio.service: Deactivated successfully. Nov 27 19:01:05 xps systemd[1436]: pulseaudio.socket: Deactivated successfully. Symptom_Type: Sound works for a while, then breaks Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2021 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd07/09/2021:br1.16:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-27T18:59:43.285943 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952533/+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 1980934] Re: Backup fail with unknown error
Hello, sorry this fell off my radar. I'm not sure what to do though, since there's so little actionable information. Is it possible to get more of the logs from running "DEJA_DUP_DEBUG=1 deja-dup"? There's nothing in what you posted originally that looks like an actual error message. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1980934 Title: Backup fail with unknown error Status in deja-dup package in Ubuntu: Incomplete Bug description: I removed the cache and start a backup in console like DEJA_DUP_DEBUG=1 deja-dup and got during verification the Unknown Error with following final outputs DUPLICITY: DEBUG 1 DUPLICITY: . Found manifest volume 845 DUPLICITY: INFO 1 DUPLICITY: . Found 845 volumes in manifest DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' DUPLICITY: DEBUG 1 DUPLICITY: . Removing still remembered temporary file /tmp/duplicity-7zeqbwou-tempdir/mkstemp-oc2otu7o-1 DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' I than checked the cache which still contains all files including the lockfile ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 7 10:55:01 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-12-07 (942 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to focal on 2020-10-04 (640 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1980934/+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 1971768] Re: Totem not running on Ubuntu 22.04 Wayland
I'm surprised that anyone can change the status of the bug. Anyway I encountered it too(#1982656) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1971768 Title: Totem not running on Ubuntu 22.04 Wayland Status in totem package in Ubuntu: Incomplete Bug description: $ totem ** (totem:106519): WARNING **: 01:12:30.962: Element 'gtkglsink' is missing, verify your installation ** (totem:106519): WARNING **: 01:12:30.962: Element 'glsinkbin' is missing, verify your installation (totem:106519): GStreamer-CRITICAL **: 01:12:33.537: gst_bus_set_flushing: assertion 'GST_IS_BUS (bus)' failed (totem:106519): GLib-GObject-CRITICAL **: 01:12:33.537: g_object_set: assertion 'G_IS_OBJECT (object)' failed --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-02-11 (448 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: totem 42.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-29.30-generic 5.15.35 Tags: wayland-session jammy Uname: Linux 5.15.0-29-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (5 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1971768/+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 1982656] [NEW] Totem not running after upgrading to Ubuntu 22.04
*** This bug is a duplicate of bug 1971768 *** https://bugs.launchpad.net/bugs/1971768 Public bug reported: ** (totem:5488): WARNING **: 17:40:41.485: Element 'gtkglsink' is missing, verify your installation ** (totem:5488): WARNING **: 17:40:41.485: Element 'glsinkbin' is missing, verify your installation (totem:5488): GStreamer-CRITICAL **: 17:40:42.700: gst_bus_set_flushing: assertion 'GST_IS_BUS (bus)' failed (totem:5488): GLib-GObject-CRITICAL **: 17:40:42.700: g_object_set: assertion 'G_IS_OBJECT (object)' failed (apparently a duplicate of #1971768) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 23 17:53:30 2022 InstallationDate: Installed on 2021-02-10 (528 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: totem UpgradeStatus: Upgraded to jammy on 2022-07-23 (0 days ago) ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** This bug has been marked a duplicate of bug 1971768 Totem not running on Ubuntu 22.04 Wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1982656 Title: Totem not running after upgrading to Ubuntu 22.04 Status in totem package in Ubuntu: New Bug description: ** (totem:5488): WARNING **: 17:40:41.485: Element 'gtkglsink' is missing, verify your installation ** (totem:5488): WARNING **: 17:40:41.485: Element 'glsinkbin' is missing, verify your installation (totem:5488): GStreamer-CRITICAL **: 17:40:42.700: gst_bus_set_flushing: assertion 'GST_IS_BUS (bus)' failed (totem:5488): GLib-GObject-CRITICAL **: 17:40:42.700: g_object_set: assertion 'G_IS_OBJECT (object)' failed (apparently a duplicate of #1971768) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 23 17:53:30 2022 InstallationDate: Installed on 2021-02-10 (528 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: totem UpgradeStatus: Upgraded to jammy on 2022-07-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1982656/+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 1980934] Re: Backup fail with unknown error
Those messages from the log look innocent enough to me. So the backups themselves work correctly, but when we get to the verification step at the end, you see an unknown error? No further output in that dialog? The verification step tries to restore a canary file we insert in the backup, just to ensure that files can be restored from the new backup. So something is going wrong with that sample restore... ** Changed in: deja-dup (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1980934 Title: Backup fail with unknown error Status in deja-dup package in Ubuntu: Incomplete Bug description: I removed the cache and start a backup in console like DEJA_DUP_DEBUG=1 deja-dup and got during verification the Unknown Error with following final outputs DUPLICITY: DEBUG 1 DUPLICITY: . Found manifest volume 845 DUPLICITY: INFO 1 DUPLICITY: . Found 845 volumes in manifest DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' DUPLICITY: DEBUG 1 DUPLICITY: . Removing still remembered temporary file /tmp/duplicity-7zeqbwou-tempdir/mkstemp-oc2otu7o-1 DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' DUPLICITY: DEBUG 1 DUPLICITY: . Releasing lockfile b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile' I than checked the cache which still contains all files including the lockfile ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 7 10:55:01 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-12-07 (942 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to focal on 2020-10-04 (640 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1980934/+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 1980908] Re: duplicity does NOT close properly
Hi, Kenneth! This would almost certainly just be Deja Dup's fault, I can't imagine duplicity would be an issue here. @khteh - it should be safe to kill an active duplicity process and restart your backup, to recover from this happening as a workaround. But obviously, there's still the bug that it did happen in the first place. How did you close Deja Dup? Normally, there's the progress dialog with cancel or resume later buttons, both of which should stop the duplicity process. If Deja Dup was shut down unexpectedly, I could maybe see this happening. ** Changed in: deja-dup Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1980908 Title: duplicity does NOT close properly Status in Déjà Dup: Incomplete Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: Duplicity process stays running after closing deja-dup backups app from Ubuntu desktop. Openning up deja-dup again, go to Restore tab, error message shows "Another duplicity instance is already running with this archive directory". `ps -ef | grep duplicity` shows the process still running. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1980908/+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 1968552] Re: Opening web link from evince doesn't work, "env: ‘/snap/bin/firefox’: Permission denied"
*** This bug is a duplicate of bug 1794064 *** https://bugs.launchpad.net/bugs/1794064 Same issue by the way with the Chromium snap if you make it the default browser: env: ‘/snap/bin/chromium’: Permission denied -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1968552 Title: Opening web link from evince doesn't work, "env: ‘/snap/bin/firefox’: Permission denied" Status in evince package in Ubuntu: Confirmed Bug description: Jammy Jellyfish 22.04. When opening a PDF document with an external link in it, clicking the link doesn't do anything. However, stderr says "env: ‘/snap/bin/firefox’: Permission denied" How to reproduce: Open example PDF file. Click link. Expected: firefox opens link. Actual result: nothing; stderr says: env: ‘/snap/bin/firefox’: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1968552/+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 1978486] Re: Right clicks on file icons select a different file
The 'use-experimental-views' option appears to have been the problem. I reset it, and the problem seems to have gone away. I do not think I explicitly set that option, so I don't know how it got turned on. But this machine has been upgraded in place several times, so it may have been something that occurred years ago. No matter, it appears to be working correctly now, in several different directories & using several different zoom levels. I believe this bug report can be marked as 'resolved'. -- 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/1978486 Title: Right clicks on file icons select a different file Status in nautilus package in Ubuntu: Incomplete Bug description: Upgraded to 20.04 from 18.04. Right clicking on files in icon view will always select a different file. This does not happen in list (or detail) mode. Switching between the two modes several times will sometimes make the functionality work for a while in icon mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 11:47:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (2894 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2022-06-07 (5 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-07-06T11:04:37.239623 usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978486/+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 1978486] Re: Right clicks on file icons select a different file
I use xorg. I have attached a movie of this behavior. ** Attachment added: "Screencast from 06-13-2022 04:40:04 PM.webm" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978486/+attachment/5597095/+files/Screencast%20from%2006-13-2022%2004%3A40%3A04%20PM.webm -- 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/1978486 Title: Right clicks on file icons select a different file Status in nautilus package in Ubuntu: Incomplete Bug description: Upgraded to 20.04 from 18.04. Right clicking on files in icon view will always select a different file. This does not happen in list (or detail) mode. Switching between the two modes several times will sometimes make the functionality work for a while in icon mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 11:47:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (2894 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2022-06-07 (5 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-07-06T11:04:37.239623 usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978486/+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 1978486] [NEW] Right clicks on file icons select a different file
Public bug reported: Upgraded to 20.04 from 18.04. Right clicking on files in icon view will always select a different file. This does not happen in list (or detail) mode. Switching between the two modes several times will sometimes make the functionality work for a while in icon mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 11:47:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (2894 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2022-06-07 (5 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-07-06T11:04:37.239623 usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1978486 Title: Right clicks on file icons select a different file Status in nautilus package in Ubuntu: New Bug description: Upgraded to 20.04 from 18.04. Right clicking on files in icon view will always select a different file. This does not happen in list (or detail) mode. Switching between the two modes several times will sometimes make the functionality work for a while in icon mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 11:47:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (2894 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2022-06-07 (5 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-07-06T11:04:37.239623 usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978486/+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 1978411] [NEW] simple-scan throws error and crashes upon scanning document
Public bug reported:
[+0.00s] DEBUG: simple-scan.vala:1720: Starting simple-scan 3.36.3, PID=94430
[+0.00s] DEBUG: unsetenv() is not thread-safe and should not be used after
threads are created
[+0.02s] DEBUG: _g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
[+0.06s] DEBUG: app-window.vala:1906: Loading state from
/home/mcapp/.cache/simple-scan/state
[+0.06s] DEBUG: app-window.vala:1885: Restoring window to 600x400 pixels
[+0.38s] DEBUG: scanner.vala:1539: sane_init () -> SANE_STATUS_GOOD
[+0.38s] DEBUG: scanner.vala:1545: SANE version 1.0.29
[+0.38s] DEBUG: scanner.vala:1606: Requesting redetection of scan devices
[+0.38s] DEBUG: scanner.vala:828: Processing request
[+0.57s] DEBUG: app-window.vala:1981: Saving state to
/home/mcapp/.cache/simple-scan/state
[+9.67s] DEBUG: app-window.vala:1981: Saving state to
/home/mcapp/.cache/simple-scan/state
[+11.26s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+11.26s] DEBUG: scanner.vala:353: Device: name="brother4:net1;dev0"
vendor="Brother" model="MFC-9130CW" type="MFC-9130CW"
[+11.55s] DEBUG: app-window.vala:1981: Saving state to
/home/mcapp/.cache/simple-scan/state
[+11.70s] DEBUG: app-window.vala:1981: Saving state to
/home/mcapp/.cache/simple-scan/state
[+12.68s] DEBUG: simple-scan.vala:1536: Requesting scan at 1200 dpi from device
'brother4:net1;dev0'
[+12.68s] DEBUG: scanner.vala:1674: Scanner.scan ("brother4:net1;dev0",
dpi=1200, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0,
paper_height=0, brightness=0, contrast=0, delay=3000ms)
[+12.68s] DEBUG: scanner.vala:828: Processing request
[+12.93s] DEBUG: app-window.vala:1981: Saving state to
/home/mcapp/.cache/simple-scan/state
[+14.30s] DEBUG: app-window.vala:1981: Saving state to
/home/mcapp/.cache/simple-scan/state
[+18.55s] DEBUG: scanner.vala:889: sane_open ("brother4:net1;dev0") ->
SANE_STATUS_GOOD
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (0)
[+18.55s] DEBUG: scanner.vala:760: Option 0: name='(null)' title='Number of
options' type=bool size=4 cap=soft-detect
[+18.55s] DEBUG: scanner.vala:763: Description: Read-only option that
specifies how many options a specific devices supports.
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (1)
[+18.55s] DEBUG: scanner.vala:760: Option 1: name='(null)' title='Mode'
type=group size=4 cap=advanced
[+18.55s] DEBUG: scanner.vala:763: Description:
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (2)
[+18.55s] DEBUG: scanner.vala:760: Option 2: name='mode' title='Scan mode'
type=string size=30 values=["Black & White", "Gray[Error Diffusion]", "True
Gray", "24bit Color", "24bit Color[Fast]"] cap=soft-select,soft-detect
[+18.55s] DEBUG: scanner.vala:763: Description: Select the scan mode
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (3)
[+18.55s] DEBUG: scanner.vala:760: Option 3: name='resolution' title='Scan
resolution' type=int size=4 unit=dpi values=[100, 150, 200, 300, 400, 600,
1200, 2400, 4800, 9600] cap=soft-select,soft-detect
[+18.55s] DEBUG: scanner.vala:763: Description: Sets the resolution of the
scanned image.
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (4)
[+18.55s] DEBUG: scanner.vala:760: Option 4: name='source' title='Scan source'
type=string size=64 values=["FlatBed", "Automatic Document Feeder(left
aligned)", "Automatic Document Feeder(centrally aligned)"]
cap=soft-select,soft-detect
[+18.55s] DEBUG: scanner.vala:763: Description: Selects the scan source (such
as a document-feeder).
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (5)
[+18.55s] DEBUG: scanner.vala:760: Option 5: name='brightness'
title='Brightness' type=fixed size=4 unit=percent min=-50.00,
max=50.00, quant=65536 cap=soft-select,soft-detect,inactive
[+18.55s] DEBUG: scanner.vala:763: Description: Controls the brightness of
the acquired image.
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (6)
[+18.55s] DEBUG: scanner.vala:760: Option 6: name='contrast' title='Contrast'
type=fixed size=4 unit=percent min=-50.00, max=50.00, quant=65536
cap=soft-select,soft-detect,inactive
[+18.55s] DEBUG: scanner.vala:763: Description: Controls the contrast of the
acquired image.
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (7)
[+18.55s] DEBUG: scanner.vala:760: Option 7: name='(null)' title='Geometry'
type=group size=4 cap=advanced
[+18.55s] DEBUG: scanner.vala:763: Description:
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (8)
[+18.55s] DEBUG: scanner.vala:760: Option 8: name='tl-x' title='Top-left x'
type=fixed size=4 unit=mm min=0.00, max=211.84, quant=6553
cap=soft-select,soft-detect
[+18.55s] DEBUG: scanner.vala:763: Description: Top-left x position of scan
area.
[+18.55s] DEBUG: scanner.vala:910: sane_get_option_descriptor (9)
[+18.55s] DEBUG: scanner.vala:760: Option 9: name='tl-y'
[Desktop-packages] [Bug 1933717] Re: Backup messages in wrong language
** Changed in: deja-dup (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1933717 Title: Backup messages in wrong language Status in deja-dup package in Ubuntu: Fix Released Bug description: My system is set to use UK English, and has never used German. When a backup completes I get the mixed language message: Backup Finished Aber nicht alle Dateien wurden erfolgreich gesichert See the attached screenshot. Ubuntu 21.04 Deja dup version 42.7 $ dconf dump /org/gnome/deja-dup/ [/] backend='google' delete-after=182 last-backup='2021-06-26T10:00:30Z' last-run='2021-06-26T09:12:53Z' nag-check='2021-06-16T10:40:36Z' periodic=true periodic-period=1 prompt-check='disabled' [file] migrated=true [gcs] folder='anthony-System-Product-Name' [goa] type='google' [google] folder='Ubuntu-backups' [local] folder='anthony-System-Product-Name' [openstack] container='anthony-System-Product-Name' [rackspace] container='anthony-System-Product-Name' [remote] folder='anthony-System-Product-Name' [s3] folder='anthony-System-Product-Name' $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1933717/+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 1778638] Re: duplicity stuck in splice() call on Bionic
** Changed in: deja-dup (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1778638 Title: duplicity stuck in splice() call on Bionic Status in Duplicity: Fix Released Status in deja-dup package in Ubuntu: Fix Released Bug description: I am using Duplicity through Deja-Dup through its deja-dup-monitor process. After update to Bionic, it has basically stopped doing backups. Version is duplicity 0.7.17+bzr1357, Python version is 2.7.15rc1, Xubuntu Bionic. It seems to be stuck in pipes related call. When I try to strace the process I get this: strace: Process 28490 attached splice(9, [359], 16, NULL, 1048576, SPLICE_F_MORE From handle 9 to 16. The handle 9 is a file on my CIFS mount to where I do backups. If I go to the directory and do ls it works fine: duplicity 28490 USER9r REG 0,52 359 67128742 /var/backups/USER/backup.HOST/duplicity- inc.20180611T014226Z.to.20180612T014125Z.manifest.gpg Handle 16 is a pipe: duplicity 28490 USER 16w FIFO 0,12 0t0 1415081 pipe Its other end is handle 13, I think: duplicity 28490 USER 13r FIFO 0,12 0t0 1415081 pipe But I do not see anyone reading from it. That sounds like the issue. It seems to be stuck in GIO file handling code: (gdb) bt #0 0x7f0e78588dda in splice (fd_in=9, off_in=0x7ffe5e958388, fd_out=16, off_out=0x0, len=1048576, flags=4) at ../sysdeps/unix/sysv/linux/splice.c:26 #1 0x7f0e6ee2672e in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #2 0x7f0e6ee2d827 in g_file_copy () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #3 0x7f0e76ccfdae in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #4 0x7f0e76ccf71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #5 0x7f0e6fb8ecfa in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so #6 0x7f0e6fb908e8 in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so #7 0x7f0e6fb84c39 in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so #8 0x5560917a1f60 in PyEval_EvalFrameEx () I have already tried to restart it and it got stuck like this again the next backup cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1778638/+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 1973816] Re: Deja Dup's Google support will break in September 2022 for versions < 43.3
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355 ** Bug watch added: Debian Bug tracker #1011355 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355 ** Also affects: deja-dup (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1973816 Title: Deja Dup's Google support will break in September 2022 for versions < 43.3 Status in deja-dup package in Ubuntu: Fix Released Status in deja-dup package in Debian: Unknown Bug description: * Impact The method Deja-Dup is using to authentificate to google account will stop working in september. * Test case Configure deja-dup to do backups on a google drive account. After confirming the authorization through the web browser it should be possible to start the backup. Check on the webview that the files are correctly added. Restore some data and unsure that's working. * Regression potential The codepath is used for oauth authentification and integration with the system mimetype. Check that the webbrowser auth workflow works as expected, testing deb and snap based browsers -- Hello! I'm the maintainer of Deja Dup. I was recently made aware that Google is removing an oauth workflow that Deja Dup uses, in September. Here's their blog post about it: https://developers.googleblog.com/2022/02/making-oauth-flows- safer.html Here's the upstream bug about switching to a new oauth flow: https://gitlab.gnome.org/World/deja-dup/-/issues/222 I've released version 43.3 with a new oauth workflow. This basically switches us from redirecting the oauth page to a local http://localhost:/ page being served by deja-dup and instead has the browser launch a custom URI like 'com.googlecontent.xxx:/oauth2redirect?code=yyy', which then launches deja-dup and gives it the correct oauth token. The key differences for packagers is just to note that now deja-dup will register itself as a handler for those weird URI schemes (they are specific to deja-dup, as they include its client ids for the service). I think this deserves a backport to all supported releases. I can whip up a patch for you in a bit, just wanted to get this registered as an issue. To be a bit more specific about what will break: - Existing users that have already granted deja-dup access to Google will continue to work without any issue. - In August, users will see a warning on the oauth screen. - And then in September, any new attempt to connect deja-dup to Google will not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1973816/+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 1973816] Re: Deja Dup's Google support will break in September 2022 for versions < 43.3
Looks like Debian stable is using 42.7 right now - should I file a bug on the Debian side to track that too? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1973816 Title: Deja Dup's Google support will break in September 2022 for versions < 43.3 Status in deja-dup package in Ubuntu: Fix Released Bug description: * Impact The method Deja-Dup is using to authentificate to google account will stop working in september. * Test case Configure deja-dup to do backups on a google drive account. After confirming the authorization through the web browser it should be possible to start the backup. Check on the webview that the files are correctly added. Restore some data and unsure that's working. * Regression potential The codepath is used for oauth authentification and integration with the system mimetype. Check that the webbrowser auth workflow works as expected, testing deb and snap based browsers -- Hello! I'm the maintainer of Deja Dup. I was recently made aware that Google is removing an oauth workflow that Deja Dup uses, in September. Here's their blog post about it: https://developers.googleblog.com/2022/02/making-oauth-flows- safer.html Here's the upstream bug about switching to a new oauth flow: https://gitlab.gnome.org/World/deja-dup/-/issues/222 I've released version 43.3 with a new oauth workflow. This basically switches us from redirecting the oauth page to a local http://localhost:/ page being served by deja-dup and instead has the browser launch a custom URI like 'com.googlecontent.xxx:/oauth2redirect?code=yyy', which then launches deja-dup and gives it the correct oauth token. The key differences for packagers is just to note that now deja-dup will register itself as a handler for those weird URI schemes (they are specific to deja-dup, as they include its client ids for the service). I think this deserves a backport to all supported releases. I can whip up a patch for you in a bit, just wanted to get this registered as an issue. To be a bit more specific about what will break: - Existing users that have already granted deja-dup access to Google will continue to work without any issue. - In August, users will see a warning on the oauth screen. - And then in September, any new attempt to connect deja-dup to Google will not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1973816/+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 1973816] Re: Deja Dup's Google support will break in September 2022 for versions < 43.3
OK, I've made a little wiki page about this issue for distro maintainers (no real new information, but it does have links to patches at the bottom). The patches should cover all affected versions that Ubuntu supports (40.7, 42.8, and 42.9). https://wiki.gnome.org/Apps/DejaDup/GoogleAuthChange2022 (hmm, how do I make that a link?) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1973816 Title: Deja Dup's Google support will break in September 2022 for versions < 43.3 Status in deja-dup package in Ubuntu: Triaged Bug description: Hello! I'm the maintainer of Deja Dup. I was recently made aware that Google is removing an oauth workflow that Deja Dup uses, in September. Here's their blog post about it: https://developers.googleblog.com/2022/02/making-oauth-flows- safer.html Here's the upstream bug about switching to a new oauth flow: https://gitlab.gnome.org/World/deja-dup/-/issues/222 I've released version 43.3 with a new oauth workflow. This basically switches us from redirecting the oauth page to a local http://localhost:/ page being served by deja-dup and instead has the browser launch a custom URI like 'com.googlecontent.xxx:/oauth2redirect?code=yyy', which then launches deja-dup and gives it the correct oauth token. The key differences for packagers is just to note that now deja-dup will register itself as a handler for those weird URI schemes (they are specific to deja-dup, as they include its client ids for the service). I think this deserves a backport to all supported releases. I can whip up a patch for you in a bit, just wanted to get this registered as an issue. To be a bit more specific about what will break: - Existing users that have already granted deja-dup access to Google will continue to work without any issue. - In August, users will see a warning on the oauth screen. - And then in September, any new attempt to connect deja-dup to Google will not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1973816/+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 1973816] [NEW] Deja Dup's Google support will break in September 2022 for versions < 43.3
Public bug reported: Hello! I'm the maintainer of Deja Dup. I was recently made aware that Google is removing an oauth workflow that Deja Dup uses, in September. Here's their blog post about it: https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html Here's the upstream bug about switching to a new oauth flow: https://gitlab.gnome.org/World/deja-dup/-/issues/222 I've released version 43.3 with a new oauth workflow. This basically switches us from redirecting the oauth page to a local http://localhost:/ page being served by deja-dup and instead has the browser launch a custom URI like 'com.googlecontent.xxx:/oauth2redirect?code=yyy', which then launches deja-dup and gives it the correct oauth token. The key differences for packagers is just to note that now deja-dup will register itself as a handler for those weird URI schemes (they are specific to deja-dup, as they include its client ids for the service). I think this deserves a backport to all supported releases. I can whip up a patch for you in a bit, just wanted to get this registered as an issue. To be a bit more specific about what will break: - Existing users that have already granted deja-dup access to Google will continue to work without any issue. - In August, users will see a warning on the oauth screen. - And then in September, any new attempt to connect deja-dup to Google will not work. ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1973816 Title: Deja Dup's Google support will break in September 2022 for versions < 43.3 Status in deja-dup package in Ubuntu: New Bug description: Hello! I'm the maintainer of Deja Dup. I was recently made aware that Google is removing an oauth workflow that Deja Dup uses, in September. Here's their blog post about it: https://developers.googleblog.com/2022/02/making-oauth-flows- safer.html Here's the upstream bug about switching to a new oauth flow: https://gitlab.gnome.org/World/deja-dup/-/issues/222 I've released version 43.3 with a new oauth workflow. This basically switches us from redirecting the oauth page to a local http://localhost:/ page being served by deja-dup and instead has the browser launch a custom URI like 'com.googlecontent.xxx:/oauth2redirect?code=yyy', which then launches deja-dup and gives it the correct oauth token. The key differences for packagers is just to note that now deja-dup will register itself as a handler for those weird URI schemes (they are specific to deja-dup, as they include its client ids for the service). I think this deserves a backport to all supported releases. I can whip up a patch for you in a bit, just wanted to get this registered as an issue. To be a bit more specific about what will break: - Existing users that have already granted deja-dup access to Google will continue to work without any issue. - In August, users will see a warning on the oauth screen. - And then in September, any new attempt to connect deja-dup to Google will not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1973816/+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 1944113]
*** Bug 148765 has been marked as a duplicate of this bug. *** -- 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/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
** Changed in: wpa (Ubuntu Jammy) Status: Fix Committed => 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/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Released Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Hi @Sebastien, no problem at all. I will create a new bug report once I'm sure I've tried everything on my side. Have a lovely day. -- 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/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Hi, I've tested the proposed package by only upgrading to wpa_supplicant 2:2.10-6ubuntu1 and no other proposed packages. After rebooting I'm still not able to connect to our enterprise network. We are also using MSCHAPv2 + PEAP + No CA Cert for authentication. Live Boot of 20.04 can connect fine. Let me know if I can provide any more information. Thank you. -- 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/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Committed Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1971995] [NEW] error de imagen el cheese, aparecen lineas grises y verdes
Public bug reported: error en la imagen, en cheese, subo prueba de como aparece ubuntu 22.04 lts ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 6 09:29:41 2022 InstallationDate: Installed on 2022-05-05 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP 245 G7 Notebook PC ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 15.62 dmi.bios.vendor: AMI dmi.bios.version: F.62 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8796 dmi.board.vendor: HP dmi.board.version: 84.49 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 84.49 dmi.modalias: dmi:bvnAMI:bvrF.62:bd04/23/2021:br15.62:efr84.49:svnHP:pnHP245G7NotebookPC:pvr:rvnHP:rn8796:rvr84.49:cvnHP:ct10:cvrChassisVersion:sku1X5V7LT#ABM: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 245 G7 Notebook PC dmi.product.sku: 1X5V7LT#ABM dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 003: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 002: ID 10c4:8108 Silicon Labs USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ** Affects: cheese (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gstreamer-ok jammy wayland-session ** Attachment added: "prueba" https://bugs.launchpad.net/bugs/1971995/+attachment/5587383/+files/Captura%20desde%202022-05-06%2009-36-43.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1971995 Title: error de imagen el cheese, aparecen lineas grises y verdes Status in cheese package in Ubuntu: New Bug description: error en la imagen, en cheese, subo prueba de como aparece ubuntu 22.04 lts ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 6 09:29:41 2022 InstallationDate: Installed on 2022-05-05 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP 245 G7 Notebook PC ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 15.62 dmi.bios.vendor: AMI dmi.bios.version: F.62 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8796 dmi.board.vendor: HP dmi.board.version: 84.49 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 84.49 dmi.modalias: dmi:bvnAMI:bvrF.62:bd04/23/2021:br15.62:efr84.49:svnHP:pnHP245G7NotebookPC:pvr:rvnHP:rn8796:rvr84.49:cvnHP:ct10:cvrChassisVersion:sku1X5V7LT#ABM: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 245 G7 Notebook PC dmi.product.sku: 1X5V7LT#ABM dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 003: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 002: ID 10c4:8108 Silicon Labs USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1971995/+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 1971632] Re: Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect; pulseautio crashes every time
Igor Kovalenko managed to identify the problem, and and fixed it. See https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1354 for details. ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1354 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1971632 Title: Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect; pulseautio crashes every time Status in pulseaudio package in Ubuntu: New Bug description: On a fresh install of Kubuntu 22.04, when I turn my properly paired bluetooth headphones on they automatically connect to the system, then immediately disconnect again. The headphones thus have to be manually 're-connected' every time. Best as I understand it from the logs (appended below), pulseaudio showing up killed just after the headphones turn up as an unregistered sender ... 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE ... is responsible for the observed problem, i.e. the disconnect, probably triggered when pulseaudio restarts ... 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. So it seems either an internal pulseaudio problem, or a problem triggered by the division by 0 in the bluetooth module ... 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] or some combination of the two ... but again, I'm only guessing here. ___ System Logs after switching headphones on: 4/30/22 7:33 PM kernel input: Nat's Flex (AVRCP) as /devices/virtual/input/input31 4/30/22 7:33 PM systemd-logind Watching system buttons on /dev/input/event19 (Nat's Flex (AVRCP)) 4/30/22 7:33 PM bluetoothd /org/bluez/hci0/dev_A8_91_3D_DF_A8_F4/fd3: fd(43) ready 4/30/22 7:33 PM rtkit-daemonSupervising 0 threads of 0 processes of 0 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8884 of process 3426 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Failed with result 'signal'. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM acpid input device has been disconnected, fd 20 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. 4/30/22 7:33 PM systemd Stopped Sound Service. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM systemd Starting Sound Service... 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8889 of process 8889 owned by '1000' high priority at nice level -11. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM pulseaudio Stale PID file, overwriting. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8890 of process 8889 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 2 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSupervising 2 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8891 of
[Desktop-packages] [Bug 1971632] [NEW] Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect; pulseautio crashes every time
Public bug reported: On a fresh install of Kubuntu 22.04, when I turn my properly paired bluetooth headphones on they automatically connect to the system, then immediately disconnect again. The headphones thus have to be manually 're-connected' every time. Best as I understand it from the logs (appended below), pulseaudio showing up killed just after the headphones turn up as an unregistered sender ... 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE ... is responsible for the observed problem, i.e. the disconnect, probably triggered when pulseaudio restarts ... 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. So it seems either an internal pulseaudio problem, or a problem triggered by the division by 0 in the bluetooth module ... 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] or some combination of the two ... but again, I'm only guessing here. ___ System Logs after switching headphones on: 4/30/22 7:33 PM kernel input: Nat's Flex (AVRCP) as /devices/virtual/input/input31 4/30/22 7:33 PM systemd-logind Watching system buttons on /dev/input/event19 (Nat's Flex (AVRCP)) 4/30/22 7:33 PM bluetoothd /org/bluez/hci0/dev_A8_91_3D_DF_A8_F4/fd3: fd(43) ready 4/30/22 7:33 PM rtkit-daemonSupervising 0 threads of 0 processes of 0 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8884 of process 3426 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Failed with result 'signal'. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM acpid input device has been disconnected, fd 20 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. 4/30/22 7:33 PM systemd Stopped Sound Service. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM systemd Starting Sound Service... 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8889 of process 8889 owned by '1000' high priority at nice level -11. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM pulseaudio Stale PID file, overwriting. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8890 of process 8889 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 2 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSupervising 2 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8891 of process 8889 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 3 threads of 1 processes of 1 users. 4/30/22 7:33 PM systemd Started Sound Service. 4/30/22 7:33 PM pulseaudio Could not find org.bluez.BatteryProviderManager1.RegisterBatteryProvider(), is bluetoothd started with experimental features enabled (-E flag)? 4/30/22 7:33 PM bluetoothd Endpoint registered: sender=:1.246 path=/MediaEndpoint/A2DPSink/sbc 4/30/22 7:33 PM bluetoothd Endpoint registered: sender=:1.246 path=/MediaEndpoint/A2DPSource/sbc 4/30/22 7:33 PM bluetoothd Endpoint registered: sender=:1.246 path=/MediaEndpoint/A2DPSink/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint registered: sender=:1.246 path=/MediaEndpoint/A2DPSource/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint registered: sender=:1.246 path=/MediaEndpoint/A2DPSink/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint registered: sender=:1.246
[Desktop-packages] [Bug 1962593] Re: SMB Mount to backup directory prevents mounting parent directories of share
Deja Dup could maybe be smarter in the specific case of SMB mounts and only try to mount the root folder... If you switch your settings from: Network Location: smb://1.2.3.4/backup/UbuntuBackup Folder: MyMachineBackup to: Network Location: smb://1.2.3.4/backup Folder: UbuntuBackup/MyMachineBackup do things work like you expect? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1962593 Title: SMB Mount to backup directory prevents mounting parent directories of share Status in Déjà Dup: New Status in Duplicity: New Status in deja-dup package in Ubuntu: Triaged Bug description: May also apply to the "duplicity" package and is related to network "mount"s: To reproduce: * Set up a writeable SMB share: smb://1.2.3.4/backup * Create a subdir: smb://1.2.3.4/backup/UbuntuBackup * Using "deja-dup" -> "Storage location" set: Storage location: Network Server Network Location: smb://1.2.3.4/backup/UbuntuBackup Folder: MyMachineBackup * REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup") * Select "deja-dup" -> "Overview" -> "Back Up Now..." * Allow the backup to start, but not finish * Go to Nautilus (file browser) -> "+ Other Locations" - At the bottom set "Connect to server" to: smb://1.2.3.4/backup Result: * The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because the "UbuntuBackup" subdir is currently mounted * Can happen at semi-random times if the backup is on a schedule * This is especially a problem when backing up remotely over a VPN which can take a long time * Prevents access to all parent folders of the backup folder * Nautilus will hang, unable to mount the "backup" parent directory * Also a problem if the "smb://1.2.3.4/backup" folder is bookmarked in nautilus * This problem is persistent throughout backup process and for a period of time afterwards until the mount to "UbuntuBackup" times out or the backup process exits Possible solutions: * Add a configuration option to deja-dup/duplicity to specify the "Share root" and mount that first before accessing the configured "Network Location" * Have deja-dup or duplicity attempt to mount the parent directory/directories first by starting at the root of the SMB share and walking down the directory tree until a successful mount is made. In the above example, start by attempting to mount "smb://1.2.3.4/backup" first and then "smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder structures, try each one successively) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 08:51:47 2022 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2021-09-13 (168 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1962593/+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 1970124] Re: duplicity backup fails with obscure error message Ubuntu 22.04
I think that /tmp filename is a file that duplicity proceeds to throw
away. It copies files there, tries to unpack them, then cleans up after
itself (regardless of success). So that error message would be a lot
more useful if it indicated what the actual source file it had copied
from the storage location was named (like duplicity-vol1.gz or
whatever).
The error message makes it sound like the file it is trying to unpack is
corrupted. It's possible that a backup file got interrupted/cutoff
during writing/transfer?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1970124
Title:
duplicity backup fails with obscure error message Ubuntu 22.04
Status in duplicity package in Ubuntu:
New
Bug description:
I try to do a backup onto a network location (ssh://192.168.1.61 - I
can successfully connect to this location via ssh). The backup
completes the scan phase, then dies with error messages like this:
Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2:
(, EOFError('Compressed file ended before the end-
of-stream marker was reached'), )
While the backup is running, we can see a duplicity* directory under
/tmp:
$ ll /tmp/duplicity-i6olpr17-tempdir/
total 16
drwx-- 2 scohen scohen 4096 Apr 24 12:52 ./
drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../
-rw--- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1
However, note that this is not the directory mentioned in the failure
message.
A scan of the directory after the failure reveals no files like
/tmp/dupl*
Why is it trying to read files that do not exist?
$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
$ apt-cache policy duplicity
duplicity:
Installed: 0.8.21-1build1
Candidate: 0.8.21-1build1
Version table:
*** 0.8.21-1build1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1970124/+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 1970060] [NEW] Firefox Snap Element Desktop URL Handler not working
Public bug reported: Summary: The Firefox snap version seems to be unable to open application URIs. Steps to reproduce the issue: - Have Element Desktop installed https://element.io/get-started - Go to https://matrix.to/#/#element-dev:matrix.org - Select Element Desktop - Click Continue Expected: - Element opens the room What happens: - Can only select „System Handler“ - Confirming to use „System Handler“ does nothing OS version: Ubuntu 22.04 LTS Snap version: 99.0.1-1 Workaround: Remove the snap version; install from Mozilla PPA ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1970060 Title: Firefox Snap Element Desktop URL Handler not working Status in firefox package in Ubuntu: New Bug description: Summary: The Firefox snap version seems to be unable to open application URIs. Steps to reproduce the issue: - Have Element Desktop installed https://element.io/get-started - Go to https://matrix.to/#/#element-dev:matrix.org - Select Element Desktop - Click Continue Expected: - Element opens the room What happens: - Can only select „System Handler“ - Confirming to use „System Handler“ does nothing OS version: Ubuntu 22.04 LTS Snap version: 99.0.1-1 Workaround: Remove the snap version; install from Mozilla PPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1970060/+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 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time
Fixed 2 days ago in updated gdm package. -- 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/1969121 Title: System fallback to gdm login screen when hot-plugging a external monitor in 1st time Status in OEM Priority Project: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: [Steps to reproduce] 1. Install Jammy daily build 2. dist-upgrade to verify https://bugs.launchpad.net/mutter/+bug/1964037 3. reboot with no attach monitor 4. attach monitor after booting [Expect result] external monitor works directly [Actual result] system go back to gdm login screen [Additional information] 1. the external port is connecting to dGPU. 2. happens on wayland only 3. Only back to login screen in 1st attach, 2nd, 3rd, etc.. works good ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 21:22:47 2022 InstallationDate: Installed on 2022-04-13 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969121/+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 1944113]
*** Bug 148562 has been marked as a duplicate of this bug. *** -- 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/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
This bug has returned on Ubuntu 22.04 Workaround: rm -r ~/.config/pulse; pulseaudio -k -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] Selected audio output device in Settings is ignored after upgrading to Ubuntu 20.04. [Test Case] Start with an older version of Ubuntu like 19.04 or 19.10 and upgrade to 20.04. When done, attempt to connect a Bluetooth or USB audio device and use it via Settings. [Regression Potential] Unknown/low. The fix is from upstream and has already been released to Ubuntu 20.10 without any problems. Only worth noting it works by detecting and removing audio configurations made via older versions of PulseAudio. So upon upgrading some old settings may be reset to defaults, but the idea is that's less bad than audio devices being unusable (this bug). [Original Bug Report] Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+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
