To withdraw my mistake, in order to install dbus x11, as an user:
1. sudo dnf install apt
2. add the Debian Buster package repositories to /etc/apt folder via root
3. After you are doing so, sudo apt update for the packages
4. sudo apt install [package]
Apr 27, 2023 08:34:53 Qubes :
> When i
Additionally, the fc37 minimal does not have GUI terminal because of its nature
of execution from formal installation of minimal setup. As a result, fc37
minimal only provides CLI based programs.
Apr 27, 2023 08:46:45 Howard Chen :
> Correct:
>
> After you went to the terminal, for Debian:
Correct:
After you went to the terminal, for Debian: execute either sudo or root:
1. dnf update
2. dnf install dbus-x11
!! Notes: must be executed in xterm, not gnome terminal. !!
Apr 27, 2023 08:41:32 Qubes :
>
>> Original Message
>> From: Howard Chen
>> Sent: Thursday,
Original Message
From: Howard Chen
Sent: Thursday, April 27, 2023 at 17:39
To: Qubes
Cc: qubes-users@googlegroups.com
Subject: [qubes-users] dbus-x11 missing from Fedora-37
Just execute 'gnome-terminal' or 'terminal' without using sudo or root.
You clearly have not read
Just execute 'gnome-terminal' or 'terminal' without using sudo or root.
Apr 27, 2023 08:34:53 Qubes :
> When i attempted to launch a root gnome-terminal on the default Fedora-37
> template i received a "dbus-launch" error.
>
> "
> [user@fedora-37-clone-1 ~]$ sudo gnome-terminal
> #
When i attempted to launch a root gnome-terminal on the default
Fedora-37 template i received a "dbus-launch" error.
"
[user@fedora-37-clone-1 ~]$ sudo gnome-terminal
# gdk_atom_intern: assertion 'atom_name != NULL' failed
# gdk_atom_intern: assertion 'atom_name != NULL' failed
# Error
Leslie Smith wrote:
> As soon as you add evince using the Add button and you
> click on Apply you should see the KSysoca error logged on your terminal
> window.
Yes. I see
10:24:04.570-warning kf.service.services unknown@0 # KServiceFactory:
unexpected object entry in KSycoca database
Qubes wrote:
I am wondering if a Qubes member can have a look at this. I have a
problem with Krusader not working properly on a Fedora appVM. In short,
if I open Krusader from cli and then I open a file in Krusader the file
does not open, instead a dialog window is given in which I must choose
