https://bugs.kde.org/show_bug.cgi?id=470983

davejpla...@gmail.com <pla...@opensuse.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WAITINGFORINFO              |LATER

--- Comment #16 from davejpla...@gmail.com <pla...@opensuse.org> ---
(In reply to Nate Graham from comment #14)
> If this is still happening in Plasma 6.3, can you try in a new clean user
> account to rule out any of your customizations or user-specific environment
> variables being at play? If it works there, hopefully we can narrow down
> which specific thing causes it, and then we can dig into whether our
> handling of it is a bug or not. Thanks!

Sorry for the delay, I've openSUSE Tumbleweed with plasma6 and Leap:15.6 with
plasma5 sharing the same home partition. The workaround that still works on
leap but no longer fixes Tumbleweed was to start mc.sh in the current shell
with bash command ".".
The best test to explain the problem is a script in your home directory "echo
-e "cd bin" > testmc && chmod 0755 testmc" if you execute 
./testmc you will remain where you are and if you execute ". testmc" you will
change to ~/bin
This problem first surfaced in plasma5 and has so many workarounds that it
gives me a headache but my mc exits into the directory that I'm in in mc when I
exit because I've modified the wrapper script. 
Unfortunately I don't have time to find the cause in plasma6, in plasma5 I only
had to disable systemd boot but it seems like systemd boot can no longer be
disabled. mc works for me with the workaround

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to