*** This bug is a duplicate of bug 2000649 ***
https://bugs.launchpad.net/bugs/2000649
The fix for bug 2000649 has been requested for inclusion in a future
22.04 update. Other than waiting, the only options are:
* Use regular Ubuntu rather than Xubuntu, and you will get a Wayland
session by
*** This bug is a duplicate of bug 2000649 ***
https://bugs.launchpad.net/bugs/2000649
Is there something I can do to trigger this bugfix to incorporated into
regular ubuntu updates? It's really annoying to work on unstable system,
and knowing it has been fixed already, sigh..?
--
You receiv
*** This bug is a duplicate of bug 2000649 ***
https://bugs.launchpad.net/bugs/2000649
I've gone through the most common Xorg crashes on 22.04 and found one
where the call addresses seem to match yours:
https://errors.ubuntu.com/problem/6c8ea4e88ac1e5642e14d17c955dc4b73b389612
So that's bug
Everything is from the fresh install, I did none modify any of the
system drivers.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2001922
Title:
Xorg crash
Status in xorg-server
Are you using the built-in amdgpu driver or did you install it manually?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2001922
Title:
Xorg crash
Status in xorg-server package in
Still much the same. No usable backtrace but one at least has a system
log (which isn't useful). I wonder if this is a Xubuntu-specific problem
with crash reports.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
htt
And another one...
35f5fbf4-abc7-11ed-9e34-fa163e993415
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2001922
Title:
Xorg crash
Status in xorg-server package in Ubuntu:
Incomp
I reinstalled the system and it happened again. The crash id from
/var/crash/_usr_lib_xorg_Xorg.0.uploaded is
f5810a24-aba6-11ed-b81a-fa163ef35206
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchp
Thanks. It sounds like Xorg is not smart enough to use the debug
symbols.
Your latest crashes on errors.ubuntu.com still show the robots are
ignoring crashes from this machine. I don't know the reasons but can
only guess something has changed during the upgrade process. And so the
only suggestion
I've got a new crash after installing the xorg-core-dbgsym, the
backtrace looks the same though. What else can I provide, other than
reinstalling the whole machine? That's something I'd really like to
avoid if possible
[60.469] (EE)
[60.469] (EE) Backtrace:
[60.472] (EE) 0: /usr/lib/x
Thanks. That's a good start but the symbols are bogus:
[ 160.566] (EE) Backtrace:
[ 160.569] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x56325264c719]
[ 160.569] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50)
[0x7f5527424520]
[ 160.569] (EE) 2: /usr/lib/xorg/Xorg (NewC
Uh, did not have time for this until now, got quite a few crashes in the
meantime. I am attaching the latest xorg log that gives a backtrace
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2001922/+attachment/5642994/+files/Xorg.0.log.old
--
Thanks. Unfortunately that doesn't contain the Xorg log that it should.
I don't know if that's because this is Xubuntu or because this is an
upgrade from 21.10 to 22.04.
On that note, you're also using an old kernel 5.13 which should have
upgraded to at least 5.15. But the old kernel is *probably*
This time it crashed almost instantly after logging in. There is a new
id in /var/crash/_usr_lib_xorg_Xorg.0.uploaded
be43a9e0-9103-11ed-9d0c-fa163e993415
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2001922/+attachment/5640509/+files/prevboot
Next time a crash happens please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.la
Two more crashes, this time without a new entries in /var/crash/.
What can I do to collect more information? The system was stable before I
upgraded from impish to jammy.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubu
Updated now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2001922
Title:
Xorg crash
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
My Ubuntu 22.04.1
It just happened again 3aa3f8c4-8f92-11ed-aafb-fa163e55efd0
In the logs I see
Jan 09 09:38:34 xlap whoopsie-upload-all[1059]:
INFO:root:/var/crash/_usr_bin_xfsettingsd.1000.crash already marked for upload,
skipping
Jan 09 09:38:34 xlap whoopsie-upload-all[1059]:
INFO:root:/var/crash/_opt_zoom_
Thanks, but there's still no stack trace info:
https://errors.ubuntu.com/oops/3aa3f8c4-8f92-11ed-aafb-fa163e55efd0
It's possible that the crashes might be rejected if your system isn't
fully up to date at the time of the crash so please make sure it is up
to date:
sudo apt update
sudo apt fu
It just happened again, the content of
/var/crash/_usr_lib_xorg_Xorg.0.uploaded is 3aa3f8c4-8f92-11ed-aafb-
fa163e55efd0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2001922
Title
That's fine, it just means Xorg crashed hard. So please report new
crashes whenever they occur again and eventually we'll have more luck.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bu
I don't see anything useful in the log:
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: sending the secret exchange:
[sx-aes-1]\npublic=4uc+8Lpm5dEaUqICltU/1RtAGdPAJRNDnjN+h4KK4+V198oPek0B866EgtZjQLXjDS9IA4iI+46VWpzNpyNd9hyBDrch5nR>
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: calling the PromptRe
No we can't process .crash files manually.
Can you check to see if Xorg logged messages about the crash in the
seconds prior to Thu Jan 5 14:09:26 2023?... Xorg likes to handle its
own crashes which sometimes causes us problems. We don't get clean crash
reports from Xorg, or that we don't get usef
The journal says contains these entries:
Jan 05 14:09:26 xlap systemd[1]: Starting Process error reports when automatic
reporting is enabled...
Jan 05 14:09:26 xlap systemd[1]: Started crash report submission.
Jan 05 14:09:26 xlap whoopsie[5359]: [14:09:26] Using lock path:
/var/lock/whoopsie/lo
Thanks. Unfortunately that's not showing the crash location, I don't
know why:
https://errors.ubuntu.com/oops/311e7093-8cfa-11ed-aae6-fa163e55efd0
Can you find the system log entries (using journalctl) from the time of
the crash? (Thu Jan 5 14:09:26 2023)
--
You received this bug notification b
The file contains this ID: 311e7093-8cfa-11ed-aae6-fa163e55efd0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2001922
Title:
Xorg crash
Status in xorg-server package in Ubuntu:
Please tell us the contents of /var/crash/_usr_lib_xorg_Xorg.0.uploaded
as it will contain the unique ID of the Xorg crash.
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this
27 matches
Mail list logo
