Date: Tue, 28 Nov 2017 20:19:41 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 199872] devel/glib20 Apps using glib 2.42.2 crashing with 'pthread_mutex_lock' abort Message-ID: <bug-199872-6497-cCS9iPGRLa@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-199872-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-199872-6497@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D199872 --- Comment #24 from rozhuk.im@gmail.com --- (In reply to Guido Falsi from comment #22) This is a very soft reaction from the user who lived almost a year without = any fam, another year the fam worked very poorly. And now, when there are two ready solutions to the problem, the community d= oes nothing at all. For a whole year the community can not decide to adopt a variant or add bot= h as options. It seems that the community does not care about not only users and their convenience, but even the developers who do something for the community. FreeBSD is not very popular, and with this attitude, the last users will tu= rn away from it. (In reply to Guido Falsi from comment #23) Original code have very bad design, it cant be fixed by series of one-line-patch. Also my code handle NOTE_RENAME more correct way: it try to find in up fold= er by inode and report deleted only if not found. Probably libinotify do same smart thing. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199872-6497-cCS9iPGRLa>