On 2/7/23 22:29, Stephan Althaus wrote:
On 2/7/23 22:11, Bill Sommerfeld wrote:
On 2/7/23 13:01, Matthew Yapit wrote:
I recently updated to 2022.10 and I've noticed that mate-system-monitor causes a core instead of launching.  Has anyone else seen this?  Is there a fix or one coming in the next update?

It happens for me, too.   Based on the traceback in exception code, it likely needs to be rebuilt with gcc 10 given the lack of C++ ABI stability.   ldd shows a mix of libraries:

% ldd =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


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

Hello!

My version of mate-system-monitor shows only the gcc 7 libs,
but maybe you're right anyway..


$ ldd `which 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

$ mate-system-monitor

...

(<unknown>:4743): glibmm-CRITICAL **: 22:24:52.725:
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 4743:    mate-system-monitor
--------------------- thread# 1 / lwp# 1 ---------------------
 00007fffaeb69d0b g_type_check_instance_cast () + 1b
 000000000044977a _ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE () + 11a  00007fff6e3c09b9 _ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine () + 149
 00007fffae841496 _g_cclosure_marshal_INT__OBJECTv () + 76
 00007fffaeb3af95 _g_closure_invoke_va () + 185
 00007fffaeb5af6d g_signal_emit_valist () + 39d
 00007fffaeb5c05d g_signal_emit () + 7d
 00007fffae8a032a g_application_call_command_line () + 7a
 00007fffae8a26b1 g_application_real_local_command_line () + 241
 00007fff6e3bf4f4 _ZN3Gio11Application24local_command_line_vfuncERPPcRi () + 54  00007fff6e3c05cb _ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi () + 10b
 00007fffae8a2845 g_application_run () + 155
 0000000000422b4e main () + 5e
 0000000000421e07 _start_crt () + 87
 0000000000421d68 _start () + 18
...


Regards,

Stephan


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

Hi!

When i rebuild mate-system-monitor in my environment,
i will get the dependencies to gcc-10 in the build.

The pstack of the core then contains on entry "????????" which i assume is a result of the gcc-10 dependencies.

Nevertheless mate-system-monitor does crash in the version (as of my BE: openindiana-2022:11:23) without gcc-10 deps.

So the primary root cause may be something different.

Regards,

Stephan



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

Reply via email to