GNOME Bugzilla – Bug 580617
Brasero floods .xsession-errors log with "Unknown (or already deleted) monitored directory" warnings
Last modified: 2009-08-26 18:55:04 UTC
Forwarding https://bugzilla.novell.com/show_bug.cgi?id=497778 =============== After burning an ISO image to a CD, Brasero ejected the CD-ROM properly, and I deleted the source ISO image. Brasero was not being very responsive so I left it up while I left the office for a couple of hours. After returning I found that my /home partition was out of disk space. Some investigation revealed that ~/.xsession-errors had grown to 4.5GB with a huge amount of the following messages: ** (brasero:8395): WARNING **: Unknown (or already deleted) monitored directory = > ignored ** (brasero:8395): WARNING **: Unknown (or already deleted) monitored directory = > ignored ** (brasero:8395): WARNING **: Unknown (or already deleted) monitored directory = > ignored I am not sure if the above warning is due to the deletion of the ISO image, but I deleted that image after the CD was ejected. Also, nothing should ever generate 4.5GB of the exact same error message. ===============
Thanks for the report. I tried to follow the instructions above but I wasn't able to reproduce the bug so there must be something else which I can't figure out. What I did though was make sure the warning would not be repeated and flood any log file. Now when a brasero receives a file notification for changes about a file he doesn't know, it will simply cancel any further notifications for this file (to avoid repeating of the warning message). While at it I also removed the warning message as it mainly served debugging purposes and was mainly harmless. So all in all, I fixed part of the bug: log file won't be flooded anymore but on the other hand I don't know why it started to write this message so many times. Now I'd really like to be able to reproduce the cause of the bug, that is why does brasero receives all these notifications in the first place for a file he apparently doesn't know? Have you got more instructions on how reproducing the bug please?
Asking in the bug downstream...
Reply from downstream: =========== Unfortunately, I cannot give you any more precise steps to duplicate the issue. I burned a couple of ISOs, and after the second one completed (and was automatically ejected), I tried to close down Brasero and found it unresponsive. As I was leaving for lunch, I didn't bother killing the process and just left it running (thinking it would probably close by itself). I did delete the source ISO image though, and then left. When I returned I found the problem documented in the original description. I agree that the original source of the problem would be nice to get resolved, but I'm afraid I cannot duplicate this issue at will, and it only happened once. The upstream fix does appear to resolve the end result of a huge log file though. =========== So I guess you can close the bug since your fix should mitigate the issue anyway.
Ok thanks, closing. Feel free to reopen if something new comes up (hopefully not).