You are not logged in.

#1 2012-11-13 11:51:04

cleberaraujo
Member
Registered: 2012-05-22
Posts: 10

Error after upgrade to KDE 4.9.3

Good morning everyone!

Because changing the init to systemd recently reinstalled Arch on my laptop and everything was 100% before the upgrade to KDE 4.9.3.

After installing the pacman finished, I reset the system to validate some settings and Arch no longer starts in graphical environment (KDE does not open automatically or via terminal).

Wondering what could be some problem related to probable loss of service configuration at startup, I tried to recreate the link automatically boot with the command systemctl enable kdm.service, but it returns:

[ 599.543091] systemd-fstab-generator[410]: Failed to create unit file: File exists
The unit files have no [Install] section. They are not meant to be enable using systemctl. 

As he tells the configuration already exists, try deleting it to recreate it but it works the same.

As it reports an error in fstab-generator, follow my fstab in full. Remember that everything worked perfectly with KDE 4.9.2:

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
tmpfs		/tmp	tmpfs	nodev,nosuid	0	0

# Partition SWAP
/dev/sda2		none		swap		defaults	0	0

# UUID=932f0f07-bca8-4295-baa3-7edc0553c08d
/dev/sda3           	/         	ext4      	rw,relatime,data=ordered	0 1

# UUID=5f94131c-f989-422f-9bcb-9b190f685a78
/dev/sda1           	/boot     	ext2      	rw,relatime	0 2

# UUID=4fb544fe-56a5-41c0-adbf-fb9933edee1d
/dev/sda5           	/home     	ext4      	rw,relatime,data=ordered	0 2

# UUID=3d514724-ba93-469d-86d1-cfce5638f225
/dev/sda6           	/tmp      	ext4      	rw,relatime,data=ordered	0 2

# Fix problem USB VirtualBox
none 			/proc/bus/usb	usbfs		auto,busgid=108,busmode=0775,devgid=108,devmode=644	0	0

If it is help with something, look the part of dmesg that represents the error:

[    4.811854] systemd-fstab-generator[141]: Failed to create unit file: File exists
[    4.814481] systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1.
[    5.015843] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.

As he says it can not add to the dependency in display-manager.service, checked his status:

# systemctl status display-manager.service
display-manager.service
     Loaded: error (Reason: No such file or directory)
     Active: inactive (dead)

Another says, it also appears in dmesg. Do not know if that affects the problem:

kvm: disabled by bios
kvm_intel: module is already loaded

Have any of you experienced this too?

How can I fix this?

Already very grateful for the help!

Last edited by cleberaraujo (2012-11-13 12:01:50)

Offline

Board footer

Powered by FluxBB