lay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VdPX66j58z4D5V for ; Mon, 13 May 2024 16:07:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1715616454; a=rsa-sha256; cv=none; b=EmqlIYqQgIgNI+A7zsa1cdYYZXVjbFP07O9LB06ZKKrvNOK7rfxjyrt30S22pBoyAd1eiT nCTt7qKWqsolIiVDmPtZqs6ZHkZ/BoS9SbayUfaC+/qAuURqO0WzPwYIdRq5b+Z+E9vAHw 80zq4cvDfvlaHHgshrHZJcabQAGy1NpXvsJe8/w3j9fVtMfxg63iNoEF/aVQdx3CbbdRo/ 0MeTF9+M5rmeyMefFNAyC2TzAAvu2OQ7C7DrXTVMRj9SZj4seOIR//osl/EIX7UuwUEifm RQYXL1sUPJjNj25eUoptAOWHU5Tg0KIA837tk3qKiR1VQ9ZD8Yg/KOc/GT5a9g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1715616454; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vEEsVNZmahamMNtyjacPN7LZfgQfCg1fgj+ep6KrH7I=; b=sYtJZ2bQeZ32rOwM9BpkgP75mt4deLtYftFueV6SkuGaA2WoxO3/tTWz5inu9NUxtbHkkB Y2Xjf0ZXosAysgP8ASboS2jHxiuQXsgoI17wVO/nSafgLpsXL3KafP0fvVG5jnr0ufcCSp 4iIEsHi9Faf1A4BZxfJMNdfx+yEq3SirCb/ngu3o2c5pWY+rZzqVgviHQh24Q7l93N/+7h LJDxyBapAqdMijMWdvVa8eDoutV/z2iblr34ys1MtAeuuqkdL/zZXhsU3sKSelNzStVSJP U2mTMPfblAXffTRJYfzDQODWlVzYBeXCl3zPI6evXeVV2XuDlbbgBswblKW+nQ== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4VdPX66BXtzvZ4 for ; Mon, 13 May 2024 16:07:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 44DG7YLB032854 for ; Mon, 13 May 2024 16:07:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 44DG7YTP032853 for desktop@FreeBSD.org; Mon, 13 May 2024 16:07:34 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: desktop@FreeBSD.org Subject: [Bug 278952] x11/lightdm Date: Mon, 13 May 2024 16:07:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: madpilot@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: desktop@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Using and improving FreeBSD on the desktop List-Archive: https://lists.freebsd.org/archives/freebsd-desktop List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-desktop@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278952 Guido Falsi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madpilot@FreeBSD.org --- Comment #2 from Guido Falsi --- Hi, Thanks for the report. This is actually an issue with the upstream software. LightDM is not develo= ped for FreeBSD, in fact it is developed by Canonical, makers of Ubuntu Linux. Adding this would require development in the upstream software. Even if the fix will most probably be coming from a FreeBSD developer, ports are not the place for original development. Custom patches can and are adde= d, but that track should be taken only when it is impossible to get the requir= ed changes upstream. Due to this you really should file a bug report/feature request upstream, so any patches addressing this can also be attached there. If you have code to fix this issue please post it. Otherwise, someone will = need to take the thing in his hands and send a patch upstream, which can be adde= d to the port. BTW, have you tested the software behaviour in Linux? it is quite probable = it does the same there, if the issue also happens in Linux it is much more probable for the upstream to care. (I have no idea how difficult this would be to implement, or if & in user n= ames is a thing in Linux) --=20 You are receiving this mail because: You are the assignee for the bug.=