Severity: important The same problem also breaks GConf, apparently: as far as I can tell, GConf marks its complete database readonly until HAL is restarted and every process using GConf (and of course GConf itself) is killed. As a side effect GNOME applications cannot store any preferences until killed and some display a message declaring that the GConf database is read only when started or used.
To me this changes the severity of the bug to important, as I, and at
least two friends of mine have the same, reproducible problem but only
in this special constellation (libpam-mount + HAL).
Greetings,
--
: Sebastian Fontius : www.fsfe.org : www.fsfe.org/en/fellows/smc
`--------+----------+--------------+-----------------------------------.
[] | "They that can give up essential liberty to obtain a little |
[][][] | temporary safety deserve neither liberty nor safety." |
|| : Attributed to Benjamin Franklin, 1759 :
signature.asc
Description: Digital signature
