Date: Sat, 12 Dec 2015 09:29:03 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: maintainer-feedback requested: [Bug 205265] sysutils/hal boots into unusable and unkillable state Message-ID: <bug-205265-6497-NwXJgKHbJX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-205265-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-205265-6497@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthias Apitz <guru@unixarea.de> has reassigned Bugzilla Automation <bugzilla@FreeBSD.org>'s request for maintainer-feedback to gnome@FreeBSD.o= rg: Bug 205265: sysutils/hal boots into unusable and unkillable state https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205265 --- Description --- Sometimes the hald started during boot goes into an unusable state which let for example the KDE power management system think that there is no battery;= =20 ps(1) shows the situation like this: 885 - Ds 0:00,01 /usr/local/sbin/hald 890 - I 0:00,03 hald-runner 764 v0- I 0:00,01 /usr/local/sbin/hald 988 v0 R 0:00,00 fgrep hal The proc (here 885) can not be killed, not even with -9, and a query for hal does not work: $ qdbus --system :1.2 org.freedesktop.ConsoleKit :1.25 :1.26 :1.27 :1.28 :1.3 :1.31 :1.32 :1.4 org.freedesktop.PolicyKit1 :1.40 org.freedesktop.DBus i.e. nothing about hald :-( This is with system r285885 and ports r392920 (July 26).=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205265-6497-NwXJgKHbJX>