Проблемы с сетью после обновления

[dr.Faust]

После сегодняшнего обновления

Код: [Выделить]

libopenexr6 (1.6.1-3ubuntu1) to 1.6.1-3ubuntu1.9.04.1
libssl0.9.8 (0.9.8g-15ubuntu3.2) to 0.9.8g-15ubuntu3.3
openssl (0.9.8g-15ubuntu3.2) to 0.9.8g-15ubuntu3.3При попытке подключится к WiFi падает нетворк манагер, а при попытке соединения со СкайЛинк машина тупо виснет насмерть.
Самое смешное - не могу найти старые версии этих пакетов. Что делать?

[VinnyPooh]

По версиям найти можно, просто через фтп. Там все и лежат

http://ftp.us.debian.org/debian/pool/main/o/openexr/

[rapidsp]

этим пакетам понадобятся еще и зависимости.
Только вчера попал в похожую ситуацию. Запустил apt-get install, тот выругался на ряд ссылок, я их перекопировал в файл, зашел в венду и wget -i <этот файл>, положил их в кеш апта и потом все установил
Способ достаточно тупой и трудоемкий, но работает. Скорее всего есть более изящные методы

[dr.Faust]

Спасибо.
Просто через браузер вытянул более новые пакеты libssl0.9.8 (0.9.8g-15ubuntu3.2) to 0.9.8g-16ubuntu3.3 и openssl (0.9.8g-16ubuntu3.2) to 0.9.8g-15ubuntu3.3
Установил их через GUI - установщик ругнулся на наличие более старой версии в источниках ПО, но конечно поставил. Проблема со Скайлинк решена - по вайфаю ещё не проверял - это дома.
Зависимостей не просил.
Пользователь решил продолжить мысль 15 Сентября 2009, 21:30:35:Не помогло
После выбора пункта подключения к сети WiFi Ничего не происходит, а при нажатии на иконка алете NM появляется надпись NetworkManager не запущен. Приходиться перезагружаться.
Откат на старые версии указаных пакетов и повторная переустановка network-manager не помогли.
Что делать?

[Suntechnic]

Аналогичная проблема.
Только у меня ядро 2.6.30.5 с BFS (то что ты выкладывал).
Из-за этого может быть? Сам на каком?

[dr.Faust]

Проверял и с дефолтным 2.6.28-15.
Та же самая ерунда.
P.S.
У тебя с 2.6.30.5 AppArmor грузится?

[Suntechnic]

Если запустить через консоль апплет  так nm-applet --sm-disable и попытаться подключится к wifi:

Код: [Выделить]

** (nm-applet:3510): DEBUG: applet_common_device_state_changed
** (nm-applet:3510): DEBUG: old state indicates that this was not a disconnect 0
** (nm-applet:3510): DEBUG: applet_common_device_state_changed
** (nm-applet:3510): DEBUG: old state indicates that this was not a disconnect 0
** (nm-applet:3510): DEBUG: applet_common_device_state_changed
** (nm-applet:3510): DEBUG: applet_common_device_state_changed
** (nm-applet:3510): DEBUG: applet_common_device_state_changed

** (nm-applet:3510): WARNING **: _nm_object_get_property: Error getting 'ServiceName' for /org/freedesktop/NetworkManager/ActiveConnection/0: The name org.freedesktop.NetworkManager was not provided by any .service files


** (nm-applet:3510): WARNING **: _nm_object_get_property: Error getting 'Connection' for /org/freedesktop/NetworkManager/ActiveConnection/0: The name org.freedesktop.NetworkManager was not provided by any .service files
А вот что в daemmons.log
Загрузка:

Код: [Выделить]

Sep 16 03:24:34 alex-laptop console-kit-daemon[2457]: GLib-GObject-WARNING: IA__g_object_get_valist: value location for `gchararray' passed as NULL
Sep 16 03:24:34 alex-laptop last message repeated 3 times
Sep 16 03:24:34 alex-laptop init: tty4 main process (2260) killed by TERM signal
Sep 16 03:24:34 alex-laptop init: tty5 main process (2261) killed by TERM signal
Sep 16 03:24:34 alex-laptop init: tty2 main process (2266) killed by TERM signal
Sep 16 03:24:34 alex-laptop init: tty3 main process (2267) killed by TERM signal
Sep 16 03:24:34 alex-laptop init: tty6 main process (2270) killed by TERM signal
Sep 16 03:24:34 alex-laptop init: tty1 main process (2923) killed by TERM signal
Sep 16 03:24:34 alex-laptop console-kit-daemon[2457]: GLib-GObject-WARNING: IA__g_object_get_valist: value location for `gchararray' passed as NULL
Sep 16 03:24:34 alex-laptop last message repeated 2 times
Sep 16 03:24:36 alex-laptop console-kit-daemon[2457]: WARNING: Unable to activate console: No such device or address
Sep 16 03:24:36 alex-laptop console-kit-daemon[2457]: GLib-GObject-WARNING: instance of invalid non-instantiatable type `(null)'
Sep 16 03:24:36 alex-laptop console-kit-daemon[2457]: GLib-GObject-CRITICAL: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Sep 16 03:24:36 alex-laptop console-kit-daemon[2457]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Sep 16 03:25:34 alex-laptop acpid: client connected from 2596[111:120]
Sep 16 03:25:34 alex-laptop NetworkManager: <info>  starting...
Sep 16 03:25:34 alex-laptop avahi-daemon[2675]: Found user 'avahi' (UID 110) and group 'avahi' (GID 119).
Sep 16 03:25:34 alex-laptop avahi-daemon[2675]: Successfully dropped root privileges.
Sep 16 03:25:34 alex-laptop avahi-daemon[2675]: avahi-daemon 0.6.23 starting up.
Sep 16 03:25:34 alex-laptop NetworkManager: <info>  (eth0): new Ethernet device (driver: 'tg3')
Sep 16 03:25:34 alex-laptop NetworkManager: <info>  (eth0): exported as /org/freedesktop/Hal/devices/net_00_1e_ec_45_fd_42
Sep 16 03:25:34 alex-laptop avahi-daemon[2675]: Successfully called chroot().
Sep 16 03:25:34 alex-laptop avahi-daemon[2675]: Successfully dropped remaining capabilities.
Sep 16 03:25:34 alex-laptop NetworkManager: <info>  (wlan0): driver supports SSID scans (scan_capa 0x01).
Sep 16 03:25:34 alex-laptop NetworkManager: <info>  (wlan0): new 802.11 WiFi device (driver: 'ath5k')
Sep 16 03:25:34 alex-laptop NetworkManager: <info>  (wlan0): exported as /org/freedesktop/Hal/devices/net_00_1f_e1_89_76_b6
Sep 16 03:25:34 alex-laptop NetworkManager: <info>  Trying to start the supplicant...
Sep 16 03:25:34 alex-laptop NetworkManager: <info>  Trying to start the system settings daemon...
Sep 16 03:25:35 alex-laptop NetworkManager: <info>  (wlan0): supplicant manager state:  down -> idle
Sep 16 03:25:35 alex-laptop avahi-daemon[2675]: No service file found in /etc/avahi/services.
Sep 16 03:25:35 alex-laptop avahi-daemon[2675]: Network interface enumeration completed.
Sep 16 03:25:35 alex-laptop avahi-daemon[2675]: Registering HINFO record with values 'I686'/'LINUX'.
Sep 16 03:25:35 alex-laptop avahi-daemon[2675]: Server startup complete. Host name is alex-laptop.local. Local service cookie is 3187901515.
Sep 16 03:25:35 alex-laptop nm-system-settings:    SCPlugin-Ifupdown: init!
Sep 16 03:25:35 alex-laptop nm-system-settings:    SCPlugin-Ifupdown: update_system_hostname
Sep 16 03:25:35 alex-laptop acpid: client connected from 2654[0:0]
Sep 16 03:25:35 alex-laptop nm-system-settings: <info>  loading system config file (/usr/local/etc/NetworkManager/nm-system-settings.conf) caused error: No such file or directory (4)
Sep 16 03:25:35 alex-laptop nm-system-settings:    SCPluginIfupdown: management mode: unmanaged
Sep 16 03:25:35 alex-laptop nm-system-settings:    SCPlugin-Ifupdown: devices added (udi: /org/freedesktop/Hal/devices/net_00_1e_ec_45_fd_42, iface: eth0)
Sep 16 03:25:35 alex-laptop nm-system-settings:    SCPlugin-Ifupdown: devices added (udi: /org/freedesktop/Hal/devices/net_00_1f_e1_89_76_b6, iface: wlan0)
Sep 16 03:25:35 alex-laptop nm-system-settings:    SCPlugin-Ifupdown: end _init.
Sep 16 03:25:35 alex-laptop nm-system-settings: Loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list.
Sep 16 03:25:35 alex-laptop nm-system-settings: Error parsing file '/usr/local/etc/NetworkManager/nm-system-settings.conf': No such file or directory
Sep 16 03:25:35 alex-laptop nm-system-settings: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Sep 16 03:25:35 alex-laptop nm-system-settings:    SCPlugin-Ifupdown: (163748736) ... get_connections.
Sep 16 03:25:35 alex-laptop nm-system-settings:    SCPlugin-Ifupdown: (163748736) connections count: 0
Sep 16 03:25:35 alex-laptop nm-system-settings:    Ifupdown: get unmanaged devices count: 0
Sep 16 03:25:35 alex-laptop nm-system-settings: Error parsing file '/usr/local/etc/NetworkManager/nm-system-settings.conf': No such file or directory
Sep 16 03:25:38 alex-laptop NetworkManager: <info>  (eth0): device state change: 1 -> 2
Sep 16 03:25:38 alex-laptop NetworkManager: <info>  (eth0): bringing up device.
Sep 16 03:25:39 alex-laptop NetworkManager: <info>  (eth0): preparing device.
Sep 16 03:25:39 alex-laptop NetworkManager: <info>  (eth0): deactivating device (reason: 2).
Sep 16 03:25:39 alex-laptop NetworkManager: <info>  Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Sep 16 03:25:39 alex-laptop NetworkManager: <info>  Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Sep 16 03:25:39 alex-laptop NetworkManager: <info>  (wlan0): device state change: 1 -> 2
Sep 16 03:25:39 alex-laptop NetworkManager: <info>  (wlan0): bringing up device.
Sep 16 03:25:39 alex-laptop NetworkManager: <info>  (wlan0): preparing device.
Sep 16 03:25:39 alex-laptop NetworkManager: <info>  (wlan0): deactivating device (reason: 2).
Sep 16 03:25:39 alex-laptop NetworkManager: <info>  (wlan0): device state change: 2 -> 3
Sep 16 03:25:39 alex-laptop NetworkManager: <info>  (wlan0): supplicant interface state:  starting -> ready
Sep 16 03:25:39 alex-laptop console-kit-daemon[2466]: WARNING: Couldn't read /proc/2464/environ: Failed to open file '/proc/2464/environ': No such file or directoryПопытка коннекта:

Код: [Выделить]

Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Activation (wlan0) starting connection 'bluestreem'
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  (wlan0): device state change: 3 -> 4
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  (wlan0): device state change: 4 -> 5
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Activation (wlan0/wireless): access point 'bluestreem' has security, but secrets are required.
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  (wlan0): device state change: 5 -> 6
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  (wlan0): device state change: 6 -> 4
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  (wlan0): device state change: 4 -> 5
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Activation (wlan0/wireless): connection 'bluestreem' has security, and secrets exist.  No new secrets needed.
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Config: added 'ssid' value 'bluestreem'
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Config: added 'mode' value '1'
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Config: added 'key_mgmt' value 'NONE'
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Config: added 'auth_alg' value 'OPEN'
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Config: added 'wep_key0' value '<omitted>'
Sep 16 03:28:23 alex-laptop NetworkManager: <info>  Config: added 'wep_tx_keyidx' value '0'

[dr.Faust]

Попробовал переустановить nm - заменил на 0.7.1-2 - эффект тот-же. Заметил, что падение происходит при соединении с сетью. Например если удалить настройки и коннектиться, то падает после ввода пароля.
Пользователь решил продолжить мысль 17 Сентября 2009, 00:11:44:Такс - вопрос меняет русло. Какой пакет ответственен за wep шифрование? Так как если соединятся с незащищённой сетью, то всё пашет на ура.