Control: tag -1 - moreinfo On Fr 28 Nov 2014 20:21:23 CET, tony mancill wrote:
Hi Tony,
On 11/25/2014 07:05 AM, Mike Gabriel wrote:Control: tag -1 moreinfo Hi Tony, On So 23 Nov 2014 04:41:53 CET, tony mancill wrote:Package: mate-screensaver Version: 1.8.1-1 Severity: normal Dear Maintainer, This could be considered minor, but it is reproducible and slightly annoying. To reproduce: 1) Suspend the laptop while docked in a docking station (with multiple monitors, if that makes a difference). 2) Eject the laptop from the docking station and resume the laptop. 3) The X display will be hung and no unlock mechanism is visible until switching to a Linux console (Ctrl-Alt-F1) and killing the /usr/lib/mate-screensaver-gl-helper process. At this point, switching back to console 7 displays the expected lock dialog. Some other windows managers can handle this - it would great if the MATE environment didn't get confused. If it makes a difference, the laptop has an Intel HD 4000 chipset.To my experience the mate-screensaver "Unlock Screen" dialog always appears on the monitor / screen where the mouse pointer was left.Hi Mike, That's an interesting observation, and very possibly explains what's going on. The behavior you described is the same for me (either docked or undocked). I run with the following configurations: docked: - (2) external monitors and laptop lid is closed - primary display is thus an external monitor undocked: - just the laptop display (obviously) Note that when I suspend while undocked and then dock for the resume, I get the unlock dialog on the (external) display, so the current code seems "smarter" in this configuration.xfor debugging: If you move the mouse over to the notebook's screen, can you then normally unlock your session?That would be possible if I opted to run all (3) displays while docked, but not with the use case I'm reporting here. In case it helps, I am attaching a screenshot of Monitor Preferences in the docked configuration, along with the xrandr output.We won't probably get this fixed for Debian jessie (unless too many people find this too annoying), we will rather have to hand it over to MATE upstream and expect help from there.Of course - no worries there. I really enjoy using MATE and am happy to see it packaged and so conveniently accessible for Debian. This is just a minor nit I noticed when switching from other WMs. Please let me know if there is other information I can provide to help with the upstream bug report.
we won't get this fixed for jessie, I guess.However, the issue needs to be reported upstream and handled there. Can you write the upstream report [1]? (That would be awesome!)
Thanks, Mike [1] https://github.com/mate-desktop/mate-screensaver/issues -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
pgpkwL8BOqqhM.pgp
Description: Digitale PGP-Signatur