MidnightCommander Problems After glib2 Update
by rahrah from LinuxQuestions.org on (#6EEFZ)
Hi,
The update to glib2-2.76.5 broke mc's (MidnightCommander's) ability to open various files.
I was able to confirm that this also broke Arch's version of mc.
The commits in glib2 seeming responsible for this are:
in 2.76.x
3fd1b63453417617fc1709a2d12aaa6f3691b40d
in 2.77.x
71b7efd08a1feadc8ddca31e164034b1f5a6bd74
Bug reports can be found:
https://gitlab.gnome.org/GNOME/glib/-/issues/3094
https://midnight-commander.org/ticket/4502
https://bugs.archlinux.org/task/79540
Other issues possibly caused by the update:
https://gitlab.gnome.org/GNOME/glib/-/issues/3095
Rolling back to glib2-2.76.4-x86_64-1.txz seems to give a workable fix to the problem. That file can be found at slackware.uk (thanks Darren) here:
https://slackware.uk/cumulative/slac...4-x86_64-1.txz
(there's the 32bit version in the cumulative hierarchy, too).
Cheers,
===Rich
The update to glib2-2.76.5 broke mc's (MidnightCommander's) ability to open various files.
I was able to confirm that this also broke Arch's version of mc.
The commits in glib2 seeming responsible for this are:
in 2.76.x
3fd1b63453417617fc1709a2d12aaa6f3691b40d
in 2.77.x
71b7efd08a1feadc8ddca31e164034b1f5a6bd74
Bug reports can be found:
https://gitlab.gnome.org/GNOME/glib/-/issues/3094
https://midnight-commander.org/ticket/4502
https://bugs.archlinux.org/task/79540
Other issues possibly caused by the update:
https://gitlab.gnome.org/GNOME/glib/-/issues/3095
Rolling back to glib2-2.76.4-x86_64-1.txz seems to give a workable fix to the problem. That file can be found at slackware.uk (thanks Darren) here:
https://slackware.uk/cumulative/slac...4-x86_64-1.txz
(there's the 32bit version in the cumulative hierarchy, too).
Cheers,
===Rich