Differences
This shows you the differences between two versions of the page.
| xfce:xfce4-session:4.16:knownproblems [2020/08/12 15:45] – created kevinbowen | xfce:xfce4-session:4.16:knownproblems [2021/02/09 01:16] (current) – sync with main page kevinbowen | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== Known problems | + | ~~NOTOC~~ |
| + | {{ : | ||
| + | ====== xfce4-session - Known Issues ====== | ||
| + | |||
| + | ==== Shutting down your computer using the session manager ==== | ||
| + | |||
| + | Since 4.1.5, the session manager supports only sudo(8)-based shutdown, other | ||
| + | method can be added by packagers if desired, just replace XfsmShutdownHelper | ||
| + | with your code. To be able to shutdown the computer, you must be listed | ||
| + | in the systems sudoers file, in particular, you must be allowed to execute | ||
| + | $HELPER_PATH_PREFIX/ | ||
| + | $HELPER_PATH_PREFIX is the directory passed to configure with the | ||
| + | --with-helper-path-prefix option or / | ||
| + | |||
| + | For example, you built xfce4-session with the default options, your hostname | ||
| + | is myhost and your user account is named myuser, then you'd have to add | ||
| + | the following line to your sudoers file (remember to use visudo to edit | ||
| + | that file): | ||
| + | |||
| + | myuser myhost=/ | ||
| + | |||
| + | Starting with xfce4-session 4.3.99.2 xfce4-session will first try to use | ||
| + | HAL (if built with D-Bus support) and fallback to the sudo method described | ||
| + | above. So if you have HAL installed on your system, and your account is | ||
| + | allowed to shutdown/ | ||
| + | sudo at all. | ||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Legacy session management ==== | ||
| + | |||
| + | As of version 4.1.7, the session manager includes native support for | ||
| + | applications that don't support the X11R6 session management protocol, | ||
| + | but support legacy (X11R5) session management. If you don't need legacy | ||
| + | session management support, you can disable it at compile time, giving | ||
| + | --disable-legacy-sm to ./ | ||
| + | |||
| + | The legacy sm code is ment as a replacement for smproxy (the X11 session | ||
| + | management proxy), which caused all kinds of trouble. That says, do NOT | ||
| + | EVER run smproxy in session that is managed by xfce4-session, | ||
| + | things will happen. The included legacy session management does everything | ||
| + | that smproxy would do, and besides that, it also support multiscreen | ||
| + | display and it is less error prone compared to smproxy (atleast once | ||
| + | the various bugs I introduced are fixed :-). | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Known issues | ||
| Installing xfce4-session from source possibly may conflict with the distribution package installation of xfce4-session 4.12, leading to a crash during startup. | Installing xfce4-session from source possibly may conflict with the distribution package installation of xfce4-session 4.12, leading to a crash during startup. | ||
| Line 12: | Line 60: | ||
| Here some more information on it: https:// | Here some more information on it: https:// | ||
| + | |||
| + | [[|Back To Top]] | ||
| + | ---- | ||
| + | [[ : | ||