buddiesofbudgie / budgie-control-center Goto Github PK

Description

I tried to run 'meson build' command but i got error missing mm-glib dependency. i tried to find the dependency using 'eopkg sr' but couldn't find the dependency

Budgie version

Operating system

Solus

Steps to reproduce the issue

Actual result

Expected result

Additional information

Budgie version

10.6.1

Use-cases

The expected behavior for anyone used to using Windows on a laptop would be to right-click by clicking the right half of the bottom corner of the touchpad, instead of clicking the touchpad with two fingers. Most Linux DEs I tested have an option to choose whether to fire a right-click with two fingers OR by clicking the bottom-right section of the touchpad. This is another feature I would consider a given.

Proposal

Inside Budgie Control Center -> Mouse & Touchpad -> Touchpad, either directly above or below the "Tap to Click" option, add an option with the title "Right click", with a dropdown menu with two options: "With two fingers" or "Bottom-right corner".

References

No response

After coming out of sleep mode, Line Out disappears and the sound is automatically connected via the front ports. The problem can be solved only by twitching the plug at the line output.
I noticed that after the update, the microphone basically fell off. Doesn't react to anything at all.
And the icons floated.

Linux Solus 4.3
Kernel 5.15.26-211.current
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)

Current BCC version: 1.0.1
OS: Solus

Before Budgie v10.6.0, Solus Budgie had many more menu entries in Menu --> System Settings which came from Gnome Control Center, like in the picture below.

But now with Budgie Control Center there are none.

Not sure if this was intentional, or if it is something that Distribution has to provide.
Opened this issue as Feature Request than Bug Report, I think it fits better here.

Use-cases

The use cases are that users can search for example for Display in menu and then by clicking it find the setting they want.

Description

Hi! I have a setup with two monitors with my external on left side of laptop. So, how by default the monitors always be added on the right side, i need switch de positions of displays in control center. But, on switch, i notice that positions regularly rollback to the default positions in interval between 15 and 30 seconds.

Budgie version

budgie-control-center 1.2.0.

Operating system

Archlinux.

Steps to reproduce the issue

1. Make a fresh install of Archlinux with budgie desktop.
2. Add a new monitor with a hdmi cable.
3. Switch the positions of display, putting the external monitor on left side.
4. Wait 15 ~ 30 seconds to the system rollback to default positions of display.

Actual result

Positions of display altered by budgie-control-center don't be permanently.

Expected result

Positions of display altered by budgie-control-center be permanently.

Additional information

I tried switch the positions with arandr and works fine!

Description

Tried to enable auto login in Budgie Control Center but after reboot it keeps asking for password. I've also noticed some weird toggle behavior like jumping back to disabled after trying to enable it.

I workaround it by manually creating a file /etc/lightdm/lightdm.conf.d/autologin.conf with the following content:

[Seat:*]
autologin-user=fedora

Budgie version

budgie-desktop 10.7.1 / budgie-control-center 1.2.0

Operating system

Fedora 38

Steps to reproduce the issue

1. Go to Budgie Control Center
2. Click on User
3. Try to enable auto login

Actual result

Auto login toggle jumps back to disabled state

Expected result

Auto login can be enabled

Additional information

Description

When setting the power button behavior to "Power Off" via budgie-control-center, the power button has no effect despite setting it to "Suspend" opening the suspend dialog.

Budgie version

10.7.2

Operating System

EndeavourOS

Steps to reproduce the issue

1. Open Budgie Control Center
2. Set power button behavior to "Power Off"
3. Press the power button

Actual result

No dialog appears

Expected result

Power off dialog appears

Additional information

Please let me know if there is anything else I can provide.

Description

This is more likely a duplicate of https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/93
Which was fixed with https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/92
But the issue persists in Fedora 38 Budgie (and probably other distributions as well).

Budgie version

10.7.1

Operating System

Fedora 38

Steps to reproduce the issue

1. Go to Budgie Control Center
2. Click on Sharing
3. Enable Remote Desktop
4. Reboot
5. Now Remote Desktop is disabled again

Actual result

Remote Desktop is disabled again after reboot

Expected result

Remote Desktop should be enabled after reboot

Additional information

No response

The project links to GVC for its sound control - it is dated 8e7a5a4c3e51007ce6579292642517e3d3eb9c50 which is Jan 12 2022.

There has been several commits since then - should we rebase GVC?

I don't personally know enough in this area to know what the risks are. From a build point of view - BCC builds with the latest commit made today.

Description

Just updated budgie-desktop to 10.6, read the blog post and tried to install budgie-control-center. I got the following error which looks like it can't replace system package. I am not really sure. Will this get added to arch repos? and should I just wait for that. Thank you.

budgie-control-center-git and gnome-control-center are in conflict. Remove gnome-control-center? [y/N] y

Package (2)                Old Version  New Version             Net Change

gnome-control-center       41.4-1                               -21.03 MiB
budgie-control-center-git               v1.0.0.r2.g5cb3b3deb-1   21.12 MiB

Total Installed Size:  21.12 MiB
Net Upgrade Size:       0.09 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                     [------------------------------------] 100%
(1/1) checking package integrity                                   [------------------------------------] 100%
(1/1) loading package files                                        [------------------------------------] 100%
(1/1) checking for file conflicts                                  [------------------------------------] 100%
error: failed to commit transaction (conflicting files)
budgie-control-center-git: /usr/local/share/man exists in filesystem (owned by filesystem)
Errors occurred, no packages were upgraded.
 -> exit status 1

Budgie version

Budgie 10.6 and attempting to install budgie-control-center-git v1.0.0.r2.g5cb3b3deb-1

Operating system

EndeavourOS

Description

Budgie just seems to ignore the option totally and uses the same source for all windows (the other option)

Budgie version

10.7.1

Operating System

Fedora 38

Steps to reproduce the issue

1. Go to System Settings
2. Go to Keyboard tab
3. Have at least two Input Sources
4. Change Input Source Switching to Switch Input sources individually for each window

Actual result

The input source is uniformed across all windows

Expected result

Each window has its own associated input source (as in GNOME)

Additional information

No response

Current budgie-control-center version

1.1.1

Use-cases

When adjusting the velocity of the cursor in the touchpad settings, i find it uncomfortable to select the velocity that I want and I think this is because the minimum velocity is ridiculously slow. So when I move the slider from maximum (top-right) to the minimum (top-left) I have to move my finger across the trackpad many times to go back to the maximum again (sometimes if I accidentally move the cursor to the very left of the screen it takes a while just to reach the slider again). I don't think that there is anybody who wants the velocity of the cursor that much slow and it feels sketchy in the setting up process.

Also I think it would be great if the scrolling velocity could be adjustable too, I personally would slow it down a little bit. I don't know if these features are difficult to implement but I think are little details that would improve the experience of customizing the budgie desktop.

PD:This is my first time doing a Feature Request or interacting with a Open Source project, so I hope i've expressed the request okay and in the right place.

We have a edge tiling switch in BDS

... and we have a similar edge tiling here in BCC

BCC just sets the mutter edge key whereas BDS sets both the mutter edge key and the Solus edge key.

So should we

1. leave this here on BCC because it has a better graphic and explanation.... and remove from BDS ... or
2. should we leave in BDS and remove from BCC .... or
3. ensure via budgie daemon that setting the mutter key / solus key individually sets the other key?

task reference to look through all commits (minus translations) to see if there are anything worth cherry-picking.

So commits may be useful but will need reworking due to changing from libhandy to libadwaita.

Task list for the remaining parts of the conversion to be done before we can start testing etc. Anyone welcome to dive in for any of this/add to etc.

• polkit stuff - rename to be budgie
• look at the gnome/its stuff - is this needed?
• Merge in various commits from the GNOME 41 branch https://gitlab.gnome.org/GNOME/gnome-control-center/-/commits/gnome-41
• Look to see why compilation throws i18 deprecated notices - maybe this? https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/37b29c32cbecfd89c9c5e0169e0f2876f00ef5eb
• Debian packaging for GNOME Control Center has a number of patches - why are they not upstream? Are they useful for all budgie users?
• Ubuntu packaging for GNOME Control Center has a number of patches - why are they not upstream? Are they useful for all budgie users?
• Create debian package for budgie-control-center and see if both gnome-control-center and budgie-control-center will install simultaneously - this will help identify what areas still need to be 'budgied' - Package partially done.

Description

The desktop file says "Budgie Control Center" https://github.com/BuddiesOfBudgie/budgie-control-center/blob/master/shell/budgie-control-center.desktop.in.in ... and the application title says "Settings".

We should be consistent.

Its arguable that "Settings" is too close to "Budgie Desktop Settings" - so maybe rename to "Budgie Control Center" ... or maybe something else?

Budgie version

v0.3

Operating system

N/A

Steps to reproduce the issue

See the icon in the Menu and the title of the applicatoin

Actual result

as above

Expected result

Should be consistent

Additional information

Description

From this commit https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/03299794a6c95f9ceff8d6ca1d5a90ec4366a4c0 gnome-shell will now deal with print screen keygrabs.

Thus our fork should logically switch to budgie - must do anyway - without the change, the now non-existent schema change will mean crashes will be observed with GSD v42 + BCC

Budgie version

0.3.0

Operating system

N/A

Steps to reproduce the issue

N/A

Actual result

N/A

Expected result

Additional information

Current budgie-control-center version

1.0.2

Use-cases

volume step via keyboard is a static 6 increment. On some computers this is a large volume step.

Proposal

Sounds section.

Bind a volume step control or similar "+/-" to the media dconf key

References

https://askubuntu.com/a/1248709

Discussed on matrix general channel.

In my opinion budgie control center is not a good name for 3 reasons

1. It is longet than what it should be imo considering some DEs and even windows just use settings
2. When someone wants to open the settings app it is a muscle memory to press the super key and write settings, but budgie control center doesn't have setting in its name so it doesn't show and makes the person a little annoyed (it does for me at least)
3. and budgie control center feels more like an app that controls budgie DE itself rather than the system, after all it is mostly settings for hardware of the system than software side that budgie will interact

In my opinion you can rename the apps to system settings and desktop settings, I feel this will be easier to understand and solve the search problems as well

Current budgie-control-center version

budgie-control-center 1.1.1
budgie-desktop 10.6.4
Arch Linux
I use gnome-calendar with my Nextcloud and want to get rid of gnome-control-center but gnome-calendar has this dependency.

Can this be solved?
Or is there a plan for a Budgie calendar with Nextcloud support?

TIA
I use Budgie now some years and it's great that Budgie is no longer just focused on Solus. 👍

I received the following ninja error:
./panels/sound/cc-alert-chooser.c:139:30: error: *USER_DIR_MODE* undeclared (first use in this function) 139 g_mkdir_with_parents (dir, USER_DIR_MODE);

Current budgie-control-center version

v0.3

Use-cases

Whilst ideally we should have a consistent settings based app amalgamating Settings and Budgie Desktop Settings. This is perhaps v11 territory.

Proposal

As a minimum lets consider adding a button on the headerbar to open budgie desktop settings i.e. at least have an easier navigation route.

Ideally we should have a similar navigation from budgie desktop settings to "Settings" ... but budgie desktop settings window is not headerbar based. Should it be?

References

N/A

Description

"Privacy" and "Online Accounts" panels in "Budgie Control Center"
get crashed when the language is different than English.

Budgie version

10.8.2

Operating System

FreeBSD 14.0-RELEASE-p3

Steps to reproduce the issue

1. Open "Budgie Control Center"
2. Go to "Region & Langauge" panel and select "Polish" language.
3. Logout - as panel suggest
4. Login again
5. Open "Budgie Control Center" again
6. Check "Privacy" and "Online Accounts" panels

Actual result

Panel crashes, sometimes it's impossible to launch "Budgie Control Center" it keeps crashing right after it open. Sometimes opens and opens in white theme (previously was set to dark). Changing the theme doesn't work.

Expected result

Possibility to open "Privacy" and "Online Accounts" panels (in any language) in "Budgie Control Center" without crashing

Additional information

No response

Description

No option to disable lockscreen notifications in the budgie control centre

Budgie version

budgie-control-center 1.2.0

Operating system

EndeavourOS

Description

Building BCC under debian bookworm - lintian warning displayed
Running lintian...
W: budgie-control-center: no-manual-page [usr/libexec/budgie-cc-remote-login-helper]
W: budgie-control-center: no-manual-page [usr/libexec/budgie-control-center-print-renderer]

Budgie version

v1.2.0

Operating system

Debian Bookworm

Steps to reproduce the issue

sbuild from source with lintian options

Actual result

see description

Expected result

No obvious lintian warnings

Additional information

Current budgie-control-center version

v1.1.1

Use-cases

Where linux fingerprint devices are supported, some login managers such as GDM3 have direct support built in to enable login.

Some login managers such as lightdm need administrator action to enable login.

Budgie could support fingerprint login via BCC with a tweak and a tuck.

Proposal

In GNOME Control Center - once a fingerprint device is detected, a new option in the Users Panel appears enabling the administrator to enrol fingerprints.

This is not currently available in BCC without using GDM3 since the code is looking for a schema key that is delivered only in GDM3.

The proposal here is to enable fingerprint enrolling via the BCC users panel for our recommended login manager - lightDM.

The suggestion here is to remove the check for the enable-fingerprint-authentication key in the GDM login schema and instead substitute it for a check if a known fingerprint device is plugged in (code is already there for this check).

This leaves the issue how to inform the user whether they have enabled lightdm (via PAM) for fprintd <-- the module that does the authentication.

sudo pam-auth-update --enable fprintd

The above enables fprintd globally i.e. not specific to lightdm/gnome-screensaver. It writes to /etc/pam.d/common-auth

auth 	sufficient	pam_fprintd.so max-tries=1

Adding the above line to /etc/pam.d/lightdm and /etc/pam.d/gnome-screensaver directly before the "@include common-auth" limits fingerprint login to both lightdm and gnome-screensaver.

GDM3 provides the PAM fprintd configuration out of the box. LightDM doesnt.

I don't know of a way to test if fprintd has been enabled in PAM. We can either ignore this particular issue and assume the user knows how to-do things. Or somehow give the user via the fingerprint dialog some sort of hint what they need to-do.

Thoughts.

References

N/A

Budgie Version : 10.6.1
OS : Ubuntu 22.04 LTS
Display server : X11

Hello,
There are untranslated strings (French language) in the Budgie Control Center.
See attached images.
Regards,
Roxfr

Budgie version

10.8.1

Use-cases

I've used KDE and Gnome for a while before switching to Budgie and both desktop environments had Fn key hotkeys implemented properly. Fn+F1 mutes audio, Fn+F2 lowers volume, Fn+F3 raises volume, Fn+F5 lowers screen brightness and so on. xev shows these actions as XF86MonBrightnessDown, XF86AudioMute, etc. There was also an overlay window that shows when you perform those actions.

On Budgie this is completely missing. I also tried binding these in the control center but there's no entry for changing screen brightness, and the Fn key itself is recognized rather than the full combination so I wasn't able to.

I also took a quick look and this also seems to mean I have no way to change screen brightness from the DE. If it's not in power settings, where is it?

Proposal

No response

References

No response

Description

v41.x of GCC released - need to sync:

• https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/badd326299e55ca751a7a24e6e314a2f069f3262
• https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/8d318a7228d3de90ccb4317e0358d1d3af97462d
• https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/212ab19dfde8573782d5b5ddee230b4e9afda2a2

Maybe consider cherry-picking the umpteen translation updates as well

Budgie version

0.3

Operating system

N/A

Steps to reproduce the issue

N/A

Actual result

N/A

Expected result

Additional information

Looking at some of the keyboard shortcuts, they are gnome-shell specific - i.e. we don't expose them in budgie-wm

For example Search and "Restore the keyboard shortcuts"

[ ] The first task is to go through all the shortcuts and identify if they really work under budgie.

[ ] the second task is to look at removing here in the BCC code

[ ] The last task is to look at developing some sort of override mechanism to hide shortcuts delivered by - for example - mutter

On the background panel the top previews shows "Activities" and the gnome-shell panel.

https://github.com/BuddiesOfBudgie/budgie-control-center/blob/master/panels/background/cc-background-preview.ui

Need a more "budgie" way to show the preview ... or at the very least remove the gnome-shell panel.

Description

Speaker icons are missing

Budgie version

10.6

Operating system

Arch Linux

Actual result

During build I am crashing on needing libwacom despite not using any wacom hardware. I noticed that while gnome-control-center has this set as optional budgie-control-center doesn't. Maybe a check on the dependencies to see which ones are required would be best.

Maybe an idea of checking what optional build flags gnome-control-center has and take them over? I didn't check beyond libwacom atm myself.

This is an GNOME-Control-Center issue now public.

https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2794

This has been resolved on ubuntu - but only on ubuntu itself and how it activates remote shell ssh.

The patch ubuntu produced actually breaks remote shell capability for other distros that don't use ubuntu's activation method.

As such Ubuntu Budgie and others also lose the remote login option (it hides itself) once the Ubuntu patch is applied.

We should wait and incorporate the upstream patch once the final decisions are made to make the CVE resolution acceptable to the wider community.

Description

Help functionality is absent, search returns nothing.

Budgie version

10.6.2
Theme: "Plata-Compact"

Operating system

Solus 4.3 Fortitude

Steps to reproduce the issue

• Open Budgie Control Center by right clicking on the desktop and selecting "System Settings"
• Click on the three vertical dots right from the text "Budgie Control Center"
• Choose "Help"

Actual result

An empty window appears, with normal title bar showing "Help", a favourites star icon, looking glass icon, three vertical dots icon.
Clicking the looking glass results in a search field opening. Entering relevant terms like "screen" or "volume" or whatever doesn't return anything at all, window stays empty.

Expected result

Some info related to the entered search term or a menu to navigate in the help info?

I try to move one display to the left in the settings but it keeps reverting it back to default. Also I don't get any confirmation dialogue at all.

../src/intel/isl/isl.c:2241: FINISHME: ../src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is disabled, but a workaround is available.
12:14:08.0699                      GLib:    DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
12:14:08.0707         cc-object-storage:    DEBUG: Finished creating D-Bus proxy for CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Color,/org/gnome/SettingsDaemon/Color,org.freedesktop.DBus.Properties)
12:14:08.0707         cc-object-storage:    DEBUG: Adding object GDBusProxy (CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Color,/org/gnome/SettingsDaemon/Color,org.freedesktop.DBus.Properties) → 0x7fbfa8024b50) to the storage
12:14:08.0707         cc-object-storage:    DEBUG: Finished creating D-Bus proxy for CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Color,/org/gnome/SettingsDaemon/Color,org.gnome.SettingsDaemon.Color)
12:14:08.0707         cc-object-storage:    DEBUG: Adding object GDBusProxy (CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Color,/org/gnome/SettingsDaemon/Color,org.gnome.SettingsDaemon.Color) → 0x7fbf9c0032e0) to the storage
12:14:08.0707          display-cc-panel:    DEBUG: setting adjustment -1.000 to -1:-0
12:14:08.0707          display-cc-panel:    DEBUG: setting adjustment -1.000 to -1:-0
12:14:08.0707         cc-object-storage:    DEBUG: Finished creating D-Bus proxy for CcObjectStorage::dbus-proxy(org.gnome.Shell,/org/gnome/Shell,org.gnome.Shell)
12:14:08.0707         cc-object-storage:    DEBUG: Adding object GDBusProxy (CcObjectStorage::dbus-proxy(org.gnome.Shell,/org/gnome/Shell,org.gnome.Shell) → 0x7fbf9c003050) to the storage
12:14:08.0707      diagnostics-cc-panel:    DEBUG: ABRT appeared
12:14:08.0716      thunderbolt-cc-panel:    DEBUG: Thunderbolt panel visible: yes
12:14:08.0716          display-cc-panel:    DEBUG: Resetting current config!
(budgie-control-center:6066): dconf-DEBUG: 12:14:08.718: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:08.718: watch_established: "/org/gnome/mutter/" (establishing: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:08.719: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:08.719: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:08.731: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:08.731: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:12.121: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:12.126: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
12:14:14.0219          display-cc-panel:    DEBUG: Resetting current config!
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.265: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.281: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.283: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.284: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.301: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.302: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
12:14:14.0328          display-cc-panel:    DEBUG: Resetting current config!
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.330: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.341: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.342: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.342: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.353: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.353: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
12:14:14.0353          display-cc-panel:    DEBUG: Resetting current config!
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.354: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.362: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.362: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.363: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.374: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.374: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
12:14:14.0777          display-cc-panel:    DEBUG: Resetting current config!
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.780: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.800: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.804: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.804: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.828: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.828: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
12:14:14.0828          display-cc-panel:    DEBUG: Resetting current config!
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.829: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.839: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.839: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.839: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.850: watch_fast: "/org/gnome/mutter/" (establishing: 0, active: 1)
(budgie-control-center:6066): dconf-DEBUG: 12:14:14.850: unwatch_fast: "/org/gnome/mutter/" (active: 2, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:17.414: change_fast
(budgie-control-center:6066): dconf-DEBUG: 12:14:17.421: unwatch_fast: "/org/gnome/desktop/session/" (active: 1, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:17.430: unwatch_fast: "/org/gnome/mutter/" (active: 1, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:17.430: unwatch_fast: "/org/gnome/desktop/lockdown/" (active: 1, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:17.430: unwatch_fast: "/org/gnome/desktop/screensaver/" (active: 2, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:17.433: unwatch_fast: "/org/gnome/desktop/screensaver/" (active: 1, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:17.433: unwatch_fast: "/org/gnome/desktop/notifications/" (active: 1, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:17.433: unwatch_fast: "/org/gnome/settings-daemon/plugins/color/" (active: 1, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:17.433: unwatch_fast: "/org/gnome/desktop/interface/" (active: 1, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:17.435: unwatch_fast: "/org/buddiesofbudgie/control-center/" (active: 1, establishing: 0)
(budgie-control-center:6066): dconf-DEBUG: 12:14:17.435: sync
12:14:17.0436         cc-object-storage:    DEBUG: Destroying cached objects

Description

Budgie Control Center crashes when trying to open it. it will crash and send you back tot he login screen. This is while running under a virtual Machine QEMO/KVM using virt-manager. A couple of things that it may not be a virtual machine problem, I reinstalled budgie-control-center it didn't help, I installed gnome-control-center this is working fine except the theme, running "budgie-control-center --version" in the terminal produces the same crash result. While I do not beleive it is virtual machine issues, I have only tested under a virtual machine and not on bare metal. I typically installed everything I plan to use under a virtual machine to see if everything is working before installing to bare metal

journal : https://pastebin.com/L2tMzpuY
dmesg: https://pastebin.com/hQuUGSAG
Installed Packages(pacman -Q) : https://pastebin.com/NVDX1Jf4

Budgie version

budgie-control-center --version crashes when ran in terminal, however its the latest version budgie-control-center 1.2.0-1 from archlinux repos

Operating system

Archlinux

Steps to reproduce the issue

Install Budgie desktop on a fresh install of archlinux under a virtual machine

Actual result

Crashes and goes back to the login screen

Expected result

To display budgie control center without crashing

this package is essential for modifying system elements

Only these packages are in the 'Community' repository.

there is no maintainer available?

Description

I’m using Solus. After every reboot or more specifically logout + login I have to reset certain key combos and the keyboard repeat-interval & delay. Moreover, global hotkeys for GoldenDict just do not work at all. All of that started misbehaving several month ago after running eopkg it --reinstall -c desktop.budgie as far as I can tell.

Budgie version

10.7.2

Operating System

Solus 4

Steps to reproduce the issue

1. eopkg it --reinstall -c desktop.budgie
2. Set or remove keyboard shortcuts
3. logout + login or reboot

Actual result

+ no longer works to switch applications amongst others. Resetting that keyboard shortcut only works for the duration of the session but survives sleep + wake cycles (Suspend).

Expected result

Custom keyboard shortcuts are persisted and standard/default ones work as expected.

Additional information

No response

Description

wiregurad connections can be added via budgie-control-center nor it doesnt show connections already added via gnome control-center.

Budgie version

10.8

Operating System

Ubuntu Budgie

Steps to reproduce the issue

add a wiregurad connection via gnome control center to network-manager.
open budgie-control-center. every connection is show beside wireguard connections

Actual result

atm you cant add wiregurad connections via budgie-control-center, only via gnome control center

BIG: budgie-control-center with all connections beside wireguard (@home, fritzbox)
SMALL: gnome control center with ALL connections

Expected result

to be able to integrade wiregurad seamlessly

Additional information

No response

Description

Budgie version

• Budgie Control Center v0.3.0
• community/budgie-desktop 10.5.3-2
• community/budgie-desktop-view 1.1.1-1
• community/budgie-extras 1.3.0-1
• community/budgie-screensaver 4.0-2

Operating system

EndeavoursOS Budgie

Steps to reproduce the issue

• Build & install budgie-control-center
• try to set up navigation shortcuts (hide windows, move windows etc...)
• Entry isn't displayed

Actual result

Expected result

Is this intended? It's just a space?

Corresponding line in budgie-control-center.pot:

Current budgie-control-center version

N/a

Use-cases

N/a

Proposal

Latest gnome settings have new alert sounds and have removed others e.g. dog bark

Suggest evaluate these and whether to similarly move to these revised alert sounds

References

Description

budgie-control-center fails to build with gnome-desktop 43 Alpha

Budgie version

budgie-control-center 1.0.2-2 on Debian/Ubuntu

Actual result

../panels/background/cc-background-chooser.c: In function ‘on_file_chooser_selection_changed_cb’:
../panels/background/cc-background-chooser.c:266:20: error: too few arguments to function ‘gnome_desktop_thumbnail_factory_generate_thumbnail’
  266 |           pixbuf = gnome_desktop_thumbnail_factory_generate_thumbnail (thumbnail_factory,
      |                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ../panels/background/cc-background-chooser.c:25:
/usr/include/gnome-desktop-3.0/libgnome-desktop/gnome-desktop-thumbnail.h:84:13: note: declared here
   84 | GdkPixbuf * gnome_desktop_thumbnail_factory_generate_thumbnail (GnomeDesktopThumbnailFactory *factory,
      |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Additional information

gnome-desktop 43 Alpha is available in Debian experimental

It's possible to update the code so that it builds against the old gnome-desktop API and the new one. Here's an example from cheese

gnome-control-center 42 has a rewritten Background page which uses the gnome-desktop thumbnailer API differently and therefore wasn't affected by this issue

Debian has pulled in various v42 patches in its patch series for v41.

Check/double check to see if those v42 patches are warranted for BCC - if they are we should merge.

https://salsa.debian.org/gnome-team/gnome-control-center/-/commit/f9420d5c77f11add188dca9bd018eb14eaecfc3d

We should be using g_spawn_check_wait_status() since exit_status is deprecated and misleading for when spawning processes. https://docs.gtk.org/glib/func.spawn_check_exit_status.html

This commit dropped a few days ago - https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/58add5197e

What I think this means is that gnome-remote-desktop will not be started/function any more via BCC
That will need to be confirmed.

In the GNOME 42 version of Settings, gnome-remote-desktop changes from VNC to RDP - which I think is covered by this commit https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/0ae59467fbd694d59fa367a0621de2482f169f44

Ubuntu 22.04 is going to backport the changes (with obvious libadwaita changes removed) back into its GNOME 41 version of Settings that it is going to carry.

So - we should at the very least watch out of this - backport the changes ourselves/merge from Ubuntu to ensure Sharing remains as a capability in BCC

Ubuntu has tidied their patch we we have (the older version) merged into our code-base.

Ubuntu has reworked this to operate better (apparently) - so need to have a look at his and re-merge if thought suitable

https://salsa.debian.org/gnome-team/gnome-control-center/-/commit/52dedfedd7d899350b6d0571614de1f99b51766e

Current budgie-control-center version

budgie-control-center 1.1.0-1 (AUR)

Use-cases

The default terminal is used by file managers and budgie-desktop-view

Remote desktop is changing its default build option for vnc support from true to false.

So basically most distros will no longer build with vnc support. We need to check that BCC can cope with optional vnc support

https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/111/diffs?commit_id=2d8cf8fef84b6b7bd143c0c46a23e16c7e230fad