Chrome works fine for me. Have you looked into update of your choice server? On April 25, 2014 9:56:18 PM PDT, C wrote:

On Fri, Apr 25, 2014 at 7:20 PM, C wrote:

...

Seems like I've got a repeatable problem after updating to KDE4.13 (update from KDE 4.12 to 4.13 with a downgrade on the branding).

I can trigger the crash by launching Chromium (any version from 31 through 33 - I tried 31, 32 and 33, wiping ~/.config/chromium each time to force a clean start). As soon as I launch Chromium, the X server dies and leaves this line in /var/log/messages:

2014-04-25T19:10:33.176822+02:00 linux-w1b9 kdm[600]: X server for display :0 terminated unexpectedly

No other error is showing up in messages, Xorg.0.log and so on (at least not that I can see).

Firefox 29.0 works fine.. Chromium is the only app so far that I've found to trigger the X Server crash after upgrading.

Any tips on finding a way to nail this one down?

Just for "fun" I installed Chrome (next to Chromium) and tried running... instantly on launch of Chrome (exactly the same as Chromium), X crashes with a "terminated unexpectedly" in the messages log.

Still no clue what's triggering this.....

C. -- openSUSE 13.1 x86_64, KDE 4.13 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Dnia sobota, 26 kwietnia 2014 07:07:14 C pisze:

This whole thing was rather odd. The KDE4.13 update didn't include a new kernel (I check the update before I apply). It was only a KDE4 update I triggered... but somehow something tweaked the NVidia driver in such a way that only Chrome and Chromium would trigger an X crash.

In the time when KDE 4.13 showed up in KDE:Current, there was also Xserver update (xorg-x11-server package) in Update repository. And this could cause issue with NVidia blob driver. Not the KDE update itself. -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member GPG: 5FCE 7241 B3B9 32FD 455B C30E 42D6 6C88 9E83 7C3D

On 26/04/14 20:14, C wrote:

On Sat, Apr 26, 2014 at 12:09 PM, Mariusz Fik wrote:

...

Dnia sobota, 26 kwietnia 2014 07:07:14 C pisze:

...

This whole thing was rather odd. The KDE4.13 update didn't include a new kernel (I check the update before I apply). It was only a KDE4 update I triggered... but somehow something tweaked the NVidia driver in such a way that only Chrome and Chromium would trigger an X crash. In the time when KDE 4.13 showed up in KDE:Current, there was also Xserver update (xorg-x11-server package) in Update repository. And this could cause issue with NVidia blob driver. Not the KDE update itself. I just spotted that here... about 1 minute after you sent your email :-)

Yes, the xorg package was the culprit that caused my odd problems with Chromium.

C.

I think that it is fair to say that people ought to be made aware of this problem with the nVidia driver as a result of upgrading to KDE 4.13. My wife loves to play backgammon (gnubg) but it stopped 'working' when she tried to play it this morning. I remembered what you said re recompiling the nVidia driver and after I did this gnubg was back in business. She is again a happy little vegemite :-) . BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 27/04/14 14:01, John Andersen wrote:

On April 26, 2014 8:49:09 PM PDT, Basil Chupin wrote:

...

...

On Sat, Apr 26, 2014 at 12:09 PM, Mariusz Fik wrote:

...

Dnia sobota, 26 kwietnia 2014 07:07:14 C pisze:

...

This whole thing was rather odd. The KDE4.13 update didn't include a new kernel (I check the update before I apply). It was only a KDE4 update I triggered... but somehow something tweaked the NVidia driver in such a way that only Chrome and Chromium would trigger an X crash. In the time when KDE 4.13 showed up in KDE:Current, there was also Xserver update (xorg-x11-server package) in Update repository. And this could cause issue with NVidia blob driver. Not the KDE update itself. I just spotted that here... about 1 minute after you sent your email :-) Yes, the xorg package was the culprit that caused my odd problems with Chromium. C. I think that it is fair to say that people ought to be made aware of

On 26/04/14 20:14, C wrote: this problem with the nVidia driver as a result of upgrading to KDE 4.13.

My wife loves to play backgammon (gnubg) but it stopped 'working' when she tried to play it this morning. I remembered what you said re recompiling the nVidia driver and after I did this gnubg was back in business. She is again a happy little vegemite :-) .

BC

Read what you quoted.

It's not a result of The KDE upgrade. It would have bitten you even without updating KDE, because there was a xorg update in another repository.

Well, I think it is only natural to assume that when this problem arose when KDE was upgraded that it was the KDE upgrade which caused the problem. In fact, I just added in YaST the Xorg repository you mentioned in one of your previous posts here and when I went to update the files I got the same dependency errors (that KDE 4.13 had dependency problems with openSUSE branding) when I upgraded to KDE 4.13. Now, why should upgrading Xorg* files have anything to do with KDE 4. 13 and its need for have openSUSE branding files of the correct flavour? :-) BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 28/04/14 05:31, John Andersen wrote:

On 04/27/2014 12:00 AM, Basil Chupin wrote:

...

In fact, I just added in YaST the Xorg repository you mentioned in one of your previous posts here and when I went to update the files I got the same dependency errors (that KDE 4.13 had dependency problems with openSUSE branding) when I upgraded to KDE 4.13.

Now, why should upgrading Xorg* files have anything to do with KDE 4. 13 and its need for have openSUSE branding files of the correct flavour? :-)

You need to learn to read those dependency error messages. It will tell you exactly which modules depend on what other modules.

I don't believe there is any branding dependencies in Xorg.

Well, I am not in a position to argue about this as my knowledge is limited on the subject. However, I can say this: I accepted your comment that the files for Xorg in the repository- http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_1?.?/ was kosher and upgraded the files to the ones in this repo. I spent close to 2 hours the next morning in recovering the system and bringing it back to a workable state because I could not boot into 13.1 but could only boot into level #3. Cause? Xorg* file incompatibility with the rest of KDE 4.13 system. The recovery involved downgrading the Xorg files from the repo you mentioned. Now that I have my system back up and working I checked the system for dependency problem using the YaST option and there are no dependency problems. BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 29/04/14 23:35, Anton Aylward wrote:

On 04/29/2014 03:54 AM, Basil Chupin wrote:

...

...

On 04/27/2014 12:00 AM, Basil Chupin wrote:

...

In fact, I just added in YaST the Xorg repository you mentioned in one of your previous posts here and when I went to update the files I got the same dependency errors (that KDE 4.13 had dependency problems with openSUSE branding) when I upgraded to KDE 4.13.

Now, why should upgrading Xorg* files have anything to do with KDE 4. 13 and its need for have openSUSE branding files of the correct flavour? :-) You need to learn to read those dependency error messages. It will tell you exactly which modules depend on what other modules.

I don't believe there is any branding dependencies in Xorg. Well, I am not in a position to argue about this as my knowledge is

On 28/04/14 05:31, John Andersen wrote: limited on the subject.

However, I can say this:

I accepted your comment that the files for Xorg in the repository-

http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_1?.?/

was kosher and upgraded the files to the ones in this repo.

I spent close to 2 hours the next morning in recovering the system and bringing it back to a workable state because I could not boot into 13.1 but could only boot into level #3. Cause? Xorg* file incompatibility with the rest of KDE 4.13 system. The recovery involved downgrading the Xorg files from the repo you mentioned.

Now that I have my system back up and working I checked the system for dependency problem using the YaST option and there are no dependency problems.

I went though this as well. However it took me less than 2 hours to recover so one simple reason. My solution was to remove that repository.

Removing 'that' repository is only the first step. You then have to determine and remove the installed rpms from that repo which affect the system, right? And after realising what the problem was, using YaST2 in keyboard-mode is not a pretty sight and takes a bit of time following which you have to recompile the nVidia driver :-) . Oh, not to mention having to eat breakfast while this is being done :-) . BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 01/05/14 17:22, medwinz wrote:

On Thu, May 1, 2014 at 1:36 PM, Basil Chupin wrote:

...

And after realising what the problem was, using YaST2 in keyboard-mode is not a pretty sight and takes a bit of time following which you have to recompile the nVidia driver :-) . Oh, not to mention having to eat breakfast while this is being done :-) .

BC You can always enable nouveau driver to get your X come alive in this situation, before you recompile the nvidia proprietary driver :-)

I did notice that the nouveau driver appeared to be installed but this did not make a difference :-( . But so many things were going thru the mind at the time that I may have been wrong about the nouveau. But no matter now - it's all a learning experience :-) . BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.2-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/01/2014 02:36 AM, Basil Chupin wrote:

On 29/04/14 23:35, Anton Aylward wrote:

[Big Snip]

...

I went though this as well. However it took me less than 2 hours to recover so one simple reason. My solution was to remove that repository.

Removing 'that' repository is only the first step. You then have to determine and remove the installed rpms from that repo which affect the system, right?

For some values of 'right', yes. The method I used was to run 'zypper up'. Well to be quite honest that I did was start zypper up, default yes and then go away and have a coffee and read the news on my phone. (I don't do paper newspapers any more.)

And after realising what the problem was, using YaST2 in keyboard-mode is not a pretty sight and takes a bit of time following which you have to recompile the nVidia driver :-) . Oh, not to mention having to eat breakfast while this is being done :-) .

"Yast2 in keyboard mode" ?? Do you mean 'zypper'? -- There are two rules for success in life: Rule 1: Don't tell people everything you know. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 05/01/2014 08:19 AM, Basil Chupin wrote:

On 01/05/14 21:44, Anton Aylward wrote:

...

On 05/01/2014 02:36 AM, Basil Chupin wrote:

...

[...] "Yast2 in keyboard mode" ??

Do you mean 'zypper'?

Nope, YaST2.

You mean that you have never had the pleasure of using YaST2 in keyboard mode?!

What you have been missing! :-)

Login as root at level 3 and then on the command line, "Yast2". Take it from here - and enjoy! :-) .

Oh you mean CURSES! Once. Never again! -- The saying often quoted from Lord Kelvin… that 'where you cannot measure your knowledge is meagre and unsatisfactory,' as applied in mental and social science, is misleading and pernicious. This is another way of saying that these sciences are not science in the sense of physical science and cannot attempt to be such without forfeiting their proper nature and function. Insistence on a concretely quantitative economics means the use of statistics of physical magnitudes, whose economic meaning and significance is uncertain and dubious. (Even wheat is approximately homogeneous only if measured in economic terms.) And a similar statement would even apply more to other social sciences. In this field, the Kelvin dictum very largely means in practice, 'if you cannot measure, measure anyhow!' — Frank Hyneman Knight 'What is Truth' in Economics? (1956), 166 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 27/04/14 14:08, Robin Klitscher wrote:

On 04/27/2014 03:49 PM, Basil Chupin wrote:

...

...

On Sat, Apr 26, 2014 at 12:09 PM, Mariusz Fik wrote:

...

Dnia sobota, 26 kwietnia 2014 07:07:14 C pisze:

...

This whole thing was rather odd. The KDE4.13 update didn't include a new kernel (I check the update before I apply). It was only a KDE4 update I triggered... but somehow something tweaked the NVidia driver in such a way that only Chrome and Chromium would trigger an X crash. In the time when KDE 4.13 showed up in KDE:Current, there was also Xserver update (xorg-x11-server package) in Update repository. And this could cause issue with NVidia blob driver. Not the KDE update itself. I just spotted that here... about 1 minute after you sent your email :-)

Yes, the xorg package was the culprit that caused my odd problems with Chromium.

C. I think that it is fair to say that people ought to be made aware of

On 26/04/14 20:14, C wrote: this problem with the nVidia driver as a result of upgrading to KDE 4.13.

My wife loves to play backgammon (gnubg) but it stopped 'working' when she tried to play it this morning. I remembered what you said re recompiling the nVidia driver and after I did this gnubg was back in business. She is again a happy little vegemite :-) .

AFAIK it's not the upgrade to KDE 4.13 that's the "problem", but the contemporary (though otherwise unconnected) update to the xorg server.

See my response to John.

For a very long time I've used the nVidia proprietary drivers, invariably installed the (so-called) "hard way". I've never had any serious or lasting trouble with this, other than self-inflicted. Having to re-install after a kernel update is a given, of course. But so it is also for xorg updates where the video drives might appear still to be working, though with much reduced functionality. Re-installing nVidia restores all that.

BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Saturday, April 26, 2014 10:12:36 AM John Andersen wrote:

On 04/26/2014 03:09 AM, Mariusz Fik wrote:

...

Dnia sobota, 26 kwietnia 2014 07:07:14 C pisze:

...

This whole thing was rather odd. The KDE4.13 update didn't include a new kernel (I check the update before I apply). It was only a KDE4 update I triggered... but somehow something tweaked the NVidia driver in such a way that only Chrome and Chromium would trigger an X crash.

In the time when KDE 4.13 showed up in KDE:Current, there was also Xserver update (xorg-x11-server package) in Update repository. And this could cause issue with NVidia blob driver. Not the KDE update itself.

But even those updates in the update repository are significantly behind the updates you will find here: http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_1?.?/ (insert version)

There are many issues that have been resolved, (perhaps not for Nvidia) in the latest version of X related packages in the above that are still broken in the update repository.

I've had image/video tearing, horrible performance using any effects, using the packages in the updates repository, but probably the best performance my machine has ever delivered using the one above.

-- Explain again the part about rm -rf / I experienced some of the same issue,s but it was Chromium and SeaMonkey browsers, Akonadi and a fourth one I don't remember. I fixed it by updating and install the Nvidia driver (now on 331-67) again. Problem was there were no openGL packages shown when Nvidia started.

I'm happy so far. Russ -- openSUSE 13.1(Linux 3.11.10-7-desktop x86_64| Intel(R) Quad Core(TM) i5-4440 CPU @ 3.10GHz|8GB DDR3| GeForce 8400GS (NVIDIA-Linux-x86_64-331.67)|KDE 4.13.0 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Does it also happen in Konq using WebKit, or in Rekonq (which is also WebKit, from which Blink running Chrom* was forked)? What's your gfxchip? Wild stab: try logging out, uninstalling Flash, then trying. Other stabs: set autoload=false under [Module-kscreen] in kdedrc disable bling globally ('Option "Composite" "Disable"' in xorg.con*) -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org