No sound, vpn problems with NM and nm-applet #25

Open
MoritzMaxeiner opened this Issue Apr 28, 2013 · 5 comments

Comments

Projects
None yet
2 participants
@MoritzMaxeiner

Hi, awesome project, but I ran into two problem that block me from using cdm:

I use Archlinux x86_64 (systemd) with the cdm-git package (compiles latest version from here) and I have an .xinitrc file to start i3 and Enlightenment17 that works perfectly with slim.
When I try to use cdm, however, after logging into the X session I do not have sound (a closer look reveals that the ACL permissions for the sound card do not get set when logging in with a user. A workaround for that would be to add the user to the audio group, but that's against the workings of systemd).
The more pressing problem is that I cannot start a VPN connection with nm-applet when starting the X session with cdm (no problems with slim), the journal states that NetworkManger cannot find the secrets for the VPN connection (which indicates to me that there a problem with the dbus sessions).

My configuration file /etc/cdmrc varies from the default one like this:

binlist=(
'/.xinitrc i3'
'
/.xinitrc e17'
'/bin/bash --login'
)

namelist=('i3' 'e17' 'Console')

flaglist=(X X C)

consolekit=no

@MoritzMaxeiner

This comment has been minimized.

Show comment
Hide comment
@MoritzMaxeiner

MoritzMaxeiner Apr 28, 2013

Apparently when you use startx/xinit from a tty the X session does not get your authentication unless you give it the vt argument for the exact same tty you're on (ttyx- > -- vtx):
http://blog.falconindy.com/articles/back-to-basics-with-x-and-systemd.html

Apparently when you use startx/xinit from a tty the X session does not get your authentication unless you give it the vt argument for the exact same tty you're on (ttyx- > -- vtx):
http://blog.falconindy.com/articles/back-to-basics-with-x-and-systemd.html

@ryneeverett

This comment has been minimized.

Show comment
Hide comment
@ryneeverett

ryneeverett Sep 29, 2013

Thanks for looking into this @calrama. I'm having the same issue running CDM on Arch. Were you able to solve this? If so, can you explain how/where you passed the vt argument since xinit/startx isn't being called explicitly?

Thanks for looking into this @calrama. I'm having the same issue running CDM on Arch. Were you able to solve this? If so, can you explain how/where you passed the vt argument since xinit/startx isn't being called explicitly?

@MoritzMaxeiner

This comment has been minimized.

Show comment
Hide comment
@MoritzMaxeiner

MoritzMaxeiner Sep 30, 2013

Sadly no and as far as I can tell there's no easy solution for this, because when using systemd there's just no apparent way to carry over the authentication from a tty login at say ttyX (which cdm uses) over to a newly started X session on ttyY - unless X = Y, of course. All of this is based on information from 5 months ago, though, maybe something has changed since then and now there is some way in a new systemd version, but if so, I know nothing about it, as I made a tactical retreat back to slim.

Sadly no and as far as I can tell there's no easy solution for this, because when using systemd there's just no apparent way to carry over the authentication from a tty login at say ttyX (which cdm uses) over to a newly started X session on ttyY - unless X = Y, of course. All of this is based on information from 5 months ago, though, maybe something has changed since then and now there is some way in a new systemd version, but if so, I know nothing about it, as I made a tactical retreat back to slim.

@ryneeverett

This comment has been minimized.

Show comment
Hide comment
@ryneeverett

ryneeverett Dec 15, 2013

After reviewing this and browsing my .cdmrc again I noticed the following promises to do exactly what you described:

# Where should the first X tty be spawned?
# special value `keep' causes to run X in current tty.
xtty='7'

After changing that line to xtty='keep', my authentication issues were solved. Turns out this was already known on the Arch forum.

After reviewing this and browsing my .cdmrc again I noticed the following promises to do exactly what you described:

# Where should the first X tty be spawned?
# special value `keep' causes to run X in current tty.
xtty='7'

After changing that line to xtty='keep', my authentication issues were solved. Turns out this was already known on the Arch forum.

@MoritzMaxeiner

This comment has been minimized.

Show comment
Hide comment
@MoritzMaxeiner

MoritzMaxeiner Dec 15, 2013

Well, yeah, but that way you stay on the same tty instead of returning to the login prompt and the x session starting on tty(7+). What this does is allowing you to start the x session automatically on any (same) tty you login from. That's not what I wanted, but if it is for you, that's good.

Well, yeah, but that way you stay on the same tty instead of returning to the login prompt and the x session starting on tty(7+). What this does is allowing you to start the x session automatically on any (same) tty you login from. That's not what I wanted, but if it is for you, that's good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment