Has anyone else had problems with the latest 5.0.7 updates? - SCO

This is a discussion on Has anyone else had problems with the latest 5.0.7 updates? - SCO ; I had been running 5.0.7, MP3, update 3, pretty much everything current as of this past spring. I decided I'd install the latest gwxlibs, openssh, and Perl from SCO's site. After doing that, I had a couple of problems, one ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: Has anyone else had problems with the latest 5.0.7 updates?

  1. Has anyone else had problems with the latest 5.0.7 updates?

    I had been running 5.0.7, MP3, update 3, pretty much everything
    current as of this past spring.

    I decided I'd install the latest gwxlibs, openssh, and Perl from
    SCO's site. After doing that, I had a couple of problems, one severe
    enough that I had to roll it all back and restore the previous
    versions.

    The not-so-severe problem is that spamd (SpamAssassin's daemonized
    version; this is from SpamAssassin 2.63, since SA3 has
    problems running on 5.0.7 with SCO's version of Perl) says
    "unix passed to setlogsock, but path not available" and becomes
    unable to write to syslog. Other than the error message and lack
    of logging, spamd works. This seems to be a common problem on
    Solaris but I can't find any reference to it for SCO systems.

    But while trying to sort that out, I found a bigger problem:
    Mozilla* thinks that every time I hit the letter q, I'm actually
    hitting the Tab key. There's nothing wrong with my keyboard; the q
    key works fine on a text screen, or even in a Unix command prompt
    window on the same multiscreen as Mozilla. This is a bit of a bizarre
    problem; the other keys I tried (including at least most of the rest
    of the alphabet) work properly. I can fix this by rolling back
    gwxlibs and reinstalling the older version, and I can break it again
    by reinstalling the newer version, so clearly something in gwxlibs
    is the issue. FWIW, this is with a Microsoft Internet Keyboard
    with a PS/2 connector.

    Anyone else seen odd problems like this from installing these
    updates?

    *: And a slap to SCO for not taking updates and security bugs
    seriously when it comes to Mozilla. They made a big deal out of
    including Mozilla in 5.0.7, yet the latest version they make available
    is 1.6, in MP3. That was over a year ago. 1.7 came out over a year
    ago. Why the delay?
    --
    Stephen M. Dunn
    >>>----------------> http://www.stevedunn.ca/ <----------------<<<

    ------------------------------------------------------------------
    Say hi to my cat -- http://www.stevedunn.ca/photos/toby/

  2. Re: Has anyone else had problems with the latest 5.0.7 updates?

    Stephen M. Dunn wrote:
    > I had been running 5.0.7, MP3, update 3, pretty much everything
    > current as of this past spring.
    >
    > I decided I'd install the latest gwxlibs, openssh, and Perl from
    > SCO's site. After doing that, I had a couple of problems, one severe
    > enough that I had to roll it all back and restore the previous
    > versions.
    >
    > The not-so-severe problem is that spamd (SpamAssassin's daemonized
    > version; this is from SpamAssassin 2.63, since SA3 has
    > problems running on 5.0.7 with SCO's version of Perl) says
    > "unix passed to setlogsock, but path not available" and becomes
    > unable to write to syslog. Other than the error message and lack
    > of logging, spamd works. This seems to be a common problem on
    > Solaris but I can't find any reference to it for SCO systems.
    >
    > But while trying to sort that out, I found a bigger problem:
    > Mozilla* thinks that every time I hit the letter q, I'm actually
    > hitting the Tab key. There's nothing wrong with my keyboard; the q
    > key works fine on a text screen, or even in a Unix command prompt
    > window on the same multiscreen as Mozilla. This is a bit of a bizarre
    > problem; the other keys I tried (including at least most of the rest
    > of the alphabet) work properly. I can fix this by rolling back
    > gwxlibs and reinstalling the older version, and I can break it again
    > by reinstalling the newer version, so clearly something in gwxlibs
    > is the issue. FWIW, this is with a Microsoft Internet Keyboard
    > with a PS/2 connector.
    >
    > Anyone else seen odd problems like this from installing these
    > updates?


    I had the problem with 'q' in mozilla but I don't know when it
    appeared. Very annoying. It's gone in the mozilla in OSR6, but also
    gone is unix kill line control-u functionality. Typing ctrl-u in the
    address bar now opens the page-source window instead of erasing the
    line.


  3. Re: Has anyone else had problems with the latest 5.0.7 updates?

    Roger Cornelius typed (on Sat, Aug 27, 2005 at 07:49:27AM -0700):
    | Stephen M. Dunn wrote:
    | > I had been running 5.0.7, MP3, update 3, pretty much everything
    | > current as of this past spring.
    | >
    | > I decided I'd install the latest gwxlibs, openssh, and Perl from
    | > SCO's site. After doing that, I had a couple of problems, one severe
    | > enough that I had to roll it all back and restore the previous
    | > versions.
    | >

    .....

    | > But while trying to sort that out, I found a bigger problem:
    | > Mozilla* thinks that every time I hit the letter q, I'm actually
    | > hitting the Tab key. There's nothing wrong with my keyboard; the q
    | > key works fine on a text screen, or even in a Unix command prompt
    | > window on the same multiscreen as Mozilla. This is a bit of a bizarre
    | > problem; the other keys I tried (including at least most of the rest
    | > of the alphabet) work properly. I can fix this by rolling back
    | > gwxlibs and reinstalling the older version, and I can break it again
    | > by reinstalling the newer version, so clearly something in gwxlibs
    | > is the issue. FWIW, this is with a Microsoft Internet Keyboard
    | > with a PS/2 connector.
    | >
    |
    | I had the problem with 'q' in mozilla but I don't know when it
    | appeared. Very annoying. It's gone in the mozilla in OSR6, but also
    | gone is unix kill line control-u functionality. Typing ctrl-u in the
    | address bar now opens the page-source window instead of erasing the
    | line.

    Use Ctrl-Delete to erase the line in the address bar.

    --
    JP

  4. Re: Has anyone else had problems with the latest 5.0.7 updates?

    Stephen M. Dunn typed (on Sat, Aug 27, 2005 at 02:56:03AM +0000):
    | I had been running 5.0.7, MP3, update 3, pretty much everything
    | current as of this past spring.
    |
    | I decided I'd install the latest gwxlibs, openssh, and Perl from
    | SCO's site. After doing that, I had a couple of problems, one severe
    | enough that I had to roll it all back and restore the previous
    | versions.
    |
    | The not-so-severe problem is that spamd (SpamAssassin's daemonized
    | version; this is from SpamAssassin 2.63, since SA3 has
    | problems running on 5.0.7 with SCO's version of Perl) says
    | "unix passed to setlogsock, but path not available" and becomes
    | unable to write to syslog. Other than the error message and lack
    | of logging, spamd works. This seems to be a common problem on
    | Solaris but I can't find any reference to it for SCO systems.

    In my /etc/rc.d/7/udaemons, I have:
    /usr/local/bin/spamd -d --syslog-socket=inet -r /u/etc/spamd.pid

    --
    JP

  5. Re: Has anyone else had problems with the latest 5.0.7 updates?

    Jean-Pierre Radley wrote:
    > Roger Cornelius typed (on Sat, Aug 27, 2005 at 07:49:27AM -0700):
    > | Stephen M. Dunn wrote:
    > | > I had been running 5.0.7, MP3, update 3, pretty much everything
    > | > current as of this past spring.
    > | >
    > | > I decided I'd install the latest gwxlibs, openssh, and Perl from
    > | > SCO's site. After doing that, I had a couple of problems, one severe
    > | > enough that I had to roll it all back and restore the previous
    > | > versions.
    > | >
    >
    > ....
    >
    > | > But while trying to sort that out, I found a bigger problem:
    > | > Mozilla* thinks that every time I hit the letter q, I'm actually
    > | > hitting the Tab key. There's nothing wrong with my keyboard; the q
    > | > key works fine on a text screen, or even in a Unix command prompt
    > | > window on the same multiscreen as Mozilla. This is a bit of a bizarre
    > | > problem; the other keys I tried (including at least most of the rest
    > | > of the alphabet) work properly. I can fix this by rolling back
    > | > gwxlibs and reinstalling the older version, and I can break it again
    > | > by reinstalling the newer version, so clearly something in gwxlibs
    > | > is the issue. FWIW, this is with a Microsoft Internet Keyboard
    > | > with a PS/2 connector.
    > | >
    > |
    > | I had the problem with 'q' in mozilla but I don't know when it
    > | appeared. Very annoying. It's gone in the mozilla in OSR6, but also
    > | gone is unix kill line control-u functionality. Typing ctrl-u in the
    > | address bar now opens the page-source window instead of erasing the
    > | line.
    >
    > Use Ctrl-Delete to erase the line in the address bar.


    Thanks, I hadn't considered that. Ctrl-backspace also works, and,
    having now looked at the mozilla help, ctrl-l followed by delete works
    regardless of where on the line the cursor is. But it will take a
    while to break the ctrl-u habit.

    Another mozillaism I discovered is typing about:config in the address
    bar. It displays, and allows you to edit, the mozilla config
    parameters.


+ Reply to Thread