From The Chakra Project - Wiki

Contents 1 Error: Could not start kstartupconfig4. Check your installation. 2 KDM rejects login / KDE doesnt start up but sends you back to KDM 3 KDM doesn't restart on logout but just send you to a black screen 4 Newly installed Applications/Plasmoids don't show in KDE 5 System monitor plasmoids are not working after upgrade 6 Strigi service failed to initialize, most likely due to an installation problem 7 broadcom-wl blocks a system update 8 Tribe can't create partition tables

Error: Could not start kstartupconfig4. Check your installation.

If you experience this error while trying to login via KDM, try the following advices:

• Verify that KDE starts via startx (uncomment the exec startkde entry in ~/.xinintrc)
• Verify that you have installed the correct packages for your architecture (i686 = 32Bit, x86_64 = 64Bit)
• Maybe the permissions of /tmp and /var/tmp are not correct, try the following:

  sudo chmod 1777 /tmp /var/tmp

• It could be that some permission in your home directory are broken, try to fix them with:

  sudo chown -R YOUR_USERNAME:YOUR_GROUP ~

• Try a fresh configuration. Move ~/.kde4, ~/.kdemod4, ~/.config and ~/.local to another place or delete it, then try again.
• Also try to create a fresh user and try to login with it.
• It could be that your KDE paths are messed up somehow. Check /etc/profile.d if there are any KDE-related files and delete them (they are not needed anymore since KDE is in /usr). Also check the contents of the files in /etc/profile.d if there are any KDE-related entries. Reboot after doing these changes.

This is a configuration issue. Experiments have shown that a reinstallation of the Arch Linux system always solves this problem. So far, not all reasons for this problem have been identified, but it IS a configuration issue.

KDM rejects login / KDE doesnt start up but sends you back to KDM

• You need to have the hal daemon in the DAEMONS array in /etc/rc.conf.
• Don't start hal backgrounded.
• Maybe you are experiencing this bug. Running these commands could solve it:

  sudo groupadd -g 81 dbus

  sudo useradd -u 81 -G dbus -d '/' -s /bin/false dbus

KDM doesn't restart on logout but just send you to a black screen

This is most probably a graphics driver issue. To solve it, uncomment and/or set the following line in /usr/share/config/kdm/kdmrc:

TerminateServer=true

Newly installed Applications/Plasmoids don't show in KDE

Run:

kbuildsycoca4

System monitor plasmoids are not working after upgrade

If system monitor plasmoids are not working (and no devices in settings) try rebooting computer.

Strigi service failed to initialize, most likely due to an installation problem

You need a java runtime environment for soprano, either jre or openjdk. The default (which works out of the box) is openjdk.

• To use openjdk:

  pacman -S openjdk6

• To use jre:

  pacman -Rd openjdk6 (if installed)

  pacman -S jre

  then add /opt/java/jre/lib/i386/server/ to your /etc/ld.so.conf and run ldconfig.

broadcom-wl blocks a system update

Whenever a new kernel version is available, the wireless driver for Broadcom cards, broadcom-wl, needs to be recompiled against this new kernel. This driver is not available in the regular repositories, but is available in AUR and in the Chakra repo for LiveCD's.

The error message looks like this:

:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: broadcom-wl: requires kernel26<2.6.3....

If you don't have a Broadcom wireless card in your system, you can safely remove:

sudo pacman -Rd broadcom-wl

If you do have any of these cards, remove this driver with the command above, and update your system. Before restarting, download the latest version from AUR.

Tribe can't create partition tables

Tribe can't create partition tables yet. So you have to use another program to do it. You can use either parted or fdisk to do that. If you get asked for a password use live.

Press the F12 in Phoix LiveCD to open the terminal (yakuake). Now follow the instructions for each program. I recommend parted.

parted

[live@chakra ~]$ sudo parted /dev/sda mktable msdos

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

Password: live
Warning: The existing disk label on /dev/sda will be destroyed and all data on this disk will be lost. Do you want to
continue?
Yes/No? yes
Information: You may need to update /etc/fstab.                           

[live@chakra ~]$

fdisk

[live@chakra ~]$ sudo fdisk /dev/sda

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

Password: live
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x2ed56051.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
         switch off the mode (command 'c') and change display units to
         sectors (command 'u').

Command (m for help): c
DOS Compatibility flag is not set

Command (m for help): u
Changing display/entry units to sectors

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.