Quirky Pyro64 version 0.6 (alpha) -- and Pyro32 0.5

[foxpup]

Another little thing:
Show Location does not do anything in pFind.

That one came up before, and I tested it and it worked.

you need to highlight the file first.

I knew that . It gives a warning that nothing is selected. But it gave nothing to me.
I installed 0.6 and it works alright. Bizar?
The wifi persistence problem is still there in pyro-0.6, for me. Am I the only one?
Could the output in console, running rc.network, be of any help to solve it? There is an error "ifconfig: SIOCSIFFLAGS: Unknown error 132" which looks like a clue. When I google this error the solution is often something with rfkill.

[don570]

Another little thing:
Show Location does not do anything in pFind.

Works for me. Use pfind to find the 'defaultfilemanager' file.

_____________________________________________

[don570]

Good . Version 0.6
Mypaint 1.3 now works properly with external apps

However gimp hasn't been upgraded to
gimp-2.8.22

_________________________________________________

[don570]

Installed on 32 gb USB stick using 4install-quirky-to-drive-mbr.gz script
- IBM Thinkcentre desktop

I wasn't able to set up a Samba server with Pyro64 0.6
I am using Simple Samba Management. It appears to go smoothly.
The other computer can see the share but doesn't connect,
apparently because there isn't a user defined??

However I defined root (password = woofwoof)

Another interesting thing I discovered...
When I tried to define another samba user

Code: Select all

smbpasswd -a don570

It wouldn't accept this.

Code: Select all

# smbpasswd -a don570
New SMB password:
Retype new SMB password:
Failed to add entry for user don570.

__________________________

[scsijon]

If you haven't already found it, cups seems to be in "task-core-lsb-command-add", together with localedef, fontconfig-utils, mailx, msmtp, chkconfig, xdg-utils, foomatic-filters, and ghostscript. Makes me wonder about them also?

That's if i'm not having you "suck eggs".

EDIT1: Ok I apologise, looks like I really need to re-read OE and get my knowledgebase updated on this one.
from BLFS:
The CUPS Filters package contains backends, filters and other software that was once part of the core CUPS distribution but is no longer maintained by Apple Inc.
BLFS uses cups-filters 1.17.2, is it worth trying that rather than going backward.
I wonder if OE is using pdf-printing still https://wiki.linuxfoundation.org/openpr ... job_format.

[BarryK]

Good . Version 0.6
Mypaint 1.3 now works properly with external apps

However gimp hasn't been upgraded to
gimp-2.8.22

_________________________________________________

Yeah, I am using the gimp in OE.

[BarryK]

I got printing working in Pyro64 0.6:

http://bkhome.org/news/201711/no-cups-s ... edded.html

That was by manually compiling packages in Pyro64. Now the challenge is to apply the fixes in OE.

Not so good that I had to rollback cups-filters, fixing it, but I don't know why. But then, have had mysterious things like that before, with cups.

[don570]

I was able to get pclock to work in pyro64 v0.6
by installing pclock 0.7.2

Then changing one line to recognize the music player from pmusic to 'defaultmediaplayer' (or xinewrapper)

Code: Select all

	pschedule -s -e "defaultmediaplayer '$ALARM'" "music Alarm" &

Code: Select all

pschedule -s -e "xinewrapper '$ALARM'" "music Alarm" &

There is a splash screen which I can't get rid of but that's okay with me.

__________________________

[Sage]

Note, I am now doing a complete x86 32-bit (i686) recompile in OE.

Yippee^2.

[don570]

The open file window...

has 'floppy' and another item 'pts'

The icon is missing beside floppy.

My computer does have a floppy drive but I never use it.

Could it be a line in fstab file???
Stretch linux has same problem
http://murga-linux.com/puppy/viewtopic. ... 155#975155
______________________________________________

[don570]

Here is quick solution to the cluttered open file window....

I commented out all the lines in fstab file and the puppy still booted fine

Code: Select all

#none          /proc        proc     defaults               0 0
#none          /sys         sysfs    defaults               0 0
#none          /dev/pts     devpts   gid=2,mode=620         0 0
#/dev/fd0      /mnt/floppy  auto     noauto,rw              0 0

This cleaned up my file open window.

However there was a complaint while booting that 'pts' wasn't defined.
____________________________________________________

[don570]

Blender 2.7.8 worked.
That means that there is no problem with openGL 2.1

https://builder.blender.org/download/
_______________________________________________

[don570]

gimp app can use gmic plug-in v1.7.9
-includes fftw3

Available:
4mb
https://drive.google.com/open?id=1-TGcu ... bk6h_A6rgp
_____________________________________

[don570]

A new version is available at git
mtpaint version 3.49.13

@wjaguar wjaguar Version 3.49.13

Updated & fixed packaging for Windows
Fixed compilation for GTK+1
Added workaround for KDE's "dialogparent" effect
Other assorted fixes

______________________________

[davids45]

G'day,

Here is quick solution to the cluttered open file window....

I commented out all the lines in fstab file and the puppy still booted fine

Code:
#none /proc proc defaults 0 0
#none /sys sysfs defaults 0 0
#none /dev/pts devpts gid=2,mode=620 0 0
#/dev/fd0 /mnt/floppy auto noauto,rw 0 0

In my Frugal Pup of Pyro32, I can confirm that by clearing the contents of the fstab file in /etc, I have a cleaner 'Places' panel when wanting to 'Open file' in, say, gimp.

This default listing of unwanted 'Places' (to look for files to open as a user) seems to be a problem (well, a minor iritation) only in recent StretchPups as well as Pyro, but not Ubuntu-Pups such as Xenial and Artful, nor in Slacko.

Re Pyro32-0.5:
I could not get a Pyro32 Full install to boot and run (blinking cursor on black screen) after installing from this Frugal or a Live-DVD (both of which do run). With just under 2GB RAM, maybe that's not enough for a Full? I tried an 8GB ext4 partition which ended up with well under 2GB of installed files for the Full (last screenshot).
As the Frugal Pyro32 seems not to utilise sfs as in normal Pups, the Frugal Pyro is at a big disadvantage when all my packages/applications are in sfs formats.

Waiting with interest to try Pyro32-0.6.

David S.

[BarryK]

Re Pyro32-0.5:
I could not get a Pyro32 Full install to boot and run (blinking cursor on black screen) after installing from this Frugal or a Live-DVD (both of which do run). With just under 2GB RAM, maybe that's not enough for a Full? I tried an 8GB ext4 partition which ended up with well under 2GB of installed files for the Full (last screenshot).
As the Frugal Pyro32 seems not to utilise sfs as in normal Pups, the Frugal Pyro is at a big disadvantage when all my packages/applications are in sfs formats.

Waiting with interest to try Pyro32-0.6.

David S.

Pyro32 0.6.1 will be uploaded soon.

For SFSs, Easy OS is the way to go. I will do a new build of Easy soon.

Yeah, that blinking cursor on blank screen is odd, I have sometimes got that too.
JWM must be running. I have asked Joe, the author of jwm, for any thoughts on that.

I am using jwm 2.3.7, which has at least two bugs, that I have informed Joe about.

I wonder if get that blank screen if I roll jwm back to rev 976 (the version I used for years, until this year).

[technosaurus]

Yeah, that blinking cursor on blank screen is odd, I have sometimes got that too.
JWM must be running. I have asked Joe, the author of jwm, for any thoughts on that.

I am using jwm 2.3.7, which has at least two bugs, that I have informed Joe about.

I wonder if get that blank screen if I roll jwm back to rev 976 (the version I used for years, until this year).

I didn't see an issue on GitHub. Joe has been really good about handling issues posted there. His source code is relatively easy to follow and since it is all in git, its easy to bisectinate to the last known working version to see what code may be causing the issue. BTW there are some differences in XML in recent versions​ that can be fixed by applying the xslt included in the source. I log on to GitHub daily and jwm is on my notifications, so if you post the issue there, I will have a look.

[BarryK]

Yeah, that blinking cursor on blank screen is odd, I have sometimes got that too.
JWM must be running. I have asked Joe, the author of jwm, for any thoughts on that.

I am using jwm 2.3.7, which has at least two bugs, that I have informed Joe about.

I wonder if get that blank screen if I roll jwm back to rev 976 (the version I used for years, until this year).

I didn't see an issue on GitHub. Joe has been really good about handling issues posted there. His source code is relatively easy to follow and since it is all in git, its easy to bisectinate to the last known working version to see what code may be causing the issue. BTW there are some differences in XML in recent versions​ that can be fixed by applying the xslt included in the source. I log on to GitHub daily and jwm is on my notifications, so if you post the issue there, I will have a look.

I contacted him by email. Yeah, I should have raised them as issues on github.

[BarryK]

Pyro32 0.6.1 is out:

http://bkhome.org/news/201712/quirky-py ... eased.html

Printing and PPLOG should now be working.

[foxpup]

The wifi persistence problem is still there in pyro-0.6, for me. Am I the only one?
Could the output in console, running rc.network, be of any help to solve it? There is an error "ifconfig: SIOCSIFFLAGS: Unknown error 132" which looks like a clue. When I google this error the solution is often something with rfkill.

The problem in pyro seems worse then in xenial or slacko: clicking the saved wlan0 in SNS does work in the latter, but not in pyro. Same for running rc.connect. It seems worse, but maybe it isn't. charlie6 reports for xenial7.5 32bit that his wlan0 keeps blocked.

Frisbee also does not work for me in pyro, it doesn't even connect at all. Frisbee does work in xenial7.5, and persists over reboots.