multiarch support
watchdog timeout
first blog entry for elilong
first blog entry for elilong
make sure you run eliloconfig which copies over whatever /boot/vmlinuz link points to to the efi boot partition, and also copies over whatever /boot/initrd.gz points to to the efi boot partition. If you have manually compiled a kernel and it is not pointed to via those simlinks, you need to manually copy your kernel and initrd to /boot/efi/EFI/Slackware and update your elilo.conf file appropriately. elilo uses the uefi boot partition fat32 reading functions to read the files, so cannot handle them...
not sure why its posted in elilo discussion, you've configured ignite-ux to configure elilo to boot from a location that is not visible at boot time via tftp. For lilo over tftp the path of images and initrd should be relative to the location of the elilo-ia64.efi file on the tftp directory. in otherwords, update the elilo-ia64.conf file and make image =isolinux/vmlinuz and similarly for initrd=isolinux/initrd.img
i tested with single and double connection to qemu vm, both ok, and also two connections, one to qemu client, and one to windows client, again both ok .
i tested with single and double connection ti qemu vm, both ok, and also two connections, one to qemu client, and one to windows client, again both ok .
that seems to fix the problem. no more flickering on remoting to qemu vm from windows client. thanks.
(same problem with a qemu 7.2.0 vm)
flickering connecting to qemu vm
many thanks. regards, Tim On 04/07/2022 03:55, William Kendrick wrote: status: open --> closed Comment: Amusingly, Tux Paint itself (via its call to |png_set_IHDR()| in |do_png_save()|) saves PNGs as interlaced, so when they are loaded, the "Interlace handling..." is echoed to STDERR. Not going to change that (for now), but will close this since all of the other STDERR-spamming culprit files that ship /with/ Tux Paint have been adjusted. (See https://sourceforge.net/p/tuxpaint/tuxpaint/ci/11ca37c8b494573e7ad68a4a6fe467b8c3f7ab64/)...
woops. correction. in the above report please swap sdl1 and sdl2
warnings when running tuxpaint from a graphical terminal.
tightvnc client remoteviewercore unknown exception connecting to linux host
you won't see the downloads from people using slackbuilds, as they download directly from the mirrors, rather than going through the sourceforge main web site, so I don't think they get included in the statistics.
many thanks. slackware still uses them (untill slackware 15 comes out).
the 3.03 and 3.04 source releases on sourceforge appear to have disappeared. Any chance of restoring them?. Some distro's ship a gtk+3 version less than 3.22/3.20 which is needed for newer versions of klavaro since using GdkDrawingContext was added in more recent versions of the code.
mention slackware options
they should both be up now. I have put up the md5sums as well, just in case.
i am uploading them to http://winsender.sourceforge.net/ my little sourceforge project...
slackware packages
Thanks the for comments. I've fixed the link, and corrected the filename and removed...
I have created an sdl2 devpack with offline documentation. it can be downloaded from...