Page 8 of 19

Posted: Sun 07 Apr 2013, 05:17
by pemasu
James C. Thank you of the information. At least one workaround has been reported.

Posted: Sun 07 Apr 2013, 07:01
by pemasu
tomo3 posted latest abiword and gnumeric pets. If someone, more experienced abiword and gnumeric user has tested them, he could post feedback.
http://www.murga-linux.com/puppy/viewto ... 758#696758

They are ok as installed pets. However the problem with error messages and abiword preferences crash goes to the abiword woof template.

I tested now strace abiword. Great bug hunter and straight in devx sfs.

strace abiword and then choose preferences and nice crash, heh.
open("/usr/share/abiword-2.9/ui/ap_UnixDialog_Options.ui", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)

Haa, reference found. Okay...what package is behind that file. Wild guess....abiword-common. Yeah, that it is. Now....why does the files are not found. Haa No 2. Woof abiword template does not include it.

Okay...lets copy that /usr/share/abiword-2.9.2/ui/* files.
Hmm....no crash....okay...lets make bug fix pet and hope that others could confirm the fix...or reject it. And post to the Barrys blog.

Please test this bug fix pet with Abiword and especially preferences.
If it work also with other Abiword users....I think that woof template tuning is the solution...okay I can add this fix as pet in to the woof and it will added that way also. But straight woof solution is always better.

Posted: Sun 07 Apr 2013, 07:31
by pemasu
I decided to check if Gnumeric has easy fix with strace gnumeric also. No, it didnt. It just registers same errors as console launching.

But....probably it is missing something. So...raw deduction to the work.
Hmm....gnumeric-common has schemas files....and they are the real worm hole in these new Ubuntus.
Lets check gnumeric processsed package in woof, yeah...they are not found.

Installing gnumeric-common from PPM fixes the error messages. What it did, it installed those missing schemas files and also run glib-compile-schemas which is needed for them to function. The compiled binary data file update is mandatory, just installing those files is not enough.

So...I created a pet with those schemas files in /usr/share/glib-2.0/schemas and pinstall.sh which launches glib-compile-schemas /usr/share/glib-2.0/schemas and produces updated gschemas.compiled binary data file.

This should fix the gnumeric initial error messages when lauched in console. More errors might be found later....

Eh.....post to the Barrys blog....

Elaborated....posts...sure.....I should clean the house today....I try to avoid the starting by doing something other useful....

Posted: Tue 09 Apr 2013, 09:55
by anikin
Hi pemasu,

A quick and weird question: how devx.sfs is built?
Do you do it manually for every release, or is it a woof job?

Thank you in advance

Posted: Tue 09 Apr 2013, 12:43
by pemasu
Anikin. It is woof thing. The included stuff has been determined by DISTRO_PKGS_SPECS file. For instance:

yes|gcc_dev|gcc-4.6-base,gcc,gcc-4.6,g++,g++-4.6,cpp,cpp-4.6|exe>dev,dev,doc,nls
meas that everything has been transferred to the devx sfs

In every package which has development files like headers or *.a or *.la files, they are included in devx sfs, if there is dev definition in DISTRO_PKGS_SPECS:
yes|gtk+|libgtk2.0-0,libgtk2.0-dev|exe,dev,doc,nls
for example...

3builddistro script in woof handles the devx sfs creation automatically.

Posted: Tue 09 Apr 2013, 14:51
by anikin
OK, woof builds it. I though as much, but wanted to be sure. A practical question now and maybe a suggestion for woof/devx improvement. I found out that "Make" in this devx is a bit outdated - 3.81, while the currently available version is 3.82.
make-3.81.tar.gz 01-Apr-2006 01:48 1.5M
make-3.82.tar.gz 28-Jul-2010 01:58 1.6M
http://ftp.gnu.org/gnu/make/

Unless it's an oversight and Barry has a reason to keep version 3.81, perhaps he should be alerted to this version lag?

And the question itself: if I compile the new version, and edit the SFS accordingly, will it work?

Thank you in advance.

Calibre tested

Posted: Tue 09 Apr 2013, 20:19
by josepinto
Hi,

I installed Calibre and all dependencies but its not working.

Simlinks necessary?

An alternative to install so many dependencies would be to group all Qt packages in a sfs.

José Pinto

Re: Calibre tested

Posted: Wed 10 Apr 2013, 01:22
by tlchost
josepinto wrote:Hi,

I installed Calibre and all dependencies but its not working.
I simply extract it to /mnt/home into /mnt/home/calibre click on the calibre file in /mnt/home/calibre ... no need to install anything else.

Thom

Posted: Wed 10 Apr 2013, 04:53
by pemasu
If I remember right, Calibre needed python-sip .deb from PPM. It wasnt listed as dependency, but it did the trick for me.

Testing more apps

Posted: Wed 10 Apr 2013, 09:25
by josepinto
1) Mcomix

Installed from ubuntu with all dependencies.

Ok.

2) Money Manager EX

Downloaded raring package from money manager ex PPA
https://launchpad.net/~mmex-developers/ ... mex-stable

and installed libwxgtk 2.8.0 deb package and dependencies forum Ubuntu

OK

3) Thunderbird

Installed from Ubuntu and copied profile form Windons instalation.

OK

4) Calibre
Extracted calibre-0.9.26-x86_64.tar.bz2 in folder created in NTFS partition.
Clicked on Calibre.
Copied config files form Calibre installed in Windows.

OK

5) Getlibreoffice
Installed pet
Downloaded Libreoffice 4.02. and Portuguese locale. Created SFS.

OK

6)SFS-Unload
Load Libre Office SFS created with Getlibreoffice.
Unload same SFS
OK. No more crashes on Unload :D

7)

Imagination
Installed sox-14.2.0-with-deps.pet
Installed imagination-3.0b.pet

Seehttp://www.murga-linux.com/puppy/viewtopic.php ... 85&t=82575

OK

José Pinto

savage video-card doesn't work

Posted: Wed 10 Apr 2013, 15:50
by rodin.s
Savage video-driver doesn't work for me anymore. It worked in latest Upup Precise. I have some distorted picture. Managed to switch to vesa by editing xorg.conf. Posting from it now. Maybe my card is too old for this kernel.

Posted: Wed 10 Apr 2013, 17:57
by pemasu
rodin.s. I would need /var/log/Xorg.0.log after failed xwin X start using savage_drv.so
dmesg output would also be useful.

I would like to see if there is something about savage.ko kernel module or savage_drv.so failure in those logs.

I have both of them included in the build...so they should be in use...when you boot without xorg.conf modification. Something clearly is not ok for you.

savage video-card doesn't work

Posted: Wed 10 Apr 2013, 21:13
by rodin.s
I have made a screenshot. But it's much worse than it is on screenshot and pdiag might have all needed information.

Posted: Wed 10 Apr 2013, 21:44
by pemasu
rodin.s
Pdiag does not collect Xorg.0.log. It possibly contains most useful information, maybe you could post it.

I noticed that you dont have drm or savage kernel modules loaded.
Do you have them loaded in Puppies where your savage card works ok.

Also....libgl1-mesa-dri does not provide savage_dri.so anymore so no 3D acceleration from that part also. Mesa-9.0.3 does not seem to include it anymore.

Tested

Posted: Thu 11 Apr 2013, 00:17
by darry1966
Machine AMD Sempron 3000+

Ram 1G

boots nicely and has correct screen setting.

Only thing wrong is with my p/s2 mouse which shows weird mouse pointer on screen. sound works.

savage card

Posted: Thu 11 Apr 2013, 07:53
by rodin.s
I have uploaded Xorg log to my previous post and I have savage and drm modules loaded for example in Precise-5.4.2

Code: Select all

# lsmod | grep savage
savage                 20554  1 
drm                   121458  2 savage

Posted: Thu 11 Apr 2013, 13:40
by pemasu
rodin.s. What happens if you logout to the console state and load manually drm and savage.
modprobe drm
modprobe savage
and then start X again.

savage card

Posted: Thu 11 Apr 2013, 14:24
by rodin.s
Almost same thing.

Raring 3.8.4.2

Posted: Thu 11 Apr 2013, 21:23
by sszindian
Raring-3.8.4.2

Everything tested appears to work well. Graphics are very nice, could be the best of any puppy so far? Fonts are good and acceptable but I had to use the 108 global font size to make them that way on a 1400x900 screen.

One issue (and this is not just for Rearing but also latest Precise, Racy and Slacko) Occasional WiFi 'drops'. Wheezy is the only puppy that I never ever had a drop with (so far).

While this only affects WiFi users, it is an issue as once you get a drop, you're finished with Internet... it just won't re-config... and you can't shut puppy down without a cold- push and hold in the button (and that's for all the above mentioned puppy's.)

It would be nice if WiFi could restart itself after a drop, (some other distro's do have that feature.)

Just my 2-cents...

>>>---Indian------>

Posted: Fri 12 Apr 2013, 12:53
by anikin
Further to make 3.82 version, I did some research but Google didn't have a clear and simple answer for me. All I could find was that this latest version carried 83 bug fixes, which let me cautiously presume, that I'd be good to go with the upgrade. I compiled the new version from source and put it into devx. But since it was compiled with the "old" make, I recompiled it once again with the new one and put finally into devx. And declared the case solved and closed. I was reading this article: http://users.wowway.com/~zlinuxman/Kernel.htm and quite unexpectedly an answer popped up:
Step 6: Install kernel-package

This is an unofficial patch: it is not provided by or endorsed by the upstream author or the Debian package maintainer. Also please note that kernel-package version 12.036+nmu1 and earlier releases are not compatible with "make" version 3.82; so don't install "make" version 3.82 or later. These problems are fixed in version 12.036+nmu2. However, if your kernel source code is version 3.3.x or later, even kernel-package version 12.036+nmu2 will need a patch, particularly if CONFIG_LGUEST is set. The patch is available in the problem log for Debian Bug Report 663474 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663474. Version 12.036+nmu3 fixes this problem: no patch is required.

Evidently, ubuntu raring has an old version of make for backward compatibility, which leads me to think: compatibility at the price of 83 bug fixes?