Inkscape gets lost between two screens
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
New
|
Undecided
|
Unassigned |
Bug Description
Hello,
I have a weird bug and it took me ages to figure out what is happening.
I have Inkscape running on my MacBook Air since years. Since winter the MacBook is connected to a larger Samsung screen, when I work at home. Around that tiem I guess (I can't remember exactly) I couldn't run INkscape properly. I deinstalled and reinstalled it several times. Sometimes it opens and sometimes I can only see the XQuartz menu. In the menu I can see that a "Neues Dokument 1" is open, but when I click on it it won't show.
Today I realized that I can see the document and work normally, when I disconnect the large screen. As soon as I connect it again, Inkscape won't be seen anywhere. The XQuartz menu is visible with the Inkscape file shown in the "windows" list.
It looks as if Inkscape is trapped between the two screens. The really weird thing: sometimes it works and I don't know why.
The result is, that I have to work on the small Laptop screen with Inkscape instead of using the larger screen.
OS: OS X El Capitan 10.11.4
XQuartz: 2.7.8
Inkscape: ? I downloaded it about 3-4 weeks ago, so it should be 0.91 or maybe 0.90
Samsung SyncMaster P2450, connected with a Thunderbolt - VGA adapter.
Thanks for your help!
Wiebke
Thank you for taking the time to file this report. The issue is known (upstream conflict of XQuartz with more recent versions of OS X), and needs to be addressed outside of Inkscape (it affects other applications running under X11 as well). For Inkscape, we already track this upstream issue in this earlier report: /bugs.launchpad .net/inkscape/ +bug/1244397
* Bug #1244397 “XQuartz on OS X 10.9 and later: limited support for multi-monitor setups”
https:/
The workaround recommended by the core developer and maintainer of XQuartz is to «Turn off "Displays have separate spaces" in Mission Control if you need to use X11 across multiple displays».
Linking as duplicate to bug #1244397.