[Spectacle] [Bug 455362] New: Spectacle segmentation fault in libjasper after copying image to clipboard

2022-06-15 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=455362 Bug ID: 455362 Summary: Spectacle segmentation fault in libjasper after copying image to clipboard Product: Spectacle Version: 22.04.2 Platform: Archlinux Packages

[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard

2022-06-15 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=455362 --- Comment #2 from CUI Hao --- (In reply to Yerrey Dev from comment #1) > Are you using JP2 file format in Configure -> Save -> Filename? > It's PNG. I never changed the setting. I also wonder about why JP2 format is used. But I cou

[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard

2022-06-15 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=455362 --- Comment #3 from CUI Hao --- I can confirm Gwenview and possibly other Qt programs crashes at the same place when copying image data. I reproduced the bug using this very simple Qt program: ``` int main(int argc, char *argv[]) { QApplication a

[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard

2022-06-16 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=455362 --- Comment #4 from CUI Hao --- Well, copying is now OK after I rebooted the system. Saving as jp2 file still triggers segfault. There was probably another bug in clipboard functions. But I think we can focus on the jp2 issue for now... -- You are

[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard

2022-06-16 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=455362 --- Comment #5 from CUI Hao --- So this is not a Spectacle-specific bug. It's a bug of Qt or Jasper. FYI, I submitted a bug report to Qt: https://bugreports.qt.io/browse/QTBUG-104398 -- You are receiving this mail because: You are watching al

[plasmashell] [Bug 459715] Wallpaper "crashes" and only black background shown when external display connected (wayland)

2022-09-28 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=459715 CUI Hao changed: What|Removed |Added CC||cuihao@gmail.com --- Comment #10 from CUI Hao

[kwin] [Bug 470189] New: One of two screens randomly goes white and blank after wake up

2023-05-23 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=470189 Bug ID: 470189 Summary: One of two screens randomly goes white and blank after wake up Classification: Plasma Product: kwin Version: 5.27.5 Platform: Other OS:

[kwin] [Bug 470189] One of two screens randomly goes white and blank after wake up

2023-05-24 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=470189 --- Comment #1 from CUI Hao --- Created attachment 159225 --> https://bugs.kde.org/attachment.cgi?id=159225&action=edit Flickering There is also a chance the screen enter the state where it flickers between white and normal video when I m

[kwin] [Bug 470189] One of two screens randomly goes white and blank after wake up

2023-06-06 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=470189 --- Comment #3 from CUI Hao --- I think it's amdgpu driver's issue: https://gitlab.freedesktop.org/drm/amd/-/issues/2354 I'm trying amdgpu.sg_display=0 kernel parameter mentioned in that thread. The system has been running half a da

[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel

2022-10-15 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=452219 --- Comment #15 from CUI Hao --- Tested on plasma 5.26 + kernel 6.0 + nvidia-open 520.56.06. Still saw the same issue. Is this related to DMABUF support on NVIDIA card? https://github.com/NVIDIA/open-gpu-kernel-modules/discussions/243 -- You are

[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel

2022-06-21 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=452219 CUI Hao changed: What|Removed |Added CC||cuihao@gmail.com -- You are receiving this mail

[krunner] [Bug 455961] New: KRunner pops up at wrong position after active screen changed since 5.25

2022-06-26 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=455961 Bug ID: 455961 Summary: KRunner pops up at wrong position after active screen changed since 5.25 Product: krunner Version: 5.25.1 Platform: Archlinux Packages OS:

[krunner] [Bug 455961] KRunner pops up at wrong position after active screen changed since 5.25

2022-06-26 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=455961 --- Comment #1 from CUI Hao --- Created attachment 150169 --> https://bugs.kde.org/attachment.cgi?id=150169&action=edit KRunner pops up at the center of the right screen -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel

2022-06-30 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=452219 --- Comment #10 from CUI Hao --- Created attachment 150302 --> https://bugs.kde.org/attachment.cgi?id=150302&action=edit My KDE log (default setting + KWIN_DRM_DEVICES to nvidia) My PC has a similar setup to a typical I+N laptop. I set Intel

[kwin] [Bug 456453] New: Windows in the 2nd screen are placed outside visible area when a panel is placed between screens and PLASMA_USE_QT_SCALING is set

2022-07-07 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=456453 Bug ID: 456453 Summary: Windows in the 2nd screen are placed outside visible area when a panel is placed between screens and PLASMA_USE_QT_SCALING is set Product: kwin V

[kwin] [Bug 456453] Windows in the 2nd screen are placed outside visible area when a panel is placed between screens and PLASMA_USE_QT_SCALING is set

2022-07-07 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=456453 CUI Hao changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail

[kwin] [Bug 456453] Windows in the 2nd screen are placed outside visible area when a panel is placed between screens and PLASMA_USE_QT_SCALING is set

2022-07-13 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=456453 --- Comment #2 from CUI Hao --- (In reply to Nate Graham from comment #1) > Pretty sure this'll be fixed by the fix for Bug 450443. > > *** This bug has been marked as a duplicate of bug 450443 *** But it seems all the patches in bug 4

[plasmashell] [Bug 455961] KRunner pops up at wrong position after active screen changed since 5.25

2022-08-11 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=455961 --- Comment #3 from CUI Hao --- (In reply to Alexander Lohnau from comment #2) > Are you on X11 or Wayland? X11. Nvidia + Intel dual cards barely work on Plasma Wayland (ref: #452219) -- You are receiving this mail because: You are watching all

[kwin] [Bug 475546] New: Unable to grab mouse cursor on Wayland

2023-10-12 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=475546 Bug ID: 475546 Summary: Unable to grab mouse cursor on Wayland Classification: Plasma Product: kwin Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED

[systemsettings] [Bug 430388] New: Custom Shortcuts cannot record key presses

2020-12-14 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=430388 Bug ID: 430388 Summary: Custom Shortcuts cannot record key presses Product: systemsettings Version: 5.20.4 Platform: Other OS: Linux Status: REPORTED Severity: n

[systemsettings] [Bug 430388] Custom Shortcuts cannot record key presses

2020-12-14 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=430388 CUI Hao changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail

[kwin] [Bug 489623] Maximizing window while panel is floating causes screen glitches

2024-07-08 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=489623 CUI Hao changed: What|Removed |Added CC||cuihao@gmail.com --- Comment #1 from CUI Hao

[systemsettings] [Bug 494118] kcm_keyboard crashed when browsing the keyboard layout list

2024-10-08 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=494118 --- Comment #2 from CUI Hao --- Does this help? Core was generated by `systemsettings kcm_keyboard'. Program terminated with signal SIGSEGV, Segmentation fault. Downloading source file /usr/src/debug/glibc/glibc/nptl/pthread_kill

[systemsettings] [Bug 494121] New: Many keyboard layouts seem to be wrongly put under "bqn" label

2024-10-04 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=494121 Bug ID: 494121 Summary: Many keyboard layouts seem to be wrongly put under "bqn" label Classification: Applications Product: systemsettings Version: 6.1.5 Platform: Arch Linux

[systemsettings] [Bug 494121] Many keyboard layouts seem to be wrongly put under "bqn" label

2024-10-04 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=494121 --- Comment #1 from CUI Hao --- Created attachment 174421 --> https://bugs.kde.org/attachment.cgi?id=174421&action=edit Screenshot 2 -- Keyboard Preview failed -- You are receiving this mail because: You are watching all bug changes.

[systemsettings] [Bug 494119] New: Nonsense country emoji icons in the keyboard layout list

2024-10-04 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=494119 Bug ID: 494119 Summary: Nonsense country emoji icons in the keyboard layout list Classification: Applications Product: systemsettings Version: 6.1.5 Platform: Arch Linux

[systemsettings] [Bug 494118] kcm_keyboard crashed when browsing the keyboard layout list

2024-10-04 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=494118 CUI Hao changed: What|Removed |Added Component|generic-crash |kcm_keyboard CC

[systemsettings] [Bug 494118] New: kcm_keyboard crashed when browsing the keyboard layout list

2024-10-04 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=494118 Bug ID: 494118 Summary: kcm_keyboard crashed when browsing the keyboard layout list Classification: Applications Product: systemsettings Version: 6.1.5 Platform: Arch Linux

[systemsettings] [Bug 494190] New: Noname but selectable ghost entries in the "Device" dropdown

2024-10-05 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=494190 Bug ID: 494190 Summary: Noname but selectable ghost entries in the "Device" dropdown Classification: Applications Product: systemsettings Version: 6.1.5 Platform: Arch Linux

[ksplash] [Bug 494840] New: KSplash screen takes long time after 6.2.1

2024-10-15 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=494840 Bug ID: 494840 Summary: KSplash screen takes long time after 6.2.1 Classification: Plasma Product: ksplash Version: 6.2.1 Platform: Arch Linux OS: Linux Status: REPORT

[ksplash] [Bug 494840] KSplash screen takes long time after 6.2.1

2024-10-15 Thread CUI Hao
https://bugs.kde.org/show_bug.cgi?id=494840 --- Comment #1 from CUI Hao --- Looks like this change between 6.2.0 and 6.2.1 caused the issue: ``` diff --git a/startkde/systemd/plasma-ksplash-ready.service.in b/startkde/systemd/plasma-ksplash-ready.service.in index 3f6744f378..0bd88e6c92 100644

[plasmashell] [Bug 358719] fcitx creates blank unusable xembed icon in systray

2016-02-04 Thread CUI Hao via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358719 CUI Hao changed: What|Removed |Added CC||cuihao@gmail.com --- Comment #5 from CUI Hao