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 451635 - gdmsetup does not handle GtkFileChooserButton's sensitivity well when files do not exist
gdmsetup does not handle GtkFileChooserButton's sensitivity well when files d...
Status: RESOLVED OBSOLETE
Product: gdm
Classification: Core
Component: general
2.19.x
Other All
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on: 404891
Blocks:
 
 
Reported: 2007-06-27 14:49 UTC by Lukasz Zalewski
Modified: 2010-06-04 20:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Lukasz Zalewski 2007-06-27 14:49:05 UTC
Please describe the problem:
gmdsetup does not handle GtkFileChooserButton and their corresponding checkbuttons (mainly Local/Logo, Remote/Logo, Users/DefaultFace) when file is defined but is not accessible on the filesystem (this does not apply when the config entry is an empty string)

Steps to reproduce:
1. point greeter/Logo (custom.conf) to a file that does not exist
2. update the daemon's config through UPDATE_CONFIG command
3. run gdmsetup and navigate to the Local tab (gdmlogin greeter)


Actual results:
Logo/Image checkbutton is active, and the corresponding filechooser widget is enabled but the filename string displayed is None

Expected results:
Logo/Image checkbutton is deactivated, and the corresponding filechooser widget is disabled (with None string displayed)

Does this happen every time?
Yes

Other information:
Before the widget is activated the only check that is performed is
if (!ve_string_empty (logo_filename)) 
however this only works if string is empty
what we should have is
if (!ve_string_empty (logo_filename) && access (logo_filename, R_OK) == 0)

The fix is included in the next gdmsetup patch
Comment 1 Brian Cameron 2007-07-31 20:26:18 UTC
Luckasz, where is the patch for this bug?  Do you mean to say it is attached to another bug report or will be attached to this bug report at some time?
Comment 2 Lukasz Zalewski 2007-07-31 21:10:31 UTC
Yes i have provided the fix in the patch for bug #404891
Comment 3 William Jon McCann 2010-06-04 20:18:15 UTC
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.