Setting the bug to Invalid because we know the cause of the "stuck at
640x480".
Separate to that it does look like some updates caused this by breaking
the previously installed Nvidia driver but I can't find much detail here
as to what went wrong.
** Package changed: xorg (Ubuntu) => ubuntu
**
Thanks for the bug report.
It appears you don't have a working graphics driver installed. Please
open the 'Additional Drivers' app and use it to install an Nvidia
driver.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Thanks for the bug report.
The main problem I can see here is that you have the kernel graphics
driver in debug mode. To fix that you will need to remove "drm.debug=0xe
plymouth:debug" from /etc/default/grub and then run:
sudo update-grub
and reboot.
If that doesn't fix the problem then I
** No longer affects: wayland (Ubuntu)
** Tags added: focal session wayland
** Tags removed: session
** Tags added: wayland-session
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to wayland in Ubuntu.
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 Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Just a reminder that most Ubuntu users can ignore this bug now because
most are getting Wayland by default instead.
--
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/1846398
Title:
** Package changed: ubuntu => xorg (Ubuntu)
--
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/2002349
Title:
I powered off and when I turned my computer on this hapened
To manage notifications
You have been subscribed to a public bug:
It's stuck at 640x480 and I can barely do anything at all
I'm using Ubuntu 20.04
I cannot even update my computer
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic
packages in main should not pull in packages in universe by default.
Either libnet-dns-perl needs to list libnet-libidn-perl as the first
alternative, or libnet-libidn2-perl needs to be promoted.
** Changed in: libnet-dns-perl (Ubuntu)
Status: New => Triaged
** Changed in: libnet-dns-perl
We have found that most of our users are Espanol speaking, So for a better
experience and enjoyable moment
https://wordle-unlimited.online/spanish-wordle/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
This means that you cannot simply guess the word right away; you must use the
clues given to you to figure out the secret word.
https://wordle-unlimited.us/wordle-junior/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati
This means that you cannot simply guess the word right away; you must use the
clues given to you to figure out the secret word.
https://wordle-unlimited.us/wordle-junior/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in
With these factors in mind, you’re sure to find
https://www.printersjet.com/best-sublimation-ink/ the best sublimation
inks for your needs. So what are you waiting for? Start shopping today!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
For testing I've created a PPA with the patches applied to 21.1.6:
https://launchpad.net/%7Ejeff250/+archive/ubuntu/xserver-xorg-with-
tearfree-modesetting
Since using it I haven't seen any tearing, and I haven't seen any new
issues (yet!) either.
--
You received this bug notification because
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 Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Changed in: mesa (Ubuntu Jammy)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1998893
Title:
NV reverse prime HDMI has no output
To manage
I think this bug/SRU snowballed. Let's take a step back.
It started with fixing two bugs: this one, and bug #1972977. At some
point later, #1972977 was deemed not really fixed[1], and was dropped in
the 0ubuntu0.3 upload[2].
That upload failed to build in jammy-proposed on arm64[3] and amd64[4].
Public bug reported:
i dont know much about those computer term,but if could you help me
somehow i would be very greatfull. thanx A.B.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.4.0-050400-generic x86_64
.tmp.unity_support_test.0:
ApportVersion:
** Description changed:
- This is a Hybrid graphics laptop with Ubuntu 22.10 and xserver-xorg-
- video-nouveau version 1.0.17-2build1.
+ This is a Hybrid graphics laptop with Ubuntu 22.10 (also happened with
+ 22.04) and xserver-xorg-video-nouveau version 1.0.17-2build1.
After locking the
** Description changed:
This is a Hybrid graphics laptop with Ubuntu 22.10 and xserver-xorg-
video-nouveau version 1.0.17-2build1.
After locking the screen manually or automatically after the specified
timeout, the whole laptop freeze or behave extremely slow, either ways a
hard
Public bug reported:
This is a Hybrid graphics laptop with Ubuntu 22.10 and xserver-xorg-
video-nouveau version 1.0.17-2build1.
After locking the screen manually or automatically after the specified
timeout, the whole laptop freeze or behave extremely slow, either ways a
hard reset is a must by
Thank you very much Christian for the confirmation (upstream as well)
and your further analysis of the issue. Your comment #12 (qemu-
system-x86_64 -display gtk) is also reflected in my observation in
comment #7.
I also appreciate your GDK_BACKEND=x11 ... workaround.
--
You received this bug
** Description changed:
+ Window actions (like maximize) no more work in wayland for QEMU using
+ GTK backend once the guest UI is intialized.
+
+ This can be seen by running an installed or even a trial Ubuntu from an
+ ISO like:
+
+ $ qemu-system-x86_64 \
+ -boot d \
+ -cdrom
Updated now.
--
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/2001922
Title:
Xorg crash
To manage notifications about this bug go to:
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]:
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1998893
Title:
NV reverse
the pci-id's were dropped from the jammy kernel for lp1990242
** Description changed:
[Impact]
The X failed to load glamoregl module on Dell's new platforms, the module is
needed by NV dGPU.
十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl"
十二 05 10:04:55
27 matches
Mail list logo
