*** This bug is a duplicate of bug 1724439 ***
https://bugs.launchpad.net/bugs/1724439
Great, thanks. This is now a duplicate of bug 1724439.
** This bug has been marked a duplicate of bug 1724439
gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
ffi_call_unix64() from
Went to the other bug and saw it is already public now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753658
Title:
Xorg crash
To manage notifications about this bug go to:
Great, thanks. But I can't access that bug so it must be private.
Unusual though, since as a member of ~ubuntu-bugcontrol I should be able
to see it...
Please wait until that bug has finished retracing, then remove any
sensitive personal information attachments from it, then change it from
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753658
Title:
Xorg crash
To
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
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
To diagnose this problem we still need a crash file. Please:
1. Apply the workaround from bug 994921.
2. Reboot and reproduce the crash.
3. Look in /var/crash for new crash files.
4. Run: ubuntu-bug /var/crash/YOURFILE.crash
5. Add a comment in this bug telling is the ID of the newly-created
