Shell stops responding to input after desktop-icons rubber band
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell-extension-desktop-icons |
New
|
Unknown
|
|||
gnome-shell-extension-desktop-icons (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This bug happened when I clicked and held the left mouse button on the desktop and moved it to make a rectangular selection window. Next, I moved the window to highlight 4 desktop shortcuts on my desktop (Middle-earth Shadow of Mordor.desktop, steam.desktop, Trash, and the icelancet or Home folder). Next, while still holding the left mouse button down, I pressed and released the right mouse button. Now a window pops up with more options, however, the window is not removable using a normal method like clicking somewhere else on the desktop or even choosing an option in the window which does nothing. Also, it introduces more bugs like: 1. clicking the icelancet/Home shortcut on the desktop does not open the Home folder, or 2. while clicking the Home folder shortcut on the sidebar does open the Home folder, this window is not moveable by the usual method of pressing down the left mouse button on the title bar of the window and moving the mouse. As such, when this bug occurs, a hard reboot is necessary to restore the stability of the system. I have reproduced the bug after a reboot and doing the same procedure - the same thing happens. This is on the latest version of Ubuntu (Release 20.04) with all the latest upstream updates installed.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSign
Uname: Linux 5.11.0-43-generic x86_64
NonfreeKernelMo
.proc.driver.
.proc.driver.
.proc.driver.
.proc.driver.
.proc.driver.
.proc.driver.
.proc.driver.
NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.94 Mon Dec 6 22:42:02 UTC 2021
GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1
ApportVersion: 2.20.11-
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckR
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 20 00:46:44 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingI
GraphicsCard:
NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:862a]
InstallationDate: Installed on 2021-11-23 (27 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: Micro-Star International Co., Ltd. MS-7C39
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_CA.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/05/2019
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.10
dmi.board.
dmi.board.name: B365M PRO-VDH(MS-7C39)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: Default string
dmi.product.name: MS-7C39
dmi.product.sku: Default string
dmi.product.
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.
version.
version.
version.
version.
version.
version.
version.
Changed in gnome-shell-extension-desktop-icons: | |
status: | Unknown → New |
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.