-
-
Notifications
You must be signed in to change notification settings - Fork 198
Dual 4K screens get scrambled on X11 #734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Do you have any screen scaling enabled? If yes, you're probably facing this issue #276 |
Unfortunately, no, I dont used the fractional scaling. Anyway, the issue happens with or without fractional scaling enabled. |
Can you describe what "broke" means? Does it take the wrong area? Is the image blurry? Do you get any screenshot captured? |
Both screens get scrambled, like mixed parts from one screen together the other. Nothing makes sense. I know that fractional scaling gave problem to other screenshot softwares (and they told me it is a deep bug inside Qt5 related to fractional scaling), but when I disable fractional scaling, they worked as expected. Unfortunately, ksnip dont work, and my guess it have something to do with ksnip trying to get both screens in the same selection (disabling one screen will make it work, but, I need both screens for my work). |
Can you double check if the issue still happens with the continuous build? I have just pushed a fix, it might need ~20min to get published. Thought for the other issue but I'm curious if it affects this one too. |
@DamirPorobic just to provide some feedback. I had some similar weird behavior (where a large QT screen was being instantiated and ksnip would eventually segfault) while using two 4k displays (1 portrait, 1 landscape). Using the latest CI build has fixed all issues. |
@gslandtreter thatnks for providing feedback! @eerbano can you check if you're still facing this issue with the continuous build? |
Can you tell me where I can get an already compiled build with this fix? The build I am using was the one on Ubuntu 20.04 repo. |
You can find that here https://github.com/ksnip/ksnip/releases/tag/continuous. The AppImage is probably the least invasive option you can just run it and delete it afterwards if you don't want it, no installing required. |
The AppImage was a no-go, it simply dont open here. So I tried the one from snap. It worked, but feels heavy, lagging (it should not lag in my hardware configuration, cpu 5950x and gpu GTX 1080 Ti). |
AppImages need to be made executable, like explained here https://github.com/ksnip/ksnip#appimage Yeah, I have experienced such behavior with snaps too, I personally don't like them because they are that big and clumsy. As you seem to be on ubuntu you could also use the deb package, that can be uninstalled.
What do you mean with "It worked", you were able to install it or the issue was gone with the continuous build? |
The issued I had is fixed, it does not "scramble the screens", as I described previously. |
That's good. You'll get that patch through Upuntu repo with the next release. I'm closing this issue. |
I installed the debian package, and that is much the same as the snap version I installed, feels heavy, lagging, when I click to take a screenshot, the mouse pointer moves in the screen like a slowmotion. |
Is it only behaving slow when selecting a region or the whole application being slow like that? Every time you try to select a region or just on the first time? Unusual, haven't had such reports of any other user. For me it worked find on Ubuntu 20.04 in a VM just recently while I was fixing another bug. Could you try if it behaves the same after a restart? If the behavior stays the same, please log a new bug. |
Describe the bug
It dont work in my current setup where I have one 2k screen, and one second 4k screen
To Reproduce
Any way you try to take a screenshot will trigger
Expected behavior
I expected it to work out of the box
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: