[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Thanks. Those crashes are from gnome-shell crashing in
libglib-2.0.so.0.6800.1+43647 but we don't have any useful debug symbols
in them :(
Please open the Extensions app and ensure you don't have any extensions
enabled other than the Ubuntu ones.
Please also upgrade to 21.10 when you can as we
I got a case of failing to wake up with GDK_SYNCHRONIZE turned on, and
I've attached the output from journalctl. However, there's no new crash
file. Am turning off wayland for now.
On 2021-10-19 2:13 a.m., Daniel van Vugt wrote:
> Per the instructions in comment #5:
>
> "If step 1 failed then
On second thought, I re-enabled wayland and turned on GDK_SYNCHRONIZE
and I'll give it a day or so to see if the bug crops up again. There's
definitely something wrong about gdm3 calling wayland because after
boot, icons that should appear on the dash only do so AFTER you run a
program, like a
After disabling the GDK_SYNCHRONIZE statement, I finally was able to get
the bug to reappear. I've attached a new prevboot file (after a power
button shot down and reboot). I also used apport-cli to upload the crash
report. It's url is
The last error reported was on Oct 18 and the url is
https://errors.ubuntu.com/oops/33300c46-3036-11ec-ad49-fa163e102db1
I've rebooted into wayland, but so far the bug has not occurred. It's
possible that the synchronization is preventing it from happening. I
will wait a while longer and if it
Per the instructions in comment #5:
"If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us."
--
You received this
I was able to upload the first crash, but no web browser opened so I
don't know where it went. The second crash would not upload because it
said that the crash was about a package that was not installed.
I edited the environment file and will try to reproduce teh bug
tomorrow.
Chris
On
In the log of comment #6 it looks like you managed a soft reboot rather
than the hard reboot I was expecting. That's good news for you but made
understanding the log a bit more difficult. It appears the problem you
hit was a gnome-shell crash:
Oct 18 12:52:58 fluffy gnome-shell[4425]: The program
Also, please edit /etc/environment and add a line:
GDK_SYNCHRONIZE=1
That will slow the system slightly but will make the next crash occur in
a more *debuggable* way. It will create a new unique crash so please
tell us the link to that one too.
--
You received this bug notification because
If ubuntu-bug fails then try apport-cli instead.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1947194
Title:
When using Wayland in 21.04, the display often never wakes up after
I tried this with my 2 crash reports but ubuntu-bug reported an internal
error each time, so I doubt that they became attached to the bug report.
Chris
On 2021-10-18 3:40 a.m., Daniel van Vugt wrote:
> Please also check for crashes using these steps:
>
One more thing. I was using Focal Fossa, but it was incompatible with a
library needed for a program I needed for my work (gle-graphics). This
forced me to upgrade to Groovy Gorilla and then Hirsute Hippo. My
problems started because 21.04 defaulted to wayland. I have tried out
Impish Indrie
Thanks Daniel. Here's the prevboot.txt file. There were 2 separate crash
files generated when I booted using wayland. The first with my user
permission was generated immediately and this was when there were no
dash icons present. The second was generated with root ownership when
the screen
Please also check for crashes using these steps:
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
Desktop Bugs, which is subscribed to mutter in Ubuntu.
OK, thanks.
Please:
1. Reproduce the bug in Wayland again.
2. Wait 10 seconds.
3. Reboot.
4. Run:
journalctl -b-1 > prevboot.txt
5. Attach the resulting text file here.
6. Also consider trying Ubuntu 21.10 which was just released a couple of
days ago.
** Summary changed:
- Wayland
16 matches
Mail list logo
