Edgy with Beryl & Kiba-dock

Screenie of my desktop

The next shot show my interface in Cube format as I switch from one desktop to another.

Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”

sudo apt-get install gtk2-engines-pixbuf
^^^^^^^^^^^^^^^^^^^^^
You want to do this.

If running kiba-dock from command line you may notice you’re getting a Gtk warning where it complains of its inability to locate the theme engine module_path pixmap - as seen below.

macewan@moc:~$ kiba-dock

(kiba-dock:21995): Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”,
** Message: Cant copy /usr/share/applications/gnome-file-roller.desktop to /home/macewan/.kiba-dock/gnome-file-roller.desktop

** Message: Cant copy /usr/share/applications/epiphany.desktop to /home/macewan/.kiba-dock/epiphany.desktop

macewan@moc:~$ sudo apt-get install gtk2-engines-pixbuf
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following NEW packages will be installed:
gtk2-engines-pixbuf
0 upgraded, 1 newly installed, 0 to remove and 21 not upgraded.
Need to get 148kB of archives.
After unpacking 246kB of additional disk space will be used.
Get:1 us.archive.ubuntu.com edgy/universe gtk2-engines-pixbuf 2.10.6-0ubuntu1 [148kB]
Fetched 148kB in 0s (176kB/s)
Selecting previously deselected package gtk2-engines-pixbuf.
(Reading database … 120211 files and directories currently installed.)
Unpacking gtk2-engines-pixbuf (from …/gtk2-engines-pixbuf_2.10.6-0ubuntu1_i386.deb) …
Setting up gtk2-engines-pixbuf (2.10.6-0ubuntu1) …
macewan@moc:~$ kiba-dock
** Message: Cant copy /usr/share/applications/gnome-file-roller.desktop to /home/macewan/.kiba-dock/gnome-file-roller.desktop

** Message: Cant copy /usr/share/applications/epiphany.desktop to /home/macewan/.kiba-dock/epiphany.desktop

*note: the solution to the *.desktop errors should be obvious enough

*note: this work is taking place on the Edgy flavor of Ubuntu

Tags: kiba-dock, theme, engine, module_path, pixmap

cat /var/log/Xorg.0.log|grep -i aiglx

*reminder
macewan@moc:~$ cat /var/log/Xorg.0.log|grep -i aiglx
(==) AIGLX enabled
(WW) AIGLX: 3D driver claims to not support visual 0×23
(WW) AIGLX: 3D driver claims to not support visual 0×24
(WW) AIGLX: 3D driver claims to not support visual 0×25
(WW) AIGLX: 3D driver claims to not support visual 0×26
(WW) AIGLX: 3D driver claims to not support visual 0×27
(WW) AIGLX: 3D driver claims to not support visual 0×28
(WW) AIGLX: 3D driver claims to not support visual 0×29
(WW) AIGLX: 3D driver claims to not support visual 0×2a
(WW) AIGLX: 3D driver claims to not support visual 0×2b
(WW) AIGLX: 3D driver claims to not support visual 0×2c
(WW) AIGLX: 3D driver claims to not support visual 0×2d
(WW) AIGLX: 3D driver claims to not support visual 0×2e
(WW) AIGLX: 3D driver claims to not support visual 0×2f
(WW) AIGLX: 3D driver claims to not support visual 0×30
(WW) AIGLX: 3D driver claims to not support visual 0×31
(WW) AIGLX: 3D driver claims to not support visual 0×32
(II) AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so
(WW) AIGLX: 3D driver claims to not support visual 0×23
(WW) AIGLX: 3D driver claims to not support visual 0×24
(WW) AIGLX: 3D driver claims to not support visual 0×25
(WW) AIGLX: 3D driver claims to not support visual 0×26
(WW) AIGLX: 3D driver claims to not support visual 0×27
(WW) AIGLX: 3D driver claims to not support visual 0×28
(WW) AIGLX: 3D driver claims to not support visual 0×29
(WW) AIGLX: 3D driver claims to not support visual 0×2a
(WW) AIGLX: 3D driver claims to not support visual 0×2b
(WW) AIGLX: 3D driver claims to not support visual 0×2c
(WW) AIGLX: 3D driver claims to not support visual 0×2d
(WW) AIGLX: 3D driver claims to not support visual 0×2e
(WW) AIGLX: 3D driver claims to not support visual 0×2f
(WW) AIGLX: 3D driver claims to not support visual 0×30
(WW) AIGLX: 3D driver claims to not support visual 0×31
(WW) AIGLX: 3D driver claims to not support visual 0×32
(II) AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so
macewan@moc:~$

gset-kiba not working?

get rid of your config, then recreate it
here is how:
first, unset the gconf settings like so:

gconftool-2 –recursive-unset /apps/kiba/options

then install the new settings like so:

gconftool-2 –install-schema-file=/etc/gconf/schemas/kiba.schemas

via: beryl/kiba-dock discussion

Tags: kiba-dock

kwik kat

hats off to Mifki for hacking Leopard!