2.12: Mozilla pupget didn't work, broke SeaMonkey
2.12: Mozilla pupget didn't work, broke SeaMonkey
Messed up here somewhere..
Tried to download & install Mozilla 1.8b1.5 with pupget & ended up losing Seamonkey? Doesn't work anymore, neither does the Mozzila 1.8b1.5 browser. Tried un & install a few times..
How do i get one or the other working again? All I get when clicking on the seamonkey icon..is a quick flash, of a screen..& then nothing
Can't seem to get Opera happening after install..doesn't show up anywhere?
Other downloads workin out ok..Firefox, Open office..
________________________
2.12 live CD with file backed up on hard drive.
Tried to download & install Mozilla 1.8b1.5 with pupget & ended up losing Seamonkey? Doesn't work anymore, neither does the Mozzila 1.8b1.5 browser. Tried un & install a few times..
How do i get one or the other working again? All I get when clicking on the seamonkey icon..is a quick flash, of a screen..& then nothing
Can't seem to get Opera happening after install..doesn't show up anywhere?
Other downloads workin out ok..Firefox, Open office..
________________________
2.12 live CD with file backed up on hard drive.
Last edited by jonyo on Sun 14 Jan 2007, 07:44, edited 4 times in total.
Punched in mozstart, in the only console I can find (..on my desktop) & top left of file [folder?] shows 'rxvt'.
So, console page starts with sh-3.00#
& when I punch in mozstart, up comes the following.
--------------------------------------------
sh-3.00# mozstart
Segmentation fault
sh-3.00#
----------------------------------
Opera..all of a sudden, shows up & is working.
So, console page starts with sh-3.00#
& when I punch in mozstart, up comes the following.
--------------------------------------------
sh-3.00# mozstart
Segmentation fault
sh-3.00#
----------------------------------
Opera..all of a sudden, shows up & is working.
Last edited by jonyo on Mon 15 Jan 2007, 01:56, edited 1 time in total.
Still workin on gettin seamonkey back (or working) & no go so far.
Tried mozstart in console again & still gettin the 'segmentation fault'.
Anyone know what the segmentation fault is about? Or how to fix seamonkey?
When I click on the seamonkey icon, still get a 'flash' (partial screen, or show) of a start & then zip.
Tried to uninstall (did a reboot this time; not sure if I did the first time) & install Mozilla 1.85b1.5 again & shows to be installed (in pupget), but don't see this anywhere either & never did after multiple attempts, to install.
Outa curiousity, this seamonky prob started when I attempted to download Moziila 1.85b1.5. Was just looking to get some secondary browsers up & running & did work out with Opera & firefox.
Have to assume that Mozilla1.85b.1.5 is Diff from Mozilla Seamonkey?
Tried mozstart in console again & still gettin the 'segmentation fault'.
Anyone know what the segmentation fault is about? Or how to fix seamonkey?
When I click on the seamonkey icon, still get a 'flash' (partial screen, or show) of a start & then zip.
Tried to uninstall (did a reboot this time; not sure if I did the first time) & install Mozilla 1.85b1.5 again & shows to be installed (in pupget), but don't see this anywhere either & never did after multiple attempts, to install.
Outa curiousity, this seamonky prob started when I attempted to download Moziila 1.85b1.5. Was just looking to get some secondary browsers up & running & did work out with Opera & firefox.
Have to assume that Mozilla1.85b.1.5 is Diff from Mozilla Seamonkey?
Last edited by jonyo on Sun 14 Jan 2007, 07:41, edited 2 times in total.
1.85b.1.5
I think that was the last version of mozilla, before it was renamed to seamonkey.
I think it was an inofficial build for Puppy 2.00 or so.
So it was built against an older version of Gtk, and maybe other older libraries.
In short words:
incompatible with Puppy 2.10 or newer.
Unfortunately installing it, you overwrote Puppys /usr/lib/mozilla.
Solution (if you run Puppy from CD):
delete
/initrd/pup_rw/usr/lib/mozilla
Then reboot.
Then the original write-protected files from the CD (aka pup_212.sfs) are used again.
If no other files were overwritten, this might work.
Mark
I think that was the last version of mozilla, before it was renamed to seamonkey.
I think it was an inofficial build for Puppy 2.00 or so.
So it was built against an older version of Gtk, and maybe other older libraries.
In short words:
incompatible with Puppy 2.10 or newer.
Unfortunately installing it, you overwrote Puppys /usr/lib/mozilla.
Solution (if you run Puppy from CD):
delete
/initrd/pup_rw/usr/lib/mozilla
Then reboot.
Then the original write-protected files from the CD (aka pup_212.sfs) are used again.
If no other files were overwritten, this might work.
Mark
Will it work in 2.12 & don imagine terminal is the same as console
Have a 2.13 multisession but messed up somewhere on that as it won't reboot after saving to it (others in the same boat on another thread).
http://www.murga-linux.com/puppy/viewtopic.php?t=14354
I could burn a read only 2.13 but i'm not past having run a live 2.12.
If just a matter of running a 2.13 (over a 2.12) , I could probly swing that...just need to know what a terminal is
Have a 2.13 multisession but messed up somewhere on that as it won't reboot after saving to it (others in the same boat on another thread).
http://www.murga-linux.com/puppy/viewtopic.php?t=14354
I could burn a read only 2.13 but i'm not past having run a live 2.12.
If just a matter of running a 2.13 (over a 2.12) , I could probly swing that...just need to know what a terminal is
Ok. Tried it out & didn't work
First, I typed in
--------------------------------
rm -f /usr/lib/mozilla & pressed enter
-----------------------------------
then this,
-----------------------
ln -sf /usr/lib/seamonkey-1.0.4 /usr/lib/mozilla
----------------------------
& pressed enter
==========================================
Console page starts with sh-3.00# & each time I press enter (after an entry) all that happens is a new line shows up begenning with sh-300#
Ends up looking like this.
sh-3'00# rm -f /usr/lib/mozilla
sh-3'00# ln -sf /usr/lib/seamonkey-1.0.4 /usr/lib/mozilla
sh-3'00#
Btw, what it that sh-3'00# about? A version # of console? & is it normal?
First, I typed in
--------------------------------
rm -f /usr/lib/mozilla & pressed enter
-----------------------------------
then this,
-----------------------
ln -sf /usr/lib/seamonkey-1.0.4 /usr/lib/mozilla
----------------------------
& pressed enter
==========================================
Console page starts with sh-3.00# & each time I press enter (after an entry) all that happens is a new line shows up begenning with sh-300#
Ends up looking like this.
sh-3'00# rm -f /usr/lib/mozilla
sh-3'00# ln -sf /usr/lib/seamonkey-1.0.4 /usr/lib/mozilla
sh-3'00#
Btw, what it that sh-3'00# about? A version # of console? & is it normal?
MU wrote:n Puppy 2.12 type:
rm -f /usr/lib/mozilla
ln -sf /usr/lib/seamonkey-1.0.4 /usr/lib/mozilla
Yeah, it's just the console prompt. It's supposed to be there.
If you are going to be doing this much modification of a standard Puppy, loading in various dotpups and so forth, you need to protect yourself by saving a copy of your pup_save file somewhere between each attempt. Neglecting that is... unwise. Puppy does not have a whole army of paid testers out there making sure old dotpups work with new revisions. It's "experimental". And it's free.
Also, read up a bit on working at the console. That is inevitable in any linux os, even though it can be minimized some.
Barry, this points up something that might be added to your latest petget effort. There needs to be a warning before proceding with the install of a new package: "DID YOU REMEMBER TO SAVE A BACKUP COPY OF YOUR PUP_SAVE FILE FIRST?" In red, flashing letters if possible. It's fairly easy to forget or not be aware. Heck, you might even have petget save its own copy of the pup_save somewhere...
If you are going to be doing this much modification of a standard Puppy, loading in various dotpups and so forth, you need to protect yourself by saving a copy of your pup_save file somewhere between each attempt. Neglecting that is... unwise. Puppy does not have a whole army of paid testers out there making sure old dotpups work with new revisions. It's "experimental". And it's free.
Also, read up a bit on working at the console. That is inevitable in any linux os, even though it can be minimized some.
Barry, this points up something that might be added to your latest petget effort. There needs to be a warning before proceding with the install of a new package: "DID YOU REMEMBER TO SAVE A BACKUP COPY OF YOUR PUP_SAVE FILE FIRST?" In red, flashing letters if possible. It's fairly easy to forget or not be aware. Heck, you might even have petget save its own copy of the pup_save somewhere...
That's good.each time I press enter (after an entry) all that happens is a new line shows up begenning with sh-300# Sad
No message means no error.
Yes, that is the so called "prompt".Btw, what it that sh-3'00# about? A version # of console? & is it normal?
So now after a change, do you still get the "segmentation fault" eror, when you type
mozstart
?
Or a different error now?
Mark
YES! Managed to copy & paste this from the console.. Don't think I was able to do that inside console & had to (PIA..for me)) type everything,, Is there a way to copy & paste into a console?
OK, mozstart now sez..
------------------------------------------------------------
sh-3.00# mozstart
/usr/local/bin/mozstart: line 16: /usr/lib/mozilla/mozilla-bin: No such file or directory
/usr/local/bin/mozstart: line 16: exec: /usr/lib/mozilla/mozilla-bin: cannot execute: No such file or directory
sh-3.00#
-------------------------------------------------------------------
Thx for the comments on backing up; hearing about it & how it's done for the first time & i'll certainely try it out..
OK, mozstart now sez..
------------------------------------------------------------
sh-3.00# mozstart
/usr/local/bin/mozstart: line 16: /usr/lib/mozilla/mozilla-bin: No such file or directory
/usr/local/bin/mozstart: line 16: exec: /usr/lib/mozilla/mozilla-bin: cannot execute: No such file or directory
sh-3.00#
-------------------------------------------------------------------
Thx for the comments on backing up; hearing about it & how it's done for the first time & i'll certainely try it out..
to copy&paste:
select text with the mouse.
Then MIDDLE click in the console to paste it.
This works in most applications, and is quite practical.
Your error:
please enter this command:
cp -ax /initrd/pup_ro2/usr/local/bin/mozstart /usr/local/bin/mozstart
This will copy the original mozstart from Puppys original write-protected systemfiles to the "active" filesystem again.
You need that, as that file was overwritten by the mozilla-package.
In seamonkey, there is no mozilla-bin , instead it is called seamonkey-bin.
So you need the original mozstart again.
Mark
select text with the mouse.
Then MIDDLE click in the console to paste it.
This works in most applications, and is quite practical.
Your error:
please enter this command:
cp -ax /initrd/pup_ro2/usr/local/bin/mozstart /usr/local/bin/mozstart
This will copy the original mozstart from Puppys original write-protected systemfiles to the "active" filesystem again.
You need that, as that file was overwritten by the mozilla-package.
In seamonkey, there is no mozilla-bin , instead it is called seamonkey-bin.
So you need the original mozstart again.
Mark
think i typed it right..this time..
sh-3.00# cp -ax /initrd/pup_ro2/usr/local/bin/mozstart /usr/local/bin/mozstart
sh-3.00#
===============
punched in mozstart
===============
sh-3.00# mozstart
/usr/local/bin/mozstart: line 20: /usr/lib/mozilla/mozilla-bin: No such file or directory
/usr/local/bin/mozstart: line 20: exec: /usr/lib/mozilla/mozilla-bin: cannot execute: No such file or directory
sh-3.00#
sh-3.00# cp -ax /initrd/pup_ro2/usr/local/bin/mozstart /usr/local/bin/mozstart
sh-3.00#
===============
punched in mozstart
===============
sh-3.00# mozstart
/usr/local/bin/mozstart: line 20: /usr/lib/mozilla/mozilla-bin: No such file or directory
/usr/local/bin/mozstart: line 20: exec: /usr/lib/mozilla/mozilla-bin: cannot execute: No such file or directory
sh-3.00#