** Package changed: python3-defaults (Ubuntu) => update-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085021
Title:
apt install python3-venv rendered system unusable
To manage not
It sounds very much like you hadn't completed your upgrade. This was
just an action that was making the next steps of upgrade happen. Nothing
to do with python3-venv itself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Patch added: "xdot_1.3-1ubuntu0.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xdot/+bug/2084949/+attachment/5829788/+files/xdot_1.3-1ubuntu0.1.debdiff
** Patch removed: "xdot_1.3-1ubuntu0.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xdot/+bug/2084949/+attachment/5829787/+
** Description changed:
+ [ Impact ]
+
+ * xdot fails to start on Ubuntu 24.04, without python3-setuptools
+ installed.
+
+ [ Test Plan ]
+
+ * Run xdot from a terminal.
+
+ * If it fails to start, you've hit this bug.
+
+ [ Where problems could occur ]
+
+ * We are adding a dependency t
** Patch added: "xdot_1.3-1ubuntu0.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xdot/+bug/2084949/+attachment/5829787/+files/xdot_1.3-1ubuntu0.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
The easy workaround would be to install python3-setuptools
** Also affects: xdot (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: xdot (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** No longer affects: ubuntu-dev-tools (Ubuntu)
** Changed in: reverse-depends
Status: New => Fix Released
** No longer affects: ubuntu-dev-tools (Ubuntu Oracular)
** No longer affects: ubuntu-dev-tools (Ubuntu Noble)
--
You received this bug notification because you are a member of Ubu
Aha, this is a fairly subtle bug in some hacky SQL. Thanks for making me
revisit it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078862
Title:
reverse-depends misses to report riscv64 architectur
** Also affects: reverse-depends
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/2078862
Title:
reverse-depends misses to report riscv64 architecture
To ma
Reported upstream: https://github.com/latchset/clevis/issues/472
** Bug watch added: github.com/latchset/clevis/issues #472
https://github.com/latchset/clevis/issues/472
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
The same occurred today.
Any thoughts on clevis-initramfs related to LUKS unlock with Tang Server
?
I am currently suspecting that it kept trying the 1st Tang Server on the
list (which was pingable but NOT unlocked, i.e. it could NOT unlock the
Desktop, which clevis was requesting to do) and keep
I shut my PC down and restarted a few Hours afterwards.
The only change in between was that Tang Host #1 was properly unlocked
this time and could properly reply Clevis requests when the Client was
booting.
So ... maybe there is something going on where Clevis sees the Host up
(ping probably succ
The only thing that comes to mind is that one of the Tang Servers was
"up" for Ping but not "unlocked" & able to Serve (but then clevis should
proceed to the next one anyways, shouldn't it ?), since I have full disk
encryption in order to not have them unlocked by default (obviously).
I'll have a
** Attachment added: "initramfs_debug_v01.txt"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2071885/+attachment/5794582/+files/initramfs_debug_v01.txt
** Tags added: regression-update
** Description changed:
This is potentially a Regression related to the previous BUG Rep
Public bug reported:
This is potentially a Regression related to the previous BUG Reports that I
filed (and Benjamin Drung [bdrung] helped me out a lot in resolving):
- https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926
- https://bugs.launchpad.net/ubuntu/+source/initramfs-too
I was about to file a new BUG Report.
I did a quick fix and uploaded to one of my Repositories:
https://github.com/luckylinux/grub-
scripts/commit/59f90b0f751fb1241b0243dc5700522ffe73bf8e
Basically you need to add one mount / umount command for the /usr
Dataset whenever the / and/or /etc Dataset
Still happens. it_IT.UTF-8, Ubuntu 24.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066388
Title:
decimal point gnored with LC_NUMERIC=it_IT.UTF-8
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2019247
Title:
perf should be compiled with libtraceevent
To manage notifications
Then I think it's OK (if you are satisfied me me being the only one
testing the fix) :).
Thanks again for your help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065037
Title:
dhcpcd is called be
** Attachment added: "initramfs_proposed_testing.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5777133/+files/initramfs_proposed_testing.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Attachment added: "dmesg_proposed_testing.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5777132/+files/dmesg_proposed_testing.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Hello Timo.
Sure, I just tested it and I get relatively good Results.
See my Conclusion below. Maybe some extra discussions needed about the
`--noarp` NOT being included in the patch, which causes the Boot time to
go from approx. 22s (with `--noarp`) to approx. 28s (without `-noarp`,
i.e. the `no
** Attachment added: "initramfs_proposed_testing.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5776985/+files/initramfs_proposed_testing.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Hello Timo.
Sure, I just tested it and I get to the (same) Result I was getting
while performing preliminary Investigations. The boot time is around 22
Seconds (down from the Original 300 Seconds).
So it's Good, from what I can tell :).
# Test Procedure & Log
# Pin noble-proposed Packages with
** Attachment added: "dmesg_proposed_testing.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5776984/+files/dmesg_proposed_testing.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Yeah I can do that, that's lower-priority ish. The good thing is that it
works. If I cannot see what's happening, that's secondary, I can just
look at `dmesg` once the boot is completed, if I really wanted (or
`/run/initramfs/initramfs.debug`).
Will you write a Patch for this issue here, like you
Just for my understanding (I had a look at that Wiki Page but didn't
understand very well) ... Did you create a SRU Bug Template ? I only see
a Patch here and the Upstream Bug Reports.
Is the SRU Bug Template creation part an automatic Pipeline ran by a Bot
?
--
You received this bug notificatio
** Attachment added: "initramfs_v9_new_norap_main_workstation.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776545/+files/initramfs_v9_new_norap_main_workstation.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
So the good news is that the Fix can be replicated on 2 Machines now :).
ZFS Pool gets mounted at 19.679602 Seconds on the Main Workstation,
while it was getting mounted at 20.698236 Seconds on the Secondary
Laptop.
That's a bit surprising since the Main Workstation needs to unlock 2
Disks via Cl
I had to reboot my Main Workstation due to some GTK/Mate/Desktop
Environment Issue (maybe related to NVIDIA Drivers ?).
Anyhow I took the opportunity to implement quickly the fixes we discussed:
- `/usr/lib/dhcpcd/dhcpcd-hooks/30-hostname`: `need_hostname || return 0`
- `/usr/share/initramfs-tools
Now I just tried with `dhclient` on my Main Workstation to check the
time it takes "from scratch" to bring up and get an IP from DHCP on
eno1.
Keep in mind that the "path" to the Router/Gateway (OPNSense Router:
192.168.1.7 master and 192.168.1.8 slave, or 192.168.1.1 Virtual IP) is
much longer (t
** Attachment added: "initramfs_v9_new_norap.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776538/+files/initramfs_v9_new_norap.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Not sure how relevant it is, but **on a booted system**, if I call
`dhclient -v` the Interface gets automatically detected, up and offered
an IP by the DHCP Server in less than 5 seconds (probably even less than
3 seconds ...).
A bit better with `--no-arp` but not by much.
Output of `systemd-anal
** Attachment added: "dmesg_v9_new_noarp.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776537/+files/dmesg_v9_new_noarp.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Yeah, I should have done that. I'm really getting tired and sleepy,
sorry about that.
The 28 seconds is the one we had before as well (the 27-28 s in ... v9,
wasn't it ?
But this error caused the script / function to behave similarly to v4 in
terms of timings. Could this indicate something else (
** Attachment added: "initramfs_v9_new_b.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776402/+files/initramfs_v9_new_b.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Attachment added: "dmesg_v9_new_b.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776403/+files/dmesg_v9_new_b.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Maybe that was the issue indeed ...
Output of `systemd-analyze` after applying the beforementioned fix:
```
Startup finished in 28.780s (kernel) + 24.552s (userspace) = 53.333s
graphical.target reached after 24.517s in userspace.
```
--
You received this bug notification because you are a membe
Probably I had an error in the code, although no error was raised (or at least
I didn't catch it):
```
if [ -z "${DEVICE}" ]; then
# _set_available_devices_to_up
fi
```
An empty if-statement is not valid (at least in BASH it's not
acceptable
About `cut -f1 -d' ' /proc/uptime` ... Wouldn't it be better to also
indicate where we are when that timestamp is registered ?
If it were BASH I'd probably do a echo "${FUNCNAME[0]} - $(cut -f1 -d' '
/proc/uptime)" but in busybox/dash I really do not know ...
--
You received this bug notificatio
Correct me if I'm wrong, but at one point you told me to ADD an `wait_for_udev
10` call before
(the now disabled) call to `_set_available_devices_to_up`.
Attached the latest `/usr/share/initramfs-tools/scripts/functions` just
to make sure we are on the same page with the Modifications.
** Atta
v9_new output of `systemd-analyze`:
```
Startup finished in 47.314s (kernel) + 27.100s (userspace) = 1min 14.415s
graphical.target reached after 27.063s in userspace.
```
Do I need to repeat `v4_new` ? Looking at `dmesg` I don't see a need
since dmesg shows very similar results for v4_new and v9_
** Attachment added: "initramfs_v9_new.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776399/+files/initramfs_v9_new.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Attachment added: "dmesg_v9_new.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776398/+files/dmesg_v9_new.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Attachment added: "initramfs_v4_new.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776397/+files/initramfs_v4_new.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Attachment added: "dmesg_v4_new.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776396/+files/dmesg_v4_new.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Alright ...
So I issued:
- `apt-get install --reinstall initramfs-tools-core`
- `apt-get install --reinstall dhcpcd-base`
v4_new:
- applied `need_hostname || return 0` in
`/usr/lib/dhcpcd/dhcpcd-hooks/30-hostname`
- issued the usual `update-initramfs -k all -u; update-grub; update-initramfs
-k
I think you deleted the _set_available_devices_to_up from the functions
file yourself when you wanted me to test a custom `functions` File.
I cannot find that function call (or function declaration for that
matter) anymore at least ...
I got a bit lost now though ...
So you want me to re-run:
v
Please be aware, not sure if relevant, that I applied a fix in attempt
to speedup the boot time.
As we discussed, this was mainly due to DHCPCD, but before we got to that
conclusion I had attempted to apply the fix described here (a few days ago):
https://github.com/latchset/clevis/issues/289#iss
I cannot compare the timing at `initramfs_v9.debug` because I didn't
save `dmesg` output then.
I only have `dmesg_v4.debug` and `dmesg_v10.debug` / `dmesg_v11.debug`.
But you can argue that 5-6 seconds difference is not that big of a deal.
I could also re-run with v9 and save dmesg this time.
L
** Attachment added: "initramfs_v11.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776176/+files/initramfs_v11.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
And now another attempt with `for ROUNDTTT in 5 5 30 60 90 120; do`
(including also --noipv4ll).
Still approximatively 24 seconds, that seems to be the minimum thus far.
** Attachment added: "dmesg_v11.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5
I did an attempt with `for ROUNDTTT in 5 15 30 60 90 120; do` (including
also --noipv4ll).
This brings it down from 30 seconds to approx. 24 seconds.
** Attachment added: "dmesg_v10.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776173/+files/dmesg
** Attachment added: "initramfs_v10.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776174/+files/initramfs_v10.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Attachment added: "dmesg_v9.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776171/+files/dmesg_v9.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I'd say we went from 45 seconds until ZFS mounting to 30 seconds until
ZFS mounting with --noipv4ll (although I did NOT save all `dmesg` until
now, I am comparing the current `dmesg_v9.debug` with --noipv4ll against
`dmesg_v4.debug` that I had provided before at
https://bugs.launchpad.net/ubuntu/+s
** Attachment added: "initramfs_v9.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776172/+files/initramfs_v9.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
OK I reverted as you instructed.
I then replaced the functions file with your version: `wget
https://launchpadlibrarian.net/728520148/functions -O
/usr/share/initramfs-tools/scripts/functions`
Followed by the usual:
`update-initramfs -k all -u; update-grub; update-initramfs -k all -u;
update-gru
Here it is
** Attachment added: "initramfs_v8.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776089/+files/initramfs_v8.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Here you have it
** Attachment added: "initramfs_v7.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776025/+files/initramfs_v7.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Also the updated /usr/share/initramfs-tools/scripts/functions file since
it changed so much now ...
** Attachment added: "functions_v7.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5776026/+files/functions_v7.debug
--
You received this bug notifica
** Attachment added: "initramfs_v6b.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5775933/+files/initramfs_v6b.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Attachment added: "initramfs_v6a.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5775932/+files/initramfs_v6a.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Sure. Here is the result. Before (v6a) and After (v6b) adding the
"wait_for_udev 10" call after the _set_available_devices_to_up call.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065037
Title:
dh
Also the updated /usr/share/initramfs-tools/scripts/functions file since
it changed so much now ...
** Attachment added: "functions_v6b.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5775934/+files/functions_v6b.debug
--
You received this bug notifi
Here it's the result
** Attachment added: "initramfs_v5.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5775867/+files/initramfs_v5.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Pretty sure the same/similar occurs in Mantic and probably even before
(even if I believe dhcpcd version is different).
But maybe it's too much effort for little benefit to fix those (Mantic
will be anyways EOL July 2024 so just a few months away). I had upgraded
all Systems that I own to Ubuntu 2
Super, many thanks. But I'll basically have to "patch" it locally,
because I guess this will not make it to Ubuntu before 24.10 at best,
right ?
New BUG Report at (hope I did it correctly):
https://bugs.launchpad.net/ubuntu/+source/dhcpcd/+bug/2065037
EDIT 1: I accidentally assigned it to initram
** Attachment added: "dmesg_v4.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+attachment/5775839/+files/dmesg_v4.debug
** Package changed: initramfs-tools (Ubuntu) => dhcpcd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs
Public bug reported:
In automatically encrypted Clevis+Tang unlock of LUKS encrypted device
(dmcrypt/cryptsetup) - on top of which the ZFS Pool for / resides,
dhcpcd is used in order to obtain automatically an IP address during
initramfs boot.
During this phase, dhcpcd is called before interfaces
Alright.
Can you please tell me what I should report in the other bug exactly
though ?
My original idea in the first post ?
>>A possible workaround would be to manually edit
>>/usr/share/initramfs-tools/scripts/functions
>>Changing this:
>>`for ROUNDTTT in 30 60 90 120; do`
>>To this:
>>`for R
** Attachment added: "dmesg_v4.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5775772/+files/dmesg_v4.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
It seems, looking at `dmesg` at least, that the "frozen" / "hang" state
went from 300 Seconds to 45 Seconds.
PS: is it normal that I cannot attach multiple files at once ?
** Attachment added: "initramfs_v4.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachm
Yes, I can confirm. Without a precise clock but just counting in my
head, it's around 45 seconds. Definitively much less than before.
Maybe I'll try to quickly play with PXE Boot / TFTP Server settings on
my OPNSense Router and see if that's responsible for the slowdown
(dhcpcd reported those PXEL
Sure, I can change it.
I'll do the change and reboot ... We'll have an answer in about 30
Minutes.
Another thing that I was thinking about is ... The `/etc/hostname` of
the System is `ubuntuworkstation01` and the DHCP-assigned (or should I
say "registered" ?) hostname is apparently `WORKSTATION01
Seems like only PATH and PWD are set ...
EDIT: correction, these variables are set (I ignored the lowercase ones because
I expected everything in ENV to be uppercase):
```
PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin
PWD=/
hostname_fqdn=no
if_configured=true
if_down=false
if_up=false
ifcarri
Updated /run/initramfs/initramfs.debug with env | sort (and also set -x
immediately afterwards) in dhcpcd Script (v3)
** Attachment added: "initramfs_v3.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5775624/+files/initramfs_v3.debug
--
You received
** Attachment added: "initramfs_v3.debug"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5775623/+files/initramfs_v3.debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Could it be related to the fact that I completely uninstalled `netplan`
from my Ubuntu Desktop ?
I saw lots of References to Netplan in `/usr/share/initramfs-
tools/scripts/functions`.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Sure. Do I also need to add set -x there as well ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064926
Title:
dhcpcd stuck for 5 Minutes (300 Seconds) during Boot Process
(LUKS/Clevis Autounlock
No worries, you are super quick to reply, I appreciate that a lot.
But ... What does this mean ? Is it a BUG that lingered around for 1.5
years without anybody else reporting it ?
Or is it a (mis)configuration Issue somewhere on my side ?
--
You received this bug notification because you are a
I had uploaded it ... it's approximately 300 more lines than before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064926
Title:
dhcpcd stuck for 5 Minutes (300 Seconds) during Boot Process
(LUKS
Updated /run/initramfs/initramfs.debug with set -x in dhcpcd Script
** Attachment added: "Updated /run/initramfs/initramfs.debug with set -x in
dhcpcd Script"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5775551/+files/initramfs_v2.debug
--
You received
Thank you for your quick answer.
a1. Why no network configured ? I think that clevis initramfs unlock
would just use DHCP and get a lease from the DHCP Server. Is an IP entry
really needed ?
https://www.kernel.org/doc/Documentation/frv/booting.txt shows some
examples in specifying ip just by conf
Also adding DMESG Output immediately after Boot Process finishes.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/+attachment/5775478/+files/dmesg.debug
** Tags added: cryptsetup
--
You received this bug notification because you are a memb
Public bug reported:
This is a long-lingering issue, probably affecting Ubuntu 23.04, surely
Ubuntu 23.10 and now surely Ubuntu 24.04.
Due to other Priorities I kept having my PC on Standby/Sleep instead of
turning it off all the time, since I would incur in 5 Minutes (300
Seconds) Boot being fro
Public bug reported:
Italian Message:
Si è verificato un problema irresolubile durante il calcolo
dell'avanzamento.
Ciò può essere causato da:
* Pacchetti software non ufficiali non forniti da Ubuntu
Utilizzare lo strumento «ppa-purge» incluso nel pacchetto
ppa-purge per rimuovere software ins
Fixed in 1.4.3-5, I think.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2047147
Title:
mmebstrap creates non-usr-merged Ubuntu releases
To manage notifications about this bug go to:
https://bugs.l
Public bug reported:
Il pacchetto mysql-server-8.0 non è ancora configurato.
dpkg: errore nell'elaborare il pacchetto mysql-server (--configure):
problemi con le dipendenze - lasciato non configurato
Elaborazione dei trigger per man-db (2.9.4-2)...
Segnalazione apport non scritta poiché il mess
I'm experiencing the same issue on my Ubuntu 22.04 LTS server with Budgie
desktop.
Both shutdown and reboot hang, both from GUI and command line.
This happens most of the time, but about once in 8-10 times shutdown or reboot
end regularly.
Operating System: Ubuntu 22.04 LTS
I send you another type of file .
** Attachment added: "screenshot help office"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1970757/+attachment/5585726/+files/Schermata%20da%202022-05-02%2007-55-39.png
--
You received this bug notification because you are a member of Ubuntu
Bu
Public bug reported:
When I open libreoffice help (F1) in some reports (as pages ""PDF Export
links or "Filter screenshots") I have no specific images but only a
generic icon (see attached PDF)
Ubuntu 21.10 Lenovo Ideapad 5
** Affects: libreoffice (Ubuntu)
Importance: Undecided
Sta
This is by design. See: https://lists.debian.org/debian-
python/2022/03/msg00039.html
There was a Debian bug tracking the effect on Meson, apparently the issue was
fixed upstream.
See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009097#32
** Bug watch added: Debian Bug tracker #1009097
** Also affects: distro-info-data (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: distro-info-data (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: distro-info-data (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects
FFe approved.
** Changed in: cl-plus-ssl (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/1960615
Title:
[FFe] cl-plus-ssl does not support OpenSSL 3.0
To man
LGTM, approved.
** Changed in: lxc (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/1967620
Title:
[FFe] LXC 5.0 LTS
To manage notifications about this bug go
** Changed in: python-molotov (Ubuntu)
Status: Fix Committed => 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/1947751
Title:
Python 3.10 is not supported
To manage notifications
Fixed in
python-molotov (2.1-3) unstable; urgency=medium
* Team upload.
[ Debian Janitor ]
* Remove obsolete field Name from debian/upstream/metadata (already present in
machine-readable debian/copyright).
[ Stefano Rivera ]
* Patch: Python 3.10 support (Closes: #1001423
FYI, I filed https://salsa.debian.org/cpython-
team/python3/-/merge_requests/18 including a fix 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/1962791
Title:
python3 -m venv installs pip to
Fixed in 3.10.2-3.
** Changed in: python3.10 (Ubuntu)
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/1940705
Title:
distutils and sysconfig returns unexpecte
1 - 100 of 5288 matches
Mail list logo
