Dear Michael, Luckily this problem did not occur again. I restarted my machine after the fill-up which caused several programs to not respond anymore in order to investigate what was going on.
On Wednesday 10 February 2010 17:17:45 Michael Biebl wrote: > Hi, > > can you reliably reproduce this? So no, I cannot reproduce this unfortunately. > Is a modem-manager process running? Currently there is a modem-manager process running and everything seems fine again. Checking the logs reveals the following messages: """ Feb 11 06:55:51 mamma NetworkManager: <info> starting... Feb 11 06:55:51 mamma NetworkManager: <info> Trying to start the modem- manager... Feb 11 06:55:51 mamma NetworkManager: SCPlugin-Ifupdown: init! Feb 11 06:55:51 mamma NetworkManager: SCPlugin-Ifupdown: update_system_hostname Feb 11 06:55:51 mamma NetworkManager: SCPluginIfupdown: guessed connection type (eth0) = 802-3-ethernet Feb 11 06:55:51 mamma NetworkManager: SCPlugin-Ifupdown: update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e Feb 11 06:55:51 mamma NetworkManager: SCPluginIfupdown: management mode: unmanaged Feb 11 06:55:51 mamma NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:40:00.0/net/eth0, iface: eth0) Feb 11 06:55:51 mamma NetworkManager: SCPluginIfupdown: locking wired connection setting Feb 11 06:55:51 mamma NetworkManager: Ifupdown: get unmanaged devices count: 1 Feb 11 06:55:51 mamma NetworkManager: SCPlugin-Ifupdown: (141091568) ... get_connections. Feb 11 06:55:51 mamma NetworkManager: SCPlugin-Ifupdown: (141091568) ... get_connections (managed=false): return empty list. Feb 11 06:55:51 mamma NetworkManager: Ifupdown: get unmanaged devices count: 1 Feb 11 06:55:51 mamma NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo) Feb 11 06:55:51 mamma NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. Feb 11 06:55:51 mamma NetworkManager: SCPlugin-Ifupdown: end _init. Feb 11 06:55:51 mamma NetworkManager: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. Feb 11 06:55:51 mamma modem-manager: Loaded plugin ZTE Feb 11 06:55:51 mamma modem-manager: Loaded plugin Novatel Feb 11 06:55:51 mamma modem-manager: Loaded plugin Generic Feb 11 06:55:51 mamma modem-manager: Loaded plugin AnyData Feb 11 06:55:51 mamma modem-manager: Loaded plugin Option High-Speed Feb 11 06:55:51 mamma modem-manager: Loaded plugin Sierra Feb 11 06:55:51 mamma modem-manager: Loaded plugin Longcheer Feb 11 06:55:51 mamma modem-manager: Loaded plugin Ericsson MBM Feb 11 06:55:51 mamma modem-manager: Loaded plugin Option Feb 11 06:55:51 mamma modem-manager: Loaded plugin Nokia Feb 11 06:55:51 mamma modem-manager: Loaded plugin Gobi Feb 11 06:55:51 mamma NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Feb 11 06:55:51 mamma NetworkManager: <info> WiFi enabled by radio killswitch; enabled by state file Feb 11 06:55:51 mamma NetworkManager: <info> WWAN enabled by radio killswitch; enabled by state file Feb 11 06:55:51 mamma modem-manager: Loaded plugin MotoC Feb 11 06:55:51 mamma modem-manager: Loaded plugin Huawei Feb 11 06:55:51 mamma NetworkManager: <info> (eth0): carrier is ON Feb 11 06:55:51 mamma NetworkManager: <info> (eth0): new Ethernet device (driver: 'tg3') Feb 11 06:55:51 mamma NetworkManager: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 Feb 11 06:55:51 mamma NetworkManager: <info> modem-manager is now available Feb 11 06:55:51 mamma NetworkManager: <WARN> default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files Feb 11 06:55:51 mamma NetworkManager: <info> Trying to start the supplicant... """ > Was this directly after installing modemmanager? Yes it was directly after installing the updates with "aptitude safe-upgrade" (and modemmanager came along with them). > What lead to this bug, where you upgrading your system or something > similar? What happens if you restart network-manager and/or dbus, do you > still get the error messages in the daemon.log. Maybe it was some race condition that occurred right after the update that caused the problem and rebooting the system (and thus restarting the network- manager and dbus too) helped to fix it. It was quite surprising to find my system in a (for me) somewhat unusable state after some updates. Furthermore I know that without being able to reproduce this issue, fixing it for others that install this package is tough. But unfortunately I cannot provide more information about it. Best regards Rico Moorman -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
