Re: [OpenIndiana-discuss] /etc/localtime
On 10/28/24 18:04, Udo Grabowski (IMK) wrote: If you are curious why mate (here caja) shows times in UTC instead of the timezone set in /etc/default/init (TZ): It specifically looks for the file /etc/localtime . That should be a link to the proper timezone binary in /usr/share/lib/zoneinfo/ , e.g., /usr/share/lib/zoneinfo/Europe/Berlin . ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Nice find! ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Heads up OpenSSH config change
On 10/15/24 10:29, Till Wegmüller wrote:
Hello everyone.
We have recently packaged OpenSSH 9.9 and have found that this also
requires us to distribute a configuration change. If you have not
edited your SSH Config this will not effect you. If you have edited
your sshd_config you will need to run the following sed script before
you run pkg update.
sed -i "s/ListenAddress ::/#ListenAddress ::/g" /etc/ssh/sshd_config
Alternatively make sure that all ListenAddress directives are either
Uncommented or commented out.
The reason for this config change is, that we had a differing
behaviour on our OS for how ListenAdress works compared to what you
find on the internet. We do not know what introduced this behaviour in
the past but it seems to have been fixed upstream. We thus make sure
OpenSSH behaves as people expect it to when changing the config.
Greetings
Till
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Hi!
There is more to check with the config, just in case someone stumbles...
[ Oct 16 11:29:35 Executing start method ("/lib/svc/method/sshd start"). ]
/etc/ssh/sshd_config line 85: Deprecated option ServerKeyBits
/etc/ssh/sshd_config line 90: Deprecated option KeyRegenerationInterval
/etc/ssh/sshd_config: line 103: Bad configuration option: MaxAuthTriesLog
/etc/ssh/sshd_config line 132: Deprecated option RhostsAuthentication
/etc/ssh/sshd_config line 138: Deprecated option RhostsRSAAuthentication
/etc/ssh/sshd_config line 145: Deprecated option RSAAuthentication
/etc/ssh/sshd_config: terminating, 1 bad configuration options
after commenting them out with a # in front, the ssh service is running.
Regards,
Stephan
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Missing driver pkg rtl for WIFI stick D-LINK DWA-171 2001:3314
On 9/3/24 18:17, Carsten Grzemba via openindiana-discuss wrote: A look at freebsd is the urtwn driver the right choise for this device. With the illumos urtwn driver I use Edimax 7811 V1 successfull which is a RTL8192CU chip. Your DWA-171 seems to be a RTL8812AU chip which is not implemented in the illumous urtwn driver. I can't find a rtl dirver anywhere, but generally begins the names of USB drivers with letter u (urtwn), without the u it is a driver for PCI cards (at least in the BSD world). Some additional dirvers are onhttp://freenicdrivers.la.coocan.jp/ but there also no driver for the RTL8812AU chips. -- Regards Carsten Hello Carsten! Thank you for clarification and for the hint to a working one! Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Missing driver pkg rtl for WIFI stick D-LINK DWA-171 2001:3314
Hello! I have an old DWA-171 USB WIFI stick, ID 2001:3314 D-Link Corp. DWA-171 but my system is somehow missing the driver "rtl" Sep 3 12:12:47 dell7720 usba: [ID 912658 kern.info] USB 2.10 device (usb2001,3314) operating at hi speed (USB 2.x) on USB 3.0 root hub: device@1, usb_mid57 at bus address 8 Sep 3 12:12:47 dell7720 usba: [ID 349649 kern.info] Realtek 802.11n WLAN Adapter 00e04c01 Sep 3 12:12:47 dell7720 genunix: [ID 936769 kern.info] usb_mid57 is /pci@0,0/pci1028,7b1@14/device@1 Sep 3 12:12:47 dell7720 genunix: [ID 408114 kern.info] /pci@0,0/pci1028,7b1@14/device@1 (usb_mid57) online Sep 3 12:12:47 dell7720 usba: [ID 349649 kern.info] usba: no driver found for interface 0 (nodename: 'interface') of Realtek 802.11n WLAN Adapter 00e04c01 The stick is part of the compatibility list https://docs.openindiana.org/community-hcl/components/#wifi-adapters D-Link DWA-171 yes 802.11abgn+ac USB 2.0 rtl Why/where is the driver ?? i have the driver package pkg://driver/network/rtls but rtl is not in the pkg repo. Any hints ?? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Cannot run texlive 2024
On 8/27/24 12:53, Udo Grabowski (IMK) wrote: On 8/27/24 12:45, Apostolos Syropoulos via openindiana-discuss wrote: Each year I compile TeXLive so I have binaries that have been compiled on a fairly recent version of OI/hipster.If you like, I can upload somewhere the binaries that I have compiled and I am using every day. Oh, that would be great, would save a lot of work ! On Tuesday, August 27, 2024 at 01:26:12 PM GMT+3, Udo Grabowski (IMK) wrote: On 8/27/24 12:06, Udo Grabowski (IMK) wrote: Hi, downloaded TeXLive 2024, but unfortunately this seems to be incompatible with illumos libc.so.1 : # ldd /usr/local/texlive/2024/bin/x86_64-solaris/pdftex libstdc++.so.6 => /usr/lib/64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 libgcc_s.so.1 => /usr/lib/64/libgcc_s.so.1 libc.so.1 => /lib/64/libc.so.1 libc.so.1 (SUNWpublic) => (version not found) # pvs -v /usr/local/texlive/2024/bin/x86_64-solaris/pdftex libstdc++.so.6 (GLIBCXX_3.4, CXXABI_1.3 [INFO], CXXABI_1.3.8); libm.so.2 (SUNW_1.2, SUNW_1.1 [INFO]); librt.so.1 (SUNW_1.2, SUNW_1.1 [INFO]); libgcc_s.so.1 (GCC_3.0); libc.so.1 (SUNWpublic, SUNW_1.23 [INFO], SUNW_1.1 [INFO], SUNW_0.8 [INFO], SUNW_0.7 [INFO], SYSVABI_1.3 [INFO], SUNWprivate_1.1); # mcs -p /usr/local/texlive/2024/bin/x86_64-solaris/pdftex /usr/local/texlive/2024/bin/x86_64-solaris/pdftex: GCC: (GNU) 5.5.0 ld: Software Generation Utilities - Solaris Link Editors: 5.11-1.3159 Any chance to get that SUNpublic version into libc.so.1 ? Any linker/elfedit trick possible to get that running ? Or do we have to completely compile it as our own package ? I remember there was a thread about the TeXLive package a while ago, just providing a download wrapper package, but this would not work given these binaries now. It seems that pkgsrc already has an extensive TeXLive 2024, so will go that path. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! What about this, is that working ?? http://docs.openindiana.org/handbook/community/texlive/ Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] gfxdrm/OpenGL error with latest update
On 7/31/24 01:57, scavenger via openindiana-discuss wrote: Originally posted by another people here: https://illumos.topicbox.com/groups/discuss/T6362d704c0be376b/gfxdrm-opengl-error-with-latest-update https://illumos.topicbox.com/groups/discuss/T024578a526b45d4d/aw-discuss-re-gfxdrm-opengl-error-with-latest-update I joined the discussion and posted further information. We are both affected by this bug. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Thats not good. Do you feel slow handling in desktop apps (aside from games etc) ? On my system the error doesn't show up, i am using nvidia: $ glxinfo -B ... OpenGL version string: 4.5.0 NVIDIA 535.183.01 ... (as my builtin intel chipset was/is not supported) Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ipmitool error (?)
On 7/30/24 13:01, Stephan Althaus wrote: ipmitool Failed to initialize the OEM info dictionary Hello! i solved it locally by replacing /usr/share/misc/enterprise-numbers with the file from https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] ipmitool error (?)
Hello! i just faced an error with ipmitool, maybe something is wrong with the package ? $ ipmitool Failed to initialize the OEM info dictionary $ pkg info ipmitool Name: system/management/ipmitool Summary: IPMI management tool Category: System/Hardware State: Installed Publisher: openindiana.org Version: 1.8.19 Branch: 2024.0.0.1 Packaging Date: July 13, 2024 at 07:00:06 AM Last Install Time: April 10, 2020 at 07:22:18 PM Last Update Time: July 19, 2024 at 12:33:47 PM Size: 2.04 MB FMRI: pkg://openindiana.org/system/management/ipmitool@1.8.19-2024.0.0.1:20240713T070006Z Project URL: https://github.com/ipmitool/ipmitool Source URL: https://github.com/ipmitool/ipmitool/archive/refs/tags/IPMITOOL_1_8_19.tar.gz Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Hardware Identification Application?
On 7/19/24 18:43, Lonnie Cumberland via openindiana-discuss wrote: Hi All, After being in the Windows, Linux, and BSD world for many years, I have recently started exploring illumos-based distros like OpenIndiana, SmartOS, OmniOS, and Tribblix as well as testing them out since I am switching over now due to the many features and stability that I have noticed in illumos. Of course, it can always use more hardware development but I think that will come in time as well. With that in mind, I am seeking some type of text based application, or library (C/C++) that will identify bare-metal hardware on a computer system (i.e. CPU, GPU, Monitors, HDD, USB devices, etc.) such that it might be used to determine the needed drivers that should be installed like Nvidia, etc. Probably, OpenIndiana-Hipster may already have something like this, and I would like to try and locate the source code and application if possible, but if not, then maybe someone knows of a good library that might be used as a starting point for this type of Hardware Identification Program (HIP). Any thoughts or suggestions would be greatly appreciated and have a great day, Lonnie ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi! On Openinidiana there are the command line tool prtconf and the GUI application ddu. Are you looking for these ? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] elegant way to move from PHP-81 to PHP-82
Hello!
Is there a more elegant way to move from php-81 to php-82 than this:
pkg list | grep php | grep 81 | awk '{print $1}' | sed "s/81/82/g" |
xargs pfexec pkg install
.. maybe something by changing a mediator ??
Regards,
Stephan
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,
On 2/12/24 17:46, Stephan Althaus wrote: On 2/12/24 17:40, Udo Grabowski (IMK) wrote: On 12/02/2024 17:32, Stephan Althaus wrote: ... That is the nvidia audio device, i can select it in vlc and hear nothing, my monitor speakers should do it - i have no clue at the moment.. i tried USB-C and HDMI connection the the monitor just right now with no luck.. # cat /dev/random > /dev/dsp1 gives no sound output.. mate-volume-control may helps. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In the mate-volume-control, i have nothing in the hardware tab, audiohd#5 and Wmonitor of audiohd#5" in the input tab, audiohd#5 in the output tab, so nothing with audiohd#6 to configure there... By the way, running latest nvidia 535.154.5. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! i crossed-checked with OI USB stick on a different older laptop with Nvidia NVS 3100M, + nvidia 340 gets used, + the devices below /dev/ look pretty much the same and seem to be correct, - "pactl list sinks" does not list the nvidia output, + DDU says it is supported by the audiohd module (and so do i guess from the links below /dev/), - the "hardware" tab in the mate-volume-control is empty (it is not if i boot debian linux with nvidia 340 on this old laptop) - the nvidia related audiohd#1 devices are not listed within mate-volume-control if i find the time i will check a desktop system with a GT1030.. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,
On 2/12/24 17:40, Udo Grabowski (IMK) wrote: On 12/02/2024 17:32, Stephan Althaus wrote: ... That is the nvidia audio device, i can select it in vlc and hear nothing, my monitor speakers should do it - i have no clue at the moment.. i tried USB-C and HDMI connection the the monitor just right now with no luck.. # cat /dev/random > /dev/dsp1 gives no sound output.. mate-volume-control may helps. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In the mate-volume-control, i have nothing in the hardware tab, audiohd#5 and Wmonitor of audiohd#5" in the input tab, audiohd#5 in the output tab, so nothing with audiohd#6 to configure there... By the way, running latest nvidia 535.154.5. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,
On 2/12/24 17:13, Carsten Grzemba via openindiana-discuss wrote: Am 12.02.24 16:43 schrieb Stephan Althaus : On 2/12/24 16:37, Carsten Grzemba via openindiana-discuss wrote: Hi ,Stephan, Am 12.02.24 16:16 schrieb Stephan Althaus : On 2/12/24 14:23, Carsten Grzemba via openindiana-discuss wrote: $ ls -l/dev/*audio* ; ls -l/dev/sound* ; ls -l /dev/*dsp** Hi Carsten! i did an pkg update this morning, so i do this again to give a consistent view of the things... $ ls -l /dev/*audio* ; ls -l /dev/sound* ; ls -l /dev/*dsp** lrwxrwxrwx 1 root root 7 Jan 3 2022 /dev/audio -> sound/0 lrwxrwxrwx 1 root �� root 10 Jan 3 2022 /dev/audioctl -> sound/0ctl total 12 lrwxrwxrwx 1 root root 9 Apr 11 2019 0 -> audiohd:5 lrwxrwxrwx 1 root root 12 Apr 11 2019 0ctl -> audiohd:5ctl lrwxrwxrwx 1 root root 9 Feb 26 2023 1 -> audiohd:6 lrwxrwxrwx 1 root root 12 Feb 26 2023 1ctl -> audiohd:6ctl lrwxrwxrwx 1 root root 51 Apr 11 2019 audiohd:5 -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,audio5 lrwxrwxrwx 1 root root 54 Apr 11 2019 audiohd:5ctl -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,audioctl5 lrwxrwxrwx 1 root root 49 Apr 11 2019 audiohd:5dsp -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,dsp5 lrwxrwxrwx 1 root root 51 Apr 11 2019 audiohd:5mixer -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,mixer5 lrwxrwxrwx 1 root root 66 Feb 26 2023 audiohd:6 -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,audio6 lrwxrwxrwx 1 root root 69 Feb 26 2023 audiohd:6ctl -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,audioctl6 lrwxrwxrwx 1 root root 64 Feb 26 2023 audiohd:6dsp -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,dsp6 lrwxrwxrwx 1 root root 66 Feb 26 2023 audiohd:6mixer -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,mixer6 lrwxrwxrwx 1 root root 4 Jan 3 2022 /dev/dsp -> dsp0 lrwxrwxrwx 1 root root 18 Apr 11 2019 /dev/dsp0 -> sound/audiohd:5dsp lrwxrwxrwx 1 root root 18 Feb 26 2023 /dev/dsp1 -> sound/audiohd:6dsp steven@dell7720:~$ pactl info Server String: /tmp/pulse-K2hFZViPE4v5/native Library Protocol Version: 33 Server Protocol Version: 33 Is Local: yes Client Index: 15 Tile Size: 65472 User Name: steven Host Name: dell7720 Server Name: pulseaudio Server Version: 13.0-rebootstrapped Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: oss_output.dsp0 Default Source: oss_input.dsp0 Cookie: 9b20:9261 Hm, the dsp0 was not the interesting part here, So please also $ pactl list sources $ pactl list sinks ;) Carsten ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Yes :-) $ pactl list sources Source #0 State: SUSPENDED Name: oss_input.dsp0 Description: audiohd#5 onboard1, a Driver: module-oss.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 6 Mute: no Volume: front-left: 65536 / 100%, front-right: 65536 / 100% balance 0.00 Base Volume: 65536 / 100% Monitor of Sink: n/a Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_VOLUME_CTRL LATENCY Properties: device.string = "/dev/dsp0" device.api = "oss" device.description = "audiohd#5 onboard1, a" device.access_mode = "serial" device.buffering.buffer_size = "15876" device.buffering.fragment_size = "1764" device.icon_name = "audio-input-microphone" Formats: pcm Source #1 State: IDLE Name: oss_output.dsp0.monitor Description: Monitor of audiohd#5 onboard1, a Driver: module-oss.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 6 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: oss_output.dsp0 Latency: 0 usec, configured 9 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of audiohd#5 onboard1, a" device.class = "monitor" device.icon_name = "audio-input-microphone" Formats: pcm $ pactl list sinks Sink #0 State: RUNNING Name: oss_output.dsp0 Description: audiohd#5 onboard1, a Driver: module-oss.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 6 Mute: no Volume: front-left: 60948 / 93%, front-right: 60948 / 93% balance 0.00 Base Volume: 65536 / 100% Monitor Source: oss_output.dsp0.monitor Latency: 105238 usec, configured 9 usec Flags: HARDWARE HW_VOLUME_CTRL LATENCY Properties: device.string = "/dev/dsp0" device.api = "oss" device.description = "audiohd#5 onboard1, a" device.access_mode = "serial" device.buffering.buffer_size = "15876"
Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,
On 2/12/24 16:37, Carsten Grzemba via openindiana-discuss wrote: Hi ,Stephan, Am 12.02.24 16:16 schrieb Stephan Althaus : On 2/12/24 14:23, Carsten Grzemba via openindiana-discuss wrote: $ ls -l/dev/*audio* ; ls -l/dev/sound* ; ls -l /dev/*dsp** Hi Carsten! i did an pkg update this morning, so i do this again to give a consistent view of the things... $ ls -l /dev/*audio* ; ls -l /dev/sound* ; ls -l /dev/*dsp** lrwxrwxrwx 1 root root 7 Jan 3 2022 /dev/audio -> sound/0 lrwxrwxrwx 1 root �� root 10 Jan 3 2022 /dev/audioctl -> sound/0ctl total 12 lrwxrwxrwx 1 root root 9 Apr 11 2019 0 -> audiohd:5 lrwxrwxrwx 1 root root 12 Apr 11 2019 0ctl -> audiohd:5ctl lrwxrwxrwx 1 root root 9 Feb 26 2023 1 -> audiohd:6 lrwxrwxrwx 1 root root 12 Feb 26 2023 1ctl -> audiohd:6ctl lrwxrwxrwx 1 root root 51 Apr 11 2019 audiohd:5 -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,audio5 lrwxrwxrwx 1 root root 54 Apr 11 2019 audiohd:5ctl -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,audioctl5 lrwxrwxrwx 1 root root 49 Apr 11 2019 audiohd:5dsp -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,dsp5 lrwxrwxrwx 1 root root 51 Apr 11 2019 audiohd:5mixer -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,mixer5 lrwxrwxrwx 1 root root 66 Feb 26 2023 audiohd:6 -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,audio6 lrwxrwxrwx 1 root root 69 Feb 26 2023 audiohd:6ctl -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,audioctl6 lrwxrwxrwx 1 root root 64 Feb 26 2023 audiohd:6dsp -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,dsp6 lrwxrwxrwx 1 root root 66 Feb 26 2023 audiohd:6mixer -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,mixer6 lrwxrwxrwx 1 root root 4 Jan 3 2022 /dev/dsp -> dsp0 lrwxrwxrwx 1 root root 18 Apr 11 2019 /dev/dsp0 -> sound/audiohd:5dsp lrwxrwxrwx 1 root root 18 Feb 26 2023 /dev/dsp1 -> sound/audiohd:6dsp steven@dell7720:~$ pactl info Server String: /tmp/pulse-K2hFZViPE4v5/native Library Protocol Version: 33 Server Protocol Version: 33 Is Local: yes Client Index: 15 Tile Size: 65472 User Name: steven Host Name: dell7720 Server Name: pulseaudio Server Version: 13.0-rebootstrapped Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: oss_output.dsp0 Default Source: oss_input.dsp0 Cookie: 9b20:9261 Hm, the dsp0 was not the interesting part here, So please also $ pactl list sources $ pactl list sinks ;) Carsten ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Yes :-) $ pactl list sources Source #0 State: SUSPENDED Name: oss_input.dsp0 Description: audiohd#5 onboard1, a Driver: module-oss.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 6 Mute: no Volume: front-left: 65536 / 100%, front-right: 65536 / 100% balance 0.00 Base Volume: 65536 / 100% Monitor of Sink: n/a Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_VOLUME_CTRL LATENCY Properties: device.string = "/dev/dsp0" device.api = "oss" device.description = "audiohd#5 onboard1, a" device.access_mode = "serial" device.buffering.buffer_size = "15876" device.buffering.fragment_size = "1764" device.icon_name = "audio-input-microphone" Formats: pcm Source #1 State: IDLE Name: oss_output.dsp0.monitor Description: Monitor of audiohd#5 onboard1, a Driver: module-oss.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 6 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: oss_output.dsp0 Latency: 0 usec, configured 9 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of audiohd#5 onboard1, a" device.class = "monitor" device.icon_name = "audio-input-microphone" Formats: pcm $ pactl list sinks Sink #0 State: RUNNING Name: oss_output.dsp0 Description: audiohd#5 onboard1, a Driver: module-oss.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 6 Mute: no Volume: front-left: 60948 / 93%, front-right: 60948 / 93% balance 0.00 Base Volume: 65536 / 100% Monitor Source: oss_output.dsp0.monitor Latency: 105238 usec, configured 9 usec Flags: HARDWARE HW_VOLUME_CTRL LATENCY Properties: device.string = "/dev/dsp0" device.api = "oss" device.description = "audiohd#5 onboard1
Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,
On 2/12/24 14:23, Carsten Grzemba via openindiana-discuss wrote: $ ls -l/dev/*audio* ; ls -l/dev/sound* ; ls -l /dev/*dsp** Hi Carsten! i did an pkg update this morning, so i do this again to give a consistent view of the things... $ ls -l /dev/*audio* ; ls -l /dev/sound* ; ls -l /dev/*dsp** lrwxrwxrwx 1 root root 7 Jan 3 2022 /dev/audio -> sound/0 lrwxrwxrwx 1 root root 10 Jan 3 2022 /dev/audioctl -> sound/0ctl total 12 lrwxrwxrwx 1 root root 9 Apr 11 2019 0 -> audiohd:5 lrwxrwxrwx 1 root root 12 Apr 11 2019 0ctl -> audiohd:5ctl lrwxrwxrwx 1 root root 9 Feb 26 2023 1 -> audiohd:6 lrwxrwxrwx 1 root root 12 Feb 26 2023 1ctl -> audiohd:6ctl lrwxrwxrwx 1 root root 51 Apr 11 2019 audiohd:5 -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,audio5 lrwxrwxrwx 1 root root 54 Apr 11 2019 audiohd:5ctl -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,audioctl5 lrwxrwxrwx 1 root root 49 Apr 11 2019 audiohd:5dsp -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,dsp5 lrwxrwxrwx 1 root root 51 Apr 11 2019 audiohd:5mixer -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,mixer5 lrwxrwxrwx 1 root root 66 Feb 26 2023 audiohd:6 -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,audio6 lrwxrwxrwx 1 root root 69 Feb 26 2023 audiohd:6ctl -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,audioctl6 lrwxrwxrwx 1 root root 64 Feb 26 2023 audiohd:6dsp -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,dsp6 lrwxrwxrwx 1 root root 66 Feb 26 2023 audiohd:6mixer -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,mixer6 lrwxrwxrwx 1 root root 4 Jan 3 2022 /dev/dsp -> dsp0 lrwxrwxrwx 1 root root 18 Apr 11 2019 /dev/dsp0 -> sound/audiohd:5dsp lrwxrwxrwx 1 root root 18 Feb 26 2023 /dev/dsp1 -> sound/audiohd:6dsp steven@dell7720:~$ pactl info Server String: /tmp/pulse-K2hFZViPE4v5/native Library Protocol Version: 33 Server Protocol Version: 33 Is Local: yes Client Index: 15 Tile Size: 65472 User Name: steven Host Name: dell7720 Server Name: pulseaudio Server Version: 13.0-rebootstrapped Default Sample Specification: s16le 2ch 44100Hz Default Channel Map: front-left,front-right Default Sink: oss_output.dsp0 Default Source: oss_input.dsp0 Cookie: 9b20:9261 Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,
On 2/10/24 09:16, Carsten Grzemba via openindiana-discuss wrote: For do some preliminary testing on update Pulseaudio I am interested in a small contribution. If anyone has more then one audio device, I am interested in the output of: $ ls -l /dev/audio* $ ls -l /dev/sound* $ ls -l /dev/dsp* Many thanks! Hello! My laptop has 1 onboard sound device and one from the nvidia card: *$ prtconf -v|grep -i aud|grep -i contr* * value='GM107 High Definition Audio Controller [GeForce 940MX]' value='CM238 HD Audio Controller' * Installed Pulseaudio Version: *$ pkg info pulseaudio* Name: library/audio/pulseaudio Summary: Sample Rate Converter for audio Category: System/Multimedia Libraries State: Installed Publisher: openindiana.org Version: 13.0 Branch: 2024.0.0.5 Packaging Date: January 13, 2024 at 07:35:31 PM Last Install Time: November 24, 2019 at 08:02:29 PM Last Update Time: January 19, 2024 at 06:04:28 AM Size: 8.40 MB * FMRI: pkg://openindiana.org/library/audio/pulseaudio@13.0-2024.0.0.5:20240113T193531Z * *$ ls -l /dev/*audio* ; ls -l /dev/sound* ; ls -l /dev/*dsp** lrwxrwxrwx 1 root root 7 Jan 3 2022 /dev/audio -> sound/0 lrwxrwxrwx 1 root root 10 Jan 3 2022 /dev/audioctl -> sound/0ctl total 12 lrwxrwxrwx 1 root root 9 Apr 11 2019 0 -> audiohd:5 lrwxrwxrwx 1 root root 12 Apr 11 2019 0ctl -> audiohd:5ctl lrwxrwxrwx 1 root root 9 Feb 26 2023 1 -> audiohd:6 lrwxrwxrwx 1 root root 12 Feb 26 2023 1ctl -> audiohd:6ctl lrwxrwxrwx 1 root root 51 Apr 11 2019 audiohd:5 -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,audio5 lrwxrwxrwx 1 root root 54 Apr 11 2019 audiohd:5ctl -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,audioctl5 lrwxrwxrwx 1 root root 49 Apr 11 2019 audiohd:5dsp -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,dsp5 lrwxrwxrwx 1 root root 51 Apr 11 2019 audiohd:5mixer -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,mixer5 lrwxrwxrwx 1 root root 66 Feb 26 2023 audiohd:6 -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,audio6 lrwxrwxrwx 1 root root 69 Feb 26 2023 audiohd:6ctl -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,audioctl6 lrwxrwxrwx 1 root root 64 Feb 26 2023 audiohd:6dsp -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,dsp6 lrwxrwxrwx 1 root root 66 Feb 26 2023 audiohd:6mixer -> ../../devices/pci@0,0/pci8086,1901@1/pci1028,17b1@0,1:sound,mixer6 lrwxrwxrwx 1 root root 4 Jan 3 2022 /dev/dsp -> dsp0 lrwxrwxrwx 1 root root 18 Apr 11 2019 /dev/dsp0 -> sound/audiohd:5dsp lrwxrwxrwx 1 root root 18 Feb 26 2023 /dev/dsp1 -> sound/audiohd:6dsp Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] firefox crashes
On 2/5/24 13:27, Predrag Zecevic wrote: pfexec zfs -o set volsize=48G rpool/swap Hello! I've increased that value from 32GB to 48 as described, no change here. My "test" is bidding on ebay, by clicking on a 'button' with a predefined bidding value, so maybe something related to javascript (?) Don't know. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] firefox crashes
Hello! since a few days, firefox dumps core from time to time. i think i can reproduce it easily. Anyone else seeing this, or is this a local problem ? I updated last time on 02.02.2024: The illumos Project illumos-b91bbe3818 February 2024 core 'core' of 4945: /usr/bin/firefox -- thread# 1 / lwp# 1 [MainThread] --- 7fff852cace2 _ZN2JS18HideScriptedCallerEP9JSContext () 7fff821ef472 _ZN7mozilla3dom27CustomElementReactionsStack15InvokeReactionsEP10AutoTArrayI6RefPtrINS0_7ElementEELm3EEP15nsIGlobalObject () + 5c 7fff821ef8c7 _ZN7mozilla3dom27CustomElementReactionsStack24PopAndInvokeElementQueueEv () + af 7fff81ca7abd _ZN7mozilla3dom14AutoCEReactionD1Ev () + 59 7fff82ab2146 _ZN7mozilla3dom15Element_BindingL12setAttributeEP9JSContextN2JS6HandleIP8JSObjectEEPvRK19JSJitMethodCallArgs () + 1ef 7fff82c06a7a _ZN7mozilla3dom14binding_detail13GenericMethodINS1_16NormalThisPolicyENS1_15ThrowExceptionsEEEbP9JSContextjPN2JS5ValueE () + 1ea 2d26f1ea4d1e () 2d26f1e59876 () 2d26f1e8b84e () 2d26f1e59876 () 2d26f1e504e6 () 7fff856b7f51 _ZL8EnterJitP9JSContextRN2js8RunStateEPh () + 13e 7fff856b83a8 _ZN2js3jit13MaybeEnterJitEP9JSContextRNS_8RunStateE () + 6a 7fff858b7550 _ZN2js9RunScriptEP9JSContextRNS_8RunStateE () + b5 7fff858b7926 _ZN2js23InternalCallOrConstructEP9JSContextRKN2JS8CallArgsENS_14MaybeConstructENS_10CallReasonE () + 1a4 7fff858b81f4 _ZN2js4CallEP9JSContextN2JS6HandleINS2_5ValueEEES5_RKNS_13AnyInvokeArgsENS2_13MutableHandleIS4_EENS_10CallReasonE () + bf 7fff8513abf7 _ZN2js9fun_applyEP9JSContextjPN2JS5ValueE () + 337 2d26f1e561c6 () 2d26f1fdf109 () 2d26f1ec7d97 () 2d26f2022db7 () 2d26f1e504e6 () 7fff856b7f51 _ZL8EnterJitP9JSContextRN2js8RunStateEPh () + 13e 7fff856b83a8 _ZN2js3jit13MaybeEnterJitEP9JSContextRNS_8RunStateE () + 6a Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] a2ensite, a2dissite, & apache2ctl all command not found
On 1/23/24 07:53, Christopher D. Bartels wrote: Hi, I'm working with a fresh install of apache 24 & am trying to disable the default site and enable the virtual host I've configured, but can't until I find how to use the a2ensite & a2dissite commands. In my case here they're both erroring with command not found with or without sudo. Can someone advise how to get these & other related apache2 commands working please? With thanks, Chris Bartels ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi! These scripts are not delivered with our apache-24 package. see: $pkg contents apache-24|grep a2 Maybe you could search the sources and create your own script files... https://gist.github.com/kevinmesiab/5404a839ce15b5f6e5e7 https://github.com/dracorp/a2enmod ... Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Lenovo p1 Gen 6 intel i7
On 1/20/24 13:20, Matthew R. Trower wrote: I don’t suppose you have the capability to boot via cdrom? I’ve had similar sorts of trouble booting from USB images on some machines. -- Matthew R. Trower On Jan 20, 2024, at 03:32, open wrote: Dear All, Lenovo P1 Gen 6 intel core i7. I am currently running Kubuntu on this laptop and have tried running a live oi image. This seems to load upto 'console login fails to star't with no other error messages. I have used both ISA and USB latest image on a USB3 formatted and loaded on linux. I have also tested this on a lenovo p1 gen 1 i5 that also halts at console login. Both Bios have secure boot not enabled and wondered if anyone has any ideas of progressing the boot process ? Thank you in anticipation. Rob Jones ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! USB-3 is still not to be considered rock-solid, there are some circumstances in which there are problems. If you have USB-2-only hardware on the host there are no problems. Maybe you have a usb-2 port on the docking station or an older USB-hub that may work(?) But wait, i have booted my laptop the day before yesterday with the 2023-10 usb image to repair my rpool, that worked flawlessly.., its a DELL precision 7720 USB-3 port Maybe you can switch between legacy and UEFI boot ?? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] pkg update hangs downloading ghostscript
On 12/14/23 19:57, Oscar del Rio wrote: Hi all, There might be an issue with /print/filter/ghostscript package that is hanging "pkg update". The update starts well for other packages but then it hangs in ghostscript consistently. I uninstalled ghostscript (not needed on this machine), then "pkg update" completed successfully. Error message: DOWNLOAD PKGS FILES XFER (MB) SPEED print/filter/ghostscript 342/472 6084/13973 209.7/603.6 -- Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: pkg://openindiana.org/print/filter/ghostscript@10.2.1,5.11-2023.0.0.0:20231126T181228Z 1: Framework error: code: E_RECV_ERROR (56) reason: Recv failure: Connection reset by peer URL: 'http://pkg.openindiana.org/hipster/openindiana.org/file/1/b1f105c0b8d1e3c2b1820f0efa8fb2a321acc971' (happened 3 times) 2: Framework error: code: E_OPERATION_TIMEOUTED (28) reason: Operation too slow. Less than 1024 bytes/sec transferred the last 30 seconds URL: 'http://pkg.openindiana.org/hipster/openindiana.org/file/1/b1f105c0b8d1e3c2b1820f0efa8fb2a321acc971' Cheers, Oscar ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! I believe that pkg.openindiana.org is slow. At my side pkg update works only well in the early morning (germany). Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Mate clock applet gone
Hello! First of all, thanks for all the recent wecome updates on the OpenIndiana distribution, it's really a great OS !! I was most impressed by the speedup of libreoffice while scrolling through calc tables.. was that a switch from GTK* to QT ? Now to the topic, nothing really severe.. Since some time (few weeks), i had the mate clock applet seen crashing and could reload it by pressing a button on the appearing dialog box. Now it seems, the clock applet does not load anymore.. (and the mate panel takes a second more to load than previously, it appears after the background and desktop contents.. Anyone else seeing this ? Where can i find the error messages regarding mate applets on OI ? Can an applet be load by command line to get the messages on the command line ? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] gthumb symbol error
Hello! I am experiencing this on a system updated on nov-23. $ gthumb DSC02245.ARW ld.so.1: gthumb: fatal: relocation error: file /usr/lib/amd64/gthumb/extensions/libexiv2_tools.so: symbol _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceEmmPKcm: referenced symbol not found Maybe a rebuild is necessary ? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] container with same ip
On 11/16/23 02:47, Goetz T. Fischer wrote: much thanks to all of you for everything so far but that's much more than i need. all i want is 1 zone that runs stuff which is available through the "real" nic's ip. and right now i'm facing much more trivial problems like: what's the root password of a newly installed zone? the one i use for the host os doesn't work. On Wed, 15 Nov 2023 20:25:21 -0500, John D Groenveld wrote: In message , Peter Tribble writes: 1. Create an etherstub Software switches are close to free. Recommend creating a stub per pair between zones or an etherstub for each application stack. 2. In the global zone, create a vnic over that etherstub, and then give it an address eg 10.0.0.1 You can also assign your physical interface to a zone and restrict access to the global zone via an out-of-band console. 4. Run haproxy or nginx (or something similar, whatever you're familiar with) in the global zone as a reverse proxy so it's listening on the system's main IP address, and proxies the traffic to the zone(s). This can be name-based websites (either from the host header for http or SNI for https), or port-based for things that can't handle routing based on names (eg ssh). +1. You can also use a bhyve branded zone for your public facing network and run your favorite router/firewall/proxy OS, perhaps OpenBSD or an appliance OS like OpenSense. So many cool possible configurations! John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Become root on the "host" / "global zone", then zlogin and youre in. "root" is a "role" in solaris, and has no default password in the zone. You may be able to set one, but you don't need to or may not want to do so (?)... Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] container with same ip
On 11/14/23 18:45, Goetz T. Fischer wrote: ah, i think now i get the idea. a vnic for the zone and then treat the zone like some server on the lan behind the firewall/router ? On Tue, 14 Nov 2023 12:38:01 -0500, John D Groenveld wrote: In message <20231114182416441063.bcadd...@r-a-c.de>, "Goetz T. Fischer" writes: thanks but i don't think this is the right one for me. i want to run services inside the container which are available from the outside through the same ip as the host os. or maybe i got the crossbow concept wrong? ipnat(8) with rdr https://illumos.org/man/8/ipnat> The IPFilter HowTo is useful: https://web.archive.org/web/20110718150143/http://www.obfuscation.org/ipf/ipf-howto.html> John groenv...@acm.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi! Something more simple to get a start: https://semmemoria.wordpress.com/2013/03/27/solaris-11-zone-with-vnic-and-dualstack-ipv4-and-ipv6/ Then use zlogin to get the zones' console and check the network inside the zone... Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] NUC boot
On 11/5/23 12:41, James wrote: On 31/10/2023 09:38, Toomas Soome wrote: Good morning, Could you try this image: http://84.50.115.54/OI-hipster-gui-20231027.usb It gets past the previous hurdle. Thank you for whatever tweak this involved. Now the "however". It fails to open a graphical login screen. Does this mean it is without graphics at all? Would a text install and then "pkg install mate_install" make any difference? This is not my machine and if this never works it is not a tragedy but solving this now could help others in future. My apologies for using screen pictures. "tip hardwire" is my preference. James. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In my experience, in most of the cases that lightdm is not working its because the X is not starting. Maybe the VESA doesn't work. Is there an /var/log/Xorg.0.log ? You could try a text-install and look at the X problem then again on the installed basic system.. OI lacks drivers for the latest Intel chipsets, but VESA should work. NVIDIA is best, if there is a PCI socket you could insert an old NVIDIA card (NVS 310 or NVS 295 are small passive ones for a few bucks) ... Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Build Server is stuck (?)
Hello! As you might have noticed, the build server is stuck and does not build the recent PRs. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] INFO: pkg update manifest hash error in package readline
On 10/28/23 12:52, Stephan Althaus wrote: On 6/1/23 22:28, Stephan Althaus wrote: I have issued a package rebuild. This will hopefully create a correct hash. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Yes, the hash error is gone and the package can be downloaded now. Thanks!! Regards, Stephan Hello! I am hit by the same error today within a zone: Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: pkg://openindiana.org/library/readline@6.3,5.11-2023.0.0.5:20230906T050309Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/library/readline@6.3,5.11-2023.0.0.5:20230906T050309Z expected: cb02cbdaa6cda8a1ed1915185fe38015a6dce552 computed: a159de951797140d09295c42401e58092f2c8fd9. (happened 4 times) A pkg update in the global and an other local zone have been successful yesterday... A pkg refresh --full && pkg update an an other global zone got this: pkg refresh --full && pkg update && exit Creating Plan (Package planning: 64/614): / Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: pkg://openindiana.org/developer/golang-120@1.20.10,5.11-2023.0.0.0:20231011T212216Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/developer/golang-120@1.20.10,5.11-2023.0.0.0:20231011T212216Z expected: cefb854835a501b27a457630019ebc73cb3c099d computed: e3d9c336f4cb17b3e0a8ea59c8a2003c4eae6db1. (happened 4 times) I don't understand this. Maybe this is an error in my local network/transport ?? I will reset my network now and try again. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Seems to be not network related on my side.. Anyone else seeing this ? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] INFO: pkg update manifest hash error in package readline
On 6/1/23 22:28, Stephan Althaus wrote: I have issued a package rebuild. This will hopefully create a correct hash. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Yes, the hash error is gone and the package can be downloaded now. Thanks!! Regards, Stephan Hello! I am hit by the same error today within a zone: Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: pkg://openindiana.org/library/readline@6.3,5.11-2023.0.0.5:20230906T050309Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/library/readline@6.3,5.11-2023.0.0.5:20230906T050309Z expected: cb02cbdaa6cda8a1ed1915185fe38015a6dce552 computed: a159de951797140d09295c42401e58092f2c8fd9. (happened 4 times) A pkg update in the global and an other local zone have been successful yesterday... A pkg refresh --full && pkg update an an other global zone got this: pkg refresh --full && pkg update && exit Creating Plan (Package planning: 64/614): / Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: pkg://openindiana.org/developer/golang-120@1.20.10,5.11-2023.0.0.0:20231011T212216Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/developer/golang-120@1.20.10,5.11-2023.0.0.0:20231011T212216Z expected: cefb854835a501b27a457630019ebc73cb3c099d computed: e3d9c336f4cb17b3e0a8ea59c8a2003c4eae6db1. (happened 4 times) I don't understand this. Maybe this is an error in my local network/transport ?? I will reset my network now and try again. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] zpool status rpool not consistent with diskinfo
On 9/20/23 15:23, Udo Grabowski (IMK) wrote: Hello! Thanks for the hints, but no change with touch /reconfigure zpool reopen rm /etc/zfs/zpool.cache should i try to "zpool offline -t c3t2d0s0" one device and reboot? It could also be that the label entry is not updated. zdb -l /dev/dsk/cxtyd0s0 should show the correct one at least in the first label. I once had such a case, and had to boot into an older openindiana version to get that fixed, but that depends of course on the available and activated pool features. -- 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 Hello! I can confirm that the zfs label have not been updated. I don't know if it a 'problem' as the root pool is ONLINE, but if you use the devices names stated in the zpool status, other commands may fail (just like zdb -l ) because the device names are wrong :-/ However, the possible solution is to boot from live media an import/export the root pool... Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] zpool status rpool not consistent with diskinfo
On 9/20/23 13:59, Toomas Soome via openindiana-discuss wrote: You can try 'zpool reopen’, if that will not help, remove /etc/zfs/zpool.cache. There is some issue that information in zpool.cache is not updated… rgds, toomas On 20. Sep 2023, at 14:14, Stephan Althaus wrote: Hello! I swapped 2 of 3 root-pool drives (after power off) to different controllers, (with power-off-saving battery pack) and now the device names are inconsistent - the device names in the pool context have not been not updated. Boot message was shown: "NOTICE: Performing full ZFS device scan!" Messages regarding the move where also in the logs: messages:923126:Sep 20 09:24:21 oi genunix: [ID 176336 kern.notice] devid register: devid for /pci@0,0/pci8086,c05@1,1/pci1028,1f1c@0/iport@20/disk@p5,0 does not match. stored: id1,sd@TATA_Patriot_P220_1TBP220HBCB230710002657, new: id1,sd@TATA_EMTEC_X150_480GB511200729140001240__. messages:923339:Sep 20 09:24:32 oi zfs: [ID 101897 kern.notice] NOTICE: vdev_disk_open /dev/dsk/c3t2d0s0: update devid from 'id1,sd@SATA_EMTEC_X150_480GB__511200729140001240/a' to 'id1,sd@TATA_EMTEC_X150_480GB511200729140001240__/a' ... but not for the "SCSI" ones (sata disks on SAS controller LSI JOBD, driver mpt_sas i believe) Pool status is ok. Is there a command to update this info? Reboot did not change the drive info. Importing/exporting the rpool via OI-USB-live-boot-stick would help, do i really have to do so ? # diskinfo TYPEDISKVID PID SIZE RMV SSD SCSIc7t5d0 EMTECX150 480GB447.13 GiB no yes SCSIc8t4d0 Patriot P220 1TB 953.87 GiB no yes SATAc3t3d0 EMTECX150 480GB447.13 GiB no yes $ zpool status pool: rpool1 state: ONLINE scan: resilvered 381G in 0 days 00:51:40 with 0 errors on Tue Sep 12 16:36:55 2023 config: NAME STATE READ WRITE CKSUM rpool1ONLINE 0 0 0 mirror-0ONLINE 0 0 0 c3t2d0s0 ONLINE 0 0 0 c3t3d0s0 ONLINE 0 0 0 c7t5d0s0 ONLINE 0 0 0 Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Thanks for the hints, but no change with touch /reconfigure zpool reopen rm /etc/zfs/zpool.cache should i try to "zpool offline -t c3t2d0s0" one device and reboot? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] zpool status rpool not consistent with diskinfo
Hello! I swapped 2 of 3 root-pool drives (after power off) to different controllers, (with power-off-saving battery pack) and now the device names are inconsistent - the device names in the pool context have not been not updated. Boot message was shown: "NOTICE: Performing full ZFS device scan!" Messages regarding the move where also in the logs: messages:923126:Sep 20 09:24:21 oi genunix: [ID 176336 kern.notice] devid register: devid for /pci@0,0/pci8086,c05@1,1/pci1028,1f1c@0/iport@20/disk@p5,0 does not match. stored: id1,sd@TATA_Patriot_P220_1TBP220HBCB230710002657, new: id1,sd@TATA_EMTEC_X150_480GB511200729140001240__. messages:923339:Sep 20 09:24:32 oi zfs: [ID 101897 kern.notice] NOTICE: vdev_disk_open /dev/dsk/c3t2d0s0: update devid from 'id1,sd@SATA_EMTEC_X150_480GB__511200729140001240/a' to 'id1,sd@TATA_EMTEC_X150_480GB511200729140001240__/a' ... but not for the "SCSI" ones (sata disks on SAS controller LSI JOBD, driver mpt_sas i believe) Pool status is ok. Is there a command to update this info? Reboot did not change the drive info. Importing/exporting the rpool via OI-USB-live-boot-stick would help, do i really have to do so ? # diskinfo TYPE DISK VID PID SIZE RMV SSD SCSI c7t5d0 EMTEC X150 480GB 447.13 GiB no yes SCSI c8t4d0 Patriot P220 1TB 953.87 GiB no yes SATA c3t3d0 EMTEC X150 480GB 447.13 GiB no yes $ zpool status pool: rpool1 state: ONLINE scan: resilvered 381G in 0 days 00:51:40 with 0 errors on Tue Sep 12 16:36:55 2023 config: NAME STATE READ WRITE CKSUM rpool1 ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 c3t2d0s0 ONLINE 0 0 0 c3t3d0s0 ONLINE 0 0 0 c7t5d0s0 ONLINE 0 0 0 Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] VirtualBox status? -- please test 6.1.46
On 9/8/23 09:28, Carsten Grzemba via openindiana-discuss wrote: I have uploaded a package 6.1.46 on http://pkg.toc.de/userland which have passed my smoke tests. Please test and report results. Hello Carsten! Thanks for your efforts, virtualbox GUI is working. I also had problems using the newest nvidia driver with virtualbox GUI and did stay with 515 until now, 535 is working with virtualbox today. So everything is fine now. Thanks!!! Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] VirtualBox status?
On 9/6/23 23:25, Carl Brewer wrote: Is this now a "Wait for us to fix it" issue? I don't have the skill or resources (AFAIK) to be involved in recompiling/porting to gcc-10. Hello! I am not an expert either. May knowledge is sort of "if it builds with gcc-10 and gmake test is ok then i am happy - FAIL otherwise". At the moment i don't find time to work through the gcc7-package-list (since 06.08.2023 now) and the new room for my little daughter (3) isn't ready yet.. We are only a few people that are using illumos-based distributions, and we all have to work together, everyone with the time and skill that is there. Whilst being here i learn about how much work it is to keep a distribution on time, and sometimes how complicated it is to 'only' compile a packages with a different compiler :-/ I am interested in assisting and will do so when i find time again. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] VirtualBox status?
On 9/7/23 08:49, Aurélien Larcher wrote: On Wed, Sep 6, 2023 at 11:25 PM Carl Brewer wrote: On 25/08/2023 9:17 pm, Stephan Althaus wrote: YES, the GUI still doesn't work, HEADLESS does. Some (x11-)libs are not gcc-10 yet.. Could make a list of the libs you found? (i had at least one lib where 'gmake test' did have no positive tests :-/) Is this now a "Wait for us to fix it" issue? I don't have the skill or resources (AFAIK) to be involved in recompiling/porting to gcc-10. For those who need the gui, use pkg:// openindiana.org/system/virtualbox@6.1.40-2022.0.0.0:20221108T082551Z pfexec pkg install pkg:// openindiana.org/system/virtualbox@6.1.40-2022.0.0.0:20221108T082551Z pfexec pkg freeze virtualbox Would "freeze" break later updates? VB is up to 7.0.10 now, so this one's lagging a bit. Thank you Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! A first simple list of packages that are build with gcc-7 would contain the ones that are packaged before Dec-2022: pkg list |grep 2020 Be aware these are only the installed ones. On my Laptop this command finds 132 entries. I had some scripts to build a list, with finding the compiler of a lib, then search the package for that lib, but i don't find that scripts anymore, so below is my list as of 2023-08-6, locally installed packages here, too.. I will search for the scripts that you can run it on your own.. P.S. Maybe the timestamp of the Makefile in the source tree would be a hint, too - didn't thought of that before.. Regards, Stephan _ pkg:/audio/faad2@2.7-2022.0.0.3 pkg:/audio/twolame@0.3.13-2020.0.1.2 pkg:/audio/wavpack@5.6.0-2022.0.0.0 pkg:/codec/libtheora@1.1.1-2022.0.0.3 pkg:/database/berkeleydb-5@5.3.28-2022.0.0.1 pkg:/database/geoip@1.6.12-2022.0.0.1 pkg:/desktop/character-map/gucharmap@3.18.2-2022.0.0.2 pkg:/desktop/compiz@0.8.18-2020.0.1.1 pkg:/desktop/compiz/plugin/compiz-fusion-extra@0.8.18-2020.0.1.0 pkg:/desktop/mate/caja/caja-extensions@1.26.1-2022.0.0.0 pkg:/desktop/mate/control-center@1.26.0-2022.0.0.1 pkg:/desktop/window-manager/enlightenment@0.21.9-2020.0.1.0 pkg:/desktop/window-manager/notion-3@2015061300-2020.0.1.0 pkg:/developer/build/autogen@5.18.16-2022.0.0.3 pkg:/developer/check@0.15.2-2020.0.1.0 pkg:/developer/clang-13@13.0.1-2022.0.0.0 pkg:/developer/debug/mdb@0.5.11-2023.0.0.21760 pkg:/developer/ui-designer/glade@3.22.2-2022.0.0.0 pkg:/developer/versioning/mercurial-37@5.9.3-2022.0.0.1 pkg:/developer/versioning/mercurial-39@5.9.3-2022.0.0.1 pkg:/diagnostic/scanpci@0.14-2020.0.1.1 pkg:/driver/graphics/drm@0.5.11-2022.0.0.73 pkg:/gnome/accessibility/at-spi2-atk@2.24.1-2022.0.0.0 pkg:/gnome/accessibility/at-spi2-core@2.24.1-2022.0.0.2 pkg:/gnome/config/dconf@0.24.0-2022.0.0.2 pkg:/gnome/help-viewer/yelp@3.20.1-2022.0.0.1 pkg:/gnome/theme/gtk2-engines-murrine@0.98.2-2022.0.0.0 pkg:/gnome/theme/gtk2-engines@2.20.2-2022.0.0.1 pkg:/gnome/theme/nimbus@1.0-2020.0.1.4 pkg:/image/library/sdl-image@1.2.12-2020.0.1.0 pkg:/library/audio/libcdio@2.1.0-2022.0.0.0 pkg:/library/audio/libdca@0.0.7-2022.0.0.1 pkg:/library/audio/libgsm@1.0.22-2022.0.0.0 pkg:/library/audio/libmpcdec@1.2.6-2022.0.0.1 pkg:/library/c++/libetonyek@0.1.10-2022.0.0.0 pkg:/library/c++/libodfgen@0.1.8-2020.0.1.0 pkg:/library/c++/libpagemaker@0.0.4-2022.0.0.2 pkg:/library/c++/libstaroffice@0.0.7-2022.0.0.1 pkg:/library/desktop/geocode-glib@3.24.0-2022.0.0.2 pkg:/library/desktop/gtk3/gtk3-nocsd@3-2020.0.1.3 pkg:/library/desktop/gtkspell@2.0.16-2022.0.0.2 pkg:/library/desktop/gtkspell3@3.0.10-2022.0.0.0 pkg:/library/desktop/json-glib@1.6.6-2022.0.0.2 pkg:/library/desktop/libbonoboui@2.24.5-2022.0.0.2 pkg:/library/desktop/libgdata@0.18.1-2022.0.0.0 pkg:/library/desktop/libgksu@2.0.12-2022.0.0.6 pkg:/library/desktop/libglade@2.6.4-2022.0.0.3 pkg:/library/desktop/libgnome@2.32.1-2022.0.0.3 pkg:/library/desktop/libgnomecanvas@2.30.3-2022.0.0.2 pkg:/library/desktop/libgnomeui@2.24.5-2022.0.0.4 pkg:/library/desktop/libpeas@1.20.0-2022.0.0.4 pkg:/library/desktop/libpeas/libpeas-python3loader@1.20.0-2022.0.0.4 pkg:/library/desktop/libsexy@0.1.11-2020.0.1.3 pkg:/library/desktop/libvisual@0.4.0-2020.0.1.0 pkg:/library/desktop/libvisual/plugins@0.4.0-2020.0.1.2 pkg:/library/desktop/libwnck3@3.32.0-2022.0.0.0 pkg:/library/desktop/libxklavier@5.4-2020.0.1.1 pkg:/library/desktop/mate/libmatemixer@1.26.0-2022.0.0.1 pkg:/library/desktop/pangox-compat@0.0.2-2022.0.0.2 pkg:/library/desktop/ptlib@2.10.11-2020.0.1.4 pkg:/library/desktop/startup-notification@0.12-2020.0.1.0 pkg:/library/desktop/vte@0.28.2-2022.0.0.6 pkg:/library/desktop/xdg/libcanberra@0.26-2022.0.0.4 pkg:/library/freetds@1.0.94-2020.0.1.0 pkg:/library/glib-networking@2.42.0-2022.0.0.4 pkg:/lib
Re: [OpenIndiana-discuss] NVidia driver Lenovo P52
On 9/6/23 13:00, Marcel Telka wrote: On Wed, Sep 06, 2023 at 12:55:53PM +0200, Olaf Bohlen wrote: Aug 9 13:15:35 p52 nvidia_modeset: [ID 107833 kern.notice] Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 470.182.03 Fri Feb 24 03:20:38 UTC 2023 Try to update. The latest nvidia-470 driver in the repo is 470.199.02. HTH Hi! I tried a P51 some time ago. It had a "optimus" called constellation between the intel and the nvidia graphics. If you have this, i doubt you have a chance to get nvidia graphics to work. If you have very dedicated hardware paths for each graphic controller, you could be able to completely disable the intel graphics. On my DELL Precision 7720 i am able to do it this way. Have a close look into your BIOS settings. Maybe you are lucky with a newer driver, P1000 is supported by 525 and 535, see here: https://www.nvidia.com/Download/driverResults.aspx/210650/en-us/ Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] VirtualBox status?
On 8/25/23 12:58, Predrag Zečević via openindiana-discuss wrote: On 8/25/23 12:35, Carsten Grzemba via openindiana-discuss wrote: Unfortunately starting the GUI VirtualBox still leads to crash VBoxSVC (SIGABRT) and no installed VM's listed in the GUI. $C 7fffadf5e270 libc.so.1`_lwp_kill+0xa() 7fffadf5e2a0 libc.so.1`raise+0x22(6) 7fffadf5e2f0 libc.so.1`abort+0x58() 7fffadf5e330 libstdc++.so.6.0.28`__gnu_cxx::__verbose_terminate_handler+0x65() 7fffadf5e350 libstdc++.so.6.0.28`__cxxabiv1::__terminate+9() 7fffadf5e370 0x7fffa67f6099() 7fffadf5e460 libstdc++.so.6.0.28`__gxx_personality_v0+0x2bc() 7fffadf5e630 libgcc_s.so.1`_Unwind_RaiseException_Phase2+0xa6() 7fffadf5e9e0 libgcc_s.so.1`_Unwind_RaiseException+0x331() 7fffadf5ea10 libstdc++.so.6.0.28`__cxa_throw+0x40() 7fffadf5eb90 Medium::i_queryInfo+0x6a6() 7fffadf5ebd0 Medium::refreshState+0x8d() 7fffadf5ec20 MediumWrap::RefreshState+0xd1() 7fffadf5ecd0 VBoxXPCOM.so`XPTC_InvokeByIndex+0x13f() 7fffadf5eea0 VBoxXPCOMIPCC.so`ipcDConnectService::OnInvoke+0x3bc() 7fffadf5eeb0 VBoxXPCOMIPCC.so`ipcDConnectService::OnIncomingRequest+0x28() 7fffadf5ef00 VBoxXPCOMIPCC.so`DConnectWorker::Run+0x137() 7fffadf5ef20 VBoxXPCOM.so`nsThread::Main+0x23() 7fffadf5ef40 VBoxXPCOM.so`_pt_root+0x86() 7fffadf5ef50 VBoxXPCOM.so`_pt_iprt_root+0xc() 7fffadf5ef70 VBoxRT.so`rtThreadMain+0x34() 7fffadf5efb0 VBoxRT.so`rtThreadNativeMain+0x43() 7fffadf5efe0 libc.so.1`_thrp_setup+0x77(7fffaeaa4a40) 7fffadf5eff0 libc.so.1`_lwp_start() also VirtualBox crashes some time with SIGSEGV $C 7fffbfffe810 libQt5Widgets.so.5.15.4`QToolBar::toolButtonStyle() 7fffbfffe850 UIVirtualBoxManagerWidget::cleanup+0x12() 7fffbfffe870 UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x2a() 7fffbfffe890 UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x12() 7fffbfffe900 libQt5Core.so.5.15.4`QObject::event+0x40() 7fffbfffe930 libQt5Widgets.so.5.15.4`QApplicationPrivate::notify_helper+0x82() 7fffbfffe9a0 libQt5Core.so.5.15.4`QCoreApplication::notifyInternal2+0x111() 7fffbfffea40 libQt5Core.so.5.15.4`QCoreApplicationPrivate::sendPostedEvents+0x170() 7fffbfffea60 libQt5Core.so.5.15.4`postEventSourceDispatch+0x1b() 7fffbfffeae0 libglib-2.0.so.0.7400.7`g_main_context_dispatch+0x23d() 7fffbfffeb40 libglib-2.0.so.0.7400.7`g_main_context_iterate.constprop.0+0x1c8() 7fffbfffeb60 libglib-2.0.so.0.7400.7`g_main_context_iteration+0x30() 7fffbfffebb0 libQt5Core.so.5.15.4`QEventDispatcherGlib::processEvents+0x64() 7fffbfffec30 libQt5Core.so.5.15.4`QEventLoop::exec+0x11b() 7fffbfffec80 UICommon.so`QIDialog::execute+0xd5() 7fffbfffed20 UICommon.so`UIMessageCenter::showMessageBox+0x33e() 7fffbfffedb0 UICommon.so`UIMessageCenter::message+0xff() 7fffbfffee20 UICommon.so`UIMessageCenter::error+0x3e() 7fffbfffeee0 UICommon.so`UIMessageCenter::cannotSetExtraData+0xe3() 7fffb130 UICommon.so`UIExtraDataManager::setExtraDataString+0x546() 7fffb170 UICommon.so`UIExtraDataManager::setSelectorWindowToolBarVisible+0x6a() 7fffb1b0 UIVirtualBoxManagerWidget::saveSettings+0x2f() 7fffb1f0 UIVirtualBoxManagerWidget::cleanup+0x12() 7fffb210 UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x2a() 7fffb230 UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x12() 7fffb250 UIVirtualBoxManager::cleanupWidgets+0x22() 7fffb270 UIVirtualBoxManager::cleanup+0x3a() 7fffb280 UIVirtualBoxManager::destroy+0x4b() 7fffb350 libQt5Core.so.5.15.4`void doActivate+0x4d4() 7fffb380 libQt5Core.so.5.15.4`QCoreApplication::aboutToQuit+0x2a() 7fffb3a0 libQt5Core.so.5.15.4`QCoreApplicationPrivate::execCleanup+0x49() 7fffb3f0 libQt5Core.so.5.15.4`QCoreApplication::exec+0x9c() 7fffb4d0 TrustedMain+0x27c() 7fffb560 main+0x5f() 7fffb590 _start_crt+0x87() 7fffb5a0 _start+0x18() Am 25.08.23 09:23 schrieb Stephan Althaus : On 8/25/23 08:46, Predrag Zečević via openindiana-discuss wrote: On 8/25/23 07:25, Carl Brewer wrote: Hey everyone, Before I break a server .. Is VirtualBox running ok on current OI? Last I saw, Russell was having trouble with it in July. Thank you! Carl Hi Carl, I had to boot in BE created in June, since one from August is not working I guess we need to wait for fix... Check mailing list for "Problem with VirtualBox since upgrade today", as some workaround is proposed there (I have decided to switch complete BE back) Regards. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! I did a pkg update now on my server with one headless VB-vm: $ beadm list BE Active Mountpoint Space Policy Created openindiana-2022:11:16 - - 124.32M stati
Re: [OpenIndiana-discuss] VirtualBox status?
On 8/25/23 08:46, Predrag Zečević via openindiana-discuss wrote:
On 8/25/23 07:25, Carl Brewer wrote:
Hey everyone,
Before I break a server .. Is VirtualBox running ok on current OI?
Last I saw, Russell was having trouble with it in July.
Thank you!
Carl
Hi Carl,
I had to boot in BE created in June, since one from August is not working
I guess we need to wait for fix...
Check mailing list for "Problem with VirtualBox since upgrade today",
as some workaround is proposed there (I have decided to switch
complete BE back)
Regards.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Hello!
I did a pkg update now on my server with one headless VB-vm:
$ beadm list
BE Active Mountpoint Space Policy Created
openindiana-2022:11:16 - - 124.32M static 2022-11-16 18:00
openindiana-2023:06:23-2 - - 81.33M static 2023-06-23 13:44
openindiana-2023:08:25 NR / 105.67G static 2023-08-25 08:57
$ VBoxManage startvm aLinux -type headless
Waiting for VM "aLinux" to power on...
VM "aLinux" has been successfully started.
$ VBoxManage list vms
"aLinux" {9019c57b-7dd4-4ef9-bc96-c20185674ed2}
$ VBoxManage list runningvms
"aLinux" {9019c57b-7dd4-4ef9-bc96-c20185674ed2}
$ ssh applepie@projekte
applepie@projekte's password:
Welcome to Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-156-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
System information disabled due to load higher than 2.0
* Strictly confined Kubernetes makes edge and IoT secure. Learn how
MicroK8s
just raised the bar for easy, resilient and secure K8s cluster
deployment.
https://ubuntu.com/engage/secure-kubernetes-at-the-edge
Expanded Security Maintenance for Applications is not enabled.
22 updates can be applied immediately.
To see these additional updates run: apt list --upgradable
Enable ESM Apps to receive additional future security updates.
See https://ubuntu.com/esm or run: sudo pro status
Last login: Tue Jul 11 15:17:16 2023 from 192.168.2.63
q... So my VM is running on today's OI.
Regards,
Stephan
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] VirtualBox status?
On 8/25/23 07:25, Carl Brewer wrote: Hey everyone, Before I break a server .. Is VirtualBox running ok on current OI? Last I saw, Russell was having trouble with it in July. Thank you! Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! I will give it a try now, pkg update is running, i'll report back. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] No sound output - no rights ?
On 8/24/23 23:28, Peter Tribble wrote: On Thu, Aug 24, 2023 at 9:21 PM Stephan Althaus < stephan.alth...@duedinghausen.eu> wrote: Hello! I have no audio output - anyone else, too ? Are you logged in on the graphical console? The way this normally works is that the login display manager will change ownership of the audio devices to whoever is logged in on the console, using logindevperm(5) via di_devperm_login() and di_devperm_logout() - there's a patch 11-login-device-permissions.patch for lightdm that actually does this for you. $ prtconf -d | grep -i audio pci1028,17b1 (pciex10de,fbc) [NVIDIA Corporation GM107 High Definition Audio Controller [GeForce 940MX]], instance #6 pci1028,7b1 (pciex8086,a171) [Intel Corporation CM238 HD Audio Controller], instance #5 $ sudo audioctl list-devices Password: audiohd#5 audiohd#6 $ audiotest Sound subsystem and version: SunOS Audio 4.0 (0x00040003) Platform: SunOS 5.11 illumos-a98a962ff1 i86pc /dev/sound/audiohd:5dsp: Permission denied /dev/sound/audiohd:6dsp: Permission denied *** Errors were detected *** $ ls -l /dev/sound/audiohd:5dsp lrwxrwxrwx 1 root root 49 Apr 11 2019 /dev/sound/audiohd:5dsp -> ../../devices/pci@0,0/pci1028,7b1@1f ,3:sound,dsp5 $ ls -l /devices/pci@0,0/pci1028,7b1@1f,3:sound,dsp5 crw--- 1 root root 30, 81 Apr 11 2019 /devices/pci@0,0/pci1028,7b1@1f,3:sound,dsp5 There's no group having rights to access the device, nor "others" - is this normal ? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Thanks to Udo and Peter for the insights! This morning (after reboot) the sound is back. I switched the Monitor device forth and back yesterday evening, this might be the cause of the device-files belonging to root:root. I will try that later. Thanks! Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] No sound output - no rights ?
Hello! I have no audio output - anyone else, too ? $ prtconf -d | grep -i audio pci1028,17b1 (pciex10de,fbc) [NVIDIA Corporation GM107 High Definition Audio Controller [GeForce 940MX]], instance #6 pci1028,7b1 (pciex8086,a171) [Intel Corporation CM238 HD Audio Controller], instance #5 $ sudo audioctl list-devices Password: audiohd#5 audiohd#6 $ audiotest Sound subsystem and version: SunOS Audio 4.0 (0x00040003) Platform: SunOS 5.11 illumos-a98a962ff1 i86pc /dev/sound/audiohd:5dsp: Permission denied /dev/sound/audiohd:6dsp: Permission denied *** Errors were detected *** $ ls -l /dev/sound/audiohd:5dsp lrwxrwxrwx 1 root root 49 Apr 11 2019 /dev/sound/audiohd:5dsp -> ../../devices/pci@0,0/pci1028,7b1@1f,3:sound,dsp5 $ ls -l /devices/pci@0,0/pci1028,7b1@1f,3:sound,dsp5 crw--- 1 root root 30, 81 Apr 11 2019 /devices/pci@0,0/pci1028,7b1@1f,3:sound,dsp5 There's no group having rights to access the device, nor "others" - is this normal ? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Problem with VirtualBox since upgrade today
On 8/5/23 14:14, Stephan Althaus wrote:
On 8/5/23 13:19, Stephan Althaus wrote:
Hello!
A little time has passed, and *some* packages have been rebuild in
the meantime, but the error still persists.
With an "pkg update" yesterday evening the VB GUI has the same errors.
Looking into the lib dependencies i find some X libs that have to be
rebuild.
I looked like this:
$ ldd /opt/VirtualBox/amd64/VirtualBox|awk '{print $3}'|sort -u|xargs
-n 1 ~/mcs-p.sh |less
.. and sorting out the output i find some X libs that are candidates
(see below),
i have made a PR for them, but i believe there will be more to find..
Regards,
Stephan
Hello!
After installing the newly build libs the GUI still doesnt work.
My search does only list GCC 10:
$ ldd /opt/VirtualBox/amd64/VirtualBox|awk '{print $3}'|sort -u|xargs
-n 1 ~/mcs-p.sh |grep GCC|sort -u
GCC: (OpenIndiana 10.4.0-oi-1) 10.4.0
GCC: (OpenIndiana 10.4.0-oi-2) 10.4.0
GCC: (OpenIndiana 10.4.0-oi-3) 10.4.0
GCC: (OpenIndiana 10.4.0-oi-4) 10.4.0
GCC: (OpenIndiana 10.5.0-oi-0) 10.5.0
So its something different..
Regards,
Stephan
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Hello!
I did another search, there is gio a candidate among others..
$ find /usr/lib -name "*.so*" | xargs -n 1 ~/mcs-p.sh|grep -v 2023 |grep
-v December|sort -u
/usr/lib/amd64/bonobo/monikers/libmoniker_extra_2.so:ld: Software
Generation Utilities - Solaris Link Editors: 5.11-1.1784
(illumos)@(#)illumos illumos-b9a2a14b8f July 2022GCC: (OpenIndiana
7.5.0-il-0) 7.5.0
/usr/lib/amd64/bonobo/monikers/libmoniker_std_2.so:ld: Software
Generation Utilities - Solaris Link Editors: 5.11-1.1784
(illumos)@(#)illumos illumos-b9a2a14b8f July 2022GCC: (OpenIndiana
7.5.0-il-0) 7.5.0
/usr/lib/amd64/caja-sendto/plugins/libnstburn.so:ld: Software Generation
Utilities - Solaris Link Editors: 5.11-1.1784 (illumos)@(#)illumos
illumos-119d61ccb9 August 2022GCC: (OpenIndiana 7.5.0-il-0) 7.5.0
/usr/lib/amd64/caja-sendto/plugins/libnstemailclient.so:ld: Software
Generation Utilities - Solaris Link Editors: 5.11-1.1784
(illumos)@(#)illumos illumos-119d61ccb9 August 2022GCC: (OpenIndiana
7.5.0-il-0) 7.5.0
/usr/lib/amd64/caja-sendto/plugins/libnstgajim.so:ld: Software
Generation Utilities - Solaris Link Editors: 5.11-1.1784
(illumos)@(#)illumos illumos-119d61ccb9 August 2022GCC: (OpenIndiana
7.5.0-il-0) 7.5.0
/usr/lib/amd64/caja-sendto/plugins/libnstpidgin.so:ld: Software
Generation Utilities - Solaris Link Editors: 5.11-1.1784
(illumos)@(#)illumos illumos-119d61ccb9 August 2022GCC: (OpenIndiana
7.5.0-il-0) 7.5.0
/usr/lib/amd64/caja-sendto/plugins/libnstremovable_devices.so:ld:
Software Generation Utilities - Solaris Link Editors: 5.11-1.1784
(illumos)@(#)illumos illumos-119d61ccb9 August 2022GCC: (OpenIndiana
7.5.0-il-0) 7.5.0
/usr/lib/amd64/caja/extensions-2.0/libcaja-gksu.so:ld: Software
Generation Utilities - Solaris Link Editors: 5.11-1.1784
(illumos)@(#)illumos illumos-119d61ccb9 August 2022GCC: (OpenIndiana
7.5.0-il-0) 7.5.0
/usr/lib/amd64/caja/extensions-2.0/libcaja-image-converter.so:ld:
Software Generation Utilities - Solaris Link Editors: 5.11-1.1784
(illumos)@(#)illumos illumos-119d61ccb9 August 2022GCC: (OpenIndiana
7.5.0-il-0) 7.5.0
/usr/lib/amd64/caja/extensions-2.0/libcaja-open-terminal.so:ld: Software
Generation Utilities - Solaris Link Editors: 5.11-1.1784
(illumos)@(#)illumos illumos-119d61ccb9 August 2022GCC: (OpenIndiana
7.5.0-il-0) 7.5.0
/usr/lib/amd64/caja/extensions-2.0/libcaja-sendto.so:ld: Software
Generation Utilities - Solaris Link Editors: 5.11-1.1784
(illumos)@(#)illumos illumos-119d61ccb9 August 2022GCC: (OpenIndiana
7.5.0-il-0) 7.5.0
/usr/lib/amd64/caja/extensions-2.0/libcaja-share.so:ld: Software
Generation Utilities - Solaris Link Editors: 5.11-1.1784
(illumos)@(#)illumos illumos-119d61ccb9 August 2022GCC: (OpenIndiana
7.5.0-il-0) 7.5.0
/usr/lib/amd64/caja/extensions-2.0/libcaja-wallpaper.so:ld: Software
Generation Utilities - Solaris Link Editors: 5.11-1.1784
(illumos)@(#)illumos illumos-119d61ccb9 August 2022GCC: (OpenIndiana
7.5.0-il-0) 7.5.0
/usr/lib/amd64/caja/extensions-2.0/libcaja-xattr-tags.so:ld: Software
Generation Utilities - Solaris Link Editors: 5.11-1.1784
(illumos)@(#)illumos illumos-119d61ccb9 August 2022GCC: (OpenIndiana
7.5.0-il-0) 7.5.0
/usr/lib/amd64/gio/modules/libdconfsettings.so:ld: Software Generation
Utilities - Solaris Link Editors: 5.11-1.1784 (illumos)@(#)illumos
illumos-b9a2a14b8f July 2022GCC: (OpenIndiana 7.5.0-il-0) 7.5.0
/usr/lib/amd64/gio/modules/libgiognomeproxy.so:ld: Software Generation
Utilities - Solaris Link Editors: 5.11-1.1786 (illumos)@(#)illumos
illumos-218c1e8d5b November 2022GCC: (OpenIndiana 7.5.0-il-0) 7.5.0
/usr/lib/amd64/gio/modules/libgiognutls.so:ld: Software Generation
Utilities - Solaris
Re: [OpenIndiana-discuss] Problem with VirtualBox since upgrade today
On 8/5/23 13:19, Stephan Althaus wrote:
Hello!
A little time has passed, and *some* packages have been rebuild in the
meantime, but the error still persists.
With an "pkg update" yesterday evening the VB GUI has the same errors.
Looking into the lib dependencies i find some X libs that have to be
rebuild.
I looked like this:
$ ldd /opt/VirtualBox/amd64/VirtualBox|awk '{print $3}'|sort -u|xargs
-n 1 ~/mcs-p.sh |less
.. and sorting out the output i find some X libs that are candidates
(see below),
i have made a PR for them, but i believe there will be more to find..
Regards,
Stephan
Hello!
After installing the newly build libs the GUI still doesnt work.
My search does only list GCC 10:
$ ldd /opt/VirtualBox/amd64/VirtualBox|awk '{print $3}'|sort -u|xargs -n
1 ~/mcs-p.sh |grep GCC|sort -u
GCC: (OpenIndiana 10.4.0-oi-1) 10.4.0
GCC: (OpenIndiana 10.4.0-oi-2) 10.4.0
GCC: (OpenIndiana 10.4.0-oi-3) 10.4.0
GCC: (OpenIndiana 10.4.0-oi-4) 10.4.0
GCC: (OpenIndiana 10.5.0-oi-0) 10.5.0
So its something different..
Regards,
Stephan
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Problem with VirtualBox since upgrade today
On 7/14/23 17:28, Carsten Grzemba via openindiana-discuss wrote: Am 14.07.23 14:53 schrieb Stephan Althaus: On 7/12/23 17:44, Carsten Grzemba via openindiana-discuss wrote: if the GCC7 - GCC10 mixup could the reason, there are libs involved which are GCC7 compiled: /usr/lib/amd64/libidn2.so.0.3.8 /usr/lib/amd64/libunistring.so.2.2.0 /usr/lib/amd64/libssh2.so.1.0.1 -- Carsten Hello! i did a pkg update a few minutes ago, and the symptoms are the same. We will have to rebuild some more libs anyway, so ... If i could get a list of the direct dependencies "top-down" from virtualbox i will work on that (from next wednesday on, until then i doubt i have time..).. is there any script resolving that? P.S. For anyone interested, the 'old' package does still work (as a temporary workaround), i just had to do a $ pfexec pkg installpkg://openindiana.org/system/virtualbox@6.1.40,5.11-2022.0.0.0:20221108T082551Z and for the next few updates this will prevent VB being updated: $ pfexec pkg freezepkg://openindiana.org/system/virtualbox@6.1.40,5.11-2022.0.0.0:20221108T082551Z Regards and thanks in advance, Stephan All the other I found build after 20.12.2022, so they should already be built with GCC 10. I check the loaded libs from core file with $ mcs -p lib.so I see in the core that it crashs nearXPTC_InvokeByIndex and it seems it should be only an exception, not a crash.? $C 7fffaddae270 libc.so.1`_lwp_kill+0xa() 7fffaddae2a0 libc.so.1`raise+0x22(6) 7fffaddae2f0 libc.so.1`abort+0x58() 7fffaddae330 0x7fffacd1a58a() 7fffaddae350 libstdc++.so.6.0.28`__cxxabiv1::__terminate+9() 7fffaddae370 0x7fffacd16099() 7fffaddae460 libstdc++.so.6.0.28`__gxx_personality_v0+0x2bc() 7fffaddae630 libgcc_s.so.1`_Unwind_RaiseException_Phase2+0xa6() 7fffaddae9e0 libgcc_s.so.1`_Unwind_RaiseException+0x331() 7fffaddaea10 libstdc++.so.6.0.28`__cxa_throw+0x40() 7fffaddaeb90 Medium::i_queryInfo+0x687() 7fffaddaebd0 Medium::refreshState+0x8d() 7fffaddaec20 MediumWrap::RefreshState+0xd1() 7fffaddaecd0 VBoxXPCOM.so`XPTC_InvokeByIndex+0x13f() 7fffaddaeea0 VBoxXPCOMIPCC.so`ipcDConnectService::OnInvoke+0x3bc() 7fffaddaeeb0 VBoxXPCOMIPCC.so`ipcDConnectService::OnIncomingRequest+0x28() 7fffaddaef00 VBoxXPCOMIPCC.so`DConnectWorker::Run+0x137() 7fffaddaef20 VBoxXPCOM.so`nsThread::Main+0x23() 7fffaddaef40 VBoxXPCOM.so`_pt_root+0x86() 7fffaddaef50 VBoxXPCOM.so`_pt_iprt_root+0xc() 7fffaddaef70 VBoxRT.so`rtThreadMain+0x34() 7fffaddaefb0 VBoxRT.so`rtThreadNativeMain+0x43() 7fffaddaefe0 libc.so.1`_thrp_setup+0x77(7fffaea95a40) 7fffaddaeff0 libc.so.1`_lwp_start() or ::status debugging core file of VBoxManage (64-bit) from notebookcg2 file: /opt/VirtualBox/amd64/VBoxManage initial argv: /opt/VirtualBox/amd64/VBoxManage list vms threading model: native threads status: process terminated by SIGABRT (Abort), pid=4743 uid=1005 code=-1 $G C++ symbol demangling enabled $C 7fffbfffddf0 libc.so.1`_lwp_kill+0xa() 7fffbfffde20 libc.so.1`raise+0x22(6) 7fffbfffde70 libc.so.1`abort+0x58() 7fffbfffdeb0 libstdc++.so.6.0.28`__gnu_cxx::__verbose_terminate_handler+0x65() 7fffbfffded0 libstdc++.so.6.0.28`__cxxabiv1::__terminate+9() 7fffbfffdef0 0x7fffacf16099() 7fffbfffdfe0 libstdc++.so.6.0.28`__gxx_personality_v0+0x2bc() 7fffbfffe1b0 libgcc_s.so.1`_Unwind_RaiseException_Phase2+0xa6() 7fffbfffe560 libgcc_s.so.1`_Unwind_RaiseException+0x331() 7fffbfffe590 libstdc++.so.6.0.28`__cxa_throw+0x40() 7fffbfffe610 VBoxC.so`VirtualBoxClient::init+0x308() 7fffbfffe630 VBoxC.so`VirtualBoxClient::FinalConstruct+0x10() 7fffbfffe660 VBoxC.so`VirtualBoxClientConstructor+0x101() 7fffbfffe670 VBoxXPCOM.so`nsGenericFactory::CreateInstance+0x1f() 7fffbfffe6c0 VBoxXPCOM.so`nsComponentManagerImpl::CreateInstance+0x7c() 7fffbfffe710 com::GlueCreateInstance+0x52() 7fffb7c0 main+0x4aa() 7fffb7f0 _start_crt+0x87() 7fffb800 _start+0x18() ::objects BASE LIMIT SIZE NAME 40 56f000 16f000 /opt/VirtualBox/amd64/VBoxManage 7fffa117 7fffa11ef000 7f000 /opt/VirtualBox/amd64/VBoxDDU.so 7fffad4c 7fffad869000 3a9000 /opt/VirtualBox/amd64/VBoxRT.so 7fffa178c000 7fffa179 4000 /lib/amd64/libthread.so.1 7fffa101 7fffa114e000 13e000 /opt/VirtualBox/amd64/VBoxXPCOM.so 7ffface1 7fffad02b000 21b000 /usr/gcc/10/lib/amd64/libstdc++.so.6.0.28 7fffacde 7fffacdfb000 1b000 /usr/gcc/10/lib/amd64/libgcc_s.so.1 7fffaf2f 7fffaf467000 177000 /lib/amd64/libc.so.1 7fffad4a 7fffad4a2000 2000 /lib/amd64/libkstat.so.1 7fffad48 7fffad487000 7000 /lib/amd64/libcontract.so.1 7fffad45 7fffad46b000 1b000 /usr/lib/amd64/libsmbios.so.1 7fffaed8 7fffaef1 19 /usr/lib/amd64/libxml2.so.2.10.4 7fffae28 7fffae293000 13000 /lib/amd64/libsocket.so.1 7fffad37 7fffad431000
Re: [OpenIndiana-discuss] Virtualbox webservice on 2023.05 won't start due to incorrect GSOAP version
On 7/28/23 19:23, Philip Kime wrote: Hmm, I already have this: pkg install pkg://openindiana.org/system/virtualbox@6.1.40,5.11-2022.0.0.0:20221108T082551Z No updates necessary for this image. and the GUI gives the GSOAP error in the ticket. PK -- Dr Phil. Philip Kime BA (Hons) Msc (Dist) PhD On 28 Jul 2023, at 18:40, Stephan Althaus wrote: On 7/28/23 17:43, Philip Kime wrote: I am trying to resolve the issue detailed on the bug tracker here: https://www.illumos.org/issues/15768 any ideas on how to deal with this until a new VB package is available? PK -- Dr Phil. Philip Kime BA (Hons) Msc (Dist) PhD ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! I use pfexec pkg install pkg://openindiana.org/system/virtualbox@6.1.40,5.11-2022.0.0.0:20221108T082551Z pfexec pkg freeze pkg://openindiana.org/system/virtualbox@6.1.40,5.11-2022.0.0.0:20221108T082551Z to get a working GUI. We have to get some more libs PR'ed for rebuild with GCC-10 until this is solved, and maybe the non-starting mate-system-monitor.. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Ah i see now... In oi-userland we need a PR for a virtualbox with a COMPONENT_REVISION=2 for example (or even better an update to 6.1.46), maybe the vboxwebsrv will run again, but we will fail in the GUI with the GCC-7-lib-problem.. i think we have to solve out this GCC-7 problem first.. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox webservice on 2023.05 won't start due to incorrect GSOAP version
On 7/28/23 17:43, Philip Kime wrote: I am trying to resolve the issue detailed on the bug tracker here: https://www.illumos.org/issues/15768 any ideas on how to deal with this until a new VB package is available? PK -- Dr Phil. Philip Kime BA (Hons) Msc (Dist) PhD ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! I use pfexec pkg install pkg://openindiana.org/system/virtualbox@6.1.40,5.11-2022.0.0.0:20221108T082551Z pfexec pkg freeze pkg://openindiana.org/system/virtualbox@6.1.40,5.11-2022.0.0.0:20221108T082551Z to get a working GUI. We have to get some more libs PR'ed for rebuild with GCC-10 until this is solved, and maybe the non-starting mate-system-monitor.. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] DELL Precision 7520 - TrackPoint/Touchpad not working
On 7/22/23 22:00, Olaf Bohlen wrote: Hello, I have a DELL Precision 7520 laptop here that has the mouse8042 driver loaded, the /var/adm/messages states also: Jul 22 21:39:44 hell i8042: [ID 526150 kern.info] 8042 device: mouse@1, mouse8042 # 0 Jul 22 21:39:44 hell genunix: [ID 936769 kern.info] mouse80420 is /pci@0,0/isa@1f/i8042@1,60/mouse@1 However neither Touchpad nor TrackPoint move the cursor. Also xev(1) doesn't see any event. An external USB mouse does work. Any ideas how to get the internal TrackPoint working? Thanks in advance, Olaf Hello Olaf! I have a 7720 and had a short look around a year ago, i believe that there is a driver that could be ported, but had no time to do it :-/ Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Problem with VirtualBox since upgrade today
On 7/12/23 17:44, Carsten Grzemba via openindiana-discuss wrote: if the GCC7 - GCC10 mixup could the reason, there are libs involved which are GCC7 compiled: /usr/lib/amd64/libidn2.so.0.3.8 /usr/lib/amd64/libunistring.so.2.2.0 /usr/lib/amd64/libssh2.so.1.0.1 -- Carsten Hello! i did a pkg update a few minutes ago, and the symptoms are the same. We will have to rebuild some more libs anyway, so ... If i could get a list of the direct dependencies "top-down" from virtualbox i will work on that (from next wednesday on, until then i doubt i have time..).. is there any script resolving that? P.S. For anyone interested, the 'old' package does still work (as a temporary workaround), i just had to do a $ pfexec pkg install pkg://openindiana.org/system/virtualbox@6.1.40,5.11-2022.0.0.0:20221108T082551Z and for the next few updates this will prevent VB being updated: $ pfexec pkg freeze pkg://openindiana.org/system/virtualbox@6.1.40,5.11-2022.0.0.0:20221108T082551Z Regards and thanks in advance, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Problem with VirtualBox since upgrade today
On 7/11/23 15:25, russell wrote:
Good Afternoon Stephan
I would advise against trying to build VirtualBox with gcc-7 due to
the incompatibility between gcc-10 and gcc-7 libraries, which causes
applications to crash or run incorrectly.
Switching the default build compiler to gcc-10 should eliminate the
mix of gcc-7 and gcc-10 compiled applications and the library
interdependency problems going forward.
Kind Regards
Russell
Hi Russell!
Ok sounds reasonable :-)
What are our next steps to get it working again?
Truss output from the new BV-build sounds weird (see below), but the
working one in the old BE does the same for gcc/10
So where can we start solving this?
Regards,
Stephan
$ truss /opt/VirtualBox/amd64/VirtualBox 2>&1 |grep -i err|grep "gcc/7"
stat("/usr/gcc/7/lib/amd64/libc.so.1", 0x7FFFBFFFDF80) Err#2 ENOENT
stat("/usr/gcc/7/lib/amd64/libsocket.so.1", 0x7FFFBFFFD780) Err#2 ENOENT
stat("/usr/gcc/7/lib/amd64/libXau.so.6", 0x7FFFBFFFDA80) Err#2 ENOENT
stat("/usr/gcc/7/lib/amd64/libxcb.so.1", 0x7FFFBFFFDD80) Err#2 ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libX11.so.4", 0x7FFFBFFFDAF0) Err#2 ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libxcb-xkb.so.1", 0x7FFFBFFFD8A0) Err#2
ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libxkbcommon.so.0", 0x7FFFBFFFC880) Err#2
ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libunistring.so.2", 0x7FFFBFFFD560) Err#2
ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libgcrypt.so.20", 0x7FFFBFFFDB40) Err#2
ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libz.so.1", 0x7FFFBFFFDB40) Err#2 ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libXdmcp.so.6", 0x7FFFBFFFDB40) Err#2 ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libxcb-render.so.0", 0x7FFFBFFFD560)
Err#2 ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libxcb-shm.so.0", 0x7FFFBFFFDB40) Err#2
ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libxcb-util.so.1", 0x7FFFBFFFDB40) Err#2
ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libXext.so.0", 0x7FFFBFFFDB40) Err#2 ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libXrender.so.1", 0x7FFFBFFFDB40) Err#2
ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libXfixes.so.1", 0x7FFFBFFFDB40) Err#2 ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libgobject-2.0.so.0", 0x7FFFBFFFD560)
Err#2 ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libglib-2.0.so.0", 0x7FFFBFFFD560) Err#2
ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libatk-1.0.so.0", 0x7FFFBFFFDB40) Err#2
ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libatspi.so.0", 0x7FFFBFFFDB40) Err#2 ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libdbus-1.so.3", 0x7FFFBFFFDB40) Err#2 ENOENT
/1: stat("/usr/gcc/7/lib/amd64/libdl.so.1", 0x7FFFBFFFDB40) Err#2 ENOENT
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Problem with VirtualBox since upgrade today
On 7/10/23 13:45, russell wrote: Hi Just performed a pkg refresh & pkg update -v --be-name and found that VirtualBox is broken as it does not clearly identify which 6.1 release it is and it does not see the existing virtual machines; so I rolled back to the previous BE. Kind Regards Russell ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi Russell! i observed this, too. The Version info is missing, the configured VMs are not listed, the GUI is not usable.. A local Rebuild 'as is' did publish but did not work either. On Wednesday i will try to compile it with gcc 7 to see if it makes a difference.. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] INFO: pkg update manifest hash error in package readline
On 6/1/23 22:12, Andreas Wacknitz wrote: Am 01.06.23 um 06:55 schrieb Stephan Althaus: On 5/31/23 22:22, Stephan Althaus wrote: Hello! I have an old system running OI from November 2022: # pkg refresh --full && pkg update Creating Plan (Package planning: 661/1021): / Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z expected: e6571024d64e235a1ef19fd8557d028837118fec computed: 658d78a4022ed30bef9c2f9b6b15edabeb81ef1f. (happened 4 times) # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT rpool1 444G 341G 103G - - 36% 76% 1.00x ONLINE - I will try again tomorrow, and i will try to remove some unused packages if this is related (this machine had various build bits like gcc-7, gcc-10 that are not needed anymore...) Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! pkg update doesn't work, because of the 'old' pakcage readline may have some hash error. i tried to verify this with a single package download, which throws the same error: # pkgrecv -s https://pkg.openindiana.org/hipster/ -a -d ./pkgtest pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z Retrieving packages for publisher openindiana.org ... Retrieving and evaluating 1 package(s)... pkgrecv: pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z expected: e6571024d64e235a1ef19fd8557d028837118fec computed: 658d78a4022ed30bef9c2f9b6b15edabeb81ef1f. (happened 4 times) I have tested the download on a different machine, same error. Maybe someone else can have a look at this? Does the package need a rebuild ? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss I have issued a package rebuild. This will hopefully create a correct hash. Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Yes, the hash error is gone and the package can be downloaded now. Thanks!! Regards, Stephan # pkgrecv -v -s https://pkg.openindiana.org/hipster/ -a -d ./pkgtest pkg://openindiana.org/library/readline@6.3-2023.0.0.4:20230601T195252Z Retrieving packages for publisher openindiana.org ... Retrieving and evaluating 1 package(s)... Archiving packages ... Packages to add: 1 Files to retrieve: 27 Estimated transfer size: 755.06 kB Packages to archive: library/readline@6.3,5.11-2023.0.0.4:20230601T195252Z DOWNLOAD PKGS FILES XFER (MB) SPEED Completed 1/1 27/27 0.7/0.7 105k/s ARCHIVE FILES STORE (MB) pkgtest 62/62 0.8/0.8 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] INFO: pkg update manifest hash error in package readline
On 6/1/23 08:28, Stephan Althaus wrote: On 6/1/23 08:14, Marcel Telka wrote: On Thu, Jun 01, 2023 at 06:55:50AM +0200, Stephan Althaus wrote: # pkgrecv -s https://pkg.openindiana.org/hipster/ -a -d ./pkgtest pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z Retrieving packages for publisher openindiana.org ... Retrieving and evaluating 1 package(s)... pkgrecv: pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z expected: e6571024d64e235a1ef19fd8557d028837118fec computed: 658d78a4022ed30bef9c2f9b6b15edabeb81ef1f. (happened 4 times) I have tested the download on a different machine, same error. Maybe someone else can have a look at this? Confirmed. Same error here. Hello! Thanks! The package readline is used by many packages and stuck in versions 5.2 and 6.3 - very special.. Should i create a PR with a new component revision to trigger a rebuild or what is "the right way" to achieve this? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Maybe it is a problem with pkg itself: pkg search -r libm.so.2 does not return any results on the old (nov 2022) system.. (?) Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] INFO: pkg update manifest hash error in package readline
On 6/1/23 08:14, Marcel Telka wrote: On Thu, Jun 01, 2023 at 06:55:50AM +0200, Stephan Althaus wrote: # pkgrecv -s https://pkg.openindiana.org/hipster/ -a -d ./pkgtest pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z Retrieving packages for publisher openindiana.org ... Retrieving and evaluating 1 package(s)... pkgrecv: pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z expected: e6571024d64e235a1ef19fd8557d028837118fec computed: 658d78a4022ed30bef9c2f9b6b15edabeb81ef1f. (happened 4 times) I have tested the download on a different machine, same error. Maybe someone else can have a look at this? Confirmed. Same error here. Hello! Thanks! The package readline is used by many packages and stuck in versions 5.2 and 6.3 - very special.. Should i create a PR with a new component revision to trigger a rebuild or what is "the right way" to achieve this? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] INFO: pkg update manifest hash error in package readline
On 5/31/23 22:22, Stephan Althaus wrote: Hello! I have an old system running OI from November 2022: # pkg refresh --full && pkg update Creating Plan (Package planning: 661/1021): / Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z expected: e6571024d64e235a1ef19fd8557d028837118fec computed: 658d78a4022ed30bef9c2f9b6b15edabeb81ef1f. (happened 4 times) # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT rpool1 444G 341G 103G - - 36% 76% 1.00x ONLINE - I will try again tomorrow, and i will try to remove some unused packages if this is related (this machine had various build bits like gcc-7, gcc-10 that are not needed anymore...) Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! pkg update doesn't work, because of the 'old' pakcage readline may have some hash error. i tried to verify this with a single package download, which throws the same error: # pkgrecv -s https://pkg.openindiana.org/hipster/ -a -d ./pkgtest pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z Retrieving packages for publisher openindiana.org ... Retrieving and evaluating 1 package(s)... pkgrecv: pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z expected: e6571024d64e235a1ef19fd8557d028837118fec computed: 658d78a4022ed30bef9c2f9b6b15edabeb81ef1f. (happened 4 times) I have tested the download on a different machine, same error. Maybe someone else can have a look at this? Does the package need a rebuild ? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] INFO: pkg update manifest hash error in package readline
Hello! I have an old system running OI from November 2022: # pkg refresh --full && pkg update Creating Plan (Package planning: 661/1021): / Errors were encountered while attempting to retrieve package or file data for the requested operation. Details follow: pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z Invalid content: manifest hash failure: fmri: pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z expected: e6571024d64e235a1ef19fd8557d028837118fec computed: 658d78a4022ed30bef9c2f9b6b15edabeb81ef1f. (happened 4 times) # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT rpool1 444G 341G 103G - - 36% 76% 1.00x ONLINE - I will try again tomorrow, and i will try to remove some unused packages (this machine had various build bits like gcc-7, gcc-10 that are not needed anymore...) Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Add inotify support to illumos-gate
On 5/12/23 10:30, Stephan Althaus wrote: On 5/2/23 20:25, Till Wegmüller wrote: Hi Stephan inotify has stubbed headers that work roughly decently. Any software should use FEN or the Native API. We add it to every programming language we can and should also add it to mate-system-monitor or rather make it use kstat if it tries to poll things under /proc which it should not for us. What does mate-system-monitor use inotify for? -Till ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! mate-system-monitor dumps core, because of a glib::gio dependency, because gio can't find(?) a filesystem-monitor-implementation : "g-io-error-quark: Unable to find default local file monitor type".. (see below) It would be nice if we could solve the problem before we announce the new release ISO images. How can we achieve this? i am willing to help, but, because of my lacking experience i need someone who tells me what exactly to do.. Regards, Stephan $ mate-system-monitor (:11943): glibmm-CRITICAL **: 10:27:01.361: 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 11943: mate-system-monitor - thread# 1 / lwp# 1 - 0044b0a1 _ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE () + 111 7fff73009ab0 _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 7fff73008722 _ZN3Gio11Application24local_command_line_vfuncERPPcRi () + 52 7fff7300939b _ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi () + fb 7fffac50bef3 g_application_run () + 133 004239f1 main () + 61 00422d37 _start_crt () + 87 00422c98 _start () + 18 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Sorry if i am asking something wrong here, if i don't know 'the right way' ... It would be nice to have this smartos-commit (origin 2014) upstreamed to illumos-gate: https://github.com/TritonDataCenter/illumos-joyent/commit/a9a246c0c49e192616e7499eaa2362b21fde8f5e Is someone willing to support this - at least in a somewhat 'political' manner? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] INFO: thunderbird 102.11.0 doesn't like network problems (?)
Hello! Just for the records. Today i observed thunderbird being unresponsible and the cause for garbage on the screen, using 1 cpu whith 100%, whilst my home mail server was not responding. I would have expected that one network thread in the background in waiting state, but not these symptoms. Starting thunderbird from the console i got these last lines of output: Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=0.480759) [GFX1-]: glxtest: libpci missing Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=0.480759) |[1][GFX1-]: glxtest: libEGL missing eglGetDisplayDriverName (t=0.480808) [GFX1-]: glxtest: libEGL missing eglGetDisplayDriverName Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=0.480759) |[1][GFX1-]: glxtest: libEGL missing eglGetDisplayDriverName (t=0.480808) |[2][GFX1-]: glxtest: libEGL missing eglGetDisplayDriverName (t=0.48082) [GFX1-]: glxtest: libEGL missing eglGetDisplayDriverName [Parent 2895, Main Thread] WARNING: Failed to connect to proxy: 'glib warning', file /jenkins/jobs/oi-userland/workspace/components/mail/thunderbird/thunderbird-102.11.0/toolkit/xre/nsSigHandlers.cpp:167 (thunderbird-default:2895): libnotify-WARNING **: 07:52:23.705: Failed to connect to proxy Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Problems with gcc-7 and gcc-10 built binaries
On 5/21/23 22:35, russell wrote: Hi Back in October 2022, when I was experiencing issues building libfilezilla in response to my posting Till pointed out that gcc-7 and gcc-10 have an ABI break. 7/10/22 18:22, Till Wegmueller wrote: Hi Russel Thats an ABI break. Looks like Gcc7 and Gcc10 produce different output. You will have to compile all with the same compiler. -Till So, are there plans to switch to using gcc-10 for the entire build of OpenIndiana to eliminate the ABI compatibility issue of mixing gcc-7 and gcc-10? Kind Regards Russell ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In oi-userland/make-rules/shared-macros.mk:GCC_VERSION = 10 is set, so the default compiler is 10. The pkg binaries may be a little behind, as the packages must be rebuild on the build server since that setting changed. But i think there is a good chance that the packages are already build with gcc-10, you just have to update your system with "pkg update". Regards, Stephan P.S. you could use 'ldd' to examine the linkage of a binary, be sure that there is no gcc/7 path in the libs used, and the libs used by the libs ... :-) $ ldd `which firefox` libpthread.so.1 => /lib/64/libpthread.so.1 libsocket.so.1 => /lib/64/libsocket.so.1 libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 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
Re: [OpenIndiana-discuss] pkg folder size escalated
On 5/18/23 10:15, Stephan Althaus wrote: On 5/18/23 09:08, Toomas Soome via openindiana-discuss wrote: pkg property | grep flush-content-cache-on-success Thank you very much for the hint, Toomas !!! :-) ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] pkg folder size escalated
On 5/18/23 09:51, Goetz T. Fischer wrote: it was set to False and i set it to True, did a "pkg refresh" and then it got even bigger. so i uninstalled something to see what happens and after that it lost around 35% in size. still more than 3 times the size of the pkg folder in solaris 11.4. On Thu, 18 May 2023 09:10:22 +0200, Stephan Althaus wrote: On 5/18/23 09:08, Toomas Soome via openindiana-discuss wrote: pkg property $ pkg property|grep fl flush-content-cache-on-success False ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss after setting pkg set-propoerty flush-content-cache-on-success True and pkg update i now have 2.33G. That may be normal for >1500 packages: $ pkg list | wc 1572 4742 127355 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] pkg folder size escalated
On 5/18/23 09:08, Toomas Soome via openindiana-discuss wrote: pkg property $ pkg property|grep fl flush-content-cache-on-success False ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] pkg folder size escalated
On 5/18/23 07:22, Goetz T. Fischer wrote: hello everyone, after a fresh indiana installation and removing a couple of packages my /var/pkg folder is more than 700mb! doing comparable things with solaris 11.4 leaves me with a /var/pkg size of less than 200. how can i clean that up safely and how can i keep it from escalating again in the future? thanks in advance for any help -- R-A-C Götz T. Fischer CertIT&Comp +49(0)7225/98 98 79 g.fisc...@r-a-c.de r-a-c.de ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Uuh, my laptop has 35.2G in /var/pkg, my tiny server has 23.5G. Both are installations from ~5(?) years ago.. Yes, it would be nice if that is (automatically) cleaned up after a pkg update. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Cups problems
On 5/16/23 18:45, Udo Grabowski (IMK) wrote: On 16/05/2023 18:37, Udo Grabowski (IMK) wrote: I've found a few problems with cups 1) it wants system/volatile/cups, but /system/volatile doesn't exist. Works if created manually and restart cups/in-lpd and /scheduler. Either system/volatile should be created somehow after boot before cups starts, or cups should be patched to put that into /var/run/cups; but... 2) ... it wants /var/run/cups/, but that doesn't exist. Should be created when it installs. 3) It complains about a missing ColorManager: "The name org.freedesktop.ColorManager was not provided by any .service files" which relates to a missing gnome-colord manager (because it's mate here...), so it can't read icc-Profiles for the printer. Don't know if that affects color-printing somehow. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss 4) it opens network connections like hell (on a simple client): ro sunts ~ # netstat -afinet | grep \.ipp | wc -l 105 don't see any messages in regard to this problem, neither in messages, syslog, cups/access_log or error_log ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! I dont't see this problem here: $ netstat -afinet | grep \.ipp | wc -l 2 $ svcs -a|grep cup legacy_run 9:40:33 lrc:/etc/rc3_d/S99cups-browsed online 9:40:19 svc:/application/cups/scheduler:default online 9:51:42 svc:/application/cups/in-lpd:default $ pkg list|grep cups library/desktop/gtk2/gtk-backend-cups 2.24.32-2023.0.0.5 i-- library/desktop/gtk3/gtk-backend-cups 3.24.34-2023.0.0.2 i-- library/print/cups-libs 2.4.2-2023.0.0.2 i-- library/python/pycups-39 2.0.1-2023.0.0.0 i-- print/cups 2.4.2-2023.0.0.2 i-- print/cups-filters 1.28.17-2023.0.0.1 i-- print/cups/system-config-printer 2.30.0-2023.0.0.7 i-- $ uname -a SunOS dell7720 5.11 illumos-864a8d6953 i86pc i386 i86pc I did a pkg update a few minutes ago.. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Add inotify support to illumos-gate
On 5/2/23 20:25, Till Wegmüller wrote: Hi Stephan inotify has stubbed headers that work roughly decently. Any software should use FEN or the Native API. We add it to every programming language we can and should also add it to mate-system-monitor or rather make it use kstat if it tries to poll things under /proc which it should not for us. What does mate-system-monitor use inotify for? -Till ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! mate-system-monitor dumps core, because of a glib::gio dependency, because gio can't find(?) a filesystem-monitor-implementation : "g-io-error-quark: Unable to find default local file monitor type".. (see below) It would be nice if we could solve the problem before we announce the new release ISO images. How can we achieve this? i am willing to help, but, because of my lacking experience i need someone who tells me what exactly to do.. Regards, Stephan $ mate-system-monitor (:11943): glibmm-CRITICAL **: 10:27:01.361: 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 11943: mate-system-monitor - thread# 1 / lwp# 1 - 0044b0a1 _ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE () + 111 7fff73009ab0 _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 7fff73008722 _ZN3Gio11Application24local_command_line_vfuncERPPcRi () + 52 7fff7300939b _ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi () + fb 7fffac50bef3 g_application_run () + 133 004239f1 main () + 61 00422d37 _start_crt () + 87 00422c98 _start () + 18 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Rebuild needed for wxwidgets-3 - consumers
On 5/10/23 22:23, Stephan Althaus wrote: On 5/10/23 18:24, Andreas Wacknitz wrote: Am 10.05.23 um 13:34 schrieb Stephan Althaus: Hello! i just found that codeblocks does not work anymore. Maybe a rebuild is needed because of the update of wxwidgets-3 Alas this is not so easy. Actually codeblocks doesn't compile with the latest wxwidgets-3. The project hasn't published a new release for three years. So from here it looks dead and we need to either find patches to make it work with wxwidgets-3 or need to obsolete it. Andreas Hello! Hm. I would vote for something that is actively developed, codelite and vscode come into mind. On an quick look at them, codelite needs libssh and cmocka..., vscode needs yarn from nodejs ... i don't know, maybe vim/emacs with code completion support would be an interesting alternative.. Ah i see debian-testing uses Version 20.03, svn @13046 : svn checkout svn://svn.code.sf.net/p/codeblocks/code/trunk@13046 From the forum: « on: May 06, 2023, 06:29:40 pm » The 06 May 2023 build (13268) is out. We switched to wx 3.2.2.1 (on 05 may 2023) Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml A new release is planned "after the summer holidays" Yes, @13046 compiles/builds and runs on my system: ( svn build rev 13046 (2022-11-17 12:54:17) gcc 10.4.0 Linux/unicode - 64 bit ) I will try @13268 tomorrow... Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! I am on the way to create a PR.. Build is ok up to now, pkg-mogrify-error has been solved, the sample-manifest has changed... Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI without a console?
On 5/10/23 22:42, Gary Mills wrote: On Mon, May 08, 2023 at 10:31:09AM -0500, Gary Mills wrote: Is anybody running OI on a computer that does not have a console? I have a system that I installed with the GUI image, and with an HDMI console and USB keyboard and mouse. Now I'd like to use this system without all of them. I have another question. Will it help to have OI boot without the X11 screen? How do I accomplish that? The text screen will be adequate for most of what I need to do. Hello! Don't know if it will help (i would not believe so). Disable the X11 login screen and you're done: # svcadm disable lightdm Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Rebuild needed for wxwidgets-3 - consumers
On 5/10/23 18:24, Andreas Wacknitz wrote: Am 10.05.23 um 13:34 schrieb Stephan Althaus: Hello! i just found that codeblocks does not work anymore. Maybe a rebuild is needed because of the update of wxwidgets-3 Alas this is not so easy. Actually codeblocks doesn't compile with the latest wxwidgets-3. The project hasn't published a new release for three years. So from here it looks dead and we need to either find patches to make it work with wxwidgets-3 or need to obsolete it. Andreas Hello! Hm. I would vote for something that is actively developed, codelite and vscode come into mind. On an quick look at them, codelite needs libssh and cmocka..., vscode needs yarn from nodejs ... i don't know, maybe vim/emacs with code completion support would be an interesting alternative.. Ah i see debian-testing uses Version 20.03, svn @13046 : svn checkout svn://svn.code.sf.net/p/codeblocks/code/trunk@13046 From the forum: « on: May 06, 2023, 06:29:40 pm » The 06 May 2023 build (13268) is out. We switched to wx 3.2.2.1 (on 05 may 2023) Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml A new release is planned "after the summer holidays" Yes, @13046 compiles/builds and runs on my system: ( svn build rev 13046 (2022-11-17 12:54:17) gcc 10.4.0 Linux/unicode - 64 bit ) I will try @13268 tomorrow... Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Rebuild needed for wxwidgets-3 - consumers
Hello! i just found that codeblocks does not work anymore. Maybe a rebuild is needed because of the update of wxwidgets-3 $ codeblocks filelist2.cpp ld.so.1: codeblocks: fatal: libwx_gtk3u_aui-3.1.so.5: open failed: No such file or directory ld.so.1: codeblocks: fatal: relocation error: file /usr/bin/codeblocks: symbol wxEVT_AUINOTEBOOK_PAGE_CLOSE: referenced symbol not found Killed $ pkg search libwx_gtk3u_aui* INDEX ACTION VALUE PACKAGE basename link usr/lib/amd64/libwx_gtk3u_aui-3.2.so pkg:/library/graphics/wxwidgets-3@3.2.2.1-2023.0.0.0 basename file usr/lib/amd64/libwx_gtk3u_aui-3.2.so.0 pkg:/library/graphics/wxwidgets-3@3.2.2.1-2023.0.0.0 Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Fwd: Add inotify support to illumos-gate
On 5/9/23 10:19, Udo Grabowski (IMK) wrote:
On 09/05/2023 07:41, Stephan Althaus wrote:
On 5/8/23 16:10, Udo Grabowski (IMK) wrote:
On 08/05/2023 11:13, Udo Grabowski (IMK) wrote:
On 05/05/2023 09:14, Stephan Althaus wrote:
Hello!
The hint to use inotify support in glib was from you, can you
please shed a
light on this?
I am lacking all sorts of background on this stuff :-{
To test this, we would have to patch and build inotify support in
illumos-gate,
install it, then compile glib2 with a check if inotify was found
and install,
and then mate-system-monitor... to see if this approach does
indeed help.. Is
there some easier way?
Regards,
Stephan
Forwarded Message
Subject: Re: [OpenIndiana-discuss] Add inotify support to
illumos-gate
Date: Tue, 2 May 2023 20:25:49 +0200
From: Till Wegmüller
Reply-To: Discussion list for OpenIndiana
To: openindiana-discuss@openindiana.org
Hi Stephan
inotify has stubbed headers that work roughly decently. Any
software should use
FEN or the Native API. We add it to every programming language we
can and should
also add it to mate-system-monitor or rather make it use kstat if
it tries to
poll things under /proc which it should not for us.
What does mate-system-monitor use inotify for?
...
The parts that use Gio for monitoring in mate-system-monitor are
located
in prettytable.cpp, where it monitors its apps-cache, and in
procman-app.cpp,
where it monitors mounts and somehow uses it to process a
commandline; that's
also the place it crashes (after complaining about the missing monitor
facility):
...
And still, even with LD_LIBRARY_PATH set to gcc 10, libgtkmm-3 again
loads itself libstdc++.so.6 from gcc 7 AND 10, as well as libgcc_s.so.1
from gcc 7 AND 10.
And the same problem for libgdkmm-3, and libpangomm-1.4. Probably
because
software that is still compiled with gcc 7 depends on them.
This mixup should be cleared first.
All libraries loaded from mate-system-monitor that depend on gcc:
/usr/lib/64/libgtkmm-3.0.so.1 ###
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
/usr/lib/64/libgdkmm-3.0.so.1 ###
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
/usr/lib/64/libxml2.so.2 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/librsvg-2.so.2 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libgiomm-2.4.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
/usr/lib/64/libglibmm-2.4.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
/usr/lib/64/libsigc-2.0.so.0 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/gcc/10/lib/amd64/libstdc++.so.6 ###
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libatkmm-1.6.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
/usr/lib/64/libpangomm-1.4.so.1 ###
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
/usr/lib/64/libcairomm-1.0.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
/usr/lib/64/libicuuc.so.68 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libcroco-0.6.so.3 ###
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
Re: [OpenIndiana-discuss] Fwd: Add inotify support to illumos-gate
On 5/9/23 10:16, Udo Grabowski (IMK) wrote: On 08/05/2023 20:59, Andreas Wacknitz wrote: Am 08.05.23 um 16:10 schrieb Udo Grabowski (IMK): On 08/05/2023 11:13, Udo Grabowski (IMK) wrote: ,,, And still, even with LD_LIBRARY_PATH set to gcc 10, libgtkmm-3 again loads itself libstdc++.so.6 from gcc 7 AND 10, as well as libgcc_s.so.1 from gcc 7 AND 10. And the same problem for libgdkmm-3, and libpangomm-1.4. Probably because software that is still compiled with gcc 7 depends on them. This mixup should be cleared first. All libraries loaded from mate-system-monitor that depend on gcc: /usr/lib/64/libgtkmm-3.0.so.1 ### 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 >> /usr/lib/64/libgdkmm-3.0.so.1 ### 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 ... /usr/lib/64/libpangomm-1.4.so.1 ### 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 I have upgraded pangomm and rebuilt its dependend packages gtkmm, gtkmm3 and gparted. So all are using the correct libraries now. libgdkmm-3.0 is also in the list and should be corrected as well. Unfortunately, my Dell T3500 (where I installed the rolling Hipster) doesn't boot anymore after update from today (serial 21623) and I'm unfortunately in HOME-Office...), so I can't check anything today. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello Udo! Sorry to hear that your system is not responding. I am on 21620 from yesterday evening (europe) that is ok. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Fwd: Add inotify support to illumos-gate
On 5/8/23 16:10, Udo Grabowski (IMK) wrote:
On 08/05/2023 11:13, Udo Grabowski (IMK) wrote:
On 05/05/2023 09:14, Stephan Althaus wrote:
Hello!
The hint to use inotify support in glib was from you, can you please
shed a
light on this?
I am lacking all sorts of background on this stuff :-{
To test this, we would have to patch and build inotify support in
illumos-gate,
install it, then compile glib2 with a check if inotify was found and
install,
and then mate-system-monitor... to see if this approach does indeed
help.. Is
there some easier way?
Regards,
Stephan
Forwarded Message
Subject: Re: [OpenIndiana-discuss] Add inotify support to
illumos-gate
Date: Tue, 2 May 2023 20:25:49 +0200
From: Till Wegmüller
Reply-To: Discussion list for OpenIndiana
To: openindiana-discuss@openindiana.org
Hi Stephan
inotify has stubbed headers that work roughly decently. Any software
should use
FEN or the Native API. We add it to every programming language we
can and should
also add it to mate-system-monitor or rather make it use kstat if it
tries to
poll things under /proc which it should not for us.
What does mate-system-monitor use inotify for?
...
The parts that use Gio for monitoring in mate-system-monitor are located
in prettytable.cpp, where it monitors its apps-cache, and in
procman-app.cpp,
where it monitors mounts and somehow uses it to process a
commandline; that's
also the place it crashes (after complaining about the missing monitor
facility):
...
And still, even with LD_LIBRARY_PATH set to gcc 10, libgtkmm-3 again
loads itself libstdc++.so.6 from gcc 7 AND 10, as well as libgcc_s.so.1
from gcc 7 AND 10.
And the same problem for libgdkmm-3, and libpangomm-1.4. Probably because
software that is still compiled with gcc 7 depends on them.
This mixup should be cleared first.
All libraries loaded from mate-system-monitor that depend on gcc:
/usr/lib/64/libgtkmm-3.0.so.1 ###
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
/usr/lib/64/libgdkmm-3.0.so.1 ###
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
/usr/lib/64/libxml2.so.2 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/librsvg-2.so.2 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libgiomm-2.4.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
/usr/lib/64/libglibmm-2.4.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
/usr/lib/64/libsigc-2.0.so.0 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/gcc/10/lib/amd64/libstdc++.so.6 ###
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libatkmm-1.6.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
/usr/lib/64/libpangomm-1.4.so.1 ###
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
/usr/lib/64/libcairomm-1.0.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
/usr/lib/64/libicuuc.so.68 ###
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
/usr/lib/64/libcroco-0.6.so.3 ###
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!
The linkage seems to be clean now:
$ ldd `which mate-system-monitor` |grep 7
$ ldd `
Re: [OpenIndiana-discuss] OI without a console?
On 5/9/23 03:32, Gary Mills wrote: On Mon, May 08, 2023 at 05:37:00PM +0200, Stephan Althaus wrote: As I can tell from history, you should set the BIOS to ignore these errors on boot like "no keyboard attached". Try this with only the monitor attached, no keyboard/mouse.. That's good to know. I have a duplicate system on order. I can use that to experiment on. I have a Backup server without keyboard/mouse/monitor attached that i power up from remote via IPMI, that boots into OI just perfextly. How do you use IPMI? I've only used it with systems that have video emulator hardware installed, with a dedicated ethernet port. Hello! Yes, it is a server with IPMI dedicated ethernet port, (capable of html5 console redirection) >10 years old now. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI without a console?
On 5/8/23 17:31, Gary Mills wrote: Is anybody running OI on a computer that does not have a console? I have a system that I installed with the GUI image, and with an HDMI console and USB keyboard and mouse. Now I'd like to use this system without all of them. Can I just disconnect them? Will OI boot fully without a console? Can I attach a console later, if I happen to need it? Hello! As I can tell from history, you should set the BIOS to ignore these errors on boot like "no keyboard attached". Try this with only the monitor attached, no keyboard/mouse.. I have a Backup server without keyboard/mouse/monitor attached that i power up from remote via IPMI, that boots into OI just perfextly. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] gthumb libraw.so.20
On 5/7/23 19:47, Andreas Wacknitz wrote: Am 07.05.23 um 17:56 schrieb Stephan Althaus: On 4/12/23 09:32, Stephan Althaus wrote: Hello! On my BE of 2023-03-31 i have a failing link to LIBRAW on gthumb. Maybe the package has to be triggered to be rebuild on the build server? Regards, Stephan $ gthumb _DS33737.ARW ld.so.1: gthumb: fatal: libraw.so.20: open failed: No such file or directory ld.so.1: gthumb: fatal: relocation error: file /usr/lib/amd64/gthumb/extensions/libraw_files.so: symbol libraw_init: referenced symbol not found Killed $ pkg search libraw.so.20 $ pkg search libraw.so INDEX ACTION VALUE PACKAGE basename link usr/lib/libraw.so pkg:/image/library/libraw@0.21.1-2023.0.0.0 basename link usr/lib/amd64/libraw.so pkg:/image/library/libraw@0.21.1-2023.0.0.0 $ ls -l /usr/lib/libraw* lrwxrwxrwx 1 root root 18 Mar 20 21:57 /usr/lib/libraw_r.so -> libraw_r.so.23.0.0 lrwxrwxrwx 1 root root 18 Mar 20 21:56 /usr/lib/libraw_r.so.23 -> libraw_r.so.23.0.0 -r-xr-xr-x 1 root bin 1.28M Mar 20 21:56 /usr/lib/libraw_r.so.23.0.0 lrwxrwxrwx 1 root root 16 Mar 20 21:57 /usr/lib/libraw.so -> libraw.so.23.0.0 lrwxrwxrwx 1 root root 16 Mar 20 21:56 /usr/lib/libraw.so.23 -> libraw.so.23.0.0 -r-xr-xr-x 1 root bin 1.28M Mar 20 21:56 /usr/lib/libraw.so.23.0.0 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Something like ln -s libraw.so.23.0.0 libraw.so.20 does help, maybe this can easily be added in the gthumb package ? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss I fear that this might lead to strange errors because the library has a new .so version which typically indicates incompatible changes. Furthermore, it was needed to add some patches in order to build gthumb with the newer libraw. I have created a PR for it and it builds now. I hope that I was right in my believe that the missing attributes can be patched out without negative impacts on gthumb. Regards Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello Andreas! Thanks for your efforts! gthumb shows the raw picutres now as expected, but not in the the small file preview list "thumbnails". (which works with folders with jpgs for example) i believe that this is to be considered 'minor' and the solution may be postponed.. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] gthumb libraw.so.20
On 4/12/23 09:32, Stephan Althaus wrote: Hello! On my BE of 2023-03-31 i have a failing link to LIBRAW on gthumb. Maybe the package has to be triggered to be rebuild on the build server? Regards, Stephan $ gthumb _DS33737.ARW ld.so.1: gthumb: fatal: libraw.so.20: open failed: No such file or directory ld.so.1: gthumb: fatal: relocation error: file /usr/lib/amd64/gthumb/extensions/libraw_files.so: symbol libraw_init: referenced symbol not found Killed $ pkg search libraw.so.20 $ pkg search libraw.so INDEX ACTION VALUE PACKAGE basename link usr/lib/libraw.so pkg:/image/library/libraw@0.21.1-2023.0.0.0 basename link usr/lib/amd64/libraw.so pkg:/image/library/libraw@0.21.1-2023.0.0.0 $ ls -l /usr/lib/libraw* lrwxrwxrwx 1 root root 18 Mar 20 21:57 /usr/lib/libraw_r.so -> libraw_r.so.23.0.0 lrwxrwxrwx 1 root root 18 Mar 20 21:56 /usr/lib/libraw_r.so.23 -> libraw_r.so.23.0.0 -r-xr-xr-x 1 root bin 1.28M Mar 20 21:56 /usr/lib/libraw_r.so.23.0.0 lrwxrwxrwx 1 root root 16 Mar 20 21:57 /usr/lib/libraw.so -> libraw.so.23.0.0 lrwxrwxrwx 1 root root 16 Mar 20 21:56 /usr/lib/libraw.so.23 -> libraw.so.23.0.0 -r-xr-xr-x 1 root bin 1.28M Mar 20 21:56 /usr/lib/libraw.so.23.0.0 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Something like ln -s libraw.so.23.0.0 libraw.so.20 does help, maybe this can easily be added in the gthumb package ? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] zoom on openindiana
On 5/5/23 10:51, Marc Lobelle wrote: Hello, One of the few times I have to start a computer in Windows is to run ZOOM for video conferences. Is there a way to use ZOOM on Openindiana ? Thanks Marc ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! I tried the firefox extension "useragent switcher" to prepend i am on linux, but that didn't help for http://zoom.us/join Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Add inotify support to illumos-gate
Hello! As a search result from this morning, glib misses inotify/fam support, which is a reason for mate-system-monitor to dump core. FAM seems to be too old, but inotify-support is not in illumos-gate, but Smartos has support for it. Which is the "right" way to include inotify support in OI ? a) Should we hopefully ask some smartos-developer to upstream this? b) As a patch (-set) within oi-userland to illumos-gate ? c) ?? A small search in the smart-os tree gives this: $ find . -iname "*inotify*" ./illumos-joyent/usr/src/lib/libc/port/sys/inotify.c ./illumos-joyent/usr/src/test/zfs-tests/tests/functional/cli_root/zfs_mount/zfs_mount_watched_inotify.ksh ./illumos-joyent/usr/src/man/man3c/inotify_rm_watch.3c ./illumos-joyent/usr/src/man/man3c/inotify_init.3c ./illumos-joyent/usr/src/man/man3c/inotify_add_watch.3c ./illumos-joyent/usr/src/man/man7/inotify.7 ./illumos-joyent/usr/src/uts/sparc/inotify ./illumos-joyent/usr/src/uts/intel/inotify ./illumos-joyent/usr/src/uts/common/io/inotify.c ./illumos-joyent/usr/src/uts/common/io/inotify.conf ./illumos-joyent/usr/src/uts/common/sys/inotify.h Regards, Stephan Althaus ___ 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
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 ? <https://src.fedoraproject.org/rpms/glib2/blob/rawhide/f/glib2.spec> ... # Remove gamin dependency Obsoletes: glib2-fam < 2.67.1-3 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openin
Re: [OpenIndiana-discuss] mate system monitor does not work any, more on recent versions of openindiana
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 ? <https://src.fedoraproject.org/rpms/glib2/blob/rawhide/f/glib2.spec> ... # Remove gamin dependency Obsoletes: glib2-fam < 2.67.1-3 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discus
Re: [OpenIndiana-discuss] mate system monitor does not work any, more on recent versions of openindiana
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
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
[OpenIndiana-discuss] gthumb libraw.so.20
Hello! On my BE of 2023-03-31 i have a failing link to LIBRAW on gthumb. Maybe the package has to be triggered to be rebuild on the build server? Regards, Stephan $ gthumb _DS33737.ARW ld.so.1: gthumb: fatal: libraw.so.20: open failed: No such file or directory ld.so.1: gthumb: fatal: relocation error: file /usr/lib/amd64/gthumb/extensions/libraw_files.so: symbol libraw_init: referenced symbol not found Killed $ pkg search libraw.so.20 $ pkg search libraw.so INDEX ACTION VALUE PACKAGE basename link usr/lib/libraw.so pkg:/image/library/libraw@0.21.1-2023.0.0.0 basename link usr/lib/amd64/libraw.so pkg:/image/library/libraw@0.21.1-2023.0.0.0 $ ls -l /usr/lib/libraw* lrwxrwxrwx 1 root root 18 Mar 20 21:57 /usr/lib/libraw_r.so -> libraw_r.so.23.0.0 lrwxrwxrwx 1 root root 18 Mar 20 21:56 /usr/lib/libraw_r.so.23 -> libraw_r.so.23.0.0 -r-xr-xr-x 1 root bin 1.28M Mar 20 21:56 /usr/lib/libraw_r.so.23.0.0 lrwxrwxrwx 1 root root 16 Mar 20 21:57 /usr/lib/libraw.so -> libraw.so.23.0.0 lrwxrwxrwx 1 root root 16 Mar 20 21:56 /usr/lib/libraw.so.23 -> libraw.so.23.0.0 -r-xr-xr-x 1 root bin 1.28M Mar 20 21:56 /usr/lib/libraw.so.23.0.0 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI hipster upgrade - Firefox broken unable to play some youtube videos
On 3/26/23 20:18, russell wrote: Hi Performed an OI Hipster update this morning, so now running illumos-b3385a702f and Firefox 111.0.1 but found that I started having issues with Youtube and videos that played fine yesterday do not play today. Instead of the video I get Firefox "Your browser can't play this video", I am also getting a message "To play video, you may need to install the required video codecs" at the top of the web page. Is any one else experiencing this issue? As I precaution will be reverting to my previous BE. TIA Russell ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello Russell! I have updated on 20th and have no issues related to firefox 111.0 Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 3/24/23 09:50, Udo Grabowski (IMK) wrote: On 24/03/2023 09:43, Marc Lobelle wrote: On 3/24/23 08:16, Toomas Soome via openindiana-discuss wrote: On 24. Mar 2023, at 07:58, Stephan Althaus wrote: On 3/22/23 20:56, Richard Lowe wrote: The challenge of answering that is you often don't know the answer until you see it The ::stacks command will give you asummarized view of every kernel thread's stack the ::cpuinfo -v command will show you what the CPUs are doing now (or were doing, before you got into kmdb). Both or either might have a smoking gun of some kind, but it's hard to predict what it might look like. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In one of my earlier update-tests i had a problem with the first OI-nvidia-525 version in cooperation with Virtualbox, so i had the idea to test this: I uninstalled 'userland-incorporation' and 'entire' as prerequisite to install nvidia version 515, now it boots! So, nvidia in the most recent version 525 stopped the boot process. (?) i checked with NVidia Solaris Driver Archive that my chipset (Quadro M1200) is on the supported list for this version: https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/ How/Why should the display driver be able to interrupt the boot process ? How/Why should the display driver be able to interrupt the boot process without further notice? That is something one can work out with debugger. But, this is binary only driver? Built *for Oracle Solaris 11.4*? With API interfaces changed inside Oracle Solaris? This means, the question is not “if” but “when” - it is only question of time when such drivers become unusable for us. Without gfx driver development, the desktop variant of illumos is dead end. without desktop, it would unfortunately mean the dead of illumos. If Oracle solaris drivers become unusable shouldn't illumos move to another driver interface that is maintained ? Maybe we wait until the cause for the problem is known before declaring everything dead ? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Maybe it's only because i use legacy boot or some Dell bios specific special case... ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 3/22/23 20:56, Richard Lowe wrote: The challenge of answering that is you often don't know the answer until you see it The ::stacks command will give you asummarized view of every kernel thread's stack the ::cpuinfo -v command will show you what the CPUs are doing now (or were doing, before you got into kmdb). Both or either might have a smoking gun of some kind, but it's hard to predict what it might look like. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In one of my earlier update-tests i had a problem with the first OI-nvidia-525 version in cooperation with Virtualbox, so i had the idea to test this: I uninstalled 'userland-incorporation' and 'entire' as prerequisite to install nvidia version 515, now it boots! So, nvidia in the most recent version 525 stopped the boot process. (?) i checked with NVidia Solaris Driver Archive that my chipset (Quadro M1200) is on the supported list for this version: https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/ How/Why should the display driver be able to interrupt the boot process ? How/Why should the display driver be able to interrupt the boot process without further notice? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 3/22/23 10:42, Udo Grabowski (IMK) wrote: On 21/03/2023 23:09, Stephan Althaus wrote: On 3/21/23 20:53, Richard Lowe wrote: A good thing to do is to get into mdb when it's hung, and see where we are with the ::stacks command. https://illumos.org/books/dev/debugging.html has other tips. I would add if you set the 1 bit of `moddebug` when you're in kmdb (I think moddebug/W 8001 is verbose and stop on _init, but I tend to forget), we will stop whenever a module `_init` is called, which can be a good trick to try to narrow down where things might have gone wrong if we don't respond to any means to get into kmdb. More manually, an illumos version which works and one which doesn't work will narrow down which illumos changes might have caused problems. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Thanks for your input. I tried the kmdb switched on on boot, with ::cont i have the same situation that i can't escape the running process to get the ::stack Comparing the boot messages of the working BE and the not-working one, it stops between these two pseudo-devices: Mar 21 22:19:56 dell7720 pseudo: [ID 129642 kern.notice] pseudo-device: signalfd0 *Mar 21 22:19:56 dell7720 genunix: [ID 936769 kern.notice] signalfd0 is /pseudo/signalfd@0* Mar 21 22:19:56 dell7720 pseudo: [ID 129642 kern.notice] pseudo-device: timerfd0 Mar 21 22:19:56 dell7720 genunix: [ID 936769 kern.notice] timerfd0 is /pseudo/timerfd@0 The line with "*signalfd0 is /pseudo/signalfd@0*" is the last output, then nothing more happens. You can pin that down to timerfd if you just mount the new BE and move away /usr/kernel/drv/amd64/timerfd and see if it then boots. Consult 'man timerfd' to convince yourself that that driver is irrelevant to illumos... ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! I followed your hint and removed timerfd, and uninstalled smartmontools in the new BE but no change. I looked around a bit more with the help of ::dcmds and found all sort of drivers, threads, tasks, it seems that rpool/ is mounted, (how can i verify?) almost everything i think of is there (sort of) - and no word of errors.. I just can't find a reason why it is not "going on everything looks fine..." Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 3/21/23 20:53, Richard Lowe wrote: A good thing to do is to get into mdb when it's hung, and see where we are with the ::stacks command. https://illumos.org/books/dev/debugging.html has other tips. I would add if you set the 1 bit of `moddebug` when you're in kmdb (I think moddebug/W 8001 is verbose and stop on _init, but I tend to forget), we will stop whenever a module `_init` is called, which can be a good trick to try to narrow down where things might have gone wrong if we don't respond to any means to get into kmdb. More manually, an illumos version which works and one which doesn't work will narrow down which illumos changes might have caused problems. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Thanks for your input. I tried the kmdb switched on on boot, with ::cont i have the same situation that i can't escape the running process to get the ::stack Comparing the boot messages of the working BE and the not-working one, it stops between these two pseudo-devices: Mar 21 22:19:56 dell7720 pseudo: [ID 129642 kern.notice] pseudo-device: signalfd0 *Mar 21 22:19:56 dell7720 genunix: [ID 936769 kern.notice] signalfd0 is /pseudo/signalfd@0* Mar 21 22:19:56 dell7720 pseudo: [ID 129642 kern.notice] pseudo-device: timerfd0 Mar 21 22:19:56 dell7720 genunix: [ID 936769 kern.notice] timerfd0 is /pseudo/timerfd@0 The line with "*signalfd0 is /pseudo/signalfd@0*" is the last output, then nothing more happens. Now i was able to enable kmdb. i found processes, stacks related to my USB keyboard, apix_no_interrupt,.. would be nice if i knew what to search for :-) how to find and select the right thread and then get the stack?? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 3/21/23 14:23, Udo Grabowski (IMK) wrote: On 20/03/2023 21:45, Stephan Althaus wrote: Hello! On 18.03.2023 i made a pkg update, after that the Boot hangs after configuring devices (last notice is of pseudo devices with boot option 'verbose') Nothing happens on the prompt... "beadm mount..." shows no fresh logfiles, so no info there, i should use some debug options but i am not familiar to that :-/ Any hints ? Didn't have such a failure after updating and booting today, but didn't reboot since 14.3. So I would recommend to revert to the previous BE and update that again. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello Udo! I did that yesterday, no change. i have in mind there was a relatively change in device numbering when building the device tree.. To summarize, the working BE is of 2022:11:23, the newly created by 'pkg update' won't work and stops after "configuring devices". Any things i could do to debug? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
Hello! On 18.03.2023 i made a pkg update, after that the Boot hangs after configuring devices (last notice is of pseudo devices with boot option 'verbose') Nothing happens on the prompt... "beadm mount..." shows no fresh logfiles, so no info there, i should use some debug options but i am not familiar to that :-/ Any hints ? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Can I downgrade?
On 3/16/23 16:58, s...@pandora.be wrote:
Something that worked for me was specifying a specific version.
https://www.illumos.org/issues/14648
pkg install pkg://hipster-encumbered/media/vlc@2.2.8-2018.0.0.2
So although I am not sure about your question in general ("can I downgrade in IPS
?"),
I think the answer is "yes a downgrade can be done in IPS, BUT it depends".
First of all you can reboot in an old BE (boot environment) if you have kept an
old BE (beadm).
An IPS downgrade also depends on the contents of the repositories, dependencies
of the packages etc.
Also sometimes you have constraints like "locks" which I have documented for
Squeak
http://docs.openindiana.org/handbook/community/squeak/index.html
pkg change-facet facet.version-lock.*
which is perhaps not applicable to VLC but it is to Squeak or some other IPS
packages.
So in the end the question "is it possible to downgrade in IPS" has no easy
answer, I think.
Basically I think the situation for media/vlc is not so bad, because 2.2.8 is
still in the repo,
and the latest versions are in the repo as well.
Also the package : ffmpeg can be used as an alternative to VLC.
Regards,
David Stes
- Op 13 mar 2023 om 21:06 schreef Matthew Yapit irixu...@gmx.com:
As of recently, the following doesn't work as intended:
Trash doesn't show trashed items, one must delete files from
~/.local/share/Trash/files.
mate-system-monitor cores on startup.
VLC 3.0.18 doesn't playback some videos correctly, some have out of sync
sound, some have strangulated sound.
With VLC, these defects are also found in Android VLC 3.5.4, I was able
to downgrade VLC in android and get a working video player.
I am aware of 'pkg update's ability to downgrade. Does anyone have a
recipe for down grading these programs? At least with VLC?
--Matthew
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Hello!
If you want that one package is left not-updated by "pkg update",
you could freeze the current installed version with "pkg freeze ..."
See man page..
Regards,
Stephan
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] mate-system-monitor crashes
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 ... (: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 - 7fffaeb69d0b g_type_check_instance_cast () + 1b 0044977a _ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE () + 11a 7fff6e3c09b9 _ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine () + 149 7fffae841496 _g_cclosure_marshal_INT__OBJECTv () + 76 7fffaeb3af95 _g_closure_invoke_va () + 185 7fffaeb5af6d g_signal_emit_valist () + 39d 7fffaeb5c05d g_signal_emit () + 7d 7fffae8a032a g_application_call_command_line () + 7a 7fffae8a26b1 g_application_real_local_command_line () + 241 7fff6e3bf4f4 _ZN3Gio11Application24local_command_line_vfuncERPPcRi () + 54 7fff6e3c05cb _ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi () + 10b 7fffae8a2845 g_application_run () + 155 00422b4e main () + 5e 00421e07 _start_crt () + 87 00421d68 _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
Re: [OpenIndiana-discuss] mate-system-monitor crashes
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 ... (: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 - 7fffaeb69d0b g_type_check_instance_cast () + 1b 0044977a _ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE () + 11a 7fff6e3c09b9 _ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine () + 149 7fffae841496 _g_cclosure_marshal_INT__OBJECTv () + 76 7fffaeb3af95 _g_closure_invoke_va () + 185 7fffaeb5af6d g_signal_emit_valist () + 39d 7fffaeb5c05d g_signal_emit () + 7d 7fffae8a032a g_application_call_command_line () + 7a 7fffae8a26b1 g_application_real_local_command_line () + 241 7fff6e3bf4f4 _ZN3Gio11Application24local_command_line_vfuncERPPcRi () + 54 7fff6e3c05cb _ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi () + 10b 7fffae8a2845 g_application_run () + 155 00422b4e main () + 5e 00421e07 _start_crt () + 87 00421d68 _start () + 18 ... Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] screensave failure to display GL screensavers
On 1/31/23 22:19, Stephan Althaus wrote: On 1/30/23 23:08, russell wrote: Hi As I am currently running the nvidia-470 driver, I wondered if downgrading to nvida-390 using the method list below would resolve the issue |#beadm create nvidia-390 #beadm mount nvidia-390 /tmp/nvidia-390 #pkg -R /tmp/nvidia-390 uninstall nvidia-470 #pkg -R /tmp/nvidia-390 install nvidia-390 #beadm activate nvidia-390 #init 6 | || Unfortunately while the driver downgrade worked, lightdm goes into maintenance so can not check if this has fixed the issue. Any suggestions on how to proceed to get lightdm working tia Russell ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi Russell! I can confirm this behavior on my machine with nvidia-515: $ /usr/lib/xscreensaver/hacks/glhanoi glhanoi: unable to allocate memory for floor display list The other programs in directory hacks don't show an error, but only show a black window, no content :-/ BTW, do you use 30bit color depth, 10bit per color RGB? $ grep -i depth /var/log/Xorg.0.log [ 67.312] (**) NVIDIA(0): Depth 30, (--) framebuffer bpp 32 Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! i tried some GL/freeglut example programs (https://cs.lmu.edu/~ray/notes/openglexamples/ : "bouncingballs.cpp", "moon.cpp") and can confirm that GL works, generally. Why the GL screensavers don't work - i have no clue.. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] screensave failure to display GL screensavers
On 1/30/23 23:08, russell wrote: Hi As I am currently running the nvidia-470 driver, I wondered if downgrading to nvida-390 using the method list below would resolve the issue |#beadm create nvidia-390 #beadm mount nvidia-390 /tmp/nvidia-390 #pkg -R /tmp/nvidia-390 uninstall nvidia-470 #pkg -R /tmp/nvidia-390 install nvidia-390 #beadm activate nvidia-390 #init 6 | || Unfortunately while the driver downgrade worked, lightdm goes into maintenance so can not check if this has fixed the issue. Any suggestions on how to proceed to get lightdm working tia Russell ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi Russell! I can confirm this behavior on my machine with nvidia-515: $ /usr/lib/xscreensaver/hacks/glhanoi glhanoi: unable to allocate memory for floor display list The other programs in directory hacks don't show an error, but only show a black window, no content :-/ BTW, do you use 30bit color depth, 10bit per color RGB? $ grep -i depth /var/log/Xorg.0.log [ 67.312] (**) NVIDIA(0): Depth 30, (--) framebuffer bpp 32 Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] screensave failure to display GL screensavers
On 1/30/23 23:08, russell wrote: Hi As I am currently running the nvidia-470 driver, I wondered if downgrading to nvida-390 using the method list below would resolve the issue |#beadm create nvidia-390 #beadm mount nvidia-390 /tmp/nvidia-390 #pkg -R /tmp/nvidia-390 uninstall nvidia-470 #pkg -R /tmp/nvidia-390 install nvidia-390 #beadm activate nvidia-390 #init 6 | || Unfortunately while the driver downgrade worked, lightdm goes into maintenance so can not check if this has fixed the issue. Any suggestions on how to proceed to get lightdm working tia Russell ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hi Russell! We should investigate what is happening first. The first thing that comes to my mind, is that X fails to start. What error messages are in /var/log/Xorg.0.log? Or, did you try starting X manually? I think i use "startx" and then "pkill twm" inside the xterm and then "mate-session" in these cases... to get a full-featured desktop. HTH Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Help needed starting postfix as a service - maintenance state
On 1/23/23 08:18, Stephan Althaus wrote: Hello! Yesterday i moved from CSWpostfix to the OI version. "postfix start" and "postfix stop" works in my zone (as root), no errors with "postfix check", but "svcadm enable postfix" results in maintenance state because of: Jan 23 07:45:37 mail postfix/postfix-script[23386]: [ID 947731 mail.crit] fatal: the Postfix mail system is already running Jan 23 07:45:38 mail postfix/postfix-script[23392]: [ID 947731 mail.crit] fatal: the Postfix mail system is already running Jan 23 07:45:39 mail postfix/postfix-script[23398]: [ID 947731 mail.crit] fatal: the Postfix mail system is already running Disabling, and re-enabling does not help, the reboot of the zone doesn't help either. Groups for role 'root' are: #groups root other bin sys adm uucp mail tty lp nuucp daemon postfix Any hints are welcome to get the service running.. Thanks! Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Just to be complete here, the solution was to remove the file /var/spool/postfix/pid/master.pid It was annoying that the manual start of postfix did not complain.. Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Help needed starting postfix as a service - maintenance state
On 1/23/23 11:47, Predrag Zecevic via openindiana-discuss wrote:
On 23.01.2023 11:38, Stephan Althaus wrote:
On 1/23/23 11:36, Predrag Zecevic via openindiana-discuss wrote:
tail -20 $(svcprop -p restarter/logfile svc:/network/smtp:postfix)
Hello!
Thanks for your help..
Nothing new here, There are my tests visible with svcadm clear
postfix...
# tail -20 $(svcprop -p restarter/logfile svc:/network/smtp:postfix)
[ Jan 23 09:29:38 Method "start" exited with status 1. ]
[ Jan 23 09:30:37 Leaving maintenance because clear requested. ]
[ Jan 23 09:30:37 Enabled. ]
[ Jan 23 09:30:37 Executing start method ("/usr/sbin/postfix start"). ]
[ Jan 23 09:30:38 Method "start" exited with status 1. ]
[ Jan 23 09:32:16 Leaving maintenance because clear requested. ]
[ Jan 23 09:32:16 Enabled. ]
[ Jan 23 09:32:16 Executing start method ("/usr/sbin/postfix start"). ]
[ Jan 23 09:32:17 Method "start" exited with status 1. ]
[ Jan 23 09:44:37 Disabled. ]
[ Jan 23 09:44:37 Rereading configuration. ]
[ Jan 23 09:45:08 Enabled. ]
[ Jan 23 09:45:08 Executing start method ("/usr/sbin/postfix start"). ]
[ Jan 23 09:45:09 Method "start" exited with status 1. ]
[ Jan 23 09:45:09 Executing start method ("/usr/sbin/postfix start"). ]
[ Jan 23 09:45:10 Method "start" exited with status 1. ]
[ Jan 23 09:45:10 Executing start method ("/usr/sbin/postfix start"). ]
[ Jan 23 09:45:11 Method "start" exited with status 1. ]
[ Jan 23 09:45:22 Leaving maintenance because disable requested. ]
[ Jan 23 09:45:22 Disabled. ]
Stephan
Than, maybe, mail log can show more. To check where it goes (I am
using rsyslog):
:; grep -w mail /etc/rsyslog.conf
*.err;kern.debug;daemon.notice;mail.crit /var/adm/messages
# Log anything (except auth, cron, daemon & mail) of level info or
higher.
*.info;mail.none;auth.none;cron.none -/var/log/misc.log
# Log all the auth, daemon & mail messages in one place.
mail.* -/var/log/mail.log
:; less /var/log/mail.log # might give a hint next...
HTH
Regards.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Hello!
Jan 23 12:00:47 mail postfix/postfix-script[28446]: [ID 947731
mail.crit] fatal: the Postfix mail system is already running
Jan 23 12:00:48 mail postfix/postfix-script[28628]: [ID 947731
mail.crit] fatal: the Postfix mail system is already running
Jan 23 12:00:49 mail postfix/postfix-script[28794]: [ID 947731
mail.crit] fatal: the Postfix mail system is already running
the process is not running because of zone reboot:
# ps ax|grep post
28813 pts/3 S 0:00 grep post
# netstat -a -P tcp|grep smtp
#
I am not shure how the start of "/usr/sbin/postfix start" within the
service should find a process, there is no process and no other listener
on the port...
Manual start/stop works as expected..
# postfix start
postfix/postfix-script: starting the Postfix mail system
# netstat -a -P tcp|grep smtp
*.smtp *.* 0 0 128000 0
LISTEN
Stephan
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Help needed starting postfix as a service - maintenance state
On 1/23/23 11:36, Predrag Zecevic via openindiana-discuss wrote:
tail -20 $(svcprop -p restarter/logfile svc:/network/smtp:postfix)
Hello!
Thanks for your help..
Nothing new here, There are my tests visible with svcadm clear postfix...
# tail -20 $(svcprop -p restarter/logfile svc:/network/smtp:postfix)
[ Jan 23 09:29:38 Method "start" exited with status 1. ]
[ Jan 23 09:30:37 Leaving maintenance because clear requested. ]
[ Jan 23 09:30:37 Enabled. ]
[ Jan 23 09:30:37 Executing start method ("/usr/sbin/postfix start"). ]
[ Jan 23 09:30:38 Method "start" exited with status 1. ]
[ Jan 23 09:32:16 Leaving maintenance because clear requested. ]
[ Jan 23 09:32:16 Enabled. ]
[ Jan 23 09:32:16 Executing start method ("/usr/sbin/postfix start"). ]
[ Jan 23 09:32:17 Method "start" exited with status 1. ]
[ Jan 23 09:44:37 Disabled. ]
[ Jan 23 09:44:37 Rereading configuration. ]
[ Jan 23 09:45:08 Enabled. ]
[ Jan 23 09:45:08 Executing start method ("/usr/sbin/postfix start"). ]
[ Jan 23 09:45:09 Method "start" exited with status 1. ]
[ Jan 23 09:45:09 Executing start method ("/usr/sbin/postfix start"). ]
[ Jan 23 09:45:10 Method "start" exited with status 1. ]
[ Jan 23 09:45:10 Executing start method ("/usr/sbin/postfix start"). ]
[ Jan 23 09:45:11 Method "start" exited with status 1. ]
[ Jan 23 09:45:22 Leaving maintenance because disable requested. ]
[ Jan 23 09:45:22 Disabled. ]
Stephan
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Help needed starting postfix as a service - maintenance state
Hello! Yesterday i moved from CSWpostfix to the OI version. "postfix start" and "postfix stop" works in my zone (as root), no errors with "postfix check", but "svcadm enable postfix" results in maintenance state because of: Jan 23 07:45:37 mail postfix/postfix-script[23386]: [ID 947731 mail.crit] fatal: the Postfix mail system is already running Jan 23 07:45:38 mail postfix/postfix-script[23392]: [ID 947731 mail.crit] fatal: the Postfix mail system is already running Jan 23 07:45:39 mail postfix/postfix-script[23398]: [ID 947731 mail.crit] fatal: the Postfix mail system is already running Disabling, and re-enabling does not help, the reboot of the zone doesn't help either. Groups for role 'root' are: #groups root other bin sys adm uucp mail tty lp nuucp daemon postfix Any hints are welcome to get the service running.. Thanks! Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] pkg install conflicts
+1 # pkg refresh && pkg update -n Creating Plan (Checking for conflicting actions): \ pkg update: The requested change to the system attempts to install multiple actions for link 'usr/lib/amd64/libgcc_s.so' with conflicting attributes: These packages cannot be installed together. Any non-conflicting subset of the above packages can be installed. On 1/20/23 10:24, Richard L. Hamilton wrote: This VM is updated almost daily, so it’s not as if it was so out-of-date that problems might be expected; so I imagine something is not consistent in the packages in the repository. root@openindiana:~# pkg update Creating Plan (Checking for conflicting actions): | pkg update: The requested change to the system attempts to install multiple actions for link 'usr/lib/amd64/libgcc_s.so' with conflicting attributes: 1 package delivers 'link path=usr/lib/amd64/libgcc_s.so target=../../gcc/10/lib/amd64/libgcc_s.so': pkg://openindiana.org/system/library/gcc-10-compat-links@10.4.0,5.11-2022.1.0.2:20221228T113632Z 1 package delivers 'link path=usr/lib/amd64/libgcc_s.so target=libgcc_s.so.1': pkg://openindiana.org/system/library/gcc-4-runtime@4.9.4,5.11-2022.0.0.10:20220716T171440Z These packages cannot be installed together. Any non-conflicting subset of the above packages can be installed. The following packages deliver conflicting action types to usr/lib/amd64/libgcc_s.so.1: link: pkg://openindiana.org/system/library/gcc-10-compat-links@10.4.0,5.11-2022.1.0.2:20221228T113632Z file: pkg://openindiana.org/system/library/gcc-4-runtime@4.9.4,5.11-2022.0.0.10:20220716T171440Z These packages cannot be installed together. Any non-conflicting subset of the above packages can be installed. The requested change to the system attempts to install multiple actions for link 'usr/lib/amd64/libgomp.so' with conflicting attributes: 1 package delivers 'link path=usr/lib/amd64/libgomp.so target=../../gcc/10/lib/amd64/libgomp.so': pkg://openindiana.org/system/library/gcc-10-compat-links@10.4.0,5.11-2022.1.0.2:20221228T113632Z 1 package delivers 'link path=usr/lib/amd64/libgomp.so target=libgomp.so.1': pkg://openindiana.org/system/library/gcc-4-runtime@4.9.4,5.11-2022.0.0.10:20220716T171440Z These packages cannot be installed together. Any non-conflicting subset of the above packages can be installed. The following packages deliver conflicting action types to usr/lib/amd64/libgomp.so.1: link: pkg://openindiana.org/system/library/gcc-10-compat-links@10.4.0,5.11-2022.1.0.2:20221228T113632Z file: pkg://openindiana.org/system/library/gcc-4-runtime@4.9.4,5.11-2022.0.0.10:20220716T171440Z These packages cannot be installed together. Any non-conflicting subset of the above packages can be installed. The requested change to the system attempts to install multiple actions for link 'usr/lib/amd64/libssp.so.0' with conflicting attributes: 1 package delivers 'link path=usr/lib/amd64/libssp.so.0 target=../../gcc/10/lib/amd64/libssp.so.0': pkg://openindiana.org/system/library/gcc-10-compat-links@10.4.0,5.11-2022.1.0.2:20221228T113632Z 1 package delivers 'link path=usr/lib/amd64/libssp.so.0 target=libssp.so.0.0.0': pkg://openindiana.org/system/library/g++-4-runtime@4.9.4,5.11-2022.0.0.10:20220716T171432Z These packages cannot be installed together. Any non-conflicting subset of the above packages can be installed. The requested change to the system attempts to install multiple actions for link 'usr/lib/libssp.so' with conflicting attributes: 1 package delivers 'link path=usr/lib/libssp.so target=../gcc/10/lib/libssp.so': pkg://openindiana.org/system/library/gcc-10-compat-links@10.4.0,5.11-2022.1.0.2:20221228T113632Z 1 package delivers 'link path=usr/lib/libssp.so target=libssp.so.0.0.0': pkg://openindiana.org/system/library/g++-4-runtime@4.9.4,5.11-2022.0.0.10:20220716T171432Z These packages cannot be installed together. Any non-conflicting subset of the above packages can be installed. The requested change to the system attempts to install multiple actions for link 'usr/lib/amd64/libstdc++.so' with conflicting attributes: 1 package delivers 'link path=usr/lib/amd64/libstdc++.so target=../../gcc/10/lib/amd64/libstdc++.so': pkg://openindiana.org/system/library/gcc-10-compat-links@10.4.0,5.11-2022.1.0.2:20221228T113632Z 1 package delivers 'link path=usr/lib/amd64/libstdc++.so target=libstdc++.so.6.0.20': pkg://openindiana.org/system/library/g++-4-runtime@4.9.4,5.11-2022.0.0.10:20220716T171432Z These packages cannot be installed together. Any non-conflicting subset of the above packages can be installed. The requested change to the system attempts to install multiple actions for link 'usr/lib/libssp.so.0' with conflicting attributes: 1 package delivers 'link path=usr/lib/libssp.so.0 target=../gcc/10/lib/libssp.so.0': pkg
