NetworkManager 0.9.8.0 from Raring is not a solution.
It use /var/lib/NetworkManager/ directory to store .lease
files. It is not allowed by apparmor policy
isc-dhcp-client: /etc/apparmor/init/network-interface-security/sbin.dhclient
If permissions for /var/lib/NetworkManager is granted to dhclient
Forget to mention that the wicd failure occurred on 13.04 amd64.deb.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124803
Title:
NetworkManager doesn't respond to SIGTERM in daemon mode
To manage
Unfortunately wicd would not install on amd64.deb for me. Failure
indicated partway through the installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124803
Title:
NetworkManager doesn't res
After I replaced network-manager with wicd on 12.10 everything works
perfectly. Now shutdown is much faster -- no delays at all. And I got
rid of the hacked init scripts that I was using to circumvent the bug.
Thanks for mentioning wicd, Russell.
--
You received this bug notification because you
Ernie, you have faced another bug in NetworkManager.
The comments are in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/comments/102
so you should post comments there
or someone should open a dedicated bug.
I have removed duplication link.
In 12.10 Quantal NetworkManager 0.9.8.0 does
Max, I have not tested either. I am using the latest 12.10 version
(0.9.6.0-0ubuntu7).
I would be happy to test further. Is there a binary version available of
0.9.6.0 with the patch you mentioned?
BTW, my machine shuts down in 5-8 seconds using wicd, compared with
20-25 seconds with NM installed
Russel, have you tested network-manager 0.9.8.0 and related
libraries form Raring or just network-manager 0.9.6.0
rebuilt with the following patch?
https://bug683932.bugzilla-attachments.gnome.org/attachment.cgi?id=224204
I expect that it should work with always enabled network
available for all u
Ernie, have you tried temporarily replacing NM with wicd on 13.04? (See
https://help.ubuntu.com/community/WICD)
When I use wicd, there is always a clean shutdown, without any delays.
On my 12.10 installation using NM 9.6.0, I can get clean shutdowns by
unchecking 'available to all users'. Checked,
Max,
I have given up on 12.10 but would like to make use of 13.04.
The Raring daily amd64.iso contains network-manager version 9.8.0 and it
exhibits the same failure pattern as 9.6.0 in 12.04.
The failure is 100% reproducible and will manifest each time the OS is shut
down UNLESS enable networ
Ernie, I can confirm that 12.10 with original network-manager
0.9.6.0 has this problem and it appears during shutdown.
I do not play with unchecking of networking, it is always enabled.
The patch mentioned in the comments fixes the issue for me.
Another option is to install to 12.10 the following
I strongly believe this problem is associated with termination rather
than startup.
I can establish conditions for failure by checking enable networking or
prevent failure by unchecking enable networking prior to reboot, restart
or shutdown.
Using a separate OS (12.04), fsck can be used to demon
A have checked x86_64 Quantal 12.10 as well.
I do not see any problem with busy /.
NetworkManager 0.9.8.0.
The only minor issue is 10 seconds pause during shutdown
due to /etc/network/if-post-down.d/avahi-daemon,
but it is likely caused by the provider and his
subdomain in .local zone. Root filesy
kernel
3.8.3-030803-generic #201303141650 SMP Thu Mar 14 20:58:52 UTC 2013 i686 i686
i686 GNU/Linux
network-manager:
Installed: 0.9.8.0-0ubuntu2
and related libnm* and libnl* libraries from raring
on the top of 12.10 quantal
The system shuts down correctly. Although I have not tried x86_64.
Er
Hi Max,
Using 64-bit 3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 19:52:57 UTC
2013 from the 2013-04_02 daily build:
1. NetworkManager stopped correctly (immediately) via sudo stop network-manager.
2. A reboot to an alternate system and fsck of the system under test presented
errors.
Regardless o
Ernie, could you, please, test if network manager stops correctly on SIGTERM
(immediately) or on SIGKILL (with 5 second pause) after
sudo stop network-manager
To start it again
sudo start network-manager
Another interesting point is last messages on shutdown:
sudo halt
I rebuild network-manager
NetworkManger version = 0.9.8.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124803
Title:
NetworkManager doesn't respond to SIGTERM in daemon mode
To manage notifications about this bug go to:
h
Ernie, what version of Network-Manager is installed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124803
Title:
NetworkManager doesn't respond to SIGTERM in daemon mode
To manage notifications ab
64-bit D07-1304 3.8.0-15-generic #25-Ubuntu SMP Wed Mar 27 19:19:30
UTC 2013 downloaded via the 2013-04_01 build FAILS!
1. Boot system
2. Enable networking
3. Shutdown system
4. Boot an alternate system fsck check throws errors EVERY time.
Disabling networking prior to shutdown results in a pro
I believe this bug is fixed in Ubuntu Raring Ringtail with this upload:
https://launchpad.net/ubuntu/+source/network-manager/0.9.8.0-0ubuntu1
As the 64342a313ef497fca8a4fb7567900d4a1460065f is part of the 0.9.8.0
release.
If you need a fix for the bug in previous versions of Ubuntu, please do
ste
>From the upstream report [1], the patch that resolves this regression
has been applied to networkmanager's master branch, so Ubuntu needs to
carry this patch until it is included upstream:
https://bug683932.bugzilla-
attachments.gnome.org/attachment.cgi?id=224204
[1] https://bugzilla.gnome.org/s
** Also affects: network-manager (Gentoo Linux)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124803
Title:
NetworkManager doesn't respond to SIGTERM in
Please, issue an update for 12.10 quantal (network-manager 0.9.6.0-0ubuntu7)
Due to this bug root filesystem can not be cleanly unmounted on shutdown.
Upstart launch NetworkManager as a daemon.
If a system-wide network connection is established,
dhclient and dnsmasqd open files for writing in /var
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124803
Tit
** Tags added: string-fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124803
Title:
NetworkManager doesn't respond to SIGTERM in daemon mode
To manage notifications about this bug go to:
https:/
** Changed in: network-manager
Status: Unknown => Fix Released
** Changed in: network-manager
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124803
Title:
Ne
25 matches
Mail list logo
