LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 10-28-2010, 08:56 AM   #46
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 826

Rep: Reputation: 106Reputation: 106

Quote:
Originally Posted by statguy View Post
I ran "find /usr /etc -name \*kd\*.new" to find them all. FYI, the kdmrc.new (and backgroundrc.new) was in /etc/kde/kdm

Once I moved the .new files into their proper names, I had a working KDE.

Nice find!
You can quickly find *.new files using slackpkg. I can't remember the argument to pass at the moment though. One thing though is that slackpkg did not find /usr/bin/startkde.new as I don't think it looks through /usr/bin.

I'm glad to hear that this worked!! Now, my next project is to find a way to get this going on Slackware 13 and beyond.

Woodsman, I'll be happy to lend you a hand on this project. Time dependent of course.
 
Old 10-28-2010, 08:58 AM   #47
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 826

Rep: Reputation: 106Reputation: 106
Quote:
Originally Posted by statguy View Post
I've noticed one strange thing. If I try to start a root session in Konsole, it rejects my password. I can still use su to become root with no trouble. I normally use sudo, but haven't set it up on the virtual machine.
Will try this when I get home.
 
Old 10-28-2010, 10:05 AM   #48
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 826

Rep: Reputation: 106Reputation: 106
Ok, everything is working much better now! KDM (which looks really good by the way) is working correctly. I had to change the "Welcome to Kubuntu"to "Welcome to Slackware". There are still a few quirks though. I'm getting a double Trash can icon on the desktop. Also, wicd is being loaded twice. That leads me to believe that something is being sourced more than once. Will take a look at this later though. Time to get some rest!

Will continue to post things as I find them. Anybody else, feel free to post your findings also.
 
Old 10-28-2010, 11:32 AM   #49
igadoter
Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: slack 12.2, debian-Trinity , openbsd
Posts: 729

Rep: Reputation: 56
To look for *.new files you may pass through all packages into /var/log/packages.
 
Old 10-28-2010, 03:21 PM   #50
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 826

Rep: Reputation: 106Reputation: 106
igadoter,

Ah, yes, that would also work. Also, running slackpkg new-config would just about catch most *.new files.

I noticed another quirk. Building knemo works, but no binary is created, as in, nothing is created in /usr/bin. I'm not entirely sure why it does that, although I thought that knemo was a qt4 application only.
 
Old 10-28-2010, 03:27 PM   #51
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,297

Rep: Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722
Quote:
Originally Posted by igadoter View Post
To look for *.new files you may pass through all packages into /var/log/packages.
That'll get a lot of false positives unless you do something like
Code:
grep -h [.]new$ /var/log/packages/* | sed 's|^|/|' | while read line; do ls "$line" 2>/dev/null; done
Unless a package is setup very weirdly that should catch everything (and it'll do it much faster than using find in /).
 
1 members found this post helpful.
Old 10-28-2010, 09:00 PM   #52
statguy
Member
 
Registered: Sep 2004
Location: Ontario, Canada
Distribution: Slackware 14.1, 13.37
Posts: 332

Rep: Reputation: 31
I solved the root shell in console problem. I guess it's using sudo. Once I added my user to the sudoer file and entered my user password instead of the root password, the root shell worked.

Now I have a couple other questions that, hopefully, Woodsman can answer next time he can check the thread.

In his README file he mentions that the packages were built with hooks for various things like libdvdcss, for example. Will the programs take advantage of that if it is already installed, or does one need to rebuild and reinstall such packages?

I also notice packages libcaldav and libical and was wondering if these permit access to Google calendars. If so, how? I saw no new korganiser resources that looked appropriate. If not, I'm hoping opensync works. On 3.5.10, it is not handling timezones correctly.

I'm nearly ready to take the plunge on my live system.
 
Old 10-28-2010, 11:57 PM   #53
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 826

Rep: Reputation: 106Reputation: 106
Ok, I was able to build dbus-qt3 on a Virtual 13.1 64 bit. All of these had to be built in order as described in Woodsman's Page:

Code:
qt-3.3.b
qca-1
qca-tls
poppler
dbus-qt3
dbus-python
arts
If everything goes well, I should be able to have packages build for Slackware 13.1 64 bit. This install will be along side KDE4 which is what I really want to test. I should be able to build 32-bit packages if everything goes well.
 
Old 10-29-2010, 12:57 AM   #54
igadoter
Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: slack 12.2, debian-Trinity , openbsd
Posts: 729

Rep: Reputation: 56
@stormtracknole
Big news. Thank's.
 
Old 10-29-2010, 01:03 AM   #55
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 826

Rep: Reputation: 106Reputation: 106
Well crap! Arts is refusing to build. Here's the error code:
Code:
g++: ../mcop/.libs/libmcop.so: No such file or directory
make[2]: *** [mcopidl] Error 1
make[2]: Leaving directory `/tmp/KDE/dependencies/arts/mcopidl'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/KDE/dependencies/arts'
make: *** [all] Error 2
Any ideas?

Hmmm...there is a patch provided on the arts source directory. I have to figure it though how to incorporate this patch into the SlackBuild.

Last edited by stormtracknole; 10-29-2010 at 01:06 AM.
 
Old 10-29-2010, 01:29 AM   #56
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 826

Rep: Reputation: 106Reputation: 106
Here's the arts.tmpdir.diff.gz patch:
Code:
--- ./mcop/mcoputils.cc.orig    2006-01-19 10:16:08.000000000 -0600
+++ ./mcop/mcoputils.cc 2006-09-19 17:07:50.000000000 -0500
@@ -47,7 +47,13 @@
   result = lstat(tmp_dir, &stat_buf);
   if ((result == -1) && (errno == ENOENT))
   {
-    return 1;
+    result = mkdir(tmp_dir, 0700);
+    if (result == -1)
+    {
+       arts_warning("Error: Can not create directory \"%s\".\n", tmp_dir);
+       return 1;
+    }
+    result = stat(tmp_dir, &stat_buf);
   }
   if ((result == -1) || (!S_ISDIR(stat_buf.st_mode)))
   {
I'm beat right now! I don't have as much experience patching files, so someone will have to lend me a hand here.
 
Old 10-29-2010, 07:17 PM   #57
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 826

Rep: Reputation: 106Reputation: 106
Well, after trying, and trying, I couldn't get arts to build in Slackware 13.1. It may build on 13.0, but I don't have it installed in Virtualbox at the moment. As it stands, it appears that installing TDE on 13.1 or beyond is a no go. I may try later using SVN instead.
 
Old 10-30-2010, 12:51 PM   #58
alekow
Member
 
Registered: Sep 2009
Distribution: Slackware
Posts: 127

Rep: Reputation: 17
I've just passed through building whole kde-3.5.10 on slackware 13.1. Arts compiled fine with just a single patch - exactly the same as the one above.
 
Old 10-30-2010, 03:53 PM   #59
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Original Poster
Rep: Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534
Hi folks,

I updated my web page with a warning not to use upgradepkg to install Trinity with KDE 3.5.10 installed.

There are two Trinity list groups that might help: one for developers and one for users. As my schedule right now is horrible for any meaningful support, please consider joining one or both groups. The links are available at the Trinity web site.

A note for those having problems: The pre-built Trinity 3.5.12 packages install in /usr and not /opt. Because the pre-built packages thus far available are intended only for 12.2, that should not pose problems as long as all remnants of KDE 3.5.10 are removed. Installing those same packages in 13.0 or later will cause problems. The solution is to rebuild the packages and ensure the build scripts build for installing in /opt.

Removing the remnants of KDE 3.5.10 include the following:

arts
kdeaccessibility
kdeaddons
kdeadmin
kdeartwork
kdebase
kdebindings
kdeedu
kdegames
kdegraphics
kdelibs
kdemultimedia
kdenetwork
kdepim
kdesdk
kdetoys
kdeutils
kdevelop
kdewebdev
k3b
ktorrent
knemo
koffice
amarok

Also:
k9copy
kaffeine
ksystemlog
etc.

The following 12.2 packaged do not have to be removed or rebuilt:

dbus-qt3-0.70
poppler*
qca-1.0-i486-4
qca-tls-1.0-i486-6
qt-3.3.8b-i486-2

Please add to these lists if I missed anything.

Please note I have not tested the build process on post 12.2 systems. I designed my build scripts to accommodate installations in either /usr or /opt, but there easily might be some bugs in that process. I also have not tested the build scripts for building foundation packages in post 12.2 systems, such as qt3, dbus, etc. My scripts at this point check for the packages being installed, but do not yet have any robust testing for ensuring those foundation packages are installed correctly and won't conflict with other expected stock packages such as qt4.

The build scripts support building Trinity 3.5.12 in 12.2 using /opt rather than /usr, which would allow both KDE 3.5.10 and Trinity 3.5.12 to be installed concurrently. Check the build scripts documentation for overriding the defaults.

I have experienced no problems using my existing ~/.kde profile when testing Trinity.

Regarding the empty K-menu problems. I'll take a wild guess the solution has already been alluded to in this thread. That is, the /etc/profile.d/kde.sh script is installed as a *.new file. Without that file being sourced correctly, the startup sequence will not find the correct xdg paths for the menus.

I built the kdebase package using *.new files because in the past I always was frustrated with the stock Slackware overwriting my customizations of those related files. My kdebase build script has a related comment about that. The script can be modified, of course. The following files are built and installed as *.new files:

/etc/X11/xinit/xinitrc.kde.new
/etc/profile.d/kde.sh.new
/etc/profile.d/kde.csh.new
usr/bin/startkde.new

Anyone who never customizes these files can simply move/rename the *.new files and be done.

Lastly, this project is a community project. Feel welcome to improve the build scripts. I will post changes and improvements at my web site.

Last edited by Woodsman; 10-31-2010 at 11:38 AM.
 
Old 10-30-2010, 03:53 PM   #60
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 826

Rep: Reputation: 106Reputation: 106
Quote:
Originally Posted by alekow View Post
I've just passed through building whole kde-3.5.10 on slackware 13.1. Arts compiled fine with just a single patch - exactly the same as the one above.
A couple of questions, did you install 3.5.10 or 3.5.12? Also, did you install it along side KDE4? I'm trying to figure out if I'm doing something wrong.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Trinity KDE: KDE 3 Zombified or Resurrected? LXer Syndicated Linux News 0 06-30-2010 08:12 PM
LXer: A toolbar trinity LXer Syndicated Linux News 1 02-11-2008 01:28 PM
Firestarter says linuxquestions.org has trinity? clausawits Linux - Security 7 01-18-2004 12:01 AM
Trinity service. JMC Linux - General 6 05-20-2002 12:50 AM
TRINITY or BUFFY? abndaddy00 General 7 02-02-2001 05:42 PM


All times are GMT -5. The time now is 06:38 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration