X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=content-transfer-encoding:content-type
	:date:from:in-reply-to:message-id:mime-version:references
	:reply-to:subject:to:x-me-proxy:x-me-proxy:x-me-sender
	:x-me-sender:x-sasl-enc; s=fm1; bh=6smaWG0NtSjaU9j6cv5Mb2zrPjE/O
	87pS7jG7D1bUyk=; b=mJwM//ml2BR2jQfCV6NEaV+5+L7c/YUn9p0aaQVGFSilW
	M3RVSsHa7HkhkZb4df6DEZiRMz+YyPKFSayCyGkiWIT3aKT/8P73xpZQldp9DXfZ
	w1dcoP7laxAkCSSP33OEoa7E1tSTgwUVUHS1GZnz5rc2nE5VmjHih+YIR1s6H/Mk
	pWl1Wf/oMm5f2HHx1ekQV8lFJABAAZpODYtGqZCFZbyJ1TBbLy8dwsS6mWyHgKZR
	O7EJLmAjUs2ez5qIYF4jQlgHpkIZSly/XqyU34ow+ofnDOt2TQ0XyT4bwOhl/d0+
	sADwtz+XRuhS0DT5K9z3+IojNxkN1/2VgrhTxEC+g==
X-ME-Sender: <xms:XsrvX2W7GP-6VqBEdPJtB6X5P5rW4prnCMxxUJRMhHBX6eXo5p0s2Q>
    <xme:XsrvXymk9nSDGyt0sLTTZ1DNpVbnCeVDDqpuNc05Ua4srKWTNgejO1Apjl-4tT-_h
    iFp-flbrHwgQq_rEA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrvddvkedgfeehucetufdoteggodetrfdotf
    fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
    uceurghilhhouhhtmecufedttdenucenucfjughrpehruffvfhfhkffffgggjggtgfesth
    ejredttdefjeenucfhrhhomhepifhirhhvihhnucfjvghrrhcuoehghhgvrhhrlhesfhgr
    shhtmhgrihhlrdgtohhmqeenucggtffrrghtthgvrhhnpeejieefiefhfeffueekfedvve
    efvddthefhhfegvdejfedtleeuheehtedufeetjeenucffohhmrghinhepshhlrggtkhgs
    uhhilhgushdrohhrghenucfkphepuddtkedrvdduhedrudelhedrvddtheenucevlhhush
    htvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehghhgvrhhrlhesfhgr
    shhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:XsrvX6YTrT-DIyHR8I7mLcmRSxrAs3mfAE-LHjpWkJxIH_b7bXYXcA>
    <xmx:XsrvX9XtQ_IvAxbPmXONESPh1P0bTL7zfwWScWpYsBMwkf4G6rmxUQ>
    <xmx:XsrvXwlmOWGdOhN51Rw0zybdxek6foEXChVLHMMLv-nvDWXlUHSPOg>
    <xmx:XsrvX8xNfZtM0JElpbx2i-_XQQ-BEcKjK9AzFH7JD0DTSrenEpMFeQ>
Subject: Re: [geda-user] gEDA 1.10.2 printing issues (was [ANNOUNCE]...)
To: geda-user AT delorie DOT com
References: <9cb1778f-8309-0550-e4a4-b32d8f9b1afd AT fastmail DOT com>
 <alpine DOT DEB DOT 2 DOT 22 DOT 394 DOT 2012280026300 DOT 2202 AT yoga>
 <7b650ea3-093f-1a1d-7e93-8204150991f9 AT epilitimus DOT com>
 <98d7a00d-3c35-0aa3-3cb9-b6f536efdf21 AT fastmail DOT com>
 <da41469b-6952-3fda-669f-d621ffc9f875 AT epilitimus DOT com>
 <3fd7d6d9-6908-bb13-6ed9-5fe46d9552a5 AT fastmail DOT com>
From: "Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID: <5a111b0c-abc9-f005-cda6-6409c59a2d8a@fastmail.com>
Date: Fri, 1 Jan 2021 17:18:10 -0800
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:68.0) Gecko/20100101
 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <3fd7d6d9-6908-bb13-6ed9-5fe46d9552a5@fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 12/29/20 2:06 PM, Girvin Herr (gherrl AT fastmail DOT com) [via 
geda-user AT delorie DOT com] wrote:
>
> On 12/29/20 11:49 AM, Glenn (glimrick AT epilitimus DOT com) [via 
> geda-user AT delorie DOT com] wrote:
>> I am just guessing here but the 1948 is probabliy the PID thunderbird
>> was running as so it would make sense that they all have the same #. All
>> the warnings mean is that thunderbird made a request on the dbus and
>> that request didn't succeed. Again as a guess thunderbird was probably
>> trying to find out which printers supported that paper size. Lots of
>> things use dbus, and anything that does so via gnome will be prone to
>> issuing gdbus errors/warnings because that is the gnome implementation
>> of the dbus interface. Avahi seems to be fairly widely used for service
>> discovery.
>>
>> Based on what I know so far I don't think the dbus message is connected
>> to the hotkey problem and is probably an artifact of Slackware being
>> bare bones. By which I mean the Volkerding focuses on producing a basic
>> working system, rather than trying to produce a system that has every
>> possible whizbang on it. Makes the user work a bit more, but you gain a
>> better understanding of how the system works, IMO. Sometimes software
>> that is ubiquitous, but not mission critical, gets left out to be added
>> if the users want it. I think avahi falls into the category.
>>
>> Another guess, there are two messages because based on my quick review
>> of the gtk print backend it makes a primary attempt at service discovery
>> and then a fallback attempt if the primary fails. But I haven't run the
>> code in a debugger to know for certain.
>>
>> While they look ominous they are really only informational and not what
>> I would consider and "ERROR". If you had avahi running and got this then
>> yes it is important, but not in this case.
>>
>> Just my $0.02 worth. B)
>> Glenn
>
> Glenn,
>
> I see SlackBuilds.org has an avahi Slackware package available. When I 
> get a few moments, I may try to install it and see if it quiets things 
> down a bit. If not, no great loss.
>
> Thanks.
>
> Girvin
>
>
Greetings,

This is an update to the symptoms of this problem. I have been able to 
duplicate the problem with another schematic, so it doesn't seem to be 
schematic file dependent. The problem is that once Ctrl-P is used to get 
the print dialog, even if that print dialog is cancelled, subsequent 
Ctrl-Ps do not do anything. Ctrl-P is "locked out". I discovered today 
that is not entirely true. Once this "lockout" occurs, I can switch 
focus out of the schematic window and when I switch focus back to the 
schematic, I can do a Ctrl-P again and get the print dialog. However, 
once again, subsequent Ctrl-Ps are locked out until I do the focus trick 
again. Note that I do not have to do anything in the sidebar, just click 
in it and click back in the schematic window. Also, clicking anywhere on 
the desktop and clicking back on the schematic will clear it. In fact, 
just clicking on the schematic in the main window will clear the 
lockout. So, something about focus causes and clears this problem. Mouse 
clicks!?

HTH.

Girvin