xpra icon
Bug tracker and wiki

Opened 6 years ago

Closed 6 years ago

Last modified 4 years ago

#1 closed defect (wontfix)

context menus of applications are sometimes drawn outside visible area

Reported by: Timo Juhani Lindfors Owned by: Antoine Martin
Priority: major Milestone: 0.0.7.x
Component: client Version:
Keywords: Cc:

Description

This is probably a known problem but I could not find a bug report about it.

If I right-click an URL in quassel IRC client I get a context menu. If the URL is on the last line of the window then the last entries of the context menu are drawn outside the visible area of the desktop :-)

I need to manually move the window and then right-click to be able to access the menu.

Attachments (1)

testcase1.png (40.1 KB) - added by Timo Juhani Lindfors 6 years ago.
see how the "Copy Link Address" context menu entry is not visible at all (it is below visiable area)

Download all attachments as: .zip

Change History (5)

Changed 6 years ago by Timo Juhani Lindfors

Attachment: testcase1.png added

see how the "Copy Link Address" context menu entry is not visible at all (it is below visiable area)

comment:1 Changed 6 years ago by Antoine Martin

Milestone: future
Priority: minormajor
Status: newaccepted

As you may have guessed, this happens because the application is drawing onto a virtual screen which is bigger than the one it eventually gets displayed on. The application and its widgets think that the space below is actually usable and shown to the user when it's not.

The best (and only?) solution is to resize the virtual screen to match the client's. The code already exists, however, to make use of it you will need a virtual screen which supports randr. The only viable option at present is Xdummy.
There is already a winswitch bug describing this: replace Xvfb with Xvnc or Xdummy

My original post describing how to use Xdummy with xpra is no longer up to date as the '--xvfb' switch has now been changed to specify the full command and arguments, which makes it a little easier.

As for the next step, I would like to make Xdummy a proper first class package, removing the need to resort to LD_PRELOAD tricks to start it, etc - see #10. Until then, this will remain a manual setup process..

Last edited 6 years ago by Antoine Martin (previous) (diff)

comment:2 Changed 6 years ago by Antoine Martin

Resolution: wontfix
Status: acceptedclosed

See #2 for a potential workaround, the real solution is #10 - closing.

comment:3 Changed 6 years ago by Antoine Martin

For more information on Xdummy, see the top-level page: Xdummy

comment:4 Changed 6 years ago by Antoine Martin

Milestone: future0.0.7.x
Note: See TracTickets for help on using tickets.