From nobody Mon Sep 18 16:09:13 2023 X-Original-To: freebsd-x11@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Rq8rN70qmz4tQHV for ; Mon, 18 Sep 2023 16:09:40 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-ua1-f49.google.com (mail-ua1-f49.google.com [209.85.222.49]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Rq8rN4Dn5z3RFg; Mon, 18 Sep 2023 16:09:40 +0000 (UTC) (envelope-from 6yearold@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ua1-f49.google.com with SMTP id a1e0cc1a2514c-7a7d7283fe5so1420784241.0; Mon, 18 Sep 2023 09:09:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695053379; x=1695658179; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=rL+uCZOreWpGJaDHxS3AvmR7SyHJ8rqqFruaWH+VsK4=; b=dZG9ou4bFK50bMTuDjw04M2JQDkkc3GUsADQrJUriySL2AfpQSR5aUCIR2/b/RajeL IDxvImXbLqV7vLdDLsis0fx1iEJBdg9kqOwhShpXx6o1kssxYt/3F8z1hGljudvazcUI hW2+CxNoM0s9gVAatvrxDViMqRVkVMtsYWes79vaf0rhsw33TGQ1nn77t4QICDAcoMNs trOxw/otTFSzhcZFD/FH85mCPLC5sYEDyhAT1cllmC0Bt867i0FbRAAmnL7mR53ohZT7 8dKr2vAIVs8yASMVqvAp+IRxyMHqlps0SHEVervecDh6E4MjqBfR90orJEkHx6PulfQ+ t09Q== X-Gm-Message-State: AOJu0YzlSL4Qyh129Wy9efEYQ8zUbTpa7IXjPCvPgOte0wnQDb2+BG1T 5DsKn0QwtPZyU89GBfB/S5iusbXMSL3QKyQ6 X-Google-Smtp-Source: AGHT+IEPMsMw47qmk41d3+Fr/fxz+1/KsLPrhAKDWMNqTPTAwFuelEfh66WDoaT07xWEAu/ssfVgYA== X-Received: by 2002:a1f:e3c6:0:b0:496:1f95:209a with SMTP id a189-20020a1fe3c6000000b004961f95209amr4280156vkh.15.1695053379140; Mon, 18 Sep 2023 09:09:39 -0700 (PDT) Received: from mail-vk1-f171.google.com (mail-vk1-f171.google.com. [209.85.221.171]) by smtp.gmail.com with ESMTPSA id g20-20020ac5c1d4000000b0048f8863b0easm1586379vkk.14.2023.09.18.09.09.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 18 Sep 2023 09:09:39 -0700 (PDT) Received: by mail-vk1-f171.google.com with SMTP id 71dfb90a1353d-495eb6e2b80so1578938e0c.1; Mon, 18 Sep 2023 09:09:38 -0700 (PDT) X-Received: by 2002:a1f:dec1:0:b0:48d:13be:92f2 with SMTP id v184-20020a1fdec1000000b0048d13be92f2mr5076468vkg.3.1695053378801; Mon, 18 Sep 2023 09:09:38 -0700 (PDT) List-Id: X11 List-Archive: https://lists.freebsd.org/archives/freebsd-x11 List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Gleb Popov Date: Mon, 18 Sep 2023 19:09:13 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: CPU consumtion by kglobalaccel / Xorg (was: Fwd: xorg-server-21.1.8_2,1 && key Control_L) To: Matthias Apitz , kde@freebsd.org, freebsd-x11@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4Rq8rN4Dn5z3RFg On Mon, Sep 18, 2023 at 7:04=E2=80=AFPM Matthias Apitz w= rote: > > I created a new user 'test', did login as 'test', copied my ~guru/.xinitr= c > to ~/.xinitrc, started KDE with 'startx' and started on the empty desktop > 'Konsole' from the Application launcher and with 'Konsole' the command > 'top'. Using the key 'Control_L' a few times, let's say 10 times in 10 > seconds, brings the proc Xorg to 60% and kglobalaccel to 20% CPU utilizat= ion. This is peculiar. At least we now know that it isn't your personal setup's problem. However, I'm not sure how to debug this further. How about killing the kglobalaccel process? Does this stop the CPU consumpt= ion?