• Error finding libXm.so.4

    From Doug Laidlaw@2:250/1 to All on Wed Oct 9 18:09:04 2019
    [I think that something like this happened once before, a library was
    there, but "invisible."]

    I am running Xephem, an astronomy program written in Motif. It has
    libXm.so.4 as a dependency. libXm.so.4 is in /usr/lib, as a symlink to libXm.so.4.0.4, but Xephem can't find it. I tried to uninstall and
    reinstall the library, but that would have removed a swag of apps,
    including Cups and Xephem itself. It worked in the past day or so. I
    ran "sudo ldconfig" as a precaution, but that may no longer be relevant
    in the systemd world. Rebooting had no effect.

    Is there a reason why this happens?

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Wed Oct 9 22:05:10 2019
    On 10/10/19 4:09 am, Doug Laidlaw wrote:
    [I think that something like this happened once before, a library was
    there, but "invisible."]

    I am running Xephem, an astronomy program written in Motif.  It has libXm.so.4 as a dependency.  libXm.so.4 is in /usr/lib, as a symlink to libXm.so.4.0.4, but Xephem can't find it.  I tried to uninstall and reinstall the library, but that would have removed a swag of apps,
    including Cups and Xephem itself.  It worked in the past day or so.  I
    ran "sudo ldconfig" as a precaution, but that may no longer be relevant
    in the systemd world.  Rebooting had no effect.

    Is there a reason why this happens?

    Two immediate silly things come to mind.
    Is it permissions or is /usr/lib in the $PATH.

    regards


    faeychild
    Running plasmashell 5.15.4 on 5.2.13-desktop-2.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Doug Laidlaw@2:250/1 to All on Thu Oct 10 01:01:58 2019
    On 10/10/19 8:05 am, faeychild wrote:
    On 10/10/19 4:09 am, Doug Laidlaw wrote:
    [I think that something like this happened once before, a library was
    there, but "invisible."]

    I am running Xephem, an astronomy program written in Motif.  It has
    libXm.so.4 as a dependency.  libXm.so.4 is in /usr/lib, as a symlink
    to libXm.so.4.0.4, but Xephem can't find it.  I tried to uninstall and
    reinstall the library, but that would have removed a swag of apps,
    including Cups and Xephem itself.  It worked in the past day or so.  I
    ran "sudo ldconfig" as a precaution, but that may no longer be
    relevant in the systemd world.  Rebooting had no effect.

    Is there a reason why this happens?

    Two immediate silly things come to mind.
    Is it permissions or is /usr/lib in the $PATH.


    Naturally, I checked both those. My next thought is that libXm.so.4.0.4
    won't work in this program (the reason why I have always advocated using
    only Mageia RPMs.) I am running Cauldron, for other reasons. 7.1
    Official doesn't have the problem. That suggested that maybe there was a recent update of the library, but the Changelog shows that there wasn't
    one. I could try recompiling xephem from the tarball.

    regards


    faeychild
    Running plasmashell 5.15.4 on 5.2.13-desktop-2.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via
    Mageia-7-x86_64-DVD.iso


    Can you please give me the sig line that pulls in this info? BitTwister
    gave it to me long ago, but I have lost it.

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Oct 10 01:16:33 2019
    On Thu, 10 Oct 2019 11:01:58 +1100, Doug Laidlaw wrote:

    Can you please give me the sig line that pulls in this info?

    That is not a line. it is a few lines in a script usually executed
    during login.

    BitTwister gave it to me long ago, but I have lost it.




    #!/bin/bash #***********************************************************************
    #* gen_sig_file.sh - generate $HOME/.signature file Version 1.0
    #*
    #* Automatically overwrites $HOME/.signature on each login
    #* with basic information about your setup.
    #*
    #* When you post to Usenet your Usenet client can append it to your
    #* post which helps respondents to provide more detailed replies.
    #*
    #* You need to place the script somewhere in your $PATH environment.
    #* echo $PATH to see possible locations.
    #*
    #* Save as gen_sig_file.sh
    #* chmod +x gen_sig_file.sh
    #*
    #* Script Test Procedure:
    #* gen_sig_file.sh
    #* cat $HOME/.signature
    #*
    #* Install:
    #* For all users:
    #* cp gen_sig_file.sh /etc/profile.d
    #* or put a link in /etc/profile.d back to gen_sig_file.sh
    #* that everyone can read/execute.
    #*
    #* For a single user:
    #* echo $PATH to see possible locations.
    #*
    #* put $HOME/wherever/gen_sig_file.sh location in user's shell's
    #* startup script, for example ~/.bash_profile or ~/.bashrc
    #*
    #* Login test:
    #* click up a terminal
    #* su - $USER
    #* cat $HOME/.signature
    #*
    #* Modify your Usenet client to add/append $HOME/.signature
    #* to your posts and post a message in one of the Usenet test groups
    #* to verify it works as desired.
    #*
    #***********************************************************************

    Sig_fn=$HOME/.signature

    DM=""
    DISTRO=""

    set $(lsb_release -d | grep Description)
    if [ $# -gt 1 ] ; then
    shift
    DISTRO="$@"
    fi

    if [ -e /etc/sysconfig/desktop ] ; then
    . /etc/sysconfig/desktop
    dm="DM=$DISPLAYMANAGER"
    fi

    if [ -e /etc/release ] ; then
    DISTRO=$(cat /etc/release)
    fi

    set -- $(systemctl status display-manager.service | grep PID:)
    Greeter=$(echo $4 | tr -d '() ')

    echo -en "-- \nRunning " > $Sig_fn
    echo "$DISTRO " >> $Sig_fn
    echo "$(uname -r) on $(uname -m) Greeter=$Greeter $DM DE=$XDG_SESSION_DESKTOP" >> $Sig_fn


    #***********end gen_sig_file.sh ***************************

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Oct 10 02:38:04 2019
    On 10/10/19 11:01 am, Doug Laidlaw wrote:


    Can you please give me the sig line that pulls in this info?  BitTwister gave it to me long ago, but I have lost it.



    Bits has considerable elaborated the sig line command these days but I
    still use the original dropped into ".bash_profile"

    *****************

    mga_release=$(cat /etc/release)
    plasma=$(plasmashell --version)
    echo "faeychild
    Running $plasma on $(uname -r) kernel.
    $mga_release installed via Mageia-7-x86_64-DVD.iso
    " > $HOME/.signature

    **************

    regards
    --
    faeychild
    Running plasmashell 5.15.4 on 5.2.13-desktop-2.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Oct 10 02:44:38 2019
    On 10/10/19 11:01 am, Doug Laidlaw wrote:

    Naturally, I checked both those.  My next thought is that libXm.so.4.0.4 won't work in this program (the reason why I have always advocated using only Mageia RPMs.)  I am running Cauldron, for other reasons. 7.1
    Official doesn't have the problem. That suggested that maybe there was a recent update of the library, but the Changelog shows that there wasn't one.  I could try recompiling xephem from the tarball.


    You can also run it with "strace". If, unlike me, you can follow the
    output and see if it finds the library.


    --


    faeychild
    Running plasmashell 5.15.4 on 5.2.13-desktop-2.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)