starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

komorebi breaks some application functionality when run as admin. #65

New Issue
Closed
opened 2026-01-05 14:48:02 +01:00 by adam · 5 comments
adam commented 2026-01-05 14:48:02 +01:00
Owner
Copy Link

Originally created by @Vernetzt on GitHub (Dec 11, 2021).

Some applications lose certain features related to mouse usage when komorebi is run as administrator. When running the problem applications with the float-rule this behavior disappears but isn't an ideal solution.

Two examples I have found so far have been Adobe Photoshop and YACReaderLibrary. Photoshop loses the ability to use pretty much any tool that requires the mouse to be held down and dragged and probably more I haven't found. YACReaderLibrary loses the ability to use drag&drop features within the main library.

Sadly due to some applications/games that I use requiring to be run as admin means that my only option is to run komorebi elevated as well to manage such windows.

komorebi - 5e3f1cb
Windows 11 - 22000.348

Originally created by @Vernetzt on GitHub (Dec 11, 2021). Some applications lose certain features related to mouse usage when komorebi is run as administrator. When running the problem applications with the `float-rule` this behavior disappears but isn't an ideal solution. Two examples I have found so far have been Adobe Photoshop and [YACReaderLibrary](https://github.com/YACReader/yacreader). Photoshop loses the ability to use pretty much any tool that requires the mouse to be held down and dragged and probably more I haven't found. YACReaderLibrary loses the ability to use drag&drop features within the main library. Sadly due to some applications/games that I use requiring to be run as admin means that my only option is to run komorebi elevated as well to manage such windows. komorebi - 5e3f1cb Windows 11 - 22000.348
adam closed this issue 2026-01-05 14:48:02 +01:00
adam commented 2026-01-05 14:48:02 +01:00
Author
Owner
Copy Link

@Vernetzt commented on GitHub (Dec 11, 2021):

So after messing with it some more I have more information that might be useful. This behavior seems to start when komorebi processes the window again after the initial opening of the application. Sadly the log doesn't indicate any error or difference between komorebi being run as admin or not.

Example steps for my system:

  1. Run komorebi as admin.
  2. Run problem application on the current workspace.
  3. Try and use the mouse functionality mentioned earlier. (works as expected)
  4. Change workspaces or move the application window to trigger komorebi events.
  5. Try to use the above mentioned functionality again. (functionality stops working)

Oddly enough running the problem applications as admin fixes this problem but is probably not an ideal solution overall.

@Vernetzt commented on GitHub (Dec 11, 2021): So after messing with it some more I have more information that might be useful. This behavior seems to start when komorebi processes the window again after the initial opening of the application. Sadly the log doesn't indicate any error or difference between komorebi being run as admin or not. Example steps for my system: 1. Run komorebi as admin. 2. Run problem application on the current workspace. 3. Try and use the mouse functionality mentioned earlier. (works as expected) 4. Change workspaces or move the application window to trigger komorebi events. 5. Try to use the above mentioned functionality again. (functionality stops working) Oddly enough running the problem applications as admin fixes this problem but is probably not an ideal solution overall.
adam commented 2026-01-05 14:48:02 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Feb 2, 2022):

I've finally got some bandwidth to start exploring process elevation related issues now. Is there any chance you could provide a video of what is happening here? I'm struggling to visualize it from the description. 😅

@LGUG2Z commented on GitHub (Feb 2, 2022): I've finally got some bandwidth to start exploring process elevation related issues now. Is there any chance you could provide a video of what is happening here? I'm struggling to visualize it from the description. 😅
adam commented 2026-01-05 14:48:03 +01:00
Author
Owner
Copy Link

@Vernetzt commented on GitHub (Feb 4, 2022):

Sure thing.

The following video shows three examples

  1. Opening YACReader Library as admin with komorebi running as admin and showcasing a drag and drop feature.
  2. Opening YACReader Library as a normal user with komorebi running as admin and showing the feature fail and even crash the program.
  3. Opening YACReader Library as a normal user without komorebi running and showing the feature working as intended.

https://user-images.githubusercontent.com/8786961/152573655-b91202a2-fd22-432b-8f0c-18034a6d033b.mp4

The next video shows what I think to be a similar issue with Photoshop.

  1. Photoshop is running as a normal user while komorebi is running as admin.
  2. Photoshop works as intended until the window is moved, resized, or the workspace is cycled.

https://user-images.githubusercontent.com/8786961/152575203-b791bfc9-01b0-4196-8a3d-913f55da4e1d.mp4

When I first came across this with YACReader I thought it could have been due to me removing the window decorations but after testing with said script off I can observe and replicate the problem in the same way as Photoshop. After the window is moved, resized, or the workspace is cycled it will cause YACReader's drag and drop feature to stop working and even crash sometimes. The reason it appears to happen differently in the first videos second example is because the script resizes the window after removing the decorations to keep the correct position.

I probably should have disabled the script before recording the first video but hopefully the above description and Photoshop example illustrate the problem better.

@Vernetzt commented on GitHub (Feb 4, 2022): Sure thing. The following video shows three examples 1. Opening YACReader Library as admin with komorebi running as admin and showcasing a drag and drop feature. 2. Opening YACReader Library as a normal user with komorebi running as admin and showing the feature fail and even crash the program. 3. Opening YACReader Library as a normal user without komorebi running and showing the feature working as intended. https://user-images.githubusercontent.com/8786961/152573655-b91202a2-fd22-432b-8f0c-18034a6d033b.mp4 The next video shows what I think to be a similar issue with Photoshop. 1. Photoshop is running as a normal user while komorebi is running as admin. 2. Photoshop works as intended until the window is moved, resized, or the workspace is cycled. https://user-images.githubusercontent.com/8786961/152575203-b791bfc9-01b0-4196-8a3d-913f55da4e1d.mp4 When I first came across this with YACReader I thought it could have been due to me removing the window decorations but after testing with said script off I can observe and replicate the problem in the same way as Photoshop. After the window is moved, resized, or the workspace is cycled it will cause YACReader's drag and drop feature to stop working and even crash sometimes. The reason it appears to happen differently in the first videos second example is because the script resizes the window after removing the decorations to keep the correct position. I probably should have disabled the script before recording the first video but hopefully the above description and Photoshop example illustrate the problem better.
adam commented 2026-01-05 14:48:03 +01:00
Author
Owner
Copy Link

@ozokuz commented on GitHub (Aug 27, 2022):

I'm experiencing the same problem but with Minecraft

@ozokuz commented on GitHub (Aug 27, 2022): I'm experiencing the same problem but with Minecraft
adam commented 2026-01-05 14:48:03 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Aug 27, 2022):

@Vernetzt it took a long time, but I think this is now fixed with the latest commit. (which was also tested by @ozokuz 🙏)

@LGUG2Z commented on GitHub (Aug 27, 2022): @Vernetzt it took a long time, but I think this is now fixed with the latest commit. (which was also tested by @ozokuz 🙏)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#65
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?