Results 1 to 8 of 8

Thread: gdm problem

  1. #1

    Default gdm problem

    I haven't messing with my system for a few days so it's been sitting there with the screen blanked. It's a fresh install of SUSE 11.1 (64-bit) running GNOME. When I woke the system up today, the screen is just scrolling the following message:

    Code:
    gdm[2732]: WARNING: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: connection refused
    Any idea what this means? I have no clue. Where should I start with troubleshooting?

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,193
    Blog Entries
    1

    Default Re: gdm problem

    I don't have definitive answer here, (someone else may do), but to get started....

    Boot up in runlevel 3 (text mode) by entering '3' at grub boot option.

    From CLI as root user, do

    rcdbus status (is dbus running?)

    If not, try

    rcdbus start

    Look for errors and post here. If all ok, do

    init 5

    to start graphical desktop.

    I'm guessing this could be as a result of an incomplete upgrade or system crash ???

    Good luck.

  3. #3

    Default Re: gdm problem

    I did that and rcdbus was running. I'm afraid that if it was a crash it will happen again.

  4. #4
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,193
    Blog Entries
    1

    Default Re: gdm problem

    Try to update system from command prompt (as root) with

    zypper up -t package

    See how that goes...

  5. #5

    Default Re: gdm problem

    Quote Originally Posted by deano_ferrari View Post
    Try to update system from command prompt (as root) with

    zypper up -t package

    See how that goes...
    It went great. No problems. It updated about a dozen things. Hopefully, I won't have any more problems.

  6. #6

    Default Re: gdm problem

    I got the error message again. Here's what happened....

    The system sat all night. The screen was blanked. I moved the mouse to wake it up (it's not in standby or anything, just screensaver and monitor blanks after a while). I got the monitor back, but couldn't get out of the screensaver until I hit the spacebar. Is that normal behavior? Anyway, I entered YAST. I wanted to check to find out if some software was installed. So I went to Software Management. I got an error message saying it couldn't start because a process was already using it or something like that. I think it said it was called "ProcessID." Rather than mess with that, I decided to reboot. So I accessed the GNOME menu and selected Shutdown. Normally, this gives a shutdown menu (turn off, reboot, etc). This just went to CLI and then started giving those error messages again. I checked the status of rcdbus and it said it was unused. So then I did "rcdbus start" and the GNOME started again and it appears to be running fine. So it seems like there is a problem with rcdbus shutting down when the screensaver's been running for a fairly long time.

    Anybody have any suggestions on how I can further troubleshoot this problem?

  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,193
    Blog Entries
    1

    Default Re: gdm problem

    Take a look at /var/log/messages. Might show up there...

  8. #8

    Arrow Re: gdm problem

    After looking through the /var/log/messages, here's what I found:

    I've got this repeated throughout the file every few minutes.
    Code:
    Jan 12 10:09:38 linux-lyx5 kernel: usb 1-8: can't restore configuration #1 (error=-71)
    Jan 12 10:09:38 linux-lyx5 kernel: usb 1-8: USB disconnect, address 68
    Jan 12 10:09:38 linux-lyx5 kernel: scsi 1708:0:0:2: rejecting I/O to dead device
               <repeat above message x3>
    Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
    Jan 12 10:09:38 linux-lyx5 kernel: scsi 1708:0:0:2: [sdd] Sense not available.
    Jan 12 10:09:38 linux-lyx5 kernel: scsi 1708:0:0:2: rejecting I/O to dead device
               <repeat above message x3>
    Jan 12 10:09:38 linux-lyx5 kernel: scsi 1708:0:0:2: [sdd] READ CAPACITY failed
    Jan 12 10:09:38 linux-lyx5 kernel: scsi 1708:0:0:2: [sdd] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
    Jan 12 10:09:38 linux-lyx5 kernel: scsi 1708:0:0:2: [sdd] Sense not available.
    Jan 12 10:09:38 linux-lyx5 kernel: scsi 1708:0:0:2: rejecting I/O to dead device
    Jan 12 10:09:38 linux-lyx5 kernel: scsi 1708:0:0:2: [sdd] Write Protect is off
    Jan 12 10:09:38 linux-lyx5 kernel: scsi 1708:0:0:2: [sdd] Mode Sense: 00 00 00 00
    Jan 12 10:09:38 linux-lyx5 kernel: scsi 1708:0:0:2: [sdd] Assuming drive cache: write through
    Jan 12 10:09:38 linux-lyx5 kernel: scsi 1708:0:0:3: rejecting I/O to dead device
               <repeat above section but for sde, sdb & sdc 2x each>
    Jan 12 10:09:39 linux-lyx5 kernel: usb 1-8: new high speed USB device using ehci_hcd and address 69
    Jan 12 10:09:39 linux-lyx5 kernel: usb 1-8: configuration #1 chosen from 1 choice
    Jan 12 10:09:39 linux-lyx5 kernel: scsi1709 : SCSI emulation for USB Mass Storage devices
    Jan 12 10:09:39 linux-lyx5 kernel: usb 1-8: New USB device found, idVendor=058f, idProduct=6362
    Jan 12 10:09:39 linux-lyx5 kernel: usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    Jan 12 10:09:39 linux-lyx5 kernel: usb 1-8: Product: Mass Storage Device
    Jan 12 10:09:39 linux-lyx5 kernel: usb 1-8: Manufacturer: Generic
    Jan 12 10:09:39 linux-lyx5 kernel: usb 1-8: SerialNumber: 058F312D81B
    Jan 12 10:09:39 linux-lyx5 kernel: usb-storage: device found at 69
    Jan 12 10:09:39 linux-lyx5 kernel: usb-storage: waiting for device to settle before scanning
    Jan 12 10:09:39 linux-lyx5 kernel: scsi 1709:0:0:0: Direct-Access     Generic  USB SD Reader    1.00 PQ: 0 ANSI: 0
    Jan 12 10:09:39 linux-lyx5 kernel: sd 1709:0:0:0: [sdb] Attached SCSI removable disk
    Jan 12 10:09:39 linux-lyx5 kernel: sd 1709:0:0:0: Attached scsi generic sg2 type 0
    Jan 12 10:09:39 linux-lyx5 kernel: scsi 1709:0:0:1: Direct-Access     Generic  USB CF Reader    1.01 PQ: 0 ANSI: 0
    Jan 12 10:09:39 linux-lyx5 kernel: sd 1709:0:0:1: [sdc] Attached SCSI removable disk
    Jan 12 10:09:39 linux-lyx5 kernel: sd 1709:0:0:1: Attached scsi generic sg3 type 0
    Jan 12 10:09:39 linux-lyx5 kernel: scsi 1709:0:0:2: Direct-Access     Generic  USB SM Reader    1.02 PQ: 0 ANSI: 0
    Jan 12 10:09:39 linux-lyx5 kernel: sd 1709:0:0:2: [sdd] Attached SCSI removable disk
    Jan 12 10:09:39 linux-lyx5 kernel: sd 1709:0:0:2: Attached scsi generic sg4 type 0
    Jan 12 10:09:39 linux-lyx5 kernel: scsi 1709:0:0:3: Direct-Access     Generic  USB MS Reader    1.03 PQ: 0 ANSI: 0
    Jan 12 10:09:39 linux-lyx5 kernel: sd 1709:0:0:3: [sde] Attached SCSI removable disk
    Jan 12 10:09:39 linux-lyx5 kernel: sd 1709:0:0:3: Attached scsi generic sg5 type 0
    Jan 12 10:09:39 linux-lyx5 kernel: usb-storage: device scan complete
    Jan 12 10:09:42 linux-lyx5 kernel: usb 1-8: reset high speed USB device using ehci_hcd and address 69
    I'm not sure what the hell that would be. I've got a USB mouse hooked up, but I doubt that's the problem. I've also got a memory card reader that's got an irda and two USB ports. I suspect that is somehow causing this problem, though I don't really know what the problem is (I'm no guru at interpreting error messages).

    Right after that one is what I suspect is causing the problem:
    Code:
    Jan 12 10:09:48 linux-lyx5 kernel: dbus-daemon[2483] general protection ip:7fa6307c31ee sp:7fff387e2590 error:0 in dbus-daemon[7fa630799000+4d000]
    Jan 12 10:09:48 linux-lyx5 console-kit-daemon[2770]: GLib-CRITICAL: g_async_queue_unref: assertion `queue->waiting_threads == 0' failed
    Jan 12 10:09:48 linux-lyx5 avahi-daemon[3501]: Disconnected from D-Bus, exiting.
    Jan 12 10:09:48 linux-lyx5 avahi-daemon[3501]: Got SIGQUIT, quitting.
    Jan 12 10:09:48 linux-lyx5 gnome-keyring-daemon[4355]: Scheduling hal init retry
    Jan 12 10:09:48 linux-lyx5 avahi-daemon[3501]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.6.2.47.
    Jan 12 10:09:48 linux-lyx5 nm-system-settings: disconnected from the system bus, exiting.
    Jan 12 10:09:48 linux-lyx5 nm-system-settings: nm_sysconfig_settings_remove_connection: assertion `NM_IS_SYSCONFIG_SETTINGS (self)' failed
    Jan 12 10:09:48 linux-lyx5 gnome-session[3647]: WARNING: Could not connect to ConsoleKit: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    Jan 12 10:09:48 linux-lyx5 gnome-session[3647]: WARNING: Could not connect to ConsoleKit: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
    Jan 12 10:09:48 linux-lyx5 gnome-session[3647]: WARNING: Could not connect to ConsoleKit: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
    Jan 12 10:09:48 linux-lyx5 console-kit-daemon[2770]: GLib-CRITICAL: g_async_queue_push: assertion `g_atomic_int_get (&queue->ref_count) > 0' failed
    Jan 12 10:09:48 linux-lyx5 kernel: console-kit-dae[3164]: segfault at 8 ip 00007fee8c4b9019 sp 00007fee8d5c60a0 error 4 in libglib-2.0.so.0.1800.2[7fee8c48c000+c3000]
    Jan 12 10:09:48 linux-lyx5 console-kit-daemon[2770]: GLib-CRITICAL: g_async_queue_lock: assertion `g_atomic_int_get (&queue->ref_count) > 0' failed
    Jan 12 10:09:48 linux-lyx5 console-kit-daemon[2770]: GLib-CRITICAL: g_async_queue_length_unlocked: assertion `g_atomic_int_get (&queue->ref_count) > 0' failed
    Jan 12 10:09:52 linux-lyx5 gdm[3103]: WARNING: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
    Does anybody see anything there that makes sense? Obviously, there was a GPF, but I don't really know what caused it. Could it be related to the USB messages above?

Posting Permissions

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