Opened 13 years ago
Closed 10 years ago
#8469 closed bug (duplicate)
Notification preferences not honored after reboot
Reported by: | jprostko | Owned by: | pulkomandy |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Servers/notification_server | Version: | R1/Development |
Keywords: | notifications | Cc: | |
Blocked By: | #9425 | Blocking: | #8584, #11382 |
Platform: | All |
Description
I noticed that disabling notifications via Preferences -> Notifications -> Disable notifications does not work as expected. I expect the disabling of notifications to survive a reboot, but it does not. Upon rebooting I see the NetworkStatus notifications (which shouldn't show), and the settings under Notifications are reset back to their original values which basically ensures that event notifications will occur against my desired behavior until I disable them again.
The latest Haiku revision I have tried is hrev44018, as of this writing.
Attachments (1)
Change History (9)
comment:1 by , 13 years ago
Cc: | removed |
---|---|
Component: | Preferences → Servers/notification_server |
Owner: | changed from | to
comment:2 by , 13 years ago
Blocking: | 8584 added |
---|
by , 12 years ago
Attachment: | 0001-Fix-8469.-Notifications-server-start-only-if-enabled.patch added |
---|
comment:3 by , 12 years ago
patch: | 0 → 1 |
---|
comment:4 by , 12 years ago
comment:5 by , 12 years ago
I agree with mmadia. I attach the patch only to point out the problem in Bootscript.
#9425 is a better solution.
comment:6 by , 12 years ago
That downside isn't huge since if the start-up code is written like the mail_daemon's the notification_server would almost immediately quit if it was disabled in its settings.
comment:7 by , 10 years ago
Blocking: | 11382 added |
---|
comment:8 by , 10 years ago
Blocked By: | 9425 added |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
Just some information, hrev37700 added notifications_server to the Bootscript.
Janus's patch would technically work. However, in order to get notifications_server to boot on the first boot build/jam/HaikuImage* would need to add the notification_server symlink in ~/config/boot/launch. Given that it isn't an ideal solution, I'm hesitant to commit it.
#9425 has been created to address these issues.