-
```
What steps will reproduce the problem?
1. ./configure
2. make
3. mkdir -p certs && sudo ./shellinaboxd -d -p 443 -u user -g staff -c certs/
What is the expected output? What do you see instead…
-
```
What steps will reproduce the problem?
1. ./configure
2. make
3. mkdir -p certs && sudo ./shellinaboxd -d -p 443 -u user -g staff -c certs/
What is the expected output? What do you see instead…
-
The issue seems similar to #92 and #99 that were reported earlier, but for the KDE-based Linux distros.
The process that runs the lock-screen: kscreenlocker_greet runs as the session user as oppose…
-
systemd 247.1-2 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2…
-
_From [lpsan...@gmail.com](https://code.google.com/u/116498127598887791078/) on January 18, 2011 10:21:10_
What steps will reproduce the problem? 1. ./configure
2. make
3. mkdir -p certs && sudo .…
KLuka updated
9 years ago
-
```
What steps will reproduce the problem?
1. ./configure
2. make
3. mkdir -p certs && sudo ./shellinaboxd -d -p 443 -u user -g staff -c certs/
What is the expected output? What do you see instead…
-
```
What steps will reproduce the problem?
1. ./configure
2. make
3. mkdir -p certs && sudo ./shellinaboxd -d -p 443 -u user -g staff -c certs/
What is the expected output? What do you see instead…
-
```
What steps will reproduce the problem?
1. ./configure
2. make
3. mkdir -p certs && sudo ./shellinaboxd -d -p 443 -u user -g staff -c certs/
What is the expected output? What do you see instead…
-
```
What steps will reproduce the problem?
1. ./configure
2. make
3. mkdir -p certs && sudo ./shellinaboxd -d -p 443 -u user -g staff -c certs/
What is the expected output? What do you see instead…
-
```
What steps will reproduce the problem?
1. ./configure
2. make
3. mkdir -p certs && sudo ./shellinaboxd -d -p 443 -u user -g staff -c certs/
What is the expected output? What do you see instead…