This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
See attachment.
Created attachment 97556 [details] *
You need to provide some more details. Can you reproduce it? How? You need to either select a project in the project view or have one of you projects set as the main project.
1. Create a new project "C++ Application" - see 1.png 2. Build Main Project 3. To restart NetBeans - see 2.png (buttons "Build Main Project", - disabled) 4. Open main.cpp 5. To restart NetBeans - see 3.png ("Set Project Configuration" - disabled)
Created attachment 97757 [details] 1.png
Created attachment 97758 [details] 2.png
Created attachment 97759 [details] 3.png
If you set one of your projects as the Main project or if you select the project after the IDE starts, the actions will be enabled. I think this is correct behavior. Reassigning to projects component for further evaluation.
(In reply to comment #7) > If you set one of your projects as the Main project or if you select the > project after the IDE starts, the actions will be enabled. I think this is > correct behavior. It is.
As there can be an active mainproject for which there is no configuration. See Final.png
Created attachment 97883 [details] final.png
I'm afraid I can't reproduce anything you claim. The only clear instructions are from comment #3, so: I build cnd.kit, run the IDE, create a C++ App (set as main by default); the combo shows Debug and Release, and Build Main Project is enabled. The same is true after any number of restarts, regardless of selection. (In reply to comment #9) > there can be an active mainproject for which there is no configuration I'm not sure what this means or if you are implying some other steps to reproduce than previously given, but for what it's worth I also tried to customize the C++ app project and remove all its configurations. I could not - the GUI does not offer the opportunity to remove the last remaining configuration. And that last configuration continues to be shown in the pulldown as expected. Before reopening, please take care to provide precise steps to reproduce your problem from scratch, and also confirm that they can be reproduced on a colleague's computer using a current NB 6.9 dev build.
Product Version: NetBeans IDE Dev (Build 201004250200) 1. Create a new project "C++ Application" (We accept all by default) 2. To open main.cpp in NetBeans 3. To restart NetBeans See final1.png 1. Create a new project "C++ Application" with "Samples C/C++" (Arguments) 2. To open args.c in NetBeans 3. To restart NetBeans 4. To change configurations on Releace 5. To restart NetBeans
Created attachment 97984 [details] final1.png
(In reply to comment #12) > 1. Create a new project "C++ Application" (We accept all by default) > 2. To open main.cpp in NetBeans > 3. To restart NetBeans Saw a blank config combo once, but was not able to reproduce this after repeated subsequent attempts, incl. with a fresh userdir and with new or the same project, with nodes selected in Projects or not. My best guess is that MakeProjectConfigurationProvider is sometimes not working, especially since I have never heard of such a problem when using j2seproject's. If you can consistently reproduce this, then you will need to debug what is happening. > 1. Create a new project "C++ Application" with "Samples C/C++" (Arguments) > 2. To open args.c in NetBeans > 3. To restart NetBeans > 4. To change configurations on Releace > 5. To restart NetBeans Not clear how this related to the previous steps. A different way to reproduce the same outcome? A different outcome? All I can reproduce in this scenario is that the active config remains "Debug" after a restart, because no change is made to configurations.xml after changing the combo to "Release" - certainly a bug in CND.
OK, will take a closer look at MakeProjectConfigurationProvider as per Jesse's recommendation.
Possible dupe of bug #185476, though without a reproducible test case I cannot say for sure.
The question is closed. The conflict between configuration files kde4-gtk-qt-engine (GTK-Style Engine for Use with Qt Plug-Ins and Settings) and kcm_gtk (KDE control module for switching GTK+ style). In system one switch of GTK-style for KDE4 is used only. After their replacement there is such error. After removal of a configuration file (~HOME/.config) and customisation of style from the beginning - all works correctly.