No crashes after 20.10 so consider it fixed.
** Changed in: mesa (Ubuntu)
Status: Confirmed => Fix Released
--
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/1871959
Public bug reported:
Release to Lunar:
http://www.bluez.org/release-of-bluez-5-66/
** Affects: bluez (Ubuntu)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: Triaged
** Tags: lunar
--
You received this bug notification because you are a member of Ubuntu
If it happens on all or a large number or systems then people should
share the same bug. Or if they have the same hardware (same laptop or
same sound chips). Otherwise people should each log their own bug
because in most cases problems like this are hardware-specific. So I'm
thinking that's 3
2.4GHz wifi networks can and will conflict with Bluetooth which shares
similar frequencies. Try using 5GHz for the wifi network if you can.
** Package changed: bluez (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Tags added: hybrid i915 multigpu nvidia
** 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/1995766
Title:
X server
*** This bug is a duplicate of bug 1969577 ***
https://bugs.launchpad.net/bugs/1969577
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 1969577, so it is being marked as such. Please
** Package changed: xorg (Ubuntu) => ubuntu
** Package changed: 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/1995761
Title:
Xorg crash
Thanks for the bug report. This sounds like it might be a kernel bug in
the i915 driver. Next time you are stuck in a poor resolution, please
run:
grep . /sys/class/drm/*/modes > modes.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
**
** Summary changed:
- Microphone not working after suspend
+ [Purism Librem 13 v4] Microphone not working after suspend
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Tags added: fixed-upstream
--
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/1993800
Title:
LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8,
** Tags added: kinetic
** Package changed: wayland (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1995305
Title:
Cursor blurry with
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #7621
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7621
** Also affects: mesa via
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7621
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Summary changed:
- Devices pair and connect, but immediately (4-5 secs) disconnect
+ [HP HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but
immediately (4-5 secs) disconnect
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- [HP
Bug 1922414 covers one of the issues with has_option so please reword
this bug to cover one other issue only.
--
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/1995236
Title:
** Package changed: xorg (Ubuntu) => mate-desktop (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/1995216
Title:
X forgets monitor configuration when HDMI cable was
Incomplete only because we need a reason for the failure... See also bug
1901115 and bug 1769800
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Thanks for the bug report. It looks like you don't have a working
graphics driver installed.
Please open the 'Additional Drivers' app and use it to install the
latest NVIDIA driver.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-520
(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/1995173
Title:
Lenovo Legion 7 Display Issues :
Thanks for the bug report.
Next time you experience a slow boot, please then run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Tags added: jammy
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received
Thanks for the bug report. I would like to establish if this is a bug in
the Xorg driver or the bad(?) resolution is coming from the kernel.
Please run:
grep . /sys/class/drm/*/modes
and tell us if you see the correct resolution there.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed
Do you experience the same issue if you log into a Wayland session?
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
** Tags added: multimonitor
--
You received this bug notification because you are a member of
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/2057
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: webkit2gtk (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: yelp (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch
*** This bug is a duplicate of bug 1990563 ***
https://bugs.launchpad.net/bugs/1990563
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 1990563, so it is being marked as such. Please
** Summary changed:
- Bluetooth issue
+ Bluetooth is not connecting to any of my phone or headsets [Intel 3165
8086:3166]
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Thanks for the bug report.
Please try deleting any local extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again.
If the problem still occurs then next time it does please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach
This is probably a kernel or firmware bug. Please try using the
officially supported Ubuntu kernel (5.15.0-52.58) and/or try a newer
upstream kernel like https://kernel.ubuntu.com/~kernel-
ppa/mainline/v6.0.3/amd64/
** Summary changed:
- bluetooth not turning on and not connectting to my device
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563
Yes the fix is in egl-wayland 1.1.10 -
https://launchpad.net/ubuntu/+source/egl-wayland
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: mesa (Ubuntu)
Status: Incomplete => Fix Released
--
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/1992667
Title:
Application windows invisible (on DG2
** Changed in: llvm-toolchain-15 (Ubuntu)
Importance: Undecided => Medium
** Changed in: mesa (Ubuntu)
Importance: Undecided => Medium
** Changed in: llvm-toolchain-15 (Ubuntu)
Status: New => Confirmed
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
** Tags added:
Incomplete. My first question is: What project is "fs_variant_partial"
in?
** Tags added: armhf
** Package changed: ubuntu => llvm-toolchain-15 (Ubuntu)
** Changed in: llvm-toolchain-15 (Ubuntu)
Status: Incomplete => New
** Bug watch added: bugzilla.opensuse.org/ #1204267
Fix/workaround?;
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19217
** Tags added: armv7
** Tags removed: focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Added a mesa task because all debugging so far points to a bug in Mesa
(vc4 and panfrost):
https://gitlab.gnome.org/GNOME/mutter/-/issues/2379
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Importance: Undecided => Medium
--
You
What is the 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.
There certainly are Bluetooth errors in the log, and some are kernel
related.
I suggest the best thing to do here is to try a newer Ubuntu release
like 22.04.1. Because there's a good chance this was a bug in the
kernel, Intel firmware, or BlueZ that has already been fixed.
** Summary changed:
** Summary changed:
- wlan errors
+ iwlwifi errors
** 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/1993560
Title:
Your hardware is too new for Ubuntu 18.04:
[2.213969] [drm] Your graphics device 9a78 is not properly supported by the
driver in this
kernel version. To force driver probe anyway, use
i915.force_probe=9a78
module parameter or CONFIG_DRM_I915_FORCE_PROBE=9a78
Supporting manual xrandr settings is generally not a priority for shell
developers. The shell expects to own and control everything, and that
the user has chosen their settings in the GUI provided by the shell /
desktop environment.
But we can make it an enhancement request to see if it's
IMHO it's not reasonable for any software to absolutely require an
environment variable that's not already set in a default console login.
We all need to build better software that still works without
environment variables.
Also changing multiple desktop environments now and into the future
Can you provide a screenshot or photo of the screen?
** 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.
Indeed there are no crashes after version 42.x
--
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/1726129
Title:
nautilus crashed with SIGSEGV in widget_needs_widget_path
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Tags added: nvidia
** Tags added: multimonitor
--
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/1992707
Title:
Thanks for the bug report. Yes the screenshot shows texture corruption
which may also relate to missing windows. If DG2 is anything like the
desktop Arc chips then you will need Mesa 22.2 (Ubuntu 22.10) to support
it. As well as kernel 6.0.
Please run:
lspci -k > lspci.txt
and attach the
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
Bug 1857392 occurs on practically all machines every day so I recommend
ignoring that one specifically. In comment #13 I think I was just
pointing out there seems to be a common root cause if we can find out
why/where bug 1857392 occurs so often.
--
You received this bug notification because you
Duplicate bug 1970402 mentions that:
> Workaround: Disable Secure Boot and SGX.
works for multiple people.
--
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/1842320
Which package should be marked as Fix Released for 22.10?
--
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/1924251
Title:
Embedded browser display corruption under Wayland
*** This bug is a duplicate of bug 1973098 ***
https://bugs.launchpad.net/bugs/1973098
Looks like bug 1973098 is the same.
** Tags added: hybrid i915 multigpu nvidia
** Tags added: regression-update
** Summary changed:
- Boot freeze
+ Boot freeze - [drm:lspcon_init [i915]] *ERROR* Failed
** No longer affects: gstreamer-vaapi (Ubuntu)
** No longer affects: gstreamer1.0 (Ubuntu)
** No longer affects: libx11 (Ubuntu)
** No longer affects: libxcb (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: gnome-shell (Ubuntu)
Status: Opinion => In Progress
** Changed in: gnome-shell (Ubuntu)
Milestone: None => ubuntu-22.10
--
You received this bug notification be
If I modify gstreamer-vaapi to ignore X11 on Wayland, then it freezes in
Wayland instead !?
#0 0x7f5ec1d10ec4 in __GI___poll (fds=0x7fff30df9e50, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7f5ec14c3e0c in wl_display_dispatch_queue ()
from
** Changed in: gstreamer-vaapi (Ubuntu)
Milestone: None => ubuntu-22.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1988488
Title:
Screen freeze before the
** Changed in: gstreamer-vaapi (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: gstreamer-vaapi (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
Workaround:
You can usually install Ubuntu on a drive in one machine and then move
the drive into another machine.
At least I think that's what I did on the affected machine with 22.04,
which is why I never discovered this bug until 22.10 development
started.
--
You received this bug
I think this was fixed in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2479
** Summary changed:
- Fractional scaling settings lost on logout
+ Fractional scaling settings lost on VM window resizing or logout
** 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. 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 explain what the problem is you would like to discuss.
** 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
** Changed in: gnome-shell (Ubuntu)
Importance: Medium => High
** Changed in: gstreamer-vaapi (Ubuntu)
Importance: Medium => High
** Changed in: gstreamer1.0 (Ubuntu)
Importance: Medium => High
** Changed in: libx11 (Ubuntu)
Importance: Medium => High
** Changed in: libxcb (Ubuntu)
Please explain in more detail (ideally with photos or a video) what the
main problem is.
** Package changed: xorg (Ubuntu) => libreoffice (Ubuntu)
** Package changed: libreoffice (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification
I feel like that's a separate bug, but on the same critical path to
getting the OSK working.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1831039
Title:
Is this a different issue to bug 1991857?
** Package changed: xorg (Ubuntu) => ubuntu
** Summary changed:
- Xorg freeze
+ Freeze
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thanks for the bug report. Is the freeze and flickering confined to just
the web browser or the whole screen?
** Summary changed:
- Web browser extensions bugs
+ The screen has frozen several times and flickers
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status:
** Tags added: rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1990891
Title:
after today's Kinetic updates, WiFi no longer working, so laptop
Here's the full freeze location (in gst-plugin-scanner) with debug
symbols:
#0 0x7ff635310ec4 in __GI___poll (fds=fds@entry=0x7fff2f5e7790,
nfds=nfds@entry=1, timeout=timeout@entry=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7ff63479ae23 in poll (__timeout=-1, __nfds=1,
gnome-shell is just an innocent victim here. It's unlikely we would need
or want to do a workaround in that.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Opinion
** Tags added: rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: ubuntu
Status: Incomplete => New
** Package changed: ubuntu => linux (Ubuntu)
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Thanks for the bug report.
Most of "lag" issues were fixed in Ubuntu 22.04 so please try that as
soon as you can:
https://ubuntu.com/download/desktop
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification
I'm not totally sure that's a fix, but let's assume it is.
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => Fix Committed
** Tags added: fixed-in-gtk-3.24.35 fixed-upstream
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/602
Importance: Unknown
** Tags added: nvidia
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags added: multimonitor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Yes people should be able to promote a feature advertised during
install...
While the bug remains open, a workaround is to:
1. Install *without* the third-party option.
2. sudo apt install ubuntu-restricted-extras
3. sudo apt remove gstreamer1.0-vaapi
--
You received this bug notification
That makes sense, and I have done the same in the past. Although this
bug highlights the fact that those third-party packages behave
differently and exercise different code paths in virtual vs real
machines.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Dropped to Medium because I don't think there's any useful reason to
tick the third party software option in virtual machines. You're not
missing out on anything that a virtual machine could otherwise do.
** Changed in: gnome-shell (Ubuntu)
Importance: High => Medium
** Changed in:
Looks like a bug in libx11 or libxcb because I don't think it's meant to
be possible for XOpenDisplay() to hang.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1988488
I think the problem is gnome-shell waiting for this command (which never
finishes):
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
-l /usr/bin/gnome-shell
because it's waiting for an X server (which does exist as Xwayland):
#0 0x7f76ea710ec4 in __GI___poll
** Tags added: kinetic
** Tags added: wayland wayland-session
** Tags added: radeon
** Summary changed:
- distorted mouse pointer under Wayland in Kinetic
+ [radeon] Distorted mouse pointer under Wayland in Kubuntu 22.10
** No longer affects: wayland (Ubuntu)
** Bug watch added: KDE Bug
Thanks for the bug report. This is probably bug 1968040 so please try
the workaround mentioned there.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Since this only seems to happen on dist upgrades (or it would after
22.10 is released) and we have a workaround, it doesn't need to be
Critical anymore.
** Tags added: regression-upgrade
** Changed in: network-manager (Ubuntu)
Importance: Critical => High
--
You received this bug
The default VirtualBox settings only give 16MB of graphics memory so the
screen will start to fail/turn black around 2K resolution.
Please try turning off the virtual machine and changing Video Memory to
64MB.
** Tags added: virtualbox vmwgfx
** Package changed: xorg (Ubuntu) => ubuntu
**
Thanks for that. Indeed the log shows the lid being closed without any
locking near the end. That might be related to bug 1857392 which is
clearly occurring at the same time. It also highlights that systemd is
responsible for initiating the locking.
** Package changed: ubuntu => systemd (Ubuntu)
** Package changed: xorg (Ubuntu) => gnome-shell (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/1991494
Title:
dark mode sometimes works
Status in gnome-shell
Fix in bug 1990705?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1990891
Title:
after today's Kinetic updates, WiFi no longer working, so laptop
basically
You can't uninstall wpasupplicant because that removes ubuntu-desktop.
Removing /etc/NetworkManager/conf.d/iwd.conf works though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1990891
Title:
after today's Kinetic
** No longer affects: linux (Ubuntu)
** Changed in: mesa (Ubuntu)
Status: Confirmed => Triaged
** Changed in: mesa (Ubuntu)
Importance: Undecided => Medium
** Tags added: fixed-in-22.2.0 fixed-upstream
** Changed in: mesa (Ubuntu)
Status: Triaged => Fix Released
** Tags
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
Thanks for the bug report.
1. Please ensure the correct driver is installed:
sudo apt install intel-media-va-driver-non-free vainfo
2. Verify the driver is working by running 'vainfo'.
3. If the problem persists then tell us what app you are using to play
video.
** Package changed: xorg
** Summary changed:
- Drivers error
+ No Local Variables are initialized for Method [RUCC]
** 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.
Thanks for the bug report. This looks like it might be a kernel driver
bug. Please open the Additional Drivers app and use it to install an
official Nvidia driver, then reboot.
If the crash persists after installing the official Nvidia driver then
please follow:
What output do you get from:
gsettings list-recursively | grep delay
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Tags added: nvidia
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Please explain 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.
*** This bug is a duplicate of bug 1990646 ***
https://bugs.launchpad.net/bugs/1990646
Please explain what kind of problem you are experiencing.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** This bug has been marked a duplicate of bug
It sounds like you're moving too fast for the default tap-to-click
thresholds :)
I would recommend disabling tap-to-click in Settings so that only
physical clicks of the pad are used as button press events. If you need
very accurate, very fast input then always use physical buttons.
** Changed
** Summary changed:
- apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)
+ apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)
from gtk_css_value_icon_theme_compute() from
gtk_css_static_style_compute_value()
--
You received this bug notification
Thanks for the bug report.
This appears to be either a hardware problem or a bug in the Nvidia
driver. I think most likely it's due to insufficient HDMI cable
bandwidth. Please ensure you are using an HDMI 2.1 certified cable
capable of at least 40 Gbit/s. An HDMI 2.0 cable will not be good
Thanks for the bug report. I can't yet see anything wrong with the
machine. Can you describe the problem in more detail, maybe with a
video?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are
PipeWire is not supported in 22.04, but it will be supported in 22.10.
Do you still experience this bug without PipeWire in 22.04?
** Tags added: jammy
** Package changed: bluez (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Tags added: a2dp
--
You received
** Changed in: mir (Ubuntu)
Assignee: aalosman (aalosman) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1276322
Title:
[enhancement] Mir lacks relative
"May be notified" generally means people will be receiving some comments
as emails, like when a bug is closed or changes status. Only "Notified
of all changes" will be receiving all comments but even then expect
those people to have email filters set up so they don't have to read
everything.
Yes you are right that it looks confusing, but this is how Launchpad
works. A bug that is fixed in any release is closed. :/
Adding a task to fix it in 22.04 will reopen the bug just for 22.04 but
generally we don't do that until someone is assigned to actually do the
work.
To request that a fix
Also we shouldn't target jammy until someone is assigned to it.
** No longer affects: bluez (Ubuntu Jammy)
--
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:
901 - 1000 of 16455 matches
Mail list logo
