GNOME Bugzilla – Bug 512864
burn: doesn't support monitoring
Last modified: 2018-09-21 16:17:12 UTC
When I start nautilus I have this warning ** WARNING **: Unable to add monitor: Not supported but except than this message I have no problem, I don't know if it is specific to GIO. please find hereunder the gdb stacktrace when running with --g-fatal-warnings [New Thread 0xb68cab90 (LWP 14180)] ** WARNING **: Unable to add monitor: Not supported aborting... Program received signal SIGTRAP, Trace/breakpoint trap. [Switching to Thread 0xb6ad96c0 (LWP 14174)] IA__g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_WARNING, format=0xb60c8236 "Unable to add monitor: %s", args1=0xbfdd804c "�CG\bpSl� \0255�h\200ݿ\0250l�") at /build/buildd/glib2.0-2.15.4/glib/gmessages.c:503 503 /build/buildd/glib2.0-2.15.4/glib/gmessages.c: No such file or directory. in /build/buildd/glib2.0-2.15.4/glib/gmessages.c (gdb) thread apply all bt
+ Trace 187231
Thread 1 (Thread 0xb6ad96c0 (LWP 14174))
Confirming, I get the same warning on 2.21.90.
The warning is from nautilus-cd-burner due to burn: not yet supporting monitoring
Are there any plans to implement this? I was trying to do some work on nautilus-cd-burner and hit a snag because of this.
Its in the queue, but more important things keep getting ahead of it.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/33.