[Bug 1912509] Re: usci_acpi USBC000:00: PPM init failed (-110)

2022-01-31 Thread Petronel MALUTAN
It happens sometimes to 
https://www.cel.ro/laptop-laptopuri/laptop-gaming-asus-tuf-f15-fx506he-intel-core-11th-gen-i7-11800h-512gb-ssd-8gb-geforce-rtx-3050-ti-4gb-fullhd-endless-rgb-eclipse-gray-pNSExPD0pMA-l/
with Ubuntu 20.04 clean install.

No options under boot to disable Intel graphics... Not played yet to
disconnect HDMI and reconnect after, as it happens sometimes and don't
plan to connect few times per day the hdmi yet.

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

Title:
  usci_acpi USBC000:00: PPM init failed (-110)

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


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

Re: [Bug 1959629] [NEW] lintian hangs during a debuild or sbuild

2022-01-31 Thread fossfreedom
About half an hour before I gave up. Previously that stage took about 10
seconds

On Mon, 31 Jan 2022, 23:30 Mattia Rizzolo, <1959...@bugs.launchpad.net>
wrote:

> Mind specifying how long you've waited on the lintian stage before claiming
> that it "never finishes"?
>
> On Tue, 1 Feb 2022, 12:10 am fossfreedom, <1959...@bugs.launchpad.net>
> wrote:
>
> > Public bug reported:
> >
> > Uplifting to the latest lintian on jammy
> >
> > a debuild -S -k0xkey on a package, the debuild never finishes - it gets
> > stuck at the lintian stage.
> >
> > I have to downgrade lintian to the previous version from impish
> >
> > Similarly, running a sbuild on any package, lintian never finishes if I
> > include lintian checks
> >
> > Now I have to workaround via sbuild -d jammy --no-run-lintian
> >
> > my ~/.sbuildrc is
> >
> > # Name to use as override in .changes files for the Maintainer: field
> > # (mandatory, no default!).
> > $maintainer_name='x ';
> >
> > # Default distribution to build.
> > $distribution = "jammy";
> > # Build arch-all by default.
> > $build_arch_all = 1;
> >
> > # When to purge the build directory afterwards; possible values are
> > "never",
> > # "successful", and "always".  "always" is the default. It can be helpful
> > # to preserve failing builds for debugging purposes.  Switch these
> comments
> > # if you want to preserve even successful builds, and then use
> > # "schroot -e --all-sessions" to clean them up manually.
> > $purge_build_directory = 'successful';
> > $purge_session = 'successful';
> > $purge_build_deps = 'successful';
> > # $purge_build_directory = 'never';
> > # $purge_session = 'never';
> > # $purge_build_deps = 'never';
> >
> > # Directory for writing build logs to
> > $log_dir=$ENV{HOME}."/ubuntu/logs";
> > $run_lintian = 1;
> > $lintian_opts = ['-i', '-I', '--pedantic'];
> >
> > # don't remove this, Perl needs it:
> > 1;
> >
> > All jammy sbuilds have worked before the latest lintian was released.
> >
> > Thoughts as to what is the issue here?
> >
> > ProblemType: Bug
> > DistroRelease: Ubuntu 22.04
> > Package: lintian 2.111.0ubuntu3
> > ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
> > Uname: Linux 5.15.0-18-generic x86_64
> > ApportVersion: 2.20.11-0ubuntu76
> > Architecture: amd64
> > CasperMD5CheckResult: pass
> > CurrentDesktop: Budgie:GNOME
> > Date: Mon Jan 31 22:56:57 2022
> > InstallationDate: Installed on 2022-01-29 (2 days ago)
> > InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha
> amd64
> > (20220129)
> > PackageArchitecture: all
> > SourcePackage: lintian
> > UpgradeStatus: No upgrade log present (probably fresh install)
> >
> > ** Affects: lintian (Ubuntu)
> >  Importance: Undecided
> >  Status: New
> >
> >
> > ** Tags: amd64 apport-bug jammy
> >
> > --
> > You received this bug notification because you are subscribed to Ubuntu.
> > https://bugs.launchpad.net/bugs/1959629
> >
> > Title:
> >   lintian hangs during a debuild or sbuild
> >
> > Status in lintian package in Ubuntu:
> >   New
> >
> > Bug description:
> >   Uplifting to the latest lintian on jammy
> >
> >   a debuild -S -k0xkey on a package, the debuild never finishes - it
> >   gets stuck at the lintian stage.
> >
> >   I have to downgrade lintian to the previous version from impish
> >
> >   Similarly, running a sbuild on any package, lintian never finishes if
> >   I include lintian checks
> >
> >   Now I have to workaround via sbuild -d jammy --no-run-lintian
> >
> >   my ~/.sbuildrc is
> >
> >   # Name to use as override in .changes files for the Maintainer: field
> >   # (mandatory, no default!).
> >   $maintainer_name='x ';
> >
> >   # Default distribution to build.
> >   $distribution = "jammy";
> >   # Build arch-all by default.
> >   $build_arch_all = 1;
> >
> >   # When to purge the build directory afterwards; possible values are
> > "never",
> >   # "successful", and "always".  "always" is the default. It can be
> helpful
> >   # to preserve failing builds for debugging purposes.  Switch these
> > comments
> >   # if you want to preserve even successful builds, and then use
> >   # "schroot -e --all-sessions" to clean them up manually.
> >   $purge_build_directory = 'successful';
> >   $purge_session = 'successful';
> >   $purge_build_deps = 'successful';
> >   # $purge_build_directory = 'never';
> >   # $purge_session = 'never';
> >   # $purge_build_deps = 'never';
> >
> >   # Directory for writing build logs to
> >   $log_dir=$ENV{HOME}."/ubuntu/logs";
> >   $run_lintian = 1;
> >   $lintian_opts = ['-i', '-I', '--pedantic'];
> >
> >   # don't remove this, Perl needs it:
> >   1;
> >
> >   All jammy sbuilds have worked before the latest lintian was released.
> >
> >   Thoughts as to what is the issue here?
> >
> >   ProblemType: Bug
> >   DistroRelease: Ubuntu 22.04
> >   Package: lintian 2.111.0ubuntu3
> >   ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
> >   Uname: Linux 5.15.0-18-generic x86_64
> >   ApportVersion: 2.20

[Bug 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions

2022-01-31 Thread Jonatan Zeidler
** Changed in: systemd
   Status: New => Confirmed

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

Title:
  On laptops, screen brightness and keyboard backlight isn't memorized
  between sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1270579/+subscriptions


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

[Bug 1959652] Re: [regression] Jammy reboot/shutdown hangs for several minutes

2022-01-31 Thread Daniel van Vugt
Kernel 5.15.0-17-generic has the same hang. Also has the same crash in
snd_soc_hdac_hda on startup.

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

Title:
  [regression] Jammy reboot/shutdown hangs for several minutes

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


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

[Bug 1959652] Re: [regression] Jammy shutdown hangs for several minutes

2022-01-31 Thread Daniel van Vugt
Maybe the kernel module crash is relevant:

[4.742767] CPU: 8 PID: 1034 Comm: pipewire-media- Not tainted 
5.15.0-18-generic #18-Ubuntu
[4.742769] Hardware name: Intel(R) Client Systems NUC9i7QNX/NUC9i7QNB, BIOS 
QXCFL579.0034.2019.1125.1436 11/25/2019
[4.742770] RIP: 0010:0x0
[4.742773] Code: Unable to access opcode bytes at RIP 0xffd6.
[4.742774] RSP: 0018:bc1f818e3938 EFLAGS: 00010202
[4.742775] RAX:  RBX: 9d8992559a00 RCX: 0007
[4.742777] RDX: 9d8989d66a00 RSI: 9d8994df4828 RDI: 9d8992559a60
[4.742778] RBP: bc1f818e3960 R08: 006c R09: 9d898d454a57
[4.742779] R10: 0007 R11: c04fb59c R12: 9d8989d66a00
[4.742779] R13: 0001 R14: 9d8994df4828 R15: 0001
[4.742780] FS:  7f39381ee7c0() GS:9d9120e0() 
knlGS:
[4.742782] CS:  0010 DS:  ES:  CR0: 80050033
[4.742783] CR2: ffd6 CR3: 000106044001 CR4: 003706e0
[4.742784] Call Trace:
[4.742786]  
[4.742788]  hdac_hda_dai_open+0x82/0xc0 [snd_soc_hdac_hda]
[4.742791]  snd_soc_dai_startup+0x37/0x70 [snd_soc_core]
[4.742805]  ? snd_soc_component_module_get+0x48/0x60 [snd_soc_core]
...

** Summary changed:

- [regression] Jammy shutdown hangs for several minutes
+ [regression] Jammy reboot/shutdown hangs for several minutes

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

Title:
  [regression] Jammy reboot/shutdown hangs for several minutes

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


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

[Bug 1959652] [NEW] [regression] Jammy reboot/shutdown hangs for several minutes

2022-01-31 Thread Daniel van Vugt
Public bug reported:

Starting a few days ago, my jammy desktop hangs for several minutes when
trying to reboot or shut down. The console always seems to report the
problem is:

  systemd-shutdown[1]: Waiting for process pulseaudio

Followed by repeated SIGTERM and SIGKILL retries. Although the system
log (journalctl -b-1) does not seem to show the same kernel messages or
show the same multi-minute delay that I suffer every time.

It seems unlikely pulseaudio is actually the cause since that's been
unchanged for months. More likely a kernel or systemd change, both of
which received updates in the past few days.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-18-generic 5.15.0-18.18
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
Date: Tue Feb  1 14:19:43 2022
InstallationDate: Installed on 2021-11-05 (87 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
MachineType: Intel(R) Client Systems NUC9i7QNX
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-18-generic N/A
 linux-backports-modules-5.15.0-18-generic  N/A
 linux-firmware 20220124.git0c6a7b3b-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/25/2019
dmi.bios.release: 5.13
dmi.bios.vendor: Intel Corp.
dmi.bios.version: QXCFL579.0034.2019.1125.1436
dmi.board.name: NUC9i7QNB
dmi.board.vendor: Intel Corporation
dmi.board.version: K49245-402
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 24.33
dmi.modalias: 
dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX:
dmi.product.family: QN
dmi.product.name: NUC9i7QNX
dmi.product.sku: BXNUC9i7QNX
dmi.product.version: K49244-403
dmi.sys.vendor: Intel(R) Client Systems

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

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


** Tags: amd64 apport-bug jammy performance regression-release

** Also 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/1959652

Title:
  [regression] Jammy reboot/shutdown hangs for several minutes

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


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

[Bug 1959605] Re: Install fail onto USB

2022-01-31 Thread Chris Guiver
Thank you for taking the time to report this issue and helping to make
Ubuntu better.

This installation looks like it was caused by a corrupted file system,
or device problems (sdb5). I notice in the logs

Jan 31 16:59:12 ubuntu kernel: [ 5700.165980] EXT4-fs error (device sdb5): 
ext4_lookup:1697: inode #278331: comm dpkg: iget: checksum invalid
Jan 31 16:59:12 ubuntu kernel: [ 5700.165987] Aborting journal on device sdb5-8.
Jan 31 16:59:13 ubuntu ubiquity: dpkg: error processing package 
libreoffice-common (--remove):#015
Jan 31 16:59:13 ubuntu ubiquity:  cannot remove 
'/target/usr/share/icons/hicolor/scalable/apps/libreoffice-writer.svg': 
Read-only file system#015
Jan 31 16:59:13 ubuntu ubiquity: dpkg: too many errors, stopping#015
Jan 31 16:59:13 ubuntu ubiquity: dpkg: error: unable to create new file 
'/target//var/lib/dpkg/status-new': Read-only file system#015
Jan 31 16:59:13 ubuntu kernel: [ 5700.822899] EXT4-fs (sdb5): Remounting 
filesystem read-only

I've marked this bug as incomplete (due hardware issues), if you believe
I'm in error please leave a comment as to why, and you can return the
status to "New".

I suggest you validate the health of your hardware (esp. disk by
checking it's SMART status using `smartctl`, `gnome-disks` or whichever
tool you prefer), and possibly the integrity of your partition table. If
you're unfamiliar with these, I suggest seeking looking up  refer to
https://discourse.ubuntu.com/t/finding-help/709  Note: USB media is
usually built to price; so doesn't include error checking like SMART

** Changed in: ubiquity (Ubuntu)
   Status: New => Incomplete

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

Title:
  Install fail onto USB

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


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

[Bug 1959651] [NEW] package munge 0.5.13-2build1 failed to install/upgrade: installed munge package post-installation script subprocess returned error exit status 1

2022-01-31 Thread Ahsan
Public bug reported:

i have uninstalled munge, during installation again, found the bug.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: munge 0.5.13-2build1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
AptOrdering:
 libmunge2:amd64: Install
 munge:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Feb  1 10:52:12 2022
ErrorMessage: installed munge package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2022-01-27 (4 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
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: munge
Title: package munge 0.5.13-2build1 failed to install/upgrade: installed munge 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package munge 0.5.13-2build1 failed to install/upgrade: installed
  munge package post-installation script subprocess returned error exit
  status 1

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


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

[Bug 1958320] Re: Prompt user to attach machine to Ubuntu Advantage

2022-01-31 Thread Launchpad Bug Tracker
This bug was fixed in the package update-notifier - 3.192.48

---
update-notifier (3.192.48) jammy; urgency=medium

  * Add Ubuntu Pro notifications (LP: #1958320)

 -- Robert Ancell   Tue, 01 Feb 2022
14:47:17 +1300

** Changed in: update-notifier (Ubuntu Jammy)
   Status: In Progress => Fix Released

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

Title:
  Prompt user to attach machine to Ubuntu Advantage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1958320/+subscriptions


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

[Bug 1917347] Re: Qterminal "Start with preset" settings have no effect.

2022-01-31 Thread Leó Kolbeinsson
** Tags added: focal jammy

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

Title:
  Qterminal "Start with preset" settings have no effect.

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


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

[Bug 1958283] Re: linux-firmware missing renoir_ta

2022-01-31 Thread Marius Meisenzahl
I downloaded and installed 1.187.26 via browser. I can also confirm that
it fixes the problem.

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

Title:
  linux-firmware missing renoir_ta

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


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

[Bug 1959649] [NEW] BlueFS spillover detected for particular OSDs

2022-01-31 Thread nikhil kshirsagar
Public bug reported:

This is an issue described in https://tracker.ceph.com/issues/38745,
where ceph health details shows messages like,

sudo ceph health detail
HEALTH_WARN 3 OSD(s) experiencing BlueFS spillover; mon juju-6879b7-6-lxd-1 is 
low on available space
[WRN] BLUEFS_SPILLOVER: 3 OSD(s) experiencing BlueFS spillover <---
osd.41 spilled over 66 MiB metadata from 'db' device (3.0 GiB used of 29 GiB) 
to slow device
osd.96 spilled over 461 MiB metadata from 'db' device (3.0 GiB used of 29 GiB) 
to slow device
osd.105 spilled over 198 MiB metadata from 'db' device (3.0 GiB used of 29 GiB) 
to slow device

The bluefs spillover is very likely caused because of the rocksdb's
level-sized issue.

https://docs.ceph.com/en/latest/rados/configuration/bluestore-config-
ref/#sizing has a statement about this leveled sizing.

Between versions 15.2.6 and 15.2.10 , if the value of
bluestore_volume_selection_policy is not set to use_some_extra, this
issue can be faced inspite of free space available, due to the fact that
RocksDB only uses "leveled" space on the NVME partition. The values are
set to be 300MB, 3GB, 30GB and 300GB. Every DB space above such a limit
will automatically end up on slow devices.

There is also a discussion at www.mail-archive.com/ceph-
us...@ceph.io/msg05782.html

Running compaction on the database, i.e ceph tell osd.XX compact
(replace XX with the OSD number) can work around the issue, but the best
fix is to either,

I am also pasting some notes Dongdong mentions on SF case 00326782,
where the fix is to either,

A. Redeploy the OSDs with a larger DB lvm/partition.

OR

B. Migrate to a new larger DB lvm/partition, this can be done offline
with ceph-volume lvm migrate, please refer to
https://docs.ceph.com/en/octopus/ceph-volume/lvm/migrate/ but it
requires to upgrade the cluster to 15.2.14 first.

A will be much safer, but more time-consuming. B will be much faster,
but its recommended to do it on one node first and wait/monitoring for a
couple of weeks before moving forward.

As mentioned above, to avoid running into the issue even with free space
available, the value of bluestore_volume_selection_policy should be set
to use_some_extra for all OSDs. 15.2.6 has
bluestore_volume_selection_policy but the default was only set to
use_some_extra 15.2.11 onwards. (https://tracker.ceph.com/issues/47053)

** Affects: ceph (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/1959649

Title:
  BlueFS spillover detected for particular OSDs

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


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

[Bug 1952976] Re: gnome fails to respond

2022-01-31 Thread Daniel van Vugt
Please try disabling all extensions in the Extensions app, even the
Ubuntu ones, and then log in again. Does the bug still occur?

** Changed in: ubuntu
   Status: Expired => Incomplete

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

Title:
  gnome fails to respond

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


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

[Bug 1927808] Re: rtw88_8821ce causes freeze

2022-01-31 Thread Paul Szabo
May I (should I) change status "Fix released" to "Confirmed"?

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

Title:
  rtw88_8821ce causes freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1927808/+subscriptions


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

[Bug 1959646] [NEW] dhcrelay does not obey -i interface option

2022-01-31 Thread Jens Elkner
Public bug reported:

If one starts dhcrelay with explicitly specifying the interfaces to
listen,it silently ignores these options and still listens on all
interfaces. This is neither what the man page says (it says, only if no
interface is given, it listen on all interfaces), nor what is needed. It
might be even considered being a security bug because dhcrelay listens
on interfaces it shouldn't. Needless filter work causes unwanted
overhead as well.

Wrt. the source package the patches/dhcrelay-listen.patch seems to be
the root cause. It makes no sense at all to me ... Please explain or
remove.

** Affects: isc-dhcp (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/1959646

Title:
  dhcrelay does not obey -i interface option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1959646/+subscriptions


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

[Bug 1927808] Re: rtw88_8821ce causes freeze

2022-01-31 Thread Paul Szabo
Sorry spoke too soon! Just after my message, my laptop froze.
The issue is not fixed on my machine (as per Comment#59).
Since I am the "original poster" or reporter of this bug,
maybe it should NOT be marked 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/1927808

Title:
  rtw88_8821ce causes freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1927808/+subscriptions


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

[Bug 1927808] Re: rtw88_8821ce causes freeze

2022-01-31 Thread Paul Szabo
Thanks! 5.13.0-28-generic seems to work fine 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/1927808

Title:
  rtw88_8821ce causes freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1927808/+subscriptions


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

[Bug 1948591] Re: package flash-kernel 3.103ubuntu1~20.10.1 failed to install/upgrade: installed flash-kernel package post-installation script subprocess returned error exit status 1

2022-01-31 Thread Launchpad Bug Tracker
[Expired for flash-kernel (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: flash-kernel (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package flash-kernel 3.103ubuntu1~20.10.1 failed to install/upgrade:
  installed flash-kernel package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1948591/+subscriptions


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

[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy

2022-01-31 Thread gregrwm
i made the jump to manjaro.  rolling release, yay!  and ipsec/xl2tpd
just works.

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

Title:
  xl2tpd "Can not find tunnel" in jammy

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


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

[Bug 1952976] Re: gnome fails to respond

2022-01-31 Thread Launchpad Bug Tracker
[Expired for Ubuntu because there has been no activity for 60 days.]

** Changed in: ubuntu
   Status: Incomplete => Expired

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

Title:
  gnome fails to respond

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


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

[Bug 1953080] Re: mouse click is delaying and sometimes don't work

2022-01-31 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  mouse click is delaying and sometimes don't work

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


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

[Bug 1959643] [NEW] I was installing the OS through live USB and got this error

2022-01-31 Thread Ahmed
Public bug reported:

I was installing UBUNTU 20 and the error popped up and the installation
was interrupted. Now I'm not sure how to do the installation. By the way
I had an older version (Actually the same version but corrupted) and I
was trying to have a fresh newly installed operating system

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.17
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb  1 07:09:34 2022
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu

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

Title:
  I was installing the OS through live USB and got this error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1959643/+subscriptions


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

[Bug 1895404] Re: marco crashed with SIGSEGV in meta_display_list_windows()

2022-01-31 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1895404

** Tags added: iso-testing

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

Title:
  marco crashed with SIGSEGV in meta_display_list_windows()

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


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

[Bug 1895465] Re: floaters crashed with signal 5 in _XEventsQueued()

2022-01-31 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1895465

** Tags added: iso-testing

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

Title:
  floaters crashed with signal 5 in _XEventsQueued()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-screensaver/+bug/1895465/+subscriptions


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

[Bug 1895466] Re: wnck-applet crashed with signal 5 in _XReply()

2022-01-31 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1895466

** Tags added: iso-testing

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

Title:
  wnck-applet crashed with signal 5 in _XReply()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1895466/+subscriptions


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

[Bug 1836938] Re: falkon failed to load some pages

2022-01-31 Thread Chris Guiver
Thank you for reporting this bug to Ubuntu.

Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.


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

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

Title:
  falkon failed to load some pages

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


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

[Bug 1850771] Re: Falkon is broken in 19.10

2022-01-31 Thread Chris Guiver
*** This bug is a duplicate of bug 1836938 ***
https://bugs.launchpad.net/bugs/1836938

** This bug has been marked a duplicate of bug 1836938
   falkon failed to load some pages

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

Title:
  Falkon is broken in 19.10

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


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

[Bug 1836938] Re: falkon failed to load some pages

2022-01-31 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: falkon (Ubuntu)
   Status: New => Confirmed

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

Title:
  falkon failed to load some pages

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


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

Re: [Bug 1959639] [NEW] Running autopkgtest in lxc crashes host's ntp

2022-01-31 Thread Scott Kitterman
On Monday, January 31, 2022 9:51:59 PM EST Bryce Harrington wrote:

> Comparing the build log from 3.6.3 with the autopkgtest log for 3.6.4,
> these lines jump out at me:
> 
> ### 3.6.3 ###
> 
>   install -m644 debian/postfix.insserv.conf
> debian/postfix/etc/insserv.conf.d/postfix txt2man -t postfix-collate -r
> postfix-3.6.3 -d  -s 1 auxiliary/collate/README >
> debian/postfix/usr/share/man/man1/postfix-collate.1 expand: 1: No such file
> or directory
>   install man/man1/*.1 debian/postfix/usr/share/man/man1
> 
> ### 3.6.4 ###
> 
>   install -m644 debian/postfix.insserv.conf
> debian/postfix/etc/insserv.conf.d/postfix txt2man -t postfix-collate -r
> postfix-3.6.4 -d 'Mon Jan 31 09:42:30 PM UTC 2022' -s 1
> auxiliary/collate/README >
> debian/postfix/usr/share/man/man1/postfix-collate.1 install man/man1/*.1
> debian/postfix/usr/share/man/man1

This was due to a quoting error in debian/rules in 3.6.3.  What's being 
expanded there is:

'$(shell date -s @$(SOURCE_DATE_EPOCH))'

Nothing to do with NTP.

Scott K

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

Title:
  Running autopkgtest in lxc crashes host's ntp

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


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

[Bug 1959599] Re: gnome-shell freezes upon trying to login

2022-01-31 Thread Daniel van Vugt
Those log messages appear to be bug 1951786 / bug 1949352 which has a
fix in proposed. I don't think that explains any freezes but you should
probably try that first:

  https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/70~ubuntu3.21.10.1

If that doesn't fix the problem then next try disabling everything in
the Extensions app. Then log in again.

If that doesn't fix the problem then please run this command to collect
more information:

  apport-collect 1959599

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome-shell freezes upon trying to login

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


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

[Bug 1940916] Re: Incorrectly excludes tmpfs filesystems

2022-01-31 Thread Bryce Harrington
** Also affects: percona-monitoring-plugins
   Importance: Undecided
   Status: New

** No longer affects: percona-monitoring-plugins

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

Title:
  Incorrectly excludes tmpfs filesystems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940916/+subscriptions


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

[Bug 1959596] Re: Applications end up in session scope, rather than per .desktop scope

2022-01-31 Thread Daniel van Vugt
This might also explain why Chrome's log messages are prefixed as gnome-
shell...

Regardless, please report the issue to gnome-shell at:
https://gitlab.gnome.org/GNOME/gnome-shell/issues

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

Title:
  Applications end up in session scope, rather than per .desktop scope

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


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

[Bug 1959599] Re: gnome-shell freezes upon trying to login

2022-01-31 Thread Daniel van Vugt
** Tags added: impish

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

Title:
  gnome-shell freezes upon trying to login

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


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

[Bug 1959639] [NEW] Running autopkgtest in lxc crashes host's ntp

2022-01-31 Thread Bryce Harrington
Public bug reported:

When running autopkgtest in a lxc container against postfix 3.6.4, it
does something that causes the host's ntp service to segfault and to
reset the system time to an earlier time.  I haven't determined if the
former causes the latter, or vice versa.

  sudo autopkgtest ../postfix_3.6.4-1ubuntu1.dsc -- null

Restarting ntp on the host is sufficient to get things back in order.
Then re-running autopkgtest reproduces the failure exactly - the time is
set again to the same time that it did before.

  sudo systemctl restart ntp

Interestingly, if I rebuild the package, then run autopkgtest, it resets
to a different time (but always that specific time).  I suspect there is
something in the build setting the system time to a date related to
either the changelog date, or the date of some artifact produced during
the build (the .dsc file?)

From watching the log and the clock, the time reset appears to occur not
during the actual test case runs but rather during the packaging,
specifically somewhere between dh_prep and dh_compress.

I have not yet been able to reproduce this behavior using postfix 3.6.3
built from .dsc, nor postfix 3.6.3 using binaries from the main archive.

Comparing the build log from 3.6.3 with the autopkgtest log for 3.6.4,
these lines jump out at me:

### 3.6.3 ###

  install -m644 debian/postfix.insserv.conf 
debian/postfix/etc/insserv.conf.d/postfix
txt2man -t postfix-collate -r postfix-3.6.3 -d  -s 1 auxiliary/collate/README > 
debian/postfix/usr/share/man/man1/postfix-collate.1
  expand: 1: No such file or directory
  install man/man1/*.1 debian/postfix/usr/share/man/man1

### 3.6.4 ###

  install -m644 debian/postfix.insserv.conf 
debian/postfix/etc/insserv.conf.d/postfix
  txt2man -t postfix-collate -r postfix-3.6.4 -d 'Mon Jan 31 09:42:30 PM UTC 
2022' -s 1 auxiliary/collate/README > 
debian/postfix/usr/share/man/man1/postfix-collate.1
  install man/man1/*.1 debian/postfix/usr/share/man/man1


The date shown in the latter log snippet is the incorrect date.

The clock running (on the host) during the build showed the following:

  $ while : ; do date; sleep 1; done
  ...
  Mon 31 Jan 2022 06:40:48 PM PST
  Mon 31 Jan 2022 06:40:49 PM PST
  Mon 31 Jan 2022 06:40:50 PM PST
  Mon 31 Jan 2022 06:40:51 PM PST
  Mon 31 Jan 2022 01:42:30 PM PST
  Mon 31 Jan 2022 01:42:31 PM PST
  Mon 31 Jan 2022 01:42:32 PM PST
  Mon 31 Jan 2022 01:42:33 PM PST
  Mon 31 Jan 2022 01:42:34 PM PST

** Affects: postfix (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/1959639

Title:
  Running autopkgtest in lxc crashes host's ntp

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


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

[Bug 1930567] Re: Popup menus don't appear at all if opened close to inter-monitor boundaries in Wayland sessions

2022-01-31 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu)
   Status: Triaged => Fix Committed

** Tags added: fixed-in-42.0 fixed-upstream

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

Title:
  Popup menus don't appear at all if opened close to inter-monitor
  boundaries in Wayland sessions

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


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

[Bug 1959507] Re: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)

2022-01-31 Thread Daniel van Vugt
Looks like this crash has been fixed twice in the past:

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2957
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4522

but all those fixes are in gnome-shell 41 already. So we need a new fix.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2957
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2957

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4522
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4522

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

Title:
  gnome-shell crashed in clutter_actor_get_real_resource_scale() with
  assertion failed: (guessed_scale >= 1.f)

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


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

[Bug 1959507] Re: gnome-shell crashed with SIGABRT in __pthread_kill_implementation()

2022-01-31 Thread Daniel van Vugt
** This bug is no longer a duplicate of bug 1871262
   gnome-shell freezes/crashes with meta_window_set_stack_position_no_sync: 
assertion 'window->stack_position >= 0' failed

** Summary changed:

- gnome-shell crashed with SIGABRT in __pthread_kill_implementation()
+ gnome-shell crashed with assertion failed: (guessed_scale >= 1.f)

** Summary changed:

- gnome-shell crashed with assertion failed: (guessed_scale >= 1.f)
+ gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion 
failed: (guessed_scale >= 1.f)

** Information type changed from Private to Public

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

Title:
  gnome-shell crashed in clutter_actor_get_real_resource_scale() with
  assertion failed: (guessed_scale >= 1.f)

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


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

[Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

2022-01-31 Thread Daniel van Vugt
Nvidia-470 has Wayland support if you add kernel parameter nvidia-
drm.modeset=1

Also the Nvidia web site (driver downloads) clarifies the difference
between the two current driver branches. Defaulting to 470 might still
be a good idea for LTS...

Production Branch (470):
Production Branch drivers provide ISV certification and optimal stability and 
performance for Unix customers. This driver is most commonly deployed at 
enterprises, providing support for the sustained bug fix and security updates 
commonly required.

New Feature Branch (495):
New Feature Branch drivers provide early adopters and bleeding edge developers 
access to the latest driver features before they are integrated into the 
Production Branches

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

Title:
  "Launch using dedicated graphics card" option absent (nvidia,
  proprietary drivers, on-demand PRIME mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1959362/+subscriptions


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

[Bug 1786013] Autopkgtest regression report (linux-meta/5.13.0.29.39)

2022-01-31 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-meta (5.13.0.29.39) for impish 
have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/248.3-1ubuntu8.2 (ppc64el, amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/impish/update_excuses.html#linux-meta

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

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


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

[Bug 1578954] Re: cron-apt package depends on cron package

2022-01-31 Thread Ken Sharp
** Tags added: bionic focal hirsute impish jammy

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

Title:
  cron-apt package depends on cron package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron-apt/+bug/1578954/+subscriptions


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

[Bug 1578954] Re: cron-apt package depends on cron package

2022-01-31 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: cron-apt (Ubuntu)
   Status: New => Confirmed

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

Title:
  cron-apt package depends on cron package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron-apt/+bug/1578954/+subscriptions


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

[Bug 1955047] Re: Nvidia drivers are marked as "auto" at installation and thus removed by `apt autoremove`

2022-01-31 Thread Brian Murray
I tested a daily install of Ubuntu 20.04 from 20220131 and no packages
are suggested for autoremoval and ubuntu-restricted-addons was installed
after the reboot. However, I didn't test with nvidia hardware so its
possible the bug in the original description still exists.

Additionally, Steve's point about this needing fixing in ubuntu-release-
upgrader might still apply in that systems that install from Ubuntu
20.04.3 media may have had packages autoremoved that should not have
been.

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

Title:
  Nvidia drivers are marked as "auto" at installation and thus removed
  by `apt autoremove`

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


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

[Bug 1959622] Re: FTBFS against openssl 3.0

2022-01-31 Thread Ubuntu Foundations Team Bug Bot
The attachment "hydra-1_9.2-1build1_9.2-1ubuntu1.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  FTBFS against openssl 3.0

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


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

[Bug 1956518] Re: linux-firmware 1.187.24 may crash USB ports

2022-01-31 Thread john crosbie
I am having similar issues.  Writing to an SDCard sometimes kills all
USB ports.  I can recover all USB ports by logging in over ssh and
running the following script:

for port in $(lspci | grep USB | cut -d' ' -f1); do
echo -n ":${port}"| sudo tee /sys/bus/pci/drivers/xhci_hcd/unbind;
sleep 5;
echo -n ":${port}" | sudo tee /sys/bus/pci/drivers/xhci_hcd/bind;
sleep 5;
done

This has happened 3 or 4 times in the last 2 weeks and each time I can
recover without reboot.

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

Title:
  linux-firmware 1.187.24 may crash USB ports

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


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

[Bug 1959592] Re: [needs-packaging] rpiboot

2022-01-31 Thread Brian Murray
*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu.  As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have Wishlist importance.  Subsequently, I'm
setting this bug's status to Wishlist.

** Changed in: ubuntu
   Importance: Undecided => Wishlist

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

Title:
  [needs-packaging] rpiboot

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


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

Re: [Bug 1959629] [NEW] lintian hangs during a debuild or sbuild

2022-01-31 Thread Mattia Rizzolo
Mind specifying how long you've waited on the lintian stage before claiming
that it "never finishes"?

On Tue, 1 Feb 2022, 12:10 am fossfreedom, <1959...@bugs.launchpad.net>
wrote:

> Public bug reported:
>
> Uplifting to the latest lintian on jammy
>
> a debuild -S -k0xkey on a package, the debuild never finishes - it gets
> stuck at the lintian stage.
>
> I have to downgrade lintian to the previous version from impish
>
> Similarly, running a sbuild on any package, lintian never finishes if I
> include lintian checks
>
> Now I have to workaround via sbuild -d jammy --no-run-lintian
>
> my ~/.sbuildrc is
>
> # Name to use as override in .changes files for the Maintainer: field
> # (mandatory, no default!).
> $maintainer_name='x ';
>
> # Default distribution to build.
> $distribution = "jammy";
> # Build arch-all by default.
> $build_arch_all = 1;
>
> # When to purge the build directory afterwards; possible values are
> "never",
> # "successful", and "always".  "always" is the default. It can be helpful
> # to preserve failing builds for debugging purposes.  Switch these comments
> # if you want to preserve even successful builds, and then use
> # "schroot -e --all-sessions" to clean them up manually.
> $purge_build_directory = 'successful';
> $purge_session = 'successful';
> $purge_build_deps = 'successful';
> # $purge_build_directory = 'never';
> # $purge_session = 'never';
> # $purge_build_deps = 'never';
>
> # Directory for writing build logs to
> $log_dir=$ENV{HOME}."/ubuntu/logs";
> $run_lintian = 1;
> $lintian_opts = ['-i', '-I', '--pedantic'];
>
> # don't remove this, Perl needs it:
> 1;
>
> All jammy sbuilds have worked before the latest lintian was released.
>
> Thoughts as to what is the issue here?
>
> ProblemType: Bug
> DistroRelease: Ubuntu 22.04
> Package: lintian 2.111.0ubuntu3
> ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
> Uname: Linux 5.15.0-18-generic x86_64
> ApportVersion: 2.20.11-0ubuntu76
> Architecture: amd64
> CasperMD5CheckResult: pass
> CurrentDesktop: Budgie:GNOME
> Date: Mon Jan 31 22:56:57 2022
> InstallationDate: Installed on 2022-01-29 (2 days ago)
> InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64
> (20220129)
> PackageArchitecture: all
> SourcePackage: lintian
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> ** Affects: lintian (Ubuntu)
>  Importance: Undecided
>  Status: New
>
>
> ** Tags: amd64 apport-bug jammy
>
> --
> You received this bug notification because you are subscribed to Ubuntu.
> https://bugs.launchpad.net/bugs/1959629
>
> Title:
>   lintian hangs during a debuild or sbuild
>
> Status in lintian package in Ubuntu:
>   New
>
> Bug description:
>   Uplifting to the latest lintian on jammy
>
>   a debuild -S -k0xkey on a package, the debuild never finishes - it
>   gets stuck at the lintian stage.
>
>   I have to downgrade lintian to the previous version from impish
>
>   Similarly, running a sbuild on any package, lintian never finishes if
>   I include lintian checks
>
>   Now I have to workaround via sbuild -d jammy --no-run-lintian
>
>   my ~/.sbuildrc is
>
>   # Name to use as override in .changes files for the Maintainer: field
>   # (mandatory, no default!).
>   $maintainer_name='x ';
>
>   # Default distribution to build.
>   $distribution = "jammy";
>   # Build arch-all by default.
>   $build_arch_all = 1;
>
>   # When to purge the build directory afterwards; possible values are
> "never",
>   # "successful", and "always".  "always" is the default. It can be helpful
>   # to preserve failing builds for debugging purposes.  Switch these
> comments
>   # if you want to preserve even successful builds, and then use
>   # "schroot -e --all-sessions" to clean them up manually.
>   $purge_build_directory = 'successful';
>   $purge_session = 'successful';
>   $purge_build_deps = 'successful';
>   # $purge_build_directory = 'never';
>   # $purge_session = 'never';
>   # $purge_build_deps = 'never';
>
>   # Directory for writing build logs to
>   $log_dir=$ENV{HOME}."/ubuntu/logs";
>   $run_lintian = 1;
>   $lintian_opts = ['-i', '-I', '--pedantic'];
>
>   # don't remove this, Perl needs it:
>   1;
>
>   All jammy sbuilds have worked before the latest lintian was released.
>
>   Thoughts as to what is the issue here?
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: lintian 2.111.0ubuntu3
>   ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
>   Uname: Linux 5.15.0-18-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu76
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: Budgie:GNOME
>   Date: Mon Jan 31 22:56:57 2022
>   InstallationDate: Installed on 2022-01-29 (2 days ago)
>   InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha
> amd64 (20220129)
>   PackageArchitecture: all
>   SourcePackage: lintian
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go t

[Bug 1959629] [NEW] lintian hangs during a debuild or sbuild

2022-01-31 Thread fossfreedom
Public bug reported:

Uplifting to the latest lintian on jammy

a debuild -S -k0xkey on a package, the debuild never finishes - it gets
stuck at the lintian stage.

I have to downgrade lintian to the previous version from impish

Similarly, running a sbuild on any package, lintian never finishes if I
include lintian checks

Now I have to workaround via sbuild -d jammy --no-run-lintian

my ~/.sbuildrc is

# Name to use as override in .changes files for the Maintainer: field
# (mandatory, no default!).
$maintainer_name='x ';

# Default distribution to build.
$distribution = "jammy";
# Build arch-all by default.
$build_arch_all = 1;

# When to purge the build directory afterwards; possible values are "never",
# "successful", and "always".  "always" is the default. It can be helpful
# to preserve failing builds for debugging purposes.  Switch these comments
# if you want to preserve even successful builds, and then use
# "schroot -e --all-sessions" to clean them up manually.
$purge_build_directory = 'successful';
$purge_session = 'successful';
$purge_build_deps = 'successful';
# $purge_build_directory = 'never';
# $purge_session = 'never';
# $purge_build_deps = 'never';

# Directory for writing build logs to
$log_dir=$ENV{HOME}."/ubuntu/logs";
$run_lintian = 1;
$lintian_opts = ['-i', '-I', '--pedantic'];

# don't remove this, Perl needs it:
1;

All jammy sbuilds have worked before the latest lintian was released.

Thoughts as to what is the issue here?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: lintian 2.111.0ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Budgie:GNOME
Date: Mon Jan 31 22:56:57 2022
InstallationDate: Installed on 2022-01-29 (2 days ago)
InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220129)
PackageArchitecture: all
SourcePackage: lintian
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  lintian hangs during a debuild or sbuild

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


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

[Bug 1959630] [NEW] provide 屏風 as a commandline alias for byobu

2022-01-31 Thread Steve Langasek
Public bug reported:

The etymology of byobu is Japanese, but the command on Ubuntu is
rendered in the Latin alphabet.  We should definitely have 屏風 as a
symlink!

** Affects: byobu (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/1959630

Title:
  provide 屏風 as a commandline alias for byobu

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


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

[Bug 1959628] Re: "require" behaves differently on ppc64el during certain conditions

2022-01-31 Thread Sergio Durigan Junior
This is impacting ruby-tilt, whose autopkgtest is failing on ppc64el
right now.  It's important to mention that Debian apparently isn't
impacted by this, which probably means that the error might be happen
somewhere else.

Note to self: glibc 2.34 doesn't ship with a separate libpthread
anymore, and load_lock eventually calls uses rb_thread_shield_wait,
which seems to make use of some pthread functions.

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

Title:
  "require" behaves differently on ppc64el during certain conditions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/1959628/+subscriptions


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

[Bug 1796047] Re: update-ieee-data throws error because of wrong url

2022-01-31 Thread Richard Laager
** Bug watch added: Debian Bug tracker #1004709
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004709

** Also affects: ieee-data (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004709
   Importance: Unknown
   Status: Unknown

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

Title:
  update-ieee-data throws error because of wrong url

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ieee-data/+bug/1796047/+subscriptions


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

[Bug 1959628] Re: "require" behaves differently on ppc64el during certain conditions

2022-01-31 Thread Sergio Durigan Junior
I debugged this a little bit and found that the difference manifests on
ruby3.0's load.c:require_internal, more specifically this part here:

1118 if (found) {
1119 if (!path || !(ftptr = load_lock(th->vm, RSTRING_PTR(path), 
warn))) {
1120 result = 0;
1121 }

On ppc64el, the call to "load_lock" fails for some reason.  On non-
ppc64el, the call succeeds and the function proceeds to successfully
load "bar".

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

Title:
  "require" behaves differently on ppc64el during certain conditions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/1959628/+subscriptions


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

[Bug 1959627] [NEW] Impish update: upstream stable patchset 2022-01-31

2022-01-31 Thread Kamal Mostafa
Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2022-01-31

Ported from the following upstream stable releases:
v5.10.91, v5.15.14

   from git://git.kernel.org/

selftests: x86: fix [-Wstringop-overread] warn in test_process_vm_readv()
tracing: Fix check for trace_percpu_buffer validity in get_trace_buf()
tracing: Tag trace_percpu_buffer as a percpu pointer
ieee802154: atusb: fix uninit value in atusb_set_extended_addr
i40e: Fix to not show opcode msg on unsuccessful VF MAC change
iavf: Fix limit of total number of queues to active queues of VF
RDMA/core: Don't infoleak GRH fields
netrom: fix copying in user data in nr_setsockopt
RDMA/uverbs: Check for null return of kmalloc_array
mac80211: initialize variable have_higher_than_11mbit
sfc: The RX page_ring is optional
i40e: fix use-after-free in i40e_sync_filters_subtask()
i40e: Fix for displaying message regarding NVM version
i40e: Fix incorrect netdev's real number of RX/TX queues
ftrace/samples: Add missing prototypes direct functions
ipv4: Check attribute length for RTA_GATEWAY in multipath route
ipv4: Check attribute length for RTA_FLOW in multipath route
ipv6: Check attribute length for RTA_GATEWAY in multipath route
ipv6: Check attribute length for RTA_GATEWAY when deleting multipath route
lwtunnel: Validate RTA_ENCAP_TYPE attribute length
batman-adv: mcast: don't send link-local multicast to mcast routers
sch_qfq: prevent shift-out-of-bounds in qfq_init_qdisc
net: ena: Fix undefined state when tx request id is out of bounds
net: ena: Fix error handling when calculating max IO queues number
power: supply: core: Break capacity loop
power: reset: ltc2952: Fix use of floating point literals
rndis_host: support Hytera digital radios
phonet: refcount leak in pep_sock_accep
power: bq25890: Enable continuous conversion for ADC at charging
ipv6: Continue processing multipath route even if gateway attribute is invalid
ipv6: Do cleanup if attribute validation fails in multipath route
usb: mtu3: fix interval value for intr and isoc
scsi: libiscsi: Fix UAF in iscsi_conn_get_param()/iscsi_conn_teardown()
ip6_vti: initialize __ip6_tnl_parm struct in vti6_siocdevprivate
net: udp: fix alignment problem in udp4_seq_show()
atlantic: Fix buff_ring OOB in aq_ring_rx_clean
mISDN: change function names to avoid conflicts
drm/amd/display: Added power down for DCN10
ipv6: raw: check passed optlen before reading
ARM: dts: gpio-ranges property is now required
Input: zinitix - make sure the IRQ is allocated before it gets enabled
fscache_cookie_enabled: check cookie is valid before accessing it
Revert "net: usb: r8152: Add MAC passthrough support for more Lenovo Docks"
mac80211: mesh: embedd mesh_paths and mpp_paths into ieee80211_if_mesh
selftests: net: udpgro_fwd.sh: explicitly checking the available ping feature
sctp: hold endpoint before calling cb in sctp_transport_lookup_process
net: ena: Fix wrong rx request id by resetting device
md/raid1: fix missing bitmap update w/o WriteMostly devices
cgroup: Use open-time credentials for process migraton perm checks
cgroup: Allocate cgroup_file_ctx for kernfs_open_file->priv
cgroup: Use open-time cgroup namespace for process migration perm checks
i2c: mpc: Avoid out of bounds memory access
net ticp:fix a kernel-infoleak in __tipc_sendmsg()
fbdev: fbmem: add a helper to determine if an aperture is used by a fw fb
drm/amdgpu: disable runpm if we are the primary adapter
auxdisplay: charlcd: checking for pointer reference before dereferencing
drm/amd/pm: Fix xgmi link control on aldebaran
drm/amd/pm: skip setting gfx cgpg in the s0ix suspend-resume
drm/amdgpu: always reset the asic in suspend (v2)
drm/amdgpu: put SMU into proper state on runpm suspending for BOCO capable 
platform
userfaultfd/selftests: fix hugetlb area allocations
UBUNTU: upstream stable to v5.10.91, v5.15.14

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

** Affects: linux (Ubuntu Impish)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Impish)
   Status: New => In Progress

** Changed in: linux (Ubuntu Impish)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Impish)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

[Bug 1959628] [NEW] "require" behaves differently on ppc64el during certain conditions

2022-01-31 Thread Sergio Durigan Junior
Public bug reported:

I have verified that under specific circumstances, 'require' can behave
differently between ppc64el and other architectures.

Simple reproducer:

$ cat > foo.rb << __EOF__
begin
  require 'bar'
rescue LoadError
  puts "Caught first LoadError.  Continuing..."
end

puts require 'bar'
__EOF__
$ cat > bar.rb << __EOF__
require 'baz'
__EOF__
$ ruby3.0 -I . foo.rb

On ppc64el, you will see:

Caught first LoadError.  Continuing...
false

On non-ppc64el, you will see:

Caught first LoadError.  Continuing...
:86:in 
`require': cannot load such file -- baz (LoadError)
Did you mean?  bar
from 
:86:in 
`require'
from /home/ubuntu/bar.rb:1:in `'
from 
:86:in 
`require'
from 
:86:in 
`require'
from foo.rb:7:in `'

** Affects: ruby3.0 (Ubuntu)
 Importance: High
 Status: Confirmed

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

Title:
  "require" behaves differently on ppc64el during certain conditions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/1959628/+subscriptions


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

[Bug 1959508] Re: Proposal to include exiv2 0.27.5 in Ubuntu 22.04 LTS

2022-01-31 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: exiv2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Proposal to include exiv2 0.27.5 in Ubuntu 22.04 LTS

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


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

[Bug 1959622] Re: FTBFS against openssl 3.0

2022-01-31 Thread Bug Watch Updater
** Changed in: hydra (Debian)
   Status: Unknown => New

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

Title:
  FTBFS against openssl 3.0

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


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

[Bug 1959625] Re: barbican autopkgtests fail with python3.10

2022-01-31 Thread Steve Langasek
*** This bug is a duplicate of bug 1959626 ***
https://bugs.launchpad.net/bugs/1959626

** This bug has been marked a duplicate of bug 1959626
   barbican autopkgtests fail with python3.10

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

Title:
  barbican autopkgtests fail with python3.10

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


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

[Bug 1959626] Re: barbican autopkgtests fail with python3.10

2022-01-31 Thread Steve Langasek
Ok restarting only barbican-worker with python3.10 doesn't fail; it
fails only after restarting apache2 with python3.10...

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

Title:
  barbican autopkgtests fail with python3.10

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


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

[Bug 1959592] Re: [needs-packaging] rpiboot

2022-01-31 Thread Dave Jones
** Description changed:

  The rpiboot utility in RaspiOS is required for working with the
  Raspberry Pi Compute Module boards, contains firmware required to
  recover from a corrupted flash, and utilities necessary for working with
  the new secure boot mode available on the CM4, 4B and 400 (certain board
  revisions of the latter two).
  
  URL: https://github.com/raspberrypi/usbboot
  License: Apache-2.0 (the rpiboot utility itself) and proprietary (included 
firmwares)
  Notes:
  
  Due to the included firmwares being closed source and proprietary
  licensed, this package would need to go into multiverse. The only
  dependency is a build-time dependency on libusb-1.0-0-dev which is
  already in the archive.
+ 
+ Test packages built in the following PPA:
+ https://launchpad.net/~waveform/+archive/ubuntu/rpiboot

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

Title:
  [needs-packaging] rpiboot

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


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

[Bug 1959624] Re: Re-merge dovecot for jammy

2022-01-31 Thread Bryce Harrington
Unfortunately there appear to be several problems with this release.

1.  After performing the merge, the autopkgtests fail for me locally
with:

static verify (ecdsa x9.62) .. : ok
0 / 23 tests failed
==3793296== Conditional jump or move depends on uninitialised value(s)
==3793296==at 0x51AB9E4: ??? (in /usr/lib/x86_64-linux-gnu/libcrypto.so.3)
==3793296==by 0x51ABCC1: ??? (in /usr/lib/x86_64-linux-gnu/libcrypto.so.3)
==3793296==by 0x50ACD74: EVP_DecryptFinal_ex (in 
/usr/lib/x86_64-linux-gnu/libcrypto.so.3)
==3793296==by 0x485F6FD: dcrypt_openssl_ctx_sym_final (dcrypt-openssl.c:547)
==3793296==by 0x128FD8: test_cipher_aead_test_vectors (test-crypto.c:182)
==3793296==by 0x12A2EE: test_run_funcs (test-common.c:346)
==3793296==by 0x12AECF: test_run (test-common.c:417)
==3793296==by 0x1209D3: main (test-crypto.c:1309)
==3793296== 
{
   
   Memcheck:Cond
   obj:/usr/lib/x86_64-linux-gnu/libcrypto.so.3
   obj:/usr/lib/x86_64-linux-gnu/libcrypto.so.3
   fun:EVP_DecryptFinal_ex
   fun:dcrypt_openssl_ctx_sym_final
   fun:test_cipher_aead_test_vectors
   fun:test_run_funcs
   fun:test_run
   fun:main
}
Failed to run: ./test-crypto
make[4]: *** [Makefile:1136: check-local] Error 1


2.  Frank Elsner reports a segfault in hook_mailbox_allocated, reportedly fixed 
by reverting one of the commits

https://www.mail-archive.com/dovecot@dovecot.org/msg85086.html

3.  A different user reports a couple potential issues (maybe not severe
though)

https://www.mail-archive.com/dovecot@dovecot.org/msg85088.html

4.  Daniel Luke indicates there's a time-util.h header still missing,
although that may only affect macOS:

https://www.mail-archive.com/dovecot@dovecot.org/msg85111.html

The mailing list has mention of a few other crashes on this version
which may be unique from the above crashes.  I'm not getting a strong
sense of this being a solid release, and given that the current version
is afaict OK, it might be better to wait and see how the next release
looks.


** Changed in: dovecot (Ubuntu)
   Status: New => Incomplete

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

Title:
  Re-merge dovecot for jammy (v2.3.18?)

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


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

[Bug 1959624] Re: Re-merge dovecot for jammy

2022-01-31 Thread Bryce Harrington
Setting to incomplete as we wait for 2.3.18.  Dovecot releases
relatively frequently so I anticipate 2.3.18 in Feb.

** Summary changed:

- Re-merge dovecot for jammy
+ Re-merge dovecot for jammy (v2.3.18?)

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

Title:
  Re-merge dovecot for jammy (v2.3.18?)

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


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

[Bug 1959527] Re: Behringer UMC22 lost capture support

2022-01-31 Thread Ohad Lutzky
Workaround: Comment out the following line:

ATTRS{idVendor}=="08bb", ATTRS{idProduct}=="2902",
ENV{ACP_PROFILE_SET}="behringer-umc22.conf"

...wherever it appears in /lib/udev/rules.d. For me this is in
90-{pipewire-alsa,pulseaudio}.rules.

I don't understand why this workaround helps. I found it here:
https://www.reddit.com/r/linuxaudio/comments/qerbqa/suddenly_cant_select_input_of_behringer_umc22/

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

Title:
  Behringer UMC22 lost capture support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1959527/+subscriptions


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

[Bug 1959625] [NEW] barbican autopkgtests fail with python3.10

2022-01-31 Thread Steve Langasek
Public bug reported:

python3-defaults in jammy-proposed switches python3 to be python3.10.
This causes barbican's autopkgtests to fail fairly inscrutably:

autopkgtest [09:11:30]: test barbican-daemons: [---
OK
OK
autopkgtest [09:16:31]: test barbican-daemons: ---]
barbican-daemons FAIL non-zero exit status 22

The 'OK' messages are confirmations that the daemons are started; the
actual failing command is the call to curl --fail http://localhost:9311,
which connects to apache and then expects a response from barbican-
worker via wsgi.  The apache log shows output such as:

[Mon Jan 31 21:45:54.931993 2022] [wsgi:error] [pid 15857:tid
139695589144128] [client 127.0.0.1:59380] Timeout when reading response
headers from daemon process 'barbican-api': /usr/share/barbican/app.wsgi

The worker log, in turn, shows only:

2022-01-31 21:34:36.092 11378 ERROR oslo.messaging._drivers.impl_rabbit
[-] Connection failed: [Errno 111] ECONNREFUSED (retrying in 2.0
seconds): ConnectionRefusedError: [Errno 111] ECONNREFUSED

It's true that the connection is refused, because the autopkgtest
doesn't install rabbitmq-server?  But this doesn't seem to be a problem
when running under python3.9?

If I upgrade to -proposed and then downgrade only python3-defaults, the
failure is still reproducible, so this may be caused by by some other
package in -proposed besides python3-defaults.

** Affects: barbican (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/1959625

Title:
  barbican autopkgtests fail with python3.10

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


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

[Bug 1959626] Re: barbican autopkgtests fail with python3.10

2022-01-31 Thread Steve Langasek
except the autopkgtest log clearly shows only python3-defaults being
pulled from -proposed, so it looks like more analysis is needed.

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

Title:
  barbican autopkgtests fail with python3.10

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


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

[Bug 1959626] [NEW] barbican autopkgtests fail with python3.10

2022-01-31 Thread Steve Langasek
Public bug reported:

python3-defaults in jammy-proposed switches python3 to be python3.10.
This causes barbican's autopkgtests to fail fairly inscrutably:

autopkgtest [09:11:30]: test barbican-daemons: [---
OK
OK
autopkgtest [09:16:31]: test barbican-daemons: ---]
barbican-daemons FAIL non-zero exit status 22

The 'OK' messages are confirmations that the daemons are started; the
actual failing command is the call to curl --fail http://localhost:9311,
which connects to apache and then expects a response from barbican-
worker via wsgi.  The apache log shows output such as:

[Mon Jan 31 21:45:54.931993 2022] [wsgi:error] [pid 15857:tid
139695589144128] [client 127.0.0.1:59380] Timeout when reading response
headers from daemon process 'barbican-api': /usr/share/barbican/app.wsgi

The worker log, in turn, shows only:

2022-01-31 21:34:36.092 11378 ERROR oslo.messaging._drivers.impl_rabbit
[-] Connection failed: [Errno 111] ECONNREFUSED (retrying in 2.0
seconds): ConnectionRefusedError: [Errno 111] ECONNREFUSED

It's true that the connection is refused, because the autopkgtest
doesn't install rabbitmq-server?  But this doesn't seem to be a problem
when running under python3.9?

If I upgrade to -proposed and then downgrade only python3-defaults, the
failure is still reproducible, so this may be caused by by some other
package in -proposed besides python3-defaults.

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


** Tags: update-excuse

** Tags added: update-excuse

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

Title:
  barbican autopkgtests fail with python3.10

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


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

[Bug 1959324] Re: sbuild-launchpad-chroot does not notice tar extract failures

2022-01-31 Thread Launchpad Bug Tracker
This bug was fixed in the package sbuild-launchpad-chroot - 0.19

---
sbuild-launchpad-chroot (0.19) jammy; urgency=medium

  * Check the exit code of tar when extracting a root file system.
Thanks to Scott Moser. (LP: #1959324)

 -- dann frazier   Mon, 31 Jan 2022 12:38:07
-0700

** Changed in: sbuild-launchpad-chroot (Ubuntu Jammy)
   Status: Confirmed => Fix Released

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

Title:
  sbuild-launchpad-chroot does not notice tar extract failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sbuild-launchpad-chroot/+bug/1959324/+subscriptions


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

[Bug 1959622] Re: FTBFS against openssl 3.0

2022-01-31 Thread Dan Bungert
** Bug watch added: Debian Bug tracker #1004707
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004707

** Also affects: hydra (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004707
   Importance: Unknown
   Status: Unknown

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

Title:
  FTBFS against openssl 3.0

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


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

[Bug 1959624] [NEW] Re-merge dovecot for jammy

2022-01-31 Thread Bryce Harrington
Public bug reported:

dovecot has already been merged once for jammy, but there's a new
upstream bugfix release that could be pulled in.

 dovecot | 1:2.3.13+dfsg1-1ubuntu3 | impish
 dovecot | 1:2.3.16+dfsg1-3ubuntu1 | jammy 

dovecot| 1:2.3.4.1-5+deb10u1~bpo9+1 | stretch-backports  
dovecot| 1:2.3.4.1-5+deb10u1~bpo9+1 | stretch-backports-debug
dovecot| 1:2.3.13+dfsg1-2   | stable 
dovecot| 1:2.3.17.1+dfsg1-1 | testing
dovecot| 1:2.3.17.1+dfsg1-1 | unstable   
dovecot| 1:2.3.17.1+dfsg1-1 | unstable-debug 


https://dovecot.org/doc/NEWS

v2.3.17.1 2021-12-07  Aki Tuomi 

- dsync: Add back accidentically removed parameters.
- lib-ssl-iostream: Fix assert-crash when OpenSSL returned syscall error
  without errno.
- master: Dovecot failed to start if ssl_ca was too large.

v2.3.17 2021-10-28  Aki Tuomi 

* Dovecot now logs a warning if time seems to jump forward at least
  100 milliseconds.
* dict: Lines logged by the dict process now contain the dict name as
  the prefix.
* lib-index: mail_cache_fields, mail_always_cache_fields and
  mail_never_cache_fields now verifies that the listed header names are
  valid. Especially the UTF8 "–" character has sometimes been wrongly
  used instead of the ASCII "-".
+ *-login: Added login_proxy_rawlog_dir setting to capture
  rawlogs between proxy and backend.
+ dict: The server process now keeps the last 10 idle dict backends
  cached for maximum of 30 seconds. Practically this acts as a
  connection pool for dict-redis and dict-ldap. Note that this doesn't
  affect dict-sql, because it already had its own internal cache.
+ doveadm: New stats add/remove commands added to support changing the
  metrics configuration on runtime.
+ lazy_expunge: Added lazy_expunge_exclude settings to disable
  lazy_expunge for specific folders. \Special-use flags can be used as
  folder names.
+ lib-lua: Added a new helper function 
dovecot.restrict_global_variables()
  to disable or enable defining new global variables.
- LAYOUT=index List index rebuild was missing.
- LAYOUT=index: Duplicate GUIDs were not detected.
- acl: When using acl_ignore_namespace Dovecot attempted to access or
  create dovecot-acl-list even when the namespace should have been
  ignored. For virtual namespaces this could have yielded errors about
  "Read-only file system" or "Permission denied".
- auth: Setting the "master" passdb field to empty value would
  cause proxying to fail with an authentication error.
  Now an empty "master" field is ignored.
- doveadm-server: Duplicate error lines were sent for failed commands.
  This didn't normally cause visible problems, except when using
  wildcards in usernames or -A parameter to go through multiple users.
- doveadm-server: Logs written by doveadm-server were often missing log
  prefixes, especially mail_log_prefix for mail commands. Logs sent to
  doveadm TCP client were also missing log prefixes.
- doveadm: v2.3 regression: batch command always crashes.
- doveadm: v2.3.11 regression: Commands failed if ssl_cert or
  ssl_key files weren't readable by the user running doveadm, even
  though doveadm didn't actually use these settings
- imap-hibernate: Process may crash at deinit:
  Panic: file ioloop.c: line 928 (io_loop_destroy): assertion failed:
  (ioloop->cur_ctx == NULL).
- imap: Using imap_fetch_failure=no-after can cause assert-crash
  with some IMAP commands if reading the mail fails (e.g. wrong cached
  mail size). Fixes:
  Panic: file index-mail-headers.c: line 198 
(index_mail_parse_header_init):
  assertion failed: (!mail->data.header_parser_initialized)
- imap: v2.3.10 regression: When using INDEXPVT to enable private
  \Seen flags (for shared or public namespaces) the STORE command did
  not send untagged replies for the \Seen flag changes.
- imap: v2.3.15 regression: If PREVIEW/SNIPPET is not the final FETCH
  option in the command, the IMAP FETCH response is broken.
- imap: v2.3.15 regression: MOVE command leaks mailbox if it can't be
  opened and crashes at deinit:
  Panic: file mail-user.c: line 229 (mail_user_deinit): assertion 
failed:
  ((*user)->refcount == 1).
- imapc: Copying nonexistent mail via imapc could have crashed. Fixes:
  Panic: file mail-storage.c: line 2385 
(mailbox_transaction_commit_get_changes):
  assertion failed: (ret < 0 || seq_range_count(&changes_r->saved_uids) 
== save_count ||
  array_count(&changes_r

[Bug 1959618] Re: shim's fallback hangs in CopyMem, can't boot ISOs

2022-01-31 Thread valdikss
>However, fbx64.efi should not be included on ISO images

Sorry, my fault, there's no fbx64.efi in that ISO, and it doesn't boot due to 
unrelated issue.
However, I got an issue with fallback on Fedora, and Ubuntu also buggy version 
of shim.

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

Title:
  shim's fallback hangs in CopyMem, can't boot ISOs

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


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

[Bug 1959622] Re: FTBFS against openssl 3.0

2022-01-31 Thread Dan Bungert
** Patch added: "hydra-1_9.2-1build1_9.2-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/hydra/+bug/1959622/+attachment/5558499/+files/hydra-1_9.2-1build1_9.2-1ubuntu1.debdiff

** Changed in: hydra (Ubuntu)
   Status: New => Confirmed

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

Title:
  FTBFS against openssl 3.0

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


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

[Bug 1959441] Re: ovn-controller crashing with "failed in flood_remove_flows_for_sb_uuid()"

2022-01-31 Thread Corey Bryant
** Also affects: ovn (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/1959441

Title:
  ovn-controller crashing with "failed in
  flood_remove_flows_for_sb_uuid()"

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1959441/+subscriptions


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

[Bug 1958777] Re: Noise before login screen with 5.13 kernel on kUbuntu

2022-01-31 Thread Yury
Today, I have updated to version 5.13.0-28. The issue is still present.
I cannot boot, I see just noise on the screen after the kubuntu logo and
before the login screen.

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

Title:
  Noise before login screen with 5.13 kernel on kUbuntu

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


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

[Bug 1895454] Re: ibus indicator is unreadable, and the dropdown doesn't clarify what option is selected

2022-01-31 Thread Bug Watch Updater
** Changed in: ibus
   Status: Unknown => Fix Released

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

Title:
  ibus indicator is unreadable, and the dropdown doesn't clarify what
  option is selected

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


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

[Bug 1959021] Re: botan ecdsa test failures on ppc64el with openssl 3

2022-01-31 Thread Steve Langasek
I tested against a build of openssl3 from trunk
(d450eb84c802b2f78971f905b251a0fb89ebb7d1) and the problem was still
present.

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

Title:
  botan ecdsa test failures on ppc64el with openssl 3

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


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

[Bug 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument

2022-01-31 Thread Fernando Sclavo
Just updated my laptop (Ubuntu 20.04.3 LTS) from 5.13.0-27-generic to 
5.13.0-28-generic and have the same issue (stuck in max brightness).
On 5.13.0-27-generic, brightness adjust works fine.

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

Title:
  amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid
  argument

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


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

[Bug 1959622] Re: FTBFS against openssl 3.0

2022-01-31 Thread Dan Bungert
** Description changed:

  Hydra will FTBFS when building against openssl 3.0 for want of a INT_MAX
  definition.
  
- In file included from hydra-mod.c:8:  
  
- /usr/include/openssl/err.h: In function ‘ERR_GET_LIB’:
  
- /usr/include/openssl/err.h:243:9: error: ‘INT_MAX’ undeclared 
  (first use in this function)  

243 | if (ERR_SYSTEM_ERROR(errcode))
  
/usr/include/openssl/err.h:31:1: note: ‘INT_MAX’ is defined in header   

- ‘’; did you forget to ‘#include ’?
  
+ In file included from hydra-mod.c:8:
+ /usr/include/openssl/err.h: In function ‘ERR_GET_LIB’:
+ /usr/include/openssl/err.h:243:9: error: ‘INT_MAX’ undeclared
+ (first use in this function)
+ 243 | if (ERR_SYSTEM_ERROR(errcode))
+ /usr/include/openssl/err.h:31:1: note: ‘INT_MAX’ is defined in header
+ ‘’; did you forget to ‘#include ’?
  
  limits.h does get included, but a conflict between the hydra configure
  file and the de-facto package layout of libmemcached-dev means that the
  wrong limits.h file, then one from memcached, is included.

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

Title:
  FTBFS against openssl 3.0

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


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

[Bug 1958724] Re: System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic

2022-01-31 Thread Martin Fehlau
Great, it works now. Thank you so much.
Martin

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

Title:
  System Shutdown and resume hangs since Kernel linux-
  image-5.13.0-23-generic

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


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

[Bug 1959621] acpidump.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1959621/+attachment/5558498/+files/acpidump.txt

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

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] WifiSyslog.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1959621/+attachment/5558497/+files/WifiSyslog.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] UdevDb.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1959621/+attachment/5558496/+files/UdevDb.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] PulseList.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1959621/+attachment/5558495/+files/PulseList.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] ProcInterrupts.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1959621/+attachment/5558493/+files/ProcInterrupts.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] ProcModules.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1959621/+attachment/5558494/+files/ProcModules.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] ProcEnviron.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1959621/+attachment/5558492/+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/1959621

Title:
  webcam doesn't work

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


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

[Bug 1959621] ProcCpuinfoMinimal.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1959621/+attachment/5558491/+files/ProcCpuinfoMinimal.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] Lsusb-v.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1959621/+attachment/5558489/+files/Lsusb-v.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] ProcCpuinfo.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1959621/+attachment/5558490/+files/ProcCpuinfo.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] Lsusb.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1959621/+attachment/5558487/+files/Lsusb.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] Lsusb-t.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1959621/+attachment/5558488/+files/Lsusb-t.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] Lspci-vt.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1959621/+attachment/5558486/+files/Lspci-vt.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] Lspci.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1959621/+attachment/5558485/+files/Lspci.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] CurrentDmesg.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1959621/+attachment/5558484/+files/CurrentDmesg.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] CRDA.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1959621/+attachment/5558483/+files/CRDA.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] AlsaInfo.txt

2022-01-31 Thread Piotr
apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1959621/+attachment/5558482/+files/AlsaInfo.txt

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

Title:
  webcam doesn't work

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


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

[Bug 1959621] [NEW] webcam doesn't work

2022-01-31 Thread Piotr
Public bug reported:

As I have reported yet 4 times [Bug 1956461][Bug 1957112][Bug 1957112], [Bug 
1957196] [Bug 1958414] the webcam Creative HD 720 p after installing any other 
kernel then the 5.4.0.91 (this time after installing the kernel # 5.4.0.97-100) 
stop working. There is no folder /dev/v4l.
lsb_release -rd
Description:Linux Mint 20.3
Release:20.3
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  piotr  2892 F pulseaudio
 /dev/snd/controlC0:  piotr  2892 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 20.3
InstallationDate: Installed on 2020-06-07 (603 days ago)
InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-97-generic 
root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash
ProcVersionSignature: Ubuntu 5.4.0-97.110-generic 5.4.162
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-97-generic N/A
 linux-backports-modules-5.4.0-97-generic  N/A
 linux-firmware1.187.25
RfKill:
 
Tags:  una
Uname: Linux 5.4.0-97-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 10/27/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: H67MA-USB3-B3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H67MA-USB3-B3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: apport-collected una

** Tags added: apport-collected una

** Description changed:

  As I have reported yet 4 times [Bug 1956461][Bug 1957112][Bug 1957112], [Bug 
1957196] [Bug 1958414] the webcam Creative HD 720 p after installing any other 
kernel then the 5.4.0.91 (this time after installing the kernel # 5.4.0.97-100) 
stop working. There is no folder /dev/v4l.
  lsb_release -rd
  Description:  Linux Mint 20.3
  Release:  20.3
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.21
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  piotr  2892 F pulseaudio
+  /dev/snd/controlC0:  piotr  2892 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 20.3
+ InstallationDate: Installed on 2020-06-07 (603 days ago)
+ InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
+ IwConfig:
+  lono wireless extensions.
+  
+  enp3s0no wireless extensions.
+ MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-97-generic 
root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash
+ ProcVersionSignature: Ubuntu 5.4.0-97.110-generic 5.4.162
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-97-generic N/A
+  linux-backports-modules-5.4.0-97-generic  N/A
+  linux-firmware1.187.25
+ RfKill:
+  
+ Tags:  una
+ Uname: Linux 5.4.0-97-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
+ _MarkForUpload: True
+ dmi.bios.date: 10/27/2011
+ dmi.bios.vendor: Award Software International, Inc.
+ dmi.bios.version: F4
+ dmi.board.name: H67MA-USB3-B3
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: x.x
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
+ dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
+ dmi.product.name: H67MA-USB3-B3
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

Title:
  webcam doesn't work

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


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

[Bug 1959622] [NEW] FTBFS against openssl 3.0

2022-01-31 Thread Dan Bungert
Public bug reported:

Hydra will FTBFS when building against openssl 3.0 for want of a INT_MAX
definition.

In file included from hydra-mod.c:8:

/usr/include/openssl/err.h: In function ‘ERR_GET_LIB’:  

/usr/include/openssl/err.h:243:9: error: ‘INT_MAX’ undeclared   
(first use in this function)

  243 | if (ERR_SYSTEM_ERROR(errcode))  

/usr/include/openssl/err.h:31:1: note: ‘INT_MAX’ is defined in header   

‘’; did you forget to ‘#include ’?  


limits.h does get included, but a conflict between the hydra configure
file and the de-facto package layout of libmemcached-dev means that the
wrong limits.h file, then one from memcached, is included.

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


** Tags: ftbfs update-excuse

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

Title:
  FTBFS against openssl 3.0

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


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

[Bug 1959588] Re: FTBFS: 'SSL_OP_BIT’ undeclared here

2022-01-31 Thread Andreas Hasenack
** Changed in: stunnel4 (Ubuntu)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: stunnel4 (Ubuntu)
   Status: New => In Progress

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

Title:
  FTBFS: 'SSL_OP_BIT’ undeclared here

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


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

[Bug 1959615] Re: DEP8 failure: deprecation warning on stderr

2022-01-31 Thread Andreas Hasenack
** Changed in: stunnel4 (Ubuntu)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: stunnel4 (Ubuntu)
   Status: New => In Progress

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

Title:
  DEP8 failure: deprecation warning on stderr

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


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

[Bug 1959588] Re: FTBFS: 'SSL_OP_BIT’ undeclared here

2022-01-31 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/stunnel4/+git/stunnel4/+merge/414829

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

Title:
  FTBFS: 'SSL_OP_BIT’ undeclared here

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


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

[Bug 1959615] Re: DEP8 failure: deprecation warning on stderr

2022-01-31 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/stunnel4/+git/stunnel4/+merge/414829

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

Title:
  DEP8 failure: deprecation warning on stderr

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


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

[Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

2022-01-31 Thread Diana
Thanks so much for this!!

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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


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

  1   2   3   4   >