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 570024 - Account data corruption if Authentication User is blank
Account data corruption if Authentication User is blank
Status: RESOLVED FIXED
Product: ekiga
Classification: Applications
Component: general
3.0.x
Other All
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2009-01-31 21:18 UTC by Alec Leamas
Modified: 2009-02-01 21:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Alec Leamas 2009-01-31 21:18:27 UTC
Please describe the problem:
If I leave the field "Authentication User" in the Edit Account dialog, a subsequent Caht | Quit + restart cycle corrupts the account data. In my case the Authentication USer, password and timeout are more or less random.

Steps to reproduce:
1. Wipe out eny existiong config; ekiga-config-tool --clean
2. Reinstall ekiga, run the configuration wizard.
3. Run the Accounts | Edit Account dialog for the Ekiga account
4. Clear the "Authentication User" field, close dialog.
5. Chat | Quit
6. Restart ekiga
7. Verify corrupted data in the Edit | Accounts | Edit Account dialog.


Actual results:
Authentication User, password and timeout are more or less random.

Expected results:
They should not be random :-). Valgrind should not report illegal memory accesses (see below).

Does this happen every time?
Yes

Other information:
Valgrind reports accesses to unitialized memory iff the Authentication User field is blank.

This is on Fedora 10/X86_64
Comment 1 Damien Sandras 2009-02-01 21:08:11 UTC
I have fixed it. Thanks for finding this !