Summary: | Printer applet crashes on dbus-daemon restart | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | GDR! <gdr> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andrew.crouthamel, cfeck, misc-kdeorg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
GDR!
2011-08-15 09:00:10 UTC
> I have restarted a hanging dbus daemon.
We should find out why it is hanging. Killing it is not supported, the dbus-daemon is a required process for KDE applications (similar to X11 server; if you kill it, you cannot expect KDE applications to reconnect to the new X11 server).
It's running out of file descriptors after 2 or 3 days of running. This has been pointed a few times in different related tickets on bugs.kde.org. Are you speaking of bug 261180? Should be fixed in KDE 4.7. Yes, this is the one I'm speaking of. Nevertheless, I think that if all other KDE applications survive the restart of dbus, maybe surviving dbus restart is doable unlike surviving X restart? FYI, I'm now running KDE 4.7 and that problem persists. Created attachment 69885 [details]
New crash information added by DrKonqi
python2 (1.8) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0
- What I was doing when the application crashed:
sudo service dbus restart
dbus stop/waiting
dbus start/running, process 26948
<crash>
- Unusual behavior I noticed:
as described in bug 964542 - including other applications to be laggy, like startup and right-click-events in dolphin
-- Backtrace (Reduced):
#6 setEnabled (enable=true, this=0x1538960) at kernel/qsocketnotifier.cpp:293
#7 QSocketNotifier::setEnabled (this=0x1538960, enable=true) at kernel/qsocketnotifier.cpp:284
[...]
#10 0x00007f95ef5a97ae in QSocketNotifier::activated (this=<optimized out>, _t1=11) at .moc/release-shared/moc_qsocketnotifier.cpp:103
#11 0x00007f95ef565c7b in QSocketNotifier::event (this=0x1538960, e=0x7fffe5a2ba80) at kernel/qsocketnotifier.cpp:317
#12 0x00007f95ed3896b4 in notify_helper (e=0x7fffe5a2ba80, receiver=0x1538960, this=0x11d05d0) at kernel/qapplication.cpp:4555
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Can't speak for the OP, but I haven't seen the issue in quite some time. I'm on Kubuntu 18.04 now, running KDE 5.12.7 / Frameworks 5.47.0, as well as Qt 5.9.5, but what do you expect like seven years after initial bug reporting ;) Thanks for the update! |