[solved] Awesome screen drawing problems

_Pi · 2013-01-04 20:57:44

Last Christmas awesome 3.5 ruined awesomewm for me. I'm actually thinking of setting up qtile.....

Below is a pic of what I'm getting in awesome. Every time I move windows I get these weird draw errors it doesn't matter if the desktop is composted or not. Nothing is coming up as an error in awesome or in it's output.

And before anyone asks, I took it with a cell phone because taking a screenshot would redraw the screen and you would see the terminal as it should be.

https://docs.google.com/open?id=0B80fRV … i01ekhvdmM

Last edited by _Pi (2013-01-05 02:00:36)

_Pi · 2013-01-04 22:58:32

Another thing I noticed is that this only happens with urxvt windows.

Trilby · 2013-01-04 23:04:28

That picture does not make the problem clear. What is the problem?

_Pi · 2013-01-04 23:32:19

In reality the urxvt on the left side has the same content as the urxvt on the right side. Whenever I change windows urxvt will redraw like that instead of redrawing properly sometimes.

This behavior stops, when I add --no-argb to awesome's commandline. However instead it gives me random and frequent crashes such as listed in https://awesome.naquadah.org/bugs/index … sk_id=1079.

I've basically reverted to 3.4.13, I'm going to ignore 3.5 until it's more stable.

tdy · 2013-01-04 23:50:59

You can try starting awesome with the --no-argb option. I'm using 3.5 and urxvt without any issues with that option.

_Pi wrote:

I've basically reverted to 3.4.13, I'm going to ignore 3.5 until it's more stable.

That's fine, but this is also the exact reason there are bugs in 3.5. You're free to do as you choose, but everyone else also chose to ignore the 3.5 branch until release, and many are still ignoring it after release.

What happens when you put these two things together?
* one active developer of awesome
* no one to test the git/master branch for fear of breakage

You should be able to do the math.. and yet people rant on the forums of a distro that the one dev doesn't even use. If you're actually interested in making awesome better, look at the awesome bugtracker and if your issue is not there, post it there so at least the one dev sees it....

Last edited by tdy (2013-01-04 23:54:35)

_Pi · 2013-01-04 23:57:04

This behavior stops, when I add --no-argb to awesome's commandline. However instead it gives me frequent crashes such as listed in https://awesome.naquadah.org/bugs/index … sk_id=1079.

I need something stable for me right now, I'm not going to use awesome if it's going to crash on me all the time.

tdy · 2013-01-04 23:59:25

_Pi wrote:

This behavior stops, when I add --no-argb to awesome's commandline. However instead it gives me frequent crashes such as listed in https://awesome.naquadah.org/bugs/index … sk_id=1079.
I need something stable for me right now, I'm not going to use awesome if it's going to crash on me all the time.

Ah I didn't look at your last post.

And as I said, that's fine, but don't expect stability for a long time at the rate things are going and with the way most users are acting.

_Pi · 2013-01-05 00:41:38

TBH, it is a crappy release, from 3.3 to 3.4 there was almost nothing going wrong, but now this. I thought they would have learned by now to stop making armageddon capability issues on every minor version release. I would be fine if 3.5 was at least stable and RC tested when they made these changes, every WM in the world has had issues with migrating to argb visuals. Not only that but the needless signal re-factoring just takes the cake. I would be fine if this was an alpha, maybe a beta, but this was seemingly just dumped into the release pool.

Trilby · 2013-01-05 00:44:51

Yes, how dare "they" provide totally free software that is not up to your standards.

_Pi · 2013-01-05 01:13:12

I'm not complaining about free software. I'm complaining that any legitimate software project doesn't just randomly kick a major release out the door. They can do whatever they want, I'm just saying they are doing things unprofessionally. If any major project did that they'd lose credibility instantly.

Trilby · 2013-01-05 01:20:09

The definition of a professional is one who gets paid for their work.

So, the developers of free software are - by definition - unprofessional. Awesomewm seems to me to be a major project. But "they" also probably aren't to worried about credibility.

_Pi · 2013-01-05 01:55:51

[accidental double post please delete]

Last edited by _Pi (2013-01-05 02:00:01)

_Pi · 2013-01-05 01:59:27

urxvt needs to have a 32 bit depth set in order to be properly drawn without the --no-argb switch. It is now properly updating. As for crashes, either re-installing 3.5-2 fixed it or not running it through gdm fixed it.

_Pi · 2013-01-05 02:13:35

Confirmed -- Running awesome through gdm with the --no-argb flag gives the following dump.

E: awesome: signal_fatal:231: signal 11, dumping backtrace
awesome(backtrace_get+0x41) [0x422551]
awesome() [0x40d1d2]
/usr/lib/libc.so.6(+0x35340) [0x7f59978cd340]
/usr/lib/libxcb-keysyms.so.1(xcb_key_symbols_get_keycode+0x32) [0x7f5998be9112]
awesome(xwindow_grabkeys+0x82) [0x422069]
awesome() [0x427466]
/usr/lib/liblua.so.5.2(+0xd11a) [0x7f5997e9d11a]
/usr/lib/liblua.so.5.2(+0x18624) [0x7f5997ea8624]
/usr/lib/liblua.so.5.2(+0xd369) [0x7f5997e9d369]
/usr/lib/liblua.so.5.2(+0xc9ab) [0x7f5997e9c9ab]
/usr/lib/liblua.so.5.2(+0xd595) [0x7f5997e9d595]
/usr/lib/liblua.so.5.2(lua_pcallk+0x7f) [0x7f5997e995df]
awesome(signal_object_emit+0x1e9) [0x42482d]
awesome(luaA_class_emit_signal+0xd) [0x4239c1]
awesome(luaA_object_emit_signal+0x312) [0x424be4]
awesome(client_manage+0xa68) [0x429dd1]
awesome(event_handle+0xc2b) [0x411c6e]
awesome() [0x40d18a]
/usr/lib/libglib-2.0.so.0(+0x47b14) [0x7f5999fbfb14]
/usr/lib/libglib-2.0.so.0(g_main_loop_run+0x72) [0x7f5999fbff72]
awesome(main+0x86a) [0x40db24]
/usr/lib/libc.so.6(__libc_start_main+0xf5) [0x7f59978b9a15]
awesome() [0x40cde9]

Reported upstream.

Arch Linux

#1 2013-01-04 20:57:44

[solved] Awesome screen drawing problems

#2 2013-01-04 22:58:32

Re: [solved] Awesome screen drawing problems

#3 2013-01-04 23:04:28

Re: [solved] Awesome screen drawing problems

#4 2013-01-04 23:32:19

Re: [solved] Awesome screen drawing problems

#5 2013-01-04 23:50:59

Re: [solved] Awesome screen drawing problems

#6 2013-01-04 23:57:04

Re: [solved] Awesome screen drawing problems

#7 2013-01-04 23:59:25

Re: [solved] Awesome screen drawing problems

#8 2013-01-05 00:41:38

Re: [solved] Awesome screen drawing problems

#9 2013-01-05 00:44:51

Re: [solved] Awesome screen drawing problems

#10 2013-01-05 01:13:12

Re: [solved] Awesome screen drawing problems

#11 2013-01-05 01:20:09

Re: [solved] Awesome screen drawing problems

#12 2013-01-05 01:55:51

Re: [solved] Awesome screen drawing problems

#13 2013-01-05 01:59:27

Re: [solved] Awesome screen drawing problems

#14 2013-01-05 02:13:35

Re: [solved] Awesome screen drawing problems

Board footer