Bug 423110 - New session welcoming sound doesn't play fully - oxygen-sounds
Summary: New session welcoming sound doesn't play fully - oxygen-sounds
Status: RESOLVED DUPLICATE of bug 422948
Alias: None
Product: Oxygen
Classification: Plasma
Component: sound (show other bugs)
Version: 5.19.1
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: pinheiro
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-17 15:21 UTC by Michał Dybczak
Modified: 2020-06-17 22:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michał Dybczak 2020-06-17 15:21:53 UTC
SUMMARY

I'm using Oxygen sounds, the best and the only usable sound theme. I set Oxygen-Sys-Log-In-Short.ogg to play when session starts. After update from 5.18 to 5.19.1 I hear only first 1-2 seconds of this sound and then it abruptly ends, as if someone violently plugged the cable of the speakers out.


STEPS TO REPRODUCE
1. Update system from 5.18 to 5.19.1
2. Reboot system and boot into session with Oxygen-Sys-Log-In-Short.ogg as new session sound.

OBSERVED RESULT

I hear only first 1-2 seconds of this sound and then it abruptly ends.

EXPECTED RESULT

The full length of the Oxygen-Sys-Log-In-Short.ogg should be played.


SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.19.1
KDE Frameworks Version: 5.71.0
Qt Version: 5.15.0
Kernel Version: 5.6.18-1-MANJARO
OS Type: 64-bity
Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz
Memory: 7,6 GiB RAM-u
Graphics Processor: Mesa Intel® HD Graphics 530

ADDITIONAL INFORMATION

Since oxygen sounds are no longer part of the system, they didn't update with the system, so I first did system update, noticed the issue, updated the oxygen-sounds to 5.19.0-1. Maybe that is the problem that there is no 5.19.1 package yet? In the backend, the sound plays fully and correctly thou.
Reboot didn't help.
Comment 1 Patrick Silva 2020-06-17 22:34:55 UTC

*** This bug has been marked as a duplicate of bug 422948 ***