[kwin] [Bug 407652] Maximizing a window by dragging turns mouse cursor into a black square
https://bugs.kde.org/show_bug.cgi?id=407652 --- Comment #6 from HM --- (In reply to Matej Mrenica from comment #4) > @HM do you still have this issue? I tried to reproduce this now(recently) and was unable to do so in both my Arch setup and a KDE Neon VM. Looks like its gone. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407652] Maximizing a window by dragging turns mouse cursor into a black square
https://bugs.kde.org/show_bug.cgi?id=407652 --- Comment #2 from HM --- Created attachment 130567 --> https://bugs.kde.org/attachment.cgi?id=130567=edit Video of the bug in action. Recorded with a camera. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407652] Maximizing a window by dragging turns mouse cursor into a black square
https://bugs.kde.org/show_bug.cgi?id=407652 HM changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- CC||mcmailf...@protonmail.com --- Comment #1 from HM --- Bug is still present. This is only present while using wayland. This bug must have been mistakenly marked resolved as this is not present while using an X session. I've found that this issue also appears when dragging the window to a screen edge with a panel as well. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 Kernel Version: 5.7.11-arch1-1 OS Type: 64-bit Processors: 12 × AMD Ryzen 5 2600 Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: Radeon RX Vega 56 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419698] Mouse-wheel action over desktop stopped working
https://bugs.kde.org/show_bug.cgi?id=419698 HM changed: What|Removed |Added Version|5.18.4 |5.19.4 CC||mcmailf...@protonmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from HM --- I can confirm this issue. Mouse scroll wheel does not work on the desktop for the default action of switching desktops or other actions I've tried. I have had this issue on all of my Plasma setups since some Plasma update not too long ago. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416540] Plasma crashes when deleting sticky note from desktop
https://bugs.kde.org/show_bug.cgi?id=416540 HM changed: What|Removed |Added CC||mcmailf...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 361725] Yakuake task appears in the task manager some times, when opening Yakuake with hotkey
https://bugs.kde.org/show_bug.cgi?id=361725 HM changed: What|Removed |Added Platform|openSUSE RPMs |Archlinux Packages Version|3.0.2 |unspecified CC||mcmailf...@protonmail.com --- Comment #10 from HM --- This issue seems to have come up again after a while. I don't remember noticing this issue going some while back. Operating System: Arch Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Kernel Version: 5.5.2-arch1-1 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416230] KDE Partition Manager crash when opening removable device
https://bugs.kde.org/show_bug.cgi?id=416230 --- Comment #2 from HM --- So the USB drive I had this crash happen with was kind of problematic. It was a promo USB that you receive at expos. (Might have been read only. I was able to format it someway with cfdisk I think. Weird drive.) It doesnt crash with my other USB drives. But I suppose the app shouldn't have crashed even so. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416230] New: KDE Partition Manager crash when opening removable device
https://bugs.kde.org/show_bug.cgi?id=416230 Bug ID: 416230 Summary: KDE Partition Manager crash when opening removable device Product: partitionmanager Version: 4.0.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mcmailf...@protonmail.com Target Milestone: --- Application: partitionmanager (4.0.0) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 5.4.11-arch1-1 x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Trying to open removable device /dev/sde in KDE Partition Manager The crash can be reproduced every time. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Floating point exception Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f63ed0f2840 (LWP 3111))] Thread 16 (Thread 0x7f63a7063700 (LWP 3126)): #0 0x7f63f0ce742c in read () at /usr/lib/libc.so.6 #1 0x7f63ef75f9f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f63ef7ad9e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f63ef7af0c8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f63ef7b00c3 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #5 0x7f63a791ebc8 in () at /usr/lib/libgio-2.0.so.0 #6 0x7f63ef78bbb1 in () at /usr/lib/libglib-2.0.so.0 #7 0x7f63f012e4cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f63f0cf62d3 in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f63a7864700 (LWP 3125)): #0 0x7f63ef75f479 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f63ef7ad147 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #2 0x7f63ef7af1b1 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f63ef7af1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f63ef7af242 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f63ef78bbb1 in () at /usr/lib/libglib-2.0.so.0 #6 0x7f63f012e4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f63f0cf62d3 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f63d49b5700 (LWP 3124)): #0 0x7f63f0ce742c in read () at /usr/lib/libc.so.6 #1 0x7f63ef75f9f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f63ef7ad9e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f63ef7af0c8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f63ef7af1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f63f12a6cdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f63f124d39c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f63f2af53b9 in () at /usr/lib/libkpmcore.so.8 #8 0x7f63f1073fd6 in () at /usr/lib/libQt5Core.so.5 #9 0x7f63f012e4cf in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f63f0cf62d3 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f63d51b6700 (LWP 3123)): #0 0x7f63f0134c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f63e3275aec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f63e32756e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f63f012e4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f63f0cf62d3 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f63d59b7700 (LWP 3122)): #0 0x7f63f0134c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f63e3275aec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f63e32756e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f63f012e4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f63f0cf62d3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f63d61b8700 (LWP 3121)): #0 0x7f63f0134c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f63e3275aec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f63e32756e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f63f012e4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f63f0cf62d3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f63d69b9700 (LWP 3120)): #0 0x7f63f0134c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f63e3275aec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f63e32756e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f63f012e4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f63f0cf62d3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f63d71ba700 (LWP 3119)): #0 0x7f63f0134c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f63e3275aec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f63e32756e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f63f012e4cf in start_thread () at
[systemsettings] [Bug 414184] Systemsettings5 crash after trying to open Window Appearance menu
https://bugs.kde.org/show_bug.cgi?id=414184 HM changed: What|Removed |Added CC||mcmailf...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413420] KRunner does not capture first few characters typed in desktop the first time on new session
https://bugs.kde.org/show_bug.cgi?id=413420 --- Comment #4 from HM --- I heard from someone that this behavior is because KRunner is now started on demand. I checked and did find that KRunner is now not started at boot. It only gets started once you type in something at the desktop and depending on how fast you type, misses the first few inputs. Isn't this bad design, taking away from the functionality and productivity that KRunner gives letting you just do stuff from the get go. Current buggy behavior can be worked around by starting KRunner at boot - create an autostart entry with command 'krunner -d' (-d for starting in background) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413420] New: KRunner does not capture first few characters typed in desktop the first time on new session
https://bugs.kde.org/show_bug.cgi?id=413420 Bug ID: 413420 Summary: KRunner does not capture first few characters typed in desktop the first time on new session Product: krunner Version: 5.17.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: mcmailf...@protonmail.com Target Milestone: --- SUMMARY KRunner fails to capture first few characters typed in to the desktop for the first time on a new session. Depending on how fast its typed, KRunner misses the first 1 or 2 characters. This buggy behavior has been present on Wayland for a while now. After updating to Plasma 5.17 this behavior is now experienced on X session. STEPS TO REPRODUCE 1. Login to new Plasma session 2. Type in command/program name/etc OBSERVED RESULT Krunner does not get the first one or two characters of the input. For example if you type in "reboot" KRunner gets only "eboot" EXPECTED RESULT The whole input starting with the first character at the desktop should be captured as input by KRunner. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 5.3.7-arch1-1-ARCH x86_64 KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408617] Dolphin doesn't remember icon size per folder with 'remember properties for each folder' configuration
https://bugs.kde.org/show_bug.cgi?id=408617 --- Comment #5 from HM --- (In reply to Méven Car from comment #3) > I suspect this bug already existed prior to the mentioned change. > > It also depends on the preview setting to have the same value in both > folders. You're probably right. I'm not sure about the relation to the mentioned change, it was a hunch as I remember the behaviour changing after the update that brought along that change. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408617] Dolphin doesn't remember icon size per folder with 'remember properties for each folder' configuration
https://bugs.kde.org/show_bug.cgi?id=408617 HM changed: What|Removed |Added Summary|Dolphin doesn't remember|Dolphin doesn't remember |icon size with 'remember|icon size per folder with |properties for each folder' |'remember properties for |configuration |each folder' configuration -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408617] Dolphin doesn't remember icon size with 'remember properties for each folder' configuration
https://bugs.kde.org/show_bug.cgi?id=408617 HM changed: What|Removed |Added Summary|Dolphin doesn't remember|Dolphin doesn't remember |icon size with 'remember|icon size with 'remember |properties for each folder' |properties for each folder' ||configuration -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408617] New: Dolphin doesn't remember icon size with 'remember properties for each folder'
https://bugs.kde.org/show_bug.cgi?id=408617 Bug ID: 408617 Summary: Dolphin doesn't remember icon size with 'remember properties for each folder' Product: dolphin Version: 19.04.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: mcmailf...@protonmail.com Target Milestone: --- SUMMARY Dolphin does not remember icon sizes/zoom level per folder when using icon view even when 'Remember properties for each folder' is enabled in Dolphin configuration. This used to work before but I remember it stopped working after the update with the change https://phabricator.kde.org/D19661 which changed the Dolphin default configuration to 'Use common properties for all folders'. STEPS TO REPRODUCE 1. Change Dolphin configuration to 'Remember properties for each folder' 2. Resize icons in a folder (in icon view) to some size. 3. Go to another folder. OBSERVED RESULT The icon sizes in all folders have changed to the icon size set in folder in step 1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395390] After making the default panel vertically-oriented, Kickoff's layout is messed up until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=395390 HM changed: What|Removed |Added CC||mcmailf...@protonmail.com --- Comment #20 from HM --- I can confirm the bug on plasmashell 5.15.1. And although I remember this bug appearing only after I updated to a plasma version a while back, I unfortunately do not remember the version. -- 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 HM changed: What|Removed |Added CC||mcmailf...@protonmail.com --- Comment #69 from HM --- Issue still there in Konsole, Yakuake,Kate Plasma version 5.14.4 Scaling at 1.4 Linux 4.19 -- You are receiving this mail because: You are watching all bug changes.
