KDE for Testers !!!

Message

rob · #61 Post by **rob** » Fri 11 Nov 2005, 17:32

I couldn't get that file to download from the non-ie link, so i downloaded from the IE one and will now upload to my server where I will share it via HTTP and FTP in a linux compatible (non-crap) way.

Nathan F · #62 Post by **Nathan F** » Fri 11 Nov 2005, 17:50

I couldn't get that file to download from the non-ie link, so i downloaded from the IE one and will now upload to my server where I will share it via HTTP and FTP in a linux compatible (non-crap) way.

You do realize that the file in question makes it Linux compatible anyway as it contains Wine, right? Still, your IE jibes are probably more than welcome here.

That one is way too big for me to host, so I can't help out. In fact I may remove the usr_devx.sfs after a few days, so if anyone wants to take that one off my hands it might not be a bad idea.

Nathan

rob · #63 Post by **rob** » Fri 11 Nov 2005, 19:33

can do

#64 Post by MU » Fri 11 Nov 2005, 20:42

Thanks Rob, the more mirrors, the better.
I wanted to upgrade my own webspace, but the upgrade has a 1 Gigabyte-limit/day. Every additional Gig costs 4 Euro.

So I will set up my own fileserver in the next days.

**edit**
Rob, no need to mirror.
See this message: http://www.murga.org/%7Epuppy/viewtopic.php?t=3645

cool

Mark

nameless foo · #65 Post by **nameless foo** » Fri 11 Nov 2005, 23:53

Looks very good but somehow it disables xmms

PeterSieg · #66 Post by **PeterSieg** » Sat 12 Nov 2005, 11:55

Hi Nathan.

As promised I made a usr_devx.sfs that should be safe to use with KDE. I didn't remove evrything relating to Qt but only what was duplicated, so it should still be possible to compile Qt applications. Get it at:
http://grafpup.com/puppy/
md5 checksum included
Let me know if there's any problems.

I run your usr_devx.sfs with Puppy 1.0.6rc + xorg + kde now on real
PC without seeming to have any problems! Great!!

What have you changed?

PS

Nathan F · #67 Post by **Nathan F** » Sat 12 Nov 2005, 14:55

Peter-

All I did was remove the Qt components from usr_devx.sfs that were in both. Clash should be gone now.

Nathan

Guest · #68 Post by **Guest** » Sun 13 Nov 2005, 12:44

Downloaded & booted up MU's mega .sfs & ran the KDE dotpup, works great but just a few minor teething troubles:

1) After booting up with the mega .sfs attached and running the dotpup, waiting until got the all clear. Went to dotpup menu and ran the KDE panel - it worked but came up with an error message

2) Exited X and did xwin startkde, worked astonishingly fast. got error on boot titled "Fatal Error! - KDE Panel" saying "The KDE panel (kicker) could not load the main panel due to a problem with your installation. " Despite this it still seemed that everything I tried worked...Not seen the error message since.

3) Upon reboot KDE loads fine, but so does ROX-filer - leading to icons piled on top of each other and also puppies icons stay on top of any application window - solved by running KSysGuard and killing ROX-filer but still an annoyance as comes back every boot.

Good work guys!

Chris

bombayrockers · #69 Post by **bombayrockers** » Sun 13 Nov 2005, 14:21

Guest your error occured because you did not reboot your system after installation. After a fresh install if you dont want to reboot you will have to run the /etc/rc.d/rc.local <- this links /root/.opt to /opt

you did neither of this and hence the error occured.

make it a unsaid rule to reboot after installing any software. you never know what system files have changed. i have already posted about rebooting on the first page, but you would not have glanced that when the post has stretched up to the fifth page.

Guest · #70 Post by **Guest** » Sun 13 Nov 2005, 16:53

Cheers for the reply, that makes sense. Afte the reboot it did work ok.

Re: rox starting is there anything to simply comment out in the startup scripts to stop it cleanly? Or perhaps add something in startkde to close rox when starting kde?

What I'm doing now is running KDE panel from Icewm by simply putting 'kicker' in rxvt, this works but comes up with this:

Code: Select all

DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
Link points to "/tmp/ksocket-root"
Link points to "/tmp/kde-root"
kbuildsycoca running...
# kbuildsycoca running...

The first DCOP... takes about 7 seconds to appear is there anything to edit to stop this happening and so speed up kicker appearing?

Cheers

bombayrockers · #71 Post by **bombayrockers** » Sun 13 Nov 2005, 19:06

For Guest,
What puppy version are you using ?
Have you edited / some program replaced /root/.xinitrc file ?

If you are using puppy version < 1.0.4 then I suppose the culprit is the
.xinitrc file.

_________________
Boosted Puppy Kernel (2.4.29) available
Download Here
KDE for testers available
Download Here

bombayrockers · #72 Post by **bombayrockers** » Sun 13 Nov 2005, 19:17

For Guest,

The DCOP Thing ->
1. It cannot be stopped from occuring
2. I think the 'could not open...' occur because you are not successfully connected to the internet using puppy.

_________________
Boosted Puppy Kernel (2.4.29) available
Download Here
KDE for testers available
Download Here

#73 Post by MU » Sun 13 Nov 2005, 23:19

Anonymous wrote: 3) Upon reboot KDE loads fine, but so does ROX-filer - leading to icons piled on top of each other and also puppies icons stay on top of any application window - solved by running KSysGuard and killing ROX-filer but still an annoyance as comes back every boot.

By default, /root/.xinitrc should contain this somewhere before the line that executes ROX:

Code: Select all

CURRENTWM="`cat /etc/windowmanager`"
if [ "$CURRENTWM" = "startkde" ];then
 exec startkde
fi

The "exec" avoids, that all lines after this are executed.
These lines should be there by default in Puppy, mabe modified versions of Puppy do not contain them, then add them with an editor.

Mark

#74 Post by MU » Mon 14 Nov 2005, 00:20

deleted

#75 Post by MU » Mon 14 Nov 2005, 04:14

Kmail just needs an additional library.

Install the attached Dotpup, and it works.
I also add a tar.gz, so that Bombayrockers may add it to KDE.
I found it out like this:
ldd /usr/lib/kde3/kio_pop3.so

I took the Package from Debian.

Mark

Nathan F · #76 Post by **Nathan F** » Mon 14 Nov 2005, 05:24

Mark-
Thanks for finding that. Kmail can now recieve just fine. However-

Code: Select all

Sending failed:
Authorization failed, An error occured during authentication: SASL(-4): no mechanism available: No worthy mechs found authentication not supported
The message will stay in the 'outbox' folder until you either fix the problem (e.g. a broken address) or remove the message from the 'outbox' folder.

This is the error I recieve when sending mail. At least it doesn't completely crash now like it did before.

Nathan

#77 Post by MU » Mon 14 Nov 2005, 05:33

I will have a look at that tomorrow, maybe there is missing another lib.

Mark

#78 Post by MU » Mon 14 Nov 2005, 05:59

ah yes, there were missing some modules.
I updated the dotpup.

Please uninstall the old "libasl2" first, as I renamed this one to the correct name "libsasl2".

Now I can send mails with kmail

Mark

bombayrockers · #79 Post by **bombayrockers** » Mon 14 Nov 2005, 06:16

PerterSieg wrote:

In the KDE from Bombayrockers and Mark are no KOffice apps...

Uploadling now... *edit* .tar.gz

_________________
Boosted Puppy Kernel (2.4.29) available
Download Here

#80 Post by MU » Mon 14 Nov 2005, 06:24

bombayrockers wrote: Uploadling now...

Great. A new usr_more.sfs?
Is it split again?

Mark

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

KDE for Testers !!!

mega puppy download