Ah ha! Glad to hear this is a firewalld issue and not something with our configuration. It must be some new change with how Docker is accessing the socket connections. I'll add myself to that GitHub issue. Thanks for taking a look at this Josh! Totally feel free to close as an upstream bug. I'll watch for firewalld updates.

In T9661#183367, @JoshStrobl wrote:

@alecbcs could you let me know what container you're using to validate this and if you have any other sort of network configuration? I tested it with the nextcloud image and it's able to use networking just fine.

@JoshStrobl apologies on the delay getting this to you. Somehow I missed the notification email from Phabricator.

• Remove license file and update appdata location

@JoshStrobl, I briefly talked with Bryan about this last week, but how would you feel if we went back to repacking the Mailspring .deb until we're able to figure out these NPM issues?

Adding @FriesischScott

Unfortunately, I can't get Mailspring v1.8.0 to build. Looks to be an issue with NPM detailed here. None of the proposed solutions on cleaning the cache have an effect. Neither does forcing graceful-fs to a higher version. Let me know if anyone has any ideas.

Working on it at the moment. Apologies on the delay, I haven't had the time until this weekend to re-setup my build environment after switching systems.

Patched to 5.5.2 and I can confirm that the tray icon is back!

Sorry for the delay everyone! I'd missed the notification for this. I'll give it a build & test tomorrow to see if we can't get the tray icon to work again.

@JoshStrobl Thanks for your work on this fix! I can confirm that the latest patch in the unstable repository fixed the issue for me. Also I did not have budgie-desktop-branding-livecd installed on my system.

@JoshStrobl I think this might have gotten lost in the stack, but the new version of Magic Wormhole in the unstable repository requires this as a runtime dependency.

@JoshStrobl thanks for the comments on removing the redundant cds. I'll remember adding the -C directory flag to the make macros in the future is a much cleaner solution.

• Replaced build step cds with make flags to look into build directory instead. Thanks Josh!

• Fixed legacy description formatting.

In D8774#141926, @Staudey wrote:

Just a note from me: This breaks try icon compatibility in e.g. Budgie. Which is why I haven't updated it yet.
Then again, Riot sneaked the same change in without me noticing, so it's probably not such a huge deal. Just a bit annyoing.

I just saw scrolling through recent patches that EbonJaeger already submitted a patch to update this a few days ago with D8749. Apologies on the duplicate patch.

@livingsilver94 I hope this helps! Starting in 9.1 you now have to compile gdb in a different directory from it's source which is a little weird in the packaging world.

I took a bit longer than normal to test out the latest build but everything looks good! D8754 should fix this request.

@adurante I just built 1.7.6. I'll test it out for a couple of hours and if all goes well, I'll submit the patch tonight.

I've been holding off on updating Mailspring to 1.7.4 because since it's release there have been a massive up-tick in in issues on Mailspring's Github page and 1.7.4 appears to break the ability to add new IMAP accounts. I'm following the issues closely however and I'll keep this thread up-to-date if there are changes and update once the issues are fixed.

Wow! I'd totally forgotten about package kit and this patch. Nice job doing some spring cleaning @JoshStrobl :)

Awesome! I'll get on this later tonight.

@JoshStrobl I'll keep an eye out for it! (Well...unless my screen freezes :P)

In T8620#165240, @DataDrake wrote:

Ah the intel resets. Yeah those are a known issue and are still present in 5.5 afaik. No fix yet.

I experienced this issue on both a Dell XPS 15 and 13 which have HDA-Intel integrated sound cards.

I just had my system lock up again. Happens maybe 1-3 times a week at irregular times. After scrubbing the journal I found these entries just before the system graphics froze. @DataDrake let me know if there's anything else you need/I can help test.

@Jacalz no worries. Keep up the good work with Brave :P

In T8548#162176, @Jacalz wrote:

I have no idea as to why you are running in to these issues (can't reproduce myself), but I would recommend doing the following:

• Remove /home/alexander/.config.
• Reinstall brave using sudo eopkg it --reinstall brave.

I have pushed a new update, see D7866, hopefully this can bring some fixes for you (chromium update might bring some necessary fixes, hard to tell).

In T2956#162092, @kyrios123 wrote:

How about this fork: https://github.com/kapitainsky/RcloneBrowser ?

Oh nice! Good find @kyrios123.

@JoshStrobl The GitHub for this project has been archived and the author mentions at the top it's no longer active/maintained. Should we still proceed with packaging this?

Might be related to this bug on Budgie's Github?

Thanks! I promise I'll figure out the sorting at some point :)

Sorted dependencies properly

Fixed git history

After updating to the latest version in the unstable repository I can confirm that I now only have one breeze-cursor option and it works in Flatpak apps. However, after updating breeze my system reverted to Adwaita (after a reboot) and I had to reinstall the breeze-cursor theme through eopkg to get it to show up in budgie desktop settings.

In D6763#106878, @Girtablulu wrote:

You did use this diff? (Because I dont have anymore two packages) It's not in unstable at the moment

@Girtablulu I can confirm that using breeze-cursor now no longer breaks flatpak apps. However, I'm still seeing two breeze cursor themes in the budgie desktop settings.

Alright, thank you for taking a look!

@JoshStrobl @Girtablulu you guys have been updating Breeze recently, maybe Flatpak expects the theme in a different location?

Fixed build to package shared library object. Thanks @aleksvor!

It looks like the Clear Linux team is no longer interested in integrating this into clr-boot-manager. If all that needed, is to mount the /boot partition before running fwupd, maybe we could consider integrating this with eopkg for the time being, and then sol later on.

Gnome thunderbolt settings appear to be functioning as expected after installing bolt from the software center.

Have you disabled thunderbolt security in your laptop's BIOS? I'd also checkout this article which references that you might need to update the dock's firmware for a more stable experience in Linux.