waddlesplash changed the topic of #haiku to: Open-source operating system that specifically targets personal computing. | https://haiku-os.org | Nightlies: https://download.haiku-os.org | Bugtracker: https://dev.haiku-os.org | SCM: https://git.haiku-os.org/ | Logs: https://oftc.catirclogs.org/haiku/ | Matrix: #haiku:matrix.org | XMPP: #haiku%irc.oftc.net@irc.jabberfr.org
vdamewood has joined #haiku
<scanty> anyone around at this hour?
HaikuUser2 has joined #haiku
<Molnija> sadly yes. i say sadly because i am not a current haiku user
HaikuUser2 has quit []
<Molnija> what's your business, what's your shame, scanty
<scanty> oh, i don't remember anymore.
tuaris has joined #haiku
<Molnija> crikey
<Molnija> well if there's anything #haiku can help you with, let us know, okay?
<erysdren> meow
<scanty> oh i remember
talos has quit [Quit: The Lounge - https://thelounge.chat]
<scanty> do i need to explicitly lock and quit a window when i'm done with it?
talos has joined #haiku
<scanty> i'm getting segfaults on quit
<scanty> thinking maybe it's time for malloc debug.
<scanty> i just don't want to dive into something that may not be necessary\
<Molnija> my instinct, I could be wrong, is that segfaults on quit are rounds-to-always a bug in the relevant program
<phschafft> I would say a segfault that is not caused by the OS or hardware is always a bug. end of story. ;)
<erysdren> SDL2/SDL3 also segfaults on exit in Haiku apps
<erysdren> some GL context double-free bug
<erysdren> which nobody has tried to fix
<erysdren> because haiku apps rarely use SDL2/SDL3
talos has quit [Quit: The Lounge - https://thelounge.chat]
<scanty> well, i'm done for now.
<phschafft> welcome back erysdren btw.
<scanty> fresh eyes tomorrow.
<phschafft> scanty: nachti!
<scanty> hi there phschafft
talos has joined #haiku
<phschafft> :)
<erysdren> hi
<nekobot> [haikuports] OscarL pushed 42 commits to branch master: https://github.com/haikuports/haikuports/compare/637c008d6d79...6e70a085c195
<nekobot> • OscarL (773dc55c): astroid: drop Python 3.9 support.…
<nekobot> • OscarL (532affa6): bottle: drop Python 3.9 support.…
<nekobot> • OscarL (7695e795): certifi: drop Python 3.9 support.…
mmu_man has quit [Ping timeout: 480 seconds]
<nekobot> [haikuports] OscarL pushed 1 commit to branch master: https://github.com/haikuports/haikuports/compare/6e70a085c195...d6f676bfedb1
<nekobot> • OscarL (d6f676bf): python3.14: update to version 3.14.0rc3. (#12939)
<nekobot> [haikuports] OscarL pushed 1 commit to branch master: https://github.com/haikuports/haikuports/compare/d6f676bfedb1...cde98336d3cd
<nekobot> • OscarL (cde98336): voxophone: retire recipe. (#12932)…
<nekobot> • OscarL (17a9eca7): flit_scm: drop Python 3.9 support.…
<nekobot> [haikuports] OscarL pushed 6 commits to branch master: https://github.com/haikuports/haikuports/compare/cde98336d3cd...cf1e4de166ac
<nekobot> • OscarL (8c454ad3): ifaddr: drop Python 3.9 support.…
<nekobot> • OscarL (976a4b52): lazy_object_proxy: drop Python 3.9 support.…
SrainUser_ has joined #haiku
OscarL has joined #haiku
<OscarL> mmm, did our regular channel operators got fired? :-P (odd not seeing waddlesplash with an @ at front :-D)
<erysdren> hmm?
<erysdren> wdym
<erysdren> also howdy OscarL
<OscarL> hey erysdren. in the user list this client shows me... channel ops always appear with @ as "nick prefix".
SrainUser has quit [Ping timeout: 480 seconds]
SrainUser_ is now known as SrainUser
<OscarL> last few days, waddlesplash appears without @, and today I only see one channel op, so... thought... that's kinda weird.
<erysdren> hmmm
<erysdren> odd
<OscarL> k. down to 11 recipes/packages that need to drop Python 3.9 support. Took me quite a few hours, but things went smoother than I expected.
<OscarL> (specially considering that I only locally tested builds for some random recipes... as the netbook has been thermally-throtling all day... hot day down here :-/)
Aedil has joined #haiku
<zdykstra> feelin' hot hot hot
<OscarL> +36 C and we didn't hit spring down here... not nice. Also... nice you read you zdykstra :-)
<zdykstra> 36C is rough. Do you at least have wind?
<OscarL> Sometimes... too much :-) (today, not enough, though!)
<OscarL> Summer time with hot winds... feels like living inside an air fryer :-D
TMM has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM has joined #haiku
<nekobot> [haikuports] OscarL pushed 4 commits to branch master: https://github.com/haikuports/haikuports/compare/cf1e4de166ac...e3436c8f8670
<nekobot> • OscarL (8f0aa87c): pip: drop support for all but current "default Python".…
<nekobot> • OscarL (b6c238cb): wheel: drop Python 3.9 support.…
<nekobot> • OscarL (b6b67c89): setuptools_scm: drop Python 3.9 support.…
WoC has quit [Remote host closed the connection]
<nekobot> [haikuports] OscarL pushed 3 commits to branch master: https://github.com/haikuports/haikuports/compare/e3436c8f8670...b9d4cac989e0
<nekobot> • OscarL (a47af1cd): installer: drop Python 3.9 support.…
<nekobot> • OscarL (5341b532): setuptools: drop support for all but "default Python".…
<nekobot> • OscarL (b9d4cac9): typing_extensions: drop Python 3.9 support.…
<nekobot> [haikuports] OscarL pushed 3 commits to branch master: https://github.com/haikuports/haikuports/compare/b9d4cac989e0...114e05afa443
<nekobot> • OscarL (b15e9801): pyproject_hooks: drop Python 3.9 support.…
<nekobot> • OscarL (a3b34c45): packaging: drop Python 3.9 support.…
<nekobot> • OscarL (114e05af): tomli: drop Python 3.9 support.…
GNU2Linux has quit [Quit: Connection closed for inactivity]
<nekobot> [haikuports] OscarL pushed 1 commit to branch master: https://github.com/haikuports/haikuports/compare/114e05afa443...7e86ffed973b
<nekobot> • OscarL (7e86ffed): flit_core: drop support for Python 3.9. (#12944)…
<OscarL> That should be the last one. /me takes a break.
<erysdren> rest well OscarL
tuaris has quit [Quit: tuaris]
MisthaLu has joined #haiku
OscarL has quit [Remote host closed the connection]
jmairboeck has joined #haiku
HaikuUser2 has joined #haiku
HaikuUser2 has quit []
OrngBomb has joined #haiku
OrangeBomb has quit [Ping timeout: 480 seconds]
OrngBomb is now known as OrangeBomb
bbjimmy has quit [Ping timeout: 480 seconds]
ChaiTRex has quit [Remote host closed the connection]
neoncortex has quit []
ChaiTRex has joined #haiku
mmu_man has joined #haiku
HaikuUser has quit [Ping timeout: 480 seconds]
Aedil has quit [Quit: leaving]
MisthaLu has quit [Quit: Leaving]
vdamewood has quit [Quit: Textual IRC Client: www.textualapp.com]
jmairboeck has quit [Ping timeout: 480 seconds]
diver1 has joined #haiku
diver has quit [Read error: Connection reset by peer]
dby has joined #haiku
bbjimmy has joined #haiku
SrainUser has quit [Remote host closed the connection]
SrainUser has joined #haiku
itaipu has quit [Ping timeout: 480 seconds]
itaipu has joined #haiku
bbjimmy has quit [Quit: Vision[]: i've been blurred!]
<phschafft> good morning.
* phschafft checks the cookie bowl. also adds a few chocolate cookies today.
GNU2Linux has joined #haiku
* coolcoder613_ drops in a few honey cookies he baked friday
<phschafft> uh! :))
Samanth0r has joined #haiku
itaipu has quit [Ping timeout: 480 seconds]
bbjimmy has joined #haiku
itaipu has joined #haiku
nephele has joined #haiku
Samanth0r has quit [Remote host closed the connection]
mmu_man has quit [Ping timeout: 480 seconds]
<nephele> scanty: the OS can't distinquish between a memory bug that is irrelevant and one that is relevant, you could argue that a memory problem on quiting a window that only concerns internal window data is not relevant, but one dealing with data you want to save it (since the OS will clean up either way), so this will always show a crash dialog... so in that sense, yes it is something that should be fixed
mmu_man has joined #haiku
nephele has quit [Quit: Vision[]: i've been blurred!]
jmairboeck has joined #haiku
scanty has quit [Quit: Vision[]: i've been blurred!]
scanty has joined #haiku
vezhlys has joined #haiku
chilledfrogs has quit [Quit: connection reset by purr]
<swiftbanana[m]> How does one uses haikuporter to build a x86 package on x86_gcc2?
<jmairboeck> add the suffix _x86 to the package name argument
<jmairboeck> e.g. haikuporter foo_x86
<swiftbanana[m]> Hm
<swiftbanana[m]> It says "Error netsurf_x86 not found in repository"
Chai-T-Rex has joined #haiku
<jmairboeck> did you enable SECONDARY_TARGET_ARCHITECTURES="x86" in haikuports.conf?
<swiftbanana[m]> Probably not
ChaiTRex has quit [Ping timeout: 480 seconds]
chilledfrogs has joined #haiku
mmu_man has quit [Ping timeout: 480 seconds]
mmu_man has joined #haiku
Aedil has joined #haiku
<swiftbanana[m]> That seems to have done the trick, thank you @jmairboeck
erysdren has quit [Ping timeout: 480 seconds]
GNU2Linux has quit [Quit: Connection closed for inactivity]
erysdren has joined #haiku
<nekobot> [haikuports] korli pushed 1 commit to branch master: https://github.com/haikuports/haikuports/compare/7e86ffed973b...fdf71fafdd04
<nekobot> • korli (fdf71faf): expat: bump version
dby has quit [Quit: Vision[]: i've been blurred!]
TMM has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM has joined #haiku
Aedil has quit [Quit: leaving]
HaikuUser has joined #haiku
HaikuUser has quit []
<scanty> anyone around? i was considering what an "expected" boot time for haiku. i timed the process from grub to desktop, and it took 56sec
dodo75 has quit [Quit: Vision[]: i've been blurred!]
<scanty> on a quad xeon 3.2 with 16GB RAM
dodo75 has joined #haiku
<B2IA> (floodlight) I haven't timed it, but it always feel "fast""
<scanty> maybe it takes some time to mount a few volumes at boot time.
christech2 has joined #haiku
OscarL has joined #haiku
<OscarL> darn thermal throttling, makes this N4020 feel like an Atom N450 :-(
<OscarL> scanty: in my far-from scientific "testing"... seems boot up times are fast on clean/new installs, and seem to get progressively (but slowly) slower overtime, depending on:
<OscarL> 1) number of installed packages. 2) number of "states" under /system/packages/administrative/, 3) number of other volumes to be scanned at boot time.
<OscarL> I had one install on HDD that became very slow too boot up for some reason (after a couple years of usage for HaikuPorts work). Even after "clean ups" seemed too slow.
<OscarL> tried enabling timestamps on the syslog, to see if I could figure out where the time was being spent...
jmairboeck has quit [Quit: Konversation terminated!]
<OscarL> was unable to figure out things that time, other that seemed to be some 12s/20s "pauses" without any logging. Dunno... perhaps the HDD became overly fragmented?
<OscarL> I remember there was at least one ticket about boot times on Trac, now I'm faling to find it :-/
WoC has joined #haiku
<scanty> hm
<scanty> i have no idea really.
<scanty> i don't specifically recall boot times any faster in earlier times
tuaris has joined #haiku
<OscarL> nothing notable on syslog? I've seen some SATA/AHCI controllers take their sweet time, sometimes with scary looking messages about interfaces being reset, or similar.
<OscarL> scanty: I guess you could try enabling timestamps for syslog (from ~/config/settings/kernel/driver/kernel file), "rm /var/log/syslog", and then reboot, then inspect the new syslog for anything odd?
<OscarL> scanty: another thinggie... nightlies have more debug output (and I think less optimized?) than releases, so that might affect things a bit too.
<christech2> afternoon
<OscarL> mmm, seems using "site:https://dev.haiku-os.org/" on a google search doesn't works anymore? perhaps due to Anubis? (haven't used google in a long time so... maybe got broken before)
<OscarL> hello there christech2.
<christech2> got my Haiku machine back up at home
<christech2> yay
<OscarL> nice :-)
<christech2> AMD Phenom II.. a bit old but still going
<OscarL> Heh, my fastest machine is a Phenom II X4 925.
<OscarL> (not using it much since a few months, since I had to change the motherboard for a crappier, but working, one)
<christech2> I paid $50 USD for the motherboard, cpu and 16GB of ram from a coworker a few years ago
<christech2> my other Haiku machine is a Xeon
<christech2> circa 2014
<OscarL> I also bought mine from a co-worker, but originally it had an Athlon II X2 245 (I bought it in mid 2012, the year I finally dropped win98 :-D... was using an Athlon T-Bird @900 till that point).
<christech2> nice
<OscarL> (I got the x4 Phenom for "cheap enough" in 2020, IIRC)
<OscarL> mmm I think it was actually 2022, yeah... was already visiting this channel again.
<OscarL> christech2: Haiku will run very nicely on the Phenom... only bad thing is the lack of a P-States driver, to avoid running it at its max freq/voltage all the time.
<christech2> full steam ahead
<OscarL> shameless plug for a simple temperature monitor driver you can use, if you care: https://github.com/OscarL/amd_temp (and depending on your motherboard, perhaps https://github.com/OscarL/it87 may work too)
<christech2> it does get hot in the garage when im running it
<christech2> I'll check it out, thanks.
<OscarL> I have been working on one for some Winbond SuperIO chips (due to my change of motherboard for the Phenom). Works OK at the moment, but haven't published yet.
WoC has quit [Remote host closed the connection]
<christech2> I've got an Asus motherboard
<christech2> RoG Crosshair V Forumula
<christech2> I'll test it out
<christech2> bbl
* christech2 is idle: BRB
WoC has joined #haiku
<OscarL> that looks like an insane mobo. would be nice to have it maxed out with a Phenom II X6 1100T :-D
OscarL has quit [Quit: "bbl, I hope"]
kescher has quit [Quit: Bye]
kescher has joined #haiku
WoC has quit [Remote host closed the connection]
WoC has joined #haiku
neoncortex has joined #haiku
SrainUser has quit [Remote host closed the connection]
Babaj has joined #haiku
OrngBomb has joined #haiku
OrangeBomb has quit [Ping timeout: 480 seconds]
<glassnerves> Night
<erysdren> night