|
From: Ed M. <edm...@ma...> - 2005-07-17 17:55:29
|
still no go... On Jul 16, 2005, at 11:30 PM, Don Tanner wrote: > 1) Run gnome under a freshly created user please. > that rus good, no problems there > 2) Running gnome under the user you are having the issues > check "Sessions->Session Options" and make sure > "Automatically save changes to session" is not checked... > Logout and log back in. Maybe somehow in the Session > it got saved when it was in a state with two panels > running. If so then you will need to remove the second > instance of gnome-panel from that session and save it as such. > by telling it save the session on logout in the popup > dialogue when you logout. Not having > "Automatically save changes to session" will force it to > popup a dialogue box asking whther or not to save the current > session or not. > well i have tried to unchecked that box before and do this procedure, but its really hard to delete as you say, removing the copy in the session with 50 for an order just re adds it when i click apply even though that box is not checked (after clicking apply). so then i try the other copy of it and it kills the panel and both copies disappear (after clicking apply), now there is no logout thing so i have to control-alt-backspace to logout, i login after that and the session now has both panels in it and i'm back to the beginning... > 3) I would like to know the results of running > gnome under a newly created user. That would > narrow things down considerably if running as the newly > created user did not have the same issue. > > > Thanks, > Don > > On Sat, 2005-07-16 at 20:05 -0400, Ed Martin wrote: >> well i whipped /tmp and check my home folder for any files with bad >> perms an still no go >> >> maybe a pic of the gnome-sessions program will help... >> >> http://server.antiwindows.gotdns.com:8080/~edman007/Screenshot- >> Sessions.png >> >> >> On Jul 16, 2005, at 6:53 PM, Don Tanner wrote: >> >>> Hello Ed, >>> >>> Clear out OR chown any files/directories with your user name >>> that you are running gnome under making sure that these >>> files/directories are owned by that user. >>> You will need to shutdown gnome before doing this. >>> >>> ie: the user you run gnome as in the file/directory name >>> in /tmp/ is what you are looking for. >>> >>> I have run across this several times after an upgrade >>> and root had become the owner of the /tmp/file.directories >>> and they should be owned by the user you run gnome as, >>> recursively of course. >>> Look for .files/directories also. >>> Find these files/directories in /tmp/ >>> (mine will have "dtanner" in the file.directory name >>> because that is the user I run gnome as) >>> and you need to replace "dtanner" in these files I am listing with >>> the >>> user that is running gnome for my setup. (my user I run gnome as) >>> >>> Here is a list of the files/directories I had to change the ownership >>> back to my that user that I run gnome under... >>> >>> ----- >>> /tmp/gconfd-dtanner/ >>> /tmp/orbit-dtanner/ >>> /tmp/orbit-dtanner-2828a868/ <- the numbers will be different for >>> you. >>> /tmp/orbit-dtanner-a86808b8/ <- the numbers will be different for >>> you. >>> ----- >>> ie: /tmp/gconfd-dtanner/ will be >>> named /tmp/gconfd-YOUR-USER-THAT-RUNS-GNOME/ >>> and the same for all the directories I listed above >>> as far as replacing "dtanner" with "your-user-that-runs-gnome" >>> in the directory names. >>> >>> 1) The first thing I would try would be to shutdown >>> gnome completely. >>> >>> 2) cd /tmp >>> >>> 3) Run this command please: >>> >>> "chown -R your-gnome-user.users gconfd-[your-user-that-runs-gnome]" >>> >>> Do the same for all the directories/files that contain your >>> user name that runs gnome that may be owned by root.root >>> >>> The files or directories that contain your-user-that-runs-gnome >>> in the file or directory NAME should be all be owned by >>> the user that runs gnome and not root. chown all these >>> that you find in /tmp/ >>> >>> 5) Look for any files or directories that contain >>> "your-user-that-runs-gnome" in the filename >>> or more than likely directory names and perform the >>> "chown -R your-gnome-user.users foo" >>> >>> 6) Restart Gnome. >>> >>> 7) If all else fails then get ready to reboot. >>> Clean out /tmp/* completely and reboot. >>> >>> This should fix your problem. >>> Let me know how it works out Ed. >>> >>> Thanks, >>> Don >>> >>> On Sat, 2005-07-16 at 06:42 -0400, Ed Martin wrote: >>>> ever since upgrading to gware 2.10.2 i have had problems with >>>> gnome-panel starting twice on login, gnome-panel detects this and >>>> gives >>>> an annoying little popup saying that the second one isn't going to >>>> start if there is already one running, which is good, but i still >>>> get >>>> the stupid popup every time i login >>>> >>>> i think it has something to do with gnome-sessions thing, when i >>>> look >>>> at that it seems to add gnome-panel in there once for the running >>>> process and then it looks like something forces an extra gnome-panel >>>> with come config stuff in the (as it has "gnome-panel >>>> --sm-config-prefix blah blah" and a non default order, one has 50 >>>> the >>>> other has 40) >>>> >>>> is there anything to do to get that stupid popup to go away, its >>>> very >>>> annoying? it weird that gnome-panel is trying to start twice and i >>>> cant >>>> stop it. I want to stop it >>> >>> -- >>> http://gware.org/ >>> >>> Freenode - #gware >>> >> > -- > http://gware.org/ > > Freenode - #gware > |