pidgin doesn't ask for a restart after upgrade

Bug #209707 reported by Nicolas Valcarcel
4
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: pidgin

I have just upgrade my system running pidgin at the same time, and after the upgrade, which include a pidgin upgrade, update-notifications doesn't ask me to restart pidgin.

Revision history for this message
Emil Sit (emilsit) wrote :

Did pidgin stop working correctly after the upgrade?

Revision history for this message
Nicolas Valcarcel (nvalcarcel) wrote : Re: [Bug 209707] Re: pidgin doesn't ask for a restart after upgrade
  • unnamed Edit (189 bytes, application/pgp-signature; name=signature.asc)

What do you mean by "stop working correctly" it doesn't stop, it works
with the old version, but starts failing at some points.

On Tue, 2008-04-01 at 03:59 +0000, Emil Sit wrote:
> Did pidgin stop working correctly after the upgrade?
>
--
aka nxvl
Peruvian LoCo Team
key fingerprint = 8104 21CE A580 7EB7 5184 8DFF 6A3A D5DA 24DC 6AF5
gpg --keyserver keyserver.ubuntu.com --recv-keys 24DC6AF5

Revision history for this message
Emil Sit (emilsit) wrote :

I too observed that no notification occurred, but I didn't stay with the old version long enough to see if it crashed (e.g., b/c some plugin or dynamic library had changed out from under the running binary). How did it start failing?

However, it seems like it would be easy to set the postinst script to create a notification, just like the firefox postinst script does.

Changed in pidgin:
status: New → Confirmed
Revision history for this message
Nicolas Valcarcel (nvalcarcel) wrote :
  • unnamed Edit (189 bytes, application/pgp-signature; name=signature.asc)

Yes, it doesn't really crash but it start working slow, and it fails at
some points, however, that is not very important at the moment, because
it can be a minor update and it doesn't fail hard enough, but, when we
have a critical update or a big one, then we will have critical and/or
big problems.

On Tue, 2008-04-01 at 16:25 +0000, Emil Sit wrote:
> I too observed that no notification occurred, but I didn't stay with the
> old version long enough to see if it crashed (e.g., b/c some plugin or
> dynamic library had changed out from under the running binary). How did
> it start failing?
>
> However, it seems like it would be easy to set the postinst script to
> create a notification, just like the firefox postinst script does.
>
> ** Changed in: pidgin (Ubuntu)
> Status: New => Confirmed
>
--
aka nxvl
Peruvian LoCo Team
key fingerprint = 8104 21CE A580 7EB7 5184 8DFF 6A3A D5DA 24DC 6AF5
gpg --keyserver keyserver.ubuntu.com --recv-keys 24DC6AF5

Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, there is no point to display a notification saying you should restart the software for every software running, that's not specific to pidgin either

Changed in pidgin (Ubuntu):
importance: Undecided → Low
status: Confirmed → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

note that there is no reason that pidgin should stop working after upgrade, the running version should not change, if you have specific issues open bugs about those

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.