A volte accade che dopo aver installato il pacchetto nvidia dei repository o, alternativamente, il file .run, si esegue nvidia-xconfig e ci si ritrova la mappatura della tastiera inglese..

Vabè, non è grave, si risolve in fretta, però è leggermente fastidioso..

Terminale! (root)

• gnome

gedit /etc/X11/xorg.conf

• kde

kate /etc/X11/xorg.conf

• xfce

mousepad /etc/X11/xorg.conf

Modificate questa sezione (InputDevice) aggiungendo una riga:

Section "InputDevice"
Identifier     "Keyboard0"
Driver         "kbd"
Option         "XkbLayout" "it"
EndSection

Ah! Se volete levare anche il logo Nvidia all'avvio aggiungete anche quest'altra riga:

Section "Device"
Identifier     "Card0"
Driver         "nvidia"
VendorName     "nVidia Corporation"
BoardName      "G72 [GeForce 7500 LE]"
Option         "NoLogo" "True"
EndSection

P.S: Aggiungete solo la riga che vi serve, ma non modificate gli altri valori perchè cambiano da pc a pc.

Ora salvate e uscite.

Ora riavviate il pc o digitate sempre dal terminale:

/etc/init.d/gdm restart

P.S 2: In alcune distribuzioni (tipo in Arch, ma non parlo di Ubuntu e Debian perchè sono sicuro al 100% che sia così) il comando da fare è

/etc/rc.d/gdm restart

P.S 3: gdm va sostituito in base a quale DE usate (per KDE kdm)

Ora dovrebbe essere tutto a posto..

P.S 4: A me sta cosa è successa con Debian, con le altre distribuzioni non lo so se accade o no, ma credo che con Ubuntu e Arch non capiti proprio..

Per prima cosa dobbiamo essere sicuri di avere attivato il supporto 3d alla nostra scheda video, per questo vi rimando alla pagina composite del wiki ufficiale di ArchLinux, istruzioni valide anche per Debian/Ubuntu. Installiamo compiz-fusion dando un "apt-get install compiz-fusion" su debian/ubuntu. Per Arch Linux invece diamo un "pacman -S compiz-fusion-gtk" se ci interessa il supporto gtk, mentre "pacman -S compiz-fusion-kde" se ci interessa il supporto per KDE.

Una volta installato compiz-fusion se usate un login grafico come GDM o KDM aggiungete una nuova sessione "fusion" seguendo queste istruzioni:

1. sudo nano /usr/share/xsessions/fusion.desktop, e inserite le seguenti righe di codice:

[Desktop Entry]
Encoding=UTF-8
# This is the name you'll see for the session in gdm
Name=Fusion
# This is the comment
Comment=Compiz Fusion Standalone
# The command
Exec=/usr/local/bin/start-fusion.sh
Type=Application

2. sudo nano /usr/local/bin/start-fusion.sh, e inserite le seguenti righe di codice:

#!/bin/bash
compiz ccp &
emerald &
# qui aggiungete altri eventuali programmi da avviare in automatico come pypanel, tint, conky etc.

3. rendete lo script eseguibile con: sudo chmod +x /usr/local/bin/start-fusion.sh

4. All'avvio della sessione con KDM o GDM scegliete "fusion"

Se invece volete avviare compiz con startx perchè non utilizzate nessun login grafico seguite queste istruzioni:

1. sudo nano /home/tuonome/.xinitrc, e inserite una riga che punta ad uno script di avvio: exec /usr/local/bin/start-fusion.sh

2. salvate e create lo script di avvio: sudo nano usr/local/bin/start-fusion.sh

3. nello script di avvio potete provare ad avviare compiz con le diverse alternative che elenco di seguito:

#!/bin/bash
compiz ccp & oppure compiz --replace cpp & oppure fusion-icon
emerald &
#qui aggiungete altri programmi che intendete far avviare in automatico

Fine! Digitando startx potete avviare compiz! Per avere un menu col tasto destro, stile openbox potete utilizzare un plugin di compiz chiamato compiz-deskmenu disponibile per Arch Linux in AUR. Per configurare le opzioni di compiz-fusion utilizzate su Arch ccsm, su Debian/Ubuntu compiz-config-settings-manager.

Si on voulait faire tout cela très proprement, il faudrait plutôt regarder pourquoi il y a deux fois la ligne "LANG=..." dans le fichier "/etc/default/locale", car manifestement, c'est une erreur...

On my recently upgraded openSUSE 11.1 Factory (Alpha 0) I've just retried to get my KDE trunk checkout back to work again (after I unbroke my system after one canceled system upgrade). The first step was replacing kdm3 with kdm4 ... after a lot of fiddling with config files (/etc/sysconfigs/displaymanager), xessions, recompiling the kdm module, setting the right path variables, etc. I finally got it to work *sight*

But it has payed off.. it looks REALLY cool in the default theme :-)

Well... problem 1 -- Solved

Let's attack problem 2: KDE startup... I've removed my config files to get a clean setup.. well.. seems it was the wrong decision.. the current trunk (24.7.2008) has a bug which prevents the recreation of the configs (if I've understood the problem correctly) .. it's described here:

Mailing list entry: http://lists.kde.org/?l=kde-core-devel&m=121615750824656&w=2

I've tried the patch.. doesn't work.. I've tried the script.. doesn't work.. plasma just won't start.. krunner works, and all programs I start from it .. as far as I've seen plasma starts and disappears emmediately :-(

well... I'll try copying my config  files from my notebook to that pc.. hope that will work out.. stay tuned for some more news tomorrow ^^

btw: take a look at phoronix (http://www.phoronix.com) ... very interesting articles to read.. my favourite articles atm are about the upcoming improvements in the X-Server (GEM, DRI2, Kernel based mode settings) .. can't get enough of news about them ^^

Dunque era da un po' che avevo problemi nel cambiare il tema a kdm: dopo aver incasinato un po' tutto dando il solito spettacolo delle mie facoltà mentali ad ore improponibili, e dopo svariate installazioni / reinstallazioni / cancellazioni di kdm e gdm ero riuscito a trovare un compresso utilizzando kdm con il tema di default "debian-moreblue".

Stamane però, dopo una nottata di riposo, mi sono sentito fresco così tò che riprendo in mano il problema. Il file per configurare il display manager /etc/kde3/kdm/kdmrc non cagava di striscio le mie modifiche, così mi son detto - installiamo ed usiamo kdmtheme - ma un eloquente:

Override files found, selected theme will not have effect

mi ha ben fatto bestemmiare pensare... Vado di locate kdmrc:

/etc/kde3/kdmrc
/etc/kde3/kdm/kdmrc
/usr/share/doc/kde/HTML/en/kdm/kdmrc-ref.docbook
/usr/share/doc/kde/HTML/it/kdm/kdmrc-ref.docbook
/var/run/kdm/kdmrc

e beh ce n'è solo tre sono fortunato O_o!
Così mi avvento su quello situato in /var/run/ e FINALMENTE sono riuscito a cambiar tema!!

Note:

1. nelle mie scorribande tra file incomprensibili mi sono imbattuto anche in /etc/default/kdm.d/10_desktop-base con righe che richimavano sempre il tema di default, alchè ho azzerato le impostazioni con parametri vuoti (es. THEME="");
2. ho cambiato anche il background di kdm che viene impostato in /var/run/kdm/backgroundrc.

Lo primero de todo es instalar Xorg:

sudo aptitude install xserver-xorg xfonts-base

Durante la instalación, es posible que nos pregunte la resolución. Ahora, dependiendo de la tarjeta gráfica que tengamos:

sudo aptitude install xserver-xorg-video-ati xserver-xorg-video-vesa

En caso de ser cualquier otra tarjeta, podemos buscarla haciendo un aptitude search xserver-xorg-video- y elegir la nuestra. De todas formas, en un artículo posterior explicaré como instalar los drivers NO PROPIETARIOS de la ATI Radeon 9200SE.

Con esto ya tenemos instalada la base del sistema. Ahora vamos a instalar KDE y KDM (gestor de acceso):

sudo aptitude install kdebase kdm kde-i18n-es

De camino, instalamos todo lo relacionado con el audio:

sudo aptitude install alsa-base alsa-utils alsa-tools kmix

En teoría, ya está todo. Eso si, KDE está instalado si nada prácticamente, ni aplicaciones ni nada por el estilo. Luego las iremos añadiendo. Reiniciamos el sistema, y debería aparecernos la pantalla de kdm para identificarnos:

reboot

Si no fuese así, hacemos un

dpkg-reconfigure xserver-xorg

Una vez llegados a este punto, podemos empezar a instalar aplicaciones (con aptitude) para nuestro entorno, dentro de las cuales os recomiendo las siguientes:

• OpenOffice: paquete integrado sustituto de Microsoft Office.
• Firefox: para mi el mejor navegador que hay. En Debian lo deberéis instalar como Iceweasel.
• Akregator: un buen lector de feeds/rss.
• Kopete: mensajería instantánea multicuenta y multiprotocolo (msn, yahoo, jabber, etc..).
• Kmldonkey: para descargas p2p de la red edonkey (amule) y torrent.
• Konversation: un buen cliente de IRC.
• Amarok, audacious: reproductores para tus mp3.
• Mplayer: Reproductor de vídeo
• K3b: utilidad para grabación de cd/dvd
• Ksmoothdock: una barra de aplicaciones, al estilo de Avant Window Manager, pero mas simple y sin tanto efecto.
• y un sin fin mas de aplicaciones que encontrarás...

sudo /etc/init.d/kdm restart,

which gets frustrating in the long run. It seems that for some reason, kdm is loaded before the NIS services and thus it cannot see the remote logins. To fix this, move kdm later in the startup process:


cd /etc/rc2.d
sudo mv S13kdm S30kdm


This workaround worked for me. Postponing the kdm startup seems to have no side effects.

Yo me he decantado por usar KDE, pero cada uno deberá elegir la alternativa mas adecuada a sus necesidades. Eso no quiere decir que no haya probado otras opciones, como por ejemplo:

• Gnome: Rival directo de KDE. Tiene montones de aplicaciones propias (usa librerias GTK), y es uno de los mas usados. Si instalas Ubuntu, este será tu escritorio. Entre las aplicaciones mas conocidas de Gnome están: Nautilus como gestor de archivos, Evolution para manejo de e-mail y agenda, GIMP, el gran sustituto en de Photoshop, y un sinfín más.
• KDE: A la altura de Gnome, otro peso pesado. A mi parecer mas ligero que Gnome (sobre esto hay rios de opiniones) y mas configurable. Actualmente ha dado el salto a la versión 4, aunque la versión 3.5.9 sigue siendo instalada por defecto en la mayoría de instalaciones que eligen este DM. Dispone de Konqueror (gestor de archivos y navegación), Korganizer (agenda personal), Kmail (email), etc...
• XFCE: Considerado el hermano pequeño de GNOME, mucho mas ligero y por ello utilizado en muchas distribuciones y minidistros especialmente concebidas para los equipos menos potentes.
• IceWM: Otro entorno liviano. Configurable a base de archivos de texto y que, a diferencia de Fluxbox, si permite una barra e iconos, así como varios gagdets estilo reloj, medidor de CPU, etc...
• Fluxbox: Basado en BlackBox. Aquí tenemos otro entorno light. Fluxbox es conocido por la ausencia de iconos en el escritorio.
• Ratpoison: Este no lo he probado, pero según he podido leer, es muy usado por desarrolladores y programadores, parco en detalles estéticos y rápido, lo ideal para trabajar sin distracciones.

Además de estas, hay otras muchas opciones, pero las mas conocidas son las 5 primeras de las descritas arriba. Ahora bien, además del entorno, debemos elegir un gestor de acceso, que será la primera pantalla que veamos y que nos pedirá nos autentifiquemos en el sistema, además de darnos diversas opciones, como apagar, resetear o cambiar de usuario. Podemos elegir entre varios: GDM, KDM, y XDM, este último el gestor básico de X.

Aquí podeis ver unas imágenes (cortesía de Wikipedia):

This book covers many diverse topics. It starts with a discussion of common "reverse engineering tools" such as disassemblers, decompilers, and debuggers. It moves along to discuss low-level details of common system architectures and file formats. It then proceeds to talk about details of the compilation process, and how high-level code becomes low-level instructions.

Unfortunately, the title "Disassemblers, Debuggers, System Architectures, File Formats, Compilers and Low-level code Generation" doesn't roll off the tongue as well as "Reverse Engineering" does.

KDM

Knowledge Discovery Metamodel (KDM) is publicly available specification from the Object Management Group (OMG). KDM is a common intermediate representation for existing software systems and their operating environments, that defines common metadata required for deep semantic integration of Application Lifecycle Management tools. KDM was designed as the OMG's foundation for software modernization, IT portfolio management and software assurance. KDM uses OMG's Meta-Object Facility to define an XMI interchange format between tools that work with existing software as well as an abstract interface (API) for the next-generation assurance and modernization tools. KDM standardizes existing approaches to knowledge discovery in software engineering artifacts, also known as software mining.

MDRE

Principles of model discovery are based on a metamodel-driven approach (see Figure 1). It means that every step is guided by a metamodel. Thus, the very first step of a model discovery process is always to define the metamodel corresponding to the models you want to discover. This step is common to all kinds of systems.

Figure 1 Metamodel driven model discovery

Then, the second step is about creating one or many discovering tools that will be called “discoverers” in this document. These tools extract necessary information from the system in order to build a model conforming to the previously defined metamodel. The way to create these discoverers is often manual but can also be semi-automatic. The output of a discoverer is a model, in XMI format for instance.

MoDisco

The MoDisco (Model Discovery) component is an Eclipse/GMT component which has been initiated by the ATLAS Team, INRIA. The aim of the GMT project is to produce a set of prototypes in the area of Model Driven Engineering (MDE). The MoDisco project acts in this way by providing a support for model-driven reverse engineering, i.e. principles, methodologies and tooling.

The goal of MoDisco (Model Discovery) is to allow practical extractions of models from legacy systems. Because of the widely different nature and technological heterogeneity of legacy systems, there are several different ways to extract models from such systems. MoDisco proposes a generic and extensible metamodel-driven approach to model discovery. A basic framework and a set of guidelines are provided to the Eclipse contributors to bring their own solutions to discover models in various kinds of legacy.

Due to the highly diversified nature of the considered legacy, MoDisco is a collaborative component involving many organizations. Each of them will bring its own expertise in a given area. A common infrastructure, inspired by the OMG KDM recommendation, will allow integrating all these contributions.

As a GMT component, MoDisco will make good use of other GMT components or solutions available in the Eclipse Modeling Project (EMF, M2M, M2T, GMF, TMF, etc), and more generally of any plugin available in the Eclipse environment.

Follow you can find same MoDisco tools.

MoDisco Tool - KDM-to-UML2 Converter

This tool is about converting KDM models into UML2 models in order to allow integrating KDM-compliant tools (i.e. discoverers) with UML2-compliant tools (e.g. modelers, model transformation tools, code generators, etc).[link]

MoDisco Tool - Jar2UML Discovery Tool

This discovery tool, written by Dennis Wagelaar from the System and Software Engineering Lab (VUB), is about generating UML models from Java APIs. It takes a Jar file as input and generates a UML file (that contains a representation of the API) as output.[link]

MoDisco Tool - Java Abstract Syntax Discovery Tool

This generic tool is about discovering a full abstract syntax tree (AST) of the code (statements, expressions, annotations and Javadoc) taken from a Java compilation unit (typically a Class). It builds models, representing Java compilation units, which conform to a metamodel designed from the Eclipse JDT Java API. [link]

References:

[wikipedia.org]

[http://www.eclipse.org/gmt/modisco]

Cominciamo

Ricordiamo che KDE 4.0 è un package mascherato, in quanto definito instabile e buggato.Per sviare da questo problema possiamo spicciarci subito mettendo nel /etc/make.conf :

ACCEPT_KEYWORDS="~x86" // se avete intel

ACCEPT_KEYWORDS="~am64" // se avete amd

Questa procedura fa si che il portage sbocchi tutti i package ritenuti instabili ovviamente non quelli hard masked [M], rendendoli stabili.

La procedura che ho illustrato precedentemente è sconsigliata al massimo da me e da chi ha un minimo di conoscenza nel campo Gentooniano, dato che rende il sistema altamente instabile.

Se vogliamo fare le cose bene per prima cosa dobbiamo inserire nel /etc/portage/package.keywords e nel /etc/portage/package.unmask i seguenti package
package.keywords
package.unmask

Prima d'installare il tutto controlliamo che dev-libs/xmlrpc-c sia compilato con le seguenti USE curl e libwww, facendo

# emerge -pv xmlrpc-c

[ebuild R ] dev-libs/xmlrpc-c-1.06.09-r2 USE="curl libwww threads" 0 kB

Dato che KDE 4.0 richiede le qt:4.0 compilate con determinate USE noi andiamo ad aggiungere la seguente riga nel /etc/portage/package.use

x11-libs/qt:4 accessibility dbus gif jpeg png qt3support ssl zlib

Fatto questo siamo pronti per compilare il tutto, Gentoo ci permette di poter installare in due modi o monoliticamente o split ebuilds, io consiglio la seconda altrimenti andrete a compilare la miriade di programmi di KDE 4.0 quindi:

split ebuilds

# emerge -avD kde-base/kde-meta:kde-4

monolitico

# emerge -avD kde-base/kdebase-startkde:kde-4

Per farlo partire tramite KDM basterà modificare etc/conf.d/xdm cambiando il tutto in

DISPLAYMANAGER=kdm-4.0

Buona prova

It called The Semantics of Business Vocabulary and Business Rules (SBVR) and if you're a system modeler those words will never leave you the same.

"SBVR specification defines a metamodel and allows to instance it, in order to create different vocabularies and to define the related business rules; it is also possible to complete these models with data suitable to describe a specific organization. the SBVR approach provides means (i.e. mapping rules) to translate natural language artifacts into MOF-compliant artifacts; this allows to exploit all the advantages related to MOF (repository facilities, interchangeability, tools, …).

Several MDA-related OMG works in progress are expected to incorporate SBVR, including:

• Business Process Definition Metamodel (BPDM)
• Organization Structure Metamodel (OSM)
• Business Motivation Model (BMM)
• UML Profile for Production Rule Representation (PRR)
• UML Profile for the Department of Defense Architecture Framework/Ministry of Defense(Canada) Architecture Framework (DoDAF/MODAF).
• Knowledge Discovery Metamodel (KDM)
• Wider interest in SBVR– Semantic Web, OASIS

The Ontology Definition Metamodel (ODM) has been made compatible with SBVR, primarily by aligning the logic grounding of the ISO Common Logic specification (CL) referenced by ODM with the SBVR Logical Formulation of Semantics vocabulary. CL itself was modified specifically so it potentially can include the modal sentence requirements of SBVR. ODM provides a bridge to link SBVR to the Web Ontology Language for Services (OWL-S), Resource Description Framework Schema (RDFS), Unified Modeling Language (UML), Topic Map (TM), Entity Relationship Modeling (ER), Description Logic (DL), and CL.

Other programs outside the OMG are adopting SBVR. The Digital Business Ecosystem (DBE), an integrated project of the European Commission Framework Programme 6, has adopted SBVR as the basis for its Business Modeling Language. The World Wide Web Consortium (W3C) is assessing SBVR for use in the Semantic Web, through the bridge provided by ODM. SBVR will extend the capability of MDA in all these areas."

Here is the PDF of the SVBR Specification

En el caso de usar GDM, vamos al menú Sistema->Administración->Ventana de entrada, o abrimos un terminal y ejecutamos gdm-setup. Nos pedirá la contraseña para entrar. Una vez dentro, vamos a la pestaña Seguridad, marcamos Activar entrada temporizada y seleccionamos nuestro usuario y cerramos.

En el caso de usar KDM, vamos a Menú K->Preferencias o ejecutamos kcontrol en un terminal. Una vez dentro del centro de control, vamos a la sección de Administración del sistema y ahí entramos al Gestor de Acceso. Nos colocamos en la pestaña Comodidad y pulsamos en Modo Administrador para que nos deje hacer cambios. Una vez que ya estamos autenticados marcamos la opción de Activar acceso automático, elegimos nuestro usuario y el tiempo de espera.

Available logos:
debian, fedora, gentoo, kubuntu, slackware, suse, tux, ubuntu

Thumbnail:

Hint:

If your Kubuntu Gutsy won't let you change the login theme this is an alternative way that works:

1. Alt + F2, type in kdesu konqueror and hit Run.
2. Search your way to this path: /usr/share/apps/kdm/themes.
3. Backup the folder Kubuntu by renaming it to for example kubuntubackup.
4. Unzip the theme, name the folder Kubuntu and place it in /usr/share/apps/kdm/themes.

Puede que si andamos utilizando más de un escritorio, tengamos la necesidad de elegir otro DM diferente del que tenemos por defecto. O por que simplemente, estemos probando algun DM experimental (como el del KDE4 en su momento) y necesitemos volver al anterior.

Para hacerlo tenemos que editar un archivito:

sudo pico /etc/X11/default-display-manager

Y dentro del archivo veremos una línea. Esa línea es la que le indíca que gestor de acceso de iniciar junto a X. Si queremos usar KDM lo dejamos así:

/usr/bin/kdm

Y si queremos usar GDM lo dejamos así:

/usr/sbin/gdm

There are a number of nice features, including a ton of connectors (10BaseT, WinModem, USB, serial, parallel, PS/2, PCMCIA). The machine just keeps going, though I have had a few (few!) lockups (normally with Amarok and something else running). With the appropriate tweaks, the KDE desktop can be as polished as any from Red Hat or Novell.

Some of the things I did:

• Replace the shutdown picture with something else; the picture of the dragon was too smarmy.
• Replace the background (of course!) - personalization to the max.
• Switch to the "Macintosh" version of menu layout; it's the most user-friendly.
• Load KDM from ports, then activate and theme it.
• Load a splash screen for the boot loader
• Switch the boot loader to grub then use a splash screen to start it off.
• Configure the special buttons to work.
• Change the KDE menu for something easier to use (such as TastyMenu or KBFX).

When all of these are combined, the environment is very slick and professional. It still wants more than 128M though.

One pet peeve of mine I might mention with regards to menus (such as KMenu or KBFX): menus should respond instantly!! I absolutely despise hiccups and watch cursors because the menu is loading its stuff. It should just pop! into place, not thrash the hard disk. Maybe one day...

What was the best part of this? I learned a ton about themes, X keys, configuring KDM, configuring the boot loader, and using grub. And learning is the best part, right?

Mi sono sempre chiesto come cambiare lo sfondo di default (vedi immagine) di Kubuntu (versione di riferimento 7.10), sfondo che compare prima e dopo il caricamento di un qualsiasi tema di KDM.

Dato che non avevo voglia di trovare sta cosa nell'immenso "centro di controllo" di Kde mi sono messo a cercare sta cazz di immagine.
Bene si chiama kubuntu-wallpaper.png e si trova nella dir /usr/share/wallpapers/.

Non mi sono sforzato granchè, infatti ho solo sovrascritto l'immagine con quella che volevo:

$ sudo mv /usr/share/wallpapers/kubuntu-wallpaper.png /usr/share/wallpapers/kubuntu-wallpaper.png~
$ sudo mv /home/utonto/mia-immagine.png /usr/share/wallpapers/kubuntu-wallpaper.png

This didn't take much work to update to. The basic steps were:

freebsd-update upgrade
freebsd-update install

Then - after a reboot (for kernel updates, I presume) another:

freebsd-update install

Relatively painless, throughout.

Then, continuing my install over the weekend, there were a few niggling things to fix. First off, the buttons up on the top of the keyboard didn't work (no surprise there). Using the xev utility helps to pin down the actual keycodes for these keys, then use the xmodmap tool to add the appropriate actions to the keys. In my case, xev reported that the keys left to right were:

• 163 (info key)
• 142 (home key)
• 154 (search key)
• 143 (mail key)

These can be configured using xmodmap and a .Xmodmap file configured this way:

keycode 163 = Help
keycode 142 = XF86HomePage
keycode 154 = XF86Search
keycode 143 = XF86Mail

The values on the right (Help, XF86HomePage, XF86Search, XF86Mail) show their XFree86 heritage, but apparently do not change for X.org. These are activated by using the command:

xmodmap .Xmodmap

A good place for this line would be in the .xinitrc. However, once this is set, it is still necessary to tie applications to the shortcuts listed. In KDE, this is done in the Keyboard Shortcuts section of the Regional and Accessibility pane in Settings. In this dialog, select the "Command Shortcuts" tab, then the application you desire to use. For example, "Find Files/Folders" could be attached to the shortcut XF86Search. Once the xmodmap has been modified using the command above, then click on the Custom radio button, and click the shortcut button. Press the actual shortcut button to define the shortcut for the application.

Do this for all four buttons, and all will be well.

Then there was the problem of the mouse not being operational when waking up from a suspend. Turns out that the moused(8) daemon is the culprit. Sending a HUP signal to the daemon fixes it, but having to do this all the time is not a desirable outcome. The utility acpiconf(8) describes how it uses /etc/rc.suspend and /etc/rc.resume before and after suspending the system. I placed the command:

pkill -HUP moused

into this script, but I don't yet know if it is truly having the desired effect or if other things are causing failures.

Another thing: the CD player would not play CDs in Amarok. Apparently, this is due to HAL and DBUS not being available. HAL depends on DBUS, so both are necessary. The following packages were needed:

hal-0.5.8.20070909
dbus-1.0.2_2
dbus-glib-0.74
dbus-qt3-0.70_1

I don't know that all the dbus packages are necessary, but I decided not to chance it. Of course, dbus is part of GNOME, but whatever. Once these packages are installed, add the following to the startup configuration in /etc/rc.conf:

hald_enable="YES"
dbus_enable="YES"

Next time the system boots, these daemons will start.

Also, up until this point X.org had to be started using startx as a normal user. However, adding the login screen isn't difficult. Edit the /etc/ttys file. In this file, there will be a line that specifies the command xdm.

Since kdm (the KDE display manager, the login screen) is actually a reworked xdm, switching one for the other is smooth and clean. Replace the xdm setting with /usr/local/bin/kdm (keeping the -nodaemon option) and set the tty to "on" (instead of "off"). Then the next time the system starts (or the ttys file is read) a login screen will activate on ttyv8 (if your file is like mine).

1. Alt + F2, type in kdesu konqueror and hit Run.
2. Search your way to this path: /usr/share/apps/kdm/themes.
3. Backup the folder Kubuntu by renaming it to for example kubuntubackup.
4. Unzip a theme, name the folder Kubuntu and place it in /usr/share/apps/kdm/themes.

Open the KDM Theme Manager and see if the theme is there and selected.