Aha!
Yes you were probably experiencing bug 1714330 in the old log of comment
#6 but not any more.
In your new log of comment #8 you are now experiencing a new assertion:
Sep 18 07:25:39 internet-ws org.gnome.Shell.desktop[1891]:
mutter:ERROR:backends/meta-monitor-
manager.c:2274:meta_monitor_ma
The system is up to date. Unfortunately the problem persist.
I'm Sorry, I have added old syslog file in previous post. Please find attached
syslog from today morning, logs starting on the time of crash.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/
Thanks. Your log shows gnome-shell is crashing in libmutter:
Sep 13 14:08:10 internet-ws kernel: [11508.541040] gnome-shell[3056]: segfault
at 2c ip 7fd7c9d0cb24 sp 7ffc4ffe2a28 error 4 in
libmutter-1.so.0.0.0[7fd7c9c6f000+13f000]
Sep 13 14:08:10 internet-ws gnome-session[2964]: gnome-se
Hello. /var/crash/ is empty. I have attached part of Syslog starting at
the time I switched off the monitor and a lot of errors were logged
since that time. Please look at it, may be it can help also determine
why crash file is not generated.
** Attachment added: "part of syslog file"
https:/
Have a look in your /var/crash/
If there are none there already then I'm not sure why, other than
dumping of core somehow failed, or less likely it's not "crashing" via
any of the normal fatal signals.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Please how to force .crash file creation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717170
Title:
Gnome-shell session crash after monitor switch-off/input change.
To manage notifications about
Apport is enabled in /etc/default/apport but no file is located
/var/crash even after crash. I have created the bug report using ubuntu-
bug tool.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717170
Sounds like you might have hit bug 1714330 but we should go though the
proper procedure in case you're experiencing a different problem...
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as
