Page 1 of 3 123 LastLast
Results 1 to 10 of 24

Thread: installed packages can't be launched

  1. #1
    Join Date
    May 2017
    Location
    Reunion Island
    Posts
    33

    Default installed packages can't be launched

    Hi everybody,

    strange issue here that I never had in 13 years of linux usage (at least 2 on tumbleweed).

    I had to run recently a fresh installation of Tumbleweed, which was comfortable enough since my /home is on a separate partition, and because OpenSuse allows to get user's settings back. I have to mention that Yast was'nt working any longer, due probably to some incompatibilities in my packages downloadings and unappropriate decisions regarding upgrades and vendor changes, and that was the reason for my reinstall.

    After that, everything seemed to work like a charm. I added Packman repository, among somme other actions like allowing dvd to be read - which is very common. And, as my laptop is an Asus with a Realtek ethernet controller, I wanted to install r8168-blacklist-r8169 as I've done many times before, because r8169 (driver provided by default) "ist defekt" (more or less broken) most of the time. I did it and, one more time, everything seemed to go ahead smoothly.

    Untill a recent update. I did it command-line with the recommended option : "sudo zypper dup --no-allow-vendor-change".

    Now, ... When I open Yast (install or delete applications), I see that r8168-blacklist-r8169 and r8168-kpm-default are installed. Unfortunately, r8168 is not launched at booting, nor r8169 of course since it is blacklisted. Should I try to launch it manually with modprobe, most of the time it will fail.

    The core of that issue seems to reside in those lines, since I tried to install avidemux3 (from yast) :

    Code:
    erik@linux-r13d:~> sudo zypper in avidemux3
    Chargement des données du dépôt...
    Lecture des paquets installés...
    'avidemux3' est déjà installé.
    Pas de candidat à la mise à jour pour 'avidemux3-2.7.1-1.31.x86_64'. La version la plus récente est déjà installée.
    Résolution des dépendances des paquets...
    
    Rien à faire.
    erik@linux-r13d:~> avidemux3
    If 'avidemux3' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf avidemux3
    So avidemux3 is installed ... but if you want to launch it : "no way".

    Any idea of the problem ? (and of a possible solution !!!) Anybody else who experiences the same issue ??? (I did'nt find any when i searched here).

    Thanks to you folks !

    Erik

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,525
    Blog Entries
    15

    Default Re: installed packages can't be launched

    Quote Originally Posted by Voronamanga View Post
    Hi everybody,

    strange issue here that I never had in 13 years of linux usage (at least 2 on tumbleweed).

    I had to run recently a fresh installation of Tumbleweed, which was comfortable enough since my /home is on a separate partition, and because OpenSuse allows to get user's settings back. I have to mention that Yast was'nt working any longer, due probably to some incompatibilities in my packages downloadings and unappropriate decisions regarding upgrades and vendor changes, and that was the reason for my reinstall.

    After that, everything seemed to work like a charm. I added Packman repository, among somme other actions like allowing dvd to be read - which is very common. And, as my laptop is an Asus with a Realtek ethernet controller, I wanted to install r8168-blacklist-r8169 as I've done many times before, because r8169 (driver provided by default) "ist defekt" (more or less broken) most of the time. I did it and, one more time, everything seemed to go ahead smoothly.

    Untill a recent update. I did it command-line with the recommended option : "sudo zypper dup --no-allow-vendor-change".

    Now, ... When I open Yast (install or delete applications), I see that r8168-blacklist-r8169 and r8168-kpm-default are installed. Unfortunately, r8168 is not launched at booting, nor r8169 of course since it is blacklisted. Should I try to launch it manually with modprobe, most of the time it will fail.

    The core of that issue seems to reside in those lines, since I tried to install avidemux3 (from yast) :

    Code:
    erik@linux-r13d:~> sudo zypper in avidemux3
    Chargement des données du dépôt...
    Lecture des paquets installés...
    'avidemux3' est déjà installé.
    Pas de candidat à la mise à jour pour 'avidemux3-2.7.1-1.31.x86_64'. La version la plus récente est déjà installée.
    Résolution des dépendances des paquets...
    
    Rien à faire.
    erik@linux-r13d:~> avidemux3
    If 'avidemux3' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf avidemux3
    So avidemux3 is installed ... but if you want to launch it : "no way".

    Any idea of the problem ? (and of a possible solution !!!) Anybody else who experiences the same issue ??? (I did'nt find any when i searched here).

    Thanks to you folks !

    Erik
    Hi
    The binary filenames... use tab completion after you type...

    Code:
    avidemux3<press tab button>
    There is _qt5, _cli and _jobs_qt5
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3
    Join Date
    May 2017
    Location
    Reunion Island
    Posts
    33

    Default Re: installed packages can't be launched

    @Malcolm

    Thanks, I have to type avidemux_cli ! This tip was helpful.

    Unfortunately the app did'nt launch. I had an output which is too long to paste here, I only post the last lines :

    Code:
    ([ADM_vf_plugin] ...)
    [ADM_vf_plugin] Plugin loaded version 1.0.0, name mpdelogo2/MPlayer delogo2
    [ADM_vf_plugin] Plugin loaded version 1.0.0, name msharpen/Msharpen
    [ADM_vf_plugin] Plugin loaded version 1.0.1, name swscale/swsResize
    [ADM_vf_plugin] Scanning done, found 49 video filer(s) so far
    *********************************
    *********************************
    End of program..
    *********************************
    *********************************
     [save] 05:01:53-932  Saving prefs to /home/erik/.avidemux3/config3.tmp
     [destroy] 05:01:53-932  Destroying preview
     [deleteAll] 05:01:53-932  [Editor] Deleting all videos
     [deleteAll] 05:01:53-932  [Editor] Deleting all videos
    Normal exit
     [uninstallSigHandler] 05:01:53-932  Removing signal handler
     [abortExitHandler] 05:01:53-932  already done, nothing to do
    09:01:53 Call terminate!!!
    I'm trying to find out what went wrong. Maybe these lines (the 2nd is purple) :

    Code:
    [videoEncoder6]Name :LibVaEncoder (HW) ApiVersion :7 Description :Simple Libva Encoder (c) 2018 Mean
     [ADM_libvaEncoder_probe] 05:01:53-643  No H264 encoding support
    /usr/lib64/ADM_plugins6/videoEncoders/libADM_ve_libva.so:ProbingFailed
    So avidemux could fail just because H264 encoder is lacking ?

    And it is not the only issue : I installed the r8168 driver for my ethernet card, but the module is not present :
    (sorry for the external link, I could'nt manage to insert an image here)
    https://www.dropbox.com/s/qecuv4e39c...r8168.png?dl=0

    Code:
    erik@linux-r13d:~> sudo modprobe -c | grep r816
    [sudo] Mot de passe de root : 
    blacklist r8169
    softdep r8169 pre: realtek
    alias pci:v00000001d00008168sv*sd00002410bc*sc*i* r8169
    alias pci:v000010ECd00002502sv*sd*bc*sc*i* r8169
    alias pci:v000010ECd00002600sv*sd*bc*sc*i* r8169
    alias pci:v000010ECd00008129sv*sd*bc*sc*i* r8169
    alias pci:v000010ECd00008136sv*sd*bc*sc*i* r8169
    alias pci:v000010ECd00008161sv*sd*bc*sc*i* r8169
    alias pci:v000010ECd00008167sv*sd*bc*sc*i* r8169
    alias pci:v000010ECd00008168sv*sd*bc*sc*i* r8169
    alias pci:v000010ECd00008169sv*sd*bc*sc*i* r8169
    alias pci:v000010FFd00008168sv*sd*bc*sc*i* r8169
    alias pci:v00001186d00004300sv*sd*bc*sc*i* r8169
    alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8169
    alias pci:v00001186d00004302sv*sd*bc*sc*i* r8169
    alias pci:v00001259d0000C107sv*sd*bc*sc*i* r8169
    alias pci:v000016ECd00000116sv*sd*bc*sc*i* r8169
    alias pci:v00001737d00001032sv*sd00000024bc*sc*i* r8169
    erik@linux-r13d:~> sudo modprobe r8168
    modprobe: FATAL: Module r8168 not found in directory /lib/modules/5.0.0-4.g6bc6477-default
    So I'm still requesting your help!

    Have a nice day

    Erik

  4. #4
    Join Date
    May 2017
    Location
    Reunion Island
    Posts
    33

    Default Re: installed packages can't be launched

    The problem is now solved for Avidemux : I had no graphic interface ... ... So I installed the qt5 one.

    But it remains for my Realtek driver's replacement of r8169 with r8168, which doesn't work in spite of the fact that it looks like it is installed ... Obviously the two issues were distinct.

    Any idea ? Thanks for reading anyway.

  5. #5
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,889

    Default AW: installed packages can't be launched

    Why do you want to blacklist r8169?
    Its the default.

    So please post:
    Code:
    zypper se -s r8168
    And why running kernel from kernel:stable?
    Module r8168 not found in directory /lib/modules/5.0.0-4.g6bc6477-default
    Last edited by Sauerland; 10-Mar-2019 at 03:08.

  6. #6
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,889

    Default AW: installed packages can't be launched

    Also please post:
    Code:
    zypper lr -d
    Code:
    uname -a

  7. #7
    Join Date
    May 2017
    Location
    Reunion Island
    Posts
    33

    Default Re: installed packages can't be launched

    @Sauerland

    It's kind of you to answer.

    I (almost) all the times have problems with ethernet on OpenSuse, especially with r8169 driver. Connection process is stuck on "Définition de l'adresse réseau" which is something like "configuring network address" and fails. I surfed the web about that and found that it could be better to blacklist r8169 and load r8168, which is way more stable and reliable. I noticed that it was the case, though a couple of times I had to unload the module (modprobe -r) and then re-load it to make it work. For the moment, I have no ethernet and reloading r8169 module has no effect (it tries to establish the connection with my box and fails).

    And why running kernel from kernel:stable?

    Module r8168 not found in directory /lib/modules/5.0.0-4.g6bc6477-default
    The answer is : I have no idea about it and I don't even understand your question because my degree of expertise is too low. I would be glad to be provided with some stuff to read...

    Now here are the outputs you asked me for :

    Code:
    erik@linux-r13d:/usr/bin> sudo zypper se -s r8168
    [sudo] Mot de passe de root : 
    Chargement des données du dépôt...
    Lecture des paquets installés...
    
    S  | Nom                         | Type          | Version                          | Architecture | Dépôt             
    ---+-----------------------------+---------------+----------------------------------+--------------+-------------------
       | r8168                       | paquet source | 8.046.00-61.44                   | noarch       | home:Sauerland    
       | r8168                       | paquet source | 8.045.08-4.31                    | noarch       | Packman Repository
    v  | r8168-blacklist-r8169       | paquet        | 8.046.00-61.44                   | x86_64       | home:Sauerland    
    i+ | r8168-blacklist-r8169       | paquet        | 8.045.08-4.31                    | x86_64       | Packman Repository
    v  | r8168-blacklist-r8169       | paquet        | 8.045.08-4.31                    | i586         | Packman Repository
       | r8168-debugsource           | paquet        | 8.045.08-4.31                    | x86_64       | Packman Repository
       | r8168-debugsource           | paquet        | 8.045.08-4.31                    | i586         | Packman Repository
    v  | r8168-kmp-default           | paquet        | 8.046.00_k5.0.0_4.g6bc6477-61.44 | x86_64       | home:Sauerland    
    i+ | r8168-kmp-default           | paquet        | 8.045.08_k4.20.13_1-4.31         | x86_64       | Packman Repository
    v  | r8168-kmp-default           | paquet        | 8.045.08_k4.20.13_1-4.31         | i586         | Packman Repository
       | r8168-kmp-default-debuginfo | paquet        | 8.045.08_k4.20.13_1-4.31         | x86_64       | Packman Repository
       | r8168-kmp-default-debuginfo | paquet        | 8.045.08_k4.20.13_1-4.31         | i586         | Packman Repository
       | r8168-kmp-pae               | paquet        | 8.045.08_k4.20.13_1-4.31         | i586         | Packman Repository
       | r8168-kmp-pae-debuginfo     | paquet        | 8.045.08_k4.20.13_1-4.31         | i586         | Packman Repository
    I assume there could be a conflict between sauerland and packman versions ??? How and why could I download both of them ? It is enough to mess my configuration, is'nt it ?

    Code:
    erik@linux-r13d:~> zypper lr -d
    #  | Alias                               | Nom                            | Activé | Vérification GPG | Rafraichir | Priorité | Type   | URI                                                                               | Service
    ---+-------------------------------------+--------------------------------+--------+------------------+------------+----------+--------+-----------------------------------------------------------------------------------+--------
     1 | download.opensuse.org-non-oss       | Dépôt principal (NON-OSS)      | Oui    | (r ) Oui         | Oui        |   99     | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/                             |        
     2 | download.opensuse.org-oss           | Dépôt principal (OSS)          | Oui    | (r ) Oui         | Oui        |   99     | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/                                 |        
     3 | download.opensuse.org-tumbleweed    | Dépôt principal de mise à jour | Oui    | (r ) Oui         | Oui        |   99     | rpm-md | http://download.opensuse.org/update/tumbleweed/                                   |        
     4 | http-download.opensuse.org-ac34bfc5 | Kernel:stable                  | Oui    | (r ) Oui         | Oui        |   99     | rpm-md | http://download.opensuse.org/repositories/Kernel:/stable/standard/                |        
     5 | http-download.opensuse.org-cacc449d | home:Sauerland                 | Oui    | (r ) Oui         | Oui        |   99     | rpm-md | http://download.opensuse.org/repositories/home:/Sauerland/Kernel_stable_standard/ |        
     6 | http-ftp.uni-erlangen.de-7bae3be0   | Packman Repository             | Oui    | (r ) Oui         | Oui        |   99     | rpm-md | http://ftp.uni-erlangen.de/pub/mirrors/packman/suse/openSUSE_Tumbleweed           |        
     7 | http-opensuse-guide.org-d587631f    | libdvdcss repository           | Oui    | (r ) Oui         | Oui        |   99     | rpm-md | http://opensuse-guide.org/repo/openSUSE_Tumbleweed/                               |        
     8 | openSUSE-20190301-0                 | openSUSE-20190301-0            | Oui    | (r ) Oui         | Non        |   99     | rpm-md | cd:/?devices=/dev/disk/by-id/ata-MATSHITADVD-RAM_UJ8G6_H092_008514                |        
     9 | repo-debug                          | openSUSE-Tumbleweed-Debug      | Non    | ----             | ----       |   99     | NONE   | http://download.opensuse.org/debug/tumbleweed/repo/oss/                           |        
    10 | repo-source                         | openSUSE-Tumbleweed-Source     | Non    | ----             | ----       |   99     | NONE   | http://download.opensuse.org/source/tumbleweed/repo/oss/                          |
    Code:
    erik@linux-r13d:~> uname -a
    Linux linux-r13d 5.0.0-4.g6bc6477-default #1 SMP Mon Mar 4 06:46:14 UTC 2019 (6bc6477) x86_64 x86_64 x86_64 GNU/Linux
    Thanks again.

    Erik

  8. #8
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,662
    Blog Entries
    14

    Default Re: installed packages can't be launched

    The problem is not with the packman packages, it's with your repos. You have two kernel related repos active, the packman packages are built against TW's current kernel 4.20.13-1-default .
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  9. #9
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,889

    Default AW: installed packages can't be launched

    i+ | r8168-kmp-default | paquet | 8.045.08_k4.20.13_1-4.31 | x86_64 | Packman Repository
    Linux linux-r13d 5.0.0-4.g6bc6477-default #1 SMP Mon Mar 4 06:46:14 UTC 2019 (6bc6477) x86_64 x86_64 x86_64 GNU/Linux
    I marked it bold.
    You are running an kernel from the Repo No. 4 (kernel:stable) but your installed kernel-module for the rtl8168 is from Repo No. 6 (Packman Repo). This is build for the kernel shipped with Tumbleweed. see the difference in my marked Quotes.

    Solution:
    Delete Repo kernel:stable and Sauerland:kernel-stable and switch to the kernel from Tumbleweed and Packman:
    As root:
    Code:
    zypper rr Kernel:stable
    zypper rr home:Sauerland
    zypper dup --allow-vendor-change
    zypper dup --from http://ftp.uni-erlangen.de/pub/mirrors/packman/suse/openSUSE_Tumbleweed
    Reboot

  10. #10
    Join Date
    May 2017
    Location
    Reunion Island
    Posts
    33

    Default Re: installed packages can't be launched

    @Knurpht & @Sauerland : thanks to both of you, I have learned something. Still a lot to learn...

    @Sauerland : I applied the prescription. My installation is much cleaner now. Unfortunately it did'nt change anything for my ethernet connection. After reboot I deleted all packages related to r8168, then I reinstalled them, but neither with r8169 alone (and not blacklisted) nor with r8169 blacklisted to favour r8168 and r8168 installed I can get my ethernet connection to work.

    BUT ...

    Code:
    erik@linux-r13d:~> sudo modprobe r8168
    modprobe: FATAL: Module r8168 not found in directory /lib/modules/5.0.0-4.g6bc6477-default
    Obviously modprobe is looking into the wrong directory. In 'modules' I have :
    • 4.20.13-1-default
    • 5.0.0-4.g6bc6477-default

    I assume the later was installed from repo "stable" and not deleted. Now why is modprobe looking into this directory ? Just because its version number is higher ? May I delete it or is there something cleaner to do ?

    Thanks again

    Erik

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •