| Summary: | sd_festival segfault noticed during boot | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | claire robinson <eeeemail> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | anaselli, eatdirt, marja11, tmb, warrendiogenese |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | speech-dispatcher | CVE: | |
| Status comment: | |||
| Attachments: | speech-dispatcher log with debug level 5 | ||
|
Description
claire robinson
2014-01-13 12:33:38 CET
journal is attachment 4764 [details]
claire robinson
2014-01-13 12:34:30 CET
Whiteboard:
(none) =>
4RC followed shortly by .. systemd[1]: speech-dispatcherd.service: main process exited, code=exited, status=1/FAILURE systemd[1]: Unit speech-dispatcherd.service entered failed state. Created attachment 4775 [details] speech-dispatcher log with debug level 5 The sd_festival module fails for 2 reasons: 1) There is no festival server running for it to connect too. 2) speech-dispatcher needs a package we don't provide, festival-freebsoft-utils, http://devel.freebsoft.org/festival-freebsoft-utils So speech-dispatcher skips the festival modules and continues on. The service fails to start because none of the modules can open a connection to the pulseaudio server. The attachment shows that the pulseaudio plugin fails with error 300 UNKNOWN ERROR. CC:
(none) =>
warrendiogenese
William Murphy
2014-01-14 09:11:35 CET
Attachment 4775 mime type:
text/x-log =>
text/plain for now I've altered meta-task to not install orca by default (wich pulls in speech-dispatcher) to not have segfaulting apps in default install... we can restore it when someone have time to fix it up CC:
(none) =>
tmb Just to say that this guy showed up within my current Cauldron update. cheers, chris. CC:
(none) =>
dirteat
Angelo Naselli
2015-06-01 18:43:35 CEST
CC:
(none) =>
anaselli
Samuel Verschelde
2015-06-02 09:49:23 CEST
Whiteboard:
4RC =>
MGA4TOO MGA5TOO Does this bug this occur in current cauldron? Keywords:
(none) =>
NEEDINFO (In reply to Samuel Verschelde from comment #6) > Does this bug this occur in current cauldron? It seems fixed in cauldron. It still happened here in a Mageia 5 install that dated from Oktober 25. The last one was: okt 29 11:49:20 localhost kernel: sd_festival[1092]: segfault at 2d0 ip 00007fb04eaee860 sp 00007fff9673e7d8 error 4 in libpthread-2.20.so[7fb04eae1000+17000] However, since I upgraded to cauldron soon after that last segfault, I never saw it again. Assigning to all packagers collectively, since there is no registered maintainer for this package. Keywords:
NEEDINFO =>
(none)
Marja Van Waes
2016-11-03 10:45:38 CET
Hardware:
i586 =>
All Hi all, Thank you for having taken the needed time to report this issue and/or to comment! Did this bug get fixed? If so, please change its status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set version to Cauldron and add MGA6TOO on the Whiteboard. Thanks, Marja No reply, so closing as OLD since Mageia 5 is no longer maintained. Resolution:
(none) =>
OLD |