Compton: BadWindow & BadPicture errors...

[ghost]

Hi,

Here's my specs;

Slacwkare 14.0 x86
Openbox 3.5.0
compton (git-v0.1_beta1-17-g796e2c6-dirty-2013-10-01

I noticed with some applications and windows I open, I'm not really sure what exact steps are producing these errors below, but if play around with an applicaiton/window, at some point in the terminal it will spit these messages out, or if I move back and forth across the desktops and return to the desktop the window or application is at, this seems to trigger it also.

But one application I found where it is always reproducable is in Gimp 2.8.2, if all I do is just start gimp and click through the toolbar menus it happens, or again moving back and forth across the desktops and returning to gimp.

I'm not seeing any issues when I'm using compton everything seems to be working good, but I only run Openbox and I don't use display managers, I just use 'start'x' which I like so when I log out of Openbox this also helps me to keep an eye on things. So the only problem with all these messages is that it's flooding the console making it hard to keep an eye on things...

THANKS

[ 102.95 ] error 3 (BadWindow) request 2 minor 0 serial 102435 ("BadWindow (invalid Window parameter)")
[ 102.95 ] error 3 (BadWindow) request 2 minor 0 serial 102446 ("BadWindow (invalid Window parameter)")

[ 2886.19 ] error 9 (BadDrawable) request 151 minor 4 serial 744751 ("BadDrawable (invalid Pixmap or Window parameter)")

[ 2886.19 ] error 172 (BadPicture) request 151 minor 8 serial 744752 ("RenderBadPicture (invalid Picture parameter)")
[ 2886.19 ] error 172 (BadPicture) request 151 minor 8 serial 744753 ("RenderBadPicture (invalid Picture parameter)")
[ 2886.19 ] error 172 (BadPicture) request 151 minor 8 serial 744754 ("RenderBadPicture (invalid Picture parameter)")
[ 2886.19 ] error 172 (BadPicture) request 151 minor 8 serial 744755 ("RenderBadPicture (invalid Picture parameter)")
[ 2886.19 ] error 172 (BadPicture) request 151 minor 8 serial 744756 ("RenderBadPicture (invalid Picture parameter)")
[ 2886.19 ] error 9 (BadDrawable) request 14 minor 0 serial 744763 ("BadDrawable (invalid Pixmap or Window parameter)")

[ 2886.20 ] error 172 (BadPicture) request 151 minor 7 serial 744764 ("RenderBadPicture (invalid Picture parameter)")
[ 2886.20 ] error 4 (BadPixmap) request 54 minor 0 serial 744765 ("BadPixmap (invalid Pixmap parameter)")

[ 3686.33 ] error 3 (BadWindow) request 20 minor 0 serial 1252447 ("BadWindow (invalid Window parameter)")
[ 3686.34 ] error 3 (BadWindow) request 2 minor 0 serial 1252452 ("BadWindow (invalid Window parameter)")
[ 3686.34 ] error 3 (BadWindow) request 15 minor 0 serial 1252453 ("BadWindow (invalid Window parameter)")
[ 3851.64 ] error 3 (BadWindow) request 20 minor 0 serial 1326765 ("BadWindow (invalid Window parameter)")
[ 3851.64 ] error 3 (BadWindow) request 2 minor 0 serial 1326770 ("BadWindow (invalid Window parameter)")
[ 3851.64 ] error 3 (BadWindow) request 15 minor 0 serial 1326771 ("BadWindow (invalid Window parameter)")
[ 3902.31 ] error 3 (BadWindow) request 20 minor 0 serial 1370422 ("BadWindow (invalid Window parameter)")
[ 3902.31 ] error 3 (BadWindow) request 2 minor 0 serial 1370427 ("BadWindow (invalid Window parameter)")
[ 3902.31 ] error 3 (BadWindow) request 15 minor 0 serial 1370428 ("BadWindow (invalid Window parameter)")
[ 3943.50 ] error 3 (BadWindow) request 20 minor 0 serial 1408620 ("BadWindow (invalid Window parameter)")
[ 3943.51 ] error 3 (BadWindow) request 2 minor 0 serial 1408625 ("BadWindow (invalid Window parameter)")
[ 3943.51 ] error 3 (BadWindow) request 15 minor 0 serial 1408626 ("BadWindow (invalid Window parameter)")
[ 3961.96 ] error 3 (BadWindow) request 20 minor 0 serial 1421642 ("BadWindow (invalid Window parameter)")
[ 3961.97 ] error 3 (BadWindow) request 2 minor 0 serial 1421647 ("BadWindow (invalid Window parameter)")
[ 3961.97 ] error 3 (BadWindow) request 15 minor 0 serial 1421648 ("BadWindow (invalid Window parameter)")
[ 3977.49 ] error 3 (BadWindow) request 20 minor 0 serial 1432821 ("BadWindow (invalid Window parameter)")
[ 3977.50 ] error 3 (BadWindow) request 2 minor 0 serial 1432826 ("BadWindow (invalid Window parameter)")
[ 3977.50 ] error 3 (BadWindow) request 15 minor 0 serial 1432827 ("BadWindow (invalid Window parameter)")
[ 4273.60 ] error 3 (BadWindow) request 20 minor 0 serial 1442317 ("BadWindow (invalid Window parameter)")
[ 4273.60 ] error 3 (BadWindow) request 2 minor 0 serial 1442322 ("BadWindow (invalid Window parameter)")
[ 4273.60 ] error 3 (BadWindow) request 15 minor 0 serial 1442323 ("BadWindow (invalid Window parameter)")
[ 4281.83 ] error 3 (BadWindow) request 20 minor 0 serial 1448764 ("BadWindow (invalid Window parameter)")
[ 4281.83 ] error 3 (BadWindow) request 2 minor 0 serial 1448769 ("BadWindow (invalid Window parameter)")
[ 4281.83 ] error 3 (BadWindow) request 15 minor 0 serial 1448770 ("BadWindow (invalid Window parameter)")
[ 4379.38 ] error 3 (BadWindow) request 20 minor 0 serial 1534328 ("BadWindow (invalid Window parameter)")
[ 4379.38 ] error 3 (BadWindow) request 2 minor 0 serial 1534333 ("BadWindow (invalid Window parameter)")
[ 4379.38 ] error 3 (BadWindow) request 15 minor 0 serial 1534334 ("BadWindow (invalid Window parameter)")

[richardgv]

52 is probably the most referenced issue here... And I'm going to do is once again. These errors are normal (somehow...) and unavoidable (we could hide them but it may cause problems when diagnostics other issues). See the issue for more info.

I just use 'start'x' which I like so when I log out of Openbox this also helps me to keep an eye on things. So the only problem with all these messages is that it's flooding the console making it hard to keep an eye on things...

Pipe is your friend.

compton &> /tmp/compton.log

You could use -b and --logpath, as well.

compton (git-v0.1_beta1-17-g796e2c6-dirty-2013-10-01

"Dirty"? What did you do with it? :smile:

[ghost]

Since I'm using the config, I'm running like this for the moment;

compton --config ~/.config/compton.sh &> /tmp/compton.log

So you want me to run it like this for a while so you can collect the log?

Dirty? I ran; compton -h | head -n1.and that's the output it gave me, something wrong with that?

thanks

[richardgv]

Since I'm using the config, I'm running like this for the moment;

compton --config ~/.config/compton.sh &> /tmp/compton.log

So you want me to run it like this for a while so you can collect the log?

Not quite. I'm pointing out the way to avoid error messages from compton to flood your virtual console.

Why compton.sh? Our configuration file is not a shell script.

Dirty? I ran; compton -h | head -n1.and that's the output it gave me, something wrong with that?

"dirty" means your source is modified, somehow. Typically git status, git diff, or git diff --cached reveals what you have changed.

[ghost]

Ok, I though you wanted log output hehe... :)

By the way do you think it's posible to create a 'Log' option for the config file so people can turn on or off logging and to whcih /path file they'd like it logged to?

I changed it to .sh because when I look at it in the terminal it displays in colors which makes it easier to read through it is all. Would running it as a .sh file cause issues? I can always change it back once I'm done reading through it...

The only thing I changed was the README.md to README for packaging into my slackware package... But I'll leave it all alone this time...

THANKS

[richardgv]

By the way do you think it's posible to create a 'Log' option for the config file so people can turn on or off logging and to whcih /path file they'd like it logged to?

Yes, it's possible, but we won't. Shell redirection is good enough.

(Except when -b is used, in which case --logpath controls where the log will go to.)

I changed it to .sh because when I look at it in the terminal it displays in colors which makes it easier to read through it is all. Would running it as a .sh file cause issues? I can always change it back once I'm done reading through it...

Not that I could see. :-)

The only thing I changed was the README.md to README for packaging into my slackware package... But I'll leave it all alone this time...

Oh, I see. :-)

[ghost]

I looked at man compton and I got this;

-b Daemonize process. Fork to background after initialization.

And I did a search for logpath and didn't see anything, sorry a bit lost here... :(

This is how I'm running compton now;

compton --config ~/.config/compton &> /tmp/compton.log

So with -b & --logpath how would I change this?

Thanks

[richardgv]

So with -b & --logpath how would I change this?

Just use your shell redirection if you don't understand it.

--logpath /path/to/log/file basically acts as shell redirection when -b is enabled (with which shell redirection has no effect, because we freopen() all output to /dev/null by default). Sorry that I forgot to document it.

[ghost]

So like this?

compton --config ~/.config/compton -b --logpath /tmp/compton.test

thanks...

[richardgv]

@SlackBox:

I believe so, although you may prefer a better file extension. :smile:

[ghost]

THANKS richard, actually like you made;

compton --config ~/.config/compton -b --logpath /tmp/compton

Keep up the great work, compton is really nice... :)