Bug 124460

Created attachment 15346 [details]
A screenshot of the problem

This is how all is happening:

from my ~/.xsession-errors

***MEMORY-ERROR***: [2688]: GSlice: failed to allocate 248 bytes (alignment:
256): Invalid argument

DCOP aborting (delayed) call from 'anonymous-2687' to 'kdesktop'
ERROR: Communication problem with kdesktop, it probably crashed.

For the record, fc5 has glib2-2.10.1, and should be fine.  Did you build arts against and older version (from a fc5 test release perhaps?)

Right now I am not sure what is wrong with KDE but this error persists even for the newly created user (i.e. /home/$USER is totally empty).

I've tried running startkde line by line manuall in a safemode and then I found out that this very line

kwrapper ksmserver $KDEWM 

causes this output:

------------

Warning: connect() failed: : No such file or directory
DCOPClient::attachInternal. Attach failed Could not open network socket
kbuildsycoca running...

***MEMORY-ERROR***: [4808]: GSlice: failed to allocate 248 bytes (alignment: 256): Invalid argument

DCOP aborting (delayed) call from 'anonymous-4807' to 'kdesktop'
ERROR: Communication problem with kdesktop, it probably crashed.

------------

This is happenening with a newly compiled KDE 3.5.2 with FC5 devel packages. I'm absolutely stuck.

I have resolved this bug by adding to my /etc/profile.d/glib2.sh file (If you don't have this file you may add this line to startkde or /etc/profile files) this line:

export G_SLICE=always-malloc

Feel free to close this bug, 'cause I do not understand what's going on in my case - I don't even understand why kdesktop fails to start and what application 'causes this misbehavior.

artsd_pid in the first message:

***MEMORY-ERROR***: [artsd_pid]: GSlice: failed to allocate 248 bytes (alignment: 
256): Invalid argument

was actually my guess - I think it's another application which PID is shown.

Looks like a glib2 bug

It might be a bug in glib2 but nonetheless Fedora Core's 5 KDE 3.5.1 works flawlessly and my own build doesn't. I tried finding any glib2 related patches in the FC5 source tree with no success.

I use vanilla KDE 3.5.2/Qt 3.3.6/GCC 4.1.0 and simple compilation flags like "-O2 -march=i686" - that's all. Maybe this bug is somehow related to extra packages which I install for KDE like: id3lib, lame, libdvdcss, libdvdnav, libdvdplay, libdvdread, libid3tag, libmad, libtunepimp, taglib, xine, xvidcore.

The final note: with glib2 2.8.6 everything works fine.

Well, kde-redhat's kde-3.5.2 pkgs WORKFORME on fc5 too.  FYI, redhat/fedora arts contains a minor glib patch, and is built with CFLAGS:
-O2 -g -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables

Either way, kde's bugzilla is not the place for this.  If you wish further discussion, I'd suggest taking it to one of the kde mailing lists, like kde-linux:
http://mail.kde.org/mailman/listinfo/kde-linux

I have upgraded to FC6 and the bug appeared again. Now even kdesktop cannot start.

I had to add `export G_SLICE=always-malloc` into my ~/.bash_profile to get KDE working.

Yeah, but fc6 doesn't have glib2-2.10.1, but glib2-2.12.3.  

Besides, there's a multitude of FC6 kde users, and I haven't seen or heard even a whisper about this problem there (until now).

Regardless, if this is indeed a glib2 bug, bugs.kde.org is no place for it, imo.

Almost no FC user uses selfcompiled KDE as I do and the problem persists.

It's not a glib2 bug because all other applications which depend on it work flawlessly.

Yes, I have a different version of glib2 now, that is: glib2-2.12.3-2.fc6

If you have no intentions to resolve this bug, I will not ever touch it again. This clearly shows that Open Source developers work for themselves.


Arivederchi

Shame on you:

http://bugs.kde.org/show_bug.cgi?id=125740

http://foo-projects.org/pipermail/lunar-dev/2006-May/005754.html

It's a duplicate noone wants to care about.

*** This bug has been marked as a duplicate of 125740 ***