Puppy Linux Discussion Forum

dimkr wrote: ↑Tue Jan 24, 2023 6:19 am

radky wrote: ↑Mon Jan 23, 2023 9:58 pm

However, I assume there are other factors in play since Chrome and IME function properly in FossaPup64-9.5 (which has gtk3 but no gtk4 libs).

What Chrome version are you using and where does it come from?

Typically, I do not use the chrome browser and have little experience with it, but currently I'm testing IME in FossaPup64 with the chrome portable prepared by 'mikewalsh' for Puppy Linux. After placing the portable app in /mnt/home, the included 'LAUNCH' script handles the run-as-spot launch of the browser.

In this scenario, the most recent chrome release is available via the URl at the bottom of the first post in the following Puppy forum thread:

https://www.forum.puppylinux.com/viewto ... p=479#p479

On first use in FossaPup64, after accepting the automatic upgrade option (requires ar), the chrome browser loads the following version:

Version 109.0.5414.74 (Official Build) unknown (64-bit)

@jrb

Can you let me know what package needs compiling in Meson?

https://forum.puppylinux.com/viewtopic. ... 384#p79384

I might try to see if can help out.

Well, how did I even miss this conversation ? Jammy64 has become my daily driver!

There is a lot more coming next in this release - this is just a development version !

Jasper wrote: ↑Tue Jan 24, 2023 3:14 pm

@jrb

Can you let me know what package needs compiling in Meson?

https://forum.puppylinux.com/viewtopic. ... 384#p79384

I might try to see if can help out.

@Jasper
Instructions at https://github.com/saivert/ddb_output_pw
Source package at https://github.com/saivert/ddb_output_p ... s/main.zip
It gave me a python error when I tried compiling. Think I was in Jammy64 at the time.

Thanks, J

@thinkpadfreak I took a look at the Chromium source code and I think I found the difference between Fossapup and others that makes IME work.

It's XLIB_SKIP_ARGB_VISUALS=1, set by /etc/profile even before woof-CE was born. Once unset, IME works fine even without installing GTK+ 4, including in a Debian 11 based dpup with no GTK+ 4 package.

EDIT: more details in https://github.com/puppylinux-woof-CE/woof-CE/pull/3867

@jrb

I did download the additional lib required but it fails to progress.

The 2x files I moved to various Lib locations with no success.

This is on FossaPup64-95.

Will try with Jammy next. Different error here.

dimkr wrote: ↑Thu Jan 26, 2023 7:04 am

It's XLIB_SKIP_ARGB_VISUALS=1, set by /etc/profile even before woof-CE was born. Once unset, IME works fine even without installing GTK+ 4, including in a Debian 11 based dpup with no GTK+ 4 package.

I am now running EasyPup 2.5 based on debian buster, and have confirmed that unsetting the environment variable (?) makes IME usable with Chrome.

thinkpadfreak wrote: ↑Thu Jan 26, 2023 12:23 pm

I am now running EasyPup 2.5 based on debian buster, and have confirmed that unsetting the environment variable (?) makes IME usable with Chrome.

Great! This fix will be part of Vanilla Dpup 9.3.6, which will be released on Saturday, and the next jammy64 build will run on February 2nd. The fix will slowly propagate into @peebee's releases as well, once they get rebuilt with woof-CE after 5596ade.

Jasper wrote: ↑Thu Jan 26, 2023 10:37 am

@jrb

I did download the additional lib required but it fails to progress.

The 2x files I moved to various Lib locations with no success.

This is on FossaPup64-95.

Will try with Jammy next. Different error here.

@Jasper , Thanks for trying. I hope you succeed. In the meantime I have installed alsaplayer, available as alsaplayer-common in PPM. I don't remember ever using it before but its very lightweight and does everything I need. Internet says it will handle Shoutcast/Icecast but I haven't figured out how and not something I use.

Cheers, J

One problem I'm having with my local WoofCE build of Jammy64 is Packages-puppy-common64-official. PPM shows it greyed out when I try to "Choose repositories" and will not access it. Have tried a few mods of DISTRO_PET_REPOS but so far no luck.

jrb wrote: ↑Fri Jan 27, 2023 7:54 pm

One problem I'm having with my local WoofCE build of Jammy64 is Packages-puppy-common64-official. PPM shows it greyed out when I try to "Choose repositories" and will not access it. Have tried a few mods of DISTRO_PET_REPOS but so far no luck.

Use apt! apt is present in jammy64, and that is why PPM is not allowed to install any program you may find in any Ubuntu/Debian repos.

@dimkr, as I expected, confusion happens. I have a PR open which will add a documentation file giving information on the same. Won't be able to test that until 1st of next month because I have exhausted my GitHub actions limit this month, and till then the PR would not merge.

BTW, if you're interested, there is a bdrv.sfs in jammy64 which contains apt.

And those who may want to understand more on the issue-

I opened an issue in GitHub which explained that using PPM to install packages destroys your /bin many a times! @dimkr, took action on this and explained that PPM has now become no good for installing packages with deep dependencies-most of the Ubuntu/Debian packages will have that. So, he then enabled BDRV in jammy64.

So, it is a feature for jammy64 to have restrictions on PPM, not a disability for jammy itself. Restrictions on PPM are intended!

This restriction can be removed if anyone volunteers to fix the various safety and reliability issues with PPM.