Bug 149928

What's the processor of the machine, ARM or Intel?
What's the macos version?
Which LO version did you use? (there's Intel or Apple Silicon version).
Could you give a try at 7.3.4 (the last LO version) ?

What precise Java version do you have? 32 bits or 64 bits?
What type of database do you use?
At which moment does it crash?

(In reply to Julien Nabet from comment #1)
> What's the processor of the machine, ARM or Intel?
> What's the macos version?
> Which LO version did you use? (there's Intel or Apple Silicon version).
> Could you give a try at 7.3.4 (the last LO version) ?
> 
> What precise Java version do you have? 32 bits or 64 bits?
> What type of database do you use?
> At which moment does it crash?

Identifier:            org.libreoffice.script
Version:               7.3.2.2 (7.3.2.2) Intel ver.
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2022-07-08 07:53:44.3586 -0400
OS Version:            macOS 12.4 (21F79)

java 13.0.2 2020-01-14
Java(TM) SE Runtime Environment (build 13.0.2+8)
Java HotSpot(TM) 64-Bit Server VM (build 13.0.2+8, mixed mode, sharing)

I just downloaded and installed LO 7.3.4 and the database crashed when I was asked whether LO should create a primary key for me. These were precisely the conditions for the crash the last time.

Ok what type of database do you use?
embedded HSQLdb, Mysql, MariaDb, Postgresql?

Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile ? (I don't think it's related but just to be sure)

(In reply to Julien Nabet from comment #3)
> Ok what type of database do you use?
> embedded HSQLdb, Mysql, MariaDb, Postgresql?
> 
> Could you give a try at
> https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile ?
> (I don't think it's related but just to be sure)

Postgresql

On pc Debian testing x86-64 with master sources updated today + Postgresql 12.4, I don't reproduce this.

Here are the steps I did:
- launched Base
- clicked "connect to an existing database"
- chose "PostgreSQL"
- for DBMS, I put:
host=127.0.0.1 dbname=test_db
- filled "User name"
- etc.
=> file created
- clicked on "Tables"
- clicked on "Create Table in Design View..."
- Field Name => id / Field Type => Integer [int4]
- clicked "Save" icon
=> dialog appeared asking schema + Table Name
- chose schema "public" and "test" for table name
=> dialog appeared asking "Should a primary key  be created now?"
- clicked "Yes"
=> No crash

Did you do something different from my step by step process?
Do you use direct connection to Postgresql or JDBC?
What's the version of Postgresql you use?

(In reply to Julien Nabet from comment #5)
> On pc Debian testing x86-64 with master sources updated today + Postgresql
> 12.4, I don't reproduce this.
> 
> Here are the steps I did:
> - launched Base
> - clicked "connect to an existing database"
> - chose "PostgreSQL"
> - for DBMS, I put:
> host=127.0.0.1 dbname=test_db
> - filled "User name"
> - etc.
> => file created
> - clicked on "Tables"
> - clicked on "Create Table in Design View..."
> - Field Name => id / Field Type => Integer [int4]
> - clicked "Save" icon
> => dialog appeared asking schema + Table Name
> - chose schema "public" and "test" for table name
> => dialog appeared asking "Should a primary key  be created now?"
> - clicked "Yes"
> => No crash
> 
> Did you do something different from my step by step process?
> Do you use direct connection to Postgresql or JDBC?
> What's the version of Postgresql you use?

Yes, that works perfectly.

(In reply to DJLConsulting from comment #6)
> ...
> Yes, that works perfectly.

So everything is ok for you and we can close this tracker?
If it's not the case, would it be possible you describe precisely how to reproduce the crash?

Let's put this one to WFM.
Don't hesitate to reopen this tracker if you still reproduce this.
In this case, please describe precisely how to reproduce the crash.