Siduction Forum > Software - Support

 [Solved] The desktop background does not refresh in Openbox

(1/1)

Colonel Panic:
Hello all.

I've found a problem which doesn't seem to be unique to Siduction; when I'm in Openbox and try to move a window around the desktop, the desktop doesn't refresh and the window leaves a trail all around the screen.
Fortunately there's a fix for it, which I found from a Ubuntu forum. You have to look for a directory called /usr/lib/x86-64-linux-gnu and then, in that, a file called openbox-autostart. Then uncomment this line;#test -z $BG || $BG -solid "#303030"

Colonel Panic:
Hi again,
I just want to say that I'm in Ubuntu 19.04 now and have discovered this exact same problem (and the same solution) there as well, so it's clearly not a problem exclusive to Seduction. I've just joined the Ubuntu One forum and mentioned it on there.

axt:

--- Quote from: Colonel Panic ---I'm in Ubuntu 19.04 now

--- End quote ---

I expect, but only for your test. Disco is EOS.


--- Quote ---the Ubuntu One forum
--- End quote ---

Probably you mean ubuntuforums.org.

Colonel Panic:
"I expect, but only for your test. Disco is EOS."

Thanks, you're right. It's possible they've fixed the bug by now and should check to make sure. I installed Ubuntu 19.04 from a cover disk from an old Linux magazine (Linux Format) and probably shouldn't have.

"Probably you mean ubuntuforums.org."

Thanks again; I found the Ubuntu homepage confusing. I had to sign up to Ubuntu One before I could post there, but you're right about that being its address.

Colonel Panic:
(Bumped, because I don't feel this justifies a new thread.)

I've had a similar problem in Fluxbox, but was unable to find the cause of it except that it was connected to a setting in the init file I was using at the time so I simply replaced it with another one, restarted fluxbox and the problem went away. Because the entries in the two init files were in a different order, it would have been very hard indeed to track down which setting in the init file was responsible for the problem but if anyone else knows what the problem might have been I'd be interested to know about it (a Google search didn't prove fruitful).

Navigation

[0] Message Index