alpha BL: tint 2 freezing and reverting to older instance

schwim · 2015-05-18 19:01:08

Heya everyone!

Something odd on my clean Jessie and alpha BL script: When I click on my Tint2 panel, it not only freezes, but the clock reverts to a previous time, the same each time (17:28) Left and right clicking on the panel space results in no action being taken. No menu, no second workspace, nada.

Killing and restarting tint2 gives me a fresh instance with a working clock..... until I click on it, at which time it freezes and the clock shows 17:28 again.

Applications and menu work fine outside of the tint2 space, it seems to be just that particular application that is having the issue.

Any thoughts on what might be the issue?

Thanks for your time!

Sector11 · 2015-05-18 19:05:03

Can you post your tint2.config file.

Head_on_a_Stick · 2015-05-18 19:10:19

Try killing tint2:

killall tint2

Then start it up again from the terminal (no ampersand):

tint2

And post any errors returned to the terminal window when you click on the panel.

schwim · 2015-05-18 19:13:13

Sector11 wrote:

Can you post your tint2.config file.

Sure!

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

# Background definitions
# ID 1
rounded = 0
border_width = 0
background_color = #000000 40
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 = LTSC
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 = 0
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 = Faenza-Dark-Bunsen

# Each launcher_item_app must be a full path to a .desktop file
# this will have to be made:
launcher_item_app = /usr/share/applications/bl-www-browser.desktop
launcher_item_app = /usr/share/applications/bl-file-manager.desktop
launcher_item_app = /usr/share/applications/bl-text-editor.desktop
launcher_item_app = /usr/share/applications/bl-terminal-emulator.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

Last edited by schwim (2015-05-18 19:22:32)

schwim · 2015-05-18 19:15:20

Head_on_a_Stick wrote:

Try killing tint2:
killall tint2
Then start it up again from the terminal (no ampersand):
tint2
And post any errors returned to the terminal window when you click on the panel.

Interesting, in spite of killall, it's still showing a previously running instance:

I get the icons to show on the original tint2 startup, but it shows errors and no icons on this restart. Issue persists when I click on the new Tint2 panel after this method of restart as well.

schwim@schwim-bl-vm:~$ killall tint2
schwim@schwim-bl-vm:~$ tint2
real transparency off.... depth: 24
xRandr: Found crtc's: 1
xRandr: Linking output VGA-0 with crtc 0
tint2 : another systray is running
NO XSETTINGS manager, tint2 use config 'launcher_icon_theme'.
tint2 : nb monitor 1, nb monitor used 1, nb desktop 2
Loading Faenza-Dark-Bunsen. Icon theme : 'Faenza-Dark-Bunsen', 'Faenza-Bunsen', 'gnome', 'hicolor',
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen/apps/22/web-browser.png
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen/apps/22/system-file-manager.png
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen/apps/22/accessories-text-editor.png
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen/apps/22/utilities-terminal.png

Last edited by schwim (2015-05-18 19:23:00)

Head_on_a_Stick · 2015-05-18 19:20:31

schwim wrote:

schwim@schwim-bl-vm:~$ killall tint2
schwim@schwim-bl-vm:~$ tint2
real transparency off.... depth: 24
xRandr: Found crtc's: 1
xRandr: Linking output VGA-0 with crtc 0
tint2 : another systray is running
NO XSETTINGS manager, tint2 use config 'launcher_icon_theme'.
tint2 : nb monitor 1, nb monitor used 1, nb desktop 2
Loading Faenza-Dark-Bunsen. Icon theme : 'Faenza-Dark-Bunsen', 'Faenza-Bunsen', 'gnome', 'hicolor',
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen/apps/22/web-browser.png
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen/apps/22/system-file-manager.png
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen/apps/22/accessories-text-editor.png
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen/apps/22/utilities-terminal.png

I get the exact same output from my panel -- do any new errors get added when the panel is suffering the problems you have described?

Also, please use code tags rather than quote tags when posting terminal output (it makes it much more readable & easier to scroll through) -- quote this post to see how I have done this

schwim · 2015-05-18 19:25:43

Done and done!

I did find this in one of the open terminal windows from which tint2 was started. I didn't see this any other time I did a restart though:

(process:7385): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

Head_on_a_Stick · 2015-05-18 19:36:15

schwim wrote:

(process:7385): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

That is probably compton-related; I get that message when restarting bl-compositor.

Try killing compton & see if that stops your problems.

I presume your tint2 has a PID of 7385?

pidof tint2

schwim · 2015-05-18 20:00:29

My tint2 pid after restart is 680. I'll give compton a shot as soon as the issue occurs again. OS restart has so far squashed the issue.

Head_on_a_Stick · 2015-05-18 20:13:06

Just to clarify: the error messages shown via the terminal *when the problems are occurring* are what we are interested in here.

schwim · 2015-05-18 20:27:13

Those that I posted were during the issue. The issue is not occurring currently and the restart is very clean:

schwim@schwim-bl-vm:~$ killall tint2
schwim@schwim-bl-vm:~$ tint2
real transparency off.... depth: 24
xRandr: Found crtc's: 1
xRandr: Linking output VGA-0 with crtc 0
NO XSETTINGS manager, tint2 use config 'launcher_icon_theme'.
tint2 : nb monitor 1, nb monitor used 1, nb desktop 2

Head_on_a_Stick · 2015-05-18 20:38:16

OK, lets try another tack -- add your user to the "systemd-journal" group:

sudo gpasswd -a schwim systemd-journal

Log out & back in again to effect this change.

Then open another terminal & run this command and see if that shows anything when the problems occur:

journalctl -xf

tknomanzr · 2015-05-19 01:28:59

Also, check ~/.xsession-errors for tint2 related stuff.i would blame my compton config if I had to make a wild guess though.

johnraff · 2015-06-03 08:45:24

This looks like the same issue: in a VirtualBox BL install sometimes, for no apparent reason, tint2 freezes and becomes unusable. The config file is default BL. Startup is via

(sleep 2s && bl-tint2-session --autostart) &

When it happens, 'killall tint2' has no effect, nor any signal except 9:

john@bunsen2:~$ killall tint2 # no effect
john@bunsen2:~$ pgrep -a tint2
1032 tint2
john@bunsen2:~$ kill 1032 # no effect
john@bunsen2:~$ kill -HUP  1032 # no effect
john@bunsen2:~$ kill -INT  1032 # no effect
john@bunsen2:~$ kill -TERM  1032 # no effect
john@bunsen2:~$ kill -STOP  1032 # no effect
john@bunsen2:~$ kill -KILL  1032 # FINALLY!

If tint2 is then restarted it runs OK.

damo · 2015-06-03 10:34:48

johnraff wrote:

This looks like the same issue: in a VirtualBox BL install sometimes, for no apparent reason, tint2 freezes and becomes unusable. The config file is default BL. Startup is via
(sleep 2s && bl-tint2-session --autostart) &
When it happens, 'killall tint2' has no effect, nor any signal except 9:
john@bunsen2:~$ killall tint2 # no effect
john@bunsen2:~$ pgrep -a tint2
1032 tint2
john@bunsen2:~$ kill 1032 # no effect
john@bunsen2:~$ kill -HUP  1032 # no effect
john@bunsen2:~$ kill -INT  1032 # no effect
john@bunsen2:~$ kill -TERM  1032 # no effect
john@bunsen2:~$ kill -STOP  1032 # no effect
john@bunsen2:~$ kill -KILL  1032 # FINALLY!
If tint2 is then restarted it runs OK.

I also occasionally have got a freeze with tint2 on my main BL install, but not in a VBox VM.
FYI After discussions with @johnraff I have changed the scripts to use "kill PID", and dropped the --autostart arg so that tint2s are killed anyway if running, and restarted. (It is an easy fix to add "-KILL" if necessary.)

johnraff · 2015-06-04 01:09:16

Easy to add -KILL but it shouldn't be necessary. If tint2 needs KILL then it has a bug, or there's something weird about the way we're launching it.

(btw the KILL signal is different from 'kill pid'. 'kill' uses TERM by default.)

Last edited by johnraff (2015-06-04 01:10:56)

damo · 2015-06-04 01:47:44

Possible recent bug? Issue 471: tint2 becomes unresponsive

Maybe @ov (Tint2 dev) might have some ideas?

johnraff · 2015-06-04 07:57:55

It looks similar - related to startup notification?

KrunchTime · 2015-06-07 02:07:44

I provided a solution to this issue in the BunsenLabs Development Team thread, but I'm going to repeat it here. I discovered the solution purely because I didn't like the tint2 launcher apps. Remove or comment out all launcher lines in /home/<user>/.config/tint2/tint2rc and the freezing will stop.

Last edited by KrunchTime (2015-06-07 02:08:33)

johnraff · 2015-06-07 03:56:52

It might well be connected with the launchers in some way.

This sometimes works to trigger the freezes - open 2 or 3 windows: file manager, text editor.. then open 5 or 6 terminals in quick sucession, clicking on the launcher, then close them quickly with multiple Ctrl+d. (Chose terminals because they open and close quickly.)

That did it a few times but when I went back just now everything was OK... drat....

When the freeze hits, only KILL is strong enough to kill the tint2 processes, so just to get a working panel back I added it to /usr/bin/bl-tint2restart on the test system. In the process of playing with that I found that sometimes there were several identical tint2 processes running. Also, there seemed to be zombie processes of bl-tint2restart itself hanging around...

So @damo I took the liberty of hacking bl-tint2restart some more so that as well as killing with KILL it wouldn't restart multiple instances of the same command and launches with setsid so the script can shut down without having to worry about its children. Also took out the fork from 'bl-compositor --restart' which didn't seem to be making any difference. This isn't in BunsenLabs, just here, for opinions:

#!/bin/bash
#
# bl-tint2restart to be used by bl-tint2-pipemenu
# Written for BunsenLabs Linux by <damo> June 2015

declare -A commands # associative array
while read pid cmd; do
    if [[ ${cmd%% *} = tint2 ]]; then
        kill -KILL "$pid"
        commands[$cmd]=1 # duplicate commands will be launched only once
    fi
done <<< "$(pgrep -a tint2)"

sleep 1
for i in "${!commands[@]}" # go through the indexes
do
    (setsid $i &)
    sleep 0.1
done

sleep 1
bl-compositor --restart  # restart compositor

exit 0

ov · 2015-06-09 20:55:23

Hi everyone,

I have just noticed this thread. This is most likely bug 471, as someone has posted above. If I understand correctly, BL uses the same packages as Jessie? This means that the version of tint2 is quite old, from what I can see: http://ftp.debian.org/debian/pool/main/t/tint2/ it's from 2012.

I don't see any way of fixing this problem without recompiling (either a newer version, or the same old version but disabling startup notifications).

I will try to find out if they are willing to accept patches that fix this issue.

Edit: I created a new branch in the repository with startup notifications disabled. Everything else in the code is identical to the one from the debian package. I would appreciate it if you confirmed if this fixes the issue:

sudo apt-get build-dep tint2
cd
mkdir tint2-debian-test
cd tint2-debian-test
wget -O tint2-debian-test.tar.gz 'https://gitlab.com/o9000/tint2/repository/archive.tar.gz?ref=debian-test'
tar xzf tint2-debian-test.tar.gz
cd tint2.git
mkdir build
cd build
cmake ..
make
killall -9 tint2
./tint2

Last edited by ov (2015-06-09 21:42:58)

KrunchTime · 2015-06-09 22:47:34

@ov: You're right. I was going to suggest backporting from Testing/Unstable, but they're both using the same version. Question is, why in Unstable using such an outdated tint2 package? I thought Unstable was supposed to be bleeding edge.

ov · 2015-06-09 23:11:21

No new tint2 releases since 2011.

LabRat · 2015-06-10 01:52:01

@ov

http://crunchbang.org/forums/viewtopic.php?id=38696

ov · 2015-06-10 07:49:23

Yep Working on it. Almost there. There have been a couple of crashes recently that have delayed the release. Also my day job is sucking life out of me at the moment.

CrunchBang Linux

SEARCH

#1 2015-05-18 19:01:08

alpha BL: tint 2 freezing and reverting to older instance

#2 2015-05-18 19:05:03

Re: alpha BL: tint 2 freezing and reverting to older instance

#3 2015-05-18 19:10:19

Re: alpha BL: tint 2 freezing and reverting to older instance

#4 2015-05-18 19:13:13

Re: alpha BL: tint 2 freezing and reverting to older instance

#5 2015-05-18 19:15:20

Re: alpha BL: tint 2 freezing and reverting to older instance

#6 2015-05-18 19:20:31

Re: alpha BL: tint 2 freezing and reverting to older instance

#7 2015-05-18 19:25:43

Re: alpha BL: tint 2 freezing and reverting to older instance

#8 2015-05-18 19:36:15

Re: alpha BL: tint 2 freezing and reverting to older instance

#9 2015-05-18 20:00:29

Re: alpha BL: tint 2 freezing and reverting to older instance

#10 2015-05-18 20:13:06

Re: alpha BL: tint 2 freezing and reverting to older instance

#11 2015-05-18 20:27:13

Re: alpha BL: tint 2 freezing and reverting to older instance

#12 2015-05-18 20:38:16

Re: alpha BL: tint 2 freezing and reverting to older instance

#13 2015-05-19 01:28:59

Re: alpha BL: tint 2 freezing and reverting to older instance

#14 2015-06-03 08:45:24

Re: alpha BL: tint 2 freezing and reverting to older instance

#15 2015-06-03 10:34:48

Re: alpha BL: tint 2 freezing and reverting to older instance

#16 2015-06-04 01:09:16

Re: alpha BL: tint 2 freezing and reverting to older instance

#17 2015-06-04 01:47:44

Re: alpha BL: tint 2 freezing and reverting to older instance

#18 2015-06-04 07:57:55

Re: alpha BL: tint 2 freezing and reverting to older instance

#19 2015-06-07 02:07:44

Re: alpha BL: tint 2 freezing and reverting to older instance

#20 2015-06-07 03:56:52

Re: alpha BL: tint 2 freezing and reverting to older instance

#21 2015-06-09 20:55:23

Re: alpha BL: tint 2 freezing and reverting to older instance

#22 2015-06-09 22:47:34

Re: alpha BL: tint 2 freezing and reverting to older instance

#23 2015-06-09 23:11:21

Re: alpha BL: tint 2 freezing and reverting to older instance

#24 2015-06-10 01:52:01

Re: alpha BL: tint 2 freezing and reverting to older instance

#25 2015-06-10 07:49:23

Re: alpha BL: tint 2 freezing and reverting to older instance

Board footer