You are not logged in.

#1 2009-07-15 22:50:32

PapaNoa
Member
Registered: 2009-02-19
Posts: 14

Window manager not starting up any more after update (using inittab)

Since the last greater update my window manager is not starting up any more without me having changed the configuration.

I use /etc/inittab to start entrance:

#
# /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 38400 vc/1 linux
c2:2345:respawn:/sbin/agetty -8 38400 vc/2 linux
c3:2345:respawn:/sbin/agetty -8 38400 vc/3 linux
c4:2345:respawn:/sbin/agetty -8 38400 vc/4 linux
c5:2345:respawn:/sbin/agetty -8 38400 vc/5 linux
c6:2345:respawn:/sbin/agetty -8 38400 vc/6 linux

ca::ctrlaltdel:/sbin/shutdown -t3 -r now

# mount the luks encrypted partitions
# crypttab??

# 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
x:5:respawn:/usr/sbin/entranced -nodaemon &> /dev/null

# End of file

What happens is that it boots to vc1 and the following message appears every 5 mins:

Id "x" respawning too fast: disabled for 5 minutes

When I then log in and start entranced from the shell, everything works as usual, it just doesn't come up automatically any more as it did before.

Relevant section from /var/log/daemon.log

Jul 15 21:38:51 flobook ntfs-3g[5417]: Version 2009.4.4 integrated FUSE 27
Jul 15 21:38:51 flobook ntfs-3g[5417]: Mounted /dev/sda1 (Read-Only, label "System", NTFS 3.1)
Jul 15 21:38:51 flobook ntfs-3g[5417]: Cmdline options: ro,noexec,nosuid,nodev,users,uid=1000,gid=100,fmask=0113,dmask=0002
Jul 15 21:38:51 flobook ntfs-3g[5417]: Mount options: ro,noexec,nosuid,nodev,users,silent,allow_other,nonempty,default_permissions,relatime,fsname=/devsda1,blkdev,blksize=4096
Jul 15 21:38:52 flobook ntfs-3g[5422]: Version 2009.4.4 integrated FUSE 27
Jul 15 21:38:52 flobook ntfs-3g[5422]: Mounted /dev/sda5 (Read-Write, label "PROGRAMS", NTFS 3.1)
Jul 15 21:38:52 flobook ntfs-3g[5422]: Cmdline options: rw,nosuid,nodev,users,uid=1000,gid=100,fmask=0113,dmask=0002
Jul 15 21:38:52 flobook ntfs-3g[5422]: Mount options: rw,nosuid,nodev,users,silent,allow_other,nonempty,default_permissions,relatime,fsname=/dev/sda5,blkdev,blksize=4096
Jul 15 21:38:52 flobook ntfs-3g[5426]: Version 2009.4.4 integrated FUSE 27
Jul 15 21:38:52 flobook ntfs-3g[5426]: Mounted /dev/sda6 (Read-Write, label "DATA", NTFS 3.1)
Jul 15 21:38:52 flobook ntfs-3g[5426]: Cmdline options: rw,nosuid,nodev,users,uid=1000,gid=100,fmask=0002,dmask=0002
Jul 15 21:38:52 flobook ntfs-3g[5426]: Mount options: rw,nosuid,nodev,users,silent,allow_other,nonempty,default_permissions,relatime,fsname=/dev/sda6,blkdev,blksize=4096
Jul 15 21:38:56 flobook init: Entering runlevel: 5
Jul 15 21:39:00 flobook ifplugd(eth0)[6521]: ifplugd 0.28 initializing.
Jul 15 21:39:00 flobook ifplugd(eth0)[6521]: Using interface eth0/xx:xx:xx:xx:xx:xx with driver <sky2> (version: 1.22)
Jul 15 21:39:00 flobook ifplugd(eth0)[6521]: Using detection mode: SIOCETHTOOL
Jul 15 21:39:00 flobook ifplugd(eth0)[6521]: Initialization complete, link beat not detected.
Jul 15 21:39:03 flobook init: Id "x" respawning too fast: disabled for 5 minutes
Jul 15 21:39:49 flobook entranced: Starting X server.
Jul 15 21:39:56 flobook entranced: Starting Entrance.
Jul 15 21:40:02 flobook entrance: PAM: Success.
Jul 15 21:40:03 flobook entrance: entranced: Requesting auth for uid 1000 (/home/xxx)
Jul 15 21:40:03 flobook entrance: _entrance_ipc_server_data = E_XAUTH_ACK
Jul 15 21:40:03 flobook entrance: Executing /usr/bin/enlightenment_start
Jul 15 21:40:03 flobook entrance: Starting session for user "xxx".
Jul 15 21:40:03 flobook entrance: Opened PAM session. xxx : :0.
Jul 15 21:40:03 flobook entrance: DEBUG1
Jul 15 21:40:03 flobook entrance: DEBUG2
Jul 15 21:40:03 flobook entrance: DEBUG3
Jul 15 21:40:03 flobook entrance: DEBUG4
Jul 15 21:40:03 flobook entrance: DEBUG5
Jul 15 21:40:03 flobook entrance: DEBUG6
Jul 15 21:40:03 flobook entrance: DEBUG7
Jul 15 21:40:03 flobook entrance: entrance_ipc_shutdown: Success
Jul 15 21:40:03 flobook entrance: DEBUG8
Jul 15 21:40:03 flobook entrance: Replacing Entrance with simple login program to wait for session end.
Jul 15 21:40:33 flobook entrance: Exec entrance login replacement: /usr/lib/entrance/entrance_login 6600 xxx :0
Jul 15 21:40:33 flobook entrance_login[6580]: Wait for xxx on :0
Jul 15 21:40:33 flobook entrance_login[6580]: Wait for pid 6600
Jul 15 21:44:05 flobook init: Id "x" respawning too fast: disabled for 5 minutes
Jul 15 21:49:06 flobook init: Id "x" respawning too fast: disabled for 5 minutes
Jul 15 21:54:07 flobook init: Id "x" respawning too fast: disabled for 5 minutes
... until eternity

I started entranced myself in this log. No problems thereafter. What could be the problem? Any hints appreciated.

Offline

#2 2009-07-18 20:29:40

nocain
Member
From: nowheresvill california
Registered: 2003-05-31
Posts: 62

Re: Window manager not starting up any more after update (using inittab)

the problem is that the -nodaemon option has changed...

change it so it is --nodaemon and it should be fine....

let me know how it goes... I have a problem where when I log out entrance comes back with the screen all scrambled, however I think this is just a problem with some change somewhere in an xorg package or in part of the intel driver, If I kill the entranced process though it comes back fine.

Offline

#3 2009-07-18 20:48:04

deadlylife
Member
Registered: 2008-12-24
Posts: 120

Re: Window manager not starting up any more after update (using inittab)

nocain wrote:

the problem is that the -nodaemon option has changed...

change it so it is --nodaemon and it should be fine....

let me know how it goes... I have a problem where when I log out entrance comes back with the screen all scrambled, however I think this is just a problem with some change somewhere in an xorg package or in part of the intel driver, If I kill the entranced process though it comes back fine.

That happened to me in an Ubuntu alpha, nex thing I knew, X crashed.

Offline

#4 2009-07-18 20:49:53

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,931

Re: Window manager not starting up any more after update (using inittab)

If anyone is having this same problem:

http://bbs.archlinux.org/viewtopic.php?id=76260

Offline

#5 2009-07-18 21:41:38

.:B:.
Forum Fellow
Registered: 2006-11-26
Posts: 5,819

Re: Window manager not starting up any more after update (using inittab)

I suppose, from the above link, that this topic concerns testing? I haven't got any 2009.7 update on my mirror yet...


Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Offline

#6 2009-07-18 22:29:57

nocain
Member
From: nowheresvill california
Registered: 2003-05-31
Posts: 62

Re: Window manager not starting up any more after update (using inittab)

B wrote:

I suppose, from the above link, that this topic concerns testing? I haven't got any 2009.7 update on my mirror yet...

Problem has nothing to do with testing packages I have no packages from testing on my computer that was experiencing this issue... I don't know why this was posted in testing.

The issue poster is talking about  only applies to the entrance desktop manager XDM, GDM, and SLiM all work fine.

Problem with entrance is that entranced no longer uses -nodaemon it is now --nodaemon problem arose last time Entrance was rebuilt around 21-6-2009 Wiki page http://wiki.archlinux.org/index.php/Add … on_startup should probably be updated to reflect the change

the other problem I have is that when I log out of my window manager and it goes back to entrance the screen is jacked up like the wrong resolution or H\V Sync is used. if I log back in with the screen messed up the Window Manager will be fine. and if I kill the entranced process it restarts fine... Oddly enough this does not occur if I use entrance via the daemon method only occurs using the init method.

Offline

Board footer

Powered by FluxBB