@Jim Warner, does your suggestion at #10 still work for you. It works
for me, if I unckeck all connections, wired, wireless and mobile.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Thanks Clint, I will try and report back soon, but...
For me, lsof is located at /usr/bin/lsof not /usr/sbin/lsof
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ok, here are two version of last-shutdown-lsof.
last-shutdown-lsof-available-unchecked is a clean shutdown with network-
manager 'available to all users' unchecked.
last-shutdown-lsof-available-checked is a unclean shutdown with network-
manager 'available to all users' checked.
Hope this helps
Oops, here the other file.
** Attachment added: last-shutdown-lsof-available-checked
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3505116/+files/last-shutdown-lsof-available-checked
--
You received this bug notification because you are a member of Desktop
Steve, as far as I can tell, NM is the only way that dhclient is
started/run. Is there a way to confirm this?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Further to #45, if I check 'Available to all user' (usually causing an
unclean filesystem at shutdown) and then do 'sudo service network-
manager stop' and then 'killall dhclient' the filesystem will then go
down cleanly.
Steve, I'm guessing that answers your question at #44.
--
You received
Clint, I have tried what you suggested (uncomment line 132 at
/etc/init.d/sendsig), and caused an unclean shutdown by checking
'Available to all users' for current NM connection. On reboot, there was
no mention of dhclient in /var/crash.
--
You received this bug notification because you are a
Ok, where to next? Is more information needed from users?
It's gone quiet on what seems like an identified problem and narrowing
evidence pointing to two culprits.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
Hi Fransisco' I agree that latest kernel has improved the situation. It
is now possible to simple uncheck 'Available to all users' in NM to get
a clean shutdown. Beware if you create a new network connection, because
it defaults to 'Available to all users' checked. Before the latest
kernel, this
I've just tested newly released kernel 3.5.0-24. It also works with
uncheck 'Available to all users' workaround mentioned above.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Not directly, but I would assume so, as unchecking 'Available to all
users' still works with 3.5.0-25.
I have also tried your suggestion at #60, thanks. It works for me -- but
I have reverted to the simple 'uncheck' as there seems no downside in my
installations and any future fix should be with
LO 4 installed as described in #45 is also working very well in 12.10,
integration with unity is as expected.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1085169
Title:
Star Man Aquarius, have you install libreoffice-debian-menus?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1085169
Title:
LibreOffice Menus Stop Working even with
Oops, I was wrong at #47. Integration not as expected. I meant that
menus are working without the this bug but within the application window
and not integrated into unity. Star Man Aquarius at #49 is correct. (You
can't expect TDF to provide unity integration for Ubuntu.)
--
You received this
This bug should be generalised to other file systems. It occurs using
xfs and jfs, as well as ext4. In my experience the fs is not relevant,
except some recover from an unclean shutdown better than others. (It's
easy to try different file systems using fsarchiver, don't forget to
change fstab to
Does anyone else see two lines about 'hub_port_status failed error
(-110)' just before shutdown and immediately following 'mount: / is
busy'? These errors always occur on several computers using different
filesystems. (None of the workarounds mentioned above or in bug #1061639
resolve the problem
Confirming comments at #121, point 8, and later.
Another (temporary) workaround, as suggested earlier, is to remove
libreoffice-gtk and revert to LO menus within the application.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Could this bug relate to libreoffice-gtk, remove it and the problem
disappears? Although, of course, you won't have unity integration. I can
live with that, in preference to randomly inoperative menus.
--
You received this bug notification because you are a member of Desktop
Packages, which is
@ Marius, I think you missed my point. I am suggesting that another
package, other than the two mentioned in this bug report, might be
implicated in this problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
apport information
** Tags added: apport-collected oneiric running-unity
** Description changed:
My Huawei E1762 modem is the only method I use to connect to the
internet. If a dropout occurs (sometime frequently in my location), the
modem is no longer recognised by network-manager and I
apport information
** Attachment added: Gconf.txt
https://bugs.launchpad.net/bugs/905622/+attachment/2655082/+files/Gconf.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: IfupdownConfig.txt
https://bugs.launchpad.net/bugs/905622/+attachment/2655083/+files/IfupdownConfig.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: IpAddr.txt
https://bugs.launchpad.net/bugs/905622/+attachment/2655084/+files/IpAddr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/905622/+attachment/2655085/+files/IwConfig.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: NMTool.txt
https://bugs.launchpad.net/bugs/905622/+attachment/2655086/+files/NMTool.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: NetDevice.eth3.txt
https://bugs.launchpad.net/bugs/905622/+attachment/2655087/+files/NetDevice.eth3.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: NetDevice.lo.txt
https://bugs.launchpad.net/bugs/905622/+attachment/2655088/+files/NetDevice.lo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: NetDevice.ppp0.txt
https://bugs.launchpad.net/bugs/905622/+attachment/2655089/+files/NetDevice.ppp0.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: NetDevice.wlan3.txt
https://bugs.launchpad.net/bugs/905622/+attachment/2655090/+files/NetDevice.wlan3.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: PciNetwork.txt
https://bugs.launchpad.net/bugs/905622/+attachment/2655091/+files/PciNetwork.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/905622/+attachment/2655092/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/905622/+attachment/2655093/+files/RfKill.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/905622/+attachment/2655094/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
apport information
** Attachment added:
modified.conffile..etc.NetworkManager.NetworkManager.conf.txt
https://bugs.launchpad.net/bugs/905622/+attachment/2655095/+files/modified.conffile..etc.NetworkManager.NetworkManager.conf.txt
--
You received this bug notification because you are a
I've worked around the dropout-then-mandatory-reboot problem in Oneiric
by using wvdial (NM still handles connection to router and on forwarding
to other devices). With wvdial, dropouts are reconnected and internet
access continues.
It's hard to measure but dropout frequency also seem less (this
This is a kinda annoying bug in 11.10. If my connection drops-out
(fairly regular event), I can't reconnect without a reboot. I have tried
sudo killall modem-manager (worked in 11.04), disable networking and
sudo restart network-manager without effect. Am I missing something? Is
there an easy
I tried sudo restart modemmanager and that seems to work after waiting
30 seconds or so.
I wonder, though, if there is a dropout, why does this process not get
automatically triggered if auto connection is set in network manager?
--
You received this bug notification because you are a member of
Anders, thanks for your help. I have filed bug report at LP#905622
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/848164
Title:
autoconnect to 3G network
Status in
Public bug reported:
My Huawei E1762 modem is the only method I use to connect to the
internet. If a dropout occurs (sometime frequently in my location), the
modem is no longer recognised by network-manager and I can't reconnect.
I have tried sudo restart network-manager and sudo restart
This post (http://mail.gnome.org/archives/networkmanager-
list/2011-December/msg00173.html) tells a similar story.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/905622
Title:
Simple workaround seems to be 'sudo service network-manager stop' 'sudo
service network-manager start' whenever the modem drops-out. I've
created a script that can be used from a remote desktop to restart the
network.
--
You received this bug notification because you are a member of Desktop
Solution at #20 only works sometimes, maybe the problem is related to
the usb modem firmware 'freezing' or 'stalling', as the only way to re-
establish internet connection seems to be to withdraw the modem and
reinsert it. (I have recently upgraded firmware but the problem
remains.)
I am trying
It could still be a problem, but I have changed my method of connecting
to the internet. I now use a portable ZTE pocket wifi modem. So my
laptop now connects through wifi and not using the broadband modem --
the ultimate workaround (after trying all of the above). I now using
12.10 and dropouts
Alexander, get rid of NM and install wicd to learn if the problem(s)
still persist.
Using wicd, I get clean and fast shutdown in 5 seconds, with no fsck
checks on reboot. Worth a try!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Ernie, I'm still on 12.10 (I'm waiting for RC before upgrading) and
using wicd with a wireless connection, so I'm not sure why you are
getting an error with your ethernet connection. You have probably
explored all the options...
In the next couple of days I'll upgrade one computer to 13.04RC and
Ernie, what version of Network-Manager is installed?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1124803
Title:
NetworkManager doesn't respond to SIGTERM in daemon mode
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'.
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
Franciso, I am using 3.5.0-26, and the my comment at #75 holds true.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext4 corruption associated with shutdown of
@Tony U Workaround using older version of Chromium for RPI is at https
://ubuntu-mate.community/t/trying-to-fix-chromium-issues/9235/10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
50 matches
Mail list logo
