SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 2013-01-29 03:11:03

ew
#! Die Hard
Registered: 2012-09-27
Posts: 1,975

[SOLVED-the issue was NOT related to Compton]

I`ve finally managed to install a kernel that goes well with my hardware and Waldorf. Siduction 3.6-8. But regardless of  which kernel I use, I have issues with compositing. In the default autostart file, compositing gets started right after nitrogen restores wallpaper. If I use this startup sequence then compton doesn`t work properly. Icons get ugly with artifacts and stripes, and often the background colors on the icons is missing. As with Thunar. Just a hammer on white background. If I disable compositing or restart it then it displays the icon properly, but then I have to restart compositing for each icon that I open in the taskbar...

After trying and failing I found a workaround. If I delay the startup of compton to 10 seconds behind everything else, then compositing works fine, and all icons are displayed properly. And it sticks. No need to restart compositing...

But because I`m working on a setup with a second tint2-panel that is manually started through a button, and is opened and closed frequently, then this workaround isn`t good enough. Because I get the same compositing issue. It seems like Compton is having trouble if a tint2 panel is started while Compton is already running.

What could cause this? I need to be able to start tint2-panels on demand, AFTER startup, because i`m only starting the taskbar and systray during startup. The rest gets activated when I want and need them:)

I have read that there has been a issue with Compton being uncompatible with VLC, and VLC is back in the image I installed from, but I can`t imagine that such a bug in either VLC or Compton should cause the issues that I have with Compton and Tint 2. So what could this be? And how to solve it?

Last edited by ew (2013-02-10 00:13:56)


- apt-mark hold account

Offline

Help fund CrunchBang, donate to the project!

#2 2013-02-05 14:04:01

RichardGv
#! Member
From: People's Republic of China
Registered: 2013-01-13
Posts: 52

Re: [SOLVED-the issue was NOT related to Compton]

compton --config /dev/null

Last edited by RichardGv (2013-02-05 15:42:16)

Offline

#3 2013-02-05 15:44:52

ew
#! Die Hard
Registered: 2012-09-27
Posts: 1,975

Re: [SOLVED-the issue was NOT related to Compton]

Last edited by ew (2013-02-05 16:30:28)


- apt-mark hold account

Offline

#4 2013-02-06 05:42:29

RichardGv
#! Member
From: People's Republic of China
Registered: 2013-01-13
Posts: 52

Re: [SOLVED-the issue was NOT related to Compton]

Offline

#5 2013-02-06 11:21:46

ew
#! Die Hard
Registered: 2012-09-27
Posts: 1,975

Re: [SOLVED-the issue was NOT related to Compton]


- apt-mark hold account

Offline

#6 2013-02-06 14:18:17

RichardGv
#! Member
From: People's Republic of China
Registered: 2013-01-13
Posts: 52

Re: [SOLVED-the issue was NOT related to Compton]

Offline

#7 2013-02-07 16:00:13

ew
#! Die Hard
Registered: 2012-09-27
Posts: 1,975

Re: [SOLVED-the issue was NOT related to Compton]

ew@CB11-G580:~$ tint2 --version
tint2 version 652M
ew@CB11-G580:~$ compton --version
compton: unrecognized option '--version'
compton (development version)
usage: compton [options]

Last edited by ew (2013-02-07 21:28:13)


- apt-mark hold account

Offline

#8 2013-02-07 21:50:21

arclance
#! Die Hard
Registered: 2012-03-29
Posts: 987

Re: [SOLVED-the issue was NOT related to Compton]

strace "command you normally start tint2 with"

Last edited by arclance (2013-02-07 21:57:01)

Offline

#9 2013-02-08 05:45:20

RichardGv
#! Member
From: People's Republic of China
Registered: 2013-01-13
Posts: 52

Re: [SOLVED-the issue was NOT related to Compton]

ew@CB11-G580:~$ tint2 --version
tint2 version 652M
ew@CB11-G580:~$ compton --version
compton: unrecognized option '--version'
compton (development version)
usage: compton [options]

Last edited by RichardGv (2013-02-08 05:58:32)

Offline

#10 2013-02-08 11:22:29

ew
#! Die Hard
Registered: 2012-09-27
Posts: 1,975

Re: [SOLVED-the issue was NOT related to Compton]

strace "command you normally start tint2 with"

- apt-mark hold account

Offline

#11 2013-02-08 12:41:03

RichardGv
#! Member
From: People's Republic of China
Registered: 2013-01-13
Posts: 52

Re: [SOLVED-the issue was NOT related to Compton]

strace tint2 &> /tmp/out.txt
strace tint2 2&>1 > /tmp/out.txt

Offline

#12 2013-02-08 13:08:09

ew
#! Die Hard
Registered: 2012-09-27
Posts: 1,975

Re: [SOLVED-the issue was NOT related to Compton]

Last edited by ew (2013-02-08 13:09:40)


- apt-mark hold account

Offline

#13 2013-02-08 13:08:18

arclance
#! Die Hard
Registered: 2012-03-29
Posts: 987

Re: [SOLVED-the issue was NOT related to Compton]

Offline

#14 2013-02-08 23:38:03

ew
#! Die Hard
Registered: 2012-09-27
Posts: 1,975

Re: [SOLVED-the issue was NOT related to Compton]

I haven`t gotten around to it yet, but to clear up any confusion about task icons and launcer icons. The vertical bar to the left contains only launchers, and have no other function. The horisontal bar at the top, is the default tint2bar that comes with Waldorf. It contains taskbar, systray. clock and battery. No launchers in that bar... I will add stuff to this post, as I have any thing to report... I have a little bit of time right now, but I don`t know how long it lasts. When the puppy wakes up again, then I have to take care of her. Housebreaking her you know. Have to watch her 24/7:)


- apt-mark hold account

Offline

#15 2013-02-09 05:33:05

RichardGv
#! Member
From: People's Republic of China
Registered: 2013-01-13
Posts: 52

Re: [SOLVED-the issue was NOT related to Compton]

--- src/server.c~	2013-02-09 11:28:01.929983406 +0800
+++ src/server.c	2013-02-09 12:53:39.299946358 +0800
@@ -391,23 +391,10 @@
 		server.colormap32 = XCreateColormap(server.dsp, server.root_win, visual, AllocNone);
 	}
 
-	if (visual && server.composite_manager != None && snapshot_path == 0) {
-		XSetWindowAttributes attrs;
-		attrs.event_mask = StructureNotifyMask;
-		XChangeWindowAttributes (server.dsp, server.composite_manager, CWEventMask, &attrs);
-
-		server.real_transparency = 1;
-		server.depth = 32;
-		printf("real transparency on... depth: %d\n", server.depth);
-		server.colormap = XCreateColormap(server.dsp, server.root_win, visual, AllocNone);
-		server.visual = visual;
-	}
-	else {
 		// no composite manager or snapshot mode => fake transparency
 		server.real_transparency = 0;
 		server.depth = DefaultDepth(server.dsp, server.screen);
 		printf("real transparency off.... depth: %d\n", server.depth);
 		server.colormap = DefaultColormap(server.dsp, server.screen);
 		server.visual = DefaultVisual(server.dsp, server.screen);
-	}
 }

Offline

#16 2013-02-09 21:42:31

ew
#! Die Hard
Registered: 2012-09-27
Posts: 1,975

Re: [SOLVED-the issue was NOT related to Compton]

Ok. I probably should tell you that I`m on Siduction 3.6.10 kernel, and have the sid repos activated in my software sources, so many packaaages gets upgraded beyond current stable build. I had to do this because my system freezes on wheezy kernels, but newer kernel fixes that issue. Anyway, I had the same issues with tint2 with the default Waldorf install, kernel 3.2.0.3 and 3.2.0.4, so it`s not my new kernel or the sid repos that has caused any of this.

Yes, we know it`s NOT a compton issue because I am multibooting Linux-distros on this computer, and I only have these issues with Tint2 on this install. I have had several issues with incompability with ivy-bridge on other distros and kernels, like boot-issues. But I have never seen anything like the issues you see in the screenshots of my two bars. So I understand why you are a bit puzzled by the issue. I`m just as puzzled, because I`ve been trough 40-50 different distros with all kinds of DE/WM`s, but never seen anything simmular to this.

But you may have saved my day, and all my issues. Do I understand you correctly when I perceived it as your patch will disable true transparancy in Tint2, but leave it on for other apps like terminal-emulators etc... That would actually solve all my problems, because I do not need real transparancy in Tint2. It`s probably what I`m already doing in my workarounds, because If I understand you correctly, Tint2 starts with fake transparancy when no compositor is present, and continues using fake transparancy even though I start a compositor at later stage. That`s why it seems to work when I start Compton later. Then Tint2 isn`t using real transparancy at all. Thanks man, you have saved my day....

I will try your patch, and if it disables real transparancy in tint2, but still makes it possible to use real transparancy with other programs and apps, then I`m fine with it. Then the issue is solved for me, unless you feel a need to solve the issue for the Tint2-developers. I have no need to do that. Since I`m a newbie and Vastone is very experienced, she reported issues we discovered with the icons for the tint2-launchers. The launcher wouldn`t follow the icon-theme that was set. It did it for some apps, but for other apps it was impossible to get Tint2 to display the correct icons according to the theme. We had to manually track each icon and replace them with the one we wanted Tint2 to use. We found it so troublesome that we instead replaced the apps that Tint 2 didn`t use the correct icons for.

For example. We used the LinuxLex8 icon-theme. Tint2 agreed to use the LinuxLex8-icon for "medit", but not for "Geany", so we used "Medit" instead. The same with Thunar. We replaced it with SpaceFM, since Tint2 agreed with the icon for SpaceFM. Also, most people would want Tint2 to use the same icons for tasks, as it uses for launchers. But that turned out to be quite difficult to achieve. Anyway, as I understand it, the Tint2-developers wouldn`t do anything with this issue, so we just have to live with it...

So if it`s ok for you, then I thank you very much for solving my issue with you patch. I have no need of real transparancy in Tint2, so if you don`t see the need either, then I guess we`re both happy. By the way, thanks for the tip about the shadows around my CPU/MEM/HDD/NET-monitor. It looks much better without the sshadow:)

Last edited by ew (2013-02-09 21:47:29)


- apt-mark hold account

Offline

#17 2013-02-10 00:10:46

ew
#! Die Hard
Registered: 2012-09-27
Posts: 1,975

Re: [SOLVED-the issue was NOT related to Compton]

Big thanks to RichardGv. I patched tint2 with the patch you provided, and now everything works perfectly. Finally I`m able to set up my Tint2-bars like I want them, without any distortion or corruptions of the icons. I`m able to do this without sacrifizing compositing in general, because Compton works like a charm, and I`m able to use the default autostart-file in Waldorf, without delaying any startup-entrys. Not even Conky.
The patch was perfect, and is stored in my dropbox-folder for other occations. Thanks man:)))

Last edited by ew (2013-02-10 00:17:59)


- apt-mark hold account

Offline

#18 2013-02-10 15:19:42

RichardGv
#! Member
From: People's Republic of China
Registered: 2013-01-13
Posts: 52

Re: [SOLVED-the issue was NOT related to Compton]

#define DEBUG_ICON_SEARCH 0

Last edited by RichardGv (2013-02-10 15:33:59)

Offline

#19 2013-02-10 22:42:04

ew
#! Die Hard
Registered: 2012-09-27
Posts: 1,975

Re: [SOLVED-the issue was NOT related to Compton]

#---------------------------------------------
# TINT2 CONFIG FILE
#---------------------------------------------
# For more information about tint2, see:
# http://code.google.com/p/tint2/wiki/Welcome
#
# For more config file examples, see:
# http://crunchbanglinux.org/forums/topic/3232/my-tint2-config/

# Background definitions
# ID 1
rounded = 0
border_width = 0
background_color = #000000 20
border_color = #828282 0

# ID 2 - task active
rounded = 1
border_width = 0
background_color = #d8d8d8 30
border_color = #d8d8d8 30

# ID 3 - task
rounded = 1
border_width = 0
background_color = #000000 0
border_color = #000000 0

# ID 4
rounded = 1
border_width = 1
background_color = #888888 20
border_color = #ED2323 60

# ID 5 - taskbar
rounded = 0
border_width = 1
background_color = #000000 0
border_color = #000000 0

# ID 6 - active taskbar
rounded = 0
border_width = 1
background_color = #d8d8d8 8
border_color = #d8d8d8 0

# ID 7 - tooltip
rounded = 3
border_width = 0
background_color = #222222 90
border_color = #222222 90

# ID 8
rounded = 1
border_width = 1
background_color = #888888 20
border_color = #888888 20

# Panel
panel_monitor = all
panel_position = top center horizontal
panel_items = TSBC
panel_size = 100% 30
panel_margin = 0 -1
panel_padding = 0 0
panel_dock = 0
wm_menu = 1
panel_layer = bottom
panel_background_id = 1

# Panel Autohide
autohide = 0
autohide_show_timeout = 0.3
autohide_hide_timeout = 1.5
autohide_height = 6
strut_policy = follow_size

# Taskbar
taskbar_mode = multi_desktop
taskbar_padding = 6 0 6
taskbar_background_id = 5
taskbar_active_background_id = 6
taskbar_name = 1
taskbar_name_background_id = 0
taskbar_name_active_background_id = 0
taskbar_name_font = Liberation Sans 9
taskbar_name_font_color = #828282 100
taskbar_name_active_font_color = #828282 100

# Tasks
urgent_nb_of_blink = 20
task_icon = 1
task_text = 0
task_centered = 1
task_maximum_size = 40 40
task_padding = 2 2
task_background_id = 3
task_active_background_id = 2
task_urgent_background_id = 4
task_iconified_background_id = 3

# Task Icons
task_icon_asb = 80 0 0
task_active_icon_asb = 100 0 0
task_urgent_icon_asb = 100 0 0
task_iconified_icon_asb = 80 0 0

# Fonts
task_font = Liberation Sans 06_55 6
task_font_color = #828282 60
task_active_font_color = #828282 100
task_urgent_font_color = #FFFFFF 100
task_iconified_font_color = #d8d8d8 60
font_shadow = 0

# Launcher
launcher_padding = 8 4 4
launcher_background_id = 0
launcher_icon_size = 24
# Specify icon theme names with launcher_icon_theme. 
# if you have an XSETTINGS manager running (like xfsettingsd), tint2 will follow your current theme.
#launcher_icon_theme = gnome-dust
# Each launcher_item_app must be a full path to a .desktop file
#launcher_item_app = /usr/share/applications/terminator.desktop
#launcher_item_app = /usr/share/applications/xfce4-file-manager.desktop
#launcher_item_app = /usr/share/applications/gedit.desktop
#launcher_item_app = /usr/share/applications/iceweasel.desktop

# System Tray
systray = 1
systray_padding = 4 2 3
systray_sort = right2left
systray_background_id = 0
systray_icon_size = 24
systray_icon_asb = 100 0 0

# Clock
time1_format = %H:%M
time1_font = Liberation Sans 11
#time2_format = %A %d %B
#time2_font = Liberation Sans 6
clock_font_color = #b5b5b5 100
clock_padding = 12 4
clock_background_id = 0
clock_lclick_command = gsimplecal
clock_rclick_command = gsimplecal

# Tooltips
tooltip = 1
tooltip_padding = 2 2
tooltip_show_timeout = 0.0
tooltip_hide_timeout = 0.0
tooltip_background_id = 7
tooltip_font_color = #d8d8d8 100
tooltip_font = Liberation Sans normal 9.0

# Mouse
mouse_middle = none
mouse_right = toggle
mouse_scroll_up = toggle
mouse_scroll_down = iconify

# Battery
battery = 1
battery_low_status = 20
battery_low_cmd = notify-send "battery low"
battery_hide = 96
bat1_font = Liberation Mono 8
bat2_font = Liberation Mono 8
battery_font_color = #b5b5b5 100
battery_padding = 2 0
battery_background_id = 0

# End of config

- apt-mark hold account

Offline

#20 2013-02-11 12:51:30

RichardGv
#! Member
From: People's Republic of China
Registered: 2013-01-13
Posts: 52

Re: [SOLVED-the issue was NOT related to Compton]

Last edited by RichardGv (2013-02-11 12:51:54)

Offline

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.
Server: bleh

Debian Logo