You are not logged in.
On one hand it's really annoying getting a core dump every five to ten minutes...
On the other hand, GNOME Shell really flies when it's restarted every five to ten minutes.
Regression, bug, or feature? ![]()
Offline
You got it right. That's why it's called stable release...
For me it seems I can minimize the restarts of gnome-shell by resizing the window I am about to close - for me it's double-clicking on he top window bar - and then close it. It's an awful workaround but at least I can work with it for the moment - that is if I am not going quickly and accidentally close a full screened app out of habit...
p.
Last edited by piedro (2017-10-08 17:17:42)
Offline
Same here, Why such problems should be exists in stable release?
Last edited by shsina (2017-10-08 17:55:52)
Offline
The issue is probably a code adaption for wayland and "who cares about X11"
The ones with a NVIDIA <=340xx driver compatible like me
Last edited by Mons1990 (2017-10-08 17:52:42)
Hardware configuration: Intel Core i5 3.4GHz, 8GB DDR3 RAM, NVIDIA GEForce 9600GT
Software configuration: Arch Linux, default kernel, NVidia 340xx drivers, Gnome 3 on X.Org
Mons
Offline
I guess that got lost in translation, but I consider "who cares about X11" to be part of the issue - certainly not my personal opinion.
(It implies "regression", regression means lousy QM and lousy QM is never a good sign of anything)
Offline
I'm having this issue as well. Intel graphics, both xorg and wayland. Thought it was just me. Hope we see a fix soon.
Offline
Now here is a full thread of people saying "me too" and bumping the thread (don't do that), yet I see no link to an upstream bug report.
Has anybody bothered looking upstream for a bug, and if there is none opened one? That would probably help far more than "bumping" here.
I disagree that "me too" isn't helpful (it can point out at how widespread problem is), but I do agree with the rest of your post.
It have nothing to do with nvidia drivers, I use AMD/ATI radeon/mesa drivers and have same problem. At first I tought I could easily reproduce it with Dolphin emulator, however, it is too random, but dolphin-emu crashes gnome-shell quite fast (as closing firefox maximized window after visiting youtube for a while for example).
Last edited by lpr1 (2017-10-09 01:29:41)
Offline
I disagree that "me too" isn't helpful (it can point out at how widespread problem is), but I do agree with the rest of your post.
I didn't want to say "me too" is unhelpful, I actually think it is. It just struck me as odd that so many people were involved, yet no upstream report ![]()
Offline
@phw Yeah I agree with that point
, O usually wait more competent people to do bug reports, and do it myself only if it's specific to me, I guess others follow similar principle
.
Offline
Reverting mutter to earlier version solves the problem for me, or build it with this commit aea66ddff6fd91edf10499b8fd156e0663f2f271
Last edited by lpr1 (2017-10-09 13:11:30)
Offline
The same here...downgrading mutter to 3.26.0+6%2Bg26cd031be-2 the error is not displayed.
Offline
There is a patch that fixes the problem in bug report from this topic posted earlier.
Offline
I've changed the official PKGBUILD for mutter-3.26 and added the patch from bugzilla. It seems to work like a charm:
https://github.com/LordPong/mutter-3.26-fixed
Offline
I've changed the official PKGBUILD for mutter-3.26 and added the patch from bugzilla. It seems to work like a charm:
https://github.com/LordPong/mutter-3.26-fixed
I just tested your patch and it works! Thanks!
Is it a good idea to report a ticket at bugs.archlinux.org so that maintainers can apply it and rebuild the package?
Can you do it please?
Offline
peter.berg wrote:I've changed the official PKGBUILD for mutter-3.26 and added the patch from bugzilla. It seems to work like a charm:
https://github.com/LordPong/mutter-3.26-fixedI just tested your patch and it works! Thanks!
Is it a good idea to report a ticket at bugs.archlinux.org so that maintainers can apply it and rebuild the package?
Can you do it please?
It's already in the process: https://bugzilla.gnome.org/show_bug.cgi?id=788666
Offline
Interesting observation. My work laptop is running openSUSE Tumbleweed and I have not observed this problem on either 3.26.0 or 3.26.1. FWIW changes in mutter package: https://build.opensuse.org/package/view … s?expand=1
Offline
Hey everybody,
i have the same issue and it is unbelievable annoying.
Could anybody tell me how to build a package with the fixed mutter version?
I have all dev tools on my system and i have experiences with compiling software from github but i never made any pacman packages before.
Thanks
Offline
@JohnD87 You have a link with a PKGBUILD that builds a patched version of mutter just few messages above. As for how to use said PKGBUILD, I suggest consulting Arch Wiki.
Last edited by Xabre (2017-10-10 10:30:10)
Offline
@JohnD87 You have a link with a PKGBUILD that builds a patched version of mutter just few messages above. As for how to use said PKGBUILD, I suggest consulting Arch Wiki.
Thanks. Worked fine.
Offline
Workaround, disable animations.
Offline
Seems like the patch was pushed and is available in arch's repo. Nice.
Last edited by Airei6oh (2017-10-10 17:57:28)
Offline
peter.berg's package solved completely the issue for me, but today's update introduces it again...
Offline
@papa33 It's because it doesn't include the latest 3 commits, including the fix yet, just reinstall the old package.
Offline
my apologies papa33, tetrox is right, the patch isn't included... yet I currently have mutter 3.26.1+6+g425df31cf-1 running and I don't have this bug anymore.. Weird.
Last edited by Airei6oh (2017-10-10 17:56:45)
Offline
3.26.1+7+g41f7a5fdf-1 new update fixes the issue for me.
Offline