users October 2020

users@lists.fedoraproject.org

106 participants
126 discussions

Re: other rpm-distros
by David 30 Oct '20

30 Oct '20

Please hit delete button if this topic does not interest you. Thank you. This is a follow-up to my post yesterday, about my first-hand experience with OpenMandriva Alpha on hardware, based on my previous experience with Fedora, and other rpm-distros. The initial problem I reported using their default Falkon browser, can simply be avoided by just using the ancient version of Firefox in their repo, Version 79. Today, I decided to try their fancier version using the heavily modified kernel called "znver1," for Ryzen processors. I installed it on a blank SSD and treated it like it was my only operating system. It had numerous problems. I can not criticize it though because it is beyond the scope of my Linux skills. Nevertheless, I decided to go even deeper and write over it a whole new fresh install using their Cooker iso for znver1, thinking, maybe I would get a newer version. ( Cooker is their very unstable branch ) The main thing I discovered doing that, is that their isos in Cooker are built with clang, and the others are apparently not. I am in their Cooker znver1 right now typing this but having to use their Firefox 79. One issue I am having, and please email me privately about it, is that Discover wants to update 785 pages ( which would put it on par with Rawhide ), and it is missing python3.8dist(six), and will not update a single package. And dnf thinks the system is up-to-date. That sounds like something that could happen in Fedora and maybe one of you know a workaround. Their Cooker is not as stable as Fedora's Rawhide. I will most likely write over my first install of their 4.2 Alpha with another distro, and keep this Cooker znver1 to see if I can learn anything. I have to assume with their tiny team, that this znver1 thing is going to have limited packages that are compatible. Right ? In its present form before the missing updates, the version numbers of packages are only 0.0.0.1 ahead of the ones in 4.2 Alpha. But the expected updates will be the latest available. I now have about 10 hours of user experience on hardware with OpenMandriva's alpha and Cooker version. Please email me privately for further info, as I can only imagine there are only a few people interested in other rpm-distros. One funny thing is their Rosa Image-writer didn't work in the Alpha version, so I had to use the Fedora Image Writer on Flathub, to create the two znver1 installs, but Rosa Image-writer did work on the Cooker version. Cheers, David Locklear

1 0

sort of rpm-distro related
by David 29 Oct '20

29 Oct '20

The only distro that I have used in the past year and a half has been Fedora Workstation. I have been using it on hardware only and using it for daily personal use, but also for my hobby business, which is the only income I have. Today, I was feeling like I needed to explore some other distros and I had a new blank SSD available. I had just updated Rawhide on my primary NVMe and Fedora 33 on my secondary NVMe, so I had a pretty good idea how they performed on a Ryzen 5 computer that I built two days ago. I spent two hours trying to install Arch from scratch, and surrendered to that idea. I decided that since I had never tried OpenMandriva that I would install their Alpha version ( 4.2 ). I do not know if it was built with clang as they advertise or brag about. ***The point to the discussion below is just to show some observations related to rpm-based distros assuming that this first-hand info might encourage or discourage a Fedora user from repeating what I just did. *** So please hit delete button now, if that is not of interest. I have been in OpenMandriva Alpha 4.2 ( Argon ) about 30 minutes, and the similarities to Fedora 33 ( KDE ) are something worth mentioning. One key difference is lots of KDE software is preinstalled, as are things a new user to Linux might want like printer drivers, and codecs. Flatpak was not preinstalled. Falkon was the only web-browser and Discover did not show another option. dnfdragora was preinstalled and showed Firefox 79 available. So I went thru all the flatpak routine in console and now writing this in Firefox 82. The main thing I found that I did not like about Falkon, is that Google does not support it. So you can't log into YouTube, Gmail, etc. However, Youtube and over video sites played out of the box. Below are a few specs as a comparison to Fedora 33 ( after an update ) Plasma 5.19.4 kernel 5.8.13 systemd 246.20200827 x11-server 1.20.9 qt 5.15.0 dnf 4.4.0 rpm 4.16.0 KDE apps 20.08 KDE frameworks 5.73.0 cups 2.3.3 libvulkan 1.2.153 mesa 20.2.0-rc3 libwayland 1.18.0 This becomes a rolling-release upon updating, so it is not really 4.2 anymore and appears to have a different repository than 4.2, so assuming this install never borks, I should never have to reinstall it. Right ? The iso was published around July 27. I did an update using dnf but then a bunch of stuff updated after that in Discover. Filesystem installed was ext4. I just see now that they had a iso optimized for Ryzen users. So I guess I should reinstall it. LOL ! I do not think Fedora lovers would like OpenMandriva, as it comes with stuff like Midnight Commander and emoji picker and lots of wallpapers pre-installed or with an easy click in Discover. I doubt Ubuntu and Manjaro / Arch users would like OpenMandriva. One disclaimer, is that my opinion or statements above are partially biased, as I lived in Mageia 6 on hardware for six months, before it was published and lived in ROSA R11 for a month on hardware before coming to Fedora. Feel free to email me privately, if you think I can offer more details, or reply to this post if there is something Fedora related to mention. I can only guess there are one or two people out there that use both Fedora and OpenMandriva, or shared development of KDE. I think what discourages some users from trying it or using it is the name "OpenMandriva." Imagine another dimension of time and space where Mandrake Linux, never lost a lawsuit. David Locklear

2 1

firewalld
by Michael J. Baars 29 Oct '20

29 Oct '20

Hi, I'm writing a client and server program for cluster computation. I noticed that nmap sees a specific port as open on Fedora Server and as filtered on Fedora Workstation when the server is running and sees this port as closed on Fedora Server and as filtered on Fedora Workstation when the server is not running. While looking into the firewalld configuration I found that Fedora Workstation and Fedora Server have one major difference their configuration files: <port protocol="udp" port="1025-65535"/> <port protocol="tcp" port="1025-65535"/> After removing these specific lines from /etc/firewalld/zones/FedoraWorkstation.xml, using firewall-cmd, the ports are still accessible by the client and server program. Can someone please tell me how to close these ports on Fedora Workstation? And why does nmap report the ports as filtered on Fedora Workstation and as open/close on Fedora Server? Best regards, Mischa.

3 7

logout problems?
by Tom Horsley 29 Oct '20

29 Oct '20

Just noticed this fedora 33 problem: With rpmfusion nvidia drivers installed, running a GNOME on Xorg session with sddm as my login manager. (What part of this is relevant, I don't know :-). If I choose "logout" from the menu in the top right, I get the logout dialog, click on logout now, then that's it. I never get another login prompt from the GUI. Have to hit Ctrl-Alt-F2 to get to a terminal and reboot.

1 0

X Org Server is abandonware
by George N. White III 29 Oct '20

29 Oct '20

It's Time To Admit It: The X.Org Server Is Abandonware - Phoronix <https://www.phoronix.com/scan.php?page=news_item&px=XServer-Abandonware> "The last major release of the X.Org Server was in May 2018 but don't expect the long-awaited X.Org Server 1.21 <https://www.phoronix.com/scan.php?page=search&q=X.Org+Server+1.21> to actually be released anytime soon. This should hardly be surprising but a prominent Intel open-source developer has conceded that the X.Org Server is pretty much "abandonware" with Wayland being the future. This comes as X.Org Server development hits a nearly two decade low <https://www.phoronix.com/scan.php?page=news_item&px=X.Org-Server-2019-Low>, the X.Org Server is well off its six month release regiment in not seeing a major release in over two years, and no one is stepping up to manage the 1.21 release." One of the motivations for Wayland was that the X.Org was becoming unmaintainable and suffered from design choices that are no longer relevant. It has been clear for some time that X Org was not getting much attention, but Wayland has been around for a while and still many drivers (Wacom professional drawing tablets) require X (and don't work with X-Wayland). An additional problem is that developers with decades of X11 experience are aging out. The Phoronix post has 100's comments, so far I haven't seen them degenerate to politics. -- George N. White III

24 31

system loses HDMI sound device
by Eyal Lebedinsky 28 Oct '20

28 Oct '20

This is up-to-date f32 amd64. From time to time I find that I do not have sound, and then pavucontrol shows no configuration is available. Sound is via HDMI to the monitor (TV). The internal sound device is not used. So far the only way out I found is to log out/in, but this is not ideal. Is there a way to make the system (I suspect it is X) see the sound device and enable it? Maybe with a udev command? When all is well, I see this: $ udevadm trigger -n -v |grep sound /sys/devices/pci0000:00/0000:00:1f.3/sound/card0 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/hwC0D0 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/hwC0D2 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input12 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input12/event12 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input13 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input13/event13 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input14 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input14/event14 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input15 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input15/event15 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input16 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input16/event17 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input17 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input17/event18 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input18 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input18/event19 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input19 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input19/event20 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input20 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input20/event21 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input21 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/input21/event22 /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/pcmC0D0c /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/pcmC0D0p /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/pcmC0D10p /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/pcmC0D1p /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/pcmC0D2c /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/pcmC0D3p /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/pcmC0D7p /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/pcmC0D8p /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/pcmC0D9p /sys/devices/pci0000:00/0000:00:1f.3/sound/card0/controlC0 /sys/devices/virtual/sound/seq /sys/devices/virtual/sound/timer When I have no sound I am missing the last two devices. In case it is related, there is also a KVM instance running on this machine. -- Eyal Lebedinsky (fedora(a)eyal.emu.id.au)

5 5

Keyboard problem in F33
by Joachim Backes 28 Oct '20

28 Oct '20

Hi guys, I upgraded almost sucessfully to F33. Before this action, my Keyboard was German,no deadkeys option, in all Fedora versions. But now, each time I logout and relogin, my keyboard is reset to an STD US keyboard. I am running as desktop a CINNAMON desktop. How can I get rid from this problem? KInd regards Joachim Backes -- Fedora release 33 (Thirty Three) Kernel-5.9.1-300.fc33.x86_64 Joachim Backes <joachim.backes(a)rhrk.uni-kl.de> https://www-user.rhrk.uni-kl.de/~backes/

3 2

DWService
by Patrick Dupre 28 Oct '20

28 Oct '20

Hello, Can I have some feedback about DWS (dwservice) https://www.dwservice.net/ ? Is it reliable ? It there alternatives? Thanks =========================================================================== Patrick DUPRÉ | | email: pdupre(a)gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 ===========================================================================

1 0

FYI: Thunderbird 78 fails after upgrade to Fedora 33
by Richard England 28 Oct '20

28 Oct '20

Launching Thunderbird, after upgrading to Fedora 33, opens a small browser window displaying the following error: > XML Parsing Error: undefined entity > Location:chrome://messenger/content/messenger.xhtml > Line Number 905, Column 3: > <key id="openLightningKey" > --^ This was working properly prior to the upgrade to Fedora 33 but after installing (via dnf update) the latest version of Thunderbird (78.3.1). You can still open it using "thunderbird --safe-mode". After much searching and guesswork I found a report describing it here: https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg5848655.html The workaround/fix for me was apparently to remove all the language packs installed in .thunderbird/(default_profile) as described here: https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg5848871.html I added back in the English GB package and it still worked. I note that I had numerous language packs that were flagged as incompatible but removing only those did not help. Unfortunately I haven't the time/resources to further debug but hopefully this will help anyone else that encounters this issue. ~~R

1 0

FYI: Thunderbird 78 fails after upgrade to Fedora 33
by Richard England 28 Oct '20

28 Oct '20

Launching Thunderbird, after upgrading to Fedora 33, opens a small browser window displaying the following error: > XML Parsing Error: undefined entity > Location: chrome://messenger/content/messenger.xhtml > Line Number 905, Column 3: > <key id="openLightningKey" > --^ This was working properly prior to the upgrade but after installing (via dnf update) the latest version of Thunderbird (78.3.1). You can still open it using "thunderbird --safe-mode". After much searching and guesswork I found a report describing it here: https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg5848655.html The workaround/fix for me was apparently to remove all the language packs installed in .thunderbird/(default_profile) as described here: https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg5848871.html I added back in the English GB package and it still worked. I note that I had numerous language packs that were flagged as incompatible but removing only those did not help. Unfortunately I haven't the time/resources to further debug but hopefully this will help anyone else that encounters this issue. ~~R

1 0

← Newer
1
2
3
4
5
6
7
...
13
Older →