# bugs: 1, the localization becomes a freak, even when I set locale in gnome setting center, there is only few thing displayed in my locale 2, press control to the position of mouse does not work at all 3, to be discovered .. # not reasonable: 1, user can not lock screen by default, but you can use gsettings to change the default behaviour: gsettings set org.gnome.desktop.lockdown disable-lock-screen false 2, can not execute X-application(like gparted) with root privilige directly, you should invoke `xhost +local:` first, then you are free to go 3, need more documentation, I'd like to execute a script when login with gdm, tried gnome autostart application(not like to work, maybe I'm making something wrong), , indeed, this is not to blame for wayland, while, when login into gdm, change wayland to xorg, everything works well
It's hard to handle this set of notes, that doesn't have much information and debugging information attached to it, but some random thought dump back: # bugs list: 1. I'm not aware of any localization problems under Wayland, and pretty sure everything worked fine. There were some issues in the 3.20 or 3.22 era with applying /etc/env.d based things (one of which could be locales over systemd based on old guides), but other than that, would need much more information what's wrong here. Even an emerge --info would be a good start.. 2. This is https://bugzilla.gnome.org/show_bug.cgi?id=690055 # "not reasonable" list: 1. Screen locking works fine and actually much better than in X.org, because it can lock successfully even when something using a "grab" is open (such as a context menu or menubar menu, etc. I don't know what was wrong for you, or rather what had set disable-lock-screen to "true" for you. Maybe you did on X via gsettings or the appropriate settings dialog and forgot about it? 2. This is by design and stays like this. This is for security. Applications like these can be built better to run under the user and handle privilege requests and so on. Maybe launching such suboptimal applications with GDK_BACKEND=x11 works around the issue for the time being better than opening up even more security issues via xhost. ------ Ultimately if you need something that isn't available with Wayland, you can still use Xorg session until a time that it works on Wayland. In Gentoo the default will be switched back to Xorg before 3.24 goes stable. Wayland default will be targeted for 3.26. And even then if USE=wayland is actually set on relevant things... Please file concrete issues one by one, things that we can actually maybe do something about and investigate, not upstream feature requests. We can't handle such a discussion on multiple points as one bugzilla entry effectively.
(In reply to Mart Raudsepp from comment #1) > It's hard to handle this set of notes, that doesn't have much information > and debugging information attached to it, but some random thought dump back: > > # bugs list: > 1. I'm not aware of any localization problems under Wayland, and pretty sure > everything worked fine. There were some issues in the 3.20 or 3.22 era with > applying /etc/env.d based things (one of which could be locales over systemd > based on old guides), but other than that, would need much more information > what's wrong here. Even an emerge --info would be a good start.. > > 2. This is https://bugzilla.gnome.org/show_bug.cgi?id=690055 > > > # "not reasonable" list: > > 1. Screen locking works fine and actually much better than in X.org, because > it can lock successfully even when something using a "grab" is open (such as > a context menu or menubar menu, etc. I don't know what was wrong for you, or > rather what had set disable-lock-screen to "true" for you. Maybe you did on > X via gsettings or the appropriate settings dialog and forgot about it? > > 2. This is by design and stays like this. This is for security. Applications > like these can be built better to run under the user and handle privilege > requests and so on. Maybe launching such suboptimal applications with > GDK_BACKEND=x11 works around the issue for the time being better than > opening up even more security issues via xhost. > > ------ > > Ultimately if you need something that isn't available with Wayland, you can > still use Xorg session until a time that it works on Wayland. In Gentoo the > default will be switched back to Xorg before 3.24 goes stable. Wayland > default will be targeted for 3.26. And even then if USE=wayland is actually > set on relevant things... > > Please file concrete issues one by one, things that we can actually maybe do > something about and investigate, not upstream feature requests. We can't > handle such a discussion on multiple points as one bugzilla entry > effectively. to be honest, I'm a little sorry for my questions, they seems more like grumble, they are here is for a note, maybe some guy just need the infomation I know wayland for some time, it seems to be the time to move on. Thank you sincerely!
it seems that I forget the localisation problem. at the time when I'm using gnome on xorg, it's the procedure that I set the locale for terminal and X environment: 1, for the terminal: echo "Asia/Harbin" > /etc/timezone emerge --config sys-libs/timezone-data echo "en_US.UTF-8 UTF-8" >> /etc/locale.gen echo "zh_CN.UTF-8 UTF-8" >> /etc/locale.gen locale-gen eselect locale set en_US.UTF-8 echo "LANG=en_US.utf8" >> ~/.bashrc 2, for X: echo "LANG=zh_CN.utf8" > ~/.xprofile in gnome-setting-center: set language to chinese and format to china and these works fine for me, terminal in english and x in chinese for current user, X default to english for others several days ago when I'm trying to use gnome over wayland: 1, for the terminal: no change for the above 2, for the wayland: as it will not read .xprofile, do not use xprofile anymore mkdir -p ~/.config/environment.d/ echo "LANG=zh_CN.utf8" > ~/.config/environment.d/lang.conf in gnome-setting-center: set language to chinese and format to china after having these done, only the day of weak showing in the center of panel displays in chinese while the any other things stays in english, and also the application language is default to english I have nothing to try to figure out how to make it work for me, so I switched back to xorg 😭, and everything thing works fine as it was,,
Created attachment 509008 [details] emerge --info this is my emerge information after having @world rebuild three or four days ago
