Just found out double-clicking on the desktop to launch dopus is no longer working, dunno if happened with the noted beta version or the previous one.
lmk if you do need any details for troubleshooting 
Works fine here.
1 Like
Make sure Opus isn’t being run elevated, as that will break desktop double-click.
(Elevating from within Opus is fine, but the whole program shouldn’t be launched elevated.)
1 Like
Thanks for the replies, and nah it isn't run elevated -- whenever i dblclick the desktop, i see the mouse pointer changing to the hourglass icon briefly, as usual, but opus isn't launched.
Perhaps it's a hiccup on my laptop when resuming from sleep - will check later today if it does still happen after a reboot, but this never happened before in the past decade or so i've been using dopus.
What about dopus.exe?
non elevated as well (at least according to ProcessHacker)
Have rebooted and it did work fine afterwards. However... then immediately closed dopus, tried to launch it by dblclick again, and no longer worked. It's like if something does remain on memory that does prevent dopusrt from working normally or such, dunno.
And this only happens with 13.16.12? Have you tried installing an older version to check that still works?
Have you rebooted since installing 13.16.12? Give that a try if you haven't.
I've installed the last two betas without having rebooted, so i think we can tell the issue only started happening with either of those two (?)
I thought downgrading could break things, but if that's not the case can try an older beta or the last stable.
Have you installed anything else recently that might have caused it? E.g. Stardock Fences can break desktop double-click, I'm sure there are other things out there that can as well.
1 Like
Well, below is the last stuff i did installed -- the last nodejs had some CVE fixes... but other than that, don't think anything else could have caused it.
PS: I haven't yet tried to install an older beta/version, but i have observed that it did worked once (without a reboot) although then stopped working again, this is becoming interesting...will try to figure things on my own and as a last resort downgrading whenever it becomes really annoying
If it works sometimes and not others (and without Opus being restarted in between), there might be another tool that's also intercepting clicks/double-clicks on the desktop and getting there first, so Opus doesn't get to see the events.
E.g. Fences and DisplayFusion are popular tools that can react to desktop double-clicks and might swallow the events (depending on how they're configured).
(Equally, Opus could cause problems for them if its desktop double-click is turned on but you want them to react to that event instead of Opus. There isn't a good way in Windows to specify which program gets to see the event first, so it comes down to disabling that functionality in everything except the program you want to handle the event.)
1 Like
Thanks Leo for the details.
Btw, i just realized context-menu -> new-lister does have the same behavior than dblclick, failing to launch dopus (if dopus is already running, it does properly work opening a list in a new window)
That sounds like an elevation issue to me.
1 Like
Well, checking through w11's taskman i don't see them elevated.
BTW, when using dblclick / new-lister, i see the "Helper Application" creating dopus.exe and dopusrt.exe, but then those processes disappear:
When i do use the Windows's StartMenu to launch the "dopus app" ...
... dopus is launched normally, but creating an additional helper (dopusrt) process (as already seen on the first screenshot)
is this normal? i don't remember how it was in the past, but looks like if the former "dopusrt" is crashed or something and a new one launched (?)
That's normal.
Have you checked what happens with other versions yet? (And a reboot after installing them to make sure no old files are still in use.) The thread assumes it's due to a change on the Opus side but I don't think you've confirmed that.
Thanks Leo. Alright, downgrade time -- i've just installed 13.16.9, rebooted, then repeated dblclick + close a handful of times and wasn't able to reproduce the issue so far.
Will come back here tomorrow to report how it goes after the usual resuming from sleep etc, i am anyway inclined to think it's something on my side if others cannot repro and you guys don't see any recent changes possibly causing it.
Everything seems fine with 13.16.9, was not able to reproduce it again today.
When i find the time, during the next days, can try to install *.10 & *.11 if that does help to narrow it down.
FWIW, this morning, upon resuming from sleep, happened again with 13.16.9, BUT only once, afterwards working as intended every time, so... unlike with 13.16.12 where the problem was happening 100% of the time, on this one so far only happened once -- dunno if these updates are of any help for you guys to figure things on whether this is coming from dopus, can keep them going if so and as pointed will try the other versions soon, and also the just released v13.17
We've not had any other reports about this so I think whatever is going on is specific to your machine. The symptoms are like something is blocking one process from talking to another sometimes, which would usually be due to either elevation issues or antivirus (or similar) intercepting things. Although why either only happens sometimes and not others is a mystery.
1 Like