Attachment 85321 Details for Bug 69026 – Log and result

Log and result

dbus.log (text/plain), 9.44 KB, created by Yannick Lanz on 2013-09-06 11:01:51 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Yannick Lanz

Created: 2013-09-06 11:01:51 UTC

Size: 9.44 KB

patch

obsolete

><Launch DBus daemon>
>590: [dbus-dataslot.c(146):_dbus_data_slot_allocator_alloc] Allocated slot 0 on allocator 0x9c908 total 1 slots allocated 1 used
>590: [dbus-sysdeps-unix.c(2807):_dbus_generate_random_bytes] /dev/urandom fd 3 opened
>590: [dbus-sysdeps-unix.c(2817):_dbus_generate_random_bytes] Read 12 bytes from /dev/urandom
>590: [dbus-socket-set-poll.c(98):_dbus_socket_set_poll_new] new socket set at 0x9d108
>590: [dbus-file-unix.c(80):_dbus_file_get_contents] file fd 3 opened
>590: [dbus-sysdeps-unix.c(1024):_dbus_listen_unix_socket] listening on unix socket /var/run/dbus/system_bus_socket abstract=0
>590: [dbus-sysdeps-unix.c(157):_dbus_open_socket] socket fd 3 opened
>590: [dbus-sysdeps-unix.c(2807):_dbus_generate_random_bytes] /dev/urandom fd 4 opened
>590: [dbus-sysdeps-unix.c(2817):_dbus_generate_random_bytes] Read 12 bytes from /dev/urandom
>590: [dbus-server.c(159):_dbus_server_init_base] Initialized server on address unix:path=/var/run/dbus/system_bus_socket,guid=cc059503383c82f7fc891d7c52157f53
>590: [dbus-watch.c(313):_dbus_watch_list_set_functions] Adding a read watch on fd 3 using newly-set add watch function
>590: [dbus-socket-set-poll.c(146):socket_set_poll_add] before adding fd 3 to 0x9d108, 0 en/0 res/8 alloc
>590: [activation.c(626):update_directory] Failed to open directory /usr/share/dbus-1/system-services: Failed to read directory "/usr/share/dbus-1/system-services": No such file or directory
>590: [activation.c(626):update_directory] Failed to open directory /lib/dbus-1/system-services: Failed to read directory "/lib/dbus-1/system-services": No such file or directory
>590: [dbus-dataslot.c(146):_dbus_data_slot_allocator_alloc] Allocated slot 0 on allocator 0x9c8ac total 1 slots allocated 1 used
>590: [dbus-userdb.c(166):_dbus_user_database_lookup] No cache for UID 0
>590: [dbus-userdb.c(156):_dbus_user_database_lookup] Using cache for UID 0 information
>590: [bus.c(861):bus_context_new] Forking and becoming daemon
>590: [dbus-sysdeps-util-unix.c(87):_dbus_become_daemon] Becoming a daemon...
>590: [dbus-sysdeps-util-unix.c(89):_dbus_become_daemon] chdir to /
>590: [dbus-sysdeps-util-unix.c(97):_dbus_become_daemon] forking...
>591: [dbus-sysdeps-util-unix.c(108):_dbus_become_daemon] in child, closing std file descriptors
>590: [dbus-sysdeps-util-unix.c(238):_dbus_write_pid_to_file_and_pipe] writing pid file /var/run/dbus.pid
>590: [dbus-sysdeps-util-unix.c(292):_dbus_write_pid_to_file_and_pipe] No pid pipe to write to
>590: [dbus-sysdeps-util-unix.c(152):_dbus_become_daemon] parent exiting
>
><Launch DBus test application>
>D-Bus bus testing application
>592: [dbus-bus.c(231):init_connections_unlocked] Filling in system bus address...
>592: [dbus-bus.c(249):init_connections_unlocked]   used default system bus "unix:path=/var/run/dbus/system_bus_socket"
>592: [dbus-bus.c(257):init_connections_unlocked] Filling in session bus address...
>592: [dbus-bus.c(263):init_connections_unlocked]   "unix:path=/tmp/dbus-9OO6rECL9p,guid=a2b95207021056f12f4d9fb352156a5c"
>592: [dbus-bus.c(268):init_connections_unlocked] Filling in activation bus address...
>592: [dbus-bus.c(275):init_connections_unlocked]   "none set"
>592: [dbus-connection.c(1851):_dbus_connection_open_internal] opening shared connection to: unix:path=/var/run/dbus/system_bus_socket
>592: [dbus-connection.c(1607):connection_lookup_shared] checking for existing connection
>592: [dbus-connection.c(1615):connection_lookup_shared] creating shared_connections hash table
>592: [dbus-connection.c(1634):connection_lookup_shared]   successfully created shared_connections
>592: [dbus-sysdeps-unix.c(799):_dbus_connect_unix_socket] connecting to unix socket /var/run/dbus/system_bus_socket abstract=0
>592: [dbus-sysdeps-unix.c(157):_dbus_open_socket] socket fd 3 opened
>592: [dbus-transport-unix.c(94):_dbus_transport_new_for_domain_socket] Successfully connected to unix socket /var/run/dbus/system_bus_socket
>592: [dbus-auth.c(2134):goto_state] client: going from state NeedSendAuth to state WaitingForData
>592: [dbus-transport.c(204):_dbus_transport_init_base] Initialized transport on address unix:path=/var/run/dbus/system_bus_socket
>592: [dbus-connection.c(1367):_dbus_connection_new_for_transport] LOCK
>592: [dbus-transport-socket.c(180):check_read_watch] fd = 3
>592: [dbus-transport-socket.c(226):check_read_watch]   setting read watch enabled = 0
>592: [dbus-transport-socket.c(165):check_write_watch] check_write_watch(): needed = 1 on connection 0x117c0 watch 0x11408 fd = 3 outgoing messages exist 0
>592: [dbus-connection.c(413):_dbus_connection_unlock] UNLOCK
>592: [dbus-connection.c(1882):_dbus_connection_open_internal] LOCK
>592: [dbus-connection.c(413):_dbus_connection_unlock] UNLOCK
>592: [dbus-dataslot.c(146):_dbus_data_slot_allocator_alloc] Allocated slot 0 on allocator 0x40090868 total 1 slots allocated 1 used
>592: [dbus-connection.c(3505):dbus_connection_send_with_reply_and_block] LOCK
>592: [dbus-connection.c(413):_dbus_connection_unlock] UNLOCK
>592: [dbus-connection.c(3370):dbus_connection_send_with_reply] LOCK
>592: [dbus-dataslot.c(146):_dbus_data_slot_allocator_alloc] Allocated slot 0 on allocator 0x400908b0 total 1 slots allocated 1 used
>592: [dbus-connection.c(2017):_dbus_connection_send_preallocated_unlocked_no_update] Message 0x11a18 (method_call /org/freedesktop/DBus org.freedesktop.DBus Hello '') for org.freedesktop.DBus added
>592: [dbus-connection.c(2033):_dbus_connection_send_preallocated_unlocked_no_update] Message 0x11a18 serial is 1
>592: [dbus-connection.c(1210):_dbus_connection_do_iteration_unlocked] start
>592: [dbus-connection.c(413):_dbus_connection_unlock] UNLOCK
>592: [dbus-connection.c(1081):_dbus_connection_acquire_io_path] locking io_path_mutex
>592: [dbus-connection.c(1085):_dbus_connection_acquire_io_path] start connection->io_path_acquired = 0 timeout = 0
>592: [dbus-connection.c(1128):_dbus_connection_acquire_io_path] end connection->io_path_acquired = 1 we_acquired = 1
>592: [dbus-connection.c(1130):_dbus_connection_acquire_io_path] unlocking io_path_mutex
>592: [dbus-connection.c(1133):_dbus_connection_acquire_io_path] LOCK
>592: [dbus-transport.c(966):_dbus_transport_do_iteration] Transport iteration flags 0x1 timeout -1 connected = 1
>592: [dbus-transport-socket.c(1047):socket_do_iteration]  iteration flags = write timeout = -1 read_watch = 0x11430 write_watch = 0x11408 fd = 3
>592: [dbus-transport-socket.c(1153):socket_do_iteration] in iteration, need_read=0 need_write=1
>592: [dbus-transport-socket.c(345):exchange_credentials] exchange_credentials: do_reading = 0, do_writing = 1
>592: [dbus-sysdeps-unix.c(1636):write_credentials_byte] wrote credentials byte
>592: [dbus-transport-socket.c(460):do_authentication]  client auth state: bytes to send
>592: [dbus-auth.c(2506):_dbus_auth_bytes_sent] client: Sent 18 bytes of: AUTH EXTERNAL 30
>
>592: [dbus-transport-socket.c(345):exchange_credentials] exchange_credentials: do_reading = 0, do_writing = 1
>592: [dbus-transport-socket.c(446):do_authentication]  client auth state: waiting for input
>592: [dbus-transport-socket.c(180):check_read_watch] fd = 3
>592: [dbus-transport-socket.c(226):check_read_watch]   setting read watch enabled = 1
>592: [dbus-transport-socket.c(165):check_write_watch] check_write_watch(): needed = 0 on connection 0x117c0 watch 0x11408 fd = 3 outgoing messages exist 1
>592: [dbus-transport-socket.c(503):do_writing] Not authenticated, not writing anything
>592: [dbus-transport-socket.c(165):check_write_watch] check_write_watch(): needed = 0 on connection 0x117c0 watch 0x11408 fd = 3 outgoing messages exist 1
>592: [dbus-transport-socket.c(1188):socket_do_iteration]  ... leaving do_iteration()
>592: [dbus-transport.c(980):_dbus_transport_do_iteration] end
>592: [dbus-connection.c(1154):_dbus_connection_release_io_path] locking io_path_mutex
>592: [dbus-connection.c(1160):_dbus_connection_release_io_path] start connection->io_path_acquired = 1
>592: [dbus-connection.c(1165):_dbus_connection_release_io_path] unlocking io_path_mutex
>592: [dbus-connection.c(1243):_dbus_connection_do_iteration_unlocked] end
>592: [dbus-connection.c(4222):_dbus_connection_get_dispatch_status_unlocked] dispatch status = complete is_connected = 1
>592: [dbus-connection.c(413):_dbus_connection_unlock] UNLOCK
>592: [dbus-connection.c(397):_dbus_connection_lock] LOCK
>592: [dbus-connection.c(413):_dbus_connection_unlock] UNLOCK
>592: [dbus-connection.c(397):_dbus_connection_lock] LOCK
>592: [dbus-connection.c(3572):_dbus_connection_flush_unlocked] doing iteration in
>592: [dbus-connection.c(1210):_dbus_connection_do_iteration_unlocked] start
>592: [dbus-connection.c(413):_dbus_connection_unlock] UNLOCK
>592: [dbus-connection.c(1081):_dbus_connection_acquire_io_path] locking io_path_mutex
>592: [dbus-connection.c(1085):_dbus_connection_acquire_io_path] start connection->io_path_acquired = 0 timeout = -1
>592: [dbus-connection.c(1128):_dbus_connection_acquire_io_path] end connection->io_path_acquired = 1 we_acquired = 1
>592: [dbus-connection.c(1130):_dbus_connection_acquire_io_path] unlocking io_path_mutex
>592: [dbus-connection.c(1133):_dbus_connection_acquire_io_path] LOCK
>592: [dbus-transport.c(966):_dbus_transport_do_iteration] Transport iteration flags 0x7 timeout -1 connected = 1
>592: [dbus-transport-socket.c(1047):socket_do_iteration]  iteration flags = readwrite timeout = -1 read_watch = 0x11430 write_watch = 0x11408 fd = 3
>592: [dbus-transport-socket.c(1120):socket_do_iteration] unlock pre poll
>592: [dbus-connection.c(413):_dbus_connection_unlock] UNLOCK
>
><DBus hangup after test application lauch>
>  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
>  586     1 root     R     2756  4.8   0 70.0 dbus-daemon --system

Actions: View

Attachments on bug 69026: 85321 | 85600 | 85689

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.