Find the answer to your Linux question:
Results 1 to 5 of 5
Hi folks, Gentoo_64 gnome-light Having encountered following problem Desktop --> Administration --> Services Login as root to start "Service settings" windows Following items displayed on the windows; Code: Graphical Login ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Guru
    Join Date
    Sep 2004
    Posts
    1,763

    Service settings not working


    Hi folks,

    Gentoo_64
    gnome-light

    Having encountered following problem

    Desktop --> Administration --> Services

    Login as root to start "Service settings" windows

    Following items displayed on the windows;
    Code:
    Graphical Login manager (xdm) [checked]
    Printer service (cupsd) [not checked]
    Remote shell server (sshd) [not checked]
    Clicking any empty box [ ] started following Error warning
    Code:
    The Application "services-admin" has quit unexpectedly.
    You can inform the developers of what happened to help them fix it.  Or you can restart the application right now.
    Restarted Application returned to Login box. Repeating the above steps still popup the "Error" warning window.

    Please advise how to fix this problem. TIA


    B.R.
    satimis

  2. #2
    Linux Enthusiast gruven's Avatar
    Join Date
    Dec 2004
    Location
    Arkansas
    Posts
    541
    Open a shel, and type
    Code:
    /etc/init.d/sshd restart
    and see if it throws an error. You can do the same thing for cupsd (the cups daemon). That will tell you where to look for the error, or if you need to recompile said programs.

    Linux User #376741
    Code is Poetry

  3. #3
    Linux Guru
    Join Date
    Sep 2004
    Posts
    1,763
    Hi gruven,

    Open a shel, and type
    Code:
    /etc/init.d/sshd restart
    and see if it throws an error.
    # /etc/init.d/sshd restart
    Code:
     * Starting eth0
     *   Bringing up eth0
     *     dhcp
     *       Running dhcpcd ...
    Error, timed out waiting for a valid DHCP server response                                                  [ !! ] * ERROR:  cannot start sshd as net.eth0 could not start
    Problem remained intact. It killed the broadband connection as well.

    # pppoe-status
    pppoe-status: Link is attached to ppp0, but ppp0 is down

    # ifconfig
    Code:
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
    # pppoe-start
    Code:
    pppoe-start: There already seems to be a PPPoE connection up (PID 5597)
    # kill 5597
    # pppoe-start
    . Connected!


    B.R.
    satimis

  4. #4
    Linux Enthusiast gruven's Avatar
    Join Date
    Dec 2004
    Location
    Arkansas
    Posts
    541
    It looks to me like you don't have your startup networking working correctly. That is why sshd isn't starting when you boot up. You need to correct that issue first, or just start sshd manually because the startup init.d script is dependent upon the ethernet (eth0, eth1, etc...) script.

    Linux User #376741
    Code is Poetry

  5. #5
    Linux Guru
    Join Date
    Sep 2004
    Posts
    1,763
    Hi gruven,

    gnome-light

    It looks to me like you don't have your startup networking working correctly.
    My broadband connection is working without problem. I still run "pppoe-start" on console to connect. Please advise where and how to check and correct the problem. Tks.

    or just start sshd manually because the startup init.d script is dependent upon the ethernet (eth0, eth1, etc...) script.
    On running sshd manually, besides killing the broadband connection the problem can't be solved. The Error warning still popup;
    Code:
    The Application "services-admin" has quit unexpectedly.
    
    You can inform the developers of what happened to help them fix it.  Or you can restart the application right now.
    B.R.
    satimis

Posting Permissions

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