After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 588186 - Accounts window and voicemails
Accounts window and voicemails
Status: RESOLVED WONTFIX
Product: ekiga
Classification: Applications
Component: OPAL
GIT master
Other All
: Normal major
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2009-07-09 18:57 UTC by Damien Sandras
Modified: 2020-06-06 16:29 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Damien Sandras 2009-07-09 18:57:21 UTC
It is now impossible to know the number of voicemails on each of the accounts.
Comment 1 Snark 2009-07-09 20:41:49 UTC
The status of each account is supposed to reflect the number of voicemails ; see lib/engine/components/opal/opal-account.cpp -- method get_status.

That means the message waiting number doesn't get set correctly in the engine.

Definitely not a GUI issue : it's an issue within ekiga's opal code.
Comment 2 Damien Sandras 2009-07-10 05:58:35 UTC
And where should it be displayed ?
Comment 3 Snark 2009-07-10 15:58:18 UTC
In the status, which is the second column...
Comment 4 Damien Sandras 2009-07-11 16:05:44 UTC
Now that the voicemail code is specific to opal accounts and that there are no more signals for it, how can we allow the systray icon to display an enveloppe when there are new messages waiting ?
Comment 5 Snark 2009-07-12 06:44:57 UTC
The same way we display an enveloppe when there are text messages waiting, perhaps?
Comment 6 Damien Sandras 2009-07-12 09:09:01 UTC
Isn't it a bit of overkill?
Comment 7 Snark 2009-07-12 15:08:46 UTC
Solution 1 (push the event) : add the code to push a notification in the Opal::Account class ; this code will be shared by each Opal::Account instance.

Solution 2 (use a signal) : the signal goes in the Ekiga::Account class, so takes room in each and every instance of the class (even LM::Account instances, which don't need it) ; and of course we'll still need code to react to the signal and push a notification.

The signal solution is overkill : let's push the notification.
Comment 8 Damien Sandras 2009-07-12 16:41:42 UTC
Please also note you really need to do something about the UI, it still looks weird.
Comment 9 Tobias Mueller 2010-04-07 14:50:19 UTC
Reopening as I can't see any open non-developer question.
Comment 10 Eugen Dedu 2012-10-21 10:07:28 UTC
Damien, Julien, closing this bug or let it still open?
Comment 11 Eugen Dedu 2012-10-21 10:23:35 UTC
Changing importance to major.
Comment 12 Eugen Dedu 2012-12-13 20:39:50 UTC
Damien, Julien, closing this bug or let it still open?
Comment 13 André Klapper 2020-06-06 16:29:43 UTC
Ekiga is not under active development anymore:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/273

Ekiga saw its last release 7 years ago. The last code commits were 4 years ago.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (and transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active Ekiga development again in the future.