** Description changed: Cheese displays and appears to accept invalid burst-delay values, but silently continues using the previous valid configuration. When an out-of-range value is entered, Cheese updates the GUI to show the new value, but the underlying GSettings value is not updated. The application silently keeps using the previously valid value without notifying the user, resulting in a GUI/backend state inconsistency. - Environment： OS: Ubuntu 22.04 LTS (64-bit) Application: Cheese 41.1 - Steps to Reproduce: 1. Launch Cheese. 2. Open Preferences. 3. Set Burst Delay to a valid value (for example, 5 seconds). 4. Verify that burst mode operates correctly with the configured delay. 5. Return to Preferences. 6. Change Burst Delay to an out-of-range value, such as:10000 7. Observe that the Preferences dialog displays the newly entered value. 8. Start burst capture. - Actual Results: The Preferences dialog displays the newly entered value (for example, 10000). However: * The application does not use the displayed value. * Burst capture continues using the previously valid delay value. * No warning or error message is shown to the user. * The configuration write operation fails internally. Example: 1. Set Burst Delay = 5 2. Burst capture waits 5 seconds 3. Set Burst Delay = 10000 4. Preferences display 10000 5. Burst capture still waits 5 seconds Terminal output shows: GLib-GIO-WARNING **: g_settings_set_value: value for key 'burst-delay' in schema 'org.gnome.Cheese' is outside of valid range This indicates that GSettings rejects the value, but the GUI continues to display it as if the configuration were successfully applied. - Expected Results: When a user enters an invalid value: * The GUI should reject the value, OR * The value should be clamped to the supported range and clearly communicated to the user, OR * An error message should be displayed. The GUI should never display a configuration value that is different from the value actually used by the application. - # Additional Findings Observed behavior: * Value 0 is effectively treated as 1 second. * Values from 1 to 10 work correctly. * Values greater than 10 are displayed by the GUI but are not applied. * The application continues using the previous valid value. This suggests a synchronization problem between the GUI configuration state and the underlying GSettings state. - # Impact + Impact: This issue can mislead users into believing that a configuration change has been applied successfully when the application is actually operating with a different configuration.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2157585 Title: GUI displays invalid burst-delay values while runtime silently uses previous valid value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/2157585/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
