Author |
Message |
akash_rawal
Joined: 25 Aug 2010 Posts: 232 Location: ISM Dhanbad, Jharkhand, India
|
Posted: Wed 25 Jul 2012, 06:35 Post subject:
|
|
peebee wrote: |
The following small test extracted from Frisbee funcs ... when run in check-mate V3 - Puppy latest LXDE desktop ! produces output in /opt/Pwireless-entry
Quote: | (Xdialog:9249): pup-volume-monitor-WARNING **: Module loaded successfully
0123456789 |
that contains unwanted warning from pup-volume-monitor in front of the typed password.
|
Updated to version 0.1.5
Changelog:
- Removed the debugging macro that was used to ensure that the volume monitor module was loaded
|
Back to top
|
|
 |
Jejy69

Joined: 20 Jan 2011 Posts: 710 Location: Perpignan
|
Posted: Wed 25 Jul 2012, 07:00 Post subject:
|
|
Yeah !
Frisbee works ! ! ! You're the best!
Thank you for being so quick and efficient!
Thank you Peebee too, have reacted so quickly, and found that this did not work! Bravo! "GG" !
All my derived will be able to function!
_________________ I'm Commander Shepard and this is my favorite Linux distrbution on the Citadel.
|
Back to top
|
|
 |
peebee

Joined: 21 Sep 2008 Posts: 4391 Location: Worcestershire, UK
|
Posted: Wed 25 Jul 2012, 09:04 Post subject:
|
|
akash_rawal wrote: | Updated to version 0.1.5
Changelog:
Removed the debugging macro that was used to ensure that the volume monitor module was loaded |
Very many thanks - thought it must have to be something like that....
Cheers
peebee
_________________
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
|
Back to top
|
|
 |
akash_rawal
Joined: 25 Aug 2010 Posts: 232 Location: ISM Dhanbad, Jharkhand, India
|
Posted: Thu 30 Aug 2012, 13:10 Post subject:
|
|
Updated to version 0.1.6
Changelog:
- Fixed destructor calling in client module, may fix crashing issues with seamonkey (Edit: It works)
|
Back to top
|
|
 |
Igo AtM
Joined: 16 Nov 2006 Posts: 25 Location: UK
|
Posted: Fri 07 Sep 2012, 04:53 Post subject:
Issue with latest ver 1.6 Subject description: Suspect causing segmentation faults |
|
Hi
I have been testing/using the volume monitor module since it first started appearing here and am much impressed with it as a initial implementation.
However I have recently uploaded the version 1.6 and I believe it started causing segmentation faults on my system. I have since reverted back to version 1.5 and have no issues.
being an event based issue The fault is some what difficult to pin down and is only ever reported as a simple seg fault. It would seem to occur most often when using a popup resource browser as a file system utility to a foreground app. The program will on change of browser window and subsequent save requests crash the parent window leaving no or little logged cause of the problem.
I am currently using Slacko 5.3.3 with window managers of compiz/openbox/icewm and pcfileman 1-0 and Libfm 1-0. I do not run a full gvfs as this also generated issues when run in competition with your event backend. My machine is a Dell Inspiron 1501 and puppy is run from an external usb hard drive. As I say puppy its self remains stable it is only the requesting app that crashes. Predominately Geany and Firefox but I notice these as I run the programs almost consistently.
I would like to be more specific in terms of logs of the issue but it is some what complicated in that to do so would require effectively disabling my set-up whilst using 1.6
|
Back to top
|
|
 |
Geoffrey

Joined: 30 May 2010 Posts: 2379 Location: Queensland
|
Posted: Mon 10 Sep 2012, 21:49 Post subject:
|
|
I tried the pup-volume-monitor-0.1.6 update in Saluki, as I was getting the browsers firefox and seamonkey crashing when mounting drives, but with the update gtkdialog seg faults on comboboxs so it seems.
I installed pup-volume-monitor-0.1.5 update, now gtkdialog is fine but still have the problem of browsers crashing when mounting drives, this is a random event, I can see no patten to it.
Geoffrey
_________________ Carolina: Recent Repository Additions

|
Back to top
|
|
 |
akash_rawal
Joined: 25 Aug 2010 Posts: 232 Location: ISM Dhanbad, Jharkhand, India
|
Posted: Tue 11 Sep 2012, 06:58 Post subject:
|
|
Updated to version 0.1.7
Changelog:
- Fixed 'accessing destroyed object' bug (thanks Geoffrey and Igo AtM, the problem was reproducible in saluki 023 and not in slacko 531)
|
Back to top
|
|
 |
Geoffrey

Joined: 30 May 2010 Posts: 2379 Location: Queensland
|
Posted: Tue 11 Sep 2012, 23:23 Post subject:
|
|
akash_rawal wrote: | Updated to version 0.1.7
Changelog:
- Fixed 'accessing destroyed object' bug (thanks Geoffrey and Igo AtM, the problem was reproducible in saluki 023 and not in slacko 531)
|
Thanks akash_rawal,
That seems to have fixed the problem, I'll continue to test, though I'm sure you have nailed it.
Cheers,
Geoffrey
_________________ Carolina: Recent Repository Additions

|
Back to top
|
|
 |
mavrothal

Joined: 24 Aug 2009 Posts: 3108
|
Posted: Mon 08 Oct 2012, 03:36 Post subject:
swap partitions in SDcards |
|
I can understand that may not be a very common situation (outside embedded systems), but pup-volume-monitor shows swap partitions in SDcards as mountable volumes both on the desktop and Thunar. This is the case in both Saluki and Carolina.
Also when an SDcard is inserted the swap partition shows twice both with the card name and as "mmcblk[0-9]p[0-9]". However, if the card is already in before boot, the swap partition shows only with the card name.
_________________ == Here is how to solve your Linux problems fast ==
|
Back to top
|
|
 |
akash_rawal
Joined: 25 Aug 2010 Posts: 232 Location: ISM Dhanbad, Jharkhand, India
|
Posted: Mon 08 Oct 2012, 10:36 Post subject:
|
|
Updated to version 0.1.8
Changelog:
- Fixed filtering of loop devices and swap partitions (thanks mavrothal)
|
Back to top
|
|
 |
mavrothal

Joined: 24 Aug 2009 Posts: 3108
|
Posted: Mon 08 Oct 2012, 14:02 Post subject:
|
|
akash_rawal wrote: | Updated to version 0.1.8
Changelog:
- Fixed filtering of loop devices and swap partitions (thanks mavrothal)
|
Nice!
There is one more issue with SDcards. Both the device and the partition are showing as distinct volumes. ie "mmcblk0" and "mmcblk0p[1-9]".
Also a less important issue is that if the mmcblk0 is removed and reinserted it gets the next available number up (ie mmcblk2 if an mmcblk1 exists) and not the original. Though I think this has more to do with the kernel.
Anyway some SD rules might be in order.
_________________ == Here is how to solve your Linux problems fast ==
|
Back to top
|
|
 |
akash_rawal
Joined: 25 Aug 2010 Posts: 232 Location: ISM Dhanbad, Jharkhand, India
|
Posted: Mon 08 Oct 2012, 14:44 Post subject:
|
|
mavrothal wrote: |
There is one more issue with SDcards. Both the device and the partition are showing as distinct volumes. ie "mmcblk0" and "mmcblk0p[1-9]".
|
Can you mount both of them?
And what is the output when you type blkid in terminal?
mavrothal wrote: |
Also a less important issue is that if the mmcblk0 is removed and reinserted it gets the next available number up (ie mmcblk2 if an mmcblk1 exists) and not the original. Though I think this has more to do with the kernel.
Anyway some SD rules might be in order.  |
Probably you are removing the card while it is mounted.
|
Back to top
|
|
 |
mavrothal

Joined: 24 Aug 2009 Posts: 3108
|
Posted: Mon 08 Oct 2012, 17:01 Post subject:
|
|
akash_rawal wrote: | mavrothal wrote: |
There is one more issue with SDcards. Both the device and the partition are showing as distinct volumes. ie "mmcblk0" and "mmcblk0p[1-9]".
|
Can you mount both of them?
And what is the output when you type blkid in terminal? |
They are mountable but not simultaneously.
Code: | # blkid
/dev/mmcblk2p1: LABEL="kingst" UUID="dbe90b0d-a311-45b1-966c-cb2afc1fb583" TYPE="ext3"
/dev/mmcblk2p2: UUID="919ad1d3-0d32-4153-8b48-5686f3564b67" TYPE="swap"
/dev/mmcblk2: LABEL="kingst" UUID="9bae5d56-87e5-4a40-a0e0-e4fa9a05f5dd" TYPE="ext2"
/dev/sda1: LABEL="XOpup" UUID="25055704-903d-4cb1-9c4a-74dbed3b6814" TYPE="ext3"
/dev/loop1: UUID="9c12f71f-a817-4d7f-bd54-80da2ef96f65" TYPE="ext3"
# fdisk -l /dev/mmcblk2
Disk /dev/mmcblk2: 4016 MB, 4016046080 bytes
4 heads, 16 sectors/track, 122560 cylinders, total 7843840 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6b0d4d74
Device Boot Start End Blocks Id System
/dev/mmcblk2p1 8192 7135231 3563520 83 Linux
/dev/mmcblk2p2 7135232 7839743 352256 82 Linux swap / Solaris
|
But I think that bay be something funny with the specific card. Tried a couple other cards and they were OK.
Quote: | mavrothal wrote: |
Also a less important issue is that if the mmcblk0 is removed and reinserted it gets the next available number up (ie mmcblk2 if an mmcblk1 exists) and not the original. Though I think this has more to do with the kernel.
Anyway some SD rules might be in order.  |
Probably you are removing the card while it is mounted. |
No this is not the case (and is not with "strange" card only either)
_________________ == Here is how to solve your Linux problems fast ==
|
Back to top
|
|
 |
Jubei-Mitsuyoshi
Joined: 10 Oct 2012 Posts: 2
|
Posted: Wed 10 Oct 2012, 16:19 Post subject:
|
|
Hi i would like help in porting this to an arch based distro i am working on, what do i need to do to get it to compile on a standard 86_64 posix platform ? ie Archlinux
And BTW friggin fantastic !!!!!
|
Back to top
|
|
 |
akash_rawal
Joined: 25 Aug 2010 Posts: 232 Location: ISM Dhanbad, Jharkhand, India
|
Posted: Thu 11 Oct 2012, 10:02 Post subject:
|
|
mavrothal wrote: |
They are mountable but not simultaneously.
Code: | # blkid
/dev/mmcblk2p1: LABEL="kingst" UUID="dbe90b0d-a311-45b1-966c-cb2afc1fb583" TYPE="ext3"
/dev/mmcblk2p2: UUID="919ad1d3-0d32-4153-8b48-5686f3564b67" TYPE="swap"
/dev/mmcblk2: LABEL="kingst" UUID="9bae5d56-87e5-4a40-a0e0-e4fa9a05f5dd" TYPE="ext2"
/dev/sda1: LABEL="XOpup" UUID="25055704-903d-4cb1-9c4a-74dbed3b6814" TYPE="ext3"
/dev/loop1: UUID="9c12f71f-a817-4d7f-bd54-80da2ef96f65" TYPE="ext3"
# fdisk -l /dev/mmcblk2
Disk /dev/mmcblk2: 4016 MB, 4016046080 bytes
4 heads, 16 sectors/track, 122560 cylinders, total 7843840 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6b0d4d74
Device Boot Start End Blocks Id System
/dev/mmcblk2p1 8192 7135231 3563520 83 Linux
/dev/mmcblk2p2 7135232 7839743 352256 82 Linux swap / Solaris
|
|
Looks like there's a bug in blkid or you have a really strange card which has a filesystem as well as a partition table. I will come up shortly with a program to investigate further.
|
Back to top
|
|
 |
|