Registered Member
|
Hi,
I just upgraded to the latest KDE plasma on Arch (plasma-desktop 5.3.1-2) and after the upgrade Chrome crashes almost instantly after opening or sometimes it lasts a few minutes. Android Studio (Java) opens but crashes after a minute of trying to index files. Various kde apps crashes at random times (such as Settings). The whole plasma desktop also sometimes crashes. If I create a new user with a brand new home directory then things seems to be OK. I have tried deleting ~/.cache and /var/tmp/kdecache-username but did not help. Anything else that needs to be deleted? The logs are full of these messages which I assume may be related: kwin_x11[971]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 26773, resource id: 65011713, major code: 18 (ChangeProperty), minor code: 0 kwin_x11[1182]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55404, resource id: 37830280, major code: 3 (GetWindowAttributes), minor code: 0 Should add that I tried to downgrade all the packages to the version before I had issue but that did not help. Firefox crashes also. When I open in terminal I see the following output (before any crash occurs): (process:1216): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ATTENTION: default value of option force_s3tc_enable overridden by environment. Can't find symbol 'glXCreateContextAttribsARB'. Thanks. |
|
You may assume that the update of plasma did NOT cause crashes in chromium, let alone some java applications - but w/o backtraces it's impossible to say what causes them.
Firefox is a *very* popular crash https://bugzilla.mozilla.org/show_bug.cgi?id=672671 Can't find symbol 'glXCreateContextAttribsARB'. This "just" means that you've no opengl3 support. The "QXcbConnection: XCB error" stuff are red herrings, they mean that something (in this case the WM) tried to alter a property on an already deleted window (what's a possible incident given that a window manager does not operate on its own clients and X11 is an async protocol - the alternative would be lots of server grabs, you wouldn't like that It does not cause any crashes at all.
Can you post a backtrace of plasmashell/kwin (or whatever you meant by "The whole plasma desktop")? Given the wide range of impact, I'd have said that something like glib or libgl is the cause, or /var being out of space, or you're running OOM - but that doesn't fit "new user" - except everything might have aligned to missing GL support there or so. |
Registered Member
|
Update - issue was due to bad memory.
Thanks for the help! |
Registered users: Bing [Bot], Evergrowing, Google [Bot], rockscient