[plasmashell] [Bug 366146] Plasma crashes when trying to add second panel
https://bugs.kde.org/show_bug.cgi?id=366146 --- Comment #4 from Pulfer--- (In reply to David Edmundson from comment #3) > Do you have any custom plasmoids in the default Rosa panel? There's only one custom plasmoid there: https://git.reviewboard.kde.org/r/127651/ Here's our layout.js: https://abf.rosalinux.ru/import/plasma5-config-fresh/blob/rosa2014.1/default-panel-layout.js > This is caused by some plasmoid having some looping code. Looks like it's caused by system tray plasmoid. Without it adding second panel works fine. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 362175] Can't create pppoe connection using KNetworkManager
https://bugs.kde.org/show_bug.cgi?id=362175 Pulferchanged: What|Removed |Added CC||pul...@list.ru --- Comment #3 from Pulfer --- (In reply to Lamarque V. Souza from comment #2) > Git commit c2be0336226cf27263ed234f69cddd3b5214c267 by Lamarque V. Souza. > Committed on 24/04/2016 at 13:23. > Pushed by lvsouza into branch 'Plasma/5.6'. > > Fix data validation when creating new pppoe connections. > FIXED-IN: 5.6.4 Looks like this commit wasn't merged to master back then. So it didn't get into Plasma 5.7 branch. And the bug still exists in Plasma NM 5.7.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366146] Plasma crashes when trying to add second panel
https://bugs.kde.org/show_bug.cgi?id=366146 --- Comment #2 from Pulfer--- This BT should be more helpful (I installed more debuginfo packages): --- #0 0xb77a5be0 in __kernel_vsyscall () #1 0xb4e34296 in nanosleep () from /lib/i686/libc.so.6 #2 0xb4e3404e in sleep () from /lib/i686/libc.so.6 #3 0xb778123e in ?? () from /usr/lib/libKF5Crash.so.5 #4 0xb77816ce in KCrash::defaultCrashHandler(int) () from /usr/lib/libKF5Crash.so.5 #5 #6 0xa6162152 in QVector ::reallocData (this=0xb5d85d8, asize=84021, aalloc=131068, options=...) at /usr/include/qt5/QtCore/qvector.h:540 #7 0xa61622ba in QVector ::append (this=0xb5d85d8, t=@0xbf386354: 0xb5d86c0) at /usr/include/qt5/QtCore/qvector.h:633 #8 0xa615c897 in operator<< (t=, this=) at /usr/include/qt5/QtCore/qvector.h:273 #9 QQuickGridLayoutBase::invalidate (this=0xb5d83c0, childItem=0xb5d86c0) at qquicklinearlayout.cpp:392 #10 0xa6159cc7 in QQuickLayout::invalidateSenderItem (this=0xb5d83c0) at qquicklayout.cpp:794 #11 0xa6164734 in QQuickLayout::qt_static_metacall (_o=0xb5d83c0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf3863d8) at .moc/moc_qquicklayout_p.cpp:69 #12 0xb526c4c8 in QMetaObject::activate (sender=0xb5d86c0, signalOffset=3, local_signal_index=24, argv=0x0) at kernel/qobject.cpp:3730 #13 0xb526ce9d in QMetaObject::activate (sender=0xb5d86c0, m=0xb705559c , local_signal_index=24, argv=0x0) at kernel/qobject.cpp:3595 #14 0xb6d682e2 in QQuickItem::implicitWidthChanged (this=0xb5d86c0) at .moc/moc_qquickitem.cpp:1148 #15 0xb6d684a9 in QQuickItemPrivate::implicitWidthChanged (this=0xb5d86e0) at items/qquickitem.cpp:6312 #16 0xb6d6d052 in QQuickItem::setImplicitSize (this=0xb5d86c0, w=237, h=42) at items/qquickitem.cpp:6531 #17 0xa615c841 in QQuickGridLayoutBase::invalidate (this=0xb5d86c0, childItem=0x0) at qquicklinearlayout.cpp:426 #18 0xa615bafe in QQuickGridLayoutBase::updateLayoutItems (this=0xb5d86c0) at qquicklinearlayout.cpp:444 #19 0xa615c86d in QQuickGridLayoutBase::invalidate (this=0xb5d86c0, childItem=0xb5d8970) at qquicklinearlayout.cpp:402 #20 0xa615c44a in QQuickGridLayoutBase::rearrange (this=0xb5d86c0, size=...) at qquicklinearlayout.cpp:532 #21 0xa615a9eb in QQuickLayout::geometryChanged (this=0xb5d86c0, newGeometry=..., oldGeometry=...) at qquicklayout.cpp:785 #22 0xb6d6d224 in QQuickItem::setSize (this=0xb5d86c0, size=...) at items/qquickitem.cpp:6591 #23 0xa615cd22 in QQuickGridLayoutItem::setGeometry (this=0xb5ee278, rect=...) at qquickgridlayoutengine_p.h:117 #24 0xb57ddb5f in QGridLayoutEngine::setGeometries (this=0xb5d84b4, contentsGeometry=..., styleInfo=0xb5d7ac0) at util/qgridlayoutengine.cpp:1034 #25 0xa615c3e8 in QQuickGridLayoutBase::rearrange (this=0xb5d83c0, size=...) at qquicklinearlayout.cpp:528 #26 0xa615a9eb in QQuickLayout::geometryChanged (this=0xb5d83c0, newGeometry=..., oldGeometry=...) at qquicklayout.cpp:785 #27 0xb6d6cf04 in QQuickItem::setImplicitSize (this=0xb5d83c0, w=234, h=35) at items/qquickitem.cpp:6554 #28 0xa615c841 in QQuickGridLayoutBase::invalidate (this=0xb5d83c0, childItem=0xb5d86c0) at qquicklinearlayout.cpp:426 #29 0xa615c44a in QQuickGridLayoutBase::rearrange (this=0xb5d83c0, size=...) at qquicklinearlayout.cpp:532 #30 0xa615a9eb in QQuickLayout::geometryChanged (this=0xb5d83c0, newGeometry=..., oldGeometry=...) at qquicklayout.cpp:785 #31 0xb6d6cf04 in QQuickItem::setImplicitSize (this=0xb5d83c0, w=237, h=42) at items/qquickitem.cpp:6554 #32 0xa615c841 in QQuickGridLayoutBase::invalidate (this=0xb5d83c0, childItem=0xb5d86c0) at qquicklinearlayout.cpp:426 #33 0xa615c44a in QQuickGridLayoutBase::rearrange (this=0xb5d83c0, size=...) at qquicklinearlayout.cpp:532 #34 0xa615a9eb in QQuickLayout::geometryChanged (this=0xb5d83c0, newGeometry=..., oldGeometry=...) at qquicklayout.cpp:785 #35 0xb6d6cf04 in QQuickItem::setImplicitSize (this=0xb5d83c0, w=234, h=35) at items/qquickitem.cpp:6554 #36 0xa615c841 in QQuickGridLayoutBase::invalidate (this=0xb5d83c0, childItem=0xb5d86c0) at qquicklinearlayout.cpp:426 #37 0xa615c44a in QQuickGridLayoutBase::rearrange (this=0xb5d83c0, size=...) at qquicklinearlayout.cpp:532 #38 0xa615a9eb in QQuickLayout::geometryChanged (this=0xb5d83c0, newGeometry=..., oldGeometry=...) at qquicklayout.cpp:785 #39 0xb6d6cf04 in QQuickItem::setImplicitSize (this=0xb5d83c0, w=237, h=42) at items/qquickitem.cpp:6554 #40 0xa615c841 in QQuickGridLayoutBase::invalidate (this=0xb5d83c0, childItem=0xb5d86c0) at qquicklinearlayout.cpp:426 #41 0xa615c44a in QQuickGridLayoutBase::rearrange (this=0xb5d83c0, size=...) at qquicklinearlayout.cpp:532 #42 0xa615a9eb in QQuickLayout::geometryChanged (this=0xb5d83c0, newGeometry=..., oldGeometry=...) at qquicklayout.cpp:785 #43 0xb6d6cf04 in QQuickItem::setImplicitSize (this=0xb5d83c0, w=234, h=35) at items/qquickitem.cpp:6554 #44 0xa615c841 in QQuickGridLayoutBase::invalidate (this=0xb5d83c0, childItem=0xb5d86c0) at
[plasmashell] [Bug 366146] Plasma crashes when trying to add second panel
https://bugs.kde.org/show_bug.cgi?id=366146 Pulferchanged: What|Removed |Added CC||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366146] Plasma crashes when trying to add second panel
https://bugs.kde.org/show_bug.cgi?id=366146 --- Comment #1 from Pulfer--- BT seems to loop forever until it eats all system memory. Maybe it's a Qt 5.6.1 bug and Plasma only triggers it. --- #0 0xb7745be0 in __kernel_vsyscall () #1 0xb4dd4296 in nanosleep () from /lib/i686/libc.so.6 #2 0xb4dd404e in sleep () from /lib/i686/libc.so.6 #3 0xb772123e in ?? () from /usr/lib/libKF5Crash.so.5 #4 0xb77216ce in KCrash::defaultCrashHandler(int) () from /usr/lib/libKF5Crash.so.5 #5 #6 0xa6107152 in QVector ::reallocData (this=0xa4656c8, asize=84213, aalloc=131068, options=...) at /usr/include/qt5/QtCore/qvector.h:540 #7 0xa61072ba in QVector ::append (this=0xa4656c8, t=@0xbf575014: 0xa4657c8) at /usr/include/qt5/QtCore/qvector.h:633 #8 0xa6101897 in operator<< (t=, this=) at /usr/include/qt5/QtCore/qvector.h:273 #9 QQuickGridLayoutBase::invalidate (this=0xa4654b0, childItem=0xa4657c8) at qquicklinearlayout.cpp:392 #10 0xa60fecc7 in QQuickLayout::invalidateSenderItem (this=0xa4654b0) at qquicklayout.cpp:794 #11 0xa6109734 in QQuickLayout::qt_static_metacall (_o=0xa4654b0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf575098) at .moc/moc_qquicklayout_p.cpp:69 #12 0xb520c4c8 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #13 0xb520ce9d in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQt5Core.so.5 #14 0xb6d082e2 in QQuickItem::implicitWidthChanged() () from /usr/lib/libQt5Quick.so.5 #15 0xb6d084a9 in QQuickItemPrivate::implicitWidthChanged() () from /usr/lib/libQt5Quick.so.5 #16 0xb6d0d052 in QQuickItem::setImplicitSize(double, double) () from /usr/lib/libQt5Quick.so.5 #17 0xa6101841 in QQuickGridLayoutBase::invalidate (this=0xa4657c8, childItem=0x0) at qquicklinearlayout.cpp:426 #18 0xa6100afe in QQuickGridLayoutBase::updateLayoutItems (this=0xa4657c8) at qquicklinearlayout.cpp:444 #19 0xa610186d in QQuickGridLayoutBase::invalidate (this=0xa4657c8, childItem=0xa465ae0) at qquicklinearlayout.cpp:402 #20 0xa610144a in QQuickGridLayoutBase::rearrange (this=0xa4657c8, size=...) at qquicklinearlayout.cpp:532 #21 0xa60ff9eb in QQuickLayout::geometryChanged (this=0xa4657c8, newGeometry=..., oldGeometry=...) at qquicklayout.cpp:785 #22 0xb6d0d224 in QQuickItem::setSize(QSizeF const&) () from /usr/lib/libQt5Quick.so.5 #23 0xa6101d22 in QQuickGridLayoutItem::setGeometry (this=0xa482420, rect=...) at qquickgridlayoutengine_p.h:117 #24 0xb577db5f in QGridLayoutEngine::setGeometries(QRectF const&, QAbstractLayoutStyleInfo const*) () from /usr/lib/libQt5Gui.so.5 #25 0xa61013e8 in QQuickGridLayoutBase::rearrange (this=0xa4654b0, size=...) at qquicklinearlayout.cpp:528 #26 0xa60ff9eb in QQuickLayout::geometryChanged (this=0xa4654b0, newGeometry=..., oldGeometry=...) at qquicklayout.cpp:785 #27 0xb6d0cf04 in QQuickItem::setImplicitSize(double, double) () from /usr/lib/libQt5Quick.so.5 #28 0xa6101841 in QQuickGridLayoutBase::invalidate (this=0xa4654b0, childItem=0xa4657c8) at qquicklinearlayout.cpp:426 #29 0xa610144a in QQuickGridLayoutBase::rearrange (this=0xa4654b0, size=...) at qquicklinearlayout.cpp:532 #30 0xa60ff9eb in QQuickLayout::geometryChanged (this=0xa4654b0, newGeometry=..., oldGeometry=...) at qquicklayout.cpp:785 #31 0xb6d0cf04 in QQuickItem::setImplicitSize(double, double) () from /usr/lib/libQt5Quick.so.5 #32 0xa6101841 in QQuickGridLayoutBase::invalidate (this=0xa4654b0, childItem=0xa4657c8) at qquicklinearlayout.cpp:426 #33 0xa610144a in QQuickGridLayoutBase::rearrange (this=0xa4654b0, size=...) at qquicklinearlayout.cpp:532 #34 0xa60ff9eb in QQuickLayout::geometryChanged (this=0xa4654b0, newGeometry=..., oldGeometry=...) at qquicklayout.cpp:785 #35 0xb6d0cf04 in QQuickItem::setImplicitSize(double, double) () from /usr/lib/libQt5Quick.so.5 #36 0xa6101841 in QQuickGridLayoutBase::invalidate (this=0xa4654b0, childItem=0xa4657c8) at qquicklinearlayout.cpp:426 #37 0xa610144a in QQuickGridLayoutBase::rearrange (this=0xa4654b0, size=...) at qquicklinearlayout.cpp:532 #38 0xa60ff9eb in QQuickLayout::geometryChanged (this=0xa4654b0, newGeometry=..., oldGeometry=...) at qquicklayout.cpp:785 #39 0xb6d0cf04 in QQuickItem::setImplicitSize(double, double) () from /usr/lib/libQt5Quick.so.5 #40 0xa6101841 in QQuickGridLayoutBase::invalidate (this=0xa4654b0, childItem=0xa4657c8) at qquicklinearlayout.cpp:426 #41 0xa610144a in QQuickGridLayoutBase::rearrange (this=0xa4654b0, size=...) at qquicklinearlayout.cpp:532 #42 0xa60ff9eb in QQuickLayout::geometryChanged (this=0xa4654b0, newGeometry=..., oldGeometry=...) at qquicklayout.cpp:785 #43 0xb6d0cf04 in QQuickItem::setImplicitSize(double, double) () from /usr/lib/libQt5Quick.so.5 #44 0xa6101841 in QQuickGridLayoutBase::invalidate (this=0xa4654b0, childItem=0xa4657c8) at qquicklinearlayout.cpp:426 #45 0xa610144a in QQuickGridLayoutBase::rearrange (this=0xa4654b0, size=...) at
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 Pulferchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #22 from Pulfer --- Fixed in upcoming 5.7.3. See more info here: https://phabricator.kde.org/D2283 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366146] New: Plasma crashes when trying to add second panel
https://bugs.kde.org/show_bug.cgi?id=366146 Bug ID: 366146 Summary: Plasma crashes when trying to add second panel Product: plasmashell Version: master Platform: ROSA RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: pul...@list.ru Plasma crashes when trying to add second panel. 1. Download the ISO from here: https://abf.rosalinux.ru/platforms/rosa2014.1/products/137/product_build_lists/15748 2. Install it (or boot in live mode) 3. Try to add second panel Plasma will crash, then restart with second panel added and crash BT info provided. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 --- Comment #21 from Pulfer--- (In reply to Ivan Čukić from comment #20) > > I used these ISOs for testing: > > https://abf.rosalinux.ru/platforms/rosa2014.1/products/137/product_build_lists/15726 > > Is the live session supposed to crash or do I need to install it? (the live > session seems to work for me) Yes, live session supposed to crash. But it's not 100% reproducible. I guess it may depend on boot speed. Marco could reproduce it (see comment 3). I suggest to use this ISO for testing: https://abf.rosalinux.ru/platforms/rosa2014.1/products/137/product_build_lists/15736 This ISO has https://quickgit.kde.org/?p=plasma-workspace.git=commit=214443fdff330629104509de9e1738aadcfe36b6 applied and extra debug output ( https://abf.rosalinux.ru/abondrov/plasma5-workspace/blob/rosa2014.1/plasma-workspace-5.7.2-debug.patch ) turned on. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 --- Comment #19 from Pulfer--- (In reply to Marco Martin from comment #18) > can you try with https://phabricator.kde.org/D2283 (based upon yours) > if reliably fixes the crash for you? I guess it should because there's no "!!! load (containments are empty, m_shell)" line in .xsession-errors (neither for crashed Plasma nor for properly started). So we don't enter "if (containments().isEmpty()) {}" and adding there "currentActivityChanged(m_activityController->currentActivity());" shouldn't change the behaviour of my patch that fixed the crash. Likely there should be another test case for this new line. Something that actually runs the code. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 --- Comment #17 from Pulfer--- (In reply to David Edmundson from comment #16) > Given this patch works round a crash, the reason for the crash presumably is > that loadLayout() creates a containment on an activity then > checkActivities() cleans up any containments are for activities that no > longer exist...but after they've been assinged to views. I guess xsession-errors log with extra debug output (lines starting with "!!!") from https://bugs.kde.org/show_bug.cgi?id=365989#c8 is very helpful to track Plasma loading order. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 --- Comment #15 from Pulfer--- Created attachment 100288 --> https://bugs.kde.org/attachment.cgi?id=100288=edit Patch to fix load order This patch seems to fix the issue. And .xsession-errors with extra debug now looks sane: --- grep .xsession-errors --- !!! setShell (init): "org.kde.plasma.desktop" !!! setShell (theme name): "rosa-fresh" !!! unload (init, m_shell) "org.kde.plasma.desktop" !!! load (init, m_shell): "org.kde.plasma.desktop" !!! checkActivities (status) 2 !!! checkActivities (id) "c01f2662-8731-4a60-8e2b-82cd4efba366" !!! loadDefaultLayout (script) "/usr/share/plasma/shells/org.kde.plasma.desktop/contents/layout.js" !!! ShellCorona screenForContainment: Plasma::Containment(0x9dccb90) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x9dccb90) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x9dccb90) Last screen is -1 !!! insertActivity (id) "94bbf033-08f1-49ca-8f58-d1963a7d6415" !!! insertActivity (plugin) "org.kde.plasma.folder" !!! createContainmentForActivity (activity) "94bbf033-08f1-49ca-8f58-d1963a7d6415" !!! createContainmentForActivity (screenNum) 0 !!! createContainmentForActivity (plugin) "org.kde.plasma.folder" !!! ShellCorona screenForContainment: Plasma::Containment(0x9dccb90) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x9dccb90) Last screen is -1 !!! insertContainment (containment): Plasma::Containment(0x9d7bef0) !!! insertContainment (activity): "94bbf033-08f1-49ca-8f58-d1963a7d6415" !!! insertContainment (screenNum): 0 !!! ShellCorona screenForContainment: Plasma::Containment(0x9dccb90) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x9dccb90) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x9dccb90) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x9dccb90) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x9d7bef0) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x9d7bef0) Last screen is -1 !!! load (containments are NOT empty, m_shell) "org.kde.plasma.desktop" !!! load (containmentType == panel) !!! load (containmentType == desktop) !!! createContainmentForActivity (activity) "94bbf033-08f1-49ca-8f58-d1963a7d6415" !!! createContainmentForActivity (screenNum) 0 --- grep .xsession-errors --- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 --- Comment #14 from Pulfer--- (In reply to Marco Martin from comment #12) > Git commit 214443fdff330629104509de9e1738aadcfe36b6 by Marco Martin. Plasma still crashes with this patch applied: --- grep .xsession-errors --- Plasma Shell startup completed org.kde.plasma: requesting config for "Просмотр папки" [translation: "Folder View"] without a containment! KCrash: Attempting to start /usr/bin/plasmashell from kdeinit KCrash: Application 'plasmashell' crashing... KCrash: Attempting to start /usr/lib/libexec/drkonqi from kdeinit --- grep .xsession-errors --- I'll try to get new backtrace log. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 --- Comment #8 from Pulfer--- Created attachment 100282 --> https://bugs.kde.org/attachment.cgi?id=100282=edit xsessions-errors with more debug output I patched plasma5-worspace to output more debug messages. The patch is https://abf.rosalinux.ru/abondrov/plasma5-workspace/blob/rosa2014.1/plasma-workspace-5.7.2-debug.patch This line looks really surprising: "!!! checkActivities (destroyed activity): "c51bdf4c-5df8-4b04-9cf8-88a446ad2445"" --- grep .xsession-errors --- !!! setShell (init): "org.kde.plasma.desktop" !!! setShell (theme name): "rosa-fresh" !!! unload (init, m_shell) "org.kde.plasma.desktop" !!! load (init, m_shell): "org.kde.plasma.desktop" !!! loadDefaultLayout (script) "/usr/share/plasma/shells/org.kde.plasma.desktop/contents/layout.js" !!! ShellCorona screenForContainment: Plasma::Containment(0x93a3748) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x93a3748) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x93a3748) Last screen is -1 !!! insertActivity (id) "c51bdf4c-5df8-4b04-9cf8-88a446ad2445" !!! insertActivity (plugin) "org.kde.plasma.folder" !!! createContainmentForActivity (activity) "c51bdf4c-5df8-4b04-9cf8-88a446ad2445" !!! createContainmentForActivity (screenNum) 0 !!! createContainmentForActivity (plugin) "org.kde.plasma.folder" !!! ShellCorona screenForContainment: Plasma::Containment(0x93a3748) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x93a3748) Last screen is -1 !!! insertContainment (containment): Plasma::Containment(0x9348618) !!! insertContainment (activity): "c51bdf4c-5df8-4b04-9cf8-88a446ad2445" !!! insertContainment (screenNum): 0 !!! ShellCorona screenForContainment: Plasma::Containment(0x93a3748) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x93a3748) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x93a3748) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x93a3748) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x9348618) Last screen is -1 !!! ShellCorona screenForContainment: Plasma::Containment(0x9348618) Last screen is -1 !!! checkActivities (status) 2 !!! checkActivities (id) "90960718-8ab6-460d-920d-3074a925c813" !!! checkActivities (destroyed activity): "c51bdf4c-5df8-4b04-9cf8-88a446ad2445" !!! load (containments are NOT empty, m_shell) "org.kde.plasma.desktop" !!! load (containmentType == panel) !!! createContainmentForActivity (activity) "c51bdf4c-5df8-4b04-9cf8-88a446ad2445" !!! createContainmentForActivity (screenNum) 0 --- grep .xsession-errors --- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 --- Comment #7 from Pulfer--- (In reply to Pulfer from comment #6) > Looks like in some cases the issue still exists (maybe because D2268). I tried not to apply D2268 but Plasma still crashes on start and there are still 2 "Plasma Shell startup completed" messages in .xsession-errors and "Activity added twice" message. Our QA engineer just reported that after first OS install from 15726 ISO he had Plasma crash and broken default desktop layout. But after second install from the same ISO Plasma didn't crash and desktop layout was properly created. In general this issue looks like some kind of a race condition. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 --- Comment #6 from Pulfer--- Looks like in some cases the issue still exists (maybe because D2268). With plasma-workspace 5.7.2 + fixed (as suggested above) layout.js + backported commits: 1. https://quickgit.kde.org/?p=plasma-workspace.git=commitdiff=f7ef6ee87b8957bebc976b6fc9e0df279cea05f1 2. https://phabricator.kde.org/D2268 Plasma crashes on start, when it tries to create default desktop from template. --- .xsession-errors --- "1" Plasma Shell startup completed Plasma Shell startup completed ... org.kde.plasma: requesting config for "Folder view" without a containment! Activity added twice "81db3eec-48a9-41d5-a967-bb9cba9fba72" () ("/home/vuohi/Desktop/Home.desktop") () log_kioremote: RemoteDirNotify::FilesChanged log_kioremote: RemoteDirNotify::toRemoteURL( QUrl("file:///home/vuohi/Desktop/Home.desktop") ) log_kioremote: result => KUrl() KCrash: Attempting to start /usr/bin/plasmashell from kdeinit KCrash: Application 'plasmashell' crashing... KCrash: Attempting to start /usr/lib/libexec/drkonqi from kdeinit ... --- .xsession-errors --- I used these ISOs for testing: https://abf.rosalinux.ru/platforms/rosa2014.1/products/137/product_build_lists/15726 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 --- Comment #5 from Pulfer--- (In reply to Marco Martin from comment #3) > can you try without the outer loop as in: > ... > this way seems to fix it for me on the live image It seems to fix the issue indeed. Thanx :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 --- Comment #2 from Pulfer--- (In reply to Pulfer from comment #0) > But in fact it only makes things worse (if backported to 5.7.2 package) - > Plasma Shell locks on load, there's only black screen without desktop and > panel. Well, it's not a deadlock. It's possible to run commands via Alt+F2. Just no desktop, panel etc. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 --- Comment #1 from Pulfer--- https://phabricator.kde.org/D2268 seems to fix Plasma Shell deadlock on start. But still loading default layout is broken: --- .xsession-errors --- ... Setting default Containment plugin: "org.kde.plasma.folder" Failed to create and switch to the activity "1" Plasma Shell startup completed ... --- .xsession-errors --- --- layout.js --- loadTemplate("org.kde.plasma.desktop.defaultPanel") for (var i = 0; i < screenCount; ++i) { var id = createActivity("Rosa Desktop", "org.kde.plasma.folder"); var desktopsArray = desktopsForActivity(id); print(desktopsArray.length); for( var j = 0; j < desktopsArray.length; j++) { desktopsArray[j].wallpaperPlugin = 'org.kde.image'; desktopsArray[j].currentConfigGroup = ["General"] desktopsArray[j].writeConfig("showToolbox", "false") //var clock = desktopsArray[j].addWidget("org.kde.plasma.analogclock"); } } --- layout.js --- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 Pulferchanged: What|Removed |Added CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 Pulferchanged: What|Removed |Added CC||h...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 Pulferchanged: What|Removed |Added CC||ivan.cu...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 Pulferchanged: What|Removed |Added CC||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] New: Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 Bug ID: 365989 Summary: Default desktop layout is not loaded properly from template Product: plasmashell Version: 5.7.2 Platform: ROSA RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: pul...@list.ru Default desktop layout is not loaded properly from system template. It happens because Plasma Shell cannot create an activity ("Failed to create and switch to the activity" message in .xsession-errors). This commit looks like an attempt to fix it: https://quickgit.kde.org/?p=plasma-workspace.git=commitdiff=f7ef6ee87b8957bebc976b6fc9e0df279cea05f1 But in fact it only makes things worse (if backported to 5.7.2 package) - Plasma Shell locks on load, there's only black screen without desktop and panel. You can try to download ROSA Desktop ISO (with Plasma 5.7.2 + backported f7ef6ee87b8957bebc976b6fc9e0df279cea05f1) and start it in live mode to reproduce Plasma deadlock: https://abf.rosalinux.ru/platforms/rosa2014.1/products/137/product_build_lists/15706 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365569] After update to KF5.24 systemtray is missing its icons (and functionalities)
https://bugs.kde.org/show_bug.cgi?id=365569 --- Comment #14 from Pulfer--- IMHO, KF 5 updates shouldn't break older Plasma 5 releases. It shouldn't be a game "guess which version of KF properly works with which version of Plasma". This bug is marked fixed now, but in fact it still exists in Plasma 5.6 branch used with KF 5.24. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365569] After update to KF5.24 systemtray is missing its icons (and functionalities)
https://bugs.kde.org/show_bug.cgi?id=365569 --- Comment #11 from Pulfer--- (In reply to Hrvoje Senjan from comment #8) > (In reply to Rex Dieter from comment #5) > > I mention this in case anyone knows of other plasma modules that should be > > rebulit on Qt5 upgrades (besides plasma-integration). > > Kwin and kwayland; though i doubt this makes a difference for this issue. Reverting these 2 commits seems to fix the issue: 1. https://quickgit.kde.org/?p=plasma-framework.git=commitdiff=6f5816fc575927201a1aa9cc1fdb0c75a1a3ab69 2. https://quickgit.kde.org/?p=plasma-framework.git=commitdiff=4f7ead27d659352efd5104af08f94cea079d35a6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365701] No icons in system tray if widgets are locked
https://bugs.kde.org/show_bug.cgi?id=365701 --- Comment #6 from Pulfer--- Reverting these 2 commits seems to fix the issue: 1. https://quickgit.kde.org/?p=plasma-framework.git=commitdiff=6f5816fc575927201a1aa9cc1fdb0c75a1a3ab69 2. https://quickgit.kde.org/?p=plasma-framework.git=commitdiff=4f7ead27d659352efd5104af08f94cea079d35a6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365701] No icons in system tray if widgets are locked
https://bugs.kde.org/show_bug.cgi?id=365701 --- Comment #5 from Pulfer--- (In reply to Marco Martin from comment #4) > does it do that even if on the previous boot was unlocked and did have icons > in? Yes, with KF 5.24.0 it's simple: locked widgets -> no systray icons, unlocked widgets -> systray icons. I'll try to find which commit to plasma-framework causes such behaviour. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365701] No icons in system tray if widgets are locked
https://bugs.kde.org/show_bug.cgi?id=365701 --- Comment #2 from Pulfer--- > Qt 5.6.1, KF 5.24.0, Plasma 6.6.5. Plasma 5.6.5, of course. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365701] No icons in system tray if widgets are locked
https://bugs.kde.org/show_bug.cgi?id=365701 --- Comment #1 from Pulfer--- Created attachment 100107 --> https://bugs.kde.org/attachment.cgi?id=100107=edit System tray without icons -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365701] New: No icons in system tray if widgets are locked
https://bugs.kde.org/show_bug.cgi?id=365701 Bug ID: 365701 Summary: No icons in system tray if widgets are locked Product: plasmashell Version: 5.6.5 Platform: ROSA RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: pul...@list.ru There are no icons in system tray after reboot if widgets are locked. Qt 5.6.1, KF 5.24.0, Plasma 6.6.5. Reproducible: Always Steps to Reproduce: 1. Lock widgets 2. Reboot (no icons in system tray) 3. Unlock widgets 4. Reboot (icons in system tray are fine) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 352057] Kdenlive segmentation fault on starting DVD Wizard (OpenGL context issue)
https://bugs.kde.org/show_bug.cgi?id=352057 --- Comment #10 from Pulfer--- (In reply to Jean-Baptiste Mardelle from comment #9) > Git commit 8e957fddf1745ba93317e49958b7b9d5dc74126d With this patch it doesn't work again. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 352057] Kdenlive segmentation fault on starting DVD Wizard (OpenGL context issue)
https://bugs.kde.org/show_bug.cgi?id=352057 --- Comment #8 from Pulfer--- Created attachment 100053 --> https://bugs.kde.org/attachment.cgi?id=100053=edit DVD Wizard window when timer is set to 0 (In reply to Jean-Baptiste Mardelle from comment #7) > Git commit 9a006b87cca38186c7c58ace9a23c338d6c67487 by Jean-Baptiste Thanx, it's almost fixed now. :-) Can you please set timer to 1000 to completely fix it? -QTimer::singleShot(0, this, SLOT(slotUpdateChaptersList())); +QTimer::singleShot(1000, this, SLOT(slotUpdateChaptersList())); -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 365204] Breeze icons are always used in some places
https://bugs.kde.org/show_bug.cgi?id=365204 --- Comment #25 from Pulfer--- (In reply to Wolfgang Bauer from comment #21) > > Please check system.svgz from Air theme. As I wrote in comment 10, I guess > > there's a typo there ("system-user" element used instead of "system-users"). > > And why do you think that is a typo or even matters? It's a typo because the proper icon name is "system-users", not "system-user": /usr/share/icons/Adwaita/32x32/apps/system-users.png /usr/share/icons/breeze/apps/32/system-users.svg /usr/share/icons/gnome/32x32/apps/system-users.png /usr/share/icons/oxygen/base/32x32/apps/system-users.png etc (including system.svgz from Breeze). Only in Air's system.svgz it's "system-user". > That particular icon is not even used anywhere AFAICS There's a chance that some plasmoid will try to use it in future. It's not related to Kicker/Kickoff, just a general Air theme bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365363] Changing icons from System Settings is broken
https://bugs.kde.org/show_bug.cgi?id=365363 --- Comment #4 from Pulfer--- Created attachment 100052 --> https://bugs.kde.org/attachment.cgi?id=100052=edit Debug output for KIconLoaderPrivate::insertCachedPixmapWithPath (In reply to Wolfgang Bauer from comment #3) > I don't see "messed up icons" or a "damaged" icon cache though. You can apply the attached debug patch to kiconthemes and then start systemsettings from terminal. You will see that System Settings keeps inserting icons from the theme it was started with even after icon theme was changed (and back button was pressed). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 365204] Breeze icons are always used in some places
https://bugs.kde.org/show_bug.cgi?id=365204 --- Comment #20 from Pulfer--- (In reply to Wolfgang Bauer from comment #19) > Haven't checked the other affected ones yet, but I suspect a similar problem > there. > system.svgz is fine though. Please check system.svgz from Air theme. As I wrote in comment 10, I guess there's a typo there ("system-user" element used instead of "system-users"). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365363] Changing icons from System Settings is broken
https://bugs.kde.org/show_bug.cgi?id=365363 Pulferchanged: What|Removed |Added CC||wba...@tmo.at -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 352057] Kdenlive segmentation fault on starting DVD Wizard (OpenGL context issue)
https://bugs.kde.org/show_bug.cgi?id=352057 --- Comment #6 from Pulfer--- Just checked kdenlive 16.04.3 (Qt 5.6.1, KF 5.24.0), still hangs in KDE4 when trying to create DVD with wizard. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365363] Changing icons from System Settings is broken
https://bugs.kde.org/show_bug.cgi?id=365363 --- Comment #1 from Pulfer--- (In reply to Wolfgang Bauer from comment #18) > Rather sounds like a problem with actually saving the selected icon theme to > kdeglobals to me... In fact, it saves the selected icon theme to ~/.config/kdeglobals properly right after applying it from SS -> Icons KCM. It's very easy to check... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365204] Breeze icons are always used in some places
https://bugs.kde.org/show_bug.cgi?id=365204 --- Comment #17 from Pulfer--- (In reply to Wolfgang Bauer from comment #16) > I am not sure about your review request though. > On the one hand you "complain" that some icons are taken from the icon > theme, and you want to fix that by taking *all* icons from the icon theme? > ;-) I rather "complain" that in general menu plasmoids' contents look inconsistent because of mixed icon sources. The only exception is desktop themes having the same icons as icon themes. But in such cases it works the same way as if "usesPlasmaTheme: false" was set. > The desktop themes should be fixed IMHO. IMHO, it's more plasmoid design issue than theme bug. If there are 2 buttons with the same action in an application ("Poweroff " etc buttons in menu), likely they should look the same. > And AFAIK, the icon module actually deletes the icon cache when you switch to > a different theme. At least in System Settings' case SS keeps "thinking" that old icons theme is still used (if you press back button instead of closing SS with KCM icons after applying new icons theme). So it inserts icons from older theme to icons cache. Maybe some other applications do the same. But likely it's better to discuss in #365363 anyway... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365204] Breeze icons are always used in some places
https://bugs.kde.org/show_bug.cgi?id=365204 --- Comment #14 from Pulfer--- (In reply to Wolfgang Bauer from comment #12) > (In reply to Pulfer from comment #10) > > Sorry, I meant system.svgz. BTW, please check system.svgz from air theme. I > > guess there's a typo there ("system-user" element instead of > > "system-users"). > > No, works fine here. > > Maybe a caching issue? > Try to delete ~/.cache/plasma* when Plasma is not running. Likely it's caused by https://bugs.kde.org/show_bug.cgi?id=365363 (System Setting may damage icons cache) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365363] New: Changing icons from System Settings is broken
https://bugs.kde.org/show_bug.cgi?id=365363 Bug ID: 365363 Summary: Changing icons from System Settings is broken Product: systemsettings Version: 5.6.5 Platform: ROSA RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: kcm_icons Assignee: unassigned-b...@kde.org Reporter: pul...@list.ru CC: unassigned-b...@kde.org Changing icons from System Settings doesn't work properly. 1.1. Open System Settings 1.2. Open Icons module 1.3. Change Icon theme from Breeze to Oxygen 1.4. Close window (!) 1.5. Open System Settings again 1.6. See new icons theme properly applied So, this way it works properly. 2.1. Open System Settings 2.2. Open Icons module 2.3. Change Icon theme from Oxygen to Breeze 2.4. Press back ("All settings") button (!) 2.5. Open Icons module again 2.6. See Oxygen theme still set 2.7. Close window 2.8. Open System Settings again 2.9. See messed up icons (because icon cache was damaged) 2.9. Open Icons module 2.10. See Breeze theme set now So, this way it doesn't work properly. Looks like System Settings must re-load configs after back button is pressed. Or maybe it's something specific to icons KCM. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365363] Changing icons from System Settings is broken
https://bugs.kde.org/show_bug.cgi?id=365363 Pulferchanged: What|Removed |Added CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365363] Changing icons from System Settings is broken
https://bugs.kde.org/show_bug.cgi?id=365363 Pulferchanged: What|Removed |Added CC||j...@jriddell.org -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 256856] Changing icon theme does not take effect in Dophin
https://bugs.kde.org/show_bug.cgi?id=256856 --- Comment #23 from Pulfer--- (In reply to Pulfer from comment #22) > Michael, should kbuildsycoca5 update ~/.cache/icon-cache.kcache? It actually > doesn't, but I don't know if it's a bug. Something is Plasma 5 creates > broken icon-cache.kcache file after icons theme change from System Settings. > Usually I need to switch to new theme twice to make it fully applied. > Otherwise I get mixed icons (some from current theme, some from previous). Well, it seems to be another bug: https://bugs.kde.org/show_bug.cgi?id=365363 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 256856] Changing icon theme does not take effect in Dophin
https://bugs.kde.org/show_bug.cgi?id=256856 Pulferchanged: What|Removed |Added CC||pul...@list.ru --- Comment #22 from Pulfer --- Michael, should kbuildsycoca5 update ~/.cache/icon-cache.kcache? It actually doesn't, but I don't know if it's a bug. Something is Plasma 5 creates broken icon-cache.kcache file after icons theme change from System Settings. Usually I need to switch to new theme twice to make it fully applied. Otherwise I get mixed icons (some from current theme, some from previous). -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 343891] khotkeysrc destroyed upon changing a shortcut setting
https://bugs.kde.org/show_bug.cgi?id=343891 Pulferchanged: What|Removed |Added CC||pul...@list.ru --- Comment #14 from Pulfer --- BTW, shouldn't khotkeys open config as KConfig::SimpleConfig? To avoid adding lines like: [Icons] Theme[$d] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365204] Breeze icons are always used in some places
https://bugs.kde.org/show_bug.cgi?id=365204 --- Comment #11 from Pulfer--- (In reply to Pulfer from comment #10) > I recorded a video where it's possible to see that launcher icon on panel is > used from icons theme, not from plasma theme (sorry for non-English Plasma > interface but it shouldn't matter): https://disk.yandex.ru/client/disk Correct URL: https://yadi.sk/i/GxaIPQUBt8nBa -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365204] Breeze icons are always used in some places
https://bugs.kde.org/show_bug.cgi?id=365204 --- Comment #10 from Pulfer--- (In reply to Wolfgang Bauer from comment #8) > > In fact, they both have such elements in start.svgz. Maybe > > plasma-frameworks's IconItem::setSource function is buggy then. > > start.svgz is only used for application launcher "icon" itself AFAIK. Sorry, I meant system.svgz. BTW, please check system.svgz from air theme. I guess there's a typo there ("system-user" element instead of "system-users"). As for application launcher icon, sometimes it uses icon from Plasma theme, sometimes from icons theme (icon may change after system reboot). I recorded a video where it's possible to see that launcher icon on panel is used from icons theme, not from plasma theme (sorry for non-English Plasma interface but it shouldn't matter): https://disk.yandex.ru/client/disk Ignore kicker favorite system actions icons on video, they are patched to use icons theme. Also note that I replaced start-here-kde from Breeze icons theme (color dots) with icon from Breeze plasma theme ("K"). But it's clear that launcher uses Breeze icons theme icon if I switch desktop theme to Oxygen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365204] Breeze icons are always used in some places
https://bugs.kde.org/show_bug.cgi?id=365204 --- Comment #7 from Pulfer--- > Neither Breeze nor Oxygen have icons like "system-log-out", "system-reboot" In fact, they both have such elements in start.svgz. Maybe plasma-frameworks's IconItem::setSource function is buggy then. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 355540] Tooltips color wrong in gtk applications
https://bugs.kde.org/show_bug.cgi?id=355540 Pulferchanged: What|Removed |Added CC||pul...@list.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365204] Breeze icons are always used in some places
https://bugs.kde.org/show_bug.cgi?id=365204 --- Comment #6 from Pulfer--- (In reply to Eike Hein from comment #5) > Maybe the Oxygen theme has no icons. Neither Breeze nor Oxygen have icons like "system-log-out", "system-reboot" etc in /usr/share/plasma/desktoptheme/*/icons/ (plasma theme) directories. And both have such icons in /usr/share/icons/* (icon theme) directories. There's a chance that using Breeze icon theme as fallback (if there's no selected icon in plasma theme) is hardcoded somewhere. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365204] Breeze icons are always used in some places
https://bugs.kde.org/show_bug.cgi?id=365204 Pulferchanged: What|Removed |Added Resolution|INVALID |FIXED --- Comment #4 from Pulfer --- (In reply to Eike Hein from comment #3) > At least in Kicker's case, the system favorites are supposed to use the > Plasma theme. Why does it use Breeze icons if Plasma theme is set to Oxygen? Is it a Plasma bug? > The Kickoff patch might be valid, please submit it via Phab. https://git.reviewboard.kde.org/r/128392/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365204] Breeze icons are always used in some places
https://bugs.kde.org/show_bug.cgi?id=365204 --- Comment #2 from Pulfer--- Created attachment 99929 --> https://bugs.kde.org/attachment.cgi?id=99929=edit Patch to make kicker and kickoff use icons from icon theme Not sure if it's desired behaviour for upstream. But as it makes Kicker and Kickoff look consistent, I'll apply it to ROSA's Plasma Desktop package. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365204] Breeze icons are always used in some places
https://bugs.kde.org/show_bug.cgi?id=365204 --- Comment #1 from Pulfer--- Created attachment 99928 --> https://bugs.kde.org/attachment.cgi?id=99928=edit Kickoff menu with messup up icons Kickoff menu is also affected. Some icons are taken from Breeze them, some from Oxygen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365204] New: Breeze icons are always used in some places
https://bugs.kde.org/show_bug.cgi?id=365204 Bug ID: 365204 Summary: Breeze icons are always used in some places Product: plasmashell Version: 5.6.5 Platform: ROSA RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: pul...@list.ru CC: plasma-b...@kde.org Even if icon theme and plasma theme are set to Oxygen (or other themes), Breeze icons are used for favorite system actions in Kicker. At the same time icons in system actions submenu are correctly set from current icon theme. Plasma 5.6.5, KF 5.23.0, Qt 5.6.1. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365166] defaultWallpaperTheme applied only on second login
https://bugs.kde.org/show_bug.cgi?id=365166 --- Comment #1 from Pulfer--- Looks like it happens because LookAndFeelPackage from system kdeglobals creates user config plasmarc with [Theme] section (based on look-and-feel package). And if this config exists (second login), default wallpaper is properly set. If there's system plasmarc config with defined plasma theme, default wallpaper from that theme is set on first user login. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365166] New: defaultWallpaperTheme applied only on second login
https://bugs.kde.org/show_bug.cgi?id=365166 Bug ID: 365166 Summary: defaultWallpaperTheme applied only on second login Product: plasmashell Version: 5.6.5 Platform: ROSA RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: pul...@list.ru For some reasons defaultWallpaperTheme applied only on second login. On first login Next wallpaper from Breeze desktoptheme is used instead. How to reproduce: 1. Add "LookAndFeelPackage=[any_desktoptheme_package]" to "[KDE]" section of /etc/xdg/kdeglobals 2. Create new user 3. Login with that user and see Next wallpaper 4. Logout 5. Login again and see wallpaper defined in desktoptheme package from #1 In case it matters, default desktop is set to org.kde.plasma.folder. KF 5.23.0, Plasma 5.6.5. Maybe it's not a bug and there's a proper way to set default Plasma desktop wallpaper in system configs (/etc/xdg)? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 365095] Missing application-menu action icon in oxygen-icons5
https://bugs.kde.org/show_bug.cgi?id=365095 --- Comment #5 from Pulfer--- Surely :-) Meanwhile I found review request that changed "Control" icon in Dolphin from categories/applications-system to actions/application-menu: https://git.reviewboard.kde.org/r/124971/ -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 365095] Missing application-menu action icon in oxygen-icons5
https://bugs.kde.org/show_bug.cgi?id=365095 --- Comment #3 from Pulfer--- I guess you just need to copy categories/applications-system.png to actions/application-menu.png KDE4 Dolphin used "applications-system" icon for this "Control" button. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 365095] Missing application-menu action icon in oxygen-icons5
https://bugs.kde.org/show_bug.cgi?id=365095 --- Comment #1 from Pulfer--- Created attachment 99854 --> https://bugs.kde.org/attachment.cgi?id=99854=edit Missing icon for Control button -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 365095] New: Missing application-menu action icon in oxygen-icons5
https://bugs.kde.org/show_bug.cgi?id=365095 Bug ID: 365095 Summary: Missing application-menu action icon in oxygen-icons5 Product: Oxygen Version: unspecified Platform: ROSA RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: icons Assignee: n...@oxygen-icons.org Reporter: pul...@list.ru There's no application-menu action icon in oxygen-icons5. It's used in Dolphin main window interface so it's quite important. oxygen-icons5 5.23.0, dolphin 16.04.2. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 363260] Can't create twitter account
https://bugs.kde.org/show_bug.cgi?id=363260 Pulferchanged: What|Removed |Added CC||pul...@list.ru --- Comment #3 from Pulfer --- Same here, Google works (opens window with login page) and Twitter doesn't (nothing visible happens). $ kcmshell5 kcm_kaccounts Checking "twitter-microblog" "twitter" Found a service, not skipping: "twitter-microblog" Trying to convert empty KLocalizedString to QString. Checking "twitter-microblog" "owncloud" Checking "google-youtube" "owncloud" Checking "twitter-microblog" "google" Checking "google-youtube" "google" Found a service, not skipping: "google-youtube" Starting new account dialog for "twitter" "twitter" Looking for plugin "" Starting auth session with "oauth2" Info: Id: 24 caption: "twitter" owner: "" userName: "" -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 352057] Kdenlive segmentation fault on starting DVD Wizard (OpenGL context issue)
https://bugs.kde.org/show_bug.cgi?id=352057 --- Comment #5 from Pulfer--- (In reply to Pulfer from comment #4) > I just tried 15.12.0. It doesn't segfault in KDE 4 but DVD Wizard dialog > window hangs when pressing "Next" button. Still the same with kdenlive 16.04.0 in KDE4. -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 361568] Systemd KCM deadlock on start
https://bugs.kde.org/show_bug.cgi?id=361568 --- Comment #3 from Pulfer--- More debug info. There's about 1 minute lock after each bus 2 method calling. --- Detected systemd 219 Persistent partition size found to: 30108 MB Volatile partition size found to: 1948 MB Calling method "Subscribe" with iface 0 on bus 0 Calling method "Subscribe" with iface 0 on bus 2 Invalid DBus interface on bus 2 Refreshing system units... Calling method "ListUnits" with iface 0 on bus 0 Calling method "ListUnitFiles" with iface 0 on bus 0 Refreshing user units... Calling method "ListUnits" with iface 0 on bus 2 Invalid DBus interface on bus 2 --- -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 361568] Systemd KCM deadlock on start
https://bugs.kde.org/show_bug.cgi?id=361568 --- Comment #2 from Pulfer--- After all it started, just took a long to do it. Looks like it happens because of blocking DBus call: --- Detected systemd 219 Persistent partition size found to: 30108 MB Volatile partition size found to: 1948 MB Invalid DBus interface on bus 2 Refreshing system units... Refreshing user units... Invalid DBus interface on bus 2 --- Backtrace: == #0 0x7f8c76d83720 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8c79acbe6a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8c7b8d52d4 in () at /usr/lib64/libQt5DBus.so.5 #3 0x7f8c7b89b757 in () at /usr/lib64/libQt5DBus.so.5 #4 0x7f8c7b89be21 in () at /usr/lib64/libQt5DBus.so.5 #5 0x7f8c7b8a6bd5 in () at /usr/lib64/libQt5DBus.so.5 #6 0x7f8c7b8a6d45 in QDBusInterface::QDBusInterface(QString const&, QString const&, QString const&, QDBusConnection const&, QObject*) () at /usr/lib64/libQt5DBus.so.5 #7 0x7f8c5907405b in kcmsystemd::callDbusMethod(QString, dbusIface, dbusBus, QList const&) (this=this@entry= 0x200fa60, method=..., ifaceName=ifaceName@entry=sysdMgr, bus=bus@entry=user, args=...) at /usr/src/debug/systemd-kcm-1.2.1/src/kcmsystemd.cpp:1518 #8 0x7f8c5907e565 in kcmsystemd::kcmsystemd(QWidget*, QList const&) (this=this@entry=0x200fa60, parent=parent@entry=0x1f8bf30, args=...) at /usr/src/debug/systemd-kcm-1.2.1/src/kcmsystemd.cpp:122 #9 0x7f8c5908847b in KPluginFactory::createInstance (QWidget*, QObject*, QList const&) (parentWidget=, parent=, args=...) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:477 == -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 361568] New: Systemd KCM deadlock on start
https://bugs.kde.org/show_bug.cgi?id=361568 Bug ID: 361568 Summary: Systemd KCM deadlock on start Product: Systemd KCM Version: 1.2.1 Platform: ROSA RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: rthoms...@gmail.com Reporter: pul...@list.ru Systemd KCM fails to start (deadlock after "Volatile partition"): --- $ kcmshell5 kcm_systemd QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object true Detected systemd 219 Persistent partition size found to: 30108 MB Volatile partition size found to: 1948 MB --- Qt 5.6.0, KF 5.20.0, Plasma 5.6.2. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 361568] Systemd KCM deadlock on start
https://bugs.kde.org/show_bug.cgi?id=361568 --- Comment #1 from Pulfer--- This happens with latest systemd kcm master as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358317] xembedsniproxy crashes when clicking on empty fcitx icon
https://bugs.kde.org/show_bug.cgi?id=358317 Pulferchanged: What|Removed |Added CC||pul...@list.ru --- Comment #5 from Pulfer --- (In reply to David Edmundson from comment #3) > Fixed with 988a7bef7e84a4a2fc6a2f6ec6145e093dfb84f8 Perhaps this commit should be pushed to master branch as well? It's still only in Plasma/5.5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358291] Kicker applications model is incomplete (missing entries)
https://bugs.kde.org/show_bug.cgi?id=358291 --- Comment #1 from Pulfer--- Created attachment 96761 --> https://bugs.kde.org/attachment.cgi?id=96761=edit Missing separator and "Install & Remove Software" application entry -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357752] Incorrect color for hovered selected items with GTK+ Qt5 style
https://bugs.kde.org/show_bug.cgi?id=357752 --- Comment #2 from Pulfer--- Created attachment 96543 --> https://bugs.kde.org/attachment.cgi?id=96543=edit Colors in Dolphin compared to colors in file open dialogs This screenshot should be more helpful. I played with GTK2 theme colors and now it's easy to see which color Dolphin uses for hovered items (the same color is used for backgrounds in file dialogs). I suggest to avoid changing text color and background color for hovered items. It's enough to highlight icons for hovered items (like it works in KDE4-based Dolphin and KF5-based file dialogs). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357752] New: Incorrect color for hovered selected items with GTK+ Qt5 style
https://bugs.kde.org/show_bug.cgi?id=357752 Bug ID: 357752 Summary: Incorrect color for hovered selected items with GTK+ Qt5 style Product: dolphin Version: 15.12.0 Platform: ROSA RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: pul...@list.ru KF5-based Dolphin sets incorrect color for hovered selected items with GTK+ Qt5 style. Only Dolphin is affected, file dialogs (like Kate -> Open file...) are fine. Reproducible: Always Steps to Reproduce: 1. Set Qt5 style to GTK+ 2. Open Dolphin 3. Select file(s) 4. Move mouse cursor over selected item 5. See incorrect selection color (neither background nor text shouldn't change but they do) See the attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357752] Incorrect color for hovered selected items with GTK+ Qt5 style
https://bugs.kde.org/show_bug.cgi?id=357752 --- Comment #1 from Pulfer--- Created attachment 96541 --> https://bugs.kde.org/attachment.cgi?id=96541=edit Incorrect colors for hovered selection in Dolphin -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357752] Incorrect color for hovered selected items with GTK+ Qt5 style
https://bugs.kde.org/show_bug.cgi?id=357752 --- Comment #3 from Pulfer--- Created attachment 96560 --> https://bugs.kde.org/attachment.cgi?id=96560=edit Patch to disable background color change for hovered items -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 348998] SDDM login manager configuration window can be unresponsive
https://bugs.kde.org/show_bug.cgi?id=348998 --- Comment #14 from Pulfer--- (In reply to jeremy9856 from comment #13) > I just tested, for fun, the Nouveau drivers and the windows don't seem to be > unresponsive anymore ! > > Maybe it's a problem with the Nvidia drivers ? But VirtualBox with 3D Acceleration turned off is also affected. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 348998] SDDM login manager configuration window can be unresponsive
https://bugs.kde.org/show_bug.cgi?id=348998 Pulferchanged: What|Removed |Added CC||pul...@list.ru --- Comment #11 from Pulfer --- Same with ROSA packages (Plasma 5.5.2). When run from systemsettings SDDM KCM is always unresponsive in my test VirtualBox machine. But when run just as "kcmshell5 sddm" it works fine. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 352057] Kdenlive segmentation fault on starting DVD Wizard (OpenGL context issue)
https://bugs.kde.org/show_bug.cgi?id=352057 --- Comment #4 from Pulfer--- I just tried 15.12.0. It doesn't segfault in KDE 4 but DVD Wizard dialog window hangs when pressing "Next" button. -- You are receiving this mail because: You are watching all bug changes.