Closed GoogleCodeExporter closed 8 years ago
IMHO, issue 435 is the same.
Original comment by nema.ar...@gmail.com
on 1 Sep 2013 at 8:15
[deleted comment]
[deleted comment]
Hi, same issue here. My graphic card is also a HD Graphics 4000, though I don't
know if it's the problem...
Original comment by elBoulan...@gmail.com
on 14 Sep 2013 at 10:33
[deleted comment]
Hey ! I just found a solution !
I changed the acceleration method of the Intel HD4000 from UXA to SNA. It's
something you configure in Xorg. Procedure for that can be found here:
https://wiki.archlinux.org/index.php/Intel_Graphics#Choose_acceleration_method
You can check which acceleration method is currently in use with the command:
$ cat /var/log/Xorg.0.log | grep -i -e uxa -e sna
This page is also interesting:
http://askubuntu.com/questions/225356/how-can-i-enable-the-sna-acceleration-meth
od-for-intel-cards-under-ubuntu-12-04
SNA is said to be less stable than UXA, we'll see...
Original comment by elBoulan...@gmail.com
on 14 Sep 2013 at 11:37
Sweet!! Can confirm that this works. Great job.
Original comment by nema.ar...@gmail.com
on 15 Sep 2013 at 2:15
Same here but I cannot get SNA to work. I am thinking of adding an option to
disable transparency as a workaround.
Original comment by mrovi9...@gmail.com
on 21 Jan 2015 at 11:54
Issue 435 has been merged into this issue.
Original comment by mrovi9...@gmail.com
on 21 Jan 2015 at 11:55
Issue 439 has been merged into this issue.
Original comment by mrovi9...@gmail.com
on 21 Jan 2015 at 11:57
Same issue described on this thread
http://crunchbang.org/forums/viewtopic.php?id=24480
Original comment by mrovi9...@gmail.com
on 28 Jan 2015 at 3:52
Original comment by mrovi9...@gmail.com
on 1 Feb 2015 at 11:49
Original comment by mrovi9...@gmail.com
on 20 Mar 2015 at 10:16
Fixed in r734. If there are any side effects let me know.
Original comment by mrovi9...@gmail.com
on 20 Mar 2015 at 10:17
Just tried it here and it looks OK, geany icon (and others) is displayed
properly, with both UXA and SNA methods. Thanks !
Original comment by elBoulan...@gmail.com
on 20 Mar 2015 at 11:27
However there's a side effect, now the panel doesn't fill the screen as it
should, there's a slight gap at one side of the screen. Here is a sample of my
conf file:
panel_position = bottom left vertical
panel_size = 100% 52
So my panel is vertical, left side of the screen, and it should fill the whole
screen vertically. But at the top of the screen, there's a gap of a few pixels.
It doesn't matter if I configure the vertical position to 'bottom' or 'top',
there's always a gap at the top of the screen.
I can confirm that this behavior doesn't happen if I launch the debian version
of tint2, it's only with the current SVN version.
Original comment by elBoulan...@gmail.com
on 20 Mar 2015 at 11:51
This is probably a regression introduced by another patch.
Could you please send me a full tint2rc (either by attaching here or on
mrovi9000@gmail.com)? Also, are you using Openbox or some other window manager?
Original comment by mrovi9...@gmail.com
on 21 Mar 2015 at 9:43
Here comes my tint2rc attached. Indeed, Openbox is my window manager.
Original comment by elBoulan...@gmail.com
on 22 Mar 2015 at 8:52
Attachments:
Thanks.
I don't see any gap here :(
But I think I know what the problem is. Until now, there was a bug in the
treatment of option "panel_dock"; tint2 was sometimes placed in the dock even
though it was set to 0. A side effect of that was that if you specified any
margins in obconf > Margins, tint2 was previously ignoring them, but now it is
forced to respect them.
Could you please check with obconf if you have any margins there, and set them
to zero?
Alternatively, you can try setting "panel_dock = 1" (unless you have other
reasons not to do so).
If this doesn't help you, it would be useful for me to see your Openbox config
file (~/.config/openbox/rc.xml).
Original comment by mrovi9...@gmail.com
on 22 Mar 2015 at 9:11
Great !
You're right, I had a top margin defined in my openbox conf, here's a sample of
the file:
<!-- You can reserve a portion of your screen where windows will not cover when
they are maximized, or when they are initially placed.
Many programs reserve space automatically, but you can use this in other
cases. -->
<margins>
<top>1</top>
<bottom>0</bottom>
<left>0</left>
<right>0</right>
</margins>
I also tried the tint2 "panel_dock" setting. If set to 1, the openbox margins
are ignored, but there's an ugly grey borderline around tint2. Hell if I know
where it comes from, ob or tint2.
So I just let the tint2 "panel_dock" setting to zero, and configure the openbox
top margin to zero, it works like a charm.
Original comment by elBoulan...@gmail.com
on 22 Mar 2015 at 9:36
Perfect, I'll add it to the FAQ.
And btw, the border is drawn by openbox.
Original comment by mrovi9...@gmail.com
on 22 Mar 2015 at 9:37
Thanks for the explanations :)
Original comment by elBoulan...@gmail.com
on 22 Mar 2015 at 9:45
Original issue reported on code.google.com by
nema.ar...@gmail.com
on 31 May 2013 at 2:31