(In reply to comment #21)
> What is the status here? Sister bug http://bugs.gentoo.org/338185 has been
> open
> for too long.
It's not really something I'm planning to spend time on in udisks since
a) I'm focusing on udisks2; and b) floppies are extremely rare nowadays.
> Is this still a proble
(In reply to comment #22)
> I doubt it's a problem with udisks2.. in fact, last I checked, all the parts
> in
> the stack (kernel, udisks2, gvfs, nautilus) worked fine with floppies, see
>
> http://people.freedesktop.org/~david/palimpsest-gvfs-udisks2-pc-floppy.png
>
> But it's not something I
(Sorry for being slow. Will post feedback soon.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281588
Title:
Disk standby timer is broken
To manage notifications about this bug go to:
https://bugs
I'll take a look.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281588
Title:
Disk standby timer is broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/udisks/+bug/1281
Hi, sorry for the lack of updates. Nothing special, just been busy with
work, I'm still planning on adding the SYNCHRONIZE CACHE command.
Hopefully I'll get to look at it soon. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
The reason that
$ udisks --detach /dev/sdX
spins down the disk properly but clicking the "Power off" menu item in
the GNOME Disks application doesn't has to do with the fact that the
udisks program is from udisks version 1 and was rewritten in udisks
version 2.
udisks v1: http://cgit.freedeskto
OK, I just made that change
http://cgit.freedesktop.org/udisks/commit/?id=fcdd8f48b6ac9b1b6da82fdf5f59230fc2ea6feb
and tested it with a couple of different units. Notes
- One of my devices (bus-powered) does not accept the START STOP UNIT
command so we just continue if it fails. That is, thi
> command “sg_start --stop /dev/sdX” really spin-downs my drive (sometimes
> on 2nd or 3rd attempt - I don’t know why), device remains in system and
> spin-up again only on my demand.
Btw, this is because the sg_start command opens the device node with
O_RDWR which causes an uevent 'change' event
Thanks for testing. I'll look into making udisks2 sending SYNCHRONIZE
CACHE and START/STOP UNIT commands. Stay tuned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239087
Title:
Safely remove is no
Hey, thanks for testing the patches.
(In reply to comment #10)
> 1.2. WD - 'Safely remove drive' option in Nautilus spinned-down it,
> gnome-disks 'Power off the drive' and 'udisksctl power-off -b /dev/sdX'
> works too.
> But there is a little difference - if I enable automount
I have an idea of
OK, I'm interested in output of /var/log/messages when it doesn't work
with the WD. Or is that what you posted in comment 15?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239087
Title:
Safely remo
(Hmm, the drives have
can_stop=1
start_stop_type=shutdown
so everything should be good. My guess is that it's the NTFS partition
that is the culprit. Specifically, unmounting it via udisks somehow
fails.)
If you manually unmount the partitions, does powering down the drive
wo
Let me see if I understand this correctly:
1. Manually unmount, then power-off via the Disks GUI works as expected.
2. The "safely remove drive" button in Nautilus does not work as expected.
Is that about right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
(In reply to comment #22)
> I have 500Gb of data on my NTFS partition, so I do not want to reformat my
> HDD. I'm sorry for this.
Fair enough. I'll try to see if I can repro on my hardware.
> If there are no other differences - please add SYNCHRONIZE CACHE, I'm ready
> to do a test and report bac
(In reply to comment #20)
> >OK, I'm interested in output of /var/log/messages when it doesn't work with
> >the WD. Or is that what you posted in comment 15?
> I tested it again - the log in comment 15 represent both situations - when
> drive spinned-down and when it does not. Only timestamps diff
Hi, finally got around to making udisks also send the SYNCHRONIZE CACHE
command. Please check if it works. The patch is on master and here:
http://cgit.freedesktop.org/udisks/commit/?id=429892f2ec39d66732bee0f78d093eb6d2c5433f
Thanks!
--
You received this bug notification because you are a memb
(In reply to comment #1)
> As for the /media -> /run/media change, I presume this was done to avoid
> having
> to clean up stale mount point directories after reboot?
Well, yeah, kinda - the idea is that such temporary mounts really are
non-persistent => they belong somewhere in /run instead of a
The motivation for moving out of /media was that with /media any user
can access the filesystem that your user mounts. Which obviously is
highly undesirable on multi-user systems. Originally we wanted to use
$XDG_USER_RUNTIME_DIR and for a while we did that, see
http://cgit.freedesktop.org/udisks/
(For the second commit link I ofcourse meant
http://cgit.freedesktop.org/udisks/commit/?id=aa02e5fc53efdeaf66047d2ad437ed543178965b
instead. Sorry for the confusion.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
No. What the FHS says about removable media is not in any way useful (it
was written a long time ago too, last revision is 2004). And using big
words like "violate" or "mandate" is not going to change any of that,
sorry. You really should know better...
--
You received this bug notification becau
You got it somewhat wrong
- udisks does not provide any UI => it's not the right place to report this bug
- there was some confusion in the UI between "Eject" and "Safely Remove Drive"
-> the feature was deemed confusing and removed from the UI
- the feature will be back in the upcoming udisks
OK, long time without an update. In the mean time development focus has
been udisks 2.0 which is a completely different codebase where floppy
disks actually work. Since udisks 2.0 has been shipping in distros since
the spring, I'm not really interested in fixing this for udisks 1.x. So
I'm closing
In udisks 2.0 this is now handled by libblkid through invocation from
udev so I'm closing this NOTOURBUG.
That said, if you don't mind, please test if it's the problem also
exists with that codebase (it's completely different from udisks-part-
id). Thanks!
--
You received this bug notification b
With udisks 2.0 this is no longer a problem I think. Closing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/476654
Title:
CD eject but not unmount when using drive button and CD is in fstab
To mana
udisks is not setting the default_permissions option. I think this is a
problem with ntfs-3g or whatever ntfs filesystem driver you are using.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/482641
Titl
For udisks 2.0 we don't do LVM stuff any more and we even changed the
default to off in the udisks1 branch and the udisks 1.0.4 release for
these reasons
http://cgit.freedesktop.org/udisks/commit/?h=udisks1&id=99de237eed6a026597e9b045527631c42ab86968
Closing as WONTFIX as there are no immediate p
(In reply to comment #9)
> Previously users could use UDISKS_DISABLE_POLLING to inhibit SMART data
> updates
> for hard drives which had a longer spindown timeout than the SMART polling
> interval (which seems to be 10 minutes). Is there a new mechanism to disable
> SMART data updates by device?
(In reply to comment #7)
> Support for the UDISKS_DISABLE_POLLING property was lost in udisks2.
udisks2 is not concerned with polling at all, we moved that into the
kernel (where it belongs). The default udev rules will enable polling.
--
You received this bug notification because you are a memb
(In reply to comment #27)
> Tagging this as WORKFORME is not acceptable and simply not true.
> Ubuntu 10.04 is LTS and use this non working version of udisk.
> 12.04 is LTS too and also use this piece of crap that is the last 1.x
> version.
>
> Some might consider beyond them as to why some peop
(In reply to comment #30)
> Perhaps it should be resolved as WONTFIX rather than WORKSFORME in that case?
If the issue wasn't fixed in 2.x and it's not an issue that I wanted to
fix I would have closed it WONTFIX. If the issue was fixed in response
to the bug, I'd close it with resolution FIXED. B
30 matches
Mail list logo
