Bug 1212342 - Midnight Commander, at least under KDE, does not remember directory
Summary: Midnight Commander, at least under KDE, does not remember directory
Status: RESOLVED DUPLICATE of bug 1203617
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Leap 15.5
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-14 07:16 UTC by Eric Schirra
Modified: 2023-06-14 11:20 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
ecsos: needinfo? (screening-team-bugs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Schirra 2023-06-14 07:16:23 UTC 
Since the update to Leap 15.5, the Midnight Commander no longer works as expected, at least in the KDE console.
In Leap 15.4, you stayed in the last directory selected in mc after exiting mc.
Now you are back in the startup directory of the mc.
However, in a Ctrl+Alt+F1 console, the mc works as expected.

Expected as in 15.4:
Start of the mc in /home.
Then change to /home/max_mueller
Exit from mc.
You are now in /home/max_mueller

In 15.5 under KDE the behavior is now the following:
Start mc in /home.
Then change to /home/max_mueller
Exit from mc.
You are now back in /home

Should be again like under 15.4
Comment 1 Dirk Weber 2023-06-14 08:04:12 UTC 
Bug 1203617 also contains a workaround.

*** This bug has been marked as a duplicate of bug 1203617 ***
Comment 2 Eric Schirra 2023-06-14 08:44:06 UTC 
(In reply to Dirk Weber from comment #1)
> Bug 1203617 also contains a workaround.
> 
> *** This bug has been marked as a duplicate of bug 1203617 ***

Okay.
But this bug is open since 2022-09.
When will it fixed in packages?
Or should every user do this for himself?
Comment 3 Dirk Weber 2023-06-14 11:20:29 UTC 
(In reply to Eric Schirra from comment #2)
> (In reply to Dirk Weber from comment #1)
> > Bug 1203617 also contains a workaround.
> > 
> > *** This bug has been marked as a duplicate of bug 1203617 ***
> 
> Okay.
> But this bug is open since 2022-09.
> When will it fixed in packages?
> Or should every user do this for himself?

The cause of the changed behavior in plasma sessions has only been identified some days ago.
Now a solution has to be found.
Still it makes sense to keep the discussion at one place - in bug 1203617.