This bug was fixed in the package checkbox - 0.13.1
---
checkbox (0.13.1) precise; urgency=low
New upstream release (LP: #925090):
[Brendan Donegan]
* Fixed the cpu_topology script so that it doesn't mistake the word
'processor' in the value of another field for the field '
** Branch linked: lp:~roadmr/ubuntu/precise/checkbox/0.13.1-retry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912522
Title:
usb_test fails on non-writable filesystems
To manage notifications abou
** Changed in: checkbox
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912522
Title:
usb_test fails on non-writable filesystems
To manage notifications a
** Changed in: checkbox (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912522
Title:
usb_test fails on non-writable filesystems
To manage notificatio
** Branch linked: lp:~roadmr/ubuntu/precise/checkbox/0.13.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912522
Title:
usb_test fails on non-writable filesystems
To manage notifications about this
** Branch unlinked: lp:~roadmr/ubuntu/precise/checkbox/0.13.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912522
Title:
usb_test fails on non-writable filesystems
To manage notifications about th
** Branch linked: lp:~roadmr/ubuntu/precise/checkbox/0.13.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912522
Title:
usb_test fails on non-writable filesystems
To manage notifications about this
On 01/21/2012 12:53 PM, Brendan Donegan wrote:
> Jeff,
>
> Have you tried using the 'DeviceIsReadOnly' property of
> org.freedesktop.UDisks.Device? That might be a straightforward way of
> telling if a partition is read-only.
>
Was looking at that the other day, but haven't tried it just yet...
T
Jeff,
Have you tried using the 'DeviceIsReadOnly' property of
org.freedesktop.UDisks.Device? That might be a straightforward way of
telling if a partition is read-only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Yeah, that would have triggered the bug since the live USB would be
mounted read-only.
I actually tested this initially using my stick mentioned above with one
of the partitions remounted read-only, so I had one mounted read-write,
one read-only and one read-write but no read permissions for non-r
As fare as i remember all i did was run the test from a live USB,
posibly the reason was that the drive was filled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912522
Title:
usb_test fails on non-
So if it encounters a usb device with say... 3 partitions and two of
those partitions are not writable and one IS, it will complete testing
ALL partitions, then fail overall by saying "Completed X iterations of
testing, but there were errors."
And the script output will tell you which partitions f
I'm not sure I quite understand. With the changes you made, does the
test still fail if it has any writable partitions? In my opinion it
shouldn't - it just makes things confusing for the tester. As Daniel
mentioned before, a good idea might be to test reading at a minimum for
read-only partitions.
Well, now the test doesn't fail at all... well it does. I've modified
the script to behave better, Instead of a nasty traceback, all you get
is an overall fail of the test and output that tells you which partition
failed. I tried in on my own systems with 2 usb keys:
1: Common use case, 8GB USB
** Branch linked: lp:~bladernr/checkbox/fix-usb-firewire-tests
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912522
Title:
usb_test fails on non-writable filesystems
To manage notifications about t
>I'd rather lose whats on my laptops HDD than what I have stored on USB disks.
Your not every one :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912522
Title:
usb_test fails on non-writable filesy
Hi!
Well, maybe the description should be changed from "test fails" to "test
fails with a nasty trace" :)
I agree that it we can't write, then we can't write, and just changing
this so that the test exits gracefully with "no writable partitions on
the device" would be quite acceptable.
However,
I'm recreating this and wondering just how big a case this is... I
think the best solution is brendan's, just write to what's writeable...
plus I think I'll add to the description suggesting that usb keys are
used in preference over usb HDDs.
I'm just concerned, given the comments here, that some
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: checkbox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912522
Title:
us
Hi François,
the usb/disk_detect test checks if the partitions are mounted (usb_test
-l).
usb_test -t is used by usb/storage_transfer, and although the purpose is
a bit vague ("This test will check your USB connection."), as Brendan
mentions, we want to test that the drive can be written to witho
We want to check the USB subsystem is working properly. Just mounting a
partition is not really good enough (would you test Wifi by just
checking that it pairs with an access point?). I would suggest that we
should try to write to every partition which is writable, and just
ignore the ones that are
"The test needs to verify that the drive is writable, so if I can't
write to it, it should still fail, but do so in a graceful manner."
Are you sure ? What is this test supposed to do ? I thought it was just
to check if Ubuntu can mount a partition from a USB stick/harddrive. Why
should it necessa
Note that this was verified too with the new usb_test from checkbox
trunk (r1160), so this complements bug 887049 that happened on a USB
stick with multiple partitions, some of which were unwritable.
I took the liberty of subscribing François as he was also experiencing
this problem.
** Also affe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912522
Title:
usb_test fails on non-writable filesystems
To manage notifications about this bug go to:
https://bugs.launchpad.net/checkbox/+bug/912522/+
24 matches
Mail list logo
