[kdenlive] [Bug 425443] in motion tab only freeze option is showing , speed option is missing
https://bugs.kde.org/show_bug.cgi?id=425443 --- Comment #1 from Masum --- you just have to make some space for the selected clips to expand while slowing it down, then you can decrease the speed below 100%. and right click--> change speed is the option for changing speed. it is not a bug -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 425443] in motion tab only freeze option is showing , speed option is missing
https://bugs.kde.org/show_bug.cgi?id=425443 Masum changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425444] New: Bottom panel missed every time after reboot with external monitor connected
https://bugs.kde.org/show_bug.cgi?id=425444 Bug ID: 425444 Summary: Bottom panel missed every time after reboot with external monitor connected Product: plasmashell Version: 5.19.4 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: zainulla.zhum...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.19.4) Qt Version: 5.14.2 Frameworks Version: 5.72.0 Operating System: Linux 5.4.0-42-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - Unusual behavior I noticed: Bottom panel missed every time after reboot. Bug happens only when external monitor connected to my laptop. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 Plasma::Applet::immutability (this=0x0) at ./src/plasma/applet.cpp:491 #5 0x7fa4c304233d in Plasma::Applet::destroy (this=0x0) at ./src/plasma/applet.cpp:303 #6 0x7fa4b929ccd8 in SystemTrayContainer::~SystemTrayContainer (this=0x557eb058e410, __in_chrg=) at /usr/include/c++/9/bits/atomic_base.h:413 #7 0x7fa4b929cd3d in SystemTrayContainer::~SystemTrayContainer (this=0x557eb058e410, __in_chrg=) at ./applets/systemtray/container/systemtraycontainer.cpp:34 #8 0x7fa4c10bdd2e in QObjectPrivate::deleteChildren (this=0x557eb0534e40) at kernel/qobject.cpp:2123 #9 0x7fa4c10c7696 in QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:1107 #10 0x7fa4c3046f6d in Plasma::Containment::~Containment (this=0x557eb0534d50, __in_chrg=) at ./src/plasma/containment.cpp:84 #11 0x7fa4c10c1043 in QObject::event (this=0x557eb0534d50, e=0x557eb064fc80) at kernel/qobject.cpp:1326 #12 0x7fa4c1c00cc3 in QApplicationPrivate::notify_helper (this=this@entry=0x557eb025fd20, receiver=receiver@entry=0x557eb0534d50, e=e@entry=0x557eb064fc80) at kernel/qapplication.cpp:3685 #13 0x7fa4c1c09f40 in QApplication::notify (this=0x7ffeec0bbeb0, receiver=0x557eb0534d50, e=0x557eb064fc80) at kernel/qapplication.cpp:3431 #14 0x7fa4c109378a in QCoreApplication::notifyInternal2 (receiver=0x557eb0534d50, event=0x557eb064fc80) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153 #15 0x7fa4c1095f74 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x557eb0254f90) at kernel/qcoreapplication.cpp:1815 #16 0x7fa4c10ecb87 in postEventSourceDispatch (s=0x557eb02cb550) at kernel/qeventdispatcher_glib.cpp:277 #17 0x7fa4bf485fbd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7fa4bf486240 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7fa4bf4862e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7fa4c10ec1e2 in QEventDispatcherGlib::processEvents (this=0x557eb02c6e90, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7fa4c109224b in QEventLoop::exec (this=this@entry=0x7ffeec0bbd60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #22 0x7fa4c109a296 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #23 0x557eaff51c09 in main (argc=, argv=) at ./shell/main.cpp:224 [Inferior 1 (process 1638) detached] The reporter indicates this bug may be a duplicate of or related to bug 420245. Possible duplicates by query: bug 420245, bug 417603, bug 415304, bug 411221, bug 377301. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 425443] New: in motion tab only freeze option is showing , speed option is missing
https://bugs.kde.org/show_bug.cgi?id=425443 Bug ID: 425443 Summary: in motion tab only freeze option is showing , speed option is missing Product: kdenlive Version: 20.04.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: kajerrebookofficial2...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. effect 2. motion 3. speed is missing 4. i tried right clicking and change speed but minimum speed is limited to 100% only OBSERVED RESULT cant add slow mo to video EXPECTED RESULT should be possible to slow mo the video SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: N/A ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 425337] The sql query and custom DateTime format are not saved in Import dialog
https://bugs.kde.org/show_bug.cgi?id=425337 Alexander Semke changed: What|Removed |Added Version Fixed In||2.8 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/educ ||ation/labplot/commit/2df970 ||3d23557e7f2d7e966987c89ffcf ||b916ee1 --- Comment #2 from Alexander Semke --- Git commit 2df9703d23557e7f2d7e966987c89ffcfb916ee1 by Alexander Semke. Committed on 17/08/2020 at 06:25. Pushed by asemke into branch 'master'. Save and show the last used SQL query for every connection in the database import dialow. FIXED-IN: 2.8 M +12 -1src/kdefrontend/datasources/ImportSQLDatabaseWidget.cpp https://invent.kde.org/education/labplot/commit/2df9703d23557e7f2d7e966987c89ffcfb916ee1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420223] "Speed" is missing from motion effects
https://bugs.kde.org/show_bug.cgi?id=420223 Masum changed: What|Removed |Added CC||kajerrebookofficial2019@gma ||il.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425439] App crashes during the maintenance process with face recognition. stacktrace and log included
https://bugs.kde.org/show_bug.cgi?id=425439 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Platform|Other |Microsoft Windows Severity|normal |crash OS|Other |Microsoft Windows --- Comment #1 from Maik Qualmann --- The log from the process monitor is unfortunately not helpful. Activate the debug output by setting an environment variable in the Windows environment editor. Variable: QT_LOGGING_RULES Value: digikam.*=true Download DebugView from Microsoft and run it. Try to reproduce the crash in digiKam and post the output from DebugView. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425096] Crash Unsupported JPEG process: SOF type 0xc8
https://bugs.kde.org/show_bug.cgi?id=425096 --- Comment #6 from Proffecanded --- I can't reproduce bug with commit 536c505d96df7434c30a2a94e03e57759f686186. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425442] New: Crashes Frequently when Opening .kra file
https://bugs.kde.org/show_bug.cgi?id=425442 Bug ID: 425442 Summary: Crashes Frequently when Opening .kra file Product: krita Version: 4.3.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: forums7...@me.com Target Milestone: --- Created attachment 130926 --> https://bugs.kde.org/attachment.cgi?id=130926&action=edit Problem Report File SUMMARY When double clicking on .kra file, Krita 4.3.0 crashes repeatedly and consistently STEPS TO REPRODUCE 1. Double Click .kra file using 4.3.0 Krita 2. Finally when Krita opens, close the app without opening any file and it crashes 3. below you will find the error from the OS OBSERVED RESULT Process: krita [1799] Path: /private/var/folders/*/krita.app/Contents/MacOS/krita Identifier:org.krita Version: 4.3.0 (???) Code Type: X86-64 (Native) Parent Process:??? [1] Responsible: krita [1799] User ID: 501 Date/Time: 2020-08-16 23:43:39.911 -0500 OS Version:Mac OS X 10.13.6 (17G14019) Report Version:12 Anonymous UUID:3BD0965A-86E6-7287-EB46-AAE7CE00265E Sleep/Wake UUID: 276DB2BA-A467-4D6A-B8E0-87176B361CE0 Time Awake Since Boot: 19000 seconds Time Since Wake: 13000 seconds System Integrity Protection: enabled Notes: Translocated Process Crashed Thread:0 Dispatch queue: com.apple.main-thread Exception Type:EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x Exception Note:EXC_CORPSE_NOTIFY Termination Signal:Segmentation fault: 11 Termination Reason:Namespace SIGNAL, Code 0xb Terminating Process: exc handler [0] -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 422021] K3b cant erase CD-RW
https://bugs.kde.org/show_bug.cgi?id=422021 falling_failing_fall...@protonmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #5 from falling_failing_fall...@protonmail.com --- I mark the bug report as resolved - not a bug cause I wasn't able to reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424913] plasma crashes
https://bugs.kde.org/show_bug.cgi?id=424913 --- 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.
[k3b] [Bug 422021] K3b cant erase CD-RW
https://bugs.kde.org/show_bug.cgi?id=422021 --- 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.
[frameworks-kio] [Bug 422539] Dolphin crashes when trying to open an image
https://bugs.kde.org/show_bug.cgi?id=422539 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.
[krita] [Bug 412846] Expose ways to select/deselect nodes in the Layer docker
https://bugs.kde.org/show_bug.cgi?id=412846 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 422002] Split editor and tags view
https://bugs.kde.org/show_bug.cgi?id=422002 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #20 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.
[kdenlive] [Bug 424093] Kdenlive crashes when importing multiple clips or switching to a different resolution profile
https://bugs.kde.org/show_bug.cgi?id=424093 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[kdenlive] [Bug 423185] File deletion in project not being tracked
https://bugs.kde.org/show_bug.cgi?id=423185 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[neon] [Bug 425411] Cancelling KDE Neon 20.04 Focal Fossa upgrade results in broken Flatpak and System Information
https://bugs.kde.org/show_bug.cgi?id=425411 --- Comment #6 from Ben --- In Kubuntu, I also tried using the EFI boot partition but it still requires me to enter commands into grub when I restart the computer. ~$ sudo update-grub2 [sudo] password for user: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.4.0-42-generic Found initrd image: /boot/initrd.img-5.4.0-42-generic Found Windows Boot Manager on /dev/nvme0n1p2@/efi/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for UEFI Firmware Settings done ~$ sudo grub-install /dev/nvme0n1p2 Installing for i386-pc platform. grub-install: warning: File system `fat' doesn't support embedding. grub-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. grub-install: error: will not proceed with blocklists. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 425441] New: Feature Request: add option 'rename' to the menu of spectacle
https://bugs.kde.org/show_bug.cgi?id=425441 Bug ID: 425441 Summary: Feature Request: add option 'rename' to the menu of spectacle Product: Spectacle Version: 20.04.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: safeerpas...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 130925 --> https://bugs.kde.org/attachment.cgi?id=130925&action=edit notification_menu_after_taking_screenshot after taking a screenshot, a notification pops up with a menu inside that has many options. the menu is marked in red in the attachments I want to add the option 'rename' to the menu that renames the taken screenshot. Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421875] Keyboard layouts section shows wrong flag for afghanistan
https://bugs.kde.org/show_bug.cgi?id=421875 Safeer Pasha changed: What|Removed |Added CC||safeerpas...@gmail.com --- Comment #1 from Safeer Pasha --- (In reply to Noor from comment #0) there must be a place where KDE got the flag from. KDE can not have done this in my opinion by its self. we need to find the place KDE got the flag's info from. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425440] New: Number of elements in folders on JFS partitions not shown
https://bugs.kde.org/show_bug.cgi?id=425440 Bug ID: 425440 Summary: Number of elements in folders on JFS partitions not shown Product: dolphin Version: 20.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: details mode Assignee: dolphin-bugs-n...@kde.org Reporter: bjarne...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Set Dolphin to view in Details Mode 2. Open a folder containing subfolders 3. See if Dolphin lists the number of elements in each subfolder OBSERVED RESULT No number of elements listed EXPECTED RESULT The number of elements in folders (containing elements) should be shown SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel version: 5.8.1-1-arch1-1 OS-type: 64-bit Processor: 8xIntel Core i7-4770K CPU @ 3.50GHz Memory: 15.6 GiB RAM Graphics Processor: AMD PITCAIRN ADDITIONAL INFORMATION In "Details Mode", Dolphin does not show the number of elements in folders or subfolders _on certain harddrives/partitions_. I.e.: It does show the number of elements in folders on my EFI, Root and Home partitions, as well as on another harddrive, which are all (except the EFI-partition) formatted ext4. It fails to show the number of elements in folders on my other three drives, which are formatted JFS. The file sizes seem to be shown correctly on all drives. Seems Dolphin has 'forgotten' to support JFS in the latest version. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 --- Comment #4 from John Apple II --- (In reply to bernie from comment #3) > Is there any hack / workaround we could put in place if GTK takes their time > to add zwp_primary_selection? > > This is quite a showstopper for moving to Wayland, at least for me. Same here - I use this feature so much in my day-to-day work that I cannot switch to Wayland from X, yet. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425439] New: App crashes during the maintenance process with face recognition. stacktrace and log included
https://bugs.kde.org/show_bug.cgi?id=425439 Bug ID: 425439 Summary: App crashes during the maintenance process with face recognition. stacktrace and log included Product: digikam Version: 7.0.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Faces-Maintenance Assignee: digikam-bugs-n...@kde.org Reporter: andsh...@gmail.com Target Milestone: --- Created attachment 130924 --> https://bugs.kde.org/attachment.cgi?id=130924&action=edit log and stacktrace from processmonitor SUMMARY App crashes during the maintenance process with face recognition STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 423579] Application: Kontact (kontact), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=423579 --- Comment #1 from john4deidre2...@xtra.co.nz --- Created attachment 130923 --> https://bugs.kde.org/attachment.cgi?id=130923&action=edit New crash information added by DrKonqi kontact (5.14.3 (20.04.3)) using Qt 5.15.0 - What I was doing when the application crashed: was just trying to start kontact. when starting it crashed -- Backtrace (Reduced): #4 std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/10/bits/atomic_base.h:420 #5 QAtomicOps::loadRelaxed (_q_value=) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #7 QtPrivate::RefCount::isShared (this=) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:101 #8 QList::append (this=0x100, t=@0x7ffedff514b0: 0x55b7a2cd7c50) at ../../include/QtCore/../../src/corelib/tools/qlist.h:622 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 423579] Application: Kontact (kontact), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=423579 john4deidre2...@xtra.co.nz changed: What|Removed |Added CC||john4deidre2...@xtra.co.nz -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 425073] Can't configure software sources through Muon package manager
https://bugs.kde.org/show_bug.cgi?id=425073 Carlo Vanini changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Latest Commit||8e18f65b8b7a285ff6edaa53911 ||26afb2c09773b --- Comment #2 from Carlo Vanini --- software-properties-kde has indeed been replaced by software-properties-qt. It has been fixed in Muon after 5.8.0, but a new version is not released yet. https://invent.kde.org/system/muon/-/commit/8e18f65b8b7a285ff6edaa5391126afb2c09773b As a workaround you can start software-properties directly from the applications menu or by running kdesudo software-properties-qt -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424488] Log out then login causes plasmashell to crashes
https://bugs.kde.org/show_bug.cgi?id=424488 Roger changed: What|Removed |Added CC||roger...@gmail.com --- Comment #1 from Roger --- Created attachment 130922 --> https://bugs.kde.org/attachment.cgi?id=130922&action=edit crash report plasmashell crashes on login after a logout. It not happens on the first login after a reboot, only when logout and login again. Versions: plasmashell 5.19.4 Qt 5.15.0 KDE Frameworks 5.73.0 openSUSE Tumbleweed 20200814 Linux 5.8.0-1-default x86_64 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425438] New: About the new UI of Annotations tools.
https://bugs.kde.org/show_bug.cgi?id=425438 Bug ID: 425438 Summary: About the new UI of Annotations tools. Product: okular Version: 1.11.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: felip...@gmail.com Target Milestone: --- Hi. Today I used the new version (1.11.0) and I got shocked by the great UI changes at the annotations interface. English is not my first language, sorry if my text sounds rude. I love to make my annotations using the old sidebar with "quick annotation tools" that I predefined. Has the sidebar annotation tools gone forever? With the new UI: - I need to navigate in a drop-down menu "Quick Annotations" using two clicks instead of one to access a predefined tool. (I tried to define a shortcut to this menu but it doesn't work.) - The actual selected "predefined annotation tool" is less visible and I can't peek at the "old" sidebar to see the shortcut by the "always present" ordered icons. - If I use the new "Annotation bar" to try to perceive what predefined tool I'm using ... I have to look at a gazillion of icons to infer (type, color, etc.) ... and this bar steals vertical space. At my use case, I don't need a bar to configure each new annotation with new colors and etc. I just need a practical way to access predefined tools (if possible, without stealing vertical space) ... with a good UI to alternate between them and see what is selected. I don't know if my "use case" is an esoteric one ... but I'm feeling a bit disappointed. Am I missing something about how to use the new UI correctly? -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 353101] List of breakpoints in Breakpoints view is not synchronizes with set breakpoints in editor (Icon border)
https://bugs.kde.org/show_bug.cgi?id=353101 --- Comment #2 from Piotr Mierzwinski --- Seems to be fixed by Bug 424431 -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 353101] List of breakpoints in Breakpoints view is not synchronizes with set breakpoints in editor (Icon border)
https://bugs.kde.org/show_bug.cgi?id=353101 Piotr Mierzwinski changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 386578] Request: Allow annotation mode to "stick" for better use with a stylus
https://bugs.kde.org/show_bug.cgi?id=386578 Felipe changed: What|Removed |Added Version|unspecified |1.11.0 CC||felip...@gmail.com Platform|unspecified |Flatpak -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367905] Breakpoint marker disappears from bar in editor after stopping application in debug mode
https://bugs.kde.org/show_bug.cgi?id=367905 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Piotr Mierzwinski --- Seems to be fixed by Bug 424431 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 363237] Breakpoints (Breakpoints View) are not updated after removing/adding couple lines of code
https://bugs.kde.org/show_bug.cgi?id=363237 Piotr Mierzwinski changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Piotr Mierzwinski --- Fixed in Bug 424431 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 424431] Loaded breakpoints don't update properly if code is edited
https://bugs.kde.org/show_bug.cgi?id=424431 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #3 from Piotr Mierzwinski --- I think this is duplication this bug #363237 "Breakpoints (Breakpoints View) are not updated after removing/adding couple lines of code" -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418038] search bar is cut in compact/mobile view
https://bugs.kde.org/show_bug.cgi?id=418038 --- Comment #5 from Stefano Milani --- search bar in discover remains cut in comapt/mobile view with kde plasma 5.19.4, kde frameworks 5.73.0 (QT 5.15.0) archlinux STEPS TO REPRODUCE 1. open discover 2. resize window as much as possible 3. click left hamburger menu 4. click search 5. observe search bar is "cut" (see screenshot) Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.7.12-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Celeron® CPU N3450 @ 1.10GHz Memory: 5.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 500 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418038] search bar is cut in compact/mobile view
https://bugs.kde.org/show_bug.cgi?id=418038 --- Comment #4 from Stefano Milani --- Created attachment 130921 --> https://bugs.kde.org/attachment.cgi?id=130921&action=edit search bar remains cut in compat/mobile view -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424402] When entering a check/account statement number using the numeric keypad, insert '.' instead of ','
https://bugs.kde.org/show_bug.cgi?id=424402 juantxor...@gmail.com changed: What|Removed |Added CC||juantxor...@gmail.com --- Comment #3 from juantxor...@gmail.com --- I can confirm this bug. I'm using fedora, it appeared after updating to version 5.1.0-1, previous working version was 5.0.8-2 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 425437] New: Collage view
https://bugs.kde.org/show_bug.cgi?id=425437 Bug ID: 425437 Summary: Collage view Product: gwenview Version: 20.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: poperi...@tuta.io Target Milestone: --- This would allow you to open up multiple images simultaneously and view them side by side in a grid. This would be useful if your trying to use multiple images as a reference and don't want to switch through multiple gwenview windows. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 425437] Collage view
https://bugs.kde.org/show_bug.cgi?id=425437 poperi...@tuta.io changed: What|Removed |Added CC||poperi...@tuta.io -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file
https://bugs.kde.org/show_bug.cgi?id=411093 --- Comment #34 from Ahmad Samir --- @Aldo: this looks like a downstream packaging issue, I suggest you file a bug report in your distro's bug tracker. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 424431] Loaded breakpoints don't update properly if code is edited
https://bugs.kde.org/show_bug.cgi?id=424431 Igor Kushnir changed: What|Removed |Added Version Fixed In||5.6.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/commit/ff7a0e ||a60d4d7546b09dafdfedfc0db18 ||b59e722 --- Comment #2 from Igor Kushnir --- Git commit ff7a0ea60d4d7546b09dafdfedfc0db18b59e722 by Igor Kushnir, on behalf of Axel Kellermann. Committed on 16/08/2020 at 19:41. Pushed by igorkushnir into branch '5.6'. Associate loaded breakpoints with a moving cursor Loaded breakpoints don't trigger markChanged(), which is normally responsible for getting a moving cursor for breakpoints. Instead the moving cursor for loaded breakpoints is now added in textDocumentCreated(). Logic for adding moving cursors is also moved into seperate function, as the same code snippet was used multiple times. FIXED-IN: 5.6.0 M +32 -23 kdevplatform/debugger/breakpoint/breakpointmodel.cpp M +3-1kdevplatform/debugger/breakpoint/breakpointmodel.h https://invent.kde.org/kdevelop/kdevelop/commit/ff7a0ea60d4d7546b09dafdfedfc0db18b59e722 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 424430] Loaded breakpoints don't show up in UI
https://bugs.kde.org/show_bug.cgi?id=424430 Igor Kushnir changed: What|Removed |Added Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/commit/cc3f98 ||b89f30a2501fdb1d848714b9b3e ||edd0c85 Version Fixed In||5.6.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Igor Kushnir --- Git commit cc3f98b89f30a2501fdb1d848714b9b3eedd0c85 by Igor Kushnir, on behalf of Axel Kellermann. Committed on 16/08/2020 at 19:41. Pushed by igorkushnir into branch '5.6'. Make sure DebugController is initialized before UI is shown DebugController is responsible for loading breakpoints, and if they are not loaded when the UI is made visible, they don't show up. FIXED-IN: 5.6.0 M +5-1kdevplatform/shell/core.cpp https://invent.kde.org/kdevelop/kdevelop/commit/cc3f98b89f30a2501fdb1d848714b9b3eedd0c85 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 425401] Audio playback during preview stopped working
https://bugs.kde.org/show_bug.cgi?id=425401 --- Comment #2 from mrpuzzle1...@gmail.com --- Going backwards on the revision fixed the problem. Since I have you, any idea why when I switched from 17 to 20 the preview video is now very choppy? Thanks. On Sun, Aug 16, 2020 at 6:48 AM emohr wrote: > https://bugs.kde.org/show_bug.cgi?id=425401 > > emohr changed: > >What|Removed |Added > > > CC||fritzib...@gmx.net > Flags||timeline_corruption+ > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from emohr --- > Please try with the current Kdenlive AppImage version 20.04.1b to see if > there > are any packaging issues https://files.kde.org/kdenlive/release/ > > If the problem/issue doesn't occur when using the AppImage, then it's your > configuration or packaging. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file
https://bugs.kde.org/show_bug.cgi?id=411093 --- Comment #33 from Aldo Latino --- After many tests (either on my work computer and in some VirtualBox machines) I discovered that this problem happens to me when I install the package mysql-server which removes some Akonadi related packages[1]. In other words, if I don't install mysql-server, Akonadi works fine. After the installation of mysql-server, Akonadi stops working. In this situation, since I need a LAMP server on my machine, I have to perform some actions in order to make Akonadi work with mysql-server. [1] MySQL is correctly installed but these are some of the lines printed during the installation process: Preconfiguring packages ... dpkg: mariadb-client-core-10.3: dependency problems, but removing anyway as you requested: akonadi-backend-mysql depends on mariadb-client-core-10.3 | virtual-mysql-client-core; however: Package mariadb-client-core-10.3 is to be removed. Package virtual-mysql-client-core is not installed. Package mariadb-client-core-10.3 which provides virtual-mysql-client-core is to be removed. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425435] Kdenlive (Snap) is unable to open filedialogs. (Apparmor suspected)
https://bugs.kde.org/show_bug.cgi?id=425435 --- Comment #1 from uli_r...@gmx.de --- Created attachment 130919 --> https://bugs.kde.org/attachment.cgi?id=130919&action=edit Messages from dmesg -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425435] New: Kdenlive (Snap) is unable to open filedialogs. (Apparmor suspected)
https://bugs.kde.org/show_bug.cgi?id=425435 Bug ID: 425435 Summary: Kdenlive (Snap) is unable to open filedialogs. (Apparmor suspected) Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snaps Assignee: neon-b...@kde.org Reporter: uli_r...@gmx.de CC: neon-b...@kde.org Target Milestone: --- Created attachment 130918 --> https://bugs.kde.org/attachment.cgi?id=130918&action=edit What was printed on the console SUMMARY Kdenlive is unable to open filedialogs. Most likely due to misconfigured apparmor. STEPS TO REPRODUCE 1. Open Terminal 2. Type "kdenlive" 3. In the toolbar click "Öffnen..." (Open) OBSERVED RESULT 1. There is nor file dialog 2. Error messages on stdout/stderr 3. Error messages in dmesg EXPECTED RESULT 1. File Dialog 2. No error messages on stdout or stderr 3. No error messages in kernel ringbuffer SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu Budgie 20.04 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 425434] New: Applications using Qt CSD have no outer shadow
https://bugs.kde.org/show_bug.cgi?id=425434 Bug ID: 425434 Summary: Applications using Qt CSD have no outer shadow Product: Breeze Version: 5.19.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: unassigned-b...@kde.org Reporter: pub...@redaril.me Target Milestone: --- SUMMARY Telegram uses this library: https://github.com/lirios/materialdecoration Telegram is a Qt-based application. Recently, it included materialdecoration on Linux which enabled CSD. This makes Telegram have no outer shadow exactly like Plasma used to do with GTK3 applications not so long ago. STEPS TO REPRODUCE 1. Install a recent version of Telegram (say 2.2) 2. Run it OBSERVED RESULT The application window has no shadow. EXPECTED RESULT The application window should have an outer shadow like all the other Qt-based applications. SOFTWARE/OS VERSIONS Operating System: Solus 4.1 KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 Kernel Version: 5.6.19-158.current OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon R9 200 Series ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425423] White screen at beginning of Presentation should be avoided
https://bugs.kde.org/show_bug.cgi?id=425423 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.1.0 Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/fd1ebec ||a27752101d0cf987160f065c79c ||22075b Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Maik Qualmann --- Git commit fd1ebeca27752101d0cf987160f065c79c22075b by Maik Qualmann. Committed on 16/08/2020 at 19:26. Pushed by mqualmann into branch 'master'. start with a black first texture FIXED-IN: 7.1.0 M +1-1NEWS M +8-0 core/dplugins/generic/view/presentation/opengl/presentationgl.cpp https://invent.kde.org/graphics/digikam/commit/fd1ebeca27752101d0cf987160f065c79c22075b -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 425433] New: HTML Preview is slow (for some messages)
https://bugs.kde.org/show_bug.cgi?id=425433 Bug ID: 425433 Summary: HTML Preview is slow (for some messages) Product: kmail2 Version: 5.15.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: trilader+kdeb...@gmail.com Target Milestone: --- SUMMARY For some messages rendering the HTML preview is slow. After selecting the message it takes about 2.2 seconds (measured with stopwatch) before the message content is visible. If switching between messages the old message content is displayed while the message list already shows the new message as selected. For some messages it's faster but still takes around a second. The same message in Thunderbird load with no noticeable delay. STEPS TO REPRODUCE 1. Open/switch to a message from a sender which is set to display as HTML by default 2. Wait.. 3. See that it took some time to display it. OBSERVED RESULT Rendering the HTML message is slow. EXPECTED RESULT It should be fast :-) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION I can supply messages to test with. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425432] Year separated with dot in title over icons when month selected
https://bugs.kde.org/show_bug.cgi?id=425432 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Here with the native Linux version and the Windows version, the year is displayed correctly. The problem with the AppImage is known, the Qt locale function does not work correctly. It affects all functions that are influenced by the system's locale settings. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425054] KWin crash when repeatedly triggering present windows hot corner
https://bugs.kde.org/show_bug.cgi?id=425054 Roger changed: What|Removed |Added CC||roger...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Jakub changed: What|Removed |Added CC|jakubmadej.pl+...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425432] New: Year separated with dot in title over icons when month selected
https://bugs.kde.org/show_bug.cgi?id=425432 Bug ID: 425432 Summary: Year separated with dot in title over icons when month selected Product: digikam Version: 7.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Searches-Dates Assignee: digikam-bugs-n...@kde.org Reporter: johannes.lists+bugs.kde@tannenhof-imshausen.de Target Milestone: --- SUMMARY When using Calendar view and a month is selected, the title over the icons is shown e.g. as August 2.020 STEPS TO REPRODUCE 1. Select 2020 -> August 2020 in Dates. 2. Look at the title (over the icons on the right) OBSERVED RESULT August 2.020 EXPECTED RESULT August 2020 SOFTWARE/OS VERSIONS digikam 7.0.0. Appimage Linux/KDE Plasma: Ubuntu 18.04.5 LTS KDE Frameworks Version: KDE Frameworks 5.70.0 Qt Version: Qt 5.14.2 (built against 5.14.2) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #216 from Ruth Ivimey-Cook --- On 16/08/2020 13:16, Christoph Cullmann wrote: > https://bugs.kde.org/show_bug.cgi?id=373232 > > --- Comment #215 from Christoph Cullmann --- > I still think is: > > https://bugreports.qt.io/browse/QTBUG-78963 > > See for more details > > https://cullmann.io/posts/kde-qt-highdpi-scaling/ > > I traced down the paint stuff, too, and think we paint the "right" rectangles > but that is then afterwards not properly "clipped". > > If you can provide them with some way to reproduce, that would be nice, I did > fail. > Well it's not too hard to demonstrate that at least some of the QRects are correct with my debug patches. I find vim is quite good at reliably producing and erasing extraneous lines, so I'll give it a go. Ruth -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 180268] Search by specific metadata as Artist, Byline, Location, City, Country, etc... [patch]
https://bugs.kde.org/show_bug.cgi?id=180268 --- Comment #25 from Johannes --- I don't know why it wasn't closed already… -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425431] New: Doesn't execute python scripts, opens them instead.
https://bugs.kde.org/show_bug.cgi?id=425431 Bug ID: 425431 Summary: Doesn't execute python scripts, opens them instead. Product: dolphin Version: 20.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: o...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Executable *.py files open instead of executing in the latest Dolphin version. *.sh files still work as intended STEPS TO REPRODUCE 1. Double-click on an executable .py file 2. Get dialog with options: Open, Execute, Cancel 3. Open and Execute do the same thing - open the file in editor SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux lom 5.8.1-arch1-1 x86_64 GNU/Linux (available in About System) KDE Plasma Version: Version 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425421] [Wayland] Log out causes the CPU utilization to jump to 100%
https://bugs.kde.org/show_bug.cgi?id=425421 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- similar to bug 421676 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425425] No shortcuts available for Slideshow entries anymore in Configure Keyboard Shortcuts…
https://bugs.kde.org/show_bug.cgi?id=425425 --- Comment #1 from caulier.gil...@gmail.com --- All default Slideshow keyboard short-cuts work as expected here under Linux with native DK 7.0.0 and Plasma desktop. In shortcuts config dialog, only the top level Slideshow action is referenced, and this action do... nothing. It's only a container for the 3 sub actions available in the main View menu. Sound like the sub-actions are not referenced to the ActionCollection instance from the application. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 425430] New: Backspace key does not remove a digit
https://bugs.kde.org/show_bug.cgi?id=425430 Bug ID: 425430 Summary: Backspace key does not remove a digit Product: kdeplasma-addons Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calculator Assignee: plasma-b...@kde.org Reporter: n...@sonic.net Target Milestone: --- When making a typo while entering digits into the calculator plasma widget, it's impossible to correct the mistake by pressing the [Backspace] key. For example: You mean to enter "360 / 12 =", but instead type "369" at first. One would assume you could hit [Backspace] and "0" to correct it, and then proceed with "/ 12 =". However, you must clear the entire calculation (e.g., with [Esc]) and start over. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425425] No shortcuts available for Slideshow entries anymore in Configure Keyboard Shortcuts…
https://bugs.kde.org/show_bug.cgi?id=425425 caulier.gil...@gmail.com changed: What|Removed |Added Component|Usability-Keyboard |Plugin-Generic-SlideShow CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 180268] Search by specific metadata as Artist, Byline, Location, City, Country, etc... [patch]
https://bugs.kde.org/show_bug.cgi?id=180268 --- Comment #24 from caulier.gil...@gmail.com --- So the Q is : what's missing to close this file now ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 305534] Annotations don't show all non-ASCII letters
https://bugs.kde.org/show_bug.cgi?id=305534 boingo-00 changed: What|Removed |Added CC|boingo...@ya.ru | -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425408] Vertical blue line appears at the left side of window when scrolling in Konsole 20.08.
https://bugs.kde.org/show_bug.cgi?id=425408 --- Comment #6 from tcanabr...@kde.org --- sorry, this is indeed the new feature, I added a second vertical line at char position and I misunderstood. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 305534] Annotations don't show all non-ASCII letters
https://bugs.kde.org/show_bug.cgi?id=305534 Yuri Chornoivan changed: What|Removed |Added CC||yousifjka...@yahoo.com --- Comment #30 from Yuri Chornoivan --- *** Bug 425429 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425429] "Typewriter" & "Inline Note" annotations do not support Arabic characters !
https://bugs.kde.org/show_bug.cgi?id=425429 Yuri Chornoivan changed: What|Removed |Added CC||yurc...@ukr.net Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Yuri Chornoivan --- *** This bug has been marked as a duplicate of bug 305534 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425148] okular import of old embedded annotations does not import the original create/modify time stamp
https://bugs.kde.org/show_bug.cgi?id=425148 jpror...@gmail.com changed: What|Removed |Added Platform|Ubuntu Packages |Compiled Sources Component|general |PDF backend -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425429] New: "Typewriter" & "Inline Note" annotations do not support Arabic characters !
https://bugs.kde.org/show_bug.cgi?id=425429 Bug ID: 425429 Summary: "Typewriter" & "Inline Note" annotations do not support Arabic characters ! Product: okular Version: 1.11.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: yousifjka...@yahoo.com Target Milestone: --- SUMMARY When I use Arabic characters with "Typewriter" & "Inline Note" annotations, they will not appearing at all. EXPECTED RESULT These 2 types of annotations should support Arabic characters SOFTWARE/OS VERSIONS Linux: Fedora 32 X64 bit Cinnamon edition. KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Other type of annotations, namely "Pop-up Note" already support Arabic characters okay. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425148] okular import of old embedded annotations does not import the original create/modify time stamp
https://bugs.kde.org/show_bug.cgi?id=425148 --- Comment #10 from jpror...@gmail.com --- I'm starting to wonder if this might actually be an issue in Poppler but need some guidance in understanding the logic that Okular follows in the conversion process. As noted, Okular is correctly restoring the original create/mod dates of the annotation from its original storage. It prompts the user to save the PDF to a file to preserve the annotations with the PDF. At this point I have traced lots of code, but it seems to come down to Okular handing of the Save operation to the PDFGenerator::save() method. There is a QHashIteration across the annotations that compares unique ids between okular annotations and poppler annotations, but doesn't seem to have any other affect. The actual save of the current Okular document that needs migration appears to be handed off to the Poppler::PDFConverter(). It seems like this utility takes the current Okular PDF document and saves it out to a temporary file. It's during this operation that the original annotation create/modify times are lost. The temp file is then copied to the saveAs target, but by that time the times are already set to the current date. Is this understanding correct? If so, is there any way to control the conversion of the annotations within Okular to avoid this issue. I thought the PopplerAnnotationProxy might be able to, but it doesn't seem to be invoked by Poppler during the PDFConverter. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425424] allow seting max resolution for export to filesystems
https://bugs.kde.org/show_bug.cgi?id=425424 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- The local file export tool has the option of reducing the size of the images, just like web export tools. It is also possible to remove the metadata. Maybe you don't have the release candidate for digiKam-7.0.0? Maik -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425428] New: Can not add custom stamp from a file if the file located within folder or path named (or part of it's name) with NON-Latin characters
https://bugs.kde.org/show_bug.cgi?id=425428 Bug ID: 425428 Summary: Can not add custom stamp from a file if the file located within folder or path named (or part of it's name) with NON-Latin characters Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: yousifjka...@yahoo.com Target Milestone: --- SUMMARY As the title saying. ADDITIONAL INFORMATION I'm refereed from GitHub of flatpak version on FlatHub to post this issue here after discovering the real nature of this issue - see: https://github.com/flathub/org.kde.okular/issues/67 See specially the following: https://github.com/flathub/org.kde.okular/issues/67#issuecomment-673992274 Best. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425408] Vertical blue line appears at the left side of window when scrolling in Konsole 20.08.
https://bugs.kde.org/show_bug.cgi?id=425408 --- Comment #5 from Benjamin Smith --- Actually, tcanabr...@kde.org, the behavior is correct. The blue line goes from top to bottom only if I scroll the whole length of the window. Otherwise, the blue line appears next to newly visible lines of text. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425427] New: System Freeze.
https://bugs.kde.org/show_bug.cgi?id=425427 Bug ID: 425427 Summary: System Freeze. Product: plasmashell Version: 5.19.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: wblwed8...@aenmail.net CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY System Removing Plasma processes from RAM when the ram is full, or system processes moving from RAM to swap, these freezes the entire system. STEPS TO REPRODUCE 1. Run large programs like Android studio, or other bunch of programs. 2. Once the System RAM is full. 3. System automatically removes even the system processes, and it freezes the system. OBSERVED RESULT System freeze, Required a force restart ( by power button or unplug system from power source ). EXPECTED RESULT Prevent to remove the system processes from RAM even ram is full, and don't allow to move system processes from RAM to swap, the system processes should be keep in RAM, even there is no space to run other user apps. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 398175] Falkon should detect network connections with additional login needed
https://bugs.kde.org/show_bug.cgi?id=398175
--- Comment #2 from Tobias Leupold ---
So, it's one year and I'm still facing the same problem ;-)
Aüpparently, Falkon doesn't follow the redirect ("Location" header) announced
by the router before the login. This is what "LC_ALL=C wget --server-response
google.de" outputs:
tobias@think ~ $ LC_ALL=C wget --server-response google.de
--2020-08-16 19:26:30-- http://google.de/
Resolving google.de... 172.217.23.35, 2a00:1450:4016:804::2003
Connecting to google.de|172.217.23.35|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 302 Hotspot login required
Cache-Control: no-cache
Content-Length: 135
Content-Type: text/html
Date: Sun, 16 Aug 2020 10:53:15 GMT
Expires: 0
Location: http://172.18.0.133/login?dst=http%3A%2F%2Fgoogle.de%2F
Location: http://172.18.0.133/login?dst=http%3A%2F%2Fgoogle.de%2F
[following]
--2020-08-16 19:26:30--
http://172.18.0.133/login?dst=http%3A%2F%2Fgoogle.de%2F
Connecting to 172.18.0.133:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Cache-Control: no-cache
Connection: Keep-Alive
Content-Length: 4540
Content-Type: text/html
Date: Sun, 16 Aug 2020 10:53:15 GMT
Expires: 0
Length: 4540 (4.4K) [text/html]
Saving to: 'index.html'
It answers with "HTTP/1.1 302 Hotspot login required", followed by the
hotspot's login page "Location: http://172.18.0.133/login";.
Shouldn't Falkon follow this redirect? Like wget, Firefox and Chrome do?
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 425168] Cannot type accented characters via dead-keys
https://bugs.kde.org/show_bug.cgi?id=425168 --- Comment #5 from Milan Knížek --- But with Flatpak, there seems to be some troubles with integration - I use quite often "Open with..." submenu to run actions outside of digiKam on the image or whole folder (based on standard .desktop files and mime db). With Flatpak, this seems to be quite complicated (it does not work to simply allow host:ro filesystem access). -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 416650] Crashes when imaging a sequence.
https://bugs.kde.org/show_bug.cgi?id=416650 mountainai...@outlook.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #11 from mountainai...@outlook.com --- More recent builds of KStars have been crashing less frequently, and 3.4.3 seems quite a bit more stable. I haven't experienced this crash during an imaging sequence for many months. Closing ticket. Hy, I apologize for not seeing your earlier comments -- had I been paying more attention, I would have responded. Thank you both! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425056] KWin crashes/dies after resume from sleep
https://bugs.kde.org/show_bug.cgi?id=425056 --- Comment #6 from Joe --- Played around a bit more - I can get to the compositing in system settings (even with the blackout, if you can guess the right place on the left nav it still works on click). Re-enabling the compositor doesn't work at all (it also has detection disabled). If I change to XRender and apply it does work again, but, either OpenGL 2 or 3.1 and it just crashes/breaks. Have to reboot to get it working again. I also noticed even after re-enabling auto detection, on reboot the compositor is still off, I have to manually go into system settings and reset everything to make it work again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394119] Panel should not stop auto-hiding even when a window wants attention
https://bugs.kde.org/show_bug.cgi?id=394119 Holger changed: What|Removed |Added CC||andydecle...@gmail.com --- Comment #29 from Holger --- *** Bug 416999 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416999] Task Manager never stops demanding attention in some cases when a window state is _NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 Holger changed: What|Removed |Added CC||private_l...@yahoo.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #23 from Holger --- *** This bug has been marked as a duplicate of bug 394119 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425096] Crash Unsupported JPEG process: SOF type 0xc8
https://bugs.kde.org/show_bug.cgi?id=425096 --- Comment #5 from Proffecanded --- I set the environment variable and found the image causing crash. It's a 70MB panoramic photo. I tried to scan again the whole folder but digikam doesn't crash anymore. I've compiled latest version including your commits. I'll launch faces scan as soon as possible. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 425426] New: Konversation could notify a user when a nickname is truncated because of server rules
https://bugs.kde.org/show_bug.cgi?id=425426 Bug ID: 425426 Summary: Konversation could notify a user when a nickname is truncated because of server rules Product: konversation Version: 1.7.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: alexander.shchadi...@gmail.com Target Milestone: --- Created attachment 130916 --> https://bugs.kde.org/attachment.cgi?id=130916&action=edit A screenshot showing a drop-down list with nicknames that will be truncated Konversation could launch a simple popup warning when a nickname is truncated because of NICKLEN server parameter. This will be especially helpful for an IRC novices like me - I think looking at a screenshot will be enough to understand why I felt a bit lost when clicking different nickname variants in a drop-down list. Those are default nicknames derived from a Linux username, the server had NICKLEN=16. This is not a bug, but a suggestion. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425425] New: No shortcuts available for Slideshow entries anymore in Configure Keyboard Shortcuts…
https://bugs.kde.org/show_bug.cgi?id=425425 Bug ID: 425425 Summary: No shortcuts available for Slideshow entries anymore in Configure Keyboard Shortcuts… Product: digikam Version: 7.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability-Keyboard Assignee: digikam-bugs-n...@kde.org Reporter: johannes.lists+bugs.kde@tannenhof-imshausen.de Target Milestone: --- SUMMARY In digikam 7.0.0 in the dialog Configure Keyboard Shortcuts… there are no shortcuts available for Slideshow -> All, Selection and With All Sub-Albums. Also, the shortcut I assigned to Slideshow-> Selection long ago, which was still working in digikam 6.4.0 Appimage, is not working anymore on 7.0.0. Instead, the new standard shortcut Alt+F9 is working and shown in the menu. STEPS TO REPRODUCE 1. Use the digikam 7.0.0 Appimage 2. Open Settings -> Configure Keyboard Shortcuts… 3. Search for Slideshow OBSERVED RESULT There is only one entry Slideshow with no shortcut assigned to it. EXPECTED RESULT There are 3 entries in Settings -> Configure Keyboard Shortcuts…: Slideshow -> All Slideshow -> Selection Slideshow -> With All Sub-Albums SOFTWARE/OS VERSIONS digikam 7.0.0. Appimage Linux/KDE Plasma: Ubuntu 18.04.5 LTS KDE Frameworks Version: KDE Frameworks 5.70.0 Qt Version: Qt 5.14.2 (built against 5.14.2) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Add an option auto-hide intelligently if and only if some window is near it, or maximized. As seen on Cinnamon Panels.
https://bugs.kde.org/show_bug.cgi?id=349785 Holger changed: What|Removed |Added CC||private_l...@yahoo.com --- Comment #18 from Holger --- Just curious: 1. How will "intelligent autohide" interact with maximized but inactive windows? Currently I have 4 desktops each running a maximized Firefox and I only see my desktop once a week on reboot - so I guess, the "intelligent" part is totally lost on me unless the panel is allowed to cover inactive windows. 2. What about the side-by-side layout via Meta+Cursor Left/Right? Should this in addition show the "intelligent autohide" panel or shall it be covered? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 180268] Search by specific metadata as Artist, Byline, Location, City, Country, etc... [patch]
https://bugs.kde.org/show_bug.cgi?id=180268 --- Comment #23 from Johannes --- Searching for Creator still works in 7.0.0. (tested with Appimage 64bit on Ubuntu 18.04.5). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425352] Cursor is huge and jagged
https://bugs.kde.org/show_bug.cgi?id=425352 Johannes changed: What|Removed |Added CC||johannes.lists+bugs.kde.org ||@tannenhof-imshausen.de --- Comment #2 from Johannes --- Same here on Ubuntu 18.04.5 64bit with Appimage. Before I used digikam 6.4.0 with Appimage, there the normal system cursor was used. But now a ugly black cursor is shown inside digikam. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425319] Mounting an ISO with multiple partitions always mounts the wrong partition
https://bugs.kde.org/show_bug.cgi?id=425319 Kwon-Young Choi changed: What|Removed |Added Status|NEEDSINFO |RESOLVED URL||https://github.com/storaged ||-project/udisks/issues/725 Resolution|WAITINGFORINFO |UPSTREAM --- Comment #5 from Kwon-Young Choi --- Thanks for your additional input. For now, I'll mark this bug as resolved and add a link to the udisks issue. If you happen to open a new issue, let me know so that I can update the url. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424311] Severe Rendering Issues on Latest Nvidia Driver (450.57) (Arch)
https://bugs.kde.org/show_bug.cgi?id=424311 --- Comment #23 from Fabian Vogt --- (In reply to Fonic from comment #22) > Same issues here: > - system settings displays black box to the left > - screen locker only shows mouse cursor, have to unlock manually from console > > Patch '0001-Use-glXGetProcAddress-for-context-creation.patch' does not seem > to have any effect. > > Gentoo Linux (amd64, stable) > Linux Kernel 5.4.48 > NVIDIA drivers 450.57 > KWin 5.18.5 > Qt 5.14.2 Yeah, the patch will only fix kwin_x11 crashes. For kscreenlocker, https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/9 might've worked around this as well. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425423] White screen at beginning of Presentation should be avoided
https://bugs.kde.org/show_bug.cgi?id=425423 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|general |Plugin-Generic-Presentation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376859] Tag Shortcut Key Combination Conflict Dialog Always Appears
https://bugs.kde.org/show_bug.cgi?id=376859 caulier.gil...@gmail.com changed: What|Removed |Added Version|6.1.0 |7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424434] Application doesn't know its window's updated position while dragging
https://bugs.kde.org/show_bug.cgi?id=424434 --- Comment #8 from php4...@gmail.com --- > But so far it seems we would just be creating > overhead and achieving nothing tangible. If making it *possible* for an application to know its window's position while moving creates overhead even for those applications who never take advantage of it, then something in the system is very badly designed and that needs to be fixed. If only those applications who actually "query" for their window position will suffer from the overhead (and if the overhead is not bigger than it needs to be), then it's up to the applications whether or not to use the feature. > If it breaks something that isn't an abuse of windows to begin with we can > change it What is "an abuse"?? You can't just say some use case is an abuse because you hadn't thought of it or because it's useless to you. Any use of windows (or of any other feature) should be assumed to be legitimate unless you can prove the contrary. You should approach it the other way around: if it breaks something (and it does, I have already provided an example, no matter how stupid), then it needs to be changed, *unless* you can prove that every single use case that gets broken, is an abuse. Which means: 1. you need to be able to give a very, very precise definition of what you mean by "an abuse" in the first place 2. you need to be able to argue not only that the particular case that is known to get broken is an abuse, but that ANY possible use case that you may have not thought of yet, is also an "abuse". And yes, that's basically impossible, which is precisely my point: the mere fact that I can make up a use case, no matter how stupid, basically means it has to be supported. There's (almost) no such thing as an "abuse", or a not-good-enough (i.e. "better than Browser Pong") use case. Consider this other use case: A window with a background that acts like... well, a literal window. That is, a window with a "virtual background" image that is anchored to the screen, and has the size of the entire screen, regardless of the position and size of the window. You move the window, you move the "hole" that lets you see the background. Why would I want that? For the sake of it. Because it's aesthetically pleasing (to someone). That's a good enough reason as far as the OS needs to be concerned. Now, regarding the supposed overhead. EVERY other operating system and every other major desktop environment except for Plasma has this. As far as I know, they don't become sluggish or less responsive when you move windows around. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424860] No EXIF display on CR3 images
https://bugs.kde.org/show_bug.cgi?id=424860 --- Comment #4 from caulier.gil...@gmail.com --- I created today a libraw entry in github about to implement an Exif getter : https://github.com/LibRaw/LibRaw/issues/323 Wait and see. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425424] New: allow seting max resolution for export to filesystems
https://bugs.kde.org/show_bug.cgi?id=425424 Bug ID: 425424 Summary: allow seting max resolution for export to filesystems Product: digikam Version: 7.0.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Plugin-WebService-FileTransfer Assignee: digikam-bugs-n...@kde.org Reporter: achim_schae...@gmx.de Target Milestone: --- SUMMARY While other export plugins like dropbox allow to reduce the resolution ogf the picture, this is currently not possible for the export to file systems. Enabele the same feature for filesystem/remote exports. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425359] First face tag moves intermittently
https://bugs.kde.org/show_bug.cgi?id=425359 --- Comment #7 from Tom Cunningham --- Just imported a file with metadata NOT used and the problem persists. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425359] First face tag moves intermittently
https://bugs.kde.org/show_bug.cgi?id=425359 --- Comment #6 from Tom Cunningham --- So is the problem something that happens at import time? I unchecked the box "Use file metadata (makes connection slower)" and the behavior persists. What is the upshot of using/not using file metadata? -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 416035] Bluetooth does not connect automatically to a paired device
https://bugs.kde.org/show_bug.cgi?id=416035 phg changed: What|Removed |Added CC||jhgru...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file
https://bugs.kde.org/show_bug.cgi?id=411093 --- Comment #32 from Erasmo Caponio --- This bug seems solved in kde neon based on Ubuntu 20.04 (at least on my upgraded system). Removing and reinstalling apparmor and snapd may help (Anyway I still have snapd removed) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425420] Lots of options blank when starting Krita in tablet mode
https://bugs.kde.org/show_bug.cgi?id=425420 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- That has nothing to do with tablet mode; it's more likely that the krita4.xmlgui file in %APPDATA%\krita has become corrupted. If you remove that file, everything should be back to normal. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 424218] Akonadi fails to start for KOrganizer in Linux Mint 20
https://bugs.kde.org/show_bug.cgi?id=424218 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #5 from Ahmad Samir --- If you have AppArmor enabled, then this looks like a duplicate of bug 411093. (which has a link to a launchpad bug report with a supposed fix). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file
https://bugs.kde.org/show_bug.cgi?id=411093 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #31 from Ahmad Samir --- So basically this means, misconfigured AppArmor rules prevent mysqld-akonadi from reading ~/.local/share/akonadi/mysql.conf, which causes this bug? if so, then it's a downstream issue in Kubuntu, and has to be fixed there, IIUC. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425396] New folder named ":foo" always created in home dir
https://bugs.kde.org/show_bug.cgi?id=425396 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- I can confirm this behavior. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 383442] vimode clipboard copy/paste line is not correct
https://bugs.kde.org/show_bug.cgi?id=383442 Jan Paul Batrina changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #2 from Jan Paul Batrina --- Upon further inspection, this seems to work for the normal delete line and yank line (dd, yy), but the behavior you describe appears when using (numbered) registers. -- You are receiving this mail because: You are watching all bug changes.
