An upload of coreutils to lunar-proposed has been rejected from the
upload queue for the following reason: "lunar EOL in 9 days; no more
SRUs".
** Changed in: coreutils (Ubuntu Lunar)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
All autopkgtests for the newly accepted util-linux (2.38.1-4ubuntu1.1) for
lunar have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/252.5-2ubuntu3 (amd64, arm64, ppc64el, s390x)
Please visit the excuses page listed below and investigat
** Changed in: util-linux (Ubuntu Lunar)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2019856
Title:
Add missing ARM-cores t
All autopkgtests for the newly accepted util-linux (2.38.1-4ubuntu1.1) for
lunar have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/252.5-2ubuntu3 (amd64, arm64, ppc64el, s390x)
Please visit the excuses page listed below and investigat
All autopkgtests for the newly accepted util-linux (2.38.1-4ubuntu1.1) for
lunar have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/252.5-2ubuntu3 (amd64, arm64, ppc64el, s390x)
Please visit the excuses page listed below and investigat
All autopkgtests for the newly accepted util-linux (2.38.1-4ubuntu1.1) for
lunar have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/252.5-2ubuntu3 (amd64, arm64, ppc64el, s390x)
Please visit the excuses page listed below and investigat
** Description changed:
Hi,
I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the
rabbit hole led me here.
Here is a very quick reproducer, first:
Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine:
```
$ cd /tmp
$ autopkgtest-bui
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2049552
Title:
[noble] ftbfs
8.2312.0-3ubuntu1 was sponsored, setting status to fix committed and
unsubscribing ubuntu-sponsors.
** Changed in: rsyslog (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to r
Public bug reported:
I am no longer able to change pulseaudio card profile from a2dp_sink to
handsfree_head_unit
It used to work before running apt upgrade where I got a new kernel
6.5.0-14-generic #14~22.04.1-Ubuntu installed. As you can see below - and
actual experience with the headphones,
** Changed in: iptables (Ubuntu Jammy)
Assignee: (unassigned) => Graham Inggs (ginggs)
** Changed in: iptables (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptabl
I sponsored the upload of iptables 1.8.7-1ubuntu5.2, now waiting for approval
in the Jammy queue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/2049318
Title:
[SRU] fre
** Changed in: openssh (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2049552
Title:
[noble] ftbfs with new zlib 1.3
Status
Looking at the attached screenshot, it covers everything in the test
plan above.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I have the `thermald` service disabled using the commands you provided,
and after 5 reboots and 1 shut down, the problem still persists.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpa
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: eglibc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net
This bug was reported more than 15 years ago.
https://sourceware.org/bugzilla/show_bug.cgi?id=6050
But there is a patch for it since 2015
https://sourceware.org/legacy-ml/libc-alpha/2015-08/msg00297.html
Who maintains libc-bin? Could you please apply these patches?
$ iconv -V
iconv (Ubuntu GLIBC
After further analysis, it looks like the trigger=wpa/2:2.10-21 highly
increases the likeliness of the error to occur.
At this point, I do not think that there is any regression in wpa
2:2.10-21 compared to 2:2.10-20. The changeset is minimal. OTOH I think
the trigger=wpa/... alters the order of e
Public bug reported:
Installed fresh, artifacts started after update. Happens when
interacting gnome; menus, changing workspaces, etc. Attached screencast
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Unam
** Merge proposal linked:
https://code.launchpad.net/~ogayot/britney/+git/britney/+merge/458822
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2048388
Title:
Test suite oft
Any testing is helpful, thanks!
I've now ran tests on Intel DG2/Arc, and things work fine at least on
6.5 kernel. 6.1 (OEM) fails to start gdm/X with a trace from the DRI
driver, need to investigate if that's a regression or not.
--
You received this bug notification because you are a member of
This sounds like a bug with your VPN. How is it trying to change the DNS
servers? If they are trying to edit /etc/resolv.conf directly, that is
not compatible with systemd-resolved. Instead, they should use the DBus
API for systemd-resolved, or use `resolvectl`, etc.
** Changed in: systemd (Ubuntu
Verification Report
===
The test is conducted on an RK3399 device (with 4x ARM Cortex-A53 cores
+ 2x ARM Cortex-A72 cores).
Test (1) original Rust program test (associated-types.rs)
-
GDB 12.1-0ubuntu1~22.04 (unpatched)
Rus
*** This bug is a duplicate of bug 1922414 ***
https://bugs.launchpad.net/bugs/1922414
** This bug has been marked a duplicate of bug 1922414
Xorg scripts fail with "has_option: command not found"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
** Tags removed: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1922414
Title:
Xorg scripts fail with "has_option: command not found"
Status in Light Display Manager:
** Tags added: noble
** Summary changed:
- nano is not available in Jammy i386
+ nano is not available in on i386
** Summary changed:
- nano is not available in on i386
+ nano is not available on i386
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
Upstream Nano doesn't seem interested.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
https://bugs.launchpad.net/bugs/782355
Title:
Invoke sudo and present password prompt when permission is denied to
wri
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nano (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
https://bugs.launchpad.net/bug
** Tags added: focal jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
https://bugs.launchpad.net/bugs/1998592
Title:
in specific situations, nano can eat characters
Status in nano package in Ubuntu:
Wily is long gone.
** Changed in: nano (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
https://bugs.launchpad.net/bugs/1539305
Title:
package nano 2.4.2-1 failed to in
** Changed in: nano (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
https://bugs.launchpad.net/bugs/1361131
Title:
constantly flashing bright green while typing
Status
Public bug reported:
This package being missing breaks several packages people currently use, and
breaks compilation of the Android Open Source Project for every current release.
https://answers.launchpad.net/ubuntu/+source/ncurses/+question/707838
Google has started work on deprecating libncurs
Successful building with the fix as patch suggested by Andreas:
https://launchpad.net/~mirespace/+archive/ubuntu/openssh-
lp2049552-ftbfs-with-zlib/+sourcepub/15701298/+listing-archive-extra
Running tests...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/openssh/+git/openssh/+merge/458841
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2049552
Public bug reported:
I ran ran apport-bug xorg and it took me here. Trying to figure out an
issue where any time I open a game, it crashes and gives the error
message "GPU not detected". From everything I've tried it seems like the
computer has no problem detecting the GPU and it seems to be worki
Thanks for the bug report. I've watched the attached screencast a few
times and can't see any artifacts in it. This is unsurprising given how
screen recording works. You will probably need to take a video of the
screen externally, like with a phone.
** Summary changed:
- screen artifacts especia
Public bug reported:
Release: Ubuntu Noble Dev Branch
the location of bluetoothd was just changed to
/usr/libexec/bluetooth/bluetoothd
this causes bluetooth to fail to start since something is still looking
for the old location
Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Blu
** Description changed:
Release: Ubuntu Noble Dev Branch
the location of bluetoothd was just changed to
/usr/libexec/bluetooth/bluetoothd
this causes bluetooth to fail to start since something is still looking
for the old location
Jan 17 21:23:26 switch systemd[1]: Starting bl
Public bug reported:
This is a tablet computer with a detachable keyboard and touchpad. When
I close and open the lid, the computer goes to sleep and wakes up as
expected, but the entire keyboard portion does not. The backlight stays
off, and keys and touchpad are unresponsive. Removing and reatta
Thanks for the bug report. It appears you no longer have an nvidia
kernel driver for the current kernel version. I'm also not sure if such
a newer kernel can be supported by the old nvidia 390 driver.
This might just be bug 1975650 so please try reinstalling the driver
using the 'Additional Driver
Thanks for the bug report. It looks like the i915 kernel graphics driver
is crashing a lot, which may or may not be related. Please run these
commands in a Terminal:
sudo apt install mesa-utils
glxinfo > glxinfo.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu)
Am I correct in assuming the problem goes away after a reboot?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2049708
Title:
bluez bluetoothd unable to locate executable
St
5.71-1ubuntu3:
Binary: /usr/libexec/bluetooth/bluetoothd
SystemD: system/bluetooth.service:ExecStart=/usr/libexec/bluetooth/bluetoothd
So that's consistent, but it sounds like you might have encountered an
upgrade bug and your systemd was looking in the old path? I'm guessing
there should be a sy
I tried daily build version 2024-01-17, but the bug is still there.
Laptop is Fujitsu WUA/H1. The solution is to restart subiquity snap
service.
https://askubuntu.com/questions/1500457/ubuntu-desktop-
installer-24-04-stuck-on-
installation?noredirect=1#comment2629138_1500457
--
You received this
You are not.
I have rebooted multiple times and continue to get this message in journalctl
(yes it's a new entry on each boot).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/
I can't seem to reproduce any such issue with 2024-01-17 here.
Please log a new bug, although it might be bug 2049617 as mentioned in
https://discourse.ubuntu.com/t/help-with-edubuntu-desktop-
installer/41683
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
Perhaps try a recursive grep for '/usr/lib/bluetooth/bluetoothd'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2049708
Title:
bluez bluetoothd unable to locate executable
There are still regressions in the following packages:
cython-legacy/0.29.36-3ubuntu1 (armhf only)
cython/3.0.7-2ubuntu1 (armhf only)
ipykernel/6.28.0-0ubuntu1
ironic-python-agent/9.1.0-1ubuntu1 (never been in Debian testing)
jupyter-client/8.6.0-0ubuntu1
numpy/1:1.24.2-2
python-memory-profiler/0.
48 matches
Mail list logo
