*** This bug is a duplicate of bug 1979244 ***
https://bugs.launchpad.net/bugs/1979244
I also have this issue on 22.04:
I am trying to install libudev-dev to compile logiops, but my up to date
system has libudev1 (249.11-0ubuntu3.7). Error below.
--
Some packages could not be
Correct, this fix is valuable for core22, so kinetic was skipped. There
should be no issues for anyone updating from jammy to kinetic. Though
this will affect core20, we expect most snaps to be using core22 so no
plan to backport it to focal.
--
You received this bug notification because you are
The verification of the Stable Release Update for glib2.0 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package glib2.0 - 2.72.4-0ubuntu2
---
glib2.0 (2.72.4-0ubuntu2) jammy; urgency=medium
* d/p/0001-gio-Make-portal-support-aware-of-snaps.patch:
- Make portal support aware of snaps (LP: #1998267)
-- Robert Ancell Wed, 22 Mar 2023
15:52:13 +1300
** C
I triggered a DEP8 run in the proper infrastructure[1], and the test
failed as expected:
autopkgtest [21:32:30]: test systemd-socket-activation: [---
Fail: ssh.socket: expected SubState=listening, but got SubState=running
autopkgtest [21:32:31]: test systemd-socket-activation:
I verified that the test was executed according to the [test plan].
I understand kinetic is not part of this SRU. The reason wasn't
explained anywhere, but I'm assuming it's because it's a) ending support
soon; and/or b) this glib update is more useful for core22 snap and core
desktop deployments,
I grabbed this for my SRU shift, but quickly realized reviewing this
patch is more complicated than I thought. I concentrated a bit more on
the DEP8 test then.
I confess I don't understand how this check is passing:
# Check that ssh.service is currently inactive/dead.
assert_unit_property ssh.ser
Yes, these specific steps performed in a core desktop VM.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1998267
Title:
glib not aware of snap confinement
Status in glib2
** Package changed: update-manager (Ubuntu) => openldap (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/2017927
Title:
Failed to start SLAPD and B&R operation fai
Public bug reported:
$ snap connections --all | grep gnome
content -
gnome-3-28-1804:gnome-3-28-1804 -
content -
gnome-3-34-1804:gnome-3
Public bug reported:
cannot install unifi network controller due unspecified unmet
dependencies
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libssl1.1 1.1.1f-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-71.78~20.04.1-generic 5.15.92
Uname: Linux 5.15.0-71-generic x86_64
ApportVersion
Tried with the oldest and newest kernels available in mainline (6.0.0
and 6.3.0). Same problem. Same ipc errors in dmesg.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs
Attempted a variety of things that I found on the internet for similar
problems:
Various options to alsa-base.conf (tried them individually):
/etc/modprobe.d/alsa-base.conf
options snd-hda-intel model=auto
options snd-hda-intel model=generic
options snd_sof sof_debug=128
options s
I mean 22.04.2 LTS, not 22.03.2 LTS
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2017832
Title:
No audio/sound after fresh 23.4 install, only dummy audio
Status in
Here is the dmesg log from 22.03.2 LTS. The sound works great on that
release. There are no tx/HW params/AsoC errors as seen in dmesg with
23.04.
[3.608109] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode
[3.632029] sof-audio-pci-intel-tgl :00:1f.3: NHLT table not found
Hello Robert,
the [test plan] has very specific steps involving the calculator,
gsettings, and an expected result. Did you perform those specifically?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https:/
** Changed in: ubuntu-meta (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-meta (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-meta (Ubuntu)
Assignee: (unassigned) => Tim Andersson (andersson123)
--
You received this bug notification because you are a me
Can you please attach logs from systemd-logind?
$ journalctl -u systemd-logind.service -b 0 > systemd-logind-log.txt
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
May be worth mentioning that I previously was running 22.04 LTS, and the
sound worked just fine on initial install, and through all the updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bu
Brian promised to update the description with the required SRU
information. On this note I have accepted the upload into jammy-
proposed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.laun
Hello Brian, or anyone else affected,
Accepted ubuntu-meta into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubuntu-meta/1.481.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Public bug reported:
MESA 22.2 contains a malfunction which causes kwin to exit regularly /
frequently, leaving the system without window management.
This is a regression compared to MESA 22.1 and fixed again in MESA 22.3.
See following MESA bug:
* https://gitlab.freedesktop.org/mesa/mesa/-/iss
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://
Hello,
On Ubuntu desktop 22.04 LTS, it seems that the hook is not executed. I'm
not sure how to verify that but sure thing is the DHCP is well
announcing the ntp server.
DHCP4.OPTION[8]:ntp_servers = X.X.X.X
DHCP4.OPTION[18]: requested_ntp_servers = 1
It looks like that libdatetime-timezone-perl ships a copy of the
timezone data. So versions in recent Ubuntu versions will contain the
tzdata update. See
https://manpages.ubuntu.com/manpages/kinetic/man3/DateTime::TimeZone::Catalog.3pm.html
--
You received this bug notification because you are a
The debdiff is against 1.481 in jammy, please rebase against the latest version
in the development release (currently 1.501 in lunar). You can use
'pull-lp-source ubuntu-meta' for this.
Please also close this bug in the changelog e.g. (LP: #2017786).
We should probably do the same for all the f
I could help myself like this:
#check current linux version
uname -a
--> Linux p15 5.19.0-40-generic #41~22.04.1-Ubuntu
# list installed linux images
apt list --installed| grep linux-image
--> there were some older ones with version 5.15
# remove the old ones
apt remove linux-image-5.15.0-69-
I did not make any changes to the design when moving it from Update-
Manager in apt, it's been this way for 10 years now, it's a proven
concept.
The initial implementation used and md5 but the math gets complex when
dealing with 128 bit integers.
You can easily override the machine-id for apt by
The size of /boot was choosen by Ubuntu during the installation (not by
me).
I never touched a file in this directory by hand.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.
To add a data point and save others from preventable headaches, I encountered a
related bug and reported it here:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2017399
If anyone cares, here are my two cents regarding phased updates:
https://github.com/xwcal/ubuntu-apt-bug#a-short-critique-of
Another question, I've found another package
`DateTime::TimeZone::Catalog.3pm.gz`
https://manpages.ubuntu.com/manpages/xenial/man3/DateTime::TimeZone::Catalog.3pm.html
Provided by: libdatetime-timezone-perl_1.95-1+2016a_all
And there is some information with only `Kiev`
Ukraine (UA)
Thanks! It works when set the environment option in the `teams` CMD.
>>
https://answers.microsoft.com/en-us/msteams/forum/all/wrong-time-in-the-ms-teams-linux-app/c14eced8-3b55-4be8-b0c2-a01015072df2?page=2
Dmytro Verbytskyi:
I have Ubuntu 20.04. To make it all automated, we could add the
enviro
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2017743/+attachment/5669128/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2017743/+attachment/5669127/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
apport information
** Tags added: apport-collected jammy
** Description changed:
To solve MS Teams Calendar issue on Ubuntu, we need to update the time
zone:
> sudo timedatectl set-timezone Europe/Kyiv
but it doesn't work, the only in old-fashioned spell 'kiev' works:
> sudo t
** Description changed:
This error happens when you try to run ifup or ifdown:
```
# ifdown enp3s0
/etc/network/if-down.d/resolved: 12: mystatedir: not found
# ifup enp3s0
/etc/network/if-up.d/resolved: 12: mystatedir: not found
```
Here's the first 12 lines of those scrip
>From the logs:
zstd: error 25 : Write error : No space left on device (cannot write
compressed block)
Not a bug in the software, but a local problem on your system.
You have to clean up your system to create enough free space.
--
You received this bug notification because you are a member of U
37 matches
Mail list logo
