Qubes and Java/Intellij Dialog Disappearing

432 views
Skip to first unread message

Bahtiar Gadimov

unread,
Feb 23, 2015, 4:43:17 AM2/23/15
to qubes...@googlegroups.com
Hello,

i noticed that some of Java programs are broken when using Qubes. This
issue happens a lot in Intellij IDEA (and it's forks), but AFAIK this
also happens in Eclipse and other Java programs.

#How to reproduce?
1. Install Idea
2. Start coding a Java program.
3. Press Ctrl + Space to complete your code
4. Probably nothing happens or if you are lucky you will see a
flashing dialog, before it disappears

#Workaround

Use a window manager for which you can define window rules, like KWin
(KDE default).

0. (In Kde open "Window Rules Settings")
1. Create a substring match to the Window Class i.e: "my-java-dev-vm"
2. Add a substring match for Windows Title i.e: for Idea it's "win"
3. Set in Arrangement & Access the checkbox "Keep above" to "Force" and "Yes"
4. In Appearance & Fixes set "No titlebar and frame" to "Force" and "yes"
5. Set "Focus stealing prevention" to "Force" and "Extreme" (?)

For more Info about the bug see also
https://youtrack.jetbrains.com/issue/IDEA-101072 . Do not use
-Dide.expansion.hints.enabled=false

I think i had the same issue in other Java programs, at least in
Eclipse, but I'm not sure anymore.

kalkin-

cprise

unread,
Feb 23, 2015, 5:47:12 AM2/23/15
to Bahtiar Gadimov, qubes...@googlegroups.com
This is the same or similar bug I started noticing with Firefox recently:

1. Install an extension like Colorific or Color Transform
2. Click on the down arrow next to the extension's toolbar button to get the menu
3. Hover over elements in the menu... Tooltips will be layered between the Firefox window and the main extension menu; As a result, they are mostly obscured but you can still see a segment of the tooltips peeking out.

Some extensions have all their documentation or important status information in the tooltips. I had to go to another computer to figure out how to use the above extensions.

Markus Kilås

unread,
Feb 23, 2015, 7:22:16 AM2/23/15
to qubes...@googlegroups.com
I can confirm this or similar issue in NetBeans IDE for "Insert code"
(Alt+Insert). The window shows but closes directly. In some rare
situations it is possible to get it to stay but mostly not.

Other similar windows like "Complete code" (Ctrl + Space) works
perfectly in NetBeans IDE.

I wonder if there is a similar workaround also for other window managers...


Cheers,
Markus

Steve Coleman

unread,
Feb 24, 2015, 1:17:05 PM2/24/15
to qubes...@googlegroups.com
I'm not sure if my issue is somehow related to the above, but I just
started using NetBeans and one old issue has reared its ugly head
apparently after some NetBeans cut-n-paste operations. My problem is
apparently bigger than just NetBeans, its just that NetBeans is the
latest issue I have had to deal with. All of them seemed somehow tied to
some VM cut-n-paste operations, and I believe its inter-VM operations
somehow triggering GUI problems. The application GUI disappearing could
be a related side effect.

I use FC20/Xfce/QubesR2/dual-monitor and have had one Work related VM in
particular acting up, I believe when I do a copy-paste operation,
usually with firefox. When it happens the Qubes GUI starts acting up,
with me completely loosing the focus to some random app that will not
give it back. Clicking on various widows gets little or no response, and
sometimes moving the mouse will start some random window scrolling. The
one way I have found to get control back is right clicking on the
desktop switcher, to see some applications alt-menu appear over the
switcher, and then clicking a few more times, I eventually regain
temporary control. Yesterday I started unplugging and re-plugging the
USB mouse which seemed to work also, but its a pain. Once this happens
in a Qubes session I almost certainly need to reboot otherwise it will
just happen again in fairly short order.

So, I just started using NetBeans the other day for a new project and
once it occurs it makes the machine almost unusable. While clicking to
explore the project and source code I didn't have any problems, until I
started copying to and from NetBeans GUI then started having these
issues in the new VM. Now I have two AppVM's that won't play nice, and
once it happens all the VMs seem to have problems with
focus/delays/timeouts and control of the GUI.

I'm not sure if that info helps in the above case, but I thought I
should speak up just in case it is somehow related or might give food
for thought.


Steve

Victor L.

unread,
Apr 8, 2015, 10:28:26 AM4/8/15
to qubes...@googlegroups.com


On Tuesday, February 24, 2015 at 7:17:05 PM UTC+1, steve.coleman wrote:
On 02/23/15 07:22, Markus Kilås wrote:
> On 02/23/2015 10:43 AM, Bahtiar Gadimov wrote:

> I can confirm this or similar issue in NetBeans IDE for "Insert code"
> (Alt+Insert). The window shows but closes directly. In some rare
> situations it is possible to get it to stay but mostly not.


I am having this problem with a Java password dialog launched by Firefox on the official Spanish "tax" website (where you fill out the Java forms and pay your taxes through digital certificate).

There are some webpages that require signing and launch a Java dialog (the one with a greenish/squarish titlebar, as seen on a regular non-Qubes Linux) asking for the certificate warehouse password. On a regular Linux setup (say Ubuntu) that appears, you type the password and then choose the certificate, but here on Qubes with Fedora-20 and XFCE the dialog is missing and so the process stops there, I have to reboot to Ubuntu to do this.

Anybody running into the same problem? any solution?



 

Marek Marczykowski-Górecki

unread,
Apr 8, 2015, 6:15:56 PM4/8/15
to Victor L., qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Apr 08, 2015 at 07:28:25AM -0700, Victor L. wrote:
>
>
> On Tuesday, February 24, 2015 at 7:17:05 PM UTC+1, steve.coleman wrote:
> >
> > On 02/23/15 07:22, Markus Kilås wrote:
> > > On 02/23/2015 10:43 AM, Bahtiar Gadimov wrote:
> >
> > > I can confirm this or similar issue in NetBeans IDE for "Insert code"
> > > (Alt+Insert). The window shows but closes directly. In some rare
> > > situations it is possible to get it to stay but mostly not.
> >
>
>
> I am having this problem with a Java password dialog launched by Firefox on
> the official Spanish "tax" website (where you fill out the Java forms and
> pay your taxes through digital certificate).
>
> There are some webpages that require signing and launch a Java dialog (the
> one with a greenish/squarish titlebar, as seen on a regular non-Qubes
> Linux) asking for the certificate warehouse password. On a regular Linux
> setup (say Ubuntu) that appears, you type the password and then choose the
> certificate, but here on Qubes with Fedora-20 and XFCE the dialog is
> missing and so the process stops there, I have to reboot to Ubuntu to do
> this.
>
> Anybody running into the same problem? any solution?

Maybe the prompt shows below some other window? Does that window
normally (on Ubuntu) has standard decorations, or some custom one?

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVJaiRAAoJENuP0xzK19csmmsH/iFUOMRGqWHFs7yfcorpwL65
LvjOfTSNS6MxU/rkIR6agUztNt1gVGcx31wgA3Xc7YLLTD5u/KcLrq37GK1b8bhv
zMRAjUlt26ZyqGNdUxqKgIRBeeMAszoiygToSLLpPkiXEJTz9r5CyjL31gkXLGCO
IcvtU9HQteULvT8CasW5NqZZPoOsy2prVl3thHMDbuKA/8UQuYygVeh1kq73ywNP
33G0rwQVViNyatdzrD29BHa5sORZtqt/0zKSmUSEmpX7aHqtOUGWOtLeundb4Z33
qJvRmd0IdMsHMM6ntK87oSjr/LHSXCBvl/wRoErvr7jY6U6nf4TlMxy+Yha0Lao=
=dh/q
-----END PGP SIGNATURE-----

Victor L.

unread,
Apr 8, 2015, 7:19:48 PM4/8/15
to qubes...@googlegroups.com, gall...@gmail.com


On Thursday, April 9, 2015 at 12:15:56 AM UTC+2, Marek Marczykowski-Górecki wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Apr 08, 2015 at 07:28:25AM -0700, Victor L. wrote:
>
>
> On Tuesday, February 24, 2015 at 7:17:05 PM UTC+1, steve.coleman wrote:
> >
> > On 02/23/15 07:22, Markus Kilås wrote:
> > > On 02/23/2015 10:43 AM, Bahtiar Gadimov wrote:
> >
> > > I can confirm this or similar issue in NetBeans IDE for "Insert code"
> > > (Alt+Insert). The window shows but closes directly. In some rare
> > > situations it is possible to get it to stay but mostly not.
> >
>
>
> I am having this problem with a Java password dialog launched by Firefox on
> the official Spanish "tax" website (where you fill out the Java forms and
> pay your taxes through digital certificate).
>
> There are some webpages that require signing and launch a Java dialog (the
> one with a greenish/squarish titlebar, as seen on a regular non-Qubes
> Linux) asking for the certificate warehouse password. On a regular Linux
> setup (say Ubuntu) that appears, you type the password and then choose the
> certificate, but here on Qubes with Fedora-20 and XFCE the dialog is
> missing and so the process stops there, I have to reboot to Ubuntu to do
> this.
>
> Anybody running into the same problem? any solution?

Maybe the prompt shows below some other window? Does that window
normally (on Ubuntu) has standard decorations, or some custom one?

No, there is no window/dialog appearing anywhere in Qubes.

Yes, they look like having custom decorations. I have attached two screenshots of the Java dialogs that pop-up in Firefox on Xubuntu and are missing in Qubes (so the website just doesn't work).

The greenish one is the first that appears, its title is "Introduce the password" and the text says "Firefox warehouse password", meaning the master password for the personal certificates.
The bluish one is the one that appears when the password is entered and let's you choose among the digital ceritificates installed in Firefox which one to use for signing. Title says "Security Dialog" and text above is "Select a certificate".

Please let me know if there is any command I could enter or debug action to offer you more information on this. It'd be really awesome to have these certificates just in Qubes.

Thanks!

 
Firefox_security_dialog_certificate_java_dialog.png
Firefox_warehouse_password_certificate_java_dialog.png

Marek Marczykowski-Górecki

unread,
Apr 8, 2015, 7:37:12 PM4/8/15
to Victor L., qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Start the VM in debug mode (qvm-start --debug VMNAME), and watch
messages in /var/log/qubes/guid.VMNAME.log when such window should pop
up. I'm especially interested in messages starting with:
Created
XDestroyWindow
set WM_NORMAL_HINTS
handle_configure_from_vm
process_xevent_configure
force_on_screen
XMoveResizeWindow

There will be a lot of messages, try to collect only those related the
the failed window - for example start "tail -f
/var/log/qubes/guid.VMNAME.log" in one window and just before triggering
failed window, enter few empty lines to separate the messages
(unfortunately there is no timestamps in this log).

You can also check similar messages from qubes-gui service in
/var/log/messages inside of VM.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVJbuhAAoJENuP0xzK19csiVAIAJRWH4+9nC0NUgxCelNnoSAp
a4elEm+SSVQj6ErewbBq1J9QGVejAU/CHYgqlVjLETgfUWRB7grJh1/Fxl1kQD1l
5OAcBxq01TdMoxOHgQXyH5EGamzwIiiBRvtHTE5CeEgk/2ZITsz3wxPRmzXzpQFX
j43DroNR7/40K4eJNzEYoN7P8SI2PxBBL2YrXM2T6xdztnqjyALqKDcghDxiLy9O
6zoiVV57Dx4HGn3UHZf01Jj/lCGg/aUBuL0jNUJZJwOPYUj3aKHxoOZXbtXbgd5G
vqJY6w8mDJJEy4uigL2y5Ar00LAYZcMamG+u7giJvoHPt8yDJ0M8zwKbX/aADhg=
=uHX8
-----END PGP SIGNATURE-----

Victor L.

unread,
Apr 8, 2015, 8:07:26 PM4/8/15
to qubes...@googlegroups.com, gall...@gmail.com


Then I would say these are the messages before and after the dialog should've appeared:

set WM_NORMAL_HINTS for window 0x4600029 to min=0/0, max=0/0, base=0/0, inc=0/0 (flags 0x0)
Created 0x460002a(0x1800001) parent 0x0(0x176) ovr=0 x/y 10/10 w/h 10/10
invalid PMinSize for 0x460002a (0/0)
invalid PMaxSize for 0x460002a (0/0)
invalid PResizeInc for 0x460002a (0/0)
invalid PBaseSize for 0x460002a (0/0)
set WM_NORMAL_HINTS for window 0x460002a to min=0/0, max=0/0, base=0/0, inc=0/0 (flags 0x0)
Created 0x460002b(0x1600007) parent 0x0(0x176) ovr=0 x/y 0/0 w/h 1/1
invalid PMinSize for 0x460002b (0/0)
invalid PMaxSize for 0x460002b (0/0)
invalid PResizeInc for 0x460002b (0/0)
invalid PBaseSize for 0x460002b (0/0)
set WM_NORMAL_HINTS for window 0x460002b to min=0/0, max=0/0, base=0/0, inc=0/0 (flags 0x5)
Created 0x460002c(0x1600008) parent 0x0(0x176) ovr=0 x/y 1/1 w/h 1/1
Created 0x460002d(0x1600020) parent 0x0(0x176) ovr=0 x/y 0/0 w/h 16/16
invalid PMinSize for 0x460002b (0/0)
invalid PMaxSize for 0x460002b (0/0)
invalid PResizeInc for 0x460002b (0/0)
invalid PBaseSize for 0x460002b (0/0)
set WM_NORMAL_HINTS for window 0x460002b to min=0/0, max=0/0, base=0/0, inc=0/0 (flags 0x5)
handle_configure_from_vm, local 0x460000d remote 0x140007f, 1210/900, was 1210/900, ovr=0, xy 1/53, was 1/53
MSG_MFNDUMP for 0x460000d(0x140007f): 1210x900, num_mfn 0x428 off 0x68


And I made another run, with this result:

Created 0x4600028(0x1200001) parent 0x0(0x176) ovr=0 x/y 10/10 w/h 10/10
invalid PMinSize for 0x4600028 (0/0)
invalid PMaxSize for 0x4600028 (0/0)
invalid PResizeInc for 0x4600028 (0/0)
invalid PBaseSize for 0x4600028 (0/0)
set WM_NORMAL_HINTS for window 0x4600028 to min=0/0, max=0/0, base=0/0, inc=0/0 (flags 0x0)
Created 0x4600029(0x1800001) parent 0x0(0x176) ovr=0 x/y 10/10 w/h 10/10
invalid PMinSize for 0x4600029 (0/0)
invalid PMaxSize for 0x4600029 (0/0)
invalid PResizeInc for 0x4600029 (0/0)
invalid PBaseSize for 0x4600029 (0/0)
set WM_NORMAL_HINTS for window 0x4600029 to min=0/0, max=0/0, base=0/0, inc=0/0 (flags 0x0)
Created 0x460002a(0x1600007) parent 0x0(0x176) ovr=0 x/y 0/0 w/h 1/1
invalid PMinSize for 0x460002a (0/0)
invalid PMaxSize for 0x460002a (0/0)
invalid PResizeInc for 0x460002a (0/0)
invalid PBaseSize for 0x460002a (0/0)
set WM_NORMAL_HINTS for window 0x460002a to min=0/0, max=0/0, base=0/0, inc=0/0 (flags 0x5)
Created 0x460002b(0x1600008) parent 0x0(0x176) ovr=0 x/y 1/1 w/h 1/1
Created 0x460002c(0x1600020) parent 0x0(0x176) ovr=0 x/y 0/0 w/h 16/16
invalid PMinSize for 0x460002a (0/0)
invalid PMaxSize for 0x460002a (0/0)
invalid PResizeInc for 0x460002a (0/0)
invalid PBaseSize for 0x460002a (0/0)
set WM_NORMAL_HINTS for window 0x460002a to min=0/0, max=0/0, base=0/0, inc=0/0 (flags 0x5)


Is there anything suspicious there? In both cases I've grep'ed away the "shmimage for" and "do_shm_update" messages only.


You may be able to see the problem too, even with a generic certificate, the url is this one:
https://www1.agenciatributaria.gob.es/static_files/common/internet/dep/aplicaciones/ov/ie52020a.html

A form appears first and then after a second, there appears on top only a bluish box that says "Cargando entorno" and a wheel starts spinning, that's when the dialog should be up front.

Thanks a lot!!
 

Vít Šesták

unread,
Jun 3, 2015, 5:38:49 AM6/3/15
to qubes...@googlegroups.com
I am getting some similar issues with IntelliJ IDEA on Qubes 3.0-RC1. The Ctrl+space popup seems to work correctly, but there are some other popups that don't work (appear and them immediatelly disappear unless you are lucky), no matter how they are invoked (menu or keyboard shotrcut):
* Ctrl+N (search class)
* Ctrl+Shift+N (search file)
There is, however, one similar popup that seems to always work:
* Double shift (search everywhere)

All these popups have no window decoration on bare-metal Ubuntu. However, Qubes adds a decoration to some of them (i.e. search class and search file, see idea-autocomplete-ok.png) and those don't work most of time. For Search everywhere, no decoration (except the tiny VM-color border) is added, see idea-search-everywhere.png. It looks like the window titlebar breaks the popup :D Well, seriously: They are probably different types of a window, one of them works correctly, the while second type does not.

There are also two minor issues with adding the window titlebar:
1. It breaks some position calculations, so the autocomplete subwindow overlaps the text input box, see idea-autocomplete-overlap.png . This is not critical in IDEA, because IDEA recalculates the subwindow position when I start typing. It might be more serious in a different app, though.
2. It supports some operations that were not intended to do. See maximized popup in idea-funny-maximize.png attachment.

It seems that language is irelevant (happens in Scala and Ruby projects, haven't try other types of project). I've tried only IDEA Ultimate (both 30-days trial and registered version) in versions 14.0.4 and 14.1.3, but the same is likely to apply for IDEA Community edition, RubyMine, PyCharm, PHPStorm, WebStorm, CLion and so on, as the GUI base is the same for all those editions.

If it is likely to be useful, I can somehow gather details about these two types of windows, e.g. through xprop or the debugging options.

Regards,
Vít Šesták 'v6ak'
idea-autocomplete-overlap.png
idea-funny-maximize.png
idea-search-everywhere.png
idea-autocomplete-ok.png

Markus Kilås

unread,
Aug 12, 2015, 9:00:27 AM8/12/15
to qubes...@googlegroups.com
I have looked into the source code of NetBeans IDE which has the problem
with the "Insert Code..." dialog most of time times directly
disappearing and I think I have tracked down the issue to be related to
that the window loses focus.

I have created a small Java application reproducing the issue. Basically
the code is the following to to display a dialog window and in order to
have it closed automagically when somebody clicks anywhere outside the
dialog a FocusListener is registered and closes the dialog on "focus
lost". This works as expected in for instance a (non-Qubes) Ubuntu,
while in Qubes most of the time the window almost directly loses focus
and is closed:

---
final JDialog popupWindow = new JDialog(this, false);
popupWindow.setTitle("PopupWin");
popupWindow.add(new JLabel("This is the popup"));
popupWindow.setLocation(100, 100);
popupWindow.pack();

popupWindow.addFocusListener(new FocusAdapter() {
@Override
public void focusLost(FocusEvent e) {
// Hide popup when focus is lost
System.out.println("Focus lost event: " + e);
popupWindow.setVisible(false);
popupWindow.dispose();
}
});

System.out.println();
System.out.println("Show");
popupWindow.setVisible(true);
---

Full source: https://github.com/netmackan/qubes-java-focus-issue

Any ideas about what could be the issue at Qubes side?

I guess I should now run the application with the AppVM in debug mode
and collect the logs.

Cheers,
Markus

Markus Kilås

unread,
Aug 12, 2015, 12:58:59 PM8/12/15
to qubes...@googlegroups.com
Below are logs from when the window should be displayed.


From appvm:/var/log/messages from the time of pressing Ctrl+S until the
"focus lost event" (approximately).
---
Aug 12 18:31:06 localhost qubes-gui: received message type 124 for 0x1200007
Aug 12 18:31:06 localhost qubes-gui: Create for 0x12001a8 class 0x1
Aug 12 18:31:06 localhost qubes-gui: Protocol take_focus supported for
Window 0x12001a8
Aug 12 18:31:06 localhost qubes-gui: Received WMHints without input hint
set for Window 0x12001a8
Aug 12 18:31:06 localhost qubes-gui: Create for 0x12001ae class 0x1
Aug 12 18:31:06 localhost qubes-gui: handle property WM_HINTS for window
0x12001a8
Aug 12 18:31:06 localhost qubes-gui: Received WMHints without input hint
set for Window 0x12001a8
Aug 12 18:31:06 localhost qubes-gui: handle property WM_NORMAL_HINTS for
window 0x12001a8
Aug 12 18:31:06 localhost qubes-gui: handle property WM_NORMAL_HINTS for
window 0x12001a8
Aug 12 18:31:06 localhost qubes-gui: handle configure event 0x12001a8
w=108 h=15 ovr=0
Aug 12 18:31:06 localhost qubes-gui: received message type 124 for 0x1200007
Aug 12 18:31:06 localhost qubes-gui: handle property WM_NORMAL_HINTS for
window 0x12001a8
Aug 12 18:31:06 localhost qubes-gui: handle property WM_NORMAL_HINTS for
window 0x12001a8
Aug 12 18:31:06 localhost qubes-gui: handle property _MOTIF_WM_HINTS for
window 0x12001a8
Aug 12 18:31:06 localhost qubes-gui: handle property WM_HINTS for window
0x12001a8
Aug 12 18:31:06 localhost qubes-gui: Received input hint 0x0 for Window
0x12001a8
Aug 12 18:31:06 localhost qubes-gui: handle configure event 0x12001a8
w=108 h=15 ovr=0
Aug 12 18:31:06 localhost qubes-gui: MAP for window 0x12001a8
Aug 12 18:31:06 localhost qubes-gui: got wmname=PopupWin
Aug 12 18:31:06 localhost qubes-gui: received message type 134 for 0x12001a8
Aug 12 18:31:06 localhost qubes-gui: configure msg, x/y 103 123 (was 100
100), w/h 108 15 (was 108 15)
Aug 12 18:31:06 localhost qubes-gui: received message type 128 for 0x1200007
Aug 12 18:31:06 localhost qubes-gui: 0x1200007 lost focus
Aug 12 18:31:06 localhost qubes-gui: handle configure event 0x12001a8
w=108 h=15 ovr=0
Aug 12 18:31:06 localhost qubes-gui: received message type 142 for 0x0
Aug 12 18:31:06 localhost qubes-gui: received message type 128 for 0x12001a8
Aug 12 18:31:06 localhost qubes-gui: WM_TAKE_FOCUS sent for 0x12001a8
Aug 12 18:31:06 localhost qubes-gui: 0x12001a8 raised
Aug 12 18:31:06 localhost qubes-gui: received message type 124 for 0x12001a8
Aug 12 18:31:06 localhost qubes-gui: received message type 126 for 0x1400007
Aug 12 18:31:06 localhost qubes-gui: received message type 126 for 0x1400007
... My note: repeated 38 additional times and then:
Aug 12 18:31:07 localhost qubes-gui: received message type 128 for 0x12001a8
Aug 12 18:31:07 localhost qubes-gui: 0x12001a8 lost focus
Aug 12 18:31:07 localhost qubes-gui: received message type 142 for 0x0
Aug 12 18:31:07 localhost qubes-gui: received message type 128 for 0x1400007
Aug 12 18:31:07 localhost qubes-gui: WM_TAKE_FOCUS sent for 0x1400007
Aug 12 18:31:07 localhost qubes-gui: 0x1400007 raised
Aug 12 18:31:07 localhost qubes-gui: received message type 125 for 0x1400007
Aug 12 18:31:07 localhost qubes-gui: send buttonevent, win 0x1400007
type=4 button=1
Aug 12 18:31:07 localhost qubes-gui: handle configure event 0x1400007
w=1887 h=1484 ovr=0
Aug 12 18:31:07 localhost qubes-gui: handle property _NET_WM_USER_TIME
for window 0x1400007
Aug 12 18:31:07 localhost qubes-gui: received message type 125 for 0x1400007
Aug 12 18:31:07 localhost qubes-gui: send buttonevent, win 0x1400007
type=5 button=1
---

While doing the same thing (not at the same time though), the following
output was recived in dom0:/var/log/qubes/guid.development.log:
---
Created 0x4a00432(0x12003bb) parent 0x0(0x176) ovr=0 x/y 100/100 w/h 1/1
invalid PMinSize for 0x4a00432 (0/0)
invalid PMaxSize for 0x4a00432 (0/0)
invalid PResizeInc for 0x4a00432 (0/0)
invalid PBaseSize for 0x4a00432 (0/0)
set WM_NORMAL_HINTS for window 0x4a00432 to min=0/0, max=0/0, base=0/0,
inc=0/0 (flags 0x5)
Created 0x4a00433(0x12003c1) parent 0x0(0x176) ovr=0 x/y 0/0 w/h 16/16
invalid PMinSize for 0x4a00432 (0/0)
invalid PMaxSize for 0x4a00432 (0/0)
invalid PResizeInc for 0x4a00432 (0/0)
invalid PBaseSize for 0x4a00432 (0/0)
set WM_NORMAL_HINTS for window 0x4a00432 to min=0/0, max=0/0, base=0/0,
inc=0/0 (flags 0x5)
invalid PMinSize for 0x4a00432 (0/0)
invalid PMaxSize for 0x4a00432 (0/0)
invalid PResizeInc for 0x4a00432 (0/0)
invalid PBaseSize for 0x4a00432 (0/0)
set WM_NORMAL_HINTS for window 0x4a00432 to min=0/0, max=0/0, base=0/0,
inc=0/0 (flags 0x5)
handle_configure_from_vm, local 0x4a00432 remote 0x12003bb, 108/15, was
1/1, ovr=0, xy 100/100, was 100/100
XMoveResizeWindow local 0x4a00432 remote 0x12003bb, xy 100 100
(vm_window is 100 100) wh 108 15
process_xevent_configure(synth 0) local 0x4a00432 remote 0x12003bb,
108/15, was 108/15, xy 100/100 was 100/100
MSG_MFNDUMP for 0x4a00432(0x12003bb): 3200x1800, num_mfn 0x15fa off 0x10
invalid PMinSize for 0x4a00432 (0/0)
invalid PMaxSize for 0x4a00432 (0/0)
invalid PResizeInc for 0x4a00432 (0/0)
invalid PBaseSize for 0x4a00432 (0/0)
set WM_NORMAL_HINTS for window 0x4a00432 to min=0/0, max=0/0, base=0/0,
inc=0/0 (flags 0x5)
invalid PMinSize for 0x4a00432 (0/0)
invalid PMaxSize for 0x4a00432 (0/0)
invalid PResizeInc for 0x4a00432 (0/0)
invalid PBaseSize for 0x4a00432 (0/0)
set WM_NORMAL_HINTS for window 0x4a00432 to min=0/0, max=0/0, base=0/0,
inc=0/0 (flags 0x5)
handle_configure_from_vm, local 0x4a00432 remote 0x12003bb, 108/15, was
108/15, ovr=0, xy 100/100, was 100/100
MSG_MFNDUMP for 0x4a00432(0x12003bb): 108x15, num_mfn 0x2 off 0x398
MSG_MFNDUMP for 0x4a00432(0x12003bb): 108x15, num_mfn 0x2 off 0x398
set title for window 0x4a00432
shmimage for 0x4a00432(remote 0x12003bb), x: 0, y: 0, w: 108, h: 15
do_shm_update for 0x4a00432(remote 0x12003bb), after border calc: x=0,
y=0, w=108, h=15
shmimage for 0x4a00432(remote 0x12003bb), x: 0, y: 0, w: 108, h: 15
do_shm_update for 0x4a00432(remote 0x12003bb), after border calc: x=0,
y=0, w=108, h=15
process_xevent_configure(synth 0) local 0x4a00432 remote 0x12003bb,
108/15, was 108/15, xy 3/23 was 100/100
process_xevent_configure(synth 1) local 0x4a00432 remote 0x12003bb,
108/15, was 108/15, xy 103/123 was 100/100
do_shm_update for 0x4a00432(remote 0x12003bb), after border calc: x=0,
y=0, w=108, h=15
handle_configure_from_vm, local 0x4a00432 remote 0x12003bb, 108/15, was
108/15, ovr=0, xy 103/123, was 103/123
MSG_MFNDUMP for 0x4a00432(0x12003bb): 108x15, num_mfn 0x2 off 0x398
shmimage for 0x4a00432(remote 0x12003bb), x: 0, y: 0, w: 108, h: 15
do_shm_update for 0x4a00432(remote 0x12003bb), after border calc: x=0,
y=0, w=108, h=15
shmimage for 0x4a00259(remote 0x1200007), x: 6, y: 29, w: 1033, h: 538
do_shm_update for 0x4a00259(remote 0x1200007), after border calc: x=6,
y=29, w=1033, h=538
shmimage for 0x4a0000d(remote 0x1400007), x: 520, y: 1457, w: 17, h: 27
do_shm_update for 0x4a0000d(remote 0x1400007), after border calc:
x=520, y=1457, w=17, h=27
shmimage for 0x4a0020c(remote 0x1a00034), x: 707, y: 40, w: 183, h: 36
... and a few more shm stuff
---

Regards,
Markus

>
> Cheers,
> Markus
>

Reply all
Reply to author
Forward
0 new messages