KDEMOD completely messed up

speng · 2009-02-19 00:11:18

So I was changing from GNOME to KDEMOD, I setup everything, had a great setup going, did a pacman -Syu which wanted to change qtmod with qt and some libraries, I just accepted. I also removed some GNOME packages before that. I reinstalled qtmod but I am still getting the error.

As soon as I log in, Plasma crashes and it gets completely screwed up (SIGABRT 6) or something similar. I have no idea what to do now. Reinstalled KDEMod. Also, I found that in the start menu, there are no apps at all. There are sections , but nothing in them. I can run programs with the terminal in KDE.

Last edited by speng (2009-02-19 00:17:38)

djnm · 2009-02-19 00:26:57

Did you follow these: http://chakra-project.org/download-kdemod.html instructions?

speng · 2009-02-19 00:40:46

Yes ofcourse, I also just got rid of KDEmod and installed the minimal version and logged in as failsafe and plasma is still going absolutely crazy. I just need a way of starting KDE with a clean slate....

FrozenFox · 2009-02-19 00:44:01

Do you have apps when you log in as a different user?

1LordAnubis · 2009-02-19 00:45:02

what kind of graphics card do you have?

... kdemod crashed for me until i removed

Option "BackingStore" "True"

from my xorg.conf. (nvidia with the 173 driver)

speng · 2009-02-19 00:48:44

I didn't have that line. I am going to try and make a new user just to see if the menus work.

This is the strangest problem I have ever had, it's also hurting my eyes.

Edit: Nope! Doesn't work on a new user either. Oh dear oh dear...

Last edited by speng (2009-02-19 00:55:47)

FrozenFox · 2009-02-19 00:58:39

Hrmm. Couple more things to try out. In xorg, disable the glx module, disable composite, and set the driver to vesa or something of the sort and comment out everything that looks like some special option for the driver that is unnecessary. Also be sure hal and fam are installed and running / added to the daemons list, then try logging in and see if you have any better luck. If that doesn't work, I'm out of ideas ;P

Last edited by FrozenFox (2009-02-19 00:59:37)

speng · 2009-02-19 01:02:43

Nope, didn't do anything. Thanks for trying.

I really don't have the time to do a full re-install, any other ideas?

mcmillan · 2009-02-19 02:53:50

There was an update today to kdelibs and kdebase-workspace that was making plasma really unstable, but seems to be working with the previous versions. I'll be investigating a little more tonight, but if nothing else I could try getting you the older packages to see if they're any better behaved.

Edit: Should have mentioned in my offer for older packages, I'm running a 64bit system. Looks like it's the kdelibs that's responsible on my end. I posted a bug report here. By the way, in the future problems with kdemod should probably go on their forums, not the Arch ones

Last edited by mcmillan (2009-02-19 03:59:35)

speng · 2009-02-19 04:48:47

mcmillan wrote:

There was an update today to kdelibs and kdebase-workspace that was making plasma really unstable, but seems to be working with the previous versions. I'll be investigating a little more tonight, but if nothing else I could try getting you the older packages to see if they're any better behaved.
Edit: Should have mentioned in my offer for older packages, I'm running a 64bit system. Looks like it's the kdelibs that's responsible on my end. I posted a bug report here. By the way, in the future problems with kdemod should probably go on their forums, not the Arch ones

Sorry didn't realise, I'm quite new to all this.
I've installed KDE 4.2 for now but I have kept KDEMOD in my cache so I can try it again later and hopefully get it to work.

Mikko777 · 2009-02-19 12:15:07

speng wrote:

I reinstalled qtmod but I am still getting the error.

You are supposed to use QT from arch repos, not qtmod.
If hal and fam are loaded and you have tried to delete settings (rm -r ~/.kde4). Then its either hardware or packaging issue

speng · 2009-02-19 14:39:50

Mikko777 wrote:

speng wrote:
I reinstalled qtmod but I am still getting the error.
You are supposed to use QT from arch repos, not qtmod.
If hal and fam are loaded and you have tried to delete settings (rm -r ~/.kde4). Then its either hardware or packaging issue

Hmm, I think it's a packaging issue! I followed the instructions on the site which were condescending , but when I did pacman -S kdemod it actually replaced qt with qtmod.

mcmillan · 2009-02-19 16:01:50

speng wrote:

Hmm, I think it's a packaging issue! I followed the instructions on the site which were condescending , but when I did pacman -S kdemod it actually replaced qt with qtmod.

It sounds more like you might have outdated packages. A few versions back they switched for using qtmod to the regular qt package. What mirror are you using to get the kdemod packages from? And can you post what version you have for kdemod-kdebase

Skripka · 2009-02-19 16:33:21

Well,

I just did a virgin Arch and kdemod-complete install-Arch via HTTP, last night. Symptoms being the Plasma crashes and restarts every 15 seconds or so, wallpaper now changes every cycle too, System prefs has all the entries there in kdemod-but all the entries are blank when you click on them. Also Appearance dialog does not respond, and is lacking options.

For argument, reformatted and installed this morning ...installed kdemod-complete and problem persists.

Qtmod was installed as a depend off of kdemod-complete, IIRC.

Last edited by Skripka (2009-02-19 16:35:02)

Janax · 2009-02-19 17:27:36

You may want to follow this thread: kdelibs & kdebase: 4.2.0-6 upgrade breaks KDE. I've regressed to the 4.2.0-5 versions and everything is working fine other than the kopete memory leak I mentioned...

Skripka · 2009-02-19 18:03:30

Janax wrote:

You may want to follow this thread: kdelibs & kdebase: 4.2.0-6 upgrade breaks KDE. I've regressed to the 4.2.0-5 versions and everything is working fine other than the kopete memory leak I mentioned...

Wowza...that might just save the day ...someone was even kind enough to post linkies to older versions still on the Chakra servers.

moonfish · 2009-02-19 21:41:17

New KDEmod packages that fix the problem are out. Now everything is fine again.

Arch Linux

#1 2009-02-19 00:11:18

KDEMOD completely messed up

#2 2009-02-19 00:26:57

Re: KDEMOD completely messed up

#3 2009-02-19 00:40:46

Re: KDEMOD completely messed up

#4 2009-02-19 00:44:01

Re: KDEMOD completely messed up

#5 2009-02-19 00:45:02

Re: KDEMOD completely messed up

#6 2009-02-19 00:48:44

Re: KDEMOD completely messed up

#7 2009-02-19 00:58:39

Re: KDEMOD completely messed up

#8 2009-02-19 01:02:43

Re: KDEMOD completely messed up

#9 2009-02-19 02:53:50

Re: KDEMOD completely messed up

#10 2009-02-19 04:48:47

Re: KDEMOD completely messed up

#11 2009-02-19 12:15:07

Re: KDEMOD completely messed up

#12 2009-02-19 14:39:50

Re: KDEMOD completely messed up

#13 2009-02-19 16:01:50

Re: KDEMOD completely messed up

#14 2009-02-19 16:33:21

Re: KDEMOD completely messed up

#15 2009-02-19 17:27:36

Re: KDEMOD completely messed up

#16 2009-02-19 18:03:30

Re: KDEMOD completely messed up

#17 2009-02-19 21:41:17

Re: KDEMOD completely messed up

Board footer