All KDE programs crash

English Applications
1

Hi,

I got a very, very annoying problem since I’ve booted my pc this morning. It seems as if almost every KDE program crashes when starting it up. Maybe I’m exaggerating a little bit, but this far I’ve got problems with: KDEwallet, Dolphin, Konqueror, kmail, yast and so forth. Didn’t try further because it’s depressing

Last time when I started the laptop, it didn’t have problems at all. Now it’s practically unworkable. I didn’t have problems like this in the past, maybe occasionally a message that a program has crashed, but afterwards i could start it again.

Could someone please help me out? I’ll post some crash reports, if you need other information, let me know.

dolphin

Application: Dolphin (dolphin), signal: Aborted
[KCrash Handler]
#5  0x00007fd74d5119e5 in raise () from /lib64/libc.so.6
#6  0x00007fd74d512ee6 in abort () from /lib64/libc.so.6
#7  0x00007fd74d8fecdd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6
#8  0x00007fd74d8fcef6 in ?? () from /usr/lib64/libstdc++.so.6
#9  0x00007fd74d8fcf23 in std::terminate() () from /usr/lib64/libstdc++.so.6
#10 0x00007fd74d8fd076 in __cxa_rethrow () from /usr/lib64/libstdc++.so.6
#11 0x00007fd74e917563 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#12 0x00007fd74e91b88b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#13 0x0000000000436c3d in _start ()

KDEwallet

Application: KWallet portefeuilledienst (kdeinit4), signal: Aborted
[KCrash Handler]
#5  0x00007ffdfac119e5 in raise () from /lib64/libc.so.6
#6  0x00007ffdfac12ee6 in abort () from /lib64/libc.so.6
#7  0x00007ffdfaffecdd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6
#8  0x00007ffdfaffcef6 in ?? () from /usr/lib64/libstdc++.so.6
#9  0x00007ffdfaffcf23 in std::terminate() () from /usr/lib64/libstdc++.so.6
#10 0x00007ffdfaffd076 in __cxa_rethrow () from /usr/lib64/libstdc++.so.6
#11 0x00007ffdfc234563 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#12 0x00007ffdfc23888b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#13 0x00007ffdef70c202 in kdemain () from /usr/lib64/libkdeinit4_kwalletd.so
#14 0x0000000000407659 in _start ()

Konqueror (maybe important: it only crashes when navigating to a local folder like /home, not when surfing on the web)

Application: Konqueror (kdeinit4), signal: Aborted
[KCrash Handler]
#5  0x00007ffdfac119e5 in raise () from /lib64/libc.so.6
#6  0x00007ffdfac12ee6 in abort () from /lib64/libc.so.6
#7  0x00007ffdfaffecdd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6
#8  0x00007ffdfaffcef6 in ?? () from /usr/lib64/libstdc++.so.6
#9  0x00007ffdfaffcf23 in std::terminate() () from /usr/lib64/libstdc++.so.6
#10 0x00007ffdfaffd076 in __cxa_rethrow () from /usr/lib64/libstdc++.so.6
#11 0x00007ffdfc234563 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#12 0x00007ffdfc23888b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#13 0x00007ffdef6f9e99 in kdemain () from /usr/lib64/libkdeinit4_konqueror.so
#14 0x0000000000407659 in _start ()

Yast

Application: KDE su (kdesu), signal: Aborted
[KCrash Handler]
#5  0x00007f26305699e5 in raise () from /lib64/libc.so.6
#6  0x00007f263056aee6 in abort () from /lib64/libc.so.6
#7  0x00007f2630956cdd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6
#8  0x00007f2630954ef6 in ?? () from /usr/lib64/libstdc++.so.6
#9  0x00007f2630954f23 in std::terminate() () from /usr/lib64/libstdc++.so.6
#10 0x00007f263095502e in __cxa_throw () from /usr/lib64/libstdc++.so.6
#11 0x00007f2630e2d5d2 in qBadAlloc() () from /usr/lib64/libQtCore.so.4
#12 0x00007f2630e378d5 in qUncompress(unsigned char const*, int) () from /usr/lib64/libQtCore.so.4
#13 0x00007f26326a5241 in KPixmapCache::Private::loadData(int, QPixmap&) () from /usr/lib64/libkdeui.so.5
#14 0x00007f26326a598d in KPixmapCache::find(QString const&, QPixmap&) () from /usr/lib64/libkdeui.so.5
#15 0x00007f26327611ea in KIconCache::find(QString const&, QPixmap&, QString*) () from /usr/lib64/libkdeui.so.5
#16 0x00007f2632761852 in KIconLoader::loadIcon(QString const&, KIconLoader::Group, int, int, QStringList const&, QString*, bool) const () from /usr/lib64/libkdeui.so.5
#17 0x00007f26327639ed in ?? () from /usr/lib64/libkdeui.so.5
#18 0x00007f2631496d55 in QIcon::pixmap(QSize const&, QIcon::Mode, QIcon::State) const () from /usr/lib64/libQtGui.so.4
#19 0x00007f2631489290 in QWidgetPrivate::setWindowIcon_sys(bool) () from /usr/lib64/libQtGui.so.4
#20 0x00007f2631442815 in QWidget::create(unsigned long, bool, bool) () from /usr/lib64/libQtGui.so.4
#21 0x00007f2631476482 in ?? () from /usr/lib64/libQtGui.so.4
#22 0x00007f2631476df1 in QClipboard::QClipboard(QObject*) () from /usr/lib64/libQtGui.so.4
#23 0x00007f26313f2c07 in QApplication::clipboard() () from /usr/lib64/libQtGui.so.4
#24 0x00007f263267bc2e in KClipboardSynchronizer::Private::setupSignals() () from /usr/lib64/libkdeui.so.5
#25 0x00007f263267bf32 in KClipboardSynchronizer::KClipboardSynchronizer(QObject*) () from /usr/lib64/libkdeui.so.5
#26 0x00007f263267bff0 in KClipboardSynchronizer::self() () from /usr/lib64/libkdeui.so.5
#27 0x00007f26327bf3c1 in ?? () from /usr/lib64/libkdeui.so.5
#28 0x00007f26327c0539 in KApplication::KApplication(bool) () from /usr/lib64/libkdeui.so.5
#29 0x0000000000409b38 in _start ()

Thanks for helping me sorting this out

Wouter

edit:
I also did an update yesterday, but this was only minor (Flash and another program but cannot recall which one, but afterwards i rebooted without any problems, so i guess this is not the cause for my probs

2

What result from:

su -
zypper ve

zypper lr -d
3

zypper ve:

Retrieving repository 'Packman Repository' metadata [done]
Building repository 'Packman Repository' cache [done]
Retrieving repository 'games' metadata [done]
Building repository 'games' cache [done]
Retrieving repository 'google-chrome' metadata [done]
Building repository 'google-chrome' cache [done]
Loading repository data...
Reading installed packages...

Dependencies of all installed packages are satisfied.

zypper lr -d

#  | Alias                                 | Name                                  | Enabled | Refresh | Priority | Type   | URI                                                                         | Service
---+---------------------------------------+---------------------------------------+---------+---------+----------+--------+-----------------------------------------------------------------------------+--------
1  | Bijwerken van openSUSE 11.3 11.3-1.82 | Bijwerken van openSUSE 11.3 11.3-1.82 | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/11.3/                                   |        
2  | Emulators                             | Emulators                             | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/Emulators/openSUSE_11.3/          |        
3  | Packman Repository                    | Packman Repository                    | Yes     | Yes     |   99     | rpm-md | http://packman.inode.at/suse/openSUSE_11.3/                                 |        
4  | download.opensuse.org-beta            | mozilla:beta                          | No      | No      |   99     | rpm-md | http://download.opensuse.org/repositories/mozilla:/beta/openSUSE_11.3/      |        
5  | games                                 | games                                 | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/games/openSUSE_11.3/              |        
6  | google-chrome                         | google-chrome                         | Yes     | Yes     |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64                         |        
7  | libdvdcss repository                  | libdvdcss repository                  | Yes     | Yes     |   99     | rpm-md | http://opensuse-guide.org/repo/11.3/                                        |        
8  | mozilla                               | mozilla                               | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/mozilla/openSUSE_11.3/            |        
9  | openSUSE-11.3 11.3-1.82               | openSUSE-11.3 11.3-1.82               | Yes     | No      |   99     | yast2  | cd:///?devices=/dev/sr0                                                     |        
10 | openSUSE:11.3:Contrib                 | openSUSE:11.3:Contrib                 | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/openSUSE:/11.3:/Contrib/standard/ |        
11 | repo-debug                            | openSUSE-11.3-Debug                   | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/distribution/11.3/repo/oss/              |        
12 | repo-non-oss                          | openSUSE-11.3-Non-Oss                 | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/11.3/repo/non-oss/                |        
13 | repo-oss                              | openSUSE-11.3-Oss                     | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/11.3/repo/oss/                    |        
14 | repo-source                           | openSUSE-11.3-Source                  | No      | Yes     |   99     | NONE   | http://download.opensuse.org/source/distribution/11.3/repo/oss/

thanx

4

Did you update short before this happened. That includes of course any automatic updates that you configured and that thus can happen whithout you even knowing!

I do nor say that it has anything to do with your problem, but in your repos list #9 should be disabled (it is the installation CD and you do not need it as a repo anymore).
Also the libdvdcss repo #7 is better disabled after you have installed the one and only package from it.

The common point in the traceback seems to be from libQtCore.so.4 and then libstdc++.so.6 and then libc.so.6. Please check from which repos these are installed.

5

Also the libdvdcss repo #7 is better disabled after you have installed the one and only package from it.

It’s OT, but… why? Contrib and Mozilla-beta seem to be more risky to me.

6

Of course they are more risky, but the OP added them for reasons I do not know (though I can guess), but libdvdcss can only be added for one reason and the general consensus is to switch it off then.
But I admit that giving the advice about libdvdcss is bit like plugging a tiny hole in the bucket which has a loose bottom in any case because of the other repos.

7

…] but libdvdcss can only be added for one reason and the general consensus is to switch it off then.

I am sorry for one more OT - I have read about this consensus, yet I ask: why?

It’s a bit on topic actually: the contrib-source could be the culprit (as far as I know Contrib offers lesser tested packages, doesn’t it?).

8

On 2011-06-16 12:06, gropiuskalle wrote:
>
>> Also the libdvdcss repo #7 is better disabled after you have installed
>> the one and only package from it.
>
> It’s OT, but… why? Contrib and Mozilla-beta seem to be more risky to
> me.

IMO, there was a reason with the videolan repo, because of the risk of
conflicts with packman or the standard repos. However, this libdvdcss only
contains one package, so I see no risk in having it enabled. The only
“problem” is a bit of time wasted to see if they have an update.

As to disabling the CD repo, there should not be a problem with it, either.
If the cd is in, it might save some time when installing a new package.
Just “might”. If the CD is “out”, then the repo is autodisabled, AFAIK.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

9

I don’t see any big issue with that repo list
I use contrib all the time, but only for dropbox.
The Mozilla beta is off anyway
There is no Videolan repo there that I can see

I suggest trying a new user login and report back how it performs.

10

@ Henk:
I did an update before this problems, but only flash and another program updated, so I guess this may not be the problem (rebooted after this flawlessly)
I’ll disable the repos you mentioned, but how do i look up to which repos these files come from?

@caf4962: I’ll check this this evening since I don’t have much time right now

thanx

11

I am only trying things. When you say it rebooted flawlessly after last update, I guess you also wanted to say, but forgot, that you loged in in KDE and that the applics you call did run without problem.
For seeing where things are installed from, use YaST > Software > Software management and type them in the search field. When no package with that name can be found, also check the box that let it search for file names.

I think Carl’s suggestion is worthwhile to try. It will show if it it something the configs in your home directory.

12

@ Carl & Henk

I cannot create a new user or look the programs up since both kpackagekit & YaST are also infected with the program, they crash immediately after booting them up.

@Henk:
Yes, when I booted (I have auto-login) the same problems ran without any problems, this last night

13

On 2011-06-16 13:36, sonicboy wrote:
> I’ll disable the repos you mentioned, but how do i look up to which
> repos these files come from?

Version tab in yast, for example.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

14

Now you see one of the bad points of autologin.

When your programs crash, can you still logout? Then do Ctrl-Alt-F1. This will bring you to the console There you can login in the CLI and then do

su -

to become *root. *Then you can do

yast

and you will get the ncurses version of YaST. Navigate with the Tab key and select with Return. Her you can go to Users and Security and so on and create a new user.
Exit from the CLI with

exit

(two times, one for root and one for yourself).

Now go back to the GUI login screen with Ctrl-Alt-F7 and login as the new user.

15

Just a minor issue: when switching to another tty, one does not use ‘su’ but locks in directly as root, so no need to double-exit either.

16

That is not as I outlined it above. I let him log in with the normal user first. I know that you can login as root directly, but that is not the “best practise” I want to promote.

17

Security wise that makes no difference - sounds to me as if you mix that up with allowing root-login via ssh or something.

Sorry for being OT again here, but sometimes I feel an urge to correct obvious misunderstandings…

18

@Henk
Carl was right indeed.

I created a new user following the steps you noted down, and everything works flawlessly with the new user. Switched back to my normal user, and everything crashes again.

Seems as if there are problems with my setting folders indeed. What do I have to do now? Delete them? I’d prefer not to, but if it’s the only solution, it’s ok. Don’t know wether this will work for every program, since I don’t now if yast has a setting folder…

Anyway, these are just my (noob) thouths :slight_smile:

Thanx for helping me out

19

Do a console login
http://dl.dropbox.com/u/10573557/Session%20Login/console.login.png

Login as your problem user and do this:

mv .kde4 .kde4-backup

That will rename your current .kde4 to .kde4-backup and a new .kde4 will be created when you start the desktop.
If there is anything your really need like say your konversation account, we can import it. But all the desktop settings I would re-do.

20

It’s getting very weird :sarcastic:

I renamed my .kde4 folder as you said, started with a virgin desktop, but guess what…

when starting up any of the programes I’ve mentionned before, they crash again…

Under my new user, everything works fine.

Very strange if you ask me :open_mouth: