¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Linuxham
  2. Topics

Wayland support for fldigi suite

 

I recently upgraded to the latest versions of KDE on Fedora, which means I am forced out of X and into Wayland. In the past I have had no problems building and running the tasks, but not they build without error, but when running flrig I get a window that opens then immediately closes, leaving the task hanging. no errors, nothing to tell me what might be happening, but no way to see anything. Without flrig running not much else is going to happen either.

I am just guessing it is a Wayland problem, or that the task is not making correct use of XWayland (a bridge I believe), and hence the window just closes. Any ideas on this? Is Wayland actually formally supported?

TIA
 

Should also probably say it included an upgrade from Fedora 39 to 40, but no kernel update along with it.
Cliff, AE5ZA
 

¿ªÔÆÌåÓý

Al,

Just to be sure, rename the .flrig config directory in your home directory and see if flrig will start with a fresh config. I've see corruption rarely happen, but when it happens that is the usual effect.

73,
Cliff, AE5ZA



On Jul 3, 2024, at 21:57, Al - KD2PNR via <ahw609@...> wrote:

Should also probably say it included an upgrade from Fedora 39 to 40, but no kernel update along with it.

 

I also have trouble running fldigi on a Raspberry Pi running Raspberry Pi OS Bookworm. It uses Wayland by default.
fldigi runs very very slow.
I switched back to openbox and it works fine.
I did not try flrig with Wayland
 

Zero issues here on Opensuse Tumbleweed running Plasma 6.1.1 and Mesa 26.1.2 and Wayland.

I know there were some early Plasma and Mesa issues especially on Nvidia hardware (AMD GPUs were unaffected mostly except for one Mesa rendering bug).

What versions is this and they may already be fixed upstream?

Rick Kunath, K9AO
 

Strange but very understandable. I run Linux Mint 21.3 and Fedora 40 in a dual configuration. Fedora runs best. My windows machine always acts up.?


Bog W7ZDX?

On Wed, Jul 3, 2024, 19:55 Al - KD2PNR via <ahw609=[email protected]> wrote:
I recently upgraded to the latest versions of KDE on Fedora, which means I am forced out of X and into Wayland. In the past I have had no problems building and running the tasks, but not they build without error, but when running flrig I get a window that opens then immediately closes, leaving the task hanging. no errors, nothing to tell me what might be happening, but no way to see anything. Without flrig running not much else is going to happen either.

I am just guessing it is a Wayland problem, or that the task is not making correct use of XWayland (a bridge I believe), and hence the window just closes. Any ideas on this? Is Wayland actually formally supported?

TIA


--

Bog W7ZDX
 

I'd be curious to see what the Plasma6 and Mesa versions were.

It seems like of late and otherwise the former good performance of Nvidia hardware has been tarnished and that AMD GPU hardware runs flawless these days.

Might any of this be part of the issue; i.e. Nvidia issues?

I've seen a lot of that lately on the Tunbleweed list. Fortunately I run AND CPUs and AMD GPUs, so I haven't really been bit by any of the Nvidia issues.

Rick Kunath, K9AO
 

On Wed, 03 Jul 2024 19:57:13 -0700
"Al - KD2PNR via groups.io" <ahw609@...> wrote:

Should also probably say it included an upgrade from Fedora 39 to 40,
but no kernel update along with it.
That doesn't sound right, you should be using kernel-6.9.7 on Fedora 40
now, it's reached stable now.

--

Brian G8SEZ
 

On Wed, Jul 3, 2024 at 9:55?PM Al - KD2PNR via <ahw609=[email protected]> wrote:
I recently upgraded to the latest versions of KDE on Fedora, which means I am forced out of X and into Wayland. In the past I have had no problems building and running the tasks, but not they build without error, but when running flrig I get a window that opens then immediately closes, leaving the task hanging. no errors, nothing to tell me what might be happening, but no way to see anything. Without flrig running not much else is going to happen either.

I am just guessing it is a Wayland problem, or that the task is not making correct use of XWayland (a bridge I believe), and hence the window just closes. Any ideas on this? Is Wayland actually formally supported?

Need more details as others have suggested. I've been running all the Flxxx programs under Gnome+Wayland for several releases now without issue. I am using an AMD video card if that matters. I got tired or rebuilding kernel modules with Nvidia every kernel update.

Thanks,
Richard
KF5OIM?
 

OK, well thanks for the responses so far. As for hardware and versions, I am using NVidia GPU, AMD processor. I was running fine until last week when I updated things, but the old builds I had did not work so I started building from the latest stable stuff, and that also fails in the same way, as described. Software is:

OS: 6.9.7-200 (this was also released to F39 before I upgraded but I did not build or try the flxxx stuff at that time.)
KDE Plasma: 6.1.1
KDE Frameworks: 6.3.0
Qt: 6.7.1

Mesa stuff is mostly 24.1.2-7, nothing newer available of Fedora distros.
 

Just tried renaming the .flrig directory and now I do get windows open again. Not able to connect or get the config correct, and then things hang, but it is a step forward I guess. Interesting how I never had any troubles with building and using all this for years now, but all of a sudden things are going bad - kind of reminds me of the old days when I was forced to use Windows for stuff!
 

Finally got it working but not completely sure how, probably stumbled on the correct device, but it suddenly spit up a bunch of errors, then some clicking of the radio, and then it works! Looking at the config files there does seem to be some changes, mostly in layout, but nothing that helped me any.

I am too old to worry about these kinds of things for very long. It works, so I will now have to wait to catch some activity on a band with it and see what it does in real life.

Thanks for the suggestions, and the latest NVidia driver (555) showed up today, but I don't think that is what fixed it (but it did improve video stuff in other areas).

1 - 12 of 12