awesome wm 3.5.3 cairo 1.12.16 after updating awesome wm to 3.5.3 i'm seeing corruption in the screen (usually just the naughty widgets) and wibox errors as if awesome just crashes. i boiled it down to my wallpaper changing that causes this error. here's the current state of that code: -- {{{ Wallpaper local wp_timer = timer { timeout = 10 } local wp_files = {} wp_timer:connect_signal("timeout", function() if next(wp_files) == nil then local fh = io.popen("find /home/razamatan/images/bkg -type f | grep -Ei \"\\\.(jpg|jpeg|gif|bmp|png)\$\" | grep -v vertical | rl") for file in fh:lines() do table.insert(wp_files, file) end io.close(fh) end local wp_file = table.remove(wp_files) naughty.notify({title = "wallpaper", text = wp_file}) --[[ uncommenting this block will actually perform the wallpaper switch for s=1, screen.count() do if string.match(wp_file, '/center/') then gears.wallpaper.centered(wp_file, s, "#000000") else gears.wallpaper.fit(wp_file, s, "#000000") end end --]] wp_timer:stop() wp_timer.timeout = 60 * 60 wp_timer:start() end) wp_timer:start() -- }}} obviously, to recreate the error, you'll have to 1. change the find statement in the io.popen to grab a directory with image files in them 2. remove the "rl" command (it's a perl script i wrote to randomize input lines) 3. uncomment the for loop that actually makes the gears.wallpaper calls to swap out the background
Awesome 3.5.4 was released recently. It reverts some changes to code dealing with cairo, maybe you shoult try it?
i'm going to see if 3.5.4 fixes. talking w/ upstream, it appears that this commit/rollback is the likely fix: http://git.naquadah.org/?p=awesome.git;a=commit;h=eef20459540991d900ed0d6e8eb6e20cefcc36e1 if 3.5.4 fixes things for me, it seems that 3.5.3 should just be skipped given the nature of the issue. the version bump effort should be minimal since i literally just symlinked the 3.5.3 ebuild to 3.5.4 and manifest/installed it. will post the results of 3.5.4 later today when i get back to my home machine.
confirming that 3.5.4 fixes this issue for me. i'd recommend bumping getting 3.5.4 in portage pronto given the "low level" nature of this bug (interaction in the X/cairo layer).
i can also confirm this problem and it would be nice to get a bump of the ebuild in portage. thanks
In case awesome is bumped to 3.5.4, it should be patched with the code from the following commit - http://git.naquadah.org/?p=awesome.git;a=commit;h=7967d05915c95c8eba7709a46093cc1b6de55572 Otherwise it will have rather nasty warnings in menubar (Mod4-P).
Commited with patch, thanks.
