You are not logged in.

#1 2010-08-01 10:08:53

papierschiff
Member
Registered: 2008-07-09
Posts: 66

kde freeze after login.

hej,
i bought a new notebook (thinkpad x100e) and wanted to leave my mac behind me. but kde doesn't work for me.
i made a new archlinux installation, all was fine. when kdm starts and ~5seconds after i push enter to login, the system freeze. i must reset the system sad
the strange thing is: when i am fast ans switch to a virtual console via strg+alt+F1 after i pushed enter, i can hear the "kde started-sound", but when i will go back i see only an empty desktop and a mousepointer.

i have no problems with xfce.

have anybody an idea? i don't want back to ubuntu / osx.


greats, papierschiff

Offline

#2 2010-08-01 12:48:19

papierschiff
Member
Registered: 2008-07-09
Posts: 66

Re: kde freeze after login.

when i don't start hal and dbus it works. of cure i get the "Error when starting KDE: Cannot open ConsoleKit session"-error (archlinux-wiki, kde)

so how can i get it to work right?

Offline

#3 2010-08-01 12:58:43

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: kde freeze after login.

Do you have

exec ck-launch-session startkde

in your ~/.xinitrc?

Offline

#4 2010-08-01 13:01:53

Vamp898
Member
From: 東京
Registered: 2009-01-03
Posts: 909
Website

Re: kde freeze after login.

Please post your /etc/rc.conf and look if something is in /var/log/messages.log

Offline

#5 2010-08-01 13:45:19

papierschiff
Member
Registered: 2008-07-09
Posts: 66

Re: kde freeze after login.

hej, thanks for your replys.
@karol: ähm.. no. but i tried it and nothing changed sad

@vamp898: i can't find something in the mesages.log.
my rc.conf

LOCALE="en_US.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Berlin"
KEYMAP="de"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

MOD_AUTOLOAD="yes"
MODULES=(powernow-k8 ac battery button fan thermal)

USELVM="no"
HOSTNAME="myhost"
eth0="dhcp"
INTERFACES=(eth0)


gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
NETWORK_PERSIST="no"

DAEMONS=(syslog-ng !dbus !hal network netfs crond @alsa kdm)

Offline

#6 2010-08-01 14:51:22

count-corrupt
Member
From: Germany
Registered: 2009-02-01
Posts: 112

Re: kde freeze after login.

I have similar problems on my X200s with KDEmod. The system hangs if I try to start the Plasma Desktop. The Netbook interface works though, so I never investigated the issue.

Edit: typo.

Last edited by count-corrupt (2010-08-01 14:52:03)

Offline

#7 2010-08-01 14:54:12

papierschiff
Member
Registered: 2008-07-09
Posts: 66

Re: kde freeze after login.

hm, perhaps it is a thinkpad problem? (of the "newer" thinkpads... becouse with my x60 i had no problems..)

Offline

#8 2010-08-01 16:01:13

Doehni
Member
From: Germany
Registered: 2007-05-19
Posts: 175

Re: kde freeze after login.

Do you guys have Windows effects enabled? On my machine (7 years old...with ATI graphics card) the KWin effects make KDE hang.

Offline

#9 2010-08-01 18:16:42

count-corrupt
Member
From: Germany
Registered: 2009-02-01
Posts: 112

Re: kde freeze after login.

papierschiff wrote:

hm, perhaps it is a thinkpad problem? (of the "newer" thinkpads... becouse with my x60 i had no problems..)

Nah, mine's just crashing, not freezing. But I don't really mind. I'm quite satisfied with the netbook Interface, should I really need to use KDE. It comes way closer to XMoad, which I use 99% of the time.

Doehni wrote:

Do you guys have Windows effects enabled? On my machine (7 years old...with ATI graphics card) the KWin effects make KDE hang.

My system crashes independently of Desktop Effects settings.

Application: Plasma Workspace (plasma-desktop), signal: Aborted
[KCrash Handler]
#5  0x00007f120fe78565 in raise () from /lib/libc.so.6
#6  0x00007f120fe799e6 in abort () from /lib/libc.so.6
#7  0x00007f1202751775 in _dbus_abort () from /usr/lib/libdbus-1.so.3
#8  0x00007f120274d67a in _dbus_warn_check_failed () from /usr/lib/libdbus-1.so.3
#9  0x00007f1202742289 in dbus_message_new_method_call () from /usr/lib/libdbus-1.so.3
#10 0x00007f120cb1ef7c in ?? () from /usr/lib/libQtDBus.so.4
#11 0x00007f120cb175e4 in ?? () from /usr/lib/libQtDBus.so.4
#12 0x00007f120cb183bc in ?? () from /usr/lib/libQtDBus.so.4
#13 0x00007f120cb27fe3 in ?? () from /usr/lib/libQtDBus.so.4
#14 0x00007f120cb28129 in QDBusInterface::QDBusInterface(QString const&, QString const&, QString const&, QDBusConnection const&, QObject*) () from /usr/lib/libQtDBus.so.4
#15 0x00007f11f13acdbd in RemoteActivatableList::init() () from /usr/lib/libknmclient.so.4
#16 0x00007f11f15cb05a in ?? () from /usr/lib/kde4/plasma_applet_networkmanagement.so
#17 0x00007f120fa90a52 in Plasma::Corona::loadLayout(QString const&) () from /usr/lib/libplasma.so.3
#18 0x00007f120fa91492 in Plasma::Corona::initializeLayout(QString const&) () from /usr/lib/libplasma.so.3
#19 0x00007f12101ee727 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#20 0x00007f12101eea18 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#21 0x00007f12101f09ef in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#22 0x00007f120c7eedef in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#23 0x00007f120c7f3def in ?? () from /usr/lib/libQtCore.so.4
#24 0x00007f120c7ec3ae in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#25 0x00007f120cf29ae4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#26 0x00007f120cf2dbca in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#27 0x00007f120e0750e6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#28 0x00007f120c7dad8c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#29 0x00007f120c806222 in ?? () from /usr/lib/libQtCore.so.4
#30 0x00007f120c8031d4 in ?? () from /usr/lib/libQtCore.so.4
#31 0x00007f12066a1b33 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0x00007f12066a2310 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#33 0x00007f12066a25ad in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0x00007f120c80387f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#35 0x00007f120cfc960e in ?? () from /usr/lib/libQtGui.so.4
#36 0x00007f120c7da172 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#37 0x00007f120c7da3ac in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#38 0x00007f120c7de7bb in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#39 0x00007f12101dbc2d in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#40 0x00007f120fe64c4d in __libc_start_main () from /lib/libc.so.6
#41 0x0000000000400629 in _start ()

Not very informative...

Last edited by count-corrupt (2010-08-01 18:17:25)

Offline

#10 2010-08-01 20:17:54

Vamp898
Member
From: 東京
Registered: 2009-01-03
Posts: 909
Website

Re: kde freeze after login.

you neither run dbus nor hal and wonder why Qt spits out dbus errors?

#7  0x00007f1202751775 in _dbus_abort () from /usr/lib/libdbus-1.so.3
#8  0x00007f120274d67a in _dbus_warn_check_failed () from /usr/lib/libdbus-1.so.3
#9  0x00007f1202742289 in dbus_message_new_method_call () from /usr/lib/libdbus-1.so.3
#10 0x00007f120cb1ef7c in ?? () from /usr/lib/libQtDBus.so.4
#11 0x00007f120cb175e4 in ?? () from /usr/lib/libQtDBus.so.4
#12 0x00007f120cb183bc in ?? () from /usr/lib/libQtDBus.so.4
#13 0x00007f120cb27fe3 in ?? () from /usr/lib/libQtDBus.so.4
#14 0x00007f120cb28129 in QDBusInterface::QDBusInterface(QString const&, QString const&, QString const&, QDBusConnection const&, QObject*) () from /usr/lib/libQtDBus.so.4

if you dont like dbus/hal dont run KDE becease it needs both (right now).

DBus maybe forever and HAL for 4.4 (afaik 4.5 too)

//EDIT: sorry i mixed up the threatds but @papiershiff you really have to run dbus and hal. I dont know where you heard it works without but it wont... really... it wont... you profed it by yourself

Last edited by Vamp898 (2010-08-01 20:19:37)

Offline

#11 2010-08-01 20:24:26

papierschiff
Member
Registered: 2008-07-09
Posts: 66

Re: kde freeze after login.

@Vamp898
i know that i need dbus and hal, and i have no problem with it. my problem is, that if i want to login and hal and dbus is started kde freece. when i stop both deamons kde runs (with many, many other problems... but i can login and start most programms...)

thats why i am here. i want kde with hal and dbus. and i don't know why it doesn't work. sad

Offline

#12 2010-08-01 20:52:19

papierschiff
Member
Registered: 2008-07-09
Posts: 66

Re: kde freeze after login.

ah... i forgot: disabling 3d changes nothing.

my kdm.log of an freeze:

(==) Log file: "/var/log/Xorg.0.log", Time: Sun Aug  1 22:29:17 2010
(==) Using config directory: "/etc/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.

this is all

last lines in /var/log/messages.log:

Aug  1 22:27:40 myhost kernel: r8169 0000:02:00.0: eth0: link up
Aug  1 22:27:40 myhost dhcpcd[1445]: version 5.2.5 starting
Aug  1 22:27:41 myhost dhcpcd[1445]: eth0: rebinding lease of 192.168.0.101
Aug  1 22:27:41 myhost dhcpcd[1445]: eth0: acknowledged 192.168.0.101 from 192.168.0.1
Aug  1 22:27:41 myhost dhcpcd[1445]: eth0: checking for 192.168.0.101
Aug  1 22:27:41 myhost kernel: Clocksource tsc unstable (delta = -192924494 ns)
Aug  1 22:27:40 myhost init: Entering runlevel: 3
Aug  1 22:27:43 myhost kernel: IBM TrackPoint firmware: 0x0e, buttons: 3/3
Aug  1 22:27:44 myhost kernel: input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio4/serio5/input/input9
Aug  1 22:27:46 myhost dhcpcd[1445]: eth0: leased 192.168.0.101 for 86400 seconds
Aug  1 22:27:46 myhost dhcpcd[1445]: forked to background, child pid 1474
Aug  1 22:27:48 myhost rpc.statd[1540]: Version 1.2.2 starting
Aug  1 22:27:48 myhost sm-notify[1541]: Version 1.2.2 starting
Aug  1 22:27:48 myhost kernel: NET: Registered protocol family 10
Aug  1 22:27:48 myhost kernel: lo: Disabled Privacy Extensions
Aug  1 22:27:48 myhost rpc.statd[1540]: Running as root.  chown /var/lib/nfs to choose different user
Aug  1 22:27:48 myhost sm-notify[1550]: Version 1.2.2 starting
Aug  1 22:27:48 myhost sm-notify[1550]: Already notifying clients; Exiting!

where could be other important kde/kdm-logs? .xsession-errors is empty (after an freeze)

Offline

Board footer

Powered by FluxBB