[plasma-nm] [Bug 400310] Changing wifi network crashes applet
https://bugs.kde.org/show_bug.cgi?id=400310 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #1 from Jan Grulich --- How do you mean that the applet crashes, does plasmashell restart completely? Do you get a drkonqi window with a backtrace? Or you just lose all visible networks when you attempt to connect to another one? Can you provide NetworkManager log? You can find information how to get it here https://techbase.kde.org/Projects/Solid/Plasma-nm. Can you run "nmcli -f all device wifi list" to see if there are any networks reported by NetworkManager and if so, check if there are any visible in the applet after this? -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 347486] don't grab keyboard focus by default by korgac dialog, improve position save/restore add size
https://bugs.kde.org/show_bug.cgi?id=347486 Laurent Montel changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kor ||ganizer/709d5c4eb9c81436c4b ||33e13756ff7750d95fa2b Resolution|--- |FIXED --- Comment #3 from Laurent Montel --- Git commit 709d5c4eb9c81436c4b33e13756ff7750d95fa2b by Laurent Montel. Committed on 26/10/2018 at 05:24. Pushed by mlaurent into branch 'master'. Patch from David Fries Summary Instead of saving position sometimes (application close, suspend reminder), save at each point the dialog hides, dismiss reminder, dismiss all, escape or window close, etc. In addition to saving the position, save the geometry to get the size as well, that way if the user wants it bigger (or smaller) the only have to do it once. The logic was show, move, which would run in that order, the window shows, then it moves to the correct location which looks bad, restore the position & size, then show, so it appears in the final location. Test Plan A quicker way to test this is with a previous patch "Show Reminders" dock menu item option, as opposed to setting a bunch of reminders and waiting for them to go off. before patch is applied/after patch is applied behaviors move the Reminder window to a corner of the screen, show the Reminder window [ before/after it will appear at the same location] move the Reminder window to a different corner, press escape, show the Reminder window [ before the escape position didn't save and it appears in the previous location, after it appears in the escape position] make the Reminders window large, show Reminders window [ before/after it is the large size] exit korgac, run korgac, show Reminders window [ before it is back to the previous normal size, after it is the larger size] Reviewers: mlaurent, dvratil Reviewed By: dvratil Subscribers: dvratil, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D16245 M +26 -11 korgac/alarmdialog.cpp M +2-1korgac/alarmdialog.h https://commits.kde.org/korganizer/709d5c4eb9c81436c4b33e13756ff7750d95fa2b -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 325752] Font weights not correctly recognized
https://bugs.kde.org/show_bug.cgi?id=325752 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 332110] Light and Hairline font weights cannot be installed at the same time
https://bugs.kde.org/show_bug.cgi?id=332110 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368345] kfontinst cannot show some font weights
https://bugs.kde.org/show_bug.cgi?id=368345 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400295] Some tray icons aren't highlighted upon hovering over them with mouse cursor
https://bugs.kde.org/show_bug.cgi?id=400295 Nate Graham changed: What|Removed |Added CC||n...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Nate Graham --- "Updates" also has a hover effect. Same with 3rd-party icons provided by Dropbox, Telegram, and Riot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400315] Freezing when running apps
https://bugs.kde.org/show_bug.cgi?id=400315 Nate Graham changed: What|Removed |Added Resolution|--- |UPSTREAM CC||n...@kde.org Status|REPORTED|RESOLVED URL||https://bugreports.qt.io/br ||owse/QTBUG-70760 --- Comment #1 from Nate Graham --- This is Qt bug introduced with 5.11.2: https://bugreports.qt.io/browse/QTBUG-70760 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400318] Window shadows Plasma panels when "Keep above others" feature is enabled
https://bugs.kde.org/show_bug.cgi?id=400318 Nate Graham changed: What|Removed |Added Component|generic-wayland |Panel Summary|Weird shadow affects plasma |Window shadows Plasma |panel when a window is |panels when "Keep above |maximized and "Keep above |others" feature is enabled |others" feature is enabled | CC||n...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Nate Graham --- This happens on X11 too. Apparently the panel counts as a window for the purpose of defining "others". Not sure whether this is intentional or a bug though. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400314] Release date should respect the format configured in the system settings
https://bugs.kde.org/show_bug.cgi?id=400314 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 400319] Kdevelop Quick Open Always show same file on multiple defination
https://bugs.kde.org/show_bug.cgi?id=400319 --- Comment #1 from TOM Harrison --- Created attachment 115908 --> https://bugs.kde.org/attachment.cgi?id=115908=edit example for demo this bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 400319] New: Kdevelop Quick Open Always show same file on multiple defination
https://bugs.kde.org/show_bug.cgi?id=400319 Bug ID: 400319 Summary: Kdevelop Quick Open Always show same file on multiple defination Product: kdevelop Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: QuickOpen Assignee: kdevelop-bugs-n...@kde.org Reporter: l12436...@gmail.com Target Milestone: --- SUMMARY Kdevelop Quick Open always show only certain file defination if function has multiple defination If a have a() define in a.c and b.c in different file. with different include. like Linux and DJGPP include. Kdevelop Quick open will only show all function defination in certain file. You can use the attachment file that could re-produce this issue. STEPS TO REPRODUCE 1. extract demo.tar.gz to /home/otakux/shm/ 2. project in "t" folder with kdevelop 3. find test2 function in quickopen OBSERVED RESULT Quick Open always show same file with those implement EXPECTED RESULT Quick open should show different file rather than same files. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 317803] Kmail2 renders colors based on the user system colors rather than the default colors browsers use.
https://bugs.kde.org/show_bug.cgi?id=317803 --- Comment #21 from Nate Graham --- Awesome, thanks Laurent! -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 400301] Command "Save as" not working
https://bugs.kde.org/show_bug.cgi?id=400301 --- Comment #1 from Simon Depiets --- If you amend the file then do Save As, does it work correctly ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400318] New: Weird shadow affects plasma panel when a window is maximized and "Keep above others" feature is enabled
https://bugs.kde.org/show_bug.cgi?id=400318 Bug ID: 400318 Summary: Weird shadow affects plasma panel when a window is maximized and "Keep above others" feature is enabled Product: plasmashell Version: 5.14.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 Created attachment 115907 --> https://bugs.kde.org/attachment.cgi?id=115907=edit screenshot STEPS TO REPRODUCE 1. open Kate under Wayland session and maximize it 2. right click the window decoration, mouseover "More actions", check "Keep above others" 3. OBSERVED RESULT Weird shadow affects the plasma panel. See the screenshot. EXPECTED RESULT no weird shadow. SOFTWARE VERSIONS Arch Linux KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51 Qt Version: 5.12 beta3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400316] Plasma crashed on Wayland when I clicked sound icon in the system tray
https://bugs.kde.org/show_bug.cgi?id=400316 David Edmundson changed: What|Removed |Added Resolution|--- |UPSTREAM CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- Crash is in Qt. I think it might be fixed, please reopen if it's an issue with Qt5.12 and we'll chase it up. Not a good investment otherwise. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400317] New: [Wayland] "Always on top" feature is not working with applets in the system tray
https://bugs.kde.org/show_bug.cgi?id=400317 Bug ID: 400317 Summary: [Wayland] "Always on top" feature is not working with applets in the system tray Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. start Wayland session, click some applet in the system tray (a popup shows up) 2. click the icon in the upper right corner to keep the popup always on top 3. open any window and maximize it OBSERVED RESULT the maximized window hides the applet popup EXPECTED RESULT applet popup should remain in foreground KDE neon Developer Edition KDE Plasma: 5.14.80 Qt: 5.11.2 KDE Frameworks: 5.52.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400316] New: Plasma crashed on Wayland when I clicked sound icon in the system tray
https://bugs.kde.org/show_bug.cgi?id=400316 Bug ID: 400316 Summary: Plasma crashed on Wayland when I clicked sound icon in the system tray Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 KDE neon Developer Edition KDE Plasma: 5.14.80 Qt: 5.11.2 KDE Frameworks: 5.52.0 Thread 12 (Thread 0x7f9021196700 (LWP 2235)): #0 0x7f9051adebf9 in __GI___poll (fds=0x7f90140054c0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f904b961439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f904b96154c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f905241951f in QEventDispatcherGlib::processEvents (this=0x7f9014000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #4 0x7f90523bd7fa in QEventLoop::exec (this=this@entry=0x7f9021195cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f90521e8bba in QThread::exec (this=this@entry=0x55ad47d0bdc0) at thread/qthread.cpp:525 #6 0x7f905637a826 in QQuickPixmapReader::run (this=0x55ad47d0bdc0) at util/qquickpixmapcache.cpp:934 #7 0x7f90521f3adb in QThreadPrivate::start (arg=0x55ad47d0bdc0) at thread/qthread_unix.cpp:367 #8 0x7f904ed1c6db in start_thread (arg=0x7f9021196700) at pthread_create.c:463 #9 0x7f9051aeb88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f900917e700 (LWP 3991)): #0 0x7f904ed229f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55ad4e0da994) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55ad4e0da940, cond=0x55ad4e0da968) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55ad4e0da968, mutex=0x55ad4e0da940) at pthread_cond_wait.c:655 #3 0x7f90521f494b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x55ad4e0da940) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=this@entry=0x55ad47d28978, mutex=mutex@entry=0x55ad47d28970, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7f90563f9b18 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x55ad47d28968) at scenegraph/qsgthreadedrenderloop.cpp:245 #6 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x55ad47d288f0) ---Type to continue, or q to quit--- at scenegraph/qsgthreadedrenderloop.cpp:709 #7 0x7f90563f9f4a in QSGRenderThread::run (this=0x55ad47d288f0) at scenegraph/qsgthreadedrenderloop.cpp:738 #8 0x7f90521f3adb in QThreadPrivate::start (arg=0x55ad47d288f0) at thread/qthread_unix.cpp:367 #9 0x7f904ed1c6db in start_thread (arg=0x7f900917e700) at pthread_create.c:463 #10 0x7f9051aeb88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f8ff0ed1700 (LWP 2271)): #0 0x7f904ed229f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55ad488726c0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55ad48872670, cond=0x55ad48872698) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55ad48872698, mutex=0x55ad48872670) at pthread_cond_wait.c:655 #3 0x7f90521f494b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x55ad48872670) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=this@entry=0x55ad4886e798, mutex=mutex@entry=0x55ad4886e790, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7f90563f9b18 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x55ad4886e788) at scenegraph/qsgthreadedrenderloop.cpp:245 #6 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x55ad4886e710) at scenegraph/qsgthreadedrenderloop.cpp:709 #7 0x7f90563f9f4a in QSGRenderThread::run (this=0x55ad4886e710) at scenegraph/qsgthreadedrenderloop.cpp:738 #8 0x7f90521f3adb in QThreadPrivate::start (arg=0x55ad4886e710) at thread/qthread_unix.cpp:367 #9 0x7f904ed1c6db in start_thread (arg=0x7f8ff0ed1700) at pthread_create.c:463 #10 0x7f9051aeb88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f903a347700 (LWP 2129)): #0 0x7f9051adebf9 in __GI___poll (fds=0x7f9030004a10, nfds=1, timeout=9991) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f904b961439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ---Type to continue, or q to quit--- #2 0x7f904b96154c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f905241951f in QEventDispatcherGlib::processEvents (this=0x7f903b20, flags=...) at
[Discover] [Bug 393079] When updating, package entries show changelogs, but app entries don't
https://bugs.kde.org/show_bug.cgi?id=393079 --- Comment #6 from Nate Graham --- Could be. The *packages* all have changelogs, so how can I determine whether or not the things that Discover determines to be apps have changelogs? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 205854] Automatic trash cleanup only triggers when a new file is trashed
https://bugs.kde.org/show_bug.cgi?id=205854 Nate Graham changed: What|Removed |Added Component|trash |Trash Version|unspecified |5.51.0 CC||kdelibs-b...@kde.org Product|kio |frameworks-kio Status|REPORTED|CONFIRMED Summary|Manual methods to trigger |Automatic trash cleanup |configured Trash cleanup|only triggers when a new ||file is trashed Ever confirmed|0 |1 Severity|wishlist|normal --- Comment #4 from Nate Graham --- Thanks for the info. #3 from your original three ideas seems like the sanest solution to me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400315] New: Freezing when running apps
https://bugs.kde.org/show_bug.cgi?id=400315 Bug ID: 400315 Summary: Freezing when running apps Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: looriin...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 When I running any application installed in my Arch system all desktop became freezed by 0.3-1 seconds. Also I noticed disk usage indicator blinking after unfreezing. Video demonstration: https://youtu.be/IHZnqeG7plA KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396351] "Remove" button changes to "Downloading" while a snap package is uninstalled
https://bugs.kde.org/show_bug.cgi?id=396351 Patrick Silva changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from Patrick Silva --- This bug is back on neon dev unstable. KDE Plasma Version: 5.14.80 Qt Version: 5.11.2 KDE Frameworks Version: 5.52.0 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 396697] Does not open with multi monitor on left screen when panel located right screen
https://bugs.kde.org/show_bug.cgi?id=396697 --- Comment #10 from JasonM --- Yes, this is the correct solution, I see now. Please apply this change! if (offscreenWindows.isEmpty()) return KWindowSystem::workArea().intersected(screenGeometry); return KWindowSystem::workArea(offscreenWindows).intersected(screenGeometry); -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400083] [Wayland] A message containing huge icon appears when I press ctrl+alt+esc and a thirdy-part icon theme is used
https://bugs.kde.org/show_bug.cgi?id=400083 --- Comment #6 from Patrick Silva --- (In reply to David Edmundson from comment #4) > And this only happens on the wayland session? yes. No message appears when I press the shorcut on X11. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 396697] Does not open with multi monitor on left screen when panel located right screen
https://bugs.kde.org/show_bug.cgi?id=396697 --- Comment #9 from JasonM --- This blog talks about some problems with having the KDE panel on a shared screen edge and struts: https://blog.martin-graesslin.com/blog/2016/08/panels-on-shared-screen-edges/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400083] [Wayland] A message containing huge icon appears when I press ctrl+alt+esc and a thirdy-part icon theme is used
https://bugs.kde.org/show_bug.cgi?id=400083 --- Comment #5 from David Edmundson --- It'll be more fallout from the p-f change a while back to make IconItem::implicitWidth be based on the icon size. Something that in hindsight was a mistake. Will fix. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 396697] Does not open with multi monitor on left screen when panel located right screen
https://bugs.kde.org/show_bug.cgi?id=396697 --- Comment #8 from JasonM --- When I print out the values of KWindowSystem::workArea(offScreenWindow) it's clear that width value is broken. It says 1774 with the parameter, and 9600 without a parameter or -1 as the default parameter. My desktop is 9600 wide (3840+3840+1920). Also the x value is wrong. When I move the KDE taskbar to a horizontal edge, then the values are good BUT there is also an offscreenWindow. I think the solution might be: if (offscreenWindows.isEmpty()) return KWindowSystem::workArea().intersected(screenGeometry); return KWindowSystem::workArea(offscreenWindows).intersected(screenGeometry); -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400083] [Wayland] A message containing huge icon appears when I press ctrl+alt+esc and a thirdy-part icon theme is used
https://bugs.kde.org/show_bug.cgi?id=400083 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #4 from David Edmundson --- And this only happens on the wayland session? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400313] Can't cancel snap transactions
https://bugs.kde.org/show_bug.cgi?id=400313 Aleix Pol changed: What|Removed |Added Summary|Button to abort Snap|Can't cancel snap |install is disabled or |transactions |unvailable | -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400312] Installed snaps don't have an icon
https://bugs.kde.org/show_bug.cgi?id=400312 Aleix Pol changed: What|Removed |Added Summary|Icon of Snap packages is|Installed snaps don't have |incorrect in the search |an icon |results | Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Aleix Pol --- First one is already fixed in kirigami master. The second isn't so I'll rename the bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400314] New: Release date should respect the format configured in the system settings
https://bugs.kde.org/show_bug.cgi?id=400314 Bug ID: 400314 Summary: Release date should respect the format configured in the system settings Product: Discover Version: 5.14.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: aleix...@kde.org Reporter: bugsefor...@gmx.com CC: jgrul...@redhat.com Target Milestone: --- Created attachment 115906 --> https://bugs.kde.org/attachment.cgi?id=115906=edit screenshot Discover shows the release date of flatpak packages. However, as we can see in the screenshot the format configured in the system settings (Formats kcm) is not respected. OBSERVED RESULT Release date shown in Discover does not respect the format configured in the system settings. EXPECTED RESULT Release date should respect the format configured in the system settings KDE neon Developer Edition KDE Plasma: 5.14.80 Qt: 5.11.2 KDE Frameworks: 5.52.0 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 396697] Does not open with multi monitor on left screen when panel located right screen
https://bugs.kde.org/show_bug.cgi?id=396697 --- Comment #7 from JasonM --- A hack that worked for me, changing the one line to: return KWindowSystem::workArea(/*offScreenWindows*/).intersected(screenGeometry); Allows yakuake to pop up on the monitors that it currently refuses to. I don't know what the proper fix is. In my case, offScreenWindows is an empty list, but it's also an empty list on the working monitors. I don't really understand what's going on in the code that's looking at "window struts". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400311] Wayland session crashes when I click "Copy to clipboard" button in Info Center
https://bugs.kde.org/show_bug.cgi?id=400311 David Edmundson changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Flags||Wayland+, X11-, ||ReviewRequest+ CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Made a fix that should prevent kwin crashing, though I think kinfocenter is crashing, so we'll probably have a bug to fix there afterwards. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 396697] Does not open with multi monitor on left screen when panel located right screen
https://bugs.kde.org/show_bug.cgi?id=396697 --- Comment #6 from JasonM --- The problem is that getDesktopGeometry returns 0,0,0,0 for width,height,x,y on the offending monitors. Looking at that function, I might actually figure it out here. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400313] Button to abort Snap install is disabled or unvailable
https://bugs.kde.org/show_bug.cgi?id=400313 --- Comment #1 from Patrick Silva --- Created attachment 115905 --> https://bugs.kde.org/attachment.cgi?id=115905=edit snap url - there is no button to abort install process -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400313] New: Button to abort Snap install is disabled or unvailable
https://bugs.kde.org/show_bug.cgi?id=400313 Bug ID: 400313 Summary: Button to abort Snap install is disabled or unvailable Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snap Backend Assignee: aleix...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 115904 --> https://bugs.kde.org/attachment.cgi?id=115904=edit button to abort install process is disabled When I click the button to install a Snap package in Discover, the button to abort install process is disabled. When I open Discover by clicking a snap url in the snap store and click the button to install the snap package, there is no button to abort the install process. See the screenshots please. OBSERVED RESULT button to abort snap install is disabled or unvailable. EXPECTED RESULT button is available and functional KDE neon Developer Edition KDE Plasma: 5.14.80 Qt: 5.11.2 KDE Frameworks: 5.52.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400312] Icon of Snap packages is incorrect in the search results
https://bugs.kde.org/show_bug.cgi?id=400312 --- Comment #1 from Patrick Silva --- Created attachment 115903 --> https://bugs.kde.org/attachment.cgi?id=115903=edit list of installed snaps icons are also wrong in the list of installed Snaps under "Settings". -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 205854] Manual methods to trigger configured Trash cleanup
https://bugs.kde.org/show_bug.cgi?id=205854 Matt Whitlock changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Matt Whitlock --- (In reply to Nate Graham from comment #1) > Is this still the way it works with KDE Frameworks 5.45 or greater? This report still applies as of KDE Frameworks 5.51. I have my Trash configured to delete files older than 90 days, yet I still have files with ctimes older than 90 days ago in my ~/.local/share/Trash/files directory. Indeed, I still have files with ctimes older than 97 days ago. $ find ~/.local/share/Trash/files -type f -ctime +97 | wc -l 2 $ find ~/.local/share/Trash/files -type f -ctime +98 | wc -l 0 If your assertion is that there is a periodic background process that should be cleaning expired files out of the Trash, then could you tell me how often this process is supposed to run? My KDE session has been logged in continuously for the last 14 days (since 11 October), yet evidently no process has cleaned the Trash. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 400312] New: Icon of Snap packages is incorrect in the search results
https://bugs.kde.org/show_bug.cgi?id=400312 Bug ID: 400312 Summary: Icon of Snap packages is incorrect in the search results Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snap Backend Assignee: aleix...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 115902 --> https://bugs.kde.org/attachment.cgi?id=115902=edit screenshot STEPS TO REPRODUCE 1. open Discover and search for something, let's say "photos" 2. 3. OBSERVED RESULT Snap packages listed in the search results have wrong icon. The icon is correct in their description page. See the screenshot. EXPECTED RESULT Snaps have correct icon in the search results. KDE neon Developer Edition KDE Plasma: 5.14.80 Qt: 5.11.2 KDE Frameworks: 5.52.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400311] Wayland session crashes when I click "Copy to clipboard" button in Info Center
https://bugs.kde.org/show_bug.cgi?id=400311 Patrick Silva changed: What|Removed |Added Summary|Wayland crashes when I |Wayland session crashes |click "Copy to clipboard" |when I click "Copy to |button in Info Center |clipboard" button in Info ||Center Version|5.13.90 |unspecified --- Comment #1 from Patrick Silva --- KDE neon Developer Edition KDE Plasma: 5.14.80 Qt: 5.11.2 KDE Frameworks: 5.52.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400311] New: Wayland crashes when I click "Copy to clipboard" button in Info Center
https://bugs.kde.org/show_bug.cgi?id=400311 Bug ID: 400311 Summary: Wayland crashes when I click "Copy to clipboard" button in Info Center Product: kwin Version: 5.13.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Cannot reproduce all the time, crash occurs randomly. Thread 1 "kwin_wayland" received signal SIGSEGV, Segmentation fault. KWayland::Server::DataSourceInterface::d_func (this=0x0) at ./src/server/datasource_interface.cpp:161 161 ./src/server/datasource_interface.cpp: No such file or directory. (gdb) thread apply all bt Thread 9 (Thread 5817.5842): #0 0x7f178e6999f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f178c0bbfb8 ) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f178c0bbf68 , cond=0x7f178c0bbf90 ) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=cond@entry=0x7f178c0bbf90 , mutex=mutex@entry=0x7f178c0bbf68 ) at pthread_cond_wait.c:655 #3 0x7f178bdc6954 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f178c0adec0 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #4 0x7f178bdc6999 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #5 0x7f178e6936db in start_thread (arg=0x7f17509e5700) at pthread_create.c:463 #6 0x7f178c74188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 5817.5840): #0 0x7f178e6999f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x558aaffb45f0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x558aaffb45a0, cond=0x558aaffb45c8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=cond@entry=0x558aaffb45c8, mutex=mutex@entry=0x558aaffb45a0) at pthread_cond_wait.c:655 #3 0x7f178d07294b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x558aaffb45a0) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=this@entry=0x558aaffb43e0, mutex=mutex@entry=0x558aaffb43d8, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7f17521f522b in FileInfoThread::run (this=0x558aaffb43c8) at fileinfothread.cpp:227 #6 0x7f178d071adb in QThreadPrivate::start (arg=0x558aaffb43c8) at thread/qthread_unix.cpp:367 #7 0x7f178e6936db in start_thread (arg=0x7f17519e7700) at pthread_create.c:463 #8 0x7f178c74188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 5817.5839): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f178d065594 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:92 #2 QtLinuxFutex::futexWait > (expectedValue=, futex=...) at thread/qfutex_p.h:107 ---Type to continue, or q to quit--- #3 futexSemaphoreTryAcquire_loop (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:221 #4 futexSemaphoreTryAcquire (timeout=-1, n=n@entry=1, u=...) at thread/qsemaphore.cpp:264 #5 QSemaphore::acquire (this=this@entry=0x558ab007a638, n=n@entry=1) at thread/qsemaphore.cpp:328 #6 0x7f1775eb099b in QtVirtualKeyboard::HunspellWorker::run (this=0x558ab007a620) at hunspellworker.cpp:293 #7 0x7f178d071adb in QThreadPrivate::start (arg=0x558ab007a620) at thread/qthread_unix.cpp:367 #8 0x7f178e6936db in start_thread (arg=0x7f17521e8700) at pthread_create.c:463 #9 0x7f178c74188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 5817.5838): #0 0x7f178c734bf9 in __GI___poll (fds=0x7f174c004660, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f17836c5439 in ?? () from target:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f17836c554c in g_main_context_iteration () from target:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f178d29751f in QEventDispatcherGlib::processEvents (this=0x7f174c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #4 0x7f178d23b7fa in QEventLoop::exec (this=this@entry=0x7f1753e6fd40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f178d066bba in QThread::exec (this=this@entry=0x558aaff464a0) at thread/qthread.cpp:525 #6 0x7f17877c04f5 in QQmlThreadPrivate::run (this=0x558aaff464a0) at qml/ftw/qqmlthread.cpp:148 #7 0x7f178d071adb in QThreadPrivate::start (arg=0x558aaff464a0) at thread/qthread_unix.cpp:367 #8 0x7f178e6936db in start_thread (arg=0x7f1753e70700) at pthread_create.c:463 #9 0x7f178c74188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 5817.5837): #0
[kdenlive] [Bug 377010] Title "Clip Problems" Title Font will be replaced by A Cut Above The Rest
https://bugs.kde.org/show_bug.cgi?id=377010 --- Comment #4 from Phuoc --- No, I don't know anything about scrolling title. If I do that I would add the pan effect on it :-) I'm already used to those message popups when I open an existing project. I simply click them away without reading hahaha If the title clip is broken the preview should show the blank lines, too. But they only appear in title editor. Those blank lines in a multiple lines text block only appear if the project has been saved before and reopen. Since I never had this problem on Linux before. I highly suspect that we are dealing with the traditional DOS \n\r issue :-) -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 399400] Plasma crashes when CUPS service is running
https://bugs.kde.org/show_bug.cgi?id=399400 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400280] Preview files in Dolphin file lists: Directories defaults to enable "Show preview of files and folders"
https://bugs.kde.org/show_bug.cgi?id=400280 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |NOT A BUG --- Comment #1 from Nate Graham --- > my views were working as intended (i.e. Details, with disabled Preview in all > directories, except those I actively enabled Preview and/or changed view > mode). You just need to tell dolphin to default to not using previews when in "Remember properties for each folder" mode. Here's how to do it from scratch: 1. Control menu or Settings menu > Dolphin Settings 2. Check "Remember properties for each folder" 3. Control menu or View menu > Adjust View Properties 4. Set your preferred default view 5. Click "Apply To > All Folders 6. Click Apply Now you can individually adjust the settings in other folders as needed to (for example) turn on previews only where desired. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 400294] SigSegFault in background parser
https://bugs.kde.org/show_bug.cgi?id=400294 Rolf Eike Beer changed: What|Removed |Added Summary|SigSegVault in background |SigSegFault in background |parser |parser CC||k...@opensource.sf-tec.de Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 400310] Changing wifi network crashes applet
https://bugs.kde.org/show_bug.cgi?id=400310 Massimiliano changed: What|Removed |Added CC||leoni.massimiliano1@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 400310] New: Changing wifi network crashes applet
https://bugs.kde.org/show_bug.cgi?id=400310 Bug ID: 400310 Summary: Changing wifi network crashes applet Product: plasma-nm Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: leoni.massimilia...@gmail.com Target Milestone: --- SUMMARY When I'm connected to a wifi and I try to connect to another one, networkmanager crashes [shows no available wifi adapters or networks]. STEPS TO REPRODUCE 1. Connect to a wifi network 2. Use networkmanager to connect to another network via the "Connect" button OBSERVED RESULT The applet crashes, no networks or network adapters are detected anymore EXPECTED RESULT It should just connect the other network SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION I'm on Kubuntu 18.04.1 + backport repositories -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400299] Double click on desktop stopped working after update to Qt 5.12 beta3
https://bugs.kde.org/show_bug.cgi?id=400299 Patrick Silva changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #2 from Patrick Silva --- to rebuild plasma-workspace package solved the problem. \o/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364258] 4.x application configuration rc files are ignored [patch]
https://bugs.kde.org/show_bug.cgi?id=364258 Hector changed: What|Removed |Added CC||reboll...@gmail.com Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #28 from Hector --- Hello friends!! My name is Hector and I'm from Argentina. First of all, excuse me to reopen the subject .. Years ago I stopped using Digikam because of this problem. Before this, it was my only photo software, I adored it. I had thousands of photos with labels, and various classifications. 2 weeks ago I have updated the system and now I use OpenSuse Tumbleweed. As always I was updating on update, in this opportunity I decided to create a new user since I never open digikam. On this occasion, the user "HAR" (previously called Hector) was created. Now with the HAR user, I was able to open digikam and have created and configured everything from scratch, but I still can not import the Digikam 4 database that has 13.4MB I have read all the comments, but I could not understand how they have been able to solve and if they have managed to import all the previous database to the new version of Digikam. Currently I have installed Digikam v5.9, but I would like to import the previous database to not lose as many years of work as it was mentioned by @Alexey Stukalov How do I use the patch that commented @Simon? Thank you very much for all your opinions and comments. I hope that with your help, I can manage to import my beloved digikam4.db -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400140] Digikam crash when exporting on google photos
https://bugs.kde.org/show_bug.cgi?id=400140 --- Comment #21 from caulier.gil...@gmail.com --- Here, the crash appear while reading Exif data, at line 100 of unit test. If i comment lines 100 and 105 the unit test pass fine. Gilles -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 399543] Handbook links to ancient help
https://bugs.kde.org/show_bug.cgi?id=399543 Luigi Toscano changed: What|Removed |Added CC||luigi.tosc...@tiscali.it --- Comment #2 from Luigi Toscano --- Can we work again on having the reference manual on docs.kde.org? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400187] Export to google photo in an existing album: bad request
https://bugs.kde.org/show_bug.cgi?id=400187 --- Comment #4 from Mat --- Hello Maik, Ok I understand. Can we imagine having listed only the digikam albums were we can upload pictures? Or having a more explicit error message? Regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400140] Digikam crash when exporting on google photos
https://bugs.kde.org/show_bug.cgi?id=400140 --- Comment #20 from Maik Qualmann --- The reading of metadata does not crash even under digiKam, only by writing to a new jpeg file... Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400140] Digikam crash when exporting on google photos
https://bugs.kde.org/show_bug.cgi?id=400140 --- Comment #19 from caulier.gil...@gmail.com --- But the Exiv2 0.27 CLI tool do not crash with the CR2 file : ./exiv2 -pa ./IMG_2520.CR2 Exif.Image.ImageWidthShort 1 6240 Exif.Image.ImageLength Short 1 4160 Exif.Image.BitsPerSample Short 3 8 8 8 Exif.Image.Compression Short 1 JPEG (old-style) Exif.Image.Make Ascii 6 Canon Exif.Image.Model Ascii 21 Canon EOS 6D Mark II Exif.Image.StripOffsets Long1 39934458 Exif.Image.Orientation Short 1 top, left Exif.Image.StripByteCounts Long1 5981241 Exif.Image.XResolution Rational1 72 Exif.Image.YResolution Rational1 72 Exif.Image.ResolutionUnitShort 1 inch Exif.Image.DateTime Ascii 20 2018:10:21 10:58:11 Exif.Image.ArtistAscii 12 Matthieu M. Exif.Image.XMLPacket Byte 4316 (Binary value suppressed) Exif.Image.Copyright Ascii 20 All rights reserved ... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 400294] SigSegVault in background parser
https://bugs.kde.org/show_bug.cgi?id=400294 Heinz Wiesinger changed: What|Removed |Added CC||ppr...@liwjatan.at Assignee|kdevelop-bugs-n...@kde.org |ppr...@liwjatan.at -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400140] Digikam crash when exporting on google photos
https://bugs.kde.org/show_bug.cgi?id=400140 --- Comment #18 from caulier.gil...@gmail.com --- I fixed the code to backport all metadat from RAW to JPEG : DMetadata meta; ret = meta.load(file); QByteArray exif = meta.getExifEncoded(); QByteArray iptc = meta.getIptc(); QByteArray xmp = meta.getXmp(); meta.load(path); meta.setExif(exif); meta.setIptc(iptc); meta.setXmp(xmp); meta.setImageDimensions(image.size()); meta.setImageOrientation(MetaEngine::ORIENTATION_NORMAL); meta.setMetadataWritingMode((int)DMetadata::WRITETOIMAGEONLY); ret = meta.applyChanges(true); This code is inspired from Panorama tool which backport from RAW to TIFF. It still crash but now i know where exactly : meta.getExifEncoded() #0 0x7fd8a2b794c3 in waitpid () at /usr/lib64/qt5/../libc.so.6 #1 0x7fd8a2afb14c in do_system () at /usr/lib64/qt5/../libc.so.6 #2 0x7fd8b2fd392c in stackTrace() [clone .part.2] () at /usr/lib64/qt5/../libQt5Test.so.5 #3 0x7fd8b2fd39cd in stackTrace() () at /usr/lib64/qt5/../libQt5Test.so.5 #4 0x7fd8b2fd3a62 in QTest::FatalSignalHandler::signal(int) () at /usr/lib64/qt5/../libQt5Test.so.5 #5 0x7fd8b0328bb0 in () at /usr/lib64/qt5/../libpthread.so.0 #6 0x7fd8ab452de2 in Exiv2::ExifParser::encode(std::vector >&, unsigned char const*, unsigned int, Exiv2::ByteOrder, Exiv2::ExifData const&) () at /usr/lib64/qt5/../libexiv2.so.0 #7 0x7fd8b1dcf38b in Exiv2::ExifParser::encode(std::vector >&, Exiv2::ByteOrder, Exiv2::ExifData const&) (blob=std::vector of length 0, capacity 0, byteOrder=Exiv2::bigEndian, exifData=...) at /usr/include/exiv2/exif.hpp:622 #8 0x7fd8b1dc6bc7 in Digikam::MetaEngine::getExifEncoded(bool) const (this=0x7ffe5b6b87f0, addExifHeader=false) at /mnt/data/GIT/6.x/core/libs/metadataengine/engine/metaengine_exif.cpp:104 For me it's clearly an Exiv2 problem. Loading Exif metadata must not be a problem here... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 337035] KDE does not play well with shared-mime-info after update from 1.2-2 to 1.3-1. "Breaks" .iso files (.txt file icon / behavior).
https://bugs.kde.org/show_bug.cgi?id=337035 tguen changed: What|Removed |Added CC|tg...@protonmail.com| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400295] Some tray icons aren't highlighted upon hovering over them with mouse cursor
https://bugs.kde.org/show_bug.cgi?id=400295 Thomas Surrel changed: What|Removed |Added CC||thomas.sur...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400140] Digikam crash when exporting on google photos
https://bugs.kde.org/show_bug.cgi?id=400140 --- Comment #17 from Maik Qualmann --- It clearly crashes in Exiv2 trying to write the metadata to the temporary QImage. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400140] Digikam crash when exporting on google photos
https://bugs.kde.org/show_bug.cgi?id=400140 --- Comment #16 from Maik Qualmann --- Git commit 661beffcbfe47a0044639463544b02020adc5ba5 by Maik Qualmann. Committed on 25/10/2018 at 19:18. Pushed by mqualmann into branch 'master'. fix QVERIFY false/true logic in the PatchPreviewTest M +2-2core/tests/metadataengine/patchpreviewtest.cpp https://commits.kde.org/digikam/661beffcbfe47a0044639463544b02020adc5ba5 -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 400309] Memory leak
https://bugs.kde.org/show_bug.cgi?id=400309 ircha...@airmail.cc changed: What|Removed |Added Platform|Other |Compiled Sources -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 400309] New: Memory leak
https://bugs.kde.org/show_bug.cgi?id=400309 Bug ID: 400309 Summary: Memory leak Product: Active Window Control Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: ircha...@airmail.cc CC: plasma-b...@kde.org Target Milestone: --- Created attachment 115901 --> https://bugs.kde.org/attachment.cgi?id=115901=edit "fake" menu SUMMARY Memory usage increases over time, and latte-dock must be killed to regain it. STEPS TO REPRODUCE 1. Just having the plasmoid active OBSERVED RESULT Latte-dock's process memory consumption increases indefinitely, but this only happens with active window control's plasmoid is active. EXPECTED RESULT No memory leak SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION the programs I use regularly that integrate well with AWC are dolphin and konsole, I don't have a patched firefox, so it shows no menu, same with steam, however, I use glowing bear, which is an electron program which has a menu, this menu can't be interacted (clicking them doesn't do anything, it doesn't show the items of the supposed menus either) with the entries: edit, view, window, help. What's more, if I switch from glowing bear to firefox, steam or any other program which has no menu, they will show the same non-interactive menu as glowing bear, this will happen until I change to an application that has a menu (like konsole and dolphin) and until I switch to glowing bear again. I don't know if this is or isn't part of the ram problem, but I'm listing it just in case. The applications I use regularly are: firefox-nightly, konsole, dolphin, gmusicbrowser, lutris, steam, feedreader, kate and glowing bear. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 400308] New: Please add a test to validate old style connects
https://bugs.kde.org/show_bug.cgi?id=400308 Bug ID: 400308 Summary: Please add a test to validate old style connects Product: clazy Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: woebbek...@kde.org CC: smart...@kde.org Target Milestone: --- As we only have runtime checks for old style connects it would be nice to get errors already at compile time: 1) does the signal text match the method text 2) test whether signal and slot are members 3) test whether signal and slot are really signals and slots I think it's necessary to separate 2) and 3) to make 3) configurable to avoid false positives when compiling with icecream (preprocessed file). Thanks in advance! Cheers, André -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398967] Media player applet hides itself in the system tray after the player to start the next audio/video playback
https://bugs.kde.org/show_bug.cgi?id=398967 mthw0 changed: What|Removed |Added CC||jari...@hotmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from mthw0 --- Yes I also have this bug but on older setup: Arch Linux KDE Plasma Version: 5.14.2 Qt Version: 5.12-beta3 KDE Frameworks Version: 5.51.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400299] Double click on desktop stopped working after update to Qt 5.12 beta3
https://bugs.kde.org/show_bug.cgi?id=400299 mthw0 changed: What|Removed |Added CC||jari...@hotmail.com Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #1 from mthw0 --- (In reply to Patrick Silva from comment #0) > After update to Qt 5.12 beta3 on Arch Linux, nothing happens on > double-clicking some icon on desktop. > > Operating System: Arch Linux > KDE Plasma Version: 5.14.2 > Qt Version: 5.12.0 beta3 > KDE Frameworks Version: 5.51.0 What icons can you reproduce this with? I have only home and trash and they both work. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 400264] Installation fails in Ubuntu 18.04 - Depends on library from the future (libmlt++3 and libmlt6) unavailable in Bionic
https://bugs.kde.org/show_bug.cgi?id=400264 Vincent PINON changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REOPENED|NEEDSINFO --- Comment #5 from Vincent PINON --- Hello, Sorry I am the responsible for your recent bad times. please try "sudo add-apt-repository ppa:kdenlive/mlt". Explanation: I have less and less time to take care of these PPA among other things, and was bored of triggering MLT builds or copying in each PPA, then waiting completion (hours), then triggering Kdenlive build... So I discovered the "PPA dependency" feature and believed it would solve the problem, by making builders only once. Partly true: PPA dependency is not automatically added on users setup, that's why you are facing this problem. I did not see that because I had the dependency PPA installed (and don't test much as I even don't do this for myself, not a ubuntu user). Please tell me if that solves the problem, then I will have to find a way to automate the process for users or for copying packages on my side, but so many other things to do. In the meantime, do you know you also can use our AppImages for a while? Regards, Vincent -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 397187] z13 vector register support for vgdb gdbserver
https://bugs.kde.org/show_bug.cgi?id=397187 --- Comment #2 from Andreas Arnez --- (In reply to Andreas Arnez from comment #1) > Created attachment 115734 [details] > Add vector register support for vgdb Is this OK? Please let me know if I may have missed anything. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 400307] New: Akregator crashes when closing a tab
https://bugs.kde.org/show_bug.cgi?id=400307 Bug ID: 400307 Summary: Akregator crashes when closing a tab Product: akregator Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: fradolc...@inventati.org Target Milestone: --- Application: akregator (5.9.2) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.15.0-38-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: Akregator has been crashing quite often lately when closing a tab of the internal browser The crash can be reproduced sometimes. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7cf1b86bc0 (LWP 30543))] Thread 26 (Thread 0x7f7b88e8d700 (LWP 32367)): #0 0x7f7ce7ea79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f7b88e8c938) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f7b88e8c8e8, cond=0x7f7b88e8c910) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f7b88e8c910, mutex=0x7f7b88e8c8e8) at pthread_cond_wait.c:655 #3 0x7f7cde83c849 in base::ConditionVariable::Wait() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7cde83ec0c in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7cde83ec9f in base::WaitableEvent::Wait() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7cde843d78 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7cde8450ff in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f7cde84dff1 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f7ce7ea16db in start_thread (arg=0x7f7b88e8d700) at pthread_create.c:463 #10 0x7f7ced9b288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f7b977fe700 (LWP 32336)): #0 0x7f7ce7ea7ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f7b977fd740, expected=0, futex_word=0x7f7b977fd928) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f7b977fd7e0, mutex=0x7f7b977fd8d8, cond=0x7f7b977fd900) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7f7b977fd900, mutex=0x7f7b977fd8d8, abstime=0x7f7b977fd7e0) at pthread_cond_wait.c:667 #3 0x7f7cde83c917 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7cde83ebf7 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7cde83ece2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7cde843d61 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7cde8452e9 in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f7cde84dff1 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f7ce7ea16db in start_thread (arg=0x7f7b977fe700) at pthread_create.c:463 #10 0x7f7ced9b288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f7ba7aee700 (LWP 30623)): #0 0x7f7cde82dd21 in base::internal::Invoker >, bool ()>::Run(base::internal::BindStateBase*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #1 0x7f7cde80d81a in base::MessageLoop::DoIdleWork() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f7cde80feb5 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f7cde83020b in base::RunLoop::Run() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7cde85260f in base::Thread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7cde84dff1 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7ce7ea16db in start_thread (arg=0x7f7ba7aee700) at pthread_create.c:463 #7 0x7f7ced9b288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f7c50b90700 (LWP 30617)): #0 0x7f7ce7ea7ed9 in
[KScreen] [Bug 400277] Display scaling is not reversible
https://bugs.kde.org/show_bug.cgi?id=400277 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |FIXED --- Comment #1 from Nate Graham --- Fixed in a later version of Plasma. 5.8.7 is quite old at this point, and you might consider upgrading to the latest LTS (5.12) or even the newest release (5.14). -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 400291] SFTP kio slave no longer built
https://bugs.kde.org/show_bug.cgi?id=400291 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375708] Turn on numlock at startup does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=375708 Andrius Štikonas changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #19 from Andrius Štikonas --- (In reply to Martin Flöser from comment #18) > Created attachment 115900 [details] > Try 3 > > I added a unit test to investigate why my patch doesn't work and found a > bug. I'm quite confident that it works now. Third time's a charm. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400303] Search results list only shows you top-level categories rather than the actual matched items
https://bugs.kde.org/show_bug.cgi?id=400303 --- Comment #3 from S --- (In reply to Nate Graham from comment #2) > It is actually finding the Compositor KCM, but what's going on here is that > the search results list only shows you top-level categories rather than the > actual matched items. It probably should. Yep, that's what I expected. It's rather confusing, and at first I thought that it wasn't locating the Compositor module at all. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 399400] Plasma crashes when CUPS service is running
https://bugs.kde.org/show_bug.cgi?id=399400 Piotr Kloc changed: What|Removed |Added CC||pepk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375708] Turn on numlock at startup does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=375708 Martin Flöser changed: What|Removed |Added Attachment #115644|0 |1 is obsolete|| --- Comment #18 from Martin Flöser --- Created attachment 115900 --> https://bugs.kde.org/attachment.cgi?id=115900=edit Try 3 I added a unit test to investigate why my patch doesn't work and found a bug. I'm quite confident that it works now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393113] Crop Tool: crop image without cropping the layers data
https://bugs.kde.org/show_bug.cgi?id=393113 Victor Wren changed: What|Removed |Added CC||artg...@gmail.com --- Comment #5 from Victor Wren --- This has valid uses, but I also depend on the crop tool to get rid of "extra stuff" outside the visible image boundary, so that I'm not saving a lot of image layer information that I'll never use. Perhaps "image resize" is a better way of accomplishing this? (although the current image resize tool is less than amazing). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 399389] akonadi_imap_resource crash on gmail
https://bugs.kde.org/show_bug.cgi?id=399389 --- Comment #4 from Brendon Higgins --- I'm not experiencing this issue anymore with the latest Debian packages. I suspect it was due to a packaging incompatibility, triggered by some transitions of Qt and KDE PIM hitting Debian unstable/testing, which was causing the QtWebKit (or is it Engine, now?) to crash during the authorization process. Now the process completes normally, for me. Frank, are you still experiencing this issue? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9
https://bugs.kde.org/show_bug.cgi?id=353370 Mark Wielaard changed: What|Removed |Added CC||sebastian.groth@enervision. ||de --- Comment #21 from Mark Wielaard --- *** Bug 400279 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400279] vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 0x0 0x89 0x3
https://bugs.kde.org/show_bug.cgi?id=400279 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Mark Wielaard --- (In reply to Sebastian Groth from comment #0) > vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xBA 0x1 0x0 0x0 > 0x0 0x89 0x3 > vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 > vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F > vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 > ==4764== valgrind: Unrecognised instruction at address 0xbc09743. > ==4764==at 0xBC09743: > QRandomGenerator::SystemGenerator::generate(unsigned int*, unsigned int*) > (in /usr/lib64/libQt5Core.so.5.11.1) That is the RDRAND instruction. > QtCore has been build with: x86_64-pc-linux-gnu-g++ -march=skylake -O2 Don't use -march=skylake, the program needs to check whether or not the processor (that valgrind emulates) support rdrand (valgrind doesn't). *** This bug has been marked as a duplicate of bug 353370 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400303] Search results list only shows you top-level categories rather than the actual matched items
https://bugs.kde.org/show_bug.cgi?id=400303 Nate Graham changed: What|Removed |Added Assignee|plasma-b...@kde.org |notm...@gmail.com Component|general |sidebarview Summary|KCM search for "compositor" |Search results list only |shows wrong item|shows you top-level ||categories rather than the ||actual matched items Keywords||usability CC||n...@kde.org --- Comment #2 from Nate Graham --- It is actually finding the Compositor KCM, but what's going on here is that the search results list only shows you top-level categories rather than the actual matched items. It probably should. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400182] After click on touchpad mouse button can't select anything on desktop
https://bugs.kde.org/show_bug.cgi?id=400182 --- Comment #9 from Nate Graham --- I'm afraid not, sorry. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400306] Internal Color Selector doesn't work in CMYK Float32 and LABA Float32 modes
https://bugs.kde.org/show_bug.cgi?id=400306 --- Comment #1 from Dmitry Kazakov --- Created attachment 115899 --> https://bugs.kde.org/attachment.cgi?id=115899=edit Screenshot in LabAF32 mode -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400306] New: Internal Color Selector doesn't work in CMYK Float32 and LABA Float32 modes
https://bugs.kde.org/show_bug.cgi?id=400306 Bug ID: 400306 Summary: Internal Color Selector doesn't work in CMYK Float32 and LABA Float32 modes Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: dimul...@gmail.com Target Milestone: --- Created attachment 115898 --> https://bugs.kde.org/attachment.cgi?id=115898=edit Screenshot in CMYKF32 mode Click on the "Dual-color" button on the toolbox and see the wrong color selector rendering in the listed modes. In CMYKF32 mode the internal color selector in completely white, in LABA32 mode it is completely black. I have a feeling that it is related to some normalization inconsistencies we have for LabA and CMYK in F32 mode. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 400264] Installation fails in Ubuntu 18.04 - Depends on library from the future (libmlt++3 and libmlt6) unavailable in Bionic
https://bugs.kde.org/show_bug.cgi?id=400264 --- Comment #4 from ocumo --- (In reply to Nate Graham from comment #3) > Ah, I missed that you were installing via the PPA. The PPA is indeed owned > by the Kdenlive developers, so it's appropriate to keep this open. > > I understand that you're frustrated, but let's try to keep the attitude to a > minimum. Thanks for the prompt reply. I totally agree that we have to keep it nice. Not only here, everywhere. There is also such thing "action and reaction". My remarks are assertive, not disrespectful, because the reply was crying for an assertive remark. I did say and repeat now that this is not about persons, it is a technical thing about code, and my report is about code and the impact of code on normal users, and I will keep it in that scope. That doesn't mean that a nonsense, not applicable, copy/paste reply that has all the characteristics of "not my fault, look elsewhere" doesn't deserve an assertive reaction, and as said in my comment, it can only be explained two ways: either a silly mistake (which seems to have been the case) or a questionable practice that is far too common in certain bug trackers on this Planet (and yes, the pun is intended: action and reaction, which is what we should try to stop). I would be delightful to prove with embarrassing evidences that what I am saying is dramatically true, but not in this thread. This bug tracker is one of the most blatant examples in my favor, but not exclusively, sadly. So while I support the use of more sugar and less vinegar, I also have to highlight that there is a good portion of the later in your comments. But to re-focus in what matters: 1. I appreciate that you recognize that I am right. This means the report is correct and valid and thus it should be processed appropriately. 2. Users that care to spend a big amount of time to produce bug reports and investigate things and follow up on FOSS programs, do so because they are committed to the project in their own way and that has also big costs for them. So it's not only the efforts of the devs. It is also the sacrifices that many users do in going through this type of things. It is dramatic that most users don't know how to or are afraid of trying reporting anything because the rule is, specially in certain bug trackers, that they are going to get either a patronizing or an evasive or yet a confusing mambojumbo dev talk about some procedural thing (equivalent to "lawyer talk") to deviate from what matters: The USER'S experience. 3. I have had so many bad experiences with Kdenlive that if I would open a bug report for each one I would get crazy. But when I decide to sacrifice a big portion of my time in order to help the developers (I program too) but most specially the USERs, the last thing I need to get through is enter in a discussion about bad attitudes or much less about semantics of what bugtrackers of the planet say an English word means. That is relevant for the owners of the project, but not at all for users. If users are treated as developers, then it's better not have bug trackers at all. Not everybody is a dev, same as not everybody is a lawyer. Though I am a developer, I have had my own bugtrackers and I know what does it mean to me when I RESOLVE something. But that is not relevant, it's NOT about me and I shall not discuss semantics here and ignore the real issue. Thanks again for rectifying your initial reply, I remain available for helping if and as I can, even if it is a small contribution. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 399300] Library feature does not display clips in UI
https://bugs.kde.org/show_bug.cgi?id=399300 emohr changed: What|Removed |Added Version|18.08.1 |18.08.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 399300] Library feature does not display clips in UI
https://bugs.kde.org/show_bug.cgi?id=399300 emohr changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Flags||Brainstorm+ --- Comment #3 from emohr --- You are right. It seems the whole library function as descript here: https://kdenlive.org/en/project/the-library-copy-paste-between-projects/ doesn’t work in anymore (even under Linux). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400305] Empty closing animation upon switching windows fast with Alt+Tab shortcut on Wayland
https://bugs.kde.org/show_bug.cgi?id=400305 Alexander Mentyu changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 399757] Can AWC use buttons style from the current Window decoration?
https://bugs.kde.org/show_bug.cgi?id=399757 tr...@yandex.com changed: What|Removed |Added CC||kwin-bugs-n...@kde.org --- Comment #31 from tr...@yandex.com --- Is there a Kwin dev who would suggest us a way to paint only a decoration button with animation created inside its class on a Plasmoid? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400305] New: Empty closing animation upon switching windows fast with Alt+Tab shortcut on Wayland
https://bugs.kde.org/show_bug.cgi?id=400305 Bug ID: 400305 Summary: Empty closing animation upon switching windows fast with Alt+Tab shortcut on Wayland Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-tabbox Assignee: kwin-bugs-n...@kde.org Reporter: notux...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Start Wayland. 2. Select 'Breeze' as windows task switcher. 3. Press Alt+Tab shortcut fast - without waiting for Breeze task switcher animation to complete OBSERVED RESULT Very often empty Breeze task switcher window fades out - not having time to display current windows EXPECTED RESULT The Breeze task switcher doesn't appears if it's not having time to display current windows - same as in X session SOFTWARE VERSIONS Operating System: KDE neon Developer Edition KDE Plasma Version: 5.14.80 Qt Version: 5.11.2 KDE Frameworks Version: 5.52.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395446] Seekbar in the media player plasmoid only starts after clicking for spotify
https://bugs.kde.org/show_bug.cgi?id=395446 Raj Amal changed: What|Removed |Added Version|5.13.0 |5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 400304] New: akonadi_imap_resource segmentation fault crash when idle on GMail account
https://bugs.kde.org/show_bug.cgi?id=400304 Bug ID: 400304 Summary: akonadi_imap_resource segmentation fault crash when idle on GMail account Product: Akonadi Version: 5.9.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: j...@holodeck1.com Target Milestone: --- SUMMARY I was away at work and when I came back home I saw a notification that akonadi_imap_resource crashed. It is with the IMAP account resorce which connects to GMail accout. Actual version of Akonadi is 5.9.2, but it is not available on the list of versions. STEPS TO REPRODUCE 1. Have a GMail acount accessed via IMAP 2. Leave it idle so only regular checking of the mail might be active OBSERVED RESULT Crash with the following backtrace Application: akonadi_imap_resource (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 28return SYSCALL_CANCEL (nanosleep, requested_time, remaining); [Current thread is 1 (Thread 0x7fa4bbac49c0 (LWP 19191))] Thread 16 (Thread 0x7fa48ddf7700 (LWP 22431)): #0 0x7fa4cfb65d34 in __GI___libc_read (fd=23, buf=buf@entry=0x7fa48ddf69b0, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fa4cd47d4b0 in read (__nbytes=16, __buf=0x7fa48ddf69b0, __fd=) at /usr/include/bits/unistd.h:44 #2 0x7fa4cd47d4b0 in g_wakeup_acknowledge (wakeup=0x7fa47400f180) at gwakeup.c:210 #3 0x7fa4cd437a4b in g_main_context_check (context=context@entry=0x7fa468019a60, max_priority=2147483647, fds=fds@entry=0x7fa46800de70, n_fds=n_fds@entry=1) at gmain.c:3698 #4 0x7fa4cd437ef0 in g_main_context_iterate (context=context@entry=0x7fa468019a60, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3917 #5 0x7fa4cd43806c in g_main_context_iteration (context=0x7fa468019a60, may_block=may_block@entry=1) at gmain.c:3981 #6 0x7fa4d02a8adb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fa468005050, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0x7fa4d0255adb in QEventLoop::exec(QFlags) (this=this@entry=0x7fa48ddf6be0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #8 0x7fa4d00a4de6 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #9 0x7fa4d00ae9b7 in QThreadPrivate::start(void*) (arg=0x55f995c330a0) at thread/qthread_unix.cpp:367 #10 0x7fa4ceb99554 in start_thread (arg=) at pthread_create.c:463 #11 0x7fa4cfb74ccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7fa494dea700 (LWP 22273)): #0 0x7fa4cfb65d34 in __GI___libc_read (fd=18, buf=buf@entry=0x7fa494de99b0, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fa4cd47d4b0 in read (__nbytes=16, __buf=0x7fa494de99b0, __fd=) at /usr/include/bits/unistd.h:44 #2 0x7fa4cd47d4b0 in g_wakeup_acknowledge (wakeup=0x7fa47c003d80) at gwakeup.c:210 #3 0x7fa4cd437a4b in g_main_context_check (context=context@entry=0x7fa47000caa0, max_priority=2147483647, fds=fds@entry=0x7fa470023800, n_fds=n_fds@entry=1) at gmain.c:3698 #4 0x7fa4cd437ef0 in g_main_context_iterate (context=context@entry=0x7fa47000caa0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3917 #5 0x7fa4cd43806c in g_main_context_iteration (context=0x7fa47000caa0, may_block=may_block@entry=1) at gmain.c:3981 #6 0x7fa4d02a8adb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fa470011d80, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0x7fa4d0255adb in QEventLoop::exec(QFlags) (this=this@entry=0x7fa494de9be0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #8 0x7fa4d00a4de6 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #9 0x7fa4d00ae9b7 in QThreadPrivate::start(void*) (arg=0x55f995c499c0) at thread/qthread_unix.cpp:367 #10 0x7fa4ceb99554 in start_thread (arg=) at pthread_create.c:463 #11 0x7fa4cfb74ccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7fa48700 (LWP 19217)): #0 0x7fa4cfb6f739 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fa4d00a3a24 in QtLinuxFutex::_q_futex(int*, int, int, unsigned long long, int*, int) (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:105 #2 0x7fa4d00a3a24 in QtLinuxFutex::futexWait >(QBasicAtomicInteger&, QBasicAtomicInteger::Type) (expectedValue=, futex=...) at thread/qfutex_p.h:107 #3 0x7fa4d00a3a24 in futexSemaphoreTryAcquire_loop(QBasicAtomicInteger&, unsigned long long, unsigned long long, int) (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:221 #4 0x7fa4d00a3a24 in
[kdenlive] [Bug 387092] Proxy clips interfere with rendering
https://bugs.kde.org/show_bug.cgi?id=387092 --- Comment #15 from emohr --- The properties of the original file proxied looks “weird”. Do you have another camera/cell phone to test? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399675] Plasma freezes on mouseover icons in the system tray and digital clock
https://bugs.kde.org/show_bug.cgi?id=399675 --- Comment #2 from Patrick Silva --- It have just happened on Arch Linux. KDE Plasma Version: 5.14.2 Qt Version: 5.12.0 beta3 KDE Frameworks Version: 5.51.0 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 349615] Semantic information (tags, etc.) not updated when changed elsewhere (e.g. Dolphin)
https://bugs.kde.org/show_bug.cgi?id=349615 --- Comment #5 from Stefan Brüns --- Git commit 43ab022f35e812b71ab866402c16505aab929529 by Stefan Brüns. Committed on 25/10/2018 at 16:11. Pushed by bruns into branch 'master'. [Scheduler] Fix wrong usage of obsolete QFileInfo::created() timestamp Summary: Baloo uses the metadata change time (stat.st_ctime, man 7 inode) to check for XAttr updates. This field corresponds to QFileInfo::metadataChangeTime(), while created() returns the first available of [birthtime, ctime, mtime]. On filesystems supporting birthtime (XFS, BTRFS) some files were continously reindexed as the BasicIndexingJob stored the ctime, while the UnindexedFileIterator compared the stored value with the btime. On the other hand, XAttr changes where not detected when ctime and btime initially matched, as the btime is fixed. While at it, document the semantics of the two timestamps. Related: bug 397549 Test Plan: 1. watch baloo_file with strace -efile during startup -> files with btime != ctime are indexed just once 2. add a Tag to a file -> file is immediately updated in index, not just after baloo_file restart (e.g. session restart) Reviewers: #baloo, #frameworks, poboiko, ngraham, lbeltrame Reviewed By: lbeltrame Subscribers: lbeltrame, kde-frameworks-devel Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D16255 M +11 -3src/engine/documenttimedb.h M +1-1src/file/basicindexingjob.cpp M +10 -3src/file/modifiedfileindexer.cpp M +10 -1src/file/unindexedfileiterator.cpp https://commits.kde.org/baloo/43ab022f35e812b71ab866402c16505aab929529 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 397549] Searching for tags in Dolphin doesn't always work
https://bugs.kde.org/show_bug.cgi?id=397549 --- Comment #3 from Stefan Brüns --- Git commit 43ab022f35e812b71ab866402c16505aab929529 by Stefan Brüns. Committed on 25/10/2018 at 16:11. Pushed by bruns into branch 'master'. [Scheduler] Fix wrong usage of obsolete QFileInfo::created() timestamp Summary: Baloo uses the metadata change time (stat.st_ctime, man 7 inode) to check for XAttr updates. This field corresponds to QFileInfo::metadataChangeTime(), while created() returns the first available of [birthtime, ctime, mtime]. On filesystems supporting birthtime (XFS, BTRFS) some files were continously reindexed as the BasicIndexingJob stored the ctime, while the UnindexedFileIterator compared the stored value with the btime. On the other hand, XAttr changes where not detected when ctime and btime initially matched, as the btime is fixed. While at it, document the semantics of the two timestamps. Related: bug 349615 Test Plan: 1. watch baloo_file with strace -efile during startup -> files with btime != ctime are indexed just once 2. add a Tag to a file -> file is immediately updated in index, not just after baloo_file restart (e.g. session restart) Reviewers: #baloo, #frameworks, poboiko, ngraham, lbeltrame Reviewed By: lbeltrame Subscribers: lbeltrame, kde-frameworks-devel Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D16255 M +11 -3src/engine/documenttimedb.h M +1-1src/file/basicindexingjob.cpp M +10 -3src/file/modifiedfileindexer.cpp M +10 -1src/file/unindexedfileiterator.cpp https://commits.kde.org/baloo/43ab022f35e812b71ab866402c16505aab929529 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400303] KCM search for "compositor" shows wrong item
https://bugs.kde.org/show_bug.cgi?id=400303 --- Comment #1 from S --- BTW, I believe that this bug is a new regression in Plasma 5.14.1, as I was playing with Compositor settings in 5.13.x and 5.14.0 and never noticed this behavior. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400303] New: KCM search for "compositor" shows wrong item
https://bugs.kde.org/show_bug.cgi?id=400303 Bug ID: 400303 Summary: KCM search for "compositor" shows wrong item Product: systemsettings Version: 5.14.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sb56...@gmail.com Target Milestone: --- Created attachment 115897 --> https://bugs.kde.org/attachment.cgi?id=115897=edit "compositor" search shows "Display and Monitor" entry, which opens "Compositor" Hi there, in Plasma 5.14.1 on openSUSE Tumbleweed, a search for "compositor" shows the "Display and Monitor" item instead of the "Compositor" item, although "Compositor" is opened when clicking the "Display and Monitor" entry. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 400291] SFTP kio slave no longer built
https://bugs.kde.org/show_bug.cgi?id=400291 --- Comment #1 from Andreas Schneider --- Which version of libssh do you have installed and do you have the devel package? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 400302] New: Contents of 'Displays' system settings module isn't updating upon resizing after pressing its Default button
https://bugs.kde.org/show_bug.cgi?id=400302 Bug ID: 400302 Summary: Contents of 'Displays' system settings module isn't updating upon resizing after pressing its Default button Product: KScreen Version: git Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm Assignee: se...@kde.org Reporter: notux...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Open 'Displays' system settings module. 2. Press 'Defaults' button in the settings module window. 3. Resize the 'Displays' window. OBSERVED RESULT 'Displays' window is resizing but its contents isn't updating SOFTWARE VERSIONS Operating System: KDE neon Developer Edition KDE Plasma Version: 5.14.80 Qt Version: 5.11.2 KDE Frameworks Version: 5.52.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377010] Title "Clip Problems" Title Font will be replaced by A Cut Above The Rest
https://bugs.kde.org/show_bug.cgi?id=377010 --- Comment #3 from emohr --- Created attachment 115896 --> https://bugs.kde.org/attachment.cgi?id=115896=edit scrolling Title Something with your title font or how do you have built your title is wrong. I assume you like to have a scrolling title. I upload and example. Is that what you want on the end? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390642] Cursor gets stuck with the wrong icon after moving between canvas and gui
https://bugs.kde.org/show_bug.cgi?id=390642 speedyblueskyf...@gmail.com changed: What|Removed |Added CC||speedyblueskyf...@gmail.com --- Comment #30 from speedyblueskyf...@gmail.com --- Hey, I am not sure if this is the same bug, but I am getting the "drag hand" icon stuck after moving the mirror on my canvas. I can draw, but the icon obscures my view and hinders drawing. relaunching fixes it. I think it sounds similar, but maybe i should report it as a separate bug? I'm on windows 10, krita 4.1.5. I did not have this issue in the previous version of krita. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 400301] New: Command "Save as" not working
https://bugs.kde.org/show_bug.cgi?id=400301 Bug ID: 400301 Summary: Command "Save as" not working Product: lokalize Version: 2.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sdepi...@gmail.com Reporter: valterm...@gmail.com CC: sha...@ukr.net Target Milestone: --- SUMMARY When using the command "Save as" (in other folder than the project one), the command doesn't save the gettext file STEPS TO REPRODUCE 1. Open within Lokalize a gettext file 2. Click the "Save as" command, choose a location 3. Click on button "Save" OBSERVED RESULT The file is not save in the target folder, the folder is empty EXPECTED RESULT The file *should be saved* in the target folder SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION KDE neon Developer Edition Same behavior experienced in Kubuntu up to 18.04 -- You are receiving this mail because: You are watching all bug changes.
