LxPupSc64 - 64bit version of Puppy with the LXDE desktop
LxPup64 - 64bit versions of Puppy with the LXDE desktop
Manual frugal install to a usb-3.0 SSD:
video-info-glx 1.5.3 Fri 16 Mar 2018 on LxPupSc64 18.03 Linux 4.15.7-lxpup64 x86_64
0.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)
X Server: Xorg Driver: nvidia
X.Org version: 1.19.6
dimensions: 3840x1080 pixels (1049x292 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 430/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 390.42
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Core 0: @1668 1: @1756 2: @1634 3: @1620 MHz
Installed kpat,vlc,gkrellm, with PPM + compiled smplayer/smtube.
One problem is that using the up-arrow key triggers the mtpaint
screenshot, the up-arrow key on the numeric keypad works fine (when I
remember to use it)
Also installed the newest Nvidia proprietary driver (Mar 12th)
Thanks.
video-info-glx 1.5.3 Fri 16 Mar 2018 on LxPupSc64 18.03 Linux 4.15.7-lxpup64 x86_64
0.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)
X Server: Xorg Driver: nvidia
X.Org version: 1.19.6
dimensions: 3840x1080 pixels (1049x292 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 430/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 390.42
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Core 0: @1668 1: @1756 2: @1634 3: @1620 MHz
Installed kpat,vlc,gkrellm, with PPM + compiled smplayer/smtube.
One problem is that using the up-arrow key triggers the mtpaint
screenshot, the up-arrow key on the numeric keypad works fine (when I
remember to use it)
Also installed the newest Nvidia proprietary driver (Mar 12th)
Thanks.
- Attachments
-
- screenshot.jpg
- (31.18 KiB) Downloaded 427 times
Re: LxPup64 - 64bit versions of Puppy with the LXDE desktop
Hi @BilltooBilltoo wrote:One problem is that using the up-arrow key triggers the mtpaint screenshot, the up-arrow key on the numeric keypad works fine (when I
remember to use it)
I don't see that problem on either of my test pc's. Anybody else seeing it??
Can you give more details of your setup so I can try to duplicate? My installs are to hdd but that shouldn't make a difference....
Is the problem there on 1st pristine frugal install with nothing added?
Is it mtpaint triggered?? It should be TAS.....
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Re: LxPup64 - 64bit versions of Puppy with the LXDE desktop
peebee wrote:Hi @BilltooBilltoo wrote:One problem is that using the up-arrow key triggers the mtpaint screenshot, the up-arrow key on the numeric keypad works fine (when I
remember to use it)
I don't see that problem on either of my test pc's. Anybody else seeing it??
Can you give more details of your setup so I can try to duplicate? My installs are to hdd but that shouldn't make a difference....
Is the problem there on 1st pristine frugal install with nothing added?
Is it mtpaint triggered?? It should be TAS.....
Hi peebee
I can't swear to it but I'm pretty sure the problem is there on a
pristine frugal install.
Yes, mtpaint is triggered,if you were to hold the up-arrow down for a
couple of seconds you might see 10 or more in the tray (see screenshot)
This was a problem on one of radky's dpup's (I think) caused by
PupControl, he had a fix for it but I can't remember what it was.
It's a problem on my hard drive install of your first release but I
didn't report it at that time.
- Attachments
-
- up-arrow.jpg
- (44.11 KiB) Downloaded 378 times
The fact that it's mtpaint suggests that the openbox config is getting overwritten....
or defaultscreenshot has been changed....
Does the PrintScreen key do anything?
see /root/.config/openbox/rc.xml
should say:
<keybind key="Print">
<action name="Execute">
<command>defaultscreenshot</command>
</action>
</keybind>
or defaultscreenshot has been changed....
Does the PrintScreen key do anything?
see /root/.config/openbox/rc.xml
should say:
<keybind key="Print">
<action name="Execute">
<command>defaultscreenshot</command>
</action>
</keybind>
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Here's the /root/.config/openbox/rc.xmlpeebee wrote:The fact that it's mtpaint suggests that the openbox config is getting overwritten....
or defaultscreenshot has been changed....
Does the PrintScreen key do anything?
see /root/.config/openbox/rc.xml
should say:
<keybind key="Print">
<action name="Execute">
<command>defaultscreenshot</command>
</action>
</keybind>
PrintScreen doesn't appear to do anything.
- Attachments
-
- rc.xml.gz
- (25.36 KiB) Downloaded 275 times
You have:
<keybind key="0x6F">
<action name="Execute">
<startupnotify>
<enabled>true</enabled>
<name>Print Screen</name>
</startupnotify>
<command>mtpaint -s</command>
</action>
</keybind>
in rc.xml so it has been overwritten....
Run xev in a terminal
press Up Arrow
should see:
keycode 111 (keysym 0xff52, Up)
Stop xev with cntrl-c
Run xev again
press PrintScreen
should see:
keycode 107 (keysym 0xff61, Print)
<keybind key="0x6F">
<action name="Execute">
<startupnotify>
<enabled>true</enabled>
<name>Print Screen</name>
</startupnotify>
<command>mtpaint -s</command>
</action>
</keybind>
in rc.xml so it has been overwritten....
Run xev in a terminal
press Up Arrow
should see:
keycode 111 (keysym 0xff52, Up)
Stop xev with cntrl-c
Run xev again
press PrintScreen
should see:
keycode 107 (keysym 0xff61, Print)
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
I chose Switch LXDE <-> JWM desktop environments from the setup menu and the up-arrow problem is gone.peebee wrote:You have:
<keybind key="0x6F">
<action name="Execute">
<startupnotify>
<enabled>true</enabled>
<name>Print Screen</name>
</startupnotify>
<command>mtpaint -s</command>
</action>
</keybind>
in rc.xml so it has been overwritten....
Run xev in a terminal
press Up Arrow
should see:
keycode 111 (keysym 0xff52, Up)
Stop xev with cntrl-c
Run xev again
press PrintScreen
should see:
keycode 107 (keysym 0xff61, Print)
Gave it a new background.
Edit: I had the same problem on my hard drive install of RC1
Linux puppypc11697 4.15.7-lxpup64 #1 SMP Thu Mar 1 07:25:15 +08 2018 x86_64 AMD Phenom(tm) II X6 1045T Processor AuthenticAMD GNU/Linux
#
Turning it into Slacko64 RC3 with an updated kernel isn't the fix you want but it is working well.
- Attachments
-
- screenshot3.jpg
- (70.91 KiB) Downloaded 322 times
-
- screenshot2.jpg
- (34.04 KiB) Downloaded 348 times
Last edited by Billtoo on Sat 17 Mar 2018, 11:10, edited 1 time in total.
Tried current update & previous. Frugal on hdd. Arrow keys just move cursor as expected. Toshiba laptop C665D cpu AMD E-450.
Edit: PrtSc brings up 'Take a Shot'. With the latest version - just booted up & no settings changed.
Edit: PrtSc brings up 'Take a Shot'. With the latest version - just booted up & no settings changed.
Last edited by ozsouth on Sat 17 Mar 2018, 21:11, edited 1 time in total.
Billtoo wrote:Here's the /root/.config/openbox/rc.xmlpeebee wrote:The fact that it's mtpaint suggests that the openbox config is getting overwritten....
or defaultscreenshot has been changed....
Does the PrintScreen key do anything?
see /root/.config/openbox/rc.xml
should say:
<keybind key="Print">
<action name="Execute">
<command>defaultscreenshot</command>
</action>
</keybind>
PrintScreen doesn't appear to do anything.
@Billtoo, Peebee:
This was the exact problem I reported (and what I did to fix it) to peebee almost a half year ago:
http://murga-linux.com/puppy/viewtopic. ... 7aa6b8602c
Surprised to see it is still occurring in many iterations of other OSes with lxde. Maybe the offending rc.xml code needs removed from rc.xml permanently, so it doesn't infect lxde-rc.xml (and anything else)? That was how I fixed it back then.
THEME Set Switcher is the issue
Tried 2 other pcs with LxPupSc64-18.03+2 on usb ext2. No issue - each time booted up and closed Quick start, Welcome & Theme Switcher unchanged.
** THEN ** - I changed the THEME SET via Switcher - billtoo & belham2's issues began. THEN I reverted to original blue theme - all OK again. Repeated with all 3 non-original blue sets. SUGGESTION - scrub Theme Set Switcher, or at least remove it from Startup.
** THEN ** - I changed the THEME SET via Switcher - billtoo & belham2's issues began. THEN I reverted to original blue theme - all OK again. Repeated with all 3 non-original blue sets. SUGGESTION - scrub Theme Set Switcher, or at least remove it from Startup.
Re: THEME Set Switcher is the issue
Thanks ozsouth - I know what I need to fix now....ozsouth wrote:Tried 2 other pcs with LxPupSc64-18.03+2 on usb ext2. No issue - each time booted up and closed Quick start, Welcome & Theme Switcher unchanged.
** THEN ** - I changed the THEME SET via Switcher - billtoo & belham2's issues began. THEN I reverted to original blue theme - all OK again. Repeated with all 3 non-original blue sets. SUGGESTION - scrub Theme Set Switcher, or at least remove it from Startup.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Delta to LxPupSc64-18.03+3
.iso md5 = 56a23bc7ef2780038824d5f850f1806b lxpupsc64-18.03+3.iso
- fixes the Theme Setter
.iso md5 = 56a23bc7ef2780038824d5f850f1806b lxpupsc64-18.03+3.iso
- fixes the Theme Setter
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
LxPupSc64 currently has ffmpeg-2.8.11 from slacko6414.2 (ffmpeg-2.8.11-x86_64_s700)
My suspicion is that this needs rebuilding/updating as for instance:
aplay /usr/share/sounds/2barks.au
is giving errors....as are some websites....
Anybody else noticed sound problems??
The problem is I don't think I've got the right compiling environment available....
My suspicion is that this needs rebuilding/updating as for instance:
aplay /usr/share/sounds/2barks.au
is giving errors....as are some websites....
Anybody else noticed sound problems??
The problem is I don't think I've got the right compiling environment available....
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
I hadn't noticed any problems on either the i5 or the core 2 duo. Just startup sound, some news type web pages and aplay. On both machines aplay returnspeebee wrote:LxPupSc64 currently has ffmpeg-2.8.11 from slacko6414.2 (ffmpeg-2.8.11-x86_64_s700)
My suspicion is that this needs rebuilding/updating as for instance:
aplay /usr/share/sounds/2barks.au
is giving errors....as are some websites....
Anybody else noticed sound problems??
The problem is I don't think I've got the right compiling environment available....
Code: Select all
# aplay /usr/share/sounds/2barks.au
Playing Sparc Audio '/usr/share/sounds/2barks.au' : Mu-Law, Rate 8000 Hz, Mono
#
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
running 18.03 from iso (unpatched;k5.15.7) savefolder. Have made no changes and have no issues with sounds or ffmpeg. pmusic works well and every video format I have plays on gnome mplayer.. Same with X-startup sound OOTB. I prefer the older ffmpeg over that offered by Slackware64-curent.
df
edit: I haven't installed the delta patches so haven't tested it, but if the slackware64 updates include gst/gstreamer 1.14.0, they conflict with any libav* from any other ffmpeg, so that could be the culprit in sound issues. I've found gstreamer or at least gst-plugins from arch linux more forgiving.
df
edit: I haven't installed the delta patches so haven't tested it, but if the slackware64 updates include gst/gstreamer 1.14.0, they conflict with any libav* from any other ffmpeg, so that could be the culprit in sound issues. I've found gstreamer or at least gst-plugins from arch linux more forgiving.
Hi DFDry Falls wrote:if the slackware64 updates include gst/gstreamer 1.14.0,
Neither LxPupSc64 nor LxPupSc include gst/gstreamer....
LxPupSc (32-bit) has ffmpeg-3.4 and that seems to work OK.
I'm beginning to think that my aplay example is a red-herring....
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Delta +4
iso md5 = fe3f2aa20b1b6fe925d1d1b080cec77f lxpupsc64-18.03+4.iso
- ffmpeg-3.4.2 (compiled in slacko64 with gcc-5.3.0)
iso md5 = fe3f2aa20b1b6fe925d1d1b080cec77f lxpupsc64-18.03+4.iso
- ffmpeg-3.4.2 (compiled in slacko64 with gcc-5.3.0)
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Installing the devx is what kills aplay.....
[edit] Also happens with 32-bit devx so needs investigation....
[edit] Also happens with 32-bit devx so needs investigation....
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
+4 applied. Audio working after the update as it was before. I just recalled that Slimmie does carry and attempt to force use of its own ffmpeg though...
Cheers,
Cheers,
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.