KDE for Testers !!!
- bombayrockers
- Posts: 427
- Joined: Sat 24 Sep 2005, 16:47
- Location: Mumbai, India
- Contact:
KDE for Testers !!!
Follow this link
http://www.murga.org/~puppy/viewtopic.php?t=5149
http://www.murga.org/~puppy/viewtopic.php?t=5149
Last edited by bombayrockers on Sat 07 Jan 2006, 16:29, edited 4 times in total.
- bombayrockers
- Posts: 427
- Joined: Sat 24 Sep 2005, 16:47
- Location: Mumbai, India
- Contact:
some of the usr files got appended with 4 digit random numbers. please remove them before using unsplit.
I edited my .xinitrc as follows
replaced exec startkde with exec xterm
on xwin startkde it starts X with an xterm. in the terminal type startkde. this way i was able to listen to the backgroud messages.
Known issues at present
1. splash screen
2. mplayer is not included - install this yourself
3. in the sound system setting in control panel - when I click on test sound I get sound output loud and clear however for ?? reasons kde apps & system notification do not generate sound.
4. however multimedia apps are working (juk, noatun, kscd..)
5. when kde tries t automount the cd-rom, it starts the pmount script. on mounting the cd-rom the output goes to rox.
I edited my .xinitrc as follows
replaced exec startkde with exec xterm
on xwin startkde it starts X with an xterm. in the terminal type startkde. this way i was able to listen to the backgroud messages.
Known issues at present
1. splash screen
2. mplayer is not included - install this yourself
3. in the sound system setting in control panel - when I click on test sound I get sound output loud and clear however for ?? reasons kde apps & system notification do not generate sound.
4. however multimedia apps are working (juk, noatun, kscd..)
5. when kde tries t automount the cd-rom, it starts the pmount script. on mounting the cd-rom the output goes to rox.
Cool. Screenshot:
http://noforum.de/dotpups/kde01.jpg
Unfortunately on Puppy 1.0.6, it just works with a new pup001.
When I use a old one converted from 1.0.5 with xorg, I get strange messages, and X will not start. The console does not work either.
If I remove usr_more.sfs , Puppy works again.
Will have to dig in deeper in the next days.
First thing I installed additionally, was my wxb_menue, to get access to all Puppy-Menue-entries:
http://www.murga.org/~puppy/viewtopic.php?t=1985
Good work!
Mark
PS. I'm uploading usr_more.sfs as 1 large file.
May host that for some days only.
Here it is (53,6 MB): http://noforum.de/dotpups/kde-01/usr_more.sfs
http://noforum.de/dotpups/kde01.jpg
Unfortunately on Puppy 1.0.6, it just works with a new pup001.
When I use a old one converted from 1.0.5 with xorg, I get strange messages, and X will not start. The console does not work either.
If I remove usr_more.sfs , Puppy works again.
Will have to dig in deeper in the next days.
First thing I installed additionally, was my wxb_menue, to get access to all Puppy-Menue-entries:
http://www.murga.org/~puppy/viewtopic.php?t=1985
Good work!
Mark
PS. I'm uploading usr_more.sfs as 1 large file.
May host that for some days only.
Here it is (53,6 MB): http://noforum.de/dotpups/kde-01/usr_more.sfs
Ok, I've made up my own usr_more.sfs.
It is identical to yours, just without /usr/X11R6/lib.
Now Puppy boots.
But when I type "konqueror" or "startkde", nothing happens.
With konqueror, the rxvt does not react any more (CTRL-C not possible).
I tried to comment some lines in startkde, but no effect.
It is quite confusing, that there are no error-messages visible.
Mark
It is identical to yours, just without /usr/X11R6/lib.
Now Puppy boots.
But when I type "konqueror" or "startkde", nothing happens.
With konqueror, the rxvt does not react any more (CTRL-C not possible).
I tried to comment some lines in startkde, but no effect.
It is quite confusing, that there are no error-messages visible.
Mark
- klhrevolutionist
- Posts: 1121
- Joined: Wed 08 Jun 2005, 10:09
hard drive
I am on a hard drive install, and have got qt properly installed & all the other
requirements. But upon rebooting to let the usr_more.sfs take effect to use
kde I have to press ctrl+alt+delete to reboot. There are errors, and I will post them as soon as the show I'm listening to is over.
requirements. But upon rebooting to let the usr_more.sfs take effect to use
kde I have to press ctrl+alt+delete to reboot. There are errors, and I will post them as soon as the show I'm listening to is over.
Heaven is on the way, until then let's get the truth out!
- klhrevolutionist
- Posts: 1121
- Joined: Wed 08 Jun 2005, 10:09
agh!
Well I thought MU had included the FILESYSTEM.tgz with his user_more.sfs, but he did'nt. So after installing that I got no errors.
But upon booting into puppy and remind you I'm on a hard drive install
there was no background no menu bar and the mouse cursor was a spinning clock. I think that you might be using Xorg ? And after looking at some files it does'nt look like people on a hard drive install should be using this unless they back up files befor edoing so.
So give some feedback about requirements bombay, such as Xorg and pupfile,
what version of puppy preferably.
But upon booting into puppy and remind you I'm on a hard drive install
there was no background no menu bar and the mouse cursor was a spinning clock. I think that you might be using Xorg ? And after looking at some files it does'nt look like people on a hard drive install should be using this unless they back up files befor edoing so.
So give some feedback about requirements bombay, such as Xorg and pupfile,
what version of puppy preferably.
Heaven is on the way, until then let's get the truth out!
- Nathan F
- Posts: 1764
- Joined: Wed 08 Jun 2005, 14:45
- Location: Wadsworth, OH (occasionally home)
- Contact:
So far so good. I'm posting this using Konqueror and everything seems a little snappier than KDE has ever been for me. It would be nice to have a fully configured menu right from the start but I'm sure it can be fixed easily.
I made the filesystem tarball into an unleashed package so that the installation can be tracked. I'll have to see if removing it breaks anything before I let anyone else use it.
I think that with a little bit of extra configuration this could be a winner. I've encountered no problems so far. I'll play with it for a while and see if that holds.
Nathan
I made the filesystem tarball into an unleashed package so that the installation can be tracked. I'll have to see if removing it breaks anything before I let anyone else use it.
I think that with a little bit of extra configuration this could be a winner. I've encountered no problems so far. I'll play with it for a while and see if that holds.
Nathan
I haven't tried the KDE, I was in an all day event today, I just got home.
But...
I am 98.3 % positive that if you install my puppy-xdgmenus.pup you will be able to get the puppy menu as KDE uses XDG.
I am not sure but I think that you will need to copy the menu file form
/usr/etc/xdg/menus/puppy.menu
to
/usr/etc/xdg/menus/applications.menu
or
/etc/xdg/menus/applications.menu
I will try later today or tomorrow but it would be great if someone tries first.
But...
I am 98.3 % positive that if you install my puppy-xdgmenus.pup you will be able to get the puppy menu as KDE uses XDG.
I am not sure but I think that you will need to copy the menu file form
/usr/etc/xdg/menus/puppy.menu
to
/usr/etc/xdg/menus/applications.menu
or
/etc/xdg/menus/applications.menu
I will try later today or tomorrow but it would be great if someone tries first.
I got it.
I just was able to run kfind with x.org (Icewm).
I think the problem was caused by usr_more.sfs, especially by symlinks overwriting folders in /usr, e.g. /usr/lib/qt
We often have the problem, that RPMs overwrite the symlink with a folder /usr/share/pixmaps, when they were converted to tgz (Dotpups).
This has a serious consequence: Windowmanagers do not work, the windows have no borders.
Seems to be something similar here.
Now I copied the files manually to the folders, thats to say the whole usr_more.sfs went to pup001.
If I can find out, which entry exactly caused the trouble, it might be possible to create another usr_more.sfs.
What really was strange:
When I started puppy with usr_more.sfs without usr_devx.sfs, I got a kernel-error:
"unable to handle kernel NULL pointer dereference at virtual address 00000000". Finish, no console, no X.
With usr_devx.sfs I could start icewm.
Just the symptoms described in a message before apeared (nothing happened running "kfind").
With a NORMAL Puppy (no xorg), it is the other way round.
With usr_devx.sfs KDE cannot start.
Without usr_devx.sfs it works.
So far for today.
The next days will be encirceling the problem, and creating a new usr_more.sfs.
Greets, Mark
I just was able to run kfind with x.org (Icewm).
I think the problem was caused by usr_more.sfs, especially by symlinks overwriting folders in /usr, e.g. /usr/lib/qt
We often have the problem, that RPMs overwrite the symlink with a folder /usr/share/pixmaps, when they were converted to tgz (Dotpups).
This has a serious consequence: Windowmanagers do not work, the windows have no borders.
Seems to be something similar here.
Now I copied the files manually to the folders, thats to say the whole usr_more.sfs went to pup001.
If I can find out, which entry exactly caused the trouble, it might be possible to create another usr_more.sfs.
What really was strange:
When I started puppy with usr_more.sfs without usr_devx.sfs, I got a kernel-error:
"unable to handle kernel NULL pointer dereference at virtual address 00000000". Finish, no console, no X.
With usr_devx.sfs I could start icewm.
Just the symptoms described in a message before apeared (nothing happened running "kfind").
With a NORMAL Puppy (no xorg), it is the other way round.
With usr_devx.sfs KDE cannot start.
Without usr_devx.sfs it works.
So far for today.
The next days will be encirceling the problem, and creating a new usr_more.sfs.
Greets, Mark
- bombayrockers
- Posts: 427
- Joined: Sat 24 Sep 2005, 16:47
- Location: Mumbai, India
- Contact:
My configuration
My configurations are
1) Puppy 1.0.5
2) NO Xorg server (the sequence of events -> made install in puppy with default xserver -> was not configured right -> i thought it had something to do with X server therefore installed Xorg.pup -> did not work -> installed xorg from slax -> worked -> When making a fresh install for uploading i was able to run kde+arts on puppys default x server)
3) qt is included in usr_more.sfs. it you already have qt installed kde might not work becaue usr_more.sfs is loaded first then the /root/.usr folder so qt from usr_more gets replaced by qt in /root/.usr
4) pristine pup001 file
5) did not use usr_devx.sfs while making the install. however i just now ran kde+puppy 1.0.5+usr_devx.sfs an even compiled openbox on it. on my box it is working. MU are you using 1.0.6 ? This can be an issue.
MU i recommend donot use xorg.pup+kde -> i was not able to get them working. if xorg is necessity then i would make another usr_moo2.sfs for the slax xorg.
klh i have no experience with hard drive install. never tried that after i had a horrible hd accident. however i think that the rc.local located in usr_more.sfs might be a problem
this is what i have done in rc.local
rmdir /opt
ln -s /root/.opt /opt
1) Puppy 1.0.5
2) NO Xorg server (the sequence of events -> made install in puppy with default xserver -> was not configured right -> i thought it had something to do with X server therefore installed Xorg.pup -> did not work -> installed xorg from slax -> worked -> When making a fresh install for uploading i was able to run kde+arts on puppys default x server)
3) qt is included in usr_more.sfs. it you already have qt installed kde might not work becaue usr_more.sfs is loaded first then the /root/.usr folder so qt from usr_more gets replaced by qt in /root/.usr
4) pristine pup001 file
5) did not use usr_devx.sfs while making the install. however i just now ran kde+puppy 1.0.5+usr_devx.sfs an even compiled openbox on it. on my box it is working. MU are you using 1.0.6 ? This can be an issue.
MU i recommend donot use xorg.pup+kde -> i was not able to get them working. if xorg is necessity then i would make another usr_moo2.sfs for the slax xorg.
klh i have no experience with hard drive install. never tried that after i had a horrible hd accident. however i think that the rc.local located in usr_more.sfs might be a problem
this is what i have done in rc.local
rmdir /opt
ln -s /root/.opt /opt
- bombayrockers
- Posts: 427
- Joined: Sat 24 Sep 2005, 16:47
- Location: Mumbai, India
- Contact:
thanks MU
yes the only other distro with kde that was faster than kde+puppy on my computer was an install of vector SOHO 5
- bombayrockers
- Posts: 427
- Joined: Sat 24 Sep 2005, 16:47
- Location: Mumbai, India
- Contact:
KDE & usr_devx.sfs
MU wrote
and usr_more.sfs also has /usr/lib/qt this leads to ?? error - kde is not able to find libqt-mt.so.3
dont know what is the solution
yes this happens because usr_devx.sfs has /usr/lib/qtWith a NORMAL Puppy (no xorg), it is the other way round.
With usr_devx.sfs KDE cannot start.
Without usr_devx.sfs it works.
and usr_more.sfs also has /usr/lib/qt this leads to ?? error - kde is not able to find libqt-mt.so.3
dont know what is the solution
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: KDE & usr_devx.sfs
No, usr_devx.sfs does not have libqt-mt.so*.bombayrockers wrote:MU wroteyes this happens because usr_devx.sfs has /usr/lib/qtWith a NORMAL Puppy (no xorg), it is the other way round.
With usr_devx.sfs KDE cannot start.
Without usr_devx.sfs it works.
and usr_more.sfs also has /usr/lib/qt this leads to ?? error - kde is not able to find libqt-mt.so.3
dont know what is the solution
It does have /usr/lib/qt/libqui.so*