Alberto,
Do you still experience this bug?
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769981
Title:
Temporary screen
Vivek,
This is a 4 year old bug reported by someone else on a different Ubuntu
version with likely different hardware. Please open your own bug by
running:
ubuntu-bug gnome-shell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've been having an issue similar to this on 22.04 (jammy) and don't
recall experiencing it on 21.10. It's actually happened not just from
standby but from just being on (with display off) as well. I'm still
testing, but it could be extensions like 'blur my shell' causing an
issue. Couldn't find
I just had a series of freezes, and managed to ssh and watch logs in the
meantime, the only messages that I that might be relevant are the
following (repeated many times):
May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap:
assertion 'SHELL_IS_EMBEDDED_WINDOW (window)'
For the default Ubuntu installation I believe we have fixed all the log
messages that look like that.
So if you're seeing those I suggest removing some/all of your
extensions:
b'org.gnome.shell' b'enabled-extensions' b"['alternate-tab@gnome-shell-
extensions.gcampax.github.com',
Daniel, not sure if they're related, but it seems that when I get back
from the "slide" screen (even if not locked) I'm getting a lot of these
errors repeated in journalctl:
May 24 14:52:47 kashyyyk gnome-shell[6901]: Object Meta.Background
(0x562f8156e590), has been already deallocated -
I only see apparmor audit messages there
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769981
Title:
Temporary screen freeze when coming back from screen standby
To manage notifications about
No messages at all just before or just after the freezes?
How about in the kernel log?; dmesg -w
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769981
Title:
Temporary screen freeze when coming
No, I've never seen any message in log that could seem related to the
issue.
Yes there are two cases here, although related. I experience these
freezes when coming out of screen standby, which sometime are longer and
end up with a session crash, but in many case they just freeze the UI
and send
If you log in remotely from another machine and watch the log:
journalctl -f
then do you find any messages coincide with the freezes?
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
> https://errors.ubuntu.com/oops/93aef40e-5deb-11e8-945f-fa163e8d4bab (most
> recent)
> https://errors.ubuntu.com/oops/c9e22fbe-58dc-11e8-9127-fa163ed44aae
> https://errors.ubuntu.com/oops/385a60b4-334f-11e8-a211-fa163ef911dc
are all bug 1731261
>
The last crash is https://errors.ubuntu.com/oops/93aef40e-5deb-11e8
-945f-fa163e8d4bab
There are a few previous chrashes with the same syntomps:
https://errors.ubuntu.com/oops/c9e22fbe-58dc-11e8-9127-fa163ed44aae
https://errors.ubuntu.com/oops/385a60b4-334f-11e8-a211-fa163ef911dc
Yes, links please.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769981
Title:
Temporary screen freeze when coming back from screen standby
To manage notifications about this bug go to:
>From the list on that page I can see that a report was indeed uploaded
for that crash:
2018-05-22 20:052018-05-22 18:05 UTCCrash xwayland
Unfortunately if I click on the link, I get an error saying that I'm not
allowed to see crash reports. Is it ok for me to share the link to
The next step I suggest is to look up automatic crash reports your
system has made:
https://errors.ubuntu.com/user/ID
where ID is the contents of /var/lib/whoopsie/whoopsie-id
If you find any relevant links there then please share them here.
As a last resort you can also:
1. Change this
@Daniel I followed the steps there (specifically, enabling crashes for X). I
just got a freeze with subsequent crash and got a new Xwayland .crash file.
Still, running ubuntu-bug on it it just exits with no error when I click to
submit, and it doesn't seem to be submitting the bug.
What steps
It gives you several steps that must be followed first to *fix* the
problem with not being able to upload it via ubuntu-bug. Please follow
all steps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That link mentions how to create a crash file, but I do have one, I just
can't upload it via ubuntu-bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769981
Title:
Temporary screen freeze when
In that case please follow the standard instructions :)
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes I have a Xwayland crash file in /var/crash with the same timestamp.
I tried running ubuntu-bug on it, but after I confirm the popup message,
it just exits without any error and it doesn't pop up a launchpad
window.
--
You received this bug notification because you are a member of Ubuntu
That's OK. We can probably ignore most Xwayland crashes anyway. They are
mostly just Xwayland dying because gnome-shell crashed...
Do you get any other crash files in /var/crash?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
Thanks Daniel,
the core file I got from the crash (in my home dir) shows as
core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style,
from '/usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4
-listen 5 -d', real uid: 1000, effective uid: 1000, real gid: 1000,
effective
If you have a core or crash file then yes please open a new bug, but
only by running:
ubuntu-bug YOURFILE
See also
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
@Daniel, I just got a session crash because of this freeze and got an Xwayland
core file in my home.
Should I open a different bug? How do I attach the core through apport?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FTR this also happens on another PC, also with Intel card (different
model), also a fresh Bionic install
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769981
Title:
Temporary screen freeze when
See also related bugs:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=unlock
** Tags added: unlock
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769981
Title:
Temporary
26 matches
Mail list logo
