@mikeslr
For google-chrome I use the "update" Fatdog 721 generates. FD
conveniently places the latest version of chrome in its root folder
for export. Works for me on tahrpup64, xenialpup64, Slacko64 6.9.9.9 and now on Bionicpup64.
Art
Bionicpup64 8.0 CE
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
@ artsown:-artsown wrote:@mikeslr
For google-chrome I use the "update" Fatdog 721 generates. FD
conveniently places the latest version of chrome in its root folder
for export. Works for me on tahrpup64, xenialpup64, Slacko64 6.9.9.9 and now on Bionicpup64.
Art
Any chance of a few more details on this one, please, mate?
Mikeslr alerted me to the 'crashing' of my Chrome SFS packages earlier on by PM. He tells me this is something to do with FatDog placing the Chrome folder actually in '/', rather than in ~/spot?
Is Chrome, then, running as a 'normal user' (Google's words, not mine!).....or as /root.....or something else? (Obviously, I would guess it's not running as root, since it's not then going to be in the /root folder...)
I've tried FatDog in the past, but I just don't like the way jamesbond and Kirk do things. I've tried getting my head round the way it works, but for me it's just too different. They're very clever guys, don't get me wrong - I have a lot of respect for them! - but it's just not my cup of tea, I'm afraid.
Some links and/or 'pointers' would be of enormous help. If I've got to re-build the packages a different way, the sooner I know about it, the better.....
Cheers.
Mike.
Hi Mike Walsh
Fatdog generates chrome installation file as a .txz which installs to /opt
and runs as spot.
Hop on over to distro.ibiblio/fatdog/iso/ and scroll down to
Fatdog64-721.iso
In fatdog, aim at control panel - Update - Get Google Chrome
You'll find explanations and info as you proceed. Fatdog first downloads
chrome and installs it, As I mentioned, the .txz file it creates is placed in
/root
Hope that helps.
Art
Fatdog generates chrome installation file as a .txz which installs to /opt
and runs as spot.
Hop on over to distro.ibiblio/fatdog/iso/ and scroll down to
Fatdog64-721.iso
In fatdog, aim at control panel - Update - Get Google Chrome
You'll find explanations and info as you proceed. Fatdog first downloads
chrome and installs it, As I mentioned, the .txz file it creates is placed in
/root
Hope that helps.
Art
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Just performed a manual frugal to a sub-directory on one of my large 'testing' partitions. Manually added entry to Grub4DOS, created save-file. Apparently save-file was created, but I ran into the same problem as watchdog.....in fact, the exact same 'bug trace', too.
Apart from that small 'glitch'.....all looking very good. Thanks, Phil!
More to follow, I have no doubt.....
Mike.
Apart from that small 'glitch'.....all looking very good. Thanks, Phil!
More to follow, I have no doubt.....
Mike.
It's working well here,artsown wrote: In fatdog, aim at control panel - Update - Get Google Chrome
You'll find explanations and info as you proceed. Fatdog first downloads
chrome and installs it, As I mentioned, the .txz file it creates is placed in
/root
Hope that helps.
Art
Thanks for the tip.
Bill
- Attachments
-
- googlechrome.jpg
- (9.28 KiB) Downloaded 2542 times
In Fatdog you can right mouse click the .txz file and Convert to SFS - but that would be a Fatdog specific sfs ('might' work in other Pup's - but ???).
When I boot liveCD Fatdog, I just burn the .txz to the DVD and 'install' it after each reboot rather than having it as a sfs and loading it. Not much different in the 'load' times, and makes no difference as I don't save any sessions (other than the occassional config changes when I reboot and without loading anything else just make the changes and save a new multi-session savefile). When a new version of Chrome comes out, just boot, run the install google process that creates a new .txz and burn that to the DVD (and don't save the session, so the DVD content is as before but just with the additional chrome tgz file stored on it). I believe (haven't tried it myself), if you save files with the same name to DVD then it shows/loads/installs the one with the latest file date i.e. you could just save (burn) with the same chrome.txz filename each time). Personally I use distinct filenames that include the version/date.
Tend to agree with Mike, the Fatdog crew are very bright, but things are set up 'unconventionally'. OpenBSD is great for consitency and hence simplicity. Linux in general tends to have things all over the place, but you do get a feel for where things might be after a while (systemD has thrown a spanner into that however). Fatdog is different again, but in a consistent way such that it can be good once you're familiar with the layout, but involves yet another learning curve. The code is very well written and laid out and based on linux from scratch. As a whole it works incredibly well. A negative for me however is a concern about updates and in particular security updates. A large support Team such as Debian's is obviously better on that front - one of the advantages/benefits of having 1000+ helping out.
When I boot liveCD Fatdog, I just burn the .txz to the DVD and 'install' it after each reboot rather than having it as a sfs and loading it. Not much different in the 'load' times, and makes no difference as I don't save any sessions (other than the occassional config changes when I reboot and without loading anything else just make the changes and save a new multi-session savefile). When a new version of Chrome comes out, just boot, run the install google process that creates a new .txz and burn that to the DVD (and don't save the session, so the DVD content is as before but just with the additional chrome tgz file stored on it). I believe (haven't tried it myself), if you save files with the same name to DVD then it shows/loads/installs the one with the latest file date i.e. you could just save (burn) with the same chrome.txz filename each time). Personally I use distinct filenames that include the version/date.
Tend to agree with Mike, the Fatdog crew are very bright, but things are set up 'unconventionally'. OpenBSD is great for consitency and hence simplicity. Linux in general tends to have things all over the place, but you do get a feel for where things might be after a while (systemD has thrown a spanner into that however). Fatdog is different again, but in a consistent way such that it can be good once you're familiar with the layout, but involves yet another learning curve. The code is very well written and laid out and based on linux from scratch. As a whole it works incredibly well. A negative for me however is a concern about updates and in particular security updates. A large support Team such as Debian's is obviously better on that front - one of the advantages/benefits of having 1000+ helping out.
[size=75]( ͡° ͜ʖ ͡°) :wq[/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Huh. Spoke too soon.....
After having said about having the same initial problem as watchdog, three more shut-down/re-boot attempts have resulted in the necessity for a 'hard power-off'. It WILL NOT shut-down cleanly.....not for me, anyway.
Can't use it like this.
Watchdog and I are the only ones who've so far reported this. It's clearly a kernel issue, from the 'bug trace'. I also know that watchdog and I both run pretty elderly hardware'; maybe this is something that early 64-bit CPUs are going to have problems with. No-one else has reported it, anyway.....at least, not yet.
If you feel you do need to re-compile the kernel, or use a different release, I'll try it again in a few weeks time. Until then, it's a 'no-go' area for me. Repeated 'hard power-downs' are not a good idea for 13-yr old hardware.
Sorry, Phil. It's early days yet, though; we can fix most issues when we set our minds to it. We've a good crew here on the Forum!
Mike.
After having said about having the same initial problem as watchdog, three more shut-down/re-boot attempts have resulted in the necessity for a 'hard power-off'. It WILL NOT shut-down cleanly.....not for me, anyway.
Can't use it like this.
Watchdog and I are the only ones who've so far reported this. It's clearly a kernel issue, from the 'bug trace'. I also know that watchdog and I both run pretty elderly hardware'; maybe this is something that early 64-bit CPUs are going to have problems with. No-one else has reported it, anyway.....at least, not yet.
If you feel you do need to re-compile the kernel, or use a different release, I'll try it again in a few weeks time. Until then, it's a 'no-go' area for me. Repeated 'hard power-downs' are not a good idea for 13-yr old hardware.
Sorry, Phil. It's early days yet, though; we can fix most issues when we set our minds to it. We've a good crew here on the Forum!
Mike.
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Upon mulling it over (and bearing in mind bigpup's pleas to only test what's there!), I'm going to try a kernel swap with Xenial64's 4.9 kernel. If I'm going to run Bionic64, I'll need to try something.
An elderly machine like this doesn't need a bang up-to-date kernel; we all know that newer versions concentrate mainly on newer device driver support. Everything I run is supported by Racy's 3.0.66 kernel, after all.....and Xenial's 4.9 gives me no issues.
So; I'll report back as to whether this fixes the issue for me. I've a feeling it will.
Mike.
An elderly machine like this doesn't need a bang up-to-date kernel; we all know that newer versions concentrate mainly on newer device driver support. Everything I run is supported by Racy's 3.0.66 kernel, after all.....and Xenial's 4.9 gives me no issues.
So; I'll report back as to whether this fixes the issue for me. I've a feeling it will.
Mike.
About google-chrome
Hi All,
From time to time I do a frugal install of a FatDog64. More often I'll just read posts to its thread, especially when they turn up while I'm trying to figure out some way to get Puppies to function the way I prefer. I prefer to perform Saves as little as possible, and to provide Google with a little information as possible. Having to run Google-Chrome & Clones as Spot under Puppies presents a "Hobson's Choice": sync my bookmarks to Google's computers, or since Spot is in /root and changes to /root are lost if not Saved, additions to/deletions of google-chrome bookmarks in /root/spot/ have to be Saved.
Searching for an alternative --in particular a way to have the Spot folder at /mnt/home-- I ran across "FatDog's" post that " Spot's home directory has been moved from /root/spot to /home/spot. This has repercussions. Please read the details here." http://www.murga-linux.com/puppy/viewto ... 770#975770 Examination of that FatDog's structure revealed a new folder "Home" did not 'hang' from /root, but was at the same upper level as /bin, lib, /opt /usr and /root. My recollection was that the location from which those first level folders "hang" is symbolized as ~ , but confusingly also referred to as "root" but meaning the Top of the operating system. [Sorry, Mike. I didn't remember that Spot was a folder in /home].
At any rate, the way Mike's Google-Chrome.sfs is supposed to work is that when first loaded files an icon is written to /usr/share/pixmaps; a desktop file written to /usr/share/applications; that the Exec argument of the desktop file is "Exec=/root/spot/chrome.sh" and that such chrome.sh file and all other files relating to Google-Chrome are written to /root/spot. Well, as I discovered after my post, under Bionic64, when Google-Chrome.sfs is loaded, a Menu listing is created, but nothing gets written to /root/spot.
Query: Are the permissions in /Bionic64/root/spot different from those in /Xenialpup64/root/spot? Does "root" no longer have authority to write to /root/spot? Is the bash version different? What else might cause that behavior?
mikesLr
From time to time I do a frugal install of a FatDog64. More often I'll just read posts to its thread, especially when they turn up while I'm trying to figure out some way to get Puppies to function the way I prefer. I prefer to perform Saves as little as possible, and to provide Google with a little information as possible. Having to run Google-Chrome & Clones as Spot under Puppies presents a "Hobson's Choice": sync my bookmarks to Google's computers, or since Spot is in /root and changes to /root are lost if not Saved, additions to/deletions of google-chrome bookmarks in /root/spot/ have to be Saved.
Searching for an alternative --in particular a way to have the Spot folder at /mnt/home-- I ran across "FatDog's" post that " Spot's home directory has been moved from /root/spot to /home/spot. This has repercussions. Please read the details here." http://www.murga-linux.com/puppy/viewto ... 770#975770 Examination of that FatDog's structure revealed a new folder "Home" did not 'hang' from /root, but was at the same upper level as /bin, lib, /opt /usr and /root. My recollection was that the location from which those first level folders "hang" is symbolized as ~ , but confusingly also referred to as "root" but meaning the Top of the operating system. [Sorry, Mike. I didn't remember that Spot was a folder in /home].
At any rate, the way Mike's Google-Chrome.sfs is supposed to work is that when first loaded files an icon is written to /usr/share/pixmaps; a desktop file written to /usr/share/applications; that the Exec argument of the desktop file is "Exec=/root/spot/chrome.sh" and that such chrome.sh file and all other files relating to Google-Chrome are written to /root/spot. Well, as I discovered after my post, under Bionic64, when Google-Chrome.sfs is loaded, a Menu listing is created, but nothing gets written to /root/spot.
Query: Are the permissions in /Bionic64/root/spot different from those in /Xenialpup64/root/spot? Does "root" no longer have authority to write to /root/spot? Is the bash version different? What else might cause that behavior?
mikesLr
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Yay! Sorted.
Renamed a copy of Xenial's 'zdrv_xenialpup_7.5.sfs' to 'zdrv_bionicpup_7.9.3.sfs'. Swapped 'em over, along with the vmlinuz.....result!
Bionicpup64 7.9.3 now shuts down/re-boots cleanly, using the 4.9.58 kernel. So it does look like a kernel issue, I'm afraid, Phil.
At least I can now get on with some testing; I couldn't have carried on like that with the newer kernel. This wasn't a kernel swap for the sake of it; it was a necessary kernel swap, with a known 'good' kernel, to fix an obviously kernel-related issue.
And it worked.
Now I can concentrate on more important issues.....like what I'm going to do about Chrome. Again.
(*sigh*)
Mike.
Renamed a copy of Xenial's 'zdrv_xenialpup_7.5.sfs' to 'zdrv_bionicpup_7.9.3.sfs'. Swapped 'em over, along with the vmlinuz.....result!
Bionicpup64 7.9.3 now shuts down/re-boots cleanly, using the 4.9.58 kernel. So it does look like a kernel issue, I'm afraid, Phil.
At least I can now get on with some testing; I couldn't have carried on like that with the newer kernel. This wasn't a kernel swap for the sake of it; it was a necessary kernel swap, with a known 'good' kernel, to fix an obviously kernel-related issue.
And it worked.
Now I can concentrate on more important issues.....like what I'm going to do about Chrome. Again.
(*sigh*)
Mike.
Although I agree with bigpup that it is important to test the applications a dev has built into an operating system, I disagree that that should be the only concern when examining a new system. Especially not when that system has been created by an experienced craftsman like 666philb using a tool like Woof which has been around for five years (albeit often being 'upgraded').
I would expect that any errors in such system would be those oversights and scribner's errors we are all heir to: quickly discovered and easily rectified.
My concern is with extensibility. I'm neither going to use nor recommend an operating system --no matter how good it is-- if it is only able to run the applications for bare-bones computing: the dev's choice of browser and a simple word-processor.
So I am please to note that among the 'builtins' are those Qt-libs required by master-pdf-editor and Foxitreader. Adding qt-libs was a stumbling block for many in prior Puppies.
If Bionicpup64 is unable to run Google-chrome or is unable to manage any level of video editing --or audio editing or other major undertaking a user might want-- than it suffers significant flaws compared to other Linux operating systems. And it is best to know this at the outset so that they can be addressed, a process which might undo or obviate the need to correct minor flaws in the current build.
So far, I have not found an easy solution to video editing. The latest Avidemux-xp-portable, 2.7.1, which runs under Wine in other Puppies, doesn't. I took a stab at building Openshot 2.4.1. Using PPM I "Download and All dependencies" --including frei0r and plugins-- 123 debs in all, and used PaDS to create both an SFS and a Pet. Neither functioned. And, unfortunately, 2.4.1 requires both qt and python. Python provides the 'executable' and as I don't know python, at all, I haven't the foggiest what went wrong.
[Sidenote: I think rockedge somewhere provided instructions on how AppImages can be unpacked and edited or then otherwise used. I could find no instructions, anywhere, for modifying flatpaks or snap-packages].
mikesLr
I would expect that any errors in such system would be those oversights and scribner's errors we are all heir to: quickly discovered and easily rectified.
My concern is with extensibility. I'm neither going to use nor recommend an operating system --no matter how good it is-- if it is only able to run the applications for bare-bones computing: the dev's choice of browser and a simple word-processor.
So I am please to note that among the 'builtins' are those Qt-libs required by master-pdf-editor and Foxitreader. Adding qt-libs was a stumbling block for many in prior Puppies.
If Bionicpup64 is unable to run Google-chrome or is unable to manage any level of video editing --or audio editing or other major undertaking a user might want-- than it suffers significant flaws compared to other Linux operating systems. And it is best to know this at the outset so that they can be addressed, a process which might undo or obviate the need to correct minor flaws in the current build.
So far, I have not found an easy solution to video editing. The latest Avidemux-xp-portable, 2.7.1, which runs under Wine in other Puppies, doesn't. I took a stab at building Openshot 2.4.1. Using PPM I "Download and All dependencies" --including frei0r and plugins-- 123 debs in all, and used PaDS to create both an SFS and a Pet. Neither functioned. And, unfortunately, 2.4.1 requires both qt and python. Python provides the 'executable' and as I don't know python, at all, I haven't the foggiest what went wrong.
[Sidenote: I think rockedge somewhere provided instructions on how AppImages can be unpacked and edited or then otherwise used. I could find no instructions, anywhere, for modifying flatpaks or snap-packages].
mikesLr
I did a manual frugal install with this in the menu.1st.
Used Remove Builtin Applications to remove Palemoon. The files seem to be gone but folders are still there. I will try to remaster later to see if it is really gone.
Apulse was already installed. Created .desktop file using apulse to access my pre-existing (use it with Debian Dog) portable latest Firefox. Works with my prexisting profile and sound works!!!!! Tested and Netflix works. Posting from it now.
Everything (sound internet mesa etc) worked on first boot.
I like the back to basics Puppy Desktop.
Only editorial comment is you might pick a more newbie friendly default terminal like lxterminal or roxterm.
Great start.
Dan
edit: I went ahead on removed Abiword, Gnumeric, and Transmission (in addition to Palemoon which I removed earlier) using Remove Builtin Packages.
Then I remastered. When I look in the PPM, it says that Palemoon, Abiword, Gnumeric and Transmission are already installed, even though I removed them with Remove Builtin Packages. I guess that is a bug???
Under /opt, Palemoon files seem to be gone, but folders are still there. Also, searching with pfinder, icon files and a script in /usr/bin are still there.
Size of ISO went down to 340 meg.
Portable firefox run with apulse.desktop file pointing to /mnt/home still works on remastered copy.
edit again: Some of the basic right-click actions in rox filer seem broken. I downloaded the Universal File Viewer and when I right clicked and chose rename or permissions or properties, nothing happened.
Created save folder, set pup event to save=0, ask on exit. That seems to work correctly.title Puppy Linux BionicPuppy in sda2 dir BionicPuppy
rootnoverify (hd0,1)
kernel /BionicPuppy/vmlinuz pmedia=ataflash psubdir=BionicPuppy
initrd /BionicPuppy/initrd.gz
Used Remove Builtin Applications to remove Palemoon. The files seem to be gone but folders are still there. I will try to remaster later to see if it is really gone.
Apulse was already installed. Created .desktop file using apulse to access my pre-existing (use it with Debian Dog) portable latest Firefox. Works with my prexisting profile and sound works!!!!! Tested and Netflix works. Posting from it now.
Everything (sound internet mesa etc) worked on first boot.
I like the back to basics Puppy Desktop.
Only editorial comment is you might pick a more newbie friendly default terminal like lxterminal or roxterm.
Great start.
Dan
edit: I went ahead on removed Abiword, Gnumeric, and Transmission (in addition to Palemoon which I removed earlier) using Remove Builtin Packages.
Then I remastered. When I look in the PPM, it says that Palemoon, Abiword, Gnumeric and Transmission are already installed, even though I removed them with Remove Builtin Packages. I guess that is a bug???
Under /opt, Palemoon files seem to be gone, but folders are still there. Also, searching with pfinder, icon files and a script in /usr/bin are still there.
Size of ISO went down to 340 meg.
Portable firefox run with apulse.desktop file pointing to /mnt/home still works on remastered copy.
edit again: Some of the basic right-click actions in rox filer seem broken. I downloaded the Universal File Viewer and when I right clicked and chose rename or permissions or properties, nothing happened.
Last edited by dancytron on Thu 20 Sep 2018, 06:05, edited 2 times in total.
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Hiya, Mike.
Problem sorted, mi amigo.
I've done a re-build of the Chrome SFS. I've created a /home directory; moved 'spot' into it; reset all the permissions, and re-jigged all the scripts'n'stuff in the appropriate places. Posting this from Chrome in Bionic64 right now.
I'm just about cracking my jaw from yawning, mind (way past my bedtime, mate!).....so I'll upload this special 'Bionic' version to the Drive tomorrow. Just be patient.
In fact, since this seems to work fine, I may in fact build 'em like this from now on. We'll see how it goes.Kirk & jamesbond are certainly right about one thing; doing it this way makes it so much more like the 'safe' set-up Google demands (as found in most other distros).....and gets it away from /root. (Which is where the majority of problems (for Puppy) in current Chrome usually stem from.)
I'm afraid this does mean you end up with two 'spot' directories..!
Essentially this gives you Chrome installed to /home/'user_directory'. On this front at least, Pup has no option but to conform to 'standards'.....since Google will never budge on this now, and if ya don't toe the line, ya don't get to use the browser. One more nail in the coffin of Puppy's uniqueness.....
(*shrug*)
Catch ya tomorrow.
Mike.
Problem sorted, mi amigo.
I've done a re-build of the Chrome SFS. I've created a /home directory; moved 'spot' into it; reset all the permissions, and re-jigged all the scripts'n'stuff in the appropriate places. Posting this from Chrome in Bionic64 right now.
I'm just about cracking my jaw from yawning, mind (way past my bedtime, mate!).....so I'll upload this special 'Bionic' version to the Drive tomorrow. Just be patient.
In fact, since this seems to work fine, I may in fact build 'em like this from now on. We'll see how it goes.Kirk & jamesbond are certainly right about one thing; doing it this way makes it so much more like the 'safe' set-up Google demands (as found in most other distros).....and gets it away from /root. (Which is where the majority of problems (for Puppy) in current Chrome usually stem from.)
I'm afraid this does mean you end up with two 'spot' directories..!
Essentially this gives you Chrome installed to /home/'user_directory'. On this front at least, Pup has no option but to conform to 'standards'.....since Google will never budge on this now, and if ya don't toe the line, ya don't get to use the browser. One more nail in the coffin of Puppy's uniqueness.....
(*shrug*)
Catch ya tomorrow.
Mike.
Last edited by Mike Walsh on Thu 20 Sep 2018, 13:09, edited 2 times in total.
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
Morning, kiddiwinks.
OK. Following last night's re-packaging exercise on Chrome to ensure it'll run under Bionic64, I'm happy to be able to offer a working package here:-
https://drive.google.com/file/d/1Zo7dsg ... sp=sharing
No excuse now for you lot not to try out Phil's new 'baby'....! Enjoy.
Mike.
OK. Following last night's re-packaging exercise on Chrome to ensure it'll run under Bionic64, I'm happy to be able to offer a working package here:-
https://drive.google.com/file/d/1Zo7dsg ... sp=sharing
No excuse now for you lot not to try out Phil's new 'baby'....! Enjoy.
Mike.
Frugal install, on a USB hard drive, formatted ext 3, using save folder.
Homebank help not working.
Help
get help on line.....
Goes to a web site for login at Ubuntu one.
Help Contents
Get this message. See image attached.
Homebank help not working.
Help
get help on line.....
Goes to a web site for login at Ubuntu one.
Help Contents
Get this message. See image attached.
- Attachments
-
- capture16345.png
- (9.33 KiB) Downloaded 1802 times
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Frugal install, on a USB hard drive, formatted ext 3, using save folder.
Kernel 4.14.67
Processor
Intel i5-6400 CPU @ 2.70GHz
16GB RAM
I too have no clean shutdown.
Seems to be updating the save. However, it is on a hard drive.
The save is mounted read/write and written directly to, when on a hard drive.
So, not sure anything is done to save at shutdown.
Shutdown does not complete.
Stops at a screen with a lot of error messages, as already stated by others.
Have to hard power off to complete shutdown.
Kernel 4.14.67
Processor
Intel i5-6400 CPU @ 2.70GHz
16GB RAM
I too have no clean shutdown.
Seems to be updating the save. However, it is on a hard drive.
The save is mounted read/write and written directly to, when on a hard drive.
So, not sure anything is done to save at shutdown.
Shutdown does not complete.
Stops at a screen with a lot of error messages, as already stated by others.
Have to hard power off to complete shutdown.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
@ mikeslr:-
Mike; re:Openshot.
Do you absolutely have to have the newest 2-series version.....which offers very little extra over the last 1-series except a bit more eye-candy?
Because if you don't object to a somewhat older version, I now have Xenial64's Openshot 1.4.3 up-and-running in Bionicpup64.
in Tahrpup & earlier, the version of Openshot offered in the PPM was always the older build type (pre-Qt5). In Xenial, both pre- and post-Qt5 versions were offered alongside each other. Now, in Bionic, it's the Qt5 build only.
Ever since apps that many of us use regularly have begun to use Qt5, I have had absolutely no luck with them at all. In fact, as soon as I see a requirement for Qt5, I just turn around, walk away, and start looking around for something that'll do the same job without the need for this bloated monstrosity.
I don't hold Phil, or the Woof-CE team to account for these Qt5 issues. Over the last 18 months or so, ever since it was released and started to gain traction, I've lost track of the number of folks who've been complaining about it on a whole range of different fora. I personally believe it needs more work; further development to make it easier to build, and to 'extend' with additional modules.
We are, however, stuck with it, 'cos it's very definitely here to stay.
----------------------------------------------------------------------------
If you absolutely have to have the latest version, just because it is the 'latest', then you can stop reading right now; I won't waste your time any further. If, however, you don't mind an older one (that works), then here's how I did it. I'm not going to provide an all-in-one package, because it's bloody complex, and I don't have Battleshooter's immense reserves of patience; I do have limits!
----------------------------------------------------------------------------
From the Xenial repos:-
Download the following:- (these are direct links)
libgoocanvas - http://nl.archive.ubuntu.com/ubuntu/poo ... _amd64.deb
python-pygoocanvas - http://nl.archive.ubuntu.com/ubuntu/poo ... _amd64.deb
python-pil - http://security.ubuntu.com/ubuntu/pool/ ... _amd64.deb
libpng12 - http://security.ubuntu.com/ubuntu/pool/ ... _amd64.deb
Openshot 1.4.3 - http://nl.archive.ubuntu.com/ubuntu/poo ... .2_all.deb
Install the first four .debs. Leave Openshot for now.
From Bionic64's PPM:-
Install 'melt'. (This one pulls in many of the other missing deps).
Install 'python-mlt'.
Install 'python-xdg'.
Install 'libquicktime'.
Install 'frei0r-plugins'
Finally - install the Openshot 1.4.3 .deb you downloaded earlier.
I make absolutely no 'guarantees' as to whether this will work for anyone else. However; all things being equal, you should be able to start Openshot from the Multimedia Menu, and (after the usual few seconds delay, while the Python scripts all interact with each other, and 'do their thing'), it should 'fire up'.
If anybody else wants to try this, and has success with it....let us all know, please!
Mike.
Mike; re:Openshot.
Do you absolutely have to have the newest 2-series version.....which offers very little extra over the last 1-series except a bit more eye-candy?
Because if you don't object to a somewhat older version, I now have Xenial64's Openshot 1.4.3 up-and-running in Bionicpup64.
in Tahrpup & earlier, the version of Openshot offered in the PPM was always the older build type (pre-Qt5). In Xenial, both pre- and post-Qt5 versions were offered alongside each other. Now, in Bionic, it's the Qt5 build only.
Ever since apps that many of us use regularly have begun to use Qt5, I have had absolutely no luck with them at all. In fact, as soon as I see a requirement for Qt5, I just turn around, walk away, and start looking around for something that'll do the same job without the need for this bloated monstrosity.
I don't hold Phil, or the Woof-CE team to account for these Qt5 issues. Over the last 18 months or so, ever since it was released and started to gain traction, I've lost track of the number of folks who've been complaining about it on a whole range of different fora. I personally believe it needs more work; further development to make it easier to build, and to 'extend' with additional modules.
We are, however, stuck with it, 'cos it's very definitely here to stay.
----------------------------------------------------------------------------
If you absolutely have to have the latest version, just because it is the 'latest', then you can stop reading right now; I won't waste your time any further. If, however, you don't mind an older one (that works), then here's how I did it. I'm not going to provide an all-in-one package, because it's bloody complex, and I don't have Battleshooter's immense reserves of patience; I do have limits!
----------------------------------------------------------------------------
From the Xenial repos:-
Download the following:- (these are direct links)
libgoocanvas - http://nl.archive.ubuntu.com/ubuntu/poo ... _amd64.deb
python-pygoocanvas - http://nl.archive.ubuntu.com/ubuntu/poo ... _amd64.deb
python-pil - http://security.ubuntu.com/ubuntu/pool/ ... _amd64.deb
libpng12 - http://security.ubuntu.com/ubuntu/pool/ ... _amd64.deb
Openshot 1.4.3 - http://nl.archive.ubuntu.com/ubuntu/poo ... .2_all.deb
Install the first four .debs. Leave Openshot for now.
From Bionic64's PPM:-
Install 'melt'. (This one pulls in many of the other missing deps).
Install 'python-mlt'.
Install 'python-xdg'.
Install 'libquicktime'.
Install 'frei0r-plugins'
Finally - install the Openshot 1.4.3 .deb you downloaded earlier.
I make absolutely no 'guarantees' as to whether this will work for anyone else. However; all things being equal, you should be able to start Openshot from the Multimedia Menu, and (after the usual few seconds delay, while the Python scripts all interact with each other, and 'do their thing'), it should 'fire up'.
If anybody else wants to try this, and has success with it....let us all know, please!
Mike.
Last edited by Mike Walsh on Thu 20 Sep 2018, 15:42, edited 1 time in total.
I have frugal install on USB Flash. Save is set to 0 and ask at shutdown, most shutdowns when save is selected have worked. Last night I selected save, which failed to save. The shutdown process hung for an excessive time before showing the kernel error message.bigpup wrote: So, not sure anything is done to save at shutdown.
-
Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
@Terry, bigpup:-
It's definitely a kernel-related issue. I can also guarantee that neither of you are running sufficiently new hardware that you truly need the very latest kernels.
Swapping to Xenial's k4.9.58 very definitely fixed it for me. You now make two more people who are reporting the problem..... I don't believe this is isolated.
Needs addressing, methinks.
Mike.
It's definitely a kernel-related issue. I can also guarantee that neither of you are running sufficiently new hardware that you truly need the very latest kernels.
Swapping to Xenial's k4.9.58 very definitely fixed it for me. You now make two more people who are reporting the problem..... I don't believe this is isolated.
Needs addressing, methinks.
Mike.