Mouse Actions Fail In Manager Modal Windows

Discussions related to using VirtualBox on Linux hosts.
Post Reply
vindicator
Posts: 10
Joined: 30. Dec 2010, 08:41
Primary OS: MS Windows Vista
VBox Version: PUEL
Guest OSses: 7;Vista;XP;Ubuntu1010;OpenSUSE1103

Mouse Actions Fail In Manager Modal Windows

Post by vindicator »

Virtualbox: 6.1.26r145957
Archlinux
KDE plasma 5.22.4

Start fresh by clearing virtualbox ~/.config/ files
Open virtualbox manager
Click on "Preferences"
Click on drop-down for "Default Machine Folder"
Select Other
*Try* to use any mouse action. Even clicking "Cancel".

Mouse actions simply do not work in that window and other similar "Select Folder" windows, other than being able to drag the scroll bars.
I'm forced to use the keyboard to navigate the window, though even then, the visuals make it next to impossible to know where my selection is.
It's actually an issue that's been going on for probably over a year, but I've only just now "had it" enough to search on it and then post about it.
fth0
Volunteer
Posts: 5661
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Mouse Actions Fail In Manager Modal Windows

Post by fth0 »

FWIW, it works for me on my Linux Mint 20 host with the Cinnamon desktop.

Perhaps some incompatibility between QT 5.15 of KDE Plasma 5.22.4 and the VirtualBox Manager? What did you change "probably over a year" ago?
vindicator
Posts: 10
Joined: 30. Dec 2010, 08:41
Primary OS: MS Windows Vista
VBox Version: PUEL
Guest OSses: 7;Vista;XP;Ubuntu1010;OpenSUSE1103

Re: Mouse Actions Fail In Manager Modal Windows

Post by vindicator »

The reply notification sent to my spam-email was put in the spam folder, so I missed your reply until now. That "forum" address is now in the safe list.
Though I sure would like it if Oracle would follow the RFC for allowable email address characters and accept the '+' character. It isn't a problem that a tech company should even be making. Surprisingly, lots of companies fail in this regard. Microsoft allows it in some cases, but I've encountered a case where they don't accept it either, and when I mentioned it, they STILL have yet to correct their problem.

"what did I change"... heh, that's a good one. It'd probably be safe to say "everything".
I know I rebuilt my root system earlier this year because of some mess-ups. My ~/ is on another drive.
As I stated, I cleared out the cache for vbox to have a fresh start with it, but to take it even further, I just created a new user account altogether on my system, switched to that user, did the same steps (except for cache clearing obviously), and the same behavior was exhibited.
fth0
Volunteer
Posts: 5661
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Mouse Actions Fail In Manager Modal Windows

Post by fth0 »

I'd suggest to experiment with the KDE settings regarding visuals, for example things like dark mode vs light mode, foreground and background colors, etc. Does anything make a difference?
vindicator
Posts: 10
Joined: 30. Dec 2010, 08:41
Primary OS: MS Windows Vista
VBox Version: PUEL
Guest OSses: 7;Vista;XP;Ubuntu1010;OpenSUSE1103

Re: Mouse Actions Fail In Manager Modal Windows

Post by vindicator »

? Why would changing "visuals" have ANY effect on whether or not mouse-clicking the cancel button action is taken?
I see the button clear-as-day, as well as my mouse cursor.
It's one thing for an action simply not registering, and it's a whole other when I'm tabbing through and can't see a selection because of a visual setting.
One has nothing to do with the other.

The whole point of this post, as stated in the title, is I'd like to be able to use my mouse.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Mouse Actions Fail In Manager Modal Windows

Post by scottgus1 »

Vindicator, you came here for help. Word to the wise: It is better to do what you're asked, so we can help you, even if you don't understand what or why you're being asked. Do first, ask for clarification after reporting what happened.
vindicator
Posts: 10
Joined: 30. Dec 2010, 08:41
Primary OS: MS Windows Vista
VBox Version: PUEL
Guest OSses: 7;Vista;XP;Ubuntu1010;OpenSUSE1103

Re: Mouse Actions Fail In Manager Modal Windows

Post by vindicator »

I really wasn't looking for "help". If anything, it's more of a bug-report.
I'm very interested to know the logic behind that thinking though. If you have any insight yourself as to why color-coordination would have any effect on whether or not a button-click event isn't being handled, I'm all ears.
And if it is somehow visuals, then I'd look for more guidance as to what visual changes I should be making.
AND when it comes down to the same scenario playing out with a fresh user account, with NO modifications, would you still want to go with "visuals"?
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Mouse Actions Fail In Manager Modal Windows

Post by scottgus1 »

Report the results first, please.

I have a very vague idea of what the concept is supposed to show, if anything does show, but I'm no Linux guru. The results of the test may help fth0, who knows a heck of a lot more than I do, figure out what's up.
fth0
Volunteer
Posts: 5661
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Mouse Actions Fail In Manager Modal Windows

Post by fth0 »

Well, you described two independent problems with the same dialog, one mouse-related and one keyboard-related, and I tried to address the easier one first, because it could be a well-known issue, and would make your workaround easier to use.

Regarding the mouse-related problem, you could perhaps use xev to analyze. BTW, do you use X11 or Wayland?
vindicator
Posts: 10
Joined: 30. Dec 2010, 08:41
Primary OS: MS Windows Vista
VBox Version: PUEL
Guest OSses: 7;Vista;XP;Ubuntu1010;OpenSUSE1103

Re: Mouse Actions Fail In Manager Modal Windows

Post by vindicator »

Ugh, I've got a scheduled btrfs scan going right now, so my system is going to be laggy for the next 4+ hours.
I am on X11 for sure. Every time I gave wayland a chance, I'd be more than disappointed. It simply is not usable in the least. I have some reports submitted about that.

Yeah, we don't have to worry about the visuals. I think I use breeze dark and have had to manually edit the css for gnucash so it works well, so I know if I need to do something about that.

I went ahead and ran xev and wasn't surprised to not see any events... EXCEPT, it wasn't even registered for when I'd drag the scrollbar (which DOES work), so I don't know what's up with that. It's my first time using the program as well, so maybe I'm missing something.

I started with opening vbox, bringing up the "select folder" window.
Then I 'xprop' on that window:

Code: Select all

_NET_WM_ICON_GEOMETRY(CARDINAL) = 1335, 1044, 115, 36
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE
_KDE_NET_WM_FRAME_STRUT(CARDINAL) = 0, 0, 29, 0
_NET_FRAME_EXTENTS(CARDINAL) = 0, 0, 29, 0
_NET_WM_DESKTOP(CARDINAL) = 0
_KDE_NET_WM_ACTIVITIES(STRING) = "5a4ef4a0-2927-4845-b3a9-ec9c0086eb84"
WM_STATE(WM_STATE):
		window state: Normal
		icon window: 0x0
_NET_WM_USER_TIME(CARDINAL) = 370025131
_NET_WM_STATE(ATOM) = _NET_WM_STATE_MODAL
WM_TRANSIENT_FOR(WINDOW): window id # 0x5c00008
_NET_WM_ICON_NAME(UTF8_STRING) = 
XdndAware(ATOM) = BITMAP
WM_NAME(STRING) = "Select Folder"
_NET_WM_NAME(UTF8_STRING) = "Select Folder"
_KDE_NET_WM_USER_CREATION_TIME(CARDINAL) = 370025096
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x3, 0x3e, 0x7e, 0x0, 0x0
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DIALOG, _NET_WM_WINDOW_TYPE_NORMAL
_XEMBED_INFO(_XEMBED_INFO) = 0x0, 0x1
WM_CLIENT_LEADER(WINDOW): window id # 0x5c00008
WM_HINTS(WM_HINTS):
		Client accepts input or input focus: True
		window id # of group leader: 0x5c00008
WM_CLIENT_MACHINE(STRING) = "computerName"
_NET_WM_PID(CARDINAL) = 1166166
_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 96472694
WM_CLASS(STRING) = "VirtualBox", "VirtualBox"
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST, _NET_WM_CONTEXT_HELP
WM_NORMAL_HINTS(WM_SIZE_HINTS):
		user specified location: 528, 183
		user specified size: 844 by 598
		program specified minimum size: 314 by 252
		window gravity: Static
Then 'xev -id 0x5c00008', and did a bunch of clicking around and dragging those scroll bars:

Code: Select all

ColormapNotify event, serial 18, synthetic NO, window 0x5c00008,
    colormap 0x20, new NO, state ColormapUninstalled

ColormapNotify event, serial 18, synthetic NO, window 0x5c00008,
    colormap 0x20, new NO, state ColormapInstalled

ColormapNotify event, serial 18, synthetic NO, window 0x5c00008,
    colormap 0x20, new NO, state ColormapUninstalled

ColormapNotify event, serial 18, synthetic NO, window 0x5c00008,
    colormap 0x20, new NO, state ColormapInstalled

ColormapNotify event, serial 18, synthetic NO, window 0x5c00008,
    colormap 0x20, new NO, state ColormapUninstalled

ColormapNotify event, serial 18, synthetic NO, window 0x5c00008,
    colormap 0x20, new NO, state ColormapInstalled
The only line that happened was the initial ColormapNotify when I started it. The others only came up as I was closing it out (manually, no mouse), then closing the other windows, and switching back to konsole.
vindicator
Posts: 10
Joined: 30. Dec 2010, 08:41
Primary OS: MS Windows Vista
VBox Version: PUEL
Guest OSses: 7;Vista;XP;Ubuntu1010;OpenSUSE1103

Re: Mouse Actions Fail In Manager Modal Windows

Post by vindicator »

After learning a little more about xev, I tried it again differently...
xwininfo:

Code: Select all

xwininfo: Window id: 0x5600416 "Select Folder"

  Absolute upper-left X:  528
  Absolute upper-left Y:  183
  Relative upper-left X:  0
  Relative upper-left Y:  0
  Width: 844
  Height: 598
  Depth: 24
  Visual: 0xe2
  Visual Class: TrueColor
  Border width: 0
  Class: InputOutput
  Colormap: 0x5600005 (not installed)
  Bit Gravity State: NorthWestGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsViewable
  Override Redirect State: no
  Corners:  +528+183  -548+183  -548-299  +528-299
  -geometry 844x598+528+183
xev:

Code: Select all

EnterNotify event, serial 18, synthetic NO, window 0x5600416,
    root 0x137, subw 0x560042e, time 373273450, (18,571), root:(546,754),
    mode NotifyNormal, detail NotifyNonlinearVirtual, same_screen YES,
    focus NO, state 16

KeymapNotify event, serial 18, synthetic NO, window 0x0,
    keys:  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

EnterNotify event, serial 18, synthetic NO, window 0x5600416,
    root 0x137, subw 0x0, time 373273464, (45,588), root:(573,771),
    mode NotifyNormal, detail NotifyInferior, same_screen YES,
    focus NO, state 16

KeymapNotify event, serial 18, synthetic NO, window 0x0,
    keys:  55  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

LeaveNotify event, serial 18, synthetic NO, window 0x5600416,
    root 0x137, subw 0x0, time 373273472, (64,598), root:(592,781),
    mode NotifyNormal, detail NotifyNonlinear, same_screen YES,
    focus NO, state 16

EnterNotify event, serial 18, synthetic NO, window 0x5600416,
    root 0x137, subw 0x0, time 373273984, (210,597), root:(738,780),
    mode NotifyNormal, detail NotifyNonlinear, same_screen YES,
    focus NO, state 16

KeymapNotify event, serial 18, synthetic NO, window 0x0,
    keys:  55  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

LeaveNotify event, serial 18, synthetic NO, window 0x5600416,
    root 0x137, subw 0x0, time 373274214, (212,587), root:(740,770),
    mode NotifyNormal, detail NotifyInferior, same_screen YES,
    focus NO, state 16

LeaveNotify event, serial 18, synthetic NO, window 0x5600416,
    root 0x137, subw 0x560042e, time 373274508, (213,581), root:(741,764),
    mode NotifyGrab, detail NotifyVirtual, same_screen YES,
    focus NO, state 272

FocusIn event, serial 18, synthetic NO, window 0x5600416,
    mode NotifyNormal, detail NotifyNonlinear

KeymapNotify event, serial 18, synthetic NO, window 0x0,
    keys:  55  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

EnterNotify event, serial 18, synthetic NO, window 0x5600416,
    root 0x137, subw 0x560042e, time 373274510, (213,581), root:(741,764),
    mode NotifyUngrab, detail NotifyVirtual, same_screen YES,
    focus YES, state 272

KeymapNotify event, serial 18, synthetic NO, window 0x0,
    keys:  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

ColormapNotify event, serial 18, synthetic NO, window 0x5600416,
    colormap 0x5600005, new NO, state ColormapInstalled

PropertyNotify event, serial 18, synthetic NO, window 0x5600416,
    atom 0x16b (_NET_WM_STATE), time 373274521, state PropertyNewValue

PropertyNotify event, serial 19, synthetic NO, window 0x5600416,
    atom 0x175 (_NET_WM_USER_TIME), time 373274540, state PropertyNewValue

EnterNotify event, serial 20, synthetic NO, window 0x5600416,
    root 0x137, subw 0x0, time 373275066, (217,553), root:(745,736),
    mode NotifyNormal, detail NotifyInferior, same_screen YES,
    focus YES, state 16

KeymapNotify event, serial 20, synthetic NO, window 0x0,
    keys:  55  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

LeaveNotify event, serial 20, synthetic NO, window 0x5600416,
    root 0x137, subw 0x0, time 373275105, (216,544), root:(744,727),
    mode NotifyNormal, detail NotifyInferior, same_screen YES,
    focus YES, state 16

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x175 (_NET_WM_USER_TIME), time 373278044, state PropertyNewValue

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x175 (_NET_WM_USER_TIME), time 373278826, state PropertyNewValue

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x175 (_NET_WM_USER_TIME), time 373279375, state PropertyNewValue

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x175 (_NET_WM_USER_TIME), time 373279955, state PropertyNewValue

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x175 (_NET_WM_USER_TIME), time 373282879, state PropertyNewValue

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x175 (_NET_WM_USER_TIME), time 373286143, state PropertyNewValue

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x175 (_NET_WM_USER_TIME), time 373287505, state PropertyNewValue

EnterNotify event, serial 20, synthetic NO, window 0x5600416,
    root 0x137, subw 0x0, time 373288765, (718,548), root:(1246,731),
    mode NotifyNormal, detail NotifyInferior, same_screen YES,
    focus YES, state 16

KeymapNotify event, serial 20, synthetic NO, window 0x0,
    keys:  55  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

LeaveNotify event, serial 20, synthetic NO, window 0x5600416,
    root 0x137, subw 0x0, time 373288827, (727,554), root:(1255,737),
    mode NotifyNormal, detail NotifyInferior, same_screen YES,
    focus YES, state 16

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x175 (_NET_WM_USER_TIME), time 373289176, state PropertyNewValue

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x175 (_NET_WM_USER_TIME), time 373290670, state PropertyNewValue

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x175 (_NET_WM_USER_TIME), time 373293412, state PropertyNewValue

UnmapNotify event, serial 20, synthetic NO, window 0x5600416,
    event 0x5600416, window 0x5600416, from_configure NO

FocusOut event, serial 20, synthetic NO, window 0x5600416,
    mode NotifyNormal, detail NotifyNonlinear

FocusIn event, serial 20, synthetic NO, window 0x5600416,
    mode NotifyNormal, detail NotifyPointer

KeymapNotify event, serial 20, synthetic NO, window 0x0,
    keys:  55  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

LeaveNotify event, serial 20, synthetic NO, window 0x5600416,
    root 0x137, subw 0x560042e, time 373293414, (772,575), root:(1300,758),
    mode NotifyNormal, detail NotifyVirtual, same_screen YES,
    focus YES, state 16

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x148 (WM_STATE), time 373293416, state PropertyDelete

ColormapNotify event, serial 20, synthetic NO, window 0x5600416,
    colormap 0x5600005, new NO, state ColormapUninstalled

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x1e6 (_NET_WM_DESKTOP), time 373293425, state PropertyDelete

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x16b (_NET_WM_STATE), time 373293425, state PropertyNewValue

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x1c7 (_KDE_NET_WM_USER_CREATION_TIME), time 373293425, state PropertyDelete

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x189 (_NET_FRAME_EXTENTS), time 373293425, state PropertyDelete

PropertyNotify event, serial 20, synthetic NO, window 0x5600416,
    atom 0x188 (_KDE_NET_WM_FRAME_STRUT), time 373293425, state PropertyDelete

ReparentNotify event, serial 20, synthetic NO, window 0x5600416,
    event 0x5600416, window 0x5600416, parent 0x137,
    (528,183), override NO

ColormapNotify event, serial 25, synthetic NO, window 0x5600416,
    colormap 0x5600005, new NO, state ColormapInstalled

ColormapNotify event, serial 25, synthetic NO, window 0x5600416,
    colormap 0x5600005, new NO, state ColormapUninstalled
So stuff WAS registering as "happening" as I was clicking, but just wasn't "doing" anything. I haven't looked at what this all means yet.
fth0
Volunteer
Posts: 5661
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Mouse Actions Fail In Manager Modal Windows

Post by fth0 »

I can give you a recipe of what I just tried myself:

First, I used xwininfo -tree to get the structure of the dialog window. Then I used watch -n 1 xdotool getmouselocation to identify the Cancel button. Third, I used xev -id <button id> to observe the events: EnterNotify and LeaveNotify events when moving the mouse pointer in and out, no event for pressing the mouse button, but a whole sequence for relasing it, starting with FocusOut and FocusIn events.

I don't understand all the details, but it's possible that one has to simultaneously watch all parents of the button, including the 1x1 windows, because events may get propagated somehow along the chain. If you have another dialog in the VirtualBox Manager where "the same" button works as expected, this could be the base for a comparison.

But I don't know if its worth the effort. Perhaps it's easier to just create a ticket in the Bugtracker.
vindicator
Posts: 10
Joined: 30. Dec 2010, 08:41
Primary OS: MS Windows Vista
VBox Version: PUEL
Guest OSses: 7;Vista;XP;Ubuntu1010;OpenSUSE1103

Re: Mouse Actions Fail In Manager Modal Windows

Post by vindicator »

Prior to retesting with your steps and submitting a bug, I downloaded the dev snapshot (6.1.97-r146677) and that "Select Folder" aspect works fine.
The design is definitely visibly different than what it is currently.
I guess the question becomes, "when will that snapshot get pushed into production?".
fth0
Volunteer
Posts: 5661
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Mouse Actions Fail In Manager Modal Windows

Post by fth0 »

Before or after Christmas, but I cannot tell you the year. ;)
Post Reply