Re: [ubuntu-uk] have to start gnome-panel manualy after upgrade to jaunty
2009/6/15 thirstyh2o thirsty...@gmail.com: On Sun, 14 Jun 2009 21:00:42 +0100, Neil Greenwood wrote: You could try creating a new user on the machine and see if that works. If so, try deleting/renaming the .gnome2 and .gnome2_private hidden directories in your home directory, then logging back in. This will lose any customisations you've made to Gnome, but should also get rid of the bad setting that is preventing the panel from running. Well, I did not try creating a new user but I did tried deleting the folders you suggest, and some others too. E.g. I tried deleting .conf and .gconf too. I did not helped. So, for now, as I already mentioned, the problem is fixed by explicitly entering gnome-panel in the list of Startup Applications applet. This way I am happy Jaunty user (though I'm not really much excited by it). The only thing that bothers me is a question:Why? What's the heck is wrong?. The gnome-panel has been starting in Hardy, it started just fine after intermediate upgrade to Intrepid and then all at a sudden it stopped starting after, without this rather smooth, upgrade to Jaunty. I would definitely try creating another user. There might well be another configuration directory that is causing the problem. Cofion, Neil. -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] have to start gnome-panel manualy after upgrade to jaunty
On Sun, 14 Jun 2009 21:00:42 +0100, Neil Greenwood wrote: Tried to run [gnome-panel ] but it still dies when I close the terminal. Sorry, my bad. The above is definitely less then clear. Here is what I meant to say. I wanted to run the gnome-terminal process at the background, then close all programs and restart the session. Before doing this, I selected Automatically remember running application when logging out in Startup Application applet. The idea was to fix the problem by forcing the system remembering its state. Well, all it remembered was the terminal being run, but not its child process certainly. So, this did not work. And BTW, ask me why I mentioned this at all? I do not know. :-) Now, I see that it just obscures the matter. Sorry, again. You could try creating a new user on the machine and see if that works. If so, try deleting/renaming the .gnome2 and .gnome2_private hidden directories in your home directory, then logging back in. This will lose any customisations you've made to Gnome, but should also get rid of the bad setting that is preventing the panel from running. Well, I did not try creating a new user but I did tried deleting the folders you suggest, and some others too. E.g. I tried deleting .conf and .gconf too. I did not helped. So, for now, as I already mentioned, the problem is fixed by explicitly entering gnome-panel in the list of Startup Applications applet. This way I am happy Jaunty user (though I'm not really much excited by it). The only thing that bothers me is a question:Why? What's the heck is wrong?. The gnome-panel has been starting in Hardy, it started just fine after intermediate upgrade to Intrepid and then all at a sudden it stopped starting after, without this rather smooth, upgrade to Jaunty. -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] have to start gnome-panel manualy after upgrade to jaunty
2009/6/13 thirstyh2o thirsty...@gmail.com: Need your help folks, I upgraded my laptop from Hardy to Intrepid and then to Jaunty yesterday. The problem is that gnome-panel never starts upon boot. Executing [killall -v gnome-panels] reports no process killed. Tried to run [gnome-panel ] but it still dies when I close the terminal. There are seemingly not helpful warnings produced in console: If you're running this command from a terminal then closing the terminal, it is expected behaviour for the gnome-panel process to be killed when the terminal process is killed. The gnome-panel process will receive a HUP (hangup) signal when the terminal process is killed. Running it in the background does not stop this signal from killing the gnome-panel process. Try running [nohup gnome-panel] or maybe [nohup gnome-panel ] - don't know if you need to put it in the background or not, I have a feeling that nohup might already do that. As you can maybe guess from my description above and the name of the command, nohup means that the child process ignores the HUP signal and keeps running. I think the details are slightly more complicated than that, but that's the gist of the command. HTH Cofion/Regards, Neil. -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
Re: [ubuntu-uk] have to start gnome-panel manualy after upgrade to jaunty
2009/6/14 Neil Greenwood neil.greenwood@gmail.com: 2009/6/13 thirstyh2o thirsty...@gmail.com: Need your help folks, I upgraded my laptop from Hardy to Intrepid and then to Jaunty yesterday. The problem is that gnome-panel never starts upon boot. Executing [killall -v gnome-panels] reports no process killed. Tried to run [gnome-panel ] but it still dies when I close the terminal. There are seemingly not helpful warnings produced in console: If you're running this command from a terminal then closing the terminal, it is expected behaviour for the gnome-panel process to be killed when the terminal process is killed. The gnome-panel process will receive a HUP (hangup) signal when the terminal process is killed. Running it in the background does not stop this signal from killing the gnome-panel process. Try running [nohup gnome-panel] or maybe [nohup gnome-panel ] - don't know if you need to put it in the background or not, I have a feeling that nohup might already do that. As you can maybe guess from my description above and the name of the command, nohup means that the child process ignores the HUP signal and keeps running. I think the details are slightly more complicated than that, but that's the gist of the command. HTH Cofion/Regards, Neil. Sorry, I've just realised that that suggestion doesn't solve your problem! You could try creating a new user on the machine and see if that works. If so, try deleting/renaming the .gnome2 and .gnome2_private hidden directories in your home directory, then logging back in. This will lose any customisations you've made to Gnome, but should also get rid of the bad setting that is preventing the panel from running. Let us know if you have any more questions, or don't understand something I've written or something that happens when you try these instructions. Cofion, Neil. -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
