http://www.freedesktop.org/wiki/Software/hal/
** Changed in: hal (Ubuntu)
Status: Incomplete => Invalid
** Changed in: baltix
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https:/
** Changed in: nautilus
Status: Invalid => Unknown
** Changed in: nautilus
Importance: Unknown => Critical
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://bugs.launchpad.net/bugs/44874
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thank you for reporting this bug.
Does this occur in Lucid?
** Changed in: hal (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: baltix
Status: New => Incomplete
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://bugs.launchpad.net/bugs/44874
You received th
** Changed in: hal (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://bugs.launchpad.net/bugs/44874
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bug
>From GNOME upstream:
"It seems from the Ubuntu report that this is a HAL bug and not a Nautilus one,
so closing NOTGNOME. Thanks for the report, please feel free to report any
other bugs you find.
"
** Changed in: hal (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
auto smbfs mo
** Changed in: nautilus
Status: New => Invalid
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://bugs.launchpad.net/bugs/44874
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bug
replacing "smbfs" with "cifs" in fstab seemed to help for me. Long
waits at boot time went away and the filesystem seems available.
Manually mounting the filesystem every boot wasn't an option, because
servers are supposed to be available automagically. (Dapper under
VMWare)
--
auto smbfs mount
...and I have also noticed that it affects both cifs and smbfs.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://bugs.launchpad.net/bugs/44874
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I think it might be worth adding something I have noticed: the bug is
more of a problem for shares where there are a large number of
files/directories present.
I am generally able to boot successfully if I only attach to "small"
shares (those with few files/folders in the root) but experience the
Hi,
Thanks for all the advise, this HAL problem happened on my old pc ages ago and
being lazy and busy i've used the wireless laptop for a while.. until now..
anyway. Got the shares working thru cifs but had a few issues so i thought
why didn't this error happen on the laptop ? hmmm, so i put
according to this thread:
http://www.ubuntuforums.org/showthread.php?p=1660934#post1660934
the hal error happens when mounting by ip address. if you enable wins
support and mount with netbios name '//netbiosname/share', the hal error
goes away.
--
auto smbfs mount in /etc/fstab causes hald hang
May I link to my bug report Bug#62607, which addresses some issues I
have with cifs. Perhaps some other cifs users can confirm it.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
I think it's largely ignored because as people have suggested, if you
use cifs instead of smbfs it works, without stalling.
>From what I know cifs is the replacement for smbfs. (from man
mount.cifs: The CIFS protocol is the successor to the SMB protocol)
It's installed when you install smbfs.
I h
[edit]
forgot to mention in reference to my fstab and permissions my shares
are all passwordless and I want anonymous r/w - hence why everythings
777.
--
O)-c
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
ubuntu-bugs mailing list
ubuntu-bugs@li
This sucks. Why does nobody take care of it? It just can't be that an
operating system aiming at taking market share away from Microsoft (Bug
#1) COMPLETELY STALLS if a network share is unavailable.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
u
** Changed in: nautilus (upstream)
Status: Unknown => Unconfirmed
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Bug watch added: GNOME Bug Tracker #361541
http://bugzilla.gnome.org/show_bug.cgi?id=361541
** Also affects: nautilus (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=361541
Importance: Unknown
Status: Unknown
--
auto smbfs mount in /etc/fstab causes hald hang at boot
I'm experiencing a problem maybe related to this, but with nfs-shares
(running up-to-date dapper):
/etc/fstab-entry:
zweistein:/home /home nfs auto,nolock,tcp 0 0
This share get's mounted successfully at boot, but it doesn't show up
neither in /etc/mtab nor running 'mount
Same here. When the samba share is auto mounted in /etc/fstab, HAL fails to
initialise, the desktop is stalled for a couple of minutes. Then the desktop
appears, and the samba share gets mounted. When doing lshal immediately in a
terminal I got a message saying that HAL could not be connected to
** Also affects: Baltix
Importance: Untriaged
Status: Unconfirmed
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'm also experiencing this issue. Changing the mounts to cifs has
alleviated the symptom of a hanging hald on startup.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/m
I don't think this is a bug in smbfs. Since I upgraded to Dapper, my
cifs (i.e. not smbfs) mount in /etc/fstab hasn't been working on boot.
There weren't any obvious problems, no errors from the kernel, and no
hangups*, so I was a bit puzzled but didn't get around to investigating
it. The share doe
I want to clarify and give credit where it is due; the full workaround
using rc.local was proposed by mambro and then further detailed for us
less skilled users by Mr. Jayme.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
ubuntu-bugs mailing list
I just (mid August '06) auto-upgraded to Dapper from Breezy.
I encountered the same problem on reboot.
The workaround provided by Nathaniel B. Jayme above worked for me.
This is a serious problem for anyone upgrading from Breezy to Dapper
with smbfs mounts in their fstab. Please fix!
Successful
One month later and still no solution, or at least, not a permanent one.
I have this same annoying bug ("Failed to initialize HAL" after adding
smbfs share to /etc/fstab), however only when I boot with kernel
2.6.15-26-386. Booting with a previous version of the kernel,
2.6.15-23-386, everything is
To me this solution partially helped:
sudo apt-get remove --purge hal dbus
I really don't need neither hal, nor dbus. But I need the samba shares
to be automatically mounted at boot time.
It *partially* works means that sometimes it mounts all samba shares,
sometimes it skips some mounts. So it'
The noauto/mount in rc.local does work, and that is how I am currently
working around the issue.
However, this is a workaround and NOT a solution. There is no reason
mounting network shares in fstab should not work, and it worked fine in
Breezy. Upgrading from Breezy gives the impression that Dapp
hello,
i encountered this experience with placing auto mountable smbfs in
/etc/fstab
if this is the case try the solution:
1) place a noauto option in your /etc/fstab smbfs entry
2) mount network shares using /etc/rc.local
if your network share is to be mounted to /mnt/shared then within /etc/r
anybody tried using the _netdev option in fstab that may work ;)
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Bug 46931 has been marked a duplicate of this bug
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
some more info:
After hanging on hald, and hanging on entering the desktop, the mount doesn't
work.
every time i do
ifdown eth0; ifup eth0
or mount /mymount
I find following message in my dmesg
Jun 13 21:44:17 localhost kernel: [4296366.388000] smb_lookup: find //DISK 1
failed, error=-5
and t
If worked here - at least for now (I restarted the system a few times
without problems).
In my opinion, this work-around also points to a timing issue between
starting the ethernet network, starting the samba system and mouting the
network shares.
Most of most of the above mentioned suggestions i
I can confirm this bug. It's really-really annoying and should be fixed
soon.
I've found a solution... Please let me know if it's working for you.
/etc/network/interfaces:
add this line right after your active interface setup:
pre-up sleep 5
i.e:
auto eth0
iface eth0 inet dhcp
pre-up sleep 5
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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
mambo your work around works for my situation. thanks, John
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Well, if the work gets done, then I'll accept this. I haven't heard a
thing from any developers about any fix that might happen. Can you
update us on this?
Martin Bergner wrote:
> Please don't play with the importance settings, this is for developers
> to prioritize the work
--
auto smbfs moun
Please don't play with the importance settings, this is for developers
to prioritize the work
** Changed in: hal (upstream)
Importance: Unknown => Untriaged
Status: Unknown => Rejected
** Changed in: hal (Ubuntu)
Importance: High => Medium
--
auto smbfs mount in /etc/fstab causes h
A workaround could be to configure /etc/fstab with "noauto" and put in
/etc/rc.local "mount /mnt/sambadirectory".
I've tried it and it works.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
Yey. Atleast the status is High now.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
39 matches
Mail list logo
