dropline GNOME 2.24.1 Beta For Slackware 12.1!

[zborgerd]

dropline GNOME 2.24.1 Beta for Slackware 12.1 is here!

http://downloads.sourceforge.net/dropli ... 86-1dl.tgz

Since there are major changes in the latest releases of GNOME, there are still a few tweaks and loose-ends that we need to take care of before we consider this one “stable”. But most of the 2.24.1 desktop is in a rather usable state and may be ready for more technical users that like living on the bleeding edge.

Users that still wish for a stable and fully-tested desktop may still wish to use the stable Dropline GNOME 2.20.3 for Slackware 12.0 for a bit longer.

-The dropline GNOME Development Team

[ertz]

Wooohoooooo!

[salvador]

Good to see people are still alive and kickin'

[b3rx]

I concur! Long live dropline GNOME!

[solarfields]

wheeeeeeeeeeeeeeeeee......!!!!!!!!!

[rscheckelhoff]

Nice Job!

I have the new dropline gnome running on Slackware 12.1 --- horray!

Nice work! It looks very good! I noticed a couple things about the installation procedure that I thought I ought to make mention of ...

I downloaded the Dropline Gnome installer file, executed the dropline-installer, and the various needed files were seemingly downloaded and installed. I subsequently received a "dropline successfully installed" (or similar such) message.

Upon my first attempt to launch a gnome session, gnome bombed with various errors about missing libraries. Based upon the error messages, I reinstalled the following packages:

- policykit-gnome-0.9.2-i686-1dl.tgz
- policykit-0.9-i686-2dl.tgz
- pango-1.22.1-i686-1dl.tgz
- cairo-1.8.0-i686-1dl.tgz
- cairomm-1.4.8-i686-2dl.tgz

The next attempt to launch Dropline Gnome was successful, and like I said, it looks great!

- Ron

[zborgerd]

Policykit is a bit broken right now. It's one of the last serious hangups. You'll find that some stuff (like shutting down the system from GNOME) may not work.

Did all of the packs that you've listed completely fail to install?

[Ridor]

*whew* I was getting ready to go to gnome slackbuild or _gasp_ ubuntu!
Thank you!

[theflockers]

Great!

I'm just compiled Gnome throug GARNOME build, but i'm really happy about dropline, because i'm having millions of problems with PoliciKit and DBUS under GARNOME...
Thanks for this beta!

[MrJackson]

Just installed on a fresh 12.1 system, for some reason it errored out on looking for the firefox plugins dir and dropped back to the main menu, but running the install again worked fine.

[Tuttle]

I had a similar issue with plugins dir.... I just 'mkdir /usr/lib/firefox/plugins' and repeated the install...
Also, the 'twotwenty' theme seems to be missing...

Great Work Guys, much appreciated.

[zborgerd]

I had a similar issue with plugins dir.... I just 'mkdir /usr/lib/firefox/plugins' and repeated the install...
Also, the 'twotwenty' theme seems to be missing...

Great Work Guys, much appreciated.

Which pack fails?

[Tuttle]

Hard to say, I didn't look at the log before restarting the install sorry...
I was excited and forgot to gather the information before proceeding, sack the troubleshooter!

[stik]

I just ran the installer on a fresh slack install and everything went well. I didn't watch the whole install
for any errors but the install itself didn't fail at all.

[Tuttle]

Ok, probably something I'd done then. I have been running 12.1 for a while now using xfce and E17, maybe I made a modification, added/removed some software which somehow removed the plugins dir?

[stik]

Well it seems that 2 people had this issue and one didn't... See how many others have or don't have the
same issue... I do install w/out the kde and xapps dirs... I will try in a vm tomorrow to see if I get the
error with a full blown slack install...

[cheesesteak]

I experienced the same problem as Tuttle. Once the installer exited, I manually created the plugins directory and re-ran dropline-installer. The install then went without a hitch (installed everything).


This was on a full, clean Slackware 12.1 install.

[Tuttle]

FYI: I only downloaded and installed slack disk1

Any extra software requirements I needed I manually installed from my nearest slack mirror: for example, Xorg packages, firefox, thunderbird, pidgin, gftp. All of these are the official slackware 'package.tgz'.

I also use audacity, avidemux2, easytag, gnomad2, mplayer etc. Any deps I have compiled myself:

Code: Select all

Shannon's Observation
   Nothing is so frustrating as a bad situation
   that is beginning to improve.

tuttle@shangrila:~$ ls .compile/
agg-2.5/              foobillard-3.0a/    pacrad_full.vpn
amsn-0.97.2/          glibmm-2.16.4/      plib-1.8.4-supertuxkart/
audacity/             gnomad2-2.9.1/      sunbird/
avidemux_2.4.1/       gparted-0.3.6/      thunar-volman-0.2.0/
dvdrip/               gtkmm-2.12.7/       vlc-0.8.6i/
easytag-2.1/          kernel/             vobcopy-1.1.1/
extremetuxracer-0.4/  libgnashplugin.so*  xfce4-mpc-plugin-0.3.3/
faac/                 libsigc++-2.0.18/   xfmpc-0.0.6/
faad2/                mplayer/
ffmpeg/               ncmpc-0.11.1/

note: although there is a folder called 'kernel' I am using the default smp kernel:

Code: Select all

Theorem: a cat has nine tails.
Proof:
   No cat has eight tails. A cat has one tail more than no cat.
   Therefore, a cat has nine tails.

tuttle@shangrila:~$ uname -a
Linux shangrila 2.6.24.5-smp #2 SMP Wed Apr 30 13:41:38 CDT 2008 i686 Intel(R) Xeon(TM) CPU 3.20GHz GenuineIntel GNU/Linux

[linuxgeek]

The package that seem to fail is the mozilla-firefox package itself. In the doinst.sh script at line 6 the scripts tries to cd usr/lib/firefox/plugins which doesn't exist in the package... and thus the script does exit with code 1

I finally got it installed. A few issues:
* hamster-applet doesnt work.
Try

Code: Select all

( exec /usr/lib/hamster-applet/hamster-applet )

(with brackets) in a terminal window will give you this:

Running installed hamster, using [/usr/lib/python2.5/site-packages/hamster:$PYTHONPATH]
Traceback (most recent call last):
File "/usr/lib/hamster-applet/hamster-applet", line 46, in <module>
import hamster.defs
File "/usr/lib/python2.5/site-packages/hamster/__init__.py", line 33, in <module>
from db import Storage
File "/usr/lib/python2.5/site-packages/hamster/db.py", line 24, in <module>
from pysqlite2 import dbapi2 as sqlite
File "/usr/lib/python2.5/site-packages/pysqlite2/dbapi2.py", line 27, in <module>
from pysqlite2._sqlite import *
ImportError: /usr/lib/python2.5/site-packages/pysqlite2/_sqlite.so: undefined symbol: sqlite3_enable_load_extension

I installed pysqlite from source and that did help... also it seems that the hamster-applet package includes pysqlite.

* Change keyboard layout to german layout doesn't work
I'm using the default xorg.conf from the Slackware install (which is the same as 'xorg.conf-vesa').
System -> Preferences -> Keyboard. Keyboard model i have set to "Generic 105-key" and then tried to add a layout. Country is "Germany" and layout is "Eliminate dead keys". I made this the "default" and turned off the option "Separate layout for each window". The selected keyboard ist still the "US" layout. The keyboard-indicator-applet shows a "?" for the german layout but it doesn't help to switch the layout using the applet.
I changed the settings in my xorg.conf to:

Option "XkbModel" "pc105"
Option "XkbLayout" "de"
Option "XkbVariant" "nodeadkeys"

...and now the keyboard-indicator-applet shows "DEU" as the german keyboard layout and i have the german umlaut keys.

Maybe that will help others to fix keyboard problems.

[slackdavid]

I had to # mkdir /usr/lib/firefox/plugins and everything went fine.
So I can continue using a desktop environment like no other.
A small issue:
I noticed that in System>Preferences there are two screensaver setting voices: the first allows changing preferences for each theme (and writes changes in ~/.xscreensaver), the second - the gnome-screensaver - only allows choosing the theme. The problem is that the gnome-screensaver only reads the global settings in .xsreensaver (for example where to pick up pictures) but ignores individual theme setting, for which i had to edit /usr/share/applications/screensavers/themename.desktop.

[zborgerd]

I had to # mkdir /usr/lib/firefox/plugins and everything went fine.
So I can continue using a desktop environment like no other.
A small issue:
I noticed that in System>Preferences there are two screensaver setting voices: the first allows changing preferences for each theme (and writes changes in ~/.xscreensaver), the second - the gnome-screensaver - only allows choosing the theme. The problem is that the gnome-screensaver only reads the global settings in .xsreensaver (for example where to pick up pictures) but ignores individual theme setting, for which i had to edit /usr/share/applications/screensavers/themename.desktop.

Oneof the entries is probably XScreensaver. We normally patch that out of the menus, but it's probably back again. Gnome-screensaver is the default, and it uses XScreensaver's hacks as a backend.

[barnowl]

The DLG looks good. So far I have only found 2 problems one was with the plugins dir for firefox, rerunning the installer solved that. The second is that sound-juicer fails with "The plugin necessary for file access was not found". I can access the cdrom to play music and mount data discs, so it loks like it is in the sound juicer app.

Other than that it is working pretty good.

[slackdavid]

Hi everyone!
Almost at the end of each boot time I get several lines saying:
"Updating icon-theme.cache in /usr/share/icons/[name]". Is that normal? That came up after installin DLG.
Thank you, good job.

[Diffie]

Hi everyone!
Almost at the end of each boot time I get several lines saying:
"Updating icon-theme.cache in /usr/share/icons/[name]". Is that normal? That came up after installin DLG.
Thank you, good job.

FYI, this has nothing to do with DLG. These get updated by Slackware's rc.M startup script. Enjoy your new desktop!

[linuxgeek]

post by barnowl

I think dropline should have fixed that already... but here is a link to http://bugzilla.gnome.org/show_bug.cgi?id=554961