GNOME Bugzilla – Bug 597318
Anjuta terminal crashes X
Last modified: 2009-11-21 07:43:01 UTC
Hello, I'm using anjuta 2.28 for the first time. I've created a generic project then compiled it. After that I run it and a terminal opened. This is the aspect of the terminal: - black - white cursor on (0,0) position, nothing written It should have written Hello world instead. After a couple of retries the computer blocked. I restart the computer, reopen the project, then re-execute and the terminal opened, but still nothing. After I restarted the execution again a couple of times, this time X freezed and then restarted with gdm. I'm using debian sid, libvte 0.22.2, 2.18.1, amd64 single core. I can't provide any traceback or such as it freezes.
I haven't seen the problem here but I have an older version of libvte. It is possible that it comes from libvte. Could you try with an older version ? I have 0.20.1. Or is there someone else who has the same problem ?
First, please require vte 0.18 in configure.in instead of 0.13. Running anjuta with 0.16 claims undefined symbols in the library. Then I've installed vte 0.20 but the problem still applies. I do Run->Execute,, it asks me to restart execution of the program (I started it before from the toolbar button) then X restarted.
(In reply to comment #2) > First, please require vte 0.18 in configure.in instead of 0.13. Running anjuta > with 0.16 claims undefined symbols in the library. Thanks for the information. This hasn't been update from quite time and I haven't checked it. > Then I've installed vte 0.20 but the problem still applies. I do Run->Execute,, > it asks me to restart execution of the program (I started it before from the > toolbar button) then X restarted. Can you use valgrind on anjuta to see if you get error reports ? Then, if you remove the terminal plugin (rename or remove the file named $(prefix)/lib/anjuta/anjuta-terminal.plugin where prefix is /usr/lib or /usr/local/lib depending on your installation), Anjuta should create a terminal, so not using vte. Could you try this and check if it's working ? I think you can still get a traceback doing the following: - Start anjuta in your X session - Switch to a console (Ctrl+Alt+F1 by example) - Get the pid of anjuta process - Start gdb with the option "--pid _pid_of_anjuta_process_" - gdb should connect to Anjuta and you should be able to get a trace.
I haven't tried the other solutions because I think there's another problem. I've tried renaming the plugin and a shell is opened and this is what I get when running my simple project: There was an error creating the child process for this terminal This happens when clicking on the toolbar button for executing the project, also from Run -> Execute. Instead with Debug -> Run program asks for a warning, say Yes, show the above error message and freezes. The program is built under the Debug directory. In Program Parameters the path of the executable is right and it works from the command line out of anjuta.
I have tried exactly, the same things than you: get anjuta 2.28 create a new C Generic project and run it, I have seen any problem. I have tried with valgrind but it looks fine. My system is 32 bits, so perhaps there is a problem only on 64 bits system. Is someone having the same problem on a 64 bits system ? Can you try with on a 32 bits system ? I will try to install a 64 bits system to check but it will take me some time.
I've delete cache, config and gconf. I've created a new project and I've noticed toolbar button for building whole project was disabled, then I've run Build->Compile... is that how it's expected to work? Anyway nothing to do. I'll try on a 32-bit machine with less things messed up.
Yes, more or less. The compile button is always on because you can compile a C source file even without a makefile due to default make rules. The other build button are disabled if you haven't run configure before. So if you have select compile without configuring your project, it can still work for very simple program.
Another thing. The shell is being opened in the terminal. The problem only occurs when launching the program. I can even run anjuta-launcher Debug/src/foobar_sample from that shell. I'm in the tty group and /dev/pts permissions look ok.
I've set /apps/anjuta/preferences/anjuta.command.terminal=xterm now the terminal starts but still the program is not run. I only get into the shell in the dir of the project.
I have been able to reproduce this bug here. I have installed a new 64 bits system on one partition of my hard disk but it's not a 64 bits problem. This bug should be ranked quite high in the list of the most stupid bugs. I think it's due to the change of the name of anjuta-launcher program. It's a small program used to launch programs in anjuta in order to get a terminal. Previously it was named anjuta_launcher, but the new name has not been updated in all files. If the program is missing, you get a quite hard crash exactly as you described. The code checks if the program exists before, but the name has been updated in the check ! I haven't seen it, because the old program has not been uninstalled and I have both anjuta_launcher and anjuta-launcher. It's a bit late today, so I will fix it tomorrow in both 2.28 and 2.29 branch. In the meantime, you can copy anjuta-launcher to anjuta_launcher and everything should work fine. Thanks for reporting this bug and replying to all my questions.
It's fixed in git master and in 2.28 branch. The fix will be available in the next release. Thanks again for your bug report. If something is still not working reopen the bug.
*** Bug 602507 has been marked as a duplicate of this bug. ***