@sbeattie I tested the package you built for 22.04 and it fixes the
problem for me.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2060354
Title:
Segfaults and assertion failures in
@sbeattie It's broken in mantic too. In xwayland, the window dies. in
xorg, the session crashes, badly.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2060354
Title:
Segfaults and
Yeah, for me it crashed 100% of the time with no changes, and removing a
configuration file (which among other things removed my non-default
preference for grayscale antialias) completely stopped the crashing.
This is in a kvm/qemu VM. So from my perspective, and from a few others
users, it looks
for what it's worth, JetBrains bug reports find that the problem is
triggered by requesting grayscale anti-aliasing.
https://youtrack.jetbrains.com/issue/IDEA-350864/Idea.sh-abort-X-window
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Ubuntu 22.04.
I still have this problem
intel-media-va-driver 22.3.0
tigerlake laptop
$ apt-cache show intel-media-va-driver
Package: intel-media-va-driver
Architecture: amd64
Version: 22.3.0+dfsg1-1
tim@ochre:~$ vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open
No data available from (1) or (2) and the problem has not reoccurred.
I have commented line 23 of crashdb.conf
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1927767
Title:
All apps
I have been investigating other bug reports. I can't find anything that
helps my very much, but I did note references to timing. It is very
puzzling why I don't have problems when booting from the installation to
an external drive. That drive is actually a USB stick (ext4 formatted).
My internal
I have been trying to work out how to log a failed session with plymouth debug
messages. I finally succeeded, it is attached.
Note that at the end of log file, it goes into suspend. That was me trying to
power off the machine, and not holding the button long enough. It actually
suspends and
I installed 20.04 beta on a usb drive on the same machine, and reinstalled
packages to resemble my main install as closely as possible. The bug does not
occur when booting from the usb drive.
The most significant difference I can think of is that the main install is on
an lvm partition
** Attachment added: "boot messages with plymouth debugging messages"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5352286/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Summary changed:
- booting with splash hangs when external monitors are connected (pure intel
laptop)
+ booting with splash hangs when external monitors are connected (pure intel
8th gen laptop)
** Description changed:
+ I think this is a problem with the splash boot loader. This problem
** Summary changed:
- booting with splash hangs when external monitors are connected
+ booting with splash hangs when external monitors are connected (pure intel
laptop)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Attachment added: "journalctl -b-1 > journal.txt"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5351782/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Attachment added: "journalctl -b0 > journal.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872159/+attachment/5351769/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1872159
Title:
booting with splash hangs when external monitors are
@Alberto, couldn't prime-select do this when going into hybrid or
Optimus mode? Only users with nvidia hybrid graphics would go down this
logic path, and they are only ones who need the fix (but only if they
are using gdm3, sddm and lightdm continue to be unaffected by this)
The set of users who
This bug persists in 20.04 daily.
The one-line Pop!OS solution
(https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/comments/26)
works, just logout and login.
Pop!OS has used this for several releases now, just saying.
** Summary changed:
- nvidia-drm.modeset=1, gdm3 and optimus
I just installed popOS 19.10 an an Optimus laptop, nvidia option. Out of
the box you get gdm3 and tear-free prime-sync; it uses Jeremy Soller's
solution (root rights granted in Xwrapper)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
And PS: workaround continues to be: use lightdm, a five minute fix at
worst.
https://askubuntu.com/questions/139491/how-to-change-from-gdm-to-lightdm
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
19.10 beta and nvidia drivers 430 and 435 have the same problem. I have
made the bug title correctly specific.
** Summary changed:
- nvidia-drm.modeset=1 results in no monitors detected by Xorg
+ nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors
detected by Xorg
--
A very similar thing just happened to me, with the 435 drivers via ppa.
Reverting to 430 solved it. Ubuntu 19.04, P50. USB mouse works.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
This is not a new problem, and it affects every gdm3-based distro that I have
used. Long story short; if you want to use modeset=1 with nvidia to get rid of
tearing (which would be every linux Optimus user on the planet), gdm3 doesn't
work. No one seems to know why.
Change your display manager
I've been testing 1.19.x in 17.04 pre-release for a few weeks, hoping to
take advantage of the Nvidia PRIME synchronisation fix for laptops with
Optimus hybrid graphics. As of 1.19.3, PRIME sync works (with a modprobe
fix related to the nvidia driver). This is a huge improvement for nvidia
Optimus
My bug message is bad. The bug reporting indicates that it is actually a
kernel panic.
Please close this bug. automatic bug reporting was fixed when I changed the
login user to belong to group sudo.
see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1289721
and
Public bug reported:
Hardware is
*-display:0
description: VGA compatible controller
product: Mobile GM965/GL960 Integrated Graphics Controller
(primary)
vendor: Intel Corporation
physical id: 2
bus info: pci@:00:02.0
I have a Dell D420. The problem still exists in 12.10 although the fix from
comment #24 has fixed the problem after I logged out and back in.
tim@bach:~$ lspci -nn|grep -i vga
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics
Release notes for kubuntu 10.10 mention this bug and a workaround
(change configuration to force an xserver restart on logout). I didn't
read the release notes until after I filed the bug report.
--
xserver crashes on logout, can not login again
https://bugs.launchpad.net/bugs/659822
You
Public bug reported:
Binary package hint: xorg
kubuntu 10.10 with kde 4.5.2 from the kubuntu-ppa
xserver crashes on logout.
here is output from Xorg.log.0 with data about the crash at the end.
This bug is always reproducible.
Hardware is a dell latitude D420 with intel graphics.
It has been
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/659822/+attachment/1690638/+files/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/659822/+attachment/1690639/+files/CurrentDmesg.txt
** Attachment added: DRM.card0.SVIDEO.1.txt
29 matches
Mail list logo
