Re: icewm anomaly after bullseye upgrade

[Andrew M.A. Cater]

On Sat, Sep 04, 2021 at 01:58:41AM -0400, Bob Bernstein wrote:
> On Fri, 3 Sep 2021, Michael Lange wrote:
> 
> > according to https://ice-wm.org/man/icewm-preferences the syntax for
> > using a bold font should rather be:
> 
> > ActiveTaskBarFontNameXft=”sans-serif:size=12:bold” .
> 
> Ah. RTFM still applies.
> 
> That did the trick for me. Thank You Sir!
> 
> > I have some doubt though, that this has anything to do with your
> > original problem.
> 
> That is correct. I did resolve my problem with 'WorkspaceNames=' not
> governing the number of workspaces shown on the Taskbar, but my error was so
> stupid I am ashamed to reveal it here in front of everyone, and probably
> won't even tell anyone off-list.
> 
> As a rule I am not above posting really dumb questions (no wisecracks, thank
> you), but that one was beyond anything even I could suffer.

No dumb questions ever. After 23 years around Debian, I still find the 
best and quickest way to find an error is to stare at it for three days,
ask someone else to look at it - and they find it in 30 seconds.

Smart wisecrack answers / demeaning someone else's efforts (always provided
they show they've done something) - that's another thing.

It's very worthwhile to think we have all sorts of people with all sorts
of experience and expertise lurking here and that somebody will know the
answer / direct you to resources to find it / have an "Aha!" moment and
sort out their own puzzle when they see you raise it.

All best, as ever,

Andy Cater

Re: icewm anomaly after bullseye upgrade

[Bob Bernstein]

On Fri, 3 Sep 2021, Michael Lange wrote:

according to https://ice-wm.org/man/icewm-preferences the 
syntax for using a bold font should rather be:



ActiveTaskBarFontNameXft=”sans-serif:size=12:bold” .


Ah. RTFM still applies.

That did the trick for me. Thank You Sir!

I have some doubt though, that this has anything to do with 
your original problem.


That is correct. I did resolve my problem with 'WorkspaceNames=' 
not governing the number of workspaces shown on the Taskbar, 
but my error was so stupid I am ashamed to reveal it here in 
front of everyone, and probably won't even tell anyone off-list.


As a rule I am not above posting really dumb questions (no 
wisecracks, thank you), but that one was beyond anything even I 
could suffer.


Thanks to all the assembled faithful as per usual.

--
What is the significance of the fact that "abstractions" and
"generalizations" and the very concepts of "time" and "space"
occur only in conjunction with a human nervous system?

 Percy W. Bridgman (1955)

Re: icewm anomaly after bullseye upgrade

[Michael Lange]

Hi,

On Thu, 2 Sep 2021 16:02:08 -0400 (EDT)
Bob Bernstein  wrote:

> Thanks to those who chimed in!
> 
> My focus today is on those lines in ~/.icewm/preferences that 
> specify fonts for the task bar. I have in mind such statements 
> as:
> 
> NormalTaskBarFontNameXft="DejaVuSans-Bold,sans-serif:size=18"
> ActiveTaskBarFontNameXft="DejaVuSans-Bold,sans-serif:size=18"
> 
> I suspect the syntax of my lines does not represent actual fonts 
> that are available on this machine.
> 
> Can anyone provide a critique of that syntax?

according to https://ice-wm.org/man/icewm-preferences the syntax for
using a bold font should rather be:

ActiveTaskBarFontNameXft=”sans-serif:size=12:bold” .

That comma-separated font list thing does not seem to work (at least not
with the IceWM version from Buster); since I suspect that "DejaVuSans"
and "sans-serif" might be equivalent here, I tried with a different font
here:

NormalTaskBarFontNameXft="Akkadian,sans-serif:size=11:bold"

This gives me the Akkadian font with normal (or medium) weight.
Changing the first font name to one that does not exist, like

NormalTaskBarFontNameXft="Akadian,sans-serif:size=11:bold"

gives me a normal weight default/fallback font. Likewise

NormalTaskBarFontNameXft="Akkadian:size=11:bold,sans-serif:size=11:bold"
resp.
NormalTaskBarFontNameXft="Akadian:size=11:bold,sans-serif:size=11:bold"

gives me a bold Akkadian font resp. that same normal weight default
fallback font as above.

I have some doubt though, that this has anything to do with your original
problem.

Best regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

It is necessary to have purpose.
-- Alice #1, "I, Mudd", stardate 4513.3

Re: icewm anomaly after bullseye upgrade

[Bob Bernstein]

Thanks to those who chimed in!

My focus today is on those lines in ~/.icewm/preferences that 
specify fonts for the task bar. I have in mind such statements 
as:


NormalTaskBarFontNameXft="DejaVuSans-Bold,sans-serif:size=18"
ActiveTaskBarFontNameXft="DejaVuSans-Bold,sans-serif:size=18"

I suspect the syntax of my lines does not represent actual fonts 
that are available on this machine.


Can anyone provide a critique of that syntax?


--
...a society must incorporate the rationalizing
power symbolized by scientific knowledge, for
otherwise it will be a fatally split society-
split between a powerful elite and the
disenfranchised mass. To this we add now: an
irrational elite is the most dangerous of all.

Holton, Gerald. 1985. On the Integrity of
Science: The Issues Since Bronowski. Leonardo
18 (4), Special Issue: Jacob Bronowski: A
Retrospective (1985): 229-232.

Re: icewm anomaly after bullseye upgrade

[Lotek]

On 9/1/21 12:17 PM, Bob Bernstein wrote:

Here's what I have onboard now after upgrading to bullseye:

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

I have never had a situation wherein the number of workspaces in the 
taskbar was _not_ determined by the contents of the line:


WorkspaceNames= " Web ", " Term ", " VNC ", etc.

in ~/.icewm/preferences. The pkgs now installed are:

$ dpkg -l |grep icewm
ii  icewm    2.1.2-1 amd64
wonderful Win95-OS/2-Motif-like window manager
ii  icewm-common 2.1.2-1 amd64
wonderful Win95-OS/2-Motif-like window manager


In order to access workspaces not displayed in the taskbar I must have 
recourse to the Window List Menu button on the extreme left side ot the 
task bar.


Thoughts?



Search "preferences" for "TaskBarShowWorkspaces"

I haven't been able to upgrade Icewm from Stretch, because the fonts in 
Buster were so bad.  So I've waiting for Bullseye with the hope that the 
fonts will look better.


Icewm was popular in the late nineties and I haven't seen anything  that 
makes me  want to change.

Re: icewm anomaly after bullseye upgrade

[Michael Lange]

Hi,

On Wed, 1 Sep 2021 15:17:11 -0400 (EDT)
Bob Bernstein  wrote:

(...)
> I have never had a situation wherein the number of workspaces in 
> the taskbar was _not_ determined by the contents of the line:
> 
> WorkspaceNames= " Web ", " Term ", " VNC ", etc.

seems to work as usual here.

> 
> in ~/.icewm/preferences. The pkgs now installed are:
> 
> $ dpkg -l |grep icewm
> ii  icewm2.1.2-1 
> amd64    wonderful Win95-OS/2-Motif-like window manager
> ii  icewm-common 2.1.2-1 
> amd64wonderful Win95-OS/2-Motif-like window manager
> 
> In order to access workspaces not displayed in the taskbar I 
> must have recourse to the Window List Menu button on the extreme 
> left side ot the task bar.
> 
> Thoughts?

What exactly does the line beginning with WorkspaceNames= look like?
What exactly is displayed resp. not displayed in the taskbar?
What is the output of `cat ~/.icewm/preferences | grep -i workspace` ?

Best regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Genius doesn't work on an assembly line basis.  You can't simply say,
"Today I will be brilliant."
-- Kirk, "The Ultimate Computer", stardate 4731.3

icewm anomaly after bullseye upgrade

[Bob Bernstein]

Here's what I have onboard now after upgrading to bullseye:

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

I have never had a situation wherein the number of workspaces in 
the taskbar was _not_ determined by the contents of the line:


WorkspaceNames= " Web ", " Term ", " VNC ", etc.

in ~/.icewm/preferences. The pkgs now installed are:

$ dpkg -l |grep icewm
ii  icewm2.1.2-1 
amd64wonderful Win95-OS/2-Motif-like window manager
ii  icewm-common 2.1.2-1 
amd64wonderful Win95-OS/2-Motif-like window manager


In order to access workspaces not displayed in the taskbar I 
must have recourse to the Window List Menu button on the extreme 
left side ot the task bar.


Thoughts?

--
...a society must incorporate the rationalizing
power symbolized by scientific knowledge, for
otherwise it will be a fatally split society-
split between a powerful elite and the
disenfranchised mass. To this we add now: an
irrational elite is the most dangerous of all.

Holton, Gerald. 1985. On the Integrity of
Science: The Issues Since Bronowski. Leonardo
18 (4), Special Issue: Jacob Bronowski: A
Retrospective (1985): 229-232.

Re: Openbox ou IceWM ou GNUstep?

[Thiago Zoroastro]

[off]Enviei um e-mail em branco de acidente. O Yahoo é ruim de manuseio 
assim.[/off]

> upower é uma opção em linha de comando


o upower não fez nada aqui.


$ upower -a
$ upower -b
$ man upower
$ upower --monitor
Monitoring activity from the power daemon. Press Ctrl+C to cancel.
^C
$ man upower
$ upower --monitor-detail
Monitoring activity from the power daemon. Press Ctrl+C to cancel.
^C
$
Fiz errado?
> Como iniciar alguma interface gráfica pelo tty ou Ctrl+Shift+F1 a F6?
Foi fácil encontrar uma solução para mim  mesmo, o startx pode ser feito assim:
$ startx /usr/bin/icewm
Mas ele não carregou configurações pessoais da barra de ferramentas. Carregou 
as abas guardadas no Iceweasel, mas não carregou as configurações salvas em 
/home/usuario/.icewm/menu e outros

Como poderia por exemplo executar o startx com o /etc/X11/icewm/menu ou o 
/home/usuario/.icewm/menu e outros?
No man ele tem isso aqui, mas não entendi a aplicabilidade:FILES
   $(HOME)/.xinitrc Client  to  run.   Typically  a shell script 
which
    runs many programs in the background.

   $(HOME)/.xserverrc   Server to run.  The default is X.

   /etc/X11/xinit/xinitrc   Client to run if the user has no .xinitrc file.

   /etc/X11/xinit/xserverrc Server to run if the user has no .xserverrc 
file.

   

Re: Openbox ou IceWM ou GNUstep?

[Thiago Zoroastro]

 

Em Sábado, 8 de Outubro de 2016 12:32, Fred Maranhão 
 escreveu:
 

 Em 08/10/2016 00:41, "Thiago Zoroastro"  escreveu:
>
> Estive usando um Positivo "merendeira" de tela minúscula nos últimos dias e 
> fiz um clonezilla para um pendrive da Kingston que pode ser mexido sem temer.
>  
> Daí eu preciso adaptar minhas necessidades afinal estou sem o ThinkPad x60s, 
> então a necessidade move o usuário de Software Livre.
>  
> Estou eliminando tudo de LX (menos lxterminal), GNOME (preciso de 
> network-manager-gnome?), Wicd é um bom substitutoMATE e KDE disponível no 
> Debian clonado no Kingston. Ele precisa ser enxuto suficiente para rodar bem 
> nesse Intel(R) Atom(TM) CPU N455   @ 1.66GHz de 2GB RAM e tela minúscula que 
> não sei a resolução.
>  
> Mexo no volume de áudio com '$ alsamixer' e vejo carga de bateria pelo '$ 
> wmbattery'. upower é uma opção em linha de comando

   

Re: Openbox ou IceWM ou GNUstep?

[Fred Maranhão]

Em 08/10/2016 00:41, "Thiago Zoroastro" 
escreveu:
>
> Estive usando um Positivo "merendeira" de tela minúscula nos últimos dias
e fiz um clonezilla para um pendrive da Kingston que pode ser mexido sem
temer.
>
> Daí eu preciso adaptar minhas necessidades afinal estou sem o ThinkPad
x60s, então a necessidade move o usuário de Software Livre.
>
> Estou eliminando tudo de LX (menos lxterminal), GNOME (preciso de
network-manager-gnome?),

Wicd é um bom substituto

MATE e KDE disponível no Debian clonado no Kingston. Ele precisa ser enxuto
suficiente para rodar bem nesse Intel(R) Atom(TM) CPU N455   @ 1.66GHz de
2GB RAM e tela minúscula que não sei a resolução.
>
> Mexo no volume de áudio com '$ alsamixer' e vejo carga de bateria pelo '$
wmbattery'.

upower é uma opção em linha de comando

Openbox ou IceWM ou GNUstep?

[Thiago Zoroastro]

Estive usando um Positivo "merendeira" de tela minúscula nos últimos dias e fiz um clonezilla para um pendrive da Kingston que pode ser mexido sem temer.
 
Daí eu preciso adaptar minhas necessidades afinal estou sem o ThinkPad x60s, então a necessidade move o usuário de Software Livre.
 
Estou eliminando tudo de LX (menos lxterminal), GNOME (preciso de network-manager-gnome?), MATE e KDE disponível no Debian clonado no Kingston. Ele precisa ser enxuto suficiente para rodar bem nesse Intel(R) Atom(TM) CPU N455   @ 1.66GHz de 2GB RAM e tela minúscula que não sei a resolução.
 
Mexo no volume de áudio com '$ alsamixer' e vejo carga de bateria pelo '$ wmbattery'. Executo vídeos e músicas com '$ mplayer destino/video.ogg' e estou aprendendo a teclar essas teclas macias com todas opções possíveis.
 
Tenho dúvidas.
1) No Openbox, quando clico com botão direito na Área de Trabalho, como faço para colocar o lxterminal no lugar do inabitável xterm ? AInda não descobri, se alguém souber por favor me fale.
2) No IceWM, eu consigo mudar o menu iniciar dele e a barra de ferramentas numa boa. Mas eu vou querer trocar. Como faço para iniciar com '$ startx' no tty1 a tty6 para trocar a GUI (Graphical User Interface) ?
 
3) Como não eliminar o network-manager que quer ir junto com o que tem de resto do MATE?
 
Por enquanto são essas dúvidas.
 
 
 
 
 Atenciosamente,
Thiago Zoroastro.

Re: [OT]: Crear applet con udevil para barra de tareas en IceWM

[Camaleón]

El Sat, 11 Jul 2015 21:37:56 -0430, Frederit Mogollon escribió:

(...)

 La pregunta/duda:
 
 Si es posible (creo que todo en GNU/Linux es posible...! ), ¿qué se
 necesitaría para crear, armar, escribir... un dockapp/applet como el que
 describí antes, basado en udevil y devmon, con ícono y todo para la
 taskbar, de forma que con un simple clic pueda desmontarse algún medio
 removible montado?.. muy a lo Xfce-mount-plugin.

Pues te diría que buscaras algún plugin que ya esté hecho para el gestor 
de archivos que usas (spacefm) y la utilidad en cuestión (udevil):

https://github.com/IgnorantGuru/spacefm/wiki/plugins

Si no te convence cómo funciona, puedes contactar con el desarrollador 
para sugerirle mejoras o nuevas funcionalidades o crear uno por tu cuenta.

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/pan.2015.07.12.09.31...@gmail.com

[OT]: Crear applet con udevil para barra de tareas en IceWM

[Frederit Mogollon]

Buenas compañeros listeros.

En esta ocasión vengo con una consulta de algo que se me ocurrió.

Primero, el ordenador sustrato:
Procesador Pentium IV 1,7 GHz, 512 MB RAM, 10 GB HD, tarjeta gráfica
GeForce2  MX/MX400 NV11.
Debian Wheezy 7.8, IceWM _1.3.7, SpaceFM_0.9.3, Udevil_0.4.3-1, SLiM_1.3.4-2.

El contexto:

Dado que uso SpaceFM con udevil, que permite montar medios removibles
(dispositivos USB, CD/DVD) sin permisos de root, pensé en la
posibilidad de un dockapp/applet para la taskbar de IceWM (gestor de
ventanas que uso), que permita desmontar fácilmente medios removibles
montados con un simple clic de ratón.

No sé si algo así, como lo pinto, existe ya; he buscado en la gran red
y no he hallado algo directamente relacionado con lo planteo (claro,
suponiendo que busqué bien...! ).

Aclaro, que aunque llevo un buen tiempo usando Debian, y alguna que
otra derivada, apenas estoy aprendiendo a programar en bash... que por
cierto,  un comentario de novato: Es genial crear algo... y que
funcione...!  :-)

La pregunta/duda:

Si es posible (creo que todo en GNU/Linux es posible...! ), ¿qué se
necesitaría para crear, armar, escribir... un dockapp/applet como el
que describí antes, basado en udevil y devmon, con ícono y todo para
la taskbar, de forma que con un simple clic pueda desmontarse algún
medio removible montado?.. muy a lo Xfce-mount-plugin.

Saludos

fdm


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cabzkbcfc4sw3rnqkd7kow1dymee3qoax_46nk2afjqfinej...@mail.gmail.com

Re: [Solucionado] PCmanFM no automonta dispositivos en Debian Wheezy + IceWM

[Frederit Mogollon]

2015-04-24 0:02 GMT-04:30, Frederit Mogollon frederitmogol...@gmail.com:
 2015-04-23 17:44 GMT-04:30, Jose Maldonado josemal...@gmail.com:
 On 23/04/15 17:42, Frederit Mogollon wrote:
 Buenas tardes usuarios debianitas...

 Reciban un cordial saludo.

 En esta ocasión solicito vuestra ayuda.

 Estoy en una máquina con CPU Pentium IV 1,7 GHz caché 256 kB;  GPU
 NV11 GeForce MX/MX 400; RAM 512 MB; HD IDE 10 GB. Una joya pues...! :)

 Como necesitaba más recursos (ram y cpu) disponibles, pero con un
 sistema operativo que brindase estabilidad, robustez, rapidez y
 eficiencia en el hardware antes descrito, eliminé el Debian con Xfce4
 que tenía, y emprendí la tarea de hacer una instalación mínima con
 Debian GNU/Linux 7.8 desde CD netinstall + IceWM como gestor de
 ventanas + PCManFM como gestor de archivos + Slim como gestor de
 entrada. Bien voy por el camino, porque el consumo basal de ram es de
 ~51 MB, frente a los ~100 MB de Xfce.

 El problema radica en que el gestor de archivos PCManFM no monta
 memorias usb como usuario normal: al insertarla aparece el aviso
 Error: Not Authorized (por lo que no aparece en /media), pero sí lo
 hace como superusuario.

 Paralelamente, monta y desmonta CD/DVD recién insertado en el usuario
 normal, pero no permite expulsarlo: al dar clic sobre el ícono del
 dispositivo en el panel lateral del gestor, aparece el mismo aviso
 Error: Not Authorized.  Como root, sí permite expulsarlo desde la
 interfaz gráfica.

 Luego de par de días buscando en Google, apliqué varias posibles
 soluciones:

 1) Desinstalé la versión estable pcmanfm_0.9.10-3 e instalé la versión
 desde wheezy-backports, debido a que leí en un foro que era un bug
 presente en el gestor.

 2) Modifiqué el archivo
 /usr/share/polkit-1/actions/org.freedesktop.udisks.policy según lo
 indicado en los siguientes foros:
 http://ubuntuforums.org/archive/index.php/t-1435044.html
 http://forums.bodhilinux.com/index.php?/topic/2214-authentication-is-required-solved/

 3) Modifiqué líneas en los archivos /home/mi_usuario/.xinitrc y
   /etc/slim.conf
 según lo indicado en éste y otros foros que no apunté la dirección:
 https://bbs.archlinux.org/viewtopic.php?id=100635

 ~/.xinitrc -- http://pastebin.com/6gqjfHXa
 /etc/slim.conf -- http://pastebin.com/7B44Lqnb

 4) Creé el grupo storage y agregué a mi_usuario a dicho grupo,
 según lo indicado en estos foros:
 http://blog.desdelinux.net/como-montar-dispositivos-usb-y-el-cdrom-en-pcman-con-nuestro-usuario/
 http://foros.archlinux-es.org/viewtopic.php?f=4t=6078

 Tengo instalado las siguientes versiones de paquetes que creo están de
 alguna forma involucrados:

 pcmanfm 1.2.3-1~bpo70+1
 gvfs-fuse 1.12.3-4
 libfm-data 1.2.3-1~bpo70+1
 libfm-gtk-data 1.2.3-1~bpo70+1
 libfm-modules 1.2.3-1~bpo70+1
 libfm-gtk4 1.2.3-1~bpo70+1
 gvfs-backends 1.12.3-4
 policykit-1-gnome 0.105-2
 lxde-icon-theme 0.5.0-1
 gnome-icon-theme 3.4.0-2
 pmount 0.9.23-2
 hal 0.5.14-8
 fuse 2.9.0-2+deb7u1
 fuse-utils 2.9.0-2+deb7u1
 usbutils 1:005-3
 usb-modeswitch 1.2.3+repack0-1

 El resultado de la orden dmesg | tail luego de insertar el pen drive
 se encuentra aquí  http://pastebin.com/RzFhAdZm

 Aquí está el contenido del fichero /etc/fstab -
 http://pastebin.com/smeD6dwb
 aunque no lo creo necesario, puesto que si se espera automontaje, no
 debería haber entradas para estos dispositivos hotplug, en este
 archivo.

 Creo que hay algún detalle que he pasado por alto, pero no lo veo. Así
 que recurro a Uds. para que me ayuden a ver luz...


 fdm



 Se te ha ocurrido habilitar Consolekit  y Dbus-launch para SLIM.

 Slim es bien conocido por que no inicia estos servicios de forma
 automatica durante el login y resultan ser necesarios para poder usar el
 automontaje usando Polkit y UDisks, que son los que vienen por defecto
 en Debian.

 Revisa por acá como configurar Consolekit y activar la opción para que
 Slim pueda activar este servicio correctamente.

 https://wiki.archlinux.org/index.php/ConsoleKit#ck-launch-session

 --
 Dios en su Cielo, todo bien en la Tierra
 -


 Compañero Jose Maldonado, gracias por la ayuda proporcionada. Ya el
 gestor de archivos pcmanfm automonta dispositivos usb y cd-rom al no
 más insertarlos.

 En cierta forma era eso, puesto que sí había habilitado el uso de
 consolekit, solo que
 tenía mal configurado el fichero  /etc/slim.conf, con la orden inadecuada
 ck-launch-session en la línea:

 login_cmd   exec dbus-launch /bin/bash -login ~/.xinitrc %session


 corrigiéndolo con la información dispuesta en el enlace que me
 sugeriste, que dice exactamente:

 Display managers like KDM, GDM, LXDM and SLiM start ConsoleKit
 automatically with each X session.
  Note:
 Do not nest ConsoleKit sessions by calling one from another, or you
 will break ConsoleKit.
 In particular, since SLiM reads ~/.xinitrc, you should make sure not to run
 ck-launch-session there.

 Por lo tanto, el fichero ~/.xinitrc, se mantiene

Re: [Solucionado] PCmanFM no automonta dispositivos en Debian Wheezy + IceWM

[Frederit Mogollon]

2015-04-23 17:42 GMT-04:30, Frederit Mogollon frederitmogol...@gmail.com:
 Buenas tardes usuarios debianitas...

 Reciban un cordial saludo.

 En esta ocasión solicito vuestra ayuda.

 Estoy en una máquina con CPU Pentium IV 1,7 GHz caché 256 kB;  GPU
 NV11 GeForce MX/MX 400; RAM 512 MB; HD IDE 10 GB. Una joya pues...! :)

 Como necesitaba más recursos (ram y cpu) disponibles, pero con un
 sistema operativo que brindase estabilidad, robustez, rapidez y
 eficiencia en el hardware antes descrito, eliminé el Debian con Xfce4
 que tenía, y emprendí la tarea de hacer una instalación mínima con
 Debian GNU/Linux 7.8 desde CD netinstall + IceWM como gestor de
 ventanas + PCManFM como gestor de archivos + Slim como gestor de
 entrada. Bien voy por el camino, porque el consumo basal de ram es de
 ~51 MB, frente a los ~100 MB de Xfce.

 El problema radica en que el gestor de archivos PCManFM no monta
 memorias usb como usuario normal: al insertarla aparece el aviso
 Error: Not Authorized (por lo que no aparece en /media), pero sí lo
 hace como superusuario.

 Paralelamente, monta y desmonta CD/DVD recién insertado en el usuario
 normal, pero no permite expulsarlo: al dar clic sobre el ícono del
 dispositivo en el panel lateral del gestor, aparece el mismo aviso
 Error: Not Authorized.  Como root, sí permite expulsarlo desde la
 interfaz gráfica.

 Luego de par de días buscando en Google, apliqué varias posibles
 soluciones:

 1) Desinstalé la versión estable pcmanfm_0.9.10-3 e instalé la versión
 desde wheezy-backports, debido a que leí en un foro que era un bug
 presente en el gestor.

 2) Modifiqué el archivo
 /usr/share/polkit-1/actions/org.freedesktop.udisks.policy según lo
 indicado en los siguientes foros:
 http://ubuntuforums.org/archive/index.php/t-1435044.html
 http://forums.bodhilinux.com/index.php?/topic/2214-authentication-is-required-solved/

 3) Modifiqué líneas en los archivos /home/mi_usuario/.xinitrc y
  /etc/slim.conf
 según lo indicado en éste y otros foros que no apunté la dirección:
 https://bbs.archlinux.org/viewtopic.php?id=100635

 ~/.xinitrc -- http://pastebin.com/6gqjfHXa
 /etc/slim.conf -- http://pastebin.com/7B44Lqnb

 4) Creé el grupo storage y agregué a mi_usuario a dicho grupo,
 según lo indicado en estos foros:
 http://blog.desdelinux.net/como-montar-dispositivos-usb-y-el-cdrom-en-pcman-con-nuestro-usuario/
 http://foros.archlinux-es.org/viewtopic.php?f=4t=6078

 Tengo instalado las siguientes versiones de paquetes que creo están de
 alguna forma involucrados:

 pcmanfm 1.2.3-1~bpo70+1
 gvfs-fuse 1.12.3-4
 libfm-data 1.2.3-1~bpo70+1
 libfm-gtk-data 1.2.3-1~bpo70+1
 libfm-modules 1.2.3-1~bpo70+1
 libfm-gtk4 1.2.3-1~bpo70+1
 gvfs-backends 1.12.3-4
 policykit-1-gnome 0.105-2
 lxde-icon-theme 0.5.0-1
 gnome-icon-theme 3.4.0-2
 pmount 0.9.23-2
 hal 0.5.14-8
 fuse 2.9.0-2+deb7u1
 fuse-utils 2.9.0-2+deb7u1
 usbutils 1:005-3
 usb-modeswitch 1.2.3+repack0-1

 El resultado de la orden dmesg | tail luego de insertar el pen drive
 se encuentra aquí  http://pastebin.com/RzFhAdZm

 Aquí está el contenido del fichero /etc/fstab -
 http://pastebin.com/smeD6dwb
 aunque no lo creo necesario, puesto que si se espera automontaje, no
 debería haber entradas para estos dispositivos hotplug, en este
 archivo.

 Creo que hay algún detalle que he pasado por alto, pero no lo veo. Así
 que recurro a Uds. para que me ayuden a ver luz...


 fdm



--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CABZkBCEcxDp7xMsUZJ+4ZJkXqxMGMimiqKs_2Qi0s=7ze9w...@mail.gmail.com

Re: PCmanFM no automonta dispositivos en Debian Wheezy + IceWM

[Jose Maldonado]

On 23/04/15 17:42, Frederit Mogollon wrote:

Buenas tardes usuarios debianitas...

Reciban un cordial saludo.

En esta ocasión solicito vuestra ayuda.

Estoy en una máquina con CPU Pentium IV 1,7 GHz caché 256 kB;  GPU
NV11 GeForce MX/MX 400; RAM 512 MB; HD IDE 10 GB. Una joya pues...! :)

Como necesitaba más recursos (ram y cpu) disponibles, pero con un
sistema operativo que brindase estabilidad, robustez, rapidez y
eficiencia en el hardware antes descrito, eliminé el Debian con Xfce4
que tenía, y emprendí la tarea de hacer una instalación mínima con
Debian GNU/Linux 7.8 desde CD netinstall + IceWM como gestor de
ventanas + PCManFM como gestor de archivos + Slim como gestor de
entrada. Bien voy por el camino, porque el consumo basal de ram es de
~51 MB, frente a los ~100 MB de Xfce.

El problema radica en que el gestor de archivos PCManFM no monta
memorias usb como usuario normal: al insertarla aparece el aviso
Error: Not Authorized (por lo que no aparece en /media), pero sí lo
hace como superusuario.

Paralelamente, monta y desmonta CD/DVD recién insertado en el usuario
normal, pero no permite expulsarlo: al dar clic sobre el ícono del
dispositivo en el panel lateral del gestor, aparece el mismo aviso
Error: Not Authorized.  Como root, sí permite expulsarlo desde la
interfaz gráfica.

Luego de par de días buscando en Google, apliqué varias posibles soluciones:

1) Desinstalé la versión estable pcmanfm_0.9.10-3 e instalé la versión
desde wheezy-backports, debido a que leí en un foro que era un bug
presente en el gestor.

2) Modifiqué el archivo
/usr/share/polkit-1/actions/org.freedesktop.udisks.policy según lo
indicado en los siguientes foros:
http://ubuntuforums.org/archive/index.php/t-1435044.html
http://forums.bodhilinux.com/index.php?/topic/2214-authentication-is-required-solved/

3) Modifiqué líneas en los archivos /home/mi_usuario/.xinitrc y
  /etc/slim.conf
según lo indicado en éste y otros foros que no apunté la dirección:
https://bbs.archlinux.org/viewtopic.php?id=100635

~/.xinitrc -- http://pastebin.com/6gqjfHXa
/etc/slim.conf -- http://pastebin.com/7B44Lqnb

4) Creé el grupo storage y agregué a mi_usuario a dicho grupo,
según lo indicado en estos foros:
http://blog.desdelinux.net/como-montar-dispositivos-usb-y-el-cdrom-en-pcman-con-nuestro-usuario/
http://foros.archlinux-es.org/viewtopic.php?f=4t=6078

Tengo instalado las siguientes versiones de paquetes que creo están de
alguna forma involucrados:

pcmanfm 1.2.3-1~bpo70+1
gvfs-fuse 1.12.3-4
libfm-data 1.2.3-1~bpo70+1
libfm-gtk-data 1.2.3-1~bpo70+1
libfm-modules 1.2.3-1~bpo70+1
libfm-gtk4 1.2.3-1~bpo70+1
gvfs-backends 1.12.3-4
policykit-1-gnome 0.105-2
lxde-icon-theme 0.5.0-1
gnome-icon-theme 3.4.0-2
pmount 0.9.23-2
hal 0.5.14-8
fuse 2.9.0-2+deb7u1
fuse-utils 2.9.0-2+deb7u1
usbutils 1:005-3
usb-modeswitch 1.2.3+repack0-1

El resultado de la orden dmesg | tail luego de insertar el pen drive
se encuentra aquí  http://pastebin.com/RzFhAdZm

Aquí está el contenido del fichero /etc/fstab -
http://pastebin.com/smeD6dwb
aunque no lo creo necesario, puesto que si se espera automontaje, no
debería haber entradas para estos dispositivos hotplug, en este
archivo.

Creo que hay algún detalle que he pasado por alto, pero no lo veo. Así
que recurro a Uds. para que me ayuden a ver luz...


fdm




Se te ha ocurrido habilitar Consolekit  y Dbus-launch para SLIM.

Slim es bien conocido por que no inicia estos servicios de forma 
automatica durante el login y resultan ser necesarios para poder usar el 
automontaje usando Polkit y UDisks, que son los que vienen por defecto 
en Debian.


Revisa por acá como configurar Consolekit y activar la opción para que 
Slim pueda activar este servicio correctamente.


https://wiki.archlinux.org/index.php/ConsoleKit#ck-launch-session

--
Dios en su Cielo, todo bien en la Tierra
-


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55396edc.9080...@gmail.com

PCmanFM no automonta dispositivos en Debian Wheezy + IceWM

[Frederit Mogollon]

Buenas tardes usuarios debianitas...

Reciban un cordial saludo.

En esta ocasión solicito vuestra ayuda.

Estoy en una máquina con CPU Pentium IV 1,7 GHz caché 256 kB;  GPU
NV11 GeForce MX/MX 400; RAM 512 MB; HD IDE 10 GB. Una joya pues...! :)

Como necesitaba más recursos (ram y cpu) disponibles, pero con un
sistema operativo que brindase estabilidad, robustez, rapidez y
eficiencia en el hardware antes descrito, eliminé el Debian con Xfce4
que tenía, y emprendí la tarea de hacer una instalación mínima con
Debian GNU/Linux 7.8 desde CD netinstall + IceWM como gestor de
ventanas + PCManFM como gestor de archivos + Slim como gestor de
entrada. Bien voy por el camino, porque el consumo basal de ram es de
~51 MB, frente a los ~100 MB de Xfce.

El problema radica en que el gestor de archivos PCManFM no monta
memorias usb como usuario normal: al insertarla aparece el aviso
Error: Not Authorized (por lo que no aparece en /media), pero sí lo
hace como superusuario.

Paralelamente, monta y desmonta CD/DVD recién insertado en el usuario
normal, pero no permite expulsarlo: al dar clic sobre el ícono del
dispositivo en el panel lateral del gestor, aparece el mismo aviso
Error: Not Authorized.  Como root, sí permite expulsarlo desde la
interfaz gráfica.

Luego de par de días buscando en Google, apliqué varias posibles soluciones:

1) Desinstalé la versión estable pcmanfm_0.9.10-3 e instalé la versión
desde wheezy-backports, debido a que leí en un foro que era un bug
presente en el gestor.

2) Modifiqué el archivo
/usr/share/polkit-1/actions/org.freedesktop.udisks.policy según lo
indicado en los siguientes foros:
http://ubuntuforums.org/archive/index.php/t-1435044.html
http://forums.bodhilinux.com/index.php?/topic/2214-authentication-is-required-solved/

3) Modifiqué líneas en los archivos /home/mi_usuario/.xinitrc y
 /etc/slim.conf
según lo indicado en éste y otros foros que no apunté la dirección:
https://bbs.archlinux.org/viewtopic.php?id=100635

~/.xinitrc -- http://pastebin.com/6gqjfHXa
/etc/slim.conf -- http://pastebin.com/7B44Lqnb

4) Creé el grupo storage y agregué a mi_usuario a dicho grupo,
según lo indicado en estos foros:
http://blog.desdelinux.net/como-montar-dispositivos-usb-y-el-cdrom-en-pcman-con-nuestro-usuario/
http://foros.archlinux-es.org/viewtopic.php?f=4t=6078

Tengo instalado las siguientes versiones de paquetes que creo están de
alguna forma involucrados:

pcmanfm 1.2.3-1~bpo70+1
gvfs-fuse 1.12.3-4
libfm-data 1.2.3-1~bpo70+1
libfm-gtk-data 1.2.3-1~bpo70+1
libfm-modules 1.2.3-1~bpo70+1
libfm-gtk4 1.2.3-1~bpo70+1
gvfs-backends 1.12.3-4
policykit-1-gnome 0.105-2
lxde-icon-theme 0.5.0-1
gnome-icon-theme 3.4.0-2
pmount 0.9.23-2
hal 0.5.14-8
fuse 2.9.0-2+deb7u1
fuse-utils 2.9.0-2+deb7u1
usbutils 1:005-3
usb-modeswitch 1.2.3+repack0-1

El resultado de la orden dmesg | tail luego de insertar el pen drive
se encuentra aquí  http://pastebin.com/RzFhAdZm

Aquí está el contenido del fichero /etc/fstab -
http://pastebin.com/smeD6dwb
aunque no lo creo necesario, puesto que si se espera automontaje, no
debería haber entradas para estos dispositivos hotplug, en este
archivo.

Creo que hay algún detalle que he pasado por alto, pero no lo veo. Así
que recurro a Uds. para que me ayuden a ver luz...


fdm


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cabzkbcepxgrsvw0ond6zhen9sosjt+tlre9gpggonzf007v...@mail.gmail.com

Re: PCmanFM no automonta dispositivos en Debian Wheezy + IceWM

[Frederit Mogollon]

2015-04-23 17:44 GMT-04:30, Jose Maldonado josemal...@gmail.com:
 On 23/04/15 17:42, Frederit Mogollon wrote:
 Buenas tardes usuarios debianitas...

 Reciban un cordial saludo.

 En esta ocasión solicito vuestra ayuda.

 Estoy en una máquina con CPU Pentium IV 1,7 GHz caché 256 kB;  GPU
 NV11 GeForce MX/MX 400; RAM 512 MB; HD IDE 10 GB. Una joya pues...! :)

 Como necesitaba más recursos (ram y cpu) disponibles, pero con un
 sistema operativo que brindase estabilidad, robustez, rapidez y
 eficiencia en el hardware antes descrito, eliminé el Debian con Xfce4
 que tenía, y emprendí la tarea de hacer una instalación mínima con
 Debian GNU/Linux 7.8 desde CD netinstall + IceWM como gestor de
 ventanas + PCManFM como gestor de archivos + Slim como gestor de
 entrada. Bien voy por el camino, porque el consumo basal de ram es de
 ~51 MB, frente a los ~100 MB de Xfce.

 El problema radica en que el gestor de archivos PCManFM no monta
 memorias usb como usuario normal: al insertarla aparece el aviso
 Error: Not Authorized (por lo que no aparece en /media), pero sí lo
 hace como superusuario.

 Paralelamente, monta y desmonta CD/DVD recién insertado en el usuario
 normal, pero no permite expulsarlo: al dar clic sobre el ícono del
 dispositivo en el panel lateral del gestor, aparece el mismo aviso
 Error: Not Authorized.  Como root, sí permite expulsarlo desde la
 interfaz gráfica.

 Luego de par de días buscando en Google, apliqué varias posibles
 soluciones:

 1) Desinstalé la versión estable pcmanfm_0.9.10-3 e instalé la versión
 desde wheezy-backports, debido a que leí en un foro que era un bug
 presente en el gestor.

 2) Modifiqué el archivo
 /usr/share/polkit-1/actions/org.freedesktop.udisks.policy según lo
 indicado en los siguientes foros:
 http://ubuntuforums.org/archive/index.php/t-1435044.html
 http://forums.bodhilinux.com/index.php?/topic/2214-authentication-is-required-solved/

 3) Modifiqué líneas en los archivos /home/mi_usuario/.xinitrc y
   /etc/slim.conf
 según lo indicado en éste y otros foros que no apunté la dirección:
 https://bbs.archlinux.org/viewtopic.php?id=100635

 ~/.xinitrc -- http://pastebin.com/6gqjfHXa
 /etc/slim.conf -- http://pastebin.com/7B44Lqnb

 4) Creé el grupo storage y agregué a mi_usuario a dicho grupo,
 según lo indicado en estos foros:
 http://blog.desdelinux.net/como-montar-dispositivos-usb-y-el-cdrom-en-pcman-con-nuestro-usuario/
 http://foros.archlinux-es.org/viewtopic.php?f=4t=6078

 Tengo instalado las siguientes versiones de paquetes que creo están de
 alguna forma involucrados:

 pcmanfm 1.2.3-1~bpo70+1
 gvfs-fuse 1.12.3-4
 libfm-data 1.2.3-1~bpo70+1
 libfm-gtk-data 1.2.3-1~bpo70+1
 libfm-modules 1.2.3-1~bpo70+1
 libfm-gtk4 1.2.3-1~bpo70+1
 gvfs-backends 1.12.3-4
 policykit-1-gnome 0.105-2
 lxde-icon-theme 0.5.0-1
 gnome-icon-theme 3.4.0-2
 pmount 0.9.23-2
 hal 0.5.14-8
 fuse 2.9.0-2+deb7u1
 fuse-utils 2.9.0-2+deb7u1
 usbutils 1:005-3
 usb-modeswitch 1.2.3+repack0-1

 El resultado de la orden dmesg | tail luego de insertar el pen drive
 se encuentra aquí  http://pastebin.com/RzFhAdZm

 Aquí está el contenido del fichero /etc/fstab -
 http://pastebin.com/smeD6dwb
 aunque no lo creo necesario, puesto que si se espera automontaje, no
 debería haber entradas para estos dispositivos hotplug, en este
 archivo.

 Creo que hay algún detalle que he pasado por alto, pero no lo veo. Así
 que recurro a Uds. para que me ayuden a ver luz...


 fdm



 Se te ha ocurrido habilitar Consolekit  y Dbus-launch para SLIM.

 Slim es bien conocido por que no inicia estos servicios de forma
 automatica durante el login y resultan ser necesarios para poder usar el
 automontaje usando Polkit y UDisks, que son los que vienen por defecto
 en Debian.

 Revisa por acá como configurar Consolekit y activar la opción para que
 Slim pueda activar este servicio correctamente.

 https://wiki.archlinux.org/index.php/ConsoleKit#ck-launch-session

 --
 Dios en su Cielo, todo bien en la Tierra
 -


Compañero Jose Maldonado, gracias por la ayuda proporcionada. Ya el
gestor de archivos pcmanfm automonta dispositivos usb y cd-rom al no
más insertarlos.

En cierta forma era eso, puesto que sí había habilitado el uso de
consolekit, solo que
tenía mal configurado el fichero  /etc/slim.conf, con la orden inadecuada
ck-launch-session en la línea:

login_cmd   exec dbus-launch /bin/bash -login ~/.xinitrc %session


corrigiéndolo con la información dispuesta en el enlace que me
sugeriste, que dice exactamente:

Display managers like KDM, GDM, LXDM and SLiM start ConsoleKit
automatically with each X session.
 Note:
Do not nest ConsoleKit sessions by calling one from another, or you
will break ConsoleKit.
In particular, since SLiM reads ~/.xinitrc, you should make sure not to run
ck-launch-session there.

Por lo tanto, el fichero ~/.xinitrc, se mantiene sin cambios:

exec ck-launch-session dbus-launch /usr/bin/icewm-session


Ya veo que tenía

How to run policykit with icewm ?

[bakshi]

Dear list,

Could anyone suggest the packages and configuration to run policykit with icewm 
in a debian box ?

Thanks


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150313065445.56805...@shiva.selfip.org

Re: Tecla de Windows en icewm

[celtictux .]

http://manualinux.heliohost.org/icewm02.html

prueba  a configurar los atajos de teclado, tal vez te sirva. yo lo hago
con ratpoison.

espero que te ayude.

un saludo!


El 14 de septiembre de 2013 04:50, Álvaro Gómez alvar...@gmail.comescribió:

 Hola a todos,

 Mi teclado tan sólo tiene una tecla de Windows (izquierda) y uso icewm
 como gestor de ventanas.

 Por defecto, icewm tiene el siguiente comportamiento:

 - Tecla Win Izquierda abre menú
 - Tecla Win Derecha muestra lista de ventanas

 Jamás uso el menú así que me gustaría permutar el comportamiento de las
 teclas de Windows en icewm. No consigo cómo hacerlo.

 Si alguien sabe cómo, agradecería un cable al respecto. O al menos saber
 cuál es el comando para desplegar la lista de ventanas para hacer:

 key Super comando

 En el ~/.icewm/keys...

 Gracias!!

 Álvaro




-- 
***celtictux***

Re: Tecla de Windows en icewm

[Camaleón]

El Fri, 13 Sep 2013 22:50:44 -0400, Álvaro Gómez escribió:

 Hola a todos,

(ese html...)
 
 Mi teclado tan sólo tiene una tecla de Windows (izquierda) y uso icewm
 como gestor de ventanas.
 
 Por defecto, icewm tiene el siguiente comportamiento:
 
 - Tecla Win Izquierda abre menú - Tecla Win Derecha muestra lista de
 ventanas
 
 Jamás uso el menú así que me gustaría permutar el comportamiento de las
 teclas de Windows en icewm. No consigo cómo hacerlo.
 
 Si alguien sabe cómo, agradecería un cable al respecto. 

Mira a ver si esto te da alguna pista:

7.5 May I use Win(95) keys with IceWM? 
http://www.icewm.org/FAQ/IceWM-FAQ-7.html#ss7.5

 O al menos saber cuál es el comando para desplegar la lista de ventanas
 para hacer:
 
 key Super comando
 
 En el ~/.icewm/keys...

Ese archivo parece más bien para asignar lo que se llama teclas 
multimedia o atajos de teclado pero me parece que lo que buscas es 
remapear/reasociar las teclas para que la windows izquierda haga la 
función de la de la derecha (que muestre la lista de ventanas).

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2013.09.14.14.43...@gmail.com

Re: Tecla de Windows en icewm

[Álvaro Gómez]

Gracias a los dos,

En ambos links hay bastante información respecto a la personalización
del teclado en iceWM. Me toca documentarme bien.

Gracias por la ayuda,

Álvaro

El día 14 de septiembre de 2013 10:43, Camaleón noela...@gmail.com escribió:
 El Fri, 13 Sep 2013 22:50:44 -0400, Álvaro Gómez escribió:

 Hola a todos,

 (ese html...)

 Mi teclado tan sólo tiene una tecla de Windows (izquierda) y uso icewm
 como gestor de ventanas.

 Por defecto, icewm tiene el siguiente comportamiento:

 - Tecla Win Izquierda abre menú - Tecla Win Derecha muestra lista de
 ventanas

 Jamás uso el menú así que me gustaría permutar el comportamiento de las
 teclas de Windows en icewm. No consigo cómo hacerlo.

 Si alguien sabe cómo, agradecería un cable al respecto.

 Mira a ver si esto te da alguna pista:

 7.5 May I use Win(95) keys with IceWM?
 http://www.icewm.org/FAQ/IceWM-FAQ-7.html#ss7.5

 O al menos saber cuál es el comando para desplegar la lista de ventanas
 para hacer:

 key Super comando

 En el ~/.icewm/keys...

 Ese archivo parece más bien para asignar lo que se llama teclas
 multimedia o atajos de teclado pero me parece que lo que buscas es
 remapear/reasociar las teclas para que la windows izquierda haga la
 función de la de la derecha (que muestre la lista de ventanas).

 Saludos,

 --
 Camaleón


 --
 To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/pan.2013.09.14.14.43...@gmail.com



--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOS9q_EqWdkezaFn6OZmtO0oVQSMDDxK=pX=sm-cm6eo_s+...@mail.gmail.com

Tecla de Windows en icewm

[Álvaro Gómez]

Hola a todos,

Mi teclado tan sólo tiene una tecla de Windows (izquierda) y uso icewm como
gestor de ventanas.

Por defecto, icewm tiene el siguiente comportamiento:

- Tecla Win Izquierda abre menú
- Tecla Win Derecha muestra lista de ventanas

Jamás uso el menú así que me gustaría permutar el comportamiento de las
teclas de Windows en icewm. No consigo cómo hacerlo.

Si alguien sabe cómo, agradecería un cable al respecto. O al menos saber
cuál es el comando para desplegar la lista de ventanas para hacer:

key Super comando

En el ~/.icewm/keys...

Gracias!!

Álvaro

Re: Changing pointer size in icewm

[Joel Roth]

Onur Aslan wrote:
 You can try to install a bigger theme. There is some themes in kde-loo.org[1].
 
 I am using Large Mouse Cursors[2] in my mothers computer.
 
 Just exract your mouse theme into ~/.icons and create a symbolic link named
 default pointing to your theme in this directory.
 
 [1]: http://kde-look.org/index.php?xcontentmode=36
 [2]: http://kde-look.org/content/show.php/Large+Mouse+Cursors?content=140787

Is this KDE specific? I don't have KDE installed.
 
 On Tue, Sep 03, 2013 at 05:33:47 -1000, Joel Roth wrote:
  Hi Everyone,
  
  I want the make the pointers bigger under icewm.  I tried
  using imagemagick's convert command to enlarge all the
  pointers in the current theme, e.g.
  ~/.icewm/themes/icedesert and in the
  /usr/share/icewm/themes/icedesert directory, but see no change,
  even after restarting X.
  
  Any ideas what to try next?
  
  Regards,
  
  Joel
  
  -- 
  Joel Roth

  
  
  -- 
  To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
  with a subject of unsubscribe. Trouble? Contact 
  listmas...@lists.debian.org
  Archive: http://lists.debian.org/20130903153347.GA6111@sprite
  
 
 
 -- 
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/20130904151312.ga12...@ev.onur.im
 

-- 
Joel Roth
  


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130909230944.GA4764@sprite

Re: Changing pointer size in icewm - SOLVED

[Joel Roth]

Joel Roth wrote:
 I want the make the pointers bigger under icewm.  

apt-get install big-cursor

 I tried
 using imagemagick's convert command to enlarge all the
 pointers in the current theme, e.g.
 ~/.icewm/themes/icedesert and in the
 /usr/share/icewm/themes/icedesert directory, but see no change,
 even after restarting X.
 
 Any ideas what to try next?
 
 Regards,
 
 Joel
 
 -- 
 Joel Roth
   
 
 
 -- 
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/20130903153347.GA6111@sprite
 

-- 
Joel Roth
  


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130910055809.GA11596@sprite

Re: Changing pointer size in icewm

[Onur Aslan]

You can try to install a bigger theme. There is some themes in kde-loo.org[1].

I am using Large Mouse Cursors[2] in my mothers computer.

Just exract your mouse theme into ~/.icons and create a symbolic link named
default pointing to your theme in this directory.

[1]: http://kde-look.org/index.php?xcontentmode=36
[2]: http://kde-look.org/content/show.php/Large+Mouse+Cursors?content=140787

On Tue, Sep 03, 2013 at 05:33:47 -1000, Joel Roth wrote:
 Hi Everyone,
 
 I want the make the pointers bigger under icewm.  I tried
 using imagemagick's convert command to enlarge all the
 pointers in the current theme, e.g.
 ~/.icewm/themes/icedesert and in the
 /usr/share/icewm/themes/icedesert directory, but see no change,
 even after restarting X.
 
 Any ideas what to try next?
 
 Regards,
 
 Joel
 
 -- 
 Joel Roth
   
 
 
 -- 
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/20130903153347.GA6111@sprite
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130904151312.ga12...@ev.onur.im

Changing pointer size in icewm

[Joel Roth]

Hi Everyone,

I want the make the pointers bigger under icewm.  I tried
using imagemagick's convert command to enlarge all the
pointers in the current theme, e.g.
~/.icewm/themes/icedesert and in the
/usr/share/icewm/themes/icedesert directory, but see no change,
even after restarting X.

Any ideas what to try next?

Regards,

Joel

-- 
Joel Roth
  


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130903153347.GA6111@sprite

ICEWM Re: quel environnement graphique choisir ?!

[Georges]

Le dimanche 24 juillet 2011 17:10:05, Gaël a écrit :
 salut à tous !
Et de même, bonjour

Bon j'en coupe un peu  
 merci pour vos réponses, ça c'est de la liste active !
 
 je suis étonné de n'avoir personne à me conseiller fluxbox :)
 
[couic...]

Pour icewm j'ai pas trouvé de doc récente alors je me suis fais la mienne ;-)
.
ICEWM

  icewm 1.3.7~pre2-1

http://www.trustonme.net/didactels/73.html
http://troumad.developpez.com/linux/serveurx/icewm/
http://mdvmondelinux.tuxfamily.org/Avoir-des-icones-sur-le-bureau-de


 --- 
Depuis  /etc/X11/icewm/  copier les fichiers menu programs toolbar  dans 
un répertoire /home/user/.icewm

*** menu: 
# ...perso 1
# Configuration du menu déroulant
# Pour un dossier :
# menu nom_dossier folder {}
# Pour un programme :
# prog nom icone programme option
#
# Note : plusieurs sous-dossiers
# peuvent se succeder.

Si je charge   xchat   pour comprendre menu alors apparaît dans menu 
déroulant Debian

prog XChat xchat xchat

prog Nom icone programme

*** programs:
J'ai ajouté  kate mais il faut entrer le chemin de l'icone car elle est à un 
endroit inhabituel

menu Éditeurs folder {
  progGaupol /usr/share/pixmaps/gaupol.xpm /bin/sh -c /usr/bin/gaupol
  progGedit /usr/share/pixmaps/gedit-icon.xpm /bin/sh -c /usr/bin/gedit
  progLeafPad /usr/share/pixmaps/leafpad.xpm /bin/sh -c /usr/bin/leafpad
  progNano /usr/share/nano/nano-menu.xpm /bin/sh -c x-terminal-emulator  
-T \Nano\ -e sh -c \/bin/nano\
  progXedit - /bin/sh -c xedit
  progKate /usr/share/icons/hicolor/32x32/apps/kate.png /bin/sh -c 
/usr/bin/kate
}

*** toolbar :
J'ai ajouté  iceweasel pour tester donc :

prog Nom(Iceweasel) icone(iceweasel) programme(iceweasel)

prog  Iceweasel iceweasel iceweasel

Mais pour kate l'icone étant à un endroit particulier
prog  Kate /usr/share/icons/hicolor/32x32/apps/kate.png /usr/bin/kate

*** preferences :

J'ai créé dans  /home/user/.icewm un fichier preferences juste pour mon image 
de fond ;-)

# .. preferences perso
DesktopBackgroundImage=~/Mes_fond_ecran/LinuxDifferPeople_640x512.png

 -
Pas taper si c'est pas l'endroit ;-) Georges
-- 
Le jour où tu découvre le Libre GNU/Linux, tu ne peu plust'en passer ;-) 

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: http://lists.debian.org/201107271554.37249.linux.debus...@free.fr

Wheezy can't login to icewm-session or jwm

[Johnny]

using Wheezy I can't login to icewm-session or jwm i get a command line 
but the keyboard does not work when that happens

I can login to icewm with no problems

What do i need to do to fix this, is there a bug


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4dee44af.6040...@gmail.com

Re: Wheezy can't login to icewm-session or jwm

[Camaleón]

On Tue, 07 Jun 2011 10:33:03 -0500, Johnny wrote:

 using Wheezy I can't login to icewm-session or jwm i get a command line
 but the keyboard does not work when that happens I can login to icewm
 with no problems
 
 What do i need to do to fix this, is there a bug

Google returned this:

gnome-settings-daemon doesn't allow to log into IceWM, LXDE.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626331

You could check your ~/.xsession-errors file and see if it matches with 
the bug's one.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.06.07.16.31...@gmail.com

Icewm GNOME and KDE menus empty

[Carl Fink]

The GNOME and KDE menus in Icewm on my system have no elements. Odd, since I 
have GNOME installed. (Icewm is way better for a netbook, so I'd rather use 
it.) GNOME itself works fine. 

Testing x86 system, 64 bit. 

I thought I'd ask here before filing a bug. Thanks for any help. 

Carl Fink
Sent via BlackBerry from T-Mobile


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1702388873-1299253276-cardhu_decombobulator_blackberry.rim.net-7762223...@bda571.bisx.prod.on.blackberry

Re: Icewm GNOME and KDE menus empty

[Jeffrin Jose]

On Fri, Mar 04, 2011 at 03:41:15PM +, Carl Fink wrote:
 The GNOME and KDE menus in Icewm on my system have no elements. Odd, since I 
 have GNOME installed. (Icewm is way better for a netbook, so I'd rather use 
 it.) GNOME itself works fine. 
 

Iam not sure about this,but please install the
packages named menu and icewm-gnome-support.
Hope something happens...

apt-get install menu icewm-gnome-support
Also check that you are clicking top level
Programs menu and not Applications.


/Jeffrin.

-- 
software engineer.
department of computer science
rajagiri school of engineering and technology.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110304201052.ga2...@debian.jeff

Re: Icewm GNOME and KDE menus empty

[Carl Fink]

On Sat, Mar 05, 2011 at 01:40:52AM +0530, Jeffrin Jose wrote:
 On Fri, Mar 04, 2011 at 03:41:15PM +, Carl Fink wrote:

 Iam not sure about this,but please install the
 packages named menu and icewm-gnome-support.
 Hope something happens...

Both already installed.
 
 apt-get install menu icewm-gnome-support
 Also check that you are clicking top level
 Programs menu and not Applications.

In Icewm, GNOME and KDE have their own top-level menus at the same level as
both Programs and Applications.  Neither is a sub-menu of any other menu.

Well, technically theyy're sub-menus of the man Icewm menu, but 
-- 
Carl Fink   nitpick...@nitpicking.com 

Read my blog at blog.nitpicking.com.  Reviews!  Observations!
Stupid mistakes you can correct!


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110304203545.ga19...@panix.com

Re: Icewm menu not working properly

[Anthony Campbell]

On 26 Feb 2010, Mark Neyhart wrote:
 Anthony Campbell wrote:
  I have used icewm for a long time and have not had any trouble with the
  menu. Recently all the entries for browsers have stopped working on my
  HP laptop (not on my desktop).
  
  The entries are of this form:
  
  prog Iceweasel -  iceweasel 
  prog Iceape - iceape 
  prog Lynx - lynx
  
  Nothing happens at all with these -no error messages, nothing. I can run
  all the browsers easily from a terminal.
 
 It could be a problem with the path used by icewm.  Have you tried
 specifying the full path in the menu file?
 
 prog Iceweasel - /usr/bin/iceweasel
 
 Mark
 
I'd already tried that, without result. I also tried xterm -e iceweasel.
Removing .xinitrc and .Xdefaults doesn't help either.

Anthony



-- 
Anthony Campbell - a...@acampbell.org.uk 
Microsoft-free zone - Using Debian GNU/Linux 
http://www.acampbell.org.uk - sample my ebooks at
http://www.smashwords.com/profile/view/acampbell


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100228190909.gb28...@acampbell.org.uk

Re: Icewm menu not working properly

[Mark Neyhart]

Anthony Campbell wrote:
 I have used icewm for a long time and have not had any trouble with the
 menu. Recently all the entries for browsers have stopped working on my
 HP laptop (not on my desktop).
 
 The entries are of this form:
 
 prog Iceweasel -  iceweasel 
 prog Iceape - iceape 
 prog Lynx - lynx
 
 Nothing happens at all with these -no error messages, nothing. I can run
 all the browsers easily from a terminal.

It could be a problem with the path used by icewm.  Have you tried
specifying the full path in the menu file?

prog Iceweasel - /usr/bin/iceweasel

Mark


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4b88142d.3020...@legis.state.ak.us

Icewm menu not working properly

[Anthony Campbell]

I have used icewm for a long time and have not had any trouble with the
menu. Recently all the entries for browsers have stopped working on my
HP laptop (not on my desktop).

The entries are of this form:

prog Iceweasel -  iceweasel 
prog Iceape - iceape 
prog Lynx - lynx

Nothing happens at all with these -no error messages, nothing. I can run
all the browsers easily from a terminal.

I have put in a bug report for icewm but I suspect the problem may lie
elsewhere. Can anyone suggest where to look for a solution? Google
didn't show anyone with a similar problem.

Anthony

-- 
Anthony Campbell - a...@acampbell.org.uk 
Microsoft-free zone - Using Debian GNU/Linux
http://www.acampbell.org.uk (blog, book reviews, 
and sceptical articles)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100225164155.ga2...@acampbell.org.uk

Re: Asunto con icewm

[Camaleón]

El Tue, 16 Feb 2010 10:56:06 +, Camaleón escribió:

El día 17 de febrero de 2010 05:10, rantis cares escribió:

(reenvío a la lista)

 Estimado Camaleon:

 Efectivamente, cuando ejecuto directamente el script desde la carpeta o
 desde la shell, este funciona a la perfeccion. Fijate que ayer al hacer
mas
 pruebas me di cuenta de lo siguiente pero que es en esecia el mismo
 problema:

 El script captura lo que sea escrito mediante teclado ahi va el ejemplo
que
 se llama CAPTURA.sh


 #!/bin/bash
 echo
 echo ESCRIBE TU PRIMER Y SEGUNDO NOMBRE echo
 read priseno
 sed s/priseno/$priseno/g tmp001  tmp002


Hum... a mi eso me da error cuando lo ejecuto desde Gnome. me dice:

sed: no se puede leer tmp001: No existe el fichero o el directorio.

Pero no entiendo bien lo que quieres hacer. 

En todo caso tendrías que usar:

***
echo $priseno  tmp001
***

Para pasar el valor de la variable a un archivo.


 El archivo tmp001 contiene lo siguiente

 ##inicia tmp001##

 Nombre: priseno

 ##termina tmp001##

 Bien, pues cuando lo ejecuto desde el menu, el script no toma el archivo
 tmp001 y por tanto no puede crear el archivo tmp002 y el tmp002 al no
tener
 una carpeta valida (que si la tiene, porque debe crearla en donde se
 ejecuta dicho script) tampoco puede ser creado.

 Pero cuando ejecuto el script directamente desde la carpeta donde se
 encuentra dicho script, si toma el archivo tmp001 y entonces si crea el
 tmp002

 La solucion que he pensado es la siguiente para el script CAPTURA.sh,
pero
 honestamente la considero poco elegante.


 #!/bin/bash
 echo
 echo ESCRIBE TU PRIMER Y SEGUNDO NOMBRE echo
 read priseno
 sed s/priseno/$priseno/g /home/rantiscares/.icewm/tmp001 
 /home/rantiscares/.icewm/tmp002


 Cuando hago la instalacion de dicho script mediante otro script llamado
 SETUP.sh lo hago de la siguiente manera (solo el comando copiar)

 #!/bin/bash
 echo INSTALANDO EL SCRIPT CAPTURA.sh
 cp tmp001 ~/.icewm

 Tal vez al momento de instalar a cada usuario dicho script, podria ser
algo
 como lo que sigue, pero como repito, se me hace poco elegante (es la
primera
 vez que creo un instalador). Primero tendria que modificar el script
 CAPTURA.sh

 #!/bin/bash
 echo
 echo ESCRIBE TU PRIMER Y SEGUNDO NOMBRE echo
 read priseno
 sed s/priseno/$priseno/g /home/miusuario/.icewm/tmp001 
 /home/miusuario/.icewm/tmp002


¿Y si pruebas con esto?

***
sed s/priseno/$priseno/g $HOME/.icewm/tmp001  $HOME/.icewm/tmp002
***


 Minetras que el script SETUP.sh seria de la siguiente manera:

 #!/bin/bash
 echo INSTALANDO EL SCRIPT CAPTURA.sh
 sed s/miusuario
 /$USER/g CAPTURA.sh  /home/$USER/.icewm/CAPTURA.sh


 Tal vez un poco enredado, pero es una solucion, al menos asi lo
considero.


No entiendo nada :-), quizá se trate de alguna restricción del IceWM.

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2010.02.17.09.19...@gmail.com

Re: Asunto con icewm

[Camaleón]

El Mon, 15 Feb 2010 18:28:14 -0600, rantis cares escribió:

(...)

 Cuando es instalado, la siguiente línea no es ejecutada:
 
 prog ALTA Informacion ~/.icewm/icons/capinf_32x32.xpm xterm
 ~/.cam/.inf/.capinf.sh
 
 Pero cuando modifico alguna linea con la informacion /home/miusuario, el
 script si es ejecutado. La línea queda de la siguiente manera:
 
 prog MAIL de Informacion ~/.icewm/icons/envmainf_32x32.xpm xterm
 /home/miusuario/.cam/.inf/.envmainf.sh
 
 ¿Alguna idea para que cada vez que lo instale, este funcione como debe
 funcionar?

Ah, qué curioso.

¿Dices que IceWM no interpreta ~ como una ruta válida? ¿Y si lo 
ejecutas directamente desde xterm, funciona?

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2010.02.16.10.56...@gmail.com

Asunto con icewm

[rantis cares]

Hola a todos:

Fijense que tengo algunas dudas con ICEWM. Como ustedes saben este gestor de
ventanas es muy ligero y se puede configurar muy bien.

He aqui la duda.

Tengo mi archivo llamado menu en la carpeta /home/rantiscares/.icewm

El menu contiene la siguiente informacion:

###INICIA MENU###
menu HOMs ~/.icewm/icons/homs_32x32.xpm {

prog ALTA Informacion ~/.icewm/icons/capinf_32x32.xpm xterm
~/.cam/.inf/.capinf.sh

prog MAIL de Informacion ~/.icewm/icons/envmainf_32x32.xpm xterm
~/.cam/.inf/.envmainf.sh
}
###FINALIZA MENU###


Les menciono que este menu sera instalado a cada usuario que sea dado de
alta. Este menu lo instalaré mediante un script cada vez que dicho usuario
sea dado de alta.

Cuando es instalado, la siguiente línea no es ejecutada:

prog ALTA Informacion ~/.icewm/icons/capinf_32x32.xpm xterm
~/.cam/.inf/.capinf.sh

Pero cuando modifico alguna linea con la informacion /home/miusuario, el
script si es ejecutado. La línea queda de la siguiente manera:

prog MAIL de Informacion ~/.icewm/icons/envmainf_32x32.xpm xterm
/home/miusuario/.cam/.inf/.envmainf.sh

¿Alguna idea para que cada vez que lo instale, este funcione como debe
funcionar?

Gracias

Re: starting Idesk automatically in IceWM on Lenny

[Lisi]

On Friday 16 October 2009 01:33:17 Tim Clewlow wrote:
 It sounds like your system is not using the xsession method of
 managing an X session, which means it is using the native xinit
 method. That's ok, and just as easy to work with. First check if you
 have a file called .xinitrc in your home directory, if it exists,
 rename it to .xinitrc.sav to move it out the way for a bit (so you
 can always rename it back later if you want) with:

 mv ~/.xinitrc ~/.xinitrc.sav

 Now create a brand new .xinitrc file in your home directory, it will
 be exactly the same as the .xsession file you made earlier, so if
 you still have the .xsession file just do:

 cp ~/.xsession ~/.xinitrc

 Or if you need to create, or want to check, the new .xinitrc file
 then it should contain:

 #!/bin/sh
 xrdb -merge ~/.Xdefaults 
 icewm 
 idesk 
 while [ 1 ] ; do
 sleep 1000d
 done

 As long as no-one has modified the X startup scripts (which is very
 unlikely for most systems), this should work, well, hopefully :-)

I did this almost immediately on getting up.  (We obviously live in different 
time zones!)

I copied as you advised, then kept my xsession but renamed it.

Then restarted.  Everything appeared to be exactly the same.

I have (mea culpa) failed to report an error message that I get when I start a 
terminal.  This has happened throughout the saga so consistently that I no 
longer register it.

Here - belatedly :-( - it is:
l...@dunhurst:~$
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.

It does not go back to the $ sign, but is immediately usable normally.

And here are excerpts from the global X files:

xinit in its entirety:

#!/bin/bash
# $Xorg: xinitrc.cpp,v 1.3 2000/08/17 19:54:30 cpqbld Exp $

# /etc/X11/xinit/xinitrc
#
# global xinitrc file, used by all X sessions started by xinit (startx)

# invoke global X session script
. /etc/X11/Xsession

an excerpt from Xsession (what I hope is the relevant bit - the whole file is 
very long):

# initialize variables for use by all session scripts

OPTIONFILE=/etc/X11/Xsession.options

SYSRESOURCES=/etc/X11/Xresources
USRRESOURCES=$HOME/.Xresources

SYSSESSIONDIR=/etc/X11/Xsession.d
USERXSESSION=$HOME/.xsession
USERXSESSIONRC=$HOME/.xsessionrc
ALTUSERXSESSION=$HOME/.Xsession
ERRFILE=$HOME/.xsession-errors

xsession was not in fact there - I had to create it.

 Also, I think there is a better way to start X than using a bashrc
 file

I am convinced of that!  But Googling automatic startup found me that.
 
 - but we'll get to that later, first we need to get X starting 
 up the way you want it.
It is extremely kind of you to stick with me, and I am very grateful.  I know 
I am labouring this.  This is my first attempt to move away from DEs, and I 
am really keen to do it, but as you can see am pretty hopeless at it.

At the moment I am still basically working on my test rig.  And this started 
as a fresh installation of Debian Lenny.  I am wondering whether it might be 
an idea to reinstall in case my previous frantic efforts messed something up.

Cheers
Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Tim Clewlow]

 On Friday 16 October 2009 01:33:17 Tim Clewlow wrote:
 It sounds like your system is not using the xsession method of
 managing an X session, which means it is using the native xinit
method. That's ok, and just as easy to work with. First check if
you
 have a file called .xinitrc in your home directory, if it exists,
rename it to .xinitrc.sav to move it out the way for a bit (so
you
 can always rename it back later if you want) with:
 mv ~/.xinitrc ~/.xinitrc.sav
 Now create a brand new .xinitrc file in your home directory, it will
 be exactly the same as the .xsession file you made earlier, so if
you still have the .xsession file just do:
 cp ~/.xsession ~/.xinitrc
 Or if you need to create, or want to check, the new .xinitrc file
then it should contain:
 #!/bin/sh
 xrdb -merge ~/.Xdefaults 
 icewm 
 idesk 
 while [ 1 ] ; do
 sleep 1000d
 done
 As long as no-one has modified the X startup scripts (which is
 very
 unlikely for most systems), this should work, well, hopefully :-)
 I did this almost immediately on getting up.  (We obviously live
in
 different
 time zones!)
 I copied as you advised, then kept my xsession but renamed it.
 Then restarted.  Everything appeared to be exactly the same.
 I have (mea culpa) failed to report an error message that I get
when
 I start a
 terminal.  This has happened throughout the saga so consistently
that I no
 longer register it.
 Here - belatedly :-( - it is:
 l...@dunhurst:~$
 Fatal server error:
 Server is already active for display 0
 If this server is no longer running, remove /tmp/.X0-lock
and start again.
 It does not go back to the $ sign, but is immediately usable
 normally.

lol - that error makes quite a difference. It means pretty much what
it says, ie X is already running, or, the combination of config
files means the system ends up trying to start X twice.

I think the first thing to do is to comment out the 'startx' line in
the ~/.bash_profile file and then restart the computer. Hopefully
this will mean X does not start, ie it is not being started by a
command in some other config file. If this is the case, then log in
and manually start it by typing 'startx'. It should then read the
xsession/xinitrc files and start up with icewm and idesk.

If after commenting out 'startx' from the .bash_profile file and
rebooting, X still startx, then we need to look at a whole bunch of
possible files to see where it is being started from. Try the first
option and we'll see if that works.

Oh, and in case your wondering, I'm more than happy to do through
this with you, I've only moved to Debian recently from another *nix
so I'm happy to have this as a learning exercise for myself too. :-)

Cheers, Tim.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Lisi]

On Friday 16 October 2009 11:10:04 Tim Clewlow wrote:
 lol - that error makes quite a difference. It means pretty much what
 it says, ie X is already running, or, the combination of config
 files means the system ends up trying to start X twice.

Yes, I am very sorry.  I know that it is essential to say everything that 
remotely might be relevant.  I am very contrite.

 I think the first thing to do is to comment out the 'startx' line in
 the ~/.bash_profile file and then restart the computer. Hopefully
 this will mean X does not start, ie it is not being started by a
 command in some other config file. If this is the case, then log in
 and manually start it by typing 'startx'. It should then read the
 xsession/xinitrc files and start up with icewm and idesk.

 If after commenting out 'startx' from the .bash_profile file and
 rebooting, X still startx, then we need to look at a whole bunch of
 possible files to see where it is being started from. Try the first
 option and we'll see if that works.

As you predicted, startx at the command line prompt started IceWM.  But iDesk 
was not running properly and there was no visible desktop background.  Also 
the mouse did not work as it should.  (E.g. right click on the desktop, which 
ought to have brought up a menu did nothing.)  The panel was there and 
functioning, so I clicked on menu and started from there.  I opened a 
terminal, and no ominous error message, but also no Idesk and no icons - they 
had disappeared.  So I started idesk from the command line and it is now 
running, apparently correctly, and continued to run after I closed the 
terminal even tho' I had forgotten the  at the end.

But there is still this grey greying out grid over everything instead of a 
desktop with icons that are not covered by a grid of any kind!  And if I 
use .bash_profile to start X and then start idesk from a terminal I get a 
fully functional system with a proper desktop.  It is the trying to start 
idesk automatically that seems to cause the problem. :-(

Thanks again,
Cheers
Lisi



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Tim Clewlow]

 On Friday 16 October 2009 11:10:04 Tim Clewlow wrote:
 lol - that error makes quite a difference. It means pretty much what
 it says, ie X is already running, or, the combination of config
files means the system ends up trying to start X twice.
 Yes, I am very sorry.  I know that it is essential to say
everything
 that
 remotely might be relevant.  I am very contrite.
 I think the first thing to do is to comment out the 'startx' line in
 the ~/.bash_profile file and then restart the computer. Hopefully
this will mean X does not start, ie it is not being started by a
command in some other config file. If this is the case, then log
in
 and manually start it by typing 'startx'. It should then read the
xsession/xinitrc files and start up with icewm and idesk.
 If after commenting out 'startx' from the .bash_profile file and
rebooting, X still startx, then we need to look at a whole bunch
of
 possible files to see where it is being started from. Try the
 first
 option and we'll see if that works.
 As you predicted, startx at the command line prompt started IceWM.

 But iDesk
 was not running properly and there was no visible desktop
 background.  Also
 the mouse did not work as it should.  (E.g. right click on the
 desktop, which
 ought to have brought up a menu did nothing.)  The panel was there
and
 functioning, so I clicked on menu and started from there.  I
opened
 a
 terminal, and no ominous error message, but also no Idesk and no
icons - they
 had disappeared.  So I started idesk from the command line and it
is
 now
 running, apparently correctly, and continued to run after I closed
the
 terminal even tho' I had forgotten the  at the end.
 But there is still this grey greying out grid over everything
 instead of a
 desktop with icons that are not covered by a grid of any kind!
And
 if I
 use .bash_profile to start X and then start idesk from a terminal
I
 get a
 fully functional system with a proper desktop.  It is the trying
to
 start
 idesk automatically that seems to cause the problem. :-(
 Thanks again,
 Cheers
 Lisi

Ok, make sure you have a directory called .idesktop, ie create it
with:

mkdir ~/.idesktop

and then kill X ctrlaltbackspace and then start is again
'startx' - I'm hoping this means you now have an idesk icon. Will
fix the background and mouse after this.

Cheers, Tim.





-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Tim Clewlow]

Ok, I found out that there is an error in the .xsession file, the
correct version is below, note the line 'icewm ' has now become
'icewm-session ' - this should bring back the correct background
and hopefully the mouse will behave noremally again :-)

#!/bin/sh
xrdb -merge ~/.Xdefaults 
icewm-session 
idesk 
while [ 1 ] ; do
sleep 1000d
done






-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Lisi]

On Friday 16 October 2009 13:06:42 Tim Clewlow wrote:
  But there is still this grey greying out grid over everything
  instead of a
  desktop with icons that are not covered by a grid of any kind!
 And
  if I
  use .bash_profile to start X and then start idesk from a terminal
 I
  get a
  fully functional system with a proper desktop.  It is the trying
 to
  start
  idesk automatically that seems to cause the problem. :-(
  Thanks again,

 Ok, make sure you have a directory called .idesktop, ie create it
 with:

     mkdir ~/.idesktop

I already have this directory - the instructions I followed initially said to 
create the directory and copy the config files there, which I have done.
I have also tried to solve the desktop problem by altering the background, but 
to no avail.

 and then kill X ctrlaltbackspace and then start is again
 'startx' - I'm hoping this means you now have an idesk icon. Will
 fix the background and mouse after this.

So I just restarted X again, and although I have literally not touched the 
computer since that last time when it failed, it started up with a functional 
desktop but covered with this grid.  So I restarted X a few more times and it 
seems to have reached that situation fairly stably.  I also tried a reboot - 
it booted to the command line, I entered startx, and the system started 
fine - just with this grey grid over everything.

As I say, it is starting idesk automatically that seems to cause the problem.  

Cheers
Lisi



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Lisi]

On Friday 16 October 2009 13:42:25 Tim Clewlow wrote:
 Ok, I found out that there is an error in the .xsession file, the
 correct version is below, note the line 'icewm ' has now become
 'icewm-session ' - this should bring back the correct background
 and hopefully the mouse will behave noremally again :-)

 #!/bin/sh
 xrdb -merge ~/.Xdefaults 
 icewm-session 
 idesk 
 while [ 1 ] ; do
 sleep 1000d
 done

Our emails crossed!

I have both IceWM _and_ idesk running correctly. \0/ 

Just out of interest, and because it would obviously be easy to reverse, I 
uncommented startx in .bash_profile.  I then rebooted.

And I have a fully operational system, but for that error message, so 
something is still not right - but hey, the presenting problem has been 
solved.  So if you want to breathe a sigh of relief and bring the shutters 
down, I shall still be greatly indebted to you.

But if you have the stamina, and enough of the will to live, I would love to 
sort it out properly.

Many thanks, 
cheers,
Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Tzafrir Cohen]

On Fri, Oct 16, 2009 at 11:33:17AM +1100, Tim Clewlow wrote:
  On Wednesday 14 October 2009 00:34:57 Tim Clewlow wrote:
   On Tuesday 13 October 2009 10:43:21 Tim Clewlow wrote:
   You can rearrange the order in which things are started in
 your
   .xsession file, ie you dont have to start the window manager
  last.
   [snip]
   Basically, when the script finishes, X will close - so dont
 let
   the
   script finish - thats what the long sleeping loop at the end
 is
   for.
   I'm guessing your .xsession should look something like:
   #!/bin/sh
   xrdb -merge ~/.Xdefaults 
   icewm 
   sleep 1
   other apps 
   idesk 
   while [ 1 ] ; do
   sleep 1000d
   done
   The line 'sleep 1' is intended to be a little delay to give
  icewm
   time to start up before attempting to run idesk. It may not
   actually
   be necessary, or it may be too small a delay, it all depends
 on
   how
   idesk determines if icewm is running, ie it may look for a
 lock
   file
   created really quickly by icewm, or it may look for a process
  that
   may take some time to appear.
  [snip]
   I am beginning to think that either it is simply not doable, or
  it
   is doable -
   but not by me. :-(
  I installed icewm and idesk, created a directory ~/.idesktop and
 then started X with .xsession containing the following:
  #!/bin/sh
  xrdb -merge ~/.Xdefaults 
  icewm 
  idesk 
  while [ 1 ] ; do
  sleep 1000d
  done
  Idesk seems to start up fine, ie I had icewm running and an icon at
  the top left that looks kind of like a house with the text
 'Idesk'
  written underneath.
  Thank you very much for trying this out.
  Yes - if you have not created any other icons, that is what you
  should see.
  I, however, still don't. :-(  There is obviously something else
  either running
  or not running as it ought to do.
  Before trying this one, I did rm .bash_profile so that that
 would
  not be
  muddying the waters.  I then did exactly as you had done.  X
 failed
  to start.
  So I added startx to your script.  Not surprisingly, that made no
 difference.
  So I recreated .bash_profile and put startx in it.
  That gave me a functional system - but no desktop.  Just a nasty
 hashed
  greying out grid.  Etc.  I have spent quite some time googling,
 and
  trying
  things out on my test system, including via the configuration
 files.
   We know
  that this works for you, and that it works for me if I start idesk
 manually.
  About the only thing I can think of to try is starting X
  differently.  But
  how?
  You have done so much already, but I would be very grateful if you
 could tell
  me how you start X on your system.
  Lisi
 
 It sounds like your system is not using the xsession method of
 managing an X session, which means it is using the native xinit
 method.

Is it?

Let's look at /etc/X11/Xsession

$ grep HOME /etc/X11/Xsession
USRRESOURCES=$HOME/.Xresources
USERXSESSION=$HOME/.xsession
USERXSESSIONRC=$HOME/.xsessionrc
ALTUSERXSESSION=$HOME/.Xsession
ERRFILE=$HOME/.xsession-errors

$ grep USERXSESSION /etc/X11/Xsession /etc/X11/Xsession.d/*
/etc/X11/Xsession:USERXSESSION=$HOME/.xsession
/etc/X11/Xsession:USERXSESSIONRC=$HOME/.xsessionrc
/etc/X11/Xsession:ALTUSERXSESSION=$HOME/.Xsession
/etc/X11/Xsession.d/40x11-common_xsessionrc:if [ -r $USERXSESSIONRC ]; then
/etc/X11/Xsession.d/40x11-common_xsessionrc:  . $USERXSESSIONRC
/etc/X11/Xsession.d/50x11-common_determine-startup:for STARTUPFILE in 
$USERXSESSION $ALTUSERXSESSION; do
/etc/X11/Xsession.d/50x11-common_determine-startup:ERRMSG=$ERRMSG no 
\$USERXSESSION\ file, no \$ALTUSERXSESSION\ file,

 That's ok, and just as easy to work with. First check if you
 have a file called .xinitrc in your home directory, if it exists,
 rename it to .xinitrc.sav to move it out the way for a bit (so you
 can always rename it back later if you want) with:
 
 mv ~/.xinitrc ~/.xinitrc.sav
 
 Now create a brand new .xinitrc file in your home directory, it will
 be exactly the same as the .xsession file you made earlier, so if
 you still have the .xsession file just do:
 
 cp ~/.xsession ~/.xinitrc
 
 Or if you need to create, or want to check, the new .xinitrc file
 then it should contain:
 
 #!/bin/sh
 xrdb -merge ~/.Xdefaults 
 icewm 
 idesk 
 while [ 1 ] ; do
 sleep 1000d
 done

And if the session lasts longer?

Seriously, though, why not use the standard:

  idesk 
  icewm

?

 
 As long as no-one has modified the X startup scripts (which is very
 unlikely for most systems), this should work, well, hopefully :-)
 
 Also, I think there is a better way to start X than using a bashrc
 file - but we'll get to that later, 

Right. Start a new X session for each new console login. For each ssh
login. For each screen session. Have fun.

BTW: users of Squeeze / Sid might want to take a look at the package
nodm.

-- 
Tzafrir Cohen | tzaf...@jabber.org | VIM is
http://tzafrir.org.il || a Mutt's
tzaf...@cohens.org.il ||  best
ICQ# 16849754

Re: starting Idesk automatically in IceWM on Lenny

[Tim Clewlow]

 On Friday 16 October 2009 13:42:25 Tim Clewlow wrote:
 Ok, I found out that there is an error in the .xsession file, the
 correct version is below, note the line 'icewm ' has now become
 'icewm-session ' - this should bring back the correct background
 and hopefully the mouse will behave noremally again :-)

 #!/bin/sh
 xrdb -merge ~/.Xdefaults 
 icewm-session 
 idesk 
 while [ 1 ] ; do
 sleep 1000d
 done

 Our emails crossed!

 I have both IceWM _and_ idesk running correctly. \0/

 Just out of interest, and because it would obviously be easy to
 reverse, I
 uncommented startx in .bash_profile.  I then rebooted.

 And I have a fully operational system, but for that error message,
 so
 something is still not right - but hey, the presenting problem has
 been
 solved.  So if you want to breathe a sigh of relief and bring the
 shutters
 down, I shall still be greatly indebted to you.

 But if you have the stamina, and enough of the will to live, I would
 love to
 sort it out properly.

 Many thanks,
 cheers,
 Lisi



Might as well make it perfect :-) If you want X to start up
automatically at boot, comment out the startx command in the
bash.profile file, and install xdm.

As root do:

apt-get install xdm

Now reboot - you should have a nice graphical user / pass thing to
play with. If you want to get rid of the graphical login, then in a
shell terminal also as root do:

update-rc.d -f xdm remove

If you change your mind and want to get it back again later do (as
root):

update-rc.d -f xdm defaults

Hopefully this will get the system to behave how you want.

Cheers, Tim.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Tim Clewlow]

 Is it?
 Let's look at /etc/X11/Xsession
 $ grep HOME /etc/X11/Xsession
 USRRESOURCES=$HOME/.Xresources
 USERXSESSION=$HOME/.xsession
 USERXSESSIONRC=$HOME/.xsessionrc
 ALTUSERXSESSION=$HOME/.Xsession
 ERRFILE=$HOME/.xsession-errors
 $ grep USERXSESSION /etc/X11/Xsession /etc/X11/Xsession.d/*
 /etc/X11/Xsession:USERXSESSION=$HOME/.xsession
 /etc/X11/Xsession:USERXSESSIONRC=$HOME/.xsessionrc
 /etc/X11/Xsession:ALTUSERXSESSION=$HOME/.Xsession
 /etc/X11/Xsession.d/40x11-common_xsessionrc:if [ -r
 $USERXSESSIONRC ]; then
 /etc/X11/Xsession.d/40x11-common_xsessionrc:  . $USERXSESSIONRC
/etc/X11/Xsession.d/50x11-common_determine-startup:for
 STARTUPFILE in $USERXSESSION $ALTUSERXSESSION; do
 /etc/X11/Xsession.d/50x11-common_determine-startup:
 ERRMSG=$ERRMSG no \$USERXSESSION\ file, no \$ALTUSERXSESSION\
file,


It is. The real problem appears to be multiple instances of X
attempting to start due to having 'startx' in a shell rc.


 Or if you need to create, or want to check, the new .xinitrc file
then it should contain:
 #!/bin/sh
 xrdb -merge ~/.Xdefaults 
 icewm 
 idesk 
 while [ 1 ] ; do
 sleep 1000d
 done
 And if the session lasts longer?
 Seriously, though, why not use the standard:
   idesk 
   icewm
 ?

Because this way I can start terminals with commands ending with 
**after** the wm has started, and not have to worry about
accidentally killing X because I just exited the controlling
terminal - which happens rarely, but enough to be annoying.

Cheers, Tim.

-- 
The code that never executes at all is the fastest.





-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Lisi]

On Wednesday 14 October 2009 00:34:57 Tim Clewlow wrote:
  On Tuesday 13 October 2009 10:43:21 Tim Clewlow wrote:
  You can rearrange the order in which things are started in your
  .xsession file, ie you dont have to start the window manager last.
 
  [snip]
 
  Basically, when the script finishes, X will close - so dont let
  the
  script finish - thats what the long sleeping loop at the end is
  for.
  I'm guessing your .xsession should look something like:
 
  #!/bin/sh
  xrdb -merge ~/.Xdefaults 
  icewm 
  sleep 1
  other apps 
  idesk 
 
  while [ 1 ] ; do
  sleep 1000d
  done
 
 
  The line 'sleep 1' is intended to be a little delay to give icewm
  time to start up before attempting to run idesk. It may not
  actually
  be necessary, or it may be too small a delay, it all depends on
  how
  idesk determines if icewm is running, ie it may look for a lock
  file
  created really quickly by icewm, or it may look for a process that
  may take some time to appear.
[snip]
  I am beginning to think that either it is simply not doable, or it
  is doable -
  but not by me. :-(

 I installed icewm and idesk, created a directory ~/.idesktop and
 then started X with .xsession containing the following:

 #!/bin/sh
 xrdb -merge ~/.Xdefaults 
 icewm 
 idesk 

 while [ 1 ] ; do
 sleep 1000d
 done


 Idesk seems to start up fine, ie I had icewm running and an icon at
 the top left that looks kind of like a house with the text 'Idesk'
 written underneath.

Thank you very much for trying this out.

Yes - if you have not created any other icons, that is what you should see.

I, however, still don't. :-(  There is obviously something else either running 
or not running as it ought to do.

Before trying this one, I did rm .bash_profile so that that would not be 
muddying the waters.  I then did exactly as you had done.  X failed to start.  
So I added startx to your script.  Not surprisingly, that made no difference.  
So I recreated .bash_profile and put startx in it.

That gave me a functional system - but no desktop.  Just a nasty hashed 
greying out grid.  Etc.  I have spent quite some time googling, and trying 
things out on my test system, including via the configuration files.  We know 
that this works for you, and that it works for me if I start idesk manually.  
About the only thing I can think of to try is starting X differently.  But 
how?

You have done so much already, but I would be very grateful if you could tell 
me how you start X on your system.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Tim Clewlow]

 On Wednesday 14 October 2009 00:34:57 Tim Clewlow wrote:
  On Tuesday 13 October 2009 10:43:21 Tim Clewlow wrote:
  You can rearrange the order in which things are started in
your
  .xsession file, ie you dont have to start the window manager
 last.
  [snip]
  Basically, when the script finishes, X will close - so dont
let
  the
  script finish - thats what the long sleeping loop at the end
is
  for.
  I'm guessing your .xsession should look something like:
  #!/bin/sh
  xrdb -merge ~/.Xdefaults 
  icewm 
  sleep 1
  other apps 
  idesk 
  while [ 1 ] ; do
  sleep 1000d
  done
  The line 'sleep 1' is intended to be a little delay to give
 icewm
  time to start up before attempting to run idesk. It may not
  actually
  be necessary, or it may be too small a delay, it all depends
on
  how
  idesk determines if icewm is running, ie it may look for a
lock
  file
  created really quickly by icewm, or it may look for a process
 that
  may take some time to appear.
 [snip]
  I am beginning to think that either it is simply not doable, or
 it
  is doable -
  but not by me. :-(
 I installed icewm and idesk, created a directory ~/.idesktop and
then started X with .xsession containing the following:
 #!/bin/sh
 xrdb -merge ~/.Xdefaults 
 icewm 
 idesk 
 while [ 1 ] ; do
 sleep 1000d
 done
 Idesk seems to start up fine, ie I had icewm running and an icon at
 the top left that looks kind of like a house with the text
'Idesk'
 written underneath.
 Thank you very much for trying this out.
 Yes - if you have not created any other icons, that is what you
 should see.
 I, however, still don't. :-(  There is obviously something else
 either running
 or not running as it ought to do.
 Before trying this one, I did rm .bash_profile so that that
would
 not be
 muddying the waters.  I then did exactly as you had done.  X
failed
 to start.
 So I added startx to your script.  Not surprisingly, that made no
difference.
 So I recreated .bash_profile and put startx in it.
 That gave me a functional system - but no desktop.  Just a nasty
hashed
 greying out grid.  Etc.  I have spent quite some time googling,
and
 trying
 things out on my test system, including via the configuration
files.
  We know
 that this works for you, and that it works for me if I start idesk
manually.
 About the only thing I can think of to try is starting X
 differently.  But
 how?
 You have done so much already, but I would be very grateful if you
could tell
 me how you start X on your system.
 Lisi

It sounds like your system is not using the xsession method of
managing an X session, which means it is using the native xinit
method. That's ok, and just as easy to work with. First check if you
have a file called .xinitrc in your home directory, if it exists,
rename it to .xinitrc.sav to move it out the way for a bit (so you
can always rename it back later if you want) with:

mv ~/.xinitrc ~/.xinitrc.sav

Now create a brand new .xinitrc file in your home directory, it will
be exactly the same as the .xsession file you made earlier, so if
you still have the .xsession file just do:

cp ~/.xsession ~/.xinitrc

Or if you need to create, or want to check, the new .xinitrc file
then it should contain:

#!/bin/sh
xrdb -merge ~/.Xdefaults 
icewm 
idesk 
while [ 1 ] ; do
sleep 1000d
done

As long as no-one has modified the X startup scripts (which is very
unlikely for most systems), this should work, well, hopefully :-)

Also, I think there is a better way to start X than using a bashrc
file - but we'll get to that later, first we need to get X starting
up the way you want it.

Cheers Tim.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Tim Clewlow]

 I don't run the xserver by entering startx in the console.  I have
it starting
 and running automatically via an entry in ~/.bash_profile.
 All entries in your .Xsession or similar must end with , so
 they'll
 run in the background, except the last one. This last one should be
 your window manager. For instance, mine's this:
 exec xscreensaver -no-splash 
 exec /usr/bin/fluxbox
 Yours should be:
 exec idesk 
 exec /path/to/otherapp 
 exec /usr/bin/icewm
 I've tried idesk before and gave up for some reason, but i think
i
 had
 it working...
 I have it working well - but only from the command lime, by
entering
 the idesk
 command.  And even then, on one of the computers, as a child of
the
 terminal,
 so that X shuts down if I close the terminal; and when it does
 start, it only
 starts up if Icewm is running
 But I want it to run automatically at startup.
 Thanks for your help.
 Lisi



You can rearrange the order in which things are started in your
.xsession file, ie you dont have to start the window manager last.
Eg, my .xsession looks like:

#!/bin/sh
xrdb -merge ~/.Xdefaults 
xset -b
wmaker 
sleep 1
xclock -geometry 60x60-1-1 
aterm -tr -trsb -sh 50 -geometry 160x64+70+5 

while [ 1 ] ; do
sleep 1000d
done


Basically, when the script finishes, X will close - so dont let the
script finish - thats what the long sleeping loop at the end is for.
I'm guessing your .xsession should look something like:

#!/bin/sh
xrdb -merge ~/.Xdefaults 
icewm 
sleep 1
other apps 
idesk 

while [ 1 ] ; do
sleep 1000d
done


The line 'sleep 1' is intended to be a little delay to give icewm
time to start up before attempting to run idesk. It may not actually
be necessary, or it may be too small a delay, it all depends on how
idesk determines if icewm is running, ie it may look for a lock file
created really quickly by icewm, or it may look for a process that
may take some time to appear.

Cheers, Tim.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Lisi]

On Monday 12 October 2009 23:02:19 Nuno Magalhães wrote:
 On Mon, Oct 12, 2009 at 22:52, Lisi lisi.re...@gmail.com wrote:
 [...]

  Yes.  But I omitted to mention that because I forgot, that putting an 
  after both startx and Idesk results in Idesk running correctly - but only
  if and when I open a terminal: and Idesk then closes when I shut the
  terminal down.

 Why are you using startx in a .Xsession? If you're running the X
 server by entering startx in the console, then having startx in
 .Xsession will launch a second X server, no? So, regardless of how you
 start up your X, the .Xsession file should not contain startx.

I don't run the xserver by entering startx in the console.  I have it starting 
and running automatically via an entry in ~/.bash_profile.

 All entries in your .Xsession or similar must end with , so they'll
 run in the background, except the last one. This last one should be
 your window manager. For instance, mine's this:

 exec xscreensaver -no-splash 
 exec /usr/bin/fluxbox

 Yours should be:

 exec idesk 
 exec /path/to/otherapp 
 exec /usr/bin/icewm

 I've tried idesk before and gave up for some reason, but i think i had
 it working...

I have it working well - but only from the command lime, by entering the idesk 
command.  And even then, on one of the computers, as a child of the terminal, 
so that X shuts down if I close the terminal; and when it does start, it only 
starts up if Icewm is running

But I want it to run automatically at startup.

Thanks for your help.

Lisi


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Lisi]

On Tuesday 13 October 2009 10:43:21 Tim Clewlow wrote:
 You can rearrange the order in which things are started in your
 .xsession file, ie you dont have to start the window manager last.
[snip]
 Basically, when the script finishes, X will close - so dont let the
 script finish - thats what the long sleeping loop at the end is for.
 I'm guessing your .xsession should look something like:

 #!/bin/sh
 xrdb -merge ~/.Xdefaults 
 icewm 
 sleep 1
 other apps 
 idesk 

 while [ 1 ] ; do
 sleep 1000d
 done


 The line 'sleep 1' is intended to be a little delay to give icewm
 time to start up before attempting to run idesk. It may not actually
 be necessary, or it may be too small a delay, it all depends on how
 idesk determines if icewm is running, ie it may look for a lock file
 created really quickly by icewm, or it may look for a process that
 may take some time to appear.

Thanks for this and for the lucid explanation.  Sadly, it didn't work any 
better than the others.  Differently, but not better.  IceWM started to open, 
then x crashed out.  I also tried various changes to see if they would help.  
E.g., as you suggested I changed the sleep time.  But I also commented out 
and commented back in the xrdb line.  It made no difference which I did.

So I am left with the best being to put startx in ~/.bash_profile and start 
idesk from the command line - but that is not acceptable.

I am beginning to think that either it is simply not doable, or it is doable - 
but not by me. :-(

Lisi




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Tim Clewlow]

 On Tuesday 13 October 2009 10:43:21 Tim Clewlow wrote:
 You can rearrange the order in which things are started in your
 .xsession file, ie you dont have to start the window manager last.
 [snip]
 Basically, when the script finishes, X will close - so dont let
 the
 script finish - thats what the long sleeping loop at the end is
 for.
 I'm guessing your .xsession should look something like:

 #!/bin/sh
 xrdb -merge ~/.Xdefaults 
 icewm 
 sleep 1
 other apps 
 idesk 

 while [ 1 ] ; do
 sleep 1000d
 done


 The line 'sleep 1' is intended to be a little delay to give icewm
 time to start up before attempting to run idesk. It may not
 actually
 be necessary, or it may be too small a delay, it all depends on
 how
 idesk determines if icewm is running, ie it may look for a lock
 file
 created really quickly by icewm, or it may look for a process that
 may take some time to appear.

 Thanks for this and for the lucid explanation.  Sadly, it didn't
 work any
 better than the others.  Differently, but not better.  IceWM started
 to open,
 then x crashed out.  I also tried various changes to see if they
 would help.
 E.g., as you suggested I changed the sleep time.  But I also
 commented out
 and commented back in the xrdb line.  It made no difference which I
 did.

 So I am left with the best being to put startx in ~/.bash_profile
 and start
 idesk from the command line - but that is not acceptable.

 I am beginning to think that either it is simply not doable, or it
 is doable -
 but not by me. :-(

 Lisi




 --
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org



I installed icewm and idesk, created a directory ~/.idesktop and
then started X with .xsession containing the following:

#!/bin/sh
xrdb -merge ~/.Xdefaults 
icewm 
idesk 

while [ 1 ] ; do
sleep 1000d
done


Idesk seems to start up fine, ie I had icewm running and an icon at
the top left that looks kind of like a house with the text 'Idesk'
written underneath.

-- 
The code that never executes at all is the fastest.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

starting Idesk automatically in IceWM on Lenny

[Lisi]

The box boots automatically into IceWM in 32 seconds from a standing start.

I have Idesk configured to my satisfaction, and it runs beautifully if I start 
it manually after I have booted up and IceWM is running.  

Any attempt, however, to make Idesk also start automatically, results in Idesk 
running fine - but not X and IceWM.  The desktop looks odd (as if it hasn't 
finished loading), and although all the icons work and the applications start 
up and function correctly, when I shut down an application, X shuts down with 
it.

I have Googled repeatedly; and tried out every permutation I could think of in 
every file that I either found recommended or could dream up.  I have looked 
in a large number of books.  I have got Idesk running fine - but never IceWm 
simultaneously.

I think that I need to put Idesk into one of the configuration files.  But 
which

TIA
Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Nuno Magalhães]

On Mon, Oct 12, 2009 at 21:32, Lisi lisi.re...@gmail.com wrote:
[...]
 Any attempt, however, to make Idesk also start automatically, results in Idesk
 running fine - but not X and IceWM.  The desktop looks odd (as if it hasn't
 finished loading), and although all the icons work and the applications start
 up and function correctly, when I shut down an application, X shuts down with
 it.

What do you mean by any atempt? Idesk must have a .start script, maybe
under .idesk, are you issuing something like:
exec /path/to/idesk 
with the ending ?

Under bash or dash? Dunno if it matters but the default shell was
recently changed.

-- 
()  ascii-rubanda kampajno - kontraŭ html-a retpoŝto
/\  ascii ribbon campaign - against html e-mail


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Lisi]

On Monday 12 October 2009 22:25:03 Nuno Magalhães wrote:
 On Mon, Oct 12, 2009 at 21:32, Lisi lisi.re...@gmail.com wrote:
 [...]

  Any attempt, however, to make Idesk also start automatically, results in
  Idesk running fine - but not X and IceWM.  The desktop looks odd (as if
  it hasn't finished loading), and although all the icons work and the
  applications start up and function correctly, when I shut down an
  application, X shuts down with it.

 What do you mean by any atempt? Idesk must have a .start script, maybe
 under .idesk, are you issuing something like:
 exec /path/to/idesk 
 with the ending ?

Yes.  But I omitted to mention that because I forgot, that putting an  after 
both startx and Idesk results in Idesk running correctly - but only if and 
when I open a terminal: and Idesk then closes when I shut the terminal down. 


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Andrew Sackville-West]

On Mon, Oct 12, 2009 at 09:32:55PM +0100, Lisi wrote:
 The box boots automatically into IceWM in 32 seconds from a standing start.
 
 I have Idesk configured to my satisfaction, and it runs beautifully if I 
 start 
 it manually after I have booted up and IceWM is running.  
 
 Any attempt, however, to make Idesk also start automatically, results in 
 Idesk 
 running fine - but not X and IceWM.  The desktop looks odd (as if it hasn't 
 finished loading), and although all the icons work and the applications start 
 up and function correctly, when I shut down an application, X shuts down with 
 it.

how are you starting Idesk automatically? 

 
 I have Googled repeatedly; and tried out every permutation I could think of 
 in 
 every file that I either found recommended or could dream up.  I have looked 
 in a large number of books.  I have got Idesk running fine - but never IceWm 
 simultaneously.
 
 I think that I need to put Idesk into one of the configuration files.  But 
 which

the way I would do it is in ~/.xinitrc

Idesk 
ice-wm

but it's been at least 4 years since I ran that same setup, so my
memory is fuzzy.

A


signature.asc
Description: Digital signature

Re: starting Idesk automatically in IceWM on Lenny

[Nuno Magalhães]

On Mon, Oct 12, 2009 at 22:52, Lisi lisi.re...@gmail.com wrote:
[...]
 Yes.  But I omitted to mention that because I forgot, that putting an  after
 both startx and Idesk results in Idesk running correctly - but only if and
 when I open a terminal: and Idesk then closes when I shut the terminal down.

Why are you using startx in a .Xsession? If you're running the X
server by entering startx in the console, then having startx in
.Xsession will launch a second X server, no? So, regardless of how you
start up your X, the .Xsession file should not contain startx.

All entries in your .Xsession or similar must end with , so they'll
run in the background, except the last one. This last one should be
your window manager. For instance, mine's this:

exec xscreensaver -no-splash 
exec /usr/bin/fluxbox

Yours should be:

exec idesk 
exec /path/to/otherapp 
exec /usr/bin/icewm

I've tried idesk before and gave up for some reason, but i think i had
it working...

HTH

-- 
()  ascii-rubanda kampajno - kontraŭ html-a retpoŝto
/\  ascii ribbon campaign - against html e-mail


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Lorenzo Beretta]

Lisi ha scritto:

The box boots automatically into IceWM in 32 seconds from a standing start.

I have Idesk configured to my satisfaction, and it runs beautifully if I start 
it manually after I have booted up and IceWM is running.  

Any attempt, however, to make Idesk also start automatically, results in Idesk 
running fine - but not X and IceWM.  The desktop looks odd (as if it hasn't 
finished loading), and although all the icons work and the applications start 
up and function correctly, when I shut down an application, X shuts down with 
it.
My guess: the startup file in icewm is supposed to do something and then 
exit (hint, hint)...


I have Googled repeatedly; and tried out every permutation I could think of in 
every file that I either found recommended or could dream up.  I have looked 
in a large number of books.  I have got Idesk running fine - but never IceWm 
simultaneously.


I think that I need to put Idesk into one of the configuration files.  But 
which


TIA
Lisi



err... how about ~/.icewm/startup?
something like idesk  should do the trick; if it does not work,
try with (sleep 3; idesk) 


good luck


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: starting Idesk automatically in IceWM on Lenny

[Lisi]

On Monday 12 October 2009 22:56:28 Andrew Sackville-West wrote:
 On Mon, Oct 12, 2009 at 09:32:55PM +0100, Lisi wrote:
  The box boots automatically into IceWM in 32 seconds from a standing
  start.
 
  I have Idesk configured to my satisfaction, and it runs beautifully if I
  start it manually after I have booted up and IceWM is running.
 
  Any attempt, however, to make Idesk also start automatically, results in
  Idesk running fine - but not X and IceWM.  
  I think that I need to put Idesk into one of the configuration files. 
  But which

 the way I would do it is in ~/.xinitrc

 Idesk 
 ice-wm

Thanks, Andrew.  I hadn't tried that order.  I have now tried it.  It has a 
slightly different background from all the other failure. :-(

Lisi




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

FIXED: can't get a terminal in icewm until after I start iceweasel

[Hendrik Boom]

I upgraded everything to current yesterday, and booted with kernel 
2.6.30-1-486, and now the terminal comes up properly.

I have no idea which of these updates made it work, but it works now.

-- hendrik


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

RE: can't get a terminal in icewm until after I start iceweasel

[Kevin Ross]

 This is in testing (currently squeeze, I believe).
 
 I log in using gdm.  My default window manager is icewm.
 I click on the little square icon on the bar at the bottom 
 (the one that 
 says XTerm in a white box when I hover the nouse over it), 
 and nothing 
 happens.
 
 I do this repeatedly, and still nothing happens.
 
 I start iceweasel, and wait until it comes up.
 
 Now, when I press the xterm icon, an xterm comes up quickly.
 
 Presumably, iceweasel starts some kind of service that the so-called 
 xterm depends on.  I say so-called because this is *not* 
 the terminal I 
 get when following the menu
 
 debian-Programs-Applications-Terminal Emulators-xterm,
 
 which does not respond to control-plus.  I suspect the terminal I get 
 from the icon may be the same as the one I get by following
 
 debian-Programs-Applications-Terminal Emulators-Gnome 
 Terminal, which 
 does honour control-plus and also won't start up before iceweasel.
 
 -- hendrik

One way to see what terminal program you're running is with the ps aux
command.

To determine why gnome-terminal won't start, try starting it from the
command line, and looking at the output.  To do this, log in via gdm on the
computer, and then switch to another virtual terminal (by hitting
Ctrl+Alt+F1), log in if necessary, and run the following:

gnome-terminal --display=:0

If it fails to start, it should output something indicating why.

You can switch back to your graphical desktop with Ctrl+Alt+F7.

Hope this helps!
-- Kevin


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: can't get a terminal in icewm until after I start iceweasel

[Hendrik Boom]

On Fri, 31 Jul 2009 01:38:41 -0700, Kevin Ross wrote:

 This is in testing (currently squeeze, I believe).
 
 I log in using gdm.  My default window manager is icewm. I click on the
 little square icon on the bar at the bottom (the one that
 says XTerm in a white box when I hover the nouse over it), and
 nothing
 happens.
 
 I do this repeatedly, and still nothing happens.
 
 I start iceweasel, and wait until it comes up.
 
 Now, when I press the xterm icon, an xterm comes up quickly.
 
 Presumably, iceweasel starts some kind of service that the so-called
 xterm depends on.  I say so-called because this is *not* the terminal
 I
 get when following the menu
 
 debian-Programs-Applications-Terminal Emulators-xterm,
 
 which does not respond to control-plus.  I suspect the terminal I get
 from the icon may be the same as the one I get by following
 
 debian-Programs-Applications-Terminal Emulators-Gnome Terminal,
 which
 does honour control-plus and also won't start up before iceweasel.
 
 -- hendrik
 
 One way to see what terminal program you're running is with the ps aux
 command.
 
 To determine why gnome-terminal won't start, try starting it from the
 command line, and looking at the output.  To do this, log in via gdm on
 the computer, and then switch to another virtual terminal (by hitting
 Ctrl+Alt+F1), log in if necessary, and run the following:
 
 gnome-terminal --display=:0
 
 If it fails to start, it should output something indicating why.
 
 You can switch back to your graphical desktop with Ctrl+Alt+F7.

Instead, I first opened an ordinary xterm, and did the following:

hend...@lovesong:~$ gnome-terminal 
[1] 7064
hend...@lovesong:~$ Failed to contact the GConf daemon; exiting.

[1]+  Exit 1  gnome-terminal
hend...@lovesong:~$ 

A clue, but it's possible that xterm doesn't set up the right environment.

Following your instructions, the output from 

gnome-terminal --display=:0

gave a few more details: 

Failed to get the session bus: dbus-launch failed to autolaunch D-Bus 
session: Autolaunch error: X11 initialization failed.

Falling back to non-factory mode.
Failed to contact the GConf daemon; exiting.

So evidently, gnome-terminal has trouble setting up some kind of dbus 
channel.  Once firefox is up, though, the channel must be ready and 
waiting.  So firefox manages to set up something that genome-terminal 
fails at.  Is this a deficiency in gnome-terminal?  Or is it some 
horrible configuration problem that failed to upgrade correctly?  This 
*is* testing, after all.

 
 Hope this helps!

I hope so too!

 -- Kevin

-- hendrik



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

can't get a terminal in icewm until after I start iceweasel

[Hendrik Boom]

This is in testing (currently squeeze, I believe).

I log in using gdm.  My default window manager is icewm.
I click on the little square icon on the bar at the bottom (the one that 
says XTerm in a white box when I hover the nouse over it), and nothing 
happens.

I do this repeatedly, and still nothing happens.

I start iceweasel, and wait until it comes up.

Now, when I press the xterm icon, an xterm comes up quickly.

Presumably, iceweasel starts some kind of service that the so-called 
xterm depends on.  I say so-called because this is *not* the terminal I 
get when following the menu

debian-Programs-Applications-Terminal Emulators-xterm,

which does not respond to control-plus.  I suspect the terminal I get 
from the icon may be the same as the one I get by following

debian-Programs-Applications-Terminal Emulators-Gnome Terminal, which 
does honour control-plus and also won't start up before iceweasel.

-- hendrik


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

New IceWm

[Frank McCormick]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1




Update of my Sid/Squeeze system included a new V of Icewm...which
doesn't like many of the themes I have installed.
That I can probably fixbut this has me puzzledit's from
xsession errors


icewmbg: using /home/frank/.icewm for private configuration files
icewmtray: using /home/frank/.icewm for private configuration files
icewmtray: Warning: latency: 0.287177
IceWM: Warning: latency: 0.209190
IceWM: Warning: latency: 0.053682

** (totem-gstreamer:3737): WARNING **: Failed to create dbus proxy
for org.gnome.SettingsDaemon: Could not get owner of name
'org.gnome.SettingsDaemon': no such name IceWM: Warning: latency:
0.088051 
1 IceWM: Warning: latency: 0.072680 IceWM: Warning: latency:
0.077447



What on earth is warning: latency: whatever number

There is nothing in the docs about it.


- -- 
Frank  fmccorm...@videotron.ca
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkocPToACgkQIyN89Z1rCtGwUgCaAvUUuaBbKYBXfKoxcSdagZnw
JssAnR1EXrWDsilP2ktX5F98mwD+HO9L
=x3Hh
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: IceWM och focus-follows-mouse i Lenny

[Bjorn Wiren]

Peter Krefting pe...@softwolves.pp.se writes:

 Hej!

 Uppgraderade min huvudmaskin från Etch till Lenny häromdagen, och allt
 fungerar fint, bortsett från en detalj: Jag kan inte få min
 fönsterhanterare IceWM att flytta fokus mellan fönster genom att bara
 peka på dem längre, som jag kunde tidigare.

 Sedan tidigare hade jag dessa inställningar:

   #  Focus windows by clicking
   ClickToFocus=0 # 0/1

   #  Raise windows when focused
   RaiseOnFocus=0 # 0/1

 och det fungerade. Jag försökte hitta en lösning, och hittade en
 referens till att jag borde lägga in

   FocusMode=0

 men det hjälpte inte. Jag måste fortfarande klicka för att fokusera,
 vilket är ganska irriterande... Är det någon som vet vad jag behöver
 göra för att få det att fungera?

Skumt, det var just det som löste problemet för mig. Här är några av
mina inställningar (men bara de två första borde ha betydelse för det
här):

% grep '^[^#]' ~/.icewm/preferences
FocusMode=0
ClickToFocus=0 # 0/1
RequestFocusOnAppRaise=0 # 0/1
RaiseOnFocus=0 # 0/1
RaiseOnClickClient=0 # 0/1
RaiseOnClickTitleBar=1 # 0/1
LowerOnClickWhenRaised=1 # 0/1
FocusOnMap=0 # 0/1
...

Mvh
-- 
Björn Wirén


--
To UNSUBSCRIBE, email to debian-user-swedish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

IceWM och focus-follows-mouse i Lenny

[Peter Krefting]

Hej!

Uppgraderade min huvudmaskin från Etch till Lenny häromdagen, och allt 
fungerar fint, bortsett från en detalj: Jag kan inte få min fönsterhanterare 
IceWM att flytta fokus mellan fönster genom att bara peka på dem längre, som 
jag kunde tidigare.


Sedan tidigare hade jag dessa inställningar:

  #  Focus windows by clicking
  ClickToFocus=0 # 0/1

  #  Raise windows when focused
  RaiseOnFocus=0 # 0/1

och det fungerade. Jag försökte hitta en lösning, och hittade en referens 
till att jag borde lägga in


  FocusMode=0

men det hjälpte inte. Jag måste fortfarande klicka för att fokusera, vilket 
är ganska irriterande... Är det någon som vet vad jag behöver göra för att 
få det att fungera?


--
\\// Peter - http://www.softwolves.pp.se/


--
To UNSUBSCRIBE, email to debian-user-swedish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: IceWM och focus-follows-mouse i Lenny

[Jonathan Abolins]

Hej!

 fungerar fint, bortsett från en detalj: Jag kan inte få min 
 fönsterhanterare IceWM att flytta fokus mellan fönster genom att bara peka 
 på dem längre, som jag kunde tidigare.

Kolla i IceWM meny:n, under 'Settings'. Det borde finnas en 'Focus'
instaellning, som du kan aendra till 'Custom'.

mvh.


-- 
To UNSUBSCRIBE, email to debian-user-swedish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

banshee in icewm

[Ólafur Jens Sigurðsson]

Hi

I was wondering if people had some experience with running banshee
under IceWM ... I can run it fine in Gnome (as another user) but when
I try to start it up in IceWM this is what I get:

[Info  22:24:34.380] Running Banshee 1.0.0

Unhandled Exception: Mono.Data.SqliteClient.SqliteSyntaxException: no
such table: SmartPlaylists
  at Mono.Data.SqliteClient.SqliteCommand.GetNextStatement (IntPtr
pzStart, System.IntPtr pzTail, System.IntPtr pStmt) [0x0] 
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader
(CommandBehavior behavior, Boolean want_results, System.Int32
rows_affected) [0x0] 
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteNonQuery () [0x0] 
  at Hyena.Data.Sqlite.HyenaSqliteCommand.Execute
(Hyena.Data.Sqlite.HyenaSqliteConnection hconnection,
Mono.Data.SqliteClient.SqliteConnection connection) [0x00093] in
/tmp/buildd/banshee-1.0.0/src/Libraries/Hyena/Hyena.Data.Sqlite/HyenaSqliteCommand.cs:116

TIA

Oli


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Icewm lost! Can't reinstall

[Anthony Campbell]

On 2008-02-08 17:26 +0100, Anthony Campbell wrote:

 On 08 Feb 2008, Sven Joachim wrote:
 There are now updated packages of libgif4 available which include
 a transitional package for libungif4g, see
 http://packages.qa.debian.org/g/giflib/news/20080207T090208Z.html.
 
 Sven
 

 I think that's the one that caused the problem in the first place. If I
 installed it I would get this:

 The following extra packages will be installed:
   gdk-imlib11 imlib11 libgif-dev libungif4-dev
 The following packages will be REMOVED
   feh giblib1 habak icewm icewm-experimental idesk libimlib2 libungif4g 
 mplayer
 The following NEW packages will be installed
   libgif-dev libgif4
 The following packages will be upgraded:
   gdk-imlib11 imlib11 libungif4-dev
 3 upgraded, 2 newly installed, 9 to remove and 3 not upgraded.

Your mirror is not quite up to date.  You need version 4.6.1-3 of

libgif4, where these transitional packages were added.  Since you
successfully downgraded imlib11 and reinstalled icewm, there is no need
to hurry, though.

The problem you encountered was triggered by the upload of imlib11
version 1.9.15-6, which was the first package to link against libgif4.
See the thread I started on
http://lists.debian.org/debian-release/2008/02/msg00065.html. 


Thanks, but this doesn't seem to be right.  I take it 4.6.1-3 is a typo
for 4.1.6-3? In that case, that's the one I was looking at, and it's the
only such package listed on the Debian site. And it still gives the
REMOVE message if I were to install it -- which, as you say, I won't do
for the moment.

Anthony


-- 
Anthony Campbell - [EMAIL PROTECTED] 
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews, 
on-line books and sceptical articles)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Icewm lost! Can't reinstall

[Sven Joachim]

On 2008-02-09 11:49 +0100, Anthony Campbell wrote:

 On 08 Feb 2008, Sven Joachim wrote:
Your mirror is not quite up to date.  You need version 4.6.1-3 of
 
libgif4, where these transitional packages were added.  Since you
successfully downgraded imlib11 and reinstalled icewm, there is no need
to hurry, though.

The problem you encountered was triggered by the upload of imlib11
version 1.9.15-6, which was the first package to link against libgif4.
See the thread I started on
http://lists.debian.org/debian-release/2008/02/msg00065.html. 


 Thanks, but this doesn't seem to be right.  I take it 4.6.1-3 is a typo
 for 4.1.6-3?

Yes, sorry.

 In that case, that's the one I was looking at, and it's the
 only such package listed on the Debian site. And it still gives the
 REMOVE message if I were to install it -- which, as you say, I won't do
 for the moment.

Hm, what command exactly do you use?  For me, aptitude safe-upgrade
duly installed libgif4 and upgraded imlib11 when the transitional
libungif4g package became available.

Sven


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Icewm lost! Can't reinstall

[Sven Joachim]

On 2008-02-09 13:13 +0100, Anthony Campbell wrote:

 I'm not using aptitude. I used wajig show-install libgif4.

 But wajig show-install imlib11 gives this:

  wajig showinstall imlib11
 Reading package lists... Done
 Building dependency tree   
 Reading state information... Done
 The following extra packages will be installed:
   libgif4 libungif4g
 The following NEW packages will be installed
   libgif4
 The following packages will be upgraded:
   imlib11 libungif4g
 2 upgraded, 1 newly installed, 0 to remove and 5 not upgraded.
 Inst libungif4g [4.1.4-5] (4.1.6-3 Debian:unstable) []
 Inst libgif4 (4.1.6-3 Debian:unstable)
 Inst imlib11 [1.9.15-5] (1.9.15-6 Debian:unstable)
 Conf libgif4 (4.1.6-3 Debian:unstable)
 Conf libungif4g (4.1.6-3 Debian:unstable)
 Conf imlib11 (1.9.15-6 Debian:unstable)


 That looks as if it should be safe, but I'm not sure.

It is okay, just go on.  It's the same as aptitude did on my system
yesterday.  If you have libungif4-dev installed, you should upgrade that
package as well (will pull in libgif-dev).

Sven


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Icewm lost! Can't reinstall

[Anthony Campbell]

On 09 Feb 2008, Sven Joachim wrote:
 On 2008-02-09 11:49 +0100, Anthony Campbell wrote:
 
  On 08 Feb 2008, Sven Joachim wrote:
 Your mirror is not quite up to date.  You need version 4.6.1-3 of
  
 libgif4, where these transitional packages were added.  Since you
 successfully downgraded imlib11 and reinstalled icewm, there is no need
 to hurry, though.
 
 The problem you encountered was triggered by the upload of imlib11
 version 1.9.15-6, which was the first package to link against libgif4.
 See the thread I started on
 http://lists.debian.org/debian-release/2008/02/msg00065.html. 
 
 
  Thanks, but this doesn't seem to be right.  I take it 4.6.1-3 is a typo
  for 4.1.6-3?
 
 Yes, sorry.
 
  In that case, that's the one I was looking at, and it's the
  only such package listed on the Debian site. And it still gives the
  REMOVE message if I were to install it -- which, as you say, I won't do
  for the moment.
 
 Hm, what command exactly do you use?  For me, aptitude safe-upgrade
 duly installed libgif4 and upgraded imlib11 when the transitional
 libungif4g package became available.
 
 Sven
 
I'm not using aptitude. I used wajig show-install libgif4.

But wajig show-install imlib11 gives this:

 wajig showinstall imlib11
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following extra packages will be installed:
  libgif4 libungif4g
The following NEW packages will be installed
  libgif4
The following packages will be upgraded:
  imlib11 libungif4g
2 upgraded, 1 newly installed, 0 to remove and 5 not upgraded.
Inst libungif4g [4.1.4-5] (4.1.6-3 Debian:unstable) []
Inst libgif4 (4.1.6-3 Debian:unstable)
Inst imlib11 [1.9.15-5] (1.9.15-6 Debian:unstable)
Conf libgif4 (4.1.6-3 Debian:unstable)
Conf libungif4g (4.1.6-3 Debian:unstable)
Conf imlib11 (1.9.15-6 Debian:unstable)


That looks as if it should be safe, but I'm not sure.

Anthony



-- 
Anthony Campbell - [EMAIL PROTECTED] 
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews, 
on-line books and sceptical articles)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Icewm lost! Can't reinstall

[Anthony Campbell]

On 09 Feb 2008, Sven Joachim wrote:
 On 2008-02-09 13:13 +0100, Anthony Campbell wrote:
 
  I'm not using aptitude. I used wajig show-install libgif4.
 
  But wajig show-install imlib11 gives this:
 
   wajig showinstall imlib11
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
libgif4 libungif4g
  The following NEW packages will be installed
libgif4
  The following packages will be upgraded:
imlib11 libungif4g
  2 upgraded, 1 newly installed, 0 to remove and 5 not upgraded.
  Inst libungif4g [4.1.4-5] (4.1.6-3 Debian:unstable) []
  Inst libgif4 (4.1.6-3 Debian:unstable)
  Inst imlib11 [1.9.15-5] (1.9.15-6 Debian:unstable)
  Conf libgif4 (4.1.6-3 Debian:unstable)
  Conf libungif4g (4.1.6-3 Debian:unstable)
  Conf imlib11 (1.9.15-6 Debian:unstable)
 
 
  That looks as if it should be safe, but I'm not sure.
 
 It is okay, just go on.  It's the same as aptitude did on my system
 yesterday.  If you have libungif4-dev installed, you should upgrade that
 package as well (will pull in libgif-dev).
 
 Sven

Thanks -- that went OK!


Anthony

 
-- 

Anthony Campbell - [EMAIL PROTECTED] 
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews, 
on-line books and sceptical articles)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Icewm lost! Can't reinstall

[Jochen Schulz]

Anthony Campbell:

 Icewm has been deleted automatically in an upgrade of Sid yesterday.

No, it did not happen automatically. You should read what aptitude is
about to do before confirming that this is what you want it to do. :)

Using 'safe-upgrade' instead of 'full-upgrade' by default is a good idea
anyway.

 I tried to reinstall but got:
 
 =
 The following packages have unmet dependencies.
   icewm: Depends: libungif4g (= 4.1.4)
 E: Broken packages
 ===

 I've put in a bug report but meanwhile it's a major disaster, though
 fortunately only on one computer so I'm holding back on the others.
 
 Anyone else met this one?

Sure. But I didn't remove IceWM. :) You should be able to downgrade it,
though.

J.
-- 
I no longer believe in father christmas but have no trouble
comprehending a nuclear apocalypse.
[Agree]   [Disagree]
 http://www.slowlydownward.com/NODATA/data_enter2.html


signature.asc
Description: Digital signature

Icewm lost! Can't reinstall

[Anthony Campbell]

Icewm has been deleted automatically in an upgrade of Sid yesterday.
I tried to reinstall but got:

=
The following packages have unmet dependencies.
  icewm: Depends: libungif4g (= 4.1.4)
E: Broken packages
===

I've put in a bug report but meanwhile it's a major disaster, though
fortunately only on one computer so I'm holding back on the others.

Anyone else met this one?


Anthony

-- 
Anthony Campbell - [EMAIL PROTECTED] 
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews, 
on-line books and sceptical articles)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Icewm lost! Can't reinstall

[Sven Joachim]

On 2008-02-08 10:43 +0100, Anthony Campbell wrote:

 Icewm has been deleted automatically in an upgrade of Sid yesterday.
 I tried to reinstall but got:

 =
 The following packages have unmet dependencies.
   icewm: Depends: libungif4g (= 4.1.4)
 E: Broken packages
 ===

 I've put in a bug report but meanwhile it's a major disaster, though
 fortunately only on one computer so I'm holding back on the others.

 Anyone else met this one?

There are now updated packages of libgif4 available which include
a transitional package for libungif4g, see
http://packages.qa.debian.org/g/giflib/news/20080207T090208Z.html.

Sven


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Icewm lost! Can't reinstall

[Ron Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/08/08 07:24, Anthony Campbell wrote:
 On 08 Feb 2008, Jochen Schulz wrote:
 Anthony Campbell:
 Icewm has been deleted automatically in an upgrade of Sid yesterday.
 No, it did not happen automatically. You should read what aptitude is
 about to do before confirming that this is what you want it to do. :)

 Using 'safe-upgrade' instead of 'full-upgrade' by default is a good idea
 anyway.

 
 I'm not using aptitude, largely because it has removed all kinds of
 things it shouldn't when I used it in the past, though safe-upgrade
 sounds good. I like wajig -- it does warn you before removing things
 though I missed it on this occasion.

If you know that it warns you about proposed removals, why did you
allow it to remove IceWM?

 Sure. But I didn't remove IceWM. :) You should be able to downgrade it,
 though.

 I was able to reinstall it from /var/cache/apt/archives.
 
 Anthony
 


- --
Ron Johnson, Jr.
Jefferson LA  USA

PETA - People Eating Tasty Animals
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHrGk6S9HxQb37XmcRAvybAKC0xtSFY18kqsyQQHOO5M5qcAJPOwCg7xL6
F1CfaOxy0iR+yi9G3GeogJw=
=5ECd
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Icewm lost! Can't reinstall

[Anthony Campbell]

On 08 Feb 2008, Sven Joachim wrote:
 On 2008-02-08 10:43 +0100, Anthony Campbell wrote:
 
  Icewm has been deleted automatically in an upgrade of Sid yesterday.
  I tried to reinstall but got:
 
  =
  The following packages have unmet dependencies.
icewm: Depends: libungif4g (= 4.1.4)
  E: Broken packages
  ===
 
  I've put in a bug report but meanwhile it's a major disaster, though
  fortunately only on one computer so I'm holding back on the others.
 
  Anyone else met this one?
 
 There are now updated packages of libgif4 available which include
 a transitional package for libungif4g, see
 http://packages.qa.debian.org/g/giflib/news/20080207T090208Z.html.
 
 Sven
 

I think that's the one that caused the problem in the first place. If I
installed it I would get this:

The following extra packages will be installed:
  gdk-imlib11 imlib11 libgif-dev libungif4-dev
The following packages will be REMOVED
  feh giblib1 habak icewm icewm-experimental idesk libimlib2 libungif4g mplayer
The following NEW packages will be installed
  libgif-dev libgif4
The following packages will be upgraded:
  gdk-imlib11 imlib11 libungif4-dev
3 upgraded, 2 newly installed, 9 to remove and 3 not upgraded.




-- 
Anthony Campbell - [EMAIL PROTECTED] 
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews, 
on-line books and sceptical articles)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Icewm lost! Can't reinstall

[Anthony Campbell]

On 08 Feb 2008, Jochen Schulz wrote:
 Anthony Campbell:
 
  Icewm has been deleted automatically in an upgrade of Sid yesterday.
 
 No, it did not happen automatically. You should read what aptitude is
 about to do before confirming that this is what you want it to do. :)
 
 Using 'safe-upgrade' instead of 'full-upgrade' by default is a good idea
 anyway.
 

I'm not using aptitude, largely because it has removed all kinds of
things it shouldn't when I used it in the past, though safe-upgrade
sounds good. I like wajig -- it does warn you before removing things
though I missed it on this occasion.

 
 Sure. But I didn't remove IceWM. :) You should be able to downgrade it,
 though.
 
I was able to reinstall it from /var/cache/apt/archives.

Anthony

-- 
Anthony Campbell - [EMAIL PROTECTED] 
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews, 
on-line books and sceptical articles)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Icewm lost! Can't reinstall

[Sven Joachim]

On 2008-02-08 17:26 +0100, Anthony Campbell wrote:

 On 08 Feb 2008, Sven Joachim wrote:
 There are now updated packages of libgif4 available which include
 a transitional package for libungif4g, see
 http://packages.qa.debian.org/g/giflib/news/20080207T090208Z.html.
 
 Sven
 

 I think that's the one that caused the problem in the first place. If I
 installed it I would get this:

 The following extra packages will be installed:
   gdk-imlib11 imlib11 libgif-dev libungif4-dev
 The following packages will be REMOVED
   feh giblib1 habak icewm icewm-experimental idesk libimlib2 libungif4g 
 mplayer
 The following NEW packages will be installed
   libgif-dev libgif4
 The following packages will be upgraded:
   gdk-imlib11 imlib11 libungif4-dev
 3 upgraded, 2 newly installed, 9 to remove and 3 not upgraded.

Your mirror is not quite up to date.  You need version 4.6.1-3 of
libgif4, where these transitional packages were added.  Since you
successfully downgraded imlib11 and reinstalled icewm, there is no need
to hurry, though.

The problem you encountered was triggered by the upload of imlib11
version 1.9.15-6, which was the first package to link against libgif4.
See the thread I started on
http://lists.debian.org/debian-release/2008/02/msg00065.html. 

Sven


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Icewm lost! Can't reinstall

[Anthony Campbell]

On 08 Feb 2008, Ron Johnson wrote:
 If you know that it warns you about proposed removals, why did you
 allow it to remove IceWM?
 


Obviously I missed the warning.

-- 
Anthony Campbell - [EMAIL PROTECTED] 
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews, 
on-line books and sceptical articles)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Como fazer IceWM ficar mais leve

[gunix]

Galera,

uso o IceWM no terminais burros da empresa.
Sorem ele é bem pesado.

Alguem sabe se o XDMCP possui alguma opção ou parametro para ele usar 256
cores como o RDP da microsoft?

Att
Gustavo

Re: alt+tab freeze si hold : bug icewm ou autre ?

[Aurelien]

On Tue, Dec 11, 2007 at 03:39:57PM +0100, Aurélien Roux wrote :
 Salut,
 
 Je tourne sous Debian AMD 64 SID mis à jour, et justement, depuis la
 dernière mise à jour, alt+tab freeze.
 J'ai une carte ATI X800 GTO 16 avec un driver libre, avec DRI
 fonctionnel, et je fonctionne avec icewm.
 Aucune trace d'erreur dans les logs de xorg.
 
 Est-ce que quelqu'un d'auter observe cela ? Avec le même wm ? Pour voir
 si je fais un rapport de bug, ou si c'est moi qui fais n'importe quoi !
 ;)

J'ai eu le temps de tester avec xfce, et je ne retrouve pas le problème,
il doit donc probablement s'agir d'un bug icewm.

-- 
==
ORL /// AMMD Booking (www.ammd.net)
° Sebkha-Chott (www.sebkhachott.net - Ohreland [FR]) - next touring 
period: 04-06/2008
° Unexpect (www.unexpect.com - Montréal [CA]) - Europe tour w/ 
Sebkha-Chott period: 09-12/2008
° La Muette (www.myspace.com/muette - Paris [FR]) - next touring 
period: 03-05/2008
° Mel-P (http://melpmusic.websanslimit.net - Le Mans [FR]) - next 
touring period: 01-04/2008
Phone: +33 (0)95 234 72 48


-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench   
Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et
Reply-To:

To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: alt+tab freeze si hold : bug icewm ou autre ?

[arenevier]

Aurelien [EMAIL PROTECTED] wrote:
 Salut,
 
 Je tourne sous Debian AMD 64 SID mis à jour, et justement, depuis la
 dernière mise à jour, alt+tab freeze.
 J'ai une carte ATI X800 GTO 16 avec un driver libre, avec DRI
 fonctionnel, et je fonctionne avec icewm.
 Aucune trace d'erreur dans les logs de xorg.
 
 Est-ce que quelqu'un d'auter observe cela ? Avec le même wm ? Pour voir
 si je fais un rapport de bug, ou si c'est moi qui fais n'importe quoi !
 ;)

C'est un bug de xorg (le bug #452167) qui se manifeste sur icewm. Pour
l'instant, j'ai réinstallé une ancienne version de xserver-xorg-core. En ce
que me concerne, c'était la version xserver-xorg-core_1.4-2_i386.deb trouvée
ici:
http://snapshot.debian.net/archive/2007/09/30/debian/pool/main/x/xorg-server/
J'imagine que pour amd64, c'est la même version qu'il faut prendre, mais je
n'en suis pas 100% sûr.

a+
arno


-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench   
Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et
Reply-To:

To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: alt+tab freeze si hold : bug icewm ou autre ?

[Aurelien]

On Wed, Dec 12, 2007 at 12:32:33PM +, [EMAIL PROTECTED] wrote :
 Aurelien [EMAIL PROTECTED] wrote:
  Salut,
  
  Je tourne sous Debian AMD 64 SID mis à jour, et justement, depuis la
  dernière mise à jour, alt+tab freeze.
  J'ai une carte ATI X800 GTO 16 avec un driver libre, avec DRI
  fonctionnel, et je fonctionne avec icewm.
  Aucune trace d'erreur dans les logs de xorg.
  
  Est-ce que quelqu'un d'auter observe cela ? Avec le même wm ? Pour voir
  si je fais un rapport de bug, ou si c'est moi qui fais n'importe quoi !
  ;)
 
 C'est un bug de xorg (le bug #452167) qui se manifeste sur icewm. Pour
 l'instant, j'ai réinstallé une ancienne version de xserver-xorg-core. En ce
 que me concerne, c'était la version xserver-xorg-core_1.4-2_i386.deb trouvée
 ici:
 http://snapshot.debian.net/archive/2007/09/30/debian/pool/main/x/xorg-server/
 J'imagine que pour amd64, c'est la même version qu'il faut prendre, mais je
 n'en suis pas 100% sûr.

OK, merci de l'info. J'avoue que j'avais pas trop le temps de chercher
en ce moment.

 
 a+
 arno
 
 
 -- 
 Lisez la FAQ de la liste avant de poser une question :
 http://wiki.debian.net/?DebianFrench   
 Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et
 Reply-To:
 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 

-- 
==
ORL /// AMMD Booking (www.ammd.net)
° Sebkha-Chott (www.sebkhachott.net - Ohreland [FR]) - next touring 
period: 04-06/2008
° Unexpect (www.unexpect.com - Montréal [CA]) - Europe tour w/ 
Sebkha-Chott period: 09-12/2008
° La Muette (www.myspace.com/muette - Paris [FR]) - next touring 
period: 03-05/2008
° Mel-P (http://melpmusic.websanslimit.net - Le Mans [FR]) - next 
touring period: 01-04/2008
Phone: +33 (0)95 234 72 48


-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench   
Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et
Reply-To:

To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

alt+tab freeze si hold : bug icewm ou autre ?

[Aurelien]

Salut,

Je tourne sous Debian AMD 64 SID mis à jour, et justement, depuis la
dernière mise à jour, alt+tab freeze.
J'ai une carte ATI X800 GTO 16 avec un driver libre, avec DRI
fonctionnel, et je fonctionne avec icewm.
Aucune trace d'erreur dans les logs de xorg.

Est-ce que quelqu'un d'auter observe cela ? Avec le même wm ? Pour voir
si je fais un rapport de bug, ou si c'est moi qui fais n'importe quoi !
;)

Merci.

-- 
==
ORL /// AMMD Booking (www.ammd.net)
° Sebkha-Chott (www.sebkhachott.net - Ohreland [FR]) - next touring 
period: 04-06/2008
° Unexpect (www.unexpect.com - Montréal [CA]) - Europe tour w/ 
Sebkha-Chott period: 09-12/2008
° La Muette (www.myspace.com/muette - Paris [FR]) - next touring 
period: 03-05/2008
° Mel-P (http://melpmusic.websanslimit.net - Le Mans [FR]) - next 
touring period: 01-04/2008
Phone: +33 (0)95 234 72 48


-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench   
Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et
Reply-To:

To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Anyone using icewm on Sid?

[Anthony Campbell]

On 19 Nov 2007, Andrei Popescu wrote:
 On Mon, Nov 19, 2007 at 08:46:23PM +0100, Florian Kulzer wrote:
  
   Yep, happens to me too, with icewm-session and -experimental. Something 
   is definitely wrong as the graphics in the toolbar are all messed up.  
   According to the aptitude log, icewm wasn't updated (on my machine) 
   since September. It is probably related to the latest xorg update.
  
  Which graphics hardware are you guys using? I noticed regressions with
  both my intel-based systems (desktop: 82Q963/Q965, laptop: 855GM). It
  seems that the video-intel driver now uses EXA by default; switching
  back to XAA made all my problems disappear. If you use other cards it
  might be worthwhile to check the relevant manpage for changes in default
  settings or suspicious new options. (At least, that helped me to
  figure out what was going on.)
 
 lspci | grep VGA
 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated 
 Graphics Device (rev 02)
 
 I'm too lazy to test your suggestion (I switched to XFCE4 just a while 
 ago).
 


I have a Matrox G550. As a workaround I've disabled the Ctrl-Esc
combination. 

I got a reply from the maintainer of xserver-xorg and I've sent him more
information.

Anthony

-- 
Anthony Campbell - [EMAIL PROTECTED] 
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews, 
on-line books and sceptical articles)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

xserver-xorg-video-intel 2:2.2.0-1 (was: Anyone using icewm on Sid?)

[Florian Kulzer]

On Mon, Nov 19, 2007 at 23:28:32 +0200, Andrei Popescu wrote:
 On Mon, Nov 19, 2007 at 08:46:23PM +0100, Florian Kulzer wrote:

[...]

  Which graphics hardware are you guys using? I noticed regressions with
  both my intel-based systems (desktop: 82Q963/Q965, laptop: 855GM). It
  seems that the video-intel driver now uses EXA by default; switching
  back to XAA made all my problems disappear. If you use other cards it
  might be worthwhile to check the relevant manpage for changes in default
  settings or suspicious new options. (At least, that helped me to
  figure out what was going on.)
 
 lspci | grep VGA
 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated 
 Graphics Device (rev 02)

My 855GM is currently unusable with KDE and the EXA default: Icons are
shown incorrectly, as are most fonts; it looks like half of the pixels
have been set to transparent in a checkerboard pattern.

I don't see any rendering artefacts with my Q965, but scrolling text in
terminal windows (manpages, etc.) has suddenly become slow and jerky.

Setting AccelMethod to XAA fixes all these issues.

 I'm too lazy to test your suggestion (I switched to XFCE4 just a while 
 ago).

It seems that these problems are unrelated to the original topic of this
thread anyway.

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Anyone using icewm on Sid?

[Anthony Campbell]

Following today's upgrade on Sid I've started getting complete lockups
in X. I thought at first it was a bug in xserver-xorg and submitted a
bug report but now I think it's to do with icewm.

In icewm you can bring up a menu with Ctrl-Esc. This is what causes the
lockup. If I bring the menu up with the mouse, but clicking on Start at
the bottom of the screen, everything works. However, as I have the habit
of bring up the menu via the keys I'm going to get a lot of lockups
unless I change window manager.

Anyone else seeing this?

-- 
Anthony Campbell - [EMAIL PROTECTED] 
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews, 
on-line books and sceptical articles)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Anyone using icewm on Sid?

[Andrei Popescu]

On Mon, Nov 19, 2007 at 06:20:03PM +, Anthony Campbell wrote:
 Following today's upgrade on Sid I've started getting complete lockups
 in X. I thought at first it was a bug in xserver-xorg and submitted a
 bug report but now I think it's to do with icewm.
 
 In icewm you can bring up a menu with Ctrl-Esc. This is what causes the
 lockup. If I bring the menu up with the mouse, but clicking on Start at
 the bottom of the screen, everything works. However, as I have the habit
 of bring up the menu via the keys I'm going to get a lot of lockups
 unless I change window manager.
 
 Anyone else seeing this?

Yep, happens to me too, with icewm-session and -experimental. Something 
is definitely wrong as the graphics in the toolbar are all messed up.  
According to the aptitude log, icewm wasn't updated (on my machine) 
since September. It is probably related to the latest xorg update.

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: Digital signature

Re: Anyone using icewm on Sid?

[Florian Kulzer]

On Mon, Nov 19, 2007 at 21:20:52 +0200, Andrei Popescu wrote:
 On Mon, Nov 19, 2007 at 06:20:03PM +, Anthony Campbell wrote:
  Following today's upgrade on Sid I've started getting complete lockups
  in X. I thought at first it was a bug in xserver-xorg and submitted a
  bug report but now I think it's to do with icewm.
  
  In icewm you can bring up a menu with Ctrl-Esc. This is what causes the
  lockup. If I bring the menu up with the mouse, but clicking on Start at
  the bottom of the screen, everything works. However, as I have the habit
  of bring up the menu via the keys I'm going to get a lot of lockups
  unless I change window manager.
  
  Anyone else seeing this?
 
 Yep, happens to me too, with icewm-session and -experimental. Something 
 is definitely wrong as the graphics in the toolbar are all messed up.  
 According to the aptitude log, icewm wasn't updated (on my machine) 
 since September. It is probably related to the latest xorg update.

Which graphics hardware are you guys using? I noticed regressions with
both my intel-based systems (desktop: 82Q963/Q965, laptop: 855GM). It
seems that the video-intel driver now uses EXA by default; switching
back to XAA made all my problems disappear. If you use other cards it
might be worthwhile to check the relevant manpage for changes in default
settings or suspicious new options. (At least, that helped me to
figure out what was going on.)

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Anyone using icewm on Sid?

[Jochen Schulz]

Anthony Campbell:

 Following today's upgrade on Sid I've started getting complete lockups
 in X. I thought at first it was a bug in xserver-xorg and submitted a
 bug report but now I think it's to do with icewm.

Same here with current IceWM and X.org from unstable. The machine wasn't
completely dead, though. I could still shut it down cleanly by pressing
the poweroff button.

J.
-- 
People talking a foreign language are romantic and mysterious.
[Agree]   [Disagree]
 http://www.slowlydownward.com/NODATA/data_enter2.html


signature.asc
Description: Digital signature

Re: Anyone using icewm on Sid?

[Andrei Popescu]

On Mon, Nov 19, 2007 at 08:46:23PM +0100, Florian Kulzer wrote:
 
  Yep, happens to me too, with icewm-session and -experimental. Something 
  is definitely wrong as the graphics in the toolbar are all messed up.  
  According to the aptitude log, icewm wasn't updated (on my machine) 
  since September. It is probably related to the latest xorg update.
 
 Which graphics hardware are you guys using? I noticed regressions with
 both my intel-based systems (desktop: 82Q963/Q965, laptop: 855GM). It
 seems that the video-intel driver now uses EXA by default; switching
 back to XAA made all my problems disappear. If you use other cards it
 might be worthwhile to check the relevant manpage for changes in default
 settings or suspicious new options. (At least, that helped me to
 figure out what was going on.)

lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated 
Graphics Device (rev 02)

I'm too lazy to test your suggestion (I switched to XFCE4 just a while 
ago).

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: Digital signature

Re: Anyone using icewm on Sid?

[Jochen Schulz]

Andrei Popescu:
 On Mon, Nov 19, 2007 at 08:46:23PM +0100, Florian Kulzer wrote:
  
 Yep, happens to me too, with icewm-session and -experimental. Something 
 is definitely wrong as the graphics in the toolbar are all messed up.  
 According to the aptitude log, icewm wasn't updated (on my machine) 
 since September. It is probably related to the latest xorg update.
 
 Which graphics hardware are you guys using? [...]
 
 lspci | grep VGA
 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated 
 Graphics Device (rev 02)

Same here. Setting

Option AccelMethod XAA

in the device section of my xorg.conf (and subsequently restarting X)
didn't help, though. This would have surprised me anyway since the
lockup only occurs when opening the menu with Ctrl-Esc, not when using
the mouse or when pressing the left windows key.

J.
-- 
I wish I was gay.
[Agree]   [Disagree]
 http://www.slowlydownward.com/NODATA/data_enter2.html


signature.asc
Description: Digital signature

Re: Anyone using icewm on Sid?

[Frank McCormick]

On Mon, 19 Nov 2007 22:49:56 +0100
Jochen Schulz [EMAIL PROTECTED] wrote:

 Andrei Popescu:
  On Mon, Nov 19, 2007 at 08:46:23PM +0100, Florian Kulzer wrote:
   
  Yep, happens to me too, with icewm-session and -experimental.
  Something is definitely wrong as the graphics in the toolbar are
  all messed up. According to the aptitude log, icewm wasn't
  updated (on my machine) since September. It is probably related
  to the latest xorg update.
 Same here. Setting
 
 Option AccelMethod XAA
 
 in the device section of my xorg.conf (and subsequently restarting X)
 didn't help, though. This would have surprised me anyway since the
 lockup only occurs when opening the menu with Ctrl-Esc, not when using
 the mouse or when pressing the left windows key.


   My menu on IceWm pops up fine but I use the Windows key as well.
Definitely control-escape related.



-- 
Frank McCormick  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

To: IceWM users - and anyone else who wants to read

[icelinux]

Hello,
  I have recently started a custom Debian distribution project which
includes IceWM as the window manager for users of older computers such
as PII and PIII. Our goal is to ease the installation process for
IceWM and provide most users with the software they want or need
immediately after installation.
  I would appreciate it if those of you who use IceWM or those of you
who may consider using this flavor of Debian would send me an email
and let me know what programs or applications you use most and would
like to see included.
  Please reply off-list. Thanks in advance.


http://icelinux.net
Everything should be made as simple as possible, but not simpler.
Albert Einstein


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Tamanho dos ícones na barra de tarefas no IceWM

[Thiago Dias]

Olá! Uso o Icewm do Sarge como desktop padrão. Consegui personalizá-lo
copiando os arquivos de configuração de /etc/X11/icewm para a pasta ./icewm
no diretório do usuário. Através deles, pude pôr wallpaper e ícones na barra
de tarefas, além de outros ajustes finos. Porém, não consigo definir um
tamanho para esses ícones, ou seja, independentemente do tamanho original
dos ícones, eles continuam bem pequenos e, em alguns casos, até
irreconhecíveis. Qual é a linha responsável pelo tamanho da barra e/ou dos
ícones?