Quirky 018 feedback

[Sit Heel Speak]

processing faad_2.7-4_i386.deb
processing libfaad-dev_2.7-4_i386.deb
Processing libfaad0
(error message about the correct libfaad .pet not being present in packages-pet)

Wow. 2createpackages even discovered that I had made a .pet package of libfaad0, when the version specified in DISTRO-PKGS_SPECS-ubuntu-lucid is libfaad2...

...and then, after I control-c'ed out of 2createpackages and corrected the libfaad (faad) entry in DISTRO-PKGS_SPECS-ubuntu-lucid,... with bated breath I tried starting 1download again, and it actually went out and *just* downloaded the single missing libfaad2_2.7-4_i386.deb package!...

!!! I am IMPRESSED !!!

Hoo man-o-man this thing is built like a brick ...table lamp, isn't it!!!

[Sit Heel Speak]

Suggestion:

Have 0setup do the same syntax-check of PKGS_SPECS_TABLE that 2createpackages does near its beginning.

This would have saved me quite a bit of eyestrain late last night, when I neglected to place a '|' after the yes in the entry for the libxtrap .pet I made, and thus kept getting the

FAIL: exe
FAIL: dev
FAIL: doc
FAIL: nls

mystery sequence in 0setup.

The string 'yeslibxtrap' is very hard to distinguish among a long list of similars from 'yes|libxtrap'...whereas the syntax check, if it were placed prior to commencement of the check for nonexistent packages, would have spared me having to closely examine the entirety of PKGS_SPECS_TABLE...

[stu90]

Hello Barryk,

Wary19: Touchpad tapping/ double tap works from the get go however there is no touchpad scrolling, i've tried some different xorg.conf configurations but no joy yet . If i remember right Quirky13 double tap /scrolling worked ok .

p.s great wary wallpaper choice

cheers.

[Sit Heel Speak]

Another suggestion:

For cases like in my second post above, where 2createpackages errors-out due to incorrect library version specified in DISTRO_PKGS_SPECS-ubuntu-lucid (e.g. libfaad0 where libfaad2 is specified in Packages-ubuntu-lucid-universe/multiverse/main) and so the user goes back into DISTRO_PKGS_SPECS and corrects the libfaad(n) entry to match the Packages-ubuntu-lucid-universe/mulltiverse/main specified version...

...it would be nice if 2createpackages were to give the user the option to resume from where left off, rather than waste half an hour to three hours starting from the top and doing the whole creation process over again, or having to go back after finished and rebuild singly the error'ed-out packages.

I know, I know, some people want instant gratification...

But when you're this close to perfection, it's hard not to ask for it...

[JustGreg]

I did a frugal Wary 019 install to my VFAT USB hard drive. It started and work well on my Acer Aspire Revo. We still need the Nvidia video driver. Hopefully Gray can do an update for the new kernel. Thanks in advance for any help on this one.

I also checked PupRadio. KNIK, which is a MMS station works now. It did not work in Quirky 018. However, the Gulch receiver still does not work. It appears that CFGP is no longer available. I get a failure to connect on that URL. The Gulch URL connects, but no audio output even though data is being receiver. I tried changing the cache size and mixer selection (oss or alsa) without any luck.

I would like to try the present 4.3.1 Gxine pet in Wary with the Gulch URL. But, I am not sure if the pet will work properly with the new kernel version.

It and Quirky work well with my Acer Aspire One net book.

[rjbrewer]

Here is a "Gulch" stream I found in my bookmarks.
Works fine regular stream or win-amp stream using
gxine on my 4.1.2 install.

http://shortwavepirate.info/pw/wordpress/the-gulch/

Cfgp.........doesn't need a player.

http://radiotime.com/station/s_7608/Rock_977.aspx

I tried to install vlc or gxine to quirky; couldn't get it to work.

[LoneRifle]

Wary 019: Xorg vesa driver seems to be problematic, see quote. Also unable to power off automatically. Again, this is tested on my non-Norhtec Edubook, so other Edubook users may have different results..

X: symbol lookup error: /usr/X11R7/lib/xorg/modules/drivers//vesa_drv.so: undefined symbol: xf86GTFMode

[nooby]

http://radiotime.com/station/s_7608/Rock_977.aspx
That one and others at radiotime works for me using q18 but I have installed mplayer 3.85 something so that maybe take care of such?

[rjbrewer]

http://radiotime.com/station/s_7608/Rock_977.aspx
That one and others at radiotime works for me using q18 but I have installed mplayer 3.85 something so that maybe take care of such?

Installed Muppymplayer and it will do that http stream from the link,
but not from pup-radio-telly.
Still not possible to enable mms.

[upnorth]

The website's picture was replaced with a thumbnail image of the desktop that updates, but the tab preview thumbnail image shows the sites intended picture.:

I had noscript activated too and privoxy on full choke so I don't think it was a script doing it.

This seamonkey is mozilla's build, and I've only seen this happen on one site.

from about:buildconfig
http://hg.mozilla.org/releases/mozilla- ... 07a617e5a5

Solved: After killing conky(1.7.2) and restarting conky the problem is gone. Probably the pseudo transparency data getting mixed up with seamonkey somehow.

[upnorth]

Here is how to turn off the tab thumbnail preview if anyone needs to::

browser.tabs.tooltippreview.enable;false

This preference used to be somewhere in menu but I couldn't find it. So used about:config to change.

[JustGreg]

I tried to get the NVIDIA video driver for Wary. I down loaded the latest version (190.36.15) for Linux. I found one needs to have the devxx.sfs for it. It needs several binary utilities. I thought it was going to work, but, it needs the kernel source to built the driver. Oh well, I need to think about this and do some research. I reached the limit of my knowledge.

OK, I found the sfs file with the kernel sources. The process went a bit farther, but still failed. This is the error message from the log:

If you are using a Linux 2.6 kernel, please make sure
you have configured kernel sources matching your kernel
installed on your system. If you specified a separate
output directory using either the "KBUILD_OUTPUT" or
the "O" KBUILD parameter, make sure to specify this
directory with the SYSOUT environment variable or with
the equivalent nvidia-installer command line option.

Depending on where and how the kernel sources (or the
kernel headers) were installed, you may need to specify
their location with the SYSSRC environment variable or
the equivalent nvidia-installer command line option.

I did also find that you need to do the building from the command line. The Xserver can not be running. Any help or suggestions will be appreciated. I am definitely "out of my league" with this one. Thank you in advance for any help.

Yes, I did find this post:
http://www.murga-linux.com/puppy/viewtopic.php?p=365818

I am following its directions.

[Hesse James]

Good morning JustGreg
I always execute the installer according to this which is identical to yours:
http://www.goingnuts.dk/mms2p412.asp#NVIDIA

Unfortunately I get that attached error message for all WOOF based Puplets as described in this Forum a page earlier (except Iguleders approad). Issue reported to Playdays for Lucid003.

Do you observe the same error mesage ?
Greetings

[nooby]

To all of you trying to get the nvidia going. Much appreciated.

My nvidia seems to work in Vesa but not in xorg set up. Video get choppy and jerky instead of having glitches which I prefer to choppy and jerky which makes me seasick looking at them.

Could there be somebody deciding they prefer the choppy and jerky over glitches and that we will get stuck with that preference for all future???

Me really worried that this is decided way high up in linux foundation something?

Could anyone give a hint if the choppy and jerkyness is an error that crept in or a deliberate design feature that somebody decided is better than glitches.

Glitches
1. A minor malfunction, mishap, or technical problem; a snag: a computer glitch; a navigational glitch; a glitch in the negotiations.
2. A false or spurious electronic signal caused by a brief, unwanted surge of electric power.

a glitch looks like a super fast narrow line that appear randomly horisontally on the screen

while a choppy or jerky is the whole movement of a person goes from one position to another in a delayed smoothed out jerking move as if they have some spastic problem moving or are playing Robots.

we are at least three members of this forum having this problem. it only happens with Quirky and Dpup and Upup and one more.

What in Linux land is going on?

[jrb]

Hi, Has anyone else noted that Gnumeric crashes when you go to Format-Cells?

Here are the error messages:

Code: Select all

# gnumeric

(gnumeric:9513): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated

(gnumeric:9513): libglade-WARNING **: could not find glade file '/usr/share/goffice/0.6.6/glade/go-rotation-sel.glade'

(gnumeric:9513): libglade-WARNING **: could not find glade file '/usr/share/goffice/0.6.6/glade/go-format-sel.glade'

** (gnumeric:9513): CRITICAL **: go_combo_text_set_text: assertion `IS_GO_COMBO_TEXT (ct)' failed

(gnumeric:9513): Gtk-CRITICAL **: gtk_tree_view_get_selection: assertion `GTK_IS_TREE_VIEW (tree_view)' failed

(gnumeric:9513): Gtk-CRITICAL **: gtk_tree_selection_select_path: assertion `GTK_IS_TREE_SELECTION (selection)' failed

(gnumeric:9513): GLib-GObject-WARNING **: gsignal.c:2310: instance `(nil)' has no handler with id `0'

(gnumeric:9513): Gtk-CRITICAL **: gtk_entry_set_text: assertion `GTK_IS_ENTRY (entry)' failed

(gnumeric:9513): GLib-GObject-WARNING **: gsignal.c:2352: instance `(nil)' has no handler with id `0'
Segmentation fault

All the formatting buttons on the toolbar work but not the menu. I was trying to change the difference between two dates into plain numbers (of days) but couldn't in gnumeric. Had to use Planmaker instead.

BTW, Barry, Great fix on Abiword and the .docx files. Have installed the .pet and am using it at work.

Thanks, J

[JustGreg]

Hesse James,

No my error is different. The NVIDIA installer is complaining about the Kbuild directory for the kernel with me. If I got your error message, I would press the No button to see if it would continue and what happens. Your message is complaining about the use of GCC, which should not be fatal. Thank you for the URL. I will have to look at it.

Thank you, Hesse James for the URL,
http://www.goingnuts.dk/mms2p412.asp#NVIDIA
It has good information I have been using VESA as the driver. I will have to try Xorg and sees what happens.

I tried the instructions of the above URL and got the same error message. This happens every so often. Time, to re-think the approach.

[Sit Heel Speak]

From the pre-built wary-019 .iso, mkdir and xorgconfig are missing.

Earlier I found that modprobe and lsmod were missing, but it was very late, the fix was trivial (copy them in from another Puppy), didn't take notes, so not sure if that was on wary or some other new woofbuild.

[`f00]

___q018 update100416/18___
Oh %#&@
Had to hardoff in q013 while testing jwm2-489-w1 dotpet/extract (an exit to prompt gave a nonresponsive cursorblink topleft, no kybd response, nada) .. on getting to a prompt (somewhere in the xorg after the initial dialogue, I think) gave the reboot cmd and it offered usual choices .. somewhere in there it did a fs3 check and wiped out the quirkysave-eighteen.3fs savefile (yes, again ) as well as quirky_devx_010.sfs (hunh ) .. it seems the checksystem may bite you on a hardoff even if you make what seems like reasonable choices.

So perhaps until the checksystem is completely understood..
a) always make backups of savefiles on an external partition
b) after a hardoff, boot a pre-q010 quirky and try to guess at how to fix things before trying to use a quirky with a checksystem - optionally, make backup(s) of possibly corrupt savefile(s) since they may be better than nothing
c) use multisession liveCD

100418
For the third time a savefile for q018 (this one's a 2fs - noticed in other pups that a 3fs savefile may not be clickmountable.. there are a few occasions when it's easier for me to do 'fixes' outside of a running pup and possibly why this is the third savefile ).

Outside of that personal observation, I like q018. Xorg seems to be a bit easier to deal with (not saying much, compared to w019 ) and offers a few tweaks for my particular twin-ati so that's one.

Another is that conky (1.7.11) works in q018 with only a minor libset (xcb-something) added - this may be due to the older pixman (0.16.2), rather than w019's more up-to-date one. Jwm is better icon-trans-wise with the 489 binary from the w dotpet.

Minor personal issue with a slapped-in jwm (either q018 or w019) and plogout. Plogout works fine in other wms (uncommented restartwm's final 3 lines to ease a button-switch without having to 'kick' it with ctrl+alt+bs), but in jwm the murgaLua window doesn't show? Put in a wmexit on tray and jwm's rootmenu so no biggie. Just puzzled why window doesn't show - if ctrl+alt+bs always dropped out of X to prompt.. yah, fussing with console(s) can be surprising occasionally for me (and why I generally leave kybd specializations on 'default' unless there's a real good reason not to).

___w019___
100416-17 w019 liveCDmulti
The dialogues on xorg need work - it took some few hardoffs and lucky guesses to get to x (plus disregarding bad or 'odd' info as reported in the final dialogues) but it did actually get the correct bus-card-display up (instead of the switched-off-in-BIOS set).

About time tabview got fixed in pmount.

Smooth gradations look nice .. in 24bit.

1st savedir (kind of a relief to get back to multisession after losing q018's savefile - yah, backup), some oddness with conky (not sure what, it may be newer version of pixman or xorg build) not displaying. Openbox still good, runs well without roxpin or fbpanel (eventmanager all unticked).

100418
It kind of grows on me (even with no conky), not that hard to get pfbpanel to liking. It (fbpanel) is a bit strange in wmx7, window decor is slightly different 'rules' there (for instance, retrovol has a 'window' even without a panel or tray up). The new display for freememapplet_tray is nice and simple, no squinting at numbers for a quick glance of a 'ballpark' of what you got to work with.

w019 does seem a bit quicker to load some apps (or it might be difference in liveCDmulti as opposed to the 'on-stick' of q018 - usb jacks on the tower are older-generation so transfer is a bit not quite what it could be).

100420 - conky alternative(s) for w019
It may just be me, but having some sysinfo clearly visible as a pseudo-transparent backwindow is a thing I've liked about torsmo/conky since meanpup (then there came the pwidget-system in p42x ).

a) use a console/htop - probably the most efficient
b) gkrellm - I'm not real familiar with gkrellm, but ttuuxxx's fairly recent gkrellm-2.3.2 dotpet works nicely in w019 and has lots of features and decent local docs ( "man gkrellm" does the usual attempt to connect to an online page rather than bring up the local dot1 - no biggie, gk's info tabs are decent and I can wade thru the dot1 if necessary for those little extras).

Do racing aerobatic planes have quirky or wary tails?

[JustGreg]

I tried Quirky 018 with the NVidia official driver. Same problem and same error. I noticed that Quirky Pets listed this driver:
xf86-video-nv-2.1.16-q1.pet

Is this the correct driver for Quirky 018 and the NVidia hardware. There are others, but, they have 7.3 in the name, which is the version of xorg that Wary 019 uses. I have tried xf86-video-nv-2.1.16-q1.pet, but the xserver refuses to start.. It seems no matter what I try, the only thing that will work is xorg Vesa driver.

The Vesa driver would be fine, if it supported the resolution of 1366 by 768. I am tried to edit xorg.conf to see if I can get the 1366 by 768 by setting the screen section resolution to 1366 by 768. It did not work.

Any thoughts, suggestions or help would be appreciated. Thank you in advance.

[Hesse James]

Good morning JustGreg
NV and Nouveau-drivers are both open source more-or-less reengineered drivers for Nvidia Hardware (no VDPAU acceleration which is important for me). Tested both of them on diverse Puplets but I wasn't successful at all. ->Risky

Again Closed Source driver: As I wrote previously a continuation after my first error message depends on the used Puplet
1.) UPUP, DPUP: possible but crash after switching to 24bits
2.) Lucid and Quirky: no continuation possible (haven't tested Lucid-8 so far)

Concerning your installation attempts: did you reboot after SFS activation of the devx-development system ? I think I have seen your error message before... when I once forgot to reboot the machine.

There is a alternative description of the installation process
http://www.murga-linux.com/puppy/viewtopic.php?t=47049
I found it recently. It was written by Iguleder who also released some early Woof based Puplets.
http://www.murga-linux.com/puppy/viewtopic.php?t=53769
Could you please give it a try in combination with the NVIDIA installer? This worked for me but wasn't a real alternative to Lucid or Quirky.
Good luck.