GNOME Bugzilla – Bug 315938
Desktop does not update when a browser downloads a file to the desktop
Last modified: 2005-10-14 14:20:22 UTC
Version details: gamin-0.16 Distribution/Version: YDL-4.0.1 Experiment #1 -------------- * Download a file to the Desktop. ==> no file is seen. * Check the contents of the Desktop folder from the command line ==> file is there. * stop and start nautilus => downloaded file now appears on Desktop. Experiment #2 ------------- * Create a folder on the Desktop * Open Home folder * copy a file from Home folder to new folder. ==> works fine Experiment #3 ------------- * Retreat to garmin-0.15. * retry Experiment #1 ==> All is well. -Joseph
What version of the kernel ? inotify or dnotify being used ? Have you run the regression tests on your platform ? Works for me on RHEL4 with a dnotify kernel interface and 0.1.16. Daniel
Daniel, * I am running a 2.6.13 kernel. * gamin-0.1[56] were both configured with dnotify and inotify disabled: --disable-dnotify --disable-inotify * running "make check" at the top of the source tree: *** gamin-0.15 *** most everything worked except: dnotify12.py -- dnotify12.py Error got event 1 expected 2 Error: monitor2 got 4 events insteads of 5 dnotify13.py -- dnotify13.py Error got event 1 expected 2 Error: monitor2 got 4 events insteads of 5 ... flood4.py -- flood4.py Error got event 8 expected 9 Error got event 8 Error got event 8 Error got event 9 *** gamin-0.16 *** There were major problems: basic.py -- basic.py error basic2.py < the test hangs at this point> I can run additional tests, rebuild with a different configuration. What would you like me to try? -Joseph -Joseph
Why on earth did you disable dnotify !!! Makes no sense to me. Daniel
Daniel, The GARNOME build configures gamin to build only the polling back end. This choice of configuration has been in place for a while. I checked the archives on my system and see this configuration used back through the 2.10.x series. If this is the wrong thing to do, what is the right thing to do, given that GARNOME needs to build on N different linux variants. -Joseph
The right thing to do is to not select any back-end, the right one will be automatically picked up upon availability at the kernel level. Daniel
Thank you, Daniel. I will give that a try. I will also poll the GARNOME mailing list to see what experiences others are having with gamin-0.1[56], built within a GARNOME-2.12.0 framework. -Joseph
Daniel, I am going to chalk this one up to a "Twilight Zone" experience [queue the theme music]... I built a new kernel, 2.6.13.1, using the same .config file from previous built kernel, linux-2.6.13. I reviewed the Changelog posted on http://www.kernel.org, but nothing jumped out at me that would affect gamin running on a PPC under YDL-4.0.1, an FC2 clone. I built gamin-0.16. This time I did not pre-select any of the back-ends, letting configure determine what to build: backends: polling, inotify, dnotify I uninstalled gamin-0.15 and then installed gamin-0.16. The good news: * desktop weirdness has "gone away" * most of the regression tests now pass. There is one other mystery, which may remain a mystery. Prior to rebuilding the kernel, I ran some additional tests. I tried building both gamin-0.15 & gamin-0.16 with different back-end configurations. Eventually I got into a state that I could not recover from. When gamin-0.15 was again rebuilt with inotify and dnotify disabled, which previously "worked", the regression test suite failed: basic.py -- basic.py error basic2.py < the test hangs at this point> Cold booting the system did not help. If you have any insights into why this might happen, I would appreciate it if you would share them. If not, I will "shrug" and move on. -Joseph
You could have hit a mismatch in inotify between the temporary API of the kernel and the final one as released in 2.6.13 or somthing like that, otherwise no idea. Daniel
Daniel, Thanks for replying. I spoke too soon. It has "reappeared" again: desktop failing to update, regression tests failing in the same manner as before. I have no idea what's going on here. I posted a query to the garnome list to learn what others are seeing with GARNOME-2.12.0. I will poke at this some more when I have the free cycles. -Joseph
Daniel, I have built garnome-2.12.1 and the problem has "gone away". Maybe a something changed in nautilus or gnome-vfs. Who knows??? -Joseph