This doesn't appear to be a bug against the GTK package at all, but
rather an issue with OpenJava. As well, it does not appear to be valid
against OpenJava either. This is based on the following error lines:
Caused by: net.sourceforge.jnlp.LaunchException: Fatal: Application Error:
Cannot
** Summary changed:
- OpenJava
+ OpenJava fails to initialize java application
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1385639
Title:
OpenJava fails to
I've marked this as Invalid against GTK because it's not really a GTK
issue based on the error logs.
Having said this, there are two Open Java versions in precise, and no
details on which, so I have marked this as affecting the Open Java
packages that are actually in precise.
I do not know
This doesn't appear to be a bug. As it stands that day listed in the
description seems to be affected by a Daylight Savings Time issue, where
the time may physically not exist in the system's timezone.
When the timezone present is set to Etc/Utc this issue does not occur.
When in a timezone
Nominated for Trusty. Since this is not affecting Utopic or Vivid, I've
marked the master bug Fix Released as it's already fixed.
** Tags added: trusty
** Changed in: util-linux (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Thanks to Brian Murray for the ping on IRC (in #ubuntu-bugs). This is
not an nginx PPA problem.
There have been no NGINX package updates in that repository since
February 10, 2015. The NGINX PPA also has ***zero dependencies,
recommends, or suggests*** on php5-fpm or any other PHP or Apache
Vivid uses systemd by default now, instead of upstart. Is this on a
non-standard system configuration?
** Changed in: upstart (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart
Can anyone confirm whether this happens with the `php5` metapackage
actually in the 'installed' state prior to the update, or whether this
happened with only `php5-fpm` installed?
We also need more steps to reproduce this before we can more thoroughly
start examining and testing.
--
You
NOTE: I do not have the `php5` metapackage installed on this server - I
explicitly installed php5-fpm WITHOUT the `php5` metapackage. I only
have the `php5-fpm` package (and related dependencies) installed. Is it
at all possible that the `php5` metapackage ignored the dependencies
list and
I've also done some testing in a system with nginx and php5-fpm
installed - nginx from the (stable) PPA, and php5-fpm from the
repositories, on a Trusty system. This is in a production environment,
on a VPS from RamNode, and the php5-fpm and nginx haven't been updated
in a while (at least three
Note that because of the Bashisms whatever address was negotiated is not
assigned. This applies at least to IPv6, and if the bashisms interfere
in IPv4 then it also interferes there.
This means the essential function of the application does not operate,
and the bug should potentially be a higher
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3566
--
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/1505328
Title:
Cups SSL is vulernable to POODLE
Public bug reported:
Hello.
I've installed today from the Ubuntu Server Daily ISO. During the
installer process, we get the system identifying network interfaces with
the traditional unpredictable naming algorithms of eth##. After
installation, the system uses systemd to identify network
** No longer affects: ubiquity (Ubuntu)
** Also affects: netcfg (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netcfg (Ubuntu)
Importance: Undecided = High
** Description changed:
Hello.
I've installed today from the Ubuntu Server Daily ISO. During the
Public bug reported:
While running nginx install/upgrade tests, I was trying to get the last
10 lines of the /var/log/apt/history.log file. Naturally, I was trying
to use 'tail' for this:
tail -n 10 /var/log/apt/history.log
Instead of only getting the last 10 lines of the file, I get the
Turns out some shells are evil, and it was a failure in the system
telling me the correct number of lines (this isn't an Ubuntu SSH client
into the server)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
Public bug reported:
Hello.
Within the past week or so, a new bug has cropped up on Network Manager
on 16.04.
When Network Manager on 16.04 is configured to use dnsmasq and not
systemd-resolved, one is expecting VPN DNS servers to be properly set
and dnsmasq to properly route DNS requests to
Sergio,
No, however I would be happy to test later today. The primary reason for my
having a backup local resolving bind9 was just for cases like this, but I'll
test the DBUS method in a few hours and get back to you
--
You received this bug notification because you are a member of Ubuntu
Sergio,
Also, I'm not 100% certain the other bug is not a dupe of this one,
because Yakkety. Their workarounds of restarting dnsmasq, etc. still
didn't work on a 16.04 system (even restarting Network Manager didn't
help - dnsmasq was still dead for *everything*), and now I'm getting
issues where
Interesting, I can't reproduce with standard WPA2 wifi connections.
I wonder if it's specific to the combination of WPA2 Enterprise (with
custom DNS settings in the system) and then that being overridden by the
VPN and that causes some breakages.
I'll test in a few hours when I'm on such a
Given the current state of Zesty and the proximity to a release day I
believe we need patience here heh.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
Public bug reported:
This remains an issue. Supposedly fixed, it's still an issue in 16.04.
When an OpenVPN connection enables, or dies off, dnsmasq ceases to
respond. The upstream DNS servers set are two bind9 instances that both
reply to direct queries, so the core issue is that `dnsmasq` is
Public bug reported:
Installation of this package as part of the Ubuntu Desktop task fails if
being executed from the mini.iso after installation. This is due to teh
Network Manager service not running when it tries to install itself.
This seems like it might be related to
Note that if you manually start the network manager service and then do
`apt-get install -f` or `sudo dpkg-reconfigure network-manager-config-
connectivity-ubuntu`, it appears to work. So something in the apt
ordering is not starting network manager once it's been installed, so a
`sudo apt-get
Sebastien:
Yeah, it complains because when it tries to execute its postinstall
tasks, the Network Manager service isn't yet started.
My suggestion would be to test if the service is actually in a 'running'
state or not before trying to install, and if not, attempt to start the
service. That's
Nginx properly builds with pcre2
** Changed in: nginx (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1792544
Title:
demotion of pcre3
** Description changed:
demotion of pcre3 in favor of pcre2. These packages need analysis what
needs to be done for the demotion of pcre3:
Packages which are ready to build with pcre2 should be marked as
'Triaged', packages which are not ready should be marked as
'Incomplete'.
NGINX has technically said this is won't fix:
>From a response to my inquiry: http://mailman.nginx.org/pipermail/nginx-
devel/2018-September/011448.html
--
Hello!
On Tue, Sep 18, 2018 at 08:12:20AM -0400, Thomas Ward wrote:
> Downstream in Ubuntu, it has been proposed to demote
Nice find, I looked in trac but must have missed that...
Sent from my Sprint Samsung Galaxy S9+.
Original message From: Anders Kaseorg Date:
9/18/18 06:22 (GMT-05:00) To: tew...@thomas-ward.net Subject: [Bug 1792544]
Re: demotion of pcre3 in favor of pcre2
Likewise, nginx
Robie:
Confirmed with a Bionic host as well using the same LXD snap and
environment, and the same reproduction steps.
(Marking as "Confirmed")
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Default nginx configurations **in Ubuntu** do not enable SSL by default.
Have you passed an SSL enabled config to your docker container first?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
This sounds more like an OpenSSL issue than an NGINX one. Until such
investigations are complete to confirm this and rule out NGINX as the
problem, I am marking this as 'Incomplete' in NGINX in Ubuntu.
** Changed in: nginx (Ubuntu)
Status: New => Incomplete
--
You received this bug
Hello.
It is still unclear whether this is still an issue in apt-xapian-index
or the underlying python apt bindings. I am marking this as Incomplete
for apt-xapian-index as this is still marked as affecting it and has
been since 2015, and the Trusty that was affected is End of Life.
Please
Hello, and thank you for opening this report.
Upon further review, this bug report as-is is not yet ready to be
considered for Sponsoring in Ubuntu, as it does not yet provide
justification for the change nor does it provide requisite information
to determine whether this change is even sensible
** Changed in: nginx (Ubuntu)
Status: Incomplete => Opinion
** Changed in: nginx (Ubuntu Bionic)
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
** Changed in: nginx (Ubuntu Bionic)
Status: New => Incomplete
--
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/1833476
Title:
libssl1.1 version
** Changed in: nginx (Ubuntu Bionic)
Status: Incomplete => Invalid
** Changed in: nginx (Ubuntu)
Status: Incomplete => Invalid
** Changed in: openssl (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: openssl (Ubuntu)
Status: New => Invalid
--
You received
** Also affects: openssl (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: nginx (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: nginx (Ubuntu Bionic)
Status: New => Incomplete
--
You received this bug notification because you are a
** Changed in: nginx (Ubuntu)
Status: New => Incomplete
** Also affects: openssl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
Public bug reported:
When using `sudo --login --user USERNAME` with Ubuntu Focal currently,
it will correctly operate but it will also throw the following error
before continuing with the logon process:
sudo: setrlimit(RLIMIT_CORE): Operation not permitted
A full run of this was tested in a
** Description changed:
When using `sudo --login --user USERNAME` with Ubuntu Focal currently,
it will correctly operate but it will also throw the following error
- before continuing with the logon process:
+ before continuing with the logon process (which completes successfully
+ except for
Marking as Opinion/Wishlist because this isn't really a bug.
** Changed in: apport (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: apport (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: perl (Ubuntu)
Importance: High => Undecided
** Changed in: perl (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
** Changed in: perl (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1897561
Title:
libperl.so.5.30.0 causes nginx to segfault
Public bug reported:
Per the SRU done at https://launchpad.net/bugs/1889218 to update Focal's
Python via SRU to 3.8.5, there is a leftover discrepancy on
python3-defaults (and the corresponding `python3` package itself, NOT
the `python3.8` binaries pulled in by it) as to which version is in
** Changed in: apparmor
Status: In Progress => Fix Released
--
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/1932331
Title:
ubuntu_qrt_apparmor: i18n test fails on
Seth Arnold has affirmed the patch is going to fix things, so it's been
reviewed by Seth.
--
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/1932331
Title:
Thanks for the confirm, Steve. However, these may be 'upstream' but
aren't yet in Ubuntu, so. The two issues on my radar are the one I
discovered needs fixed for something to properly WORK for torbrowser-
launcher, and the other is this one Seth poked at me to include on any
SRU for HIrsute.
Public bug reported:
In Focal, abstractions/X has the following section in it:
# the unix socket to use to connect to the display
/tmp/.X11-unix/* rw,
unix (connect, receive, send)
type=stream
peer=(addr="@/tmp/.X11-unix/X[0-9]*"),
unix (connect, receive, send)
So, fixed upstream, but not present in Hirsute or Impish... guess its
patching time.
--
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/1934005
Title:
abstractions/X:
I did some testing with the adjusted X abstractions, and porting the
torbrowser-launcher apparmor rules back as part of testing. With the X
abstractions added, and the adjusted X abstractions working, all looks
good there.
The other component of the SRU is a tests fix, that will only show in
the
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
--
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/1934005
Title:
abstraction
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
--
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/1932331
Title:
ubuntu_qrt_appar
Has the fidelity of the patch attached here been vetted by anyone?
(Seth Arnold asked me to take a look @ this while I'm pushing hard for
1934005 to fix some major chaos so this gets in with that update / SRU)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Also affects: apparmor (Ubuntu Impish)
Importance: High
Assignee: Thomas Ward (teward)
Status: New
** Also affects: apparmor (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu Hirsute)
Importance: Undecided => High
** Chan
SRU template applied because this'll need SRU'd as well, after this
lands in Impish.
** Description changed:
+ [Impact]
+ Any application that requires access to X11 sockets for the Display may want
to include abstractions/X in the AppArmor rules, which usually will include
rules that we would
** Also affects: apparmor (Ubuntu Hirsute)
Importance: Undecided
Status: New
--
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/1932331
Title:
ubuntu_qrt_apparmor:
** Changed in: apparmor (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: apparmor (Ubuntu Hirsute)
Assignee: (unassigned) => Thomas Ward (teward)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ap
I have no insights into whether the linked GitHub issue fixes anything.
That's a Perl package problem, and not an NGINX one. We could
potentially stop requiring the Perl module but a segfault in libperl is
a Perl issue, not an nginx one. However, we don't have a *clear*
reproduction solution
@Kraut
That would work for *testing* but Perl is interlaced in **a huge
portion** of the Ubuntu OS. Which means for any SRU, **all**
autopkgtests need to pass, which is a lot more painful if anything
fails.
There's more than just NGINX that needs tested with *any* Perl SRU.
Which is why I say
@Kraut Further, the linked patch at the end of the upstream bug is
**not** yet part of the Perl codebase, so it's not been accepted
upstream, which is another consideration point and probably why this
hasn't had much movement on it yet (and why it's marked 'Incomplete' for
Perl)
--
You received
** Changed in: perl (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1897561
Title:
libperl.so.5.30.0 causes nginx to segfault
The version of sudo in the repos already prior to this
(1.9.4p2-2ubuntu3) works as expected, though, with proper permissions
being set:
root@hirsute-test:~# apt-cache policy sudo
sudo:
Installed: 1.9.4p2-2ubuntu3
Candidate: 1.9.4p2-2ubuntu3
Version table:
1.9.5p2-2ubuntu1 400
Confirmed the regression that iLogin sees.
>From within a hirsute daily LXD container with full apt update and apt
dist-upgrade done to it, with `sudo apt install -t hirsute-proposed
sudo` done to get the sudo AND updated libc it requires):
root@hirsute-test:~# ls -al $(which sudo)
-rwsr-xr-x 1
Looks like the permissions issue is caused by
https://bugs.launchpad.net/ubuntu/+source/fakeroot/+bug/1915250 and
everything is now frozen until that is fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1943840
Title:
[FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
Status in ubuntu-meta package in
I've got some extra cycles later today, so I'll happily help the
Security team out and get this uploaded later today (Eastern US time for
clarity sake when I say "later today")
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
** Changed in: op
[ubuntu/jammy-proposed] openssl 3.0.2-0ubuntu1 (Accepted)
Uploaded to proposed, it has to go through the usual process of passing
autopkgtests and such. It shouldn't need any additional package
rebuilds because of no ABI changes but expect autopkgtests to run hot a
while
** Changed in: openssl
If Qt6 is dead upstream, then it's probably a candidate for removal as
soon as Qt5 is retired.
Note that because Debian has refused to even add Qt6 because QtChooser
is dead upstream by design, and I'm gathering as such should not be used
with Qt6, I opened a Debian bug suggesting that they mark
I've sponsored/uploaded both the Jammy and Kinetic debdiffs. Kinetic is
accepted, jammy-proposed has to go through SRU.
Removing Sponsors as there is nothing more to sponsor here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: elfutils (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 elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1987356
Title:
[BPO] elfutils/0.187-1 from
Marking this as Won't Fix because of identified issues and Unit
indicating that this should be withdrawn.
** Changed in: dh-python (Ubuntu Focal)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
> I intend to update Ubuntu's debuginfod instance to use this new
package in the near future.
By "update" do you mean SRU or via Backports? If you are not going to
be doing this via Backports, then I would suggest that you hunt an SRU
on the sole basis that mixing and matching SRU/Backports
OpenSSL is one of those tricky things out there I would like to get a
Security insight for before we do any kind of backporting of it.
There's other things this could impact, backports or not.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I've discussed this with mapreri who is another person on the
backporters team.
Given the API/ABI changes that happen during OpenSSL microreleases that
break packages integrations AND that this will add a security delta
(-backports doesn't receive Security Team support so if they change and
patch
Mark, are you asking this to be backported in -backports or in -updates
and -security? This is one of the packages that if we do this in
-backports any security patches applied by the Security team for OpenSSL
in -security and -updates would be ignored with the higher version of
this in
Regarding NGINX, PCRE2 support is now available in NGINX nginx 1.21.5+
so there was support as of December 24th 2021 and later.
Which means that NGINX 1.22+ supports PCRE2. This could be marked as
Triaged *for 23.04 and later* once NGINX is merged in from Debian
upstream, if someone can put a
After discussion with the Security Team, we do not believe this is a
Security bug and that there currently is no need to keep it private as
there is other public discourse via other related bugs on other trackers
and here in Launchpad with other bugs (marked as dupes of this or such).
**
78 matches
Mail list logo
