This is upstream [commit
79d341e26ebc](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=79d341e26ebcdbc622348b6f8f89b6fdb25f).
Thank you for upstreaming it.
It’d be great, if you also documented the measurements. Do you still
have them, and can add them here as a
My bad, actually looking on the device, *brltty* was installed for a
long time. :-(
/var/log/dpkg.log.12.gz:2020-06-24 18:24:40 upgrade brltty:amd64
5.6-11ubuntu2 6.0+dfsg-4ubuntu6
Sorry about the confusion. It looks like the user tested this exact USB
serial converter (0403:6001) the first
apport information
** Attachment added: "VarLogDistupgradeScreenlog.txt"
https://bugs.launchpad.net/bugs/1976293/+attachment/5594312/+files/VarLogDistupgradeScreenlog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "VarLogDistupgradeApttermlog.txt"
https://bugs.launchpad.net/bugs/1976293/+attachment/5594309/+files/VarLogDistupgradeApttermlog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "VarLogDistupgradeMainlog.txt"
https://bugs.launchpad.net/bugs/1976293/+attachment/5594311/+files/VarLogDistupgradeMainlog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "VarLogDistupgradeLspcitxt.txt"
https://bugs.launchpad.net/bugs/1976293/+attachment/5594310/+files/VarLogDistupgradeLspcitxt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "VarLogDistupgradeAptclonesystemstate.tar.gz"
https://bugs.launchpad.net/bugs/1976293/+attachment/5594307/+files/VarLogDistupgradeAptclonesystemstate.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "VarLogDistupgradeAptlog.txt"
https://bugs.launchpad.net/bugs/1976293/+attachment/5594308/+files/VarLogDistupgradeAptlog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1976293/+attachment/5594305/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976293
apport information
** Attachment added: "VarLogDistupgradeAptHistorylog.txt"
https://bugs.launchpad.net/bugs/1976293/+attachment/5594306/+files/VarLogDistupgradeAptHistorylog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1976293/+attachment/5594303/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1976293/+attachment/5594304/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected dist-upgrade jammy wayland-session
** Description changed:
On a default Ubuntu desktop installation (with GNOME) doing `do-release-
upgrade` from 21.10 to 22.04 installed *brltty* breaking FTDI USB serial
devices.
```
[
1. This is Debian bug report #667616.
2. *brltty* was installed when doing `do-release-upgrade` from 21.10 to 22.04
[2].
[1]: https://bugs.debian.org/667616
[2]:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293
** Bug watch added: Debian Bug tracker #667616
Public bug reported:
On a default Ubuntu desktop installation (with GNOME) doing `do-release-
upgrade` from 21.10 to 22.04 installed *brltty* breaking FTDI USB serial
devices.
```
[ 2435.150025] usb 1-2: new full-speed USB device number 6 using xhci_hcd
[ 2435.305646] usb 1-2: New USB device
Thank you all for your help.
$ apt-cache policy qemu gcc-powerpc64-linux-gnu
qemu:
Installed: (none)
Candidate: 1:6.0+dfsg-2expubuntu1.1
Version table:
1:6.0+dfsg-2expubuntu1.1 500
500 http://de.ports.ubuntu.com/ubuntu-ports impish-updates/universe
Public bug reported:
On Ubuntu 21.10 (ppc64le) trying to install QEMU’s build dependencies
fails with:
```
$ sudo apt build-dep qemu-system-ppc
Reading package lists... Done
Picking 'qemu' as source package instead of 'qemu-system-ppc'
Reading package lists... Done
Building dependency tree...
The system was updated from Ubuntu 20.04 to 21.10, but it’s still not
working out of the box without the script `a2dp.py`.
I am not able to work more on the issue, as I do not have the
environment, but maybe Canonical and Google should work more closely
together on the QA side.
--
You received
I read at [1] about the issue.
@kaihengfeng, I suggest to send the patch upstream for review even with
no tests. Maybe there will be testers on the Linux kernel mailing list.
[1]: https://etbe.coker.com.au/2022/01/09/video-conferencing-lca/
--
You received this bug notification because you are
Yes, thank you for assigning the right component.
Personally, for desktops, I would always recommend the latest release. I
think a lot of users do not know the difference, and just click the
green button.
> We also have the latest BlueZ in Ubuntu already.
Do you mean 21.10, which has
I understand, that bugs are probably fixed in newer versions.
https://ubuntu.com/#download still offers Ubuntu 20.04 for desktops, and
even highlighted green. So what functionality can users expect?
Anyway, I just wanted to report it, and, as it is not my device, I am
also unable to debug more.
** Attachment added: "a2dp.py fixing the problem"
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1956147/+attachment/5550575/+files/a2dp-0.6.2.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is not my system, so I cannot debug a lot.
Linux kernel 5.4.x is used, and Linux logs hci related messages, and
bluetoothd also segfaults. (Ubuntu noticed the crash, and should have
uploaded the resulting dumps.)
What fixed it was using `a2dp.py`:
```
$ curl
Public bug reported:
Connect a Google Nest to a ASUS laptop running Ubuntu 20.04, the devices
pair, and *Office Speaker* shows up as an output device in the *Sound*
settings, but no sound is heard (also doing the speaker test).
In Debian sid/unstable with GNOME Shell 41.2 and *gnome-bluetooth*
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1279
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1279
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1279
Importance: Unknown
Status: Unknown
--
You received this
Under *Tools* → *Options* → *View*, what theme do you have selected?
Even with *Elementary (SVG)* I get blurry icons with *libreoffice*
7.2.1-3 from Debian sid/unstable.
I reported the issue [upstream][1].
[1]: https://bugs.documentfoundation.org/show_bug.cgi?id=144583
** Bug watch added:
The article *Firefox 90 on POWER (and a JIT progress report)* [1]
summarizes the issue in NSS. It’s upstream bug report 1566124 [2], and
there are two simple patches to be applied to NSS 3.66.
Starting Firefox with `NSS_DISABLE_PPC_GHASH=1` works around the issue.
[1]:
** Bug watch added: Mozilla Bugzilla #1566124
https://bugzilla.mozilla.org/show_bug.cgi?id=1566124
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937245
Title:
ppc64le: Fails to load HTTPS pages
Public bug reported:
Firefox 90.0+build1-0ubuntu0.21.04.1 fails to load HTTPS URLs with the
error:
> Secure Connection Failed
>
> An error occurred during a connection to blog.fefe.de. The client has
> encountered bad data from the server.
>
> Error code: SSL_ERROR_BAD_SERVER
>
> * The page
I am also seeing this on a the AMD Ryzen desktop system Dell OptiPlex
5055 with Linux 5.13-rc7.
[0.00] DMI: Dell Inc. OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.25
05/03/2021
[…]
[ 12.810715] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control
method not found
[
** Package changed: procps (Ubuntu) => linux-meta-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931630
Title:
Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ`
cause
In #ubuntu-ser...@irc.libera.chat I was told to move this issue to
*linux-image-kvm*. How can I do that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931630
Title:
Linux images for virtual
Public bug reported:
*procps* ships `/etc/sysctl.d/10-magic-sysrq.conf:kernel.sysrq = 176`,
which is run by `systemd-sysctl.service`. This fails on a system run
with a Linux image built for virtual machines *linux-image-kvm*, which
has `CONFIG_MAGIC_SYSRQ` not set.
```
$ sudo
Public bug reported:
With `/bin/sh` being dash and not Bash, the postinst script fails.
```
$ sudo apt reinstall nis
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need
Rico is right. I only had the entry below. No idea, if I only added the
line below several versions ago or some upgrade changed it. (Probably
the former.)
deb http://de.ports.ubuntu.com groovy-proposed main restricted
Following https://wiki.ubuntu.com/Testing/EnableProposed I added
Public bug reported:
Among other, package *libreoffice* 7.0.5-0ubunt0.20.10.1 is missing in
the *groovy-proposed* archives.
```
$ more /etc/os-release
NAME="Ubuntu"
VERSION="20.10 (Groovy Gorilla)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.10"
VERSION_ID="20.10"
Please create a separate bug report, as the error type is different from
the original report here. Also, in the new report (best upstream), give
more information (firmware version, extension cards, …), and also
*attach* (not paste) the output of `lspci -tvnn` and `sudo lspci
-vvxxx`.
--
You
For every one affected, at least attach the output of `lspci -nn`,
`dmesg`, and give details for your system.
As this bug has gotten long, and causes go from firmware, firmware
configuration to hardware issues, it’s better if you opened a separate
report directly upstream, after testing the
Public bug reported:
On ppc64le and Ubuntu 20.10 with *evolution-data-server* 3.38.1-1, the
logs contain, when starting an Xfce session over X2Go.
[98982.444956] systemd-xdg-autostart-generator[297820]: Exec binary
'/usr/libexec/evolution-data-server/evolution-alarm-notify' does not exist:
Public bug reported:
Upgrading GRUB on a ppc64le machine (8335-GCA (IBM Power System S822LC))
2021-03-15 08:20:23 upgrade grub-common:ppc64el 2.04-1ubuntu26.8
2.04-1ubuntu26.11
`grub-initrd-fallback.service` failed to restart.
```
$ sudo journalctl -xe
[…]
Mar 15 08:20:30 s822lc
** Attachment added: "Output of `strace -ff prep-bootdev -l`"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915007/+attachment/5461237/+files/strace-prep-bootdev-l.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Doing `apt upgrade`
2021-02-08 10:41:20 upgrade grub-ieee1275:ppc64el 2.04-1ubuntu26
2.04-1ubuntu26.8
the postinst hangs:
```
root 236284 0.0 0.0 18304 9536 ?S09:59 0:00 sudo apt
full-upgrade
root 236285 0.0 0.0 77376 64256 ?S
I create upstream issue https://github.com/intel/Intel-Linux-Processor-
Microcode-Data-Files/issues/35.
** Bug watch added:
github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues #35
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/35
--
You received
Public bug reported:
Ubuntu announces the 20.10 release, despite it running already. Probably
related to some poor integration of *oem-release* (purged) or *oem-
config* .
```
user@helmut-XPS-13-9310:~$ ssh helmut@192.168.0.3
Welcome to Ubuntu 20.10 (GNU/Linux 5.10.0-rc1+ x86_64)
*
Public bug reported:
On a Dell XPS 13 9310 with shipped Dell Ubuntu 20.04.1, after allowing
release upgrades, and running `sudo do-release-upgrade` and upgrading to
20.10, looking at `/etc/os-release` still showed 20.04, as it was
redirected to `/usr/lib/os-release.oem`.
The integration really
Public bug reported:
With (Dell) Ubuntu 20.04.1 on a Dell XPS 13 9310, after allowing release
upgrades, the process crashed the first time.
```
$ sudo do-release-upgrade
Neue Veröffentlichungen von Ubuntu werden gesucht
Holen:1 Signatur der Aktualisierungsanwendung [819 B]
The output of `ubuntu-bug` is attached, and contains everything that’s
needed as far as I can see.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897745
Title:
Surface Pro 4 with Linux 5.4.x: WPA:
Public bug reported:
On the Surface Pro 4 with USB Marvell Bluetooth/WLAN device, upgrading
from Ubuntu 18.04 with Linux 4.15.x to Ubuntu 20.04 with Linux 5.4.x,
only WPA2 Enterprise networks stop working, but other continue to work.
WPA: Failed to set GTK to the driver (alg=2 keylen=32
>From the manual page capabilities(7):
CAP_SYS_NICE
* Lower the process nice value (nice(2), setpriority(2)) and
change the nice value for arbitrary processes;
* set real-time scheduling policies for calling process, and set
*** This bug is a duplicate of bug 1872564 ***
https://bugs.launchpad.net/bugs/1872564
The original report contains two issues, where only the second one is
fixed in
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564.
For the first audit messages for `cups-browsed`
[
Public bug reported:
In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents
`/usr/sbin/cups-browsed` to change its nice value.
$ sudo dmesg | grep apparmor
[541870.509461] audit: type=1400 audit(1600898428.089:60):
apparmor="DENIED" operation="capable"
@skliarie, your pasted log message is actually a different issue, and I
just reported
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369 for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Am 18.09.20 um 13:55 schrieb Mirek Ingr:
> Okay, please find the attached journal.
Thank you. There it is:
Sep 18 08:15:43 B4 kernel: DMI: Dell Inc. Latitude 5591/0DVVG1,
BIOS 1.13.1 07/14/2020
Sep 18 08:15:43 B4 kernel: microcode: sig=0x906ea, pf=0x20,
revision=0xd6
So, it is the
Am 18.09.20 um 09:40 schrieb Mirek Ingr:
> Sure thing, here you are:
> $ grep -i microcode /proc/cpuinfo
> microcode : 0xd6
> microcode : 0xd6
> microcode : 0xd6
> microcode : 0xd6
> microcode : 0xd6
> microcode : 0xd6
> microcode : 0xd6
> microcode : 0xd6
>
Am 18.09.20 um 09:13 schrieb Mirek Ingr:
> $ dmesg | grep microcode
>
Please attach the whole output.
> $ iucode-tool -Sv
> iucode-tool: system has processor(s) with signature 0x000906ea
> iucode-tool: assuming all processors have the same type, family and model
>
>
> $ lscpu
> Architecture:
@mirek-ingr, can you please attach the output of `dmesg` when running
the updated firmware?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882943
Title:
Dell Latitude 5591, i7-8850H,
It looks like microcode update revision 0xd6 is still the officially
shipped version.
The often occurring hangs without the power cable plugged in, are still
happening.
Booting with `maxcpus=1` and adding
earlyprintk=efi earlycon=efifb debug
to the Linux command, the last messages are:
Shouldn’t the metadata (Conflicts, Replaces, …) reflect that, so apt can
find an upgrade path?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887959
Title:
Unable to upgrade several qt5 packages
Thank you for the quick response.
Yes, with that apt seems to be able to resolve the conflicts.
```
$ sudo apt install libqt5core5a
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libqt5dbus5
Public bug reported:
After upgrading from Ubuntu 19.10 (maybe 18.04) to 20.04, I am unable to
upgrade the packages below.
The following packages have been kept back:
libboost-date-time-dev libboost-dev libboost-filesystem-dev libqt5core5a
libqt5dbus5 libqt5gui5 libqt5network5
```
$ apt list --upgradable
Listing... Done
libboost-date-time-dev/focal 1.71.0.0ubuntu2 ppc64el [upgradable from: 1.67.0.2]
libboost-dev/focal 1.71.0.0ubuntu2 ppc64el [upgradable from: 1.67.0.2]
libboost-filesystem-dev/focal 1.71.0.0ubuntu2 ppc64el [upgradable from:
1.67.0.2]
libqt5core5a/focal
Is this still a problem with *xserver-xorg-input-libinput*, which
replaces *xserver-xorg-input-evdev*?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/313514
Title:
MASTER: evdev driver ignores
*** This bug is a duplicate of bug 313514 ***
https://bugs.launchpad.net/bugs/313514
If this still an issue, please check with the libinput tools.
sudo libinput debug-events
I got the currency keys working on the Acer TravelMate 5735Z [1].
[1]:
PS: The Linux command line parameter `dis_ucode_ldr` can be used to
disable applying microcode updates [1].
[1]: https://lkml.org/lkml/2020/6/11/651
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Trying to find out, if bug #1883065 [1] is a duplicate of this one.
Is this a laptop? If yes, does having the power cable plugged in make a
difference?
Starting with `maxcpus=1` and then trying to bring more CPUs online, on
the Dell Precision 3540 with dedicated AMD graphics card, it always
[0.00] microcode: microcode updated early to revision 0xd6,
date = 2020-04-23
The system was given to a user, so I won’t be able to test.
Maybe this bug is about two issues.
1. Sometimes boot failures (cold boot and from hibernate) with no power cable
plugged in. (Yesteday, I wasn’t
It might be related to the latest microcode updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883065
Title:
Dell Latitude/Precision: Linux hangs without plugged in power cable
To manage
Public bug reported:
Already present reported in project *dell-sputnik*. (Note, it happened
here also without suspend/resume.):
1. https://bugs.launchpad.net/dell-sputnik/+bug/1661741
2. Quote from https://bugs.launchpad.net/dell-sputnik/+bug/1661741/comments/26:
> A similar bug affects
Here are the Linux messages.
** Attachment added: "Linux messages with `acpi=off debug` on the Linux command
line"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883019/+attachment/5382802/+files/morley-acpi-off.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
Public bug reported:
With Ubuntu 20.04 (and 18.04) Starting the Dell Precision with
`acpi=off` (to debug power cable issue) powering of the system, it halts
but does not power off.
[1]: https://bugs.launchpad.net/bugs/1661741
[2]: https://bugs.launchpad.net/dell-sputnik/+bug/1871491
** Affects:
@piscvau, the original report is not about a crash, so your issue is
unrelated. Please create a separate report for the crash Ubuntu 20.04.
(Also mention there, if it is a system crash/hang? Does the numlock key
still work? Can you switch to a virtual console with Ctrl + Alt + F4?
Can you still
This is a common problem on AMD Zen systems.
Patches were posted to LKML (Linux Kernel Mailing List) in February
2019, but version 2 still needs to rewrite a comment, and v3 wasn’t
posted since then.
[1]: https://lkml.org/lkml/2019/2/14/1145
--
You received this bug notification because you
Just a note, on the Dell OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.20
05/31/2019 (AGESA SummitPI-AM4 1.0.0.7a) I am only seeing the interrupt
warning. Performance counters are supported there.
[0.870894] pci :00:00.2: AMD-Vi: IOMMU performance counters
supported
[0.871377] pci
I am also seeing this with current Linux (5.7-rc7) on an MSI B350M
MORTAR and a Dell OptiPlex 5055. Both are AMD Ryzen systems, so this
seems to affect all of those.
The IOMMU subsystem maintainer responded to report this issue to the
mainboard vendor, so they fix the firmware [1].
Everybody
It’d be great if Canonical also used their Dell and AMD contacts to get
this fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804589
Title:
AMD-Vi write error
To manage notifications about
Public bug reported:
The update from Ubuntu 19.04 to 19.10 *and* 19.10 to 20.04 failed with
the message (for 20.04 upgrade) below.
[…]
Unpacking autofs (5.1.6-2) over (5.1.5-1ubuntu1) ...
dpkg-deb: error: failed to read archive
@magean, I believe you are having a different issue here, so please
create a separate bug report, and, as you reproduced this with Linux 5.4
(also try https://kernel.ubuntu.com/~kernel-ppa/), contact linux-
p...@vger.kernel.org and the PCI subsystem maintainers directly, and
attach `dmesg` to your
@ads-launchpad, that looks like a separate issue. Please make a new
report (especially as this is in the project(?)/category(?) *dell-
sputnik* in Launchpad, and also upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Sorry, I wasn’t subscribed to the notifications.]
@hui.wang, your attached firmware, what version is that?
$ md5sum sof-icl.ri
2ca373e6254b0e9b37439f7a31984973 /dev/shm/sof-icl.ri
@adamfubuntu, do you still have the problem *without* `dsp_driver=0` on
an up-to-date Ubuntu 19.10 with
And in Clear Linux: https://community.clearlinux.org/t/new-installation-
no-sound-swift-5-i7-1065gt-iris-plus/2407/14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856366
Title:
PCI/internal sound
A Fedora user reported the same issue in
https://bugzilla.redhat.com/show_bug.cgi?id=1772498#c16, and the created
an upstream GitHub issue
https://github.com/thesofproject/sof/issues/2126.
Please update the meta-information of this bug accordingly.
--
You received this bug notification because
This is still an issue, and due to HiDPI getting more and more common,
Ubuntu should really look into this to give users a good experience with
the setups.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can this be closed/tagged as fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488620
Title:
Add LZ4 support to initramfs-tools
To manage notifications about this bug go to:
Off-topic: Adam, you should also install the other firmware files like
for graphics.
```
[1.029518] i915 :00:02.0: vgaarb: changed VGA decodes:
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[1.029567] i915 :00:02.0: Direct firmware load for
i915/icl_dmc_ver1_09.bin failed with
It should work out of the box without the user having to specify any
options.
1. There does not seem to be an Ubuntu package for Sound Open Firmware
yet. Adam, does the pre-built firmware file from
https://github.com/thesofproject/sof/releases work? Linux 5.3, 5.4,
5.5-rc1?
2. With the
Upstream issue: https://github.com/OpenPrinting/cups-filters/issues/162
** Bug watch added: github.com/OpenPrinting/cups-filters/issues #162
https://github.com/OpenPrinting/cups-filters/issues/162
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The same issues exists with cups-filters 1.25.6 in Debian Sid/unstable.
>From `/var/log/cups/error_log`:
```
D [01/Oct/2019:11:15:54 +0200] [Job 168] Removing cups-browsed-dest-printer
option from argumentsmalloc.c:2389: sysmalloc: Assertion `(old_top ==
initial_top (av) && old_size == 0) ||
@andre-miras, we do not experience the problem with Ubuntu 18.10(?) and
19.04 anymore. Please try to update, or test these releases. No idea,
what the cause and solution was in the end.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tested this yesterday with Ubuntu 18.10, and Firefox did crash
anymore. So this can be tagged as solved. I do not know the first fixed
version though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On a ppc64le system I verified, that the version in cosmic-proposed
fixes this issue.
A big thanks to everyone, fixing this so quickly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818121
Title:
It worked with bionic-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818121
Title:
NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no
hosts available
To manage
On 25.03.19 07:53, Christian Ehrhardt wrote:
> @Paul - you were so active before - thanks for checking the PPAs and
> all that. But I still have no NFS server uncoorperative enough to
> trigger this; Could you for the (final) SRU verification as asked on
> the comments #18 and #19 confirm that
I checked, that your packages fix the problem on both Bionic and Cosmic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818121
Title:
NFSv4 shares with option `-vers=4.0` are not mounted:
@Paul - please test the PPA on Disco (19.04) [1] and let me know if it
works fine.
I just tested this. With autofs 5.1.2-4ubuntu1 it does *not* work, with
autofs 5.1.2-4ubuntu2~ppa1 it does work.
[1]: https://launchpad.net/~paelzer/+archive/ubuntu/bug-1818121-autofs-
nfs4.x
--
You received
Ubuntu Disco is 19.04, right? I’ll try to test this properly today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818121
Title:
NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no
Our NFS server is not a Ubuntu system. It’s basically an LFS based set-
up [1]. The autofs client installed on our system has no trouble
connecting to the server, so some minor detail seems to be different,
that it doesn’t work with the Ubuntu client out of the box.
[1]:
Our NFS server does not advertise/support NFSv3 for example.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818121
Title:
NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no
Thank you for trying to reproduce the issue, and sorry for missing out
information. In this case, due to NFS 4.2 issues, we have specified the
exact NFS version.
joey -vers=4.0 claptrap:/amd/claptrap/2/home/edv/joey
Bisecting the fix in autofs 5.1.4, results in the commit aa1f4321
** Summary changed:
- NFSv4 shares are not mounted: mount(nfs): no hosts available
+ NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts
available
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
With Ubuntu 18.10 and autofs 5.1.2-4ubuntu1, mounting NFSv4 shares does
not work. Directly mounting them with `mount.nfs` works.
```
Feb 28 18:08:30 nfsclient automount[22978]: expire_proc: exp_proc =
131147807650128 path /home_mariux
Feb 28 18:08:30 nfsclient
1 - 100 of 180 matches
Mail list logo
