(old)Puppy Linux Discussion Forum

Posted: **Fri 18 Jan 2019, 00:50**

they seem to be upgraded and installed already

libmypaint needs to be installed for gimp 2.10

Posted: **Fri 18 Jan 2019, 00:52**

As well I found that the mypaint brushes should be installed.

Download mypaint brushes for gimp 2.10:
Size 2.4 mb

https://drive.google.com/open?id=1moqfJ ... RKQ--_pDWc

Posted: **Tue 22 Jan 2019, 05:18**

@Jamesbond , @step and any other fatdog team

I'm using linux version of Telegram messenger from fatdog (700).
but , recently , and specially from 800 alpha , Telegram dont start easily.
in 90% of times , message appeard , and if you try several time , suddenly skip button works and telegram will be appear.

first i think it's about telegram application , but as this problem only show up in fatdog , ... , I came here for any help and suggestion.

Thank you

Posted: **Tue 22 Jan 2019, 08:10**

@borzeh, sorry I don't use telegram. Have you tried a newer Telegram binary? There's a Telegram AppImage that *should* work in all Linux versions. You could try that. There's also a thread about Telegram in this forum. Another thing you can try is to start telegram in a terminal window and see if it prints out any error messages, which could shed some more light on this issue.

Posted: **Tue 22 Jan 2019, 13:19**

@spot
Thank you very much

I also try to run telegram from terminal (As Spot mentioned before) , and ...

first time it show : floating point exception / and nothing run
second time a window appeard that show try to check update! / when i click try again , nothing happened , and when i click on skip window closed and floating point exception in terminal.
third time: check update window appeard again / when i click try again , nothing happened , and when i click on skip / Update window freeze and cpu usage get to 25% level.
when kill process from task manager , window disappear and in the terminal i have only "killed" text.

at the 4th time , when i type telegram, it run without any exception!

if i close telegram process and run it again , every thing going to start point!

sometimes skip button on update window , run program!

Posted: **Wed 23 Jan 2019, 01:37**

is there a way to remove the USB stick after boot, run from RAM layer, then reinsert the USB stick before shutdown and save the RAM layer onto the USB stick? i seem to bump the USB stick into everything as it protrudes 2 inches out of the side of my laptop.

i tried currently, but when i re-insert the USB stick it mounts with a different name so it cannot backup properly when i shutdown.

I think such an option would add a lot of value to fatdog since laptops are ubiquitous nowadays and i assume others may be as clumsy as I am when moving around.

Posted: **Wed 23 Jan 2019, 01:52**

h2sammo3 wrote:is there a way to remove the USB stick after boot, run from RAM layer, then reinsert the USB stick before shutdown and save the RAM layer onto the USB stick? i seem to bump the USB stick into everything as it protrudes 2 inches out of the side of my laptop.

i tried currently, but when i re-insert the USB stick it mounts with a different name so it cannot backup properly when i shutdown.

I think such an option would add a lot of value to fatdog since laptops are ubiquitous nowadays and i assume others may be as clumsy as I am when moving around.

A couple of things to consider. 1. Use a nano usb stick as they only protrude about one centimetre. 2. Use the blkid to identify your usb stick rather than sdb1 etc. This way your usb stick will always be found. Look in Fatdog help for boot options for more information. Search for uuid.

Posted: **Wed 23 Jan 2019, 07:41**

I don't believe that qmake is in devX. I need it to build synergy.

Edit: I installed "qt5" from gsplat and it had the missing file

Edit 2 I also installed qt4 since I couldn't figure out how to compile synergy for qt5. My previously complied package for synergy worked after installing qt4.

Posted: **Fri 25 Jan 2019, 09:55**

Modifying fstab seems to prevent fatdog64 from stating up. This seems to affect the current and previous version of fatdog64. Here is an example line I added (ip and mount point slightly modified):

Code: Select all

//192.168.x.x/puppyshare /mnt/samba     iocharset=utf8,file_mode=0777,dir_mode=0777,uid=0,gid=0,credentials=/etc/samba/smbcred 0 0

This modification of fstab works for me to access a samba share from another computer. Unfortunately it prevents me from booting.

Posted: **Fri 25 Jan 2019, 20:36**

s243a wrote:Modifying fstab seems to prevent fatdog64 from stating up. This seems to affect the current and previous version of fatdog64. Here is an example line I added (ip and mount point slightly modified):
Code: Select all
//192.168.x.x/puppyshare /mnt/samba     iocharset=utf8,file_mode=0777,dir_mode=0777,uid=0,gid=0,credentials=/etc/samba/smbcred 0 0

The fstab line you posted is missing the required file system field, cifs in this case.
How does Fatdog64 "not start", can you describe in more detail? Does it hang at some point in the boot process? What's on the screen at that point?
How do you connect to the network? wifi or wired, when you mount the samba share successfully after Fatdog64 has booted?
If Fatdog64 hangs while booting you could try to add option "showerr" (without quotes) to your initrd line in the boot manager configuration file or directly from the boot manager menu. This option directs boot error messages to the screen.
One of the things that could block initrd is password prompts from the samba mounter. With "showerr" you'll be able to see such prompts. I see that you've included a credentials file to the samba mount options but maybe it isn't enough.

Posted: **Sun 27 Jan 2019, 02:33**

smokey01 wrote:
h2sammo3 wrote:is there a way to remove the USB stick after boot, run from RAM layer, then reinsert the USB stick before shutdown and save the RAM layer onto the USB stick? i seem to bump the USB stick into everything as it protrudes 2 inches out of the side of my laptop.

i tried currently, but when i re-insert the USB stick it mounts with a different name so it cannot backup properly when i shutdown.

I think such an option would add a lot of value to fatdog since laptops are ubiquitous nowadays and i assume others may be as clumsy as I am when moving around.
A couple of things to consider. 1. Use a nano usb stick as they only protrude about one centimetre. 2. Use the blkid to identify your usb stick rather than sdb1 etc. This way your usb stick will always be found. Look in Fatdog help for boot options for more information. Search for uuid.

one problem: i cannot umount the partition which contains the fatdog system. how do i bypass this problem.

Posted: **Tue 29 Jan 2019, 20:45**

I have a usb scanner CanoScan N656U that worked with xsane on Fatdog 721.
However, in Fatdog 800b it is not recognized in xsane.
In both cases running without savefile.
The results of the sane-find-scanner and scanimage commands are
In 721:

Code: Select all

# sane-find-scanner 

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.
  # Also you need support for SCSI Generic (sg) in your operating system.
  # If using Linux, try "modprobe sg".

found USB scanner (vendor=0x04a9 [Canon], product=0x2206 [CanoScan], chip=LM9832/3) at libusb:002:004
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.


# scanimage -L
device `v4l:/dev/video0' is a Noname HP Webcam-101: HP Webcam-101 virtual device
device `plustek:libusb:002:004' is a Canon CanoScan N650U/N656U flatbed scanner

In 800b:

Code: Select all

# sane-find-scanner 

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.
  # Also you need support for SCSI Generic (sg) in your operating system.
  # If using Linux, try "modprobe sg".

found USB scanner (vendor=0x04a9 [Canon], product=0x2206 [CanoScan], chip=LM9832/3) at libusb:002:004
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.


# scanimage -L 
device `v4l:/dev/video0' is a Noname HP Webcam-101: HP Webcam-101 virtual device

In 800b xsane only recognizes the HP Webcam-101: HP Webcam-101.

The sane-backends (this scanner uses plustek) are version 1.0.27 in Fatdog800b and 1.0.25 in Fatdog721

Posted: **Tue 29 Jan 2019, 21:19**

@Mories
A stab in the dark:

http://sane-project.org/ wrote:Note 3: The Linux USB3 workaround which was added in version 1.0.25 is now disabled by default. If you have difficulty using a scanner which previously worked, or intermittent scanner availability, try setting the new environment variable SANE_USB_WORKAROUND=1 before starting your frontend.

Greetings!

Posted: **Tue 29 Jan 2019, 22:46**

@SFR
Thanks for your hint. I had already tried it and it was not solved either.
Found the solution at https://wiki.archlinux.org/index.php/SA ... k_scanners
Some plustek scanners (noticeably Canoscan ones), require a lock directory. Make sure that /var/lock/sane directory exists ...

In Fatdog721 that directory exists, but in Fatdog800b is missing.
Creating this directory in Fatdog800b with the same permissions that it have in Fatdog721, the scanner is detected and works correctly.

Posted: **Tue 29 Jan 2019, 23:23**

Thanks Mories, we'll fix it.

Greetings!

Posted: **Wed 30 Jan 2019, 08:49**

The owner and group of /home/spot in the devx sfs is set to root:root , which causes problems when the devx loads over the basesfs (for example, seamonkey-spot does not start).

Similarly /home/default and /home /ftp in initrd?

Posted: **Wed 30 Jan 2019, 09:11**

mories wrote:The owner and group of /home/spot in the devx sfs is set to root:root , which causes problems when the devx loads over the basesfs (for example, seamonkey-spot does not start).

Thanks. This is a bug, we'll fix it.

Similarly /home/default and /home /ftp in initrd?

This should not be an issue because initrd is always at the bottom of the stack, but I'll make sure that the basesfs overrides these two as well.

@h2sammo: use the "multisession" mode. Multisession mode does not "hog" your device, you can take it out and plug it back in later.

Posted: **Fri 01 Feb 2019, 02:40**

Apologies for the late report. As p310don mentioned back in December in this thread, I am seeing unusual CPU usage. I am running kernel v4.19.10.

It happens about 15 seconds after reaching desktop - CPU usage increases to 50% and remains there. HTOP shows nothing.

Additionally, I have a problem with wine:

Code: Select all

# winecfg
wine: created the configuration directory '/root/.wine'
wine: Unhandled page fault on read access to 0x00000004 at address 0xf798de04 (thread 000b), starting debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 10 100") (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
err:ole:marshal_object couldn't get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046}
err:ole:marshal_object couldn't get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa}
err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002
err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002
err:ole:get_local_server_stream Failed: 80004002
err:ole:marshal_object couldn't get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046}
err:ole:marshal_object couldn't get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa}
err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002
err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002
err:ole:get_local_server_stream Failed: 80004002
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
Wine cannot find the ncurses library (libncursesw.so.5).
wine: Unhandled page fault on read access to 0x00000004 at address 0x7e75ee04 (thread 0009), starting debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 8 100") (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
# wine: Unhandled page fault on read access to 0x00000004 at address 0x7e926e04 (thread 0018), starting debugger...
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:winediag:schan_imp_init Failed to load libgnutls, secure connections will not be available.
fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x6a0cb608, context 0x938710, init_notify 0, handle 0x116e7b4): stub

EDIT: CPU Usage returned normal after around 10-15 mins. Unsure if it was something I did.

EDIT2: /etc/init.d/91-autochownd was the cause.

Posted: **Fri 01 Feb 2019, 05:28**

@jake29: which version of wine?

autochown ... Do you have a lot of stuff under "Downloads" folder? If you do, it could explain it.

Posted: **Fri 01 Feb 2019, 06:18**

jamesbond wrote:@jake29: which version of wine?

autochown ... Do you have a lot of stuff under "Downloads" folder? If you do, it could explain it.

wine-2.0.1-721.sfs is the version I need to run a specific app. I see Wine 4.0 installs and successfully.

The 91-autochownd issue is in a clean install - 'Downloads' folder is almost empty.

EDIT: I just realized that I should probably try compiling wine 2.0.1 for Fatdog64-800 <blush>

(old)Puppy Linux Discussion Forum

Fatdog64-800 Alpha / Beta [20 Dec 2018] [CLOSED]

mypaint brushes

Telegram

remove USB stick after boot

Re: remove USB stick after boot

Re: remove USB stick after boot

Usb scanner CanoScan N656U

owner:group /home/spot in devx sfs

Re: owner:group /home/spot in devx sfs

50% CPU Usage when idle