cheers ...fixedJames C wrote:
...if it doesn't have "amd64", that is the cause of the problem.
tahrpup64 6.0.5 CE
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
-
- Posts: 361
- Joined: Fri 27 May 2011, 17:21
- Location: Reading UK
VLC skipping
Hello 666philb
I have installed MPV 0.8.3 and it works normally with no skipped frames. So it looks like something is wrong with VLC 2.2.1
VLC gives a lot of " frame too late to display" errors even when there is only 55% cpu load.
In Fatdog all of the media players like: VLC 2.1.5, MPV, GXINE behave alike when doing H.264 + YADIF 2x in software, without any problem.
There were only seven dependencies needed for MPV 0.8.3 with Tahr64. I already had the amd64 Trusty debs that I used when I installed MPV on Fatdog, which made the test very quick. I didn't need to use the package manager.
I have installed MPV 0.8.3 and it works normally with no skipped frames. So it looks like something is wrong with VLC 2.2.1
VLC gives a lot of " frame too late to display" errors even when there is only 55% cpu load.
In Fatdog all of the media players like: VLC 2.1.5, MPV, GXINE behave alike when doing H.264 + YADIF 2x in software, without any problem.
There were only seven dependencies needed for MPV 0.8.3 with Tahr64. I already had the amd64 Trusty debs that I used when I installed MPV on Fatdog, which made the test very quick. I didn't need to use the package manager.
Sure, but Debian is officially migrating from avconv to ffmpeg, why not using the "official" builds?avconv in kdenlive
Re: https://wiki.debian.org/Debate/libav-provider/ffmpeg
markdown files, I open them with Geanymd an odd extension
.webm sorry,
but misses
.opus > VLC / DeaDBeeF
.m4b > VLC / DeaDBeeF
.wma open in DeaDBeeF but do not play, OK with VLC
OK How did you know? no warning, good guess?musique & amarok need phonon-backend-gstreamer plus some gstreamer1.0 plugins .... maybe the good and bad plugins
Can't run Rythmbox either:
root# rhythmbox
** (rhythmbox:17453): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
(rhythmbox:17453): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
(rhythmbox:17453): Gtk-CRITICAL **: gtk_css_provider_load_from_path: assertion 'path != NULL' failed
(rhythmbox:17453): GLib-GIO-ERROR **: Settings schema 'org.gnome.rhythmbox' is not installed
Trace/breakpoint trap
root#
Seems to run great.
I too need 32 bit compatibility though, and the way to do it with Ubuntu doesn't seem to work.
http://askubuntu.com/questions/454253/h ... ntu-64-bit
Did the steps in the above and I get the following.
I too need 32 bit compatibility though, and the way to do it with Ubuntu doesn't seem to work.
http://askubuntu.com/questions/454253/h ... ntu-64-bit
Did the steps in the above and I get the following.
Code: Select all
bash: /usr/bin/skype: cannot execute binary file: Exec format error
"In a world that exists without walls and fences, who needs Windows and Gates?"
Re: VLC skipping
I'll switch back to the vlc from the ppm for the next build see if that's any betterLateAdopter wrote:Hello 666philb
I have installed MPV 0.8.3 and it works normally with no skipped frames. So it looks like something is wrong with VLC 2.2.1
VLC gives a lot of " frame too late to display" errors even when there is only 55% cpu load.
In Fatdog all of the media players like: VLC 2.1.5, MPV, GXINE behave alike when doing H.264 + YADIF 2x in software, without any problem.
There were only seven dependencies needed for MPV 0.8.3 with Tahr64. I already had the amd64 Trusty debs that I used when I installed MPV on Fatdog, which made the test very quick. I didn't need to use the package manager.
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
if you have opus & m4b files handy can you right click on them and choose 'set run action' and post the info in the picture below.live wrote:Sure, but Debian is officially migrating from avconv to ffmpeg, why not using the "official" builds?avconv in kdenlive
Re: https://wiki.debian.org/Debate/libav-provider/ffmpeg
markdown files, I open them with Geanymd an odd extension
.webm sorry,
but misses
.opus > VLC / DeaDBeeF
.m4b > VLC / DeaDBeeF
.wma open in DeaDBeeF but do not play, OK with VLC
OK How did you know? no warning, good guess?musique & amarok need phonon-backend-gstreamer plus some gstreamer1.0 plugins .... maybe the good and bad plugins
Can't run Rythmbox either:root# rhythmbox
** (rhythmbox:17453): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
(rhythmbox:17453): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
(rhythmbox:17453): Gtk-CRITICAL **: gtk_css_provider_load_from_path: assertion 'path != NULL' failed
(rhythmbox:17453): GLib-GIO-ERROR **: Settings schema 'org.gnome.rhythmbox' is not installed
Trace/breakpoint trap
root#
rhythmbox ...yes i know about that error and it's fixed in next iso thanks to iguleder
you should be able to fix it by re-installing glib from the PPM and then running
Code: Select all
/usr/bin/glib-compile-schemas /usr/share/glib-2.0/schemas/
- Attachments
-
- capture2771.png
- (21.62 KiB) Downloaded 1297 times
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
hi sketchman,sketchman wrote:Seems to run great.
I too need 32 bit compatibility though, and the way to do it with Ubuntu doesn't seem to work.
http://askubuntu.com/questions/454253/h ... ntu-64-bit
Did the steps in the above and I get the following.
Code: Select all
bash: /usr/bin/skype: cannot execute binary file: Exec format error
i'll be looking into 32bit compatibility next release ... i've got a 32bit enabled kernel and some pointers from jamesbond
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
puppy.css is in slacko-5.9.3 ....either it used to be in woof once or i pinched it from 01mickomavrothal wrote:No. What I'm asking is where the files /usr/share/doc/installation.htm and /usr/share/doc/puppy.css that are present in the 32bit TahrPup-6.0.x are coming from?bigpup wrote:The installer in Tahr-6.0.x.mavrothal wrote: This is not or ever was in woof!
Where is it coming from in Tahr-6.0.x ?
It calls up this web page:
http://puppylinux.com/install.htm
There are not in woof, they are not in z_hacks So how did they make it into Puppy Tahr 6.0.2?
EDIT: it was in woof ....here's where it gets lost https://github.com/puppylinux-woof-CE/woof-CE/pull/517
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
It was in woof.
It got changed when someone else changed the docs. I can't remember who off hand but they were a web dev, I am not.
EDIT: I just changed it to use ./manual.css. Looks fine. I'll commit to woof.
Try it yourself.
It got changed when someone else changed the docs. I can't remember who off hand but they were a web dev, I am not.
EDIT: I just changed it to use ./manual.css. Looks fine. I'll commit to woof.
Try it yourself.
- Attachments
-
- installation.htm.gz
- (3.91 KiB) Downloaded 204 times
Puppy Linux Blog - contact me for access
Actually this is the commit and it does changes the css tp puppy.css. But this commit does NOT delete /usr/share/doc/installation.htm. I actually checked the git log of woof-CE for that file and it was never in woof-CE666philb wrote: EDIT: it was in woof ....here's where it gets lost https://github.com/puppylinux-woof-CE/woof-CE/pull/517
Regarding the Tahr version of installation.htm, indeed all you need is to change the css to puppy.css. But where is the original to change it there?...
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
The /usr/share/doc/installation.htm thing was _supposed_ to be commited when I committed the improved puppy installer but I must have missed it
Fixed anyway by now.
Fixed anyway by now.
Puppy Linux Blog - contact me for access
Aha!
@666philb
I have finally found my jwmrc fixup script! It was part of my petbuilds all along, however it doesn't execute in woof through the pinstall.sh. However, I can bung one line into 3builddistro and have it it execute if it exists in chroot. (No, won't do that, have it called from a pinstall.sh instead, sample with output below -from latest woof-ce)
here it is: (edited) name it fixjwmrc and it must be in usr/local/nin of the jwm package.
Be careful doing copy/paste from the forum as it adds a space to line ends that breaks scripts!
pinstall.sh
sample output of 3builddistro
Now, when you build jwm from source then in it there is the jwm*.xslt (in the case of jwm-2.3.2 its called jwm-2.3.xslt). If you copy that into etc of the package the script will run when executed.
I have now made the script compliant for stable and snapshot versions of JWM.
@666philb
I have finally found my jwmrc fixup script! It was part of my petbuilds all along, however it doesn't execute in woof through the pinstall.sh. However, I can bung one line into 3builddistro and have it it execute if it exists in chroot. (No, won't do that, have it called from a pinstall.sh instead, sample with output below -from latest woof-ce)
here it is: (edited) name it fixjwmrc and it must be in usr/local/nin of the jwm package.
Be careful doing copy/paste from the forum as it adds a space to line ends that breaks scripts!
Code: Select all
#!/bin/sh
# script to update configs
# if file is newer than June 1, 2015 we skip it
# JWMV is for stable releases, JWMGV is for snapshots
#set -x
# get the version
JWMV=`jwm -v|cut -d ' ' -f2|sed 's/v//'|head -n1`
[ -z "$JWMV" ] && exit
echo "$JWMV" | grep -q '^git' && JWMGV=${JWMV##*-} JWMSV=231 F=0 || \
JWMSV=${JWMV//./} JWMGV=1066 F=1 #hack
# quit if too old
if [ $JWMSV -lt 231 -o $JWMGV -lt 1066 ];then
exit
fi
case $F in
0)JWM=$JWMGV;;
1)JWM=$JWMSV
esac
echo "fixing for JWM version $JWM..."
XSLT=`find /etc -type f -name 'jwm*.xslt'`
[ -z "$XSLT" ] && exit
for i in `find /etc $HOME /root -type f -name '*jwmrc*'`;do
echo "fixing $i"
if grep -q '<JWM>' $i;then
echo "$i is compliant"
else
echo "$i not valid" && continue
fi
age=$(date +%s -r $i)
[ $age -gt 1433080800 ] && echo "$i seems up to date" && continue
cp $i ${i}.old
xsltproc ${XSLT} ${i}.old > $i
[ $? -ne 0 ] && "fixing $i failed" || echo "fixing $i succeeded!"
rm ${i}.old
done
Code: Select all
#!/bin/sh
#post-install script.
#Puppy Linux
#Woof: if current directory is rootfs-complete, it has the final filesystem.
if [ "`pwd`" != "/" ];then
if [ ! -f ./usr/bin/fvwm95 ];then
if [ ! -f ./usr/bin/fbpanel ];then
if [ ! -f ./usr/bin/lxpanel ];then
echo -n "jwm" > ./etc/windowmanager
fi
fi
fi
if [ -x usr/local/bin/fixjwmrc ];then
echo "Attempting to fix old jwm config files"
chroot . usr/local/bin/fixjwmrc
fi
else
Xdialog -title "Fix JWM Configs" \
-yesno "This is a new version of JWM
and configs may need upgrading.
Click 'Yes' to upgrade, 'No' to quit.
You can run /usr/local/bin/fixjwmrc later." 0 0 || \
exit
[ ! -x /usr/local/bin/fixjwmrc ] && \
Xdialog -title "Fix JWM Configs" -msgbox "Fail" 0 0 && \
exit
/usr/local/bin/fixjwmrc | xmessage -name 'Fix JWM Configs' -file -
fi
#end#
Code: Select all
Setting geany as defaulttexteditor
Post-install script for glib...
Setting gnome-mplayer as defaultmediaplayer and defaultvideoplayer
post-install for gxmessage, creating symlink to replace xmessage
setting HexChat as default chat
Attempting to fix old jwm config files
fixing for JWM version 232...
fixing /etc/xdg/templates/_root_.jwmrc
/etc/xdg/templates/_root_.jwmrc is compliant
/etc/xdg/templates/_root_.jwmrc seems up to date
fixing /etc/system.jwmrc
/etc/system.jwmrc is compliant
/etc/system.jwmrc seems up to date
fixing /root/.jwm/jwmrc-personal2
/root/.jwm/jwmrc-personal2 is compliant
fixing /root/.jwm/jwmrc-personal2 succeeded!
fixing /root/.jwm/jwmrc-personal
/root/.jwm/jwmrc-personal is compliant
fixing /root/.jwm/jwmrc-personal succeeded!
fixing /root/.jwm/themes/purplegum-jwmrc
/root/.jwm/themes/purplegum-jwmrc is compliant
/root/.jwm/themes/purplegum-jwmrc seems up to date
fixing /root/.jwm/themes/Stardust_bright-jwmrc
/root/.jwm/themes/Stardust_bright-jwmrc is compliant
/root/.jwm/themes/Stardust_bright-jwmrc seems up to date
fixing /root/.jwm/themes/DarkGradient-jwmrc
/root/.jwm/themes/DarkGradient-jwmrc is compliant
/root/.jwm/themes/DarkGradient-jwmrc seems up to date
fixing /root/.jwm/themes/Black-vg-jwmrc
/root/.jwm/themes/Black-vg-jwmrc is compliant
fixing /root/.jwm/themes/Black-vg-jwmrc succeeded!
fixing /root/.jwm/themes/flat-green-jwmrc
/root/.jwm/themes/flat-green-jwmrc is compliant
/root/.jwm/themes/flat-green-jwmrc seems up to date
fixing /root/.jwm/themes/Cloudy-jwmrc
/root/.jwm/themes/Cloudy-jwmrc is compliant
/root/.jwm/themes/Cloudy-jwmrc seems up to date
fixing /root/.jwm/themes/Stardust_dark-jwmrc
/root/.jwm/themes/Stardust_dark-jwmrc is compliant
/root/.jwm/themes/Stardust_dark-jwmrc seems up to date
fixing /root/.jwmrc-tray
/root/.jwmrc-tray is compliant
fixing /root/.jwmrc-tray succeeded!
fixing /root/.jwm/jwmrc-personal2
/root/.jwm/jwmrc-personal2 is compliant
/root/.jwm/jwmrc-personal2 seems up to date
fixing /root/.jwm/jwmrc-personal
/root/.jwm/jwmrc-personal is compliant
/root/.jwm/jwmrc-personal seems up to date
fixing /root/.jwm/themes/purplegum-jwmrc
/root/.jwm/themes/purplegum-jwmrc is compliant
/root/.jwm/themes/purplegum-jwmrc seems up to date
fixing /root/.jwm/themes/Stardust_bright-jwmrc
/root/.jwm/themes/Stardust_bright-jwmrc is compliant
/root/.jwm/themes/Stardust_bright-jwmrc seems up to date
fixing /root/.jwm/themes/DarkGradient-jwmrc
/root/.jwm/themes/DarkGradient-jwmrc is compliant
/root/.jwm/themes/DarkGradient-jwmrc seems up to date
fixing /root/.jwm/themes/Black-vg-jwmrc
/root/.jwm/themes/Black-vg-jwmrc is compliant
/root/.jwm/themes/Black-vg-jwmrc seems up to date
fixing /root/.jwm/themes/flat-green-jwmrc
/root/.jwm/themes/flat-green-jwmrc is compliant
/root/.jwm/themes/flat-green-jwmrc seems up to date
fixing /root/.jwm/themes/Cloudy-jwmrc
/root/.jwm/themes/Cloudy-jwmrc is compliant
/root/.jwm/themes/Cloudy-jwmrc seems up to date
fixing /root/.jwm/themes/Stardust_dark-jwmrc
/root/.jwm/themes/Stardust_dark-jwmrc is compliant
/root/.jwm/themes/Stardust_dark-jwmrc seems up to date
fixing /root/.jwmrc-tray
/root/.jwmrc-tray is compliant
/root/.jwmrc-tray seems up to date
Configuring Osmo...
Configuring ROX Filer...
Xarchive post-install script
xorg_base post-install script...
Fixing wallpapers
END OF pinstall.sh SCRIPT.
Now setting /etc/os-release file
If you did not get 'End of pinstall.sh' message above, then
it aborted before completion. Press ENTER or CTRL-C:
Now, when you build jwm from source then in it there is the jwm*.xslt (in the case of jwm-2.3.2 its called jwm-2.3.xslt). If you copy that into etc of the package the script will run when executed.
I have now made the script compliant for stable and snapshot versions of JWM.
Puppy Linux Blog - contact me for access
tahrpup has a problem (actually it is ubuntu problem) - its librsvg2-2 cannot render SVG images with xlink:href in it.
My fix: use an older version of librsvg2-2 (version 2.34) from either quantal or precise.
My fix: use an older version of librsvg2-2 (version 2.34) from either quantal or precise.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Anyone else have problem using the GetJAVA utility in the Menu.
After download, I lead the installation to install to RAM. It recommends to save the SFS in /tmp. Then this error occurs following that recommendation.
Update: targeting it to a permanent partition does not steer to error.
After download, I lead the installation to install to RAM. It recommends to save the SFS in /tmp. Then this error occurs following that recommendation.
Update: targeting it to a permanent partition does not steer to error.
- Attachments
-
- GetJAVA.png
- (229.95 KiB) Downloaded 751 times
This is a bug in sfs_load when it tries to install an sfs saved in /tmp (in RAM) and not specific to this puplet or the given SFS.gcmartin wrote:After download, I lead the installation to install to RAM. It recommends to save the SFS in /tmp. Then this error occurs following that recommendation.
Better report in the sfs_load thread.
Latter: Here is a work around
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
Update:666philb wrote:hi bigpup,bigpup wrote:01micko and 666philb,
Because I am using the Tahr_kernel.4.1.7.tar.xz that 01micko made.
I am not sure if you want me to report any problems I may have.
You tell me?
yes definitely report.... the kernel in tahrpup64 isn't set yet, I've just used the 3.14 as it boots to a desktop for me where as 4* ones don't. i would like to go with the latest 4* kernel and will look into missing firmware as 01micko suggested.
This kernel seems to be working OK for me.
Definitely need it for my Geforce GTX 960 graphics card support.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
thanks 01micko,01micko wrote:Aha!
@666philb
I have finally found my jwmrc fixup script! It was part of my petbuilds all along, however it doesn't execute in woof through the pinstall.sh. However, I can bung one line into 3builddistro and have it it execute if it exists in chroot. (No, won't do that, have it called from a pinstall.sh instead, sample with output below -from latest woof-ce)
i'll give it a go in my next build
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
thanks to jamesbond we now have 32bit apps running in tahrpup64
skypes working, wine works running 32bit apps, and 32bit steam works.
the picture has steam (32bit) running a 64bit game. this the first time i've had this game running on a puppy
skypes working, wine works running 32bit apps, and 32bit steam works.
the picture has steam (32bit) running a 64bit game. this the first time i've had this game running on a puppy
- Attachments
-
- steam.jpg
- (224.86 KiB) Downloaded 536 times
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331