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

Thread: [openSUSE13.2]chromium: symbol lookup error: after zypper up

  1. #1

    Default [openSUSE13.2]chromium: symbol lookup error: after zypper up


    Hello, I don't use Chromium very much. Actually I detest it's UI. But I
    prefer to use a separate browser to do any "social networking" from the one
    I frequently close completely when I'm done with an on-line banking
    transaction. (besides, this way Firefox never even gets a Facebook cookie,
    for other sites to track me with). But it used to work under openbox
    on my opensuse 13.2 system... {Um, if it matters I boot to console, and use
    startx when ready to deal with the GUI.}

    This morning I did this from a root login:
    Code:
    zypper ref
    zypper up
    There were no reported errors.

    Though I noticed something that I don't remember zypper as doing before 13.2?

    The first thing it did was to list 760 package updates that wouldn't be
    installed. I checked several of them with "zypper if" and I couldn't find
    one that wasn't "up to date". So I wonders why/"how long" zypper reports the updates
    it doesn't need this way? But that's probably better handled in a separate thread.

    Anyway, this update upgraded the boot kernel IE:

    vmlinuz-3.16.7-21-desktop =-> vmlinuz-3.16.7-24-desktop

    I rebooted into the new kernel. Fired up openbox, And proceeded to check
    my mail, run Firefox && Opera {for different purposes} And every thing
    seemed to be working. Until I noticed an email notice that someone had
    posted something on my timeline.

    So I switched to desktop area where I do any social networking, and hit my
    keyboard shortcut. But Chromium didn't start. After a second try, I opened
    ~/.config/openbox/rc.xml with less, to check that the keybinding was still
    set properly.{and to remind myself whether opensuse was one of the distro's
    where I use Chromium for that instead of google chrome...}

    The next step was to try to start chromium from the bash command line:
    Code:
    JtWdyP -> /home/jtwdyp
    > chromium
    /usr/lib64/chromium/chromium: symbol lookup error: /usr/lib64/chromium/lib/libmedia.so: undefined symbol: _ZN18third_party_ffmpeg15InitializeStubsERKSt3mapINS_11StubModulesESt6vectorISsSaISsEESt4lessIS1_ESaISt4pairIKS1_S4_EEE
    JtWdyP -> /home/jtwdyp
    >
    So I opened a root shell and:
    Code:
    /home/filEshuttlE
    UnderTree=-> zypper if chromium
    Loading repository data...
    Reading installed packages...
    
    
    Information for package chromium:
    ---------------------------------
    Repository: openSUSE-13.2-Oss
    Name: chromium
    Version: 38.0.2125.104-1.1
    Arch: x86_64
    Vendor: openSUSE
    Installed: Yes
    Status: up-to-date
    Installed Size: 219.3 MiB
    Summary: Google's opens source browser project
    Description:
    Chromium is the open-source project behind Google Chrome. We invite you to join us in our effort
    to help build a safer, faster, and more stable way for all Internet users to experience the web,
    and to create a powerful platform for developing a new generation of web applications.
    /home/filEshuttlE
    UnderTree=->
    Does this mean that Version: 38.0.2125.104-1.1 is borked. Or do I have
    other problems???

    I note that a startpage search found a very similar thread, that was moved to
    TUMBLEWEED. But I'm using 13.2:
    https://forums.opensuse.org/showthre...56#post2722056

    --
    JtWdyP


  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,773
    Blog Entries
    3

    Default Re: [openSUSE13.2]chromium: symbol lookup error: after zypper up

    Here, chromium is doing fine, though not my main browser.

    Quote Originally Posted by jtwdyp View Post
    Does this mean that Version: 38.0.2125.104-1.1 is borked. Or do I have
    other problems???
    I think it means that your system is borked or your repos are borked.

    Checking what I have installed, I have
    chromium 44.0.2403.89-38.1
    chromium-ffmpeg 44.0.2403.80-44.1

    Here's a question that you should ask yourself --
    How is it possible that you ran updates and got the latest kernel, but still have an older version of chromium?

    My guess is that you have incompatible versions of "chromium" and "chromium-ffmpeg".
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  3. #3
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,387
    Blog Entries
    2

    Default Re: [openSUSE13.2]chromium: symbol lookup error: after zypper up

    If you think you have a bindings or configuration issue, you can try force re-installing the app, ie
    Code:
    zypper in -f chromium
    TSU

  4. #4

    Default Re: [openSUSE13.2]chromium: symbol lookup error: after zypper up


    It would appear that on Aug 16, nrickert did say:

    > Here, chromium is doing fine, though not my main browser.
    >
    > jtwdyp;2724224 Wrote:
    > > Does this mean that Version: 38.0.2125.104-1.1 is borked. Or do I have
    > > other problems???

    >
    > I think it means that your system is borked or your repos are borked.
    >
    > Checking what I have installed, I have
    > chromium 44.0.2403.89-38.1
    > chromium-ffmpeg 44.0.2403.80-44.1
    >
    > Here's a question that you should ask yourself --
    > How is it possible that you ran updates and got the latest kernel, but
    > still have an older version of chromium?


    Are you running opensuse 13.2?

    From which repo did you get chromium 44.0.2403.89-38.1 ?
    my chromium 38.0.2125.104-1.1 comes from openSUSE-13.2-Oss
    And zypper says it's up to date.

    As are my:
    chromium-pepper-flash 18.0.0.209-1.1 from packman.links2linux.de
    and
    chromium-ffmpeg 44.0.2403.89-44.1 from packman.links2linux.de

    All of which specify Arch: x86_64 Which this old HP Pavilion is.

    I thought maybe I needed to get chromium from packman to,
    But:
    Code:
    zypper if -r packman.inode.at-suse  chromium
    gives me same exact output, except it refers to the
    "openSUSE-13.2-Oss" repo as "@System"

    From which I conclude that packman itself doesn't have the chromium browser package.
    And which brings me back to the question:
    From which repo did you get chromium 44.0.2403.89-38.1 ?

    > My guess is that you have incompatible versions of "chromium" and
    > "chromium-ffmpeg".


    Yeah, I suspect so. But don't know from where to get chromium 44
    Nor do I know from where I could now get chromium-ffmpeg 38

    I just noticed that you said you have:

    chromium-ffmpeg 44.0.2403.80-44.1 from ???
    Where as mine is: ^
    chromium-ffmpeg 44.0.2403.89-44.1 from packman.links2linux.de
    ^
    So maybe it's the chromium-ffmpeg 44.0.2403.89-44.1 that's borked?

    --
    JtWdyP


  5. #5

    Default Re: [openSUSE13.2]chromium: symbol lookup error: after zypper up


    It would appear that on Aug 16, tsu2 did say:

    > If you think you have a bindings or configuration issue, you can try
    > force re-installing the app, ie
    >
    > Code:
    > --------------------
    > zypper in -f chromium
    > --------------------


    I think it's more likely an incompatibility between
    chromium 38.0.2125.104-1.1 & chromium-ffmpeg 44.0.2403.89-44.1

    Though zypper says both are up to date.

    Though your suggestion makes me wonder about an Off Topic question...

    IF "zypper in -f $PackageName" will redo the configuration files?
    Then is there a package I could reinstall that way on my laptop
    to force the re-detection of the built in hardware sound system?

    --
    JtWdyP


  6. #6
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,773
    Blog Entries
    3

    Default Re: [openSUSE13.2]chromium: symbol lookup error: after zypper up

    Quote Originally Posted by jtwdyp View Post
    Are you running opensuse 13.2?
    Yes.

    From which repo did you get chromium 44.0.2403.89-38.1 ?
    my chromium 38.0.2125.104-1.1 comes from openSUSE-13.2-Oss
    And zypper says it's up to date.
    It is in the update-repo: openSUSE-13.2-Update

    Maybe you don't have that enabled. But that's a puzzle, because that's where kernel 3.16.7-24 can be found, and you indicated that you did update to that kernel. And, yes, I'm using x86_64.

    But don't know from where to get chromium 44
    From the update repo (update-oss, not update-nonoss).

    Nor do I know from where I could now get chromium-ffmpeg 38
    I don't think that's anywhere. It was originally on packman, but packman now has only the newer version.

    If you want to stick with chromium 38, then uninstall chromium-ffmpeg and install chromium-ffmpegsumo in its place, though that won't have all of the multimedia support.

    I just noticed that you said you have:

    chromium-ffmpeg 44.0.2403.80-44.1 from ???
    I did not provide "from" information. But it is from packman.

    chromium-ffmpeg 44.0.2403.89-44.1 from packman.links2linux.de
    No, it's just a version incompatibility problem
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  7. #7
    Join Date
    Sep 2008
    Posts
    2,997

    Default Re: [openSUSE13.2]chromium: symbol lookup error: after zypper up

    I think there are 2 possibilities, #1 you don't have the update repo enabled or it's somehow misconfigured maybe a lower priority from the install DVD (if you have the install DVD as a repo remove it it's obsolete), #2 you have a bad repository (a factory or 13.1 repo)

    post the output of zypper lr -d

  8. #8

    Default Re: [openSUSE13.2]chromium: symbol lookup error: after zypper up


    It would appear that on Aug 16, nrickert did say:

    > jtwdyp;2724262 Wrote:
    > > Are you running opensuse 13.2?

    > Yes.
    >
    > > From which repo did you get chromium 44.0.2403.89-38.1 ?
    > > my chromium 38.0.2125.104-1.1 comes from openSUSE-13.2-Oss
    > > And zypper says it's up to date.

    >
    > It is in the update-repo: openSUSE-13.2-Update
    >
    > Maybe you don't have that enabled. But that's a puzzle, because that's
    > where kernel 3.16.7-24 can be found, and you indicated that you did
    > update to that kernel. And, yes, I'm using x86_64.


    I think I understand what I did to myself now...

    It has to do with repo priorities. I forgot I'd experimented with them.
    Then I upgraded from 13.1 to 13.2 using zypper dup.

    I'd set packman to a lower priority number than anything else.
    Then I'd set the opensuse, oss and non-oss repos in between packman, and
    the rest of the repos. But I seem to have failed to have included the
    update repos in that priority switch.

    That didn't seem to cause any trouble while I was running "13.1". Likely
    because "zypper up" doesn't change vendor. But when I did the zypper dup to
    "13.2" some of the packages that should have been from repo-update-oss,
    or repo-update-non-oss. were probably switched to the repo-oss, or
    repo-non-oss repos, due to their lower priority...

    If I'm right, it's a tribute to the robustness of opensuse that Chromium is
    {so far} the only obvious casualty of such a borked repo config.

    And the question is how to fix it.

    I've already corrected the priority of the update repos. But I think I'm
    going to have to do some repo switching to avoid future such problems.

    I think that if I'm going to fix it with zypper, It will take three dups:

    Code:
    zypper dup --from repo-update-non-oss
    zypper dup --from repo-update-oss
    zypper dup --from packman.inode.at-suse
    I think the order of the dups is important. And I think I should probably
    run them from the console. As it's quite possible that X could have
    problems in the middle of this.

    And I think I'd like a bit of sanity checking on my reasoning, and
    especially my proposed solution.

    --
    JtWdyP


  9. #9
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,773
    Blog Entries
    3

    Default Re: [openSUSE13.2]chromium: symbol lookup error: after zypper up

    After fixing the priorities (give the update repos the same priority as the corresponding main repo), try doing
    Code:
    zypper patch
    That should apply any patches that you may have missed.

    And a note on your "zypper dup" plans -- you can add the "-D" option to do a dry run, and just see what will be done.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  10. #10
    Join Date
    Sep 2008
    Posts
    2,997

    Default Re: [openSUSE13.2]chromium: symbol lookup error: after zypper up

    Quote Originally Posted by jtwdyp View Post
    It would appear that on Aug 16, nrickert did say:

    > jtwdyp;2724262 Wrote:
    > > Are you running opensuse 13.2?

    > Yes.
    >
    > > From which repo did you get chromium 44.0.2403.89-38.1 ?
    > > my chromium 38.0.2125.104-1.1 comes from openSUSE-13.2-Oss
    > > And zypper says it's up to date.

    >
    > It is in the update-repo: openSUSE-13.2-Update
    >
    > Maybe you don't have that enabled. But that's a puzzle, because that's
    > where kernel 3.16.7-24 can be found, and you indicated that you did
    > update to that kernel. And, yes, I'm using x86_64.


    I think I understand what I did to myself now...

    It has to do with repo priorities. I forgot I'd experimented with them.
    Then I upgraded from 13.1 to 13.2 using zypper dup.

    I'd set packman to a lower priority number than anything else.
    Then I'd set the opensuse, oss and non-oss repos in between packman, and
    the rest of the repos. But I seem to have failed to have included the
    update repos in that priority switch.

    That didn't seem to cause any trouble while I was running "13.1". Likely
    because "zypper up" doesn't change vendor. But when I did the zypper dup to
    "13.2" some of the packages that should have been from repo-update-oss,
    or repo-update-non-oss. were probably switched to the repo-oss, or
    repo-non-oss repos, due to their lower priority...

    If I'm right, it's a tribute to the robustness of opensuse that Chromium is
    {so far} the only obvious casualty of such a borked repo config.

    And the question is how to fix it.

    I've already corrected the priority of the update repos. But I think I'm
    going to have to do some repo switching to avoid future such problems.

    I think that if I'm going to fix it with zypper, It will take three dups:

    Code:
    zypper dup --from repo-update-non-oss
    zypper dup --from repo-update-oss
    zypper dup --from packman.inode.at-suse
    I think the order of the dups is important. And I think I should probably
    run them from the console. As it's quite possible that X could have
    problems in the middle of this.

    And I think I'd like a bit of sanity checking on my reasoning, and
    especially my proposed solution.

    --
    JtWdyP
    no no don't do that many dup's, you'll break something, if your system is up to 13.2 only do a dup once for packman, post/check your repo's, if you upgraded from 13.1 you could still have some old 13.1 repo's.

    ps I'm not sure the dup command works like that, for some repo's maybe.
    run zypper lr -d
    zypper will give each repo a number starting from 1 to the number of repo's.
    zypper dup --from <number for the repo you want to dup>

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
  •