#12636: The notification server starts to peg one core of the cpu
-------------------------------------------+----------------------------
Reporter: Giova84 | Owner: pulkomandy
Type: bug | Status: new
Priority: normal | Milestone: Unscheduled
Component: Servers/notification_server | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: x86
-------------------------------------------+----------------------------
Comment (by Giova84):
Well, I've done a search for the file "notifications" using the Tracker's
Find utility, but it wasn't present on my disk. Then I opened the
Notification preflet, I selected both checkboxes and now this file is
present.
But the troubles which I described are still present: suddenly and
randomly, the notification_server starts to peg the cpu, and to activate
the notifications again, I have to reboot Haiku (manually restart the
notification_server doesn't re-enable the notifications); maybe is related
to the launch_daemon?[[BR]]
'''If I kill or quit the notification_server after the cpu issue''', and
then I manually restart the notification server, eg via the following
command
{{{
~> open /boot/system/servers/notification_server
}}}
Or by a simple double click on notification_server in Tracker, '''this
action doesn't reenable the notifications'''.[[BR]]
But after a reboot, notifications works again. (at the boot, the
notification_server is started by the launch daemon, by the file "system"
located in "/boot/system/data/launch")
There is a "new way", using the launch daemon, to manually start (on
user's demand) app and services?
--
Ticket URL: <https://dev.haiku-os.org/ticket/12636#comment:2>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
