Fatdog64-710 beta [28 August 2016] [CLOSED]
Some issues...
1) I had problems with using Abiword in 710 as the entire program and all work are lost as you try to save it. The program simply terminate and work is just lost. I consider my self a not complete newbee at Fatdog.
2) As i updated trough Gslapt today, my firefox was downgraded from 48.x to 38 "Nightly". That seems to be backwards to me?
apart from that... VERY HAPPY...
Can not wait for the release.
1) I had problems with using Abiword in 710 as the entire program and all work are lost as you try to save it. The program simply terminate and work is just lost. I consider my self a not complete newbee at Fatdog.
2) As i updated trough Gslapt today, my firefox was downgraded from 48.x to 38 "Nightly". That seems to be backwards to me?
apart from that... VERY HAPPY...
Can not wait for the release.
@Gobbi:
@Atle:
I don't use sopcast-player so I don't know which ports etc that it needs. I hope someone more knowledgeable will come to your rescue.I would like to set eztables to allow an application like Sopcast-Player to access internet .
I only started eztabes from Control Panel/System/Manage Servers and Services .
I understand that I should fix a new rule in the first group of rules in /etc/eztables/eztables.cfg .
I don't know how to , I tried but I don't get it . What kind of SERVICE and how to discover which group
of destination ports the application uses ... Maybe connecting only to Google DNS_SERVERS is not
enough ? Please , I need some help here ! Can anybody help ?
Yes, this is the normal behaviour of the new rox. There is no harm, though I suppose it get some time to get used to.Loading devx sfs . After that , opening /usr/lib64 folder (which became quite big) show
the folders icons with a small delay . During this delay I see only rectangles instead
of the folder-icons . It happens only the first time I load the devx sfs .
Because you said "It works good and fast after that" I think the problem is not because of Fatdog itself, but more probably because of the disk space used to store 710 savefile/savedir is now heavily fragmented.Another issue : opening Seamonkey takes a little more than 10 seconds . It works good and
fast after that . I made a test . I put Seamonkey 2.40 in FD700 and it opens normally , that is as
fast as Seamonkey 2.32 , which I usually use in that release . On the other hand - I tested Seamonkey
2.32 in FD710b an it opens also slow as Seamonkey 2.40 . I already updated rox .
Somehow FD710b is a bit slower than FD700 . My FD700 iso I used for these tests has more than 800 Mb.
@Atle:
Abiword is very crash-prone. We are getting rid of it on the next release, so please don't get too attached to it.1) I had problems with using Abiword in 710 as the entire program and all work are lost as you try to save it. The program simply terminate and work is just lost. I consider my self a not complete newbee at Fatdog.
Our self-compiled Firefox is only up to version 38 (for many reasons). We may compile a newer ESR version of firefox, but that will take time. If you want to update to the latest, use Control Panel -> Updates -> Update Firefox instead. This will install the latest official binary from Mozilla. Beware that you need to install GTK3 first from gslapt, otherwise it won't work.2) As i updated trough Gslapt today, my firefox was downgraded from 48.x to 38 "Nightly". That seems to be backwards to me?
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Thanks for answering jamesbond . Searching the net I found that both Sopcast and Eiskaltdcpp ,
need a wide range of ports opened , so I don't see any sense opening so many ports under
eztables . I'm afraid it's either having an efficient firewall or using those applications .
browsers . FD710b is fast in every aspect except for Samonkey and Firefox which are slow to start .
Google Chrome opens in less than a second though ... so I don't know what to say ...
need a wide range of ports opened , so I don't see any sense opening so many ports under
eztables . I'm afraid it's either having an efficient firewall or using those applications .
I always run Fatdog or other Puppies without savefile , copying the OS in RAM. I tried all threejamesbond wrote: Because you said "It works good and fast after that" I think the problem is not because of Fatdog itself, but more probably because of the disk space used to store 710 savefile/savedir is now heavily fragmented.
browsers . FD710b is fast in every aspect except for Samonkey and Firefox which are slow to start .
Google Chrome opens in less than a second though ... so I don't know what to say ...
SFS files not executable
I don't see any mention of this so far and therefore suspect it's something I have done incorrectly. I've install Fatdog64-710 beta to HDD and everything appears fine other than that sfs files are not executable / recognised in ROX Filer. Some SFS files can be loaded via Control Panel > System SFS Loader.
I've updated all packages via Fatdog System Updater if that is a factor.
On a more positive note, handling of Wine app windows works better in the beta than in the alpha.
I've updated all packages via Fatdog System Updater if that is a factor.
On a more positive note, handling of Wine app windows works better in the beta than in the alpha.
@jake29, are you clicking sfs files in rox? If so then right-click the sfs file and choose "load SFS" to activate it. The default left-click action is to open the sfs file as a folder, so you can explore it. Left-clicking the sfs file again closes the folder.
@gobbi, what happens if you open a terminal and run seamonkey-spot? Do you get error messages? If so paste them in your reply.
@gobbi, what happens if you open a terminal and run seamonkey-spot? Do you get error messages? If so paste them in your reply.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
"load SFS" and "unload SFS" options are not available. There is no default left-click action assigned. I can however use terminal:step wrote:@jake29, are you clicking sfs files in rox? If so then right-click the sfs file and choose "load SFS" to activate it. The default left-click action is to open the sfs file as a folder, so you can explore it. Left-clicking the sfs file again closes the folder.
Code: Select all
load_sfs.sh --load kodi-16.1-x86_64.sfs
Is it just load_sfs not being properly installed? You should see all the top four menu entries in your rox right-click menu for an sfs file...
- Attachments
-
- xscreenshot-00007.png
- (17.13 KiB) Downloaded 461 times
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
None of those options are available to me. I'm running: rox-filer-jun7 2016.08.step wrote:Is it just load_sfs not being properly installed? You should see all the top four menu entries in your rox right-click menu for an sfs file...
Could this be a permissions issue? When installing Fatdog, I formatted the drive; no old system files remained.
Cannot understand why some old pets I use on many other pups do
not work on fatdog64. They appear to install, and there are menu
entries, but nothing happens when they are clicked.
One pet is inkgui-.2.pet and the other is candi-1.4-.pet (by rcrsn51
for canon printers). In the case of candi "Canon scangearmp scanner"
appears in the Graphic menu (indicating the candi install) but the
scanner is not invoked. In the case of inkgui it appears in the System
menu but it never activates.
The Canon printer installed without a hitch and the Xsane scanner
works. The Canon scanner (designed by Canon) is much better, and
I'd like very much to use it, as well as to have a ink level indicator.
So any help would be appreciated.
not work on fatdog64. They appear to install, and there are menu
entries, but nothing happens when they are clicked.
One pet is inkgui-.2.pet and the other is candi-1.4-.pet (by rcrsn51
for canon printers). In the case of candi "Canon scangearmp scanner"
appears in the Graphic menu (indicating the candi install) but the
scanner is not invoked. In the case of inkgui it appears in the System
menu but it never activates.
The Canon printer installed without a hitch and the Xsane scanner
works. The Canon scanner (designed by Canon) is much better, and
I'd like very much to use it, as well as to have a ink level indicator.
So any help would be appreciated.
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
@prehistoric
Yes, both 32bit-libs-slacko.sfs and 32bit-slacko.sfs
Then after loading I did a ldconfig in the terminal.
Tried rebooting to no avail.
Actually, I thought this unnecessary since I read that the 32 bit libs are
preinstalled in Fatdog64?
Edit: No, james was writing about wine handling both 32 and 64 bit, not
fatdog64 as such.
Searching led me to a requirement for fd64-32bit-libs-7.sfs but I
couldn't locate it .... only the -6.sfs which I tried to no avail. What
a mess
Yes, both 32bit-libs-slacko.sfs and 32bit-slacko.sfs
Then after loading I did a ldconfig in the terminal.
Tried rebooting to no avail.
Actually, I thought this unnecessary since I read that the 32 bit libs are
preinstalled in Fatdog64?
Edit: No, james was writing about wine handling both 32 and 64 bit, not
fatdog64 as such.
Searching led me to a requirement for fd64-32bit-libs-7.sfs but I
couldn't locate it .... only the -6.sfs which I tried to no avail. What
a mess
Last edited by artsown on Sun 09 Oct 2016, 17:04, edited 1 time in total.
jake29 wrote:None of those options are available to me. I'm running: rox-filer-jun7 2016.08.step wrote:Is it just load_sfs not being properly installed? You should see all the top four menu entries in your rox right-click menu for an sfs file...
Could this be a permissions issue? When installing Fatdog, I formatted the drive; no old system files remained.
Perhaps that system updater messed up mime types, which link to right-click associations. Can you please tell how you installed FD beta exactly, what steps?earlier jake29 wrote:I don't see any mention of this so far and therefore suspect it's something I have done incorrectly. I've install Fatdog64-710 beta to HDD and everything appears fine other than that sfs files are not executable / recognised in ROX Filer. Some SFS files can be loaded via Control Panel > System SFS Loader.
I've updated all packages via Fatdog System Updater if that is a factor.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
I did not use the OS much prior to running the system updater so cannot confirm the issue existed before doing so.step wrote:Perhaps that system updater messed up mime types, which link to right-click associations. Can you please tell how you installed FD beta exactly, what steps?
Below is a screenshot of current HDD partition layout. Windows is on SDA2/3. I formatted SDA1 and went through the Fatdog64 installer. No Bootloader was installed. ISO was used for step 3.
After this, any time I want to load Fatdog64, I use the live cd - it detects the fd64save.ext4 on SDA1 - a method I'd previously used with the 710 alpha with no obvious issues.
Also I note 'GParted' is not in the system menu - maybe it was my imagination but I thought it was there in the 710 alpha.
- Attachments
-
- screenshot1a.png
- (20.55 KiB) Downloaded 379 times
That could be the culprit, indeed; there's much going on with packages now.jake29 wrote:I've updated all packages via Fatdog System Updater if that is a factor.
I'd suggest to make another, clean install and see if it's ok.
It's here: http://distro.ibiblio.org/fatdog/iso/710beta/artsown wrote:Searching led me to a requirement for fd64-32bit-libs-7.sfs but I
couldn't locate it .... only the -6.sfs which I tried to no avail.
Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]
Okay, thanks. Unless it would be of genuine benefit to you or the other developers - I would prefer to live with things as they are for now. I have no other problems.SFR wrote:That could be the culprit, indeed; there's much going on with packages now.jake29 wrote:I've updated all packages via Fatdog System Updater if that is a factor.
I'd suggest to make another, clean install and see if it's ok.
Not everyone agrees, apparently, but I find it inconceivable that anyone would mix any Linux on the same disc as a Windydoze in this day and age! So many options at such low cost. I find the best way is with caddies and incredibly cheap HDs, but other options include USB, SD booting or running a liveCD. FD may have grown massively in size since BK's Puppyv1.1, but it's still a moderately compact distro which would run satisfactorily on a last year's (5yr old, even) box. You can find a 64-bit compatible 754/939, even late P4 boxes in skips/dumpsters/charity shop/local amenity recycling facility - if not entirely free, perhaps a charitable donation. Recertified HDs are as good as new for a few shekels more if you need greater peace of mind. Let's all beat this crazy spiral driven by the Wintel cartel and stop further landfill; recycling is cool. Let's avoid unnecessary intellectual SW puzzles?
Sage - I can't help feel your comments are directed at me. Perhaps I did bring disgrace and shame into this forum with my post and it's revelation. But just as you should not attribute to malice what can be accounted for by stupidity; do not attribute ignorance to what could be necessity and practicality and the choice between paying the rent and eating. Yes, even in the western world; incredible poverty still exists.Sage wrote:Not everyone agrees, apparently, but I find it inconceivable that anyone would mix any Linux on the same disc as a Windydoze in this day and age! So many options at such low cost. I find the best way is with caddies and incredibly cheap HDs, but other options include USB, SD booting or running a liveCD. FD may have grown massively in size since BK's Puppyv1.1, but it's still a moderately compact distro which would run satisfactorily on a last year's (5yr old, even) box. You can find a 64-bit compatible 754/939, even late P4 boxes in skips/dumpsters/charity shop/local amenity recycling facility - if not entirely free, perhaps a charitable donation. Recertified HDs are as good as new for a few shekels more if you need greater peace of mind. Let's all beat this crazy spiral driven by the Wintel cartel and stop further landfill; recycling is cool. Let's avoid unnecessary intellectual SW puzzles?
jake: You completely misunderstand.
Money is NOT necessarily needed!
You could start by indicating in which country you reside. If it is anywhere near me I will GIVE you a spare system, including caddies. But you can obtain what you need by keeping your eyes and ears open, making good friends and politely asking for cast-offs. Many folks are only too glad to off-load their surplus stuff rather than sending to landfill. And, please don't complain about me before you check out my record.
Money is NOT necessarily needed!
You could start by indicating in which country you reside. If it is anywhere near me I will GIVE you a spare system, including caddies. But you can obtain what you need by keeping your eyes and ears open, making good friends and politely asking for cast-offs. Many folks are only too glad to off-load their surplus stuff rather than sending to landfill. And, please don't complain about me before you check out my record.