date:20240225

[Bug 2054814] Re: lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

2024-02-25 Thread Simon Déziel

I got the initial assessment wrong, thanks Heinrich for clearing up that
confusion :)


Here is what happened here:

On Jammy, lxd-agent-loader (0.5) is configured to start lxd-agent.service when 
the multi-user.target was reached coupled with a 
ConditionPathExists=/dev/virtio-ports/org.linuxcontainers.lxd
This means it would do nothing if that virtio-ports device was missing.

On Noble, lxd-agent-loader (0.6) was changed to have udev start lxd-
agent.service only when it sees a virtio-ports LXD knows. Along with
that change, the ConditionPathExists was removed as no longer relevant.


Heinrich did a distro-upgrade moving lxd-agent-loader from 0.5 -> 0.6 but this 
left behind the following symlinks:

```
/etc/systemd/system/multi-user.target.wants/lxd-agent.service
/etc/systemd/system/multi-user.target.wants/lxd-agent-9p.service
```

Causing lxd-agent.service to always want to start, even if the virtio-
ports is not there, thus causing this bug/failure to start lxd-
agent.service.


The fix will be to have the package cleanup the old symlinks left in the 
multi-user.target.wants directory.

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

Title:
  lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2054814/+subscriptions


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

[Bug 2039571] Re: systemd-modules-load fails on Azure 23.10 images on arm64

2024-02-25 Thread Nick Rosbrook

Is this still an issue on 24.04?

** Also affects: systemd (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

** Changed in: systemd (Ubuntu Mantic)
   Importance: Undecided => Low

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

Title:
  systemd-modules-load fails on Azure 23.10 images on arm64

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


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

[Bug 882255] Re: No administrative actions possible (password refused) after enabling passwordless login

2024-02-25 Thread ravi mano

Stragely though, when I reboot my ubuntu and mosue-click some times out of my 
ubuntu and inside my VmWare player randomly some times, it allowed me in. and 
also on reboot, it works with an Enter
( i.e  removing password effected ).

Also i tried to change password with passwd command giving the same
string I had used earlier, as new password. Strangely, this fails saying
"please enter a longer password". Then why was I allowed to be using a
"shorter" password all these days ?

My config:
--
anon@ubuntu:~$ 
anon@ubuntu:~$ uname -as
Linux ubuntu 4.15.0-142-generic #146~16.04.1-Ubuntu SMP Tue Apr 13 09:27:15 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux
anon@ubuntu:~$ 
anon@ubuntu:~$ 

anon@ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.7 LTS
Release:16.04
Codename:   xenial
anon@ubuntu:~$


VmWare player version: ( not related though )
VMware® Workstation 16 Pro
16.1.2 build-17966106

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

Title:
  No administrative actions possible (password refused) after enabling
  passwordless login

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


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

[Bug 2054845] [NEW] mlxbf-gige: support bobcat

2024-02-25 Thread Asmaa Mnebhi

Public bug reported:

SRU Justification:

[Impact]

Bobcat is a new board which doesn't have an external PHY connected to
the OOB. There are no MDIO busses involved and no PHY involved. The OOB
is directly connected to the switch (MAC to MAC). SO we need to use the
linux fixed phy to be able to emulate the mdio behavior and load the
ethernet driver.

[Fix]

* Register the fixed-phy register in the case of the bobcat.

[Test Case]

* Important: For testing on the bobcat board, make sure the corresponding UEFI 
image is also loaded, otherwise, the oob driver will fail to load.  For other 
board, it is backward compatible.
* Check if the mlxbf-gige is loaded on bobcat
* Check that it is using the fixed-phy via dmesg | grep PHY
* check that the oob interface is pingable
* check that files can be copied over via oob interface
* rmmod/modprobe
* ifconfig up/down
* reboot test

[Regression Potential]

* Redo all the OOB testing on other boards (moonraker) and make sure the
bobcat changes dont trigger any regressions.

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

Title:
  mlxbf-gige: support bobcat

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


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

[Bug 2054845] Re: mlxbf-gige: support fixed phy for Bobcat

2024-02-25 Thread Asmaa Mnebhi

** Summary changed:

- mlxbf-gige: support bobcat
+ mlxbf-gige: support fixed phy for Bobcat

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

Title:
  mlxbf-gige: support fixed phy for Bobcat

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


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

[Bug 2041732] Re: Touchpad is extra-sensitive on Wayland

2024-02-25 Thread Connor Nolan

I just loaded up the latest Ubuntu 24.04 daily build on a USB, and I can
reproduce the bug on it 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/2041732

Title:
  Touchpad is extra-sensitive on Wayland

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


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

[Bug 2054785] Re: cloud-init destroys the password of existing 'ubuntu' account

2024-02-25 Thread James Falcon

I believe that cloud-init is working as intended here. I'm unfamiliar
with the Ubuntu Image tool, but it looks like there is overlap between
the user-creation from that tool and cloud-init.

When cloud-init runs, it will by default create a distro-default user with no
password and password login disabled. On Ubuntu, this user is 'ubuntu'. This
behavior can be overridden using user data alongside the network-config.
The user data file is described here:
https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html#file-formats

Whereas the user data for creating users is described here:
https://cloudinit.readthedocs.io/en/latest/reference/modules.html#users-and-groups

It describes how the default user can be overridden.

Based on this, I think I can explain your 3 scenarios:
1. Cloud-init created user ubuntu with no password which somehow superseded the
Ubuntu image user creation.
2. 1 happened, but since you also specified another user, that user got created
and so works as expected.
3. With no NoCloud seed data, cloud-init didn't run and didn't attempt to
create any default user.

Does that help?

** Changed in: cloud-init (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/2054785

Title:
cloud-init destroys the password of existing 'ubuntu' account

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2054785/+subscriptions

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

[Bug 2041732] Re: Touchpad is extra-sensitive on Wayland

2024-02-25 Thread Connor Nolan

Hmm, this might be scaling related. I set my laptop to 100% scaling
(instead of 200%) and the bug seemed to disappear.

Unfortunately, using 100% scaling on a HiDPI laptop is not a practical
solution.

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

Title:
  Touchpad is extra-sensitive on Wayland

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


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

[Bug 2041732] Re: Touchpad is extra-sensitive on Wayland

2024-02-25 Thread Connor Nolan

Yup, I just tested with 300% scaling and the bug is even worse. I think
something's being multiplied by the scaling factor on Wayland that
shouldn't be.

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

Title:
  Touchpad is extra-sensitive on Wayland

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


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

[Bug 2051939] Autopkgtest regression report (autopkgtest/5.32ubuntu3~23.10.1)

2024-02-25 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted autopkgtest (5.32ubuntu3~23.10.1) for 
mantic have finished running.
The following regressions have been reported in tests triggered by the package:

surf/2.1+git20221016-5 (arm64, armhf)


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/mantic/update_excuses.html#autopkgtest

[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/2051939

Title:
  [SRU exception] backport 5.32 to Jammy and Mantic

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


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

1 2 3 4 5 >

1 - 100 of 402 matches

Mail list logo