The patch contains some bug fixes, and hacked scripts.
It mainly has fixes for wbar, and hacked restartwm, wmreboot, and wmpoweroff scripts necessary for xfce4-panel.
So, in short..if you don't want to install the xfce4-panel to run with openbox, then you don't really need the patch.

Also I am uploading a Solidpup OBXF version.
OBXF is just short for "Openbox-xfce4panel". This is mainly to test the new desktop envrionment for bugs.
Along with the files needed to run xfce4-panel, I have only added Opera as an additional app, so far.
More apps will be added later on...

Please don't try to download the new OBXF pup yet... current upload time remaining is about 1hour from now.

In fact, my problem was I have not the /etc/openbox_panel file.
So, I did a symlink /usr/bin/xfce4-panel in the /root/Startup directory (and remove the symlink wmbar in).

It sounds like you didn't install the patch first, because the patch also removes that symlink to wbar and replaces it with "wbar_launcher".
When xfce4-panel is running, the wrapper doesn't run wbar...but wbar will launch by itself in icewm. I recommend installing the patch now... the desktop will revert back to openbox + tint2 once you restart-x.

Next enter this in the terminal:

Code:

geany /etc/openbox_panel

In this text file, just put the command for the panel you want to run... tint2, xfce4-panel. fbpanel etc...
Of course, fbpanel is not installed by default, so it will only work after you install it. fbpanel-6.0-patched-3-q1.pet

I have just found a rather odd problem with Opera... .pet files downloaded as .gz files. Does anyone know the solution for this???

> I have just found a rather odd problem with Opera... .pet files downloaded as .gz files. Does anyone know the solution for this???

Yep. Simply rename them with a *.pet suffix when you save them. Will unpack and install stuff as usual.
Probably opera derives its suffix from the first few bytes of the file instead of the filename itself. (And indeed pet files do use the .gz compression.)

Musher, thanks for the tip. It kinda makes sense since .pet files are just .gz files with the extension renamed.
This problem doesn't happen to me all the time in Opera. I've downloaded a lot of pets that have not been renamed to .gz files.
... strange indeed.

I have some bad news... bad news for me at least. I said in some previous post that Shinobar's getnvidia pet did not work for me.
So I finally got around to try and make the nvidia pet manually. Unfortunately, that didn't work for me either.
The nvidia-installer.log file says this:

I couldn't figure out the problem with that info though.
As a hunch, I loaded up an older version of Solidpup, and tried Shinobar's getnvidia.pet. It worked perfectly for me.
If I can't figure it out the problem, then it looks like I will have to backtrack to version beta-2.3, and start again from there... aargh!

Luckily, I documented (almost) all of the changes I made along the way, but I estimate that this will set me back about 2 weeks.
Current releases are still stable to use, but having video drivers not being able to compile is an absolute no-no for me.
In the meantime, you guys can play with what I've released and a new Nvidia pet is now available for testing. nvidia-glx-304-60-k2.6.32.28.pet
-Last edited by Tman on Fri 02 Nov 2012, 14:53; edited 2 times in total

Musher, thanks for the tip. It kinda makes sense since .pet files are just .gz files with the extension renamed.
This problem doesn't happen to me all the time in Opera. I've downloaded a lot of pets that have not been renamed to .gz files.
... strange indeed.

In Opera 12.02:
Tools->Preferences->Advanced->Downloads

Uncheck "File types opened with Opera"

Edit the MIME type application/x-gzip
by adding pet to the comma-separated list of File extensions

--------

EDIT: I'm not sure about that. I do recall seeing something (perhaps in an Opera thread or another forum) about hopw to fix that problem.

To be honest, I am using old-fashioned wired LAN connection. Although I do have a Wireless-N usb stick and an older model Wireless-G router, I don't really have a need for them with my desktop computer, so they just sit, stored-away in boxes.

But when I did try them for a little while, about 2 years back, I remember that I had to set up the wifi password and other settings with the Network Connection Wizard, but my settings were saved when I rebooted.

So, I don't know why it is not saving your settings...perhaps placing your questions somewhere in the "House Training" section of this forum will get you the answers you are looking for.

Also, the link to the new Nvidia pet (a few posts above) is now fixed.
-

Hi, how can I have it connect to wireless on bootup? Network Wizard lets me connect, but it doesn't connect on later boot,

Hi Sheldon, one of the main reasons I use SolidpupLITE is that it has always reconnected my wireless after boot - and it does this faster than most of my other puppies - so I think Solidpup itself is good in this area.
Which Network wizard do you use for your setup? Do you use SNS, Frisbee or the standard (classic) network wizard? I almost always use the standard wizard as I fins SNS unreliable, and have had some variable behaviour from Frisbee on some machines/puppies.
Are you able to do a trial by making a fresh Solidpup installation, with fresh savefile, and then connect with only the standard wizard then resave? See if that allows reconnection after boot?
(Also are you choosing a different puppy hostname for each puppy install? eg: not puppypc but something like puppypc1234?) Some routers (like my Thomson) keep a sort of database of which machines come online (IP address, MAC address and hostname) and it seems to affect the reliability of connection if the same hostname is attached to multiple devices.

Hi, how can I have it connect to wireless on bootup? Network Wizard lets me connect, but it doesn't connect on later boot,

Hi Sheldon, one of the main reasons I use SolidpupLITE is that it has always reconnected my wireless after boot - and it does this faster than most of my other puppies - so I think Solidpup itself is good in this area.
Which Network wizard do you use for your setup? Do you use SNS, Frisbee or the standard (classic) network wizard? I almost always use the standard wizard as I fins SNS unreliable, and have had some variable behaviour from Frisbee on some machines/puppies.
Are you able to do a trial by making a fresh Solidpup installation, with fresh savefile, and then connect with only the standard wizard then resave? See if that allows reconnection after boot?
(Also are you choosing a different puppy hostname for each puppy install? eg: not puppypc but something like puppypc1234?) Some routers (like my Thomson) keep a sort of database of which machines come online (IP address, MAC address and hostname) and it seems to affect the reliability of connection if the same hostname is attached to multiple devices.

Just a brief reply, because I'm tired etc.
At the moment, it's the standard (classic) network wizard, using WEP.
Her old computer is still using that, while I test this one. Maybe that's why WPA-2 gave trouble?
I don't know where to get Frisbee that works under SolidPup?

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum