Bug 26698 - Either creating a new database or importing an MS Access database Kexi crashes
Summary: Either creating a new database or importing an MS Access database Kexi crashes
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO, UPSTREAM
Depends on:
Blocks:
 
Reported: 2020-05-28 23:40 CEST by I027614 I027614
Modified: 2021-01-08 12:37 CET (History)
4 users (show)

See Also:
Source RPM: kexi-3.2.0-1.mga7.src.rpm
CVE:
Status comment:


Attachments

Description I027614 I027614 2020-05-28 23:40:48 CEST
Description of problem:
Kexi crashes when creating a new database or importing an MS Access database

Version-Release number of selected component (if applicable):
 kexi-3.2.0-1.mga7.src.rpm

How reproducible:
Either importing an MS Access database or creating a new one.

Steps to Reproduce:
1. Open Kexi
2. Create a new database or import an MS Access database
3. Select "database stored in file" and complete options.

When importing an MS Access database: 

kexi-3.2
gui updated 4 min. ago, next auto-update in 56 min.
selectedFile: "/home/antonio/Documentos/Bases de datos/Exporta-Kexi/Silbato 2004.mdb"
selectedFile after applyEnteredFileName(): "/home/antonio/Documentos/Bases de datos/Exporta-Kexi/Silbato 2004.mdb"
Project File: "/home/antonio/Documentos/Bases de datos/Exporta-Kexi/Silbato 2004.mdb"
"Tag 'html' is not defined in message {<__kuit_internal_top__>El asistente de importación de bases de datos va a ...}."
File Destination...
Current file name: "/home/antonio/Documentos/Silbato 2004.kexi"
Structure and data selected
File Destination...
Current file name: "/home/antonio/Documentos/Silbato 2004.kexi"
Structure and data selected
File Destination...
Current file name: "/home/antonio/Documentos/Silbato 2004.kexi"
Structure and data selected
"/home/antonio/Documentos/Silbato 2004.kexi"
Performing import...
CONNECTING...
GETTING TABLENAMES...
Reading list of tables...
num_keys 1
key 1 col 1 "Numero_del_campo"
num_keys 1
key 1 col 1 "Localidad"
num_keys 1
key 1 col 1 "ID"
num_keys 1
key 1 col 1 "Numero"
num_keys 1
key 1 col 1 "Numero"
num_keys 1
key 1 col 1 "Numero"
num_keys 1
key 1 col 1 "Numero"
num_keys 1
key 1 col 1 "Numero"
num_keys 1
key 1 col 1 "Numero"
num_keys 1
key 1 col 1 "Numero"
num_keys 1
key 1 col 1 "Numero"
num_keys 1
key 1 col 1 "Numero"
num_keys 1
key 1 col 1 "Numero"
num_keys 1
key 1 col 1 "Numero"
num_keys 1
key 1 col 1 "Numero"
num_keys 1
key 1 col 1 "ID"
num_keys 1
key 1 col 1 "Categoria"
Violación de segmento (`core' generado)

When creating a new database:

kexi-3.2
gui updated 26 min. ago, next auto-update in 34 min.
QUrl("file:///home/antonio/Documentos/Base de datos nueva.kexi")
filters: ("*.kexi|Proyecto basado en archivos de base de datos Kexi (*.kexi)") path: "/home/antonio/Documentos/Base de datos nueva.kexi"
Missing recent focus widget for KexiProjectCreationPage(0x7f78a4009d30) -- this cat lead to usability isses; please call KexiAssistantPage::setRecentFocusWidget() for that page.
Violación de segmento (`core' generado)
Comment 1 David GEIGER 2020-05-29 09:07:24 CEST
Can you report this bug upstream at https://bugs.kde.org/enter_bug.cgi?product=KEXI , please?

CC: (none) => geiger.david68210

Comment 2 Lewis Smith 2020-06-01 20:59:56 CEST
And when you have, please put that bug's URL in the field of the same name in this bug header.

Keywords: (none) => UPSTREAM
CC: (none) => lewyssmith

Comment 3 Aurelien Oudelet 2020-08-27 11:38:21 CEST
Hi, sorry leaving this too long.

Does this have been reported upstream?
Or, better, does it still occur?

Keywords: (none) => NEEDINFO

Aurelien Oudelet 2020-08-27 11:39:02 CEST

Severity: critical => major

Comment 4 Aurelien Oudelet 2020-09-01 22:34:02 CEST
Reporter, could you please reply to the previous question? If you don't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
Aurelien Oudelet 2020-09-02 17:48:49 CEST

CC: (none) => ouaurelien

Comment 5 I027614 I027614 2020-09-03 17:45:07 CEST
Sorry for the delay in anwering.

I have reported the bug to KDE.

It still happens.

Thanks,

I027614
Comment 6 Aurelien Oudelet 2020-09-09 12:49:33 CEST
Could you provide link to upstream bugs report?
Comment 7 Aurelien Oudelet 2020-12-21 16:58:44 CET
Reporter, could you please reply to the previous question? If you don't reply within two weeks from now, I will have to close this bug as INVALID. Thank you.
Comment 8 Marja Van Waes 2021-01-08 12:37:00 CET
(In reply to Aurelien Oudelet from comment #7)
> Reporter, could you please reply to the previous question? If you don't
> reply within two weeks from now, I will have to close this bug as INVALID.
> Thank you.

@ I027614

No reply, so closing.

Feel free to reopen this report while providing the requested link to the upstream bug report.

Status: NEW => RESOLVED
Resolution: (none) => OLD
CC: (none) => marja11


Note You need to log in before you can comment on or make changes to this bug.