ALT Linux Bugzilla
– Attachment 5369 Details for
Bug 27009
Не выключается ПК самостоятельно
New bug
|
Search
|
[?]
|
Help
Register
|
Log In
[x]
|
Forgot Password
Login:
[x]
|
EN
|
RU
messages
messages.txt (text/plain), 55.58 KB, created by
Alexander Shemetov
on 2012-03-09 10:02:23 MSK
(
hide
)
Description:
messages
Filename:
MIME Type:
Creator:
Alexander Shemetov
Created:
2012-03-09 10:02:23 MSK
Size:
55.58 KB
patch
obsolete
>Файл /etc/NetworkManager/dispatcher.d/10-netfs веÑнÑл к иÑÑ Ð¾Ð´Ð½Ð¾Ð¼Ñ Ð²Ð¸Ð´Ñ! ÐиÑего в нем не закомменÑиÑовано! > >ÐаÑало. ШаÑÑ Ð¿Ñи загÑÑзке не ÑмонÑиÑованÑ! Ð fstab ÑаÑкомменÑиÑовал две ÑаÑÑ nfs, ÑмонÑиÑовал Ð¸Ñ mount /mnt/public (вÑоÑÑÑ Ð¿Ð¾ аналогии) и опÑÑÑ Ð·Ð°ÐºÐ¾Ð¼Ð¼ÐµÐ½ÑиÑовал. reboot. > >Mar 9 11:42:14 kab302-laborant shutdown[5805]: shutting down for system reboot >Mar 9 11:42:14 kab302-laborant init: Switching to runlevel: 6 >Mar 9 11:42:16 kab302-laborant plymouth: Activating splash succeeded >Mar 9 11:42:16 kab302-laborant alteratord: alteratord shutdown succeeded >Mar 9 11:42:17 kab302-laborant dm: rundm shutdown succeeded >Mar 9 11:42:17 kab302-laborant virtualbox: Unloading VirtualBox module (vboxnetadp): succeeded >Mar 9 11:42:17 kab302-laborant virtualbox: Unloading VirtualBox module (vboxnetflt): succeeded >Mar 9 11:42:17 kab302-laborant virtualbox: Unloading VirtualBox module (vboxpci): succeeded >Mar 9 11:42:17 kab302-laborant virtualbox: Unloading VirtualBox module (vboxdrv): succeeded >Mar 9 11:42:17 kab302-laborant sshd[4639]: Received signal 15; terminating. >Mar 9 11:42:18 kab302-laborant sshd: sshd shutdown succeeded >Mar 9 11:42:18 kab302-laborant nmbd[5042]: [2012/03/09 11:42:18.147641, 0] nmbd/nmbd.c:71(terminate) >Mar 9 11:42:18 kab302-laborant nmbd[5042]: Got SIGTERM: going down... >Mar 9 11:42:18 kab302-laborant nmb: nmbd shutdown succeeded >Mar 9 11:42:18 kab302-laborant smb: smbd shutdown succeeded >Mar 9 11:42:19 kab302-laborant cups: cupsd shutdown succeeded >Mar 9 11:42:20 kab302-laborant autofs: automount shutdown succeeded >Mar 9 11:42:20 kab302-laborant ntpd[4981]: dispatch_imsg in main: pipe closed >Mar 9 11:42:20 kab302-laborant ntpd[4981]: Terminating >Mar 9 11:42:20 kab302-laborant ntpd: ntpd shutdown succeeded >Mar 9 11:42:20 kab302-laborant rc: Stopping keytable: succeeded >Mar 9 11:42:20 kab302-laborant rc: Stopping fbsetfont: succeeded >Mar 9 11:42:21 kab302-laborant random: Saving random seed: succeeded >Mar 9 11:42:21 kab302-laborant rpcbind: rpcbind shutdown succeeded >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <info> (eth0): device state change: 8 -> 3 (reason 39) >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <info> (eth0): deactivating device (reason: 39). >Mar 9 11:42:21 kab302-laborant dhcpcd[4332]: eth0: received SIGTERM, stopping >Mar 9 11:42:21 kab302-laborant avahi-daemon[4557]: Withdrawing address record for 192.168.112.228 on eth0. >Mar 9 11:42:21 kab302-laborant avahi-daemon[4557]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.112.228. >Mar 9 11:42:21 kab302-laborant avahi-daemon[4557]: Interface eth0.IPv4 no longer relevant for mDNS. >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <info> (eth0): canceled DHCP transaction, DHCP client pid 4332 >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <info> (eth0): writing resolv.conf to /sbin/resolvconf >Mar 9 11:42:21 kab302-laborant avahi-daemon[4557]: Got SIGHUP, reloading. >Mar 9 11:42:21 kab302-laborant avahi-daemon: Reloading Avahi mDNS/DNS-SD service: succeeded >Mar 9 11:42:21 kab302-laborant nmcli: Device state: 3 (disconnected) >Mar 9 11:42:21 kab302-laborant NetworkManager: Disconnecting eth0: succeeded >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <info> caught signal 15, shutting down normally. >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <warn> quit request received, terminating... >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <info> (eth1): now unmanaged >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <info> (eth1): device state change: 2 -> 1 (reason 36) >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <info> (eth1): cleaning up... >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <info> (eth1): taking down device. >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <info> (eth0): now unmanaged >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <info> (eth0): device state change: 3 -> 1 (reason 36) >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <info> (eth0): cleaning up... >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <info> (eth0): taking down device. >Mar 9 11:42:21 kab302-laborant NetworkManager[3997]: <info> (eth0): writing resolv.conf to /sbin/resolvconf >Mar 9 11:42:22 kab302-laborant NetworkManager[3997]: <info> exiting (success) >Mar 9 11:42:22 kab302-laborant NetworkManager: NetworkManager shutdown succeeded >Mar 9 11:42:22 kab302-laborant nm-dispatcher.action: Caught signal 15, shutting down... >Mar 9 11:42:22 kab302-laborant modem-manager[4142]: <info> Caught signal 15, shutting down... >Mar 9 11:42:22 kab302-laborant network: Computing interface groups: >Mar 9 11:42:22 kab302-laborant network: . >Mar 9 11:42:22 kab302-laborant network: 1 interfaces found >Mar 9 11:42:22 kab302-laborant network: Processing /etc/net/vlantab: empty. >Mar 9 11:42:22 kab302-laborant network: Stopping group 0/virtual (1 interfaces) >Mar 9 11:42:22 kab302-laborant network: ^IStopping lo: >Mar 9 11:42:22 kab302-laborant network: . >Mar 9 11:42:22 kab302-laborant network: OK >Mar 9 11:42:22 kab302-laborant rc: Stopping network: succeeded >Mar 9 11:42:22 kab302-laborant avahi-daemon[4557]: Disconnected from D-Bus, exiting. >Mar 9 11:42:22 kab302-laborant avahi-daemon[4557]: Got SIGTERM, quitting. >Mar 9 11:42:22 kab302-laborant avahi-daemon[4557]: avahi-daemon 0.6.28 exiting. >Mar 9 11:42:22 kab302-laborant messagebus: dbus-daemon shutdown succeeded >Mar 9 11:42:22 kab302-laborant udevd: udevd shutdown succeeded >Mar 9 11:42:23 kab302-laborant exiting on signal 15 >Mar 9 11:45:10 kab302-laborant syslogd 1.4.1: restart. >Mar 9 11:45:10 kab302-laborant syslogd: syslogd startup succeeded >Mar 9 11:45:10 kab302-laborant polkitd[4143]: started daemon version 0.102 using authority implementation `local' version `0.102' >Mar 9 11:45:10 kab302-laborant dbus[3857]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' >Mar 9 11:45:10 kab302-laborant NetworkManager[3995]: <info> monitoring kernel firmware directory '/lib/firmware'. >Mar 9 11:45:10 kab302-laborant NetworkManager[3995]: etcnet-alt: Current network profile: (none) >Mar 9 11:45:10 kab302-laborant NetworkManager[3995]: <info> Loaded plugin etcnet-alt: (c) 2008 Mikhail Efremov <sem@altlinux.org>. >Mar 9 11:45:10 kab302-laborant NetworkManager[3995]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. >Mar 9 11:45:10 kab302-laborant NetworkManager[3995]: etcnet-alt: Couldn't access iface directory /etc/net/ifaces/eth1 . >Mar 9 11:45:10 kab302-laborant NetworkManager[3995]: etcnet-alt: eth1: Readed connection "System eth1" >Mar 9 11:45:10 kab302-laborant udevd-final: Handling remaining udev events: succeeded >Mar 9 11:45:10 kab302-laborant NetworkManager[3995]: etcnet-alt: eth0: Readed connection "System eth0" >Mar 9 11:45:10 kab302-laborant rc: Starting fbsetfont: succeeded >Mar 9 11:45:10 kab302-laborant NetworkManager[3995]: <info> WiFi enabled by radio killswitch; enabled by state file >Mar 9 11:45:10 kab302-laborant NetworkManager[3995]: <info> WWAN enabled by radio killswitch; enabled by state file >Mar 9 11:45:10 kab302-laborant NetworkManager[3995]: <info> WiMAX enabled by radio killswitch; enabled by state file >Mar 9 11:45:10 kab302-laborant NetworkManager[3995]: <info> Networking is enabled by state file >Mar 9 11:45:10 kab302-laborant NetworkManager[3995]: <info> ((null)): writing resolv.conf to /sbin/resolvconf >Mar 9 11:45:10 kab302-laborant keytable: Loading keymap: ruwin_ct_sh-UTF-8 >Mar 9 11:45:10 kab302-laborant loadkeys: Loading /lib/kbd/keymaps/i386/qwerty/ruwin_ct_sh-UTF-8.map.gz >Mar 9 11:45:10 kab302-laborant setsyskeytable: Loading keymap: ruwin_ct_sh-UTF-8 succeeded >Mar 9 11:45:10 kab302-laborant keytable: ^[[73G >Mar 9 11:45:10 kab302-laborant keytable: [ >Mar 9 11:45:10 kab302-laborant keytable: ^[[1m^[[32m >Mar 9 11:45:10 kab302-laborant keytable: DONE >Mar 9 11:45:10 kab302-laborant keytable: ^[[39;49m^[[0;10m >Mar 9 11:45:11 kab302-laborant keytable: Loading compose keys: compose.latin >Mar 9 11:45:11 kab302-laborant loadkeys: Loading /lib/kbd/keymaps/include/compose.latin >Mar 9 11:45:11 kab302-laborant setsyskeytable: Loading compose keys: compose.latin succeeded >Mar 9 11:45:11 kab302-laborant keytable: ^[[73G >Mar 9 11:45:11 kab302-laborant keytable: [ >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth1): carrier is OFF >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth1): new Ethernet device (driver: '8139too' ifindex: 3) >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/0 >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth1): now managed >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth1): device state change: 1 -> 2 (reason 2) >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth1): bringing up device. >Mar 9 11:45:11 kab302-laborant keytable: ^[[1m^[[32m >Mar 9 11:45:11 kab302-laborant keytable: DONE >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth1): preparing device. >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth1): deactivating device (reason: 2). >Mar 9 11:45:11 kab302-laborant keytable: ^[[39;49m^[[0;10m >Mar 9 11:45:11 kab302-laborant keytable: Binding extra Win keys, loading: windowkeys-compose.inc >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth0): carrier is OFF >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth0): new Ethernet device (driver: 'via-rhine' ifindex: 2) >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth0): now managed >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth0): device state change: 1 -> 2 (reason 2) >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth0): bringing up device. >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth0): preparing device. >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth0): deactivating device (reason: 2). >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth0): carrier now ON (device state 2) >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth0): device state change: 2 -> 3 (reason 40) >Mar 9 11:45:11 kab302-laborant loadkeys: Loading /lib/kbd/keymaps/i386/include/windowkeys-compose.inc.gz >Mar 9 11:45:11 kab302-laborant setsyskeytable: Binding extra Win keys, loading: windowkeys-compose.inc succeeded >Mar 9 11:45:11 kab302-laborant keytable: ^[[73G >Mar 9 11:45:11 kab302-laborant keytable: [ >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> modem-manager is now available >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <warn> bluez error getting default adapter: No such adapter >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <warn> bluez error getting default adapter: No such adapter >Mar 9 11:45:11 kab302-laborant keytable: ^[[1m^[[32m >Mar 9 11:45:11 kab302-laborant keytable: DONE >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> Trying to start the supplicant... >Mar 9 11:45:11 kab302-laborant dbus[3857]: [system] Activating service name='fi.epitest.hostap.WPASupplicant' (using servicehelper) >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) starting connection 'System eth0' >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth0): device state change: 3 -> 4 (reason 0) >Mar 9 11:45:11 kab302-laborant keytable: ^[[39;49m^[[0;10m >Mar 9 11:45:11 kab302-laborant keytable: The BackSpace key sends: ^? loading delete.inc >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth0): device state change: 4 -> 5 (reason 0) >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth0): device state change: 5 -> 7 (reason 0) >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds) >Mar 9 11:45:11 kab302-laborant dbus[3857]: [system] Successfully activated service 'fi.epitest.hostap.WPASupplicant' >Mar 9 11:45:11 kab302-laborant loadkeys: Loading /lib/kbd/keymaps/i386/include/delete.inc.gz >Mar 9 11:45:11 kab302-laborant setsyskeytable: The BackSpace key sends: ^? loading delete.inc succeeded >Mar 9 11:45:11 kab302-laborant keytable: ^[[73G >Mar 9 11:45:11 kab302-laborant keytable: [ >Mar 9 11:45:11 kab302-laborant keytable: ^[[1m^[[32m >Mar 9 11:45:11 kab302-laborant keytable: DONE >Mar 9 11:45:11 kab302-laborant keytable: ^[[39;49m^[[0;10m >Mar 9 11:45:11 kab302-laborant rc: Starting keytable: succeeded >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> dhcpcd started with pid 4330 >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. >Mar 9 11:45:11 kab302-laborant dhcpcd[4330]: eth0: dhcpcd 4.0.15 starting >Mar 9 11:45:11 kab302-laborant NetworkManager[3995]: <info> (eth0): DHCPv4 state changed nbi -> preinit >Mar 9 11:45:11 kab302-laborant dhcpcd[4330]: eth0: broadcasting for a lease >Mar 9 11:45:11 kab302-laborant dm: rundm startup succeeded >Mar 9 11:45:12 kab302-laborant autofs: automount startup succeeded >Mar 9 11:45:12 kab302-laborant dhcpcd[4330]: eth0: offered 192.168.112.228 from 192.168.112.112 >Mar 9 11:45:12 kab302-laborant dhcpcd[4330]: eth0: acknowledged 192.168.112.228 from 192.168.112.112 >Mar 9 11:45:12 kab302-laborant dhcpcd[4330]: eth0: leased 192.168.112.228 for 18748800 seconds >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> (eth0): DHCPv4 state changed preinit -> bound >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled... >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started... >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> address 192.168.112.228 >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> prefix 24 (255.255.255.0) >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> gateway 192.168.112.112 >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> nameserver '192.168.112.112' >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> domain name 'school' >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> Scheduling stage 5 >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> Done scheduling stage 5 >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete. >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... >Mar 9 11:45:12 kab302-laborant avahi-daemon[4555]: Found user '_avahi' (UID 106) and group '_avahi' (GID 116). >Mar 9 11:45:12 kab302-laborant avahi-daemon[4555]: Successfully dropped root privileges. >Mar 9 11:45:12 kab302-laborant avahi-daemon[4555]: avahi-daemon 0.6.28 starting up. >Mar 9 11:45:12 kab302-laborant avahi-daemon[4555]: Successfully called chroot(). >Mar 9 11:45:12 kab302-laborant avahi-daemon[4555]: Successfully dropped remaining capabilities. >Mar 9 11:45:12 kab302-laborant avahi-daemon[4555]: Loading service file /services/ssh.service. >Mar 9 11:45:12 kab302-laborant avahi-daemon[4555]: Loading service file /services/udisks.service. >Mar 9 11:45:12 kab302-laborant avahi-daemon[4555]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.112.228. >Mar 9 11:45:12 kab302-laborant avahi-daemon[4555]: New relevant interface eth0.IPv4 for mDNS. >Mar 9 11:45:12 kab302-laborant avahi-daemon[4555]: Network interface enumeration completed. >Mar 9 11:45:12 kab302-laborant avahi-daemon[4555]: Registering new address record for 192.168.112.228 on eth0.IPv4. >Mar 9 11:45:12 kab302-laborant avahi-daemon[4555]: Registering HINFO record with values 'I686'/'LINUX'. >Mar 9 11:45:12 kab302-laborant avahi-daemon: avahi-daemon startup succeeded >Mar 9 11:45:12 kab302-laborant rc.sysinit: Mounting proc filesystem: succeeded >Mar 9 11:45:12 kab302-laborant rc.sysinit: Mounting sys filesystem: succeeded >Mar 9 11:45:12 kab302-laborant udevd: udevd startup succeeded >Mar 9 11:45:12 kab302-laborant udevd: Populating /dev: succeeded >Mar 9 11:45:12 kab302-laborant rc.sysinit: Activating swap partitions: succeeded >Mar 9 11:45:12 kab302-laborant rc.sysinit: Setting hostname kab302-laborant.local: succeeded >Mar 9 11:45:12 kab302-laborant fsck: /dev/sda2: clean, 91233/589824 files, 813575/2359296 blocks >Mar 9 11:45:12 kab302-laborant rc.sysinit: Checking root filesystem succeeded >Mar 9 11:45:12 kab302-laborant rc.sysinit: Remounting root filesystem in read/write mode: succeeded >Mar 9 11:45:12 kab302-laborant clock: Setting system clock (localtime): succeeded >Mar 9 11:45:12 kab302-laborant clock: Today's date: Fri Mar 9 11:44:58 YEKT 2012 succeeded >Mar 9 11:45:12 kab302-laborant rc.sysinit: Finding module dependencies: succeeded >Mar 9 11:45:12 kab302-laborant rc.sysinit: Configuring kernel parameters: succeeded >Mar 9 11:45:12 kab302-laborant vgchange: No volume groups found >Mar 9 11:45:12 kab302-laborant lvm_start: Setting up LVM2: succeeded >Mar 9 11:45:12 kab302-laborant fsck: /dev/sda5: recovering journal >Mar 9 11:45:12 kab302-laborant fsck: /dev/sda5: clean, 5681/189696 files, 292328/758272 blocks >Mar 9 11:45:12 kab302-laborant rc.sysinit: Checking filesystems succeeded >Mar 9 11:45:12 kab302-laborant rc.sysinit: Mounting local filesystems: succeeded >Mar 9 11:45:12 kab302-laborant rc.sysinit: Checking loopback filesystems: succeeded >Mar 9 11:45:12 kab302-laborant rc.sysinit: Mounting loopback filesystems: succeeded >Mar 9 11:45:12 kab302-laborant rc.sysinit: Cleaning up temporary files from previous boot: succeeded >Mar 9 11:45:12 kab302-laborant rc.sysinit: Activating swap space: succeeded >Mar 9 11:45:12 kab302-laborant rc.sysinit: Updating chrooted environments: succeeded >Mar 9 11:45:12 kab302-laborant init: Entering runlevel: 5 >Mar 9 11:45:12 kab302-laborant x11presetdrv: Preparing X11 drivers succeeded >Mar 9 11:45:12 kab302-laborant alteratord: alteratord startup succeeded >Mar 9 11:45:12 kab302-laborant messagebus: dbus-daemon startup succeeded >Mar 9 11:45:12 kab302-laborant network: Computing interface groups: >Mar 9 11:45:12 kab302-laborant network: . >Mar 9 11:45:12 kab302-laborant network: 1 interfaces found >Mar 9 11:45:12 kab302-laborant network: Starting group 0/virtual (1 interfaces) >Mar 9 11:45:12 kab302-laborant network: ^IStarting lo: >Mar 9 11:45:12 kab302-laborant network: . >Mar 9 11:45:12 kab302-laborant last message repeated 3 times >Mar 9 11:45:12 kab302-laborant network: OK >Mar 9 11:45:12 kab302-laborant network: Processing /etc/net/vlantab: empty. >Mar 9 11:45:12 kab302-laborant rc: Starting network: succeeded >Mar 9 11:45:12 kab302-laborant NetworkManager: Setting network parameters: succeeded >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> NetworkManager (version 0.8.6) is starting... >Mar 9 11:45:12 kab302-laborant NetworkManager[3995]: <info> Read config file /etc/NetworkManager/NetworkManager.conf >Mar 9 11:45:12 kab302-laborant NetworkManager: NetworkManager startup succeeded >Mar 9 11:45:12 kab302-laborant bluetoothd[4045]: Bluetooth deamon 4.93 >Mar 9 11:45:12 kab302-laborant bluetoothd: bluetoothd startup succeeded >Mar 9 11:45:12 kab302-laborant bluetoothd[4045]: Starting SDP server >Mar 9 11:45:12 kab302-laborant rpcbind: cannot create socket for udp6 >Mar 9 11:45:12 kab302-laborant rpcbind: cannot create socket for tcp6 >Mar 9 11:45:13 kab302-laborant rpcbind: rpcbind startup succeeded >Mar 9 11:45:13 kab302-laborant random: Initializing random number generator: succeeded >Mar 9 11:45:13 kab302-laborant NetworkManager[3995]: <info> VPN: loaded org.freedesktop.NetworkManager.l2tp >Mar 9 11:45:13 kab302-laborant NetworkManager[3995]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp >Mar 9 11:45:13 kab302-laborant NetworkManager[3995]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn >Mar 9 11:45:13 kab302-laborant NetworkManager[3995]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc >Mar 9 11:45:13 kab302-laborant NetworkManager[3995]: <info> trying to start the modem manager... >Mar 9 11:45:13 kab302-laborant dbus[3857]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) >Mar 9 11:45:13 kab302-laborant dbus[3857]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper) >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> ModemManager (version 0.5) starting... >Mar 9 11:45:13 kab302-laborant dbus[3857]: [system] Successfully activated service 'org.freedesktop.ModemManager' >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin MotoC >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin X22X >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin Novatel >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin Gobi >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin SimTech >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin ZTE >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin Longcheer >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin Linktop >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin AnyData >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin Nokia >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin Option >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin Wavecom >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin Ericsson MBM >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin Sierra >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin Option High-Speed >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin Generic >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin Samsung >Mar 9 11:45:13 kab302-laborant modem-manager[4140]: <info> Loaded plugin Huawei >Mar 9 11:45:13 kab302-laborant NetworkManager[3995]: <info> (eth0): writing resolv.conf to /sbin/resolvconf >Mar 9 11:45:13 kab302-laborant sshd[4622]: Server listening on 0.0.0.0 port 22. >Mar 9 11:45:13 kab302-laborant sshd: sshd startup succeeded >Mar 9 11:45:13 kab302-laborant avahi-daemon[4555]: Server startup complete. Host name is kab302-laborant.local. Local service cookie is 347596397. >Mar 9 11:45:13 kab302-laborant avahi-daemon[4555]: Got SIGHUP, reloading. >Mar 9 11:45:13 kab302-laborant avahi-daemon: Reloading Avahi mDNS/DNS-SD service: succeeded >Mar 9 11:45:13 kab302-laborant NetworkManager[3995]: <info> (eth0): device state change: 7 -> 8 (reason 0) >Mar 9 11:45:14 kab302-laborant avahi-daemon[4555]: Service "kab302-laborant" (/services/udisks.service) successfully established. >Mar 9 11:45:14 kab302-laborant avahi-daemon[4555]: Service "kab302-laborant" (/services/ssh.service) successfully established. >Mar 9 11:45:14 kab302-laborant NetworkManager[3995]: <info> Policy set 'System eth0' (eth0) as default for IPv4 routing and DNS. >Mar 9 11:45:14 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) successful, device activated. >Mar 9 11:45:14 kab302-laborant dbus[3857]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) >Mar 9 11:45:14 kab302-laborant NetworkManager[3995]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. >Mar 9 11:45:14 kab302-laborant dbus[3857]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' >Mar 9 11:45:15 kab302-laborant cups: cupsd startup succeeded >Mar 9 11:45:15 kab302-laborant ntpd: ntpd startup succeeded >Mar 9 11:45:15 kab302-laborant virtualbox: Loading VirtualBox module (vboxdrv): succeeded >Mar 9 11:45:15 kab302-laborant ntpd[4884]: dispatch_imsg in main: pipe closed >Mar 9 11:45:15 kab302-laborant ntpd[4884]: Terminating >Mar 9 11:45:15 kab302-laborant virtualbox: Loading VirtualBox module (vboxpci): succeeded >Mar 9 11:45:16 kab302-laborant virtualbox: Loading VirtualBox module (vboxnetflt): succeeded >Mar 9 11:45:16 kab302-laborant ntpd: ntpd shutdown succeeded >Mar 9 11:45:16 kab302-laborant virtualbox: Loading VirtualBox module (vboxnetadp): succeeded >Mar 9 11:45:16 kab302-laborant ntpd: ntpd startup succeeded >Mar 9 11:45:16 kab302-laborant nmb: nmbd startup succeeded >Mar 9 11:45:18 kab302-laborant smb: smbd startup succeeded >Mar 9 11:45:18 kab302-laborant plymouth: Deactivating splash succeeded >Mar 9 11:45:20 kab302-laborant dbus[3857]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper) >Mar 9 11:45:21 kab302-laborant dbus[3857]: [system] Successfully activated service 'org.freedesktop.ConsoleKit' >Mar 9 11:45:26 kab302-laborant gnome-keyring-daemon[5437]: GLib-GIO: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. >Mar 9 11:45:26 kab302-laborant gnome-keyring-daemon[5437]: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files >Mar 9 11:45:26 kab302-laborant last message repeated 2 times >Mar 9 11:45:27 kab302-laborant gnome-keyring-daemon[5437]: The Secret Service was already initialized >Mar 9 11:45:28 kab302-laborant gnome-keyring-daemon[5437]: The SSH agent was already initialized >Mar 9 11:45:31 kab302-laborant gnome-keyring-daemon[5437]: The GPG agent was already initialized >Mar 9 11:45:33 kab302-laborant gnome-keyring-daemon[5437]: The PKCS#11 component was already initialized >Mar 9 11:45:38 kab302-laborant dbus[3857]: [system] Activating service name='org.freedesktop.UDisks' (using servicehelper) >Mar 9 11:45:38 kab302-laborant dbus[3857]: [system] Successfully activated service 'org.freedesktop.UDisks' >Mar 9 11:45:38 kab302-laborant dbus[3857]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper) >Mar 9 11:45:40 kab302-laborant dbus[3857]: [system] Successfully activated service 'org.freedesktop.UPower' >Mar 9 11:45:50 kab302-laborant pulseaudio[5652]: pid.c: Daemon already running. >Mar 9 11:45:51 kab302-laborant dbus[3857]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper) >Mar 9 11:45:51 kab302-laborant blueman-mechanism: Starting blueman-mechanism >Mar 9 11:45:51 kab302-laborant dbus[3857]: [system] Successfully activated service 'org.blueman.Mechanism' >Mar 9 11:45:52 kab302-laborant blueman-mechanism: reload 0 0 >Mar 9 11:46:21 kab302-laborant blueman-mechanism: Exiting >Mar 9 11:46:31 kab302-laborant ntpd[4997]: adjusting local clock by -61.094935s > >ÐÑодолжение. ШаÑÑ Ð½Ðµ ÑмонÑиÑованÑ! ÐообÑе Ð¸Ñ Ð½ÐµÑ, ни вÑÑÑнÑÑ, ни авÑомаÑом не монÑиÑÑÑ. > >Mar 9 11:48:18 kab302-laborant smbd[5093]: [2012/03/09 11:48:18.977496, 0] smbd/server.c:281(remove_child_pid) >Mar 9 11:48:19 kab302-laborant smbd[5093]: Could not find child 5842 -- ignoring >Mar 9 11:48:52 kab302-laborant shutdown[5868]: shutting down for system reboot >Mar 9 11:48:52 kab302-laborant init: Switching to runlevel: 6 >Mar 9 11:48:54 kab302-laborant plymouth: Activating splash succeeded >Mar 9 11:48:54 kab302-laborant alteratord: alteratord shutdown succeeded >Mar 9 11:48:55 kab302-laborant dm: rundm shutdown succeeded >Mar 9 11:48:55 kab302-laborant virtualbox: Unloading VirtualBox module (vboxnetadp): succeeded >Mar 9 11:48:55 kab302-laborant virtualbox: Unloading VirtualBox module (vboxnetflt): succeeded >Mar 9 11:48:55 kab302-laborant virtualbox: Unloading VirtualBox module (vboxpci): succeeded >Mar 9 11:48:55 kab302-laborant virtualbox: Unloading VirtualBox module (vboxdrv): succeeded >Mar 9 11:48:56 kab302-laborant sshd[4622]: Received signal 15; terminating. >Mar 9 11:48:56 kab302-laborant sshd: sshd shutdown succeeded >Mar 9 11:48:56 kab302-laborant nmbd[5040]: [2012/03/09 11:48:56.169147, 0] nmbd/nmbd.c:71(terminate) >Mar 9 11:48:56 kab302-laborant nmbd[5040]: Got SIGTERM: going down... >Mar 9 11:48:56 kab302-laborant nmb: nmbd shutdown succeeded >Mar 9 11:48:56 kab302-laborant smb: smbd shutdown succeeded >Mar 9 11:48:57 kab302-laborant cups: cupsd shutdown succeeded >Mar 9 11:48:58 kab302-laborant autofs: automount shutdown succeeded >Mar 9 11:48:58 kab302-laborant ntpd[4997]: dispatch_imsg in main: pipe closed >Mar 9 11:48:58 kab302-laborant ntpd[4997]: Terminating >Mar 9 11:48:58 kab302-laborant ntpd: ntpd shutdown succeeded >Mar 9 11:48:58 kab302-laborant rc: Stopping keytable: succeeded >Mar 9 11:48:58 kab302-laborant rc: Stopping fbsetfont: succeeded >Mar 9 11:48:59 kab302-laborant dd: 1+0 records in >Mar 9 11:48:59 kab302-laborant dd: 1+0 records out >Mar 9 11:48:59 kab302-laborant dd: 512 bytes (512 B) copied, 0.000324383 s, 1.6 MB/s >Mar 9 11:48:59 kab302-laborant random: Saving random seed: succeeded >Mar 9 11:48:59 kab302-laborant rpcbind: rpcbind shutdown succeeded >Mar 9 11:48:59 kab302-laborant NetworkManager[3995]: <info> (eth0): device state change: 8 -> 3 (reason 39) >Mar 9 11:48:59 kab302-laborant NetworkManager[3995]: <info> (eth0): deactivating device (reason: 39). >Mar 9 11:48:59 kab302-laborant dhcpcd[4330]: eth0: received SIGTERM, stopping >Mar 9 11:48:59 kab302-laborant avahi-daemon[4555]: Withdrawing address record for 192.168.112.228 on eth0. >Mar 9 11:48:59 kab302-laborant avahi-daemon[4555]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.112.228. >Mar 9 11:48:59 kab302-laborant avahi-daemon[4555]: Interface eth0.IPv4 no longer relevant for mDNS. >Mar 9 11:48:59 kab302-laborant NetworkManager[3995]: <info> (eth0): canceled DHCP transaction, DHCP client pid 4330 >Mar 9 11:48:59 kab302-laborant NetworkManager[3995]: <info> (eth0): writing resolv.conf to /sbin/resolvconf >Mar 9 11:48:59 kab302-laborant avahi-daemon[4555]: Got SIGHUP, reloading. >Mar 9 11:48:59 kab302-laborant avahi-daemon: Reloading Avahi mDNS/DNS-SD service: succeeded >Mar 9 11:48:59 kab302-laborant nmcli: Device state: 3 (disconnected) >Mar 9 11:48:59 kab302-laborant NetworkManager: Disconnecting eth0: succeeded >Mar 9 11:48:59 kab302-laborant NetworkManager[3995]: <info> caught signal 15, shutting down normally. >Mar 9 11:48:59 kab302-laborant NetworkManager[3995]: <warn> quit request received, terminating... >Mar 9 11:48:59 kab302-laborant NetworkManager[3995]: <info> (eth1): now unmanaged >Mar 9 11:48:59 kab302-laborant NetworkManager[3995]: <info> (eth1): device state change: 2 -> 1 (reason 36) >Mar 9 11:48:59 kab302-laborant NetworkManager[3995]: <info> (eth1): cleaning up... >Mar 9 11:48:59 kab302-laborant NetworkManager[3995]: <info> (eth1): taking down device. >Mar 9 11:48:59 kab302-laborant NetworkManager[3995]: <info> (eth0): now unmanaged >Mar 9 11:48:59 kab302-laborant NetworkManager[3995]: <info> (eth0): device state change: 3 -> 1 (reason 36) >Mar 9 11:48:59 kab302-laborant NetworkManager[3995]: <info> (eth0): cleaning up... >Mar 9 11:48:59 kab302-laborant NetworkManager[3995]: <info> (eth0): taking down device. >Mar 9 11:49:00 kab302-laborant NetworkManager[3995]: <info> (eth0): writing resolv.conf to /sbin/resolvconf >Mar 9 11:49:00 kab302-laborant NetworkManager[3995]: <info> exiting (success) >Mar 9 11:49:00 kab302-laborant NetworkManager: NetworkManager shutdown succeeded >Mar 9 11:49:00 kab302-laborant nm-dispatcher.action: Caught signal 15, shutting down... >Mar 9 11:49:00 kab302-laborant modem-manager[4140]: <info> Caught signal 15, shutting down... >Mar 9 11:49:00 kab302-laborant network: Computing interface groups: >Mar 9 11:49:00 kab302-laborant network: . >Mar 9 11:49:00 kab302-laborant network: 1 interfaces found >Mar 9 11:49:00 kab302-laborant network: Processing /etc/net/vlantab: empty. >Mar 9 11:49:00 kab302-laborant network: Stopping group 0/virtual (1 interfaces) >Mar 9 11:49:00 kab302-laborant network: ^IStopping lo: >Mar 9 11:49:00 kab302-laborant network: . >Mar 9 11:49:00 kab302-laborant network: OK >Mar 9 11:49:00 kab302-laborant rc: Stopping network: succeeded >Mar 9 11:49:00 kab302-laborant avahi-daemon[4555]: Disconnected from D-Bus, exiting. >Mar 9 11:49:00 kab302-laborant avahi-daemon[4555]: Got SIGTERM, quitting. >Mar 9 11:49:00 kab302-laborant avahi-daemon[4555]: avahi-daemon 0.6.28 exiting. >Mar 9 11:49:00 kab302-laborant messagebus: dbus-daemon shutdown succeeded >Mar 9 11:49:00 kab302-laborant udevd: udevd shutdown succeeded >Mar 9 11:49:01 kab302-laborant exiting on signal 15 >Mar 9 11:49:55 kab302-laborant syslogd 1.4.1: restart. >Mar 9 11:49:55 kab302-laborant syslogd: syslogd startup succeeded >Mar 9 11:49:55 kab302-laborant udevd-final: Handling remaining udev events: succeeded >Mar 9 11:49:55 kab302-laborant polkitd[4137]: started daemon version 0.102 using authority implementation `local' version `0.102' >Mar 9 11:49:55 kab302-laborant dbus[3851]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' >Mar 9 11:49:55 kab302-laborant NetworkManager[3989]: <info> monitoring kernel firmware directory '/lib/firmware'. >Mar 9 11:49:55 kab302-laborant rc: Starting fbsetfont: succeeded >Mar 9 11:49:55 kab302-laborant NetworkManager[3989]: etcnet-alt: Current network profile: (none) >Mar 9 11:49:55 kab302-laborant NetworkManager[3989]: <info> Loaded plugin etcnet-alt: (c) 2008 Mikhail Efremov <sem@altlinux.org>. >Mar 9 11:49:55 kab302-laborant NetworkManager[3989]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. >Mar 9 11:49:55 kab302-laborant NetworkManager[3989]: etcnet-alt: Couldn't access iface directory /etc/net/ifaces/eth1 . >Mar 9 11:49:55 kab302-laborant NetworkManager[3989]: etcnet-alt: eth1: Readed connection "System eth1" >Mar 9 11:49:55 kab302-laborant NetworkManager[3989]: etcnet-alt: eth0: Readed connection "System eth0" >Mar 9 11:49:55 kab302-laborant NetworkManager[3989]: <info> WiFi enabled by radio killswitch; enabled by state file >Mar 9 11:49:55 kab302-laborant NetworkManager[3989]: <info> WWAN enabled by radio killswitch; enabled by state file >Mar 9 11:49:55 kab302-laborant NetworkManager[3989]: <info> WiMAX enabled by radio killswitch; enabled by state file >Mar 9 11:49:55 kab302-laborant NetworkManager[3989]: <info> Networking is enabled by state file >Mar 9 11:49:55 kab302-laborant NetworkManager[3989]: <info> ((null)): writing resolv.conf to /sbin/resolvconf >Mar 9 11:49:55 kab302-laborant keytable: Loading keymap: ruwin_ct_sh-UTF-8 >Mar 9 11:49:55 kab302-laborant loadkeys: Loading /lib/kbd/keymaps/i386/qwerty/ruwin_ct_sh-UTF-8.map.gz >Mar 9 11:49:55 kab302-laborant setsyskeytable: Loading keymap: ruwin_ct_sh-UTF-8 succeeded >Mar 9 11:49:55 kab302-laborant keytable: ^[[73G >Mar 9 11:49:55 kab302-laborant keytable: [ >Mar 9 11:49:55 kab302-laborant keytable: ^[[1m^[[32m >Mar 9 11:49:55 kab302-laborant keytable: DONE >Mar 9 11:49:56 kab302-laborant keytable: ^[[39;49m^[[0;10m >Mar 9 11:49:56 kab302-laborant keytable: Loading compose keys: compose.latin >Mar 9 11:49:56 kab302-laborant loadkeys: Loading /lib/kbd/keymaps/include/compose.latin >Mar 9 11:49:56 kab302-laborant setsyskeytable: Loading compose keys: compose.latin succeeded >Mar 9 11:49:56 kab302-laborant keytable: ^[[73G >Mar 9 11:49:56 kab302-laborant keytable: [ >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth1): carrier is OFF >Mar 9 11:49:56 kab302-laborant keytable: ^[[1m^[[32m >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth1): new Ethernet device (driver: '8139too' ifindex: 3) >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/0 >Mar 9 11:49:56 kab302-laborant keytable: DONE >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth1): now managed >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth1): device state change: 1 -> 2 (reason 2) >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth1): bringing up device. >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth1): preparing device. >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth1): deactivating device (reason: 2). >Mar 9 11:49:56 kab302-laborant keytable: ^[[39;49m^[[0;10m >Mar 9 11:49:56 kab302-laborant keytable: Binding extra Win keys, loading: windowkeys-compose.inc >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth0): carrier is OFF >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth0): new Ethernet device (driver: 'via-rhine' ifindex: 2) >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth0): now managed >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth0): device state change: 1 -> 2 (reason 2) >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth0): bringing up device. >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth0): preparing device. >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth0): deactivating device (reason: 2). >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth0): carrier now ON (device state 2) >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth0): device state change: 2 -> 3 (reason 40) >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> modem-manager is now available >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <warn> bluez error getting default adapter: No such adapter >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <warn> bluez error getting default adapter: No such adapter >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> Trying to start the supplicant... >Mar 9 11:49:56 kab302-laborant dbus[3851]: [system] Activating service name='fi.epitest.hostap.WPASupplicant' (using servicehelper) >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) starting connection 'System eth0' >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth0): device state change: 3 -> 4 (reason 0) >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth0): device state change: 4 -> 5 (reason 0) >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth0): device state change: 5 -> 7 (reason 0) >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds) >Mar 9 11:49:56 kab302-laborant loadkeys: Loading /lib/kbd/keymaps/i386/include/windowkeys-compose.inc.gz >Mar 9 11:49:56 kab302-laborant setsyskeytable: Binding extra Win keys, loading: windowkeys-compose.inc succeeded >Mar 9 11:49:56 kab302-laborant keytable: ^[[73G >Mar 9 11:49:56 kab302-laborant keytable: [ >Mar 9 11:49:56 kab302-laborant keytable: ^[[1m^[[32m >Mar 9 11:49:56 kab302-laborant keytable: DONE >Mar 9 11:49:56 kab302-laborant keytable: ^[[39;49m^[[0;10m >Mar 9 11:49:56 kab302-laborant keytable: The BackSpace key sends: ^? loading delete.inc >Mar 9 11:49:56 kab302-laborant dbus[3851]: [system] Successfully activated service 'fi.epitest.hostap.WPASupplicant' >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> dhcpcd started with pid 4315 >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. >Mar 9 11:49:56 kab302-laborant dhcpcd[4315]: eth0: dhcpcd 4.0.15 starting >Mar 9 11:49:56 kab302-laborant loadkeys: Loading /lib/kbd/keymaps/i386/include/delete.inc.gz >Mar 9 11:49:56 kab302-laborant setsyskeytable: The BackSpace key sends: ^? loading delete.inc succeeded >Mar 9 11:49:56 kab302-laborant keytable: ^[[73G >Mar 9 11:49:56 kab302-laborant keytable: [ >Mar 9 11:49:56 kab302-laborant keytable: ^[[1m^[[32m >Mar 9 11:49:56 kab302-laborant keytable: DONE >Mar 9 11:49:56 kab302-laborant keytable: ^[[39;49m^[[0;10m >Mar 9 11:49:56 kab302-laborant NetworkManager[3989]: <info> (eth0): DHCPv4 state changed nbi -> preinit >Mar 9 11:49:56 kab302-laborant rc: Starting keytable: succeeded >Mar 9 11:49:56 kab302-laborant dhcpcd[4315]: eth0: broadcasting for a lease >Mar 9 11:49:56 kab302-laborant dm: rundm startup succeeded >Mar 9 11:49:57 kab302-laborant dhcpcd[4315]: eth0: offered 192.168.112.228 from 192.168.112.112 >Mar 9 11:49:57 kab302-laborant dhcpcd[4315]: eth0: acknowledged 192.168.112.228 from 192.168.112.112 >Mar 9 11:49:57 kab302-laborant dhcpcd[4315]: eth0: leased 192.168.112.228 for 18748800 seconds >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> (eth0): DHCPv4 state changed preinit -> bound >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled... >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started... >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> address 192.168.112.228 >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> prefix 24 (255.255.255.0) >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> gateway 192.168.112.112 >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> nameserver '192.168.112.112' >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> domain name 'school' >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> Scheduling stage 5 >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> Done scheduling stage 5 >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete. >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... >Mar 9 11:49:57 kab302-laborant autofs: automount startup succeeded >Mar 9 11:49:57 kab302-laborant avahi-daemon[4549]: Found user '_avahi' (UID 106) and group '_avahi' (GID 116). >Mar 9 11:49:57 kab302-laborant avahi-daemon[4549]: Successfully dropped root privileges. >Mar 9 11:49:57 kab302-laborant avahi-daemon[4549]: avahi-daemon 0.6.28 starting up. >Mar 9 11:49:57 kab302-laborant avahi-daemon[4549]: Successfully called chroot(). >Mar 9 11:49:57 kab302-laborant avahi-daemon[4549]: Successfully dropped remaining capabilities. >Mar 9 11:49:57 kab302-laborant avahi-daemon[4549]: Loading service file /services/ssh.service. >Mar 9 11:49:57 kab302-laborant avahi-daemon[4549]: Loading service file /services/udisks.service. >Mar 9 11:49:57 kab302-laborant avahi-daemon[4549]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.112.228. >Mar 9 11:49:57 kab302-laborant avahi-daemon[4549]: New relevant interface eth0.IPv4 for mDNS. >Mar 9 11:49:57 kab302-laborant avahi-daemon[4549]: Network interface enumeration completed. >Mar 9 11:49:57 kab302-laborant avahi-daemon[4549]: Registering new address record for 192.168.112.228 on eth0.IPv4. >Mar 9 11:49:57 kab302-laborant avahi-daemon[4549]: Registering HINFO record with values 'I686'/'LINUX'. >Mar 9 11:49:57 kab302-laborant avahi-daemon: avahi-daemon startup succeeded >Mar 9 11:49:57 kab302-laborant rc.sysinit: Mounting proc filesystem: succeeded >Mar 9 11:49:57 kab302-laborant rc.sysinit: Mounting sys filesystem: succeeded >Mar 9 11:49:57 kab302-laborant udevd: udevd startup succeeded >Mar 9 11:49:57 kab302-laborant udevd: Populating /dev: succeeded >Mar 9 11:49:57 kab302-laborant rc.sysinit: Activating swap partitions: succeeded >Mar 9 11:49:57 kab302-laborant rc.sysinit: Setting hostname kab302-laborant.local: succeeded >Mar 9 11:49:57 kab302-laborant fsck: /dev/sda2: clean, 91233/589824 files, 813594/2359296 blocks >Mar 9 11:49:57 kab302-laborant rc.sysinit: Checking root filesystem succeeded >Mar 9 11:49:57 kab302-laborant rc.sysinit: Remounting root filesystem in read/write mode: succeeded >Mar 9 11:49:57 kab302-laborant clock: Setting system clock (localtime): succeeded >Mar 9 11:49:57 kab302-laborant clock: Today's date: Fri Mar 9 11:49:44 YEKT 2012 succeeded >Mar 9 11:49:57 kab302-laborant rc.sysinit: Finding module dependencies: succeeded >Mar 9 11:49:57 kab302-laborant rc.sysinit: Configuring kernel parameters: succeeded >Mar 9 11:49:57 kab302-laborant vgchange: No volume groups found >Mar 9 11:49:57 kab302-laborant lvm_start: Setting up LVM2: succeeded >Mar 9 11:49:57 kab302-laborant fsck: /dev/sda5: clean, 5684/189696 files, 292335/758272 blocks >Mar 9 11:49:57 kab302-laborant rc.sysinit: Checking filesystems succeeded >Mar 9 11:49:57 kab302-laborant rc.sysinit: Mounting local filesystems: succeeded >Mar 9 11:49:57 kab302-laborant rc.sysinit: Checking loopback filesystems: succeeded >Mar 9 11:49:57 kab302-laborant rc.sysinit: Mounting loopback filesystems: succeeded >Mar 9 11:49:57 kab302-laborant rc.sysinit: Cleaning up temporary files from previous boot: succeeded >Mar 9 11:49:57 kab302-laborant rc.sysinit: Activating swap space: succeeded >Mar 9 11:49:57 kab302-laborant rc.sysinit: Updating chrooted environments: succeeded >Mar 9 11:49:57 kab302-laborant init: Entering runlevel: 5 >Mar 9 11:49:57 kab302-laborant x11presetdrv: Preparing X11 drivers succeeded >Mar 9 11:49:57 kab302-laborant alteratord: alteratord startup succeeded >Mar 9 11:49:57 kab302-laborant messagebus: dbus-daemon startup succeeded >Mar 9 11:49:57 kab302-laborant network: Computing interface groups: >Mar 9 11:49:57 kab302-laborant network: . >Mar 9 11:49:57 kab302-laborant network: 1 interfaces found >Mar 9 11:49:57 kab302-laborant network: Starting group 0/virtual (1 interfaces) >Mar 9 11:49:57 kab302-laborant network: ^IStarting lo: >Mar 9 11:49:57 kab302-laborant network: . >Mar 9 11:49:57 kab302-laborant last message repeated 3 times >Mar 9 11:49:57 kab302-laborant network: OK >Mar 9 11:49:57 kab302-laborant network: Processing /etc/net/vlantab: empty. >Mar 9 11:49:57 kab302-laborant rc: Starting network: succeeded >Mar 9 11:49:57 kab302-laborant NetworkManager: Setting network parameters: succeeded >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> NetworkManager (version 0.8.6) is starting... >Mar 9 11:49:57 kab302-laborant NetworkManager[3989]: <info> Read config file /etc/NetworkManager/NetworkManager.conf >Mar 9 11:49:57 kab302-laborant NetworkManager: NetworkManager startup succeeded >Mar 9 11:49:57 kab302-laborant bluetoothd[4039]: Bluetooth deamon 4.93 >Mar 9 11:49:57 kab302-laborant bluetoothd: bluetoothd startup succeeded >Mar 9 11:49:57 kab302-laborant bluetoothd[4039]: Starting SDP server >Mar 9 11:49:57 kab302-laborant rpcbind: cannot create socket for udp6 >Mar 9 11:49:58 kab302-laborant rpcbind: cannot create socket for tcp6 >Mar 9 11:49:58 kab302-laborant rpcbind: rpcbind startup succeeded >Mar 9 11:49:58 kab302-laborant random: Initializing random number generator: succeeded >Mar 9 11:49:58 kab302-laborant NetworkManager[3989]: <info> VPN: loaded org.freedesktop.NetworkManager.l2tp >Mar 9 11:49:58 kab302-laborant NetworkManager[3989]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp >Mar 9 11:49:58 kab302-laborant NetworkManager[3989]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn >Mar 9 11:49:58 kab302-laborant NetworkManager[3989]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc >Mar 9 11:49:58 kab302-laborant NetworkManager[3989]: <info> trying to start the modem manager... >Mar 9 11:49:58 kab302-laborant dbus[3851]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) >Mar 9 11:49:58 kab302-laborant dbus[3851]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper) >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> ModemManager (version 0.5) starting... >Mar 9 11:49:58 kab302-laborant dbus[3851]: [system] Successfully activated service 'org.freedesktop.ModemManager' >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin MotoC >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin X22X >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin Novatel >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin Gobi >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin SimTech >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin ZTE >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin Longcheer >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin Linktop >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin AnyData >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin Nokia >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin Option >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin Wavecom >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin Ericsson MBM >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin Sierra >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin Option High-Speed >Mar 9 11:49:58 kab302-laborant NetworkManager[3989]: <info> (eth0): writing resolv.conf to /sbin/resolvconf >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin Generic >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin Samsung >Mar 9 11:49:58 kab302-laborant modem-manager[4134]: <info> Loaded plugin Huawei >Mar 9 11:49:58 kab302-laborant sshd[4631]: Server listening on 0.0.0.0 port 22. >Mar 9 11:49:58 kab302-laborant sshd: sshd startup succeeded >Mar 9 11:49:58 kab302-laborant avahi-daemon[4549]: Server startup complete. Host name is kab302-laborant.local. Local service cookie is 1358837361. >Mar 9 11:49:59 kab302-laborant avahi-daemon[4549]: Got SIGHUP, reloading. >Mar 9 11:49:59 kab302-laborant avahi-daemon: Reloading Avahi mDNS/DNS-SD service: succeeded >Mar 9 11:49:59 kab302-laborant NetworkManager[3989]: <info> (eth0): device state change: 7 -> 8 (reason 0) >Mar 9 11:49:59 kab302-laborant avahi-daemon[4549]: Service "kab302-laborant" (/services/udisks.service) successfully established. >Mar 9 11:49:59 kab302-laborant avahi-daemon[4549]: Service "kab302-laborant" (/services/ssh.service) successfully established. >Mar 9 11:49:59 kab302-laborant NetworkManager[3989]: <info> Policy set 'System eth0' (eth0) as default for IPv4 routing and DNS. >Mar 9 11:49:59 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) successful, device activated. >Mar 9 11:49:59 kab302-laborant dbus[3851]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) >Mar 9 11:49:59 kab302-laborant NetworkManager[3989]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. >Mar 9 11:49:59 kab302-laborant dbus[3851]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' >Mar 9 11:50:00 kab302-laborant cups: cupsd startup succeeded >Mar 9 11:50:00 kab302-laborant ntpd: ntpd startup succeeded >Mar 9 11:50:01 kab302-laborant ntpd[4880]: dispatch_imsg in main: pipe closed >Mar 9 11:50:01 kab302-laborant ntpd[4880]: Terminating >Mar 9 11:50:01 kab302-laborant virtualbox: Loading VirtualBox module (vboxdrv): succeeded >Mar 9 11:50:01 kab302-laborant virtualbox: Loading VirtualBox module (vboxpci): succeeded >Mar 9 11:50:01 kab302-laborant ntpd: ntpd shutdown succeeded >Mar 9 11:50:01 kab302-laborant ntpd: ntpd startup succeeded >Mar 9 11:50:01 kab302-laborant virtualbox: Loading VirtualBox module (vboxnetflt): succeeded >Mar 9 11:50:01 kab302-laborant virtualbox: Loading VirtualBox module (vboxnetadp): succeeded >Mar 9 11:50:02 kab302-laborant nmb: nmbd startup succeeded >Mar 9 11:50:03 kab302-laborant smb: smbd startup succeeded >Mar 9 11:50:04 kab302-laborant plymouth: Deactivating splash succeeded >Mar 9 11:50:06 kab302-laborant dbus[3851]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper) >Mar 9 11:50:06 kab302-laborant dbus[3851]: [system] Successfully activated service 'org.freedesktop.ConsoleKit' >Mar 9 11:50:11 kab302-laborant gnome-keyring-daemon[5432]: GLib-GIO: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. >Mar 9 11:50:11 kab302-laborant gnome-keyring-daemon[5432]: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files >Mar 9 11:50:11 kab302-laborant last message repeated 2 times >Mar 9 11:50:13 kab302-laborant gnome-keyring-daemon[5432]: The Secret Service was already initialized >Mar 9 11:50:15 kab302-laborant gnome-keyring-daemon[5432]: The SSH agent was already initialized >Mar 9 11:50:19 kab302-laborant gnome-keyring-daemon[5432]: The GPG agent was already initialized >Mar 9 11:50:25 kab302-laborant gnome-keyring-daemon[5432]: The PKCS#11 component was already initialized >Mar 9 11:50:26 kab302-laborant dbus[3851]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper) >Mar 9 11:50:26 kab302-laborant dbus[3851]: [system] Activating service name='org.freedesktop.UDisks' (using servicehelper) >Mar 9 11:50:26 kab302-laborant dbus[3851]: [system] Successfully activated service 'org.freedesktop.UDisks' >Mar 9 11:50:26 kab302-laborant dbus[3851]: [system] Successfully activated service 'org.freedesktop.UPower' >Mar 9 11:50:34 kab302-laborant pulseaudio[5645]: pid.c: Daemon already running. >Mar 9 11:50:35 kab302-laborant dbus[3851]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper) >Mar 9 11:50:36 kab302-laborant blueman-mechanism: Starting blueman-mechanism >Mar 9 11:50:36 kab302-laborant dbus[3851]: [system] Successfully activated service 'org.blueman.Mechanism' >Mar 9 11:50:37 kab302-laborant blueman-mechanism: reload 0 0 >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 27009
:
5359
| 5369