Seg Fault

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Specify a tint2rc that was working before instead of the default
2.
3.

What is the expected output? What do you see instead?
A beautiful taskbar.  Segmentation fault.

What version of the product are you using? On what operating system?
tint2-svn.  Arch Linux.

Please provide any additional information below.
I upgraded to Arch from Xubuntu, and after moving my tintrc file over from a 
working envirnoment it is now caused Tint to crash.  I've tried mutliple 
versions of tint from the repositories and from AUR.  

real transparency on... depth: 32
xRandr: Found crtc's: 2
xRandr: Linking output LVDS1 with crtc 1
tint2 : nb monitor 1, nb monitor used 1, nb desktop 1
real transparency on... depth: 32
xRandr: Found crtc's: 2
xRandr: Linking output LVDS1 with crtc 1
tint2 : invalid option "panel_mode",
  upgrade tint2 or correct your config file
tint2 : invalid option "task_margin",
  upgrade tint2 or correct your config file
tint2 : nb monitor 1, nb monitor used 1, nb desktop 1
Segmentation fault

Original issue reported on code.google.com by george.f...@gmail.com on 20 Feb 2011 at 6:52

Attachments:

• tint2rc

[GoogleCodeExporter]

Thanks for your report, we're going to fix this in svn. In the meantime I 
believe you can avoid the problem by specifying a background id for the clock 
in your tint2rc, for example like this:

clock_background_id = 0

Original comment by mrovi%in...@gtempaccount.com on 20 Feb 2011 at 7:20

• Changed state: Accepted

[GoogleCodeExporter]

Awesome, it's back!  

Thanks!

(It doesn't draw all the way to the ends of the screen though, for some reason?)

Original comment by george.f...@gmail.com on 20 Feb 2011 at 8:10

[GoogleCodeExporter]

Are you talking about those 2 pixels at the left and the right? That's because 
you specified a horizontal margin of 4. See 
http://code.google.com/p/tint2/wiki/Configure#Panel

for full width you need to have:
panel_margin = 0 0

instead what you have now is:
panel_margin = 4 0

Original comment by mrovi%in...@gtempaccount.com on 20 Feb 2011 at 10:25

[GoogleCodeExporter]

Sorry for the mistake + thank you for helping me with it.

Original comment by george.f...@gmail.com on 21 Feb 2011 at 4:39

[GoogleCodeExporter]

You're welcome! :)

Original comment by mrovi%in...@gtempaccount.com on 21 Feb 2011 at 4:48

[GoogleCodeExporter]

Original comment by mrovi9...@gmail.com on 21 Jan 2015 at 11:31

• Changed state: Fixed