[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 Denis Prost changed: What|Removed |Added CC|denis.pr...@wanadoo.fr | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400277] New: Display scaling is not reversible
https://bugs.kde.org/show_bug.cgi?id=400277 Bug ID: 400277 Summary: Display scaling is not reversible Product: systemsettings Version: 5.8.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: thopp...@web.de Target Milestone: --- When using systemsettings/Display and Monitor/Display/Scale display the scale factor is set and work. OK. But it is not possible to reverts this setting! When choose these menu again after you scale your display to eg. 1.2 the slider for the scale factor is set to 1.0 and you are not possible to revert the scale factor below 1. :-\ KDE Plasma Version: 5.8.7 KDE Frameworks Version: 5.32.0 Qt Version: 5.6.2 ADDITIONAL INFORMATION A hint in which config file these setting is saved will be neccessary if these versions are not fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 399333] kdeconnectd crashed in clipboardplugin
https://bugs.kde.org/show_bug.cgi?id=399333 --- Comment #1 from Lukáš Karas --- Current version (1.3.1) fixes the crashes by disabling clipboard plugin. It is more or less workaround, working clipboard plugin would be great! But I understand that provide clipboard support on Wayland may be difficult, it should be resolved in Qt codebase... -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 400265] Schedule with single frame capture does not initiate meridian flip
https://bugs.kde.org/show_bug.cgi?id=400265 --- Comment #5 from Jasem Mutlaq --- One possible problem I see is that the capture module might do focusing or dithering and then on the next capture, it decides to do meridian flip. So all the focusing/dithering would be a waste of valuable observing time. So maybe the check should exist in both places. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400278] New: Widget keyboard shortcut works only for its activation on Wayland - not working for deactivation
https://bugs.kde.org/show_bug.cgi?id=400278 Bug ID: 400278 Summary: Widget keyboard shortcut works only for its activation on Wayland - not working for deactivation Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: notux...@gmail.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. Start Wayland. 2. Set shortcut for any panel or desktop widget - for example right click on digital clock panel widget -> Keyboard shortcuts -> set shortcut to Ctrl+Alt+Y -> apply. 3. Invoke digital clock widget by newly set shortcut. 4. Press the shortcut one more time. OBSERVED RESULT The widget not deactivates EXPECTED RESULT Widget deactivates - X behavior 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.
[kmail2] [Bug 390733] KMail cannot send mails using gmail smtp
https://bugs.kde.org/show_bug.cgi?id=390733 --- Comment #9 from Tom Kijas --- Now it is similar, but this time, KMail doesn't even tell me there is an error, the mail simply hangs in Outgoing folder! That's so unprofessional... Je tu někdo, s kým by se dalo na vyřešení problému pracovat? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 400265] Schedule with single frame capture does not initiate meridian flip
https://bugs.kde.org/show_bug.cgi?id=400265 --- Comment #4 from Wolfgang Reissenberger --- Well, promising that it does not cause any regressions is challenging for the Capture module :-/ But sure, yes, I will give it a try. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #44 from Maik Qualmann --- Git commit 71fe4107faa82bd992756392e53910897ab4fc09 by Maik Qualmann. Committed on 25/10/2018 at 06:12. Pushed by mqualmann into branch 'master'. try to fix progressInfo crash Related: bug 397919 M +3-3core/libs/threadimageio/loadsavetask.cpp M +3-0core/libs/threadimageio/loadsavetask.h https://commits.kde.org/digikam/71fe4107faa82bd992756392e53910897ab4fc09 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397919] Segmentation fault during maintenance
https://bugs.kde.org/show_bug.cgi?id=397919 --- Comment #41 from Maik Qualmann --- Git commit 71fe4107faa82bd992756392e53910897ab4fc09 by Maik Qualmann. Committed on 25/10/2018 at 06:12. Pushed by mqualmann into branch 'master'. try to fix progressInfo crash Related: bug 399923 M +3-3core/libs/threadimageio/loadsavetask.cpp M +3-0core/libs/threadimageio/loadsavetask.h https://commits.kde.org/digikam/71fe4107faa82bd992756392e53910897ab4fc09 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400276] New: Removed desktop widgets keep returning after reboot on Wayland
https://bugs.kde.org/show_bug.cgi?id=400276 Bug ID: 400276 Summary: Removed desktop widgets keep returning after reboot on Wayland Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: notux...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. Start Wayland session 2. Add some widgets to desktop 3. Remove them 4. Logout/login OBSERVED RESULT Widgets returned to desktop stacked in top left corner 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 ADDITIONAL INFORMATION Panel widget are not returning after their removal -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400276] Removed desktop widgets keep returning after reboot on Wayland
https://bugs.kde.org/show_bug.cgi?id=400276 Alexander Mentyu changed: What|Removed |Added Component|Desktop Containment |generic-wayland Assignee|se...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400276] Removed desktop widgets keep returning after reboot on Wayland
https://bugs.kde.org/show_bug.cgi?id=400276 --- Comment #1 from Alexander Mentyu --- Widgets on panel also keep returning - except digital clock -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 400122] Latte-dock memory consumption increases after being open for a while
https://bugs.kde.org/show_bug.cgi?id=400122 --- Comment #6 from Michail Vourlakos --- Nice -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 400262] Falkon logo text is unreadable in about dialog when using a dark theme
https://bugs.kde.org/show_bug.cgi?id=400262 tr...@yandex.com changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||tr...@yandex.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400250] alt-f2 too quickly launching wrong desktop file
https://bugs.kde.org/show_bug.cgi?id=400250 Ludwig Nussel changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Ludwig Nussel --- Aha, so I added "-bg yellow" to /usr/share/applications/xterm.desktop to be able to differentiate between a white, yellow and bigger font xterm. Turns out that actually when typing too fast alt-f2 just executes plain xterm itself as command. Ie I get a white xterm. If I'm a bit slower the one from my home with bigger font is launched. Then I changed then name of my local copy to 00XTerm. Now the command line choice ends up always on top so I always get a white xterm. There is no duplicate desktop file entry. However, the desktop file entry never goes back to the top now. Even after deleting ~/.local/share/applications/xterm.desktop, running kbuildsycoca5, rebooting *sigh*. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 399367] Selecting text deletes it
https://bugs.kde.org/show_bug.cgi?id=399367 --- Comment #7 from Laurent Montel --- So it's a color bug not a kmail bug. Perhaps you can report to color system or other but for sure it's not a kmail bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400282] META KEY DONT OPEN LAUNCHER
https://bugs.kde.org/show_bug.cgi?id=400282 Patrick Silva changed: What|Removed |Added Assignee|k...@privat.broulik.de |k...@davidedmundson.co.uk Product|krunner |plasmashell Target Milestone|--- |1.0 CC||bugsefor...@gmx.com, ||plasma-b...@kde.org Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398266] Desktop icon isn't removing in Wayland
https://bugs.kde.org/show_bug.cgi?id=398266 --- Comment #3 from Alexander Mentyu --- *** Bug 400276 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400210] [Qt5.12] App dashboard stops to be repainted after a while
https://bugs.kde.org/show_bug.cgi?id=400210 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from David Edmundson --- \o/ thanks -- 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 ocumo changed: What|Removed |Added CC||j...@kdenlive.org -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 400121] Kdenlive doesn't show pictures in the timeline but project bin if the source folder contains question mark.
https://bugs.kde.org/show_bug.cgi?id=400121 emohr changed: What|Removed |Added Version|17.12.3 |18.08.2 Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Flags||Brainstorm+ --- Comment #7 from emohr --- Thanks for hte help. Confirmed. If the path or the clip contains a no standard unicode character the clip get not viewed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 396398] KMail 5.8.2 displays HTML formatting on top of message
https://bugs.kde.org/show_bug.cgi?id=396398 Laurent Montel changed: What|Removed |Added Latest Commit||https://commits.kde.org/mes ||sagelib/33991513a4fb0e55feb ||89e81ab7e8f5306714191 Version Fixed In||5.9.3 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Laurent Montel --- Git commit 33991513a4fb0e55feb89e81ab7e8f5306714191 by Laurent Montel. Committed on 25/10/2018 at 11:43. Pushed by mlaurent into branch 'Applications/18.08'. Fix Bug 396398 - KMail 5.8.2 displays HTML formatting on top of message FIXED-IN: 5.9.3 M +8-6messageviewer/src/messagepartthemes/default/defaultrenderer.cpp https://commits.kde.org/messagelib/33991513a4fb0e55feb89e81ab7e8f5306714191 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays
https://bugs.kde.org/show_bug.cgi?id=333655 Axel Braun changed: What|Removed |Added CC||axel.br...@gmx.de --- Comment #71 from Axel Braun --- I'm running baloo 5.45.0 on openSUSE Leap 15, and notice that my complete desktop freezes regularly for 1-2 minutes(!). CPU monitor reports during that time 100% Load on both cores, but top does not show any process of a considerable CU load. The problem is more the couple of baloo and akonadi, as iotop shows: Total DISK READ : 10.37 M/s | Total DISK WRITE :1060.53 K/s Actual DISK READ: 10.37 M/s | Actual DISK WRITE: 197.36 K/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO>COMMAND 4497 idle axel9.73 M/s0.00 B/s 0.00 % 99.52 % baloo_file_extractor 2847 idle axel 651.54 K/s 1058.15 K/s 0.00 % 97.97 % akonadi_indexing_agent --identifier akonadi_indexing_agent 23 be/4 root0.00 B/s0.00 B/s 0.00 % 0.10 % [kworker/1:1] 2479 be/4 axel0.00 B/s0.00 B/s 0.00 % 0.08 % plasmashell 849 be/4 root4.76 K/s0.00 B/s 0.00 % 0.00 % [xfsaild/sda2] (interesting percentage calculation of iotop by the way) System disk is a SSD, data disk is a hybrid 1TB disk with 8G cache. Dont know if this is the right bug for this, but it looks like. Any idea how to tune/tweak the system to prevent these system freezes? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396356] Discover froze when I clicked "update all" button immediately after cancel the password dialog to start update proccess
https://bugs.kde.org/show_bug.cgi?id=396356 --- Comment #3 from Patrick Silva --- I do not remember the PackageKitQt version. And the problem is no longer reproducible on neon dev unstable. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 370644] Subfolders on Domino servers do not work properly
https://bugs.kde.org/show_bug.cgi?id=370644 --- Comment #1 from Alexander Stehlik --- I can confirm this problem. The same server works fine with other clients (e.g. Thunderbird). I had the same suspicion as Jörg that the problem might be related to the double encoded backslashes. -- 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 ocumo changed: What|Removed |Added CC||vpi...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373439] tabbar uses white text on light background
https://bugs.kde.org/show_bug.cgi?id=373439 --- Comment #2 from flo --- screen shot attachment 115889 taken with - kde-neon - konsole 18.08.2 - KDE Frameworks 5.51.0 - Qt 5.11.2 (built against 5.11.1) - plasmashell 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 400292] cruft in plasma-desktop tars
https://bugs.kde.org/show_bug.cgi?id=400292 Harald Sitter changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Harald Sitter --- Lol 5.10 I suspect the "new" script download tech doesn't properly clean up after itself. It may be prudent to actually add a global cleanup before archiving. Relying on individual units to clean up is somewhat unreliable as we can see. OTOH I am sure I had a reason for doing it this way. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400288] New: Titlebar appmenu sometimes closes itself when changing categories
https://bugs.kde.org/show_bug.cgi?id=400288 Bug ID: 400288 Summary: Titlebar appmenu sometimes closes itself when changing categories Product: kwin Version: 5.14.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: appmenu Assignee: kwin-bugs-n...@kde.org Reporter: noaha...@gmail.com Target Milestone: --- SUMMARY When changing categories (e.g., File, Edit, View) or subcategories, the titlebar appmenu will sometimes close itself. STEPS TO REPRODUCE 1. Open titlebar appmenu 2. Attempt to move the mouse cursor through each category OBSERVED RESULT The titlebar appmenu will eventually close itself EXPECTED RESULT The appmenu should stay open until I click away from it or click on the titlebar appmenu button SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51 Qt Version: 5.11.2 ADDITIONAL INFORMATION I don't think this problem happens to the global menu widget. Video showing the issue: https://www.youtube.com/watch?v=_6ul9gACjAQ -- 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 #2 from ocumo --- (In reply to Nate Graham from comment #1) > Since it's a distro packaging problem, there's unfortunately nothing we can > do about it here in KDE. You'll need to find another way to report this to > the Ubuntu folks. Since Launchpad isn't helpful, I would recommend filing a > Phabricator ticket (https://phabricator.kde.org/maniphest/task/edit/form/1/) > and tag "Kubuntu". Thanks! NO. This reply is unacceptable. The Launchpad page does not belong to "Ubuntu" or "Kubuntu" folks. It belongs to Kdenlive. The names of the owners is listed there, they are Kdenlive folks, not Canonical or anybody else. For courtesy I am not listing here those names because this is not personal. But it's not a secret, it's public and don't force me to make this about people's names. This type of reply is not new. I have seen this practically copy/paste even in your forum. And again, it's very annoying, not say a bit on the limits of what's honest, to not assume responsibilities and throw users in a crazy direction. If me or any other user starts opening bug reports in the wild nobody will take ownership of something that it's not theirs. This is either a plain and silly mistake, or a very irresponsible and insulting way of "RESOLVING" issues. By the way the issue is NOT mainstream, it is NOT resolved and I have marked reopened. I would like a reply from one of the members of the Kdenlive team that are active in the Official Kdenlive Launchpad project page, or a very clear and credible explanation of why there would be common names in both Kdenlive and Launchpad Official Kdenlive PPA projects. Coincidence? What is Kdenlive interest in have a PPA with broken packages and then deceptive communication with users to avoid debugging? Who is responsible for this? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400293] New: NFS root folder not writable with 18.08.2 - works with 18.08.1
https://bugs.kde.org/show_bug.cgi?id=400293 Bug ID: 400293 Summary: NFS root folder not writable with 18.08.2 - works with 18.08.1 Product: dolphin Version: 18.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: gbill...@runbox.com CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY After upgrading to 18.08.2 I'm getting the same behavior as described in bug 387936 https://bugs.kde.org/show_bug.cgi?id=387936 the root folder of a NFS mount is not writable from Dolphin while I can write to it from the shell Downgrading to 18.08.1 fixes this STEPS TO REPRODUCE 1. Upgrade to 18.08.2 2. Access the root folder of a NFS share your user has RW access to 3. Try to create a folder OBSERVED RESULT Dolphin doesn't give the option to create a folder EXPECTED RESULT Be able to create a folder SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 dolphin 18.08.2 dolphin-plugins 18.08.2 ADDITIONAL INFORMATION I've first downgraded the kio and kio-extras but that produced no result. Only after downgrading dolphin and dolphin-plugins did it resolve the issue -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400293] NFS root folder not writable with 18.08.2 - works with 18.08.1
https://bugs.kde.org/show_bug.cgi?id=400293 gbill...@runbox.com changed: What|Removed |Added CC||gbill...@runbox.com -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 400297] New: Window that shows compression progress is too narrow
https://bugs.kde.org/show_bug.cgi?id=400297 Bug ID: 400297 Summary: Window that shows compression progress is too narrow Product: ark Version: 18.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: bugsefor...@gmx.com CC: rthoms...@gmail.com Target Milestone: --- Created attachment 115894 --> https://bugs.kde.org/attachment.cgi?id=115894=edit demonstration Firstly disable the progress tracking in the task manager and system tray following the steps below: Right click on notifications applet in the system tray -> Notifications Settings -> uncheck "Track file transfers and other jobs", click "ok" button. Right click the task manager in the plasma panel, select "configure task manager...", uncheck "Show progress and status information in task buttons", click "ok" button and restart plasma session. STEPS TO REPRODUCE 1. right click some big file in Dolphin 2. select "Compress > Here as (tar.gz/zip)" 3. focus the window that shows the progress by clicking its entry in the task manager OBSERVED RESULT the window is too narrow, watch the screencast please. EXPECTED RESULT correct window size Operating System: 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.
[plasmashell] [Bug 400298] New: System Activity window doesn't remember it resized parameters
https://bugs.kde.org/show_bug.cgi?id=400298 Bug ID: 400298 Summary: System Activity window doesn't remember it resized parameters Product: plasmashell Version: 5.14.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: q...@tvchd.com Target Milestone: 1.0 SUMMARY System Activity window doesn't remember it resized parameters STEPS TO REPRODUCE 1. Invoke System Activity with ctrl+esc 2. Resize the window 3. Close it and open up again OBSERVED RESULT Window size changed to it's defaults EXPECTED RESULT Window should remember the size changes SOFTWARE VERSIONS Operating System: KDE neon 5.14 KDE Plasma Version: 5.14.1 Qt Version: 5.11.2 KDE Frameworks Version: 5.51.0 Kernel Version: 4.15.0-38-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 7.5 GiB of RAM ADDITIONAL INFORMATION I think it's happened after plasma 5.14 update, didn't notice the same behavior on 5.13 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 400205] Recheck influence of conditional compilation on syntax colouring and code navigation
https://bugs.kde.org/show_bug.cgi?id=400205 --- Comment #3 from Markus Elfring --- (In reply to Kevin Funk from comment #1) Would a reload of the selected project be sufficient for the activation of changed software build parameters? Does the development environment monitor any corresponding configuration files? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373714] Please make active / passive tab color configurable
https://bugs.kde.org/show_bug.cgi?id=373714 flo changed: What|Removed |Added CC||kde-b...@cyborgsociety.org --- Comment #2 from flo --- I agree this bug report can be closed. It is very old an does not apply (at least not to me). If I select breeze-dark in "Workspace Theme"->"Look and Feel" the selected tab in konsole is very light compared to non-selected tabs. (Font color of non-selected tabs is also very dark and almost unreadable -> time for new bug..) Also attached image shows mac light theme. - kde-neon - konsole 18.08.2 - KDE Frameworks 5.51.0 - Qt 5.11.2 (built against 5.11.1) - plasmashell 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 399367] Selecting text deletes it
https://bugs.kde.org/show_bug.cgi?id=399367 --- Comment #6 from conta...@protonmail.com --- (In reply to Laurent Montel from comment #5) > so we can close it. It's a workaround, the bug isn't fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400250] alt-f2 too quickly launching wrong desktop file
https://bugs.kde.org/show_bug.cgi?id=400250 --- Comment #3 from Ludwig Nussel --- ok, found the settings button and turned off all modules besides applications. Not exactly what that thing was intended for I guess but at least reliable now :-) -- 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 ocumo changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DOWNSTREAM |--- -- 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 Thomas Surrel changed: What|Removed |Added CC||thomas.sur...@protonmail.co ||m -- 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 --- Comment #28 from tr...@yandex.com --- > Does anyone know who is responsible for AWC these days? You, Zren, anyone else,... but not the original dev. He hasn't replied anyone on his github for a long time. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 393079] When updating, package entries show changelogs, but app entries don't
https://bugs.kde.org/show_bug.cgi?id=393079 --- Comment #5 from Aleix Pol --- Are you sure it's not applications without a changelog? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396356] Discover froze when I clicked "update all" button immediately after cancel the password dialog to start update proccess
https://bugs.kde.org/show_bug.cgi?id=396356 Aleix Pol changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400295] New: Some tray icons aren't highlighted upon hovering over them with mouse cursor
https://bugs.kde.org/show_bug.cgi?id=400295 Bug ID: 400295 Summary: Some tray icons aren't highlighted upon hovering over them with mouse cursor Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: notux...@gmail.com Target Milestone: 1.0 SUMMARY For example Digital Clock, Battery, Networks tray icons aren't highlighted but Sound, Vaults, Clipboard are 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.
[Active Window Control] [Bug 399757] Can AWC use buttons style from the current Window decoration?
https://bugs.kde.org/show_bug.cgi?id=399757 --- Comment #29 from Chris Holland --- > 2. I dont quite like how the layout of AWC is produced. Is trying to do too > many things e.g. buttons above the window title of menu etc... > I read somewhere that for [2] Zren is playing with it. I've thought about changing the defaults to something more Ubuntu Unity like. There's now alternative widgets for displaying just the buttons + app title + global menu, so I believe this widget should focus on combining all 3 "widgets" by default in a manner similar to unity (which is probably what people are after). https://phabricator.kde.org/D16328 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 400296] New: Window that shows compression/extraction progress shows nothing when I click the button to show details
https://bugs.kde.org/show_bug.cgi?id=400296 Bug ID: 400296 Summary: Window that shows compression/extraction progress shows nothing when I click the button to show details Product: ark Version: 18.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: bugsefor...@gmx.com CC: rthoms...@gmail.com Target Milestone: --- Firstly disable the progress tracking in the task manager and system tray following the steps below: Right click on notifications applet in the system tray -> Notifications Settings -> uncheck "Track file transfers and other jobs", click "ok" button. Right click the task manager in the plasma panel, select "configure task manager...", uncheck "Show progress and status information in task buttons", click "ok" button and restart plasma session. STEPS TO REPRODUCE 1. open dolphin, right click some big compressed file, select "Extract > Extract archive here" 2. focus the window that shows the progress by clicking its entry in the task manager 3. click the down arrow to show the details OBSERVED RESULT no detail about the progress is shown EXPECTED RESULT show details about the operation Operating System: Arch Linux KDE Plasma Version: 5.14.2 Qt Version: 5.12.0 beta3 KDE Frameworks Version: 5.51.0 ADDITIONAL INFORMATION Also there are no details when I compress files. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400289] New: Plasma Crashed
https://bugs.kde.org/show_bug.cgi?id=400289 Bug ID: 400289 Summary: Plasma Crashed Product: plasmashell Version: 5.12.6 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: hard...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.6) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-38-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: I was using Chrome when suddenly Plasma crashed and restarted itself. The crash does not seem to be reproducible. -- Backtrace: 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 0x7f1a81446800 (LWP 7980))] Thread 28 (Thread 0x7f196b7fe700 (LWP 22249)): #0 0x7f1a7a2b79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55eafc78be74) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1a7a2b79f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55eafc78be20, cond=0x55eafc78be48) at pthread_cond_wait.c:502 #2 0x7f1a7a2b79f3 in __pthread_cond_wait (cond=0x55eafc78be48, mutex=0x55eafc78be20) at pthread_cond_wait.c:655 #3 0x7f1a7b13159b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1a7eeb66a8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f1a7eeb6b0a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f1a7b13016d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1a7a2b16db in start_thread (arg=0x7f196b7fe700) at pthread_create.c:463 #8 0x7f1a7aa2b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f196affd700 (LWP 30225)): #0 0x7f1a7a2b79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f1a6400ba80) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1a7a2b79f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f1a6400ba30, cond=0x7f1a6400ba58) at pthread_cond_wait.c:502 #2 0x7f1a7a2b79f3 in __pthread_cond_wait (cond=0x7f1a6400ba58, mutex=0x7f1a6400ba30) at pthread_cond_wait.c:655 #3 0x7f1a7b13159b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1a7eeb66a8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f1a7eeb6b0a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f1a7b13016d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1a7a2b16db in start_thread (arg=0x7f196affd700) at pthread_create.c:463 #8 0x7f1a7aa2b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f1968844700 (LWP 11559)): #0 0x7f1a7a2b79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55eafc575390) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1a7a2b79f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55eafc575340, cond=0x55eafc575368) at pthread_cond_wait.c:502 #2 0x7f1a7a2b79f3 in __pthread_cond_wait (cond=0x55eafc575368, mutex=0x55eafc575340) at pthread_cond_wait.c:655 #3 0x7f1a7b13159b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1a7eeb66a8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f1a7eeb6b0a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f1a7b13016d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1a7a2b16db in start_thread (arg=0x7f1968844700) at pthread_create.c:463 #8 0x7f1a7aa2b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f1942162700 (LWP 10406)): #0 0x7f1a7a2b79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55eafb731cb4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1a7a2b79f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55eafb731c60, cond=0x55eafb731c88) at pthread_cond_wait.c:502 #2 0x7f1a7a2b79f3 in __pthread_cond_wait (cond=0x55eafb731c88, mutex=0x55eafb731c60) at pthread_cond_wait.c:655 #3 0x7f1a7b13159b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1a7eeb66a8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f1a7eeb6b0a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f1a7b13016d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1a7a2b16db in start_thread (arg=0x7f1942162700) at pthread_create.c:463 #8 0x7f1a7aa2b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f1920d88700 (LWP 9048)): #0 0x7f1a7a2b79f3 in futex_wait_cancelable (private=,
[Akonadi] [Bug 370644] Subfolders on Domino servers do not work properly
https://bugs.kde.org/show_bug.cgi?id=370644 Alexander Stehlik changed: What|Removed |Added CC||alexander.steh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 400292] New: cruft in plasma-desktop tars
https://bugs.kde.org/show_bug.cgi?id=400292 Bug ID: 400292 Summary: cruft in plasma-desktop tars Product: releaseme Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sit...@kde.org Reporter: rikmi...@kubuntu.org Target Milestone: --- SUMMARY Releaseme includes unwanted files in with .po files for some localisations in plasma-desktop tars. STEPS TO REPRODUCE 1. Upload a plasma-desktop tar to Ubuntu as a SRU 2. Wait for Ubuntu release team to review and process the upload OBSERVED RESULT Observe the rejection email received stating that that the upload has binary and other 'cruft' EXPECTED RESULT No cruft, and upload accepted (unless you otherwise screwed up). ADDITIONAL INFORMATION On a serious note, seems to have been the cruft in released tars since plasma 5.10, so this is quite late being picked up! Example listing from 5.12.7: plasma-desktop-5.12.7/kcms/autostart/addscriptdialog.cpp plasma-desktop-5.12.7/kcms/autostart/addscriptdialog.h plasma-desktop-5.12.7/po/sr@ijekavianlatin/scripts/ plasma-desktop-5.12.7/po/sr@ijekavianlatin/scripts/kfontinst/ plasma-desktop-5.12.7/po/sr@ijekavianlatin/scripts/kfontinst/kfontinst.js plasma-desktop-5.12.7/po/sr@ijekavianlatin/scripts/kfontinst/.svn/ plasma-desktop-5.12.7/po/sr@ijekavianlatin/scripts/kfontinst/.svn/entries plasma-desktop-5.12.7/po/sr@ijekavianlatin/scripts/kfontinst/.svn/format plasma-desktop-5.12.7/po/sr@ijekavianlatin/scripts/kfontinst/.svn/pristine/ plasma-desktop-5.12.7/po/sr@ijekavianlatin/scripts/kfontinst/.svn/pristine/5a/ plasma-desktop-5.12.7/po/sr@ijekavianlatin/scripts/kfontinst/.svn/pristine/5a/5a626e01c24fb40324448dba9b875a77c0be9990.svn-base plasma-desktop-5.12.7/po/sr@ijekavianlatin/scripts/kfontinst/.svn/tmp/ plasma-desktop-5.12.7/po/sr@ijekavianlatin/scripts/kfontinst/.svn/wc.db plasma-desktop-5.12.7/po/sr@ijekavianlatin/scripts/kfontinst/.svn/wc.db-journal plasma-desktop-5.12.7/po/sr@ijekavian/scripts/ plasma-desktop-5.12.7/po/sr@ijekavian/scripts/kfontinst/ plasma-desktop-5.12.7/po/sr@ijekavian/scripts/kfontinst/kfontinst.js plasma-desktop-5.12.7/po/sr@ijekavian/scripts/kfontinst/.svn/ plasma-desktop-5.12.7/po/sr@ijekavian/scripts/kfontinst/.svn/entries plasma-desktop-5.12.7/po/sr@ijekavian/scripts/kfontinst/.svn/format plasma-desktop-5.12.7/po/sr@ijekavian/scripts/kfontinst/.svn/pristine/ plasma-desktop-5.12.7/po/sr@ijekavian/scripts/kfontinst/.svn/pristine/1d/ plasma-desktop-5.12.7/po/sr@ijekavian/scripts/kfontinst/.svn/pristine/1d/1db547f1e3e22e03e2ec6163ece3bde6afd2eaf2.svn-base plasma-desktop-5.12.7/po/sr@ijekavian/scripts/kfontinst/.svn/tmp/ plasma-desktop-5.12.7/po/sr@ijekavian/scripts/kfontinst/.svn/wc.db plasma-desktop-5.12.7/po/sr@ijekavian/scripts/kfontinst/.svn/wc.db-journal plasma-desktop-5.12.7/po/sr@latin/scripts/ plasma-desktop-5.12.7/po/sr@latin/scripts/kfontinst/ plasma-desktop-5.12.7/po/sr@latin/scripts/kfontinst/kfontinst.js plasma-desktop-5.12.7/po/sr@latin/scripts/kfontinst/.svn/ plasma-desktop-5.12.7/po/sr@latin/scripts/kfontinst/.svn/entries plasma-desktop-5.12.7/po/sr@latin/scripts/kfontinst/.svn/format plasma-desktop-5.12.7/po/sr@latin/scripts/kfontinst/.svn/pristine/ plasma-desktop-5.12.7/po/sr@latin/scripts/kfontinst/.svn/pristine/5a/ plasma-desktop-5.12.7/po/sr@latin/scripts/kfontinst/.svn/pristine/5a/5a626e01c24fb40324448dba9b875a77c0be9990.svn-base plasma-desktop-5.12.7/po/sr@latin/scripts/kfontinst/.svn/tmp/ plasma-desktop-5.12.7/po/sr@latin/scripts/kfontinst/.svn/wc.db plasma-desktop-5.12.7/po/sr@latin/scripts/kfontinst/.svn/wc.db-journal plasma-desktop-5.12.7/po/sr/scripts/ plasma-desktop-5.12.7/po/sr/scripts/kfontinst/ plasma-desktop-5.12.7/po/sr/scripts/kfontinst/kfontinst.js plasma-desktop-5.12.7/po/sr/scripts/kfontinst/.svn/ plasma-desktop-5.12.7/po/sr/scripts/kfontinst/.svn/entries plasma-desktop-5.12.7/po/sr/scripts/kfontinst/.svn/format plasma-desktop-5.12.7/po/sr/scripts/kfontinst/.svn/pristine/ plasma-desktop-5.12.7/po/sr/scripts/kfontinst/.svn/pristine/1d/ plasma-desktop-5.12.7/po/sr/scripts/kfontinst/.svn/pristine/1d/1db547f1e3e22e03e2ec6163ece3bde6afd2eaf2.svn-base plasma-desktop-5.12.7/po/sr/scripts/kfontinst/.svn/tmp/ plasma-desktop-5.12.7/po/sr/scripts/kfontinst/.svn/wc.db plasma-desktop-5.12.7/po/sr/scripts/kfontinst/.svn/wc.db-journal -- 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 #3 from Nate Graham --- 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. Please see https://community.kde.org/Get_Involved/Bug_Reporting#Bug_tracker_etiquette. You catch more flies with honey than vinegar. :) Also please understand the resolution statuses: https://community.kde.org/Get_Involved/Bug_Reporting#Understand_what_the_resolution_statuses_mean RESOLVED does not necessarily mean "fixed for you personally with your usage today", but it can mean "Fixed in the code even though it's not released yet or available for your choice of distro", or even "there is nothing we can do here; the problem is elsewhere". This is all completely normal and it's the way every bug tracker on the planet works. In this case, you were right and it should remain open since the PPA is something something that the Kdenlive developers own, but please understand that sometimes a RESOLVED status may not be what you were hoping for and you'll need to follow up somewhere else. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 399727] Support systemd suspend-then-hibernate
https://bugs.kde.org/show_bug.cgi?id=399727 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 400294] New: SigSegVault in background parser
https://bugs.kde.org/show_bug.cgi?id=400294
Bug ID: 400294
Summary: SigSegVault in background parser
Product: kdevelop
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Language Support: PHP
Assignee: kdevelop-bugs-n...@kde.org
Reporter: o...@gmx.at
Target Milestone: ---
Created attachment 115890
--> https://bugs.kde.org/attachment.cgi?id=115890=edit
Example file for crash background parser
SUMMARY
KDevelop crashes while background parsing my files of the project (since
updating from 5.2.4 to 5.2.80)
Thread 17 "Queue(0x563" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffa6286700 (LWP 9521)]
Php::ExpressionVisitor::visitStaticMember (this=0x7fffa62816b0,
node=0x7fff8e16ce80) at
/home/opitz/kde/src/extragear/kdevelop/plugins/kdev-php/parser/php.g:870
870 | variableIdentifier
Compiled from git-master with debugging information and with help from IRC
channel I dragged this down to one line out of Symfony package.
> $ ./duchainify -r ~/projects/vendor/symfony/debug/DebugClassLoader.php
> Added 1 files to the background parser
> parsing with 2 threads
> Speicherzugriffsfehler (Speicherabzug geschrieben)
The line in question is: > self::${$annotation}[$name] = '';<
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 400290] Syntax highlighting engine makes wrong guesses for XML files with different extension
https://bugs.kde.org/show_bug.cgi?id=400290 Ongun Kanat changed: What|Removed |Added CC||ongun.ka...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 400290] New: Syntax highlighting engine makes wrong guesses for XML files with different extension
https://bugs.kde.org/show_bug.cgi?id=400290 Bug ID: 400290 Summary: Syntax highlighting engine makes wrong guesses for XML files with different extension Product: kate Version: 18.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: ongun.ka...@gmail.com Target Milestone: --- Created attachment 115888 --> https://bugs.kde.org/attachment.cgi?id=115888=edit Example file. fontconfig configuration. SUMMARY Syntax highlighting engine wrongly guesses the type of files written in XML but have different extensions such as .conf STEPS TO REPRODUCE 1. Open a .conf file in Kate OBSERVED RESULT File type recognized as INI. EXPECTED RESULT File type should be recognized as XML. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION n/a -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 370644] Subfolders on Domino servers do not work properly
https://bugs.kde.org/show_bug.cgi?id=370644 Christophe Giboudeaux changed: What|Removed |Added Assignee|chrig...@fastmail.fm|kdepim-b...@kde.org --- Comment #2 from Christophe Giboudeaux --- The original report is quite old, what's your kimap version ? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373439] tabbar uses white text on light background
https://bugs.kde.org/show_bug.cgi?id=373439 flo changed: What|Removed |Added CC||kde-b...@cyborgsociety.org --- Comment #1 from flo --- Created attachment 115889 --> https://bugs.kde.org/attachment.cgi?id=115889=edit konsole screen shot - using dark theme: dark font color on non-selected (dark) tabs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400210] [Qt5.12] App dashboard stops to be repainted after a while
https://bugs.kde.org/show_bug.cgi?id=400210 --- Comment #3 from mthw0 --- (In reply to David Edmundson from comment #2) > \o/ thanks Just an off-topic question/notice, there is missing version 5.14.2 in 'Version:'. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 400296] Window that shows compression/extraction progress shows nothing when I click the button to show details
https://bugs.kde.org/show_bug.cgi?id=400296 --- Comment #1 from Patrick Silva --- Created attachment 115893 --> https://bugs.kde.org/attachment.cgi?id=115893=edit demonstration Watch the screencast please. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 399837] clip with speed effect
https://bugs.kde.org/show_bug.cgi?id=399837 emohr changed: What|Removed |Added Flags||Brainstorm+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400180] Java apps cannot be pinned
https://bugs.kde.org/show_bug.cgi?id=400180 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 400262] Falkon logo text is unreadable in about dialog when using a dark theme
https://bugs.kde.org/show_bug.cgi?id=400262 --- Comment #7 from David Rosca --- It's not a single color as breeze icons, so that wouldn't work very well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399184] Folder View widget loses its shortcut when plasma is restarted
https://bugs.kde.org/show_bug.cgi?id=399184 Patrick Silva changed: What|Removed |Added Summary|Shortcut doesn't saves |Folder View widget loses ||its shortcut when plasma is ||restarted -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400254] Allow pixel font sizes in text tool
https://bugs.kde.org/show_bug.cgi?id=400254 --- Comment #4 from Alex Gleason --- Created attachment 115895 --> https://bugs.kde.org/attachment.cgi?id=115895=edit (left) 8px font in Gimp, (right) 6pt font in Krita Points is fine, but Krita cannot go below 6pt. The font must be 8px, so it needs 1.9pt. I'm not sure it will still be blurry if rendered at the appropriate size? I'm using Krita to create pixel art for a low-resolution 2D video game. I works wonderfully with the preset pixel brush tools for drawing art, but cannot handle text very well for this purpose. Sadly ORA doesn't support text. My workflow is to export an ORA without text, open with GIMP to create text. Convert text to raster, save as ORA, and reopen in Krita to continue drawing. -- 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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[kdenlive] [Bug 399994] Fcitx not avaliabe with appimage
https://bugs.kde.org/show_bug.cgi?id=34 --- Comment #3 from emohr --- Run the Appimage from the terminal (press CTRL + ALT + T). Move to the AppImage folder and run the .AppImage: ./Kdenlive*.AppImage -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400299] New: Double click on desktop stopped working after update to Qt 5.12 beta3
https://bugs.kde.org/show_bug.cgi?id=400299 Bug ID: 400299 Summary: Double click on desktop stopped working after update to Qt 5.12 beta3 Product: plasmashell Version: 5.14.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.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 -- 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 #8 from Carsten --- so it is not possible to fixe the problem with my 18.04 LTS? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 370644] Subfolders on Domino servers do not work properly
https://bugs.kde.org/show_bug.cgi?id=370644 --- Comment #3 from Alexander Stehlik --- The problem still seems to be present in current versions (tested on Fedora 28): kf5-kimap-18.04.3-1.fc28.src.rpm KMail: 5.8.3 KDE Frameworks 5.48.0 Qt 5.11.1 -- 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.
[ksysguard] [Bug 400300] New: KSysGuard crashed upon close
https://bugs.kde.org/show_bug.cgi?id=400300 Bug ID: 400300 Summary: KSysGuard crashed upon close Product: ksysguard Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: notux...@gmail.com Target Milestone: --- Application: ksysguard (5.14.2) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.19.0-1-MANJARO x86_64 Distribution: "Netrunner Rolling" -- Information about the crash: - What I was doing when the application crashed: Opened KSysGuard from System Load Viewer desktop widget, after that closed KSysGuard window and it crashed -- Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7174a18000 (LWP 2689))] Thread 5 (Thread 0x7f716a879700 (LWP 2694)): #0 0x7f71818d2afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f716ae131ac in () at /usr/lib/dri/i965_dri.so #2 0x7f716ae12ee8 in () at /usr/lib/dri/i965_dri.so #3 0x7f71818cca9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f71819e6b23 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f717114f700 (LWP 2692)): #0 0x7f71819dbc21 in poll () at /usr/lib/libc.so.6 #1 0x7f717af1aee0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f717af1afce in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f7180155fe4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f71801018cc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f717ff4aeb9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f7180440ba6 in () at /usr/lib/libQt5DBus.so.5 #7 0x7f717ff54f65 in () at /usr/lib/libQt5Core.so.5 #8 0x7f71818cca9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f71819e6b23 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f717276a700 (LWP 2691)): #0 0x7f71819dbc21 in poll () at /usr/lib/libc.so.6 #1 0x7f717bbd1630 in () at /usr/lib/libxcb.so.1 #2 0x7f717bbd32db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f71738e6c5a in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f717ff54f65 in () at /usr/lib/libQt5Core.so.5 #5 0x7f71818cca9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f71819e6b23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f7174a11700 (LWP 2690)): #0 0x7f71818d2afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f717fdb7cd1 in __gthread_cond_wait (__mutex=, __cond=) at /build/gcc/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu/bits/gthr-default.h:864 #2 0x7f717fdb7cd1 in std::condition_variable::wait(std::unique_lock&) (this=, __lock=...) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/condition_variable.cc:53 #3 0x7f717ebeef14 in () at /usr/lib/libQt5WebKit.so.5 #4 0x7f717ebef039 in () at /usr/lib/libQt5WebKit.so.5 #5 0x7f717fdbe063 in std::execute_native_thread_routine(void*) (__p=0x5654535cbcd0) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/thread.cc:80 #6 0x7f71818cca9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f71819e6b23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f7174a18000 (LWP 2689)): [KCrash Handler] #6 0x7f717ffc8da6 in operator==(QString const&, QString const&) () at /usr/lib/libQt5Core.so.5 #7 0x7f7180cd5358 in QLabel::setText(QString const&) () at /usr/lib/libQt5Widgets.so.5 #8 0x7f7181b1fe15 in () at /usr/lib/libkdeinit5_ksysguard.so #9 0x7f718176b5b9 in KSGRD::SensorAgent::processAnswer(char const*, int) () at /usr/lib/libksgrd.so.7 #10 0x7f7181772cd0 in () at /usr/lib/libksgrd.so.7 #11 0x7f718012cbd0 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #12 0x7f71800952eb in QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #13 0x7f718009af44 in () at /usr/lib/libQt5Core.so.5 #14 0x7f718009b3a0 in () at /usr/lib/libQt5Core.so.5 #15 0x7f718012ca7c in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #16 0x7f71801386ba in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #17 0x7f7180138a12 in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #18 0x7f7180ba4e14 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #19 0x7f7180bac6e1 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7f7180102c39 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x7f7180156c2b
[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.
[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 377492] Video Profiles vs Project settings issues
https://bugs.kde.org/show_bug.cgi?id=377492 emohr changed: What|Removed |Added Version|16.12.2 |18.08.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399184] Shortcut doesn't saves
https://bugs.kde.org/show_bug.cgi?id=399184 q...@tvchd.com changed: What|Removed |Added CC||q...@tvchd.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from q...@tvchd.com --- any news/updates on this? I found out that changing shortcut to something else than meta+A also disappears after plasma restart or login/logout. Also in System Settings > Shortcuts > Global Shortcuts > Plasma it says that activate home widget is assigned to meta+A, and sometimes that record disappears, sometimes not. Anyway I still need to manually set this shortcut in home widget settings :( -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400254] Allow pixel font sizes in text tool
https://bugs.kde.org/show_bug.cgi?id=400254 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #3 from Boudewijn Rempt --- Um... Working in points is what we intended. And since we render through Qt's font engine, I doubt that really small pixel fonts will actually work well in any case. -- 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 Francis Herne changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||m...@flherne.uk --- Comment #2 from Francis Herne --- Reproducible with current 5.3-git. A file containing only '
[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.
[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.
[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.
[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 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.
[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.
[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.
[Active Window Control] [Bug 399757] Can AWC use buttons style from the current Window decoration?
https://bugs.kde.org/show_bug.cgi?id=399757 --- Comment #30 from Michail Vourlakos --- (In reply to Chris Holland from comment #29) > > 2. I dont quite like how the layout of AWC is produced. Is trying to do too > > many things e.g. buttons above the window title of menu etc... > > > I read somewhere that for [2] Zren is playing with it. > > I've thought about changing the defaults to something more Ubuntu Unity > like. There's now alternative widgets for displaying just the buttons + app > title + global menu > Is there an alternative widget for displaying active window buttons that I don't know of? -- 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.
