(old)Puppy Linux Discussion Forum

peebee wrote:Is there a typo at line 14 in pinstall.sh ? - fasle - should be false ??

peebee wrote:Also the puninstall.sh looks for file /etc/.eventmanager_ORIG but this file is not created by the pinstall.sh - should it be??

cp /etc/eventmanager /etc/.eventmanager_ORIG

• Mounting and unmounting made more flexible using scripts at /usr/libexec/pup-volume-monitor/
• Several multithreading bugs fixed
• Some more GIO functions implemented

• New container written from scratch permitting icon arrangement in multiple rows
• More advanced positioning options
• New label widget written from scratch that allows controlling no. of lines to be displayed.
• Performance improvements at several places
• Extra workarounds added for openbox window manager

sc0ttman wrote:I tried to compile , and I get this:

Code: Select all

  CCLD   pup-volume-monitor
pup_volume_monitor-drive-probes.o: In function `pup_volume_assert':
/root/Downloads/pup-volume-monitor-0.1.10/daemon/drive-probes.c:172: undefined reference to `blkid_new_probe_from_filename'
collect2: ld returned 1 exit status
make[2]: *** [pup-volume-monitor] Error 1
make[2]: Leaving directory `/root/Downloads/pup-volume-monitor-0.1.10/daemon'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/Downloads/pup-volume-monitor-0.1.10'
make: *** [all] Error 2

I'm using glib-2.30 if that makes a difference, not patched... Is that my problem? Will it be a problem if I get past this one above?

I'm using blkid 1.0.0 (12-Feb-2003)... I assume it's too old, or needs re-compilng etc... If so... Where are the sources? Do I need specially patched puppy sources for blkid? Is ther ea pet for blkid or do I need to update the whole e2fsprogs pkg (if that is where blkid comes from)..?

okokoook wrote:i just have little concern about the pup-volume-monitor. as instructed, i created those two scripts and left them in their corresponding directories respectively. but when i reboot, i got "not syncing, attempting to kill init" message. could anyone give me a hint on this? thank you

regards

michael

mavrothal wrote: On Pecise-5.5 desktop_drive_icons fails with GLib-GObject-WARNINGs and segfault. Does it still needs the patched glib?

mavrothal wrote: On Upup works fine but fails to update icons when a new removable is inserted. I remember this was also a problem in (the now removed) ArchPup. You need to restart pup-volume-monitor and desktop_drive_icons to see the new drives.

mavrothal wrote: Talking about restart, /etc/init.d/start-pup-volume-monitor has a typo on line 15. It should be: pup-volume-monitor-starter

akash_rawal wrote:

mavrothal wrote: On Upup works fine but fails to update icons when a new removable is inserted. I remember this was also a problem in (the now removed) ArchPup. You need to restart pup-volume-monitor and desktop_drive_icons to see the new drives.

udev events aren't reaching pup-volume-monitor. Check whether
udev is running, and udev rules file (/etc/udev/rules.d/50-pup-volume-monitor.rules) is actually used.

• Fixed persisting drive icons in gtk filechooser when daemon crashes
• Fixed incorrect signal emissions when a mounted drive is removed
• Removed the starter script pup-volume-monitor-starter. Now pup-volume-monitor-admin --start is used to start the daemon.
• Fixed event logging to log files.
• Now registers as a native volume monitor, fixes conflicts with Jemimah's glib patch. Export PUP_VOLUME_MONITOR_NO_NATIVE=1 to revert to original behavior.

• Fixed 'division by 0' error when no drives are connected

akash_rawal wrote: Source package: desktop_drive_icons-0.0.4.tar.gz

Older versions: http://www.dropbox.com/sh/k1hn0un11p395 ... rive-icons

mavrothal wrote: The desktop_drive_icons-0.0.4 link point to desktop_drive_icons-0.0.3.tar.gz.
desktop_drive_icons-0.0.4.tar.gz can be found in the "older versions"

mavrothal wrote: However, after getting it and compiling it still fails to run in Precise. Any hope there?

akash_rawal wrote: If you are referring to the same 'two different plugins' problem you need the original glib. Compile and install an appropriate version from http://ftp.gnome.org/pub/GNOME/sources/glib/

mavrothal wrote:The only problem I have is that Y offset "-40" appears to be hard coded somewhere and even if /root/.config/desktop_drive_icons/config.ini has a different value (other settings in config.ini are "respected"). It can be changed and will adjust the position of the drivers but on re-launch will be -40 again

• Fixed a typo in src/settings.c, affecting saving of X and Y offsets in config file.(Thanks mavrothal)

peebee wrote:Hi

I am using p-v-m very succesfully with lxde/pcmanfm on top of slacko5.5 and other puppies....

However I have found a difference in behaviour between version 0.1.11 and the latest 0.1.12

The difference occurs when mounting a Samba network share with Yassm.

With 0.1.11 the share appears in the bookmark area of pcmanfm on mount - see screenie attached

With 0.1.12 the mount occurs and can be accessed from pcmanfm but no bookmark appears so the share cannot be unmounted from pcmanfm

Is this a deliberate change in behaviour? Hope not.

Cheers
peebee

killall pcmanfm
export PUP_VOLUME_MONITOR_NO_NATIVE=1
pcmanfm -p LXDE --desktop &
disown

akash_rawal wrote:Looks like I didn't know GLib's default mount monitor that pup-volume-monitor-0.1.12 overrides, shows samba shares also.

Just for confirmation, does the problem disappear when you start pcmanfm with environment variable PUP_VOLUME_MONITOR_NO_NATIVE=1, like:

Code: Select all

killall pcmanfm
export PUP_VOLUME_MONITOR_NO_NATIVE=1
pcmanfm -p LXDE --desktop &
disown

If it does I'll invert environment variable control in next version.

I had done that because I noticed that with Jemimah's patch mounted drives are shown twice in file manager.

akash_rawal wrote: desktop-drive-icons updated to version 0.1.5

mavrothal wrote:

akash_rawal wrote: desktop-drive-icons updated to version 0.1.5

I do not know about version 0.1.5, but version 0.0.5 works fine

peebee wrote:

Code: Select all

killall pcmanfm
export PUP_VOLUME_MONITOR_NO_NATIVE=1
pcmanfm -p LXDE --desktop &
disown

I'll try your "experiment" when I can - might be a couple of days....

Thanks for your help and for all your work on p-v-m

Cheers
peebee

export PUP_VOLUME_MONITOR_NO_NATIVE=1 

• Inverted environment variable control over overriding native volume monitor. Now export PUP_VOLUME_MONITOR_BE_NATIVE=1 to override native volume monitor.