Launchpad has imported 28 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=354230.
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 2015-10-22T21:26:52+00:00 Quesseb wrote: Hello i just upgraded an Kubuntu 15.04 to 15.10 today. After ssdm login, plasma starts launching, I can see wallpaper and desktop icons, but taskbar is empty. Nothing can be done during 30 first seconds with mouse or keyboard in this tty. During this time, in another tty1 I can see cpu at 3% only... I reproduce the problem at every startup and at every login with my usual login or with a newly created account. Bootchart shows a python3 process sleeping a long time and then plasmashell finishes to load.. How to identify this process or to debug it? Reproducible: Always I can attach bootchart.svg if necessary Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/0 ------------------------------------------------------------------------ On 2015-10-22T21:28:02+00:00 U26 wrote: I can attach bootchart.svg if necessary yes please. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/1 ------------------------------------------------------------------------ On 2015-10-23T16:20:17+00:00 U26 wrote: Marking as needsinfo till we get the chart, as till then this doesn't contain anything to go on Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/3 ------------------------------------------------------------------------ On 2015-10-23T19:37:14+00:00 Quesseb wrote: Created attachment 95094 bootchart svg python3 from 10th to 60th second on boot Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/6 ------------------------------------------------------------------------ On 2015-10-24T14:35:43+00:00 U26 wrote: thanks Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/12 ------------------------------------------------------------------------ On 2015-10-24T14:36:09+00:00 U26 wrote: *** Bug 354304 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/13 ------------------------------------------------------------------------ On 2015-10-24T15:00:08+00:00 U26 wrote: No idea what that python process is. It's not anything from Plasma. Can you try and find out? also a time this long with no CPU activity is probably DBus blocking - we'll be waiting for a reply from something that isn't answering. Any chance you can add "dbus-monitor > ~/my-dbus-log" to your startkde file Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/14 ------------------------------------------------------------------------ On 2015-10-24T15:06:10+00:00 amichair wrote: Same problem here. Just upgraded today, panel takes a minute to be operational. Beore that it's kind of half-drawn, with some task buttons there, some icon frames, and many icons just missing. After a long while it all just works. This happens after reboot, but also saw it at other times (possibly after monitor resumes from power savings mode? not sure). At the moment I have a completely frozen panel, not sure if it's related or not. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/15 ------------------------------------------------------------------------ On 2015-10-24T15:17:38+00:00 amichair wrote: btw I just found out that it happens consistently every time I 'killall plasmashell && plasmashell'. No need to reboot to recreate. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/16 ------------------------------------------------------------------------ On 2015-10-24T15:25:04+00:00 amichair wrote: Also, using this technique it takes 53 seconds from running the command plasmashell until it's operational. Maybe the first 3 seconds is regular startup, then 50 second timeout on something? also, in the terminal (where I run plasmashell) the last thing logged before it hangs is: unversioned plugin detected, may result in instability org.kde.plasma.pulseaudio: state callback and the first thing after it resumes 50 seconds later is: plasma-nm: Failed to enumerate BT adapters I hope this helps. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/17 ------------------------------------------------------------------------ On 2015-10-24T15:47:24+00:00 U26 wrote: >plasma-nm: Failed to enumerate BT adapters That seems like it could be it. can you run dbus-monitor (or ideally bustle if you can install that) and launch plasmashell Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/18 ------------------------------------------------------------------------ On 2015-10-24T16:44:39+00:00 amichair wrote: If I understand the output of bustle correctly, there's nothing obviously wrong here. There's one line at 2928 which is a method return value from PowerManagement.PolicyAgent.ListInhibitions, and the next line after it is at 53016 (that's the 50 seconds later) which is a request for NetworkManagement Introspect. There don't appear to be any request/response crossing that line, so the time appears to be spent somewhere else, not stuck on a dbus transaction. The method durations statistics pane shows all durations at the millisecond level. Is that the kind of thing you're looking for? Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/19 ------------------------------------------------------------------------ On 2015-10-24T17:53:12+00:00 Pelzlurch wrote: It's definitely a BT-Problem. Putting in a BT-USB-Stick the desktop starts much faster. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/21 ------------------------------------------------------------------------ On 2015-10-24T18:48:07+00:00 U26 wrote: Can you see if: - any of the lines in bustle were red if so, the full output of that line. - screenshots of the statistics page Message frequencies and Method Durations Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/22 ------------------------------------------------------------------------ On 2015-10-24T18:58:47+00:00 U26 wrote: oh bother, of couse you won't see anything bustle is monitoring the session bus by default. network manager is on the system bus I don't think bustle has a UI for it, but bustle-pcap --system somefile then open it in bustle Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/23 ------------------------------------------------------------------------ On 2015-10-24T18:59:05+00:00 amichair wrote: Created attachment 95108 bustle output when panel hangs I attached the bustle output. It starts just before starting plasmashell, and ends when it's all good. Nothing else going on in between. You can see the hang in the entries at the very bottom. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/24 ------------------------------------------------------------------------ On 2015-10-24T19:17:51+00:00 U26 wrote: Thanks, in case you missed it I posted a comment 1 minute before you uploaded this realising I need something else. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/25 ------------------------------------------------------------------------ On 2015-10-24T20:41:15+00:00 amichair wrote: Created attachment 95113 bustle output (pcap,system) when panel hangs Thanks, I did miss that comment. Here it is. Quite short. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/29 ------------------------------------------------------------------------ On 2015-10-24T21:05:39+00:00 U26 wrote: heh, that wasn't very useful. Has nothing from network manager or bluetooth which is where we think we want to be looking. The interface must have sniffing turned off. Does sudo bustle-pcap include anything better? Altnernate approach is we go from the other side and run "gdb plasma" then after 10s (where everything else should should be stopped) type "control+c" "bt" and we find where plasma is blocked and waiting If that's a bit much, I'll install Kubuntu 15.10 in a virtual machine which won't have bluetooth - and poke it there. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/30 ------------------------------------------------------------------------ On 2015-10-24T21:26:35+00:00 amichair wrote: #0 0x00007ffff25d38dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007fffef11472f in () at /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x00007fffef1133ae in () at /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x00007fffef0fc014 in () at /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x00007fffef0fcacc in () at /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x00007fffef0fcfca in dbus_connection_send_with_reply_and_block () at /lib/x86_64-linux-gnu/libdbus-1.so.3 #6 0x00007ffff7f62ad0 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x00007ffff7f64316 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x00007ffff7f70dcd in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x00007ffff7f70f15 in QDBusInterface::QDBusInterface(QString const&, QString const&, QString const&, QDBusConnection const&, QObject*) () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x00007fff36ed46c5 in Handler::isBtEnabled() () at /usr/lib/x86_64-linux-gnu/libplasmanm_internal.so #11 0x00007fff36ed5cb4 in Handler::Handler(QObject*) () at /usr/lib/x86_64-linux-gnu/libplasmanm_internal.so #12 0x00007fff3712c780 in () at /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/networkmanagement/libplasmanm_qmlplugins.so #13 0x00007ffff54816cb in QQmlType::create() const () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x00007ffff54e58fd in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x00007ffff54e7a8d in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x00007ffff54e7e2b in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x00007ffff54e459d in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #18 0x00007ffff54e4f81 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #19 0x00007ffff54e60b4 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #20 0x00007ffff546eec7 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x00007ffff546f7b4 in QQmlIncubationController::incubateFor(int) () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #22 0x00007ffff61577ac in () at /usr/lib/x86_64-linux-gnu/libKF5Declarative.so.5 #23 0x00007ffff546f5c9 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x00007ffff546ae0c in QQmlComponent::create(QQmlIncubator&, QQmlContext*, QQmlContext*) () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #25 0x00007ffff6147845 in KDeclarative::QmlObject::completeInitialization(QHash<QString, QVariant> const&) () at /usr/lib/x86_64-linux-gnu/libKF5Declarative.so.5 #26 0x00007ffff799f658 in PlasmaQuick::AppletQuickItem::init() () at /usr/lib/x86_64-linux-gnu/libKF5PlasmaQuick.so.5 #27 0x00007fffcae665dc in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #28 0x00007fffcae65bc9 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #29 0x00007ffff2ed7651 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x00007ffff5ef410b in QQuickItem::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #31 0x00007fffcae66896 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #32 0x00007ffff3983b8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x00007ffff3989230 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #34 0x00007ffff2ea5f1b in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x00007ffff2ea8057 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x00007ffff2efce73 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x00007fffef380ff7 in g_main_context_dispatch (context=0x7fffdc0016f0) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3154 #38 0x00007fffef380ff7 in g_main_context_dispatch (context=context@entry=0x7fffdc0016f0) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3769 #39 0x00007fffef381250 in g_main_context_iterate (context=context@entry=0x7fffdc0016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3840 #40 0x00007fffef3812fc in g_main_context_iteration (context=0x7fffdc0016f0, may_block=1) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3901 #41 0x00007ffff2efd27f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #42 0x00007ffff2ea375a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #43 0x00007ffff2eab2cc in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #44 0x00000000004322c3 in main () Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/31 ------------------------------------------------------------------------ On 2015-10-24T21:34:34+00:00 U26 wrote: We can see we're making some blocking calls to BlueZ here. QDBusInterface managerIface("org.bluez", "/", "org.freedesktop.DBus.ObjectManager", QDBusConnection::systemBus(), this); is blocking QDBusReply<QMap<QDBusObjectPath, NMVariantMapMap> > reply = managerIface.call("GetManagedObjects"); is blocking QDBusInterface adapterIface("org.bluez", objPath, "org.bluez.Adapter1", QDBusConnection::systemBus(), this); is blocking and finally const bool adapterEnabled = adapterIface.property("Powered").toBool(); Arguably bluez shouldn't be taking so long to respond, but I think we can turn this async. We need to handle an adaptor enabling at runtime regardless so we need to handle it changing in handler.cpp anyway Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/32 ------------------------------------------------------------------------ On 2015-10-25T06:42:07+00:00 Jgrulich wrote: *** Bug 354249 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/33 ------------------------------------------------------------------------ On 2015-10-25T16:37:21+00:00 Jgrulich wrote: Git commit f3e940d49574b3d464b8d7118cdced136283579b by Jan Grulich. Committed on 25/10/2015 at 16:37. Pushed by grulich into branch 'master'. Make all bluez calls asynchronous REVIEW:125785 M +62 -55 libs/handler.cpp M +3 -4 libs/handler.h http://commits.kde.org/plasma- nm/f3e940d49574b3d464b8d7118cdced136283579b Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/34 ------------------------------------------------------------------------ On 2015-10-25T16:38:23+00:00 Jgrulich wrote: Git commit 48a45ebad0e1d5ecc023a9e8866a95d47c76790f by Jan Grulich. Committed on 25/10/2015 at 16:38. Pushed by grulich into branch 'Plasma/5.4'. Make all bluez calls asynchronous REVIEW:125785 M +62 -55 libs/handler.cpp M +3 -4 libs/handler.h http://commits.kde.org/plasma- nm/48a45ebad0e1d5ecc023a9e8866a95d47c76790f Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/35 ------------------------------------------------------------------------ On 2015-10-25T16:44:58+00:00 Jgrulich wrote: Can someone please test the fix? I wasn't able to reproduce this issue even without this fix so we need someone else to confirm that making bluez calls asynchronous helps. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/36 ------------------------------------------------------------------------ On 2015-10-25T19:51:59+00:00 amichair wrote: Is there a simple way to test it without modifying my system? Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/37 ------------------------------------------------------------------------ On 2015-10-26T07:35:13+00:00 Jgrulich wrote: Unfortunately no, you would need to compile plasma-nm or if you know how to make deb packages then you need just download the patch and make a new package. Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/38 ------------------------------------------------------------------------ On 2015-10-26T11:29:53+00:00 Jgrulich wrote: *** Bug 354396 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma- nm/+bug/1509334/comments/40 ** Changed in: plasma-nm Status: Unknown => Fix Released ** Changed in: plasma-nm Importance: Unknown => Medium -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-nm in Ubuntu. https://bugs.launchpad.net/bugs/1509334 Title: KDE/Plasma very slow to launch (Kubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/plasma-nm/+bug/1509334/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
