© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I figured that was what the hal-lock was for. During my test of mount umount sequences the hal-lock used by ubiquity did me no good either.
I just ran dbus-monitor --system on the live-cd system during a failing install. It has many of the following messages. The whole output file is attached, starting with the reflection of the monitor program starting, and the lock done by ubiquity.
signal sender=:1.5 -> dest=(null destination) path=/org/
int32 3
array [
struct {
string "volume.
boolean false
boolean false
}
struct {
string "volume.
boolean false
boolean false
}
struct {
string "volume.is_mounted"
boolean false
boolean false
}
]
signal sender=:1.5 -> dest=(null destination) path=/org/
int32 3
array [
struct {
string "volume.
boolean false
boolean false
}
struct {
string "volume.
boolean false
boolean false
}
struct {
string "volume.is_mounted"
boolean false
boolean false
}
]
signal sender=:1.5 -> dest=(null destination) path=/org/
int32 3
array [
struct {
string "volume.
boolean false
boolean false
}
struct {
string "volume.
boolean false
boolean false
}
struct {
string "volume.is_mounted"
boolean false
boolean false
}
]