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 312732 - Drivel complains about a @ character in the username
Drivel complains about a @ character in the username
Status: RESOLVED FIXED
Product: drivel
Classification: Deprecated
Component: general
2.0.x
Other All
: Normal minor
: ---
Assigned To: Todd Kulesza
Todd Kulesza
Depends on:
Blocks:
 
 
Reported: 2005-08-06 03:36 UTC by Don Smith
Modified: 2006-04-23 16:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to correct the bug (494 bytes, patch)
2006-03-06 17:09 UTC, palfrey
none Details | Review

Description Don Smith 2005-08-06 03:36:58 UTC
Please describe the problem:
I use friendster for my blog, which uses typepad. Friendster requires my email
address as a username including the @ sign, and while drivel accepts an @
character in the username, it complains about every other keystroke in the
username thereafter

Steps to reproduce:
1. open drivel
2. put a username with an @ character in
3. click ok to various dialog boxes


Actual results:
A dialog box pops up after every following keystroke in the username field

Expected results:
drivel accepts the @ character without complaint

Does this happen every time?
yes

Other information:
Thanks for all the great work on drivel
Comment 1 palfrey 2006-03-06 17:09:39 UTC
Created attachment 60769 [details] [review]
Patch to correct the bug

This patch seems to correct the problem for me, but may break other stuff. Try it and see!
Comment 2 Jean-Baptiste Quenot 2006-04-07 17:31:34 UTC
Great!  I was looking for this patch.  Thanks for this, works perfectly.
Comment 3 Todd Kulesza 2006-04-23 16:04:34 UTC
Cool, this takes care of the issue.  The list of restricted characters was from the days when Drivel only supported LiveJournal, and seemed like a cool way to catch serious typos right away.  Now that we support more journal types, that list needs to be updated.  Thanks!