[kwin] [Bug 449797] Plasma 5.24 and nvidia GPU: segfault in KWin::GbmSurface::swapBuffersForDrm()
https://bugs.kde.org/show_bug.cgi?id=449797 soee changed: What|Removed |Added CC||kont...@soee.pl --- Comment #26 from soee --- I have similar problems on KDE Neon. Plasma 5.24 + Nvidia Driver 510. Plasmashell won't start but apps windows do. When i try manually start for example krunner it produces: #krunner qt.qpa.wayland: Could not create EGL surface (EGL error 0x321c) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488670] New: Freeze with black screen when trying to enter the Wayland session
https://bugs.kde.org/show_bug.cgi?id=488670 Bug ID: 488670 Summary: Freeze with black screen when trying to enter the Wayland session Classification: Plasma Product: kwin Version: git-stable-Plasma/6.1 Platform: Neon OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kont...@soee.pl Target Milestone: --- SUMMARY Some scenario leads to a situation when trying to login to Wayland session the PC just freezes after SDDM with black screen and white _ in the upper left corner of the screen. STEPS TO REPRODUCE I am not sure how to reproduce it. I am sure it has something to do with playing with the Display Settings where we can set the refresh rate, adaptive synchronization, color profile etc. I had this situation twice already. I was playing with the display setting to test poor performance on the Nvidia GPU. I was changing the refresh rate, adaptive synchronization, once set build in color profile. There were no crashes when playing with tho settings, just PC freeze after reboot and login with SDDM. There is one workaround/manual fix which allows me to restore my desktop and use Wayland session: - enter recovery mode or CLI when not in any active session - remove file: ~/.config/kwinoutputconfig.json After that i can login just fine. I have notification that i am running in the graphics safe mode (nomodeset) but after next reboot/login its gone any my desktop works fine. Looking at logs i'v seen such entries for example: cze 17 19:48:32 TachikomaPC-Neon kwin_wayland[1821]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. and are incompatible cze 17 19:48:32 TachikomaPC-Neon kwin_wayland[1821]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" cze 17 19:48:32 TachikomaPC-Neon kwin_wayland[1821]: kwin_wayland_drm: Checking test buffer failed! cze 17 19:48:32 TachikomaPC-Neon kwin_wayland[1821]: kwin_core: Applying output config failed! OBSERVED RESULT The PC sometimes freezes when trying to enter Wayland session. EXPECTED RESULT Wayland session should work fine without any PC freezes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon KDE Plasma Version: 6.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 GPU: Nvidia 4080 GPU Driver Version: 555.52.04 ADDITIONAL INFORMATION I am not sure what causes this problem and i am not 100% sure if it is some bug, but i am posting it here as maybe someone can confirm it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488670] Freeze with black screen when trying to enter the Wayland session
https://bugs.kde.org/show_bug.cgi?id=488670 --- Comment #3 from soee --- Created attachment 170598 --> https://bugs.kde.org/attachment.cgi?id=170598&action=edit Working config -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488670] Freeze with black screen when trying to enter the Wayland session
https://bugs.kde.org/show_bug.cgi?id=488670 --- Comment #4 from soee --- Created attachment 170599 --> https://bugs.kde.org/attachment.cgi?id=170599&action=edit Failing config -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488670] Freeze with black screen when trying to enter the Wayland session
https://bugs.kde.org/show_bug.cgi?id=488670 --- Comment #5 from soee --- I have posted 2 configs: 1 working and 1 failing, the one working is not the default one though (i have played with settings a bit, so it probably was updated). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488670] Freeze with black screen when trying to enter the Wayland session
https://bugs.kde.org/show_bug.cgi?id=488670 --- Comment #6 from soee --- Ok i did one test: - i have enabled HDR - i have rebooted - session failed to start with black screen - i have set highDynamicRange: false - reboot and session still failed to start - i have set wideColorGamut: false - reboot and session starts fine -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488754] New: Minimize all action bound to screen corner stops to restore windows
https://bugs.kde.org/show_bug.cgi?id=488754 Bug ID: 488754 Summary: Minimize all action bound to screen corner stops to restore windows Classification: Plasma Product: kwin Version: git-stable-Plasma/6.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kont...@soee.pl Target Milestone: --- SUMMARY For several already i am using screen corners to bind some actions. One of them is the Minimize All which is bound to lower left cornet. On X11 it works just fine. On Wayland session if it hover it multiple times (like 3-4) to minimize/unminimize windows, the action stops working with all windows being minimized. If i maximize some of the windows by clicking on teh app icon in the task manager, i can minimize it again, but the situation is the same - it stops working after few attempts to minimize/unminimize it. STEPS TO REPRODUCE 1. Bind the Minimize All action to screen corner 2. Move mouse to this corner several times no minimize and then restore windows 3. After like 3-4 times the corner stops to react and minimized windows are not restored again OBSERVED RESULT Minimiza All action bound to screen corner does not restore minimized windows after several show/hide triggers EXPECTED RESULT If the windows were minimized by hovering with mouse the corner where the Minimize All action is bound, they should be always restored (unminimized) after second time the corner was hovered. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon KDE Plasma Version: 6.1 KDE Frameworks Version: 6.3 Qt Version: 6.7 GPU: Nvidia 4080 GPU Driver Version: 555.52.04 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488754] Minimize all action bound to screen corner stops to restore windows
https://bugs.kde.org/show_bug.cgi?id=488754 --- Comment #1 from soee --- I am not sure if there was any fix for this, but it seems the issue is gone for me now. I am already on Plasma 6.1.1. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478404] New: Visible glitches on Wayland session when moving cursor over Application Dashboard (Nvidia GPU)
https://bugs.kde.org/show_bug.cgi?id=478404 Bug ID: 478404 Summary: Visible glitches on Wayland session when moving cursor over Application Dashboard (Nvidia GPU) Classification: Plasma Product: kwin Version: 5.27.10 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kont...@soee.pl Target Milestone: --- SUMMARY When i am using Nvidia GPU with proprietary drivers and i am on Wayland session, the Application Dashboard has visual glitches when moving cursor on the blurred background (you can check attached video file). This glitch in some cases is less intensive. Foe example if i have fullscreen webbrowser opened and playing some YT video and i open Application Dashboard, this glitch shows up only very close to the mouse cursor and does not leave this track as shown on the video. STEPS TO REPRODUCE 1. Use PC with Nvidia GPU and proprietary drivers 2. Login with Wayland session 3. Open Application Dashboard (when blur effect is active in system) 4. Move mouse cursor around - you should see the glitches OBSERVED RESULT Moving cursor over Application Dashboard blurred bckground renders glitches - leavs strange darker track after cursor. EXPECTED RESULT Moving mouse when Application Dashboard is opened (fullscreen) should not render any glitches. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478404] Visible glitches on Wayland session when moving cursor over Application Dashboard (Nvidia GPU)
https://bugs.kde.org/show_bug.cgi?id=478404 --- Comment #1 from soee --- Created attachment 164094 --> https://bugs.kde.org/attachment.cgi?id=164094&action=edit Video showing rendered glitches -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 436999] New: New calendar renders dots for months and years view
https://bugs.kde.org/show_bug.cgi?id=436999 Bug ID: 436999 Summary: New calendar renders dots for months and years view Product: frameworks-kwidgetsaddons Version: 5.82.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: kont...@soee.pl CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 138376 --> https://bugs.kde.org/attachment.cgi?id=138376&action=edit Buggy months view With the new, redesigned calendar widget the dots were introduced to represents events for days. They work fine for days view but are rendered duplicated on whole width of the single month/year box on months and years view. STEPS TO REPRODUCE 1. Click on the digital clock widget 2. Switch calendar view to monts or years view OBSERVED RESULT The month/year box renders duplicated dots at the bottom. EXPECTED RESULT Probably month/year view should not render dots for events or show only one dot with number of events next to it instead of to many dots. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425465] New: Add systray monochrome icon for Elisa music player
https://bugs.kde.org/show_bug.cgi?id=425465 Bug ID: 425465 Summary: Add systray monochrome icon for Elisa music player Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: kont...@soee.pl CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 130937 --> https://bugs.kde.org/attachment.cgi?id=130937&action=edit Default Elisa icon on dark panel Elisa music player has an option to be docked in systray. The current icon is used but it doesn't look good especially on dark panel as well as it isn't aligned horizontally with other icons. STEPS TO REPRODUCE 1. Open Elisa music player 2. Go to properties and set option to dock app in systray when main window is closed 3. Close player window and check icon in systrtay OBSERVED RESULT The icon placed on dark panel isn't readable and is not aligned horizontally with other icons EXPECTED RESULT Elisa has monochrome icon used in systray that looks good on dark and light panels and is aligned horizontally with other icons SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.19 Focal KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.72 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 476416] New: When filtering desktop effects list, item with more details overlaps next item on the list
https://bugs.kde.org/show_bug.cgi?id=476416 Bug ID: 476416 Summary: When filtering desktop effects list, item with more details overlaps next item on the list Classification: Frameworks and Libraries Product: frameworks-kirigami Version: 5.111.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: kont...@soee.pl CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: Not decided Created attachment 162793 --> https://bugs.kde.org/attachment.cgi?id=162793&action=edit Image shows described issue SUMMARY If we go to System Settings -> Desktop Effects module and filter the list, item which has author or license information rendered, does not render as is should (text renders over next item). STEPS TO REPRODUCE 1. Open System Settings 2. Go to Desktop Effects KCM 3. Filter list, make sure there will be at least 1 item with author/license details OBSERVED RESULT The item with author/license details partially renders over next item. EXPECTED RESULT Each item should be rendered without overlaping some other. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Check attached screenshot. It was taken on Wayland session with nvidia drivers being used. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 476416] When filtering desktop effects list, item with more details overlaps next item on the list
https://bugs.kde.org/show_bug.cgi?id=476416 soee changed: What|Removed |Added CC||kont...@soee.pl -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 431759] New: Add monochrome systray icon for KTeaTime app
https://bugs.kde.org/show_bug.cgi?id=431759 Bug ID: 431759 Summary: Add monochrome systray icon for KTeaTime app Product: Breeze Version: 5.20.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: kont...@soee.pl CC: kain...@gmail.com Target Milestone: --- KTeaTime app could have dedicated, monochrome systray icon to fit other stanard apps icons visible in systray. STEPS TO REPRODUCE 1. Install KTeamTime - sudo apt install kteatime 2. Run the app 3. Check icon in systray The icon rendered it systray is standard with colors. The icon in systray should be monochrome. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 431953] New: Change widgets panel layout
https://bugs.kde.org/show_bug.cgi?id=431953 Bug ID: 431953 Summary: Change widgets panel layout Product: frameworks-kwidgetsaddons Version: 5.78.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: cf...@kde.org Reporter: kont...@soee.pl CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 135069 --> https://bugs.kde.org/attachment.cgi?id=135069&action=edit Current widgets panel layout At the moment widgets panel is pretty small and has a lot of controls put next to each other and it might lead to general layout to be broken a bit when labels get translated to longer texts (see attached image 1.) I am attaching not so nice in general image (i am no designer) but it shows concept of extended panel with categories list and controls position changed. Please check second attached file. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 431953] Change widgets panel layout
https://bugs.kde.org/show_bug.cgi?id=431953 --- Comment #1 from soee --- Created attachment 135070 --> https://bugs.kde.org/attachment.cgi?id=135070&action=edit Widgets panel redesign concept -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 346622] notifications won't stop popping
https://bugs.kde.org/show_bug.cgi?id=346622 soee changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #15 from soee --- This bug does not happen anymore for a long time. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 461682] Some plasma elements are drawn way too big after upgrade to Frameworks 5.100
https://bugs.kde.org/show_bug.cgi?id=461682 soee changed: What|Removed |Added CC||kont...@soee.pl --- Comment #7 from soee --- I have the same issue with Frameworks 100 on Neon 22.04 and Plasma 5.26. In my case it is also the audio applet as shown on the first attatchment. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 461682] Some plasma elements are drawn way too big after upgrade to Frameworks 5.100
https://bugs.kde.org/show_bug.cgi?id=461682 --- Comment #8 from soee --- (In reply to soee from comment #7) > I have the same issue with Frameworks 100 on Neon 22.04 and Plasma 5.26. > In my case it is also the audio applet as shown on the first attatchment. 100% Global Scale, not set $PLASMA_USE_QT_SCALING. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488670] Freeze with black screen when trying to enter the Wayland session
https://bugs.kde.org/show_bug.cgi?id=488670 soee changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433827] New: Digital Camera KCM is missing headline when activated as default item in category
https://bugs.kde.org/show_bug.cgi?id=433827 Bug ID: 433827 Summary: Digital Camera KCM is missing headline when activated as default item in category Product: systemsettings Version: 5.21.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_deviceautomounter Assignee: tdfisc...@kde.org Reporter: kont...@soee.pl CC: plasma-b...@kde.org Target Milestone: --- Created attachment 136302 --> https://bugs.kde.org/attachment.cgi?id=136302&action=edit Video where we can see the bug If we go to System Settings and open Removable Storage category, the default KCM has no headline until we switch to different KCM and go back. STEPS TO REPRODUCE 1. Open System Settings 2. Open Removable Storage category OBSERVED RESULT The Digital Camera KCM is selected by default on the category items list and it is activated but has no headline. EXPECTED RESULT The Digital Camera KCM is selected by default on the category items list and it is activated and has headline visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 5.21 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413600] New: Update/Check all updates checkbox is not vertically aligned with checkboxes on the list
https://bugs.kde.org/show_bug.cgi?id=413600 Bug ID: 413600 Summary: Update/Check all updates checkbox is not vertically aligned with checkboxes on the list Product: Discover Version: 5.17.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: kont...@soee.pl CC: aleix...@kde.org Target Milestone: --- Created attachment 123569 --> https://bugs.kde.org/attachment.cgi?id=123569&action=edit Checkboxes alignment SUMMARY The Update/Check all updates checkbox is not vertically aligned with checkboxes on packages to update list. STEPS TO REPRODUCE 1. Open Discover 2. Compare checkboxes alignment when there are some update available OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413600] Update/Check all updates checkbox is not vertically aligned with checkboxes on the list
https://bugs.kde.org/show_bug.cgi?id=413600 soee changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 400663] New: Digital clock plasmoid has inconsistent callendar settings window layout
https://bugs.kde.org/show_bug.cgi?id=400663 Bug ID: 400663 Summary: Digital clock plasmoid has inconsistent callendar settings window layout Product: frameworks-kcoreaddons Version: 5.51.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mp...@kde.org Reporter: kont...@soee.pl CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 116082 --> https://bugs.kde.org/attachment.cgi?id=116082&action=edit Callendar settings window conrent If we open digital clock plasmoid settings and go to callendar properites section, we will see that whole layout is inconsistent - checkboxes and labels aren't aligned as they should (probably in one vertical line starting from the left). STEPS TO REPRODUCE 1. Open digital clock settings 2. Got to callendar settings section 3. Watch the layout OBSERVED RESULT checkboxes and labels aren't aligned as they should EXPECTED RESULT Checkboxes and labels should probably be in one vertical line starting from the left SOFTWARE VERSIONS KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 422922] Change dropdown list to select audio source to combobox icon and static text
https://bugs.kde.org/show_bug.cgi?id=422922 --- Comment #1 from soee --- Created attachment 129315 --> https://bugs.kde.org/attachment.cgi?id=129315&action=edit Audio applet before changes. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 422922] New: Change dropdown list to select audio source to combobox icon and static text
https://bugs.kde.org/show_bug.cgi?id=422922 Bug ID: 422922 Summary: Change dropdown list to select audio source to combobox icon and static text Product: plasma-pa Version: 5.19.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: kont...@soee.pl CC: plasma-b...@kde.org Target Milestone: --- At the moment media controls widgets in systray renders dropdown menu to select the audio source that should be used to present data for. My suggestion is it replace this dropdown menu with by adding footer section where single icon will be rendered as a combobox to select source and the selected source name will be rendered as a static text next to this icon. I have attached image that shows the concept. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 422922] Change dropdown list to select audio source to combobox icon and static text
https://bugs.kde.org/show_bug.cgi?id=422922 --- Comment #2 from soee --- Created attachment 129316 --> https://bugs.kde.org/attachment.cgi?id=129316&action=edit Audio applet after changes. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 423183] New: Discover crash during standard usage, scrolling list of items
https://bugs.kde.org/show_bug.cgi?id=423183 Bug ID: 423183 Summary: Discover crash during standard usage, scrolling list of items Product: Discover Version: 5.19.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: kont...@soee.pl CC: aleix...@kde.org Target Milestone: --- During typical usage, discover crashed with stack: Application: Odkrywca (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 QScopedPointer >::operator-> (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 #5 qGetPtrHelper > const> (ptr=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1133 #6 QNetworkReply::d_func (this=this@entry=0x0) at access/qnetworkreply.h:192 #7 QNetworkReply::attribute (this=this@entry=0x0, code=code@entry=QNetworkRequest::RedirectionTargetAttribute) at access/qnetworkreply.cpp:687 #8 0x7f33d49618e4 in Icon::handleFinished (this=0x55aeb8220f20, reply=0x0) at ./src/icon.cpp:342 #9 0x7f33f09706d7 in QtPrivate::QSlotObjectBase::call (a=0x7ffd2cabfac0, r=0x55aeb8220f20, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate (sender=0x55aeb8815470, signal_index=10, argv=0x7ffd2cabfac0) at kernel/qobject.cpp:3870 #11 0x7f33f096af92 in QMetaObject::activate (sender=sender@entry=0x55aeb8815470, m=m@entry=0x7f33eeb88980 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3930 #12 0x7f33ee92b7a3 in QNetworkReply::finished (this=this@entry=0x55aeb8815470) at .moc/moc_qnetworkreply.cpp:385 #13 0x7f33ee88ebd7 in QNetworkReplyHttpImplPrivate::finished (this=0x55aeb8b89270) at access/qnetworkreplyhttpimpl.cpp:2214 #14 0x7f33ee88eeb5 in QNetworkReplyHttpImplPrivate::replyFinished (this=) at access/qnetworkreplyhttpimpl.cpp:1107 #15 0x7f33ee930cf9 in QNetworkReplyHttpImpl::qt_static_metacall (_o=, _c=, _id=, _a=) at .moc/moc_qnetworkreplyhttpimpl_p.cpp:261 #16 0x7f33f096857b in QObject::event (this=0x55aeb8815470, e=0x7f33914a91e0) at kernel/qobject.cpp:1339 #17 0x7f33f21179ac in QApplicationPrivate::notify_helper (this=this@entry=0x55aeb51cdd90, receiver=receiver@entry=0x55aeb8815470, e=e@entry=0x7f33914a91e0) at kernel/qapplication.cpp:3685 #18 0x7f33f211ebb0 in QApplication::notify (this=0x7ffd2cac0280, receiver=0x55aeb8815470, e=0x7f33914a91e0) at kernel/qapplication.cpp:3431 #19 0x7f33f09354a8 in QCoreApplication::notifyInternal2 (receiver=0x55aeb8815470, event=0x7f33914a91e0) at kernel/qcoreapplication.cpp:1075 #20 0x7f33f093567e in QCoreApplication::sendEvent (receiver=receiver@entry=0x55aeb8815470, event=event@entry=0x7f33914a91e0) at kernel/qcoreapplication.cpp:1470 #21 0x7f33f0938121 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55aeb51c9240) at kernel/qcoreapplication.cpp:1815 #22 0x7f33f09386b8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1674 #23 0x7f33f0995103 in postEventSourceDispatch (s=0x55aeb5223900) at kernel/qeventdispatcher_glib.cpp:277 #24 0x7f33ea15d417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f33ea15d650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f33ea15d6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f33f09947ac in QEventDispatcherGlib::processEvents (this=0x55aeb5227870, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7f33f0933d2a in QEventLoop::exec (this=this@entry=0x7ffd2cac01b0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #29 0x7f33f093d4a0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1383 #30 0x55aeb4700592 in main (argc=, argv=) at ./discover/main.cpp:184 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423218] New: Notification with a progress bar shows the button for more info when there is no more info
https://bugs.kde.org/show_bug.cgi?id=423218 Bug ID: 423218 Summary: Notification with a progress bar shows the button for more info when there is no more info Product: plasmashell Version: 5.19.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: kont...@soee.pl CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 129521 --> https://bugs.kde.org/attachment.cgi?id=129521&action=edit Video rendering notification While rendering video in Kdenlive notification was rendered. It shows the rendering progress bar and 2 buttons: to stop the process and to show more info. The more info button - when clicked - shows nothing so I think in some cases this button shouldn't be rendered at all. STEPS TO REPRODUCE 1. Run Kdenlive 2. Prepare some video to render 3. Start rendering process OBSERVED RESULT The notification includes a button to show more info but when clicked no extra info is visible EXPECTED RESULT The notification either show some more info when the button next to stop is clicked to this button should be hidden SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon KDE Plasma Version: 5.19.1 KDE Frameworks Version: 5.71 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420036] New: Add separator line between KCM window action buttons and other buttons inside content area
https://bugs.kde.org/show_bug.cgi?id=420036 Bug ID: 420036 Summary: Add separator line between KCM window action buttons and other buttons inside content area Product: systemsettings Version: 5.18.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcmshell Assignee: plasma-b...@kde.org Reporter: kont...@soee.pl Target Milestone: --- Created attachment 127510 --> https://bugs.kde.org/attachment.cgi?id=127510&action=edit Embedded KCM Various KCM windows embedded inside System Settings or in standalone view often generate 2 rows of buttons where the bottom row is the common action buttons like Reset/Defaults/Apply/Cancel. Maybe a good move would be to separate them a bit by using a thin separator (horizontal line) above the common action buttons row. I have attached 2 screenshots with embedded KCM and standalone one to demonstrate this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420036] Add separator line between KCM window action buttons and other buttons inside content area
https://bugs.kde.org/show_bug.cgi?id=420036 --- Comment #1 from soee --- Created attachment 127511 --> https://bugs.kde.org/attachment.cgi?id=127511&action=edit Standalone view -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414875] After entering the password, SDDM doesn't respond to pressing "Enter", you need to click on the ">" button to it's right
https://bugs.kde.org/show_bug.cgi?id=414875 soee changed: What|Removed |Added CC||kont...@soee.pl --- Comment #4 from soee --- I have the same problem also on lock screen. I have to press the button to be able to unlock it. KDE neon 5.17 Plazma KDE: 5.17.4 Frameworks: 5.64.0 Qt: 5.13.2 Kernel: 5.0.0-37-generic -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 390358] New: Make sure date in copyrights text is up to date
https://bugs.kde.org/show_bug.cgi?id=390358 Bug ID: 390358 Summary: Make sure date in copyrights text is up to date Product: Discover Version: 5.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kont...@soee.pl Target Milestone: --- We had situation today when one user visited our Neon channel and was worried that Discover is no longer maintained. Hes thinking was based on the dates in copyrights text inside About App window - we see value: 2010-2016. If would be good move to update dates to current year. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 390358] Make sure date in copyrights text is up to date
https://bugs.kde.org/show_bug.cgi?id=390358 soee changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 390360] New: Modal background is not fully covered
https://bugs.kde.org/show_bug.cgi?id=390360 Bug ID: 390360 Summary: Modal background is not fully covered Product: kdeplasma-addons Version: 5.12.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: QuickShare Assignee: aleix...@kde.org Reporter: kont...@soee.pl CC: plasma-b...@kde.org Target Milestone: --- Created attachment 110602 --> https://bugs.kde.org/attachment.cgi?id=110602&action=edit QuickShare modal window When we place QuickShare widget inside panel that is not stretched to full screen size but is smaller and maybe centered we can see that the modal window has at the bottom like 10px darker line that seems to be missing background in this section (see attached screenshot). Same things sometimes happen on the right edge of this modal window. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 390360] Modal background is not fully covered
https://bugs.kde.org/show_bug.cgi?id=390360 --- Comment #4 from soee --- Atm. i'm on Neon User Edition with: Plasma 5.12.1 Frameworks 5.43.0 Qt 5.9.3 Nvidia GPU with propriety driver Kernel 4.15.x -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 390360] Modal background is not fully covered
https://bugs.kde.org/show_bug.cgi?id=390360 soee changed: What|Removed |Added Version|5.12.0 |5.12.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375318] New: Calendar control buttons aren't fully visible
https://bugs.kde.org/show_bug.cgi?id=375318 Bug ID: 375318 Summary: Calendar control buttons aren't fully visible Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Calendar Assignee: plasma-b...@kde.org Reporter: kont...@soee.pl Target Milestone: 1.0 Created attachment 103544 --> https://bugs.kde.org/attachment.cgi?id=103544&action=edit Image shows mentioned bug If we open callendar widget and hover one of the 3 action buttons (previous, current, next) that we will see that the bottom of each of them is cut off (probably covered by next element in the layout or their container height is to small). See attached image for details. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375371] New: Segmentation fault on dev version
https://bugs.kde.org/show_bug.cgi?id=375371 Bug ID: 375371 Summary: Segmentation fault on dev version Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kont...@soee.pl Target Milestone: --- Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f27af20f8c0 (LWP 6123))] Thread 42 (Thread 0x7f26e67fc700 (LWP 6166)): #0 0x7f27ab52f69d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f27a6b64740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f27a6b20e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f27a6b21340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f27a6b21722 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2744555916 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7f27a6b47bc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f27a89c86ba in start_thread (arg=0x7f26e67fc700) at pthread_create.c:333 #8 0x7f27ab53f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 41 (Thread 0x7f26e6ffd700 (LWP 6165)): #0 0x7f27a6b65ac9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f27a6b20b51 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f27a6b21317 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f27a6b214ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f27a6b214e9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f27a6b47bc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f27a89c86ba in start_thread (arg=0x7f26e6ffd700) at pthread_create.c:333 #7 0x7f27ab53f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 40 (Thread 0x7f26e77fe700 (LWP 6164)): #0 0x7f27ab533b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f27a6b2139c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f27a6b214ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f27ac16723b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f27ac111cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f27abf36fb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f27abf3bb98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f27a89c86ba in start_thread (arg=0x7f26e77fe700) at pthread_create.c:333 #8 0x7f27ab53f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 39 (Thread 0x7f26e7fff700 (LWP 6163)): #0 0x7f27ab533b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f27a6b2139c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f27a6b214ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f27ac16723b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f27ac111cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f27abf36fb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f27abf3bb98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f27a89c86ba in start_thread (arg=0x7f26e7fff700) at pthread_create.c:333 #8 0x7f27ab53f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 38 (Thread 0x7f2704ff9700 (LWP 6162)): #0 0x7f27a6b65ae4 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f27a6b20920 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f27a6b212cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f27a6b214ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f27ac16723b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f27ac111cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f27abf36fb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f27abf3bb98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f27a89c86ba in start_thread (arg=0x7f2704ff9700) at pthread_create.c:333 #9 0x7f27ab53f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 37 (Thread 0x7f27057fa700 (LWP 6161)): #0 0x7f27abf32fe0 in QMutex::lock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f27ac16698f in
[plasmashell] [Bug 375379] New: Segmentation fault while playing with systray
https://bugs.kde.org/show_bug.cgi?id=375379 Bug ID: 375379 Summary: Segmentation fault while playing with systray Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kont...@soee.pl CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f81508788c0 (LWP 2209))] Thread 30 (Thread 0x7f7fe6ffd700 (LWP 10841)): #0 0x7f814b1a5b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8146b6139c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8146b614ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f814bad023b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f814ba7acea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f814b89ffb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f814dee7675 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f814b8a4b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f814a74a6ba in start_thread (arg=0x7f7fe6ffd700) at pthread_create.c:333 #9 0x7f814b1b182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 29 (Thread 0x7f7fe77fe700 (LWP 7494)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f814b8a5a4b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f808fb8107f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #3 0x7f808fb85078 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f808fb8026d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f808fb850d2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f808fb8026d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f808fb850d2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f808fb8026d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f808fb850d2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f808fb8026d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7f808fb850d2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7f808fb8026d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7f808fb850d2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x7f808fb8026d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #15 0x7f808fb82bf0 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #16 0x7f814b8a4b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f814a74a6ba in start_thread (arg=0x7f7fe77fe700) at pthread_create.c:333 #18 0x7f814b1b182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 28 (Thread 0x7f7fe7fff700 (LWP 7493)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f814b8a5a4b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f808fb8107f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #3 0x7f808fb85078 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f808fb8026d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f808fb850d2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f808fb8026d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f808fb850d2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f808fb8026d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x
[plasmashell] [Bug 375404] New: Panel set to autohide is visible after boot until we hover it
https://bugs.kde.org/show_bug.cgi?id=375404 Bug ID: 375404 Summary: Panel set to autohide is visible after boot until we hover it Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: kont...@soee.pl Target Milestone: 1.0 The auto hide feature of the panel has small problem when we boot our system. Panel stays visible util we hover it and move out mouse cursor from it. It seems that then hide action is triggered but not after session starts. I noticed also that i we logout and login again (not reboot), this panel gets hidden so maybe all this have something to do how fast session loads etc. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 375534] New: Crash on saving chnages - Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=375534 Bug ID: 375534 Summary: Crash on saving chnages - Segmentation fault Product: kmenuedit Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kont...@soee.pl Target Milestone: --- Application: KDE Menu Editor (kmenuedit), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4bc1768940 (LWP 5669))] Thread 2 (Thread 0x7f4bbd2dd700 (LWP 5671)): #0 0x7f4bd277569d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4bc96be740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4bc967ae84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4bc967b340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f4bc967b4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f4bcf1ac23b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4bcf156cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4bcef7bfb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f4bd2dd17a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f4bcef80b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f4bcb5216ba in start_thread (arg=0x7f4bbd2dd700) at pthread_create.c:333 #11 0x7f4bd278582d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f4bc1768940 (LWP 5669)): [KCrash Handler] #6 0x7f4bcf185c93 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4bcf1863b7 in QObject::disconnectImpl(QObject const*, void**, QObject const*, void**, QMetaObject const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f4bbe652ee3 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/KDEPlasmaPlatformTheme.so #9 0x7f4bcfbb14a0 in QMenu::actionEvent(QActionEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f4bcfa8b398 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f4bcfbb748b in QMenu::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f4bcfa4489c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f4bcfa4c296 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f4bcf158cf8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f4bcfa8276c in QWidget::removeAction(QAction*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f4bcfa3dd27 in QAction::~QAction() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f4bcfa8e2ed in QWidgetAction::~QWidgetAction() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f4bd073fe09 in KActionMenu::~KActionMenu() () from /usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #19 0x7f4bcf1822e3 in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f4bcfa86d94 in QWidget::~QWidget() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f4bd1c4eb11 in KMainWindow::~KMainWindow() () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #22 0x7f4bd2a71b5a in ?? () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kmenuedit.so #23 0x7f4bd2a71c59 in ?? () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kmenuedit.so #24 0x7f4bcf184a50 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f4bcfa8b58b in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f4bcfb884cb in QMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f4bd1c50fa7 in KMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #28 0x7f4bd1c960d5 in KXmlGuiWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #29 0x7f4bcfa4489c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7f4bcfa4c296 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7f4bcf158cf8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f4bcf15b3bb in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f4bcf1abe13 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7f4bc967b1a7 in g_main_context
[plasmashell] [Bug 375802] New: Widget does not scale properly when configured to show city in current timezone
https://bugs.kde.org/show_bug.cgi?id=375802 Bug ID: 375802 Summary: Widget does not scale properly when configured to show city in current timezone Product: plasmashell Version: 5.9.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: kont...@soee.pl Target Milestone: 1.0 Created attachment 103736 --> https://bugs.kde.org/attachment.cgi?id=103736&action=edit City name If we configure digital clock to show city in current timezone, the city name renders outside widget area (see attached screenshot). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388883] New: Install and Remove buttons on the lists should have different styles/states
https://bugs.kde.org/show_bug.cgi?id=33 Bug ID: 33 Summary: Install and Remove buttons on the lists should have different styles/states Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kont...@soee.pl Target Milestone: --- With the latest patches lists have more condensed layout but one thing that could be improved is styles of the button next to title - it should be different for Install and Remove actions. IMO `more` visible should be button when it represents Install action and less visible for Remove action :) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388974] New: Make search field sticky
https://bugs.kde.org/show_bug.cgi?id=388974 Bug ID: 388974 Summary: Make search field sticky Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kont...@soee.pl Target Milestone: --- Atm. if our Discover window is small the left column content will be scrollable. If we scroll down the content search field won't be visible. Maybe search field could be sticky and stay always visible in the left column. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380386] New: Task manager items icons are aligned different when sound indicator is rendered
https://bugs.kde.org/show_bug.cgi?id=380386 Bug ID: 380386 Summary: Task manager items icons are aligned different when sound indicator is rendered Product: plasmashell Version: 5.10.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: kont...@soee.pl CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 105789 --> https://bugs.kde.org/attachment.cgi?id=105789&action=edit Icon Task Manager on wide vertical panel If we put Icon Task Manager on wide vertical panel than application icons are aligned differently if application plays sound (the sound indicator is rendered): - if the sound indicator is visible than application icon is aligned to the left side - if sound indicator icon is not rendered than application icon is centered Please check attached image. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 370521] [Regresion] SDDM breeze theme unable to change backgound.
https://bugs.kde.org/show_bug.cgi?id=370521 soee changed: What|Removed |Added CC||kont...@soee.pl --- Comment #11 from soee --- In Neon 5.9.1 if i set background image for sddm (through KCM) is has only white color as a background then. KCM is broken for a long time already (doesn't show selected image preview, wallpaper is not set properly - white color instead of image). Bug should be reopened IMO. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching
https://bugs.kde.org/show_bug.cgi?id=342186 --- Comment #29 from soee --- As it still exists in Plasma 5.9 and doesn't looks like it will be fixed in 5.10, here is my workaround for it: Check activities list to see theit ID-s: #qdbus org.kde.ActivityManager /ActivityManager/Activities ListActivities In System Settings -> Shorcuts define Custom Shortcuts: New -> Global Shortcus -> DBUS Command remote program: org.kde.ActivityManager remote object: /ActivityManager/Activities function: SetCurrentActivity arguments: [paste activity ID] -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 384351] New: Make Update All button more visible/reachable after we scroll down the packages list
https://bugs.kde.org/show_bug.cgi?id=384351 Bug ID: 384351 Summary: Make Update All button more visible/reachable after we scroll down the packages list Product: Discover Version: 5.10.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kont...@soee.pl Target Milestone: --- If we have long list with packages to be updated often we scroll down to check what will be updated. From the UI/UX point of view we have a small issue here, where Update All button will be hidden when we scroll down the list. We have to scroll to top again to reach the button again. - maybe this top bar with this button should be sticky above the list and always visible - maybe we could should the same button under the list - maybe we should add sctoll to top button at the bottom For me first option would be most efficient. Share your opinions :-) -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 374547] New: [UI/UX] Setting 2 rows with launcher names and popup enabled makes widget unreadable
https://bugs.kde.org/show_bug.cgi?id=374547 Bug ID: 374547 Summary: [UI/UX] Setting 2 rows with launcher names and popup enabled makes widget unreadable Product: kdeplasma-addons Version: 5.8.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Quicklaunch Assignee: now...@gmail.com Reporter: kont...@soee.pl Target Milestone: --- Created attachment 103193 --> https://bugs.kde.org/attachment.cgi?id=103193&action=edit Image presenting mentioned configuration If we place quicklaunch widget on the panel (thin and horizontal) and configure it to use more than 1 row (it can be 2 or more), display names and show popup than whole widget is totally unreadable. Maybe we could somehow check if space for each launcher (icon and name) is pretty small and than just render icon without names. At the moment with more than 1 row on thin panels often only fist/one letter of the launcher name is visible and icon hidden (imo icon should have priority). -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 374547] [UI/UX] Setting 2 rows with launcher names and popup enabled makes widget unreadable
https://bugs.kde.org/show_bug.cgi?id=374547
--- Comment #2 from soee ---
When widget is placed on panel can we check its width and based on that
calculate:
widget width / (total items / rows) = item width
and than:
if (item width < X) {
render only icons
}
?
--
You are receiving this mail because:
You are watching all bug changes.
[kdeplasma-addons] [Bug 375137] New: Rounding error for pastebin button results with a bit different look
https://bugs.kde.org/show_bug.cgi?id=375137 Bug ID: 375137 Summary: Rounding error for pastebin button results with a bit different look Product: kdeplasma-addons Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: QuickShare Assignee: aleix...@kde.org Reporter: kont...@soee.pl CC: plasma-b...@kde.org Target Milestone: --- The Pastebin button has some strange style (different than other) due to rounding problem. See how it behaves on drag/scroll: https://www.youtube.com/watch?v=vtjMTSoVj-8 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375225] New: Discover started to crash - Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=375225 Bug ID: 375225 Summary: Discover started to crash - Segmentation fault Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kont...@soee.pl Target Milestone: --- Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f79057958c0 (LWP 9785))] Thread 43 (Thread 0x7f782bfff700 (LWP 9829)): #0 0x7f7901ab8b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f78fd0a739c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f78fd0a7722 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7888555916 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f78fd0cdbc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f78fef4d6ba in start_thread (arg=0x7f782bfff700) at pthread_create.c:333 #6 0x7f7901ac482d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 42 (Thread 0x7f7848dbd700 (LWP 9828)): #0 0x7f7901ab469d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f78fd0ea740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f78fd0a6e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78fd0a7340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f78fd0a74ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f78fd0a74e9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f78fd0cdbc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f78fef4d6ba in start_thread (arg=0x7f7848dbd700) at pthread_create.c:333 #8 0x7f7901ac482d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 41 (Thread 0x7f78497fa700 (LWP 9827)): #0 0x7f79024b8009 in QMutex::lock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f79026eb98f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f78fd0a692d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78fd0a72cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f78fd0a74ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f79026ec23b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7902696cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f79024bbfb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f79024c0b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f78fef4d6ba in start_thread (arg=0x7f78497fa700) at pthread_create.c:333 #10 0x7f7901ac482d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 40 (Thread 0x7f7849ffb700 (LWP 9826)): #0 0x7f79026eb9c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f78fd0a692d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f78fd0a72cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78fd0a74ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f79026ec23b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7902696cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f79024bbfb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f79024c0b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f78fef4d6ba in start_thread (arg=0x7f7849ffb700) at pthread_create.c:333 #9 0x7f7901ac482d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 39 (Thread 0x7f784a7fc700 (LWP 9825)): #0 0x7f78fd0ebac9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f78fd0a6ddc in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f78fd0a7340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78fd0a74ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f79026ec23b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7902696cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f79024bbfb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f79024c0b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f78fef4d6ba in start_thread (arg=0x7f784a7fc700) at pthread_create.c:333 #9 0x7f7901ac482d in clone () at ../sysdeps/unix/
[Breeze] [Bug 370248] The Person Widget is using the Desktop icon in ...
https://bugs.kde.org/show_bug.cgi?id=370248 soee changed: What|Removed |Added CC||kont...@soee.pl --- Comment #2 from soee --- I can confirm this bug on Plasma 5.9-dev (Neon dev/unstable). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365097] New: Krunner has broken shadow / corners
https://bugs.kde.org/show_bug.cgi?id=365097 Bug ID: 365097 Summary: Krunner has broken shadow / corners Product: plasmashell Version: 5.6.95 Platform: Neon Packages URL: http://i.imgur.com/8qUPVhm.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kont...@soee.pl CC: bhus...@gmail.com, plasma-b...@kde.org As attached image shows, krunner widget has broken corner / shadows. Reproducible: Always Steps to Reproduce: 1. Run krunner 2. See broken corners / shadows Actual Results: Two bottom corners are broken and makes teh shadow looks broken. Expected Results: Whole shadow around krunner widget shoudl be visible without whitespaces. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365099] New: Settings window - scrollbar for smaller window covers buttons
https://bugs.kde.org/show_bug.cgi?id=365099 Bug ID: 365099 Summary: Settings window - scrollbar for smaller window covers buttons Product: plasmashell Version: 5.6.95 Platform: Neon Packages URL: http://i.imgur.com/Fo6tBVM.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: kont...@soee.pl If we open Systray settings window and got to Elements section, than if scrollbar is rendered (for smaller sized window) it hovers the 'cancel' buttons for shortcuts (see attached screenshot). Reproducible: Always Steps to Reproduce: 1. Open Systray settings window 2. Go to Elements section 3. If scrollbar isnot visible, make teh window a bit smaller to have it 4. Observe how the scrollbar covers buttons Actual Results: 'Cancel' buttons are partially covered by scrollbar. Expected Results: Scrollbar should be rendered next to buttons not cover them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365097] Krunner has broken shadow / corners
https://bugs.kde.org/show_bug.cgi?id=365097 --- Comment #4 from soee --- Indeed it was cache issue. I have removed ~/.cache and /var/tmp/kdecache-$USER and the problem is gone. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365111] New: Widgets explorer is missing a lot of icons for its items
https://bugs.kde.org/show_bug.cgi?id=365111 Bug ID: 365111 Summary: Widgets explorer is missing a lot of icons for its items Product: plasmashell Version: 5.6.95 Platform: Neon Packages URL: https://youtu.be/yYed-56WJmw OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kont...@soee.pl CC: bhus...@gmail.com, plasma-b...@kde.org As presented on the video (see attached link) widgets explorer items are missing their unique icons. We see blank document icons instead. Reproducible: Always Steps to Reproduce: 1. Open widgets explorer 2. See a lot of missing icons (white document icon instead) 3. Actual Results: We see a lot of missing icons wor presented widgets. Expected Results: Each widget in the explorer shoudl have own, unique icon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365111] Widgets explorer is missing a lot of icons for its items
https://bugs.kde.org/show_bug.cgi?id=365111 --- Comment #2 from soee --- (In reply to Marco Martin from comment #1) > screenshot? There is a link to video in this bug report but ok here is the screenshot: -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365111] Widgets explorer is missing a lot of icons for its items
https://bugs.kde.org/show_bug.cgi?id=365111 --- Comment #3 from soee --- Created attachment 99862 --> https://bugs.kde.org/attachment.cgi?id=99862&action=edit Missing icons in widgets explorer -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365111] Widgets explorer is missing a lot of icons for its items
https://bugs.kde.org/show_bug.cgi?id=365111 --- Comment #8 from soee --- Also various applications (liek Clementine) are missing icon when docked in systray - we see only blank page icon. Is this related to this bug or shall i open new one? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365111] Widgets explorer is missing a lot of icons for its items
https://bugs.kde.org/show_bug.cgi?id=365111 --- Comment #9 from soee --- Created attachment 99874 --> https://bugs.kde.org/attachment.cgi?id=99874&action=edit Missing icon in systray example on Clementine This is how the missing icon looks in systry -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365097] Krunner has broken shadow / corners
https://bugs.kde.org/show_bug.cgi?id=365097 --- Comment #5 from soee --- I don't know why but this problem is back. It was working fin for some time but all of sudden is roken again and i'm not sure why :/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365097] Krunner has broken shadow / corners
https://bugs.kde.org/show_bug.cgi?id=365097 --- Comment #6 from soee --- Created attachment 99875 --> https://bugs.kde.org/attachment.cgi?id=99875&action=edit Other dropdowns have the same problem The dropdown in panel settings has the same issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365137] New: Application minimaizng animation is rendered to the removed taska manager instance
https://bugs.kde.org/show_bug.cgi?id=365137 Bug ID: 365137 Summary: Application minimaizng animation is rendered to the removed taska manager instance Product: plasmashell Version: 5.6.95 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: kont...@soee.pl CC: plasma-b...@kde.org I have 2 screens setup: latop + external monitor connected through hdmi. Both screens have separate panels with tasks managers configured a bit different. I have application runnig on screen 2. Than i have added new default panel on screen 1 and removed it. Now my application minimize effect direction points to removed panel/task manager so ot is completly wrong :) Reproducible: Always Steps to Reproduce: 1. Run some app and have it displayed on current panel task manager 2. Add next/new defaulr panel to the desktop 3. Remove this new panel Actual Results: Running application will be minimized to the direction of removed panel - task manager it contained not the existing instance. Expected Results: Application should be minimized to the existing task manager instance on the current screen not removed one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365137] Application minimizing animation is rendered to the removed task manager instance
https://bugs.kde.org/show_bug.cgi?id=365137 soee changed: What|Removed |Added Summary|Application minimaizng |Application minimizing |animation is rendered to|animation is rendered to |the removed taska manager |the removed task manager |instance|instance -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365137] Application minimizing animation direction points to the removed task manager instance
https://bugs.kde.org/show_bug.cgi?id=365137 soee changed: What|Removed |Added Summary|Application minimizing |Application minimizing |animation is rendered to|animation direction points |the removed task manager|to the removed task manager |instance|instance -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342873] After removing a second panel with taskbar, windows still animate minimization into it
https://bugs.kde.org/show_bug.cgi?id=342873 --- Comment #7 from soee --- This bug exists in Plasma 5.7. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365150] New: Running Discover for the first time - see not too detailed message about Appstream
https://bugs.kde.org/show_bug.cgi?id=365150 Bug ID: 365150 Summary: Running Discover for the first time - see not too detailed message about Appstream Product: Discover Version: 5.6.95 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kont...@soee.pl If we run Discover for the first time we will see hilighted message: "Please make sure that Appstream is properly setup on your system". This message doesn't explain how/what to do to check if Appstream is ssetup as it should. Please add more detailed message what steps user should take to make sure all is configured as required by Discover. Reproducible: Always Steps to Reproduce: 1. Run Discover first time Actual Results: See simple message "Please make sure that Appstream is properly setup on your system" Expected Results: We shoudl see more detailed message that explains what user has to do to check the setup. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 365150] Running Discover for the first time - see not too detailed message about Appstream
https://bugs.kde.org/show_bug.cgi?id=365150 --- Comment #1 from soee --- Created attachment 99886 --> https://bugs.kde.org/attachment.cgi?id=99886&action=edit Current message rendered in Discover -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344076] Panels appear on top of each other when switching back to single-monitor
https://bugs.kde.org/show_bug.cgi?id=344076 soee changed: What|Removed |Added CC||kont...@soee.pl --- Comment #11 from soee --- This problem exists sometimes after system reboot - panel from my laptop screen jumps to connected screen and covers the one that exists there. I was asked to post 'working' plasma-org.kde.plasma.desktop-appletsrc file content and after panel jumps/is moved to wrong screen. So check the attached files for them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344076] Panels appear on top of each other when switching back to single-monitor
https://bugs.kde.org/show_bug.cgi?id=344076 --- Comment #13 from soee --- Created attachment 100036 --> https://bugs.kde.org/attachment.cgi?id=100036&action=edit PANEL MOVED plasma-org.kde.plasma.desktop-appletsrc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344076] Panels appear on top of each other when switching back to single-monitor
https://bugs.kde.org/show_bug.cgi?id=344076 --- Comment #12 from soee --- Created attachment 100035 --> https://bugs.kde.org/attachment.cgi?id=100035&action=edit WORKING plasma-org.kde.plasma.desktop-appletsrc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365706] New: Dialog position is not updated properly
https://bugs.kde.org/show_bug.cgi?id=365706 Bug ID: 365706 Summary: Dialog position is not updated properly Product: plasmashell Version: 5.7.1 Platform: Neon Packages URL: https://www.youtube.com/watch?v=BUTgDLr-Kkg OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: kont...@soee.pl As shown on the video, after one panel is resized the dialog postion on smaller panel is not updated and there is an empty space between panel and opened dialog (like systray extended view or kicker). This might be related to multi screen setup. Reproducible: Always Steps to Reproduce: 1. Create 2 panels at the bottom of the screens 2. Make one panel higher or smaller than the second one 3. Open systray extended view or kicker on smaller panel and observe empty space between panel and dialog. Actual Results: There is an epty space between panel and dialog. Expected Results: Dialog shoudl always stick to the panel. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 365947] New: Icons inside toolbutton are not centered vertically/horizontally
https://bugs.kde.org/show_bug.cgi?id=365947 Bug ID: 365947 Summary: Icons inside toolbutton are not centered vertically/horizontally Product: frameworks-plasma Version: 5.24.0 Platform: Neon Packages URL: http://i.imgur.com/6PkUAIW.jpg OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: kont...@soee.pl Icons inside toolbutton are not centered vertically/horizontally (close button for notification or windows in present mode) Reproducible: Always Steps to Reproduce: 1. Load some element that uses toolbutton, it can be dummy (notify-send test) or real notification or trigger the present windows effect (and hover one of them) 2. The tollbutton for closing those elements has icon inside that is not centered vertically/horizontally 3. Actual Results: Icon inside toolbutton is not centered v/h Expected Results: Icon inside toolbutton should be centered v/h -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 366156] New: ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=366156 Bug ID: 366156 Summary: ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics Product: ksmserver Version: 5.7.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: kont...@soee.pl Each time i try to switch GPU profile from nvidia to intel on a laptop with Optimus technology the ksmserver crashes. I think this started since upgrade to Plasma 5.7 or latest Frameworks (5.23/5.24). Reproducible: Always Steps to Reproduce: 1. Work/have nvidia GPU set as active on your machine 2. Using nvidia-settings GUI or command line change GPU profile to intel 3. Try to logout and login again (as it it required to make the changes work) 4. After Logout button is clicked ksmserver crashes Actual Results: ksmserver crashes when trying to logout after we try to switch from nvidia to intel GPU profile. Having the crash window visible (without decorations) we can save stack trace and/or click on "Restart application" button and sometimes clicking it moves us to sddm and sometimes screen becomes unresponsive. Expected Results: After GPU profile is changed from nvidia to intel and we click on Logout button, we should be moved to sddm without any crashes. I have attached crash report so it might help finding the problem source. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 366156] ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=366156 --- Comment #1 from soee --- Created attachment 100326 --> https://bugs.kde.org/attachment.cgi?id=100326&action=edit ksmserver-20160726-175540.kcrash.txt Crash report. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 366156] ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=366156 --- Comment #2 from soee --- I should also mention that doing it from the other side - switching from intel to nvidia profile - does not generate any crash. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 366156] ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=366156 --- Comment #3 from soee --- Created attachment 100327 --> https://bugs.kde.org/attachment.cgi?id=100327&action=edit .xsession-errors file content I removed one text that spammed this file (more than 13.00 lines were): kde.systemtray: Wrong IconThemePath "/home/soee/.dropbox-dist/dropbox-lnx.x86_64-6.4.14/images" : too short or does not end with 'icons' -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 366156] ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=366156 --- Comment #4 from soee --- Typo: the removed text was in more than 13.000 lines. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 366158] New: Switching sections inside Info module results with small lag when rendering their content
https://bugs.kde.org/show_bug.cgi?id=366158
Bug ID: 366158
Summary: Switching sections inside Info module results with
small lag when rendering their content
Product: kinfocenter
Version: 5.7.2
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: hubn...@gmail.com
Reporter: kont...@soee.pl
When switching Info module sections that use some variables loaded for example
from files, than we see for a moment those variables placeholders like
{NameVersionLabel} or {UrlLabel} in About System section.
See attached screenshot to see it.
Reproducible: Always
Steps to Reproduce:
1. Open Info module
2. Switch between Memory and About System sections
3. Observ the lag when loading and replacing placeholders in About System
section content
Actual Results:
For a moment we see variables placeholders like {NameVersionLabel}
Expected Results:
Placeholders hsould never be seen - just final output
--
You are receiving this mail because:
You are watching all bug changes.
[kinfocenter] [Bug 366158] Switching sections inside Info module results with small lag when rendering their content
https://bugs.kde.org/show_bug.cgi?id=366158 --- Comment #1 from soee --- Created attachment 100329 --> https://bugs.kde.org/attachment.cgi?id=100329&action=edit About System kcm content with variables placeholders inside Info mdule -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 366405] New: Progress bar does not work as expected for package download status
https://bugs.kde.org/show_bug.cgi?id=366405 Bug ID: 366405 Summary: Progress bar does not work as expected for package download status Product: Discover Version: 5.7.3 Platform: Neon Packages URL: https://www.youtube.com/watch?v=YQDvzOGFohg OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Updater Assignee: aleix...@kde.org Reporter: kont...@soee.pl hen we are updating packages than for each of them progress bar is rendered. For some reason it reaches ~ 75% for each of packages and that for a moment all progress bars are set to ~ 15% and packages start to install. See link to the video - it demonstrates this behaviour. Reproducible: Always Steps to Reproduce: 1. Open Discover Updater when there are some updates available 2. Click Update 3. Observe progress bars (they all reach ~ 75% than it jumps to ~ 15%) 4. See packages beeing installed Actual Results: Progress par for package download reaches ~ 75% than jumps to 15%. Expected Results: Progress bar should reach 100% for package that is downloaded and never jump to lower value. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 366410] New: Search field should have 'clear' button
https://bugs.kde.org/show_bug.cgi?id=366410 Bug ID: 366410 Summary: Search field should have 'clear' button Product: Discover Version: 5.7.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kont...@soee.pl The main search field should have like other similiar elements in KDE Application the "Clear" button. Please check attached image for details. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 366410] Search field should have 'clear' button
https://bugs.kde.org/show_bug.cgi?id=366410 --- Comment #1 from soee --- Created attachment 100452 --> https://bugs.kde.org/attachment.cgi?id=100452&action=edit Second element shows search field with button to clear entered text -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 366412] New: At the upper left corner of the menu icon there is 3-4 pixels artifact
https://bugs.kde.org/show_bug.cgi?id=366412 Bug ID: 366412 Summary: At the upper left corner of the menu icon there is 3-4 pixels artifact Product: Discover Version: 5.7.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kont...@soee.pl Between search field and hamburger menu button there are some 3-4 dark pixels (probably some small shape of something). See attached screenshot for more details. Reproducible: Always Steps to Reproduce: 1. Open Discover -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 366412] At the upper left corner of the menu icon there is 3-4 pixels artifact
https://bugs.kde.org/show_bug.cgi?id=366412 --- Comment #1 from soee --- Created attachment 100454 --> https://bugs.kde.org/attachment.cgi?id=100454&action=edit Artifact near search field and menu button -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 366478] New: Make systray icon monochrmoe dark/light wariants
https://bugs.kde.org/show_bug.cgi?id=366478 Bug ID: 366478 Summary: Make systray icon monochrmoe dark/light wariants Product: rsibreak Version: 0.12 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: aa...@kde.org Reporter: kont...@soee.pl It would be great if we could have an option to use monochrome icon in systray. Desktop environments like Plasma or GNOME allow to set different themes for users desktops and usually icons in systray are all monochrome. When it comes to KDE Plasma, i'm sure that Visual Design Group could provide monochrome version if someone could implement it. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 366478] Make systray icon monochrmoe dark/light wariants
https://bugs.kde.org/show_bug.cgi?id=366478 --- Comment #1 from soee --- Created attachment 100483 --> https://bugs.kde.org/attachment.cgi?id=100483&action=edit RSIBreak icons compared to other systray items on Plasma desktop -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 366478] Make systray icon monochrome dark/light variants
https://bugs.kde.org/show_bug.cgi?id=366478 soee changed: What|Removed |Added Summary|Make systray icon |Make systray icon |monochrmoe dark/light |monochrome dark/light |wariants|variants -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 369857] New: Images from the wallpapers list can't be removed
https://bugs.kde.org/show_bug.cgi?id=369857 Bug ID: 369857 Summary: Images from the wallpapers list can't be removed Product: kscreenlocker Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm Assignee: plasma-b...@kde.org Reporter: kont...@soee.pl CC: bhus...@gmail.com, mgraess...@kde.org It looks like Screen Locking kcm for selecting wallaper uses the same component that we see in desktop settings. The problem with it when using inside kcm is that we can't remove and image from the wallpapers list. When having opened desktop settings, wallpaper can be removed if we mark it to remove and close the window. Inside Screen Locking kcm if we do the same and close the window the wallpaper is never removed. Reproducible: Always Steps to Reproduce: 1. Open Screen Locking kcm 2. Go to Wallpaper tab and mark any image to be removed from the list 3. Close the window 4. Open Screen Locking kcm again Actual Results: Image marked to remove is still here. Expected Results: Image marked to be remove should be removed. >From the UX, UI point of view this is pretty strange how this wallpapers removal works atm. I think if we mark any image to remove than "Apply" button should switch to active and we should be able to apply changes by clicking on it and not waiting to close the window to have those images removed. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 369857] Images from the wallpapers list can't be removed
https://bugs.kde.org/show_bug.cgi?id=369857 --- Comment #2 from soee --- (In reply to Kai Uwe Broulik from comment #1) > Images marked for deletion are only removed when you apply the dialog. While > this isn't very ideal and obvious, it's the same for the desktop and lock > screen settings. Only if you Apply it will remove the image from the list, > just closing the dialog won't, in both cases. By "apply" you mean pressing the Apply button or OK? If we mark image for deletion that Apply button is never active either in desktop settings or kcm. Pressing OK button indeed removes image when we are in desktop settings but does not work inside kcm. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 371658] New: Items on the sources list in Settings section are rendered outside layout borders
https://bugs.kde.org/show_bug.cgi?id=371658 Bug ID: 371658 Summary: Items on the sources list in Settings section are rendered outside layout borders Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kont...@soee.pl Inside Settings section on sources list we have often entries with long text and such text is than rendered outside current layout borders. Those texts should fit to current windows size (we should hide or cut to long content or break it to new line etc.). Reproducible: Always Steps to Reproduce: 1. Open Discover 2. Navigate to Settings view 3. Try to resize window to a smaller size Actual Results: Observe how items on the list are rendered outside layout if they d not fix actual window size Expected Results: The items text should be hidden on cut to prevent rendering it outside layout. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 371658] Items on the sources list in Settings section are rendered outside layout borders
https://bugs.kde.org/show_bug.cgi?id=371658 --- Comment #1 from soee --- Created attachment 101773 --> https://bugs.kde.org/attachment.cgi?id=101773&action=edit Image shows how sources with long text are rendered outside layout borders -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368803] New: Panel shadow is not restored with compositor
https://bugs.kde.org/show_bug.cgi?id=368803 Bug ID: 368803 Summary: Panel shadow is not restored with compositor Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kont...@soee.pl CC: bhus...@gmail.com, plasma-b...@kde.org I have some apps like Steam or single games windows set to disable compositor when they run. This works pretty good. The only small issue is that when i close such app, compositor is restored but panel shadow is missing. To bring it back i have to toggle desktop effects ALT + SHIFT + F12. Reproducible: Always Steps to Reproduce: 1. Configure some app to disable compositor when running. 2. Run app 3. Close app Actual Results: Panel shadow is missing after compositor was restored. Expected Results: Panel shadow should be rendered after compositor ws enabled again. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 369116] New: [FEATURE] Make Quicklaunch widget configurable per activity
https://bugs.kde.org/show_bug.cgi?id=369116 Bug ID: 369116 Summary: [FEATURE] Make Quicklaunch widget configurable per activity Product: kdeplasma-addons Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Quicklaunch Assignee: now...@gmail.com Reporter: kont...@soee.pl It would be cool to have an option to confgure Quicklaunch widget to use launchers configured for current activity only. So by default it would use some global setup but if user check option to restrict configuration for current activity, then it will show only launchers set and visible on this activity. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 366827] New: Widget location configuration is lost after reboot
https://bugs.kde.org/show_bug.cgi?id=366827 Bug ID: 366827 Summary: Widget location configuration is lost after reboot Product: kdeplasma-addons Version: 5.7.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: weather Assignee: kosse...@kde.org Reporter: kont...@soee.pl CC: plasma-b...@kde.org If we set location for the widget it is lost after system reboot and thus widget show only dummy icon without any weather data. Reproducible: Always Steps to Reproduce: 1. Add widget 2. Select location 3. Reboot system Actual Results: Location configuration is lost after reboot Expected Results: Location shoudl be always available after it was configured. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 366828] New: When we type location in "Location" field and press ENTER key, configuration window gets closed
https://bugs.kde.org/show_bug.cgi?id=366828 Bug ID: 366828 Summary: When we type location in "Location" field and press ENTER key, configuration window gets closed Product: kdeplasma-addons Version: 5.7.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: weather Assignee: kosse...@kde.org Reporter: kont...@soee.pl CC: plasma-b...@kde.org If we type any location name inside "Location" field in configuration window than natural action is to hit ENTER key to search for given place. But if we hit ENTER than configuration window is closed. Reproducible: Always Steps to Reproduce: 1. Open widget configuration window 2. Type some location name 3. Hit ENTER key Actual Results: Configuration window gets closed. Expected Results: Widget should search for selected location when ENTER key is pressed after name was entered. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 366827] Widget location configuration is lost after reboot
https://bugs.kde.org/show_bug.cgi?id=366827 --- Comment #2 from soee --- It is lost. There are no any signs of it beeing restored. I will test more with cable connection also as not im using LTE (usb modem with sim). So when i boot my system modem needs ~ 2-3 min. to connect but when rebooting it is usually active at start. -- You are receiving this mail because: You are watching all bug changes.
