Linux Mint Forums

You're funny!

Yup, i guess there a few Logitech headset users out there after all!

In a certain way, this problematic belongs to LMDE KDE but it should be in a sub-thread of sorts.

zerozero wrote: handing over to Schoelje.

Headache...but the mandriva link had an interesting suggestion

With a bit of change it's worth to try: You'll need to fiddle with the positioning (start or end of the file) and reboot a lot to check if it's working (do NOT unplug the headset).

Just post alsa-base.conf here, so we can take a look at it.

Permission denied.

Ah, you need to login as su after which you can run the above code.
You can also open your default text editor and paste the code in.
LMDE: LMDE KDE: and paste the code:

Goccha!

# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7
# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd && { /sbin/modprobe --quiet snd-ioctl32 ; /sbin/modprobe --quiet snd-seq ; }
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi && { /sbin/modprobe --quiet snd-seq-midi ; : ; }
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 && { /sbin/modprobe --quiet snd-emu10k1-synth ; : ; }

# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
# Keep snd-pcsp from beeing loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2

Gotcha, in the sense of: I found the file, or is it working now?

If not, make your file look like this: This will make your headset the default soundcard.
If it works, you can change the line to Well, experiment on the index number.

Goccha = managed to do "su"
Still no sound.

Need some tutoring to modify whatever file you want me to.

DaComboMan wrote:Goccha = managed to do "su"
Still no sound.

Need some tutoring to modify whatever file you want me to.

I'm sorry DaComboMan, now I'm really out of ideas.
Any suggestions I found on the internet were referring to changes in the alsa config file but because I don't have the hardware to test it with It's impossible to debug your issue.

Can't say we didn't try!

Thank you Shoelje and ZeroZero too!

Have posted on other forums so if a solution comes about,
i'll drop you a line.

[splitted from http://forums.linuxmint.com/viewtopic.p ... 70#p643170 into its own topic, let's hope this way we get more help solving this]

Not sure if Shoelje understood me correctly.

He wanted me to make it look like this. Just how can i do that?

# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7
# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd && { /sbin/modprobe --quiet snd-ioctl32 ; /sbin/modprobe --quiet snd-seq ; }
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi && { /sbin/modprobe --quiet snd-seq-midi ; : ; }
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 && { /sbin/modprobe --quiet snd-emu10k1-synth ; : ; }

# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
# Keep snd-pcsp from beeing loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
#options snd-usb-audio index=-2
options snd-usb-audio index=0
remove snd-usb-audio { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-usb-audio

Just open the file as described in my message above: http://forums.linuxmint.com/viewtopic.p ... 28#p643028
Then copy/paste the code and save the file as in the other message above: http://forums.linuxmint.com/viewtopic.p ... 53#p643053

This is strange. Don't recall seeing this:

~ $ su
# gksu pluma /etc/modprobe.d/alsa-base.conf

(gksu:3236): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


(gksu:3236): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


(gksu:3236): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


(pluma:3237): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported

MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)

(pluma:3237): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)

(pluma:3237): Gtk-WARNING **: Attempting to store changes into `/root/.local/share/recently-used.xbel', but failed: Failed to create file '/root/.local/share/recently-used.xbel.EBT4MW': No such file or directory

(pluma:3237): Gtk-WARNING **: Attempting to set the permissions of `/root/.local/share/recently-used.xbel', but failed: No such file or directory
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)

(pluma:3237): Gtk-WARNING **: Attempting to store changes into `/root/.local/share/recently-used.xbel', but failed: Failed to create file '/root/.local/share/recently-used.xbel.VIKDNW': No such file or directory

(pluma:3237): Gtk-WARNING **: Attempting to set the permissions of `/root/.local/share/recently-used.xbel', but failed: No such file or directory
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)

(pluma:3237): Gtk-WARNING **: Attempting to store changes into `/root/.local/share/recently-used.xbel', but failed: Failed to create file '/root/.local/share/recently-used.xbel.QKI7MW': No such file or directory

(pluma:3237): Gtk-WARNING **: Attempting to set the permissions of `/root/.local/share/recently-used.xbel', but failed: No such file or directory
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)

(pluma:3237): Gtk-WARNING **: Attempting to store changes into `/root/.local/share/recently-used.xbel', but failed: Failed to create file '/root/.local/share/recently-used.xbel.84NHNW': No such file or directory

(pluma:3237): Gtk-WARNING **: Attempting to set the permissions of `/root/.local/share/recently-used.xbel', but failed: No such file or directory
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://wiki.mate-desktop.org/docs:mate-conf for information. (Details - 1: Failed to get connection to session: The connection is closed)
^C

gksu is the frontend for su (as far as I know) so you don't need to login as su.
Impressive messages though, but didn't pluma start just the same (mine did after login as su and gksu pluma)?

Me make booboo!

After reboot, i don't have any Logitech headset options at all (even sound control from usb device no longer works).

DaComboMan wrote:Me make booboo!

After reboot, i don't have any Logitech headset options at all (even sound control from usb device no longer works).

I'm sorry, but then you need to revert the config file to its original state as in your own message here: http://forums.linuxmint.com/viewtopic.p ... 49#p643049

Okay. So, i guess we're back to square one.

DaComboMan wrote:Okay. So, i guess we're back to square one.

...for the third time...

Some Americans might say, "strike three, you're out!"

When reviewing Google's latest adventure (Chrome Remote Desktop) and its possibilities, wonder if that could help?
https://chrome.google.com/webstore/deta ... ihenigjmpp

DaComboMan wrote:When reviewing Google's latest adventure (Chrome Remote Desktop) and its possibilities, wonder if that could help?
https://chrome.google.com/webstore/deta ... ihenigjmpp

To do what?