You are not logged in.
I'm having trouble with udisksvm. It used to automount sd cards whenever I would put them in my reader, but now when I start it with udisksvm -a it just says system device is not managed here when ever i put in an sd card.
Last edited by syamajala (2013-11-19 03:44:58)
Offline
Is your udisksvm up-to-date (currently 2.4.1)? Is the automounting problem only with sd cards, or usb drives as well?
In any case, I would try posting in the udisksvm thread or on the github.
Offline
Hello syamajala
system device is not managed here
Since 2.3.2, udisksvm system device management is rejected; this is detected by the 'HintSystem' property of the udisks2 block device interface.
As your sd cards reader is regarded as a system device, udisksvm presently will not treat it anymore.
But I can try to look if it is possible to detect it and make an exception for it.
For that, I need the output of:
udisksctl info --block-device DEVICE
where DEVICE is the one for the sd card reader
before and after a sd card is inserted.
I need also the output of:
udisksctl status
So I could look for something specific to the reader to detect it and authorize it again.
Last edited by berbae (2013-11-17 22:15:19)
Offline
There is no entry for the sdcard reader in /dev before i insert a sd card.
Here is what I get after I insert a card.
udisksctl info --block-device /dev/mmcblk0
/org/freedesktop/UDisks2/block_devices/mmcblk0:
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice: '/'
Device: /dev/mmcblk0
DeviceNumber: 45832
Drive: '/'
HintAuto: false
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: true
HintSymbolicIconName:
HintSystem: true
Id:
IdLabel:
IdType:
IdUUID:
IdUsage:
IdVersion:
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice: /dev/mmcblk0
ReadOnly: false
Size: 32191283200
Symlinks:
org.freedesktop.UDisks2.PartitionTable:
Type: dosudisksctl info --block-device /dev/mmcblk0p1
/org/freedesktop/UDisks2/block_devices/mmcblk0p1:
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice: '/'
Device: /dev/mmcblk0p1
DeviceNumber: 45833
Drive: '/'
HintAuto: false
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: true
HintSymbolicIconName:
HintSystem: true
Id:
IdLabel:
IdType: vfat
IdUUID: 2B69-1CE3
IdUsage: filesystem
IdVersion: FAT32
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice: /dev/mmcblk0p1
ReadOnly: false
Size: 32190234624
Symlinks: /dev/disk/by-uuid/2B69-1CE3
org.freedesktop.UDisks2.Filesystem:
MountPoints:
org.freedesktop.UDisks2.Partition:
Flags: 128
IsContained: false
IsContainer: false
Name:
Number: 1
Offset: 1048576
Size: 32190234624
Table: '/org/freedesktop/UDisks2/block_devices/mmcblk0'
Type: 0x0c
UUID: udiskctl status doesn't have anything for the sdcard even when i mount it.
MODEL REVISION SERIAL DEVICE
--------------------------------------------------------------------------
WDC WD10JPVT-22A1YT0 01.01A01 WD-WXA1E42MVV50 sda
MKNSSDAT120GB-DX 504ABBF0 MKN1246A0000147218 sdb
PLDS DVD-RW DS8A8SH KU51 S45N7602Z1ZM1R004K4D sr0 Offline
udisksvm 2.4.2-1 is just released and should fix your sd card automounting problem.
I use the 'mmcblk0' device name used for multi media cards and sd cards.
Confirm the fix by posting a feedback here please.
Thanks for providing me with the needed infos to correct this bug.
Could you change the thread title to 'udisksvm no longer automounts sd cards' and add [SOLVED] to it.
Last edited by berbae (2013-11-18 15:49:07)
Offline
It is working. Thanks!
Also, I made a small change to traydvm. If you feel like taking a look. https://github.com/syamajala/udisksvm/c … 821#diff-4
Offline
Thanks Syamajala for the feedback.
I looked at the changes you made in traydvm to use the 'activate' signal of the GtkStatusIcon.
You use it to launch a file browser on the mountpoint of a device; it's an interesting suggestion you make to possibly extend the features of udisksvm.
But you should prevent multiple instances of the file browser from running concurrently after several left-clicks on the same tray icon;
and a browser instance for each device will run, though one is enough to inspect several device mountpoints, if you launch the file browser elsewhere in the DE/WM, and you know the mountpoints of the devices.
So I will not presently adopt your changes in the traydvm script; I prefer to let the user choose to launch whatever s/he wants through the DE/WM environment, rather than from the udisksvm/traydvm.
But you made me to think to use the 'activate' signal to notify the user of the state of the device: if it is mounted and where.
I will see to incorporate that in a next release.
So thanks for the suggestion.
Cheers.
Last edited by berbae (2013-11-19 22:26:20)
Offline