| Summary: | Run Command Crashed After Launching Program | ||
|---|---|---|---|
| Product: | [Plasma] krunner | Reporter: | Aric Gregson <aorchid> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | pjfloyd, rakuco, rnejdl |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | FreeBSD | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Aric Gregson
2010-05-24 19:49:18 UTC
*** Bug 243538 has been marked as a duplicate of this bug. *** *** Bug 250267 has been marked as a duplicate of this bug. *** Can you still reproduce this issue? On Mon, 27 Sep 2010 18:30:58 +0200 (CEST), Raphael Kubo da Costa <kubito@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=238722 > > > Raphael Kubo da Costa <kubito@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |kubito@gmail.com > > > > > --- Comment #3 from Raphael Kubo da Costa <kubito gmail com> > 2010-09-27 18:30:55 --- > Can you still reproduce this issue? I don't think I can any more. The number of bugs in KDE did drop a lot with this last release, but there are still a few left. Sincerely, Rusty Nejdl Well, it does look like those upstream D-Bus issues which should be fixed by D-Bus 1.4.0. There's bug 208921 which looks a lot like this one, but it is marked as a Dolphin bug. For now, I think it's better to close this one then. If the issue pops up again (especially after D-Bus 1.4.0 hits the ports tree, probably after the next GNOME update), please reopen. On Mon, 27 Sep 2010 19:26:56 +0200 (CEST), Raphael Kubo da Costa <kubito@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=238722 > > > Raphael Kubo da Costa <kubito@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution| |WORKSFORME > > > > > --- Comment #5 from Raphael Kubo da Costa <kubito gmail com> > 2010-09-27 19:26:55 --- > Well, it does look like those upstream D-Bus issues which should be > fixed by > D-Bus 1.4.0. > > There's bug 208921 which looks a lot like this one, but it is marked > as a > Dolphin bug. > > For now, I think it's better to close this one then. If the issue > pops up again > (especially after D-Bus 1.4.0 hits the ports tree, probably after the > next > GNOME update), please reopen. Thanks and sounds good! Created attachment 52785 [details]
New crash information added by DrKonqi
krunner (0.1) on KDE Platform 4.5.2 (KDE 4.5.2) using Qt 4.6.3
- What I was doing when the application crashed:
I hit alt-f2 for the run prompt. Then I chose chrome from the list which already there. Chrome successfully luached and then about 2 seconds later the crash report came up.
-- Backtrace (Reduced):
#7 0x000000080c463c90 in dbus_connection_set_change_sigpipe () from /usr/local/lib/libdbus-1.so.3
#8 0x000000080c4733de in dbus_get_local_machine_id () from /usr/local/lib/libdbus-1.so.3
#9 0x000000080c467993 in dbus_connection_send_with_reply_and_block () from /usr/local/lib/libdbus-1.so.3
#10 0x00000008012483b6 in QDBusConnectionPrivate::timerEvent () from /usr/local/lib/qt4/libQtDBus.so.4
#11 0x0000000801547cc4 in QObject::event () from /usr/local/lib/qt4/libQtCore.so.4
As mentioned on the kde-freebsd mailing list, these issues should probably go away now that dbus 1.4.0 has been committed to the ports tree. |