On 15.11.2011 10:34, Bjørn Mork wrote:
However, this does not consider the situation when *nothing* ever calls into
the
org.freedesktop.UDisks service, a condition which is perfectly normal on any
non-desktop (or even non-gnome?) system. On such systems, udisks-daemon will
not
run. And
Michael Biebl bi...@debian.org writes:
I can't see the usability regression.
OK. I certainly don't have the full picture here, and this might be a
bug in some other part of the puzzle. If you can provide any pointers
where to look further, then I'd appreciate that.
But the observed fact on
On 15.11.2011 12:32, Bjørn Mork wrote:
Michael Biebl bi...@debian.org writes:
I can't see the usability regression.
OK. I certainly don't have the full picture here, and this might be a
bug in some other part of the puzzle. If you can provide any pointers
where to look further, then I'd
reassign 648810 udev 172-1
thanks
Michael Biebl bi...@debian.org writes:
What exactly used to work? udisks-daemon has always been started on
demand so I fail to see the regression wrt udisks.
Right. Sorry about jumping to conclusions when noticing that simply
running udisks --dump fixed my
On Nov 15, Michael Biebl bi...@debian.org wrote:
It sounds like running udisks-daemon triggers a uevent which causes udev
to probe the partition on that device.
Probably by opening the block device.
Marco, do you have maybe an idea why the partition is not correctly
probed initially?
No, but
Marco d'Itri m...@linux.it writes:
On Nov 15, Michael Biebl bi...@debian.org wrote:
It sounds like running udisks-daemon triggers a uevent which causes udev
to probe the partition on that device.
Probably by opening the block device.
Marco, do you have maybe an idea why the partition is not
On Nov 15, Bjørn Mork bj...@mork.no wrote:
OK. I'm currently running linux-image-3.1.0-1-amd64 version 3.1.1-1,
but I had this problem with the previous kernel as well
(linux-image-3.0.0-2-amd64 version 3.0.0-6). Unfortunately I am not
entirely sure when things worked the last time, as the
Marco d'Itri m...@linux.it writes:
On Nov 15, Bjørn Mork bj...@mork.no wrote:
OK. I'm currently running linux-image-3.1.0-1-amd64 version 3.1.1-1,
but I had this problem with the previous kernel as well
(linux-image-3.0.0-2-amd64 version 3.0.0-6). Unfortunately I am not
entirely sure when
8 matches
Mail list logo
