Re: [Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()
Rachel, no need to switch to Mac to avoid this problem. What I ended up doing was this: $ sudo add-apt-repository ppa:kubuntu-ppa/backports $ sudo apt update && sudo apt upgrade $ sudo apt install kubuntu-desktop -- Daniel Wilches On Thu, Mar 15, 2018 at 4:21 AM, Rachel Greenham <1724...@bugs.launchpad.net > wrote: > Well, my bug #1756036 just got (automatically-i-think) marked as a > duplicate of this one, and I'm on 18.04 (gnome-shell 3.27.92-0ubuntu1) > So that's one, Daniel. ;-) I'd been getting this on some mornings, but > the bug report was getting rejected because of outdated packages until > this morning. Interestingly it doesn't seem to happen again later in the > day, so, as noted before, length-of-sleep may be a factor. > > I reported a lot on these bugs in 17.10, until I eventually gave up and > just used my (half-the-speed) mac for a while. Freshly-installed 18.04 > and tried again, and I *am* having far less trouble. When it does go > wrong, it "fails better", in that it seems to recover reasonably well > and leave me with a working session, even if there are a couple of side- > effects (eg: having both dash-to-dock and the dash in > activities/applications) which clear on an orderly logout/login. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1724439 > > Title: > gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from > ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from > function_call() > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mutter/+bug/1724439/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724439 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724439/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753658] Re: Xorg crash
Went to the other bug and saw it is already public now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1753658 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753658/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753658] Re: Xorg crash
@vanvugt I followed your instructions and created the bug https://bugs.launchpad.net/bugs/1753912 with the crash file -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1753658 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753658/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753658] Re: Xorg crash
Found the issue when looking at `/var/log/apport.log`. This may be useful for other people to whom you ask to do that workaround: RROR: apport (pid 2496) Tue Mar 6 21:33:37 2018: apport: report /var/crash/_usr_bin_gnome-shell.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS So I removed the crashes I already had in /var/crash. Will reproduce the crash now and report back in a moment. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1753658 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753658/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753658] Re: Xorg crash
Tried two workarounds mentioned in that bug, none worked (the crash did
not generate any files in /var/crash).
The first workaround I tried was:
comment out line 23 ("'problem_types': ['Bug', 'Package'],") in
'/etc/apport/crashdb.conf'.
I put an # at the beginning of line 20, not 23 because line 20 is the
one that mentions problem_types, but after a restart and reproducing the
crash I didn't get any new crash files in that folder.
Also tried adding `Crash` to the list of problem_types (as mentioned in
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/993450/comments/13
) but same thing, no new files after a restart and a crash.
Something else I can try to generate the crash file?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1753658
Title:
Xorg crash
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753658/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
Me too: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1753658 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
