Quirky Xerus 8.6 (Aug. 16), Beaver 8.7.1 (Sept. 21), 2018

[Rodney Byne]

Hi ETP,

Indeed, I am not sorry I asked and with my eager curiosity
it is the only way I can learn new things.
Thanks for all the explanations, incl wbar.

Without doubt that is a most impressive array of partitions
controlling your systems. It's a wonder you can keep
track of all that's going on.

For simplicity, I keep my distros on separate usb flash drives with small
identified tie-on tag labels, written in pencil so they can be re-used
when a new distro is being tested.
All stored in an ex-electric shaver zip wallet for convenience.
A very different arrangement from yours & antiquated but effective
to me.

My laptop still has Win7 installed but with the ethernet data path
to it disabled internally for virus intrusion safety. (sda1 & 2)

The web is surfed from its boot menu (as sdb), selecting whichever
flash drive takes my fancy. There is a wide choice available to me.

Best regards.

[ottod]

Hi lp-dolittle,
Thank you for reaching out to me. If there is more people having keyboard issues we together can find the solution. I love Quirky but this bug is not letting me use the latest 8.3. My graphics chipset is Intel HD 520 from i5-6200u CPU.

[lp-dolittle]

Hi ottod,

there are several indications that some computer's Intel graphics chipset is 'co-responsible' for the keyboard-layout issue which we experience, probably together with a not yet fixed bug in the XkbConfigManager? Therefore, it's not really a surprise to read your computer's hardware specifications.

If you have the opportunity to run quirky xerus64-8.3 on a machine equipped with a different graphics chipset (e.g. Nvidia), you perhaps/hopefully may be able to configure the keyboard-layout according to your need.

Maybe, my clumsy workaround, described in a yesterday post, could work also in your situation??

Moreover, Barry is aware of the problem, and I'm sure he soon will present a solution!

kind regards

[Rodney Byne]

Hi,
I wonder if anyone using a flashing light usb stick
such as Emtec has noticed that rapid repeated
rhythmic flashing and stop gaps from boot,
can be stopped immediately by right clicking
the indicated temp icon to quit.
If these are writes to stick, don't like them.

Going back awhile to xerus 7.0.1, this effect described
never happened.

[Philh]

Doing a frugal install to a usb partition from a cd
The menu.lst hints for grub v1 says hd19,1 which should be hd0,1 on my drive

retrovol values not remembered on a frugal install
If I run
alsactl -f /etc/asound.state store
in a terminal then asound.state gets updated with the retrovol values
but running /usr/sbin/savesession doesnt seem to update the asound.state with the retrovol values so it gets saved with the old values in s.sfs
although youve added it #170723

[don570]

The most recent audacity is easy to compile
Audacity 2.1.3
I disabled ffmpeg

Available:
https://drive.google.com/file/d/0B7JZA8 ... sp=sharing

______________________________________________

[rameshiyer]

What is the default login user id and password for Qurky Xerux 8.3. How to remove auto login for Quirky Xerux 8.3 due to security reasons.

[don570]

default login user id and password for Qurky Xerux 8.3

It's the same for all of Barry's distros
User: root
Password: woofwoof

As for auto login , read ..
http://puppylinux.org/wikka/autologin
__________________________________________

Tip:

When Samba is ON it wastes time logging messages.
The logging can be stopped by making a simple change to
the smb.conf file (in /etc/Samba)

log level = 0

Log levels

The level of logging that Samba uses can be set in the smb.conf file using the global log level or debug level option; they are equivalent. The logging level is an integer that can range from 0 to 10. At level 0, no logging is done. Higher values result in more voluminous logging. For example, let's assume that we will use a Windows client to browse a directory on a Samba server. For a small amount of log information, you can use log level = 1, which instructs Samba to show only cursory information, in this case only the connection itself:

05/25/02 22:02:11 server (192.168.236.86) connect to service public as user pcguest
(uid=503,gid=100) (pid 3377)

Higher debug levels produce more detailed information. Usually, you won't need more than level 3, which is fully adequate for most Samba administrators. Levels above 3 are used by the developers and dump enormous amounts of cryptic information.

[TIW]

Hi everybody.
I own a Microsoft "Lumina 950" phone and have problems to transfer data per blue-tooth.
As it stands Lumina can "see" Quirky Xerus 8.2 and even "pairing" seems to be no problem, but ...
the connection happens for only a couple of seconds and becomes again unconnected after that.

What do you make of that ? I am only a consumer and do not understand much about that technology,
but if I can be of any help I would be happy to be of assistance.

By the way: How do I transmit and receive data, after the connection is made successfully i.e. permanently ?

Thanks for your help.

[charlie6]

Hi,
thanks Barry for this xerus8.3 !

reading this here:
http://murga-linux.com/puppy/viewtopic. ... 331#923331
I got a try to find an already compiled 64 bits Gnumeric-1.10.17 and found one here:
http://distro.ibiblio.org/fatdog/packag ... 6_64-1.txz
Using XArchve, I extracted it on / ;
and also needed to make this relative link:

Code: Select all

ln -r /lib/x86_64_linux-gnu/libpng12.so.0.54.0 /lib/x86_64_linux-gnu/libpng16.so.16

as gnumeric claims for libpng16.so.16

Afterwards had to edit/adjust /usr/share/applications/gnumeric.desktop to get the menu entry:

Code: Select all

[Desktop Entry]
Encoding=UTF-8
Name=Gnumeric
Name[fr]=Gnumeric
Exec=gnumeric
Icon=/usr/share/pixmaps/gnumeric.png
Terminal=false
Type=Application
Categories=Office;Spreadsheet;
X-GNOME-Bugzilla-Bugzilla=GNOME
X-GNOME-Bugzilla-Product=Gnumeric
X-GNOME-Bugzilla-Version=1.10.17
X-GNOME-Bugzilla-Component=General
X-GNOME-DocPath=gnumeric
MimeType=application/x-gnumeric;application/vnd.ms-excel;application/excel;application/msexcel;application/x-excel;application/x-ms-excel;application/x-msexcel;application/x-xls;application/xls;application/x-dos_ms_excel;zz-application/zz-winassoc-xls;application/vnd.openxmlformats-officedocument.spreadsheetml.sheet;application/tab-separated-values;text/csv;text/x-csv;text/spreadsheet;text/tab-separated-values;application/vnd.lotus-1-2-3;application/x-123;application/vnd.sun.xml.calc;application/vnd.sun.xml.calc.template;application/x-applix-spreadsheet;application/x-mps;application/x-oleo;application/x-planperfect;application/x-quattropro;application/x-sc;application/x-sylk;application/x-dbase;application/x-dbf;application/x-xbase;

Then do in terminal

Code: Select all

fixmenus

and restart X and its done.

Seems running well ...
Thanks for any comment / advice

Best regards
Charlie

[don570]

I had success using the newest Mypaint with my Wacom bamboo tablet.

I got the instructions from here...
http://murga-linux.com/puppy/viewtopic. ... 638#964992

I downloaded and I have it stored at google

https://drive.google.com/open?id=0B7JZA ... 2hEOUE0ZUE

Here is my review...
Menu icons show properly

As far as a background goes , there is a menu item to set background..

Layer > Set background

What I did was set my favorite background (white)
and save an ORA file to disk as my default file.

Then to open mypaint I use the terminal

Code: Select all

./MyPaint-1.3.0-git.1a513bc.glibc2.15-x86_64.AppImage  default.ora

The file opens automatically and i am ready to start.

I can use the clipboard to transfer an image to GIMP.
That I believe is a new feature!
__________________________________

[artsown]

A few issues using frugal install to hard drive:

1. Cannot get rid of original icons
2. At reboot, apparently need a delay before invoking wireless connection.
3. Package Manager needs work. While all dependencies can be found
and seen, there is sometimes no option to install them all. One must
laboriously install them one by one (unless I'm missing something).
4. Pup-Advert Blocker does not modify /etc/hosts

Otherwise, 8.3 is a winner for my purposes!

Art

[wuwei]

Don't know if this has been addressed on one of the other 46 pages in this thread but I have a strange phenomenon with Quirky Xerus 8.3:

All desktop settings disappear from one boot to another. Programs that I have installed are, however, retained. The desktop reverts to the default settings with wallpaper, icons, tray all in the default setup.

I have installed Quirky on USB following Barry's instructions on this page
http://distro.ibiblio.org/quirky/quirky ... nstall.htm
under the heading "Windows".

There is no icon "save" on the desktop.
Executing mksquashfs makes no difference.
pfind does not find s.sfs or q.sfs

So, what am I missing (never had this before with any Puppy)?

Thanks

PS: It gets increasingly more mysterious:
After several reboots the desktop now retains the wallpaper plus the icon style I have set. Drive icons and other icons always appear in the default settings.I.e. icons deleted by me and replaced by other icons revert to the default setup. A backup of /root/Choices/ROX-Filer/PuppyPin is useless.

[Leon]

All desktop settings disappear from one boot to another. Programs that I have installed are, however, retained. The desktop reverts to the default settings with wallpaper, icons, tray all in the default setup.

It was one of Quirky’s mysteries for me, too.

I noticed that desktop changes have to be manually saved

from file

/root/Choices/ROX-Filer/PuppyPin

to file

/root/Choices/ROX-Filer/PuppyPinBACKUP

I prefer on desktop are shown only drive icons.

My /root/Choices/ROX-Filer/PuppyPin file

Code: Select all

# cat PuppyPin
<?xml version="1.0"?>
<pinboard>
  <backdrop style="Stretched">/usr/share/backgrounds/mybackground.jpg</backdrop>
  <icon x="32" y="704" label="drives" args="any 0">/root/.pup_event/drive_drives</icon>
</pinboard>

My /root/Choices/ROX-Filer/PuppyPinBACKUP file with same contents as /root/Choices/ROX-Filer/PuppyPin file

Code: Select all

# cat PuppyPinBACKUP
<?xml version="1.0"?>
<pinboard>
  <backdrop style="Stretched">/usr/share/backgrounds/mybackground.jpg</backdrop>
  <icon x="32" y="704" label="drives" args="any 0">/root/.pup_event/drive_drives</icon>
</pinboard>

[wuwei]

Leon wrote:

I noticed that desktop changes have to be manually saved

from file

/root/Choices/ROX-Filer/PuppyPin

to file

/root/Choices/ROX-Filer/PuppyPinBACKUP

I tried that and it seems to work halfway.
When I arrange icons and wallpaper it does show up correctly in the file PuppyPin. Manually save that to PuppyPinBACKUP and the choice and positions of the desktop icons are retained upon a restart of X or a reboot. (There is no automatic backup, though)

BUT...the drive icons always revert back to some sort of default positions. Even a manual correction of the y-position in PuppyPin and/or PuppyPinBACKUP has no effect.

Sorry, but this is a "quirk" that needs addressing, IMHO.

[ab12]

Hi,

Has anybody else had this problem. When I boot xerus64-8.3.1 from a fresh boot it sticks on the line creating zram. However, when booted from a reboot from any other distro on the the thumb-drive, it boots flawlessly. I've tried several xerus64 installations, i.e full and frugal, but does the same thing every time.

Many thanks for any advice or solutions on the matter.

[Philh]

How did you install it.
What format is your partition you installed to.

my grub
title Quirky Xerus64 8.3 frugal in sdb1 dir xer648v3
uuid DA72-4947
kernel /xer648v3/vmlinuz rw
initrd /xer648v3/initrd.q

I dont know if you need rootwait added.
vmlinuz rootwait rw

[ab12]

Thanks for your response Philh.

Standard installation from DVD iso image
Partition format ext2

Grub supplied by Xerus during installation, cut and paste into Grub4dos, two options supplied, used both:

title Quirky Xerus64 8.3 frugal in sdb7 dir xerus64-8.3
find --set-root --ignore-floppies /xerus64-8.3/initrd.q
kernel /xerus64-8.3/vmlinuz rootwait rw
initrd /xerus64-8.3/initrd.q

title Quirky Xerus64 8.3 frugal in sdb7 dir xerus64-8.3
uuid 15187091-8ec2-4191-9d71-3d1d63a285de
kernel /xerus64-8.3/vmlinuz rw
initrd /xerus64-8.3/initrd.q

Both of these setups will boot on reboot from another puppy.

[Philh]

If you look in /boot/initrd-tree you could check the install_specs match your installation.
Maybe copy the Q_ID to your xerus64-8.3 folder though it shouldnt need it.
Have you tried a different usb port.
My flash drive is fairly slow but it boots ok.
Maybe try adding qfix=fsck to the kernel line.
But apart from that I dont know.

[Leon]

When I boot xerus64-8.3.1 from a fresh boot it sticks on the line creating zram.

Similar problem appeared when I moved Quirky Xerus frugal installation to another partition.

1. Old location

Hard drive, sda3, vfat

grub4dos menu.lst | Boot succeed

title Quirky Xerus64 8.3, sda3, qx6483
find --set-root --ignore-floppies /qx6483/initrd.q
kernel /qx6483/vmlinuz rootwait rw
initrd /qx6483/initrd.q

2. New location

Hard drive, sda5, vfat

a) grub4dos menu.lst | Boot process stops at creating zram

title Quirky Xerus64 8.3, sda5, qx6483
find --set-root --ignore-floppies /qx6483/initrd.q
kernel /qx6483/vmlinuz rootwait rw
initrd /qx6483/initrd.q

b) grub4dos menu.lst | Boot succeed

title Quirky Xerus 8.3, sda5, 0EE6-55A0, qx6483
uuid 0EE6-55A0
find --set-root --ignore-floppies /qx6483/initrd.q
kernel /qx6483/vmlinuz install_specs=UUID=0EE6-55A0:vfat:qx6483
initrd /qx6483/initrd.q

Determining boot partition’s UUID

Code: Select all

# blkid /dev/sda3
/dev/sda3: LABEL="Quirky" UUID="0EE6-55A0" TYPE="vfat"