from:"markus"

** Attachment added: "whoopsie file for incident added"
   
https://bugs.launchpad.net/ubuntu/+source/libusb-1.0/+bug/1973091/+attachment/5588779/+files/_usr_bin_ink.1000.crash

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973091

Title:
  Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libusb-1.0/+bug/1973091/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973091] Re: Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink

** Tags added: jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973091

Title:
  Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libusb-1.0/+bug/1973091/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973091] Re: Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink

To my knowledge this issue is not related to the Linux kernel, but to
the libusb-1.0-0 package.

** Changed in: libusb-1.0 (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973091

Title:
  Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libusb-1.0/+bug/1973091/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973091] Re: Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink

** Package changed: linux (Ubuntu) => libusb-1.0 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973091

Title:
  Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libusb-1.0/+bug/1973091/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973091] [NEW] Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink

Public bug reported:

The following packages are installed:

1. libusb-1.0-0/jammy,now 2:1.0.25-1ubuntu1 amd64
2. libinklevel5/jammy,now 0.9.3-3 amd64
3. ink/jammy,now 0.5.3-3 amd64

Command invoked is:

ink -p usb

Result is a segmentation fault. Backtrace in gdb:

gdb) bt
#0  0x77dfcf74 in pthread_mutex_lock () from 
/lib/x86_64-linux-gnu/libc.so.6
#1  0x77d52879 in libusb_get_device_list () from 
/lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x77f96c90 in find_printer () from 
/lib/x86_64-linux-gnu/libinklevel.so.5
#3  0x77f963e5 in get_device_id () from 
/lib/x86_64-linux-gnu/libinklevel.so.5
#4  0x77f90d55 in get_ink_level () from 
/lib/x86_64-linux-gnu/libinklevel.so.5
#5  0x554e in ?? ()
#6  0x77d8ed90 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x77d8ee40 in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
#8  0x5795 in ?? ()

I have compiled libusb-1.0.26 into my $HOME and pointed LD_LIBRARY_PATH
to it. Then I get the expected result:

ink -p usb
ink 0.5.3 (c) 2018 Markus Heinz

hp deskjet 5550

Black:   0%
Color:   0%

ldd /usr/bin/ink 
linux-vdso.so.1 (0x7ffe6e47b000)
libinklevel.so.5 => /lib/x86_64-linux-gnu/libinklevel.so.5 
(0x7f479dd44000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f479db1c000)
libusb-1.0.so.0 => 
/home/markus/privat/programmieren/c/printer/libusb-dist/libusb-1.0.26/libusb/.libs/libusb-1.0.so.0
 (0x7f479dafc000)
/lib64/ld-linux-x86-64.so.2 (0x7f479dd79000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f479dad2000)

So I have the assumption that there is a regression in libusb-1.0.25
which has been fixed in libusb-1.0.26.

On Ubuntu 20.04 there was no problem with libusb and libinklevel / ink.
It just appeared after the update to Ubuntu 22.04 which I did today.

** Affects: linux (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/1973091

Title:
  Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973091/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971168]

2022-05-11 Thread Markus W

(In reply to Al Savage from comment #6)
> [...] it may not be limited to FF, snaps, or even Mozilla, since my Chrome 
> install behaves similarly.

You are right, this is actually affecting other applications, too. I get
the exact same behavior described in the steps to reproduce when using
Chromium installed via snap: Local files open fine, opening files on
network shares does not trigger any reaction.

Should this issue here remain open?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971168

Title:
  [snap] Files on local network shares are not opened / written

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971168] Re: [snap] Downloaded files not saved when saving to local network share

2022-05-09 Thread Markus W

I've updated the bug to reflect that multiple applications are affected
by this. On my system I can reproduce the issue with Firefox and
Chromium, both installed via snap.

** Also affects: snapd (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  Steps to reproduce:
  
- 1. Run Firefox as a Snap package in Ubuntu 22.04
+ 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
- 4. Open any website containing images in Firefox
+ 4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share
  
  Actual behavior:
  
  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown
  
  Expected behavior:
  
  * File is saved to selected network share location
  * No error is shown
  
  Additional information:
  
  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
+ * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

** Summary changed:

- [snap] Downloaded files not saved when saving to local network share
+ [snap] Files on local network shares are not opened / written

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971168

Title:
  [snap] Files on local network shares are not opened / written

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971967] [NEW] TestInotifyOverflow test fails on newer host systems

2022-05-06 Thread Markus Ueberall

Public bug reported:

The included TestInotifyOverflow test unexpectedly fails on newer host
systems if the host system's fs.inotify.max_queued_events is greater
than 128*1024:

[2022-05-06T11:15:11+0200] 
ubuntu@pbuilder-amd64:/var/cache/pbuilder/tmp/podman_buildah_skopeo% grep FAIL 
golang-fsnotify_151-2_all.log__REDO
--- FAIL: TestInotifyOverflow (0.91s)
FAIL
FAILgithub.com/fsnotify/fsnotify9.762s
FAIL

[2022-05-06T11:18:18+0200] root@desktop01:~# sysctl fs.inotify.max_queued_events
fs.inotify.max_queued_events = 1048576

In order to rebuild the package, it's necessary to temporarily modify
said system value (e.g., using "sysctl -w
fs.inotify.max_queued_events=16384"), which is rather cumbersome -- cf.
https://www.mail-archive.com/pkg-go-maintainers@alioth-
lists.debian.net/msg04669.html

It would be best to remove the above test (or maybe keep it but replace
the threshold with an absurdly high number?)


[2022-05-06T11:18:25+0200] root@desktop01:~# lsb_release -rd
Description:Ubuntu 20.04.4 LTS
Release:20.04

[2022-05-06T11:25:45+0200] 
ubuntu@pbuilder-amd64:/var/cache/pbuilder/tmp/podman_buildah_skopeo% _hgrep 
dget | grep fsnotify
 9911  [2022-05-06T11:06:06+0200]  dget 
http://archive.ubuntu.com/ubuntu/pool/universe/g/golang-fsnotify/golang-fsnotify_1.5.1-1.dsc
[2022-05-06T11:25:53+0200] 
ubuntu@pbuilder-amd64:/var/cache/pbuilder/tmp/podman_buildah_skopeo% ll 
original/*fsnotify*
-rw-rw-r-- 1 ubuntu ubuntu  3588 2022-05-06 10:05:47 
original/golang-fsnotify_1.5.1-1.debian.tar.xz
-rw-rw-r-- 1 ubuntu ubuntu  2228 2022-05-06 10:05:46 
original/golang-fsnotify_1.5.1-1.dsc
-rw-rw-r-- 1 ubuntu ubuntu 32691 2022-05-06 10:05:46 
original/golang-fsnotify_1.5.1.orig.tar.gz


** Affects: golang-fsnotify (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/1971967

Title:
  TestInotifyOverflow test fails on newer host systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-fsnotify/+bug/1971967/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971168] Re: [snap] Downloaded files not saved when saving to local network share

2022-05-05 Thread Markus W

Corresponding bug in Mozilla bugtracker:
https://bugzilla.mozilla.org/show_bug.cgi?id=1767316

** Bug watch added: Mozilla Bugzilla #1767316
   https://bugzilla.mozilla.org/show_bug.cgi?id=1767316

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971168

Title:
  [snap] Downloaded files not saved when saving to local network share

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971168/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971191] Re: No Ubuntu Desktop option in tasksel, in Ubuntu Server 22.04

2022-05-03 Thread Markus Szillat

Same issue. I chose one of the Gnome options and my desktop now appears
to be Debian?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971191

Title:
  No Ubuntu Desktop option in tasksel, in Ubuntu Server 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tasksel/+bug/1971191/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971168] Re: [snap] Downloaded files not saved when saving to local network share

2022-05-02 Thread Markus W

** Description changed:

  Steps to reproduce:
  
  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share
  
  Actual behavior:
  
  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown
  
  Expected behavior:
  
  * File is saved to selected network share location
  * No error is shown
  
  Additional information:
  
- * When saving to a folder on the local machine instead, saving works
- correctly as expected.
+ * When saving to a folder on the local machine instead, saving works 
correctly as expected
+ * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971168

Title:
  [snap] Downloaded files not saved when saving to local network share

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971168/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971168] [NEW] [snap] Downloaded files not saved when saving to local network share

2022-05-02 Thread Markus W

Public bug reported:

Steps to reproduce:

1. Run Firefox as a Snap package in Ubuntu 22.04
2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
3. Have one such share mounted and writable
4. Open any website containing images in Firefox
5. Right-click on an image and select "Save Image As..."
6. In the file save dialog, navigate to the mounted share
7. Assert content of network share is visible and browsable from within the 
save dialog
8. Select "Save" at any folder in the network share

Actual behavior:

* File is not saved to selected network share location
* No download entry is created
* No error is shown

Expected behavior:

* File is saved to selected network share location
* No error is shown

Additional information:

* When saving to a folder on the local machine instead, saving works correctly 
as expected
* In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share

** Affects: firefox (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: snap

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971168

Title:
  [snap] Downloaded files not saved when saving to local network share

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971168/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

2022-04-23 Thread Markus Kuhn

It may also be worth noting that Kerberos/GSSAPI authentication for NFS
works a bit differently from Kerberos/GSSAPI authentication for
applications, because NFS happens in the kernel, and therefore the
kernel needs to get access to the Kerberos tickets (credentials). The
kernel's NFS client does so via a helper process called rpc.gssd, which
is usually started at boot time as a daemon by systemd, then listens on
/run/rpc_pipefs for kernel requests (upcalls) to authenticate an NFS
RPCSEC_GSS session via Kerberos, and then does execure the Kerberos
protocol in user space, and passes the resulting session key back to the
RPCSEC_GSS code in the kernel, which then uses it to cryptographically
protect the NFS RPC requests that go over the network. While doing this,
the rpc.gssd process takes on the effective UID of the user application
that made the NFS file/IO request, and as such reads the Kerberos
ticket, traditionally from the user's credential cache at
/tmp/krb5cc_$UID or (depending on the value of $KRB5CCNAME) from some
other credential cache, e.g. the kernel keyring.

So the question is: if rpc.gssd does take over the control flow, UID,
and environment variables of an NFS I/O request made by a snap
application, does it effectively run, from AppArmor's point of view, as
the snap application that tried to access a file via Kerberized NFS?
Does then the AppArmor profile of the snap application therefore also
apply to rpc.gssd and therefore have to enable it to read the Kerberos
ticket, such that rpc.gssd can inherit that right as well?

If you run AppArmor in complaint mode rather than enforce mode, does it report 
in the log that it would have prevented rpc.gssd from doing its thing (reading 
the ticket, using the network, etc.)
?

KRB5CCNAME syntax:
https://web.mit.edu/kerberos/krb5-1.17/doc/basic/ccache_def.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784774

Title:
  snapd is not autofs aware and fails with nfs home dir

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1784774/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968258] Re: Data corruption in qemu_rbd_co_block_status

2022-04-12 Thread Markus Schade

Hi Christian,

thanks you very much for getting this out of the door so fast!
I can confirm that new version with the patches resolves the issues.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968258

Title:
  Data corruption in qemu_rbd_co_block_status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1968258/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968258] [NEW] Data corruption in qemu_rbd_co_block_status

2022-04-08 Thread Markus Schade

Public bug reported:

Hi Christian,

we have started testing jammy and triggered a qemu bug which has already
been fixed upstream.

The qemu 6.2 in jammy has currently a buggy implementation of 
.bdrv_co_block_status in block/rbd.
This can result in data corruption and/or crash of the instance.

https://tracker.ceph.com/issues/53784

Please consider backporting the following patches into qemu jammy before
the release:

https://git.qemu.org/?p=qemu.git;a=patch;h=9e302f64bb407a9bb097b626da97228c2654cfee
https://git.qemu.org/?p=qemu.git;a=patch;h=fc176116cdea816ceb8dd969080b2b95f58edbc0

A repoducer is in the Ceph tracker. Trying to create a qcow2 snapshot
from a running rbd-backed  virtual machine will lead to a crash of the
virtual machine, e.g.

# virsh snapshot-create-as --domain vm-123 --no-metadata --disk-only
--diskspec sda,file=/var/lib/libvirt/qemu/snapshot/disk-123.qcow2

Resulting core dump:

#0  0x7fbaee61f18b in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fbaee5fe859 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x7fbaee5fe729 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x7fbaee60ff36 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
#4  0x7fbaed64663f in qemu_rbd_co_block_status (bs=, 
want_zero=, offset=4259840, bytes=12288, pnum=0x7fba27bfb980, 
map=, file=0x7fba27bfb6c8) at ../../block/rbd.c:1355
#5  0x5566ab8f574c in bdrv_co_block_status (bs=0x5566ac468220, 
want_zero=want_zero@entry=false, offset=4259840, bytes=12288, 
pnum=pnum@entry=0x7fba27bfb980, map=map@entry=0x7fba27bfb770, 
file=0x7fba27bfb778) at ../../block/io.c:2489
#6  0x5566ab8f582b in bdrv_co_block_status (bs=bs@entry=0x5566ac62ffd0, 
want_zero=want_zero@entry=false, offset=offset@entry=4259840, 
bytes=bytes@entry=12288, pnum=pnum@entry=0x7fba27bfb980, map=map@entry=0x0, 
file=0x0) at ../../block/io.c:2557
#7  0x5566ab8f8589 in bdrv_co_common_block_status_above 
(bs=bs@entry=0x5566acdf0400, base=base@entry=0x0, 
include_base=include_base@entry=false, want_zero=want_zero@entry=false, 
offset=offset@entry=4259840, bytes=bytes@entry=12288, pnum=0x7fba27bfb980, 
map=0x0, file=0x0, depth=0x7fba27bfb824) at ../../block/io.c:2667
#8  0x5566ab8c975a in bdrv_common_block_status_above (bs=0x5566acdf0400, 
base=base@entry=0x0, include_base=include_base@entry=false, 
want_zero=want_zero@entry=false, offset=4259840, bytes=bytes@entry=12288, 
pnum=0x7fba27bfb980, map=0x0, file=0x0, depth=0x0) at block/block-gen.c:444
#9  0x5566ab8f8920 in bdrv_co_is_zero_fast (bs=bs@entry=0x5566acdf0400, 
offset=, bytes=12288) at ../../block/io.c:2755
#10 0x5566ab91c924 in is_zero_cow (m=0x5566ac938660, bs=0x5566acdf0400) at 
../../block/qcow2.c:2477
#11 handle_alloc_space (l2meta=, bs=0x5566acdf0400) at 
../../block/qcow2.c:2477
#12 qcow2_co_pwritev_task (l2meta=, qiov_offset=, 
qiov=0x5566ad374160, bytes=, offset=, 
host_offset=, bs=0x5566acdf0400) at ../../block/qcow2.c:2550
#13 qcow2_co_pwritev_task_entry (task=) at 
../../block/qcow2.c:2594
#14 0x5566ab919866 in qcow2_add_task (bs=bs@entry=0x5566acdf0400, 
pool=pool@entry=0x0, func=func@entry=0x5566ab91c640 
, 
subcluster_type=subcluster_type@entry=QCOW2_SUBCLUSTER_UNALLOCATED_PLAIN, 
host_offset=471040, offset=offset@entry=4272128, bytes=4096, 
qiov=0x5566ad374160, qiov_offset=0, l2meta=0x5566ac938660) at 
../../block/qcow2.c:2249
#15 0x5566ab919fe7 in qcow2_co_pwritev_part (bs=0x5566acdf0400, 
offset=4272128, bytes=4096, qiov=0x5566ad374160, qiov_offset=0, 
flags=) at ../../block/qcow2.c:2645
#16 0x5566ab8f9099 in bdrv_driver_pwritev (bs=bs@entry=0x5566acdf0400, 
offset=offset@entry=4272128, bytes=bytes@entry=4096, 
qiov=qiov@entry=0x5566ad374160, qiov_offset=qiov_offset@entry=0, 
flags=flags@entry=0) at ../../block/io.c:1252
#17 0x5566ab8fb15f in bdrv_aligned_pwritev (child=0x5566ac6271e0, 
req=0x7fba27bfbe00, offset=4272128, bytes=4096, align=, 
qiov=0x5566ad374160, qiov_offset=0, flags=0) at ../../block/io.c:2126
#18 0x5566ab8fbba8 in bdrv_co_pwritev_part (child=0x5566ac6271e0, 
offset=, offset@entry=4272128, bytes=, 
bytes@entry=4096, qiov=, qiov@entry=0x5566ad374160, 
qiov_offset=, qiov_offset@entry=0, flags=flags@entry=0) at 
../../block/io.c:2314
#19 0x5566ab8ec21d in blk_co_do_pwritev_part (blk=0x5566ad94e410, 
offset=4272128, bytes=4096, qiov=0x5566ad374160, 
qiov_offset=qiov_offset@entry=0, flags=0) at ../../block/block-backend.c:1283
#20 0x5566ab8ec38f in blk_aio_write_entry (opaque=0x5566adfeefc0) at 
../../block/block-backend.c:1467
#21 0x5566ab9ddaa3 in coroutine_trampoline (i0=, 
i1=) at ../../util/coroutine-ucontext.c:173
#22 0x7fbaee637660 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#23 0x7ffc5fa8c270 in ?? ()
#24 0x in ?? ()

** Affects: qemu (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/1968258

[Bug 337377] Re: please restore netselect package: it's _not_ debian-specific

2022-03-06 Thread Markus Ueberall

Any news on this?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/337377

Title:
  please restore netselect package: it's _not_ debian-specific

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/337377/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772451]

Reproducible on:

Version: 7.3.0.3 (x64) / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772451

Title:
  [upstream] Diacritical marks become visible only after changing view
  in Writer

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1772451/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772439]

The problem seems to have been resolved on LO 7.3.0.3 on Windows 10. To
test PDF output this time, I used Adobe Acrobat DC 2021.011.20039
64-bit. I haven't tested on Linux, where the problem initially appeared.

Version: 7.3.0.3 (x64) / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772439

Title:
  [upstream] Arabic text gets deformed when creating a PDF in
  LibreOffice Writer

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1772439/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772445]

Reproducible on:

Version: 7.3.0.3 (x64) / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772445

Title:
  [upstream] Text cannot be rotated in a RTL table in LibreOffice Writer

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1772445/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772520]

Reproducible on:

Version: 7.3.0.3 (x64) / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772520

Title:
  [upstream] Font metrics mixed up when selecting Arabic characters in
  Writer

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1772520/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774244]

Sorry, I take back my word. It's still the same issue in RTL paragraphs
on LO 7.3.0.3. Writing my previous comment, I had only tested LTR
paragraphs, which had other issues. RTL paragraphs still displace the
text one inch to the left and up.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774244

Title:
  [upstream] Rotated Arabic text is displaced in PDF when substitute
  glyphs are used

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1774244/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1793126]

Reproducible on:

Version: 7.3.0.3 (x64) / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793126

Title:
  [upstream] Automatic cell alignment in Calc breaks with bidi-neutral
  characters

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793126/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774244]

This particular problem seems to have been resolved on LO 7.3.0.3 on
Windows 10. Rotating these and other Arabic-script characters does not
work as expected (sometimes the text won't rotate at all or if it does,
the letters are in reversed order) but these seem to be separate issues.

Version: 7.3.0.3 (x64) / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774244

Title:
  [upstream] Rotated Arabic text is displaced in PDF when substitute
  glyphs are used

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1774244/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1793127]

2022-03-01 Thread Miikka-Markus Alhonen

Created attachment 178599
Screenshot on 7.3.0.3

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793127

Title:
  [upstream] Font metrics mixed up for RTL insets in a LTR context in
  Calc

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793127/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1793127]

2022-03-01 Thread Miikka-Markus Alhonen

Tested again on LibreOffice 7.3.0.3 on Windows 10. Now the formula line
looks good but all LTR cells in the main view have font metrics mixed
up, whether I'm currently typing them or not. For some reason, cells
starting with a RTL character that Calc automatically aligns to the
right behave as they should, although they're still not truly RTL, as
the order of mixed LTR/RTL elements is wrong. See the attached
screenshot.

Version: 7.3.0.3 (x64) / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793127

Title:
  [upstream] Font metrics mixed up for RTL insets in a LTR context in
  Calc

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793127/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960159] Re: 5.13 amdgpu, random pixel screen

2022-02-09 Thread Markus H

Hi Juerg,
Installing the new firmware fixes it.Got some error messages but now I am on 
5-13.0-28
Thank you for the support. 

** Attachment added: "Screenshot_2022-02-09_22-51-01.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960159/+attachment/5560088/+files/Screenshot_2022-02-09_22-51-01.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960159

Title:
  5.13 amdgpu, random pixel screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960159/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960454] [NEW] package mysql-server-8.0 8.0.28-0ubuntu0.21.10.3 failed to install/upgrade: »installiertes mysql-server-8.0-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1

2022-02-09 Thread Markus Riepe

Public bug reported:

upgrade to a new ubuntu release

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: mysql-server-8.0 8.0.28-0ubuntu0.21.10.3
ProcVersionSignature: Ubuntu 5.11.0-49.55-generic 5.11.22
Uname: Linux 5.11.0-49-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Feb  9 21:11:14 2022
ErrorMessage: »installiertes mysql-server-8.0-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2021-01-14 (391 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Logs.var.log.daemon.log:
 
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Zu viele Ebenen aus symbolischen 
Links: '/etc/mysql/my.cnf'
MySQLVarLibDirListing: ['server-cert.pem', 'ibdata1', 'binlog.000311', 
'binlog.000324', 'binlog.000308', 'ib_buffer_pool', 'binlog.000313', 
'public_key.pem', 'performance_schema', 'binlog.000327', 'binlog.000323', 
'auto.cnf', 'binlog.000325', '#ib_16384_0.dblwr', 'binlog.000322', 
'binlog.000320', 'private_key.pem', 'binlog.000315', 'ca-key.pem', 
'binlog.index', 'binlog.000321', 'binlog.000312', 'mysql', 'undo_001', 
'client-key.pem', 'binlog.000314', 'ca.pem', 'binlog.000318', 'server-key.pem', 
'binlog.000317', 'ib_logfile0', 'binlog.000316', 'client-cert.pem', 
'binlog.000326', 'ib_logfile1', 'mysql.ibd', 'binlog.000309', 
'mysql_upgrade_info', 'debian-5.7.flag', '#ib_16384_1.dblwr', 'sys', 
'undo_002', 'binlog.000319', '#innodb_temp', 'binlog.000310']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.11.0-49-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.20.9ubuntu2
 apt  2.3.9
SourcePackage: mysql-8.0
Title: package mysql-server-8.0 8.0.28-0ubuntu0.21.10.3 failed to 
install/upgrade: »installiertes mysql-server-8.0-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
UpgradeStatus: Upgraded to impish on 2022-02-09 (0 days ago)

** Affects: mysql-8.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960454

Title:
  package mysql-server-8.0 8.0.28-0ubuntu0.21.10.3 failed to
  install/upgrade: »installiertes mysql-server-8.0-Skript des Paketes
  post-installation«-Unterprozess gab den Fehlerwert 1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1960454/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960159] Re: 5.13 amdgpu, random pixel screen

2022-02-06 Thread Markus H

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960159/+attachment/5559379/+files/lspci-vnvn.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960159

Title:
  5.13 amdgpu, random pixel screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960159/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960159] [NEW] 5.13 amdgpu, random pixel screen

2022-02-06 Thread Markus H

Public bug reported:

Hi, I have a Laptop with a Ryzen 5500U, running Linux Mint 20.3. To make
use of the graphics driver, I update the kernel from 5.4 to 5.13. The
computer is booting up, the LM splash screen apprears and then the
screen gets funky with a random assignment of pixels. It seems each
pixel gets a random assigned color (white, red, blue, green?, black).
The pixels change color roughly every 200-500 ms. This happens with
5.13.0-28 and 5.13.0-23. The laptop is not responding to anything.

Using 5.11.22 works without any flaws. AMD gpu drivers are installed correctly.

Mandatory information 1st:

This one is running:
Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22

Description:Linux Mint 20.3
Release:20.3

description: Notebook
product: 82LM (LENOVO_MT_82LM_BU_idea_FM_IdeaPad 5 14ALC05)
vendor: LENOVO
version: IdeaPad 5 14ALC05
serial: MP1X
width: 64 bits

** Affects: linux (Ubuntu)
Importance: Undecided
Status: New

** Tags: 5.13.0-23 5.13.0-28 amdgpu kernel-bug

** Attachment added: "IMG_20220206_130329s.jpg"

https://bugs.launchpad.net/bugs/1960159/+attachment/5559378/+files/IMG_20220206_130329s.jpg

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960159

Title:
5.13 amdgpu, random pixel screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960159/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959727] [NEW] Live-Disc install failure: ubi-partman exits 141 - file not found

2022-02-01 Thread markus

Public bug reported:

Using Ubuntu 20.04.1 Desktop Live CD i tried manually formatting my disc
using an encrypted disc as root and an additional partition as boot.

I got this from syslog:

Feb  1 20:36:12 ubuntu ubiquity: /lib/partman/choose_partition/30lvm/choices: 
475: cannot open /var/lib/partman/outfifo: No such file
Feb  1 20:36:12 ubuntu ubiquity: sh: 0: getcwd() failed: No such file or 
directory
Feb  1 20:36:12 ubuntu ubiquity: 
/lib/partman/choose_partition/35crypto/choices: 475: cannot open 
/var/lib/partman/outfifo: No such file
Feb  1 20:36:12 ubuntu ubiquity: sh: 0: getcwd() failed: No such file or 
directory
Feb  1 20:36:12 ubuntu ubiquity: message repeated 4 times: [ sh: 0: getcwd() 
failed: No such file or directory]
Feb  1 20:36:12 ubuntu ubiquity[111530]: Traceback (most recent call last):
Feb  1 20:36:12 ubuntu ubiquity[111530]:   File 
"/usr/lib/ubiquity/ubiquity/misc.py", line 184, in grub_options
Feb  1 20:36:12 ubuntu ubiquity[111530]: for part in p.partitions():
Feb  1 20:36:12 ubuntu ubiquity[111530]:   File 
"/usr/lib/ubiquity/ubiquity/parted_server.py", line 207, in partitions
Feb  1 20:36:12 ubuntu ubiquity[111530]: self.open_dialog('PARTITIONS')
Feb  1 20:36:12 ubuntu ubiquity[111530]:   File 
"/usr/lib/ubiquity/ubiquity/parted_server.py", line 140, in open_dialog
Feb  1 20:36:12 ubuntu ubiquity[111530]: self.outf = open(outfifo, 'r')
Feb  1 20:36:12 ubuntu ubiquity[111530]: FileNotFoundError: [Errno 2] Datei 
oder Verzeichnis nicht gefunden: '/var/lib/partman/outfifo'
Feb  1 20:36:12 ubuntu ubiquity[111530]:
Feb  1 20:36:12 ubuntu ubiquity[111530]: Traceback (most recent call last):
Feb  1 20:36:12 ubuntu ubiquity[111530]:   File 
"/usr/lib/ubiquity/ubiquity/misc.py", line 213, in boot_device
Feb  1 20:36:12 ubuntu ubiquity[111530]: for part in p.partitions():
Feb  1 20:36:12 ubuntu ubiquity[111530]:   File 
"/usr/lib/ubiquity/ubiquity/parted_server.py", line 207, in partitions
Feb  1 20:36:12 ubuntu ubiquity[111530]: self.open_dialog('PARTITIONS')
Feb  1 20:36:12 ubuntu ubiquity[111530]:   File 
"/usr/lib/ubiquity/ubiquity/parted_server.py", line 142, in open_dialog
Feb  1 20:36:12 ubuntu ubiquity[111530]: self.error_handler()
Feb  1 20:36:12 ubuntu ubiquity[111530]:   File 
"/usr/lib/ubiquity/ubiquity/parted_server.py", line 130, in error_handler
Feb  1 20:36:12 ubuntu ubiquity[111530]: raise 
PartedServerError(exception_type, message, options)
Feb  1 20:36:12 ubuntu ubiquity[111530]: 
ubiquity.parted_server.PartedServerError: ('', '', [])
Feb  1 20:36:12 ubuntu ubiquity[111530]:
Feb  1 20:36:12 ubuntu ubiquity[111530]: Traceback (most recent call last):
Feb  1 20:36:12 ubuntu ubiquity[111530]:   File 
"/usr/lib/ubiquity/ubiquity/misc.py", line 184, in grub_options
Feb  1 20:36:12 ubuntu ubiquity[111530]: for part in p.partitions():
Feb  1 20:36:12 ubuntu ubiquity[111530]:   File 
"/usr/lib/ubiquity/ubiquity/parted_server.py", line 207, in partitions
Feb  1 20:36:12 ubuntu ubiquity[111530]: self.open_dialog('PARTITIONS')
Feb  1 20:36:12 ubuntu ubiquity[111530]:   File 
"/usr/lib/ubiquity/ubiquity/parted_server.py", line 142, in open_dialog
Feb  1 20:36:12 ubuntu ubiquity[111530]: self.error_handler()
Feb  1 20:36:12 ubuntu ubiquity[111530]:   File 
"/usr/lib/ubiquity/ubiquity/parted_server.py", line 130, in error_handler
Feb  1 20:36:12 ubuntu ubiquity[111530]: raise 
PartedServerError(exception_type, message, options)
Feb  1 20:36:12 ubuntu ubiquity[111530]: 
ubiquity.parted_server.PartedServerError: ('', '', [])
Feb  1 20:36:12 ubuntu ubiquity[111530]:
Feb  1 20:36:13 ubuntu ubiquity[111530]: debconffilter_done: ubi-partman 
(current: None)

** 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/1959727

Title:
  Live-Disc install failure: ubi-partman exits 141 - file not found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1959727/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956776] Re: g.extension crashed with FileNotFoundError in _execute_child(): [Errno 2] No such file or directory: 'svn'

2022-01-08 Thread Markus Neteler

In essence, it has already been fixed in GRASS GIS 7.8.6.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956776

Title:
  g.extension crashed with FileNotFoundError in _execute_child(): [Errno
  2] No such file or directory: 'svn'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grass/+bug/1956776/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956776] Re: g.extension crashed with FileNotFoundError in _execute_child(): [Errno 2] No such file or directory: 'svn'

2022-01-08 Thread Markus Neteler

The reason is that the GRASS GIS Addons repository has been restructured
in 2021 to distinguish GRASS GIS 7 from the new version 8.

Hence,

`Downloading source code for  from
`

is no longer a valid path, the new path is:

https://github.com/OSGeo/grass-addons/tree/grass7/src/raster/r.in.usgs

Possibilities for you:
a) you use GRASS GIS 7.8.2 which is fairly old. Please update as `g.extension` 
has been updated accordingly to use the new path in later versions (starting 
from GRASS GIS 7.8.6).
b) if that's not possible, you may edit your local `g.extension` file in 
`/usr/lib64/grass78/scripts/g.extension`, using the changes provided here: 
https://github.com/OSGeo/grass/pull/1762

See also:

https://trac.osgeo.org/grass/wiki/Release/7.8.6-News#Majormodulechanges
- G78:g.extension: updated to match new addon repository structure (PR:1762)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956776

Title:
  g.extension crashed with FileNotFoundError in _execute_child(): [Errno
  2] No such file or directory: 'svn'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grass/+bug/1956776/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1951812] [NEW] Version 1.1.0-19-g135c72a-6 results in segfault

2021-11-22 Thread Markus Rassow

Public bug reported:

PHP7.4 result in segfault if installed.
Syslog entries (repeated):
(servername) kernel: [timestamp] php7.4[various number]: segfault at (various 
address) ip (various address) sp (various address) error 4 in libc.so.6[various 
address]
(servername) kernel: [timestamp] Code: 96 13 00 e8 34 be ff ff 0f 1f 40 00 f3 
0f 1e fa 48 85 ff 0f 84 9b 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 62 
f1 16 00 <48> 8b 47 f8 64 8b 2b a8 02 75 37 48 8b 15 e8 f0 16 00 64 48 83 3a

The code always is the same.

I checked three times to install and test, remove and test again with the 
result, if facedetect was installed i got the error and after remove the error 
also is removed.
php7.4-facedetect (1.1.0-19-g135c72a-6+ubuntu20.04.1+deb.sury.org+1) on ubuntu 
server 21.10.

** Affects: php-facedetect (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/1951812

Title:
  Version 1.1.0-19-g135c72a-6 results in segfault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-facedetect/+bug/1951812/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1933880] Re: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it

2021-11-19 Thread Markus

Confirming this problem.
The work-around does not work for me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933880

Title:
  systemd-logind crash when suspend with nvidia-suspend.service masked,
  bringing session down with it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1933880/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1090625] Re: zaz crashes on startup

2021-10-21 Thread Markus Koschany

This issue should bw fixed with version 1.0.1 because the music files
can be distributed now.

** Changed in: zaz (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: zaz (Ubuntu)
 Assignee: (unassigned) => Markus Koschany (apoleon)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090625

Title:
  zaz crashes on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zaz/+bug/1090625/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1089234] Re: segmentation fault on starting a new level

2021-10-21 Thread Markus Koschany

I consider this issue fixed in version 1.0.1-1. The music files are free
now and we can ship them again. Everything should work as expected now.

** Changed in: zaz (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: zaz (Ubuntu)
 Assignee: (unassigned) => Markus Koschany (apoleon)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1089234

Title:
  segmentation fault on starting a new level

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zaz/+bug/1089234/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945868] Re: focal kvm virtio_net set_features failed (-22)

2021-10-04 Thread Markus Neubauer

The relevant part of the kern.log is already within the description. As
the server is in production we needed to return to previous kernel.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945868

Title:
  focal kvm virtio_net set_features failed (-22)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945868/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945888] [NEW] DHCPv6 too strict when the response is missing IAID for some sections

2021-10-03 Thread Ole Markus With

Public bug reported:

Systemd incorrectly ignores whole messages when IAID is missing for some 
sections.
This has been reported upstream [1] and fixed [2].

$ lsb_release -rd
Description:Ubuntu 21.04
Release:21.04

 $ apt-cache policy systemd
systemd:
  Installed: 247.3-3ubuntu3.6
  Candidate: 247.3-3ubuntu3.6
  Version table:
 *** 247.3-3ubuntu3.6 500
500 http://no.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 247.3-3ubuntu3.4 500
500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
 247.3-3ubuntu3 500
500 http://no.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages


What is expected to happen is that systemd will ignore only the relevant part 
of the message, not the entire message. 

What is happening is that the entire message is ignored, leading to DHCP
leases not being renewed. This is fairly easy to replicate e.g in AWS by
enabling both an IPv6 prefix and an IPv6 single address to the same
interface.

[1] https://github.com/systemd/systemd/issues/20803
[2] https://github.com/systemd/systemd/pull/20807

** Affects: systemd (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/1945888

Title:
  DHCPv6 too strict when the response is missing IAID for some sections

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1945888/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945887] [NEW] org.bluez.obex.service contains unresolved '@libexecdir@'

2021-10-03 Thread Markus Ueberall

Public bug reported:

After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday,
the following error message showed up in the syslog:

Oct  2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760]
Activated service 'org.bluez.obex' failed: Failed to execute program
org.bluez.obex: No such file or directory

Upon inspection, this was due to the fact that the service definition
contained the line 'Exec=@libexecdir@/obexd' which could not be resolved
(this placeholder is supposedly to be replaced at build time).

Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this
(together with 'systemctl --user daemon-reload; systemctl --user restart
obex').

Note that this problem should be part of *all* current versions of the
bluez[-obexd] package, regardless of the used architecture (including
Focal, Impish):

% wget 
https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb
[...]
Länge: 217906 (213K) [application/x-debian-package]
Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert.
[...]
2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« 
gespeichert [217906/217906]

% dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish
% grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service
Exec=@libexecdir@/obexd
% wget 
https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb
[...]
Länge: 160832 (157K) [application/x-debian-package]
Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert.
[...]
2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« 
gespeichert [160832/160832]

% dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal
% grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service
Exec=@libexecdir@/obexd
%


# lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
# apt-cache policy bluez-obexd
bluez-obexd:
[...]
 5.53-0ubuntu3.3 500
500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
[...]

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945887

Title:
  org.bluez.obex.service contains unresolved '@libexecdir@'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1945887/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945868] Re: focal kvm virtio_net set_features failed (-22)

** Also affects: focal (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/1945868

Title:
  focal kvm virtio_net set_features failed (-22)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/focal/+bug/1945868/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945868] Re: focal kvm virtio_net set_features failed (-22)

Just found found out, it is regarding to kernel linux-
image-5.4.0-88-generic and it occured after upgrading to focal.

I returned to kernel Linux version 4.15.0-159-generic and everything is
as expected (normal).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945868

Title:
  focal kvm virtio_net set_features failed (-22)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1945868/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945868] Re: focal kvm virtio_net set_features failed (-22)

** Description changed:

- Using linux-modules-5.4.0-88-generic within focal.
+ Setup linux-modules-5.4.0-88-generic within focal guest on a (equal)
+ ubuntu 20.04 kvm bare metal machine.
  
  When using virtio as network driver it is failing with:
  
  net eth0: Fail to set guest offload.
  virtio_net virtio1 eth0: set_features() failed (-22); wanted 
0x008000174a29, left 0x0
  0800017ca29
  
  followed by further kern log entries:
  [ cut here ]
   netdevice: br0: failed to disable 0x8000 on eth0!
   WARNING: CPU: 0 PID: 1048 at net/core/dev.c:8683 
__netdev_update_features+0x4d1/0x9f0
   Modules linked in: macvlan virtio_gpu ttm drm_kms_helper fb_sys_fops 
input_leds syscopyarea joydev sysfillrect serio_raw sysimgblt mac_hid 
sch_fq_codel 9p fscache 9pnet_virtio 9pnet bridge stp llc drm virtio_rng 
ip_tables x_tables autofs4 dm_thin_pool dm_persistent_data dm_bio_prison 
dm_bufio libcrc32c psmouse virtio_net i2c_piix4 virtio_blk net_failover 
failover pata_acpi floppy
   CPU: 0 PID: 1048 Comm: brctl Tainted: GW 5.4.0-88-generic 
#99-Ubuntu
   Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
   RIP: 0010:__netdev_update_features+0x4d1/0x9f0
   Code: c7 c2 9b 30 9b a0 4c 8b 4d 88 48 85 c0 4d 0f 44 d4 4d 89 f0 48 8d 4d 
b8 4c 89 ca 4c 89 d6 48 c7 c7 d0 94 a3 a0 e8 dc 2d 19 00 <0f> 0b e9 5b fe ff ff 
8b 45 9c 85 c0 0f 84 96 00 00 00 8b 45 9c f7
   RSP: 0018:bf1840e0ba98 EFLAGS: 00010282
   RAX:  RBX: 000f RCX: 0006
   RDX: 0007 RSI: 0082 RDI: 9c2c13a178c0
   RBP: bf1840e0bb10 R08: 02d1 R09: 0004
   R10:  R11: 0001 R12: 9c2c0b258000
   R13: 9c2c0b2580c0 R14: 9c2c0615a000 R15: 000f
   FS:  7f98be558580() GS:9c2c13a0() knlGS:
   CS:  0010 DS:  ES:  CR0: 80050033
   CR2: 7fffc24a1080 CR3: 00030b3e4000 CR4: 06f0
   Call Trace:
    netdev_update_features+0x25/0x60
    br_device_event+0x20f/0x300 [bridge]
    notifier_call_chain+0x55/0x80
    raw_notifier_call_chain+0x16/0x20
    call_netdevice_notifiers_info+0x2e/0x60
    netdev_update_features+0x59/0x60
    dev_disable_lro+0x21/0xf0
    br_add_if+0x301/0x650 [bridge]
    add_del_if+0x67/0x80 [bridge]
    br_dev_ioctl+0x54/0x80 [bridge]
    dev_ifsioc+0xe5/0x3e0
    ? _cond_resched+0x19/0x30
    dev_ioctl+0x2dd/0x470
    sock_do_ioctl+0xa8/0x140
    ? evict+0x14c/0x1b0
    sock_ioctl+0x24f/0x3c0
    ? _cond_resched+0x19/0x30
    ? get_max_files+0x20/0x20
    do_vfs_ioctl+0x407/0x670
    ksys_ioctl+0x67/0x90
    __x64_sys_ioctl+0x1a/0x20
    do_syscall_64+0x57/0x190
    entry_SYSCALL_64_after_hwframe+0x44/0xa9
   RIP: 0033:0x7f98be47c50b
   Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff 
ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 
01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48
   RSP: 002b:7ffd783321e8 EFLAGS: 0246 ORIG_RAX: 0010
   RAX: ffda RBX: 0002 RCX: 7f98be47c50b
   RDX: 7ffd78332210 RSI: 89a2 RDI: 0003
   RBP: 7ffd78332210 R08: 0020 R09: fefefeff77686d74
   R10: 7ffd78333e80 R11: 0246 R12: 7ffd78333e7e
   R13: 7ffd78333e7e R14:  R15: 
   ---[ end trace 240d361752e8f3f0 ]---
   [ cut here ]
  
  Temporary solution is to return to the old rtl8139 driver and slow
  network down

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945868

Title:
  focal kvm virtio_net set_features failed (-22)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1945868/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1945868] [NEW] focal kvm virtio_net set_features failed (-22)

Public bug reported:

Using linux-modules-5.4.0-88-generic within focal.

When using virtio as network driver it is failing with:

net eth0: Fail to set guest offload.
virtio_net virtio1 eth0: set_features() failed (-22); wanted 
0x008000174a29, left 0x0
0800017ca29

followed by further kern log entries:
[ cut here ]
 netdevice: br0: failed to disable 0x8000 on eth0!
 WARNING: CPU: 0 PID: 1048 at net/core/dev.c:8683 
__netdev_update_features+0x4d1/0x9f0
 Modules linked in: macvlan virtio_gpu ttm drm_kms_helper fb_sys_fops 
input_leds syscopyarea joydev sysfillrect serio_raw sysimgblt mac_hid 
sch_fq_codel 9p fscache 9pnet_virtio 9pnet bridge stp llc drm virtio_rng 
ip_tables x_tables autofs4 dm_thin_pool dm_persistent_data dm_bio_prison 
dm_bufio libcrc32c psmouse virtio_net i2c_piix4 virtio_blk net_failover 
failover pata_acpi floppy
 CPU: 0 PID: 1048 Comm: brctl Tainted: GW 5.4.0-88-generic 
#99-Ubuntu
 Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
 RIP: 0010:__netdev_update_features+0x4d1/0x9f0
 Code: c7 c2 9b 30 9b a0 4c 8b 4d 88 48 85 c0 4d 0f 44 d4 4d 89 f0 48 8d 4d b8 
4c 89 ca 4c 89 d6 48 c7 c7 d0 94 a3 a0 e8 dc 2d 19 00 <0f> 0b e9 5b fe ff ff 8b 
45 9c 85 c0 0f 84 96 00 00 00 8b 45 9c f7
 RSP: 0018:bf1840e0ba98 EFLAGS: 00010282
 RAX:  RBX: 000f RCX: 0006
 RDX: 0007 RSI: 0082 RDI: 9c2c13a178c0
 RBP: bf1840e0bb10 R08: 02d1 R09: 0004
 R10:  R11: 0001 R12: 9c2c0b258000
 R13: 9c2c0b2580c0 R14: 9c2c0615a000 R15: 000f
 FS:  7f98be558580() GS:9c2c13a0() knlGS:
 CS:  0010 DS:  ES:  CR0: 80050033
 CR2: 7fffc24a1080 CR3: 00030b3e4000 CR4: 06f0
 Call Trace:
  netdev_update_features+0x25/0x60
  br_device_event+0x20f/0x300 [bridge]
  notifier_call_chain+0x55/0x80
  raw_notifier_call_chain+0x16/0x20
  call_netdevice_notifiers_info+0x2e/0x60
  netdev_update_features+0x59/0x60
  dev_disable_lro+0x21/0xf0
  br_add_if+0x301/0x650 [bridge]
  add_del_if+0x67/0x80 [bridge]
  br_dev_ioctl+0x54/0x80 [bridge]
  dev_ifsioc+0xe5/0x3e0
  ? _cond_resched+0x19/0x30
  dev_ioctl+0x2dd/0x470
  sock_do_ioctl+0xa8/0x140
  ? evict+0x14c/0x1b0
  sock_ioctl+0x24f/0x3c0
  ? _cond_resched+0x19/0x30
  ? get_max_files+0x20/0x20
  do_vfs_ioctl+0x407/0x670
  ksys_ioctl+0x67/0x90
  __x64_sys_ioctl+0x1a/0x20
  do_syscall_64+0x57/0x190
  entry_SYSCALL_64_after_hwframe+0x44/0xa9
 RIP: 0033:0x7f98be47c50b
 Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff 
c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 
c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48
 RSP: 002b:7ffd783321e8 EFLAGS: 0246 ORIG_RAX: 0010
 RAX: ffda RBX: 0002 RCX: 7f98be47c50b
 RDX: 7ffd78332210 RSI: 89a2 RDI: 0003
 RBP: 7ffd78332210 R08: 0020 R09: fefefeff77686d74
 R10: 7ffd78333e80 R11: 0246 R12: 7ffd78333e7e
 R13: 7ffd78333e7e R14:  R15: 
 ---[ end trace 240d361752e8f3f0 ]---
 [ cut here ]

Temporary solution is to return to the old rtl8139 driver and slow
network down

** Affects: qemu-kvm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal kvm virtio

** Description changed:

  Using linux-modules-5.4.0-88-generic within focal.
  
  When using virtio as network driver it is failing with:
  
  net eth0: Fail to set guest offload.
  virtio_net virtio1 eth0: set_features() failed (-22); wanted 
0x008000174a29, left 0x0
  0800017ca29
  
  followed by further kern log entries:
  [ cut here ]
-  netdevice: br0: failed to disable 0x8000 on eth0!
-  WARNING: CPU: 0 PID: 1048 at net/core/dev.c:8683 
__netdev_update_features+0x4d1/0x9f0
-  Modules linked in: macvlan virtio_gpu ttm drm_kms_helper fb_sys_fops 
input_leds syscopyarea joydev sysfillrect serio_raw sysimgblt mac_hid 
sch_fq_codel 9p fscache 9pnet_virtio 9pnet bridge stp llc drm virtio_rng 
ip_tables x_tables autofs4 dm_thin_pool dm_persistent_data dm_bio_prison 
dm_bufio libcrc32c psmouse virtio_net i2c_piix4 virtio_blk net_failover 
failover pata_acpi floppy
-  CPU: 0 PID: 1048 Comm: brctl Tainted: GW 5.4.0-88-generic 
#99-Ubuntu
-  Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
-  RIP: 0010:__netdev_update_features+0x4d1/0x9f0
-  Code: c7 c2 9b 30 9b a0 4c 8b 4d 88 48 85 c0 4d 0f 44 d4 4d 89 f0 48 8d 4d 
b8 4c 89 ca 4c 89 d6 48 c7 c7 d0 94 a3 a0 e8 dc 2d 19 00 <0f> 0b e9 5b fe ff ff 
8b 45 9c 85 c0 0f 84 96 00 00 00 8b 45 9c f7
-  RSP: 0018:bf1840e0ba98 EFLAGS: 00010282
-  RAX:  RBX: 000f RCX: 0006
-  RDX: 0007 RSI: 0082 RDI: 9c2c13a178c0
-  RBP: bf1840e0bb10

[Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]

2021-10-01 Thread Markus W

This bug should be fixed with 
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2003
I cannot reproduce the issue anymore when this change is applied on my system.

Can someone initiate that this fix is backported into Ubuntu 21.04?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933996

Title:
  Alt-tab stops switching windows [JS ERROR: TypeError: window is null
  _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942622] Re: Gnome control center displays tab crashes if you unplug all monitors

2021-09-06 Thread Markus Ilmola

The link is:
https://errors.ubuntu.com/oops/47a66160-0f28-11ec-b051-fa163e6cac46

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942622

Title:
  Gnome control center displays tab crashes if you unplug all monitors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942622/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913421] Re: Load of pre-upgrade qemu modules needs to avoid noexec

2021-09-06 Thread Markus Schade

As this has bitten us more than once in the past, we had to find a solution 
that would work for us while this issue was discussed. Adding a mount unit 
without noexec for /run/qemu was the obvious and most straightforward solution. 
We have on average at least one qemu update between reboots, so having a 
reliable and trackable mount unit would be the preferred solution. 
But I do acknowledge that the DH acrobatics are a bit ugly. :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913421

Title:
  Load of pre-upgrade qemu modules needs to avoid noexec

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1913421/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942622] Re: Gnome control center displays tab crashes if you unplug all monitors

2021-09-03 Thread Markus Ilmola

** Description changed:

  1. Open gnome control center.
  2. Open the "Displays" tab
  3. Unplug ALL monitors
  4. Plug a monitor back in.
  5. Gnome Control center has crashed
+ 
+ ps.
+ Also tested this on Ubuntu 21.04 using a live USB stick and interestingly 
Gnome control center does not crash but freezes instead and has to be force 
quit.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  3 19:25:36 2021
  InstallationDate: Installed on 2021-08-26 (7 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: gnome-control-center
  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/1942622

Title:
  Gnome control center displays tab crashes if you unplug all monitors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942622/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942622] [NEW] Gnome control center displays tab crashes if you unplug all monitors

2021-09-03 Thread Markus Ilmola

Public bug reported:

1. Open gnome control center.
2. Open the "Displays" tab
3. Unplug ALL monitors
4. Plug a monitor back in.
5. Gnome Control center has crashed

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.5-0ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  3 19:25:36 2021
InstallationDate: Installed on 2021-08-26 (7 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942622

Title:
  Gnome control center displays tab crashes if you unplug all monitors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942622/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937269] Re: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build

2021-07-22 Thread Markus

** Description changed:

  Crash dialog show up on reboot right after kernel update + reinstalling
  using:
  
  apt purge nvidia-driver-460 # enforce a fresh install
  apt install nvidia-driver-460
+ 
+ Besides the crash dialog, I did not notice any problems so far; e.g. no
+ visual impact, nvidia utils launch as usual showing information, etc...
+ 
+ - - - - - - - - - - - - -
+ 
  
  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.8.0-59-generic
  Date: Wed Jul 21 08:14:54 2021
  Dependencies:
  
  DuplicateSignature: 
dkms:nvidia-kernel-source-460:460.91.03-0ubuntu0.20.04.1:clang: error: 
unsupported option '-dumpspecs'
  InstallationDate: Installed on 2021-05-27 (55 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageVersion: 460.91.03-0ubuntu0.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-460
  Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel 
module failed to build
  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/1937269

Title:
  nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel
  module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1937269/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937269] [NEW] nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build

2021-07-22 Thread Markus

Public bug reported:

Crash dialog show up on reboot right after kernel update + reinstalling
using:

apt purge nvidia-driver-460 # enforce a fresh install
apt install nvidia-driver-460

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.8.0-59-generic
Date: Wed Jul 21 08:14:54 2021
Dependencies:

DuplicateSignature: 
dkms:nvidia-kernel-source-460:460.91.03-0ubuntu0.20.04.1:clang: error: 
unsupported option '-dumpspecs'
InstallationDate: Installed on 2021-05-27 (55 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageVersion: 460.91.03-0ubuntu0.20.04.1
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: nvidia-graphics-drivers-460
Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel 
module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-460 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

** Description changed:

- Crash dialog show up right after kernel update + reinstalling using:
+ Crash dialog show up on reboot right after kernel update + reinstalling
+ using:
  
  apt purge nvidia-driver-460 # enforce a fresh install
  apt install nvidia-driver-460
  
  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.8.0-59-generic
  Date: Wed Jul 21 08:14:54 2021
  Dependencies:
-  
+ 
  DuplicateSignature: 
dkms:nvidia-kernel-source-460:460.91.03-0ubuntu0.20.04.1:clang: error: 
unsupported option '-dumpspecs'
  InstallationDate: Installed on 2021-05-27 (55 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageVersion: 460.91.03-0ubuntu0.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
-  dpkg 1.19.7ubuntu3
-  apt  2.0.6
+  dpkg 1.19.7ubuntu3
+  apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-460
  Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel 
module failed to build
  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/1937269

Title:
  nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel
  module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1937269/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1936967] [NEW] grub fails on fresh Ubuntu 21.04 installation

2021-07-20 Thread Miikka-Markus Alhonen

Public bug reported:

I did a fresh Ubuntu 21.04 installation from a USB drive on a machine
which already had Windows 10. I selected default settings for dual-boot,
did not connect to Wifi since I didn't have time to wait for downloads,
and checked 3rd party software. Everything went fine until it was time
to set up grub, at which point I got a fatal error saying grub
installation failed on /dev/sda. The installation program launched
desktop mode, so that I could investigate the problem. I downloaded
boot-repair and launched it but it failed, since the installation
program was still running. Next I shut down the computer and was
surprised to notice that the hard drive did actually boot grub, from
where I was able to select Ubuntu. Though the system had started, I
decided to run boot-repair again just to make sure nothing's missing.
Boot-repair suggested some commands (including apt install -fy) that I
copy-pasted to term, and as a result I lost access to Wifi and could not
mount the USB drive anymore - apparently it had removed network-manager
plus other important packages and had not reinstalled them. At this
point, booting from the hard drive had stopped working, as I was only
presented with a "grub rescue" prompt, so I booted a live system from
the Ubuntu installation flash drive, downloaded boot-repair and ran it
again. Boot-repair claimed to have fixed something but even after that,
I only got a grub rescue prompt. Then I rebooted from the Ubuntu USB
again, and selected reinstallation without removing user files. This
time I connected to Wifi but unchecked updates during installation.
Everything progressed normally until it was again time to set up grub,
and the system gave me the same fatal error as in the beginning. I'm
still looking for a way to make everything work.

The machine is an older HP Pavilion g series laptop with BIOS (no UEFI),
Windows is on /dev/sda1 with around 250 GB of space and the partition I
tried Ubuntu on is at the end of the hard drive with around 450 GB of
space. There are a couple of smaller partitions in between (Windows
rescue etc.).

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.19
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-gl-390_390.141-0ubuntu2_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-460/libnvidia-gl-460_460.67-0ubuntu1_amd64.deb
CasperMD5CheckResult: fail
CasperVersion: 1.461
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 20 16:59:52 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 LANGUAGE=fi_FI.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 LC_NUMERIC=C.UTF-8
RebootRequiredPkgs:
 linux-image-5.11.0-16-generic
 linux-base
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute ubiquity-21.04.19 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936967

Title:
  grub fails on fresh Ubuntu 21.04 installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1936967/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929833] Re: bluez: meshctl missing

2021-06-24 Thread Markus Becker

I do see an update to 5.88 with
https://git.launchpad.net/ubuntu/+source/bluez/commit/?id=f0877af285d9360c02762de34a79ed11c72a84ca,
but I do not see the binary meshctl being added.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929833

Title:
  bluez: meshctl missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1929833/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929833] Re: bluez: meshctl missing

2021-06-24 Thread Markus Becker

I do see an update of bluez to 5.58
https://git.launchpad.net/ubuntu/+source/bluez/commit/?id=f0877af285d9360c02762de34a79ed11c72a84ca
5.58, but no changes that would add meshctl.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929833

Title:
  bluez: meshctl missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1929833/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929833] [NEW] bluez: meshctl missing

2021-05-27 Thread Markus Becker

Public bug reported:

bluez has added a new tool for BT mesh handling.

Debian has a new binary package: https://packages.debian.org/bullseye
/bluez-meshd

Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579

** Affects: bluez (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/1929833

Title:
  bluez: meshctl missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1929833/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891817] Re: Raspberry Pi: u-boot hangs when (non-boot-related) USB disks are attached during boot

2021-05-18 Thread Markus Dobel

Thanks for the update. This hint (about dropping U-Boot) is actually
something I found elsewhere as well, and I can confirm that it works.

And if that's the way how the problem goes away for Ubuntu installs, I
would not even call it "won't fix". I don't need U-Boot, I just need a
system that boots reliably :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891817

Title:
  Raspberry Pi: u-boot hangs when (non-boot-related) USB disks are
  attached during boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1891817/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913421] Re: Load of pre-upgrade qemu modules needs to avoid noexec

2021-05-06 Thread Markus Schade

Are there any plans to go forward with any of the above mentioned solutions?
Currently I either have to migrate off all guests before a qemu upgrade or set 
up a tmpfs mount with exec on /run/qemu.

Happy to help testing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913421

Title:
  Load of pre-upgrade qemu modules needs to avoid noexec

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1913421/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913866] Re: intel-microcode 20210216 bump request

2021-04-27 Thread Markus Schade

Please consider importing the 20210216 update from Debian where it has
been available since February. It contains fixes for INTEL-SA-00381 on
Skylake and CascadeLake systems.

** Summary changed:

- intel-microcode 20201118 bump request
+ intel-microcode 20210216 bump request

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913866

Title:
  intel-microcode 20210216 bump request

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1913866/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921880] Re: Add EPYC-Milan model

focal: qemu 1:4.2-3ubuntu6.15, libvirt 6.0.0-0ubuntu8.8

# qemu-system-x86_64 -cpu ? | grep EPYC
x86 EPYC (alias configured by machine type)
x86 EPYC-IBPB (alias of EPYC-v2)
x86 EPYC-Rome (alias configured by machine type)
x86 EPYC-Rome-v1 AMD EPYC-Rome Processor
x86 EPYC-v1 AMD EPYC Processor
x86 EPYC-v2 AMD EPYC Processor (with IBPB)
x86 EPYC-v3 AMD EPYC Processor

# virsh domcapabilities

  EPYC-Rome
  AMD
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


After:

# qemu-system-x86_64 -cpu ? | grep EPYC
x86 EPYC (alias configured by machine type)
x86 EPYC-IBPB (alias of EPYC-v2)
x86 EPYC-Milan (alias configured by machine type)
x86 EPYC-Milan-v1 AMD EPYC-Milan Processor
x86 EPYC-Rome (alias configured by machine type)
x86 EPYC-Rome-v1 AMD EPYC-Rome Processor
x86 EPYC-Rome-v2 AMD EPYC-Rome Processor
x86 EPYC-v1 AMD EPYC Processor
x86 EPYC-v2 AMD EPYC Processor (with IBPB)
x86 EPYC-v3 AMD EPYC Processor


  EPYC-Milan
  AMD
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


Still working as expected


** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921880

Title:
  Add EPYC-Milan model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921880/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921754] Re: Add missing cpu feature bits in EPYC-Rome model

focal: qemu 1:4.2-3ubuntu6.15, libvirt 6.0.0-0ubuntu8.8

# qemu-system-x86_64 -cpu ? | grep EPYC
x86 EPYC  (alias configured by machine type)  
x86 EPYC-IBPB (alias of EPYC-v2)  
x86 EPYC-Rome (alias configured by machine type)  
x86 EPYC-Rome-v1  AMD EPYC-Rome Processor 
x86 EPYC-v1   AMD EPYC Processor  
x86 EPYC-v2   AMD EPYC Processor (with IBPB)  
x86 EPYC-v3   AMD EPYC Processor

# virsh domcapabilities

  EPYC-Rome
  AMD
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


After:

# qemu-system-x86_64 -cpu ? | grep EPYC
x86 EPYC  (alias configured by machine type)  
x86 EPYC-IBPB (alias of EPYC-v2)  
x86 EPYC-Milan(alias configured by machine type)  
x86 EPYC-Milan-v1 AMD EPYC-Milan Processor
x86 EPYC-Rome (alias configured by machine type)  
x86 EPYC-Rome-v1  AMD EPYC-Rome Processor 
x86 EPYC-Rome-v2  AMD EPYC-Rome Processor 
x86 EPYC-v1   AMD EPYC Processor  
x86 EPYC-v2   AMD EPYC Processor (with IBPB)  
x86 EPYC-v3   AMD EPYC Processor   


  EPYC-Milan
  AMD
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


Still working as expected

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921754

Title:
  Add missing cpu feature bits in EPYC-Rome model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921754/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921754] Re: Add missing cpu feature bits in EPYC-Rome model

Old:
qemu 1:4.2-3ubuntu6.15, libvirt 6.0.0-0ubuntu8.8

# qemu-system-x86_64 -cpu ? | grep Rome
x86 EPYC-Rome (alias configured by machine type)  
x86 EPYC-Rome-v1  AMD EPYC-Rome Processor

# virsh domcapabilities

  EPYC-Rome
  AMD
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


New:
# qemu-system-x86_64 -cpu ? | grep Rome
x86 EPYC-Rome (alias configured by machine type)  
x86 EPYC-Rome-v1  AMD EPYC-Rome Processor 
x86 EPYC-Rome-v2  AMD EPYC-Rome Processor

# virsh domcapabilities

  EPYC-Rome
  AMD
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


Instance with ibrs flag can now be run

processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 23
model   : 49
model name  : AMD EPYC-Rome Processor
stepping: 0
microcode   : 0x165
cpu MHz : 2495.312
cache size  : 512 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm rep_good nopl cpuid extd_apicid tsc_known_freq pni pclmulqdq ssse3 
fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor 
lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw 
topoext perfctr_core ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 
rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves clzero 
xsaveerptr wbnoinvd arat npt nrip_save umip rdpid
bugs: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass
bogomips: 4990.62
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:


Migration of guest (e.g. with EPYC-IBPB or EPYC-Rome) from previous version to 
proposed still works.

Migration of guest (EPYC-Rome with ibrs) to previous version doesn't (as
expected)

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921754

Title:
  Add missing cpu feature bits in EPYC-Rome model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921754/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922907] Re: Unable to use Skylake capability on Cascadelake server

Testing before with libvirt 6.0.0-0ubuntu8.8 on Xeon 6130 (Skylake):


  Cascadelake-Server
  Intel
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


With 6.0.0-0ubuntu8.9


  Skylake-Server-IBRS
  Intel
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


On Xeon 5218 (CascadeLake)

Before/After (no change):


  Cascadelake-Server
  Intel
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922907

Title:
  Unable to use Skylake capability on Cascadelake server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1922907/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921880] Re: Add EPYC-Milan model

Before state as in LP#1921754  (linux 5.11.0-16-generic, qemu 1:5.2
+dfsg-9ubuntu2, libvirt 7.0.0-2ubuntu1)

With proposed:

# qemu-system-x86_64 -cpu ? | grep EPYC-Milan
x86 EPYC-Milan(alias configured by machine type)

x86 EPYC-Milan-v1 AMD EPYC-Milan Processor

# virsh domcapabilities
...

  EPYC-Milan
  AMD
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

...


Launching a guest with with EPYC-Milan works:

# cat /proc/cpuinfo 
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 25
model   : 1
model name  : AMD EPYC-Milan Processor
stepping: 1
microcode   : 0x165
cpu MHz : 2445.404
cache size  : 512 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm rep_good nopl cpuid extd_apicid tsc_known_freq pni pclmulqdq ssse3 
fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand 
hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 
3dnowprefetch osvw topoext perfctr_core invpcid_single ssbd ibrs ibpb stibp 
vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt 
clwb sha_ni xsaveopt xsavec xgetbv1 xsaves clzero xsaveerptr wbnoinvd arat npt 
nrip_save umip pku ospke rdpid fsrm
bugs: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass
bogomips: 4890.80
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:


** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921880

Title:
  Add EPYC-Milan model

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1921880/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921754] Re: Add missing cpu feature bits in EPYC-Rome model