Re: [OpenIndiana-discuss] mate system monitor does not work any, more on recent versions of openindiana

2023-05-02 Thread Stephan Althaus 

On 5/2/23 11:15, Udo Grabowski (IMK) wrote:

On 02/05/2023 11:06, Stephan Althaus wrote:

On 5/2/23 11:01, Udo Grabowski (IMK) wrote:

On 02/05/2023 10:55, Udo Grabowski (IMK) wrote:

On 01/05/2023 22:02, Stephan Althaus wrote:

On 4/19/23 15:59, Udo Grabowski (IMK) wrote:

On 19/04/2023 15:55, russell wrote:

Hi Marc

When I run /usr/bin/mate-system-monitor the executable aborts.
On a hunch I performed an ldd /usr/bin/mate-system-monitor and 
found that like
the non working screensavers see 
(https://www.illumos.org/issues/15138) which

abort or fail to display and are all linked to gcc7.

$  ldd /usr/bin/mate-system-monitor | grep gcc
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1

If the screensavers and mate-system-monitor is just linked to 
gcc 10 I believe

it should fix the issue



You can essentially force that via LD_LIBRARY_PATH, without
editing the runpath:

ro sunts /tmp # LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 
mate-system-monitor


(:12354): glibmm-CRITICAL **: 15:56:28.001:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault

It goes to gcc10 solely, so the glib error persists:

ro sunts /tmp # env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 ldd 
`which mate-system-monitor`|grep gcc

libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hello!

Info:

This error persists even after upgrade glib2 to 2.74.7 as build on 
the official build server on 30.04.2023 (pkg update some minutes 
ago)..
On a fast search i did not find any 'easy' configure option to add 
"inotify/fam support" as suggested by Udo Grabowski


Regards,

Stephan Althaus

_

$ pkg info glib2
  Name: library/glib2
   Summary: GNOME core libraries
  Category: Desktop (GNOME)/Libraries
 State: Installed
 Publisher: openindiana.org
   Version: 2.74.7
    Branch: 2023.0.0.0
    Packaging Date: April 30, 2023 at 08:34:29 PM
Last Install Time: September  7, 2019 at 07:43:17 PM
  Last Update Time: May  1, 2023 at 05:59:29 PM
  Size: 21.65 MB
  FMRI: 
pkg://openindiana.org/library/glib2@2.74.7-2023.0.0.0:20230430T203429Z 



$ env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 mate-system-monitor

(:4045): Gtk-WARNING **: 21:53:22.206: Theme parsing 
error: gtk-widgets.css:6:28: The style property 
GtkRange:slider-width is deprecated and shouldn't be used anymore. 
It will be removed in a future version

..
(:4045): glibmm-CRITICAL **: 21:53:22.275:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation Fault (core dumped)

$ pstack core
core 'core' of 4045:    mate-system-monitor
- thread# 1 / lwp# 1 -
  7fffac7c6ca7 g_type_check_instance_cast () + 17
  0044977a 
_ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE 
() + 11a
  7fff9e799ab0 
_ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine 
() + 160

  7fffac4ace5f _g_cclosure_marshal_INT__OBJECTv () + 6f
  7fffac79aa08 _g_closure_invoke_va () + 188
  7fffac7baf92 g_signal_emit_valist () + 332
  7fffac7bc17d g_signal_emit () + 7d
  7fffac509933 g_application_call_command_line () + a3
  7fffac50bd71 g_application_real_local_command_line () + 211
  7fff9e798722 
_ZN3Gio11Application24local_command_line_vfuncERPPcRi () + 52
  7fff9e79939b 
_ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi 
() + fb

  7fffac50bef3 g_application_run () + 133
  00422b4e main () + 5e
  00421e07 _start_crt () + 87
  00421d68 _start () + 18



Yes, it's also still ingesting both gcc-7 and 10 libraries.
The configure script for glib2 seems to check for the presence of
libfam and inotify by default, but fam support could be switched
off by an explicitly set option. The fam library is installed by
package library/file-monitor/gamin .



Has fam-support been removed from glib2 ?


...
# Remove gamin dependency
Obsoletes: glib2-fam < 2.67.1-3

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Found this:

Re: [OpenIndiana-discuss] mate system monitor does not work any, more on recent versions of openindiana

2023-05-02 Thread Udo Grabowski (IMK) 

On 02/05/2023 11:06, Stephan Althaus wrote:

On 5/2/23 11:01, Udo Grabowski (IMK) wrote:

On 02/05/2023 10:55, Udo Grabowski (IMK) wrote:

On 01/05/2023 22:02, Stephan Althaus wrote:

On 4/19/23 15:59, Udo Grabowski (IMK) wrote:

On 19/04/2023 15:55, russell wrote:

Hi Marc

When I run /usr/bin/mate-system-monitor the executable aborts.
On a hunch I performed an ldd /usr/bin/mate-system-monitor and 
found that like
the non working screensavers see 
(https://www.illumos.org/issues/15138) which

abort or fail to display and are all linked to gcc7.

$  ldd /usr/bin/mate-system-monitor | grep gcc
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1

If the screensavers and mate-system-monitor is just linked to gcc 
10 I believe

it should fix the issue



You can essentially force that via LD_LIBRARY_PATH, without
editing the runpath:

ro sunts /tmp # LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 
mate-system-monitor


(:12354): glibmm-CRITICAL **: 15:56:28.001:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault

It goes to gcc10 solely, so the glib error persists:

ro sunts /tmp # env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 ldd 
`which mate-system-monitor`|grep gcc

libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hello!

Info:

This error persists even after upgrade glib2 to 2.74.7 as build on 
the official build server on 30.04.2023 (pkg update some minutes ago)..
On a fast search i did not find any 'easy' configure option to add 
"inotify/fam support" as suggested by Udo Grabowski


Regards,

Stephan Althaus

_

$ pkg info glib2
  Name: library/glib2
   Summary: GNOME core libraries
  Category: Desktop (GNOME)/Libraries
 State: Installed
 Publisher: openindiana.org
   Version: 2.74.7
    Branch: 2023.0.0.0
    Packaging Date: April 30, 2023 at 08:34:29 PM
Last Install Time: September  7, 2019 at 07:43:17 PM
  Last Update Time: May  1, 2023 at 05:59:29 PM
  Size: 21.65 MB
  FMRI: 
pkg://openindiana.org/library/glib2@2.74.7-2023.0.0.0:20230430T203429Z


$ env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 mate-system-monitor

(:4045): Gtk-WARNING **: 21:53:22.206: Theme parsing error: 
gtk-widgets.css:6:28: The style property GtkRange:slider-width is 
deprecated and shouldn't be used anymore. It will be removed in a 
future version

..
(:4045): glibmm-CRITICAL **: 21:53:22.275:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation Fault (core dumped)

$ pstack core
core 'core' of 4045:    mate-system-monitor
- thread# 1 / lwp# 1 -
  7fffac7c6ca7 g_type_check_instance_cast () + 17
  0044977a 
_ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE () + 11a
  7fff9e799ab0 
_ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine () + 160

  7fffac4ace5f _g_cclosure_marshal_INT__OBJECTv () + 6f
  7fffac79aa08 _g_closure_invoke_va () + 188
  7fffac7baf92 g_signal_emit_valist () + 332
  7fffac7bc17d g_signal_emit () + 7d
  7fffac509933 g_application_call_command_line () + a3
  7fffac50bd71 g_application_real_local_command_line () + 211
  7fff9e798722 
_ZN3Gio11Application24local_command_line_vfuncERPPcRi () + 52
  7fff9e79939b 
_ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi () + fb

  7fffac50bef3 g_application_run () + 133
  00422b4e main () + 5e
  00421e07 _start_crt () + 87
  00421d68 _start () + 18



Yes, it's also still ingesting both gcc-7 and 10 libraries.
The configure script for glib2 seems to check for the presence of
libfam and inotify by default, but fam support could be switched
off by an explicitly set option. The fam library is installed by
package library/file-monitor/gamin .



Has fam-support been removed from glib2 ?


...
# Remove gamin dependency
Obsoletes: glib2-fam < 2.67.1-3

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Found this:

https://github.com/AOSC-Dev/aosc-os-abbs/pull/3768



Which

Re: [OpenIndiana-discuss] mate system monitor does not work any, more on recent versions of openindiana

2023-05-02 Thread Stephan Althaus 

On 5/2/23 11:01, Udo Grabowski (IMK) wrote:

On 02/05/2023 10:55, Udo Grabowski (IMK) wrote:

On 01/05/2023 22:02, Stephan Althaus wrote:

On 4/19/23 15:59, Udo Grabowski (IMK) wrote:

On 19/04/2023 15:55, russell wrote:

Hi Marc

When I run /usr/bin/mate-system-monitor the executable aborts.
On a hunch I performed an ldd /usr/bin/mate-system-monitor and 
found that like
the non working screensavers see 
(https://www.illumos.org/issues/15138) which

abort or fail to display and are all linked to gcc7.

$  ldd /usr/bin/mate-system-monitor | grep gcc
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1

If the screensavers and mate-system-monitor is just linked to gcc 
10 I believe

it should fix the issue



You can essentially force that via LD_LIBRARY_PATH, without
editing the runpath:

ro sunts /tmp # LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 
mate-system-monitor


(:12354): glibmm-CRITICAL **: 15:56:28.001:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault

It goes to gcc10 solely, so the glib error persists:

ro sunts /tmp # env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 ldd 
`which mate-system-monitor`|grep gcc

libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hello!

Info:

This error persists even after upgrade glib2 to 2.74.7 as build on 
the official build server on 30.04.2023 (pkg update some minutes ago)..
On a fast search i did not find any 'easy' configure option to add 
"inotify/fam support" as suggested by Udo Grabowski


Regards,

Stephan Althaus

_

$ pkg info glib2
  Name: library/glib2
   Summary: GNOME core libraries
  Category: Desktop (GNOME)/Libraries
 State: Installed
 Publisher: openindiana.org
   Version: 2.74.7
    Branch: 2023.0.0.0
    Packaging Date: April 30, 2023 at 08:34:29 PM
Last Install Time: September  7, 2019 at 07:43:17 PM
  Last Update Time: May  1, 2023 at 05:59:29 PM
  Size: 21.65 MB
  FMRI: 
pkg://openindiana.org/library/glib2@2.74.7-2023.0.0.0:20230430T203429Z


$ env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 mate-system-monitor

(:4045): Gtk-WARNING **: 21:53:22.206: Theme parsing error: 
gtk-widgets.css:6:28: The style property GtkRange:slider-width is 
deprecated and shouldn't be used anymore. It will be removed in a 
future version

..
(:4045): glibmm-CRITICAL **: 21:53:22.275:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation Fault (core dumped)

$ pstack core
core 'core' of 4045:    mate-system-monitor
- thread# 1 / lwp# 1 -
  7fffac7c6ca7 g_type_check_instance_cast () + 17
  0044977a 
_ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE 
() + 11a
  7fff9e799ab0 
_ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine 
() + 160

  7fffac4ace5f _g_cclosure_marshal_INT__OBJECTv () + 6f
  7fffac79aa08 _g_closure_invoke_va () + 188
  7fffac7baf92 g_signal_emit_valist () + 332
  7fffac7bc17d g_signal_emit () + 7d
  7fffac509933 g_application_call_command_line () + a3
  7fffac50bd71 g_application_real_local_command_line () + 211
  7fff9e798722 
_ZN3Gio11Application24local_command_line_vfuncERPPcRi () + 52
  7fff9e79939b 
_ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi 
() + fb

  7fffac50bef3 g_application_run () + 133
  00422b4e main () + 5e
  00421e07 _start_crt () + 87
  00421d68 _start () + 18



Yes, it's also still ingesting both gcc-7 and 10 libraries.
The configure script for glib2 seems to check for the presence of
libfam and inotify by default, but fam support could be switched
off by an explicitly set option. The fam library is installed by
package library/file-monitor/gamin .



Has fam-support been removed from glib2 ?


...
# Remove gamin dependency
Obsoletes: glib2-fam < 2.67.1-3

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Found this:

https://github.com/AOSC-Dev/aosc-os-abbs/pull/3768



___

Re: [OpenIndiana-discuss] mate system monitor does not work any, more on recent versions of openindiana

2023-05-02 Thread Udo Grabowski (IMK) 

On 02/05/2023 10:55, Udo Grabowski (IMK) wrote:

On 01/05/2023 22:02, Stephan Althaus wrote:

On 4/19/23 15:59, Udo Grabowski (IMK) wrote:

On 19/04/2023 15:55, russell wrote:

Hi Marc

When I run /usr/bin/mate-system-monitor the executable aborts.
On a hunch I performed an ldd /usr/bin/mate-system-monitor and found 
that like
the non working screensavers see 
(https://www.illumos.org/issues/15138) which

abort or fail to display and are all linked to gcc7.

$  ldd /usr/bin/mate-system-monitor | grep gcc
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1

If the screensavers and mate-system-monitor is just linked to gcc 10 
I believe

it should fix the issue



You can essentially force that via LD_LIBRARY_PATH, without
editing the runpath:

ro sunts /tmp # LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 
mate-system-monitor


(:12354): glibmm-CRITICAL **: 15:56:28.001:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault

It goes to gcc10 solely, so the glib error persists:

ro sunts /tmp # env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 ldd `which 
mate-system-monitor`|grep gcc

libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hello!

Info:

This error persists even after upgrade glib2 to 2.74.7 as build on the 
official build server on 30.04.2023 (pkg update some minutes ago)..
On a fast search i did not find any 'easy' configure option to add 
"inotify/fam support" as suggested by Udo Grabowski


Regards,

Stephan Althaus

_

$ pkg info glib2
  Name: library/glib2
   Summary: GNOME core libraries
  Category: Desktop (GNOME)/Libraries
 State: Installed
 Publisher: openindiana.org
   Version: 2.74.7
    Branch: 2023.0.0.0
    Packaging Date: April 30, 2023 at 08:34:29 PM
Last Install Time: September  7, 2019 at 07:43:17 PM
  Last Update Time: May  1, 2023 at 05:59:29 PM
  Size: 21.65 MB
  FMRI: 
pkg://openindiana.org/library/glib2@2.74.7-2023.0.0.0:20230430T203429Z


$ env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 mate-system-monitor

(:4045): Gtk-WARNING **: 21:53:22.206: Theme parsing error: 
gtk-widgets.css:6:28: The style property GtkRange:slider-width is 
deprecated and shouldn't be used anymore. It will be removed in a 
future version

..
(:4045): glibmm-CRITICAL **: 21:53:22.275:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation Fault (core dumped)

$ pstack core
core 'core' of 4045:    mate-system-monitor
- thread# 1 / lwp# 1 -
  7fffac7c6ca7 g_type_check_instance_cast () + 17
  0044977a 
_ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE () + 11a
  7fff9e799ab0 
_ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine () + 160

  7fffac4ace5f _g_cclosure_marshal_INT__OBJECTv () + 6f
  7fffac79aa08 _g_closure_invoke_va () + 188
  7fffac7baf92 g_signal_emit_valist () + 332
  7fffac7bc17d g_signal_emit () + 7d
  7fffac509933 g_application_call_command_line () + a3
  7fffac50bd71 g_application_real_local_command_line () + 211
  7fff9e798722 
_ZN3Gio11Application24local_command_line_vfuncERPPcRi () + 52
  7fff9e79939b 
_ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi () + fb

  7fffac50bef3 g_application_run () + 133
  00422b4e main () + 5e
  00421e07 _start_crt () + 87
  00421d68 _start () + 18



Yes, it's also still ingesting both gcc-7 and 10 libraries.
The configure script for glib2 seems to check for the presence of
libfam and inotify by default, but fam support could be switched
off by an explicitly set option. The fam library is installed by
package library/file-monitor/gamin .
 


Has fam-support been removed from glib2 ?


...
# Remove gamin dependency   
Obsoletes: glib2-fam < 2.67.1-3
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] mate system monitor does not work any, more on recent versions of openindiana

2023-05-02 Thread Udo Grabowski (IMK) 

On 01/05/2023 22:02, Stephan Althaus wrote:

On 4/19/23 15:59, Udo Grabowski (IMK) wrote:

On 19/04/2023 15:55, russell wrote:

Hi Marc

When I run /usr/bin/mate-system-monitor the executable aborts.
On a hunch I performed an ldd /usr/bin/mate-system-monitor and found 
that like
the non working screensavers see 
(https://www.illumos.org/issues/15138) which

abort or fail to display and are all linked to gcc7.

$  ldd /usr/bin/mate-system-monitor | grep gcc
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1

If the screensavers and mate-system-monitor is just linked to gcc 10 
I believe

it should fix the issue



You can essentially force that via LD_LIBRARY_PATH, without
editing the runpath:

ro sunts /tmp # LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 mate-system-monitor

(:12354): glibmm-CRITICAL **: 15:56:28.001:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault

It goes to gcc10 solely, so the glib error persists:

ro sunts /tmp # env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 ldd `which 
mate-system-monitor`|grep gcc

libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hello!

Info:

This error persists even after upgrade glib2 to 2.74.7 as build on the 
official build server on 30.04.2023 (pkg update some minutes ago)..
On a fast search i did not find any 'easy' configure option to add 
"inotify/fam support" as suggested by Udo Grabowski


Regards,

Stephan Althaus

_

$ pkg info glib2
  Name: library/glib2
   Summary: GNOME core libraries
  Category: Desktop (GNOME)/Libraries
     State: Installed
     Publisher: openindiana.org
   Version: 2.74.7
    Branch: 2023.0.0.0
    Packaging Date: April 30, 2023 at 08:34:29 PM
Last Install Time: September  7, 2019 at 07:43:17 PM
  Last Update Time: May  1, 2023 at 05:59:29 PM
  Size: 21.65 MB
  FMRI: 
pkg://openindiana.org/library/glib2@2.74.7-2023.0.0.0:20230430T203429Z


$ env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 mate-system-monitor

(:4045): Gtk-WARNING **: 21:53:22.206: Theme parsing error: 
gtk-widgets.css:6:28: The style property GtkRange:slider-width is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version

..
(:4045): glibmm-CRITICAL **: 21:53:22.275:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation Fault (core dumped)

$ pstack core
core 'core' of 4045:    mate-system-monitor
- thread# 1 / lwp# 1 -
  7fffac7c6ca7 g_type_check_instance_cast () + 17
  0044977a 
_ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE () + 11a
  7fff9e799ab0 
_ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine () + 160

  7fffac4ace5f _g_cclosure_marshal_INT__OBJECTv () + 6f
  7fffac79aa08 _g_closure_invoke_va () + 188
  7fffac7baf92 g_signal_emit_valist () + 332
  7fffac7bc17d g_signal_emit () + 7d
  7fffac509933 g_application_call_command_line () + a3
  7fffac50bd71 g_application_real_local_command_line () + 211
  7fff9e798722 _ZN3Gio11Application24local_command_line_vfuncERPPcRi 
() + 52
  7fff9e79939b 
_ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi () + fb

  7fffac50bef3 g_application_run () + 133
  00422b4e main () + 5e
  00421e07 _start_crt () + 87
  00421d68 _start () + 18



Yes, it's also still ingesting both gcc-7 and 10 libraries.
The configure script for glib2 seems to check for the presence of
libfam and inotify by default, but fam support could be switched
off by an explicitly set option. The fam library is installed by
package library/file-monitor/gamin .
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] mate system monitor does not work any, more on recent versions of openindiana

2023-05-01 Thread Stephan Althaus 

On 4/19/23 15:59, Udo Grabowski (IMK) wrote:

On 19/04/2023 15:55, russell wrote:

Hi Marc

When I run /usr/bin/mate-system-monitor the executable aborts.
On a hunch I performed an ldd /usr/bin/mate-system-monitor and found 
that like
the non working screensavers see 
(https://www.illumos.org/issues/15138) which

abort or fail to display and are all linked to gcc7.

$  ldd /usr/bin/mate-system-monitor | grep gcc
    libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
    libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
    libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1

If the screensavers and mate-system-monitor is just linked to gcc 10 
I believe

it should fix the issue



You can essentially force that via LD_LIBRARY_PATH, without
editing the runpath:

ro sunts /tmp # LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 mate-system-monitor

(:12354): glibmm-CRITICAL **: 15:56:28.001:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault

It goes to gcc10 solely, so the glib error persists:

ro sunts /tmp # env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 ldd `which 
mate-system-monitor`|grep gcc

libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hello!

Info:

This error persists even after upgrade glib2 to 2.74.7 as build on the 
official build server on 30.04.2023 (pkg update some minutes ago)..
On a fast search i did not find any 'easy' configure option to add 
"inotify/fam support" as suggested by Udo Grabowski


Regards,

Stephan Althaus

_

$ pkg info glib2
 Name: library/glib2
  Summary: GNOME core libraries
 Category: Desktop (GNOME)/Libraries
    State: Installed
    Publisher: openindiana.org
  Version: 2.74.7
   Branch: 2023.0.0.0
   Packaging Date: April 30, 2023 at 08:34:29 PM
Last Install Time: September  7, 2019 at 07:43:17 PM
 Last Update Time: May  1, 2023 at 05:59:29 PM
 Size: 21.65 MB
 FMRI: 
pkg://openindiana.org/library/glib2@2.74.7-2023.0.0.0:20230430T203429Z


$ env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 mate-system-monitor

(:4045): Gtk-WARNING **: 21:53:22.206: Theme parsing error: 
gtk-widgets.css:6:28: The style property GtkRange:slider-width is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version

..
(:4045): glibmm-CRITICAL **: 21:53:22.275:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation Fault (core dumped)

$ pstack core
core 'core' of 4045:    mate-system-monitor
- thread# 1 / lwp# 1 -
 7fffac7c6ca7 g_type_check_instance_cast () + 17
 0044977a 
_ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE 
() + 11a
 7fff9e799ab0 
_ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine 
() + 160

 7fffac4ace5f _g_cclosure_marshal_INT__OBJECTv () + 6f
 7fffac79aa08 _g_closure_invoke_va () + 188
 7fffac7baf92 g_signal_emit_valist () + 332
 7fffac7bc17d g_signal_emit () + 7d
 7fffac509933 g_application_call_command_line () + a3
 7fffac50bd71 g_application_real_local_command_line () + 211
 7fff9e798722 _ZN3Gio11Application24local_command_line_vfuncERPPcRi 
() + 52
 7fff9e79939b 
_ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi 
() + fb

 7fffac50bef3 g_application_run () + 133
 00422b4e main () + 5e
 00421e07 _start_crt () + 87
 00421d68 _start () + 18



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] mate system monitor does not work any, more on recent versions of openindiana

2023-04-19 Thread Udo Grabowski (IMK) 

On 19/04/2023 15:55, russell wrote:

Hi Marc

When I run /usr/bin/mate-system-monitor the executable aborts.
On a hunch I performed an ldd /usr/bin/mate-system-monitor and found that like
the non working screensavers see (https://www.illumos.org/issues/15138) which
abort or fail to display and are all linked to gcc7.

$  ldd /usr/bin/mate-system-monitor | grep gcc
libstdc++.so.6 => /usr/gcc/7/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/7/lib/amd64/libgcc_s.so.1
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1

If the screensavers and mate-system-monitor is just linked to gcc 10 I believe
it should fix the issue



You can essentially force that via LD_LIBRARY_PATH, without
editing the runpath:

ro sunts /tmp # LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 mate-system-monitor

(:12354): glibmm-CRITICAL **: 15:56:28.001:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault

It goes to gcc10 solely, so the glib error persists:

ro sunts /tmp # env LD_LIBRARY_PATH=/usr/gcc/10/lib/amd64 ldd `which 
mate-system-monitor`|grep gcc

libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 =>  /usr/gcc/10/lib/amd64/libgcc_s.so.1


--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] mate system monitor does not work any more on recent versions of openindiana

2023-04-19 Thread Udo Grabowski (IMK) 

On 19/04/2023 15:01, Marc Lobelle wrote:

Hello Udo,

I do not really understand what to do: uninstalling the old gcc 7 ? But I do not
see the relation between fam and the system monitor program.

What exactly should I do ?



You can't do anything. mate-system-monitor has to be recompiled
so that it don't load both gcc7 and gcc10 libraries. I emulated
that by changing the binary with elfedit, linking libraries
locally and preloading. But then you trap on the root cause,
which is the missing fam support in glib that causes most of
the gio stuff to fail. This is also seen in a report on the
GNU Hurd list: 



On 4/19/23 14:46, Udo Grabowski (IMK) wrote:

On 19/04/2023 13:00, Stephan Althaus wrote:

On 4/19/23 12:25, Marc Lobelle wrote:

Hello,

I updated openindiana from 2021-10 to 2022-10 on my notebook and the mate
system monitor does not start if I click on the widget: the widget is still
there and displays cpu usage, but if I click on it to get the window with full
information, I see a hourglass for a few seconds then nothing: it seems to
crash before opening the window.

Is there a workaround ?

Thanks

Marc


Hello!

This issue persists for several weeks now and is reproducible.

Alas, i can't see the root caause from the 'pstack' of the core dump, maybe
someone else is able to dig this out.

Regards,

Stephan

$ pstack core
core 'core' of 7849:mate-system-monitor
- thread# 1 / lwp# 1 -
 7fffaf40729a _lwp_kill () + a
 7fffaf39b1ee raise (6) + 1e
 7fffaf374c58 abort () + 58
 7fffab6e2b0e  ()
 7fffab8708c1 __gxx_personality_v0 () + d1
 7fffaccd5756 _Unwind_RaiseException_Phase2 () + a6
 7fffaccd6126 _Unwind_Resume () + 126
 7fff7712b9d5  ()
 0042f84b _ZN11PrettyTableC1Ev () + 1db
 004223e1 _ZN8ProcData12get_instanceEv () + 81
 0044832c _ZL16procman_data_newP10_GSettings () + 1c
 0044904d _ZN10ProcmanApp10on_startupEv () + 4d
 7fff770f9615 _ZN3Gio17Application_Class16startup_callbackEP13_GApplication
...


This boils down essentially to two problems at once: Both gcc7 and gcc10
libstdc++.so and libgcc_s.so are loaded, which breaks exception handling.
Massaging dyn:runpath and preloading then uncovers the second problem:

ro sunts /tmp # ./mate-system-monitor

(:11878): glibmm-CRITICAL **: 14:08:27.008:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault


That's what I already wrote in the thread


The /usr/lib/gio/modules/ directory has the giomodule.cache file.
When you try to recreate it with gio-querymodules /usr/lib/gio/modules/,
it's gone!

So probably the right fixes should be: Sort out the gcc7/10 confusion,
and compile glib with inotify/fam support.

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss



--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] mate system monitor does not work any more on recent versions of openindiana

2023-04-19 Thread Udo Grabowski (IMK) 

On 19/04/2023 13:00, Stephan Althaus wrote:

On 4/19/23 12:25, Marc Lobelle wrote:

Hello,

I updated openindiana from 2021-10 to 2022-10 on my notebook and the mate
system monitor does not start if I click on the widget: the widget is still
there and displays cpu usage, but if I click on it to get the window with full
information, I see a hourglass for a few seconds then nothing: it seems to
crash before opening the window.

Is there a workaround ?

Thanks

Marc


Hello!

This issue persists for several weeks now and is reproducible.

Alas, i can't see the root caause from the 'pstack' of the core dump, maybe
someone else is able to dig this out.

Regards,

Stephan

$ pstack core
core 'core' of 7849:mate-system-monitor
- thread# 1 / lwp# 1 -
 7fffaf40729a _lwp_kill () + a
 7fffaf39b1ee raise (6) + 1e
 7fffaf374c58 abort () + 58
 7fffab6e2b0e  ()
 7fffab8708c1 __gxx_personality_v0 () + d1
 7fffaccd5756 _Unwind_RaiseException_Phase2 () + a6
 7fffaccd6126 _Unwind_Resume () + 126
 7fff7712b9d5  ()
 0042f84b _ZN11PrettyTableC1Ev () + 1db
 004223e1 _ZN8ProcData12get_instanceEv () + 81
 0044832c _ZL16procman_data_newP10_GSettings () + 1c
 0044904d _ZN10ProcmanApp10on_startupEv () + 4d
 7fff770f9615 _ZN3Gio17Application_Class16startup_callbackEP13_GApplication
...


This boils down essentially to two problems at once: Both gcc7 and gcc10
libstdc++.so and libgcc_s.so are loaded, which breaks exception handling.
Massaging dyn:runpath and preloading then uncovers the second problem:

ro sunts /tmp # ./mate-system-monitor

(:11878): glibmm-CRITICAL **: 14:08:27.008:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code  : 0
what  : Unable to find default local file monitor type

Segmentation fault


That's what I already wrote in the thread


The /usr/lib/gio/modules/ directory has the giomodule.cache file.
When you try to recreate it with gio-querymodules /usr/lib/gio/modules/,
it's gone!

So probably the right fixes should be: Sort out the gcc7/10 confusion,
and compile glib with inotify/fam support.
--
Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
http://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology   http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] mate system monitor does not work any more on recent versions of openindiana

2023-04-19 Thread Stephan Althaus 

On 4/19/23 12:25, Marc Lobelle wrote:

Hello,

I updated openindiana from 2021-10 to 2022-10 on my notebook and the 
mate system monitor does not start if I click on the widget: the 
widget is still there and displays cpu usage, but if I click on it to 
get the window with full information, I see a hourglass for a few 
seconds then nothing: it seems to crash before opening the window.


Is there a workaround ?

Thanks

Marc


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Hello!

This issue persists for several weeks now and is reproducible.

Alas, i can't see the root caause from the 'pstack' of the core dump, 
maybe someone else is able to dig this out.


Regards,

Stephan

$ pstack core
core 'core' of 7849:    mate-system-monitor
- thread# 1 / lwp# 1 -
 7fffaf40729a _lwp_kill () + a
 7fffaf39b1ee raise (6) + 1e
 7fffaf374c58 abort () + 58
 7fffab6e2b0e  ()
 7fffab8708c1 __gxx_personality_v0 () + d1
 7fffaccd5756 _Unwind_RaiseException_Phase2 () + a6
 7fffaccd6126 _Unwind_Resume () + 126
 7fff7712b9d5  ()
 0042f84b _ZN11PrettyTableC1Ev () + 1db
 004223e1 _ZN8ProcData12get_instanceEv () + 81
 0044832c _ZL16procman_data_newP10_GSettings () + 1c
 0044904d _ZN10ProcmanApp10on_startupEv () + 4d
 7fff770f9615 
_ZN3Gio17Application_Class16startup_callbackEP13_GApplication () + c5

 7fffac79aa08 _g_closure_invoke_va () + 188
 7fffac7bb9b9 g_signal_emit_valist () + d59
 7fffac7bc17d g_signal_emit () + 7d
 7fffac50b7b2 g_application_register () + 122
 7fffac50bb6a g_application_real_local_command_line () + 6a
 7fff770f8722 _ZN3Gio11Application24local_command_line_vfuncERPPcRi 
() + 52
 7fff770f939b 
_ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi 
() + fb

 7fffac50be93 g_application_run () + 133
 00422b4e main () + 5e
 00421e07 _start_crt () + 87
 00421d68 _start () + 18
- thread# 2 / lwp# 2 [pool-spawner] --
 7fffaf4001d7 __lwp_park () + 17
 7fffaf3f969b cond_wait_queue (625cf0, 6217a0, 0) + 5b
 7fffaf3f9cda __cond_wait (625cf0, 6217a0) + 8a
 7fffaf3f9d44 cond_wait (625cf0, 6217a0) + 24
 7fffaf3f9d7b pthread_cond_wait (625cf0, 6217a0) + b
 7fffac6eb825 g_cond_wait () + 95
 7fffac6529b3 g_async_queue_pop_unlocked () + 63
 7fffac6bd4cf g_thread_pool_spawn_thread () + 6f
 7fffac6bce45 g_thread_proxy () + 45
 7fffaf3ffe7c _thrp_setup (7fffabeb02c0) + 6c
 7fffaf400190 _lwp_start ()
- thread# 3 / lwp# 3 [gmain] -
 7fffaf406d8a __pollsys () + a
 7fffaf397f01 poll (4d1970, 1, ) + 51
 7fffac689fcd g_main_context_iterate.constprop.0 () + 15d
 7fffac68a0e0 g_main_context_iteration () + 30
 7fffac68a131 glib_worker_main () + 21
 7fffac6bce45 g_thread_proxy () + 45
 7fffaf3ffe7c _thrp_setup (7fffabeb0ac0) + 6c
 7fffaf400190 _lwp_start ()
- thread# 4 / lwp# 4 [gdbus] -
 7fffaf406d8a __pollsys () + a
 7fffaf397f01 poll (6ef9e0, 3, ) + 51
 7fffac689fcd g_main_context_iterate.constprop.0 () + 15d
 7fffac68a323 g_main_loop_run () + 83
 7fffac54bdde gdbus_shared_thread_func () + 1e
 7fffac6bce45 g_thread_proxy () + 45
 7fffaf3ffe7c _thrp_setup (7fffabeb1ac0) + 6c
 7fffaf400190 _lwp_start ()
- thread# 5 / lwp# 5 [dconf worker] --
 7fffaf406d8a __pollsys () + a
 7fffaf397f01 poll (8512c0, 1, ) + 51
 7fffac689fcd g_main_context_iterate.constprop.0 () + 15d
 7fffac68a0e0 g_main_context_iteration () + 30
 7fffa1aebd55 dconf_gdbus_worker_thread () + 25
 7fffac6bce45 g_thread_proxy () + 45
 7fffaf3ffe7c _thrp_setup (7fffabeb22c0) + 6c
 7fffaf400190 _lwp_start ()



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss