(old)Puppy Linux Discussion Forum

One thing I did was change Homebanks icons and save a lot of space.
ttuuxxx

Ttuxxx, thank you for the offer, but don't spend too much time on it.

I don't remember the issue in 4.1.2. I googled but didn't find back.

I think, when I tried and failed miserably to compile libofx, I got the code from here
I remember I had to go from compile session to compile session, as dependencies were reported missing at each run, until finally I had a libofx, but it didn't work with Homebank then.

Looking forward to see work on dpup. I tried the 014 one, but it didn't detect my e-sata connected external HDD. Probably a kernel issue.
upup 015 however detects that HDD, but the kernel version is higher.

I suppose you will give news on dpup in the woof 3 thread?

Ok Beem you owe me one for this
2 packages one is the main application and one is all the locales, please tell me how it works, So I know if I should release it in the Software section.
Oh by the way I think it will be a option because its larger, 1MB compressed as a pet.larger. Maybe a repo item ? The locales are the size of the package in 4.2
ttuuxxx

Béèm wrote:I suppose you will give news on dpup in the woof 3 thread?

Naaa I think I will be making my own Dpup thread because I'm going to be doing it differently.
ttuuxxx

Well Beem does it work? Or are you just taking the goods and running
lol
ttuuxxx

vanchutr wrote:Is this crazy?
In Puppy 4.2RC4: I can use SCIM
In Puppy 4.2: SCIM is disable.
Anyone test this? Please give some instructions/comments? Thanks

But,it work on urxvt.
It is not work on GTK APs.
I do not know reason.

ttuuxxx,

Thanks for compiling the full version of Homebank, I have wanted to use it also, however, only if it can import my data.

Sadly, it doesn't work. Running it in a terminal returns "/usr/lib/libstdc++.so.6 version 'GLIBCXX_3.4.9' not found".

Jim

Jim1911 wrote:ttuuxxx,

Thanks for compiling the full version of Homebank, I have wanted to use it also, however, only if it can import my data.

Sadly, it doesn't work. Running it in a terminal returns "/usr/lib/libstdc++.so.6 version 'GLIBCXX_3.4.9' not found".

Jim

What version of puppy are you using?
can you please post a file that contains ofx, just a mockup so I can test it, you might have to package it up as tar.gz
thanks
ttuuxxx

Jim1911 wrote:ttuuxxx,

Thanks for compiling the full version of Homebank, I have wanted to use it also, however, only if it can import my data.

Sadly, it doesn't work. Running it in a terminal returns "/usr/lib/libstdc++.so.6 version 'GLIBCXX_3.4.9' not found".

Jim

Can you also tell which part of homebank is giving you that error. It took a few packages to get it going, some wouldn't compile right so I substituted.
Then I compiled Homebank on 4.2 and that worked, its just a couple of dependencies that I had to use from other sources.
ttuuxxx

panzerpuppy wrote:Puppy needs a quick service release (4.2.1).DeepThought 4.2 feels a bit rushed.

Feelings can be misleading, panzerpuppy. Ask any pilot who has to fly using instruments only! That's not the same as flying "blind", BTW.

panzerpuppy wrote:Bugs:
--------

- pnethood is broken, needs a fix

See Puppy 4.2 Official Patches & Updates thread. I find releasing patches and updates where necessary emminently preferable to uploading 6 x new iso's to our mirrors and expecting everyone to download the whole thing again for a minor patch. JMHO.

panzerpuppy wrote:- Blinky and freememapplet are broken.
The patch doesn't help (see screenshots)
Freememapplet fails to show up in the tray.

See Official Patches & Updates thread. Patch posted there has been tested and works

panzerpuppy wrote:- When taking a screenshot with MtPaint,the process isn't terminated after closing the MtPaint window.
You'll have to end it manually with Pprocess.

Not a Puppy 4.2 issue. Please report in the mtPaint development thread where developer Dmitry (wjaguar) will see it and respond.

panzerpuppy wrote:- RemaX is still buggy and consumes a lot of memory

See Official Patches & Updates thread.

panzerpuppy wrote:- Xonclock is still movable

NOT a "Bug". We like it that way!

panzerpuppy wrote:- GPicView doesn't zoom a small picture to fit it to the window when the 'fit to window' option is enabled.The feature works only when the image is larger than the window.

Not an issue with Puppy 4.2 - please post your question in a separate thread for Gpicview. Developer Hairywill is on a sabatical, so you may have to wait or hope that one of the other devs will look into your issues. For most users the current Gpicview is perfectly functional.

panzerpuppy wrote:- ALSA: the libs are updated to 1.0.19,but the mixer and the tools are still the old ones from 1.0.16.

NOT a "Bug". I have already told you that the 1.0.16 utilities are the latest I have available. When someone gets the urge to compile a later update we'll look at it.

panzerpuppy wrote:- JWM is not updated

NOT a "Bug". Puppy has never promised to use the latest iteration of ANY package, including the window manager. Both Barry Kauler and I have elected to use what we know works for most people, whether that's the latest version or not. You are well aware - because I've told you before - that Patriot doesn't consider his JWM updates as stable enough yet for inclusion. Neither do I and they will only be included in an official release when the person bundling that release decides.

panzerpuppy wrote:- Lots of unstripped libs / executables

An oversight at best, but not a "Bug". I am examining the issue of unstripped libs and will consider at the appropriate time whether a patch or a dotpoint release is the more appropriate method for correcting that oversight.

Thank you for your report.

8-bit wrote:This is a bug using sane...[snip]...
Checking dmesg in terminal shows segmentation faults of supporting libraries when trying to save.

Install "xsane-0.994-patched2" from PETget and report whether your problem is resolved by that action, thanks.

Fix for Remaster Express bug reported on page 1 of this thread (just too late to get the fix into 4.2 Final!):

Alternative 1: Use the attached .PET which incorporates the fix, as well as a warning to users about how remastering may use a whole lot of RAM. But see alternative 2 below, which is faster and easier.

Alternative 2: Edit line 78 of the /usr/sbin/remax script yourself to fix this embarrassingly simple bug (which apparently shows up only if the PUPSTATE file doesn't set a PUP_LAYER variable, and I missed it because mine does).

Original code: Fixed code--just remove the dollar sign from the first "$PUP_LAYER" but not from the second one: Note to advocates of compiled programs as supposedly superior to interpreted ones: Bet you can't fix bugs in a few seconds like that (EDIT: and have users fix them too--even if the users can't write code)!

pa_mcclamrock wrote:Alternative 2: Edit line 78 of the /usr/sbin/remax script yourself to fix this embarrassingly simple bug (which apparently shows up only if the PUPSTATE file doesn't set a PUP_LAYER variable, and I missed it because mine does).

No need to be embarrassed by this one, pa. My super tight release schedule didn't really give you enough pre-release testing time, or I'm sure that small glitch would have been caught and fixed much earlier.

I have also included the updated version in the Official Patches & Updates thread, so it's getting plenty of notification for interested users.

Blame the Big Guy - I've got broad shoulders (and everything else, or so I'm told!)

WhoDo wrote:No need to be embarrassed by this one, pa. My super tight release schedule didn't really give you enough pre-release testing time [ . . . ]

Um, well, now that you mention it . . . maybe next time there could be more prominent announcements of deadlines.

I have also included the updated version in the Official Patches & Updates thread, so it's getting plenty of notification for interested users.

Thanks--but I'll still watch the Beginners' Help forum for new users who notice the bug and not the fix! Who knows, maybe some of them who edit line 78 will notice--as I did back in about 2000 or 2001--that it's really easy to make changes that work in interpreted scripts, and they'll be inspired (as I was) to learn how to write code!

pa_mcclamrock wrote:Um, well, now that you mention it . . . maybe next time there could be more prominent announcements of deadlines.

Oh, I don't regret the way things went for this release. I was just making sure you didn't get the blame for something that was a direct consequence of my deliberate decision. "There are more things in Heaven and Earth, Horatio ....", and in fact I'm am still being "pressured", however quietly and gently, to get things tidied up quickly so we (the dev team) can move on to the next release!

We all have crosses to bear, but I'm just trying to ensure that you don't get crucified on the one that I built for you, ok?

Whodo

I made the bcm43xx workaround as a pet, so that you can post it in the Official Patch Thread...since it's official I don't feel to post there..better you do it Whodo..

Instruction & Explaination:

This patch is to avoid bcm43xx to be loaded in network wizard.
Install this pet and reboot (if first boot, please create pup_save). On the next reboot, then go to network wizard, bcm43xx won't be loaded

Thanks

trio wrote:I made the bcm43xx workaround as apet, so that you can post it in the Official Patch Thread...since it's official I don't feel to post there..better you do it Whodo..

Instruction & Explaination:

This patch is to avoid bcm43xx to be loaded in network wizard.
Install this pet and reboot (if first boot, please create pup_save). On the nex reboot, then go to network wizard, bcm43xx won't be loaded

Thanks, trio. If I keep control of what goes up in that thread then there is less likelihood of conflicting things being posted. Thanks for your consideration and for making the pet update for the bcm43xxx workaround. It is much appreciated.

trio wrote:Whodo

I made the bcm43xx workaround as a pet, so that you can post it in the Official Patch Thread...since it's official I don't feel to post there..better you do it Whodo..

Instruction & Explaination:

This patch is to avoid bcm43xx to be loaded in network wizard.
Install this pet and reboot (if first boot, please create pup_save). On the next reboot, then go to network wizard, bcm43xx won't be loaded

Thanks

Should that be a default patch? Will it interfere with other users network configs, meaning does it remove or reduce the range of network devices, Do people need bcm43xx??? I don't know, networking works fine for me I'm just wondering if this will stop some other people from getting online?
ttuuxxx

ttuuxxx wrote:

trio wrote:Whodo

I made the bcm43xx workaround as a pet, so that you can post it in the Official Patch Thread...since it's official I don't feel to post there..better you do it Whodo..

Instruction & Explaination:

This patch is to avoid bcm43xx to be loaded in network wizard.
Install this pet and reboot (if first boot, please create pup_save). On the next reboot, then go to network wizard, bcm43xx won't be loaded

Thanks

Should that be a default patch? Will it interfere with other users network configs, meaning does it remove or reduce the range of network devices, Do people need bcm43xx??? I don't know, networking works fine for me I'm just wondering if this will stop some other people from getting online?
ttuuxxx

actually, if you open up initrd.gz then you'll see that Barry stated it's a bad hack in 4.1.2, dunno why he did that..until now, the problem is only with broadcom wireless users, people without that problem shouldn't install that patch (as I do not know what it will do, if it affects other things). I have no problem after the patch though (in my broadcom installed laptop) and on another laptop (intel wireless) I DON'T install the patch. Anywya, broadcom users who already installed the patch, are welcome to give comments. Or maybe non broadcom users who installed the patch also can give comments if there's a conflict or is it just working fine?

Thanks

trio wrote:
actually, if you open up initrd.gz then you'll see that Barry stated it's a bad hack in 4.1.2, dunno why he did that..until now, the problem is only with broadcom wireless users, people without that problem shouldn't install that patch (as I do not know what it will do, if it affects other things). I have no problem after the patch though (in my broadcom installed laptop) and on another laptop (intel wireless) I DON'T install the patch. Anywya, broadcom users who already installed the patch, are welcome to give comments. Or maybe non broadcom users who installed the patch also can give comments if there's a conflict or is it just working fine?

Thanks

I was thinking maybe have a folder in root called Modem-Fixes and a small text message saying "Iif your broadcom modem is working, please don't use the patch, but if it isn't feel free to try the patch."
and have the patch in the folder, that would take a whole 3-4kb lol whats that 1 icon
ttuuxxx