![]() |
ubuntu.com - launchpad.net - ubuntu help
|
|
|||||||
Hello, Unregistered You are browsing a READ only archive of the main support categories pre 4/21/2008. You will not be able to post or reply any threads in this section.
|
|
Desktop Environments Support for your Ubuntu desktop. Including Gnome, KDE and XFCE. |
|
|
Thread Tools | Display Modes |
|
|
#1 |
|
A Carafe of Ubuntu
![]() Join Date: Jan 2006
Location: Germany
Beans: 120
Ubuntu 9.10 Karmic Koala
|
I want to define some environment variables that are available for applications started from a gnome desktop launcher. Following suggestions found in this forum, I put the definitions in ~./gnomerc. They are ignored. I also made it executable and included the #!/bin/bash header, but that made no difference. The same export statements in ~./bashrc work fine, but only for terminal sessions. I also tried .gtkrc and .gtkrc-2.0 (as suggested in another message) but this was no different. None of them work. I did log out/in for each trial.
Help. |
|
|
|
|
|
#2 | |
|
Fresh Brewed Ubuntu
![]() |
Re: .gnomerc does not run
Quote:
Code:
~/.gnomerc then you can export variable like this Code:
export VAR_NAME=value; export VAR_NAME="string" no $ before the var name. I don't think the file need to be executable, simple read access for all should be enough. You have to logout/login gnome each time you change something in this file and want to see the changes.
__________________
my blog - linux user #423778 - Ubuntu user #4214 HP nc6400 Core duo 1,66GHz Ram 3Go GChip i945GM HD 250Go@7200rpm Get a dynamic blogroll - Install gnome globalmenu |
|
|
|
|
|
|
#3 |
|
A Carafe of Ubuntu
![]() Join Date: Jan 2006
Location: Germany
Beans: 120
Ubuntu 9.10 Karmic Koala
|
Re: .gnomerc does not run
Thanks, but I am already doing exactly what you specified.
~./gnomerc is in the same directory as ~./bashrc and the export statements are the same. .bashrc works and .gnomerc does not (apps started from desktop launchers see the variables as undefined). I cannot rule out some stupid mistake but I have looked and looked... |
|
|
|
|
|
#4 | |
|
Fresh Brewed Ubuntu
![]() |
Re: .gnomerc does not run
Quote:
Code:
ls ~/.gnomerc && cat ~/.gnomerc
__________________
my blog - linux user #423778 - Ubuntu user #4214 HP nc6400 Core duo 1,66GHz Ram 3Go GChip i945GM HD 250Go@7200rpm Get a dynamic blogroll - Install gnome globalmenu |
|
|
|
|
|
|
#5 |
|
A Carafe of Ubuntu
![]() Join Date: Jan 2006
Location: Germany
Beans: 120
Ubuntu 9.10 Karmic Koala
|
Re: .gnomerc does not run
Code:
~ $: ls ~/.gnomerc /home/mico/.gnomerc ~ $: cat ~/.gnomerc #!/bin/bash export HISTFILESIZE=10000 export HISTSIZE=10000 export MALLOC_CHECK=2 export programs="/home2/mico/programs" alias beroot="/home/mico/beroot/beroot" alias lang="/home2/mico/programs/shell/setlocale" So the real question is: why no alias command in a launcher? Or, is there a way? thanks |
|
|
|
|
|
#6 | |
|
Fresh Brewed Ubuntu
![]() |
Re: .gnomerc does not run
Quote:
Code:
sudo ln -sf /home/mico/beroot/beroot /usr/local/bin
__________________
my blog - linux user #423778 - Ubuntu user #4214 HP nc6400 Core duo 1,66GHz Ram 3Go GChip i945GM HD 250Go@7200rpm Get a dynamic blogroll - Install gnome globalmenu |
|
|
|
|
|
|
#7 |
|
A Carafe of Ubuntu
![]() Join Date: Jan 2006
Location: Germany
Beans: 120
Ubuntu 9.10 Karmic Koala
|
Re: .gnomerc does not run
Thanks Ayoli for your help. Your last post sent me on a wild ride. I tried a variation of your suggestion:
+ I created a directory ~/bin and put my program beroot there + I set PATH in ~/.gnomerc: export PATH=$PATH:~/bin + I made a desktop launcher with beroot as the command After logging out and back in, my desktop was locked up and no launchers appeared on the desktop. I bailed out with ctrl-alt-backspace and logged into my escape hatch root account. I cycled in and out again to be sure of the problem. Rebooted, no help. Then from root I deleted .gnomerc, which was no help. Then I deleted some files where gnome saves states and sessions. That fixed the problem and my gnome desktop came back. There was a huge nautilus log file, from the common problem of nautilus looping and writing debug messages (this comes and goes ever since 7.10, and I am astounded it has not been fixed by now). Note that I never ran beroot or any other non-gnome program. This adventure came solely from gnome. So I am giving up on this project. I have again been given a lesson that I have been given many times already: don't be adventurous and do uncommon things, because you will run into untested code and trash your system. |
|
|
|
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|