Results 1 to 10 of 10

Thread: Firefox no longer working

  1. #1

    Default Firefox no longer working

    Hi
    Tubleweed VERSION_ID="20160307"/ default KDE desktop. Just upgraded this morning and now Firefox is not working any more. I only get the firefox window with the following text:"XML Parsing Error: undefined entity
    Location: chrome://browser/content/browser.xul
    Line Number 2646, Column 17: <image id="web-notifications-notification-icon" class="notification-anchor-icon" role="button"
    ----------------^"
    All other browsers (Chromium, Opera and Konqueror) are working.
    I went into Yast and reinstalled Firefox (version 45.0-2.1) with the same result. Then I went to yast again, deleted the existing Firefox browser and reinstalled it again with the same result. What is the matter with firefox?
    Cheers
    Uli

  2. #2

    Default Re: Firefox no longer working

    I tried a few more things. First here are the repos:
    Code:
    linux-top:~ # zypper lr
    # | Alias                               | Name         | Enabled | GPG Check | Refresh
    --+-------------------------------------+--------------+---------+-----------+--------
    1 | Mozilla                             | Mozilla      | Yes     | (r ) Yes  | Yes    
    2 | http-download.opensuse.org-12779cf9 | security     | Yes     | (r ) Yes  | Yes    
    3 | packman                             | packman      | Yes     | (r ) Yes  | Yes    
    4 | repo-debug                          | repo-debug   | Yes     | (r ) Yes  | Yes    
    5 | repo-non-oss                        | repo-non-oss | Yes     | (r ) Yes  | Yes    
    6 | repo-oss                            | repo-oss     | Yes     | (r ) Yes  | Yes    
    7 | repo-update                         | repo-update  | No      | ----      | Yes
    I changed the Mozilla repos' priority to 90 to make sure all of Mozilla's software items are coming from the same repo. A zypper dup resulted in
    Code:
    The following package is going to change vendor:
      libnsssharedhelper0  openSUSE -> obs://build.opensuse.org/mozilla
    Now I tried Firefox again and I get the following error message in the Firefox window:
    "XML Parsing Error: undefined entity
    Location: chrome://browser/content/browser.xul
    Line Number 470, Column 7: <menu id="context_tabViewMenu" label="&moveToGroup.label;"
    ------^"

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

    Default Re: Firefox no longer working

    I'd suggest you do it the other way round and dup to the oss (and packman as not to break multimedia) repo
    Code:
    sudo zypper dup --from 6 --from 3
    and remove the mozilla repo as firefox is updated in the oss repo regularly

    edit
    I'm on LEAP and am not having any Firefox issues, but that's the chance you take using a rolling distro

  4. #4

    Default Re: Firefox no longer working

    Thanks I_A your suggestion worked - Firefox is working now - although it is version 44 where I had the 45 which was in the Mozilla repo. The 44 version was working in Tumbleweed too. I have seen that on LEAP they recommend (for security) to upgrade to version 45. At this stage I didn't upgrade my LEAP computer because of this problem. Are you running the 44 or the 45 version? May be I wait a bit and see what others say. Hopefully when the update comes to Tumbleweed in the oss repo this problem does not occur again.
    One problem - amongst the from the command 'zypper dup --from 6 --from 3' selected packages for deletion was the xdm package and only after the computer crashed out of the gui the second time with this command I noticed and completed the command in runlevel 3.
    Cheers
    Uli

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

    Default Re: Firefox no longer working

    again I'm not on TW but afaik if you have any extra repos (like you have the mozilla and packman and security) you should not use zypper dup without the --from switch as you will end up with mixed up packages and errors, only use zypper dup on a TW that only has the oss and non-oss repo's, even adding packman will mess things up as packages with the same name but different functionalities exist on different repo's
    on systems with multiple repositories use zypper up as that will not do a vendor change and only update packages from the same repo.

    I'd suggest removing the mozilla repo as it has more packages then just firefox, a lot of Linux libraries depend on the mozilla networking packages and mixing repo's is a bad idea.

  6. #6

    Default Re: Firefox no longer working

    I had removed the Mozilla repo before writing the previous mail. I added it several years ago when the firefox browser used up too many resources (e.g. 80+%CPU) and the computer came to a standstill. There is an old thread about this here too.
    Packman has a tumbleweed repo and the security is for some tests I made with fail2ban etc. So I probably should put all the Tumbleweed repos on a lower priority and leave the security repo on 99.
    Cheers
    Uli

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

    Default Re: Firefox no longer working

    I don't think the priorities in Yast are used any more I could be wrong
    you don't have to remove a repo you are using just be aware that using zypper dup without the --from switch will download the latest version of a package no matter what repository it is in, this can brake multimedia as you could end-up with packages from the OSS repo, or if you have a lot of extra OBS repo's that are out of sync you can brake your system (like your Firefox issue), I'd say you should use
    zypper dup --from <insert oss repo #> --from <insert non-oss repo #> --from <insert packman repo #>
    where a repo # is the repositories number you can get by using zypper lr, for completeness sake if the repository list is like in your table above you should use
    zypper dup --from 6 --from 5 --from 3

  8. #8
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,503
    Blog Entries
    3

    Default Re: Firefox no longer working

    Quote Originally Posted by I_A View Post
    I don't think the priorities in Yast are used any more I could be wrong
    It seems to be mixed.

    As best I can tell, "zypper dup" honors the priorities. "zypper up" is going to be affected more by vendor, so unless the updates from both repos have the same vendor, the priorities won't matter so much.

    It looks as if "zypper patch" will apply patches regardless of the patch repo priority. Maybe it will also switch vendor -- I'll have to test that.

    And maybe kernel updates don't properly follow priority, perhaps because the updated kernel is an added package rather than a replacement (due to multi-version kernel support).

    This is based on my experience with Krypton (Tumblweed variant with different priorities), and on one system where I have enabled the update-test repo for Leap, but given it a priority of 101. Yast online update, and "zypper patch" want to install updates from the test repo. But "zypper up" doesn't -- except that it wants to install kernel updates. And zypper dup won't install updates from the test repo (except kernel updates).

    At present, I'm disabling the update-test repo before most updates, then re-enabling (so I can see what's coming down the pike).
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

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

    Default Re: Firefox no longer working

    As best I can tell, "zypper dup" honors the priorities. "zypper up" is going to be affected more by vendor, so unless the updates from both repos have the same vendor, the priorities won't matter so much.
    that would be the case if the package version numbers wore the same in those different repo's in that case zypper would get the one from the preferred repo, but as is often the case OBS repo's have newer packages and in that case using zypper dup without the --from switch would pull some packages from a 3rd repo and that could break something right?

    There is something I still don't understand about TW, TW does not have an update repo (it has but it's rarely used) how are packages in it's oss repo updated is it on a time table or as soon as an update is available it replaces the previous version, when will Firefox 45 land in TW's oss?

  10. #10
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,503
    Blog Entries
    3

    Default Re: Firefox no longer working

    Quote Originally Posted by I_A View Post
    that would be the case if the package version numbers wore the same in those different repo's in that case zypper would get the one from the preferred repo, but as is often the case OBS repo's have newer packages and in that case using zypper dup without the --from switch would pull some packages from a 3rd repo and that could break something right?
    It depends on how you are using the repos.

    For normal Tumbleweed, I give packman a lower priority number. That should prefer packages from packman when available there. And that mostly works. Occasionally a package is revered to the oss repo, probably because of a dependency requirement.

    Krypton is Tumbleweed with unstable KDE repos that have lower priority numbers. So it should prefer to install everything KDE from the unstable repos rather than the main repo. Usually this should not be a problem. It is when you install part of KDE from the unstable repos and part from the standard repo, that you could run into problems, particularly if the version numbers happen to be in the wrong order.

    There is something I still don't understand about TW, TW does not have an update repo (it has but it's rarely used) how are packages in it's oss repo updated is it on a time table or as soon as an update is available it replaces the previous version, when will Firefox 45 land in TW's oss?
    I think somebody makes an explicit decision to "publish" the new snapshot. I don't know the full details. But I surmise that the new versions are copied to the main repo, and the repo metadata is rebuilt to refer only to the new versions. Apparently (based on a factory mailing list message a while back), the old packages actually stay in the repo and are removed around 3 days later. I assume that's so somebody in the middle of doing an update when a new snapshot is published won't get unpleasant surprises.

    As for firefox. I'm guessing that it is already in unpublished factory, and we will see it when the current problems (the ones blocking 20160308) are fixed. It that takes too long, they might push it to the update repo (again, I'm guessing).
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

Posting Permissions

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