18.04 is quite old and partially out of support, maybe upgrade to
22.04 and then try again.
On 8/31/22 14:50, Marco Moock wrote:difference and nothing in the trash.
18.04 is quite old and partially out of support, maybe upgrade to
22.04 and then try again.
Interesting, was going to try going with 20 first but says not enough space on /. Not sure what's taking that up. Does / signify places like the desktop too as I have a lot of stuff on the desktop? I tried the apt clean as suggested but no
Interesting, was going to try going with 20 first but says not enough
space on /. Not sure what's taking that up. Does / signify places
like the desktop too as I have a lot of stuff on the desktop? I
tried the apt clean as suggested but no difference and nothing in the
trash.
Am Mittwoch, 31. August 2022, um 15:32:09 Uhr schrieb wAYNE:
Interesting, was going to try going with 20 first but says not enough
space on /. Not sure what's taking that up. Does / signify places
like the desktop too as I have a lot of stuff on the desktop? I
tried the apt clean as suggested but no difference and nothing in the
trash.
Use df and du -h to find the big folders.
You need ~10 GB free on partition that provides /.
I recommend backup of everything now it's easier to do.
Try LTS Ubuntu like 22 clean install afterwards.
Upgrade path would have to much bloating and uncertainty.
Although upgrade would be possible it's likely an uncertain system.
Since you use appimage the snap can be scheduled once a week e.g.
Don't mix flatpack with snaps, flatpack turns your Ubuntu into a
hybrid Fedora system .
Although flatpack is very fast.
Snaps are bizarre slow, I don't understand why.
Ok, I looked at that, and also looked with gparted, but didn't help
much. As an experiment, I transferred over 10 GB of data from the
desktop to a spare hard drive and didn't make any difference, so I
assume the desktop data didn't matter. Maybe try the same thing with
home next, not sure.
In the past, I always had to delete previous kernals and it would
solve this issue. I had a lot of kernals this time as well that I
deleted, but didn't help.
On 9/1/22 02:44, Marco Moock wrote:From my undertanding, because Appimages are constructed to contain all and any libraries they might need, the disk
Am Mittwoch, 31. August 2022, um 15:32:09 Uhr schrieb wAYNE:
Interesting, was going to try going with 20 first but says not enough
space on /. Not sure what's taking that up. Does / signify places
like the desktop too as I have a lot of stuff on the desktop? I
tried the apt clean as suggested but no difference and nothing in the
trash.
Use df and du -h to find the big folders.
You need ~10 GB free on partition that provides /.
Ok, I looked at that, and also looked with gparted, but didn't help much. As an experiment, I transferred over 10 GB of
data from the desktop to a spare hard drive and didn't make any difference, so I assume the desktop data didn't matter.
Maybe try the same thing with home next, not sure.
In the past, I always had to delete previous kernals and it would solve this issue. I had a lot of kernals this time as
well that I deleted, but didn't help.
On 8/31/22 16:34, Paul wrote:difference and nothing in the trash.
On 8/31/2022 3:32 PM, wAYNE wrote:
On 8/31/22 14:50, Marco Moock wrote:
18.04 is quite old and partially out of support, maybe upgrade to
22.04 and then try again.
Interesting, was going to try going with 20 first but says not enough space on /. Not sure what's taking that up. Does / signify places like the desktop too as I have a lot of stuff on the desktop? I tried the apt clean as suggested but no
upgrade because there isn't enough space. The one right next to it is the home partition. I tried shrinking that, allowing free space, but then I was unable to resize the 19 GB partition any larger.
I use "df" command for a quick review. "df" is Disk Free.
The "gnome-disks", for mounted volumes, graphically shows how
full mounted partitions are, when you click on the partition
in the GUI.
You can expand the partition... if there is room to the right.
You can use gparted, with a LiveDVD as the booted OS, to
do some disk editing.
A typical giant waste of space, is if you are a QEMU
user and wave around one or two QCOWs for fun :-) Since
the QCOW files are hidden in a root-owned location, you
have to run your disk-listing programs as root.
Analysis of disk contents (the slash partition) can
be done with one of the dirstat programs, like kdirstat
or qdirstat. sudo qdirstat / is an example of a command
for this job.
While this picture is not an entire recipe, I can tell
you that when I used gparted to resize and move around
the materials for this, it took the whole damned day
to do it :-) The partition started at maybe 35GB, but
ended up a lot larger.
[Picture]
https://i.postimg.cc/SKZ39NRp/make-space-with-gparted.gif
Paul
This is a dual boot system. Win 10 or Ubuntu selected at start up. I did reboot with the Live CD and took a look at the partitions with gparted. I believe the partition in question is a 19 GB one with 17 GB being used, which is why I can't
Initially, I had a lot of kernals from prior updates and went in and deleted those except one prior kernal just in case things go wrong with the current kernal. However, while in the past this always freed up enough space, it didn't work this time.place. I think some sort of update did it, so most likely would repeat itself once again at some point.
Seems like a lot of extra work just trying to get these Appimages to work again! Is there no other solution? I tried downloading some Appimage updates and got the same error message when clicked on.
Someone else suggested reinstalling the latest Ubuntu version from scratch. With a dual boot system, this won't be easy and not desired at this point.
As a last resort, I do have a back up of my current system from a month ago before the Appimages would no longer work. That would be the easiest way to get them going again, but still doesn't solve the issue of why they stopped working in the first
On 8/31/22 17:05, Sativa GNutella wrote:
I recommend backup of everything now it's easier to do.
My last back up was from a month ago, so pretty good there.
I'll take a look at it again once my back up from a month ago is
finished. First step will be to determine, after I again update Ubuntu
once again, whether or not the appimages are still working. Then, I
might consider the upgrade and test it out once I have made a current
back up once again.
I had some problems in that there was I believe a small partition in
between, so I couldn't expand the partition in question. And I couldn't delete the partition. It's used while Ubuntu is in operation, I'll be
darned if I can think of the name now.... serves the same purpose as a "scratch" drive for certain programs.
On Thu, 1 Sep 2022 11:37:37 -0400, wAYNE wrote:
I'll take a look at it again once my back up from a month ago is
finished. First step will be to determine, after I again update Ubuntu
once again, whether or not the appimages are still working. Then, I
might consider the upgrade and test it out once I have made a current
back up once again.
I had some problems in that there was I believe a small partition in
between, so I couldn't expand the partition in question. And I couldn't
delete the partition. It's used while Ubuntu is in operation, I'll be
darned if I can think of the name now.... serves the same purpose as a
"scratch" drive for certain programs.
Yep, moving stuff around while in use is a good way to create problems.
For partition work, I use gparted from a systemrescue cd or live cd
That way you can dismount a partition on the target system.
See http://www.sysresccd.org/Download for latest release.
On 9/1/22 17:37, wAYNE wrote:difference and nothing in the trash.
On 9/1/22 10:49, Paul wrote:
On 9/1/2022 9:46 AM, wAYNE wrote:
On 8/31/22 16:34, Paul wrote:
On 8/31/2022 3:32 PM, wAYNE wrote:
On 8/31/22 14:50, Marco Moock wrote:
18.04 is quite old and partially out of support, maybe upgrade to >>>>>>> 22.04 and then try again.
Interesting, was going to try going with 20 first but says not enough space on /. Not sure what's taking that up. Does / signify places like the desktop too as I have a lot of stuff on the desktop? I tried the apt clean as suggested but no
upgrade because there isn't enough space. The one right next to it is the home partition. I tried shrinking that, allowing free space, but then I was unable to resize the 19 GB partition any larger.
I use "df" command for a quick review. "df" is Disk Free.
The "gnome-disks", for mounted volumes, graphically shows how
full mounted partitions are, when you click on the partition
in the GUI.
You can expand the partition... if there is room to the right.
You can use gparted, with a LiveDVD as the booted OS, to
do some disk editing.
A typical giant waste of space, is if you are a QEMU
user and wave around one or two QCOWs for fun :-) Since
the QCOW files are hidden in a root-owned location, you
have to run your disk-listing programs as root.
Analysis of disk contents (the slash partition) can
be done with one of the dirstat programs, like kdirstat
or qdirstat. sudo qdirstat / is an example of a command
for this job.
While this picture is not an entire recipe, I can tell
you that when I used gparted to resize and move around
the materials for this, it took the whole damned day
to do it :-) The partition started at maybe 35GB, but
ended up a lot larger.
[Picture]
https://i.postimg.cc/SKZ39NRp/make-space-with-gparted.gif
Paul
This is a dual boot system. Win 10 or Ubuntu selected at start up. I did reboot with the Live CD and took a look at the partitions with gparted. I believe the partition in question is a 19 GB one with 17 GB being used, which is why I can't
first place. I think some sort of update did it, so most likely would repeat itself once again at some point.
Initially, I had a lot of kernals from prior updates and went in and deleted those except one prior kernal just in case things go wrong with the current kernal. However, while in the past this always freed up enough space, it didn't work this time.
Seems like a lot of extra work just trying to get these Appimages to work again! Is there no other solution? I tried downloading some Appimage updates and got the same error message when clicked on.
Someone else suggested reinstalling the latest Ubuntu version from scratch. With a dual boot system, this won't be easy and not desired at this point.
As a last resort, I do have a back up of my current system from a month ago before the Appimages would no longer work. That would be the easiest way to get them going again, but still doesn't solve the issue of why they stopped working in the
I might ask?
When you shrank /home, you were supposed to move that to the right.
+-----+----------+---------------------+
| MBR | Full | Donor | Shrink the Donor
+-----+----------+---------------------+
+-----+----------+-----------+---------+
| MBR | Full | Donor |<unalloc>| Now, move Donor to the right
+-----+----------+-----------+---------+
+-----+----------+---------+-----------+
| MBR | Full |<unalloc>| Donor | Expand the Full partition, into space
+-----+----------+---------+-----------+
+-----+--------------------+-----------+
| MBR | Full | Donor | Do Upgrade
+-----+--------------------+-----------+
Paul
Ok, so resized and moved and now 20.04 is attempting to install. However, it has been sitting at "refreshing snap core18" for a long time now with no progress being made. Don't know if that's normal or not. What happens if it doesn't go beyond this
Well, after it stayed stuck there for about 2 hours, I decided to try shutting down and rebooting. Instead of shutting down, I was logged out. I logged back in and then selected software update. Was informed that a partial upgrade had beencompleted and asked for permission to finish. Appears to be all done now. I hope everything is ok. That was a strange way of doing things. At least all my appimages are working again. I think this had something to do with snap. After the log
It's good to hear you made "forward progress" without more
of my bumbling :-)
On 9/1/22 22:32, Paul wrote:
It's good to hear you made "forward progress" without more
of my bumbling :-)
-------apologetic cut--------------------------------
Thanks for further info. A lot of that is too technical for me, but it
was an interesting read. Obviously you are far more into the
programming and command side of things than I am.
I switched over to Ubuntu probably a decade ago after growing tired of Windows by constantly having to have viral scanners and such, plus I
found that Windows would get less and less functional the more it was
updated unless one bought a new PC. Plus, many of the virus programs I
used tended to slow things down too much.
I had examined several Linux options (distros I believe is the correct
term if I'm not mistaken) and settled on Ubuntu. I tried several of
them on virtual machines first. I sort of liked Debian, but found that
it was far too basic. There were others close in functionality and user friendliness to Ubuntu, but finally settled on Ubuntu.
I hadn't realized that a degree of Linux programming knowledge was
actually needed after the switchover, unlike Win where everything is
plug and play. At first I scoffed at this, but didn't take me long to realize the advantages of it. So I tried to learn what I could at a
very basic level. What I can't figure things out, as is often the case,
I found several user friendly Linux based groups like this one, all of
which have helped tremendously when I have encountered hitches.
For example, a friend of mine came onto this group a couple of years
back. He liked to listen to what is called online SDRs. These are software defined radios (SDR) that are accessible to anyone who has
online access. I'm not really all that interested in it, but he wanted
to be able to record many of these stations simultaneously as he was
looking for some very specific radio signals. He was trying to use
python and scripts to set up recording times, number of stations and
such and had no idea how to proceed. He posted an inquiry here and one
kind gentleman spent days communicating with him on here and helping him
to set up the necessary scripts. He learned enough from his man that he
has been able to write up workable scripts ever since. Kudos to whoever that was, but my friend still talks about the kind encounter here and
how it really helped him along.
Talking about rambling, look at me, ha ha. Well, I am in the process of backing up my system, which was finally how I wanted it after the
upgrade yesterday. I did one hitch to solve and that's when I
inadvertently chose Firefox to "refresh" itself after it asked me to
after the upgrade. When I did that, I lost all of my ad ons but
reinstalled and all solved now. After the back up today, guess what,
I'm going to try installing v22! Now I do understand that there may be issues with the appimages, but there seems to be plenty of online info
on how to solve it so keeping my fingers crossed.
Thanks to you and the others who helped here. I really liked the
diagram you made about how to shrink, move and expand the needed
partition. I will probably have to do the same with the laptop here
once the desktop is done. This laptop all has v18 but needs upgraded as well. When things start not working on v18, which was obviously the
case with snap and the appimages, it's past time to update.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 89:35:19 |
Calls: | 6,697 |
Calls today: | 2 |
Files: | 12,232 |
Messages: | 5,348,420 |