| Summary: | krunner crashes on start [@ Plasma::FrameSvg::setImagePath] | ||
|---|---|---|---|
| Product: | [Plasma] krunner | Reporter: | cold_sun |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | alberto.quattrinili, darckense, denis.zalewsky, elof_sam, juha.stalnacke, mail, paul.rebholz, thijs22nospam |
| Priority: | NOR | ||
| Version: | 4.7.4 | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.8.2 | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
cold_sun
2012-06-03 08:48:59 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
After another dist-upgrade just now, krunner works again like a charm. Solved for me. 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
*** Bug 301193 has been marked as a duplicate of this bug. *** 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
*** Bug 301255 has been marked as a duplicate of this bug. *** 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). 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. > (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. > > 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
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
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
*** Bug 301556 has been marked as a duplicate of this bug. *** 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
After the last update of kde-workspace-bin (4.8.4-2), this issue seems to be solved. 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. > and for me it is also fine now. thanks! |