[Bug 1053910] Re: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem
Launchpad has imported 11 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=55136.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2012-09-20T10:14:32+00:00 kenorb wrote:
Basically I've huge problems with dbus.
My main problem is that different binaries like kdialog and plasma-desktop are
freezing and crashing all the time, so I can't use my Linux (Ubuntu) desktop
properly.
Problems include:
https://bugs.kde.org/show_bug.cgi?id=307049
https://bugs.kde.org/show_bug.cgi?id=307048
Here is strace example of sent message by kdialog:
8549 sendmsg(7, {msg_name(0)=NULL,
msg_iov(2)=[{l\1\0\1\21\0\0\0\20\0\0\0\177\0\0\0\1\1o\0\25\0\0\0/org/fre...,
144}, {\f\0\0\0org.kde.kded\0, 17}], msg_controllen=0, msg_flags=0},
MSG_NOSIGNAL) = 161 0.15
8549 poll([{fd=7, events=POLLIN}], 1, 25000) = 1 ([{fd=7, revents=POLLIN}])
0.61
8549 recvmsg(7, {msg_name(0)=NULL,
msg_iov(1)=[{l\2\1\1\t\0\0\0\6\0\0\0=\0\0\0\6\1s\0\6\0\0\0:1.169\0\0...,
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 89
0.09
8549 recvmsg(7, 0x7fff71c561e0, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource
temporarily unavailable) 0.10
8549 sendmsg(7, {msg_name(0)=NULL,
msg_iov(2)=[{l\1\0\1\0\0\0\0\21\0\0\0k\0\0\0\1\1o\0\5\0\0\0/kded\0\0\0...,
128}, {, 0}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 128 0.10
8549 poll([{fd=7, events=POLLIN}], 1, 25000) = 0 (Timeout) 25.020763
Last number show the time spent in system calls.
poll() = 25 seconds
I've 4 of these in one run:
8549 poll([{fd=7, events=POLLIN}], 1, 25000) = 0 (Timeout) 25.020763
8549 poll([{fd=7, events=POLLIN}], 1, 25000) = 0 (Timeout) 25.008094
8549 poll([{fd=7, events=POLLIN}], 1, 25000) = 0 (Timeout) 25.025128
8549 poll([{fd=7, events=POLLIN}], 1, 25000) = 0 (Timeout) 25.025123
25 second each = 1 minute to run single popup window (kdialog).
The same happening with plasma-desktop, once I click on panel, it takes
few minutes to react on my click!
Here are some socket statistics:
$ netstat -na | grep dbus | grep CONNECTED | wc -l
124
Is there any connection limit to dbus before the timeout?
$ sudo netstat -nap | grep dbus | grep CONNECTED | awk '{print $8}' | sort |
uniq -c
2 1932/dbus-launch
95 1933/dbus-daemon
4 2490/gvfsd-trash
2 2492/gvfsd-burn
44 865/dbus-daemon
I was playing with dbus-monitor, but it didn't help anything, because it
doesn't show even which process (PID) is connecting to it. I found some
references to (--print-pid), but I didn't know how to use this feature.
Here is something, that I found as possible cause of it.
When starting dbus-daemon manually, I've the following error:
$ /bin/dbus-daemon --print-pid 5 --print-address 7 --session
Failed to start message bus: Writing to pipe: Bad file descriptor
Running with sudo doesn't help either.
strace gives me this:
stat(/usr/share/dbus-1/services/org.gnome.Rhythmbox3.service,
{st_mode=S_IFREG|0644, st_size=66, ...}) = 0
stat(/usr/share/dbus-1/services/org.ayatana.bamf.service,
{st_mode=S_IFREG|0644, st_size=68, ...}) = 0
open(/usr/share/dbus-1/services/org.ayatana.bamf.service, O_RDONLY) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=68, ...}) = 0
read(5, ..., 68) = 68
close(5)= 0
stat(/usr/share/dbus-1/services/org.ayatana.bamf.service,
{st_mode=S_IFREG|0644, st_size=68, ...}) = 0
stat(/usr/share/dbus-1/services/org.gnome.evince.Daemon.service,
{st_mode=S_IFREG|0644, st_size=74, ...}) = 0
open(/usr/share/dbus-1/services/org.gnome.evince.Daemon.service, O_RDONLY) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=74, ...}) = 0
read(5, ..., 74) = 74
close(5)= 0
stat(/usr/share/dbus-1/services/org.gnome.evince.Daemon.service,
{st_mode=S_IFREG|0644, st_size=74, ...}) = 0
getdents(4, /* 0 entries */, 32768) = 0
close(4)= 0
write(7, ..., 73) = -1 EBADF (Bad file descriptor)
close(3)= 0
write(2, ..., 67Failed to start message bus: Writing to pipe: Bad file
descriptor
) = 67
exit_group(1) = ?
First I thought it's failing because of the last file, but the file is fine and
after moving it, it's still failing, so it must something else.
Currently it's up-and-running as:
102872 0.0 0.0 25028 1884 ?Ss Sep19 0:00 dbus-daemon
--system --fork --activation=upstart
kenorb1969 0.0 0.0 26548 388 ?SSep19 0:00
/usr/bin/dbus-launch --exit-with-session /usr/bin/startkde
kenorb1970 0.0 0.0 27792 3580 ?Ss Sep19 0:02
//bin/dbus-daemon --fork --print-pid 5 --print-address 7
[Bug 1053910] Re: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem
Launchpad has imported 38 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=307049.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2012-09-19T14:42:18+00:00 kenorb wrote:
When I'm using Chrome 18.0.1025.168 (Developer Build 134367 Linux) on
Ubuntu 12.04, the KDialog takes around 25 seconds to show up!
Reproducible: Always
Steps to Reproduce:
1. Go to: https://code.google.com/p/chromium/issues/entry
2. Click on: Attach the file
3. Click on: Choose File
4. Problem: Nothing happens.
5. After 25 seconds KDialog appears.
6. It takes another 20-30 seconds to fully load (still you can't click
anything).
7. After the whole 1 minute you can choose the file.
Expected Results:
In Firefox (which doesn't uses KDialog) it works within few seconds.
Qt: 4.8.1
KDE Development Platform: 4.8.4 (4.8.4)
KDialog: 1.0
When executed manually the following command:
strace kdialog --attach=71303405 --title=Open File --getopenfilename
/home/kenorb/Sites/x/sites/all/modules/contrib/simpletest_clone
It seems to stop on poll for exactly 25 seconds!
write(3, \1\0\0\0\0\0\0\0, 8) = 8
poll([{fd=6, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=6, revents=POLLOUT}])
writev(6,
[{\225\24\31\0\32\0\300\5\1\0\0\0+\0\0\0\7\0\t\0\377\377\t\0\t\0\0\0\3648\0\0...,
400}, {NULL, 0}, {, 0}], 3) = 400
recvfrom(6, 0x7aef44, 4096, 0, 0, 0)= -1 EAGAIN (Resource temporarily
unavailable)
write(3, \1\0\0\0\0\0\0\0, 8) = 8
sendmsg(7, {msg_name(0)=NULL,
msg_iov(2)=[{l\1\0\1\21\0\0\0\20\0\0\0\177\0\0\0\1\1o\0\25\0\0\0/org/fre...,
144}, {\f\0\0\0org.kde.kded\0, 17}], msg_controllen=0, msg_flags=0},
MSG_NOSIGNAL) = 161
poll([{fd=7, events=POLLIN}], 1, 25000) = 1 ([{fd=7, revents=POLLIN}])
recvmsg(7, {msg_name(0)=NULL,
msg_iov(1)=[{l\2\1\1\t\0\0\0\6\0\0\0=\0\0\0\6\1s\0\6\0\0\0:1.162\0\0...,
2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 89
recvmsg(7, 0x7fff4ef79770, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily
unavailable)
sendmsg(7, {msg_name(0)=NULL,
msg_iov(2)=[{l\1\0\1\0\0\0\0\21\0\0\0k\0\0\0\1\1o\0\5\0\0\0/kded\0\0\0...,
128}, {, 0}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 128
poll([{fd=7, events=POLLIN}], 1, 25000
Is there any sleep(25) or something? Why?
It happens every time to me when I'm trying to upload anything on any site in
Chrome browser, but it also happens in other software using KDialog as well.
Qt: 4.8.1
KDE Development Platform: 4.8.5 (4.8.5)
KDialog: 1.0
Reply at:
https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1053910/comments/0
On 2012-09-19T14:49:59+00:00 Christoph-maxiom wrote:
Please temporarily rename ~/.kde/share/apps/kfileplaces/bookmarks.xml
and try again. You might have some remote places in the places panel
that get stuck waiting for a connection.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1053910/comments/1
On 2012-09-19T15:02:06+00:00 kenorb wrote:
I've moved the file. The file was re-created within few seconds after 'Choose
file' click to default, but still it took KDialog 25 seconds to appear.
bookmarks.xml file seems to be default as it was.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1053910/comments/2
On 2012-09-19T15:08:37+00:00 Christoph-maxiom wrote:
Could you try running solid-hardware list details in a Konsole, and
check if it blocks for the same long time? Is dbus-daemon running for
your current user?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1053910/comments/3
On 2012-09-19T15:11:50+00:00 kenorb wrote:
Simulating the same command like as it was executed by Chrome (it's doing the
same):
$ time kdialog --attach=56623340 --title=Open File --getopenfilename
/home/kenorb/Downloads/
kdialog(8234)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize()
D-Bus call failed: Did not receive a reply. Possible causes include: the
remote application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network connection was
broken.
real1m42.668s
user0m0.496s
sys 0m0.088s
Time when kdialog was run and first attempt to click Cancel.
dbus-daemon is run for current user:
$ ps wuax | grep dbus-daemon
102868 0.0 0.0 25064 2060 ?Ss 13:41 0:00 dbus-daemon
--system --fork --activation=upstart
kenorb1955 0.0 0.0 26476 2400 ?Ss 13:42 0:01
//bin/dbus-daemon --fork --print-pid 5 --print-address 7
[Bug 1053910] Re: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem
This bug was fixed in the package muon - 1.4.1-0ubuntu1 --- muon (1.4.1-0ubuntu1) quantal; urgency=low * New upstream bugfix release (LP: #1053910) -- Jonathan Thomas echidna...@kubuntu.org Sat, 29 Sep 2012 15:08:07 -0400 ** Changed in: muon (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1053910 Title: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1053910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053910] Re: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem
** Branch linked: lp:ubuntu/muon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1053910 Title: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1053910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053910] Re: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem
I've committed a fix upstream for 1.4.1: http://commits.kde.org/muon/c67667633ada69b6feee0216de4da03de963a82c ** No longer affects: dbus (Ubuntu) ** No longer affects: kde-baseapps (Ubuntu) ** Changed in: muon (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to muon in Ubuntu. https://bugs.launchpad.net/bugs/1053910 Title: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1053910/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1053910] Re: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem
I can confirm, that this is caused by muon-notifier service. After renaming /usr/share/kde4/services/kded/muon-notifier.desktop file and restarting kdeinit4 everything works fine and above two bugs are not reproducible. $ dpkg -l | grep muon-notifier ii muon-notifier 1.3.1-0ubuntu2 update notifier for KDE ** Package changed: kde-baseapps (Ubuntu) = muon (Ubuntu) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to muon in Ubuntu. https://bugs.launchpad.net/bugs/1053910 Title: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1053910/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1053910] Re: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem
Killing the following process solve the problem: kenorb 11328 0.0 0.3 131788 12392 ?S13:55 0:00 /usr/bin/python /usr/share/kde4/apps/muon-notifier/releasechecker -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to muon in Ubuntu. https://bugs.launchpad.net/bugs/1053910 Title: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1053910/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1053910] Re: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem
When running it manually again using the same command line, I've this error: /usr/bin/python /usr/share/kde4/apps/muon-notifier/releasechecker Unhandled exception in thread started by bound method MetaReleaseCore.download of UpdateManager.Core.MetaRelease.MetaReleaseCore object at 0x228f9d0 Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/UpdateManager/Core/MetaRelease.py, line 262, in download uri=urllib2.urlopen(req, timeout=20) File /usr/lib/python2.7/urllib2.py, line 126, in urlopen return _opener.open(url, data, timeout) File /usr/lib/python2.7/urllib2.py, line 400, in open response = self._open(req, data) File /usr/lib/python2.7/urllib2.py, line 418, in _open '_open', req) File /usr/lib/python2.7/urllib2.py, line 378, in _call_chain result = func(*args) ... File /usr/lib/python2.7/socket.py, line 447, in readline data = self._sock.recv(self._rbufsize) socket.error: [Errno 104] Connection reset by peer Probably, because I'm behind the proxy. ** Bug watch added: KDE Bug Tracking System #307049 https://bugs.kde.org/show_bug.cgi?id=307049 ** Also affects: muon via https://bugs.kde.org/show_bug.cgi?id=307049 Importance: Unknown Status: Unknown ** Also affects: kde-baseapps (Ubuntu) Importance: Undecided Status: New ** Also affects: dbus (Ubuntu) Importance: Undecided Status: New ** Bug watch added: freedesktop.org Bugzilla #55136 https://bugs.freedesktop.org/show_bug.cgi?id=55136 ** Also affects: dbus via https://bugs.freedesktop.org/show_bug.cgi?id=55136 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to muon in Ubuntu. https://bugs.launchpad.net/bugs/1053910 Title: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1053910/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1053910] Re: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem
I've installed d-feet and it gives me some interesting results, like (each of them repeating plenty of times): $ d-fee ERROR: Some clever service is trying to be cute and has the same signal name in the same interface ERROR: Some clever service is trying to be cute and has the same method name in the same interface ERROR:dbus.proxies:Introspect error on :1.117:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ERROR:dbus.proxies:Introspect error on org.freedesktop.Notifications:/App: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ERROR:dbus.proxies:Introspect error on org.kde.DeviceNotifications:/DataEngine: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ERROR:dbus.proxies:Introspect error on org.freedesktop.Notifications:/KBookmarkManager: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ERROR:dbus.proxies:Introspect error on org.kde.DeviceNotifications:/KIO: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ERROR:dbus.proxies:Introspect error on org.kde.StatusNotifierHost-2186:/MainApplication: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ERROR:dbus.proxies:Introspect error on org.kde.plasma-desktop:/kickoff: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ERROR:dbus.proxies:Introspect error on :1.129:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownObject: No such object path '/' org.freedesktop.DBus.Error.UnknownObject: No such object path '/' Not sure if it's related somehow. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-baseapps in Ubuntu. https://bugs.launchpad.net/bugs/1053910 Title: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-baseapps/+bug/1053910/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1053910] Re: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem
** Tags added: dbus -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-baseapps in Ubuntu. https://bugs.launchpad.net/bugs/1053910 Title: My plasma-desktop is critically sluggish, panel and kdialog reacts after few minutes because of dbus Timeout problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-baseapps/+bug/1053910/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
