[Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
Hi renbag,
Thanks for attaching your smb.conf and sssd.conf, I will try add them
into my reproducer and see if I get closer to seeing the problem.
Maybe when you log in, smbd mounts the samba shares to
/home/aduser/{Public},{Shared} before kerberos manages to acquire a new
ticket and place it in /tmp, so gvfs doesn't get KRB5CCNAME set.
Maybe on your faster system, it can get the kerberos ticket before smbd
starts mounting shares.
This is still a race condition where gvfs is starting too early though.
Let me re-adjust my reproducer, and I will let you know how I get on.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779890
Title:
Nautilus does not use a valid Kerberos ticket when accessing Samba
share
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899909] Re: [gdm3] Screen keyboard doesn't work after session locked
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899909 Title: [gdm3] Screen keyboard doesn't work after session locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899909] Re: [gdm3] Screen keyboard doesn't work after session locked
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899909 Title: [gdm3] Screen keyboard doesn't work after session locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948748] Re: [MIR] swtpm
Added a libvirt task to bring in the dependency. ** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948748 Title: [MIR] swtpm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autogen/+bug/1948748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967596] Re: Gnome on-screen keyboard unreliable
*** This bug is a duplicate of bug 1899909 *** https://bugs.launchpad.net/bugs/1899909 ** Tags added: osk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967596 Title: Gnome on-screen keyboard unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960598] Re: libvigraimpex: FTBFS with GCC 11
** Changed in: libvigraimpex (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960598 Title: libvigraimpex: FTBFS with GCC 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/3depict/+bug/1960598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions
> Maybe switching from wayland to xorg caused the problem. > > That menu was only present on the first login screen, so I tried moving back > to Wayland. Yes if the first login fails then gdm3 assumes that means it was Wayland that failed so on the second try it will remove the Wayland option and you will get Xorg only. So it might be possible to say that every Wayland login attempt is failing(?) This log from duplicate bug 1967025 seems to show the 'vmwgfx' kernel driver failing: https://launchpadlibrarian.net/593819338/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice with VirtualBox Guest Additions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967595] Re: Display Issue in 5:4
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 1967595 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: jammy ** Summary changed: - Display Issue in 5:4 + Xubuntu Display Issue in 5:4 ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967595 Title: Xubuntu Display Issue in 5:4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1967595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948748] Re: [MIR] swtpm
libtpms [1] and even the auto unblocked ppc build of swtpm [2] migrated to jammy-release in universe. For both we have the MIR ack, Security ack and all required todos implemented. Time to seed or depend on this accordingly. The one I know that was planned was a recommends from libvirt which can utilize it to provide swtpm based functionalities to VMs. Feel free to suggest propose other seeding as well, but this is the one I'm going for now. Proposed here [3]. [1]: https://launchpad.net/ubuntu/+source/libtpms/0.9.3-0ubuntu1 [2]: https://launchpad.net/ubuntu/+source/swtpm/0.6.3-0ubuntu1 [3]: https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/418313 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948748 Title: [MIR] swtpm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autogen/+bug/1948748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948748] Re: [MIR] swtpm
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/418313 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948748 Title: [MIR] swtpm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autogen/+bug/1948748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions
** Tags added: vbox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice with VirtualBox Guest Additions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)
Tracking upstream in https://gitlab.gnome.org/GNOME/mutter/-/issues/2210 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2210 https://gitlab.gnome.org/GNOME/mutter/-/issues/2210 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2210 Importance: Unknown Status: Unknown ** Summary changed: - [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument) + [radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument) ** Tags removed: amdgpu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967714] [NEW] application freezes after copy/paste via mouse context menu
Public bug reported: Pidgin 2.13.0 Ubuntu 20.04 Copy/pasting a command into the text box causes Pidgin to freeze - and I need to force quit the application then. This only happens when I click in the text field with my right mouse button and select paste. This does not happen when I select the text field and copy/paste via keyboard (CTRL+V). ❯ lsb_release -rd Description:Ubuntu 20.04.4 LTS Release:20.04 ❯ apt-cache policy pidgin pidgin: Installed: 1:2.13.0-2.2ubuntu4 Candidate: 1:2.13.0-2.2ubuntu4 Version table: *** 1:2.13.0-2.2ubuntu4 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: pidgin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967714 Title: application freezes after copy/paste via mouse context menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1967714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)
I just tried commenting out MUTTER_DEBUG_USE_KMS_MODIFIERS=0 and get the original problem again, so the issue is still happening without the workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966818] Re: zsys crashing on snap mounts
*** This bug is a duplicate of bug 1967585 *** https://bugs.launchpad.net/bugs/1967585 ** This bug has been marked a duplicate of bug 1967585 Failed to start ZSYS daemon service (panic: runtime error) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966818 Title: zsys crashing on snap mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1966818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session
** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Confirmed ** Also affects: nvidia-graphics-drivers-495 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964037 Title: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1964037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided => High ** Also affects: nvidia-graphics-drivers-495 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953264] Re: Ubuntu 21.10 Bluetooth adapter not detected
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953264 Title: Ubuntu 21.10 Bluetooth adapter not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954597] Re: Application Indicators in panel missing after weekend updates
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954597 Title: Application Indicators in panel missing after weekend updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1954597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959844] Re: lagging
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959844 Title: lagging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1959844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)
Comment #16 is surprising. Can anyone else confirm? ** Description changed: Wayland started crashing for me on upgrade to Jammy, which I'm aware is currently in alpha. gdm was crashing, and changing to lightdm addressed this issue. If I select 'Ubuntu on Xorg' - I can login without problems. If I select Wayland instead, I just get a black screen, and I have to kill gnome-session from a virtual console. + + WORKAROUND: + + Add this to /etc/environment: MUTTER_DEBUG_USE_KMS_MODIFIERS=0 + + --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 15:23:51 2022 DisplayManager: lightdm InstallationDate: Installed on 2022-03-19 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967609] Re: Nvidia 510 driver causes screen corruption in X for Ubuntu 22.04
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-510 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967609 Title: Nvidia 510 driver causes screen corruption in X for Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1967609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967580] Re: Gnome not loading on boot after fresh install.
*** This bug is a duplicate of bug 1966808 *** https://bugs.launchpad.net/bugs/1966808 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 1966808, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1966808 [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967580 Title: Gnome not loading on boot after fresh install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967602] Re: intell error
** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967602 Title: intell error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1967602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878457] Re: Window shrinks on switching focus
** Changed in: mate-desktop Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878457 Title: Window shrinks on switching focus To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1878457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])
It appears the address of a stack variable has overwritten the return address for the offending function call. So we have no stack trace. I wonder if there's a way to catch stack corruption without going so far as Valgrind... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964120 Title: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967487] Re: gnome-shell crashed with signal 5 in g_log_structured_array()
*** This bug is a duplicate of bug 1964037 *** https://bugs.launchpad.net/bugs/1964037 ** This bug is no longer a duplicate of private bug 1967486 ** This bug has been marked a duplicate of bug 1964037 gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967487 Title: gnome-shell crashed with signal 5 in g_log_structured_array() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967707] [NEW] Nvidia Wayland sessions sometimes flood the log with [clutter_frame_clock_notify_presented: code should not be reached]
Public bug reported: Nvidia Wayland sessions sometimes flood the log with: [ 13.105877] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.106163] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.112490] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.125302] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.142242] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached I've been seeing the issue for months although it only seems to happen *after* something has gone wrong in mutter. Not by default. Then when the messages start, restarting gnome-shell won't fix it. You have to reboot the whole machine so it seems like something has latched in the nvidia-drm kernel driver. ** Affects: mutter (Ubuntu) Importance: Undecided Assignee: Daniel van Vugt (vanvugt) Status: New ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: jammy nvidia nvidia-wayland wayland-session ** Tags added: jammy nvidia nvidia-wayland wayland-session ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Description changed: Nvidia Wayland sessions sometimes flood the log with: [ 13.105877] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.106163] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.112490] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.125302] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.142242] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached I've been seeing the issue for months although it only seems to happen *after* something has gone wrong in mutter. Not by default. Then when the messages start, restarting gnome-shell won't fix it. You - have to reboot the whole machine. + have to reboot the whole machine so it seems like something has latched + in the nvidia-drm kernel driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967707 Title: Nvidia Wayland sessions sometimes flood the log with [clutter_frame_clock_notify_presented: code should not be reached] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
This bug was fixed in the package dbus - 1.12.20-2ubuntu4 --- dbus (1.12.20-2ubuntu4) jammy; urgency=medium * Prevent dbus from being restarted on upgrade (LP: #1962036) -- Dave Jones Fri, 01 Apr 2022 18:02:54 +0100 ** Changed in: dbus (Ubuntu Jammy) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1964458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965673] Re: Object 0x... of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management
** Changed in: ibus (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid ** Tags added: fixed-in-1.5.27 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965673 Title: Object 0x... of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1965673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963755] Re: extensions get turned off spontaneously when I log out and log back in
** Changed in: ubuntu Status: Incomplete => Fix Released ** Changed in: ubuntu Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963755 Title: extensions get turned off spontaneously when I log out and log back in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1963755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949075] Re: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949075 Title: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967651] Re: Unicomp trackball/keyboard not recognised in Xorg sessions
Let's keep this bug about the trackball/keyboard problem. Please open a new bug about the flashes in Wayland sessions. That looks like a kernel problem in the amdgpu driver so please run: ubuntu-bug linux ** Summary changed: - jammy beta xorg no kb / mouse + Unicomp trackball/keyboard not recognised in Xorg sessions ** Package changed: xorg-server (Ubuntu) => xserver-xorg-input-libinput (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967651 Title: Unicomp trackball/keyboard not recognised in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1967651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)
Strictly speaking, the fix for this bug was introduced in xorg-server 2:21.1.3-2ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959995 Title: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1959995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965321] Re: u-boot 2022.01+dfsg-2ubuntu1 breaks nvme on RISC-V unmatched board
This bug was fixed in the package u-boot - 2022.01+dfsg-2ubuntu2 --- u-boot (2022.01+dfsg-2ubuntu2) jammy; urgency=medium * d/patches: Add SiFive Unmatched PCIe fix (LP: #1965321) -- Alexandre Ghiti Fri, 25 Mar 2022 11:15:18 +0100 ** Changed in: u-boot (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965321 Title: u-boot 2022.01+dfsg-2ubuntu1 breaks nvme on RISC-V unmatched board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1965321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967703] Re: tlp causing sudden shutdowns, followed by reboot
** Description changed: Ubuntu 20.04. Thinkpad W530. I had `tlp` installed with acpi-call-dkms, which led to errors as described here: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/ (Some details are available there with my posts.) I removed these two packages and then took the advice of @linrunner to use the PPA to install tlp 1.5.0-2. I did not install acpi-call-dkms 1.2.2, figuring I'd just wait for kernel 5.17: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/comments/21 The result on first use after `tlp` install, was that I had a sudden shutdown followed by reboot. I didn't have a battery in my laptop and so assumed the power had gone out. So, I shut down, put the battery in and restarted with the laptop connected to AC. After some time (2 hours?) I had another sudden shutdown/ reboot. They both felt as if the power plug had been pulled. It was at the third shutdown/reboot that I decided to remove `tlp`. I haven't had a problem since. + + `tlp` is no longer installed, so `apport-collect` isn't allowing me to + collect any more information. Let me know if there's something else I + can do. ** Description changed: Ubuntu 20.04. Thinkpad W530. I had `tlp` installed with acpi-call-dkms, which led to errors as described here: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/ (Some details are available there with my posts.) I removed these two packages and then took the advice of @linrunner to use the PPA to install tlp 1.5.0-2. I did not install acpi-call-dkms 1.2.2, figuring I'd just wait for kernel 5.17: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/comments/21 - The result on first use after `tlp` install, was that I had a sudden - shutdown followed by reboot. I didn't have a battery in my laptop and - so assumed the power had gone out. So, I shut down, put the battery in - and restarted with the laptop connected to AC. After some time (2 - hours?) I had another sudden shutdown/ reboot. They both felt as if the - power plug had been pulled. It was at the third shutdown/reboot that I - decided to remove `tlp`. I haven't had a problem since. + The result on first use after `tlp` install, was that after a couple of + hours, I had a sudden shutdown followed by reboot. I didn't have a + battery in my laptop and so assumed the power had gone out. So, I shut + down, put the battery in and restarted with the laptop connected to AC. + After some time (2 hours?) I had another sudden shutdown/ reboot. They + both felt as if the power plug had been pulled. It was at the third + shutdown/reboot that I decided to remove `tlp`. I haven't had a problem + since. `tlp` is no longer installed, so `apport-collect` isn't allowing me to collect any more information. Let me know if there's something else I can do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967703 Title: tlp causing sudden shutdowns, followed by reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1967703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878457] Re: Window shrinks on switching focus
** Bug watch added: github.com/mate-desktop/mate-terminal/issues #350 https://github.com/mate-desktop/mate-terminal/issues/350 ** Also affects: mate-desktop via https://github.com/mate-desktop/mate-terminal/issues/350 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878457 Title: Window shrinks on switching focus To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1878457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967703] [NEW] tlp causing sudden shutdowns, followed by reboot
Public bug reported: Ubuntu 20.04. Thinkpad W530. I had `tlp` installed with acpi-call-dkms, which led to errors as described here: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/ (Some details are available there with my posts.) I removed these two packages and then took the advice of @linrunner to use the PPA to install tlp 1.5.0-2. I did not install acpi-call-dkms 1.2.2, figuring I'd just wait for kernel 5.17: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/comments/21 The result on first use after `tlp` install, was that I had a sudden shutdown followed by reboot. I didn't have a battery in my laptop and so assumed the power had gone out. So, I shut down, put the battery in and restarted with the laptop connected to AC. After some time (2 hours?) I had another sudden shutdown/ reboot. They both felt as if the power plug had been pulled. It was at the third shutdown/reboot that I decided to remove `tlp`. I haven't had a problem since. ** Affects: tlp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967703 Title: tlp causing sudden shutdowns, followed by reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1967703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967702] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967702 Title: Accessibility features have been disabled, modules like speakup_soft and others are missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967702] [NEW] Accessibility features have been disabled, modules like speakup_soft and others are missing
Public bug reported: From very old versions of Kernel for Ubuntu until version 5.13, accessibility features were enabled, allowing blind users to use screen readers in text mode, such as "speakup" via "espeakup" package. In Kernels 5.15 packages for Ubuntu 22.04 beta, such as "linux-image-5.15.0-23-generic", accessibility features are disabled (no justification for such occurrence was listed in the file "changelog.Debian.gz"), with this the espeakup application doesn't work, it depends on the missing speakup_soft module. Missing in the file "/boot/config-5.15.0-23-generic" comparing with the file "/boot/config-5.13.0-39-generic", the line CONFIG_ACCESSIBILITY=y and the following lines are also missing: # # Speakup console speech # CONFIG_SPEAKUP=m CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m CONFIG_SPEAKUP_SYNTH_DUMMY=m # end of Speakup console speech ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tiago 1259 F pulseaudio /dev/snd/pcmC0D0p: tiago 1259 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Apr 3 22:05:39 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220330) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=9e0e837b-49f2-4e10-945a-f7460bcc8286 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0KD03P dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.0:bd12/06/2021:br1.17:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0KD03P:rvrA03:cvnDellInc.:ct10:cvr:sku08CA: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967702 Title: Accessibility features have been disabled, modules like speakup_soft and others are missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939638] Re: [regression] USB device is not detected during boot
Hello Dries and Tilman, Thank you for providing the logs and other relevant information. For clarification, when you were testing if the issue still exists, was this from cold boot or warm boot? And if you sometimes see it working from cold boot it indeed seems to be very racey. There now should be a 100ms power-on-to-good delay on all usb 3.0 hubs since 5.4.0-97, which seems like it used to delay whatever race seems to be going on when the roothubs are being registered (as per the discussion here https://bugzilla.kernel.org/show_bug.cgi?id=214021), but maybe that isn't enough to avoid the race in your case? p.s. If you run lsusb -v as root you should be able to see the bPwrOn2PwrGood value of the root hubs as 100ms. Also, the patchset that seemed to directly address this issue got reverted due to regressions and never seemed to be re-addressed upstream... there seem to be a lot of fixes for those introduced problems since then though so maybe it would make sense to reintroduce those patches. I will send an email to the upstream usb mailing list asking about this and see what their thoughts are. Thanks, - Luke ** Bug watch added: Linux Kernel Bug Tracker #214021 https://bugzilla.kernel.org/show_bug.cgi?id=214021 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939638 Title: [regression] USB device is not detected during boot To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967585] Re: Failed to start ZSYS daemon service (panic: runtime error)
Installing the package jibel linked also fixed bug 1966818 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967585 Title: Failed to start ZSYS daemon service (panic: runtime error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1967585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966818] Re: zsys crashing on snap mounts
This seems to resolve this bug aswell: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1967585/comments/2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966818 Title: zsys crashing on snap mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1966818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967629] Re: gnome-sound-recorder 42 is not wanted for jammy
** No longer affects: gnome-clocks (Ubuntu) ** No longer affects: gnome-weather (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967629 Title: gnome-sound-recorder 42 is not wanted for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sound-recorder/+bug/1967629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962470] Re: Jammy Live installer not producing booting gpt partition table / EFI partition hard drive installations
With the same Xubuntu 20220402 Daily jammy-desktop-2022-04-02-amd64.iso I thought to do an automatic partitioning installation. I knew I would not end up with a XFS formatted root partition, but a booting system with gpt partition table would be better than a non-booting system. The installer created the following partitions: sda1 1MB BIOS BOOT sda2 500MB EFI System sda3 1TB / ext4 So, an additional partition my working Xubuntu 20.04.2 system did not require... the 1MB BIOS BOOT partition. I had high hopes... Nope! Still will not boot from the HDD. I mentioned in my failed installation test results I would update this same defect case with the results of the failed auto partition installation attempt. The only way I can make Xubuntu 22.04 boot on this system is to manually bring up Gparted, create a blank MSDOS partition table, and then a single 1TB / xfs partition... it boots just fine with that legacy configuration... which I do not install as the BIOS is new enough to support UEFI Smart Boot... which I have that disabled. Test system is based on a Intel DG33BU motherboard and Intel Core 2 Duo E8500 CPU -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962470 Title: Jammy Live installer not producing booting gpt partition table / EFI partition hard drive installations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1962470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967677] Re: Mate Panel Menu no longer displays "applications, places, system" for redmond theme.
fresh install into vbox for ubuntu 22.04 mate-desktop incorrect behavior in attached video ** Attachment added: "ubuntu 22.04 mate-desktop.webm" https://bugs.launchpad.net/ubuntu/+source/mate-desktop/+bug/1967677/+attachment/5576584/+files/ubuntu%2022.04%20mate-desktop.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967677 Title: Mate Panel Menu no longer displays "applications, places, system" for redmond theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-desktop/+bug/1967677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967677] Re: Mate Panel Menu no longer displays "applications, places, system" for redmond theme.
ubuntu 20.04 mate-desktop expected behavior in attached video ** Attachment added: "ubuntu 20.04 mate-desktop-2022-04-03T22-31-08-793994000Z.webm" https://bugs.launchpad.net/ubuntu/+source/mate-desktop/+bug/1967677/+attachment/5576583/+files/ubuntu%2020.04%20mate-desktop-2022-04-03T22-31-08-793994000Z.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967677 Title: Mate Panel Menu no longer displays "applications, places, system" for redmond theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-desktop/+bug/1967677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967698] [NEW] Just displays a blank window when running on Wayland
Public bug reported: $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 $ apt-cache policy stellarium stellarium: Installed: 0.20.4-3 Candidate: 0.20.4-3 Version table: *** 0.20.4-3 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status When using Wayland, I expect the application to display a window with controls and sky display. Instead a blank window with a black background is displayed. There are no controls or sky displayed. Running under x-org works as expected. Graphics: OpenGL version string: 4.6.0 NVIDIA 510.60.02 Running from a terminal gives this text: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. - [ This is Stellarium 0.20.4 - https://stellarium.org/ ] [ Copyright (C) 2000-2021 Fabien Chereau et al. ] - Writing log file to: "/home/paul/.stellarium/log.txt" File search paths: 0 . "/home/paul/.stellarium" 1 . "/usr/share/stellarium" Config file is: "/home/paul/.stellarium/config.ini" Default surface format: QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize -1, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Desired surface format: QSurfaceFormat(version 2.1, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) StelGLWidget constructor StelGraphicsScene constructor QOpenGLWidget: Failed to make context current QPainter::begin: Paint device returned engine == 0, type: 1 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::worldTransform: Painter not active QPainter::save: Painter not active QPainter::restore: Unbalanced save/restore QPainter::setWorldTransform: Painter not active QPainter::end: Painter not active, aborted Running with QT_QPA_PLATFORM=wayland stellarium core dumps with (non of the suggestions work): Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. Aborted (core dumped) ** Affects: stellarium (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Just displays a blank window + Just displays a blank window using Wayland ** Summary changed: - Just displays a blank window using Wayland + Just displays a blank window when running on Wayland ** Description changed: $ lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 - $ apt-cache policy stellarium stellarium: - Installed: 0.20.4-3 - Candidate: 0.20.4-3 - Version table: - *** 0.20.4-3 500 - 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 0.20.4-3 + Candidate: 0.20.4-3 + Version table: + *** 0.20.4-3 500 + 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages + 100 /var/lib/dpkg/status I expect the application to display window with controls and sky display. Instead a blank, window with a black background is displayed. There are no controls or sky displayed. + Graphics: + OpenGL version string: 4.6.0 NVIDIA 510.60.02 + + Running from a terminal gives this text: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. - - + - [ This is Stellarium 0.20.4 - https://stellarium.org/ ] [ Copyright (C) 2000-2021 Fabien Chereau et al. ] - - + - Writing log file to: "/home/paul/.stellarium/log.txt" File search paths: - 0 . "/home/paul/.stellarium" - 1 . "/usr/share/stellarium" + 0 . "/home/paul/.stellarium" + 1 . "/usr/share/stellarium" Config file is: "/home/paul/.stellarium/config.ini" Default surface format: QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize -1, redBufferSize -1, greenBufferSize -1,
[Bug 1967673] Re: coredump when attempting to use menu options
When running the app it either immediately segfaults, or displays an initial layout, that if any menu options are selected under account icon, immediately segfaults. I can only find a one line segfault log entry in /var/log/kern.log telegram-deskto[49305]: segfault at 56284c3bd83a ip 562d2b920aa0 sp 7ffd4b076e10 error 4 in telegram-desktop[562d29543000+2a01000] Code: 4c 8b 7f 60 48 89 7c 24 28 64 48 8b 04 25 28 00 00 00 48 89 44 24 48 31 c0 4c 39 fa 75 25 eb 32 66 2e 0f 1f 84 00 00 00 00 00 <8b> 40 04 85 c0 74 1a 49 8b 47 08 48 39 c6 74 18 49 83 c7 28 4c 39 crash file attached ** Attachment added: "_usr_bin_telegram-desktop.1000.crash" https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1967673/+attachment/5576582/+files/_usr_bin_telegram-desktop.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967673 Title: coredump when attempting to use menu options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1967673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942394] Re: [MIR] mdevctl 1.0.0 (rust switch)
** Changed in: mdevctl Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942394 Title: [MIR] mdevctl 1.0.0 (rust switch) To manage notifications about this bug go to: https://bugs.launchpad.net/mdevctl/+bug/1942394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944094] Re: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD
This issue is FIXED with Linux kernel 5.16.0 (tested with liquorix kernel). Details: https://gitlab.freedesktop.org/drm/amd/-/issues/1671 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944094 Title: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967691] Re: Ubuntu Studio will not install on VM with UEFI
** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967691 Title: Ubuntu Studio will not install on VM with UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1967691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967697] [NEW] Not possible to change cpu-frequency
Public bug reported: Hello. Installed Ubuntu 22.04 and trying to set CPU frequency. My CPU is a Intel® Core™ i5-10210U CPU @ 1.60GHz × 8. With Ubuntu 21.10 I was able to set the CPU frequency via Settings -> Power -> Power Mode to all three status (Performance, Balanced, Powersave). With Ubuntu 22.04 this doesn't work anymore. The CPU frequency always stays the same. If I check with s-tui I can see that the frequency is always on demand, no matter what I set. ** Affects: cpufrequtils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967697 Title: Not possible to change cpu-frequency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufrequtils/+bug/1967697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967612] Re: xdg-desktop-portal-gnome crashed with SIGSEGV in wl_proxy_get_version()
*** This bug is a duplicate of bug 1966784 *** https://bugs.launchpad.net/bugs/1966784 Setting the chrome://flags Preferred Ozone platform to Auto works around the problem in Google Chrome Documentation: Selects the preferred platform backend used on Linux. The default one is "X11". "Auto" selects Wayland if possible, X11 otherwise. – Linux #ozone-platform-hint -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967612 Title: xdg-desktop-portal-gnome crashed with SIGSEGV in wl_proxy_get_version() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/1967612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967613] Re: Gnome session reset after docking station disconnects
Another case: [Sun Apr 3 22:13:48 2022] lenovo 0005:17EF:6048.0007: input,hidraw6: BLUETOOTH HID v3.12 Keyboard [ThinkPad Compact Bluetooth Keyboard with TrackPoint] on c8:e2:65:2f:b3:9e [Sun Apr 3 22:21:02 2022] wlp3s0: deauthenticating from 60:3d:26:8c:93:af by local choice (Reason: 3=DEAUTH_LEAVING) [Sun Apr 3 22:21:02 2022] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb 93955633 port 1: DPCD read on addr 0x60 for 1 bytes NAKed [Sun Apr 3 22:21:03 2022] [drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb 93955633 port 1: DPCD read on addr 0x60 for 1 bytes NAKed [Sun Apr 3 22:21:03 2022] PM: suspend entry (deep) [Sun Apr 3 22:21:03 2022] Filesystems sync: 0.006 seconds [Sun Apr 3 22:21:03 2022] Freezing user space processes ... (elapsed 0.276 seconds) done. [Sun Apr 3 22:21:03 2022] OOM killer disabled. [Sun Apr 3 22:21:03 2022] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [Sun Apr 3 22:21:03 2022] printk: Suspending console(s) (use no_console_suspend to debug) [Sun Apr 3 22:21:04 2022] [drm] free PSP TMR buffer [Sun Apr 3 22:21:04 2022] amdgpu :05:00.0: amdgpu: MODE2 reset [Sun Apr 3 22:21:04 2022] ACPI: EC: interrupt blocked [Sun Apr 3 22:21:04 2022] ACPI: Preparing to enter system sleep state S3 [Sun Apr 3 22:21:04 2022] ACPI: EC: event blocked [Sun Apr 3 22:21:04 2022] ACPI: EC: EC stopped [Sun Apr 3 22:21:04 2022] PM: Saving platform NVS memory [Sun Apr 3 22:21:04 2022] Disabling non-boot CPUs ... [Sun Apr 3 22:21:04 2022] IRQ 28: no longer affine to CPU1 [Sun Apr 3 22:21:04 2022] IRQ 41: no longer affine to CPU1 [Sun Apr 3 22:21:04 2022] IRQ 50: no longer affine to CPU1 [Sun Apr 3 22:21:04 2022] IRQ 91: no longer affine to CPU1 [Sun Apr 3 22:21:04 2022] IRQ 95: no longer affine to CPU1 [Sun Apr 3 22:21:04 2022] smpboot: CPU 1 is now offline [Sun Apr 3 22:21:04 2022] IRQ 27: no longer affine to CPU2 [Sun Apr 3 22:21:04 2022] IRQ 39: no longer affine to CPU2 [Sun Apr 3 22:21:04 2022] IRQ 48: no longer affine to CPU2 [Sun Apr 3 22:21:04 2022] IRQ 90: no longer affine to CPU2 [Sun Apr 3 22:21:04 2022] smpboot: CPU 2 is now offline [Sun Apr 3 22:21:04 2022] IRQ 26: no longer affine to CPU3 [Sun Apr 3 22:21:04 2022] smpboot: CPU 3 is now offline [Sun Apr 3 22:21:04 2022] smpboot: CPU 4 is now offline [Sun Apr 3 22:21:04 2022] smpboot: CPU 5 is now offline [Sun Apr 3 22:21:04 2022] ACPI: Low-level resume complete [Sun Apr 3 22:21:04 2022] ACPI: EC: EC started [Sun Apr 3 22:21:04 2022] PM: Restoring platform NVS memory [Sun Apr 3 22:21:04 2022] LVT offset 0 assigned for vector 0x400 [Sun Apr 3 22:21:04 2022] Enabling non-boot CPUs ... [Sun Apr 3 22:21:04 2022] x86: Booting SMP configuration: [Sun Apr 3 22:21:04 2022] smpboot: Booting Node 0 Processor 1 APIC 0x1 [Sun Apr 3 22:21:04 2022] microcode: CPU1: patch_level=0x08600103 [Sun Apr 3 22:21:04 2022] ACPI: \_SB_.PLTF.C001: Found 3 idle states [Sun Apr 3 22:21:04 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 22:21:04 2022] CPU1 is up [Sun Apr 3 22:21:04 2022] smpboot: Booting Node 0 Processor 2 APIC 0x2 [Sun Apr 3 22:21:04 2022] microcode: CPU2: patch_level=0x08600103 [Sun Apr 3 22:21:04 2022] ACPI: \_SB_.PLTF.C002: Found 3 idle states [Sun Apr 3 22:21:04 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 22:21:04 2022] CPU2 is up [Sun Apr 3 22:21:04 2022] smpboot: Booting Node 0 Processor 3 APIC 0x4 [Sun Apr 3 22:21:04 2022] microcode: CPU3: patch_level=0x08600103 [Sun Apr 3 22:21:04 2022] ACPI: \_SB_.PLTF.C003: Found 3 idle states [Sun Apr 3 22:21:04 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 22:21:04 2022] CPU3 is up [Sun Apr 3 22:21:04 2022] smpboot: Booting Node 0 Processor 4 APIC 0x5 [Sun Apr 3 22:21:04 2022] microcode: CPU4: patch_level=0x08600103 [Sun Apr 3 22:21:04 2022] ACPI: \_SB_.PLTF.C004: Found 3 idle states [Sun Apr 3 22:21:04 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 22:21:04 2022] CPU4 is up [Sun Apr 3 22:21:04 2022] smpboot: Booting Node 0 Processor 5 APIC 0x6 [Sun Apr 3 22:21:04 2022] microcode: CPU5: patch_level=0x08600103 [Sun Apr 3 22:21:04 2022] ACPI: \_SB_.PLTF.C005: Found 3 idle states [Sun Apr 3 22:21:04 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 22:21:04 2022] CPU5 is up [Sun Apr 3 22:21:04 2022] ACPI: Waking up from system sleep state S3 [Sun Apr 3 22:21:04 2022] ACPI: EC: interrupt unblocked [Sun Apr 3 22:21:04 2022] ACPI: EC: event unblocked [Sun Apr 3 22:21:04 2022] [drm] PCIE GART of 1024M enabled. [Sun Apr 3 22:21:04 2022] [drm] PTB located at 0x00F40090 [Sun Apr 3 22:21:04 2022] [drm] PSP is resuming... [Sun Apr 3 22:21:04 2022] pci :00:00.2: can't derive routing for PCI INT A [Sun Apr 3 22:21:04 2022] pci :00:00.2: PCI INT A: no GSI [Sun Apr 3 22:21:04 2022] [drm] reserve 0x40 from
[Bug 1940443] Re: [snap] Not included ukrainian language pack
The attachment "nl-oc-uk-support.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940443 Title: [snap] Not included ukrainian language pack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1940443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964695] Re: Pseudo-Terminals are broken, please backport fix from upstream
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964695 Title: Pseudo-Terminals are broken, please backport fix from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967691] Re: Ubuntu Studio will not install on VM with UEFI
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1967691/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967691 Title: Ubuntu Studio will not install on VM with UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1967691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799008] Re: [SRU] Update logo for cosmic
I think this wasn’t done on time for Cosmic; now Jammy has the correct version number in the logo but the point is moot because Ubuntu is getting a new logo. ** Changed in: unity-control-center (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799008 Title: [SRU] Update logo for cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1799008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875505] Re: Unity Tweak Tool or the Appearance settings can't find Yaru
** Changed in: unity-control-center (Ubuntu) Importance: Undecided => Medium ** Changed in: unity-tweak-tool (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875505 Title: Unity Tweak Tool or the Appearance settings can't find Yaru To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1875505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967565] Re: upower takes long time to detect laptop AC charger plugged in
Thanks! ** Changed in: upower (Ubuntu) Status: New => Triaged ** Also affects: upower via https://gitlab.freedesktop.org/upower/upower/-/issues/179 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967565 Title: upower takes long time to detect laptop AC charger plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1967565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967602] Re: intell error
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967602 Title: intell error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967628] Re: Compression dialog not large enough, it truncates the popover for archive type when opened
*** This bug is a duplicate of bug 1967480 *** https://bugs.launchpad.net/bugs/1967480 thanks, that's bug #1967480 and will be fixed in 42.1 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1967480 GUI error in "compress file". Menu content is wider than menu window. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967628 Title: Compression dialog not large enough, it truncates the popover for archive type when opened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1967628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967632] Re: apparmor denied when trying to load pkcs11 module for smart card authentication
Thanks, that's known and on the desktop jira and tracked upstream as https://bugzilla.mozilla.org/show_bug.cgi?id=1734371 ** Bug watch added: Mozilla Bugzilla #1734371 https://bugzilla.mozilla.org/show_bug.cgi?id=1734371 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967632 Title: apparmor denied when trying to load pkcs11 module for smart card authentication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926028] Re: "About this computer" reports 20.04 instead of 20.10
This is fixed in Jammy now. ** Changed in: unity-control-center (Ubuntu) Status: New => Fix Released ** Changed in: unity-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926028 Title: "About this computer" reports 20.04 instead of 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1926028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965812] Re: After "apt upgrade" around Mar 18, shotwell desktop slideshow does not work any more
** Changed in: shotwell (Ubuntu) Status: Incomplete => New ** Summary changed: - After "apt upgrade" around Mar 18, shotwell desktop slideshow does not work any more + slideshow does not work any more with dark mode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965812 Title: slideshow does not work any more with dark mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1965812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967696] Re: [snap] KeePassXC browser integration can't comunicate with KeePassXC app
*** This bug is a duplicate of bug 1741074 *** https://bugs.launchpad.net/bugs/1741074 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 1741074, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1741074 [snap] chrome-gnome-shell extension fails to detect native host connector -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967696 Title: [snap] KeePassXC browser integration can't comunicate with KeePassXC app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967696] [NEW] [snap] KeePassXC browser integration can't comunicate with KeePassXC app
*** This bug is a duplicate of bug 1741074 *** https://bugs.launchpad.net/bugs/1741074 Public bug reported: KeePassXC browser integration does not work on Firefox Snap version. When I try to communicate with a properly configured KeePassXC (browser integration enabled) application, the error appears: "KeePassXC-Browser has encountered an error: Key exchange was not successful. " ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967696 Title: [snap] KeePassXC browser integration can't comunicate with KeePassXC app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967121] Re: Glitch on multiple windows selector when auto-hide is enabled
Indeed. I hadn't tested auto-hide + right click popup yet. But it is glitching as well. I have updated the title of the issue. ** Summary changed: - Glitch on multiple windows selector when auto-hide is enabled + Contextual menus are glitching when auto-hide is enabled (right click + windows selector) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967121 Title: Contextual menus are glitching when auto-hide is enabled (right click + windows selector) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1967121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966589] Re: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1`
@brian-murray Brian Tested Dell Latitude 7280 box 03.04.2022 Before running the upgrade Lubuntu Focal to Lubuntu Jammy I installed Firefox snap with command "snap install firefox" rebooted and ran the "sudo do-release-upgrade -d". The system upgraded and without errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966589 Title: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903920] Re: Warning message about cryptsetup during boot
The correct way to disable the warning seems to be to add RESUME=none to /etc/initramfs-tools/conf.d/resume if your swap has a /dev/urandom key. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903920 Title: Warning message about cryptsetup during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967634] Re: matplotlib python not working in beta 22.04
*** This bug is a duplicate of bug 1967633 *** https://bugs.launchpad.net/bugs/1967633 ** This bug has been marked a duplicate of bug 1967633 matplotlib python not working in beta 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967634 Title: matplotlib python not working in beta 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matplotlib/+bug/1967634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967633] Re: matplotlib python not working in beta 22.04
** Package changed: ubuntu-release-upgrader (Ubuntu) => matplotlib (Ubuntu) ** Summary changed: - matplotlib python not working in beta 22.04 + matplotlib python not working in beta 22.04 under wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967633 Title: matplotlib python not working in beta 22.04 under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matplotlib/+bug/1967633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967635] Re: matplotlib python not working in beta 22.04
*** This bug is a duplicate of bug 1967633 *** https://bugs.launchpad.net/bugs/1967633 ** This bug has been marked a duplicate of bug 1967633 matplotlib python not working in beta 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967635 Title: matplotlib python not working in beta 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1967635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967637] Re: gnome-extensions-app crashing on startup, not producing reportable crash for some reason
*** This bug is a duplicate of bug 1966221 *** https://bugs.launchpad.net/bugs/1966221 thank you for the bug report, it's a known issue under xorg reported as bug #1966221 ** This bug has been marked a duplicate of bug 1966221 gnome-extensions-app crashes with "Segmentation fault (core dumped)" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967637 Title: gnome-extensions-app crashing on startup, not producing reportable crash for some reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967695] Re: xdg-desktop-portal-gnome crashed with SIGSEGV in wl_proxy_get_version()
*** This bug is a duplicate of bug 1966784 *** https://bugs.launchpad.net/bugs/1966784 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1966784, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1967695/+attachment/5576572/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1967695/+attachment/5576574/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1967695/+attachment/5576577/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1967695/+attachment/5576578/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1967695/+attachment/5576579/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1967695/+attachment/5576580/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1967695/+attachment/5576581/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1966784 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967695 Title: xdg-desktop-portal-gnome crashed with SIGSEGV in wl_proxy_get_version() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/1967695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967575] Re: VAAPI is broken in 22.04 (22.3.0+dfsg1-1)
Note: if I download: * intel-media-driver-non-free_22.3.0+ds1-1.dsc * intel-media-driver-non-free_22.3.0+ds1.orig.tar.xz * intel-media-driver-non-free_22.3.0+ds1-1.debian.tar.xz then unpack and rebuild them with dpkg-buildpackage on my own Jammy system, the resulting deb appears to work correctly, as in: * vainfo loads /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so and works OK * /usr/share/mfx/samples/sample_decode can decode a H.264 video in hardware OK So maybe the published .deb files have been built against some incorrect dependency? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967575 Title: VAAPI is broken in 22.04 (22.3.0+dfsg1-1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1967575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967693] Re: intel-media-va-driver-non-free was built against an ABI-breaking version of libigdgmm
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: intel-media-driver-non-free (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967693 Title: intel-media-va-driver-non-free was built against an ABI-breaking version of libigdgmm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver-non-free/+bug/1967693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966362] Re: libigdgmm12 version 22.1.1+ds1-1 breaks vaapi video decoding
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: intel-gmmlib (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966362 Title: libigdgmm12 version 22.1.1+ds1-1 breaks vaapi video decoding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gmmlib/+bug/1966362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967693] [NEW] intel-media-va-driver-non-free was built against an ABI-breaking version of libigdgmm
Public bug reported: Hello, as reported in https://bugs.launchpad.net/ubuntu/+source/intel- gmmlib/+bug/1966362 for Ubuntu 22.04, libigdgmm12 version 22.1.1+ds1-1 had an ABI-breaking change that brokje vaapi - this was fixed with the version 22.1.2+ds1-1, but unfortunately it seems that intel-media-va- driver-non-free 22.3.0+dfsg1-1 (and probably intel-media-va-driver, too) have been built against libigdgmm12 22.1.1+ds1-1, which means that the ABI-incompatibility now exists in reverse - please rebuild intel-media- driver-va-non-free to compile it with libigdgmm12 version 22.1.2+ds1-1 to fix the ABI incompatibilities that break vaapi. ** Affects: intel-media-driver-non-free (Ubuntu) Importance: Undecided Status: Confirmed ** Summary changed: - intel-media-va-driver-non-free was built against an ABI-breaking version of gmmlib + intel-media-va-driver-non-free was built against an ABI-breaking version of libigdgmm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967693 Title: intel-media-va-driver-non-free was built against an ABI-breaking version of libigdgmm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver-non-free/+bug/1967693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961502] Re: anbox fails in lts 22 with anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity [ 2022-02-20 00:55:41] [launch.cpp:71@launch_session_manager_dbus] Fai
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: anbox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961502 Title: anbox fails in lts 22 with anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity [ 2022-02-20 00:55:41] [launch.cpp:71@launch_session_manager_dbus] Failed to start session manager instance via dbus [ 2022-02-20 00:56:56] [daemon.cpp:61@Run] [org.freedesktop.DBus.Error.Timeout] Connection timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anbox/+bug/1961502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967575] Re: VAAPI is broken in 22.04 (22.3.0+dfsg1-1)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: intel-media-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967575 Title: VAAPI is broken in 22.04 (22.3.0+dfsg1-1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1967575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967575] Re: VAAPI is broken in 22.04 (22.3.0+dfsg1-1)
Bug 1966571 supposedly fixed this, with "Rebuild with the current libva version (lp: #1966571)", for package version 22.2.1+dfsg1-1build1, but that specific build unfortunately disappeared from the ubuntu archive. But indeed now it's broken again; not sure what Sebastien Bacher did for bug 1966571 to fix it, except rebuilding against a different version of libva? Or something else? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967575 Title: VAAPI is broken in 22.04 (22.3.0+dfsg1-1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1967575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961581] Re: 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411'
@aletschius For me, running: “sudo modprobe i2c-hid-acpi” on the terminal worked. To avoid running this after every log-in, just add: “i2c-hid-acpi” in a new line to: “/etc/modules” -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961581 Title: 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1961581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940443] Re: [snap] Not included ukrainian language pack
** Patch added: "nl-oc-uk-support.patch" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1940443/+attachment/5576560/+files/nl-oc-uk-support.patch ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940443 Title: [snap] Not included ukrainian language pack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1940443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967691] [NEW] Ubuntu Studio will not install on VM with UEFI
Public bug reported: I tried to install Ubuntu Studio 22.04 Beta on both VirtualBox and VMware set for UEFI with GPT partitioning. I used the same settings that I have previously used to install Ubuntu Studio on both virtual machines and computers. I was also successful installing previous versions of Ubuntu Studio 22.04 (alpha versions) with the settings. When I try the install, I can click "Install Ubuntu Studio"; the screen then changes to a blank screen. My UEFI settings are: 512 Mb FAT32 boot, ~15 Gb root, ~25 Gb home. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967691 Title: Ubuntu Studio will not install on VM with UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1967691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964695] Re: Pseudo-Terminals are broken, please backport fix from upstream
Added testcase and patch ** Patch added: "patch from upstream that fixes the bug" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964695/+attachment/5576559/+files/fix_tty_64char_lines.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964695 Title: Pseudo-Terminals are broken, please backport fix from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964695] Re: Pseudo-Terminals are broken, please backport fix from upstream
** Attachment added: "simple testcase to reproduce the bug" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964695/+attachment/5576558/+files/ptytest_simple.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964695 Title: Pseudo-Terminals are broken, please backport fix from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967690] [NEW] Denied association with wpasupplicant 2:2.10-2
Public bug reported: When I upgraded my computer to Ubuntu 22.04 with "wpasupplicant" version 2:2.10-2, it would no longer connect to my WiFi, but instead tries multiple times without success. The WiFi card is a "Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)", the WiFi access point is a AVM FritzBox 7530 with the current firmware 07.29. The WiFi security is set PSK/personal mode with "WPA 2 + WPA 3". Please see below for Syslog messages. Downgrading to version 2:2.9.0-21build1 makes WiFi connectivity work again. This sound a lot like the following problem to me: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003907 It might not be a bug in package wpasupplicant itself, but it seems to effectively prevent networking and should probably be circumvented. Syslog excerpt with wpasupplicant 2.10: Apr 3 19:32:49 intel2400 wpa_supplicant[11655]: wlan0: SME: Trying to authenticate with xx:xx:xx:xx:xx:xx (SSID='xx' freq=5180 MHz) Apr 3 19:32:49 intel2400 kernel: [22688.198598] wlan0: authenticate with xx:xx:xx:xx:xx:xx Apr 3 19:32:49 intel2400 NetworkManager[849]: [1649007169.4799] device (wlan0): supplicant interface state: disconnected -> authenticating Apr 3 19:32:49 intel2400 kernel: [22688.201456] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3) Apr 3 19:32:49 intel2400 wpa_supplicant[11655]: wlan0: SME: Trying to authenticate with xx:xx:xx:xx:xx:xx (SSID='xx' freq=5180 MHz) Apr 3 19:32:49 intel2400 kernel: [22688.403926] wlan0: authenticate with xx:xx:xx:xx:xx:xx Apr 3 19:32:49 intel2400 kernel: [22688.403938] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3) Apr 3 19:32:49 intel2400 wpa_supplicant[11655]: wlan0: PMKSA-CACHE-ADDED xx:xx:xx:xx:xx:xx 0 Apr 3 19:32:49 intel2400 wpa_supplicant[11655]: wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='xx' freq=5180 MHz) Apr 3 19:32:49 intel2400 NetworkManager[849]: [1649007169.7386] device (wlan0): supplicant interface state: authenticating -> associating Apr 3 19:32:49 intel2400 kernel: [22688.461401] wlan0: authenticated Apr 3 19:32:49 intel2400 kernel: [22688.465084] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3) Apr 3 19:32:49 intel2400 kernel: [22688.467925] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x1511 status=40 aid=0) Apr 3 19:32:49 intel2400 kernel: [22688.467956] wlan0: xx:xx:xx:xx:xx:xx denied association (code=40) Apr 3 19:32:49 intel2400 wpa_supplicant[11655]: wlan0: CTRL-EVENT-ASSOC-REJECT bssid=xx:xx:xx:xx:xx:xx status_code=40 Apr 3 19:32:49 intel2400 wpa_supplicant[11655]: wlan0: SME: Deauth request to the driver failed Apr 3 19:32:49 intel2400 wpa_supplicant[11655]: BSSID xx:xx:xx:xx:xx:xx ignore list count incremented to 2, ignoring for 10 seconds Apr 3 19:32:49 intel2400 NetworkManager[849]: [1649007169.7705] device (wlan0): supplicant interface state: associating -> disconnected Apr 3 19:32:49 intel2400 NetworkManager[849]: [1649007169.8706] device (wlan0): supplicant interface state: disconnected -> scanning [after that it would repeat] ** Affects: wpasupplicant (Ubuntu) Importance: Undecided Status: New ** Package changed: wpa (Ubuntu) => wpasupplicant (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967690 Title: Denied association with wpasupplicant 2:2.10-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1967690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949075] Re: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10
This still happens on a clean 22.04 install (with 5.15.0-23-generic). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949075 Title: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962289] Re: Mediatek AIoT i500 support
I've re-reviewed this, updated README to match the new behavior and tweaked changelog slightly, and I've uploaded this to jammy - failing to add the LP: #1962289 in changelog; it's currently in the UNAPPROVED queue https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text= I agree this should go with Debian along with a bazillion changes we have in Ubuntu, but such "API" like changes would indeed ideally be prioritized in our upstreaming efforts. ** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => Loïc Minier (lool) ** Changed in: flash-kernel (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962289 Title: Mediatek AIoT i500 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675394] Re: Unhelpful error message when neutron server is unavailable
Hello, I am an outreachy applicant. I would like to submit a patch for the stable/ocata branch that fixes this issue if it is decided that this is the right way to fix this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675394 Title: Unhelpful error message when neutron server is unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/python-openstackclient/+bug/1675394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967613] Re: Gnome session reset after docking station disconnects
Another case, this time the same machine but another system: Pop OS! System: Pop Os! 21.10, GNOME 40.4.0, X11 Kernel: 5.16.15-76051615-generic Logs: [Sun Apr 3 19:14:50 2022] PM: suspend entry (deep) [Sun Apr 3 19:14:50 2022] Filesystems sync: 0.007 seconds [Sun Apr 3 19:14:52 2022] Bluetooth: hci0: Timed out waiting for suspend events [Sun Apr 3 19:14:52 2022] Bluetooth: hci0: Suspend timeout bit: 9 [Sun Apr 3 19:14:52 2022] Bluetooth: hci0: Suspend notifier action (3) failed: -110 [Sun Apr 3 19:14:52 2022] Freezing user space processes ... (elapsed 0.003 seconds) done. [Sun Apr 3 19:14:52 2022] OOM killer disabled. [Sun Apr 3 19:14:52 2022] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [Sun Apr 3 19:14:52 2022] printk: Suspending console(s) (use no_console_suspend to debug) [Sun Apr 3 19:14:52 2022] [drm] free PSP TMR buffer [Sun Apr 3 19:14:52 2022] amdgpu :05:00.0: amdgpu: MODE2 reset [Sun Apr 3 19:14:52 2022] ACPI: EC: interrupt blocked [Sun Apr 3 19:14:52 2022] ACPI: PM: Preparing to enter system sleep state S3 [Sun Apr 3 19:14:52 2022] ACPI: EC: event blocked [Sun Apr 3 19:14:52 2022] ACPI: EC: EC stopped [Sun Apr 3 19:14:52 2022] ACPI: PM: Saving platform NVS memory [Sun Apr 3 19:14:52 2022] Disabling non-boot CPUs ... [Sun Apr 3 19:14:52 2022] smpboot: CPU 1 is now offline [Sun Apr 3 19:14:52 2022] smpboot: CPU 2 is now offline [Sun Apr 3 19:14:52 2022] smpboot: CPU 3 is now offline [Sun Apr 3 19:14:52 2022] smpboot: CPU 4 is now offline [Sun Apr 3 19:14:52 2022] smpboot: CPU 5 is now offline [Sun Apr 3 19:14:52 2022] ACPI: PM: Low-level resume complete [Sun Apr 3 19:14:52 2022] ACPI: EC: EC started [Sun Apr 3 19:14:52 2022] ACPI: PM: Restoring platform NVS memory [Sun Apr 3 19:14:52 2022] LVT offset 0 assigned for vector 0x400 [Sun Apr 3 19:14:52 2022] Enabling non-boot CPUs ... [Sun Apr 3 19:14:52 2022] x86: Booting SMP configuration: [Sun Apr 3 19:14:52 2022] smpboot: Booting Node 0 Processor 1 APIC 0x1 [Sun Apr 3 19:14:52 2022] microcode: CPU1: patch_level=0x08600103 [Sun Apr 3 19:14:52 2022] ACPI: \_SB_.PLTF.C001: Found 3 idle states [Sun Apr 3 19:14:52 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 19:14:52 2022] CPU1 is up [Sun Apr 3 19:14:52 2022] smpboot: Booting Node 0 Processor 2 APIC 0x2 [Sun Apr 3 19:14:52 2022] microcode: CPU2: patch_level=0x08600103 [Sun Apr 3 19:14:52 2022] ACPI: \_SB_.PLTF.C002: Found 3 idle states [Sun Apr 3 19:14:52 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 19:14:52 2022] CPU2 is up [Sun Apr 3 19:14:52 2022] smpboot: Booting Node 0 Processor 3 APIC 0x4 [Sun Apr 3 19:14:52 2022] microcode: CPU3: patch_level=0x08600103 [Sun Apr 3 19:14:52 2022] ACPI: \_SB_.PLTF.C003: Found 3 idle states [Sun Apr 3 19:14:52 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 19:14:52 2022] CPU3 is up [Sun Apr 3 19:14:52 2022] smpboot: Booting Node 0 Processor 4 APIC 0x5 [Sun Apr 3 19:14:52 2022] microcode: CPU4: patch_level=0x08600103 [Sun Apr 3 19:14:52 2022] ACPI: \_SB_.PLTF.C004: Found 3 idle states [Sun Apr 3 19:14:52 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 19:14:52 2022] CPU4 is up [Sun Apr 3 19:14:52 2022] smpboot: Booting Node 0 Processor 5 APIC 0x6 [Sun Apr 3 19:14:52 2022] microcode: CPU5: patch_level=0x08600103 [Sun Apr 3 19:14:52 2022] ACPI: \_SB_.PLTF.C005: Found 3 idle states [Sun Apr 3 19:14:52 2022] ACPI: FW issue: working around C-state latencies out of order [Sun Apr 3 19:14:52 2022] CPU5 is up [Sun Apr 3 19:14:52 2022] ACPI: PM: Waking up from system sleep state S3 [Sun Apr 3 19:14:52 2022] ACPI: EC: interrupt unblocked [Sun Apr 3 19:14:52 2022] ACPI: EC: event unblocked [Sun Apr 3 19:14:52 2022] [drm] PCIE GART of 1024M enabled. [Sun Apr 3 19:14:52 2022] [drm] PTB located at 0x00F40090 [Sun Apr 3 19:14:52 2022] [drm] PSP is resuming... [Sun Apr 3 19:14:52 2022] pci :00:00.2: can't derive routing for PCI INT A [Sun Apr 3 19:14:52 2022] pci :00:00.2: PCI INT A: no GSI [Sun Apr 3 19:14:52 2022] nvme :04:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000d address=0xffb0f000 flags=0x] [Sun Apr 3 19:14:52 2022] nvme nvme0: 16/0/0 default/read/poll queues [Sun Apr 3 19:14:52 2022] nvme nvme1: 15/0/0 default/read/poll queues [Sun Apr 3 19:14:52 2022] [drm] reserve 0x40 from 0xf41f80 for PSP TMR [Sun Apr 3 19:14:52 2022] amdgpu :05:00.0: amdgpu: RAS: optional ras ta ucode is not available [Sun Apr 3 19:14:53 2022] amdgpu :05:00.0: amdgpu: RAP: optional rap ta ucode is not available [Sun Apr 3 19:14:53 2022] amdgpu :05:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [Sun Apr 3 19:14:53 2022] amdgpu :05:00.0: amdgpu: SMU is resuming... [Sun Apr 3 19:14:53 2022] amdgpu :05:00.0: amdgpu: dpm has been disabled [Sun Apr 3 19:14:53 2022] amdgpu :05:00.0:
[Bug 1967677] Re: Mate Panel Menu no longer displays "applications, places, system" for redmond theme.
Please clarify with exact steps to reproduce and screenshots. ** Changed in: mate-desktop (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967677 Title: Mate Panel Menu no longer displays "applications, places, system" for redmond theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-desktop/+bug/1967677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967659] Re: Qt apps broken on nVidia/Wayland (Event thread blocked)
David, inspecting the merge request you pointed to, you'll notice that one of those commenters is one of the people I subscribed to this bug. This means we are very well aware of the issue. Also, notice that this package does not contain an ubuntu suffix. This means the package is directly sync'd from Debian. Therefore, while well- placed, this bug report may have been unnecessary. :) I can confirm that GNOME/Wayland sessions aren't affected by this, so that's not the issue here. Remember, Wayland is a protocol, not a display server/library that everything talks to. Each window manager has its own implementation, so what happens with Wayland in KDE does not affect Wayland in GNOME. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967659 Title: Qt apps broken on nVidia/Wayland (Event thread blocked) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwayland-opensource-src/+bug/1967659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967659] Re: Qt apps broken on nVidia/Wayland (Event thread blocked)
I can confirm this. I have no problem launching the KDE Wayland Session under Intel graphics, but switching my system to the dGPU (Nvidia graphics) causes the entire session to crash and several processes hang. ** Also affects: qtwayland-opensource-src (Ubuntu Jammy) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967659 Title: Qt apps broken on nVidia/Wayland (Event thread blocked) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwayland-opensource-src/+bug/1967659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967655] Re: bluetooth
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Changed in: ubuntu Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+question/701187 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967655 Title: bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1967655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967659] Re: Qt apps broken on nVidia/Wayland (Event thread blocked)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtwayland-opensource-src (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967659 Title: Qt apps broken on nVidia/Wayland (Event thread blocked) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwayland-opensource-src/+bug/1967659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922187] Re: [snap] No menu on i3wm/xorg
** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922187 Title: [snap] No menu on i3wm/xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1922187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
