Chromium update crash

[Ɗα√ϵς§]

OK - Chromium finally crashed and downgrading immediately to nvidia-280 brought it back to life. I've not even rebooted, just restarted X (which did not run), rmmod nvidia, modprobe nvidia then restarted X again, and it's all good.

Not sure what I think about comments about who is in the wrong here, chromium or nvidia. chromium is open-source, nvidia is not, therefore can the developers of chromium see what's changed in the module that causes the problem? The only justification I can see for keeping nvidia-285 is if it fixed other things or made other cards work. Maybe it's time for a legacy split-off again?

[JohnW_57]

http://www.nvnews.net/vbulletin/showthread.php?p=2487046

Fixed a bug causing some applications to hang on exit  was the reason
to update to nvidia-285.
There was a application in Broken packages section with that issue.
That issue is indeed solved.

Did just a suggestion on the forum:  http://www.pclinuxos.com/forum/index.php/topic,98325.0.html
to avoid such problems in the future (hopefully).

JohnW

[Georgetoon]

All this Chromium talk has me using it more.  Really nice.  Only thing is, when I launch it, KDE Wallet opens and asks for passwords for some reason.

[JohnW_57]

All this Chromium talk has me using it more.  Really nice.  Only thing is, when I launch it, KDE Wallet opens and asks for passwords for some reason.

http://www.pclinuxos.com/forum/index.php/topic,98267.0.html   

JohnW

[Texstar]

All this Chromium talk has me using it more.  Really nice.  Only thing is, when I launch it, KDE Wallet opens and asks for passwords for some reason.

I just clicked next next next and it has never asked me again.

[Georgetoon]

All this Chromium talk has me using it more.  Really nice.  Only thing is, when I launch it, KDE Wallet opens and asks for passwords for some reason.

I just clicked next next next and it has never asked me again.

Where's "next?" i don't see it in my KDE wallet.

[Texstar]

I don't know. When it popped up in Chromium I clicked through it without entering any data.

[Georgetoon]

I don't know. When it popped up in Chromium I clicked through it without entering any data.

Well, the KDE wallet window just popped up again. I'm only given "Open" and "Cancel" as choices.

EDIT - Jut went into "Configure Your Desktop" and disabled the KDE Wallet subsystem.  This will probably do the trick. I don't use KDE Wallet.

[edday]

Here it is December.  Chromium has been working fine on my ASUST1000 netbook with an intel graphics chip.  Until a few days ago when I did an update to the system and flash started crashing.  Then, last evening I shut the computer down.  When I started it up again today, chromium would not start.  Trying to start from command line I get a "segmentation fault". 

Is there a solution to this as yet?  Chromium is my favorite browser.  Firefox does work, but flash doesn't work in it either, but at least it will open.

[CaptainSarcastic]

Today I started having the same issue - ran an update last night and this morning Iron wouldn't launch.  Ran it from a terminal and found I was getting a segfault.  Before searching the forums I tried using Bleachbit to clear the cache and kill the current session - no joy.  Reinstalled using Synaptic - no joy.  Installed Chromium, and it won't launch, either - it just generates a one line segfault with no additional details.

Am running current Nvidia drivers here, and both Firefox and Opera are running just fine.

Here's the error Iron is generating:

[captainsarcastic@localhost ~]$ iron-browser
./iron: /usr/lib/libz.so.1: no version information available (required by ./iron)
./iron: /usr/lib/libz.so.1: no version information available (required by ./iron)
/usr/lib/iron-browser/iron: /usr/lib/libz.so.1: no version information available (required by /usr/lib/iron-browser/iron)
/usr/lib/iron-browser/iron: /usr/lib/libz.so.1: no version information available (required by /usr/lib/iron-browser/iron)
Segmentation fault

[uggy]

Captain Sarcastic Can you try something.

In synaptic, do a complete removal of prelink, it will take a couple of minutes.

Dont reboot, just see if Iron will then work.

[CaptainSarcastic]

Captain Sarcastic Can you try something.

In synaptic, do a complete removal of prelink, it will take a couple of minutes.

Dont reboot, just see if Iron will then work.

That did it!  Now I'm just mildly concerned about having both Iron and Chromium installed, but removing prelink made Iron fire right up again.

Thank you, uggy!

[Vorteggs]

The opposite here in KDE.

I had Chromium segmentation faults but it seems recent updates fixed the problem (to say two or three weeks ago).

[uggy]

Captain Sarcastic Can you try something.

In synaptic, do a complete removal of prelink, it will take a couple of minutes.

Dont reboot, just see if Iron will then work.

That did it!  Now I'm just mildly concerned about having both Iron and Chromium installed, but removing prelink made Iron fire right up again.

Thank you, uggy!

CaptainSarcastic, Glad you got it sorted.

Vortex, I think there are different issues here, I & others had problems with Chromium, Iron & KDE crashes etc, after nvidia updates. Prelink runs itself in background, then comp goes potty! 

[mrreality13]

I Had the issue but followed this - and solved it

Captain Sarcastic Can you try something.

In synaptic, do a complete removal of prelink, it will take a couple of minutes.

Dont reboot, just see if Iron will then work.