[okular] [Bug 421484] Center viewport at mouse position during Ctrl-scroll zoom
https://bugs.kde.org/show_bug.cgi?id=421484 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Can you confirm that https://invent.kde.org/kde/okular/-/merge_requests/134 is what you want? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421464] XPkeywords not being updated
https://bugs.kde.org/show_bug.cgi?id=421464 --- Comment #6 from Maik Qualmann --- Git commit 243d975d99bc8dfd8ec7ba2678d62eed62f1a7a6 by Maik Qualmann. Committed on 14/05/2020 at 05:44. Pushed by mqualmann into branch 'master'. add Exif.Image.XPKeywords to the remove metadata BQM tool M +7-1core/dplugins/bqm/metadata/removemetadata/removemetadata.cpp https://invent.kde.org/kde/digikam/commit/243d975d99bc8dfd8ec7ba2678d62eed62f1a7a6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356899] Desktop Settings are not saved and loads default settings on reboot/startup.
https://bugs.kde.org/show_bug.cgi?id=356899 --- Comment #29 from Scott Grayban --- New bug created https://bugs.kde.org/show_bug.cgi?id=421498 because it's not exactly the same OP bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421499] Plasmashell crash when moving desktop icons
https://bugs.kde.org/show_bug.cgi?id=421499 DGLS changed: What|Removed |Added Platform|unspecified |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421499] New: Plasmashell crash when moving desktop icons
https://bugs.kde.org/show_bug.cgi?id=421499 Bug ID: 421499 Summary: Plasmashell crash when moving desktop icons Product: plasmashell Version: 5.18.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dgls...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.3.0-51-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: Rearanging icons on the desktop - Unusual behavior I noticed: Before the crash the icon that was being dragged didn't show the icon's graphic next to the cursor. - Custom settings of the application: Plasmashell running on a 4K display, with the UI scalled to 150% The crash can be reproduced sometimes. -- 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 0x7f3eb4c9f840 (LWP 3537))] Thread 8 (Thread 0x7f3e551f1700 (LWP 3553)): #0 0x7f3eade909f3 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f3eae8d51db in QWaitConditionPrivate::wait (deadline=..., this=0x55847821e2b0) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x7f3e9800a160, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f3eae8d5359 in QWaitCondition::wait (this=this@entry=0x7f3e9800a168, mutex=mutex@entry=0x7f3e9800a160, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #4 0x7f3eb29d8233 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x7f3e9800a158) at scenegraph/qsgthreadedrenderloop.cpp:255 #5 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x7f3e9800a0c0) at scenegraph/qsgthreadedrenderloop.cpp:905 #6 0x7f3eb29d8691 in QSGRenderThread::run (this=0x7f3e9800a0c0) at scenegraph/qsgthreadedrenderloop.cpp:1000 #7 0x7f3eae8cec2c in QThreadPrivate::start (arg=0x7f3e9800a0c0) at thread/qthread_unix.cpp:342 #8 0x7f3eade8a6db in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f3eae1c388f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 7 (Thread 0x7f3e56ea9700 (LWP 3550)): #0 0x7f3eae1b6bf9 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f3ea82535c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3ea82536dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3eaeb1d7cb in QEventDispatcherGlib::processEvents (this=0x7f3e5b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f3eaeabcd2a in QEventLoop::exec (this=this@entry=0x7f3e56ea8d20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f3eae8cd757 in QThread::exec (this=) at thread/qthread.cpp:536 #6 0x7f3e59808467 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f3eae8cec2c in QThreadPrivate::start (arg=0x5584780d1bc0) at thread/qthread_unix.cpp:342 #8 0x7f3eade8a6db in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f3eae1c388f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7f3e7d185700 (LWP 3544)): #0 0x7f3eade909f3 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f3eae8d51db in QWaitConditionPrivate::wait (deadline=..., this=0x558475669360) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x5584756692b0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f3eae8d5359 in QWaitCondition::wait (this=this@entry=0x5584756692b8, mutex=mutex@entry=0x5584756692b0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #4 0x7f3eb29d8233 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x5584756692a8) at scenegraph/qsgthreadedrenderloop.cpp:255 #5 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x558475669210) at scenegraph/qsgthreadedrenderloop.cpp:905 #6 0x7f3eb29d8691 in QSGRenderThread::run (this=0x558475669210) at scenegraph/qsgthreadedrenderloop.cpp:1000 #7 0x7f3eae8cec2c in QThreadPrivate::start (arg=0x558475669210) at thread/qthread_unix.cpp:342 #8 0x7f3eade8a6db in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f3eae1c388f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7f3e7fb47700 (LWP 3541)): #0 0x7f3eae1b6bf9 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f3ea82535c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3ea82536dc in g_main_context_iteration ()
[plasmashell] [Bug 421498] Desktop settings get nuked on every startup
https://bugs.kde.org/show_bug.cgi?id=421498 --- Comment #1 from Scott Grayban --- And just to be sure it wasn't my account since it had been updated/merged into the new plasma desktop I created a brand new user and the same issue persisted and desktop settings were not saved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421498] Desktop settings get nuked on every startup
https://bugs.kde.org/show_bug.cgi?id=421498 Scott Grayban changed: What|Removed |Added CC||sgray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421498] New: Desktop settings get nuked on every startup
https://bugs.kde.org/show_bug.cgi?id=421498 Bug ID: 421498 Summary: Desktop settings get nuked on every startup Product: plasmashell Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sgray...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Plasma Desktop Settings like Wallpaper,Desktop Layout (Folder View) etc. are lost and are resetted to defaults on reboot. STEPS TO REPRODUCE 1. Right click on desktop and click on desktop settings 2. Change layout to Desktop view. 3. Change wallpaper to blur and keep proportions 4. Logout and login OBSERVED RESULT Reverts to default settings. EXPECTED RESULT Should keep desired desktop settings. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 10 KDE Plasma Version: 5.14.5 Qt Version: 5.11.3 KDE Frameworks Version: 5.54.0 Kernel Version: 5.3.0-0.bpo.2-amd64 OS Type: 64-bit ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421464] XPkeywords not being updated
https://bugs.kde.org/show_bug.cgi?id=421464 --- Comment #5 from Maik Qualmann --- In BQM we have expanded the tool for removing metadata in digiKam-7.0.0-RC. It is easy to add the option to remove XPkeywords. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409739] [Question] Importing video files with multiple audio streams causes Kdenlive to only use the first audio stream - is multi-stream audio import worked on?
https://bugs.kde.org/show_bug.cgi?id=409739 Roger changed: What|Removed |Added CC||rogertgodzilla...@yahoo.com --- Comment #4 from Roger --- I would really like this feature. I have a bad habit of forgetting to do a sound check before recording, and having to deal with atrocious audio balance issues when editing. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 89299] prevent paste of newline characters
https://bugs.kde.org/show_bug.cgi?id=89299 Felipe Veas changed: What|Removed |Added CC||fjv...@gmail.com --- Comment #55 from Felipe Veas --- Apparently, some applications such as Firefox or Sublime Text tend to write to the clipboard using CRLF line endings. That wasn't really an issue when copy-pasting into Konsole since a popup would show up letting us to filter those extra CR characters if one wanted to. Then, last year in November, a couple of patches changed the filter behavior and one of those added the CR character to a whitelist [1], thus disabling the popup notification for this scenario. >From a somewhat related bug report [2], a similar issue affected Firefox when running on Wayland, in which the root cause was Gtk because of the way it normalizes the clipboard content depending on the mime type [3]. However, I am not sure if the same applies here because I use X11 instead, so at least it is not the same situation. Anyways, like George suggested, it would be nice to have the popup back, even if it is just a workaround for the time being. Thanks, Felipe [1] https://cgit.kde.org/konsole.git/commit/?id=5e142c9dadc8a00d7017c6f60603798bcaa6ae85 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1547595 [3] https://gitlab.gnome.org/GNOME/gtk/issues/2307 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 421496] KDE binary factory fails building KDE Connect for OSX
https://bugs.kde.org/show_bug.cgi?id=421496 idoitprone changed: What|Removed |Added Platform|Other |macOS Disk Images -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416739] Panel disappears from time to time and after a while re-appears
https://bugs.kde.org/show_bug.cgi?id=416739 --- Comment #19 from Mika Norén --- In my dual screen setup, a mysterious third output appears in .config/plasmashellrc under section [ScreenConnectors] What it's supposed to look like in my case: [ScreenConnectors] 0=DisplayPort-0 1=DisplayPort-1 What it looks like when this bug triggers: [ScreenConnectors] 0=DisplayPort-0 1=:0.0 2=DisplayPort-1 Sometimes it also looks like this: [ScreenConnectors] 0=DisplayPort-0 1=DisplayPort-1 2=:0.0 To restore the previous screen configuration, I remove the :0.0 -line from the section mentioned, and restore the order of the remaining valid outputs. I save changes and restarts plasmashell. (killall plasmashell && plasmashell --replace) Once plasmashell restarts, it's back to the intended screen configuration with all panels and widgets back in place again. This might or might not happen at any time when screens are turned on after being off, computer restarts or resuming from sleep. It's random and there seem to be no rime or reason to it. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 421497] Add age rating to mainfest
https://bugs.kde.org/show_bug.cgi?id=421497 --- Comment #2 from Urs Fleisch --- Thanks, I have added it. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 421497] Add age rating to mainfest
https://bugs.kde.org/show_bug.cgi?id=421497 Urs Fleisch changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||kid3/commit/83014d1bbf1690c ||713f7b4d87e06b2e365e2158f Status|REPORTED|RESOLVED --- Comment #1 from Urs Fleisch --- Git commit 83014d1bbf1690c713f7b4d87e06b2e365e2158f by Urs Fleisch. Committed on 14/05/2020 at 04:57. Pushed by ufleisch into branch 'master'. Add content rating to manifest This is required for Flatpak and it's part of the official standard: https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-content_rating M +1-0src/app/org.kde.kid3.appdata.xml https://invent.kde.org/kde/kid3/commit/83014d1bbf1690c713f7b4d87e06b2e365e2158f -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 421497] New: Add age rating to mainfest
https://bugs.kde.org/show_bug.cgi?id=421497 Bug ID: 421497 Summary: Add age rating to mainfest Product: kid3 Version: 3.8.x Platform: Flatpak OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: k...@kevindegeling.nl Target Milestone: --- the current appdata.xml does not have an oars tag. This is required for Flatpak and it's part of the official standard: https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-content_rating In the current version on Flatpak, I use sed to add an empty age rating element to the manifest: https://github.com/flathub/flathub/pull/1505 If you can add a tag to the manifest for the next version, then that would be great. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 419528] Dolphin crash smb connect with login
https://bugs.kde.org/show_bug.cgi?id=419528 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 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.
[plasmashell] [Bug 356899] Desktop Settings are not saved and loads default settings on reboot/startup.
https://bugs.kde.org/show_bug.cgi?id=356899 --- Comment #28 from Scott Grayban --- Forgot to add my KDE info in above comment... sorry. Operating System: Debian GNU/Linux 10 KDE Plasma Version: 5.14.5 Qt Version: 5.11.3 KDE Frameworks Version: 5.54.0 Kernel Version: 5.3.0-0.bpo.2-amd64 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz Memory: 15.7 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356899] Desktop Settings are not saved and loads default settings on reboot/startup.
https://bugs.kde.org/show_bug.cgi?id=356899 Scott Grayban changed: What|Removed |Added CC||sgray...@gmail.com --- Comment #27 from Scott Grayban --- Same issue as well still on Debian Buster. Only the Desktop settings are not being saved. I have tried everything using chattr +i to setting chmod 400 and still cannot get the desktop settings to save. And just to make sure it wasn't a issue using a old user account on my box I created a brand new account and on that account the same issue still happened. All settings are saved for everything BUT the desktop settings. Selected wallpaper is not being saved nor is the icon layout in Desktop Layout (Folder View). Switched to desktop mode and that didn't save either and keeps reverting back to the default desktop layout. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 420057] spectacle config
https://bugs.kde.org/show_bug.cgi?id=420057 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 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.
[Discover] [Bug 419175] Discover crashes every time I try to open a .flatpakrepo file
https://bugs.kde.org/show_bug.cgi?id=419175 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 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.
[Discover] [Bug 419253] Discovery crashes while installing the package org.freedesktop Nvidia435
https://bugs.kde.org/show_bug.cgi?id=419253 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 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 376197] Flattening an animation layer with a color filter is VERY SLOW
https://bugs.kde.org/show_bug.cgi?id=376197 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- 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.
[kio-extras] [Bug 419038] internal not specified error in libsmbclient in Network SMB search
https://bugs.kde.org/show_bug.cgi?id=419038 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #17 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.
[dolphin] [Bug 420736] Basic searching fails to find files
https://bugs.kde.org/show_bug.cgi?id=420736 --- 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.
[kdeconnect] [Bug 421496] New: KDE binary factory fails building KDE Connect for OSX
https://bugs.kde.org/show_bug.cgi?id=421496 Bug ID: 421496 Summary: KDE binary factory fails building KDE Connect for OSX Product: kdeconnect Version: unspecified Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: monkeyboy...@yahoo.com Target Milestone: --- SUMMARY Hi maintainers, I am here to inform you that the binary factory has been failing to build KDE Connect for OSX for over a month. https://binary-factory.kde.org/view/MacOS/job/kdeconnect-kde_Nightly_macos/ STEPS TO REPRODUCE 1. Wait one day 2. The build throw errors on the fourth step. 3. OBSERVED RESULT 05:18:16 + cd /Users/packaging/Craft/BinaryFactory/ 05:18:16 + /usr/local/bin/python3 craftmaster/Craftmaster.py --config binary-factory-tooling/craft/configs/master/CraftBinaryCache.ini --target macos-64-clang -c --no-cache --target master kdeconnect-kde 05:18:17 05:18:17 Status: None: None 0% ['extragear/kdeconnect-kde'] 05:18:17 05:18:17 *** Handling package: extragear/kdeconnect-kde, action: all *** 05:18:17 *** Action: fetch for extragear/kdeconnect-kde *** 05:18:17 executing command: /usr/bin/git fetch 05:18:18 From https://invent.kde.org/kde/kdeconnect-kde 05:18:18 08ea3d78..785f70c2 master -> origin/master 05:18:18 executing command: /usr/bin/git checkout master 05:18:18 Already on 'master' 05:18:18 Your branch is behind 'origin/master' by 1 commit, and can be fast-forwarded. 05:18:18(use "git pull" to update your local branch) 05:18:18 Updating 08ea3d78..785f70c2 05:18:18 Fast-forward 05:18:18 smsapp/qml/ConversationList.qml | 2 +- 05:18:18 1 file changed, 1 insertion(+), 1 deletion(-) 05:18:18 executing command: /usr/bin/git checkout master 05:18:18 Already on 'master' 05:18:18 Your branch is up to date with 'origin/master'. 05:18:18 *** Action: unpack for extragear/kdeconnect-kde *** 05:18:18 *** Action: compile for extragear/kdeconnect-kde *** 05:18:18 *** cmake -G "Ninja" -DBUILD_TESTING=ON -DCMAKE_INSTALL_PREFIX="/Users/packaging/Craft/BinaryFactory/macos-64-clang" -DCMAKE_PREFIX_PATH="/Users/packaging/Craft/BinaryFactory/macos-64-clang" -DCMAKE_BUILD_TYPE=RelWithDebInfo -DKDE_INSTALL_BUNDLEDIR="/Users/packaging/Craft/BinaryFactory/macos-64-clang/Applications/KDE" -DAPPLE_SUPPRESS_X11_WARNING=ON -DKDE_INSTALL_USE_QT_SYS_PATHS=ON "/Users/packaging/Craft/BinaryFactory/downloads/git/extragear/kdeconnect-kde" *** 05:18:18 executing command: "/Users/packaging/Craft/BinaryFactory/macos-64-clang/dev-utils/bin/cmake" -G "Ninja" -DBUILD_TESTING=ON -DCMAKE_INSTALL_PREFIX="/Users/packaging/Craft/BinaryFactory/macos-64-clang" -DCMAKE_PREFIX_PATH="/Users/packaging/Craft/BinaryFactory/macos-64-clang" -DCMAKE_BUILD_TYPE=RelWithDebInfo -DKDE_INSTALL_BUNDLEDIR="/Users/packaging/Craft/BinaryFactory/macos-64-clang/Applications/KDE" -DAPPLE_SUPPRESS_X11_WARNING=ON -DKDE_INSTALL_USE_QT_SYS_PATHS=ON "/Users/packaging/Craft/BinaryFactory/downloads/git/extragear/kdeconnect-kde" 05:18:19 -- The C compiler identification is AppleClang 11.0.0.1133 05:18:19 -- The CXX compiler identification is AppleClang 11.0.0.1133 05:18:19 -- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang 05:18:20 -- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang - works 05:18:20 -- Detecting C compiler ABI info 05:18:20 -- Detecting C compiler ABI info - done 05:18:20 -- Detecting C compile features 05:18:20 -- Detecting C compile features - done 05:18:20 -- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ 05:18:20 -- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ - works 05:18:20 -- Detecting CXX compiler ABI info 05:18:20 -- Detecting CXX compiler ABI info - done 05:18:20 -- Detecting CXX compile features 05:18:20 -- Detecting CXX compile features - done 05:18:21 CMake Error at CMakeLists.txt:14 (find_package): 05:18:21Could not find a configuration file for package "ECM" that is compatible 05:18:21with requested version "5.70.0". 05:18:21 05:18:21The following configuration files were considered but not accepted: 05:18:21 05:18:21 /Users/packaging/Craft/BinaryFactory/macos-64-clang/share/ECM/cmake/ECMConfig.cmake, version: 5.69.0 05:18:21 05:18:21 05:18:21 05:18:21 -- Configuring incomplete, errors occurred! 05:18:21 See also
[kdeconnect] [Bug 421496] KDE binary factory fails building KDE Connect for OSX
https://bugs.kde.org/show_bug.cgi?id=421496 idoitprone changed: What|Removed |Added URL||https://binary-factory.kde. ||org/view/MacOS/job/kdeconne ||ct-kde_Nightly_macos/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392343] Text editor's Font-Style droplist and Bold button are broken
https://bugs.kde.org/show_bug.cgi?id=392343 --- Comment #9 from Tyson Tan --- May I ask if we can, for the moment, just disable the "auto-completion" and "automatically selecting a font as you type" thing for the input box? It's very broken at the moment, inputting a font name is basically impossible and it really makes life so difficult around the text tool. Accessing font-style is also a nightmare because of it. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 421495] Feature request: push-to-talk (PTT) for recording streams/microphones
https://bugs.kde.org/show_bug.cgi?id=421495 Matthias Hartmann changed: What|Removed |Added CC||mahar...@mahartma.com -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 421495] New: Feature request: push-to-talk (PTT) for recording streams/microphones
https://bugs.kde.org/show_bug.cgi?id=421495 Bug ID: 421495 Summary: Feature request: push-to-talk (PTT) for recording streams/microphones Product: kmix Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: es...@kde.org Reporter: mahar...@mahartma.com Target Milestone: --- SUMMARY While using different kinds of video/audio conferencing software every day I realized the need of a push-to-talk (PTT) shortcut for muting and unmuting recording streams, or more specific, microphones. Since not every conferencing software supports configuring PTT, it might be a great feature for KDE. Adding PTT could be accomplished by enabling users to set global push-to-talk options and a global shortcut and then activate PTT for specific recording streams. Potential options for PTT could be (imspired by mumble): - DoublePush Time: If you press the PTT shortcut twice in this period of time, push-to-talk will be "locked" and the microphone active until you press the shortcut once again, to mute the microphone - Hold Time: The time the microphone stays activated after releasing the shortcut, to avoid that words could be cut off when releasing the key too early This feature could also enhance security because PTT is not controlled by conferencing software itself, but on OS level. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420614] Devices panel: "Hard disk of xxx.x GiB" displays a strange xxx.x value (NOT being GiB)
https://bugs.kde.org/show_bug.cgi?id=420614 --- Comment #2 from Christoph Feck --- Does the size shown in the Devices panel come from Solid? -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 400117] crash on exit
https://bugs.kde.org/show_bug.cgi?id=400117 Christoph Feck changed: What|Removed |Added CC||dac...@public-files.de --- Comment #16 from Christoph Feck --- *** Bug 420358 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 420358] Choqok
https://bugs.kde.org/show_bug.cgi?id=420358 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 400117 *** -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 419480] Crashed during scaling or bolding
https://bugs.kde.org/show_bug.cgi?id=419480 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 391018 *** -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 391018] Crash after adding new column in Calligra Sheets
https://bugs.kde.org/show_bug.cgi?id=391018 Christoph Feck changed: What|Removed |Added CC||k...@startport.com --- Comment #8 from Christoph Feck --- *** Bug 419480 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 391018] Crash after adding new column in Calligra Sheets
https://bugs.kde.org/show_bug.cgi?id=391018 Christoph Feck changed: What|Removed |Added CC||bird_ma...@hotmail.com --- Comment #7 from Christoph Feck --- *** Bug 420643 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 420643] Crash after pasting formatting
https://bugs.kde.org/show_bug.cgi?id=420643 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 391018 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420429] Cannot rightclick files in Dolphin without it crashing
https://bugs.kde.org/show_bug.cgi?id=420429 --- Comment #4 from Christoph Feck --- Please add the backtrace. Then it will be possible to tell which debug symbol packages are still missing. Without a backtrace, nothing can be investigated. See also https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415986] Printing to HP1120C with gutenprint driver from Okular not working.
https://bugs.kde.org/show_bug.cgi?id=415986 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from Christoph Feck --- New information was added with comment 6; changing status for inspection. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419420] Plasma crashes anytime.
https://bugs.kde.org/show_bug.cgi?id=419420 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #8 from Christoph Feck --- There aren't many places in Qt's xcb platform plugin that call exit(), so it is possible to investigate without debug symbols, see https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/platforms/xcb/qxcbconnection.cpp#n982 I suggest to report this issue directly to Qt developers via https://bugreports.qt.io/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421494] New: Dolphin crashes when creating new folder with existing folder name
https://bugs.kde.org/show_bug.cgi?id=421494 Bug ID: 421494 Summary: Dolphin crashes when creating new folder with existing folder name Product: dolphin Version: 20.04.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sm.emon...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Trying to create new folder with existing folder name, dolphin crashes. STEPS TO REPRODUCE 1. Create new folder with existing folder name 2. May not crash at first try. 3. For me crashed almost every second or first try. OBSERVED RESULT Dolphin Crashes. EXPECTED RESULT Show warning about existing folder. SOFTWARE/OS VERSIONS Linus: Manjaro 20.04 Linux/KDE Plasma: Linux (x86_64) release 5.6.11-1-MANJARO (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 (built against 5.14.2) ADDITIONAL INFORMATION Terminal output: [smie@smie-pc ~]$ dolphin kf5.kio.core: We got some errors while running testparm "Error loading services." kf5.kio.core: We got some errors while running 'net usershare info' kf5.kio.core: "Can't load /etc/samba/smb.conf - run testparm to debug it\n" "A folder named /home/smie/a already exists." "A folder named /home/smie/a already exists." Segmentation fault (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 421493] New: After being able to boot in legacy mode still gives this crash while shutting down or restart computer
https://bugs.kde.org/show_bug.cgi?id=421493 Bug ID: 421493 Summary: After being able to boot in legacy mode still gives this crash while shutting down or restart computer Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: dario.j.a.mart...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 128441 --> https://bugs.kde.org/attachment.cgi?id=128441=edit debugger of logout shutdown restart crash diagnosis SUMMARY STEPS TO REPRODUCE 1. after clean install used i normal boot mode without usb live session 2. but same error like in live mode still occurs unable to restart or shutdown computer 3. says that the ksmserver-logout-greeter or whatsoever crashed please restart application OBSERVED RESULT Unable to shutdown or restart computer EXPECTED RESULT Able to shutdown without "long press" power button SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: latest KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421295] Krita zooms to the max and rotates wildly when using touch gestures with a Wacom Intuos Pro M on Linux
https://bugs.kde.org/show_bug.cgi?id=421295 --- Comment #2 from P. Varet --- Pull request sent. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420353] No options to add activites in settings
https://bugs.kde.org/show_bug.cgi?id=420353 Christoph Feck changed: What|Removed |Added Resolution|MOVED |WAITINGFORINFO --- Comment #3 from Christoph Feck --- > OBSERVED RESULT > Blank options Could you please add a screen shot of the window where you would expect the options to appear? -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 419739] No icons on the left (Albums, Artists, Songs, ...) when using Qt 5.15
https://bugs.kde.org/show_bug.cgi?id=419739 --- Comment #9 from Christoph Feck --- If this is still a problem, please change the status to REOPENED and provide tested version and steps to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419538] Cannot disable touchpad while typing
https://bugs.kde.org/show_bug.cgi?id=419538 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421295] Krita zooms to the max and rotates wildly when using touch gestures with a Wacom Intuos Pro M on Linux
https://bugs.kde.org/show_bug.cgi?id=421295 --- Comment #1 from P. Varet --- Created attachment 128440 --> https://bugs.kde.org/attachment.cgi?id=128440=edit Patch fixing the issue. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 421492] New: Screen brightness isn’t reset when it was dimmed because of inactivity and a paused media is put on play from KDE Connect
https://bugs.kde.org/show_bug.cgi?id=421492 Bug ID: 421492 Summary: Screen brightness isn’t reset when it was dimmed because of inactivity and a paused media is put on play from KDE Connect Product: Powerdevil Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pe...@hack-libre.org Target Milestone: --- SUMMARY If the screen is dimmed after some time of inactivity (Dim screen option in Energy Saving KCM), and that a paused media is put on play with KDEConnect, then the screen stay dimmed and will get dimmer next time it stays inactive enough to trigger the dim. STEPS TO REPRODUCE 1. Install KDE Connect, both on your desktop and phone 2. In Power Management → Energy Saving, set «Dim screen» to a low value (to ease testing) 3. Launch a video in a MPRIS-enabled player (e.g. VLC) 4. Pause the media 5. Wait for the screen to get dim because of inactivity 6. Put the media on play with KDE Connect OBSERVED RESULT - Screen brightness is not reset to its normal value. - You can repeat steps 4. to 6. to get the screen dimmer and dimmer. - Moving the mouse or typing a key reset the brightness to normal, either when the screen is dim or after it went into screen energy saving mode. EXPECTED RESULT Screen brightness is reset to normal if something like playing a video is blocking energy saving, even if no key has been typed and the cursor hasn’t been moved. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 393904] kde partition manager crashed after resizing luks partition
https://bugs.kde.org/show_bug.cgi?id=393904 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Andrius Štikonas --- It's very likely to be fixed in kpmcore git master. If it still doesn't work in future releases (I guess 4.2.0) please reopen. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403980] Partition manager crashes with segmentation fault when finished moving or resizing partitions
https://bugs.kde.org/show_bug.cgi?id=403980 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Andrius Štikonas --- Tjis might be fixed in kpmcore git master although a bit hard to tell since reported didn't provide any backtrace. If it still doesn't work in future releases (I guess 4.2.0) please reopen. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 396721] Investigate possible crashes when some external commands fail
https://bugs.kde.org/show_bug.cgi?id=396721 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 398306] Window hang and crash after move and resize ntfs partition
https://bugs.kde.org/show_bug.cgi?id=398306 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Andrius Štikonas --- It's very likely to be fixed in kpmcore git master. If it still doesn't work in future releases (I guess 4.2.0) please reopen. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 414465] Partition manager crashes when analysing devices at startup
https://bugs.kde.org/show_bug.cgi?id=414465 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Andrius Štikonas --- It's very likely to be fixed in kpmcore git master. If it still doesn't work in future releases (I guess 4.2.0) please reopen. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 393236] KDE Partition Manager crash when observing or scrolling detailed report
https://bugs.kde.org/show_bug.cgi?id=393236 --- Comment #5 from Andrius Štikonas --- (In reply to Andrius Štikonas from comment #4) > *** Bug 415929 has been marked as a duplicate of this bug. *** It's very likely to be fixed in kpmcore git master. If it still doesn't work in future releases (I guess 4.2.0) please reopen. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 393236] KDE Partition Manager crash when observing or scrolling detailed report
https://bugs.kde.org/show_bug.cgi?id=393236 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 413418] KDE Partition Manager crashes when opening partition information on USB drive
https://bugs.kde.org/show_bug.cgi?id=413418 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Andrius Štikonas --- Andrius Štikonas 2020-05-14 00:20:23 UTC It's very likely to be fixed in kpmcore git master. If it still doesn't work in future releases (I guess 4.2.0) please reopen. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 417370] Crash when saving an error report
https://bugs.kde.org/show_bug.cgi?id=417370 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Andrius Štikonas --- Andrius Štikonas 2020-05-14 00:20:23 UTC It's very likely to be fixed in kpmcore git master. If it still doesn't work in future releases (I guess 4.2.0) please reopen. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 419826] KDE Partion Manager crash while resizing partition
https://bugs.kde.org/show_bug.cgi?id=419826 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Andrius Štikonas --- It's very likely to be fixed in kpmcore git master. If it still doesn't work in future releases (I guess 4.2.0) please reopen. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 421017] KDE Partition Manager crashes each time I try to open it
https://bugs.kde.org/show_bug.cgi?id=421017 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #26 from Andrius Štikonas --- (In reply to Titus Rwantare from comment #25) > (In reply to Andrius Štikonas from comment #24) > > > > Sorry, I meant uninstalling apt version and compiling 4.1.0 (not from latest > > git version but from "git checkout v4.1.0") to make sure that the fix is > > between 4.1.0 and master. As opposed to some other factors. > > I've just tried this and yes, 4.1.0 crashes and master does not. Both from > source Ok, so hopefully the speculative fix works. I'll close this and other bugs with similar backtrace as fixed. If it still crashes for somebody, then please reopen (or file a new bug). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 267277] configurable delay for autohide/show of panels
https://bugs.kde.org/show_bug.cgi?id=267277 ahangarha changed: What|Removed |Added CC||ahanga...@gmail.com --- Comment #63 from ahangarha --- As of now, on Kubuntu 20.04 which uses Kde Plasma 5.18.4, implementation of hot corners is somehow detecting pressure. They wont get activated by moving mouse to them but but putting little pressure. I think if the same thing be implemented for panels would work. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 421017] KDE Partition Manager crashes each time I try to open it
https://bugs.kde.org/show_bug.cgi?id=421017 --- Comment #25 from Titus Rwantare --- (In reply to Andrius Štikonas from comment #24) > > Sorry, I meant uninstalling apt version and compiling 4.1.0 (not from latest > git version but from "git checkout v4.1.0") to make sure that the fix is > between 4.1.0 and master. As opposed to some other factors. I've just tried this and yes, 4.1.0 crashes and master does not. Both from source -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421213] Can no longer copy/move files into a symlinked folder
https://bugs.kde.org/show_bug.cgi?id=421213 --- Comment #7 from Ben --- The bug is fixed on KDE Neon as of 2020-05-13. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421213] Can no longer copy/move files into a symlinked folder
https://bugs.kde.org/show_bug.cgi?id=421213 Nate Graham changed: What|Removed |Added CC||eleanorh...@outlook.com --- Comment #6 from Nate Graham --- *** Bug 421483 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421483] Move / copy / link tries to overwrite destination directory
https://bugs.kde.org/show_bug.cgi?id=421483 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 421213 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402017] Cannot save PDF when loaded file has been deleted
https://bugs.kde.org/show_bug.cgi?id=402017 --- Comment #14 from Nate Graham --- Temporarily wasting some memory or disk space is a far better alternative than data loss. :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421479] Right-click on file in panel yields "Could not find the program 'konsole'" on a .txt file.
https://bugs.kde.org/show_bug.cgi?id=421479 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Christoph Feck --- Indeed. *** This bug has been marked as a duplicate of bug 421374 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 421374] Service file specifiying 'Run in terminal' gives "Error code 100, Could not find the program ‘konsole’" after Plasma 5.18.5 update.
https://bugs.kde.org/show_bug.cgi?id=421374 Christoph Feck changed: What|Removed |Added CC||rcburn...@gmail.com --- Comment #10 from Christoph Feck --- *** Bug 421479 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 76082] smooth scrolling in all apps
https://bugs.kde.org/show_bug.cgi?id=76082 hoperidesal...@protonmail.ch changed: What|Removed |Added CC||hoperidesalone@protonmail.c ||h -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421469] [Regression] Slow search in the contents pane
https://bugs.kde.org/show_bug.cgi?id=421469 --- Comment #7 from Ahmad Samir --- Indeed it is slower... reverting the changes in KTreeViewSearchLine::itemMatches() restores the old behaviour. I am looking at it, so far I don't see anything obvious, other than that QRegExp::FixedString has some kind of optimisation that is much faster than what can be achieved by using QRegularExpression::escape() on the pattern (QRegExp docs say that using FixedString is equivalent to searching by using a pattern escaped by using QRegExp::escape()). I could just use plain string comparison when the "regular expression" search option is disabled; string comparison is always faster than regular expression; that doesn't fix the issue for "regular expression"... I'll test some more (but it'll have to wait until tomorrow, it's getting late and I am almost asleep...). Sorry about the trouble :) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 421491] New: [Esc] doesn't cancel Rectangular Region screenshot of a pop-up window
https://bugs.kde.org/show_bug.cgi?id=421491 Bug ID: 421491 Summary: [Esc] doesn't cancel Rectangular Region screenshot of a pop-up window Product: Spectacle Version: 19.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: skierp...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY You can get into a situation where pressing [Esc] doesn't cancel a screenshot of a Rectangular Region. It seems to happen if you activate a KDE menu. STEPS TO REPRODUCE 1. Run a KDE app like KolourPaint 2. Run Spectacle, e.g. press [PrtSc] key. 3. Set Capture Mode to Area: Rectangular Region and Delay: 5 seconds 4. click [Take a New Screenshot] 5. Open a menu in KolourPaint, e.g. Help. Or right-click on any KWin titlebar. 6. Wait... 7. When Spectacle's prompt to "Click and drag to draw a selection rectangle, or press Esc to quit" appears, press [Esc] repeatedly. OBSERVED RESULT Pressing [Esc] doesn't cancel taking a screenshot. The cursor initially isn't Spectacle's '+' cursor, it's still a KDE menu cursor. Pressing [Esc] the first time changes the cursor to Spectacle's '+' cursor, but [Esc] still doesn't dismiss. The workaround is to left-click anywhere with the mouse to begin region selection (Spectacle's prompt changes), and now you can dismiss by pressing [Esc]. If you've already taken a rectangular region screenshot, the behavior is slightly different, but [Esc] still doesn't cancel. This bug *doesn't* happen if I open a Firefox menu (e.g. press [Alt+H] for help). EXPECTED RESULT Pressing [Esc] should always dismiss as the instructions say. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.13.2 running on xcb/X Windows. ADDITIONAL INFORMATION I'm sure this is a subtle interaction with X11 pointer and event grabbing :-) , but it confused me. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421421] Pound sign in filename or directory makes Okular unable to read the file
https://bugs.kde.org/show_bug.cgi?id=421421 Jack changed: What|Removed |Added Summary|Pond in filename or |Pound sign in filename or |directory makes Okular |directory makes Okular |unable to read the file |unable to read the file CC||ostroffjh@users.sourceforge ||.net --- Comment #5 from Jack --- Edited the subject (pond -> pound sign) to reflect the problem. Perhaps an explicit "#" in the subject would be better? I'd also ask whether the problem is only for a leading # in the file name or can it be anywhere? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 421455] Lots of segmentation fault while „removing space”
https://bugs.kde.org/show_bug.cgi?id=421455 --- Comment #1 from had...@danisch.de --- I just used appimage 19.12.3 for further editing and didn't see a single crash of that kind. So I'd guess that the problem came in between 19.12.3 and 20.04.0b -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402017] Cannot save PDF when loaded file has been deleted
https://bugs.kde.org/show_bug.cgi?id=402017
David Hurka changed:
What|Removed |Added
CC||p...@kde.org
--- Comment #13 from David Hurka ---
Please look at the following. It seems like keeping the file was implemented in
2008, specifically with Firefox in mind. But it broke something else, so it was
disabled using an #undef. There is no way anymore to enable it with a compile
switch or through an environment variable. It was also only implemented for
UNIX OSes.
@Pino: Can you tell more about the problem? Can it be fixed, or do we need
another approach than creating a file handle?
If we need another approach, I vote for creating a temporary full copy of the
file, if
a) the file is smaller than a limit, set by the memory performance mode
b) (optionally) the file is from a remote location or has a path that is likely
to be temporary (e. g. /tmp/, or **/.*/)
APPENDIX A: This is a self-descriptive heading for an appendix
commit 5b5b4cabe1d8e07392641ba9cf574eda4678b12f
Author: Pino Toscano
Date: Sat Jun 7 21:52:11 2008 +
disable the open handle on the file, it breaks the file watching
CCBUG: 163363
svn path=/trunk/KDE/kdegraphics/okular/; revision=818144
diff --git a/part.cpp b/part.cpp
--- a/part.cpp
+++ b/part.cpp
@@ -182,8 +182,5 @@
#undef OKULAR_KEEP_FILE_OPEN
-#if defined(Q_OS_UNIX)
-# define OKULAR_KEEP_FILE_OPEN
-#endif
#ifdef OKULAR_KEEP_FILE_OPEN
static bool keepFileOpen()
{
commit 6531398b919e58def8c6ba4711d20ea517147189
Author: Pino Toscano
Date: Sat Jun 7 21:08:41 2008 +
Keep an open file handle on the local file currently open: this way, we can
get it back from it,
in case for some reason (read: Firefox blindly removing temporary files) it
gets "deleted".
Of course, this works (and thus it is activated) only on UNIX systems (as
the file is not deleted for real until there are open handles on it).
BUG: 163363
(If not wanted, this behavior can be disabled by export'ing
OKULAR_NO_KEEP_FILE_OPEN to 1.)
Also, in case the local file gets deleted but the real document is remote,
use its (remote) URL for the copy.
svn path=/trunk/KDE/kdegraphics/okular/; revision=818136
diff --git a/part.cpp b/part.cpp
--- a/part.cpp
+++ b/part.cpp
@@ -124,0 +182,8 @@
+#undef OKULAR_KEEP_FILE_OPEN
+#if defined(Q_OS_UNIX)
+# define OKULAR_KEEP_FILE_OPEN
+#endif
+
+#ifdef OKULAR_KEEP_FILE_OPEN
+static bool keepFileOpen()
+{
--
You are receiving this mail because:
You are watching all bug changes.
[partitionmanager] [Bug 421017] KDE Partition Manager crashes each time I try to open it
https://bugs.kde.org/show_bug.cgi?id=421017 --- Comment #24 from Andrius Štikonas --- (In reply to Titus Rwantare from comment #23) > If you mean the latest source on kde/kpmcore master, then no, it doesn't > crash with that version. However, removing partitionmanager and kpmcore, and > reinstalling through apt, which is versioned 4.1.0 also, the apt version > insta crashes. I've gone back and forth between the two. Sorry, I meant uninstalling apt version and compiling 4.1.0 (not from latest git version but from "git checkout v4.1.0") to make sure that the fix is between 4.1.0 and master. As opposed to some other factors. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421464] XPkeywords not being updated
https://bugs.kde.org/show_bug.cgi?id=421464 --- Comment #4 from Kyle Hershberger --- Not a surprise that it is some bizarre Microsoft quirk. A possible low-effort resolution is to allow the option of removing the XPkeywords tag altogether when writing out metadata. This would resolve the issue of tags set in XPkeywords perpetually reappearing after each resync. I see this as much more favorable than the current behavior. In my version of Windows 10 it is able to read keyword tags from the other EXIF locations that digiKam writes to. So even if XPkeywords was blown away, Windows would still be able to get the tags from the other EXIF fields. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412101] Wayland session does not remember the last used keyboard layout. The first keyboard layout listed in "layouts" tab of the "Keyboard" kcm is always used after login instead.
https://bugs.kde.org/show_bug.cgi?id=412101 Andrey changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |butir...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 421017] KDE Partition Manager crashes each time I try to open it
https://bugs.kde.org/show_bug.cgi?id=421017 --- Comment #23 from Titus Rwantare --- If you mean the latest source on kde/kpmcore master, then no, it doesn't crash with that version. However, removing partitionmanager and kpmcore, and reinstalling through apt, which is versioned 4.1.0 also, the apt version insta crashes. I've gone back and forth between the two. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 421490] New: Missing effects
https://bugs.kde.org/show_bug.cgi?id=421490 Bug ID: 421490 Summary: Missing effects Product: kdenlive Version: 20.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: had...@danisch.de Target Milestone: --- Both the AppImage and the ubuntu snap seem to come with a basic set of filters only. Most filters known from older versions just seem to miss. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421399] Different setting of continuous view mode per windows does not work correctly
https://bugs.kde.org/show_bug.cgi?id=421399 --- Comment #3 from David Hurka --- Others state that different settings for Continuous mode work in their Okular. How do the other view modes work for you (Single Page, Facing Pages, ...)? > However if I turn on continuous view in one window, turn it off in a second > window and come back to the first strange things happen. The view blocks > completely until I toogle continous view 2 more times, the view is displayed > continuously although the menu setting says otherwise, and so on. This sounds more serious. I never noticed such behaviour. I had similar bugs while moving the Continuous option to the View Mode submenu, but I fixed them as far as I could test. Can you make a screencast, so the problem is clear? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421489] New: Cannot to open Thermal Monitor configuration window
https://bugs.kde.org/show_bug.cgi?id=421489 Bug ID: 421489 Summary: Cannot to open Thermal Monitor configuration window Product: plasmashell Version: 5.18.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: solidus...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.3.0-51-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: I tried to modify the configuration of the plasmoid "Thermal Monitor" but when the configuration window is opened it crash the whole desktop. The crash can be reproduced every time. -- 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 0x7fa0f0ed11c0 (LWP 1828))] Thread 9 (Thread 0x7fa092f58700 (LWP 2770)): #0 0x7fa0ea226bf9 in __GI___poll (fds=0x7fa084195510, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa0e40ab5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa0e40ab6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa0eabd87cb in QEventDispatcherGlib::processEvents (this=0x7fa0841dcdd0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa0eab77d2a in QEventLoop::exec (this=this@entry=0x7fa092f57d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fa0ea988757 in QThread::exec (this=) at thread/qthread.cpp:536 #6 0x7fa0ee53ffc5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fa0ea989c2c in QThreadPrivate::start (arg=0x7fa0d400fcb0) at thread/qthread_unix.cpp:342 #8 0x7fa0e75c16db in start_thread (arg=0x7fa092f58700) at pthread_create.c:463 #9 0x7fa0ea23388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fa0915a6700 (LWP 2345)): #0 0x7fa0e75c79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55d2f0ac4730) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55d2f0ac46e0, cond=0x55d2f0ac4708) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55d2f0ac4708, mutex=0x55d2f0ac46e0) at pthread_cond_wait.c:655 #3 0x7fa0ea9901db in QWaitConditionPrivate::wait (deadline=..., this=0x55d2f0ac46e0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55d2f0a5be00, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fa0ea990359 in QWaitCondition::wait (this=0x55d2f0a5be08, mutex=0x55d2f0a5be00, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7fa0eea93233 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fa0eea93691 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fa0ea989c2c in QThreadPrivate::start (arg=0x55d2f0a5bd60) at thread/qthread_unix.cpp:342 #9 0x7fa0e75c16db in start_thread (arg=0x7fa0915a6700) at pthread_create.c:463 #10 0x7fa0ea23388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fa0942a5700 (LWP 2310)): #0 0x7fa0e75c79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55d2ef903114) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55d2ef9030c0, cond=0x55d2ef9030e8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55d2ef9030e8, mutex=0x55d2ef9030c0) at pthread_cond_wait.c:655 #3 0x7fa0ea9901db in QWaitConditionPrivate::wait (deadline=..., this=0x55d2ef9030c0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55d2f002db90, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fa0ea990359 in QWaitCondition::wait (this=0x55d2f002db98, mutex=0x55d2f002db90, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7fa0eea93233 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fa0eea93691 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fa0ea989c2c in QThreadPrivate::start (arg=0x55d2f002daf0) at thread/qthread_unix.cpp:342 #9 0x7fa0e75c16db in start_thread (arg=0x7fa0942a5700) at pthread_create.c:463 #10 0x7fa0ea23388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fa09d150700 (LWP 2306)): #0 0x7fa0ea226bf9 in __GI___poll (fds=0x7fa0980029e0, nfds=1, timeout=3438530) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa0e40ab5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa0e40ab6dc in g_main_context_iteration () from
[krita] [Bug 421485] daily builds not only for krita next
https://bugs.kde.org/show_bug.cgi?id=421485 vanyossi changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||ghe...@gmail.com Severity|normal |wishlist Ever confirmed|0 |1 --- Comment #1 from vanyossi --- Hi! AFAIK beta releases are done manually by boud, only next and plus are done with our nighites system. Im setting this as a wish for now This wish is to add Krita Plus to OSX as well. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421414] allow the use of a stylus eraser button in presentation mode
https://bugs.kde.org/show_bug.cgi?id=421414 --- Comment #1 from David Hurka --- Does it work to assign the Wacom button as a shortcut in Settings -> Configure Shortcuts? If so, it might make sense to set this shortcut by default. Setting shortcuts is a bit glitchy in Okular. The key question is whether pressing the Wacom button changes anything on the „Custom Shortcut“ button. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 421270] GHNS windows show unreadable error messages with Breeze Dark global theme
https://bugs.kde.org/show_bug.cgi?id=421270 Nate Graham changed: What|Removed |Added CC||n...@kde.org Version Fixed In||5.71 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421488] New: Plasma crashes after login
https://bugs.kde.org/show_bug.cgi?id=421488 Bug ID: 421488 Summary: Plasma crashes after login Product: plasmashell Version: 5.18.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ro...@xtra.co.nz CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.14.1 Frameworks Version: 5.70.0 Operating System: Linux 4.12.14-lp151.28.48-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: On login, KDE desktop opened with default wallpaper and icons repositioned. While restoring custom config, desktop crashed to blank (black) and unresponsive screen - Unusual behavior I noticed: Several reboots all resulted in similar behaviour, ending with Plasma crash and black screen The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f94a6f90540 (LWP 2158))] Thread 11 (Thread 0x7f943e1fd700 (LWP 2716)): #0 0x7f949d8fe87d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f94a09f90db in QWaitConditionPrivate::wait (deadline=..., this=0x5629349b0740) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x5629349baf40, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f94a09f9259 in QWaitCondition::wait (this=this@entry=0x5629349baf48, mutex=mutex@entry=0x5629349baf40, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #4 0x7f94a4b35213 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x5629349baf38) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-lp151.1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:255 #5 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x5629349baea0) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-lp151.1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:905 #6 0x7f94a4b35671 in QSGRenderThread::run (this=0x5629349baea0) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-lp151.1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1000 #7 0x7f94a09f2b2c in QThreadPrivate::start (arg=0x5629349baea0) at thread/qthread_unix.cpp:342 #8 0x7f949d8f84f9 in start_thread () from /lib64/libpthread.so.0 #9 0x7f94a02eaf2f in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7f9445563700 (LWP 2682)): #0 0x7f94a02e06db in poll () from /lib64/libc.so.6 #1 0x7f947b0e92e4 in ?? () from /usr/lib64/libnvidia-glcore.so.440.36 #2 0x7f947b1d1105 in ?? () from /usr/lib64/libnvidia-glcore.so.440.36 #3 0x7f947b0c7c4e in ?? () from /usr/lib64/libnvidia-glcore.so.440.36 #4 0x7f9481bb0f04 in ?? () from /usr/lib64/libGLX_nvidia.so.0 #5 0x7f9481b86061 in glXSwapBuffers () from /usr/lib64/libGLX_nvidia.so.0 #6 0x7f9482048242 in ?? () from /usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #7 0x7f94a1222d8f in QOpenGLContext::swapBuffers(QSurface*) () from /usr/lib64/libQt5Gui.so.5 #8 0x7f94a4b31717 in QSGRenderThread::syncAndRender (this=this@entry=0x562933c496c0, grabImage=grabImage@entry=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-lp151.1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:841 #9 0x7f94a4b3562f in QSGRenderThread::run (this=0x562933c496c0) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-lp151.1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:980 #10 0x7f94a09f2b2c in QThreadPrivate::start (arg=0x562933c496c0) at thread/qthread_unix.cpp:342 #11 0x7f949d8f84f9 in start_thread () from /lib64/libpthread.so.0 #12 0x7f94a02eaf2f in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f9450814700 (LWP 2649)): #0 0x7f94a02e06db in poll () from /lib64/libc.so.6 #1 0x7f949a2ed749 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7f949a2ed85c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f94a0c417eb in QEventDispatcherGlib::processEvents (this=0x7f9448000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f94a0be0d4a in QEventLoop::exec (this=this@entry=0x7f9450813c70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f94a09f1657 in QThread::exec (this=) at thread/qthread.cpp:536 #6 0x7f9453137c37 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #7 0x7f94a09f2b2c in QThreadPrivate::start (arg=0x562933b05390) at thread/qthread_unix.cpp:342 #8 0x7f949d8f84f9 in start_thread () from /lib64/libpthread.so.0 #9 0x7f94a02eaf2f in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f945b23e700 (LWP
[okular] [Bug 346259] [feature] zoom to selected area
https://bugs.kde.org/show_bug.cgi?id=346259 David Hurka changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from David Hurka --- This bug report was about not using the zoom tool. I don’t really understand that, but Cade must have had a reason to report this. If someone can explain why adding this feature is more important than keeping the context menu simple, please explain. Otherwise I let this be closed in 30 days. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421486] No input in nested session
https://bugs.kde.org/show_bug.cgi?id=421486 Andrey changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410582] Konsole with two tabs crashes when you press ctrl+d
https://bugs.kde.org/show_bug.cgi?id=410582 --- Comment #9 from Mykola Krachkovsky --- Application: konsole (20.04.0) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.6.11-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Closing tabs one by one with Ctrl+D. There were no "read only" tabs. Some tabs were SSH tabs (Konsole profile with ssh command). I'm not sure, maybe mouse was over some of the opened/closing tabs. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f50149fd800 (LWP 2382))] Thread 7 (Thread 0x7f5008ec6700 (LWP 2488)): #0 0x7f5015d7d795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f500adb181b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f500adb1697 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f5015d76efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f501864d3bf in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f50096c7700 (LWP 2487)): #0 0x7f5015d7d795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f500adb181b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f500adb1697 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f5015d76efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f501864d3bf in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f5009ec8700 (LWP 2486)): #0 0x7f5015d7d795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f500adb181b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f500adb1697 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f5015d76efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f501864d3bf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f500a6c9700 (LWP 2485)): #0 0x7f5015d7d795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f500adb181b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f500adb1697 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f5015d76efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f501864d3bf in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f5010968700 (LWP 2447)): #0 0x7f5018642acf in poll () from /lib64/libc.so.6 #1 0x7f50153a69de in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f50153a6aff in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f5016e64beb in QEventDispatcherGlib::processEvents (this=0x7f5004000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5016e0cb7b in QEventLoop::exec (this=this@entry=0x7f5010967d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f5016c375ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f501644c507 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f5016c38698 in QThreadPrivate::start (arg=0x7f50164ceda0) at thread/qthread_unix.cpp:342 #8 0x7f5015d76efa in start_thread () from /lib64/libpthread.so.0 #9 0x7f501864d3bf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f5012904700 (LWP 2403)): #0 0x7f5018642acf in poll () from /lib64/libc.so.6 #1 0x7f5015db2772 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f5015db343a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f5012ae9ab0 in QXcbEventQueue::run (this=0x55c7cb427cd0) at qxcbeventqueue.cpp:228 #4 0x7f5016c38698 in QThreadPrivate::start (arg=0x55c7cb427cd0) at thread/qthread_unix.cpp:342 #5 0x7f5015d76efa in start_thread () from /lib64/libpthread.so.0 #6 0x7f501864d3bf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f50149fd800 (LWP 2382)): [KCrash Handler] #6 QWidget::testAttribute (attribute=, this=) at kernel/qwidget.h:883 #7 QWidget::isEnabled (this=0x0) at kernel/qwidget.h:780 #8 QWidget::setFocus (this=0x0, reason=Qt::OtherFocusReason) at kernel/qwidget.cpp:6295 #9 0x7f5016e429de in QtPrivate::QSlotObjectBase::call (a=0x7ffea7ecc3a0, r=0x55c7cb9387c0, this=0x55c7cb97aa70) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #10 doActivate (sender=0x7f50040142c0, signal_index=15, argv=0x7ffea7ecc3a0) at kernel/qobject.cpp:3870 #11 0x7f5016e3d19f in QMetaObject::activate (sender=, m=, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7ffea7ecc3a0) at kernel/qobject.cpp:3930 #12 0x7f50184fa422 in Konsole::TabbedViewContainer::activeViewChanged (this=, _t1=) at /usr/src/debug/konsole-20.04.0-1.1.x86_64/build/src/konsoleprivate_autogen/EWIEGA46WW/moc_ViewContainer.cpp:273 #13 0x7f501846d739 in Konsole::TabbedViewContainer::currentTabChanged (index=4, this=0x7f50040142c0) at /usr/src/debug/konsole-20.04.0-1.1.x86_64/src/ViewContainer.cpp:517 #14 Konsole::TabbedViewContainer::currentTabChanged
[kwin] [Bug 421486] No input in nested session
https://bugs.kde.org/show_bug.cgi?id=421486 Andrey changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |butir...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421487] New: Bottom-Left Applet (kickoff) doesn't obey fitt's law
https://bugs.kde.org/show_bug.cgi?id=421487 Bug ID: 421487 Summary: Bottom-Left Applet (kickoff) doesn't obey fitt's law Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: zrenf...@gmail.com Target Milestone: 1.0 Can anyone confirm this? When you click the bottom of the screen, you open the kickoff widget. If you click the bottom-left corner, or the left of the screen/panel, the widget does not open. * I noticed this when I switched to Manjaro's plasma-git, but wasn't sure it might've been already fixed. * So I just tested neon-unstable-20200510-1103.iso in a VM, and noticed the same behavior when the VM was in fullscreen. * I tested kubuntu-disco-desktop-amd64.iso as well, and noticed it obeyed fitt's law as I could activate the widget by clicking the bottom-left of the screen and the left edge of the panel. I could not figure out what caused it. * https://github.com/KDE/plasma-desktop/commits/master/desktoppackage/contents/views/Panel.qml * https://github.com/KDE/plasma-desktop/commits/master/containments/panel * https://github.com/KDE/plasma-framework/commits/master/src/desktoptheme/breeze/translucent/widgets/panel-background.svg Older bugs which might be useful for figuring it out: * https://bugs.kde.org/show_bug.cgi?id=394819 * https://bugs.kde.org/show_bug.cgi?id=389215 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421486] No input in nested session
https://bugs.kde.org/show_bug.cgi?id=421486 Andrey changed: What|Removed |Added Depends on|412101 | Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=412101 [Bug 412101] Wayland session does not remember the last used keyboard layout. The first keyboard layout listed in "layouts" tab of the "Keyboard" kcm is always used after login instead. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412101] Wayland session does not remember the last used keyboard layout. The first keyboard layout listed in "layouts" tab of the "Keyboard" kcm is always used after login instead.
https://bugs.kde.org/show_bug.cgi?id=412101 Andrey changed: What|Removed |Added Blocks|421486 | Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=421486 [Bug 421486] No input in nested session -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410582] Konsole with two tabs crashes when you press ctrl+d
https://bugs.kde.org/show_bug.cgi?id=410582 Mykola Krachkovsky changed: What|Removed |Added CC||w01dn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412101] Wayland session does not remember the last used keyboard layout. The first keyboard layout listed in "layouts" tab of the "Keyboard" kcm is always used after login instead.
https://bugs.kde.org/show_bug.cgi?id=412101 Andrey changed: What|Removed |Added Blocks||421486 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=421486 [Bug 421486] No input in nested session -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421486] New: No input in nested session
https://bugs.kde.org/show_bug.cgi?id=421486 Bug ID: 421486 Summary: No input in nested session Product: kwin Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: major Priority: NOR Component: libinput Assignee: kwin-bugs-n...@kde.org Reporter: butir...@gmail.com CC: aspotas...@gmail.com, bugsefor...@gmx.com, butir...@gmail.com, kwin-bugs-n...@kde.org Depends on: 412101 Target Milestone: --- SUMMARY When run nested on Wayland, startplasma-wayland starts session with no input. This is due it tries to always use libinput by default, which is inappropriate for nested session. Seems internally it passes the option to kwin: --libinput Enable libinput support for input events processing. Note: never use in a nested session. STEPS TO REPRODUCE 1. run startplasma-wayland in Wayland session OBSERVED RESULT no input in the launched session EXPECTED RESULT session launch and reacts on input WORKAROUND pass any non-destructive option to startplasma-wayland, other than --libinput. Example: > startplasma-wayland > --exit-with-session=/usr/libexec/startplasma-waylandsession Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=412101 [Bug 412101] Wayland session does not remember the last used keyboard layout. The first keyboard layout listed in "layouts" tab of the "Keyboard" kcm is always used after login instead. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421413] toolbar in presentation mode not opening when moving unpressed stylus to the top left
https://bugs.kde.org/show_bug.cgi?id=421413 David Hurka changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from David Hurka --- I like the suggestion from Comment 3. Alternatively, there could be a menu button in the top left corner, which is always shown. That button would open the toolbar, then the toolbar covers this button. I think it would make sense to keep the toolbar open (sticky) when it is explicitly opened by clicking this button. To close it, it would have a close button in the left corner. Someone who does presentation should decide whether such a button is aesthetically acceptable. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421469] [Regression] Slow search in the contents pane
https://bugs.kde.org/show_bug.cgi?id=421469 Albert Astals Cid changed: What|Removed |Added Summary|Slow search in the contents |[Regression] Slow search in |pane|the contents pane -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421469] Slow search in the contents pane
https://bugs.kde.org/show_bug.cgi?id=421469 Albert Astals Cid changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #6 from Albert Astals Cid --- Ahmad it seems this regresion was introduced by you in commit 4a4456abd794d05074dd13aec10ffe5990b2b47d Port QRegExp to QRegularExpression in a couple of locations Some instances of QRegExp are still left: generators/mobipocket and generators/epub Before it i can search "esr" in the contents pane and it takes like 2 seconds, after it takes like 22 seconds. Could you please try to fix this? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421485] New: daily builds not only for krita next
https://bugs.kde.org/show_bug.cgi?id=421485 Bug ID: 421485 Summary: daily builds not only for krita next Product: krita Version: 4.3.0-beta1 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Unittests Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Actually, we have only krita next available as a daily build. Krita plus and Krita beta are not available. Realized this here: https://krita-artists.org/t/krita-4-3-0-beta-is-out-you-too-can-help-with-beta-testing/6611/28?u=mangatengu https://krita-artists.org/t/krita-4-3-0-beta-is-out-you-too-can-help-with-beta-testing/6611/29?u=mangatengu https://krita-artists.org/t/krita-4-3-0-beta-is-out-you-too-can-help-with-beta-testing/6611/31?u=mangatengu https://krita-artists.org/t/krita-4-3-0-beta-is-out-you-too-can-help-with-beta-testing/6611/33?u=mangatengu -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421469] Slow search in the contents pane
https://bugs.kde.org/show_bug.cgi?id=421469 Albert Astals Cid changed: What|Removed |Added Summary|Slow search |Slow search in the contents ||pane -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415199] Okular doesn't show digital signatures without visible component
https://bugs.kde.org/show_bug.cgi?id=415199 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||okular/commit/4b1d85f81bf0d ||f1fdfc86e74ad71e9cf8201092f Resolution|--- |FIXED --- Comment #6 from Albert Astals Cid --- Git commit 4b1d85f81bf0df1fdfc86e74ad71e9cf8201092f by Albert Astals Cid. Committed on 13/05/2020 at 21:21. Pushed by aacid into branch 'master'. Show signatures that don't belong to any page in the signature panel Needs poppler 0.88, we "pretend" the belong to page 0 since in Okular core there's no concept of having a signature that doesn't belong to any page M +10 -0generators/poppler/CMakeLists.txt M +3-0generators/poppler/config-okular-poppler.h.cmake M +58 -4generators/poppler/generator_pdf.cpp M +2-2generators/poppler/generator_pdf.h https://invent.kde.org/kde/okular/commit/4b1d85f81bf0df1fdfc86e74ad71e9cf8201092f -- You are receiving this mail because: You are watching all bug changes.
