BTW, we have fixed many gnome-shell bugs with these symptoms recently in
Ubuntu 18.04. So please try 18.04 and log a new bug if you have any
problems.
--
You received this bug notification because you are a member of Ubuntu
Desktop, which is subscribed to the bug report.
This bug is closed due to no response from the original reporter, so
please don't add further comments.
Everyone else should:
1. If using a release older than 18.04 then apply the workaround from
bug 994921 first.
2. Run: ubuntu-bug /var/crash/YOURFILE.crash
** Changed in: gnome-shell
This bug is closed due to no response from the original reporter, so
please don't add further comments.
Everyone else should:
1. If using a release older than 18.04 then apply the workaround from
bug 994921 first.
2. Run: ubuntu-bug /var/crash/YOURFILE.crash
--
You received this bug
If 'ubuntu-bug' fails for you then please try applying the workaround
from bug 994921 first.
--
You received this bug notification because you are a member of Ubuntu
Desktop, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1721428
Title:
Artful (17.10) Session logout
See comments #52 and #64.
--
You received this bug notification because you are a member of Ubuntu
Desktop, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1721428
Title:
Artful (17.10) Session logout after screen turned off
To manage notifications about this bug go
This bug is closed.
Please log new bugs if you have any issues at all.
--
You received this bug notification because you are a member of Ubuntu
Desktop, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1721428
Title:
Artful (17.10) Session logout after screen turned off
I mean:
Bug closed, due to no response from the original reporter after over 2
months (see comment #52).
Everyone else please keep logging your own bugs if you have any issues.
--
You received this bug notification because you are a member of Ubuntu
Desktop, which is subscribed to the bug
Bug closed, due to no response from the original reporter after over 3
months (see comment #52).
Everyone else, please keep logging your own bugs if you have any issues.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
** Changed in: mutter (Ubuntu)
Status:
** Project changed: nouveau => ubuntu
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1721428
Title:
Artful (17.10) Session logout after screen turned off
To
Bug 1750773 does not seem to exist (!?)
--
You received this bug notification because you are a member of Ubuntu
Desktop, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1721428
Title:
Artful (17.10) Session logout after screen turned off
To manage notifications about
Everyone please log your own separate bugs for this issue. Because it's
not really one issue - it is multiple different gnome-shell crashes.
Logging your own bug will help us to figure out exactly which crash you
are experiencing and which fix you need.
--
You received this bug notification
Craig, in that case please just:
1. Open a bug https://bugs.launchpad.net/ubuntu/+source/xorg-server/+filebug
2. Add tag "xwayland"
3. Change it from Public to Private (top right of the page)
4. Attach your crash file to the bug.
Normally we do not recommend doing it that way as there's no
Everyone please log your own separate bugs for this issue. Because it's
not really one issue - it is multiple different gnome-shell crashes.
Logging your own bug will help us to figure out exactly which crash you
are experiencing and which fix you need.
--
You received this bug notification
Everyone please log your own separate bugs for this issue. Because it's
not really one issue - it is multiple different gnome-shell crashes.
Logging your own bug will help us to figure out exactly which crash you
are experiencing and which fix you need.
--
You received this bug notification
If the bug does get closed due to lack of response from the reporter
then that actually doesn't stop us commenting here.
Everyone please report your own separate bugs for crashes so that we may
diagnose and group them more accurately. If you like, please mention the
ID of your new bug(s) here.
OK, I am assuming "That worked" means you found the bug ID(s) your
machine is experiencing, and they were not this one :)
Per comment #52, if the original reporter does not reply by early
February then this bug will be closed due to lack of response. That
doesn't mean this bug doesn't exist, just
Yes, sorry, that seems to be a missing feature (or bug?) of apport. It
tells you a crash happened but not where to follow it up on the web.
Here's how to find out where your crash(es) went. In a terminal run the
below command. It will ask you for your password because for some
(security) reason
Hi all,
There are a number of bugs in gnome-shell that would exhibit symptoms
like this bug describes. So I'm going to ask:
@koalay only: Please run 'apport-collect 1721428' on the affected
machine to help us gather more information.
Everyone: Look in /var/crash for some .crash files. If you
** Project changed: mutter => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1721428
Title:
Artful (17.10)
** Changed in: gnome-shell
Importance: Undecided => Unknown
** Changed in: gnome-shell
Status: New => Unknown
** Changed in: gnome-shell
Remote watch: None => GNOME Bug Tracker #789166
** Package changed: ubuntu => gnome-shell (Ubuntu)
--
You received this bug notification because
20 matches
Mail list logo
