FYI, my installation was a complete install to a blank disk... But I am
not Kent.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065405
Title:
cups-proxyd[2318]: segfault at 18 ip 5975fb88bd75
Hi Kent,
you should be able to still run a previous version of the kernel with the boot
menu, like what I do, and you can see if your problems are listed at:
The original issue seems to be fixed in 23.10:
```
/tmp/test$ dash -c "name=прстуфхцчшщ;echo \$name > \$name"
/tmp/test$ ls
прстуфхцчшщ
/tmp/test$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10
```
--
You received this bug notification because
Unfortunately /var/crash is empty, maybe due to the failure to start.
sudo cat /var/lib/whoopsie/whoopsie-id
ad33826e2f810e105835159dfb99f6a96d895ef0f2572f8db1cf7693a913ff9e35a336244664aaa184f4ed2f0f925f99e481379028b0c7eba2bd9df9363ca035
So there seem to be stuff at:
neric" to boot does bring a working system.
I still get with the older and working kernel:
etienne@etienne-MS-7D77:~$ sudo dmesg | grep -A1 array-
[3.078005] UBSAN: array-index-out-of-bounds in
/build/linux-hwe-6.5-5nKPnc/linux-hwe-6.5-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2717:34
[
For information, ubuntu-24.04 has updated Linux kernel from 6.5.0-28 to
6.8.0-31
The problem reported is only with newer 6.8.0-31, and also failure to
reach a working system is only with new kernel.
The previous Linux kernel is still available in the Grub menu, and choosing
"6.5.0-28-generic"
Public bug reported:
Ubuntu 24-04 no more start in graphic mode after latest upgrade, only
control-alt-f2 to get console.
The driver for Radeon R9 290x/390x generate:
[ 2.812012] UBSAN: array-index-out-of-bounds in
/build/linux-yrLejD/linux-6.8.0/drivers/gpu/drm/radeon/radeon_atombios.c:2718:34
Public bug reported:
dmesg shows, ubuntu-24.04 just updated and no more booting to graphic, more
details in the attached tgz:
It might be apparmor fault, or the other problems before in dmesg attached...
[5.391769] show_signal: 175 callbacks suppressed
[5.391770] traps: gdm3[2173] trap
Thanks Alberto :
Re-enabling the snapd.apparmor service has fixed my issue.
Therefore, I have migrated my issue to a contribution to
https://bugs.launchpad.net/snapd/+bug/1806135
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871148
Title:
services start before apparmor profiles are loaded
To manage notifications about this bug go to:
$ systemctl status snapd.apparmor
○ snapd.apparmor.service - Load AppArmor profiles managed internally by snapd
Loaded: loaded (/lib/systemd/system/snapd.apparmor.service; disabled;
vendor preset: enabled)
Active: inactive (dead)
I do NOT remember having manually disabled this service.
Inside the attached journal for the 'apparmor.service' unit, I do NOT
understand at all which "DENIED" messages are normal and which are
abnormal.
For independent reasons, I would like to keep my machine running for several
days (or weeks).
But after I reboot, and before running the
Yes, on the slower machine (where I am seeing this issue), I will NOT be
able to start firefox until I have run that apparmor_parser command.
Not even if I try starting firefox well after the login.
$ ls -l /etc/apparmor.d/disable
total 0
lrwxrwxrwx. 1 root root 31 août 27 2019 usr.bin.firefox
** Attachment added: "systemd-analyze-plot-sirius-2022-05-18.svg"
https://bugs.launchpad.net/apparmor/+bug/1871148/+attachment/5590993/+files/systemd-analyze-plot-sirius-2022-05-18.svg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The issue that I am seeing is exactly the one explained in the bug
description.
More precisely, on my slower machine, each time I start firefox (which is now a
snap) from a terminal, following error message is displayed :
cannot change profile for the next exec call: No such file or directory
With the Live CD of Ubuntu Desktop 22.04 (Jammy Jellyfish), this issue
did NOT occur for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945011
Title:
kernel BUG at fs/inode.c:1676! during Live
Raised upstream at https://savannah.gnu.org/bugs/index.php?62456
** Bug watch added: GNU Savannah Bug Tracker #62456
http://savannah.gnu.org/bugs/?62456
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With snapd 2.55.3+22.04ubuntu1 and apparmor 3.0.4-2ubuntu2 from Ubuntu
22.04 (Jammy Jellyfish) :
- On a machine with a powerful i7-7700 HQ processor, the issue did NOT
appear yet.
- On a machine with the slower AMD FX-8370E processor, the issue occurs
systematically after each reboot.
$
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871148
Title:
services start before apparmor profiles are loaded
To manage notifications about this bug go to:
I fully confirm that this Evince issue is linked to Apparmor :
$ aa-exec -p unconfined evince example.pdf
systematically opens the PDF file in the same large windows and with the same
side pane as the last time.
I have added following line at the end of /etc/apparmor.d/local/usr.bin.evince :
Same issue with evince 42.1-3 and apparmor 3.0.4-2ubuntu2 on cinnamon
5.2.7-4 from Ubuntu 22.04 (Jammy Jellyfish)
The apparmor workaround fixes it for me. Thanks Karsten.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915910
Title:
evince does not print (apparmor, pxgsettings)
To manage notifications about this bug go to:
This bug is still present in grub2 version 2.06-2ubuntu7 from 'Ubuntu
22.04 Jammy Jellyfish'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479516
Title:
grub-install documentation is truncated or
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479516
Title:
grub-install documentation is truncated or too succint
To manage notifications about this bug go to:
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579457
Title:
ubiquity must NOT format a valid SWAP partition on manual partitioning
To manage notifications about this bug go
1) I do NOT know how to retrieve the ntfsresize options.
2) In order to retrieve file system metadata in the attached 'ntfsinfo.log'
file, I used following command :
$ for dev in $(sudo blkid -o device -t TYPE=ntfs); do sudo ntfsinfo -fm
"$dev"; echo; done
** Attachment added: "File system
This bug is probably a duplicate of bug #1945011
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946828
Title:
ntfsresize hang and call traces in syslog
To manage notifications about this bug go
This issue is exactly the same with the final Live CD of Ubuntu Desktop
21.10 (Impish Indri) with full graphics.
The process which causes warnings from 'fs/block_dev.c' is ntfsresize.
So, this issue is probably the same as bugs #121943 and #1946828
--
You received this bug notification because
The faulty package is NOT kerneloops, but linux.
So, I created a new bug #1945011 for the linux package, which automatic uploads
additional useful attachments.
And I close this bug for the kerneloops package as invalid.
** Changed in: kerneloops (Ubuntu)
Status: New => Invalid
--
You
Public bug reported:
On this computer with ext4, FAT and NTFS partitions :
I successfully booted from the Live CD of Ubuntu Desktop 21.10 (Impish
Indri) beta with full graphics.
I started the ubiquity graphical interface and successfully completed
the first screens.
But on the 'Updates and
Public bug reported:
On this computer with ext4, FAT and NTFS partitions :
I successfully booted from the Live CD of Ubuntu Desktop 21.10 (Impish
Indri) beta with full graphics.
I started the ubiquity graphical interface and successfully completed
the first screens.
But on the 'Updates and
Public bug reported:
I am upgrading because I cannot install Steam ( have spent hours trying)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.36
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
Patch for focal copied from Debian buster's 3.0.4 security fix. Please
review! :)
** Patch added: "Patch for focal"
https://bugs.launchpad.net/ubuntu/+source/shibboleth-sp/+bug/1926250/+attachment/5503831/+files/1-3.0.4+dfsg1-1ubuntu0.2.debdiff
--
You received this bug notification because
*** This bug is a security vulnerability ***
Public security bug reported:
Upstream advisory:
https://shibboleth.net/community/advisories/secadv_20210426.txt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Shibboleth Service Provider Security Advisory [26 April 2021]
An updated version of the
Is there something missing from the proposed patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919419
Title:
Phishing vulnerability: Template generation allows external parameters
to override
Assigned CVE: 2021-28963
https://security-tracker.debian.org/tracker/CVE-2021-28963
For some reason, the "link to CVE" on the right rejects "2021-28963"...
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-28963
--
You received this bug notification because you are a member of
Patch for focal copied from Debian buster's 3.0.4 security fix.
** Description changed:
- Upstream has given advance warning that a security patch would be
- released on 2021-03-17 (USA time). See
- https://shibboleth.net/pipermail/users/2021-March/049488.html
-
- Details to be published at
+
** Bug watch added: Debian Bug tracker #985405
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985405
** Also affects: shibboleth-sp (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985405
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919419
Title:
Template generation allows external parameters to override
This bug is still present in grub2 version 2.04-1ubuntu35.4 from 'Ubuntu
20.10 Groovy Gorilla'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479516
Title:
grub-install documentation is truncated
Inside Ubuntu 20.10 (Groovy Gorilla), I just tested with systemd versions
246.6-1ubuntu1 and 246.6-1ubuntu1.1 :
The issue has disappeared; umask is correct under gnome-terminal.
So, I remove the 'groovy' tag.
** Tags removed: groovy
--
You received this bug notification because you are a
Public bug reported:
An unresolvable problem occurred while calculating the upgrade.
Attempting to upgrade distro from 18.04.5 bionic.
This was likely caused by:
* Unofficial software packages not provided by Ubuntu
Please use the tool 'ppa-purge' from the ppa-purge
package to remove software
** Tags added: groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579457
Title:
ubiquity must NOT format a valid SWAP partition on manual partitioning
To manage notifications about this bug go
This bug is still present in grub2 version 2.04-1ubuntu34 from 'Ubuntu
20.10 Groovy Gorilla Beta'
** Tags added: groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479516
Title:
grub-install
REGRESSION: With systemd 246.6-1ubuntu1 from Ubuntu 20.10 Beta (Groovy
Gorilla), the issue had reappeared
** Tags added: groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
Public bug reported:
I installed python3-bluez on Ubuntu 20.04:
$> sudo apt install python3-bluez
However, using this package in python3 leads to an error:
$> python3
Python 3.8.2 (default, Jul 16 2020, 14:00:26)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for
Public bug reported:
Using the File menu of ocrfeeder :
- Adding a JPG image systematically succeeds,
- Importing a PDF systematically fails (without any error message).
Please fix the handling of PDF by ocrfeeder.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ocrfeeder
Public bug reported:
$ ocrfeeder -h
usage: ocrfeeder [-h] [-d DIR] [-v] [IMAGE [IMAGE ...]]
This syntax is correct.
ocrfeeder man and info pages both display :
Other options
-i IMAGE1 [IMAGE2 ...], --images=IMAGE1 [IMAGE2 ...]
Add the specified images to OCRFeeder
snapd messages inside syslog :
systemd[19415]: Listening on REST API socket for snapd user session agent.
systemd[19415]: snapd.session-agent.socket: Succeeded.
systemd[19415]: Closed REST API socket for snapd user session agent.
snapd[1729]: AppArmor status: apparmor is enabled and all features
** Tags removed: fossa
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849669
Title:
do-release-upgrade (19.04 -> 19.10) aborts when snapd is disabled
To manage notifications
When snapd is not in a good state, do-release-upgrade systematically
fails on upgrade from eoan (19.10) to fossa (20.04).
The only messages displayed on the terminal by do-release-upgrade are :
Restoring original system state
Aborting
Before using snapd, I think that do-release-upgrade must test
** Tags added: eoan fossa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849669
Title:
do-release-upgrade (19.04 -> 19.10) aborts when snapd is disabled
To manage notifications about this bug go
On Ubuntu 20.04, I successfully downgraded Unison (text only) to the
version compiled with OCaml 4.02 from https://www.urs-
mueller.ch/de/computer/download/unison-2.48.4-linux-x86_64-text-
static.tar.gz
Using the unison-jz snap installing Unison 2.51.2 compiled against OCaml 4.02.3
as described
With systemd version 245.2-1ubuntu2 from Ubuntu 20.04 Beta (Focal
Fossa), the issue is still the same.
** Tags added: eoan focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
This bug is still present in grub2 version 2.04-1ubuntu22 from 'Ubuntu
20.04 Focal Fossa Beta'
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479516
Title:
grub-install
** Tags added: eoan focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729736
Title:
10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti
Mobile
To manage notifications about
** Tags added: eoan focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579457
Title:
ubiquity must NOT format a valid SWAP partition on manual partitioning
To manage notifications about this bug
Sven, here are the workaround steps (as root) :
1) Create the folder '/etc/systemd/user/gnome-terminal-server.service.d' (with
usual mode 755).
2) In this newly created folder, create the 'umask.conf' file with following
content :
[Service]
UMask=
--
You received this bug notification
Thanks to @Adam Conrad (adconrad) for the updated packages in eoan-proposed :
My laptop can now successfully boot with Secure boot enabled.
$ uname -a
Linux urbah-15 5.3.0-21-generic #22-Ubuntu SMP Tue Oct 29 22:55:51 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
$ dmesg | grep -i -e secure -e
This bug is still present in grub2 version 2.04-1ubuntu6 from 'Ubuntu
19.10 Eoan Ermine Beta'
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479516
Title:
grub-install
In order that gnome-terminal starts with the correct umask :
Lot of thanks to Olivier JOLY for comment #27 :
His workaround is effective.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
Ubuntu 19.04 (disco) will switch to read-only when a automatically mounted VFAT
filesystem with errors is detected.
You have to umount the filesystem and then run "sudo fsck.vfat /dev/sd"
multiple times, until fsck.vfat do no more ask to correct the new errors
detected in the filesystem.
Currently, the upstream issue has NOT been migrated to GNOME GitLab yet,
but is still being tracked at
https://bugzilla.gnome.org/show_bug.cgi?id=780622
** Bug watch added: bugzilla.gnome.org/ #780622
https://bugzilla.gnome.org/show_bug.cgi?id=780622
--
You received this bug notification
This bug is still present in grub2 version 2.02+dfsg1-12ubuntu2 from
'Ubuntu 19.04 Disco Dingo'
** Tags added: cosmic disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479516
Title:
Public bug reported:
Gnote Help displays :
To set preferences for Gnote, select Preferences from the application menu.
But Gnote application menu does NOT contain a Preferences item, NEITHER
in the gnome top bar menu NOR in the Gnote titlebar menu.
Thank you in advance for permitting users to
source package was renamed shibboleth-sp2 -> shibboleth-sp
** Changed in: shibboleth-sp2 (Ubuntu Cosmic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
source package was renamed shibboleth-sp2 -> shibboleth-sp
** Changed in: shibboleth-sp2 (Ubuntu Bionic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
version in disco is the target one
** Changed in: shibboleth-sp (Ubuntu Cosmic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3
source package was renamed opensaml2 -> opensaml
** Changed in: opensaml2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3
source package was renamed opensaml2 -> opensaml
** Changed in: opensaml2 (Ubuntu Cosmic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth
source package was renamed opensaml2 -> opensaml
** Changed in: opensaml2 (Ubuntu Bionic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth
version in disco is the target one
** Changed in: opensaml (Ubuntu Cosmic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3 for
version in disco is the target one
** Changed in: xml-security-c (Ubuntu Bionic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth
version in disco is the target one
** Changed in: log4shib (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3 for bionic
version in disco is the target one
** Changed in: xml-security-c (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3 for
version in disco is the target one
** Changed in: xmltooling (Ubuntu Bionic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3
version in disco is the target one
** Changed in: log4shib (Ubuntu Cosmic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3 for
version in disco is the target one
** Changed in: xmltooling (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3 for
version in disco is the target one
** Changed in: shibboleth-resolver (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3
version in disco is the target one
** Changed in: xmltooling (Ubuntu Cosmic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3
version in disco is the target one
** Changed in: log4shib (Ubuntu Bionic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3 for
version in disco is the target one
** Changed in: xml-security-c (Ubuntu Cosmic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth
version in disco is the target one
** Changed in: shibboleth-resolver (Ubuntu Bionic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU:
version in disco is the target one
** Changed in: shibboleth-resolver (Ubuntu Cosmic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU:
version in disco is the target one
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3 for bionic
To manage notifications about this bug go to:
nt state of Ubuntu
packages in the Git repositories on salsa under ubuntu/ (changelog,
patches, etc.) so that all of this can be unified. I'd still need
sponsorship to upload though, but that can be sorted later.
Cheers,
Etienne
[1] https://salsa.debian.org/shib-team
--
You received this bug no
Anyway, thank you very much Robie for your help so far! :D I really
appreciate it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3 for bionic
To manage
the
> development release, and landing routine bugfixes in stable releases
> are much easier.
It is indeed a daunting task for a newcomer. I submitted one security
patch for Shibboleth just before and it went well so I figured I'd
embark on a larger endeavour. :) For me, how packages are mainta
Upstream's release notes for this version are unfortunately empty, but
the git log contains:
commit 2962366d07003ac8edc8734417e7a5962c635686 (tag: 3.0.1, upstream/master,
origin/master, master)
Author: Scott Cantor
Date: Thu Feb 21 15:18:04 2019 -0500
Bump version.
config_win32.h
I've looked at the changes (git log) in opensaml2-tools and xml-
security-c-utils to find out whether the programs they provide had
changed, but apparently there are only internal changes, nothing
changing the CLI. The man pages didn't change either.
Neither the release notes for xml-security-c
Regarding #10:
> Usage of the libraries for other purposes is generally not supported.
"not supported" here means not supported by upstream developers -- i.e.
the Shibboleth project -- and isn't meant as a license to break other
packages in bionic.
--
You received this bug notification because
** Also affects: shibboleth-resolver (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
[Impact]
Bionic released with version 2 of the Shibboleth Service Provider (and
its accompanying dependencies) and with OpenSSL 1.1. However, the SPv2
isn't compatible
> I cannot further comment on the impact upon Moonshot-related packages,
but I can ask their Debian maintainer if needed.
So I asked Sam Hartman on the pkg-shibboleth-devel list and he replied:
> So, there was a new release of shibboleth-resolver along with the 3.x SP.
> I'm not sure whether the
Hi Robie,
Thank you for taking the time to review this SRU. I've considered the
use cases of Shibboleth packages and searched for reverse dependencies
and here is what I can say.
All five source packages are maintained by Shibboleth project developers
as components of the Shibboleth Service
** Description changed:
[Impact]
Bionic released with version 2 of the Shibboleth Service Provider (and
its accompanying dependencies) and with OpenSSL 1.1. However, the SPv2
isn't compatible with OpenSSL 1.1, only 1.0 (and earlier), and was
therefore shipped compiled against 1.0.
Public bug reported:
Please sync opensaml 3.0.1-1 (universe) from Debian unstable (main)
Changelog entries since current disco version 3.0.0-2:
opensaml (3.0.1-1) unstable; urgency=medium
* [d1daef5] Revert "Temporarily ignore build test failures"
* [792ec83] New upstream release: 3.0.1
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3 for bionic
To manage notifications about this bug go to:
The backported packages install and upgrade cleanly on bionic, tested
with `piuparts -b /var/cache/pbuilder/base-bionic-amd64.tgz
--distribution=bionic --keep-sources-list --arch=amd64 -D ubuntu
--shell-on-error --single-changes-list
log4shib_2.0.0-2~ubuntu18.04.1_amd64.changes xml-security-
Package shibboleth-sp 3.0.3+dfsg1-1 from disco needs a revert from
debhelper compat level 12 to 11. No other changes are required to build
on bionic.
** Patch added: "shibboleth-sp_1-3.0.3+dfsg1-1~ubuntu18.04.1.debdiff"
Would someone please review and sponsor this SRU?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822069
Title:
SRU: Shibboleth SPv3 for bionic
To manage notifications about this bug go to:
1 - 100 of 1471 matches
Mail list logo
