[Bug 48734] Re: Home permissions too open
Schools have started installing/upgrading to 22.04.1 and we're just now seeing this. This change takes away the ability of the users to share some of their data WITHOUT involving the administrator. It's not "privacy by default", it's "mandatory privacy". Privacy by default could be done with umask. Administrative actions can mitigate the issue, but they're tricky as they cannot easily be applied to users that haven't logged in yet and folders that don't exist yet. Sudoer scripts that would give the ability to the users to share stuff by themselves can be a worse security risk. On the other hand, encrypted home directories is a trend with similar issues. I guess it'll be a bit easier to rewrite all the programs that need access to /home/username to use other locations such as /run/user/XXX, /home/shared/XXX, /home/public_html/XXX, /var/lib/AccountsService/users/user/face.png, /var/spool/* etc, than to introduce an XDG specification for a new /home/user/private directory, and rewrite all the programs that need private or encryped data to use that one. That would be a much cleaner solution, but it can't be a goal for a single distribution. So while this change does require us to spend some weeks reimplementing our shared folders software, it might be for the best, let's see how it goes. Cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/48734 Title: Home permissions too open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/48734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
I also see it on Ubuntu MATE Jammy. Will the fix come from Xorg, or should we add LightDM to the affected projects list? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922414 Title: ssh-agent fails to start (has_option: command not found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.
I still have the issue in Ubuntu MATE 22.04. Removing ayatana-indicator-application (which replaced indicator-application) works around the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761606 Title: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1761606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962021] Re: Make the deb package install the firefox snap
The commands to install firefox.deb from the PPA are: sudo -i add-apt-repository --yes ppa:mozillateam/ppa echo 'Package: * Pin: release o=LP-PPA-mozillateam Pin-Priority: 1001' >/etc/apt/preferences.d/60local apt install firefox firefox-locale-en If you need more locales like `firefox-locale-el` add them to the last command. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962021 Title: Make the deb package install the firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967728] Re: Some packages need a restart to appear in the menu
*** This bug is a duplicate of bug 1903355 *** https://bugs.launchpad.net/bugs/1903355 ** Also affects: mate-menus (Ubuntu) Importance: Undecided Status: New ** No longer affects: mate-panel (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967728 Title: Some packages need a restart to appear in the menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-menus/+bug/1967728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903355] Re: manually installed software doesn't show in the all programs list until after a reboot
** No longer affects: brisk-menu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903355 Title: manually installed software doesn't show in the all programs list until after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-menus/+bug/1903355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967728] Re: Some packages need a restart to appear in the menu
The attached patch fixes the issue. It replaces g_idle_add(...) that immediately calls the hooks, with g_timeout_add_seconds (1, ...) that calls them a second later, when the symlink to the binary has been generated. It worked in 100% of my tests. ** Patch added: "lp1967728.patch" https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1967728/+attachment/5579971/+files/lp1967728.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967728 Title: Some packages need a restart to appear in the menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1967728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967739] Re: Don't hardcode snap.desktop launcher locations
** Also affects: ubuntu-mate-settings (Ubuntu) Importance: Undecided Status: New ** No longer affects: mate-panel (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967739 Title: Don't hardcode snap.desktop launcher locations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-settings/+bug/1967739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967736] Re: Firefox.deb menu blacklisted in 22.04
The problem is caused by /usr/share/mate/applications/firefox.desktop It contains this line: NoDisplay=true By removing that file, the menu appears again. Reassigning to the correct package `ubuntu-mate-default-settings` that ships it. ** Also affects: ubuntu-mate-settings (Ubuntu) Importance: Undecided Status: New ** No longer affects: mate-panel (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967736 Title: Firefox.deb menu blacklisted in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-settings/+bug/1967736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967736] Re: Firefox.deb menu blacklisted in 22.04
** Summary changed: - Firefox.deb menu missing in 22.04 + Firefox.deb menu blacklisted in 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/1967736 Title: Firefox.deb menu blacklisted in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1967736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967739] Re: Don't hardcode snap.desktop launcher locations
** Description changed: - # grep -r firefox /usr/share/applications + # grep -r firefox /usr/share/mate-panel/layouts ubuntu.layout:launcher-location=/usr/share/applications/firefox.desktop ubuntu-mate.layout:launcher-location=/var/lib/snapd/desktop/applications/firefox_firefox.desktop This means that if someone has firefox.snap installed, they'll see it in the panel if they select ubuntu-mate.layout, but not ubuntu.layout. The opposite will happen if someone has firefox.deb installed. Please use something like `launcher-location=firefox.desktop` instead, and handle the snap-specific paths in the code, so that end users see the panel applications whether they use .debs or .snaps. E.g. currently if a school installs firefox.deb instead of firefox.snap, each student will need to manually add firefox to their panel. - - An alternative idea would be to use "generic-browser", "generic-mailer" icons, and launch "sensible-browser" or "xdg-open ..." instead, but that would be a bigger change, not appropriate so close to the 22.04 release. + An alternative idea would be to use "generic-browser", "generic-mailer" + icons, and launch "sensible-browser" or "xdg-open ..." instead, but that + would be a bigger change, not appropriate so close to the 22.04 release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967739 Title: Don't hardcode snap.desktop launcher locations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1967739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967739] [NEW] Don't hardcode snap.desktop launcher locations
Public bug reported: # grep -r firefox /usr/share/applications ubuntu.layout:launcher-location=/usr/share/applications/firefox.desktop ubuntu-mate.layout:launcher-location=/var/lib/snapd/desktop/applications/firefox_firefox.desktop This means that if someone has firefox.snap installed, they'll see it in the panel if they select ubuntu-mate.layout, but not ubuntu.layout. The opposite will happen if someone has firefox.deb installed. Please use something like `launcher-location=firefox.desktop` instead, and handle the snap-specific paths in the code, so that end users see the panel applications whether they use .debs or .snaps. E.g. currently if a school installs firefox.deb instead of firefox.snap, each student will need to manually add firefox to their panel. An alternative idea would be to use "generic-browser", "generic-mailer" icons, and launch "sensible-browser" or "xdg-open ..." instead, but that would be a bigger change, not appropriate so close to the 22.04 release. ** Affects: mate-panel (Ubuntu) Importance: Undecided Status: New ** Description changed: # grep -r firefox /usr/share/applications ubuntu.layout:launcher-location=/usr/share/applications/firefox.desktop ubuntu-mate.layout:launcher-location=/var/lib/snapd/desktop/applications/firefox_firefox.desktop This means that if someone has firefox.snap installed, they'll see it in the panel if they select ubuntu-mate.layout, but not ubuntu.layout. The opposite will happen if someone has firefox.deb installed. Please use something like `launcher-location=firefox.desktop` instead, and handle the snap-specific paths in the code, so that end users see the panel applications whether they use .debs or .snaps. E.g. currently if a school installs firefox.deb instead of firefox.snap, each student will need to manually add firefox to their panel. + + + An alternative idea would be to use "generic-browser", "generic-mailer" icons, and launch "sensible-browser" or "xdg-open ..." instead, but that would be a bigger change, not appropriate so close to the 22.04 release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967739 Title: Don't hardcode snap.desktop launcher locations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1967739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967736] [NEW] Firefox.deb menu missing in 22.04
Public bug reported: I guess a developer has blacklisted it to avoid duplicate menus at the beta period when snap and deb coexisted, but now that blacklisting isn't needed anymore. Steps to reproduce: 1) Install firefox.deb from the mozillateam PPA: sudo -i add-apt-repository ppa:mozillateam echo 'Package: * Pin: release o=LP-PPA-mozillateam Pin-Priority: 1001' >/etc/apt/preferences.d/mozillateam apt install firefox apt purge snapd 2) At that point, no firefox menu shows up even if you reboot 3) A workaround to make it show up is to rename it: sudo dpkg-divert --divert /usr/share/applications/firefox-diverted.desktop --rename /usr/share/applications/firefox.desktop ** Affects: mate-panel (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/1967736 Title: Firefox.deb menu missing in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1967736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967728] [NEW] Some packages need a restart to appear in the menu
Public bug reported: Steps to reproduce: 1) sudo apt install virtualbox 2) See that it doesn't appear in the menus 3) To make it appear, run any ONE of the following actions: 3a) Logout/login 3b) Or run: mate-panel --reset 3c) Or fake any menu file modification to cause a rescan: sudo sed 's/a/a/' -i /usr/share/applications/mate-calc.desktop This isn't a problem in the VirtualBox packaging. All other desktop environments correctly show its menu. It's a race condition that affects other packages as well; I'll try to explain it below. When installing virtualbox, the following things happen: 1) The virtualbox package is unpacked and it provides a binary at /usr/share/virtualbox/VBox.sh. 2) The virtualbox-qt package is unpacked and it provides the menu at /usr/share/applications/virtualbox.desktop. 3) MATE scans for menu changes. It sees that virtualbox.desktop contains this line: TryExec=VirtualBox It tries to locate a VirtualBox binary, and fails because it doesn't exist yet. It marks that menu as invalid. 4) A split second later the virtualbox-qt installation continues and the debhelper code that corresponds to `debian/virtualbox-qt.links` creates the `/usr/share/virtualbox/VBox.sh /usr/bin/VirtualBox` symlink and makes the VirtualBox binary available. So the menu doesn't show up because it was marked as "missing executable" at step (3); it will show up if we ping the backend to scan the menus once more. The solution would be to postpone the backend scanning for a second, when the symlink will exist. Note that even though brisk-menu defines `BRISK_RELOAD_TIME 2000`, I think this isn't appropriate because it re-uses the wrong backend information from 2 seconds ago, when the symlink was missing. ** Affects: mate-panel (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/1967728 Title: Some packages need a restart to appear in the menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1967728/+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.
The differences are: Old /usr/share/mate-panel/layouts/redmond.layout: [Object mate-menu] locked=true position=0 toplevel-id=bottom applet-iid=MateMenuAppletFactory::MateMenuApplet object-type=applet New /usr/share/mate-panel/layouts/redmond.layout: [Object briskmenu] object-type=applet applet-iid=BriskMenuFactory::BriskMenu toplevel-id=bottom position=0 locked=true I think that the "MateMenuApplet" component isn't available anymore. Personally I've replaced it with the simple menu: My /usr/share/mate-panel/layouts/redmond.layout: [Object menu] locked=true position=0 toplevel-id=bottom object-type=menu An additional issue is that the opensuse.layout is broken now, as it's using the missing component "MateMenuApplet". -- 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/brisk-menu/+bug/1967677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962021] Re: Make the deb package install the firefox snap
The upgrade dialog says: ``` Upgrade to the firefox snap Starting in Ubuntu 22.04, all new releases of firefox are only available to Ubuntu users through the snap package. This package update will transition your system over to the snap by installing it. It is recommended to close all open firefox windows before proceeding to the upgrade. ``` Is it possible to add a button there, so that people that don't want to install snap get a chance to cancel that upgrade, so that they uninstall firefox first, and then resume with their `apt full-upgrade`s? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962021 Title: Make the deb package install the firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875066] Re: Missing NM-icon for established vpn-connections
Another quick workaround is: sudo ln -sf ../../../ubuntu-mono-dark/status/22/nm-device-wired-secure.svg /usr/share/icons/Ambiant-MATE/status/22/nm-device-wired-secure.svg sudo ln -sf ../../../ubuntu-mono-light/status/22/nm-device-wired-secure.svg /usr/share/icons/Radiant-MATE/status/22/nm-device-wired-secure.svg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875066 Title: Missing NM-icon for established vpn-connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1875066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964705] Re: System policy prevents modification of network settings for all users
My problem is a bit different: everything works fine, but the dialog appears when we ACTIVATE a VPN connection, even if we don't want to modify it. 1) I've prepared a VPN connection for my non-admin users and put it in /etc/NetworkManager/system-connections/vpn.nmconnection. 2) When they click to activate it, they get the "System policy prevents..." dialog. 3a) If I do enter the root password there, the vpn.nmconnection file isn't modified. Why did it ask for permission then? 3b) If the users cancel the dialog (twice), they're able to properly connect to the VPN. Why did it show up then? That's on fully updated Ubuntu 20.04.4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964705 Title: System policy prevents modification of network settings for all users To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/964705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962021] Re: Make the deb package install the firefox snap
Will the firefox-esr Debian package be available in universe like all the other browsers there? If not, I guess in cases like netbooted clients where snap apps don't work properly yet, Ubuntu users will have no option but to migrate to google-chrome.deb. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962021 Title: Make the deb package install the firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951676] Re: Ubiquity crash while installing Jammy MATE
** Description changed: I was trying to install today's daily build of Ubuntu MATE 22.04, and a bit after the "user account data" page, ubiquity crashed. - This was inside VirtualBox, so I don't have any weird hardware etc. - A month ago, the daily built has worked fine. + UbiquitySyslog.txt shows that the problem is that + /target/etc/apt/sources.list is missing, and a `grep` command fails the + installation: + + """ + Nov 20 08:35:18 ubuntu-mate ubiquity: grep: /target/etc/apt/sources.list + Nov 20 08:35:18 ubuntu-mate ubiquity: : No such file or directory + ... + ubiquity.install_misc.InstallStepError: AptSetup failed with code 127 + """ + ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 21.10.10 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 Date: Sat Nov 20 10:36:15 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211120) SourcePackage: ubiquity 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/1951676 Title: Ubiquity crash while installing Jammy MATE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1951676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951676] Re: Ubiquity crash while installing Jammy MATE
I guess the culprit shows up in the last lines of the attached UbiquitySyslog.txt: Nov 20 08:35:18 ubuntu-mate ubiquity: grep: /target/etc/apt/sources.list Nov 20 08:35:18 ubuntu-mate ubiquity: : No such file or directory Nov 20 08:35:18 ubuntu-mate plugininstall.py: Exception during installation: Nov 20 08:35:18 ubuntu-mate plugininstall.py: Traceback (most recent call last): Nov 20 08:35:18 ubuntu-mate plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1854, in Nov 20 08:35:18 ubuntu-mate plugininstall.py: install.run() Nov 20 08:35:18 ubuntu-mate plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 60, in wrapper Nov 20 08:35:18 ubuntu-mate plugininstall.py: func(self) Nov 20 08:35:18 ubuntu-mate plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 188, in run Nov 20 08:35:18 ubuntu-mate plugininstall.py: self.configure_apt() Nov 20 08:35:18 ubuntu-mate plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 588, in configure_apt Nov 20 08:35:18 ubuntu-mate plugininstall.py: raise install_misc.InstallStepError( Nov 20 08:35:18 ubuntu-mate plugininstall.py: ubiquity.install_misc.InstallStepError: AptSetup failed with code 127 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951676 Title: Ubiquity crash while installing Jammy MATE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1951676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951676] [NEW] Ubiquity crash while installing Jammy MATE
Public bug reported: I was trying to install today's daily build of Ubuntu MATE 22.04, and a bit after the "user account data" page, ubiquity crashed. This was inside VirtualBox, so I don't have any weird hardware etc. A month ago, the daily built has worked fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 21.10.10 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 Date: Sat Nov 20 10:36:15 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211120) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-21.10.10 ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951676 Title: Ubiquity crash while installing Jammy MATE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1951676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892014] Re: 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS
The issue is still there in today's Ubuntu MATE 22.04 daily built. Greeks cannot even type their names in the installer (ubiquity)... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892014 Title: 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1892014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951674] [NEW] Incorrectly warns "No EFI System Partition was found" on BIOS/MBR
Public bug reported: While installing Ubuntu MATE 22.04 under BIOS mode, I select manual partitioning and I create an MBR disk with a single ext4 partition. Then I get a dialog with this warning: """ Go back to the menu and resume partitioning? No EFI System Partition was found. This system will likely not be able to boot successfully, and the installation process may fail. Please go back and add an EFI System Partition, or continue at your own risk. """ That dialog is inappropriate there and may scare inexperienced users. Ubiquity could check that /sys/firmware/efi doesn't exist, and that the disk is formatted with MBR, and not display that dialog. ** Affects: ubiquity (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/1951674 Title: Incorrectly warns "No EFI System Partition was found" on BIOS/MBR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1951674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916377] Re: ayatana-indicator-printers-service crashed with SIGSEGV in __GI_____strtol_l_internal()
This is still an issue on Ubuntu MATE 22.04 daily build, tested today. I also marked other 5 instances of the same issue as duplicates of this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916377 Title: ayatana-indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1916377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928667] Re: ayatana-indicator-printers-service crashed with SIGSEGV in __GI_____strtol_l_internal()
*** This bug is a duplicate of bug 1916377 *** https://bugs.launchpad.net/bugs/1916377 ** This bug has been marked a duplicate of bug 1916377 ayatana-indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928667 Title: ayatana-indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-printers/+bug/1928667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933811] Re: ayatana-indicator-printers-service crashed with SIGSEGV in __GI_____strtol_l_internal()
*** This bug is a duplicate of bug 1916377 *** https://bugs.launchpad.net/bugs/1916377 ** This bug has been marked a duplicate of bug 1916377 ayatana-indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933811 Title: ayatana-indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-printers/+bug/1933811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577117] Re: unknown file type error while saving
This is still an issue in Ubuntu 22.04, I reported it upstream there: https://bugs.kde.org/show_bug.cgi?id=444998 ** Bug watch added: KDE Bug Tracking System #444998 https://bugs.kde.org/show_bug.cgi?id=444998 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577117 Title: unknown file type error while saving To manage notifications about this bug go to: https://bugs.launchpad.net/kdeedu/+bug/1577117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875129] Re: [SRU] Upgrade to 1.7.3.4 to fix regression breaking Epoptes
@brian-murray, this is about a microrelease: https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases What .debdiff would I upload here? The new version is already in Ubuntu, it could just be copied... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875129 Title: [SRU] Upgrade to 1.7.3.4 to fix regression breaking Epoptes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/socat/+bug/1875129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772859] Re: Network Manager is not able to manage the devices on Ubuntu 18.04
While working on a remote server, it took me 2-3 hours to locate this bug report and apply its workarounds. It's certainly not a good default behavior. In case someone has already removed netplan, the recommended steps to get network-manager to manage the interfaces, as I understood them, are: ``` sudo -i apt install ubuntu-minimal echo "# Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager" >/etc/netplan/01-network-manager-all.yaml update-initramfs -u # Not sure if this is needed or not reboot ``` I.e. I think that /etc/netplan/01-network-manager-all.yaml comes from some installer and it's not part of some package and it needs to be manually re-created. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926355] Re: Snap applications segfault with new core20 (rev: 1015+)
Another variant of the problem that I mentioned in comment #15. An
ubuntu user just reported it on IRC:
$ apt install clang
The following packages have unmet dependencies:
clang : Depends: clang-10 (>= 10~) but it is not going to be installed
That apt message is misleading, as the underlying error is the libc6
version:
$ dpkg -l | awk '$3=="2.31-0ubuntu9.3" { print $2, $3 }'
libc-bin 2.31-0ubuntu9.3
libc-dev-bin 2.31-0ubuntu9.3
libc6:amd64 2.31-0ubuntu9.3
libc6:i386 2.31-0ubuntu9.3
libc6-dbg:amd64 2.31-0ubuntu9.3
libc6-dev:amd64 2.31-0ubuntu9.3
locales 2.31-0ubuntu9.3
To be able to install clang, all these packages would have to be
downgraded manually, with:
$ sudo apt install $(dpkg -l | awk '$3=="2.31-0ubuntu9.3" { print
$2"=2.31-0ubuntu9.2" }')
The following packages will be DOWNGRADED:
libc-bin libc-dev-bin libc6 libc6:i386 libc6-dbg libc6-dev locales
But we can't expect thousands of Ubuntu users to run that command manually.
Please do upload a new glibc 2.31-0ubuntu9.4 version, to amend 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/1926355
Title:
Snap applications segfault with new core20 (rev: 1015+)
To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-core20/+bug/1926355/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 206924] Re: Make it possible to create a guest account
** No longer affects: ltsp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206924 Title: Make it possible to create a guest account To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/206924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839431] Re: ldm logs users with non-default login shell in as root
Closing old LTSP bugs as they're no longer relevant after LTSP has been rewritten from scratch. ** No longer affects: ldm (Ubuntu) ** Changed in: ltsp 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/1839431 Title: ldm logs users with non-default login shell in as root To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/1839431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 220947] Re: Installer progress bar is not very indicative of progress
Closing old LTSP bugs as they're no longer relevant after LTSP has been rewritten from scratch. ** Changed in: ltsp (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/220947 Title: Installer progress bar is not very indicative of progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/220947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 949360] Re: No icon for USB drives on desktop or unity launcher
Closing old LTSP bugs as they're no longer relevant after LTSP has been rewritten from scratch. ** Changed in: ltsp (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/949360 Title: No icon for USB drives on desktop or unity launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/949360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 540571] Re: [needs-packaging] Please break ltsp-build-client and ltsp-update-image out into a separate package
Closing old LTSP bugs as they're no longer relevant after LTSP has been rewritten from scratch. ** Changed in: ltsp (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: ltsp (Ubuntu) Assignee: Jonathan Carter (jonathan) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/540571 Title: [needs-packaging] Please break ltsp-build-client and ltsp-update-image out into a separate package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/540571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977369] Re: No Icon when using usb pendrive, Ubuntu 12.04
Closing old LTSP bugs as they're no longer relevant after LTSP has been rewritten from scratch. ** Changed in: ltsp (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977369 Title: No Icon when using usb pendrive, Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/977369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1052020] Re: Ltsp-build-client updates kernel a tftboot for all images
Closing old LTSP bugs as they're no longer relevant after LTSP has been rewritten from scratch. ** No longer affects: ltsp (Ubuntu) ** Changed in: ltsp Status: Confirmed => Won't Fix ** Changed in: ltsp Assignee: Vagrant Cascadian (vagrantc) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1052020 Title: Ltsp-build-client updates kernel a tftboot for all images To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/1052020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433712] Re: apt-pinning is non-functional when building LTSP client chroot
Closing old LTSP bugs as they're no longer relevant after LTSP has been rewritten from scratch. ** Changed in: ltsp (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433712 Title: apt-pinning is non-functional when building LTSP client chroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1433712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836791] Re: LDM SegFault when loading additional plugins
Closing old LTSP bugs as they're no longer relevant after LTSP has been rewritten from scratch. ** Changed in: ldm (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836791 Title: LDM SegFault when loading additional plugins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldm/+bug/1836791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802707] Re: Error: 'C.UTF-8' is not a supported language or locale
Closing old LTSP bugs as they're no longer relevant after LTSP has been rewritten from scratch. ** Changed in: ltsp (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802707 Title: Error: 'C.UTF-8' is not a supported language or locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1802707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926355] Re: Snap applications segfault with new core20 (rev: 1015+)
Hi, the libc update + removal caused the following issue: 1) On 2021-04-26, libc version 2.31-0ubuntu9.3 got uploaded to Ubuntu Focal. 2) Many people updated to it. 3) Two days later, on 2021-04-28, it got removed because it was causing the issues descripted in this bug report. 4) If any of the persons that updated, tries to install libc6-dev now, it says it's not installable as it depends on libc6=2.31-0ubuntu9.2, while 2.31-0ubuntu9.3 is installed. In some cases they can downgrade with `apt install libc6=2.31-0ubuntu9.2`, but that's not always easy when additional dependencies are involved. I believe a solution would be to re-upload 2.31-0ubuntu9.2 as 2.31-0ubuntu9.4. This would then not break snap, while allowing people to install libc6-dev, as it wouldn't have a lower version than in the archives anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926355 Title: Snap applications segfault with new core20 (rev: 1015+) To manage notifications about this bug go to: https://bugs.launchpad.net/snap-core20/+bug/1926355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813541] Re: Shim uses wrong TFTP server IP in proxyDHCP mode
@patpat, see at that top of this page, the link that says: auto-github-rhboot-shim #165 You can check the discussion there; I haven't tested any more recent upstream binaries to see if they work now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813541 Title: Shim uses wrong TFTP server IP in proxyDHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/shim/+bug/1813541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902109] Re: rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted
Since this was fixed upstream and it doesn't affect any LTS Ubuntu releases, I don't think it's important enough to do SRUs. Thank you! (For LTSP users, that are affected by this: once a fixed rsync version lands in Ubuntu, I'll copy it to the LTSP PPA for Groovy, so LTSP will work there too) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902109 Title: rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1902109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902879] Re: [SRU] slick-greeter crashes after recent systemd update
Thank you Andy, slick-greeter 1.1.4-1ubuntu0.18.04.1 from proposed did indeed solve the problem for me in Ubuntu MATE 18.04. I'll set the appropriate verification tag. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902879 Title: [SRU] slick-greeter crashes after recent systemd update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slick-greeter/+bug/1902879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902879] Re: slick-greeter crashes after recent systemd update
Thank you Sebastien, I updated the title and description with the SRU information. Focal isn't impacted by this, no need to SRU there, it's only needed for bionic. ** Description changed: - Systemd 237-3ubuntu10.43 landed this week in Bionic, and it enforces - memory limits (LP: #1830746). + [Impact] + Systemd 237-3ubuntu10.43 landed this week in Bionic, and it enforces memory limits (LP: #1830746). This makes slick-greeter crash, which people observe as "black screen with blinking cursor". seb128 proposed that we need this commit backported: https://github.com/linuxmint/slick-greeter/commit/f9af95ea3f.patch Similar issues have also been discussed in LP: #1662244 and in https://github.com/canonical/lightdm/issues/55. + + [Test case] + Try to boot with an up to date Ubuntu MATE 18.04 system, without having autologin enabled. A black screen with a blinking cursor will appear, instead of lightdm/slick-greeter. + + [Regression potential] + Low. It's an upstream patch that affects a specific small part of the code, which has been tested widely in more recent version of Ubuntu, like Bionic. I've also tested a package with this patch applied and it seems to work fine. ** Summary changed: - slick-greeter crashes after recent systemd update + [SRU] slick-greeter crashes after recent systemd update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902879 Title: [SRU] slick-greeter crashes after recent systemd update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slick-greeter/+bug/1902879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902879] Re: slick-greeter crashes after recent systemd update
I couldn't find the slick-greeter git sources in launchpad so I uploaded a patched version in https://code.launchpad.net/~ts.sch.gr/+git/slick-greeter. I also used a recipe to build it, the updated packages are available in the Greek schools PPA if anyone needs them: https://code.launchpad.net/~ts.sch.gr/+archive/ubuntu/ppa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902879 Title: slick-greeter crashes after recent systemd update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slick-greeter/+bug/1902879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902879] Re: slick-greeter crashes after recent systemd update
I verify that the patch that seb128 proposed solves the issue for slick-greeter. Should I link a branch with it applied, will it speed up the resolution of 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/1902879 Title: slick-greeter crashes after recent systemd update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slick-greeter/+bug/1902879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)
Thank you Łukasz, I filed it in LP: #1902879. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830746 Title: memlock setting in systemd (pid 1) too low for containers (bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902879] [NEW] slick-greeter crashes after recent systemd update
Public bug reported: Systemd 237-3ubuntu10.43 landed this week in Bionic, and it enforces memory limits (LP: #1830746). This makes slick-greeter crash, which people observe as "black screen with blinking cursor". seb128 proposed that we need this commit backported: https://github.com/linuxmint/slick-greeter/commit/f9af95ea3f.patch Similar issues have also been discussed in LP: #1662244 and in https://github.com/canonical/lightdm/issues/55. ** Affects: slick-greeter (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902879 Title: slick-greeter crashes after recent systemd update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slick-greeter/+bug/1902879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662244] Re: lightdm causes all greeters to fail to start
What torel proposed in https://bugs.launchpad.net/ubuntu/+source/unity- greeter/+bug/1662244/comments/14 avoids the segfault: * soft memlock 262144 * hard memlock 262144 Should all lightdm users manually put that in limits.conf, or should we expect some update? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662244 Title: lightdm causes all greeters to fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1662244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)
What torel proposed in https://bugs.launchpad.net/ubuntu/+source/unity- greeter/+bug/1662244/comments/14 avoids the segfault: * soft memlock 262144 * hard memlock 262144 Should all lightdm users manually put that in limits.conf, or should we expect some update? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830746 Title: memlock setting in systemd (pid 1) too low for containers (bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662244] Re: lightdm causes all greeters to fail to start
Hi, a recent systemd update in 18.04 makes slick-greeter segfault. So all Ubuntu MATE 18.04 users now get black screens instead of lightdm. It's related to memory limits so I'm cross-referencing it here: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746 This didn't help: [LightDM] lock-memory=false Can I put something in /etc/security/limits.conf to see if it helps? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662244 Title: lightdm causes all greeters to fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1662244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)
Hi, this update makes slick-greeter segfault, so Ubuntu MATE 18.04 users doing normal updates now get a black screen with a flicking cursor. A temporary workaround is to enable autologin in /etc/lightdm/lightdm.conf: [Seat:*] autologin-guest=false autologin-user=administrator autologin-user-timeout=0 *** What would be a proper fix for this? *** A related discussion about memory limits and lightdm issues exists in this bug report: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1662244 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830746 Title: memlock setting in systemd (pid 1) too low for containers (bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902109] Re: rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted
Hi Robie, thank you for the feedback, I located an upstream bug report in glibc for this: https://sourceware.org/bugzilla/show_bug.cgi?id=26401 ** Bug watch added: Sourceware.org Bugzilla #26401 https://sourceware.org/bugzilla/show_bug.cgi?id=26401 ** Also affects: rsync via https://sourceware.org/bugzilla/show_bug.cgi?id=26401 Importance: Unknown Status: Unknown ** No longer affects: rsync ** Also affects: glibc via https://sourceware.org/bugzilla/show_bug.cgi?id=26401 Importance: Unknown Status: Unknown ** Also affects: glibc (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/1902109 Title: rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1902109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902109] [NEW] rsync uses lchmod and fails in Ubuntu >= 20.10
Public bug reported:
Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it
returned "no" before.
Steps to reproduce:
# Emulate /proc not being mounted
$ mount --bind / /mnt
$ chroot /mnt rsync -a /bin/ls .
rsync: [receiver] failed to set permissions on "/.ls.CDExhu": Operation not
supported (95)
rsync error: some files/attrs were not transferred (see previous errors) (code
3) at main.c(1330) [sender=3.2.3]
I reported this issue upstream in
https://github.com/WayneD/rsync/issues/109 but the rsync developer says
it's a problem in libc, and it might well be.
Simple C code to reproduce the problem without rsync:
printf("lchmod returned: %d\n", lchmod("/tmp/ls", 0755));
If /tmp/ls is e.g. mode=0123, and needs to be changed, lchmod fails when
/proc isn't mounted, yet it succeeds if it is mounted.
Python had a similar issue, and they ended up avoiding
AC_CHECK_FUNC(lchmod) under Linux:
https://bugs.python.org/issue34652
https://github.com/python/cpython/commit/69e96910153219b0b15a18323b917bd74336d229#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810R3140
```c
if test "$MACHDEP" != linux; then
AC_CHECK_FUNC(lchmod)
fi
```
So I'm not sure which package is causing the bug here. Should autoconf
return false? Should libc implement lchown without the bug? Or should
rsync skip lchmod under Linux, like python did?
** Affects: rsync (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/1902109
Title:
rsync uses lchmod and fails in Ubuntu >= 20.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1902109/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
In case anyone needs to install the last known binaries that work, I uploaded a nice overview of the problem and direct links to the Ubuntu packages here: https://github.com/alkisg/liveusb/issues/3 ** Bug watch added: github.com/alkisg/liveusb/issues #3 https://github.com/alkisg/liveusb/issues/3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855594] Re: Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main)
After observing for months how schools handled this issue, I'd like to confirm my initial predictions; all of them now install google-chrome instead of chromium-browser in order to avoid snap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855594 Title: Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium/+bug/1855594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897298] [NEW] apturl uses --no-install-recommends
Public bug reported: In Ubuntu MATE 20.04, `apt install wine` pulls wine32 as a recommended dependency, while `xdg-open apt:wine` doesn't install wine32; it's like if `apt --no-install-recommends` was used, which according to Debian Policy isn't appropriate. ** Affects: apturl (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/1897298 Title: apturl uses --no-install-recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apturl/+bug/1897298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
Same problem here when telling software-properties-gtk to refresh the cache, in Ubuntu MATE 20.04.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829401 Title: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854190] Re: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow
*** This bug is a duplicate of bug 1829401 *** https://bugs.launchpad.net/bugs/1829401 ** This bug has been marked a duplicate of bug 1829401 gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854190 Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1854190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892014] Re: 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS
Hi Gunnar, thank you for the feedback,
> Possibly console-setup could be modified again, so the default
shortcut depends on XDG_CURRENT_DESKTOP ("No toggling" for GNOME and
"Alt+Shift" for others). That way there wouldn't be a need to involve
ubiquity or other desktops.
When launching a console, XDG_CURRENT_DESKTOP isn't guaranteed to be
set. E.g. one can just switch to vt2 and login there, or one can run
`sudo -i` which doesn't preserve the XDG_* environment variables. Losing
the ability to type Greek because I used `sudo -i` wouldn't be
appropriate.
> Right. Super+Space is default on GNOME.
Up to now, /etc/default/keyboard allowed for defining a shortcut
GLOBALLY, and the console, the display managers, and all the desktop
environments respected that. Is supporting "a global shortcut" no longer
a Debian/Ubuntu goal?
> That's reasonably about personal preferences rather than geographical.
Well, the official Greek school books teach Alt+Shift for layout
toggling, so I'm not sure it can be called a "personal preference" and
not a geographical one. That said, I wouldn't mind if Linux decided to
globally endorse Win+Space, but AFAIK console doesn't support Win+Space
as an option yet.
> As regards the console, is there a use case which would be worth to
take into consideration where there is a need to switch to a non-latin
keyboard layout?
Normal PC usage is impossible without it. Some examples:
# Change directory to Desktop
cd "Επιφάνεια εργασίας"
# Edit a file
nano Αρχείο.txt
# Set a user's name
usermod -c Άλκης alkisg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892014
Title:
18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1892014/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately
The problem is not in firefox or mate, it's in gdebi-gtk, and specifically in GDebiGtk.py, line 619: os.execv(pkexec_cmd, pkexec_args+gdebi_args) This replaces the current process with a pkexec call. This is not a valid usage of pkexec, as pkexec requires the parent process to not be init (ppid!=1). To reproduce the issue without firefox, one can just run `setsid gdebi- gtk package.deb`. In a similar bug report for update-manager (LP: #1020115), this flag was used instead of os.execv: flags = GObject.SPAWN_DO_NOT_REAP_CHILD https://bazaar.launchpad.net/~ubuntu-core-dev/update-manager/main/view/head:/UpdateManager/backend/InstallBackendSynaptic.py#L63 Is gdebi still maintained by Ubuntu developers, or should we report this in Debian? Can we propose a patch similar to the update manager, or even just use a simple shell wrapper? ** Summary changed: - Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox + gdebi-gtk calls pkexec inappropriately ** No longer affects: firefox (Ubuntu) ** Project changed: ubuntu-mate => gdebi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: gdebi-gtk calls pkexec inappropriately To manage notifications about this bug go to: https://bugs.launchpad.net/gdebi/+bug/1854588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892014] Re: 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS
> I can't recall that Ubiquity asks about shortcut for switching input sources. I believe it relied on console-setup for the correct default. So, console-setup shouldn't stop providing a default until AFTER ubiquity had a question about "how to toggle the layout". > Please take into consideration that standard Ubuntu does not need it. The previous default Alt+Shift caused confusion and issues. I just tested on Ubuntu GNOME and I can't switch the layout with Alt+Shift. I can switch it with Win+Space, which isn't appropriate for Greece. Also, I can't type Greek in neither the console nor in GDM. Gunnar, what are you proposing? I believe that LP: #1762952 should be reverted, and if GNOME chokes while reading /etc/default/keyboard, then we can work on fixing GNOME. Are you proposing that we should file bugs against console-setup, all display managers, and all other desktop environments, to assume a default toggling switch, because we can't fix GNOME? In which direction should I be trying to resolve this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892014 Title: 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1892014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892014] Re: 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS
Regarding the "which shortcut should be used by default for toggling layouts". Ubuntu or Gnome should not decide that shortcut worldwide. It depends on the locale. In Greece, we've been using Alt+Shift since at least the '80s. Windows recently started offering Win+Space as well, but in parallel, without cancelling Alt+Shift, and very few people use Win+Space here. AFAIK console-setup already has code to provide the correct defaults for most locales. If, for some locales, there's no sensible default, then ubiquity should ASK the user, not default to "none". None does not make sense; of course a Greek user will need to type Greek. Console-setup already has such a dialog, if ubiquity doesn't want to use a default shortcut after 18.04.2, it should at least present the layout toggling switch dialog, NOT default to "none". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892014 Title: 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1892014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892014] Re: 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS
> How do you define "right" and "wrong" in this context? After selecting "Greece/Greek" in an operating system installer, users should be able to switch between English and Greek in the console, and IF they run a GUI, in the display manager (to type the password), AND in the desktop environment after login. As far as I can remember, this was solved centrally in console-setup, up to 18.04.2, when layout switching stopped working. These 3 use cases (console, login screen, display environment) are the essential ones, the "system defaults". Now additionally, there's another need: in multi-user and multi-cultural environments, per-user settings might be needed. IF there's need for that, then sysadmins should select a display manager and a desktop environment that supports it. So "most" of the users will still be using the defaults, while "some" of the users will have to go to the desktop environment settings and choose a layout different to the default. But having the desktop environment support different layouts per user, should in no way cancel the defaults; it should not prohibit the console users or the all-users-have-the-same-language environments from typing Greek, like it does now. What I'm proposing: If I run `dpkg-reconfigure keyboard-configuration`, I'm presented with some questions/options. Most installers like ubiquity or debian-installer ask the same questions/options. So, /etc/default/keyboard ***SHOULD BE THE SAME IN BOTH CASES***. I believe that's they key part, if we can agree on that we can the propose solutions. After 18.04.2, ubiquity generates a different /etc/default/keyboard than `dpkg-reconfigure keyboard-configuration`, and I think this is a bug in ubiquity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892014 Title: 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1892014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892014] Re: 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS
Hi Gunnar, thank you for your input, > Why is there a need to switch keyboard layout during the installation? One example is to set the user name, e.g. Διαχειριστής (Administrator). Another is to be able to surf etc while ubiquity is running in the background. > As regards post-install, i.e. at first boot/login, the desktop environment ought to provide some default shortcut for switching input sources. By with package? Xorg by itself supports Alt+Shift, and this worked fine up to 18.04.1, while it broke in 18.04.2, is "plain xkb" now unsupported? By default, MATE doesn't ship ibus or fcitx, isn't that OK? I haven't tested in other flavors yet.. `setxkbmap -query` shows the wrong settings now; if one runs `dpkg- reconfigure keyboard-configuration` after installation, then it works fine again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892014 Title: 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1892014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Hi, this fix caused a regression in ubiquity: LP: #1892014 Ubiquity doesn't put alt_shift_toggle in XKBOPTIONS anymore, so we cannot switch to e.g. Greek using Alt+Shift, after going through a normal installation (or even in the live session). Are users expected to manually run `dpkg-reconfigure keyboard- configuration` right after a GUI installation of Ubuntu? E.g. ubuntu-mate-18.04.2-desktop-amd64.iso is affected while 18.04.1 isn't. Should this issue be resolved in console-setup or in ubiquity? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892014] [NEW] 18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS
Public bug reported:
Up to ubuntu-mate-18.04.1.iso, everything was fine. Starting with
18.04.2, XKB_OPTIONS does not contain "alt_shift_toggle" anymore and we
cannot switch the keyboard layout to e.g. Greek using Alt+Shift.
Reading the changelog, I see:
$ ~/source/ubiquity$ git show 786a5325ef
+console-setup (1.178ubuntu6) cosmic; urgency=medium
+
+ * keyboard-configuration.{config,templates}: There is no good default for
+layout toggling, stop pretending there is. Console users can set one
+with dpkg-reconfigure or editing /etc/defaults/keyboard (LP: #1762952)
I'm guessing that ubiquity duplicates some code from console-setup, and
LP: #1762952 caused this regression.
To reproduce:
1) Start ubuntu-mate-18.04.1-desktop-amd64.iso
2) Select Ελληνικά (Greek) and start installing Ubuntu using the default options
3) Right after the keyboard layout step, run:
$ grep XKBOPTIONS /etc/default/keyboard
XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll"
4) Verify that you can switch to Greek with Alt+Shift
Starting from ubuntu-mate-18.04.2-desktop-amd64.iso (.1=OK, .2=BAD), we cannot
switch to Greek using Alt+Shift anymore:
$ grep XKBOPTIONS /etc/default/keyboard
XKBOPTIONS="grp_led:scroll"
Does ubiquity really expect the users to run `dpkg-reconfigure console-
setup`?
Note that selecting Greek in the syslinux menu produces the correct
XKBOPTIONS, yet ubiquity overwrites them later on with the wrong ones.
** Affects: ubiquity (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/1892014
Title:
18.04.14.7 regression: no alt_shift_toggle in XKBOPTIONS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1892014/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
Thank for you all the feedback guys, OK, since upstream already replied "won't fix", of course there's no point to report an issue. As long as i386 installations are still supported, we that need this functionality, can keep using the last working grub. > Why are you not using -amd64.iso? One use case is to be able to use the same .iso or live USB or netbooted installation for many client computers. For example, we have a few hundred schools here that have both 32bit and 64bit clients; they all netboot from a 32bit installation so that the teacher doesn't have to maintain many installations. We can keep using the old grub until 18.04 is EOLed in 2023. Another use case is to be able to troubleshoot 32bit-only bugs in 64bit hardware (that in some cases only supports UEFI booting); for example, Ryzen/amdgpu-based computers currently show black screen with 32bit installations yet they work fine with 64bit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
Hello Hamish, please do; as currently I'm developing a lot of software for schools that open in September, so for the next few months I won't have time to file this. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557367] Re: gnome-flashback crashed with signal 5 in doGetScreenResources()
Ouch again launchpad sends no notifications... @Alberts, we've switched to Ubuntu MATE in 2016, so I'm not sure if this is still an issue or not... thank you though :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557367 Title: gnome-flashback crashed with signal 5 in doGetScreenResources() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1557367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766859] Re: Display corrupted in virtualbox
It still happens with the latest virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 on Ubuntu 20.04.1 and kernel 5.4. ** Changed in: virtualbox (Ubuntu) Status: Expired => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766859 Title: Display corrupted in virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1766859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
> Why not use a 64-bit kernel? Should be a much better option. Because I'm trying to boot the stock, unmodified lubuntu-18.04.5-desktop-i386.iso that was released yesterday. It has a 32bit kernel. > If you manually hacked together an i386 install in UEFI mode, it's up to you to maintain. It's just a custom grub.cfg. I believe that using the "loopback" command to boot a vanilla ubuntu .iso should be within the "normal, supported use of grub". People using grub should be allowed to ask for support even though the installer uses grub in a different way. Grub doesn't exist in the archive only to serve ubiquity. Anyways, since the problem came from redhat, we should move the discussion there and the fix will eventually reach Ubuntu, thank you very much for that information! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867415] Re: Hardlinking snaps wastes 400 MB tmpfs RAM in live CDs
The 20.04.1 live CDs appear not to be affected anymore, /cow only uses 50M RAM now. Thumbs up! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867415 Title: Hardlinking snaps wastes 400 MB tmpfs RAM in live CDs To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1867415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805129] Re: glade crash: drawable is not a native X11 window
** Also affects: appmenu-gtk-module (Ubuntu) Importance: Undecided Status: New ** Summary changed: - glade crash: drawable is not a native X11 window + appmenu-gtk-module makes glade crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805129 Title: appmenu-gtk-module makes glade crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-gtk-module/+bug/1805129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805129] Re: glade crash: drawable is not a native X11 window
The problem seems to be caused by /etc/profile.d/vala-panel-appmenu.sh that sets GTK_MODULES="$GTK_MODULES:appmenu-gtk-module" If one unsets that environment variable, glade works: `GTK_MODULES= glade` That file seems to be shipped by Debian and not by upstream, if Ubuntu doesn't respond we should probably file the bug against Debian > vala- panel-appmenu. ** Also affects: vala-panel-appmenu (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/1805129 Title: glade crash: drawable is not a native X11 window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glade/+bug/1805129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805129] Re: glade crash: drawable is not a native X11 window
Affects me too, on Ubuntu MATE 20.04. Glade on Debian GNOME Bullseye works fine, both with Wayland and Xorg. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805129 Title: glade crash: drawable is not a native X11 window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glade/+bug/1805129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
For those looking for the last good binaries, some notes. Signed (support secure boot), need extraction from the .deb: Good: https://launchpad.net/ubuntu/+source/grub2-signed/1.136/+build/18767810 Bad: https://launchpad.net/ubuntu/+source/grub2-signed/1.137/+build/18827799 Unsigned, but directly downloadable with plain wget: Good: http://archive.ubuntu.com/ubuntu/dists/eoan/main/uefi/grub2-amd64/current/ Bad: http://archive.ubuntu.com/ubuntu/dists/eoan-updates/main/uefi/grub2-amd64/current/ Grub publishing history: https://launchpad.net/ubuntu/+source/grub2-signed/+publishinghistory Everything later than focal 1.137 and eoan 1.128.2 are broken. Main grub launchpad page: https://launchpad.net/ubuntu/+source/grub2-signed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
For secure boot to work, the distribution's grub is needed, as it contains the distribution's signing keys. For now, as a workaround, we're using bionic's grub, for example: https://github.com/alkisg/ltsp5-uefi/blob/master/ltsp5-uefi#L49 Let's hope we hear back from the Ubuntu developers... Would a patch help? It's just about removing this line: https://git.launchpad.net/ubuntu/+source/grub2/tree/debian/patches/ubuntu-linuxefi.patch#n2105 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
> we're using bionic's grub I meant the original one from bionic and not from bionic-updates, because the updated bionic grub is broken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
Around 20 schools so far were affected by this, more will be affected in September. This regression breaks existing installations: 32bit Ubuntu 18.04 in UEFI mode that just run `apt full-upgrade`, and they're no longer able to boot. Could we please have some feedback? Even if it is "don't care; won't fix", we will know that we should solve it locally, e.g. via a PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
This problem is Ubuntu-specific, caused by that line: https://git.launchpad.net/ubuntu/+source/grub2/tree/debian/patches/ubuntu-linuxefi.patch#n2105 That line was added by that commit: https://git.launchpad.net/ubuntu/+source/grub2/commit/?id=6a814c759e10feafb40c3669be30aa51eb5ce39b @cyphermox, this prohibits loading 32bit kernels under UEFI, would it be possible to revert it? For example, before this patch, I was able to boot lubuntu-18.04-desktop-i386.iso under UEFI using https://github.com/alkisg/liveusb; after the patch, I can't. True, the use cases for booting 32bit kernels under UEFI are limited, but is there a reason to have an Ubuntu-specific patch to block it when it works fine? ** Changed in: grub2 (Ubuntu) Importance: Undecided => Low ** Changed in: grub2 (Ubuntu) Status: New => Triaged ** Changed in: grub2 (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876969] Re: 1.55 no irq handler for vector
OK, but please don't assign random packages as their maintainers aren't really the ones that need to help you there. If you don't know which package causes the problem, either leave it in general "ubuntu", or try asking the forums etc. ** Package changed: ltsp (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876969 Title: 1.55 no irq handler for vector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1876969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876969] Re: 1.55 no irq handler for vector
Paul, are you sure you're using LTSP? LTSP is about booting thin clients over the network. What's the output of this command? dpkg -l | grep ltsp ** Changed in: ltsp (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/1876969 Title: 1.55 no irq handler for vector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1876969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
A workaround is to run `rmmod tpm` before `loopback loop some.iso`. See the linked Debian bug for more details. Fedora isn't affected because it doesn't include tpm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: loopback command hangs in 2.04 under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
** Bug watch added: Debian Bug tracker #959425 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959425 ** Also affects: grub2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959425 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/1851311 Title: loopback command hangs in 2.04 under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
Fedora doesn't seem to be affected. From: https://koji.fedoraproject.org/koji/buildinfo?buildID=1499982 Downloaded: https://kojipkgs.fedoraproject.org//packages/grub2/2.04/15.fc33/x86_64/grub2-efi-x64-2.04-15.fc33.x86_64.rpm Extracted: /boot/efi/EFI/fedora/grubx64.efi Tried the command: loopback loop ubuntu.iso And it didn't hang. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: loopback command hangs in 2.04 under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
Debian is affected as well. Downloaded: http://ftp.us.debian.org/debian/pool/main/g/grub2/grub-efi-amd64-bin_2.04-7_amd64.deb Extracted: /usr/lib/grub/x86_64-efi/monolithic/grubx64.efi Tried the command: loopback loop ubuntu.iso And it hangs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: loopback command hangs in 2.04 under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
I started testing binaries from the release history page: https://launchpad.net/ubuntu/+source/grub2-signed/+publishinghistory The last working one is: https://launchpad.net/ubuntu/+source/grub2-signed/1.116 https://launchpad.net/ubuntu/+source/grub2-signed/1.116/+build/17166212/+files/grub-efi-amd64-signed_1.116+2.02+dfsg1-12ubuntu3_amd64.deb The first broken one is: https://launchpad.net/ubuntu/+source/grub2-signed/1.117 https://launchpad.net/ubuntu/+source/grub2-signed/1.117/+build/17277557/+files/grub-efi-amd64-signed_1.117+2.04-1ubuntu1_amd64.deb So indeed 2.02 works and 2.04 doesn't. I will check if the problem affects other distributions as well. ** Summary changed: - Grub 2.04 Out of memory error, No server error + loopback command hangs in 2.04 under UEFI ** Changed in: grub2 (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: loopback command hangs in 2.04 under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818557] Re: Include regexp in grubx64.efi.signed
Ubuntu 20.04 shipped with grub containing regexp. Thank you cjwatson! /me will prepare and upload a new https://github.com/alkisg/liveusb today. :) ** Changed in: grub2-signed (Ubuntu) Importance: Undecided => Wishlist ** Changed in: grub2-signed (Ubuntu) Status: New => Fix Released ** Changed in: grub2-signed (Ubuntu) Assignee: (unassigned) => Colin Watson (cjwatson) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818557 Title: Include regexp in grubx64.efi.signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1818557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867415] Re: Hardlinking snaps wastes 400 MB tmpfs RAM in live CDs
@mvo, I still see the issue in the official 20.04 isos. I boot ubuntu-20.04-desktop-amd64.iso, I run `df -h`, and again I see: Filesystem Size Used Avail Use% Mounted on /cow 2.0G 434M 1.5G 23% / The snapd version in the CD is 2.44.3+20.04, is the fix supposed to be included there? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867415 Title: Hardlinking snaps wastes 400 MB tmpfs RAM in live CDs To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1867415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875129] Re: [SRU] Upgrade to 1.7.3.4 to fix Epoptes regression
1.7.3.4 has landed in Groovy, I tested https://launchpad.net/ubuntu/+archive/primary/+files/socat_1.7.3.4-1_amd64.deb in Focal and it works fine. I also copied it to the Epoptes stable PPA, https://launchpad.net/~epoptes/+archive/ubuntu/ppa/+packages. Btw the regression is in socat, not in Epoptes, it can be reproduced without involving Epoptes at all. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875129 Title: [SRU] Upgrade to 1.7.3.4 to fix Epoptes regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/socat/+bug/1875129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875129] Re: Socat 1.7.3.3 in focal has regression, please sync with sid
** Description changed: - Hi, I reported a socat regression that only appears in version 1.7.3.3: + [Impact] + The socat version in Focal, 1.7.3.3, has a regression that breaks the "remote terminal" functionality of the "epoptes" package. + + I reported it to Debian, and the Debian maintainer packaged the new socat 1.7.3.4 which solves the issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958452 - The Debian maintainer just packaged the new version 1.7.3.4 which solves - the issue. - - Is it possible to get that in Focal? It could be considered a microrelease: + This new upstream version is a bug fixing release which I believe can be considered a microrelease: https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases + Please sync it to focal-proposed. + [Test case] Here are the regression details, in order to be able to reproduce it: - Epoptes is a computer lab management tool, I'm upstream and - Debian maintainer for it. It uses socat to forward a "student" terminal - to the "teacher". To reproduce the issue without installing Epoptes, the - following similar commands may be used instead: + Epoptes is a computer lab management tool, I'm upstream and Debian + maintainer for it. Among other things, it uses socat to forward a + "student" terminal to the "teacher". To reproduce the issue without + installing Epoptes, the following similar commands may be used instead: Teacher (just run it in a terminal tab): xterm -e socat tcp-listen:1234,reuseaddr,keepalive=1 stdio,raw,echo=0 Student (just run it in another terminal tab): TERM=xterm socat EXEC:'screen bash -l',pty,stderr tcp:localhost:1234 This works fine with all socat versions except 1.7.3.3. - In 1.7.3.3, it's like line buffering is enabled or something similar, - and pressing for example the up arrow in the keyboard shows "^[OA" - instead of displaying the last bash command. Thus, the forwarded xterm - is almost unusable. + In 1.7.3.3, it's like line buffering is enabled or something similar, and pressing for example the up arrow in the keyboard shows "^[OA" instead of displaying the last bash command. Thus, the forwarded xterm is almost unusable. + + [Regression potential] + Low. It's a bug fixing upstream release. + I have compiled 1.7.3.4 from source and I've been using it for about a month with no visible issues. I also installed the .deb from sid to my focal box today and it appears to work fine. + Note though that https://tracker.debian.org/pkg/socat shows a unit test failure on arm64 (networkd-test.py), I don't know if that was the case with previous versions or not. ** Summary changed: - Socat 1.7.3.3 in focal has regression, please sync with sid + [SRU] Regression in socat 1.7.3.3, please sync 1.7.3.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875129 Title: [SRU] Regression in socat 1.7.3.3, please sync 1.7.3.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/socat/+bug/1875129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875129] [NEW] Socat 1.7.3.3 in focal has regression, please sync with sid
Public bug reported: Hi, I reported a socat regression that only appears in version 1.7.3.3: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958452 The Debian maintainer just packaged the new version 1.7.3.4 which solves the issue. Is it possible to get that in Focal? It could be considered a microrelease: https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases Here are the regression details, in order to be able to reproduce it: Epoptes is a computer lab management tool, I'm upstream and Debian maintainer for it. It uses socat to forward a "student" terminal to the "teacher". To reproduce the issue without installing Epoptes, the following similar commands may be used instead: Teacher (just run it in a terminal tab): xterm -e socat tcp-listen:1234,reuseaddr,keepalive=1 stdio,raw,echo=0 Student (just run it in another terminal tab): TERM=xterm socat EXEC:'screen bash -l',pty,stderr tcp:localhost:1234 This works fine with all socat versions except 1.7.3.3. In 1.7.3.3, it's like line buffering is enabled or something similar, and pressing for example the up arrow in the keyboard shows "^[OA" instead of displaying the last bash command. Thus, the forwarded xterm is almost unusable. ** Affects: socat (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/1875129 Title: Socat 1.7.3.3 in focal has regression, please sync with sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/socat/+bug/1875129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
Thank you seb128! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855594] Re: Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main)
Thank you for resolving this. I would like to mention that there are other browsers/snaps in Universe that are just synced from Debian, without any policy about preventing them from reaching Ubuntu, and that this decision will probably move users to Google Chrome rather than snaps, but ...alea iacta est. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855594 Title: Sync chromium 78.0.3904.108-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium/+bug/1855594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
Anydesk too. Thanks for the fix! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
Hi all, final freeze is approaching, and I don't see anyone syncing Andrej's new version from Debian... Maybe it would be easier to just accept my patch, to have this solved for 20.04, and do the syncing for 20.10? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
** Description changed: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu + + To reproduce this: + + Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: + - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf + - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. + + With these, the problem happens in around 10% of the cases. + To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: + - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf + - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. + - systemctl stop network-manager + - killall wpa_supplicant + - systemctl start network-manager + + Then insert a USB wifi adapter that results in a big name with 15 + characters like wlx74ee2ae2436a and try to connect to a wifi network. I + will keep asking for a password. + + Then apply the patch, run the 3 commands above to restart network- + manager, and verify that it can now connect properly. ** Description changed: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 - characters like wlx74ee2ae2436a and try to connect to a wifi network. I + characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1867908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
