Summary: | kde-base/kdm-4.2.0 crashes on root login with a segfault | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robert Holzknecht <nightdragon> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | andriy155, egorchel, kshots, reavertm |
Priority: | High | Flags: | tampakrap:
Bugday+
|
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 300393, 313999 |
Description
Robert Holzknecht
2009-02-02 06:49:00 UTC
Here are the segfault from /var/log/messages: --------------------------------------------- kdm[10783]: segfault at 0 ip 08051f26 sp bf8d1ce0 error 4 in kdm[8048000+22000] kdm[10808]: segfault at 0 ip 08051f26 sp bf8d1ce0 error 4 in kdm[8048000+22000] Please try with newest kdm from portage (4.2.4) Unfortunately, the problem still remains with 4.2.4. Hmm, do you happen to have qt-gui emerged with gtkstyle USE flag enabled? Also does this crash happen when you try to log into newly created user account? Czesc Maciej, This only happens for the root account logins (and not only on my machine) and, yes, gtk use flag is enabled. Would you like me to recompile the package without the flag? I will try to do that later in the week - won't be able to do it earlier. Note that root logins work fine when I use kdm from the 3.5 branch. andriy *** Bug 239672 has been marked as a duplicate of this bug. *** I may be wrong, but it may be related to Qt4 Gtk style (Qt4 style using Gtk2 and its plugins for rendering) It may appear when one used gtk-engines-qt (the other way around - Gtk2 style using Qt4 style for rendering) - applications will crash. See bug 250504 You could try the following: - make sure you have export GTK2_RC_FILES=~/.gtkrc-2.0 in ~/.kde4/env/gtk-style.sh (remove any other conflicting files from there) - install >=x11-themes/gtk-chtheme-0.3.1-r2 - choose some Gtk theme (for accounts that kdm crashes with, so for root, you need to run it in any X session that works for you) - relogin, crashes should be gone for that account - if so, run systemsettings and for KDE4 apps set Qt4 style you want (it supposedly crashes because this style is set to Gtk - using qt-gui[gtkstyle] but still having remnants of gtk-engines-qt). Thanks! I will try it on the weekend or early next week and will let you know. Hi and sorry for not replying earlier. This is strange, but I do not seem to have any gtk-style.sh files on my system at all (and in the directory you mentioned in particular). I tried creating one and following the steps but the crashes remain. I am guessing, I need to figure out why I do not have the file in the first place before proceding further. Alas, I was not able to find much online regarding this. It's fine that you don't have such file - as it's just example file where you can set GTK2_RC_FILES for your kde session. The point is - in the same location there could have been either some other similar (remnants of gtk-engines-qt) that combined with Gtk2 Qt style (provided by qt-gui[gtkstyle]) could render your qt4 apps unusable and require manual gtk theme switch (to sth other than gtk theme using qt engine) while having qt theme using gtk engine enabled. At least that was the case of kdm segfaults I encountered. Any feedback? Andriy, if you want attention (like in bug 244720), you need to provide one as well, and report whether issue is still reproducible for you. Besides we all are yet to see any meaningful backtrace attached. (In reply to comment #11) > Any feedback? Andriy, if you want attention (like in bug 244720), you need to > provide one as well, and report whether issue is still reproducible for you. > Besides we all are yet to see any meaningful backtrace attached. > Hi Maciej, Sorry about the delay. Unfortunately, even with the upgrade to the latest kde (and kdm 4.3.0-r1) and gcc 4.4.1 I still run into the issue. I was trying to look for the files you've mentioned but could not find anything. Could you recommend other files where I can look for inconsistencies? With regards to backtrace, I would be happy to provide you with it, but not sure how to do this. The only thing that I can give you so far is the output in dmesg: kdm[14386]: segfault at 0 ip 0805339f sp bfa07df0 error 4 in kdm[8048000+23000] So far, this is not a big issue as I can either use kdm from the 3.5 series or gdm, but it would be great to figure out what is going on. Please let me know what else I can do... Hmm, to get coredumps, you could: 1. Enable core dumps In /etc/profile.d/ create shell script with line 'ulimit -c 65536' (should be big enough for just backtraces) 2. Issue storing core dumps in some common place, for example this way: In /etc/conf.d/local in local_start() add lines: mkdir -p /tmp/core && chmod 1777 /tmp/core echo "/tmp/core/%u:%g-%e.core" > /proc/sys/kernel/core_pattern This will make coredumps created in /tmp/core/ 3. Get kdm + kdelibs built with debug symbols This can be achieved using /etc/portage/env hack. In files /etc/portage/env/kde-base/kdelibs and /etc/portage/env/kde-base/kdm add lines: CFLAGS="-O0 -ggdb" CXXFLAGS="${CFLAGS}" FEATURES="${FEATURES} splitdebug" after that reemerge kdelibs and kdm, /etc/init.d/local restart and relogin (remove those files in /etc/portage/env/kde-base when issue is solved as you don't need them built this way permanently I suppose) Any news on this? Situation with 4.3.5 or 4.4.1? I couldn't reproduce with 4.4.2, you could try also, so I'm marking this as fixed for 4.4.2. If the problem persists for you, attach the backtrace here and please open an upstream bug with the backtrace and paste the link here (comment 13 has the info you want for this). Feel fre to reopen. Thanks Same problem here, with kdm-4.4.4-r1. Not currently in a position to do a backtrace, but it's apparently still an issue. |