Open peter-stoll opened 7 months ago
I cannot replicate this problem.
Try renaming $HOME/.config/geeqie/geeqierc.xml and then running Geeqie. A default configuration file will be generated. Then edit it as above and try again.
[v1.7.2 is a rather old version]
We get closer: Doing what you recommended, I found that with the default configuration it worked, but by changing line by line in geeqierc.xml between my buggy version and the default version, I found that that the variable 'save_windowworkspace' affects on which workspace the windows is shown on start, which is odd to me, since a 'save..' options should, just by it's name, not affect the starting behavior.
Starting with the default configuration file for all other options, and being on workspace 0, I can reproduce it like this:
With this setting:
save_window_workspace = "false"
workspace = "1"
the windows pops up at workspace 0 , while with this setting:
save_window_workspace = "true"
workspace = "1"
the window pops up at workspace 1, which is why it was not shown.
Taking this for it's own, the behavior might be correct, but one would expect, that setting the option:
use_saved_window_positions_for_new_windows = "false"
would prevent the window from popping up on anther workspace. This is the behavior of version 2.4, which I tried (installed from flatpak), so I assume the developers agree on this. With that I conclude that the correct Bug description should be:
Setting the option use_saved_window_positions_for_new_windows="false" does not affect the workspace where the windows was shown, but still uses the old workspace.
For myself, I will continue by using the flatpak 2.4 version, so this is not an issue for me anymore. But since the 1.7 version is still distributed as dpkg on Mint 21.3, and probably also on Ubuntu 22.04, it might be worth to fix this on an older version.
Setup (please complete the following information):
Describe the bug With the precondition that there is no geeqie running yet: When, and only when, in $HOME/.config/geeqierc.xml the variable save_window_workspace is set to true, like this: save_window_workspace = "true" , then the geeqie windows does not show after I type on the console: $ geeqie [Enter] I notice sometimes a very short blinking in the dash at one place (where the icon should occur), but nothing else happens. There is no output on the console, and the process continues to run in the foreground. There process consumes no measurable CPU time. Simply changing above option to "false" makes geeqie working as expected. In case that the precondition is that there is already a geeqie running (even though it has no window), the process goes in background. Giving an image as argument does not change the behavior.
Notice that setting variable use_saved_window_positions_for_new_windows = "true" or "false" does not make any difference, in both cases. This is remarkable, since the issue is when starting the application, so one might expect that the value of this variable could cause an issue, while 'save_windowsworkspace' would only matter when the software is closed. But that is not the case, it is the 'save...' which causes (at least correlates) with this bug.
To reproduce Steps to reproduce the behavior:
Set in $HOME/.config/geeqierc.xml the variable save_window_workspace to true, like this: save_window_workspace = "true" Execute this in a shell:
Executing this commands in another shell might provide more information. It shows at least that geeqie is running as X11 application. Note that I use two 4K-Monitors side by side. The window should be in the visible area.
Expected behavior The window should be shown. An Icon should appear in the dash. Neither happens, except for a very short flash in the dash.
Screenshots nothing to see.
Image sources nothing to see.
Error logs or seg. fault files This is the output when started with --debug
Additional context none