Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client icon artifacts in taskbar after client exits when using custom widget template with awful.widget.tasklist. #3810

Open
djsigmann opened this issue May 16, 2023 · 2 comments

Comments

@djsigmann
Copy link

Output of awesome --version:
awesome v4.3-1588-gb54e50ad6 (Too long)
• Compiled against Lua 5.4.4 (running with 0.9.2)
• API level: 4
• D-Bus support: yes
• xcb-errors support: yes
• execinfo support: yes
• xcb-randr version: 1.6
• LGI version: /usr/share/lua/5.4/lgi/version.lua
• Transparency enabled: yes
• Custom search paths: no

How to reproduce the issue:

awful.widget.tasklist { -- Create a tasklist widget
	screen = s,
	filter = awful.widget.tasklist.filter.currenttags,
	buttons = require("binds.tasklist").mouse,
	layout = {
		layout  = wibox.layout.fixed.horizontal,
		spacing = 8,
		spacing_widget = {
			color  = "transparent",
			widget = wibox.widget.separator,
		},
	},
	style = {
		disable_task_name = true,
	},
	widget_template = {
		layout = wibox.layout.fixed.vertical,
		---[[
		{
			widget = wibox.container.background,
			id = "background_role",
			forced_height = 4,
			shape = gears.shape.rounded_bar,
		},
		--]]
		{
			layout = wibox.layout.stack,
			--[[
			{
				id = "icon_role",
				widget = wibox.widget.imagebox,
			},
			--[==[]]
			awful.widget.clienticon,
			--]==]
			{
				widget = wibox.container.place,
				valign = "bottom",
				halign = "left",
				{
					id		= "text_role",
					widget	= wibox.widget.textbox,
				},
			},
		},
		end,
	},
}

Actual result:

output.mp4

Expected result:

Those small artifacts that are essentially the cropped edges of the client's icon should not be there after the client exits.

Using a compositor has no effect on this behaviour.

@actionless
Copy link
Member

Transparency enabled: yes

try running awesome with --no-argb flag or with compositor

@djsigmann
Copy link
Author

djsigmann commented May 18, 2023

try running awesome with --no-argb flag or with compositor

Had no effect, other than (obviously) there not being any transparency with or without a compositor; the visual artifacts still appear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants