[Desktop-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported
** Changed in: supysonic (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: New Status in pygobject package in Ubuntu: Fix Released Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: New Status in python-taskflow package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: Invalid Status in supysonic package in Ubuntu: Fix Released Status in vorta package in Ubuntu: New Status in ipywidgets package in Debian: New Status in pygobject package in Debian: Fix Released Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: Confirmed Status in python-hypothesis package in Debian: Fix Released Status in supysonic package in Debian: Fix Released Status in vorta package in Debian: Confirmed Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942702] Re: Ubuntu Dock "Show Applications" button: click target doesn't extend to screen edges
** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu) Status: New => In Progress ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => High ** Changed in: yaru-theme (Ubuntu) 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/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: In Progress 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 1723117] Re: Desktop icons goes under the Dock, if the Dock is set to auto-hide.
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Low => Medium ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Low => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Triaged => 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/1723117 Title: Desktop icons goes under the Dock, if the Dock is set to auto-hide. Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: This bug is found in Artful. Desktop icons goes under the Dock, if the Dock is set to auto-hide. Either the Dock should auto-hide on the Desktop as well, or the Desktop Icons should leave a margin with the same size of the Dock. This happen both horizontal and vertical Dock positions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1723117/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934185] Re: Ubuntu Dock popup menu in top left corner of the screen and won't go away
Akbarkhon, do you have also a log from journalctl /usr/bin/gnome-shell for that? -- 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/1934185 Title: Ubuntu Dock popup menu in top left corner of the screen and won't go away Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Every so often, typically when I'm using Thunderbird, I attempt to use the dock context menu to create a new window or something like that, and the "New Window" popup comes up, but does not work. Attempts to click on it have no effect. I cannot make the popup go away, other than by logging out and logging back in again (or rebooting). I did not observe this problem until I installed Ubuntu 21.04, so I expect it's a glitch that is new to this release. See attached screenshot for an example of the popup that won't go away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 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: Wed Jun 30 10:57:22 2021 InstallationDate: Installed on 2018-08-03 (1062 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-06-03 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1934185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945679] Re: character duplicates and log duplicates OS icons and unattended update last night. that was me. i guess. 18.0 > 20.0 upgrade.
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1945679 Title: character duplicates and log duplicates OS icons and unattended update last night. that was me. i guess. 18.0 > 20.0 upgrade. Status in firefox package in Ubuntu: Expired Bug description: Let me know if I can help more thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 92.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: c 1607 F pulseaudio /dev/snd/pcmC0D0p: c 1607 F...m pulseaudio BuildID: 20210903235534 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 09:46:22 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:358 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2021-09-30 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.1.1 dev wlx00c0ca9587ea proto dhcp metric 600 169.254.0.0/16 dev wlx00c0ca9587ea scope link metric 1000 192.168.1.0/24 dev wlx00c0ca9587ea proto kernel scope link src 192.168.1.9 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:358 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=92.0/20210903235534 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to focal on 2021-09-30 (0 days ago) dmi.bios.date: 05/07/2019 dmi.bios.vendor: AMI dmi.bios.version: F.15 dmi.board.asset.tag: 8CC8400GVQ dmi.board.name: 8446 dmi.board.vendor: HP dmi.board.version: dmi.chassis.asset.tag: 8CC8400GVQ dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.15:bd05/07/2019:svnHP:pnHPAll-in-One22-c0xx:pvr:rvnHP:rn8446:rvr:cvnHP:ct13:cvr: dmi.product.family: 103C_53311M HP OPP dmi.product.name: HP All-in-One 22-c0xx dmi.product.sku: 3LB95AA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1945679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958823] Re: Xorg freeze
*** This bug is a duplicate of bug 1958412 *** https://bugs.launchpad.net/bugs/1958412 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1958412, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Tags added: amdgpu ** Summary changed: - Xorg freeze + Screen Keeps Blinking/Flickering after waking up from lock ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** This bug has been marked a duplicate of bug 1958412 [amdgpu] at startup and shutdown screen gets white noise -- 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/1958823 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Screen Keeps Blinking/Flickering after waking up from lock 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 10:44:54 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days 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 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) 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 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.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/1958823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958823] [NEW] Xorg freeze
Public bug reported: Screen Keeps Blinking/Flickering after waking up from lock 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 10:44:54 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days 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 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) 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 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.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/1958823 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Screen Keeps Blinking/Flickering after waking up from lock 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 10:44:54 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days 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 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) 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:
[Desktop-packages] [Bug 1958673] Re: SRU Request for upgrade to X-Server 1.20.14 in focal/20.04-LTS
** Tags added: focal -- 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/1958673 Title: SRU Request for upgrade to X-Server 1.20.14 in focal/20.04-LTS Status in psychtoolbox-3 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I was asked by one of your X-Server maintainers (Timo) to file a bug report here to request an upgrade to the current X-Server 1.20.14 for focal / Ubuntu 20.04-LTS from X-Server 1.20.13. I think this is called a SRU? The 1.20.14 version contains patches to fix some recent CVE's which are already in your 1.20.13 server, and additionally two patches from myself, cfe. the following merge request for the backport: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/778 Therefore an upgrade to 1.20.14 would add my two patches from that merge request. These are trivial backports from master and X-Server 21.1, which did not need any adaptation of the patches. One patch is a bug fix for a bug present in server 1.20 since day one. The other patch can be considered a regression fix for Ubuntu 20.04-LTS on hybrid graphics laptops with Intel iGPU + some other dGPU, although this is not a regression in the X-Server itself, but how the video driver selection by current Ubuntu interacts with the server. See explanation below why i consider it a regression fix. One patch fixes a bug: "Fix RandR leasing for more than 1 simultaneously active lease." The bug is a trivial code bug, which was there since RandR leasing was introduced into the 1.20 server by Keith Packard. Keith has reviewed my bug description and fix and agreed that it is indeed a bug and that my fix is correct. See the following merge request for the master branch with Keith's R-b in the discussion: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/767 The bug triggers whenever more than one RandR output gets leased out simultaneously during a session. It doesn't matter if multiple outputs get leased to a single client application, or if multiple separate client applications each lease out one output, or any mix of these. Only the very last output leased in a session can be released back to the server by the corresponding client (voluntarily or due to client exit, crash etc.). All other previously leased out outputs by the same or other clients will be completely dead and unusable until the X-Session is terminated and the X-Server restarted. So this can be seen as a denial of service bug. Typically affected applications would be Vulkan applications using the direct display extension, e.g., the octave-psychtoolbox-3 package in Ubuntu for scientific/medical research, or high end video games which may use this functionality, and probably most prominently VR applications built with SteamVR or the OpenXR Monado runtime and VR compositor. It has been tested extensively by myself on single X-Screen and dual X-Screen setups with 1, 2 and three displays, leasing out 1, 2 or 3 outputs. The second patch is "modesetting: Allow Present flips with mismatched stride on atomic drivers." It applies to the xorg-video-modesetting ddx. It does not fix a bug in the strict sense, but it does improve the quality and performance of unredirected fullscreen applications like video games or scientific software like octave-psychtoolbox-3 under PRIME render offload in a way that turns them from "technically correct behavior, but unusable in practice" to "good". The patch is based on a tip by Michel Daenzer from AMD. See the following original merge request for X-Server master for details: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/740 On modern kernels and atomic modesetting drivers, the patch allows the modesetting-ddx to use page flipping for fullscreen applications even if the Pixmap stride between the display gpu (iGPU, e.g., Intel, AMD) and the render offload gpu (e.g., AMD, NVidia) is mismatched, as atomic modesetting drivers can easily handle that. Without the patch, on such mismatched stride configurations, rejecting the pageflip, normally the X-Server and modesetting-ddx would fall back to a fullscreen copy swap, executed via glamor and therefore Mesa as a framebuffer copy from application backbuffer to system/X-Server frontbuffer. This increases required memory bandwidth and thereby reduces cpu and gpu performance, increases latency and the potential for skipped frames, e.g., for OpenGL and Vulkan applications, and makes presentation timestamps unreliable, which is especially bad for scientific applications like the octave-psychtoolbox-3 package. More importantly for the general case, it causes massive visual tearing and display artifacts. The current implementation of the X-Servers DRI3/Present backend
[Desktop-packages] [Bug 1958684] Re: gnome-shell crashed with SIGFPE in meta_wayland_xdg_toplevel_send_configure() from meta_window_wayland_configure()
Also tracked in: https://gitlab.gnome.org/GNOME/mutter/-/issues/1527 https://gitlab.gnome.org/GNOME/mutter/-/issues/1739 ** Tags added: fixed-in-40 fixed-upstream ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/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 1958684] Re: gnome-shell crashed with SIGFPE in meta_wayland_xdg_toplevel_send_configure() from meta_window_wayland_configure()
Tracking in https://errors.ubuntu.com/problem/bd270ee843b327813e28ccddde4a1357b64e1326 ** Summary changed: - gnome-shell on wayland crashes when starting Qt Creator + gnome-shell crashed with SIGFPE in meta_wayland_xdg_toplevel_send_configure() from meta_window_wayland_configure() ** Description changed: + 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. + 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. + "-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 + ?? () 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: ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1958684/+attachment/5556248/+files/CoreDump.gz ** Information type changed from Private to Public ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1527 https://gitlab.gnome.org/GNOME/mutter/-/issues/1527 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1739 https://gitlab.gnome.org/GNOME/mutter/-/issues/1739 -- 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/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
[Desktop-packages] [Bug 1958818] Re: /usr/bin/gnome-shell:8:meta_wayland_xdg_toplevel_send_configure:meta_window_wayland_configure:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
*** This bug is a duplicate of bug 1958684 *** https://bugs.launchpad.net/bugs/1958684 ** This bug has been marked a duplicate of private bug 1958684 -- 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/1958818 Title: /usr/bin/gnome- shell:8:meta_wayland_xdg_toplevel_send_configure:meta_window_wayland_configure:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist Status in gnome-shell package in Ubuntu: New 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~21.04.1, the problem page at https://errors.ubuntu.com/problem/bd270ee843b327813e28ccddde4a1357b64e1326 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1958818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958722] Re: improve the sound -> over-amplification row
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Muqtadir (muqtxdir-m) ** Changed in: gnome-control-center (Ubuntu) Status: New => In Progress -- 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/1958722 Title: improve the sound -> over-amplification row Status in gnome-control-center package in Ubuntu: In Progress Bug description: Issue: - The Over-Amplification setting present under Sound-panel in ubuntu-22.04 is a bit outdated because all the other settings-options in the sound-panel make use of round-listboxes in GNOME-41. - I also noticed Over-Amplification's description GtkLabel is not aligned. Proposal: - make use of GtkListbox, HdyPreferencesRow and HdyActionRow for Over-Amplification. - MR for the same: https://gitlab.gnome.org/Community/Ubuntu/gnome-control-center/-/merge_requests/6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1958722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958726] Re: gnome-control-center online-accounts cannot load accounts.google.com
See also bug 1892064 -- 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/1958726 Title: gnome-control-center online-accounts cannot load accounts.google.com Status in gnome-control-center package in Ubuntu: New Bug description: - Fresh install of Ubuntu 21.10, all packages upgraded. - Trying to connect my Google account opens a small window which gets stuck at "Loading accounts.google.com". (See attachment.) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 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: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jan 22 13:16:15 2022 InstallationDate: Installed on 2022-01-22 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color 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/1958726/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958818] [NEW] /usr/bin/gnome-shell:8:meta_wayland_xdg_toplevel_send_configure:meta_window_wayland_configure:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
*** This bug is a duplicate of bug 1958684 *** https://bugs.launchpad.net/bugs/1958684 Public bug reported: 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~21.04.1, the problem page at https://errors.ubuntu.com/problem/bd270ee843b327813e28ccddde4a1357b64e1326 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- 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/1958818 Title: /usr/bin/gnome- shell:8:meta_wayland_xdg_toplevel_send_configure:meta_window_wayland_configure:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist Status in gnome-shell package in Ubuntu: New 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~21.04.1, the problem page at https://errors.ubuntu.com/problem/bd270ee843b327813e28ccddde4a1357b64e1326 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1958818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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.
If you can reinstall the OS then yes that would be the fastest solution. Otherwise please run: dpkg -l > allpackages.txt and attach the resulting text file here. -- 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 1958733] Re: Settings menu will not open. Other things seem messed up.
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 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 1958759] Re: Had some crash on log out after chaging locale, it went away on log out, couldnt post it
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg-server (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1958759 Title: Had some crash on log out after chaging locale, it went away on log out, couldnt post it Status in Ubuntu: Incomplete Bug description: Had some crash on log out after chaging locale, it went away on log out, couldnt post it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-96.109~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-96-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sun Jan 23 06:06:46 2022 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 915GM/GMS/910GML Express Graphics Controller [1028:01c9] Subsystem: Dell Mobile 915GM/GMS/910GML Express Graphics Controller [1028:01c9] InstallationDate: Installed on 2022-01-15 (7 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. ME051 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-96-generic root=UUID=8c2d7681-4766-4186-bb7a-845993d56fb2 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RJ272 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/07/2006:svnDellInc.:pnME051:pvr:rvnDellInc.:rn0RJ272:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: ME051 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1958759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958778] Re: Laptop not waking up from suspend, or waking up with random noise on screen.
The noise problem is already covered by bug 1958412 and bug 1958591. So this bug is now just about failing to wake from suspend. ** Tags added: amdgpu ** Summary changed: - Laptop not waking up from suspend, or waking up with random noise on screen. + [amdgpu] Laptop not waking up from suspend, or waking up with random noise on screen. ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Summary changed: - [amdgpu] Laptop not waking up from suspend, or waking up with random noise on screen. + [amdgpu] Laptop not waking up from suspend ** Tags added: resume suspend-resume -- 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/1958778 Title: [amdgpu] Laptop not waking up from suspend Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Starting today my laptop will not wake up from suspend no matter what I try. After closing my laptop or leaving it alone for a while, the screen goes black like normal, but then no matter how much I mash the keyboard, touch the mouse, press the power button etc. the screen will not turn on. The power light is still on when this happens, so the computer is on. I've had to resort to holding the power button to restart every time. The behavior only changed (and got even weirder) when I plugged my monitor into my laptop. Things worked normally until my laptop went into standby. This time the monitor woke up as normal, and my laptop screen became filled with colorful static. I'm able to use the computer as normal on the monitor, which is how I'm filing this report. I should note that I installed routine updates yesterday through Software Updater, which is likely what triggered these issues. I also had a possibly related bug yesterday (after updating) where my laptop's fan stopped working. I restarted once and the fan still wouldn't turn on. I switched to my Windows partition and the fan started working. Then when I switched back to my Ubuntu partition the fan was working normally. 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: Sun Jan 23 17:11:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3f1a] InstallationDate: Installed on 2021-08-04 (171 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 81X2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=464df196-22f9-4ea4-989d-dda2cb0a5ec5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2020 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EECN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ARE05 dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrEECN31WW:bd12/18/2020:br1.31:efr1.20:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:skuLENOVO_MT_81X2_BU_idea_FM_IdeaPadFlex514ARE05: dmi.product.family: IdeaPad Flex 5 14ARE05 dmi.product.name: 81X2 dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05 dmi.product.version: IdeaPad Flex 5 14ARE05 dmi.sys.vendor: LENOVO 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.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/1958778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1946258] Re: Panels unclickable after screen area capture
*** This bug is a duplicate of bug 1910235 *** https://bugs.launchpad.net/bugs/1910235 ** This bug has been marked a duplicate of bug 1910235 The mouse stops working after trying to take an area screenshot in some apps on Xorg -- 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/1946258 Title: Panels unclickable after screen area capture Status in Gnome Screenshot: Unknown Status in gnome-screenshot package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: When I try to capture screen area using gnome tool, mouse pointer changes to a cross and it is impossible to click on left or top panels. Closing gnome screen capture toll does not help. I am only able to do Alt-Tab, Ctrl+Alt+T and Ctrl+Alt+Del. Logoff and Logon help to fix the problem. It appears more often when Remmina is active. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 6 22:50:35 2021 InstallationDate: Installed on 2020-07-10 (453 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all 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/gnome-screenshot/+bug/1946258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910235] Re: The mouse stops working after trying to take an area screenshot in some apps on Xorg
It looks like we forgot to fix focal so there are still bug reports there. ** Tags added: rls-ff-incoming -- 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/1910235 Title: The mouse stops working after trying to take an area screenshot in some apps on Xorg Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Groovy: Fix Released Bug description: [ Impact ] Mouse stops working after taking an area screenshot [ Test case ] 1. Open Chromium browser. 2. Go to the page with the form in which there is a standard browser drop-down menu (form select) 3. Open it 4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen 5. Try to switch between applications using the panel and check the operation of the mousein other applications besides browser (in my case Slack) [ Regression potential ] Grab events don't happen or pointer isn't ungrabbed when required. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-26 (71 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1910235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958635] Re: Dock + window menus unresponsive after attempting to do an area screenshot
*** This bug is a duplicate of bug 1910235 *** https://bugs.launchpad.net/bugs/1910235 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1910235, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1910235 The mouse stops working after trying to take an area screenshot in some apps on Xorg -- 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/1958635 Title: Dock + window menus unresponsive after attempting to do an area screenshot Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Reproduced this issue several times, but it doesn't happen all the time. After trying to take a screenshot of an area, the screenshotting may fail and the ubuntu dock and all window menus become unresponsive. Mouseover on the dock will change the cursor to the plus-sign used when selecting the area to screenshot, but nothing happens if you try to click or click/drag. Shift+Print Screen will allow you to try to click/drag and the pointer stops becoming a plus-sign after this, but the dock and menus are still unresponsive. Alt+F2 & r seems to resolve the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83 Uname: Linux 5.10.0-1057-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 10:57:48 2022 InstallationDate: Installed on 2021-04-25 (270 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all 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/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1958635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] [NEW] If apt installs snap package, then show size of it
Public bug reported:
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
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Affects: snap (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy snap
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Also affects: snap (Ubuntu)
Importance: Undecided
Status: New
--
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:
New
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
[Desktop-packages] [Bug 1958810] [NEW] Apt installing snap package if got some error why didnt finish, thinks apt is installed, but snap cant be removed
Public bug reported:
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
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Affects: snap (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy snap
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Also affects: snap (Ubuntu)
Importance: Undecided
Status: New
--
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:
New
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
4Done
[Desktop-packages] [Bug 1958812] [NEW] If apt installs snap package, then warn, because maybe i dont want snap package.
Public bug reported:
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
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Affects: snap (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy snap
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Also affects: snap (Ubuntu)
Importance: Undecided
Status: New
--
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:
New
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:
[Desktop-packages] [Bug 1926799] Re: Cursor is not rendered in the correct location when at maximum desktop zoom
** Tags removed: hirsute ** Tags added: impish ** Changed in: gnome-shell (Ubuntu) Status: Won't Fix => New -- 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/1926799 Title: Cursor is not rendered in the correct location when at maximum desktop zoom Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Affected version LSB Version: core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Gnome Version: 3.38.4 Occurs in: Xorg and Wayland Bug summary 1. zoom focus shifts - lets assume a window in the center of the screen and i am at 3x zoom and i try to point my mouse at something and try to click that. 90% of the time zoom focus shifts away from the mouse location to mostly top left corner of the screen. 2. mouse pointing away from the object - Similarly when i reach above some zoom limit sets say 4x and now lets say i am in a browser trying to click a link i point at the link cursor changes to hand and when i try to click i couldnt. So i try to zoom out and i fid that the pointer was not exactly placed on the link. To sum up when zoomed in it seems like i am pointing at a link while the cursor is actually placed away from the link 3. Compressing text - after reaching certain high zoom level as said 4x or 5x the content on the screen becomes a bit compressed on the sides texts and images and everything on screen becomes elongated Steps to reproduce 1. Turn on zoom from settings -> Accessibility 2. Zoom in above 3.x 3. Try clicking on some object inside a window 4. Choose Follow mouse cursor or on screen part droopdown choose full screen. 5. My current settings are Screen part: Full Screen, Magnifier cursor pushes content arround. However these issues persist with all the other options under magnifier position. Such as Follow mouse cursor or magnifier cursor pushes content arround or any such option provided. Screenshot_from_2021-05-03_14-37-09 What happened 1. Zoom focus shifts away from the cursor mostly towards top left of the window or the desktop. 2.While zoomed in cursor seems to be placed above a link or an object but is actually placed awway either to the left or right of the object. Original position of the cursor reveals when zoomed out. 3.Content on screen seems to be compressed from the sides as text and other objects appear elongated. I have also posted the same issue on the GNOME Community: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4228 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-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/gnome-shell/+bug/1926799/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930371] Re: top bar displayed on top of a fullscreen window that gets moved from one monitor to another
Thanks for the bug report. First, please try removing these extensions: 'fullscreen-hot-cor...@sorrow.about.alice.pm.me', 'transparentosd@ipaq3870' then log in again. ** Tags removed: hirsute ** Tags added: impish ** Changed in: gnome-shell (Ubuntu) Status: Won't Fix => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1930371 Title: top bar displayed on top of a fullscreen window that gets moved from one monitor to another Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have two monitors: the laptop's internal one (primary), and an external LCD positioned above the it. I have configured mpv to be the default video player in Nautilus. I have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'. Steps to reproduce: - click on a video file in Nautilus - mpv is launches in fullscreen mode on the external monitor - drag the mpv window with the mouse to the internal monitor Expected behavior: - mpv is fullscreen on the internal monitor Actual behavior - mpv is fullscreen, but the gnome-shell top bar is displayed on top of the video Workaround: hit twice. Alternative workaround: alt-tab so a different window is on top of mpv then alt-tab back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 10:02:15 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (719 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1930371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933890] Re: No wacom tablet or stylus discovered, Fujitsu T935
** Changed in: gnome-control-center (Ubuntu) Status: Won't Fix => New ** Changed in: mutter (Ubuntu) Status: Won't Fix => New ** Tags removed: hirsute ** Tags added: impish -- 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/1933890 Title: No wacom tablet or stylus discovered, Fujitsu T935 Status in gnome-control-center package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I installed Ubuntu 21.04 on my Fujitsu T935, which has a Wacom stylus and screen. The command line seems to find it, and it works fine, but I cannot calibrate it without the gnome-control-center. $ xsetwacom --list devices Wacom MultiTouch Sensor Finger touch id: 10 type: TOUCH Wacom MultiTouch Sensor Pen stylusid: 11 type: STYLUS Wacom MultiTouch Sensor Pen eraserid: 15 type: ERASER Any ideas what to do? Thanks, Rob ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 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: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 17:45:08 2021 InstallationDate: Installed on 2021-05-25 (34 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color 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/1933890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
The 5.5 beta driver: https://www.synaptics.com/products/displaylink- graphics/downloads/ubuntu has also solved a serious issue in Wayland sessions for me... https://gitlab.gnome.org/GNOME/mutter/-/issues/2005 ** Bug watch added: 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 1880995] Re: HP ZBook x2 touchpad is detected as a mouse when detached
Found this project, seems working. https://github.com/himekifee/hid-hp-zbook.git -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1880995 Title: HP ZBook x2 touchpad is detected as a mouse when detached Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: * Kubuntu version 20.04 When the keyboard is attached, running `xinput` produces: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ... ⎜ ↳ NXP Semiconductors LPC I2C HID Consumer Control id=11 [slave pointer (2)] ⎜ ↳ NXP Semiconductors LPC I2C HID Mouse id=31 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ... ↳ NXP Semiconductors LPC I2C HID System Controlid=10 [slave keyboard (3)] ↳ NXP Semiconductors LPC I2C HID Consumer Control id=12 [slave keyboard (3)] ↳ NXP Semiconductors LPC I2C HIDid=13 [slave keyboard (3)] ## Props Device 'NXP Semiconductors LPC I2C HID Consumer Control': Device Enabled (155): 1 Coordinate Transformation Matrix (157): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Natural Scrolling Enabled (291): 0 libinput Natural Scrolling Enabled Default (292): 0 libinput Send Events Modes Available (276): 1, 0 libinput Send Events Mode Enabled (277):0, 0 libinput Send Events Mode Enabled Default (278):0, 0 Device Node (279): "/dev/input/event11" Device Product ID (280):8137, 136 libinput Drag Lock Buttons (293): libinput Horizontal Scroll Enabled (294): 1 Device 'NXP Semiconductors LPC I2C HID Mouse': Device Enabled (155): 1 Coordinate Transformation Matrix (157): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Natural Scrolling Enabled (291): 0 libinput Natural Scrolling Enabled Default (292): 0 libinput Scroll Methods Available (295):0, 0, 1 libinput Scroll Method Enabled (296): 0, 0, 0 libinput Scroll Method Enabled Default (297): 0, 0, 0 libinput Button Scrolling Button (298): 2 libinput Button Scrolling Button Default (299): 2 libinput Middle Emulation Enabled (300):0 libinput Middle Emulation Enabled Default (301):0 libinput Accel Speed (302): 0.20 libinput Accel Speed Default (303): 0.00 libinput Accel Profiles Available (304):1, 1 libinput Accel Profile Enabled (305): 1, 0 libinput Accel Profile Enabled Default (306): 1, 0 libinput Left Handed Enabled (307): 0 libinput Left Handed Enabled Default (308): 0 libinput Send Events Modes Available (276): 1, 0 libinput Send Events Mode Enabled (277):0, 0 libinput Send Events Mode Enabled Default (278):0, 0 Device Node (279): "/dev/input/event14" Device Product ID (280):8137, 136 libinput Drag Lock Buttons (293): libinput Horizontal Scroll Enabled (294): 1 When the keyboard is detached, it changes: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ... ⎜ ↳ HP ZBook x2 Bluetooth Keyboard Consumer Control id=10 [slave pointer (2)] ⎜ ↳ HP ZBook x2 Bluetooth Keyboard Mouse id=31 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ... ↳ HP ZBook x2 Bluetooth Keyboard Consumer Control id=11 [slave keyboard (3)] ↳ HP ZBook x2 Bluetooth Keyboardid=12 [slave keyboard (3)] ↳ HP ZBook x2 Bluetooth Keyboard System Control id=13 [slave keyboard (3)] ## Props Device 'HP ZBook x2 Bluetooth Keyboard Consumer Control': Device Enabled (155): 1 Coordinate Transformation Matrix (157): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Natural Scrolling Enabled (291): 0 libinput Natural Scrolling Enabled Default (292): 0 libinput Send Events Modes Available (276): 1, 0 libinput Send Events Mode Enabled (277):0, 0 libinput
[Desktop-packages] [Bug 1956005] Re: Firefox Snap won't open links to WhatsApp API
I looked at firefox snap and didn't see a --classic confinement option to install.. But, I am also new to snap so I might just be ignorant of how to apply this setting -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1956005 Title: Firefox Snap won't open links to WhatsApp API Status in firefox package in Ubuntu: Confirmed Bug description: The .deb version of Firefox handles links to WhatsApp API (https://api.whatsapp.com/send/?phone=) without any problem: these links open the WhatsApp web client. Snap version of Firefox doesn't know how to handle these links. It opens the pop up "Choose an application to open whatsapp lnks" that only shows the option System Handler (which fails opening them if selected). Choosing Firefox is not possible as /bin and similar folders are out of range for the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956005/+subscriptions -- Mailing list: https://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 1949618] Re: system locks up when selection one of top 2 items in dock
This behavior disappeared in 21.10 Robert E. Novak sailnf...@gmail.com Cell: +1 (209) 620-3130 FAX: +1 (866) 889-1639 Skype: sailnfool.ren https://www.linkedin.com/in/sailnfool On Sat, Jan 22, 2022 at 8:25 PM Launchpad Bug Tracker <1949...@bugs.launchpad.net> wrote: > > [Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there > has been no activity for 60 days.] > > ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) >Status: Incomplete => Expired > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1949618 > > Title: > system locks up when selection one of top 2 items in dock > > Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: > Expired > > Bug description: > This bug occurs when using the cursor to select one of the top two icons on > the dock area of the Ubuntu desktop. When the system is under load and I > click the cursor on one of the two icons, the cursor freezes and the system > is unresponsive, requiring a power down reboot to recover. > Description: Ubuntu 21.04 > Release: 21.04 > > ProblemType: Bug > DistroRelease: Ubuntu 21.04 > Package: dash > 0.5.11+git20200708+dd9ef66+really0.5.11+git20200708+dd9ef66-5ubuntu1 > ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 > Uname: Linux 5.11.0-38-generic x86_64 > ApportVersion: 2.20.11-0ubuntu65.4 > Architecture: amd64 > CasperMD5CheckResult: unknown > CurrentDesktop: ubuntu:GNOME > Date: Wed Nov 3 09:56:31 2021 > InstallationDate: Installed on 2021-03-06 (241 days ago) > InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: dash > UpgradeStatus: Upgraded to hirsute on 2021-06-10 (145 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1949618/+subscriptions > -- 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/1949618 Title: system locks up when selection one of top 2 items in dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: This bug occurs when using the cursor to select one of the top two icons on the dock area of the Ubuntu desktop. When the system is under load and I click the cursor on one of the two icons, the cursor freezes and the system is unresponsive, requiring a power down reboot to recover. Description: Ubuntu 21.04 Release: 21.04 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: dash 0.5.11+git20200708+dd9ef66+really0.5.11+git20200708+dd9ef66-5ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 3 09:56:31 2021 InstallationDate: Installed on 2021-03-06 (241 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dash UpgradeStatus: Upgraded to hirsute on 2021-06-10 (145 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1949618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956005] Re: Firefox Snap won't open links to WhatsApp API
I am having this issue for zoom and slack or anything else that needs an external app. I have been having this issue for at least 3 months.. Also, I noticed that my firefox snap is not classic version so I am not sure if that makes a difference. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1956005 Title: Firefox Snap won't open links to WhatsApp API Status in firefox package in Ubuntu: Confirmed Bug description: The .deb version of Firefox handles links to WhatsApp API (https://api.whatsapp.com/send/?phone=) without any problem: these links open the WhatsApp web client. Snap version of Firefox doesn't know how to handle these links. It opens the pop up "Choose an application to open whatsapp lnks" that only shows the option System Handler (which fails opening them if selected). Choosing Firefox is not possible as /bin and similar folders are out of range for the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956005] Re: Firefox Snap won't open links to WhatsApp API
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1956005 Title: Firefox Snap won't open links to WhatsApp API Status in firefox package in Ubuntu: Confirmed Bug description: The .deb version of Firefox handles links to WhatsApp API (https://api.whatsapp.com/send/?phone=) without any problem: these links open the WhatsApp web client. Snap version of Firefox doesn't know how to handle these links. It opens the pop up "Choose an application to open whatsapp lnks" that only shows the option System Handler (which fails opening them if selected). Choosing Firefox is not possible as /bin and similar folders are out of range for the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958778] Re: Laptop not waking up from suspend, or waking up with random noise on screen.
Update: I suspended my computer again. This time when I opened it the monitor worked, the laptop screen was black, and the mouse had completely disappeared. -- 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/1958778 Title: Laptop not waking up from suspend, or waking up with random noise on screen. Status in xorg package in Ubuntu: New Bug description: Starting today my laptop will not wake up from suspend no matter what I try. After closing my laptop or leaving it alone for a while, the screen goes black like normal, but then no matter how much I mash the keyboard, touch the mouse, press the power button etc. the screen will not turn on. The power light is still on when this happens, so the computer is on. I've had to resort to holding the power button to restart every time. The behavior only changed (and got even weirder) when I plugged my monitor into my laptop. Things worked normally until my laptop went into standby. This time the monitor woke up as normal, and my laptop screen became filled with colorful static. I'm able to use the computer as normal on the monitor, which is how I'm filing this report. I should note that I installed routine updates yesterday through Software Updater, which is likely what triggered these issues. I also had a possibly related bug yesterday (after updating) where my laptop's fan stopped working. I restarted once and the fan still wouldn't turn on. I switched to my Windows partition and the fan started working. Then when I switched back to my Ubuntu partition the fan was working normally. 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: Sun Jan 23 17:11:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3f1a] InstallationDate: Installed on 2021-08-04 (171 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 81X2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=464df196-22f9-4ea4-989d-dda2cb0a5ec5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2020 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EECN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ARE05 dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrEECN31WW:bd12/18/2020:br1.31:efr1.20:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:skuLENOVO_MT_81X2_BU_idea_FM_IdeaPadFlex514ARE05: dmi.product.family: IdeaPad Flex 5 14ARE05 dmi.product.name: 81X2 dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05 dmi.product.version: IdeaPad Flex 5 14ARE05 dmi.sys.vendor: LENOVO 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.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/xorg/+bug/1958778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958778] [NEW] Laptop not waking up from suspend, or waking up with random noise on screen.
Public bug reported: Starting today my laptop will not wake up from suspend no matter what I try. After closing my laptop or leaving it alone for a while, the screen goes black like normal, but then no matter how much I mash the keyboard, touch the mouse, press the power button etc. the screen will not turn on. The power light is still on when this happens, so the computer is on. I've had to resort to holding the power button to restart every time. The behavior only changed (and got even weirder) when I plugged my monitor into my laptop. Things worked normally until my laptop went into standby. This time the monitor woke up as normal, and my laptop screen became filled with colorful static. I'm able to use the computer as normal on the monitor, which is how I'm filing this report. I should note that I installed routine updates yesterday through Software Updater, which is likely what triggered these issues. I also had a possibly related bug yesterday (after updating) where my laptop's fan stopped working. I restarted once and the fan still wouldn't turn on. I switched to my Windows partition and the fan started working. Then when I switched back to my Ubuntu partition the fan was working normally. 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: Sun Jan 23 17:11:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3f1a] InstallationDate: Installed on 2021-08-04 (171 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 81X2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=464df196-22f9-4ea4-989d-dda2cb0a5ec5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2020 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EECN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ARE05 dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrEECN31WW:bd12/18/2020:br1.31:efr1.20:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:skuLENOVO_MT_81X2_BU_idea_FM_IdeaPadFlex514ARE05: dmi.product.family: IdeaPad Flex 5 14ARE05 dmi.product.name: 81X2 dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05 dmi.product.version: IdeaPad Flex 5 14ARE05 dmi.sys.vendor: LENOVO 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.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/1958778 Title: Laptop not waking up from suspend, or waking up with random noise on screen. Status in xorg package in Ubuntu: New Bug description: Starting today my laptop will not wake up from suspend no matter what I try. After closing my laptop or leaving it alone for a while, the screen goes black like normal, but then no matter how much I mash the keyboard, touch the mouse, press the power button etc. the screen will not turn on. The power light is still on when this happens, so the computer is on. I've had to resort to holding the power button to restart every time. The behavior only changed (and got even weirder) when I plugged my monitor into my laptop. Things worked normally until my laptop went into standby. This time the monitor woke up as normal, and my laptop screen became filled with colorful static. I'm able to use the computer as normal on the monitor, which is how I'm filing this report. I should note that I installed routine updates yesterday through Software Updater, which is
[Desktop-packages] [Bug 1958759] Re: Had some crash on log out after chaging locale, it went away on log out, couldnt post it
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- 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/1958759 Title: Had some crash on log out after chaging locale, it went away on log out, couldnt post it Status in xorg-server package in Ubuntu: New Bug description: Had some crash on log out after chaging locale, it went away on log out, couldnt post it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-96.109~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-96-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sun Jan 23 06:06:46 2022 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 915GM/GMS/910GML Express Graphics Controller [1028:01c9] Subsystem: Dell Mobile 915GM/GMS/910GML Express Graphics Controller [1028:01c9] InstallationDate: Installed on 2022-01-15 (7 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. ME051 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-96-generic root=UUID=8c2d7681-4766-4186-bb7a-845993d56fb2 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RJ272 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/07/2006:svnDellInc.:pnME051:pvr:rvnDellInc.:rn0RJ272:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: ME051 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1958759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958721] Re: appstreamcli refresh-cache reports MDB_MAP_FULL
using appstreamcli 0.15.2 build from git master (g...@github.com:ximion/appstream.git) does not result in any error: david@bee:~/src/appstream/build$ ./tools/appstreamcli --version AppStream version: 0.15.2 david@bee:~/src/appstream/build$ sudo ./tools/appstreamcli refresh --force ** (appstreamcli:311703): WARNING **: 09:35:44.249: Found icon of unknown type 'unknown' in 'system/flatpak/flatpak/cc.nift.nsm/*', skipping it. ** (appstreamcli:311703): WARNING **: 09:35:44.250: Found icon of unknown type 'unknown' in 'system/flatpak/flatpak/cc.nift.nsm/*', skipping it. ? Metadata cache was updated successfully. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1958721 Title: appstreamcli refresh-cache reports MDB_MAP_FULL Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Impish: New Status in appstream source package in Jammy: Fix Released Bug description: On Ubuntu 21.10 aarch64 AppStream version: 0.14.5 I get the following error: % sudo appstreamcli refresh-cache --force Unable to add data: MDB_MAP_FULL: Environment mapsize limit reached Using: sudo ltrace -f -l liblmdb.so.0 appstreamcli refresh-cache I see that the DB is initialized with a 256MB size [pid 244512] libappstream.so.4->mdb_env_set_mapsize(0xd38f46e0, 0x1000, 0xd38f46e0, 0) = 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1958721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958721] Re: appstreamcli refresh-cache reports MDB_MAP_FULL
> You have a cache bigger than 256MB?? This issue is already fixed with appstream 0.15.0, but I still would like to know why your cache is so huge. What's you system locale? I would like to understand it too. System locale: david@bee:~$ locale -a C C.UTF-8 POSIX en_US.utf8 david@bee:~$ locale LANG=C.UTF-8 LANGUAGE=C LC_CTYPE="C" LC_NUMERIC="C" LC_TIME="C" LC_COLLATE="C" LC_MONETARY="C" LC_MESSAGES="C" LC_PAPER="C" LC_NAME="C" LC_ADDRESS="C" LC_TELEPHONE="C" LC_MEASUREMENT="C" LC_IDENTIFICATION="C" LC_ALL=C If you could provide any tips on how to determine how or why my cache would be so large, it might help identify the source of this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1958721 Title: appstreamcli refresh-cache reports MDB_MAP_FULL Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Impish: New Status in appstream source package in Jammy: Fix Released Bug description: On Ubuntu 21.10 aarch64 AppStream version: 0.14.5 I get the following error: % sudo appstreamcli refresh-cache --force Unable to add data: MDB_MAP_FULL: Environment mapsize limit reached Using: sudo ltrace -f -l liblmdb.so.0 appstreamcli refresh-cache I see that the DB is initialized with a 256MB size [pid 244512] libappstream.so.4->mdb_env_set_mapsize(0xd38f46e0, 0x1000, 0xd38f46e0, 0) = 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1958721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
