(old)Puppy Linux Discussion Forum

There's also a difference between varieties or rar file. It's an ever changing format that targets paid archive Winrar on Windows. There is a free and non-free version of unrar in the repos. The non-free one includes more formats that it can read and uncompress. There may be times where the file has been created in the latest version of Winrar and no Linux unrar will recognize it yet. Those could show themselves in silly things like not prompting for a password.

RAR 5.90   Copyright (c) 1993-2020 Alexander Roshal   26 Mar 2020
Trial version             Type 'rar -?' for help

Usage:     rar <command> -<switch 1> -<switch N> <archive> <files...>
               <@listfiles...> <path_to_extract\>

(gtkdialog4:10133): GLib-GObject-WARNING **: 00:19:06.330: g_object_get_is_valid_property: object class 'VteTerminal' has no property named 'inner-border'

(gtkdialog4:10133): Gdk-WARNING **: 00:19:06.343: Native Windows wider or taller than 32767 pixels are not supported

enrique wrote:

(gtkdialog4:10133): GLib-GObject-WARNING **: 00:19:06.330: g_object_get_is_valid_property: object class 'VteTerminal' has no property named 'inner-border'

(gtkdialog4:10133): Gdk-WARNING **: 00:19:06.343: Native Windows wider or taller than 32767 pixels are not supported

echo '<terminal><width>83</width></terminal>' | gtkdialog -s

export UEXTRACT_TERM=roxterm

echo '<terminal><width>83</width></terminal>' | gtkdialog -s

(gtkdialog:30967): GLib-GObject-WARNING **: 19:25:29.284: g_object_get_is_valid_property: object class 'VteTerminal' has no property named 'inner-border'

(gtkdialog:30967): Gdk-WARNING **: 19:25:29.294: Native Windows wider or taller than 32767 pixels are not supported
The program 'gtkdialog' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 255 error_code 11 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

SFR wrote:I just checked it in BusterDog-openbox_jwm-2019-12-29_32-bit.iso and there's something wrong with Gtkdialog itself (which is actually gtkwialog-0.8.7).
For some reason this code crashes X (under Openbox) or returns errors and doesn't work (under JWM):

SFR wrote: (gtkdialog4:10133): Gdk-WARNING **: 00:19:06.343: Native Windows wider or taller than 32767 pixels are not supported

I just checked it in BusterDog-openbox_jwm-2019-12-29_32-bit.iso and there's something wrong with Gtkdialog itself (which is actually gtkwialog-0.8.7).
For some reason this code crashes X (under Openbox) or returns errors and doesn't work (under JWM):

Code: Select all

echo '<terminal><width>83</width></terminal>' | gtkdialog -s

Gtkdialog binary imported from Slacko-5.7 works as expected.

root@xenial64:/mnt/live/mnt/sda1# gtkdialog --version
gtkdialog version 0.8.4 release (C) 2003-2007 Laszlo Pere, 2011-2012 Thunor
Built with support for: GTK+ 2, Glade, VTE.
root@xenial64:/mnt/live/mnt/sda1# echo '<terminal><width>83</width></terminal>' | gtkdialog -s

(gtkdialog:28186): GLib-GObject-WARNING **: g_object_get_valist: object class 'VteTerminal' has no property named 'inner-border'

(gtkdialog:28186): Gdk-WARNING **: Native Windows wider or taller than 32767 pixels are not supported
The program 'gtkdialog' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 286 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
root@xenial64:/mnt/live/mnt/sda1#

VTE
---
Gtkdialog's configure script will compile-in support for the Virtual
Terminal Emulator if it finds libvte and its development headers.
libvte source package -> http://ftp.gnome.org/pub/GNOME/sources/vte/

SFR wrote:Yes, turns out that the actual culprit is in Mick's fork (which, I assume, was used a base for Gtkwialog?), in this PR:
https://github.com/01micko/gtkdialog/pull/82

Reverting this particular change fixes VTE terminal in GTK2 build:

Code: Select all

- #if 0 //#if VTE_CHECK_VERSION(0,26,0)
+ #if VTE_CHECK_VERSION(0,26,0)

but I think it might be better to revert the whole commit, just in case.

Greetings!

woodenshoe-wi wrote:@SFR and @wiak

I changed automaton.c to stop using the 'inner-border' property, and 01micko merged it, so if you could try again and see if it is fixed or not please.

I didn’t think the 'inner-border' property was removed until the version of vte used for gtk+3, so I am puzzled that it would be causing problems in a gtk+2 build. Maybe the code for using the 'inner-border' property was buggy? I reused some of it for gtk+3 VTE support...

You shouldn’t have to do anything special to enable VTE support for a gtk+2 build. If you want to enable VTE support in a gtk+3 build, you will need to install the gtk+3 version of libvte, which is known to pkg-config as vte-2.91, and set some environment variables to make it use the gtk+3 version instead of the gtk+2 version.

Code: Select all

export VTE_CFLAGS=`pkg-config --cflags "vte-2.91"`
export VTE_LIBS=`pkg-config --libs "vte-2.91"`

Then you should have VTE support when you configure gtkdialog with --enable-gtk3

/* VTE is telling me that vte_terminal_get_padding() has been
* deprecated since 0.26 and that I should get 'inner-border'
* but GLib is telling me that 'VteTerminal' has no property
* named 'inner-border' so I have to go with the deprecated
* vte_terminal_get_padding() */

GtkBorder inner_border
...
g_object_get(G_OBJECT(widget), "inner-border", &inner_border, NULL);

GtkBorder *inner_border
...
gtk_widget_style_get (widget, "inner-border", &inner_border, NULL);
...
gtk_border_free (inner_border);

wiak wrote: ...
and planned to try instead something like (note especially use instead: inner_border as a 'pointer' to GtkBorder):

Code: Select all

GtkBorder *inner_border
...
gtk_widget_style_get (widget, "inner-border", &inner_border, NULL);
...
gtk_border_free (inner_border);

I'll maybe look into it all further myself later.

wiak