Tiny Core Linux

Tiny Core Extensions => TCE Corepure64 => Topic started by: andyj on November 13, 2016, 03:20:56 PM

Title: lxterminal assertion failed
Post by: andyj on November 13, 2016, 03:20:56 PM: I finally got around to running tce-update and now I get this trying to run lxterminal:

(lxterminal:9307): Gtk-WARNING **: GtkWindow 0x2190270 is drawn without a current allocation. This should not happen.
(lxterminal:9307): Gtk-WARNING **: GtkVBox 0x21c4180 is drawn without a current allocation. This should not happen.
(lxterminal:9307): Gtk-WARNING **: GtkVScrollbar 0x242a290 is drawn without a current allocation. This should not happen.
(lxterminal:9307): Gtk-WARNING **: GtkMenuBar 0x21c51d0 is drawn without a current allocation. This should not happen.
(lxterminal:9307): Gtk-WARNING **: GtkImageMenuItem 0x23841a0 is drawn without a current allocation. This should not happen.
(lxterminal:9307): Gtk-WARNING **: GtkAccelLabel 0x23833e0 is drawn without a current allocation. This should not happen.
(lxterminal:9307): Gtk-WARNING **: GtkImageMenuItem 0x2384ab0 is drawn without a current allocation. This should not happen.
(lxterminal:9307): Gtk-WARNING **: GtkAccelLabel 0x2383f80 is drawn without a current allocation. This should not happen.
(lxterminal:9307): Gtk-WARNING **: GtkImageMenuItem 0x2417650 is drawn without a current allocation. This should not happen.
(lxterminal:9307): Gtk-WARNING **: GtkAccelLabel 0x2416b70 is drawn without a current allocation. This should not happen.
(lxterminal:9307): Gtk-WARNING **: GtkImageMenuItem 0x241a240 is drawn without a current allocation. This should not happen.
(lxterminal:9307): Gtk-WARNING **: GtkAccelLabel 0x24199a0 is drawn without a current allocation. This should not happen.
(lxterminal:9307): Gtk-CRITICAL **: gtk_border_copy: assertion 'border_ != NULL' failed
Segmentation fault

What would have broken this? Do we need a gtk3 and/or lxterminal rebuild?
Title: Re: lxterminal assertion failed
Post by: Juanito on November 14, 2016, 12:03:52 AM: lxterminal-0.20 is old (2014) and both vte and gtk3 have been updated many times since then - I'll take a look.
Title: Re: lxterminal assertion failed
Post by: Juanito on November 14, 2016, 12:48:58 AM: I tried recompiling lxterminal and using a more recent version of vte-2.90, but the error remains.

I see debian uses lxterminal and vte compiled against gtk2 rather than gtk3 - perhaps this is a solution until lxterminal releases an update or perhaps the github version of lxterminal will work?

Otherwise, there's gnome-terminal...
Title: Re: lxterminal assertion failed
Post by: Juanito on November 14, 2016, 01:41:32 AM: got it - the github version of lxterminal will compile against the latest vte (as opposed to vte-2.90), which fixes the segfault.

The warnings remain, but don't seem to be a problem.

posted
Title: Re: lxterminal assertion failed
Post by: andyj on November 18, 2016, 09:12:20 PM: Now it opens, but I get this with alsa:

tc@box:~$ alsamixer
Error opening terminal: xterm-256color.

Do I need a link somewhere? Which xterm returns nothing.

Also, lxterminal now has a "feature". When I resize the window to make it taller OR shorter, it gets narrower. At least I can widen it afterwards.
Title: Re: lxterminal assertion failed
Post by: Juanito on November 19, 2016, 01:05:58 AM: Quote from: andyj on November 18, 2016, 09:12:20 PM
Now it opens, but I get this with alsa:

$ alsamixer
Error opening terminal: xterm-256color.
loading ncurses-terminfo fixes this - comment added to info file

Quote
Do I need a link somewhere? Which xterm returns nothing.
Oops - forgot the wrapper script, extension re-posted

Quote
Also, lxterminal now has a "feature". When I resize the window to make it taller OR shorter, it gets narrower. At least I can widen it afterwards.
I see the same with flwm - a bug in flwm, lxterminal or vte?
Title: Re: lxterminal assertion failed
Post by: patrikg on November 19, 2016, 03:30:38 AM: Some circumstances you could setting another terminal to support the program.
I do it this like these two ways:
export TERM=xterm
export TERM=linux
Title: Re: lxterminal assertion failed
Post by: andyj on November 19, 2016, 08:28:53 AM: The apps browser needs the wrapper script. We've been down that road already. The resizing thing doesn't affect aterm. Lilyterm segfaults, so I can't say about that. I am using flwm_topside in a VMware VM, using open-vm-tools (trying to get 10.1 ready for submission which is how all this started) on a Slackware 14.2 host using the open source radeon driver. Everything is 64 bit. It "could" be a video driver quirk somewhere in the stack, but right now I don't know of anything else having issues.

Is ncurses-terminfo a dependency or a "nice to have?". Dejavu-fonts-ttf deserves a mention in the info file as well. Without it whatever fonts lxterminal uses by default look kinda rough.
Title: Re: lxterminal assertion failed
Post by: Juanito on November 19, 2016, 11:26:09 PM: Quote from: andyj on November 19, 2016, 08:28:53 AM
Is ncurses-terminfo a dependency or a "nice to have?".
It only seems to be needed for lxterminal to display alsamixer, but there may be others - note that only xterm-256color is used for this

Quote
Dejavu-fonts-ttf deserves a mention in the info file as well. Without it whatever fonts lxterminal uses by default look kinda rough.
The info file already says "Optional deps: More font TCZs, load fontconfig then load lxterminal"
Title: Re: lxterminal assertion failed
Post by: andyj on November 20, 2016, 07:54:20 AM: Sorry I haven't looked at the info file in a while ::) I did notice though that while in an lxterminal window I loaded dejavu-fonts-ttf and started another lxterminal from the first and the fonts improved immediately, so it seems to "prefer" different fonts.