From: Maxime Devos <maximedevos@telenet.be>
To: Roman Riabenko <roman@riabenko.com>,
Tobias Geerinckx-Rice <me@tobias.gr>,
55625@debbugs.gnu.org
Subject: bug#55625: GNOME: totem controls not accessible
Date: Sat, 28 May 2022 21:28:04 +0200 [thread overview]
Message-ID: <be93e39031c9ed8b613dbe54d4974592f8e4b0f1.camel@telenet.be> (raw)
In-Reply-To: <a3b6be0550f48da545bca86e0104671830af22c3.camel@riabenko.com>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
Roman Riabenko schreef op za 28-05-2022 om 22:15 [+0300]:
> > (totem:147294): Totem-WARNING **: 16:32:42.898: Failed to acquire
> > screensaver proxy: Failed to execute child process ?dbus-launch?
> (No
> > such file or directory)
> >
> > ^^^ file names needing a substitute*
>
> I do not see this when I start totem from terminal. Maybe that is
> because I am using GNOME. I mean that I have the system configured
> with (service gnome-desktop-service-type) and totem is installed as a
> system application.
Probably the reason is that I am doing things in a ‘pure’ environment
here:
$ guix shell --pure totem -- totem a-file.mp4
In a ‘pure’ environment, various environment variables are unset, which
avoids interference with other installed applications, which can be
usefel for debugging. If you try "guix shell --pure totem -- totem",
you'll probably at least see the logo warning.
I don't expect it to be related to the issue you originally reported
though.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-05-28 19:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 6:03 bug#55625: GNOME: totem controls not accessible Roman Riabenko
2022-05-28 15:11 ` Maxime Devos
2022-05-28 15:35 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-05-28 16:29 ` Maxime Devos
2022-05-28 16:34 ` Maxime Devos
2022-05-28 19:15 ` Roman Riabenko
2022-05-28 19:28 ` Maxime Devos [this message]
2022-05-28 19:31 ` Maxime Devos
2022-05-30 18:45 ` Roman Riabenko
2022-05-28 15:20 ` Maxime Devos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=be93e39031c9ed8b613dbe54d4974592f8e4b0f1.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55625@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=roman@riabenko.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.