Awesome wm visual anomaly - awesome-wm

I have Awesome window manager running on a Manjaro-running desktop with nvidia GeForce GTX 750 card using non-free nvidia drivers.
The machine gives off a visual anomaly when scrolling through text, both in a tiled window, or full screen. The anomalies also show up playing video. The anomaly is a horizontal band of "ripples" that appears in the middle of the screen. As I write this post, the ripple does not happen when I scroll in the "body" text edit window of the Stackoverflow page, but does appear and distort text in that text edit field when I scroll a comparable amount using the slider on the right edge of the browser window, scrolling the whole page, not just the post text. I do not remember seeing such an anomaly when running Linux Mint with the cinnamon desktop environment, but it did happen when I added Awesome wm to that Mint install. I run two monitors and the effect happens on both. Note that this anomaly does not happen on another Awesome-running machine I have, so it's not inherent to the window manager.

Related

RStudio window zoom when changing from laptop only to docked to monitors, auto-adjust possible?

I was given a new laptop at work and when I switch back and forth from a docking station, RStudio seems to have problems realizing the change in display, while all the other programs seem to auto-detect and re-zoom appropriately. The only fixes I've found is logging out and back into my Windows user account, or going through R-Studio's View>Zoom-in or View>Zoom-out when going back and forth between docked and undocked, which takes time.
There's not some setting I'm missing, is there, so RStudio detects the type of display and auto-adjusts? Example images below.
thank you, dave
This is a known issue, and there is some indication that there are plans to address this in rstudio v1.2.
https://community.rstudio.com/t/dramatic-screen-resolution-issue-see-screen-snip/3703/6
A workaround suggested here:
You should be able to work around this by toggling the Zoom level in the Appearances pane
RStudio is basically a browser window (chrome web application). It will render according to the resolution of the screen, at the current zoom setting. It will not change your zoom level as you switch monitors. Ctr- and Ctrl+ are shortcuts for zooming in and out, where you should also see a popup with a reset (to 100%) option.
Zooming is not the same as changing font sizes, which is the preferable way of ensuring a good visual experience for a resolution.

Chrome video with transparent color overlay and blur shows a weird grid

Some Macs with Chrome show a strange grid over the whole web page (screenshots below).
Screenshot that shows the grid
Here is a very simple example where the client confirmed they see the grid on:
https://vanjajelic.com/clients/thedoor/index.html
As you can see, it's only a full screen HTML5 video with a div on top. The video has a blur on it and the div has an opacity and a background color (I can not put blur and color in the video as it changes dynamically).
My conclusion is that the grid is obviously not part of the DOM as there is nothing in it to create it.
The only cause I can think of is, this is has to be a Chrome bug but wanted check if any of you experienced anything similar.
Note that the client was able to see the grid only on a few computers with this spec:
Chrome Version 65.0.3325.146 (Official Build) (64-bit)
on
MacBook Air (13-inch, Early 2015)
MacOS Sierra Version 10.12.5 (16F73)
Graphics Intel HD Graphics 6000 1536 MB
I cannot reproduce it on my Mac nor on a number of PCs I run tests on :(
Any ideas?

Why does twitter bootstrap "hiccup" on Google Chrome when resizing?

I was playing with adaptative CSS by changing my Google Chrome window size when I noticed that the Twitter Bootstrap page seems to "make google chrome fail" on certain occasions.
Steps to reproduce (from a desktop computer):
Start with a blank Google Chrome tab, full screen
Visit http://twitter.github.com/bootstrap/
Gradually make the window narrower, letting go the mouse every 100 pixels or so.
Keep going until you get the "totally mobile version", at around 400px (The blue "View project on github" button is on top of the white "Download Bootstrap" button, and they are both full-width).
Now make the window thick again, letting the mouse go after every 20 pixels or so.
Chances are that you will get weird behaviour while doing steps 4 or 5 - Chrome gets confused about the sizes, or forgets to draw a vertical region of the page (which is rendered white). I've also managed to get a "phantom side pane" in some rare occasions.
I've tried in two different computers, and I still get the same issues (both using Ubuntu 12)
The thing is, other responsive sites don't have this issue. See for example http://css-tricks.com/ . You can change its size all you want, and Chrome never has any trouble rendering the multiple layouts it has (in fact, it has more layouts than twitter bootstrap).
So I can only conclude that this problem is twitter-bootstrap-specific. Probably related with the way the CSS rules or HTML content is written, or maybe related with the way files are structured.
I'm using twitter bootstrap as a base for one of my sites, and I'd like to solve this issue. Does anyone have any ideas on how to proceed?
If you believe this is bootstrap-specific this should be posted to the Twitter Bootstrap Github Pages instead of SO. However, I've been participating in an issue ticket reg. this which was closed after we pointed out that we're unable to reproduce the error on both Chrome / OS X and Chrome / Win 7 with the same browser build as the OP. This suggest that this is a platform specific chrome-error rather than a problem with the Bootstrap toolkit. With that said, I'd raise a ticket with the chrome team including your build # and OS/Platform setup.
Link to the Github Issue

Qt: How to make window icon bigger (SVG)?

I'm using Qt 4.8.1, and set the window icon with:
app.setWindowIcon(QIcon("/path/to/icon.svg"));
However, no matter how big the svg icon is, the icon shown in the menu bar or when using "alt-tab" in gnome is always very low resolution and "pixelized".
How can I make it render the icon in a higher resolution?
Seems like this can be only avoided when providing a desktop menu entry with a high a resolution icon.
I downloaded qtcreator to test it: When running the version from the web, the icon is bad. As soon as the installed version is run, it works, because the icon from the menu is used.

Safari + jQuery thickbox = massive visual glitches?

I need help determining what the cause of a serious visual glitch is with one of my production websites. It is only happening with Safari - Chrome and all other browsers are fine.
http://www.philanthropicdirectory.org/search
This is a Drupal 6.x website, running the following simultaneously:
jQuery 1.3.2 (Drupal base/default)
jQuery 1.4.4 (This is used here and there by overriding the jQuery namespace to '$js' for certain advanced operations 1.3.2 can't handle)
jQuery UI 1.7.3
Thickbox 1.8.2.19 (I've slightly modified this .js)
TO REPRODUCE:
Click link (visit the page): http://www.philanthropicdirectory.org/search
Click twice (once to center) on any of the 5 'coverflow' panels to trigger Thickbox content
Once TB content loads, resize the browser window horizontally left or right
Notice the odd background-image and background-color offsetting
Switch between any of the 5 'tab' icons in the upper right of the modal system
At any point, use Web Inspector to uncheck and then recheck any CSS property, anywhere
Notice how this instantly clears/fixes all visual glitches
Resize the browser window again or tab between the other tabs, and notice the glitches return.
If you notice the same things I am, it'd be great to get your machine config and Safari version.
Before
After resizing
After tabbing
The images say it all, and as far as I could test, I can only reproduce this problem in the following setup, with Safari:
MacPro, 6-core Xeon (2010)
OS X 10.6.8
2 monitors: 1x 23" Cinema Display (old silver one) + 1x 27" Apple Cinema Display
ATI Radeon HD 5770 (Mac version w/01.00.436 Driver)
Safari 5.1+
I've tested other machines and other machines with earlier versions of Safari (4.x), and the problems are simply not present.
Is there anything you think I can test to figure out why this is happening?
PS: Only using one monitor at a time produces the same problems.
SOLUTION!
I noticed this happening with another website we've built - a website with nothing in common with the Drupal one with the problem here, save for the fact that this new one also has a Flash (SWF) file in the body, and I was applying a CSS property to an element with a negative z-index value.
It was happening on this new website because the container for the object in the HTML was set to
z-index: -1;
in order for elements positioned to overlap the object could be clicked on (otherwise, links on top of the object could not be interacted with).
I was able to permanently fix it by instead setting any elements positioned on top of the object
z-index: 1; /* or anything > 0 */
Given that solution, I hunted down any and all "z-index: -1" CSS on the Drupal website and sure enough there was an element within the Thickbox container that was shown on every tab - the big green "SEARCH" input button. It was styled that way because of visual needs (something to do with the fake inner-drop-shadow on the button).
I disabled the entire z-index property for this element, and lo-and-behold, the funkiness permanently disappeared on the Drupal website.
Hurray! It was surely providence that I came across the same issue more acutely on a different website.
Now I'm not sure the exact bug in Safari that is behind this without intense testing, but all I do know is that an object on the page + any element near it set to z-index: -1 equals total meltdown (on a Mac running Safari 5.x).
I checked in Safari 5.1 (7534.50) on an HP Xeon running Windows 7. I don't see any glitches.
That's weird. Sounds like a race condition of some sort. Maybe there is a bug in your ATI driver? Since it fixes itself when you re-render it, perhaps you could introduce some delay somewhere which might give it more time to render properly?

Resources