Thanks for the report. Are you able to try creating a new database on an MySQL  or PostgreSQL server please? This can help to narrow down the area.

Also does the opening an existing .kexi file work?

Another question, do you experience these crashes after system's update? KEXI was not updated since 3.2.0 is the most recent one, so we need to know if there's an issue with any package used by KEXI.

Created attachment 128939 [details]
signature.asc

Hi,

Opening an existing Kexi database:

kexi-3.2
gui updated 3 min. ago, next auto-update in 57 min.
selectedFile: "/home/antonio/Documentos/Bases de datos/Varias/Silbato
2000.kexi"
selectedFile after applyEnteredFileName():
"/home/antonio/Documentos/Bases de datos/Varias/Silbato 2000.kexi"
Project File:  "/home/antonio/Documentos/Bases de datos/Varias/Silbato
2000.kexi"
Violación de segmento (`core' generado)

El vie, 29-05-2020 a las 10:09 +0000, Jarosław Staniek escribió:
> https://bugs.kde.org/show_bug.cgi?id=422216
> 
> Jarosław Staniek <staniek@kde.org> changed:
> 
>            What    |Removed                     |Added
> -------------------------------------------------------------------
> ---------
>                  CC|                            |staniek@kde.org
> 
> --- Comment #1 from Jarosław Staniek <staniek@kde.org> ---
> Thanks for the report. Are you able to try creating a new database on
> an MySQL 
> or PostgreSQL server please? This can help to narrow down the area.
> 
> Also does the opening an existing .kexi file work?
>

Thanks. Backtrace (stack trace) would be needed for this crash. You may need to find out how to obtain it in Mageia.

Created attachment 128960 [details]
volcado

Hi,

I hope the attached file works.

Thanks,

I027614

 

El sáb, 30-05-2020 a las 23:28 +0000, Jarosław Staniek escribió:
> https://bugs.kde.org/show_bug.cgi?id=422216
> 
> --- Comment #4 from Jarosław Staniek <staniek@kde.org> ---
> Thanks. Backtrace (stack trace) would be needed for this crash. You
> may need to
> find out how to obtain it in Mageia.
>

Created attachment 128961 [details]
signature.asc

Thanks. The file only shows what are the files accessed. E.g. /home/antonio/Documentos/Silbato.kexi was not found. Not sure it should already exist before the crash though. 

If even opening any .kexi file crashes for you we shall focus on that activity one and not on importing mdb files.

Created attachment 128962 [details]
volcado2

Hi,

I don't think it should exist previously, since it is the result of
importing the .mdb file.

For opening .kexi files, the attached file.

Thanks,

I027614

El dom, 31-05-2020 a las 21:35 +0000, Jarosław Staniek escribió:
> https://bugs.kde.org/show_bug.cgi?id=422216
> 
> --- Comment #7 from Jarosław Staniek <staniek@kde.org> ---
> Thanks. The file only shows what are the files accessed. E.g.
> /home/antonio/Documentos/Silbato.kexi was not found. Not sure it
> should already
> exist before the crash though. 
> 
> If even opening any .kexi file crashes for you we shall focus on that
> activity
> one and not on importing mdb files.
>

Created attachment 128963 [details]
signature.asc

Thanks. I've not concluded anything special from the strace log.
Debug packages for KEXI / KDb would be needed. I am unsure how and if this is available for the distribution. 

It seems there is a way for Megeia, please follow the loing in this section: https://community.kde.org/Kexi/File_a_bug_or_wish#In_case_of_crashes

So it's best if the crash dialog appears with the stack trace (in a Developer tab like this https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Crash.21 ).

Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!

Still the same problem, sorry

I027614

@Justin 
I wanted to say the 3.2.0 is still the newest so such questions do not move us forward.