From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C363E158086 for ; Wed, 12 Jan 2022 00:14:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8997D2BC02C; Wed, 12 Jan 2022 00:14:48 +0000 (UTC) Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 387012BC003 for ; Wed, 12 Jan 2022 00:14:47 +0000 (UTC) Received: by mail-ot1-x32d.google.com with SMTP id 60-20020a9d0142000000b0059103eb18d4so727183otu.2 for ; Tue, 11 Jan 2022 16:14:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:in-reply-to:references:mime-version:date:message-id:subject:to; bh=BZn0zN69MHAYXOD0UQnjNqOlUVsernUyIxV9WZ1618Y=; b=k5IQGwRZ50jfneAfEpiWabjB4sJc3Su0gRDNIMDndA+2EgQwqr9v78XzQJUbHGbBBy Qd1hjAAXjzI6QKWLPy0k762kTA4sD+CDnjkkLF3h4rBp8jtCO6pSc1lRNUIZXNTExgYx pFb46hxBc7yBwnFLs/uC69AdxRpJ/DSD9wnoiAoFtZwF+oQIcXmmZsqEUfIUP+fqtERT vjIjNKeRF7fRxzQxckrGOyFynrUTmSJ8VTjcHVJCgOusT6S8f4p7UMY9e0MeJdRhY9BU aNdFH+n8Hl2TImZRRvHoj4UR3iRM0EUKmD9ykiu8z0OpTmLdBfs9bmhLngW8BzBWInWX i78w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to; bh=BZn0zN69MHAYXOD0UQnjNqOlUVsernUyIxV9WZ1618Y=; b=R4QIhrN5mf75GBFBHrpPmU00XwEzyIPJQgzhTNLj+PmFzzcTNcVqVhob2E7KFmnMF0 5wQMtcg+vflqY8h7SjINQc1Sk5k9IF0FPKl1XqcGDgBgP1esHPEpLiTi2dzY+dAIYm7Q JpUJaVULyg3t/3sGqo4IMzjJITNVqYbSSzSPPvirJzukIjiVmClU9THhj6p0VzdDvxUg THvvsORaWe1mKSvdQnZ0kcsxvVDCopfE0XgoLnxuagWUFBK6Dke5/aCyIXwtkefA4jJy cO73SygKOAAaFSmUNDMNLKhgYq4ln9KeVR/m4rkIHqz/yVStS/4h3Kxuo5OmObktXmPz ieng== X-Gm-Message-State: AOAM532nhDAOh6exgAqJlHmy7KsLxWkSwmtF/+oZBCeZHMb0mbtlkLWQ rcPwX7ki3JUXvqio1iPOCusU7Zefu1+Bh95IoNiUfOIe X-Google-Smtp-Source: ABdhPJxVUGBZ2HSQJCOzp6WtpheATftLuTnm1e5Ac81DJIKoq4KEW3/xPI+5ngiDluM8gLIOzASpLOcrNNFWc3HOIMk= X-Received: by 2002:a9d:7c86:: with SMTP id q6mr5021522otn.229.1641946486542; Tue, 11 Jan 2022 16:14:46 -0800 (PST) Received: from 533632962939 named unknown by gmailapi.google.com with HTTPREST; Tue, 11 Jan 2022 18:14:45 -0600 From: ny6p01 In-Reply-To: <20220111102544.6992b86f@anfink-laptop> References: <20220111102544.6992b86f@anfink-laptop> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Date: Tue, 11 Jan 2022 18:14:45 -0600 Message-ID: Subject: Re: [gentoo-user] Strange behaviour disconnecting and reconnecting USB-C screen To: gentoo-user Content-Type: multipart/alternative; boundary="00000000000012179b05d557752d" X-Archives-Salt: 498027ae-df41-4807-9862-6a59922ec4a2 X-Archives-Hash: 831d62ed678ec353bce8ba83eca064b1 --00000000000012179b05d557752d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable What I would do is create a bash script and link to a keyboard shortcut to execute as needed. One of the advantages of xrandr is the ease of scripting= . Lee =F0=9F=98=8E On Jan 11, 2022 at 1:25 AM, Andreas Fink wrote: Hello, I've got a new laptop and see a strange behaviour when disconnecting and reconnecting my USB-C screen. Here are the steps that I am doing. I have a dual screen setup with xrandr, with my notebook screen being the primary screen and a second large external screen connected via USB-C to my notebook directly. Now I disconnect the USB-C cable and do not do anything software wise, i.e. my X-Server is still pretending to run on two screens, I can move the screen outside of my notebook screen (into the area where the external screen). Now I reconnect the USB-C cable but the screens stays blank (the the screen it says "No USB Type-C connection from your computer"). The only way to get a signal again is to first use xrandr to only use my notebook screen, and at the exact time udev gets a DRM event, and suddently my external monitor appears within xrandr as connected (I did not touch the cable, I only ran an xrandr command to use only the notebook screen). Right after the DRM event I can run the xrandr command to use both screens, but it is annoying to degrade first to one screen, because all windows are moved around and I do not end up with the same window setup as before. Using the same screen with the same experiment as described above but with a different notebook the screen is able to pick up the signal again, so it's not purely a problem with the external screen. Any idea what is going on and how I can workaround it? I just want to disconnect the cable and reconnect it without the need to switch any xrandr setup. Thanks for your ideas and help Andreas --00000000000012179b05d557752d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
What I would do is create a bash script a= nd link to a keyboard shortcut to execute as needed. One of the advantages = of xrandr is the ease of scripting.


Lee =F0=9F=98=8E
On Jan 11, 2022 at 1:25 AM, Andreas Fink <finkandreas@web.de> wrote: 

Hello,

I've got a new laptop and see a strange behaviour when disconnectin=
g

and reconnecting my USB-C screen.

Here are the steps that I am doing. I have a dual screen setup with

xrandr, with my notebook screen being the primary screen and a second

large external screen connected via USB-C to my notebook directly.

Now I disconnect the USB-C cable and do not do anything software wise,

i.e. my X-Server is still pretending to run on two screens, I can move

the screen outside of my notebook screen (into the area where the

external screen).

Now I reconnect the USB-C cable but the screens stays blank (the the

screen it says "No USB Type-C connection from your computer")=
. The only

way to get a signal again is to first use xrandr to only use my

notebook screen, and at the exact time udev gets a DRM event, and

suddently my external monitor appears within xrandr as connected (I did

not touch the cable, I only ran an xrandr command to use only the

notebook screen). Right after the DRM event I can run the xrandr

command to use both screens, but it is annoying to degrade first to one

screen, because all windows are moved around and I do not end up with

the same window setup as before.



Using the same screen with the same experiment as described above but

with a different notebook the screen is able to pick up the signal

again, so it's not purely a problem with the external screen.

Any idea what is going on and how I can workaround it? I just want to

disconnect the cable and reconnect it without the need to switch any

xrandr setup.



Thanks for your ideas and help

Andreas
--00000000000012179b05d557752d--