## Setup - ARM computer FriendlyARM mini210s - Debian Linux 3.0.8 (armv7l) + IceWM ## How can I start an application alone without the desktop environment? For the sake of prototyping I want to start Chromium alone in fullscreen. In /usr/share/xsessions/ I found 2 files: root@FriendlyARM:~# ls -al /usr/share/xsessions/ -rw-r--r-- 1 root root 238 Feb 18 2013 IceWM.desktop -rw-r--r-- 1 root root 204 Feb 18 2013 icewm-session.desktop ### root@FriendlyARM:~# more /usr/share/xsessions/IceWM.desktop [Desktop Entry] Encoding=UTF-8 # The names/descriptions should really be better Name=IceWM Comment=This is the window manager IceWM Comment[de]=Dies ist der Fenstermanager IceWM Exec=/usr/bin/icewm-session Icon=icewm.xpm Type=Application ### root@FriendlyARM:~# more /usr/share/xsessions/icewm-session.desktop [Desktop Entry] Version=1.0 Encoding=UTF-8 Name=icewm Name[en_US]=icewm Comment=Simple and fast window manager Terminal=false Exec=icewm-session TryExec=icewm-session [Window Manager] SessionManaged=true Assuming that this is the right way to do it, how do I tweak these files to achieve my objective?

When changing the hostname in the icewm-session, the application startup breaks down. Such errors are written in the logs .xsession-errors when launching applications:

Authorization required, but no authorization protocol specified
xterm: Xt error: Can't open display: :0

When i start the distribution (native build), xdm starts. After logging in to xdm, the script .xsession is run from the user's home directory, which contains:

#!/bin/bash

icewm-session -s

Next, the icewm session starts. If I log in again, then everything works fine. But as soon as I change the hostname, it becomes impossible to launch applications, although there are no problems in the icewm session. I created a issue for the problem, but it was rejected. Do I need to configure something additionally?

I use the IceWM window manager. I would like the screen to lock after closing the laptop lid. I've found a couple of guides that looked promising ((https://unix.stackexchange.com/questions/260737/switch-off-display-and-lock-screen-in-xfce-power-manager-when-laptop-lid-is-clos) , (https://help.ubuntu.com/community/LaptopLidAndDockScripts)) but unfortunately didn't work for me. Maybe there is a solution that I'm currently missing?

The current taskbar layer is stuck on "onTop" and I would like to change it to "Normal" so it will be hidden when not focused. A similar issue to mine can be found here but I'm unfamiliar with Linux and have no direct access to the configuration files, therefore I'm trying to solve it through the terminal.

In AntiX Linux, using the default iceWM window manager. When I suspend a session, then wake it up, I expect it to ask for my screenlock password. Current behavior: it just wakes up without asking for password.

I'm using preinstalled on opensuse icewm-lite as distraction-free environment, and already got rid of the menu/start button. Is there an option to disable XTerm button too?

I just installed antiX Linux 19.3. When I (auto-)login and IceWM comes up, I get an error dialog saying: > The pin board has not yet been used ... set the default background. Start ROX-Filer with 'rox -p = Default' to activate the pin board. 1. WTF? I haven't done anything. Haven't even touched any configuration settings, and already an error? 2. Who starts rox? i.e. where should I start it differently? 3. What is the pin board, and should it be "activated" at all? Note: I've seen some forum threads suggesting an increase to some startup delay; and people reporting mixed results with that. I'd like a proper solution please.

I've installed antiX Linux 19.3, and I want to change the file manager - for the first user and by default - to something other than the annoying rox (sorry, I just don't like it). So, I've installed pcmanfm, went to the Control Center pressed "Preferred application" and got a dialog with paths of .desktop file. Ok, so far so good. The file manager one is: deskto-p-defaults-follow-fm.desktop, suggesting the setting is actually taken from elsewhere. Now, that .desktop file runs:

desktop-defaults-run -fm --follow

there's a matching desktop-defaults-set, but - if I run that one, I get the dialog I saw before. So it's as though there's a recursion without anybody choosing a file manager. I then looked into desktop-defaults-run, and it seems to be looking for a file-manager-related .desktop file, which itself runs desktop-defaults-run -fm --follow. Unless I've mis-parsed the script (which I may have - it sources some more scripts when it starts). What's going on?

I wanted to create **my own** small lightweight distro based on **Debian**. So I have decided to use **IceWM**, **Xorg** and **XDM**. I used these commands:

apt-get update
apt-get install icewm xserver-xorg xdm
apt-get update

But when I type in icewm or icewm-session it just says Can't open display: . X must be running and $DISPLAY set. Please help!

I have several applications in my system tray which are not the default monitoring gadgets of Icewm. For example, below you can see, from left to right, \ **pnmixer**, **nm-applet**, a keyboard leds indicator **trayleds.py**, a brightness indicator **traybr.py**, the battery level indicator and the network monitoring widget (the last two are Icewm builtins). The order of the first four, non-builtin is apparently randomly defined at startup. How may I fix the order for them (say, , , \ and )? man icewm-winoptions mentions > **order**: NUMBER (default: 0) > > The sorting order of task buttons and tray icons. The default value is zero. Increasing positive values go farther right, > while decreasing negative values > go farther left. The order option applies to the task pane, the tray pane and the system tray. but how can I find out the appropriate names to add to ~/.icewm/winoptions?

Notification through libnotify seems to work under icewm, as the different notifications from applications like konversation show. But I can't get it to work from the command line using the notify-send command. When I try it, the notification doesn't appear on my screen at all. How can I get it to work under icewm? **Edit 1:** I've now tried dbus-monitor. It seems there's a problem with notify-send: it isn't specifying any destination, whereas konversation for example specifies knotify as destination. Maybe this is what's causing the problem? **Edit 2:** I've also tried d-feet to reproduce the query :(see http://dropcanvas.com/521xc/97) , still nothing. The query I tried to reproduce was this one:

method call sender=:1.14 -> dest=org.kde.knotify serial=1024 path=/Notify; interface=org.kde.KNotify; member=event  
   string "queryMessage"  
   string "konversation"  
   array [  
   ]  
   string ""  
   string " hello"  
   array [  
   ]  
   array [  
   ]  
   int32 -1  
   int64 33554870  
method return sender=:1.8 -> dest=:1.14 reply_serial=1024  
   int32 1072

It was captured using dbus-monitor, sent from konversation when receiving a PM from myself to myself (using xchat, konversation and two nicks).

I'm looking for a way to bind for example the Ctrl+Alt+Ins key combination to a command line that would restart icewm (just to make it read the configuration files again and be aware of the edits). So what should go into that .icewm/keys file ?

"Alt+Ctrl+k"   ?

This used to work. My icewm menu has an item for running konsole. In .icewm/menu the line is: prog "xterm" xterm konsole Sometime, a month or so ago, without any changes to my .icewm/ files or /etc or anywhere, it stopped. Bringing up the menu and clicking 'xterm' (a misnomer, but whatever) nothing at all happens. Previously, a Konsole window with bash prompt would appear. I can still get konsole to run straight from any command line in another xterm, rxvt, konsole, or gnome-terminal. There are no error messages or anything suspicious. I'm running on Arch Linux, updated just a few months ago, well before this mysterious loss of function. Perhaps related, in Thunar, "open xterm here" doesn't do anything. It used to work, and as far as I recall, stopped working at the same time. I tried using pacman to remove and reinstall konsole, and thunar, but no change. Note that I'm not using the KDE desktop, but do use kwrite, konsole, ksnapshot and a few other KDE-based apps.

Anybody managed to bind the Windows key in IceWM ? It seems I can't bind it to anything since I disabled the "treat as Ctrl+Alt" option. # Treat Super/Win modifier as Ctrl+Alt # ModSuperIsCtrlAlt=1 # 0/1 ModSuperIsCtrlAlt=0 # 0/1

I am currently using Linux Mint 17.2 Cinnamon. Nothing unusual, just the main download available when one goes to the Mint website. (I can update to the latest 18.2, if that is needed.) This is what I want to do: 1. install icewm 2. make it the default/only windows manager 3. remove ALL of what I do not need anymore Any answers for EITHER removing package no longer used after I switch to icewm OR removing any default Mint/Ubuntu packages a developer doesn't need would be appreciated.

I would like to replace a default xfce windowmanager (xfwm4) with icewm. I have installed the following package using apt: icewm. In the file: `/etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml xfwm4 is replaced with icewm. I have created a file winoptions (touch winoptions) in the directory ~/.icewm`. The file contains the following line: testApp1.SimpleGL.geometry: 500x1000+300+0 where testApp1 is a window class and SimpleGL is a window title. A window manager starts but the config file has no effect when I start a defined window. What might be wrong ?

On a Debian box, I have installed IceWM and IceWM-lite, I'd like it to boot with IceWM-lite by default. So far I have done this through the desktop menu after each boot.

So, I hate window managers. I hate them all. My current distribution is Ubuntu 12.04. Here is my /etc/init/lightdm.conf: # LightDM - light Display Manager # # The display manager service manages the X servers running on the # system, providing login and auto-login services # # based on gdm upstart script exit 0; In short, I do everything in the TTY. Setting my system up like this means that TTY7 is full of system messages. I use the other ones and screen to do almost everything. And I'm happy that way. If I really really need to, I start Ubuntu 12.10's default desktop environment, lightdm, by typing sudo lightdm into TTY6, which opens the display manager itself in TTY7. When I'm done, I just CTRL + C in TTY6 to kill the display manager. (Unfortunately this also means that going back to TTY7 will freeze my computer entirely, a bug I have yet to report. But as long as I stay away from that black hole, things are fine.) Lately I've been playing around with other WMs, notably IceWM. I start it by typing xinit /usr/bin/icewm-session into TTY6, and voila. It's much nicer than lightdm, moving at light speed by comparison. There's just one problem. I get sound output for IceWM if I move over to a TTY. But when I am in the actual TTY that runs IceWM, looking at Skype or something, I can't actually hear anything. So, for example, I send some messages on Skype, then move over into my warm, cozy TTY1 (always open to weechat-curses) while my interlocutor writes her reply, and then and only then do I actually hear the stupid chat alert noises. Or, for example, I go over into the nice, warm, darkness of TTY2 and start playing some music with mplayer. I hear music up until the point when I switch back into TTY7, where IceWM is running. (This doesn't happen when I'm running lightdm.) Is this integration with ALSA all just a bit lacking IceWM, or might there be a more orthodox way to be WM-agnostic? (For what it's worth, I've read of other people having issues with sound not playing in IceWM. But I'm wondering if there's a more recommended approach to doing what I do.)