** No longer affects: dbus (Ubuntu Lucid)
** No longer affects: dbus (Ubuntu Natty)
** No longer affects: netbase (Ubuntu Lucid)
** No longer affects: netbase (Ubuntu Natty)
** No longer affects: network-manager (Ubuntu Lucid)
** No longer affects: network-manager (Ubuntu Natty)
** No longer
Markus, your screenshot shows a network-manager error:
nm-dispatcher.action: Caught signal 15, shutting down...
This indicates that some part of NM is not being correctly guarded from
/etc/init.d/sendsigs, resulting in abnormal termination that breaks the
network connection before network
Steve, turns out, there already was such a bug report:
https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1066484/comments/11
Regarding the CIFS mounts: Today, I changed the auto cifs mounts during
startup to noauto,user mounts, which get mounted by my user using a script
after
The problem is still there on a fresh Raring installation.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are
It affects me too, but the last 20 times I clicked on this link ( This
bug affects 119 people. Does this bug affect you? Edit ) since
yesterday, it gives me a time out error, please try again in a few
minutes
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Th e problems continues on precise pangolin and quantal quetzal
short info:
(cisco vpn, mount.cifs of drives, when shutting down it takes about 2 minutes
because there a problem with the unmounting of the cifs drives; when manually
unmounting before shutting down there is no problem, shutdown
only info:
the vpn seems to work fine,
mvg,
G
On za, 2012-04-21 at 04:28 +, Clint Byrum wrote:
What type of VPN connection? If it is managed by NetworkManager, it
should be brought down when network manager is brought down, *after* all
network filesystems are brought down.
If not,
** Attachment added: unknown-KR3lma
https://bugs.launchpad.net/bugs/211631/+attachment/3121146/+files/unknown-KR3lma
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
I'll open a bug myself shortly for the VPN case; and reply here with the
bug number.
** No longer affects: network-manager
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
On Sat, Apr 21, 2012 at 04:47:40AM -, Mathieu Trudel-Lapierre wrote:
Well, that would normally be correct, but the VPN plugins depend on
vpnc, pptp, openvpn, etc. to be running to establish and keep the VPN
connection up for rekeying and such. Those don't get a pid file in
I have tried the cifs mount over VPN scenario and shutting down does still
take time. I think connected mounts at shutdown are fixed so they unmount,
but if the VPN is disconnected prior to shutdown the unmount will hang
still.
--
You received this bug notification because you are a member of
What type of VPN connection? If it is managed by NetworkManager, it
should be brought down when network manager is brought down, *after* all
network filesystems are brought down.
If not, that seems like a bug in whatever is running VPNs, but its
probably not *this* bug. I would suggest reporting
Well, that would normally be correct, but the VPN plugins depend on
vpnc, pptp, openvpn, etc. to be running to establish and keep the VPN
connection up for rekeying and such. Those don't get a pid file in
/run/sendsigs.omit.d yet, and so they would get killed by the sendsigs
script shortly before
On vr, 2012-04-06 at 10:12 +, James wrote:
Steve Langasek - I have just tried to replicate in 12.04 beta and could
not reproduce the issue any more. I had a mounted a SMB share using
/etc/fstab which appeared to be successfully unmounted prior to shutdown
(or at least, it didn't hang for a
Steve Langasek - I have just tried to replicate in 12.04 beta and could
not reproduce the issue any more. I had a mounted a SMB share using
/etc/fstab which appeared to be successfully unmounted prior to shutdown
(or at least, it didn't hang for a minute or so, it shut down
immediately).
--
You
Come on, a fix can't be done for this 4 years on? With all the various
workarounds people have put in above comments, surely one of them can
work for everyone?!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Come on, a fix can't be done for this 4 years on?
In fact, between dbus and network-manager now waiting for the
'deconfiguring-networking' event before shutting down, and NM
registering its child processes with /run/sendsigs.omit.d to fix bug
#869635, I believe this should resolve the problem
wpasupplicant no longer includes an init script at all, so this task can
also be considered fixed.
** Changed in: wpasupplicant (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
** No longer affects: null
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are unmounted (CIFS
timeout at shutdown)
another note:
The cifs mount are avalaible through vpn (in this case cisco vpn),
whenever the vpn connection is gone/disconnect,
but the remote drives still appear as mounted in mtab,
then
$umount --a -t cifs -l -f
takes a lot of time
HTH
--
You received this bug notification because you are
On Wed, Nov 02, 2011 at 12:31:00PM -, Gonzals, S. wrote:
The cifs mount are avalaible through vpn (in this case cisco vpn),
whenever the vpn connection is gone/disconnect,
but the remote drives still appear as mounted in mtab,
then
$umount --a -t cifs -l -f
takes a lot of time
Yep,
This bug is disappeared for me (it started reapppearing a week ago), with
the changes in /etc/init/dbus.conf still in effect.
Maybe this has to do with my reinstall of grub2; after that, my computer
shuts again. This possinly indicates it has to do with certain boot options?
--
You received
Is the solution described in comment #143 and comment #147 really the
correct one?
In short, that means dbus always stops on the event deconfiguring-
networking, which is emitted when /etc/init.d/networking stop is
called.
In other words, whenever /etc/init.d/networking stop is called, dbus gets
On Sat, Oct 29, 2011 at 04:31:21PM -, Alonso Andres wrote:
Is the solution described in comment #143 and comment #147 really the
correct one?
No, it isn't; it just seems to be the best workaround anyone has proposed so
far.
In short, that means dbus always stops on the event
On Wed, 2011-10-26 at 22:09 +, Ernst wrote:
Since a week or so, the shutdown is delayed again (on Ubuntu 11.10), despite
the script in dbus.conf. Does anyone has a solution for this?
the same on 10.4
also changing the shutdown, reboot (halt and poweroff) and restart
in /sbin
only works for
Since a week or so, the shutdown is delayed again (on Ubuntu 11.10), despite
the script in dbus.conf. Does anyone has a solution for this?
On Mon, Oct 24, 2011 at 16:03, Gonzals, S.
211...@bugs.launchpad.netwrote:
i'll try that,
but,
i have never putted trailing slashes in the mointpoints,
I have the same problem:
on
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 10.04.3 LTS
Release:10.04
Codename: lucid
none of the these options worked for me, short:
- dbus.conf
- K14 links
- S31 earlier
- a modprobe option
Off topic, but the multiple mount can be caused if you miss trailing
slashes off the mountpoint in fstab
/media/myfsbad
/media/myfs/ good
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
i'll try that,
but,
i have never putted trailing slashes in the mointpoints,
and the double moutings only occus for the cifs ro mounts
mvg,
G
On Mon, 2011-10-24 at 12:50 +, Steve Sutton wrote:
Off topic, but the multiple mount can be caused if you miss trailing
slashes off the mountpoint
@jonbonjovi, @c0l2e did say :)
Put it in /etc/init/dbus.conf. You'll probably find an existing pre-
start/end script section in it (I did in mine). Just paste all the
lines (including the pre-stop and end script lines) into that file,
after the existing end script, or before the line that
@ Steve Sutton:
done! it works!
Thanx!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are unmounted (CIFS
timeout
found a better fix via /etc/init/dbus.conf
add the pre-stop script:
pre-stop script
trap TERM signal TERM
/bin/umount -a -t cifs -f -l
trap - TERM
end script
It works for me and few tested notebooks and desktop PC.
--
You received this bug notification because you are a member
@c0l2e : Wow, thanks man! I can confirm that your fix works great on all
all systems as well (lucid).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought
Please read : on all *my* systems as well
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are unmounted (CIFS
@c0l2e: could you please provide a step-by-step explanation about how to make
your solution work?
Where should I put that text?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
After months of attempts to fix this, I've finally found one that works
for Kubuntu 11.04 (Natty). The problem is that Kubuntu (and I believe
KDE more generally) starts the shutdown process in a way different than
Gnome/Ubuntu, so even the dbus / netbase fixes, the fix above in #158,
and using
I have had this problem for a long time, in different ubuntu versions,
but this is the first time (Ubuntu 11.04) that I am unable to find a
workaround.
Before, I used to create a script that would umount the network drives
and place it at /etc/network/if-down.d. It used to work for Ubuntu
10.10,
Your options are :
1. Use a wired connection
2. Avoid Samba/CIFS shares and configure your server for NFS instead
3. Use AutoFS to create your network shares.
In case 3, AutoFS replaces the need to configure anything in /etc/fstab.
Seems to work well enough with most connections, although
The Upstart file I posted on #153 +autofs5 installed(very important)
solves it for me on 10.10. over wifi. Autofs has to be installed, or the
bug will stay. Today i found this is the working combo for me. You might
want to try this with Natty, i was planning in the next few days, too
tired today.
I have two machines running 11.04 with a wireless connection. I was able
to get a clean shutdown on both by changing the link to
/etc/init.d/umountnfs.sh in /etc/rc0.d and /etc/rc6.d from
S31umountnfs.sh to K15umountnfs.sh. This is a workaround, not a fix, as
it simply starts the cifs/nfs file
Hello
I got this bug on my Kubuntu 10.10 and 11.04 machine
Adding this conf file solved the problem for me on Kubuntu 10.10, but on 11.04
the bug is present even though the upstart job kicks off( the NAS is mounted)
Other described solutions for the bug, which used to work on 10.10 does not on
I still have a hang on reboot / shutdown even after installing the more
recent netbase (4.45ubuntu3) and dbus (1.4.8-3ubuntu2) packages on my
Kubuntu 11.04 laptop. I have four cifs shares defined in fstab. If I
shutdown or reboot, I see network-manager caught signal 15, then a
message about
On a functional level perhaps it is worth considering whether Network
Manager, on stopping, should simply leave the interfaces as currently
configured instead of taking them down. I can make the argument that
Network Manager is a tool to make it easy for the user to control
network interfaces,
Good point!
Den 24 maj 2011 22.54 skrev bdoe brian...@att.net:
On a functional level perhaps it is worth considering whether Network
Manager, on stopping, should simply leave the interfaces as currently
configured instead of taking them down. I can make the argument that
Network Manager is a tool
Excerpts from bdoe's message of Tue May 24 20:54:25 UTC 2011:
On a functional level perhaps it is worth considering whether Network
Manager, on stopping, should simply leave the interfaces as currently
configured instead of taking them down. I can make the argument that
Network Manager is a
** Also affects: dhcdbd (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: network-manager (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: samba (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: sysvinit (Ubuntu
@Clint Byrum
How about we fix the bug for the next release instead of marking it as invalid?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down
Bug was rasied on 2008-04-04 and has 14 duplicates, yet this is somehow invalid?
I don't even use Ubuntu anymore because of silly issues like this.
What do we need to do to get action on this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Excerpts from flaccid's message of Mon May 23 06:27:57 UTC 2011:
Bug was rasied on 2008-04-04 and has 14 duplicates, yet this is somehow
invalid?
I don't even use Ubuntu anymore because of silly issues like this.
What do we need to do to get action on this?
flaccid, its not Invalid as a bug,
** Also affects: netbase (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network
So I've done some analysis, and I believe the root of the problem is
that dbus is stopped too early. network-manager stops whenever dbus
stops, because it is needed. We currently stop dbus on runlevel [06]
.. that is too early, because it is needed until after umountnfs runs
as part of the
On a functional level perhaps it is worth considering whether Network
Manager, on stopping, should simply leave the interfaces as currently
configured instead of taking them down. I can make the argument that
Network Manager is a tool to make it easy for the user to control
network interfaces, but
This bug was fixed in the package netbase - 4.45ubuntu2
---
netbase (4.45ubuntu2) oneiric; urgency=low
* debian/netbase.init: adding initctl call to allow upstart jobs which
support networking to shutdown at the appropriate moment. just before
networking is deconfigured.
** Branch linked: lp:ubuntu/dbus
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are unmounted (CIFS
timeout at
Excerpts from Mike Perrin's message of Mon May 23 20:28:52 UTC 2011:
On a functional level perhaps it is worth considering whether Network
Manager, on stopping, should simply leave the interfaces as currently
configured instead of taking them down. I can make the argument that
Network Manager
This bug was fixed in the package dbus - 1.4.8-3ubuntu2
---
dbus (1.4.8-3ubuntu2) oneiric; urgency=low
* debian/dbus.upstart: stop on deconfiguring-networking, a new
event emitted during shutdown just before networking is deconfigured.
This is a somewhat obtuse solution to
Excerpt from Clint Byrum's comment #146
Excerpts from Mike Perrin's message of Mon May 23 20:28:52 UTC 2011:
On a functional level perhaps it is worth considering whether Network
Manager, on stopping, should simply leave the interfaces as currently
configured instead of taking them down. I
This bug is present in 11.04. CIFS mounted with wifi network connection
hangs forever on shutdown. Wired shuts down fine. For what it is
worth, liinux mint 10 gnome on the same machine, same network identical
CIFS mount in /etc/fstab does NOT exhibit the failure. Mint is using a
symbolic link
Here's some info, if it helps:
Neither of the solutions on
https://help.ubuntu.com/community/MountWindowsSharesPermanently#System%20Hangs%20on%20Shutdown
or
https://wiki.ubuntu.com/MountWindowsSharesPermanently#Fixing%20a%20CIFS%20bug%20with%20network%20manager
worked for me (after one or two
@Fabio: Do you know if this is fixed in another Linux Distro? If so,
please tell us so we can see how they've addressed this problem.
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug
@Robbie Williamson: Yes other distros have solved this. Like Arch. I
switched my laptop to arch for that very reason.
With Arch, I first have my shares that I want connected in fstab. The
Ubuntu documentation is ample on the subject.
Secondly, in Arch, netfs daemon is used to control
God, even Ubuntu 10.10 still suffer from this bug 2 years later...
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This is still a big issue on WiFi-enabled workstations. To put it into
perspective, we have upgraded from 8.04 LTS to 10.04 LTS and shutdown
still takes around 40 minutes for the 16 cifs mounts in FSTAB on four
workstations. Users are seriously inconvenienced.
As hinted earlier, a workaround
Same problem in Kubuntu 10.4
(which means KDE 4.4.2 and it's network manager)
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team,
I had already mentioned above: It's not only a network-manager problem
because it is exactly the same with WICD.
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you
I absolutely do agree with Tom and varanasi. This is a serious usability
problem that should be fixed as soon as possible!
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification
** Changed in: network-manager
Status: New = Confirmed
** Changed in: network-manager
Status: Confirmed = New
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification
Agree with Tom in full.
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Not fixed for wireless network with WICD too !
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
It seems NetworkManager 0.8 fixed this issue for those on wired
connections, so I'm marking as fix released for n-m.
Wireless connections apparently still broken.
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Fix Released
--
Network is brought down before network
Since management of wireless network connections is a principal use case
of NM, this is not fixed.
** Changed in: network-manager (Ubuntu)
Status: Fix Released = Confirmed
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
It's unfortunate that people have to write custom scripts to unmount
CIFS shares, especially since .bash_logout doesn't seem to run in Ubuntu
9.10 for super-users. I fixed the problems by creating my own self-
healing wireless scripts to replace Network Manager and (as related to
the mounts, and
Advice: stop wasting time on ubuntu bugs. Nothing is done about them. I
moved away from Ubuntu years ago because of this fact and every now and
then major bugs like this are updated with a new comment and nothing is
ever done. If you want politics and bugs, use ubuntu; if not move to a
distro that
I think comment #121 workaround will only work if you are using GDM,
this bug affects KDE and other desktop environment users as well.
Comment #120 states
I *think* that this bug is only apparent now if :
a) You're mounting remote NFS/CIFS shares by specifying them in /etc/fstab AND
b) You're
re #100:
- hacking the shutdown sequence to make it unmount network filesystems
earlier (for example moving S31umountnfs.sh to S14umountnfs.sh in
/etc/rc[06].d) : will fix it if you aren't executing anything on those
network filesystems
This is not safe, as at S14 applications might still
Hi Spaetz. That fix was documented as early as comment 7 and is
discussed thoroughly throughout the 110 or so comments. Sadly, the fix
doesn't work in Karmic any more. Well, I'll qualify that - it works for
wired connections, but not for WIFI. Network Manager brings WIFI
connections down
I don't get the message CIFS VFS server not responding on shutdown any
more on the Ubuntu PCs that I have upgraded to Karmic (and which have
cifs lines in /etc/fstab). So the bug is fixed ?
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
@sixela: It still happens on wifi system
@Thierry Carrez
I can't use the gvfs because I'm not using Gnome on my system.
Something lite on a netbook makes much more sense but I don't want an overly
simplified interface like you get with most netbook interfaces, so I'm using
Fluxbox with a bunch
Ditto, gvfs is Gnome-centric and this is an underlying system issue.
The network:/ and smb: protocol in KDEs Dolphin works well enough but
for instance, Amarok doesn't allow music collections to be used via
smb:/ but does handle Samba mounts via mount.cifs. fusesmb also doesn't
do much as it
@James : That would be awesome and exactly what I'll propose to the
networkmanager list (when I get round to it).
@Sixela : As H3g3m0n notes, the bug is still apparent on WIFI systems.
In general, worth noting another reason gvfs shares don't always work
out - nautilus won't process thumbnails
I have a use case of wanting to pack up my laptop up quickly after using
wireless
at a client's office where I have to mount a remote Windows filesystem using
Samba.
Any reason why you don't use nautilus-based mounts (typing smb:// ... in
Nautilus) ? fstab-based network filesystem mounts
An other important reason is that gvfs does not support cifs UNIX
Extensions yet.
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server
** Project changed: hundredpapercuts = null
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
I can confirm that this bug is fixed for wired network users. However,
I can no longer get any previously expounded solution to work when using
wireless. Any workaround would be a godsend to me.
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
Confirmed here too. I've tried all the solutions listed previously to
resolve this issue in Karmic and Wireless, but I always experience a
hang on shutdown. The only workaround (not really) I've found so far
is to add the users option to my /etc/fstab entry for my cifs share,
then manually
The moving/copying of the rc0/6 scripts doesn't seem to work in Karmic
RC (using wireless). I just get a hang on shutdown with the message
init: usplash post-start process (2446) terminated with status 1 and
never seems to shut down. If I put the scripts back the way they're
supposed to be, then
** Changed in: sysvinit (Debian)
Status: Unknown = New
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team, which is
NM 0.8 does not bring down ethernet connections on exit anymore. I don't
think we will be able to something similar for wifi soon. Is that good
enough for this bug?
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
This still occurs in the 9.10 beta. In fact, the upgrade has disabled
the fix I'd put in, based on this bug, under 9.04.
As it's such a simple fix, lets do this for 9.10 final shall we ?
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
Hi Tom
I installed Karmic Beta the other day and no longer get this error (with
the entries in the /etc/fstab as I originally described).
Hamish
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received
I am facing this issue on intrepid and jaunty using wired connection (with NM
in system mode).
Even before reading this thread I went through moving S31umountnfs.sh up in the
rc0/6 scripts in order to find the critical tip. For me this was S20sendsigs
(as described by Thierry), i.e.
Please don't add bugs to hundredpapercuts when you know the bug is not a
paper cut!
** Changed in: hundredpapercuts
Status: New = Invalid
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received
** Also affects: network-manager
Importance: Undecided
Status: New
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You
Add this to the One Hundred Paper Cuts Project to allow for more
visibility. I know that this may not fit the easy to fix part of the
projects description, but it does negatively affect the user experience.
I am hoping that Karmic will have a solution.
--
Network is brought down before network
Thanks for this status update.
As Thuerry Carrez proposed, I tried to avoid system wide CIFS mounts via
fstab by monting my cifs shares manually with mount.cifs ... in my
home folder. The shutdown problem is still the same.
Using GNOME vfs pseudomounts is not a solution for me because the cifs
I am still having the issue with the latest Jaunty Beta 9.04 64-bit
Desktop install.
This would seem to me to be a moderate usability due to the fact it can
take upwards of 5-10 minutes to shutdown depending on the system.
In 8.10 the system would never shut down for me. Now it seems to
Status update
This problem is well-identified, it will affect Jaunty, there is no need
to confirm it or add to this already-long thread. Please just use the
This bug affects me link at the top instead.
This issue comes from the shutdown sequence that is not supporting a use
case of mounted
There is *some* sendsigs omission support in wpasupplicant, but
apparently not enough. It still should write something to
/lib/init/rw/sendsigs.omit.d...
** Changed in: wpasupplicant (Ubuntu)
Status: New = Confirmed
--
Network is brought down before network filesystems are unmounted
98 matches
Mail list logo
