Red Hat Bugzilla – Bug 815514
Thunar slow to open and prompts with an error
Last modified: 2012-04-23 15:27:06 EDT
Description of problem:
After upgrading, when I try to run Thunar, whether from the command line, menu, or icons on the Desktop I receive an error message the first time it runs:
The folder could not be opened
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.
After the first time I run Thunar the error message does not reappear until I reboot, however it still opens very slowly on subsequent runs.
Version-Release number of selected component (if applicable):
Seems 100%. I am affected on two different systems
Steps to Reproduce:
1. Install Fedora 17 with XFCE
2. Log into XFCE
3. Try to run Thunar
Wait several seconds, and get prompted with an error message.
Thunar opens quickly and without an error message.
How are you logging into Xfce? via gdm?
How did you upgrade? yum? media? which one?
It seems the samba4 packages are to blame for this. I just replaced them with the samba packages and things are working normally.
I upgraded using the DVD which replaced the samba packages I had installed with samba4 equivelants.
Cool. I think that should be fixed up soon... shall we keep this open and move it to samba4 for tracking, or just close it out?
It should be ok to close it. I ran across something in the Xfce bugzilla that made me think this might be network and therefore samba related, and now that I am looking I don't see the samba4 packages on the DVD.
I think I got these post upgrade running a yum update; it was trying to install some samba4 packages for dependencies even though I had samba (3.x) packages installed, which was causing the yum update to fail due to a conflict.
I think I uninstalled all the samba (3.x) packages at which point a yum update installed the samba4 packages to fulfill the dependencies. So hopefully not too many people will run into this, if at all.
Great. Thanks for the bug and detective work. ;)