[Event Request] Codeunit 1001 "Job Post-Line" OnBeforeJobPlanningLineInsert

Hello,
Could You please add the following event in Codeunit 1001 "Job Post-Line" into the procedure PostPlanningLine?
procedure PostPlanningLine(var JobPlanningLine: Record "Job Planning Line")
    var
        Job: Record Job;
    begin
        if JobPlanningLine."Line Type" = JobPlanningLine."Line Type"::"Both Budget and Billable" then begin
            Job.Get(JobPlanningLine."Job No.");
            if not Job."Allow Schedule/Contract Lines" or
               (JobPlanningLine.Type = JobPlanningLine.Type::"G/L Account")
            then begin
                JobPlanningLine.Validate("Line Type", JobPlanningLine."Line Type"::Budget);
                JobPlanningLine.Insert(true);
                InsertJobUsageLink(JobPlanningLine);
                JobPlanningLine.Validate("Qty. to Transfer to Journal", 0);
                JobPlanningLine.Modify(true);
                JobPlanningLine."Job Contract Entry No." := 0;
                JobPlanningLine."Line No." := JobPlanningLine."Line No." + 10000;
                JobPlanningLine.Validate("Line Type", JobPlanningLine."Line Type"::Billable);
            end;
        end;
        if (JobPlanningLine.Type = JobPlanningLine.Type::"G/L Account") and
           (JobPlanningLine."Line Type" = JobPlanningLine."Line Type"::Billable)
        then
            ChangeGLNo(JobPlanningLine);
        //NEW CODE
        OnBeforeJobPlanningLineInsert(JobPlanningLine);
        //END NEW CODE
        JobPlanningLine.Insert(true);
        JobPlanningLine.Validate("Qty. to Transfer to Journal", 0);
        JobPlanningLine.Modify(true);
        if JobPlanningLine."Line Type" in
           [JobPlanningLine."Line Type"::Budget, JobPlanningLine."Line Type"::"Both Budget and Billable"]
        then
            InsertJobUsageLink(JobPlanningLine);
    end;

    [IntegrationEvent(false, false)]
    local procedure OnBeforeJobPlanningLineInsert(var JobPlanningLine: Record "Job Planning Line")
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 10893.


Properly handle empty pipeline in Pipeline Editor clear button

Fixes #1789. Changes from erasing entire file content to erasing all nodes when clear button is pressed in pipeline editor.
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

@marthacryan do we need to clear "Pipeline Properties"?

@lresende Good catch - just pushed to clear the pipeline properties as well.


Unable to login

After successfully opening a project, on an attempt to view the component, Figma asks for a login. On trying to login nothing happens further. This is after having checked for problems / output.

Same issue here. Connected and am able to see the project files but when I want to preview them, a login page shows that does nothing

Same issue. The configuration is good. But on preview i'm facing figma login page.

Same issue. I have clicked login button, but nothing happen.

I'm currently working on new version. You can follow it here https://github.com/Idered/iridium


OAuth CI tests are failing

PR: https://github.com/NationalSecurityAgency/skills-service/pull/1635


Added Hostinger PHP info

Thank you! Come back and let us know when things have changed would you? Or add some PHP URLs so we can scan em.


show_in_notebook not working

Hi, Marco Tulio Ribeiro:
I have installed your reps on my macbook pro, and run the tutorials. Everything is ok but the show_in_notebook shows nothing, what I can see is just output:
<IPython.core.display.HTML object>
I don't know why this happend.

Hello,
I'm sorry it doesn't work! Would you please tell me:

what python version are you using?
what notebook version are you using?
Can you please try exp.save_to_file('/tmp/temp.html'), and then open the /tmp/temp.html file to see if it renders correctly?
Thanks,

Thanks for your reply!
What I used：
notebook:
jupyter 4.1.0
python:
Python 2.7.10
exp.save_to_file('/tmp/temp.html') and open /tmp/temp.html file by browser, it works fine, I can see the figure in the browser.

I wasn't able to replicate the problem. Would you please share your notebook?
Also, this may be a longshot, but do you happen to have doctest on?
Thanks,

I'm sorry for my mistake! I run the jupyter in the console mode, and get the strange result. Now, I run the example in the jupyter notebook, and it works fine! Thank you.

Great : )

For people coming here in the future: I was having trouble with it on Windows, and @marcotcr fixed the issue in the last few days, so if you're getting an error with show_in_notebook, and you're on a Windows machine, update to the latest version (currently <IP_ADDRESS>) and see if that solves the problem for you like it did for me!


Upgrades JSDoc examples to ES6

Upgrades JSDoc example based on latest ES6 rules

Thanks for the pull request @sanjeetsuhag!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

Thanks @sanjeetsuhag!


scrub URL errors with heroku/x/scrub

Prevents credential leaks to rollbar by removing them from URL's.

Ugh. Well, whatever. Let's do it. Though, maybe we should fork ln-roll directly into our stuff at this point.


Clean up setup-grafana cleanup slightly

see https://github.com/dotnet/dnceng/issues/1148
do cleanup before initial download in setup.sh
just apt-get check instead of apt-get install --fix-broken

fixing broken packages is not commonly necessary

also display /tmp and /var disk usage
nit: don't use findstr in a PowerShell script

use pscore b/c that supports the || operator
a small part of https://github.com/dotnet/dnceng/issues/967

I ran a slightly older version of this branch (prior to rebasing on today's main) to deploy Grafana to staging in #20231006.4 and production in #20231006.5. Both builds and their deployments were successful.
Both builds also hide the df and du command output (added in #961 and here) because that comes before the 4K chunk that az vm run-command invoke deigns to output ☹


Upgrade Android Gradle plugin to 4.2.0

Android Gradle plugin is currently at 3.6.4.
Upgrade it to at least 4.2.0.

Resolved by #22


scripts: kconfig: Extend the assignment-failed warning

Tailor the warning when the symbol has no prompt, explaining how
promptless symbols get values. Add some anti-select propaganda too.

Reference the 'Setting configuration values' in the Board Porting
Guide. It explains Kconfig.defconfig files.

Fixes: #8388

CC @carlescufi

Codecov Report

Merging #8417 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #8417   +/-   ##
=======================================
  Coverage   64.61%   64.61%
=======================================
  Files         421      421
  Lines       40296    40296
  Branches     6803     6803
=======================================
  Hits        26037    26037
  Misses      11126    11126
  Partials     3133     3133

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9846570...1f02722. Read the comment docs.

@SebastianBoe
Updated it to say "assignments in configuration files".
I increased the textwrap width to 100 too. Just noticed that the symbol reference link was being broken across two lines.


Package doesn't work for me on Mac os Yosemite Atom 0.174

help me to make it work please.

How is it not working?
Does it work in safe mode (atom --safe)?
Do you have the git-diff package enabled?

just tried to run it with safe mode but no result.
git-diff is enabled, I even disabled and enabled it again, and it still doesn't work

How are you launching Atom? Do you have the base of a Git repository open as the root of the project?

have the same problem.. i have to constantly untick and retick the "show icons in gutter" checkbox for the package to work.

My assumption is that it's working, but that the show icons in gutter option doesnt work anymore

Closing in favor of #46. If this is not the case, please comment.

fixed on latest version


[Bug]: After selection "portfolio-website" option, there "index.js" file is not exist

Describe the bug
When I select the Portfolio-Websites, and afterward run npm install, It give error index.js file is not found.
How To Re-produce

Run universal-box init
Select Portfolio-Websites
Select Simple
Run npm install

ScreenShots

Solution
Create index.js file, and mentions other files like app.js, index.css or etc.

@Nik4Furi I'd like to work on this issue under Hacktoberfest.

Hey @HazemAbdo are you still working on this issue?
The portfolio directory has been restructured and this bug dosen't persist anymore

@Abhishek-Mallick Feel free to close this issue. I haven't invested any time in it yet, so it's not a problem at all.

Cool


Proper error message if there are no log files to export

One post-issue from a Galaxy Store QA feedback issue #301
We need https://github.com/umair13adil/flutter_logs/issues/39 for this

If I switch to isar (#269) I'll transition to do the logging to a table. Then it'll be easy to tell if there are any logs or not

The isar version is ready


Week 5

Score:
Graded by:

[x] Fibonacci Hack
[x] Javascript/Html Hack
[x] Wireframes (5)

Score: 2.7/3
Graded by: Linda Liu
Fibonacci Hack
Javascript/Html Hack
Wireframes (5)


Feature/adds aws iam

@DorukAkinci I fixed the issue that you are not asked for setting the Role for aws collie config.


CLIP text model output. How/Why two outputs word_features & sentence features?

I was wondering why you are expecting two outputs when calling word_features, sentence_features = self.clip_model.encode_text(clip_tokens) here
As far as I understand, you are using a vanilla clip model which outputs only one embedding for clip_model.encode_text().
Evidently this cant be the case since you are expecting two different embeddings. So where did you implement the custom functionality to get two embeddings from  encode_text()?

Hi, see here

Yes, exactly. @Xiaolong-RRL Thank you for helping answer it!


Place the assets dir in COMPRESS_OUTPUT_DIR

This may need some more discussion
Fixes issue #37

It looks like the tests are broken for Python 2.6 and Django 1.4.
@gavinwahl do we still want to support that?

I fixed the ASSETS_URL but this might not be backward compatible :/


ADBDEV-6278: pg_dump incorrectly generate cleanup for external tables (#1045)

pg_dump incorrectly generate cleanup for external tables (#1045)
Fixes issue #1025. DROP EXTERNAL TABLE in pg_dump output had incorrect syntax,
this patch fixes the typo.
Ticket: ADBDEV-6257
Changes from original commit:

Removed tests since this code only affects GPDB 6 compatibility,
there is no way to reach this line using only GPDB 7.

Co-authored-by: eshkinkot<EMAIL_ADDRESS>(cherry picked from commit eaafa97a524e34f6533b5b5ee406fce5bf430d94)

Note: Do not squash to preserve authorship

IMHO if you say in the description that EXTERNAL tables were in 6.x, but they are FOREIGN in 7.x, it would be much clearer why there are no tests here.

IMHO if you say in the description that EXTERNAL tables were in 6.x, but they are FOREIGN in 7.x, it would be much clearer why there are no tests here.

This patch is about using the pg_dump binary from 7X with a database from 6X.


Yosegi-77 Creating unit tests for jp.co.yahoo.yosegi.util.io.diffencoder.

What is the necessity of this update? What is updated?
Created unit tests.
Also fixed bugs.
How did you do the test? (Not required for updating documents)

LGTM


skhd: 0.0.12 -> 0.0.14

Motivation for this change
@LnL7
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build skhd

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: skhd
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: skhd
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-darwin (full log)
Attempted: skhd
Partial log (click to expand)
installing
install flags: install SHELL=/nix/store/r8bx3qf1bpncb14i9gzma4vr089pc3pv-bash-4.4-p19/bin/bash BUILD_PATH=\$\(out\)/bin
rm -rf /nix/store/jzvysvc3fkdbvw9al5i6ikisg2jcnndf-skhd-0.0.14/bin
mkdir -p /nix/store/jzvysvc3fkdbvw9al5i6ikisg2jcnndf-skhd-0.0.14/bin
clang src/skhd.c -std=c99 -O3 -framework Carbon -o /nix/store/jzvysvc3fkdbvw9al5i6ikisg2jcnndf-skhd-0.0.14/bin/skhd
post-installation fixup
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/jzvysvc3fkdbvw9al5i6ikisg2jcnndf-skhd-0.0.14/bin
patching script interpreter paths in /nix/store/jzvysvc3fkdbvw9al5i6ikisg2jcnndf-skhd-0.0.14
/nix/store/jzvysvc3fkdbvw9al5i6ikisg2jcnndf-skhd-0.0.14


Namespacing... and more!

I kinda went down the rabbit hole...
This was branched from the PR #50 branch.  Hopefully it all looks good to you. If not, I can find my way back out of the rabbit hole.
I didn't update README.md
This allows for namespaced properties falling back up the tree. One should be able to mix and match locations of the properties, e.g. lockup_hint and lockup.codeword. It should also support unprefixed properties such as the cookie_lifetime_in_weeks.  This also means that if someone is using codeword or hint in their YAML files, it will use those.

@guaguasi 🤤 Some really good stuff in here, thank you! I’m out of the office this week, but I’ll get this reviewed and tested as soon as I can. Thanks for splitting it out from #50.


[bug] Protection values not refreshed

Version
Checklist:

[x] I am not using Home Assistant. Or: a developer has told me to come here.
[x] I have checked the troubleshooting section and my problem is not described there.
[x] I have read the changelog and my problem is not mentioned there.

Build/Run method

[ ] Docker
[ ] PKG
[x] Snap package
[ ] Manually built (git clone - yarn install - yarn run build )

Zwavejs2Mqtt version: 5.11.0
Z-Wave JS version: 8.7.5
Describe the bug
On a Fibaro FGD-212 dimmer, I use protection commands to prevent using the physical switch the night (thank you children ;) )
When I change the value in the control panel (or from mqtt), the change is effectuve but I have the old value
To Reproduce
I've made a screen recording of the reproduction: https://www.screencast.com/t/aX5b6cZFJ
Expected behavior
When I change the protection, I want to see the new value
Additional context
I have attached log files.
Nota, in the logs, I do the counter than in the video
In the video, I try to set No Operation Possible
In the log I try to set [Unprotected]
zwavejs_2021-11-18.log
zwavejs2mqtt_2021-11-18.log

This is not actually a driver bug. There are several non-critical values that aren't refreshed after a SET and have to be assumed to be successfully set.
@robertsLando setValue updates the value in the Value DB but does not emit an event because it would spam unnecessary updates. After all the application knows which value it just set.
If the setValue call resolves to true, you need to update the value in your cache yourself. You might still get an updated value afterwards, but don't rely on it.


Tutorial behind latest version of EFC API

[Enter feedback here]
The tutorial does not seem to be up to date. In the API code section there is a reference to ToListAsync() which is not available in the latest version of EFC

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ab408035-6313-a183-9940-32de00e0e977
Version Independent ID: ab408035-6313-a183-9940-32de00e0e977
Content: Tutorial: Create a minimal web API with ASP.NET Core
Content Source: aspnetcore/tutorials/min-web-api.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

It's linking to EF 6.


retain open/closed status of the modal window across page loads

Sorry for the duplicate, I decided to setup git properly instead of just using web but I messed a few things up along the way.
If the modal window is opened, it will always be opened when loading mousehuntgame.com until it is manually closed (by either the close button or clicking the button/link to render the window). It will then remain closed in subsequent refreshes until manually opened again.

didn't realize all updates to the branch on my side would propagate here, going to resubmit again


[XamarinProfiler-MAC]: Accessibility: Keyboard: MAS2.1.1: Context menu present in Data tables of "Allocations/Call Tree/Snapshots" of Allocations Profiler and "Call Tree/Samples" of Timer Profiler are not accessible using keyboard.

Prerequisites

Install Xamarin Profiler.
Launch Visual Studio.
Create a project and build the solution.
Navigate to Run Menu Tab and Invoke it. Navigate to ""Start Profiling"" option and invoke it.
This will invokes ""Xamarin Profiler"" application.

Steps to Reproduce
Scenario 1:

Follow the pre-requisite to launch the xamarin profiler application.
Select the Available instruments to "Allocations" and invoke next button. This will invokes Common options window.
Navigate to "Start Profiling" button and invoke it. This will launch Allocations profiling page.
Navigate to "Allocations" table and invoke the context menu.

Scenario 2:

Follow the pre-requisite to launch the xamarin profiler application.
Select the Available instruments to "Time Profiler" and invoke next button. This will invokes Common options window.
Navigate to "Start Profiling" button and invoke it. This will launch Time Profiler profiling page of Call Tree.
Navigate to "Call Tree" table and invoke the context menu.

Expected Behavior
Context menu present in the table should be invoked.
Actual Behavior
Context menu present in Data tables of "Allocations/Call Tree/Snapshots" of Allocations Profiler and "Call Tree/Samples" of Timer Profiler are not accessible using keyboard.
(Please refer the screenshots).
User Impact
User will be blocked to access the context menu present in the tables.
Screenshots

Environment
macOS High Sierra OSX version: 10.13.4
Visual Studio for Mac Enterprise version: 7.5.2(build 40)
Xamarin Profiler version: 1.6.3-400

Log File

Please add the following tags to this bug:
A11yMAS
Accessibility
MAS2.1.1
Xamarin-Profiler-MAC
Wipro


Random desktop environment crash

Initially please make sure the problem hasn't been already addressed:

[ yes ] Are you using the latest driver? (5.2.14)
(https://www.displaylink.com/downloads/ubuntu)
[ yes ] Are you using the latest EVDI version? (1.6.2.r29.gb5c5791-1, latest git commit)
(https://github.com/DisplayLink/evdi/releases)
[ yes ] If you are using a DisplayLink device, have you checked 'troubleshooting'
on DisplayLink's website?
(https://support.displaylink.com/knowledgebase/topics/103927-troubleshooting-ubuntu)
[ yes ] Is this issue related to evdi/kernel?
(if it is rather connected to DisplayLinkManager please take a look at support
https://support.displaylink.com or forum https://www.displaylink.org/forum/)

Some information for baseline would help a lot:

Linux distribution and its version
Arch Linux
Linux kernel version
5.5.10-arch1-1
Xorg version (if used)
1.20.7
Desktop environment in use
XFCE 4.14

Please provide good title for the issue and description.
I refrained from updating to kernel 5.5 for a while for the well know issue (package in Arch Linux AUR still does not have the patch: https://aur.archlinux.org/packages/evdi/)
Since it was taking a while, I decided to try and update the kernel to 5.5 and used the git version of the Arch package (https://aur.archlinux.org/packages/evdi-git/).
After updating, everything seemed to work, but, more than once during the same hour of usage, the desktop crashed killing the whole session and going back to the lightdm login screen. This never happened with the old evdi package and kernel 5.4; Unplugged from the docking station with evdi and dispalylink process running, this does not happen.
If you can give us logs they will be welcome but please don't paste long listings
as they will make it hard to read the thread, instead you can use other services
for sharing raw text like pastebin or gist.
can you please suggest what logs to share? Xorg.log? dmesg?
Thank you

+1

Have same problem on Gentoo while having connected two displaylink devices.
With Linux 5.4.24-ck (ck-patches, will try stock Gentoo kernel now with 5.5.13). Xorg-server 1.20.7
In Xorg-Logs there is nothing. But i've a kernel trace (journalctl -b).
Happens especially under having loads (e.g. looking HD videos or compiling in parallel):
Mär 25 23:27:17 smallLukasGentoo kernel: ------------[ cut here ]------------
Mär 25 23:27:17 smallLukasGentoo kernel: WARN_ON(bound & ((((1UL))) << (8)))
Mär 25 23:27:17 smallLukasGentoo kernel: WARNING: CPU: 1 PID: 423226 at drivers/gpu/drm/i915/i915_vma.c:722 __i915_vma_do_pin+0x32/0x3b0
Mär 25 23:27:17 smallLukasGentoo kernel: Modules linked in: md4 cifs fscache btusb btrtl btbcm btintel uinput rfcomm nft_chain_nat nf_nat nf_log_ipv4 nf_log_common nft_reject_ipv4 nft_log nft_reject_ipv6 nft_reject nft_counter nft_ct nf_t>
Mär 25 23:27:17 smallLukasGentoo kernel: CPU: 1 PID: 423226 Comm: Xorg Tainted: G        W  O      5.4.24-ck #3
Mär 25 23:27:17 smallLukasGentoo kernel: Hardware name: TUXEDO N24_25BU/N24_25BU, BIOS 5.12 02/23/2018
Mär 25 23:27:17 smallLukasGentoo kernel: RIP: 0010:__i915_vma_do_pin+0x32/0x3b0
Mär 25 23:27:17 smallLukasGentoo kernel: Code: 55 48 89 fd 53 48 83 ec 20 4c 8b af 08 01 00 00 41 0f ba e5 08 73 20 48 c7 c6 cc e3 49 82 48 c7 c7 ad aa 4c 82 e8 1d c0 b9 ff <0f> 0b 41 bc f0 ff ff ff e9 de 00 00 00 4c 89 e8 48 89 cb 25 00 >
Mär 25 23:27:17 smallLukasGentoo kernel: RSP: 0018:ffffc90000e1ba08 EFLAGS: 00010286
Mär 25 23:27:17 smallLukasGentoo kernel: RAX:<PHONE_NUMBER>000000 RBX: ffffc90000e1bb90 RCX:<PHONE_NUMBER>000000
Mär 25 23:27:17 smallLukasGentoo kernel: RDX:<PHONE_NUMBER>000000 RSI: ffffffff82c2a583 RDI: ffffffff82c2812c
Mär 25 23:27:17 smallLukasGentoo kernel: RBP: ffff8882a9a40240 R08: 000138e7ae8b728e R09:<PHONE_NUMBER>000023
Mär 25 23:27:17 smallLukasGentoo kernel: R10:<PHONE_NUMBER>000000 R11:<PHONE_NUMBER>000023 R12: ffffc90000e1bb30
Mär 25 23:27:17 smallLukasGentoo kernel: R13:<PHONE_NUMBER>0003ff R14: ffff8882a9a40240 R15:<PHONE_NUMBER>00001c
Mär 25 23:27:17 smallLukasGentoo kernel: FS:  00007fc9a18f7940(0000) GS:ffff888464080000(0000) knlGS:0000000000000000
Mär 25 23:27:17 smallLukasGentoo kernel: CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
Mär 25 23:27:17 smallLukasGentoo kernel: CR2: 00007f4bd888c008 CR3:<PHONE_NUMBER>5b6001 CR4:<PHONE_NUMBER>3606e0
Mär 25 23:27:17 smallLukasGentoo kernel: Call Trace:
Mär 25 23:27:17 smallLukasGentoo kernel:  ? kfree+0x17d/0x19b
Mär 25 23:27:17 smallLukasGentoo kernel:  ? do_raw_spin_lock+0x2b/0x52
Mär 25 23:27:17 smallLukasGentoo kernel:  eb_lookup_vmas+0x435/0x88b
Mär 25 23:27:17 smallLukasGentoo kernel:  ? intel_gt_terminally_wedged+0x1e/0xeb
Mär 25 23:27:17 smallLukasGentoo kernel:  i915_gem_do_execbuffer+0x65c/0x10d1
Mär 25 23:27:17 smallLukasGentoo kernel:  ? pollwake+0x56/0x70
Mär 25 23:27:17 smallLukasGentoo kernel:  ? kfree+0x17d/0x19b
Mär 25 23:27:17 smallLukasGentoo kernel:  ? slab_free_freelist_hook+0x39/0xa0
Mär 25 23:27:17 smallLukasGentoo kernel:  ? kfree+0x111/0x19b
Mär 25 23:27:17 smallLukasGentoo kernel:  ? drm_atomic_state_default_release+0x1f/0x29
Mär 25 23:27:17 smallLukasGentoo kernel:  ? slab_free_freelist_hook+0x39/0xa0
Mär 25 23:27:17 smallLukasGentoo kernel:  ? kfree+0x111/0x19b
Mär 25 23:27:17 smallLukasGentoo kernel:  ? drm_atomic_helper_dirtyfb+0x1cd/0x208
Mär 25 23:27:17 smallLukasGentoo kernel:  i915_gem_execbuffer2_ioctl+0x21d/0x2b7
Mär 25 23:27:17 smallLukasGentoo kernel:  ? i915_gem_execbuffer_ioctl+0x25e/0x25e
Mär 25 23:27:17 smallLukasGentoo kernel:  drm_ioctl_kernel+0x8d/0xe1
Mär 25 23:27:17 smallLukasGentoo kernel:  drm_ioctl+0x1f9/0x2d3
Mär 25 23:27:17 smallLukasGentoo kernel:  ? i915_gem_execbuffer_ioctl+0x25e/0x25e
Mär 25 23:27:17 smallLukasGentoo kernel:  ? selinux_file_ioctl+0x154/0x1a1
Mär 25 23:27:17 smallLukasGentoo kernel:  vfs_ioctl+0x19/0x26
Mär 25 23:27:17 smallLukasGentoo kernel:  do_vfs_ioctl+0x52a/0x554
Mär 25 23:27:17 smallLukasGentoo kernel:  ksys_ioctl+0x49/0x68
Mär 25 23:27:17 smallLukasGentoo kernel:  __x64_sys_ioctl+0x11/0x14
Mär 25 23:27:17 smallLukasGentoo kernel:  do_syscall_64+0x48/0x55
Mär 25 23:27:17 smallLukasGentoo kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Mär 25 23:27:17 smallLukasGentoo kernel: RIP: 0033:0x7fc9a1fa3557
Mär 25 23:27:17 smallLukasGentoo kernel: Code: 00 00 00 75 0c 48 c7 c0 ff ff ff ff 48 83 c4 18 c3 e8 4d be 01 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 09 29 0d 00 f7 d8 64 89 01 >
Mär 25 23:27:17 smallLukasGentoo kernel: RSP: 002b:00007fff15b06948 EFLAGS: 00000202 ORIG_RAX:<PHONE_NUMBER>000010
Mär 25 23:27:17 smallLukasGentoo kernel: RAX: ffffffffffffffda RBX: 00000000ffffffff RCX: 00007fc9a1fa3557
Mär 25 23:27:17 smallLukasGentoo kernel: RDX: 00007fff15b06990 RSI:<PHONE_NUMBER>406469 RDI:<PHONE_NUMBER>00000d
Mär 25 23:27:17 smallLukasGentoo kernel: RBP: 00007fff15b06990 R08: 00000000ffffffff R09:<PHONE_NUMBER>000000
Mär 25 23:27:17 smallLukasGentoo kernel: R10: 00007fff15b06ac0 R11:<PHONE_NUMBER>000202 R12:<PHONE_NUMBER>406469
Mär 25 23:27:17 smallLukasGentoo kernel: R13:<PHONE_NUMBER>00000d R14: 00005645bdde2b28 R15:<PHONE_NUMBER>000000
Mär 25 23:27:17 smallLukasGentoo kernel: ---[ end trace<PHONE_NUMBER>e0923b ]---

As there is so much i915 and some kernel bug trackers mention heavy issues with Kernel 5.4.x and i915
@UnoSD : may you able to check if you have also kernel traces in your kernel log? As stated above, can check in terminal with journalctl -b and than search for the word trace or scroll by date/time of crash.

Mar 26 07:09:51 GrantsThinkpad kernel: ------------[ cut here ]------------
Mar 26 07:09:51 GrantsThinkpad kernel: refcount_t: underflow; use-after-free.
Mar 26 07:09:51 GrantsThinkpad kernel: WARNING: CPU: 7 PID: 263 at lib/refcount.c:87 refcount_dec_not_one+0x50/0x60
Mar 26 07:09:51 GrantsThinkpad kernel: Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg hid_generic usbhid hid joydev mousedev evdi(OE) bnep cdc_ether usbnet snd_hda_codec_hdmi x86_pkg_temp_thermal snd_sof_pci intel_powercl>
Mar 26 07:09:51 GrantsThinkpad kernel:  intel_uncore amdgpu intel_spi snd_hwdep iwlmvm intel_rapl_perf spi_nor i915 psmouse input_leds pcspkr snd_pcm mtd i2c_i801 mac80211 snd_timer r8169 gpu_sched uvcvideo ttm realtek libarc4 libphy i2c_>
Mar 26 07:09:51 GrantsThinkpad kernel: CPU: 7 PID: 263 Comm: kworker/7:2 Tainted: G           OE     5.5.11-arch1-1 #1
Mar 26 07:09:51 GrantsThinkpad kernel: Hardware name: LENOVO 20RD0011AU/20RD0011AU, BIOS R16ET21W (1.07 ) 11/29/2019
Mar 26 07:09:51 GrantsThinkpad kernel: Workqueue: events delayed_fput
Mar 26 07:09:51 GrantsThinkpad kernel: RIP: 0010:refcount_dec_not_one+0x50/0x60
Mar 26 07:09:51 GrantsThinkpad kernel: Code: 74 f3 83 f8 01 74 27 8d 50 ff 39 c2 76 e1 80 3d 6a ea 09 01 00 75 de 48 c7 c7 c8 3b f4 95 c6 05 5a ea 09 01 01 e8 72 63 c1 ff <0f> 0b eb c7 31 c0 c3 66 0f 1f 84 00 00 00 00 00 41 55 49 89 f5 41
Mar 26 07:09:51 GrantsThinkpad kernel: RSP: 0018:ffff9f3f0044fdd0 EFLAGS: 00010286
Mar 26 07:09:51 GrantsThinkpad kernel: RAX:<PHONE_NUMBER>000000 RBX:<PHONE_NUMBER>080005 RCX:<PHONE_NUMBER>000000
Mar 26 07:09:51 GrantsThinkpad kernel: RDX:<PHONE_NUMBER>000001 RSI:<PHONE_NUMBER>000096 RDI: 00000000ffffffff
Mar 26 07:09:51 GrantsThinkpad kernel: RBP: ffff9ac3a154c800 R08:<PHONE_NUMBER>0004ca R09:<PHONE_NUMBER>000001
Mar 26 07:09:51 GrantsThinkpad kernel: R10:<PHONE_NUMBER>000000 R11:<PHONE_NUMBER>000001 R12:<PHONE_NUMBER>000000
Mar 26 07:09:51 GrantsThinkpad kernel: R13: ffff9ac3b585e868 R14: ffff9ac3ce565a60 R15: ffff9ac3a7247a80
Mar 26 07:09:51 GrantsThinkpad kernel: FS:<PHONE_NUMBER>000000(0000) GS:ffff9ac3d15c0000(0000) knlGS:0000000000000000
Mar 26 07:09:51 GrantsThinkpad kernel: CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
Mar 26 07:09:51 GrantsThinkpad kernel: CR2: 000055d57a96a0e8 CR3:<PHONE_NUMBER>bd2001 CR4:<PHONE_NUMBER>3606e0
Mar 26 07:09:51 GrantsThinkpad kernel: Call Trace:
Mar 26 07:09:51 GrantsThinkpad kernel:  refcount_dec_and_mutex_lock+0x13/0x70
Mar 26 07:09:51 GrantsThinkpad kernel:  drm_gem_object_put_unlocked+0x2e/0x80 [drm]
Mar 26 07:09:51 GrantsThinkpad kernel:  drm_gem_dmabuf_release+0x16/0x20 [drm]
Mar 26 07:09:51 GrantsThinkpad kernel:  dma_buf_release+0x4e/0xd0
Mar 26 07:09:51 GrantsThinkpad kernel:  __fput+0xae/0x230
Mar 26 07:09:51 GrantsThinkpad kernel:  delayed_fput+0x1f/0x30
Mar 26 07:09:51 GrantsThinkpad kernel:  process_one_work+0x1e1/0x3d0
Mar 26 07:09:51 GrantsThinkpad kernel:  worker_thread+0x4a/0x3d0
Mar 26 07:09:51 GrantsThinkpad kernel:  kthread+0xfb/0x130
Mar 26 07:09:51 GrantsThinkpad kernel:  ? process_one_work+0x3d0/0x3d0
Mar 26 07:09:51 GrantsThinkpad kernel:  ? kthread_park+0x90/0x90
Mar 26 07:09:51 GrantsThinkpad kernel:  ret_from_fork+0x1f/0x40
Mar 26 07:09:51 GrantsThinkpad kernel: ---[ end trace 2138961c7247be62 ]---

Mar 26 11:55:18 GrantsThinkpad kernel: ------------[ cut here ]------------
Mar 26 11:55:18 GrantsThinkpad kernel: refcount_t: underflow; use-after-free.
Mar 26 11:55:18 GrantsThinkpad kernel: WARNING: CPU: 6 PID: 528 at lib/refcount.c:87 refcount_dec_not_one+0x50/0x60
Mar 26 11:55:18 GrantsThinkpad kernel: Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg joydev mousedev bnep hid_generic uvcvideo btusb videobuf2_vmalloc videobuf2_memops btrtl videobuf2_v4l2 btbcm videobuf2_common usbhid b>
Mar 26 11:55:18 GrantsThinkpad kernel:  intel_cstate nls_iso8859_1 intel_uncore snd_hda_core nls_cp437 ofpart vfat fat iwlmvm i915 intel_rapl_perf cmdlinepart snd_hwdep intel_spi_pci intel_spi snd_pcm spi_nor psmouse input_leds pcspkr mac>
Mar 26 11:55:18 GrantsThinkpad kernel: CPU: 6 PID: 528 Comm: kworker/6:3 Tainted: G           OE     5.5.11-arch1-1 #1
Mar 26 11:55:18 GrantsThinkpad kernel: Hardware name: LENOVO 20RD0011AU/20RD0011AU, BIOS R16ET21W (1.07 ) 11/29/2019
Mar 26 11:55:18 GrantsThinkpad kernel: Workqueue: events delayed_fput
Mar 26 11:55:18 GrantsThinkpad kernel: RIP: 0010:refcount_dec_not_one+0x50/0x60
Mar 26 11:55:18 GrantsThinkpad kernel: Code: 74 f3 83 f8 01 74 27 8d 50 ff 39 c2 76 e1 80 3d 6a ea 09 01 00 75 de 48 c7 c7 c8 3b b4 a7 c6 05 5a ea 09 01 01 e8 72 63 c1 ff <0f> 0b eb c7 31 c0 c3 66 0f 1f 84 00 00 00 00 00 41 55 49 89 f5 41
Mar 26 11:55:18 GrantsThinkpad kernel: RSP: 0018:ffffaa2b80a63dd0 EFLAGS: 00010286
Mar 26 11:55:18 GrantsThinkpad kernel: RAX:<PHONE_NUMBER>000000 RBX:<PHONE_NUMBER>080005 RCX:<PHONE_NUMBER>000000
Mar 26 11:55:18 GrantsThinkpad kernel: RDX:<PHONE_NUMBER>000001 RSI:<PHONE_NUMBER>000096 RDI: 00000000ffffffff
Mar 26 11:55:18 GrantsThinkpad kernel: RBP: ffff95af1fe0a400 R08:<PHONE_NUMBER>0004c6 R09:<PHONE_NUMBER>000001
Mar 26 11:55:18 GrantsThinkpad kernel: R10:<PHONE_NUMBER>000000 R11:<PHONE_NUMBER>000001 R12:<PHONE_NUMBER>000000
Mar 26 11:55:18 GrantsThinkpad kernel: R13: ffff95af4d422868 R14: ffff95af4e4a0660 R15: ffff95af272d9000
Mar 26 11:55:18 GrantsThinkpad kernel: FS:<PHONE_NUMBER>000000(0000) GS:ffff95af51580000(0000) knlGS:0000000000000000
Mar 26 11:55:18 GrantsThinkpad kernel: CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
Mar 26 11:55:18 GrantsThinkpad kernel: CR2: 00007f2be4ff6d68 CR3:<PHONE_NUMBER>60a002 CR4:<PHONE_NUMBER>3606e0
Mar 26 11:55:18 GrantsThinkpad kernel: Call Trace:
Mar 26 11:55:18 GrantsThinkpad kernel:  refcount_dec_and_mutex_lock+0x13/0x70
Mar 26 11:55:18 GrantsThinkpad kernel:  drm_gem_object_put_unlocked+0x2e/0x80 [drm]
Mar 26 11:55:18 GrantsThinkpad kernel:  drm_gem_dmabuf_release+0x16/0x20 [drm]
Mar 26 11:55:18 GrantsThinkpad kernel:  dma_buf_release+0x4e/0xd0
Mar 26 11:55:18 GrantsThinkpad kernel:  __fput+0xae/0x230
Mar 26 11:55:18 GrantsThinkpad kernel:  delayed_fput+0x1f/0x30
Mar 26 11:55:18 GrantsThinkpad kernel:  process_one_work+0x1e1/0x3d0
Mar 26 11:55:18 GrantsThinkpad kernel:  worker_thread+0x4a/0x3d0
Mar 26 11:55:18 GrantsThinkpad kernel:  kthread+0xfb/0x130
Mar 26 11:55:18 GrantsThinkpad kernel:  ? process_one_work+0x3d0/0x3d0
Mar 26 11:55:18 GrantsThinkpad kernel:  ? kthread_park+0x90/0x90
Mar 26 11:55:18 GrantsThinkpad kernel:  ret_from_fork+0x1f/0x40
Mar 26 11:55:18 GrantsThinkpad kernel: ---[ end trace 6924403fbc83f670 ]---

Would love to help if I can get an idea of the best place to start? :-)

@UnoSD : may you able to check if you have also kernel traces in your kernel log? As stated above, can check in terminal with journalctl -b and than search for the word trace or scroll by date/time of crash.

@monofox I just tried, but unfortunately it has been purged from the logs, it happened last time on the 23rd and then I decided to roll back to 5.4.

All given stack traces here have to do with DRM so likeley evdi has some incompatibilities with kernel?  Although don't get any traces with kernel 5.5.13, but had a smaller interval until next crash of display manager.
So switched back to kernel 5.2.3-ck to see if the crashes appears there as well for me.
@grant-traynor : does the issues appear for you on earlier kernel releases? You're right now using 5.5.11.

Hi @monofox,
I'm happy to give it a crack. I've been using arch for about 5 years now and have not had a need to build a kernel since using it. So I'm pretty well out of practice in general, and have never done it on arch at all. Do you have a recommendation for the best method to do that? https://wiki.archlinux.org/index.php/Kernel/Arch_Build_System ?

Hi @grant-traynor,
i know only the gentoo way, which mostly should work for all operation systems until some specific routines regarding initramfs is required. Download the kernel from https://www.kernel.org/ in the wanted version, take my current kernel configuration file, make oldconfig, make and make modules_install / make install, provide the initramfs file in /boot and regenerate the grub configuration with grub-mkconfig (the "easy" way of gentoo are two commands [emerge to download the sources and genkernel to do the rest). For Arch seems best to go the way, as described in your linked page.
I tested during the day my old kernel 5.2.3-ck which worked without any crash. There was couple of minutes ago only one issue, that displaylink docking station freezed (no ethernet anymore, no usb, images were frozen). So this actually does not have to do with evdi.

OK. I'm running 5.2.3 now. I'll let you know how it goes.
 ~  $  uname -a
Linux GrantsThinkpad 5.2.3-arch1-1-gkt-5-2-3 #1 SMP PREEMPT Sat, 28 Mar 2020 23:31:38 +0000 x86_64 GNU/Linux

So I've been running in the 5.2.3 kernel all day and it seems "rock solid". No issues. Good in fact. I'll stick on this version and report back if it fails, but I think you're onto something @monofox

@monofox @UnoSD @grant-traynor
Are you all on Intel iGPUs?

@abucodonosor , yes:
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)

@monofox Same here: Intel Corporation UHD Graphics 620 (Whiskey Lake)

@abucodonosor
Yes: Me too.
 ~  $  lspci
00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem
00:14.0 USB controller: Intel Corporation Device 02ed
00:14.2 RAM memory: Intel Corporation Device 02ef
00:14.3 Network controller: Intel Corporation Wireless-AC 9462
00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface
00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller
00:1c.0 PCI bridge: Intel Corporation Device 02b8 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Device 02bc (rev f0)
00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device 0284
00:1f.3 Audio device: Intel Corporation Device 02c8
00:1f.4 SMBus: Intel Corporation Device 02a3
00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller
03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] (rev c0)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
07:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a809

 ~  $  lsusb
Bus 002 Device 005: ID 17ef:a357 Lenovo
Bus 002 Device 004: ID 17ef:a359 Lenovo
Bus 002 Device 003: ID 17e9:6015 DisplayLink USB3.1 Hub
Bus 002 Device 002: ID 17ef:a356 Lenovo USB3.1 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 27c6:55a4 Shenzhen Goodix Technology Co.,Ltd. Goodix FingerPrint Device
Bus 001 Device 003: ID 5986:2130 Acer, Inc Integrated Camera
Bus 001 Device 008: ID 046d:0a4d Logitech, Inc. G430 Surround Sound Gaming Headset
Bus 001 Device 010: ID 17ef:609b Lenovo USB2.0 Hub
Bus 001 Device 009: ID 17ef:a354 Lenovo
Bus 001 Device 007: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 005: ID 17ef:1029 Lenovo
Bus 001 Device 002: ID 17ef:1028 Lenovo USB2.0 Hub
Bus 001 Device 006: ID 8087:0026 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

No crashes today also.

Those bugs look to me like Intel drm bugs, especially after they did the eb_* rework.
There are still bug reported all over the place about gnome-shell and gdm breaking.
Is someone willing to test a vanilla 5.6 kernel?
If so let me know since evdi need a patch for 5.6 to work.

Same here at
5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux
X-Session (xfce4 and lxqt) crashed randomly - I suppose especially in Browser activity (heavily load) and brought back to lightdm login screen.
HW is thinkpad x260 with following lspci-output:
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection I219-LM (rev 21) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) 04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
logs after crash are attached:
user.log
Mar 27 10:03:26 foo xfce4-notifyd[4507]: xfce4-notifyd: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0. Mar 27 10:03:28 foo lightdm[36441]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files Mar 27 10:03:43 foo lightdm[36632]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files Mar 27 10:03:43 foo lightdm[801]: g_dbus_connection_call_sync_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed Mar 27 10:40:22 foo org.freedesktop.thumbnails.Thumbnailer1[47642]: Registered thumbnailer ffmpegthumbnailer -i %i -o %o -s %s -f
If I could do something more, pls let me know.

@abucodonosor : sure, i'm willing to test.

@monofox I noticed @displaylink-dkurek already added a fix for 5.6 kernels in git.
This commit https://github.com/DisplayLink/evdi/commit/34d92e8a78a7a3b8df848b61469c783f352e360c. It is similar to my fix just with <= logic :-)

@abucodonosor : Kernel is configured, compiled, installed:
Linux smallLukasGentoo 5.6.0 #1 SMP Tue Mar 31 14:51:37 CEST 2020 x86_64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz GenuineIntel GNU/Linux
Corresponding devel-branch of evdi is compiled and installed. Both evdi connected monitors are attached and working.
So lets see how stable it is :)

Was a short test. Desktop environment crashed after round about 30 minutes.
Pasted log to https://gist.github.com/monofox/96e62d9373a10db636c41b41978567ec
Xorg.0.log at https://gist.github.com/monofox/953c891f59375d4c150fac88c6cfdc45

@monofox
nothing interesting in the logs. Can you maybe use journalctl or similar to get a full dmesg?

@monofox
also have a look at https://github.com/DisplayLink/evdi/issues/179 and https://github.com/DisplayLink/evdi/issues/173

@abucodonosor
#179 does not affect me (messages and behaviour does not fit)
#173 also referes to some hang or freeze, whereas messages and behaviour do not fit to my system.
Full log is here: https://gist.github.com/monofox/9199cb2a5a844c9c706c621b60f6c91b
Relevant part starts at Mär 31 16:31:58 where the kernel module was loaded and Xserver restarted. On 16:32:08 display server was terminated and restarted intentionally by me. On 16:32:36 i've attached the DisplayLink docking station. You can ignore messages regarding NetworkManager - wifi fails always due to broken Intel wifi support in 5.6.0 and finally at 16:56:49 the xsession crashed. I don't have any coredump in coredumpctl list from today.
I didn't worked last two hours (so in last two hours nothing happened). But i'll stick a while for 5.6 and check how its going.

@monofox
Still nothing interesting from edvi there. But the interesting part starts with you running out-of-date firmware for your iGPU :-). Please update linux-firmware package.
Well, #179 & 173 are all about those bugs, regarding the messages.

Putting this here for future reference ==> dkms install evdi/1.6.2 -k 5.6.0-arch1-1-gkt-5-6

Ok. I'm using this version today. Did not get time with it yesterday due to work commitments. I'll let you know how it goes.
Linux GrantsThinkpad 5.6.0-arch1-1-gkt-5-6 #2 SMP PREEMPT Tue, 31 Mar 2020 21:06:06 +0000 x86_64 GNU/Linux

@abucodonosor : Package was up-to-date. Just my initramfs not. I've updated it. And made two tests: one with GUC enable and one with GUC disabled. In both cases, crash happens: https://gist.github.com/monofox/5a15cd0672dc6eacc4e0c1a987aceeb0
(same behaviour and unfortunately, the logs do not reveal any (for me) helpful).

OK. Might be a bit premature, but I've been using this version for the whole morning with no issues, doing the sorts of things that would normally cause the crash (Videoconferencing, flowcharting and graphical stuff, Moving windows between the laptop and the two attached screens). It seems a little slower though?
For reference:

Using awesomewm with predominantly chromium, Zoom, slack (thick client) and termite / terminals
Installed evdi as a dkms module using AUR evdi-git
Built the 5.6 kernel using the methods defined in https://wiki.archlinux.org/index.php/Kernel/Arch_Build_System yesterday afternoon.

Linux GrantsThinkpad 5.6.0-arch1-1-gkt-5-6 #2 SMP PREEMPT Tue, 31 Mar 2020 21:06:06 +0000 x86_64 GNU/Linux

dkms install evdi/1.6.2 -k 5.6.0-arch1-1-gkt-5-6

A couple of crashes now. I'm going to head back to 5.2.3 to see if it remains solid. Snips from journalctl -b below. I've kept the log and can dig more out of it if it helps. These don't look the same as previous logs, maybe not evdi any more?
dump1.txt
dump2.txt

Back on 5.2.3 and no problems. Snappier also. I haven't really been exposed to this driver infrastructure, would be interested to hear from  someone who know's what's going on in kernel land as to what's going on. A theory?

Yes buggy Intel driver. And yes 5.2.x seems to be a working kernel for Intel iGPUs.
See as example:
https://marc.info/?l=linux-kernel&m=158551437904739&w=2
https://gitlab.freedesktop.org/drm/intel/-/issues/1585
Ofc lots more there, https://gitlab.freedesktop.org/drm/intel/issues/
Your crashes are from iwlwifi which is fixed in 5.6.2 and Xorg crashing in modeseting driver.
In any way, I do not own such HW, and I do not think is related to evdi. Either you guys
report these to Intel people or someone is trying to bisect 5.2 -> 5.3++ kernel and find the broken commits.

Nope it still crashes to login screen for me.

https://gitlab.freedesktop.org/drm/intel/-/issues/1667
I raised this to give the intel/drm guys a heads up. They're probably already across it.
Trying to help, tell me to go away if not.

I confirm it's not better with 5.6.2. Testing with 5.2.3-arch1 to confirm if it's better

Tested earlier also with 5.6.3.; after 20 minutes, its crashing. Based on the intel gitlab issue tracker, i've figured out some debug parameters drm.debug=0x1e log_buf_len=4M, producing huge log, but actually did not really helped me. I will later provide it to the ticket created by @grant-traynor . I'm working in parallel two ways right now: (1) part about drm to figure out, to get any kind of kernel messages, error messages through proc, etc. and (2) figure out on XServer side, why its terminating, but not directly "crashing" (there is no coredump, or similar and based on logs, no graceful termination).

Yeah, just to put the icing on this, 5.2.3 doesn't appear to crash at all. It's more performant, and rock solid stable.

I've been running this version all day today.
5.6.4-arch1-1 #1 SMP PREEMPT Mon, 13 Apr 2020 12:21:19 +0000 x86_64 GNU/Linux

Things have definitely improved, not sure if I'm jumping the gun. But it seems to be back to it's good old 5.2.3 self again, maybe even a little tiny bit better. No crashes so far, not holding back in terms of workload. Hope that this is the light at the end of the tunnel.

I wanted to wait a little bit more before posting a comment but I agree that it's really better. Almost 2 days without any crash as well on my side with 5.6.4

So I've gone back to 5.3.2 for now. 5.6.4 is definitely better, but still not really done. I've also noticed that DisplayLinkManager hangs on reboot, possibly as a result of a previous error the reason for which I rebooted.
@deimosfr are you still on 5.6.4?
I get the impression that there's a lot of work going on, and that things might naturally settle down as that work matures?

@grant-traynor since 5 days, I got only 1 crash. So I agree the work is not completed. To confirm my setup:

I recently updated to 5.6.5-arch3-1 (and saw 5.6.6 is out as well)
Installed evdi from devel branch
Hope this can help

@grant-traynor since 5 days, I got only 1 crash. So I agree the work is not completed. To confirm my setup:
* I recently updated to 5.6.5-arch3-1 (and saw 5.6.6 is out as well)

* Installed evdi from devel branch
  Hope this can help

I've tried this - it wont help you

can confirm this for pre 5.6.4 kernel and maybe even add that it freezed with 5.6.4 and some before.

I am running 5.5.0-2-amd64 on debian testing (bullseye).  Any recommondations from you to run the fix on such distribution?

Just tried 5.2.7 and it crashed within about 15 minutes. Didn't grab the log, work is killing me at the moment. Arrggh. What on earth is going on in the intel driver space?

Just tried 5.6.7 and it crashed within about 15 minutes. Didn't grab the log, work is killing me at the moment. Arrggh. What on earth is going on in the intel driver space?

As far as i know logs for displaylink hardware are binary :) - happy reading ;)

@grant-switchdin i have no idea either. DisplayLink doesnt work at all for me now.

@0k00l .. honestly dude ... you think you're the only person who knows what's going on here? How does this help?

@0k00l .. honestly dude ... you think you're the only person who knows what's going on here? How does this help?

Saving your time (i just informed you that logs are binary )

Some improvements with newest evdi(devel branch) with displaylink 5.3.1.
It take much more time to crash and crash itself doesn't logout it shutdown screen (screen make itself black).  I have just seen the new 1.7 release, but I'm holding the update to make sure there is some feedback first.

I installed (you need sudo...) latest official ubuntu driver on debian testing/bullseye right now running kernel 5.6.0-1-amd64 from https://www.displaylink.com/downloads/ubuntu and I had no restarts so far...
xrand command, to start displaylink external display looks like this:
xrandr --setprovideroutputsource 4 0
and /usr/share/X11/xorg.conf.d/20-displaylink.conf looks like this:
Section "Device"
    Identifier  "DisplayLink"
    Driver      "modesetting"
    Option      "PageFlip" "false"
EndSection

hope this helps

Yeah, I've done something similar and making some progress. Installed the latest DisplayLink driver using a patch of the module in the Arch User Repository:
Linux GrantsThinkpad 5.6.11-arch1-1 #1 SMP PREEMPT Wed, 06 May 2020 17:32:37 +0000 x86_64 GNU/Linux displaylink <IP_ADDRESS>-1 evdi-git 1.7.0.r71.gdc595db-1
Still playing with it, but it appears to be getting there.

It works but still crashes every 1-48 hours.
evdi 1.7.0-1
displaylink <IP_ADDRESS>-1
5.6.13-arch1-1

I've been using spectrwm for a few week, and yesterday thought I'd give gnome a go again. Ran all day without a crash, which I find troubling. Seems that the lightweight window managers make this worse?
xorg-server 1.20.8-2
evdi-git 1.7.0.r71.gdc595db-1
gnome-shell 1:3.36.2+7+ge4199c71c-1
displaylink <IP_ADDRESS>-1
linux 5.6.13.arch1-1

I have similar issue in the following environment.

fedora-32-displaylink-1.7.0-1.x86_64.rpm
Linux 5.6.14-300.fc32.x86_64
xorg-x11-server-Xorg-1.20.8-1.fc32.x86_64
mesa-dri-drivers-20.0.7-1.fc32.x86_64
2 monitors (laptop's monitor and external monitor connected via displaylink)

In the issue, Xorg crashes by SIGABRT at _iris_batch_flush(). I am not sure if it is evdi issue. However, the issue cannot be reproduced without displaylink. I have reported the issue as BZ#1839949.

Any update or workaround, please? This is holding kernel updates back (3 months now). Is this library supported by DELL? would it help to contact DELL directly?

I've been using the following, which I think are the latest versions available as of last Friday:

5.6.15-arch1-1
evdi-git 1.7.0.r71.gdc595db-1
displaylink <IP_ADDRESS>-2
xorg-server 1.20.8-2
gnome-shell 1:3.36.3-1

processor	: 7
vendor_id	: GenuineIntel
cpu family	: 6
model		: 142
model name	: Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz

00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02)
03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] (rev c0)

And it's been pretty stable with two external displays via a Lenovo dock using Displaylink, and the laptop display under GNOME. I think it's about as good as 5.2.3 was, almost.
I've noticed that more lightweight window managers appeared to be less stable. I'll run today using spectrwm to see if that's still the case and report back.

I've been using spectrwm for a few days now with no issues. Looks as though this might have come to come conclusion. Performance seems to be back on par with 5.2.3. Upgraded to the linux 5.7 series and things are looking pretty solid:
linux 5.7.2.arch1-1
evdi-git 1.7.0.r71.gdc595db-1
displaylink <IP_ADDRESS>-2
xorg-server 1.20.8-2
spectrwm 3.3.0-1

@grant-traynor thank you for confirming. Has anyone else on the thread updated and got a stable environment?

Currently 3 day uptime.
displaylink <IP_ADDRESS>-2
evdi-git 1.7.0.r6.g9b124a6-1
linux 5.7.2.arch1-1
linux-headers 5.7.2.arch1-1
xorg-server 1.20.8-2
i3-gaps 4.18.1-2

Just upgraded from Ubuntu 18.04 to 20.04.  Upon rebooting with 20.04 running, I only had one monitor working, whereas before that upgrade, I had two.  Upgraded the driver from https://www.displaylink.com/downloads/ubuntu
So far so good.  How can I get the more detailed version numbers like in https://github.com/DisplayLink/evdi/issues/197#issuecomment-645727982 ?  Is there a one-shot command that does that?

Just upgraded from Ubuntu 18.04 to 20.04. Upon rebooting with 20.04 running, I only had one monitor working, whereas before that upgrade, I had two. Upgraded the driver from https://www.displaylink.com/downloads/ubuntu
Rebooted.  Now 2 monitors working again.  So far so good. How can I get the more detailed version numbers like in #197 (comment) ? Is there a one-shot command that does that?

Same for me, 3 days uptime, no issue with:
displaylink <IP_ADDRESS>-2
linux 5.7.2.arch1-1
evdi 1.7.0-1
xorg-server 1.20.8-2
i3-wm 4.18.1-1

thank you all for the confirmation. I will attempt to update in the next few days and provide feedback for xfce

Update: I just updated, had one system freeze and now video playback is insanely slow. I will have to downgrade once again.
Will try evdi-git first, but I have no hope this will be fixed. I'm getting really close to toss the docking station out of the window.
displaylink <IP_ADDRESS>-2
linux 5.7.6.arch1-1
evdi 1.7.0-1
xorg-server 1.20.8-2
xfce 4.14

Same issue with evdi-git.

ffs! now I downgraded and videos are still slow!

I wonder if it's helped by some of the other tweaking I've been playing with over time. Note that I'm also using X11 not Wayland.
 ~  $  cat /etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
  # -- Common Options
  Identifier 	"Intel Graphics"
  Option 	"DRI"			"3"
  # -- Modesetting Driver Options
  #Driver      	"modesetting"
  #Option 	"AccelMethod"		"glamor"
  # -- Intel Driver Options
  Driver 	"intel"
  Option 	"AccelMethod"		"sna"
  Option	"TearFree"		"true"
  Option 	"AccelMethod"		"uxa"
  #Option	"NoAccel"		"True"
  #Option	"DRI"			"False"
  #Option 	"AccelMethod"		"sna"
  #Option 	"AccelMethod"		"blt"
EndSection

Section "Device"
    Identifier  "DisplayLink"
    Driver      "modesetting"
    Option      "PageFlip" "false"
EndSection

I also tried stuff on this thread at some point and thought it helped:
https://displaylink.org/forum/showthread.php?t=65650
I'm upgrading arch at the moment, I'll let you know if I see a problem on the latest versions.

thank you @grant-traynor , I will give your settings a go.
I am also using X11, I actually wanted to try Wayland as I saw some posts around issues with X11, but I'm on XFCE and LightDM, and I understand that it's not well supported/not doable at all.
I was on kernel 5.4.15.arch1-1 with evdi 1.6.40-2 and displaylink 5.2.14-1 and it all worked fine, beside crashes when plugging/unplugging, but I was used to that.
I updated to 5.7.6.arch1-1 with evdi 1.7.0 also latest displaylink and video playback on GPU was extremely slow (1FPS) and it started disconnecting and reconnecting every 15 minutes.
I decided then to re-downgrade evdi, displaylink and use the LTS kernel 5.4.49-1-lts and now video is still unusable and it still disconnects/reconnects often, making it completely unusable! I'm desperate, I'm about to throw the docking station out of the window and but a USB-C -> HDMI for one of the monitors.
I am trying now to rebuild the old kernel to see if that helps, but I'm getting all sort of incompatibility issues with the new gcc... I basically wasted a weekend on this.
any help would be really appreciated as I'm desperate and this is becoming more and more frustrating. If I didn't have all the cables stapled and only one HDMI, I would have already thrown away the docking station.

Hi @UnoSD
So I'm running this at the moment, and it's been stable and performant since yesterday when I said I'd do the upgrade.
linux 5.7.6.arch1-1
evdi-git 1.7.0.r71.gdc595db-1
displaylink <IP_ADDRESS>-2
xorg-server 1.20.8-2
spectrwm 3.4.1-1

I think I patched my own display link driver, but that was just a versioning / download URL change from what I remember.
The machine is a Lenovo E15 with an external USB-C hub.
USB:
Bus 002 Device 004: ID 17ef:a359 Lenovo
Bus 002 Device 003: ID 17e9:6015 DisplayLink USB3.1 Hub

PCI:
03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] (rev c0)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model

I've got this file:
 ~  $  cat /usr/share/X11/xorg.conf.d/20-displaylink.conf
Section "Device"
  Identifier "DisplayLink"
  Driver "modesetting"
  Option "PageFlip" "false"
EndSection

And I'm setting my monitors up with a shell script depending upon if I'm home or in the office. Mostly at home at the moment.
 ~  $  cat ~/.config/screen_layout_home.sh
#!/bin/sh

# Mouse Speed
xset mouse 3 6

# Setup DIsplayLink Monitors
xrandr --setprovideroutputsource 1 0
xrandr --setprovideroutputsource 2 0

# Home Monitors
xrandr --output eDP-1 --primary --mode 1920x1080 --pos 1920x1080 --rotate normal \
       --output DP-1 --off \
       --output HDMI-1 --off \
       --output HDMI-2 --off \
       --output DVI-I-3-2 --mode 1920x1080 --pos 0x0 --rotate normal \
       --output DVI-I-2-1 --mode 1920x1080 --pos 1920x0 --rotate normal

Most of this I've pieced together using the information from this wiki article: https://wiki.archlinux.org/index.php/DisplayLink
The only other file I have I think is this one:
 ~  $  cat /etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
  # -- Common Options
  Identifier 	"Intel Graphics"
  Option 	"DRI"			"3"
  # -- Modesetting Driver Options
  #Driver      	"modesetting"
  #Option 	"AccelMethod"		"glamor"
  # -- Intel Driver Options
  Driver 	"intel"
  Option 	"AccelMethod"		"sna"
  Option	"TearFree"		"true"
  Option 	"AccelMethod"		"uxa"
  #Option	"NoAccel"		"True"
  #Option	"DRI"			"False"
  #Option 	"AccelMethod"		"sna"
  #Option 	"AccelMethod"		"blt"
EndSection

Section "Device"
    Identifier  "DisplayLink"
    Driver      "modesetting"
    Option      "PageFlip" "false"
EndSection

Note that I had problems with spectrwm for a while, and using GNOME seemed stable. Maybe there's still something going on that XFCE has a problem with. Have you tried an alternative WM / DE for a while to see if that helps?

@grant-traynor Thank you very much, I really appreciate you sharing your configuration.
I managed to downgrade back to a working kernel/evdi combination.
I had to get the old kernel from the archives, downgrade gcc, compile evdi, re-upgrade gcc and finally I got it to the same state as before (no constant disconnects/reconnects and working audio).
I will need to get this sorted at some point, when I have some time, I'll back all this up and try with your configuration and I will give some feedback. Thanks again.

@UnoSD  .... I did notice today that if I routed audio out through the HDMI connections in the dock then the video slowed down .... routing it to a USB connected headset on the same dock was fine.

@grant-traynor that may be related to the same issue I was experiencing, that was apparently fixed in the new kernel, but I haven't tried it:
https://github.com/DisplayLink/evdi/issues/211#issuecomment-654117060

Throwing my hat in the ring.  Getting similar error as https://github.com/DisplayLink/evdi/issues/197#issuecomment-604169999 and tempted to throw it out the window as well :) So far I haven't been able to find a good combo on 18.04 and the 5.7+ kernels aren't available yet.
Linux distribution and its version: Ubuntu 18.04
Linux kernel version: 5.4.0-51-generic #56~18.04.1-Ubuntu
Xorg version (if used): 1.20.8
Desktop environment in use: Qtile
Display Link: <IP_ADDRESS>

I got fed up with this issues and I decided to plug my monitors buying some adaptors directly in the laptop so I can't really comment on this issue anymore. But I'll gladly try again later if it seems resolved for the others.

To add to the frustration I thought I was safe by going back to Gnome and it just crashed on me. :(

Starting to get to the same point. This clearly looks like something that displaylink really aren't interested in continuing ... need to find another answer.

Looks like a good Samaritan in arch has raised a ticket on xorg. Apparently it's on know regression. There is hope: https://aur.archlinux.org/packages/displaylink/

I've been struggling thinking it was my Ubuntu install and heavy usage of apps. I'm testing out a non-DisplayLink setup, I'm also going to try upgrading to Ubuntu 20.10 with kernel 5.8 and see if that makes any difference.

@timnolte Same, I'm moving some of my workloads that aren't compatible with Ubuntu 20.10 in a KVM as a last ditch effort to see if 5.8 works which sounds like success on this issue thread.

+1
First, thank you @displaylink-dkurek, for the amazing work.
I was hoping #225 (kernel > 5.8) would finally solve the present issue as well as #126.
However, desktop environment still crashes when under high load (which at first I thought was 'random').
The crash only happens when high load graphic tasks are performed, such as playing videos.
This is reported in several ways here and in the DisplayLink forum.
While I can't be certain, I think there is a good chance these issues are related.
(i.e.: "Random DE crash", "Disconnecting randomly D6000 dock", "High system Load", etcetera.)
Here it is mentioned to report these problems to the DisplayLink forum instead. But some of the (perhaps) related issues are still open.
I would be happy to test or report log files if needed.

+1
First, thank you @displaylink-dkurek, for the amazing work.
I was hoping #225 (kernel > 5.8) would finally solve the present issue as well as #126.
However, desktop environment still crashes when under high load (which at first I thought was 'random').
The crash only happens when high load graphic tasks are performed, such as playing videos.
This is reported in several ways here and in the DisplayLink forum.
While I can't be certain, I think there is a good chance these issues are related.
(i.e.: "Random DE crash", "Disconnecting randomly D6000 dock", "High system Load", etcetera.)
Here it is mentioned to report these problems to the DisplayLink forum instead. But some of the (perhaps) related issues are still open.
I would be happy to test or report log files if needed.

Hi, i have a laptop with nvidia video card, the dock work perfectly with other note, but with my notebook crash randomly, freezing the bluethoot and usb ports (my keyboard and mouse). I tested 1 million of things, but dosent work anything.
Some day i founded one conbination that work like a charm on my laptop.
The linux mint 19.3 fresh installation and drivers nvidia "nvidia-driver-450", this its important, with other drivers dosent work correctly, but with this drives, the dock its wonderfull.

Hi all, same/similar problem here. Randomly dropping out of the X session to login screen. Sometimes this happens immediately after login, i.e. I get the desktop for a brief moment or even only a "blink". Feels like on 2nd login it then always works... until it drops out later after n or nn minutes. Nothing regular as far as I see. Appears to happen more or less only when browsing the web ("normal" sites, not even videos). Where to start? Logs don't really give me a hint, see below, but first some data on the setup maybe.
18.04.5 LTS, originally "Xubuntu" running XFce. Read that maybe another WM/DE might do (better), so switched to openbox/LXqt. Not better. However, a number of XFce applets and from other DEs still in use. A cleaner approach would be to backup the machine and re-install a 20.04 Lubuntu from scratch...but rather would like to get it fixed instead of wiped...
The Dock is a "lenovo hybrid USB-C with USB-A dock", connected via a HDMI-DVI adaptor cable to a HP ZR24w. Running without problems on two different lenovo thinkpads with W10. So, no hardware issues.
$ uname -a && lsb_release -a
Linux S6214T 5.5.4-050504-generic #202002150446 SMP Sat Feb 15 09:50:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
LSB Version:	core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.5 LTS
[...]

running 5.5.4 as others freeze my machine randomly; not related to displaylink
$ lspci
00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0c)
00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0c)
00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0c)
00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0c)
00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0c)
00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0c)
00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0c)
00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0c)
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter

$ inxi -G
Graphics:  Card: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display
           Display Server: x11 (X.Org 1.20.8 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution<EMAIL_ADDRESS>
           OpenGL: renderer: Mesa DRI Intel HD Graphics (BYT) version: 4.2 Mesa 20.0.8

$ lsmod | grep evdi
evdi                   57344  5
drm_kms_helper        200704  2 evdi,i915
drm                   528384  16 drm_kms_helper,evdi,i915
syscopyarea            16384  2 drm_kms_helper,evdi
sysfillrect            16384  2 drm_kms_helper,evdi
sysimgblt              16384  2 drm_kms_helper,evdi

$ sudo dkms status
evdi, 1.9.1, 5.2.21-050221-generic, x86_64: installed
evdi, 1.9.1, 5.2.5-050205-generic, x86_64: installed
evdi, 1.9.1, 5.5.4-050504-generic, x86_64: installed
evdi, 1.9.1, 5.6.17-050617-generic, x86_64: installed
evdi, 5.2.14, 5.2.21-050221-generic, x86_64: built
evdi, 5.2.14, 5.2.5-050205-generic, x86_64: built

$ apt-cache policy xorg
xorg:
  Installed: 1:7.7+19ubuntu7.1
  Candidate: 1:7.7+19ubuntu7.1
  Version table:
 *** 1:7.7+19ubuntu7.1 500
        500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1:7.7+19ubuntu7 500
        500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

$ cat /etc/X11/xorg.conf.d/20-displaylink.conf
Section "OutputClass"
    Identifier  "DisplayLink"
    MatchDriver "evdi"
    Driver      "modesetting"
    Option      "AccelMethod" "none"
    Option      "PageFlip" "false"
EndSection

Added the "PageFlip" "false" but didn't help. From what I read it appears necessary in cases where the displaylink connected screens aren't usable at all. Not my case.
Now for the little information I can find from the logs. Apologies for not knowing better where to get what from, maybe throw me some hints what I should gather.
/var/log/Xorg.1.log.old or ...0.log.old are outdated, not really from the respective crashes, or not containing any "EE" messages for the crash if they are from the recent login/session. Strange!? It dies so "hard" it can't even log what happened!?
From jorunalctl:
There's always this one line for "Did the X11 server die?", but the bit in front always is different.
May 04 22:54:29 S6214T org.kde.KScreen[2051]: The X11 connection broke (error 1). Did the X11 server die?
After that crash, I logged in again a few seconds later, and was kicked out immediately again with the same:
May 04 22:54:51 S6214T org.kde.KScreen[2051]: The X11 connection broke (error 1). Did the X11 server die?
My understanding: the "did it die?" line is triggered by any "first" application to notice it, and the name of that component is then mentioned. But I don't think it is that particular application which caused the fault. Before that line, there's mostly several seconds without any entries, so nothing "related" visible right before that "and out we are again" message.
After this line, there's then always several messages from various programs running in the X session which report that they terminate (because they think the session was ended... so these messages look like after any usual "log out"). Can't see from them that any of the programs would have "triggered" the problem.
For the above crash, I found this in ~/,xsession-errors.old:
(nm-applet:8851): Gtk-WARNING **: 22:54:42.417: Can't set a parent on widget which has a parent
File::Glob::glob() will disappear in perl 5.30. Use File::Glob::bsd_glob() instead. at /usr/bin/shutter line 8212.
(0x7fff2f29bbe0) Debug: systemd: "CanReboot" = "yes"
(0x7fff2f29bbe0) Debug: systemd: "CanPowerOff" = "yes"
Translator is not loaded "qlipper_en_GB" "/usr/share/qlipper/translations"
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/^<.*>\n{ <-- HERE / at /usr/share/shutter/resources/system/upload_plugins/upload/vgyme.pm line 159.

(shutter:8780): Wnck-WARNING **: 22:54:51.767: Unhandled action type _OB_WM_ACTION_UNDECORATE

(shutter:8780): Wnck-WARNING **: 22:54:51.785: Unhandled action type _OB_WM_ACTION_UNDECORATE
The X11 connection broke (error 1). Did the X11 server die?
Gdk-Message: 22:54:51.883: light-locker: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Gdk-Message: 22:54:51.883: blueman-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Once (!) I got this:
May 04 22:15:36 S6214T kernel: traps: Core[2246] general protection fault ip:7f35a115f0a6 sp:7f358bdc8a60 error:0 in libc-2.27.so[7f35a111c000+1e7000]
but could not locate a dump (nothing for that date/time in /var/crash). Shouldn't there be one? There is dumps for individual apps every now and then, but not related to the times of X crashing. What do I need to set up to make the xServer (?) get dumped/dump properly?
Another time I had these two lines
May 04 23:30:16 S6214T xfce4-notifyd[9741]: xfce4-notifyd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
May 04 23:30:16 S6214T org.kde.KScreen[2051]: The X11 connection broke (error 1). Did the X11 server die?

But again, not much in front (several seconds silence), and only messages thereafter resulting from the "log out".

replying to my own post: took the "easy" way (well...):
0) took two backups (timeshift and a clonezilla image - just in case)

installed Lubuntu 20.04 from scratch. Runs kernel 5.8.0-53-generic out of the box
$ sudo apt-get install dkms libdrm-dev
downloaded the latest official displaylink driver package zip file (5.4 as of today) from synaptic homepage and unzipped it
$ sudo ./displaylink-driver-5.4.0-55.153.run
rebooted.
Been running for several hours now while I'm setting up /restoring from timeshift rsync archive the various bits and pieces of the new lubtuntu installation. Runs without any glitches so far.

I have been experiencing the same issue, random crashes sometimes several times per day, with a ThinkPad Hybrid USB-C running Xubuntu 20.04 and DisplayLink 5.3.1.
However I have not had a single crash after upgrading DisplayLink to 5.4.0 about two weeks ago.

@tbjornli 5.8.x Kernel?

Sorry, I forgot to include the kernel. I'm running on 5.4.0-73-generic.

Got a crash today with fairy recent kernel and displaylink driver:
I believe it happened when I checked gitlab job output which updated the screen very often.
 See the documentation of g_child_watch_source_new() for possible causes.

Bumping this issue back as I believe I might be having the same issue as poeple were having here. I was able to at least have the monitors displaying properly with a 4K display and another vertical monitor. But as stated early in the issue, heavy workloads just seem to crash either the Wayland/Xorg (tried both).
I've also used this fork which has a script to installing all the required dependencies for the DisplayLink driver to work properly.
Here is my system info:
--------------- Linux system info ----------------

Distro: Pop
Release: impish
Kernel: 5.16.11-76051611-generic

---------------- DisplayLink info ----------------

Driver version: 1.10.0
1.9.1
DisplayLink service status: up and running
EVDI service version: 1.10.0

------------------ Graphics card -----------------

Vendor: i915
Subsystem: Graphics
VGA: Intel Corporation HD Graphics 630 (rev 04)
VGA (3D): NVIDIA Corporation GM107M [GeForce GTX 950M] (rev a2)
X11 version: 1.20.13-1ubuntu1.1
X11 configs: /etc/X11/xorg.conf.d/backup.conf /etc/X11/xorg.conf.d/20-displaylink.conf

These are the output right before crashing DisplayLink (or I believe it must be DisplayLink):
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card1) Notifying display power state: on
Mar 07 21:37:05 pop-os kernel: evdi: [W] evdi_painter_connect:882 (card2) Double connect - replacing 00000000deae87c7 with 00000000deae87c7
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Connected with Task 71408 (DesktopManagerE) of process 71399 (DisplayLinkMana)
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Connector state: connected
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Notifying mode changed: 3840x2160@60; bpp 32; pixel format XR24 little-endian (0x34325258)
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Notifying display power state: on
Mar 07 21:37:05 pop-os kernel: evdi: [W] evdi_painter_connect:882 (card2) Double connect - replacing 00000000deae87c7 with 00000000deae87c7
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Connected with Task 71408 (DesktopManagerE) of process 71399 (DisplayLinkMana)
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Connector state: connected
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Notifying mode changed: 3840x2160@60; bpp 32; pixel format XR24 little-endian (0x34325258)
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Notifying display power state: on
Mar 07 21:37:05 pop-os kernel: evdi: [W] evdi_painter_connect:882 (card2) Double connect - replacing 00000000deae87c7 with 00000000deae87c7
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Connected with Task 71408 (DesktopManagerE) of process 71399 (DisplayLinkMana)
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Connector state: connected
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Notifying mode changed: 3840x2160@60; bpp 32; pixel format XR24 little-endian (0x34325258)
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Notifying display power state: on
Mar 07 21:37:05 pop-os kernel: evdi: [W] evdi_painter_connect:882 (card2) Double connect - replacing 00000000deae87c7 with 00000000deae87c7
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Connected with Task 71408 (DesktopManagerE) of process 71399 (DisplayLinkMana)
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Connector state: connected
Mar 07 21:37:05 pop-os kernel: evdi: [I] (card2) Notifying mode changed: 3840x2160@60; bpp 32; pixel format XR24 little-endian (0x34325258)
Mar 07 21:37:08 pop-os kernel: evdi: [I] (card2) Notifying display power state: on
Mar 07 21:37:08 pop-os kernel: evdi: [W] evdi_painter_connect:882 (card2) Double connect - replacing 00000000deae87c7 with 00000000deae87c7
Mar 07 21:37:08 pop-os kernel: evdi: [I] (card2) Connected with Task 71408 (DesktopManagerE) of process 71399 (DisplayLinkMana)
Mar 07 21:37:08 pop-os kernel: evdi: [I] (card2) Connector state: connected
Mar 07 21:37:08 pop-os kernel: evdi: [I] (card2) Notifying mode changed: 3840x2160@60; bpp 32; pixel format XR24 little-endian (0x34325258)
Mar 07 21:37:09 pop-os PackageKit[2426]: get-packages transaction /5784_cecbbbad from uid 1000 finished with success after 732ms
Mar 07 21:37:09 pop-os kernel: evdi: [I] (card2) Notifying display power state: on
Mar 07 21:37:09 pop-os kernel: evdi: [W] evdi_painter_connect:882 (card2) Double connect - replacing 00000000deae87c7 with 00000000deae87c7
Mar 07 21:37:09 pop-os kernel: evdi: [I] (card2) Connected with Task 71408 (DesktopManagerE) of process 71399 (DisplayLinkMana)
Mar 07 21:37:09 pop-os kernel: evdi: [I] (card2) Connector state: connected
Mar 07 21:37:09 pop-os kernel: evdi: [I] (card2) Notifying mode changed: 3840x2160@60; bpp 32; pixel format XR24 little-endian (0x34325258)

I have a portable monitor which is unusable when set to vertical with xorg. Using the latest kernel (5.15..) and displaylink beta. I'll add details later.

Still getting the same kernel BUG with recent drivers and kernel:
Kernel version: 5.17.12
DisplayLink driver: v<IP_ADDRESS>
Gnome: 42.x (gnome-shell 42.1)
Session: wayland
Kernel crash log:
jun 11 21:42:05 comp-core-i5-8250u-8f89bf rtkit-daemon[2627]: Supervising 0 threads of 0 processes of 0 users.
jun 11 21:42:05 comp-core-i5-8250u-8f89bf rtkit-daemon[2627]: Supervising 0 threads of 0 processes of 0 users.
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: BUG: kernel NULL pointer dereference, address:<PHONE_NUMBER>000148
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: #PF: supervisor write access in kernel mode
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: #PF: error_code(0x0002) - not-present page
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: PGD 0 P4D 0
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: Oops: 0002 [#1] PREEMPT SMP PTI
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: CPU: 3 PID: 4177 Comm: gnome-shell Tainted: G        W  OE     5.17.12-un-def-alt1 #1
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: Hardware name: LENOVO 20L5004SMH/20L5004SMH, BIOS N24ET67W (1.42 ) 11/17/2021
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RIP: 0010:evdi_prime_import_sg_table+0xcc/0x150 [evdi]
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: Code: 89 da 41 89 df 48 63 db e8 b1 92 d5 fe 48 8d 3c dd 00 00 00 00 48 c1 eb 3d 75 62 be c0 0c 00 00 ba ff ff ff ff e8 a4 f5 e8 e2 <48> 89 85 48 01 00 00 48 89 c6 48 85 c0 74 4f 44 89 fa 4c 89 e7 e8
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RSP: 0018:ffffc0c8c3843cd8 EFLAGS: 00010246
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RAX: ffff9ca904ea0000 RBX:<PHONE_NUMBER>000000 RCX:<PHONE_NUMBER>000000
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RDX:<PHONE_NUMBER>000000 RSI:<PHONE_NUMBER>000000 RDI:<PHONE_NUMBER>000000
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RBP:<PHONE_NUMBER>000000 R08:<PHONE_NUMBER>000000 R09:<PHONE_NUMBER>000000
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: R10:<PHONE_NUMBER>000000 R11:<PHONE_NUMBER>000000 R12: ffff9ca882b40060
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: R13:<PHONE_NUMBER>000000 R14:<PHONE_NUMBER>000000 R15:<PHONE_NUMBER>001000
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: FS:  00007fca9c3375c0(0000) GS:ffff9cab726c0000(0000) knlGS:0000000000000000
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: CR2:<PHONE_NUMBER>000148 CR3:<PHONE_NUMBER>982004 CR4:<PHONE_NUMBER>3706e0
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: Call Trace:
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  <TASK>
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  drm_gem_prime_import_dev+0x89/0x150 [drm]
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  ? fget+0x7c/0xd0
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  drm_gem_prime_fd_to_handle+0xc8/0x1d0 [drm]
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  ? drm_prime_destroy_file_private+0x20/0x20 [drm]
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  drm_ioctl_kernel+0xb8/0x150 [drm]
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  ? wp_page_reuse+0x66/0x80
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  drm_ioctl+0x231/0x3f0 [drm]
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  ? drm_prime_destroy_file_private+0x20/0x20 [drm]
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  __x64_sys_ioctl+0x8e/0xd0
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  do_syscall_64+0x5c/0x90
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  ? get_vtime_delta+0xf/0xc0
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  ? vtime_user_enter+0x1c/0x80
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  ? __context_tracking_enter+0x64/0xb0
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RIP: 0033:0x7fcaa13d481b
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1b 48 8b 44 24 18 64 48 2b 04 25 28 00
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RSP: 002b:00007ffce3b102d0 EFLAGS: 00000246 ORIG_RAX:<PHONE_NUMBER>000010
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RAX: ffffffffffffffda RBX: 00007ffce3b1036c RCX: 00007fcaa13d481b
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RDX: 00007ffce3b1036c RSI: 00000000c00c642e RDI:<PHONE_NUMBER>00012c
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RBP: 00000000c00c642e R08:<PHONE_NUMBER>00001e R09: 0000559db7ee1010
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: R10: 00007fcaa14c5aa0 R11:<PHONE_NUMBER>000246 R12:<PHONE_NUMBER>000073
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: R13:<PHONE_NUMBER>00012c R14: 0000559dc458a578 R15:<PHONE_NUMBER>000a00
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  </TASK>
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: Modules linked in: tun veth ax88179_178a uinput wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel hid_generic usbhid >
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp iTCO_wdt think_lmi kvm_intel intel_pmc_bxt wmi_bmof firmware_attributes_class iTCO_vendor_support ee1004 mei_hdcp intel_xhci_usb_role_switch intel>
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel:  e1000e tiny_power_button acpi_thermal_rel hwmon acpi_pad i2c_smbus cfg80211 snd_pcm ac xhci_pci battery int3403_thermal intel_rapl_common xhci_pci_renesas mei_me rfkill int340x_thermal_zone xhci_hcd int>
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: CR2:<PHONE_NUMBER>000148
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: ---[ end trace<PHONE_NUMBER>000000 ]---
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RIP: 0010:evdi_prime_import_sg_table+0xcc/0x150 [evdi]
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: Code: 89 da 41 89 df 48 63 db e8 b1 92 d5 fe 48 8d 3c dd 00 00 00 00 48 c1 eb 3d 75 62 be c0 0c 00 00 ba ff ff ff ff e8 a4 f5 e8 e2 <48> 89 85 48 01 00 00 48 89 c6 48 85 c0 74 4f 44 89 fa 4c 89 e7 e8
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RSP: 0018:ffffc0c8c3843cd8 EFLAGS: 00010246
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RAX: ffff9ca904ea0000 RBX:<PHONE_NUMBER>000000 RCX:<PHONE_NUMBER>000000
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RDX:<PHONE_NUMBER>000000 RSI:<PHONE_NUMBER>000000 RDI:<PHONE_NUMBER>000000
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: RBP:<PHONE_NUMBER>000000 R08:<PHONE_NUMBER>000000 R09:<PHONE_NUMBER>000000
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: R10:<PHONE_NUMBER>000000 R11:<PHONE_NUMBER>000000 R12: ffff9ca882b40060
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: R13:<PHONE_NUMBER>000000 R14:<PHONE_NUMBER>000000 R15:<PHONE_NUMBER>001000
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: FS:  00007fca9c3375c0(0000) GS:ffff9cab726c0000(0000) knlGS:0000000000000000
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
jun 11 21:42:06 comp-core-i5-8250u-8f89bf kernel: CR2:<PHONE_NUMBER>000148 CR3:<PHONE_NUMBER>982004 CR4:<PHONE_NUMBER>3706e0


Update to last chromium

Hi, you can upgrade to the latest chromium build version or tell how to do it??? Thanks.

@sergeymild
If i have time will upgrade to 55 version recently.
please see the README upgrade step

Has been upgraded to 55 kernel version


JSON returned by ichiran/cli

I'm using ichiran-cli with the -f argument to provide my scripts with the full segmentation of a sentence. I'm writing my own little parser for the returned JSON, but I'm having problems since there's lots of structure in it, and I don't know where to find everything or what exactly should I expect from it. Here is an example:
['itsuni', {'reading': '一に 【いつに】', 'text': '一に', 'kana': 'いつに', 'score': 128, 'seq': 1160930, 'gloss': [{'pos': '[adv]', 'gloss': 'solely; entirely; only; or'}], 'conj': []}, []]
Sometimes the 'gloss' list is empty, sometimes the 'conj' list is, and sometimes both in the case of e.g. suffixes. I don't know where to find the tense in the case of verbs.
Where can I find an explanation of the structure of the JSON that is returned by ichiran-cli?

Thank you very much. That should cover most words one encounters regularly. Is there no reference where I can find every type of word and structure that could be returned? If there is none, consider the issue solved.

@blunderedbishop you're probably missing conj.csv file from here or jmdict-data variable is pointing to the incorrect path in settings.lisp


Logs still showing even though it's disabled through config

Prerequisites

[ ] I am running the latest version. (up upgrade)
[x] I searched to see if the issue already exists.
[x] I inspected the verbose debug output with the -v, --verbose flag.
[ ] Are you an Up Pro subscriber?

Description
Logs like the ones below are overflowing cloudwatch metrics and thus increasing the overall bill. I've been looking for a way to disable those logs but the disable option is already set for me.
Example:
{"fields":{"app":"app-name","commit":"commit-hash","plugin":"relay","region":"us-east-1","stage":"production","version":"108"},"level":"info","timestamp":"2020-10-28T15:52:22.524151567Z","message":"{"}
currently using v1.5.1 (I'm maintaining the project so no upgrades were done)
Love Up? Yeah!
Please consider signing up for Up Pro (https://up.docs.apex.sh/#guides.subscribing_to_up_pro) or donating via https://opencollective.com/apex-up/donate.
Slack
Join us on Slack https://chat.apex.sh/

Fixed. Thanks anways


Config file + secret generation

Salt and secret are stored in the db as SALT and SECRET to align with the current naming in the env file.
Might want to change that to align with naming convention used in the db


Fix readme typo

Fixing the link to Llama.cpp

Thank you for your contribution and for highlighting the typo.
At the moment, we're focusing our efforts on accepting PRs that introduce new features or make significant documentation improvements. While we can't accept this PR, we definitely value your help and encourage you to continue submitting future PRs that align with our current focus.
We appreciate your understanding.


[BUG] Cannot have fsGroup injected

What happened:
I am trying to deploy the postgres into microshift. the postgres cannot be started successfully. the error is Permission denied to access /etc/ssh/sshd_config. the folder is mounted from a configmap. there is no fsGroup injected into the statefulset.
it works in KinD cluster or OCP cluster. for OCP cluster, scc can help to inject fsGroup: xxx so that the folder is accessible by that group. for KinD cluster, the fsGroup: 26 is injected as well ( I do not how to do it)
What you expected to happen:
the fsGroup: 26 is injected so that the pod can be running normally.
How to reproduce it (as minimally and precisely as possible):

docker run -d --rm --name hub --privileged -v hub-data:/var/lib -p 36443:6443 quay.io/microshift/microshift-aio:latest to start microshift
follow this document to deploy postgres https://access.crunchydata.com/documentation/postgres-operator/v5/quickstart/ into microshift

Anything else we need to know?:
Is it a bug or is it a designed behaviour? if it is a bug and was fixed, where can I get the latest image? Thanks.
Environment:

Microshift version (use microshift version):  quay.io/microshift/microshift-aio:latest
Hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Others:

Relevant Logs

The team is moving away from supporting deployment using podman and focusing on RPMs and systemd. The main branch has changed considerably since the 4.8 release, and as we're working on product builds we haven't been keeping the community build up to date. We do intend to resume work on Fedora support, but it may be a few months. In the mean time, if building from source from the main branch and deploying using systemd does not resolve this problem, please open a new issue with the details.


Mark the extension as parallel-safe

This has been tested in godotengine/godot-docs (https://github.com/godotengine/godot-docs/pull/2669), in which it seems to be working well so far.
This closes #32.

@djungelorm Bump :slightly_smiling_face:

Released in v1.1.13  :)


Whitespace in PDF Export

Fiddle: http://jsfiddle.net/0w6audhr/1/
The exported PDF has in the fiddle has a lot of whitespace on the right side of the chart. This seems to relate to the hight of the chart container in some way. A Container height above 1500px fails to produce a PDF completely.
Image based exports work fine.

I found a solution to the problem: Render the chart in portait mode.
In renderPdf change the following line.
var doc = new jsPDF('l', 'mm', [context.destWidth, context.destHeight]);;

to
var doc = new jsPDF('p', 'mm', [context.destWidth, context.destHeight]);;


Increment version for template releases

Increment package version after release of azure_template

@chidozieononiwu any reason why this PR was created and not automatically closed with the testing workflow?


Removed defaults for engagement tracking so that template settings could...

... be applied when using the SDK

Any reason not to merge this @nornholdj ? Do we need any additional tests here?

Sorry @richleland, I didn't realize that this was still open.  Yes I believe this can be merged.  Its to align with a change we made to the node sdk a while ago.  It was a bug where the sdk made it impossible to rely on the engagement settings on a template and would cause them to always be set on the transmission level.


[nova] use short service name for CommonName vencrypt cert

The CommonName has a max length of 64 bytes.
From https://docs.openstack.org/nova/latest/admin/remote-console-access.html#vnc-proxy-security
An x509 certificate to be presented to the VNC server. While libvirt/QEMU will not currently do any validation of the CommonName field, future versions will allow for setting up access controls based on the CommonName. The CommonName field should match the primary hostname of the controller node.

Related: https://issues.redhat.com/browse/OSPRH-8652

pinging container registry quay.rdoproject.org: Get "https://quay.rdoproject.org/v2/": dial tcp <IP_ADDRESS>:443: i/o timeout

/test openstack-operator-build-deploy-kuttl

/cherry-pick 18.0.0-proposed


Parse second column of the station_status table in Clearinghouse

@britt-allen can you add a description and project metadata?

I will when I get time.


Fix implicit any return type for jest TypeScript

When TypeScript is configured to not allow implicit any's, the
compilation fails with this error:
/path/to/project/node_modules/jest-enzyme/src/index.d.ts
[1] (17,9): error TS7010: 'toHaveText', which lacks return-type annotation, implicitly has an 'any' return type.

By adding the void return type to these definitions like we've done on
the others. It resolves this issue.

Whoops, just noticed https://github.com/blainekasten/enzyme-matchers/pull/102


Add confirmation dialog when exiting unsubmitted feature wish

When the user exits the request form, the data they have already entered in the text fields is lost. It could improve the user experience if a confirmation dialogue was displayed and the user was asked if they would like to discard the data they have already entered in the fields to ensure that exiting the view was not done accidentally.

I wonder if an even better enhancement is that the data in the text fields is just saved so when they exit and come back, the data remains there. The swift-sharing library could also make it easy to persist this only within an app session.


Unable to run a saved TM1py script from Jupyter Notebook

Hi All,
I have saved a TM1py script to move file between 2 SFTP servers, Script works fine when it run from a new notebook.
However when the notebook is saved and reopened in the next session it fails with "NameError: name 'paramiko' is not defined".
Sample Code :
ssh = paramiko.SSHClient()
ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy())
ssh.connect(hostname = "sftp.xxx-xxx.com",username  = 'xxxx', password = 'xxxxx', port=22)
sftp_client = ssh.open_sftp()
sftp_client.get('source','dest')
sftp_client.close()
ssh.close()
ssh = paramiko.SSHClient()
ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy())
ssh.connect(hostname = 'sftp-xx.planning-analytics.xxxx.com',username  = 'xxxx', password = 'xxxxx',port = 22)
sftp_client = ssh.open_sftp()
sftp_client.put('source','dest')
sftp_client.close()
ssh.close()

Not a  TM1py question, but are you perhaps missing the import paramiko statement at the top of your script?

Hi Marius,
I have included the import statement on the top.
import paramiko
from TM1py import TM1Service
I have installed TM1py in 2 different servers and saved the script with same name in both places, will it be the cause?

Please post the error that you receive when you run the script


Error parsing theme !

Hi,
Here is my output in Sublime Text. Can anyone help me to fix this error?
Errors parsing theme: icon_folder_loading is missing layer0.opacity, setting to 1.0 for backwards compatibility icon_file_type is missing layer0.opacity, setting to 1.0 for backwards compatibility
Build: 3143

One of the errors is from the A File Icon plugin. There's actually third error:
The following error is A File Icon related:
top level value must be an array

The next is Boxy Theme:
Errors parsing theme:
icon_folder_loading is missing layer0.opacity, setting to 1.0 for backwards compatibility

And then another one from A File Icon:
Errors parsing theme:
icon_file_type is missing layer0.opacity, setting to 1.0 for backwards compatibility

Yeah, that's known issue: https://github.com/ihodev/a-file-icon/issues/133
I'll fix that with the next release of A File Icon.

I also seem to be getting a message in the console to restart a lot. Is that part of the same issue?
***
A File Icon: Please restart Sublime Text for the applied icons to take effect ...
***

Nope, I think that you install new theme and A File Icon patches it. In any case wait next A File Icon version I have plans to significantly improve it.

I recently install 'A File Type' and using material theme. But its not working and  this is the message in console:
generating meta info summary
reloading settings Packages/User/Package Control.sublime-settings
reloading settings Packages/User/Preferences.sublime-settings

***
A File Icon: Please restart Sublime Text for the applied icons to take effect ...
***

Errors parsing theme:
Rule is missing a class name
icon_file_type is missing layer0.opacity, setting to 1.0 for backwards

any help?


Logan/fixes

Removed extra logic in postViews that used timers and drawRect to fill the cell. Instead just set background color
Sorted the liked posts alphabetically (for now, i guess we want to sort by liked date)
Implemented updated design for liked table view cells

Looks good, just fix that one issue and merge


[WIP] Fix TestResults

We use dotnet test and generate trx files, so I am not sure why this is needed.

Also, you need to always use / because the steps are shared between Windows and Unix

Can we close this out?

Oh, I see.
I thought we were using the NUnit runner to run the tests.


Increment version for core releases

Increment package version after release of azure-core

/check-enforcer override