Messages

46

Internet / Re: Dooble releases-Qt6

« on: August 26, 2024, 09:44:09 am »

Yeah that will be the 6.2.8 libs with the exception of qtwebengine that's still at 6.2.6. I guess I could/should package up a build wih those binaries.

Given there is now also https://lists.qt-project.org/pipermail/announce/2024-July/000505.html I guess I could update the core libs (minus qtwebengine) to 6.2.9.

47

Internet / Re: Dooble releases-Qt6

« on: August 26, 2024, 05:38:49 am »

The core DLLs in post 1 of that thread are still current (November 2023).

That build is still current, but to support drive letters in the urlbar, needs the updated DLLs from yesterday.

48

Internet / Re: Dooble releases-Qt6

« on: August 25, 2024, 09:45:38 am »

does file:///c:\config.sys work with the qt5 build? If so,  I'll examine the changes more closely...

My changes are at https://github.com/psmedley/qt6-webengine-os2/commit/0e53634c9674d1520049ebba82dc8d0d463021dd

49

Internet / Re: Dooble releases-Qt6

« on: August 25, 2024, 07:42:22 am »

https://smedley.id.au/tmp/qt6weben-6.2.6-20240825.zip has the rebuilt qt6web*.dll. These should be unzipped over the top of the ones from the last Qt 6.2.6 drop. Not tested locally.

EDit: something like:
file:///c:/config.sys works
but
file:///c:\config.sys doesn't  work

50

Internet / Re: Dooble releases-Qt6

« on: August 25, 2024, 01:21:06 am »

Here's hoping Paul can add this to the QT6 version too...

It'll happen. I fixed my build issues, currently at [1482/3105] so ~1600 source files left to  compile from the initial ~25,600.  Patches are also in place to  support drive letters in the URL  bar. Hopefully some time later today assuming no unforeseen issues.

51

Internet / Re: Dooble releases-Qt6

« on: August 24, 2024, 01:22:33 am »

<sigh> [listing of woes] Why is everything so hard?

In Ancient Times folk would have said something like, "God is testing you for a Great Task, so go with it." These days, dunno. Maybe you're due to have one of those life-rebooting Road To Damascus Warpstock experiences in due course.

OK it had been a while since I'd built the Qt 6.2 based browser. Turns out that I had some remnants of qt 6.2.8  code in there (which is based on a chromium version what we can't yet build) left over.

Hopefully,  I'm on the path to being able to build an updated DLL again.... and I'll include the url fixes.

On a positive note,  whilst investigating a build break,  I think I fixed a problem generating filename.js.compressed caused by brotli.exe not using binary mode on stdout. Time will tell, that may allow me to revert some hacks

52

Internet / Re: Dooble releases-Qt6

« on: August 23, 2024, 10:44:20 pm »

Thanks Dave - it's working well here!

 There is a long standing bug in Dooble on OS/2 where if you try to open an HTML file, it always says 'Your file couldn't be accessed' even though you just clicked on it. However, if that file is on your %UNIXROOT% drive (say C:), and you remove 'C:' from the address bar with that file name on it, the file is displayed. If it is not on the %UNIXROOT% drive, removing, say 'D:' does not help and can not be displayed.

 The implication is the code is using a Linux standard to find the file (no drive letters) so it works this way only on the %UNIXROOT% drive. But the Windows version of Dooble does use drive letters and it does work, so it seems there must be a code path available to use drive letters when displaying files if needed.

 Are you familiar with this? Has it been looked at in the past? The reason it is important to me is I would like to use Dooble to display e-mail messages from PMMail, but it doesn't work because PMMail is not on %UNIXROOT% so even removing the drive letter doesn't help in that case. Seems like there should be a straight forward solution to this, if the proper code was identified...

Regards,

I vaguely remember that Dmitry already had a fix in place that went into a test version of one of the Qt5 DLLs. I just cannot remember which one that was ...

Thanks for the tip.

There is: https://github.com/bitwiseworks/qtwebengine-chromium-os2/issues/50
&
https://github.com/bitwiseworks/qtwebengine-chromium-os2/commit/6d53f8735fc37460d217f6d641eae585960c1e53

This may have been applied by Dmitry after I created my diffs... I certainly don't have it in my branch...

53

Internet / Re: Dooble releases-Qt6

« on: August 23, 2024, 10:56:31 am »

<sigh> build stops regenerating .gn files and trying to work out what's going on, git diff is giving a SIGSEGV. Why is everything so hard?

54

Internet / Re: Dooble releases-Qt6

« on: August 23, 2024, 09:39:38 am »

I'll have a poke around the chromium/qtwebengine code...

I reckon this might be it: https://github.com/qt/qtwebengine-chromium/blob/b45f07bfbe74c333f1017810c2409e1aa6077a1b/chromium/url/url_canon_unittest.cc#L2091

Oops that's the unittest - but I reckon the solution is in the source folder....

55

Internet / Re: Dooble releases-Qt6

« on: August 22, 2024, 11:23:03 pm »

I searched the dooble code for Q_OS_WINDOWS and I don't see anything obvious. I suspect it may be using a Qt API that is using the unix code path not a windows path on OS/2.

56

Programming / Re: GCC - updates

« on: August 19, 2024, 10:06:50 am »

binutils 2.43.1 - lightly tested - https://smedley.id.au/tmp/binutils-2.43.1-os2-20240819.zip

57

Networking / Re: Updated Samba Client

« on: August 17, 2024, 11:25:21 pm »

Can try try and capture server logs?

remove \mptn\etc\samba\logs\*
start smbd with 'smdb -d 10'
generate hang
zip \mptn\etc\samba\logs\* and email to me

58

Networking / Re: Updated Samba Client

« on: August 16, 2024, 10:50:42 pm »

Hey David,
Thanks for testing.I had only tested the server with a linux client.  I just attached and OS/2 client (running on the same machine as the server) and got a hang <sigh>

Is your OS/2 client running on the same box or a separate client?

I guess the 'good' news here  is that the hang isn't due to GCC 14...

Edit:  I had some additional changes that seem to be the cause of the hang here... I've reverted those changes, and I can no longer reproduce the hang ...

Does it make any difference if you start smbd.exe and nmbd.exe directory - not via sscc?

59

Networking / Re: Updated Samba Client

« on: August 16, 2024, 02:36:14 am »

Will update Post 1 shortly...

samba 4.19.8 (Build with GCC 9.x, which seems to resolve some hangs at exit) - https://smedley.id.au/tmp/samba-4.19.8-os2-20240816.zip
Client DLL  - https://smedley.id.au/tmp/smbcl419-4.19.8-20240816.zip

issues with 'net rpc user' persist.

60

Networking / Re: Updated Samba Client

« on: August 13, 2024, 11:25:45 am »

Hi KO!

I omitted the directory as part of the socket  name as I couldn't remember the rules around  socket names - but figured something like \\socket\\c:\mptn\etc\samba\np\xxxx may not be allowed..

Yes you are right - that was a typo. That now lets me trigger a hang as soon as I attempt 'net rpc user -S 192.168.1.135' from a linux box (where 192.168.1.135 is the IP of the ArcaOS box).

The error is still:

Code: [Select]

[2024/08/13 18:47:25.882000, 10, pid=4720, effective(109, 514), real(0, 0)] ../../source3/rpc_client/local_np.c:175(np_sock_connect_connected)
  np_sock_connect_connected: async_connect_recv returned Can't assign requested address
[2024/08/13 18:47:25.882000, 10, pid=4720, effective(109, 514), real(0, 0)] ../../source3/rpc_client/local_np.c:699(local_np_connect_connected)
  local_np_connect_connected: np_sock_connect failed: Can't assign requested address

Interestingly, log.samba-dceprcd ends with:

Code: [Select]

[2024/08/13 18:47:26.181000, 10, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:2435(rpc_host_send)
  rpc_host_send: server_setup for U:/dev/samba-os2-4.19.x/bin/rpcd_classic.exe index 0
[2024/08/13 18:47:26.368000, 10, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:2435(rpc_host_send)
  rpc_host_send: server_setup for U:/dev/samba-os2-4.19.x/bin/rpcd_epmapper.exe index 1
[2024/08/13 18:47:26.548000, 10, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:2435(rpc_host_send)
  rpc_host_send: server_setup for U:/dev/samba-os2-4.19.x/bin/rpcd_fsrvp.exe index 2
[2024/08/13 18:47:26.736000, 10, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:2435(rpc_host_send)
  rpc_host_send: server_setup for U:/dev/samba-os2-4.19.x/bin/rpcd_lsad.exe index 3
[2024/08/13 18:47:27.370000, 10, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:2435(rpc_host_send)
  rpc_host_send: server_setup for U:/dev/samba-os2-4.19.x/bin/rpcd_mdssvc.exe index 4
[2024/08/13 18:47:27.730000, 10, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:2435(rpc_host_send)
  rpc_host_send: server_setup for U:/dev/samba-os2-4.19.x/bin/rpcd_spoolss.exe index 5
[2024/08/13 18:47:27.902000, 10, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:2435(rpc_host_send)
  rpc_host_send: server_setup for U:/dev/samba-os2-4.19.x/bin/rpcd_winreg.exe index 6
[2024/08/13 18:47:28.058000, 10, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:1784(rpc_host_sigchld)
  rpc_host_sigchld: pid=4726, wstatus=0
[2024/08/13 18:47:28.058000,  1, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:1752(rpc_worker_exited)
  rpc_worker_exited: No worker with PID 4726
[2024/08/13 18:47:28.058000, 10, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:1784(rpc_host_sigchld)
  rpc_host_sigchld: pid=4724, wstatus=0
[2024/08/13 18:47:28.058000,  1, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:1752(rpc_worker_exited)
  rpc_worker_exited: No worker with PID 4724
[2024/08/13 18:47:28.058000, 10, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:1784(rpc_host_sigchld)
  rpc_host_sigchld: pid=4723, wstatus=0
[2024/08/13 18:47:28.058000,  1, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:1752(rpc_worker_exited)
  rpc_worker_exited: No worker with PID 4723
[2024/08/13 18:47:28.355000, 10, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:1784(rpc_host_sigchld)
  rpc_host_sigchld: pid=4730, wstatus=0
[2024/08/13 18:47:28.355000,  1, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:1752(rpc_worker_exited)
  rpc_worker_exited: No worker with PID 4730
[2024/08/13 18:47:28.654000, 10, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:1784(rpc_host_sigchld)
  rpc_host_sigchld: pid=4728, wstatus=0
[2024/08/13 18:47:28.654000,  1, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:1752(rpc_worker_exited)
  rpc_worker_exited: No worker with PID 4728
[2024/08/13 18:47:28.663000, 10, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:1784(rpc_host_sigchld)
  rpc_host_sigchld: pid=4733, wstatus=0
[2024/08/13 18:47:28.663000,  1, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:1752(rpc_worker_exited)
  rpc_worker_exited: No worker with PID 4733
[2024/08/13 18:47:28.683000, 10, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:1784(rpc_host_sigchld)
  rpc_host_sigchld: pid=4735, wstatus=0
[2024/08/13 18:47:28.683000,  1, pid=4722, effective(0, 0), real(0, 0)] ../../source3/rpc_server/rpc_host.c:1752(rpc_worker_exited)
  rpc_worker_exited: No worker with PID 4735

That could be due to pipe() in lieu of socketpair()... will go hunting...

Edit:  attached patch eliminates the errors in log.samba-dcerpcd but still get the log.smbd errors.