Bug 307257 - Import not working at all (crash due to uninitialized components)
Summary: Import not working at all (crash due to uninitialized components)
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Import-MainView (show other bugs)
Version: 3.0.0
Platform: unspecified Linux
: NOR critical
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-23 08:59 UTC by Andi Clemens
Modified: 2012-09-23 11:43 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 3.0.0

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Andi Clemens 2012-09-23 08:59:59 UTC 
Import is not working at all, if you select a folder for example and press CTRL+I, it crashes after the folder selection.

This is because the freeSpaceWidget, for example, is not initialized.
If I change the order in the ImportUi constructor, other components crash due to nullpointer exceptions.

I would suggest that the issue should be solved by Islam Wazery, who seems to have modified a lot on 2012-08-15, according to "git blame"...

Andi

Reproducible: Always

Steps to Reproduce:
1. Select folder
2. Press CTRL+I
3. Import a folder
Actual Results:  
crashes due to nullpointer issues

Expected Results:  
should not crash
Comment 1 Islam Wazery 2012-09-23 09:55:28 UTC 
I think this happens because of my last commit to git/master, I will investigate more about that and fix the problem.
Comment 2 Islam Wazery 2012-09-23 10:34:39 UTC 
Git commit 16a17f5a1724d9ae92ce8e21b1b75cc4dbf0a6d7 by Islam Wazery.
Committed on 23/09/2012 at 12:28.
Pushed by wazery into branch 'master'.

Fixed import tool crash
Andi, can you please test it and let me know if the bug still exist?

M  +19   -18   utilities/importui/main/importui.cpp
M  +2    -0    utilities/importui/main/importui_p.h

http://commits.kde.org/digikam/16a17f5a1724d9ae92ce8e21b1b75cc4dbf0a6d7
Comment 3 Andi Clemens 2012-09-23 10:54:59 UTC 
yes, it seems to be fixed now...