Author |
Message |
akash_rawal
Joined: 25 Aug 2010 Posts: 232 Location: ISM Dhanbad, Jharkhand, India
|
Posted: Tue 03 Jul 2012, 10:29 Post subject:
|
|
Jejy69 wrote: |
I do not know if you've had this bug, but I unfortunately can not delete some folders. It returns me an error message:
"Invalid cross-device link".
My Thunar is 1.4.
|
On updating thunar to 1.4 I get "Invalid argument" instead and that too only sometimes.
It can't be pup-volume-monitor bug as it does not implement any vfs.
|
Back to top
|
|
 |
Jejy69

Joined: 20 Jan 2011 Posts: 709 Location: Perpignan
|
Posted: Tue 03 Jul 2012, 10:34 Post subject:
|
|
Thank you very much for your answer! I will then move to the previous version.
_________________ I'm Commander Shepard and this is my favorite Linux distrbution on the Citadel.
|
Back to top
|
|
 |
jemimah

Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL
|
Posted: Tue 03 Jul 2012, 11:05 Post subject:
|
|
This fixed my laptop with the internal optical drive.
But on my netbook with the USB drive, I can't get the volume monitor to acknowledge the existence of sr0 at all. It doesn't show up if I run "pup-volume-monitor-admin -l". I verified that the drive works fine if I mount it by hand.
Ideas?
_________________ http://saluki-linux.com
|
Back to top
|
|
 |
akash_rawal
Joined: 25 Aug 2010 Posts: 232 Location: ISM Dhanbad, Jharkhand, India
|
Posted: Tue 03 Jul 2012, 11:27 Post subject:
|
|
jemimah wrote: |
But on my netbook with the USB drive, I can't get the volume monitor to acknowledge the existence of sr0 at all. It doesn't show up if I run "pup-volume-monitor-admin -l". I verified that the drive works fine if I mount it by hand.
|
What is the output of udevadm monitor when you plug in the drive?
|
Back to top
|
|
 |
jemimah

Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL
|
Posted: Tue 03 Jul 2012, 11:51 Post subject:
|
|
Code: | # udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[1341316280.050720] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3 (usb)
KERNEL[1341316280.053092] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0 (usb)
KERNEL[1341316280.053629] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3 (scsi)
KERNEL[1341316280.054045] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/scsi_host/host3 (scsi_host)
KERNEL[1341316280.056948] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/usb_device/usbdev1.5 (usb_device)
UDEV [1341316280.074994] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3 (usb)
UDEV [1341316280.091578] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/usb_device/usbdev1.5 (usb_device)
UDEV [1341316280.204800] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0 (usb)
UDEV [1341316280.215018] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3 (scsi)
UDEV [1341316280.225889] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/scsi_host/host3 (scsi_host)
KERNEL[1341316281.063576] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0 (scsi)
KERNEL[1341316281.064294] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0/3:0:0:0 (scsi)
UDEV [1341316281.082122] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0 (scsi)
KERNEL[1341316281.172254] add /devices/virtual/bdi/11:0 (bdi)
KERNEL[1341316281.177409] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0/3:0:0:0/block/sr0 (block)
KERNEL[1341316281.177638] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0/3:0:0:0/scsi_device/3:0:0:0 (scsi_device)
KERNEL[1341316281.177851] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0/3:0:0:0/bsg/3:0:0:0 (bsg)
UDEV [1341316281.186419] add /devices/virtual/bdi/11:0 (bdi)
KERNEL[1341316281.191525] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0/3:0:0:0/block/sr0 (block)
UDEV [1341316281.229634] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0/3:0:0:0 (scsi)
UDEV [1341316281.247390] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0/3:0:0:0/scsi_device/3:0:0:0 (scsi_device)
UDEV [1341316281.269651] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0/3:0:0:0/bsg/3:0:0:0 (bsg)
UDEV [1341316281.324799] add /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0/3:0:0:0/block/sr0 (block)
UDEV [1341316281.335682] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0/3:0:0:0/block/sr0 (block)
KERNEL[1341316290.987391] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0/3:0:0:0/block/sr0 (block)
UDEV [1341316291.000075] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/target3:0:0/3:0:0:0/block/sr0 (block) |
_________________ http://saluki-linux.com
|
Back to top
|
|
 |
akash_rawal
Joined: 25 Aug 2010 Posts: 232 Location: ISM Dhanbad, Jharkhand, India
|
Posted: Tue 03 Jul 2012, 13:18 Post subject:
|
|
The output is similar to one I get when I plug in my usb modem which also behaves like an optical drive. Yet when I plug it in, it is detected by the volume monitor and shown.
All I can guess is that /etc/udev/rules.d/50-pup-volume-monitor.rules could have gone missing. Don't know how it happens it has happened to me several times while working with autotools.
|
Back to top
|
|
 |
jemimah

Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL
|
Posted: Tue 03 Jul 2012, 14:40 Post subject:
|
|
Udev events from other drives make it through - I can see them with pup-volume-monitor-admin -e.
I've attached the udevd debug log.
Description |
|

Download |
Filename |
udevdebug.gz |
Filesize |
4.84 KB |
Downloaded |
758 Time(s) |
_________________ http://saluki-linux.com
|
Back to top
|
|
 |
jemimah

Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL
|
Posted: Tue 03 Jul 2012, 19:08 Post subject:
|
|
It's definitely a packaging problem of some sort. I booted a fresh install on my development machine and it doesn't work with the internal drive there either.
I'll try to figure out what's missing.
_________________ http://saluki-linux.com
|
Back to top
|
|
 |
akash_rawal
Joined: 25 Aug 2010 Posts: 232 Location: ISM Dhanbad, Jharkhand, India
|
Posted: Wed 04 Jul 2012, 10:39 Post subject:
|
|
Udev events are as expected. But what maybe going wrong is totally unexpected.
I am attaching modified plugins/cdrom.c with debugging code added wherever necessary. Hope it will help with debugging.
Description |
.gz extension is fake, rename it to cdrom.c, replace plugins/cdrom.c with it and recompile.
|

Download |
Filename |
cdrom.c.gz |
Filesize |
13.68 KB |
Downloaded |
742 Time(s) |
|
Back to top
|
|
 |
jemimah

Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL
|
Posted: Thu 05 Jul 2012, 14:24 Post subject:
|
|
I'm not seeing the additional debugging output even on the working system. Strange - can't figure out why that would be.
_________________ http://saluki-linux.com
|
Back to top
|
|
 |
jemimah

Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL
|
Posted: Thu 05 Jul 2012, 14:52 Post subject:
|
|
I changed the g_degugs to printfs and now I can see output on the working system.
On the nonworking system I get this:
# pup-volume-monitor
Code: | pup-volume-monitor-Message: Config file for plugin libcdrom not found, it will use default settings
(pup-volume-monitor:15730): GModule-CRITICAL **: g_module_symbol: assertion `module != NULL' failed |
What's happening here?
_________________ http://saluki-linux.com
|
Back to top
|
|
 |
jemimah

Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL
|
Posted: Fri 06 Jul 2012, 10:56 Post subject:
|
|
Ok I think I figured it out. The existence of /usr/lib/pup-volume-monitor/libcdrom.a and/or /usr/lib/pup-volume-monitor/libcdrom.la seems to be crashing it.
_________________ http://saluki-linux.com
|
Back to top
|
|
 |
akash_rawal
Joined: 25 Aug 2010 Posts: 232 Location: ISM Dhanbad, Jharkhand, India
|
Posted: Fri 06 Jul 2012, 11:06 Post subject:
|
|
Surely cdrom plugin failed to load with some error.
I agree there's a bug ahead leading to a call to g_module_symbol() even after plugin failed to load, but it should have shown the plugin path...
Code: |
// libpupvm/pupvm-settings.c:117
gboolean pup_vm_plugin_load(GTypeModule *module)
{
PupVMPlugin *self = PUP_VM_PLUGIN(module);
g_return_val_if_fail(self->plugin_name && self->plugin_path, FALSE);
self->module = g_module_open(self->plugin_path, 0);
if (!self->module)
{
g_debug("Module path: %s", self->plugin_path);
}
if (module && (! self->initialised))
{ ...
|
Edit: I didn't notice g_module_error() earlier. I improved pup_vm_plugin_load() error output and fixed that bug. This will not cause plugin to load correctly but we'd come to know why plugin failed to load.
libpupvm/pupvm-settings.c:117
Code: |
gboolean pup_vm_plugin_load(GTypeModule *module)
{
PupVMPlugin *self = PUP_VM_PLUGIN(module);
g_return_val_if_fail(self->plugin_name && self->plugin_path, FALSE);
self->module = g_module_open(self->plugin_path, 0);
if (!self->module)
{
//g_debug("Module path: %s", self->plugin_path);
g_critical("Plugin %s (path: %s) failed to open: %s",
self->plugin_name, self->plugin_path, g_module_error());
}
if (self->module && (! self->initialised))
{
//Load plugin's config
self->cfg_file = g_key_file_new();
pup_load_cfg_file(self->cfg_file, self->plugin_name);
//Run the plugin's init func
PupVMPluginInit plugin_init_func;
if (g_module_symbol(self->module, "pup_vm_plugin_init",
(gpointer *) &plugin_init_func))
{
plugin_init_func(self);
}
self->initialised = TRUE;
}
if (module) return TRUE;
else return FALSE;
}
|
|
Back to top
|
|
 |
akash_rawal
Joined: 25 Aug 2010 Posts: 232 Location: ISM Dhanbad, Jharkhand, India
|
Posted: Fri 06 Jul 2012, 14:25 Post subject:
|
|
jemimah wrote: | Ok I think I figured it out. The existence of /usr/lib/pup-volume-monitor/libcdrom.a and/or /usr/lib/pup-volume-monitor/libcdrom.la seems to be crashing it. |
Updated to version 0.1.4
Changelog:
- Now static libraries are filtered out while loading plugins
- A few minor bug-fixes
|
Back to top
|
|
 |
peebee

Joined: 21 Sep 2008 Posts: 3253 Location: Worcestershire, UK
|
Posted: Wed 25 Jul 2012, 04:05 Post subject:
|
|
Hi akash_rawal
The following small test extracted from Frisbee funcs:
Code: | #!/bin/bash
MSG="Please enter the Password."
Xdialog --title "Frisbee" --password --inputbox "$MSG" 0 0 > /opt/Pwireless-entry 2>&1 |
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.
Any ideas why this is happening - and how to stop the warning text being produced please? It is stopping Frisbee working correctly on check-mate.
Thanks
PeeBee
_________________
LxPup = Puppy + LXDE
|
Back to top
|
|
 |
|