Only some days left for new KDE release
http://techbase.kde.org/Schedules/KDE4/ ... e_Schedule
Where is the Salix KDE / Salix KDE SC release?
- damNageHack
- Posts: 663
- Joined: 24. Sep 2009, 17:07
Where is the Salix KDE / Salix KDE SC release?
This is the oppinion of the author, it does not force you to share and is signed automatically.
You are free to keep them all errors for your own. Linux is the best game I ever played.
- damNageHack
- Posts: 663
- Joined: 24. Sep 2009, 17:07
Re: Where is the Salix KDE / Salix KDE SC release?
I copied kde.desktop according to the wiki howto. Alternatively, selection of openbox-kde.
Also needed: slapt-get -i xmessage
But that explains a lot
removepkg gdm results in no window manager available any more.xauth: creating new authority file /root/.serverauth.1859
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Slackware 13.1 Slackware Linux Project
Current Operating System: Linux vbox-salix-lxde 2.6.33.4-smp #2 SMP Wed May 12 22:47:36 CDT 2010 i686
Kernel command line: auto BOOT_IMAGE=Linux ro root=801 quiet vt.default_utf8=1
Build Date: 05 May 2010 01:54:53AM
Current version of pixman: 0.16.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Aug 8 01:50:54 2010
(==) Using default built-in configuration (30 lines)
(EE) Failed to load module "fbdev" (module does not exist, 0)
OpenGL Warning: Failed to connect to host. Make sure 3D acceleration is enabled for this VM.
(EE) AIGLX error: Calling driver entry point failed
(EE) AIGLX: reverting to software rendering
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(EE) VirtualBox USB Tablet: failed to initialize for relative axes.
/usr/bin/kde4-config: error while loading shared libraries: libQtDBus.so.4: cannot open shared object file: No such file or directory
kstartupconfig4: error while loading shared libraries: libQtDBus.so.4: cannot open shared object file: No such file or directory
Warning: Missing charsets in String to FontSet conversion
waiting for X server to shut down
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80a1e6b]
1: /usr/bin/X (0x8048000+0x57b75) [0x809fb75]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]
3: /usr/bin/X (0x8048000+0x39bf0) [0x8081bf0]
4: /usr/bin/X (0x8048000+0x1b3b5) [0x80633b5]
5: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb73eab86]
6: /usr/bin/X (0x8048000+0x1afa1) [0x8062fa1]
Segmentation fault at address 0x1
Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
... fixed with "slapt-get -i ConsoleKit"./usr/bin/kdm: error while loading shared libraries: libck-connector.so.0: cannot open shared object file: No such file or directory
(lots more of this messages)
INIT: Id "x1" respawning too fast: disabled for 5 minutes
Also needed: slapt-get -i xmessage
But that explains a lot
alien wrote:You will need to run Slackware-current dated July 18th 2010 or newer.
These packages will probably not work on Slackware 13.1 so if you want KDE 4.5
you are encouraged to upgrade to Slackware-current!
There are two dependencies (i.e. non-KDE and-or non Slackware packages) which
need to be upgraded this time. They are soprano (which is a version update to
the default Slackware package) and libdbusmenu-qt (which does not yet exist in
Slackware). You'll find those in the 'deps' directory.
This set of KDE SC 4.4.95 (aka 4.5-rc3) packages can be installed on Slackware
-current, replacing the older version of KDE which came with Slackware.
This is the oppinion of the author, it does not force you to share and is signed automatically.
You are free to keep them all errors for your own. Linux is the best game I ever played.
Re: Where is the Salix KDE / Salix KDE SC release?
This is why you always should "RTFM"...
- damNageHack
- Posts: 663
- Joined: 24. Sep 2009, 17:07
Re: Where is the Salix KDE / Salix KDE SC release?
Repository for slackware current, where is it? I remember there was recently a slackware-current folder on the mirrors, why is it gone away
This is the oppinion of the author, it does not force you to share and is signed automatically.
You are free to keep them all errors for your own. Linux is the best game I ever played.
Re: Where is the Salix KDE / Salix KDE SC release?
We don't have a Salix current yet and so we don't have a Slackware current mirror, too. You have to use some original Slackware mirror.
- damNageHack
- Posts: 663
- Joined: 24. Sep 2009, 17:07
Re: Where is the Salix KDE / Salix KDE SC release?
I will try with
ftp://ftp.slackware.no/linux/ISO-images ... ISO-build/
... or http://www.slackware.com/~alien/tools/m ... current.sh
EDIT:
Interesting ...
http://alien.slackbook.org/blog/fiddlin ... -4-5-beta/
Ergo: We need QT 4.7 (not officially released yet, need to use some excerpt from the developer sources )
UPDATE:
Those dependencies are needed to get kde starting with Salix 13.1.1:
http://alien.slackbook.org/ktown/4.4.5/x86/deps/
http://alien.slackbook.org/kdesc/4.5.0/x86/deps/
Yes... both links are important!
Some packages are already available in Salix' repository in a very older version, but it is suggested to take the current ones - i have tested it.
- additionally to those from AlienBOB:
xmessage
strigi (libstreamanalyzer.so)
qca (libqca.so.2)
And last but not least the main packages:
http://alien.slackbook.org/kdesc/4.5.0/x86/kde/
Finally, follow the guide "Starting KDE " on
http://www.salixos.org/wiki/index.php/H ... tall_KDE_4
Should work. Have fun!
ftp://ftp.slackware.no/linux/ISO-images ... ISO-build/
... or http://www.slackware.com/~alien/tools/m ... current.sh
EDIT:
Interesting ...
http://alien.slackbook.org/blog/fiddlin ... -4-5-beta/
Ergo: We need QT 4.7 (not officially released yet, need to use some excerpt from the developer sources )
UPDATE:
Those dependencies are needed to get kde starting with Salix 13.1.1:
http://alien.slackbook.org/ktown/4.4.5/x86/deps/
http://alien.slackbook.org/kdesc/4.5.0/x86/deps/
Yes... both links are important!
Some packages are already available in Salix' repository in a very older version, but it is suggested to take the current ones - i have tested it.
- additionally to those from AlienBOB:
xmessage
strigi (libstreamanalyzer.so)
qca (libqca.so.2)
And last but not least the main packages:
http://alien.slackbook.org/kdesc/4.5.0/x86/kde/
Finally, follow the guide "Starting KDE " on
http://www.salixos.org/wiki/index.php/H ... tall_KDE_4
Should work. Have fun!
This is the oppinion of the author, it does not force you to share and is signed automatically.
You are free to keep them all errors for your own. Linux is the best game I ever played.