ports/177226: glib update: gnome-gmail-notifier won't start and nautilus eats cpu
Eimar Koort
eimar.koort at gmail.com
Fri Mar 22 09:30:00 UTC 2013
>Number: 177226
>Category: ports
>Synopsis: glib update: gnome-gmail-notifier won't start and nautilus eats cpu
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Mar 22 09:30:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Eimar Koort
>Release: 9.1-RELEASE
>Organization:
>Environment:
FreeBSD box 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
glib-2.34.3
glibmm-2.34.1,1
gnome-gmail-notifier-0.10.1_3
nautilus-2.32.2.1_3
1)
eimar at box: ~ > gnome-gmail-notifier
GLib (gthread-posix.c): Unexpected error from C library during 'pthread_mutex_unlock': Operation not permitted. Aborting.
eimar at box: ~ >
2)
Nautilus is constantly using cpu (taken from "top" command):
load averages: 0.78, 0.84, 0.90
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
95338 eimar 5 23 0 519M 115M wait 1 445:20 14.45% nautilus
I'm not sure how both problems are related, but both appeared right after glib update from 2.28.8_5 to 2.34.3.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list