Updating system broke chromium, help me figure out which package causes it?

[nathanvy]

System: Fedora 16 running kernel 3.6, Gnome 3/Shell (or whatever the hell it's called)

I recently installed a bunch of updates and now I get the "Aw Snap" on every. single. page. Every page. I submitted a bug report for chromium but as we all know Google's support is awful so I expect that to go nowhere (also it's not really chromium's fault; one of the fedora packages broke my system)

So here's a rundown of what happened:

1. Chromium working fine
2. Ran "Software Update" which I assume is just a frontend for yum
3. One of the packages "was from an untrusted source" and needed manual confirmation and root password to install
4. Tried for hours to figure out which package it was, but there was no way to tell which package.
5. Eventually got frustrated and clicked Install
6. System needed to restart because one update was latest kernel
7. Browser now gets "Aw Snap" error on every single page, nothing can be done
8. --enable-logging and --v=1 do not produce log files for chromium
9. Booting older kernel does not help

I am seriously at a loss here. I would assume that the offending package was a fix for the Java 0day that was recently released, as I did see something about CVE-something-something in the package list.

However, as I mentioned there was no way to tell which package was the untrusted one.

Now I can't use my laptop until I figure this out, or perhaps go back to windows or something.

Please help me figure out which package is causing these problems!

[PatMcLJr]

me too

messages

[  584.359661] chromium-browse[2823]: segfault at 122 ip 00007f9c4b12dde3 sp 00007f9c2ffd1bb0 error 6 in chromium-browser[7f9c49f51000+474f000]

[PabloTwo]

I run F16.x86_64. I do not use Gnome. I use google-chrome-stable from the Google repos, not chromium.
I am experiencing no problems using google-chrome-stable-24.0.1312.52-175374.x86_64, latest version.

I use yum/rpm at the command line only. I never use a GUI package manager as they are all garbage.
Using yum at the command line keeps you fully informed as to what is going on.

If you had done a "sudo yum update", and one or more of the packages were not signed, yum would have halted the install and reported which package was not signed. Because a package is not signed does not automatically mean it is evil or the culprit behind your current problem. It does mean that it is coming from a repo which you do not have the gpg signing key installed for that repo (some repos do not use signing keys and thus the rpm packages from them are not signed).

You can get a list of your currently enabled repos using: yum repolist

You can see what repos you have gpg signing keys installed for using: ls /etc/pki/rpm-gpg/

Compare the two outputs and you should be able to deduce which enabled repo you have that has no signing key installed. From that, you should be able to determine with package(s) installed unsigned.

Run as root, the command "yum history list" will give a listing of several of your most recent yum transactions, with the first column being the ID number of the transaction. To examine the details of any transaction, and see what was installed/erased/updated, use: yum history info <transaction_number>

If there was a package installed that had "CVE" as part of the package name, then use: rpm -qa | grep -i cve

to identify it (would also show up in your "yum history" searches.

I really have no clue as to why your chromium is now giving you those "Awe Snap" messages. I've never encountered anything like that in google-chrome-stable.

---------- Post added at 11:21 AM ---------- Previous post was at 11:18 AM ----------

If your chromium repo will support it, you could also try:

yum downgrade chromium (or whatever the actual package name is)

to revert back to the previous version.

[nathanvy]

Thanks Pablo

I ended up switching to F18 (didn't realize it was out now) and the problem seems to have evaporated during the update process, but I appreciate the advice all the same!