Before plugging in this 3rd monitor both of my screens (the ones in red
and blue colors) were close to another without any green space in
between them.
Of course in order to reach the spawned desktop in between any of those
monitors I need to drag the mouse quite a long road before it reaches as
Public bug reported:
I have just upgraded from dual monitors by adding one up now up to
three.
Detecting the monitor went ok. However recalibration messed up my screen
positions.
Another issue is that when attempting to recreate physical setup under
"monitor preferences" isn't very friendly.
Spinning forever sounds like a different problem from failing to render,
perhaps?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2023322
Title:
GTK internal
After more testing it seems that regardless on which workspace the
browser was in before going into full screen that it will end up on the
opposite workspace after getting unmaximized.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
Using 2x screens in portrait mode, if I display my browser on the right-
side panel of workspace 1, watch a video and full screen it, after I
off the video the browser will now be displayed on the left-side
panel of workspace 1.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
And as always, everything is in:
https://git.launchpad.net/~bluetooth/bluez
--
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/2036149
Title:
BlueZ release 5.70
Status in
** Attachment added: "bluez_5.70-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2036149/+attachment/5713325/+files/bluez_5.70-0ubuntu1.debian.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "bluez_5.70.orig.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2036149/+attachment/5713323/+files/bluez_5.70.orig.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
** Changed in: bluez (Ubuntu)
Milestone: None => ubuntu-24.01
--
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/2036149
Title:
BlueZ release 5.70
Status in bluez package
Verified working in webkit2gtk 2.42.1-2.
Tested Nvidia 535 with both X11 and Wayland, in both Online Accounts and
Ubuntu Desktop Guide.
** Changed in: webkit2gtk (Ubuntu)
Status: In Progress => Fix Released
** Changed in: yelp (Ubuntu)
Status: Triaged => Invalid
** Changed in:
** Changed in: bluez (Ubuntu)
Status: Triaged => In Progress
** Tags added: noble
--
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/2036149
Title:
BlueZ release 5.70
It looks like there are recurring problems coming from the Nvidia kernel
driver here, but let's start with this:
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
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2040657
When reporting bugs in the future please use apport by using 'ubuntu-
Public bug reported:
The command /usr/bin/look prints only words that begin with an upper-
case letter, even if the search string begins with a lower-case letter.
$ look big
BigQuery
BigQuery's
Bigfoot
Bigfoot's
Biggles
Biggles's
This is incorrect behavior. "look" should also print words like
Oh I see you have unsupported Mesa packages installed and I can't tell
where those came from:
23.2.0.20230712.1-2073~22.04
You can get the correct packages from:
https://launchpad.net/ubuntu/+source/mesa/23.0.4-0ubuntu1~23.04.1/+build/26314308
but it might be easier to just reinstall Ubuntu.
Your GPU is detected and working as far as I can tell.
What is the problem you are seeing?
--
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/2040318
Title:
GPU not found
The purpose here is to evaluate what can be moved from Minimal to Full.
The size of the Full install would not change but the size of Minimal
should be smaller.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7062
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
** Summary changed:
- Ubuntu default/minimal installation should be smaller
+ Ubuntu default/minimal installation is only ~11% smaller than full
installation
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
I can see bug 1861609 happening in XorgLogOld.txt, but also you seem to
have a few vbox-related kernel crashes. Overall I think this is bug
1861609 which seems to be common on VirtualBox.
The matter of two
See also bug 1899971
** Changed in: xorg (Ubuntu)
Importance: Undecided => Low
** Changed in: xorg (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
#0 __GI_getenv (name=0x7fc095eefdd8 "EXPAT_ACCOUNTING_DEBUG") at
./stdlib/getenv.c:31
ep = 0x559dca3a7720
len = 22
#1 0x7fc095eee73f in ?? () from /lib/x86_64-linux-gnu/libexpat.so.1
No symbol table info available.
#2 0x7fc095ed4f88 in ?? () from
Thanks for the crash file. That's certainly a segfault so let's make
this bug about that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2039340
Title:
gnome-shell
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
** Summary changed:
- Unable to setup Google Online Accounts with Nvidia drivers
+ GTK internal browser does not render with Nvidia drivers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2023322
Title:
Unable to setup Google Online Accounts with Nvidia drivers
Status in
Thanks for the bug report. Can you explain in more detail where and when
you see the error?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Summary changed:
- Nwidia driver Ubuntu bug
+ Nvidia driver Ubuntu bug
** Package changed: ubuntu
** Summary changed:
- [amdgpu] Screen artifacts/UI oddities on Wayland following Steam/Proton
session
+ [amdgpu] Screen artifacts/UI oddities on Wayland
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: mesa (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Also just in case you've found a new form of bug 2034619 please try
adding this to /etc/environment:
MUTTER_DEBUG_KMS_THREAD_TYPE=user
and then reboot.
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Package changed: xorg (Ubuntu) => 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/2039391
Title:
pakage broken
Status in Ubuntu:
Incomplete
Bug description:
There's also a lot of this in the journal:
GNOME Shell crashed with signal 11
so to help us find the cause of the crash please follow these steps:
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
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: nvidia suspend-resume
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 2034619 ***
https://bugs.launchpad.net/bugs/2034619
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 2034619, so it is being marked as such. Please
Also reported in:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7062
** Package changed: xorg (Ubuntu) => mesa (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7062
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
Public bug reported:
Ubuntu default/minimal installation should be made smaller in future.
It's a little too close to the full install size right now. As of mantic
2023-10-10, the default/minimal install ends up 8.4 GB whereas the full
install is 9.4 GB.
*** This bug is a duplicate of bug 1980889 ***
https://bugs.launchpad.net/bugs/1980889
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 1980889, so it is being marked as such. Please
This is usually a problem with display connection quality. Please try a
different HDMI cable.
Also next time the problem happens please run:
journalctl -b0 > journal.txt
grep . /sys/class/drm/*/status > connections.txt
sudo apt install drm-info
drm_info > drminfo.txt
and attach the
** Summary changed:
- bluetooth not working proper;ly
+ Intel AX210 Bluetooth not working properly in focal kernel 5.15
** Package changed: bluez (Ubuntu) => linux-hwe-5.15 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: mesa (Ubuntu)
Milestone: mantic-updates => ubuntu-23.10
--
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/2037497
Title:
gnome-shell crashes on Intel Ice
** No longer affects: mutter (Ubuntu)
** No longer affects: mutter
--
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/2037497
Title:
gnome-shell crashes on Intel Ice Lake with
*** This bug is a duplicate of bug 1976276 ***
https://bugs.launchpad.net/bugs/1976276
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 1976276, so it is being marked as such. Please
Upstream found the fix:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24045
** Changed in: mesa (Ubuntu)
Milestone: ubuntu-23.10 => mantic-updates
** Tags added: fixed-in-mesa-23.3 fixed-upstream
** Changed in: mesa (Ubuntu)
Status: Confirmed => Triaged
** Summary
Thanks for the bug report. Please run the following commands:
sudo apt install drm-info
drm_info > drminfo.txt
grep . /sys/class/drm/*/status > connections.txt
and then attach the two resulting text files here.
** Tags added: multimonitor
** Package changed: xorg (Ubuntu) => ubuntu
**
Please report the bug to Upscayl. Although it is possible the cause is
the driver issue here so I'll make that more clear in the bug title...
** Summary changed:
- upscayl software do not work
+ MESA-INTEL: warning: Haswell Vulkan support is incomplete
** Changed in: mesa (Ubuntu)
I don't know if this counts as "do not work", but it seems clear that
Mesa's Vulkan driver for Haswell is incomplete and it's fallen back to
LLVM (software rendering). That should "work" very slowly still. Was
there actually any error?
Also this change to your system is not supported by Ubuntu:
** Changed in: mesa (Ubuntu)
Milestone: None => ubuntu-23.10
** Changed in: mutter (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
*** This bug is a duplicate of bug 2020183 ***
https://bugs.launchpad.net/bugs/2020183
** This bug has been marked a duplicate of bug 2020183
i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state
--
You received this bug notification because you are a member of Ubuntu
Dropped severity because this bug is proving elusive. Most of us are
never seeing it, even when we try with similar hardware.
** Changed in: mesa (Ubuntu)
Importance: Critical => High
** Changed in: mutter (Ubuntu)
Importance: Critical => High
--
You received this bug notification
Bug confirmed but it does unfortunately result in bug 2015857, and no
assertion mentioned in the system log.
I think the circumstances are consistent with bug 2036889 though
(asserting on X11 session shutdown), so we should focus on fixing that
first.
** No longer affects: ubiquity (Ubuntu)
**
** Bug watch added: github.com/ubuntu/yaru/issues #3977
https://github.com/ubuntu/yaru/issues/3977
** Also affects: yaru via
https://github.com/ubuntu/yaru/issues/3977
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- BlueZ release 5.69
+ BlueZ release 5.70
** Description changed:
- Update to BlueZ 5.69 (or later) in Ubuntu 24.04
+ Update to BlueZ 5.70 (or later) in Ubuntu 24.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Tags added: mantic
** Summary changed:
- Bluetooth LE not working after upgrade from 22.04 to 23.10
+ [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10
** Package changed: ubuntu => linux (Ubuntu)
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status:
I can see Xorg crashing in XorgLogOld.txt but the lack of debug symbols
makes the stack trace wildly inaccurate so please:
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
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
Oh sorry, I missed the "legacy" part. I'll try and reproduce it this
week.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2036440
Title:
Choosing "Try Ubuntu" on
** Package changed: xorg (Ubuntu) => yaru-theme (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/2037698
Title:
Icon theme changed after recent update
Status in
** Tags added: mantic raspi raspigfx
** Tags removed: raspigfx
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2037642
Title:
[FFe] Raspberry Pi 5 support
Status
Tracking in: https://gitlab.freedesktop.org/mesa/mesa/-/issues/9889
** Also affects: mesa via
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9889
Importance: Unknown
Status: Unknown
** Bug watch added: Red Hat Bugzilla #2238711
It appears 'pipe' is NULL in the Mesa source at:
static void
end_query(struct gl_context *ctx, struct gl_query_object *q)
{
struct st_context *st = st_context(ctx);
struct pipe_context *pipe = ctx->pipe;
bool ret = false;
st_flush_bitmap_cache(st_context(ctx));
if ((q->Target ==
It looks like the window is taller than the screen and the mutter
constraints logic is in a loop?
Please try maximizing the window to see if the problem stops.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received
I can't think of a good solution here, but if you would like the same
"safe graphics" mode that also happens to disable the GPU, then you can
edit /etc/default/grub and change:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
and then run:
** Tags added: regression-release
--
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/2037497
Title:
gnome-shell crashed with SIGSEGV in ?? (iris_dri.so) from end_query()
from
Looks like it's related to this update:
https://launchpad.net/ubuntu/+source/mesa/23.2.0~rc4-1ubuntu1
** Summary changed:
- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in ?? (iris_dri.so) from end_query() from
cogl_gl_create_timestamp_query() from
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
Also mentioned in bug 2017224
--
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/2037212
Title:
ConfigurationDirectory 'bluetooth' already exists but the mode is
different.
Can you explain in more detail what you mean by "monitor crashes"?
** 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
Unfortunately that log doesn't contain a gnome-shell crash.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2036440
Title:
Choosing "Try Ubuntu" on daily-legacy image
I recall this bug was reported around last cycle too. But I wonder; is
it specific to Nvidia desktops like bug 1876632?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
** Tags added: amdgpu
** Summary changed:
- Xorg freeze
+ [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0 [amdgpu]
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Summary changed:
- [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0
** Summary changed:
- package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso
instalado paquete bluez script post-installation devolvió el código de salida
de error 1
+ package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso
instalado paquete bluez script
*** This bug is a duplicate of bug 2012388 ***
https://bugs.launchpad.net/bugs/2012388
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 2012388, so it is being marked as such. Please
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (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/2036802
Title:
HDMI not detected on HP Zbook Power 15 G9
Status
I have more questions than answers now...
* It looks like source_gnome-shell.py already attaches journalctl
output, so why didn't it here?
* data/general-hooks/generic.py also attaches journal errors, so why
didn't it here?
* Do we really want all Ubuntu bug reports to have journal data that
I meant all bug reports, not just gnome-shell. But gnome-shell is the
best place to start.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2036440
Title:
Choosing "Try
Indeed I've been meaning to learn about apport because I would like ALL
bug reports to automatically come with:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
*** This bug is a duplicate of bug 2036428 ***
https://bugs.launchpad.net/bugs/2036428
Looks like kernel 6.5 is missing required firmware?
[ 38.846558] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 38.846638] Bluetooth: hci0: Failed to load Intel firmware file
It missed the 45.0 tag and gnome-45 branch so currently only exists in
future release 46. Hopefully it will get cherry picked into 45.
** Tags added: fixed-upstream
** Tags added: fixed-in-gsettings-desktop-schemas-46
--
You received this bug notification because you are a member of Ubuntu
Signal 6 is SIGABRT which usually means an assertion failed, which means
the system log will contain an explanation. Next time it happens please
run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Changed in: gnome-shell (Ubuntu)
Status: Invalid => Incomplete
** Summary changed:
- Printing Ubuntu Bold font - strange symbol
+ Cyrillic characters not spaced correctly when printing with Ubuntu Bold font
** Changed in: fonts-ubuntu (Ubuntu)
Status: Incomplete => New
** Also affects: cups (Ubuntu)
Importance: Undecided
Status: New
--
** Changed in: mesa (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-mesa-23.3
--
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/2034672
Title:
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
*** 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
*** This bug is a duplicate of bug 2020183 ***
https://bugs.launchpad.net/bugs/2020183
** This bug has been marked a duplicate of bug 2020183
i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 2020183 ***
https://bugs.launchpad.net/bugs/2020183
** This bug has been marked a duplicate of bug 2020183
i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 2020183 ***
https://bugs.launchpad.net/bugs/2020183
** This bug has been marked a duplicate of bug 2036159
i915 keeps crashing with "pipe state doesn't match!" in verify_crtc_state
#4
** This bug is no longer a duplicate of bug 2036159
i915 keeps
Public bug reported:
Update to BlueZ 5.69 (or later) in Ubuntu 24.04
** Affects: bluez (Ubuntu)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Thanks for the bug report. There is no software brightness adjustment on
desktop machines. You need to adjust the brightness on the monitor
instead.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you
I'm guessing the HDMI port is connected to the Nvidia GPU, it usually is
on a hybrid laptop. And I'm seeing that you don't have a proper driver
for the Nvidia GPU installed. Please open the 'Additional Drivers' app
to install a supported Nvidia driver.
** Package changed: xorg (Ubuntu) => ubuntu
It's not surprising if 0908.2 doesn't have the workaround. It didn't
land for a day or so after that.
--
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/2034672
Title:
(Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mesa (Ubuntu)
Importance: Undecided => Medium
** Changed in: mesa (Ubuntu)
Status: New => In Progress
--
You received
This sounds like a consequence of a common problem with Intel graphics
-- the kernel occasionally misdetects the screen resolution.
It's not a big deal if only the startup animations are affected but let
us know if you have similar problems on the desktop (such as when
resuming from sleep).
**
Thanks for the fix Gunnar.
The reason I didn't raise it with you earlier was because I figured a
better solution would be to:
1. Patch to revert to a colon in the default US English translation.
2. Propose to upstream to not use RATIO in future because fonts don't
often implement the
> (Daniel: I can't explain how you hid the issue by using en_AU.UTF-8,
though.)
Maybe en_AU inherits from en_GB?
** Changed in: gnome-desktop (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: language-pack-gnome-en (Ubuntu)
Status: New => Won't Fix
** Changed in:
Seems LANG isn't the only factor here. My mantic desktop that was
installed months ago and updated daily doesn't have the bug even if I
force it to US English. Other machines with fresh mantic installs do
have the bug.
--
You received this bug notification because you are a member of Ubuntu
It looks like kernel 5.15 is only working because there's no graphics
driver there that supports the GPU. So it's defaulting to legacy
software rendering which kind of works... You can do the same in kernel
6.2 by using the kernel parameter "nomodeset".
** Package changed: xorg (Ubuntu) =>
Somewhat related:
https://github.com/canonical/ubuntu-desktop-installer/issues/2324
Without that installer bug I wouldn't encounter this bug.
** Bug watch added: github.com/canonical/ubuntu-desktop-installer/issues #2324
https://github.com/canonical/ubuntu-desktop-installer/issues/2324
--
** Package changed: fonts-ubuntu (Ubuntu) => language-pack-gnome-en
(Ubuntu)
** Also affects: language-pack-gnome-en-base (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Actually this might only be coming from GObject introspection builds, so
not from the C compiler?
** Description changed:
- Building on Raspberry Pi mantic, these warnings keep repeating:
+ Building on Raspberry Pi mantic, these messages keep repeating:
401 - 500 of 18149 matches
Mail list logo
