severe chromium crash on tumbleweed

on my tumbleweed with kde 4.9.3 if I launch, also from konsole, chromium the web browser, it crash and the desktop restart as if I press the ctrl>alt>backspace-twice keystroke combination, I tried on my 12.2 with kde 4.9.3 and everything go fine, does it happent to you too??
thnx, ciao, pier:)

Nope, but I did experience this with google-earth a while ago. Installing Mesa-32bit “solved” it. “Solved” since I think it’s a bug. A true 64bit Chrome should not need Mesa-32bit

On 11/18/2012 12:26 AM, pier andreit wrote:
>
> on my tumbleweed with kde 4.9.3 if I launch, also from konsole, chromium
> the web browser, it crash and the desktop restart as if I press the
> ctrl>alt>backspace-twice keystroke combination, I tried on my 12.2 with
> kde 4.9.3 and everything go fine, does it happent to you too??
> thnx, ciao, pier:)
>
>
I got that (months ago) and had to reinstall Nvidia to fix it. I don’t
know why.


Regards
swerdna

thnx:-) but it didn’t work, Mesa-32bit was already installed and I installed also the mesa devel packages, but the crash is still there, I’m reading only now the swerdna suggestion too, I will try to reinstall the nvidia driver in the hardway ofcourse:-))

I reinstalled 304.51 nvidia driver, using SANDI, option D, it didn’t work :slight_smile:

with nouveau chromium works well, so, I don’t know if I “really” reinstalled the nvidia driver…, using SANDI I followed the first two instructions and didn’t read results…:-)) I used LNWHW but something failed so I’m with nouveau now, it isn’t so bad at the end:-))

On 11/18/2012 09:56 PM, pier andreit wrote:
>
> pier_andreit;2504578 Wrote:
>> I reinstalled 304.51 nvidia driver, using SANDI, option D, it didn’t
>> work :-)with nouveau chromium works well, so, I don’t know if I “really”
> reinstalled the nvidia driver…, using SANDI I followed the first two
> instructions and didn’t read results…:-)) I used LNWHW but something
> failed so I’m with nouveau now, it isn’t so bad at the end:-))
>
>
The current version of Nvidia driver (on their website) is 310.19. You
were trying 304.51

When I had my issue, I suspect it was because I had fallen behind the
times. And getting the new version and installing it IIRC was the answer
for me then, but that was a long time ago, hard to remember.


Regards
swerdna