On Mon, 06 Oct 2014 13:15:54 -0400 Matthias Clasen <mclasen@xxxxxxxxxx> wrote: > Hey Jonathan, thanks for the feedback. Thanks to everybody for the responses! > > - The main thing is that resume does not work in F21. Things appear > > to suspend just fine, but there is no response to pressing the > > blinking power button. I simply have to hold it until it powers > > down hard and start over. > > On my own Carbon with F21, suspend/resume seems to work fine, with lid > close, power button or systemctl suspend. Given that you seem to have > ruled out a kernel problem, I would point at systemd as the best > starting point for further investigation. Is your system using EFI for > booting ? Yes, EFI. I have secure turned off at the moment, but for no particular reason; everything worked the same with it turned on. > > - Emacs is *totally* confused about its window size. Any new window > > comes up essentially full screen, but the sizes it shows when one > > resizes indicates that it thinks its window is quite small - even > > though text display works just fine. F20 shows this too, it's not an > > F21 specific thing. > > Emacs is using GTK+ in 'interesting' way, things could certainly go > wrong here. My system is not hidpi, but if I manually force a scale with > GDK_SCALE=2 emacs, it seems to mostly work as I would expect it - > everything is twice as big (except for the content font - thats the area > where emacs is most special). You can see the screenshot I sent for an example of how it looks. Running Emacs with GDK_SCALE set to 1 makes everything happy again. The HiDPI pixel scaling stuff seems to be full of surprises, though. I've been exploring the intersection with external monitors, which is...not fully pleasing. > > - The huge onscreen keyboard seems to be easy to provoke and hard to > > make go away; this does seem to be new with F21. Is there any way to > > just turn that off? I like my touchscreen, but it's permanently > > attached to a physical keyboard a few cm away; I will *never* want > > the onscreen one. > > To make it go away, use the keyboard button in the lower right corner. > Of course, having it come up unexpectedly is not great, and we need to > improve this. Just as a data point, this hasn't been a problem at all with F20; something changed in 21 to make it much more aggressive. > > - Whatever happened to the ability to associate actions with mouse > > button events? That seems to be gone in F20 too? Is that another > > one of those things we're not supposed to worry our pretty little > > heads about anymore? > > What actions do you mean here ? I could imagine at least 2 things you > might mean here - first, the modifier-click to trigger wm actions on the > content of windows or second, various titlebar click actions. The former. One other thing I've noticed, while I'm typing, is that something seems to reset the keyboard map occasionally. The X1 keyboard is a bit weird, requiring some repairs with xmodmap; occasionally those want to go away. They are easy to get back, of course, but it's a bit of an annoyance. Thanks, jon -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
