Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
xsession error: xsm not found
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
duderonomy
Guru
Guru


Joined: 20 Mar 2004
Posts: 349
Location: SF Bay Area

PostPosted: Sat Feb 18, 2012 2:49 am    Post subject: xsession error: xsm not found Reply with quote

Hello,

Does xorg-server depend on the package x11-apps/xsm?
Could this missing un-installed package be the reason login fails when starting X via xdm?

When I create .xsession file, run xdm, then attempt login, I see:
Failed to execute login command

However, when I remove .xsession and install .xinitrc file, I can start X form command line via startx.

Any suggestions on what I could read to learn more about the differences between xsession method and xinitrc method?

Cheers!
:D

PS: please let me know what info I need to supply...
Back to top
View user's profile Send private message
The Doctor
Moderator
Moderator


Joined: 27 Jul 2010
Posts: 2630

PostPosted: Sat Feb 18, 2012 3:03 am    Post subject: Reply with quote

You can check that with equery.
Code:
equery -d x11-apps/xsm
 * These packages depend on x11-apps/xsm:
x11-apps/xinit-1.3.2 (!minimal ? x11-apps/xsm)

so yes(ish).
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.
Back to top
View user's profile Send private message
duderonomy
Guru
Guru


Joined: 20 Mar 2004
Posts: 349
Location: SF Bay Area

PostPosted: Sat Feb 18, 2012 8:24 am    Post subject: Reply with quote

Thanks for the reminder about equery depends.

Code:
$ equery d x11-apps/xsm
 * These packages depend on x11-apps/xsm:
x11-apps/xinit-1.3.1-r1 (!minimal ? x11-apps/xsm)


So, how was it possible that my build process omitted xsm,
if I do not recall using the use flag "minimal"?
Very strange. I wonder if this is a bug.

It is notable however (and FTR) I did the emerge on xfce4
before xorg because I was hoping xorg would be a dependency of xfce.
It was not, IIRC.

On my box I currently see:
Code:
# eix xorg-server
[I] x11-base/xorg-server
     Available versions:  1.9.5-r1 1.10.4-r1 ~1.11.2-r1 1.11.2-r2 ~1.11.3 ~1.11.4 [M]~1.11.99.902 {dmx doc ipv6 kdrive minimal nptl static-libs tslib +udev xnest xorg xvfb}
     Installed versions:  1.11.2-r2(11:34:36 02/09/12)(ipv6 nptl udev xorg -dmx -doc -kdrive -minimal -static-libs -tslib -xnest -xvfb)
     Homepage:            http://xorg.freedesktop.org/
     Description:         X.Org X servers

# emerge -tvp xsm

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild  N     ] x11-apps/xsm-1.0.2  USE="-rsh" 143 kB

Total: 1 package (1 new), Size of downloads: 143 kB
 


If portage and the ebuild was working correctly, is there a way
to get portage/emerge to pull in the xsm package via dependency
of xorg at this point?

If not, is the one-shot emerge the usual way to solve this problem?

thanks!
:D
Back to top
View user's profile Send private message
duderonomy
Guru
Guru


Joined: 20 Mar 2004
Posts: 349
Location: SF Bay Area

PostPosted: Sat Feb 18, 2012 9:36 am    Post subject: Reply with quote

If "x11-apps/xinit" appears in the following dependency graph, and
xsm is not being included, then perhaps the problem is related to xinit?
Code:
# equery g xorg-server-1.11.2-r2
 * Searching for xorg-server1.11.2-r2 ...

 * dependency graph for x11-base/xorg-server-1.11.2-r2
 `--  x11-base/xorg-server-1.11.2-r2  amd64
   `--  app-admin/eselect-opengl-1.2.4  (>=app-admin/eselect-opengl-1.0.8) amd64
   `--  dev-libs/openssl-1.0.0g  (dev-libs/openssl) amd64
   `--  media-libs/freetype-2.4.8  (media-libs/freetype) amd64
   `--  x11-apps/iceauth-1.0.5  (>=x11-apps/iceauth-1.0.2) amd64
   `--  x11-apps/rgb-1.0.4  (>=x11-apps/rgb-1.0.3) amd64
   `--  x11-apps/xauth-1.0.6  (>=x11-apps/xauth-1.0.3) amd64
   `--  x11-apps/xkbcomp-1.2.3  (x11-apps/xkbcomp) amd64
   `--  x11-libs/libpciaccess-0.12.1  (>=x11-libs/libpciaccess-0.10.3) amd64
   `--  x11-libs/libXau-1.0.6  (>=x11-libs/libXau-1.0.4) amd64
   `--  x11-libs/libXdmcp-1.1.0  (>=x11-libs/libXdmcp-1.0.2) amd64
   `--  x11-libs/libXfont-1.4.4  (>=x11-libs/libXfont-1.4.2) amd64
   `--  x11-libs/libxkbfile-1.0.7  (>=x11-libs/libxkbfile-1.0.4) amd64
   `--  x11-libs/pixman-0.24.0  (>=x11-libs/pixman-0.21.8) amd64
   `--  x11-libs/xtrans-1.2.6  (>=x11-libs/xtrans-1.2.2) amd64
   `--  x11-misc/xbitmaps-1.1.1  (>=x11-misc/xbitmaps-1.0.1) amd64
   `--  x11-misc/xkeyboard-config-2.4.1-r3  (>=x11-misc/xkeyboard-config-2.4.1-r3) amd64
   `--  x11-libs/libXt-1.1.1  (x11-libs/libXt) amd64
   `--  x11-libs/libdmx-1.1.1  (>=x11-libs/libdmx-1.0.99.1) amd64
   `--  x11-libs/libX11-1.4.4  (>=x11-libs/libX11-1.1.5) amd64
   `--  x11-libs/libXaw-1.0.9  (>=x11-libs/libXaw-1.0.4) amd64
   `--  x11-libs/libXext-1.3.0  (>=x11-libs/libXext-1.0.99.4) amd64
   `--  x11-libs/libXfixes-5.0  (>=x11-libs/libXfixes-5.0) amd64
   `--  x11-libs/libXi-1.4.3-r1  (>=x11-libs/libXi-1.2.99.1) amd64
   `--  x11-libs/libXmu-1.1.0  (>=x11-libs/libXmu-1.0.3) amd64
   `--  x11-libs/libXrender-0.9.6  (x11-libs/libXrender) amd64
   `--  x11-libs/libXres-1.0.5  (>=x11-libs/libXres-1.0.3) amd64
   `--  x11-libs/libXtst-1.2.0  (>=x11-libs/libXtst-1.0.99.2) amd64
   `--  x11-libs/libXv-1.0.6  (x11-libs/libXv) amd64
   `--  media-libs/mesa-7.11.2  (>=media-libs/mesa-7.8_rc) amd64  [nptl=]
   `--  x11-libs/tslib-1.0-r1  (>=x11-libs/tslib-1.0) amd64
   `--  sys-fs/udev-171-r5  (>=sys-fs/udev-150) amd64
   `--  x11-apps/xinit-1.3.1-r1  (>=x11-apps/xinit-1.3) amd64
   `--  sys-devel/flex-2.5.35_p10  (sys-devel/flex) amd64
   `--  x11-proto/bigreqsproto-1.1.1  (>=x11-proto/bigreqsproto-1.1.0) amd64
   `--  x11-proto/compositeproto-0.4.2  (>=x11-proto/compositeproto-0.4) amd64
   `--  x11-proto/damageproto-1.2.1  (>=x11-proto/damageproto-1.1) amd64
   `--  x11-proto/fixesproto-5.0  (>=x11-proto/fixesproto-5.0) amd64
   `--  x11-proto/fontsproto-2.1.1  (>=x11-proto/fontsproto-2.0.2) amd64
   `--  x11-proto/glproto-1.4.14-r1  (>=x11-proto/glproto-1.4.14) amd64
   `--  x11-proto/inputproto-2.0.2  (>=x11-proto/inputproto-1.9.99.902) amd64
   `--  x11-proto/kbproto-1.0.5  (>=x11-proto/kbproto-1.0.3) amd64
   `--  x11-proto/randrproto-1.3.2  (>=x11-proto/randrproto-1.2.99.3) amd64
   `--  x11-proto/recordproto-1.14.1  (>=x11-proto/recordproto-1.13.99.1) amd64
   `--  x11-proto/renderproto-0.11.1  (>=x11-proto/renderproto-0.11) amd64
   `--  x11-proto/resourceproto-1.2.0  (>=x11-proto/resourceproto-1.0.2) amd64
   `--  x11-proto/scrnsaverproto-1.2.1  (>=x11-proto/scrnsaverproto-1.1) amd64
   `--  x11-proto/trapproto-3.4.3  (>=x11-proto/trapproto-3.4.3) amd64
   `--  x11-proto/videoproto-2.3.1  (>=x11-proto/videoproto-2.2.2) amd64
   `--  x11-proto/xcmiscproto-1.2.1  (>=x11-proto/xcmiscproto-1.2.0) amd64
   `--  x11-proto/xextproto-7.2.0  (>=x11-proto/xextproto-7.1.99) amd64
   `--  x11-proto/xf86dgaproto-2.1  (>=x11-proto/xf86dgaproto-2.0.99.1) amd64
   `--  x11-proto/xf86rushproto-1.1.2  (>=x11-proto/xf86rushproto-1.1.2) amd64
   `--  x11-proto/xf86vidmodeproto-2.3.1  (>=x11-proto/xf86vidmodeproto-2.2.99.1) amd64
   `--  x11-proto/xineramaproto-1.2.1  (>=x11-proto/xineramaproto-1.1.3) amd64
   `--  x11-proto/xproto-7.0.22  (>=x11-proto/xproto-7.0.22) amd64
   `--  x11-proto/dmxproto-2.3.1  (>=x11-proto/dmxproto-2.2.99.1) amd64
   `--  www-client/links-2.4-r2  (www-client/links) amd64
   `--  www-client/lynx-2.8.7_p1  (www-client/lynx) amd64
   `--  www-client/w3m-0.5.2-r4  (www-client/w3m) amd64
   `--  x11-proto/xf86driproto-2.1.1  (>=x11-proto/xf86driproto-2.1.0) amd64
   `--  x11-proto/dri2proto-2.6  (>=x11-proto/dri2proto-2.6) amd64
   `--  x11-libs/libdrm-2.4.27  (>=x11-libs/libdrm-2.4.20) amd64
   `--  sys-devel/libtool-2.4-r1  (>=sys-devel/libtool-2.2.6a) amd64
   `--  sys-devel/m4-1.4.15  (sys-devel/m4) amd64
   `--  x11-misc/util-macros-1.15.0  (>=x11-misc/util-macros-1.15.0) amd64
   `--  media-fonts/font-util-1.2.0  (>=media-fonts/font-util-1.2.0) amd64
   `--  dev-util/pkgconfig-0.26  (>=dev-util/pkgconfig-0.23) amd64
   `--  app-text/asciidoc-8.5.3  (app-text/asciidoc) amd64
   `--  app-text/xmlto-0.0.24-r1  (app-text/xmlto) amd64
   `--  app-doc/doxygen-1.7.3  (app-doc/doxygen) amd64
   `--  app-text/docbook-xml-dtd-4.1.2-r6  (app-text/docbook-xml-dtd) amd64
   `--  app-text/docbook-xml-dtd-4.2-r2  (app-text/docbook-xml-dtd) amd64
   `--  app-text/docbook-xml-dtd-4.3-r1  (app-text/docbook-xml-dtd) amd64
   `--  x11-base/xorg-drivers-1.11  (>=x11-base/xorg-drivers-1.11) amd64
[ x11-base/xorg-server-1.11.2-r2 stats: packages (75), max depth (1) ]

Back to top
View user's profile Send private message
The Doctor
Moderator
Moderator


Joined: 27 Jul 2010
Posts: 2630

PostPosted: Sat Feb 18, 2012 7:15 pm    Post subject: Reply with quote

Quote:
If portage and the ebuild was working correctly, is there a way
to get portage/emerge to pull in the xsm package via dependency
of xorg at this point?

If not, is the one-shot emerge the usual way to solve this problem?


I would expect that emerge -auvND world would catch that. If it does not then that is the perfect use for emerge -1.

Quote:
If "x11-apps/xinit" appears in the following dependency graph, and
xsm is not being included, then perhaps the problem is related to xinit?


I think that xsm is not included in your above graph because it is a dependency of a dependency.
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.
Back to top
View user's profile Send private message
duderonomy
Guru
Guru


Joined: 20 Mar 2004
Posts: 349
Location: SF Bay Area

PostPosted: Sat Feb 18, 2012 11:28 pm    Post subject: Reply with quote

penguin swordmaster wrote:
I would expect that emerge -auvND world would catch that.


This is what I would expect...
Uh... if a dependency of a dependency is broken then Gentoo is doomed, right? ;) lol!
I wonder if I can spot a bug by reading the ebuilds?
Seems something broken is lurking down there.
Is it likely to be a defect in an ebuild, as opposed to a broken portage engine?


penguin swordmaster wrote:
If it does not then that is the perfect use for emerge -1.


Code:
emerge -1 xsm


Cool. I like small world files.

So, yes indeed, the X Session Manager was definitely the component that was mysteriously missing.
Now I can run xdm, see a typical login screen, and after auth I see a full desktop loaded.
(not a hung UI and message "Failed to execute login command" on a black screen)

As I was attempting to isolate the issue, I tried different window managers.
One of them brought up an xterm without the surrounding desktop.
Xorg errors indicated it could not find xsm.
This is all starting to make sense. :)

Thanks much for the dialog, swordmaster... :)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum