Description of problem: In details view mode with Thunar (http://launchpadlibrarian.net/40868278/Gigolo.png), if I enter a subdirectory by using the mouse, once inside I cannot interact with any file or directory: selecting by single-click and launching by double-click don't work, and right-click displays a context menu as if the mouse pointer is over an empty area (i.e. not over an entry). Version-Release number of selected component (if applicable): gtk+ 2.19 & 2.20 How reproducible: Problem occurs with files detail view in thunar. Steps to Reproduce: 1. Show file details in thunar via detail view 2. 3. Actual results: Thunar does not recognize any mouse clicks or presses of enter key. Expected results: Thunar opens folder or file that was clicked. Additional info: Bug is known: https://bugzilla.gnome.org/show_bug.cgi?id=612802 See also here: http://bugs.archlinux.org/task/18904
Work around: http://bugzilla.xfce.org/attachment.cgi?id=2940 http://bugzilla.xfce.org/show_bug.cgi?id=6230#c11 Please provide a package for testing, so I can check the patch against Fedora.
This bug also affects pcmanfm. I think it first surfaced after updating to gtk2-2.20.0-1.fc13.i686 about a week ago (and I've been using nautilus since then). also see: http://bugs.archlinux.org/task/18904?project=1
This is a patch to the 'exo' package. I didn't see this bug as it's against gtk2 until someone pointed it out to me on irc. ;) Note that this 'fix' isn't really a fix... it's a workaround for changed behavior in gtk2. http://koji.fedoraproject.org/koji/taskinfo?taskID=2135748 has a scratch build exo if you want to test it/use it as a workaround.
http://koji.fedoraproject.org/koji/taskinfo?taskID=2135766 is a rawhide scratch build as well.
WorksForMe - thanks Kevin.
(In reply to comment #3) > This is a patch to the 'exo' package. So change Component to exo or at least thunar? > I didn't see this bug as it's against > gtk2 until someone pointed it out to me on irc. ;) No claims here. Someone = Me ;)
(In reply to comment #3) > http://koji.fedoraproject.org/koji/taskinfo?taskID=2135748 > > has a scratch build exo if you want to test it/use it as a workaround. The x86_64 package is linked against i686 dependencies?
Created attachment 409006 [details] Output of " yum localinstall --nogpgcheck Downloads/exo-0.3.106-3.fc13.x86_64.rpm " x86_64 package linked against i686 dependencies?
(In reply to comment #4) > http://koji.fedoraproject.org/koji/taskinfo?taskID=2135766 is a rawhide scratch > build as well. The same problem as stated in comments #7 and #8 for f14 package.
Your attachment seems to be some kind of xml bookmarks file? Can you try again uploading the yum output?
Created attachment 409090 [details] yum localinstall --nogpgcheck Downloads/exo-0.3.106-3.fc13.x86_64.rpm > exo.log oops ... how could that happen? now (hopefully) the right log
Raphael: No idea why the i686 is being pulled in there. How about just doing a 'rpm -Uvh exo*.rpm' ?
(In reply to comment #3) > http://koji.fedoraproject.org/koji/taskinfo?taskID=2135748 > > has a scratch build exo if you want to test it/use it as a workaround. Works for me then. Although, I am using rawhide.
f13's Thunar is still affected by this bug outofthebox. no exo update.
exo-0.3.106-3.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/exo-0.3.106-3.fc13
(In reply to comment #14) @Jason: The patch from comment #4 did fix the bug for me in Fedora 13. Can you confirm this?
(In reply to comment #16) > (In reply to comment #14) > @Jason: The patch from comment #4 did fix the bug for me in Fedora 13. Can you > confirm this? indeed it did.
*** Bug 593508 has been marked as a duplicate of this bug. ***
exo-0.3.106-3.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug seems to be fixed.