https://bugs.kde.org/show_bug.cgi?id=359611
David Edmundson changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=359611
Evstifeev Roman changed:
What|Removed |Added
CC||someuniquen...@gmail.com
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=359611
Simon Andric changed:
What|Removed |Added
CC||simonandr...@gmail.com
--
You are receiving thi
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #41 from Martin Kyral ---
Are the blocking calls in the device manager widget going to be fixed, too? I
sometimes mount nfs drive and when I'm out of the connection and need to
restart plasma (or plasma crashes), it won't come up because of
https://bugs.kde.org/show_bug.cgi?id=359611
Stefan Schmid changed:
What|Removed |Added
CC||schmidi...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #40 from David Edmundson ---
Git commit cc5ee1a8495aaf126abf1e7c7d3163ea5813d279 by David Edmundson.
Committed on 27/03/2016 at 16:22.
Pushed by davidedmundson into branch 'master'.
Make one more DBus call async
Calling kded in a blocking
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #39 from Eugene Shalygin
---
Oh, David, I'm so sorry! Indeed, there was one patch (commit
5e9c9ff09cc88448d41d9043ee156a5be1a9d880) on top of master branch.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #38 from David Edmundson ---
Or your kded is super old and you don't have
827bad8a7db80ae0c02efa0eeea4bb4d00765316
which came in for v5.18.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #37 from David Edmundson ---
That trace doesn't make any sense.
#4 0x7f7e909b13e1 in QMetaObject::invokeMethod(QObject*, char const*,
#5 0x7f7e9267dbfe in Kded::messageFilter(QDBusMessage const&) () from
target:/usr/lib64/libkdeini
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #36 from Eugene Shalygin
---
David, KDed log is in the bottom part of the comment #33
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #35 from Eugene Shalygin
---
And this one is from Dolphin when I invoke "Delete" for the first time after
Dolphin launch:
(gdb) thread apply all bt
Thread 5 (Thread 0x7fffd1733700 (LWP 3510)):
#0 0x7fffeeb3a358 in pthread_cond_timedw
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #34 from David Edmundson ---
I'll make this non blocking as it really doesn't need to be, but it's not the
real problem.
Whilst we're in that state, can you get the same trace on kded5 so we can see
where that's stuck.
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #33 from Eugene Shalygin
---
Device Notifier, click on a "Open with file manager"
(gdb) thread apply all bt
Thread 9 (Thread 0x7f9f6251b700 (LWP 31685)):
#0 0x7f9f71f71d3d in poll () from /lib64/libc.so.6
#1 0x7f9f75f81ac2 in _x
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #32 from David Edmundson ---
If anyone still has lockups *with the patches applied*
please attach new backtraces of the frozen processes.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #31 from Eugene Shalygin
---
Thank you, Rex! After applying the patch from
https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/xorg-server&id=bb37fae55e67f14bc491ca6bcccde3907f73b21c
the whole UI does not freeze any
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #30 from Rex Dieter ---
If any of you experiencing recent freezing are using xorg-x11-server-1.18.2 ,
it's a bug/regression there (not qt or plasma related), see also:
http://bugs.freedesktop.org/show_bug.cgi?id=94515
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #29 from Eugene Shalygin
---
Caught the first hang after an X restart, and X ate 16 GiB of memory.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #28 from Eugene Shalygin
---
After each of these hangs X server eats a lot of memory. There were about ten
of them on my system after the last reboot, and now X server takes 48.5 GiB
VIRT and 28.9 GiB RES. This is with the "fix" from QTBUG
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #27 from Eugene Shalygin
---
Even worse: if the systray is not touched for a few minutes, and then I try to
interact with any systray element except of palsma-nm, it hangs my desktop
completely.
P.S. How it is possible that Qt DBus module
https://bugs.kde.org/show_bug.cgi?id=359611
opensuse.lietuviu.ka...@gmail.com changed:
What|Removed |Added
CC||opensuse.lietuviu.kalba@gma
https://bugs.kde.org/show_bug.cgi?id=359611
Jonathan Riddell changed:
What|Removed |Added
CC||j...@jriddell.org
Severity|normal
https://bugs.kde.org/show_bug.cgi?id=359611
Alexander Potashev changed:
What|Removed |Added
CC||aspotas...@gmail.com
--- Comment #22 from
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #25 from Martin Kyral ---
(In reply to David Edmundson from comment #24)
> There is a patch for Qt. See email on KDE packagers ml.
>
> If you use a distro without that patch, your distro sucks and you should
> change.
Thanks, I updated qt
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #26 from Eugene Shalygin
---
I've applied three patches to Qt 5.6.0 (QTBUG-51648, QTBUG-51649, QTBUG-51676).
Yet the problem is not completely solved. Plasmashell binary starts without
delays, but each first interaction with either Plasma s
https://bugs.kde.org/show_bug.cgi?id=359611
Martin Kyral changed:
What|Removed |Added
CC||sine.nom...@centrum.cz
--- Comment #23 from Mart
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #24 from David Edmundson ---
There is a patch for Qt. See email on KDE packagers ml.
If you use a distro without that patch, your distro sucks and you should
change.
--
You are receiving this mail because:
You are watching all bug changes
https://bugs.kde.org/show_bug.cgi?id=359611
Hrvoje Senjan changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=359611
Arthur Țițeică changed:
What|Removed |Added
CC||arthur.tite...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #21 from Eugene Shalygin
---
Confirm that reverting commit a1ba281a26d065d2e901b3a947a8517ec5790504 from
qtbase helps.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359611
Rex Dieter changed:
What|Removed |Added
CC||rdie...@math.unl.edu
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #20 from David Edmundson ---
Git commit 49440a7ce0623d1bc8aca459eaed35612d384cfd by David Edmundson.
Committed on 29/02/2016 at 11:09.
Pushed by davidedmundson into branch 'master'.
Avoid blocking DBus calls in SNI startup
All autogenerate
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #19 from David Faure ---
The last bt is very informative:
* the main thread is in a BlockingQueuedConnection signal emission, the signal
is signalNeedsConnecting(), and it's handled by the dbus thread.
* the dbus thread is in QDBusConnectio
https://bugs.kde.org/show_bug.cgi?id=359611
d...@kaosx.us changed:
What|Removed |Added
CC||d...@kaosx.us
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #18 from Hrvoje Senjan ---
With commit a1ba281a26d065d2e901b3a947a8517ec5790504 from qtbase reverted &&
5e9c9ff09cc88448d41d9043ee156a5be1a9d880 from kded reverted, lock-ups no longer
happens. I'm not sure whether both are needed, or just re
https://bugs.kde.org/show_bug.cgi?id=359611
Luca Beltrame changed:
What|Removed |Added
CC||fa...@kde.org
--- Comment #17 from Luca Beltram
https://bugs.kde.org/show_bug.cgi?id=359611
Luca Beltrame changed:
What|Removed |Added
CC||lbeltr...@kde.org
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=359611
Raymond Wooninck changed:
What|Removed |Added
CC||tittiatc...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=359611
David Rosca changed:
What|Removed |Added
CC||now...@gmail.com
--- Comment #16 from David Rosca
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #15 from Hrvoje Senjan ---
Created attachment 97539
--> https://bugs.kde.org/attachment.cgi?id=97539&action=edit
ANother one with libQt5Core debuginfo
and after running
unset XDG_CURRENT_DESKTOP
export KDE_SESSION_VERSION=5
export K
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #14 from Hrvoje Senjan ---
Created attachment 97538
--> https://bugs.kde.org/attachment.cgi?id=97538&action=edit
thread apply all bt on locked up kded5
This is after disabling touchpad and khotkeys kdeds
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=359611
Hrvoje Senjan changed:
What|Removed |Added
CC||hrvoje.sen...@gmail.com
--- Comment #13 from Hr
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #12 from Eugene Shalygin
---
I was wrong: there are no deadlocks in kded with Qt 5.5.1. Will bisecting Qt
help?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #11 from Eugene Shalygin
---
Ah, kde-FRAMEWORKS-devel... That change is included in my Qt build.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #10 from David Edmundson ---
https://www.mail-archive.com/kde-frameworks-devel@kde.org/msg30345.html
in your backtraces can you be sure to include all the threads. (upload as
attachments if need be)
We're hitting a lock, so we need to know
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #9 from Eugene Shalygin ---
(In reply to Eugene Shalygin from comment #8)
> I'm not a member of kde-devel and the archive is private (why?).
Ups.. mail.kde.org says that archives are private, while lists.kde.org shows
archives. But I did no
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #8 from Eugene Shalygin ---
I'm not a member of kde-devel and the archive is private (why?). Qt was updated
just now. And I had the same problem with 5.5.1.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359611
David Edmundson changed:
What|Removed |Added
Status|NEEDSINFO |CONFIRMED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #6 from Eugene Shalygin ---
BTW, it is with Qt from branch "5.6"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #5 from Eugene Shalygin ---
I removed khotkeys package, restarted kded5 and when it stops loading, the
backtrace is:
#0 0x7571dfaf in pthread_cond_wait () from /lib64/libpthread.so.0
#1 0x75d55f1a in QWaitCondition::wait(Q
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #4 from Eugene Shalygin ---
backtrace from kded5, kglobalaccel compiled with debug information :
#0 0x7571dfaf in pthread_cond_wait () from /lib64/libpthread.so.0
#1 0x75d55f1a in QWaitCondition::wait(QMutex*, unsigned lon
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #3 from Eugene Shalygin ---
The same happens also in another user account after cleaning its ${HOME}
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359611
--- Comment #2 from Eugene Shalygin ---
Here it is, please:
(gdb) thread apply all bt
Thread 7 (Thread 0x7fd1d4531700 (LWP 8641)):
#0 0x7fd1ed58dfaf in pthread_cond_wait () from /lib64/libpthread.so.0
#1 0x7fd1efcacf1a in QWaitCondition::wai
https://bugs.kde.org/show_bug.cgi?id=359611
David Edmundson changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|UNCONFIRMED
53 matches
Mail list logo
