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 273684 - Unable to change signature script path using edit dialog
Unable to change signature script path using edit dialog
Status: RESOLVED DUPLICATE of bug 273156
Product: evolution
Classification: Applications
Component: general
2.0.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-03-14 17:41 UTC by mlynx
Modified: 2005-06-01 14:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description mlynx 2005-03-14 17:41:23 UTC 
Distribution: Mandrakelinux release 10.1 (Official) for i586
Package: Evolution
Priority: Normal
Version: GNOME2.6.2 2.0.3
Gnome-Distributor: MandrakeSoft
Synopsis: Unable to change signature script path using edit dialog
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: 2.0.3
Description:
Description of Problem:
The user is unable to change the path to a script in an existing
signature.

Steps to reproduce the problem:
1. Open the Settings Dialong
2. Click on "Composer Preferences"
3. Select the "Signatures" tab
4. Click "Add Script"
5. In the dialog, enter a path for the script, ie. /usr/games/fortune
6. Click "OK"
7. Click on the "Edit"
8. Change the path for the script, ie. /usr/bin/fortune
9. Click "OK"

Actual Results:
The path reverts back to the original setting. This can be confirmed by
selecting "Edit" or noting that the change does not update the signature
in the preview window.

Expected Results:
The preview window or selecting "Edit" should show that the signature
has been updated.

How often does this happen?
Every time

Additional Information:


Unknown reporter: mlynx@comcast.net, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 André Klapper 2005-06-01 14:48:19 UTC 
thanks for reporting, however, this is a duplicate. :-)

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