Hi to all,

When i start ./mystic -cfg and then i go to "Network" and select "Edit
Areafix Help", "Edit Filefix Help" or "Edit File Request" i got imidiatly a Segfault and the mystic -cfg is closed.

An unhandled exception occurred at $0000000000412130: EAccessViolation: $0000000000412130 Segmentation fault (core dumped).

I run Ubuntu 20.04.02 LTS 64 Bit, and i install the latest Mystic V1.12 A47
64 Bit PreAlpha Version.

Installed as root at /mystic with chown -R mystic:mystic /mystic changed to mystic user and started as user mystic

Hope this help to fix the problem

Best regards
Alisha
--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: swissIRC BBS (2:301/113)

When i start ./mystic -cfg and then i go to "Network" and select BW> AS> BW> AS> BW> AS> "Edi
Areafix Help", "Edit Filefix Help" or "Edit File Request" i got imidiatly a Segfault and the mystic -cfg is closed.

An unhandled exception occurred at $0000000000412130: BW> AS> BW> BW> AS> AS> EAccessViolatio
$0000000000412130 Segmentation fault (core dumped).

I don't seem to be able to reproduce this here on Ubuntu 20 64-bit with the latest A47. I wonder what could be different? I'll make a new build since I
have that filename change for the View anyway for you to test... Let me know if it still happens in the latest build.

... Hard work never killed anyone but why take a risk?

--- Mystic BBS v1.12 A47 2021/08/10 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

When i start ./mystic -cfg and then i go to "Network" and select "Edit Areafix Help", "Edit Filefix Help" or "Edit File Request" i got
imidiatly a Segfault and the mystic -cfg is closed.

Thanks I will see if I can reproduce this and get it fixed up if so.

... The seminar on time travel will be held two weeks ago

--- Mystic BBS v1.12 A47 2021/08/10 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hi g00r00,

Is there any Mailinglist or Echomail witch you announce when a new prealpha Release is released to know when i shut download a new binary? What i see is that the Name of the prealpha has always the same name, there is no indicator when a new version is uploaded. Is there any plan for the future to extend
the filename by a date and houre prefix to know when a new version is
released.

Best regards
Alisha
--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: swissIRC BBS (2:301/113)

For me as a Sysop Point of view to test a prealpha and give you feedback would be nice to see very fast, without to download and install if there is a new version online or not. The easy way to do this is to extend the existing prealpha download file name by mys112a47_202108142110_l64.rar means this release ist build on the 14th of August 2021 at 21:10 or 09:10pm at utc timezone.

The date is already set on the timestamp of the file within the listing, so you can already use that to accomplish what you're hoping for in a very simple way:

For example you can do:
"wget -N http://mysticbbs.com/downloads/prealpha/mys112a47_l64.rar"

And that will look at the file date and download the file if its been updated since the last time you've downloaded it. If the filename contained the date stamp within the filename then this would not work.

... How is it possible to have a civil war?
--- Mystic BBS v1.12 A47 2021/08/08 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

On 14 Aug 2021, g00r00 said the following...

The date is already set on the timestamp of the file within the listing, so you can already use that to accomplish what you're hoping for in a
very simple way:

For example you can do:
"wget -N http://mysticbbs.com/downloads/prealpha/mys112a47_l64.rar"

I have a small shell script setup to check whenever I think about it:

### begin myschk.sh ###
#!/bin/bash
cd /home/pi/mystic
echo "Current version:"
/home/pi/mystic/mystic -ver
cd /tmp
[ -f "/tmp/mys112a47_p32.zip" ] && rm -f /tmp/mys112a47_p32.zip
wget -q http://mysticbbs.com/downloads/prealpha/mys112a47_p32.zip
echo #
unzip -l ./mys112a47_p32.zip
echo #
read -p "Delete zip? " -n 1 -r
echo #
if [[ $REPLY =~ ^[Yy]$ ]]
then
rm -f /tmp/mys112a47_p32.zip
fi
echo #
### end myschk.sh ###


$ ./myschk.sh
Current version:
Mystic BBS v1.12 A47 Raspberry Pi/32 Compiled 2021/08/14 09:02:05

Archive: ./mys112a47_p32.zip
Length Date Time Name
--------- ---------- ----- ----
1278 2021-08-14 12:02 file_id.ans
905 2021-08-14 12:02 file_id.diz
113416 2021-08-14 12:02 install
5866272 2021-08-14 12:02 install_data.mys
14653 2021-08-14 12:02 unix.install.txt
136624 2021-08-14 12:02 upgrade
31059 2021-08-14 12:02 upgrade.txt
223925 2021-08-14 12:02 whatsnew.txt
--------- -------
6388132 8 files

Delete zip? y


Jay

... Finagle's first Law: If an experiment works, something has gone wrong.

--- Mystic BBS v1.12 A47 2021/08/14 (Raspberry Pi/32)
* Origin: Northern Realms (1:229/664)

I have a small shell script setup to check whenever I think about it:

I made one real quick that will check for a new version and download it if there is a newer version.

You could easily modify this to send an e-mail or to even unrar it and do a "./install replace /mystic" to automatically install it. You'd still need to keep an eye on the upgrade/whatsnew text though in case there are additional steps needed.

NEW_VERSION=$(wget -N http://mysticbbs.com/downloads/prealpha/mys112a47_l64.rar 2>&1 >/dev/null | grep -c "Saving to:*")

if [ "$NEW_VERSION" -eq 1 ] ; then
echo "A new version of Mystic BBS is available"

# Do whatever you want here
else
echo "No new version found"
fi

... A social life? Where can I download that!?

--- Mystic BBS v1.12 A47 2021/08/08 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello g00r00!

On 14 Aug 2021, g00r00 said the following...

I don't seem to be able to reproduce this here on Ubuntu 20 64-bit with the latest A47. I wonder what could be different? I'll make a new
build since I have that filename change for the View anyway for you to test... Let me know if
it still happens in the latest build.

Unfortunately, yes -- same error message...

Tried some gdb but doesn't have any symbols, so no good references to
anything there, I think?

bbs@glimmer:~/mystic$ gdb -ex=r --args /home/bbs/mystic/mystic -cfg

(pressing N and then R)

Thread 1 "mystic" received signal SIGSEGV, Segmentation fault.
0x0000000000460f5d in ?? ()
(gdb) bt full
#0 0x0000000000460f5d in ?? ()
No symbol table info available.
#1 0x00007fffffff3850 in ?? ()
No symbol table info available.
#2 0x000000000063aba0 in ?? ()
No symbol table info available.
#3 0x0000000000000000 in ?? ()
No symbol table info available.
(gdb) quit
A debugging session is active.

Inferior 1 [process 7929] will be killed.

Quit anyway? (y or n) y

Not sure how to proceed in the best way...

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/14 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Hi Bjoern,

I was make some other Test as well "./mystic -text blah.txt" and it crash, so it looks that the fault is general in the text editor module of mystic and
not related to the ./mystic -cfg module when i select any files to edit with the editor.

Best regards
Alisha
--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: swissIRC BBS (2:301/113)

Unfortunately, yes -- same error message...

Its not reproducable on any of my machines here, so there has to be something else. What is your window/terminal size when you start it?

... A Scarf is just an unfinished Afghan

--- Mystic BBS v1.12 A47 2021/08/08 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello Alisha!

Thank you for your reply!

On 15 Aug 2021, Alisha Stutz said the following...

I was make some other Test as well "./mystic -text blah.txt" and it
crash, so it looks that the fault is general in the text editor module
of mystic and not related to the ./mystic -cfg module when i select any files to edit with the editor.

Ah, thanks, good to know!

Let's hope g00r00 can find something (or perhaps point us in some direction on how to assist him in locating the cause of this).

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/14 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Hello g00r00!

On 15 Aug 2021, g00r00 said the following...

Its not reproducable on any of my machines here, so there has to be something else. What is your window/terminal size when you start it?

I noticed now that it only happens if/when I fullsize my PuTTY Windows (SSHing from my Windows machine to the Debian box).

On my machine, this is:

bbs@glimmer:~$ tput cols
237
bbs@glimmer:~$ tput lines
63

bbs@glimmer:~$ set | grep TERM
TERM=xterm

...whereas 80x24 (in a standard-sized PuTTY Windows) works fine.

So it appears to have something to do with the screen size (lines/columns).

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/14 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

i use Putty under Windows 10 Pro to access my Ubuntu Linux 20.04.02 LTS, but i have it as well on macOS Catalina 10.15.7 with the build in
Terminal when i access the Ubuntu Linux 20.04.02 LTS.

Thank you! I believe I have fixed this now in the latest build! :)

... Message encrypted: Press ALT-F4 to read encoded message

--- Mystic BBS v1.12 A47 2021/08/08 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Its not reproducable on any of my machines here, so there has to be something else. What is your window/terminal size when you start it?

I noticed now that it only happens if/when I fullsize my PuTTY Windows (SSHing from my Windows machine to the Debian box).

I thought it might be something like that.

Based on the feedback from both of you I think I found and fixed the issue today in the latest build.

Thanks again to both of you for the report let me know if you still have any issues.

... What does it mean to pre-board? Do you get on before you get on?

--- Mystic BBS v1.12 A47 2021/08/08 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello g00r00!

Thank you for your reply!

On 15 Aug 2021, g00r00 said the following...

Based on the feedback from both of you I think I found and fixed the
issue today in the latest build.

That's great!

Yep, it seems to be working fine now!

Thanks again to both of you for the report let me know if you still have any issues.

You're very welcome! Thanks for fixing this so fast!

Best regards
Bj”rn
--- Mystic BBS v1.12 A47 2021/08/15 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Hi g00r00,

Yes i can confirm fault is fixed. Thanks for your fast support to fix this issus.

Best regards
Alisha
--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: swissIRC BBS (2:301/113)