Hi, I had a bit of trouble after doing the above with preupgrade, because of pre-existing rpm fusion nvidia kmod driver. After moving to nouveau, to get the GUI going, I have noticed two weird things: ===== nautilus: just doesn't start: 0$ time nautilus --browser
(nautilus:14701): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(nautilus:14701): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
real 0m50.127s user 0m0.026s sys 0m0.010s
===== investigating, I noticed packagecleanup --problems showed problems with tigervnc: http://fedora.pastebin.com/m4734c0fe
Seems tigervnc needs a higher nvr pushed into fedora12updates - doesn't seem to be in update-testing either. ===== Ideas ?
Sorry, I'm currently internet challenged, and can't even get a bugzilla page to complete load, but mil is OK.
On 11/14/2009 07:55 PM, David Timms wrote:
Hi, I had a bit of trouble after doing the above with preupgrade, because of pre-existing rpm fusion nvidia kmod driver. After moving to nouveau, to get the GUI going, I have noticed two weird things: ===== nautilus: just doesn't start: 0$ time nautilus --browser
(nautilus:14701): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(nautilus:14701): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
real 0m50.127s user 0m0.026s sys 0m0.010s
===== after install of debuginfo packages (all night), gdb gives me: $ gdb nautilus GNU gdb (GDB) Fedora (7.0-3.fc12) Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-redhat-linux-gnu". For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/nautilus...Reading symbols from /usr/lib/debug/usr/bin/nautilus.debug...done. done. (gdb) r Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] warning: .dynamic section for "/usr/lib/libtdb.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgvfscommon.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libudev.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations [New Thread 0xb7dd0b70 (LWP 2942)] [Thread 0xb7dd0b70 (LWP 2942) exited]
(nautilus:2939): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(nautilus:2939): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [New Thread 0xb7dd0b70 (LWP 2943)] [New Thread 0xb71ffb70 (LWP 2944)] [Thread 0xb7dd0b70 (LWP 2943) exited] [Thread 0xb71ffb70 (LWP 2944) exited]
Program exited normally. (gdb) ===== # rpm -Va *dbus* is silent.
How would you begin to debug this or if that isn't worth the effort, do you think a yum reinstall of dbus or nautilus would solve it ?
Cheers, DaveT.
On 11/15/2009 10:53 PM, David Timms wrote:
How would you begin to debug this or if that isn't worth the effort, do
... OK, during that 50 seconds of doing nothing I hit ctrl-c and get bt: ^C Program received signal SIGINT, Interrupt. 0x0028b424 in __kernel_vsyscall () (gdb) thread apply all bt
Thread 2 (Thread 0xb7dd0b70 (LWP 3114)): #0 0x0028b424 in __kernel_vsyscall () #1 0x006f1f72 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_timedwait.S:179 #2 0x00d68f3f in g_cond_timed_wait_posix_impl (cond=<value optimized out>, entered_mutex=<value optimized out>, abs_time=<value optimized out>) at gthread-posix.c:242 #3 0x007357cc in g_async_queue_pop_intern_unlocked (queue=0x827dfc8, try=<value optimized out>, end_time=<value optimized out>) at gasyncqueue.c:365 #4 0x007358e6 in IA__g_async_queue_timed_pop (queue=<value optimized out>, end_time=<value optimized out>) at gasyncqueue.c:491 #5 0x00787046 in g_thread_pool_wait_for_new_pool () at gthreadpool.c:121 #6 g_thread_pool_thread_proxy () at gthreadpool.c:324 #7 0x00785a40 in g_thread_create_proxy (data=<value optimized out>) at gthread.c:635 #8 0x006edab5 in start_thread (arg=<value optimized out>) at pthread_create.c:297 #9 0x00ed883e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Thread 1 (Thread 0xb7fd1790 (LWP 3111)): #0 0x0028b424 in __kernel_vsyscall () #1 0x00ecde46 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0x00a44d6c in _dbus_poll (fds=<value optimized out>, n_fds=<value optimized out>, timeout_milliseconds=<value optimized out>) at dbus-sysdeps-unix.c:1976 #3 0x00a3cabf in socket_do_iteration (transport=<value optimized out>, flags=<value optimized out>, timeout_milliseconds=<value optimized out>) at dbus-transport-socket.c:1066 #4 0x00a3ac4c in _dbus_transport_do_iteration ( transport=<value optimized out>, flags=<value optimized out>, timeout_milliseconds=<value optimized out>) at dbus-transport.c:956 #5 0x00a24fd3 in _dbus_connection_do_iteration_unlocked ( connection=<value optimized out>, flags=6, timeout_milliseconds=<value optimized out>) at dbus-connection.c:1163 #6 0x00a27793 in _dbus_connection_block_pending_call ( pending=<value optimized out>) at dbus-connection.c:2421 #7 0x00a35312 in dbus_pending_call_block (pending=<value optimized out>) at dbus-pending-call.c:705 #8 0x00da4010 in dbus_g_proxy_end_call_internal (proxy=<value optimized out>, call_id=<value optimized out>, error=0xbffff528, first_arg_type=64, args= ---Type <return> to continue, or q <return> to quit--- 0xbffff4ec ",\365\377\277") at dbus-gproxy.c:2272 #9 0x00da4a7a in dbus_g_proxy_call (proxy=0x8273488 [DBusGProxy], method= 0x6de7584 "SendMessage", error=0xbffff528, first_arg_type=64) at dbus-gproxy.c:2601 #10 0x06de6360 in org_gtk_UniqueApp_send_message (error=<value optimized out>, OUT_response=<value optimized out>, IN_time=<value optimized out>, IN_message=<value optimized out>, IN_command=<value optimized out>, proxy=<value optimized out>) at uniquebackend-glue.h:32 #11 unique_backend_dbus_send_message (error=<value optimized out>, OUT_response=<value optimized out>, IN_time=<value optimized out>, IN_message=<value optimized out>, IN_command=<value optimized out>, proxy=<value optimized out>) at uniquebackend-dbus.c:206 #12 0x06de2f4b in unique_backend_send_message (backend= 0x8275918 [UniqueBackendDBus], command_id=1, message_data=0x828f6b0, time_= 1258286563) at ./uniquebackend.c:286 #13 0x06de1c97 in unique_app_send_message (app=0x82758f0 [UniqueApp], command_id=1, message_data=0x0) at ./uniqueapp.c:700 #14 0x0806d36a in nautilus_application_startup ( application=<value optimized out>, kill_shell=<value optimized out>, no_default_window=<value optimized out>, no_desktop=<value optimized out>, browser_window=<value optimized out>, geometry=<value optimized out>, urls=<value optimized out>) at nautilus-application.c:895 #15 0x0807ebbd in main (argc=1, argv=0xbffff8b4) at nautilus-main.c:530 ===== Is that any help ?
On 11/15/2009 11:04 PM, he who yodels into the -test abys without answers wrote:
I wish I could get nautilus working again, sigh...
Any pointers, hints much appreciated.
Cheers, DaveT.
On 11/16/2009 05:05 AM, David Timms wrote:
On 11/15/2009 11:04 PM, he who yodels into the -test abys without answers wrote:
I wish I could get nautilus working again, sigh...
Any pointers, hints much appreciated.
You said somewhere that "rpm -Va *dbus*" was silent. Are you sure all dbus things are installed. On my nouveau-based beast:
dbus-devel-1.2.12-2.fc11.x86_64 dbus-1.2.12-2.fc11.x86_64 dbus-glib-0.80-2.fc11.x86_64 ndesk-dbus-glib-0.4.1-5.fc11.x86_64 dbus-python-0.83.0-5.fc11.x86_64 dbus-x11-1.2.12-2.fc11.x86_64 python-slip-dbus-0.1.15-3.fc11.noarch dbus-libs-1.2.12-2.fc11.x86_64 dbus-glib-devel-0.80-2.fc11.x86_64 ndesk-dbus-0.6.1a-6.fc11.x86_64
are all installed, so I'd check all of them. Also verify that dbus-daemon is running (it's launched via /etc/rc.d/init.d/messagebus). ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer ricks@nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - The light at the end of the tunnel is really an oncoming train. - ----------------------------------------------------------------------
On 11/17/2009 05:43 AM, Rick Stevens wrote:
On 11/16/2009 05:05 AM, David Timms wrote:
On 11/15/2009 11:04 PM, he who yodels into the -test abys without answers wrote:
I wish I could get nautilus working again, sigh...
Any pointers, hints much appreciated.
You said somewhere that "rpm -Va *dbus*" was silent. Are you sure all dbus things are installed. On my nouveau-based beast:
dbus-devel-1.2.12-2.fc11.x86_64 dbus-1.2.12-2.fc11.x86_64 dbus-glib-0.80-2.fc11.x86_64 ndesk-dbus-glib-0.4.1-5.fc11.x86_64 dbus-python-0.83.0-5.fc11.x86_64 dbus-x11-1.2.12-2.fc11.x86_64 python-slip-dbus-0.1.15-3.fc11.noarch dbus-libs-1.2.12-2.fc11.x86_64 dbus-glib-devel-0.80-2.fc11.x86_64 ndesk-dbus-0.6.1a-6.fc11.x86_64
Firstly, Rick, thanks for the reply. Well, I'm on the F12 beta, with updates so: # rpm -qa *dbus*|sort dbus-1.2.16-8.fc12.i686 dbus-debuginfo-1.2.16-8.fc12.i686 dbus-devel-1.2.16-8.fc12.i686 dbus-glib-0.82-2.fc12.i686 dbus-glib-debuginfo-0.82-2.fc12.i686 dbus-glib-devel-0.82-2.fc12.i686 dbus-libs-1.2.16-8.fc12.i686 dbus-python-0.83.0-6.fc12.i686 dbus-qt-0.70-7.fc12.i686 dbus-x11-1.2.16-8.fc12.i686 eggdbus-0.5-2.i686 ndesk-dbus-0.6.1a-8.fc12.i686 ndesk-dbus-glib-0.4.1-8.fc12.i686 python-slip-dbus-0.2.7-1.fc12.noarch
So, looks like I have all you have (for F11), and more.
are all installed, so I'd check all of them. Also verify that dbus-daemon is running (it's launched via /etc/rc.d/init.d/messagebus).
# ps uax|grep dbus dbus 1436 0.0 0.0 14044 2192 ? Ssl Nov16 0:00 dbus-daemon --system gdm 1988 0.0 0.0 3496 580 ? S Nov16 0:00 /usr/bin/dbus-launch --exit-with-session davidt 2076 0.0 0.0 3496 584 ? S Nov16 0:00 dbus-launch --sh-syntax --exit-with-session davidt 2077 0.0 0.0 13596 1504 ? Ssl Nov16 0:00 /bin/dbus-daemon --fork --print-pid 7 --print-address 9 --session root 4750 0.0 0.0 4208 712 pts/2 S+ 23:40 0:00 grep dbus
Does that seem normal ? The 0:00 activity time seems small, but I'm not up on the details of dbus.
DaveT.
On 11/17/2009 11:44 PM, David Timms wrote:
# ps uax|grep dbus dbus 1436 0.0 0.0 14044 2192 ? Ssl Nov16 0:00 dbus-daemon --system gdm 1988 0.0 0.0 3496 580 ? S Nov16 0:00 /usr/bin/dbus-launch --exit-with-session davidt 2076 0.0 0.0 3496 584 ? S Nov16 0:00 dbus-launch --sh-syntax --exit-with-session davidt 2077 0.0 0.0 13596 1504 ? Ssl Nov16 0:00 /bin/dbus-daemon --fork --print-pid 7 --print-address 9 --session root 4750 0.0 0.0 4208 712 pts/2 S+ 23:40 0:00 grep dbus
Does that seem normal ? The 0:00 activity time seems small, but I'm not up on the details of dbus.
I also notice that the icons on my desktop are not being drawn. What is the solution ?