Puppy 4.3.1 -- bug reports and suggestions
I already did that last night
Efficient aren't I?
This thread is all read through at this point, one or two posts not on the tracker yet as I pm'd the posters to try and get clarification of bits and bobs. Lots of posts not really bugs so didn't go on. The outstanding posts that I am waiting on responses should be on by the end of the week. I will keep watching the thread and put new posts onto the tracker unless it has already been done.
Job jobbed and it's a good'un.
Efficient aren't I?
This thread is all read through at this point, one or two posts not on the tracker yet as I pm'd the posters to try and get clarification of bits and bobs. Lots of posts not really bugs so didn't go on. The outstanding posts that I am waiting on responses should be on by the end of the week. I will keep watching the thread and put new posts onto the tracker unless it has already been done.
Job jobbed and it's a good'un.
Help with 4.3.1
I made a full install of Puppy 4.3.1. Everything seems to be fine EXCEPT the program does not giveme the option to save on shutdown, nor will it load pupsave files previously saved (using boot from CD or USB). Is there anything I can do to modify this or is it a bug?
Thanks!
Thanks!
Duh -- long day on the computer
Yes, that makes a lot of sense! Thanks for letting me know. I was going nuts thinking I had missed something regarding the pupsave
The only bad part is I have a pupsave from my CD booted sessions and will lose data and whatnot now that I have converted to the full installation
But I'm just glad that things are working okay!
Best --
Lisa
The only bad part is I have a pupsave from my CD booted sessions and will lose data and whatnot now that I have converted to the full installation
But I'm just glad that things are working okay!
Best --
Lisa
I had problems with abiword. I was working with a document, cutting, pasting and changing fonts, and all at once the document displayed complete garbage. I saved it in a temp file and re-opened it, and it looked fine. Happened a few times, but now for some reason I am unable to reproduce the failure.
- Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
Re: Duh -- long day on the computer
Click on the save file. Puppy should mount it and open a window inside, so that you can grab the data you want to keep. Click it again to unmount it.Lisa Fine wrote:The only bad part is I have a pupsave from my CD booted sessions and will lose data and whatnot now that I have converted to the full installation
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
PaulBx1, Abiword has often given issues like that if you search the forum. Scrolling can bork it badly as well. I won't put it on the tracker because I believe Abiword is already being dealt with for 4.4
http://www.murga-linux.com/puppy/viewto ... 2914963dbd
Somewhere in that thread it gets a mention.
http://www.murga-linux.com/puppy/viewto ... 2914963dbd
Somewhere in that thread it gets a mention.
Two suggestions.
First one is going to make some people growl but so be it.
I have been using windows since 95 or thereabouts and only started using puppy 3 months or so ago.
One thing I so so miss is a unified print dialogue.
It doesn't matter what application you use in windows you get the same print dialogue and the same result.
Puppy: mtpaint needs to be set up with the right command before it will print and gives you no set up dialogue just starts printing. Firefox gives it's own basic dialogue, Abiword and Gnumeric need fettling before they find the cups printer. etc etc. Today I downloaded gtklp.
Oh My God.
Could that possibly be set as a unified print dialogue that each and every application calls up when the print command is issued? It has virtually all you need, is clean and straightforward and (sorry) is extremely familiar to all those windows users out there. And making it easy for new users to get results is surely A Good Thing.
Second one, that pmirrorget website downloader. That needs a big red button with STOP written on it.
I tried to download a site containing some picture repositories (not that sort of picture you smutty minded schoolboy!) and off Pmirrorget went. I had my dinner and went back to the screen, Still going. Hmmmm. 1 hour later, still going, 1.5 hours later still going Oooh, 2 hours later. Shit, how do I turn this off, where's the stop button, Shit Shit the whole internet is going to be on my compooter, There isn't room, it's going to leak out and start filling the room, then the house, then the world....Help,help. HELP.
Just a simple way of stopping it that those unfamiliar with process manager, kill etc could use. Trying to find a man page for kill while the whole interweb is being sucked into your living room is slightly stressful!
First one is going to make some people growl but so be it.
I have been using windows since 95 or thereabouts and only started using puppy 3 months or so ago.
One thing I so so miss is a unified print dialogue.
It doesn't matter what application you use in windows you get the same print dialogue and the same result.
Puppy: mtpaint needs to be set up with the right command before it will print and gives you no set up dialogue just starts printing. Firefox gives it's own basic dialogue, Abiword and Gnumeric need fettling before they find the cups printer. etc etc. Today I downloaded gtklp.
Oh My God.
Could that possibly be set as a unified print dialogue that each and every application calls up when the print command is issued? It has virtually all you need, is clean and straightforward and (sorry) is extremely familiar to all those windows users out there. And making it easy for new users to get results is surely A Good Thing.
Second one, that pmirrorget website downloader. That needs a big red button with STOP written on it.
I tried to download a site containing some picture repositories (not that sort of picture you smutty minded schoolboy!) and off Pmirrorget went. I had my dinner and went back to the screen, Still going. Hmmmm. 1 hour later, still going, 1.5 hours later still going Oooh, 2 hours later. Shit, how do I turn this off, where's the stop button, Shit Shit the whole internet is going to be on my compooter, There isn't room, it's going to leak out and start filling the room, then the house, then the world....Help,help. HELP.
Just a simple way of stopping it that those unfamiliar with process manager, kill etc could use. Trying to find a man page for kill while the whole interweb is being sucked into your living room is slightly stressful!
Windows provides the print dialog as a builtin function: PrintDlg() in COMDLG32.DLL ("Common Dialog Box Library", as MSDN calls it).diaeresis wrote:One thing I so so miss is a unified print dialogue.
It doesn't matter what application you use in windows you get the same print dialogue and the same result.
POSIX systems cannot do the same, for the simple reason of not having One True GUI Toolkit or One True Printing Subsystem.
So everyone uses whatever print functionality one can implement at a "good enough" level - either toolkit-provided if it exists (say, GTK+ didn't have it before version 2.10), or custom-built.
IOW, this is a fact of life.
mtPaint doesn't have a printing dialog of its own precisely because using gtklp as a print command makes more sense than building a poor replica of it into mtPaint.mtpaint needs to be set up with the right command before it will print and gives you no set up dialogue just starts printing. <...>
Today I downloaded gtklp.
Oh My God.
Could that possibly be set as a unified print dialogue that each and every application calls up when the print command is issued?
And that is why gtklp should be built in to puppy and mtpaint set to use it "out of the box" rather than have new users with little or no familiarity with the "Linux Way" struggle to get a decent print.
And as many other apps as possible, thereby providing "a unified print dialogue"
It's not a problem, it's a solution.
And as many other apps as possible, thereby providing "a unified print dialogue"
It's not a problem, it's a solution.
- SilverPuppy
- Posts: 143
- Joined: Fri 29 May 2009, 02:21
Well, well!
Well, those of you who've been around awhile know that I felt that Puppy 4.2 was itself one big bug, and was Puppy's "Vista" moment (and indeed, it even looked like Vista, and was slow like Vista!)........and frankly, I have been leery of everything since, and using 4.1.2 exclusively. However, I stumbled across the information about Barry coming out of retirement to oversee 4.3, and a few days ago I thought, well, if Barry made it, it's got to be good.
I hafta say, I just fired it up a few minutes ago, (4.3.1) and....I'm very pleased. It has a pleasing look out-of-the-box, but isn't encumbered by widgets and sidebars and such that, try as I might, I never could get to really go away. Also, 4.3 seems to be light, which is key for usability for my purposes, as I use it primarily to refit sub-500mhz computers for the Internet Age. I'm not very comfortable with Flash 10 yet, but perhaps it will be OK.
One thing that I like is that Pnethood works again in 4.3 (it never worked for me in 4.2) and things seem to be all wonderfulness.
I did notice one minor bug: in CPU frequency scaling, the button that should say "QUIT" actually says "OUIT".....oqps
I hafta say, I just fired it up a few minutes ago, (4.3.1) and....I'm very pleased. It has a pleasing look out-of-the-box, but isn't encumbered by widgets and sidebars and such that, try as I might, I never could get to really go away. Also, 4.3 seems to be light, which is key for usability for my purposes, as I use it primarily to refit sub-500mhz computers for the Internet Age. I'm not very comfortable with Flash 10 yet, but perhaps it will be OK.
One thing that I like is that Pnethood works again in 4.3 (it never worked for me in 4.2) and things seem to be all wonderfulness.
I did notice one minor bug: in CPU frequency scaling, the button that should say "QUIT" actually says "OUIT".....oqps
- SilverPuppy
- Posts: 143
- Joined: Fri 29 May 2009, 02:21
Improper shutdowns
That's why I wrote this. (Click here)enhu wrote:if the computer is shutdown improperly, do we still need to run the xwin again in this new release. its getting sicker everytime it happens.
Soon I'll be updating the top post to include a version I'll be making this afternoon for 4.3.1 (If you beat me to it, just insert my code into your files in the requisite places. See files for details.)
Hotkeys
Hi everybody,
can you help me with hotkeys that in 4.3.1 don't work properly? When I want to set brightness, in example, I have to exit from Xorg, losting all applications running, and press on light keys to chance. In 4.2.1, this behavior was not.
Please note: in these days, I have tried only with my Acer Extensa 5620z, but not yet on my Eeepc (already seen ASUS Eee ACPI support topic by Tempestuous for 4.3.0).
Thanks, bye.
can you help me with hotkeys that in 4.3.1 don't work properly? When I want to set brightness, in example, I have to exit from Xorg, losting all applications running, and press on light keys to chance. In 4.2.1, this behavior was not.
Please note: in these days, I have tried only with my Acer Extensa 5620z, but not yet on my Eeepc (already seen ASUS Eee ACPI support topic by Tempestuous for 4.3.0).
Thanks, bye.
[b][i][color=darkred][size=134]*.* Snow *.*[/size][/color][/i][/b] :wink:
?Partition size bug in drive icons (I think)
Bear with me
Desktop of 431 has a row of partition/drive icons at the bottom (unless you turn this off).
If I do this:
Right click on an icon
select any partition
and select the line App dir
select properties
-
it is always showing the size of 20K
I think this is suppose to be the partition size, but maybe not?
scsijon
Desktop of 431 has a row of partition/drive icons at the bottom (unless you turn this off).
If I do this:
Right click on an icon
select any partition
and select the line App dir
select properties
-
it is always showing the size of 20K
I think this is suppose to be the partition size, but maybe not?
scsijon
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
Hi,
only on my medion 600MHz PIII laptop 192MBRam!
after frugal installation using Puppy Universal Installer, got error «..not syncing: attempted to kill init»
No problem booting from live-cd.
No problem with the frugal instal of the «full» pup-431 instead.
problem is: only about 8MB of the 93MB sized pup-431.iso is copied on the ext3 partition /puppy431 folder upon frugal installation.
This happens only with pup-small-431 on my medion 600MHz PIII laptop - not on desktops.
Trying to copy the pup-431.sfs from live-cd to /puppy431 resulted in an «input/output error».
Then extracting pup-431.sfs from the iso and copying it to a USB stick, and afterwards from stick to /puppy431 worked.
Now pup-431-small boots OK.
Cheers, Charlie
only on my medion 600MHz PIII laptop 192MBRam!
after frugal installation using Puppy Universal Installer, got error «..not syncing: attempted to kill init»
No problem booting from live-cd.
No problem with the frugal instal of the «full» pup-431 instead.
problem is: only about 8MB of the 93MB sized pup-431.iso is copied on the ext3 partition /puppy431 folder upon frugal installation.
This happens only with pup-small-431 on my medion 600MHz PIII laptop - not on desktops.
Trying to copy the pup-431.sfs from live-cd to /puppy431 resulted in an «input/output error».
Then extracting pup-431.sfs from the iso and copying it to a USB stick, and afterwards from stick to /puppy431 worked.
Now pup-431-small boots OK.
Cheers, Charlie
Fix for erratic module-loading preference function
tempestuous, et al,
Reports of unreliable handling of module preferences, as given in the BootManager Preference option, probably resulted from a bug in the pup_event_backend_modprobe script, which is responsible for the loading of appropriate hardware driver modules. The attached package, pup_event_backend_modprobe_fix_to_p43x-1.pet, resolves that bug and extends the capabilities of the Preference function to (1) provide predictable control over module preferences and (2) support some special cases of module selection and substitution.
The current implementation of preferences not only can fail to make a substitution, but may load a module other than the one specified, if more than one alternative is appropriate. Specifying the name of a module as a substitute merely results in substitution with whatever module is available for the device; if there are multiple candidates available, the one loaded may not be the one named as the preference.
This new version of the script extends the preference function by (1) allowing multiple preferences for the same module (separated by a "|" and ordered first-choice-first if needed), the selection being governed by the particular modules that identify themselves as supporting a particular device, and (2) allowing dynamic activation of a set of preferences needed when certain conditions occur. The special preferences reside in /etc/rc.d/MODULESCONFIG as assignment statements setting variables named PREF...; they are not accessible through the BootManager.
One use of these extensions is for hybrid USB storage-modem devices (e.g., wireless modems), which require two drivers but only one of them normally gets loaded. All such devices may initially require module usb-storage, then need one of several possible modem drivers. If the normally-loaded driver is usb-storage instead of the others, an internally activated preference is used if usb-storage is already loaded (which it normally is), but the modem driver must be the one(s) intended for the modem (known at load time).
Another use is for supporting ALSA modems that might instead actually be Conexant modems. The Conexant (Linuxant) driver issues an error message if the modem is not a Conexant. In this case, preferences can be activated to force use of the alternate (ALSA) driver after a reboot of Puppy. The new features could support other special module-loading situations as they become known.
This package/dotpet has been tested with all three kernel versions of Puppy 4.3.1. It should be installed by anyone experiencing a problem with preferred modules not loading (e.g., atl1e instead of atl1c). Do not use this package on Puppies 4.1.x or 4.2.x; instead, use the similar, but bugfix-only package created for those Puppies and available in the Bugs/Fixes threads for 4.1.2 and 4.2.1. Use of the HSF/ALSA reselection requires installation of the new modem "fix pack" package (to be uploaded soon in this thread). This fix can be applied to any Puppy 4.3 installation and is a candidate for inclusion in 4.4CE.
Richard
Reports of unreliable handling of module preferences, as given in the BootManager Preference option, probably resulted from a bug in the pup_event_backend_modprobe script, which is responsible for the loading of appropriate hardware driver modules. The attached package, pup_event_backend_modprobe_fix_to_p43x-1.pet, resolves that bug and extends the capabilities of the Preference function to (1) provide predictable control over module preferences and (2) support some special cases of module selection and substitution.
The current implementation of preferences not only can fail to make a substitution, but may load a module other than the one specified, if more than one alternative is appropriate. Specifying the name of a module as a substitute merely results in substitution with whatever module is available for the device; if there are multiple candidates available, the one loaded may not be the one named as the preference.
This new version of the script extends the preference function by (1) allowing multiple preferences for the same module (separated by a "|" and ordered first-choice-first if needed), the selection being governed by the particular modules that identify themselves as supporting a particular device, and (2) allowing dynamic activation of a set of preferences needed when certain conditions occur. The special preferences reside in /etc/rc.d/MODULESCONFIG as assignment statements setting variables named PREF...; they are not accessible through the BootManager.
One use of these extensions is for hybrid USB storage-modem devices (e.g., wireless modems), which require two drivers but only one of them normally gets loaded. All such devices may initially require module usb-storage, then need one of several possible modem drivers. If the normally-loaded driver is usb-storage instead of the others, an internally activated preference is used if usb-storage is already loaded (which it normally is), but the modem driver must be the one(s) intended for the modem (known at load time).
Another use is for supporting ALSA modems that might instead actually be Conexant modems. The Conexant (Linuxant) driver issues an error message if the modem is not a Conexant. In this case, preferences can be activated to force use of the alternate (ALSA) driver after a reboot of Puppy. The new features could support other special module-loading situations as they become known.
This package/dotpet has been tested with all three kernel versions of Puppy 4.3.1. It should be installed by anyone experiencing a problem with preferred modules not loading (e.g., atl1e instead of atl1c). Do not use this package on Puppies 4.1.x or 4.2.x; instead, use the similar, but bugfix-only package created for those Puppies and available in the Bugs/Fixes threads for 4.1.2 and 4.2.1. Use of the HSF/ALSA reselection requires installation of the new modem "fix pack" package (to be uploaded soon in this thread). This fix can be applied to any Puppy 4.3 installation and is a candidate for inclusion in 4.4CE.
Richard
- Attachments
-
- pup_event_backend_modprobe_fix_to_p43x-1.pet
- Corrects module-loading preference bug and extends preference capabilities.
Installable on any Puppy 4.3.x system, but NOT 4.1 or 4.2. - (4.62 KiB) Downloaded 1611 times