The reason I want to remove the code is that it wasn't meant for
Desktop. It works on Desktop when using wayland but this is was
definitely not the intent back then. As I say in
https://code.launchpad.net/~adrien/ubuntu/+source/openssl/+git/openssl/+merge/466581
, I don't think the postinst can be
Well, we're not in the world of needrestart just yet, it's only seeded in
Server.
On Thu, 30 May 2024, 04:20 Seth Arnold, <244...@bugs.launchpad.net>
wrote:
> Adrien, thanks so much for digging into this again.
>
> This is so very complicated, why does openssl need special handling in
> the
Adrien, thanks so much for digging into this again.
This is so very complicated, why does openssl need special handling in
the world of needrestart? My inclination is to remove all this
complexity and address any shortcomings of needrestart in the
needrestart package. Am I off base?
Thanks
--
I did some archeology because I'm trying to get rid of the Ubuntu delta
compared to Debian.
I think the code change in 1.0.0e-2ubuntu3 is problematic. No blame: the
shell script was already hairy and difficult to understand and in order
to spot that, I had to identify a chunk of dead code, remove
A web server is supposed to retrieve data from database, run application
logic, write back to database if needed, write an HTML document or JSON
object to output, and wait for the next request. Ideally, it's stateless
between requests.
A desktop application, on the other hand, is more likely to
@mdeslaur: Thank you for your reply! Does that mean that it is supposed
to happen on an Ubuntu server system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/244250
Title:
Spurious reboot
@khaled-blah: yes, on a server, it should do the usual and add a reboot
required blurb to the motd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/244250
Title:
Spurious reboot notifications caused
@mdeslaur: Again, thank you for your reply! Pardon my ignorance but I've
never quite understood why that is - why is an update of libssl
different from an update of other libs where you can simply restart the
depending applications/daemons? And why is it different on a desktop?
Maybe these
On Ubuntu 14.04 this bug still persists. Is there any reason why libssl
would require different treatment than other libraries? I.e. why
wouldn't it suffice to restart services depending on libssl or
libcrypto?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
@khaled-blah: please file a new bug, you are not supposed to see reboot
notifications when openssl gets upgraded on a desktop system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/244250
Title:
The problem still exists. Xubuntu 11.10 on a desktop, the only
application with an open window that is obviously using SSL is Firefox,
the only update was for libssl and openssl, and Update Manager still
tells me a reboot is required.
--
You received this bug notification because you are a
Agreed. It really doesn't make sense to issue the reboot-required
notification when we aren't doing the whole restart-services dance.
I'll look at the branch you proposed for this.
** Changed in: openssl (Ubuntu)
Status: Fix Released = In Progress
--
You received this bug notification
This bug was fixed in the package openssl - 1.0.0e-2ubuntu3
---
openssl (1.0.0e-2ubuntu3) oneiric; urgency=low
* Only issue a restart required notification on important upgrades, and
not other actions such as reconfiguration or initial installation.
(LP: #244250)
-- Anders
Actually, we do want a reboot notification when we issue security
updates. When we issue security updates, we don't enter the major
upgrade section, as we don't want the update to automatically restart
services, but we do want the sysadmin to perform a planned
reboot/service restart as the running
On Tue, Oct 4, 2011 at 3:37 PM, Marc Deslauriers
marc.deslauri...@canonical.com wrote:
Actually, we do want a reboot notification when we issue security
updates. When we issue security updates, we don't enter the major
upgrade section, as we don't want the update to automatically restart
We've already removed reboot notifications from openssl on desktops, I'm
just talking about servers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/244250
Title:
Spurious reboot notifications caused
How do you distinguish a server from a desktop, and what about servers that
don't run ssl-using daemons?
Thomas
On Oct 4, 2011 2:05 PM, Marc Deslauriers marc.deslauri...@canonical.com
wrote:
We've already removed reboot notifications from openssl on desktops, I'm
just talking about servers.
Right now, the best way we have of determining if we're a server or a
desktop is to check if X is running. It's not ideal, and suggestions are
welcome.
We need a way for sysadmins to get notifications that some of the major
automatic updates they are installing, such as openssl and the kernel,
On Wed, Oct 5, 2011 at 12:54 AM, Marc Deslauriers
marc.deslauri...@canonical.com wrote:
Right now, the best way we have of determining if we're a server or a
desktop is to check if X is running. It's not ideal, and suggestions are
welcome.
I think my question is suggesting that there really
This bug was fixed in the package openssl - 1.0.0e-2ubuntu1
---
openssl (1.0.0e-2ubuntu1) oneiric; urgency=low
* Resynchronise with Debian, fixes CVE-2011-1945, CVE-2011-3207 and
CVE-2011-3210 (LP: #850608). Remaining changes:
- debian/libssl1.0.0.postinst:
+ Display
This bug is not fixed. It’s still the case that libssl1.0.0 generates a
spurious reboot notification during reconfiguration, on initial
installation, and on non-critical upgrades, as originally reported. The
only change in 1.0.0e-2ubuntu1 is that this no longer happens at all on
systems running
** Branch linked: lp:~sbeattie/ubuntu/oneiric/openssl/lp850608
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/244250
Title:
Spurious reboot notifications caused by libssl upgrades.
To manage
** Changed in: openssl (Ubuntu)
Assignee: Luke Yelavich (themuso) = Marc Deslauriers (mdeslaur)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/244250
Title:
Spurious reboot notifications caused
** Tags added: glucid lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/244250
Title:
Spurious reboot notifications caused by libssl upgrades.
--
ubuntu-bugs mailing list
Still seen on my 8.04 development workstation and my 10.10 laptop.
Based on Colin Watson's comment, I guess it should work like this:
1. Automatically restart services that depend on SSL, just as we do
when the services' packages are upgraded.
2. Give a logout recommended notice (not a reboot
I've changed the description to more precisely characterize the
actionable problem here, namely a buggy postinst script that sends
spurious reboot notifications.
** Summary changed:
- reboot every single update in the past month on ubuntu hardy nearly.
massively decreasing my uptime.
+ Spurious
26 matches
Mail list logo
