Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#18929 - [terminator] We can't change the transparency

Attached to Project: Community Packages
Opened by darkvodka (darkvodka) - Friday, 02 April 2010, 13:30 GMT
Last edited by Dan Griffiths (Ghost1227) - Sunday, 04 April 2010, 01:47 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Dan Griffiths (Ghost1227)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:We can't change the transparency


Additional info:
* package version(s)
* config and/or log files etc.

package version : 0.91-1

Steps to reproduce:
Go in preferences, in profiles, in background, change the transparency ... there is no effect.
This task depends upon

Closed by  Dan Griffiths (Ghost1227)
Sunday, 04 April 2010, 01:47 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Bug was in vte, not terminator
Comment by julien (abala) - Friday, 02 April 2010, 14:15 GMT
Same problem with segfault if I try to open new terminator :
/usr/bin/termin[4953]: segfault at 0 ip b74ea768 sp bfff963c error 4 in libc-2.11.1.so[b7477000+141000]
Comment by coldsphinx (ColdSphinX) - Friday, 02 April 2010, 17:43 GMT
/usr/lib/python2.6/site-packages/terminatorlib/prefseditor.py line 548 is declared as "on_darken_background_scale_change_value(self, widget):" but the call is "on_darken_background_scale_change_value(self, widget, <ScrollType>, <float>)".
Comment by Mick (lunix) - Saturday, 03 April 2010, 09:54 GMT
I don't know if this is related or not. I'm happy to file it as a separate bug if needed.
I am unable to run terminator on x86_32.
I do not believe this is actually a terminator issue though as I downgraded from 0.91 to 0.90 & 0.14 and the same bug exists.

terminator -d
http://pastie.org/901486

In /var/log/everything.log is the following

Apr 3 19:15:54 pintara kernel: /usr/bin/termin[24778]: segfault at 0 ip b68eff6b sp bfb74ba0 error 4 in libcairo.so.2.10906.0[b6887000+aa000]
Apr 3 19:53:41 pintara kernel: /usr/bin/termin[32639]: segfault at 0 ip b68ebf6b sp bfaf9570 error 4 in libcairo.so.2.10906.0[b6883000+aa000]
Apr 3 20:12:14 pintara kernel: /usr/bin/termin[3952]: segfault at 0 ip b6a68f6b sp bfaa7230 error 4 in libcairo.so.2.10906.0[b6a00000+aa000]
Apr 3 20:13:46 pintara kernel: /usr/bin/termin[4010]: segfault at 0 ip b6960f6b sp bff65980 error 4 in libcairo.so.2.10906.0[b68f8000+aa000]

I have attached the output of a strace -f (PS. its fairly large)

I tried upgrading cairo to the pre-release version (1.9.6) (built from abs) but the problem still exists
Apr 3 19:15:49 pintara pacman: upgraded cairo (1.8.10-1 -> 1.9.6-1)

I haven't tried downgrading cairo as it would require downgrading too many deps
   terminator.strace (749.7 KiB)
Comment by Ionut Biru (wonder) - Saturday, 03 April 2010, 11:56 GMT
https://bugzilla.gnome.org/show_bug.cgi?id=614511


try reverting http://git.gnome.org/browse/vte/commit/?id=5f4f67f579c9530af716573d6aaafc9cdb060e09 in vte and report here.
Comment by Ionut Biru (wonder) - Saturday, 03 April 2010, 15:49 GMT
status using vte 0.24.0-2?
Comment by Filipp Andjelo (scorp) - Saturday, 03 April 2010, 18:26 GMT
Splitting terminator crashes with segmentation fault since last update.
Comment by Mick (lunix) - Saturday, 03 April 2010, 22:35 GMT
Bingo !
A quick _pacman -Syu_ later and vte-0.24.0-2 installed and terminator runs now.
No more segfault on startup and I can split screens etc

Woooo Thanks.

Loading...