Skip to content
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

URxvt - mod+f - Wallpaper distorted and slight broder artifacts #1254

Closed
i3bot opened this issue Jun 8, 2014 · 3 comments

Comments

Projects
None yet
2 participants
@i3bot
Copy link

commented Jun 8, 2014

[Originally reported by i3-new-ticket]
(These are my system specs;

Slackware 14.1 x86_64
i3 4.7.2
xorg-server-1.14.3
Nvidia GTX660M - drivers 331.67
rxvt-unicode-9.20

These are the steps to reproduce the problem

I have URxvt setup in my conf like below;

for_window [class="URxvt"] floating enable border pixel 1

  1. mod+enter - opens urxvt
  2. mod+f - make urxvt full screen
  3. Pressing mod+f once or several times going back and forth, background wallpaper is distorted viewing through urxvt.

Also at times I see slight white artifacts appearing around the edges of the thin blue border running aound the window that will completly turn white with compton, and with compton turned off, it will only appear as white in a few areas, not the entire border, just small sections of white.

I've have created three videos that show the wallpaper distortion. The last video, mod+f_3.m4v shows the white artificats around the entire border edge with compton. I was not able to take a video with compton turned off showing just small areas of white around the border, I'm not always able to reproduce this, it just appears for some reason on occassion.

Without compton the wallpaper distortion

https://www.dropbox.com/s/dk73t73j2b5elwo/mod%2Bf_1.m4v
https://www.dropbox.com/s/os5xa8xwcie0l6o/mod%2Bf_2.m4v

With compton white artificat around border edge
https://www.dropbox.com/s/6x2ulu07ne7y1xd/mod%2Bf_3.m4v

I will also report the last video to the compton developer.

Thank you all very much for your time and help with these issues, keep up the great work!

@i3bot

This comment has been minimized.

Copy link
Author

commented Jun 8, 2014

[Original comment by anonymous]

Sorry made a mistake before. I created the first two videos to show the wallpaper distortion, and the last video to show the white appearing around the edge.

Notice in mod+f_1 the logo appears in all corners and in the second video you can see the wallpaper torn into different segements/sections.

Depending on the wallpaper there is always some sort of tearing going on.

Thank you again...

@stapelberg

This comment has been minimized.

Copy link
Member

commented Jun 8, 2014

Note that the usage of compton or any other compositor is not supported with i3.

As for the other distortion: I’ve only ever noticed them with the nvidia driver. With any other driver, they don’t appear. So far, all evidence points towards a bug in the nvidia driver. In case you have contrary evidence, feel free to reopen, but we can’t realistically do something about problems related to closed source software.

@i3bot

This comment has been minimized.

Copy link
Author

commented Jun 10, 2014

[Original comment by anonymous]

I said the words; 'with compton' and no menton of it before, meaning for the first two videos I was not using compton, I even mention this above the videos;

Without compton the wallpaper distortion

With compton white artificat around border edge

Anyhow...

I've personally never used a tiling WM till now, so I've never opened and maiximized and minimized a terminal this fast till now, so I went back and tried to do the same in Openbox and I noticed too in Openbox the wallpaper being torn.

But as I also mentioned, without compton I will see slight white artifacts appearing on the borders edge, meaning the default blue color of the border, running around the sides and bottom will have flashes of white appear in it, not sure this is also caused by Nvidia...

thanks

@i3bot i3bot self-assigned this Jun 10, 2014

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.