Hi, I found the problem also mentioned here: https://www.reddit.com/r/Fedora/comments/dp8xvj/issues_with_the_kernel53x_series/ I don't know if the problem is known by the kernel upstream... Regarding Fedora updates, I always run it manually from the command line, so I just enter: dnf upgrade -x kernel*

Mystery solved.

Looks like adding under [Timer] OnBootSec=10min OnUnitActiveSec=4h Would do what I'm looking for, going to test.

@black3dynamite No change, still getting a blank connection. Just a black session.

@dafyre said in Network routing question: @dafyre said in Network routing question: DNS server is at 10.50.235.235 Configure your computer to look to 235.235 for DNS... and configure the DNS server at 235.235 to forward anything it doesn't recognize along to your Meraki? I added 235.235 as an additional DNS in the 250.254 network. I tried this yesterday but silly me forgot to "refresh" the NIC so it could grab the new settings. All is good & working.

@dafyre said in PATH Error with TimeScaleDB-Tune on Fedora 30: then why are you even using it? Capacity Planning, for example.

It is also a free trial weekend for the game on Steam, for anyone wanting to fire it up and see what they think.

I've been using Duplicati where I need a standalone backup of a thing. Web based management interface makes it super simple to manage.

Vultr got back to me last week with an email - "Hello, We apologize for the delayed response to this ticket, while we investigated this matter further. We are continuing to review our OS template and application images, and should be applying comprehensive changes across all available deploy images in the near future. Your continued patience and understanding is appreciated in the meantime. If you have any followup questions or concerns, please feel free to reach out."

@Emad-R said in KVM on Fedora 30, Error creating virtual network: @black3dynamite said in KVM on Fedora 30, Error creating virtual network: @Emad-R said in KVM on Fedora 30, Error creating virtual network: @stacksofplates said in KVM on Fedora 30, Error creating virtual network: Can you create it with virsh? Wondering if it's just a virt-manager issue since they are deprecating it. Over my dead body. I love virt-manager they kick that out and I will be kicking them out. not everyone wants web gui using resources and being inefficient with VNC protocol and opening another port. The web gui hardly use enough resources for you to even notice. I do agree, cause I have split personality but that said I still want virt-manager to be around. It is very mature and snappy. Deprecated is probably the same as how ifconfig is deprecated it will be around forever.

@matteo-nunziati said in Fedora 30 Workstation default partition scheme: @black3dynamite cool... If not official docs what else? Strange... It is the official docs. I'm just being stubborn about some screenshots that doesn't go with the current release.

Dont' use bullet/number lists in instructions and guides like this. it makes it annoying for those that want to copy and paste. This guide is assuming that you are running as root. If not prepend everything here with sudo. Install the salt-master package dnf install salt-master Open the required ports in the firewall firewall-cmd --add-port=4505-4506/tcp --permanent firewall-cmd --reload Enable the salt-master service to start on boow, and also start it now. systemctl enable --now salt-master.service

Dropped to alternate shell with Ctrl+Alt+F2. sudo dnf group remove "Cinnamon Desktop" sudo dnf group install "Cinnamon Desktop" sudo dnf group remove "Deepin Desktop" sudo dnf group install "Cinnamon Desktop" # this installed 26 packages reboot Cinnamon Desktop usable again

@Dashrender said in Fedora 30 LAMP Web Server Varnish Cache Broken After Update: @scottalanmiller said in Fedora 30 LAMP Web Server Varnish Cache Broken After Update: @Obsolesce said in Fedora 30 LAMP Web Server Varnish Cache Broken After Update: Wow so they just decide to up and change ports? And I thought Windows updates were bad... They accidentally hard coded to the default. did you report it? Unlikely.

@scottalanmiller said in Updating to Fedora 30 Gives Pix Error: Doing an upgrade from Fedora 29 to Fedora 30 and you get... Error: Problem: package pix-1.8.2-1.fc29.x86_64 requires libexiv2.so.26()(64bit), but none of the providers can be installed - exiv2-libs-0.26-12.fc29.x86_64 does not belong to a distupgrade repository - problem with installed package pix-1.8.2-1.fc29.x86_64 (try to add '--skip-broken' to skip uninstallable packages) This seems to happen with most normal workstation installs of Fedora. Easiest thing to do is simply remove Pix. sudo dnf remove pix -y Your update should work fine after that. I don't ever use it. But, yeah it is there by default.

@StuartJordan I kinda like the netplan approach (ducks for cover)

Upgraded from F29 to 30, also switched to Deepin. So far, I'm liking the Deepin desktop.