Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[BryanC]

Dialog boxes that open in a minimized or hidden state (must be expanded to full screen with my WM shortcut keys to see them).
Text entry into most fields is unreliable, for instance entering repeating characters causes issues with the text completion. Same when deleting characters (I select and delete now by habit). When it doesn't break, it's slow.
Copy-paste is unreliable from outside->inside MC and vice versa.
The modern tag editor is very slow, especially with multiple files selected.

[mwillems]

Dialog boxes that open in a minimized or hidden state (must be expanded to full screen with my WM shortcut keys to see them).

I do see that very occasionally.  I've never figured out what causes it, which makes it hard to report.  I've noticed that (at least the way it presents on my system) is that the windows aren't minimized, they're just about two pixels wide and ten or twenty pixels tall.  So if you can find the tiny window you can drag it bigger in addition to using shortcuts (or in case shortcuts don't work).  It's like there isn't a minimum size for some windows?

Text entry into most fields is unreliable, for instance entering repeating characters causes issues with the text completion. Same when deleting characters (I select and delete now by habit).

I've noticed the double letter problem for sure.  What's weird is that I reported it a while back and it got fixed, but then it recurred.  For me it seems to be related to some kind of diacritic selection pop up?  Like if I type two "n"s in quick suggestion I get a sudden flash of Spanish n with a tilde over it as an autocomplete suggestion which steals focus from the text entry window and that breaks text entry.  Ditto if I type two o's in quick succession, I get a bunch of diacritical suggestions.  For some letters it breaks text entry without offering diacritic suggestions (maybe because there aren't any?) like typing two "g"s.  It's like JRiver is calling out to (or tripping over) some kind of text entry library that interprets two of the same character in quick succession as a request for diacritics.  But the focus stealing/key eating is definitely a pain point.

Copy-paste is unreliable from outside->inside MC and vice versa.

I've never noticed that one. I guess there are two (or maybe three?) different clipboards on Linux (see https://wiki.archlinux.org/title/Clipboard), which might be part of the issue.  I don't frequently use the select/middle-click clipboard, and I tested just now and that clipboard doesn't seem to work in JRiver at all.  I pretty much only use the control-C, control-V clipboard when moving text into JRiver, and that one has always worked consistently for me.   

Alternatively, if you're seeing bad behavior with the Ctrl-C/Ctrl-V clipboard, I'm using Gnome with no clipboard manager FWIW, if you want to try and narrow down what might be different about our environments that causes it.

The modern tag editor is very slow, especially with multiple files selected.

This I definitely see.  Tag editing is slower on Linux than it was on Windows for sure.

[JimH]

Some of that could be the desktop GUI.

[BryanC]

Re: the modern tag editor, the interesting thing is that it's not that slow on library clients, it's only slow on the server. So maybe there is some extra i/o, attribute reading or something that is slowing it down, whereas the client can only operate on the database.

Re:  DE's, it could certainly be WM or DE-related, it's a complex beast. I have a hunch that XWayland isn't helping (especially long-term) so that would be the first step I'd tackle, and if you're seeking video parity with Windows it's probably a requirement.

[mwillems]

Some of that could be the desktop GUI.

The double letter issue probably is, although for whatever reason I don't see it in any other program except JRiver.  I just checked and I can't reproduce the double letter issue with a minimal window manager, so it probably is some kind of interaction between JRiver and *some* desktop component, but whatever that component is it's not unique to one desktop (I see the issue in both Gnome and KDE).  So if I had to guess, it's probably some kind of shared text entry/framework thingo like ibus that's getting tripped.

[JimH]

That seems like a display problem.

[mwillems]

That seems like a display problem.

So I remembered reporting the double letter issue previously and there being a fix.  Here are some threads from MC24 where this was previously reported and fixed.  It seems to have become unfixed sometime in the intervening versions:

https://yabb.jriver.com/interact/index.php/topic,116364.0.html  (reporting the original problem with bob's commentary)
https://yabb.jriver.com/interact/index.php?topic=117727.0  (separate report noting that it brings up a diacritical window)

It looks like (based on the second thread) if you long press a key on JRiver for Windows you get a diacritical window, but on Linux just repeating a letter twice can trigger it?  I will note that it looks like back when the original issue occurred that typing two of the same letters one after the other in JRiver would always trigger the diacritical popup no matter how much time elapsed between letters.  Now it seems to only happen when you type the two letters very quickly one after the other.  Otherwise the issue presents the same way, so presumably the issue is related to the one back then?

[HTPC Videophile]

Dialog boxes that open in a minimized or hidden state (must be expanded to full screen with my WM shortcut keys to see them).
Text entry into most fields is unreliable, for instance entering repeating characters causes issues with the text completion. Same when deleting characters (I select and delete now by habit). When it doesn't break, it's slow.
Copy-paste is unreliable from outside->inside MC and vice versa.
The modern tag editor is very slow, especially with multiple files selected.

+1 . Same problem for me on Fedora 40(Gnome/Cinnamon). This drawback forcing me to stay on Kodi in Fedora unlike Windows where i use both Kodi and JRiver .

[JimH]

Try a different desktop.

[Awesome Donkey]

Also if you're using Wayland, you'd probably have better luck using an X11 session instead. MC doesn't actually support Wayland though it runs more-or-less fine besides UI weirdness and small issues like dialog boxes appearing very small via XWayland.

[mattkhan]

At this point in time, can MC seriously say it supports Linux without working fine on Wayland? Given MC says it is tested in Debian and given a default Debian stable setup, as far I know, uses Wayland, I would say no. I would say the same about the relatively poor behaviour on kde too mind you (albeit I'm biased cos I use kde).

[JimH]

I don't think I said that. I suggested a test.

[mattkhan]

I was more responding to the point about using X11 for an MC setup, I mean that might be fine as a suggestion for getting a more useable system but (imo) it's can only be considered a temporary workaround given the prevalence of Wayland these days.

Fwiw I did try a stock Debian stable setup recently and it still had a variety of glitches of the sort described in this thread.

Ultimately people who use Linux tend to use the flavour they like so MC has to work on that setup to be useable for them. NB: I have no idea how much work such an endeavour actually is or whether it's worth it to you.

[Awesome Donkey]

At this point in time, can MC seriously say it supports Linux without working fine on Wayland? Given MC says it is tested in Debian and given a default Debian stable setup, as far I know, uses Wayland, I would say no. I would say the same about the relatively poor behaviour on kde too mind you (albeit I'm biased cos I use kde).

To be fair, a lot of software still doesn't natively support Wayland. Most desktop environments (Xfce, MATE, etc.) still don't support it yet either. It's thanks to XWayland that a lot of software including MC runs as good as it does on Wayland.

[David Sydney]

Also if you're using Wayland, you'd probably have better luck using an X11 session instead. MC doesn't actually support Wayland though it runs more-or-less fine besides UI weirdness and small issues like dialog boxes appearing very small via XWayland.

I use Manjaro/KDE and I know there is some interaction with MC and the search /tag text entry that is affected I think by this also. I would interested to pursue but I dont know I can use a X11 session?

[Awesome Donkey]

KDE Plasma is known to have quirks with MC. I seem to recall a workaround for one of the quirks exists but I don't remember what it is and what it's for. X11 may not matter in those cases.

[bob]

There is something up with the modern tag window, I think it's WRT event processing of redraws overwhelming the key release events on linux.
Looking at it.
Fixed one thing, which is the suggestion window stealing focus. That will be in the next build.
In the meantime I just tested the legacy tag window and it works well for me.

[Awesome Donkey]

Can you set a minimum size for some windows like the About dialog and the dialog that pops up when doing a library backup to workaround the Wayland-related issues where they appear very small? Are the window sizes for those windows saved somewhere?

[BryanC]

It came up in another topic but there's also a bug in Find & Replace, the first time it's opened it will rapidly switch focus between the find and replace fields (subsequent reopens are more stable).

[bob]

Can you set a minimum size for some windows like the About dialog and the dialog that pops up when doing a library backup to workaround the Wayland-related issues where they appear very small? Are the window sizes for those windows saved somewhere?

There actually is supposed to be a calculated minimum size. Is it just those 2 dialogs?
BTW, I can't get that to happen on debian bullseye and wayland gnome
wayland plasma is a disaster in general.

[Awesome Donkey]

Those are the main two I've noticed. It did happen once for the Options window too, but hasn't again. I suspect it could happen with others like RM&C, would need to mess with that.

I use GNOME, not Plasma (thankfully).

[mwillems]

There actually is supposed to be a calculated minimum size. Is it just those 2 dialogs?
BTW, I can't get that to happen on debian bullseye and wayland gnome
wayland plasma is a disaster in general.

For me with Gnome on Wayland, it happens to me infrequently with almost any child window (I've seen it with options, I've seen it with the registration dialog, about, etc.).  And when I say I see it infrequently it's like, maybe once a month using MC on Linux every day.  I've never seen it on XFCE4 FWIW, only with Gnome. 

I haven't found a way to reproduce it or I'd have reported it, but the window is always a pixel or two wide and maybe ten pixels tall when I see it, and it's mostly just a challenge to realize that this thing has happened, find the tiny window, and resize it.

[bob]

For me with Gnome on Wayland, it happens to me infrequently with almost any child window (I've seen it with options, I've seen it with the registration dialog, about, etc.).  And when I say I see it infrequently it's like, maybe once a month using MC on Linux every day.  I've never seen it on XFCE4 FWIW, only with Gnome. 

I haven't found a way to reproduce it or I'd have reported it, but the window is always a pixel or two wide and maybe ten pixels tall when I see it, and it's mostly just a challenge to realize that this thing has happened, find the tiny window, and resize it.

In general the popup windows are created (not shown) 1x1 which is the minimum in X (0x0 in windows and Mac) then on first show set to their actual size which shouldn't be under 400x400 (at least for the about box). Wayland on my i9 with intel graphics and plasma even the system dialogs are screwed up. Gnome is better but still lacking smoothness.

[Awesome Donkey]

I haven't found a way to reproduce it or I'd have reported it, but the window is always a pixel or two wide and maybe ten pixels tall when I see it, and it's mostly just a challenge to realize that this thing has happened, find the tiny window, and resize it.

Almost always happens to me after running MC after doing a system reboot with the About dialog, library backup dialog, etc. all doing that when using Wayland (and XWayland).

[David Sydney]

Another one ...on Windows version the top back,forward,refrsh buttons (next to the window tabs) operate like a browser and take me back/forward to the last/next screen I have looked at.

Unfortunately in Linux version, the backbutton takes me back all the way to the front of "Start" or whatever I was looking at. Then I have browse about 4 screens back to the same place for Forum, Linux version then the thread I was looking at before. I am running KDE on Manjaro if that makes a difference.

David