Debian 7.7 Wheezy, xorg, SLIM, i3 I'm unable to have x11vnc -usepw -forever started with SLIM, to offer a vnc connection on boot, as I do not have a monitor attached to the computer. I tried to add sessionstart_cmd /usr/bin/x11vnc -usepw -forever to the /etc/slim.conf but that didn't seem to help. I have a ssh service running on boot, so I thought I could just ssh to the machine and start x11vnc then use the remote desktop connection, but the command fails as it is unable to x11vnc was unable to open the X DISPLAY: ":0", it cannot continue. (tried display 0-9).. How can I enable x11vnc on boot or start it via ssh?

I am using slim login manager. when I log out from my session, or restart slim from the commandline: service slim restart I get blank console for couple of minutes, before the slim login screen appears again. When I attach to the slim process with strace, I see many "Resource temporarily unavailable" and "Connection timed out" lines: socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC, 0) = 4 connect(4, {sa_family=AF_UNIX, sun_path=@"/tmp/.X11-unix/X0"}, 20) = -1 ECONNREFUSED (Connection refused) close(4) = 0 socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC, 0) = 4 getsockopt(4, SOL_SOCKET, SO_SNDBUF, , ) = 0 connect(4, {sa_family=AF_UNIX, sun_path="/tmp/.X11-unix/X0"}, 110) = -1 ENOENT (No such file or directory) close(4) connect(4, {sa_family=AF_INET, sin_port=htons(6000), sin_addr=inet_addr("127.0.0.1")}, 16) = ? ERESTARTSYS (To be restarted if SA_RESTART is set) --- SIGUSR1 {si_signo=SIGUSR1, si_code=SI_USER, si_pid=5440, si_uid=0} --- rt_sigaction(SIGUSR1, {sa_handler=0x55961af808a0, sa_mask=[USR1], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f545cc5afd0}, {sa_handler=0x55961af808a0, sa_mask=[USR1], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f545cc5afd0}, 8) = 0 rt_sigreturn({mask=[]}) = 42 connect(4, {sa_family=AF_INET, sin_port=htons(6000), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 ETIMEDOUT (Connection timed out) close(4) full strace here after few minutes slim login screen reappears again, and everything works fine. When I restart computer, slim works fine the first time, probably because I have autologin in my /etc/slim.conf: auto_login yes What is going on? And how can I fix it?

Suppose I run

docker run --rm -ti --entrypoint bash test-image

I know this is based on debian:bullseye but I have no other info about the image.

$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/ "
SUPPORT_URL="https://www.debian.org/support "
BUG_REPORT_URL="https://bugs.debian.org/ "

Is there a way (OS-wise) to check if this is a slim docker image of the full flavoured one? e.g. perhaps check some packages which are NOT supposed to be found in a slim image?

I am trying to run a container and I have to install ruby:2.5-slim and I have a dependency on postgresql-client-9.4. When I try to install this, why am I getting the following error message? Reading package lists... E: Unable to locate package postgresql-client-10 ERROR: Service 'mobydock' failed to build: The command '/bin/sh -c apt-get update && apt-get install -qq -y build-essential nodejs libpq-dev postgresql-client-10 --fix-missing --no-install-recommends' returned a non-zero code: 100

I have a laptop and a PC, both with Debian 10 installed. I am using slim login manager on both. When I log out from the X server session on my PC, I get the slim login screen. After few seconds, the monitor automatically suspends/sleeps. But when I log out from X on my laptop, the slim login screen stays forever, and laptop display never suspends. I cannot find any difference between my laptop and PC. Where is this configured? How can I suspend laptop display, after I log out? here is the relevant settings in the ServerLayout section of xorg.conf. These are same on both PC and laptop: Option "StandbyTime" "0" Option "SuspendTime" "0" Option "OffTime" "0" Option "BlankTime" "0"

I have an installation of alpine linux running in a virtualbox vm with slim + xfce4 for the desktop engine. Kernel Version: I have tried with both the latest (3.6.2) Standard and Virtual Kernel from https://alpinelinux.org/downloads/ I have not been able to get the guest to utilize the entire screen resolution, instead it is only able to go up to 1024x768. I was wondering if anyone could help me figure out what I'm missing/doing wrong. Below are the steps I've taken: I followed the steps in this video exactly **Standard Alpine Linux install** - Using all repositories: apk update && apk upgrade - setup-xorg-base - apk add alpine-desktop - apk add xfce4 - apk add thunar-volman - apk add faenza-icon-theme - apk add slim - rc-service dbus start - rc-update add dbus - rc-service udev start - rc-service add udev - rc-update add slim - reboot **Virtualbox Specific Packages:** *Standard Kernel:* apk add virtualbox-guest-modules-grsec virtualbox-additions-grsec virtualbox-guest-additions-5.1.26-r0 *Virtual Kernel:* apk add virtualbox-guest-additions-5.1.26-r0 apk add virtualbox-guest-modules-grsec "apk add virtualbox-guest-modules-grsec" give the following warning message: depmod could not open /lib/modules/4.9.44-0-hardened/modules.order I did NOT do the following: apk add virtualbox-additions-grsec Because that breaks my installation, only allows me to boot into the command prompt and spams the following error: tty port_close_start: tty->count = 1 port count = 2 **Virtualbox Settings:** - Version: 5.1.26 r117224 (Qt5.6.2) - VirtualBox > Preferences > Display > Maximum Guest Screen Size: None - View > Auto-resize Guest Display checked (It's greyed out, can't select it) - VM Settings > Display > Screen: Video Memory 128MB, 1 Monitor, 100% scale factor, Enable 3D Acceleration turned on

I am using slim login manager on Debian 10. slim-1.3.6 part of the slim package is slimlock, a screenlocker. When I lock my screen (Ctrl+Alt+Del), two things happen: 1) typical lock screen appears, where I have to provide password to unlock 2) after few seconds my display goes to sleep When I then come back and either move mouse, or type on keyboard, then the display wakes up and the lock screen appears again, where I can type my password to unlock. I need to change the following: When screen is locked and display is asleep, do not wake up on mouse movements. Only when I type on keyboard should the display wake up, and the lock screen password dialog appear. How can I do this? Does this need to be patched in the slim/slimlock package, or is this xserver ? I would be happy to recompile the slim package, if somebody could kindly point me what to modify and where.

I am using slim login manager, and it has its own pam rules file: /etc/pam.d/slim. auth requisite pam_nologin.so auth required pam_env.so readenv=1 auth required pam_env.so readenv=1 envfile=/etc/default/locale @include common-auth @include common-account session required pam_limits.so session required pam_loginuid.so @include common-session @include common-password it seems that the pam_env.so rules are setting the environment variables for the running process, such as: USER, HOME, PWD, SHELL, ... Is it possible, after these have been set, to force SHELL to be /bin/sh? I mean, regardless what shell user has specified in /etc/passwd, I want to force to use /bin/sh for slim process.

What would be the simplest way to launch a script during the boot or desktop startup process in debian? The script in question consists of a single command (ifup wlan0) to connect the wifi and requires root privileges. My system is debian testing, slim login manager, and jwm as window manager. I have tried the following: 1. creating the .service way with systemd. It starts the script, but turns it off at desktop login, can't figure out why. 2. using the startup command in Jwm, but it fails I assume because launching ifup requires root privileges. 3. put the command in the .bashrc file. same as the above 4. place the script in the /etc/rc5.d directory. nothing worked so far. suggestions?

I have installed the Simple Login Manager, slimas my login manager for xorg. I am using the Lumina desktop and FreeBSD 12.0. > SLiM is a lightweight login manager for X11, allowing the > initialization of a graphical session by entring username and password in a login > screen. I installed it with: pkg install slim Also placed into /etc/rc.conf slim_enable="YES" The graphical login interfaces does appear, however after inputing login and password, it gives the error Failed to execute login command. What to do?

I am using slim login manager and LXDE desktop environment. When I am logged in in LXDE, and switch to text console (ctrl+alt+F1), I can log in as another user in the text console and type: startx -- :1 vt8 which will start another X session on tty8 and automatically log me into LXDE. While that works OK, I am wondering whether there is a better way to do it. Using startx circumvents the login manager completely. There must be some advantage in using login managers, otherwise we would not need them, and I would log in into my regular X session (tty7) using startx. Is it possible to start my login manager (slim) on second graphical console (tty8) automatically, so that I can log in, without having to use startx?

I'm having trouble determining where to add these two commands: setxkbmap latam to set the correct keyboard layout, and xcompmgr -c -C & to enable transparency. Before installing SLiM, I used this recommendation, and it worked, but it stopped working afterwards. I tried adding it to ~/.xinitrc, like shown below: #!/bin/sh # # ~/.xinitrc # # Executed by startx (run your window manager from here) if [ -d /etc/X11/xinit/xinitrc.d ]; then for f in /etc/X11/xinit/xinitrc.d/*; do [ -x "$f" ] && . "$f" done unset f fi exec setxkbmap latam exec xcompmgr -c -C & exec startxfce4 But this seemed to crash it, and it just froze before starting XFCE4 (after logging in). I also tried using this recommendation from the Arch Wiki , but it didn't seem to do anything. Any recommendations? Note that I'd like these commands to be the default setting for all users that log into xfce4.

I recently installed Arch Linux on my notebook and it works fine. But there is still one small problem. Following to the SLiM manual I can use exit to exit to the shell. Unlike expected, I won't return to the shell, there is just a black screen where I cannot input anything. Also ALT + F1, ALT + F2, ALT + F3 or ALT + F4 makes no difference. Do I need to configure anything? Any suggestions?

I've just figured I don't actually need an image when logging into slim, especially if that image is a few megabytes large. Currently they're both set to 1x1 png images, however, then that image has to be rendered a few million times each frame, which isn't quite efficient either. How can I disable both the background image and the panel image in SLiM?

I'm trying to change my login manager to [SLiM](http://slim.berlios.de/index.php) and the theme I want for my login screen is archlinux-simplyblack: [cesar@arch ~]$ ls -la /usr/share/slim/themes/ total 108 drwxr-xr-x 27 root root 4096 May 9 19:43 . drwxr-xr-x 3 root root 4096 May 8 11:11 .. drwxr-xr-x 2 root root 4096 Nov 23 2008 archlinux-darch-grey drwxr-xr-x 2 root root 4096 Nov 23 2008 archlinux-darch-white drwxr-xr-x 2 root root 4096 Nov 23 2008 archlinux-retro drwxr-xr-x 2 root root 4096 Nov 23 2008 archlinux-simplyblack drwxr-xr-x 2 root root 4096 Nov 23 2008 archlinux-soft-grey drwxr-xr-x 2 root root 4096 Feb 25 04:16 capernoited drwxr-xr-x 2 root root 4096 Feb 25 04:16 debian-moreblue drwxr-xr-x 2 root root 4096 May 8 11:11 default drwxr-xr-x 2 root root 4096 Feb 25 04:16 fingerprint drwxr-xr-x 2 root root 4096 Feb 25 04:16 flat drwxr-xr-x 2 root root 4096 Feb 25 04:16 flower2 drwxr-xr-x 2 root root 4096 Feb 25 04:16 isolated drwxr-xr-x 2 root root 4096 Feb 25 04:16 lake drwxr-xr-x 2 root root 4096 Feb 25 04:16 lotus-midnight drwxr-xr-x 2 root root 4096 Feb 25 04:16 lotus-sage drwxr-xr-x 2 root root 4096 Feb 25 04:16 lunar drwxr-xr-x 2 root root 4096 Feb 25 04:16 mindlock drwxr-xr-x 2 root root 4096 Feb 25 04:16 parallel-dimensions drwxr-xr-x 2 root root 4096 Feb 25 04:16 previous drwxr-xr-x 2 root root 4096 Feb 25 04:16 rainbow drwxr-xr-x 2 root root 4096 Feb 25 04:16 rear-window drwxr-xr-x 2 root root 4096 Feb 25 04:16 scotland-road drwxr-xr-x 2 root root 4096 Feb 25 04:16 subway drwxr-xr-x 2 root root 4096 Feb 25 04:16 wave drwxr-xr-x 2 root root 4096 Feb 25 04:16 zenwalk In order to run SLiM at boot time I edited my /etc/rc.conf an added slim to DAEMONS (I haven't changed my /etc/inittab): DAEMONS=(syslog-ng dbus hal networkmanager net-profiles net-auto-wireless crond alsa gdm slim) I created the ~/.initrc: #!/bin/sh exec gnome-session And also make ~/.initrc executable: -rwxr-xr-x 1 cesar users 30 May 9 00:22 .xinitrc This is the what /var/log/slim.log shows: Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. Please consult the The X.Org Foundation support at http://wiki.x.org for help. Giving up. slim: unable to connect to X server /usr/bin/xauth: file /var/run/slim.auth does not exist Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. Please consult the The X.Org Foundation support at http://wiki.x.org for help. Invalid MIT-MAGIC-COOKIE-1 keyGiving up. slim: unable to connect to X server What am I missing or doing wrong? **EDIT: /etc/slim.conf** # Path, X server and arguments (if needed) # Note: -xauth $authfile is automatically appended default_path /bin:/usr/bin:/usr/local/bin default_xserver /usr/bin/X xserver_arguments -nolisten tcp vt07 # Commands for halt, login, etc. halt_cmd /sbin/shutdown -h now reboot_cmd /sbin/shutdown -r now console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login" #suspend_cmd /usr/sbin/suspend # Full path to the xauth binary xauth_path /usr/bin/xauth # Xauth file for server authfile /var/run/slim.auth # Activate numlock when slim starts. Valid values: on|off numlock on # Hide the mouse cursor (note: does not work with some WMs). # Valid values: true|false hidecursor false # This command is executed after a succesful login. # you can place the %session and %theme variables # to handle launching of specific commands in .xinitrc # depending of chosen session and slim theme # # NOTE: if your system does not have bash you need # to adjust the command according to your preferred shell, # i.e. for freebsd use: # login_cmd exec /bin/sh - ~/.xinitrc %session login_cmd exec /bin/bash -login ~/.xinitrc %session # Commands executed when starting and exiting a session. # They can be used for registering a X11 session with # sessreg. You can use the %user variable # # sessionstart_cmd some command # sessionstop_cmd some command # Start in daemon mode. Valid values: yes | no # Note that this can be overriden by the command line # options "-d" and "-nodaemon" # daemon yes # Available sessions (first one is the default). # The current chosen session name is replaced in the login_cmd # above, so your login command can handle different sessions. # see the xinitrc.sample file shipped with slim sources sessions gnome-session # Executed when pressing F11 (requires imagemagick) screenshot_cmd import -window root /slim.png # welcome message. Available variables: %host, %domain welcome_msg Welcome to %host # Session message. Prepended to the session name when pressing F1 # session_msg Session: # shutdown / reboot messages shutdown_msg The system is halting... reboot_msg The system is rebooting... # default user, leave blank or remove this line # for avoid pre-loading the username. #default_user simone # Focus the password field on start when default_user is set # Set to "yes" to enable this feature #focus_password no # Automatically login the default user (without entering # the password. Set to "yes" to enable this feature #auto_login no # current theme, use comma separated list to specify a set to # randomly choose from current_theme archlinux-simplyblack # Lock file lockfile /var/lock/slim.lock # Log file logfile /var/log/slim.log

I configured my system to do an autologin using awesome wm. However, after an upgrade of my Debian Sid (which wasn't without difficulty because of a bug in the package of my graphic driver, I had to reinstall some packages such as SLiM before figuring out a solution.), SLiM is now using Gnome Classic as default WM. My configuration is the following, feel free to ask me more information, I'll provide anything I can. Relevant parts of /var/log/slim.log: login_cmd exec /bin/bash -login /etc/X11/Xsession %session sessions awesome,startxfce4,openbox,ion3,icewm,wmaker,blackbox default_user max auto_login yes

I've got a public PC on which there are: - 1 big screen - 1 touchscreen, the user can touch it and navigate through a website - the website is in fullscreen, right click is disabled and the keyboard that appears doesn't have keys like Alt, F1, etc.. At startup, I would like to check if every components plugged to the PC work and if it's the case, I'd like to run these two windows on each screen. I didn't find any solution to start both instances of chromium in fullscreen to 2 different screens, so I started firefox for the big screen and chromium for the touchscreen. These instances of chromium and firefox are running at startup, (by the user which is -automatically- connected to the session) by adding a custom file in the .config/autostart folder. I'm running Debian 7.9. I use slim as display manager. Yes i use autologin, so there are no "login screen". I need root access for listing and opening devices. I need to check their presence and test them before I can open chromium and firefox windows. I would like the script to be ran after the autologin. ------------ Now, I tried to put the script to check if the components work in /etc/rc.local, but this file runs at runlevel 2, so I can't interact with X server by opening windows, etc. My question is: Do I have to wait runlevel 4 (or 5) to run a script as root or there is another better solution ? I feel what I do is just a dirty DIY...