Fatdog64 702 Final [7 Feb 2016] [CLOSED]

Message

SFR · #31 Post by **SFR** » Sat 23 Jan 2016, 20:10

Not a biggie (I'm running out of actual bugs

), but can we disable startup_notification in dunst?

# diff /aufs/pup_ro/etc/xdg/dunst/dunstrc /etc/xdg/dunst/dunstrc 
19c19
<     startup_notification = true
---
>     startup_notification = false
#

It's rather annoying to see "startup dunst is up and running" pop-up along with normal notification from another app, when dunst gets invoked for the first time in given X session.

Greetings!

L18L · #32 Post by **L18L** » Sun 24 Jan 2016, 10:24

SFR wrote:It's rather annoying to see "startup dunst is up and running" pop-up...

..and even more annoying if one (me) not knowing what this is all about.

SFR · #33 Post by **SFR** » Sun 24 Jan 2016, 10:29

L18L wrote:
SFR wrote:It's rather annoying to see "startup dunst is up and running" pop-up...
..and even more annoying if one (me) not knowing what this is all about.

Hey L18L, try this:

Code: Select all

notify-send "That's what I mean..."

Greetings!

mavrothal · #34 Post by **mavrothal** » Sun 24 Jan 2016, 15:20

Trying 702rc on my retina Macbook and as older FD64 versions, works with similar issues (blacklist broadcom module, disable some gpe interrupts that hog the CPU, allow vaterry to run even if /proc/acpi/battery is empty, add a big cursor, adjust global and app-specific font sizes etc).
One issue I have is that I can not change the tray height adding "height=XX" in /etc/xdg/razor/razor-panel/panel.conf uder [panel] (or any other way I tried). Any hints?
Another little annoyance is that hfs+ (mac) volumes are mounted ro by default although all the tools are there for rw and you can do it with "-o force,rw". This means that FS files can not be saved in Mac partitions, which maybe wise but how do I change it if I feel risky?

As a general notion, a lot of FD specific apps do not scale well in high resolution screens or when you increase font size globally (because you need glasses change...). The FD control panel, Nathan wp setter, Wifi GUI etc are pretty bad. flSynclient is simply terrible since is ignoring global fond size too.
I guess not many high resolution screen machines will be using FD tomorrow, but 3-4 year down the road when they age enough and the windows registry will do its thing, they will.

A couple more Mac specific issues, BT detected but failed to connect with magic mouse (and I did try). Adjusting the touchpad with flSysclent is a pain and never really works well.

Bottom line, is nice that I can boot FD in the Macbook but it looks much better running in a VM under OSX

Gobbi · #35 Post by **Gobbi** » Sun 24 Jan 2016, 21:27

mavrothal wrote: One issue I have is that I can not change the tray height adding "height=XX" in /etc/xdg/razor/razor-panel/panel.conf uder [panel] (or any other way I tried). Any hints?

Usually , rightclick on the panel -> Configure panel -> uncheck 'Use automatic sizing'
If it doesn't work , look into /usr/share/razor/themes/yourtheme/razor-panel.qss

step · #36 Post by **step** » Sun 24 Jan 2016, 22:51

OK, I started testing RC just minutes ago. So far so good, I'm running a split initrd as usual. Minor fix, /usr/bin/dir2pet line 106

Code: Select all

[ -f /etc/xdg/menus/hierarchy] && . /etc/xdg/menus/hierarchy #has PUPHIERARCHY variable.

There should be a space between 'y' and ']'

mavrothal · #37 Post by **mavrothal** » Mon 25 Jan 2016, 05:43

Gobbi wrote:
mavrothal wrote: One issue I have is that I can not change the tray height adding "height=XX" in /etc/xdg/razor/razor-panel/panel.conf uder [panel] (or any other way I tried). Any hints?
Usually , rightclick on the panel -> Configure panel -> uncheck 'Use automatic sizing'

Thanks that did it (I had to connect a mouse since no reliable rightclick with touchpad...). Just wondering where the entry in /etc/xdg/razor/razor-panel/panel.conf was overwritten.
Unfortunately the increased panel height did not solve the problem was intended for, the small tray icons and and writing (see pick). Anyway to adjust that one specifically?
BTW the mtPaint screen capture message also does not scale or observe global font size.

Another strange thing is that rightclick (now that I have it

) on the desktop gives a different menu than the panel menu! I guess different things are called but maybe shouldn't.

Gobbi · #38 Post by **Gobbi** » Mon 25 Jan 2016, 10:30

mavrothal wrote:Just wondering where the entry in /etc/xdg/razor/razor-panel/panel.conf was overwritten.

/root/.config/razor/razor-panel/panel.conf

Unfortunately the increased panel height did not solve the problem was intended for, the small tray icons and and writing (see pick). Anyway to adjust that one specifically?

I edited /usr/share/razor/themes/mytheme/razor-panel.qss - I've put the height , spacing and icon-size to 32 and the clock font-size to 18 and everything looks better . But I guess there is a limit playing with this...
The free disk space font size belong to a transparent icon so icon-size increase would help a little . Try also to increase the global font size from ControlPanel/Desktop/Set global font size because your display resolution is high . Also the fonts from the taskbar buttons are bound to the gtk-theme fonts : ControlPanel/Desktop/Chtheme GTK theme chooser

Another strange thing is that rightclick (now that I have it ) on the desktop gives a different menu than the panel menu! I guess different things are called but maybe shouldn't.

Rightclick menu belongs to the window manager - the bottom left menu belongs to the panel .

mavrothal · #39 Post by **mavrothal** » Mon 25 Jan 2016, 11:32

Gobbi wrote: I edited /usr/share/razor/themes/mytheme/razor-panel.qss -

A bit tedious but it works. Thanks.
BTW neither the gliper not the mixer icons scale above 24px.

Also, how do you resize the quicklaunch icon size?

Another GUI little thing. Which script/config file positions the dive icons in FD? Looks like repositioning by user is lost after X restart.

SFR · #40 Post by **SFR** » Mon 25 Jan 2016, 12:37

mavrothal wrote:Another GUI little thing. Which script/config file positions the dive icons in FD? Looks like repositioning by user is lost after X restart.

It's Event Manager (Control Panel -> Desktop -> Fatdog64 Event Manager) or manually in /etc/eventmanager, just like in Puppy.

Greetings!

step · #41 Post by **step** » Mon 25 Jan 2016, 14:03

Is it just me or does anybody else see the same thing? pnmtojpeg used to work in 701

Code: Select all

# pnmtojpeg
pnmtojpeg: error while loading shared libraries: libnetpbm.so.10: cannot open shared object file: No such file or directory

Code: Select all

# readlink -f `which pnmtojpeg`
/usr/bin/pnmtojpeg

# find /aufs/pup_ro -name *netpbm*
/aufs/pup_ro/usr/lib64/libnetpbm.so
/aufs/pup_ro/usr/lib64/libnetpbm.so.11
/aufs/pup_ro/usr/lib64/libnetpbm.so.11.64
/aufs/pup_ro/usr/share/netpbm
/aufs/pup_ro/var/log/packages/netpbm-advanced-10.64.1-x86_64-1

jamesbond · #42 Post by **jamesbond** » Mon 25 Jan 2016, 14:15

@mavrothal: "As a general notion, a lot of FD specific apps do not scale well in high resolution screens or when you increase font size globally (because you need glasses change...). The FD control panel, Nathan wp setter, Wifi GUI etc are pretty bad."

-> We discussed this earlier during FatdogArm running on XO.
A lot of these issues depend on the application authors; it's not a simple matter.
As Gobbi and others said, the most crude workaround is by setting the Xft.dpi parameter; but as you found out not all apps honours this setting.
It's also not a simple matter of just using larger-sized icons. I acknowledge that this is a problem, but something that will probably take a long time to address. We'll probably address this as we go, one (very little) step at at time

(Motivation is very low because I don't own those hi-dpi machines

)

"Another little annoyance is that hfs+ (mac) volumes are mounted ro by default although all the tools are there for rw and you can do it with "-o force,rw"

-> Please run guess_fstype on the hfs+ partition. I tried creating an image with hfs+ and it is mounted as rw. guess_fstype on the image returns "hfsplus". If you can tell me whether or not your hfs+ is detected as "hfsplus" (output of guess_fstype from your Mac partition), then I can force it to be loaded as "rw" from initrd (and mount-helper) too.

"on the desktop gives a different menu than the panel menu!"

-> As Gobbi said - right-click comes from openbox. Panel menu comes razor-panel.

I agree the openbox right-click menu could be made better. smokey01 actually worked out to add decorations and icons to the openbox manu so that it looks more like the panel menu, but if I recall correctly it is done by hardcoding the menus so adding/removing apps to /usr/share/applications no longer has effect.

"BT detected but failed to connect with magic mouse"

-> This could be BT adapter not fully supported. What's the BT chip used in the Mac? Is it the infamous Broadcom? (If it is, forget it - I threw away my Broadcrap wifi+bt combo so that I don't have to deal with it).

"Also, how do you resize the quicklaunch icon size?"

-> Create a new file in /etc/control-panel-applets.dir, inside specify ICON_DISPLAY_SIZE="32 32" (change "32 32" to "48 48" or "128 128" as you wish). Beware that most of the icons are actually 48x48 so scaling larger than that makes the icon blurred.

@step: fixed. It's anyway just cosmetic because Fatdog doesn't have /etc/xdg/menus/hierarchy anyway.

"cant run pnmtojpeg" -> can't reproduce. You may have accidentally installed older pnmtojpeg from elsewhere.

Code: Select all

# ldd /usr/bin/pnmtojpeg 
	linux-vdso.so.1 (0x00007fffc1b4d000)
	libnetpbm.so.11 => /usr/lib64/libnetpbm.so.11 (0x00007fa0e775d000)
	libjpeg.so.8 => /usr/lib64/libjpeg.so.8 (0x00007fa0e7512000)
	libm.so.6 => /lib64/libm.so.6 (0x00007fa0e7221000)
	libc.so.6 => /lib64/libc.so.6 (0x00007fa0e6eab000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fa0e799a000)

mavrothal · #43 Post by **mavrothal** » Mon 25 Jan 2016, 15:30

SFR wrote:
mavrothal wrote:Another GUI little thing. Which script/config file positions the dive icons in FD? Looks like repositioning by user is lost after X restart.
It's Event Manager (Control Panel -> Desktop -> Fatdog64 Event Manager) or manually in /etc/eventmanager, just like in Puppy.

Thanks.
However must be more to is since changing "MARGIN_BOTTOM" from 65 to 100, nothing happens and then at 105 jumps up and stays there till 128+

Somehow in the process one of my drives does not show anymore. I probably did something to block its appearance as all the cli tools report it and mount it OK. Where this block would be to remove it?

jamesbond wrote:Please run guess_fstype on the hfs+ partition. I tried creating an image with hfs+ and it is mounted as rw. guess_fstype on the image returns "hfsplus". If you can tell me whether or not your hfs+ is detected as "hfsplus" (output of guess_fstype from your Mac partition), then I can force it to be loaded as "rw" from initrd (and mount-helper) too.

Yes they report as "hfsplus" both in blkid and guess_fstype. However unless I "force" mount in terminal clicking on the icons just opens an empty folder.

jamesbond · #44 Post by **jamesbond** » Mon 25 Jan 2016, 16:08

mavrothal wrote: Thanks.
However must be more to is since changing "MARGIN_BOTTOM" from 65 to 100, nothing happens and then at 105 jumps up and stays there till 128+

It's because how the icon grid is calculated. Icon placements are done in a grid; the number of the cells is calculated as follows, here:

Code: Select all

	# 2. calc grid parameters	
	# exclude the margins
	windx = xwin - left - right; 
	windy = ywin - top - bottom;
	
	# number of cells
	cellx = int ( windx / xgrid )+1; # how many cells in x-coord
	celly = int ( windy / ygrid )+1; # how many cells in y-coord
	cellmax = celly * cellx; # total number of cells

The file that contains this code is /usr/sbin/fatdog-drive-icon-get_free_coord.awk

Somehow in the process one of my drives does not show anymore. I probably did something to block its appearance as all the cli tools report it and mount it OK. Where this block would be to remove it?

Try deleting the /etc/pup_save/etc/eventmanager (that deletes the eventmanager from the save layer), type "aufs_reval" in terminal, then restart X.

Yes they report as "hfsplus" both in blkid and guess_fstype. However unless I "force" mount in terminal clicking on the icons just opens an empty folder.

That's odd. You're saying, in terminal, doing a "mount -o rw /dev/sdXX /mnt/sdXX" result is an "ro" mount? You have to use "-o force,rw"? I am very reluctant to use "force" for the obvious reasons.

SFR · #45 Post by **SFR** » Mon 25 Jan 2016, 16:52

RE: HFS+

I just remembered that few months ago I created a HFS+ parition on SD card (to test something, can't even recall what was it, doesn't matter) and it was RW.
But not so long ago when I was trying to copy something there, it suddenly became RO.
Maybe it wasn't unmounted cleanly or something like that..?
I don't know if fsck.hfsplus is safe and reliable, but maybe it's worth a try (or maybe better natively under OSX).

In fact, I just recreated this by plugging the card out without unmounting it and on the next try I got:

Code: Select all

[ 6013.210071] hfsplus: Filesystem was not cleanly unmounted, running fsck.hfsplus is recommended.  mounting read-only.

Greetings!

mavrothal · #46 Post by **mavrothal** » Mon 25 Jan 2016, 20:45

jamesbond wrote:
Yes they report as "hfsplus" both in blkid and guess_fstype. However unless I "force" mount in terminal clicking on the icons just opens an empty folder.
That's odd. You're saying, in terminal, doing a "mount -o rw /dev/sdXX /mnt/sdXX" result is an "ro" mount? You have to use "-o force,rw"? I am very reluctant to use "force" for the obvious reasons.

Yes.
And one 450MB (sda2) hfsplus partition it simply can not handle. And is not because it has the OS.

Code: Select all

# blkid | grep sdd2 
/dev/sdd2: UUID="af1382ee-9a34-3b0a-ae79-2a5bb1920d9d" LABEL="OSX" TYPE="hfsplus" PARTLABEL="OSX" PARTUUID="4c13950b-cf49-46de-97c9-9579eca0ac71"
# mount -t hfsplus -o rw /dev/sdd2 /mnt/sdd2
# cat /proc/mounts | grep sdd2
/dev/sdd2 /mnt/sdd2 hfsplus ro,relatime,umask=22,uid=0,gid=0,nls=utf8 0 0
# blkid | grep sda2
/dev/sda2: UUID="456a3bf8-b3ce-3600-8edd-d33769e1be8a" LABEL="Macintosh HD" TYPE="hfsplus" PARTLABEL="Customer" PARTUUID="964d0714-2903-4849-9181-dfcca02f0cc8"
# blkid | grep sda3
/dev/sda3: UUID="14c6f485-5bf3-386d-9fc4-397ca79c0143" LABEL="Recovery HD" TYPE="hfsplus" PARTLABEL="Recovery HD" PARTUUID="8ada4883-4551-49a2-a5b5-8d9ccf5d1e97"
# mount -t hfsplus -o rw /dev/sda2 /mnt/sda2
mount-FULL: wrong fs type, bad option, bad superblock on /dev/sda2,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
# dmesg | tail
[ 1369.736241] hfsplus: invalid secondary volume header
[ 1369.736243] hfsplus: unable to find HFS+ superblock

##and after a "successful" ie ro mount kernel says
[ 1568.340517] hfsplus: write access to a journaled filesystem is not supported, use the force option at your own risk, mounting read-only.

Should point out that all partitions were checked with a couple mac utilities just before booting FD, and found ok

On a different note, booting from a USB stick while another USB stick is present and the "savefile=ram:usb:/fd64save_702.ext4" boot option, is a lotary to get to get the right USB. The init looks at the first USB found and not the one booted from or ask if more that one found.

tomhewitt · #47 Post by **tomhewitt** » Mon 25 Jan 2016, 23:47

@ JamesBond

That's funny isn't it because when Bindee points out that FD is fuzzy and doesn't display media correctly and anyone saying otherwise needs glasses then you have a cringe worthy public outburst calling him a troll followed by an embarrassing bout of public paranoia accusing everyone of being Bindee.Yet here you are now acknowledging that FD has visual problems and casting aspersions that anyone that likes a larger font or desktop needs glasses.

Either you are a dishonest two faced hypocrite or you have serious emotional health issues that you need too address.

you can't carry on with one rule for you and a different one for everyone else as that isn't fair.

smokey01 · #48 Post by **smokey01** » Tue 26 Jan 2016, 04:14

jamesbond wrote:I agree the openbox right-click menu could be made better. smokey01 actually worked out to add decorations and icons to the openbox manu so that it looks more like the panel menu, but if I recall correctly it is done by hardcoding the menus so adding/removing apps to /usr/share/applications no longer has effect.

If you would like to add icons to the Openbox right click menu, install the attached package. It seems to work fine here in FD700/701/702. Most of the credit belongs to CatDude, sfs and mobeus.

There is a way to add an additional menu system with a mouse left click but it takes some manual editing. Works pretty well though. I have mine setup to display all of the control panel apps.

jamesbond · #49 Post by **jamesbond** » Tue 26 Jan 2016, 05:19

@mavrothal - thank you for the info and tests on hfs+
It seems that the problem is caused by the limitation of Linux kernel itself.
From wikipedia: https://en.wikipedia.org/wiki/HFS_Plus#Linux
Documented in Ubuntu https://help.ubuntu.com/community/hfsplus
Last seen happening for OpenSuse user: https://forums.opensuse.org/showthread. ... n-R-W-mode

"On a different note, booting from a USB stick while another USB stick is present and the "savefile=ram:usb:/fd64save_702.ext4" boot option, is a lotary to get to get the right USB. The init looks at the first USB found and not the one booted from or ask if more that one found."

Hmmm ... if you more than one matching savefile (on different usb devices) you should be prompted on which one to use. Did you use "waitdev" to tell the kernel to wait a little bit so that all USB devices are recognised by the kernel before the search process start?

@smokey01 - thank you.

mavrothal · #50 Post by **mavrothal** » Tue 26 Jan 2016, 05:55

jamesbond wrote:"On a different note, booting from a USB stick while another USB stick is present and the "savefile=ram:usb:/fd64save_702.ext4" boot option, is a lotary to get to get the right USB. The init looks at the first USB found and not the one booted from or ask if more that one found."

Hmmm ... if you more than one matching savefile (on different usb devices) you should be prompted on which one to use. Did you use "waitdev" to tell the kernel to wait a little bit so that all USB devices are recognised by the kernel before the search process start?

Actually only one USB has the savefile and I have a 10sec wait.
A thing I noticed is that at the end of the boot process only one of the two appears on the desktop. If it is the right one you are in luck.

Not sure how relevant for this issue it may be but I'm booting from a USB loop mounting the ISO as per Ted Dog's facility.
My full grub entry is

Code: Select all

menuentry "Start Fatdog64-702rc.iso MacBook Pro" {
loopback loop0  (hd0,msdos1)/Fatdog64-702rc.iso
linux (loop0)/vmlinuz pkeys=bbig rootfstype=ramfs waitdev=10 video=displayport:2880x1800 savefile=ram:usb:/fd64save_702.ext4
initrd (loop0)/initrd
}

Regarding hfs+ and the linux kernel, "Oh well..."

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Fatdog64 702 Final [7 Feb 2016] [CLOSED]