Lucid Puppy 5.2.7 RC2

[bigpup]

Playdayz,

Futwerk has made some new wallpapers specific for Lucid Puppy 5.2.6

He will work with you if there is something specific you would like to have.

Take a look:
http://www.murga-linux.com/puppy/viewto ... 952#546952

Example of one in use

[jpeps]

Just loaded 264; no errors with gnome-mplayer 1.0.4 or mplayer (I'm using the same downloaded youtube video and music files as previous tests)

Edit: I got gnome-mplayer-1.0.3 working without errors in lucid 525 by installing over version.0.9.9.2. The latter includes the libs and lintian overrides. Version 1.0.3 package is full of docs, manuals, and language support that bloats it quite a bit and can be removed.

[Sage]

Sage, The flashplayer install dialog should start when the browser is first started (not when it is installed). This will only work on new installs, not updates, and not if one has previously declined the offer. It has worked for me. Can you boot with pfix=ram, then install Opera with Quickpet, then start Opera and see what happens. Thanks.

At present, I don't have 266 installed. It is running 'live' with pfix=ram. No message to install Flash showed up. Opera 11.5 was chosen from the browser selection rather than opera.com. The usual overlay indicated that Flash need to be d/l-ed. I used the FP.pet to install it rather than a fresh d/l. ipso facto, there remains a Flash issue - sorry.

[bigpup]

Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
info: 0, warning: 3, error: 6
Done

This is almost certainly mplayer. I cannot recreate it by playing videos. Have you changed any of the options in gnome-mplayer? For instance, changing the Edit -> Preferences -> Video output to vfdpau. Probably not, I know Does knowing that it relates to mplayer give you any clues?

Oh, I can recreate it. Perhaps there is an option to turn that off.

It looks like good news Béèm. Gnome-mplayer 1.0.3 does not seem to do this. Kevin DeKorte who is the man for gnome-mplayer said that 1.0.4 has over 3,000 lines of new code, so reversion to 1.0.3. Gnome-mplayer 1.0.3 is a very nice version, and well-behaved too Thanks.

Found this info about this error message.

mplayer was initially compiled with vdpau and in order to take advantage of this feature Nvidia proprietary driver must be installed. First of all,

This is easily fixed. The issue is caused by Gnome Mplayer attempting to use the default VDPAU, which does not exists. To remove the message, launch Gnome Mplayer, select Edit->Preference. Enter xv into the video output and press close. This tells it to use xv instead of the default vdpau. I figured it out reading this blog:

Found this here:
http://forums.opensuse.org/english/get- ... ckend.html

More info here:
http://vsingleton.blogspot.com/2010/02/ ... ckend.html

[WB7ODYFred]

With my testing of Lucid 5.2.5 , I had problems with Gparted and "parted" (ie Graphical and regular partition editor )
crashing when reading a NON-DOS Disk Geometry where head size was greater than
63 heads on a brand new 4 GigaByte USB Flash disk from SanDisk Cruzer.
When SanDisk formated the USB Curzer Flash disk, they used non-sensical numbers for the Sectors per Track, Cylinders,
and number of Heads, that did not match up with what a REAL physical hard disk drive would use.
I did send a forum post to the parted group and compiled a newer version of parted 0.8.3
that did not crash with Head Size greater than 63 heads.

> Assertion (head_size <= 63) at dos.c:736 in function probe_partition_for_geom()
> failed. for Parted version 2.3
parted /dev/sdc
fdisk -l /dev/sdc
gparted /dev/sdc

Brian Lane's Patch file to fix bad DOS geometry crashes of Partedhttp://www.mail-archive.com/bug-parted@ ... 03310.html
Brian C Lane's reply to my March 8th 2011 Bug Posthttp://lists.gnu.org/archive/html/bug-p ... 00006.html

My Mail Bug Post to bug-parted mail-archive See March 8th entry http://lists.gnu.org/archive/html/bug-p ... index.html

So Trying to go from a freshly booted ISO PuppyLinux CDROM (freshly burned) to do a direct install of
Puppy Linux 5.2.5 to a USB Flash Drive would fail unless you searched on the www.murga-linux.com forum
and learned how to zero out the USB Flash partition first (ie /dev/sdc).
ie. dd if=/dev/zero of=/dev/sdc bs=512 count=1

Full Forum post on installing to USB Flash Disk. Thanks RDOG!
Bootable USB using GRUB and Puppy 5.2
http://www.murga-linux.com/puppy/viewtopic.php?t=64630

DarkCity's Forum Post on making a bootable USB Flash disk from another linux
http://www.murga-linux.com/puppy/viewto ... 51&t=54566

See the new July 23 2001 update on the Gparted Software. It drops the ability to resize FAT16 and FAT32 partitions,
that is a bummer, but fixes the bad DOS geometry crash problem.

Please CHECK Luci-266 CDROM --> to USB Install for a 8Gig and 16Gig and maybe 32GIG USB Flash drives.

http://gparted.sourceforge.net/news.php
The GParted team is proud to announce a new stable release of GParted Live (0.9.0-6).

This release includes GParted 0.9.0 and libparted-0.2.3-7 with the patch file fix-head-size-assertion.patch from Ubuntu.
The patch fixes a problem whereby GParted would crash if an unusual disk geometry was encountered.
This release is based on the Debian Sid repository as of July 23, 2011 (linux kernel 2.6.39-2).

I am looking for quality through checking that Luci-266 when fresh booted from a CDROM
can then install Luci-266 to either a 4 Gig USB Flash Drive or to a 8 Gig USB Flash drive with no errors.
Then next check that the USB Flash drives will boot in your PC with / or with out a Hard Disk Drive.

I want third world countries to be able to use PuppyLinux directly from USB Flash Drives.

Fred
ps. I posted here, because I did not know how to search all 54 pages on Luci-266 to find the entries that talked
about USB Flash install except for the 1st page which I manually read. I apologize for bringing up a topic,
that might already been solved and completed.

pss. Look I try to provide very complete information so that someone can extend from my documented work
to find an answer, but it seems my posts are so much wordier than most. Then after posting, no one
follows up to fix the posted error. (in this case installing to a 4Gigabyte USB Flash Drive).

I attached the file gparted_bad_pt_32.zip which can be unzipped into gparted_bad_pt_32
which is a copy of the first 32 sectors from a fresh never touched SanDisk Cruzer 4 gigabyte USB Flash disk drive.
You can test to see if Luci-266 gparted or parted crashes when trying to editor a USB partiton with a bad DOS geometry.

Will someone else please pickup the baton, and prove that gparted or parted have been
fixed in Luci-266 to not cause errors when installing PuppyLinux to the new large 4Gigabyte USB Flash drives?
Thank you very much, Fred

[jpeps]

This is easily fixed. The issue is caused by Gnome Mplayer attempting to use the default VDPAU, which does not exists. To remove the message, launch Gnome Mplayer, select Edit->Preference. Enter xv into the video output and press close. This tells it to use xv instead of the default vdpau. I figured it out reading this blog:

Thanks for finding this. Another reason why it's important to fresh compile apps. Another issue I found was a deprecated /root/.nvidia-settings-rc file that installed when I was experimenting with drivers. This triggered line 59 in /root/.xinitrc. When I commented it out, the problem went away.

edit: My copy of Gnome Mplayer 1.0.3 video output is set to x11...I didn't touch it.

[bigpup]

Luci266
Frugal + save

After installing Pwidgets
Nathan Wallpaper Setter no longer has view window active at bottom left of program window.

[bigpup]

This is easily fixed. The issue is caused by Gnome Mplayer attempting to use the default VDPAU, which does not exists. To remove the message, launch Gnome Mplayer, select Edit->Preference. Enter xv into the video output and press close. This tells it to use xv instead of the default vdpau. I figured it out reading this blog:

Thanks for finding this. Another reason why it's important to fresh compile apps. Another issue I found was a deprecated /root/.nvidia-settings-rc file that installed when I was experimenting with drivers. This triggered line 59 in /root/.xinitrc. When I commented it out, the problem went away.

edit: My copy of Gnome Mplayer 1.0.3 video output is set to x11...I didn't touch it.

Another option I found to deal with this, but not sure what other effects it will have.
in /etc/mplayer/mplayer.conf
Line 20
make active vo=xv,x11

Update:
Well it looked like a fix at first, but does not seem to totally cure the problem.

[bigpup]

While we are looking at xerrs.log
What about some of this other stuff.
Like in mine. What is all this stuff with Pwidgets?

X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-25-server i686 Ubuntu
Current Operating System: Linux puppypc 2.6.33.2 #1 SMP Thu May 27 10:56:32 EST 2010 i686
Kernel command line: pmedia=atahd psubdir=Luci266 pfix=fsck
Build Date: 23 April 2010 05:11:50PM
xorg-server 2:1.7.6-2ubuntu7 (Bryce Harrington <bryce@ubuntu.com>)
Current version of pixman: 0.16.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 25 08:36:21 2011
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/usr/lib/X11/xorg.conf.d"
(EE) Failed to load module "nouveau" (module does not exist, 0)
(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri.so failed (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
(EE) GLX: could not load software renderer
cat: /sys/block/fd0/device/vendor: No such file or directory
cat: /sys/block/fd0/device/model: No such file or directory
/usr/bin/openbox
/usr/sbin/fixwidgets: line 5: kill: (6604) - No such process
/usr/sbin/fixwidgets: line 6: kill: (6609) - No such process
Conky: /root/.pwidgets/widgets/Ram_bar: 8: no such configuration: 'HEIGHT=40'
Conky: /root/.pwidgets/widgets/Ram_bar: 9: no such configuration: 'OFFSET_X_LEFT=40'
Conky: /root/.pwidgets/widgets/Ram_bar: 10: no such configuration: 'OFFSET_X_RIGHT=20'
Conky: /root/.pwidgets/widgets/Calendar: 8: no such configuration: 'WEEK_FIRST_DAY=SUNDAY'
Conky: /root/.pwidgets/widgets/Calendar: 9: no such configuration: 'HEIGHT=170'
Conky: /root/.pwidgets/widgets/Calendar: 10: no such configuration: 'OFFSET_X_LEFT=40'
Conky: /root/.pwidgets/widgets/Calendar: 11: no such configuration: 'OFFSET_X_RIGHT=20'
Conky: /root/.pwidgets/widgets/Puppylinux: 7: no such configuration: 'HEIGHT=60'
Conky: /root/.pwidgets/widgets/Puppylinux: 8: no such configuration: 'OFFSET_X_LEFT=40'
Conky: /root/.pwidgets/widgets/Puppylinux: 9: no such configuration: 'OFFSET_X_RIGHT=35'
Conky: /root/.pwidgets/widgets/Cpu_bar: 7: no such configuration: 'HEIGHT=50'
Conky: /root/.pwidgets/widgets/Cpu_bar: 8: no such configuration: 'OFFSET_X_LEFT=40'
Conky: /root/.pwidgets/widgets/Cpu_bar: 9: no such configuration: 'OFFSET_X_RIGHT=20'
Conky: forked to background, pid is 6660
Conky: forked to background, pid is 6661
Conky: forked to background, pid is 6662
Conky: forked to background, pid is 6663




Conky: desktop window (40001e) is subwindow of root window (43)
Conky: desktop window (40001e) is subwindow of root window (43)
Conky: window type - override
Conky: drawing to created window (0x1000001)
Conky: window type - override
Conky: drawing to created window (0xe00001)
Conky: drawing to double buffer
Conky: drawing to double buffer
Conky: setting bg window (e00001)
Conky: setting bg window (e00001)
Conky: desktop window (40001e) is subwindow of root window (43)
Conky: window type - override
Conky: drawing to created window (0x1200001)
Conky: desktop window (40001e) is subwindow of root window (43)
Conky: window type - override
Conky: drawing to created window (0x1400001)
Conky: drawing to double buffer
Conky: setting bg window (1200001)
Conky: drawing to double buffer
Conky: setting bg window (1400001)
Conky: setting bg window (1400001)
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
Conky: setting bg window (1200001)
Conky: setting bg window (1000001)
openbox
Generating /root/.fbpanel/default...
killall: blinky_tray: no process killed
/usr/sbin/delayedrun: line 129: 6656 Terminated $a
/usr/sbin/delayedrun: line 129: 6757 Terminated $a
killall: traytemp: no process killed
killall: vattery: no process killed
killall: powerapplet_tray: no process killed
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
[13379423750304:ERROR:extension_prefs.cc(734)] Bad or missing pref 'state' for extension 'hpibmhghjndideebpackbdlpncgkcppp'
[13379423750473:ERROR:extension_prefs.cc(734)] Bad or missing pref 'state' for extension 'lncjcfkpannmofmpgdfoonkniofdnaba'
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory
sh: /usr/local/pwidgets/widgets/scripts/PuppyName: No such file or directory

[rerwin]

playdayz,
Dalterton's diag files reveal that there is a bug in the determination of sound cards as being modems and not real sound cards. I have corrected that in the attached package. The fix was simple, as shown in the difference listing for pup_event_backend_modprobe:

Code: Select all

48,49c48,49
<    echo -e -n "snd-atiixp-modem\nsnd-intel8x0m\nsnd-via82xx-modem\n$NONAUDIOMODS" | grep -q -w "$dMODULE" \
<     && CNTSND=1 #110319 avoid 0 nonaudio cards
---
>    echo -e -n "snd-atiixp-modem\nsnd-intel8x0m\nsnd-via82xx-modem\n$NONAUDIOMODS" | sed 's/.*/&Z/' | grep -q -w "${dMODULE}Z" \
>     && CNTSND=1 #110319 avoid 0 nonaudio cards #110725

It was confusing snd-via82xx with snd-via82xx-modem. One more bug squashed.
Richard

[PaulBx1]

For what it's worth,here is part ofmy xerrs.log in 525:

WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
Warning: Only changing the first 5 of 12 buttons.
/usr/bin/jwm
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
EXIT="Exit on timeout"
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory

(seamonkey-bin:5565): Pango-WARNING **: libthai.so.0: cannot open shared object file: No such file or directory
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory

(seamonkey-bin:5565): Gdk-WARNING **: XID collision, trouble ahead

(seamonkey-bin:5565): Gdk-WARNING **: XID collision, trouble ahead

(seamonkey-bin:5565): Gdk-WARNING **: XID collision, trouble ahead

(seamonkey-bin:5565): Gdk-WARNING **: XID collision, trouble ahead

(seamonkey-bin:5565): Gdk-WARNING **: XID collision, trouble ahead

(seamonkey-bin:5565): Gdk-WARNING **: XID collision, trouble ahead

[PaulBx1]

Testing 266...

Booting my D510MO is broken again!

I did the same thing as before with 265: Created a 266 CD, booted it on the laptop, used Universal Installer to create a bootable flash drive, and attempted to boot that on the D510MO. The only difference is that I had previously used gparted to create a large ext2 partition on the flash drive and a small FAT32 partition. The ext2 is marked "boot" as before.

Symptom: gives the isolinux line (Peter Anvin et al) and hangs.

I compared my 265 flash drive with the 266 one. ldlinux.sys appears the same. However instead of having syslinux.cfg (as on 265) it has extlinux.conf instead. The two have identical contents though. I also noticed the USBFLASH file was missing. I copied it over from the 265 flash drive, and copied over syslinux.cfg too, but it didn't help.

Guess I will try re-doing it with UI again, dumping the extra partition, etc.

[rerwin]

All developers,

WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
Warning: Only changing the first 5 of 12 buttons.
/usr/bin/jwm
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
EXIT="Exit on timeout"

Note that there is no longer a file, modprobe.conf. Any reading of it will not find anything. To avoid the above "Deprecated" warnings, please review any code that might reference modprobe.conf. To read the replacement .conf files, substitute "`cat /etc/modprobe.d/*`" for modprobe.conf. To add to the replacement for modprobe.conf, write to a new .conf file, named to identify its creator, in /etc/modprobe.d/. (There are probably other techniques, but those are what I use.)

Note also that .conf files named "blacklist"(anything) will be removed at bootup. Names beginning with "modem_" are removed by pupdial's CHOOSE > ERASE function.

Please feel free to contact me about this, if in doubt about a substitution.
Richard

[rerwin]

zigbert,
I have been looking for clues about the various xerrs.log messages we are seeing. In the process, I have stumbled upon a possible pfind problem when I booted into 266 and, after a few minutes of inactivity, ran pfind to find text within files. Checking xerrs.log, I found this:

** ERROR **: GtkDialog: Could not find the dialog description in the environment variable 'MAIN_DIALOG'.
aborting...
/usr/local/pfind/pfind: line 438: 5888 Aborted gtkdialog3 is /usr/sbin/gtkdialog3
EXIT="Ready"

Now, while writing this message, the following has been added to the log (unrelated to pfind, I expect):

** (roxterm:8289): WARNING **: Failed to connect to session manager: SESSION_MANAGER environment variable not defined

I have 2 rox sessions going, for directories ~ and /tmp. Not sure who this goes to.
Richard

[rerwin]

playdayz,
While using XArchive to extract from a pmodemdiag tar.gz file, my xerrs.log file gets totally replaced by the single line:

extention tar.z ignored

It occurred after clicking on the "Extract" button, which pops up the "Extraction Directory" dialog window. It happened a second time while I was writing this message (with no interaction with the dialog).

Its listing of the directories and files inside the tar.gz file show none with names containing "tar.z" (because it was ignored, I suppose). But the contents do get extracted as expected. I tried "tar -xvf" on the same file -- it did not produce the "ignored" message in the console session, but (maybe coincidentally) the message appeared again in the log.
- I have quit XArchive and will let puppy sit for awhile with pfind displaying some found file names, to see if the message continues to be issued.
- Came back 1/2 hour later to find the log has been updated with the same single message.
- Closed the pfind window (X) and saw the log be updated again with same message. (Currently running: Geany, rox, urxvt, seamonkey browser)
- Waited a minute, checked log (in Geany) and same message updated (reloaded)
- Closed the 2 rox windows and waited a few minutes -- the message updated again.
- Closed urxvt and waited about 10 minutes -- message updated/reloaded.
- opened the file in nicoedit, which showed the same single line.
- Opened urxvt and entered "cat /tmp.xerrs.log" which showed the "ignored" line followed by many other lines (many "Failed to open VDPAU backend..." messages plus "(nicoedit:31319): GtkSourceView-CRITICAL **: gtk_source_language_manager_get_language: assertion `id != NULL' failed")

However, the disconcerting part is that the message wipes out the log. I am not sure what to do about this, but I wanted to get it into the record.

There are 2 postings about this from a while back:
- http://www.murga-linux.com/puppy/viewto ... 688#365688
- http://www.murga-linux.com/puppy/viewto ... 681#461681

I have to conclude that there is something wrong about the "ignored" message that causes the editors to think that message is the end of the file, although "cat" shows added lines. the "ignored message appears updated when additional lines are appended, but do not appear in the editors' window. Maybe that nicoedit message is a clue. It does seem that the programs I quit are not the source of the problem. Now, to exit seamonkey and monitor only with urxvt, watching the "ls -l /tmp/xerrs.log" command show the logs timestamp changing. Fun.
Richard

[PaulBx1]

1) A really small item. The first thing a person sees is "Personalize Settings". When you exit, a little window comes up saying "Nothing is changed." The header for that window is "Pers...tings" because the window has been made so short. Normally I wouldn't care about such things but since it is the very first thing people see, it looks a bit unpolished and the window should be lengthened.

2) I tried all sorts of things getting my new flash drive to boot the D510MO (it boots the laptop just fine). Nothing seemed to work, not different mbrs, etc. So finally I booted the flash drive that does work (which had luci265), in sda1, put the new drive in sdb, and did "dd if=/dev/sda of=/dev/sdb", and that DID work. So it's not the flash drive hardware that is the problem. Something either in gparted or universal installer is broken, at least for the D510MO.

3) I noticed when messing with this the mbr window of the UI says there is in /usr/lib/syslinux the mbr's mentioned in the list (sys-nopart.mbr, mbr.bin, mbrfat.bin and spb2_mbr.bin) and that dd could be used outside the UI to try installing them. Problem is, only mbr.bin and mbrfat.bin from that list are in that directory. Also there is one not mentioned in the list, gptmbr.bin. The other strange thing about these mbrs is that they are not 446 bytes long as one would expect.

[Béèm]

Thanks rerwin to raise an issue with xerrs.log
After a couple of hours mine grows to 2.5MB. I am in spup 311
When I try to open it, geany says it's an invalid file type and thinks its a binary file.
When I do a tail I get indeed clear error messages, sometimes some 200 lines the same message.
I wonder if those messages are really in that quantity in the file.

So maybe considering 266 as well as 311 given strange situations, I wonder if there isn't a more upstream cause and I am thinking of woof, which is the base for developments like lucid and spup.

[jpeps]

Thanks rerwin to raise an issue with xerrs.log
After a couple of hours mine grows to 2.5MB. I am in spup 311
When I try to open it, geany says it's an invalid file type and thinks its a binary file.

...maybe it's transforming itself into a self-destructive app. At 3 MB, it will probably wipe out your hard drive.


Meanwhile, here's a weight reduction script: (only 4K)

Code: Select all

#!/bin/sh
sed -i '/VDPAU/d' /tmp/xerrs.log

[rerwin]

playdayz,
I think I have found the source of the bizarre one-line message and at least one way to solve it!

While using XArchive to extract from a pmodemdiag tar.gz file, my xerrs.log file gets totally replaced by the single line:
Quote:
extention tar.z ignored

There is a set of "wrapper" scripts associated with XArchive, in /usr/local/lib/xarchive/wrappers/. The one for tar.gz files appears to be tar-wrap.sh. It sends messages to the stderr by such commands as:

Code: Select all

echo extention $EXTS ignored >/dev/stderr

That would appear to start a new stderr file, unless there are ways to control that with bash options. What I see is that only the last of at least 2 messages ends up in xerrs.log.

As an experiment, I replaced all of the "> /dev/stderr" strings with "1>&2". As a result, attempting to extract the same file as before does not damage the log and shows both messages:

compress and uncompress not found
extention tar.z ignored
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory

That last line (Failed...) continued to be visible after the "ignored" message, as it continued to fill the log.

Since the header area of tar-wrap.sh contains:

# modified by technosaurus for puppy 4.4a
# added lzma and xz and changed --use-compress-program={progs} -{ajJzZ}

I would like to hear from technosaurus before modifying all of the -wrap.sh files. Pfind shows the following files as containing the word, extention, probably also the ">/dev/stderr":

• /usr/local/lib/xarchive/wrappers/7za-wrap.sh
  /usr/local/lib/xarchive/wrappers/deb-wrap.sh
  /usr/local/lib/xarchive/wrappers/jar-wrap.sh
  /usr/local/lib/xarchive/wrappers/rar-wrap.sh
  /usr/local/lib/xarchive/wrappers/rpm-wrap.sh
  /usr/local/lib/xarchive/wrappers/tar-wrap.sh
  /usr/local/lib/xarchive/wrappers/xpi-wrap.sh
  /usr/local/lib/xarchive/wrappers/xz-wrap.sh
  /usr/local/lib/xarchive/wrappers/zip-wrap.sh

I am willing to make the changes, but would like direction to do so or advice on a simpler way to solve the issue.
Richard

[Snail]

Rox Right Click options, tailored to the mime-type is working in 266. It may have been working earlier but I was mislead by clicking on a mime type that had no type-specific option defined, e.g. a directory.

I may be dense, in fact I am sure I am, but surely having a great list of totally irrelevant applications popping up when you click open with is both useless and confusing. The current set-up in Lucid is the antithesis of user-friendly.

There is no application that is relevant to all mime-types, or even to most of them. The only one that comes close is the text-handler, which has its very own special right click menu item. (“Open as text