well, it seems quite a big bug to me as well. Isn't it enough to have shipped
Dapper with issues like this untouched?
it seems to affect a lot of people.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
i agree with willie: this kind of bug should have been fixed before
releasing something that you call production ready. in a real
environment i think there are many cases of file-serving through samba
and not being able to automount the share is quite a severe bug in my
opinion.
--
auto smbfs
Public bug report changed:
https://launchpad.net/malone/bugs/34886
Comment:
i'm not really happy with this: you should leave the possibility for
advanced users to customize this behaviour.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Public bug report changed:
https://launchpad.net/malone/bugs/34886
Comment:
testing it: this new behaviour is really crap, it's not flexible at all.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Public bug report changed:
https://launchpad.net/malone/bugs/34886
Comment:
thanks for the advice martin, but i have absolutely no idea about how to write
hal policies, in my opinion it is a bit too complex even for a skilled user, i
really do not understand the reason they chaged it, gconf was
Public bug reported:
https://launchpad.net/malone/bugs/34894
Affects: gnome-vfs2 (Ubuntu)
Severity: Normal
Priority: (none set)
Status: Unconfirmed
Description:
since new upgrade all mounted partition are shown in mount disk applet,
desktop and Places. On a system with
