Posted: Sat 11 Feb 2012, 03:14
Did you try that ffmpeg command in wary ? If no, why do you answer this ?
READ-ONLY Archive
https://oldforum.puppylinux.com/
I know this already but in wary, it's empty by default, so should we keep empty folders ?Monsie wrote:@linuxcbon:
The empty opt directory is not an artifact or a bug. Some third party applications choose to install to this directory rather than /local and in my case I see that qt4 is installed in the opt directory.
Monsie
I found some time to look into this further.npierce wrote:I have not yet determined if setting GDK_NATIVE_WINDOWS=true will affect only ROX-Filer, or will affect every GTK/GDK application it opens.
The reason that I set it in /usr/local/apps/ROX-Filer/AppRun instead of /root/.xinitrc or earlier, is to, hopefully, limit its effect to ROX-Filer. But it is certainly possible that, once set, all GTK/GDK applications will be affected. I have noticed that when I use ROX-Filer to run urxvt, GDK_NATIVE_WINDOWS does not appear in the environment. So maybe I got lucky.
Code: Select all
xwininfo -children
Code: Select all
xwininfo: Window id: 0x800024 "ROX-Filer"
Root window id: 0xaa (the root window) (has no name)
Parent window id: 0xaa (the root window) (has no name)
1 child:
0x800025 (has no name): () 1x1+-1+-1 +-1+-1
Code: Select all
rox -p /root/Choices/ROX-Filer/PuppyPin
Code: Select all
xwininfo: Window id: 0x800024 "ROX-Filer"
Root window id: 0xaa (the root window) (has no name)
Parent window id: 0xaa (the root window) (has no name)
32 children:
0x800056 (has no name): () 58x75+1219+91 +1219+91
0x800055 (has no name): () 58x75+1219+187 +1219+187
0x800054 (has no name): () 58x75+1219+2 +1219+2
0x800053 (has no name): () 58x75+131+91 +131+91
0x800052 (has no name): () 58x75+131+187 +131+187
0x800051 (has no name): () 58x75+259+2 +259+2
0x800050 (has no name): () 58x75+195+91 +195+91
0x80004f (has no name): () 58x75+323+2 +323+2
0x80004e (has no name): () 66x75+383+2 +383+2
0x80004d (has no name): () 58x75+3+91 +3+91
0x80004c (has no name): () 64x75+2+187 +2+187
0x80004b (has no name): () 58x75+131+2 +131+2
0x80004a (has no name): () 58x75+67+2 +67+2
0x800049 (has no name): () 58x75+3+2 +3+2
0x800048 (has no name): () 58x75+3+283 +3+283
0x800047 (has no name): () 68x75+2+379 +2+379
0x800046 (has no name): () 58x75+67+91 +67+91
0x800045 (has no name): () 58x75+67+187 +67+187
0x800044 (has no name): () 58x75+195+2 +195+2
0x800043 (has no name): () 58x75+67+283 +67+283
0x800042 (has no name): () 58x75+3+699 +3+699
0x800041 (has no name): () 58x75+67+699 +67+699
0x800040 (has no name): () 58x75+131+699 +131+699
0x80003f (has no name): () 58x75+195+699 +195+699
0x80003e (has no name): () 58x75+259+699 +259+699
0x80003d (has no name): () 58x75+323+699 +323+699
0x80003c (has no name): () 58x75+387+699 +387+699
0x80003b (has no name): () 58x75+451+699 +451+699
0x80003a (has no name): () 58x75+515+699 +515+699
0x800039 (has no name): () 58x75+579+699 +579+699
0x800038 (has no name): () 58x75+643+699 +643+699
0x800025 (has no name): () 1x1+-1+-1 +-1+-1
Code: Select all
xwininfo: Window id: 0x4400003 "Puppy Setup"
Root window id: 0xaa (the root window) (has no name)
Parent window id: 0x6b0ffc (has no name)
1 child:
0x4400004 (has no name): () 1x1+-1+-1 +202+221
Code: Select all
xwininfo: Window id: 0x4400003 "Puppy Setup"
Root window id: 0xaa (the root window) (has no name)
Parent window id: 0x6b235e (has no name)
12 children:
0x4400032 (has no name): () 32x24+300+317 +528+564
0x4400031 (has no name): () 26x26+306+286 +534+533
0x4400030 (has no name): () 26x26+306+255 +534+502
0x440002f (has no name): () 27x27+305+223 +533+470
0x440002e (has no name): () 28x28+304+190 +532+437
0x440002d (has no name): () 26x26+306+159 +534+406
0x440002c (has no name): () 26x26+306+128 +534+375
0x440002b (has no name): () 26x26+306+97 +534+344
0x440002a (has no name): () 26x25+306+67 +534+314
0x4400029 (has no name): () 26x26+306+36 +534+283
0x4400028 (has no name): () 26x26+306+5 +534+252
0x4400004 (has no name): () 1x1+-1+-1 +227+246
Code: Select all
<label>Bypass log-in</label>
Code: Select all
#111231 Ensure non-null logon info for wvdial...
[ ! ${ENTRYACC1USER} ] && ENTRYACC1USER="MYUSERNAME"
[ ! ${ENTRYACC1PASS} ] && ENTRYACC1PASS="MYPASSWORD"
[ ! ${ENTRYACC2USER} ] && ENTRYACC2USER="MY2USERNAME"
[ ! ${ENTRYACC2PASS} ] && ENTRYACC2PASS="MY2PASSWORD"
echo '[Dialer Defaults]' > /etc/wvdial.conf
Thank you a lot for test, explanations and solution: I feel much better now!Apparently it works the way I hoped that it would. By setting GDK_NATIVE_WINDOWS in /usr/local/apps/ROX-Filer/AppRun instead of earlier, it is affecting only ROX-Filer, not applications started by ROX-Filer. So other GTK/GDK applications will continue to use "client-side windows", and should not suffer any loss of speed when creating windows.
Done. See blog post:rerwin wrote:Barry,
In the new "testing" version of lucid pup 5.2.8, I addressed issues that keep frustrating new users of pupdial. I submit them for consideration to be included in woof/wary/racy.
When instructed to omit the login ID and password for wireless modem connections, new users encounter the error message from wvdial complaining about the absence of those items. The remedy is to select "Stupid mode", which is not something novices could infer by themselves. To eliminate that booby trap, I made these changes (copied for my original posting):My label fix in 2 places is:
- - In the pupdial modem dialer, changed the label of the "Stupid mode" checkbox to "Bypass log-in", which is what it does -- many new users get frustrated when they delete the login and password default, following their ISP's instructions, and cannot connect, only to be advised to turn on Stupid mode, which is not at all obvious.
- In pupdial, also ensured that a login and password are passed to wvdial (which requires them) by filling the empty fields with the default values.The latter fix is implemented thusly:Code: Select all
<label>Bypass log-in</label>
All but the last line would be inserted into wary 5.2.2's pupdial after line 696.Code: Select all
#111231 Ensure non-null logon info for wvdial... [ ! ${ENTRYACC1USER} ] && ENTRYACC1USER="MYUSERNAME" [ ! ${ENTRYACC1PASS} ] && ENTRYACC1PASS="MYPASSWORD" [ ! ${ENTRYACC2USER} ] && ENTRYACC2USER="MY2USERNAME" [ ! ${ENTRYACC2PASS} ] && ENTRYACC2PASS="MY2PASSWORD" echo '[Dialer Defaults]' > /etc/wvdial.conf
Thanks for considering this.
Richard
It is working for me too!npierce wrote:You're welcome. I'm glad to hear that (so far) it is working for you.
Disaster!BarryK wrote:It is working for me too!npierce wrote:You're welcome. I'm glad to hear that (so far) it is working for you.
Trying to recall back when I last tried GDK_NATIVE_WINDOWS=true, I think that I put it as a prefix to the running of rox in /root/.xinitrc.
I was using it back then and noticed lots of gdk critical error reports on stderr, although I don't recall if anything actually crashed.
Anyway, I reckon that I will put your solution into the rox-filer PET pkg -- in the 'common' repo, the PET that most x86 Puppy builds use.
Code: Select all
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0"
after 11851 requests (11851 known processed) with 0 events remaining.
(ROX-Filer:12439): Gdk-WARNING **: Native children wider or taller than 65535 pixels are not supported
(ROX-Filer:12439): Gdk-WARNING **: Native children wider or taller than 65535 pixels are not supported
(ROX-Filer:12439): Gdk-WARNING **: Native children wider or taller than 65535 pixels are not supported
(ROX-Filer:12439): Gdk-WARNING **: Native children wider or taller than 65535 pixels are not supported
(ROX-Filer:12439): Gdk-WARNING **: Native children wider or taller than 65535 pixels are not supported
(ROX-Filer:12439): Gdk-WARNING **: Native children wider or taller than 65535 pixels are not supported
(ROX-Filer:12439): Gdk-WARNING **: Native children wider or taller than 65535 pixels are not supported
(ROX-Filer:12439): Gdk-WARNING **: Native children wider or taller than 65535 pixels are not supported
I would like to understand this situation better before implementing this solution.zekebaby wrote:In Wary 5.2.2, I noticed a problem with shutdown hanging if I don't manually unmount NFS or SSHFS mounted drives before shutting down. Poking around rc.shutdown, I found that //network drives are unmounted, but the grep does not pick up host:dir mounted drives.
Adding the following 4 lines in rc.shutdown near Line 190 solves the problem:Edit: made code more generic to detect other types of network drives such as sshfsCode: Select all
for MOUNTPOINT in `mount | grep ':' | cut -d ' ' -f 3 | tr '\n' ' '` do umount -f $MOUNTPOINT done
I would like to propose another solution based on pemasu's idea on the Dpup Exprimo.BarryK wrote:anyway, I have put zekebaby's patch into rc.shutdown:
http://bkhome.org/blog/?viewDetailed=02697
Code: Select all
#120203 pemasu and shinobar: space in smb or cifs share causes hanging in shutdown
for T in cifs smbfs nfs sshfs; do
umount -a -t $T
done
shinobar,shinobar wrote:I would like to propose another solution based on pemasu's idea on the Dpup Exprimo.BarryK wrote:anyway, I have put zekebaby's patch into rc.shutdown:
http://bkhome.org/blog/?viewDetailed=02697
http://www.murga-linux.com/puppy/viewto ... start=1734Code: Select all
#120203 pemasu and shinobar: space in smb or cifs share causes hanging in shutdown for T in cifs smbfs nfs sshfs; do umount -a -t $T done
Regarding the GDK_NATIVE_WINDOWS=true being a bad solution, see my post previous page.
The new rox-filer PET solves the old focus problem.Argolance wrote:Hello,
@BarryRegarding the GDK_NATIVE_WINDOWS=true being a bad solution, see my post previous page.
So sorry to have to say that the patch does not solve the issue reported above while the "bad" solution proposed by npierce does it (perfectly)!
Did I miss something?
Regards!