Unhandled promise rejection in _loadFile@resource:///org/gnome/shell/ui/background.js

Bug #1965820 reported by David
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GNOME Shell
Fix Released
Unknown
gnome-shell (Ubuntu)
Fix Released
Low
Jeremy Bícha
Jammy
Fix Released
Low
Jeremy Bícha
Kinetic
Fix Released
Low
Jeremy Bícha

Bug Description

Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:#012 _loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012 _load@resource:///org/gnome/shell/ui/background.js:533:14#012 _init@resource:///org/gnome/shell/ui/background.js:282:14#012 Background@resource:///org/gnome/shell/ui/background.js:237:4#012 getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012 _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34#012 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14
Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: message repeated 8 times: [ Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:#012 _loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012 _load@resource:///org/gnome/shell/ui/background.js:533:14#012 _init@resource:///org/gnome/shell/ui/background.js:282:14#012 Background@resource:///org/gnome/shell/ui/background.js:237:4#012 getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012 _updateBackgrounds@resource:///o]

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.06.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 21 20:57:30 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GA104 [GeForce RTX 3070 Lite Hash Rate] [10de:2488] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GA104 [GeForce RTX 3070 Lite Hash Rate] [1458:404c]
InstallationDate: Installed on 2022-03-16 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
MachineType: Gigabyte Technology Co., Ltd. B550 AORUS MASTER
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=f0d454f1-0a2b-48a3-b6ff-6ba06e951a1b ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F13h
dmi.board.asset.tag: Default string
dmi.board.name: B550 AORUS MASTER
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF13h:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSMASTER:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B550 MB
dmi.product.name: B550 AORUS MASTER
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.3.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

Revision history for this message
David (roastedtoast) wrote :
affects: xorg (Ubuntu) → gnome-shell (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I think I've seen that unhandled promise in _loadFile in other peoples' logs too, maybe even my own. And it sounds related to a black screen, but nobody else is reporting a black screen!?

summary: - Screen goes black when opening Settings, following error appears
+ Screen goes black when opening Settings [Unhandled promise rejection in
+ _loadFile@resource:///org/gnome/shell/ui/background.js:503:20]
Revision history for this message
David (roastedtoast) wrote : Re: Screen goes black when opening Settings [Unhandled promise rejection in _loadFile@resource:///org/gnome/shell/ui/background.js:503:20]

The black screen occurs regularly (but not systematically) when I click on "Settings" or sometimes even when I try to change a setting, like Bluetooth or WiFi.
And this error is one of those that appear in the logs.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The log messages seem common so I've made this bug just about them (fixed in 42.1 in theory).

If you still have black screen issues after this reaches 'Fix Released' then please open a new bug.

summary: Screen goes black when opening Settings [Unhandled promise rejection in
- _loadFile@resource:///org/gnome/shell/ui/background.js:503:20]
+ _loadFile@resource:///org/gnome/shell/ui/background.js]
Changed in gnome-shell (Ubuntu):
status: Confirmed → Fix Committed
summary: - Screen goes black when opening Settings [Unhandled promise rejection in
- _loadFile@resource:///org/gnome/shell/ui/background.js]
+ Unhandled promise rejection in
+ _loadFile@resource:///org/gnome/shell/ui/background.js
tags: added: fixed-in-42.1 fixed-upstream
tags: added: logspam
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

gnome-shell (42.1-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #1973373, LP: #1968911)
  * Drop patches applied in new release

 -- Jeremy Bicha <email address hidden> Fri, 13 May 2022 16:32:49 -0400

Changed in gnome-shell (Ubuntu):
status: Fix Committed → Fix Released
importance: Undecided → Low
assignee: nobody → Jeremy Bicha (jbicha)
Changed in gnome-shell (Ubuntu Jammy):
status: New → In Progress
importance: Undecided → Low
assignee: nobody → Jeremy Bicha (jbicha)
Changed in gnome-shell:
status: Unknown → Fix Released
Changed in gnome-shell (Ubuntu Jammy):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.