summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Update Bulgarian translationAlexander Shopov2023-03-301-1/+1
| | | | (cherry picked from commit c262359ef3f127b913c78f5b346df15e8e73a611)
* datetime: Fix NTP switch getting out of sync.Robert Ancell2023-03-301-5/+5
| | | | | The state needs to be set to the state that was requested before the D-Bus call. The existing code used the state received from D-Bus, which will be the previous state.
* datetime: Use g_object_bind_property to show NTP stateRobert Ancell2023-03-301-20/+5
|
* datetime: Fix widget names and typesRobert Ancell2023-03-292-74/+72
|
* Depend on snapd-glib-2 (soup3 version)Robert Ancell2023-03-291-1/+1
|
* user-accounts: Set language-chooser to hide on closeMaksym Hazevych2023-03-291-0/+1
|
* Resolving suggestionsMaksym Hazevych2023-03-2919-35/+19
|
* Use `gtk_window_present` and `gtk_window_close`Maksym Hazevych2023-03-293-7/+7
|
* Remove unnecessary visibility changeMaksym Hazevych2023-03-2915-20/+0
|
* Replace all occurrences of 'gtk_widget_hide'Maksym Hazevych2023-03-2933-101/+101
| | | | | Replace all occurrences of 'gtk_widget_hide(smth)' with 'gtk_widget_set_visible(smth, FALSE)'.
* Replace all occurrences of 'gtk_widget_show'Maksym Hazevych2023-03-2941-100/+100
| | | | | Replace all occurrences of 'gtk_widget_show(smth)' with 'gtk_widget_set_visible(smth, TRUE)'.
* shell/style: Add workaround to make disabled pictures are painted as suchMarco Trevisan (Treviño)2023-03-281-0/+8
| | | | See: https://gitlab.gnome.org/GNOME/libadwaita/-/merge_requests/814
* illustrated-row, split-row: Add widget name and css classMarco Trevisan (Treviño)2023-03-282-0/+4
| | | | | It's not possible to theme them right now, while it could be useful so make them more recognizable in the widget tree.
* region: Fix label of formats for the login screenGunnar Hjalmarsson2023-03-281-0/+2
| | | | | | | | When system_region equals system_language, the UI should state the country of the system_language as the selected login screen formats, and that is not always "United States". Fixes: GNOME/gnome-control-center#2418
* thunderbolt: Have normal page contents clamped like othersEmad Saadat2023-03-281-192/+144
| | | | | | | | By converting the normal stack page (when thunderbolt is present) to an AdwPreferencesPage and making all constituent groups of widgets on the page AdwPreferenceGroups, we can make the page's content be clamped more similarly to other pages.
* panels/wifi: Make the security status and signal strength read by screen readersLukáš Tyrychtr2023-03-281-0/+10
| | | | | | Before this MR, the signal level was not available at all, and the security status only as an a11y description of an image. Now, these pieces of information are part of the description of the item itself.
* build-aux: Fix flatpak build manifest Emad Saadat2023-03-281-1/+1
| | | | | By removing an errant space in the libndp url. This prevented Settings from building using flatpak-builder, at least on my system.
* gitignore: Add flatpak-builder directory to .gitignoreEmad Saadat2023-03-281-0/+1
|
* notifications: Change "Apps" header to "App Notifications"Automeris naranja2023-03-271-1/+1
| | | | | | | | With this change, the header will clearly indicate that the user will tweak app notification settings, specially when using a screen reader. This is aligned with the following mockup: https://gitlab.gnome.org/Teams/Design/settings-mockups/-/blob/master/notifications/notifications.png
* Update Dutch translationNathan Follens2023-03-261-2391/+2902
| | | | (cherry picked from commit 5242d3ff69d05b0e48f921fac247a350e1b9b6e7)
* Update Indonesian translationKukuh Syafaat2023-03-261-187/+166
|
* Update POTFILES.inPiotr Drąg2023-03-251-2/+0
|
* cc-wifi-connection-list: Fix incorrect stylingCyber Phantom2023-03-241-5/+5
| | | | There should be a space before opening parenthesis.
* removed dead variableGotam Gorabh2023-03-241-1/+0
|
* user-accounts: Removed account activity windowGotam Gorabh2023-03-247-528/+0
| | | | | | | This changes remove the account activity window or login history as it is less used or no use. Fixes: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2096
* network: Increase maximum MTU value from 10000 to 65536Simon Arlott2023-03-242-2/+2
| | | | | | | | | | | | | | | | | | | | | | The maximum MTU value of 10000 is too low for USB Ethernet, which has a maximum (for Linux USB gadgets) of 15412 bytes (although the upper limit is the USB wMaxPacketSize which goes up to 4294967295 bytes): linux/drivers/usb/gadget/function/u_ether.c:#define GETHER_MAX_MTU_SIZE 15412 Multiple Intel NICs can use an MTU of 16110 bytes: linux/drivers/net/ethernet/intel/e1000/e1000_hw.h:#define MAX_JUMBO_FRAME_SIZE 0x3F00 linux/drivers/net/ethernet/intel/e1000e/defines.h:#define MAX_JUMBO_FRAME_SIZE 0x3F00 linux/drivers/net/ethernet/intel/igbvf/defines.h:#define MAX_JUMBO_FRAME_SIZE 0x3F00 The NetworkManager limit is 4294967295 bytes but this is unreasonable in a typical enivornment because of the memory required for packets of that size. The maximum IPv4 and IPv6 (without using Jumbograms) packet size is 65535 bytes so increase the maximum MTU value to 65536 allow full size IP packets to be used. There is a corresponding change in network-manager-applet.
* sharing: Disable AdwActionRow markup for networksvelsinki2023-03-241-0/+2
| | | | | | | | Network names have many allowed characters, among which `&`, `<`, and `>`. These are problematic for Pango markup. By default, AdwActionRow has markup enabled for its title. We could escape strings at every `adw_preferences_row_set_title` call, but this might be easy to forget in the future. Instead, let's disable markup altogether for these rows.
* network: proxy: Keep current mode when enabling proxyMohammed Sadiq2023-03-241-2/+4
| | | | | | Don't force 'automatic' proxy mode when the user enables proxy. Closes #2401
* network: proxy: Add a method to get selected proxy modeMohammed Sadiq2023-03-241-12/+27
| | | | | Also replace the code with the method where it's used. We shall use this elsewhere in the next commit
* cc-wifi-connection-list: Don't show empty listboxCyber Phantom2023-03-231-0/+6
| | | | | | When there are no wifi networks, the wifi listbox is still visible as a thin line which doesn't look good. Fix this by setting the visibility based on the number of networks.
* split-row / illustrated-row: Keep track of the resources pathMarco Trevisan (Treviño)2023-03-232-8/+21
| | | | | | | | | | | | | We pass to the setter a const char* but we don't control the ownership of that and it may be returned later from the property getter. While this is not causing any crash right now, going in the inspector and try to check the property leads to some scrambled chars which seems an indication of a memory error. In general the string passed to these APIs could come from anywhere and it's not guaranteed that it's always a constant string (and in fact is not in some cases).
* network: Validate max length of hotspot SSIDAthul Iddya2023-03-232-16/+46
| | | | | | | | | | Added validation for maximum length of hotspot SSID, which cannot exceed 32 bytes. As this error might be unintuitive, an error message was also added below the entry row similar to the password entry row. The error messages are generic as some characters can require multiple bytes and mentioning the byte limitation might be too technical. Fixes #1065
* remove extra lineGotam Gorabh2023-03-231-1/+0
|
* keyboard:Fix cancel button issueGotam Gorabh2023-03-231-0/+2
|
* display: Removed the loop from the snapping functionEmilia Daria Majewska2023-03-231-8/+2
| | | | In all my tests, the snapping algorithm was successful on the first pass.
* display: Remove the monitor argument for cc_display_config_snap_outputEmilia Daria Majewska2023-03-233-7/+3
| | | | | The function tries to snap all the outputs anyway, so might as well remove the unnecessary argument.
* display: Try snapping all the displays after a config changeEmilia Daria Majewska2023-03-231-8/+34
| | | | | | | | | This issue was originally addressed in !257 ("display snap after changes"). However it only dealt with a two-monitor setup, so the user is still unable to rotate the middle display with three or more monitors. This commit tries to snap the displays until all are adjacent to another.
* Update Lithuanian translationAurimas Černius2023-03-221-51/+64
| | | | (cherry picked from commit 74fbf5400be00a3380d11e9c904087d3d25aad02)
* panels/mouse: Simplify binding of touchpad sensitive widgetsMarco Trevisan (Treviño)2023-03-222-24/+4
| | | | | | Instead of creating multiple and more complex GSetting bindings for the sensitive state, just bind the sensitivity of the touchpad widgets to the active state of the touchpad toggle switch
* panels/mouse: Do not bind sensitivity to touchpad settingsMarco Trevisan (Treviño)2023-03-221-5/+10
| | | | | | If doing so, these options may be marked as sensitive by GSettingsBind, ignoring the send-events global setting binding; and causing the widgets to be always sensitive regardless the touchpad state.
* sound: Prevent duplicate sound device entriesvelsinki2023-03-221-1/+5
| | | | | | | | | | | | For unknown reasons, GVC mixer control can sometimes signal a new device with the same id as one that was added before. This means that in `device_added_cb`, a duplicate entry with that id is created, in my case with a different name. However, the last one added is valid, but that one cannot be selected because all other logic in the sound panel assumes the first hit in `get_iter` is valid. This breaks sound input selection then. The fix is easy; only add a new list entry if none with that id exists.
* Update Occitan translationQuentin PAGÈS2023-03-221-110/+126
|
* color-panel: Do not try to access to null pointer in destructionMarco Trevisan (Treviño)2023-03-211-1/+2
| | | | | | | | | | | | | | | | | | | | | | | During destruction toolbar_devices is nullified, but gtk_widget_in_destruction() does not perform a NULL-check, and we could crash: ==22708== Invalid read of size 1 ==22708== at 0x505CC0B: gtk_widget_in_destruction (gtkwidget.c:10643) ==22708== by 0x189553: gcm_prefs_list_box_row_selected_cb (cc-color-panel.c:1708) ==22708== by 0x4A61714: g_cclosure_marshal_VOID__OBJECTv (gmarshal.c:1910) ==22708== by 0x4A5E148: _g_closure_invoke_va (gclosure.c:895) ==22708== by 0x4A784F3: g_signal_emit_valist (gsignal.c:3462) ==22708== by 0x4A78722: g_signal_emit (gsignal.c:3612) ==22708== by 0x4F5B121: gtk_list_box_remove (gtklistbox.c:2420) ==22708== by 0x4F5B222: gtk_list_box_dispose (gtklistbox.c:439) ==22708== by 0x4A63338: g_object_unref (gobject.c:3891) ==22708== by 0x4EAA994: gtk_box_dispose (gtkbox.c:230) ==22708== by 0x4A63338: g_object_unref (gobject.c:3891) ==22708== by 0x4EAA994: gtk_box_dispose (gtkbox.c:230) ==22708== Address 0xfffffffffffffeb2 is not stack'd, malloc'd or (recently) free'd See: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2009913
* dispaly: Allow configuring all monitors and apply settings at onceMarco Trevisan (Treviño)2023-03-212-0/+32
| | | | | | | | | | When multiple monitors are available, it's not possible anymore to configure them all and eventually apply all the changed parameters. To make this possible again, add a back button in the apply titlebar that is shown only when we are in the display-settings child. See: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012043
* Update Turkish translationSabri Ünal2023-03-191-45/+58
|
* Update Catalan translationJordi Mas i Hernandez2023-03-191-33/+46
| | | | (cherry picked from commit 2294116b7fd8ccc721f6dc24225d377694caef1a)
* Update Finnish translationJiri Grönroos2023-03-181-7/+13
| | | | (cherry picked from commit 60d4f58867dce06f778b991607cb1922bbd54871)
* Update Bulgarian translationAlexander Shopov2023-03-181-30/+42
| | | | (cherry picked from commit 5a4dade93213dec7436bbbc0b85a3f08110cba6a)
* Update Basque translationAsier Sarasua Garmendia2023-03-181-30/+42
| | | | (cherry picked from commit 4343bd4ca453cfddd3b422ca1891878d6ffb05db)
* mouse: Prevent infinite loop on settings changesMarco Trevisan (Treviño)2023-03-171-0/+4
| | | | | | | | | We may get an infinite loop on mouse panel startup, in fact the scroll method changed event emits a gsettings change that also leads to a notify::use-default emission that again tries to writes to settings, leading to another change: infinitely. Closes: #2405
View Lorry Controller Status