[Desktop-packages] [Bug 1952217] Re: bluetoothd coredumps from double free on connection of headset
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1952217 Title: bluetoothd coredumps from double free on connection of headset Status in bluez package in Ubuntu: Expired Bug description: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+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 1952375] Re: Blutooth headset not taking
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1952375 Title: Blutooth headset not taking Status in bluez package in Ubuntu: Expired Bug description: Blutooth Headset problem ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 26 01:09:24 2021 InstallationDate: Installed on 2020-07-22 (491 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-54 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=c9b8ebcf-747e-454e-8dfb-68b609629c3a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to impish on 2021-10-15 (41 days ago) dmi.bios.date: 08/01/2019 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Doc_WC dmi.board.vendor: CML dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd08/01/2019:br1.11:efr1.6:svnAcer:pnAspireA515-54:pvrV1.11:rvnCML:rnDoc_WC:rvrV1.11:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 84:FD:D1:EA:D2:2D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:151467 acl:66 sco:0 events:20824 errors:0 TX bytes:13788724 acl:20413 sco:0 commands:299 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952375/+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 1788535] Re: gnome-control-center shows 120Hz display frequencies that the display doesn't support (really only 60Hz hardware)
** Changed in: mutter (Ubuntu) Status: Fix Committed => In Progress -- 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/1788535 Title: gnome-control-center shows 120Hz display frequencies that the display doesn't support (really only 60Hz hardware) Status in Mutter: New Status in mutter package in Ubuntu: In Progress Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/275 --- gnome-control-center shows 120Hz display frequencies that the display doesn't support (it's really only 60Hz) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.29.91-1 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 Date: Thu Aug 23 11:08:09 2018 InstallationDate: Installed on 2018-08-17 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1788535/+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 1872870] Re: When zoom is enabled, mouse pointer leaves square trails on desktop
** Changed in: mutter (Ubuntu) Status: Fix Committed => In Progress -- 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/1872870 Title: When zoom is enabled, mouse pointer leaves square trails on desktop Status in Mutter: Unknown Status in mutter package in Ubuntu: In Progress Bug description: Problem: When you turn on Zoom from the Accessibility menu, the mouse leaves square shaped trails as it moves. Steps to Reproduce: 1. Under the Settings applet's Accessibility menu, turn on Zoom. 2. Observe the mouse cursor leaving little square patterns wherever it goes, obscuring whatever you're trying to work on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 21:50:16 2020 InstallationDate: Installed on 2020-01-09 (96 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: meta-gnome3 UpgradeStatus: Upgraded to focal on 2020-01-24 (82 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1872870/+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 1820523] Re: OSK Enter, space and backspace keys don't work when typing in Greek
** Changed in: mutter (Ubuntu) Status: Fix Committed => In Progress -- 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/1820523 Title: OSK Enter, space and backspace keys don't work when typing in Greek Status in GNOME Shell: New Status in mutter package in Ubuntu: In Progress Bug description: The enter, space and backspace keys on the Ubuntu On-screen keyboard don't work when typing in Greek. Applies to Ubuntu 18.10 and 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1820523/+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 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
** Changed in: mutter (Ubuntu) Status: Fix Committed => In Progress -- 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/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: In Progress Bug description: When a new Wayland session is created from a login, Alt-tab works as expected to change windows. After sometime Alt-tab fails to do anything (super-tab still works to change applications) and the following error is created in syslog: gnome-shell[18]: JS ERROR: TypeError: window is null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24 The only workaround I have found is to logout and log back in, however after some time the error repeats itself. Ubuntu 21.04 gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 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: Tue Jun 29 10:53:32 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-11 (230 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
** Changed in: mutter (Ubuntu) Status: Fix Committed => 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/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Unknown Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: In Progress Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 1933186] Re: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from met
** Changed in: mutter (Ubuntu) Status: Fix Committed => In Progress -- 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/1933186 Title: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from meta_window_force_placement() Status in Mutter: Unknown Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Unknown Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7ae33f650c2de2c5580905f0c63e5b6c35fb46c6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1933186/+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 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
** Changed in: mutter (Ubuntu) Status: Fix Committed => In Progress -- 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/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: In Progress Bug description: When clock changes value, it doesn't displaying time properly To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1882291/+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 1945121] Re: Ubuntu auto-suspends when I unplug my laptop after not having used it for a few minutes.
** Changed in: mutter (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1945121 Title: Ubuntu auto-suspends when I unplug my laptop after not having used it for a few minutes. Status in GNOME Settings Daemon: Unknown Status in Mutter: Unknown Status in gnome-settings-daemon package in Ubuntu: Invalid Status in mutter package in Ubuntu: In Progress Bug description: I'm using Ubuntu 20.04.3 LTS I have my power settings so that Ubuntu will never auto-suspend if plugged in, but will do so after 20 minutes if on battery power. If I leave it plugged in but untouched for 20 minutes, and then unplug it (to move it to another room when I come back to it), then it suspends on the way there. It would seem more intuitive that unplugging/plugging in would be considered interaction, and would reset the delay. The expected behavior, in that case, would be that it gets unplugged, stays on, and then suspends after 20 minutes if there is no further interaction. I know any official fix would probably take a while, if one is even considered. Is there any workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.91.03 Fri Jul 2 06:04:10 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 26 14:35:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.91.03, 5.11.0-34-generic, x86_64: installed nvidia, 460.91.03, 5.11.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Mobile) [1043:18fe] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti Mobile] [1043:18fe] InstallationDate: Installed on 2021-02-21 (216 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:5666 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 005: ID 1b1c:1b5c Corsair CORSAIR NIGHTSWORD RGB Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. TUF GAMING FX504GE_FX80GE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic root=UUID=94577a37-4156-ac57-02e9-af5914abc257 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX504GE.320 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX504GE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX504GE.320:bd06/19/2020:br5.13:efr1.16:svnASUSTeKCOMPUTERINC.:pnTUFGAMINGFX504GE_FX80GE:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnFX504GE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF GAMING dmi.product.name: TUF GAMING FX504GE_FX80GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-inpu
[Desktop-packages] [Bug 1947820] Re: [SRU] Backport xorg-server 1.20.13 to focal
** Changed in: amd Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1947820 Title: [SRU] Backport xorg-server 1.20.13 to focal Status in amd: Fix Released Status in OEM Priority Project: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in xorg-server source package in Focal: Fix Released Bug description: [Impact] The delay phenomenon is serious in 'External display mode' during the 'On-demand' mode working. Please reference lp:1940247 and lp:1919118. [Fix] I installed 21.10 on Raptor12(ThinkPad-P15-Gen-2i), with xorg-server 2:1.20.13-1ubuntu1 and nvidia-495.38 test driver, this issue is solved. But in 20.04, it's still 2:1.20.11-1ubuntu1~20.04.2. [Test] On Raptor12(ThinkPad-P15-Gen-2i), P17 Gen 2 and P1 Gen 4, with latest 20.04, it could be reproduced. [Where problems could occur] Although the nvidia driver is not released, I thought it's no harm to upgrade xorg-server first. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1947820/+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 1958852] Re: Auto-rotation does not work anymore
Thanks for the bug report. You seem to be using an unsupported kernel AND have unsupported Mesa packages installed from a PPA. So it's unsurprising that rotation and hardware acceleration might not work. If you don't know how to fix this yourself then please just reinstall Ubuntu, and avoid installing PPAs or custom kernels in future. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1958852 Title: Auto-rotation does not work anymore Status in Ubuntu: Invalid Bug description: With my Radeon Vega graphics card auto-rotation of the screen used to work in 21.04 but does not work anymore in 21.10. Also Cinnamon (which I have uninstall now) shows an error, saying that hardware acceleration does not work. output of `lspci | grep VGA`: ```04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] (rev c1) 04:00.7 Non-VGA unclassified device: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/Renoir Sensor Fusion Hub `` ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.14.21-051421-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 12:20:21 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-02-09 (714 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.21-051421-generic root=UUID=4bbf320c-9d1b-4cb2-a03e-a7f170d88509 ro noplymouth resume=/swapfile radeon.si_support=1 radeon.cik_support=1 amd_iommu=off SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.release: 15.19 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 41.36 dmi.modalias: dmi:bvnAMI:bvrF.19:bd12/26/2019:br15.19:efr41.36:svnHP:pnHPENVYx360Convertible13-ar0xxx:pvr:rvnHP:rn85DE:rvr41.36:cvnHP:ct31:cvrChassisVersion:sku7BR48EA#ABD: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ar0xxx dmi.product.sku: 7BR48EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.3.2~kisak1~i version.libgl1-mesa-glx: libgl1-mesa-glx 21.3.2~kisak1~i version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1958852/+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 1948008] Re: Copying and pasting files between desktop and Nautilus does not work
Yes the fix is in gnome-shell-extension-desktop-icons-ng >= 34 ** Bug watch added: gitlab.com/rastersoft/desktop-icons-ng/-/issues #195 https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/195 ** Also affects: gnome-shell-extension-desktop-icons-ng via https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/195 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1948008 Title: Copying and pasting files between desktop and Nautilus does not work Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Confirmed Status in gnome-shell-extension-desktop-icons source package in Focal: Confirmed Status in gnome-shell-extension-desktop-icons-ng source package in Focal: Invalid Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Invalid Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: Won't Fix Status in gnome-shell source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons source package in Impish: Invalid Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Confirmed Bug description: [Impact] * After upstream Nautilus has reverted the following commit [1] related to upstream bug [2] the desktop icons extension lost it's ability to copy to/from nautilus. * This is related to the fact that before there was some metadata passed along in the clipboard along with text data. This was causing issues with compatibility with some applications that were not expecting any metadata (MIME type in this case) was glued to the text clipboard contents. Hence, it was reverted upstream [3]. * Fixing the root cause of this issue required changes to Nautilus [3], gnome-shell [4] and desktop-icons [5] [6]. Nautilus and gnome- shell parts are already implemented and present in Hirsute and Impish. [Test Plan] 1) Make sure desktop-icons extension is enabled. 2) Open nautilus window and copy any file from there by right-clicking and selecting "Copy" from the popup menu. 3) Right-click on desktop and select "Paste" from the context menu. Expected result: selected file is copied to the desktop. Actual result: "Paste" item is disabled in the menu. [Where problems could occur] * Mixing a version of nautilus without commit [3] and fixed version of desktop-icons may still lead to a scenario when copying will not work. * Any extension/application copying to desktop using the smuggled-in- text clipboard behavior should be expected to stop working. [Other Info] [1] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/289 [2] https://gitlab.gnome.org/GNOME/nautilus/-/issues/634 [3] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573 [4] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1321 [5] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [6] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1948008/+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 1958684] Re: gnome-shell crashed with SIGFPE in meta_wayland_xdg_toplevel_send_configure() from meta_window_wayland_configure()
Yes the fix is in Ubuntu 21.10 and later. If you would like it in 20.04 then please add tag 'rls-ff-incoming'. Although I don't know how feasible or soon that would be. -- 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/1958684 Title: gnome-shell crashed with SIGFPE in meta_wayland_xdg_toplevel_send_configure() from meta_window_wayland_configure() Status in mutter package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/bd270ee843b327813e28ccddde4a1357b64e1326 --- To reproduce with Ubuntu 20.04: 1. Run Gnome or the Gnome-based Ubuntu Desktop on Wayland. 2. Download and install the snapshot build of Qt Creator from https://master.qt.io/snapshots/qtcreator/6.0/6.0.3/624/qt-creator-opensource-linux-x86_64-6.0.3_624.run Sorry for the inconvenience that the installer requires an account. You can easily get one free of charge. Let me know if you need help with that. 3. Start the installed Qt Creator with parameter "-tcs". "-tcs" will ignore local settings saved for Qt Creator, so it will not mess up settings you might have. The log-in session crashes. All running applications are being closed immediately and you get back to the login screen. Sure, there might be something wrong in our snapshot package, but no matter how wrong our package might be, Wayland/Gnome should not crash, should they? If I should provide any further information, please let me know. gnome-shell: 3.36.9-0ubuntu0.20.04.2 libwayland-server0: 1.18.0-1 xwayland: 2:1.20.13-1ubuntu1~20.04.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 18:18:40 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1621432157 InstallationDate: Installed on 2021-12-17 (35 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/qtrob RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 Signal: 8 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGFPE in g_closure_invoke() 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/mutter/+bug/1958684/+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 1958733] Re: Settings menu will not open. Other things seem messed up.
** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1958733 Title: Settings menu will not open. Other things seem messed up. Status in gnome-control-center package in Ubuntu: Invalid Bug description: I installed DWM and was learning how to use the shortcuts. I was mashing keys because I had no idea what the shorcuts were and I am a newb. When I rebooted into DWM, it said it couldn't open firefox because of an IBUS warning. When I rebooted again and went into the normal Ubuntu window manager everthing worked fine. When I went to click on settings, the settings menu would not open. I tried to open settings by using the following command "gnome-control-center display" which did not work. Should I just reinstall everything? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 22 14:53:58 2022 InstallationDate: Installed on 2022-01-19 (3 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1958733/+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 1947149] Re: Dock auto-hide off but hidden on screen unlock
** Changed in: gnome-shell-extension-ubuntu-dock (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-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1947149 Title: Dock auto-hide off but hidden on screen unlock Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: When the dock is set to "Auto-hide the Dock" = Off, the dock will un- hide when logging on. Both on boot and after locking the user. This causes any open full-screen windows to move and resize as needed. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 21.10 Release: 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-shell-extension-ubuntu-dock: Installed: 70~ubuntu3 Candidate: 70~ubuntu3 Version table: *** 70~ubuntu3 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish/main i386 Packages 100 /var/lib/dpkg/status 3) What you expected to happen The dock to start displayed (un-hidden) as per the settings. And not move. 4) What happened instead The dock appears from the left, as if hidden. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1947149/+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 1958890] Re: Xorg freeze
** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Summary changed: - Xorg freeze + [amdgpu] the screen is flickering after waking up from sleep -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1958890 Title: [amdgpu] the screen is flickering after waking up from sleep Status in linux-hwe-5.13 package in Ubuntu: New Bug description: the screen is flcikering after waking up from sleep ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 23:04:53 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.0.15-1098277: added ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f95] InstallationDate: Installed on 2022-01-11 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 82KT ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=7e63c3e2-afff-4841-8da3-9dad122a8352 ro nouveau.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 07/23/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: GLCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55726WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14ALC6 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrGLCN40WW:bd07/23/2021:br1.40:efr1.40:svnLENOVO:pn82KT:pvrIdeaPad314ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrIdeaPad314ALC6:skuLENOVO_MT_82KT_BU_idea_FM_IdeaPad314ALC6: dmi.product.family: IdeaPad 3 14ALC6 dmi.product.name: 82KT dmi.product.sku: LENOVO_MT_82KT_BU_idea_FM_IdeaPad 3 14ALC6 dmi.product.version: IdeaPad 3 14ALC6 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958890/+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 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken
** Description changed: + [ Impact ] + Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or- previews" options no longer work as expected. + + [ Test case ] + + 1. gsettings set org.gnome.shell.extensions.dash-to-dock click-action "previews" + - Open multiple windows for an application + - Click on the icon, previews should be shown + + 2. gsettings set org.gnome.shell.extensions.dash-to-dock click-action "minimize-or-previews" + - Open multiple windows for an application + - Click on the icon, previews should be shown + + [ Regression potential ] + + Wrong action is taken if an application has urgent windows + + + For "previews": No previews are shown when clicking on the app icon. For "minimize-or-previews": When multiple windows of the same application are open and I click on the app icon, no previews are shown anymore. - Schema: org.gnome.shell.extensions.dash-to-dock Name: click-action Value: "minimize-or-previews" Value: "previews" - Description: Ubuntu 21.10 Release: 21.10 gnome-shell-extension-ubuntu-dock: - Installed: 70~ubuntu3 + Installed: 70~ubuntu3 - ProblemType: Bug - DistroRelease: Ubuntu 21.10 + ProblemType: BugDistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 11:32:51 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-21 (1090 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) - PackageArchitecture: all - SourcePackage: gnome-shell-extension-ubuntu-dock + PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago) -- 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/1947445 Title: Click actions "previews" and "minimize-or-previews" are broken Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Impish: In Progress Bug description: [ Impact ] Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or- previews" options no longer work as expected. [ Test case ] 1. gsettings set org.gnome.shell.extensions.dash-to-dock click-action "previews" - Open multiple windows for an application - Click on the icon, previews should be shown 2. gsettings set org.gnome.shell.extensions.dash-to-dock click-action "minimize-or-previews" - Open multiple windows for an application - Click on the icon, previews should be shown [ Regression potential ] Wrong action is taken if an application has urgent windows For "previews": No previews are shown when clicking on the app icon. For "minimize-or-previews": When multiple windows of the same application are open and I click on the app icon, no previews are shown anymore. Schema: org.gnome.shell.extensions.dash-to-dock Name: click-action Value: "minimize-or-previews" Value: "previews" Description: Ubuntu 21.10 Release: 21.10 gnome-shell-extension-ubuntu-dock: Installed: 70~ubuntu3 ProblemType: BugDistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 11:32:51 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-21 (1090 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1947445/+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 1949572] Re: Shell freeze after right click on the app in the dock
This was fixed in gnome-shell-extension-ubuntu-dock_72~ubuntu1 ** No longer affects: gnome-shell-extension-dashtodock (Ubuntu Impish) ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Status: In Progress => Won't Fix ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Triaged => Fix Released ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: Triaged => In Progress ** Description changed: + [ Impact ] + When you click the icon of the app in the dock to open it for the first time and then immediately right click to see options, everything freezes and you are forced to reboot. + [ Test case ] + + - Under wayland, open an application and immediately right-click its icon + - The shell should show the application window that has just been opened in + the windows submenu, and continue working + + [ Regression potential] + + No windows previews are showing in the application menu + + --- + I'm using Ubuntu 21.10. I installed it today. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 - CurrentDesktop: ubuntu:GNOME - DistroRelease: Ubuntu 21.10 + CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-03 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Tags: impish wayland-session Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True -- 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/1949572 Title: Shell freeze after right click on the app in the dock Status in gnome-shell-extension-appindicator package in Ubuntu: Invalid Status in gnome-shell-extension-dashtodock package in Ubuntu: Won't Fix Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Impish: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Impish: In Progress Bug description: [ Impact ] When you click the icon of the app in the dock to open it for the first time and then immediately right click to see options, everything freezes and you are forced to reboot. [ Test case ] - Under wayland, open an application and immediately right-click its icon - The shell should show the application window that has just been opened in the windows submenu, and continue working [ Regression potential] No windows previews are showing in the application menu --- I'm using Ubuntu 21.10. I installed it today. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-03 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Tags: impish wayland-session Uname: Linux 5.13.0-20-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-appindicator/+bug/1949572/+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 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: High => Low ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Importance: High => Low ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: New => 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/1947445 Title: Click actions "previews" and "minimize-or-previews" are broken Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Impish: In Progress Bug description: Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or- previews" options no longer work as expected. For "previews": No previews are shown when clicking on the app icon. For "minimize-or-previews": When multiple windows of the same application are open and I click on the app icon, no previews are shown anymore. Schema: org.gnome.shell.extensions.dash-to-dock Name: click-action Value: "minimize-or-previews" Value: "previews" Description: Ubuntu 21.10 Release: 21.10 gnome-shell-extension-ubuntu-dock: Installed: 70~ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 11:32:51 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-21 (1090 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1947445/+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 1874578] Re: Dock has very long load time when show-mounts is enabled
** Description changed: + [ Impact ] + + Icons are not showing on loading when mount-points are showing + + [ Test case ] + + - Start a new session (ensure that the system has mounted devices) + - The launcher icons should show promptly without any delay + + [ Regression potential ] + + Mounted devices will have wrong or no icon. + + + I just upgraded from Ubuntu 18.04 to 20.04. When I boot my system I have to wait at least 10 to 15 seconds for the application icons to load on dock. Meanwhile everything else seems to be working properly. I didn't experience this behavior in Ubuntu 18.04. Also the dock doesn't trigger when I move my cursor to the left of the screen. (I have set the docker to Auto-Hide mode and it's position is on the left of my screen). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip - CurrentDesktop: ubuntu:GNOME - DistroRelease: Ubuntu 20.04 + CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-08-03 (1359 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal third-party-packages wayland-session Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True -- 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/1874578 Title: Dock has very long load time when show-mounts is enabled Status in Dash to dock: New Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Impish: In Progress Bug description: [ Impact ] Icons are not showing on loading when mount-points are showing [ Test case ] - Start a new session (ensure that the system has mounted devices) - The launcher icons should show promptly without any delay [ Regression potential ] Mounted devices will have wrong or no icon. I just upgraded from Ubuntu 18.04 to 20.04. When I boot my system I have to wait at least 10 to 15 seconds for the application icons to load on dock. Meanwhile everything else seems to be working properly. I didn't experience this behavior in Ubuntu 18.04. Also the dock doesn't trigger when I move my cursor to the left of the screen. (I have set the docker to Auto-Hide mode and it's position is on the left of my screen). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-08-03 (1359 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal third-party-packages wayland-session Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1874578/+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 1951599] Re: gnome-shell logs errors when ejecting SD card
** Also affects: gnome-shell-extension-dashtodock (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-dashtodock (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-dashtodock (Ubuntu Impish) Status: New => Fix Committed ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Importance: Undecided => Medium ** Description changed: + [ Impact ] + When I click eject SD card in Files(nautilus), I found the gnome-shell reported some crash logs. + + [ Test case ] + + - Mount a device + - Eject the device + - No errors should be shown and the device re-mountable + + [ Regression Potential ] + + Devices could be leaked if gc doesn't work as expected + + + --- Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object .Gjs_components_autorunManager_AutorunSource (0x55a9d8e846e0), has been already deallocated — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object Gio.Settings (0x55a9db521970), 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. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: == Stack trace for context 0x55a9d8a00120 == Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #0 7ffc0b63cc20 b resource:///org/gnome/shell/ui/messageTray.js:785 (bc6f58577e0 @ 149) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #1 55a9d8f150b0 i resource:///org/gnome/shell/ui/components/autorunManager.js:270 (1ec3f0bf4060 @ 69) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #2 55a9d8f15018 i resource:///org/gnome/shell/ui/components/autorunManager.js:176 (1ec3f0bf4290 @ 25) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #3 7ffc0b63d8c0 b self-hosted:850 (1ec3f0b2a650 @ 454) ** No longer affects: gnome-shell-extension-dashtodock (Ubuntu Impish) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: New => In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) 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/1951599 Title: gnome-shell logs errors when ejecting SD card Status in OEM Priority Project: Triaged Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Impish: In Progress Bug description: [ Impact ] When I click eject SD card in Files(nautilus), I found the gnome-shell reported some crash logs. [ Test case ] - Mount a device - Eject the device - No errors should be shown and the device re-mountable [ Regression Potential ] Devices could be leaked if gc doesn't work as expected --- Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object .Gjs_components_autorunManager_AutorunSource (0x55a9d8e846e0), has been already deallocated — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object Gio.Settings (0x55a9db521970), 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. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: == Stack trace for context 0x55a9d8a00120 == Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #0 7ffc0b63cc20 b resource:///org/gnome/shell/ui/messageTray.js:785 (bc6f58577e0 @ 149) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #1 55a9d8f150b0 i resource:///org/gnome/shell/ui/components/autorunManager.js:270 (1ec3f0bf4060 @ 69) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #2 55a9d8f15018 i resource:///org/gnome/shell/ui/components/autorunManager.js:176 (1ec3f0bf4290 @ 25) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #3 7ffc0b63d8c0 b self-hosted:
[Desktop-packages] [Bug 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Importance: Undecided => High ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Assignee: (unassigned) => Pepijn Bogaard (pbgrd) -- 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/1947445 Title: Click actions "previews" and "minimize-or-previews" are broken Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Impish: New Bug description: Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or- previews" options no longer work as expected. For "previews": No previews are shown when clicking on the app icon. For "minimize-or-previews": When multiple windows of the same application are open and I click on the app icon, no previews are shown anymore. Schema: org.gnome.shell.extensions.dash-to-dock Name: click-action Value: "minimize-or-previews" Value: "previews" Description: Ubuntu 21.10 Release: 21.10 gnome-shell-extension-ubuntu-dock: Installed: 70~ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 11:32:51 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-21 (1090 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1947445/+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 1874578] Re: Dock has very long load time when show-mounts is enabled
** Also affects: gnome-shell-extension-dashtodock (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-dashtodock (Ubuntu Impish) Status: New => Confirmed ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Importance: Undecided => Low ** No longer affects: gnome-shell-extension-dashtodock (Ubuntu Impish) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: New => 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/1874578 Title: Dock has very long load time when show-mounts is enabled Status in Dash to dock: New Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Impish: In Progress Bug description: [ Impact ] Icons are not showing on loading when mount-points are showing [ Test case ] - Start a new session (ensure that the system has mounted devices) - The launcher icons should show promptly without any delay [ Regression potential ] Mounted devices will have wrong or no icon. I just upgraded from Ubuntu 18.04 to 20.04. When I boot my system I have to wait at least 10 to 15 seconds for the application icons to load on dock. Meanwhile everything else seems to be working properly. I didn't experience this behavior in Ubuntu 18.04. Also the dock doesn't trigger when I move my cursor to the left of the screen. (I have set the docker to Auto-Hide mode and it's position is on the left of my screen). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-08-03 (1359 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal third-party-packages wayland-session Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1874578/+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 1949352] Re: Removable drives are not auto-mounted after screen lock/unlock
** Description changed: + [ Impact ] + If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. + [ Test case ] + + - Mount a device + - Lock the screen + - Unlock the screen + - The device should be re-mounted (and no errors in journal) + + [ Regression Potential ] + + Devices could be leaked if gc doesn't work as expected + + --- + I could fix the issue by modifying the source code as given in the attached patch. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME - DisplayManager: gdm3 - DistroRelease: Ubuntu 21.10 + DisplayManager: gdm3DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-01 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Also affects: gnome-shell-extension-dashtodock (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-dashtodock (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-dashtodock (Ubuntu Impish) Status: New => In Progress ** Changed in: gnome-shell-extension-dashtodock (Ubuntu Impish) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** No longer affects: gnome-shell-extension-dashtodock (Ubuntu Impish) ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Status: In Progress => Won't Fix ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: New => 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/1949352 Title: Removable drives are not auto-mounted after screen lock/unlock Status in gnome-shell-extension-dashtodock package in Ubuntu: Won't Fix Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Impish: In Progress Bug description: [ Impact ] If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. [ Test case ] - Mount a device - Lock the screen - Unlock the screen - The device should be re-mounted (and no errors in journal) [ Regression Potential ] Devices could be leaked if gc doesn't work as expected --- I could fix the issue by modifying the source code as given in the attached patch. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-01 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Tags: wayland-session impish Uname: Linux 5.13.0-20-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-dashtodock/+bug/1949352/+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 1949572] Re: Shell freeze after right click on the app in the dock
** Also affects: gnome-shell-extension-dashtodock (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-appindicator (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-appindicator (Ubuntu Impish) Importance: Undecided => High ** Changed in: gnome-shell-extension-appindicator (Ubuntu Impish) Status: New => Invalid ** Changed in: gnome-shell-extension-dashtodock (Ubuntu Impish) Importance: Undecided => High ** Changed in: gnome-shell-extension-dashtodock (Ubuntu Impish) Status: New => In Progress ** Changed in: gnome-shell-extension-dashtodock (Ubuntu Impish) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Importance: Undecided => High ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: New => Triaged ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1949572 Title: Shell freeze after right click on the app in the dock Status in gnome-shell-extension-appindicator package in Ubuntu: Invalid Status in gnome-shell-extension-dashtodock package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Status in gnome-shell-extension-appindicator source package in Impish: Invalid Status in gnome-shell-extension-dashtodock source package in Impish: In Progress Status in gnome-shell-extension-ubuntu-dock source package in Impish: Triaged Bug description: When you click the icon of the app in the dock to open it for the first time and then immediately right click to see options, everything freezes and you are forced to reboot. I'm using Ubuntu 21.10. I installed it today. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-03 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Tags: impish wayland-session Uname: Linux 5.13.0-20-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-appindicator/+bug/1949572/+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 1954980] Re: Chromium showing Japanese fonts incorrectly
It fixes itself eventually, without restarting Ubuntu. Is this because mistakes are been made with the update, and then later corrected?! I wonder if its move to Snap is representative of a de-prioritizing of this application and that is reflected in the inability to provide globally competent versions of it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1954980 Title: Chromium showing Japanese fonts incorrectly Status in chromium-browser package in Ubuntu: New Bug description: It simply shows square rectangles for all Japanese characters this occurred after a recent update (earlier this week), a restart fixed it the first time but now it has reverted, probably after another update. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 11:54:12 2021 InstallationDate: Installed on 2019-02-08 (1041 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Snap: chromium 96.0.4664.110 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2021-12-01 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1954980/+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 1958710] Re: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main)
It's always ok to report issues you would like to see fixed, I was just pointing out that we usually have other way to list packages that need to be rebased on Debian. For desktop we use https://people.canonical.com/~platform/desktop/versions/desktop- packages.html for example ** Changed in: network-manager (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1958710 Title: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main) Status in network-manager package in Ubuntu: Triaged Bug description: There are some differences between versions from Debian and Ubuntu. A new version has been released a week ago. Debian Changelog: network-manager (1.34.0-2) unstable; urgency=medium * Demote wpasupplicant to Recommends. There are enough use cases for network-manager not involving Wi-Fi which justifies to make this dependency optional. (Closes: #919619, #980218) -- Michael Biebl Tue, 18 Jan 2022 20:59:36 +0100 network-manager (1.34.0-1) unstable; urgency=medium * New upstream version 1.34.0 * Rebase patches * Install nm-priv-helper service * Update symbols file for libnm0 -- Michael Biebl Fri, 14 Jan 2022 00:18:58 +0100 NM ChangeLog: = NetworkManager-1.34 Overview of changes since NetworkManager-1.32 = * initrd: wait for both IPv4 and IPv6 with "ip=dhcp,dhcp6". * core: better handle sd-resolved errors when resolving hostnames. * nmcli: fix import WireGuard profile with DNS domain and address family disabled. * ndisc: send router solicitations before expiry. * policy: send earlier the ip configs to the DNS manager. * core: support linking with LLD 13. * wireguard: importing wg-quick configuration files with nmcli no longer sets a negative, exclusive "dns-priority". This plays better with common split DNS setups that use systemd-resolved. Adjust the "dns-priority" to your liking after import yourself. * NetworkManager no longer listens for netlink events for traffic control objects (qdiscs and filters). * core: add internal nm-priv-helper service for separating privileges and have a way to drop capabilities from NetworkManager daemon. * bond: add support for setting queue-id of bond port. * dns: support configuring DNS over TLS (DoT) with systemd-resolved. * nmtui: add support for WireGuard profiles. * nmcli: add aliases `nmcli device up|down` beside connect|disconnect. * conscious language: Deprecate 'Device.Slaves' D-Bus property in favor of new 'Device.Ports' property. Depracate 'nm_device_*_get_slaves()' in favor of 'nm_device_get_ports()' in libnm. * nmcli: invoking nmcli command without arguments will now show 'default' instead of null address in route4 or route6 section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1958710/+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 1958912] [NEW] package libreoffice-common 1:7.2.5-0ubuntu0.21.10.1 failed to install/upgrade: o subprocesso instalado, do pacote libreoffice-common, o script post-installation
Public bug reported: I have error to update OS ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libreoffice-common 1:7.2.5-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 AptOrdering: vim-runtime:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Jan 24 15:30:15 2022 DpkgTerminalLog: A preparar para desempacotar .../vim-runtime_2%3a8.2.2434-3ubuntu3.2_all.deb ... A descompactar vim-runtime (2:8.2.2434-3ubuntu3.2) sobre (2:8.2.2434-3ubuntu3.1) ... Configurando libreoffice-common (1:7.2.5-0ubuntu0.21.10.1) ... dpkg: erro ao processar o pacote libreoffice-common (--configure): o subprocesso instalado, do pacote libreoffice-common, o script post-installation retornou erro do status de saída 10 ErrorMessage: o subprocesso instalado, do pacote libreoffice-common, o script post-installation retornou erro do status de saída 10 InstallationDate: Installed on 2021-05-03 (266 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.7, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: libreoffice Title: package libreoffice-common 1:7.2.5-0ubuntu0.21.10.1 failed to install/upgrade: o subprocesso instalado, do pacote libreoffice-common, o script post-installation retornou erro do status de saída 10 UpgradeStatus: Upgraded to impish on 2021-10-22 (93 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1958912 Title: package libreoffice-common 1:7.2.5-0ubuntu0.21.10.1 failed to install/upgrade: o subprocesso instalado, do pacote libreoffice- common, o script post-installation retornou erro do status de saída 10 Status in libreoffice package in Ubuntu: New Bug description: I have error to update OS ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libreoffice-common 1:7.2.5-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 AptOrdering: vim-runtime:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Jan 24 15:30:15 2022 DpkgTerminalLog: A preparar para desempacotar .../vim-runtime_2%3a8.2.2434-3ubuntu3.2_all.deb ... A descompactar vim-runtime (2:8.2.2434-3ubuntu3.2) sobre (2:8.2.2434-3ubuntu3.1) ... Configurando libreoffice-common (1:7.2.5-0ubuntu0.21.10.1) ... dpkg: erro ao processar o pacote libreoffice-common (--configure): o subprocesso instalado, do pacote libreoffice-common, o script post-installation retornou erro do status de saída 10 ErrorMessage: o subprocesso instalado, do pacote libreoffice-common, o script post-installation retornou erro do status de saída 10 InstallationDate: Installed on 2021-05-03 (266 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.7, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: libreoffice Title: package libreoffice-common 1:7.2.5-0ubuntu0.21.10.1 failed to install/upgrade: o subprocesso instalado, do pacote libreoffice-common, o script post-installation retornou erro do status de saída 10 UpgradeStatus: Upgraded to impish on 2021-10-22 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1958912/+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 1946525] Re: Removable media are not mounted automatically
It's a strange one. I appear to have had this as well. The output from dmesg shows it detects the drive just fine. It also appears in Nautilus, which will mount it for you when you click on it, but that's obviously a complete no-go. What fixed it for me was simply reinstalling the fuse package: sudo apt install --reinstall fuse and rebooting, as per the advice here https://askubuntu.com/questions/1361627/ubuntu-mate-21-04-usb-stick- will-not-automount which I know isn't 21.10, but worked for me regardless. No clue why it went wrong in the first place, but at least I've got it sorted for now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1946525 Title: Removable media are not mounted automatically Status in udisks2 package in Ubuntu: Confirmed Bug description: 1) Ubuntu Desktop amd 64 20211008.1 daily build 2) udisks 2.9.4-1 3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions disk images, should be mounted automatically 4) the automount feature seems to be gone or non-functional in the last couple of days ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 60-vboxadd.rules 70-snap.snap-store.rules Date: Sat Oct 9 01:37:13 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash SourcePackage: udisks2 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:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: 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/ubuntu/+source/udisks2/+bug/1946525/+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 1958900] [NEW] Spelling and Grammer window doesn't scale properly with HiDPI displays
Public bug reported: What I expected to happen: The Spelling and Grammar window to be scaled properly with my display, like the main window and every other subwindow. What actually happens: The window elements in the Spelling and Grammar window are the wrong size, causing the options to be unreadable. Attached are photos of this occurring. The size of the elements scales up when moved to the 1X scaled display, but the sizing of the elements are still wrong. This only affects the Spelling and Grammar window. With every other subwindow, the behavior works fine. Notes: I'm using a dual monitor set up on Wayland with a 4K monitor at 2X scaling attached to a 2560x1080 monitor at 1X scaling I have the LanguageTool Plugin Installed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 11:42:41 2022 InstallationDate: Installed on 2020-11-18 (431 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Attachment added: "LibreOffice Scaling Bug.zip" https://bugs.launchpad.net/bugs/1958900/+attachment/5557129/+files/LibreOffice%20Scaling%20Bug.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1958900 Title: Spelling and Grammer window doesn't scale properly with HiDPI displays Status in libreoffice package in Ubuntu: New Bug description: What I expected to happen: The Spelling and Grammar window to be scaled properly with my display, like the main window and every other subwindow. What actually happens: The window elements in the Spelling and Grammar window are the wrong size, causing the options to be unreadable. Attached are photos of this occurring. The size of the elements scales up when moved to the 1X scaled display, but the sizing of the elements are still wrong. This only affects the Spelling and Grammar window. With every other subwindow, the behavior works fine. Notes: I'm using a dual monitor set up on Wayland with a 4K monitor at 2X scaling attached to a 2560x1080 monitor at 1X scaling I have the LanguageTool Plugin Installed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 11:42:41 2022 InstallationDate: Installed on 2020-11-18 (431 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1958900/+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 1958890] [NEW] Xorg freeze
Public bug reported: the screen is flcikering after waking up from sleep ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 23:04:53 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.0.15-1098277: added ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f95] InstallationDate: Installed on 2022-01-11 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 82KT ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=7e63c3e2-afff-4841-8da3-9dad122a8352 ro nouveau.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 07/23/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: GLCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55726WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14ALC6 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrGLCN40WW:bd07/23/2021:br1.40:efr1.40:svnLENOVO:pn82KT:pvrIdeaPad314ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrIdeaPad314ALC6:skuLENOVO_MT_82KT_BU_idea_FM_IdeaPad314ALC6: dmi.product.family: IdeaPad 3 14ALC6 dmi.product.name: 82KT dmi.product.sku: LENOVO_MT_82KT_BU_idea_FM_IdeaPad 3 14ALC6 dmi.product.version: IdeaPad 3 14ALC6 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1958890 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: the screen is flcikering after waking up from sleep ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 23:04:53 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.0.15-1098277: added ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f95] InstallationDate: Installed on 2022-01-11 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 82KT ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=7e63c3e2-afff-4841-8da3-9dad122a8352 ro nouveau.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 07/23/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: GLCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55726WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14ALC6 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrGLCN40WW:bd07/23/2021:br1.40:efr1.4
[Desktop-packages] [Bug 1958811] Re: If apt installs snap package, then show size of it
** No longer affects: chromium-browser (Ubuntu)
** Changed in: apt (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: snapd (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1958811
Title:
If apt installs snap package, then show size of it
Status in apt package in Ubuntu:
Invalid
Status in snapd package in Ubuntu:
New
Bug description:
If apt installs snap package, then show size of it
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
Uname: Linux 5.15.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
DRM.card0-Virtual-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
modes: 1024x768 1920x1080 1600x1200 1680x1050 1680x1050 1400x1050 1400x1050
1600x900 1280x1024 1440x900 1440x900 1280x960 1366x768 1366x768 1360x768
1280x800 1280x800 1280x768 1280x768 1280x720 800x600 800x600 848x480 640x480
Date: Mon Jan 24 03:36:26 2022
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/xvda3 ext411G 8,3G 1,5G 86% /
tmpfs tmpfs 1,9G 6,6M 1,9G 1% /dev/shm
/dev/xvda3 ext411G 8,3G 1,5G 86% /
InstallationDate: Installed on 2022-01-21 (2 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
(20220121)
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: Xen HVM domU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic
root=UUID=d8fb805e-11ec-4105-9320-3618a2dfa835 ro quiet splash vt.handoff=7
Snap.Changes:
ID Status Spawn Ready Summary
4Done2022-01-24T03:33:37+02:00 2022-01-24T03:34:29+02:00 Install
"chromium" snap
Snap.ChromeDriverVersion: ChromeDriver 97.0.4692.99
(d740da257583289dbebd2eb37e8668928fac5ead-refs/branch-heads/4692@{#1461})
Snap.ChromiumVersion: Chromium 97.0.4692.99 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2022
dmi.bios.release: 4.14
dmi.bios.vendor: Xen
dmi.bios.version: 4.14.3
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias:
dmi:bvnXen:bvr4.14.3:bd01/08/2022:br4.14:svnXen:pnHVMdomU:pvr4.14.3:cvnXen:ct1:cvr:sku:
dmi.product.name: HVM domU
dmi.product.version: 4.14.3
dmi.sys.vendor: Xen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1958811/+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 1704870] Re: Keys can't be grabbed under Wayland
Issue is still present in 21.10 Wayland in combination with Citrix Workspace App. No options / toggle for Citrix in Gnome settings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1704870 Title: Keys can't be grabbed under Wayland Status in remmina: New Status in wayland: Confirmed Status in remmina package in Ubuntu: Invalid Status in wayland package in Fedora: Confirmed Bug description: Special keys are not working under Remmina. Seems to be a Wayland specification and implementation of that specification. This bug could embrace all apps that need this behavior (VirtualBox, vncviewer, etc) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: remmina 1.1.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 17 15:36:36 2017 InstallationDate: Installed on 2017-07-04 (13 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170626) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/remmina/+bug/1704870/+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 1952107] Re: Google Contacts API Deprecated
Pardon me if this should be a separate issue, but ... GNOME Contacts has this same issue. And I'm not sure if the fix provided for Evolution will propagate to GNOME Contacts. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1856032] Re: Removable media icon stays on the dock after eject.
This should be fixed by gnome-shell-extension-ubuntu-dock 72~ubuntu1, please re-open if it's not the case. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => 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/1856032 Title: Removable media icon stays on the dock after eject. Status in OEM Priority Project: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Impish: Confirmed Bug description: 1) Ubuntu 19.10 2) Dock 3) I placed a DVD in the optical drive. An optical disc with a DVD tag appeared on the dock. I pressed the button on the optical drive to open it. I removed the disc and pressed in the tray. The icon should have disappeared from the dock. 4) The icon did NOT disappear from the dock. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1856032/+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 1958684] Re: gnome-shell crashed with SIGFPE in meta_wayland_xdg_toplevel_send_configure() from meta_window_wayland_configure()
Can you tell already which versions of Ubuntu will receive the fix? -- 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/1958684 Title: gnome-shell crashed with SIGFPE in meta_wayland_xdg_toplevel_send_configure() from meta_window_wayland_configure() Status in mutter package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/bd270ee843b327813e28ccddde4a1357b64e1326 --- To reproduce with Ubuntu 20.04: 1. Run Gnome or the Gnome-based Ubuntu Desktop on Wayland. 2. Download and install the snapshot build of Qt Creator from https://master.qt.io/snapshots/qtcreator/6.0/6.0.3/624/qt-creator-opensource-linux-x86_64-6.0.3_624.run Sorry for the inconvenience that the installer requires an account. You can easily get one free of charge. Let me know if you need help with that. 3. Start the installed Qt Creator with parameter "-tcs". "-tcs" will ignore local settings saved for Qt Creator, so it will not mess up settings you might have. The log-in session crashes. All running applications are being closed immediately and you get back to the login screen. Sure, there might be something wrong in our snapshot package, but no matter how wrong our package might be, Wayland/Gnome should not crash, should they? If I should provide any further information, please let me know. gnome-shell: 3.36.9-0ubuntu0.20.04.2 libwayland-server0: 1.18.0-1 xwayland: 2:1.20.13-1ubuntu1~20.04.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 18:18:40 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1621432157 InstallationDate: Installed on 2021-12-17 (35 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/qtrob RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 Signal: 8 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGFPE in g_closure_invoke() 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/mutter/+bug/1958684/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1958733] Re: Settings menu will not open. Other things seem messed up.
Unfortunately I just re installed the os yesterday so I am unable to recreate the error. On Sun, Jan 23, 2022 at 8:49 PM, Daniel van Vugt - 1958733 at bugs.launchpad.net wrote: > Also if you open a Terminal window and run: > > gnome-control-center > > then what messages do you see? > > ** Changed in: gnome-control-center (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1958733 > > Title: > Settings menu will not open. Other things seem messed up. > > Status in gnome-control-center package in Ubuntu: > Incomplete > > Bug description: > I installed DWM and was learning how to use the shortcuts. I was > mashing keys because I had no idea what the shorcuts were and I am a > newb. When I rebooted into DWM, it said it couldn't open firefox > because of an IBUS warning. When I rebooted again and went into the > normal Ubuntu window manager everthing worked fine. When I went to > click on settings, the settings menu would not open. I tried to open > settings by using the following command "gnome-control-center display" > which did not work. > > Should I just reinstall everything? > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-control-center 1:3.36.5-0ubuntu3 > ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 > Uname: Linux 5.13.0-27-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu27.21 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sat Jan 22 14:53:58 2022 > InstallationDate: Installed on 2022-01-19 (3 days ago) > InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) > ProcEnviron: > PATH=(custom, no user) > XDG_RUNTIME_DIR= > LANG=en_US.UTF-8 > SHELL=/bin/bash > SourcePackage: gnome-control-center > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1958733/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1958733 Title: Settings menu will not open. Other things seem messed up. Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I installed DWM and was learning how to use the shortcuts. I was mashing keys because I had no idea what the shorcuts were and I am a newb. When I rebooted into DWM, it said it couldn't open firefox because of an IBUS warning. When I rebooted again and went into the normal Ubuntu window manager everthing worked fine. When I went to click on settings, the settings menu would not open. I tried to open settings by using the following command "gnome-control-center display" which did not work. Should I just reinstall everything? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 22 14:53:58 2022 InstallationDate: Installed on 2022-01-19 (3 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1958733/+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 1876352] Re: [ubuntu-dock] App Grid icons out of alignment when opening from overview
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => 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/1876352 Title: [ubuntu-dock] App Grid icons out of alignment when opening from overview Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Affected version: Ubuntu 20.04 Gnome Shell Version 3.36.1 Only tested on xorg Bug summary: When opening the App Grid (aka "Show Applications) from the window overview (I don't know the technical terms) the icons shift out of alignment. This gets worse if you have multiple pages of apps (as I do), and it gets even worse the more you open and close the App Grid in this manner. I cannot see the same bug if you just open the App Grid from the desktop. Steps to reproduce: 1. Open the overview window using the Super Key 2. Click the "Show Applications" icon 3. You will see the icons in the App Grid shift downwards 4. Scroll down to see the icons move further out of alignment What did GNOME Shell do that was unexpected?: Display the App Window icons out of alignment when accessing the app grid via the window overview (pressing the Super key) What did you expect to happen: I expected the icons to display properly. Video of the bug: https://www.youtube.com/watch?v=IJ3EYZ2qoK4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 19:16:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-14 (169 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-24 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1876352/+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 1951786] Re: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated
*** This bug is a duplicate of bug 1949352 *** https://bugs.launchpad.net/bugs/1949352 ** This bug has been marked a duplicate of bug 1949352 Removable drives are not auto-mounted after screen lock/unlock -- 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/1951786 Title: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: on Ubuntu 21.10 gnome-shell 40.5-1ubuntu2 Locking desktop and then unlocking it makes gnome-shell spit out a stack trace. v 22 02:00:49 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated — impossible to access it. This might be caused by the> Nov 22 02:00:49 saturn gnome-shell[33781]: == Stack trace for context 0x5572c18e3130 == Nov 22 02:00:49 saturn gnome-shell[33781]: #0 7ffcbc579470 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:567 (22c5be1b1d80 @ 25) Nov 22 02:00:49 saturn gnome-shell[33781]: #1 5572c8ea2dc0 i resource:///org/gnome/shell/ui/components/autorunManager.js:159 (374b9f3380 @ 31) Nov 22 02:00:49 saturn gnome-shell[33781]: #2 7ffcbc57a1d0 b resource:///org/gnome/shell/ui/components/__init__.js:56 (374b9d7650 @ 66) Nov 22 02:00:49 saturn gnome-shell[33781]: #3 7ffcbc57a960 b resource:///org/gnome/shell/ui/components/__init__.js:22 (374b9d7790 @ 15) Nov 22 02:00:49 saturn gnome-shell[33781]: #4 7ffcbc57b030 b self-hosted:225 (374b92ab50 @ 273) Nov 22 02:00:49 saturn gnome-shell[33781]: #5 5572c8ea2d30 i resource:///org/gnome/shell/ui/components/__init__.js:22 (374b9d78d0 @ 110) ...skipping... Nov 22 02:04:21 saturn gnome-shell[33781]: #7 7ffcbc578a80 b resource:///org/gnome/shell/ui/sessionMode.js:200 (25da4d8e6d30 @ 284) Nov 22 02:04:21 saturn gnome-shell[33781]: #8 7ffcbc579630 b resource:///org/gnome/shell/ui/sessionMode.js:168 (25da4d8e6e20 @ 116) Nov 22 02:04:21 saturn gnome-shell[33781]: #9 7ffcbc579dc0 b resource:///org/gnome/shell/ui/screenShield.js:574 (25da4d8d4a60 @ 79) Nov 22 02:04:21 saturn gnome-shell[33781]: #10 7ffcbc57a550 b resource:///org/gnome/shell/ui/screenShield.js:565 (25da4d8d4ab0 @ 17) Nov 22 02:04:21 saturn gnome-shell[33781]: #11 7ffcbc57acd0 b resource:///org/gnome/shell/gdm/authPrompt.js:604 (25da4d8f24c0 @ 65) Nov 22 02:04:21 saturn gnome-shell[33781]: #12 7ffcbc57b460 b resource:///org/gnome/shell/ui/unlockDialog.js:871 (374b9053d0 @ 40) Nov 22 02:04:21 saturn gnome-shell[33781]: #13 7ffcbc57bbf0 b resource:///org/gnome/shell/ui/screenShield.js:565 (25da4d8d4b00 @ 50) Nov 22 02:04:21 saturn gnome-shell[33781]: #14 7ffcbc57c380 b resource:///org/gnome/shell/ui/screenShield.js:116 (25da4d8dc6f0 @ 13) Nov 22 02:04:21 saturn gnome-shell[33781]: #15 7ffcbc57ca50 b resource:///org/gnome/gjs/modules/core/_signals.js:114 (22c5be1b1330 @ 439) Nov 22 02:04:21 saturn gnome-shell[33781]: #16 5572c39ba218 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:152 (22c5be1a5b50 @ 39) Nov 22 02:04:21 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated — impossible to connect to any signal on it. This migh> Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Nov 22 02:04:21 saturn dbus-daemon[33727]: [session uid=1000 pid=33727] Activating service name='org.freedesktop.FileManager1' requested by ':1.20' (uid=1000 pid=33781 comm> Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Nov 22 02:04:21 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated — impossible to access it. This might be caused by the> Nov 22 02:04:21 saturn gnome-shell[33781]: g_volume_monitor_get_volumes: assertion 'G_IS_VOLUME_MONITOR (volume_monitor)' failed Nov 22 02:04:21 saturn gnome-shell[33781]: == Stack trace for context 0x5572c18e3130 == Nov 22 02:04:21 saturn gnome-shell[33781]: #0 5572c39ba218 i resource:///org/gnome/shell/ui/components/automountManager.js:66 (374b9f3e20 @ 30) Nov 22 02:04:21 saturn gnome-shell[33781]: #1 7ffcbc57d550 b self-hosted:850 (374b92a650 @ 398) Nov 22 02:04:21 saturn N
[Desktop-packages] [Bug 1942702] Re: Ubuntu Dock "Show Applications" button: click target doesn't extend to screen edges
Dock side is fixed by gnome-shell-extension-ubuntu-dock 72~ubuntu1, will need to update yaru to get the full fix. ** 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/1942702 Title: Ubuntu Dock "Show Applications" button: click target doesn't extend to screen edges Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: In Progress Bug description: How to reproduce === Boot up Impish live media, with the default left-side dock setup, swing the mouse pointer to the bottom-leftmost corner of the screen. The "Show Applications" button is not highlighted and cannot be activated. Also see Demonstration in attachment. Expected behaviour === The click target of this button should extend to the very edges of the screen like the rest of the UI elements. Fitts's law should be fulfilled. Apport info === ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-ubuntu-dock 70~ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 5 09:14:42 2021 LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1942702/+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 1855968] Re: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1090]: unreachable code after return statement
Could be cleaned up, but nothing problematic. It's a patch we've only in
the dock fork.
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Triaged => Won't Fix
--
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/1855968
Title:
JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-
d...@ubuntu.com/appIcons.js 1090]: unreachable code after return
statement
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Won't Fix
Bug description:
JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-
d...@ubuntu.com/appIcons.js 1090]: unreachable code after return
statement
which is true:
popupMenu() {
return false;
this._removeMenuTimeout();
this.actor.fake_release();
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1855968/+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 1405452] Re: Typo in man page ("introduce a much improvement mechanism")
** Changed in: wpa (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1405452
Title:
Typo in man page ("introduce a much improvement mechanism")
Status in One Hundred Papercuts:
Fix Released
Status in wpa package in Ubuntu:
Fix Released
Status in wpa package in Debian:
New
Bug description:
"introduce a much improvement mechanism" should be "introduce a much
improved mechanism".
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: wpasupplicant 2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 24 16:19:30 2014
InstallationDate: Installed on 2014-12-19 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64
(20141022.1)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1405452/+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 1875015] Re: Displaylink is extremely slow
** Bug watch removed: gitlab.gnome.org/GNOME/mutter/-/issues #2005 https://gitlab.gnome.org/GNOME/mutter/-/issues/2005 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1948008] Re: Copying and pasting files between desktop and Nautilus does not work
It seems this has been fixed with https://gitlab.com/rastersoft/desktop- icons-ng/-/commit/4c6de6a39f3e0d7ccff4399cb06f4bcd6485c047 I'll look into a way of backporting it into impish. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1948008 Title: Copying and pasting files between desktop and Nautilus does not work Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Confirmed Status in gnome-shell-extension-desktop-icons source package in Focal: Confirmed Status in gnome-shell-extension-desktop-icons-ng source package in Focal: Invalid Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Invalid Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: Won't Fix Status in gnome-shell source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons source package in Impish: Invalid Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Confirmed Bug description: [Impact] * After upstream Nautilus has reverted the following commit [1] related to upstream bug [2] the desktop icons extension lost it's ability to copy to/from nautilus. * This is related to the fact that before there was some metadata passed along in the clipboard along with text data. This was causing issues with compatibility with some applications that were not expecting any metadata (MIME type in this case) was glued to the text clipboard contents. Hence, it was reverted upstream [3]. * Fixing the root cause of this issue required changes to Nautilus [3], gnome-shell [4] and desktop-icons [5] [6]. Nautilus and gnome- shell parts are already implemented and present in Hirsute and Impish. [Test Plan] 1) Make sure desktop-icons extension is enabled. 2) Open nautilus window and copy any file from there by right-clicking and selecting "Copy" from the popup menu. 3) Right-click on desktop and select "Paste" from the context menu. Expected result: selected file is copied to the desktop. Actual result: "Paste" item is disabled in the menu. [Where problems could occur] * Mixing a version of nautilus without commit [3] and fixed version of desktop-icons may still lead to a scenario when copying will not work. * Any extension/application copying to desktop using the smuggled-in- text clipboard behavior should be expected to stop working. [Other Info] [1] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/289 [2] https://gitlab.gnome.org/GNOME/nautilus/-/issues/634 [3] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573 [4] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1321 [5] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [6] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948008/+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 1958856] [NEW] gnome-software continues running in the background even after its window is closed
Public bug reported: 1) Ubuntu 20.04.3 LTS 2) gnome-software 3.36.1-0ubuntu0.20.04.0 3) Closing the window should kill the process altogether 4) The process remains in the background instead [ STEPS TO REPRODUCE ] This becomes obvious when launched from the shell: ~ gnome-software & [1] 7972 ~ 11:25:23:0836 Gs enabled plugins: desktop-categories, fwupd, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blacklist, modalias, odrs, packagekit-refine, rewrite-resource, snap, packagekit-history, provenance, systemd-updates, generic-updates, provenance-license, icons, key-colors, key-colors-metadata 11:25:23:0836 Gs disabled plugins: dpkg, dummy, repos 11:25:26:0660 Gs Only 0 apps for recent list, hiding 11:25:31:0006 Gs automatically prevented from changing kind on system/snap/*/runtime/io.snapcraft.bare-EISPgh06mRh1vordZY9OZ34QHdd7OrdR/latest/stable from runtime to unknown! 11:25:31:0817 Gs automatically prevented from changing kind on system/snap/*/runtime/io.snapcraft.core20-DLqre5XGLbDqg9jPtiAhRRjDuPVa5X1q/latest/stable from runtime to unknown! 11:25:32:0448 Gs automatically prevented from changing kind on system/snap/*/desktop/io.snapcraft.snapd-PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4/latest/stable from desktop to unknown! 11:25:32:0721 Gs automatically prevented from changing kind on system/snap/*/runtime/io.snapcraft.core18-CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6/latest/stable from runtime to unknown! here, the window is closed but the process is still running as shown below ~ jobs [1]+ Running gnome-software & Launching Software, window appears ~ wmctrl -lpG | grep 'Software$' 0x0267 0 7972 29 -8 1274 916 hp Software Closing Software, window disappears, yet the process is still running as shown above ~ wmctrl -lpG | grep 'Software$' ~ [ WORKAROUND ] The workaround here is to kill the process manually, e.g. `pkill gnome-software`. [ SUGGESTION ] Is it designed so to prevent interruptions (accidental or not) during updates? If it is, perhaps a more elegant way would be to display a confirmation dialog/prompt/popup in the case of an ongoing update process, gracefully quit the program otherwise (the process is killed for good). END OF REPORT ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.1-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jan 24 16:19:33 2022 InstallationDate: Installed on 2021-05-17 (252 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.1-0ubuntu0.20.04.0 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.cron.daily.apport: [modified] mtime.conffile..etc.cron.daily.apport: 2022-01-10T23:09:37.086519 ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: 1) Ubuntu 20.04.3 LTS 2) gnome-software 3.36.1-0ubuntu0.20.04.0 3) Closing the window should kill the process altogether 4) The process remains in the background instead + + [ STEPS TO REPRODUCE ] This becomes obvious when launched from the shell: ~ gnome-software & [1] 7972 ~ 11:25:23:0836 Gs enabled plugins: desktop-categories, fwupd, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blacklist, modalias, odrs, packagekit-refine, rewrite-resource, snap, packagekit-history, provenance, systemd-updates, generic-updates, provenance-license, icons, key-colors, key-colors-metadata 11:25:23:0836 Gs disabled plugins: dpkg, dummy, repos 11:25:26:0660 Gs Only 0 apps for recent list, hiding 11:25:31:0006 Gs automatically prevented from changing kind on system/snap/*/runtime/io.snapcraft.bare-EISPgh06mRh1vordZY9OZ34QHdd7OrdR/latest/stable from runtime to unknown! 11:25:31:0817 Gs automatically prevented from changing kind on system/snap/*/runtime/io.snapcraft.core20-DLqre5XGLbDqg9jPtiAhRRjDuPVa5X1q/latest/stable from runtime to unknown! 11:25:32:0448 Gs automatically prevented from changing kind on system/snap/*/desktop/io.snapcraft.snapd-PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4/latest/stable from desktop to unknown! 11:25:32:0721 Gs automatically prevented from changing kind on system/snap/*/runtime/io.snapcraft.core18-CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6/latest/stable from runtime to unknown! here, the wi
[Desktop-packages] [Bug 1958852] [NEW] Auto-rotation does not work anymore
Public bug reported: With my Radeon Vega graphics card auto-rotation of the screen used to work in 21.04 but does not work anymore in 21.10. Also Cinnamon (which I have uninstall now) shows an error, saying that hardware acceleration does not work. output of `lspci | grep VGA`: ```04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] (rev c1) 04:00.7 Non-VGA unclassified device: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/Renoir Sensor Fusion Hub `` ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.14.21-051421-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 12:20:21 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-02-09 (714 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.21-051421-generic root=UUID=4bbf320c-9d1b-4cb2-a03e-a7f170d88509 ro noplymouth resume=/swapfile radeon.si_support=1 radeon.cik_support=1 amd_iommu=off SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.release: 15.19 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 41.36 dmi.modalias: dmi:bvnAMI:bvrF.19:bd12/26/2019:br15.19:efr41.36:svnHP:pnHPENVYx360Convertible13-ar0xxx:pvr:rvnHP:rn85DE:rvr41.36:cvnHP:ct31:cvrChassisVersion:sku7BR48EA#ABD: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ar0xxx dmi.product.sku: 7BR48EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.3.2~kisak1~i version.libgl1-mesa-glx: libgl1-mesa-glx 21.3.2~kisak1~i version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1958852 Title: Auto-rotation does not work anymore Status in xorg package in Ubuntu: New Bug description: With my Radeon Vega graphics card auto-rotation of the screen used to work in 21.04 but does not work anymore in 21.10. Also Cinnamon (which I have uninstall now) shows an error, saying that hardware acceleration does not work. output of `lspci | grep VGA`: ```04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] (rev c1) 04:00.7 Non-VGA unclassified device: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/Renoir Sensor Fusion Hub `` ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.14.21-051421-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 12:20:21 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-02-09 (714 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Machi
[Desktop-packages] [Bug 1958710] Re: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main)
Hi Sebastien, Sorry I didn't know your team was already tracking that. I opened this issue because I was trying to find the root cause of random disconnections when using Ubuntu Jammy: is it NM/iwd/kernel? I'm using 'iwd' and I noticed it was outdated: 1.15 while the latest version is 1.21 and available on Debian side. So I opened this issue: https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1958711 While at it, I also opened this issue for NM because I was not sure if the merge were done by requests or not. I mean: even if a few people can see there is an update available, I don't know if someone will update it because (s)he is in charge of that or if everybody would think "someone will do that" but because there is no specific task, the update can be pending for a long time if you see what I mean :) In the past, I had a similar issue with Git which was not updated for quite a while because a merge had to be done and nobody was really in charge of update it. I had to ask for an update on IRC. This time, I opened an issue: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1956773 Do you think I should better close these 3 issues (NM/iwd/git)? Should I find someone on IRC to look at that instead? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1958710 Title: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main) Status in network-manager package in Ubuntu: New Bug description: There are some differences between versions from Debian and Ubuntu. A new version has been released a week ago. Debian Changelog: network-manager (1.34.0-2) unstable; urgency=medium * Demote wpasupplicant to Recommends. There are enough use cases for network-manager not involving Wi-Fi which justifies to make this dependency optional. (Closes: #919619, #980218) -- Michael Biebl Tue, 18 Jan 2022 20:59:36 +0100 network-manager (1.34.0-1) unstable; urgency=medium * New upstream version 1.34.0 * Rebase patches * Install nm-priv-helper service * Update symbols file for libnm0 -- Michael Biebl Fri, 14 Jan 2022 00:18:58 +0100 NM ChangeLog: = NetworkManager-1.34 Overview of changes since NetworkManager-1.32 = * initrd: wait for both IPv4 and IPv6 with "ip=dhcp,dhcp6". * core: better handle sd-resolved errors when resolving hostnames. * nmcli: fix import WireGuard profile with DNS domain and address family disabled. * ndisc: send router solicitations before expiry. * policy: send earlier the ip configs to the DNS manager. * core: support linking with LLD 13. * wireguard: importing wg-quick configuration files with nmcli no longer sets a negative, exclusive "dns-priority". This plays better with common split DNS setups that use systemd-resolved. Adjust the "dns-priority" to your liking after import yourself. * NetworkManager no longer listens for netlink events for traffic control objects (qdiscs and filters). * core: add internal nm-priv-helper service for separating privileges and have a way to drop capabilities from NetworkManager daemon. * bond: add support for setting queue-id of bond port. * dns: support configuring DNS over TLS (DoT) with systemd-resolved. * nmtui: add support for WireGuard profiles. * nmcli: add aliases `nmcli device up|down` beside connect|disconnect. * conscious language: Deprecate 'Device.Slaves' D-Bus property in favor of new 'Device.Ports' property. Depracate 'nm_device_*_get_slaves()' in favor of 'nm_device_get_ports()' in libnm. * nmcli: invoking nmcli command without arguments will now show 'default' instead of null address in route4 or route6 section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1958710/+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 1948008] Re: Copying and pasting files between desktop and Nautilus does not work
Thank you for this observation Gunnar. Indeed, looks like its fixed for jammy. I'll try to figure out the right commit and backport it. ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1948008 Title: Copying and pasting files between desktop and Nautilus does not work Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Confirmed Status in gnome-shell-extension-desktop-icons source package in Focal: Confirmed Status in gnome-shell-extension-desktop-icons-ng source package in Focal: Invalid Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Invalid Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: Won't Fix Status in gnome-shell source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons source package in Impish: Invalid Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Confirmed Bug description: [Impact] * After upstream Nautilus has reverted the following commit [1] related to upstream bug [2] the desktop icons extension lost it's ability to copy to/from nautilus. * This is related to the fact that before there was some metadata passed along in the clipboard along with text data. This was causing issues with compatibility with some applications that were not expecting any metadata (MIME type in this case) was glued to the text clipboard contents. Hence, it was reverted upstream [3]. * Fixing the root cause of this issue required changes to Nautilus [3], gnome-shell [4] and desktop-icons [5] [6]. Nautilus and gnome- shell parts are already implemented and present in Hirsute and Impish. [Test Plan] 1) Make sure desktop-icons extension is enabled. 2) Open nautilus window and copy any file from there by right-clicking and selecting "Copy" from the popup menu. 3) Right-click on desktop and select "Paste" from the context menu. Expected result: selected file is copied to the desktop. Actual result: "Paste" item is disabled in the menu. [Where problems could occur] * Mixing a version of nautilus without commit [3] and fixed version of desktop-icons may still lead to a scenario when copying will not work. * Any extension/application copying to desktop using the smuggled-in- text clipboard behavior should be expected to stop working. [Other Info] [1] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/289 [2] https://gitlab.gnome.org/GNOME/nautilus/-/issues/634 [3] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573 [4] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1321 [5] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [6] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948008/+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 1958312] Re: Livepatch not working on Ubuntu 22.04 LTS
Thanks, indeed that should be a temporary situation. The software- properties code allows to enable livepatch since it's a LTS serie but the service hasn't been enabled yet and is failing. The situation could be handled better but it's going to be resolved once livepatch starts working for the LTS ** Package changed: xdg-desktop-portal-gtk (Ubuntu) => software- properties (Ubuntu) ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1958312 Title: Livepatch not working on Ubuntu 22.04 LTS Status in software-properties package in Ubuntu: Confirmed Bug description: No such file or directory error when I'll try to use livepatch on a 22.04 device with dev updates enabled. It turns off automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1958312/+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 1958658] Re: GTK File Chooser file type filter too restrictive
** Changed in: xdg-desktop-portal-gtk (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1958658 Title: GTK File Chooser file type filter too restrictive Status in xdg-desktop-portal-gtk package in Ubuntu: New Bug description: Description: Ubuntu 21.10 Release: 21.10 xdg-desktop-portal-gtk: Installed: 1.8.0-1build1 When calling the GTK File Chooser from inside another program such as Google Chrome, the files displayed are filtered according to a file extension filter. The bottom right of the chooser window shows a button "customised files". This creates a problem in that file extensions are an unreliable indication of file type. For example, when uploading an image to a website, Google Chrome filters for image files by lower case extensions. Any images with upper case file extensions are filtered out. The user has to select "all files" to see the files with upper case file names/extensions. Google Chrome is to blame for sending incomplete file filter information to the file chooser, however the file chooser could also match both upper and lower case extensions so that the calling program doesn't need to take this into account. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xdg-desktop-portal-gtk 1.8.0-1build1 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 15:20:00 2022 ExecutablePath: /usr/libexec/xdg-desktop-portal-gtk InstallationDate: Installed on 2019-10-11 (832 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: xdg-desktop-portal-gtk UpgradeStatus: Upgraded to impish on 2021-10-20 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1958658/+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 1958719] Re: Copy paste does not work from and to Desktop
*** This bug is a duplicate of bug 1948008 *** https://bugs.launchpad.net/bugs/1948008 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1948008 Copying and pasting files between desktop and Nautilus does not work -- 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/1958719 Title: Copy paste does not work from and to Desktop Status in nautilus package in Ubuntu: New Bug description: A similar problem is reported here by someone: https://askubuntu.com/questions/1241475/cut-paste-or-copy-paste-not- working-on-ubuntu-20-04-on-using-right-click-context Everything was working fine when I had installed Ubuntu. This problem began either ever since I did an update or perhaps after I installed (don't know which) program. The problem: If I copy a file/folder directly from the Desktop, then open Nautilus and try to paste the file/folder into any other folder, the Paste option is shown as disabled, in the right click menu. Image attached. Same way, if I copy a file/folder from Nautilus and try pasting it directly onto the Desktop, the Paste option is shown as disabled in the right click menu. However, when I open the Desktop folder in Nautilus, I can copy or paste any files or folders to any other file or folder that's open in Nautilus. I'm sure this is not a file or folder permission issue. I'm able to copy and move the files/folders without sudo when I use the terminal. If I try to copy a file from Nautilus and right click on any folder on the Desktop, the "paste into folder" option is not available either. Guys, Ubuntu has such really annoying bugs related to the Desktop. Please fix them ASAP. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 22 20:17:40 2022 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'205' b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-10-24 (89 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1958719/+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 1958710] Re: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main)
Thank you for your report, do you plan to work on that merge or did you just want to point out that the package has update available (if so we do know and have reports about outdated packages so you can avoid manual work in the futur) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1958710 Title: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main) Status in network-manager package in Ubuntu: New Bug description: There are some differences between versions from Debian and Ubuntu. A new version has been released a week ago. Debian Changelog: network-manager (1.34.0-2) unstable; urgency=medium * Demote wpasupplicant to Recommends. There are enough use cases for network-manager not involving Wi-Fi which justifies to make this dependency optional. (Closes: #919619, #980218) -- Michael Biebl Tue, 18 Jan 2022 20:59:36 +0100 network-manager (1.34.0-1) unstable; urgency=medium * New upstream version 1.34.0 * Rebase patches * Install nm-priv-helper service * Update symbols file for libnm0 -- Michael Biebl Fri, 14 Jan 2022 00:18:58 +0100 NM ChangeLog: = NetworkManager-1.34 Overview of changes since NetworkManager-1.32 = * initrd: wait for both IPv4 and IPv6 with "ip=dhcp,dhcp6". * core: better handle sd-resolved errors when resolving hostnames. * nmcli: fix import WireGuard profile with DNS domain and address family disabled. * ndisc: send router solicitations before expiry. * policy: send earlier the ip configs to the DNS manager. * core: support linking with LLD 13. * wireguard: importing wg-quick configuration files with nmcli no longer sets a negative, exclusive "dns-priority". This plays better with common split DNS setups that use systemd-resolved. Adjust the "dns-priority" to your liking after import yourself. * NetworkManager no longer listens for netlink events for traffic control objects (qdiscs and filters). * core: add internal nm-priv-helper service for separating privileges and have a way to drop capabilities from NetworkManager daemon. * bond: add support for setting queue-id of bond port. * dns: support configuring DNS over TLS (DoT) with systemd-resolved. * nmtui: add support for WireGuard profiles. * nmcli: add aliases `nmcli device up|down` beside connect|disconnect. * conscious language: Deprecate 'Device.Slaves' D-Bus property in favor of new 'Device.Ports' property. Depracate 'nm_device_*_get_slaves()' in favor of 'nm_device_get_ports()' in libnm. * nmcli: invoking nmcli command without arguments will now show 'default' instead of null address in route4 or route6 section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1958710/+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 1944727] Re: Screen shot leaves HP printer in non-working state
** Package changed: gnome-screenshot (Ubuntu) => cups (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1944727 Title: Screen shot leaves HP printer in non-working state Status in cups package in Ubuntu: New Bug description: This is a weird bug and difficult to debug. However: I have Ubuntu 21.04 fully updated as of 2021-09-23. Printing something that has been captured by gnome-screenshot will print fine with my HP Color Laserjet Pro M477fdw printer. However, it will leave the printer in a state where any subsequent print will fail, regardless of document or machine. Even printing from a Macbook Air will fail. The printer reports any subsequent file to be printed as corrupt and nothing comes out. The only way to recover from this state is to power-cycle the printer. This ONLY happen with screenshots. It happens BOTH when the screenshot has been pasted into Libre Office, and when the screenshot has been saved to a .png and printed from Image Viewer. This issue does however NOT happen on my CANON Pro 100 inkjet printer. So blame the printer, yes, but I have not been able to repeat it without gnome-screenshot. It's the common factor. Before Ubuntu 21.04 the default screen capture program was different, or at least it looked different, but previously I had no problem. I have been running Ubuntu with this printer for many years. Summary: I can only print screenshots once. I expect to be able to print two screen shots in sequence without requiring to power cycle the printer in between. I can upload an example file (that only print once) if required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1944727/+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 1947149] Re: Dock auto-hide off but hidden on screen unlock
Looks like the fix has been uploaded as part of: gnome-shell-extension-ubuntu-dock (72~ubuntu1) jammy; urgency=medium -- 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/1947149 Title: Dock auto-hide off but hidden on screen unlock Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Bug description: When the dock is set to "Auto-hide the Dock" = Off, the dock will un- hide when logging on. Both on boot and after locking the user. This causes any open full-screen windows to move and resize as needed. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 21.10 Release: 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-shell-extension-ubuntu-dock: Installed: 70~ubuntu3 Candidate: 70~ubuntu3 Version table: *** 70~ubuntu3 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish/main i386 Packages 100 /var/lib/dpkg/status 3) What you expected to happen The dock to start displayed (un-hidden) as per the settings. And not move. 4) What happened instead The dock appears from the left, as if hidden. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1947149/+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 1723117] Re: Desktop icons goes under the Dock, if the Dock is set to auto-hide.
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 72~ubuntu1 --- gnome-shell-extension-ubuntu-dock (72~ubuntu1) jammy; urgency=medium [ Marco Trevisan (Treviño) ] * Revert "extension: Disable starting in the overview" * locations: Do not manually dispose objects (LP: #1949352, LP: #1951599) * po/es.po: Remove duplicated entry for Quit translation * docking: Delay dash animation callback at actual completion * utils: Fix variable in error template string * appIcons: In case we have no window to activate, let's just present it * docking: Do not try to re-add a Meta.Later if one is already queued * docking: Optionally disable animation to overview on startup * dash: Track hover on separator item so that it can contribute to scrolling * dash: Remove the scroll view visibility idle if triggering actor is destroyed * docking: Handle monitoring of discrete GPU not to leak signals * appIcons: Random cleanups to use more relevant variable names * appIcons: Compare workspaces instead of their indexes * appIcons: Ensure we only consider as urgent the ones respecting our rules * appIcons: Use new-window action only when requested, avoiding duplication * appIcons: Fixed logic on handling preview click actions (LP: #1947445) * stylesheet: Use some better naming for start marging value * stylesheet: Use scss generation for overview-icon background * stylesheet: Set the dash-separator color in both horizontal and vertical mode * windowPreview: Try generating previews clones on meta later only if have valid size (LP: 1949572) * utils: Remove handlers in reversed order * Dash: Update appIcon geometry on parent geometry changes * docking: Reduce the space used by the window picker / app grid * cleanup: Use cached settings values instead of doing C calls * locations: Use shell domain to translate reused strings * locations: Use native GIcon as location Apps-icons (LP: #1874578) * locations: Use native Gio.FileMonitor rate limit instead of a custom idle * locations: Fix typo on FileManager app (un)wrapping functions * locations: Fix handling of location apps on isolated workspaces mode * locations: Also destroy all removable devices on Removables manager destruction * locations: Only emit changed signal if a monitored device has been removed * locations: Only update Trash icon on changes * locations: Remove unmounted locations by value * locations: Use native AppInfo's and Shell mount operations * metadata: Add support for gnome-shell 42 * fileManager1API: Cleanup the code to get windows from location path * fileManager1API: Keep windows paths cached so we can monitor changes * utils: Add support for (un)blocking signals handlers * locations: Smart managing wrapped windows backed applications signal connections * locations: Use proxy properties to expose private items to public object * locations: Chain up to parent destroy() function if any * locations: Manage sources as part of DtdData * locations: Manage windows changes in base class * cleanup: Move shellAppCompare under Utils as it's a generic tool * locations: Keep locations windows ordered following the shell algorithm * locations: Use windows array directly where there's no need for method call * locations: Resort and notify windows changes on user-time changes * locations: Sort location windows apps only demand * fileManager1API: Only emit windows-changed signal if windows / locations changed * fileManager1API: Manage unmanaged windows early * locations: Include actual app ID in the string representation * utils: Add CancellableChild, a GCancellable that monitors a parent instance * locations: Get Trash icon from the folder attributes * locations: Add support for showing custom icon files on mounts * fileManager1API: Include transient windows as part of the location windows * locations: Monitor windows-changed from apps and not from fm1Client (LP: #1947476) * locations: Ignore native file manager windows-changed signal emissions * locations: Try to get trash status from metadata info before iterating * locations: Move handling of trash logic into TrashAppInfo * locations: Manage all mountable volumes, whether they're mounted or not * locations: Add support for optionally showing all mountable devices * locations: Add support for showing network volumes * locations: Use ChildCancellable to avoid queuing multiple trash updates * locations: Do not try to perform (un)mount actions concurrently * appIcons: Show menu item as insensitive if the app is busy * locations: Wait for location apps to own windows before updating file-manager (LP: #1947476) * locations: Add support for starting app state * locations: Support opening new location windows when using nautilus * 10_ubuntu-dock.gschema.override: Update settings override for ubuntu * debian/control: Add support to GNOM
[Desktop-packages] [Bug 1874578] Re: Dock has very long load time when show-mounts is enabled
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 72~ubuntu1 --- gnome-shell-extension-ubuntu-dock (72~ubuntu1) jammy; urgency=medium [ Marco Trevisan (Treviño) ] * Revert "extension: Disable starting in the overview" * locations: Do not manually dispose objects (LP: #1949352, LP: #1951599) * po/es.po: Remove duplicated entry for Quit translation * docking: Delay dash animation callback at actual completion * utils: Fix variable in error template string * appIcons: In case we have no window to activate, let's just present it * docking: Do not try to re-add a Meta.Later if one is already queued * docking: Optionally disable animation to overview on startup * dash: Track hover on separator item so that it can contribute to scrolling * dash: Remove the scroll view visibility idle if triggering actor is destroyed * docking: Handle monitoring of discrete GPU not to leak signals * appIcons: Random cleanups to use more relevant variable names * appIcons: Compare workspaces instead of their indexes * appIcons: Ensure we only consider as urgent the ones respecting our rules * appIcons: Use new-window action only when requested, avoiding duplication * appIcons: Fixed logic on handling preview click actions (LP: #1947445) * stylesheet: Use some better naming for start marging value * stylesheet: Use scss generation for overview-icon background * stylesheet: Set the dash-separator color in both horizontal and vertical mode * windowPreview: Try generating previews clones on meta later only if have valid size (LP: 1949572) * utils: Remove handlers in reversed order * Dash: Update appIcon geometry on parent geometry changes * docking: Reduce the space used by the window picker / app grid * cleanup: Use cached settings values instead of doing C calls * locations: Use shell domain to translate reused strings * locations: Use native GIcon as location Apps-icons (LP: #1874578) * locations: Use native Gio.FileMonitor rate limit instead of a custom idle * locations: Fix typo on FileManager app (un)wrapping functions * locations: Fix handling of location apps on isolated workspaces mode * locations: Also destroy all removable devices on Removables manager destruction * locations: Only emit changed signal if a monitored device has been removed * locations: Only update Trash icon on changes * locations: Remove unmounted locations by value * locations: Use native AppInfo's and Shell mount operations * metadata: Add support for gnome-shell 42 * fileManager1API: Cleanup the code to get windows from location path * fileManager1API: Keep windows paths cached so we can monitor changes * utils: Add support for (un)blocking signals handlers * locations: Smart managing wrapped windows backed applications signal connections * locations: Use proxy properties to expose private items to public object * locations: Chain up to parent destroy() function if any * locations: Manage sources as part of DtdData * locations: Manage windows changes in base class * cleanup: Move shellAppCompare under Utils as it's a generic tool * locations: Keep locations windows ordered following the shell algorithm * locations: Use windows array directly where there's no need for method call * locations: Resort and notify windows changes on user-time changes * locations: Sort location windows apps only demand * fileManager1API: Only emit windows-changed signal if windows / locations changed * fileManager1API: Manage unmanaged windows early * locations: Include actual app ID in the string representation * utils: Add CancellableChild, a GCancellable that monitors a parent instance * locations: Get Trash icon from the folder attributes * locations: Add support for showing custom icon files on mounts * fileManager1API: Include transient windows as part of the location windows * locations: Monitor windows-changed from apps and not from fm1Client (LP: #1947476) * locations: Ignore native file manager windows-changed signal emissions * locations: Try to get trash status from metadata info before iterating * locations: Move handling of trash logic into TrashAppInfo * locations: Manage all mountable volumes, whether they're mounted or not * locations: Add support for optionally showing all mountable devices * locations: Add support for showing network volumes * locations: Use ChildCancellable to avoid queuing multiple trash updates * locations: Do not try to perform (un)mount actions concurrently * appIcons: Show menu item as insensitive if the app is busy * locations: Wait for location apps to own windows before updating file-manager (LP: #1947476) * locations: Add support for starting app state * locations: Support opening new location windows when using nautilus * 10_ubuntu-dock.gschema.override: Update settings override for ubuntu * debian/control: Add support to GNOM
[Desktop-packages] [Bug 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 72~ubuntu1 --- gnome-shell-extension-ubuntu-dock (72~ubuntu1) jammy; urgency=medium [ Marco Trevisan (Treviño) ] * Revert "extension: Disable starting in the overview" * locations: Do not manually dispose objects (LP: #1949352, LP: #1951599) * po/es.po: Remove duplicated entry for Quit translation * docking: Delay dash animation callback at actual completion * utils: Fix variable in error template string * appIcons: In case we have no window to activate, let's just present it * docking: Do not try to re-add a Meta.Later if one is already queued * docking: Optionally disable animation to overview on startup * dash: Track hover on separator item so that it can contribute to scrolling * dash: Remove the scroll view visibility idle if triggering actor is destroyed * docking: Handle monitoring of discrete GPU not to leak signals * appIcons: Random cleanups to use more relevant variable names * appIcons: Compare workspaces instead of their indexes * appIcons: Ensure we only consider as urgent the ones respecting our rules * appIcons: Use new-window action only when requested, avoiding duplication * appIcons: Fixed logic on handling preview click actions (LP: #1947445) * stylesheet: Use some better naming for start marging value * stylesheet: Use scss generation for overview-icon background * stylesheet: Set the dash-separator color in both horizontal and vertical mode * windowPreview: Try generating previews clones on meta later only if have valid size (LP: 1949572) * utils: Remove handlers in reversed order * Dash: Update appIcon geometry on parent geometry changes * docking: Reduce the space used by the window picker / app grid * cleanup: Use cached settings values instead of doing C calls * locations: Use shell domain to translate reused strings * locations: Use native GIcon as location Apps-icons (LP: #1874578) * locations: Use native Gio.FileMonitor rate limit instead of a custom idle * locations: Fix typo on FileManager app (un)wrapping functions * locations: Fix handling of location apps on isolated workspaces mode * locations: Also destroy all removable devices on Removables manager destruction * locations: Only emit changed signal if a monitored device has been removed * locations: Only update Trash icon on changes * locations: Remove unmounted locations by value * locations: Use native AppInfo's and Shell mount operations * metadata: Add support for gnome-shell 42 * fileManager1API: Cleanup the code to get windows from location path * fileManager1API: Keep windows paths cached so we can monitor changes * utils: Add support for (un)blocking signals handlers * locations: Smart managing wrapped windows backed applications signal connections * locations: Use proxy properties to expose private items to public object * locations: Chain up to parent destroy() function if any * locations: Manage sources as part of DtdData * locations: Manage windows changes in base class * cleanup: Move shellAppCompare under Utils as it's a generic tool * locations: Keep locations windows ordered following the shell algorithm * locations: Use windows array directly where there's no need for method call * locations: Resort and notify windows changes on user-time changes * locations: Sort location windows apps only demand * fileManager1API: Only emit windows-changed signal if windows / locations changed * fileManager1API: Manage unmanaged windows early * locations: Include actual app ID in the string representation * utils: Add CancellableChild, a GCancellable that monitors a parent instance * locations: Get Trash icon from the folder attributes * locations: Add support for showing custom icon files on mounts * fileManager1API: Include transient windows as part of the location windows * locations: Monitor windows-changed from apps and not from fm1Client (LP: #1947476) * locations: Ignore native file manager windows-changed signal emissions * locations: Try to get trash status from metadata info before iterating * locations: Move handling of trash logic into TrashAppInfo * locations: Manage all mountable volumes, whether they're mounted or not * locations: Add support for optionally showing all mountable devices * locations: Add support for showing network volumes * locations: Use ChildCancellable to avoid queuing multiple trash updates * locations: Do not try to perform (un)mount actions concurrently * appIcons: Show menu item as insensitive if the app is busy * locations: Wait for location apps to own windows before updating file-manager (LP: #1947476) * locations: Add support for starting app state * locations: Support opening new location windows when using nautilus * 10_ubuntu-dock.gschema.override: Update settings override for ubuntu * debian/control: Add support to GNOM
[Desktop-packages] [Bug 1947476] Re: Clicking the "Trash" entry in the dock shows both Files and Trash icon as open until the dock refreshes
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 72~ubuntu1 --- gnome-shell-extension-ubuntu-dock (72~ubuntu1) jammy; urgency=medium [ Marco Trevisan (Treviño) ] * Revert "extension: Disable starting in the overview" * locations: Do not manually dispose objects (LP: #1949352, LP: #1951599) * po/es.po: Remove duplicated entry for Quit translation * docking: Delay dash animation callback at actual completion * utils: Fix variable in error template string * appIcons: In case we have no window to activate, let's just present it * docking: Do not try to re-add a Meta.Later if one is already queued * docking: Optionally disable animation to overview on startup * dash: Track hover on separator item so that it can contribute to scrolling * dash: Remove the scroll view visibility idle if triggering actor is destroyed * docking: Handle monitoring of discrete GPU not to leak signals * appIcons: Random cleanups to use more relevant variable names * appIcons: Compare workspaces instead of their indexes * appIcons: Ensure we only consider as urgent the ones respecting our rules * appIcons: Use new-window action only when requested, avoiding duplication * appIcons: Fixed logic on handling preview click actions (LP: #1947445) * stylesheet: Use some better naming for start marging value * stylesheet: Use scss generation for overview-icon background * stylesheet: Set the dash-separator color in both horizontal and vertical mode * windowPreview: Try generating previews clones on meta later only if have valid size (LP: 1949572) * utils: Remove handlers in reversed order * Dash: Update appIcon geometry on parent geometry changes * docking: Reduce the space used by the window picker / app grid * cleanup: Use cached settings values instead of doing C calls * locations: Use shell domain to translate reused strings * locations: Use native GIcon as location Apps-icons (LP: #1874578) * locations: Use native Gio.FileMonitor rate limit instead of a custom idle * locations: Fix typo on FileManager app (un)wrapping functions * locations: Fix handling of location apps on isolated workspaces mode * locations: Also destroy all removable devices on Removables manager destruction * locations: Only emit changed signal if a monitored device has been removed * locations: Only update Trash icon on changes * locations: Remove unmounted locations by value * locations: Use native AppInfo's and Shell mount operations * metadata: Add support for gnome-shell 42 * fileManager1API: Cleanup the code to get windows from location path * fileManager1API: Keep windows paths cached so we can monitor changes * utils: Add support for (un)blocking signals handlers * locations: Smart managing wrapped windows backed applications signal connections * locations: Use proxy properties to expose private items to public object * locations: Chain up to parent destroy() function if any * locations: Manage sources as part of DtdData * locations: Manage windows changes in base class * cleanup: Move shellAppCompare under Utils as it's a generic tool * locations: Keep locations windows ordered following the shell algorithm * locations: Use windows array directly where there's no need for method call * locations: Resort and notify windows changes on user-time changes * locations: Sort location windows apps only demand * fileManager1API: Only emit windows-changed signal if windows / locations changed * fileManager1API: Manage unmanaged windows early * locations: Include actual app ID in the string representation * utils: Add CancellableChild, a GCancellable that monitors a parent instance * locations: Get Trash icon from the folder attributes * locations: Add support for showing custom icon files on mounts * fileManager1API: Include transient windows as part of the location windows * locations: Monitor windows-changed from apps and not from fm1Client (LP: #1947476) * locations: Ignore native file manager windows-changed signal emissions * locations: Try to get trash status from metadata info before iterating * locations: Move handling of trash logic into TrashAppInfo * locations: Manage all mountable volumes, whether they're mounted or not * locations: Add support for optionally showing all mountable devices * locations: Add support for showing network volumes * locations: Use ChildCancellable to avoid queuing multiple trash updates * locations: Do not try to perform (un)mount actions concurrently * appIcons: Show menu item as insensitive if the app is busy * locations: Wait for location apps to own windows before updating file-manager (LP: #1947476) * locations: Add support for starting app state * locations: Support opening new location windows when using nautilus * 10_ubuntu-dock.gschema.override: Update settings override for ubuntu * debian/control: Add support to GNOM
[Desktop-packages] [Bug 1949352] Re: Removable drives are not auto-mounted after screen lock/unlock
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 72~ubuntu1 --- gnome-shell-extension-ubuntu-dock (72~ubuntu1) jammy; urgency=medium [ Marco Trevisan (Treviño) ] * Revert "extension: Disable starting in the overview" * locations: Do not manually dispose objects (LP: #1949352, LP: #1951599) * po/es.po: Remove duplicated entry for Quit translation * docking: Delay dash animation callback at actual completion * utils: Fix variable in error template string * appIcons: In case we have no window to activate, let's just present it * docking: Do not try to re-add a Meta.Later if one is already queued * docking: Optionally disable animation to overview on startup * dash: Track hover on separator item so that it can contribute to scrolling * dash: Remove the scroll view visibility idle if triggering actor is destroyed * docking: Handle monitoring of discrete GPU not to leak signals * appIcons: Random cleanups to use more relevant variable names * appIcons: Compare workspaces instead of their indexes * appIcons: Ensure we only consider as urgent the ones respecting our rules * appIcons: Use new-window action only when requested, avoiding duplication * appIcons: Fixed logic on handling preview click actions (LP: #1947445) * stylesheet: Use some better naming for start marging value * stylesheet: Use scss generation for overview-icon background * stylesheet: Set the dash-separator color in both horizontal and vertical mode * windowPreview: Try generating previews clones on meta later only if have valid size (LP: 1949572) * utils: Remove handlers in reversed order * Dash: Update appIcon geometry on parent geometry changes * docking: Reduce the space used by the window picker / app grid * cleanup: Use cached settings values instead of doing C calls * locations: Use shell domain to translate reused strings * locations: Use native GIcon as location Apps-icons (LP: #1874578) * locations: Use native Gio.FileMonitor rate limit instead of a custom idle * locations: Fix typo on FileManager app (un)wrapping functions * locations: Fix handling of location apps on isolated workspaces mode * locations: Also destroy all removable devices on Removables manager destruction * locations: Only emit changed signal if a monitored device has been removed * locations: Only update Trash icon on changes * locations: Remove unmounted locations by value * locations: Use native AppInfo's and Shell mount operations * metadata: Add support for gnome-shell 42 * fileManager1API: Cleanup the code to get windows from location path * fileManager1API: Keep windows paths cached so we can monitor changes * utils: Add support for (un)blocking signals handlers * locations: Smart managing wrapped windows backed applications signal connections * locations: Use proxy properties to expose private items to public object * locations: Chain up to parent destroy() function if any * locations: Manage sources as part of DtdData * locations: Manage windows changes in base class * cleanup: Move shellAppCompare under Utils as it's a generic tool * locations: Keep locations windows ordered following the shell algorithm * locations: Use windows array directly where there's no need for method call * locations: Resort and notify windows changes on user-time changes * locations: Sort location windows apps only demand * fileManager1API: Only emit windows-changed signal if windows / locations changed * fileManager1API: Manage unmanaged windows early * locations: Include actual app ID in the string representation * utils: Add CancellableChild, a GCancellable that monitors a parent instance * locations: Get Trash icon from the folder attributes * locations: Add support for showing custom icon files on mounts * fileManager1API: Include transient windows as part of the location windows * locations: Monitor windows-changed from apps and not from fm1Client (LP: #1947476) * locations: Ignore native file manager windows-changed signal emissions * locations: Try to get trash status from metadata info before iterating * locations: Move handling of trash logic into TrashAppInfo * locations: Manage all mountable volumes, whether they're mounted or not * locations: Add support for optionally showing all mountable devices * locations: Add support for showing network volumes * locations: Use ChildCancellable to avoid queuing multiple trash updates * locations: Do not try to perform (un)mount actions concurrently * appIcons: Show menu item as insensitive if the app is busy * locations: Wait for location apps to own windows before updating file-manager (LP: #1947476) * locations: Add support for starting app state * locations: Support opening new location windows when using nautilus * 10_ubuntu-dock.gschema.override: Update settings override for ubuntu * debian/control: Add support to GNOM
[Desktop-packages] [Bug 1951599] Re: gnome-shell logs errors when ejecting SD card
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 72~ubuntu1 --- gnome-shell-extension-ubuntu-dock (72~ubuntu1) jammy; urgency=medium [ Marco Trevisan (Treviño) ] * Revert "extension: Disable starting in the overview" * locations: Do not manually dispose objects (LP: #1949352, LP: #1951599) * po/es.po: Remove duplicated entry for Quit translation * docking: Delay dash animation callback at actual completion * utils: Fix variable in error template string * appIcons: In case we have no window to activate, let's just present it * docking: Do not try to re-add a Meta.Later if one is already queued * docking: Optionally disable animation to overview on startup * dash: Track hover on separator item so that it can contribute to scrolling * dash: Remove the scroll view visibility idle if triggering actor is destroyed * docking: Handle monitoring of discrete GPU not to leak signals * appIcons: Random cleanups to use more relevant variable names * appIcons: Compare workspaces instead of their indexes * appIcons: Ensure we only consider as urgent the ones respecting our rules * appIcons: Use new-window action only when requested, avoiding duplication * appIcons: Fixed logic on handling preview click actions (LP: #1947445) * stylesheet: Use some better naming for start marging value * stylesheet: Use scss generation for overview-icon background * stylesheet: Set the dash-separator color in both horizontal and vertical mode * windowPreview: Try generating previews clones on meta later only if have valid size (LP: 1949572) * utils: Remove handlers in reversed order * Dash: Update appIcon geometry on parent geometry changes * docking: Reduce the space used by the window picker / app grid * cleanup: Use cached settings values instead of doing C calls * locations: Use shell domain to translate reused strings * locations: Use native GIcon as location Apps-icons (LP: #1874578) * locations: Use native Gio.FileMonitor rate limit instead of a custom idle * locations: Fix typo on FileManager app (un)wrapping functions * locations: Fix handling of location apps on isolated workspaces mode * locations: Also destroy all removable devices on Removables manager destruction * locations: Only emit changed signal if a monitored device has been removed * locations: Only update Trash icon on changes * locations: Remove unmounted locations by value * locations: Use native AppInfo's and Shell mount operations * metadata: Add support for gnome-shell 42 * fileManager1API: Cleanup the code to get windows from location path * fileManager1API: Keep windows paths cached so we can monitor changes * utils: Add support for (un)blocking signals handlers * locations: Smart managing wrapped windows backed applications signal connections * locations: Use proxy properties to expose private items to public object * locations: Chain up to parent destroy() function if any * locations: Manage sources as part of DtdData * locations: Manage windows changes in base class * cleanup: Move shellAppCompare under Utils as it's a generic tool * locations: Keep locations windows ordered following the shell algorithm * locations: Use windows array directly where there's no need for method call * locations: Resort and notify windows changes on user-time changes * locations: Sort location windows apps only demand * fileManager1API: Only emit windows-changed signal if windows / locations changed * fileManager1API: Manage unmanaged windows early * locations: Include actual app ID in the string representation * utils: Add CancellableChild, a GCancellable that monitors a parent instance * locations: Get Trash icon from the folder attributes * locations: Add support for showing custom icon files on mounts * fileManager1API: Include transient windows as part of the location windows * locations: Monitor windows-changed from apps and not from fm1Client (LP: #1947476) * locations: Ignore native file manager windows-changed signal emissions * locations: Try to get trash status from metadata info before iterating * locations: Move handling of trash logic into TrashAppInfo * locations: Manage all mountable volumes, whether they're mounted or not * locations: Add support for optionally showing all mountable devices * locations: Add support for showing network volumes * locations: Use ChildCancellable to avoid queuing multiple trash updates * locations: Do not try to perform (un)mount actions concurrently * appIcons: Show menu item as insensitive if the app is busy * locations: Wait for location apps to own windows before updating file-manager (LP: #1947476) * locations: Add support for starting app state * locations: Support opening new location windows when using nautilus * 10_ubuntu-dock.gschema.override: Update settings override for ubuntu * debian/control: Add support to GNOM
[Desktop-packages] [Bug 1952107] Re: Google Contacts API Deprecated
This bug was fixed in the package evolution - 3.40.4-1ubuntu2 --- evolution (3.40.4-1ubuntu2) impish; urgency=medium * debian/patches/git_contact_api.patch: - use the right version of the eds webdav API (lp: #1952107) -- Sebastien Bacher Tue, 30 Nov 2021 21:38:27 +0100 ** Changed in: evolution (Ubuntu Impish) Status: Fix Committed => Fix Released ** Changed in: evolution-data-server (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1952107] Re: Google Contacts API Deprecated
This bug was fixed in the package evolution-data-server - 3.40.4-1ubuntu1 --- evolution-data-server (3.40.4-1ubuntu1) impish; urgency=medium * debian/patches/git-contact-api.patch: - use the new google contact api since the old one is deprecated and is going to stop working (lp: #1952107) -- Sebastien Bacher Fri, 26 Nov 2021 18:23:27 +0100 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1952107] Update Released
The verification of the Stable Release Update for evolution has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1958811] Re: If apt installs snap package, then show size of it
** Package changed: snap (Ubuntu) => snapd (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1958811
Title:
If apt installs snap package, then show size of it
Status in apt package in Ubuntu:
Invalid
Status in chromium-browser package in Ubuntu:
New
Status in snapd package in Ubuntu:
New
Bug description:
If apt installs snap package, then show size of it
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
Uname: Linux 5.15.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
DRM.card0-Virtual-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
modes: 1024x768 1920x1080 1600x1200 1680x1050 1680x1050 1400x1050 1400x1050
1600x900 1280x1024 1440x900 1440x900 1280x960 1366x768 1366x768 1360x768
1280x800 1280x800 1280x768 1280x768 1280x720 800x600 800x600 848x480 640x480
Date: Mon Jan 24 03:36:26 2022
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/xvda3 ext411G 8,3G 1,5G 86% /
tmpfs tmpfs 1,9G 6,6M 1,9G 1% /dev/shm
/dev/xvda3 ext411G 8,3G 1,5G 86% /
InstallationDate: Installed on 2022-01-21 (2 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
(20220121)
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: Xen HVM domU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic
root=UUID=d8fb805e-11ec-4105-9320-3618a2dfa835 ro quiet splash vt.handoff=7
Snap.Changes:
ID Status Spawn Ready Summary
4Done2022-01-24T03:33:37+02:00 2022-01-24T03:34:29+02:00 Install
"chromium" snap
Snap.ChromeDriverVersion: ChromeDriver 97.0.4692.99
(d740da257583289dbebd2eb37e8668928fac5ead-refs/branch-heads/4692@{#1461})
Snap.ChromiumVersion: Chromium 97.0.4692.99 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2022
dmi.bios.release: 4.14
dmi.bios.vendor: Xen
dmi.bios.version: 4.14.3
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias:
dmi:bvnXen:bvr4.14.3:bd01/08/2022:br4.14:svnXen:pnHVMdomU:pvr4.14.3:cvnXen:ct1:cvr:sku:
dmi.product.name: HVM domU
dmi.product.version: 4.14.3
dmi.sys.vendor: Xen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1958811/+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 1958810] Re: Apt installing snap package if got some error why didnt finish, thinks apt is installed, but snap cant be removed
** Package changed: snap (Ubuntu) => snapd (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1958810
Title:
Apt installing snap package if got some error why didnt finish, thinks
apt is installed, but snap cant be removed
Status in apt package in Ubuntu:
Invalid
Status in chromium-browser package in Ubuntu:
New
Status in snapd package in Ubuntu:
New
Bug description:
Apt installing snap package if got some error why didnt finish, thinks
apt is installed, but snap cant be removed
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
Uname: Linux 5.15.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
DRM.card0-Virtual-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
modes: 1024x768 1920x1080 1600x1200 1680x1050 1680x1050 1400x1050 1400x1050
1600x900 1280x1024 1440x900 1440x900 1280x960 1366x768 1366x768 1360x768
1280x800 1280x800 1280x768 1280x768 1280x720 800x600 800x600 848x480 640x480
Date: Mon Jan 24 03:37:18 2022
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/xvda3 ext411G 8,3G 1,4G 86% /
tmpfs tmpfs 1,9G 6,6M 1,9G 1% /dev/shm
/dev/xvda3 ext411G 8,3G 1,4G 86% /
InstallationDate: Installed on 2022-01-21 (2 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
(20220121)
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: Xen HVM domU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic
root=UUID=d8fb805e-11ec-4105-9320-3618a2dfa835 ro quiet splash vt.handoff=7
Snap.Changes:
ID Status Spawn Ready Summary
4Done2022-01-24T03:33:37+02:00 2022-01-24T03:34:29+02:00 Install
"chromium" snap
Snap.ChromeDriverVersion: ChromeDriver 97.0.4692.99
(d740da257583289dbebd2eb37e8668928fac5ead-refs/branch-heads/4692@{#1461})
Snap.ChromiumVersion: Chromium 97.0.4692.99 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2022
dmi.bios.release: 4.14
dmi.bios.vendor: Xen
dmi.bios.version: 4.14.3
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias:
dmi:bvnXen:bvr4.14.3:bd01/08/2022:br4.14:svnXen:pnHVMdomU:pvr4.14.3:cvnXen:ct1:cvr:sku:
dmi.product.name: HVM domU
dmi.product.version: 4.14.3
dmi.sys.vendor: Xen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1958810/+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 1958812] Re: If apt installs snap package, then warn, because maybe i dont want snap package.
** Package changed: snap (Ubuntu) => snapd (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1958812
Title:
If apt installs snap package, then warn, because maybe i dont want
snap package.
Status in apt package in Ubuntu:
Won't Fix
Status in chromium-browser package in Ubuntu:
New
Status in snapd package in Ubuntu:
New
Bug description:
If apt installs snap package, then warn, because maybe i dont want
snap package.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
Uname: Linux 5.15.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
DRM.card0-Virtual-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
modes: 1024x768 1920x1080 1600x1200 1680x1050 1680x1050 1400x1050 1400x1050
1600x900 1280x1024 1440x900 1440x900 1280x960 1366x768 1366x768 1360x768
1280x800 1280x800 1280x768 1280x768 1280x720 800x600 800x600 848x480 640x480
Date: Mon Jan 24 03:35:44 2022
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/xvda3 ext411G 8,3G 1,5G 86% /
tmpfs tmpfs 1,9G 9,1M 1,9G 1% /dev/shm
/dev/xvda3 ext411G 8,3G 1,5G 86% /
InstallationDate: Installed on 2022-01-21 (2 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
(20220121)
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: Xen HVM domU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic
root=UUID=d8fb805e-11ec-4105-9320-3618a2dfa835 ro quiet splash vt.handoff=7
Snap.Changes:
ID Status Spawn Ready Summary
4Done2022-01-24T03:33:37+02:00 2022-01-24T03:34:29+02:00 Install
"chromium" snap
Snap.ChromeDriverVersion: ChromeDriver 97.0.4692.99
(d740da257583289dbebd2eb37e8668928fac5ead-refs/branch-heads/4692@{#1461})
Snap.ChromiumVersion: Chromium 97.0.4692.99 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2022
dmi.bios.release: 4.14
dmi.bios.vendor: Xen
dmi.bios.version: 4.14.3
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias:
dmi:bvnXen:bvr4.14.3:bd01/08/2022:br4.14:svnXen:pnHVMdomU:pvr4.14.3:cvnXen:ct1:cvr:sku:
dmi.product.name: HVM domU
dmi.product.version: 4.14.3
dmi.sys.vendor: Xen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1958812/+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 1958839] Re: mouse not working
Thanks for the bug report. According to Lsusb.txt above, there is no mouse or wireless receiver plugged into any USB port. So this is a kernel bug if anything. ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1958839 Title: mouse not working Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Hi I got a Redragon M808-KS WIRED & WIRELESS mouse and it is working fine in windows. But, when I switch to Ubuntu it is not working and the strange part is the mouse is plug and play type and does not need any particular driver. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.86 Tue Oct 26 21:55:45 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 11:47:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.86, 5.11.0-41-generic, x86_64: installed nvidia, 470.86, 5.13.0-27-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:11cd] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:11cd] InstallationDate: Installed on 2021-10-21 (94 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=01a2cb99-7964-4a0b-a8f4-2b16aa8fdd89 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.204:bd01/23/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N550JK dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958839/+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 1958839] [NEW] mouse not working
Public bug reported: Hi I got a Redragon M808-KS WIRED & WIRELESS mouse and it is working fine in windows. But, when I switch to Ubuntu it is not working and the strange part is the mouse is plug and play type and does not need any particular driver. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.86 Tue Oct 26 21:55:45 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 24 11:47:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.86, 5.11.0-41-generic, x86_64: installed nvidia, 470.86, 5.13.0-27-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:11cd] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:11cd] InstallationDate: Installed on 2021-10-21 (94 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=01a2cb99-7964-4a0b-a8f4-2b16aa8fdd89 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.204:bd01/23/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N550JK dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1958839 Title: mouse not working Status in xorg package in Ubuntu: New Bug description: Hi I got a Redragon M808-KS WIRED & WIRELESS mouse and it is working fine in windows. But, when I switch to Ubuntu it is not working and the strange part is the mouse is plug and play type and does not need any particular driver. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.86 Tue Oct 26 21:55:45 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Er
[Desktop-packages] [Bug 1958811] Re: If apt installs snap package, then show size of it
Arguably people could hack in an override for Installed-Size when
building the deb somehow to give a rough estimate, but might not be
worth the effort.
** Changed in: apt (Ubuntu)
Status: New => Won't Fix
** Changed in: apt (Ubuntu)
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1958811
Title:
If apt installs snap package, then show size of it
Status in apt package in Ubuntu:
Invalid
Status in chromium-browser package in Ubuntu:
New
Status in snap package in Ubuntu:
New
Bug description:
If apt installs snap package, then show size of it
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
Uname: Linux 5.15.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
DRM.card0-Virtual-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
modes: 1024x768 1920x1080 1600x1200 1680x1050 1680x1050 1400x1050 1400x1050
1600x900 1280x1024 1440x900 1440x900 1280x960 1366x768 1366x768 1360x768
1280x800 1280x800 1280x768 1280x768 1280x720 800x600 800x600 848x480 640x480
Date: Mon Jan 24 03:36:26 2022
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/xvda3 ext411G 8,3G 1,5G 86% /
tmpfs tmpfs 1,9G 6,6M 1,9G 1% /dev/shm
/dev/xvda3 ext411G 8,3G 1,5G 86% /
InstallationDate: Installed on 2022-01-21 (2 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
(20220121)
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: Xen HVM domU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic
root=UUID=d8fb805e-11ec-4105-9320-3618a2dfa835 ro quiet splash vt.handoff=7
Snap.Changes:
ID Status Spawn Ready Summary
4Done2022-01-24T03:33:37+02:00 2022-01-24T03:34:29+02:00 Install
"chromium" snap
Snap.ChromeDriverVersion: ChromeDriver 97.0.4692.99
(d740da257583289dbebd2eb37e8668928fac5ead-refs/branch-heads/4692@{#1461})
Snap.ChromiumVersion: Chromium 97.0.4692.99 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2022
dmi.bios.release: 4.14
dmi.bios.vendor: Xen
dmi.bios.version: 4.14.3
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias:
dmi:bvnXen:bvr4.14.3:bd01/08/2022:br4.14:svnXen:pnHVMdomU:pvr4.14.3:cvnXen:ct1:cvr:sku:
dmi.product.name: HVM domU
dmi.product.version: 4.14.3
dmi.sys.vendor: Xen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1958811/+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 1958810] Re: Apt installing snap package if got some error why didnt finish, thinks apt is installed, but snap cant be removed
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1958810
Title:
Apt installing snap package if got some error why didnt finish, thinks
apt is installed, but snap cant be removed
Status in apt package in Ubuntu:
Invalid
Status in chromium-browser package in Ubuntu:
New
Status in snap package in Ubuntu:
New
Bug description:
Apt installing snap package if got some error why didnt finish, thinks
apt is installed, but snap cant be removed
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
Uname: Linux 5.15.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
DRM.card0-Virtual-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
modes: 1024x768 1920x1080 1600x1200 1680x1050 1680x1050 1400x1050 1400x1050
1600x900 1280x1024 1440x900 1440x900 1280x960 1366x768 1366x768 1360x768
1280x800 1280x800 1280x768 1280x768 1280x720 800x600 800x600 848x480 640x480
Date: Mon Jan 24 03:37:18 2022
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/xvda3 ext411G 8,3G 1,4G 86% /
tmpfs tmpfs 1,9G 6,6M 1,9G 1% /dev/shm
/dev/xvda3 ext411G 8,3G 1,4G 86% /
InstallationDate: Installed on 2022-01-21 (2 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
(20220121)
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: Xen HVM domU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic
root=UUID=d8fb805e-11ec-4105-9320-3618a2dfa835 ro quiet splash vt.handoff=7
Snap.Changes:
ID Status Spawn Ready Summary
4Done2022-01-24T03:33:37+02:00 2022-01-24T03:34:29+02:00 Install
"chromium" snap
Snap.ChromeDriverVersion: ChromeDriver 97.0.4692.99
(d740da257583289dbebd2eb37e8668928fac5ead-refs/branch-heads/4692@{#1461})
Snap.ChromiumVersion: Chromium 97.0.4692.99 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2022
dmi.bios.release: 4.14
dmi.bios.vendor: Xen
dmi.bios.version: 4.14.3
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias:
dmi:bvnXen:bvr4.14.3:bd01/08/2022:br4.14:svnXen:pnHVMdomU:pvr4.14.3:cvnXen:ct1:cvr:sku:
dmi.product.name: HVM domU
dmi.product.version: 4.14.3
dmi.sys.vendor: Xen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1958810/+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 1958812] Re: If apt installs snap package, then warn, because maybe i dont want snap package.
** Changed in: apt (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1958812
Title:
If apt installs snap package, then warn, because maybe i dont want
snap package.
Status in apt package in Ubuntu:
Won't Fix
Status in chromium-browser package in Ubuntu:
New
Status in snap package in Ubuntu:
New
Bug description:
If apt installs snap package, then warn, because maybe i dont want
snap package.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
Uname: Linux 5.15.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
DRM.card0-Virtual-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
modes: 1024x768 1920x1080 1600x1200 1680x1050 1680x1050 1400x1050 1400x1050
1600x900 1280x1024 1440x900 1440x900 1280x960 1366x768 1366x768 1360x768
1280x800 1280x800 1280x768 1280x768 1280x720 800x600 800x600 848x480 640x480
Date: Mon Jan 24 03:35:44 2022
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/xvda3 ext411G 8,3G 1,5G 86% /
tmpfs tmpfs 1,9G 9,1M 1,9G 1% /dev/shm
/dev/xvda3 ext411G 8,3G 1,5G 86% /
InstallationDate: Installed on 2022-01-21 (2 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
(20220121)
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: Xen HVM domU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic
root=UUID=d8fb805e-11ec-4105-9320-3618a2dfa835 ro quiet splash vt.handoff=7
Snap.Changes:
ID Status Spawn Ready Summary
4Done2022-01-24T03:33:37+02:00 2022-01-24T03:34:29+02:00 Install
"chromium" snap
Snap.ChromeDriverVersion: ChromeDriver 97.0.4692.99
(d740da257583289dbebd2eb37e8668928fac5ead-refs/branch-heads/4692@{#1461})
Snap.ChromiumVersion: Chromium 97.0.4692.99 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2022
dmi.bios.release: 4.14
dmi.bios.vendor: Xen
dmi.bios.version: 4.14.3
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias:
dmi:bvnXen:bvr4.14.3:bd01/08/2022:br4.14:svnXen:pnHVMdomU:pvr4.14.3:cvnXen:ct1:cvr:sku:
dmi.product.name: HVM domU
dmi.product.version: 4.14.3
dmi.sys.vendor: Xen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1958812/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
This is now part of Azure's cloud images (focal to devel) and I can confirm that it fixes the issue. -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Incomplete Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Incomplete Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(
