The small linux problem thread

Nevermind, I discovered my mistake. I needed to enable another google api. After that it works.

2 Likes

Wireshark? Or is it like a driver issue?

Not sure. I don’t even know if there is a problem with network connectivity. I guess I see an area where I’m not familiar with and an opportunity to at worst get better debugging. Consider it an exploratory mission.

Assume you have some weird upstream issues with a webserver returning 500’s, and a db server that serves as the backend. There’s no real “finger pointing” at the DB network connectivity layer, but it wouldn’t hurt to be able to verify if this is a route to check or not.

This looks like a decent beginner’s guide. Hits on the high points I would talk about:

https://www.redhat.com/sysadmin/beginners-guide-network-troubleshooting-linux

for people with cinnamon on multi monitor setups, does your windows get moved onto a single monitor if you leave your desktop on idle?

Is it from the slideshow applet?
Does Gnome shell crash and put all your windows on your primary monitor?

I ask because I was thinking of filling out a issue on github, but the linux mint guide mentioned that the devs aren’t there to troubleshoot. Also I don’t really have a fix for it, so I wanted to ask here first.
https://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/when.html

1 Like

Solved my own problem, posting here:
My “main machine” is now a VM hosted on my NAS in the garage, and there’s no real reason to mess with hibernating it, except for firefox which is loaded with tabs because I haven’t set up my intended note taking and bookmark utility. The VM on it’s own will be roughly from 0-3% activity, but with firefox it’ll be 1-6% activity.

So thankfully, firefox’s thread are all nice and in one big group (htop -t), and there’s nothing else running with “firefox” in the name.

So to suspend firefox only run:
pkill -STOP firefox

To resume it run:
pkill -CONT firefox

Note that it you resume Firefox shortly after stopping it, it’ll be functional instantly, but if you resume it after leaving it overnight, it may take a minute or two to start working again.

Way simpler than I expected. Let me know if there are any caveats for userspace programs.

2 Likes

I everyone Shadowbane here and I have another Linux problem, I hope this community can fix it. I recently installed Kubuntu 20.4.1 on a brand new SSD I purchased a few months ago, the installation of Kubuntu went exactly as planned. No problems. It wasn’t until last night when I tried to update Kubuntu, I discovered my problem. Apparently one of Ubuntu’s PPA’s failed to update or my installation can’t find it. I know I could fix the problem by removing the PPA from my machine, but I would rather fix the PPA than remove it. I have enclosed a copy of what happens when I type the command sudo apt update into the terminal.

[sudo] password for prince_charming: 
Hit:1 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu focal InRelease
Get:3 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 DEP-11 Metadata [263 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu focal-updates/universe amd64 DEP-11 Metadata [205 kB]                              
Get:7 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 DEP-11 Metadata [2,468 B]                                    
Get:8 http://us.archive.ubuntu.com/ubuntu focal-backports/universe amd64 DEP-11 Metadata [1,768 B]                                    
Get:9 http://security.ubuntu.com/ubuntu focal-security InRelease [109 kB]                                                             
Ign:10 http://ppa.launchpad.net/embrosyn/xapps/ubuntu focal InRelease    
Hit:11 http://ppa.launchpad.net/gns3/ppa/ubuntu focal InRelease                     
Err:12 http://ppa.launchpad.net/embrosyn/xapps/ubuntu focal Release                 
  404  Not Found [IP: 91.189.95.85 80]
Get:13 http://security.ubuntu.com/ubuntu focal-security/main amd64 DEP-11 Metadata [24.3 kB]
Get:14 http://security.ubuntu.com/ubuntu focal-security/universe amd64 DEP-11 Metadata [56.6 kB]
Reading package lists... Done               
E: The repository 'http://ppa.launchpad.net/embrosyn/xapps/ubuntu focal Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
prince_charming@Doc:~$ ```

You could ping the dev, and see if he will respin for the new version of Ubunutu- he last reved the packages to 19.04.

Or you could downgrade your install to 18.04 and hope the dev does 20.04 later?

Last change on launchpad was updating the packages to 19.04, done on 22 December 2019

1 Like

It’s not something that broke on your end and so nothing you can fix yourself.

When you look at the PPA, there is none for 20.04:

When you open the Technical Details for the PPA there is a version selector, those are the ones the author has published the PPA for:

image

So as Trooper says, you can ping the developer but that’s about everything you can do on that version.

1 Like

Thanks, @Trooper_ish, and @mihawk90 for the information. I will try ping the dev Since he last updated a little over a year ago, I will assume he is running a little behind in updating.

1 Like

I got an un deleteable file.

It’s a corrupt file, due to an error while copying it to my nas. Now I can’t delete it.
rm -f file results in this error: Resource temporary unavailable

What can I do to remove it? Formatting the nas isn’t really an option…

Have you double checked the file is actually there? And I presume you tried to force it as root?

Otherwise, might it be a link/pointer to a file which no longer exists? As in just the metadata of a file left on the system?

I’ve also tried with sudo, but no dice.

You might be on to something with the meta data, it was a mp4 file, but looking at it’s properties, it 0 bytes in size, and is listed as a text/plain document.

But ls still lists the file, so it’s still there. Somehow?

1 Like

I don’t suppose

lsof filename

Shows it in use with anything?

But that is more a temporary block against deleting a file in use by another process

It wasn’t in use.

But I’ve successfully deleted it by doing it from the terminal on my nas. It didn’t care, just poof :slight_smile:

I also posted my problem on another forum, which is where I was suggested doing it directly on the nas.

What were you doing before? SSH?

Nah, First with Mints file explorer, then from the command line.

1 Like

Also thanks for the help :slight_smile:

1 Like

It’s okay, we all know I’m just here for moral support, sounding board and to cheerlead

1 Like