Tiny Core Linux
dCore Import Debian Packages to Mountable SCE extensions => dCore X86 => dCore x86 Imported Extensions => Topic started by: uggla on September 20, 2013, 12:48:11 PM
-
Virt-manager says:
internal error Unable to locate libvirtd daemon in $PATH
I have virt-manager, qemu and libvirt0 in mydesktop-megapackage.
-
Ok, I will look into it.
-
It loads here as a standalone import, I will try again as part of a file list import.
https://docs.google.com/file/d/0B_xwlkY06TgZVUg2RFBLUFc3VkU/edit?usp=sharing
-
Ok, I see, libvirt-bin needed to be added as a dep. Added, re-import and test.
-
libvirtd won't start: "Initialization failed"
-
It seems a python issue, I will look more deeply soon.
-
I adjusted the dependency list and startup scripts of some of the python related dependent packages, virt-manager now starts on my machine. Please re-import and test.
-
Now I get:
~ $ virt-manager
Traceback (most recent call last):
File "/usr/share/virt-manager/virt-manager.py", line 383, in <module>
main()
File "/usr/share/virt-manager/virt-manager.py", line 286, in main
raise gtk_error
ImportError: No module named cairo
-
I see here too after a re-import. I will find what was left out of the fix.
-
Now I see exaile does not work too, also a pygtk package. Something in the fix has broken things. Will try to fix it tonight.
-
Should be fixed now.
It was a simple issue of a broken symlink in the python-support package. I at first made a kludge in the python-cairo startup script to enable cairo to be imported, but then virtinst could not be imported. I saw there were broken symlinks in the python-support package. /usr/lib/python2.7/dist-packages/python-support.pth and /usr/lib/python2.6/dist-packages/python-support.pth. Those are the files that set the python path so it finds modules, very important and surely affects other python related packages as well.
Some files in Debian packages are relative symlinks, and that works as is when installing those files to the filesystem, but do not work when symlinking them. The fix is to simply copy those symlinks to the live filesystem, so the relative path thing works. "rm /usr/lib/python2.7/dist-packages/python-support.pth && cp -a /tmp/tcloop/PKGNAME/usr/lib/python2.7/dist-packages/python-support.pth /usr/lib/python2.7/dist-packages/" takes care of it in the startup script.
Broken symlinks in any package is always a red flag. Using the below command identifies which files in the live filesystem are broken symlinks, install the findutils package for this:
find /usr -type l -xtype l
I detail this so that advanced users can help in testing and finding issues as they arise.
-
I get
find: unrecognized: -xtype
???
-
I copied and pasted that above command into my terminal, and it works. What is the result of the command "which find"?
-
Works for me, l is lower case L
And find is GNU 4.4.2 from findutils.tcz
Sent from my iPad using Tapatalk HD
-
I copied and pasted that above command into my terminal, and it works. What is the result of the command "which find"?
$ which find
/bb/find
Findutils is loaded from mega-sce.
-
Ok, your system is using the busybox find.
What is the output of this command, assuming your mega sce is installed?:
grep findutils: /tmp/.installed
-
$ grep findutils: /tmp/.installed
findutils:
-
two more commands, "echo $PATH"
and ls -l /usr/bin/find
-
$ echo $PATH
//.local/bin:/usr/local/sbin:/usr/local/bin:/bb:/bin:/sbin:/usr/bin:/usr/sbin:/etc/sysconfig/tcedir/ondemand
$ ls -l /usr/bin/find
lrwxrwxrwx 1 root root 34 Oct 17 22:05 /usr/bin/find -> /tmp/tcloop/mydesktop/usr/bin/find
-
PATH is prioritized from left to right, therefore /bb/find is prioritized over /usr/bin/find.
-
The correct PATH from dCore /etc/profile is:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/bb"
-
The correct PATH from dCore /etc/profile is:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/bb"
Thanks, that solved it.