Re: [opensuse] Errors after d-bus updates on 10.3

Jeffrey L. Taylor wrote:
Quoting David C. Rankin <drankinatty@xxxxxxxxxxxxxxxxxx>:
Jeffrey L. Taylor wrote:
After the d-bus updates I started getting the following errors:

Mar 17 21:21:13 odysseus powersaved[3302]: WARNING (sendMethodCallWithReturn:483) Could not send method call to D-BUS system bus: Rejected send message, 1 matched rules; type="method_call", sender=":1.14" (uid=0 pid=3302 comm="/usr/sbin/powersaved -d -f /var/run/acpid.socket -") interface="org.freedesktop.Hal.Device.CPUFreq" member="GetCPUFreqGovernor" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=2351 comm="/usr/sbin/hald --daemon=yes "))
[snip]
I think all related packages are stock SuSE 10.3. Any suggestions?

TIA,
Jeffrey
WTF???

I should have perused the list before updating :(

Mar 18 03:46:09 nirvana syslog-ng[23379]: last message repeated 19 times
Mar 18 03:46:10 nirvana console-kit-daemon[2488]: WARNING: Couldn't connect to
system bus: Failed to connect to socket /var/run/dbus/system_bus_socket:
Connection refused
[snip]
Jeffrey, did you file a bug report? If so what's the number so I can add
comments. (I know I could search, but what are friends for...)


I encountered this problem also. Solved by rebooting.

HTH,
Jeffrey


What?? Now we have to 'reboot' after updates? Where have I heard that before?

After 24 hours of:

Mar 18 17:39:43 bonza console-kit-daemon[2294]: WARNING: Couldn't connect to
system bus: Failed to connect to socket /var/run/dbus/system_bus_socket:
Connection refused
Mar 18 17:40:01 bonza syslog-ng[25812]: last message repeated 6 times
Mar 18 17:40:01 bonza /usr/sbin/cron[20382]: (assistance) CMD
(/usr/local/bin/Learn_as_spam_cron)
Mar 18 17:40:04 bonza console-kit-daemon[2294]: WARNING: Couldn't connect to
system bus: Failed to connect to socket /var/run/dbus/system_bus_socket:
Connection refused
Mar 18 17:40:23 bonza syslog-ng[25812]: last message repeated 6 times
Mar 18 17:40:25 bonza console-kit-daemon[2294]: WARNING: Couldn't connect to
system bus: Failed to connect to socket /var/run/dbus/system_bus_socket:
Connection refused
Mar 18 17:41:23 bonza syslog-ng[25812]: last message repeated 19 times
Mar 18 17:41:25 bonza console-kit-daemon[2294]: WARNING: Couldn't connect to
system bus: Failed to connect to socket /var/run/dbus/system_bus_socket:
Connection refused
Mar 18 17:42:23 bonza syslog-ng[25812]: last message repeated 19 times

I rebooted -- it worked.

--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

Relevant Pages

  • Re: karmic to lucid success
    ... there is one problem i met when i upgrade from 9.10 to 10.04, the gvim does ... None of that involved updating to a new Win OS like Vista or Win7 ... Woops, I forgot that I also needed to update CCleaner, Spybot, AVG, ... rebooting after the "updates". ...
    (Ubuntu)
  • Re: karmic to lucid success
    ... claws-mail, ekiga, abiword, gnumeric, gimp, ristretto, evince, ... None of that involved updating to a new Win OS like Vista or Win7 ... Woops, I forgot that I also needed to update CCleaner, Spybot, AVG, ... rebooting after the "updates". ...
    (Ubuntu)
  • Re: Help needed on IE6 after attack of ibm00003 virus
    ... After updating, ... scanning, deleting files and rebooting everything seemed fine. ...
    (alt.comp.anti-virus)
  • [5.4-PRE regression] radeon drm => instant reboot
    ... After updating the world and kernel, ... rebooting, etc. after startx I get an instant reboot (Xorg prints the ... Xorg.0.log.new.no_drm - Xorg log on the new kernel without drm ...
    (freebsd-current)
  • Re: Printer & Scanner drivers quit working?
    ... Friends - Recently, about 2-3 hours after rebooting, when I try to ... print or scan I get balloons telling me the device is not installed, ... USB ports, Properties, on PowerManagement tab, there's a power saver setting ...
    (microsoft.public.windowsxp.hardware)