PJBrs

Results 35 comments of PJBrs

... and here's the log where the error occurs about eight minutes after approving the connection in the authenticator app for the second time: ``` user@host:~$ WLOG_LEVEL=DEBUG xfreerdp ~/profile.rdp [14:16:12:201]...

I read that, so I tried that as well, but it failed pretty soon: ``` user@host:~$ WLOG_LEVEL=TRACE xfreerdp ~/profile.rdp /gt:rpc [14:46:58:129] [23641:23641] [DEBUG][com.freerdp.utils] - Registering signal hook... [14:46:58:132] [23641:23641] [DEBUG][com.freerdp.client.common.cmdline]...

@akallabeth They're probably confidential. But I'll send an email to my employer's service desk and see what happens. What I _can_ do, is test patches and compiler settings, etc. I'm...

One more comment - my connection finally went through for once! Too busy to catch a log, but the next time I will. I did notice one thing though, my...

@akallabeth I'm afraid that my employer do not have the time to help unearth server-side logs... Please let me know if there's anything else I can do. I did fiddle...

My employer switched to a different authentication mechanism, I needed to update to 3.0.0-beta2 to make that work. (I also tried 3.0.0-beta4, but that one wouldn't connect :-( ). In...

Here examples of unpatched and patched monsters. Unpatched: [gm-session-notes-unpatched.pdf](https://github.com/canismarko/dungeon-sheets/files/14727445/gm-session-notes-unpatched.pdf) Patched: [gm-session-notes-patched.pdf](https://github.com/canismarko/dungeon-sheets/files/14727446/gm-session-notes-patched.pdf)

The latex output for monsters had a small bug (invisible though), and it included loads of spurious newlines. My latest force-push fixes that.

... and before and after examples of some tables, one with and one without table header: ![image](https://github.com/canismarko/dungeon-sheets/assets/5177219/1754b84d-9ac7-484b-8dd0-289e8a31bbd1) ![image](https://github.com/canismarko/dungeon-sheets/assets/5177219/dd28152f-7bb5-47f9-ac34-c7e6881691d5)

I've reflected some more on these patches. It seems to me that there's one single risk in switching to dndtable, that is, under the hoodit uses the tabularx environment instead...