(old)Puppy Linux Discussion Forum

Luci-236 with the latest Trinity..................

Many thanks to Iguleder for giving us further updates to test and admire....

I've loaded the new SFSs onto a frugal install of luci236 as thats the main route that people will see its availability I think.

I first tried it with a pristine (new) lucisave and then I reused the lucisave that I'd been using with the previous version ("downgrading" it to jwm and removing the old SFS load before doing the transfer)

The main usability problems I have (none show stoppers but maybe need health warnings of some sort for Lucid Puppy users) are:

1. no usb detection onto the desktop - pmount can be used

2. now solved

3. reboot and poweroff not automatic from menu - have to type shock horror at prompt or use PupShutdown Manager pet

4. now solved

5. menus are a mishmash of Lucid and Trinity entries with most Lucid items in the humungous "Lost & Found" menu.

6. Konqueror file manager does not have actions for Puppy file types - RoxFiler is occasionally needed.

Would love to help to make some of these better but not clever or knowledgeable enough to know where to start.....for instance if I started to tidy up the menu structure how would I export my results so that they could be used by others? Or if I were to tailor PupShutdown how would I create a new Trinity specific PET?

Cheers
Peter

peebee wrote:Many thanks to Iguleder for giving us further updates to test and admire....

I've loaded the new SFSs onto a frugal install of luci236 as thats the main route that people will see its availability I think.

I first tried it with a pristine (new) lucisave and then I reused the lucisave that I'd been using with the previous version ("downgrading" it to jwm and removing the old SFS load before doing the transfer)

The main usability problems I have (none show stoppers but maybe need health warnings of some sort for Lucid Puppy users) are:

1. no usb detection onto the desktop - pmount can be used

Same with squeeze 009

peebee wrote:2. -23 hour clock display after a reboot

In squeeze I get the correct time.

peebee wrote:3. reboot and poweroff not automatic from menu - have to type shock horror at prompt or use PupShutdown Manager pet

Same in squeeze 009 and this issue has been raised in this thread already.

peebee wrote:4. no sound volume control in the tray - no system use graphic like in jwm

In squeeze 009 on first boots I got the KDE volume, not anymore. But normally retrovol should have come to life. Not anymore. I just found out that's because Kmix isn't run at boot probably. I executed Kmix and have the KDE vol now.

peebee wrote:5. menus are a mishmash of Lucid and Trinity entries with most Lucid items in the humungous "Lost & Found" menu.

Same in squeeze 009 and has also been addressed here. The reason seems to be the category entries not being the same for JWM and KDE. I move those entries with Kmenu setup the proper place, eventually by creating new categories, but my question how to 'export' this menu setup remains unandwered.

peebee wrote:6. Konqueror file manager does not have actions for Puppy file types - RoxFiler is occasionally needed.

Normal, it's a different file manager. The same will happen if a different file manager in JWM is used. Konqueror has to be 'teached' how to handle file types.

peebee wrote:Would love to help to make some of these better but not clever or knowledgeable enough to know where to start.....for instance if I started to tidy up the menu structure how would I export my results so that they could be used by others? Or if I were to tailor PupShutdown how would I create a new Trinity specific PET?

Cheers
Peter

Cheers.

This Trinity experiment is so funny ... lulz

I want to try another approach - make a mutated Pdebthing version just for Trinity and use the Trinity repo of Debian Squeeeze with the Ubuntu Lucid repo - Trinity itself from the Trinity repo and all dependencies from Ubuntu Lucid. There's a good chance this won't work ... but I still think it's a good idea.

I also intend to start working on the actual trinitypup experiment - a "kdpup" built with Woof. The previous plan was to bake a barebones "dpup", then stir it with the Trinity SFSs, but the recipe turned out to be non-booting

In the first KDE (base) when hovering with the mouse over a running application in the system tray, I got the complete name in a 'balloon'.
With this latest Trinity not any more.
I checked settings of the system tray, but didn't find where I have to tick an option.
Anyone knows?

With this new Trinity-core, amarok still don't run on my PS apart from a 2 second splash screen.

Béèm wrote:In the first KDE (base) when hovering with the mouse over a running application in the system tray, I got the complete name in a 'balloon'.
With this latest Trinity not any more.
I checked settings of the system tray, but didn't find where I have to tick an option.
Anyone knows?

I just discovered it, but there is some inverse logic in play here.
In Configure KDE - panel - appearance I had to untick 'Enable icon mouse_over effect.'
Not very logical.

Béèm wrote:With this new Trinity-core, amarok still don't run on my PS apart from a 2 second splash screen.

For what its worth, Amarok works fine on both Luci-236 and Zen-006....both frugal installs with the two new Trinity sfs files,

Related to earlier posts, here on Zen/Trinity 006 I do have usb detection.

A way to get the sound control in the tray is:

Run kmix - this creates a tray item and opens a window
Close the kmix window
Save the session
In the Session Manager - choose start with saved session

Cheers
Peter

James C wrote:

Béèm wrote:With this new Trinity-core, amarok still don't run on my PS apart from a 2 second splash screen.

For what its worth, Amarok works fine on both Luci-236 and Zen-006....both frugal installs with the two new Trinity sfs files,

Related to earlier posts, here on Zen/Trinity 006 I do have usb detection.

I didn't specify, but it was with Trinity on squeeze 009.
No amarok, no USB devices.

I just installed on 236 now.
Amarok is running and after editing fstab, I have the USB devices, but they can't be mounted.
Message: HAL is needed.
And indeed I don't see in the running processes HAL is running and I don't see a hald bin/script.

is there a weather widget for kde?

I have worked now with trinity-core and the apps.
In squeeze 009 as well as in lucid 236.
In squeeze I have slowness and functions of wine programs that don't work any more. A new save file had to be made.

In lucid 236 I had the applications, like SeaMonkey on the screen but not in a window. So I didn't have the close button and I had to cole by menu|file|quit.
In ROX there is no menu, so I had to kill the application.

I had to make two times a new save file already for lucid.

Hi,
on my Puppy 5.1.1 frugal i removed 2 previous packages and replaced them with new *trinity*.sfs ones.
Now during boot I can only get to command line, no one window manager starts. When I type startx, I get to JWM. But from there I can only shutdown/reboot. No other option in Shutdown menu section works!
What is wrong?

You have to type xwin startkde

Béèm wrote:You have to type xwin startkde

Nope, that did not help. Moreover, after that xwin did not work as "standalone" either. Only xwin jwm launched JWM. But no KDE stilll.

It doesn't work isn't very helpful.
You have to give details about what you see.

Béèm wrote:I saw a Gnome bluetooth Wizard in Trinity.
Did anyone succeed in using it?
dbus is already in Trinity.
But I suppose Bluez and other apps might be necessary to install.

Anybody an idea?

will you be including kmail soon?
how do you set konqueror as default browser? i had opera set as default before installing kde.

edit- i changed the file found here /usr/local/bin/defaultbrowser to konqueror.

Béèm wrote:It doesn't work isn't very helpful.
You have to give details about what you see.

When I type xwin startkde, screen flickers, then returns to the same prompt where it recommends launch xorgconf. But that does not help, still same black screen with few lines of text after re-configuring.
And JWM starts without any problem.

Hi darkduck

Did you keep the same pupsave after removing the earlier sfs's and starting with the latest?

I think you will need to start again with a clean pupsave......there is some residue in your old pupsave that is stopping the new kde starting.

From bitter experience I always try 1st a new pupsave, then a COPY of my old pupsave so I can always go back if there are problems. Takes a bit longer but is better for peace of mind.

Cheers
Peter