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
Desktop Bugs, which is subscribed to the bug report.
** 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
Desktop Bugs,
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
** 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
Desktop Bugs, which is a direct subscriber.
--
** 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
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
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 mount
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 in
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
...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
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs
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
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
--
[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
--
desktop-bugs mailing list
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
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Changed in: nautilus (upstream)
Status: Unknown = Unconfirmed
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-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
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
** Also affects: Baltix
Importance: Untriaged
Status: Unconfirmed
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-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
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
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
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!
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
--
desktop-bugs mailing
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
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
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
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
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
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 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
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
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
** 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
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Yey. Atleast the status is High now.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
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
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
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
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 mount
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
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
same problem here, too.
even cifs workaround doesn't do it.
i would rate this a major problem!
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
This is a big bug for SMB users!
** Changed in: hal (Ubuntu)
Importance: Medium = High
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
My last post is about the change of importance from Medium to High...
sorry about that.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Same problem here.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I also have this problem. Adding noauto to the end has solved it, but it
is rather annoying to mount my shares by hand...
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I am also having the same problem.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
After the long hald timeout (which doesn't happen every time), I seem to also
get a long wait before the desktop initializes the menu and the icons (i get
the desktop background with empty bars for the menus) (this may not be related).
After waiting for a long time, the desktop comes through.
fraco, that is completely related.
Except for one thing: I no longer have this issue. I didn't touch
configurations or anything.
You know what, though, is I always leave my computer sitting at the
login screen for about two minutes. Try setting the mount back to auto,
wait for two minutes at the
It seems to be a timing issue.
I put smbfs into /etc/modules to get the module loaded early in the boot
process. This seems to help sometimes, but most of the time, it doesn't
help either.
I don't get it. Doesn't the developers automount their shares???
Perhaps they have faster machines where
I can confirm the hald -- smbfs problem on an AMD64-machine in Dapper
Drake. I'm currently using cifs as workaround, but there seems to be
antother problem: cifs-mounts auto-mounted via fstab don't show up in
mtab, but work otherwise as supposed to. This can lead to a bit of a
fuzz aka
One time Gaim wouldn't start, Firefox couldn't find anything, then after
a few minutes everything was fine. It must be that!
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
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
Well, dapper is out including this bug. :/
I don't get it. Doesn't the developers automount their shares???
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Did we put this in the wrong spot??? Maybe it belongs to smbfs
** Also affects: hal (upstream)
Severity: Unknown
Priority: Unknown
Status: Unknown
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
hi i have the same problem
i´m useing kubuntu dapper since flight 6 and had no big problems during the
boot up
but when i updated a big bunch of packages about May 10th the boot process hung
at startup of the HALD , i´m still not very familliar with linux so i had no
idea what the problem for
I haven't tried noauto.. but the 'sudo mount.. ' in a script is what is
causing my freeze ;-)
But I see what you mean.. put it in the /etc/fstab, but the noauto just
means that I don't have to use the entire command in the script... ok,
thanks, I will try. That might be the workaround I need...
ok, get this. I put this in my /etc/fstab:
//deb/andrea/home/bkastor/test-mount smbfs
noauto,users,sync,username=andrea%password,dmask=777,fmask=777 0 0
(which I can type in .. using mount -t.. and it works)
After putting this in the fstab, I open a terminal and type in:
sudo mount
whoops.. sorry, messed that up..
When I type it into the xterm, it works fine...
When I double click the executable file with
sudo mount //deb/andrea
it hangs...
sorry... little flustered. I can type this all just fine, and now my
wife is learning what the hell was going on in the background!
I have on that boots with the fstab just fine.. but with my laptop, I
didn't want to do that. I 'had' a file that I made executable and
clicked on with ease for more than a year.. until I upgraded to Dapper.
Now the entire box freezes... hard.. I can type it in manually, but if
I run it, it
Have you put noauto in your fstab?
If you can get it to boot with noauto, then a simple sudo mount
/your/share should do it (that's all that's in my startup script)
On 6/1/06, ipguru99 [EMAIL PROTECTED] wrote:
I have on that boots with the fstab just fine.. but with my laptop, I
didn't want to
How do you assign it to someone then?
This is getting very annoying now to manually mount the shares.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I don't think you can. Hopefully SOMEONE notices...
:(
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
It's not a good solution, but it simplified things for me...
I've got my smbfs drives marked as noauto, so everything boots nicely,
but them I've just set a script to run at startup that mounts the
drives. It probably possible to make them user mountable, but I
wasn't in the mood to fiddle wth
I am also experiencing this bug, using the k7 kernel on an nForce 4
mobo. Changing the mount option from smbfs to cifs works as a stopgap
measure.
Is someone working on this?
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing
Since it isn't assigned to anyone, I don't think so.
Changing to cifs is one idea, but it isn't always the best. Adding
noauto to the end of the options part in smbfs also works as well...
except you have to mount it manually on boot-up.
--
auto smbfs mount in /etc/fstab causes hald hang at
Same here, though Nautilus still cannot browse the Go - Network -
Windows Network area.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Another workaround is to change smbfs mounts in /etc/fstab to cifs.
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Bug 37683 has been marked a duplicate of this bug
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
(Sorry about the repeated messages. It turns out that if the browser
refreshes the page after you post a bug on launchpad, that re-posts the
bug. And if you reboot your computer and the browser comes back with
Session Saver, that refreshes the page... From now on I'll close a bug
window
** Bug 44157 has been marked a duplicate of this bug
** Changed in: Ubuntu
Sourcepackagename: None = hal
Status: Unconfirmed = Confirmed
--
auto smbfs mount in /etc/fstab causes hald hang at boot
https://launchpad.net/bugs/44874
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Today's packages updates for Dapper included a new smbfs package. I
updated all packages on my Athlon64 to the latest, and put back the auto
smbfs mount.
When I booted, it did not hang in hald! However, the GNOME desktop took
over 45 seconds (I timed it) to start. Once the desktop was up, I
69 matches
Mail list logo