- Joined
- Jun 25, 2015
- Messages
- 704
- Reaction score
- 631
- First Language
- English
- Primarily Uses
- RMMV
I've recently switched to Manjaro Linux running KDE Plasma 5 and ran into some problems with the Steam Linux version 1.6.0.
The Problem Summary
Basically, RPG Maker is using its own libQt5Core.so.5 library while Plasma 5 is using a newer version. When I go to open a new project, the open dialog causes a crash because MV is opening my system file dialog which uses the latest version and you can't mix qt versions without problems.
The Logging Process
So as a fresh installation of both steam and RPG Maker MV everything seems to work fin, the MV editor opens up fine, but the open project is what causes the crash, I attached the full terminal log in a txt document.
The core of the errors are shown here
Editor Starting:
LD_LIBRARY_PATH=/usr/libs/
The Solution Process'
Current Workaround: Use different Desktop Enviroment xfce4 runs MV well.
Same issue: https://forums.rpgmakerweb.com/inde...ux-open-folder-doesnt-work.76302/#post-716482
I started a topic over at the Manjaro forums to see if we can come up with a workaround as well as figure out the core of the problem.
Manjaro Forums Thread: https://forum.manjaro.org/t/rpg-maker-mv-dialog-window-crash-libqt5core-so-5/36011/3
Personally, I would love to work with the developers and community to get this updated in the next main MV Editor update and figure out a workaround in the meantime, other than a different desktop environment.
I would love to hear your take on it, maybe you have a solution in the works, maybe you plan on updating the QT libraries included with MV, either way, I would love to hear from you and get this figured out.
The Problem Summary
Basically, RPG Maker is using its own libQt5Core.so.5 library while Plasma 5 is using a newer version. When I go to open a new project, the open dialog causes a crash because MV is opening my system file dialog which uses the latest version and you can't mix qt versions without problems.
The Logging Process
So as a fresh installation of both steam and RPG Maker MV everything seems to work fin, the MV editor opens up fine, but the open project is what causes the crash, I attached the full terminal log in a txt document.
The core of the errors are shown here
Editor Starting:
Upon opening the "Open Project" dialog:[1206/203044.700593:ERROR:web_plugin_impl.cc(38)] Widevine registration is not supported after context initialization
Setting breakpad minidump AppID = 769
Steam_SetMinidumpSteamID: Caching Steam ID: 76561197996992700 [API loaded no]
GameAction [AppID 363890, ActionID 1] : LaunchApp changed task to SiteLicenseSeatCheckout with ""
GameAction [AppID 363890, ActionID 1] : LaunchApp changed task to CreatingProcess with ""
GameAction [AppID 363890, ActionID 1] : LaunchApp waiting for user response to CreatingProcess ""
GameAction[AppID 363890, ActionID 1] : LaunchApp continues with user response "CreatingProcess"
Opted-in Controller Mask: 0
Game update: AppID 363890 "RPG Maker MV", ProcID 8713, IP 0.0.0.0:0
>>> Adding process 8713 for game ID 363890
GameAction [AppID 363890, ActionID 1] : LaunchApp changed task to WaitingGameWindow with ""
GameAction [AppID 363890, ActionID 1] : LaunchApp changed task to Completed with ""
[1206/203045.701678:ERROR:web_plugin_impl.cc(38)] Widevine registration is not supported after context initialization
Then upon crash, I get this message:Cannot mix incompatible Qt library (version 0x50903) with this library (version 0x50902)
And the (core dumped) log which is what is logged to Linux after it crashes is shown here.Installing breakpad exception handler for appid(steam)/version(1509425745)
Installing breakpad exception handler for appid(steam)/version(1509425745)
/home/brank/.local/share/Steam/steamapps/common/RPG Maker MV/RPG Maker MV.sh: line 15: 8719 Aborted (core dumped) $dirname/$appname "$@"
Game removed: AppID 363890 "RPG Maker MV", ProcID 8719
I tried creating a symlink to override the Mv version of libQt5Core to use my system's version but this caused more issues. I logged via terminal after the symlink2017-12-06 10:46 AM systemd-coredump Process 23711 (RPG Maker MV) of user 1000 dumped core.
Stack trace of thread 23711:
#0 0x00007ff78a9e68a0 raise (libc.so.6)
#1 0x00007ff78a9e7f09 abort (libc.so.6)
#2 0x00007ff78b6e7a2e n/a (/home/brank/.local/share/Steam/steamapps/common/RPG Maker MV/libQt5Core.so.5)
#3 0x0000000000000004 n/a (n/a)
I have also attempted to change the RPG Maker MV.sh script to point the LD_LIBRARY_PATH variable to my /usr/libs/ directoryGameAction [AppID 363890, ActionID 1] : LaunchApp changed task to SiteLicenseSeatCheckout with "" GameAction [AppID 363890, ActionID 1] : LaunchApp changed task to CreatingProcess with "" GameAction [AppID 363890, ActionID 1] : LaunchApp waiting for user response to CreatingProcess "" GameAction[AppID 363890, ActionID 1] : LaunchApp continues with user response "CreatingProcess" Opted-in Controller Mask: 0 Game update: AppID 363890 "RPG Maker MV", ProcID 12203, IP 0.0.0.0:0 >>> Adding process 12203 for game ID 363890 GameAction [AppID 363890, ActionID 1] : LaunchApp changed task to WaitingGameWindow with "" GameAction [AppID 363890, ActionID 1] : LaunchApp changed task to Completed with "" Cannot mix incompatible Qt library (version 0x50902) with this library (version 0x50903) /home/user/.local/share/Steam/steamapps/common/RPG Maker MV/RPG Maker MV.sh: line 15: 12209 Aborted (core dumped) $dirname/$appname "$@"
LD_LIBRARY_PATH=/usr/libs/
The Solution Process'
Current Workaround: Use different Desktop Enviroment xfce4 runs MV well.
It would seem someone had this same problem and tried to make the developers aware of it but has gone unnoticed.sudo pacman -S xfce4
Same issue: https://forums.rpgmakerweb.com/inde...ux-open-folder-doesnt-work.76302/#post-716482
I started a topic over at the Manjaro forums to see if we can come up with a workaround as well as figure out the core of the problem.
Manjaro Forums Thread: https://forum.manjaro.org/t/rpg-maker-mv-dialog-window-crash-libqt5core-so-5/36011/3
Personally, I would love to work with the developers and community to get this updated in the next main MV Editor update and figure out a workaround in the meantime, other than a different desktop environment.
I would love to hear your take on it, maybe you have a solution in the works, maybe you plan on updating the QT libraries included with MV, either way, I would love to hear from you and get this figured out.
Attachments
-
68.3 KB Views: 1
Last edited:





