I chose to install openal-1.13.pet to solve this however a symlink to openal-soft may be a better approach
![Confused :?](./images/smilies/icon_confused.gif)
You can always add more layers to get more colors. That is what I did with mtpaint anyhow. Any more than 256 makes it difficult to get to the colors anyhow.ttuuxxx wrote:Close but it only has 256-color drawing, not enough colours:)
ttuuxxx
Looks fine here, alone or in combination. Few lang tested (including french - pic).LazY Puppy wrote:1.) using pkeys as boot parameter and boot is failing (puppy sfs not found)
2.) using plang as boot parameter and boot is failing (puppy sfs not found)
<snip>
Booting pkeys and plang tested in combination and as single used options - failed all the way. Failed also using 'fr' (french). Other languages not tested.
The use of pkeys while booting off USB drive is causing such problems due to absence of some modules (which usually were in initrd.gz) that should be compiled into vmlinuz.LazY Puppy wrote:1.) using pkeys as boot parameter and boot is failing (puppy sfs not found)
Can't recreate - works for me (USB & CD)...LazY Puppy wrote:2.) using plang as boot parameter and boot is failing (puppy sfs not found)
PGPRS' files have been lost in action.LazY Puppy wrote:3.) can't connect to the internet using my GPRS Mobile USB-Modem (it is detected and ready for use - as the messages say; menus are updated but nothing else happens after this; no menu entries, no option to connect - works always in Lucid and Precise)
Just checked in VBox & QEmu and can not recreate this behaviour...MochiMoppel wrote:Can somebody confirm?
Code: Select all
gnumeric > /tmp/gnumeric.log 2>&1
Looks relevant, but not pleasant:SFR wrote:Just checked in VBox & QEmu and can not recreate this behaviour...
Anything relevant in the output?Code: Select all
gnumeric > /tmp/gnumeric.log 2>&1
Code: Select all
gnumeric: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Makes sense. With the new kernel setup (no modules in initrd.gz) booting from a vfat usb drive with non-english will fail since it can not read the filesystem and find the files.SFR wrote:The use of pkeys while booting off USB drive is causing such problems due to absence of some modules (which usually were in initrd.gz) that should be compiled into vmlinuz.LazY Puppy wrote:1.) using pkeys as boot parameter and boot is failing (puppy sfs not found)
http://www.murga-linux.com/puppy/viewto ... 977#789977
http://www.murga-linux.com/puppy/viewto ... 324#790324
Does it also happens while booting off USB, in your case?
relating to VFAT
Yes, I'm booting generally from a VFAT Partition. Also generally from USB. This time External 500GB USB HDD.Does it also happens while booting off USB, in your case?
Since you are playing with the initrd then it should be easy to use the tahpup kernel (3.14.20) that has the modules built in and should be OK. Is fairly easy to exchange themLazY Puppy wrote:Yes, I'm booting generally from a VFAT Partition. Also generally from USB. This time External 500GB USB HDD.
As I was running into this I did use my modified version of the initrd.gz.
Since the PGPRS Files have been lost in action may I suggest a small tweak to its GUI for next release of Slacko (5.9.4?, 6.0?).SFR wrote:PGPRS' files have been lost in action.![]()
https://github.com/puppylinux-woof-CE/w ... issues/498
Hi.LazY Puppy wrote:Hi.
While doing some work on this I have found a issue in precise 5.7.1.
The file /etc/DISTRO_SPECS in main sfs is different to the file /DISTRO_SPECS in initrd.gz. The one in initrd.gz is missing this:Code: Select all
#multiarch distros, such as Ubuntu, will have this. ex: /usr/lib/i386-linux-gnu, so DISTRO_ARCHDIR=i386-linux-gnu DISTRO_ARCHDIR='i386-linux-gnu'
The idea of CE (community edition) is not that the community suggests and one or 2 persons are materializing the suggestions, but rather that the suggestions are implemented by the community and contributed to the project in a form of a patch(set) in a pull request.LazY Puppy wrote: Since you are already changing things in WoofCE may I add another suggestion to the one posted above,
but how and who exactly is "the community"? I understand the idea of patch contribution, but I don't understand the authorization process. If 10 people come with patches, who sorts this out? Who does the quality control? And who has the final say on what's in and what's out? Sorry for my naive questions, but I'm used to a company environment with quite different decision processesmavrothal wrote:suggestions are implemented by the community
No, I have stated earlier, I can't do such!mavrothal wrote:The idea of CE (community edition) is not that the community suggests and one or 2 persons are materializing the suggestions, but rather that the suggestions are implemented by the community and contributed to the project in a form of a patch(set) in a pull request.LazY Puppy wrote: Since you are already changing things in WoofCE may I add another suggestion to the one posted above,
This way more work gets done and every one is properly credited for their contribution (in the git log)
So please, if you or anybody else wants to implement this (I know you -plural- can do it), patches are welcome
Code: Select all
# Copy the DISTRO_SPECS file to /etc (/pup_new)
cp -af /DISTRO_SPECS /pup_new/etc/
Code: Select all
sync
#killall -USR1 hotplug2 #v423
umount /proc/bus/usb
umount /sys
umount /proc
#now using cpio archive for initramfs 'initial ramdisk'...
#exec switch_root -c /dev/console /pup_new /bin/busybox init 3
exec switch_root /pup_new /sbin/init
###END###
Any one with a github account can issue a pull request.MochiMoppel wrote:but how and who exactly is "the community"? I understand the idea of patch contribution, but I don't understand the authorization process. If 10 people come with patches, who sorts this out? Who does the quality control? And who has the final say on what's in and what's out?mavrothal wrote:suggestions are implemented by the community
Maybe I don't understand git terminology, but that does not appear to answer MochiMoppel's question.mavrothal wrote:Any one with a github account can issue a pull request.MochiMoppel wrote:but how and who exactly is "the community"? I understand the idea of patch contribution, but I don't understand the authorization process. If 10 people come with patches, who sorts this out? Who does the quality control? And who has the final say on what's in and what's out?mavrothal wrote:suggestions are implemented by the community
Any of the 7 current members (pic below) of woof-CE can honor (pull in) a pull request.
How so?rcrsn51 wrote:Maybe I don't understand git terminology, but that does not appear to answer MochiMoppel's question.mavrothal wrote:Any one with a github account can issue a pull request.MochiMoppel wrote: but how and who exactly is "the community"? I understand the idea of patch contribution, but I don't understand the authorization process. If 10 people come with patches, who sorts this out? Who does the quality control? And who has the final say on what's in and what's out?
Any of the 7 current members (pic below) of woof-CE can honor (pull in) a pull request.