[SOLVED] LastPass 1.73.3 Crashing Chromium 12.0.7.18?

bryanmoore · #1 9th July 2011, 01:36 PM

Is anyone else running into the problem with the latest LastPass extension (1.73.3) for Chromium? It works fine on my Ubuntu install, but crashes Chromium 12.0.718.0 (0) on my Fedora 15 (Lovelock) install. I have a support request in to LastPass, but I was hoping someone here may actually be able to help.

Any ideas?

bike_head · #2 9th July 2011, 03:28 PM

Yes I get this too for fresh installs of F15 and chrome. The problem goes away if you turn selinux off "setenforce 0". I tried using audit2allow to create a new selinux policy to allow the failure, but I didn't have any success. The strange thing is I just upgraded another machine from F14 to F15 and it doesn't exhibit this problem.

bryanmoore · #3 10th July 2011, 01:00 AM

Hmm... didn't even think SELinux could be the problem; any idea what it's blocking? Also, I wonder if there's a better/more elegant solution to have the 'setenforce 0' occur at startup than a script.

By the forum's silence, can I assume disabling SELinux is actually the best option for me? That kind of seems like circumcising with an axe...

jj97403 · #4 15th July 2011, 04:44 PM

I have the same problem. Lastpass extensions always immediately crashes on 32 bit Fedora 15 w/Chrome. Please post if there is a simple workaround.

bryanmoore · #5 15th July 2011, 06:39 PM

Quote:

Originally Posted by jj97403

I have the same problem. Lastpass extensions always immediately crashes on 32 bit Fedora 15 w/Chrome. Please post if there is a simple workaround.

Sorry, I should have marked this as "solved" because the problem no longer persists when SELinux is disabled. Apparently, as usual, SELinux seems to be the root of the problem because of its restrictive properties.

cheerio158 · #6 24th July 2011, 02:32 PM

I have the same problem on my EeePC 701 (chromium-12.0.742.91-1.fc14.i686) for some time now. It crashes shortly after the Chromium window appears. However, the x86_64 build works fine on my desktop and laptop.

I verified the integrity of all the installed packages on my EeePC using rpm so I am sure that Chromium is the problem. I since gave up up Chromium and use Chrome instead.

However, I just built a F14 i686 live USB and Chromium is broken on that too! I can't use Chrome because Chrome's installation does something funky and causes the the live image build process to fail.

In both cases, SELinux is disabled.