SeaMonkey bug in 1.1 (I think) - Mozilla

This is a discussion on SeaMonkey bug in 1.1 (I think) - Mozilla ; On 1/20/2007 7:19 PM Roger Fink created this reply > Michael Gordon wrote: > >> Two suggestions: >> >>>> 1. Trim your posts to something less than 228 lines :-) >>>> 2. File a bug if the reinstallation doesn't work: ...

+ Reply to Thread
Page 2 of 2 FirstFirst 1 2
Results 21 to 24 of 24

Thread: SeaMonkey bug in 1.1 (I think)

  1. Re: SeaMonkey bug in 1.1 (I think)

    On 1/20/2007 7:19 PM Roger Fink created this reply
    > Michael Gordon wrote:
    >
    >> Two suggestions:
    >>
    >>>> 1. Trim your posts to something less than 228 lines :-)
    >>>> 2. File a bug if the reinstallation doesn't work:
    >>>> http://prefbar.mozdev.org/bugs.html
    >>>> If it is a bug this will give Manuel Reimer a chance to look at it &
    >>>> possibly fix it.
    >>>>
    >>>>
    >>> Please explain to me, or provide a link, on how to do this, if it is
    >>> something other than wholesale deleting of text.
    >>>
    >>>
    >>>
    >>>

    >> Hello Roger,
    >>
    >> When you reply to a long post you can highlight that part that does
    >> not pertain to your answer and select Edit/Cut to remove the extra
    >> text, or highlight the text and right click the mouse and select Cut.
    >>
    >> However in this case all the text pertains to trying to solve your
    >> problem and a late arrival may miss some important discussion.
    >>
    >> For the gentleman who suggested shortening your post because it is
    >> very long I suggest he use the "Space Bar" to scroll page by page.
    >>
    >> Michael
    >>

    >
    > I thought that there might have been some automated way to do it. Now that I
    > think of it, I'm using the Devil's Newsreader anyway, so extensions would be
    > pointless.
    > Last you'll hear from me until I'm finished with the exercises above.
    >
    >
    >

    What I want to read (hear) is good news.

    Michael

    --
    Posting Guidelines for MTMM

    Posting To Mozilla.Test.Multimedia


    SeaMonkey the all in one browser, mail, and composer SeaMonkey

    The "All In One Internet Application Suite"

  2. Re: SeaMonkey bug in 1.1 (I think)

    On 1/20/2007 7:36 PM NoOp created this reply
    > Michael Gordon wrote:
    >
    >> Two suggestions:
    >>
    >>>> 1. Trim your posts to something less than 228 lines :-)
    >>>> 2. File a bug if the reinstallation doesn't work:
    >>>> http://prefbar.mozdev.org/bugs.html
    >>>> If it is a bug this will give Manuel Reimer a chance to look at it &
    >>>> possibly fix it.
    >>>>
    >>>>
    >>> Please explain to me, or provide a link, on how to do this, if it is
    >>> something other than wholesale deleting of text.
    >>>
    >>>
    >>>
    >>>

    >> Hello Roger,
    >>
    >> When you reply to a long post you can highlight that part that does not
    >> pertain to your answer and select Edit/Cut to remove the extra text, or
    >> highlight the text and right click the mouse and select Cut.
    >>
    >> However in this case all the text pertains to trying to solve your
    >> problem and a late arrival may miss some important discussion.
    >>
    >> For the gentleman who suggested shortening your post because it is very
    >> long I suggest he use the "Space Bar" to scroll page by page.
    >>
    >> Michael
    >>
    >>

    >
    > A late arrival can scroll back up in the thread to obtain additional
    > information. It's easy enough to do this. Just tacking on to the end of
    > each post seems to be a carryover from the old Netscape newgroup whereby
    > everyone just added something at the end (sometimes only a single
    > sentence or word) and the posts would grow to 300 lines or more. You
    > then spend the time scrolling down each one only to find some dit
    > tacking a "I agree" or similar at the end.
    >
    > The OP (and others) can do as they wish, but common courtesy would
    > suggest that trimming posts to the relevant bits makes life easier for
    > those that follow the posts in the thread :-)
    >
    > As an added point; it's always good to also include attributes in your
    > reply so that other folks know who you are responding to. Example; in
    > your post (left intact on purpose because Michael Gordon provided no
    > attribute to who he was responding to) you responded do someone but
    > there is no attribute to who you are reponding to (e.g., Roger Fink
    > wrote: or NoOp wrote. You can fix this by:
    >
    > about:config
    > pref mailnews.reply_header_authorwrote
    > insert the original: %s wrote
    > and that will get you back to the basic "author wrote" setting.
    >

    I just now looked at your reference in my about:config and it reads:

    %s created this reply

    Is there something else I missed?

    Michael
    > For the OP/Roger:
    >
    > Select the irrelevent bits of what you are replying to and delete them;
    > marked the dead space as [snip] if you'd like to indicate that you've
    > cut text out of the post you are replying to. However, if you do include
    > text from multiple authors in the post be sure to include the "author
    > wrote" bit at the top. Example:
    >
    > NoOp wrote:
    >
    >> Roger Fink wrote:
    >>
    >>

    >
    > That way folks know that lines with > are from the author listed first
    > (in this case NoOp) and lines with >> are from the author listed second etc.
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >



    --
    Posting Guidelines for MTMM

    Posting To Mozilla.Test.Multimedia


    SeaMonkey the all in one browser, mail, and composer SeaMonkey

    The "All In One Internet Application Suite"

  3. Re: SeaMonkey bug in 1.1 (I think)

    Chris Ilias wrote:
    > _Roger Fink_ spoke thusly on 20/01/2007 8:19 PM:
    >> Michael Gordon wrote:
    >>> However in this case all the text pertains to trying to solve your
    >>> problem and a late arrival may miss some important discussion.
    >>>
    >>> For the gentleman who suggested shortening your post because it is
    >>> very long I suggest he use the "Space Bar" to scroll page by page.

    >>
    >> I thought that there might have been some automated way to do it. Now
    >> that I
    >> think of it, I'm using the Devil's Newsreader anyway, so extensions
    >> would be
    >> pointless.
    >> Last you'll hear from me until I'm finished with the exercises above.

    >
    > The Mozilla Forum Etiquette page says to trim.
    >

    just found a weird bug.
    attempted to send a post to person signed and encrypted. received a pop
    down say failed can not send to such and such (name of person) I
    dismissed the warning. The received a hard crash of SM 1.1.

    Previous versions Mozilla/communicator it would sign it and send the
    key. once the signer on the other end click on the key they could read
    the message. What happened?

    --
    ------------------------------------------------------------------------
    Phillip M. Jones, CET http://www.vpea.org
    If it's "fixed", don't "break it"! mailtojones@kimbanet.com
    http://www.kimbanet.com/~pjones/default.htm
    ------------------------------------------------------------------------

  4. Re: SeaMonkey bug in 1.1 (I think)

    Michael Gordon wrote:
    > On 1/19/2007 9:18 PM Roger Fink created this reply
    >> Michael Gordon wrote:
    >>
    >>> On 1/19/2007 7:36 PM Roger Fink created this reply
    >>>
    >>>> Daniel wrote:
    >>>>
    >>>>
    >>>>> Roger Fink wrote:
    >>>>>
    >>>>>
    >>>>>> I just installed SeaMonkey 1.1 (browser only) exactly by the
    >>>>>> book,
    >>>>>> and I also uninstalled all extensions before doing so, adding
    >>>>>> them
    >>>>>> back one by one, quicklaunch off, closing and opening the browser
    >>>>>> between installs, and testing it out as I went along, which was a
    >>>>>> good thing or else I wouldn't have been able to isolate the
    >>>>>> problem.
    >>>>>>
    >>>>>> Everything was fine until I got to the prefbar. It installed OK,
    >>>>>> self-updated OK, browser worked fine, but when I switched
    >>>>>> profiles
    >>>>>> a note popped up, as it also had done in the default profile,
    >>>>>> asking
    >>>>>> if I wanted to update its data base. I clicked yes, and the note
    >>>>>> closed but then a big blank 1" band appeared across the bottom of
    >>>>>> the screen. I closed the browser but after that it froze, and
    >>>>>> wouldn't open with any shortcut or seamonkey.exe.
    >>>>>>
    >>>>>> Reverted with GoBack to before the prefbar installation and
    >>>>>> installed it again. When I switched profiles, same thing happened
    >>>>>> again. This time I answered no to the data base update box
    >>>>>> ("cancel" as I recall), but the result was the same. Love
    >>>>>> SeaMonkey, but unfortunately this one's mission-critical so I'm
    >>>>>> back to 1.0.7 until it can be fixed.
    >>>>>>
    >>>>>> One additional item. When you delete an extension with the
    >>>>>> extension manager, it asks you to specify a place to create a
    >>>>>> back
    >>>>>> up folder (I believe, but I'm not sure, that you don't have to
    >>>>>> fill this in). I specified D:\ , but no files or folders were
    >>>>>> ever created there. Everything was automatically backed up to
    >>>>>> *.slt\chrome\uninstall\backup\ of the default profile. No harm
    >>>>>> that
    >>>>>> I can see, but the user-defined location doesn't work, at least
    >>>>>> it didn't for me.
    >>>>>>
    >>>>>> Extensions: adblock (old), dictionary search, flashblock,
    >>>>>> prefbar, themer, home button (on nav. toolbar), extension
    >>>>>> manager, extension uninstallerapi.
    >>>>>>
    >>>>>> Running Windows 98SE.
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>> Roger, I had a similar thing happen (band across bottom of browser
    >>>>> screen) a few versions ago (may have even been Moz suite).
    >>>>>
    >>>>> With mine, there was a message in the bottom part of screen, that
    >>>>> indicated one of the extensions I was using was incompatible with
    >>>>> the updated browser. Do you get similar message?? If so, go
    >>>>> looking
    >>>>> for an updated version of problem extension....maybe give
    >>>>> developers a couple of days!
    >>>>>
    >>>>> HTH
    >>>>>
    >>>>> Daniel
    >>>>>
    >>>>>
    >>>> The same thought had occurred to me - wait for a prefbar update. I
    >>>> just updated the version I had, which was one behind, thinking that
    >>>> maybe the problem was that it couldn't make the jump, and then
    >>>> repeated the whole process, but the result was the same. BTW, still
    >>>> no message on the bottom band.
    >>>>
    >>>>
    >>>>
    >>>>
    >>> Hello Roger,
    >>>
    >>> Preference Bar works very well here on Win XP Pro.
    >>>
    >>> From your description I suspect it is an incompatibility between
    >>> themes and another extension.
    >>> Try removing all your extensions and see how it works, then try
    >>> installing them again one at a time until you find the culprit. It
    >>> is
    >>> not SeaMonkey 1.1 that is at fault, it is one of the add on
    >>> applications that is not compatible with another ad on application.
    >>>
    >>> Michael
    >>>

    >>
    >> Michael, you may be right that it is not SeaMonkey 1.1, but that
    >> does not necessarily equate to not having a mystery on my hands. The
    >> first time I installed prefbar in 1.1 I used the default modern
    >> theme and all extensions had been removed and reinstalled one by
    >> one, and prefbar was the last in that sequence. When I installed it
    >> the second time (upgraded to latest prefbar version) all extensions
    >> had again been removed, I was again using the default modern theme,
    >> but this time prefbar was the first install in the sequence. A
    >> possible culprit could be a dated operating system that overworked
    >> developers (understandably) can't spend enough time on. Or, perhaps
    >> certain jar edits I do to customize the GUI had an effect, but I've
    >> been through many of these upgrades now (like for instance every one
    >> of them) and this has never presented a problem before.
    >>
    >> I assume that prefbar will in fact be updated as a result of this
    >> release - I hope so because it's so customizable and can display so
    >> much information that it's probably a more important tool for
    >> SeaMonkey than for FF. I'll try again then, or earlier if there is
    >> some procedure I did that could be improved, but it sounds to me as
    >> though what I did was pretty much what you are suggesting.
    >>
    >>
    >>
    >>
    >>
    >>
    >>
    >>
    >>
    >>

    > Roger,
    >
    > You may be right in that developers no longer take the time required
    > to
    > make their systems, plugins, and extensions compatible for older
    > Microsoft operating systems.
    >
    > I recall that Mozilla products install critical files in different
    > locations between Win 98 and Win XP, but if the extensions and themes
    > are partly installed in the Mozilla/SeaMonkey program folder then
    > deleting the program folder and all its contents will cause major
    > problems such as you now have.
    >
    > In Win XP plugins are saved in the Mozilla/SeaMonkey program folder,
    > and extensions are stored in the SeaMonkey Profile folder. It is for
    > this
    > reason that when I upgrade to a new version of SeaMonkey I do not
    > allow
    > the installer to remove the program folder and all remaining files and
    > when I install an extension I install for a single user.
    >
    > After installing the new version all my plugins, extensions and themes
    > are intact and working well.
    >
    > Michael



    First off, praise be to GoBack. I don't know how folks who regularly do
    software troubleshooting get by without it, though obviously many do.

    I did deviate from the plan, but in this case it was a good move, as the
    first thing I tried was also the last. I did a conventional browser-only
    install of 1.1 by first uninstalling 1.0.7 (recall that I have only the
    browser installed). I didn't uninstall any extensions or themes, even though
    some of them needed to be upgraded. What changed this time was that as you
    (and the uninstall dialog) recommended, I did not uninstall the program
    folder. That made all the difference, and SeaMonkey seems to be running fine
    now, with all extensions and themes properly upgraded after the fact.

    So - operator error. Thanks for putting me on the right track.

    Boy, this thing is fast.





+ Reply to Thread
Page 2 of 2 FirstFirst 1 2