When an application like remmina, telegram, keepassxc, ecc. is start,
it put an icon on tray on all other DE like Cinnamon, Mate, ecc....
In Gnome, where is, and how to access, to this tray icons out of the
box, without add an extension?
(inviato dal mio Linux Fedora 30 Workstation)
After 2 successful upgrades from F29 to F30 and 2 successful full
installations, I decided to upgrade my main machine (that runs fine
since past november, installed in F28 then upgraded to F29).
No luck: unable to login (graphical, textual, ssh) except root.
The journal shows:
May 20 12:31:41 ... kernel: Linux version 5.0.16-300.fc30.x86_64 (mockbuild(a)bkernel03.phx2.fedoraproject.org) (gcc version 9.1.1 20190503 (Red Hat 9.1.1-1) (GCC)) #1 SMP Tue May 14 19:33:09 UTC 2019
May 20 12:37:44 ... systemd-logind: New session 3 of user fm.
May 20 12:37:44 ... systemd: Starting User Manager for UID 1005...
May 20 12:37:48 ... systemd: Started Getty on tty2.
May 20 12:38:16 ... systemd: pam_unix(systemd-user:session): session opened for user fm by (uid=0)
May 20 12:38:16 ... systemd: PAM failed: Cannot allocate memory
May 20 12:38:16 ... systemd: pam_unix(systemd-user:session): session closed for user fm
May 20 12:38:16 ... systemd: user(a)1005.service: Failed to set up PAM session: Cannot allocate memory
May 20 12:38:16 ... systemd: user(a)1005.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Cannot allocate memory
I add time, from a second textual console as root, to see the "systemd
--user" process reach more than 40 GB of memory before dying.
The lightdm session fails also with the same error.
Tries that do not solved this problem:
- re-installing kernel, systemd
- downgrading systemd to systemd-239-12.git8bca462.fc29
- fresh install in F30
Tries that solve this problem:
- adding mem=8192M to the kernel command line
this machine a 64 G of memory
- commenting pam_systemd.so from PAM (but want to keep it)
Any idea how to debug that?
Thanks a lot.
I've just installed fedora30 desktop on a friend's computer for him.
It was installed and configured here before he brought it to his house
and connected it to his cable modem. Previously I had set up port
forwarding on his modem from port 8027 to port 8027 on his system for
web access and port 8022 to port 8022 on his system for remote ssh
I used the gnome network manager to configure networking and just
manually configured ssh to listen on port 8022 instead of the default.
The problem is that, after bringing it back to his house and putting
it online, the default route was not added properly and the system was
unreachable until I stepped him through the process of adding it
This is the command I had him run as root to configure the default route:
# route add default gw 192.168.9.1 dev enp4s6
Here is that /etc/sysconfig/network-scripts/ifcfg-Wired_connection_2 config:
NAME="Wired connection 2"
Is there something immediately identifiable that would prevent the
default route from working?
Typically NAME and DEVICE are the name of the device, like enp4s6, but
they don't exist in this config. Is that what is missing? I can't
easily reboot this machine, so want to be sure before I do it.
Can dnf get me OSM? I tried osm, OSM, and openstreetmap. I don't
doubt there's some sort of .iso on their own site, but with a program so
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.
I have a newly installed F30, XFCE system.
google-earth-pro will run from a terminal (user fred) but has a 50 second
startup and closedown time.
Tests have shown that su - fred and then running google-earth-pro
avoids the delay.
env shows greatly fewer environmental variables are set in the "su - fred" case.
This led to an alternative approach of un-setting some environmental variables.
(without the "su - fred" step)
unset XDG_RUNTIME_DIR; unset DBUS_SESSION_BUS_ADDRESS; google-earth-pro
The delay is no longer present and google-earth-pro appears to run OK.
Has anyone any idea what is going on here?
How important are those environmental variables?
For a very long time I was using Fedora, much older versions. A few
days back I installed Fedora 30.
I was using fdisk to format an USB pendrive. After creating a new
partition with 'n' and checking with 'p' that it was created, I typed
't' to change the type from 'Linux Filesystem' to something compatible
with MSW. If I am remembering correctly, earlier I used 'c' for 'LBA
32' partition. But now, when I hit 'L' for the list, it showed me an
entirely unknown kind of table.
I could nowhere get any documentation for this new kind of table. I
could not understand anything.
Thanks in advance for any help.
I'm running Fedora 30 in a LXC container (the host is CentOS 7). When I
start the container, I get the usual console messages, then nothing. I
do not get a login prompt.
When I attach to the container and run systemctl, I don't see
console-getty.service running. When I try to start it, systemctl says
it is masked. Unmasking and starting console-getty.service gives me the
missing login prompt.
Does anyone know why console-getty.service is masked by default?
Michael Eager eager(a)eagerm.com
1960 Park Blvd., Palo Alto, CA 94306
For those of you wondering the Fedora status of the MDS CVEs that went
public on Tuesday. Here is where we stand:
kernel-5.0.16 and microcode_ctl-2.1-29 contain the initial mitigations
for kernel/microcode, and are in stable updates for F29 and F30, The
kernel is still in updates-testing for F28 as it needs karma, but
should make it to regular updates soon.
libvirt and qemu have updates in updates-testing across all releases.
F29 and F30 updates will push to stable today, and F28 still needs
All updates, once they hit stable, may take a day or two to reach all
mirrors, so if you do not see it available, you can keep trying, or go
directly to the main mirror.
If you do not know what the MDS CVEs are, or would like more
infomation on them, there is a good write up at
On Sun, 2019-05-19 at 19:16 -0400, Stephen John Smoogen wrote:
> There will be an outage starting at 2019-04-10 21:00 UTC ,
> which will last approximately 5 hours.
Hmm, today there will be an outage last month? ;-)
Hi, I've installed tigervnc according to the instructions here for a
new fedora30 install:
mate-desktop doesn't seem to work properly, so I've just stuck with
the default xinitrc, which produces the default fedora30 desktop.
I can connect to the remote machine after providing authorization,
then the local authorization at least twice and finally getting to the
remote desktop. It appears as it normally does, with "Activities" in
The problem is that after starting any applications, whether it's the
file manager, Firefox, or a regular terminal, it starts, but the app
does not appear. I believe it's being directed to another display. Is
I've started the application, and I can confirm it's running by
connecting to the machine via ssh and finding it in the process list,
but it just doesn't display on the remote desktop. I don't have
physical access to the machine to see if the app is started on the
Here is my ~/.vnc/xstartup:
$ cat xstartup
Here is the log file that is produced after starting vncserver:
$ cat localhost.localdomain\:1.log
Xvnc TigerVNC 1.9.0 - built Feb 3 2019 09:54:51
Copyright (C) 1999-2018 TigerVNC Team and many others (see README.rst)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12003000, The X.Org Foundation
Thu May 16 20:28:43 2019
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5901
vncext: created VNC server for screen 0
Thu May 16 20:28:47 2019
ComparingUpdateTracker: 0 pixels in / 0 pixels out
ComparingUpdateTracker: (1:-nan ratio)
Thu May 16 20:29:02 2019
Connections: accepted: 22.214.171.124::37586
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VeNCrypt(19)
SVeNCrypt: Client requests security type TLSVnc (258)
VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888
VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888
Here is the command I run on the local machine to start the vncserver
as the regular user (gary):
$ vncserver :1 -geometry 800x600 -depth 24
Here is what the vncserver command shows in the process table:
$ ps ax|grep vnc
6991 pts/5 Sl 0:05 /usr/bin/Xvnc :1 -auth
/home/gary/.Xauthority -depth 24 -desktop localhost.localdomain:1
(gary) -fp catalogue:/etc/X11/fontpath.d -geometry 800x600 -pn
-rfbauth /home/gary/.vnc/passwd -rfbport 5901 -rfbwait 30000
The reason the hostname is displayed as "localhost.localdomain" is
because it's on a private IP range (192.168.9.110) without DNS, and
I'm using port forwarding from the cable modem to this host for port
5900 through 6000.
Ideas greatly appreciated.