Find the answer to your Linux question:
Results 1 to 5 of 5
I was able to get the internet and amsn to connect after having so many problems getting my cable internet to work. Here is the problem When i log in ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jul 2004
    Posts
    14

    very wierd problem, can't even show anyone what it is>>


    I was able to get the internet and amsn to connect after having so many problems getting my cable internet to work.

    Here is the problem

    When i log in as root from the main redhat screen, everything logs in and works fine. I installed my internet rpm file here and amsn etc.

    However, when i log in with my other username from the main redhat screen, unless i log in as root and log out of root then log in as 'username' i get an error. In other words i get an error when i reboot the system fully and first log in as 'username' All i get is an error box with a red cross in it, and continuous error boxes and then when i close them all there is a start menu at the top of the screen with a footprint as the start button. When i click on it there is a menu which looks like its been chopped up thinly and you can't see anything??? I hit ctrl alt f1, reboot and when i log in as root its fine???? I re-installed the system packages from the bootup cd and it is still there.

    I also tried adding the other username to the groups 'wheel' and 'root' and i am still unable to install programs etc with my normal username unless i use 'su' from the command line and do it all by commands?

    Any help would be appreciated.

    Is there a way to totally remove the other user? I just deleted it freom the group menu logged in as root and put a new user and set the group but it does the same thing

    Thanks again!!!

  2. #2
    Just Joined!
    Join Date
    Jul 2004
    Posts
    14

    forgot to mention

    here is some of the data from my messages file in var/log

    This i think is what happens when i try to log in as 'method' and not root. It just goes over and over until i ctrl alt f1 it.
    Also i noticed it thinks i have 2 cpus installed when i just have 1 p4 3.0c with hyperthreading Disabled.???? So whenever i download rpms i have to get the ones with the -smp extention???

    ************************************************** ************************************************** *****
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6694): starting (version 2.2.0), pid 6694 user 'method'
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6692): starting (version 2.2.0), pid 6692 user 'method'
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6690): Failed to get lock for daemon, exiting: Directory /home/method/.gconfd has a problem, gconfd can't use it
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6694): Bad permissions 777 on dir /home/method/.gconfd
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6696): starting (version 2.2.0), pid 6696 user 'method'
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6692): Bad permissions 777 on dir /home/method/.gconfd
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-669: starting (version 2.2.0), pid 6698 user 'method'
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6696): Bad permissions 777 on dir /home/method/.gconfd
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6684): Failed to get lock for daemon, exiting: Directory /home/method/.gconfd has a problem, gconfd can't use it
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6692): Failed to get lock for daemon, exiting: Directory /home/method/.gconfd has a problem, gconfd can't use it
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-669: Bad permissions 777 on dir /home/method/.gconfd
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6702): starting (version 2.2.0), pid 6702 user 'method'
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6696): Failed to get lock for daemon, exiting: Directory /home/method/.gconfd has a problem, gconfd can't use it
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6700): starting (version 2.2.0), pid 6700 user 'method'
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-669: Failed to get lock for daemon, exiting: Directory /home/method/.gconfd has a problem, gconfd can't use it
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6702): Bad permissions 777 on dir /home/method/.gconfd
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6694): Failed to get lock for daemon, exiting: Directory /home/method/.gconfd has a problem, gconfd can't use it
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6700): Bad permissions 777 on dir /home/method/.gconfd
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6702): Failed to get lock for daemon, exiting: Directory /home/method/.gconfd has a problem, gconfd can't use it
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6704): starting (version 2.2.0), pid 6704 user 'method'
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6700): Failed to get lock for daemon, exiting: Directory /home/method/.gconfd has a problem, gconfd can't use it
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6706): starting (version 2.2.0), pid 6706 user 'method'
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6704): Bad permissions 777 on dir /home/method/.gconfd
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-670: starting (version 2.2.0), pid 6708 user 'method'
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6704): Failed to get lock for daemon, exiting: Directory /home/method/.gconfd has a problem, gconfd can't use it
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-670: Bad permissions 777 on dir /home/method/.gconfd
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6706): Bad permissions 777 on dir /home/method/.gconfd
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-670: Failed to get lock for daemon, exiting: Directory /home/method/.gconfd has a problem, gconfd can't use it
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6706): Failed to get lock for daemon, exiting: Directory /home/method/.gconfd has a problem, gconfd can't use it
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6711): starting (version 2.2.0), pid 6711 user 'method'
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6713): starting (version 2.2.0), pid 6713 user 'method'
    Jul 21 10:01:31 cpe-138-217-58-218 gconfd (method-6711): Bad permissions 777 on dir /home/method/.gconfd


    ************************************************** ************************************************** *******

    I also get this


    Jul 21 23:09:57 cpe-138-217-58-218 modprobe: modprobe: Can't locate module sound-slot-0
    Jul 21 23:09:57 cpe-138-217-58-218 modprobe: modprobe: Can't locate module sound-service-0-3
    Jul 21 23:10:15 cpe-138-217-58-218 modprobe: modprobe: Can't locate module sound-slot-0
    Jul 21 23:10:15 cpe-138-217-58-218 modprobe: modprobe: Can't locate module sound-service-0-3
    Jul 21 23:10:19 cpe-138-217-58-218 modprobe: modprobe: Can't locate module sound-slot-0
    Jul 21 23:10:19 cpe-138-217-58-218 modprobe: modprobe: Can't locate module sound-service-0-3
    Jul 21 23:10:35 cpe-138-217-58-218 modprobe: modprobe: Can't locate module sound-slot-0
    Jul 21 23:10:35 cpe-138-217-58-218 modprobe: modprobe: Can't locate module sound-service-0-3
    Jul 21 23:11:57 cpe-138-217-58-218 modprobe: modprobe: Can't locate module sound-slot-0
    Jul 21 23:11:57 cpe-138-217-58-218 modprobe: modprobe: Can't locate module sound-service-0-3

  3. #3
    Linux Newbie
    Join Date
    May 2004
    Location
    Boston, MA
    Posts
    246
    As far as the first set of error messages goes, make sure the permissions on the directories /home/method/.gconf and /home/method/.gconfd are correct. They should be owned by you and your group, and rwx by the user. Try to get to a text console as user method, and type
    Code:
    $ ls -la ~/ | grep gconf                # Tells you the permissions of the directories you want in your home directory
      drwx------   4 method method          4096 Jul 20 23:14 .gconf
      drwx------   2 method method          4096 Jul 20 23:18 .gconfd
    This is the output you should get, but you'll probably get something more like
    Code:
      drwxrwxrwx   4 method method          4096 Jul 20 23:18 .gconfd
    or
    Code:
      drwxrwxrwx   4 root root              4096 Jul 20 23:18 .gconfd
    If this is the case, change the owner and group to method with the chown and chgrp commands, and change the permissions to 700 with
    Code:
    $ chmod 700 .gconf .gconfd
    You might also want to make sure these are the permissions of the file(s) inside .gconfd. Hope this helps a little.
    Situations arise because of the weather,
    And no kinds of love are better than others.

  4. #4
    Linux Guru kkubasik's Avatar
    Join Date
    Mar 2004
    Location
    Lat: 39:03:51N Lon: 77:14:37W
    Posts
    2,396
    It looks like your user doesnt have read permissons on your system drive, so when you log in as root, you have acess, but you need to change the driver permissions. But the odd part is, i thouhgt that 777 was full access.... try
    Code:
    chmod 777 systemdevicename
    but that might do nothing at all as im not even sure the command syntax is correct.
    Avoid the Gates of Hell. Use Linux
    A Penny for your Thoughts

    Formerly Known as qub333

  5. #5
    Just Joined!
    Join Date
    Jul 2004
    Posts
    14

    thanks so much!

    Thanks for your help, it was the permissions, i tried to change the permissions on the method dir in home via root login. When i tried the commands above it just listed no permission for all of it and gave me the %bash console >>

    I removed the user method and home dir, and then just added it again and all is ok now.

    Thanks again for your help

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •