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 571268 - group wise - A blank error window when adding proxy rights
group wise - A blank error window when adding proxy rights
Status: RESOLVED DUPLICATE of bug 561188
Product: evolution
Classification: Applications
Component: Mailer
2.26.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[groupwise]
Depends on:
Blocks:
 
 
Reported: 2009-02-11 05:15 UTC by Akhil Laddha
Modified: 2013-09-13 00:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
Screenshot (63.53 KB, image/jpeg)
2009-02-11 05:16 UTC, Akhil Laddha
Details

Description Akhil Laddha 2009-02-11 05:15:12 UTC
When i try to give proxy rights to a user, evolution pops up a blank error
window and i cann't add user for proxy rights. We should pop up a right error
message.
Comment 1 Akhil Laddha 2009-02-11 05:16:06 UTC
Created attachment 128445 [details]
Screenshot
Comment 2 Akhil Laddha 2009-02-11 05:26:00 UTC
Comment from downstream bug 
https://bugzilla.novell.com/show_bug.cgi?id=464017

The issue in here is none of the GW error messages would be displayed since the
processing of error files do not happen during the build. So messages marked
for translation are still at fault and none of the error messages could be
extracted from the error files of the plugins.

Solutions:
1) Change the behaviour of groupwise-features plugin like other plugins which
process the error files.

2) Add the processing code separately for groupwise-features plugin and retain
the existing behaviou
Comment 3 Akhil Laddha 2009-05-19 08:18:48 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 561188 ***