WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: lxterminal assertion failed  (Read 650 times)

Offline andyj

  • Sr. Member
  • ****
  • Posts: 375
lxterminal assertion failed
« on: November 13, 2016, 12: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?


Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9008
Re: lxterminal assertion failed
« Reply #1 on: November 13, 2016, 09:03:52 PM »
lxterminal-0.20 is old (2014) and both vte and gtk3 have been updated many times since then - I'll take a look.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9008
Re: lxterminal assertion failed
« Reply #2 on: November 13, 2016, 09:48:58 PM »
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...

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9008
Re: lxterminal assertion failed
« Reply #3 on: November 13, 2016, 10:41:32 PM »
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

Offline andyj

  • Sr. Member
  • ****
  • Posts: 375
Re: lxterminal assertion failed
« Reply #4 on: November 18, 2016, 06: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.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9008
Re: lxterminal assertion failed
« Reply #5 on: November 18, 2016, 10:05:58 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?

Offline patrikg

  • Full Member
  • ***
  • Posts: 234
Re: lxterminal assertion failed
« Reply #6 on: November 19, 2016, 12: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


Offline andyj

  • Sr. Member
  • ****
  • Posts: 375
Re: lxterminal assertion failed
« Reply #7 on: November 19, 2016, 05: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.
« Last Edit: November 19, 2016, 05:32:33 AM by andyj »

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9008
Re: lxterminal assertion failed
« Reply #8 on: November 19, 2016, 08:26:09 PM »
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"
« Last Edit: November 20, 2016, 08:09:57 PM by Juanito »

Offline andyj

  • Sr. Member
  • ****
  • Posts: 375
Re: lxterminal assertion failed
« Reply #9 on: November 20, 2016, 04: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.