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
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
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.
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
*** 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,
** 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
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"
** 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:
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)
** 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
** 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
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,
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
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
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
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
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
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
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
** 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.
+
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
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
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:
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
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.
*** 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
*** 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
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,
@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,
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:
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
** 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:
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
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.
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.
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
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.
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
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.
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.
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.
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
@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
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)
--
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
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).
+
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:
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.
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
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:
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
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
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]
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
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
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
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
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
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)
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:
*** 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
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,
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
> 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
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,
> 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
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
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
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
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
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.
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.
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.
> 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
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
** 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
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
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
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
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...
> 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:
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;
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,
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:
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
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.
** 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
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
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
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
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
@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
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
** 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
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
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:
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
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:
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,
** 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,
1 - 100 of 1390 matches
Mail list logo
