GNOME Sound Recorder unusable because of "invalid capture settings"
When I start GNOME Sound Recorder in 2.6~rc1 and press “Record” I get an error: Your audio capture settings are invalid.. If I try to record from Audacity without changing my sound setting I can record my microphone. I couldn’t find any way of further configuring GNOME Sound Recorder which rendes it completely unusable.
Parent Task: #10950 (closed)
Original created by @sajolida on 11780 (Redmine)
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- intrigeri changed milestone to %Tails_2.12
changed milestone to %Tails_2.12
By hefee on 2019-11-22T01:59:56 (imported from GitLab project)
- intrigeri added Code Hardware support labels
added Code Hardware support labels
- Author Owner
Metadata changes
- Assignee set to @hybridwipe
Assigning to hybridwipe, but otherwise anonym should have a look and maybe revert this from 2.6.
Original created by @sajolida on 11780#note-1 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
sajolida wrote:
Assigning to hybridwipe, but otherwise anonym should have a look and maybe revert this from 2.6.
This looks like https://bugs.launchpad.net/gnome-media/+bug/61211. The Ubuntu (audio) setup from a few years ago doesn’t exactly match Today’s tails, so this will take some more digging.
Original created by @sajolida on 11780#note-2 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
Metadata changes
- Parent task set to #10950 (closed)
Original created by @sajolida on 11780#note-3 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
Just a random idea: in
config/chroot_local-includes/etc/asound.conf
we configure ALSA to use PulseAudio by default. Perhaps this config lacks some bits about inputs?Now wearing my backup RM hat: there are less than 2 days left to get a fix in for 2.6. Any chance this happens, or should I instead revert the addition of GNOME Sound Recorder?
Original created by @sajolida on 11780#note-4 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
intrigeri wrote:
Just a random idea: in
config/chroot_local-includes/etc/asound.conf
we configure ALSA to use PulseAudio by default. Perhaps this config lacks some bits about inputs?Now wearing my backup RM hat: there are less than 2 days left to get a fix in for 2.6. Any chance this happens, or should I instead revert the addition of GNOME Sound Recorder?
Let’s revert for now. Sorry for the trouble.
Original created by @sajolida on 11780#note-5 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
Metadata changes
- Priority changed from ~~Elevated~~ to Normal
-
Target version changed from
%Tails_2.6to %Tails_2.9.1
Original created by @sajolida on 11780#note-6 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
Let’s revert for now. Sorry for the trouble.
Done. No problem! I should really have tested this myself before merging.
Original created by @sajolida on 11780#note-7 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
So Tails 2.6 has been delayed until 2016-09-20, so if this can be fixed until 2016-09-19 we can still make this happen. Any chances for that?
Original created by @sajolida on 11780#note-8 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
anonym wrote:
So Tails 2.6 has been delayed until 2016-09-20, so if this can be fixed until 2016-09-19 we can still make this happen. Any chances for that?
I will have a chance to look for sure, but since I haven’t figured out the issue yet, no guarantee of a fix :)
Original created by @sajolida on 11780#note-9 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
hybridwipe wrote:
anonym wrote:
So Tails 2.6 has been delayed until 2016-09-20, so if this can be fixed until 2016-09-19 we can still make this happen. Any chances for that?
I will have a chance to look for sure, but since I haven’t figured out the issue yet, no guarantee of a fix :)
sound-recorder changed substantially between the wheezy and jessie, which is what broke it. The pulse/audio bits did not. No fix yet.
Original created by @sajolida on 11780#note-10 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
FWIW this problem is still there in Tails 3.0~alpha1, after installing
gnome-sound-recorder
3.21.92-1 by hand.Original created by @sajolida on 11780#note-11 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
Metadata changes
-
Target version changed from
%Tails_2.9.1to %Tails 2.10
Original created by @sajolida on 11780#note-12 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri -
Target version changed from
- Author Owner
Metadata changes
-
Target version changed from
%Tails 2.10to %Tails_2.12
Original created by @sajolida on 11780#note-13 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri -
Target version changed from
- Author Owner
hybridwipe, any status update or ETA?
Original created by @sajolida on 11780#note-14 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
intrigeri wrote:
hybridwipe, any status update or ETA?
So I searched my email to check the debian bug, and I found I didn’t file the bug I thought that I had :(. I have filed one now:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852870Sorry about that!
Original created by @sajolida on 11780#note-15 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
hybridwipe wrote:
intrigeri wrote:
hybridwipe, any status update or ETA?
So I searched my email to check the debian bug, and I found I didn’t file the bug I thought that I had :(. I have filed one now:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852870Sorry about that!
I also filed one upstream with Gnome: https://bugzilla.gnome.org/show_bug.cgi?id=777862
Original created by @sajolida on 11780#note-16 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
I also filed one upstream with Gnome: https://bugzilla.gnome.org/show_bug.cgi?id=777862
Thanks! I’m marking the Debian bug as forwarded upstream, then.
Original created by @sajolida on 11780#note-17 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri - Author Owner
intrigeri wrote:
I also filed one upstream with Gnome: https://bugzilla.gnome.org/show_bug.cgi?id=777862
Thanks! I’m marking the Debian bug as forwarded upstream, then.
FYI, I’ve gotten a response from upstream maintainer, who thinks it’s an issue with old glib. I see the issue on my debian unstable machine, with an allegedly unaffected glib, however. Investigation continues..
Original created by @sajolida on 11780#note-18 (Redmine)
By hefee on 2019-11-22T05:52:07 (imported from GitLab project)
Edited by intrigeri