Network manager applet icon not visible in KDE plasma systray - Fedora 24/25 VM
62 views
Skip to first unread message
Adrian Rocha
Dec 24, 2016, 12:31:36 AM12/24/16
to qubes-users
Hi,
I created a new sys-net VM based on Fedora-24 template. The network works fine but the systray applet icon isn't visible. If I click the mouse over the systray space I can see the menu, connect to the wifi, etc. Something is wrong with the icon. The icon is visible in XFCE, so I think that is some issue in the new version of the Network Manager Applet respect to the KDE systray.
The network manager applet version in Fedora-25 is 1.4.0 and 1.0.10 for Fedora-23.
I created a new template VM Fedora-25, but the issue persists.
Any ideas?
I created a new sys-net VM based on Fedora-24 template. The network works fine but the systray applet icon isn't visible. If I click the mouse over the systray space I can see the menu, connect to the wifi, etc. Something is wrong with the icon. The icon is visible in XFCE, so I think that is some issue in the new version of the Network Manager Applet respect to the KDE systray.
The network manager applet version in Fedora-25 is 1.4.0 and 1.0.10 for Fedora-23.
I created a new template VM Fedora-25, but the issue persists.
Any ideas?
Andrew David Wong
Dec 24, 2016, 1:06:29 AM12/24/16
to Adrian Rocha, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
This is a known issue, but it was previously reported in a Debian 9
sys-net, whereas yours is based on Fedora. It sounds like the common
factor in both cases is KDE in dom0.
https://github.com/QubesOS/qubes-issues/issues/2283
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJYXhBYAAoJENtN07w5UDAwE7AP/0oA2Ey6Emvi63EUM4G9WvoS
sh9IKgx9uV5qmsj7Y4PkjmeM1Zi2DVoQlZR7CSOiO1y1rt2oftP4Ar3oLt1txMWL
tps6GYUqOXOatLM5PKqEP+JJfiv5NYUWWwez7L793RSeyhtOx+AuFX655gTXVdot
NBp6O1a7hBp3ReVtavZRXrs4DjWuJ+yDjSP45BkaD5I1lfjPKAO2BBV/o4JSh4ws
77VkrPY35gnJpXQH0uC4flkKVyPNhzLzRRfcLp9fe5+S0Wggv0H8ARWzKQU14yj7
MXnqzTQOK0MTYoQNuulgOIhlRY3i6i3yc+3g2ReYA9rfmzknS9/U4cdQZkZo8GBR
nV/HdvOjgAjyziCC4j40QshVSDKVkacCPsIHDW5fPA4oCM4md4/QOTk6R2mzzGjV
0cYh24vtrZIWm5Dyieg22u4+i3LDWyW6Tff9gte7HkRxLISCLuVkcltF4tVw1lvO
VQ6XYBXd/K5BdVb76++vwWD3yiei0CUQTMSLaYp8VfXsPl9oql1gd0/2oXgtuq3m
TenAARQi7hA6/BbUajybvuUR8Yw6ZoWKmhA4KqsFi8g5WS3Oy6QebsDI3Hz5oN5S
uMwm/ney0HemaUEg3iJWD9uby1sVSb1YNgAyibebTKvph1PzlALgxb2U7KRY7n2K
KCOqAzrPy/qWUIOISxqA
=s3cs
-----END PGP SIGNATURE-----
Hash: SHA512
sys-net, whereas yours is based on Fedora. It sounds like the common
factor in both cases is KDE in dom0.
https://github.com/QubesOS/qubes-issues/issues/2283
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJYXhBYAAoJENtN07w5UDAwE7AP/0oA2Ey6Emvi63EUM4G9WvoS
sh9IKgx9uV5qmsj7Y4PkjmeM1Zi2DVoQlZR7CSOiO1y1rt2oftP4Ar3oLt1txMWL
tps6GYUqOXOatLM5PKqEP+JJfiv5NYUWWwez7L793RSeyhtOx+AuFX655gTXVdot
NBp6O1a7hBp3ReVtavZRXrs4DjWuJ+yDjSP45BkaD5I1lfjPKAO2BBV/o4JSh4ws
77VkrPY35gnJpXQH0uC4flkKVyPNhzLzRRfcLp9fe5+S0Wggv0H8ARWzKQU14yj7
MXnqzTQOK0MTYoQNuulgOIhlRY3i6i3yc+3g2ReYA9rfmzknS9/U4cdQZkZo8GBR
nV/HdvOjgAjyziCC4j40QshVSDKVkacCPsIHDW5fPA4oCM4md4/QOTk6R2mzzGjV
0cYh24vtrZIWm5Dyieg22u4+i3LDWyW6Tff9gte7HkRxLISCLuVkcltF4tVw1lvO
VQ6XYBXd/K5BdVb76++vwWD3yiei0CUQTMSLaYp8VfXsPl9oql1gd0/2oXgtuq3m
TenAARQi7hA6/BbUajybvuUR8Yw6ZoWKmhA4KqsFi8g5WS3Oy6QebsDI3Hz5oN5S
uMwm/ney0HemaUEg3iJWD9uby1sVSb1YNgAyibebTKvph1PzlALgxb2U7KRY7n2K
KCOqAzrPy/qWUIOISxqA
=s3cs
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages