While I cherry-picked the fix, as this only affects Debian, I'm going to
mark the bug as Won't Fix.
** Changed in: software-properties (Ubuntu)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
** Changed in: software-properties (Ubuntu)
Importance: High => Low
** Changed in: software-properties (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Updated the bug tasks to show while this is fixed in lunar, we don't
know what fixed it.
** Package changed: gnome-shell (Ubuntu) => ubuntu
** No longer affects: gjs (Ubuntu)
** No longer affects: mozjs102 (Ubuntu)
** No longer affects: network-manager (Ubuntu)
--
You received this bug notifi
> Jun 06 01:46:37 big-bucks systemd-tmpfiles[536]: Detected unsafe path
transition / (owned by beland) → /var (owned by root) during
canonicalization of /var.
Well, that's fairly clear - you have insecure permissions on your root
filesystem and systemd-tmpfiles is failing to act. You'll want to
** Attachment added: "Output of "journalctl -b 0 --no-pager -lu
systemd-tmpfiles-setup""
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2023001/+attachment/5678283/+files/journalctl.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
systemctl status systemd-tmpfiles-setup says:
systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static)
Active: active (exited) since Tue 2023-06-06 01:46:37 EDT; 23h ago
Docs: man:tmpfiles.d
I was finally able to get the browser approach to work (advice: there is
a little slider at the very top of the gnome-extensions-app GUI that you
have to click to get the extensions to activate, or else you begin to
lose your mind thinking that you have to install it manually from source
because cl
This bug was fixed in the package console-setup - 1.221ubuntu1
---
console-setup (1.221ubuntu1) mantic; urgency=medium
* Merge with Debian unstable (LP: #2020749). Remaining changes:
- debian/clean: Delete Keyboard/tree-keymaps/ on clean
- Add an apport hook
- If the loc
…yes please, sru emergency, ubuntu 20.04 LTS variants reach EOL.
It's been more than a year now color printing is out of order in some
context.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.laun
Hi Isaac,
I'm at end of my shift so don't have time for a full review, just a few
notes before I hand-off to the next patch pilot:
- In your changelog entry, please reference this bug report, i.e.:
- I'd recommend making your PPA version be "1:1.35.0-4ubuntu2~ppa5"
- Name your patch
Hi Dave,
Thanks for including the packaging branch in addition to the ppa and
debdiff, that definitely helps with the review! Btw, since you use
packaging branches, you can file 'Merge Proposal' requests that are
helpful for structuring reviews. When creating an MP for a merge
against debian uns
Opened a bug task on systemd as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2023001
Title:
sshd not starting because of missing /run/sshd
Status in openssh packa
If you saw this problem after reboots, then the question is why tmpfiles
handling is not working as expected.
I don't know if these jobs log anything relevant, but a place to start
is:
- output of systemctl status systemd-tmpfiles-setup
- output of journalctl -b 0 --no-pager -lu systemd-tmpfile
I don't know whether sshd was running immediately after the install; I
noticed this problem a couple reboots after the install process was
complete. Are there any logs I can check that would be helpful to
reconstruct the sequence of events?
--
You received this bug notification because you are a
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu/+source/cron/+git/cron/+merge/444197
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/2023077
Title:
Pleas
This bug affects me too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2023008
Title:
cannot install libegl-mesa0 on 22.04.2 LTS
Status in mesa package in Ubuntu:
New
Bu
Public bug reported:
Tracking bug.
** Affects: cron (Ubuntu)
Importance: Undecided
Assignee: Nick Rosbrook (enr0n)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https:
I do not believe the ganeti/3.0.2-3 (arm64, ppc64el) failures on Lunar
are caused by the openssh update. In both failures[1][2], the
__main__.TestX509Certificates.test and
__main__.TestX509Certificates.testNoEmpty unit tests fail. This exact
same failure can be seen in an earlier migration-referenc
I have verified the fix using util-linux 2.34-0.1ubuntu9.4 from focal-
proposed:
$ qemu-img create -f qcow2 test.img 20G
Formatting 'test.img', fmt=qcow2 cluster_size=65536 extended_l2=off
compression_type=zlib size=21474836480 lazy_refcounts=off refcount_bits=16
$ qemu-system-x86_64 -enable-kvm
Did this happen before or after you rebooted into Ubuntu 23.04?
If before the reboot, /run/sshd should already have been present on the
system, created by the previous version of
/lib/systemd/system/ssh.service.
If after the reboot, it should be created by
/usr/lib/tmpfiles.d/openssh-server.conf,
** Changed in: gdb (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1902225
Title:
SRU: update gdb 8.1.1 for 18.04 LTS
Status in gdb pack
There's now CUPS 2.4.4 with a hotfix for a segfault.
https://github.com/OpenPrinting/cups/releases/tag/v2.4.4
--
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/1971242
Title:
p
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
I could not replicate the crash in currently supported versions (focal,
jammy, kinetic, lunar, manti
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 14.04 (trusty) reached end-of-standard-support on Apri
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
I could not replicate that bug in curr
This bug is awaiting verification that the linux-azure/5.4.0-1110.116
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.4.0-1104.112
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, ch
Public bug reported:
Some of the cyrus-sasl2 dep8 tests have never passed on ppc64el or
s390x.
s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-
mantic/mantic/s390x/c/cyrus-sasl2/20230606_065455_398c1@/log.gz
saslauthdFAIL non-zero exit status 253
shared-secret-mechs FAIL n
This was fixed in debian and synced to ubuntu in
https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg1-1.
** Changed in: cyrus-sasl2 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launc
(In reply to Cameron Berkenpas from comment #765)
> Alas, you are correct. The good news is that this is being worked on for
> the Legion... But it seems to be for the latest model of the Legion
> (which does haven't Cirrus Logic, it has TI smart amps IIRC). I have the
> 2nd to latest (which I t
I haven't been able to get this working properly. I was able to get
sound with this approach a few months ago, but I was getting "AMP short"
errors, which I'm sure can't be good.
On 6/5/23 06:45, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comme
Conflict Report:
gdb
Sat May 13 15:44:04 2023
Below now follows the report of the automated merge of the Ubuntu
changes to the gdb source package against the new Debian version.
This file is designed to be both human readable and machine-parseable.
Any line beginning with four sp
Public bug reported:
The upstream version 13.1-3 should be merged into mantic. The current
version is 13.1-2ubuntu2.
See the merge conflict report: https://merges.ubuntu.com/g/gdb/REPORT
Note: this is a tracking bug
** Affects: gdb (Ubuntu)
Importance: Undecided
Assignee: Dominik Vier
** Changed in: gdb (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1992947
Title:
gdb fails in Ubuntu-22.04
Status in gdb package in
** Description changed:
# Summary
`apt install libegl-mesa0` does not install it due to a dependency
conflict in the apt repo.
libegl-mesa0 has dependency to explicit versions of:
* libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1)
* libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1)
But the l
Public bug reported:
# Summary
`apt install libegl-mesa0` does not install it due to a dependency
conflict in the apt repo.
libegl-mesa0 has dependency to explicit versions of:
* libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1)
* libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1)
But the latest in ubuntu repos a
Thank you for your bug report. Could you after the system has restarted do
$ journalctl -b -1 > journal.log
and add the log to the report?
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification bec
37 matches
Mail list logo
