Bug 95837 - Quanta crashes when defining a new project -and- there is no project opened already.
Summary: Quanta crashes when defining a new project -and- there is no project opened a...
Status: RESOLVED WORKSFORME
Alias: None
Product: quanta
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: András Manţia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-26 14:22 UTC by J Reitsma
Modified: 2005-06-21 15:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description J Reitsma 2004-12-26 14:22:39 UTC 
Version:            (using KDE KDE 3.3.0)
Installed from:    SuSE RPMs
Compiler:          gcc version 3.3.4 (pre 3.3.5 20040809) 
OS:                Linux

Quanta crashes when creating a new project, and no project has been opened yeat. The crash appears on the moment when all necessary fiels are filled, and I press the 'Finish' button. After the crash, the project directories and the .webprj-file appear to have been created though, and when restarting Quanta I can open the project without crash.
Comment 1 Pawel Orzechowski 2005-01-03 13:00:11 UTC 
Quanta crashes when creating new project with project files pointing to an empty directory. This happens in kde 3.3.2 from RedHat packages on Fedora Core 3. It could be the same bug as 88763.
Comment 2 András Manţia 2005-02-18 17:22:21 UTC 
Do any of you have a usable backtrace?
Comment 3 Pawel Orzechowski 2005-02-20 23:04:37 UTC 
Well, I don't have. I have installed kdewebdev packages from kde-redhat.sf.net and now it works correctly.
Comment 4 András Manţia 2005-02-22 17:40:45 UTC 
As I cannot reproduce either, I close the bug. Please reopen if you 
still see in 3.4.

Andras
Comment 5 Sigbjørn Lund Olsen 2005-06-21 15:14:44 UTC 
I have encountered this bug in Quanta/KDE 3.4.1. I've provided information/backtrace etc at https://bugs.kde.org/show_bug.cgi?id=88763 as this bug seems to be a duplicate of 88763.