Sounds like the bug only exists in gdk-pixbuf 2.42.9 (Ubuntu 22.10) ...
https://gitlab.gnome.org/GNOME/eog/-/issues/255#note_1534033
** No longer affects: gnome-shell (Ubuntu)
** No longer affects: gnome-control-center (Ubuntu)
** Also affects: gdk-pixbuf (Ubuntu)
Importance: Undecided
** Tags added: jammy
** Summary changed:
- Font alignment issue when using scaling factor > 1
+ Font alignment issue in search bar when using scaling factor > 1
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
To
*** This bug is a duplicate of bug 1989477 ***
https://bugs.launchpad.net/bugs/1989477
Thanks for the bug report. It appears you need to toggle the color
selection to get it to apply to the "toolbox" (aggregate menu):
Settings > Appearance > Style > Color = change values
** Package changed:
It looks like the NVIDIA-525 driver is correctly installed and working.
What makes you think otherwise?
** 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 packag
*** This bug is a duplicate of bug 1999320 ***
https://bugs.launchpad.net/bugs/1999320
** This bug has been marked a duplicate of bug 1999320
Font alignment issue in search bar when using scaling factor > 1
--
You received this bug notification because you are a member of Ubuntu
Touch see
** Package changed: xorg (Ubuntu) => conky (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/139
Title:
The conky display stopped working after recent update
Statu
Please open a terminal window and run 'top'. What process is using the
most CPU?
** 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
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. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Looks like the same kernel message as in bug 1970495
** Summary changed:
- Xorg freeze
+ [amdgpu] Monitor does not wake from sleep unless power cycled
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Tags added: amdgpu
--
You received this bug notification because you are a member of Ub
*** This bug is a duplicate of bug 1878076 ***
https://bugs.launchpad.net/bugs/1878076
Sounds like a duplicate of bug 1878076, but see also bug 1949340.
** Package changed: xorg (Ubuntu) => ubuntu
** This bug has been marked a duplicate of bug 1878076
GTK save-dialogs input-focus moves fr
See also bug 1878076
--
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/1949340
Title:
[upstream] Saving downloads or pages is difficult because of unfocused
file chooser di
*** This bug is a duplicate of bug 1987040 ***
https://bugs.launchpad.net/bugs/1987040
Hello! Those are two unrelated bugs...
The issue with screen recording in Kazam doesn't seem to be a bug...
Kazam appears to be an old X11 app and so cannot read the Wayland
screen. This is a security featu
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470
(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/2000637
Title:
Xorg freeze
Status in nvidia-graphics
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. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
*** This bug is a duplicate of bug 1901115 ***
https://bugs.launchpad.net/bugs/1901115
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 1901115, so it is being marked as such. Please look
** Tags added: kinetic
--
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/1901115
Title:
package bluez failed to install/upgrade: installed bluez package post-
installation sc
*** This bug is a duplicate of bug 1999008 ***
https://bugs.launchpad.net/bugs/1999008
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 1999008, so it is being marked as such. Please look
** Package changed: xorg (Ubuntu) => linux (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 xorg in Ubuntu.
https://bugs.launchpad.net/b
If the same keyboard works on a different 20.04 machine then it's likely
to be a difference in kernel driver (or associated hardware).
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Package changed: xorg (Ubuntu) => linux (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/2000791
Title:
When my laptop wakes up from sleep, it displays a message ea
I have promised to actually test this on some older hardware but I want
to get through the past month's bug mail first...
--
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/1972977
*** This bug is a duplicate of bug 1988825 ***
https://bugs.launchpad.net/bugs/1988825
Re comment #2, yes I can see the nouveau kernel driver is crashing a
lot. Please use the Additional Drivers app to replace it with the proper
Nvidia driver. But that's not what this bug is about...
** Summ
If the machines are in different locations then they will experience
different interference. It might only fail in the presence of too much
2.4GHz noise like wifi networks or other Bluetooth devices. Such
interference will come and go over time.
--
You received this bug notification because you a
Thanks for the bug report. Next time the problem happens, please open a
terminal (Ctrl+Alt+T) and run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
I am wondering if this might be bug 1968040.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter
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 2000833
When reporting bugs in the future please use apport by using 'ubuntu-
Thanks for the bug report. Can you attach a photo or video of the
problem?
** Tags added: amdgpu
** 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, wh
Tested jammy with crocus on an i5-4300U, both 22.0.5-0ubuntu0.1 and
22.0.5-0ubuntu0.2
gnome-shell's RSS grows but seems to plateau similarly with both.
Based on upstream's comments, I started counting i915.gem instances in
/proc/PID/smaps and found that both 22.0.5-0ubuntu0.1 and
22.0.5-0ubuntu0.
Yeah kinetic doesn't have this bug so we can probably fix jammy via the
backport without knowing which commits are most important.
--
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
Likely (the proper) fix committed to mesa in:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20397
** Changed in: mesa (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in
*** This bug is a duplicate of bug 1783689 ***
https://bugs.launchpad.net/bugs/1783689
It looks like ALSA (the kernel) needs some tweaking because it is
reporting "speaker_outs=0"
Jan 05 09:59:52 luis-XPS-15-9560 kernel: snd_hda_codec_realtek hdaudioC0D0:
autoconfig for ALC3266: line_outs=1
*** This bug is a duplicate of bug 1783689 ***
https://bugs.launchpad.net/bugs/1783689
Tracking in bug 1783689.
** This bug has been marked a duplicate of bug 1783689
[Dell XPS 15 9560] No sound from speakers
--
You received this bug notification because you are a member of Ubuntu
Touch
*** This bug is a duplicate of bug 1783689 ***
https://bugs.launchpad.net/bugs/1783689
** This bug has been marked a duplicate of bug 1783689
[Dell XPS 15 9560] No sound from speakers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 1783689 ***
https://bugs.launchpad.net/bugs/1783689
** This bug has been marked a duplicate of bug 1783689
[HDA-Intel - HDA Intel PCH, playback] No sound at all
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
Zero speaker_outs sounds like the issue:
[4.273272] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3266:
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[4.273274] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0
(0x0/0x0/0x0/0x0/0x0)
[4.273276] snd_hda_codec_realtek hdaudi
Please tell us the contents of /var/crash/_usr_lib_xorg_Xorg.0.uploaded
as it will contain the unique ID of the Xorg crash.
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this
It is supported, just the name of the GPU is unknown in 22.04. This has
been fixed already in later Ubuntu versions and should not affect
performance at all.
** Summary changed:
- Seems like my GPU isn't supported
+ Intel PCI ID 8086:9a78 missing in pci.ids
** Package changed: xorg (Ubuntu) => p
If anyone was using jammy and experiencing this then maybe consider:
https://launchpad.net/ubuntu/+source/linux-signed-oem-6.0
Otherwise the unsupported options:
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
--
You received this bug notification because you are a member of Ubuntu
Touch
Usually the HDMI port is wired to the discrete GPU which is Nvidia in
this case. And it appears there is no Nvidia kernel driver being loaded.
Please use the 'Additional Drivers' app to install/reinstall one.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New =>
** 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
Touch seeded packages, which is subscribed to wayland in Ubuntu.
htt
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 wou
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
Touch seeded packages, which is subscribed to xorg i
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
** C
Thanks for the bug report.
The problem preventing Xorg from loading appears to be:
intel: waited 2020 ms for i915.ko driver to load
But 'intel' is an old buggy driver that nobody should be using. Please
remove any custom configs in /root/xorg.conf.new and
/usr/share/X11/xorg.conf.d that are lo
Workaround committed to mutter for the next lunar update, whenever that
may be.
https://salsa.debian.org/gnome-team/mutter/-/commit/d615363fa9
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-mesa-22.3.3 fixed-upstream
--
You received this bug
Can you attach a screenshot or photo of the problem?
** Summary changed:
- erro Icon connection
+ The ethernet connection icon has disappeared
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bu
This work is not currently scheduled. It's just on the backlog queue.
Looks like a simple patch though. Given how simple it is I might try to
do it in the coming weeks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in
Oh, I forgot I don't own Sony WH-1000XM4 anymore but hopefully the bug
reproduces with other headphones.
--
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/1988364
Title:
Missin
(Ubuntu Kinetic)
Status: New => Fix Released
** Changed in: bluez (Ubuntu Kinetic)
Importance: Undecided => High
** Changed in: bluez (Ubuntu Jammy)
Status: New => In Progress
** Changed in: bluez (Ubuntu Jammy)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Description changed:
- Sony WH-1000XM4 missing the A2DP profile and defaults to low quality
+ [ Impact ]
+
+ Sony WH-1000XM4 missing the A2DP profile and defaults to low quality.
+ Probably other headphone types would be affected too.
https://github.com/bluez/bluez/issues/313
+
+ [ Test
Debdiff for jammy
** Patch added: "bluez_5.64-0ubuntu1.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1988364/+attachment/5641583/+files/bluez_5.64-0ubuntu1.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
Patch attached above, but can anyone help with a reliable test plan?
(edit the top of this page)
** Tags removed: rls-jj-incoming
--
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/bug
Thanks. I did have a configuration in which I could reproduce this
recently so myself or someone else should look at confirming it's really
fixed.
I wasn't too worried about this bug though because:
* It never happens on 22.04
* 23.04 will get kernels 6.1 and 6.2 in the coming months
** Cha
Hmm perhaps bug 2001914 needs revisiting though (22.04)
--
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/1998950
Title:
GPU hang on Alder Lake laptop
Status in Linux:
New
St
Thanks for the bug report.
The biggest issue here seems to be a kernel crash:
Jan 16 19:40:28 semiauto kernel: [84513.834489] adding CRTC not allowed without
modesets: requested 0x4, affected 0x7
Jan 16 19:40:28 semiauto kernel: [84513.834564] WARNING: CPU: 4 PID: 2041 at
drivers/gpu/drm/drm_at
*** This bug is a duplicate of bug 1969140 ***
https://bugs.launchpad.net/bugs/1969140
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 1969140, so it is being marked as such. Please look
** Summary changed:
- video corruption when using gnome-display settings
+ Settings window becomes broken and unresponsive when changing scales,
sometimes
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status:
Thanks for the bug report.
The Nvidia Xorg driver doesn't appear to be loading for some reason,
which is the main problem. Although the Nvidia kernel driver is loaded.
You are using Nvidia driver version 470.161.03 but their website
suggests the current supported version for your Quadro P620 is
5
Rafael, I can't seem to find a way to reproduce the bug with the
headphones I do have. Can you outline the steps (and the model of
headphones) you are using?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
htt
I was expecting upstream to say "won't fix". Aside from the protocol
saying it's the expected behaviour, we also wouldn't want to impact
performance of fullscreen games just because they accidentally used RGBA
instead of RGBX or RGB. So disallowing anything to show through in full
screen makes sens
OK so you may or may not be commenting on the right bug. Assuming you
are, we'll just ask you to test the proposed fix when it is built...
** Description changed:
[ Impact ]
Sony WH-1000XM4 missing the A2DP profile and defaults to low quality.
Probably other headphone types would be affe
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => mutter (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/2003237
Title:
Monitor does not turn off after idle
Yeah I can't see this bug anymore on kinetic with kernel
5.19.0-29-generic. So this is closed and bug 2001914 separated.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** No longer affects: mesa (Ubuntu)
--
You received this bug notification because you are a member of
Thanks for the bug report.
Please take care to ensure each bug report covers one issue only. You
should open a separate bug for each issue so please reword this bug to
describe one of the issues only.
The problem with text and icons disappearing sounds like it might be bug
1876632.
** Package ch
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. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then t
See also bug 1973098
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- LSPCON failure
+ [i915] LSPCON failure
** Tags added: i915
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
http
For completeness I bisected the cause of the issue (introduced in mutter
43.1):
909616b20876478bc56932cd18c8e85e982645f6 is the first bad commit
commit 909616b20876478bc56932cd18c8e85e982645f6
Author: Sebastian Wick
Date: Tue May 3 18:47:57 2022 +0200
window-actor/wayland: Draw black backg
** Summary changed:
- Unable to display 4K 60hz Ubuntu 20.10 for Raspberry Pi
+ Unable to display 4K 60hz Ubuntu 22.10 for Raspberry Pi
** Description changed:
- Ubuntu 20.10 won't display 4K at 60hz on Raspberry Pi 4. Workaround of
+ Ubuntu 22.10 won't display 4K at 60hz on Raspberry Pi 4. Work
Please make sure you have enabled hdmi_enable_4kp60 in the correct
config file. Please also try different HDMI cables because 4K60Hz
requires an HDMI 2.0 cable. HDMI 1.4 cables and older will be limited to
4K30Hz.
** Package changed: xorg (Ubuntu) => linux-raspi (Ubuntu)
** Tags added: raspi rasp
We know. It's in the queue but I'm guessing there are not enough
sponsors with authority to keep up with the backlog:
http://reqorts.qa.ubuntu.com/reports/sponsoring/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer1
jeejah42, it sounds like you need to log a separate bug. Please do that
by running:
ubuntu-bug linux
--
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/1969959
Title:
[nouveau
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. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
See also:
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=xrandr-scaling
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Tags added: cursor multimonitor nvidia
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Tags added: xrandr-scaling
--
You rec
** Changed in: glib2.0 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1999098
Title:
Update glib to 2.74.3
Status in
Public bug reported:
Update to glib >= 2.75.1 because that's what mutter 44 now requires.
** Affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Tags: lunar upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
OTOH, it's a trivial revert in mutter 44 to drop the new glib
dependency.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004241
Title:
Update to glib >= 2.75.1
Status in
The full set of messages related to this bug seems to be:
Jan 31 22:26:18 t935 wireplumber[1791]: 0x56370f33ca08: error 24
Jan 31 22:26:18 t935 wireplumber[1791]: RFCOMM write error: Connection reset by
peer
Jan 31 22:26:18 t935 acpid[876]: input device has been disconnected, fd 18
Jan 31 22:26:1
Thanks for the bug report.
I have just tested:
Settings >
Multitasking >
Application Switching >
Include applications from the current workspace only
and although I wasn't able to reproduce exactly the same bug, I was able
to reproduce a similar bug in that the dot next to the Files ico
It looks like you're using Xorg fractional scaling, so yes that will
take the texture requirements past the limit supported by the GPU if you
do it across multiple 4K monitors. Some parts of the desktop will cope
and other parts (GTK) might not cope.
To confirm this, please run:
xrandr --verbos
The most likely explanation here is that the kernel is not offering 4K
as a supported resolution, which you can check by running:
grep . /sys/class/drm/*/modes
If it's not listed there then you need a higher quality HDMI 2.0 cable.
Or even better to use DisplayPort instead.
** Package changed
** No longer affects: nvidia-graphics-drivers-525 (Ubuntu)
--
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/2004533
Title:
Gtk-WARNING **: ...: drawing failure for widget '.
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. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Please also collect a system log of the problem.
If you had to reboot to recover from it then run:
journalctl -b-1 > prevboot.txt
or if you didn't need to reboot then run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => ubuntu
*
** Summary changed:
- very unstable desktop, icons vanish, cannot control windows, cannot resize or
scale multi monitors easily.
+ Gtk-WARNING **: ...: drawing failure for widget '...': invalid value
(typically too big)
** Summary changed:
- Gtk-WARNING **: ...: drawing failure for widget '...
** Changed in: pipewire (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: pipewire (Ubuntu Jammy)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu.
https:
Thanks for the bug report. I can see it happening in:
[ 870.506] (II) modeset(0): Modeline "1366x768"x0.0 76.30 1366 1404 1426
1592 768 771 777 798 -hsync -vsync (47.9 kHz eP)
[ 1932.032] (II) config/udev: removing device PixArt USB Optical Mouse
[ 1932.033] (**) Option "fd" "29"
[ 1932.
Thanks for the bug report.
Next time the problem happens, please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
** Summary changed:
- Laptop often freezes after waking up from suspend to ram
+ [Asus ZenBook UX430UAR] Laptop
Thanks for the bug report.
Next time the problem happens, please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
** Summary changed:
- can't restart when screen sleeps and power adapter plugged in
+ [Asus ZenBook UX325EA] ca
The attached information looks like memory mapped files. So that's
virtual address space, not real memory.
Please run:
ps auxw > psall.txt
and attach the resulting text file here.
** Project changed: xorg-server => gnome-software
** Package changed: xorg (Ubuntu) => gnome-software (Ubuntu)
** Changed in: gst-plugins-base1.0 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: gstreamer1.0 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: pipewire (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: gst-plugins-base1.0 (Ubuntu Jammy)
Ass
** Tags added: jammy lunar
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1887252
Title:
config-error-dialog.sh should pass --no-markup
Status in gdm3 package in Ubuntu:
Yes this sounds like a GTK-only bug, probably new in Ubuntu 22.10. But
potentially related to that, please run:
xrandr --verbose > xrandr.txt
and attach the resulting text file here.
Also remember one of the issues you mentioned earlier is likely to be
bug 1876632 so please read that.
--
You
Thanks for the bug report.
It looks like this is probably a bug in the nouveau graphics driver, and
most likely the HDMI port is connected to your Nvidia GPU. The nouveau
driver is also logging errors which may or may not be related to this
bug.
Please open the 'Additional Drivers' app and use it
I just noticed this is a shutdown crash, which isn't obvious until you
scroll down to frames #46-#54:
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
Although that's probably not an excuse for letting this sneak into
jammy.
Another interesting note is that it looks lik
I think this is a consequence of your desktop being 18432 pixels wide.
Each 4K monitor is 6144 logical pixels wide because of a custom Xrandr
scaling factor of 1.6.
Turning off screens wouldn't fix it, only unplugging them might. But
still this sounds like a GTK bug because modern Nvidia GPUs like
Tracking upstream in https://gitlab.gnome.org/GNOME/gtk/-/issues/3050
--
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/2004533
Title:
Gtk-WARNING ... drawing failure for wid
To achieve a scaling factor of 1.6 I suspect the logic is to render at
8x resolution and then downscale 5x (because 8/5 = 1.6). And GTK has
internal size limits of 65535 in each dimension, I think. So the maximum
window size is 65535 / 8 = 8191. That should be enough to have two 4K
(3840 px) monito
Another suggestion is to use a scaling factor of 1.5 instead of 1.6.
That might simplify the required quotient to 3/2 (initially rendering at
3x resolution instead of 8x), so might be enough to have all three
monitors working.
--
You received this bug notification because you are a member of Ubun
And yes that is an inefficient way to do fractional scaling. Only Xorg
does it that way out of necessity to fit in with legacy X11. Wayland
does not need such upscaling-then-downscaling so does fractional scaling
much more efficiently than Xorg sessions.
But Nvidia's Wayland support is still sligh
Out of curiosity, how did you configure a scaling factor of 1.6?
--
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/2004533
Title:
Gtk-WARNING ... drawing failure for widget .
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Medium
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => Triaged
--
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.
501 - 600 of 16693 matches
Mail list logo
