Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
I don't see any random logouts in the attached logs. Let's treat it as a
crash anyway...
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run
It sounds like you're reporting multiple unrelated issues here. Please
be careful to only report one issue per bug report.
* kernel: ACPI Error: are BIOS bugs and can be safely ignored in most
cases. Also Ubuntu can't fix those.
* Random log out: Sounds like the biggest issue so let's focus on th
I'm using regular, vanilla Ubuntu, running bare metal on a laptop.
Apologies for pointing at PAM without knowing, but it was the best I
could come up with.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https:
** Also affects: pam (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2080821
Title:
Custom caps lock action inconsistent on
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it
^^^
Still isn't in Oracular in case anyone was wondering.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1869655
Title:
Boot animations start too late to be useful
*** This bug is a duplicate of bug 2076869 ***
https://bugs.launchpad.net/bugs/2076869
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2076869, so it is being marked as such. Please look
Assuming the bug is in journal-1.txt, it looks like the nouveau kernel
graphics driver that's crashing. To solve that I suggest installing an
official Nvidia driver from the 'Additional Drivers' app.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- Xorg freeze
+ [nouvea
** Package changed: xorg (Ubuntu) => libreoffice (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2080806
Title:
wrong font size is displaying on editing
Status in li
Reverting to mirror mode suggests the system doesn't recognise the new
config on wakeup as being equal to the old config before sleeping.
One of your configurations in ~/.config/monitors.xml seems to contain a
disabled "unknown" monitor which likely was bug 2060268. So I suggest:
1. Make sure you
** Tags added: multimonitor nvidia
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2080782
Title:
Problems when my computer monitors go to sleep
Status in xorg package in Ubu
** Summary changed:
- Bluetoth turning off every reboot and i need to reinstall e restart the
modules everytime
+ [QCA9377] Bluetoth turning off every reboot and i need to reinstall e restart
the modules everytime
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2062951, so it is being marked as such. Please look
It appears there are hidden settings internally:
org.gnome.desktop.a11y.keyboard mousekeys-accel-time 300
org.gnome.desktop.a11y.keyboard mousekeys-enable false
org.gnome.desktop.a11y.keyboard mousekeys-init-delay 300
org.gnome.desktop.a11y.keyboard mousekeys-max-speed 10
You can adjust t
** Summary changed:
- ラップトップをタブレットとして使用する際画面回転を認識しない
+ [Lenovo Yoga 7 14ARB7] Screen rotation support is intermittent
** Package changed: xorg (Ubuntu) => linux-hwe-6.8 (Ubuntu)
** Also affects: iio-sensor-proxy (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-shell (
Thanks Jack. Your system I expect will suffer from all of these due to
the Quadro K4200 being limited to Nvidia driver 470:
* https://gitlab.gnome.org/GNOME/mutter/-/issues/3196 (fixed in Mutter 47.rc)
* https://gitlab.gnome.org/GNOME/mutter/-/issues/3464 (fixed in Mutter 47.rc)
* Bug 206208
*** This bug is a duplicate of bug 2066353 ***
https://bugs.launchpad.net/bugs/2066353
Yes please click that link and submit the requested info in bug 2066353.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubunt
Nvidia users might have bug 2062082 to blame here. Please try:
sudo apt install libnvidia-egl-wayland1
and reboot. So maybe it's really two issues:
* Nvidia is using Zink when it shouldn't (bug 2062082)
* For non-Nvidia systems that might need Zink, it doesn't work (bug 2066353)
--
You r
Thanks for the bug report. It looks like the machine is missing an
Nvidia kernel driver (and failed to use the open source driver). Please
try installing a new driver through the 'Additional Drivers' app. I
expect only Nvidia driver 470 supports the GT 730.
After rebooting, if that hasn't fixed th
** Summary changed:
- Wrong screen resolution
+ Wrong screen resolution (missing nvidia kernel module)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2080266
Title:
Wrong sc
Everyone affected; please run:
lspci -k > lspci.txt
dpkg -l > packages.txt
and attach the resulting text files here.
Also if anyone has the skills to test patches then please try:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30479.patch
(from bug 2075549 which I think Marco
See also bug 2066353.
** Tags added: zink
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2075549
Title:
Running gtk applications in compositor supporting only shared memory
> wondering why Ubuntu never noticed this during the beta phase??
The answer appears to be at the top of the page ("This bug affects 6
people"). So not many people (and apparently zero developers) have
encountered the bug.
** Tags added: jammy noble
** Tags removed: jammy
--
You received this
*** This bug is a duplicate of bug 2066353 ***
https://bugs.launchpad.net/bugs/2066353
Great, that's a workaround. The main issue here (at least what looks
like the main issue) is already being tracked in bug 2066353.
** Package changed: gdm3 (Ubuntu) => mesa (Ubuntu)
** Summary changed:
-
** Package changed: xorg (Ubuntu) => thunar (Ubuntu)
** Summary changed:
- Xfce interface display problem
+ [fbdev] Xfce interface display problem
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.
** Also affects: pipewire (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2080192
Title:
High fidelity playback won't be
*** This bug is a duplicate of bug 2063557 ***
https://bugs.launchpad.net/bugs/2063557
Ah yes, confirmed that logo.png in unity-greeter_23.10.1-0ubuntu4 does
say "23.10". It must have been corrected during packaging. And that's
the package version also used by Ubuntu 24.04 (see
https://launchp
Public bug reported:
The utility 'file' reports different mime-types depending on the content
length of a text file with just multiple times 'X' as content.
For a file with 5789792 times the letter 'X' as content the 'file' tool returns
'application/SIMH-tape-data' as mime-type.
With just 1 lett
I don't think BlueZ is involved here. It's the libinput Xorg driver
that's claiming anything with buttons as a keyboard. Although this may
need to be patched as a udev rule in udev, systemd, or somewhere else.
So shipping the rule in 'bluez' may still make sense.
** Also affects: xserver-xorg-inpu
Thanks for the bug report. While the problem is happening, please open a
virtual terminal (Ctrl+Alt+F4) and run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You r
Also reported in:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7508
https://gitlab.gnome.org/GNOME/mutter/-/issues/3477
https://gitlab.gnome.org/GNOME/mutter/-/issues/3340
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7508
https://gitlab.gnome.org/GNOME/gnome-shell/-/i
Curiously, the current source for unity-greeter contains a logo.png that
says "ubuntu 13.10", not 23.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/2078959
Title:
Thanks for the bug report.
Please try removing all local extensions:
cd ~/.local/share/gnome-shell
rm -rf extensions
and then log in again. Does the bug still occur?
** Tags added: focus
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: New
Hi Sam,
The popup is "needed" because special permission is required to "create
a color managed device." This is typically relevant to fancy color-
corrected computer displays and the like. The problem is that when you
are logging in via a remote connection like VNC or RDP, there is no
directly-co
I'm going to call this a bug in gst-plugins-good1.0 too. Because it
sounds like libvpx is failing to use transparency in libgstvpx.so, yet
working in FFmpeg (ffmpeg -c:v libvpx-vp9).
** Also affects: gst-plugins-good1.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this b
Thanks. I'm still not sure what package that image comes from, but
here's a first guess.
** Package changed: ubuntu => unity-greeter (Ubuntu)
** Changed in: unity-greeter (Ubuntu)
Status: Incomplete => New
** Also affects: ubuntu-themes (Ubuntu)
Importance: Undecided
Status: New
It looks like the image viewer app has leaked override redirect windows.
Although that suggests to me it's still running?
If you run 'xwininfo -all' and then click on the artifacts, does it
reveal where they come from?
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnom
Thanks for the bug report. It appears this USB device is the wireless
receiver for the mouse:
Bus 001 Device 007: ID 3151:3020 YICHIP Wireless Device
and some googling is telling me that other people have connection
problems with the same device.
Since the wireless part of this setup is done e
Thanks for the bug report. That kernel looks old and should have been
updated by now. Please try:
sudo apt install linux-generic-hwe-22.04
and reboot.
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New => Incomplete
--
You r
Thanks for the bug report. That kernel looks old and should have been
updated by now. Please try:
sudo apt install linux-generic-hwe-22.04
and reboot.
** Summary changed:
- I cannot change or control display brightness
+ [Lenovo LOQ 15ARP9] I cannot change or control backlight brightness
**
Thanks for the bug report. First we should check to see if the problem
is specific to GNOME/Xorg or coming from the kernel. You can do this by
pressing Ctrl+Alt+F4 and logging into a virtual terminal. Does the bug
still occur there?
To return to GNOME, press Alt+F2.
** Package changed: xorg (Ubun
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
Please:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you
*** This bug is a duplicate of bug 2063827 ***
https://bugs.launchpad.net/bugs/2063827
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2063827, so it is being marked as such. Please look
Also was there an assertion in the journal?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2078280
Title:
System Crash on reboot/screen lockout: systemd-logind crashed wit
Looks like it's still a common issue:
https://errors.ubuntu.com/?package=systemd&period=week
but we'd need the crash ID or the machine's whoopsie ID to tell which
instance this is.
** Package changed: xorg (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New => Inco
Please explain in more detail what kind of problem you are experiencing.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg
Thanks for the bug report. I can see two main problems here:
1. The amdgpu kernel graphics driver is emitting warnings that look like
crashes.
2. The rtw_8821ce kernel wifi driver is flooding the system log (this is
probably the performance issue).
So I can only suggest trying an older Ubuntu r
** Package changed: ubuntu-release-upgrader (Ubuntu) => gtk+3.0 (Ubuntu)
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2049578
Title:
Not loading mo
*** This bug is a duplicate of bug 2049578 ***
https://bugs.launchpad.net/bugs/2049578
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2049578, so it is being marked as such. Please look
It looks like you triggered the screen magnifier. Try holding the
Windows key and pressing +/- or =/-
Please also run this command to collect more system information:
apport-collect 2077825
** Package changed: xorg (Ubuntu) => plasma-desktop (Ubuntu)
** Changed in: plasma-desktop (Ubuntu)
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2077822
Title:
Bluetooth killing headphones
Thanks for the bug report. It looks like mutter-x11-frames is
segfaulting repeatedly. That's probably not helping. Let's treat this as
a crash and see what else might be crashing. Please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.t
** Package changed: xorg (Ubuntu) => linux-hwe-6.8 (Ubuntu)
** Package changed: linux-hwe-6.8 (Ubuntu) => linux (Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
Unfortunately all forms of smooth scrolling are toolkit or app-specific.
So we will make this one about Firefox.
** Package changed: xorg (Ubuntu) => firefox (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ub
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1861609, so it is being marked as such. Please look
** Tags removed: gnome-shell-leak
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2077254
Title:
GNOME session is shut down during OOM and returns back to login screen
Sta
Nvidia driver 555 is not supported by Ubuntu for now:
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-555
But it sounds like you have hit bug 1975650, so if the driver is from a
PPA then you can try something like:
sudo apt install linux-modules-nvidia-555-`uname -r`
** Package
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2077612
Title:
Slow X11 performance through ssh
Status in xorg-serve
** Tags added: udeng-4096
** No longer affects: dbus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/2077451
Title:
GNOME 47: GNOME apps don't launch for around the
** Changed in: xdg-desktop-portal-gnome (Ubuntu)
Milestone: None => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/2077451
Title:
GNOME 47: GNOME apps don't
Maybe it isn't extensions either. The bug does NOT happen with upstream
gnome-shell even with extensions. Is a distro patch to blame?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/b
My Nautilus does not crash. I just interrupted it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/2077451
Title:
GNOME 47: GNOME apps don't launch for around the first 20 sec
I can avoid the bug by disabling ALL extensions. Just disabling one
extension doesn't help. So this feels like gnome-shell is blocking G-app
registration if extensions are loaded.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
nautilus while failing to display:
#0 0x7c6fd4f1ba00 in __GI_ppoll
(fds=0x6097f0a42f90, nfds=1, timeout=, sigmask=0x0)
at ../sysdeps/unix/sysv/linux/ppoll.c:42
#1 0x7c6fd6615d11 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7c6fd65b5eb7 in g_main_loop_run () at
/
It appears the messages in the bug description are actually status
messages from the kernel, and not bluetoothctl commands. So the UI
design of bluetoothctl is a little misleading. But it makes me think
even more that this is a kernel issue. Also I can't reproduce the
problem here.
Please see comm
This sounds like it's chip-specific. Please run:
lsusb > lsusb.txt
lspci > lspci.txt
dmesg > dmesg.txt
and attach the resulting text files here.
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch
Thanks. Those crash reports are from 1-2 years ago so don't look
relevant.
journal.txt seems to show the problem. The system ran out of memory at
Aug 18 10:08:14 but gnome-shell kept running. It was then told to shut
down cleanly by systemd and you can see the clean shutdown a few seconds
later at
Based on the description I think this is most likely to be bug 2037055.
But to be sure, please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash for crash files and if f
As a workaround, please try adding this to /etc/environment:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
and reboot.
** Tags added: i915 psr regression-update
** Package changed: xorg (Ubuntu) => linux-hwe-6.8 (Ubuntu)
** Changed in: linux-hwe-6.8 (Ubuntu)
Importance: Undecided => Medium
** Summa
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2062951, so it is being marked as such. Please look
And why would we delay the login screen waiting for Chromium to be
mounted? Surely that should only delay your ability to launch Chromium.
** Package changed: mysql-8.0 (Ubuntu) => chromium (Ubuntu)
** No longer affects: apt (Ubuntu)
--
You received this bug notification because you are a membe
It sounds like you're referring to OBEX used to transfer files between
devices. But also since you're using Unity 7, I don't know what other
legacy components might be getting in the way here.
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu
Please explain what kind of messages you are talking about.
** Summary changed:
- the system bluetooth manager doesn't receive any messages and hardly send
them to paired devices. already have the problem with the 16.04, apparently not
fixed in your 24.04 release.
+ [Intel 8265] the system blu
Just in case killing the shell is *correct*, please ensure you don't
have any local extensions installed:
cd ~/.local/share/gnome-shell
rm -rf extensions
and then log in again. Because extensions are the main cause of shell
memory leaks, and it looks like there is one:
[522352.701692] [
For most people, having too many browser tabs or virtual machines open
will be the trigger for this. But we should also discuss the correctness
of killing the shell via systemd-oomd.
** Package changed: xorg (Ubuntu) => systemd (Ubuntu)
** Summary changed:
- GUI crashes and returns back to login
Thanks for the bug report. Please try this for a little while to see if
the bug goes away:
gnome-extensions disable ubuntu-d...@ubuntu.com
** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock
(Ubuntu)
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Ne
Please also try adding the 'fastboot' kernel parameter in case this is
related to Plymouth waiting for some slow file system checks.
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu)
Status: New => Incomplete
** Changed in: mysql-8.
It looks like the main culprit is apt-daily-upgrade.service, so does
that show up on every slow boot? Or does apt-daily-upgrade.service go
away and only mysql.service is left as the main bottleneck?
** Package changed: gnome-shell (Ubuntu) => apt (Ubuntu)
** Also affects: mysql-8.0 (Ubuntu)
Im
We'll know for sure when bug 2051574 stops dominating the top of the crash list:
https://errors.ubuntu.com/?release=Ubuntu%2024.04&package=gnome-shell&period=week
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubu
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2077290
Title:
GLArea transparency broken
Status in gtk+3.0 package in Ubuntu:
Fix Released
Status i
It sounds like Security might have just fixed it indirectly;
"debian/rules: build with portal_helper=false to use the default
browser instead of the embedded webkit2gtk browser."
https://launchpad.net/ubuntu/+source/gnome-shell/46.0-0ubuntu6~24.04.3
--
You received this bug notification beca
Yes there are lots of kernel warnings from the nvidia driver. I can't
tell if they're fatal but they're certainly the only problem I can see
right now.
In case your main "crash" has a different cause, please follow these
steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalct
Thanks for the bug report.
We will need to see a boot log that's not in recovery mode. Please
reproduce the bug again, then reboot into recovery mode and run:
journalctl -b-1 > prevboot.txt
And attach the resulting text file here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: u
** Package changed: bluez (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2076407
Title:
Title: Bluetooth 5.4 Adapter (Ugreen CM749) Not Functionin
** Package changed: xorg (Ubuntu) => kwin (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2076495
Title:
Display Configuration is not remembered with external monitor
Please describe what kind of problem you are experiencing.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
h
Please tell us what kind of problem you are encountering.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
ht
Please tell us what kind of problem you are encountering.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
htt
Thanks for the bug report.
Most intermittent black screen flickers are caused by a loss of display
signal integrity. It's especially common at high resolutions or refresh
rates (I notice you're using 4K). That can usually be fixed by replacing
the display cable and/or taking the dock out of the eq
*** This bug is a duplicate of bug 1997550 ***
https://bugs.launchpad.net/bugs/1997550
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1997550, so it is being marked as such. Please look
Thanks for the bug report. If you can then please try a USB-C monitor
cable, you should be able to find one that is HDMI on the other end.
That will allow you to avoid running the signal through the Nvidia card
and should provide a better experience.
Please also try selecting 'Ubuntu on Wayland' f
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
Thanks for the bug report. Next time the problem happens, immediately
after rebooting run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Tags added: multimonitor
** Package changed: wayland (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status:
The crash is probably bug 2050865 which is rolling out in automatic updates
this week. And since you're using Xorg it's possible that crash is happening
even more often than you know, because gnome-shell will just automatically
restart on Xorg with apps still running. So if you don't already hav
*** This bug is a duplicate of bug 1876632 ***
https://bugs.launchpad.net/bugs/1876632
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1876632, so it is being marked as such. Please look
Thanks for the bug report. Please try adding this to /etc/environment:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
and then reboot.
** Summary changed:
- Top margin of secondary monitor covered with black flickering rectangle
+ [nouveau] Top margin of secondary monitor covered with black flickering
r
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
Please try adding kernel parameter:
i915.enable_psr=0
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notifi
Thanks for the bug report. Please attach a video or photo of the
problem. You can create either by pressing PrtScn.
** Tags added: nouveau
** Package changed: xorg (Ubuntu) => ubuntu
** Summary changed:
- smash the window
+ [nouveau] menu turns on and off at a very high speed
** Changed in: ub
1 - 100 of 1004 matches
Mail list logo
