Tiny Core Linux
dCore Import Debian Packages to Mountable SCE extensions => dCore X86 => dCore x86 Imported Extensions => Topic started by: jls on January 29, 2015, 09:02:44 AM
-
Hi
I'm on trusty, I think there is a problem with udisks:
ps shows:
message+ 3913 1 0 14:26 ? 00:00:00 /usr/bin/dbus-daemon --system
and
jls@eeepc:~$ udisksctl dump
(process:16278): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(process:16278): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:16278): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(process:16278): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:16278): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(process:16278): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:16278): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(process:16278): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:16278): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(process:16278): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(process:16278): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Error connecting to the udisks daemon: Error calling StartServiceByName for org.freedesktop.UDisks2: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 127
jls@eeepc:~$
thanks Jason
-
Ok, on a remote login of my dCore-jessie box the command works, I will try to find out tonight what the issue is with ub-dCore-trusty.
Thanks.
-
Here is the output on ub-dCore-trusty of the same command, screenshot attached.
-
I've the following in debextra
http://packages.bodhilinux.com/bodhi trusty main
http://archive.canonical.com/ubuntu/ trusty partner
http://dl.google.com/linux/talkplugin/deb/ stable main
http://it.archive.ubuntu.com/ubuntu/ trusty multiverse
http://it.archive.ubuntu.com/ubuntu/ trusty restricted
http://security.ubuntu.com/ubuntu trusty-security main
http://security.ubuntu.com/ubuntu trusty-security multiverse
http://security.ubuntu.com/ubuntu trusty-security restricted
http://security.ubuntu.com/ubuntu trusty-security universe
http://sourceforge.net/projects/ubuntuzilla/files/mozilla/apt all main
http://it.archive.ubuntu.com/ubuntu/ trusty universe
http://it.archive.ubuntu.com/ubuntu/ trusty-updates main
http://it.archive.ubuntu.com/ubuntu/ trusty-updates multiverse
http://it.archive.ubuntu.com/ubuntu/ trusty-updates restricted
http://it.archive.ubuntu.com/ubuntu/ trusty-updates universe
are they good or some are uneeded?
what about your debextras?
-
Ok. When re-importing udisks2, which repo does it say the package is from? That would help in finding the issue.
-
udisks2 is a standard ubuntu trusty package.
-
Ok, it is probably an incompatibility with a linked library that is being installed from a package in those other repos.
I am not sure how to remedy that situation except to be aware that installing packages from other repos can cause potential breakage.
Has "updatesce -a" been run lately, and all SCEs been updated? That would eliminate the variable of old packages being presently installed.
-
I installed yesterday ub-dcore-tusty
-
At this point it may well be that library packages from the mix of the repos being used are not playing well with each other.
-
I imported udisks2 with your same /opt/debextra contents as listed above, and still works good.
I am updating my whole SCE directory to that debextra and will see if that makes udisks fail. If it does not, then it almost surely has to be an issue of conflict due to outdated SCEs being loaded into the system.
-
after a re-import it works also on my system, strange cause I started using trusty only 2 days ago
-
I just finished re-importing my system and it still works ok as well. Good thing is that it is working now.