Your message dated Wed, 16 Nov 2016 14:50:43 -0500
with message-id <019901d24042$b7a85fd0$26f91f70$@yahoo.com>
and subject line Fixed: not a bug
has caused the Debian Bug report #844544,
regarding chromium: Window clipped over x11 (PuTTY + XMing)
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 ow...@bugs.debian.org
immediately.)
--
844544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 53.0.2785.143-1~deb8u1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
Starting chromium in a fowarded X11 session clips the window when I
attempt to resize it. After resizing, only a quarter of chromium is
visible, the rest of the client window is black, and unresponsive to
mouse clicks.
Client is PuTTY 0.67 with XMing 7.7.07 on Windows 7 Ultimate x86_64
I expect the chromium application to size itself to the client window.
-- System Information:
Debian Release: 8.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages chromium depends on:
ii libasound2 1.0.28-1
ii libatk1.0-0 2.14.0-1
ii libc6 2.19-18+deb8u6
ii libcairo2 1.14.0-2.1+deb8u1
ii libcups2 1.7.5-11+deb8u1
ii libdbus-1-3 1.8.20-0+deb8u1
ii libexpat1 2.1.0-6+deb8u3
ii libfontconfig1 2.11.0-6.3+deb8u1
ii libfreetype6 2.5.2-3+deb8u1
ii libgcc1 1:4.9.2-10
ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u5
ii libglib2.0-0 2.42.1-1+b1
ii libgnome-keyring0 3.12.0-1+b1
ii libgtk2.0-0 2.24.25-3+deb8u1
ii libjpeg62-turbo 1:1.3.1-12
ii libnspr4 2:4.12-1+debu8u1
ii libnss3 2:3.26-1+debu8u1
ii libpango-1.0-0 1.36.8-3
ii libpangocairo-1.0-0 1.36.8-3
ii libpci3 1:3.2.1-3
ii libspeechd2 0.8-7
ii libstdc++6 4.9.2-10
ii libx11-6 2:1.6.2-3
ii libxcomposite1 1:0.4.4-1
ii libxcursor1 1:1.1.14-1+b1
ii libxdamage1 1:1.1.4-2+b1
ii libxext6 2:1.3.3-1
ii libxfixes3 1:5.0.1-2+b2
ii libxi6 2:1.7.4-1+b2
ii libxml2 2.9.1+dfsg1-5+deb8u3
ii libxrandr2 2:1.4.2-1+b1
ii libxrender1 1:0.9.8-1+b1
ii libxslt1.1 1.1.28-2+deb8u2
ii libxss1 1:1.2.2-1
ii libxtst6 2:1.2.2-1+b1
ii x11-utils 7.7+2
ii xdg-utils 1.1.0~rc1+git20111210-7.4
chromium recommends no packages.
Versions of packages chromium suggests:
pn chromium-inspector <none>
pn chromium-l10n <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,
I erroneously reported in a bug in chromium.
The issue was resolved by restarting the XMing X server.
Thank you for your time,
Steven G. Messervey
--- End Message ---
