Lucid Puppy 5.2.8 - Updated ISO Version 005 - APR 05 2012
Hi All
First can I say how much I appreciate all of the work that is being done to update Lucid Puppy 528. It is my favorite puppy and I use it daily. It works well with my old Toshiba Satellite Pro 4200 800MHz 320MB. I have various versions of 528 and other puppies as frugal installs as well as XP (rarely used) on my hd booting with grub. I have 528.005 with two save files and I installed the set of update pets produced by rerwin in one of these for testing. These are show below. All seemed well and every thing seemed to work.
I decided I would give the new isos a try and selected lupu-5.2.8.6-2 0131028. I did a manual install. I installed the appropriate video driver and other applications that I use. I had been using Opera 11.50. I decided to update to 12.16 which is the most up to date version in quickpet. I set up Opera with my favorites etc. but I found that some of the dialogue boxes do not display properly (see attached). You get to this from opera-settings-preferences-advanced.
I thought I would go back to see if there were any problems with Opera in the updated 528.005 that I had not noticed and found there were (see attached). This is in Opera 11.5. This only happens in the savefile I updated and so I assume it is caused by something that was in the update pets and has carried forward into the isos.
I am sorry that I seem to have got the attachments in reverse order. I am not sure how to correct this.
Regards,
Ken.
First can I say how much I appreciate all of the work that is being done to update Lucid Puppy 528. It is my favorite puppy and I use it daily. It works well with my old Toshiba Satellite Pro 4200 800MHz 320MB. I have various versions of 528 and other puppies as frugal installs as well as XP (rarely used) on my hd booting with grub. I have 528.005 with two save files and I installed the set of update pets produced by rerwin in one of these for testing. These are show below. All seemed well and every thing seemed to work.
I decided I would give the new isos a try and selected lupu-5.2.8.6-2 0131028. I did a manual install. I installed the appropriate video driver and other applications that I use. I had been using Opera 11.50. I decided to update to 12.16 which is the most up to date version in quickpet. I set up Opera with my favorites etc. but I found that some of the dialogue boxes do not display properly (see attached). You get to this from opera-settings-preferences-advanced.
I thought I would go back to see if there were any problems with Opera in the updated 528.005 that I had not noticed and found there were (see attached). This is in Opera 11.5. This only happens in the savefile I updated and so I assume it is caused by something that was in the update pets and has carried forward into the isos.
I am sorry that I seem to have got the attachments in reverse order. I am not sure how to correct this.
Regards,
Ken.
- Attachments
-
- opera1150.jpg
- Opera 11.50 in updated 528.005 with partly corrupted dialog box
- (21.8 KiB) Downloaded 700 times
-
- opera1216.jpg
- Opera 12.16 with partly corrupted dialogue box
- (44.79 KiB) Downloaded 805 times
-
- updates.jpg
- Update pets installed in 528.005
- (43.37 KiB) Downloaded 701 times
keniv,
Thanks for reporting this. With the 20131028 version I introduced a check for pet conflicts with a replacement version of lupu528. I would expect it to pop up a window the first time you boot after changing the lupu_528.sfs file. Note that it is not perfect, in that many packages do not follow the usual naming conventions regarding version numbers.
I would expect the popup to list all of those packages you installed because their versions should match the ones built into 20131028. The popup should recommend that you uninstall all of those packages, in case the new version of something is better that the pet version.
One thing to note: the gtkdialog4 package is older that the gtkdialog package included in 5.2.8.6. So, regardless of whether it showed up in the popup window, that package must be uninstalled in order to make the newest version available to the "p" packages (e.g., pBurn) that need it.
Be sure you keep a copy of your pupsaves in case things do not go perfectly. This will be a good test of the process of upgrading lupu under an existing, package-enhanced pupsave environment. Please keep us informed as to how it goes.
Richard
Thanks for reporting this. With the 20131028 version I introduced a check for pet conflicts with a replacement version of lupu528. I would expect it to pop up a window the first time you boot after changing the lupu_528.sfs file. Note that it is not perfect, in that many packages do not follow the usual naming conventions regarding version numbers.
I would expect the popup to list all of those packages you installed because their versions should match the ones built into 20131028. The popup should recommend that you uninstall all of those packages, in case the new version of something is better that the pet version.
One thing to note: the gtkdialog4 package is older that the gtkdialog package included in 5.2.8.6. So, regardless of whether it showed up in the popup window, that package must be uninstalled in order to make the newest version available to the "p" packages (e.g., pBurn) that need it.
Be sure you keep a copy of your pupsaves in case things do not go perfectly. This will be a good test of the process of upgrading lupu under an existing, package-enhanced pupsave environment. Please keep us informed as to how it goes.
Richard
Hi Richard
Thanks for your reply. With 528.005 I updated an existing savefile so I can see why there could be version conflicts. However, with the lupu-5.2.8.6-2 0131028 iso I made a new savefile and then installed Opera 12.16 from quick pet. The only thing that has come from a previous version of Opera was my bookmarks which I imported via Opera rather than manually swapping the bookmarks.adr file in .opera. I also added the urlfilter.ini file to .opera. I did install other pet packages but so far have only noticed a problem with Opera. I will keep testing to see if it occurs with dialogue boxes in other applications. Could the gtkdialog package included in 5.2.8.6. be newer than Opera 12.16 expects? If this is the case could this cause my problem or are the updates back compatible. I also thought of uninstalling the pets from 528.005 one at a time, gtkdialog first. However, I am not sure if this would leave the older original version or would it have been overwritten. Is it worth trying this? It would be interesting to know if anybody else is using Opera with the new iso and whether they are having any problems. I am at a bit of a loss as to what to try with this one.
Regards,
Ken.
Thanks for your reply. With 528.005 I updated an existing savefile so I can see why there could be version conflicts. However, with the lupu-5.2.8.6-2 0131028 iso I made a new savefile and then installed Opera 12.16 from quick pet. The only thing that has come from a previous version of Opera was my bookmarks which I imported via Opera rather than manually swapping the bookmarks.adr file in .opera. I also added the urlfilter.ini file to .opera. I did install other pet packages but so far have only noticed a problem with Opera. I will keep testing to see if it occurs with dialogue boxes in other applications. Could the gtkdialog package included in 5.2.8.6. be newer than Opera 12.16 expects? If this is the case could this cause my problem or are the updates back compatible. I also thought of uninstalling the pets from 528.005 one at a time, gtkdialog first. However, I am not sure if this would leave the older original version or would it have been overwritten. Is it worth trying this? It would be interesting to know if anybody else is using Opera with the new iso and whether they are having any problems. I am at a bit of a loss as to what to try with this one.
Regards,
Ken.
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
dialog boxes
(Portions snipped)
A day or two ago, I had downloaded
lupumini-5.2.8.6-20131028.iso It's size was 167938048
I put its vmlinuz, initrd.gz, and .sfs files into a new directory in my frugal
/mnt/home/ directory
Booted it.
Made a save file, rebooted, and added opera-12.16-1860.i386.opt.sfs to be autoloaded.
I have not done any of the update files you did.
To test, I did Tools->Preferences-Advanced, and did _not_ see the dialog box problem in Tabs
However, when I did the Bookmarks, right-clicked a bookmark, and clicked Properties, I saw the problem you showed.
It doesn't happen with the old 528.005.
Regarding your thought about gtkdialog, may I just say: I'd had lots of problems with Pmusic because of that, ie it was "expecting" some version of gtkdialog that wasn't there, or ???
Zigbert knows a lot about this stuff; as does, I guess, 01micko.
I tried to check on this:keniv wrote:Thanks for your reply. With 528.005 I updated an existing savefile so I can see why there could be version conflicts. However, with the lupu-5.2.8.6-2 0131028 iso I made a new savefile and then installed Opera 12.16 from quick pet. The only thing that has come from a previous version of Opera was my bookmarks which I imported via Opera rather than manually swapping the bookmarks.adr file in .opera. I also added the urlfilter.ini file to .opera. I did install other pet packages but so far have only noticed a problem with Opera. I will keep testing to see if it occurs with dialogue boxes in other applications. Could the gtkdialog package included in 5.2.8.6. be newer than Opera 12.16 expects? If this is the case could this cause my problem or are the updates back compatible. I also thought of uninstalling the pets from 528.005 one at a time, gtkdialog first. However, I am not sure if this would leave the older original version or would it have been overwritten. Is it worth trying this? It would be interesting to know if anybody else is using Opera with the new iso and whether they are having any problems. I am at a bit of a loss as to what to try with this one.
A day or two ago, I had downloaded
lupumini-5.2.8.6-20131028.iso It's size was 167938048
I put its vmlinuz, initrd.gz, and .sfs files into a new directory in my frugal
/mnt/home/ directory
Booted it.
Made a save file, rebooted, and added opera-12.16-1860.i386.opt.sfs to be autoloaded.
I have not done any of the update files you did.
To test, I did Tools->Preferences-Advanced, and did _not_ see the dialog box problem in Tabs
However, when I did the Bookmarks, right-clicked a bookmark, and clicked Properties, I saw the problem you showed.
It doesn't happen with the old 528.005.
Regarding your thought about gtkdialog, may I just say: I'd had lots of problems with Pmusic because of that, ie it was "expecting" some version of gtkdialog that wasn't there, or ???
Zigbert knows a lot about this stuff; as does, I guess, 01micko.
Dell E6410: BusterPup, BionicPup64, Xenial, etc
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P
This is exactly the reason why I'm continuing the numbering of gtkdialog. Versions above gtkdialog 0.8.0 are renamed to gtkdialog5 and if I will enter any new issue/problem in a newer gtkdialog, I will use gtkdialog6 for its newer version. Since I'm using strictly SFS files (plus some RoxApps), I'm converting the (each) PET to SFS. Before that I'm just editing the scripts (for example of Pmusic) to change the gtkdialog calls and then including the gtkdialog binary into the new created SFS file.Regarding your thought about gtkdialog, may I just say: I'd had lots of problems with Pmusic because of that, ie it was "expecting" some version of gtkdialog that wasn't there, or ???
Zigbert knows a lot about this stuff; as does, I guess, 01micko.
I really don't care on the SFS files size to load and use a mount point for. And some of these SFS-Apps are automatically unloaded after exiting the application.
[b][url=http://lazy-puppy.weebly.com]LazY Puppy[/url][/b]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]
keniv,
Thanks for pursuing the problem. But, please, uninstall all of the pets you mentioned above. The gtkdialog version in 5.2.8.6 is the latest and is (I believe) required for pmusic and pburn and probably other utilities. When you uninstall a program, the original from the current lupu ISO (puppy layer, /initrd/pup_ro2) replaces the previously installed program. So, be sure to uninstall only when you are running with 5.2.8.6, to get its version of each restored file.
Just to be sure you have the correct versions of gtkdialog, please verify -- after you uninstall the gtkdialog4 package -- that /usr/sbin contains gtkdialog (as well as gtkdialog2 & gtkdialog3) as an executable and that gtkdialog4 is a link to gtkdialog (which is the latest version, now).
If you don't have the correct files operating, you can clean things up by going to /initrd/pup_rw/usr/sbin and deleting any gtkdialog* file you see there. That should let the released versions of those files be used.
If you still see the problem then we probably need the help of zigbert or thunor in the 'gtkdialog development' thread, to determine if gtkdialog is at fault.
BTW: I just now uploaded a replacement for the pfbpanel package (as -0.2.1) here:
http://www.murga-linux.com/puppy/viewto ... 415#733415
Thanks for pursuing the problem. But, please, uninstall all of the pets you mentioned above. The gtkdialog version in 5.2.8.6 is the latest and is (I believe) required for pmusic and pburn and probably other utilities. When you uninstall a program, the original from the current lupu ISO (puppy layer, /initrd/pup_ro2) replaces the previously installed program. So, be sure to uninstall only when you are running with 5.2.8.6, to get its version of each restored file.
Just to be sure you have the correct versions of gtkdialog, please verify -- after you uninstall the gtkdialog4 package -- that /usr/sbin contains gtkdialog (as well as gtkdialog2 & gtkdialog3) as an executable and that gtkdialog4 is a link to gtkdialog (which is the latest version, now).
Code: Select all
# ls -l /usr/sbin/gtkdialog*
-rwxr-xr-x 1 root root 237400 2013-06-08 22:27 /usr/sbin/gtkdialog
-rwxr-xr-x 1 root root 82588 2005-09-10 18:20 /usr/sbin/gtkdialog2
-rwxr-xr-x 1 root root 134332 2011-07-04 08:46 /usr/sbin/gtkdialog3
lrwxrwxrwx 1 root root 9 2013-09-29 17:28 /usr/sbin/gtkdialog4 -> gtkdialog
If you still see the problem then we probably need the help of zigbert or thunor in the 'gtkdialog development' thread, to determine if gtkdialog is at fault.
BTW: I just now uploaded a replacement for the pfbpanel package (as -0.2.1) here:
http://www.murga-linux.com/puppy/viewto ... 415#733415
Last edited by rerwin on Thu 31 Oct 2013, 21:33, edited 1 time in total.
pfbpanel-0.3.1-lucid.pet working well
Hi rerwin &All,
pfbpanel-0.3.1-lucid.pet, http://murga-linux.com/puppy/viewtopic. ... 9b4#733415 appears to be working fine in your LupuLibre.
I booted out of LupuLibre, created a Protected SaveFile, deleted the SaveFile and edited GRUB4Dos's menu.lst to boot LupuLibre pfix=ram. Booted into LupuLibre, created a new SaveFile, rebooted and installed your pet. Restarting X showed the default two launchers, “show-desktop
pfbpanel-0.3.1-lucid.pet, http://murga-linux.com/puppy/viewtopic. ... 9b4#733415 appears to be working fine in your LupuLibre.
I booted out of LupuLibre, created a Protected SaveFile, deleted the SaveFile and edited GRUB4Dos's menu.lst to boot LupuLibre pfix=ram. Booted into LupuLibre, created a new SaveFile, rebooted and installed your pet. Restarting X showed the default two launchers, “show-desktop
Hi All
Based on the post by sheldonissac where he ran Opera from an sfs I thought I would try it and see what happened. I had used opera-12.11-1661.i386.opt.sfs before and had a copy on a flash drive which I copied to my hd. After booting 5286 I loaded it "on the fly" and ran it. It started with my home page and with all my bookmarks, toolbars etc. I believe it is using the .opera from the 12.16 version I have installed from a pet. I checked opera-help-about opera to check that I was running the 12.11 version and I was (see attached). But guess what, now all the dialogue boxes display properly! Does this mean the problem is version specific?
Richard
Are you suggesting that I uninstall the pets from the 528.005 version. If this is the case then I'm not sure what you mean here.
Regards,
Ken.
Based on the post by sheldonissac where he ran Opera from an sfs I thought I would try it and see what happened. I had used opera-12.11-1661.i386.opt.sfs before and had a copy on a flash drive which I copied to my hd. After booting 5286 I loaded it "on the fly" and ran it. It started with my home page and with all my bookmarks, toolbars etc. I believe it is using the .opera from the 12.16 version I have installed from a pet. I checked opera-help-about opera to check that I was running the 12.11 version and I was (see attached). But guess what, now all the dialogue boxes display properly! Does this mean the problem is version specific?
Richard
Are you suggesting that I uninstall the pets from the 528.005 version. If this is the case then I'm not sure what you mean here.
To me this seems to suggest that I would be running 528.005 in order to uninstall the update pets but at the same time be running 5286 in some way. Sorry if I am being a bit thick here.So, be sure to uninstall only when you are running with 5.2.8.6, to get its version of each restored file.
Regards,
Ken.
- Attachments
-
- aboutopera.jpg
- Info in "About Opera" about version running
- (8.61 KiB) Downloaded 387 times
Have uninstalled all of the update pets from 528.005 and rebooted. This has not completely cleared the problem. If I right-click on the bookmarks toolbar then choose "properties" I get the corrupted bookmarks properties box shown in my earlier post. If I choose opera-settings-preferences-advance I get an uncorrupted box. Shown below is what I have in /usr/sbin. I am more concerned that Opera works in 5286 and based on my experience with opera-12.11-1661.i386.opt.sfs I do still wonder if it is version specific.
Regards,
Ken.
Regards,
Ken.
- Attachments
-
- usrsbin.jpg
- gtkdialog files left in /usr/sbin
- (5.11 KiB) Downloaded 349 times
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
re the messed-up dialog boxes
Oops.Booted it.
Made a save file, rebooted, and added opera-12.16-1860.i386.opt.sfs to be autoloaded.
I have not done any of the update files you did.
To test, I did Tools->Preferences-Advanced, and did _not_ see the dialog box problem in Tabs
However, when I did the Bookmarks, right-clicked a bookmark, and clicked Properties, I saw the problem you showed.
I just booted the 5.2.8.6 without a save file, and did the SFS-Load on-the-fly of the Opera .sfs.
The Bookmarks properties box looks fine!
I guess something in my save-file is messed up.
Sheldon
Dell E6410: BusterPup, BionicPup64, Xenial, etc
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P
Clean frugal install of Lupu3HD 5.2.8.6
Installed the Opera -12-lucid pet offered in Quickpet->Internet pets
I get the same display problems as keniv in opera-settings-preferences-advanced.
Wonder if this pet is made proper for Puppy.
Did a dependency check on Opera install and got this:
Installed the Opera -12-lucid pet offered in Quickpet->Internet pets
I get the same display problems as keniv in opera-settings-preferences-advanced.
Wonder if this pet is made proper for Puppy.
Did a dependency check on Opera install and got this:
- Attachments
-
- opera dependency check.jpg
- (32.88 KiB) Downloaded 336 times
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Installed Opera-12.16.1860-i386.pet from here:
http://distro.ibiblio.org/quirky/pet_packages-common/
No display problems using this pet of Opera 12.16
However, this one did not make an entry in the menu->Internet
Had to run it from terminal.
http://distro.ibiblio.org/quirky/pet_packages-common/
No display problems using this pet of Opera 12.16
However, this one did not make an entry in the menu->Internet
Had to run it from terminal.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Had to get in on the browser testing fun......
Latest Lucid test release...fresh frugal install. Opera from Quickpet.....not good.
Latest Lucid test release...fresh frugal install. Opera from Quickpet.....not good.
- Attachments
-
- Opera from Quickpet.jpg
- (20.59 KiB) Downloaded 324 times
Continued..... Opera downloaded directly from Opera........ looks good.
- Attachments
-
- Direct from Opera.jpg
- (39.73 KiB) Downloaded 361 times
While I've got a minute....... installed some of the usual stuff,everything appears nominal.20131028 version.
# report-video
VIDEO REPORT: Lucid , version 528
Chip description:
VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
Modules requested to be loaded: dbe glx dri
Drivers requested to be loaded: nvidia
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nvidia
Loaded modules: dbe dri dri2 extmod fb glx kbd mouse ramdac record
Actual rendering on monitor:
Resolution: 1440x900 pixels (411x263 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
5683 frames in 5.0 seconds
4472 frames in 5.0 seconds
6103 frames in 5.0 seconds
6090 frames in 5.0 seconds
6080 frames in 5.0 seconds
-Computer-
Processor : AMD Athlon(tm) XP 2400+
Memory : 1034MB (190MB used)
Operating System : Puppy Linux 0.52
User Name : root (root)
Date/Time : Thu 31 Oct 2013 11:06:12 PM CDT
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : GeForce4 MX 440 with AGP8X/AGP/SSE/3DNOW!
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : VIA8233 - VIA 8235
# free
total used free shared buffers
Mem: 1034888 637460 397428 0 57860
Swap: 1228932 0 1228932
Total: 2263820 637460 1626360
#
Looking solid.
# report-video
VIDEO REPORT: Lucid , version 528
Chip description:
VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
Modules requested to be loaded: dbe glx dri
Drivers requested to be loaded: nvidia
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nvidia
Loaded modules: dbe dri dri2 extmod fb glx kbd mouse ramdac record
Actual rendering on monitor:
Resolution: 1440x900 pixels (411x263 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
5683 frames in 5.0 seconds
4472 frames in 5.0 seconds
6103 frames in 5.0 seconds
6090 frames in 5.0 seconds
6080 frames in 5.0 seconds
-Computer-
Processor : AMD Athlon(tm) XP 2400+
Memory : 1034MB (190MB used)
Operating System : Puppy Linux 0.52
User Name : root (root)
Date/Time : Thu 31 Oct 2013 11:06:12 PM CDT
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : GeForce4 MX 440 with AGP8X/AGP/SSE/3DNOW!
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : VIA8233 - VIA 8235
# free
total used free shared buffers
Mem: 1034888 637460 397428 0 57860
Swap: 1228932 0 1228932
Total: 2263820 637460 1626360
#
Looking solid.
Hi All
After removing all the update pets in 528.005 as Richard suggested and still having problems with Opera I decided to try something else. Having found that opera-12.11-1661.i386.opt.sfs worked with 5286 without dialogue box corruption I decided to try it in 528.005. I decided to uninstall the opera pet.
I moved .opera from root to the hd as I was not sure if it would be uninstalled with the pet. I then moved it back to root. I then loaded the sfs "on the fly". Opera opened using my origiolal .opera file and so all my bookmarks etc were there. There was no dialog box corruption. I then re-installed 7 of the 8 update files (I did not include frisbee as I don't use it). Tried Opera again and found no corruption. Rebooted and tried again but still no corruption.
Quote from bigpup.
Regards,
Ken.
After removing all the update pets in 528.005 as Richard suggested and still having problems with Opera I decided to try something else. Having found that opera-12.11-1661.i386.opt.sfs worked with 5286 without dialogue box corruption I decided to try it in 528.005. I decided to uninstall the opera pet.
I moved .opera from root to the hd as I was not sure if it would be uninstalled with the pet. I then moved it back to root. I then loaded the sfs "on the fly". Opera opened using my origiolal .opera file and so all my bookmarks etc were there. There was no dialog box corruption. I then re-installed 7 of the 8 update files (I did not include frisbee as I don't use it). Tried Opera again and found no corruption. Rebooted and tried again but still no corruption.
Quote from bigpup.
Does the fact that Opera-12.16.1860-i386.pet and opera-12.11-1661.i386.opt.sfs seem to work without dialogue box corruption suggest that this is a problem with different versions of Opera?Installed Opera-12.16.1860-i386.pet from here:
http://distro.ibiblio.org/quirky/pet_packages-common/
No display problems using this pet of Opera 12.16
Regards,
Ken.
Different versions of Opera could be the reason, I found postings about the same issue in the Opera forum.Does the fact that Opera-12.16.1860-i386.pet and opera-12.11-1661.i386.opt.sfs seem to work without dialogue box corruption suggest that this is a problem with different versions of Opera?
It could also be caused by the person who made the Opera Pet package, missing something that Opera needed. That was why I tried using an Opera pet package, from a different location, made by a different person.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Ken,keniv wrote:Richard
Are you suggesting that I uninstall the pets from the 528.005 version. If this is the case then I'm not sure what you mean here.To me this seems to suggest that I would be running 528.005 in order to uninstall the update pets but at the same time be running 5286 in some way.So, be sure to uninstall only when you are running with 5.2.8.6, to get its version of each restored file.
As I said, this is what happens when you uninstall a pet. Admittedly, it may be counter-intuitive:
If you are running with "005", then its version of the files will replace the ones from your pet package installs. That just puts you back to the way it was under "005". But you are trying to get things to work under "5.2.8.6", so need its version of the files to replace the pet-installed versions.I wrote:When you uninstall a program, the original from the current lupu ISO (puppy layer, /initrd/pup_ro2) replaces the previously installed program
The gtkdialog files you posted show that you are not running with the 5.2.8.6 version of gtkdialog. The current version is a file named gtkdialog without any number; gtkdialog4 should be a link to that new file.
Please try again with a copy of your original pupsave that has the packages installed and only the 5.2.8.6 puppy CD or frugal install. Leave the "005" completely out of this exercise. Once you have uninstalled your gtkdialog package(s), please check the gtkdialog* files as you did. For good measure, you might get the output of the command:
ls -l /usr/sbin/gtkdialog*
('-l' is hyphen-ell; you can insert the option '--color=never' to avoid colored file names in console output.)
R