After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 639093 - I can't start a new project properly
I can't start a new project properly
Status: RESOLVED FIXED
Product: anjuta
Classification: Applications
Component: plugins: project-wizard
2.32.x
Other Linux
: Normal blocker
: ---
Assigned To: Sébastien Granjoux
Anjuta maintainers
: 630327 649836 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-01-09 19:11 UTC by kfirufk
Modified: 2011-07-02 20:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description kfirufk 2011-01-09 19:11:49 UTC
Hello.
The problem started happening since anjuta-2.32.1.0. previous versions does not have this problem.

I use gentoo linux. i tried both to emerge anjuta or to install it myself and the same problem occurred. currently i'm experiencing problems with anjuta-2.32.1.1.

These are the steps that i'm taking to create a new project:

FIle -> New -> Project ->  C Tab -> Gtk+-2.0 -> Forward ->

Confirm the following inforamtion:

Project Type: GTK+

Clicked Apply -> new project popup closes and in the "new project assistant" i see "new project has been created successfully." it did not allow me to choose the location of the project, it's name, it's dependencies nor the gtk+ version that i want the application to be build against.

i do not have a new project in the projects tab.

I'm willing to test and do whatever you want to resolve the issue!

system information:
Linux tux-music 2.6.37-gentoo #2 SMP PREEMPT Sat Jan 8 13:25:17 IST 2011 x86_64 Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz GenuineIntel GNU/Linux

glib: 2.26.1
gtk: 2.22.1
anjuta: 2.32.1.1


thanks!
Comment 1 Johannes Schmid 2011-01-09 20:46:10 UTC
Is there any output on the command-line when you run anjuta in a terminal? Sounds pretty much like it cannot read the xml file which can have multiple reasons.

On other idea would be to use anjuta in C locale in case a translation is broken.

Thanks!
Comment 2 kfirufk 2011-01-09 21:53:12 UTC
hello. thanks for the quick response.
when i ran anjuta from command line i did not receive any output.
when i checked the locale settings I noticed that my default locale is "C", when i changed it "en_us.UTF-8" the project creation worked.

that resolve my problem.

let me know if I need to do any more testing to why it does not work in "C" locale.
Comment 3 Sébastien Granjoux 2011-01-10 21:25:00 UTC
I get a problem (with the latest development version of Anjuta) if I run the project wizard with the local set to "C". If I select the Gtk project, the wizard asks me only the project name.

I will check what's happen it shouldn't be too difficult to fix it.
Comment 4 Sébastien Granjoux 2011-01-11 22:04:08 UTC
Thanks for reporting this bug.

It was more difficult to find than expected because it's not linked to my latest changes in the project wizard (include translation in .wiz file) as I have thought at the beginning. It's an old bug due to the encoding. Here it was failing due to the author name value. I was using the default encoding while the project wizard file are always in UTF-8.

It's fix in this commit:
http://git.gnome.org/browse/anjuta/commit/?id=76a87162de7fae40546ea3e4a756cca25988bc4e

The fix will be available in the next release 2.91.6 

If you can compile anjuta 2.32.1 from source, you can apply the fix and check. I will be interested to know if it really fix the issue on your system just to be sure.
Comment 5 kfirufk 2011-01-12 21:41:37 UTC
this patch resolved the problem.
Comment 6 Sébastien Granjoux 2011-01-12 21:47:48 UTC
Thanks for checking it. It was probably hidden in previous version because the .wiz file was containing far less UTF-8 characters, the translation was outside.
Comment 7 Sébastien Granjoux 2011-05-10 17:45:05 UTC
*** Bug 649836 has been marked as a duplicate of this bug. ***
Comment 8 Sébastien Granjoux 2011-07-02 20:48:26 UTC
*** Bug 630327 has been marked as a duplicate of this bug. ***