[Shr-User] Unknown internal dbus error: Process /usr/libexec/dbus-daemon-launch-helper received signal 6, 79 (dbus-glib-error-quark), code 26

[Steven **]

More info (hopefully related):
I did an opkg update ; opkg upgrade.  I get the following:
$ opkg upgrade
Upgrading frameworkd-config-shr-dev on root from
0.9.5.9+gitr1537+29e5316c13768dff8a94b879e8f30c7baebef0cc-93+0c164b58a270c689e7381e1c63e0a94ba1947af3-r7
to 0.9.5.9+gitr1542+e6a560a4435e0d14b892490df5fb6ae4a10a899a-93+0c164b58a270c689e7381e1c63e0a94ba1947Downloading
http://build.shr-project.org/shr-unstable/ipk//armv4t/frameworkd-config-shr-dev_0.9.5.9+gitr1542+e6a560a4435e0d14b892490df5fb6ae4a10a899a-93+0c164b58a270c689e7381e1c63e0a94ba1947af3-r7_armv4t.ipk
Collected errors:
 * ERROR: Cannot satisfy the following dependencies for
frameworkd-config-shr-dev:
	 *  frameworkd-config-shr (=
0.9.5.9+gitr1542+e6a560a4435e0d14b892490df5fb6ae4a10a899a-93+0c164b58a270c689e7381e1c63e0a94ba1947af3-r7)
*

opkg says frameworkd-config-shr is already installed and up-to-date.
So, I did a force-reinstall then did another opkg upgrade.  Same
error.  So, I reran the opkg upgrade with -nodeps.  Now I get the
following error in ophonekitd.log:
** (process:2105): DEBUG: list_resources_callback()
** (process:2105): DEBUG: Unknown error, try again in 10s
** (process:2105): DEBUG: list_resources()
Unknown internal dbus error: Activation of org.freesmartphone.ousaged
timed out, 79 (dbus-glib-error-quark), code 20


-Steven

On Tue, Jul 28, 2009 at 7:08 AM, Steven **<montgoss+shr at gmail.com> wrote:
> I did a reboot (because my phone would no longer auto-suspend) and now
> pretty much nothing works.
> See the ophonekitd log here: http://pastebin.com/m674dc9e4
> Various modules of SHR-Settings say "Couldn't connect to FSO"
>
> I tried someone's tip for restarting FSO without a full reboot and
> noticed /etc/init.d/frameworkd doesn't exist.  Was that removed or is
> that maybe part of the problem?  I copied that script from a working
> install and used it to start FSO, but it didn't help.  I still get the
> "Couldn't connect to FSO" errors.
>
> Anyone else seeing this?  Any idea how to fix it (besides reflashing)?
>
> Thanks,
> -Steven
>