From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id cGaCOHUp2mWAGAAAe85BDQ:P1 (envelope-from ) for ; Sat, 24 Feb 2024 18:37:58 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id cGaCOHUp2mWAGAAAe85BDQ (envelope-from ) for ; Sat, 24 Feb 2024 18:37:58 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=GrVLG8uc; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1708796277; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=V7C1Wv4NFC0WAdWDn1DsU1O+SY83fDQ68467Z6O0Y6s=; b=H1iPk374oq1AQqKKtIq0jxuDVzW7TStkT0SyKHbrvzdTa0Q9qzv0ul3/hEW1FSSVDzqeQ3 GMpsCYdQCo8uLiOk3LdJ4qItpcJLf+gomyW4FqmCuHPhAbmzcEwMW+i0ugKDiZAKG7hxdd PesiqxdvfVGtGAlY5iRJ60FUukrsPm7C7xq9FGogsH5GVHxrw30ZR+1AgzbT3akt3wd+PZ e4icVRHn4LPtj3NdNf2XCnthL/u+p4qHLRAEvxMibSP/ugdus1FTi3vBcwYtCmnZht3Qdu CXMry7+f9LAfPwN6Pe478a6dXq+8MH1dgiGbfNtCYfPJjWL3c/W5SWgm+HgJGQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=GrVLG8uc; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1708796277; a=rsa-sha256; cv=none; b=Z8wQCtfk/jheMcQvAbHx6jhFi3F6PUDufiktoK3uFiZ5PVbiSC3zNnJD0pUpLjP4nQ4BsL TvZLNlCbGik2L1oRX+25vCZ3xGr1tA9wgJkYog0x4VPHpuzdB2d16QuOwLEfBUhAASLAUY th3oUFaVjDah+8zHHbq0YBStN3PAq3We+Xr1VCsxpADQW1WWUnzNzxfiXYixduE7bEn/JC MvVcfWmpV5FZedMIUenBSMZh6UzHGuh+5sA1weCU54nMLlGYslY1+gpst6D6pePjHnivmJ ETPTJRTuqn7hTSiKGIDYEHQhqVKDFwcDiz/wd1iubrXDNr2RfWsACxO1dKOtVw== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id B87E068F5F for ; Sat, 24 Feb 2024 18:37:57 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rdvxx-0001Wh-OG; Sat, 24 Feb 2024 12:37:37 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rdvxw-0001WI-02 for emacs-orgmode@gnu.org; Sat, 24 Feb 2024 12:37:36 -0500 Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rdvxt-00080g-T7 for emacs-orgmode@gnu.org; Sat, 24 Feb 2024 12:37:35 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 6B6EB240101 for ; Sat, 24 Feb 2024 18:37:31 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1708796251; bh=QW+HLEmBYwIsjOh3fAOdHz0TlJSTe5dtUTdAWfzC1+w=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=GrVLG8ucH07qPYc8D2eATmIRUoqsNCqVtrCLgOj2AHYoJbrq4/OUKIzG5d4sHjxQ/ QjAJdiGNeOt2In9p+E4w5iMoYS0reWkhSH9wunoSq1TKYYrhO5DH0Up+Fgd6ynFEwv cd1dXutBNlUSY026P/RUg8GTXvwCVeWbOyOjpMWdZ1sn7OOROcbPMSeyCrutIw+81m cbk1ng7548M9Y+0lBZPiieJNxqUmrvJfoQ/DZQg13j0VSmbB13fVVkpAkQ7UT1i+46 RLisE60w//Yv1w4ovjr2j4KyyFUgoFfS0/N/Mx4okFpJ8RhI3rxeEmDnorVGYuyRM7 2prynQkm/gLrg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4ThvGL6CGJz6tsb; Sat, 24 Feb 2024 18:37:30 +0100 (CET) From: Ihor Radchenko To: Sau P Cc: emacs-orgmode@gnu.org Subject: Re: [BUG] org clock wants to resolve clocks every time a clock in, occurs [9.7 (9.7-??-0dd2c5e @, /home/aayush/.config/emacs/.local/straight/build-29.2/org/)] In-Reply-To: References: Date: Sat, 24 Feb 2024 17:41:18 +0000 Message-ID: <87bk85wyip.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Scanner: mx10.migadu.com X-Migadu-Spam-Score: -4.62 X-Spam-Score: -4.62 X-Migadu-Queue-Id: B87E068F5F X-TUID: dQXd2ozjqeTn Sau P writes: > What should happen? > When I clock in, the clock should continue > until I clock out (or go idle). > > What actually happens? > Every minute I will get a popup requesting me to resolve a clock. > > This has been happening for a number of days now and I thought I had > dangling clocks but I don't think this is the case. > Even after "resolving" the clock (I have exhausted every option the > popup gives), the resolve popup comes back a minute later. Sounds like your `org-clock-idle-time' is customized to a small number (1 minute). > I believe I have seen someone with a similar issue on stackexchange, > here is the link: > https://emacs.stackexchange.com/questions/70084/resolving-idle-time-after-forced-closing-crash That sounds different and that is not a bug - org-clock-out does not trigger clock resolution. Only attempting to clock-in will do it. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at