Page 5 of 9
Posted: Mon 19 Nov 2012, 01:12
by MinHundHettePerro
Hello
!
Latest PVM & DDI for slacko, in slacko 5.3 (RC2, 5.2.97 actually, though it shouldn't matter).
I have 19 internal partitions, which means that - on my 1280x1024 screen - quite a few of them are way out to the right of the wieving area.
Adding another partition, say sr0, gives a "Floating point exception" in DDI, which crashes.
Recompiling DDI so as to stay within my horizontal screen estate (shrinking icon-size, inter-icon padding etc.) makes DDI work - until the horizontal right is passed; resulting in a "Floating point exception".
Strangely, in vertical view, although a lot of the icons are well below the lower screen limit - there are no crashes of DDI.
In both horizontal and vertical view, DDI can be started with "too many partitions", while removing one, USB or sr0, results in the same DDI crash of "Floating point exception" in horizontal view only.
A bit more serious, though, is that when plugging in a USB-stick, say sdd, partitions are shown (sdd1, sdd2 etc), as well as, the MBR-block sdd.
PVM actually offers to mount (and save to, at least in FF) the MBR-block of USB flash-devices (not for USB HDDs, though).
Perhaps a multi-row table for drive icons
.
I would like to also see my FDD in PVM/DDI
.
Craps, a lot of critisism
- but, I wouldn't have bothered if I didn't have high hopes for PVM/DDI
.
Cheers
/ MHHP
Posted: Sun 25 Nov 2012, 21:12
by 01micko
Hello akash_rawal
I have built a compiz sfs for the new slacko (when released) and it will be based around lxpanel and pcmanfm. I installed your slacko-1.10 pet on the first page and it seems to run well.
Thanks for a great job!
Posted: Tue 27 Nov 2012, 02:57
by technosaurus
mavrothal wrote:Tried to see into icon.c and icon-view.c (so I will not only ask
) but my C is less than rudimentary.
(BTW I find that developing in git/cvs is very educational for others since it allows them to see the logic and the code changes. Eventually this may pay off
)
its much nicer than gtk's builtin iconview, the made it nearly impossible to set the gtk version's background image let alone transparency - kudos
Posted: Fri 30 Nov 2012, 05:18
by okokoook
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
Posted: Fri 30 Nov 2012, 11:02
by gmahuaer
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
Hi, michael,
Your sysytem might get other troubles. My test is ok (v789)， but Chinese characters in file-name are garbled when I inserted a USB disk with vfat FileSystem.
Posted: Tue 18 Dec 2012, 11:08
by simargl
removed
Posted: Sat 29 Dec 2012, 05:27
by tenochslb
Is it just me or the source tar contains nothing to extracr?
Posted: Sun 30 Dec 2012, 15:05
by Geoffrey
tenochslb wrote:Is it just me or the source tar contains nothing to extracr?
It appears fine to me, I assume you are referring to pup-volume-monitor-0.1.10.tar.gz
it contains
Code: Select all
aclocal.m4 config.h.in daemon ltmain.sh missing
admin config.sub depcomp m4 module
compile configure install-sh Makefile.am plugins
config.guess configure.ac libpupvm Makefile.in tester
Posted: Wed 27 Mar 2013, 15:35
by sc0ttman
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)..?
If the problem is not with blkid, why can't I compile this?
Or maybe there is a pet for wary 51x somewhere? That should work for me... I already tried the latest version from the Carolina repo, but I did not get any drives listed in thunar, I only got these errors(?) in the terminal:
Code: Select all
# pup-volume-monitor-starter
/usr/bin/pup-volume-monitor-starter: line 7: 26836 Trace/breakpoint trap pup-volume-monitor-admin --list-all &>/dev/null
Re: Precise pet
Posted: Thu 28 Mar 2013, 19:57
by peebee
mavrothal wrote:Edit Version 0.1.10-1has different defaults and a better pinstall script
Hi Mav
Was looking inside the Precise pet......
Is there a typo at line 14 in pinstall.sh ? - fasle - should be false ??
Also the puninstall.sh looks for file /etc/.eventmanager_ORIG but this file is not created by the pinstall.sh - should it be??
Cheers
peebee
Posted: Mon 01 Apr 2013, 15:11
by mavrothal
peebee wrote:Is there a typo at line 14 in pinstall.sh ? - fasle - should be false ??
Corrected in
version 0.1.10-2. Thanks
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??
but it does. Line 3 has
Code: Select all
cp /etc/eventmanager /etc/.eventmanager_ORIG
Posted: Wed 03 Apr 2013, 16:39
by akash_rawal
Very sorry for replying late. I had been preparing for my board exams, performance in which can form (or deform) my future.
I still have engineering entrances left, but since I have already went through syllabus I decide to resume the development.
I may not be quick to respond now, as I have to study as well.
Posted: Wed 03 Apr 2013, 16:58
by akash_rawal
pup-volume-monitor updated to version 0.1.11
Changes:
- Mounting and unmounting made more flexible using scripts at /usr/libexec/pup-volume-monitor/
- Several multithreading bugs fixed
- Some more GIO functions implemented
desktop-drive-icons updated to version 0.0.3
Changes:
- 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
Posted: Wed 03 Apr 2013, 17:09
by akash_rawal
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)..?
blkid is too old. That must be the problem.
The lowest puppy version I tested, lucid puppy 511, has blkid 2.17.0.
blkid is in util-linux package,
https://www.kernel.org/pub/linux/utils/util-linux/
Posted: Wed 03 Apr 2013, 17:12
by akash_rawal
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
At which state does it happen exactly? And which puppy?
Posted: Wed 03 Apr 2013, 18:20
by mavrothal
Hi Akash
nice to have you back.
Tries your pup-volume-monitor-0.1.11-i686-precise.pet/desktop_drive_icons-0.0.3-0-i686-precise5.4.0.90.pet in Precise-5.5 and
Upup Precise 3.8.3.1
On Pecise-5.5 desktop_drive_icons fails with GLib-GObject-WARNINGs and segfault. Does it still needs the patched glib?
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.
Talking about restart, /etc/init.d/start-pup-volume-monitor has a typo on line 15. It should be: pup-volume-monitor-start
er
Posted: Wed 03 Apr 2013, 19:00
by akash_rawal
mavrothal wrote:
On Pecise-5.5 desktop_drive_icons fails with GLib-GObject-WARNINGs and segfault. Does it still needs the patched glib?
It's not exactly patched glib you need. The original glib source code doesn't have that bug. It has nothing to do with Jemimah's patch.
The guys who compile glib package are using some modified source on which I couldn't yet get my hands on.
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.
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
Oh yes it is.
I have fixed the precise pet.
Posted: Thu 04 Apr 2013, 04:38
by mavrothal
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.
Right.
Trying to get rid of the last pup_even drive icon, I had actually inactivated hotplug support in eventmanager, that also kills udevd
Posted: Tue 16 Apr 2013, 17:10
by akash_rawal
pup-volume-monitor updated to 0.1.12
Changes:
- 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.
desktop-drive-icons updated to 0.0.4
Changes:
- Fixed 'division by 0' error when no drives are connected
Re: Desktop-drive-icons
Posted: Tue 16 Apr 2013, 19:05
by mavrothal
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"
However, after getting it and compiling it still fails to run in Precise. Any hope there?