I'm not sure Argyll is going to be MIR-able; could we instead demote
colord-sensor-argyll to universe?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/2003833
Title:
colord
This issue is still present on 23.04, resolved by deleting old
certificate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1973441
Title:
Printing does not work on Ubuntu
** Description changed:
[Impact]
Occasionally, during instance boot or machine start-up, dhclient will
attempt to acquire a dhcp lease and fail, leaving the instance with no
IP address and making it unreachable.
This happens about once every 100 reboots on bare metal, or Chris
Public bug reported:
colord recently re-enabled argyll support. Unfortunately since argyll is
in universe and colord is in main, this is causing an 'impossible
depends' migration error for colord.
colord-sensor-argyll/amd64 in main cannot depend on argyll in universe
Impossible Depends: colord
I wanted to report a similar issue on Lenovo Legion 7 Slim AMD. Onboard
speakers do not seem to produce sound but in settings menu sound appears
to be getting produced on the speakers. Headphones work fine. Thankfully
I primarily use headphones but wanted to report the issue.
--
You received
Public bug reported:
This is the same as https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=943425 which is fixed in Debian bullseye and
Ubuntu impish but still present in focal.
** Affects: klibc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
This bug was fixed in the package libnl3 - 3.4.0-1ubuntu0.1
---
libnl3 (3.4.0-1ubuntu0.1) focal; urgency=medium
* Backport one upstream fix to support devices using NLA_F_NESTED
- 7de65a051fb3 (attr: mark nested attributes as NLA_F_NESTED)
(LP: #1998765)
-- Robert Liu
The verification of the Stable Release Update for libnl3 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
I'm going to go ahead and mark this as block-proposed-bionic so I don't
keep checking this :).
Please ping in #ubuntu-release if this actually needs to be released to
users.
** Tags added: block-proposed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch
Since this is link-specific DNS, isn't the scope ID implied?
I do see the odd formatting issue in the 'DNS Servers' list:
$ resolvectl status wlp0s20f3
Link 4 (wlp0s20f3)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Sadly dpkg terminal log is missing. So the information for further
investigation is missing. Reinstalling tzdata (sudo apt install
--reinstall tzdata) should solve the issue. I assume that has happened
in the
This should be not a problem in Ubuntu 14.04 any more:
https://launchpad.net/ubuntu/trusty/amd64/tzdata-java
** Changed in: tzdata (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Description changed:
package tzdata-java 2012e-0ubuntu0.12.04.1 failed to install/upgrade:
problemas de dependencias - se deja sin configurar
+
+ ```
+ dpkg: dependency issues prevent configuration of tzdata-java:
+ tzdata-java depends on tzdata (= 2012e-0ubuntu0.12.04.1); Nevertheless:
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. There have been many changes in Ubuntu since
that time you reported the bug and your problem may have been
** Changed in: tzdata (Ubuntu)
Importance: Undecided => Medium
** Changed in: tzdata (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
*** This bug is a duplicate of bug 78175 ***
https://bugs.launchpad.net/bugs/78175
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant dpkg terminal log:
```
Setting up tzdata (2015d-0ubuntu0.14.04) ...
Can't locate object method "new" via package
*** This bug is a duplicate of bug 78175 ***
https://bugs.launchpad.net/bugs/78175
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant dpkg terminal log:
```
Setting up tzdata (2016f-0ubuntu0.14.04) ...
Can't locate object method "new" via package
Thanks for the update. I'll mark this as invalid since there is nothing
to do.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant parts of dpkg terminal log:
```
Processing triggers for initramfs-tools ...
/usr/sbin/update-initramfs: 115: /usr/sbin/update-initramfs: ln: not found
update-initramfs: Generating
*** This bug is a duplicate of bug 500175 ***
https://bugs.launchpad.net/bugs/500175
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The relevant dpkg terminal log:
```
Use of uninitialized value $reply in scalar chomp at
Yes, please fix.
>From a security standpoint, we can't tell the "good" held backs (Phased
Updates) from the "bad" held backs (problem with package). So we assume
its a package problem, go in with a hammer, and use Aptitude's safe-
upgrade to force the updates. Now we've subverted/undermined the
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This issue is caused by an (probably hardware) issue with your system
drive as the error message and dmesg indicate:
```
[ 148.235621] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant dpkg terminal log:
```
dpkg: error processing package tzdata (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
```
--
You received
*** This bug is a duplicate of bug 1914875 ***
https://bugs.launchpad.net/bugs/1914875
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This particular bug has already been reported and is a duplicate of bug
#1914875, so it is being marked as such. Please
*** This bug is a duplicate of bug 1914875 ***
https://bugs.launchpad.net/bugs/1914875
** This bug is no longer a duplicate of bug 1800065
package tzdata 2018f-0ubuntu0.18.10 failed to install/upgrade: installed
tzdata package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 1914875 ***
https://bugs.launchpad.net/bugs/1914875
** This bug is no longer a duplicate of bug 1800065
package tzdata 2018f-0ubuntu0.18.10 failed to install/upgrade: installed
tzdata package post-installation script subprocess returned error exit status
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm is shipped by debconf.
So reassigning to debconf.
** Package changed: tzdata (Ubuntu) => debconf (Ubuntu)
--
You received this bug notification because you are a
** Tags added: cosmic focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1914875
Title:
Use of uninitialized value $ret in string eq at
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
The idea is that a user will want to request the sources for a given
binary package – after all, that is the promise of GPL and co that you
can easily get the source for the binary you have installed. So for me
at least this binary-to-source mapping is very intuitive and I would be
very confused
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
/usr/share/perl5/Debconf/Element/Noninteractive/Select.pm is shipped by
debconf. So reassigning to debconf.
** Package changed: tzdata (Ubuntu) => debconf (Ubuntu)
--
You received this bug notification because
Relevant dpkg terminal log:
```
Setting up tzdata (2011g-0ubuntu0.10.04) ...
Can't locate POSIX.pm in @INC (@INC contains: /etc/perl
/usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5
/usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10
/usr/local/lib/site_perl .) at
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant part from VarLogDistupgradeApttermlog:
```
Setting up tzdata (2015a-0ubuntu0.12.04) ...
Can't locate overload.pm in @INC (@INC contains: /etc/perl
/usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Relevant dpkg terminal logs:
```
Setting up tzdata (2015b-0ubuntu0.14.10) ...
Can't locate strict.pm in @INC (you may need to install the strict module)
(@INC contains: /etc/perl
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This is an issue with debconf, but I cannot explain it. debconf
1.5.79ubuntu1 ships /usr/share/perl5/Debconf/Db.pm. So Perl should find
Debconf/Db.pm in its search path /usr/share/perl5.
** Package changed:
** Description changed:
+ ```
+ Setting up tzdata (2022g-0ubuntu0.22.04.1) ...
+ Can't locate Debconf/Db.pm in @INC (you may need to install the Debconf::Db
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.34.0
/usr/local/share/perl/5.34.0
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This has been fixed in 2012h: "Bahia no longer has DST.
(Thanks to Kelley Cook.)"
** Changed in: tzdata (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a
Public bug reported:
tzdata 2021b says in NEWS: "Merge more location-based Zones whose
timestamps agree since 1970, as pre-1970 timestamps are out of scope.
This is part of a process that has been ongoing since 2013. This does
not affect post-1970 timestamps, and timezone historians who build
** Changed in: python3.5 (Debian)
Status: New => Fix Released
** Changed in: python3.4 (Debian)
Status: New => Fix Released
** Changed in: python2.7 (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@Bryce, @RAOF: thanks for the notice! I feel we should then reuse this
MIR to file a new template with our modern MIR rules (Note that the
initial demand was made in 2011!)
I’m thus marking it as incomplete until this is DONE, feel free to redirect
this request directly to the team who will own
** Package changed: ubuntu => tzdata (Ubuntu)
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2003793
Title:
package tzdata
You have been subscribed to a public bug:
>lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: tzdata 2022g-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic
There have been several updates on the upstream bug, so I have opened a
task for jammy.
** Also affects: systemd via
https://github.com/systemd/systemd/issues/25091
Importance: Unknown
Status: Unknown
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status:
Public bug reported:
Bluetooth pairing reports established using bluetoothctl, but the sound
device is not available on the Ubuntu device(?settings) manager.
Only the existing speakers (non buetooth) are showing as sound outputs
(sinks).
Bluetooth data:
beadon@semiauto:~$ bluetoothctl
Agent
Public bug reported:
apt source exact-source-package doesn't download the right source
package
when specifying source package, i expect the exact source package to be
downloaded.
example:
$ apt source linux-lowlatency => incorrectly downloads linux-meta-lowlatency
$ apt source --only-source
after powering down and up all devices DNS is working again with IPv4 resolution
see appended screenshot with a wireshark trace.
** Attachment added: "wireshark trace with correct DNS resolution of IPv4"
This bug was fixed in the package mutter - 43.2-5ubuntu1
---
mutter (43.2-5ubuntu1) lunar; urgency=medium
* Merge with Debian. Remaining change:
- Add x11-Add-support-for-fractional-scaling-using-Randr.patch
mutter (43.2-5) unstable; urgency=medium
[ Daniel van Vugt ]
*
Public bug reported:
In a network with a local nameserver that has IPv4-address 10.1.0.1 and
link-local IPv6-address fe80::2a0:57ff:fe24:b041%2 'resolvectl' returns:
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: uplink
Link 2 (ens33)
Current
@sil2100 marked out test case in the bug report more clearly.
** Description changed:
This is *probably* the wrong package, but it's the best I can figure for
this, so here goes.
Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5,
UEFI, no secure boot. Testing
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=ubiquity
** Also affects: ubiquity (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Jammy)
Importance:
The issue with being less verbose is that users will end up with the
same issue when two neighbor machines have different updates. This also
applies to machines belonging to different people as soon as these
people discuss about a but that could be caused or solved by these
updates.
I'd prefer to
51 matches
Mail list logo
