(old)Puppy Linux Discussion Forum

I have stumble across a strange problem with textmaker in Precise 5.4.x.

The German spell checker rejects all words all words containing one of the German special characters (umlaut ä, ö, ü, etc. and ß), but otherwise seems to operate correctly, even underlining old spellings like "daß" in blue.

This does not occur with all Puppies.

A fuller description of the problem is to be found in the appropriate thread:

http://murga-linux.com/puppy/viewtopic. ... 4&start=55

new background .

@ Barry

It is not my habit, I do not ask others to do the job for me, but since I can not do it alone (and I'm not the only one) ...

I think I begin to be familiar with Puppy, but I'm not good with Woof.
I tried several times to create an iso file (Precise base), but I still get the same result: the boot liveCD gives me error messages.
I tried to get a Woof iso really light (at the main sfs). For this, I wanted to create a zdrv.sfs

My request for the next version of Puppy Precise, would it be possible to offer users/contributors a version with a file zdrv.sfs ? So that we can test its operation.

Sincerely,

Openbox+Extras 1.1 now available with two panel options and full gettext support

Testers and translators needed:

http://murga-linux.com/puppy/viewtopic.php?t=82800

Wrong thread. Sorry.

GSM modem ZTE WCDMA Technologies MSM MF110/MF627/MF636 problem
in precise 5.4.3 and slacko 5.4 (kernel 3.2.33 )I have tested modem huawei E173 (it worked out of the box ) but encountered modem address detect problem
for modem ZTE MF627. If the E173 modem creates only one /dev/ttyUSB0 serial modem and it is correctly discovered by PGRS MODEM SETUP, the ZTE MF627 modem creates 3 devices
/dev/ttyUSB0 , /dev/ttyUSB1, /dev/ttyUSB2 ( and only the first one is detected and the wrong one by the PGRS MODEM SETUP). in my case the good device was /dev/ttyUSB2.
If I put in 'Serial Modem Device File' /dev/ttyUSB2 , it worked fine. This problem was discussed by ubuntu people too, their opinion was that the right device should be detected
frome where it points the symlink /dev/gsmmodem .... I know that modifying the PGRS MODEM script could generate new bugs but an explicative text for this ZTE modems could help many people
, or at first step only to extend "(detected devices:/dev/ttyUSB0 /dev/ttyS0 )" to include also where it points /dev/gsmmodems too.
It also looks like the gsm modem stoping script not functioning proper, i could not simply close the network (by riht click& Disconect from network won't work), in slacko was easy I could
close the terminal window which remained open by the ppp PAP script on connect.
please send this observation to the maintainer of PGRS MODEM SETUP

npierce wrote:(This bug is not limited to Precise 5.4.3, but I'm adding a link in this thread because it is in Woof, and Precise 5.4.3 is the latest Puppy built from Woof. I suspect that the bug actually lives in all Puppies that contain Pudd.)

Pudd causes screeching from internal speaker during backup: Explanation and suggested fix

Thanks, your fix plus more applied, see here:

http://bkhome.org/blog2/?viewDetailed=00104

Barry,

You're welcome.

Thanks for getting my fix and your additional Pudd improvements into Woof.

Also, thanks for updating the jwmconfig2 .pet a while back.

I guess line 189 of pupcamera should be gettexted.

rodin.s wrote:In /sbin/pup_event_frontend changed this:

Code: Select all

LANG=$OLDLANG
  yaf-splash -bg orange -placement top -close never -text "$(gettext "Saving RAM to 'pup_save' file...")" &
  LANG=C

or maybe it should be done like this:

Code: Select all

LANG=$OLDLANG yaf-splash -bg orange -placement top -close never -text "$(gettext "Saving RAM to 'pup_save' file...")"

In /etc/rc.d/rc.sysinit I manually translate lines 825 and 836:

Code: Select all

echo '<icon x="768" y="128" label="Сохранить">/usr/sbin/savesession-dvd</icon>' >> /root/Choices/ROX-Filer/PuppyPin

Thanks, changes made to pup_event_frontend_d.

For rc.sysinit, I have added the line:

s%"save"%%

In file /usr/share/sss/script_strings.

phdzaps wrote:My single thing I can report on is that xload in /usr/bin ought to be a link, since it is also in /usr/X11R7/bin. I came across this because I disable xload so precise will run on older computers faster.

Hmmm, yes. OK, fixed.

Brown Mouse wrote:FFConvert appears to be broken for me.
Unable to change the compression ratio of mp3's as in previous versions of FFC..

I think Precise 5.4.3 has FFConvert 1.3.
The latest is 1.3.1, there is also an older "stable" version.

Would you mind going here and install the latest, if no good try the older stable version:
http://www.murga-linux.com/puppy/viewtopic.php?t=54056

linuxcbon wrote:Precise Puppy 5.4.3

menu - desktop - pwallpaper :
Apply a new background image, error message "no pinboard was in use"
then right or left click on desktop, it displays alternatively old and new image

# wcpufreq
/usr/sbin/wcpufreq: line 156: cd: /lib/modules/3.2.29/kernel/arch/*/kernel/cpu/cpufreq: No such file or directory
ERROR: modinfo: could not find module Choices
ERROR: modinfo: could not find module File-Sharing
ERROR: modinfo: could not find module Startup

menu - system - Pschedule
click (star icon) about
click link to forum , it doesnt open browser.

/usr/lib and /usr/local/lib dont need to be in LD_LIBRARY_PATH ?

DISPLAY=:0 should be 0.0 instead ?

Pwallpaper works fine for me.

Yes, wcpufreq has a bug. This is TaZoc's baby, but TaZoc has had health issues, not sure of current situation.
Anyway, I fixed it, see new PET version 0.8.1:
http://murga-linux.com/puppy/viewtopic. ... 397#683397

Pschedule is zigbert's baby. There will be a later version in the next release of Precise Puppy (and all other Woof-built pups).
If the problem persisits, report in the Pschedule Forum thread.

linuxcbon wrote:Precise Puppy 5.4.3
- run pupx
set mouse acceleration to 1.0
set mouse threshold to 1
click ok
run pupx again, nothing has changed.
error message :

Code: Select all

dc: syntax error at '1.0'
xset:  unknown option /10

Works for me. Acceleration does change, and no error messages.

@Barryk,
Think you saw both of these.

1. NTFS - Per your request
2. This is a small item that may have benefit to 32bit PUPs

I have made 2 minor mods to the pdiag tool, so post it here for inclusion in woof. Thanks.
Richard

rodin.s wrote:I guess line 189 of pupcamera should be gettexted.

Thanks, fixed.

BarryK wrote:

Brown Mouse wrote:FFConvert appears to be broken for me.
Unable to change the compression ratio of mp3's as in previous versions of FFC..

I think Precise 5.4.3 has FFConvert 1.3.
The latest is 1.3.1, there is also an older "stable" version.

Would you mind going here and install the latest, if no good try the older stable version:
http://www.murga-linux.com/puppy/viewtopic.php?t=54056

I installed the latest version of FFConvert 1.3.1 and I am now able to change the compression ratio of mp3's.

Thank you

BarryK wrote:

linuxcbon wrote:Precise Puppy 5.4.3
- run pupx
set mouse acceleration to 1.0
set mouse threshold to 1
click ok
run pupx again, nothing has changed.
error message :

Code: Select all

dc: syntax error at '1.0'
xset:  unknown option /10

Works for me. Acceleration does change, and no error messages.

LC_NUMERIC, decimal comma versus decimal point?
/MHHP

MinHundHettePerro wrote:LC_NUMERIC, decimal comma versus decimal point?
/MHHP

Nice catch, MHHP. That's it!

Attached is a modified version of pupx (based on the current pupx-0.3.pet in the noarch repository) that should work.

I also made some changes to allow commas as decimal points in the keyboard delay value, and the screen-saver delay and cycle values. Note that only integers are accepted by xset, so there is no point in using a decimal point for those values, but just in case a user tries to use one, pupx rounds the value down so that xset will be passed an acceptable value and not fail. I haven't changed that -- I just changed it to allow commas to be used in addition to periods, which were already supported.

For the combo box lists for the mouse acceleration & threshold values, pupx now uses the decimal point character of the current locale. But for the other values, pupx now accepts either a period or a comma, no matter what the current locale is. That way if a user has become used to the fact that pupx always wanted a period for a decimal point, the period won't suddenly stop working. And a look at the couple of hundred locals supported by Puppy, I found no locale that used anything other than a period or a comma for a non-monetary decimal point, so there should be no surprises there.