[dolphin] [Bug 420027] Status bar unnecessarily says "Unknown size" when an entry under certain sections of places panel is selected
https://bugs.kde.org/show_bug.cgi?id=420027
Méven Car changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit||https://invent.kde.org/syst
||em/dolphin/commit/bf4388c75
||525cffd150a51e6c4e0455f60db
||520f
Version Fixed In||20.08
Status|CONFIRMED |RESOLVED
--- Comment #10 from Méven Car ---
Git commit bf4388c75525cffd150a51e6c4e0455f60db520f by Méven Car.
Committed on 08/06/2020 at 05:49.
Pushed by meven into branch 'master'.
Status bar: Hide the space free bar when size is unknown
Summary:
Related: bug 46
FIXED-IN: 20.08
Test Plan: {F8312398}
Reviewers: #dolphin, ngraham, broulik, #vdg, elvisangelaccio
Reviewed By: #dolphin, ngraham, #vdg, elvisangelaccio
Subscribers: elvisangelaccio, kfm-devel
Tags: #dolphin
Differential Revision: https://phabricator.kde.org/D29213
M +4-2src/statusbar/dolphinstatusbar.cpp
M +3-1src/statusbar/spaceinfoobserver.cpp
M +1-0src/statusbar/spaceinfoobserver.h
M +45 -18 src/statusbar/statusbarspaceinfo.cpp
M +6-0src/statusbar/statusbarspaceinfo.h
https://invent.kde.org/system/dolphin/commit/bf4388c75525cffd150a51e6c4e0455f60db520f
--
You are receiving this mail because:
You are watching all bug changes.
[kio-extras] [Bug 422226] Status bar says "Unknown size" when I open an archive (tar.gz, zip and 7z formats) as folder
https://bugs.kde.org/show_bug.cgi?id=46
Méven Car changed:
What|Removed |Added
Version Fixed In||20.08
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
Latest Commit||https://invent.kde.org/syst
||em/dolphin/commit/bf4388c75
||525cffd150a51e6c4e0455f60db
||520f
--- Comment #2 from Méven Car ---
Git commit bf4388c75525cffd150a51e6c4e0455f60db520f by Méven Car.
Committed on 08/06/2020 at 05:49.
Pushed by meven into branch 'master'.
Status bar: Hide the space free bar when size is unknown
Summary:
Related: bug 420027
FIXED-IN: 20.08
Test Plan: {F8312398}
Reviewers: #dolphin, ngraham, broulik, #vdg, elvisangelaccio
Reviewed By: #dolphin, ngraham, #vdg, elvisangelaccio
Subscribers: elvisangelaccio, kfm-devel
Tags: #dolphin
Differential Revision: https://phabricator.kde.org/D29213
M +4-2src/statusbar/dolphinstatusbar.cpp
M +3-1src/statusbar/spaceinfoobserver.cpp
M +1-0src/statusbar/spaceinfoobserver.h
M +45 -18 src/statusbar/statusbarspaceinfo.cpp
M +6-0src/statusbar/statusbarspaceinfo.h
https://invent.kde.org/system/dolphin/commit/bf4388c75525cffd150a51e6c4e0455f60db520f
--
You are receiving this mail because:
You are watching all bug changes.
[kstars] [Bug 422613] New: No tool-tips for control icons in "What's Interesting..."
https://bugs.kde.org/show_bug.cgi?id=422613 Bug ID: 422613 Summary: No tool-tips for control icons in "What's Interesting..." Product: kstars Version: 3.4.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: n...@sonic.net Target Milestone: --- SUMMARY The meanings of the various icons at the bottom of the "What's Interesting..." panel (gear, magnifying glass with 'i', curved arrow, eye, star, down arrow, question mark) are not explained. No tool-tip appears when hovering over them. (The left-arrow is labeled "Back", but the others have no labels.) STEPS TO REPRODUCE 1. Click "Tools", then "What's Interesting..." 2. Hover mouse over any of the icons at the bottom of the panel that appears OBSERVED RESULT Nothing happens. EXPECTED RESULT Tool-tips should appear that describe the function of each button. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 KDE Plasma Version: 5.18.5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420704] External Editor changes not reflected in Digikam thumbnail
https://bugs.kde.org/show_bug.cgi?id=420704 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||7.0.0 --- Comment #6 from Maik Qualmann --- In digiKam-7.0.0-rc we have a new option under Tools "Scan for new Items". This also works if you have a search view open. I close the bug. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415798] [Wayland] task switcher is black after changing
https://bugs.kde.org/show_bug.cgi?id=415798 Mojahed Yavazi changed: What|Removed |Added Version|5.17.4 |git master CC||mojahed...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 409919] [Wayland] KDE application don't remember maximization state after closing and re-opening
https://bugs.kde.org/show_bug.cgi?id=409919 Mojahed Yavazi changed: What|Removed |Added Version|5.60.0 |5.70.0 CC||mojahed...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419956] Export errors after a certain number of photos in the 2nd pass
https://bugs.kde.org/show_bug.cgi?id=419956 --- Comment #5 from Maik Qualmann --- Can you please send me an image with this caption? Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414984] panel applets animation not working on plasma wayland
https://bugs.kde.org/show_bug.cgi?id=414984 Mojahed Yavazi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 422612] New: Don't display devices with a single unplugged port
https://bugs.kde.org/show_bug.cgi?id=422612 Bug ID: 422612 Summary: Don't display devices with a single unplugged port Product: plasma-pa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: n...@kde.org CC: plasma-b...@kde.org Target Milestone: --- Created attachment 129134 --> https://bugs.kde.org/attachment.cgi?id=129134=edit Messy audio device display My new laptop--a Lenovo ThinkPad X1 Yoga--has a very messy audio device selection in the plasma-pa KCM and applet. It displays three devices for HDMI/DisplayPort audio (two for the two Thunderbolt+DisplayPort ports, and one for the HDMI port). Each of these devices has a single port, which is listed as "unplugged" in pavucontrol, accurately reflecting their status. We should consider filtering out devices with a single port that is listed as "unplugged" because interacting with them does nothing and therefore they are simply visual clutter. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422597] Upload counts on Google Drive space
https://bugs.kde.org/show_bug.cgi?id=422597 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- No, this is restricted in the API, see here: https://developers.google.com/photos/library/guides/api-limits-quotas#photo-storage-quality Maik -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 422190] Unreadable row under account details when Breeze Dark global theme is used
https://bugs.kde.org/show_bug.cgi?id=422190 --- Comment #1 from Peter J. Mello --- I'm experiencing precisely the same thing since adding the KDE Neon Git-Unstable repository to my Kubuntu 20.04 LTS system. Without sifting through the commit history yet, this smells like a regression. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 422190] Unreadable row under account details when Breeze Dark global theme is used
https://bugs.kde.org/show_bug.cgi?id=422190 Peter J. Mello changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 422611] New: Export to non-default keyserver broken
https://bugs.kde.org/show_bug.cgi?id=422611 Bug ID: 422611 Summary: Export to non-default keyserver broken Product: kgpg Version: 20.04.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@opensource.sf-tec.de Reporter: ad...@petermello.net Target Milestone: --- SUMMARY The option to select a keyserver to communicate with in the Key Server Dialog window is inoperative; the default keyserver is always used instead. DESCRIPTION Finding one of my keys to be absent from keys2.kfwebs.net, the site KGpg itself directs to when selecting the menu item Keys|Open Key URL, I entered the application settings and added it to the list of keyservers successfully. Proceeding to the menu item File|Key Server Dialog, I selected the new keyserver and the key in question from the drop-down lists and clicked the Export button. Though the message indicated that the outcome was a success, the output below indicated that the contacted server was my default keyserver and not the specific one I had selected above. Subsequent packet capture on TCP port 11371 using Wireshark confirmed that was indeed the case. I observed that the keyserver selection drop-down on the Key Server Dialog window was ignored in every iteration of my debug attempts regardless of which server was chosen, communication always took place with the configured default keyserver. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 LTS "Focal Fossa" with KDE Neon Dev-Unstable package repository active KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 422542] smartphone put (nearly always) in vibration mode
https://bugs.kde.org/show_bug.cgi?id=422542 --- Comment #3 from Duns --- I was wrong: my smartphone is not put in "silence" mode, but in "vibration" mode. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 422542] smartphone put (nearly always) in vibration mode
https://bugs.kde.org/show_bug.cgi?id=422542 Duns changed: What|Removed |Added Summary|smartphone put (nearly |smartphone put (nearly |always) in do not disturb |always) in vibration mode |(/silent) mode | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421688] Fedora 31 LInux KDE Plasma 5.17.5 Keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=421688 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421296] WiFi disconnecting and reconnecting randomly
https://bugs.kde.org/show_bug.cgi?id=421296 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420901] Discover Startup
https://bugs.kde.org/show_bug.cgi?id=420901 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421968] The onion skin is not working for me.
https://bugs.kde.org/show_bug.cgi?id=421968 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 421947] Movie durations visible in KDE Plasma Version 5.18.4 no longer displayed
https://bugs.kde.org/show_bug.cgi?id=421947 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421243] Krita does not recognize pen pressure but Huion drivers do
https://bugs.kde.org/show_bug.cgi?id=421243 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 421961] File transfer from intern SSD (ext4) to external HDD (ntfs) freezes OS for about 10 seconds
https://bugs.kde.org/show_bug.cgi?id=421961 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 422610] kinfocenter5 show wrong USB-Device sub version number
https://bugs.kde.org/show_bug.cgi?id=422610 Dieter Nützel changed: What|Removed |Added CC||die...@nuetzel-hh.de -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 422610] kinfocenter5 show wrong USB-Device sub version number
https://bugs.kde.org/show_bug.cgi?id=422610 Dieter Nützel changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 422610] New: kinfocenter5 show wrong USB-Device sub version number
https://bugs.kde.org/show_bug.cgi?id=422610 Bug ID: 422610 Summary: kinfocenter5 show wrong USB-Device sub version number Product: kinfocenter Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: USB Devices Assignee: hubn...@gmail.com Reporter: die...@nuetzel-hh.de CC: plasma-b...@kde.org Target Milestone: --- Created attachment 129133 --> https://bugs.kde.org/attachment.cgi?id=129133=edit kinfocenter5-5.18.5-1.12.x86_64.png SUMMARY kinfocenter5 (openSUSE Tumbleweed version 5.18.5-1.2.x86_64 and several former) show wrong USB device sub version number (the '.' dot is @ the wrong position. STEPS TO REPRODUCE 1. open kinfocenter5 2. open Devices 3. open USB-Devices OBSERVED RESULT USB 1.01 / 2.01 / 3.01 / etc. (see attachment) EXPECTED RESULT USB 1.10 / 2.10 / 3.10 / etc. lsusb.py (examples) 1-1.2 04b4:0060 00 2IFs [USB 1.10, 1.5 Mbps, 100mA] (Areson USB Device) 1-1.4 04a9:220d ff 1IF [USB 1.10,12 Mbps, 500mA] (Canon CanoScan) usb3 1d6b:0003 09 1IF [USB 3.10, 1 Mbps, 0mA] (xhci-hcd :0f:00.0) hub SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed / 5.18.5 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 387366] Energy consumption statistics not available
https://bugs.kde.org/show_bug.cgi?id=387366 --- Comment #16 from Dieter Nützel --- (In reply to Dieter Nützel from comment #15) > (In reply to Dieter Nützel from comment #14) > > I can second that. > > > > kinfocenter5-5.18.5-1.2.x86_64 > > -rwxr-xr-x 1 root root 114176 31. Mai 02:53 > > /usr/lib64/qt5/plugins/kcms/kcm_energyinfo.so > > > > opensuse Tumbleweed > > kde apps 20.04.1 > > plasma 5.18.5 > > kde frameworks 5.70.0 > > qt 5.15.0 > > But something in the logs: > > /home/dieter> kinfocenter > Couldn't load plugin "kcms/kcm_about_distro" : "Die dynamische Bibliothek > konnte nicht gefunden werden." -- falling back to old-style loading from > desktop file rwxr-xr-x 1 root root 64848 31. Mai 02:53 /usr/lib64/qt5/plugins/kcm_about_distro.so Is in the 'wrong' place. If I link it over to /usr/lib64/qt5/plugins/kcms lrwxrwxrwx 1 root root 22 8. Jun 05:24 kcm_about_distro.so -> ../kcm_about_distro.so I get this: Error creating object from plugin "/usr/lib64/qt5/plugins/kcm_about_distro.so" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379959] Could not start database initializer
https://bugs.kde.org/show_bug.cgi?id=379959 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372680] Cannot delete files from NAS
https://bugs.kde.org/show_bug.cgi?id=372680 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 387366] Energy consumption statistics not available
https://bugs.kde.org/show_bug.cgi?id=387366
--- Comment #15 from Dieter Nützel ---
(In reply to Dieter Nützel from comment #14)
> I can second that.
>
> kinfocenter5-5.18.5-1.2.x86_64
> -rwxr-xr-x 1 root root 114176 31. Mai 02:53
> /usr/lib64/qt5/plugins/kcms/kcm_energyinfo.so
>
> opensuse Tumbleweed
> kde apps 20.04.1
> plasma 5.18.5
> kde frameworks 5.70.0
> qt 5.15.0
But something in the logs:
/home/dieter> kinfocenter
Couldn't load plugin "kcms/kcm_about_distro" : "Die dynamische Bibliothek
konnte nicht gefunden werden." -- falling back to old-style loading from
desktop file
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option allow_draw_out_of_order overridden by
environment.
Cyclic dependency detected between
"file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
and
"file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/FormLayout.qml:250:13: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:50:5: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ComboBox.qml:96:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:44: Error:
Cannot assign [undefined] to QObject*
[krita] [Bug 422609] New: Canvas entirely broken on 4k screens in latest Krita Plus
https://bugs.kde.org/show_bug.cgi?id=422609 Bug ID: 422609 Summary: Canvas entirely broken on 4k screens in latest Krita Plus Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: Microsoft Windows Status: REPORTED Severity: grave Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: i...@ralek.art Target Milestone: --- Created attachment 129132 --> https://bugs.kde.org/attachment.cgi?id=129132=edit Affected canvas I updated to the latest version of Krita Plus, (Hash 428be56) And the canvas is entirely inoperable on my Cintiq. It works fine on my main screen, but the second it's dragged to my 4k one, it breaks. Attached is what it looks like. The bottom left quadrant is the actual canvas, but the rest of the canvas is unusable. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 387366] Energy consumption statistics not available
https://bugs.kde.org/show_bug.cgi?id=387366 Dieter Nützel changed: What|Removed |Added CC||die...@nuetzel-hh.de --- Comment #14 from Dieter Nützel --- I can second that. kinfocenter5-5.18.5-1.2.x86_64 -rwxr-xr-x 1 root root 114176 31. Mai 02:53 /usr/lib64/qt5/plugins/kcms/kcm_energyinfo.so opensuse Tumbleweed kde apps 20.04.1 plasma 5.18.5 kde frameworks 5.70.0 qt 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373266] Albums disappears from view
https://bugs.kde.org/show_bug.cgi?id=373266 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 96072] add ability to import planner tasks
https://bugs.kde.org/show_bug.cgi?id=96072 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org --- Comment #2 from gjditchfi...@acm.org --- Imendio Planner is now GNOME planner, https://wiki.gnome.org/Apps/Planner -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 422608] New: spectacle -solo capura todo (2 pantallas)
https://bugs.kde.org/show_bug.cgi?id=422608 Bug ID: 422608 Summary: spectacle -solo capura todo (2 pantallas) Product: Spectacle Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: ajorgederosa...@yahoo.com.ar CC: k...@david-redondo.de Target Milestone: --- el capturador de pantalla Spectacle: lo quiero configurar p q capture solo area o monitor o ventana actual, y no anda, solo captura todo (incluyendo 1 monitor y el TV x hdmi) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 422607] New: jpg porcentaje de compresion no funciona
https://bugs.kde.org/show_bug.cgi?id=422607 Bug ID: 422607 Summary: jpg porcentaje de compresion no funciona Product: gwenview Version: 19.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: ajorgederosa...@yahoo.com.ar Target Milestone: --- -cuando grabo jpg no comprime segun porcentaje, 10% 50% 90% 80% 1% es igual siempre es el mismo archivo. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 422606] New: salir con tecla escape de app
https://bugs.kde.org/show_bug.cgi?id=422606 Bug ID: 422606 Summary: salir con tecla escape de app Product: gwenview Version: Other (add details in bug description) Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: ajorgederosa...@yahoo.com.ar Target Milestone: --- Gwenview: no anda redefinir teclado para ampliar y reducir imagen con tecla del teclado numerico + y - quiero redefinir q con esc valla p atras en el visor, y luego salga del visor, no me deja, si configuro esc, cuando la apreto no hace paso intermedio hacia atras directamente sale -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 422605] New: cambio de resolucion, iconos desplazados
https://bugs.kde.org/show_bug.cgi?id=422605 Bug ID: 422605 Summary: cambio de resolucion, iconos desplazados Product: Active Window Control Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: ajorgederosa...@yahoo.com.ar CC: plasma-b...@kde.org Target Milestone: --- -en el escritorio de kubuntu (kde plasma 5.18.4)una app q me cambia la resolucion de la pantalla a una menor, luego cuando vuelvo al escritorio con resolucion anterior iconos quedan desplazados, eso no tiene q pasar, me acuerdo q en microsoft windows tambien ocurre, si tiene una logica, pero en linux lo pueden mejorar a q restaure como estaba. -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 422604] problemas con las ventanas en 2 pantallas
https://bugs.kde.org/show_bug.cgi?id=422604 Jorge de rosario changed: What|Removed |Added Platform|Other |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 422604] New: problemas con las ventanas en 2 pantallas
https://bugs.kde.org/show_bug.cgi?id=422604 Bug ID: 422604 Summary: problemas con las ventanas en 2 pantallas Product: Active Window Control Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: ajorgederosa...@yahoo.com.ar CC: plasma-b...@kde.org Target Milestone: --- -en el escritorio de kubuntu (kde plasma 5.18.4) kwin por ejemplo con vlc(con kate pasa diferente) y teniendo 2 pantallas (donde quiero q aparezcan las ventanas inicialmente en en 1) pero cuando reinicio app recuerda la ultima ubicacion, entonces si lo puse en pantalla 2, aparece cuando la inicio en la 2, cuando quiero q siempre aparezcan en la 1. ahora ej con kate: -en el escritorio de kubuntu (kde plasma 5.18.4) kwin por ejemplo con kate y teniendo 2 pantallas (donde quiero q aparezcan las ventanas inicialmente en en 1) pero cuando reinicio app recuerda la ultima ubicacion, eso anda ok (recordar tamaño no funciona), siempre y cuando no me valla a la otra pantalla, pero cuando pongo en pantalla 2, aparece cuando la inicio en la 2, cuando quiero q siempre aparezcan en la 1. deberia recordar la ultima coordenada de la pantalla 1 (me parece q para q eso se cumpla hay q poner condicion q se apliquen reglas segun dimensiones de pantallas, ej. para q sepa cuando aplicar coordenadas anteriores cuando me voy a pantalla no deseada. -por ejemplo forzar esta ok:si pongo forzar en la 1, esta bien, me la fuerza y nunca me deja ponerla en la 2, por mas uqe reinicie aplicacion, eso esta bien!. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422381] Make Krita's Windows Installer Translatable
https://bugs.kde.org/show_bug.cgi?id=422381 --- Comment #19 from Tyson Tan --- The updated simplified Chinese patch I submitted has been accepted by NSIS. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 94625] associate time with events that have no time associated with them by drag and drop
https://bugs.kde.org/show_bug.cgi?id=94625 gjditchfi...@acm.org changed: What|Removed |Added CC||kde-2011...@dotancohen.com --- Comment #3 from gjditchfi...@acm.org --- *** Bug 192315 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 192315] Drag all-day item to specific hours
https://bugs.kde.org/show_bug.cgi?id=192315 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |DUPLICATE CC||gjditchfi...@acm.org Status|CONFIRMED |RESOLVED --- Comment #3 from gjditchfi...@acm.org --- *** This bug has been marked as a duplicate of bug 94625 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #56 from TheRogueGrunt --- (In reply to Simon Redman from comment #55) > (In reply to TheRogueGrunt from comment #54) > > > > Trying to test this tonight but I have never done anything with Android > > Studio before. Is there a guide on how I'm supposed to do this? Also, what > > do I need to even edit? Do I download the source code of kdeconnect-sms from > > github? > > The instructions for how to download the patch in question are on Gitlab: > https://invent.kde.org/network/kdeconnect-android/-/merge_requests/158 under > the button labeled "Check out branch" > > I don't remember the exact process to set up Android Studio, but if I recall > correctly there was some way to open or import an existing project I... cannot make any sense of any of this. Its just a whole ton of code that I have no idea what it does or even what is what. I have the folder "kdeconnect-android-use-simple-conversation-interface" and everything inside it, but how the hell do I make that an .apk to put on my phone? -- You are receiving this mail because: You are watching all bug changes.
[katomic] [Bug 422603] New: Crash when pressing shift+tab
https://bugs.kde.org/show_bug.cgi?id=422603 Bug ID: 422603 Summary: Crash when pressing shift+tab Product: katomic Version: 4.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dim...@gmail.com Reporter: calend...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Press the "shift" key and the "tab" key simultaneously OBSERVED RESULT Segmentation fault EXPECTED RESULT Unknown, probably cycle to previous tile SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) Linux Mint 19.3 KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION Tab cycles the selected tile so I assumed shift+tab would cycle in reverse. It crashes -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422144] Clock and system tray icons are misaligned in the left of the taskbar, for a short moment, after logging in
https://bugs.kde.org/show_bug.cgi?id=422144 --- Comment #2 from Raul --- (In reply to Konrad Materka from comment #1) > Is this really a problem? It is a part of booting process, elements are > loaded and starts in parallel, it takes only fraction of second. At the end > all elements are there correctly placed. It depends. KDE emphasizes animations a lot, so this looks a bit unpolished -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421937] In GTK applications that use CSD, pointing the cursor to the top right edge of the window doesn't select the close button
https://bugs.kde.org/show_bug.cgi?id=421937 Raul changed: What|Removed |Added Summary|In applications that use|In GTK applications that |CSD, pointing cursor to the |use CSD, pointing the |top right edge of the |cursor to the top right |window doesn't select the |edge of the window doesn't |close button|select the close button -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422602] In Kickoff favorites section, after right clicking on a item, there is a delay to show the menu
https://bugs.kde.org/show_bug.cgi?id=422602 Raul changed: What|Removed |Added Summary|In KLauncher favorites |In Kickoff favorites |section, after right|section, after right |clicking on a item, there |clicking on a item, there |is a delay to show the menu |is a delay to show the menu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422602] In Kickoff favorites section, after right clicking on a item, there is a delay to show the menu
https://bugs.kde.org/show_bug.cgi?id=422602 --- Comment #1 from Raul --- I meant Kickoff, not KLauncher. Sorry! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422602] New: In KLauncher favorites section, after right clicking on a item, there is a delay to show the menu
https://bugs.kde.org/show_bug.cgi?id=422602 Bug ID: 422602 Summary: In KLauncher favorites section, after right clicking on a item, there is a delay to show the menu Product: plasmashell Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: raul94go...@outlook.com.br CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY - STEPS TO REPRODUCE 1. Logout and login 2. Open KLauncher 3. Right click in a item in the favorites section OBSERVED RESULT The menu will show with a delay. EXPECTED RESULT Menu not delaying after right clicking. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION I've encountered this bug after several minutes after being logged in, but I wasn't able to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #55 from Simon Redman --- (In reply to TheRogueGrunt from comment #54) > > Trying to test this tonight but I have never done anything with Android > Studio before. Is there a guide on how I'm supposed to do this? Also, what > do I need to even edit? Do I download the source code of kdeconnect-sms from > github? The instructions for how to download the patch in question are on Gitlab: https://invent.kde.org/network/kdeconnect-android/-/merge_requests/158 under the button labeled "Check out branch" I don't remember the exact process to set up Android Studio, but if I recall correctly there was some way to open or import an existing project -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 422601] valgrind throws 'has_nonempty_rw' assertion failure on dlopen() if other mappings exist
https://bugs.kde.org/show_bug.cgi?id=422601 Laurent Pinchart changed: What|Removed |Added Summary|valgrind throwns|valgrind throws |'has_nonempty_rw' assertion |'has_nonempty_rw' assertion |failure on dlopen() if |failure on dlopen() if |other mappings exist|other mappings exist -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 422601] valgrind throwns 'has_nonempty_rw' assertion failure on dlopen() if other mappings exist
https://bugs.kde.org/show_bug.cgi?id=422601 Laurent Pinchart changed: What|Removed |Added CC||laurent.pinchart@ideasonboa ||rd.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 422601] New: valgrind throwns 'has_nonempty_rw' assertion failure on dlopen() if other mappings exist
https://bugs.kde.org/show_bug.cgi?id=422601 Bug ID: 422601 Summary: valgrind throwns 'has_nonempty_rw' assertion failure on dlopen() if other mappings exist Product: valgrind Version: 3.15 SVN Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: laurent.pinch...@ideasonboard.com Target Milestone: --- Created attachment 129131 --> https://bugs.kde.org/attachment.cgi?id=129131=edit Test case that exhibits the issue SUMMARY When processing the mmap() calls from dlopen(), valgrind loads debug symbols from the ELF library being opened. If conflicting other mappings were previously created, a 'has_nonempty_rw' assertion failure is thrown. STEPS TO REPRODUCE 1. Compile the attached test case with 'gcc -o valgrind-test -lm valgrind-test.c' 2. Run 'valgrind ./valgrind-test' OBSERVED RESULT ==23177== Memcheck, a memory error detector ==23177== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==23177== Using Valgrind-3.15.0-608cb11914-20190413 and LibVEX; rerun with -h for copyright info ==23177== Command: ./valgrind-test ==23177== --23177-- Valgrind options: --23177---v --23177-- Contents of /proc/version: --23177-- Linux version 5.4.28-gentoo (root@pendragon) (gcc version 8.3.0 (Gentoo 8.3.0-r1 p1.1)) #1 SMP PREEMPT Fri Apr 17 17:51:31 EEST 2020 --23177-- --23177-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c-rdrand --23177-- Page sizes: currently 4096, max supported 4096 --23177-- Valgrind library directory: /usr/lib64/valgrind --23177-- Reading syms from /home/laurent/src/test/valgrind-test --23177-- Reading syms from /lib64/ld-2.30.so --23177-- Considering /usr/lib/debug/lib64/ld-2.30.so.debug .. --23177-- .. CRC is valid --23177-- Reading syms from /usr/lib64/valgrind/memcheck-amd64-linux --23177-- Considering /usr/lib/debug/usr/lib64/valgrind/memcheck-amd64-linux.debug .. --23177-- .. CRC is valid --23177--object doesn't have a dynamic symbol table --23177-- Scheduler: using generic scheduler lock implementation. --23177-- Reading suppressions file: /usr/lib64/valgrind/default.supp ==23177== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-23177-by-laurent-on-??? ==23177== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-23177-by-laurent-on-??? ==23177== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-23177-by-laurent-on-??? ==23177== ==23177== TO CONTROL THIS PROCESS USING vgdb (which you probably ==23177== don't want to do, unless you know exactly what you're doing, ==23177== or are doing some strange experiment): ==23177== /usr/lib64/valgrind/../../bin/vgdb --pid=23177 ...command... ==23177== ==23177== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==23177== /path/to/gdb ./valgrind-test ==23177== and then give GDB the following command ==23177== target remote | /usr/lib64/valgrind/../../bin/vgdb --pid=23177 ==23177== --pid is optional if only one valgrind process is running ==23177== --23177-- REDIR: 0x401e290 (ld-linux-x86-64.so.2:strlen) redirected to 0x580c9122 (vgPlain_amd64_linux_REDIR_FOR_strlen) --23177-- REDIR: 0x401e070 (ld-linux-x86-64.so.2:index) redirected to 0x580c913c (vgPlain_amd64_linux_REDIR_FOR_index) --23177-- Reading syms from /usr/lib64/valgrind/vgpreload_core-amd64-linux.so --23177-- Considering /usr/lib/debug/usr/lib64/valgrind/vgpreload_core-amd64-linux.so.debug .. --23177-- .. CRC is valid --23177-- Reading syms from /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so --23177-- Considering /usr/lib/debug/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so.debug .. --23177-- .. CRC is valid ==23177== WARNING: new redirection conflicts with existing -- ignoring it --23177-- old: 0x0401e290 (strlen ) R-> (.0) 0x580c9122 vgPlain_amd64_linux_REDIR_FOR_strlen --23177-- new: 0x0401e290 (strlen ) R-> (2007.0) 0x04839db0 strlen --23177-- REDIR: 0x401aab0 (ld-linux-x86-64.so.2:strcmp) redirected to 0x483ae00 (strcmp) --23177-- REDIR: 0x401e7d0 (ld-linux-x86-64.so.2:mempcpy) redirected to 0x483e6d0 (mempcpy) --23177-- Reading syms from /lib64/libdl-2.30.so --23177-- Considering /usr/lib/debug/lib64/libdl-2.30.so.debug .. --23177-- .. CRC is valid --23177-- Reading syms from /lib64/libc-2.30.so --23177-- Considering /usr/lib/debug/lib64/libc-2.30.so.debug .. --23177-- .. CRC is valid --23177-- REDIR: 0x4940660 (libc.so.6:memmove) redirected to 0x482c1b0 (_vgnU_ifunc_wrapper) --23177-- REDIR: 0x493f9e0 (libc.so.6:strncpy) redirected to 0x482c1b0 (_vgnU_ifunc_wrapper) --23177-- REDIR: 0x4940970 (libc.so.6:strcasecmp) redirected to 0x482c1b0 (_vgnU_ifunc_wrapper) --23177-- REDIR: 0x493f320 (libc.so.6:strcat) redirected to 0x482c1b0 (_vgnU_ifunc_wrapper) --23177--
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #54 from TheRogueGrunt --- (In reply to Simon Redman from comment #52) > (In reply to poperigby from comment #51) > > > > I'm happy to test. How can I do it? > > If you already have Android Studio installed, you can build using that, > otherwise you can install Android Studio or build using gradle > https://developer.android.com/studio/build/building-cmdline > > I've had pretty much 0% success sharing .apks built from my development > session, so I can't provide a pre-built one, sorry Trying to test this tonight but I have never done anything with Android Studio before. Is there a guide on how I'm supposed to do this? Also, what do I need to even edit? Do I download the source code of kdeconnect-sms from github? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422574] File Open requires .pdf suffix to display in "All Supported Files"
https://bugs.kde.org/show_bug.cgi?id=422574 --- Comment #3 from K.J. Petrie --- The GIMP. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422600] New: Okular is unable to print to fit page
https://bugs.kde.org/show_bug.cgi?id=422600 Bug ID: 422600 Summary: Okular is unable to print to fit page Product: okular Version: 1.10.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: gregorystar...@gmail.com Target Milestone: --- Created attachment 129130 --> https://bugs.kde.org/attachment.cgi?id=129130=edit This highlights the broken print. SUMMARY I was printing some scanned-in documents today, and when printed thru Okular, there were large borders around the document. When printed through Evince, however, the documents fit the page perfectly (with fit to printable area selected). STEPS TO REPRODUCE 1. Print document with print set to fit. OBSERVED RESULT Massive margins around the page. EXPECTED RESULT Page fits as in Evince. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Attached are pictures of the broken print, here is a google drive link to a reproducible document: https://drive.google.com/file/d/1UquoDj-ld2mMAFyqkVjh_eIYj9Uuu3WE/view?usp=sharing This printed as shown in Okular, but successfuly, filling the page, in Evince. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 422098] Notification shown after a batch renaming of items reports the total number of items (files and dirs) as "files"
https://bugs.kde.org/show_bug.cgi?id=422098 Ahmad Samir changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/kio/commit/a874dc35c ||049df7877d9d5dee1c7e67dd206 ||1a89 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Ahmad Samir --- Git commit a874dc35c049df7877d9d5dee1c7e67dd2061a89 by Ahmad Samir. Committed on 07/06/2020 at 12:42. Pushed by dfaure into branch 'master'. [BatchRenameJob] Use KJob::Items when reporting the progress info A batch rename job is usually fast (direct renaming), calculating the number of individual files and dirs would mean stat'ing which would make things slower for little gain. Instead, per dfaure's suggestion in the bug report, use "items" as a neutral term to represent files and dirs, this way the notification message would be "correct" when reporting "Job Finished, x of y items". Also note that if the user is using Dolphin, or other KIO based file managers, that data is already visible in the status bar when the user selects the files/dirs to be renamed. M +2-2src/core/batchrenamejob.cpp https://invent.kde.org/frameworks/kio/commit/a874dc35c049df7877d9d5dee1c7e67dd2061a89 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #53 from poperi...@tuta.io --- (In reply to Simon Redman from comment #52) > (In reply to poperigby from comment #51) > > > > I'm happy to test. How can I do it? > > If you already have Android Studio installed, you can build using that, > otherwise you can install Android Studio or build using gradle > https://developer.android.com/studio/build/building-cmdline > > I've had pretty much 0% success sharing .apks built from my development > session, so I can't provide a pre-built one, sorry Ok. I'll do it soon when I have time. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #52 from Simon Redman --- (In reply to poperigby from comment #51) > > I'm happy to test. How can I do it? If you already have Android Studio installed, you can build using that, otherwise you can install Android Studio or build using gradle https://developer.android.com/studio/build/building-cmdline I've had pretty much 0% success sharing .apks built from my development session, so I can't provide a pre-built one, sorry -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #51 from poperi...@tuta.io --- (In reply to Simon Redman from comment #50) > This is my latest proposal to resolve this issue: If someone watching this > thread with an affected device could test it and leave comments on the PR, > it would be appreciated: > https://invent.kde.org/network/kdeconnect-android/-/merge_requests/158 I'm happy to test. How can I do it? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 Simon Redman changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ | |kdeconnect-android/commit/4 | |a0c53610f5b8f82162bda0a2ac8 | |1d789f00e64a| --- Comment #50 from Simon Redman --- This is my latest proposal to resolve this issue: If someone watching this thread with an affected device could test it and leave comments on the PR, it would be appreciated: https://invent.kde.org/network/kdeconnect-android/-/merge_requests/158 -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 418024] Cannot see gdrive directory
https://bugs.kde.org/show_bug.cgi?id=418024 --- Comment #1 from Elvis Angelaccio --- Is this still an issue? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422574] File Open requires .pdf suffix to display in "All Supported Files"
https://bugs.kde.org/show_bug.cgi?id=422574 Albert Astals Cid changed: What|Removed |Added Severity|normal |wishlist --- Comment #2 from Albert Astals Cid --- It's not a bug because it's not a bug, a bug is "i wanted to print and instead it kick me in the face" At most it's a missing feature. "Linux does not identify file types by name or suffix." Prove it, give me a graphical program that will do what you say. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 418300] Crash using keyboard to rename folder after folder
https://bugs.kde.org/show_bug.cgi?id=418300 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org --- Comment #1 from Elvis Angelaccio --- Can you reproduce this crash? If yes, please provide a valgrind log. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422574] File Open requires .pdf suffix to display in "All Supported Files"
https://bugs.kde.org/show_bug.cgi?id=422574 K.J. Petrie changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #1 from K.J. Petrie --- Please explain how this can not be a bug. PDF is a supported format. A PDF file is therefore supported, so why should it not be shown as such? Closing "Not a bug" without explaining why is unhelpful. Why is this not a bug? Only a Windows user would think this not a bug. It can't be intentional behaviour because it makes no sense. Linux does not identify file types by name or suffix. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422500] Okular does not open djvu files with non-ASCII names on Windows
https://bugs.kde.org/show_bug.cgi?id=422500 Christoph Cullmann changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/okular/commit/bb532664 |hics/okular/commit/3ad9fc70 |30aee995288fca92ec4cc5376fd |28bba05f6d9fbee7f5e3c18bcdd |4c2e3 |42264 --- Comment #5 from Christoph Cullmann --- Git commit 3ad9fc7028bba05f6d9fbee7f5e3c18bcdd42264 by Christoph Cullmann. Committed on 07/06/2020 at 11:52. Pushed by aacid into branch 'release/20.04'. allow unicode filenames to work on Windows, too M +3-3generators/djvu/kdjvu.cpp https://invent.kde.org/graphics/okular/commit/3ad9fc7028bba05f6d9fbee7f5e3c18bcdd42264 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422574] File Open requires .pdf suffix to display in "All Supported Files"
https://bugs.kde.org/show_bug.cgi?id=422574 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG CC||aa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 --- Comment #3 from Johannes Zarl-Zierl --- Created attachment 129129 --> https://bugs.kde.org/attachment.cgi?id=129129=edit Script for logging calls to ffmpeg Can you try adding the attached script to your path and see if ffmpeg is having problems with some files? A quick way to add the script to your path would be: mkdir ~/temp-ffmpeg # copy script to ~/temp-ffmpeg chmod +x ~/temp-ffmpeg/ffmpeg export PATH="~/temp-ffmpeg:$PATH" kphotoalbum Afterwards, you should find a file /tmp/ffmpeg.log on your system. Of special interest would be any lines not starting with "[0]" and/or the last few lines. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422569] Destkop effects disabled at login by Latte-Dock
https://bugs.kde.org/show_bug.cgi?id=422569 --- Comment #1 from Nataniel --- UPDATE: It seems it is not related to dock-only blur after all. I disabled background on the dock and I got the problem again at boot. Sorry, it seems the issue doesn't happen ALL the time (I'd say 8/10), and didn't happen when I tried narrowing down the bug. Is there a way to find out where this bug comes from? Willing to help find out ;) -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 422599] New: Better sorting
https://bugs.kde.org/show_bug.cgi?id=422599 Bug ID: 422599 Summary: Better sorting Product: elisa Version: 0.4.1 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: herb...@graeber-clan.de Target Milestone: --- SUMMARY MP3 Tage have special tags for sorting albums, album artists, artists, composers and titles. Hos shall be used for sorting. STEPS TO REPRODUCE 1. Add an album of "The Beatles" 2. Sort by album artist OBSERVED RESULT 1. The Beatles" are shown under "T" EXPECTED RESULT "The Beatles" shall be sorted under "B" ADDITIONAL INFORMATION There are tags ALBUMSORT, ALBUMARTISTSORT, ARTISTSORT, COMPOSERSORT and TITLESORT. THse shall be used for sorting if provides by the files. If not sorting shall fallback to the tags without the SORT-suffix. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379959] Could not start database initializer
https://bugs.kde.org/show_bug.cgi?id=379959 dajomu changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372680] Cannot delete files from NAS
https://bugs.kde.org/show_bug.cgi?id=372680 dajomu changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373266] Albums disappears from view
https://bugs.kde.org/show_bug.cgi?id=373266 dajomu changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 422598] New: Windows borders get thick when scaling the screen
https://bugs.kde.org/show_bug.cgi?id=422598 Bug ID: 422598 Summary: Windows borders get thick when scaling the screen Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: mrausch...@gmx.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY i have laptop with a full hd 14" screen. So all is very small. To work better I scale the screen in the seetings for example to 125%. Then all windows get a bold black border (window decoration / aurorae) even if no window border was set. If you scale the screen more the border gets even thicker. Additionally I saw some visual problems in some other places. For example the check boxes seem to get a small shadow or something like this looking strange. STEPS TO REPRODUCE 1. Go to the settings and set the display scaling to 125 %. or more. 2. All windows get a bold black frame - even if you set "no borders". 3. You can test it with most of the window decorations (aurorare) - for example with "Qogir". OBSERVED RESULT s. above. EXPECTED RESULT Windows should not get any thicker border then in 100% scaling setting. If I scale the screen I do not want to scale the window decoration. It looks quire ugly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: neon 18.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 422596] Discover window's content is transparent at startup
https://bugs.kde.org/show_bug.cgi?id=422596 --- Comment #1 from Raul --- Also, maximizing the window after opening Discover makes the shadow of the previous window state to appear. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422597] New: Upload counts on Google Drive space
https://bugs.kde.org/show_bug.cgi?id=422597 Bug ID: 422597 Summary: Upload counts on Google Drive space Product: digikam Version: 7.0.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-Google Assignee: digikam-bugs-n...@kde.org Reporter: k...@euhm.de Target Milestone: --- Upload using the Google Photos Export always counts on Google Drive/Photos space, even if "Upload original image file" is not checked. Is it possible to upload to the "free unlimited space" (with high quality and reduced image file size)? Or is the API not able to do that? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 422596] New: Discover window's content is transparent at startup
https://bugs.kde.org/show_bug.cgi?id=422596 Bug ID: 422596 Summary: Discover window's content is transparent at startup Product: Discover Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: raul94go...@outlook.com.br CC: aleix...@kde.org Target Milestone: --- Created attachment 129128 --> https://bugs.kde.org/attachment.cgi?id=129128=edit discover bug SUMMARY STEPS TO REPRODUCE 1. Open Discover OBSERVED RESULT Window's content is transparent/glitched. EXPECTED RESULT Make the content to not be transparent. Maybe adding a "loading" text is a solution. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421392] plasmashell crashes when opening the thermal monitor widget settings
https://bugs.kde.org/show_bug.cgi?id=421392 Alexander Kandaurov changed: What|Removed |Added CC||aakandau...@yandex.ru --- Comment #23 from Alexander Kandaurov --- Did a git bisect on plasma-frameworks, the breaking commit is 48f60533b92231c706da3c9ff0f62cff206ee8d5. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 246196] When filling in forms, make it possible to set the font size of the forms
https://bugs.kde.org/show_bug.cgi?id=246196 Shmerl changed: What|Removed |Added CC||shtetl...@gmail.com --- Comment #18 from Shmerl --- So currently there is no way to change form font size in Okular? This truncation makes this feature rather broken. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 422148] Respects settings only when the spectacle window is opened
https://bugs.kde.org/show_bug.cgi?id=422148 Antonio changed: What|Removed |Added CC||antonio.prc...@gmail.com --- Comment #1 from Antonio --- Hi, thanks for he report. But I'm not quite sure what you mean with "Crop screenshot". Do you mean "take a screenshot" or literally cropping an image? Sorry for me not understanding this properly, I'd like to help but first I need to understand the question :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419956] Export errors after a certain number of photos in the 2nd pass
https://bugs.kde.org/show_bug.cgi?id=419956 hmueller changed: What|Removed |Added CC||k...@euhm.de --- Comment #4 from hmueller --- Hi Maik, I got this error message too: Error transferring https://photoslibrary.googleapis.com/v1/mediaItems:batchCreate - server replied: Bad Request Uploaded only 16 pics and it took only a view seconds. I uploads and fails at the end. Album is empty after that action in Google Photos. Restarting digikam did not help. After experimenting a while it happens also if I upload only one picture. If I choose another picture it works. The difference is the picture caption. In this case I had ,3,-5 FN=0 FB = 0 outdoor = 1 ISO = 50.00 exp=10.00 return = 0 FM0 CR0.51 FC10101: bfalic 1211X:zH87020gzz0 d e9 007804385f03184502ee1040 92417e389 0 029d 2528c 0 0 0 0 0 0 0 028ca1e0a1ac 179 1276a1a1a190 179 1260a1c1a1b9 178 124aa1dba1e2 178 1234a1d9a1fa 177 121ea1cba213 176 1208a19aa1ff 177 1234a156a1bf 277 123fa1bba221 276 124aa1d0a21e 276 1255a1e6a215 276 1260a1f2a206 276 1255a1f7a1f6 377 12851c85c 2595e5e 05e 0 b 04f 0 b 7 7 7 6 8 9 7 a4445787446515d4e3d3f a b2529 d e 9 b2330 b b211a5e4e3c433c2c3e432320101021271e1e b b d b1311 c c138e1388138813881388138813881388138913881388138813881388138813881388138813881388138e1388138813881388138813881388138d138813881388138b1388138813881614138813881388161413881388138816141388138813881590138813881388159013881388138815bc1388138813881389138813881388138813881388138815a613881388138815d21388138813881389138813881388138813881388138813931388138813881388138813881388138813881388138813b013881388138813881388138813881388138813881388138813881388138813881388138813881388138813881388138813881388138813881388138813881388138813881388138813881388138813881388138813881388138813881388 Produced by my smartphone camera app. If I delete this caption, upload works ... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 421849] Unable to create proxy clips
https://bugs.kde.org/show_bug.cgi?id=421849 --- Comment #9 from Frank --- (SOLVED) Mark solved? In the 'Proxy' tab from 'Project settings' I changed the 'Encoding profile' to x264. Now all clips are perfectly converted to proxy clips. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 421382] Add more kmymoney icons
https://bugs.kde.org/show_bug.cgi?id=421382 --- Comment #9 from Dawid Wróbel --- Some additional effort made in 2016: https://forum.kde.org/viewtopic.php?f=69=133554 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 422595] New: No tab focus indication for certain components in gtk theme
https://bugs.kde.org/show_bug.cgi?id=422595 Bug ID: 422595 Summary: No tab focus indication for certain components in gtk theme Product: Breeze Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: xsr...@gmail.com Target Milestone: --- SUMMARY There is no way to tell that a checkbox or a radio button has tab focus in the GTK theme. This problem does not seem to impact the QT theme. STEPS TO REPRODUCE 1. Open the GTK theme preview for Breeze 2. Tab through the components OBSERVED RESULT There is indication of focus on the radio button, the checkbox, or the tabs. EXPECTED RESULT The label of the button, checkbox and/or tab is underlined, like in the QT theme. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 422394] Spectacle not being finalized when ran in background mode
https://bugs.kde.org/show_bug.cgi?id=422394 Antonio changed: What|Removed |Added CC||antonio.prc...@gmail.com --- Comment #3 from Antonio --- Just tried it with v20.04.1 on Manjaro and it does close properly. Tho the notification has to disappear which takes 10 seconds. Just to get this right: The notification appears & disappears, but spectacle keeps still running? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 422506] Capture Mode Radio Buttons instead of Drop Down Menu.
https://bugs.kde.org/show_bug.cgi?id=422506 Antonio changed: What|Removed |Added CC||antonio.prc...@gmail.com --- Comment #1 from Antonio --- IMHO, wasted space. You can also use your mouse scroll wheel to 'quickly' change the Capture Mode. And than there are the shortcuts: Meta + Print -> Active window Meta + Shift + Print -> Rectangular region etc. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 422594] New: Akregator crashes a few minutes after starting
https://bugs.kde.org/show_bug.cgi?id=422594 Bug ID: 422594 Summary: Akregator crashes a few minutes after starting Product: akregator Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jonathancc...@fastmail.fm Target Milestone: --- Application: akregator (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-55-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: Starting Akregator brings up an absurd number of unread items, then after a few minutes it crashes (Installed from Ubuntu packages) -- 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 0x7f6b3cf2cf00 (LWP 3308))] Thread 21 (Thread 0x7f6acb98b700 (LWP 6591)): #0 0x7f6b491f46e0 in futex_abstimed_wait_cancelable (private=, abstime=0x7f6acb98a470, clockid=, expected=0, futex_word=0x7f6acb98a5b8) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 0x7f6b491f46e0 in __pthread_cond_wait_common (abstime=0x7f6acb98a470, clockid=, mutex=0x7f6acb98a568, cond=0x7f6acb98a590) at pthread_cond_wait.c:520 #2 0x7f6b491f46e0 in __pthread_cond_timedwait (cond=0x7f6acb98a590, mutex=0x7f6acb98a568, abstime=0x7f6acb98a470) at pthread_cond_wait.c:656 #3 0x7f6b4c47110b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f6b4c471ab2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f6b4c471ba6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f6b4c433705 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f6b4c435f96 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f6b4c436258 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f6b4c473c75 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f6b491ed669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f6b511ce323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f6b1b7fe700 (LWP 3584)): #0 0x7f6b491f46e0 in futex_abstimed_wait_cancelable (private=, abstime=0x7f6b1b7fd470, clockid=, expected=0, futex_word=0x7f6b1b7fd5b8) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 0x7f6b491f46e0 in __pthread_cond_wait_common (abstime=0x7f6b1b7fd470, clockid=, mutex=0x7f6b1b7fd568, cond=0x7f6b1b7fd590) at pthread_cond_wait.c:520 #2 0x7f6b491f46e0 in __pthread_cond_timedwait (cond=0x7f6b1b7fd590, mutex=0x7f6b1b7fd568, abstime=0x7f6b1b7fd470) at pthread_cond_wait.c:656 #3 0x7f6b4c47110b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f6b4c471ab2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f6b4c471ba6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f6b4c433705 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f6b4c435f96 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f6b4c436258 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f6b4c473c75 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f6b491ed669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f6b511ce323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f6b1affd700 (LWP 24634)): #0 0x7f6b491f46e0 in futex_abstimed_wait_cancelable (private=, abstime=0x7f6b1affc470, clockid=, expected=0, futex_word=0x7f6b1affc5b8) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 0x7f6b491f46e0 in __pthread_cond_wait_common (abstime=0x7f6b1affc470, clockid=, mutex=0x7f6b1affc568, cond=0x7f6b1affc590) at pthread_cond_wait.c:520 #2 0x7f6b491f46e0 in __pthread_cond_timedwait (cond=0x7f6b1affc590, mutex=0x7f6b1affc568, abstime=0x7f6b1affc470) at pthread_cond_wait.c:656 #3 0x7f6b4c47110b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f6b4c471ab2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f6b4c471ba6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f6b4c433705 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f6b4c435f96 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f6b4c436258 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f6b4c473c75 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f6b491ed669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f6b511ce323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f6aca887700 (LWP 3380)): #0
[konqueror] [Bug 422557] Backport/merge location bar functionality from Dolphin to Konqueror
https://bugs.kde.org/show_bug.cgi?id=422557 hyil...@gmail.com changed: What|Removed |Added CC||hyil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397065] 'perspective', 'warp' and 'cage' and 'liquify' transformation modes do not work on vector layers
https://bugs.kde.org/show_bug.cgi?id=397065 ametedi...@gmail.com changed: What|Removed |Added CC||ametedi...@gmail.com --- Comment #3 from ametedi...@gmail.com --- This is also a critical feature for me. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 323295] Mouse settings for pointer and threshold have no effect.
https://bugs.kde.org/show_bug.cgi?id=323295 Alan Prescott changed: What|Removed |Added CC|alanjpresc...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 323295] Mouse settings for pointer and threshold have no effect.
https://bugs.kde.org/show_bug.cgi?id=323295 --- Comment #5 from Alan Prescott --- Ok, stet my last. It looks like this was a hardware glitch. I rebooted to Windoze 10 (dual boot) and had the same problems with the mouse so obviously not a software problem. Switched mouse off (again), replaced batteries (again) and then unplugged/replugged wifi dongle and then all Ok. Once the RSI has cooled down a bit I can get back to programming my Python script :-) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 422098] Notification shown after a batch renaming of items reports the total number of items (files and dirs) as "files"
https://bugs.kde.org/show_bug.cgi?id=422098 --- Comment #5 from Ahmad Samir --- Git commit 7ef49de74f7feb973df80f2997548e548c1d6a26 by Ahmad Samir. Committed on 07/06/2020 at 13:26. Pushed by dfaure into branch 'master'. Integrate the KJob::Unit::Items This unit can be used to report the progress info as a total, without distinguishing between the respective number of e.g. files and dirs handled by the job. M +6-0src/kuiserverjobtracker.cpp M +29 -12 src/kwidgetjobtracker.cpp M +4-2src/kwidgetjobtracker_p.h https://invent.kde.org/frameworks/kjobwidgets/commit/7ef49de74f7feb973df80f2997548e548c1d6a26 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 422593] New: KRunner crashes when typing
https://bugs.kde.org/show_bug.cgi?id=422593 Bug ID: 422593 Summary: KRunner crashes when typing Product: krunner Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: nicolas.fe...@gmx.de Target Milestone: --- Application: krunner (5.19.80) (Compiled from sources) Qt Version: 5.15.0 Frameworks Version: 5.71.0 Operating System: Linux 5.6.15-1-MANJARO x86_64 Windowing system: Wayland Distribution: Manjaro Linux -- Information about the crash: As soon as I start typing KRunner crashes reliably, no matter what is typed The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Bus error Content of s_kcrashErrorMessage: (null) [KCrash Handler] #5 QReadWriteLock::tryLockForRead(int) (this=0x560e027ee010, timeout=-1) at thread/qreadwritelock.cpp:263 #6 0x7f10c00ce7f1 in QReadLocker::relock() (this=0x7ffeee439b70) at /home/nico/kde/usr/include/QtCore/qreadwritelock.h:106 #7 0x7f10c00ce875 in QReadLocker::QReadLocker(QReadWriteLock*) (this=0x7ffeee439b70, areadWriteLock=0x560e027ee010) at /home/nico/kde/usr/include/QtCore/qreadwritelock.h:125 #8 0x7f10c00ce2ac in Plasma::QueryMatch::urls() const (this=0x560e03638890) at /home/nico/kde/src/krunner/src/querymatch.cpp:264 #9 0x7f10c00bc0c1 in Plasma::AbstractRunner::mimeDataForMatch(Plasma::QueryMatch const&) (this=0x560e036389e0, match=...) at /home/nico/kde/src/krunner/src/abstractrunner.cpp:203 #10 0x7f10c00d93b2 in Plasma::RunnerManagerPrivate::loadInstalledRunner(QExplicitlySharedDataPointer) (this=0x560e02af2900, service=...) at /home/nico/kde/src/krunner/src/runnermanager.cpp:331 #11 0x7f10c00d8454 in Plasma::RunnerManagerPrivate::loadRunners() (this=0x560e02af2900) at /home/nico/kde/src/krunner/src/runnermanager.cpp:211 #12 0x7f10c00d670c in Plasma::RunnerManager::launchQuery(QString const&, QString const&) (this=0x560e02ad4db0, untrimmedTerm=..., runnerName=...) at /home/nico/kde/src/krunner/src/runnermanager.cpp:803 #13 0x7f10c00d648a in Plasma::RunnerManager::launchQuery(QString const&) (this=0x560e02ad4db0, term=...) at /home/nico/kde/src/krunner/src/runnermanager.cpp:773 #14 0x7f10c0189a07 in Milou::RunnerResultsModel::setQueryString(QString const&) (this=0x560e02be9a80, queryString=...) at /home/nico/kde/src/milou/lib/runnerresultsmodel.cpp:194 #15 0x7f10c0184215 in Milou::ResultsModel::setQueryString(QString const&) (this=0x560e02ad4aa0, queryString=...) at /home/nico/kde/src/milou/lib/resultsmodel.cpp:370 #16 0x7f10c017e94d in Milou::ResultsModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x560e02ad4aa0, _c=QMetaObject::WriteProperty, _id=0, _a=0x7ffeee439ff0) at lib/milou_autogen/EWIEGA46WW/moc_resultsmodel.cpp:228 #17 0x7f10d5f5188f in QQmlPropertyData::writeProperty(QObject*, void*, QFlags) const (flags=..., value=0x7ffeee439fc8, target=, this=0x7f10b01f2f68) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:375 #18 GenericBinding<10>::doStore(QString, QQmlPropertyData const*, QFlags) const (flags=..., pd=0x7f10b01f2f68, value=..., this=0x560e02ceefc0) at qml/qqmlbinding.cpp:342 #19 GenericBinding<10>::write(QV4::Value const&, bool, QFlags) (this=0x560e02ceefc0, result=..., isUndefined=, flags=...) at qml/qqmlbinding.cpp:323 #20 0x7f10d5f5208e in QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) (this=0x560e02ceefc0, watcher=..., flags=..., scope=...) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/jsruntime/qv4scopedvalue_p.h:239 #21 0x7f10d5f4fd44 in QQmlBinding::update(QFlags) (this=0x560e02ceefc0, flags=...) at qml/qqmlbinding.cpp:194 #22 0x7f10d5f2bddd in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) (endpoint=, a=0x0) at qml/qqmlnotifier.cpp:104 #23 0x7f10d47089d5 in doActivate(QObject*, int, void**) (sender=0x560e02b8c060, signal_index=32, argv=argv@entry=0x0) at kernel/qobject_p.h:110 #24 0x7f10d47023bd in QMetaObject::activate(QObject*, int, int, void**) (sender=, signalOffset=, local_signal_index=, argv=argv@entry=0x0) at kernel/qobject.cpp:3959 #25 0x7f10d5ed87e5 in QQmlVMEMetaObject::activate(QObject*, int, void**) (this=this@entry=0x560e02b10f90, object=, index=, args=args@entry=0x0) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/qml/qqmlpropertycache_p.h:386 #26 0x7f10d5edadbd in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) (this=0x560e02b10f90, o=, c=, _id=, a=) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/qml/qqmlpropertycache_p.h:376 #27 0x7f10d5e1616a in QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*,
[kdenlive] [Bug 422592] Rendering speed extremly slow, when no filters are applied
https://bugs.kde.org/show_bug.cgi?id=422592 Harri changed: What|Removed |Added CC||bugs@uhrlau.de -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 422578] Window appears in the top-left corner of the screen with >100% scale factor on X11
https://bugs.kde.org/show_bug.cgi?id=422578 --- Comment #2 from Nate Graham --- Hmm, could be a Qt regression. :/ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 422592] New: Rendering speed extremly slow, when no filters are applied
https://bugs.kde.org/show_bug.cgi?id=422592 Bug ID: 422592 Summary: Rendering speed extremly slow, when no filters are applied Product: kdenlive Version: 20.04.1 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: bugs@uhrlau.de Target Milestone: --- SUMMARY Rendering an video with h264 or h265 is extremly slow when no filters are on the video.That means: When I render a video using any filter (even a dummy-"Transform" on Master Effects will do) it will take about 60 minutes for a 15 minute video. When I do the same video without any filter then rendering takes about 11 hours (11 times as much). Cpu usage is 100% on all cores in either case. This strange effect is independent of the video, raw format and so on. STEPS TO REPRODUCE 1. render a short movie without any filter from mp4 input. 2. render the same movie using any filter, you can try "Transform" without giving it anything to do. 3. whatch the rendering times. OBSERVED RESULT rendering takes much longer without filter. EXPECTED RESULT rendering should take longer with filter. KDENLIVE-VERSION kdenlive-20.04.1b-x86_64.appimage SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.1 KDE Plasma Version: 5.18.90 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 4.12.14-lp151.28.48-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz Memory: 31,3 GiB Arbeitsspeicher Graphics Processor: GeForce GTX 1060 6GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 396889] When built from source, breeze-gtk displays no checkboxes in Firefox
https://bugs.kde.org/show_bug.cgi?id=396889 --- Comment #7 from Nate Graham --- (In reply to David Faure from comment #6) > (Also, that KCM messed up the font in Firefox (for tabs and URL bar etc.), > it's all an awful monospaced "Adobe Courier" now)... And I wish there was a > way to just pick the default KDE font... but I'm off-topic) Seems like a bug we should fix, not work around with otherwise unnecessary configurability. :) Can you file a bug on systemsettings | kcm_style? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422591] New: Add "logout" option after inactivity period
https://bugs.kde.org/show_bug.cgi?id=422591 Bug ID: 422591 Summary: Add "logout" option after inactivity period Product: Powerdevil Version: 5.18.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rossl...@gmail.com Target Milestone: --- SUMMARY We are multiple user on the same machine, and some leave idle sessions. I would like to set the power management so that idle users get logged off, but the only options are sleep/hibernate, lock screen and shutdown. STEPS TO REPRODUCE 1. Open Powerdevil configuration 2. Got to "Suspend session entry" 3. Check the options offered. OBSERVED RESULT No possibility to logout user/terminate session. EXPECTED RESULT This possibility is offered. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION My ultimate goal is to turn off the computer if there were only "idlers" logged in. Being able to poll the activity status of those users would be good already as I could write a cronjob that would do the rest. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422590] Cannot save or split layer - software froze
https://bugs.kde.org/show_bug.cgi?id=422590 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Platform|Windows CE |MS Windows CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Boudewijn Rempt --- Can you please specify which version of Krita you are using? Please attach the output of help->system information for bug reports to this report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422590] New: Cannot save or split layer - software froze
https://bugs.kde.org/show_bug.cgi?id=422590 Bug ID: 422590 Summary: Cannot save or split layer - software froze Product: krita Version: unspecified Platform: Windows CE OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: sallyseymo...@yahoo.com Target Milestone: --- SUMMARY I created a 2 layer drawing. File size 12Mb. I tried to split the colorize mask but I could not. When I tried to save the file as a back up, the system froze.I cannot save it - This is the message " You are saving a file while the image is still rendering. The saved file may be incomplete or corrupted. Please select a location where the original file will not be overridden!" SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
