All autopkgtests for the newly accepted python-tz (2022.7.1-3ubuntu0.1) for
lunar have finished running.
The following regressions have been reported in tests triggered by the package:
cinder/2:22.0.0-0ubuntu1.1 (armhf)
ironic/1:21.4.0-0ubuntu1 (armhf)
python-caldav/0.11.0-1 (arm64)
Public bug reported:
Los siguientes paquetes tienen dependencias incumplidas:
libcc1-0 : Depende: gcc-12-base (= 12.1.0-2ubuntu1~22.04) pero 12.2.0-14 va a
ser instalado
libitm1 : Depende: gcc-12-base (= 12.1.0-2ubuntu1~22.04) pero 12.2.0-14 va a
ser instalado
liblsan0 : Depende: gcc-12-base
All autopkgtests for the newly accepted iptables (1.8.4-3ubuntu2.1) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
nova/2:21.2.4-0ubuntu2.3 (armhf)
systemd/245.4-4ubuntu3.21 (armhf, ppc64el, s390x)
ufw/0.36-6ubuntu1 (amd64)
All autopkgtests for the newly accepted iptables (1.8.4-3ubuntu2.1) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
nova/2:21.2.4-0ubuntu2.3 (armhf)
systemd/245.4-4ubuntu3.21 (armhf, ppc64el, s390x)
ufw/0.36-6ubuntu1 (amd64)
I thought as part of this work we agreed to always unpack tar with
xattrs, but i'm not sure how to check if this was done or in place. will
investigate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
I cleared the DEP8 failures:
- nova: retry fixed it
- west-chamber/i386: migration-reference/0 is also failing, so that cleared it
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
An upload of gst-plugins-ugly1.0 to jammy-proposed has been rejected
from the upload queue for the following reason: "Request for test cases
on gst-plugins-ugly1.0 has gone unanswered since last July".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
An upload of gst-python1.0 to jammy-proposed has been rejected from the
upload queue for the following reason: "rejected as discussed on the
bug".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu.
Affects my Brother QL-800 label printer too, just after the upgrade to 23.04.
My Xerox Phaser-3010 printer is fine although connected to the same computer.
Setting the printer to mirror-print in settings won't help.
--
You received this bug notification because you are a member of Ubuntu
Touch
I've sent a fix related to this issue:
https://github.com/lxc/lxc/commit/8575ffeb7fc04b96e1d7bc736afb46670c5f7631
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1979258
Title:
This seems to be logged after entering username and clicking next:
May 16 19:02:28 maunium kernel: WebKitWebProces[560981]: segfault at
563a37787e6d ip 563a37787e6d sp 7ffea85fdc98 error 14 in
WebKitWebProcess[563f5260e000+1000] likely on CPU 15 (core 7, socket 0)
May 16
All autopkgtests for the newly accepted openssh (1:9.0p1-1ubuntu7.2) for
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.50.2-2 (ppc64el)
hg-git/0.10.4-3 (amd64, arm64, armhf, ppc64el, s390x)
nova/3:26.1.0-0ubuntu2.1 (armhf)
** Also affects: util-linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: util-linux (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Thank you for reporting a bug in ufw. I've committed a fix for this to
add get_rules_ipv4() and get_rules_ipv6().
** Changed in: ufw
Importance: Undecided => Wishlist
** Changed in: ufw
Status: New => Fix Committed
** Changed in: ufw
Assignee: (unassigned) => Jamie Strandboge
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
ad. 1 not sure whether that's the one but I only see google chrome
beside
-rw-r- 1 mastier whoopsie 11313793 May 15 17:43
_usr_bin_gnome-control-center.1000.crash
-rw-r--r-- 1 mastier whoopsie0 May 15 17:43
_usr_bin_gnome-control-center.1000.upload
-rw--- 1 whoopsie
Public bug reported:
[Impact]
When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report
a model name:
Vendor ID: ARM
Model: 0
[Fix]
Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The
commit below adds the specific codes missing from Jammy's
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Thank you for your bug report. Could you do
$ journalctl -f
then trigger the bug and see if any error is printed in the journal log?
** Changed in: gnome-online-accounts (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-online-accounts (Ubuntu)
Status: Confirmed => Incomplete
Thank you for your bug report. Could you give some details on your
system?
The error is
> Failed to stop bluetooth.service: Unit bluetooth.service not loaded.
it seems bluetooth isn't active. It also look from the report that you
have the bluez snap installed? Did you disable the bluetooth deb
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
@Steve / @Vorlon
As outlined above we still can't see the diff in dependencies due to LTO.
But I'm sure you have seen it or you wouldn't have said so and we want to spot
where in our work the mistake was ...
Therefore let me ask - was that a local build that you did or is that somewhere
we
Hmm - odd,
Michal has checked the files and the build logs as he outlined above.
And in addition to all those checks being done, if we just grep for all final
dependencies and compare there is no difference (other than a glibc min version
level).
I know names are not too helpful:
- ~ppa1 =
Hi - the majority of engineers where on Sprints in the recent weeks, so
we were a bit short on staff - apologize. This bug got already assigned.
But to get you unblocked, you may just remove (sudo apt remove ...) the package
in question (and the one that has it as dependency), since they are not
25 matches
Mail list logo
