[Bug 1989632] Re: Ctrl+Home shortcut selects first tab instead of going to top of document
This seems to have been fixed, I cannot reproduce anymore ** Changed in: gnome-text-editor (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/1989632 Title: Ctrl+Home shortcut selects first tab instead of going to top of document To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1989632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2011404] Re: vanilla-gnome-desktop depends on pulseaudio which conflicts with pipewire
** Tags added: noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2011404 Title: vanilla-gnome-desktop depends on pulseaudio which conflicts with pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2011404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869225] [NEW] nm-applet should not attempt to create system-wide WiFi connections for regular users
Public bug reported: When a standard (non-administrator user) selects a WiFi network using the applet, the applet attempts to create a system connection, instead of a user connection, and thus it asks for an administrator user's password. On the other hand, if the same standard user opens the WiFi settings and selects a network there, no admin password is requested, as the connection is created for this user only, not system-wide. This is a workaround I discovered recently (see https://askubuntu.com/a/1163852/375543). This has bitten me several times, as I hand out laptops for new users; when they get home, they try to connect to their network and as I have no other way to help them (before I discovered the workaround), I ended up giving them the administrator password. The applet should not attempt to create a system-wide connection for users that are unable to do it. There is no security implication to implement this, as the users are able to create a connection anyway with the workaround mentioned above. But the improvement in terms of UX would be huge. ** Affects: network-manager-applet (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/1869225 Title: nm-applet should not attempt to create system-wide WiFi connections for regular users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1869225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869117] Re: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)
** Also affects: python-pip (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/1869117 Title: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1869117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868914] [NEW] package vanilla-gnome-default-settings 18.10.1 failed to install/upgrade: installed vanilla-gnome-default-settings package post-installation script subprocess returned error exit s
Public bug reported: I got this error when attempting to install vanilla-gnome-desktop on a system just upgraded to 20.04. I don't know if it is related to #1761014. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: vanilla-gnome-default-settings 18.10.1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Wed Mar 25 01:12:09 2020 ErrorMessage: installed vanilla-gnome-default-settings package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2018-12-14 (466 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 2.0.0 SourcePackage: ubuntu-gnome-default-settings Title: package vanilla-gnome-default-settings 18.10.1 failed to install/upgrade: installed vanilla-gnome-default-settings package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2020-03-25 (0 days ago) ** Affects: ubuntu-gnome-default-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868914 Title: package vanilla-gnome-default-settings 18.10.1 failed to install/upgrade: installed vanilla-gnome-default-settings package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1868914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860055] Re: codec can't decode byte 0xff in position 0: invalid start byte
I was able to fix this by upgrading the BIOS on the machine. Still, the error reporting in landscape config could be improved. It could say something like: "Your machine's DMI information could not be decoded and is probably corrupt. Try upgrading your BIOS". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860055 Title: codec can't decode byte 0xff in position 0: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1860055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860055] Re: codec can't decode byte 0xff in position 0: invalid start byte
Same here, also with a NUC. It seems the DMI information is incorrect: gpothier@nuc-reuniones:~$ cat /sys/class/dmi/id/sys_vendor � gpothier@nuc-reuniones:~$ cat /sys/class/dmi/id/chassis_vendor � gpothier@nuc-reuniones:~$ cat /sys/class/dmi/id/product_name � gpothier@nuc-reuniones:~$ cat /sys/class/dmi/id/bios_vendor Intel Corporation However, the failure to decode DMI information is not properly reported I think, as at a timeout error is the output of the command. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860055 Title: codec can't decode byte 0xff in position 0: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1860055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
