Puppy Linux Discussion Forum

You can't, because drive icons are dynamically created at boot or when you plug in a USB/MMC device. You can, however, enable showing actual labels (if any): System -> Puppy Event Manager -> ROX Icons -> Show labels for each PARTITION . In order to set/change a label, you need to use a utility ...

You can't, because drive icons are dynamically created at boot or when you plug in a USB/MMC device. You can, however, enable showing actual labels (if any): System -> Puppy Event Manager -> ROX Icons -> Show labels for each PARTITION . In order to set/change a label, you need to use a utility ...

Chrome was installed via the FatDog control panel installer. I find it pretty odd that the FatDog sound test works but Chrome stays silent... Unfortunately, I don't have a USB headset, so can't even try to reproduce it, but here are some questions that could help narrowing down the culprit: - did ...

BarryK wrote: ↑Sat Jun 25, 2022 9:14 am

Will try "-o ro,noload" later. But, it may only apply to ext4 with a journal, and my partition does not have a journal.

You may also want to try losetup with '-r Read-only' option (if available) as a middleman.

Greetings!

Is there a schedule for a new FatDog release? Looking forward to your feedback. :thumbup: Well, nothing's set in stone yet. We're on a hiatus/vacation right now, but there should be 813 release (bugfixes and updates), before 900, whenever it's gonna happen... Thanks for the interest, though ...

Browse to /aufs/pup_multi/root/Desktop_launchers/Quick_apps and look for any whiteouts, e.g. .wh.htop.desktop . If it's there, removing it should make the actual symlink usable again. The presence of both file and .wh.file in /aufs/pup_multi is the result of creating that file, saving session, then ...

Fatdog64 uses qt5 5.11, so there is an obvious problem. How did you launch that Krita AppImage? It (5.1.0-prealpha) works for me in 813 (WIP). The problem with some AppImages, especially those using QT, is that they pick up system libs instead of the included ones, so if you run them from terminal ...

I see a lot of images of DeaDBeeF dressed up like a Xmas tree, with all sorts of stuff showing; music analyzers, spectrograms, all sorts of other stuff. Now, I have a lot of these in the 'plugins' directory.....and you can see all sorts of info about them in the 'Preferences' window.....but how the ...

Probably this is what happend: https://forum.puppylinux.com/viewtopic.php?t=4720 It's already fixed upstream: https://github.com/puppylinux-woof-CE/woof-CE/pull/2691 As for the recovery, ntfsundelete works pretty well, but here the file itself wasn't deleted, but its contents, so I wouldn't expect ...

Is the 1GB not enough all of a sudden? Yes, I think this might be the culprit. Although FD can boot in QEmu with only 1G, in case of a real hardware, some of the RAM can be seized by GPU as VideoRAM and hence inaccessible for CPU. Maybe 812's initrd size crossed the threshold. You still should be ...

I think it's the problem with booting itself... chiefengineer : Perhaps upgrading to a newer kernel would help. The latest we have in repo is 5.10.63 ( How to use a different kernel ). Also, I've read somewhere that acpi=off boot option helped somebody with a similar issue. Posting a photo of that ...

I think it's because the default shell for root is not /bin/bash, but /bin/sh (which is a symlink to bash, but still).

Try .shinit instead, it works for me.

Or change the shell to bash using chsh --shell /bin/bash root and re-login with wmexit logout.

Greetings!

Some searching the internet leads to no further information. All i can read is that it is not possible to have two files with identical names in one directory [...] Sure it's possible, it's just enough to fiddle with the filenames using a hex editor. ;) xscreenshot-20220401T225422.gif Anyway, it's ...

Great, thanks for testing! One more revision, though. I analyzed the system init script and it turned out that in addition to ...:multi:<dev>:... parameter, also ...:multi:device:<dev>:... and ...:multi:uuid:<uuid>:... constructs are accepted. That info is not present in FAQ. So, in the current ...

The correct command for multisession is multi, not device.
If it worked for you with the latter, it's probably by some weird coincidence...

Also, when you drag a folder, you'll get the correct argument, but for a savefolder.

Ok, so the final conclusion is that it works, right?

Greetings!

Thanks @JakeSFR, I did see that update. Two question for creating the 'correct' argument: Should the Multisession folder's base or the other folder within "/Sessions" be the one the user must drag to "3." field?Sessions-Folder.png. Or should FATDOG searching the /Sessions contents be enough for FD ...

Our Busybox's (v1.27.0) crond doesn't support special times yet, it was added in v1.28.0.
https://github.com/mirror/busybox/commi ... e3a706c016

Greetings!

@Clarity: note the 3rd point in the new builder: "3. Drag your savefile, savefolder or SFS into this box".

Greetings!

Have the FATDOG session names changed or is it because I have a test release? No, the savefile proto is defined in /etc/BOOTSTATE and it's still fd64save : # grep 'SAVEFILE_PROTO' /etc/BOOTSTATE SAVEFILE_PROTO='/fd64save.ext4' I think it switched to Sessions for you when you used that boot option ...

SAVEFILE Argument Builder error This leads to a problem that could/should be addressed in 'Savefile Argument Builder', where a drag-drop of the Sessions folder to the app does NOT yield an acceptable recommendation in the field below it in the utility. The error/bug is shown in this picture. https ...

savefile=direct:device:sda7:Sessions The path argument expects a path that includes the name of a savefile/dir, or in this case, a session SFS file. So, something like this: savefile=direct:device:sda7:/Sessions/session should read/create Sessions/multi-session-2022...sfs and so on. savefile=direct ...

Updated to v1.11. Changelog in the second post.

Greetings!

Hmm, that's how this glyph (f0 9f 8c 92) actually looks like and I agree that somebody should be fired. ;) The other one is an emoji, rendered by the browser; they've "fixed" it, apparently. I use Unifont instead of Symbola, btw. Anyway, it's possible to "invert" them 8 codepoints: 0x1f311 (127761 ...

That's very nice, and to my mind more time-effective than the Check Disk Usage utility for general awareness. It seems to me that a toggle for this would be a good addition to the Fatdog64 Event Manager settings. Well, if the rest of the guys would like the idea, then why not? Is there a reason to ...

I've been using this script since 2013, but recently I pimped it up by adding free/used bar to drive icons, in addition to free space info in tooltips. Note that it shows the bar only if the drive/partition is mounted and contains an actual filesystem (so no LUKS). I didn't want to make it an ...

GDM has a little indicator of free RAM space in the bottom panel. Technically, it's not GDM's indicator, it's freemem.sh script, which invokes GDM on right-click, but that's a detail. Once FatDog is loaded into RAM, it indicates 3.1GB of free space. During normal day operation this sometimes drops ...

FatDog64 ships with Graphical Disk Map 0.8.1. "Files are displayed in a cushioned tree map." Are there alternative tools available, both command line and GUI based, that allow you to analyze disk space usage in more detail and with filter options (tree style rather than visual map)? Check ncdu (CLI ...

debianfan wrote: ↑Thu Feb 10, 2022 1:39 am

Version 4.9 cannot be used in thunar file manager

Why not, what do you mean? Works for me.
And are you saying that versions up to 4.8 worked ok for you and only 4.9 is affected?

Greetings!

Version 4.9:

- fix AppRun breaking completely if Gtkdialog is built without VTE (thanks to jamesbond)
- add audio/x-mo3 MIME (thanks to Grey)

First post updated.

Greetings!

Oh, I forgot to add audio/x-mo3 MIME type. Will be fixed in next version.

Thanks for the feedback &
Greetings!