Quirky 021 feedback

[BarryK]

quirky021 frugal
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20091216 SeaMonkey/1.1.18

+ try to download by clicking on the paper clip or the word "Download"
http://murga-linux.com/puppy/viewtopic. ... &start=232
JustGreg's grub4dos_htm.zip
+ the "Save it to disk" dialog will not go away
+ I can move that dialog to show the underlying save dialog
+ then continue the save

+ using right-click (contextual menu) works no problem

Only seems Gecko has changed between quirky021 and puppy431

puppy431 frugal
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20090910 SeaMonkey/1.1.18

No problem with clicking the paper clip or Download.

There is a problem with SeaMonkey 1.1.18 and Openbox window manager. Surprising that it has this bug, considering that Openbox is supposed to be a very mature product.

You don't really have to drag the save-as dialog away, just click on the underlying destination-chooser dialog -- notice that it's header is flashing -- must be Openbox's way of letting you know that this dialog should be on top but isn't.

[BarryK]

Hi all,
@BarryK
Barry, there is still something amiss with xorgwizard.
You may not remember but in the Q013 thread I reported that after following your instructions,dated 31/3/10, the X05 would run with the Intel i810 driver.
In the Quirky 018 thread I reported that no matter what I did xorgwizard would revert to the vesa driver.
Again in Quirky 021 xorgwizard reverts to the vesa driver. This time it does remove the intel driver from /usr/X11R7/lib/xorg/modules/drivers and inserts the i810 driver, but it applies the vesa driver.
I tried changing vesa to i810 in xorg.conf, but that did not work. Had to run xorgwizard to get graphics.
Any suggestions?
Cheers

Looks like you will have to manually remove /usr/lib/xorg/modules/drivers/vesa_drv.so.

Hmmm, that might not work. The Xorg probe only chooses vesa as a last resort, so it is thinking that i810 is not suitable. So, I don't know if removing vesa will force it to choose i810.

[JustGreg]

The system is Acer Aspire Revo, about 1 Gigabyte memory and Nvidia Ion video. Quirky 022 first tried the nv driver and failed due to the Ion video not being found. Second try, fresh without a save file, I pick the Nvidia 195.26.15 driver (just nvidia in list). It worked with out a problem. I am posting this using Quirky 022.

I want the nvidia-settings tool. So, I expanded only the nvidia-195.36.15-pkg1.run file. I copy the nvidia-settings file to /root/my-applications/bin and try running it. The tool started and worked. I got this error message:

Code: Select all

ERROR: libGL setup error : libGL.so.1: cannot open shared object file: No such  file or directory

I copied to /root/my-applications/lib the file, libGL.so.195.136.15 and create link libGL.so.195.1 to it.. Ran the nvidia-settings tool again. It worked with this error message:

Code: Select all

ERROR: libGL setup error : libGLcore.so.1: cannot open shared object file: No such file or directory

I copied to /root/my-applications/lib the file, libGL.core.so.195.36.15 and link to it, libGL.core.so.1. Ran the nvidia-settings tool and got this error:

Code: Select all

ERROR: libGL setup error : libnvidia-tls.so.1: cannot open shared object file: No such file or directory

I did the same for the file, libnvidia.tls.so.195.36.15 and linked it to libnvidia.tls.so.1. This time when I tried to run the nvidia-settings tool, it failed to run with a segmentation fault. Eliminating the link, allowed nvidia-settings tool to run with a minor non-fatal error. If you get the segmentation error with the nvidia-settings tool, then look for libnvidia.tls.so.1 file and rename or delete it.

The nvidia-settings tool and the first two libraries require about 25 Megabytes of storage. The nvidia-settings tool by itself requires 1511 Kbytes of storage. I do not know for sure if the two libraries are really needed.

I hope this helps.

[Hesse James]

Hi Barry
Finally many thanks from my side for the 022. It was the first time ever I have seen a Puplet initially starting with 1900x1050x24 on my TV with a fully working Nvidia-driver.
The next will be the installation of some Lirc, Sat and other drivers which seem to be a little bumpy as I have quickly tested that this morning. I will see.
Many thanks again and good luck for the release.

[BarryK]

The system is Acer Aspire Revo, about 1 Gigabyte memory and Nvidia Ion video. Quirky 022 first tried the nv driver and failed due to the Ion video not being found. Second try, fresh without a save file, I pick the Nvidia 195.26.15 driver (just nvidia in list). It worked with out a problem. I am posting this using Quirky 022.

I want the nvidia-settings tool. So, I expanded only the nvidia-195.36.15-pkg1.run file. I copy the nvidia-settings file to /root/my-applications/bin and try running it. The tool started and worked. I got this error message:

Code: Select all

ERROR: libGL setup error : libGL.so.1: cannot open shared object file: No such  file or directory

I copied to /root/my-applications/lib the file, libGL.so.195.136.15 and create link libGL.so.195.1 to it.. Ran the nvidia-settings tool again. It worked with this error message:

Code: Select all

ERROR: libGL setup error : libGLcore.so.1: cannot open shared object file: No such file or directory

I copied to /root/my-applications/lib the file, libGL.core.so.195.36.15 and link to it, libGL.core.so.1. Ran the nvidia-settings tool and got this error:

Code: Select all

ERROR: libGL setup error : libnvidia-tls.so.1: cannot open shared object file: No such file or directory

I did the same for the file, libnvidia.tls.so.195.36.15 and linked it to libnvidia.tls.so.1. This time when I tried to run the nvidia-settings tool, it failed to run with a segmentation fault. Eliminating the link, allowed nvidia-settings tool to run with a minor non-fatal error. If you get the segmentation error with the nvidia-settings tool, then look for libnvidia.tls.so.1 file and rename or delete it.

The nvidia-settings tool and the first two libraries require about 25 Megabytes of storage. The nvidia-settings tool by itself requires 1511 Kbytes of storage. I do not know for sure if the two libraries are really needed.

I hope this helps.

I don't understand what you have done exactly. If you are using Q022, it has the cutdown Nvidia. Ok, to get nvidia-settings and all the extra libraries, you need my full Nvidia PET package.

I have recently improved that package, and uploaded it a few minutes ago. Get it from here:

http://distro.ibiblio.org/pub/linux/dis ... 2-1-q1.pet

...install that, you should get an entry for nvidia-settings in the Setup menu. The settings won't be remembered between boots -- see my recent blog post -- fixed in next Quirky.

[Béèm]

Already reported in quirky 13 and still here in quirky 22 (didn't try quirky 21)

When going with the mouse cursor over the desktop drive icons, the filesystem is in the pop-up box, but not the size.

Kinda annoying.

[Béèm]

Already reported before.

When starting with pfix=ram at the end of the session the panel to create a save file isn't displayed and a message is issued session not saved

The circumvention I found is to do a first boot with pfix=ram and psubdir=
I then get the panel to create a save file
Once a save file created, the psubdir= isn't needed anymore

It's kinda annoying as f.e. Lucid doesn't have this issue, so when installing a new quirky, I forget about this.

[Béèm]

When configuring with SNS the internet connection, at next boot this configuration is lost and has to be done again.
I am not sure, but I think this has been reported earlier.

Supplementary a suggestion.
Sometimes I enter the WEP key and forget to select the WEP radio button.
The only choice I have then is to go back to the initial sceen.
It would be user-friendly if one could go back one step to select that radio button, while retaining the key entered.

[aarf]

q21 has this same linking error as lupu113

[BarryK]

Already reported in quirky 13 and still here in quirky 22 (didn't try quirky 21)

When going with the mouse cursor over the desktop drive icons, the filesystem is in the pop-up box, but not the size.

Kinda annoying.

The size information has always been there for me.

The size information is obtained in script /usr/bin/pup_event_frontend_d:

Code: Select all

    PROBEPART="`probepart -k | grep -E '\|ext4\||\|ntfs\||\|msdos\||\|vfat\||\|ext2\||\|ext3\||\|iso9660\||\|xfs\||\|reiser'`"
    DRVINFO="`echo "$PROBEPART" | grep "$drvPATTERN" | cut -f 1,2,3 -d '|' | tr '\n' ' '`"

The size info is in the 3rd field of DRVINFO.

The information is obtained from this, try it in a terminal:

# probepart -k

[BarryK]

Already reported before.

When starting with pfix=ram at the end of the session the panel to create a save file isn't displayed and a message is issued session not saved

The circumvention I found is to do a first boot with pfix=ram and psubdir=
I then get the panel to create a save file
Once a save file created, the psubdir= isn't needed anymore

It's kinda annoying as f.e. Lucid doesn't have this issue, so when installing a new quirky, I forget about this.

This is another one that I can't reproduce. If I don't get this problem, then I can't fix it. I certainly have no idea theoretically why it would happen.

[BarryK]

When configuring with SNS the internet connection, at next boot this configuration is lost and has to be done again.
I am not sure, but I think this has been reported earlier.

I haven't had this problem. I doubt that the configuration is "lost", it is just that the network connection script at bootup is failing to make the connection.

After you have configured your connection with SNS, you should see an entry in file /etc/simple_network_setup/connections.

At bootup, /usr/local/simple_network_setup/rc.network is run, which reads the 'connections' file and tries to make a connection from the information in it.

So, if you have booted up and failed to get a connection, try running this in a terminal:

# /usr/local/simple_network_setup/rc.network

...see if there are any error messages.

[BarryK]

q21 has this same linking error as lupu113

I looked at your post in the Lupu thread, however you have not explained it completely. Just posting a picture showing the error means little. What operation did you perform to cause this error?

[Béèm]

quirky 22 frugal desktop drive icons don't give size

Thank you for your reply.
I forgot to say I have this after the first boot with pfix=ram already.
At this point my Belgium keyboard is selected as well as the country locale nl_BE@euro: Dutch,Belgium
Another (wild?) idea: was quirky 13 the first one with fbpanel in stead of JWM? As before the 13 I didn't have that problem.

probepart -k gives

Code: Select all

# probepart -k
/dev/sda1|ntfs|22695088
/dev/sda2|vfat|13245120
/dev/sdb1|vfat|78140128
/dev/sdb2|ext3|78140160
/dev/sdb3|none|1
/dev/sdb4|ntfs|27262305
/dev/sdb5|ext3|10482381
/dev/sdb6|vfat|78140128
/dev/sdb7|ext2|40403443
/dev/sr0|none|1048575
#

Look good I suppose

Then I tried to find /usr/bin/pup_event_frontend_d: , but I only found /usr/bin/pup_event_frontend_d (no double dot) in /sbin not in /usr/bin

Code: Select all

# find / |grep pup_event_frontend
/sbin/pup_event_frontend_d
/initrd/pup_ro2/sbin/pup_event_frontend_d

The code you reference is indeed in this script.

I tried to execute the script in a terminal and get this

Code: Select all

# sh pup_frontend_d
sh: pup_frontend_d: No such file or directory
# find / |grep pup_event_frontend:
# pwd
/sbin
# 

Don't know quite well how to diagnose on further.

[Béèm]

Already reported before.

When starting with pfix=ram at the end of the session the panel to create a save file isn't displayed and a message is issued session not saved

The circumvention I found is to do a first boot with pfix=ram and psubdir=
I then get the panel to create a save file
Once a save file created, the psubdir= isn't needed anymore

It's kinda annoying as f.e. Lucid doesn't have this issue, so when installing a new quirky, I forget about this.

This is another one that I can't reproduce. If I don't get this problem, then I can't fix it. I certainly have no idea theoretically why it would happen.

I understand when you aren't able to reproduce the issue it's difficult to solve. As I have a circumvention, it's ok for me.

[Béèm]

When configuring with SNS the internet connection, at next boot this configuration is lost and has to be done again.
I am not sure, but I think this has been reported earlier.

I haven't had this problem. I doubt that the configuration is "lost", it is just that the network connection script at bootup is failing to make the connection.

After you have configured your connection with SNS, you should see an entry in file /etc/simple_network_setup/connections.

At bootup, /usr/local/simple_network_setup/rc.network is run, which reads the 'connections' file and tries to make a connection from the information in it.

So, if you have booted up and failed to get a connection, try running this in a terminal:

# /usr/local/simple_network_setup/rc.network

...see if there are any error messages.

I looked in /etc/simple_network_setup/connections and the configuration info was in there.
So I rebooted in order to apply your tip and to my surprise for the first time the connection was made automatically.
So if after subsequent reboots I have the issue again, I know what to do to diagnose further.

[alec78]

Hi all,
@BarryK
Barry, there is still something amiss with xorgwizard.
You may not remember but in the Q013 thread I reported that after following your instructions,dated 31/3/10, the X05 would run with the Intel i810 driver.
In the Quirky 018 thread I reported that no matter what I did xorgwizard would revert to the vesa driver.
Again in Quirky 021 xorgwizard reverts to the vesa driver. This time it does remove the intel driver from /usr/X11R7/lib/xorg/modules/drivers and inserts the i810 driver, but it applies the vesa driver.
I tried changing vesa to i810 in xorg.conf, but that did not work. Had to run xorgwizard to get graphics.
Any suggestions?
Cheers

I deleted the vesa driver, result a black screen, I had to do a fresh boot from the CD.
Interestingly, when I plugged in the dongle with the save file on, and looked inside the save file all looked fine, with just the libi810 file at /usr/X11R7/lib and the i810 driver at /drivers.
Cheers
Looks like you will have to manually remove /usr/lib/xorg/modules/drivers/vesa_drv.so.

Hmmm, that might not work. The Xorg probe only chooses vesa as a last resort, so it is thinking that i810 is not suitable. So, I don't know if removing vesa will force it to choose i810.

[aarf]

q21 has this same linking error as lupu113

I looked at your post in the Lupu thread, however you have not explained it completely. Just posting a picture showing the error means little. What operation did you perform to cause this error?

this is lupu112
top left is puppy symlinked on an ext3 partition.
bottom right is an attempt which fails to symlink apuppy on a FAT partition
the space in the file name My Documents may or may not contribute to the error. subsequent linking attempts with FAT folders that dont have a space in the file name have also failed on Lupu112, but some test were possible in lupu113 when no space was in the file name.

[Béèm]

When configuring with SNS the internet connection, at next boot this configuration is lost and has to be done again.
I am not sure, but I think this has been reported earlier.

I haven't had this problem. I doubt that the configuration is "lost", it is just that the network connection script at bootup is failing to make the connection.

After you have configured your connection with SNS, you should see an entry in file /etc/simple_network_setup/connections.

At bootup, /usr/local/simple_network_setup/rc.network is run, which reads the 'connections' file and tries to make a connection from the information in it.

So, if you have booted up and failed to get a connection, try running this in a terminal:

# /usr/local/simple_network_setup/rc.network

...see if there are any error messages.

I looked in /etc/simple_network_setup/connections and the configuration info was in there.
So I rebooted in order to apply your tip and to my surprise for the first time the connection was made automatically.
So if after subsequent reboots I have the issue again, I know what to do to diagnose further.

When experimenting with a left vertical tray, I got the issue that I had no tittle bar for the applications. I restored to a bottom horizontal one, but I have still that issue. So I will have to stat with a fres quirky 22 save file.
I then reverted back to quirky 18 with which I have the SNS issue also.
I checked the connections file and all info in there is correct
I then executed the rc.network as instructed by you in a terminal and I have an error message, see below.

Code: Select all

# ls
help_security  rc.network  sns
# sh rc.network
Error for wireless request "Set Frequency" (8B04) :
    SET failed on device eth1 ; Operation not supported.
dhcpcd: version 5.1.5 starting
dhcpcd: eth1: broadcasting for a lease
dhcpcd: eth1: offered 192.168.1.3 from 192.168.1.1
dhcpcd: eth1: acknowledged 192.168.1.3 from 192.168.1.1
dhcpcd: eth1: checking for 192.168.1.3
dhcpcd: eth1: leased 192.168.1.3 for 172800 seconds
dhcpcd: forking to background
#

As I got an IP, the connection is working.
I will have to see what will happen on subsequent boots.

[JustGreg]

With my Acer Aspire Revo with Nvidia Ion graphics, I found with Quirky 021 and nvidia-195.36.15-k2.6.33.2-q1.pet installed that the installed nvidia-settings tool would fail with a "segmentation fault". I managed to get nvidia-settings tool to run by deleting this link:
/usr/X11R7/lib/libnvidia-tls.so.1
Running the nvidia-settings in a console terminal, it ran and worked properly (I changed resolution), but, there was a missing library error. Restoring the link, /usr/X11R7/lib/libnvidia-tls.so.1 to usr/X11R7/lib/libnvidia-tls.so.195.36.15, resulted in the nvidia-settings tool failing to work (the segmentation fault error).

Using Quirky 022, which has only the nvidia driver items, but no nividia-settings tool. I got nvidia-settings to work by coping from the Quirky021 nvidia pet installation, nvidia-settings to the Quirky022 save file directory /root/my-applications/bin. The two libraries ( /usr/X11R7/lib/libGL.so.195.36.15, /usr/X11R7/lib/libGLcore.so.195.36.15) to /root/my-applications/lib. I created links /root/my-applications/lib/libGL.so.1 and /root/my-applications/libGLcore.so.1 to the needed libraries. The nvidia-settings tool now works in Quirky022. Adding these items requires about 25 Megabytes of storage.