I can confirm this. Recompiling kde-workspace didn't help.

Arch's Qt package has been patched with these three patches (and one of them must be the cause of this crash):

https://bugs.archlinux.org/task/28381
https://bugs.archlinux.org/task/29158
https://bugs.archlinux.org/task/29402

*** Bug 298154 has been marked as a duplicate of this bug. ***

*** Bug 298162 has been marked as a duplicate of this bug. ***

*** Bug 298166 has been marked as a duplicate of this bug. ***

Created attachment 70390 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:

I just start up my pc and the window of crash was there. I upgraded qt yesterday to 4.8.1-2 and worked fine until shut down and boot again after the update.

Other packages of interest(I think) I upgraded in the same session:
dbus-core (1.4.16-1 -> 1.4.20-2)
dbus (1.4.16-1 -> 1.4.20-1)
dbus-python (0.84.0-1 -> 1.0.0-1)
xorg-server-common (1.12.0.902-1 -> 1.12.1-1)
xorg-server (1.12.0.902-1 -> 1.12.1-1)

Other applications like kopete, akregator, choqok and amarok (they uses qt) seems to work fine for me.

Now, I cannot startup KRunner anyway. I hope that helps :)

-- Backtrace (Reduced):
#12 0x00007f36f6b95484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007f36f6b99bf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007f36e4aaa50f in kdemain () from /usr/lib/libkdeinit4_krunner.so
#15 0x00000000004083e4 in _start ()

Workaround is to change a desktop theme! I get no crashes if I use "Gentle Glow", "Oxygen", "Air", "Aya", but krunner crashes on "Androbit", "Fragile", "Tibana", "Product" themes.

Actually, on two accounts on my KDE this workaround was a success, but on the third it failed.

Created attachment 70393 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:

Logging in. I have slim as loging manager. I have dbus in daemons. This is a fairly fresh install, I have deleted my old config files.

-- Backtrace (Reduced):
#12 0x00007f0ee3b33484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007f0ee3b37bf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007f0ed191e50f in kdemain () from /usr/lib/libkdeinit4_krunner.so
#15 0x00000000004083e4 in _start ()

(In reply to comment #7)
> Workaround is to change a desktop theme! I get no crashes if I use "Gentle
> Glow", "Oxygen", "Air", "Aya", but krunner crashes on "Androbit", "Fragile",
> "Tibana", "Product" themes.

Hi,
Yeah, I changed the plasma theme "slim glow" and krunner starts correctly now.
Thanks.

Created attachment 70403 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- Unusual behavior I noticed:

Error dialog appears on startup, krunner not working.

- Custom settings of the application:

Linux kernel 3.3.1 x86_64
KDE 4.8.2

-- Backtrace (Reduced):
#12 0x00007f1a4345f484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007f1a43463bf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007f1a312c350f in kdemain () from /usr/lib/libkdeinit4_krunner.so
#15 0x00000000004083e4 in _start ()

*** Bug 298190 has been marked as a duplicate of this bug. ***

Created attachment 70409 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:
Booted up the system. Instantly after logging in, krunner crashed.
If I try to open Krunner from the Dashboard with left-clik/Run command the same thing happens

-- Backtrace (Reduced):
#12 0x00007f0ff2f54484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007f0ff2f58bf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007f0fe1bcb50f in kdemain () from /usr/lib/libkdeinit4_krunner.so
#15 0x00000000004083e4 in _start ()

Created attachment 70411 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:
Krunner crashes immediately after starting both during startup and if I try to run it via Konsole.

-- Backtrace (Reduced):
#12 0x00007fc3ce297484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007fc3ce29bbf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007fc3d1b9e50f in kdemain () from /usr/lib/libkdeinit4_krunner.so
[...]
#16 0x00000000004006d1 in _start ()

(In reply to comment #11)
> Created attachment 70403 [details]
> New crash information added by DrKonqi
> 
> krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1
> 
> - Unusual behavior I noticed:
> 
> Error dialog appears on startup, krunner not working.
> 
> - Custom settings of the application:
> 
> Linux kernel 3.3.1 x86_64
> KDE 4.8.2
> 
> -- Backtrace (Reduced):
> #12 0x00007f1a4345f484 in
> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
> /usr/lib/libQtCore.so.4
> #13 0x00007f1a43463bf8 in QCoreApplication::exec() () from
> /usr/lib/libQtCore.so.4
> #14 0x00007f1a312c350f in kdemain () from /usr/lib/libkdeinit4_krunner.so
> #15 0x00000000004083e4 in _start ()

It could be due to a conflict with a previous configurations (maybe related to some plasma*rc file),  just deleted all in ~/.kde4/share/config and the error has gone.

(In reply to comment #15)
> 
> It could be due to a conflict with a previous configurations (maybe related
> to some plasma*rc file),  just deleted all in ~/.kde4/share/config and the
> error has gone.

Actually you only needed to delete plasma* files (plasma-appletsrc plasmarc).

(In reply to comment #16)
> (In reply to comment #15)
> > 
> > It could be due to a conflict with a previous configurations (maybe related
> > to some plasma*rc file),  just deleted all in ~/.kde4/share/config and the
> > error has gone.
> 
> Actually you only needed to delete plasma* files (plasma-appletsrc plasmarc).

Nope, I was wrong, this also is per account basis.

*** Bug 298228 has been marked as a duplicate of this bug. ***

Created attachment 70434 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed: I was booting the KDE eviroment whe error window appear.
Apparently all system works perfectly.

Thanks

-- Backtrace (Reduced):
#12 0x00007f52b9f7b484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007f52b9f7fbf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007f52a7e9250f in kdemain () from /usr/lib/libkdeinit4_krunner.so
#15 0x00000000004083e4 in _start ()

Created attachment 70443 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:
When I logg in to my KDE session, KDE desktop loads and I see the error dialog message every single time. 
Any attempts to launch krunner manually results in similar error.

-- Backtrace (Reduced):
#12 0x00007ff5ee2d6484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007ff5ee2dabf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007ff5f1bdd50f in kdemain () from /usr/lib/libkdeinit4_krunner.so
[...]
#16 0x00000000004006d1 in _start ()

A rollback on the qt package solved my problem.
Changing the desktop theme as suggested above did not work for me.
for the arch people, please use the archlinux rollback machine.
For other distros there should be repros available with the older package

Created attachment 70445 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:

Same here, after updating qt4 krunner keep crashing on startup.

-- Backtrace (Reduced):
#12 0x00007f835afb1484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007f835afb5bf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007f8348f0450f in kdemain () from /usr/lib/libkdeinit4_krunner.so
#15 0x00000000004083e4 in _start ()

Created attachment 70451 [details]
Output from krunner (stderr and stdout)

This is the output from krunner. Most people only post backtraces here, but the standard and error output can also provide a lot of useful information. What can be seen in the backtrace:

1) The problem might be somehow related to the shame of KDE - the Nepomuk/Akonadi bloat that has never ever worked or started properly.

2) At the end, I can see a couple of lines mentioning a std::bad_alloc exception. Since my laptop has 16 GB of RAM, out of which about 512 MB were used when I started krunner, this exception may not be caused by the lack of memory...

> 1) The problem might be somehow related to the shame of KDE - the
> Nepomuk/Akonadi bloat that has never ever worked or started properly.
> 

Not true, I've compiled my KDE installation without nepomuk/akonadi/soprano, and have the same problem.

I have the same bug. Changing plasma theme does not resolve issue. Falling back to qt 4.8.1-1 is working like a charm. It is also related with graphic driver. I had no problems with proprietary nvidia driver, but with open source ati driver i had to fall back to old version of qt package.

Created attachment 70467 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:

I just upgrading my system from KDE 4.8.1 to 4.8.2 in arch linux.

-- Backtrace (Reduced):
#12 0x00007f1262afe484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007f1262b02bf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007f126640550f in kdemain () from /usr/lib/libkdeinit4_krunner.so
[...]
#16 0x00000000004006d1 in _start ()

Hi,

It happens the same on my machine and I can confirm this started after updating to qt 4.8.1-2 and using some desktop themes like ghost, androbit and the others metioned before.

This is shown in stderr before the exception is thrown, but after downgrading to 4.8.1-1 the same errors are shown but krunner does not crash.

X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Extension:    149 (RENDER)
  Minor opcode: 4 (RenderCreatePicture)
  Resource id:  0x5c0028e
X Error: RenderBadPicture (invalid Picture parameter) 163
  Extension:    149 (RENDER)
  Minor opcode: 8 (RenderComposite)
  Resource id:  0x5c0028e
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 55 (X_CreateGC)
  Resource id:  0x5c0028e
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 55 (X_CreateGC)
  Resource id:  0x5c0028e
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 73 (X_GetImage)
  Resource id:  0x5c0028e
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

*** Bug 298215 has been marked as a duplicate of this bug. ***

*** Bug 298330 has been marked as a duplicate of this bug. ***

*** This bug has been confirmed by popular vote. ***

The std::bad_alloc crash occurs with the proprietary NVidia driver as well.

Created attachment 70475 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:

I update my system with pacman package manager (pacman -Syu). I try to remove .kde4/config, and this helps until i swith off kde desktop effects.

- Custom settings of the application:

Desktop effects is switched off.

-- Backtrace (Reduced):
#12 0x00007fd8c0d00484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007fd8c0d04bf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007fd8aeb2250f in kdemain () from /usr/lib/libkdeinit4_krunner.so
#15 0x00000000004083e4 in _start ()

It just crossed my mind that this has something to do with the gcc version Arch uses. qt-4.8.1-2 is compiled with newer version of gcc prerelase.

(In reply to comment #31)
> The std::bad_alloc crash occurs with the proprietary NVidia driver as well.

May be this is not related to the video driver at all, I have an Intel card and also had that problem.

People, create a new user and start session, if the error stops, then is just a problem of an old configuration, in that case follow the instructions of comment #16:

https://bugs.kde.org/show_bug.cgi?id=298131#c16

Strange. I really don't have this error with nVidia GT430 and latest proprietary driver. But if I use integrated video of amd 785g chipset and ati opensource driver I get this error. Here is Arch Linux bug report https://bugs.archlinux.org/task/29467?project=1&order=dateopened&sort=desc&pagenum=2 . It is definitely related with new gcc version.

Please stop talking about deleting the kde configuration, the problem can be worked-around changing the desktop theme to the default.

I choosed to downgrade qt but that was only because  I like too much the ghost theme :)

(In reply to comment #37)
> Please stop talking about deleting the kde configuration, the problem can be
> worked-around changing the desktop theme to the default.
> 
> I choosed to downgrade qt but that was only because  I like too much the
> ghost theme :)

I tried changing the desktop theme before deleting the configuration files, but that did not fixed the problem.

(In reply to comment #38)

I don't know, it's kinda weird.

When I was trying to debug krunner I've found that there is a QT option called sync. I'm not so sure what it means but I guess it is something related to threading and event dispatch/handling.

Anyway, calling krunner --sync works for me.

Can you try the previous command and let us know if it works?

(In reply to comment #39)
> (In reply to comment #38)
> 
> I don't know, it's kinda weird.
> 
> When I was trying to debug krunner I've found that there is a QT option
> called sync. I'm not so sure what it means but I guess it is something
> related to threading and event dispatch/handling.
> 
> Anyway, calling krunner --sync works for me.
> 
> Can you try the previous command and let us know if it works?

As I said before, I deleted the configuration files, now all the errors are gone, then make no sense to test that command or not.

*** Bug 298375 has been marked as a duplicate of this bug. ***

calling krunner --sync works for me too. But this command doesn't fix problem..

*** Bug 298479 has been marked as a duplicate of this bug. ***

Created attachment 70539 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:
Everytime I restarted KDE or the complete OS

-- Backtrace (Reduced):
#12 0x00007f930b15f484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007f930b163bf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007f92f8ecb50f in kdemain () from /usr/lib/libkdeinit4_krunner.so
#15 0x00000000004083e4 in _start ()

Created attachment 70540 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

After upgrading qt krunner crashes on every start. Here is what it says when i start it via the konsole:
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

terminate called after throwing an instance of 'std::bad_alloc'

-- Backtrace (Reduced):
#12 0x00007f511a350484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007f511a354bf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007f511dc5750f in kdemain () from /usr/lib/libkdeinit4_krunner.so
[...]
#16 0x00000000004006d1 in _start ()

*** Bug 298505 has been marked as a duplicate of this bug. ***

*** Bug 298514 has been marked as a duplicate of this bug. ***

Created attachment 70546 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

Krunner Interface crashes on startup.

-- Backtrace (Reduced):
#12 0x00007f05feb46484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007f05feb4abf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007f060244d50f in kdemain () from /usr/lib/libkdeinit4_krunner.so
[...]
#16 0x00000000004006d1 in _start ()

Created attachment 70557 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- Unusual behavior I noticed:

Crash happens immediately after logging in.

-- Backtrace (Reduced):
#12 0x00007fc39a7d9484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007fc39a7ddbf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007fc3887aa50f in kdemain () from /usr/lib/libkdeinit4_krunner.so
#15 0x00000000004083e4 in _start ()

*** Bug 298649 has been marked as a duplicate of this bug. ***

*** Bug 298698 has been marked as a duplicate of this bug. ***

Hello,

I found nice workaround, when i try to debug problem with krunner, kscreensaver, etc..

Next steps solve this problem without downgrading to previous version of Qt:

1. Sync abs tree from root
2. Go to /var/abs/extra/kdebase-workspace
3. Edit PKGBUILD and change:

-DCMAKE_BUILD_TYPE=Release

to

-DCMAKE_BUILD_TYPE=Debug

4. Same for /var/abs/extra/kdelibs

5. Build and install both packages with 'pacman -U'

After this trick krunner, kscreensaver, and some other components of KDE start working as expected.

Also i prepare compiled packages (for x86_64):

http://lsupport.net/resources/files-library/category/6-packages-with-debug-symbols.html

Created attachment 70627 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:
Every time I logged in, krunner crashs
- Unusual behavior I noticed:
If I change the theme, krunner runs normal (I'm using androbit)

-- Backtrace (Reduced):
#12 0x00007fc58ab46484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007fc58ab4abf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007fc58e44d50f in kdemain () from /usr/lib/libkdeinit4_krunner.so
[...]
#16 0x00000000004006d1 in _start ()

I can confirm that enabling/compiling with Debugging symbols fixes the bug for me. See Comment #52

*** Bug 298822 has been marked as a duplicate of this bug. ***

*** Bug 298727 has been marked as a duplicate of this bug. ***

Created attachment 70711 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:

After updating my system, suddenly on the next login the krunner crashed.

-- Backtrace (Reduced):
#12 0x00007fa38ebe4484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007fa38ebe8bf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007fa37cb3c50f in kdemain () from /usr/lib/libkdeinit4_krunner.so
#15 0x00000000004083e4 in _start ()

*** Bug 298928 has been marked as a duplicate of this bug. ***

*** Bug 299082 has been marked as a duplicate of this bug. ***

*** Bug 299087 has been marked as a duplicate of this bug. ***

*** Bug 299101 has been marked as a duplicate of this bug. ***

*** Bug 299116 has been marked as a duplicate of this bug. ***

*** Bug 299363 has been marked as a duplicate of this bug. ***

Created attachment 70858 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1

still had crash after upgrading to 4.8.3-1 in Arch.

-- Backtrace (Reduced):
#11 0x00007fd1d4813484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#12 0x00007fd1d4817bf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#13 0x00007fd1c27bf50f in kdemain () from /usr/lib/libkdeinit4_krunner.so
#14 0x0000000000408292 in _start ()

 OK so I've found out what this crash was about but on Frugalware linux, I've already fixed it there and all seems fine.
 I'm not sure what goes wrong on other distro like Arch but it could be the same or similar.
 Here's what to do:
 1. Make debug version of Qt4 ( with debug symbols so gdb can find line numbers and such )
 2. Make version with debug flags stuff , kdeworkspace on Frugalware. Please note that I don't mean compile KDE with debug option, then the error will be gone. You should modify the flags for KDE cmake , can't remeber right now , and add -ggdb3. I can find it again if you need.
 3. Now gdb krunner
 4. from gdb prompt : catch throw
 5. run --nofork
 6. You should now have a backtrace of where the exception is thrown from. It's not what DrKonqi displays as you will see. Line numbers should be included.

*** Bug 299457 has been marked as a duplicate of this bug. ***

Created attachment 70888 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1

- What I was doing when the application crashed:
I was trying to switch user from the Application Launcher

-- Backtrace (Reduced):
#11 0x00007f901de33484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#12 0x00007f901de37bf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#13 0x00007f90216e050f in kdemain () from /usr/lib/libkdeinit4_krunner.so
[...]
#15 0x00000000004006d1 in _start ()

Created attachment 70894 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1

- What I was doing when the application crashed:
Logging in. This crash happens on every single login just as the desktop is shown.

-- Backtrace (Reduced):
#11 0x00007f1ff3c1d484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#12 0x00007f1ff3c21bf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#13 0x00007f1fe1a1a50f in kdemain () from /usr/lib/libkdeinit4_krunner.so
#14 0x0000000000408292 in _start ()

 Please see my comments above on how to debug the problem if you want to help. I can help you fix this but you must provide more info.

*** Bug 299512 has been marked as a duplicate of this bug. ***

I experience the same crash, also on Arch Linux. My workaround for now is to downgrade Qt to 4.8.1-1 and it works again.

Hi, I enabled the KDE Desktop effects and now I can open krunner using Alt + F2, or it was because I clicked on lock screen and nothing happen, after few tries the krunner loaded and ask me to save session, close session, logout or something like that, weird.

I must add that plasma-desktop crashed after enabling the effects and reload it self successfully.

Hope this helps.

Regards,
Damjan Dimitrioski.

 KDE compile flags are in FindKDE4Internal.cmake  ,you just need to add "-ggdb3" to release flags.

Created attachment 70940 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1

- What I was doing when the application crashed:

Crashes during boot time. As I read from the bug report, its similar to the krunner crash.

-- Backtrace (Reduced):
#11 0x00007fb5c0288484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#12 0x00007fb5c028cbf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#13 0x00007fb5ae23150f in kdemain () from /usr/lib/libkdeinit4_krunner.so
#14 0x0000000000408292 in _start ()

 There's a patch for this by Aaron Seigo, could anyone try it ? 

http://mail.kde.org/pipermail/plasma-devel/attachments/20120508/b7d0e586/attachment.diff

 The source if from the conversation here:

 http://mail.kde.org/pipermail/plasma-devel/2012-May/019472.html

Compiling now. Will report in about an hour.

kdebase-workspace patched (Arch Linux):
http://pkgbuild.com/~andrea/pkgs/kdebase-workspace/trunk/kdebase-workspace-4.8.3-2-i686.pkg.tar.xz
http://pkgbuild.com/~andrea/pkgs/kdebase-workspace/trunk/kdebase-workspace-4.8.3-2-x86_64.pkg.tar.xz

Please try them, thanks.

(In reply to comment #77)

Andrea,

I'm sorry, but the packages are not there, can you check again please?

I'll be happy to test then :)

http://pkgbuild.com/~andrea/pkgs/kdebase-workspace/trunk/

(In reply to comment #78)

I mean, the 64-bit package is not there

I can confirm, the patch by Aaron Seigo fixes this bug for me! Thanks a lot!

(In reply to comment #80)

Idem here, with Andrea's package

Thanks!

Created attachment 70988 [details]
New crash information added by DrKonqi

krunner (0.1) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1

- What I was doing when the application crashed:

Logging into kde.  Krunner crashes every time.

-- Backtrace (Reduced):
#11 0x00007ff1ee4c1484 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#12 0x00007ff1ee4c5bf8 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#13 0x00007ff1f1d6e50f in kdemain () from /usr/lib/libkdeinit4_krunner.so
[...]
#15 0x00000000004006d1 in _start ()

*** Bug 299767 has been marked as a duplicate of this bug. ***

*** Bug 299201 has been marked as a duplicate of this bug. ***

*** Bug 299117 has been marked as a duplicate of this bug. ***

*** Bug 298566 has been marked as a duplicate of this bug. ***

*** Bug 300688 has been marked as a duplicate of this bug. ***

*** Bug 300689 has been marked as a duplicate of this bug. ***

*** Bug 300993 has been marked as a duplicate of this bug. ***

*** Bug 301003 has been marked as a duplicate of this bug. ***

*** Bug 301096 has been marked as a duplicate of this bug. ***

*** Bug 302401 has been marked as a duplicate of this bug. ***

*** Bug 302400 has been marked as a duplicate of this bug. ***

Greetings!

I just wanted to confirm that all crashes have gone after I have upgraded a) gcc to 4.7.1 and b) kde to 4.8.4 (built from source on a Gentoo x64 system).

My original report had been added to Bug 301096, which has been marked as a duplicate of this one. But this is what happened: krunner/plasma crashed on my system right after login. This crash was gone after upgrading to gcc 4.7.1 and rebuilding kde 4.8.3. But the crash happened again every time I plugged in or unplugged an external monitor on my laptop. The latter crash is now gone, too. Hopefully for good now.

Here are the settings and packages used right now on my laptop:

X11:
----
xorg-server-1.12.2 with:
- libdrm-2.4.33
- mesa-8.0.3 (With EGL, GLES1 and GLES2 support enabled)
- xf86-video-intel-2.19.0

QT:
---
Version 4.8.2 with EGL support, set to raster engine. kwin has been compiled with GLES support.

gcc LD/C(XX)FLAGS:
---------------
Everything has been compiled adding the following flags as both CFLAGS and CXXFLAGS:
"-march=native -pipe -ftree-vectorize -ggdb -O2 -fgraphite-identity -floop-interchange -floop-strip-mine -floop-block -ftree-loop-distribution"

The following LDFLAGS have been used in addition to the CFLAGS above:
"-Wl,--sort-common -Wl,--hash-style=gnu -Wl,--as-needed"

*** Bug 302725 has been marked as a duplicate of this bug. ***

*** Bug 303042 has been marked as a duplicate of this bug. ***

*** Bug 303293 has been marked as a duplicate of this bug. ***

*** Bug 303294 has been marked as a duplicate of this bug. ***

*** Bug 303637 has been marked as a duplicate of this bug. ***