Bug 155731 - KDE 4.0 crashes during splashscreen
Summary: KDE 4.0 crashes during splashscreen
Status: RESOLVED NOT A BUG
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-14 10:57 UTC by Mikko Piippo
Modified: 2008-01-16 15:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mikko Piippo 2008-01-14 10:57:12 UTC 
Version:            (using KDE KDE 4.0.0)
Installed from:    Ubuntu Packages
OS:                Linux

I'm using fresh install of Kubuntu 7.10 + KDE 4.0.0 from
deb http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu gutsy main and all possible updates:

KDE 4.0 fails to start, splashscreen is shown, but after some flashs I get back to KDM. No problems whatsoever with KDE 3.5.8.

I'm using Asus A7v8-MX SE -mobo + 768 MB with VIA KM400. I have reported this also as Bug #182599 for Ubuntu (https://bugs.launchpad.net/ubuntu/+source/meta-kde4/+bug/182599).

From /var/log/apport.log:

apport (pid 6094) Sun Jan 13 17:39:31 2008: called for pid 5983, signal 6
apport (pid 6094) Sun Jan 13 17:39:31 2008: executable: /usr/bin/Xorg (command line "/usr/bin/X -br -nolisten tcp :0 vt7 -auth /var/run/xauth/A:0-Jra47O")
apport (pid 6099) Sun Jan 13 17:39:32 2008: called for pid 6082, signal 11
apport (pid 6099) Sun Jan 13 17:39:32 2008: executable: /usr/lib/kde4/lib/kde4/libexec/klauncher (command line "klauncher")
apport (pid 6099) Sun Jan 13 17:39:32 2008: apport: report /var/crash/_usr_lib_kde4_lib_kde4_libexec_klauncher.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS

/var/log/messages

Jan 13 17:39:13 kubuntu kernel: [ 2134.756000] agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
Jan 13 17:39:13 kubuntu kernel: [ 2134.756000] agpgart: Device is in legacy mode, falling back to 2.x
Jan 13 17:39:13 kubuntu kernel: [ 2134.756000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
Jan 13 17:39:13 kubuntu kernel: [ 2134.756000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
Jan 13 17:39:32 kubuntu kernel: [ 2153.344000] agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
Jan 13 17:39:32 kubuntu kernel: [ 2153.344000] agpgart: Device is in legacy mode, falling back to 2.x
Jan 13 17:39:32 kubuntu kernel: [ 2153.344000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
Jan 13 17:39:32 kubuntu kernel: [ 2153.344000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode

/var/log/daemon.log

Jan 13 17:39:13 kubuntu kdm[4881]: X server for display :0 terminated unexpectedly
Jan 13 17:39:31 kubuntu kdm[4881]: X server for display :0 terminated unexpectedly
Jan 13 17:39:55 kubuntu NetworkManager: <info> Updating allowed wireless network lists.
Jan 13 17:39:55 kubuntu NetworkManager: <WARN> nm_dbus_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - org.freedesktop.NetworkManagerInfo.NoNetworks.

/var/log/syslog

Jan 13 17:39:13 kubuntu kdm[4881]: X server for display :0 terminated unexpectedly
Jan 13 17:39:13 kubuntu kernel: [ 2134.756000] agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
Jan 13 17:39:13 kubuntu kernel: [ 2134.756000] agpgart: Device is in legacy mode, falling back to 2.x
Jan 13 17:39:13 kubuntu kernel: [ 2134.756000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
Jan 13 17:39:13 kubuntu kernel: [ 2134.756000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
Jan 13 17:39:31 kubuntu kdm[4881]: X server for display :0 terminated unexpectedly
Jan 13 17:39:32 kubuntu kernel: [ 2153.344000] agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
Jan 13 17:39:32 kubuntu kernel: [ 2153.344000] agpgart: Device is in legacy mode, falling back to 2.x
Jan 13 17:39:32 kubuntu kernel: [ 2153.344000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
Jan 13 17:39:32 kubuntu kernel: [ 2153.344000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
Jan 13 17:39:55 kubuntu NetworkManager: <info> Updating allowed wireless network lists.
Jan 13 17:39:55 kubuntu NetworkManager: <WARN> nm_dbus_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - org.freedesktop.NetworkManagerInfo.NoNetworks.

To post a comment you must log in.
Comment 1 Mikko Piippo 2008-01-15 09:09:33 UTC 
.xsession-errors after a new try:
---------------------------------------------------------------------
Xsession: X session started for mjp at ti 15.1.2008 10:05:49 +0200
startkde: Starting up...
startkde: kpersonalizer not found! Please install to properly configure your use                              r.
kbuildsycoca running...
*** attempt to put segment in horiz list twice
kbuildsycoca running...
Reusing existing ksycoca
Ignored duplicate item: Kontact
Ignored duplicate item: KDE Groupwaren ohjattu toiminto
Ignored duplicate item: KArm
Ignored duplicate item: KDE Groupwaren ohjattu toiminto
Ignored duplicate item: KNotes
Ignored duplicate item: Strigi
kdecore (KProcess): WARNING: _attachPty() 14
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x80dbe08 ): KAccel                               object already contains an action name "file_quit"
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x80dbe08 ): KAccel                               object already contains an action name "file_quit"
kdecore (KProcess): WARNING: _attachPty() 11
No battery found.
This is not a laptop, quitting ...
Comment 2 Lubos Lunak 2008-01-16 14:21:04 UTC 
"Jan 13 17:39:13 kubuntu kdm[4881]: X server for display :0 terminated unexpectedly" - X server crashed, not KDE.
Comment 3 Mikko Piippo 2008-01-16 15:13:31 UTC 
Ok, somehow X server crashes only with KDE4, not with KDE3...