Bug#450563: marked as done (xpdf: [missing feature] ignore Xresources and window at +0+0)
Your message dated Wed, 27 Jan 2021 15:38:10 +0100
with message-id <20210127143810.GW287729@ZEDAT.FU-Berlin.DE>
and subject line Re: Bug#383377: ignore Xresources and window at +0+0
has caused the Debian Bug report #383377,
regarding xpdf: [missing feature] ignore Xresources and window at +0+0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
383377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383377
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: xpdf: overrides window manager placement?
- From: Tim Connors <reportbug@rather.puzzling.org>
- Date: Thu, 08 Nov 2007 15:51:36 +1100
- Message-id: <20071108045136.28764.49637.reportbug@scuzzie.rather.puzzling.org>
Package: xpdf-reader
Version: 3.02-1.2
Severity: normal
On an xinerama aware set of screens, my window manager makes almost
all applications start up in the screen that currently owns the mouse
cursor. xpdf though always pops up at +0+0 on the left screen.
I can't see any geometries etc defined in my own dot files; is there
likely something I have missed, or this a real "feature"?
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages xpdf depends on:
ii xpdf-common 3.02-1.2 Portable Document Format (PDF) sui
ii xpdf-reader 3.02-1.2 Portable Document Format (PDF) sui
ii xpdf-utils 3.02-1.2 Portable Document Format (PDF) sui
xpdf recommends no packages.
Versions of packages xpdf-reader depends on:
ii gsfonts 1:8.11+urwcyr1.0.7~pre41-3 Fonts for the Ghostscript interpre
ii lesstif2 1:0.95.0-2.1 OSF/Motif 2.1 implementation relea
ii libc6 2.6.1-6 GNU C Library: Shared libraries
ii libfreetype6 2.3.5-1+b1 FreeType 2 font engine, shared lib
ii libgcc1 1:4.2.2-3 GCC support library
ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library
ii libpaper1 1.1.23 library for handling paper charact
ii libsm6 2:1.0.3-1+b1 X11 Session Management library
ii libstdc++6 4.2.2-3 The GNU Standard C++ Library v3
ii libt1-5 5.1.1-1.1 Type 1 font rasterizer library - r
ii libx11-6 2:1.0.3-7 X11 client-side library
ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar
ii libxp6 1:1.0.0.xsf1-1 X Printing Extension (Xprint) clie
ii libxpm4 1:3.5.7-1 X11 pixmap library
ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library
ii xpdf-common 3.02-1.2 Portable Document Format (PDF) sui
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: Adam Sampson <ats@offog.org>, 383377-done@bugs.debian.org
- Subject: Re: Bug#383377: ignore Xresources and window at +0+0
- From: Florian Schlichting <fsfs@debian.org>
- Date: Wed, 27 Jan 2021 15:38:10 +0100
- Message-id: <20210127143810.GW287729@ZEDAT.FU-Berlin.DE>
- In-reply-to: <X/ENoVgfxCrWM6MZ@cartman.at.offog.org>
- References: <20060816210837.GA21407@lapse.madduck.net> <X/ENoVgfxCrWM6MZ@cartman.at.offog.org>
On Sun, Jan 03, 2021 at 12:19:45AM +0000, Adam Sampson wrote:
> > In fact, I'd say that xpdf-reader always opens with top-left corner at
> > +0+0 and thus completely ignores any window hints from the window
> > manager.
>
> This bug seems to have been fixed -- I've tested it with Debian xpdf
> 3.04-4, upstream xpdf 3.04 and xpopple, and -geometry now sets the
> correct WM hint for position. (It does so via Motif, so this might have
> been a Lesstif/Motif problem.)
indeed. I'm thus closing this bug.
Florian
--- End Message ---
Reply to: