Opened 3 years ago

Last modified 3 years ago

#13783 new bug

media_addon_server fails after upgrade

Reported by: gholmer Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Audio & Video Version: R1/Development
Keywords: media_addon_server Cc:
Blocked By: Blocking:
Platform: All


I frequently see failures of media_addon_server when rebooting after upgrading Haiku. I've seen this on several machines. The error message is:

The application: /boot/system/servers/media_addon_server has encountered an error which prevents it from continuing. Haiku will terminate the application and clean up.

I update like this:

pkgman add$(getarch)/current pkgman add$(getarch)/current pkgman full-sync shutdown -r

Log file attached.

Attachments (3) (23.6 KB ) - added by gholmer 3 years ago.
debug report
listdev.txt (4.5 KB ) - added by gholmer 3 years ago.
output of listdev
syslog (255.3 KB ) - added by gholmer 3 years ago.

Download all attachments as: .zip

Change History (7)

by gholmer, 3 years ago

debug report

by gholmer, 3 years ago

Attachment: listdev.txt added

output of listdev

by gholmer, 3 years ago

Attachment: syslog added


comment:1 by bruno, 3 years ago

see #13346 similar problem... maybe same! Always crashing after updating...

comment:2 by diver, 3 years ago

Try to blacklist /boot/system/add-ons/media/firewire_dv.media_addon.

comment:3 by gholmer, 3 years ago

I blacklisted firewire_dv three times by using the safe mode options in the boot menu, and all three times the system came up normally and played the "BeStartup" sound correctly.

How do I make this permanent? I see instructions here:

but how do I find the package name to use? and how much of the path do I use in the EntryBlacklist section? e.g. would it be "add-ons/media/firewire_dv"?

comment:4 by diver, 3 years ago

package name is 'haiku' as this driver comes from the base haiku package. The path looks good too.

Note: See TracTickets for help on using tickets.