|
»
»
« Return to Thread: X gets killed immediately after successful graphical logon
Re: X gets killed immediately after successful graphical logon
by Kent West
::
Rate this Message:
Uwe Dippel wrote:
> It seems my install simply fails me completely now. I had to do some
> repair when booting a few days back, then it worked and now the repair
> tends to come up at boot, again.
> But even if it doesn't, it is not okay. Unfortunately, all messages
> flash by too quickly, and don't show in dmesg neither.
> But there is always something like /dev/shm not found, some
> udevdevdevsdev-message, the wireless is recognized, but fails latrer
> during boot, and now apt-get also shows some weird messages.
>
If you'll disable any login managers you have (one method would be to
edit /etc/init.d/[k|g|w|x]dm for example, and make "exit 0" the first
executable line in that script), then you'll be able to Shift-PgUp
through all the boot-up messages after logging in, even the ones not
shown by dmesg (as long as you don't switch to another VT, that is).
> That means, I better forget the whole thing and install, again, after
> some 3 years?
>
I would only wipe/reinstall if you suspect a security compromise, or
just think it'd take less time than repairing. Repairing is usually the
better route.
> But I'd still like to save/backup as much as possible.
> The following script shows some of the misery:
>
> % apt-get upgrade
> Reading package lists... Done
> Building dependency tree... Done
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> 10 not fully installed or removed.
> Need to get 0B of archives.
> After unpacking 0B of additional disk space will be used.
> Do you want to continue [Y/n]? y
> Setting up linux-image-2.6.18-6-686 (2.6.18.dfsg.1-18etch4) ...
> Running depmod.
> Finding valid ramdisk creators.
> Using mkinitramfs-kpkg to build the ramdisk.
> /usr/sbin/mkinitramfs-kpkg: line 35: /usr/bin/touch: Permission denied
> mkinitramfs-kpkg failed to create initrd image.
> Failed to create initrd image.
> dpkg: error processing linux-image-2.6.18-6-686 (--configure):
> subprocess post-installation script returned error exit status 9
> Setting up libxul0d (1.8.0.15~pre080323b-0etch2) ...
> /var/lib/dpkg/info/libxul0d.postinst: line 6: /usr/bin/touch: Permission denied
>
You're doing this as root, right?
Try touching a file (e.g., "touch myfile"); does it create, or update
the timestamp on, the file? Also try "/usr/bin/touch myfile" to make
sure you don't have a path issue.
Does "/usr/sbin/mkinitramfs-kpgk" exist? What are the perms on the file?
Is the volume on which that file sits mounted read/write?
--
Kent West
http://kentwest.blogspot.com
--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...
> It seems my install simply fails me completely now. I had to do some
> repair when booting a few days back, then it worked and now the repair
> tends to come up at boot, again.
> But even if it doesn't, it is not okay. Unfortunately, all messages
> flash by too quickly, and don't show in dmesg neither.
> But there is always something like /dev/shm not found, some
> udevdevdevsdev-message, the wireless is recognized, but fails latrer
> during boot, and now apt-get also shows some weird messages.
>
If you'll disable any login managers you have (one method would be to
edit /etc/init.d/[k|g|w|x]dm for example, and make "exit 0" the first
executable line in that script), then you'll be able to Shift-PgUp
through all the boot-up messages after logging in, even the ones not
shown by dmesg (as long as you don't switch to another VT, that is).
> That means, I better forget the whole thing and install, again, after
> some 3 years?
>
I would only wipe/reinstall if you suspect a security compromise, or
just think it'd take less time than repairing. Repairing is usually the
better route.
> But I'd still like to save/backup as much as possible.
> The following script shows some of the misery:
>
> % apt-get upgrade
> Reading package lists... Done
> Building dependency tree... Done
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> 10 not fully installed or removed.
> Need to get 0B of archives.
> After unpacking 0B of additional disk space will be used.
> Do you want to continue [Y/n]? y
> Setting up linux-image-2.6.18-6-686 (2.6.18.dfsg.1-18etch4) ...
> Running depmod.
> Finding valid ramdisk creators.
> Using mkinitramfs-kpkg to build the ramdisk.
> /usr/sbin/mkinitramfs-kpkg: line 35: /usr/bin/touch: Permission denied
> mkinitramfs-kpkg failed to create initrd image.
> Failed to create initrd image.
> dpkg: error processing linux-image-2.6.18-6-686 (--configure):
> subprocess post-installation script returned error exit status 9
> Setting up libxul0d (1.8.0.15~pre080323b-0etch2) ...
> /var/lib/dpkg/info/libxul0d.postinst: line 6: /usr/bin/touch: Permission denied
>
You're doing this as root, right?
Try touching a file (e.g., "touch myfile"); does it create, or update
the timestamp on, the file? Also try "/usr/bin/touch myfile" to make
sure you don't have a path issue.
Does "/usr/sbin/mkinitramfs-kpgk" exist? What are the perms on the file?
Is the volume on which that file sits mounted read/write?
--
Kent West
http://kentwest.blogspot.com
--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...
« Return to Thread: X gets killed immediately after successful graphical logon
| Free Forum Powered by Nabble | Forum Help |