Bug 24644 - Volume Control loses settings on reboot
Summary: Volume Control loses settings on reboot
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-09 16:55 CEST by Brian Rockwell
Modified: 2019-04-13 04:27 CEST (History)
1 user (show)

See Also:
Source RPM: mageia-7-live-gnome-x86_64 (beta3_2)
CVE:
Status comment:

Attachments
Apr 09 journal file (136.84 KB, application/gzip)
2019-04-09 17:00 CEST, Brian Rockwell 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Brian Rockwell 2019-04-09 16:55:06 CEST 
Description of problem: Volume control defaults to mute when system is rebooted


Version-Release number of selected component (if applicable): 7beta3 (Apr 5, 2019)


How reproducible:  Set volume (using headphone choice)


Steps to Reproduce:
1. Set volume (using headphone choice)
2. Reboot
3. goes back to mute
Comment 1 Brian Rockwell 2019-04-09 17:00:08 CEST 
Created attachment 10913 [details]
Apr 09 journal file

Attaching today's journal file.  I see some pulse messages.  Maybe this will help.
Comment 2 Marja Van Waes 2019-04-13 00:07:00 CEST 
(In reply to Brian Rockwell from comment #0)
> Description of problem: Volume control defaults to mute when system is
> rebooted

> Steps to Reproduce:
> 1. Set volume (using headphone choice)
> 2. Reboot
> 3. goes back to mute

It's a PulseAudio feature ;-)

You can try whether the instructions here work
https://unix.stackexchange.com/questions/220848/headphones-always-muted-after-restart

CC: (none) => marja11

Comment 3 Brian Rockwell 2019-04-13 04:27:15 CEST 
Interestingly - the latest build fixed this.

Go figure, but yes I think the stackexchange note would have done it.

Thank You,
Brian

FYI - I'm resolving this.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.