Summary: | x11-apps/xinit-1.2.0 breaks my login manager (slim) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Helmut Jarausch <jarausch> |
Component: | [OLD] Library | Assignee: | Jeremy Olexa (darkside) (RETIRED) <darkside> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | skrattaren, yaq |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Helmut Jarausch
2009-11-15 14:50:08 UTC
Try setting -minimal for xinit. I didn't have time to analyze it any further, but it works for me. It actually didn't work for me, problem still occurs. Sorry for the inconvenience. I have the same issue,installing xinit-1.2.0 with -minimal won't help either my xorg.conf can be found here: http://dpaste.com/121053/ and here's startx output: http://dpaste.com/121052/ I have the same problem. Apparently the file /etc/X11/xinit/xinitrc no longer has this section: # First try ~/.xinitrc if [ -f "$HOME/.xinitrc" ]; then XINITRC="$HOME/.xinitrc" if [ -x $XINITRC ]; then # if the x bit is set on .xinitrc # it means the xinitrc is not a # shell script but something else exec $XINITRC else exec /bin/sh "$HOME/.xinitrc" fi So it never tries to run .xinitrc in my home directory, then the failsafe section also fails because after running emerge --depclean xterm xclock and twm packages are removed, but xinit-1.2.0 still depends on them. Bug number 293342 is related to this one. I'm not sure whether there's a real bug here. We did change a few things : The system xinitrc no longer looks at users' .xinitrc because startx is already responsible for this. Now I don't know what slim does, but if slim does indeed run the system's xinitrc, it should be fixed to look for users' too. The old behavior was a Gentoo-only behavior and we fixed it to how it really should be (and like it is on all other distros). So please try xinit-1.2.0-r1 which fixes the xterm/XTERM issue. If that's still not enough, we'll get slim's maintainer here to take a look at the issue. Thanks (In reply to comment #5) > I'm not sure whether there's a real bug here. We did change a few things : > > The system xinitrc no longer looks at users' .xinitrc because startx is already > responsible for this. Now I don't know what slim does, but if slim does indeed > run the system's xinitrc, it should be fixed to look for users' too. The old > behavior was a Gentoo-only behavior and we fixed it to how it really should be > (and like it is on all other distros). > > So please try xinit-1.2.0-r1 which fixes the xterm/XTERM issue. If that's still > not enough, we'll get slim's maintainer here to take a look at the issue. > > Thanks > I need some help! slim has a 'login_cmd' in /etc/slim.conf which I can configure. But when to execute /etc/X11/xinit/xinitrc ? The new version of it executes /etc/X11/chooser.sh and all scripts in /etc/X11/xinit/xinitrc.d what I don't want to. May I skip execution of /etc/X11/xinit/xinitrc altogether and just exec /home/$USER/.xinitrc ? Many thanks, Helmut. Try setting the XSESSION variable in your bashrc or something. You should read the scripts you mentioned, they also contains clues that could help you out. In any case, it's either a slim bug/missing feature or a just a configuration issue. Thanks (In reply to comment #7) > Try setting the XSESSION variable in your bashrc or something. You should read > the scripts you mentioned, they also contains clues that could help you out. > > In any case, it's either a slim bug/missing feature or a just a configuration > issue. I did read the files! And I did say I don't want to execute the new /etc/X11/xinit/xinitrc since it unconditionally executes /etc/X11/chooser.sh (if present) and the scripts in /etc/X11/xinit/xinitrc.d (there are some) But on the other hand I need the first part of /etc/X11/xinit/xinitrc like xrdb -merge $sysresources xmodmap $sysmodmap xrdb -merge "$userresources" xmodmap "$usermodmap" Now I am forced to include these into my ~/.xinitrc and check each new version of /etc/X11/xinit/xinitrc and fix my .xinitrc accordingly. The old solution which skipped executing etc/X11/chooser.sh and the scripts in /etc/X11/xinit/xinitrc.d if a user's .xinitrc is available was much more user friendly. The argument that other distributions handle it the "new" way doesn't convince me. I using Gentoo because it's better isn't it? Helmut. (In reply to comment #8) > I did read the files! And I did say I don't want to execute the new > /etc/X11/xinit/xinitrc > since it unconditionally executes /etc/X11/chooser.sh (if present) > and the scripts in /etc/X11/xinit/xinitrc.d (there are some) > > But on the other hand I need the first part of /etc/X11/xinit/xinitrc > like > xrdb -merge $sysresources > xmodmap $sysmodmap > xrdb -merge "$userresources" > xmodmap "$usermodmap" > > Now I am forced to include these into my ~/.xinitrc and check each new > version of /etc/X11/xinit/xinitrc and fix my .xinitrc accordingly. You're not forced to do anything, those scripts are there to _help_ you. If you don't like them, replace them. You've found out slim's preference. Just create a new script, shove it into /etc/helmuts-xinit-scripts/ and be done with it. > The argument that other distributions handle it the "new" way doesn't > convince me. I using Gentoo because it's better isn't it? Gentoo is about _empowering_ the user, not doing hand-holding. We're not hiding anything, you have access to all the scripts and you can easily create your own packages, should you wish to do so. If _really_ something we provide doesn't suit your needs, then just replace it. You obviously seem to be able to do so. Given that slim is - according to Jeremy, its maintainer - a piece of junk, I don't think there's anything to be done here for either of us. :) Closing INVALID because there's no other resolution that really fits. Thanks |