[Desktop-packages] [Bug 1992688] Re: firefox deb not installed
The favourite icon in the shell isn't part of the firefox package, but the /usr/bin/firefox wrapper script has some logic to rewrite the favourite entry from "firefox.desktop" (deb package) to "firefox_firefox.desktop" (snap). So for dist upgrades, this is important (if the deb is removed, the icon disappears because the shell cannot locate "firefox.desktop", so it hides the favourite entry). The deb also sets up dpkg alternatives for x-www-browser and gnome-www- browser, which snaps currently cannot do (see https://forum.snapcraft.io/t/firefox-snap-cannot-be-set-as-default- browser/26636). -- 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/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: New 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 1991659] Re: crash open folder raccourci
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Opinion -- 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/1991659 Title: crash open folder raccourci Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Opinion Bug description: Hello. When I want to open via my dock any folder "Videos, Downloads, Photos" etc... I have the folder that closes itself instead of opening as requested. (Right click of the mouse and I select any folder). This only happens when a folder is already open (since the menu changes if no folder is open). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-02 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Tags: wayland-session jammy Uname: Linux 5.15.0-50-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/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1991659/+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 1991659] Re: Nautilus crashes when Ubuntu Dock shortcut selected
*** This bug is a duplicate of bug 1961472 *** https://bugs.launchpad.net/bugs/1961472 Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Summary changed: - crash open folder raccourci + Nautilus crashes when Ubuntu Dock shortcut selected ** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => nautilus (Ubuntu) ** Changed in: nautilus (Ubuntu) Status: Opinion => Incomplete ** Summary changed: - Nautilus crashes when Ubuntu Dock shortcut selected + Nautilus crashes when Ubuntu Dock right-click shortcut selected ** Changed in: nautilus (Ubuntu) Status: Incomplete => Confirmed -- 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/1991659 Title: Nautilus crashes when Ubuntu Dock right-click shortcut selected Status in nautilus package in Ubuntu: Confirmed Bug description: Hello. When I want to open via my dock any folder "Videos, Downloads, Photos" etc... I have the folder that closes itself instead of opening as requested. (Right click of the mouse and I select any folder). This only happens when a folder is already open (since the menu changes if no folder is open). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-02 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Tags: wayland-session jammy Uname: Linux 5.15.0-50-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/ubuntu/+source/nautilus/+bug/1991659/+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 1991659] Re: Nautilus crashes when Ubuntu Dock right-click shortcut selected
*** This bug is a duplicate of bug 1961472 *** https://bugs.launchpad.net/bugs/1961472 I reproduced the crash and found it was bug 1961472. ** This bug has been marked a duplicate of bug 1961472 nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() -- 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/1991659 Title: Nautilus crashes when Ubuntu Dock right-click shortcut selected Status in nautilus package in Ubuntu: Confirmed Bug description: Hello. When I want to open via my dock any folder "Videos, Downloads, Photos" etc... I have the folder that closes itself instead of opening as requested. (Right click of the mouse and I select any folder). This only happens when a folder is already open (since the menu changes if no folder is open). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-02 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Tags: wayland-session jammy Uname: Linux 5.15.0-50-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/ubuntu/+source/nautilus/+bug/1991659/+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 1961472] Re: nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()
More instructions to reproduce the crash are in bug 1991659. -- 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/1961472 Title: nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() Status in nautilus package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/b08214abbd45a512fd85cd586ff646af50a1e2bc --- Ubuntu 20.04 ha riscontrato un errore interno ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:41.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 11:50:21 2022 ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1643917917 GsettingsChanges: InstallationDate: Installed on 2022-02-10 (8 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcCwd: /home/computer ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=it_IT.UTF-8 SegvAnalysis: Segfault happened at: 0x7f7af91c055f:mov0x8(%rbp),%rax PC (0x7f7af91c055f) ok source "0x8(%rbp)" (0x5009c) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_display_error_trap_push () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_screen_supports_net_wm_hint () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: nautilus crashed with SIGSEGV in gdk_x11_display_error_trap_push() UpgradeStatus: Upgraded to jammy on 2022-02-10 (8 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince41.3-3 file-roller 3.40.0-4 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1961472/+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 1992590] [NEW] Reverting a previous zsys revert breaks the system: Failed to start Network Configuration
You have been subscribed to a public bug: I've created a virtual machine to assess if zsys is still safe to use in Ubuntu 22.04 LTS and I've tried to revert to a previous snapshot. So far so good, but once I try to revert the revert it gets unbootable: systemd loops between Starting Network Time Synchronization and Failed to start Network Configuration. Steps to reproduce the behavior: 1. Revert to a previous snapshot 2. Revert the revert 3. See error Expected behavior: Should revert the revert. It's basically a fresh install of Ubuntu 22.04 LTS done following this guide: https://openzfs.github.io/openzfs- docs/Getting%20Started/Ubuntu/Ubuntu%2022.04%20Root%20on%20ZFS.html# I've create a btrfs snapshot of the virtual machine image prior to attempting the revert, thus the issue is 100% reproducible on demand. I'll be able to keep the VM snapshot around for a couple of weeks before having to get rid of it to free up some space. In the meantime I'll be able to provide remote access to it if you desire so. Upstream issue: https://github.com/ubuntu/zsys/issues/236 ** Affects: zsys (Ubuntu) Importance: Undecided Status: New ** Tags: zsys -- Reverting a previous zsys revert breaks the system: Failed to start Network Configuration https://bugs.launchpad.net/bugs/1992590 You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. -- 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 1992590] Re: Reverting a previous zsys revert breaks the system: Failed to start Network Configuration
** Package changed: ubiquity (Ubuntu) => zsys (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1992590 Title: Reverting a previous zsys revert breaks the system: Failed to start Network Configuration Status in zsys package in Ubuntu: New Bug description: I've created a virtual machine to assess if zsys is still safe to use in Ubuntu 22.04 LTS and I've tried to revert to a previous snapshot. So far so good, but once I try to revert the revert it gets unbootable: systemd loops between Starting Network Time Synchronization and Failed to start Network Configuration. Steps to reproduce the behavior: 1. Revert to a previous snapshot 2. Revert the revert 3. See error Expected behavior: Should revert the revert. It's basically a fresh install of Ubuntu 22.04 LTS done following this guide: https://openzfs.github.io/openzfs- docs/Getting%20Started/Ubuntu/Ubuntu%2022.04%20Root%20on%20ZFS.html# I've create a btrfs snapshot of the virtual machine image prior to attempting the revert, thus the issue is 100% reproducible on demand. I'll be able to keep the VM snapshot around for a couple of weeks before having to get rid of it to free up some space. In the meantime I'll be able to provide remote access to it if you desire so. Upstream issue: https://github.com/ubuntu/zsys/issues/236 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1992590/+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 1961472] Re: nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()
The crash in my case seems to originate from unity-bookmarks-handler.c which is from nautilus patch debian/patches/12_unity_launcher_support.patch #5 0x7f5710b9be82 in gdk_x11_window_set_user_time (window=0x55dcabbf21c0, timestamp=timestamp@entry=1665045124) at x11/../../../../../gdk/x11/gdkwindow-x11.c:3633 #6 0x55dca9345e2d in activate_bookmark_by_quicklist (menu=, timestamp=1665045124, bookmark=) at ../src/unity-bookmarks-handler.c:62 I'm running Wayland so don't think X11 Window logic should be used anymore. I wonder if we can drop 12_unity_launcher_support.patch ? ** Changed in: nautilus (Ubuntu) Importance: Undecided => High ** Summary changed: - nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() + nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() if opened via Ubuntu Dock shortcuts ** Changed in: nautilus (Ubuntu) Status: Confirmed => Triaged ** Summary changed: - nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() if opened via Ubuntu Dock shortcuts + nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() when opened via Ubuntu Dock shortcuts -- 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/1961472 Title: nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() when opened via Ubuntu Dock shortcuts Status in nautilus package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/b08214abbd45a512fd85cd586ff646af50a1e2bc --- Ubuntu 20.04 ha riscontrato un errore interno ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:41.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 11:50:21 2022 ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1643917917 GsettingsChanges: InstallationDate: Installed on 2022-02-10 (8 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcCwd: /home/computer ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=it_IT.UTF-8 SegvAnalysis: Segfault happened at: 0x7f7af91c055f:mov0x8(%rbp),%rax PC (0x7f7af91c055f) ok source "0x8(%rbp)" (0x5009c) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_display_error_trap_push () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_screen_supports_net_wm_hint () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: nautilus crashed with SIGSEGV in gdk_x11_display_error_trap_push() UpgradeStatus: Upgraded to jammy on 2022-02-10 (8 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince41.3-3 file-roller 3.40.0-4 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1961472/+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 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
Indeed there are no crashes after version 42.x -- 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/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: Fix Released Status in gtk+3.0 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gtk/issues/2457 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+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 1992752] [NEW] The length of video is inconsistent with the actual when using Cheese to record video
Public bug reported: [steps reproduce] 1. Preload Ubuntu system 22.04.1 2. Lanuch Cheese to record video; 3. Found that the length of video is inconsistent with the actual recorded time. 4. It can pause when play the record video and play time exceeds record time. [failure rate] 100% [expected result] The video time should align with actual cost [actual result] The video play time exceeds record time [addtional infromation] CPU: Intel i5-12500H 2.5G Video: Intel® Iris® Xe Graphics Memory: 2x 8GB Storage: 512GB SSD ** Affects: oem-priority Importance: Undecided Status: New ** Affects: cheese (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1990246 sutton -- 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/1992752 Title: The length of video is inconsistent with the actual when using Cheese to record video Status in OEM Priority Project: New Status in cheese package in Ubuntu: New Bug description: [steps reproduce] 1. Preload Ubuntu system 22.04.1 2. Lanuch Cheese to record video; 3. Found that the length of video is inconsistent with the actual recorded time. 4. It can pause when play the record video and play time exceeds record time. [failure rate] 100% [expected result] The video time should align with actual cost [actual result] The video play time exceeds record time [addtional infromation] CPU: Intel i5-12500H 2.5G Video: Intel® Iris® Xe Graphics Memory: 2x 8GB Storage: 512GB SSD To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992752/+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 1992752] Re: The length of video is inconsistent with the actual when using Cheese to record video
** Attachment added: "cheese-video-length.png" https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1992752/+attachment/5623824/+files/cheese-video-length.png ** Tags added: oem-priority originate-from-1990246 sutton ** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #98 https://gitlab.gnome.org/GNOME/cheese/-/issues/98 ** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #79 https://gitlab.gnome.org/GNOME/cheese/-/issues/79 -- 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/1992752 Title: The length of video is inconsistent with the actual when using Cheese to record video Status in OEM Priority Project: New Status in cheese package in Ubuntu: New Bug description: [steps reproduce] 1. Preload Ubuntu system 22.04.1 2. Lanuch Cheese to record video; 3. Found that the length of video is inconsistent with the actual recorded time. 4. It can pause when play the record video and play time exceeds record time. [failure rate] 100% [expected result] The video time should align with actual cost [actual result] The video play time exceeds record time [addtional infromation] CPU: Intel i5-12500H 2.5G Video: Intel® Iris® Xe Graphics Memory: 2x 8GB Storage: 512GB SSD To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992752/+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 1992752] Re: The length of video is inconsistent with the actual when using Cheese to record video
Some upstream bugs might be related to this issue. https://askubuntu.com/questions/1392849/cheese-captures-long-corrupted- videos https://gitlab.gnome.org/GNOME/cheese/-/issues/98 https://gitlab.gnome.org/GNOME/cheese/-/issues/79 -- 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/1992752 Title: The length of video is inconsistent with the actual when using Cheese to record video Status in OEM Priority Project: New Status in cheese package in Ubuntu: New Bug description: [steps reproduce] 1. Preload Ubuntu system 22.04.1 2. Lanuch Cheese to record video; 3. Found that the length of video is inconsistent with the actual recorded time. 4. It can pause when play the record video and play time exceeds record time. [failure rate] 100% [expected result] The video time should align with actual cost [actual result] The video play time exceeds record time [addtional infromation] CPU: Intel i5-12500H 2.5G Video: Intel® Iris® Xe Graphics Memory: 2x 8GB Storage: 512GB SSD To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992752/+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 1991659] Re: Nautilus crashes when Ubuntu Dock right-click shortcut selected
*** This bug is a duplicate of bug 1934579 *** https://bugs.launchpad.net/bugs/1934579 ** This bug is no longer a duplicate of bug 1961472 nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() when opened via Ubuntu Dock shortcuts ** This bug has been marked a duplicate of bug 1934579 Nautilus crashes when opening places from the dock contextmenu -- 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/1991659 Title: Nautilus crashes when Ubuntu Dock right-click shortcut selected Status in nautilus package in Ubuntu: Confirmed Bug description: Hello. When I want to open via my dock any folder "Videos, Downloads, Photos" etc... I have the folder that closes itself instead of opening as requested. (Right click of the mouse and I select any folder). This only happens when a folder is already open (since the menu changes if no folder is open). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-02 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Tags: wayland-session jammy Uname: Linux 5.15.0-50-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/ubuntu/+source/nautilus/+bug/1991659/+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 1965567] Re: nautilus crashed with SIGSEGV
*** This bug is a duplicate of bug 1934579 *** https://bugs.launchpad.net/bugs/1934579 ** This bug is no longer a duplicate of bug 1961472 nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() when opened via Ubuntu Dock shortcuts ** This bug has been marked a duplicate of bug 1934579 Nautilus crashes when opening places from the dock contextmenu -- 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/1965567 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: New Bug description: Nautilus crashes when trying to open a second window from main menu ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:42~rc-1ubuntu1 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: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 18:33:50 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1260, 732)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'312' InstallationDate: Installed on 2021-12-29 (78 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=es_ES.UTF-8 SegvAnalysis: Segfault happened at: 0x7f753a74f52f:mov0x8(%rbp),%rax PC (0x7f753a74f52f) ok source "0x8(%rbp)" (0x5009c) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: () at /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_display_error_trap_push () at /lib/x86_64-linux-gnu/libgdk-3.so.0 () at /lib/x86_64-linux-gnu/libgdk-3.so.0 () at /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_screen_supports_net_wm_hint () at /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince42~rc-1 file-roller 3.41.90-1 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1965567/+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 1975525] Re: nautilus crashed with SIGSEGV in gdk_x11_display_error_trap_push()
*** This bug is a duplicate of bug 1934579 *** https://bugs.launchpad.net/bugs/1934579 ** This bug is no longer a duplicate of bug 1961472 nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() when opened via Ubuntu Dock shortcuts ** This bug has been marked a duplicate of bug 1934579 Nautilus crashes when opening places from the dock contextmenu -- 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/1975525 Title: nautilus crashed with SIGSEGV in gdk_x11_display_error_trap_push() Status in nautilus package in Ubuntu: New Bug description: Crashed while opening folders ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 23 21:35:40 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1131, 1005)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'209' InstallationDate: Installed on 2022-05-01 (22 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7fa3e503252f:mov0x8(%rbp),%rax PC (0x7fa3e503252f) ok source "0x8(%rbp)" (0x5009c) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_display_error_trap_push () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_screen_supports_net_wm_hint () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: nautilus crashed with SIGSEGV in gdk_x11_display_error_trap_push() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo mtime.conffile..etc.apport.crashdb.conf: 2022-05-17T00:40:19.420743 separator: usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1975525/+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 1961549] Re: /usr/bin/nautilus:11:delete_outdated_error_traps:gdk_x11_display_error_trap_push:get_net_supporting_wm_check:fetch_net_wm_check_window:gdk_x11_screen_supports_net_
*** This bug is a duplicate of bug 1934579 *** https://bugs.launchpad.net/bugs/1934579 ** This bug is no longer a duplicate of bug 1961472 nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() when opened via Ubuntu Dock shortcuts ** This bug has been marked a duplicate of bug 1934579 Nautilus crashes when opening places from the dock contextmenu -- 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/1961549 Title: /usr/bin/nautilus:11:delete_outdated_error_traps:gdk_x11_display_error_trap_push:get_net_supporting_wm_check:fetch_net_wm_check_window:gdk_x11_screen_supports_net_wm_hint Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:41.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/b08214abbd45a512fd85cd586ff646af50a1e2bc 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/ubuntu/+source/nautilus/+bug/1961549/+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 1961471] Re: executable path /usr/libexec/traker-exstract-3
*** This bug is a duplicate of bug 1934579 *** https://bugs.launchpad.net/bugs/1934579 ** This bug is no longer a duplicate of bug 1961472 nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() when opened via Ubuntu Dock shortcuts ** This bug has been marked a duplicate of bug 1934579 Nautilus crashes when opening places from the dock contextmenu -- 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/1961471 Title: executable path /usr/libexec/traker-exstract-3 Status in nautilus package in Ubuntu: New Bug description: Ubuntu 20.04 ha riscontrato un errore interno ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:41.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 11:50:21 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2022-02-10 (8 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=it_IT.UTF-8 SegvAnalysis: Segfault happened at: 0x7f7af91c055f:mov0x8(%rbp),%rax PC (0x7f7af91c055f) ok source "0x8(%rbp)" (0x5009c) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_display_error_trap_push () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_screen_supports_net_wm_hint () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: nautilus crashed with SIGSEGV in gdk_x11_display_error_trap_push() UpgradeStatus: Upgraded to jammy on 2022-02-10 (8 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince41.3-3 file-roller 3.40.0-4 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1961471/+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 1961472] Re: nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() when opened via Ubuntu Dock shortcuts
*** This bug is a duplicate of bug 1934579 *** https://bugs.launchpad.net/bugs/1934579 ** This bug has been marked a duplicate of bug 1934579 Nautilus crashes when opening places from the dock contextmenu -- 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/1961472 Title: nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() when opened via Ubuntu Dock shortcuts Status in nautilus package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/b08214abbd45a512fd85cd586ff646af50a1e2bc --- Ubuntu 20.04 ha riscontrato un errore interno ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:41.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 11:50:21 2022 ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1643917917 GsettingsChanges: InstallationDate: Installed on 2022-02-10 (8 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcCwd: /home/computer ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=it_IT.UTF-8 SegvAnalysis: Segfault happened at: 0x7f7af91c055f:mov0x8(%rbp),%rax PC (0x7f7af91c055f) ok source "0x8(%rbp)" (0x5009c) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_display_error_trap_push () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_screen_supports_net_wm_hint () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: nautilus crashed with SIGSEGV in gdk_x11_display_error_trap_push() UpgradeStatus: Upgraded to jammy on 2022-02-10 (8 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince41.3-3 file-roller 3.40.0-4 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1961472/+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 1961453] Re: ubuntu-dock crashes nautilus
*** This bug is a duplicate of bug 1934579 *** https://bugs.launchpad.net/bugs/1934579 ** This bug is no longer a duplicate of bug 1961472 nautilus crashed with SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push() when opened via Ubuntu Dock shortcuts ** This bug has been marked a duplicate of bug 1934579 Nautilus crashes when opening places from the dock contextmenu -- 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/1961453 Title: ubuntu-dock crashes nautilus Status in nautilus package in Ubuntu: Confirmed Bug description: Right-clicking on nautilus pinned to the dock displays nautilus bookmars shall at least one nautilus window is open. This is very convenient and is expected behaviour from Unity dock. Clicking on the bookmark however crashes nautilus with segmentation fault. Confirmed on Ubuntu 20.04 and 22.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 18 18:26:01 2022 InstallationDate: Installed on 2021-10-21 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to jammy on 2022-02-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1961453/+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 1992756] [NEW] Screen turns black for a long time after each login and when detecting screens or changing screen layout.
Public bug reported: I have a Thinkpad P15 with a A2000 GPU with Ubuntu 22.04.1 LTS. This happens using Wayland and nvidia cuda drivers. It seems like the system uses very long to identify the screens. This happens when I use external monitors, but also when only using the laptop screen. Changing the screen layout takes so long that I am unable to accept the change before it is reverted to the previous. Only the mouse pointer is visible, the rest of the screens are black during this process. $ apt-cache policy cuda cuda: Installed: 11.7.1-1 Candidate: 11.8.0-1 Version table: 11.8.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages *** 11.7.1-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages 100 /var/lib/dpkg/status 11.7.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages $ nvidia-smi Thu Oct 13 10:46:02 2022 +-+ | NVIDIA-SMI 515.65.01Driver Version: 515.65.01CUDA Version: 11.7 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA RTX A200... On | :01:00.0 On | N/A | | N/A 46CP5 8W / N/A |146MiB / 4096MiB | 22% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 4451 G /usr/lib/xorg/Xorg145MiB | +-+ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 13 10:25:17 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-05 (37 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "journalctl -b-0" https://bugs.launchpad.net/bugs/1992756/+attachment/5623831/+files/currentboot.txt -- 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/1992756 Title: Screen turns black for a long time after each login and when detecting screens or changing screen layout. Status in gnome-shell package in Ubuntu: New Bug description: I have a Thinkpad P15 with a A2000 GPU with Ubuntu 22.04.1 LTS. This happens using Wayland and nvidia cuda drivers. It seems like the system uses very long to identify the screens. This happens when I use external monitors, but also when only using the laptop screen. Changing the screen layout takes so long that I am unable to accept the change before it is reverted to the previous. Only the mouse pointer is visible, the rest of the screens are black during this process. $ apt-cache policy cuda cuda: Installed: 11.7.1-1 Candidate: 11.8.0-1 Version table: 11.8.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages *** 11.7.1-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages 100 /var/lib/dpkg/status 11.7.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages $ nvidia-smi Thu Oct 13 10:46:02 2022 +-+
[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock contextmenu
Tracking in: https://errors.ubuntu.com/problem/b08214abbd45a512fd85cd586ff646af50a1e2bc Steps to reproduce also mentioned in: bug 1961453 and bug 1991659. The crash in my case seems to originate from unity-bookmarks-handler.c which is from nautilus patch debian/patches/12_unity_launcher_support.patch #5 0x7f5710b9be82 in gdk_x11_window_set_user_time (window=0x55dcabbf21c0, timestamp=timestamp@entry=1665045124) at x11/../../../../../gdk/x11/gdkwindow-x11.c:3633 #6 0x55dca9345e2d in activate_bookmark_by_quicklist (menu=, timestamp=1665045124, bookmark=) at ../src/unity- bookmarks-handler.c:62 I'm running Wayland so don't think X11 Window logic should be used anymore. I wonder if we can drop 12_unity_launcher_support.patch ? ** Changed in: nautilus (Ubuntu) Status: Confirmed => Triaged ** Tags removed: hirsute ** Tags added: jammy ** Summary changed: - Nautilus crashes when opening places from the dock contextmenu + Nautilus crashes when opening places from the dock context menu [SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()] -- 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/1934579 Title: Nautilus crashes when opening places from the dock context menu [SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()] Status in nautilus package in Ubuntu: Triaged Bug description: After updating to Ubuntu 21.04, Nautilus crashes every time I try to open a second folder by right-clicking on the Nautilus icon in the "Favorites" left sidebar (i.e., launch panel) and selecting a bookmarked "Places" folder. Normally, this would open a second Nautilus window for the selected folder, but instead, any open Nautilus windows disappear and no window opens for the selected folder. In other words, Nautilus crashes. This did not occur on Ubuntu 20.10. This AskUbuntu post describes the same issue: https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying- to-open-another-window-by-right-clicking-the-nautil If, instead, I right-click the Nautilus icon, select "New Window" and then select the desired "Places" folder from the left sidebar of the newly opened window, Nautilus does not crash. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 4 13:36:13 2021 InstallationDate: Installed on 2020-02-05 (514 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579/+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 1992756] Re: Screen turns black for a long time after each login and when detecting screens or changing screen layout.
Thanks for the bug report. Please collect a log from when the bug is happening by: 1. Open a Terminal window and run: lspci -k > lspci.txt journalctl -f > recentjournal.txt Leave it running. 2. Reproduce the bug. 3. Press Ctrl+C in the Terminal window. 4. Attach the two resulting text files here. ** Tags added: hybrid i915 multigpu nvidia ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Also affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: New => Incomplete -- 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/1992756 Title: Screen turns black for a long time after each login and when detecting screens or changing screen layout. Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-515 package in Ubuntu: Incomplete Bug description: I have a Thinkpad P15 with a A2000 GPU with Ubuntu 22.04.1 LTS. This happens using Wayland and nvidia cuda drivers. It seems like the system uses very long to identify the screens. This happens when I use external monitors, but also when only using the laptop screen. Changing the screen layout takes so long that I am unable to accept the change before it is reverted to the previous. Only the mouse pointer is visible, the rest of the screens are black during this process. $ apt-cache policy cuda cuda: Installed: 11.7.1-1 Candidate: 11.8.0-1 Version table: 11.8.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages *** 11.7.1-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages 100 /var/lib/dpkg/status 11.7.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages $ nvidia-smi Thu Oct 13 10:46:02 2022 +-+ | NVIDIA-SMI 515.65.01Driver Version: 515.65.01CUDA Version: 11.7 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA RTX A200... On | :01:00.0 On | N/A | | N/A 46CP5 8W / N/A |146MiB / 4096MiB | 22% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 4451 G /usr/lib/xorg/Xorg145MiB | +-+ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 13 10:25:17 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-05 (37 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1992756/+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 1992756] Re: Screen turns black for a long time after each login and when detecting screens or changing screen layout.
I was wrong about using wayland. Like you can see from `nvidia-smi` I am using Xorg it seems. -- 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/1992756 Title: Screen turns black for a long time after each login and when detecting screens or changing screen layout. Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-515 package in Ubuntu: Incomplete Bug description: I have a Thinkpad P15 with a A2000 GPU with Ubuntu 22.04.1 LTS. This happens using Wayland and nvidia cuda drivers. It seems like the system uses very long to identify the screens. This happens when I use external monitors, but also when only using the laptop screen. Changing the screen layout takes so long that I am unable to accept the change before it is reverted to the previous. Only the mouse pointer is visible, the rest of the screens are black during this process. $ apt-cache policy cuda cuda: Installed: 11.7.1-1 Candidate: 11.8.0-1 Version table: 11.8.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages *** 11.7.1-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages 100 /var/lib/dpkg/status 11.7.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages $ nvidia-smi Thu Oct 13 10:46:02 2022 +-+ | NVIDIA-SMI 515.65.01Driver Version: 515.65.01CUDA Version: 11.7 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA RTX A200... On | :01:00.0 On | N/A | | N/A 46CP5 8W / N/A |146MiB / 4096MiB | 22% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 4451 G /usr/lib/xorg/Xorg145MiB | +-+ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 13 10:25:17 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-05 (37 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1992756/+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 1992667] Re: Application windows invisible (on DG2 graphics)
I've managed to reproduce this bug on an Arc A380 and Arc A770 GPU. I've attached the requested lspci output for the A770. Ubuntu 22.04 has already received a mesa update with backported patches for DG2 support: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1971712 I haven't tried 22.10 yet, but I will do so in the coming days. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+attachment/5623860/+files/lspci.txt -- 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/1992667 Title: Application windows invisible (on DG2 graphics) Status in linux-oem-6.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: When using GNOME Shell with Wayland, all application windows become invisible from time to time. This usually happens right after starting GNOME Shell for the first time or after having a VRAM intensive application open, such as a game. I have installed the latest linux-oem-6.0 kernel and manually enabled support for DG2 graphics by passing the i915.force_probe parameter with the PCIe ID of the graphics card. I have attached a screenshot of the described behavior below. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 17:23:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+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 1992756] Re: Screen turns black for a long time after each login and when detecting screens or changing screen layout.
Yes we know. Please follow the instructions in comment #2. -- 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/1992756 Title: Screen turns black for a long time after each login and when detecting screens or changing screen layout. Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-515 package in Ubuntu: Incomplete Bug description: I have a Thinkpad P15 with a A2000 GPU with Ubuntu 22.04.1 LTS. This happens using Wayland and nvidia cuda drivers. It seems like the system uses very long to identify the screens. This happens when I use external monitors, but also when only using the laptop screen. Changing the screen layout takes so long that I am unable to accept the change before it is reverted to the previous. Only the mouse pointer is visible, the rest of the screens are black during this process. $ apt-cache policy cuda cuda: Installed: 11.7.1-1 Candidate: 11.8.0-1 Version table: 11.8.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages *** 11.7.1-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages 100 /var/lib/dpkg/status 11.7.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages $ nvidia-smi Thu Oct 13 10:46:02 2022 +-+ | NVIDIA-SMI 515.65.01Driver Version: 515.65.01CUDA Version: 11.7 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA RTX A200... On | :01:00.0 On | N/A | | N/A 46CP5 8W / N/A |146MiB / 4096MiB | 22% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 4451 G /usr/lib/xorg/Xorg145MiB | +-+ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 13 10:25:17 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-05 (37 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1992756/+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 1971712] Re: Add support for Intel DG2
you need to use i915.force_probe until maybe 6.2, but other than that it works quite well for the most part even in 6.0 -- 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/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: In Progress Status in mesa source package in Jammy: Fix Released Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1969274] Re: openvpn client no longer connects in 22.04 until certificate update
I have a laptop and a desktop, both on kinetic now. I can connect the laptop to a VPN but not the desktop, both using the same config and keys etc. I get the same error as on the screenshot, and no idea how to get forward.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1969274 Title: openvpn client no longer connects in 22.04 until certificate update Status in network-manager-openvpn package in Ubuntu: New Bug description: Client no longer connects. previous version had no problem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openvpn 1.8.18-1 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 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 15:09:56 2022 InstallationDate: Installed on 2022-04-15 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1969274/+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 1992642] Re: Update freerdp2 to 2.8.1
This bug was fixed in the package freerdp2 - 2.8.1+dfsg1-0ubuntu1 --- freerdp2 (2.8.1+dfsg1-0ubuntu1) kinetic; urgency=medium * Sync with Debian. * New upstream bugfix release. (LP: #1992642) - Includes fixes for CVE-2022-39282 & CVE-2022-39282 * Drop patch: applied in new release freerdp2 (2.8.0+dfsg1-1) unstable; urgency=medium * New upstream version. (Closes: #1016491). * debian/control: + Bump Standards-Version: to 4.6.1. No changes needed. * debian/copyright: + Update auto-generated copyright.in file. + Update copyright attributions. * debian/patches: + Drop 1001_keep-symbol-DumpThreadHandles-if-debugging-is-disabled.patch. Similar solution applied upstream, but only partially, it seems. + Add 1001_amend-DumpThreadHandles-inclusion.patch. Amend missing adjustment in thread.h. * debian/*.symbols: + Update .symbols files for 2.8.0. -- Jeremy Bicha Wed, 12 Oct 2022 08:45:55 -0400 ** Changed in: freerdp2 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1992642 Title: Update freerdp2 to 2.8.1 Status in freerdp2 package in Ubuntu: Fix Released Bug description: Impact -- New bugfix release for 2.8 series https://github.com/FreeRDP/FreeRDP/releases/tag/2.8.1 This bug is only for the Kinetic upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1992642/+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 1992498] Re: Disable offline update feature
This bug was fixed in the package gnome-software - 43.0-1ubuntu1 --- gnome-software (43.0-1ubuntu1) kinetic; urgency=medium [ Nathan Pratta Teodosio ] * Add patch to disable apt updates (Closes: #787485) (LP: #1992498) -- Jeremy Bicha Tue, 11 Oct 2022 14:44:58 -0400 ** Changed in: gnome-software (Ubuntu) Status: In Progress => Fix Released -- 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/1992498 Title: Disable offline update feature Status in gnome-software package in Ubuntu: Fix Released Bug description: Impact -- The GNOME Software app has a feature to install updates when powering off the computer. (Screenshot attached.) This is unnecessary in Ubuntu since we already ask to restart when there are updates that we know need a restart to be applied. GNOME Software may also prevent installing updates except by restarting the computer which is frustrating to people who don't want to restart immediately. GNOME Software does not provide an option to turn this feature off. Years ago, Ubuntu's version of the GNOME Software .deb disabled this feature, but it was (unintentionally?) dropped when we resynced our packaging with Debian after switching the Ubuntu Store to be provided by a snap instead of a .deb. This issue affects Ubuntu Budgie and Xubuntu which ship the .deb version of GNOME Software. It also affects people who have uninstalled the snap and installed the .deb. This patch actually disables all apt updates. This is ok for Ubuntu because we use update-manager for apt updates and all non-KDE official desktop flavors depend on update-manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1992498/+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 1888495] Re: fprintd-verify fails with an USB UPEK reader
** No longer affects: libfprint (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1888495 Title: fprintd-verify fails with an USB UPEK reader Status in fprintd package in Ubuntu: Fix Released Status in fprintd source package in Focal: Fix Released Status in fprintd source package in Groovy: Won't Fix Bug description: [ Impact ] The fingerprint reader is an UPEK TCRE3C usb fingerprint reader. It was working fine with ubuntu 16.04 and 18.04. [ Test case ] With an UPEK fingerprint reader run: - fprintd-verify Verification should work properly [ Regression potential ] Fingers are not verified lsusb shows: 0483:2016 STMicroelectronics Fingerprint Reader user@xubuntu:~$ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 failed to claim device: Open failed with error: transfer timed out user@xubuntu:~$ fprintd-list user found 1 devices Device at /net/reactivated/Fprint/Device/0 Using device /net/reactivated/Fprint/Device/0 User user has no fingers enrolled for UPEK TouchStrip. This bug is probably the same as: https://bugzilla.redhat.com/show_bug.cgi?id=1832229 Related to bug #1881380 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1888495/+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 1992775] [NEW] gnome-session fails to build on kinetic
Public bug reported: gnome-session fails to build on kinetic because it tries to install gnome-session-custom-session. See https://bugs.debian.org/1013672 for more details. Basically, we don't enable the enable_session_selector build option and gnome-session now correctly doesn't install gnome-session-custom-session in that case. ** Affects: gnome-session (Ubuntu) Importance: High Status: In Progress ** Tags: ftbfs kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1992775 Title: gnome-session fails to build on kinetic Status in gnome-session package in Ubuntu: In Progress Bug description: gnome-session fails to build on kinetic because it tries to install gnome-session-custom-session. See https://bugs.debian.org/1013672 for more details. Basically, we don't enable the enable_session_selector build option and gnome- session now correctly doesn't install gnome-session-custom-session in that case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1992775/+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 1960336] Re: No login screen when fprintd crashes
*** This bug is a duplicate of bug 1962566 *** https://bugs.launchpad.net/bugs/1962566 This is currently fixed, see: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962566 ** This bug has been marked a duplicate of bug 1962566 gnome-shell crash after resume from suspend in gdm/util.js:154 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1960336 Title: No login screen when fprintd crashes Status in fprintd package in Ubuntu: Incomplete Status in gdm3 package in Ubuntu: New Bug description: After a recent update, when using gdm3 as login manager, there is no account visible and it is not possible to login. When switching to lightdm I can login but sleep is broken and some notifications do not work. Running the latest 22.04 dev branch with Wayland and Nvidia driver. Had to select kernel 5.12 to have display link working. This issue occurs with and without external displays attached. A recent attempt to switch back to gdm3 gave me just a black screen. I tried to reinstall gdm3 to no avail. This seems like a quite serious issue, hence this report for the dev version. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: lightdm DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-12-17 (784 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset wl nvidia Package: gnome-shell 41.3-1ubuntu1 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 41.3-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.12.19-051219-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1960336/+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 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental
policykit-1 121+compat0.1-5 is now in Debian Unstable. Could I get a clear answer from the Ubuntu Security Team if this is acceptable to autosync when Ubuntu 23.04 development opens? ** Tags added: block-proposed ** Summary changed: - [security review] Sync policykit-1 0.120-6 (main) from Debian experimental + [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable ** Description changed: - Please sync policykit-1 0.120-6 (main) from Debian experimental + Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable for + Ubuntu 23.04 Changelog entries since current kinetic version 0.105-33: - https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6 + https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. It appears the Debian maintainer is considering switching Debian to the updated version in time for the next Debian Stable release (so uploading to unstable later this year). - - My requested deadline is August 25, Ubuntu 22.10 Feature Freeze. ** Description changed: Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable for Ubuntu 23.04 Changelog entries since current kinetic version 0.105-33: https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. - - It appears the Debian maintainer is considering switching Debian to the - updated version in time for the next Debian Stable release (so uploading - to unstable later this year). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1972654 Title: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable Status in policykit-1 package in Ubuntu: Confirmed Bug description: Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable for Ubuntu 23.04 Changelog entries since current kinetic version 0.105-33: https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1992779] [NEW] With ubuntu 22.04, Manual PLMN scan via GUI shows Timeout
Public bug reported: Test steps: Boot the RVP Run the Modem Manager in debug mode Search the PLMN using "Scan" API & check results Disable Automatic Network in GUI Check the available networks in UI. Observation:- When we tried to do Scan through python framework it worked. When we tried to disable automatic network in GUI observed "timeout was reached" Expected result:- After disabling the automatic network in GUI we should get all the Networks available Note:- When tried to disable network two time initially response has come but later observed "timeout was reached" We analyzed from Host and Modem end, there is no issue observed. But issue observed in GUI. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot_fail_with_GUI.png" https://bugs.launchpad.net/bugs/1992779/+attachment/5623890/+files/Screenshot_fail_with_GUI.png -- 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/1992779 Title: With ubuntu 22.04, Manual PLMN scan via GUI shows Timeout Status in gnome-shell package in Ubuntu: New Bug description: Test steps: Boot the RVP Run the Modem Manager in debug mode Search the PLMN using "Scan" API & check results Disable Automatic Network in GUI Check the available networks in UI. Observation:- When we tried to do Scan through python framework it worked. When we tried to disable automatic network in GUI observed "timeout was reached" Expected result:- After disabling the automatic network in GUI we should get all the Networks available Note:- When tried to disable network two time initially response has come but later observed "timeout was reached" We analyzed from Host and Modem end, there is no issue observed. But issue observed in GUI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1992779/+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 1992683] Re: Update gnome-terminal to 3.46.2
This bug was fixed in the package gnome-terminal - 3.46.2-1ubuntu1 --- gnome-terminal (3.46.2-1ubuntu1) kinetic; urgency=medium * Merge with Debian. Remaining changes: + gnome-terminal.wrap, debian/rules: - Add a wrapper script to restore command line compatibility. + debian/control.in: - gnome-terminal depends on python3, python3-gi and gir1.2-glib-2.0 for the wrapper script. - add a build dependency on gettext to match the use of the i18n meson module + Add 0001-Restore-transparency.patch: - Restore transparency support + Add 0001-Add-style-classes-and-CSS-names-to-some-of-our-widge.patch: - Add CSS names and style classes so we can theme things more easily. + Add 0001-screen-window-Extra-padding-around-transparent-termi.patch: - Fix transparency on Wayland. Patch by Owen Taylor, via Debarshi Ray @ Fedora + Add 52_support_apturl.patch: - Support apt: urls. + Add 60_add_lp_handler.patch: - Add a handler for launchpad bug URLs. + Add scrollbar-background-theming.patch: - Draw background under the scrollbar that matches the actual terminal background color. This allows proper theming. + Add screen-Use-clean-env-when-creating-new-tab.patch: - Fix environment variables on opening new tab via the "Open in Terminal" right click menu in Nautilus. (LP: #1922839) gnome-terminal (3.46.2-1) unstable; urgency=medium * New upstream release (LP: #1992683) * Drop 3 patches applied in new release -- Jeremy Bicha Wed, 12 Oct 2022 13:56:53 -0400 ** Changed in: gnome-terminal (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1992683 Title: Update gnome-terminal to 3.46.2 Status in gnome-terminal package in Ubuntu: Fix Released Bug description: Impact - New upstream release in the stable 3.46.x series https://gitlab.gnome.org/GNOME/gnome- terminal/-/compare/3.46.1...3.46.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1992683/+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 1972654] Re: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable
ACK from the security team to sync from unstable. Please make sure the policy overrides in policykit-desktop-privileges still work or are converted to their equivalent JS before doing so. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1972654 Title: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable Status in policykit-1 package in Ubuntu: Confirmed Bug description: Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable for Ubuntu 23.04 Changelog entries since current kinetic version 0.105-33: https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog In particular, see the 0.120-4 changelog entry. I am filing a bug for Security Team review. Previously, Debian and Ubuntu developers agreed to keep using the last version of policykit before it switched to using JavaScript rules. But that was years ago. I believe Debian & Ubuntu are the only distros to have opted out of the new policykit. It is harder to maintain the old style rules when upstream rules use the new format. And it is a challenge to backport security and other bugfixes from the new series, without making mistakes or missing important details. There was a proposal to use duktape instead of mozjs for the JavaScript interpreter but I don't think that's been merged yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1992783] [NEW] Internet connection crashed during update from 20.04 to 22.04. Tried to fix the install with sudo apt --fix-broken install
Public bug reported: The rest of the update completed and version 22.04 is running. System is running fine but can't install a new package with apt-get install ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 104.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1586 F pulseaudio BuildID: 20220818191623 CasperMD5CheckResult: unknown Channel: Unavailable Date: Thu Oct 13 14:03:06 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 10 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-27 (200 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev wlp170s0 proto dhcp metric 600 169.254.0.0/16 dev wlp170s0 scope link metric 1000 192.168.1.0/24 dev wlp170s0 proto kernel scope link src 192.168.1.104 metric 600 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.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to jammy on 2022-08-29 (44 days ago) dmi.bios.date: 12/14/2021 dmi.bios.release: 3.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.07 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0A dmi.board.vendor: Framework dmi.board.version: AA dmi.chassis.asset.tag: FRANBMCPAA1445003R dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AA dmi.modalias: dmi:bvnINSYDECorp.:bvr03.07:bd12/14/2021:br3.7:svnFramework:pnLaptop:pvrAA:rvnFramework:rnFRANBMCP0A:rvrAA:cvnFramework:ct10:cvrAA:skuFRANBMCP0A: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0A dmi.product.version: AA dmi.sys.vendor: Framework ** 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/1992783 Title: Internet connection crashed during update from 20.04 to 22.04. Tried to fix the install with sudo apt --fix-broken install Status in firefox package in Ubuntu: New Bug description: The rest of the update completed and version 22.04 is running. System is running fine but can't install a new package with apt-get install ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 104.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1586 F pulseaudio BuildID: 20220818191623 CasperMD5CheckResult: unknown Channel: Unavailable Date: Thu Oct 13 14:03:06 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 10 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-27 (200 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev wlp170s0 proto dhcp metric 600 169.254.0.0/16 dev wlp170s0 scope link metric 1000 192.168.1.0/24 dev wlp170s0 proto kernel scope link src 192.168.1.104 metric 600 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.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to jammy on 2022-08-29 (44 days ago) dmi.bios.date: 12/14/2021 dmi.bios.release: 3.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.07 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0A dmi.board.vendor: Framework dmi.board.version: AA dmi.chassis.asset.tag: FRANBMCPAA1445003R dmi.chassis.type: 10 dmi.c
[Desktop-packages] [Bug 1992783] Re: Internet connection crashed during update from 20.04 to 22.04. Tried to fix the install with sudo apt --fix-broken install
Problem solved by adding the package name after the command (sudo apt --fix-broken install firefox) -- 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/1992783 Title: Internet connection crashed during update from 20.04 to 22.04. Tried to fix the install with sudo apt --fix-broken install Status in firefox package in Ubuntu: New Bug description: The rest of the update completed and version 22.04 is running. System is running fine but can't install a new package with apt-get install ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 104.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1586 F pulseaudio BuildID: 20220818191623 CasperMD5CheckResult: unknown Channel: Unavailable Date: Thu Oct 13 14:03:06 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 10 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-27 (200 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev wlp170s0 proto dhcp metric 600 169.254.0.0/16 dev wlp170s0 scope link metric 1000 192.168.1.0/24 dev wlp170s0 proto kernel scope link src 192.168.1.104 metric 600 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.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to jammy on 2022-08-29 (44 days ago) dmi.bios.date: 12/14/2021 dmi.bios.release: 3.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.07 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0A dmi.board.vendor: Framework dmi.board.version: AA dmi.chassis.asset.tag: FRANBMCPAA1445003R dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AA dmi.modalias: dmi:bvnINSYDECorp.:bvr03.07:bd12/14/2021:br3.7:svnFramework:pnLaptop:pvrAA:rvnFramework:rnFRANBMCP0A:rvrAA:cvnFramework:ct10:cvrAA:skuFRANBMCP0A: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0A dmi.product.version: AA dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992783/+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 1861913] Re: "Strict" tracking protection sometimes causes _all_ content to fail to display on browser launch
** Changed in: firefox Importance: Medium => Unknown -- 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/1861913 Title: "Strict" tracking protection sometimes causes _all_ content to fail to display on browser launch Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: This morning I booted my machine and launched Firefox. I restored my tabs from my previous session, and _none of them_ displayed any content. The tabs included pins, regular sites, and extension dialogs (specifically, a couple of instances of the LastPass 2FA prompt). Further to that, Firefox menus also wouldn't display; either via right-click on tabs, or via the "hamburger" menu in the top-right. (I could still close tabs via Ctrl-W for non-pinned tabs, or via middle- click for pinned tabs.) favicons were displayed correctly, and I confirmed that the pages were actually being fetched from the remote sites because I typed the address for a page I know redirects and the redirect happened (specifically, "!g foo" in my address bar caused DuckDuckGo to redirect me to Google). Restarting the browser did not fix this. Closing all of my tabs and restarting the browser did not fix this. Closing all of my tabs and restarting the browser, however, _did_ allow the Firefox menus to render (provided I didn't try to open any web pages before using them), which allowed me to switch "Enhanced Tracking Protection" from Strict to Standard, fixing the problem. (This is the second time I've experienced this exact behaviour, which is how I knew to try modifying the tracking protection setting. The last time was on an older version of Firefox in August: https://wrestle.town/@Odd_Bloke/102655281770357045) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 72.0.2+build1-0ubuntu1 Uname: Linux 5.4.5-050405-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BuildID: 20200117190643 Channel: Unavailable CurrentDesktop: i3 Date: Tue Feb 4 13:01:53 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-05-07 (273 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-94f8002b-6eb0-4faf-98c0-257a62150805 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:724 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=72.0.2/20200117190643 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2019-11-15 (80 days ago) dmi.bios.date: 01/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1861913/+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 1796777] Re: Download folder settings are inconsistent between create and move
** Changed in: thunderbird Importance: Medium => Unknown -- 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/1796777 Title: Download folder settings are inconsistent between create and move Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: When "message synchronizing" is set to download messages from an IMAP account, a newly created folder under the inbox is automatically set to download messages as well, but when that folder is then moved (using the mouse) under some other folder, the "download" check box on the panel "Items for offline use" is cleared. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: thunderbird 1:52.9.1+build3-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: humphrey 2434 F pulseaudio /dev/snd/controlC1: humphrey 2434 F pulseaudio BuildID: 20180710085647 Channel: Unavailable CurrentDesktop: Unity Date: Tue Oct 9 11:41:44 2018 ExecutablePath: /usr/lib/thunderbird/thunderbird Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-12-13 (299 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.101 metric 100 IwConfig: lono wireless extensions. enp4s0no wireless extensions. Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-3f3dab64-e8aa-4350-afd1-b05560180506 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js [Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js Profiles: Profile0 (Default) - LastVersion=52.9.1/20180710085647 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to xenial on 2018-08-28 (41 days ago) dmi.bios.date: 06/22/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0N185P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd06/22/2010:svnDellInc.:pnVostro420Series:pvr:rvnDellInc.:rn0N185P:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.name: Vostro 420 Series dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1796777/+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 1838200] Re: Popover prompts remain on top of the display even when firefox is unfocused
** Changed in: firefox Importance: Medium => Unknown -- 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/1838200 Title: Popover prompts remain on top of the display even when firefox is unfocused Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: You can see video that appears this problem below (in comments). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 68.0.1+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BuildID: 20190719083815 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 19:09:48 2019 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/firefox/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-07-27 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190726) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.0.1/20190719083815 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1838200/+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 868175] Re: Thunderbird doesn't remember last window position or state
** Changed in: thunderbird Importance: Medium => Unknown -- 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/868175 Title: Thunderbird doesn't remember last window position or state Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: thunderbird should honor the location where it was closed last time and open at the same position when started. for example: on my dual monitor setup, thunderbird opens on the first screen in fullscreen mode. i then move it to the second screen and close theunderbird. opening it again, thunderbird opens on the first screen instead of screen 2. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: thunderbird 7.0.1+build1+nobinonly-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: NVidia [HDA NVidia], device 0: VT1708B Analog [VT1708B Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ulrich 1605 F pulseaudio /dev/snd/pcmC0D0p: ulrich 1605 F...m pulseaudio /dev/snd/controlC1: ulrich 1605 F pulseaudio BuildID: 20110929183320 CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xf9f78000 irq 21' Mixer name : 'Nvidia MCP77/78 HDMI' Components : 'HDA:1106e721,10438345,00100100 HDA:10de0002,10de0101,0010' Controls : 38 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'Speakers'/'Logitech Logitech Z-5 Speakers at usb-:00:04.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB046d:0a13' Controls : 2 Simple ctrls : 1 Channel: release Date: Wed Oct 5 10:26:13 2011 ExecutablePath: /usr/lib/thunderbird-7.0.1/thunderbird-bin ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2) IpRoute: default via 192.168.2.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.106 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. Prefs: places.database.lastMaintenance - 1317037118 extensions.lastAppVersion - 7.0.1 network.cookie.prefsMigrated - true font.size.variable.x-western - 14 places.history.expiration.transient_current_max_pages - 124626 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=7.0.1/20110929183320 (Running) RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3N78-VM 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.:bvr0406:bd06/02/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/868175/+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 848183] Re: RFC822 Attachments and .EML files cannot be moved to folders
** Changed in: thunderbird Importance: Medium => Unknown -- 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/848183 Title: RFC822 Attachments and .EML files cannot be moved to folders Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: From https://wiki.mozilla.org/Thunderbird:Fix_some_longstanding_bugs#RFC822_Attachments_and_.EML_files: "It should be possible to file (import) the attachment or the .EML file directly into a mail folder (bug 11013 / bug 226877, bug 204612). The menu action Message | Copy To | folder would be an elegant way to implement this." ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: thunderbird 3.1.13+build1+nobinonly-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Sep 12 15:02:59 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1) ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/zsh SourcePackage: thunderbird UpgradeStatus: Upgraded to natty on 2011-04-30 (135 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/848183/+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 794598] Re: Keyboard Shortcut to Zoom (Ctrl ++) doesn't work until after menu Zoom
** Changed in: thunderbird Importance: Medium => Unknown -- 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/794598 Title: Keyboard Shortcut to Zoom (Ctrl ++) doesn't work until after menu Zoom Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird To demonstrate this bug: Open thunderbird, click in the window pane with the message, try the shortcut (Ctrl ++). (Nothing happens no matter how many times you do. However, if you use the menu once to zoom, then the shortcut works just fine. Rob ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: thunderbird 3.1.10+build1+nobinonly-0ubuntu0.11.04.2 ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 NonfreeKernelModules: nvidia Architecture: i386 CheckboxSubmission: b3f7c5231c874165f4d7945857608f87 CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Wed Jun 8 07:36:55 2011 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird UpgradeStatus: Upgraded to natty on 2011-04-14 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/794598/+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 350407] Re: Locally saved webpages not displaying correctly
** Changed in: firefox Importance: Medium => Unknown -- 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/350407 Title: Locally saved webpages not displaying correctly Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: WORKAROUND: Firefox Scrapbook Addon: https://addons.mozilla.org/en-US/firefox/addon/427 -- Firefox Information: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032711 Ubuntu/8.04 (hardy) Firefox/3.0.8 Web pages that have been saved locally are not displaying correctly. To see this problem run the following steps: 1). Go to the jwebunit website ( http://jwebunit.sourceforge.net/ ). Suggesting saving a page from this website as a test since this provided a very good example of the problem. 2). Right click on the main web page and select "Save As..." 3). Save the web page somewhere on the local drive. On Ubuntu there is an option in the save dialog specifying how to save the web page. Make sure that "Web page, complete" is selected. 4). Navigate to the location where the web page was stored and attempt to load the saved page back into firefox At this point the web page that is loaded from the hard disk should display very differently than the real web page. Styles and elements of the original web page should be missing. I also tested this same process on Windows XP SP2 (using firefox 3.0.8) and I see the exact same behavior. This seems to eliminate the problem being caused by local browser settings (since I see the same thing under Windows and Linux on two separate machines with totally different preferences). Furthermore I was able to run steps 1 - 4 using Opera 9.64 and this produces a saved web page that displays identically to the web page navigated to on the internet. ...Additionally I just tried loading the webpage saved locally using opera and this loads into firefox correctly. So the problem appears to be with the actual web page save using firefox and not the fact that the page is saved locally. ProblemType: Bug Architecture: i386 Date: Sat Mar 28 11:36:15 2009 DistroRelease: Ubuntu 8.04 Package: firefox-3.0 3.0.8+nobinonly-0ubuntu0.8.04.2 PackageArchitecture: i386 ProcEnviron: PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-23-generic i686 Update - Looks like this bug report may have gone to the wrong place. I was expecting this to be submitted against firefox instead of Ubuntu... Apparently selecting --> Help --> Report a Problem inside of the firefox web browser sends bug reports to Ubuntu. - Ok, please disregard this bug report; I've got this submitted to the correct place now. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/350407/+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 329455] Re: canberra-gtk-pl seg fault
Once I have faced this issue and I searched on google and got the solution. So you should try on google Regards https://almotion.net//";>Alight Motion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/329455 Title: canberra-gtk-pl seg fault Status in libcanberra package in Ubuntu: New Bug description: Gnome crashed on me and took me back to the login prompt. Messages file shows this: Feb 14 10:45:03 ubuntudesktop bonobo-activation-server (reece-7936): could not associate with desktop session: Failed to connect to socket /tmp/dbus-dXvoGakMY9: Connection refused Feb 14 10:45:04 ubuntudesktop kernel: [829984.836630] mtrr: type mismatch for e000,1000 old: write-back new: write-combining Feb 14 10:45:23 ubuntudesktop pulseaudio[8049]: ltdl-bind-now.c: Failed to find original dlopen loader. Feb 14 10:45:23 ubuntudesktop pulseaudio[8051]: pid.c: Stale PID file, overwriting. Feb 14 10:45:23 ubuntudesktop pulseaudio[8051]: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted Feb 14 10:45:23 ubuntudesktop pulseaudio[8051]: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted Feb 14 10:45:33 ubuntudesktop kernel: [830013.327147] canberra-gtk-pl[8099]: segfault at 929dcd0 ip b727584d sp b7012f10 error 6 in libpulse.so.0.4.1[b7236000+4e000] I have no idea what else to provide - let me know and I'll provide it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/329455/+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 1992511] Re: Update gtksourceview5 to 5.6.1
This bug was fixed in the package gtksourceview5 - 5.6.1-1 --- gtksourceview5 (5.6.1-1) unstable; urgency=medium * New upstream release (LP: #1992511) -- Jeremy Bicha Tue, 11 Oct 2022 16:20:22 -0400 ** Changed in: gtksourceview5 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview5 in Ubuntu. https://bugs.launchpad.net/bugs/1992511 Title: Update gtksourceview5 to 5.6.1 Status in gtksourceview5 package in Ubuntu: Fix Released Bug description: Impact -- New upstream bug fix release for GNOME 43 https://gitlab.gnome.org/GNOME/gtksourceview/-/blob/5.6.1/NEWS https://gitlab.gnome.org/GNOME/gtksourceview/-/compare/5.6.0...5.6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview5/+bug/1992511/+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 1988488] Re: Screen freeze before the login screen (if the third party software option was selected)
This bug was fixed in the package gnome-shell - 43.0-1ubuntu2 --- gnome-shell (43.0-1ubuntu2) kinetic; urgency=medium [ Daniel van Vugt ] * Avoid deadlocking in gst_init_check() on startup (LP: #1988488) [ Jeremy Bicha ] * debian/source_gnome-shell.py: Don't try to report nonexistent mouse gsettings schema * Cherry-pick 4 patches from the future gnome-shell 43.1 to fix various issues -- Jeremy Bicha Wed, 12 Oct 2022 11:25:50 -0400 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- 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/1988488 Title: Screen freeze before the login screen (if the third party software option was selected) Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Fix Released Bug description: [ Workaround ] 1. Install *without* the third-party option. 2. sudo apt install ubuntu-restricted-extras 3. sudo apt remove gstreamer1.0-vaapi [ Original Description ] The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1988488/+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 1992756] Re: Screen turns black for a long time after each login and when detecting screens or changing screen layout.
I tried updating graphics drivers to cuda-drivers-520 and the problem persists. I've attached updated lspci.txt and recentjournal.txt with these new drivers. Let me know if you want me to reproduce with cuda-drivers-515 instead. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1992756/+attachment/5623939/+files/lspci.txt -- 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/1992756 Title: Screen turns black for a long time after each login and when detecting screens or changing screen layout. Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-515 package in Ubuntu: Incomplete Bug description: I have a Thinkpad P15 with a A2000 GPU with Ubuntu 22.04.1 LTS. This happens using Wayland and nvidia cuda drivers. It seems like the system uses very long to identify the screens. This happens when I use external monitors, but also when only using the laptop screen. Changing the screen layout takes so long that I am unable to accept the change before it is reverted to the previous. Only the mouse pointer is visible, the rest of the screens are black during this process. $ apt-cache policy cuda cuda: Installed: 11.7.1-1 Candidate: 11.8.0-1 Version table: 11.8.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages *** 11.7.1-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages 100 /var/lib/dpkg/status 11.7.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages $ nvidia-smi Thu Oct 13 10:46:02 2022 +-+ | NVIDIA-SMI 515.65.01Driver Version: 515.65.01CUDA Version: 11.7 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA RTX A200... On | :01:00.0 On | N/A | | N/A 46CP5 8W / N/A |146MiB / 4096MiB | 22% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 4451 G /usr/lib/xorg/Xorg145MiB | +-+ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 13 10:25:17 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-05 (37 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1992756/+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 1992756] Re: Screen turns black for a long time after each login and when detecting screens or changing screen layout.
** Attachment added: "recentjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1992756/+attachment/5623940/+files/recentjournal.txt ** Information type changed from Public to Public Security -- 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/1992756 Title: Screen turns black for a long time after each login and when detecting screens or changing screen layout. Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-515 package in Ubuntu: Incomplete Bug description: I have a Thinkpad P15 with a A2000 GPU with Ubuntu 22.04.1 LTS. This happens using Wayland and nvidia cuda drivers. It seems like the system uses very long to identify the screens. This happens when I use external monitors, but also when only using the laptop screen. Changing the screen layout takes so long that I am unable to accept the change before it is reverted to the previous. Only the mouse pointer is visible, the rest of the screens are black during this process. $ apt-cache policy cuda cuda: Installed: 11.7.1-1 Candidate: 11.8.0-1 Version table: 11.8.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages *** 11.7.1-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages 100 /var/lib/dpkg/status 11.7.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages $ nvidia-smi Thu Oct 13 10:46:02 2022 +-+ | NVIDIA-SMI 515.65.01Driver Version: 515.65.01CUDA Version: 11.7 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA RTX A200... On | :01:00.0 On | N/A | | N/A 46CP5 8W / N/A |146MiB / 4096MiB | 22% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 4451 G /usr/lib/xorg/Xorg145MiB | +-+ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 13 10:25:17 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-05 (37 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1992756/+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 1989314] Re: To support Elan fp device [04F3:0C88]
** Also affects: libfprint (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: libfprint (Ubuntu Jammy) Importance: Undecided => High ** Changed in: libfprint (Ubuntu Jammy) Status: New => Triaged ** Changed in: libfprint (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1989314 Title: To support Elan fp device [04F3:0C88] Status in OEM Priority Project: Fix Committed Status in libfprint package in Ubuntu: In Progress Status in libfprint source package in Jammy: Triaged Bug description: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/7899bf4240819a28f3e29bd40d4e36aa432343b6 This ID is included in upstream. [Impact] * Devices have Elan [04F3:0C88] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be [04F3:0C88] will be supported. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1989314/+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 1992783] Re: Internet connection crashed during update from 20.04 to 22.04. Tried to fix the install with sudo apt --fix-broken install
** Changed in: firefox (Ubuntu) Status: New => Invalid -- 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/1992783 Title: Internet connection crashed during update from 20.04 to 22.04. Tried to fix the install with sudo apt --fix-broken install Status in firefox package in Ubuntu: Invalid Bug description: The rest of the update completed and version 22.04 is running. System is running fine but can't install a new package with apt-get install ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 104.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1586 F pulseaudio BuildID: 20220818191623 CasperMD5CheckResult: unknown Channel: Unavailable Date: Thu Oct 13 14:03:06 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 10 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-27 (200 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev wlp170s0 proto dhcp metric 600 169.254.0.0/16 dev wlp170s0 scope link metric 1000 192.168.1.0/24 dev wlp170s0 proto kernel scope link src 192.168.1.104 metric 600 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.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to jammy on 2022-08-29 (44 days ago) dmi.bios.date: 12/14/2021 dmi.bios.release: 3.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.07 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0A dmi.board.vendor: Framework dmi.board.version: AA dmi.chassis.asset.tag: FRANBMCPAA1445003R dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AA dmi.modalias: dmi:bvnINSYDECorp.:bvr03.07:bd12/14/2021:br3.7:svnFramework:pnLaptop:pvrAA:rvnFramework:rnFRANBMCP0A:rvrAA:cvnFramework:ct10:cvrAA:skuFRANBMCP0A: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0A dmi.product.version: AA dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992783/+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 1992775] Re: gnome-session fails to build on kinetic
This bug was fixed in the package gnome-session - 43.0-1ubuntu2 --- gnome-session (43.0-1ubuntu2) kinetic; urgency=medium * debian/gnome-session-bin.install: Don't install gnome-session-custom-session (LP: #1992775) -- Jeremy Bicha Thu, 13 Oct 2022 07:13:51 -0400 ** Changed in: gnome-session (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1992775 Title: gnome-session fails to build on kinetic Status in gnome-session package in Ubuntu: Fix Released Bug description: gnome-session fails to build on kinetic because it tries to install gnome-session-custom-session. See https://bugs.debian.org/1013672 for more details. Basically, we don't enable the enable_session_selector build option and gnome- session now correctly doesn't install gnome-session-custom-session in that case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1992775/+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 1992504] Re: Update libsoup to 2.74.3
This bug was fixed in the package libsoup2.4 - 2.74.3-1 --- libsoup2.4 (2.74.3-1) unstable; urgency=medium * New upstream release (LP: #1992504) * Drop 3 test patches applied in new release -- Jeremy Bicha Tue, 11 Oct 2022 15:28:32 -0400 ** Changed in: libsoup2.4 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1992504 Title: Update libsoup to 2.74.3 Status in libsoup2.4 package in Ubuntu: Fix Released Bug description: New upstream bugfix release in the stable libsoup 2.74 series https://gitlab.gnome.org/GNOME/libsoup/-/blob/2.74.3/NEWS https://gitlab.gnome.org/GNOME/libsoup/-/compare/2.74.2...2.74.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1992504/+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 1992495] Re: Update gnome-session to 43.0
This bug was fixed in the package gnome-session - 43.0-1ubuntu2 --- gnome-session (43.0-1ubuntu2) kinetic; urgency=medium * debian/gnome-session-bin.install: Don't install gnome-session-custom-session (LP: #1992775) -- Jeremy Bicha Thu, 13 Oct 2022 07:13:51 -0400 ** Changed in: gnome-session (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1992495 Title: Update gnome-session to 43.0 Status in gnome-session package in Ubuntu: Fix Released Bug description: gnome-session 43 is a minor bugfix release. Since we otherwise ship the rest of GNOME 43 in Ubuntu 22.10, it would be good to include this update too. https://gitlab.gnome.org/GNOME/gnome- session/-/compare/42.0...43.0?from_project_id=1659 Two bugfix changes (one of them is https://bugs.debian.org/1013672 ) and translation updates. https://gitlab.gnome.org/GNOME/gnome-session/-/blob/43.0/NEWS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1992495/+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 1990200] Re: goa-daemon crashed with SIGABRT
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1990200/+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 1990200] Re: goa-daemon crashed with SIGABRT
** Changed in: gnome-online-accounts (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1990200/+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 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04
** Description changed: + [Impact] + + By removing the firefox deb and installing the snap instead, ubuntu- + release-upgrader is subverting the logic of the firefox transitional + deb. + + [Test Case] + + Perform an upgrade from focal to jammy: + + $ do-release-upgrade + + On an affected system, the firefox deb will be removed by the upgrade, + and the snap will be installed instead. On a fixed system, ubuntu- + release-upgrader will not remove the firefox deb, and the deb will + handle the transition to the snap. + + [Where problems could occur] + + If the patch was wrong, e.g. JSON syntax error or similar, it could mess + up the remaining deb2snap entries. + + [Original Description] + 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 (Kubuntu Jammy live session in QEMU VM) 2) apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:22.04.6 3) expected (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.) * Firefox icon on panel to be intact. * Clicked icon launches browser. * Icon tooltip/mouse hover to describe application. 4) happened instead * Icon is missing/replaced with a generic icon * Icon click produces error notification "Plasma Workspace - preferred://browser" * Icon tooltip/mouse hover appears, though is blank. Additional info: * firefox is still installed, works as expected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy dist-upgrade Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True -- 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/1964036 Title: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04 Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in firefox source package in Jammy: New Status in ubuntu-release-upgrader source package in Jammy: Triaged Bug description: [Impact] By removing the firefox deb and installing the snap instead, ubuntu- release-upgrader is subverting the logic of the firefox transitional deb. [Test Case] Perform an upgrade from focal to jammy: $ do-release-upgrade On an affected system, the firefox deb will be removed by the upgrade, and the snap will be installed instead. On a fixed system, ubuntu- release-upgrader will not remove the firefox deb, and the deb will handle the transition to the snap. [Where problems could occur] If the patch was wrong, e.g. JSON syntax error or similar, it could mess up the remaining deb2snap entries. [Original Description] 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 (Kubuntu Jammy live session in QEMU VM) 2) apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:22.04.6 3) expected (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.) * Firefox icon on panel to be intact. * Clicked icon launches browser. * Icon tooltip/mouse hover to describe application. 4) happened instead * Icon is missing/replaced with a generic icon * Icon click produces error notification "Plasma Workspace - preferred://browser" * Icon tooltip/mouse hover appears, though is blank. Additional info: * firefox is still installed, works as expected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy dist-upgrade Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sourc
[Desktop-packages] [Bug 1990200] Re: goa-daemon crashed with SIGABRT
Impact: I miss new events because I no longer get calendar notifications because the calendar does not sync anymore when that happens. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1990200/+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 1992822] [NEW] /usr/libexec/goa-daemon:6:g_assertion_message:g_assertion_message_expr:finish_call:rest_proxy_call_sync:get_identity_sync
*** This bug is a duplicate of bug 1990200 *** https://bugs.launchpad.net/bugs/1990200 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-online-accounts. This problem was most recently seen with package version 3.46.0-1, the problem page at https://errors.ubuntu.com/problem/595467fba803f55fea2dfef4bb4b3a77a787e18e 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/. ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: kinetic kylin-22.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1992822 Title: /usr/libexec/goa- daemon:6:g_assertion_message:g_assertion_message_expr:finish_call:rest_proxy_call_sync:get_identity_sync Status in gnome-online-accounts package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-online-accounts. This problem was most recently seen with package version 3.46.0-1, the problem page at https://errors.ubuntu.com/problem/595467fba803f55fea2dfef4bb4b3a77a787e18e 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/ubuntu/+source/gnome-online-accounts/+bug/1992822/+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 1992822] Re: /usr/libexec/goa-daemon:6:g_assertion_message:g_assertion_message_expr:finish_call:rest_proxy_call_sync:get_identity_sync
*** This bug is a duplicate of bug 1990200 *** https://bugs.launchpad.net/bugs/1990200 ** This bug has been marked a duplicate of bug 1990200 goa-daemon crashed with SIGABRT -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1992822 Title: /usr/libexec/goa- daemon:6:g_assertion_message:g_assertion_message_expr:finish_call:rest_proxy_call_sync:get_identity_sync Status in gnome-online-accounts package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-online-accounts. This problem was most recently seen with package version 3.46.0-1, the problem page at https://errors.ubuntu.com/problem/595467fba803f55fea2dfef4bb4b3a77a787e18e 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/ubuntu/+source/gnome-online-accounts/+bug/1992822/+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 1990200] Re: goa-daemon crashed with SIGABRT
error tracker entry is https://errors.ubuntu.com/problem/595467fba803f55fea2dfef4bb4b3a77a787e18e ** Tags added: rls-kk-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1990200/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken
I was unable to recreate this bug using these packages: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with additional characters (extra variants) ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME ** Attachment added: "Screenshot from 2022-10-13 08-26-26.png" https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+attachment/5623977/+files/Screenshot%20from%202022-10-13%2008-26-26.png ** Changed in: gnome-font-viewer (Ubuntu) Importance: Undecided => Low ** Tags removed: jj-rls-incoming ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fonts-dejavu package in Ubuntu: Invalid Status in gnome-font-viewer package in Ubuntu: New Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken
There was no change in the fonts-dejavu package between Focal -> Jammy. ** Also affects: gnome-font-viewer (Ubuntu) Importance: Undecided Status: New ** Changed in: fonts-dejavu (Ubuntu) Status: New => Invalid ** Tags removed: foundations-triage-discuss ** Tags added: jj-rls-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fonts-dejavu package in Ubuntu: Invalid Status in gnome-font-viewer package in Ubuntu: New Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+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 1991412] Re: gnome-terminal icon not placed correctly in pinned area; called "preferences"
Fixed in repo, version 3.46.2-1ubuntu1. ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1991412 Title: gnome-terminal icon not placed correctly in pinned area; called "preferences" Status in gnome-terminal package in Ubuntu: Fix Released Bug description: I've pinned gnome-terminal to gnomes-shells (favorites? launch?) area. When launching, it doesn't track that it's launched like normal favorited apps, but instead creates an icon to the right of the divider, called "preferences." I'm not sure if it's something with the Action in the .desktop file going wrong? Screenshot attached shows issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1991412/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Xubuntu 22.04.1 after upgrading from 20.04 In order to get multiple Windows 10 systems to "discover" the samba shares on two different Xubuntu systems, I had to re-enable SMB1 protocol on all the Windows systems. Microsoft apparently keeps disabling this on system updates. As reported above, old Windows mapped drive assignments made to Ubuntu samba shares have continued to work over time, but new shares cannot be seen unless SMB1 is enabled. of course, this should all just work using newer secure protocols. For a significant piece of server software, the fact that this hasn't been addressed long ago is a real mystery. -- 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/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 885525] Re: Deleting a Gmail Message Always Sends Item to [Gmail]/Trash
** Changed in: thunderbird Importance: Medium => Unknown -- 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/885525 Title: Deleting a Gmail Message Always Sends Item to [Gmail]/Trash Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Thunderbird 7.0.1, Ubuntu 11.10 Gmail accounts do not obey the setting in Account Settings --> [Account] --> Server Settings --> When I delete a message I changed this to move the message to Gmail's "All Mail" folder, attempting to imitate the Gmail web interface's "Archive" option. However, regardless of setting, the item always moved to Trash. This persisted after restart of the client. The settings save, but have no effect. Caveat: This was tested on two Google Apps for Domains accounts, though I suspect this behavior will happen with gmail.com accounts as well. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/885525/+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 597825] Re: Menu accelerators in Firefox don't follow the GNOME policy.
** Changed in: firefox Importance: Medium => Unknown -- 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/597825 Title: Menu accelerators in Firefox don't follow the GNOME policy. Status in Mozilla Firefox: Confirmed Status in One Hundred Papercuts: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Binary package hint: firefox The current GNOME default is that menu accelerators are hidden, and shown when you press the ALT key. Firefox doesn't observe this policy and have their menu accelerators displayed all the time. Also, pressing ALT alone in GNOME and Firefox doesn't invoke any menu command. This inconsistent behavior is a usability issue and also makes Ubuntu desktop look unprofessional. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.3+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 Date: Wed Jun 23 21:37:05 2010 EcryptfsInUse: Yes FirefoxPackages: firefox 3.6.3+nobinonly-0ubuntu4 firefox-gnome-support 3.6.3+nobinonly-0ubuntu4 firefox-branding 3.6.3+nobinonly-0ubuntu4 abroswer N/A abrowser-branding N/A ProcEnviron: PATH=(custom, user) LANG=pl_PL.utf8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/597825/+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 334693] Re: Search type should be remembered for each mailbox.
** Changed in: thunderbird Importance: Medium => Unknown -- 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/334693 Title: Search type should be remembered for each mailbox. Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird I have an Inbox and a Sent box (among others) that I search frequently. When I search the Inbox, I usually search Subject/From, but when I search the Sent, it is usually To. The problem is that Thunderbird doesn't remember that for each mailbox. When I change from Inbox to Sent, I have to change the search criteria again, and likewise when I change back. It would be nice if that could be remembered. If you don't like this, perhaps just making the default search criteria for Sent to be To/Subject might work nicely too. Best regards, Rob ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 Package: mozilla-thunderbird 2.0.0.19+nobinonly-0ubuntu0.8.10.1 PackageArchitecture: all ProcEnviron: PATH=/usr/local/brightq//bin:/usr/local/brightq//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.27-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/334693/+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 1979352] Re: system frozen after sleep
Maybe related to this https://github.com/mate-desktop/mate- desktop/issues/519 ** Bug watch added: github.com/mate-desktop/mate-desktop/issues #519 https://github.com/mate-desktop/mate-desktop/issues/519 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Confirmed Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 1979352] Re: system frozen after sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: acpid (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Confirmed Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 1979352] Re: system frozen after sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Confirmed Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 1979352] Re: system frozen after sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upower (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Confirmed Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 1992675] Re: cd-info man page incomplete
** Tags added: manpage -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcdio in Ubuntu. https://bugs.launchpad.net/bugs/1992675 Title: cd-info man page incomplete Status in libcdio package in Ubuntu: New Bug description: Ubuntu Server 22.04.1 LTS amd64 libcdio-utils: 2.1.0-3build1 amd64 The man page for cd-info libcdio-utils reads, in part, --no-cddb Does nothing since this program is not -P, --cddb-port=INT CDDB-enabled -H, --cddb-http --cddb-server=STRING --cddb-cache=STRING --cddb-email=STRING --no-cddb-cache --cddb-timeout=INT The sentence fragment and missing descriptions were not expected. What was expected is something closer to the descriptions at https://www.systutorials.com/docs/linux/man/1-cd-info/ which are --no-cddb Don't look up audio CDDB information or print it -P, --cddb-port=INT CDDB port number to use (default 8880) -H, --cddb-http Lookup CDDB via HTTP proxy (default no proxy) --cddb-server=STRING CDDB server to contact for information (default: freedb.freedb.org) --cddb-cache=STRING Location of CDDB cache directory (default ~/.cddbclient) --cddb-email=STRING Email address to give CDDB server (default me [at] home) --no-cddb-cache Disable caching of CDDB entries locally (default caches) --cddb-timeout=INT CDDB timeout value in seconds (default 10 seconds) Bonus point: If there were an example showing the use of these options with http://gnudb.gnudb.org as CDDB source, that would be awesome. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcdio-utils 2.1.0-3build1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 16:13:35 2022 InstallationDate: Installed on 2022-05-06 (158 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libcdio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1992675/+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 1980805] Re: Backport packages for 20.04.5 HWE stack
** Changed in: llvm-toolchain-13 (Ubuntu) Status: New => Invalid -- 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/1980805 Title: Backport packages for 20.04.5 HWE stack Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in mesa-amber package in Ubuntu: Invalid Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-13 source package in Focal: Fix Committed Status in mesa source package in Focal: New Status in mesa-amber source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.5 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] libdrm: pci-id updates, some minor api updates mesa: a new major release, but we'll pull the final stable release of 22.0.x series, so there shouldn't be any regressions left at that point mesa-amber: forked from mesa 21.3.x, this LTS branch keeps old DRI drivers that were removed from main mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1980805/+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 1992838] [NEW] GUI PDP Auto-connect option is not working
Public bug reported: Setup details: Kernel Version: 5.15.36--wwan-bkc-5 OS Version: Ubuntu 20.04.1 LTS IOSM: IOSM_DRIVER_v8.06.13_5.15.36-wwan-bkc-5_2022_SEP01 MSDK_Version : MSDK_4G_ML_2022_SEP01_00 ModemManager Version (ModemManager -V) : 1.19.1 libMbim Version (mbimcli -V): 1.27.5 mmcli Version : 1.19.1 Test Scenario : 1) Boot up RVP with Auto PDP enable -> Auto PDP enabled from UI 2) Registered to LTE Cell in good radio conditions 3) Start the ping 4) Change the Power level on simulator to bad radio conditions & make sure UE goes to OOS 5) Change the Power level to good conditions on simulator. 6) Check whether UE attaches to N/W & ping will resume Observations: 1) After recovery from OOS data call is not resumed & UE stays in modemstate "8" only Expected Result: After OOS recovery data call should resume. >> From modem and modem manager we observed that host is not able to send the MBIM_CONNECT_CID to activate the connection. That is because Auto-connect was not successfully activated from the UI. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Description changed: Setup details: Kernel Version: 5.15.36--wwan-bkc-5 OS Version: Ubuntu 20.04.1 LTS IOSM: IOSM_DRIVER_v8.06.13_5.15.36-wwan-bkc-5_2022_SEP01 MSDK_Version : MSDK_4G_ML_2022_SEP01_00 ModemManager Version (ModemManager -V) : 1.19.1 libMbim Version (mbimcli -V): 1.27.5 mmcli Version : 1.19.1 - Modem Version: M2_7560_R_01.2236.00 Test Scenario : 1) Boot up RVP with Auto PDP enable -> Auto PDP enabled from UI 2) Registered to LTE Cell in good radio conditions 3) Start the ping 4) Change the Power level on simulator to bad radio conditions & make sure UE goes to OOS 5) Change the Power level to good conditions on simulator. 6) Check whether UE attaches to N/W & ping will resume Observations: 1) After recovery from OOS data call is not resumed & UE stays in modemstate "8" only Expected Result: After OOS recovery data call should resume. >> From modem and modem manager we observed that host is not able to send the MBIM_CONNECT_CID to activate the connection. That is because Auto-connect was not successfully activated from the UI. -- 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/1992838 Title: GUI PDP Auto-connect option is not working Status in gnome-shell package in Ubuntu: New Bug description: Setup details: Kernel Version: 5.15.36--wwan-bkc-5 OS Version: Ubuntu 20.04.1 LTS IOSM: IOSM_DRIVER_v8.06.13_5.15.36-wwan-bkc-5_2022_SEP01 MSDK_Version : MSDK_4G_ML_2022_SEP01_00 ModemManager Version (ModemManager -V) : 1.19.1 libMbim Version (mbimcli -V): 1.27.5 mmcli Version : 1.19.1 Test Scenario : 1) Boot up RVP with Auto PDP enable -> Auto PDP enabled from UI 2) Registered to LTE Cell in good radio conditions 3) Start the ping 4) Change the Power level on simulator to bad radio conditions & make sure UE goes to OOS 5) Change the Power level to good conditions on simulator. 6) Check whether UE attaches to N/W & ping will resume Observations: 1) After recovery from OOS data call is not resumed & UE stays in modemstate "8" only Expected Result: After OOS recovery data call should resume. >> From modem and modem manager we observed that host is not able to send the MBIM_CONNECT_CID to activate the connection. That is because Auto-connect was not successfully activated from the UI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1992838/+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 1980386] Re: `radeonsi_dri.so` driver missing on riscv64
** Changed in: llvm-toolchain-15 (Ubuntu Jammy) Status: New => Invalid -- 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/1980386 Title: `radeonsi_dri.so` driver missing on riscv64 Status in llvm-toolchain-15 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-15 source package in Jammy: Invalid Status in mesa source package in Jammy: Confirmed Status in llvm-toolchain-15 source package in Kinetic: Fix Released Status in mesa source package in Kinetic: Confirmed Bug description: The package is missing the `radeonsi` driver, with the reasoning that LLVM is not implemented on the architecture: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618 That said, it works just fine on focal, where it is still enabled. Without this driver there's no way to use AMD graphics cards on RISC-V. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.1-1ubuntu2 ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30 Uname: Linux 5.15.0-1007-generic riscv64 ApportVersion: 2.20.11-0ubuntu82 Architecture: riscv64 CasperMD5CheckResult: unknown Date: Thu Jun 30 15:48:11 2022 ProcCpuinfoMinimal: processor: 3 hart : 4 isa : rv64imafdc mmu : sv39 uarch: sifive,u74-mc ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-15/+bug/1980386/+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 1985856] Re: Update Mutter to 42.5
** Summary changed: - Update Mutter to 42.4 + Update Mutter to 42.5 ** Description changed: Impact -- There is a new bugfix release in the stable 42 series. - https://gitlab.gnome.org/GNOME/mutter/-/blob/42.4/NEWS + https://gitlab.gnome.org/GNOME/mutter/-/blob/42.5/NEWS It's hoped that this update will be included in Ubuntu 22.04.1 LTS. Test Case - sudo apt install budgie-desktop gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: Budgie GNOME GNOME Classic Ubuntu Ubuntu on Xorg What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- 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/1985856 Title: Update Mutter to 42.5 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Triaged Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.5/NEWS It's hoped that this update will be included in Ubuntu 22.04.1 LTS. Test Case - sudo apt install budgie-desktop gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: Budgie GNOME GNOME Classic Ubuntu Ubuntu on Xorg What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1985856/+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 1985856] Re: Update Mutter to 42.5
** Changed in: mutter (Ubuntu Jammy) Status: In Progress => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1985856 Title: Update Mutter to 42.5 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Triaged Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.5/NEWS It's hoped that this update will be included in Ubuntu 22.04.1 LTS. Test Case - sudo apt install budgie-desktop gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: Budgie GNOME GNOME Classic Ubuntu Ubuntu on Xorg What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1985856/+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
From #ubuntu-devel on 2022-10-13 10:12 < bdmurray> oSoMoN: with regards to bug 1992688 isn't having the x-www-browser and gnome-www-browser important functionality? 10:12 -ubottu:#ubuntu-devel- Bug 1992688 in firefox (Ubuntu) "firefox deb not installed" [Undecided, New] https://launchpad.net/bugs/1992688 10:13 < oSoMoN> bdmurray, it is 10:14 < bdmurray> oSoMoN: Can you work with the desktop team on getting it seeded then? 10:15 < oSoMoN> seb128, do we want to seed firefox again for this? ^ 11:27 < seb128> oSoMoN, I think so, I though we had it installed by default on the iso for 22.04 still no? if so how did it drop? 11:29 < bdmurray> I did not see it in the manifest for 22.04 11:34 < seb128> k, maybe I misremember and we just added it back so there was a way to accomodate those requirements 11:35 < seb128> but it would make sense to have it installed by default to have the alternative and the package provide 11:36 < bdmurray> I think the release upgrader would install it on upgrades if it ends up being seeded in kinetic 11:45 < seb128> ack 11:45 < seb128> oSoMoN, +1 from me for doing the change -- 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/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: New 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 1992841] [NEW] Same symbols are exposed in libraries causing potential GType issues
Public bug reported: [ Impact ] Both libfprint-2.so and libfprint-2.so.2.0.0 and libfprint-2-tod.so.1 (that the first one loads) are defining some symbols instead of just referencing them. This can lead to hangs, or deadlocks because we could try to re-define the same GType multiple times. See more details at: https://gitlab.freedesktop.org/3v1n0/libfprint/-/merge_requests/2 [ Test case ] 1. Download this script: https://gitlab.freedesktop.org/3v1n0/libfprint/-/raw/tod/libfprint/tod/tests/check-library-symbols.sh 2. Run it as: libfprint/tod/tests/check-library-symbols.sh \ /usr/lib/x86_64-linux-gnu/libfprint-2.so.2 \ /usr/lib/x86_64-linux-gnu/libfprint-2-tod.so.1 3. Ensure that no duplicated symbols are shown [ Regression potential ] Shared libraries linking with libfprint (or tod) may not find symbols. ** Affects: libfprint (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1992841 Title: Same symbols are exposed in libraries causing potential GType issues Status in libfprint package in Ubuntu: Triaged Bug description: [ Impact ] Both libfprint-2.so and libfprint-2.so.2.0.0 and libfprint-2-tod.so.1 (that the first one loads) are defining some symbols instead of just referencing them. This can lead to hangs, or deadlocks because we could try to re-define the same GType multiple times. See more details at: https://gitlab.freedesktop.org/3v1n0/libfprint/-/merge_requests/2 [ Test case ] 1. Download this script: https://gitlab.freedesktop.org/3v1n0/libfprint/-/raw/tod/libfprint/tod/tests/check-library-symbols.sh 2. Run it as: libfprint/tod/tests/check-library-symbols.sh \ /usr/lib/x86_64-linux-gnu/libfprint-2.so.2 \ /usr/lib/x86_64-linux-gnu/libfprint-2-tod.so.1 3. Ensure that no duplicated symbols are shown [ Regression potential ] Shared libraries linking with libfprint (or tod) may not find symbols. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1992841/+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 1992690] Re: Fix large thumbnails with Nautilus
** Changed in: glib2.0 (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992690 Title: Fix large thumbnails with Nautilus Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 package in Debian: Fix Released Bug description: Impact -- Copying this report from Debian. I have a 4K monitor with 175% fractional scaling. Nautilus 43 broke hi-dpi thumbnailing [1], and goes into an infinite loop trying to create x-large and xx-large thumbnails, consuming CPU forever. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1992690/+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 1992843] [NEW] Windows previewes are not scaled in HiDPI monitors
Public bug reported: [ Impact ] Menu previews in the dock are not scaled when using hi-dpi integer scaling (no fractional scaling) [ Test Case ] 1. Scale your display to 2x or any other integer value 2. Ensure that the fractional scaling is disabled (may require logout/login) 3. Open one or more windows 4. Right-click to see the windows previews 5. The scaled windows should have a size that is scaled and proportional to scaling [ Regression potential ] It's not possible to see / use all the windows previews, or they have wrong aspect ratio. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1992843 Title: Windows previewes are not scaled in HiDPI monitors Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock source package in Jammy: New Bug description: [ Impact ] Menu previews in the dock are not scaled when using hi-dpi integer scaling (no fractional scaling) [ Test Case ] 1. Scale your display to 2x or any other integer value 2. Ensure that the fractional scaling is disabled (may require logout/login) 3. Open one or more windows 4. Right-click to see the windows previews 5. The scaled windows should have a size that is scaled and proportional to scaling [ Regression potential ] It's not possible to see / use all the windows previews, or they have wrong aspect ratio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1992843/+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 1971012] Re: Nautilus windows not respecting workspace isolation
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: New => Triaged -- 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/1971012 Title: Nautilus windows not respecting workspace isolation Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Triaged Bug description: In settings, under multitasking > application switching, setting "include applications from the current workspace only" is supposed to provide workspace isolation, making only apps in the current workspace show in the dock. For example, if I have 2 firefox windows in workspace 1, and a terminal window in workspace 2, terminal should not show as open in the dock in workspace 1, and firefox should not show as open in the dock in workspace 2. Additionally, quitting all windows from right click in the dock should close only all windows of that app in the current workspace. This mostly works correctly, but for some reason some apps, including nautilus and software and updates, do not respect it. If you switch workspaces with them open, the new workspace shows them as having the same number of open windows as the previous workspace, even though no windows are open in that workspace. If you quit with right click from the dock, it sometimes quits all instances across all workspaces. If you open a separate window in the new workspace with right click on the dock, it then updates to the correct number, but the problem then returns on switching back to the previous workspace. If you open and close a window in the new workspace, then switch back to the old one, it is possible to get to a point where despite several windows of the app being open in that workspace, it shows as not open in the dock. The problem persists across different installs and machines To reproduce: Open ubuntu (a live version is fine). Turn on workspace isolation in settings. Pin nautilus to favorites so it shows in the dock. Open a window of nautilus, and a window of some other app (firefox works). Switch workspaces. Observe that an orange dot is still present under nautilus, and it still acts like it is open in the new workspace --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-25 (735 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1971012/+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 1965208] Re: Ubuntu dock is visible too early during the login animation
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1965208 Title: Ubuntu dock is visible too early during the login animation Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock source package in Jammy: New Bug description: Ubuntu dock is visible too early during the login animation: It appears immediately, disappears, then appears again. In jammy this problem only occurred in Xorg sessions, but in kinetic it now occurs in Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965208/+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 1992845] [NEW] Icons are not animated when launching a new application instance
Public bug reported: [ Impact ] Clicking on any ubuntu dock icons doesn't animate animate the icon [ Test case ] - Click on any dash-to-dock icon - The icon should animate on click (when it opens a new application) - The same when launching a new application instance (ctrl + click) [ Regression potential ] Launching an application doesn't work anymore, animations are shown even when is not relevant. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- 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/1992845 Title: Icons are not animated when launching a new application instance Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: [ Impact ] Clicking on any ubuntu dock icons doesn't animate animate the icon [ Test case ] - Click on any dash-to-dock icon - The icon should animate on click (when it opens a new application) - The same when launching a new application instance (ctrl + click) [ Regression potential ] Launching an application doesn't work anymore, animations are shown even when is not relevant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1992845/+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 1992847] [NEW] Left/right arrow in app-grid is not usable when using auto-hiding dock and big icons
Public bug reported: [ Impact ] Left or right icons to switch the application grid is not visible or not properly centered in the overview when using auto-hiding dock [ Test case ] 1. Enable auto-hide in dock 1a. Increase the icons size (to make the bug clearer) 2. Open the app grid (super+a) 3. Try to navigate right/left using the right/left arrows 4. They should be usable and properly centered in the available space [ Regression potential ] App grid has not the proper size. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1992847 Title: Left/right arrow in app-grid is not usable when using auto-hiding dock and big icons Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock source package in Jammy: New Bug description: [ Impact ] Left or right icons to switch the application grid is not visible or not properly centered in the overview when using auto-hiding dock [ Test case ] 1. Enable auto-hide in dock 1a. Increase the icons size (to make the bug clearer) 2. Open the app grid (super+a) 3. Try to navigate right/left using the right/left arrows 4. They should be usable and properly centered in the available space [ Regression potential ] App grid has not the proper size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1992847/+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 1887235] Re: System hangs, syslog filled with: Object St.BoxLayout (...), has been already deallocated - impossible to access it. Called from ubuntu-d...@ubuntu.com/docking.js:
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Fix Released -- 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/1887235 Title: System hangs, syslog filled with: Object St.BoxLayout (...), has been already deallocated - impossible to access it. Called from ubuntu- d...@ubuntu.com/docking.js:184 from tweener.js:322 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Description: Ubuntu 18.04.4 LTS Release: 18.04 I have been having incidents where the system suddenly hangs and nothing except a restart works. The only thing that I can see in logs are the following: Syslog filled up with repeats of: ``` Jul 11 20:27:18 gnome-shell[3317]: Object St.BoxLayout (0x55b1d8322450), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: == Stack trace for context 0x55b1d37ee320 == Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #0 0x7fff7db4aa50 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:184 (0x7f523f3bfab0 @ 35) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #1 0x7fff7db4b480 b resource:///org/gnome/gjs/modules/tweener/tweener.js:322 (0x7f52845d2bc0 @ 1462) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #2 0x7fff7db4b530 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f52845d2c48 @ 100) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #3 0x7fff7db4b5c0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f52845d2cd0 @ 10) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #4 0x7fff7db4b6b0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f52845d2230 @ 386) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #5 0x7fff7db4b760 b resource:///org/gnome/shell/ui/tweener.js:244 (0x7f52845cf808 @ 159) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #6 0x7fff7db4b7c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f52845b5de0 @ 71) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #7 0x7fff7db4b860 b resource:///org/gnome/shell/ui/tweener.js:219 (0x7f52845cf780 @ 15) Jul 11 20:27:18 gnome-shell[3317]: clutter_actor_queue_relayout: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 11 20:27:18 gnome-shell[3317]: Object St.BoxLayout (0x55b1d8322450), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: == Stack trace for context 0x55b1d37ee320 == Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #0 0x7fff7db4aa50 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:184 (0x7f523f3bfab0 @ 35) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #1 0x7fff7db4b480 b resource:///org/gnome/gjs/modules/tweener/tweener.js:322 (0x7f52845d2bc0 @ 1462) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #2 0x7fff7db4b530 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f52845d2c48 @ 100) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #3 0x7fff7db4b5c0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f52845d2cd0 @ 10) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #4 0x7fff7db4b6b0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f52845d2230 @ 386) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #5 0x7fff7db4b760 b resource:///org/gnome/shell/ui/tweener.js:244 (0x7f52845cf808 @ 159) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #6 0x7fff7db4b7c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f52845b5de0 @ 71) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #7 0x7fff7db4b860 b resource:///org/gnome/shell/ui/tweener.js:219 (0x7f52845cf780 @ 15) Jul 11 20:27:18 gnome-shell[3317]: clutter_actor_queue_relayout: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 11 20:27:18 gnome-shell[3317]: Object St.BoxLayout (0x55b1d8322450), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 11 20:27:18 gnome-shell[3317]: clutter_actor_queue_relayout: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: == Stack trace for context 0x55b1d37ee320 == Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #0 0x7fff7db4aa50 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:184 (0x7f523f3bfab0 @ 35) Jul 11 20:27:18 org.gnome.Shell.desktop[3317]: #1 0x7fff7db4b480 b resource:///org/gnome/gjs/modules/tweener/tweener.js:322 (0x7f52845d2bc0 @ 1462)
[Desktop-packages] [Bug 1965208] Re: Ubuntu dock is visible too early during the login animation
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1965208 Title: Ubuntu dock is visible too early during the login animation Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Bug description: Ubuntu dock is visible too early during the login animation: It appears immediately, disappears, then appears again. In jammy this problem only occurred in Xorg sessions, but in kinetic it now occurs in Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965208/+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 1992847] Re: Left/right arrow in app-grid is not usable when using auto-hiding dock and big icons
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1992847 Title: Left/right arrow in app-grid is not usable when using auto-hiding dock and big icons Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock source package in Jammy: In Progress Bug description: [ Impact ] Left or right icons to switch the application grid is not visible or not properly centered in the overview when using auto-hiding dock [ Test case ] 1. Enable auto-hide in dock 1a. Increase the icons size (to make the bug clearer) 2. Open the app grid (super+a) 3. Try to navigate right/left using the right/left arrows 4. They should be usable and properly centered in the available space [ Regression potential ] App grid has not the proper size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1992847/+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 1992845] Re: Icons are not animated when launching a new application instance
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1992845 Title: Icons are not animated when launching a new application instance Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock source package in Jammy: In Progress Bug description: [ Impact ] Clicking on any ubuntu dock icons doesn't animate animate the icon [ Test case ] - Click on any dash-to-dock icon - The icon should animate on click (when it opens a new application) - The same when launching a new application instance (ctrl + click) [ Regression potential ] Launching an application doesn't work anymore, animations are shown even when is not relevant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1992845/+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 1992843] Re: Windows previewes are not scaled in HiDPI monitors
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1992843 Title: Windows previewes are not scaled in HiDPI monitors Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock source package in Jammy: In Progress Bug description: [ Impact ] Menu previews in the dock are not scaled when using hi-dpi integer scaling (no fractional scaling) [ Test Case ] 1. Scale your display to 2x or any other integer value 2. Ensure that the fractional scaling is disabled (may require logout/login) 3. Open one or more windows 4. Right-click to see the windows previews 5. The scaled windows should have a size that is scaled and proportional to scaling [ Regression potential ] It's not possible to see / use all the windows previews, or they have wrong aspect ratio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1992843/+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
** Merge proposal linked: https://code.launchpad.net/~osomon/ubuntu-seeds/+git/ubuntu/+merge/431530 -- 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: In Progress Status in firefox source package in Jammy: New Status in ubuntu-meta source package in Jammy: New 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 1983130] Re: Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so.
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1983130 Title: Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so. Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock source package in Jammy: In Progress Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 Expected behavior: Dock set to auto-hide would remain shown after either a right-click menu option is selected, or a right-click menu is cancelled. Actual behavior: Dock hides after a right-click menu closes even when there are no windows in its space. Additional notes: Dock can be temporarily reset to its normal behavior when one of these actions are performed: - when a window enters the dock's usual space - when the "show applications" menu is opened and closed - when a maximized window is opened and closed/minimized To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1983130/+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
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: ubuntu-meta (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: In Progress Status in firefox source package in Jammy: New Status in ubuntu-meta source package in Jammy: New 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 1992688] Re: firefox deb not installed
** Also affects: ubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: firefox (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu Jammy) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: ubuntu-meta (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: In Progress Status in firefox source package in Jammy: New Status in ubuntu-meta source package in Jammy: New 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 1992852] [NEW] Update gnome-desktop to 42.5
Public bug reported: Impact -- The only thing this update does is update the GNOME version number shown in the GNOME Settings > About dialog from 42.4 to 42.5 That's desired because in general we are running 42.5 Test Case - Install the updated packages Open the Settings app. Scroll down in the left sidebar and click About The GNOME Version should be 42.3 What Could Go Wrong --- Because this is part of core GNOME, it falls under the https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- GNOME 43 will use gnome-shell to display the version number so that's one less SRU required for future Ubuntu releases. ** Affects: gnome-desktop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1992852 Title: Update gnome-desktop to 42.5 Status in gnome-desktop package in Ubuntu: New Bug description: Impact -- The only thing this update does is update the GNOME version number shown in the GNOME Settings > About dialog from 42.4 to 42.5 That's desired because in general we are running 42.5 Test Case - Install the updated packages Open the Settings app. Scroll down in the left sidebar and click About The GNOME Version should be 42.3 What Could Go Wrong --- Because this is part of core GNOME, it falls under the https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- GNOME 43 will use gnome-shell to display the version number so that's one less SRU required for future Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1992852/+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 1992847] Re: Left/right arrow in app-grid is not usable when using auto-hiding dock and big icons
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 74ubuntu2 --- gnome-shell-extension-ubuntu-dock (74ubuntu2) kinetic; urgency=medium [ Marco Trevisan (Treviño) ] * debian/control: Update maintainer to myself * docking: Don't try to call a null callback (LP: #1989170) * docking: Do not wait for dash animation two times with no overview (LP: #1965208) * docking: Ensure we perform the startup animation completely on docks updates (LP: #1965208, LP: #1989170) * docking: Use a try/catch statement on our promise to show errors in case (LP: #1989170) * windowPreviews: Take global scaling in account to set the clone sizes (LP: #1992843) * docking: Keep overview controls layout proportions when resizing it (LP: #1992847) * docking: Also reduce the app grid area when in auto-hide mode (LP: #1992847) * docking: Use an even width for the overview content area (LP: #1979096) * docking: Check if autohide or intellihide is enabled on menu closed (LP: #1983130) * appIcons: Ensure icons are animated when new instances are launched (LP: #1992845) * docking: Do not try to focus potentially undefined window * appSpread: Do not anything on destruction if not supported * docking: Ignore hover changes if overview is visible (LP: #1983130) [ Daniel van Vugt ] * docking: Handle when dash is destroyed during the login animation (LP: #1989170) -- Marco Trevisan (Treviño) Thu, 13 Oct 2022 22:00:20 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: In Progress => Fix Released -- 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/1992847 Title: Left/right arrow in app-grid is not usable when using auto-hiding dock and big icons Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: In Progress Bug description: [ Impact ] Left or right icons to switch the application grid is not visible or not properly centered in the overview when using auto-hiding dock [ Test case ] 1. Enable auto-hide in dock 1a. Increase the icons size (to make the bug clearer) 2. Open the app grid (super+a) 3. Try to navigate right/left using the right/left arrows 4. They should be usable and properly centered in the available space [ Regression potential ] App grid has not the proper size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1992847/+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 1992843] Re: Windows previewes are not scaled in HiDPI monitors
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 74ubuntu2 --- gnome-shell-extension-ubuntu-dock (74ubuntu2) kinetic; urgency=medium [ Marco Trevisan (Treviño) ] * debian/control: Update maintainer to myself * docking: Don't try to call a null callback (LP: #1989170) * docking: Do not wait for dash animation two times with no overview (LP: #1965208) * docking: Ensure we perform the startup animation completely on docks updates (LP: #1965208, LP: #1989170) * docking: Use a try/catch statement on our promise to show errors in case (LP: #1989170) * windowPreviews: Take global scaling in account to set the clone sizes (LP: #1992843) * docking: Keep overview controls layout proportions when resizing it (LP: #1992847) * docking: Also reduce the app grid area when in auto-hide mode (LP: #1992847) * docking: Use an even width for the overview content area (LP: #1979096) * docking: Check if autohide or intellihide is enabled on menu closed (LP: #1983130) * appIcons: Ensure icons are animated when new instances are launched (LP: #1992845) * docking: Do not try to focus potentially undefined window * appSpread: Do not anything on destruction if not supported * docking: Ignore hover changes if overview is visible (LP: #1983130) [ Daniel van Vugt ] * docking: Handle when dash is destroyed during the login animation (LP: #1989170) -- Marco Trevisan (Treviño) Thu, 13 Oct 2022 22:00:20 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: In Progress => Fix Released -- 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/1992843 Title: Windows previewes are not scaled in HiDPI monitors Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: In Progress Bug description: [ Impact ] Menu previews in the dock are not scaled when using hi-dpi integer scaling (no fractional scaling) [ Test Case ] 1. Scale your display to 2x or any other integer value 2. Ensure that the fractional scaling is disabled (may require logout/login) 3. Open one or more windows 4. Right-click to see the windows previews 5. The scaled windows should have a size that is scaled and proportional to scaling [ Regression potential ] It's not possible to see / use all the windows previews, or they have wrong aspect ratio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1992843/+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 1992845] Re: Icons are not animated when launching a new application instance
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 74ubuntu2 --- gnome-shell-extension-ubuntu-dock (74ubuntu2) kinetic; urgency=medium [ Marco Trevisan (Treviño) ] * debian/control: Update maintainer to myself * docking: Don't try to call a null callback (LP: #1989170) * docking: Do not wait for dash animation two times with no overview (LP: #1965208) * docking: Ensure we perform the startup animation completely on docks updates (LP: #1965208, LP: #1989170) * docking: Use a try/catch statement on our promise to show errors in case (LP: #1989170) * windowPreviews: Take global scaling in account to set the clone sizes (LP: #1992843) * docking: Keep overview controls layout proportions when resizing it (LP: #1992847) * docking: Also reduce the app grid area when in auto-hide mode (LP: #1992847) * docking: Use an even width for the overview content area (LP: #1979096) * docking: Check if autohide or intellihide is enabled on menu closed (LP: #1983130) * appIcons: Ensure icons are animated when new instances are launched (LP: #1992845) * docking: Do not try to focus potentially undefined window * appSpread: Do not anything on destruction if not supported * docking: Ignore hover changes if overview is visible (LP: #1983130) [ Daniel van Vugt ] * docking: Handle when dash is destroyed during the login animation (LP: #1989170) -- Marco Trevisan (Treviño) Thu, 13 Oct 2022 22:00:20 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: In Progress => Fix Released -- 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/1992845 Title: Icons are not animated when launching a new application instance Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: In Progress Bug description: [ Impact ] Clicking on any ubuntu dock icons doesn't animate animate the icon [ Test case ] - Click on any dash-to-dock icon - The icon should animate on click (when it opens a new application) - The same when launching a new application instance (ctrl + click) [ Regression potential ] Launching an application doesn't work anymore, animations are shown even when is not relevant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1992845/+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