Bug 1435 - Gnome & DraftSight won't open, save or new file dialop -> crash.
Summary: Gnome & DraftSight won't open, save or new file dialop -> crash.
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: http://www.draftsight.com
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-26 18:32 CEST by Maurizio Dal Magro
Modified: 2011-10-11 12:51 CEST (History)
0 users

See Also:
Source RPM: None: Close-source from DraftSight
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Maurizio Dal Magro 2011-05-26 18:32:47 CEST 
Description of problem:
DraftSight 4 Linux within Gnome crash when open, save or new file dialog.
It won't crash if you run DraftSight within KDE.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Download DraftSight 4 Linux rpm from website and install
2. Run DraftSight
3. Click New-file or Open-file or Save-file -> crash

Terminal output:
maurizio@Mag_21:~$ /opt/dassault-systemes/draftsight/bin/DraftSight
QFSFileEngine::open: No file name specified
QFileInfo::absolutePath: Constructed with empty filename
QFileInfo::absolutePath: Constructed with empty filename
QFileInfo::absolutePath: Constructed with empty filename
QFileInfo::absolutePath: Constructed with empty filename
QFSFileEngine::open: No file name specified
I/O error : No such file or directory
/usr/share/mime/inode/directory.xml:1: parser error : Extra content at the end of the document

^
QMetaObject::connectSlotsByName: No matching signal for on_pbDetails_clicked()
maurizio@Mag_21:~$ 

Crash-report from DraftSight: http://users.telenet.be/x86_64/Zip/crash_report.zip

Maurizio
Manuel Hiebel 2011-07-10 15:38:17 CEST

Component: Installer => RPM Packages

Comment 1 Manuel Hiebel 2011-10-11 12:51:01 CEST 
draftsight is not in the reposity so closing as invalid

Status: NEW => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.