Date: Tue, 28 Nov 2017 19:02:31 +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-1HiWmpc7uj@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 #22 from Guido Falsi <madpilot@FreeBSD.org> --- (In reply to rozhuk.im from comment #21) > (In reply to Guido Falsi from comment #20) >=20 > > At present the glib20 port does not include an option to use inotify or= your patch. >=20 > Yes, and no one care this. > But patches for both case available. >=20 [...] >=20 > IMHO FreeBSD desktop is unusable with current glib fam. > We can discuss here what is right way to fix it, but users will migrate to > other OSes where developers fix problems. >=20 > This bug 2,5 years old, there is two stable solutions=3Dpathes and it doe= s not > commited/fixed yet. > In commercial or more an adequate community this situation is impossible! I am not a gnome committer I cannot decide which code should go in. I've not even said mine is better. In fact I don't know. You already stated you have another PR with a better solution, the people in charge of this port will choose what they prefer to commit. Please avoid this kind of aggressive posts. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199872-6497-1HiWmpc7uj>