You are not logged in.
It seems arch may have updated awesome or some component of that, resulting in scrambled backgrounds (see partial screenshot below).
Initially, awesome started with red error box (also jigsawed) listing various things that went wrong in the startup -- e.g. not finding debian menu components, etc. I tried to fiddle with the rc.lua awesome config file (prior rc.lua was overwritten by update) and the red box is gone (after restarting awesome), but the scramble remains.
The top bar is not scrambled. Scramble is different each time. Tried replacing Nouveau with nvidia, but that didn't work.
I'm not exactly sure what the root of this is - didn't see anything obvious in the Xorg.0 log.
any suggestions appreciated. Thanks!
http://i41.photobucket.com/albums/e267/ … _scrot.png
EDIT: marking this solved ... I'm not sure what to do, specifically, to fix the issue.
Last edited by notacar (2013-04-23 03:33:30)
Offline
http://i.imgur.com/rQUZJPe.png?1
Fresh install - here's another one. Is this a vid card failing? I'm sort of at a loss. Thanks for any ideas....
Note that there's no colored stippling on the top bar - makes me think this is not a hardware issue but rather something to do with how awesome/feh are dealing with the background... hmm... Using 2 different-resolution monitors in dual configuration...
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by notacar (2013-04-20 00:18:43)
Offline
What are you using to set the background?
I tired awesome recently, and I had to make the desktop redraw (in my case, killed xfdesktop and let it respawn) otherwise it was a little scrambled like this. Maybe somehow your desktop is drawn, then awesome starts up, taking random stuff from video memory, and displayed as is because nothing rewrote the appropriate content (the actual background image) to it.
Have you tried changing the desktop wallpaper while the desktop is corrupt and see if it comes back normal after a wallpaper change? The point is to redraw the content on the X root window, anything that can set the wallpaper should work.
Offline
e.g. not finding debian menu components, etc.
These are the Arch boards; please use the Debian boards for support.
https://wiki.archlinux.org/index.php/Fo … pport_ONLY
Closing -- for deletion
Offline
I am assured the "debian menu components" is an awesome, distro dependant, error... Reopening.
Offline
THANKS, appreciate the response. Awesome uses, I believe, fehbg. Mod deleted thread, but your response was correct - restarting awesome clears the corruption. So, awesome needs to affirmatively redraw the background each time & that is apparently not happening (?). Thanks again for the response - gives me something to pursue. cheers!
"So, awesome needs to affirmatively redraw the background each time & that is apparently not happening (?)"
Since Awesome is not a compositing manager, it's a window manager. All it does, it place the windows on the screen, ask them to redraw themself. The problem is not with awesome itself, it's probably because of the way X.org works. The screen is probably indeed repainted correctly too. The way it works, everything in X.org is a window. There's a root window, which is where desktop managers or background managers like fehbg or nitrogen paints their background. Once its painted, those usually just exit as they usually have no more work to do at all (by contrast to more complete and featured desktops, like those with icons on it which need the program to stay open to respond to clicks). This means the root window will keep this state forever, usually containing only the background. But in some cases, changing the resolution, changing window managers and stuff like that will erase the root window content (or will overflow to it), corrupting what's there. Since there are no program running to repaint the window, X just repaints the same corrupted content on your screen, which is what you see in your screenshots. Just running fehbg again should fix it, it's just the order things happen that result the X root window being in an undefined state.
If you feel like experimenting, you can try changing resolution while the background is ok. It will get all corrupted again because it has a new size, and thus have moved in memory. You will see the previous content of that memory location, which can be noise or image fragments from something else, or even 3D textures. Anything is possible. Run the background again, it will be fixed. Revert resolution again, and it will corrupt again!
Also, I'm curious as why you are getting debian errors while starting awesome (which also confused the admins). Have you migrated from an older Debian-based Awesome config or something?
Offline
Since Awesome is not a compositing manager, it's a window manager. All it does, it place the windows on the screen, ask them to redraw themself. The problem is not with awesome itself, it's probably because of the way X.org works. The screen is probably indeed repainted correctly too. The way it works, everything in X.org is a window. There's a root window, which is where desktop managers or background managers like fehbg or nitrogen paints their background. Once its painted, those usually just exit as they usually have no more work to do at all (by contrast to more complete and featured desktops, like those with icons on it which need the program to stay open to respond to clicks). This means the root window will keep this state forever, usually containing only the background. But in some cases, changing the resolution, changing window managers and stuff like that will erase the root window content (or will overflow to it), corrupting what's there. Since there are no program running to repaint the window, X just repaints the same corrupted content on your screen, which is what you see in your screenshots. Just running fehbg again should fix it, it's just the order things happen that result the X root window being in an undefined state.
If you feel like experimenting, you can try changing resolution while the background is ok. It will get all corrupted again because it has a new size, and thus have moved in memory. You will see the previous content of that memory location, which can be noise or image fragments from something else, or even 3D textures. Anything is possible. Run the background again, it will be fixed. Revert resolution again, and it will corrupt again!
Also, I'm curious as why you are getting debian errors while starting awesome (which also confused the admins). Have you migrated from an older Debian-based Awesome config or something?
Thanks mod, for reviving thread. This is arch_64.
Wow Max-P: very helpful response. The explanation of the root window is really helpful. I keep wanting to think the fault here may be awesome wm not telling fehbg to refresh (or somehow changing resolution during the start perhaps), but I see what you write above that the problem may lie with something X is doing during startup. I have 2 different size monitors side-by-side with a custom nouveau rule. Suspect something stopped working as expected there if it's not a fault with awesome wm's management of fehbg.
re debian: yes, awesome's configs default (or at least did default prior to current) to searching for a debian menu (which is of course never found). Usually this non-find does not result in any error, but with a recent awesome wm update, the described constellation of errors resulted, presumably when my local .config/awesome/rc.lua tried to speak with the updated awesome - result: errorlist.
As stated above, this is a stock arch install (both the prior instance and the reinstall attempting to erase whatever I broke to result in the corrupted background).
I'm still not sure what to do to try to fix this, but I think I should mark this "solved" because the problem isn't really an arch problem. I'll try to talk to some awesome wm folks and some X folks to see if anyone else has similar issues.
Offline
... the problem isn't really an arch problem. I'll try to talk to some awesome wm folks and some X folks to see if anyone else has similar issues.
Perhaps not, and thus this should be taken "upstream" as well. But there are many awesomewm users on these forums - and archlinux has a good reputation of contributing to upstream because the community works on solutions to this sort of problem.
That said, I don't use awesome, can can't contribute directly to this issue.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline