I can confirm crash on latest 20.04 is still there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871959
Title:
Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
To manage not
Hello,
Thanks for your answers. I did a full update/upgrade and install latest
displaylink driver. I'll let you know if crash still here.
"X server crash in iris driver" subject is still open, no news since 8
months. Any way to know if it's still in progress or if it's on pause? I
just try to kno
Hello,
You spoke about a fixed in your comment on 2021-06-22
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1871959/comments/30
. Is that to say that no fix will be part of Ubuntu next LTS version
22.04?
I see your link on mesa. No reponse since 8 months. In your comment on
2021-03-05 you si
Hello Daniel,
So far I still have the issue on Ubuntu 20.04 LTS. Can you tell me if
the patch will be in next 22.04 LTS ? Or maybe there's a way to patch
20.04?
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Well, maybe or not but I don't understand how to install the patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871959
Title:
Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Hello,
Any news on when it will be solved ? No update solved it on my ubuntu
with officials updates.
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871959
Title:
Xorg crashed with SIGABRT
Hi,
Last message seems to indicate that a fix is found, good news! Anything
to do to get the fix?
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871959
Title:
Xorg crashed with SIGABRT in
Hello,
I sent a mail to DisplayLink, here is their answer...
"
Thank you for bringing it to our attention but based on the log files and
errors over there the best way would be to discuss it with Xorg engineers as
the majority of problems comes from the OS itself and not from our driver here.
"
Hi, thanks,
can't I just do a sudo apt purge linux-generic-hwe-20.04 ?
For now, i'll keep the choice to boot on kernel 5.8 or 5.4. About the
subject you opened on
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275 it seems to have
some news. That's very technical, can you put here information
Hello,
This is why you have no report from kernel 5.8+ :
"The supported kernel version range is from 4.15 to 5.5, minimum supported Xorg
version is 1.16 and minimum supported Mutter (Wayland) is 3.32."
https://support.displaylink.com/knowledgebase/articles/684649
Some people seems to have kern
Hello,
Well I tried... and have some troubles :). After reboot, displaylink didn't
work anymore. I tried to uninstall but when I try to reinstall, here what I
get :
ERROR (dkms apport): binary package for evdi: 1.7.0 not found
Error! Bad return status for module build on kernel: 5.8.0-43-gener
Hi,
I created an account on mesa forum. I don't really know what to tell,
and which file send them. Can you help me and tell me what to say and
send?
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
*** This bug is a duplicate of bug 1871959 ***
https://bugs.launchpad.net/bugs/1871959
Hi,
Ok thanks. In bug 1871959 you ask to report to mesa, what's "mesa"? I
don't think I have installed myself this. If it cause the bug, is it
possible to remove it?
Thanks,
--
You received this bug noti
Well if I couldn't use ubuntu bug, I could use that, hope it'll help :
apport-cli -c /var/crash/_usr_lib_xorg_Xorg.1000.crash
It then create this bug entry :
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1915375
--
You received this bug notification because you are a member of Ubu
Hi,
Ok, if there's nothing here about xorg crash, how may I provide you more
information about that :
ppaquin@PORTABLE-PPAQUIN:/var/crash$ ls -alrt
.
-rw-r- 1 username whoopsie 17322105 févr. 10 14:15
_usr_lib_xorg_Xorg.1000.crash
It seems I have some informations on my system abou
Oh I forgot, Yes, i have installed dbgsym :
$ dpkg -l| grep dbgsym
ii libgl1-mesa-dri-dbgsym:amd64 20.2.6-0ubuntu0.20.04.1 amd64 debug symbols for
libgl1-mesa-dri
ii xserver-xorg-core-dbgsym 2:1.20.9-2ubuntu1.2~20.04.1 amd64 debug symbols for
xserver-xorg-core
--
You received this bug notifica
Hi, one more crash for me, you'll find iris_dri error at 14:15:47 time
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1907142/+attachment/5462347/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1907142 ***
https://bugs.launchpad.net/bugs/1907142
Ok, seems installed, I'll report on the other bug id next time :
$ dpkg -l| grep dbgsym
ii libgl1-mesa-dri-dbgsym:amd64 20.2.6-0ubuntu0.20.04.1
amd64debu
*** This bug is a duplicate of bug 1907142 ***
https://bugs.launchpad.net/bugs/1907142
Yes it seems to be the same thing.
What can i do next to help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
*** This bug is a duplicate of bug 1907142 ***
https://bugs.launchpad.net/bugs/1907142
Hi,
I Have no idea for bu 1861398. Tell me if i can do anything.
Yes, i did #16 install when you asked it. I just did it again, seems I
can do it again with no warning. I expected something like "yet
insta
Hello,
I just had the crash. I send you the new curboot file for investigation.
I have a new entry on /var/crash, but no "uploaded" and i can't ubuntu-bug the
crash file. There's no entry on "Error reports" webpage. As the crash file is
"_usr_lib_xorf_Xorg.1000.crash", i did a "ubuntu-bug xorg"
Public bug reported:
follow up for https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1914573
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
.tmp.unity_support_test.0
I opened my session in Xorg this morgning. I only want one of Wayland or
Xorg to work, which one you think we have a better chance? You already
see some logs and probably have some idea about Xorg. My suggest is to
continue for this day with Xorg, I'll send you logs each time I get the
crash (I use
Hello,
You're true, I changed to Wayland because it seems to be the next
default of ubuntu, and it's recommended to use with Displaylink (even if
in the past it had some troubles). Whatever, I'll use Xorg as you ask
and I'll send you next crash information.
--
You received this bug notification
Another time, another log :).
Thanks for help.
** Attachment added: "curboot2.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5461238/+files/curboot2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Error tracker entry :
https://errors.ubuntu.com/oops/3d57ee6e-69f3-11eb-8529-fa163e102db1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914573
Title:
[DisplayLink] Xorg crashes and return to login
There's something new in /var/crash, I have a gnome-shell entry, with
uploaded file. Here is file
** Attachment added: "_usr_bin_gnome-shell.1000.uploaded"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5461215/+files/_usr_bin_gnome-shell.1000.uploaded
--
You
same file, after reboot.
** Attachment added: "prevboot3.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5461212/+files/prevboot3.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Hello,
I had the bug just now. It was a bit different, the screen freeze in a
strange way before "gnome reboot", so maybe it's different...
Here are the 2 files, before and after reboot just in case you need
both. They may be the same file or nearly.
** Attachment added: "curboot.txt"
https:
I assume I had to rename "ddeb" to "deb" in extension. I did that and
redo the journalctl command line. Here's the file it outputs.
I don't see anything different, but I don't realy know what i'm
searching (debug symbols). Hope that help.
** Attachment added: "prevboot.txt"
https://bugs.launc
Just one more description, for information... My bug is a crash of gnome
that redirect me to login screen, not a full reboot. So the shutdown
information at the end of the "prevboot.txt" are not related to the bug.
Lines begin to be strange there :
févr. 05 09:59:51 XX kernel: i915 :0
I see that in /var/crash directory :
-rw-r--r-- 1 someone whoopsie0 févr. 5 08:37
_usr_lib_xorg_Xorg.1000.upload
-rw--- 1 whoopsie whoopsie 37 févr. 5 08:37
_usr_lib_xorg_Xorg.1000.uploaded
drwxrwsrwt 2 root whoopsie 4096 févr. 5 09:59 .
-rw-r- 1 someone wh
about last Error tracker, the datetime is strange because crash occured
05/02 at about 10:0x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914573
Title:
[DisplayLink] Desktop crashes and return to
Here is the new entry on Error tracker :
https://errors.ubuntu.com/oops/00b2327a-6785-11eb-9850-fa163e983629
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914573
Title:
[DisplayLink] Desktop crashe
I just have the gnome crash to login now. I join the result of the command :
journalctl -b-1 > prevboot.txt
Thanks for help
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5460445/+files/prevboot.txt
--
You received this bu
there's no more uploaded file for xorg crash... I'll do what you ask on
next crash and reboot.
I found the origin of the gnome-shell entries in journalctl, they came
from chrome. I try to not use it today and we'll see if I have no more
gnome crash. I have no idea if it's related but it's not, I'l
the uploaded file.
** Attachment added: "_opt_displaylink_DisplayLinkManager.0.uploaded"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5460225/+files/_opt_displaylink_DisplayLinkManager.0.uploaded
--
You received this bug notification because you are a member
Hello,
1. I have 3 crash files in /var/crash but the ubuntu-bug command fail.
Each one has a ".upload" and ".uploaded" file so I think they're already
uploaded. Shall I empty the folder to have a clean start point for next
time the bug appear?
2. Many files in this page. These are the 3 related w
By the way, my "journalctl" is full of this, maybe related, maybe not...
févr. 05 07:36:11 PORTABLE-USERNAME gnome-shell[3662]: Errors:
févr. 05 07:36:11 PORTABLE-USERNAME gnome-shell[3662]:
[4886:4886:0205/073611.340319:ERROR:shared_context_state.cc(74)] Skia shader
compilation error
févr. 05 0
Public bug reported:
The bug is that all at a sudden gnome reset to login screen. When i log
again, the only "sound output" allowed is simulation, my devices are not
displayed.
I'm using
- Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug was
present at that moment but i
40 matches
Mail list logo
