Gwenview launches without issue for me — launching via the command-line produces the same warning messages you indicated, however it still launches as expected.
Note that many applications may produce warnings when launched from the command-line. This doesn’t necessarily indicate a problem for the User.
As Gwenview doesn’t launch at all for you, then the problem might be elsewhere – one of the first things to rule out is that the problem is due to local configuration;
Please create a new User account for testing purposes, reboot and login to that account, and launch Gwenview normally and via the command-line to see if the problem persists.
Also note any differences in the warning messages that appear, if any. Report back with your findings.
Please provide your system information formatted according to forum guidelines:
[Mini-HowTo] Provide System Information
Basic details provided by *-fetch type apps might give enough information for someone wishing to buy a computer, however, for Support purposes it’s best to ask your system directly.
Output of the inxi command will generate more useful and detailed information for those who may wish to help:
Command output should be presented as pre-formatted text in accordance with forum guidelines.
Running inxi within a chroot environment
Add --color=0 to the long-form command, or…
Change the short-form command to inxi -zv8c0
Your privacy is respected
[Mini-HowTo] Present code or command output
Note: Grave accent (or, backtick) characters are used.
For inlinecode or to show a single command:
please follow this simple example: code here.
For multi-linecommand output:
place text beween two rows of three (```) backtick characters to form a scrollable text box, or …
use the </> button in the Compose window to achieve the same result.
The empty row between these rows of backtick characters is where to paste any multi-line command output (such as inxi).
An example of a pre-formatted text enclosure:
What is a Quark?
A. In Physics, an elementary particle and fundamental constituent of matter.
B. A character from the Star Trek: "Deep Space Nine" television series.
C. A soft, creamy, usually unsalted cheese traditional to central Europe.
uuuhh … thx - that was easy: removed the “recent folders” which contained some smb shares on my NAS, which of course I dont have when I travel …
in general: not very resilient – shouldn’t a reasonably decent application catch such trivial errors instead of endlessly trying to mount a non-existent share?
That is not up to dolphin, but it may depend on how you mount the Samba shares. If you mount them unconditionally, then dolphin will of course assume that they are always there.
thx Aragorn … well I mount them through systemd automount/mount units assuming this is the proper way to do it? Sometimes I remotely access my NAS via wireguard to copy a file to/from a share … but i assumed the automounts would timeout after a while again? don’t they?
The scenario I’m about to describe doesn’t happen very often – but, it does happen – most recently with LibreOffice, but also with various other applications:
Scenario:
I launch an application and there is no apparent result; I try again, and again with no result.
Then I notice a small vertical line in the center of the screen – maybe 100px high and 2-4px wide – which I initially mistake for screen tearing, and ignore, while working the problem of the application not opening.
After a reboot, the screen tearing artifact is gone (yay, one less thing to be concerned with) and I try to launch the application again, as if the reboot might magically solve the issue.
The screen tearing artifact reappears. This time I hover the mouse over it, and the cursor changes to a sizing icon.
What the…?
I carefully position the mouse (the sizing icon is difficult to make appear again) and finally drag it to the right a little, and to my surprise it reveals the application that I presumes wasn’t starting.
It was starting just fine, only it’s dimensions were too small for me to notice it.
So, carefully check for this scenario in case it’s actually open but not easily visible.
This reminds me of around the time I finally switched to Wayland, > 2½ years ago; I needed to reset the “Special Window Settings” (or it might have been the application ones). I was getting tiny boxes show up with stuff I tried to show from the panel on hover, etc. and popups appearing in the wrong place (separated from the panel). I wonder if this is related? … if it is, removing those customizations will fix it.
