SessionMenuButton on greeter ignores new user session setting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Japanese Kaizen Project |
Expired
|
Undecided
|
Unassigned | ||
gnome-shell (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
It seems that SessionMenuButton of js/gdm/
gnome-shell greeeter menu ignores new user session setting and login as previous session selection.
How to reproduce:
1. Existing user (userA) login as "Ubuntu on Xorg"
2. Create new account (userB) from Settings application
3. Check new account select default session
$ grep XSession /var/lib/
XSession=
4. Logout exisiting user (userA)
5. Select userB on GDM
6. Check session selection
Expected result:
* Mark "Ubuntu" session
* Login userB as Wayland session
* Result of "echo $XDG_SESSION_TYPE" should be "wayland"
Actual result:
* Mark "Ubuntu on Xorg"
* Login userB as Wayland session
* Result of "echo $XDG_SESSION_TYPE" is "wayland"
---
Original message:
Ubuntu 17.10 で Ubuntu on Xorg が選択されているのに Wayland でログインされる
再現方法
1.) 既存のユーザーのログイン画面で Ubuntu on Xorg を選択してログイン
2.) ログインしたユーザーで gnome control center を起動し、ユーザーを新規作成
3.) ログアウトし、
4.) 歯車ボタンをクリックすると自動的に Ubuntu on Xorg が選択されているので、そのままログイン
5.) コマンドを実行して X と Wayland のどちらが動いているか確認
$ loginctl show-session 11 -p Type
Type=wayland
ログイン画面で勝手に Ubuntu on Xorg が選択されているものの、実際には Wayland が動作しているようです。
description: | updated |
Changed in ubuntu-jp-improvement: | |
status: | New → Incomplete |
status: | Incomplete → Confirmed |
Changed in gnome-shell (Ubuntu): | |
status: | New → Confirmed |
summary: |
- Ubuntu 17.10 で Ubuntu on Xorg が選択されているのに Wayland でログインされる + SessionMenuButton on greeter ignores new user session setting |
description: | updated |
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases: /wiki.ubuntu. com/Releases
https:/
We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.