You are not logged in.
I shut down my primary mythtv backend/frontend this morning to swap it's 160GB recording storage drive to a 250GB drive. I put the drive in another computer and had that computer build a RAID1 to copy the data from the 160 over easily.
Well I put the 250GB drive back in, turned the computer back on and of course, something went wrong.
The computer starts up, Slim login manager starts just fine, but as soon as I sign in, X restarts.
The slim log doesn't seem to show anything useful:
/usr/bin/xauth: creating new authority file /var/run/slim.auth
X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN
Current Operating System: Linux htpc-backend 2.6.20-ARCH #1 SMP PREEMPT Sat Feb 17 16:59:09 CET 2007 i686
Build Date: 10 January 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 19 22:44:55 2007
(==) Using config file: "/etc/X11/xorg.conf"
/usr/bin/xauth: creating new authority file /home/user/.Xauthority
Found Xv 2.2
XV_COLORKEY set to 0
slim: waiting for X server to shut downand the xorg log isn't any more useful. It can sit there at the slim login screen forever no problem, X doesn't crash and restart. If I am signed in as root or "user" (the user the mythfrontend and everything typically runs on) and issue the command "startx", X starts, then plops me back to a command prompt.
That was all happening the same with 2.6.19, so I upgraded to 2.6.20-4 and all the other packages that were updated since I built this system just over a week ago. Of course, upgrading the software didn't resolve the problem.
Here is my xorg.conf:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
#2.6.20 FontPath "built-ins"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "glx"
Load "extmod"
Load "xtrap"
Load "record"
Load "dbe"
Load "dri"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30 - 50
VertRefresh 60.0
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "NV34 [GeForce FX 5200]"
BusID "PCI:1:0:0"
Option "TVStandard" "NTSC-M"
Option "TVOutFormat" "SVIDEO"
Option "TVOverScan" "0.7"
Option "ConnectedMonitor" "TV"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 24
Modes "640x480"
EndSubSection
EndSectionI can get the contents of more config and log files if needed to help diagnose this.
Here's my slim.conf:
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path ./:/bin:/usr/bin:/usr/local/bin:/usr/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# Commands for halt, login, etc.
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd /usr/sbin/suspend
# Full path to the xauth binary
xauth_path /usr/bin/xauth
# Xauth file for server
authfile /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
# numlock on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
#
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd exec /bin/sh - ~/.xinitrc %session
login_cmd exec /bin/bash -login ~/.xinitrc %session
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
#
# sessionstart_cmd some command
# sessionstop_cmd some command
# Start in daemon mode. Valid values: yes | no
# Note that this can overridden by the command line
# option "-d"
# daemon yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg Welcome to %host
# shutdown / reboot messages
shutdown_msg The system is halting...
reboot_msg The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
#default_user simone
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme default
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.logLast edited by kansei (2007-02-22 04:45:23)
Offline
Could you post your .xinitrc?
hightower
Last edited by hightower (2007-02-20 12:39:18)
Offline
here's the .xinitrc for the user that I am signing in with.
The xvattr command is to get rid of the nvidia driver bug I'm seeing via my s-video out, and the other stuff is pretty self-explanatory.
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
#
#exec wmaker
# exec startkde
# exec icewm
# exec blackbox
exec xvattr -a XV_COLORKEY -v 0
exec amixer set Master 95% unmute
exec amixer set PCM 80% unmute
exec fluxboxOffline
Try to login as root or a different user.
hightower
Offline
yeah actually everything is running fine as root. I just did "startx" and then ran mythfrontend from the terminal window in that.
Offline
Don't use root! It was only a test. Perhaps you could create a new user and try step by step to adapt your old config to this user.
hightower
Offline
yeah it's worth a shot.
it's not a massive security risk to run mythfrontend as root, no matter how much you try to convince me that it is.
this is a "production" level system in the house so I gotta keep it up and running with the frontend running as root until I get it sorted out (I have final exams starting tomorrow so not until this weekend). There's no personal data or anything at all sensitive on the computer so if it get hax0red, oh well. plus, not a single port open on the firewall forwards to that computer so I'm not worried. It's just the primary backend and living room frontend in the house.
Offline
Your problem is in .xinitrc. You see, in the unix world exec means something along the lines of "replace the current process with what this command does". When you use exec in a shell script (like .xinitrc is) the script will end right there. In other words, you only want the last line of your .xinitrc to contain exec, otherwise your session ends when xvattr is done doing its thing. Just remove the exec word from all xvattr and amixer lines, and you're good.
All of your mips are belong to us!!
Offline
why did it work for a whole week the other way o_O maybe I never restarted X so it never even had to deal with that.. hmm
Offline
SOLVED. Thanks guys! it was the .xinitrc after all, nothin wrong with slim. Oh well, I'm using 2.6.20-4 now, finally integrated ivtv drivers yay!
Offline