Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,

[Carsten Grzemba via openindiana-discuss]

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
>

Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,

[Carsten Grzemba via openindiana-discuss]

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

Re: [OpenIndiana-discuss] ask for a small contribution related Pulseaudio,

[Carsten Grzemba via openindiana-discuss]

Hi Stephan,

Am 10.02.24 09:41 schrieb Stephan Althaus  : 
> 
> 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
> 
> 

Because your device instance numbers are not the same like the /dev/dsp index, 
I also interested in the output of 

$ pactl info 


Thanks!

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

[OpenIndiana-discuss] ask for a small contribution related Pulseaudio,

[Carsten Grzemba via openindiana-discuss]

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!

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

[OpenIndiana-discuss] Pulseaudio 17 for test

[Carsten Grzemba via openindiana-discuss]

If some one interested to test or review

here is the current version of Pulseaudio, on
http://pkg.toc.de/userland
you can find the latest version of pulseaudio packaged for OI.
(but without Gary's patch for #9732)


Regards

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

[OpenIndiana-discuss] pulseaudio issue

[Carsten Grzemba via openindiana-discuss]

since one month or so I see the problem that the volume control applet is not 
working any more for me and on logout I get the notice
that mate-settings-daemon is still running
The reason behind is that there some pulsaudio processes hang:

1399 /usr/sbin/lightdm
 2259 lightdm --session-child 13 25
 2268 mate-session --debug
 2312 /usr/lib/amd64/mate/mate-settings-daemon
 2314 /usr/bin/pulseaudio --start --log-target=syslog
 2315 /usr/bin/pulseaudio --start --log-target=syslog
 2316 /usr/bin/pulseaudio --start --log-target=syslog
 2318 /usr/lib/amd64/pulse/gsettings-helper


Some strange is the first pulseaudio process has a zombie in his stomach
314: /usr/bin/pulseaudio --start --log-target=syslog
- thread# 1 / lwp# 1 -
 7fffaf40a28a read (7, 7fffb6c0, 4)
 7fffa7fa6f32 pa_read () + 22
 7fffa7fa705e pa_loop_read () + 5e
 0040d645 main () + 18e5
 00407477 _start_crt () + 87
 004073d8 _start () + 18
- thread# 2 / lwp# 2 -
 7fffa7fd4a30 internal_thread_func(), exit value = 0x
 ** zombie (exited, not detached, not yet joined) **


I see this on my laptop. Has this anyone seen too? And an idea how to get rid 
of it?
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Heads-Up: Obsoletion of 39 old packages

[Carsten Grzemba via openindiana-discuss]

Am 10.01.24 10:34 schrieb Marcel Telka  : 
> 
> On Tue, Jan 09, 2024 at 04:08:13PM -0600, Matthew R. Trower wrote:
> > > All of them are:
> > > - very old - they are more than 10 years old
> > > - not maintained - we have no knowledge how to build them (there are
> > > no build recipes for them in oi-userland)
> > > - not needed - nothing in OpenIndiana depends on them
> > 
> > I'm not very knowledgeable on how OI is packaged; how are they in the repos
> > currently if we can't build them? Did we inherit them in binary format in
> > the ON IPS repos or something?
> 
> Without browsing to a lot of details the short answer is: yes.
> 
> All these OpenIndiana packages (and also ca 60 more packages that are
> not on the list) are just binary blobs nobody knows for sure what
> exactly is there, what bugs they contain, what security vulnerabilities,
> or possibly malware, etc.
> 
> If you or somebody else believe we should keep any of them then somebody
> needs to sit down and create build recipes for them. This needs labor
> and time somebody needs to invest. Since nobody cared so far for many
> many years it looks obvious that these pacakges are abandoned, unused,
> rotted.
> 
> > I can say JEdit still works at a cursory glance. I don't use it very often
> > anymore, but I'm not sure why it should have to go if it isn't broken. Is
> > it causing you problems somehow?
> 
> Our current jedit package is at version 4.3. This version was released
> upstream 14 years ago. Since 4.3 there were about 15 new releases
> upstream. The latest one is 5.6.0 released on September 2020.
> 
> More info: https://sourceforge.net/projects/jedit
> 
> The current jedit package is distributed (at least partly) under GPLv2.
> This means that OpenIndiana should provide sources and build recipes for
> the package. We do not have that, so it looks like we violate the
> license (IANAL). We should stop.
> 
> > dwdiff appears to have source available
> > https://os.ghalkes.nl/dwdiff.html
> 
> We are at 1.5.2 released upstream 15 years ago. The latest upstream is
> 2.1.4 released 3 years ago. License: GPLv3 (see above)
> 
> > as does mtx
> > https://sourceforge.net/projects/mtx/
> 
> Our package is 1.3.11 released upstream 17 years ago. The latest is
> 1.3.12 released 15 years ago. License: GPLv2 (see above)
> 
> > I wonder why we don't?
> 
> Why we don't what?
> 
> > For the CDE packages, we don't ship an entire CDE, right? So all they can do
> 
> We do ship this:
> 
> $ pkg list -a | grep '\'
> cde/calendar-manager-server 0.5.11-2013.0.0.0 ---
> cde/cde-runtime 0.5.11-2013.0.0.0 ---
> cde/cde-utilities 0.5.11-2013.0.0.0 ---
> cde/help-viewer 0.5.11-2013.0.0.0 ---
> consolidation/cde/cde-incorporation 0.5.11-2013.0.0.0 i--
> $
> 
> I do not know how complete it is.
> 
> > is support programs intended to run on/integrate with CDE, on machines that
> > don't actually have CDE installed... right? Furthermore, CDE is open source
> 
> No idea.
> 
> > these days. I don't know if current releases compile on OI, but it did at
> > least compile at one time (I use it as my DE, in fact), and at any rate
> 
> If you are able to compile it, then you are welcome to contribute it to
> oi-userland.
> 
> The git repo is here: https://github.com/OpenIndiana/oi-userland
> 
> > ought to be able to be made to compile again. So, people ought to be able to
> > get a proper release of CDE if they desire one (though that may change if
> > enough of the wrong 32-bit libs disappear). Therefore, I would say CDE
> > packages probably constitute cruft and ought to be able to go.
> 
> -- 
> +---+
> | Marcel Telka e-mail: mar...@telka.sk |
> | homepage: http://telka.sk/ |
> +---+
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 

Should we really remove all GPL licensed components?   Sources and build 
recipes are public available.   
I use mtx and I would update the package.
  
-- 

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

Re: [OpenIndiana-discuss] Python abstact socket and config printer applet.py

[Carsten Grzemba via openindiana-discuss]

Am 14.12.23 00:08 schrieb Bill Sommerfeld via openindiana-discuss  
: 
> 
> On 12/13/23 15:03, Joshua M. Clulow via openindiana-discuss wrote:
> >On Wed, 13 Dec 2023 at 09:24, Carsten Grzemba via openindiana-discuss
> > wrote:
> >>A sock.bind with an normal string works, but not the style with the leading 
> >>\0. This is the syntax for abstract sockets on Linux.
> >>I have no idea if abstract sockets would work on Illumos and Python. But 
> >>how should work the printer applet on non Linux systems?
> >
> >You will need to put the socket in a directory with the appropriate 
> >permissions.
> >
> >Note that any user on the system can connect() to a UNIX socket if
> >they can see the directory entry for it, regardless of the permissions
> >on the socket entry itself. If the socket server is not using
> >getpeerucred(3C) or equivalent to inspect the credentials of the
> >connecting process, you should put the socket in a directory owned by
> >the user with mode 0700 to prevent connections from unauthorised
> >processes.
> 
> A quick look at the applet.py code shows that it creates the bound socket as 
> a lock (to prevent multiple instances from running as the same user) but 
> never uses it for anything or passes it to anything outside the "__main__" 
> block.
> 
> So there's no need to prevent connections - the daemon will never call 
> sock.accept()
> 
The code is really only for the reason what the exception notice says: To check 
if the applet already running.
There are no more compatible solutions for this task?



-- 

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

[OpenIndiana-discuss] Python abstact socket and config printer applet.py

[Carsten Grzemba via openindiana-discuss]

I don't know when I have seen the last time the printer applet in mate-panel.

On my attempts to revive the applet I stumbled on the abstract socket stuff in 
the Python code of applet.py

If i try to start 

/usr/share/system-config-printer/applet.py I get the exception 

Process already running (2:No such file or directory). Exiting.


For the used syntax 

sock.bind("\0printer-applet-lock-user-" + getpass.getuser())
the error is 2:No such file or directory, the "Process already running" notice 
is the interpretation of the exception handler

A sock.bind with an normal string works, but not the style with the leading \0. 
This is the syntax for abstract sockets on Linux.
I have no idea if abstract sockets would work on Illumos and Python. But how 
should work the printer applet on non Linux systems?


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

Re: [OpenIndiana-discuss] Login timeout on failed login

[Carsten Grzemba via openindiana-discuss]

Am 06.12.23 08:29 schrieb russell  : 
> 
> Hi,
> 
> Previously when I made a mistake typing my login password you would get an 
> error and then you could re-enter your password.
> Since updating to SunOS 5.11 illumos-f5a3d331e8 on the 29th Nov, when 
> entering an incorrect password no error is generated, the mouse still moves, 
> the cancel and login buttons are available but can not be depressed. So after 
> two minutes I rebooted my desktop and made sure I entered my password 
> correctly.
> Has there been a change to the default behaviour or is this a bug?
> 

I see this behaviour on an BE from 28th Nov

$ ssh admin@con3
(admin@con3) Password: 
Received disconnect from 172.16.xx.xx port 22:2: Too many authentication 
failures
Disconnected from 172.16.xx.xx port 22


but on a BE from 4th Dec it works normal with 3 attempts possible before 
failing finally.

Can you confirm this for mate-greeter login.

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

Re: [OpenIndiana-discuss] Mate clock applet gone

[Carsten Grzemba via openindiana-discuss]

Am 02.12.23 11:50 schrieb Stephan Althaus  : 
> 
> 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 
> ?
> 

Yes, and I guess you will get a message about mixed gtk2 and gtk3 symbols.

Which is wrong, the test for that in glib seems to be not reentrant and there 
is a similat test in libsoup about version 2 and 3. That leads to a false 
positve.

For publish the libsoup@2.74.3-2023.0.0.1 or newer we need a rebuild of 
illumos-gate becasue this is used by rtld and this in turn needs an patched 
libxml2@2.12.1.
It is all in the queue but rebuild needs some time.

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

Re: [OpenIndiana-discuss] Cannot delete an ADDROBJ in ipadm?

[Carsten Grzemba via openindiana-discuss]

Am 30.11.23 14:34 schrieb Philip Kime  : 
> 
> I was trying to switch from fixed IP to DHCP and finally managed to get it to 
> work but in the process, I created a dhcp addr on the interface with ipadm 
> and now I can't get rid of it:
> 
> root@park:~# ipadm
> ADDROBJ TYPE STATE ADDR
> lo0/v4 static ok 127.0.0.1/8
> rge0/_a dhcp ok 192.168.0.50/24
> lo0/v6 static ok ::1/128
> rge0/? static ok fe80::baae:edff:fedb:1e5c%rge0/10
> rge0/? addrconf ok 2a02:1210:14dd:3100:baae:edff:fedb:1e5c/64
> rge0/addr dhcp disabled ?
> root@park:~# ipadm delete-addr rge0/addr
> ipadm: could not delete address: Object not found
> root@park:~#
> 
> The underlined can't be removed any way I've tried. Does anyone know how to 
> delete it? Network is working fine with DHCP using the /_a ADDROBJ but I want 
> to clean this up.
> On Hipster 2023.05
> 

Do you see any warnings related nwamd or dhcp in /var/adm/messages since system 
boot?
If yes, please post.


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

Re: [OpenIndiana-discuss] spam>Re: update ConsoleKit

[Carsten Grzemba via openindiana-discuss]

Am 24.11.23 08:14 schrieb Marcel Telka  : 
> 
> On Thu, Nov 23, 2023 at 12:06:06PM +0100, Carsten Grzemba via 
> openindiana-discuss wrote:
> > Does anyone knows which components really use this tools and would be
> > affected by this change (beside SunRay)?
> 
> $ target/release/oi-pkg-checker check-fmri library/xdg/consolekit
> [INFO] fmri pkg:/library/xdg/consolekit is required by:
> [INFO] type: require, dependency: RUNTIME, package: 
> pkg://openindiana.org/mate_install@1,5.11-2023.0.0.0:20231020T195142Z
> [INFO] type: incorporate, dependency: RUNTIME, package: 
> pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11,5.11-2023.0.0.2:20231119T212227Z
> [INFO] type: require, dependency: RUNTIME, package: 
> pkg://openindiana.org/library/security/pam/module/pam-consolekit@0.4.1,5.11-2022.0.0.4:20220718T153347Z
> [INFO] type: require, dependency: RUNTIME, package: 
> pkg://openindiana.org/system/display-manager/lightdm@1.30.0,5.11-2022.0.0.3:20220910T170257Z
> [INFO] component name: library/ConsoleKit
> $
> 
> PS: The tool is available here: https://github.com/aueam/oi-pkg-checker
> 

Thanks!

It is also possible to check which packages comes from oi-userland and which 
from illumos-gate?

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

[OpenIndiana-discuss] zoneadm attach -u failed

[Carsten Grzemba via openindiana-discuss]

I want to reattach a local ipkg zone and run in an error:

Traceback (most recent call last):
 File "/usr/bin/pkg", line 5962, in handle_errors
 __ret = func(*args, **kwargs)
 File "/usr/bin/pkg", line 5947, in main_func
 return func(op=subcommand, api_inst=api_inst,
 File "/usr/bin/pkg", line 2268, in install
 out_json = client_api._install(op, api_inst, pargs,
 File "/usr/lib/python3.9/vendor-packages/pkg/client/client_api.py", line 1516, 
in _install
 return __api_op(op, api_inst, _accept=accept, _li_ignore=li_ignore,
 File "/usr/lib/python3.9/vendor-packages/pkg/client/client_api.py", line 1395, 
in __api_op
 ret = __api_plan(_op=_op, _api_inst=_api_inst,
 File "/usr/lib/python3.9/vendor-packages/pkg/client/client_api.py", line 1256, 
in __api_plan
 ret = __api_plan_exception(_op, _noexecute, _verbose,
 File "/usr/lib/python3.9/vendor-packages/pkg/client/client_api.py", line 1230, 
in __api_plan
 for pd in api_plan_func(**kwargs):
 File "/usr/lib/python3.9/vendor-packages/pkg/client/api.py", line 1578, in 
__plan_op
 self.__plan_common_exception(
 File "/usr/lib/python3.9/vendor-packages/pkg/client/api.py", line 1207, in 
__plan_common_exception
 six.reraise(exc_type, exc_value, exc_traceback)
 File "/usr/lib/python3.9/vendor-packages/six.py", line 719, in reraise
 raise value
 File "/usr/lib/python3.9/vendor-packages/pkg/client/api.py", line 1513, in 
__plan_op
 self._img.make_install_plan(**kwargs)
 File "/usr/lib/python3.9/vendor-packages/pkg/client/image.py", line 4509, in 
make_install_plan
 self.__make_plan_common(op, progtrack, check_cancel,
 File "/usr/lib/python3.9/vendor-packages/pkg/client/image.py", line 4492, in 
__make_plan_common
 self.__call_imageplan_evaluate(ip)
 File "/usr/lib/python3.9/vendor-packages/pkg/client/image.py", line 4404, in 
__call_imageplan_evaluate
 ip.evaluate()
 File "/usr/lib/python3.9/vendor-packages/pkg/client/imageplan.py", line 3879, 
in evaluate
 self.__evaluate_pkg_plans()
 File "/usr/lib/python3.9/vendor-packages/pkg/client/imageplan.py", line 4061, 
in __evaluate_pkg_plans
 pp.evaluate(self.__old_excludes, self.__new_excludes,
 File "/usr/lib/python3.9/vendor-packages/pkg/client/pkgplan.py", line 346, in 
evaluate
 dest_pub, self.image.trust_anchors,
 File "/usr/lib/python3.9/vendor-packages/pkg/client/image.py", line 352, in 
trust_anchors
 x509.load_pem_x509_certificate(
 File "/usr/lib/python3.9/vendor-packages/cryptography/x509/base.py", line 583, 
in load_pem_x509_certificate
 return rust_x509.load_pem_x509_certificate(data)
cryptography.utils.CryptographyDeprecationWarning: Parsed a negative serial 
number, which is disallowed by RFC 5280.



How can I fix this?

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

[OpenIndiana-discuss] update ConsoleKit

[Carsten Grzemba via openindiana-discuss]

I would do a small rework of ConsoleKit. 

- update to 0.4.6
- build in 64bit

- change the path for tools (ck-collect-session-info, ck-get-x11-server-pid, 
ck-get-x11-display-device):

 -CONFIGURE_OPTIONS+= --libexecdir=/usr/lib
+CONFIGURE_OPTIONS+= --libexecdir=/usr/libexec/$(MACH$(BITS))


Does anyone knows which components really use this tools and would be affected 
by this change (beside SunRay)?
Is 32bit build still needed?


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

Re: [OpenIndiana-discuss] gccgo issue

[Carsten Grzemba via openindiana-discuss]

Am 23.10.23 10:35 schrieb russell  : 
> 
>  
>   
> 
> 
> 
>  
> Hi Carsten
>  
> Tried 
>  
> # pkg refresh
>  # pkg fix gcc-10
>  No updates necessary for this image.
>  
>  
> Kind Regards
>  
> Russell
> 
>  
> 

so 

# pkg contents gcc-10 

should list:
...

usr/gcc/10/bin/go
...
-- 
Carsten Grzemba
Tel.: +49 3677 64740
Mobil: +49 171 9749479
Email: carsten.grze...@contac-dt.de
contac Datentechnik GmbH
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] gccgo issue

[Carsten Grzemba via openindiana-discuss]

Am 23.10.23 08:41 schrieb russell  : 
> 
> Hi
> 
> Tried installing pkg:/developer/gcc-10@10.5.0-2023.0.0.1
> 
> # pkg install pkg:/developer/gcc-10@10.5.0-2023.0.0.1
> No updates necessary for this image.
> 
> Kind Regards
> 
> Russell
> 
> On 10/23/23 07:12, russell wrote:
> >
> > Hi
> >
> > I have the package pkg:/developer/gcc-10@10.5.0-2023.0.0.1 installed 
> > but the /usr/gcc/10/bin/go which is apart of the pkg is not installed
> > Do I need to re-install the pkg:/developer/gcc-10@10.5.0-2023.0.0.1 
> > package?
> >
> > Kind Regards
> >
> > Russell
> >
> > On 10/22/23 19:17, russell wrote:
> >>
> >>
> >> Update my desktop around 10 mins ago, getting the same error after update
> >>
> >> $ uname -a
> >> SunOS tesla 5.11 illumos-9fbdb45a98 i86pc i386 i86pc
> >>
> >> $ gccgo -v
> >> Using built-in specs.
> >> COLLECT_GCC=gccgo
> >> COLLECT_LTO_WRAPPER=/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/lto-wrapper
> >> Target: x86_64-pc-solaris2.11
> >> Configured with: 
> >> /jenkins/jobs/oi-userland/workspace/components/developer/gcc-10/gcc-releases-gcc-10.5.0/configure
> >>  
> >> CC=/usr/gcc/10/bin/gcc CXX=/usr/gcc/10/bin/g++ 
> >> F77=/usr/gcc/10/bin/gfortran FC=/usr/gcc/10/bin/gfortran CFLAGS=-O2 
> >> CXXFLAGS=-O2 FFLAGS=' -O3 ' FCFLAGS=-O2 LDFLAGS=-m64 
> >> PKG_CONFIG_PATH=/usr/openssl/3.1/lib/64/pkgconfig:/usr/mariadb/10.6/lib/amd64/pkgconfig:/usr/lib/amd64/pkgconfig:/usr/lib/pkgconfig
> >>  
> >> --prefix=/usr/gcc/10 --mandir=/usr/gcc/10/share/man 
> >> --bindir=/usr/gcc/10/bin --libdir=/usr/gcc/10/lib 
> >> --sbindir=/usr/gcc/10/sbin --sbindir=/usr/gcc/10/bin 
> >> --libdir=/usr/gcc/10/lib --libexecdir=/usr/gcc/10/lib --host 
> >> x86_64-pc-solaris2.11 --build x86_64-pc-solaris2.11 --target 
> >> x86_64-pc-solaris2.11 --with-pkgversion='OpenIndiana 10.5.0-oi-1' 
> >> --with-bugurl=https://bugs.openindiana.org --without-gnu-ld 
> >> --with-ld=/usr/bin/ld 
> >> --with-build-time-tools=/usr/gnu/x86_64-pc-solaris2.11/bin 
> >> --disable-bootstrap --with-gnu-as --with-as=/usr/bin/gas 
> >> LDFLAGS=-R/usr/gcc/10/lib --with-diagnostics-urls=auto-if-env 
> >> --enable-plugins --enable-objc-gc 
> >> --enable-languages=c,c++,fortran,go,lto,objc --disable-libitm 
> >> enable_frame_pointer=yes
> >> Thread model: posix
> >> Supported LTO compression algorithms: zlib zstd
> >> gcc version 10.5.0 (OpenIndiana 10.5.0-oi-1)
> >> COMPILER_PATH=/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/:/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/:/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/:/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/:/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/:/usr/ccs/bin/
> >> LIBRARY_PATH=/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/:/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/../../../amd64/:/lib/amd64/:/usr/lib/amd64/:/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/../../../:/lib/:/usr/lib/
> >> COLLECT_GCC_OPTIONS='-v' '-shared-libgcc' '-mtune=generic' 
> >> '-march=x86-64'
> >> /usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/collect2 -V -M 
> >> /usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/../../../libgcc-unwind.map
> >>  
> >> -Y P,/usr/gcc/10/lib/amd64:/lib/amd64:/usr/lib/amd64 -R 
> >> /usr/gcc/10/lib/amd64 -L /usr/gcc/10/lib/amd64 -Qy 
> >> /usr/lib/amd64/crt1.o 
> >> /usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/crtp.o 
> >> /usr/lib/amd64/crti.o /usr/lib/amd64/values-Xa.o 
> >> /usr/lib/amd64/values-xpg6.o 
> >> /usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/crtbegin.o 
> >> -L/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0 
> >> -L/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/../../../amd64 
> >> -L/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/../../.. -t 
> >> -lgcc_s -lgcc -lc -lgcc_s -lgcc 
> >> /usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/crtend.o 
> >> /usr/lib/amd64/crtn.o
> >> ld: Software Generation Utilities - Solaris Link Editors: 5.11-1.1790 
> >> (illumos)
> >> Undefined first referenced
> >> symbol in file
> >> main /usr/lib/amd64/crt1.o
> >> ld: fatal: symbol referencing errors. No output written to a.out
> >> collect2: error: ld returned 1 exit status
> >>
> >> Other gcc compilers work
> >>
> >> $ gcc -v
> >> Using built-in specs.
> >> COLLECT_GCC=gcc
> >> COLLECT_LTO_WRAPPER=/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/lto-wrapper
> >> Target: x86_64-pc-solaris2.11
> >> Configured with: 
> >> /jenkins/jobs/oi-userland/workspace/components/developer/gcc-10/gcc-releases-gcc-10.5.0/configure
> >>  
> >> CC=/usr/gcc/10/bin/gcc CXX=/usr/gcc/10/bin/g++ 
> >> F77=/usr/gcc/10/bin/gfortran FC=/usr/gcc/10/bin/gfortran CFLAGS=-O2 
> >> CXXFLAGS=-O2 FFLAGS=' -O3 ' FCFLAGS=-O2 LDFLAGS=-m64 
> >> PKG_CONFIG_PATH=/usr/openssl/3.1/lib/64/pkgconfig:/usr/mariadb/10.6/lib/amd64/pkgconfig:/usr/lib/amd64/pkgconfig:/usr/lib/pkgconfig
> >>  
> >> --prefix=/usr/gcc/10 --mandir=/usr/gcc/10/share/man 
> >> --bindir=/usr/gcc/10/bin --libdir=/usr/gcc/10/lib 
> >> --sbindir=/usr/gcc/10/sbin --sbindir=/usr/gcc/10/bin 
> >> --libdir=/usr/gcc/10/lib 

Re: [OpenIndiana-discuss] gccgo issue

[Carsten Grzemba via openindiana-discuss]

Am 23.10.23 08:12 schrieb russell  : 
> 
> Hi
> 
> I have the package pkg:/developer/gcc-10@10.5.0-2023.0.0.1 installed but 
> the /usr/gcc/10/bin/go which is apart of the pkg is not installed
> Do I need to re-install the pkg:/developer/gcc-10@10.5.0-2023.0.0.1 package?
> 
> Kind Regards
> 
> Russell
> 
> On 10/22/23 19:17, russell wrote:
> >
> >
> > Update my desktop around 10 mins ago, getting the same error after update
> >
> > $ uname -a
> > SunOS tesla 5.11 illumos-9fbdb45a98 i86pc i386 i86pc
> >
> > $ gccgo -v
> > Using built-in specs.
> > COLLECT_GCC=gccgo
> > COLLECT_LTO_WRAPPER=/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/lto-wrapper
> > Target: x86_64-pc-solaris2.11
> > Configured with: 
> > /jenkins/jobs/oi-userland/workspace/components/developer/gcc-10/gcc-releases-gcc-10.5.0/configure
> >  
> > CC=/usr/gcc/10/bin/gcc CXX=/usr/gcc/10/bin/g++ 
> > F77=/usr/gcc/10/bin/gfortran FC=/usr/gcc/10/bin/gfortran CFLAGS=-O2 
> > CXXFLAGS=-O2 FFLAGS=' -O3 ' FCFLAGS=-O2 LDFLAGS=-m64 
> > PKG_CONFIG_PATH=/usr/openssl/3.1/lib/64/pkgconfig:/usr/mariadb/10.6/lib/amd64/pkgconfig:/usr/lib/amd64/pkgconfig:/usr/lib/pkgconfig
> >  
> > --prefix=/usr/gcc/10 --mandir=/usr/gcc/10/share/man 
> > --bindir=/usr/gcc/10/bin --libdir=/usr/gcc/10/lib 
> > --sbindir=/usr/gcc/10/sbin --sbindir=/usr/gcc/10/bin 
> > --libdir=/usr/gcc/10/lib --libexecdir=/usr/gcc/10/lib --host 
> > x86_64-pc-solaris2.11 --build x86_64-pc-solaris2.11 --target 
> > x86_64-pc-solaris2.11 --with-pkgversion='OpenIndiana 10.5.0-oi-1' 
> > --with-bugurl=https://bugs.openindiana.org --without-gnu-ld 
> > --with-ld=/usr/bin/ld 
> > --with-build-time-tools=/usr/gnu/x86_64-pc-solaris2.11/bin 
> > --disable-bootstrap --with-gnu-as --with-as=/usr/bin/gas 
> > LDFLAGS=-R/usr/gcc/10/lib --with-diagnostics-urls=auto-if-env 
> > --enable-plugins --enable-objc-gc 
> > --enable-languages=c,c++,fortran,go,lto,objc --disable-libitm 
> > enable_frame_pointer=yes
> > Thread model: posix
> > Supported LTO compression algorithms: zlib zstd
> > gcc version 10.5.0 (OpenIndiana 10.5.0-oi-1)
> > COMPILER_PATH=/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/:/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/:/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/:/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/:/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/:/usr/ccs/bin/
> > LIBRARY_PATH=/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/:/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/../../../amd64/:/lib/amd64/:/usr/lib/amd64/:/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/../../../:/lib/:/usr/lib/
> > COLLECT_GCC_OPTIONS='-v' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
> > /usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/collect2 -V -M 
> > /usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/../../../libgcc-unwind.map 
> > -Y P,/usr/gcc/10/lib/amd64:/lib/amd64:/usr/lib/amd64 -R 
> > /usr/gcc/10/lib/amd64 -L /usr/gcc/10/lib/amd64 -Qy 
> > /usr/lib/amd64/crt1.o 
> > /usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/crtp.o 
> > /usr/lib/amd64/crti.o /usr/lib/amd64/values-Xa.o 
> > /usr/lib/amd64/values-xpg6.o 
> > /usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/crtbegin.o 
> > -L/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0 
> > -L/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/../../../amd64 
> > -L/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/../../.. -t -lgcc_s 
> > -lgcc -lc -lgcc_s -lgcc 
> > /usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/crtend.o 
> > /usr/lib/amd64/crtn.o
> > ld: Software Generation Utilities - Solaris Link Editors: 5.11-1.1790 
> > (illumos)
> > Undefined first referenced
> > symbol in file
> > main /usr/lib/amd64/crt1.o
> > ld: fatal: symbol referencing errors. No output written to a.out
> > collect2: error: ld returned 1 exit status
> >
> > Other gcc compilers work
> >
> > $ gcc -v
> > Using built-in specs.
> > COLLECT_GCC=gcc
> > COLLECT_LTO_WRAPPER=/usr/gcc/10/lib/gcc/x86_64-pc-solaris2.11/10.5.0/lto-wrapper
> > Target: x86_64-pc-solaris2.11
> > Configured with: 
> > /jenkins/jobs/oi-userland/workspace/components/developer/gcc-10/gcc-releases-gcc-10.5.0/configure
> >  
> > CC=/usr/gcc/10/bin/gcc CXX=/usr/gcc/10/bin/g++ 
> > F77=/usr/gcc/10/bin/gfortran FC=/usr/gcc/10/bin/gfortran CFLAGS=-O2 
> > CXXFLAGS=-O2 FFLAGS=' -O3 ' FCFLAGS=-O2 LDFLAGS=-m64 
> > PKG_CONFIG_PATH=/usr/openssl/3.1/lib/64/pkgconfig:/usr/mariadb/10.6/lib/amd64/pkgconfig:/usr/lib/amd64/pkgconfig:/usr/lib/pkgconfig
> >  
> > --prefix=/usr/gcc/10 --mandir=/usr/gcc/10/share/man 
> > --bindir=/usr/gcc/10/bin --libdir=/usr/gcc/10/lib 
> > --sbindir=/usr/gcc/10/sbin --sbindir=/usr/gcc/10/bin 
> > --libdir=/usr/gcc/10/lib --libexecdir=/usr/gcc/10/lib --host 
> > x86_64-pc-solaris2.11 --build x86_64-pc-solaris2.11 --target 
> > x86_64-pc-solaris2.11 --with-pkgversion='OpenIndiana 10.5.0-oi-1' 
> > --with-bugurl=https://bugs.openindiana.org --without-gnu-ld 
> > --with-ld=/usr/bin/ld 
> > --with-build-time-tools=/usr/gnu/x86_64-pc-solaris2.11/bin 
> > --disable-bootstrap 

Re: [OpenIndiana-discuss] gccgo crashes

[Carsten Grzemba via openindiana-discuss]

Am 20.10.23 03:21 schrieb "Goetz T. Fischer"  : 
> 
> hi,
> 
> gccgo keeps crashing. following are the gcc10 results but the same happened 
> with gcc13.
> as you can see even something as simple as "env" crashes. the system in 
> question has been updated about 
> an hour ago. i don't know whether it worked before or not.
> anyway here is some debugging:
> 
> mdb -e ::status /usr/gcc/10/bin/go ./core 
> debugging core file of go (64-bit) from openindiana
> file: /usr/gcc/10/bin/go
> initial argv: /usr/gcc/10/bin/go env
> threading model: native threads
> status: process terminated by SIGSEGV (Segmentation Fault), addr=8
> 
> mdb -e ::stack /usr/gcc/10/bin/go ./core 
> libgcc_s.so.1`uw_frame_state_for+0x451()
> libgcc_s.so.1`_Unwind_Backtrace+0x4b()
> libgo.so.16.0.0`backtrace_full+0x69()
> libgo.so.16.0.0`runtime_callers+0x66()
> libgo.so.16.0.0`runtime.getSiginfo+0x2b()
> libgo.so.16.0.0`runtime.sigtrampgo+0x414()
> libc.so.1`__sighndlr+6()
> libc.so.1`call_user_handler+0x1d1(12, 7fffaefa7ef0, 7fffaefa7b90)
> libc.so.1`sigacthandler+0xee(12, 7fffaefa7ef0, 7fffaefa7b80)
> 0x()
> libc.so.1`wait4+0xaa(217, 7fff857fe1ec, 0, c0001b8000)
> libgo.so.16.0.0`syscall.Wait4+0x3d()
> libgo.so.16.0.0`os.Process.wait+0xbf()
> libgo.so.16.0.0`os.Process.Wait+0x16()
> libgo.so.16.0.0`os..z2fexec.Cmd.Wait+0x44()
> libgo.so.16.0.0`os..z2fexec.Cmd.Run+0x28()
> libgo.so.16.0.0`os..z2fexec.Cmd.CombinedOutput+0xb4()
> cmd..z2fgo..z2finternal..z2fwork.Builder.gccSupportsFlag+0x52d()
> cmd..z2fgo..z2finternal..z2fwork.Builder.compilerCmd+0x372()
> cmd..z2fgo..z2finternal..z2fwork.Builder.GccCmd+0x90()
> cmd..z2fgo..z2finternal..z2fenvcmd.ExtraEnvVarsCostly+0x272()
> cmd..z2fgo..z2finternal..z2fenvcmd.runEnv+0x392()
> main.main+0x642()
> libgo.so.16.0.0`runtime.main+0x385()
> libgo.so.16.0.0`runtime.kickoff+0x77()
> libc.so.1`resumecontext()
> 
> 
> and here is trying to run the "hello world" example:
> 
> mdb -e ::status /usr/gcc/10/bin/go ./core
> debugging core file of go (64-bit) from openindiana
> file: /usr/gcc/10/bin/go
> initial argv: /usr/gcc/10/bin/go run .
> threading model: native threads
> status: process terminated by SIGSEGV (Segmentation Fault), addr=8
> 
> mdb -e ::stack /usr/gcc/10/bin/go ./core 
> libgcc_s.so.1`uw_frame_state_for+0x451()
> libgcc_s.so.1`_Unwind_Backtrace+0x4b()
> libgo.so.16.0.0`backtrace_full+0x69()
> libgo.so.16.0.0`runtime_callers+0x66()
> libgo.so.16.0.0`runtime.getSiginfo+0x2b()
> libgo.so.16.0.0`runtime.sigtrampgo+0x414()
> libc.so.1`__sighndlr+6()
> libc.so.1`call_user_handler+0x1d1(12, 7fffad877ef0, 7fffad877b90)
> libc.so.1`sigacthandler+0xee(12, 7fffad877ef0, 7fffad877b80)
> 0x()
> libc.so.1`wait4+0xaa(261, 7fff79ffc1ec, 0, c0002d)
> libgo.so.16.0.0`syscall.Wait4+0x3d()
> libgo.so.16.0.0`os.Process.wait+0xbf()
> libgo.so.16.0.0`os.Process.Wait+0x16()
> libgo.so.16.0.0`os..z2fexec.Cmd.Wait+0x44()
> libgo.so.16.0.0`os..z2fexec.Cmd.Run+0x28()
> libgo.so.16.0.0`os..z2fexec.Cmd.CombinedOutput+0xb4()
> cmd..z2fgo..z2finternal..z2fwork.Builder.gccgoToolID+0x3f7()
> cmd..z2fgo..z2finternal..z2fwork.Builder.buildActionID+0xf7e()
> cmd..z2fgo..z2finternal..z2fwork.Builder.build+0xdb()
> cmd..z2fgo..z2finternal..z2fwork.cmd..z2fgo..z2finternal..z2fwork..thunk0+9()
> cmd..z2fgo..z2finternal..z2fwork..1cmd..z2fgo..z2finternal..z2fwork.Builder.Do..func2+0xc0()
> cmd..z2fgo..z2finternal..z2fwork..1cmd..z2fgo..z2finternal..z2fwork.Builder.Do..func3+0x113()
> cmd..z2fgo..z2finternal..z2fwork.cmd..z2fgo..z2finternal..z2fwork..thunk9+0xa()
> libgo.so.16.0.0`runtime.kickoff+0x77()
> libc.so.1`resumecontext()
> 0x19c00012a258()
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 


for gcc12 can you replace the /usr/gcc/12/lib/amd64/libgo.so.21.0.0 with the 
attached lib in the link

https://space.toc.de/s/7FQm7pm76Kr

and test again. If this works I can provide a patch.

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

Re: [OpenIndiana-discuss] gccgo crashes

[Carsten Grzemba via openindiana-discuss]

Am 20.10.23 03:21 schrieb "Goetz T. Fischer"  : 
> 
> hi,
> 
> gccgo keeps crashing. following are the gcc10 results but the same happened 
> with gcc13.
> as you can see even something as simple as "env" crashes. the system in 
> question has been updated about 
> an hour ago. i don't know whether it worked before or not.
> anyway here is some debugging:
> 
> mdb -e ::status /usr/gcc/10/bin/go ./core 
> debugging core file of go (64-bit) from openindiana
> file: /usr/gcc/10/bin/go
> initial argv: /usr/gcc/10/bin/go env
> threading model: native threads
> status: process terminated by SIGSEGV (Segmentation Fault), addr=8
> 
> mdb -e ::stack /usr/gcc/10/bin/go ./core 
> libgcc_s.so.1`uw_frame_state_for+0x451()
> libgcc_s.so.1`_Unwind_Backtrace+0x4b()
> libgo.so.16.0.0`backtrace_full+0x69()
> libgo.so.16.0.0`runtime_callers+0x66()
> libgo.so.16.0.0`runtime.getSiginfo+0x2b()
> libgo.so.16.0.0`runtime.sigtrampgo+0x414()
> libc.so.1`__sighndlr+6()
> libc.so.1`call_user_handler+0x1d1(12, 7fffaefa7ef0, 7fffaefa7b90)
> libc.so.1`sigacthandler+0xee(12, 7fffaefa7ef0, 7fffaefa7b80)
> 0x()
> libc.so.1`wait4+0xaa(217, 7fff857fe1ec, 0, c0001b8000)
> 

c0001b8000 seems not to be a valid address, here is a pointer of struct rusage 
expected

> 
> 
> libgo.so.16.0.0`syscall.Wait4+0x3d()
> libgo.so.16.0.0`os.Process.wait+0xbf()
> libgo.so.16.0.0`os.Process.Wait+0x16()
> libgo.so.16.0.0`os..z2fexec.Cmd.Wait+0x44()
> libgo.so.16.0.0`os..z2fexec.Cmd.Run+0x28()
> libgo.so.16.0.0`os..z2fexec.Cmd.CombinedOutput+0xb4()
> cmd..z2fgo..z2finternal..z2fwork.Builder.gccSupportsFlag+0x52d()
> cmd..z2fgo..z2finternal..z2fwork.Builder.compilerCmd+0x372()
> cmd..z2fgo..z2finternal..z2fwork.Builder.GccCmd+0x90()
> cmd..z2fgo..z2finternal..z2fenvcmd.ExtraEnvVarsCostly+0x272()
> cmd..z2fgo..z2finternal..z2fenvcmd.runEnv+0x392()
> main.main+0x642()
> libgo.so.16.0.0`runtime.main+0x385()
> libgo.so.16.0.0`runtime.kickoff+0x77()
> libc.so.1`resumecontext()
> 
> 
> and here is trying to run the "hello world" example:
> 
> mdb -e ::status /usr/gcc/10/bin/go ./core
> debugging core file of go (64-bit) from openindiana
> file: /usr/gcc/10/bin/go
> initial argv: /usr/gcc/10/bin/go run .
> threading model: native threads
> status: process terminated by SIGSEGV (Segmentation Fault), addr=8
> 
> mdb -e ::stack /usr/gcc/10/bin/go ./core 
> libgcc_s.so.1`uw_frame_state_for+0x451()
> libgcc_s.so.1`_Unwind_Backtrace+0x4b()
> libgo.so.16.0.0`backtrace_full+0x69()
> libgo.so.16.0.0`runtime_callers+0x66()
> libgo.so.16.0.0`runtime.getSiginfo+0x2b()
> libgo.so.16.0.0`runtime.sigtrampgo+0x414()
> libc.so.1`__sighndlr+6()
> libc.so.1`call_user_handler+0x1d1(12, 7fffad877ef0, 7fffad877b90)
> libc.so.1`sigacthandler+0xee(12, 7fffad877ef0, 7fffad877b80)
> 0x()
> libc.so.1`wait4+0xaa(261, 7fff79ffc1ec, 0, c0002d)
> libgo.so.16.0.0`syscall.Wait4+0x3d()
> libgo.so.16.0.0`os.Process.wait+0xbf()
> libgo.so.16.0.0`os.Process.Wait+0x16()
> libgo.so.16.0.0`os..z2fexec.Cmd.Wait+0x44()
> libgo.so.16.0.0`os..z2fexec.Cmd.Run+0x28()
> libgo.so.16.0.0`os..z2fexec.Cmd.CombinedOutput+0xb4()
> cmd..z2fgo..z2finternal..z2fwork.Builder.gccgoToolID+0x3f7()
> cmd..z2fgo..z2finternal..z2fwork.Builder.buildActionID+0xf7e()
> cmd..z2fgo..z2finternal..z2fwork.Builder.build+0xdb()
> cmd..z2fgo..z2finternal..z2fwork.cmd..z2fgo..z2finternal..z2fwork..thunk0+9()
> cmd..z2fgo..z2finternal..z2fwork..1cmd..z2fgo..z2finternal..z2fwork.Builder.Do..func2+0xc0()
> cmd..z2fgo..z2finternal..z2fwork..1cmd..z2fgo..z2finternal..z2fwork.Builder.Do..func3+0x113()
> cmd..z2fgo..z2finternal..z2fwork.cmd..z2fgo..z2finternal..z2fwork..thunk9+0xa()
> libgo.so.16.0.0`runtime.kickoff+0x77()
> libc.so.1`resumecontext()
> 0x19c00012a258()
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] printer manager core dumps

[Carsten Grzemba via openindiana-discuss]

Am 13.10.23 02:06 schrieb "Goetz T. Fischer"  : 
> 
> hi there,
> 
> the printer manager always core dumps. it did so with the 2023.4 version and 
> still does so on a system 
> that was fully upgraded today.
> 
> maybe related is that cups doesn't recognize usb printers. the printer (oki 
> 4350 usb) correctly shows up 
> in the device list but cups' lpinfo -v doesn't show usb as path at all. cups' 
> usb driver file however 
> does exist.
> maybe i'm missing something like having to activate cups usb support or so. 
> anyway printer and box are 
> fine; both have been working under rhel 8.
> 
> as usual, any help is welcome ...
> 

Do you have a core file? Does core cupsd or cups-browsed? Can you send a 


# mdb -e ::status  
and 

# mdb -e ::stack  

Carsten
___
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

[Carsten Grzemba via openindiana-discuss]

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.

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

Re: [OpenIndiana-discuss] DKIM violationRe: VirtualBox status?

[Carsten Grzemba via openindiana-discuss]

Am 07.09.23 08:49 schrieb Aurélien Larcher  : 
> 
> 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?
> 
> 

These still needs rebuild with gcc10:
/usr/lib/64/libXdamage.so.1
/usr/lib/64/libxkbcommon-x11.so.0
/usr/lib/64/libxkbcommon.so.0
/usr/lib/64/libxcb-render-util.so.0
/usr/lib/64/libxcb-icccm.so.4


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

Re: [OpenIndiana-discuss] VirtualBox status?

[Carsten Grzemba via openindiana-discuss]

Am 07.09.23 08:49 schrieb Aurélien Larcher  : 
> 
> 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
> >
> 

I did some effort in the last days and the current status is

GCC10 builds always crash in C++ exception handling on 'throw S_OK' 

(Cheers to the C++ programmers, it - then - else is boring ;))
   

Well aware of the problem with the libstdc++ and libgcc_s mixup I tried to 
build with GCC12.
   
Builds with GCC12 I have the two issues:
- on one testenv I get the problem described in: 
https://www.virtualbox.org/ticket/18134
- the hosts system crashes in vboxdrv on startup a guest

> $C
fe00191c6a70 0xf43b8cb2()
fe00191c6b20 0xf43906e3()
fe00191c6b50 0xf4390804()
fe00191c6c00 supdrvIOCtl+0x15f2()
fe00191c6cc0 VBoxDrvSolarisIOCtl+0x187(260002, c0185687, 7fffaaa7ed10, 
202003, fe11bf29da68, fe00191c6e18)
fe00191c6d00 cdev_ioctl+0x3f(260002, c0185687, 7fffaaa7ed10, 202003, 
fe11bf29da68, fe00191c6e18)
fe00191c6d50 spec_ioctl+0x55(fe119e9db700, c0185687, 7fffaaa7ed10, 
202003, fe11bf29da68, fe00191c6e18, 0)
fe00191c6de0 fop_ioctl+0x40(fe119e9db700, c0185687, 7fffaaa7ed10, 
202003, fe11bf29da68, fe00191c6e18, 0)
fe00191c6f00 ioctl+0x144(b, c0185687, 7fffaaa7ed10)
fe00191c6f10 sys_syscall+0x17d()

This is similar described here:
https://illumos.topicbox.com/groups/omnios-discuss/T2c1cc2017f4a8d96-M634438a6a4d1b61d3ace014f/virtualbox-is-core-dumping

Set disable_smap=1 makes no difference.

Any hints?

If someone like to test the Virtualbox package 6.1.46 and the GCC12 runtilme is 
available here:
http://pkg.toc.de/userland


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

Re: [OpenIndiana-discuss] VirtualBox status?

[Carsten Grzemba via openindiana-discuss]

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 static 2022-11-16 18:00
> 

Re: [OpenIndiana-discuss] Problem with VirtualBox since upgrade today

[Carsten Grzemba via openindiana-discuss]

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 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
> 

 
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 7f

Re: [OpenIndiana-discuss] Problem with VirtualBox since upgrade today

[Carsten Grzemba via openindiana-discuss]

Am 12.07.23 16:51 schrieb Carsten Grzemba via openindiana-discuss  
: 
> 
> 
> 
> Am 12.07.23 14:38 schrieb russell : 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Hi Carsten
> > 
> > 
> > I can see in the truss I shared with Stephan that VirtualBox does in fact 
> > identify all the VMs as it lists opening the .vbox files per VM.
> > This is also works with VBoxManage list vms. 
> > 
> > 
> > Kind Regards
> > 
> > Russell
> > 
> > 
> > 
> 
>  
> So far I can see until now: 
>  
> 
>  
> VBoxManage: error: Failed to create the VirtualBox object!
> VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted 
> (extended info not available)
> VBoxManage: error: Most likely, the VirtualBox COM server is not 
> 
>  
> because the VBoxSVC crashs in sGenericFactory::CreateInstance 
> 
>  
> 
>  
> #19 0x0089b01a in ?? ()
> #20 0x7fffa0d22ce2 in nsGenericFactory::CreateInstance (this=0xb58b60, 
> aOuter=0x0, aIID=..., aResult=0x7fffaea0dd20) at 
> /ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/xpcom/glue/nsGenericFactory.cpp:82
> #21 0x7fffa0cbcc5f in nsComponentManagerImpl::CreateInstance 
> (this=0xb88cd0, aClass=..., aDelegate=0x0, aIID=..., aResult=0x7fffaea0dd20) 
> at 
> /ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/xpcom/components/nsComponentManager.cpp:1876
> #22 0x7fffa0604052 in ipcDConnectService::OnSetup (this=0xbe30d0, peer=1, 
> setup=0xb58c20, opLen=40) at 
> /ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:3729
> #23 0x7fffa0603ede in ipcDConnectService::OnIncomingRequest 
> (this=0xbe30d0, peer=1, op=0xb58c20, opLen=40) at 
> /ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:3700
> #24 0x7fffa0601aab in DConnectWorker::Run (this=0xb5a8a0) at 
> /ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:2979
> #25 0x7fffa0cd376c in nsThread::Main (arg=0xb6b450) at 
> /ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/xpcom/threads/nsThread.cpp:118
> #26 0x7fffa0d1fd71 in _pt_root (arg=0xbe5560) at 
> /ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:224
> #27 0x7fffa0d1feba in _pt_iprt_root (Thread=0xbe5610, pvUser=0xbe5560) at 
> /ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:272
> #28 0x7fffa00b25a4 in rtThreadMain (pThread=0xbe5610, NativeThread=4, 
> pszThreadName=0xbe5ee8 "nspr-2") at 
> /ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Runtime/common/misc/thread.cpp:727
> #29 0x7fffa0217384 in rtThreadNativeMain (pvArgs=0xbe5610) at 
> /ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Runtime/r3/posix/thread-posix.cpp:386
> #30 0x7fffaf401dc7 in _thrp_setup () from /lib/64/libc.so.1
> #31 0x7fffaf402110 in ?? () from /lib/64/libc.so.1
> #32 0x in ?? ()
> 
> 
>  
>  
> -- 
> Carsten
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 

 
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
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Problem with VirtualBox since upgrade today

[Carsten Grzemba via openindiana-discuss]

Am 12.07.23 14:38 schrieb russell  : 
> 
> 
>   
> 
> 
> 
>  
> Hi Carsten
>  
>  
> I can see in the truss I shared with Stephan that VirtualBox does in fact 
> identify all the VMs as it lists opening the .vbox files per VM.
>  This is also works with VBoxManage list vms. 
>  
>  
> Kind Regards
>  
> Russell
> 
>  
> 

 
So far I can see until now: 
 

 
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted 
(extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not 

 
because the VBoxSVC crashs in  sGenericFactory::CreateInstance   

 

 
#19 0x0089b01a in ?? ()
#20 0x7fffa0d22ce2 in nsGenericFactory::CreateInstance (this=0xb58b60, 
aOuter=0x0, aIID=..., aResult=0x7fffaea0dd20) at 
/ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/xpcom/glue/nsGenericFactory.cpp:82
#21 0x7fffa0cbcc5f in nsComponentManagerImpl::CreateInstance 
(this=0xb88cd0, aClass=..., aDelegate=0x0, aIID=..., aResult=0x7fffaea0dd20) at 
/ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/xpcom/components/nsComponentManager.cpp:1876
#22 0x7fffa0604052 in ipcDConnectService::OnSetup (this=0xbe30d0, peer=1, 
setup=0xb58c20, opLen=40) at 
/ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:3729
#23 0x7fffa0603ede in ipcDConnectService::OnIncomingRequest (this=0xbe30d0, 
peer=1, op=0xb58c20, opLen=40) at 
/ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:3700
#24 0x7fffa0601aab in DConnectWorker::Run (this=0xb5a8a0) at 
/ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:2979
#25 0x7fffa0cd376c in nsThread::Main (arg=0xb6b450) at 
/ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/xpcom/threads/nsThread.cpp:118
#26 0x7fffa0d1fd71 in _pt_root (arg=0xbe5560) at 
/ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:224
#27 0x7fffa0d1feba in _pt_iprt_root (Thread=0xbe5610, pvUser=0xbe5560) at 
/ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:272
#28 0x7fffa00b25a4 in rtThreadMain (pThread=0xbe5610, NativeThread=4, 
pszThreadName=0xbe5ee8 "nspr-2") at 
/ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Runtime/common/misc/thread.cpp:727
#29 0x7fffa0217384 in rtThreadNativeMain (pvArgs=0xbe5610) at 
/ws/grzemba/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Runtime/r3/posix/thread-posix.cpp:386
#30 0x7fffaf401dc7 in _thrp_setup () from /lib/64/libc.so.1
#31 0x7fffaf402110 in ?? () from /lib/64/libc.so.1
#32 0x in ?? ()


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

Re: [OpenIndiana-discuss] Problem with VirtualBox since upgrade today

[Carsten Grzemba via openindiana-discuss]

Am 11.07.23 20:32 schrieb russell  : 
> 
> Hi Stephan
> 
> I ran "truss -leaf -o /tmp/truss.vb VirtualBox" to try an understand why 
> my existing virtual machines are not detected then closed VirtualBox. 
> Checking the truss.vb I found 275223 error messages types :-
> 
>  13316 ENOENT 261610 EAGAIN 35 ESRCH 
>  42 ENXIO 132 ETIME 38 ENOTTY 
>  13 ENOMEM 8 EEXIST 6 
> EACCES 4 ECHILD 4 EPERM 
> 3 ERESTART 4 EBADF 6 EINVAL 
>  2 EINTR
> 
> I also got to SIGSEGV segmentation faults
> 
> 2432/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x0008 
> 2432/1: Received signal #11, SIGSEGV [default] 
> 2432/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x0008
> 
> Looking through the truss searching for my name I can see that 
> VirtualBox correctly opened all my VirtualBox VMs .vbox 
> files but was looking for /home/russell/.config/QtProject.conf found it, 
> but had access issues checking my file I found it owned by root:root 
> dated 23rd March 2021. I changed the permissions so I owned the file; 
> started VirtualBox (no change in respect of virtual machines not 
> appearing). However when I attempted to close VirtualBox I get the 
> following error "Failed to set the global VirtualBox extra data for key 
> GUI/LastWindowPosition to value { 2967,61,869,772}." and when I look at 
> the details I get get the following Callee RC:
> 
> 
>   
> 
> NS_ERROR_CALL_FAILED (0x800706BE)
> 
> I have to pkill VirtualBox as I am unable to stop it via the GUI.
> 
> Do you get something similar?
> 
> Kind Regards
> 
> Russell
> 
> 
> On 7/11/23 16:31, Stephan Althaus wrote:
> > 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
> 

 
I would recommend downsize and try to isolate the problem, start with 

 
$ VBoxManage list vms
 

 
 
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org

Re: [OpenIndiana-discuss] Intel HD Grapics 520 / ThinkPad T470

[Carsten Grzemba via openindiana-discuss]

Am 15.06.23 10:39 schrieb Olaf Bohlen  : 
> 
> Hi,
> 
> I'm running OI Hipster on a Lenovo T470 with Intel HD Graphics
> 520:
> 
> --8<---cut here---start->8---
> pci bus 0x cardnum 0x02 function 0x00: vendor 0x8086 device 0x1916
>  Intel Corporation Skylake GT2 [HD Graphics 520]
> --8<---cut here---end--->8---
> 
> However my X server only uses the VESA driver :/
> 
> The X Server log says:
> 
> --8<---cut here---start->8---
> [ 60.254] (--) PCI:*(0:0:2:0) 8086:1916:17aa:2245 rev 7, Mem @ 
> 0xeb00/16777216, 0xa000/268435456, I/O @ 0xe000/64
> [ 60.255] (II) LoadModule: "glx"
> [ 60.272] (II) Loading /usr/lib/xorg/modules/extensions/amd64/libglx.so
> [ 60.425] (II) Module glx: vendor="X.Org Foundation"
> [ 60.425] compiled for 1.19.7, module version = 1.0.0
> [ 60.425] ABI class: X.Org Server Extension, version 10.0
> [ 60.425] (==) Matched intel as autoconfigured driver 0
> [ 60.425] (==) Matched vesa as autoconfigured driver 1
> [ 60.425] (==) Assigned the driver to the xf86ConfigLayout
> [ 60.426] (II) LoadModule: "intel"
> [ 60.426] (II) Loading /usr/lib/xorg/modules/drivers/amd64/intel_drv.so
> [ 60.461] (II) Module intel: vendor="X.Org Foundation"
> [ 60.461] compiled for 1.19.5, module version = 2.99.917
> [ 60.461] Module class: X.Org Video Driver
> [ 60.461] ABI class: X.Org Video Driver, version 23.0
> [ 60.461] (II) LoadModule: "vesa"
> [ 60.461] (II) Loading /usr/lib/xorg/modules/drivers/amd64/vesa_drv.so
> [ 60.510] (II) Module vesa: vendor="X.Org Foundation"
> [ 60.510] compiled for 1.19.5, module version = 2.6.0
> [ 60.510] Module class: X.Org Video Driver
> [ 60.510] ABI class: X.Org Video Driver, version 23.0
> [ 60.510] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
>   i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
>   915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
>   Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
>   GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
> [ 60.511] (II) intel: Driver for Intel(R) HD Graphics
> [ 60.511] (II) intel: Driver for Intel(R) Iris(TM) Graphics
> [ 60.511] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
> [ 60.511] (II) VESA: driver for VESA chipsets: vesa
> [ 60.511] (++) using VT number 7
> 
> [ 60.591] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
> [ 60.591] (II) Loading sub module "vbe"
> [ 60.591] (II) LoadModule: "vbe"
> [ 60.592] (II) Loading /usr/lib/xorg/modules/amd64/libvbe.so
> [ 60.592] (II) Module vbe: vendor="X.Org Foundation"
> [ 60.592] compiled for 1.19.7, module version = 1.1.0
> [ 60.592] ABI class: X.Org Video Driver, version 23.0
> [ 60.592] (II) Loading sub module "int10"
> [ 60.592] (II) LoadModule: "int10"
> [ 60.592] (II) Loading /usr/lib/xorg/modules/amd64/libint10.so
> [ 60.613] (II) Module int10: vendor="X.Org Foundation"
> [ 60.613] compiled for 1.19.7, module version = 1.0.0
> [ 60.613] ABI class: X.Org Video Driver, version 23.0
> [ 60.613] (II) VESA(0): initializing int10
> [ 60.619] (II) VESA(0): Primary V_BIOS segment is: 0xc000
> [ 60.619] (II) VESA(0): VESA BIOS detected
> [ 60.620] (II) VESA(0): VESA VBE Version 3.0
> [ 60.620] (II) VESA(0): VESA VBE Total Mem: 32704 kB
> [ 60.620] (II) VESA(0): VESA VBE OEM: Intel(R) SKL/KBL Mobile/Desktop 
> Graphics Chipset Accelerated VGA BIOS
> [ 60.620] (II) VESA(0): VESA VBE OEM Software Rev: 0.0
> [ 60.644] (II) VESA(0): Creating default Display subsection in Screen section
>   "Default Screen Section" for depth/fbbpp 24/32
> [ 60.644] (==) VESA(0): Depth 24, (--) framebuffer bpp 32
> [ 60.644] (==) VESA(0): RGB weight 888
> [ 60.644] (==) VESA(0): Default visual is TrueColor
> [ 60.644] (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
> --8<---cut here---end--->8---
> 
> My understanding is that the Intel HD Graphics driver support,
> should also support my card. However might be our driver is too
> old.
> 
> Has someone here had success witht the Intel HD 520, or has some
> an idea how I could get it running?
> 
> Thank you,
> 
> Olaf
> 
> Hi Olaf,
> 

 
my Acer notebook uses also only vesa driver because the i915 driver do not 
support the Intel Graphics.

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

Re: [OpenIndiana-discuss] DKIM violation My Firefox tab has crashed

[Carsten Grzemba via openindiana-discuss]

Am 18.02.23 02:08 schrieb Gary Mills  : 
> 
> Whenever I tell Firefox to show me www.royalbank.com, and click on the
> Sign In box, it tells me that my tab just crashed. This behavior just
> started happening today. It happens before I get an opportunity to
> authenticate. I get the same thing on a newly-upgraded BE as I do
> from one that's about a year old. The curious thing is that Firefox
> on Linux works perfectly with this same URL. That's the only way I
> can access my bank now.
> 
> I assume that the bank's web site is doing something that does not
> work on OI. Could it be something simple, like a missing library? Is
> there any way to get a traceback of that tab crash or to send one to a
> developer?
> 
> 

So far I can test it it works with the current firefox 102.7.0esr for me  (and 
also 109, 91.2.0esr) .
 -- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] DKIM violation My Firefox tab has crashed

[Carsten Grzemba via openindiana-discuss]

Am 18.02.23 02:08 schrieb Gary Mills  : 
> 
> Whenever I tell Firefox to show me www.royalbank.com, and click on the
> Sign In box, it tells me that my tab just crashed. This behavior just
> started happening today. It happens before I get an opportunity to
> authenticate. I get the same thing on a newly-upgraded BE as I do
> from one that's about a year old. The curious thing is that Firefox
> on Linux works perfectly with this same URL. That's the only way I
> can access my bank now.
> 
> I assume that the bank's web site is doing something that does not
> work on OI. Could it be something simple, like a missing library? Is
> there any way to get a traceback of that tab crash or to send one to a
> developer?
> 
> 
Have you attempt use of website with new profile also? Perhaps there are some 
confusing things like cookies stored in the profile which let the tab crash.
 -- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] DKIM violationRe: OI on HP Gen 10 Microserver

[Carsten Grzemba via openindiana-discuss]

Am 16.02.23 14:28 schrieb Michelle  : 
> 
> Hi Russell,
> 
> That's great. Cheers for that.
> 
> Is there any advice on running a server for years from a USB stick
> please?
> 
> I'm thinking of an SSD hard drive on a USB adaptor instead. Not sure
> yet. Grateful for any thoughts and information that could help me make
> up my mind.
> 
> Michelle.
> 
> On Thu, 2023-02-16 at 13:13 +, russell wrote:
> > Hi Michelle
> > 
> > If you go here you can download a Live USB image to boot from 
> > https://www.openindiana.org/download/
> > 
> > Kind Regards
> > 
> > Russell
> >
> 
Until https://www.illumos.org/issues/15270 is fixed, it is only possible to 
boot from USB device with Live or Install image, not installed rpool.

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

Re: [OpenIndiana-discuss] DKIM violationRe: GIMP issues loading jpg and png

[Carsten Grzemba via openindiana-discuss]

Am 19.01.23 07:18 schrieb Carsten Grzemba via openindiana-discuss  
: 
> 
> 
> 
> Am 18.01.23 18:25 schrieb Andreas Wacknitz : 
> > 
> > Am 18.01.23 um 16:05 schrieb Udo Grabowski (IMK):
> > >On 17/01/2023 07:32, russell wrote:
> > >>...
> > >>GIMP Message
> > >>
> > >>Plug-in crashed: "file-jpeg"
> > >>(/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg)
> > >>...
> > >>
> > >>GIMP Message
> > >>
> > >>...
> > >>Plug-in crashed: "file-png"
> > >>(/usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png)
> > >>...
> > >>
> > >>Has anyone else noticed this?
> > >>
> > >
> > >Yes, same problem here. Both plugins crash with a segfault, while
> > >a gif-file loads without problems:
> > >
> > >ts(~) gimp
> > >GIMP-Message: Some fonts failed to load:
> > >- /usr/share/gimp/2.0/fonts/
> > >
> > >Plug-in "gtkam-gimp"
> > >(/usr/lib/amd64/gimp/2.0/plug-ins/gtkam-gimp) is installing procedure
> > >"gtkam-capture" with a full menu path "/File/Acquire/Capture
> > >from Camera..." as menu label, this deprecated and will be an error in
> > >GIMP 3.0
> > >Plug-in "gtkam-gimp"
> > >(/usr/lib/amd64/gimp/2.0/plug-ins/gtkam-gimp) is installing procedure
> > >"gtkam-load" with a full menu path "/File/Acquire/Load from
> > >Camera..." as menu label, this deprecated and will be an error in GIMP
> > >3.0
> > >/usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error:
> > >Segmentation Fault
> > >/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error:
> > >Segmentation Fault
> > >/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error:
> > >Segmentation Fault
> > >/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error:
> > >Segmentation Fault
> > >/usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error:
> > >Segmentation Fault
> > >/usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error:
> > >Segmentation Fault
> > >/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error:
> > >Segmentation Fault
> > >/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error:
> > >Segmentation Fault
> > >/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error:
> > >Segmentation Fault
> > >gimp: GEGL-WARNING:
> > >(../../gegl-0.4.40/gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy:
> > >runtime check failed: (g_queue_is_empty (_queue))
> > >eEeek! 14 GeglBuffers leaked
> > >
> > >___
> > >openindiana-discuss mailing list
> > >openindiana-discuss@openindiana.org
> > >https://openindiana.org/mailman/listinfo/openindiana-discuss
> > I can confirm the problem but alas I don't get a core file which would
> > be helpful to locate the problem.
> > Can anybody provide a core dump?
> > 
> 
>  
> Gimp do not dump. It has a code for backtracing but not for OI. 
> 
>  
> That is what I could grab with gdb 
> 
>  
> Thread 2 received signal SIGSEGV, Segmentation fault.
> 0x7fffb070 in ?? ()
> (gdb) bt
> #0 0x7fffb070 in ()
> #1 0x7fffaf3f5e35 in _Unwind_ForcedUnwind_Body () at /lib/64/libc.so.1
> #2 0x7fffaf3f608f in _Unwind_Resume () at /lib/64/libc.so.1
> #3 0x7fffa2cb81fc in 
> Exiv2::XmpProperties::nsInfo(std::__cxx11::basic_string std::char_traits, std::allocator > const&) [clone .cold] ()
>  at /usr/lib/64/libexiv2.so.27
> #4 0x7fffa2cb3d58 in 
> Exiv2::XmpProperties::ns(std::__cxx11::basic_string std::char_traits, std::allocator > const&) ()
>  at /usr/lib/64/libexiv2.so.27
> #5 0x7fffa2ef6262 in gexiv2_metadata_register_xmp_namespace ()
>  at /usr/lib/64/libgexiv2.so.2
> #6 0x7fffa3458baf in gimp_metadata_class_init (klass=0x5c74a0)
>  at 
> /ws/grzemba/oi-userland/components/image/gimp/gimp-2.10.32/libgimpbase/gimpmetadata.c:205
> #7 0x7fffa3458baf in gimp_metadata_class_intern_init (klass=0x5c74a0)
>  at 
> /ws/grzemba/oi-userland/components/image/gimp/gimp-2.10.32/libgimpbase/gimpmetadata.c:199
> #8 0x7fffac1f3132 in g_type_class_ref.localalias ()
>  at /usr/lib/64/libgobject-2.0.so.0
> #9 0x7fffac1d2288 in g_object_new_with_properties ()
>  at /usr/lib/64/libgobject-2.0.so.0
> #10 0x7fffac1d31a9 in g_object_new 

[OpenIndiana-discuss] marco crash in XResQueryClientIds

[Carsten Grzemba via openindiana-discuss]

I got reports that latest marco 1.26.1 crashs here:


core '/var/cores/core.marco.3294' of 3294: marco
- thread# 1 / lwp# 1 -
 7fffaf37d156 _free_unlocked () + 16
 7fffa373249a XResQueryClientIds () + fa
 7fffa382f740 reload_net_wm_pid () + 40
 7fffa382fc0d meta_window_reload_properties_from_xwindow () + fd
 7fffa383d893 meta_window_new_with_attrs.part.39 () + 593
 7fffa382532b meta_screen_manage_all_windows () + 5b
 7fffa380f920 meta_display_open () + c80
 004037d5 main () + 6a5
 00402ec7 _start_crt () + 87
 00402e28 _start () + 18


Anyone else see this?
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] DKIM violationRe: GIMP issues loading jpg and png

[Carsten Grzemba via openindiana-discuss]

Am 18.01.23 18:25 schrieb Andreas Wacknitz  : 
> 
> Am 18.01.23 um 16:05 schrieb Udo Grabowski (IMK):
> >On 17/01/2023 07:32, russell wrote:
> >>...
> >>GIMP Message
> >>
> >>Plug-in crashed: "file-jpeg"
> >>(/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg)
> >>...
> >>
> >>GIMP Message
> >>
> >>...
> >>Plug-in crashed: "file-png"
> >>(/usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png)
> >>...
> >>
> >>Has anyone else noticed this?
> >>
> >
> >Yes, same problem here. Both plugins crash with a segfault, while
> >a gif-file loads without problems:
> >
> >ts(~) gimp
> >GIMP-Message: Some fonts failed to load:
> >- /usr/share/gimp/2.0/fonts/
> >
> >Plug-in "gtkam-gimp"
> >(/usr/lib/amd64/gimp/2.0/plug-ins/gtkam-gimp) is installing procedure
> >"gtkam-capture" with a full menu path "/File/Acquire/Capture
> >from Camera..." as menu label, this deprecated and will be an error in
> >GIMP 3.0
> >Plug-in "gtkam-gimp"
> >(/usr/lib/amd64/gimp/2.0/plug-ins/gtkam-gimp) is installing procedure
> >"gtkam-load" with a full menu path "/File/Acquire/Load from
> >Camera..." as menu label, this deprecated and will be an error in GIMP
> >3.0
> >/usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error:
> >Segmentation Fault
> >/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error:
> >Segmentation Fault
> >/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error:
> >Segmentation Fault
> >/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error:
> >Segmentation Fault
> >/usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error:
> >Segmentation Fault
> >/usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error:
> >Segmentation Fault
> >/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error:
> >Segmentation Fault
> >/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error:
> >Segmentation Fault
> >/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error:
> >Segmentation Fault
> >gimp: GEGL-WARNING:
> >(../../gegl-0.4.40/gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy:
> >runtime check failed: (g_queue_is_empty (_queue))
> >eEeek! 14 GeglBuffers leaked
> >
> >___
> >openindiana-discuss mailing list
> >openindiana-discuss@openindiana.org
> >https://openindiana.org/mailman/listinfo/openindiana-discuss
> I can confirm the problem but alas I don't get a core file which would
> be helpful to locate the problem.
> Can anybody provide a core dump?
> 

 
Gimp do not dump. It has a code for backtracing but not for OI. 

 
That is what I could grab with gdb 

 
Thread 2 received signal SIGSEGV, Segmentation fault.
0x7fffb070 in ?? ()
(gdb) bt
#0 0x7fffb070 in ()
#1 0x7fffaf3f5e35 in _Unwind_ForcedUnwind_Body () at /lib/64/libc.so.1
#2 0x7fffaf3f608f in _Unwind_Resume () at /lib/64/libc.so.1
#3 0x7fffa2cb81fc in 
Exiv2::XmpProperties::nsInfo(std::__cxx11::basic_string, std::allocator > const&) [clone .cold] ()
 at /usr/lib/64/libexiv2.so.27
#4 0x7fffa2cb3d58 in 
Exiv2::XmpProperties::ns(std::__cxx11::basic_string, std::allocator > const&) ()
 at /usr/lib/64/libexiv2.so.27
#5 0x7fffa2ef6262 in gexiv2_metadata_register_xmp_namespace ()
 at /usr/lib/64/libgexiv2.so.2
#6 0x7fffa3458baf in gimp_metadata_class_init (klass=0x5c74a0)
 at 
/ws/grzemba/oi-userland/components/image/gimp/gimp-2.10.32/libgimpbase/gimpmetadata.c:205
#7 0x7fffa3458baf in gimp_metadata_class_intern_init (klass=0x5c74a0)
 at 
/ws/grzemba/oi-userland/components/image/gimp/gimp-2.10.32/libgimpbase/gimpmetadata.c:199
#8 0x7fffac1f3132 in g_type_class_ref.localalias ()
 at /usr/lib/64/libgobject-2.0.so.0
#9 0x7fffac1d2288 in g_object_new_with_properties ()
 at /usr/lib/64/libgobject-2.0.so.0
#10 0x7fffac1d31a9 in g_object_new () at /usr/lib/64/libgobject-2.0.so.0
#11 0x7fffa3459dc1 in gimp_metadata_load_from_file 
(file=file@entry=0x56f160, error=error@entry=0x0)
 at 
/ws/grzemba/oi-userland/components/image/gimp/gimp-2.10.32/libgimpbase/gimpmetadata.c:992
#12 0x7fff9fe5e25b in gimp_image_metadata_load_prepare (image_ID=, mime_type=mime_type@entry=0x40ca7b "image/png", file=file@entry=0x56f160, 
error=error@entry=0x0)
 at 
/ws/grzemba/oi-userland/components/image/gimp/gimp-2.10.32/libgimp/gimpimagemetadata.c:86
#13 0x0040a428 in run (name=, nparams=3, param=0x4594b0, 
nreturn_vals=0x7fffb654, return_vals=)
 at 
/ws/grzemba/oi-userland/components/image/gimp/gimp-2.10.32/plug-ins/common/file-png.c:481
#14 0x7fffa17f7e11 in gimp_proc_run (proc_run=)
 at 
/ws/grzemba/oi-userland/components/image/gimp/gimp-2.10.32/libgimp/gimp.c---Type
  to continue, or q  to quit---
:2460
#15 0x7fffa17f7e11 in gimp_loop ()
 at 
/ws/grzemba/oi-userland/components/image/gimp/gimp-2.10.32/libgimp/gimp.c:2272
#16 0x7fffa17f7e11 in gimp_main (info=, argc=, argv=)
 at 
/ws/grzemba/oi-userland/components/image/gimp/gimp-2.10.32/libgimp/gimp.c:678
#17 0x004063f7 

Re: [OpenIndiana-discuss] GIMP issues loading jpg and png

[Carsten Grzemba via openindiana-discuss]

Am 18.01.23 16:05 schrieb "Udo Grabowski (IMK)"  : 
> 
> On 17/01/2023 07:32, russell wrote:
> >...
> >GIMP Message
> >
> >Plug-in crashed: "file-jpeg"
> >(/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg)
> >...
> >
> >GIMP Message
> >
> >...
> >Plug-in crashed: "file-png"
> >(/usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png)
> >...
> >
> >Has anyone else noticed this?
> >
> 
> Yes, same problem here. Both plugins crash with a segfault, while
> a gif-file loads without problems:
> 
> ts(~) gimp
> GIMP-Message: Some fonts failed to load:
> - /usr/share/gimp/2.0/fonts/
> 
> Plug-in "gtkam-gimp"
> (/usr/lib/amd64/gimp/2.0/plug-ins/gtkam-gimp) is installing procedure 
> "gtkam-capture" with a full menu path "/File/Acquire/Capture from 
> Camera..." as menu label, this deprecated and will be an error in GIMP 3.0
> Plug-in "gtkam-gimp"
> (/usr/lib/amd64/gimp/2.0/plug-ins/gtkam-gimp) is installing procedure 
> "gtkam-load" with a full menu path "/File/Acquire/Load from 
> Camera..." as menu label, this deprecated and will be an error in GIMP 3.0
> /usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error: Segmentation 
> Fault
> /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: 
> Segmentation Fault
> /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: 
> Segmentation Fault
> /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: 
> Segmentation Fault
> /usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error: Segmentation 
> Fault
> /usr/lib/amd64/gimp/2.0/plug-ins/file-png/file-png: fatal error: Segmentation 
> Fault
> /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: 
> Segmentation Fault
> /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: 
> Segmentation Fault
> /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg: fatal error: 
> Segmentation Fault
> gimp: GEGL-WARNING: 
> (../../gegl-0.4.40/gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy:
>  runtime check failed: (g_queue_is_empty (_queue))
> eEeek! 14 GeglBuffers leaked
> 
> 

 
and: 
 

Jan 18 16:37:24 notebookcg2 genunix: [ID 533030 kern.notice] NOTICE: 
file-jpeg[5145] attempt to execute code on stack by uid 1005
Jan 18 16:37:25 notebookcg2 genunix: [ID 533030 kern.notice] NOTICE: 
file-jpeg[5146] attempt to execute code on stack by uid 1005
Jan 18 16:37:33 notebookcg2 genunix: [ID 533030 kern.notice] NOTICE: 
file-jpeg[5147] attempt to execute code on stack by uid 1005
Jan 18 16:39:09 notebookcg2 genunix: [ID 533030 kern.notice] NOTICE: 
file-jpeg[5162] attempt to execute code on stack by uid 1005
 



-- 

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

Re: [OpenIndiana-discuss] How should a disk partition layout looks like

[Carsten Grzemba via openindiana-discuss]

Am 06.01.23 11:43 schrieb Toomas Soome  : 
> 
> 
> 
> > On 6. Jan 2023, at 12:06, Carsten Grzemba via openindiana-discuss 
> >  wrote:
> > 
> > I have a disk installed with Openindiana and installboot shows bootloader 
> > at cxt0d0s1 and has not cxt0d0p1
> > The disk will not recognized by BIOS for boot but it boots if selected in 
> > loader.
> > 
> > On other resources shows EFI boot files on cxt0d0p1.
> > 
> > Is p1 partition necessary for boot?
> > How looks like a correct disk partitioning nowadys?
> > 
> 
> sX is partition from either GPT or VTOC
> 
> p0 is whole disk
> p1-p4 are MBR primary partitions and p5.. are extended.
> 
> With GPT you have MBR in absolute sector 0 and only one partition defined 
> (EFI), this is “protective” MBR and meant to tell non-GPT aware partition 
> programs that you have partition defined. GPT itself is on absolute sector 1 
> and followed by partition array.
> 
> Classic Solaris x86 partitioning is MBR + VTOC, you are supposed to have one 
> Solaris2 MBR primary partition per disk and on that partition you have VTOC. 
> 
> With zpool “whole disk” setup, you will get GPT partitioning, with s0[, s1] 
> and s8 defined (GPT does not allow overlapping partitions). Depending if 
> zpool create -B was used, you may or may not have efi system partition.
> 
> MBR + VTOC scheme is assuming you have single Solaris2 MBR (primary) 
> partition, in it you have VTOC table and it has to be manually described 
> (usually has root, backup (s2) and boot slices).
> 
> rgds,
> toomas
> 

 
I have: 

 Total disk size is 60799 cylinders Cylinder size is 64260 (512 byte) blocks 
Cylinders Partition Status Type Start End Length % = == 
 = === == === 1 EFI 0 60799 60800 100 # prtvtoc 
/dev/rdsk/c3t0d0s0
* /dev/rdsk/c3t0d0s0 EFI partition map
*
* Dimensions:
* 512 bytes/sector
* 3906963456 sectors
* 3906963389 accessible sectors
*
* Flags:
* 1: unmountable
* 10: read-only
*
* Unallocated space:
* First Sector Last
* Sector Count Sector
* 34 222 255
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory 0 12 00 256 524288 
524543 1 4 00 524544 3906422495 3906947038 8 11 00 3906947039 16384 3906963422
 
 

but installboot show boot files on s1



# installboot -V -i /dev/rdsk/c3t0d0s1
PMBR block from /dev/rdsk/c3t0d0p0:
Format: loader (illumos)
Signature: 0xaa55 (valid)
UniqueMBRDiskSignature: 0x5f107
Loader STAGE1_STAGE2_LBA: 524544
Loader STAGE1_STAGE2_SIZE: 1
Loader STAGE1_STAGE2_UUID: f24d9e68-cfe1-6158-8448-dc2a119643a3 VBR block from 
/dev/rdsk/c3t0d0s1:
Format: loader (illumos)
Signature: 0xaa55 (valid)
UniqueMBRDiskSignature: 0
Loader STAGE1_STAGE2_LBA: 525568
Loader STAGE1_STAGE2_SIZE: 279
Loader STAGE1_STAGE2_UUID: f24d9e68-cfe1-6158-8448-dc2a119643a3 Boot block from 
/dev/rdsk/c3t0d0s1:
Boot Block Extended Info Header: magic: EXTINFO version: 1 flags: 0 extended 
version string offset: 71 extended version string size: 16 hashing type: 1 
(MD5) hash offset: 54 hash size: 16
Extended version string: 1.1-2022.09.04.1
MD5 hash: cadb10776e17f7ff8d53653ae3b8e9c2 # installboot -V -i 
/dev/rdsk/c3t0d0s2
open: I/O error
# installboot -V -i /dev/rdsk/c3t0d0s0
Booting pcfs from EFI labeled disks requires the boot partition.

Is s1 the correct location? Should BIOS recognizes the boot disk?


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

[OpenIndiana-discuss] How should a disk partition layout looks like

[Carsten Grzemba via openindiana-discuss]

I have a disk installed with Openindiana and installboot shows bootloader at 
cxt0d0s1 and has not cxt0d0p1
The disk will not recognized by BIOS for boot but it boots if selected in 
loader.

On other resources shows EFI boot files on cxt0d0p1.

Is p1 partition necessary for boot?
How looks like a correct disk partitioning nowadys?

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

Re: [OpenIndiana-discuss] question about HAL, DBUS and upowerd

[Carsten Grzemba via openindiana-discuss]

Am 15.11.22 18:40 schrieb Carsten Grzemba via openindiana-discuss  
: 
> 
> Recently we fixed a problem with HAL and newer glib versions 
> 
> https://www.illumos.org/issues/15025
> 
> Now I see that on current OI the notifications for mate-power-manager no long 
> work. So the battery and the AC adapter state in mate-panel not updated 
> anymore. If I disconnect the AC adapter HAL changed the properties of 
> 
> /org/freedesktop/Hal/devices/pseudo/acpi_drv_0_battery0_0. This I can check 
> with
> 
> lshal -l -u /org/freedesktop/Hal/devices/pseudo/acpi_drv_0_battery0_0
> 
> But there is no signaling for mate-power-manager to see
> 
> 'dbus-monitor --system' shows events:
> 
> signal time=1668508780.607616 sender=:1.6 -> destination=(null destination) 
> serial=245 path=/org/freedesktop/Hal/devices/pseudo/acpi_drv_0_battery0_0; 
> interface=org.freedeskt
> op.Hal.Device; member=PropertyModified
>  int32 1
>  array [
>  struct {
>  string "battery.rechargeable.is_charging"
>  boolean false
>  boolean false
>  }
>  ]
> signal time=1668508780.607884 sender=:1.6 -> destination=(null destination) 
> serial=246 path=/org/freedesktop/Hal/devices/pseudo/acpi_drv_0_battery0_0; 
> interface=org.freedeskt
> op.Hal.Device; member=PropertyModified
>  int32 1
>  array [
>  struct {
>  string "battery.rechargeable.is_discharging"
>  boolean false
>  boolean false
>  }
>  ]
> signal time=1668508780.608317 sender=:1.6 -> destination=(null destination) 
> serial=247 path=/org/freedesktop/Hal/devices/pseudo/acpi_drv_0_battery0_0; 
> interface=org.freedeskt
> op.Hal.Device; member=PropertyModified
>  int32 1
>  array [
>  struct {
>  string "battery.reporting.current"
>  boolean false
>  boolean false
>  }
>  ]
> 
> 
> A sender :1.6 signals the change of power state. 
> 
> 
> Who is the sender :1.6 on DBUS? dbus-send ListNames shows me some servies 
> with names and some with only :1.numbers
> 
> On the former working setup I see event from UPower
> 
> signal time=1668508780.612616 sender=:1.5 -> destination=(null destination) 
> serial=49 path=/org/freedesktop/UPower/devices/battery_acpi_drv_0_battery0; 
> interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
>  string "org.freedesktop.UPower.Device"
>  array [
>  dict entry(
>  string "UpdateTime"
>  variant �� uint64 1668508780
>  )
>  dict entry(
>  string "Capacity"
>  variant double 72.7415
>  )
>  dict entry(
>  string "EnergyRate"
>  variant double 8.558
>  )
>  dict entry(
>  string "Energy"
>  variant double 17.626
>  )
>  dict entry(
>  string "IconName"
>  variant string "battery-full-symbolic"
>  )
>  dict entry(
>  string "TimeToEmpty"
>  variant int64 7414
>  )
>  dict entry(
>  string "Percentage"
>  variant double 72.7415
>  )
>  dict entry(
>  string "State"
>  variant uint32 2
>  )
>  ]
>  array [
>  ]
> 
> 
> This event I am missing on the current OI.
> 
> 
> On the fomer working setup I see with dbus-monitor --session also
> 
> method call time=1668508728.086076 sender=:1.19 -> destination=:1.42 
> serial=20 path=/org/freedesktop/Notifications; 
> interface=org.freedesktop.Notifications; member=Notify
>  string "Energieverwaltung"
>  uint32 0
>  string "gpm-battery-080"
>  string "Akku entlädt"
>  string "2 Stunden 12 Minuten der Akkuladung verbleibend (73%)"
>  array [
>  ]
>  array [
>  dict entry(
>  string "urgency"
>  variant byte 1
>  )
>  ]
>  int32 3
> 
> 
> On the current setup this method call I can't see with dbus-monitor --session.
> 
> The summary: the upowerd updates normally all 20s the battery properties and 
> sends notifications to mate-panel. But in the moment it does not. 
> 
> 
> Any hints?
> 
> Many Thanks!
> -- 
> 
> Carsten
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 

  
Found the reason, it similar to https://www.illumos.org/issues/15025 and 
https://github.com/OpenIndiana/oi-userland/pull/9932 created.

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

[OpenIndiana-discuss] question about HAL, DBUS and upowerd

[Carsten Grzemba via openindiana-discuss]

Recently we fixed a problem with HAL and newer glib versions 

https://www.illumos.org/issues/15025

Now I see that on current OI the notifications for mate-power-manager no long 
work. So the battery and the AC adapter state in mate-panel not updated 
anymore. If I disconnect the AC adapter HAL changed the properties of 

/org/freedesktop/Hal/devices/pseudo/acpi_drv_0_battery0_0. This I can check with

lshal -l -u /org/freedesktop/Hal/devices/pseudo/acpi_drv_0_battery0_0

But there is no signaling for mate-power-manager to see

'dbus-monitor --system' shows events:

signal time=1668508780.607616 sender=:1.6 -> destination=(null destination) 
serial=245 path=/org/freedesktop/Hal/devices/pseudo/acpi_drv_0_battery0_0; 
interface=org.freedeskt
op.Hal.Device; member=PropertyModified
 int32 1
 array [
 struct {
 string "battery.rechargeable.is_charging"
 boolean false
 boolean false
 }
 ]
signal time=1668508780.607884 sender=:1.6 -> destination=(null destination) 
serial=246 path=/org/freedesktop/Hal/devices/pseudo/acpi_drv_0_battery0_0; 
interface=org.freedeskt
op.Hal.Device; member=PropertyModified
 int32 1
 array [
 struct {
 string "battery.rechargeable.is_discharging"
 boolean false
 boolean false
 }
 ]
signal time=1668508780.608317 sender=:1.6 -> destination=(null destination) 
serial=247 path=/org/freedesktop/Hal/devices/pseudo/acpi_drv_0_battery0_0; 
interface=org.freedeskt
op.Hal.Device; member=PropertyModified
 int32 1
 array [
 struct {
 string "battery.reporting.current"
 boolean false
 boolean false
 }
 ]


A sender :1.6 signals the change of power state. 


Who is the sender :1.6 on DBUS? dbus-send ListNames shows me some servies with 
names and some with only :1.numbers

On the former working setup I see event from UPower

signal time=1668508780.612616 sender=:1.5 -> destination=(null destination) 
serial=49 path=/org/freedesktop/UPower/devices/battery_acpi_drv_0_battery0; 
interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
 string "org.freedesktop.UPower.Device"
 array [
 dict entry(
 string "UpdateTime"
 variant �� uint64 1668508780
 )
 dict entry(
 string "Capacity"
 variant double 72.7415
 )
 dict entry(
 string "EnergyRate"
 variant double 8.558
 )
 dict entry(
 string "Energy"
 variant double 17.626
 )
 dict entry(
 string "IconName"
 variant string "battery-full-symbolic"
 )
 dict entry(
 string "TimeToEmpty"
 variant int64 7414
 )
 dict entry(
 string "Percentage"
 variant double 72.7415
 )
 dict entry(
 string "State"
 variant uint32 2
 )
 ]
 array [
 ]


This event I am missing on the current OI.


On the fomer working setup I see with dbus-monitor --session also

method call time=1668508728.086076 sender=:1.19 -> destination=:1.42 serial=20 
path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications; 
member=Notify
 string "Energieverwaltung"
 uint32 0
 string "gpm-battery-080"
 string "Akku entlädt"
 string "2 Stunden 12 Minuten der Akkuladung verbleibend (73%)"
 array [
 ]
 array [
 dict entry(
 string "urgency"
 variant byte 1
 )
 ]
 int32 3


On the current setup this method call I can't see with dbus-monitor --session.

The summary: the upowerd updates normally all 20s the battery properties and 
sends notifications to mate-panel. But in the moment it does not. 


Any hints?

Many Thanks!
-- 

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

Re: [OpenIndiana-discuss] mate-screensaver

[Carsten Grzemba via openindiana-discuss]

I could to manage to build the mate-screensaver for OI. I use the PAM-helper 
style for lock-unlock the screen. In this kind the seteuid nightmare for check 
password is somewhat mitigated. Only the pwd-helper has to set the setuid bit. 
   

Who like to test this build can find the package on: http://pkg.toc.de/userland



pkg set-publisher -g http://pkg.toc.de/userland openindiana.org

pkg install mate-screensaver



recipe: 
https://github.com/cgrzemba/oi-userland/tree/mate-screensaver/components/desktop/mate/mate-screensaver

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

[OpenIndiana-discuss] mate-screensaver

[Carsten Grzemba via openindiana-discuss]

I am interested to replace the xscreensaver with the mate-screensaver. Our 
Xscreensaver is quite old and the current will not work out of the box. On 
Xscreensaver the PAM code was patched to use BSM even so it supports Solaris.
mate-screensaver compiles on OI. 

mate-screensaver PAM code is reworked but I seems it will not work on Illumos. 
Solaris support seems to be removed.

Is anyone already working on this? Or has experience with the PAM setup for 
mate-screensaver?

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

Re: [OpenIndiana-discuss] Problem with Audio in Firefox

[Carsten Grzemba via openindiana-discuss]

Am 26.07.22 12:21 schrieb russell  : 
> 
> HI
> 
> When I perform an update I always create a new BE.
> I performed a update on the 2022-07-03 and audio playback in Firefox was 
> fine.
> On the 2022-07-20 I performed an update, while VLC played audio okay, 
> Firefox would not play Youtube audio.
> I tried further updates on the 2022-07-23 and 2022-07-25 audio playback 
> via Firefox was still broken but VLC was fine.
> Has anyone else experienced this?
> 
> Russell
> 

 
I did an update to the latest bits incl. FF@102.0.1 on my Acer TravelMate 5760 
and 
 
youtube audio is working in the same kind like VLC.
 

 
the FF process has loaded the libs eg. 
 
 
/usr/lib/amd64/libpulse.so.0.21.1
/usr/lib/amd64/pulseaudio/libpulsecommon-13.0.so
/usr/lib/amd64/libsndfile.so.1.0.31
/usr/lib/amd64/libFLAC.so.8.3.0

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

Re: [OpenIndiana-discuss] DKIM violationRe: DKIM violationRe: libwww-perl-524 dependency problem

[Carsten Grzemba via openindiana-discuss]

Am 27.07.22 12:05 schrieb Aurélien Larcher  : 
> 
> On Wed, Jul 27, 2022 at 11:26 AM Carsten Grzemba via openindiana-discuss <
> openindiana-discuss@openindiana.org> wrote:
> 
> >
> >
> > Am 27.07.22 11:06 schrieb Aurélien Larcher :
> > >
> > > On Wed, Jul 27, 2022 at 9:53 AM Carsten Grzemba via openindiana-discuss <
> > > openindiana-discuss@openindiana.org> wrote:
> > >
> > > > If libwww-perl-524 is installed it is not possible to update
> > xscreensaver
> > > > and others because the dependency for
> > > >
> > > > library/perl-5/encode-locale-524 cannot longer resolved.
> > > > This package is obsoleted now.
> > >
> > >
> > > > Can anyone fix this?
> > > >
> > >
> > > There is seemingly no problem with the package dependencies, xscreensaver
> > > does not depend on perl-524 anymore.
> > > Could you try installing/updating specific package versions?
> > >
> > > I have noticed that pkg is sometimes not able to cope well with updates
> > > involving deprecation.
> > > It attempts to resolve the dependency to the deprecated packages and
> > update
> > > this latter although it should be dropped.
> > >
> > > Explicitly providing the versions you want to install on the command line
> > > usually circumvents the issue.
> > >
> >
> >
> > This seems to be wrong for me:
> >
> >
> >
> >
> > grzemba@oi-hipster:~$ pkg contents -o fmri -t depend
> > libwww-perl-524@latest
> > FMRI
> > library/perl-5/encode-locale-524
> > library/perl-5/file-listing-524
> > library/perl-5/html-parser-524
> > library/perl-5/http-cookies-524
> > library/perl-5/http-daemon-524
> > library/perl-5/http-date-524
> > library/perl-5/http-message-524
> > library/perl-5/http-negotiate-524
> > library/perl-5/lwp-mediatypes-524
> > library/perl-5/net-http-524
> > library/perl-5/uri-524
> > library/perl-5/www-robotrules-524
> > pkg:/runtime/perl-524@5.24.3-2020.0.1.3
> >
> >
> > and
> >
> > pkg list -af library/perl-5/encode-locale-524@latest
> > NAME (PUBLISHER) VERSION IFO
> > library/perl-5/encode-locale-524 (openindiana.org) 1.5-2022.0.0.2 --o
> >
> 
> I agree.
> 
> However that does not explain why updating xscreensaver fails although it
> does not depend on perl 5.24 anymore.
> 

 
but it has a dependency for libwww-perl. How IPS decides which version of this 
package will installed finally I do not know. 

 
I could upgrade BE in this kind:
 
pkg update \
 
--reject library/perl-5/libwww-perl-524 \ 
--reject library/perl-5/http-daemon-524 \ 
--reject library/perl-5/http-negotiate-522 \ 
--reject library/perl-5/http-negotiate-524 \ 
--reject library/perl-5/net-http-522 \ 
--reject library/perl-5/net-http-524 \ 
osnet-incorporation@latest userland-incorporation@latest 
install-incorporation@latest
 

 
all of this Perl packages have dependencies which are obsolete now.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] DKIM violationRe: libwww-perl-524 dependency problem

[Carsten Grzemba via openindiana-discuss]

Am 27.07.22 11:06 schrieb Aurélien Larcher  : 
> 
> On Wed, Jul 27, 2022 at 9:53 AM Carsten Grzemba via openindiana-discuss <
> openindiana-discuss@openindiana.org> wrote:
> 
> > If libwww-perl-524 is installed it is not possible to update xscreensaver
> > and others because the dependency for
> >
> > library/perl-5/encode-locale-524 cannot longer resolved.
> > This package is obsoleted now.
> 
> 
> > Can anyone fix this?
> >
> 
> There is seemingly no problem with the package dependencies, xscreensaver
> does not depend on perl-524 anymore.
> Could you try installing/updating specific package versions?
> 
> I have noticed that pkg is sometimes not able to cope well with updates
> involving deprecation.
> It attempts to resolve the dependency to the deprecated packages and update
> this latter although it should be dropped.
> 
> Explicitly providing the versions you want to install on the command line
> usually circumvents the issue.
> 

 
This seems to be wrong for me: 

 

 
 grzemba@oi-hipster:~$ pkg contents -o fmri -t depend libwww-perl-524@latest
FMRI
library/perl-5/encode-locale-524
library/perl-5/file-listing-524
library/perl-5/html-parser-524
library/perl-5/http-cookies-524
library/perl-5/http-daemon-524
library/perl-5/http-date-524
library/perl-5/http-message-524
library/perl-5/http-negotiate-524
library/perl-5/lwp-mediatypes-524
library/perl-5/net-http-524
library/perl-5/uri-524
library/perl-5/www-robotrules-524
pkg:/runtime/perl-524@5.24.3-2020.0.1.3


and

pkg list -af library/perl-5/encode-locale-524@latest
NAME (PUBLISHER) VERSION IFO
library/perl-5/encode-locale-524 (openindiana.org) 1.5-2022.0.0.2 --o
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] libwww-perl-524 dependency problem

[Carsten Grzemba via openindiana-discuss]

If libwww-perl-524 is installed it is not possible to update xscreensaver and 
others because the dependency for 

library/perl-5/encode-locale-524 cannot longer resolved.
This package is obsoleted now.

Can anyone fix this?

Thanks
-- 

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

Re: [OpenIndiana-discuss] Problem with Audio in Firefox

[Carsten Grzemba via openindiana-discuss]

Am 26.07.22 12:21 schrieb russell  : 
> 
> HI
> 
> When I perform an update I always create a new BE.
> I performed a update on the 2022-07-03 and audio playback in Firefox was 
> fine.
> On the 2022-07-20 I performed an update, while VLC played audio okay, 
> Firefox would not play Youtube audio.
> I tried further updates on the 2022-07-23 and 2022-07-25 audio playback 
> via Firefox was still broken but VLC was fine.
> Has anyone else experienced this?
> 
> Russell
> 
> --
> 
I can confirm the FF@102 is working correctly.
 
I try to verify this with FF@102.1. But in the moment my update process 
complains dependency problems with xscreensaver and libwww-perl
 

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

[OpenIndiana-discuss] Firefox 102 preview package available for testing

[Carsten Grzemba via openindiana-discuss]

Thanks to the work of Geoffrey Weiss we have already a Firefox package for 
version 102. In september the firefox community will release the new ESR 
version. With this work we have FF 102 for testing already now.

For those who interested on testing:

$ pfexec pkg set-publisher -g http://pkg.toc.de/userland openindiana.org
$ pfexec pkg install firefox@102.0

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

Re: [OpenIndiana-discuss] need driver for wireless card or siupported wireledd card

[Carsten Grzemba via openindiana-discuss]

I use the Edimax USB Wifi dongle with the urtwn driver. Unfortunateley in the 
meantime this driver has some short comings with the current usb hci drivers. 
But mainly it works.

Am 15.01.22 17:30 schrieb Marc Lobelle  : 
> 
> Hello,
> 
> I'm configuring an H elitebook 820G3 for use with openindiana.
> 
> Unfortunately, the wireless card, an Intel wireless 8260 does not seem 
> to be supported. Do you know if a driver is available ? Or is there 
> another PCIe wifi card that could replace it ?
> 
> Thanks
> 
> Marc
> 
> 
> -- 
>   
> 
> Marc Lobelle
> professeur émérite
> 
> ICTEAM
> UCLouvain / SST / ICTEAM / INGI
> 
> Place Ste Barbe, 2, bte L5.02.01 - 1348 Louvain-la-Neuve
> marc.lobe...@uclouvain.be 
> <mailto:prenom@uclouvain.be(javascript:main.compose( )>
> Tél.+32 (0) 475 494 616
> Fax +32 (0) 10 47 51 20
> www.uclouvain.be <https://uclouvain.be>
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
-- 
Carsten Grzemba
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] wiki.openindiana.org needs to be re/started and fixed

[Carsten Grzemba via openindiana-discuss]

Am 25.11.21 10:23 schrieb "Nikola M."  : 
> 
> On 11/23/21 09:53, Udo Grabowski (IMK) wrote:
> >
> >
> > On 23/11/2021 09:19, Nikola M. wrote:
> >> On 11/22/21 17:18, Udo Grabowski (IMK) wrote:
> >>>
> >>> 
> >>> "Important changes to our server and Data Center products
> >>> We’ve ended sales for new server licenses and will end support for
> >>> server on February 2, 2024."
> >>
> >> February 2, 2024 sounds just fine, till that time, things can get 
> >> changed multiple times, things reworked, there only needs a green 
> >> light for:
> >> To actually see if license is attainable for fresh instance to be put 
> >> up, ...
> >
> > Read again: "W E' V E E N D E D S A L E S F O R
> > N E W S E R V E R L I C E N S E S"
> 
> No need to shout it loud.
> They never used to sale licenses to OI, they gave it for free.
> I can contact them to ask for free license and migration options, till 
> their support period is out.
> 

That would be helpful!  
   
Maybe they also offer the cloud license for free.   Then we would no longer 
have to deal with the hosting and update issue also.
 
> 
> 
> 
> It doesn't mean Wiki can not continue to live with migrating history and 
> data
> and not to be put offline hidden and closed for everyone.
> Mediawiki is also neat.
> it just needs to be free to use and not limited.
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] wiki.openindiana.org needs to be re/started and fixed

[Carsten Grzemba via openindiana-discuss]

Am 22.11.21 17:18 schrieb "Udo Grabowski (IMK)"  : 
> 
> On 22/11/2021 16:55, Nikola M. wrote:
> > ...
> >Atlassian granted to the then Openindiana named project a license that does 
> >not need paying, maybe renewal.
> >It didn't bother the community to use it for ten years or so.
> >
> >I think license to Confluence Wiki will be provided also for new install, 
> >one just needs to ask Atlassian. And do fresh install and migrate data.
> >Fresh install of Confluence providing 2 things above is I think very 
> >possible, it is not, only if it is not allowed to happen.
> > ...
> 
> 
> "Important changes to our server and Data Center products
>  We’ve ended sales for new server licenses and will end support for
>  server on February 2, 2024."
> 

Perhaps do Atlassian migrates the free community licenses to the Cloud licenses 
also?
 -- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] NFSv4 client problem on OI with Solaris 11.4 NFS server

[Carsten Grzemba via openindiana-discuss]

Am 15.11.21 15:04 schrieb Carsten Grzemba via openindiana-discuss  
: 
> 
> Hallo,
> 
> I use Openindiana as NFS client which has the home directory mounted on an 
> NFS server running Solaris 11.4. Since the last update to Solaris 11.4.38 I 
> see the following behavior :
> 
> I attempt to start Firefox.
> Than Firefox stops immeditaly with "resource lost"
> Trussing the Firefox shows the the Firefox gets a SIGLOST and in 
> /var/adm/messagesI see the following messages:
> 
> 
> Nov 15 12:26:58 oi-hipster nfs: [ID 269213 kern.info] NOTICE: [NFS4][Server: 
> con03][Mntpt: /home/grzemba]Process 2755 lost its locks on file 
> ./.mozilla/firefox/6w0glrzw.Default User/storage.sqlite (rnode_pt: 
> fe11e4027bb8) due to NFS recovery error (NFS4ERR_NO_GRACE) on server 
> con03.
> Nov 15 12:26:58 oi-hipster nfs: [ID 941083 kern.info] NOTICE: NFS4 FACT 
> SHEET: 
> Nov 15 12:26:58 oi-hipster Action: NR_CLIENTID 
> Nov 15 12:26:58 oi-hipster NFS4 error: NFS4ERR_EXPIRED 
> 
> 
> I see the NFS errors also for other files.
> 
> 
> Until the update the NFS server runs 11.4.14 without this problems.
> 
> Anyone has seen similar problems with NFSv4? Is there a configuration item 
> for fixing the problem?
> 
> -- 
> Carsten
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 

commands like 'git pull' also not working anymore.
 
 
If I set on OI
 
sudo sharectl set -p client_versmax=3 nfs
 

 
it works 'like' before, but it would be nice if I could continue to use NFSv4.
 
 
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] NFSv4 client problem on OI with Solaris 11.4 NFS server

[Carsten Grzemba via openindiana-discuss]

Hallo,

I use Openindiana as NFS client which has the home directory mounted on an NFS 
server running Solaris 11.4. Since the last update to Solaris 11.4.38 I see the 
following behavior :

I attempt to start Firefox.
Than Firefox stops immeditaly with "resource lost"
Trussing the Firefox shows the the Firefox gets a SIGLOST and in 
/var/adm/messagesI see the following messages:


Nov 15 12:26:58 oi-hipster nfs: [ID 269213 kern.info] NOTICE: [NFS4][Server: 
con03][Mntpt: /home/grzemba]Process 2755 lost its locks on file 
./.mozilla/firefox/6w0glrzw.Default User/storage.sqlite (rnode_pt: 
fe11e4027bb8) due to NFS recovery error (NFS4ERR_NO_GRACE) on server con03.
Nov 15 12:26:58 oi-hipster nfs: [ID 941083 kern.info] NOTICE: NFS4 FACT SHEET: 
Nov 15 12:26:58 oi-hipster Action: NR_CLIENTID 
Nov 15 12:26:58 oi-hipster NFS4 error: NFS4ERR_EXPIRED 


I see the NFS errors also for other files.


Until the update the NFS server runs 11.4.14 without this problems.

Anyone has seen similar problems with NFSv4? Is there a configuration item for 
fixing the problem?

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

Re: [OpenIndiana-discuss] VirtulaBox crash at guest startup with QT5

[Carsten Grzemba via openindiana-discuss]

Am 21.10.21 09:05 schrieb Stephan Althaus  : 
> 
> On 10/21/21 8:20 AM, Carsten Grzemba via openindiana-discuss wrote:
> >
> > Am 20.10.21 19:26 schrieb Stephan Althaus 
> > : 
> >> Hi Carsten!
> >>
> >> I did a pkg update and i am now on qt 50.1.3.
> >> Via VBox gui i see no problems so far...
> >>
> >> $ pkg list qt5
> >> NAME (PUBLISHER) 
> >> VERSION IFO
> >> library/qt5 (openindiana.org) 
> >> 5.12.10-2020.0.1.3 i--
> >>
> >> Do you have this problem with all your vms?
> >>
> >>
> >> Greetings,
> >> Stephan
> >>
> >> On 10/20/21 11:56 AM, Carsten Grzemba via openindiana-discuss wrote:
> >>>> ::status
> >>> debugging core file of VirtualBoxVM (64-bit) from notebookcg2
> >>> initial argv: /opt/VirtualBox/amd64/VirtualBoxVM --comment Win7 --startvm 
> >>> 36c5217a-535b-4ff0-
> >>> threading model: native threads
> >>> status: process terminated by SIGABRT (Abort), pid=5959 uid=1005 code=-1
> >>>> ::walk thread | ::findstack
> >>> stack pointer for thread 1: 7fffb130
> >>> [ 7fffb130 libc.so.1`_lwp_kill+0xa() ]
> >>> 7fffb160 libc.so.1`raise+0x1e()
> >>> 7fffb1b0 libc.so.1`abort+0x58()
> >>> 7fffb2a0 
> >>> libQt5Core.so.5.12.10`_ZNK14QMessageLogger7warningERK16QLoggingCategoryPKcz()
> >>> 7fffb440 
> >>> libQt5Gui.so.5.12.10`_ZN22QGuiApplicationPrivate25createPlatformIntegrationEv+0x14ad()
> >>> 7fffb460 
> >>> libQt5Gui.so.5.12.10`_ZN22QGuiApplicationPrivate21createEventDispatcherEv+0x3d()
> >>> 7fffb4e0 
> >>> libQt5Core.so.5.12.10`_ZN23QCoreApplicationPrivate4initEv+0xb35()
> >>> 7fffb5e0 
> >>> libQt5Gui.so.5.12.10`_ZN22QGuiApplicationPrivate4initEv+0x1f()
> >>> 7fffb600 
> >>> libQt5Widgets.so.5.12.10`_ZN19QApplicationPrivate4initEv+0x11()
> >>> 7fffb6d0 VirtualBoxVM.so`TrustedMain+0x156()
> >>> 7fffb710 SUPR3HardenedMain+0x12f()
> >>> 7fffb740 _start_crt+0x87()
> >>> 7fffb750 _start+0x18()
> >>>
> >>> root@notebookcg2:~# pkg list virtualbox
> >>> NAME (PUBLISHER) VERSION IFO
> >>> system/virtualbox (openindiana.org) 6.1.22-2020.0.1.2 i--
> >>> root@notebookcg2:~# pkg list qt5
> >>> NAME (PUBLISHER) VERSION IFO
> >>> library/qt5 (openindiana.org) 5.12.10-2020.0.1.3 i--
> >>>
> >>>
> >>>
> >>> Have anyone similar issues?
> >>> 
> >>>
> >>>
> >>
> >> ___
> >> openindiana-discuss mailing list
> >> openindiana-discuss@openindiana.org
> >> https://openindiana.org/mailman/listinfo/openindiana-discuss
> >>
> > On all VM's the same, on startup if the Console Window have to raise.
> > -- 
> > Carsten
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> Hello!
> 
> You could check if it is a QT5 problem, if other packages are affected, too:
> 
> $ pkg search -Hlo pkg.name require:library/qt5
> system/virtualbox
> diagnostic/wireshark
> media/vlc
> 
> i would now check vlc and/or wireshark if they show a window..
> 
> hth
> 
> Stephan
> 

 
In headless mode the VM's work, so it seems the console window is really the 
root cause.
 

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

Re: [OpenIndiana-discuss] VirtulaBox crash at guest startup n QT5

[Carsten Grzemba via openindiana-discuss]

Am 20.10.21 19:26 schrieb Stephan Althaus  : 
> 
> Hi Carsten!
> 
> I did a pkg update and i am now on qt 50.1.3.
> Via VBox gui i see no problems so far...
> 
> $ pkg list qt5
> NAME (PUBLISHER) 
> VERSION IFO
> library/qt5 (openindiana.org) 
> 5.12.10-2020.0.1.3 i--
> 
> Do you have this problem with all your vms?
> 
> 
> Greetings,
> Stephan
> 
> On 10/20/21 11:56 AM, Carsten Grzemba via openindiana-discuss wrote:
> >> ::status
> > debugging core file of VirtualBoxVM (64-bit) from notebookcg2
> > initial argv: /opt/VirtualBox/amd64/VirtualBoxVM --comment Win7 --startvm 
> > 36c5217a-535b-4ff0-
> > threading model: native threads
> > status: process terminated by SIGABRT (Abort), pid=5959 uid=1005 code=-1
> >> ::walk thread | ::findstack
> > stack pointer for thread 1: 7fffb130
> > [ 7fffb130 libc.so.1`_lwp_kill+0xa() ]
> > 7fffb160 libc.so.1`raise+0x1e()
> > 7fffb1b0 libc.so.1`abort+0x58()
> > 7fffb2a0 
> > libQt5Core.so.5.12.10`_ZNK14QMessageLogger7warningERK16QLoggingCategoryPKcz()
> > 7fffb440 
> > libQt5Gui.so.5.12.10`_ZN22QGuiApplicationPrivate25createPlatformIntegrationEv+0x14ad()
> > 7fffb460 
> > libQt5Gui.so.5.12.10`_ZN22QGuiApplicationPrivate21createEventDispatcherEv+0x3d()
> > 7fffb4e0 
> > libQt5Core.so.5.12.10`_ZN23QCoreApplicationPrivate4initEv+0xb35()
> > 7fffb5e0 
> > libQt5Gui.so.5.12.10`_ZN22QGuiApplicationPrivate4initEv+0x1f()
> > 7fffb600 
> > libQt5Widgets.so.5.12.10`_ZN19QApplicationPrivate4initEv+0x11()
> > 7fffb6d0 VirtualBoxVM.so`TrustedMain+0x156()
> > 7fffb710 SUPR3HardenedMain+0x12f()
> > 7fffb740 _start_crt+0x87()
> > 7fffb750 _start+0x18()
> >
> > root@notebookcg2:~# pkg list virtualbox
> > NAME (PUBLISHER) VERSION IFO
> > system/virtualbox (openindiana.org) 6.1.22-2020.0.1.2 i--
> > root@notebookcg2:~# pkg list qt5
> > NAME (PUBLISHER) VERSION IFO
> > library/qt5 (openindiana.org) 5.12.10-2020.0.1.3 i--
> >
> >
> >
> > Have anyone similar issues?
> > 
> >
> >
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 

On all VM's the same, on startup if the Console Window have to raise.
 -- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] VirtulaBox crash at guest startup n QT5

[Carsten Grzemba via openindiana-discuss]

> ::status
debugging core file of VirtualBoxVM (64-bit) from notebookcg2
initial argv: /opt/VirtualBox/amd64/VirtualBoxVM --comment Win7 --startvm 
36c5217a-535b-4ff0-
threading model: native threads
status: process terminated by SIGABRT (Abort), pid=5959 uid=1005 code=-1
> ::walk thread | ::findstack
stack pointer for thread 1: 7fffb130
[ 7fffb130 libc.so.1`_lwp_kill+0xa() ]
 7fffb160 libc.so.1`raise+0x1e()
 7fffb1b0 libc.so.1`abort+0x58()
 7fffb2a0 
libQt5Core.so.5.12.10`_ZNK14QMessageLogger7warningERK16QLoggingCategoryPKcz()
 7fffb440 
libQt5Gui.so.5.12.10`_ZN22QGuiApplicationPrivate25createPlatformIntegrationEv+0x14ad()
 7fffb460 
libQt5Gui.so.5.12.10`_ZN22QGuiApplicationPrivate21createEventDispatcherEv+0x3d()
 7fffb4e0 
libQt5Core.so.5.12.10`_ZN23QCoreApplicationPrivate4initEv+0xb35()
 7fffb5e0 libQt5Gui.so.5.12.10`_ZN22QGuiApplicationPrivate4initEv+0x1f()
 7fffb600 
libQt5Widgets.so.5.12.10`_ZN19QApplicationPrivate4initEv+0x11()
 7fffb6d0 VirtualBoxVM.so`TrustedMain+0x156()
 7fffb710 SUPR3HardenedMain+0x12f()
 7fffb740 _start_crt+0x87()
 7fffb750 _start+0x18()
> 


root@notebookcg2:~# pkg list virtualbox
NAME (PUBLISHER) VERSION IFO
system/virtualbox (openindiana.org) 6.1.22-2020.0.1.2 i--
root@notebookcg2:~# pkg list qt5
NAME (PUBLISHER) VERSION IFO
library/qt5 (openindiana.org) 5.12.10-2020.0.1.3 i--



Have anyone similar issues?



-- 

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

[OpenIndiana-discuss] Ekiga

[Carsten Grzemba via openindiana-discuss]

Hi,


Is there anyone who uses Ekiga on openindiana or has experience with Ekiga on 
other platforms   ?

I ask because Ekiga seems to be out of development and if nobody use it we can 
it remove from oi-userland.


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

Re: [OpenIndiana-discuss] Firefox68esr for testing

[Carsten Grzemba via openindiana-discuss]

Am 19.07.21 20:56 schrieb Stephan Althaus  : 
> 
> On 7/19/21 8:52 PM, Apostolos Syropoulos via openindiana-discuss wrote:
> > Any ideas how one can install this new firefox? I tried 
> >
> > # pkg install web/browser/firefox@90.0
> > Creating Plan (Solver setup): \
> > pkg install: No matching version of web/browser/firefox can be installed:
> > Reject: pkg://userland/web/browser/firefox@90.0-2020.0.1.0
> > Reason: This version is excluded by installed incorporation 
> > consolidation/userland/userland-incorporation@0.5.11-2020.0.1.14047
> >
> > A.S.
> >
> > --Apostolos Syropoulos
> > Xanthi, Greece
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> Hello!
> 
> Try a pkg update first, to get the most recent basic installation.
> 
> i am on
> pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2020.0.1.14247
> 
> see: ->"14247"
> 
> which worked. Anything newer should work, too.
> 
> Stephan
> 
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 

  
The userland-incorporation will hold the firefox version at 78.12. If you like 
to install and test firefox v90.0 you have to unlock the version on the 
userland-incorporation.

$ pkg change-facet facet.version-lock.web/browser/firefox=false 
facet.version-lock.web/data/firefox-bookmarks=false

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

Re: [OpenIndiana-discuss] Smartcards on Openindiana

[Carsten Grzemba via openindiana-discuss]

Am 16.06.21 11:06 schrieb Stephan Althaus  : 
> 
> On 6/16/21 10:05 AM, Carsten Grzemba via openindiana-discuss wrote:
> >
> >
> >
> > Is there anyone who uses smartcards on OpenIndiana? There are some 
> > recommendations which reader devices can be used?
> >
> > Many Thanks,
> > Carsten
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> Hello!
> 
> i am using two USB SD card readers:
> 
> HAMA USB 3.0 00123901 idVendor = 0x56e idProduct = 0x8007
> 
> Sandisk Extreme Pro UHS-II USB-C Card reader SDDR-409 idVendor = 
> 0x781 idProduct = 0xcfca
> 
> 
> Both work well on my USB 3.0 Type A port.
> 
> Stephan
> 

I mean smartcards like cryptocards with keys and certificates or similar.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Smartcards on Openindiana

[Carsten Grzemba via openindiana-discuss]

Is there anyone who uses smartcards on OpenIndiana? There are some 
recommendations which reader devices can be used?

Many Thanks,
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] gimp crash on JPG or PNG image export

[Carsten Grzemba via openindiana-discuss]

Am 28.05.21 14:44 schrieb Stephan Althaus  : 
> 
> On 5/28/21 2:39 PM, Carsten Grzemba via openindiana-discuss wrote:
> > with the current gimp 2.10.22 I get a crash on export images as JPEG or 
> > PNG. The export is done bz plugin:
> >
> > /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg
> >
> > this is started via exec:
> >
> > 10533/1: 13.8110 
> > execve("/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg", 
> > 0x7FFFBFFFE550, 0x02CD7A00) argc = 6
> > 10533/1: argv: /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg
> > 10533/1: -gimp 15 14 -run 0
> > 10533/1: envp: _=*10224*/usr/bin/gimp AUDIODEV= COLORTERM=truecolor
> > 10533/1: CORONA_TOKEN=pseudo.002128e65261
> > 10533/1: 
> > DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-PPpzlt3UCi,guid=71a6c67bc283c28e74ca3aa760af6b42
> > 10533/1: DESKTOP_SESSION=gnome DTDEVROOT=/tmp/SUNWut/sessions/12
> > 10533/1: DTSCREENSAVERLIST=StartDtscreenBlank GDMSESSION=gnome
> > 10533/1: GDM_KEYBOARD_LAYOUT=de GDM_LANG=de_DE.UTF-8
> > 10533/1: GNOME_DESKTOP_SESSION_ID=this-is-deprecated
> > 10533/1: HOME=/home/grzemba LANG=de_DE.UTF-8 LOGNAME=grzemba
> > 10533/1: ORBIT_SOCKETDIR=/var/tmp/orbit-grzemba
> > 10533/1: PAGER=/usr/bin/less -ins
> > 10533/1: 
> > PATH=/usr/bin:/usr/sbin:/sbin:/opt/SUNWut/bin:/opt/SUNWsamfs/bin:/opt/csw/bin
> > 10533/1: PULSE_CONFIG=/etc/opt/SUNWut/pulse/daemon.conf
> > 10533/1: PULSE_LOG_NO_RATE_LIMIT=1
> > 10533/1: PULSE_SCRIPT=/etc/opt/SUNWut/pulse/default.pa
> > 10533/1: PULSE_SINK=srout.12 PULSE_SOURCE=srin.12.monitor
> > 10533/1: PWD=/home/grzemba
> > 10533/1: SESSION_MANAGER=local/gnom:/tmp/.ICE-unix/3161
> > 10533/1: SHELL=/usr/bin/ksh SHLVL=3 SSH_AGENT_PID=3273
> > 10533/1: SSH_AUTH_SOCK=/tmp/ssh-XXwtailg/agent.3161
> > 10533/1: SUN_SUNRAY_TOKEN=pseudo.002128e65261 TERM=xterm-256color
> > 10533/1: USER=grzemba USERNAME=grzemba UTAUDIODEV=
> > 10533/1: UTDEVROOT=/tmp/SUNWut/sessions/12/unit VTE_VERSION=5405
> > 10533/1: WINDOWID=44040655
> > 10533/1: 
> > XAUTHORITY=/tmp/gdm-auth-cookies-avaqdf/auth-for-grzemba-evaqdf/database
> > 10533/1: _AST_FEATURES=UNIVERSE - att A__z="*SHLVL
> > 10533/1: PYTHONPATH=/usr/lib/amd64/gimp/2.0/python DISPLAY=:12
> >
> > but crashed:
> >
> > 10533/1: 2 rB410 3 =BB10 4 R9610 51D9D10 6 2 x10 6FD7F10 81B9490 8DD a10
> > 10533/1: 9FB v90 :BD C10 ;DB X90 86 A90 ?9B1C90 @ f #90
> > 10533/1: A84 910 B F0590 C d1B10 D %E790 E CFD10 F05C990 G #DF10 GEEE610
> > 10533/1: I03C110 ICEC810 JE3A310 KAEAA10 LCCBF90 M8E8C10 NACA190 O n n10
> > 10533/1: P8C8390 Q W8A90 R l e90 S 7 l90 T L G90 U17 N90 V , )90 VF7 090
> > 10533/1: X15 F10 XD71290 YF5 (10 ZB6F490 [D5\n10 \A01110 ]B4EC10 ^7FF310
> > 10533/1: _94CE10 ` _D510 a }EA90 b ?B710 c ]CC90 d1F9910 e =AE90 f\bB590
> > 10533/1: g1D9090 gE89790 hFD r90 iC8 y90 jDD T90 kA8 [90 lC6 q10 m88 =90
> > 10533/1: nA6 S10 o h1F90 p86 510 q Q <10 r f1710 s 11E10 t EF910 u11\010
> > 10533/1: v /1590 vF0E210 x0EF790 xD0C410 yEED990 zB0A610 {CEBB90 |99C290
> > 10533/1: }AE9D90 ~ yA4907F8E7F90\001020302030203020302030204\00301020302
> > 10533/1: 05\0030203020301060706070607060706070607060706070607060706070607
> > 10533/1: 0607060706070607060706070607060706070607060706070607060706070607
> > 10533/1: 0607060706070607060706070607060706070607060706070607060706070607
> > 10533/1: 06070607060706070607060706070607060706070607060706070607\0\01C
> > 10533/1: 01\0\0\00E10\005\0\01C 01\0\0\00E10\005\0\0 * 001\t\0\0 * 001\t
> > 10533/1: \0\01C 01\0\0\00E10\005 C E S T\0 C E T\0 C E M T\0\0\00101\001
> > 10533/1: 0101\0\0\0\0\0\00101
> > 10533/1: 17.5854 close(11) = 0
> > 10533/1: 17.5854 time() = 1622203035
> > 10533/1: 17.5854 time() = 1622203035
> > 10533/1: 17.5857 Incurred fault #6, FLTBOUNDS %pc = 0x7FFFAF3593D6
> > 10533/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x504D4947
> > 10533/1: 17.5857 Received signal #11, SIGSEGV [caught]
> > 10533/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x504D4947
> > 10533/1: 17.5857 lwp_sigmask(SIG_SETMASK, 0xFFBFFEFF, 0xFFF7, 
> > 0x01FF, 0x) = 0xFFBFFEFF [0x]
> > 10533/1: 17.5858 write(2, " / u s r / l i b / a m d".., 86) = 86
> > 10533/1: 17.5860 mmap(0x, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, 
> > MAP_PRIVATE|MAP_ANON, 4294967295, 0) = 0x7FFFAC4F
> > 10533/1: 17.5863 _exit(1)
> >
> >
> > unfortunately I cant find any core file. The good side the image was saved, 
> > so I am guessing the crash is on plugin exit.
> >
> > 
> > 
> > Has anzone seen similar problems?
> >
> Hi!
> 
&

[OpenIndiana-discuss] gimp crash on JPG or PNG image export

[Carsten Grzemba via openindiana-discuss]

with the current gimp 2.10.22 I get a crash on export images as JPEG or PNG. 
The export is done bz plugin:

/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg

this is started via exec:

10533/1: 13.8110 execve("/usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg", 
0x7FFFBFFFE550, 0x02CD7A00) argc = 6
10533/1: argv: /usr/lib/amd64/gimp/2.0/plug-ins/file-jpeg/file-jpeg
10533/1: -gimp 15 14 -run 0
10533/1: envp: _=*10224*/usr/bin/gimp AUDIODEV= COLORTERM=truecolor
10533/1: CORONA_TOKEN=pseudo.002128e65261
10533/1: 
DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-PPpzlt3UCi,guid=71a6c67bc283c28e74ca3aa760af6b42
10533/1: DESKTOP_SESSION=gnome DTDEVROOT=/tmp/SUNWut/sessions/12
10533/1: DTSCREENSAVERLIST=StartDtscreenBlank GDMSESSION=gnome
10533/1: GDM_KEYBOARD_LAYOUT=de GDM_LANG=de_DE.UTF-8
10533/1: GNOME_DESKTOP_SESSION_ID=this-is-deprecated
10533/1: HOME=/home/grzemba LANG=de_DE.UTF-8 LOGNAME=grzemba
10533/1: ORBIT_SOCKETDIR=/var/tmp/orbit-grzemba
10533/1: PAGER=/usr/bin/less -ins
10533/1: 
PATH=/usr/bin:/usr/sbin:/sbin:/opt/SUNWut/bin:/opt/SUNWsamfs/bin:/opt/csw/bin
10533/1: PULSE_CONFIG=/etc/opt/SUNWut/pulse/daemon.conf
10533/1: PULSE_LOG_NO_RATE_LIMIT=1
10533/1: PULSE_SCRIPT=/etc/opt/SUNWut/pulse/default.pa
10533/1: PULSE_SINK=srout.12 PULSE_SOURCE=srin.12.monitor
10533/1: PWD=/home/grzemba
10533/1: SESSION_MANAGER=local/gnom:/tmp/.ICE-unix/3161
10533/1: SHELL=/usr/bin/ksh SHLVL=3 SSH_AGENT_PID=3273
10533/1: SSH_AUTH_SOCK=/tmp/ssh-XXwtailg/agent.3161
10533/1: SUN_SUNRAY_TOKEN=pseudo.002128e65261 TERM=xterm-256color
10533/1: USER=grzemba USERNAME=grzemba UTAUDIODEV=
10533/1: UTDEVROOT=/tmp/SUNWut/sessions/12/unit VTE_VERSION=5405
10533/1: WINDOWID=44040655
10533/1: 
XAUTHORITY=/tmp/gdm-auth-cookies-avaqdf/auth-for-grzemba-evaqdf/database
10533/1: _AST_FEATURES=UNIVERSE - att A__z="*SHLVL
10533/1: PYTHONPATH=/usr/lib/amd64/gimp/2.0/python DISPLAY=:12

but crashed:

10533/1: 2 rB410 3 =BB10 4 R9610 51D9D10 6 2 x10 6FD7F10 81B9490 8DD a10
10533/1: 9FB v90 :BD C10 ;DB X90 86 A90 ?9B1C90 @ f #90
10533/1: A84 910 B F0590 C d1B10 D %E790 E CFD10 F05C990 G #DF10 GEEE610
10533/1: I03C110 ICEC810 JE3A310 KAEAA10 LCCBF90 M8E8C10 NACA190 O n n10
10533/1: P8C8390 Q W8A90 R l e90 S 7 l90 T L G90 U17 N90 V , )90 VF7 090
10533/1: X15 F10 XD71290 YF5 (10 ZB6F490 [D5\n10 \A01110 ]B4EC10 ^7FF310
10533/1: _94CE10 ` _D510 a }EA90 b ?B710 c ]CC90 d1F9910 e =AE90 f\bB590
10533/1: g1D9090 gE89790 hFD r90 iC8 y90 jDD T90 kA8 [90 lC6 q10 m88 =90
10533/1: nA6 S10 o h1F90 p86 510 q Q <10 r f1710 s 11E10 t EF910 u11\010
10533/1: v /1590 vF0E210 x0EF790 xD0C410 yEED990 zB0A610 {CEBB90 |99C290
10533/1: }AE9D90 ~ yA4907F8E7F90\001020302030203020302030204\00301020302
10533/1: 05\0030203020301060706070607060706070607060706070607060706070607
10533/1: 0607060706070607060706070607060706070607060706070607060706070607
10533/1: 0607060706070607060706070607060706070607060706070607060706070607
10533/1: 06070607060706070607060706070607060706070607060706070607\0\01C
10533/1: 01\0\0\00E10\005\0\01C 01\0\0\00E10\005\0\0 * 001\t\0\0 * 001\t
10533/1: \0\01C 01\0\0\00E10\005 C E S T\0 C E T\0 C E M T\0\0\00101\001
10533/1: 0101\0\0\0\0\0\00101
10533/1: 17.5854 close(11) = 0
10533/1: 17.5854 time() = 1622203035
10533/1: 17.5854 time() = 1622203035
10533/1: 17.5857 Incurred fault #6, FLTBOUNDS %pc = 0x7FFFAF3593D6
10533/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x504D4947
10533/1: 17.5857 Received signal #11, SIGSEGV [caught]
10533/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x504D4947
10533/1: 17.5857 lwp_sigmask(SIG_SETMASK, 0xFFBFFEFF, 0xFFF7, 0x01FF, 
0x) = 0xFFBFFEFF [0x]
10533/1: 17.5858 write(2, " / u s r / l i b / a m d".., 86) = 86
10533/1: 17.5860 mmap(0x, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, 
MAP_PRIVATE|MAP_ANON, 4294967295, 0) = 0x7FFFAC4F
10533/1: 17.5863 _exit(1)


unfortunately I cant find any core file. The good side the image was saved, so 
I am guessing the crash is on plugin exit.



Has anzone seen similar problems?

-- 

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

[OpenIndiana-discuss] Off topic: Sun keyboards

[Carsten Grzemba via openindiana-discuss]

Off topic: 
Is there anyone who is interested in Sun keyboards X3733A, en-layout
I have some on stock and would yield them for shipping costs only.
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Firefox68esr for testing

[Carsten Grzemba via openindiana-discuss]

Am 21.05.21 13:40 schrieb Stephan Althaus  : 
> 
> On 3/28/21 8:11 AM, Carsten Grzemba wrote:
> >
> > there is it again: libspeechd
> >
> > as workaround you can remove the libspeechd.
> >
> > Von meinem Xperia™ von Sony-Smartphone gesendet
> >
> >
> >
> >  Stephan Althaus schrieb 
> >
> > On 03/27/21 04:07 PM, Carsten Grzemba via openindiana-discuss wrote:
> > > unfortunatly the pstack delivers here not a usefull result: the
> > threads with pollsys, portfs or __lwp_park on top are not the reason
> > for core.
> > > I hope
> > > 
> > >
> > > 
> > > $ mdb /usr/lib/amd64/firefox/firefox core
> > >> ::stack
> > > 
> > > delivers here better information.
> > > 
> > > 
> > > --
> > > Carsten
> > > ___
> > > openindiana-discuss mailing list
> > > openindiana-discuss@openindiana.org
> > <mailto:openindiana-discuss@openindiana.org(javascript:main.compose( )>
> > > https://openindiana.org/mailman/listinfo/openindiana-discuss
> > <https://openindiana.org/mailman/listinfo/openindiana-discuss>
> >
> > Hello!
> >
> > Unfornunateliy, the core file was destroyed in the meantime.
> >
> > Fonrtunately i could reproduce the crash by opening the link once one:
> >
> > $ ls -l core
> > -rw--- 1 steven lp 1.80G Mar 27 22:54 core
> > steven@dell6510:~$ pstack core | c++filt | head -100
> > core 'core' of 2652: /usr/lib/amd64/firefox/firefox
> > https://www.ebay.de/itm/384063032538?mk
> > <https://www.ebay.de/itm/384063032538?mk>
> > - thread# 1 / lwp# 1 -
> > 7 fffaf3fd04a __pollsys () + a
> > 7 fffaf38e1d1 poll (fa31840, 9, ) + 51
> > 7 fffa01d29ab PollWrapper(_GPollFD*, unsigned int,
> > int) () + 56
> > 7 fffaee3bbae g_main_context_iterate.isra
> > <http://g_main_context_iterate.isra>.23 () + 15e
> > 7 fffaee3be8f g_main_context_iteration () + 2f
> > 7 fffa01d2ab8 nsAppShell::ProcessNextNativeEvent(bool)
> > () + 12
> > 7 fffa0194617
> > nsBaseAppShell::DoProcessNextNativeEvent(bool) () + 33
> > 7 fffa0194728
> > nsBaseAppShell::OnProcessNextEvent(nsIThreadInternal*, bool) () + f4
> > 7 fff9dd902ea nsThread::ProcessNextEvent(bool, bool*)
> > () + 520
> > 7 fff9dd8ec55 NS_ProcessNextEvent(nsIThread*, bool) ()
> > + 2d
> > 7 fff9e2dc50b
> > mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) () + ef
> > 7 fff9e2a5b05 MessageLoop::RunInternal() () + 13
> > 7 fff9e2a5d4d MessageLoop::Run() () + 37
> > 7 fffa0191672 nsBaseAppShell::Run() () + 2e
> > 7 fffa0f5fdde nsAppStartup::Run() () + 4a
> > 7 fffa102272c XREMain::XRE_mainRun() () + a2c
> > 7 fffa102333f XREMain::XRE_main(int, char**,
> > mozilla::BootstrapConfig const&) () + 7e7
> > 7 fffa10234f6 XRE_main(int, char**,
> > mozilla::BootstrapConfig
> > const&) () + f1
> > 7 fffa10248ad mozilla::BootstrapImpl::XRE_main(int,
> > char**,
> > mozilla::BootstrapConfig const&) () + 11
> > 00411 cb0 do_main(int, char**, char**) ()
> > + 20d
> > 00411 d66 main () + 7b
> > 00411397  _start_crt () + 87
> > 004112 f8 _start () + 18
> >  thread# 2 / lwp# 2 [Gecko_IOThread] -
> > 7 fffaf3fc70a _portfs () + a
> > 7 fff9a9457fd evport_dispatch () + 18d
> > 7 fff9a92d83c event_base_loop () + 25c
> > 7 fff9e2a4b42
> > base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () + a4
> > 7 fff9e2a5b05 MessageLoop::RunInternal() () + 13
> > 7 fff9e2a5d4d MessageLoop::Run() () + 37
> > 7 fff9e2bf4c7 base::Thread::ThreadMain() () + 14d
> > 7 fff9e2a46e9 ThreadFunc(void*) () + a
> > 7 fffaf3f613c _thrp_setup (7fffae2b0240) + 6c
> > 7 fffaf3f6450 _lwp_start ()
> > - thread# 4 / lwp# 4 [Timer] -
> > 7 fffaf3f6497 __lwp_park () + 17
> > 7 fffaf3ef94b cond_wait_queue (559d38, 559d18,
> > 7fffae23e9f0) + 5b
> > 7 fffaf3efd9d cond_wait_common (559d38, 559d18,
> > 7fffae23e9f0) + 1dd
> > 7 fffaf3f00fa __cond_timedwait (559d38, 559d18,
> > 7fffae23eaf0) + ba
> > 7 fffaf3f0161 cond_timedwait (559d38, 559d18,
> > 7fffae23eaf0) + 31
> > 7 fffaf3f01a0 pthread_cond_timedwait (559d38, 559d18,
> > 7fffae23eaf0)
> > + 10
> > 0

Re: [OpenIndiana-discuss] Graphics card CLI enquiry

[Carsten Grzemba via openindiana-discuss]

Am 26.04.21 14:29 schrieb Michelle  : 
> 
> As QNAP are enforcing their malware removal tool out, which is then
> deleting files but has no log of which files it's deleted (and you
> can't turn the malware removal tool off... it just re-installs itself
> and keeps running)
> 
> ...I'm having to press my backup N54L into use and install OI on it.
> 
> The problem is, I need to query my currently running N54L with OI to
> find out what graphics card is in it, so I can order a second one.
> 
> The usual linux command isn't there so I was wondering what CLI command
> I run to find out what's in there please, as it isn't exactly a command
> I use every day :-)
> 

Perhaps helps: 

 
$ sudo scanpci
 
 
 
> 
> -- 
> 
> 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Firefox 78 and MP4

[Carsten Grzemba via openindiana-discuss]

short note:

To get MP4 working on Firefox 78 the package 

video/ffmpeg
from the hipster-encumbered repository have to be installed.

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

[OpenIndiana-discuss] openindiana crash on startup with wifi usb dongle

[Carsten Grzemba via openindiana-discuss]

Today I started my laptop with WIFI USB dongle connected. There I get a system 
crash late on startup 


... 8< ...

pseudo-device: nsmb0
nsmb0 is /pseudo/nsmb@0
pseudo-device: signalfd0
signalfd0 is /pseudo/signalfd@0
pseudo-device: timerfd0
timerfd0 is /pseudo/timerfd@0
pseudo-device: winlock0
winlock0 is /pseudo/winlock@0
Universal TUN/TAP device driver ver 1.3.2 03/30/2020 (C) 1999-2000 Maxim 
Krasnyansky
pseudo-device: tap0
tap0 is /pseudo/tap@0 
Universal TUN/TAP device driver ver 1.3.2 03/30/2020 (C) 1999-2000 Maxim 
Krasnyansky
pseudo-device: tun0
tun0 is /pseudo/tun@0
NOTICE: urtwn1 unregistered

panic[cpu3]/thread=fe0010a45c20: 
mutex_enter: bad mutex, lp=fe0ba6024940 owner=fe000fd2dc20 
thread=fe0010a45c20


fe0010a45a80 unix:mutex_panic+4a ()
fe0010a45af0 unix:mutex_vector_enter+307 ()
fe0010a45b70 genunix:cv_timedwait_hires+eb ()
fe0010a45bc0 genunix:cv_timedwait+52 ()
fe0010a45c00 f80ec61e ()
fe0010a45c10 unix:thread_start+b ()

dumping to /dev/zvol/dsk/rpool/dump, offset 65536, content: kernel
NOTICE: ahci0: ahci_tran_reset_dport port 0 reset port

> ::status
debugging crash dump vmcore.0 (64-bit) from notebookcg2
operating system: 5.11 illumos-6859ab0054 (i86pc)
build version: heads/master-0-g6859ab0054-dirty

image uuid: 8bea7c30-0a9a-c4ca-edfb-e24b5cecb314
panic message: mutex_enter: bad mutex, lp=fe0ba6024940 
owner=fe000fd2dc20 thread=fe0010a45c20
dump content: kernel pages only
> 



> fe0010a45c20::thread -p
 ADDR PROC LWP CRED
fe0010a45c20 fbc48080 0 fe0ba01e5db0
> fbc48080::ps
S PID PPID PGID SID UID FLAGS ADDR NAME
R 0 0 0 0 0 0x0001 fbc48080 sched

This means that scheduler process get the bad mutex, but there may be also 
other suspect stacks like this?

stack pointer for thread fe000fa8fc20 (TS_FREE) 
(unix`thread_create_intr()): fe000fa8f7d0
 fe000fa8f810 0xfe0bba4df340()
 fe000fa8f840 smt_adjust_cpu_score+0x13()
 fe000fa8f860 cpu_score+0x67()
 fe000fa8f900 disp_lowpri_cpu+0xa3()
 fe000fa8f940 setkpdq+0x11a()
 fe000fa8f9b0 setbackdq+0x33f()
 fe000fa8f9e0 0xa()
 fe000fa8fa20 cv_signal+0x88()
 fe000fa8faa0 taskq_dispatch+0x12a()
 fe000fa8fad0 callout_normal+0x64()
 fe000fa8fb60 cyclic_softint+0xe2()
 fe000fa8fb80 av_check_softint_pending+0x1b()
 fe000fa8fbd0 apix_do_softint_epilog+0xac()
 fe000fa8fc00 apix_dispatch_softint+0x41()
 fe000fa953f0 switch_sp_and_call+0x15()
 814f1 [no mapping for address]



> ::prtusb
INDEX DRIVER INST NODE GEN VID.PID PRODUCT 
1 ehci 0 pci1025,574 2.0 . No Product String
2 ehci 1 pci1025,574 2.0 . No Product String
3 hubd 0 hub 2.0 8087.0024 No Product String
4 hubd 1 hub 2.0 8087.0024 No Product String
5 usb_mid 0 miscellaneous 2.0 064e.c21c 1.3M HD WebCam
6 urtwn 1 device 2.0 7392.7811 802.11n WLAN Adapter
7 usb_mid 2 device 2.0 046d.c52b USB Receiver


The related USB dongle is idx 6 with urtwn driver

If I connect the USB Wifi dongle later all works like expected.
The kernel comes from package osnet-incorporation@0.5.11-2020.0.1.20237
Has the urtwn v0.8.1-oi151a driver some shortcommings? 



Has anyone else seen such problems?

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

Re: [OpenIndiana-discuss] Firefox68esr for testing

[Carsten Grzemba via openindiana-discuss]

Am 28.03.21 10:37 schrieb Apostolos Syropoulos via openindiana-discuss  
: 
> 
> Is this 
> 
> https://github.com/brailcom/speechd
> 
> the source code of libspeechd?
> 
Correct! There is a newer version, but it seems that in the related source is 
no change. 

> 
> 
> --
> Apostolos Syropoulos
> Xanthi, Greece
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Firefox68esr for testing

[Carsten Grzemba via openindiana-discuss]

there is it again: libspeechd

as workaround you can remove the libspeechd. 

Von meinem Xperia™ von Sony-Smartphone gesendet

 Stephan Althaus schrieb 

>On 03/27/21 04:07 PM, Carsten Grzemba via openindiana-discuss wrote:
>> unfortunatly the pstack delivers here not a usefull result: the threads with 
>> pollsys, portfs or __lwp_park on top are not the reason for core.
>> I hope
>>   
>>
>>   
>> $ mdb /usr/lib/amd64/firefox/firefox core
>>> ::stack
>>   
>> delivers here better information.
>>   
>>   
>>   --
>> Carsten
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
>Hello!
>
>Unfornunateliy, the core file was destroyed in the meantime.
>
>Fonrtunately i could reproduce the crash by opening the link once one:
>
>$ ls -l core
>-rw---   1 steven   lp 1.80G Mar 27 22:54 core
>steven@dell6510:~$ pstack core | c++filt | head -100
>core 'core' of 2652:    /usr/lib/amd64/firefox/firefox 
>https://www.ebay.de/itm/384063032538?mk
>- thread# 1 / lwp# 1 -
>  7fffaf3fd04a __pollsys () + a
>  7fffaf38e1d1 poll (fa31840, 9, ) + 51
>  7fffa01d29ab PollWrapper(_GPollFD*, unsigned int, int) () + 56
>  7fffaee3bbae g_main_context_iterate.isra.23 () + 15e
>  7fffaee3be8f g_main_context_iteration () + 2f
>  7fffa01d2ab8 nsAppShell::ProcessNextNativeEvent(bool) () + 12
>  7fffa0194617 nsBaseAppShell::DoProcessNextNativeEvent(bool) () + 33
>  7fffa0194728 
>nsBaseAppShell::OnProcessNextEvent(nsIThreadInternal*, bool) () + f4
>  7fff9dd902ea nsThread::ProcessNextEvent(bool, bool*) () + 520
>  7fff9dd8ec55 NS_ProcessNextEvent(nsIThread*, bool) () + 2d
>  7fff9e2dc50b 
>mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) () + ef
>  7fff9e2a5b05 MessageLoop::RunInternal() () + 13
>  7fff9e2a5d4d MessageLoop::Run() () + 37
>  7fffa0191672 nsBaseAppShell::Run() () + 2e
>  7fffa0f5fdde nsAppStartup::Run() () + 4a
>  7fffa102272c XREMain::XRE_mainRun() () + a2c
>  7fffa102333f XREMain::XRE_main(int, char**, 
>mozilla::BootstrapConfig const&) () + 7e7
>  7fffa10234f6 XRE_main(int, char**, mozilla::BootstrapConfig 
>const&) () + f1
>  7fffa10248ad mozilla::BootstrapImpl::XRE_main(int, char**, 
>mozilla::BootstrapConfig const&) () + 11
>  00411cb0 do_main(int, char**, char**) () + 20d
>  00411d66 main () + 7b
>  00411397 _start_crt () + 87
>  004112f8 _start () + 18
> thread# 2 / lwp# 2 [Gecko_IOThread] -
>  7fffaf3fc70a _portfs () + a
>  7fff9a9457fd evport_dispatch () + 18d
>  7fff9a92d83c event_base_loop () + 25c
>  7fff9e2a4b42 
>base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () + a4
>  7fff9e2a5b05 MessageLoop::RunInternal() () + 13
>  7fff9e2a5d4d MessageLoop::Run() () + 37
>  7fff9e2bf4c7 base::Thread::ThreadMain() () + 14d
>  7fff9e2a46e9 ThreadFunc(void*) () + a
>  7fffaf3f613c _thrp_setup (7fffae2b0240) + 6c
>  7fffaf3f6450 _lwp_start ()
>- thread# 4 / lwp# 4 [Timer] -
>  7fffaf3f6497 __lwp_park () + 17
>  7fffaf3ef94b cond_wait_queue (559d38, 559d18, 7fffae23e9f0) + 5b
>  7fffaf3efd9d cond_wait_common (559d38, 559d18, 7fffae23e9f0) + 1dd
>  7fffaf3f00fa __cond_timedwait (559d38, 559d18, 7fffae23eaf0) + ba
>  7fffaf3f0161 cond_timedwait (559d38, 559d18, 7fffae23eaf0) + 31
>  7fffaf3f01a0 pthread_cond_timedwait (559d38, 559d18, 7fffae23eaf0) 
>+ 10
>  00412c30 
>mozilla::detail::ConditionVariableImpl::wait_for(mozilla::detail::MutexImpl&, 
>mozilla::BaseTimeDuration const&) 
>() + 14a
>  7fff9dd95e88 TimerThread::Run() () + fe
>  7fff9dd90404 nsThread::ProcessNextEvent(bool, bool*) () + 63a
>  7fff9dd8ec55 NS_ProcessNextEvent(nsIThread*, bool) () + 2d
>  7fff9e2dc8c9 
>mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*) 
>() + 109
>  7fff9e2a5b05 MessageLoop::RunInternal() () + 13
>  7fff9e2a5d4d MessageLoop::Run() () + 37
>  7fff9dd9b6e4 nsThread::ThreadFunc(void*) () + d8
>  7fffa4404a06 _pt_root () + cb
>  7fffaf3f613c _thrp_setup (7fffae2b1240) + 6c
>  7fffaf3f6450 _lwp_start ()
>- thread# 5 / lwp# 5 [Socket Thread] -
>  7fffaf3fd04a __pollsys () + a
>  7fffaf38e1d1 poll (7fffae2ae7d0, 15, ) + 51
>  7fffa440329e _pr_poll_with_poll () + 383
>  7fffa4403509 PR_Poll 

Re: [OpenIndiana-discuss] Firefox68esr for testing

[Carsten Grzemba via openindiana-discuss]

Am 24.03.21 13:30 schrieb Stephan Althaus  : 
> 
> On 03/17/21 03:13 PM, Carsten Grzemba via openindiana-discuss wrote:
> > the same, I will upload FF78 in the moment so you can test this also. 
> > But my first impression is needs more resources (RAM), less 
> > performance, at least on my not so young laptop with 8GRAM ;)
> So, here i have a first crash with FF78:
> 
> console output:
> "$ client_loop: send disconnect: Broken pipe
> steven@dell6510:~/src/oi/hoewweken$ Exiting due to channel error.
> Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close 
> with reason=AbnormalShutdown (t=99524.5) [GFX1-]: Receive IPC close with 
> reason=AbnormalShutdown
> Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close 
> with reason=AbnormalShutdown (t=100780) [GFX1-]: Receive IPC close with 
> reason=AbnormalShutdown
> Exiting due to channel error.
> Exiting due to channel error.
> Exiting due to channel error.
> Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close 
> with reason=AbnormalShutdown (t=20821.4) [GFX1-]: Receive IPC close with 
> reason=AbnormalShutdown
> Exiting due to channel error.
> Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close 
> with reason=AbnormalShutdown (t=101365) [GFX1-]: Receive IPC close with 
> reason=AbnormalShutdown
> Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close 
> with reason=AbnormalShutdown (t=99485.3) [GFX1-]: Receive IPC close with 
> reason=AbnormalShutdown
> Exiting due to channel error.
> Exiting due to channel error.
> Exiting due to channel error.
> Exiting due to channel error.
> Exiting due to channel error.
> "
> 
> 
> $ pstack core | c++filt | head -100
> 
> 
> core 'core' of 2909: firefox
> - thread# 1 / lwp# 1 -
>  7fffaf3fd04a __pollsys () + a
>  7fffaf38e1d1 poll (6944390, 9, ) + 51
>  7fff9dd529ab PollWrapper(_GPollFD*, unsigned int, int) () + 56
>  7fffaee3bbae g_main_context_iterate.isra.23 () + 15e
>  7fffaee3be8f g_main_context_iteration () + 2f
>  7fff9dd52ab8 nsAppShell::ProcessNextNativeEvent(bool) () + 12
>  7fff9dd14617 nsBaseAppShell::DoProcessNextNativeEvent(bool) () + 33
>  7fff9dd14728 
> nsBaseAppShell::OnProcessNextEvent(nsIThreadInternal*, bool) () + f4
>  7fff9b9102ea nsThread::ProcessNextEvent(bool, bool*) () + 520
>  7fff9b90ec55 NS_ProcessNextEvent(nsIThread*, bool) () + 2d
>  7fff9be5c50b 
> mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) () + ef
>  7fff9be25b05 MessageLoop::RunInternal() () + 13
>  7fff9be25d4d MessageLoop::Run() () + 37
>  7fff9dd11672 nsBaseAppShell::Run() () + 2e
>  7fff9eadfdde nsAppStartup::Run() () + 4a
>  7fff9eba272c XREMain::XRE_mainRun() () + a2c
>  7fff9eba333f XREMain::XRE_main(int, char**, 
> mozilla::BootstrapConfig const&) () + 7e7
>  7fff9eba34f6 XRE_main(int, char**, mozilla::BootstrapConfig 
> const&) () + f1
>  7fff9eba48ad mozilla::BootstrapImpl::XRE_main(int, char**, 
> mozilla::BootstrapConfig const&) () + 11
>  00411cb0 do_main(int, char**, char**) () + 20d
>  00411d66 main () + 7b
>  00411397 _start_crt () + 87
>  004112f8 _start () + 18
>  thread# 2 / lwp# 2 [Gecko_IOThread] -
>  7fffaf3fc70a _portfs () + a
>  7fff984c57fd evport_dispatch () + 18d
>  7fff984ad83c event_base_loop () + 25c
>  7fff9be24b42 
> base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () + a4
>  7fff9be25b05 MessageLoop::RunInternal() () + 13
>  7fff9be25d4d MessageLoop::Run() () + 37
>  7fff9be3f4c7 base::Thread::ThreadMain() () + 14d
>  7fff9be246e9 ThreadFunc(void*) () + a
>  7fffaf3f613c _thrp_setup (7fffae270240) + 6c
>  7fffaf3f6450 _lwp_start ()
> - thread# 4 / lwp# 4 [Timer] -
>  7fffaf3f6497 __lwp_park () + 17
>  7fffaf3ef94b cond_wait_queue (559f48, 559f28, 7fff9840d9f0) + 5b
>  7fffaf3efd9d cond_wait_common (559f48, 559f28, 7fff9840d9f0) + 1dd
>  7fffaf3f00fa __cond_timedwait (559f48, 559f28, 7fff9840daf0) + ba
>  7fffaf3f0161 cond_timedwait (559f48, 559f28, 7fff9840daf0) + 31
>  7fffaf3f01a0 pthread_cond_timedwait (559f48, 559f28, 7fff9840daf0) 
> + 10
>  00412c30 
> mozilla::detail::ConditionVariableImpl::wait_for(mozilla::detail::MutexImpl&, 
> mozilla::BaseTimeDuration const&) 
> () + 14a
>  7fff9b915e88 TimerThread::Run() () + fe
>  7fff9b910404 nsThread::ProcessNextEvent(bool, bool*) () + 63a
>  7fff9b90ec55 NS_ProcessNextEvent(nsIThread*, bool) () + 2d
>  000

Re: [OpenIndiana-discuss] Firefox and Thunderbird

[Carsten Grzemba via openindiana-discuss]

Am 25.03.21 17:25 schrieb Apostolos Syropoulos  : 
> 
> The site says that version has firefox version 68.12.0 dated
> March 16, 2021 11:42:47 AM Obviously something is wrong
> A.S.
> --
> Apostolos Syropoulos
> Xanthi, Greece
> 
just in the moment I refreshed the repo.
 -- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Firefox and Thunderbird

[Carsten Grzemba via openindiana-discuss]

Hi,

to the repository 

http://pkg.toc.de/userland
 I added thunderbird78.8.1 and firefox78.9.0 (Thanks to Geoff)

If you give it a try, keep in mind that there will a new profile used. How the 
old profile can migrated to new I don't know in the moment.

Happy testing
-- 
Carsten Grzemba
Tel.: +49 3677 64740
Mobil: +49 171 9749479
Email: carsten.grze...@contac-dt.de
contac Datentechnik GmbH
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Firefox68esr for testing

[Carsten Grzemba via openindiana-discuss]

Am 22.03.21 11:57 schrieb Stephan Althaus  : 
> 
> On 03/22/21 11:45 AM, Apostolos Syropoulos via openindiana-discuss wrote:
> >Of course I am using 78.8.0esr (64-bit)
> >
> >--
> >Apostolos Syropoulos
> >Xanthi, Greece
> >
> >
> >
> >
> >___
> >openindiana-discuss mailing list
> >openindiana-discuss@openindiana.org
> >https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> At
> 
> https://belnumizmatika.by/
> 
> no crash here. FF 78.8.0 esr. hm.
> 
it is possible, that is also related to libspeechd.so which is mostly pulledin 
by Qt5.
 
> 
> 
> 
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Firefox68esr for testing

[Carsten Grzemba via openindiana-discuss]

If you have a core file, please send:

$ pstack core | c++filt | head -100

Am 22.03.21 11:45 schrieb Apostolos Syropoulos via openindiana-discuss  
: 
> 
> 
> Of course I am using 78.8.0esr (64-bit)
> 
> --
> Apostolos Syropoulos
> Xanthi, Greece
> 
> 
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Firefox68esr for testing

[Carsten Grzemba via openindiana-discuss]

Am 22.03.21 09:35 schrieb Carsten Grzemba via openindiana-discuss  
: 
> 
> 
> 
> Am 19.03.21 05:33 schrieb Bill Sommerfeld : 
> > 
> > On 03/18/21 21:03, Joshua M. Clulow via openindiana-discuss wrote:
> > >>(if I'm reading it correctly, it trapped in strlen()).
> > >
> > >It does look that way. If you add a "-v" to ::findstack you might see
> > >arguments, which can be helpful. If there aren't arguments this
> > >program may need to be built with -msave-args.
> > No arguments in the firefox code, but we do have them in libc and that lets 
> > us get the siginfo_t and ucontext_t out of 
> > sigacthandler()/call_user_handler():
> > 
> > [ 7fffa8fee070 libc.so.1`_lwp_kill+0xa() ]
> > 7fffa8fee0a0 libc.so.1`raise+0x1e(b)
> > 7fffa8fee0f0 libxul.so`nsProfileLock::FatalSignalHandler+0xcb()
> > 7fffa8fee180 libxul.so`WasmTrapHandler+0xf2()
> > 7fffa8fee190 libc.so.1`__sighndlr+6()
> > 7fffa8fee230 libc.so.1`call_user_handler+0x1db(b, 7fffa8fee608, 
> > 7fffa8fee2a0)
> > 7fffa8fee280 libc.so.1`sigacthandler+0xee(b, 7fffa8fee608, 7fffa8fee2a0)
> > 7fffa8fee7f0 libc.so.1`strlen+0x30()
> > 7fffa8fee860 libspeechd.so.2.6.0`spd_list_synthesis_voices+0x1d()
> > 7fffa8feeb80 
> > libxul.so`mozilla::dom::SpeechDispatcherService::Setup+0xc8()
> > 7fffa8feeb90 
> > libxul.so`mozilla::detail::RunnableMethodImpl >  void +0x27()
> > 7fffa8feec90 libxul.so`nsThread::ProcessNextEvent+0x63a()
> > 7fffa8feecc0 libxul.so`NS_ProcessNextEvent+0x2d()
> > 7fffa8feed00 
> > libxul.so`mozilla::ipc::MessagePumpForNonMainThreads::Run+0x116()
> > 7fffa8feed10 libxul.so`MessageLoop::RunInternal+0x13()
> > 7fffa8feed60 libxul.so`MessageLoop::Run+0x37()
> > 7fffa8feef70 libxul.so`nsThread::ThreadFunc+0xd8()
> > 7fffa8feefb0 libnspr4.so`_pt_root+0xcb()
> > 7fffa8feefe0 libc.so.1`_thrp_setup+0x6c(7fffab768a40)
> > 7fffa8feeff0 libc.so.1`_lwp_start()
> > 
> > > 7fffa8fee608::siginfo
> > signal 11 (SEGV)
> > code 1 (from kernel)
> > errno 0 (Error 0)
> > fault address = 0x0
> > trapno = 0
> > instruction address = 0x0
> > > 7fffa8fee2a0::ucontext
> > flags = 0xf 
> > link = 0x0
> > sigmask = 0x 0x 0x 0x
> > stack = sp 0x7fffa8faf000 size 0x4 flags 0
> > mcontext = 0x7fffa8fee2e0
> > > 7fffa8fee2a0::regs -u
> > %rax = 0x7fffa8fee7b8 %r8 = 0x0017
> > %rbx = 0x7fff9d1eed00 %r9 = 0x4543494f
> > %rcx = 0x %r10 = 0x0d53
> > %rdx = 0x0100 %r11 = 0x000a
> > %rsi = 0x %r12 = 0x
> > %rdi = 0x %r13 = 0x7fff9d1eed00
> > %r14 = 0x124d8e00
> > %r15 = 0x
> > 
> > %cs = 0x0053 %fs = 0x %gs = 0x
> > %ds = 0x004b %es = 0x004b %ss = 0x004b
> > 
> > %rip = 0x7fffaf35bab0 libc.so.1`strlen+0x30
> > %rbp = 0x7fffa8fee7f0
> > %rsp = 0x7fffa8fee788
> > 
> > %rflags = 0x00010246
> > id=0 vip=0 vif=0 ac=0 vm=0 rf=1 nt=0 iopl=0x0
> > status=
> > 
> > %gsbase = 0x
> > %fsbase = 0x7fffab768a40
> > %trapno = 0xe
> > %err = 0x4
> > 
> > Faulting instruction is:
> > libc.so.1`strlen+0x30: pcmpeqb (%rsi),%xmm0
> > 
> > %rsi is 0
> > 
> > my read: spd_list_synthesis_voices() is most likely calling strlen(NULL).
> > 
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> > 
> 
> 
> I get thist too, if I access Yandex.com with FF78. I will provide an FF78 
> build with -msave-args.
> -- 
> 

 
But if it seems it's a problem of libspeechd, if I remove this lib it works. 

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

Re: [OpenIndiana-discuss] Firefox68esr for testing

[Carsten Grzemba via openindiana-discuss]

Am 19.03.21 05:33 schrieb Bill Sommerfeld  : 
> 
> On 03/18/21 21:03, Joshua M. Clulow via openindiana-discuss wrote:
> >>(if I'm reading it correctly, it trapped in strlen()).
> >
> >It does look that way. If you add a "-v" to ::findstack you might see
> >arguments, which can be helpful. If there aren't arguments this
> >program may need to be built with -msave-args.
> No arguments in the firefox code, but we do have them in libc and that lets 
> us get the siginfo_t and ucontext_t out of 
> sigacthandler()/call_user_handler():
> 
> [ 7fffa8fee070 libc.so.1`_lwp_kill+0xa() ]
>  7fffa8fee0a0 libc.so.1`raise+0x1e(b)
>  7fffa8fee0f0 libxul.so`nsProfileLock::FatalSignalHandler+0xcb()
>  7fffa8fee180 libxul.so`WasmTrapHandler+0xf2()
>  7fffa8fee190 libc.so.1`__sighndlr+6()
>  7fffa8fee230 libc.so.1`call_user_handler+0x1db(b, 7fffa8fee608, 
> 7fffa8fee2a0)
>  7fffa8fee280 libc.so.1`sigacthandler+0xee(b, 7fffa8fee608, 7fffa8fee2a0)
>  7fffa8fee7f0 libc.so.1`strlen+0x30()
>  7fffa8fee860 libspeechd.so.2.6.0`spd_list_synthesis_voices+0x1d()
>  7fffa8feeb80 
> libxul.so`mozilla::dom::SpeechDispatcherService::Setup+0xc8()
>  7fffa8feeb90 
> libxul.so`mozilla::detail::RunnableMethodImpl  void +0x27()
>  7fffa8feec90 libxul.so`nsThread::ProcessNextEvent+0x63a()
>  7fffa8feecc0 libxul.so`NS_ProcessNextEvent+0x2d()
>  7fffa8feed00 
> libxul.so`mozilla::ipc::MessagePumpForNonMainThreads::Run+0x116()
>  7fffa8feed10 libxul.so`MessageLoop::RunInternal+0x13()
>  7fffa8feed60 libxul.so`MessageLoop::Run+0x37()
>  7fffa8feef70 libxul.so`nsThread::ThreadFunc+0xd8()
>  7fffa8feefb0 libnspr4.so`_pt_root+0xcb()
>  7fffa8feefe0 libc.so.1`_thrp_setup+0x6c(7fffab768a40)
>  7fffa8feeff0 libc.so.1`_lwp_start()
> 
> > 7fffa8fee608::siginfo
>  signal 11 (SEGV)
>  code 1 (from kernel)
>  errno 0 (Error 0)
>  fault address = 0x0
>  trapno = 0
>  instruction address = 0x0
> > 7fffa8fee2a0::ucontext
>  flags = 0xf 
>  link = 0x0
>  sigmask = 0x 0x 0x 0x
>  stack = sp 0x7fffa8faf000 size 0x4 flags 0
>  mcontext = 0x7fffa8fee2e0
> > 7fffa8fee2a0::regs -u
> %rax = 0x7fffa8fee7b8 %r8 = 0x0017
> %rbx = 0x7fff9d1eed00 %r9 = 0x4543494f
> %rcx = 0x %r10 = 0x0d53
> %rdx = 0x0100 %r11 = 0x000a
> %rsi = 0x %r12 = 0x
> %rdi = 0x %r13 = 0x7fff9d1eed00
>  %r14 = 0x124d8e00
>  %r15 = 0x
> 
> %cs = 0x0053 %fs = 0x %gs = 0x
> %ds = 0x004b %es = 0x004b %ss = 0x004b
> 
> %rip = 0x7fffaf35bab0 libc.so.1`strlen+0x30
> %rbp = 0x7fffa8fee7f0
> %rsp = 0x7fffa8fee788
> 
> %rflags = 0x00010246
>  id=0 vip=0 vif=0 ac=0 vm=0 rf=1 nt=0 iopl=0x0
>  status=
> 
> %gsbase = 0x
> %fsbase = 0x7fffab768a40
> %trapno = 0xe
>  %err = 0x4
> 
> Faulting instruction is:
> libc.so.1`strlen+0x30: pcmpeqb (%rsi),%xmm0
> 
> %rsi is 0
> 
> my read: spd_list_synthesis_voices() is most likely calling strlen(NULL).
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 


I get thist too, if I access Yandex.com with FF78. I 
will provide an FF78 build with -msave-args.

-- 




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

Re: [OpenIndiana-discuss] Firefox68esr for testing

[Carsten Grzemba via openindiana-discuss]

Am 17.03.21 15:23 schrieb Stephan Althaus  : 
> 
> On 03/17/21 03:13 PM, Carsten Grzemba via openindiana-discuss wrote:
> >>Is this still the case with 78 ESR ?
> >>
> >the same, I will upload FF78 in the moment so you can test this also. But my 
> >first impression is needs more resources (RAM), less performance, at least 
> >on my not so young laptop with 8GRAM;)
> > 
> 
> This sounds to me we might want more than 1 firefox release to choose from
> like recently done with nvidia graphics driver ?
> 

Please test, FF68 is EOL since summer 2020, so we have to go forward and the 
next ESR will come this summer.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Firefox68esr for testing

[Carsten Grzemba via openindiana-discuss]

Am 17.03.21 14:25 schrieb Stephan Althaus  : 
> 
> On 03/17/21 02:09 PM, Gary Mills wrote:
> >On Tue, Mar 16, 2021 at 04:27:31PM +0100, Carsten Grzemba via 
> >openindiana-discuss wrote:
> >>I made available a firefox package 68esr for testing
> >>
> >>Unfortunately for the moment there is a restriction!
> >>There is a setting in /etc/system necessary:
> >>
> >>set _userlimit=0x7fffc000
> >>
> >>whithout this, FF will raise a assertion in JS code.
> >It sounds as if we need the illumos developers to make the appropriate
> >change to the illumos kernel or to the linker so that this setting
> >will not be necessary. An illumos bug report would be a good starting
> >point.
> >
> >
> Hm..
> 
> How is this handled with Solaris and solaris-userland ?
> 
Solaris 11.4 x86 has changed his VA managment to be more like Linux and 
friends. Only for Sparc is a special mapfile and modified linker neccessary. 
Sparc has secure in silicon which uses also something like tagged pointer.
 
> 
> 
> 
> Is this still the case with 78 ESR ?
> 
the same, I will upload FF78 in the moment so you can test this also. But my 
first impression is needs more resources (RAM), less performance, at least on 
my not so young laptop with 8GRAM ;)
 
> 
> 
> 
> Stephan
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Firefox68esr for testing

[Carsten Grzemba via openindiana-discuss]

I made available a firefox package 68esr for testing

Unfortunately for the moment there is a restriction!
There is a setting in /etc/system necessary:

set _userlimit=0x7fffc000

whithout this, FF will raise a assertion in JS code.

If you want to give it a try then:

$ pfexec pkg set-publisher http://pkg.toc.de/userland userland
$ pfexec pkg set-publisher --non-sticky openindiana.org
$ pfexec pkg install firefox@68.12.0 firefox-bookmarks@68.12.0

Many thanks to
Till for the powerfull build server,
Alan for the valuable hints about the VM configuration,
the mozilla community for hints to adapt the code for illumos

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

Re: [OpenIndiana-discuss] after Installation, no X11?

[Carsten Grzemba via openindiana-discuss]

>I use SunRay on OI since some years and have contribute an install guide on 
>docs.openindiana.org.

> 
> Actually it's still only a PR:
> https://github.com/OpenIndiana/oi-docs/pull/150
> If you'll fix the existing conflict, I will integrate it.
> 
> Regards,
> Andreas
> 
Done

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

Re: [OpenIndiana-discuss] after Installation, no X11?

[Carsten Grzemba via openindiana-discuss]

Am 24.02.21 23:44 schrieb "Rolf M. Dietze"  : 
> 
> 
> Quoting Tim Mooney via openindiana-discuss 
> :
> 
> >In regard to: Re: [OpenIndiana-discuss] after Installation, no X11?, Rolf...:
> >
> >>Hi,
> >>yes, got it running. xdm login, twm as window manager. Fast and
> >>smart:)
> >>
> >>As I started up with a text console only, Andreas and Carsten
> >>on this list told me to do a pkg install mate_install and start
> >>the SMF-service for lightdm. With a little nvidia driver update
> >>all worked fine. Since I like fast minimalistik desktops that do
> >>not consume the compute power for windows decorations, I did:
> >>pkg install twm
> >>pkg install xdm
> >>copied th svc-lightdm method to svc-xdm, set it up for xdm, reseted
> >>the xdm-fmri as was installed alongside by pkg install xdm, pointed
> >>it to the freshly createt login-xdm. (guess I could have used the
> >>default anyway, it just starts xdm so:)
> >
> >I'm glad you found a solution that works, but I think there might
> >have been an easier way that didn't involve messing with SMF at all.
> >
> >Lightdm is capable of launching any "session" it knows about. What
> >exactly a "session" is depends on the desktop environment, but for
> >the "xterm" failsafe, it's just an xterm.
> >
> >Sessions are defined in a .desktop text file in /usr/share/xsessions/
> >The .desktop file format is documented here:
> >
> > https://specifications.freedesktop.org/desktop-entry-spec/latest/
> >
> >Using the 'mate.desktop' and 'xterm.desktop' as examples, someone
> >that knows TWM well could probably create a twm.desktop, drop it into
> >/usr/share/xesssions/, and then continue to use lightdm as the login
> >(rather than XDM), but get it to launch your twm session.
> >
> >I know that Ubuntu and some other Linux distros that use lightdm have
> >a twm.desktop configured for their distro. That might also serve as
> >a useful example.
> >
> >Either way, if you know how to get twm to "launch" after X is already
> >running, it's probably a lot easier to just make it a selectable choice
> >from Lightdm than it is to create a different SMF.
> >
> >Hope this helps,
> [..]
> well yes and no. I do not really like the look and feel of lightdm as so
> with the gdm-login, which specially denied me using cde once gnome was
> tried out and judged to be to performanceconsuming. Same goes with the
> unity stuff and debian as well. I normally use cde-login as I am still
> supporting sunray at some places, I love CDE so
> With FreeBSD I came back to xdm as a login manager and configured it to
> look as desired, with some scripting around one can dynamically select
> the windows manager to start with xdm as well. With that and having an
> identical login manager look and feel around FreeBSD-, ubuntu-, debian-
> and now the first OI-boxes. It is simply far simpler to just change SMF
> than to have a bunch full of differnt login managers on whatever boxes.
> For the OI testbox that I set up, OI feels simply great, thanks for all
> the work and time put in OI. Next step is bhyve, Stephan Althaus just
> posted his experience with that.
> 
> Right now I am fiddling with CDE. In fact, sunray on OI works? If, please
> give me a pointer, I'd love to put that on an OI box. Is there a newer
> firefox than 60.9.0? Firefox could be a show stopper for OI as a desktop
> replacement because of the old certificates. Yes sure, I could fence a
> more recent version of that power consuming firefox in some newer linux
> branded zone. That goes for me, assumingly for most of the readers of that
> list, but not for all users I have to support.
> 
I use SunRay on OI since some years and have contribute an install guide on 
docs.openindiana.org.
SunRay works, but with the old GDM.

At the moment I work on building an current firefox 68 or 78, but for now the 
bits simply end in core dump.
Unfortunatly build in debug mode ends in link errors and the c++ objects have 
also no reference to the source files.
 
> 
> 
> 
> Rolf
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] after Installation, no X11?

[Carsten Grzemba via openindiana-discuss]

# pkg install mate_install 

should do the job

Am 23.02.21 20:20 schrieb "Rolf M. Dietze"  : 
> 
> Hi,
> after a fresh install on a new box, the installation
> finished with a reboot and a login on the text console.
> 
> So, how to install X11, is there a meta package name as
> in oracle solaris were there is a group/system/solaris-desktop
> to install.
> Any tips on what might have gone wrong an how to add
> missing software as a bundle?
> 
> Rolf
> 
> 
> 
> ___
> 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

Re: [OpenIndiana-discuss] Is the Atheros AR9462 WiFi card supported?

[Carsten Grzemba via openindiana-discuss]

Am 21.01.21 03:23 schrieb John D Groenveld  : 
> 
> In message , Chris writes:
> >Ive got an Atheros AR9462 WiFi card in my fresh OI install.
> >Is it supported? If not, is there a driver similar I can hack
> >on?
> 
> No and maybe:
> http://pkg.openindiana.org/hipster/manifest/0/driver%2Fnetwork%2Fath%400.5.11%2C5.11-2020.0.1.20243%3A20210120T012047Z>
> 
> You'll want to read the illumos DDI/DDK docs:
> https://illumos.org/books/wdd/partintro-1.html#partintro-1>
> 
> Happy hacking,
> John
> groenv...@acm.org
> 
Tried to extend the driver for "AR9287 Wireless Network Adapter (PCI-Express)", 
but without success so far, it attached and opens but found no signals etc.
There I have to less knowledge how Wifi works.
 
> 
> 
> ___
> 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

Re: [OpenIndiana-discuss] local pkg repo error

[Carsten Grzemba via openindiana-discuss]

Am 14.01.21 21:08 schrieb Pierfrancesco Caci  : 
> 
> The "rebuild" did the trick, but how do I specify to pkg to install the
> version from my repo instead of the official one? The version is the same
> 
> 
> On Thu, Jan 14, 2021 at 8:39 PM Aurélien Larcher 
> wrote:
> 
> > You can even
> >
> > pkgrepo -s /path/to/repo list
> >
> > to make sure it was published where you think it was.
> >
> > On Thu, 14 Jan 2021, 8:10 pm Aurélien Larcher,  > >
> > wrote:
> >
> > > You can try to:
> > >
> > > pkgrepo -s /path/to/repo rebuild
> > >
> > > to update the repo index.
> > >
> > > On 1/14/21, Pierfrancesco Caci  wrote:
> > > > Hello,
> > > > I'm trying to learn how to recompile a package and put it in a local
> > > repo.
> > > > I've followed the ips-dev-guide.pdf for setting up the repo, and the
> > > > "Getting started with the Userland Consolidation" from github.
> > > > I got the package to compile and copy to the repo (gmake publish), but
> > > when
> > > > I try to search for that package with "pkg search sudo" I get this
> > error:
> > > >
> > > > pkg: Some repositories failed to respond appropriately:
> > > > ik5pvx-repo:
> > > > file protocol error: code: E_FTP_WEIRD_PASS_REPLY (11) reason: Search
> > > > temporarily unavailable.
> > > > Repository URL: 'file:///export/home/ik5pvx/my-repo'. (happened 4
> > times)
> > > >
> > > > What am I doing wrong?
> 
its normal, search do not work on file repositories, only on pkg server.
 
> 
> 
> > > >
> > > > Pf
> > > >
> > > > --
> > > > Pierfrancesco Caci, ik5pvx
> > > > ___
> > > > openindiana-discuss mailing list
> > > > openindiana-discuss@openindiana.org
> > > > https://openindiana.org/mailman/listinfo/openindiana-discuss
> > > >
> > >
> > >
> > > --
> > > ---
> > > Praise the Caffeine embeddings
> > >
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> >
> 
> 
> -- 
>  Pierfrancesco Caci, ik5pvx
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 

you shoud set up your publisher in this kind:
builder@oi-dev:/code/github/openindiana/oi-userland/components/developer/rust$ 
pkg publisher
PUBLISHER TYPE STATUS P LOCATION
userland origin online F file:///code/github/openindiana/oi-userland/i386/repo/
openindiana.org (non-sticky) origin online T http://pkg.openindiana.org/hipster/

the order is important an can set with the --search-before option of 'pkg 
set-publisher'.
if you create a newer version you can fail on the userland-incorporation 
package which define the versions of packages if they installed. Than you have 
to unlock the version locking of userland-incorporation whith
$ sudo pkg change-facet 
which is the facet you have to unlock can you check whith
$ pkg contents -m userland-incorporation | grep 
 
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Tasks to focus on -- firefox

[Carsten Grzemba via openindiana-discuss]

Am 08.01.21 10:25 schrieb "Joshua M. Clulow"  : 
> 
> On Thu, 7 Jan 2021 at 23:34, Carsten Grzemba via openindiana-discuss
>  wrote:
> > > >On 07.01.21 23:47, Joshua M. Clulow via openindiana-discuss wrote:
> > > >>If you hit any trouble with Rust, I'd love to hear about it! We have
> > > >>a good relationship with the Rust project itself, so we should be able
> > > >>to get things fixed as they arise, without needing to float additional
> > > >>patches.
> > I try to build firefox 78esr for openindiana. The problems with Rust are 
> > much smaller than a while ago.
> 
> I took a spin at building Firefox last year, and while I didn't get a
> complete build finished (ran out of time) it was honestly easier to
> get master to build than ESR. The main branch usually uses updated
> crates, and thus tends to have _better_ support for illumos than the
> older ESR branches.
> 
> > But I stopped to use the rustc installed with rustup because this use a 
> > toolchain naming like x86_64-unknown-illumos.
> >
> > For that the rustc sources build instruction have to extent for target_os 
> > "solaris" to target_os "illumos", which is an additional effort.
> >
> > So I updated the oi-userland build reciept for rust to provide an newer 
> > version (1.41.1) where the target tripple x86_64-sun-solaris is used.
> > So there are no patching of lib.rs and others is necessary.
> > Or it is possible with rustup to get the target toolchain 
> > x86_64-sun-solaris also?
> 
> The old "sun-solaris" targets are not really being maintained by the
> illumos community at this point -- either in the Rust toolchain
> itself, or in the crates in the Rust ecosystem at large. I would
> recommend using the illumos target and getting any build issues fixed
> upstream in whatever crates have remaining platform-specific issues.
> 
> I and some other folks have been doing that sort of thing a lot
> throughout 2019-2020. Most or all of our patches and testing are for
> the illumos target, even if the Solaris targets sometimes also come
> along for the ride.
> 
> I think it'd be best if OI ships an illumos target toolchain for Rust,
> rather than the increasingly obsolete solaris target. Then we're all
> testing and working on the same bits!
> 
> 
> Cheers.
> 
> -- 
> Joshua M. Clulow
> http://blog.sysmgr.org
> 

Some other findings related buld FF on OI
- update ICU, if we want use system ICU 

- update mozilla-nss, if we want system-nss
- update rust
- if we use system-sqlite3, in sqlite3 libsqlite-3 2 symbols not exported 
because these missing in mapfile
these all are already in my repository on github



- readelf (2.34) of our binutil package is unable to read the libxul.so, 
readelf (2.33) of Solaris 11.4 can it read. updated readelf (2.35.2) reports 
less errors but fails also.

 

I deceide to use GCC9 because the trouble to compile with clang was bigger, 
GCC7 stopped with a suspicouse memory allocation error.


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

Re: [OpenIndiana-discuss] Tasks to focus on

[Carsten Grzemba via openindiana-discuss]

Am 08.01.21 05:15 schrieb Chris  : 
> 
> On 2021-01-07 19:06, Till Wegmueller wrote:
> >On 07.01.21 23:47, Joshua M. Clulow via openindiana-discuss wrote:
> >>On Thu, 7 Jan 2021 at 13:57, Till Wegmueller  wrote:
> >>>I will get myself a Physical host with Hetzner with a ton of RAM and CPU
> >>>so we can dedicate some zones and VM's to OpenIndiana building packages.
> >>>Olaf has been working on a revised Jenkins pipeline which fully
> >>>automates PR builds and allows to push them into seperate repos for
> >>>testing with others. So others can just use that repo for testing and
> >>>don't need to build. We will implement that Capability there.
> >>
> >>Before you spend any money, or at least in parallel with doing so, I
> >>would encourage you to see if Fosshost will provide some resources for
> >>the project. They have reached out to illumos in the past, and I
> >>think OpenIndiana meets all of their eligibility criteria (open
> >>source, no commercial backing, etc):
> >>
> >> https://fosshost.org
> >>
> >>It seems they will provide one or more virtual machines to projects
> >>for hosting of web resources and builds and such.
> >>
> >
> >Oh nice will have a talk with them also. That one server is not just for OI, 
> >it is
> >also to replace my failed HomeLab server and move stuff from that out to a 
> >DC. And
> >then also to host some company resources and others. But Of course I would 
> >not
> >need that much RAM for that.
> >
> >Let's see what they can do. But having infrastructure under our control is 
> >the
> >Goal. Evercity is doing a very good sponsoring but we need to do updates to 
> >the
> >Jenkins infrastructure and redo the setup. So having somewhere where we can 
> >do
> >that without needing to burden work onto others is one of our goals with 
> >this. And
> >we will also need a couple of package servers.
> You might also be interested in what Oregon State University is offering
> (free to opren source && includes IPv6)
> https://osuosl.org/services/hosting/
> 
> >
> >>>We also talked about making a rustup.mk which will use jmclulows rustup
> >>>work to bootstrap a rust compiler to build rust software and rust itself.
> >>
> >>If you hit any trouble with Rust, I'd love to hear about it! We have
> >>a good relationship with the Rust project itself, so we should be able
> >>to get things fixed as they arise, without needing to float additional
> >>patches.
> 

I try to build firefox 78esr for openindiana. The problems with Rust are much 
smaller than a while ago. 
 
But I stopped to use the rustc installed with rustup because this use a 
toolchain naming like x86_64-unknown-illumos.
 
For that the rustc sources build instruction have to extent for target_os 
"solaris" to target_os "illumos", which is an additional effort.
 
So I updated the oi-userland build reciept for rust to provide an newer version 
(1.41.1) where the target tripple x86_64-sun-solaris is used. 
 
So there are no patching of lib.rs and others is necessary. 
Or it is possible with rustup to get the target  toolchain x86_64-sun-solaris 
also?
  
 

> 
> 
> >
> >Will let you know how it went in any case. I expect no big problems though.
> >
> >-Till
> >
> >___
> >openindiana-discuss mailing list
> >openindiana-discuss@openindiana.org
> >https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> -- 
> ~40yrs of UNIX and counting
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
-- 
Carsten Grzemba
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] WPA2 support

[Carsten Grzemba via openindiana-discuss]

Am 05.03.20 17:18 schrieb Marc Lobelle  : 
> 
> Dear all,
> 
> I observed several times than my notebook (running OI-hipster 2019.04) 
> could not connect to the WIFI: it remains in the "connecting" stage. 
> Recently, I discovered that the corresponding access points were using 
> WPA2 and not WPA. Is this supported by OI-hipster? What shoud I do. It 
> is really annoying because my current smart phone, that I use as access 
> point when I do not have any network, is one of the WPA2-only APs ?
> 
I use since many years OI with urtwn driver with my Android Smartphone as AP, 
it works with WPA2 PSK there.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] SunRay on OI/Hipster

[Carsten Grzemba via openindiana-discuss]

On 19.08.19 12:34, Jonathan Adams   wrote: 
> 
> 
> GDM from here? :
> 
> https://github.com/GNOME/gdm
> 
> 

The simpliest way is use GDM from oi-userland before it was marked obsolete. 
 

 
so what I did on oi-userland 


remove or recommit git commits related Remove gdm, metacity, ...; 
Commit messages:

Remove gnome-session 
Remove gnome-menus 
Remove gnome-panel 
Remove libgnomekbd 
Remove gnome-desktop 
Remove gdm 
Remove metacity 
libgweather: update to 3.24.1 
gnome/config/gconf 




 update COMPONENT_REVISION 


unlock version

pkg change-facet facet.version-lock.library/desktop/gnome-desktop=false
pkg change-facet facet.version-lock.library/desktop/gnome-menus=false
pkg change-facet facet.version-lock.gnome/gnome-session=false pkg change-facet 
facet.version-lock.system/display-manager/gdm=false
pkg change-facet version-lock.library/desktop/libgweather=false
pkg change-facet version-lock.gnome/window-manager/metacity=false 

build and install gnome-desktop 
build and install gnome-menus 
install libwnck-1.0

pkg install libwnck
pkg install libbonboui
pkg install gnome-themes-standard 

build and install gweather@2.30.3 
build and install gnome-session@2.32.1 
build and install gnome-panel@2.32.1 
build and install metacity@2.30.3 
build and install gdm@2.30.7 
build and install libgnomekbd@2.30.0 
build and install gnome-settings-daemon@2.32.1 
build and install xscreensaver 32bit because of 32bit PAM modules for 
SUNRay  

 
 

> 
> 
> 
> (https://github.com/GNOME/gdm )
> 
> 
> might be worth the pet project to check if it will work. thanks
> 
> Jon
> 
> 
> 
> On Mon, 19 Aug 2019 at 10:48, Carsten Grzemba  wrote:
> 
> > 
> > 
> > On 19.08.19 11:29, Jonathan Adams   wrote: 
> > > 
> > > 
> > > so a standard install + Mate desktop could possibly work?
> > > 
> > 
> > no 
> >  
> > disable lightdm and build and install the GDM packages with newer versions 
> > than in hipster repo. There is some work, because hipster-repo has set this 
> > packages to '--o' (obsolete)
> >  
> >  
> > 
> > > 
> > > 
> > > 
> > > 
> > > It'd be a complete shame to have to dispose of 300+ Sunrays (including a 
> > > dozen SunRay 3+ boxes)
> > > 
> > > Jon
> > > 
> > > P.S. we might be closing some offices in a couple of months, and will 
> > > probably be losing the SunRays if that is the case, is anyone interested 
> > > in taking possession of any of them? (contact me off list)
> > > 
> > > 
> > > 
> > > On Mon, 19 Aug 2019 at 10:26, Carsten Grzemba via openindiana-discuss 
> > >  wrote:
> > > 
> > > > You can use SunRay on latest Hipster if you review GDM. Mate desktop 
> > > > can be used. But the Firefox 60 is a little bit slow on filling 
> > > > textareas or forms.
> > > > 
> > > > It is like it refresh the whole page an every keystroke.
> > > > 
> > > > 
> > > > 
> > > > On 19.08.19 11:03, Jonathan Adams  wrote: 
> > > > 
> > > > > 
> > > > 
> > > > > Hi everyone,
> > > > 
> > > > > 
> > > > 
> > > > > we used to run our SunRays on Solaris 10, back in the day, and then 
> > > > > moved
> > > > 
> > > > > to Centos in order to get access to updated desktop apps (firefox, 
> > > > > chrome,
> > > > 
> > > > > wine, xrdp mostly).
> > > > 
> > > > > 
> > > > 
> > > > > We obviously now have issues in that the gtk+ on Centos is ancient and
> > > > 
> > > > > causes the latest Firefox to crash for some windows (print, "save as" 
> > > > > ...).
> > > > 
> > > > > 
> > > > 
> > > > > I'd really like to move back to running them in the Solaris/OI world.
> > > > 
> > > > > 
> > > > 
> > > > > Do you know if it is still possible to run the SunRays on the latest
> > > > 
> > > > > version of OI/Hipster, and if so does anyone have a guide/walkthrough?
> > > > 
> > > > > 
> > > > 
> > > > > Thanks
> > > > 
> > > > > 
> > > > 
> > > > > Jon
> > > > 
> > > > > ___
> > > > 
> > > > > openindiana-discuss mailing list
> > > > 
> > > > > openindiana-discuss@openindiana.org
> > > > 
> > > > > https://openindiana.org/mailman/listinfo/openindiana-discuss
> > > > 
> > > > > 
> > > > 
> > > > -- 
> > > > 
> > > > Carsten
> > > > 
> > > > ___
> > > > 
> > > > openindiana-discuss mailing list
> > > > 
> > > > openindiana-discuss@openindiana.org
> > > > 
> > > > https://openindiana.org/mailman/listinfo/openindiana-discuss
> > > >  
> > > 
> > >  
> > > 
> > -- 
> > Carsten 
> 
>  
> 
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] SunRay on OI/Hipster

[Carsten Grzemba via openindiana-discuss]

On 19.08.19 11:29, Jonathan Adams   wrote: 
> 
> 
> so a standard install + Mate desktop could possibly work?
> 

no 
 
disable lightdm and build and install the GDM packages with newer versions than 
in hipster repo. There is some work, because hipster-repo has set this packages 
to '--o' (obsolete)
 
 

> 
> 
> 
> 
> It'd be a complete shame to have to dispose of 300+ Sunrays (including a 
> dozen SunRay 3+ boxes)
> 
> Jon
> 
> P.S. we might be closing some offices in a couple of months, and will 
> probably be losing the SunRays if that is the case, is anyone interested in 
> taking possession of any of them? (contact me off list)
> 
> 
> 
> On Mon, 19 Aug 2019 at 10:26, Carsten Grzemba via openindiana-discuss 
>  wrote:
> 
> > You can use SunRay on latest Hipster if you review GDM. Mate desktop can be 
> > used. But the Firefox 60 is a little bit slow on filling textareas or forms.
> > 
> > It is like it refresh the whole page an every keystroke.
> > 
> > 
> > 
> > On 19.08.19 11:03, Jonathan Adams  wrote: 
> > 
> > > 
> > 
> > > Hi everyone,
> > 
> > > 
> > 
> > > we used to run our SunRays on Solaris 10, back in the day, and then moved
> > 
> > > to Centos in order to get access to updated desktop apps (firefox, chrome,
> > 
> > > wine, xrdp mostly).
> > 
> > > 
> > 
> > > We obviously now have issues in that the gtk+ on Centos is ancient and
> > 
> > > causes the latest Firefox to crash for some windows (print, "save as" 
> > > ...).
> > 
> > > 
> > 
> > > I'd really like to move back to running them in the Solaris/OI world.
> > 
> > > 
> > 
> > > Do you know if it is still possible to run the SunRays on the latest
> > 
> > > version of OI/Hipster, and if so does anyone have a guide/walkthrough?
> > 
> > > 
> > 
> > > Thanks
> > 
> > > 
> > 
> > > Jon
> > 
> > > ___
> > 
> > > openindiana-discuss mailing list
> > 
> > > openindiana-discuss@openindiana.org
> > 
> > > https://openindiana.org/mailman/listinfo/openindiana-discuss
> > 
> > > 
> > 
> > -- 
> > 
> > Carsten
> > 
> > ___
> > 
> > openindiana-discuss mailing list
> > 
> > openindiana-discuss@openindiana.org
> > 
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> >  
> 
>  
> 
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] SunRay on OI/Hipster

[Carsten Grzemba via openindiana-discuss]

You can use SunRay on latest Hipster if you review GDM. Mate desktop can be 
used. But the Firefox 60 is a little bit slow on filling textareas or forms.
It is like it refresh the whole page an every keystroke.

On 19.08.19 11:03, Jonathan Adams   wrote: 
> 
> Hi everyone,
> 
> we used to run our SunRays on Solaris 10, back in the day, and then moved
> to Centos in order to get access to updated desktop apps (firefox, chrome,
> wine, xrdp mostly).
> 
> We obviously now have issues in that the gtk+ on Centos is ancient and
> causes the latest Firefox to crash for some windows (print, "save as" ...).
> 
> I'd really like to move back to running them in the Solaris/OI world.
> 
> Do you know if it is still possible to run the SunRays on the latest
> version of OI/Hipster, and if so does anyone have a guide/walkthrough?
> 
> Thanks
> 
> Jon
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
-- 
Carsten
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Notepad mouse not working after upgrade

[Carsten Grzemba]

On 25.03.19 16:08, Carsten Grzemba   wrote: 
> 
> I upgraded to 
> osnet-incorporation@0.5.11-2018.0.0.1814
> but there the notebook touchpad mouse is not working, only the external usb 
> connected mouse.
> Any hints what to check to fix the problem?
> 
> Thanks
> 
The Xorg.0.log (not working) and Xorg.0.log.old (working) show no difference.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Notepad mouse not working after upgrade

[Carsten Grzemba]

I upgraded to 
osnet-incorporation@0.5.11-2018.0.0.1814
but there the notebook touchpad mouse is not working, only the external usb 
connected mouse.
Any hints what to check to fix the problem?

Thanks
--
 
Carsten Grzemba
Tel.: +49 3677 64740
Mobil: +49 171 9749479
Email: carsten.grze...@contac-dt.de
contac Datentechnik GmbH
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Sun Rays might just be back on modern OI

[Carsten Grzemba]

On 03.02.19 18:51, Jim Klimov   wrote: 
> 
> On February 3, 2019 2:09:47 PM UTC, Gary Mills  wrote:
> >On Sun, Feb 03, 2019 at 10:54:37AM +, Jim Klimov wrote:
> >
> >> And on my side, I dug into why that venerable piece of software,
> >> the Sun DHCP server which I've actually used and liked, just up and
> >> died in illumos-gate some years back (ultimately leading to its
> >> removal), and what can be done about it.
> >
> >> Thanks to andyf I revived the SUNWdhcpd for the setup I maintain
> >> and had to recently update to modern OI releases, see
> >> http://www.jimklimov.com/2019/02/long-live-sunwdhcpd.html for
> >> details and caveats, and
> >> https://github.com/jimklimov/illumos-gate/tree/revive-SUNWdhcpd for
> >> equivalent codebase fix :)
> >
> >You don't need the Sun DHCP server to operate Sun Ray terminals. You
> >can use the ISC DHCP server instead. Here's what I used to use in the
> >ISC configuration file:
> >
> > # Sun Ray vendor options
> > option space NewT;
> > option NewT.AuthSrvr code 21 = ip-address;
> > ...
> > subnet 192.168.0.0 netmask 255.255.255.0 {
> > range 192.168.0.129 192.168.0.158;
> > option subnet-mask 255.255.255.0;
> > option broadcast-address 192.168.0.255;
> > option routers 192.168.0.1;
> > default-lease-time 600;
> > max-lease-time 7200;
> > if option vendor-class-identifier = "SUNW.NewT.SUNW" {
> > vendor-option-space NewT;
> > option NewT.AuthSrvr 130.179.16.87;
> > }
> > }
> >
> >This configuration specifies a dynamic IP address for the Sun Ray
> >terminal, and 130.179.16.87 as the IP address of the Sun Ray login
> >server. There's more that can be specified, but this is the minimum.
> >
> >The ISC configuration for Sun Ray terminals is all documented in
> >Sun documents, now presumably Oracle Solaris documents.
> 
> I suspected something of the kind =D
> 
> I mean, surely any standard DHCP server can send proper packets at proper 
> time, and nowadays a DNS setup could suffice, but the first thing (AFAIK) 
> people trying to install or update SRSS is not having a dependency package 
> for it, which is not too hard to work around but does complicate things. Also 
> SRSS wizards being able to configure the address range by telling the DHCP 
> server to do so was nice.
> 
> And there's guys like me (oh, maybe only me?) actually using it as a generic 
> DHCP server for a multi-subnet LAN of varied devices, not just Sun Rays, just 
> because it is nifty with the macros and we always did ;)
> 
> Anyhow, I had fun and learned something new as I scratched my long-standing 
> itch, and can delay migrating that config to lots of repetitive lines ix  n 
> ISC DHCP files for a few more years =)
> 
> Cheers,
> Jim
> 
I am suprised because I got not response for this problem:
 https://openindiana.org/pipermail/openindiana-discuss/2019-January/022692.html
 
I my experiance SunRay   SS do not work with lightdm. Is there a workaround?

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

[OpenIndiana-discuss] Sun Ray and ligthdm

[Carsten Grzemba]

I try to figure out if it possible to run SunRay with lightdm. At first it 
looks possible because gdm also uses ConsoleKit. 
In the moment I see in the logs and ConsoleKit history, that Seat will added 
but no login session starts. It will only add an 'empty' session:


1547650804.324 type=SEAT_ADDED : seat-id='utSunRaySeat12' seat-kind=1
1547719388.480 type=SEAT_SESSION_ADDED : seat-id='utSunRaySeat12' 
session-id='Session11' session-type='' display-type='' session-x11-display='' 
session-x11-display-device='' session-display-device='' 
session-remote-host-name='' session-is-local=FALSE session-unix-user=0 
session-creation-time=''

normaly should follow here:
1505312753.308 type=SEAT_SESSION_ADDED : seat-id='utSunRaySeat11' 
session-id='Session5' session-type='LoginWindow' display-type='utSunRay' 
session-x11-display=':11' session-x11-display-device='/dev/dtlocal' 
session-display-device=' ? ' session-remote-ost-name='' session-is-local=TRUE 
session-unix-user=50 session-creation-time='2017-09-13T14:25:47.347784Z'

I can't see that utxinit is called.
The DTU is still in OSD 26D state, no Xnewt is started.

I do not know if there is a direct communication between utsessiond and 
gnome-session-worker, which would be a showstopper.

I found a document on 
https://us-east.manta.joyent.com/jmc/public/opensolaris/ARChive/LSARC/2009/432/onepager-consolekit.txt
 which mentions that there is patch in ck-seat-tool necessary:

 Currently this program is added by a Solaris-specific patch to
 support the gdmdynamic program, needed for backwards compatibility.
 The Sun GNOME team is working with the external community to 
 upstream this feature.

I do not know if it is still necessary and which patch it is.

Xnewt do not knows the option -seat  and . Can I ignore this 
options or it is still possible to use Xorg for SunRay DTU's?

Has anyone more experiance with ConsoleKit?
--
 
Carsten


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

Re: [OpenIndiana-discuss] pkg install problem after update

[Carsten Grzemba]

If you do not get any hint of the failing package with 
# pkg install -v -v -v build-essential
you can install the packages listed by 
# pkg contents -r -m build-essential
step by step and see which package install is failing. The perhaps a remove of 
the old package before install the new may help.

On 10.01.19 13:08, Marianne Spiller   wrote: 
> 
> Hi,
> 
> after the colleagues moved our system to 2018.10 I get errors when I try 
> to work with oi-userland. The main problem at the moment is that I’m 
> not able to install the package build-essential with the error message 
> shown below (but I installed smartmontools without any issue, so pkg 
> install seems not to be a problem in general).
> 
> Please: what can I do to get my compiler back? :)
> 
> Cheers,
>  Marianne
> 
> 
> 
> 
> # uname -a
> SunOS zfs-2011 5.11 illumos-9b40c3052b i86pc i386 i86pc
> 
> # cat /etc/release
>  OpenIndiana Hipster 2018.10 (powered by illumos)
>  OpenIndiana Project, part of The Illumos Foundation (C) 
> 2010-2018
>  Use is subject to license terms.
>  Assembled 23 October 2018
> 
> 
> # pkg install pkg:/metapackages/build-essential@1.0-2018.0.0.13
> Creating Plan (Checking for conflicting actions): /
> Traceback (most recent call last):
>  File "/usr/bin/pkg", line 5678, in handle_errors
>  __ret = func(*args, **kwargs)
>  File "/usr/bin/pkg", line 5664, in main_func
>  pargs=pargs, **opts)
>  File "/usr/bin/pkg", line 2123, in install
>  display_plan_cb=display_plan_cb, logger=logger)
>  File "/usr/lib/python2.7/vendor-packages/pkg/client/client_api.py", 
> line 1558, in _install
>  logger=logger)
>  File "/usr/lib/python2.7/vendor-packages/pkg/client/client_api.py", 
> line 1446, in __api_op
>  logger=logger, **kwargs)
>  File "/usr/lib/python2.7/vendor-packages/pkg/client/client_api.py", 
> line 1317, in __api_plan
>  display_plan_cb=display_plan_cb)
>  File "/usr/lib/python2.7/vendor-packages/pkg/client/client_api.py", 
> line 1289, in __api_plan
>  for pd in api_plan_func(**kwargs):
>  File "/usr/lib/python2.7/vendor-packages/pkg/client/api.py", line 
> 1525, in __plan_op
>  log_op_end_all=True)
>  File "/usr/lib/python2.7/vendor-packages/pkg/client/api.py", line 
> 1153, in __plan_common_exception
>  six.reraise(exc_type, exc_value, exc_traceback)
>  File "/usr/lib/python2.7/vendor-packages/pkg/client/api.py", line 
> 1459, in __plan_op
>  self._img.make_install_plan(**kwargs)
>  File "/usr/lib/python2.7/vendor-packages/pkg/client/image.py", line 
> 4353, in make_install_plan
>  reject_list=reject_list)
>  File "/usr/lib/python2.7/vendor-packages/pkg/client/image.py", line 
> 4334, in __make_plan_common
>  self.__call_imageplan_evaluate(ip)
>  File "/usr/lib/python2.7/vendor-packages/pkg/client/image.py", line 
> 4247, in __call_imageplan_evaluate
>  ip.evaluate()
>  File "/usr/lib/python2.7/vendor-packages/pkg/client/imageplan.py", 
> line 3249, in evaluate
>  self.__merge_actions()
>  File "/usr/lib/python2.7/vendor-packages/pkg/client/imageplan.py", 
> line 3925, in __merge_actions
>  self.__find_all_conflicts()
>  File "/usr/lib/python2.7/vendor-packages/pkg/client/imageplan.py", 
> line 2807, in __find_all_conflicts
>  gone_fmris, fmri_dict)
>  File "/usr/lib/python2.7/vendor-packages/pkg/client/imageplan.py", 
> line 2441, in __update_act
>  assert act.attrs[act.key_attr] == key
> AssertionError
> 
> 
> pkg: This is an internal error in pkg(5) version fdaa5606. Please log a
> Service Request about this issue including the information above and 
> this
> message.
> 
> 
> 
> 
> 

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

Re: [OpenIndiana-discuss] hipster serial console via IPMI

[Carsten Grzemba]

On 25.10.18 23:03, Gary Mills   wrote: 
> 
> On Thu, Oct 25, 2018 at 06:15:15PM +, Carsten John wrote:
> > 
> > I'm struggeling to get serial over lan via IPMI on Supermicro
> > mainboards running with hipster.
> > 
> > As long as OI used grub I had a working setup.
> > 
> > After moving to BootForth this does not work any more.
> > 
> > The recipe at http://docs.openindiana.org/handbook/common-tasks/
> > does not work for me.
> 
> I have a system with a Supermicro motherboard and another with a Tyan
> motherboard. Both have a VGA device that converts text to serial,
> with a separate ethernet port dedicated to this device. I use ipmitool
> running on a third system to connect to these ethernet ports. Is that
> similar to what you have?
> 
> It shouldn't matter what operating system is running on the Supermicro
> system, at least for BIOS output. Do you get that output? Once the OS
> boots, it configures ttya and ttyb for I/O on the hardware serial ports.
> Putting the console on ttyc might solve your problems.
> 
> 

I use a Supermicro X10SLM-F which works with loader via SOL: 

BIOS:
 
 pre.western { font-family: "Courier New",monospace; }pre.cjk { font-family: 
"FZSongTi",monospace; }pre.ctl { font-family: "Courier New",monospace; }p { 
margin-bottom: 0.21cm; }a:link { }code.western { font-family: "Courier 
New",monospace; }code.cjk { font-family: "FZSongTi",monospace; }code.ctl { 
font-family: "Courier New",monospace; }

Terminal Type [VT-UTF8]Bits per second [115200]Data Bits [8]Parity [None]Stop 
Bits [1]Flow Control [None]VT-UTF8 Combo Key Support [Enabled]Recorder Mode 
[Disabled]Resolution 100x31 [Enabled]Legacy OS Redirection Resolution 
[80x24]Putty KeyPad [VT100]Redirection After BIOS POST [Always Enable]

$ eeprom
keyboard-layout=Unknown
ata-dma-enabled=1
atapi-cd-dma-enabled=1
ttyd-rts-dtr-off=false
ttyd-ignore-cd=true
ttyc-rts-dtr-off=false
ttyc-ignore-cd=true
ttyb-rts-dtr-off=false
ttyb-ignore-cd=true
ttya-rts-dtr-off=false
ttya-ignore-cd=true
ttyd-mode=9600,8,n,1,-
ttyc-mode=9600,8,n,1,-
ttyb-mode=115200,8,n,1,-
ttya-mode=115200,8,n,1,-
lba-access-ok=1
console=ttyb

have no config in /boot/loader.d/
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Firefox 32bit future: Rustc

[Carsten Grzemba]

On 01/26/18 10:41 AM, Aurélien Larcher wrote:

On Fri, Jan 26, 2018 at 10:11 AM, Carsten Grzemba <grze...@contac-dt.de>
wrote:



On 25.01.18 19:58, Alan Coopersmith  <alan.coopersm...@oracle.com> wrote:

On 01/25/18 10:40 AM, russell wrote:

Is there any immediate danger of Mozilla retiring the 32bit version of

Firefox?

I believe the most immediate item of concern is that Firefox now uses

code

written in Rust, so you'll be limited to platforms that the Rust compiler
generates code for, and I don't know if anyone is bothering to do 32-bit

code

generation for Solaris/illumos in Rust.


I did some attempts to package rustc for OI, based on the kind of SmartOS,
but with no success for now:
https://github.com/cgrzemba/oi-userland/tree/rust/
components/developer/rust

For Rust community is Solaris a tier 3 platform which means no support.
But the recipe tries to download the rust-std library wich is not
available for Solaris.
I have no pkgsrc build system to see how it works for SmartOS.
I would be grateful if anyone can give some advice.


I created a component for Rust some time ago.
I'll try to push it later today as an example.
Not sure whether it will work with recent versions.


I updated my work on github but it throws still erros on build because 
it use cc instead of gcc for linking, although I set


--default-linker=gcc

and


RUSTFLAGS="-C linker=gcc"


The similar setup works with pkgsrc on smartos.


Perhaps someone has an idea?






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

Re: [OpenIndiana-discuss] Firefox 32bit future: Rustc

[Carsten Grzemba]

On 25.01.18 19:58, Alan Coopersmith   wrote: 
> 
> On 01/25/18 10:40 AM, russell wrote:
> > Is there any immediate danger of Mozilla retiring the 32bit version of 
> > Firefox?
> 
> I believe the most immediate item of concern is that Firefox now uses code
> written in Rust, so you'll be limited to platforms that the Rust compiler
> generates code for, and I don't know if anyone is bothering to do 32-bit code
> generation for Solaris/illumos in Rust.
> 
I did some attempts to package rustc for OI, based on the kind of SmartOS, but 
with no success for now:
https://github.com/cgrzemba/oi-userland/tree/rust/components/developer/rust

For Rust community is Solaris a tier 3 platform which means no support.
But the recipe tries to download the rust-std library wich is not available for 
Solaris.
I have no pkgsrc build system to see how it works for SmartOS.
I would be grateful if anyone can give some advice.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] [HEADS UP] Gnome 2 is dead

[Carsten Grzemba]

On 23.01.18 16:21, Alexander Pyhalov   wrote: 
> 
> The title says its all, but there are details.
> 
> Today libunique, gnome-power-manager and gdm were removed from oi-userland 
> (together with support for creating Gnome2 installation images). So if you 
> still use Gnome 2 due to some strange reason, don't be surprised when 
> essential applications (including GDM) disappear on system update,
> 
Is Openindiana then still useable on SunRay (without gdm)? 
 
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss