You are not logged in.
Hello all!
I'm using Arch for 6-7 months now. First I installed it on my Lenovo laptop (nvidia gpu) everything was fine, 0 problems. Now I installed it on my old PC (ati gpu, hd4850), I'm using slim and openbox. Everything is ok, except one thing. When I log in (in slim) I get black screen and nothing happens. Then when I have this black screen I switch to console, login to the same user which I typed in slim, run startx command I get the same black screen. Next I go back to the console, xorg console output gives 0 erros. Then I kill the xorg (ctrl+c) and switch back to the X (where the blackscreen still is) and openbox magically started and everything is ok. I have to do this procedure everytime I reboot. Everything is up to date (using xorg 1.11 and catalyst 12.4, used wiki instructions). Ati driver is ok, I'm able to play 3d games. I'm dealing with this issue for about 10h and I'm confused now how to repair it. Any advice would be great. Here are my config files:
.xinitrc
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
exec ck-launch-session openbox-sessionrc.conf
#
# /etc/rc.conf - Main Configuration for Arch Linux
#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="pl_PL.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Warsaw"
KEYMAP="pl"
CONSOLEFONT="lat2-16"
CONSOLEMAP="8859-2"
USECOLOR="yes"
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
#
MODULES=(loop)
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="ArchCan"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
#
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
interface=eth0
address=
netmask=
broadcast=
gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This requires the netcfg package
#
#NETWORKS=(main)
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
#
DAEMONS=(hwclock syslog-ng dbus networkmanager netfs crond slim)inittab
#
# /etc/inittab
#
# Runlevels:
# 0 Halt
# 1(S) Single-user
# 2 Not used
# 3 Multi-user
# 4 Not used
# 5 X11
# 6 Reboot
## Only one of the following two lines can be uncommented!
# Boot to console
id:3:initdefault:
# Boot to X11
#id:5:initdefault:
rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p
# -8 options fixes umlauts problem on login
c1:2345:respawn:/sbin/agetty -8 -s 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 -s 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 -s 38400 tty3 linux
c4:2345:respawn:/sbin/agetty -8 -s 38400 tty4 linux
c5:2345:respawn:/sbin/agetty -8 -s 38400 tty5 linux
c6:2345:respawn:/sbin/agetty -8 -s 38400 tty6 linux
# Serial Virtual Console for KVM and others VMs
#s0:2345:respawn:/sbin/agetty -8 -s 9600 ttyS0 linux
# Hypervisor Virtual Console for Xen and KVM
#h0:2345:respawn:/sbin/agetty -8 -s 38400 hvc0 linux
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
# Example lines for starting a login manager
x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/bin/slim >/dev/null 2>&1
# End of filexorg.conf
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
EndSection
Section "Module"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Files"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/cantarell"
FontPath "/usr/share/fonts/cyrillic"
FontPath "/usr/share/fonts/encodings"
FontPath "/usr/share/fonts/local"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/OTF"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/util"
EndSection
Section "DRI"
Mode 0666
EndSectionLast edited by chevy (2012-06-29 17:20:38)
Offline
ck-launch-session is not needed anymore in .xinitrc since slim 1,3.x. And I would try starting slim from initab instead of rc.conf, and disabeling xdm as well.
Last edited by swanson (2012-06-29 19:16:16)
Offline
First, remove the ck-launchs-session from your xinitrc. There are countless threads describing why if you are curious. I doubt, however, that this would lead to the problems you are describing.
Next, Slim is the devil. Yes, bashing doesn't help, but it is *very* finiky software. Id recommend taking slim out of deamons and putting it in inittab instead. This has solved many problems for people with slim - it does not seem to "work as advertised" when run from the daemons array. [Excorsize one daemon].
Edit: swanson beat me to both points. But now they've been suggested twice.
Last edited by Trilby (2012-06-29 19:18:29)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I did like you said. Now when I login in slim it takes about 20-30s to start openbox. I dont have to switch between cli and gui now. I think the problem now is dbus. I read that dbus problems may slow openbox. And one thing more, when I plugin a pendrive it doesnt automount. Using thunar I get console output:
(thunar:728): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supportedEdit...
I tryied with lightdm. It doesnt start at all. I'm getting "id "x" respawning too fast disabled for 5 minutes" even if I have dbus id daemons arrey.
Last edited by chevy (2012-06-29 21:40:24)
Offline
Check the output of 'ck-list-sessions', it should contain a session with a line 'active = TRUE'. I think you should first check your config files, because I suspect there are problems there.
However, you could also be bitten by this bug: https://bugs.archlinux.org/task/30476. The bug report has a workaround/fix.
Offline
Do you have gvfs installed? Dp you have "thunar --daemon &" in autostart?
Offline
For Openbox as a stand-alone wm, using startx, this is the recommended ~/.xinitrc:
exec ck-launch-session dbus-launch openbox-sessionhttps://wiki.archlinux.org/index.php/Op … d-alone_WM
But if you use SLiM...
https://wiki.archlinux.org/index.php/Sl … vironments
Basically it says that your ~/.xinitrc should only have:
exec openbox-sessionThe note says that as of v1.3.3, it starts "ck-launch-session" and that you should add "dbus-launch" to the login_cmd line from /etc/slim.conf.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Searching more in logs, I've found:
Jun 30 10:48:55 ArchCan dbus[358]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Jun 30 10:48:55 ArchCan dbus[358]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 30 10:48:55 ArchCan dbus[358]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Jun 30 10:48:55 ArchCan console-kit-daemon[461]: WARNING: polkit_authority_get: Error getting authority: Error initializing authority: Could not connect: No such file or directory
Jun 30 10:48:55 ArchCan dbus[358]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Jun 30 10:48:56 ArchCan dhcpcd[451]: eth0: sending IPv6 Router Solicitation
Jun 30 10:48:56 ArchCan dbus[358]: [system] Activating service name='org.freedesktop.RealtimeKit1' (using servicehelper)
Jun 30 10:48:56 ArchCan dbus[358]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Jun 30 10:48:56 ArchCan dbus[358]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Jun 30 10:49:00 ArchCan dhcpcd[451]: eth0: sending IPv6 Router Solicitation
Jun 30 10:49:00 ArchCan dhcpcd[451]: eth0: no IPv6 Routers available
Jun 30 10:49:08 ArchCan NetworkManager[383]: <info> (eth0): IP6 addrconf timed out or failed.
Jun 30 10:49:08 ArchCan NetworkManager[383]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jun 30 10:49:08 ArchCan NetworkManager[383]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jun 30 10:49:08 ArchCan NetworkManager[383]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jun 30 10:49:21 ArchCan dbus[358]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Jun 30 08:49:21 ArchCan rtkit-daemon[550]: Warning: PolicyKit call failed: Activation of org.freedesktop.PolicyKit1 timed out
Jun 30 10:49:23 ArchCan dbus[358]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Jun 30 10:49:24 ArchCan kernel: [ 46.113860] fuse init (API version 7.18)
Jun 30 10:49:48 ArchCan dbus[358]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Jun 30 08:49:48 ArchCan rtkit-daemon[550]: Warning: PolicyKit call failed: Activation of org.freedesktop.PolicyKit1 timed outAnd I found something similar on Gentoo forums (http://forums.gentoo.org/viewtopic-p-7058298.html). Where I can find older versions of polkit package?
Offline
Where I can find older versions of polkit package?
Offline
polkit 0.105 works ok here with slim and openbox-session. The Gentoo thread was about polkit 0.106. Are you sure that's your problem?
Offline
I've given up. I reinstalled Arch. Now everything seems to be ok. However I wanted to replace Slim with Lightdm and lightdm still gives me "respawning too fast error". But with slim and openbox everything now is ok. Thank you everyone for your advices.
Offline