resolved
dkuchay
offlineMember
Using xvkbd on version 3 and I see that there are no usable fonts. Xvkbd wont open. I am lang=en kmap=us and from research I see
xfonts-75dpi
xfonts-100dpi
as the solution to this problem however I do not see any slitaz packages for.
Since xvkbd is in the repo I would assume that someone else has run in to this. Is there a better workaround than converting say a debian package?
dkuchay
offlineMember
update, I tried converting debian packages but had a hard time doing so. Debian uses all sorts of underscores and plus signs in their packages. IE:
xfonts-75dpi-7.7+2_i386.deb
When I convert these I saw all sorts of diiffernt outcomes from what what I input including titles with / char’s.
I renamed these files to only . notation. It seems tazpkg convert looks at the tile of the package from within and renames the tazpkg away from any retitling of the deb file. The outcome was that I could install xfonts-75dpi however when it came to xfonts-utils the resulting tazpkg had an error about not being able to use fs/*
Thinking that more of my issues are related to text encoding. Is UTF-8 possible? I might be able to get xvkbd to start if it was.
The specific xvkbd error is that there are no ISO8859 fonts available.... no usable fonts.
dkuchay
offlineMember
Tried converting both debian stretch and fedora 10 fonts both 100 and 75 with tazpkg. The fedora packages indicated ISO8859 in the title. Didnt work. Tried editing /etc/locale.conf to include utf-8 and that also didnt work. Slitaz only offers one virtual keyboard but you have matchbox in repos. No matchbox keyboard.... Would be better. I love this distribution but I seem to hit many many hurdles.
dkuchay
offlineMember
would someone be able to suggest how to install iso8859 fonts in slitaz? I commented out the LC_ALL line in /etc/locale.conf, writefs and rebooted but xvkbd still asks for 8859 fonts. I hear that matchbox keyboard works with. only one font on the system. My only question is weather or not repo maintainers enabled —keyboard when building the matchbox package. iIt has similar payload to xvkbd and deps At current on default core iso with en and us selected your xvkbd application is not working. Please advise
dkuchay
offlineMember
photo of error
1FBF3C67-E319-48B8-BCC6-85E04C5E519D..jpeg (94 KB, 365 downloads) 3 years old
dkuchay
offlineMember
also have used control box to change language to uft-8 by double clicking on it but after writefs and rebooting the file is not taking. its in default form.
This and syslinux conf files are giving problems. Im on a tablet. No keyboard attached and none available on slim login screen. Autologin is essential. Each time i look at xorg.conf there is a kernel boot line that does not match what i defined in /home/boot/syslinux/syslinux.conf
Slim works and I have writtenfs after issuing it as root many times over. What do i need to doto enable the boot line that i want to use?
There are things about slitax v3 that fight the user on lang and env as well as syslinux. What is overwriting my /etc/locale.conf?
Would i be better to hard code utf8 in /etc/profile? If i have to use iso8859 it will look like an ascii virus infected all ncurses applications. I notice when i call bash that it complains about not being able to set LC_ALL. across more than 1 slitaz version. Do you have a working configuration for an english speaking user in america non iso8859?
dkuchay
offlineMember
Finally figured out that this is a bug report.
I installed fedora 10 in vm and installed x-fonts-75 and 100 dpi. Manually copied out the fonts and got them copied in to Slitaz. fc-cache -v -f and fc-list and they are there, yay. Well it still didn't work.
Then I got cook setup on a wok and went to cook xvkbd. Went good up too the point of having listed deps in the receipt that are not in the repo.
I tried xvkbd-compact and it segfauled. This is from the repo. Its broken. I think it was built without the dev or the maintainer didn't comment out the imake file in the right way. Can someone rebuild this package without Xorg-libXaw3d? You don't offer it in the repo but the developer goes over how to comment out a few lines to remove the build dependency.
dkuchay
offlineMember
this distro keeps me busy,
I see on careful examination of /var/log/Xorg.0.log that my font directories do not have valid directory structure. It is suggested in brackets to run mkfontscale on /usr/share/fonts/X11/utils/*
Haha. Not in packages until newest cooking but I see version 1.0.7 which is like from 2012 so I use it. Installed and although the above suggested * wildcard failed I went in to each /usr/share/font/X11 - directory and ran it. Saving with writefs gzip now but I am not 100% this is a bug but I know I am not the only one. ron85 8 years ago posted the same on this forum only his trick is not working for me out of the box. His post was titled xvkbd broke. I also copied in 2 each 75dpi and 100dpi fonts and how have 4 font directories in /use/share/fonts/X11. I ran mkfontdir in each. Before anyone asks, yes, I do have mkfontscale also installed (on v3) and yes both utils run without errors. I uncommented the directories in my xorg.conf file and ran fc-cache -f -v .... waited for it to finish and ran fc-list to see my new fonts in all 4 folders in the font db.
So I am not sure that xvkbd was built incorrectly. I installed strace on this image so that I can trace better what is not happening correctly.
I will remove the new packages I borrowed from v5 once I see that xvkbd works, if it does. These do not belong on v3 and I feel they will cause problems in future times.
dkuchay
offlineMember
Okay,
This is finally fixed!
If anyone behind me cant get xvkbd to work on slitaz v3 here is the workaround.
edit /etc/X11/xorg.conf file to include (within font section)
add:
FontPath “/usr/share/fonts/X11/util”
FontPath “/usr/share/fonts/X11/misc”
Not sure if its needed or not but I also downloaded fedora 10 and installed it to a vm and once set up I installed iso-8859 fonts for my region. Inserted usb stick and copied out the /usr/share/fonts/X11/75dpi
and the /usr/share/fonts/X11/100dpi
folders out to usb stick.
In Slitaz I inserted usb and on command line:
mount /dev/sda1 /mnt
Here I only copied in two fonts from courier, both in 100dpi and 75dpi folders to /usr/share/fonts/X11/75dpi or 100pi respectively.
I then ejected usb stick and went to normal desktop computer and went to slitaz package search page. This was because by looking at xorg.log file I saw that font directories were not valid and it was suggested to run mkfontdir in the directories. Only slitaz did not include these until v5-cooking.
So in package search on slitaz site download both xorg-mkfontdir as well as xorg-mkfontscale from v5 repo. Put on usb and get it mounted back in target hardware. Install with tazpkg and go in to each directory for fons
/usr/share/fonts/X11/75dpi
/usr/share/fonts/X11/100dpi
/usr/share/fonts/X11/util
/usr/share/fonts/X11/misc
in each of these directories run mkfontdir using cd to change between and running command in each. Double check xorg.conf file to make sure these are active and not commented out.
To include fonts in font db we need some prep:
fc-cache -f -v
watch it finish and double check with:
fc-list
and you should see new fonts in the total counts for each category.
In my case I am installed as live usb to internal HDD so I run
tazusb writefs gzip /dev/hda1
and after rebooting xvkbd works!!
dkuchay
offlineMember
Image of virtual keyboard showing
A6797169-D446-4768-B7B9-9BE9DF317FAA..jpeg (84.2 KB, 368 downloads) 3 years old You must log in to post.
