Bug 301089 - krunner crashes on start [@ Plasma::FrameSvg::setImagePath]
Summary: krunner crashes on start [@ Plasma::FrameSvg::setImagePath]
Status: RESOLVED FIXED
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 4.7.4
Platform: Debian unstable Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 301193 301255 301556 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-06-03 08:48 UTC by cold_sun
Modified: 2012-06-19 13:01 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.8.2
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (4.07 KB, text/plain)
2012-06-04 06:57 UTC, Török Edwin
Details
New crash information added by DrKonqi (4.28 KB, text/plain)
2012-06-05 14:13 UTC, elof_sam
Details
New crash information added by DrKonqi (3.77 KB, text/plain)
2012-06-05 21:27 UTC, darckense
Details
New crash information added by DrKonqi (3.84 KB, text/plain)
2012-06-06 22:22 UTC, Peter Schulte-Stracke
Details
New crash information added by DrKonqi (3.88 KB, text/plain)
2012-06-07 20:11 UTC, Denis Zalewsky
Details
New crash information added by DrKonqi (3.79 KB, text/plain)
2012-06-08 12:26 UTC, Alberto Quattrini Li
Details
New crash information added by DrKonqi (3.90 KB, text/plain)
2012-06-10 08:22 UTC, mmdanziger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description cold_sun 2012-06-03 08:48:59 UTC
Application: krunner (0.1)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.8.1
Operating System: Linux 3.4-0.slh.3-aptosid-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
Hello,

after dist-upgrade on debian SID, krunner is crashing on each start.

The crash can be reproduced every time.

-- Backtrace:
Application: Interface d'exécution de commande (krunner), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcf1d4c27a0 (LWP 4564))]

Thread 2 (Thread 0x7fcf15ac1700 (LWP 4565)):
#0  0x00007fcf32c9dd93 in *__GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fcf281184d4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fcf281185f4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fcf2f68c7c6 in QEventDispatcherGlib::processEvents (this=0x2583a50, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007fcf2f65d14f in QEventLoop::processEvents (this=this@entry=0x7fcf15ac0d10, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fcf2f65d3d8 in QEventLoop::exec (this=0x7fcf15ac0d10, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fcf2f560c50 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007fcf2f63daaf in QInotifyFileSystemWatcherEngine::run (this=0x2582000) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fcf2f563beb in QThreadPrivate::start (arg=0x2582000) at thread/qthread_unix.cpp:298
#9  0x00007fcf23df7b74 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1
#10 0x00007fcf285e5b50 in start_thread (arg=<optimized out>) at pthread_create.c:304
#11 0x00007fcf32ca89dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fcf1d4c27a0 (LWP 4564)):
[KCrash Handler]
#6  0x00007fcf32c02475 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007fcf32c056f0 in *__GI_abort () at abort.c:92
#8  0x00007fcf2efc368d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007fcf2efc1796 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007fcf2efc17c3 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007fcf2efc1a36 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007fcf2f674430 in QMetaObject::activate (sender=0x2601210, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3576
#13 0x00007fcf3213325b in Plasma::FrameSvg::setImagePath (this=0x2601210, path=...) at ../../plasma/framesvg.cpp:113
#14 0x00007fcf32f802cf in KRunnerDialog::updatePresentation (this=0x2599f30) at ../../krunner/krunnerdialog.cpp:245
#15 0x00007fcf32f80d75 in KRunnerDialog::KRunnerDialog (this=0x2599f30, runnerManager=<optimized out>, parent=<optimized out>, f=...) at ../../krunner/krunnerdialog.cpp:94
#16 0x00007fcf32f86644 in Interface::Interface (this=0x2599f30, runnerManager=0x238eee0, parent=<optimized out>) at ../../krunner/interfaces/default/interface.cpp:69
#17 0x00007fcf32f83686 in KRunnerApp::initialize (this=0x2390e60) at ../../krunner/krunnerapp.cpp:168
#18 0x00007fcf32f83ef3 in KRunnerApp::KRunnerApp (this=0x2390e60) at ../../krunner/krunnerapp.cpp:79
#19 0x00007fcf32f83f45 in KRunnerApp::self () at ../../krunner/krunnerapp.cpp:66
#20 0x00007fcf32f84695 in kdemain (argc=1, argv=0x7fffc0835c78) at ../../krunner/main.cpp:62
#21 0x00007fcf32beeead in __libc_start_main (main=<optimized out>, argc=<optimized out>, ubp_av=<optimized out>, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffc0835c68) at libc-start.c:228
#22 0x00000000004006f1 in _start ()

Reported using DrKonqi
Comment 1 Török Edwin 2012-06-04 06:57:09 UTC
Created attachment 71558 [details]
New crash information added by DrKonqi

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

- What I was doing when the application crashed:

Login to KDE after a dist-upgrade on Debian unstable and I get a crash report about krunner

-- Backtrace (Reduced):
#13 0x00007f4a35af225b in Plasma::FrameSvg::setImagePath (this=0xf462e0, path=...) at ../../plasma/framesvg.cpp:113
#14 0x0000003cf36292cf in KRunnerDialog::updatePresentation (this=0xf4fbd0) at ../../krunner/krunnerdialog.cpp:245
#15 0x0000003cf3629d75 in KRunnerDialog::KRunnerDialog (this=0xf4fbd0, runnerManager=<optimized out>, parent=<optimized out>, f=...) at ../../krunner/krunnerdialog.cpp:94
#16 0x0000003cf362f644 in Interface::Interface (this=0xf4fbd0, runnerManager=0xf1b6b0, parent=<optimized out>) at ../../krunner/interfaces/default/interface.cpp:69
#17 0x0000003cf362c686 in KRunnerApp::initialize (this=0xd88d00) at ../../krunner/krunnerapp.cpp:168
Comment 2 cold_sun 2012-06-04 16:40:13 UTC
After another dist-upgrade just now, krunner works again like a charm. Solved for me.
Comment 3 elof_sam 2012-06-05 14:13:10 UTC
Created attachment 71602 [details]
New crash information added by DrKonqi

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

- What I was doing when the application crashed:

Every time I launch krunner, it craches, regardless of how I choose to launch it.

-- Backtrace (Reduced):
#13 0x00007f4d5cb4e25b in Plasma::FrameSvg::setImagePath (this=0x1fb1e80, path=...) at ../../plasma/framesvg.cpp:113
#14 0x00007f4d5d99b2cf in KRunnerDialog::updatePresentation (this=0x1fc1d00) at ../../krunner/krunnerdialog.cpp:245
#15 0x00007f4d5d99bd75 in KRunnerDialog::KRunnerDialog (this=0x1fc1d00, runnerManager=<optimized out>, parent=<optimized out>, f=...) at ../../krunner/krunnerdialog.cpp:94
#16 0x00007f4d5d9a1644 in Interface::Interface (this=0x1fc1d00, runnerManager=0x1d4a360, parent=<optimized out>) at ../../krunner/interfaces/default/interface.cpp:69
#17 0x00007f4d5d99e686 in KRunnerApp::initialize (this=0x1d3be60) at ../../krunner/krunnerapp.cpp:168
Comment 4 Myriam Schweingruber 2012-06-05 19:47:34 UTC
*** Bug 301193 has been marked as a duplicate of this bug. ***
Comment 5 darckense 2012-06-05 21:27:21 UTC
Created attachment 71607 [details]
New crash information added by DrKonqi

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

Crash on startup on debian sid.

-- Backtrace (Reduced):
#13 0x00007f6cccc4925b in Plasma::FrameSvg::setImagePath (this=0x12b0870, path=...) at ../../plasma/framesvg.cpp:113
#14 0x00007f6ccda962cf in KRunnerDialog::updatePresentation (this=0x129d410) at ../../krunner/krunnerdialog.cpp:245
#15 0x00007f6ccda96d75 in KRunnerDialog::KRunnerDialog (this=0x129d410, runnerManager=<optimized out>, parent=<optimized out>, f=...) at ../../krunner/krunnerdialog.cpp:94
#16 0x00007f6ccda9c644 in Interface::Interface (this=0x129d410, runnerManager=0x1269e60, parent=<optimized out>) at ../../krunner/interfaces/default/interface.cpp:69
#17 0x00007f6ccda99686 in KRunnerApp::initialize (this=0x10c8d00) at ../../krunner/krunnerapp.cpp:168
Comment 6 Thijs 2012-06-06 07:03:02 UTC
*** Bug 301255 has been marked as a duplicate of this bug. ***
Comment 7 Thijs 2012-06-06 07:07:04 UTC
Thusfar, all the reports have been with the exact same setup: Debian unstable, KDE 4.7.4, Qt 4.8.1. Likely to be something upstream, downstream and/or already resolved. Did somebody file this bug at Debian? 
@Cold_sun: If this has been resolved for you after another update, do you know what exactly was updated the second time? (and the first).
Comment 8 Paul 2012-06-06 07:41:53 UTC
not yet, but I can do this.

On Wed, Jun 6, 2012 at 9:07 AM, Thijs <thijs22nospam@googlemail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=301089
>
> Thijs <thijs22nospam@googlemail.com> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |NEW
>     Ever confirmed|0                           |1
>
> --- Comment #7 from Thijs <thijs22nospam@googlemail.com> ---
> Thusfar, all the reports have been with the exact same setup: Debian
> unstable,
> KDE 4.7.4, Qt 4.8.1. Likely to be something upstream, downstream and/or
> already
> resolved. Did somebody file this bug at Debian?
> @Cold_sun: If this has been resolved for you after another update, do you
> know
> what exactly was updated the second time? (and the first).
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>
Comment 9 Paul 2012-06-06 08:00:06 UTC
(In reply to comment #8)
tried to file a bug, but got following advice instead:
Your version (4:4.7.4-2+b1) of kde-workspace-bin appears to be out of date.                                                                                                                                   
The following newer release(s) are available in the Debian archive:                                                                                                                                           
  experimental: 4:4.8.3-2
suggestions?
> not yet, but I can do this.
> 
> On Wed, Jun 6, 2012 at 9:07 AM, Thijs <thijs22nospam@googlemail.com> wrote:
> 
> > https://bugs.kde.org/show_bug.cgi?id=301089
> >
> > Thijs <thijs22nospam@googlemail.com> changed:
> >
> >           What    |Removed                     |Added
> >
> > ----------------------------------------------------------------------------
> >             Status|UNCONFIRMED                 |NEW
> >     Ever confirmed|0                           |1
> >
> > --- Comment #7 from Thijs <thijs22nospam@googlemail.com> ---
> > Thusfar, all the reports have been with the exact same setup: Debian
> > unstable,
> > KDE 4.7.4, Qt 4.8.1. Likely to be something upstream, downstream and/or
> > already
> > resolved. Did somebody file this bug at Debian?
> > @Cold_sun: If this has been resolved for you after another update, do you
> > know
> > what exactly was updated the second time? (and the first).
> >
> > --
> > You are receiving this mail because:
> > You are on the CC list for the bug.
> >
Comment 10 Peter Schulte-Stracke 2012-06-06 22:22:10 UTC
Created attachment 71629 [details]
New crash information added by DrKonqi

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

- What I was doing when the application crashed:
Starting the KDE session (crash immediately after login)

-- Backtrace (Reduced):
#13 0x00007fb40e29925b in Plasma::FrameSvg::setImagePath (this=0x19a0a00, path=...) at ../../plasma/framesvg.cpp:113
#14 0x00007fb40f0e62cf in KRunnerDialog::updatePresentation (this=0x1948190) at ../../krunner/krunnerdialog.cpp:245
#15 0x00007fb40f0e6d75 in KRunnerDialog::KRunnerDialog (this=0x1948190, runnerManager=<optimized out>, parent=<optimized out>, f=...) at ../../krunner/krunnerdialog.cpp:94
#16 0x00007fb40f0ec644 in Interface::Interface (this=0x1948190, runnerManager=0x170ab10, parent=<optimized out>) at ../../krunner/interfaces/default/interface.cpp:69
#17 0x00007fb40f0e9686 in KRunnerApp::initialize (this=0x16f6d10) at ../../krunner/krunnerapp.cpp:168
Comment 11 Denis Zalewsky 2012-06-07 20:11:50 UTC
Created attachment 71648 [details]
New crash information added by DrKonqi

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

- What I was doing when the application crashed:

Booting KDE, krunner was just started. Running krunner from the commandline gives the same crash

-- Backtrace (Reduced):
#13 0x00007f1743ec525b in Plasma::FrameSvg::setImagePath (this=0x2751630, path=...) at ../../plasma/framesvg.cpp:113
#14 0x00007f1744d122cf in KRunnerDialog::updatePresentation (this=0x26273b0) at ../../krunner/krunnerdialog.cpp:245
#15 0x00007f1744d12d75 in KRunnerDialog::KRunnerDialog (this=0x26273b0, runnerManager=<optimized out>, parent=<optimized out>, f=...) at ../../krunner/krunnerdialog.cpp:94
#16 0x00007f1744d18644 in Interface::Interface (this=0x26273b0, runnerManager=0x25ea4e0, parent=<optimized out>) at ../../krunner/interfaces/default/interface.cpp:69
#17 0x00007f1744d15686 in KRunnerApp::initialize (this=0x2435cd0) at ../../krunner/krunnerapp.cpp:168
Comment 12 Alberto Quattrini Li 2012-06-08 12:26:09 UTC
Created attachment 71663 [details]
New crash information added by DrKonqi

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

- What I was doing when the application crashed:

The system was just starting up all the applications after the boot of the laptop.

-- Backtrace (Reduced):
#13 0x00007f0cb408e25b in Plasma::FrameSvg::setImagePath (this=0x1de2b00, path=...) at ../../plasma/framesvg.cpp:113
#14 0x00007f0cb4edb2cf in KRunnerDialog::updatePresentation (this=0x1dbe390) at ../../krunner/krunnerdialog.cpp:245
#15 0x00007f0cb4edbd75 in KRunnerDialog::KRunnerDialog (this=0x1dbe390, runnerManager=<optimized out>, parent=<optimized out>, f=...) at ../../krunner/krunnerdialog.cpp:94
#16 0x00007f0cb4ee1644 in Interface::Interface (this=0x1dbe390, runnerManager=0x1c619b0, parent=<optimized out>) at ../../krunner/interfaces/default/interface.cpp:69
#17 0x00007f0cb4ede686 in KRunnerApp::initialize (this=0x1c4f680) at ../../krunner/krunnerapp.cpp:168
Comment 13 Anne-Marie Mahfouf 2012-06-10 07:34:44 UTC
*** Bug 301556 has been marked as a duplicate of this bug. ***
Comment 14 mmdanziger 2012-06-10 08:22:54 UTC
Created attachment 71693 [details]
New crash information added by DrKonqi

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

- What I was doing when the application crashed:

Crashes every time on startup after recent dist-upgrade.

-- Backtrace (Reduced):
#13 0x00007fd57cc3c25b in Plasma::FrameSvg::setImagePath (this=0x1c284b0, path=...) at ../../plasma/framesvg.cpp:113
#14 0x00007fd57da89227 in KRunnerDialog::updatePresentation (this=0x1b3f8d0) at ../../krunner/krunnerdialog.cpp:239
#15 0x00007fd57da89d75 in KRunnerDialog::KRunnerDialog (this=0x1b3f8d0, runnerManager=<optimized out>, parent=<optimized out>, f=...) at ../../krunner/krunnerdialog.cpp:94
#16 0x00007fd57da8f644 in Interface::Interface (this=0x1b3f8d0, runnerManager=0x1b11ca0, parent=<optimized out>) at ../../krunner/interfaces/default/interface.cpp:69
#17 0x00007fd57da8c686 in KRunnerApp::initialize (this=0x1971cc0) at ../../krunner/krunnerapp.cpp:168
Comment 15 Alberto Quattrini Li 2012-06-13 08:32:50 UTC
After the last update of kde-workspace-bin (4.8.4-2), this issue seems to be solved.
Comment 16 Paul 2012-06-13 09:27:52 UTC
yep, problem solved for me as well - thanks!

On Wed, Jun 13, 2012 at 10:32 AM, Alberto Quattrini Li <
alberto.quattrinili@gmail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=301089
>
> --- Comment #15 from Alberto Quattrini Li <alberto.quattrinili@gmail.com>
> ---
> After the last update of kde-workspace-bin (4.8.4-2), this issue seems to
> be
> solved.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>
Comment 17 Denis Zalewsky 2012-06-13 12:45:03 UTC
and for me it is also fine now. thanks!
Comment 18 Myriam Schweingruber 2012-06-19 13:01:51 UTC
Closing based on comments #15, 16 and 17. Thank you all for the feedback.