FWN/Issue284

From FedoraProject

< FWN
Jump to: navigation, search

Contents

Fedora Weekly News Issue 284

Welcome to Fedora Weekly News Issue 284[1] for the week ending August 17, 2011. What follows are some highlights from this issue.

We start this week's issue off with development announcements, including details on Fedora 16 Alpha and updates for Evolution in Fedora 16 and rawhide. In Ambassador news, highlights from discussion including regional and country meeting minutes and events from this past week. In Quality Assurance news, details on next week's internationalization and localization test week, updates on Fedora 16 Alpha preparation, and a new release of AutoQA. Security Advisories is next, with the latest security-related releases over the past week, and we conclude this issue with another great installment of Fedora LATAM, with a Spanish language look at the dwm window manager.

An audio version of some issues of FWN - FAWN - are available! You can listen to existing issues[2] on the Internet Archive. If anyone is interested in helping spread the load of FAWN production, please contact us!

If you are interested in contributing to Fedora Weekly News, please see our 'join' page[3]. We welcome reader feedback: news@lists.fedoraproject.org

FWN Editorial Team: Pascal Calarco, Adam Williamson

  1. http://fedoraproject.org/wiki/FWN/Issue284
  2. http://www.archive.org/search.php?query=subject%3A%22FWN%22
  3. http://fedoraproject.org/wiki/NewsProject/Join


Announcements

In this section, we cover announcements from the Fedora Project, including general announcements[1], development announcements[2] and Events[3].

Contributing Writer: Pascal Calarco

  1. http://lists.fedoraproject.org/pipermail/announce/
  2. http://lists.fedoraproject.org/pipermail/devel-announce/
  3. http://fedoraproject.org/wiki/Events

Fedora Announcements

There were no announcements this past week.

Fedora Development News

The Development Announcement[1] list is intended to be a LOW TRAFFIC announce-only list for Fedora development.

Acceptable Types of Announcements

  • Policy or process changes that affect developers.
  • Infrastructure changes that affect developers.
  • Tools changes that affect developers.
  • Schedule changes
  • Freeze reminders

Unacceptable Types of Announcements

  • Periodic automated reports (violates the INFREQUENT rule)
  • Discussion
  • Anything else not mentioned above
  1. https://admin.fedoraproject.org/mailman/listinfo/devel-announce

Fedora 16 Alpha is hereby declared GOLD!

Robyn Bergeron announced[1]:

"At the F16 Alpha Go/No-Go Meeting that just occurred, the Fedora 16 Alpha release was declared GOLD. F16 Alpha will be released Tuesday, August 23, 2011.

Thanks to all of those who helped out to make this happen, as always -- we wouldn't be here without everyone's assistance and hard work.

For those interested in the details...

Minutes:[2] Logs: [3]

Documentation folks: Please note that there is a known bug that is being requested to be documented in the Alpha release notes; details are in the logs/minutes. Thank you!!

Cheers,

-Robyn


Full minutes follow below:


  1. fedora-meeting: F16 Alpha Go/No-Go Meeting (redux)

Meeting started by adamw at 21:05:45 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2011-08-17/f16_alpha_gono-go_meeting_#2.2011-08-17-21.05.log.html

Meeting summary


  • roll call (adamw, 21:06:18)
  * present nirik tflink, thedonvaughn, pjones, athmane, gr72, nb,
    cebbert, viking_ice, boblfoot  (adamw, 21:07:33)
  • preamble (adamw, 21:07:49)
  * the Purpose of the Go/No-Go is to gather yay/nay's from Release
    Engineering, QA, and devel on whether or not what we have put
    together is ready for release and meets the release criteria.
    (adamw, 21:08:18)
  * LINK: http://fedoraproject.org/wiki/Fedora_15_Alpha_Release_Criteria
    (rbergeron, 21:10:36)
  * LINK: http://fedoraproject.org/wiki/Fedora_16_Alpha_Release_Criteria
    (rbergeron, 21:11:13)
  * LINK: https://fedoraproject.org/wiki/Current_Release_Blockers
    (rbergeron, 21:11:32)
  * LINK:
    https://fedoraproject.org/wiki/Test_Results:Fedora_16_Alpha_RC5_Install
    (adamw, 21:11:49)
  * LINK:
    https://fedoraproject.org/wiki/Test_Results:Fedora_16_Alpha_RC5_Base
    (adamw, 21:11:58)
  * There are no remaining proposed blockers, and no unresolved approved
    blockers.  (rbergeron, 21:11:58)
  * LINK:
    https://fedoraproject.org/wiki/Test_Results:Fedora_16_Alpha_RC5_Desktop
    (adamw, 21:12:11)
  * AGREED: : document 731529 as a known bug, to be fixed by beta as it
    is a blocker, in alpha release notes  (rbergeron, 21:18:41)
  * AGREED: document 731529 as a known bug, to be fixed by beta as it is
    a blocker, in alpha release notes  (rbergeron, 21:19:05)
  * ACTION: rbergeron to copy docs for release notes purposes on meeting
    minutes  (rbergeron, 21:19:30)
  * QA is a 'go' - no remaining unresolved blockers, test matrices look
    good.  (rbergeron, 21:20:20)
  • release engineering (rbergeron, 21:20:24)
  * release engineering is a 'go', no issues are known, nirik is
    channeling dgilmore. :)  (rbergeron, 21:22:52)
  • Devel (rbergeron, 21:22:58)
  * Nirik is in for fesco/devel - he is a go.  (rbergeron, 21:23:26)
  • It's a go! (rbergeron, 21:23:34)
  * Release will be tuesday, 2011-08-23.  (rbergeron, 21:23:55)
  * ACTION: rbergeron to send out meeting notes to appropriate lists.
    (rbergeron, 21:24:05)
  * RC5 is our guy. All parties needed for this meeting agree that we
    are GO.  (rbergeron, 21:24:27)
  • Any other business? (rbergeron, 21:25:33)
  * dgilmore has verified that releng is a go.  (rbergeron, 21:30:31)

Meeting ended at 21:30:52 UTC.

Action Items


  • rbergeron to copy docs for release notes purposes on meeting minutes
  • rbergeron to send out meeting notes to appropriate lists.

Action Items, by person


  • rbergeron
  * rbergeron to copy docs for release notes purposes on meeting minutes
  * rbergeron to send out meeting notes to appropriate lists.
  • **UNASSIGNED**
  * (none)

People Present (lines said)


  • rbergeron (57)
  • adamw (49)
  • nirik (16)
  • gr72 (11)
  • thedonvaughn (9)
  • jsmith (7)
  • nb (5)
  • zodbot (5)
  • Viking_Alpha (5)
  • pjones (4)
  • robatino (3)
  • tflink (2)
  • cebbert (2)
  • dgilmore (2)
  • BobLfoot (1)
  • jforbes_kvmforum (1)
  • clumens (1)
  • athmane (1)

  1. http://lists.fedoraproject.org/pipermail/devel-announce/2011-August/000826.html
  2. http://meetbot.fedoraproject.org/fedora-meeting/2011-08-17/f16_alpha_gono-go_meeting_%232.2011-08-17-21.05.html
  3. http://meetbot.fedoraproject.org/fedora-meeting/2011-08-17/f16_alpha_gono-go_meeting_%232.2011-08-17-21.05.log.html

Fedora 16 Alpha Go/No-Go Meeting #2, Wednesday, August 17 @ 17:00 EDT

Robyn Bergeron announced[1]:

"Sorry for belated notice, though I've talked to almost everyone involved about the timing - have been travelling.

Join us on irc.freenode.net #fedora-meeting for this important meeting.

Wednesday, August 17, 2011 @22:00 UTC (17:00 EDT/14:00 PDT)

"Before each public release Development, QA and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the: Go/No-Go Meeting."

"Verifying that the Release criteria are met is the responsibility of the QA Team."

For more details about this meeting see[2]

In the meantime, keep an eye on the Fedora 16 Alpha Blocker list[3]

-Robyn"

  1. http://lists.fedoraproject.org/pipermail/devel-announce/2011-August/000825.html
  2. https://fedoraproject.org/wiki/Go_No_Go_Meeting
  3. https://fedoraproject.org/wiki/Current_Release_Blockers

evolution-data-server's libcamel soname version bump in Fedora 16/rawhide for 3.1.90 next week

Milan Crha announced[1]:

"Hi,

Just after 3.1.5 release of evolution-data-server was added an API change in libcamel, thus the next week, when 3.1.90 will be released and I'll do an update in Fedora 16/rawhide, anything depending on libcamel will require a rebuild.

Again, I'll take care of everything I will be able to, and I'll also add it to the same update as evolution-data-server. After my yesterday turn, there are still packages I cannot do anything with, also because other dependency issues with them (like almanah depending on libcrypt), but I will do my best to make this (most likely final) soname version bump not that painful for others. Bye, Milan"

  1. http://lists.fedoraproject.org/pipermail/devel-announce/2011-August/000824.html

Fedora Events

The purpose of event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning. Events can be added to this page whether or not they have an Ambassador owner. Events without an owner are not eligible for funding, but being listed allows any Ambassador to take ownership of the event and make it eligible for funding. In plain words, Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!

Upcoming Events (June - August 2011)

  • North America (NA)[1]
  • Central & South America (LATAM): [2]
  • Europe, Middle East, and Africa (EMEA)[3]
  • India, Asia, Australia (India/APJ)[4]
  1. http://fedoraproject.org/wiki/Events#FY12_Q2_.28June_2011_-_August_2011.29
  2. http://fedoraproject.org/wiki/Events#FY12_Q2_.28June_2011_-_August_2011.29_2
  3. http://fedoraproject.org/wiki/Events#FY12_Q2_.28June_2011_-_August_2011.29_3
  4. http://fedoraproject.org/wiki/Events#FY12_Q2_.28June_2011_-_August_2011.29_4

Past Events

Archive of Past Fedora Events[1]

  1. http://fedoraproject.org/wiki/FedoraEvents/PastEvents

Additional information

  • Reimbursements -- reimbursement guidelines.
  • Budget -- budget for the current quarter (as distributed by FAMSCo).
  • Sponsorship -- how decisions are made to subsidize travel by community members.
  • Organization -- event organization, budget information, and regional responsibility.
  • Event reports -- guidelines and suggestions.
  • LinuxEvents -- a collection of calendars of Linux events.


Ambassadors

This section covers the news surrounding the Fedora Ambassadors Project[1].

Contributing Writer: Richard A Vijay

Covering activity of the Ambassadors list[2] for the period of 10th August 2011 to 18th August 2011

  1. http://fedoraproject.org/wiki/Ambassadors
  2. http://lists.fedoraproject.org/pipermail/ambassadors/

Beat this week

Hightlights from mailing lists

  • EMEA Ambassadors 10 August Minutes
  • Request to update Media Inventory
  • University of Bangladesh and Fedora 15 DVD distribution
  • FAD KL 2011 registations - Malaysia
  • Biweekly APAC meeting is on Saturday, August 20th, 2011 at 04:00 UTC
  • Classroom Series On Fedora Marketing Topics
  • Ambassador of Indonesia interviewed by newspaper
  • Ambassador Survey Results on FAmSco
  • FAmNA meeting for 2011-08-16

Welcome New Ambassadors

This week the Fedora Ambassadors Project had no new members reported.

Summary of traffic on Ambassadors mailing list

EMEA ambassadors meeting summary on 2011-08-10-20 from Christoph [1]

Request from Christoph to update Fedora media distribution Inventroy. Ambassadors, Please update the critical swag inventory information, Its essential to complete this update as soon as possible. [2]

Next APAC FAD meeting on Saturday 27th of August Agenda [3]

700 copies of Fedora 15 DVD were distributed in the university students of Bangladesh by Rejaul Islam [4]

FAD KL 2011 is open for registration - reported by Mohd Izhar Firdaus Ismail from Malaysia; more details in the Event section, below

Biweekly APAC meeting is on Saturday, August 20th, 2011 at 04:00 UTC is planned by David Ramsey [5] Find more info at [6]

French Fedora meeting held on 15 August 2011 [7]

Ambassador of Indonesia, Alzea, was interviewed by newpaper [8]

Review on Corporate needs and Fedora by Buddhika Kurera [9]

Meeting planned -FAmNA meeting for 2011-08-16 in #fedora-meeting at 21:00 EST [10]

FAmSCo Meeting

Classroom series covering marketing aspects of the fedora project to be conducted by Buddhika Kurera for FAms [11]

Events reported on Ambassadors mailing list

FAD KL 2011 is open for registration - Reproted by Mohd Izhar Firdaus Ismail [12]

Campus Ambassadors mailing list-Summary of traffic

Buddhika Kurera organises a Fedora Classroom session for FAms (no obligation for participating any other as well) on 2011-08-20 at 1300 UTC in #fedora-classroom [13]

More information [14]

  1. http://meetbot.fedoraproject.org/fedora-meeting/2011-08-10/fedora-meeting.2011-08-10-20.02.html
  2. http://lists.fedoraproject.org/pipermail/ambassadors/2011-August/018059.html
  3. http://lists.fedoraproject.org/pipermail/ambassadors/2011-August/018060.html
  4. http://lists.fedoraproject.org/pipermail/ambassadors/2011-August/018061.html
  5. http://lists.fedoraproject.org/pipermail/ambassadors/2011-August/018068.html
  6. https://fedoraproject.org/wiki/User:Bckurera/The_FAms_Way
  7. http://fedoraproject.org/wiki/R%C3%A9unions_hebdomadaires_de_la_French_team
  8. http://lists.fedoraproject.org/pipermail/ambassadors/2011-August/018080.html
  9. http://lists.fedoraproject.org/pipermail/ambassadors/2011-August/018091.html
  10. https://fedoraproject.org/wiki/Meeting:NA_Ambassadors_2011-08-16
  11. http://lists.fedoraproject.org/pipermail/ambassadors/2011-August/018072.html
  12. http://fedora.foss.org.my/events/fadkl092011/
  13. http://lists.fedoraproject.org/pipermail/campus-ambassadors/2011-August/000114.html
  14. https://fedoraproject.org/wiki/User:Bckurera/The_FAms_Way

QualityAssurance

In this section, we cover the activities of the QA team[1]. For more information on the work of the QA team and how you can get involved, see the Joining page[2].

Contributing Writer: Adam Williamson

  1. http://fedoraproject.org/wiki/QA
  2. http://fedoraproject.org/wiki/QA/Join

Test Days

Next week will be internationalization and localization test week, with three test days: desktop localization on Monday 2011-08-22[1], localization and internationalization in the installer on Wednesday 2011-08-24[2], and desktop internationalization on Friday 2011-08-26[3]. Fedora is used in many countries and many languages, so it's vital to make sure translations, keyboard layouts, input methods and so on are working well. There is also a significant new feature to test: GNOME input integration[4], which brings an integrated input method selector to the GNOME 3 desktop.

  1. http://fedoraproject.org/wiki/Test_Day:2011-08-22_L10n_Desktop
  2. http://fedoraproject.org/wiki/Test_Day:2011-08-24_L10n_I18n_Installation
  3. http://fedoraproject.org/wiki/Test_Day:2011-08-26_I18n_Desktop
  4. http://fedoraproject.org/wiki/Features/GnomeInputIntegration

Fedora 16 Alpha preparation

The team began the week with validation testing on the Fedora 16 Alpha release candidates, with RC2 landing on 2011-08-09[1] and RC3 following soon after[2]. RC3 unfortunately proved still to contain several blocker bugs, and so at the Go / No-Go meeting of 2011-08-10[3], the release was delayed by one week. The team worked with the development group to prepare for an RC4 build.

  1. http://lists.fedoraproject.org/pipermail/test-announce/2011-August/000262.html
  2. http://lists.fedoraproject.org/pipermail/test-announce/2011-August/000263.html
  3. http://meetbot.fedoraproject.org/fedora-meeting/2011-08-10/f16_alpha_gono-go_meeting.2011-08-10-21.00.html

Release criteria updates

Adam Williamson proposed modifying the release criteria and validation tests so that text-mode firstboot functionality would not be required[1].

  1. http://lists.fedoraproject.org/pipermail/test/2011-August/101727.html

AutoQA

The AutoQA team released version 0.6.1, and began work on planning AutoQA 0.7.0[1].

  1. http://fedorahosted.org/pipermail/autoqa-devel/2011-August/002751.html


Security Advisories

In this section, we cover Security Advisories from fedora-package-announce for the three weeks ending August 11, 2011.

http://lists.fedoraproject.org/pipermail/package-announce

Contributing Writer: Pascal Calarco

Fedora 15 Security Advisories

Fedora 14 Security Advisories


LATAM Fedora!

LATAM Fedora is a regular column of Spanish language contributions around open source software. It is our first expansion into incorporating foreign language content into FWN.

This week's contribution is from Guillermo Gómez, a review of the dwm window manager. Enjoy!

dwm

  1. yum install dwm

Cuando se intenta organizar ventanas en otros entornos de escritorio, la mayoría son una pesadilla, pruebe dwm, hiperligero, sólo para geeks. dwm consiste de un único binario de 54k (el distribuido por Fedora) que sólo se puede personalizar recompilando los fuentes. Ya veremos más adelante que en Fedora esto se puede hacer fácilmente.

Al comenzar ni sabrá cómo arrancar su primera aplicación, la documentación (man dwm) dice Mod4-Shift-Return para arrancar uxterm, eso se traduce usualmente a:

TeclaWin+Shift+Enter

   uxterm es un envoltorio para xterm, un emulador de terminal para X, ambos provistos por el paquete xterm.

A partir de ahí puede arrancar sus aplicaciones, si, desde un terminal, no olvide agregar el & para dejarla en el fondo, por ejemplo.

$ totem & dwm-user¶

dwm-user incluye los fuentes de dwm y el guión de arranque dwm-start.

  1. yum install dwm-user

Login

El paquete dwm provee una entrada /usr/share/xsessions/dwm.desktop y el paquete dwm-user incluye /usr/share/xsessions/dwm-user.desktop. La única diferencia es el modo de arranque.

dwm.desktop

[Desktop Entry] Type=Application Encoding=UTF-8 Name=dwm GenericName=Window Manager Comment=Dynamic window manager for X Exec=dwm Terminal=false TryExec=dwm

[Window Manager] SessionManaged=true

dwm-user.desktop =

[Desktop Entry] Type=Application Encoding=UTF-8 Name=dwm-user GenericName=Window Manager Comment=Dynamic window manager for X (user configuration) Exec=dwm-start Terminal=false TryExec=dwm-start

[Window Manager] SessionManaged=true </code>

dwm-start es el método de arranque preferido para DWM en Fedora ya que entonces podrá personalizar su entorno, esto significa compilar su versión de DWM con su versión de las cabeceras en su directorio personal sin intervención manual, ¡cool!.

Keybindings

Layouts

  • Mod4-t Poner la disposición tiled (cuadros).
  • Mod4-f Poner la disposición a floating (flotante).
  • Mod4-m Poner la disposición a monocle (monóxulo).
  • Mod4-Shift-space Conmuta la disposición de estado de la ventana enfocada entre tiled y flotante.

Navegar entre ventanas

  • Mod4-j Cambiar/enfocar la próxima ventana.
  • Mod4-k Cambiar/enfocar la ventana previa.
  • Mod4-Tab Cambia a los tags previamente seleccionados.

Area maestra

  • Mod4-h Decrementa el tamaño del área maestra.
  • Mod4-l Incrementa el tamaño del área maestra.
  • Mod4-Return Cicla/aumenta la ventana enfocada desde/hacia el área maestra (sólo en disposición de cuadros).


Salir/cerrar

  • Mod4-Shift-c Cerrar la ventana enfocada.
  • Mod4-Shift-q Salir de dwm.

Poniendo los tags a las ventanas

  • Mod4-Shift-[1..n] Aplica el tag n a la ventana enfocada.
  • Mod4-Button1-tagicon Aplica el tag n a la ventana enfocada (haga clic en la barra con botón izquierdo)
  • Mod4-Button2-tagicon Agrega el tag n a la ventana enfocada (haga clic en la barra con botón derecho)
  • Mod4-Shift-0 Aplica todos los tags a la ventana enfocada.

Dos pantallas

  • Para enviar una app de una pantalla a otra tiene las siguientes tres opciones:
  * En modo flotante, se puede simplemente arrastrar la ventana de una pantalla a otra.
  * Mod4-Shift-, envía la ventana con el foco a la pantalla previa, si hay alguna.
  * Mod4-Shift-. envía la ventana con el foco a la próxima pantalla, si hay alguna.

dmenu: lanzador de aplicaciones

dmenu es un menú dinámico para X (lanzador de aplicaciones).

  1. yum install dmenu

Para usarlo en dwm Fedora presione:

TeclaWin+p

Aparecerá un menú en la parte superior, en la medida que tipee se reducirán las opciones, termina tu selección, o navega con las teclas flecha, presiona enter y listo, su aplicación será iniciada, incluso puede utilizar tab para autocompletar.

Hacks

stalonetray systray

stalonetray es un systray simple, punto.

~/.dwm/config.h

static Rule rules[] = { /* class instance title tags mask isfloating */ { "stalonetray", NULL, "stalonetray", ~0, False }, };

Esto asegura que stalonetray sea visible a lo largo de todos los tags.

terminator en vez de uxterm

Mod4-Shift-Return de caja arranca uxterm, deseo cambiar eso a terminator

~/.dwm/config.h

1 /*static const char *termcmd[] = { "uxterm", NULL };*/ 2 static const char *termcmd[] = { "terminator", NULL };

tags con nombres

Tener los tags simplemente numerados es conveniente, pero tal vez sienta la necesidad de ponerles un nombre.

~/.dwm/config.h

/* tagging */ static const char *tags[] = { "term", "web", "email", "chat", "fm", "mmx", "7", "8", "9" };

Foco sigue al ratón, deshabilitar

No me gusta la idea de que el movimiento del ratón defina el foco de las ventanas, suele provocarme problemas por la sensibilidad de los touchpad y de los ratones ópticos que "se mueven solos" entonces cambian el foco de la ventana a una ventana que nada que ver con lo que estoy trabajando. En este caso debe comentar una declaración en el código fuente.

/usr/src/dwm-user-5.8.2-9.fc15/dwm.c

1 [DestroyNotify] = destroynotify, 2 /* [EnterNotify] = enternotify, */ 3 [Expose] = expose,

Y forzar una compilación, yo resolví ajustando ficticiamente por ejemplo un nombre de un tag y luego devolviendo el cambio (no estoy seguro que el sistema de construcción de dwm en Fedora note mis cambios en dwm.c).

Dos monitores al vuelo

Si iniciamos sesión DWM con los dos monitores encendidos en Fedora no hay problemas todo funciona al pelo, sin embargo, puede que necesite conectar y encender el segundo monitor una vez ya iniciada la sesión, por supuesto no queremos reiniciar nuestra sesión DWM. Casualmente me tropecé con esta circunstancia y reusé un pequeño script xrandr, la sorpresa es que no tuve que hacer nada con DWM, simplemente apareció el segundo monitor con sus nueve tags listo para trabajar. En resumidas, sólo debe configurar para detectar el segundo monitor, el script abajo es la forma que usé en mi laptop:

~/xrandr

xrandr --output VGA1 --mode 1280x1024 xrandr --output LVDS1 --mode 1280x800 xrandr --output VGA1 --left-of LVDS1

~/xrandr-alreves

xrandr --output VGA1 --mode 1024x768 xrandr --output LVDS1 --mode 1280x800 xrandr --output VGA1 --right-of LVDS1

La primera forma es para que el segundo monitor quede al lado izquierdo del primero, la segunda, al revés.

Aplicaciones systray

Ya sea con stalonetray o cualquier otro panel que incorpore un systray para el sistema, seguro deseará usar algunas de las siguientes aplicaciones:

  • nm-applet : applet para systray de Network Manager, le facilitará conectarse a redes.
  • PNMixer : mezclador de audio para el systray, le permitirá ajustar el volumen.
  • Empathy , cliente chat.
  • Pidgin , cliente chat.
  • batti, monitor de batería, suspender, hibernar.

Mi configuración feliz

Esta sección es para poner "mi configuración", mis ajustes, mis aplicaciones preferidas que se ajustan a mi manera de trabajar en dwm.

  • fbpanel configurado a lo mínimo, no toma foco y se esconde solo, lo veo cuando quiero :).
  • dmenu como lanzador de aplicaciones.
  • terminator como emulador de terminales.
  • tmux multiplexor de terminales.
  • pidgin cliente multiprotocolo para chat (irc, gtalk, identica, twitter, fb ).
  • pcmanfm es mi gestor de archivos gui preferido, seguido de nautilus.
  • totem y/o xine para ver películas y videos en general.
  • listen como reproductor de audio.
  • radiotray como reproductor de radio.
  • nm-applet para conectarme a redes.
  • batti para vigilar la batería de mi laptop, suspender e hibernar.
  • Pendiente bloqueo de pantalla.

Un pantallazo, por supuesto.

Referencias

Pendientes

  • Al usar tint2 este es sujeto de foco de ventana, quiero evitar ello ya que no deseo pasar por tint2 para llegar a otra aplicación, es en realidad el primer punto fastidioso para mi en el uso de dwm. Si tint2 aparece en todos los tags (algo deseable), entonces es sujeto de tener el foco, es una "ventana más flotante" (stalonetray sufre igual).
  • Con dos pantallas, en mi Fedora funciona perfecto, incluso mover las apps de una pantalla a otra, BUT, cómo etiqueto una app para que esté en la "otra" pantalla. En las dos pantallas tengo el panel con los 9 tags individuales del 1 al 9.
  • dmenu no se muestra correctamente, en mi laptop cuando arranco con dos monitores, dmenu no se muestra correctamente, el reconectar físicamente el segundo monitor repara la falla, es algo con el X o el propio dwm.

Gomix"