Your message dated Sat, 24 Oct 2015 23:35:08 -0400 with message-id <CANTw=mmb+behrecjl+uwaya80oqpoujutsmntu75ncabkqx...@mail.gmail.com> and subject line Re: chromium: Reacts poorly to changes in dpi after suspend and resume has caused the Debian Bug report #790712, regarding chromium: Reacts poorly to changes in dpi after suspend and resume 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 [email protected] immediately.) -- 790712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790712 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: chromium Version: 43.0.2357.130-1 Severity: minor Minimal sequence to reproduce: % xrandr --dpi 200 % chromium & <suspend> <resume> In order to work around bug #789213 ("HiDPI mistakes with xfce4 again") under xfwm4 version 4.12.3-1, I ran "xrandr --dpi 200" before starting Chromium. After suspend and resuming, Chromium behaves very strangely with respect to the mouse: a mouse click registers for chromium some distance to the upper-left (varying depending on the precise position). The mouse pointer shape also changes accordingly; that is, the mouse pointer will change to a text insert symbol if the relevant point to the upper-left is a text input field. Note that the display resolution is reset to 96 dpi after suspending and resuming, for some reason I haven't tracked down. However, manually changing the dpi with xrandr does not cause strange behavior. -- System Information: Debian Release: stretch/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, 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.16.0-2 ii libc6 2.19-18 ii libcairo2 1.14.2-2 ii libcups2 1.7.5-12 ii libdbus-1-3 1.8.18-1 ii libexpat1 2.1.0-6+b3 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-4 ii libgdk-pixbuf2.0-0 2.31.4-2 ii libglib2.0-0 2.44.1-1.1 ii libgnome-keyring0 3.12.0-1+b1 ii libgtk2.0-0 2.24.28-1 ii libharfbuzz0b 0.9.41-1 ii libjpeg62-turbo 1:1.4.0-7 ii libnspr4 2:4.10.8-2 ii libnspr4-0d 2:4.10.8-2 ii libnss3 2:3.19.2-1 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 libsnappy1 1.1.2-4 ii libspeechd2 0.8-7 ii libspeex1 1.2~rc1.2-1 ii libsrtp0 1.4.5~20130609~dfsg-1.1 ii libstdc++6 5.1.1-12 ii libx11-6 2:1.6.3-1 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.2+dfsg1-3 ii libxrandr2 2:1.4.2-1+b1 ii libxrender1 1:0.9.8-1+b1 ii libxslt1.1 1.1.28-2+b2 ii libxss1 1:1.2.2-1 ii libxtst6 2:1.2.2-1+b1 ii x11-utils 7.7+3 ii xdg-utils 1.1.0~rc1+git20111210-7.4 chromium recommends no packages. Versions of packages chromium suggests: ii chromium-l10n 43.0.2357.130-1 -- no debconf information
--- End Message ---
--- Begin Message ---On Sat, Jul 25, 2015 at 10:07 PM, Michael Gilbert wrote: > Please submit this issue to crbug.com and link back here since this is > not a packaging issue. Not done, please reopen if that changes. Best wishes, Mike
--- End Message ---
