Somehow, openSUSE has built SeaMonkey without ChatZilla.

So I dumped out the tarball into my home folder for now.

how could you build SM without Chatzilla? i would of thought to build it without the composer rather than chatzilla

Needs an --enable-irc in the mozconfig. You can pick the xpi fro the official tarball.

LOL

Just toss it in there.

I don't know that I want their package anyway. It's 2.53.14.

frg_Away: Is there a way you could maybe drop the --enable-irc and just make it so you have to build ChatZilla?

I think it would be easier than reporting a bug on a distribution and waiting around for anyone to care.

Or maybe drop that and make it --disable-irc if you realyl don't want it?

I think it got overlooked. I don't think they did this deliberately.

we could probably invert it and provide a disable-irc. Lighting is on by default Just needs --enable-irc --enable-dominspector --enable-debugqa

debugqa is only enabled in beta builds.

I wonder if I could just grab the SeaMonkey RPMs from obs and pound pound pound ignore the signature and then dump Chatzilla's xpi in with it.

This is beginning to be a habit. I've already done this with yt-dlp, mullvad, and btrfsprogs.

just report it. Will be fixed fast I bet

First ve make a chocolate moooooseeee.

Here moosey moooseey.

Okay, it says it needs a newer nss.

No problem. BREAK SEAMONKEY pound pound pound.

Eh, it works.

THey're building it with gcc 7.5.0?

It needs the latest esr102 ess. If they privode a lower one they miss sec fixed and you should use the internal nss.

3.90 May 15th they updated this.

If that's the system one, that's probably what their Firefox ESR 115.1 is using.

--with-system-ns is in the Firefox buildconfig.

--enable-alsa <---- Does this even do anything anymore?

I've used seamoney since 2009. Love it.

3.90 is later and the build should not complain.

IsambardPrince: enables alsa?

should make sense for as long as it's possible to use ALSA directly with SeaMonkey.

now *if* the distribution defaults to using pulseaudio directly, then perhaps that shouldn't be there?

s/be there/be enabled/

njsg: and now the latest hotness is Pipewire

should we care?

good morning frg_Away

tomman: yes because it will end pulse audio and alsa

because their way is the right way THE ONLY way

pipewire will be the only system media subsystem like systemd is

tomman: no idea, haven't read much about it, although I think I've seen it discussed in gentoo-user or other gentoo mailing list.

my only major criticism in the pulseaudio-alsa mess is when people come up with the "but alsa only allows a single application at once" thing, which isn't true, although I think there was something causing dmix to be disabled by default for some surround-capable devices. Last time I had to use pulseaudio software, apulse was a working workaround.

CaptainTobin hi

njsg: my experiences with dmix were awful, tho

nothing replaces a real sound card

but those are pretty much extinct nowadays

(thaaaaaanks, Creative!)

my experience with Pulse on the other side has been good, as long as it doesn't get in my way

but if the machine has a legit sound card with multiple hardware streams, then I'll disable/kill Pulse on those setups, as its services are not useful for me on those platforms

fyi just pulled in another set of ubuntu updates and lag problem appears to be gone, so far. it may still crop up after some more usage but so far so good

yeah spoke too soon. it's lagging again.

nuts...

hyc: was off for a bit trying rebooitng stuff. are you talking about what could be an internet issue? reason i was gone rebooting was to make sure problem was not on my end after I wasted about 1/2 hour rebooting and retesting after reconnecting one thing at a time and not finding anything the problem here disappeared so if that is what you are seeing i suspect the issue is somewhere in...

...the cloud.

the ONLY clouds i care about are vape clouds

which is why I am now doing contracted work to do a basic info and conservatively social website for the local vape shop providers of fine nicotine and hemp products.

every time I gear up to do BinOC things.. something comes up.. still i can use this to push my own work forward

plus after over a decade isn't it time I also did the minimally nessisary for mobile web lol

i figure at certain width just 100% and use old people font sizes

... basic mobile

with xhtml 1.0/transitional of course

the ONLY lazy doctype allowed

I really do need to tighten it up and get it sent through the xml parser instead of html

I'm more of a fan of XHTML 1.0/Strict, but that's because JavaServer Faces "converted" me... forcefully :D

i admit it i didn't go 1.0/strict because I was too lazy

on the flip side, if I get a XML rendering error from my browser, that means somewhere deep into my presentation layer I did a no-no

went xhtml.. but not strict

also reminds me that time I had to file a bug at some JavaScript library because XHTML forces tag names to lowercase, but the lib was expecting uppercase tags instead

i want to do a successor spec based on xhtml 1.0 as a document markup language .. as well as a xul successor with matched features but obviously execution context ..

that one was fun (and remains unfixed)

ended monekypatching that one, but uuuuugh...

filled 8 YEARS AGO!

still... untriaged, unanswered, unfixed, and unloved

and I guess it will remain that way, as the last commit to that repo was in January 2020

Basically start with xhtml 1.0 spec and just call it xhdml eXtensable HyperDocument Markup Language and xhuml eXtensable HyperUi Markup Language

tomman: ah, perhaps the problem was lack of hw mixer then. or maybe both (that and dmix not being on out of the box for some cards)...

njsg: in the years I used Fedora, dmix was never the default, especially after they started enforcing Pulseaudio as the default sound server

you had to craft your own .alsarc

and even then that introduced lag or outright didn't worked at all

Pulse or Pipewire hijack apps that use "ALSA" anyway.

At least Poettering is officially at Microsoft now.