gnome-shell freeze
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
When using the app drawer the ui eventually freezes and an hard reset is required
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSign
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CasperMD5CheckR
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 13:44:24 2020
DistUpgraded: 2020-04-24 11:41:00,761 ERROR got error from PostInstallScript ./xorg_
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingI
GpuHangFrequency: Very infrequently
GraphicsCard:
Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:118c]
InstallationDate: Installed on 2019-11-09 (166 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Acer Swift SF314-52
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
dmi.bios.date: 08/23/2018
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.09
dmi.board.
dmi.board.name: Suntory_KL
dmi.board.vendor: KBL
dmi.board.version: V1.09
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnInsydeCo
dmi.product.family: Swift 3
dmi.product.name: Swift SF314-52
dmi.product.sku: 0000000000000000
dmi.product.
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.
version.
version.
version.
version.
version.
version.
affects: | ubuntu → xorg (Ubuntu) |
affects: | xorg (Ubuntu) → gnome-shell (Ubuntu) |
summary: |
- Xorg freeze + gnome-shell freeze |
Thank you for your bug report. What do you call 'the app drawer'? could you make a small video showing the issue?
Could you also add your 'journalctl -b 0' log after getting the bug and indicate at what time you hit the issue (to match the proper log section)