Windows/Linux journal_event discrepancies
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 182
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
**Please complete the following information:**
[//]: # (You can gather most of this information with the EDMC System Profiler)
- Version: 6.1.2
- Game Version: 'Odyssey'
- OS: Windows 11, CachyOS Linux
- OS Locale: English
- If applicable: N/A
**Describe the bug**
During game startup EDMC is emitting different journal events on Linux vs Windows. Specifically the StartUp and Loadout events.
**To Reproduce**
Steps to reproduce the behavior:
Run EDMC, start ED and login on windows, do the same on Linux.
**Expected behavior**
The synthetic StartUp events and the actual Loadout events should be sent to the journal_event() of the plugins.
**Additional context**
I created EDMarketConnector-debug.log logs on Windows and on Linux and had a plugin that the first line of its journal_event() function wrote a debug entry stating what the event was.
Those logs are attached along with the actual game logs for the same session from both machines.
There are minor differences (Friends, Carrier etc.) due to it being two commanders but what is significant is on Windows there are two StartUp events and one Loadout event both of which are missing on Linux.
Windows:
*StartUp*
Fileheader
*StartUp*
*StartUp*
Commander
Materials
Rank
Progress
Reputation
EngineerProgress
LoadGame
Statistics
Location
ShipLocker
Missions
*Loadout*
Cargo
Linux:
Fileheader
Commander
Materials
LoadGame
Rank
Progress
Reputation
EngineerProgress
Statistics
ReceiveText
Location
ShipLocker
Missions
Cargo
This is happening every time and I've been unable to determine what is causing it. I asked on Discord but received silence.
**Please Confirm the Following...**
[//]: # (Add any other context about the problem here.)
- [Y] I have checked [Open Issues](https://github.com/EDCD/EDMarketConnector/issues/) to ensure this is not a duplicate
- [Y] I have checked the [Troubleshooting Guide](https://github.com/EDCD/EDMarketConnector/wiki/Troubleshooting) to check for known workarounds
**Logs**
[windows-Journal.2026-08-31T224057.01.log](https://github.com/user-attachments/files/31676450/windows-Journal.2026-08-31T224057.01.log)
[windows-EDMarketConnector-debug.log](https://github.com/user-attachments/files/31676449/windows-EDMarketConnector-debug.log)
[linux-Journal.2026-08-31T222546.01.log](https://github.com/user-attachments/files/31676451/linux-Journal.2026-08-31T222546.01.log)
[linux-EDMarketConnector-debug.log](https://github.com/user-attachments/files/31676452/linux-EDMarketConnector-debug.log)
Contributor guide
Research direction
Start by comparing the attached Windows and Linux EDMarketConnector-debug.log and journal logs, then trace how journal_event() receives the startup sequence. Done means synthetic StartUp events and the actual Loadout event are delivered consistently to plugins on both Windows and Linux.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100