Description of problem: I've been trying the past few days to get sound from a little Jabra bluetooth ear piece. I'd like to use it to listen to some podcasts while I'm wondering around the room/house/loo/etc or with skype. When the headset it paired and connected sound anywhere does not work, audacity for instance just says Buffering when trying to play a local mp3/ogg file. clicking on 'Open Sound Preferences' in bluetooth-applet (gnome) gives an error 'Waiting for Sound System to Respond' None of that is really directly relevant to this bug though but it is how I noticed the error, and given the problems I've been having and the nature of the bug I thought it might be somehow related. $ pavucontrol ** (pavucontrol:20400): DEBUG: Failed to initialize device manager extension: No such extension It also happens when run as root.
Created attachment 1048 [details] urpmi command for all packages containing files accessed by pavucontrol Save the attachment, then run chmod a+x ./nameoffile sudo ./nameoffile The command was generated by running pavucontrol under strace up to the point it displays normal output, and then running a script that gets all of the package names containing files in the strace output. The urpmi command has the --test option, so it will simply show which (if any) packages are needed, that are not on your system.
Thanks Dave. Looks like its only some fonts that it's missing, some of which are Indian character fonts.. To satisfy dependencies, the following packages are going to be installed: (test only, installation will not be actually done) Package Version Release Arch (medium "Core Release") gnu-free-fonts-common 20100919 4.mga1 noarch gnu-free-sans-fonts 20100919 4.mga1 noarch gnu-free-serif-fonts 20100919 4.mga1 noarch google-droid-sans-fonts 20100409 2.mga1 noarch lohit-kannada-fonts 2.4.5 6.mga1 noarch samyak-fonts-common 1.2.2 4.mga1 noarch samyak-oriya-fonts 1.2.2 4.mga1 noarch vemana2000-fonts 1.1.3 2.mga1 noarch 9.8MB of additional disk space will be used. 3.9MB of packages will be retrieved. Proceed with the installation of the 8 packages? Installing them makes no difference.
Try (as root) chown -Rc claire:claire /home/claire If that doesn't fix it, as claire, run strace -f -ostrace.txt pavucontrol and then attach strace.txt
CC: (none) => davidwhodgins
(In reply to comment #3) > Try (as root) chown -Rc claire:claire /home/claire > If that doesn't fix it, as claire, run > strace -f -ostrace.txt pavucontrol > and then attach strace.txt @ Claire Did you ever get around to trying this?
Keywords: (none) => NEEDINFOCC: (none) => marja11
@ Claire Please reply to the question above within two weeks from now, to avoid this bug being closed as OLD. (If you need more time, please say so)
Sorry marja, I'd forgotten all about this one.
$ find . \! -user claire -print none $ find . \! -group claire -print ./.Xauthority.R8Fyo ./.Xauthority.A81gv ./.Xauthority.J5MLI ./.gnome2/epiphany/.migrated ./.gnome2/epiphany/ephy-history.xml ./.gnome2/epiphany/ephy-favicon-cache.xml ./.gnome2/epiphany/bookmarks.rdf ./.gnome2/epiphany/epiphany-toolbars-3.xml ./.gnome2/epiphany/states.xml ./.gnome2/epiphany/ephy-bookmarks.xml ./.gnome2/epiphany/favicon_cache/a161a37670f6455277c74c8044328082 ./.Xauthority.H3FCE ./.Xauthority.4jnCQ
Created attachment 1392 [details] strace.out With the BT headset connected pavucontrol sits for a while with a blank window except: Establishing a connection to pulseaudio, please wait.. After that it displays normally but with no BT device showing but two messages in terminal: ** (pavucontrol:3492): DEBUG: Connection failed, attempting reconnect ** (pavucontrol:3492): DEBUG: Ignoring sink-input due to it being designated as an event and thus handled by the Event widget
thx Claire :) assigning to maintainer
Keywords: NEEDINFO => (none)Assignee: bugsquad => mageia
Thankyou marja :)
Just for reference, you generally shouldn't need to run anything as root here. I've just paired a Jabra headset I have here. It's not designed for Audio (no A2DP profile) but it worked OK (after I fought with gnome-bluetooth to make it pair properly...). Can you still reproduce this issue?
Status: NEW => ASSIGNED
IIRC nothing was run as root Colin. I don't think anything has changed so I would imagine it is still reproducible but I'll give it another go and report back. The pairing was not the issue really it was getting it to work as an audio device but as you say it maybe isn't supposed to! It should still be able to be used as a headset though shouldn't it? It won't do that either at the moment, not registering in PA.
Well the strange thing to me is the "Connection failed" message. This should not come up. It indicates a bit of a problem - e.g. perhaps pulseaudio crashed and this message is indicative of a bigger problem. Other than this connection refused message, all the other DEBUG messages you've listed are expected and harmless. Cheers :)
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: ASSIGNED => RESOLVEDResolution: (none) => WONTFIX