SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
This bug is actually pretty hard to describe, and even harder to trigger, but it certainly comes up with some frequency.
I think it has to do with the openbox + tint2 + xcompmgr combination I am running, but I can't be sure. It certainly never never happens in KDE. It looks something like this:
It gets triggered when I start an application. I feel like it's okular quite often, but sometimes it's konsole or dolphin or something else. So call it application foo. So I start that application, and its window mostly fails to draw over some part of the screen, like a rectangle, usually in upper left. In fact, nothing gets redrawn in that rectangle anymore while the application foo is running. The lower and right margins of the screen get drawn OK: there I can see the application foo as well as everything else. When I kill the application foo, everything goes back to normal. Sometimes, killing all windows fixes the bug. Other times, restarting tint2 fixes the bug. Sometimes (quite rarely), only killing X fixes the bug, and that is the only thing that always works. Anyone seen anything like that?
Sounds similar to what I occasionally experience with my Debian system. I also have Openbox, tint2 and xcompmgr, but I am not convinced any of those are the problem. For me, the trigger seems to be connected with the file manage and the game Simultrans. If Thunar or PCManFM is running when Simultrans is started a second time it occasionally generates a problem. It never happens the first time the game is started.
I forgot to mention two things.
It happens with Thunar and PCManFM, but not with Krusader.
The work around I have found to restore a normal desktop is to open an Ace of Penguins game. I have no idea why, but it works.
Last edited by Randicus Draco Albus; 01-18-2014 at 06:06 AM.
Why not switch to compton, sounds like a compositor problem? Used compton with OB and tint2 for a while with no sweat. You can build it from git with src2pkg and have a package for it very easily, no extra make or configure options. Just src2pkg /path/to/compton/
Cool! I started with xcompmgr and thought it was kinda limited especially with transparency options. Here's my compton start up line if you want, but I'm not using transparency but you could tweak it, the main thing that the backend glx solved for me was being able to stop screen tearing on my desktop (Nvidia) and laptop (hd4000) plus it stopped a lot of glitches I was getting while watching video in vlc while using nvidia hardware decoding!