Question

3

dbus calls to gnome shell don't work under Ubuntu 22.04

rated 0 times [ 3] [ 0] / answers: 1 / hits: 1304 / 1 Year ago, sun, january 15, 2023, 11:08:39

Trivial example: Under Ubuntu 20.04, the following command:

gdbus call -e -d org.gnome.Shell -o /org/gnome/Shell -m org.gnome.Shell.Eval true

produces this output:

(true, 'true')

but under 22.04 the same command produces this output:

(false,'')

The same output is produced for any other "Eval" statement I've tried under 22.04.

What's going wrong? The 20.04 and 22.04 systems are both newly-installed, vanilla installations.

Update: This seems to be one of the problems that gcdev (https://askubuntu.com/users/1216972/gcdev) was trying to report earlier:

How to get the current active window in Ubuntu 22.04?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

antoccasiona

Add To Favorites

Follow

Total Points: 430

Total Questions: 127

Total Answers: 131

Location: Netherlands

Member since Sat, Jun 26, 2021

3 Years ago

antoccasiona questions

1 Chrome not working after upgrading to Ubuntu 22.04

Sat, Oct 23, 21, 22:34, 3 Years ago

1 org.bluez.Error.AuthenticationTimeout; org.bluez.Error.Failed br-connection-unknown

Tue, Mar 8, 22, 09:39, 2 Years ago

1 NTFS hard drive is read only

Sat, Sep 24, 22, 09:39, 2 Years ago

1 HP laptop: Ubuntu install and live disk failed: pcie trouble: fixed

Sat, Aug 27, 22, 18:13, 2 Years ago

1 How to batch rename sequentially prefixed numbers to new sequential prefixes via terminal?

Sat, Feb 25, 23, 11:04, 1 Year ago

View All

answered 1 Year ago scusaper · Accepted Answer

Like everywhere else, stricter security is also being implemented in Gnome Shell.

The org.gnome.Shell interface provides a private API to other core
components to implement desktop functionalities like Settings or
global keybindings. It is not meant as a public API, so limit it
to a set of expected callers.

(https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/a628bbc4)

This is why many such commands no longer work. One can enter global.context.unsafe_mode = true in the Looking Glass (Alt+F2, lg Enter) to make them work for the current session. There is an extension, Unsafe mode menu, that allows to toggle between safe and unsafe mode (with thanks to Bryan Wright). It should also be possible to start Gnome Shell with an --unsafe option.