Thanks. It appears Ubuntu on X11 is trying to start (3 times) and
failing, which is why it chooses Wayland instead.
You appear to be using the 'oibaf' PPA which is not supported and is
known to cause bugs like this. Please uninstall it using 'ppa-purge',
reboot, and then open new bugs about any
*** This bug is a duplicate of bug 1945061 ***
https://bugs.launchpad.net/bugs/1945061
** This bug has been marked a duplicate of bug 1945061
gdm3 crashed with SIGSEGV in ensure_display_for_seat()
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
*** This bug is a duplicate of bug 1945061 ***
https://bugs.launchpad.net/bugs/1945061
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gdm3. This problem was most recently seen with package version 41~rc-0ubuntu1,
the problem page at
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Tracking in
https://errors.ubuntu.com/problem/131b21d4843931d315a4548121d7d352cfd1e3a8
** Information type changed from Private to Public
** Description changed:
+ https://errors.ubuntu.com/problem/131b21d4843931d315a4548121d7d352cfd1e3a8
+
+ ---
+
no time for handling, hope everything
This appears to be in the same family as bug 1943406. But rather than
being driver-specific it looks like mutter is trying to delete an
invalid texture, which will crash differently for each driver.
** Summary changed:
- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in
You have been subscribed to a public bug:
I'm using Ubuntu 20.04.3 LTS
I have my power settings so that Ubuntu will never auto-suspend if
plugged in, but will do so after 20 minutes if on battery power.
If I leave it plugged in but untouched for 20 minutes, and then unplug
it (to move it to
Public bug reported:
https://gitlab.freedesktop.org/libfprint/libfprint/-/blob/master/libfprint/drivers/goodixmoc/goodix.c#L1505
This ID is included in upstream.
** Affects: libfprint (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
Thanks for the bug report. After reproducing the bug again please run:
journalctl -b0 > journal.txt
and then attach the resulting text file here.
Please also follow these instructions to check for crashes:
Seems to be a regression in 41~rc-0ubuntu1
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1945061
Title:
gdm3 crashed with SIGSEGV in
Public bug reported:
https://gitlab.freedesktop.org/libfprint/libfprint/-/blob/master/libfprint/drivers/goodixmoc/goodix.c#L1507
This ID is included in upstream.
** Affects: libfprint (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- To support goodix fp device
Thanks for the bug report. While the stutter is still happening, please
run:
lspci -kv > lspci.txt
journalctl -b0 > journal.txt
and attach the resulting text files here.
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are
Thanks Daniel , Will try to remove waydroid , which was not working
anyway
--
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/1945047
Title:
Gdm does not start anymore on 20.04
To
** Tags added: braswell
** No longer affects: mutter (Ubuntu)
--
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/1767654
Title:
[Intel Braswell] Cursor gets stuck on left side of the
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1471
https://github.com/micheleg/dash-to-dock/issues/1471
** Also affects: dash-to-dock via
https://github.com/micheleg/dash-to-dock/issues/1471
Importance: Unknown
Status: Unknown
** Changed in:
Tracking upstream in https://gitlab.gnome.org/GNOME/gnome-settings-
daemon/-/issues/134 although I found it by
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/563 which
better matches this bug.
** Package changed: xorg (Ubuntu) => gnome-settings-daemon (Ubuntu)
** Bug watch added:
Tracking in
https://errors.ubuntu.com/problem/d20095c0f9516f2d25a5e5b9194fdb87eec5ba8b
** Tags added: vmware vmwgfx
** Summary changed:
- gnome-shell crashed with SIGSEGV
+ [vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from
mm_buffer_destroy() from pb_destroy()
** Package
*** This bug is a duplicate of bug 1945010 ***
https://bugs.launchpad.net/bugs/1945010
** This bug has been marked a duplicate of bug 1945010
[vmwgfx] gnome-shell crashed with SIGSEGV in u_mmFreeMem.isra.0() from
mm_buffer_destroy() from pb_destroy()
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
*** This bug is a duplicate of bug 1945010 ***
https://bugs.launchpad.net/bugs/1945010
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
40.2-1ubuntu1, the problem page
Thanks that is the way droid repo that broke .
I fixed it by restoring the ubuntu repo version.
--
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/1945047
Title:
Gdm does not start
Still the case, at Mint 20, Evolution 3.36.5-0ubuntu1
The work around from Jacob still works well, evolution --force-shutdown.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
Now I get a problem that cannot be reported
** Attachment added: "Screenshot from 2021-09-28 16-27-45.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1943406/+attachment/5528718/+files/Screenshot%20from%202021-09-28%2016-27-45.png
--
You received this bug notification
** Changed in: gdm3 (Ubuntu)
Milestone: None => ubuntu-21.10
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1945061
Title:
gdm3 crashed with SIGSEGV in ensure_display_for_seat()
** No longer affects: gnome-shell-extension-desktop-icons (Ubuntu
Impish)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1917010
Title:
Hard to detect
[Expired for gnome-software (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: gnome-software (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in
[Expired for gtk+2.0 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gtk+2.0 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
[Expired for fcitx (Ubuntu) because there has been no activity for 60
days.]
** Changed in: fcitx (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to fcitx in Ubuntu.
[Expired for Ubuntu MATE because there has been no activity for 60
days.]
** Changed in: ubuntu-mate
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to fcitx in Ubuntu.
[Expired for mate-panel (Ubuntu) because there has been no activity for
60 days.]
** Changed in: mate-panel (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to fcitx in Ubuntu.
This part looks suspicious:
#43 0x7f6a08e3c36e in _cogl_pipeline_free (pipeline=0x0) at
../cogl/cogl/cogl-pipeline.c:386
__func__ =
#44 _cogl_object_pipeline_indirect_free (obj=0x0) at
../cogl/cogl/cogl-pipeline.c:69
No locals.
#45 0x7f6a09457957 in
This part looks suspicious:
#37 0x7fabd14d636e in _cogl_pipeline_free (pipeline=0x0) at
../cogl/cogl/cogl-pipeline.c:386
__func__ =
#38 _cogl_object_pipeline_indirect_free (obj=0x0) at
../cogl/cogl/cogl-pipeline.c:69
No locals.
#39 0x7fabd1af1983 in
*** This bug is a duplicate of bug 1945061 ***
https://bugs.launchpad.net/bugs/1945061
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1945061, so is being marked as such.
[Expired for human-theme (Ubuntu) because there has been no activity for
60 days.]
** Changed in: human-theme (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk2-engines in Ubuntu.
[Expired for software-center (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: software-center (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk2-engines in
[Expired for gtk2-engines (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: gtk2-engines (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk2-engines in Ubuntu.
[Expired for mate-themes (Ubuntu) because there has been no activity for
60 days.]
** Changed in: mate-themes (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk2-engines in Ubuntu.
While the screenshot shows that GNOME is aware of the current resolution
being different to the configured resolution, it cannot guess as to
which app has caused the change and when is the right time to change
back. It's the responsibility of the application (atari800-jz) to clean
up after itself.
Sadly I don't think this is a bug in Ubuntu...
Assuming you're using Xorg, the emulator is talking directly to Xorg
(via Xrandr) to change the screen resolution. Gnome Shell is not
involved at all. It is therefore the job of the emulator to restore the
original resolution on exit.
--
You
** This bug has been marked a duplicate of bug 1944581
Session preference not respected; Wayland session started despite Xorg being
selected
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
42 matches
Mail list logo
