Budgie Control Center not working after fresh install

unexceptable

Fresh install, ran all the updates, and am running into a few issues.

Trying to open Budgie Control Centre via any of the menu options, or even from the cli does not work (no errors and nothing obvious in journalctrl).

Launching gnome-control-center from the cli works though. So I guess I have a work around in the mean time.

Secondary issue: Spotify doesn't seem to want to install.
First was a hash error of some sort which when clicking close on the error locked up the sc until I killed the process from the cli, and on a second attempt/reboot it seemed to then hit a rate limit error.

brent

unexceptable Trying to open Budgie Control Centre via any of the menu options, or even from the cli does not work (no errors and nothing obvious in journalctrl).

Launching gnome-control-center from the cli works though. So I guess I have a work around in the mean time.

the devs should know about this, for sure. as long as I can remember I have just right-clicked on the desktop to get budgie desktop settings...and I can right now. I never tried any other way so let me try.
ok--went thru menu and could open them both (control center and settings).
I did not try the terminal.
So mostly cannot replicate.
first instinct (I'm wrong a lot) is broken symlink(s). sudo eopkg rdb?
sudo eopkg check might throw a few of false positives (pending fixes in transit) but may be worthwhile too
For a new install (WELCOME btw 🙂), Other opinions forthcoming so hang i there.

Can't address point #2.

Staudey

unexceptable First was a hash error of some sort which when clicking close on the error locked up the sc until I killed the process from the cli, and on a second attempt/reboot it seemed to then hit a rate limit error.

The rate limit error should be fixed by an update I coincidentally applied to the script just yesterday
When's the last time you tried it?

unexceptable Trying to open Budgie Control Centre via any of the menu options, or even from the cli does not work (no errors and nothing obvious in journalctrl).

So it just auto-closes, or does it freeze and you have to terminate it?

unexceptable

Also for context, I've been running Solus for YEARS, and this laptop (Dell XPS from 3 years ago) has had the same Solus install since I got it, and only reinstalled just now because my wifi drivers died, and nothing obvious solved it, where the USB Boot had wifi fully working, and now after the reinstall wifi still works, so progress!

Staudey The rate limit error should be fixed by an update I coincidentally applied to the script just yesterday
When's the last time you tried it?

Just tried it and got:

unpack: check file hash failed

As for the control panel

Staudey So it just auto-closes, or does it freeze and you have to terminate it?

Budgie control panel just doesn't open, at all, visually speaking. Regardless of which way I start it. The process runs and I can see it if I do ps aux | grep budgie-control-center. Even the 'sound' and other panels show up as processes if I try an open them directly.

New wrinkle: Slack doesn't work (I only just tried it, so for this install it 'never' worked).

sudo journalctl -g slack
logs show (cut down to avoid duplicate stack traces):

                                                  Stack trace of thread 7:
                                                  #0  0x00007fe83c111906 n/a (libc.so.6 + 0x95906)
                                                  #1  0x00007fe83c11421e pthread_cond_wait (libc.so.6 + 0x9821e)
                                                  #2  0x00005569ad58f266 n/a (slack + 0x5ec5266)
                                                  #3  0x00005569ad5b919a n/a (slack + 0x5eef19a)
                                                  #4  0x00005569ad5320c5 n/a (slack + 0x5e680c5)
                                                  #5  0x00005569ad4ef647 n/a (slack + 0x5e25647)
                                                  #6  0x00005569ad557521 n/a (slack + 0x5e8d521)
                                                  #7  0x00005569ad516b2e n/a (slack + 0x5e4cb2e)
                                                  #8  0x00005569ac0e1af9 n/a (slack + 0x4a17af9)
                                                  #9  0x00005569ad58fad1 n/a (slack + 0x5ec5ad1)
                                                  #10 0x00007fe83c11541e n/a (libc.so.6 + 0x9941e)
                                                  #11 0x00007fe83c18cd04 __clone (libc.so.6 + 0x110d04)
                                                  
                                                  Stack trace of thread 1:
                                                  #0  0x00007fe83c111906 n/a (libc.so.6 + 0x95906)
                                                  #1  0x00007fe83c11421e pthread_cond_wait (libc.so.6 + 0x9821e)
                                                  #2  0x00005569ad58f266 n/a (slack + 0x5ec5266)
                                                  #3  0x00005569ad5b919a n/a (slack + 0x5eef19a)
                                                  #4  0x00005569ad5320c5 n/a (slack + 0x5e680c5)
                                                  #5  0x00005569ac1e123c n/a (slack + 0x4b1723c)
                                                  #6  0x00005569b159bf04 n/a (slack + 0x9ed1f04)
                                                  #7  0x00005569b003470a n/a (slack + 0x896a70a)
                                                  #8  0x00005569b003a9ba n/a (slack + 0x89709ba)
                                                  #9  0x00005569ae9ab3e1 n/a (slack + 0x72e13e1)
                                                  #10 0x00005569ad53552f n/a (slack + 0x5e6b52f)
                                                  #11 0x00005569ad556d86 n/a (slack + 0x5e8cd86)
                                                  #12 0x00005569ad4ef60c n/a (slack + 0x5e2560c)
                                                  #13 0x00005569ad557521 n/a (slack + 0x5e8d521)
                                                  #14 0x00005569ad516b2e n/a (slack + 0x5e4cb2e)
                                                  #15 0x00005569b15ab797 n/a (slack + 0x9ee1797)
                                                  #16 0x00005569a9dec606 n/a (slack + 0x2722606)
                                                  #17 0x00005569a9ded241 n/a (slack + 0x2723241)
                                                  #18 0x00005569a9dee60a n/a (slack + 0x272460a)
                                                  #19 0x00005569a9debf29 n/a (slack + 0x2721f29)
                                                  #20 0x00005569a9dec030 n/a (slack + 0x2722030)
                                                  #21 0x00005569a9aba538 n/a (slack + 0x23f0538)
                                                  #22 0x00007fe83c0a630e n/a (libc.so.6 + 0x2a30e)
                                                  #23 0x00007fe83c0a63c9 __libc_start_main (libc.so.6 + 0x2a3c9)
                                                  #24 0x00005569a96ac02a _start (slack + 0x1fe202a)
                                                  ELF object binary architecture: AMD x86-64
Jul 26 09:58:53 excelsus slack.desktop[26539]:     at /usr/lib64/slack/resources/app.asar/dist/main.bundle.js:259:6596
Jul 26 09:58:53 excelsus slack.desktop[26539]:     at /usr/lib64/slack/resources/app.asar/dist/main.bundle.js:259:6574
Jul 26 09:58:53 excelsus slack.desktop[26539]:     at /usr/lib64/slack/resources/app.asar/dist/main.bundle.js:22:7178
Jul 26 09:58:53 excelsus slack.desktop[26539]:     at /usr/lib64/slack/resources/app.asar/dist/main.bundle.js:9:34248
Jul 26 09:58:53 excelsus slack.desktop[26539]:     at /usr/lib64/slack/resources/app.asar/dist/main.bundle.js:260:920
Jul 26 09:58:53 excelsus slack.desktop[26539]:     at dispatch (/usr/lib64/slack/resources/app.asar/dist/main.bundle.js:4:57034)
Jul 26 09:58:53 excelsus slack.desktop[26539]:     at Object.next (/usr/lib64/slack/resources/app.asar/dist/main.bundle.js:308:90421)
Jul 26 09:58:53 excelsus slack.desktop[26539]:     at /usr/lib64/slack/resources/app.asar/dist/main.bundle.js:259:6596
Jul 26 09:58:53 excelsus slack.desktop[26539]:     at /usr/lib64/slack/resources/app.asar/dist/main.bundle.js:259:6574
Jul 26 09:58:53 excelsus slack.desktop[26539]:     at /usr/lib64/slack/resources/app.asar/dist/main.bundle.js:22:7178
Jul 26 09:58:53 excelsus slack.desktop[26539]:     at /usr/lib64/slack/resources/app.asar/dist/main.bundle.js:9:34248
Jul 26 09:58:53 excelsus slack.desktop[26539]:     at /usr/lib64/slack/resources/app.asar/dist/main.bundle.js:260:920
Jul 26 09:58:53 excelsus slack.desktop[26539]:     at dispatch (/usr/lib64/slack/resources/app.asar/dist/main.bundle.js:4:57034)
Jul 26 09:58:53 excelsus slack.desktop[26539]:     at Object.next (/usr/lib64/slack/resources/app.asar/dist/main.bundle.js:308:90421)

Staudey

unexceptable Just tried it and got:
unpack: check file hash failed

Hmm, can't reproduce that. Perhaps it (for some reason) cached an incomplete download? Try a sudo eopkg dc and then doing it again.

unexceptable

Maybe a more relevant error from slack:

Jul 26 13:17:45 excelsus slack.desktop[47857]: [47857:0726/131745.160894:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /StatusNotifierWatcher: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jul 26 13:17:45 excelsus slack.desktop[47857]: [47857:0726/131745.165915:ERROR:browser_main_loop.cc(278)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed

unexceptable

Welp, installing Nvdia drivers fixed the control center not opening, and Slack too!

Spotify is still not installing though, but hey, progress 😛

murbert

unexceptable
I'm not sure of the term, but if you go to Spotify in a Chrome based browser, you get the option to install Spotify from there, it takes 3 seconds.

pomon

Try:

sudo eopkg bi --ignore-safety https://raw.githubusercontent.com/getsolus/3rd-party/master/multimedia/music/spotify/pspec.xml
sudo eopkg it spotify*.eopkg;sudo rm spotify*.eopkg

It also comes as a flatpak.

killall budgie-control-center.
Install gdb if you don't have it.
gdb budgie-control-center.
After the sign (gdb) enter r after bt. Look for errors.

AlphaElwedritsch

murbert should be an PWA in this case

unexceptable

I'm marking this as solved mostly for the Control Center and Slack issues, where installing nvidia drivers fixed those for me.

I can't get spotify to work. sudo eopkg dc didn't help, and trying to build it directly also produced the same error:

adrian@excelsus ~ $ sudo eopkg bi --ignore-safety https://raw.githubusercontent.com/getsolus/3rd-party/master/multimedia/music/spotify/pspec.xml
pspec.xml                      (22.0 KB)100%      0.00 --/- [--:--:--] [complete]
actions.py                     (490.0  B)100%      0.00 --/- [--:--:--] [complete]
DEBUG: InstallDB initialized in 0.0427479743958.
DEBUG: RepoDB initialized in 3.60012054443e-05.
Building source package: spotify
component.xml                  (48.0  B)100%      0.00 --/- [--:--:--] [complete]
Fetching source from: http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.2.42.290.g242057a2_amd64.deb
spotify-client_1.2.42.290.g242057a2_amd64.deb (140.9 MB) 69%      9.13 MB/s [00:00:05]Source archive is stored: /var/cache/eopkg/archives/spotify-client_1.2.42.290.g242057a2_amd64.deb
Unpacking archive(s)...
Program terminated.
unpack: check_file_hash failed
Please use 'eopkg help' for general help.

Staudey

unexceptable Interesting. It seems to fail in the same way the Python3 version of eopkg fails for me. That is, it doesn't retry an incomplete download and instead simply continues with the partial file.

I honestly don't know what to do about this in that case. In fact I specifically changed the Spotify download URL to the http:// version because the https:// URL often/always breaks the connection at some point, requiring a retry. But if that also happens to you with the http:// URL then I don't even have a workaround.