-
Notifications
You must be signed in to change notification settings - Fork 45
Weird behaviour #52
Comments
Keys are installed in that location. |
How did you install the game? Normally this is not where the data is installed |
I'm packaging the game right now as an rpm for openSUSE. I'm using the openSUSE Cmake macro.
Thus setting the prefix to /usr |
Ok, I understand now why it works in that one terminal. I think opmon needs to be patched to look for the location in the official places (/usr/local/share and /usr/share). It would be best if one could use the value that was given to it via CMake. Not sure if or how that is possible. |
Shouldnt https://github.com/OpMonTeam/OpMon/blob/master/src/utils/path.cpp#L92 do this? BTW I'm using the 0.14 release tarball. But according to git blame it already contains this. |
Okay give me a minute, I might be on it ;) |
We are in a while loop and plan to go through all elements of XDG_DATA_DIRS. So far we actually returned out of it if only the first path is not containig the OpMon dir, not even checking the other elements. Only return the default /usr/local/share/OpMon path if none of the elements in XDG_DATA_DIRS contain OpMon. Fixes OpMonTeam/OpMon#52
Solved it :) |
We are in a while loop and plan to go through all elements of XDG_DATA_DIRS. So far we actually returned out of it if only the first path is not containig the OpMon dir, not even checking the other elements. Only return the default /usr/local/share/OpMon path if none of the elements in XDG_DATA_DIRS contain OpMon. Fixes OpMonTeam/OpMon#52
I just installed opmon and get a very wird behaviour which might be a problem on my side. But I think I will need your help to track it down.
I launch opmon in a terminal and I get:
No window is displayed. Program exits.
Funny enough I have another terminal instance open in which case it launches opmon when I type the name.
For both I get:
So it's the same executable.
When starting over the desktop file in GNOME3 menu it also doesn't start (which is the reason I went to the terminal in the first place).
So my question: under which circumstance is this error message displayed?
The text was updated successfully, but these errors were encountered: