mkkde: create your custom KDE 3.5.5
-
- Posts: 9
- Joined: Sun 31 Dec 2006, 20:46
I don't mean to kick this topic, but I don't want to crowd up the forum with a separate one.
I recently ran the mkkde script, and everything seemed to go well. I used that last list in the first post for my tgz. I moved the sfs file to "/mnt/home/" and then ran the DotPup file as required. Then I reboot, logged out of XFCE, and ran "startkde" A series of errors popped up, so I went into xfce, opened up a terminal, and tried to run "Kicker" but all it gives are errors. Any help?
Running Puppy 2.12
I recently ran the mkkde script, and everything seemed to go well. I used that last list in the first post for my tgz. I moved the sfs file to "/mnt/home/" and then ran the DotPup file as required. Then I reboot, logged out of XFCE, and ran "startkde" A series of errors popped up, so I went into xfce, opened up a terminal, and tried to run "Kicker" but all it gives are errors. Any help?
Running Puppy 2.12
you must run the dotpup after rebooting, not before.
Maybe you can fix it by installing it again.
If not, try these steps:
Boot WITHOUT the .sfs
Then delete these folders:
/initrd/pup_rw/opt
/initrd/pup_rw/usr/lib/qt
/initrd/pup_rw/usr/local/MU-XDG-activator
Then reboot WITH the .sfs.
Then install the dotpup again.
To say more, please post the errors you get (after these steps):
Run "Kicker" in the consolewindow.
Select the errormessages with the mouse, then middle-click in a forum-message to paste them.
Mark
Maybe you can fix it by installing it again.
If not, try these steps:
Boot WITHOUT the .sfs
Then delete these folders:
/initrd/pup_rw/opt
/initrd/pup_rw/usr/lib/qt
/initrd/pup_rw/usr/local/MU-XDG-activator
Then reboot WITH the .sfs.
Then install the dotpup again.
To say more, please post the errors you get (after these steps):
Run "Kicker" in the consolewindow.
Select the errormessages with the mouse, then middle-click in a forum-message to paste them.
Mark
Thanks, Mark.
This cleared up a problem I was having with KDEmini.
There were some broken symlinks in /usr/lib/qt/lib (to libqt-mt.so and libqt-mt.so.3 in /usr/lib/qt-3.3.6). I also added a symlink to libqt.so. Don't know if the last thing was needed but everything works now.
Best wishes!
This cleared up a problem I was having with KDEmini.
There were some broken symlinks in /usr/lib/qt/lib (to libqt-mt.so and libqt-mt.so.3 in /usr/lib/qt-3.3.6). I also added a symlink to libqt.so. Don't know if the last thing was needed but everything works now.
Best wishes!
If only I could be half as good as my dog thinks I am
- lickthefrog2
- Posts: 57
- Joined: Wed 22 Nov 2006, 18:30
Specifically re: BasKet
So I uninstalled with Gslapt the incorrect gpgme then installed the specific one you described: gpgme-1.0.3-i486-2df
But I'm still getting the error message. The more notes I make the more times the error comes up.
Any advice?
When you say install gpgme with gslapt, that's independent of KDE, right? Meaning, I don't put that package in with the other packages I'm using to customize my miniKDE?
And thanks again. I'm having fun (and only a little frustration) as a now-dedicated Linux user.
- lickthefrog2
Hi Mark,MU wrote: The gpgme-error appears, if you install the wrong gpgme with gslapt.
Be sure to use the version I mentioned above.
I also had tried another one before, and got the same error.
Mark
So I uninstalled with Gslapt the incorrect gpgme then installed the specific one you described: gpgme-1.0.3-i486-2df
But I'm still getting the error message. The more notes I make the more times the error comes up.
Any advice?
When you say install gpgme with gslapt, that's independent of KDE, right? Meaning, I don't put that package in with the other packages I'm using to customize my miniKDE?
And thanks again. I'm having fun (and only a little frustration) as a now-dedicated Linux user.
- lickthefrog2
- lickthefrog2
- Posts: 57
- Joined: Wed 22 Nov 2006, 18:30
No luck. Do I need to reboot after the uninstall before the reinstall?
The initial trouble I had, and why I tried it first with a different gpgme, is because I couldn't see the exact one you specified.
Since it didn't work, I went searching around and realized that I could add a different Gslapt Package Source.
After adding one or two, I then saw the correct gpgme and installed it with Gslapt.
The error message didn't go away, so I uninstalled mkkde and redid it.
Still the same problem.
I saw that gpgme was compiled with pth-2.0.7, so I'm going to try that.
The initial trouble I had, and why I tried it first with a different gpgme, is because I couldn't see the exact one you specified.
Since it didn't work, I went searching around and realized that I could add a different Gslapt Package Source.
After adding one or two, I then saw the correct gpgme and installed it with Gslapt.
The error message didn't go away, so I uninstalled mkkde and redid it.
Still the same problem.
I saw that gpgme was compiled with pth-2.0.7, so I'm going to try that.
- lickthefrog2
- Posts: 57
- Joined: Wed 22 Nov 2006, 18:30
mkkde in Muppy 007
Hi,
I set up my own mkkde in Muppy007 as I am upgrading and starting from a clean slate.
I set up BasKet Note Pads in my KDE on Muppy006 but was getting an error message. Mark, you suggested that I install 4 Slackware packages with gslapt:
attr 2.4.32_1-i486-1
acl 2.2.39_1-i486-1
libgpg-error1.4-i486-1df
gpgme 1.0.3-i486-2df
Whereas in Muppy006, I might have made a mistake with gpgme, this time I didn't.
So I'm thinking there's something else I'm missing. How can I find out?
Everything else is great. Thanks again.
-lickthefrog2
I set up my own mkkde in Muppy007 as I am upgrading and starting from a clean slate.
I set up BasKet Note Pads in my KDE on Muppy006 but was getting an error message. Mark, you suggested that I install 4 Slackware packages with gslapt:
attr 2.4.32_1-i486-1
acl 2.2.39_1-i486-1
libgpg-error1.4-i486-1df
gpgme 1.0.3-i486-2df
Whereas in Muppy006, I might have made a mistake with gpgme, this time I didn't.
So I'm thinking there's something else I'm missing. How can I find out?
Everything else is great. Thanks again.
-lickthefrog2
It moved to a new server.
It is back in some hours, when the DNS servers were updated.
Meanwhile use:
http://puppyfiles.org/dotpupsde/files/
http://puppyfiles.org/dotpupsde/dotpups/
Or this tool:
http://puppyfiles.org/dotpupsdelink.php
Mark
It is back in some hours, when the DNS servers were updated.
Meanwhile use:
http://puppyfiles.org/dotpupsde/files/
http://puppyfiles.org/dotpupsde/dotpups/
Or this tool:
http://puppyfiles.org/dotpupsdelink.php
Mark
If it is a .tar.gz from slakware, you could try to install it with gslapt.
But I think the cleaner way is to add it to the folder with the KDE-.tar.gz files and run mkkde again.
Then it will be added to the new .sfs, and the new dotpup will delete any .wh files in the folders it installs to.
Those .wh files are a bug from unionfs, so if you encounter problems when installing with gslapt, create a new kde.sfs.
Mark
But I think the cleaner way is to add it to the folder with the KDE-.tar.gz files and run mkkde again.
Then it will be added to the new .sfs, and the new dotpup will delete any .wh files in the folders it installs to.
Those .wh files are a bug from unionfs, so if you encounter problems when installing with gslapt, create a new kde.sfs.
Mark
-
- Posts: 42
- Joined: Wed 07 Mar 2007, 01:09
-
- Posts: 42
- Joined: Wed 07 Mar 2007, 01:09
Reading startkde2 I assume if I place a file kdewm.sh in ~/.kde with the contents "export KDEWM=beryl-manager" and make it executable, a new environment variable should be created.
after startup however "terminal>env" does not list KDEWM, furthermore kwin still initializes.
What am I missing?
sincerely,
orbisvicis
after startup however "terminal>env" does not list KDEWM, furthermore kwin still initializes.
What am I missing?
sincerely,
orbisvicis
-
- Posts: 42
- Joined: Wed 07 Mar 2007, 01:09
very nice!
i just stuck "export KDEWM=beryl-manager" into startkde with all the other exports and kwin no longer starts.
Just a note, kde doesnt seem to load anything in .xinitrc
http://murga-linux.com/puppy/viewtopic. ... 831#104831
This helps well
thanks,
orbisvicis
i just stuck "export KDEWM=beryl-manager" into startkde with all the other exports and kwin no longer starts.
Just a note, kde doesnt seem to load anything in .xinitrc
http://murga-linux.com/puppy/viewtopic. ... 831#104831
This helps well
thanks,
orbisvicis
I think .xinitrc has in the beginning somewhere
Or similar.
That was made to avoid, that for example ROX starts with KDE.
It seems it was removed in Puppy 2.14, but 2.11 or 2.12 still had it I think.
So you had to put stuff before that part.
However, using startkde is just fine, too
It might be even better, as with Puppys systemfiles like .xinitrc there is always the risk, that it will be overwritten by an upgrade or so.
Mark
Code: Select all
if [ $CURRENTWM == "startkde" ];then
exec startkde
fi
That was made to avoid, that for example ROX starts with KDE.
It seems it was removed in Puppy 2.14, but 2.11 or 2.12 still had it I think.
So you had to put stuff before that part.
However, using startkde is just fine, too
It might be even better, as with Puppys systemfiles like .xinitrc there is always the risk, that it will be overwritten by an upgrade or so.
Mark