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 3355 - should be able to provide a buffer for GtkEntry
should be able to provide a buffer for GtkEntry
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: .General
1.3.x
Other other
: Normal enhancement
: future
Assigned To: gtk-bugs
gtk-bugs
: 152001 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 1999-11-05 23:30 UTC by Havoc Pennington
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Havoc Pennington 2001-01-27 19:46:55 UTC 
Package: gtk+
Version: 1.2.x

Werner Koch (author of GPG) requested the ability to provide a buffer to
GtkEntry to be filled in with the entry contents. The reason is that
passwords and such are normally placed in memory with paging disabled
(using mlock()), and normally you have to disable paging right at the
start of a program, so you can drop root privileges. So you want to give
GtkEntry an mlock()'d buffer.

havoc




------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-27 14:46 -------
This bug was previously known as bug 3355 at http://bugs.gnome.org/
http://bugs.gnome.org/show_bug.cgi?id=3355
Originally filed under the gtk+ product and general component.

Reassigning to the default owner of the component, gtk-bugs@gtk.org.
Comment 1 Havoc Pennington 2001-01-28 05:17:31 UTC 
I'm not sure if PangoLayout makes this easier or harder. Anyway, still
kind of painful to implement...
Comment 2 Havoc Pennington 2001-01-29 19:38:49 UTC 
Put all GTK 1.3.x bugs on 2.0.0 milestone
Comment 3 Havoc Pennington 2001-01-29 19:49:41 UTC 
Setting API-affecting bugs to the API freeze milestone
Comment 4 Havoc Pennington 2001-02-15 21:22:28 UTC 
Punting for 2.0
Comment 5 Owen Taylor 2001-04-26 14:59:40 UTC 
Actually, not at all painful to implement - 
gtk_entry_real_insert_text() is the only place that needs to be 
modified.

Of course, there is the possibility of the entered text
leaking out in other ways - GtkIMContext and so forth,
but it wouldn't be all in one chunk.
Comment 6 Owen Taylor 2004-09-06 17:45:28 UTC 
*** Bug 152001 has been marked as a duplicate of this bug. ***
Comment 7 Matthias Clasen 2004-11-30 14:01:56 UTC 
Lets WONTFIX this for now. There is no point in keeping this bug open further if
it hasn't attacted any duplicates and no volunteer has shown up to implement
this after 5 years...