Fatdog64-520RC2

[tony]

Hi,

just installed scribus from package manager.

libQtGui.so.4 => not found
libQtXml.so.4 => not found
libQtNetwork.so.4 => not found
libQtCore.so.4 => not found
libpython2.6.so.1.0 => not found

Anyone know where these libs can be found?

Regards Tony

[jamesbond]

Hi tony,
The first four - install qt4 from PPM.
The last one - install python also from PPM.
cheers!

[kirk]

Hi tony,
The first four - install qt4 from PPM.
The last one - install python also from PPM.
cheers!

And reboot

[tony]

Hi kirk and jamesbond,

Thanks for the info, scribus is now up and running.

I'm getting to like this 64 bit pup, no problems on my thinkpad T61.

Hope we do not overwork you.

Regards Tony

[James C]

First, I went ahead and did a frugal install of RC2 on the dual-core reported on the first page of the thread.... been working fine and no real problems to speak of.
http://www.murga-linux.com/puppy/viewto ... 992#555992
Second,RC2 live multi-session dvd on a different box.Same result,everything working on initial boot and nothing really bad to report yet.Looks good.

-Computer-
Processor : 4x AMD Athlon(tm) II X4 620 Processor
Memory : 3796MB (288MB used)
Machine Type : Physical machine
Operating System : Puppy Linux 0.50
User Name : root (root)
Date/Time : Sat 03 Sep 2011 01:24:44 AM GMT+5
-Display-
Resolution : 1366x768 pixels
OpenGL Renderer : Software Rasterizer
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel - HDA NVidia
Audio Adapter : PC-Speaker - pcsp


-Version-
Kernel : Linux 3.0.3 (x86_64)
Version : #1 SMP Thu Aug 18 22:58:50 GMT+5 2011
C Library : GNU C Library version 2.11.1 (stable)
Distribution : Puppy Linux 0.50

[Fishy]

Tried to install on a new barebones system for my nephew. Seemed to load properly but went black screen. so I a cannot get or give anymore information. Regular puppy versions tend to lock up shortly after starting to use them.

The kit came with 8 gig of memory. Windows7 - 64 works perfectly but they would like to have puppy back.

Is the problem that Fdog automatically selects video properties therefore not allowing repair is selction is wrong?

Anybody having similar issues with the new AMD processor?

[Fishy]

Tried to install Calibre in Fatdog and got the following message in terminal. I have installed the python pet required to install it in puppy 5.2.8.

I do have the devx.sfs installed. Fdog otherwise is working well.

Thanks

[gcmartin]

... Gcmartin, not that's not a font problem, more like incorrect configuration of pango/gtk, but I never have that kind of error before. Have you check your ISO's md5sum? ... !

Yes, the md5 and ISO match. I am running from a Live media with a single save-session. The only PET in the save session is the updated "report-video-glx" tool for reporting to this thread. I've wait for next release.

Iwait for the next release, if you feel this may be an anomaly that may be result of some hardware mis-driven by the application. Just seemed like a problem from last year.

Hope this helps

[jamesbond]

Tried to install on a new barebones system for my nephew. Seemed to load properly but went black screen. so I a cannot get or give anymore information. Regular puppy versions tend to lock up shortly after starting to use them.

The kit came with 8 gig of memory. Windows7 - 64 works perfectly but they would like to have puppy back.

Is the problem that Fdog automatically selects video properties therefore not allowing repair is selction is wrong?

Anybody having similar issues with the new AMD processor?

Fishy,
Try booting with "pfix=vesa". If this still fails, try booting with both "pfix=vesa" and "nomodeset".

cheers!

[jamesbond]

Tried to install Calibre in Fatdog and got the following message in terminal. I have installed the python pet required to install it in puppy 5.2.8.

I do have the devx.sfs installed. Fdog otherwise is working well.

Thanks

libdbus is available on Fatdog PPM.

[jamesbond]

... Gcmartin, not that's not a font problem, more like incorrect configuration of pango/gtk, but I never have that kind of error before. Have you check your ISO's md5sum? ... !

Yes, the md5 and ISO match. I am running from a Live media with a single save-session. The only PET in the save session is the updated "report-video-glx" tool for reporting to this thread. I've wait for next release.

Iwait for the next release, if you feel this may be an anomaly that may be result of some hardware mis-driven by the application. Just seemed like a problem from last year.

Hope this helps

No, this doesn't seem to be hardware problem, more like software problem. Try running abiword from terminal and see if you get any error messages that we can decipher

[rcrsn51]

I am running from a Live media with a single save-session.

Have you tried booting with no save sessions? I cannot reproduce your problem.

[Barkingmad]

Hello

jamesbond -- this might be a bit late as I see you have the final release out but as a follow up to

Anyway, I've compiled the latest jwm for you, it's located here: http://distro.ibiblio.org/pub/linux/dis ... x86_64.pet, if you can tell me whether this fixes most of your problem (or not), that would be good.

Still won't play that VOB but that happened under both WM anyway. Points: If I dismiss the report of "plugin failed to open" there is another error about permissions so you must be right -- is this something I could fix with the file or what? Another VOB ripped from a different disk but with the same ripper will play with no trouble.


Xine Open > File menu now works.

Mplayer GUI still freezes X. As you suggested mplayer runs from a terminal with no graphical controls.

Thanks again for all your work.

BTW is there a list anywhere of changes from RC2 to final relese so I could see if it's worth the download?

Will

[jamesbond]

Still won't play that VOB but that happened under both WM anyway. Points: If I dismiss the report of "plugin failed to open" there is another error about permissions so you must be right -- is this something I could fix with the file or what? Another VOB ripped from a different disk but with the same ripper will play with no trouble.

The permission problem is a known problem - supposed to be fixed a couple of while ago but didn't because we forgot about it Now that we have a proper bug-tracker, we should remember better.
The fix - edit /usr/local/bin/defaultmediaplayer, change "xine.sh" with "xine" and you're good to go.

Xine Open > File menu now works.

Good - that's what the new jwm is for.

Mplayer GUI still freezes X. As you suggested mplayer runs from a terminal with no graphical controls.

Didn't test this yet, so can't comment, but thanks for testing.

BTW is there a list anywhere of changes from RC2 to final relese so I could see if it's worth the download?

Will

Major update: fotoxx (you need to see it to believe it), latest gnumeric, and jwm-500 and a few libraries, plus other fixes video/sound related fixes.

[Barkingmad]

Thanks James for replying.

The fix for Xine sounds easy enough I'll do that.

BTW is there a list anywhere of changes from RC2 to final relese so I could see if it's worth the download?

Will

Major update: fotoxx (you need to see it to believe it), latest gnumeric, and jwm-500 and a few libraries, plus other fixes video/sound related fixes.

Right, that sounds worth having -- I'll have to see how I'm doing for download allowance this month though before trying it.

Thanks again for the developement.
Will

[8-bit]

I have a Toshiba Satellite laptop 64 bit system.
Hardinfo shows my wireless device as a Realtek rtl8192se rev B
But when I use the connection wizard and load that module, it tells me no new interfaces found.
I also inadvertently blacklisted my wired port driver, but did not save settings so I guess I am safe there.
I booted from CD with fatdog pfix=ram.

But to get on to my question.
Has the rtl8192se wireless driver been tested?
What can I do to try to set it up manually?

I know not to try to use a 32bit system driver.
I posted this in the wrong place as I have Fatdog 64bit 520 final.
But I still need help with this.