@peebee I couldn't hold back anymore..........viewforum.php?f=180
[CLOSED] VoidPup32 & VoidPup64 development thread
Moderator: Forum moderators
- rockedge
- Site Admin
- Posts: 6556
- Joined: Mon Dec 02, 2019 1:38 am
- Location: Connecticut,U.S.A.
- Has thanked: 2760 times
- Been thanked: 2640 times
- Contact:
- peebee
- Posts: 1637
- Joined: Mon Jul 13, 2020 10:54 am
- Location: Worcestershire, UK
- Has thanked: 157 times
- Been thanked: 715 times
- Contact:
Re: VoidPup64 SAMBA request, to match mainline PUPs subsystems
Clarity wrote: Sat Jan 22, 2022 10:52 pmSAMBA continues to be stable and secure in PUP use, could it be included in the future releases of this distro versus requiring user installation.
Hi @Clarity
I want to provide the latest Void release of Samba (and not have to build a pup-specific version) but it is large and pulls in Python3 dependency so would prefer to leave as an "add-on"........
[vpm_] Installing packages: samba (xbps-install -S samba) ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/cur ... 4-repodata' ...Name Action Version New version Download size
libtdb install - 1.4.5_1 44KB
lmdb install - 0.9.29_1 81KB
ldb install - 2.3.2_1 173KB
samba-libs install - 4.14.11_1 5154KB
python3 install - 3.10.2_1 7361KB
libpytalloc-util install - 2.3.3_1 5477B
libpyldb-util install - 2.3.2_1 6824B
samba install - 4.14.11_1 7556KBSize to download: 20MB
Size required on disk: 72MB
Space available on disk: 3918MB
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
- peebee
- Posts: 1637
- Joined: Mon Jul 13, 2020 10:54 am
- Location: Worcestershire, UK
- Has thanked: 157 times
- Been thanked: 715 times
- Contact:
Re: VoidPup32 & VoidPup64 BETA 19-Jan-22 Woof-CE build
c90ab2c911638ebf87644aa7b0b88f2c VoidPup64-22.01Beta+4.iso
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
- mikeslr
- Posts: 2968
- Joined: Mon Jul 13, 2020 11:08 pm
- Has thanked: 179 times
- Been thanked: 924 times
Re: VoidPup32 & VoidPup64 BETA 23-Jan-22 Woof-CE build
rockedge has created a new location for Voidpups, under Mainline. viewtopic.php?t=5016 Probably best to continue discussions there.
Re: VoidPup32 & VoidPup64 BETA 23-Jan-22 Woof-CE build
Beta +4 generated using the delta. md5sum correct, clean boot and run both updating my Beta +3 JWM savefile install and updating the Beta +3 LXDE savefile install (using the updated ydrv). My stock Fujitsu S761 and S762 hardware.
My only major deviation from the golden way is to install and use the bona-fide synaptics driver for the touchpad. Same procedure I outlined in the LxPupSc64 thread, libinput continues to handle all other input devices.
Intel_Pstate and its Schedutil governor give excellent power/thermal management on these lappies with the 5.16.2 kernel onboard and no issues with early loading Intel microcode though it changes little on these 2nd gen i5s.
I'm running the LXDE version as my daily for now with Slimjet64 33.0.0.0 from SFS; un-googled chromium version 96.0.4664.110, sylpheed 3.7.0, MasterPDFEditor 4, and LibreOffice 6.06 all as portables. The shared portables and all profiles and data reside on a dedicated EXT2 partition on the main SSD. Edited wallpaper using MTPaint to get a Void LXDE label in it so I know where in the kennels I am, TAS used, CUPS set up Brother HL-2170W laser printer continues to work well. Tax time and trying to rescue my wifes aging Droid phone.
Two things I don't have down yet:
One is how to set the GTK3 theme and get it harmonized with the GTK2+ theme using apps, not solely a Void issue.
The other is getting my head around a package manager that leaves no record of what has been installed so far as I can see. PPM uninstall and the associated packages records have been immensely useful to me as I muck about. I see ways to convert debs or directories into .xbps files but is there any way to extract a .xbps to a directory? I apologise in advance if it is obvious.
Might be the smoothest Beta launch I've munched on yet.
Thanks,
My pups: LxPupSc64 and Voidpup64 with LXDE ydrv and synaptics touchpad drivers, both using small savefiles for customizations. Ydrv based NoblePup64 and Fossapup64-small (both LXDE/PCManFM with no savefiles). No fdrvs throughout.
-
- Posts: 3844
- Joined: Fri Jul 24, 2020 10:59 pm
- Has thanked: 1633 times
- Been thanked: 527 times
Re: VoidPup32 & VoidPup64 BETA 23-Jan-22 Woof-CE build
Hi @peebee. Sent a short read via PM.
I am now testing VoidPUP64b4.
I did this:
Code: Select all
# smbd
sh: smbd: command not found
#
# vpm sync
[vpm_] Synchronizing remote repository data: (xbps-install -S):
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/x86_64-repodata' ...
x86_64-repodata: 1717KB [avg rate: 1920KB/s]
[vpm_] [xbps-install -S] return code: 0
# xbps-install -S samba
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/x86_64-repodata' ...
Certificate verification failed for /C=US/O=Internet Security Research Group/CN=ISRG Root X1
SSL_connect returned 1
ERROR: [reposync] failed to fetch file `https://alpha.de.repo.voidlinux.org/current/x86_64-repodata': Operation not permitted
Name Action Version New version Download size
libtdb install - 1.4.5_1 44KB
lmdb install - 0.9.29_1 81KB
ldb install - 2.3.2_1 173KB
samba-libs install - 4.14.11_1 5154KB
python3 install - 3.10.2_1 7361KB
libpytalloc-util install - 2.3.3_1 5477B
libpyldb-util install - 2.3.2_1 6824B
samba install - 4.14.11_1 7556KB
Size to download: 20MB
Size required on disk: 72MB
Space available on disk: 3033MB
Do you want to continue? [Y/n]
[*] Downloading packages
Certificate verification failed for /C=US/O=Internet Security Research Group/CN=ISRG Root X1
SSL_connect returned 1
ERROR: [trans] failed to download `libtdb-1.4.5_1' signature from `https://alpha.de.repo.voidlinux.org/current': Operation not permitted
Transaction failed! see above for errors.
# sudo xbps-install -S samba
sudo: PAM account management error: Permission denied
sudo: a password is required
# su
# xbps-install -S samba
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/x86_64-repodata' ...
Certificate verification failed for /C=US/O=Internet Security Research Group/CN=ISRG Root X1
SSL_connect returned 1
ERROR: [reposync] failed to fetch file `https://alpha.de.repo.voidlinux.org/current/x86_64-repodata': Operation not permitted
Name Action Version New version Download size
libtdb install - 1.4.5_1 44KB
lmdb install - 0.9.29_1 81KB
ldb install - 2.3.2_1 173KB
samba-libs install - 4.14.11_1 5154KB
python3 install - 3.10.2_1 7361KB
libpytalloc-util install - 2.3.3_1 5477B
libpyldb-util install - 2.3.2_1 6824B
samba install - 4.14.11_1 7556KB
Size to download: 20MB
Size required on disk: 72MB
Space available on disk: 3033MB
Do you want to continue? [Y/n]
[*] Downloading packages
Certificate verification failed for /C=US/O=Internet Security Research Group/CN=ISRG Root X1
SSL_connect returned 1
ERROR: [trans] failed to download `libtdb-1.4.5_1' signature from `https://alpha.de.repo.voidlinux.org/current': Operation not permitted
Transaction failed! see above for errors.
#
These are preliminary results for others to view.
- peebee
- Posts: 1637
- Joined: Mon Jul 13, 2020 10:54 am
- Location: Worcestershire, UK
- Has thanked: 157 times
- Been thanked: 715 times
- Contact:
Re: VoidPup32 & VoidPup64 BETA 23-Jan-22 Woof-CE build
Please use vpm in Beta+4 rather than xbps - i.e.
vpm i samba
or prepend xbps* - i.e.
SSL_NO_VERIFY_PEER=1 xbps-install -S samba
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
-
- Posts: 3844
- Joined: Fri Jul 24, 2020 10:59 pm
- Has thanked: 1633 times
- Been thanked: 527 times
Re: VoidPup32 & VoidPup64 BETA 23-Jan-22 Woof-CE build
Results posted on this distro's NEW forum site: Click here
Results posted on this distro's NEW forum site, Click here
- peebee
- Posts: 1637
- Joined: Mon Jul 13, 2020 10:54 am
- Location: Worcestershire, UK
- Has thanked: 157 times
- Been thanked: 715 times
- Contact:
Re: VoidPup32 & VoidPup64 BETA 23-Jan-22 Woof-CE build
be7e83f509df936a143030322ce295c4 VoidPup64-22.01Beta+5.iso
should fix ca-certificates issue
if not pristine install - delete /opt/vpup/vpm_holds and restart
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
- peebee
- Posts: 1637
- Joined: Mon Jul 13, 2020 10:54 am
- Location: Worcestershire, UK
- Has thanked: 157 times
- Been thanked: 715 times
- Contact:
Re: VoidPup32 & VoidPup64 BETA 24-Jan-22 Woof-CE build
2f3cb9c22d9c34d7a56f3aa0d4c163cb VoidPup32-22.01Beta+6.iso
same build state as VoidPup64
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
Re: VoidPup32 & VoidPup64 BETA 24-Jan-22 Woof-CE build
Beta +4 64 bit installs bumped to Beta +5 using the delta. /opt/vpup/vpm_holds deleted when my savefiles are scrubbed before a reboot. Working in the JWM install for now, inst-xbps now sucessfully installs sylpheed 3.70 from a local xbps file. No nags, clean terminal run. The sylpheed runs perfectly, using my link in /root to my sylpheed profile on the EXT2 Data partition. One observation. JWM wouldn't show the .desktop in the tray til I changed the .desktop icon to a .svg, LXDE didn't mind. I just used /usr/share/pixmaps/puppy/mail.svg, the default email icon. Changing the default email to sylpheed and putting that in the tray would have worked as well I guess. Still the daily driver here.
An LXDE/ydrv note, probably relevant to me only: evince segfaults when the ydrv is loaded, both in pristine installs and in my configured LXDE install, both in Beta +4 and Beta +5. No information in terminal, no missing libs show up using LDD. I didn't go any further back in testing than those Betas. Didn't see it til now as I had been using the MasterPDFEditor portable.
Cheers,
Edit: Just installed pcmanfm ver. 1.3.2 from the Void repo using vpm -i. No terminal nags or clutter. Working in the JWM install of VoidPup64 Beta +5. Up and working as the default FM. As with sylpheed, took a bit of tinkering with the .desktop icon before JWM would empanel it.
.
My pups: LxPupSc64 and Voidpup64 with LXDE ydrv and synaptics touchpad drivers, both using small savefiles for customizations. Ydrv based NoblePup64 and Fossapup64-small (both LXDE/PCManFM with no savefiles). No fdrvs throughout.
- peebee
- Posts: 1637
- Joined: Mon Jul 13, 2020 10:54 am
- Location: Worcestershire, UK
- Has thanked: 157 times
- Been thanked: 715 times
- Contact:
Re: VoidPup32 & VoidPup64 BETA 24-Jan-22 Woof-CE build
Marv wrote: Mon Jan 24, 2022 5:27 pmAn LXDE/ydrv note, probably relevant to me only: evince segfaults when the ydrv is loaded,
Hi Jim
I've rebuilt the 64-bit LXDE ydrv ......... has fixed the evince problem.
Thanks
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
Re: VoidPup32 & VoidPup64 BETA 24-Jan-22 Woof-CE build
Rebuilt ydrv loaded, evince now working in my Void64 Beta+5 LXDE install. I'll continue to use that install as my daily and see what else I bump up against. Guess I'll play a bit more with themes next. Some more PDF and spreadsheet work on the docket too. Sylpheed works flawlessly either configured as a portable or installed using inst-xbps, using the portable for now on the LXDE side, the VPM installed sylpheed, pcmanfm and gvfs on the JWM side. Both sides work well but LXDE is like an old comfortable shoe to me.
An aside: With all of the new kernels, certainly anything since 5.15.0, I no longer need a restartwm when coming out of lidsuspend. Could be hardware dependent, but it works perfectly on my i5 based all intel Fujitsu lappies circa 2012. I do it in LxPupSc64, LxPupSc, fossapup64, and now in Void64 so long as the kernel is new enough. The 5.15.0 is by memory. Leaves you right where you left off -for example in the middle of this post-. I comment out line 57 in /etc/ACPI/actions/suspend.sh.
Thanks,
My pups: LxPupSc64 and Voidpup64 with LXDE ydrv and synaptics touchpad drivers, both using small savefiles for customizations. Ydrv based NoblePup64 and Fossapup64-small (both LXDE/PCManFM with no savefiles). No fdrvs throughout.
- peebee
- Posts: 1637
- Joined: Mon Jul 13, 2020 10:54 am
- Location: Worcestershire, UK
- Has thanked: 157 times
- Been thanked: 715 times
- Contact:
Re: VoidPup32 & VoidPup64 BETA 24-Jan-22 Woof-CE build
Marv wrote: Mon Jan 24, 2022 5:27 pmAs with sylpheed, took a bit of tinkering with the .desktop icon before JWM would empanel it.
Yes - that is a problem with any "foreign" package manager which installs apps from a distro with a menu category scheme different to Pup - and given that the Pup menu category scheme is unique and different to all other distros it's a problem with all "foreign" package managers..... but we like the Pup scheme I think!
@dimkr has tackled the same issue in his work on using apt in VanillaPup but I think he may have added some sort of post-processing to apt.....
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
-
- Posts: 2427
- Joined: Wed Dec 30, 2020 6:14 pm
- Has thanked: 53 times
- Been thanked: 1203 times
Re: VoidPup32 & VoidPup64 BETA 24-Jan-22 Woof-CE build
peebee wrote: Wed Jan 26, 2022 7:13 am@dimkr has tackled the same issue in his work on using apt in VanillaPup but I think he may have added some sort of post-processing to apt.....
https://github.com/puppylinux-woof-CE/w ... /fixmenusd
Yes, I added a super simple daemon that watches /usr/share/applications and runs fixmenus if needed.
It doesn't fix the categories thing.
- OscarTalks
- Posts: 623
- Joined: Tue Jul 14, 2020 10:11 pm
- Location: London UK
- Has thanked: 2 times
- Been thanked: 247 times
Re: VoidPup32 & VoidPup64 BETA 24-Jan-22 Woof-CE build
Started testing VoidPup32 22.01 Beta+6 manual frugal install to HDD.
Fixed the missing menu icons for gftp and Light browser by editing the .desktop files.
Menu > Utility > X Virtual Keyboard does not work because xvkbd is not installed
Installed xvkbd via VPM and it works, but there is still something not quite right with the fonts (X?) for it.
Installed linphone-desktop via VPM which seems to have worked fine, dragged in all the needed dependencies including the Qt5 libs. Nice to have Linphone 4.3.2 on a 32bit Puppy with a few simple clicks.
Loaded devx and kernel_sources to try some compiling and found that I was getting a lot of unexpected errors, not sure why, need to investigate further on that. I am not avoiding the inevitable drift towards 64bit, but happy to see efforts being made to keep 32bit options alive and viable.
- Attachments
-
- linphone432-void32.jpg (56.76 KiB) Viewed 44500 times
- OscarTalks
- Posts: 623
- Joined: Tue Jul 14, 2020 10:11 pm
- Location: London UK
- Has thanked: 2 times
- Been thanked: 247 times
Re: VoidPup32 & VoidPup64 BETA 24-Jan-22 Woof-CE build
Is there by any chance a kernel_headers package for VoidPup32 ? (as is the case with ScPup)
I am still having no joy compiling anything
- peebee
- Posts: 1637
- Joined: Mon Jul 13, 2020 10:54 am
- Location: Worcestershire, UK
- Has thanked: 157 times
- Been thanked: 715 times
- Contact:
Re: VoidPup32 & VoidPup64 BETA 24-Jan-22 Woof-CE build
OscarTalks wrote: Wed Jan 26, 2022 10:01 pmIs there by any chance a kernel_headers package for VoidPup32 ? (as is the case with ScPup)
I am still having no joy compiling anything
Hi OT
Kernel 5.4 in VoidPup32 is a Github Woof-CE build from:
https://github.com/puppylinux-woof-CE/woof-CE/actions
which doesn't include a separate Kernel-headers.....
@dimkr may know why not as kernel-kit does produce them....
Void Linux has something called kernel-libc-headers - maybe relevant??
https://voidlinux.org/packages/?arch=i686&q=kernel-libc
The devx has not been tested much - what problems are you seeing?
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
-
- Posts: 2427
- Joined: Wed Dec 30, 2020 6:14 pm
- Has thanked: 53 times
- Been thanked: 1203 times
Re: VoidPup32 & VoidPup64 BETA 24-Jan-22 Woof-CE build
Yes - generally, it's a bad idea to replace a distro's kernel headers package with the kernel headers from another kernel version. This can break the C compiler, because libc headers #include the kernel headers.
It's safe to compile an application against one kernel headers version and run on another, because the kernel is backwards-compatible and most applications that try to use a newly-introduced system have some fallback for kernels that tell the application, at runtime, that the system call is unavailable.
To sum it up - Puppy-supplied kernel header packages are useless, and even dangerous. Just use the Void package.
- OscarTalks
- Posts: 623
- Joined: Tue Jul 14, 2020 10:11 pm
- Location: London UK
- Has thanked: 2 times
- Been thanked: 247 times
Re: VoidPup32 & VoidPup64 BETA 24-Jan-22 Woof-CE build
Installing the kernel-libc-headers package via VPM has helped a lot
I presume this should be added to the devx?
I was now able to compile PSIP-1.42 with the dependencies portaudio-19 pjproject-1.16 and osxcart-1.2.0
My builds now have some updates to the default buddies list with (now dead?) ekiga stuff removed and other nice test addresses added.
As a test I also compiled latest osmo-0.4.4 which is strictly GTK3 and configured --without-contacts to avoid the huge optional webkit2gtk dependency.
There is still a bit of an issue with gettext
VPM reports it as already installed which it is, but it lacks some of the executables which are found in the Debian package.
The osmo build was showing errors that msgfmt was "command not found"
(not fatal but causes a problem for NLS ?)
I tried compiling pmcputemp-0.90
That complained that xgettext was "command not found"
- Attachments
-
- psip-void32.jpg (50.22 KiB) Viewed 44416 times
-
- osmo044-void32.jpg (95.75 KiB) Viewed 44416 times
- peebee
- Posts: 1637
- Joined: Mon Jul 13, 2020 10:54 am
- Location: Worcestershire, UK
- Has thanked: 157 times
- Been thanked: 715 times
- Contact:
Re: VoidPup32 & VoidPup64 BETA 27-Jan-22 Woof-CE build
ee7d27f71c257227412b3788e6e27aaa VoidPup32-22.01Beta+7.iso
6d2896d7ed2b844fe56d835746bf54f8 VoidPup64-22.01Beta+6.iso
Better support for .xbps files, right click options extended, new devx with kernel-libc-headers included
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
- OscarTalks
- Posts: 623
- Joined: Tue Jul 14, 2020 10:11 pm
- Location: London UK
- Has thanked: 2 times
- Been thanked: 247 times
Re: VoidPup32 & VoidPup64 BETA 27-Jan-22 Woof-CE build
dir2pet fails with:-
** (gtkdialog4:25372): ERROR **: 09:45:34.682: gtkdialog: Error in line 90, near token '</default>': syntax error
Aborted creation of PET package.
So obviously right-click > Create a Pet package doesn't work either.
- OscarTalks
- Posts: 623
- Joined: Tue Jul 14, 2020 10:11 pm
- Location: London UK
- Has thanked: 2 times
- Been thanked: 247 times
Re: VoidPup32 & VoidPup64 BETA 27-Jan-22 Woof-CE build
Thanks for the updates to 22.01Beta+7 and devx (32bit)
Having compiled a package from source I can create a .xbps package using dir2xbps
eg osmo-0.4.4-i686 (directory tree) produces osmo-0.4.4_1.i686.xbps (in /root or wherever)
But then attempting to install this as per instructions with:-
inst-xbps osmo-0.4.4_1.i686.xbps
Does not work. There is a flash of the screen, terminal returns to prompt with no output and nothing installs.
- peebee
- Posts: 1637
- Joined: Mon Jul 13, 2020 10:54 am
- Location: Worcestershire, UK
- Has thanked: 157 times
- Been thanked: 715 times
- Contact:
Re: VoidPup32 & VoidPup64 BETA 27-Jan-22 Woof-CE build
Seems to work OK for me..... did you have anything else installed?
.
.
/usr/bin/inst-xbps was overcomplicated so simplified version attached (remove -false.gz and make executable)
- Attachments
-
- inst-xbps-false.gz
- (1.68 KiB) Downloaded 94 times
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
- OscarTalks
- Posts: 623
- Joined: Tue Jul 14, 2020 10:11 pm
- Location: London UK
- Has thanked: 2 times
- Been thanked: 247 times
Re: VoidPup32 & VoidPup64 BETA 27-Jan-22 Woof-CE build
No, I completely deleted my save-folder when I upgraded from +6 to +7 and I just tried again with a fresh pfix=ram boot. Only did the GB settings in quick-setup and nothing else.
Still getting the same error from dir2pet when it gets to the stage of bringing up the GUI
How peculiar. Maybe I am doing something silly, but I make .pets quite a lot in loads of different Pups.
I tried substituting gtkdialog from Dpup Stretch but it did the same.
Good news with the inst-xbps script you posted - that now works here.
I made my package top-directory name follow the same name and number conventions as the completed package
Not sure how strict this is (hyphens, underscores and dots)
So psip-1.42_1.i686 (top directory) packages up as psip-1.42_1.i686.xbps
That now installs correctly with inst-xbps <package name>
It doesn't run fixmenus though, wonder if that can be added.
- rockedge
- Site Admin
- Posts: 6556
- Joined: Mon Dec 02, 2019 1:38 am
- Location: Connecticut,U.S.A.
- Has thanked: 2760 times
- Been thanked: 2640 times
- Contact:
Re: VoidPup32 & VoidPup64 BETA 27-Jan-22 Woof-CE build
@peebee I'm interested in the simplified init-xbps
and if it will work in KLV. I will download it and give it a try out and will consider swapping your version in if tests are successful.
It doesn't run fixmenus though, wonder if that can be added.
it would mean either making specific init-xbps
programs for VoidPup or KLV or for WDL or put a function in that can identify if the desktop is JWM and needs a fixmenu
triggered.
- peebee
- Posts: 1637
- Joined: Mon Jul 13, 2020 10:54 am
- Location: Worcestershire, UK
- Has thanked: 157 times
- Been thanked: 715 times
- Contact:
Re: VoidPup32 & VoidPup64 BETA 27-Jan-22 Woof-CE build
rockedge wrote: Fri Jan 28, 2022 3:43 pm@peebee I'm interested in the simplified
init-xbps
and if it will work in KLV.
I just removed the extra terminal as inst-xbps is run from terminal in VoidPup anyway and I couldn't work out how to fix the code!
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
- peebee
- Posts: 1637
- Joined: Mon Jul 13, 2020 10:54 am
- Location: Worcestershire, UK
- Has thanked: 157 times
- Been thanked: 715 times
- Contact:
Re: VoidPup32 & VoidPup64 BETA 27-Jan-22 Woof-CE build
OscarTalks wrote: Fri Jan 28, 2022 3:39 pmStill getting the same error from dir2pet when it gets to the stage of bringing up the GUI
How peculiar.
devx loaded?? clutching at straws....
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
- OscarTalks
- Posts: 623
- Joined: Tue Jul 14, 2020 10:11 pm
- Location: London UK
- Has thanked: 2 times
- Been thanked: 247 times
Re: VoidPup32 & VoidPup64 BETA 27-Jan-22 Woof-CE build
No, devx is not loaded.
But what is in your "testpet" directory?
If I make a "testpet" with just a few very small files it works and the GUI pops up
When I start to load in a few files of any size in "testpet" it stops working and the error appears.
So something to do with whatever is reading the size of the installed package (which displays in the GUI) may be causing it?
EDIT:- tried devx -no change
Re: VoidPup32 & VoidPup64 BETA 27-Jan-22 Woof-CE build
I'm in VoidPup64 Beta +6 with the LXDE ydrv and I'm seeing this error when trying to create a pet, 42kb and 8 files. Just a little bodge, done before in several pups. Just a wrapper script, wmctrl, and a .desktop to put the calculator always on top. No devx loaded.
Code: Select all
GUI window
Press ENTER key to bring up a GUI window that will help you to create
a database entry for the package. This will be shown in a text editor
for saving somewhere, also written to file 'pet.specs' inside the pkg.
Press ENTER:
aVoidontopcalc bBusiness cEMPTY dPerform simple and scientific calculations eVoidontopcalc f72 gEMPTY hyes iEMPTY
** (gtkdialog4:13683): ERROR **: 15:13:49.325: gtkdialog: Error in line 90, near token '</default>': syntax error
Aborted creation of PET package.
#
I'm happy wrt themes for now. The three themes from @dimkr posted here viewtopic.php?p=47777#p47777 and in VanillaDPup meld gtk-2 and gtk-3 well. I got tired of manually editing the gtk-3 themes and figuring out what themes in the package support both gtks so I put together the bare bones of a switcher for the LXDE VoidPup. Ugly but works. The nudge came from here: https://gist.github.com/albfan/88cbf404 ... 5df52e334e VoidPup does not use gtk-3.0 settings.ini, thus most of the differences.
Code: Select all
#!/bin/sh
# rudimentary script to config gtk3 themes in LXDE/openbox VoidPup64
GTK_VERSION=3
# paths
user_home=/root
system_theme_dir=/usr/share/themes
CURRENT_GTK_THEME=$(grep sNet/ThemeName= /root/.config/lxsession/LXDE/desktop.conf | awk '{split($0,a,"="); print a[2]}')
echo
echo "Your theme is: ${CURRENT_GTK_THEME}"
if [ $# -eq 0 ]; then
echo
echo "Avaliable Gtk${GTK_VERSION} themes:"
find ${system_theme_dir} -type d -name "gtk-${GTK_VERSION}.0"| awk -F'/' '{print " " $5}'
if [ -d ${theme_dir} ]; then
find ${theme_dir} -type d -name "gtk-${GTK_VERSION}.0" | awk -F'/' '{print " " $5}'
fi
echo
read -p "To change to one of them cut and paste it here, return exits : " CHOSEN_THEME
if [ ! $CHOSEN_THEME ]; then
echo "Now exiting without changing theme. Theme remains: " ${CURRENT_GTK_THEME}
else
echo "Now replacing " ${CURRENT_GTK_THEME} " with " ${CHOSEN_THEME} " as the openbox desktop and LXDE gtk-3.0 theme"
sed -i "s/${CURRENT_GTK_THEME}/${CHOSEN_THEME}/" /root/.config/lxsession/LXDE/desktop.conf
sed -i "s/${CURRENT_GTK_THEME}/${CHOSEN_THEME}/" /root/.config/openbox/lxde-rc.xml
echo
CURRENT_GTK_THEME=$(grep sNet/ThemeName= /root/.config/lxsession/LXDE/desktop.conf | awk '{split($0,a,"="); print a[2]}')
echo "Done, your current gtk-3.0 theme is now" $CURRENT_GTK_THEME
echo "Now restarting the window manager."
sleep 2
restartwm
fi
fi
My pups: LxPupSc64 and Voidpup64 with LXDE ydrv and synaptics touchpad drivers, both using small savefiles for customizations. Ydrv based NoblePup64 and Fossapup64-small (both LXDE/PCManFM with no savefiles). No fdrvs throughout.