[plasmashell] [Bug 457266] When using "Keep the selection and clipboard the same", selecting everything with Ctrl+A puts the entire selection in the clipboard
https://bugs.kde.org/show_bug.cgi?id=457266 --- Comment #7 from Tor <0x7...@gmail.com> --- Hi. It's been 11 months, but no changes. Does this bug cause discomfort only to me? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457266] When using "Keep the selection and clipboard the same", selecting everything with Ctrl+A puts the entire selection in the clipboard
https://bugs.kde.org/show_bug.cgi?id=457266 Tor <0x7...@gmail.com> changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457266] New: Old behavior of klipper: When only mouse-selected text gets into the history.
https://bugs.kde.org/show_bug.cgi?id=457266 Bug ID: 457266 Summary: Old behavior of klipper: When only mouse-selected text gets into the history. Product: plasmashell Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: 0x7...@gmail.com Target Milestone: 1.0 Please bring back the old clipboard behavior. When only the text selected by the mouse got into the history of the klipper. Now you can make klipper history to include not only the text selected with the mouse, but also the text selected with ctrl+a. This is quite inconvenient, especially if you often use "actions". Linux/KDE Plasma: KDE Plasma Version: 5.25.0 and newer -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457266] Old behavior of klipper: When only mouse-selected text gets into the history.
https://bugs.kde.org/show_bug.cgi?id=457266 Tor <0x7...@gmail.com> changed: What|Removed |Added Alias||klipper -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457266] Old behavior of klipper: When only mouse-selected text gets into the history.
https://bugs.kde.org/show_bug.cgi?id=457266 --- Comment #2 from Tor <0x7...@gmail.com> --- (In reply to Nate Graham from comment #1) > Can you clarify what exactly the old behavior was, and what you can't do > anymore? Is there no setting to re-enable the behavior you aren't able to > use? I don't know English so I use google translator. Sorry for the unclear writing. The old behavior is when you select text with the mouse and it appears in the klipper history. And when you select with the help ctrl+a does not get. This is a convenient behavior. It has existed for many years until recently. Example in this video: youtu.be/m1Ij6gjYTxU . The new behavior is when you select text with the mouse or with ctrl+a and it appears in the klipper's history. It's already uncomfortable. Example in this video: youtu.be/NoABLieVvBM I would like this behavior to be customizable. So that it can be enabled so that only the text selected by the mouse gets into the history of klipper. I hope that's clearer... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457266] When using "Keep the selection and clipboard the same", selecting everything with Ctrl+A puts the entire selection in the clipboard
https://bugs.kde.org/show_bug.cgi?id=457266 --- Comment #4 from Tor <0x7...@gmail.com> --- I'll try to explain why it's not correct, from my point of view, when the text selected with ctrl+a goes to the clipboard. For example, you have copied some text and you are going to paste it on some website into a field that already contains text. There is no clear button, so to quickly delete this text, you need to select it with ctrl+a and then click the delete button. This selected text immediately gets into the buffer and klipper history, and the text you need in the history becomes one position lower. And before inserting it, you must first select it in the history of the klipper. And imagine what will go down in history if you don't get into the field with the mouse and press ctrl+a on some complex site with a lot of text... In the old behavior, you didn't have to do these extra steps. It would be very nice if it could be enabled in the settings so that only the text selected with the mouse gets into the buffer history. I hope my position is clear. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457266] When using "Keep the selection and clipboard the same", selecting everything with Ctrl+A puts the entire selection in the clipboard
https://bugs.kde.org/show_bug.cgi?id=457266 Tor <0x7...@gmail.com> changed: What|Removed |Added Alias|klipper | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476872] New: [Feature Requests] Add setting the minimum and maximum speed of the touchpad cursor to the wayland session.
https://bugs.kde.org/show_bug.cgi?id=476872 Bug ID: 476872 Summary: [Feature Requests] Add setting the minimum and maximum speed of the touchpad cursor to the wayland session. Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: 0x7...@gmail.com CC: natalie_clar...@yahoo.de Target Milestone: --- Created attachment 163068 --> https://bugs.kde.org/attachment.cgi?id=163068&action=edit Screenshot in case you forgot what it looks like in x11. On my laptop in a wayland session the cursor moves slowly. In wayland the touchpad settings are limited and I can’t correctly set the minimum and maximum speed, I can only do it in X11. Because of the slow cursor, I can’t use the wayland session. Please add these settings to wayland. If it is now possible to set the minimum and maximum speed of the touchpad cursor in the configuration file, please tell me how to do this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457266] When using "Keep the selection and clipboard the same", selecting everything with Ctrl+A puts the entire selection in the clipboard
https://bugs.kde.org/show_bug.cgi?id=457266 Tor <0x7...@gmail.com> changed: What|Removed |Added Version|5.25.3 |5.27.80 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476872] [Feature Requests] Add setting the minimum and maximum speed of the touchpad cursor to the wayland session.
https://bugs.kde.org/show_bug.cgi?id=476872 --- Comment #2 from Tor <0x7...@gmail.com> --- Created attachment 163371 --> https://bugs.kde.org/attachment.cgi?id=163371&action=edit My touchpad customizer on wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476872] [Feature Requests] Add setting the minimum and maximum speed of the touchpad cursor to the wayland session.
https://bugs.kde.org/show_bug.cgi?id=476872 --- Comment #3 from Tor <0x7...@gmail.com> --- (In reply to Nate Graham from comment #1) > There's a "Pointer Speed" setting there on the Touchpad page On wayland I only have "Pointer acceleration" (screenshot in previous message). I tried to configure this and I managed to make the pointer move quickly, but when I move my finger very slowly on the touchpad, the pointer moves further than it should and faster than I would like and I can’t hit the very small buttons. If I reduce the acceleration, I start hitting the small buttons, but then the pointer speed is not fast enough. On x11 there is a different touchpad customizer and there I was able to configure it as I needed (screenshot in the first message), but on wayland I could not do this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 7952] [Feature Request] klipper: Add possibility to deactivate actions without deleting
https://bugs.kde.org/show_bug.cgi?id=7952 Tor <0x7...@gmail.com> changed: What|Removed |Added CC||0x7...@gmail.com Summary|klipper: Add possibility to |[Feature Request] klipper: |deactivate actions without |Add possibility to |deleting|deactivate actions without ||deleting Version|5.15.3 |5.27.80 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 7952] [Feature Request] klipper: Add possibility to deactivate actions without deleting
https://bugs.kde.org/show_bug.cgi?id=7952 --- Comment #5 from Tor <0x7...@gmail.com> --- I support. I would like to disable some actions but not delete them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477382] New: [Feature Request] klipper: Add the ability to change the order of added actions and commands.
https://bugs.kde.org/show_bug.cgi?id=477382 Bug ID: 477382 Summary: [Feature Request] klipper: Add the ability to change the order of added actions and commands. Classification: Plasma Product: plasmashell Version: 5.27.80 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: 0x7...@gmail.com Target Milestone: 1.0 Add the ability to change the order of added actions and commands by dragging and dropping. Now, in order to change the order of actions and commands, we have to delete them and then add them in the right order. It's quite tedious. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409995] New: Scan for Faces in video files is not yet supported
https://bugs.kde.org/show_bug.cgi?id=409995 Bug ID: 409995 Summary: Scan for Faces in video files is not yet supported Product: digikam Version: 6.1.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Faces-Detection Assignee: digikam-bugs-n...@kde.org Reporter: tor...@live.com Target Milestone: --- SUMMARY I hope you soon will add the support for "Scan for Faces" in video files. If so, do you have an ETA on that? Thanks. STEPS TO REPRODUCE 1. Import video files 2. Scan for Faces 3. No faces are detected (It works with picture files, so it is turned on) OBSERVED RESULT Does not find faces in video files EXPECTED RESULT Some faces in "People" should show up for me to name. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION Hope you will add this as I hope to get away from Google Photos solution next coming months/years... -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 479119] No terminal emulator in Konqueror
https://bugs.kde.org/show_bug.cgi?id=479119 --- Comment #4 from Willi Tor --- Created attachment 165960 --> https://bugs.kde.org/attachment.cgi?id=165960&action=edit It seems the same bug like Bug 480878. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 480878] show terminal opens pane bellow file window in koqueror, but it's a blank pane.
https://bugs.kde.org/show_bug.cgi?id=480878 Willi Tor changed: What|Removed |Added CC||willi...@web.de --- Comment #1 from Willi Tor --- It seems the same bug like Bug 479119. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 479119] No terminal emulator in Konqueror
https://bugs.kde.org/show_bug.cgi?id=479119 --- Comment #5 from Willi Tor --- Created attachment 165964 --> https://bugs.kde.org/attachment.cgi?id=165964&action=edit Konqueror 22.12.3, Raspberry Pi OS Bookworm with JWM The same bug on the Raspberry Pi (5B), just looks a little different. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 480878] show terminal opens pane bellow file window in koqueror, but it's a blank pane.
https://bugs.kde.org/show_bug.cgi?id=480878 --- Comment #3 from Willi Tor --- Please, see Bug 479119. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 480878] show terminal opens pane bellow file window in koqueror, but it's a blank pane.
https://bugs.kde.org/show_bug.cgi?id=480878 --- Comment #6 from Willi Tor --- Thanks for the tip. Unfortunately, it doesn't work, neither on Debian nor on the Raspberry Pi. It's not empty windows that open, just something completely different. It seems like a completely pointless link. It may work on SuSE. It's only Debian, but I like it. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 479119] New: No terminal emulator in Konqueror
https://bugs.kde.org/show_bug.cgi?id=479119 Bug ID: 479119 Summary: No terminal emulator in Konqueror Classification: Applications Product: konqueror Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: shellcmdplugin Assignee: konq-b...@kde.org Reporter: willi...@web.de Target Milestone: --- SUMMARY *** The menu function "Settings => Show terminal emulator" (deutsch: "Einstellungen => Terminal-Emulator anzeigen") does not work correctly in konqueror. *** STEPS TO REPRODUCE OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 12.4 bookworm (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION 1. This bug also affects the Raspberry Pi OS "Bookworm". 2. I read that in other distributions the error should no longer occur. 3. Sorry, this is a translation with Google. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 479119] No terminal emulator in Konqueror
https://bugs.kde.org/show_bug.cgi?id=479119 --- Comment #3 from Willi Tor --- Created attachment 164539 --> https://bugs.kde.org/attachment.cgi?id=164539&action=edit Bookworm Desktop -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 453661] Shortcuts are not working across multiple keyboard layouts (US and CZ for me)
https://bugs.kde.org/show_bug.cgi?id=453661 Tor Arne changed: What|Removed |Added CC||tora...@gmail.com --- Comment #31 from Tor Arne --- Andrey. Your patch has not been "attacked". There is technical disagreement on the validity of the patch. I suggest you approach this in a more constructive manner. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 375101] Crashed while moving file
https://bugs.kde.org/show_bug.cgi?id=375101 --- Comment #4 from Tor Bellino --- (In reply to Julian Schraner from comment #3) > Can you still reproduce this crash with Dolphin 17.12.3? I'm using Dolphin 17.04.3 but no, I can no longer reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 375101] Crashed while moving file
https://bugs.kde.org/show_bug.cgi?id=375101 Tor Bellino changed: What|Removed |Added CC||ar...@bellino.com.ar --- Comment #2 from Tor Bellino --- I recently had the same issue. Additionally, when dragging the file, the list of subdirectories popped up (the one that appears when clicking in a subdirectory name, to select another). But of course I didn't click anything, as I was holding the button down while dragging the file. Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe317db0d40 (LWP 3758))] Thread 4 (Thread 0x7fe2f2fcd700 (LWP 3762)): #0 0x7fe30de24029 in g_mutex_lock (mutex=mutex@entry=0x7fe2ec000990) at ././glib/gthread-posix.c:1336 #1 0x7fe30ee5 in g_main_context_prepare (context=context@entry=0x7fe2ec000990, priority=priority@entry=0x7fe2f2fccbc0) at ././glib/gmain.c:3504 #2 0x7fe30ddde8fb in g_main_context_iterate (context=context@entry=0x7fe2ec000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909 #3 0x7fe30dddeaec in g_main_context_iteration (context=0x7fe2ec000990, may_block=1) at ././glib/gmain.c:3990 #4 0x7fe3124944ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe31243c0fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe312261d43 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe312266c68 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe30e96e6ca in start_thread (arg=0x7fe2f2fcd700) at pthread_create.c:333 #9 0x7fe3177bf0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7fe2fbfff700 (LWP 3761)): #0 0x7fe3177aec8d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe30de22c80 in read (__nbytes=16, __buf=0x7fe2fbffeab0, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #2 0x7fe30de22c80 in g_wakeup_acknowledge (wakeup=0x7fe2fc0015b0) at ././glib/gwakeup.c:210 #3 0x7fe30ddde485 in g_main_context_check (context=context@entry=0x7fe2f4000990, max_priority=2147483647, fds=fds@entry=0x7fe2f4008310, n_fds=n_fds@entry=1) at ././glib/gmain.c:3707 #4 0x7fe30ddde974 in g_main_context_iterate (context=context@entry=0x7fe2f4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3926 #5 0x7fe30dddeaec in g_main_context_iteration (context=0x7fe2f4000990, may_block=1) at ././glib/gmain.c:3990 #6 0x7fe3124944ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe31243c0fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe312261d43 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fe317e9c575 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7fe312266c68 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fe30e96e6ca in start_thread (arg=0x7fe2fbfff700) at pthread_create.c:333 #12 0x7fe3177bf0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7fe301d33700 (LWP 3760)): #0 0x7fe3177b30bd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe30bd03c62 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fe30bd058d7 in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fe30428a299 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fe312266c68 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe30e96e6ca in start_thread (arg=0x7fe301d33700) at pthread_create.c:333 #6 0x7fe3177bf0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7fe317db0d40 (LWP 3758)): [KCrash Handler] #6 0x7fe3122c7010 in QHashData::free_helper(void (*)(QHashData::Node*)) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe3173f8034 in KFileItemModel::insertItems(QList&) () at /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #8 0x7fe3173f84df in KFileItemModel::dispatchPendingItemsToInsert() () at /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #9 0x7fe3173f8ec2 in KFileItemModel::slotCompleted() () at /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #10 0x7fe31246bbec in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fe3158a62f5 in KCoreDirLister::completed(QUrl const&) () at /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #12 0x7fe3158b9369 in () at /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #13 0x7fe3158b984c in () at /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #14 0x7fe31246bb49 in QMetaObject::activate(QObject*, int,
[plasmashell] [Bug 494838] Icons-Only Task Manager not showing icons
https://bugs.kde.org/show_bug.cgi?id=494838 Tor Røttum changed: What|Removed |Added CC||t...@rottum.me --- Comment #1 from Tor Røttum --- (In reply to Juan Chan from comment #0) > Created attachment 174868 [details] > bug-fullscreen.jpg – Screenshot of the desktop after reboot, showing the > Icons-Only Task Manager without any icons displayed. bug-hover.jpg – > Screenshot showing the behavior when hovering over the Ico > > SUMMARY > Icons-Only Task Manager does not display icons after boot. Entering Edit > Mode temporarily resolves the issue. > > STEPS TO REPRODUCE > 1. reboot or start the system > > OBSERVED RESULT > Icons are not displayed in the Icons-Only Task Manager after reboot (see > attached bug-fullscreen.jpg). > Hovering over the task manager widget shows the corresponding app name, but > no icons (see attached bug-hover.jpg). > Entering Edit Mode makes the icons reappear, dismissing the bug (see > attached normal.jpg). > EXPECTED RESULT > Icons should appear correctly in the Icons-Only Task Manager after boot (as > shown in normal.jpg). > > SOFTWARE/OS VERSIONS > Operating System: Arch Linux > KDE Plasma Version: 6.2.0 > KDE Frameworks Version: 6.7.0 > Qt Version: 6.8.0 > Kernel Version: 6.11.3-zen1-1-zen (64-bit) > > ADDITIONAL INFORMATION > This issue has been present prior to the current KDE Plasma version (6.2.0), > but the exact starting version is unknown. I had the same problem with task manager and system tray and after upgrading to KDE Plasma 6.2.x. Entering edit mode only helped temporarily. Today I noticed that the plasma renderer was set to software. After changing it to Open GL the icons re-appeared again. I tried using the Vulkan renderer as well, but it went into a crash and restart loop -- You are receiving this mail because: You are watching all bug changes.
