You are not logged in.
You might want to recompile some local packages (if you have any) which depend on KDE libs.
:: / my web presence
Offline
ICERAM: sorry i don't get it, what do you mean?
Offline
Sorry, it seems I was a bit unclear.
I meant that, if you have some locally compiled KDE packages (in /var/abs/local for example) such as KDE window decorations or styles, you might need to recompile them in order to use them without a problem. Or, there might be some other application invoked by KDE which needs recompilation on that system.
It could be similar to the kernel26 and nvidia situation. You need to reinstall nvidia after you upgrade the kernel (well, not actually recompile). Maybe this isn't a very good example.
Anyway.. if the libs change, some incompatibilities may rise with the apps depending on them, so the apps must be recompiled.
Of course, I may be totally wrong about this precise problem... but... those are my 2c.
:: / my web presence
Offline
ah ok, well it's the .1 release so i guess bugfixes were the most things, all old stuff should run.
Most problems arise when major number grows, not minor numbers.
Offline
It doesn't seem to be a bug limited to 3.4.1 only (I've discovered it in 3.4 recently), but it seems limits enforced by pam_limits don't work when relogging via kdm (they work just after autologging, though). Anyone got the same behaviour and/or any clues about that?
Moreover, tpowa, I guess you could remove 'system-auth' options and pam_console line from /etc/pam.d/kde-np. Both seem to be obsolete, at least in Arch ;-)
Offline
I have installed KDE 3.4.1 yesterday and it went without a problem, good work!
Today I updated qt from 3.3.4-7 to 3.3.4-8. After that kwin consistently crashed after a KDE start (SIGSEGV). I went back to 3.3.4-7 and everything is OK.
Anybody else having this problem?
--
Harald
Offline
Yes! KDE started misbehaving after updating my notebook today. I kept getting a message that Kwin was crashing and things would just hang. I will acknowledge to anyone else who has this problem that backtracking to qt 3.3.4-7 appears to fix things.
Bob Pisciotta
"You're only young once, but you can always be immature."
Offline
Downgrading QT fixed this for me too. Haven't gotten to dig into it any more than that though. Late. Need sleep.
Offline
...as above, I am getting the kwin crash. The funny thing is that I have 2 computers almost identical (processor speed only) and one does not have the problem and the other does. Spooky. I have not tried reverting to the old qt, but I do not have problems if I log out and then in again after a reboot. Some others might want to try that if they need the new qt for some reason.
Offline
i don't have the problem, but all of you with problems, could you try to rebuild kdelibs against this new qt release? we only changed one patch in qt. Hope that helps
Offline
I'll give that a shot. I'll ssh in after I get to work. I also have tightvnc so I can see if it fixes the issue.
Offline
Hmm.. my KSysGuard applet stopped working... and I haven't upgraded in a few days... or.. have I?
Anyway, I'm also getting a crash BUT when I log off - it looks like Kicker. It's probably because I have lots of applets (screenshot).
:: / my web presence
Offline
Well, I built kdelibs against the new QT release and it fixed my problem. However I have no way to really test it because I only had the problem on one of my boxes. And yes, the boxes are almost identical. I can make a link to download the package if anybody's interested...but like I said, I really have no way to test it.
Offline
Well, I for one would be interested in the package. Bob
"You're only young once, but you can always be immature."
Offline
Actually, turns out it must not have fixed it. I rebooted a few times and....well, now it's inconsistant. Sometimes Kwin crashes on first login after bootup, sometimes it doesn't... :?
Offline
hm you guys with problems do you run any special extension with kde?
did you try and fresh user?
could you please try to debug kwin, it's really hard for me to guess where the error comes from.
Do you run packages from testing?
Please check your RAM with memtest etc.
thanks
greetings tpowa
Offline
Hmmm...I don't run any special extensions..
Have not tried a fresh user but will...
I don't run any packages at all from testing.
I tested my RAM a couple of weeks ago and all good..
Offline
PLEASE TEST such stuff with a test user!
if it happens there too then start posting such stuff. else your user is just misconfigured somewhere and i can't guess where.
Offline
Yep. Happened with a brand new user. Went through the KDE configuration wizard and didn't change anything. Accepted all defaults. Kwin crashed. I have to run right now, but I'll dig through some log files when I get a chance and let you know if I find anything.
Offline
Hmm... the ksysguard panels are back (KDE didn't ask me for entering connection settings for KSysGuard). I just restored the config file from a backup.. and it was working again.
I haven't figured it out yet why kicker crashes on exit. Actually... I'm not sure I've seen it crash lately. It was probably because of the ksysguard applet.
Other than that, my KDE runs perfectly.
:: / my web presence
Offline
kicker crashes on exit.
kicker crashes on my System, too. i go back to kde 3.4.
[14:52] [sven@linux ~]$ dmesg
Jabber-ID: sven-schaefer@jabber.ccc.de
Offline
kwin crashes with a freshly created test user, too.
I have debug info but cannot figure out as to how to attach a file to a posting ... submitted in a direct message to tpowa ...
--
Harald
Offline
Just to strengthen: kicker crashes on exit here (=on log off).
:: / my web presence
Offline
so after a long test, i found out what makes kicker crash! it crashes on logout, after you have changed it with KDE Menu Editor.
[14:52] [sven@linux ~]$ dmesg
Jabber-ID: sven-schaefer@jabber.ccc.de
Offline
It might be a KDE bug. They are currently playing with kicker for KDE4 and they probably did some changes for KDE3 branch too.
:: / my web presence
Offline