Open Bug 728956 Opened 13 years ago Updated 13 years ago

gtk warnings when locating files

Categories

(SeaMonkey :: General, defect)

SeaMonkey 2.5 Branch
x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: grgoffe, Unassigned)

References

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0a1) Gecko/13.0a1 Firefox/13.0a1 SeaMonkey/2.10a1 Build ID: 20120218003027 Steps to reproduce: Attach a file via mail.yahoo.com Actual results: The file IS present and WAS found but I get these messages a LOT. (seamonkey:23483): Gtk-WARNING **: Unable to retrieve the file info for `file:///opt/incoming/GRGRes110801ux1x2.doc': Error stating file '/opt/incoming/GRGRes110801ux1x2.doc': No such file or directory Expected results: No messages.
Are you using Ubuntu? This sounds like Bug 722038 (Saving a page terminal shows Gtk-WARNING **: Unable to retrieve the file info for "filename")
See Also: → 722038
Philip, This system is Fedora (Core) 16 x86_64, as up to date as possible. It does look similar to 722038 but not exactly. This directory exists AND so does the file... AND, I'm uploading, not downloading. Hope this helps. Regards, George...
Google tells me that you may have some GTK debug settings turned on: http://developer.gnome.org/gtk/2.24/gtk-running.html#GTK-Debug-Options Do you have GTK_DEBUG in your environment and set to something?
Philip, What does Google have to say about this bug? Are they involved somehow? I do NOT have any debug settings enabled that I am aware of. Regards, George...
Philip, The problem happens with Firefox "nightly" also... Perhaps this is a GTK problem and NOT the browsers (seamonkey or firefox)? Regards, George...
Does this also happen with *other* GTK based programs? Google shows a wide variety of linux applications where this was reported in their support forums. Just Google for: Gtk-WARNING Unable to retrieve the file
Philip, The two browsers are the only GTK based programs I've seen these messages on. Do you have a list of others you'd like me to try? Regards, George...
Sorry no. but try asking on the Fedora forums. If they say this message is safe to ignore (warnings are usually ignorable).
Philip, This is a BUG that needs to be fixed! Regards, George...
Debug warnings are usually not "Bugs". It appears harmless. Does the message prevent attaching a file via mail.yahoo.com?
Philip, The operation(s) succeed but these messages clutter up the xterm where I start these browsers and sometimes interfere with whatever I'm doing in that xterm since some appear randomly. Regards, George...
Philip, In thinking about this problem, I think that the warnings about files not being present are incorrectly used. If a file does not exist, it merits a warning only when a read or move attempt is performed. Imagine getting a warning about every file you try to reference that doesn't exist. For example, commands like "cp file.a file.b" where file.b doesn't exist. If it doesn't exist, who cares? If I do care I can add the "-iv" flag. If it does exist and will be over written and I have NOT added the "-iv" flag then it'll be over written. Does this make sense? George...
Yes. As I said look in your ENV to see if GTK_DEBUG is set to something. http://developer.gnome.org/gtk/2.24/gtk-running.html#id465743
Philip, Did you see my comment #4 above here? George...
> Did you see my comment #4 above here? Y3s but you didn't explicitly say you checked GTK_DEBUG. I just want to make sure we are both on the same page not to mention the same book.
Philip, You're right to check. This problem seems readily recreatible would a trace help? (strace -xvf <cmd>) Regards, George...
I guess we need to see what the Firefox people come up with in Bug 722038. They have more resources than we do. I'm going to set a dependency so if that bug changes we'll know about it.
Depends on: 722038
See Also: 722038
(In reply to George R. Goffe from comment #11) > Philip, > > The operation(s) succeed but these messages clutter up the xterm where I > start these browsers and sometimes interfere with whatever I'm doing in that > xterm since some appear randomly. > > Regards, > > George... To avoid cluttering the xterm, you could use any of the following: a) Start from a desktop shortcut b) Redirect lo a logfile:
(unwittingly pressed Tab Space) b) redirect to a logfile seamonkey >> seamonkey.log 2>&1 c) redirect to /dev/null seamonkey > /dev/null 2>&1
Tony, Thanks for your response. It seems a better idea to turn off the warning(s). Your suggestion would make ALL messages disappear or add filesystem clutter with yet another log file. It seems to me that the logic is wrong. If you're writing to a file, why tell me that it doesn't exist? If you're reading a file, telling me that makes sense. George...
You need to log in before you can comment on or make changes to this bug.