3.0.6 include this fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1994165
Title:
CMS_final: do not ignore CMS_dataFinal result
Status in openssl package in Ubuntu:
Public bug reported:
When using a custom image with the notify-send command (e.g. notify-send
-i /home//images/test.png "test") the image, once loaded, is
not refreshed. This can be tested by running a command such as the
example one, then overwriting "current.png" with a different image, and
run
Typo? I'd expect 'Just "w" is enough' ;-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1993572
Title:
samba profile: missing rule for mkdir /var/cache/samba/printing
S
You can close this. I did an upgrade from ubuntu 18.04 since I initially
upgraded to 22.04 from this version, and openssh-server's sockets didn't
break the install.
If the error happened it's either related to the Ubuntu 18.04
install/image that was provided by my host or some freak corruption. If
/var/cache/samba/printing/ w, # without r,
Just "r" was enough indeed!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1993572
Title:
samba profile: missing rule for mkd
The attachment "openssh_9.0p1-1ubuntu8.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" t
** Description changed:
After the fix for bug #1990692, one more rule is needed it seems.
I put all samba profiles in enforce mode, and when I ran that final
- command, got an error and an apparmor denied message:
+ rpcclient command, got an error and an apparmor denied message:
+
+ Prep:
seems like a hardware problem affecting as it affects only one of the
two GPU fans. I think that this bug report can be disregarded.
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
name="apparmor/.null" is used to remove access to an already open file
that is being inherited and should no longer be available. Whether
because policy doesn't allow it. AppArmor can't just close the file
because the fd for the file might have meaning and closing the file
would free up the fd slot
** Description changed:
- The listed resolution 1400x900 (3:2) it's not correct: my monitor is 16:10
and I can see black bars.
- I suppose the real resolution is 1400x960 (3:2), but the actual 1400x900
(16:10) is missing.
+ The listed resolution 1440x900 (3:2) it's not correct: my monitor is 16:
aa-disable calls apparmor_parser, so this is most likely a problem
between apparmor_parser and the kernel. I've updated the summary
accordingly.
** Summary changed:
- "aa-disable" fails on autopkgtest.u.c (armhf)
+ parser fails to unload profile via "aa-disable" on autopkgtest.u.c (armhf) -
"Per
Based on your DENIED message, I wonder if read (= directory listing)
permissions are really needed, or if
/var/cache/samba/printing/ w, # without r
would be enough. Can you please test and report back?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
A few comments and explanations:
> As part of that it locks down /dev to read-only:
> /dev/ r,
>
> However that also means /dev/pts is read-only, hence the error above denies
> write access.
The rule for /dev/ only allows reading the directory listing of /dev/.
It doesn't say or allow anything
** Patch added: "openssh_9.0p1-1ubuntu8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+attachment/5627076/+files/openssh_9.0p1-1ubuntu8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to open
** Description changed:
[Impact]
When attempting to authenticate against a Windows Active Directory
server configured to require SASL channel binding over SSL/TLS ldap
connections (ldaps), authentication will fail stating invalid
credentials as the cause.
This is due to cyrus-sas
** Description changed:
There is a issue rsyncing to a rsync module with the error: failed:
Read-only file system (30)
Both server are ubuntu 22.04.1 with rsync version 3.2.3-8ubuntu3
I tried with no success "use chroot" different value options
Permissions are OK in the end side
I tried an unbind/bind with the xhci_hcd driver as explained here:
https://stackoverflow.com/questions/35605178/ubuntu-sound-network-usb-
trouble-after-suspend-how-to-restart
It didn't help.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
There is a issue rsyncing to a rsync module with the error: failed:
Read-only file system (30)
Both server are ubuntu 22.04.1 with rsync version 3.2.3-8ubuntu3
I tried with no success "use chroot" different value options
Permissions are OK in the end side
Installing manual
** Description changed:
+ [Impact]
+
+ Users with /etc/ssh/sshd_config's that contain ListenAddress entries
+ with the port specified will not be migrated to socket-activated ssh
+ correctly, or may be migrated when they should not be (e.g. if
+ ListenAddress, with a port number, is specified mor
** Also affects: openssh (Ubuntu Kinetic)
Importance: Critical
Status: Triaged
--
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/1993478
Title:
package openssh-serv
Public bug reported:
The listed resolution 1400x900 (3:2) it's not correct: my monitor is 16:10 and
I can see black bars.
I suppose the real resolution is 1400x960 (3:2), but the actual 1400x900
(16:10) is missing.
I updated some packages today and the issue came after reboot:
2022-10-26 16:48
Public bug reported:
Everything related to settings in the newly released Ubuntu 22.10 is
very laggy. It might work fine for a while, then when I try scrolling,
it laggs and nothing happens for a few seconds. It might even crash.
This happens in Settings, in Extension Manager or some GS extension'
Incomprehensible, a new reboot solved my issue
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1971984
Title:
pcscd 1.9.5-3 do not start automatically, only manual
Statu
"git tag --contains 67c0460b89cc1b0644a1a59af78284dfd8d720af" shows that
no release contains the upstream commit yet.
** Description changed:
https://github.com/openssl/openssl/pull/18876
The CMS_dataFinal result is important as signature may fail, however, it
is ignored while returning
Hello,
I am facing a very similar issue
I managed to make it work on fresh install but it stopped working after a reboot
The two commands above do not resolve on my laptop
$ sudo service pcscd status
○ pcscd.service - PC/SC Smart Card Daemo
** Changed in: presage (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to presage in Ubuntu.
https://bugs.launchpad.net/bugs/1988196
Title:
presage: ftbfs with GCC-11
Status in pres
This bug was fixed in the package tzdata - 2022e-0ubuntu0.20.04.0
---
tzdata (2022e-0ubuntu0.20.04.0) focal; urgency=medium
* New upstream releases (LP: #1992692):
- Palestine transitions are now Saturdays at 02:00. This means 2022 falls
back 10-29 at 02:00, not 10-28 at 0
This bug was fixed in the package tzdata - 2022e-0ubuntu0.18.04.0
---
tzdata (2022e-0ubuntu0.18.04.0) bionic; urgency=medium
* New upstream releases (LP: #1992692):
- Palestine transitions are now Saturdays at 02:00. This means 2022 falls
back 10-29 at 02:00, not 10-28 at
The verification of the Stable Release Update for tzdata has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
This bug was fixed in the package tzdata - 2022e-0ubuntu0.22.04.0
---
tzdata (2022e-0ubuntu0.22.04.0) jammy; urgency=medium
* New upstream releases (LP: #1992692):
- Palestine transitions are now Saturdays at 02:00. This means 2022 falls
back 10-29 at 02:00, not 10-28 at 0
This bug was fixed in the package tzdata - 2022e-0ubuntu0.20.04.0
---
tzdata (2022e-0ubuntu0.20.04.0) focal; urgency=medium
* New upstream releases (LP: #1992692):
- Palestine transitions are now Saturdays at 02:00. This means 2022 falls
back 10-29 at 02:00, not 10-28 at 0
This bug was fixed in the package tzdata - 2022e-0ubuntu0.18.04.0
---
tzdata (2022e-0ubuntu0.18.04.0) bionic; urgency=medium
* New upstream releases (LP: #1992692):
- Palestine transitions are now Saturdays at 02:00. This means 2022 falls
back 10-29 at 02:00, not 10-28 at
The verification of the Stable Release Update for tzdata has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
This bug was fixed in the package tzdata - 2022e-0ubuntu0.22.04.0
---
tzdata (2022e-0ubuntu0.22.04.0) jammy; urgency=medium
* New upstream releases (LP: #1992692):
- Palestine transitions are now Saturdays at 02:00. This means 2022 falls
back 10-29 at 02:00, not 10-28 at 0
I think it's a bug where update-manager installs those additional
packages which stems from its implementation of phased updates, but it's
also not a priority to work on because this only happens when an SRU
introduces a new dependency which does not happen all that often.
** Package changed: apt
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Fix Committed => Confirmed
--
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/1971712
Title:
Add support for Intel DG2
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-oem-6.0 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs
** Tags removed: foundations-triage-discuss
--
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/1993869
Title:
openssh-server cannot listen or bind to anything other than :::2
Following https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343896#131
and mark this bug as Won't Fix.
** Changed in: openssh (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openss
The above analysis is true for SSH, but, I realise it's different for
the PTY passed in by lxc exec.
So my analysis is true maybe, but I am going to move this SSH fix over
to Bug #1667016 so this bug can stay open for the general PTY/buffering
issue.
There is a gap in my explanation of: It's not
40 matches
Mail list logo