Gnome + XMonad: tint disappears on click

[GoogleCodeExporter]

What steps will reproduce the problem?
1. open tint
2. click on it

What is the expected output? What do you see instead?
Switch focussed task/desktop
Tint disappears, without closing. Notice that XMonad does not see that tint
window has been disappeared, since the maximized windows don't cover the
empty space. 

What version of the product are you using? On what operating system?
I tested with tint 0.6 stable and svn trunk
I use Ubuntu 8.10 64bit, Xmonad 0.8, Gnome 2.24.1
XMonad is used as Winwod Manager for Gnome
Gnome-panel running

Please provide any additional information below.
I used this configuration on another computer with Ubuntu 8.04 32bit
/XMonad 0.7 /Gnome 2.22 and the problem does not verify.
On the PC with trouble I check that tint + XMonad 0.8 without Gnome and
tint + Gnome without XMonad works out of the box

Original issue reported on code.google.com by guancio@gmail.com on 3 Dec 2008 at 11:48

[GoogleCodeExporter]

I noticed that when the problem occurs, Tint correctly select the focused
task/desktop, before that the taskbar window disappears

Original comment by guancio@gmail.com on 3 Dec 2008 at 11:51

[GoogleCodeExporter]

Original comment by thilo...@gmail.com on 30 Dec 2008 at 3:22

• Changed state: Accepted

[GoogleCodeExporter]

if you have tint2, perhaps you can do more test:
- try option task_icon = 1 and task_text = 0 
- and then try option task_icon = 0 and task_text = 1 

to see if the problem is specific to text or icon drawing...

Original comment by thilo...@gmail.com on 6 Jun 2009 at 7:51

[GoogleCodeExporter]

I've testes both suggested options
(task_icon = 1 and task_text = 0)
and 
(task_icon = 0 and task_text = 1)
but Yint2 continues to disappears.
Now I use Arch linux with LXDE and the problem persists

Original comment by guancio@gmail.com on 12 Jun 2009 at 1:08

[GoogleCodeExporter]

Defect persists in tint2 0.9; it makes it unusable with xmonad (which is a 
shame; 
xmonad needs a 3rd party system tray utility)

Original comment by leo.alek...@gmail.com on 20 Mar 2010 at 3:16

[GoogleCodeExporter]

could you try
panel_layer=top
in your tint2rc... Maybe this solves the problem?

Original comment by Andreas.Fink85 on 20 Mar 2010 at 3:11

[GoogleCodeExporter]

it doesn't solve the problem

I'm, too, really sorry tint2 doesn't work with XMonad, because I like them much 
and
they would complement each other well

Original comment by vcu...@gmail.com on 16 Apr 2010 at 2:22

[GoogleCodeExporter]

btw, any click on any place on tint makes it disappear, but the process doesn't 
quit

Original comment by vcu...@gmail.com on 16 Apr 2010 at 2:25

[GoogleCodeExporter]

Issue 236 seems to be a duplicate bug

Original comment by vcu...@gmail.com on 16 Apr 2010 at 2:26

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have the same problem when using Xmonad 0.9 + xmobar 0.9.2 + tint2 0.9.
After starting tint2 is over xmobar, above. After clicking on the panel tint2 
it moves 
back and xmobar turns up blocking tint3. Now even if you click on tint2 it 
remains 
inactive behind.

Original comment by deepbad...@gmail.com on 18 May 2010 at 6:21

[GoogleCodeExporter]

latest SVN r461 have a way to fixed this issue.
you have to take care in your config file
- with option panel_layer = bottom, tint2 try to stay behind all others windows
- with option panel_layer = top or normal, tint2 doesn't change the stack order

Original comment by thilo...@gmail.com on 18 May 2010 at 8:55

[GoogleCodeExporter]

Thank you, after install latest SVN r461 it works, problem is solved.

Original comment by deepbad...@gmail.com on 18 May 2010 at 2:20

[GoogleCodeExporter]

good news.

Original comment by thilo...@gmail.com on 18 May 2010 at 4:16

• Changed state: Fixed