Hi, Well, if you could do the following for me it will make things easier:
(1) install audacious-dbg, audacious-plugins-dbg, libglib2.0-0-dbg (2) gdb audacious (3) inside gdb, "br g_return_if_fail_warning" (4) inside gdb, "run --no-log" (5) continue each time this call is made until you find the message that is giving you the trouble Thanks. William On Mon, 2008-07-21 at 17:15 -0700, Alex Malinovich wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > William Pitcock wrote: > | severity 491655 important > | thanks > | > | Thank you for taking the time to report a bug in Audacious in Debian and > | thus make it better. > | > | This is not a critical bug however. :) > > As I said in the bug report, it's probably not what would typically > qualify as critical. :) However, in my particular case it did cause me > to lose an entire POP3 mailbox in Evolution since the file couldn't be > written to disk, hence the critical marking. (thankfully the mailbox was > a mailing list archive so no major damage, but it could have been rather > bad) > > Severity notwithstanding, I'd love to hear any idea on things I can > check to make the error go away. I'm getting tired of checking my > audacious log file every 30 minutes for fear of losing more data that's > waiting to be written to disk. (It's growing at about 1GB every 30 > minutes, and I have about 1 GB of space available on that partition.) > I'm considering making log a symlink to /dev/null and seeing if that > works while I'm waiting for this to get resolved. I haven't found a way > to tell Audacious to just not do any logging in the meantime. Any > suggestions would be greatly appreciated. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.8 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkiFJpwACgkQBPYwh6bSSDcNEgCffiosIjguyOJGBOgFU7kgqiia > XcMAniX+cc0MaCT8JovscIumvcKxVQ5x > =CkHd > -----END PGP SIGNATURE----- >
signature.asc
Description: This is a digitally signed message part
